Versions Compared

Key

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

...

  • 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 responsibility of the OPC UA client.
  • then activate the command Trigger. This must be executed after the previous write command was sucessfully successfully completed.
BooleanseN.A.id
FieldNameTypeReading fieldDetailsSelect

String

co_

0 Select

1 Execute

AsduTypeTBCco_typeType of ASDU

id

co_id = PIVOT ID


String

co_

PIVOT Id, determined using written NodeId

TBC: Does the OPC client NEED to specify a specific co_oa (originator address), In that case, a variable "Origin" or "Address" may have to be added with data co_oa

Cause

UInt32

co_cotSee Cause of Transmission
TestBooleanco_testTest command (true = test)
NegativeBooleanco_negativeNegative command (true= negative)
PulseBooleanco_quPulse command (true= pulse)
Value(See below)co_value(See below)
ReplySame as Value
(Read-Only)
co_reply

Return value form the south equipment.true:

Trigger

Boolean

co_ts

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 using 4 booleans in parameters):

See Cause of Transmission) : Select (False = Select, True= Execute) TBC!!!

type

co_type = "opcua_sps" | "opcua_dps" |  "opcua_inc" | "opcua_apc" | "opcua_bsc"

Other types not supported in current version.

FieldNameTypeReading fieldDetails
AsduTypeTBCco_typeType of ADSU
N.A.Stringco_idPIVOT Id TBC: Does the OPC client NEED to specify a specific co_oa (originator address), In that case, a variable "Origin" or "Address" may have to be added with data co_oa
Cause

UInt32

co_cot

Value(See below)co_value(See below)
ReplySame as Value
(Read-Only)
co_reply

Return value form the south equipment.

Trigger

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

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.

...

Not supported in current versionNot supported in current versionNot supported in current version
PIVOT Type

TypeId of

exchanged_data.datapoints.pivot_type

BaseDataType of

ns=1;s=<PIVOT_ID>/Value

Note
SPSTypopcua_spsBoolean_Id (=1)
DPSTypopcua_dpsString_Id (=12)

Enum is shown as string encoded.

See CDC double point status (DPSTyp)

BSCTypopcua_bscTBDNot supported in current versionString_Id (=12)
MVTypopcua_mviInt32_Id (=6)In that case, the "mag.f" field is ignored
MVTypopcua_mvfFloat_Id (=10)In that case, the "mag.i" field is ignored
SPCTypopcua_spcBoolean_Id (=1)
DPCTypopcua_dpcByte_Id (=2)
INCTypopcua_incInt32_Id (=6)Not supported in current version
APCTypopcua_apcFloat_Id (=10)Not supported in current version
BSCTypopcua_bscTBDString_Id (=12)