Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
BaSyx / Documentation / Components / DataBridge / Features / Protocol Integration / PLC4X
Contents
PLC4X
The apache PLC4X can be integrated with DataBridge. Apache PLC4X allows you to communicate directly with your industrial Hardware without retrofitting it [1]. For more information please refer to Apache PLC4X
Configuration
To configure the PLC4X source in DataBridge you need to provide the unique id, the connection details like host, port, and the service path (*), options (*), the driver and the tags. The driver could be any of the drivers supported by the PLC4X. For more information on the configuration please refer Camel PLC4X
* - Optional attributes
Sample Configuration
[ { "uniqueId": "property1", "serverUrl": "localhost", "serverPort": 50201, "driver": "modbus-tcp", "servicePath": "", "options": "", "tags": [ { "name": "value_1", "value": "holding-register:1" } ] } ]
Similarly, you can configure multiple PLC4X inside the configuration file.
Naming Convention
The name of the PLC4X configuration file should be plc4xconsumer.json.
Working Example
The integration example with PLC4X as a data source, Json Jackson and JSONata as a transformer, and AAS as a data sink is on GitHub DataBridge Example.