Data sources



Like every other Peakboard datasource, the OPC UA datasource needs a name (1).

A [client certificate] (2) is necessary. This certificate is stored as a whole (public + private key) on client side. Afterwards the public key part has to be transferred to the server and stored as a trusted certificate ( only exception: the “none:none:?” endpoint is used )



Create a new certificate

Insert the URL to the OPC UA Server (3). Should look like ( *opc.tcp://.:[/]* ) The server URL can be scripted using the [{ } button].


This script will only be executed once, when connecting to the server on startup!

Load the endpoints of the server using the [refresh button] on the right of the endpoint selection (4). When a certificate popup is shown, accept the server certificate. Afterwards select the endpoint of your choice. Endpoints differ by their encryption and signing levels and algorithms.

If desired, use an authentication method (username, certificate) (5). The OPC UA authentication is used to authenticate the OPC UA user against the server.


Client and server certificate are used to authenticate the client and the server against each other and thus differ from the user authentication.

[Connect] to the server (6). If the connection works, all inserted information is valid.

If an OPC UA connection is already stored (personal/hub/visualization), it can be used with this button.


Certificates will still have to be created and accepted (to accept the server certificate reload and switch the endpoint).

OPC UA Data Handling


Select the communication type of your datasource

[Edit Subscription specific settings] (2). Should only be done, if you know what you are doing.

Choose a Message Type (3):

Manage your subscriptions (4).


The “Title” of a subscribed node will be used, to access this node from within the Peakboard visualization.


The browse dialog will show the tree of nodes stored on the connected OPC UA server. Selecting a node will add a new subscription deselecting will remove the matching subscription.


The Title, Namespace and Identifier of a node can be edited. Namespace and Identifier can be scripted. This script will be executed only once, when subscribing to the OPC UA server on startup.

If a connection to the server is possible, the [Fetch Node Info] button can be used, to read additional node information (node class, data type, …) from the server.

Node classes:

Enable the listener to check if all subscriptions are defined properly. The listener works the same as the data source in the visualization later on.

Be enlightened!

Do you need more support?

Peakboard Youtube icon Visit our YouTube channel

Our numerous videos for beginners and advanced users explain exactly how to design your dashboard.

Peakboard Templates icon Visit the Peakboard Templates

Download our templates for various use cases for free.

Peakboard icon Visit

Find out all about Peakboard and browse our different use cases and success stories.