
Many teams building medical robots solutions start in ROS 2. It is where they visualize, simulate, plan motion and iterate quickly. Kinova is now bringing that workflow to KIMA, its next-generation medical-grade robotic arm, with a ROS 2 package built on top of the KIMA Robot Control Library (RCL). Teams moving from Gen3 to KIMA can keep the tools they know and get full access to KIMA's real-time architecture.
KIMA does not put a closed, embedded controller between your software and the joints. Its seven actuators sit directly on an EtherCAT network (100 Mbps, CiA 402 drive profile), and your own real-time computer is the EtherCAT master. No extra controller adds its own cycle, buffering or scheduling to the loop.
The result is best-in-class, real-time low-level 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 position (CSP), velocity (CSV) or torque (CST) commands straight to the joints.
A simulation is only as useful as its match with the real robot. When the control loop runs at a fixed 1 kHz with minimal jitter and latency, the physical arm behaves the way your control model expects, without hidden timing from an embedded controller. This means:
The ROS 2 package does not reimplement control. It relies on RCL, Kinova's high-performance, medical-grade C++ robot control library, developed for KIMA's IEC 62304 Class C software. RCL runs the real-time loop on Linux RT or QNX and provides both low-level joint control (CSP, CSV, CST) and high-level control (Cartesian position and velocity, joint position and velocity, and wrench).
The ROS 2 node connects directly to the RCL real-time loop. ROS 2 adds convenience and ecosystem access, while RCL keeps ownership of the timing-critical path.
ROS 2 is very useful for developing and quickly prototyping medical-grade solutions. With the KIMA ROS 2 package, teams get:
The ROS 2 package is for development and prototyping. It is not medically certified and is not intended for deployment in commercial or clinical systems. When a project moves toward a product, teams keep the same foundation: RCL, integrated directly in C++. The control library used during prototyping is the same one that goes into the medical device, so the path from lab to product is shorter and less risky.
The KIMA ROS 2 package and example projects are available on Kinova's public GitHub repository. For more information, contact info@kinovarobotics.com