OPC UA Adapter Sample

In the Project Explorer view, open the sample you just loaded.

if you see red marks on a project folder, wait a moment for the project to load its features.

If the red marks do not resolve themselves after a minute, select the project, right-click, and select Maven>Update Project from the context menu.

Open the src/main/eventflow/packageName folder.

Open the opcua-sample.sbapp file and click the Run button. This opens the SB Test/Debug perspective and starts the module. All the adapters are configured to connect to the OPC UA server at startup.

Wait for the Control operator to issue a status tuple indicating the connection was successful. If a connection problem occurs the console will provide more information.

In the Manual Input view, select the BrowseCmd input stream, and enter a list of OPC nodes to query. Send a tuple with NodeList set to a list containing a single null entry to browse the root node. If connected to the server configured by default, you can use entries such as:

Click Send Data, and observe that the output stream that received the data is the BrowserResult stream. The emitted tuple's Nodes field has one entry for every requested node, listing its metadata and referenced child nodes.

In the Manual Input view, select the ReaderCmd input stream, and enter a list of nodes to query. Using the default server you can query for nodes like:

Click Send Data, and observe that the output stream that received the data is the ReaderResult stream. The tuple Values field contains one entry for every requested node, detailing the node's value and associated metadata.

In the Manual Input view, select the WriterCmd input stream, and enter a list of nodes to update, with the value you wish to set for them. On the default server you could send:

Click Send Data, and observe that the output stream that received the data is the WriterResult stream. The tuple contains the status of the write operation for every requested node.

You may wish to use the Reader adapter again to confirm that the values have been modified on the server.

In the Manual Input view, select the SubCmd input stream, set the Action field to subscribe, and enter a list of tag names to monitor. For example on the default server:

Click Send Data, and observe that the SubStatus port has sent one tuple to indicate that the subscription has been successfully created (and in that tuple, the SubscriptionID assigned by the server to this subscription will be mentioned), and that the SubResult output stream is now emitting periodical tuples containing the updated values for the specified nodes.

You may cancel this subscription by sending a new tuple to the SubCmd input stream with Action set to unsubscribe and setting SubscriptionID to the value given by the status tuple's SubscriptionID entry, or any result tuple's SubscriptionID field.

When done, press F9 or click the Terminate EventFlow Fragment button.