Page History

...

• 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.

...

• There is one Variable for each exposed filed of the PIVOT data:
  • NodeId ns=1;s=<PIVOT_ID>/<FieldName>
  • BrowseName/DisplayName <FieldName>
  • IsOrganizedBy ns=1;s=<PIVOT_ID>

TeleMeasure /TeleSignal

Both TeleMeasure and TeleSignal use exactly the same OPC variables organization. They both represent data received from a south plugin and therefore only expose Read-Only Nodes.

...

TeleControl

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.

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 repsonsibility of the OPC UA client.
• then activate the command Trigger. This must be executed after the previous write command was sucessfully completed.

...

0 Select

1 Execute

...

UInt32

...

Return value form the south equipment.true:

...

Boolean

...

True: Triggers the TC with current values and current timestamp of the variables related to the same PIVOT object.

False: Ignored

Note that OPC UA clients do not need ot reset the Trigger to false between two TRUE writes operations.

TBC: another option is (use a mask in trigger rather than ussing 4 booleans in parameters):

...

0 Select

1 Execute

...

UInt32

...

Return value form the south equipment.

...

UInt8

...

co_se

co_test

co_negative

co_qu

co_ts

...

Writing this node triggers the TC with current values, current timestamp and the command flags depending on the Trigger Value:

• Bit 0 (0x01) : Test
• Bit 1 (0x02) : Negative
• Bit 2 (0x04) : Pulse
• Bit 3 (0x08) : Select (False = Select, True= Execute) TBC!!!

Examples:

• Writing "0" triggers a Select TC with Test, Negative and Pulse set to 0
• Writing "9" (= 8 OR 1) triggers an Execute TC with Test set to 1 and Negative and Pulse set to 0

Common notes

• With <PIVOT_ID> as provided in exchanged_data.datapoints[].pivot_id section configuration.
• All read-only variables have a OpcUa_BadWaitingForInitialData quality (0x80320000) initial value until a valid value is received from FledgePower.
• All non-mandatory values will be set automatically by the server if not received from a south device.
• If a mandatory value is missing, then the whole PIVOT object is not updated.
• As a standard OPC UA server, all functional data are organized under the Root.Objects  node of namespace 0 ( nodeId = i=85).
• All data are stored under the namespace 1. Its URI is configured in protocol "namespaces" parameter.

Value content and metadata

PIVOT timestamp

The ns=1;s=<PIVOT_ID>/Value variable contains the pivot timestamp value (t.FractionOfSecond + t.SecondSinceEpoch) is converted to OPC-UA timestamp (Unit=  number of 100 nanosecond since Jan 1st,1600).

The timestamp is not optional in OPCUA. Thus, in case the timestamp were not provided by south layers, the OPC UA north plugin will set the timestamp to 0.

PIVOT value validity

The ns=1;s=<PIVOT_ID>/Value variable contains the pivot value <Root>.<type>.q.validity field. It is represented as the OPC UA Quality of the variable, using the following conversion:

TeleControl

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.

Common notes

• With <PIVOT_ID> as provided in exchanged_data.datapoints[].pivot_id section configuration.
• All read-only variables have a OpcUa_BadWaitingForInitialData quality (0x80320000) initial value until a valid value is received from FledgePower.
• All non-mandatory values will be set automatically by the server if not received from a south device.
• If a mandatory value is missing, then the whole PIVOT object is not updated.
• As a standard OPC UA server, all functional data are organized under the Root.Objects  node of namespace 0 ( nodeId = i=85).
• All data are stored under the namespace 1. Its URI is configured in protocol "namespaces" parameter.

Value content and metadata

PIVOT timestamp

The ns=1;s=<PIVOT_ID>/Value variable contains the pivot timestamp value (t.FractionOfSecond + t.SecondSinceEpoch) is converted to OPC-UA timestamp (Unit=  number of 100 nanosecond since Jan 1st,1600).

The timestamp is not optional in OPCUA. Thus, in case the timestamp were not provided by south layers, the OPC UA north plugin will set the timestamp to 0.

PIVOT value validity

The ns=1;s=<PIVOT_ID>/Value variable contains the pivot value <Root>.<type>.q.validity field. It is represented as the OPC UA Quality of the variable, using the following conversion:

PIVOT variant value

The base type of the value itself is static and depends on the configuration provide in  "exchanged_data" section.