...
- 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.
FieldName | Type | Reading field | Details | Select | Boolean
---|---|---|---|---|
String | co_ | se0 Select 1 Execute | ||
AsduType | TBC | co_type | Type of ASDU | |
id | co_id = PIVOT ID | |||
String | co_ | idPIVOT 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_cot | See Cause of Transmission | |
Test | Boolean | co_test | Test command (true = test) | |
Negative | Boolean | co_negative | Negative command (true= negative) | |
Pulse | Boolean | co_qu | Pulse command (true= pulse) | |
Value | (See below) | co_value | (See below) | |
Reply | Same 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):
FieldName | Type | Reading field | Details | |
---|---|---|---|---|
AsduType | TBC | co_type | Type of ADSU | |
N.A. | String | co_id | PIVOT 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 | See Cause of Transmissiontype | co_type = "opcua_sps" | "opcua_dps" | "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) | 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
| ) : Select (False = Select, True= Execute) TBC!!!
Examples:
|
Common notes
- With
<PIVOT_ID>
as provided inexchanged_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.
...
PIVOT Type | TypeId of
| BaseDataType of
| Note | ||
---|---|---|---|---|---|
SPSTyp | opcua_sps | Boolean_Id (=1) | |||
DPSTyp | opcua_dps | String_Id (=12) | Enum is shown as string encoded. | ||
BSCTyp | opcua_bsc | TBD | Not supported in current version | String_Id (=12) | |
MVTyp | opcua_mvi | Int32_Id (=6) | In that case, the "mag.f" field is ignored | ||
MVTyp | opcua_mvf | Float_Id (=10) | In that case, the "mag.i" field is ignored | ||
SPCTyp | opcua_spc | Boolean_Id (=1) | Not supported in current version|||
DPCTyp | opcua_dpc | Byte_Id (=2) | Not supported in current version|||
INCTyp | opcua_inc | Int32_Id (=6) | Not supported in current version | ||
APCTyp | opcua_apc | Float_Id (=10) | Not supported in current version | ||
BSCTyp | opcua_bsc | TBD | Not supported in current versionString_Id (=12) |