Skip to content

RoboDK

Talks to a running RoboDK through its API. CONNECT never starts RoboDK or opens a station by itself.

ParameterExample
Host / Portlocalhost / 20500
Robot nameempty = first robot of the station
Program nameMainProgram (optional)

Talks to a running RoboDK through its API — CONNECT never starts RoboDK or opens a station by itself, and your RoboDK licence must allow API access. Addresses: axis<n> (joint values in RoboDK’s units, also published as <interface>.axis1 …), param:<name> (a station parameter, read every 500 ms or written on change depending on the signal direction), sim:speed (simulation speed), and prog:run, prog:stop, prog:loop to control the named program. Program feedback comes back as <interface>.prog.busy, .done and .error. Switching RoboDK to simulation mode and setting its speed on connect happen 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.

  • Manually. Enter axis<n>, param:<name>, sim:speed, prog:run, prog:stop or prog:loop.
  • 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.