...
- Endpoint URL
- Server certificate (It is the responsibility of the client to ensure iopcua_dpst that it is connecting to the expected server)
- User login/password, if applicable.
...
The TeleControls represent commands received from an OPC UA client -connected to the North plugin- that must be sent to a south service. Therefore, they expose Read/Write variables that will be written by a client, except for the feedback of operation, which is Read-Only (Variable Reply
).
As a single PIVOT TC contains the information provided in several OPC variables, the following procedure has been defined to ensure atomicity of the operation. An OPC UA client must:
- first write all relevant parameters in the TC variables. This can be done in a single OPC UA 'write' operation, The plugin will not check that all fields have been updated. This is under the responsibility of the OPC UA client.
- then activate the command
Trigger
. This must be executed after the previous write command was successfully completed.
OpcUa node ( ns=1;s= <PIVOT_ID> / ...) | Type | Reading field | Details |
---|---|---|---|
String | co_id | co_id = PIVOT ID | |
String | co_type | co_type = "opcua_inc" | "opcua_apc" | "opcua_bsc" Other types not supported in current version. | |
Value | (See below) | co_value | (See below) |
Reply |
Value
(Read-Only)
Boolean | ro_reply / ro_id |
Return value |
from the south |
service |
Trigger
UInt8
Quality:
Value :
Note that there is no timeout handled in the plugin itself. If the remote equipment never acknowledges the request, | ||
Trigger | UInt8 | co_test |
co_test
co_negative
co_quco_se | Writing this node triggers the TC with current values, current timestamp and the command flags depending on |
Trigger
Value:the
|
|
|
|
|
|
Examples:
|
|
|
|
| |||
Timestamp | co_ts | co_ts = timestamp (Number of seconds since Linux Epoch). The value is defined by local time when |
PIVOT variant value
The base type of the value itself is static and depends on the configuration provide in "exchanged_data
" section.
...