Purpose
Understand the message flow between fleet control and mobile robots.
Prerequisites
- Familiarity with MQTT publish/subscribe
Safety considerations
- Follow your site's lockout / isolation and robot-zone entry rules before approaching equipment.
- Only trained, authorized personnel perform service actions. This page is concept training.
Normal behavior
Robot publishes connection and state regularly; orders and instant actions arrive and are acknowledged through state.
Conceptual operation
- Fleet control → broker → robot: order, instantActions.
- Robot → broker → fleet control: state, visualization, connection, factsheet.
Inspection points
- Broker connectivity
- Message timestamps
Diagnostics
- Is 'connection' reporting online?
- Is 'state' updating?
- Do order IDs in state match the last order?
Common symptoms
- Order sent but robot idle
- State stale
Recovery decision tree
1. Is state updating?
YES → Compare order/state IDs and errors.
NO → Check connection topic, broker session and network.
Authorized procedure
INTERNAL / AUTHORIZED ONLY
Broker addresses, credentials, certificates and topic namespaces — available only in the model-specific, authorized SOP for your site. Not published on this website.
Verification
- Orders execute and state reflects progress
Escalation
Integration owner with message timestamps (no credentials).