Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

FieldNameTypeReading fieldDefault valueDetails
Cause

UInt32

(Read-Only)

do_cotMandatorySee Cause of Transmission
ConfirmationBoolean

(Read-Only)

do_confirmationfalse
SourceString

(Read-Only)

do_source"process"

"process" | "substituted"

ComingFromString

(Read-Only)

do_comingfromMandatoryAny protocol name ("iec104" ,"opcua", ...)
TmOrgString

(Read-Only)

do_ts_org"genuine" "genuine" |  "substituted"
TmValidityString

(Read-Only)

do_ts_validity"good"

Validity of the Timestamp of Value

"good" | "invalid" | "reserved" | "questionable"

DetailQualityUInt32

(Read-Only)

do_quality0

OR-Mask of following values:

0x0001 = badReference 
0x0002 = failure
0x0004 = inconsistent
0x0008 = innaccurate
0x0010 = oldData
0x0020 = oscillatory
0x0040 = outOfRange
0x0080 = overflow
0x1000 = test
0x2000 = operator blocked

TimeQualityUInt32

(Read-Only)

do_ts_quality0

OR-Mask of following values:

0x01 = clockFailure
0x02 = clockNotSynch
0x04 = leapSecondKnown

SecondSinceEpochUInt64

(Read-Only)

do_ts0Number of seconds since Linux Epoch
Value(See below)

(Read-Only)

do_value

do_value_quality

Mandatory(See below)

...

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.
co_reply
OpcUa node ( ns=1;s=<PIVOT_ID>/...)TypeReading fieldDetails

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
Same as Value
(Read-Only)
Booleanro_reply / ro_id

Return value

form

from the south

equipment.

co_test

co_negative

co_qu

service

Trigger

UInt8

Quality:

  • reset to OpcUa_BadRefreshInProgress when the Trigger variable is written.
  • set to OPC_UA_GOOD when the acknowledgement is received. (The "Reply" field is updated using the "opcua_reply" reading (See Filter plugin OPCUA to Pivot).

Value :

  • True: The command has been acknowledged (ro_reply=1)
  • False : The command has not been acknowledged (ro_reply=0 or any other value)

Note that there is no timeout handled in the plugin itself. If the remote equipment never acknowledges the request, Reply may never get OPC_UA_GOOD quality.

Trigger

UInt8

co_test

co_se



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 set <=> co_test=1)
  • Bit 1 (0x02) : Negative (bit set <=> co_negative=1)
  • Bit 2 (0x04) : Pulse

    the Trigger Value:

    • Bit 0 (0x01) : Test (bit set <=> co_
    qu
    • test=1)
    • Bit
    3
    • 1 (
    0x08
    • 0x02) : Select (bit set <=>co_se =1).
          Note : co_se=
    1
    • 0 is "Execute" and co_se=
    0
    • 1 is "Select"

    Examples:

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

    Timestamp

    co_ts

    co_ts = timestamp (Number of seconds since Linux Epoch). The value is defined by local time when Trigger is written.

    PIVOT variant value

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

    ...