Kiwicocoa Robotics 6DOF Framework multi-robot messaging and registry architecture.
The framework establishes a decoupled robot display communication architecture where the source of a message does not need to know what type of display will ultimately render it.
The architecture separates four fundamentally different responsibilities: Message Creation (InteractionContexts), Data Transport (IInteractionContext), Destination Routing (Kiwicocoa6DOFAPI), and Rendering (IRobotDisplayController).
The most important architectural decision is the introduction of the IRobotDisplayController as the universal display boundary. Any object capable of receiving and interpreting a robot interaction context can become a robot display controller (e.g., physical LCDs, uGUI panels, web dashboards).
public interface IRobotDisplayController
{
void ProcessInteractionContext(IInteractionContext context);
}
Displays are routed using a semantic vocabulary of RobotID + DisplayRole, rather than direct GameObject references. A factory method constructs the strongly-typed contexts (like PixelTextInteractionContext) easily.
Example of creating a message payload with semantic status colors and routing it to a robot's Primary Terminal:
var context = InteractionContexts.PixelText(
"SYS: READY",
"MODE: AUTO",
StatusColors.Ready
);
Kiwicocoa6DOFAPI.SendDisplayMessage(
RobotID.Robot_01,
DisplayRole.PrimaryTerminal,
context
);