Supported robots and integrations
Yes, RLSOK supports Universal Robots UR5e as its first official integration, using the official Universal Robots ROS 2 Driver and scaled_joint_trajectory_controller on the documented Jazzy stack. Other robots may be generically ROS 2 compatible, but that is not an official hardware-support claim.
Updated · RLSOK
Find the matching evaluation pathChoose the applicable channel
A recognized message type is only one prerequisite. Check the command meaning, observed receiver, configuration boundary and validation scope before selecting an evaluation.
| Path | Available scope | What remains unproven |
|---|---|---|
| Stable Runtime v1.4.5 | UR5e, official UR driver, Jazzy, Fast DDS and the reference trajectory controller | Physical UR5e operation and site-specific configurations |
| Local Check 1.5.0 | Configure supported interface meanings and field mappings; compare declared configuration and observed facts locally | Humble, private interfaces and physical robot operation |
Support status model
- Official integration
- A named robot, official driver, controller profile, and environment with tested automatic discovery and configuration.
- Generic ROS 2 compatible
- Standard JointState and FollowJointTrajectory interfaces can be integrated, but engineering work and independent validation may be required.
- Experimental / community
- A non-official integration may be explored or maintained outside the verified RLSOK support profile.
- Unsupported
- The required execution boundary or interfaces are absent, or RLSOK explicitly rejects the detected profile.
UR5e official integration matrix
| Field | Tested value | Status |
|---|---|---|
| Robot | Universal Robots UR5e | Official integration |
| Operating system | Ubuntu 24.04 x86_64 | Validated |
| ROS / middleware | ROS 2 Jazzy · Fast DDS through rmw_fastrtps_cpp | Validated |
| Driver | official Universal Robots ROS 2 Driver | Validated |
| Controller | scaled_joint_trajectory_controller | Validated |
| Physical hardware | Physical UR5e motion | Not validated |
What the official validation proves
- official-driver mock/reference simulation.
- real ROS 2 DDS.
- Shadow zero-dispatch.
- Evidence generation and verification.
Generic ROS 2 compatibility
RLSOK can observe sensor_msgs/msg/JointState and use control_msgs/action/FollowJointTrajectory through its reference gateway. Interface compatibility alone does not prove robot identity, controller semantics, automatic setup, hardware behavior, or an official integration.
Local Check 1.5.0 can configure supported Twist, trajectory, Cartesian and allowlisted TP-program meanings with explicit field mappings. Try the included example on Ubuntu, see which setting changed, then choose a guide for your own project. No robot or account is needed for the example. Its public-source recipes are reviewed mappings, not customer endorsements or official support for those robots. Use the configuration and source-workspace guides for each path's exact requirements.
Known limitations
- No physical UR5e hardware validation is claimed by the current release.
- No universal robot compatibility claim is made.
- Non-UR5e models detected through the Universal Robots driver are not promoted to the official profile.
- Every physical deployment still requires the team's own integration, safety, and operational validation.
Sources and verification scope
Source code and guides describe implementation and setup. Release notes identify reported checks and their limits. Publication alone does not establish customer use or physical-robot validation.
Continue with the relevant guide
Try the local example without an application. For setup or integration help, you can also contact us.