Universal Robots
Overview
Section titled “Overview”Reads joint positions, digital outputs and robot state over RTDE from URSim or a UR controller; inputs are set through a short URScript program.
Set up and parameters
Section titled “Set up and parameters”| Parameter | Example |
|---|---|
| Host | 192.168.0.4 |
| RTDE / secondary port | 30004 / 30001 |
| Output frequency | 20 Hz |
Joint positions, digital outputs and robot state are read over RTDE; joints are converted to degrees and also published as <interface>.axis1 … axis6. Addresses: do0 … do7 and cdo0 … cdo7 (digital and configurable outputs, read), di0 … di7 and cdi0 … cdi7 (inputs, written), axis1 … axis6, status and runtime. IO numbering is zero-based, as on the teach pendant. Inputs are set with a short URScript program on the secondary port, sent only when a value changes.
Create or import signals
Section titled “Create or import signals”- Manually. Enter
do0…do7andcdo0…cdo7(read),di0…di7andcdi0…cdi7(written),axis1…axis6,statusorruntime. IO numbering is zero-based. - Browse. No browse: enter addresses by hand.
- File import. No protocol-specific file import.
- From the model. Use Addresses → Import address table… in the signal-mapping section of the CONNECT panel: a CSV or TSV with
name;address[;dataType[;topic]]rows, where the name is the model’s signal name. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. Fill from controller… has nothing to match, because this protocol cannot be browsed. See Configuring interfaces.
How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.
See also
Section titled “See also”- Common concepts — text signals, direction, write access, tracking signals
- Configuring interfaces — adding signals, direction and write access
- All supported interfaces
- Troubleshooting — connection and signal problems