AutoXing Mars
The AutoXing Mars class is a service robot Hybot's Core RMS supports out of the box through the AutoXing cloud API. Paired to a project it joins that venue's fleet, accepts delivery, collection and bill tasks, streams position, state and battery to the dashboard, and returns to its dock to charge automatically.
What we can state
| Vendor | AutoXing |
|---|---|
| Integration | AutoXing cloud API |
| Core RMS robot type | autoxing_mars |
| Live telemetry | Position, state and battery over WebSocket |
| Task types accepted | DELIVER_ORDER, GET_ORDER, DELIVER_BILL, COLLECT_DISHES |
| Charging | Automatic below a configurable battery threshold |
| Fleet statistics recorded | Lifetime and daily task and distance totals |
What Core RMS does with this robot
Once the robot is paired to a project it becomes a member of that project's fleet. The assignment scheduler treats it like any other robot: every two seconds it is scored against every waiting task by priority, distance and battery together, and the best pairing is committed. There is no queue someone has to work through by hand.
Robots can be added, removed and reloaded with no server restart, and a misconfigured robot is skipped at startup with a warning rather than taking the whole fleet down with it. An inactive robot still broadcasts its state; it is simply passed over for assignment.
Supported task types
| Task type | Meaning | Capability |
|---|---|---|
DELIVER_ORDER | Carry a placed order out to a table. | Delivery |
DELIVER_BILL | Take the bill to a table. | Delivery |
GET_ORDER | Collect an order from the pass. | Collection |
COLLECT_DISHES | Return used dishes to the wash. | Collection |
Beyond the four task types, POST /api/robots/{id}/go-to-poi dispatches a
robot straight to a named point on the floor plan, which is the mechanism
behind guiding a guest to a table.
What is on this page and what is not
Everything above is integration behaviour we can point at in the product. Hardware figures — payload, tray count, battery life, dimensions, speed — are not listed, because we quote them from the vendor's current sheet for the exact configuration being ordered rather than from memory. Ask for them in the quote and they arrive with it.
Where this robot fits
- Delivery — orders and bills out to the table
- Collection — dishes and orders back
- Guidance — leading a guest to a point on the floor plan
- Service robots for restaurants — the whole loop in one room
Common questions
- Do I need a separate controller for each robot?
- No. Core RMS talks to every paired robot from one project instance, so a venue configures floors, points of interest and task rules once rather than per robot. Robots can be added, removed and reloaded without restarting the server.
- What happens when a robot runs low on battery?
- Each robot has a configurable battery threshold. When it drops below that level the robot is taken out of the assignment pool and sent to charge, and it rejoins automatically once it is charged. Nobody has to watch a battery gauge.
- Where are the payload, battery life and dimension figures?
- They are not published here. We quote the vendor specification from the vendor's own current sheet for the exact configuration being ordered, so those figures come with the quote rather than from a marketing page that could go stale.