An autonomous mobile robot or a service robot carries a sensor set that would have needed a rack of computers ten years ago: two to four cameras, a lidar over Ethernet, an IMU, wheel encoders, a battery management system and a fleet link. The design tension is always the same: more cameras, less power, and a mechanical envelope that keeps shrinking.
What the robot requires
- Camera count and synchronisation. Stereo or multi-view perception needs several MIPI-CSI lanes with hardware trigger, not USB webcams.
- Inference at frame rate. 6 TOPS is the practical entry point for detection plus depth on 1080p streams.
- Real-time chassis control. Motor loops and safety-rated stop functions belong on the MCU or the drive, not on the host.
- Power. 12 to 24 V from the battery pack, with a clean 5 V rail for the compute module and a supervisor that shuts down before the pack cuts off.
- Fleet connectivity. Wi-Fi in the building, 4G/5G outdoors, and an over-the-air update path.
Recommended configuration
| Function | Recommended TOPEET part |
|---|---|
| Perception and planning host | iTOP-RK3588 Single Board Computer with 5G Module for outdoor fleets, or the base kit for indoor units with Wi-Fi |
| Smaller service robot, delivery or disinfection unit | iTOP-RK3576 Single Board Computer: 6 TOPS, three camera interfaces on the carrier, 4G support |
| Custom carrier in the chassis | iTOP-RK3588 Connector SoM (60 x 70 mm, 320 pins) or iTOP-RK3588S SoM |
| Depth and navigation cameras | IMX415 8 MP, OS08A20 Camera Module |
| Cellular backhaul | RM500U-CN 5G Module for RK3588 / RK3568 |
Why RK3588: six MIPI-CSI ports on the module (two 4-lane D-PHY, two 3-lane C-PHY, four 2-lane D-PHY), an 8K decoder for recorded teleop video, a 48 MP ISP, and enough PCIe for an NVMe log and a second NIC. The 5G kit removes the modem integration work from your BOM.
Interface checklist
- Cameras on hardware trigger, with a shared clock; USB cameras will not hold phase.
- Lidar or depth over Ethernet, on a port separate from the fleet link.
- IMU and encoders on the MCU, fused on the host.
- Battery: SMBus or CAN from the BMS, with a host-side shutdown threshold above the pack cutoff.
- Safety: bumpers, e-stop and motor disable in hardware.
What we would validate with you
Thermal behaviour in a sealed chassis, Wi-Fi roaming between access points, camera latency from trigger to inference result, and the power budget at peak inference with the drive accelerating.
Documents
English datasheets, mechanical drawings and BSP sources are in the resource portal. 12-month warranty, email engineering support.
Frequently asked questions
How many cameras can one host take?
Count MIPI lanes before counting cameras: the RK3576 carrier exposes three camera interfaces, an RK3588 module exposes up to six CSI lanes, and an RK3568 carrier exposes one 4-lane port. Stereo or multi-view perception needs hardware-triggered MIPI-CSI, not USB webcams.
What NPU class is needed for frame-rate inference?
6 TOPS is the practical entry point for detection plus depth on 1080p streams, which is why the RK3588 and RK3576 are the default host choices for AMR perception.
What is validated on a mobile robot?
Thermal behaviour in a sealed chassis, Wi-Fi roaming between access points, latency from camera trigger to inference result, and the power budget at peak inference while the drive is accelerating.
0 comments