Robot arm controllers: where the SBC belongs, and where the servo loop has to live

A six-axis robot arm picking a part, operator at the teach pendant

A six-axis arm needs a 1 kHz current loop, a 100 to 400 Hz position loop and a trajectory planner. No general-purpose Linux board does the inner loops; that is the servo drive's job. What the board does well is the layer above: trajectory planning, hand-eye vision, the teach pendant, fieldbus supervision and the log that lets you prove why a move failed.

What the control layer requires

  • Fieldbus with real-time behaviour. EtherCAT or PROFINET need a dedicated network interface, PREEMPT_RT and a cycle budget that leaves room for the application. Plan the hardware with a spare MAC.
  • Vision. Two to four cameras for pick accuracy: one wrist-mounted, one fixed overhead, plus a barcode or part-ID camera.
  • Determinism where it counts. The trajectory is planned on the host, but the interpolation and the safety limits live on the drive or a motion controller.
  • Teach pendant. A panel or a web HMI on the operator's tablet, with a hard-wired emergency stop outside the software path.

Recommended configuration

Function Recommended TOPEET part
Vision-guided arm controller, 2 to 4 cameras iTOP-RK3588S Single Board Computer or iTOP-RK3576: 6 TOPS NPU, up to 5 MIPI-CSI lanes on the module
Four-axis SCARA or palletising cell iTOP-RK3568 Single Board Computer: dual Gigabit Ethernet, CAN, RS-485, PCIe for a second NIC
Cameras IMX415 8 MP Camera Module for part localisation, OV5695 5 MP for the wrist view
Multi-camera carrier Camera Extender Board for RK3588 / RK3576 / RK3568
Teach pendant panel 10.1-inch Capacitive HMI Panel

Interface checklist

  • Dedicated NIC for the fieldbus; keep the vision traffic on the second port.
  • Hard-wired safety chain: E-stop, guard interlock and drive enable do not pass through the host.
  • Encoder feedback is consumed by the drive, not by the host, unless you are building a soft motion controller and have budgeted for PREEMPT_RT tuning.
  • Trigger and strobe lines from the host to the cameras, with the latency documented.
  • UPS or a supervised power-down so the last program state survives a mains dip.

What we would validate with you

Vision cycle time against your required takt, jitter of the host's fieldbus stack with vision running, and the behaviour of the cell when the host is rebooted mid-cycle.

Documents

Schematics, BSP and Linux images are in the resource portal. 12-month warranty, engineering support by email.

Frequently asked questions

Can the host board close the servo loop?

No. A six-axis arm needs a 1 kHz current loop and a 100 to 400 Hz position loop, which is the servo drive's job. The board runs trajectory planning, hand-eye vision, the teach pendant, fieldbus supervision and the log that proves why a move failed.

Which board for a vision-guided cell?

The iTOP-RK3588S or iTOP-RK3576 with a 6 TOPS NPU and up to five MIPI-CSI lanes for two to four cameras. The iTOP-RK3568 covers a four-axis SCARA or palletising cell with dual Gigabit Ethernet, CAN, RS-485 and PCIe for a second NIC.

What must be planned for EtherCAT or PROFINET?

A dedicated network interface, PREEMPT_RT and a cycle budget that leaves room for the application - plan a spare MAC address on the carrier from the start.

0 comments

Leave a comment

Please note, comments need to be approved before they are published.