UR5e teleoperation: RTDE streaming, leader arms and remote help for the arm now sold as the UR7e

The Universal Robots UR5e is a 6-axis cobot with a 5 kg payload, an 850 mm reach and ±0.03 mm repeatability. Universal Robots says more than 90,000 of its cobots have been delivered, and the UR5e is the model that three separate community LeRobot integrations target. That gives it two teleoperation audiences: research teams collecting demonstrations, and plants that want a person to step in remotely when a program runs into something it cannot handle. Both start with the same question, because UR no longer sells it under that name.

UR5e or UR7e: what actually changed

UR's e-Series page now lists a UR7e where the UR5e used to be, and UR's own announcement for Vietnam describes the UR7e and UR12e as upgraded versions of the UR5e and UR10e, with payloads raised to 7.5 kg and 12.5 kg. Put the numbers side by side and the overlap is obvious:

For teleoperation and data collection this matters in one place: configuration. The UR ROS 2 driver accepts ur5e and ur7e as separate robot types, and leader arms, URDFs and inverse kinematics should match the arm you actually have. Datasets recorded on a UR5e remain the closest public reference for a UR7e on CB5.

"UR5e remote control" means three different things

How to stream motion to a UR5e

The RTDE interface exchanges data with the controller at up to 500 Hz on e-Series robots without breaking its real-time behavior. Two details catch people out. Connecting from an external PC requires enabling the RTDE service in the robot's security settings, and only one RTDE client can control a given input variable at a time, so a teleop client and a second tool cannot both write the same registers. If the controller is short of resources it skips output packages and sends only the most recent data.

The UR ROS 2 driver covers e-Series, PolyScope X and CB3 controllers, with release branches for Humble, Jazzy, Kilted and newer. It runs through the External Control URCap: you press play on an external_control program on the pendant (or use headless mode), and ROS takes over motion from inside that program. Its controller set is what makes it useful for teleoperation:

For joint-space teleoperation, the open-source GELLO leader arm already has UR5e code you can start from. The lerobot_ur5e_gello project pairs a GELLO leader with a UR5e and Robotiq gripper over RTDE, records LeRobot datasets, and serves π0 policies from a GPU server for inference.

Control rates and latency

The controller can take updates at 500 Hz, but nobody teleoperates at 500 Hz. The operator's device and the policy you train usually run at 10 to 30 Hz, and the PC next to the robot fills the gap by interpolating and clamping velocity. At 20 Hz a step is 50 ms, which sets the budget for a remote operator:

Run the operator's client on your side of a VPN and stream targets, rather than streaming a remote desktop. Our latency guide has budgets by task.

Safety with a remote operator: the controller stays in charge

Per the UR5e datasheet, the arm has 17 configurable safety functions and complies with EN ISO 13849-1 (PLd, Category 3) and EN ISO 10218-1. A remote operator works inside that configuration and never edits it. The practical rules we apply on a UR cell:

Typical exceptions on a UR cell are a part that landed in the wrong place, a regrasp after a slipped pick, or a fixture that jammed. Each one is a short teleoperated recovery, and each recovery can be logged as a correction episode for the next version of the program or policy. More on that model in our warehouse and factory page.

Data and LeRobot on a UR5e

LeRobot does not include a UR driver of its own, but its third-party robots page lists three UR5e integrations: lerobot_robot_ur5e, a drop-in plugin for a UR5e with a Robotiq gripper over RTDE; UR5e-LeRobot, an extension with single-arm and bimanual support; and lerobot_ur5e_auto, an extension for a mobile UR5e that records at scale with minimal supervision. The two extensions are marked as needing custom setup rather than working with an unmodified LeRobot install.

For a public reference, lerobot/berkeley_autolab_ur5 is a LeRobot port of UC Berkeley Autolab's UR5 demonstrations: 1,000 episodes with three 640×480 camera streams, recorded at 5 fps. It is the older UR5, not the e-Series, and 5 fps is slower than most current policies expect, so treat it as a reference rather than a pretraining set. Our data collection guide covers formats and checks.

What a good UR operator does

UR5e, UR10e or a research arm?

The UR10e (now UR12e) uses the same software stack with 12.5 kg and 1300 mm, which suits palletizing and larger machine tending. For pure research data on contact-rich tasks, a torque-sensing 7-axis arm such as the Franka Research 3 gives joint-level torque feedback and a redundant elbow. The UR5e's strengths are an interface that is the same on the lab bench and the factory floor, and a software ecosystem (the ROS 2 driver, RTDE and three LeRobot integrations) that already exists.

How RoboPilots runs UR5e teleoperation

The arm stays where it is. We agree the input device with you (GELLO, 3D mouse or VR), install the operator client on your side of a VPN, and agree the hand-over points and stop rules with whoever owns the cell's safety. Then we train a dedicated group of operators on your unit and your task protocol before they touch a live cell or record an episode.