
Most robotic arms come with a dedicated controller: a separate box that sits between the robot and the medical device's own controller. Every command and every feedback sample has to go through it. Kinova took a different approach with KIMA, its next-generation medical-grade robotic arm. The KIMA Robot Control Library (RCL) runs directly on the OEM controller, the real-time computer already at the heart of your medical device. There is no controller in the middle, so your application gets real-time performance that has not been possible before. And a single controller can run up to four KIMA arms.
In a typical architecture, the application on the OEM controller sends commands to the robot controller, which then drives the joints. That intermediate controller runs its own cycle, buffering and scheduling. Each layer adds latency and jitter, and the timing it adds is hidden from the device developer.
It also adds hardware: one more box to integrate, mount, cable, power, cool and maintain, and one more component to account for in the medical device.
KIMA's seven actuators sit directly on an EtherCAT network (100 Mbps, CiA 402 drive profile). Your OEM controller is the EtherCAT master, and RCL runs the real-time control loop on it, on Linux RT or QNX. RCL supports both x86 and arm64 architectures, so you can pick the computer that fits your device, from industrial PCs to compact embedded boards. Your application and the robot control run in the same real-time loop, on the same computer.
The result is best-in-class real-time control at 1 kHz, with minimal jitter and latency between your control loop and the actuators. In every cycle, your application reads joint feedback and sends commands straight to the joints, with no extra controller adding its own timing.
A single OEM controller hosting RCL can control up to four KIMA arms. Instead of one dedicated controller per robot, all arms share the same real-time computer and run in the same 1 kHz control loop.
Because every arm is driven from the same loop, coordinating them is straightforward: their feedback is read and their commands are sent in the same cycle, without synchronizing separate controllers over a network. This opens the door to multi-arm procedures, such as one arm holding an instrument while another positions a camera or an imaging device, with fewer components and a smaller footprint than a setup with one controller per arm.
RCL is a high-performance C++ library that gives you the level of control your application needs:
In many medical procedures, the clinician positions the arm by hand. RCL makes that interaction feel natural: because hand guiding runs in the same 1 kHz real-time loop as the rest of the control, the arm responds instantly and smoothly to the user's hand, with no lag or jerk from an intermediate controller.
RCL was developed for KIMA's IEC 62304 Class C software. It is not a prototyping layer that must be replaced later: it is the control foundation that goes into the medical device.
For development and quick prototyping, Kinova also offers a ROS 2 package built on top of RCL. Teams can visualize, simulate and iterate in ROS 2, then integrate RCL directly in C++ when the project moves toward a product. The control library used in the lab is the same one that ships, so the path from lab to product is shorter and less risky.
To learn more about KIMA RCL and how to integrate it in your medical device, contact info@kinovarobotics.com.