Guide · Robotics middleware
Connect PLEXA with ROS 2
Use the public integration boundary to distinguish model and visualization support from governed robot control.
Available now
Model, visualization, and planning context
The current ROS 2 path covers a PLEXA robot description and an RViz workflow. MoveIt planning groups and kinematics configuration are available as development evidence.
PLEXA geometry, joints, and visualization context.
Inspect the model and joint state representation.
Planning groups and kinematics without Runtime execution.
Governed command and feedback mapping for PLEXA.
Control boundary
ROS 2 does not bypass HorstOS
A robot model or successful motion plan does not imply that commands may be sent directly to drives or realtime components. The future bridge terminates at the same Runtime boundary as every other high-level client.
The public ROS 2 package and installation commands will be published after compatibility and control-boundary tests are part of the release process.