igus ReBeL
Overview
Section titled “Overview”Connects to the igus robot control (iRC) or its simulation over the CRI protocol.
Set up and parameters
Section titled “Set up and parameters”| Parameter | Example |
|---|---|
| Host / Port | 127.0.0.1 / 3921 |
| Axis count | 6 (up to 9) |
| Speed (override) | 100 % |
Connects to the igus robot control (iRC) or its simulation over the CRI protocol. Addresses: axis<n> (joints in degrees, also published as <interface>.axis1 …), dout<n> (digital output bit, read), gsig<n> (global signal, written), cmd:override and cmd:active (override and enable, written).
cmd:movejoint and cmd:movecart start a move on a rising edge to the set-point signals <interface>.setpoint.axis1 … or <interface>.setpoint.x … rz (cartesian, in robot base coordinates); progress comes back as <interface>.move.busy, .done and .error. A move requested while another one runs is rejected, and a trigger that stays on across a reconnect starts exactly one move. Override and enable on connect are sent only with write access.
Moves and program starts on igus, RoboDK and NOVA need Allow web to PLC, react to a rising edge only and are never repeated after a reconnect.
Create or import signals
Section titled “Create or import signals”- Manually. Enter
axis<n>,dout<n>,gsig<n>,cmd:override,cmd:active,cmd:movejointorcmd:movecart. - 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