Skip to content

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.

PUBLIC CONCEPTSafe architectural / educational information.

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
See it animated

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.

  1. Business / warehouse
  2. Orchestration
  3. Communication
  4. Network
  5. Robot software
  6. Embedded control
  7. Electromechanical
  8. Physical world

One command, slowed down

  1. Warehouse requestSOFTWARE
  2. OrchestrationSOFTWARE
  3. SchedulingSOFTWARE
  4. Communication serviceSOFTWARE
  5. NetworkNETWORK
  6. Wi-FiNETWORK
  7. Robot softwareSOFTWARE
  8. Safety checkCONTROL
  9. Motion controlCONTROL
  10. DriversELECTRICAL
  11. Motors & mechanismELECTRICAL
  12. SensorsSENSOR
  13. State reportNETWORK
  14. 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 CONTROLMQTT BROKERROBOT CLIENTorder

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

  1. Operator UISOFTWARE
  2. Control interfaceSOFTWARE
  3. NetworkNETWORK
  4. Robot wireless clientNETWORK
  5. Robot computerSOFTWARE
  6. Safety & interlocksCONTROL
  7. Motion controllerCONTROL
  8. Lift driverELECTRICAL
  9. Lift motorELECTRICAL
  10. ↑ FEEDBACK RETURNS

    EncoderSENSOR
  11. ControllerCONTROL
  12. Robot softwareSOFTWARE
  13. Operator UISOFTWARE

Physical robot

IDLE

05 · Orchestration

Who decides what happens next?

  1. 01Upstream systemWMS / ERP / OMS send demand.
  2. 02Orchestration layerDecides what work happens, when and where — for example GreyMatter.
  3. 03Equipment scheduling / algorithmsTask allocation, path planning, traffic and charging.
  4. 04Robot / control interfacesTranslate tasks into robot messages (APIs, VDA 5050, vendor interfaces).
  5. 05RobotInterprets and executes.
  6. 06HardwareControllers, drives, motors, sensors.
PUBLIC CONCEPTSafe architectural / educational information.

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.