DDT Data Structures
Original instructions
About us
Introduction
If you enable the IEC 61850 server, enable the client, and create one or more report and GOOSE control blocks, Control Expert adds the following DDT data structures to your project:
Module Information
The {Module_name}_MOD_INFO DDT presents information for the module, IED server, and IED client states, as well as the module control status, the names of which are the prefix of the DDT:
Element
Type
Description
MODULE_STATE
{Module}_STATE
global status of the BMENOP0300 modules
SERVER_STATE
{Module}_SERVER_STATE
server diagnostic information
CLIENT_STATE
{Module}_CLIENT_STATE
client diagnostic information
Module Control
The {Module_name}_MOD_CONTROL DDT presents information for module control for dual network redundancy, the name of which is the prefix of the DDT:
Element
Type
Description
DualModuleDiag1
ARRAY[0...8] of UDINT
module diagnostic. Its content is reserved for system usage and is not displayed by default in Control Expert. Its contents is a copy of {Module_name}_MOD_DIAG.
ModDiag1
MOD_DIAG
module diagnostic
ModuleControl2
WORD
module mode control, one bit per functions
SimulateMode2
BOOL
Bit 0: Effect on GOOSE publish
  • 0: normal mode
  • 1: simulation mode
ClearDiag2
BOOL
Bit 1: Clear diagnostic information of IEC 61850
  • 1: clear, take effect on raise edge
1 read only
2 read write
Module Diagnostics
The {Module_name}_MOD_DIAG DDT presents read-only information for module diagnostics, the name of which is the prefix of the DDT. This data is updated by the IEC 61850 server:
Element
Type
Description
HeartBeat
UDINT
the counter of heart beat, increment per PAC cycle
ScanCount
UDINT
the counter of I/O data scan
CurEntryID
ARRAY [0...3] of WORD
current entry ID
TimeStamp
TIME_850_FORMAT
time entry
ScanState
WORD
scan status
  • 0: idle
  • 1: on-going
ModelSig
UDINT
module signature
Module State
The {Module_name}_MODULE_STATE DDT presents diagnostic information for the IEC 61850 module, the name of which is the prefix of the DDT (all read only):
Element
Type
Bit
Description
EthStatus
WORD
–
Ethernet status
Port1Link
BOOL
0
link up/down for Ethernet port 1
Port2Link
BOOL
1
link up/down for Ethernet port 2
Port3Link
BOOL
2
link up/down for Ethernet port 3
EthBkpPortLink
BOOL
3
link up/down for Ethernet backplane port
NetworkStatus
BOOL
6
0: Traffic overload detected (example: broadcast storm). Check your network topology and configuration.
1: No traffic overload detected.
GlobalStatus
BOOL
7
0: One or more services not operating normally.
1: All services operational.
ServiceStatus
WORD
–
one bit for each user-observable feature
RstpService
BOOL
0
0: Service not operating normally.
1: Service operating normally or disabled.
Port502Service
BOOL
1
0: Service not operating normally.
1: Service operating normally or disabled.
SnmpService
BOOL
2
0: Service not operating normally.
1: Service operating normally or disabled.
MainIpAddressStatus
BOOL
3
main IP address status (0 in the case of duplicate IP or no IP assigned)
IedServer
BOOL
6
0: Service not operating normally.
1: Service operating normally or disabled.
IedClient
BOOL
7
0: Service not operating normally.
1: Service operating normally or disabled.
SntpClient
BOOL
8
0: Service not operating normally.
1: Service operating normally or disabled.
FirmwareUpgrade
BOOL
9
0: Service not operating normally.
1: Service operating normally or disabled.
FtpServer
BOOL
10
0: Service not operating normally.
1: Service operating normally or disabled.
LldpService
BOOL
11
LLDP service status
EventLogStatus
BOOL
12
0: Event log service not operating normally.
1: Event log service operating normally or disabled.
LogServerNotReachable
BOOL
13
0: Acknowledgment received from the syslog server.
1: No acknowledgment received from the syslog server.
SNtpServerNotReachable
BOOL
15
0: Service not operating normally.
1: Service operating normally or disabled.
EthPort1Port2Status
BYTE
–
Ethernet port 1 and 2 status
Port 1 function
–
0...1
0: disabled
1: access port
2: mirror port
3: network port
(Reserved)
–
2...3
–
Port 2 function
–
4...5
0: disabled
1: access port
2: mirror port
3: network port
RSTP Role
–
6...7
0: alternate
1: backup
2: designated
3: root
EthPort3BkpStatus
BYTE
–
Ethernet port 3 and backplane port status
Port 3 function
–
0...1
0: disabled
1: access port
2: mirror port
3: network port
RSTP Role
–
2...3
0: alternate
1: backup
2: designated
3: root
Eth Bkp Port function
–
4...5
0: disabled
1: access port
2: mirror port
3: network port
(Reserved)
–
6...7
–
FirmwareVersion
WORD
–
MSB: major revision
LSB: minor revision
ServiceStatus2
WORD
–
One bit for each user-observable feature
Network3MainIpAddressStatus
BOOL
2
Network 2 IP Address Status (0 if duplicate IP address or no IP address assigned)
Reserved1
UDINT
–
reserved
InPackets
UINT
–
number of packets received
InErrors
UINT
–
number of inbound packets that contain detected errors
OutPackets
UINT
–
number of packets sent
OutErrors
UINT
–
number of outbound packets that contain detected errors
ConfSig
UDINT
–
Signature of configuration file
Server State
The {Module_name}_SERVER_STATE DDT presents diagnostic information for the IEC 61850 server in the module, the name of which is the prefix of the DDT:
Element
Type
Description
Active
BOOL
server status:
  • 0 = disabled
  • 1 = enabled
Health
BOOL
server health:
  • 0 = not operational
  • 1 = operational
ProtoEd
BYTE
IEC 61850 protocol edition:
  • 0x10 = 1.0
  • 0x20 = 2.0
ActiveConn
BYTE
number of established server connections
VariableRd
UDINT
count of read variable requests received by the server
VariableRdErr
UDINT
count of rejected MMS read variable requests
VariableWrt
UDINT
count of write variable requests received by the server
VariableWrtErr
UDINT
count of rejected MMS write variable requests
ReportsTx
UDINT
count of information report messages sent by the server
GooseTx
UDINT
count of GOOSE messages transmitted by the server
GooseRx
UDINT
count of GOOSE messages received by the server
GooseErr
UDINT
count of invalid GOOSE messages received by the server
ErrorCode (low word)
WORD
InvalidConf
BOOL
low word:
  • 0x0001: invalid configuration
  • 0x0002: stack init error detected
  • 0x0004: config init error detected
  • 0x0010...0x00F0: BP comm error detected
  • 0x0100: DB binding error detected
StackInitErr
BOOL
ConfInitErr
BOOL
BpCommErr
BOOL
DbBindErr
BOOL
ErrorCode (high word)
WORD
ClockNotSyn
BOOL
high word:
  • 0x1000: clock not synchronized
  • 0x2000: default IP
  • 0x4000: IP not available
DefaultIp
BOOL
IPNotAvailable
BOOL
RptEntity
IED_RPT[x]
report diagnostic information
GooseEntity
IED_GOOSE[x]
report diagnostic information
Client State
The {Module_name}_CLIENT_STATE DDT presents diagnostic information for the IEC 61850 client in the module, the name of which is the prefix of the DDT:
Element
Type
Description
Active
BOOL
client status:
  • 0 = disabled
  • 1 = enabled
Health
BOOL
client health:
  • 0 = not operational
  • 1 = operational
ProtoEd
BYTE
IEC 61850 protocol edition:
  • 0x10 = 1.0
  • 0x20 = 2.0
ActiveConn
BYTE
number of established server connections: 0...16
IEDHealth1
WORD
IED connection status:
  • 0 = disconnected
  • 1 = connected
NOTE: Each bit represents one IED in the same order as the sequence of IEDs in the SCL file.
{IED_HEALTH}
BOOL
Bit-0
{IED_HEALTH}
BOOL
Bit-1
...
BOOL
...
{IED_HEALTH}
BOOL
Bit-15
IEDHealth2
WORD
IED connection status:
  • 0 = disconnected
  • 1 = connected
NOTE: Each bit represents one IED in the same order as the sequence of IEDs in the SCL file.
{IED_HEALTH}
BOOL
Bit-0
{IED_HEALTH}
BOOL
Bit-1
...
BOOL
...
{IED_HEALTH}
BOOL
Bit-15
VariableRd
UDINT
count of read variable requests received by the server
VariableRdErr
UDINT
count of rejected MMS read variable requests
VariableWrt
UDINT
count of write variable requests received by the server
VariableWrtErr
UDINT
count of rejected MMS read variable requests
ReportsRx
UDINT
count of information report messages received by the client
GooseRx
UDINT
count of GOOSE messages received by the client
GooseErr
UDINT
count of invalid GOOSE messages received by the client
ErrorCode (low word)
WORD
InvalidConf
BOOL
low word:
  • 0x0001: invalid configuration
  • 0x0002: stack init error detected
  • 0x0004: config init error detected
  • 0x0010: BP communication detected error
  • 0x0020: data dictionary disabled
  • 0x0100: DB binding error detected
  • 0x1000: Report ID mismatch detected
StackInitErr
BOOL
ConfInitErr
BOOL
BpCommErr
BOOL
DdtRdErr
BOOL
DbBindErr
BOOL
RptidMismatch
BOOL
Error Code (high word)
WORD
ClockNotSyn
BOOL
High word:
  • 0x0001...0x00FF: configuration inconsistent (index of IED in SCL)
  • 0x1000: clock not synchronized
  • 0x2000: default IP address
  • 0x4000: IP not available
DefaultIp
BOOL
IPNotAvailable
BOOL
GooseEntity
IED_GOOSE[x]
report diagnostic information
GOOSE Diagnostics
The {Module_name}_IED_GOOSE DDT presents GOOSE control block diagnostic information for the IEC 61850 module, the name of which is the prefix of the DDT:
Element
Type
Description
Service
BYTE
  • 0 = publish
  • 1 = GOOSE subscribe for server
  • 2 = GOOSE subscribe for client
Status
BOOL
  • true = active
  • false = not active
NdsCom
BOOL
The Need Commission attribute has a value of TRUE if the GoCB requires further configuration when:
  • The attribute DataSet has a value of NULL.
  • The number or size of values being conveyed by the elements in the DatSet referenced data-set exceeds constraint determined by the SCSM or the implementation.
Simulation
BOOL
A value of True indicates Sim messages are received and accepted.
LastStNum
UDINT
the last state number
LastSqNum
UDINT
the last sequence number
LastError
UINT
the last detected error:
  • 1: MAC not consist with configuration.
  • 2: AppID not consist with configuration.
  • 3: GOOSE data set not consist with configuration.
  • 4: initAddr is missing.
  • 5: GOOSE not received after Time to Alive expired.
  • 6: stNum is out of order.
  • 7: sqNum out of order.
  • 8: GOOSE ConfRev not consistent with configuration.
  • 9: Decoding GOOSE data error detected.
  • 10: Other unknown detected errors.
  • 11: NdsCom = True.
  • 12: Go Ref is incorrect.
Reserve
UINT
<reserved>
DDT Overview for Server
The {Module}_{IED name DDT overview for the IEC 61850 server data structure is as follows:
Element
Type
Trigger
Definition
Freshness
BOOL
-
0: data is not fresh
1: data is fresh
When there is no IEC 61850 connection or backplane communication, this element is set to 0 (FALSE).
   -DataModel
          -{LD}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
-
This definition can be viewed in the IEC 61850 Configuration Tool by navigating to IEC61850 Server → Data Model.
          -{LD}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
-
This definition can be viewed in the IEC 61850 Configuration Tool by navigating to IEC61850 Server → Data Model.
... ...
   -DatasetSOE
        -{SOE DS name}
        -{SOE DS name}
{ERT_BUF}
-
It is used to transfer external events to the BMENOP0300 module.
DDT Overview for Client
The {Module}_{IED name DDT overview for the IEC 61850 client data structure is as follows
Element
Type
Trigger
Definition
Freshness
BOOL
-
0: data is not fresh
1: data is fresh
When there is no IEC 61850 connection or backplane communication, this element is set to 0 (FALSE).
ConenctCtrl
BOOL
-
0: Auto connect
1: disconnect
-Data Model
          -{LD}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
-
This definition can be viewed in the IEC 61850 Configuration Tool by navigating to IEC61850 Server → Data Model.
          -{LD}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{DA_Type}
-
This definition can be viewed in the IEC 61850 Configuration Tool by navigating to IEC61850 Server → Data Model.
-PollBlock
Polling control for each IED
    POLL_GRPx
              X= 1...5
{Module}_POLLING_CTRL
-
-ControlBlock
General control
          -{LD}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{CB_Type}
{LD_Type}
    -{LN_Type}
         -{DO_Type
             -{CB_Type}
-
-ReportBlock
Report control
     {report cb name}
{LD_Type}
    -{LN_Type}
      -
{Module}_Report_BRCB}
      -
{Module}_Report_URCB}
......
{LD_Type}
    -{LN_Type}
      -
{Module}_Report_BRCB}
      -
{Module}_Report_URCB}
-
-gooseDiagnostic
Goose control block
{ModuleGooseDiag}
{IED_1}
       {LD_1}
              {GooseName}
                     {a}
                     {b}
{IED_2}
       {LD_1}
              {GooseName}
                     {a}
                     {b}
-
IEDName
LD_Name
GooseDiag
BOOL
BOOL
IEDName
LD_Name
GooseDiag
BOOL
BOOL
Buffered Report Control Block
The data structure of the buffered report {Report_name}_REPORT_BRCB of the client function:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Option
BYTE
-
option: operation selection, whose values include:
  • 1: set RptEna
  • 2: set BufTms
  • 3: set IntgPd
  • 4: set ResvTms
  • 5: set TrgOps
  • 6: set OptFlds
  • 8: set EntryID
  • 9: set RptID
    NOTE: Execute option value 9 once before enabling the report control block in the server to receive report information.
  • 10: set DataSet
    NOTE: For set RptID and set DataSet commands, the source is the SCL file and cannot be set dynamically in PLC memory.
  • 11: set GI
  • 12: set Purge buffer
  • 101: get RptEna
  • 102: get BufTms
  • 103: get IntgPd
  • 104: get ResvTms
  • 105: get TrgOps
  • 106: get OptFlds
  • 108: get EntryID
  • 120: get ConfRev
  • 121: get SgNum
Index
BYTE
-
buffer index number: 1...99
NOTE: If the Index element is set to 0 (false), indexing is not used for this report. In this case, leave the element value at 0.
AutoEna
BYTE
-
How is report enabled?
  • 0 = enable on demand
  • 1 = auto enable
NOTE: Auto-enable is recommended so the report is enabled in case of redundant switchover.
Attribute
DWORD
-
common area for read/write of attribute, depending on the selected option:
  • BufTms DWORD
  • IntgPd DWORD
  • ResvTms DWORD
  • ConfRev DWORD
  • TrgOps low WORD of attribute
    Refer to the BITSTRING topic for the bit detail of trigger option.
  • OptFlds low WORD of attribute
    Refer to the BITSTRING topic for the bit detail of option field.
  • SgNum low WORD of attribute
  • RptEna low WORD (bit 0) of attribute
  • GI low WORD (bit 0) of attribute
  • PurgeBuf low WORD (bit 0) of attribute
Entry_ID
UINT[4]
-
entry ID reported in the last response
NOTE: Supported only by buffered report control blocks (BRCB).
RptStatus
WORD
-
  • low byte: index of report control block (1...99)
  • high byte:
    • bit 0 = ConfRev change
    • bit 1 = buffer overflow
Status
WORD
-
Status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6..7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code
AddCause Detected Error Codes
The following is a list of report and control object detected AddCause error codes:
Code
Short Description
Explanation of IEC 61850-7-2
1
Not-supported
Not supported.
2
Blocked-by-switching-hierarchy
Not successful, because one of the downstream Loc switches like in CSWI has the value TRUE.
3
Select-failed
Canceled due to an unsuccessful selection (select service).
4
Invalid-position
Control action is aborted due to invalid switch position (Pos in XCBR or XSWI).
5
Position-reached
Switch is already in the intended position (Pos in XCBR or XSWI).
6
Parameter-change-in-execution
Control action is blocked due to running parameter change.
7
Step-limit
Control action is blocked because tap changer has reached the limit
EndPosR or EndPosL in YLTC).
8
Blocked-by-Mode
Control action is blocked because the LN (CSWI or XCBR/XSWI)is in a mode (Mod) which doesn’t allow any switching.
9
Blocked-by-process
Control action is blocked due to some external event at process level that prevents a successful operation for example blocking indication (EEHealth in XCBR or XSWI).
10
Blocked-by-interlocking
Control action is blocked due to interlocking of switching devices (in CILO attribute EnaOpn.stVal= FALSE or EnaCls.stVal= FALSE).
11
Blocked-by-synchrocheck
Control action with synchrocheck is aborted due to exceed of time limit and missing synchronism condition.
12
Command-already-in-execution
Control select or cancel service is rejected because control action is already running.
13
Blocked-by-health
Control action is blocked due to some internal event that prevents a successful operation (Health).
14
1-of-n-control
Control action is blocked because another control action in a domain (for example substation) is already running (in any XCBR or XSWI of that domain the DPC.stSeld= TRUE).
15
Abortion-by-cancel
Control action is aborted due to cancel service.
16
Time-limit-over
Control action is terminated due to exceed of some time limit.
17
Abortion-by-trip
Control action is aborted due to a trip (PTRC with ACT.general = TRUE).
18
Object-not-selected
Control action is rejected because control object was not selected.
19
Object-already-selected
Select action is not executed because the addressed object is already selected.
20
No-access-authority
Control action is blocked due to lack of access authority.
21
Ended-with-overshoot
Control action executed but the end position has overshoot.
22
Abortion-due-to-deviation
Control action is aborted due to deviation between the command value and the measured value.
23
Abortion-by-communication-loss
Control action is aborted due to the loss of connection with the client that issued the control.
24
Blocked-by-command
Control action is blocked due to the data attribute CmdBlk.stVal is TRUE.
25
None
Command not successful due to Unknown causes.
26
Inconsistent-parameters
The parameters between successive control services are not consistent for example the ctlNum of Select and Operate service are different.
27
Locked-by-other-client
Another client has already reserved the object.
Detected Error Codes
The following is a list of detected error codes for operations (polling, report control, GOOSE control and general control):
Function
Code
Short Description
Explanation of IEC 61850-7-2
Control point
1...27
AddCause
Refer to AddCause detected errors.
61
Disconnected
Offline with remote IED
63
Input parameter error detected
Input parameter in data block is incorrect. For example, a CtlVal is out of range.
Polling
61
Disconnected
Offline with remote IED
62
Polling did not succeed
One or more DOs or DAs are missing in remote IED. Polling will continue if this error is detected.
63
Input parameter error detected
Input parameter in data block is incorrect.
Report Control
60
Auto-enable did not succeed
A report was not enabled after going online. Check the AutoEna element setting of the control block.
61
Disconnected
Offline with remote IED
63
Input parameter error detected
Input parameter in data block is incorrect.
GOOSE Control
0
GOOSE disabled
GOOSE control block is disabled
1
GOOSE enabled
GOOSE control block is enabled
61
Disconnected
Offline with remote IED
Unbuffered Report Control Block
The data structure of the unbuffered report {Report_name}_REPORT_URCB of the client function:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Option
BYTE
-
option: operation selection, whose values include:
  • 1: set RptEna
  • 2: set BufTms
  • 3: set IntgPd
  • 5: set TrgOps
  • 6: set OptFlds
  • 7: set ResvUrcb
  • 9: set RptID
  • 10: set DataSet
    NOTE: For set RptID and set DataSet commands, the source is the SCL file and cannot be set dynamically in PLC memory.
  • 11: set GI
  • 101: get RptEna
  • 102: get BufTms
  • 103: get IntgPd
  • 105: get TrgOps
  • 106: get OptFlds
  • 107: get ResvUrcb
  • 111: get GI
  • 120: get ConfRev
  • 121: get SgNum
Index
BYTE
-
buffer index number: 1...99
NOTE: If the Index element is set to 0 (false), indexing is not used for this report. In this case, leave the element value at 0.
AutoEna
BYTE
-
How is report enabled?
  • 0 = enable on demand
  • 1 = auto enable
NOTE: Auto-enable is recommended so the report is enabled in case of redundant switchover.
Attribute
DWORD
-
common area for read/write of attribute, depending on the selected option:
  • BufTms DWORD
  • IntgPd DWORD
  • ConfRev DWORD
  • GI low WORD of attribute
  • TrgOps low WORD of attribute
    Refer to the BITSTRING topic for the bit detail of trigger option.
  • OptFlds low WORD of attribute
    Refer to the BITSTRING topic for the bit detail of option field.
  • SgNum low WORD of attribute
  • RptEna low WORD (bit 0) of attribute
  • UrcbResv low WORD (bit 0) of attribute
RptStatus
UINT
-
  • low byte: index of report control block (1...99)
  • high byte: bit 0 = ConfRev change
Status
STATUS
-
Status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6..7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code
GOOSE Control Block
The data structure of the {Module_name}_GOOSE_CB DDT:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Option
BYTE
-
option: operation selection:
  • 0 = GOOSE disable
  • 1 = GOOSE enable
  • 2 = Get GoCB
Status
WORD
-
status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6..7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code
Polling Control Block
The data structure of the {Module_name}_POLLING_CTRL DDT:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: eeffective on change
Option
BYTE
-
Not displayed.
Status
WORD
-
status of command execution:
  • Busy: command is executing
  • OK: command is successful
  • Unsuccessful: one of the following events occurred:
    • the client received a negative response.
    • a timeout occurred before the client received a response.
NOTE: If a polling command detects an error for a DO, the Status element for that DO displays a detected error code, and the polling process continues for the next DO.
OPER Control Objects
The OPER control object presents alternative structures, depending on the data type: BOOLEAN, INT8, INT32, ENUM, or ANA. An example of each DDT structure follows for the OPER control object:
The data structure of the {Module_name}_CO_OPER_BOOL control object DDT:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Check
BYTE
-
  • bit 0...1: operation type:
    • 0 = operate
    • 1 = select
    • 2 = cancel
    • 3 = auto (select & operate)
  • bit 2...4 = reserved
  • bit 5: synchrocheck: whether to perform synchrocheck
  • Bit 6: synchrocheck: whether to check for interlocking condition
  • Bit 7: test
CtVal
BYTE
-
bit 0: ctlVal; value to control
Resv
BYTE
-
reserved for alignment
Status
WORD
-
Status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6..7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code
The data structure of the {Module_name}_CO_OPER_INT8 control object DDT:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Check
BYTE
-
  • bit 0...1: operation type:
    • 0 = operate
    • 1 = select
    • 2 = cancel
    • 3 = auto (select & operate)
  • bit 2...4 = reserved
  • bit 5: synchrocheck: whether to perform synchrocheck
  • Bit 6: synchrocheck: whether to check for interlocking condition
  • Bit 7: test
CtVal
INT
-
value to control
Resv
BYTE
-
reserved for alignment
Status
WORD
-
status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6...7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code
The data structure of the {Module_name}_CO_OPER_INT32 control object DDT:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Check
BYTE
-
  • bit 0...1: operation type:
    • 0 = operate
    • 1 = select
    • 2 = cancel
    • 3 = auto (select & operate)
  • bit 2...4 = reserved
  • bit 5: synchrocheck: whether to perform synchrocheck
  • Bit 6: synchrocheck: whether to check for interlocking condition
  • Bit 7: test
CtVal
DINT
-
value to control
Status
WORD
-
status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6...7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code
The data structure of the {Module_name}_CO_OPER_FLOAT and {Module_name}_CO_OPER_FLOAT control object DDTs:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Check
BYTE
–
  • bit 0...1: operation type:
    • 0 = operate
    • 1 = select
    • 2 = cancel
    • 3 = auto (select & operate)
  • bit 2...4 = reserved
  • bit 5: synchrocheck: whether to perform synchrocheck
  • Bit 6: synchrocheck: whether to check for interlocking condition
  • Bit 7: test
CtlVal_i
UDINT
–
value to control int32 point
CtlVal_f
REAL
–
value to control float point
Status
STATUS
–
status of command execution
The data structure of the {Module_name}_CO_OPER_ENUM control object DDT:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Check
BYTE
-
  • bit 0...1: operation type:
    • 0 = operate
    • 1 = select
    • 2 = cancel
    • 3 = auto (select & operate)
  • bit 2...4 = reserved
  • bit 5: synchrocheck: whether to perform synchrocheck
  • Bit 6: synchrocheck: whether to check for interlocking condition
  • Bit 7: test
CtVal
DINT
-
value to control
Status
WORD
-
status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6...7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code
The data structure of the {Module_name}_CO_OPER_ANA control object DDT:
Element
Type
Trigger
Definition
Cmd
BYTE
Dchg
trigger: effective on change
Check
BYTE
-
  • bit 0...1: operation type:
    • 0 = operate
    • 1 = select
    • 2 = cancel
    • 3 = auto (select & operate)
  • bit 2...4 = reserved
  • bit 5: synchrocheck: whether to perform synchrocheck
  • Bit 6: synchrocheck: whether to check for interlocking condition
  • Bit 7: test
CtVal_i
DINT
-
value to control
CtVal_f
REAL
-
value to control
Status
WORD
-
status of command execution:
  • low byte: same as command trigger
  • high byte:
    • bits 6...7: 1 = OK; 2 = error detected
    • bits 0...5: detected error code