robot-system-hero
Robot System

Sensor data from the floor,
to the robot and to your screen

Robot System is our own robot platform. It carries sensor capture, delivery between algorithms,
frame management, remote visualisation, recording and replay on one stack.

Structure

Fast inside one machine,
far between machines

Within a single machine, shared memory cuts the cost of moving large images and point clouds. Between machines, remote transport carries the floor's data to wherever it is needed.

01 Low-latency delivery Sensors and algorithms share one data structure, and inside a machine they share memory.
02 Remote visualisation The state of a machine on the floor and its 3D sensor data, seen on a laptop elsewhere.
03 Record and replay Sensor input is recorded and played back to study a failure or review a change.
Demo

A working plant,
watched from somewhere else

The point cloud a forklift sends up from the floor, put on screen somewhere else with the pick-up and drop-off zones laid over it.

A plant point cloud and its work zones, seen remotely
Speed

How much delivery cost
does it actually save

Rather than copying large images and point clouds to move them, Robot System hands them over through shared memory.
We measured it side by side with ROS 2 on the same machine.

Handing over one point cloud (3.7MB)310× faster
Handing over one 4K frame (24.9MB)11.5× faster
Frames missed by either sideNone

In-house run, 16 September 2026. Time between processes on one machine, using synthetic sensor data.

Internal experiment Time to hand over one point cloud 115,200 points · 3.7MB · 10Hz.
Two seconds of warm-up then a 20-second load, repeated three times; all 600 target frames were received.
Robot System0.035msBaseline
ROS 2 Reliable10.816ms310× slower
p95 is 0.044 against 11.069ms, p99 0.598 against 13.589ms.
Internal experiment Time to hand over one 4K frame 3840×2160 RGB8 · 24.9MB · 30Hz, uncompressed.
Same method; all 1,800 target frames were received.
Robot System1.183msBaseline
ROS 2 Reliable13.645ms11.5× slower
p95 is 1.508 against 24.604ms, p99 2.288 against 35.446ms. This is a ratio of delivery latency, not of throughput, and it does not carry over to traffic crossing a network or to other hardware.
Next

Also worth reading

LOCALIZATION Five kilometres in, and nothing has slipped Start away from the dock, hold position as the site changes. STEREO DEPTH Half a millimetre, from cameras alone Two views are enough to rebuild the 3D shape of the workpiece.
Data flow background

It sits on top of
what you already run

Interface specifications, an SDK and example code come with it. We do not ask you to conform to our conventions.

Talk to us