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.
Difference between revisions of "BaSyx / Documentation / Components / DataBridge / Features / Protocol Integration / OPCUA"
m (→Working Example) |
m (Adds username & password) |
||
| Line 13: | Line 13: | ||
"serverPort": 12686, | "serverPort": 12686, | ||
"pathToService": "milo", | "pathToService": "milo", | ||
| − | "nodeInformation": "ns=2;s=HelloWorld/ScalarTypes/Double" | + | "nodeInformation": "ns=2;s=HelloWorld/ScalarTypes/Double", |
| + | "username": "name", | ||
| + | "password": "secretPassword", | ||
} | } | ||
] | ] | ||
Revision as of 12:10, 2 June 2023
Contents
OPC UA
The OPC UA client can be integrated with DataBridge. The Milo Client component provides access to OPC UA servers using the Eclipse Milo™ implementation.
Configuration
To configure OPC UA client source in DataBridge you need to provide the unique id, and the OPC UA server details like host, port, service path along with the node information as a query parameter. For more information on query parameters OPC UA Client Query Parameters
Sample Configuration
[
{
"uniqueId": "doublescalar",
"serverUrl": "127.0.0.1",
"serverPort": 12686,
"pathToService": "milo",
"nodeInformation": "ns=2;s=HelloWorld/ScalarTypes/Double",
"username": "name",
"password": "secretPassword",
}
]
Disclaimer: Please note that only the query parameter (node) listed i.e. nodeInformation in the sample configuration is supported as of now.
Similarly, you can configure multiple OPC UA client consumers inside the configuration file.
Naming Convention
The name of the OPC UA consumer configuration file should be opcuaconsumer.json.
Working Example
The integration example with timer triggered OPC UA as a data source, with two transformers JSONata and Jackson, and AAS as a data sink is on GitHub DataBridge Example.