Skip to content

KUKA iiQKA / RSI

CONNECT is the UDP server of an RSI Ethernet context: the KUKA iiQKA VRC or controller sends a packet every cycle and CONNECT answers each one at once.

ParameterExample
Listen address / RSI port0.0.0.0 / 49152
Cycle4 ms (4, 8 or 12)
Axis count6 (up to 12)
Digital / analog channels8 / 0

CONNECT is the UDP server of an RSI Ethernet context: the KUKA iiQKA VRC or controller sends a packet every cycle and CONNECT answers each one at once, echoing its IPOC. Until the first packet arrives the interface shows Connecting; when packets stop for ten receive timeouts in a row it reconnects. Addresses: digin<n> and anain<n> are written by realvirtual, digout<n> and anaout<n> are read, axis<n> are the joints (actual or set-point positions, selectable). Joint positions are also published as <interface>.axis1 … axisN.

  • Manually. Enter digin<n> and anain<n> (written by realvirtual), digout<n> and anaout<n> (read) or axis<n>. Numbering starts at 1 and must fit the configured channel counts.
  • 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.