A quadruped is the most demanding small robot to instrument: twelve joints, a gait controller that runs at several hundred hertz, two to four cameras looking at terrain, and an operator link that has to stay alive while the robot climbs stairs. The compute split is unforgiving.
What the robot requires
- High-rate vision. Terrain perception wants 60 fps or better at 1080p, from cameras that are rigidly mounted and hardware-triggered.
- Low-latency inference. A missed step is a fall; the perception-to-foot-placement loop has to stay in the tens of milliseconds.
- Joint control off the host. Twelve servo loops with force estimation belong on MCUs or drives on the leg bus; the host plans.
- Power and thermal. A 30 to 60 minute mission on a pack; every watt of host power is range lost.
Recommended configuration
| Function | Recommended TOPEET part |
|---|---|
| Perception host with four cameras | iTOP-RK3588S Single Board Computer (4 GB + 32 GB, six CSI lanes, 6 TOPS) |
| Compact chassis with a custom carrier | iTOP-RK3588S SoM or iTOP-RK3576 SoM (65 x 50 mm) |
| Terrain cameras | OS08A20 Camera Module for low light, IMX415 8 MP for daylight detail |
| Leg bus | CAN from the carrier, one channel per leg group, isolated |
| Operator link | Wi-Fi 5 or 6 on the carrier, RG255AA-CN 5G M.2 Module for outdoor range |
Honest limitation, and the reason we list it: the camera modules on this page carry rolling-shutter sensors. At a walking gait they are fine; at a fast trot or a jump the frame will skew. If your controller runs above roughly 2 Hz leg frequency, specify a global-shutter sensor on the same MIPI-CSI lanes rather than asking a rolling-shutter part to do the job.
Interface checklist
- Four CSI lanes minimum, all hardware-triggered from one source.
- IMU on SPI at 1 kHz or better, timestamped in the kernel.
- Leg bus: CAN FD with isolation, one channel per pair of legs.
- Power: 5 V rail sized for peak inference, with an undervoltage supervisor.
- Thermal: the module on a heat spreader tied to the chassis plate, not to a plastic shell.
What we would validate with you
Camera skew and latency at your gait frequency, thermal soak during a 30-minute mission, CAN jitter with all twelve joints active, and the behaviour when the operator link drops.
Documents
Schematics, module mechanical drawings and BSP sources are in the resource portal. 12-month warranty, email support.
Frequently asked questions
Why must gait control stay off the host board?
Twelve joints running at several hundred hertz need deterministic timing on a dedicated controller. The host's job is terrain perception and foot placement, and that loop has to stay in the tens of milliseconds - a missed step is a fall.
Which compute for a legged robot?
iTOP-RK3588S with 4 GB + 32 GB, six CSI lanes and a 6 TOPS NPU for a perception host with four cameras, or the iTOP-RK3576 SoM at 65 x 50 mm for a compact chassis with a custom carrier.
What is validated before a field trial?
Camera skew and latency at your gait frequency, a 30-minute thermal soak, CAN jitter with all twelve joints active, and the robot's behaviour when the operator link drops.
0 comments