Skip to content

OPC UA

Connects CONNECT as an OPC UA client to an OPC UA server, for example a CODESYS runtime or a PLC with a built-in server. CONNECT connects anonymously with security policy None, so the server must allow that. Addresses are NodeIds.

ParameterExample
Endpointopc.tcp://192.168.1.20:4840

Addresses are node ids as the server publishes them, for example ns=2;s=Motor1.Speed. The address space can be browsed, so signals are usually selected rather than typed.

Browse reports the OPC UA data type (Boolean, Int16, Double, …) and a direction only where the node’s access level states one: a read-only node is a PLC output, a write-only node a PLC input. Most servers, CODESYS included, publish their variables as readable and writable, so these arrive without a direction. A signal the model already has takes the model’s direction; any other one is bound as a PLC output and can be switched in the signal dialog. See Who decides the direction.

  • Manually. Enter the NodeId as the server publishes it, for example ns=2;s=Motor1.Speed.
  • Browse. Yes. Browse opens a separate connection, reads the server’s address space and lists nodes with their OPC UA data type. A direction is proposed only where the node’s access level states one.
  • File import. No protocol-specific file import. Use Addresses → Import address table… (see below) for a list prepared elsewhere.
  • From the model. When the model already has its PLC signals, Addresses → Fill from controller… in the signal-mapping section of the CONNECT panel previews matches by exact name against what Browse finds and then writes the addresses. Addresses → Import address table… takes a CSV or TSV with name;address[;dataType[;topic]] rows. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. See Configuring interfaces.

How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.