Skip to content

Bosch Rexroth ctrlX

Two interface types reach a ctrlX CORE: the Data Layer (native) type needs nothing installed on the device, the bridge tunnel uses the ctrlx-rv-bridge snap. Both use the same node paths.

There are two ways to reach a ctrlX CORE, and they are chosen by interface type.

CONNECT authenticates against the ctrlX identity manager and uses the Data Layer API directly. Nothing has to be installed on the device.

ParameterExample
Address / Port192.168.1.30 / 443
User / Passworddevice credentials

Addresses are Data Layer node paths, for example plc/app/Application/sym/MAIN.fSpeed. TLS validation is on by default; accept an untrusted certificate only for a device you deliberately trust with its factory certificate.

The alternative uses the ctrlx-rv-bridge snap running on the device. Deploy the snap on the ctrlX CORE and configure the interface in CONNECT. If the snap is missing, the interface reports this. An optional bridge publish interval (ms) is sent to the bridge on connect. If left empty, the bridge keeps its own setting.

Both modes use the same node paths, so an interface can be moved from one to the other.

  • Manually. Enter the Data Layer node path, for example plc/app/Application/sym/MAIN.fSpeed.
  • Browse. Yes, for both interface types. Browse lists the Data Layer nodes of the device.
  • File import. No protocol-specific file import. Use Addresses → Import address table… for a prepared list.
  • 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.