The mock robot simulator
The mock simulator is a software robot that behaves like real hardware inside Hybot's Core RMS. It accepts the same task types, moves across the same floor plans, reports battery and position, and lets a venue rehearse routes and staff workflows before any physical robot arrives on site.
What we can state
| Hardware required | None |
|---|---|
| Integration key | mock |
| Task types accepted | DELIVER_ORDER, GET_ORDER, DELIVER_BILL, COLLECT_DISHES |
| Telemetry | Position, state and battery, over the same live stream as hardware |
| Sold separately | No — part of Core RMS |
Not a robot you can buy
This page is here for completeness, not for the price list. The mock simulator is a software robot inside Core RMS: it is not hardware, it is not sold on its own, and it should never be read as an item in the catalogue. It appears here because it changes how a deployment is planned, and that is worth knowing before you order anything.
Why it exists
Hardware arrives late and floor plans change. Both are normal, and both usually push a deployment date to the right, because every other piece of configuration is waiting behind the robot.
The simulator takes the robot off the critical path. Because it registers in
Core RMS under the mock integration key and accepts the same four task types
as a physical machine, the work that genuinely matters can be done and checked
first:
- Floors and points of interest. Plan images, imported points and the affine alignment between them are all set up and verified without a robot on site.
- Task flows. Delivery, collection and bill tasks are queued and watched through the same assignment pass — the one that re-scores every two seconds by priority, distance and battery.
- Staff training. The dashboard, the customer-request queue and the confirmation steps behave identically, so training is not rehearsal for a different system.
- Guest surfaces. Menus, languages, QR routing and the survey are configured and tested against a running fleet rather than against nothing.
What it does not prove
It proves nothing physical. Doorway widths, lift access, floor surfaces, real battery endurance and how the room behaves at full service are questions about a building and a machine, and they are answered during the site survey with the real robot. A simulator that claimed otherwise would be worse than no simulator at all.
When the hardware lands, the configuration is already there and the fleet is
switched from mock to the real integration.
See the AutoXing Mars integration for the hardware side, what the robots actually do, or a real deployment.
Common questions
- Can the simulator be used for a live demo?
- Yes. It uses the same task pipeline and the same live position stream as real hardware, so a simulated fleet behaves the same way in the dashboard as a physical one and the demo is not a separate build.
- Is the simulator something we buy?
- No. It is not hardware and it is not sold separately. It is part of Core RMS, and it exists so that configuration and training are not blocked waiting for a delivery date.
- What will the simulator not tell us?
- Anything physical. It will not prove that a doorway is wide enough, that a lift can be used, or how long a real battery lasts in your building. Those are confirmed during the site survey with the actual robot, not in software.