OPC UA: Configuring a Machine Data Interface Correctly

Jason IP2 min read
OPC / OPC UAOther ManufacturerTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

UnderlyingSystem is only an example data source used by the SDK examples. Do not reuse it as the production machine interface. Build a machine-specific data acquisition mechanism and make its data available to the NodeManager.

Separate the Example from the Production Design

The example UnderlyingSystem represents data consumed by the NodeManager; it is not a required OPC UA production component. Its purpose is to demonstrate the boundary between the server node layer and an underlying data source.

Component Evidence-supported role Production decision
UnderlyingSystem Example data source Replace it rather than adopting the example class
NodeManager Uses data represented by the data source Connect it to the machine-specific acquisition mechanism
Machine interface Actual source of machine data Implement a mechanism appropriate to that interface

Connect the Machine Data Path

The available evidence does not identify the machine interface, protocol, data format, or SDK-specific integration API. Keep the implementation generic until those details are known.

  1. Identify how the machine exposes the required data.
  2. Create a mechanism that acquires that data for the OPC UA server.
  3. Provide the acquired data to the NodeManager through the integration points supported by the SDK project.
  4. Verify that the NodeManager receives machine data rather than values generated by the example UnderlyingSystem.

Determine Whether XML Is Required

The evidence does not establish an XML schema, model file, import procedure, or relationship between XML and UnderlyingSystem. Do not assume that copying or modifying an example XML file will create the machine connection. First define the machine interface and the data acquisition path; then consult the SDK documentation to determine whether its node model requires XML or another configuration mechanism.

FAQ

Should I use the example UnderlyingSystem class in production?

No. It is a simple example data source; create your own mechanism for obtaining data from the machine.

How does machine data reach the OPC UA NodeManager?

Acquire the data through a machine-specific interface mechanism and make that data available to the NodeManager using the SDK project's supported integration points.

Do I need XML for UnderlyingSystem or the OPC UA model?

The supplied evidence does not specify an XML requirement or format. Determine the machine data path first, then verify the SDK's model configuration requirements in its documentation.

Back to blog