ROS command and buffered RT paths
Two separate components connect ROS to the stack. Choose according to execution ownership; using both does not establish arbitration.
| Component | Path | Behavior |
|---|---|---|
| plexa-ext-ros | ROS → Runtime Command API | Maps joints and units, forwards complete operations; no local planning/retiming |
| fruitcore_ros2 | MoveIt → BufferedTrajectoryController → hardware/client → RT → KL7 | Resamples complete trajectories to 2 ms, buffers ahead, handles cancel and completion |
Use the Runtime command guide for complete operations and Runtime feedback. The RT workspace pins the buffered path for cyclic joint targets. ROS uses radians/metres; select RAD in the RT client and verify the joint mapping.
ROS RT feedback uses receipt time without sensor source timestamps. Measured feedback belongs to the documented real six-axis HORST configuration. New suffix replacement requires running-system acceptance; measured feedback for other multi-axis configurations needs separate verification.
A combined deployment requires explicit Runtime/RT execution coordination and a compatible Neo ComMsg connector. The two paths provide no shared arbitration by themselves.
Sources and recorded runs
The fruitcore_ros2 README records Mock, TCP-Fake and real six-axis HORST runs. Its revisions and test conditions define those results. The ROS TODO tracks running-system acceptance of suffix replacement.
RT guide · Deployment · Coming soon · fruitcore_ros2 source