Software & Control
From warehouse request
to robot motion.
Purpose first, protocol second, details third. See who sends instructions, how they travel and how feedback comes back.
01 · The stack
Seven levels. One movement.
Click any layer. Its neighbours light up; everything else fades.
Level 3
Robot software
The robot's brain: understands the job and plans how to move.
- Sends up
- State reports
- Sends down
- Motion requests
02 · One command
One click. Thousands of operations.
Press Retrieve tote. Time slows down so you can follow the command through every layer — and the confirmation back.
- Business / warehouse
- Orchestration
- Communication
- Network
- Robot software
- Embedded control
- Electromechanical
- Physical world
One command, slowed down
- Warehouse requestSOFTWARE
- OrchestrationSOFTWARE
- SchedulingSOFTWARE
- Communication serviceSOFTWARE
- NetworkNETWORK
- Wi-FiNETWORK
- Robot softwareSOFTWARE
- Safety checkCONTROL
- Motion controlCONTROL
- DriversELECTRICAL
- Motors & mechanismELECTRICAL
- SensorsSENSOR
- State reportNETWORK
- Task updatedSENSOR
03 · VDA 5050
Orders down. State up.
VDA 5050 describes communication between fleet control and mobile robots using MQTT and JSON. Choose a topic to send a message.
Fleet control → broker → robot
order
Fleet control sends the robot a route of nodes and edges, with actions to perform.
Never shown here: broker addresses, credentials, certificates or real topic namespaces.
ILLUSTRATIVE, SIMPLIFIED EXCERPT — SEE THE OFFICIAL SCHEMA
{
"headerId": 42,
"timestamp": "<ISO-8601>",
"version": "<spec version>",
"manufacturer": "<manufacturer>",
"serialNumber": "<robot>",
"orderId": "order-1234",
"orderUpdateId": 0,
"nodes": [{ "nodeId": "relay-A04", "sequenceId": 0, "released": true, "actions": [] }],
"edges": []
}04 · Software → physical
A command on a screen becomes motion.
Left: human interaction. Centre: the software and network path. Right: the robot. Use 0.1× or Step to slow it right down.
Human interaction
AUTHORIZED SERVICE / CONTROL SOFTWARE · SIMULATED
Network / software path
- Operator UISOFTWARE
- Control interfaceSOFTWARE
- NetworkNETWORK
- Robot wireless clientNETWORK
- Robot computerSOFTWARE
- Safety & interlocksCONTROL
- Motion controllerCONTROL
- Lift driverELECTRICAL
- Lift motorELECTRICAL
↑ FEEDBACK RETURNS
EncoderSENSOR- ControllerCONTROL
- Robot softwareSOFTWARE
- Operator UISOFTWARE
Physical robot
IDLE
05 · Orchestration
Who decides what happens next?
- 01Upstream systemWMS / ERP / OMS send demand.
- 02Orchestration layerDecides what work happens, when and where — for example GreyMatter.
- 03Equipment scheduling / algorithmsTask allocation, path planning, traffic and charging.
- 04Robot / control interfacesTranslate tasks into robot messages (APIs, VDA 5050, vendor interfaces).
- 05RobotInterprets and executes.
- 06HardwareControllers, drives, motors, sensors.
Vendors split these layers differently — some combine a warehouse software platform with a separate equipment scheduling system for allocation, path planning and charging.
SITE IMPLEMENTATIONVaries by deployment — confirm against your site's documentation.Your site's exact software path — which product does what, and how it connects to your robots — should be documented as a site implementation, not assumed from a generic vendor diagram.