Connections between the driver and sensors in the model can either be done individually from the sensor itself or globally for all sensors by clicking on the Summary button and choosing specific data points for the respective sensor.

The example model provided with HYPERSIM comes ready with connections between the driver and the model. It can be used as an example to understand how the connections between the model and the driver should be done.

Each point setup provides a connection point to return data to the model. The connection point is created with the name of the point under a folder structure according to the path parameter that has been given by the user, in the driver configuration GUI. Based on the value of the direction parameter for each point setup, connection point direction is determined. If the direction is set to "Client to server" then the icon is blue It is a read operation and the data will be read from the client and returned to the simulation. If the direction of the point setup is set to "Server to client" then the icon is red, it is a write operation. The signal will be written to the client.

In addition to these connection points, each point setup set in the direction "Server to client" will have an additional connection point called Quality control to feed status code to the client. It will have the name of the point setup with the suffix "quality". These connections points are optional, by default they are not enabled. These can be enabled by checking the box "enable quality control" for each point set up in the UI configuration section.

OPC UA Server can be configured to run on external timestamp; for this, the driver provides two connection points to obtain the timestamp via two data points namely "epoch time" and "nanoseconds". By default, this option is not enabled and it can be enabled by checking the "Use external synchronization" box on the general page of the OPC UA Server UI configuration section.

Connection with the OPC UA Server

Connecting using an OPC UA Client

To connect to the OPC UA server running on the simulator using an OPC client, the user has to provide the IP address of the server in the following format:

where xxx.xxx.xxx.xxx is the IP address of the network interface provided in the general configuration section.

Open

If needed, the user can change the TCP port (4840) using the UI general configuration section (see example in the 'Driver configuration' section)

Connecting Using a Classic OPC Client

Even though the server uses the OPC UA protocol, it is possible to use a classic OPC client to connect to it. But in order to achieve this connectivity, an OPC UA Proxy must be deployed on the host computer where the classic OPC client is running.

To do so, you have to install Matrikon's OPC UA Proxy software that comes with a 30-day evaluation license. The full version can be purchased through our sales department. The proxy acts as a 'bridge' between the classic OPC client and the OPC UA server.

To configure:

• Launch the software, click Add New Connection.

• Open

  

  Enter the UA Server URL matching this example: opc.tcp://xxx.xxx.xxx.xxx:YYYY with the right IP address and TCP port. The IP address (xxxx) and TCP port (YYYY) are the network interface and port provided in the general configuration section of the driver.

• Set the security option to None-none, choose a connection name for the server, and then click Done. Some additional options are available when clicking on Logging Options.

You should then see the connection you just created:

• click the connection

• Start the proxy connection by clicking on the play icon.

• Start your OPC client.

Connect to the server by giving the name UAProxy.OPAL_OPC_UA.1.

You can now browse through the folder tree specified in the UI configuration section to add data to be monitored or controlled.