RLSOK
UR5e reference integration

Start a UR5e release-authorization evaluation in Shadow

Check whether your environment matches the documented UR5e reference before starting. RLSOK checks whether an approved software release still matches its robot and controller configuration. Shadow records that decision without sending controller commands. Physical UR5e behavior is not established by this reference.

Updated · RLSOK

Download and try RLSOK
01

Exact tested environment

Robot
Universal Robots UR5e
Operating system
Ubuntu 24.04 x86_64
ROS
ROS 2 Jazzy
RMW
Fast DDS through rmw_fastrtps_cpp
Driver
official Universal Robots ROS 2 Driver
Controller
scaled_joint_trajectory_controller
02

Automatic discovery boundary

  • Identify UR5e from robot_description in the same ROS namespace.
  • Require the official-driver controller-manager signals used by the tested profile.
  • Require a complete six-joint UR5e JointState sample.
  • Require the active trajectory controller's claimed joints to match that observed joint set.
  • Reject Universal Robots driver graphs that do not form the validated UR5e profile.
03

Validation performed

  • Launch the official driver with ur_type:=ur5e and use_mock_hardware:=true.
  • Run the scaled_joint_trajectory_controller in the official reference graph.
  • Use real ROS 2 Jazzy DDS discovery rather than replacing DDS with an in-process stub.
  • Verify that Shadow receives proposals while attempting zero controller goals.
  • Generate and verify Evidence for the resulting decisions.
04

What is not yet proven

The current proof does not include a physical UR5e, physical motion, site-specific controller parameters, task performance, functional safety, or production-readiness certification. Mock-hardware validation proves the software integration boundary, not physical behavior.

05

Start with the environment you already have

Use the current stable installer and the published Zero-to-Shadow instructions. The documented reference requires Ubuntu 24.04 x86_64, ROS 2 Jazzy, Fast DDS, the official Universal Robots ROS 2 Driver, a running UR5e mock graph, live JointState and the active scaled_joint_trajectory_controller. Setup also requires Hosted pairing and independent approval of the exact release.

After setup, inspect the actual decision and Evidence. Expected Shadow outcomes include zero controller goals attempted and no hardware signal sent. If a prerequisite is missing or a step fails, report the first blocked step. A successful reference attempt does not validate a third-party integration or physical motion.

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

Start the documented Shadow setupUnderstand configuration changes and approvalFull support matrixShadow Mode behaviorReference environment documentation

Try the local example without an application. For setup or integration help, you can also contact us.