Details of the IEC 61850 client
"Quality" and "Time" related Information
The attributes "Quality" (q) and "Time" (t) are available for the following Common Data Classes (CDCs). Please note that the information "Quality" and "Time" is not available for all attributes, e.g. the attribute "instMag" of the class "MV" only provides the information "Quality" and not "Time".
| CDC | Data attribute q applies to | Data attribute t applies to |
|---|---|---|
| SPS | stVal | |
| DPS | stVal | |
| INS | stVal | |
| ENS | stVal | |
| ACT | general, phsA, phsB, phsC, neut | |
| ACD | general, dirGeneral, phsA, dirPhsA, phsB, dirPhsB, phsC,dirPhsC, neut, dirNeut | |
| BCR | actVal, frVal | actVal |
| HST | hstVal | |
| VSS | stVal | |
| MV | instMag, mag, range | mag, range |
| CMV | instCVal, cVal, range | cVal, range |
| SAV | instMag | |
| HMV | Har | |
| HWYE | phsAHar, phsBHar, phsCHar, neutHar, netHar, resHar | |
| HDEL | phsABHar, phsBCHar, phsCAHar | |
| SPC | stVal | |
| DPC | stVal | |
| INC | stVal | |
| ENC | stVal | |
| BSC | valWTr | |
| ISC | valWTr | |
| APC | mxVal | |
| BAC | mxVal | |
| SEC | - | cnt |
Quality type definition for bits (0-12)
| Attribute name | Attribute type | Value/Value range | M/O/C | ||
|---|---|---|---|---|---|
| PACKED LIST | |||||
| validity | CODED ENUM | good | invalid | reserved | questionable | M | ||
| detailQual | PACKED LIST | M | |||
| overflow | BOOLEAN | DEFAULT FALSE | M | ||
| outOfRange | BOOLEAN | DEFAULT FALSE | M | ||
| badReference | BOOLEAN | DEFAULT FALSE | M | ||
| oscillatory | BOOLEAN | DEFAULT FALSE | M | ||
| failure | BOOLEAN | DEFAULT FALSE | M | ||
| oldData | BOOLEAN | DEFAULT FALSE | M | ||
| inconsistent | BOOLEAN | DEFAULT FALSE | M | ||
| inaccurate | BOOLEAN | DEFAULT FALSE | M | ||
| source | CODED ENUM |
process | substituted DEFAULT process |
M | ||
| test | BOOLEAN | DEFAULT FALSE | M | ||
| operatorBlocked | BOOLEAN | DEFAULT FALSE | M | ||
IEC 61850 Client Errors
These codes are protocol-specific and defined by the IEC standard.
The values of the column "Short description" are written to the log as part of the respective log message.
The error codes are generated by the IEC 61850 client's protocol stack as a response to any ACSI service requests. They may originate in a request to the stack or in a callback. If the error code is received in a callback, it is a response from the server.
| Enumerated value | Numerical value | Short description | Explanation / possible solution |
|---|---|---|---|
| Client_SUCCESS | 0 | Success | The service request has been completed successfully. |
| Client_ERR_NULL_SERVER | 1 | NULL Server |
There is no server configured for the request sent to the driver. Should not happen during normal operation, may happen when configuring a new connection. Most common reasons in this case:
|
| Client_ERR_NOT_CONNECTED | 2 | Not Connected |
The MMS connection to the server exists, but the status of the connection is down. This happens if the server is disconnected for any reason. |
| Client_ERR_NO_CONNECTION | 3 | No Connection |
The server did not accept the connection request, the MMS connection could not be established. Reason might be incorrect security settings. |
| Client_ERR_FLOW_CONTROLLED | 4 | Flow Controlled |
The client sent more service requests to the server than this server can handle.
|
| Client_ERR_MAX_SERVICES_EXCEEDED | 5 | Max Services Exceeded |
More service requests passed to the communication stack of the client than this stack can handle.
|
| Client_ERR_NO_READ_DATA | 6 | No Read data |
A read request was issued containing no data to read. This may be transient.
|
| Client_ERR_MEMORY | 7 | Memory |
The client's communication stack needs more memory than available.
|
| Client_ERR_ENCODING | 8 | Encoding |
An incorrect data format was passed to the client's communication stack. This may be transient.
|
| Client_ERR_BAD_TRANSACTION | 9 | Bad Transaction |
A malformed request has been sent to the client's communication. This may be transient.
|
| Client_ERR_NO_TRANSACTIONS | 10 | No Transactions |
A request sent to the communication stack failed. This may be transient.
|
| Client_ERR_CONNECTION_CLOSED | 11 | Connection Closed |
Returned by all requests remaining to be processed after the connection has been closed. Happens if the connection is lost. Please note that this error may be returned several times, depending on the number of requests in progress when the connection was lost. |
| Client_ERR_TIMED_OUT | 12 | Timed Out | The service request took longer than the timeout configured for this type of service. |
| Client_ERR_CONNECTION_STATE | 13 | Connection State | The connection state is incorrect for the type of service requested. Please see also Client_ERR_NOT_CONNECTED |
| Client_ERR_APPLICATION | 14 | Application Error |
Any error not specified otherwise. This may be transient.
|
| Client_ERR_PARAMETERS | 15 | Bad Parameters |
The parameters of the request passed to the communication stack are invalid. This may be transient.
|
| Client_ERR_CONFIRMED_ERROR | 16 | Confirmed Error |
Error on confirmed request reported by the server. This means that the server confirmed the request, i.e. the request sent to the server is valid, but upon processing the request the server encountered an unspecified error. |
| Client_ERR_REJECT | 17 | Rejected |
The server rejected a request.
|
| Client_ERR_NO_AUTHENTICATION | 18 | No Authentication | Authentication failure in case of secure connection, e.g. if the security parameters are incorrect. |
| Client_ERR_CONCLUDE_SVC_OUTSTANDING | 19 | Conclude with services outstanding |
The connection was closed while service requests were still pending. This happens if the client closes or loses the connection while requests are still being processed. |
| Client_ERR_CONCLUDE_OTHER | 20 | Conclude Other | Any other error on closing a connection. |
WinCC OA IEC 61850 Error Codes
| Error codes | Description |
|---|---|
| 100 | Success |
| 101 | NULL Server |
| 102 | Not Connected |
| 103 | No Connection |
| 104 | Flow controlled |
| 105 | Max Services Exceeded |
| 106 | No Read data |
| 107 | Memory |
| 108 | Encoding |
| 109 | Bad Transaction |
| 110 | No Transaction |
| 111 | Connection Closed |
| 112 | Timed Out |
| 113 | Connection State |
| 114 | Application Error |
| 115 | Bad Parameters |
| 116 | Confirmed Error |
| 117 | Reject |
| 118 | No Authentication |
| 119 | Conclude with services outstanding |
| 200 | object-invalidated |
| 201 | hardware-fault |
| 202 | temporarily-unavailable |
| 203 | object-access-denied |
| 204 | object-undefined |
| 205 | invalid-address |
| 206 | type-unsupported |
| 207 | type-inconsistent |
| 208 | object-attribute-inconsistent |
| 209 | object-access-unsupported |
| 210 | object-non-existent |
| 211 | object-value-invalid |
| 212 | Unknown |
RCB States
| State | Description |
|---|---|
| 0 |
Not active Target device online, RCB not enabled/reserved |
| 1 |
Reserved Target device online, RCB reserved |
| 2 |
Active Target device online, RCB enabled and active |
| 3 |
Enable failed Manual enable failed, RCB in use |
| 4 |
Enable failed Automatic enable exhausted maximum number of retries (refer to reportEnaMaxRetry), RCB in use |
| 5 |
Not connected Target device not connected |
| 6 |
Initializing State on first enable or first reserve |
| 7 |
Reserving Try reserving, in case of BRCB not supporting resvTms the availability is checked |
| 8 |
Enabling Try enabling the RCB |
| 9 |
Enable retry Indicate retry for enabling the RCB |
| 10 |
Manual enable failed Manual enable failed (error on writing attribute) |
| 11 |
Auto enable failed Automatic enable failed (error on writing attribute) |
| 12 |
Initialized RCB has been inizialized from file |
| 13 |
Initialization failed Initializing RCB failed |
| 14 |
Checking attributes Checking RCB attributes prior to enabling |
| 15 |
Data set mismatch Indicates a mismatch in data set configuration in case the data set attribute is not writeable. |
| 16 |
Attribute mismatch Indicates a mismatch in the RCB attribute setting of any non-writable RCB attribute. |
| 17 |
Init ready RCB attribute settings received from the device |
| 18 |
Init error Reading RCB attributes from device failed |
| 19 |
RPT_PURGE_ERROR Sending purge buffer failed |
| 20 |
RPT_PURGING_ON_CONF_CHANGE Purging buffer in case a BRCB is enabled with a new dataset |
| 21 |
RPT_REQUEST_CONFIG Sending RCB attribute write requests to the device |
| 22 |
RPT_WRITING_CONFIG Prior to enabling, transitions to enabling if all write requests were successful |
| 23 |
RPT_REQUEST_ENABLE Set when all checks have been passed, RCB is ready to be enabled |
| 24 |
RPT_DYN_DATSET_RETRY Waiting for dynamic dataset to be written (UI displays RPT_ENABLE_RETRY) |
| 25 |
RPT_DISABLING Waiting for confirmation from device that RCB has been disabled |
| 26 |
RPT_RELEASING Waiting for confirmation from device that RCB has been released |
RCB Response Codes
| Response Code | Description |
|---|---|
| 0 | Success |
| 1 | object invalid |
| 2 | hardware fault |
| 3 | temporarily unavailable |
| 4 | object access denied |
| 5 | object undefined |
| 6 | invalid address |
| 7 | type not supported |
| 8 | type inconsistent |
| 9 | object attribute inconstant |
| 10 | object access unsupported |
| 11 | object not existent |
| 12 | object value invalid |
| 13 | NULL server |
| 14 | not connected |
| 15 | No connection |
| 16 | flow controlled |
| 17 | max. services exceeded |
| 18 | no read data |
| 19 | memory |
| 20 | encoding |
| 21 | bad transaction |
| 22 | no transaction |
| 23 | connection closed |
| 24 | time out |
| 25 | connection state |
| 26 | application error |
| 27 | bad parameters |
| 28 | confirmed error |
| 29 | reject |
| 30 | no authentication |
| 31 | conclude with services outstanding |
File Transfer Response Code
The values of the column "Short description" are written to the log as part of the respective log message.
The numerical values are written to the internal DPE _IEC61850_IED.State.FileTransferResponseCode.
They are written by the IEC 61850 client's communication stack as a response to any file service request. They may originate in a request to the communication stack or, as a response from the server, in the callback to such request.
The entries marked "Currently unused" are for the future implementation of an RPC or any other extended interface. These values are currently not set.
| Enumerated value | Numerical value | Short description | Explanation / possible solution |
|---|---|---|---|
| FILE_DIRECTORY_SUCCESS | 0 | Success | Directory on server successfully read, file list correctly received |
| FILE_DOWNLOAD_SUCCESS | 51 | File Download Success | File successfully downloaded |
| FILE_LIST_SRV_COUNT_NOT_MATCH | 52 | File List Srv Count Not Match |
The file list in the message received from server (in an answer to a directory read request) is inconsistent. Server issue, may be transient. |
| FILE_LIST_SRV_NO_ELEMENTS | 53 | File List Srv No Elements |
The file list read from server does not contain any elements. Server issue, may be transient |
| FILE_SRV_COULD_NOT_OPEN | 54 | File Srv Could Not Open |
The requested file could not be opened for reading on server side. The server sent a not further specified error on trying to open a file. Most common reasons are:
|
| FILE_CLI_PATH_NOT_FOUND | 55 | File Client Path Not Found |
No target directory has been set on client side. The default is: <project directory>/data/IEC61850/DR/
|
| FILE_SERVER_INACTIVE | 56 | File Server Inactive |
No connection to server.
|
| FILE_SRV_READ_DIR_ERROR | 57 | File List Srv Read Error |
The file directory on the server could not be read. The server sent an unspecified error on trying to read the file list. Either a server issue or an incorrect path (not existing path) has been requested. |
| FILE_QUEUE_OVERFLOW | 58 | File Queue Overflow |
More files have been requested than the driver’s read request queue limit allows. Unlikely error since the default for this limit currently is 50,000. This limit can be changed by the config file entry [iec61850] readRequestQueueLimit. |
| FILE_LIST_RPC_EMPTY | 59 | File List RPC Empty | Currently unused |
| FILE_LIST_RPC_TOO_LONG | 60 | File List RPC Too Lon | Currently unused |
| FILE_LIST_RPC_MISSING | 61 | File List RPC Missing | Currently unused |
| FILE_READ_DIR_NOT_SENT | 62 | File Read Directory Not Sent |
Read directory request could not be sent. Unspecified client-side issue. If the error is not transient, i.e. if it happens repeatedly, please contact ETM support. |
| FILE_CLI_COULD_NOT_OPEN | 63 | File Client File Not Open |
File could not be opened for writing on client side. Either a non-existing target directory (destination path at _IEC61850_IED.FileTransfer.DestinationPath) has been defined, or the driver does not have the necessary permissions to write to the specified directory. |
| FILE_OPEN_NOT_SENT | 64 | File Open Not Sent |
File open request could not be sent. Most common reasons are:
|
| FILE_ERR_IMPLEMENTATION | 65 | File Error Implementation |
WinCC OA implementation error. If the error is not transient, i.e. if it happens repeatedly, please contact ETM support. |
| FILE_SERVER_BUSY | 66 | File Server Busy |
The file close request could not be sent or was not confirmed by the server, further requests may be blocked for some time. If a file remains open on the server, some file services requests may be blocked. The server will close the file automatically after the configured timeout. The length of this timeout is a configuration issue of the server. This timeout cannot be read, so this state cannot be reset. The only solution is to try whatever request is required again until it works. |
| FILE_LIST_TRUNCATED | 67 | File List Truncated |
The file list received from the server is incomplete. This error may be transient. If it happens repeatedly, it is a server issue which needs to be resolved on server side. |
| FILE_READ_DIR_IN_PROGRESS | 100 | File Read Directory In Progress | A read directory request is in progress, no other file services requests are allowed. |
| FILE_DOWNLOAD_IN_PROGRESS | 101 | File Download In Progress | A download file request is in progress, a read directory request is not allowed, download file requests will be queued by the driver. |
Debug Flags
-report ALL
Provides information on configuration and status for
- all created devices
- every enabled RCB
Inactive RCBs are displayed as "disabled…"
"Enabled" refers to the Engineering Tool's configuration settings and not to the activation state of the RCB on the device.
WCCOAiec618501:<<<<<<<<<< IEC 61850 (num <driver number>) Information >>>>>>>>>>
WCCOAiec618501:---------------------------------------------------
WCCOAiec618501:Report for device <OA device name> (IP:<IP>:<port>)
WCCOAiec618501:Connection state : <state>
WCCOAiec618501:Browse state : <state>
WCCOAiec618501: Configuration
WCCOAiec618501: * Device active : <0/1>
WCCOAiec618501: * Connect passive : <0/1>
WCCOAiec618501: * Read complete buffer : <0/1>
WCCOAiec618501: * Authentication : <0/1>
WCCOAiec618501: * Enable RCB configuration : <0/1>
WCCOAiec618501:Number of Report Control Blocks: <number of configured RCBs>
WCCOAiec618501:-- RCB <RCB name>
WCCOAiec618501: State : <Driver internal state>
WCCOAiec618501: State at device: <Actual state at device>
WCCOAiec618501: Response code : <Response code>
WCCOAiec618501: Configuration
WCCOAiec618501: * ReportID : <Report ID>
WCCOAiec618501: * Buffered : <0/1>
WCCOAiec618501: * Indexed : <0/1>
WCCOAiec618501: * Max enable : <Maximum number of instances>
WCCOAiec618501: * Reserve : <0/1>
WCCOAiec618501: * Enable : <0/1>
WCCOAiec618501: Trigger options
WCCOAiec618501: + <Trigger option>: <0/1>
WCCOAiec618501: + Integrity period: <Integrity period>
WCCOAiec618501: + Buffer time : <Buffer time>
WCCOAiec618501: Optional fields
WCCOAiec618501: ~ <Optional field> : <0/1>
WCCOAiec618501: Dataset name : <Dataset name>
WCCOAiec618501: Is dynamic : <Yes|No>
WCCOAiec618501: Is persistent: <Yes|No> (only shown for dynamic datasets)
WCCOAiec618501: --------------
WCCOAiec618501:-- RCB <RCB name>
WCCOAiec618501: Disabled...
WCCOAiec618501: --------------
WCCOAiec618501:------------------ End IEC device -----------------
WCCOAiec618501:<<<<<<<<<<<<<<<<<< End IEC 61850 >>>>>>>>>>>>>>>>>>-report ALL -dbg DATASET
If -report ALL is used with option -dbg DATASET, only detailed information on datasets is provided. In addition to the information provided by -report ALL, a list of dataset elements is given for every enabled RCB.
WCCOAiec618501:<<<<<<<<<< IEC 61850 (num <driver number>) Information >>>>>>>>>>
WCCOAiec618501:-- Dataset information; printed only for enabled RCBs
WCCOAiec618501:---------------------------------------------------
WCCOAiec618501:Dataset report for device <OA device name> " (IP:<IP>:<port>)IP:192.168.154.76:102) "
WCCOAiec618501:-- RCB <RCB name>
WCCOAiec618501: Dataset name : <dataset name>
WCCOAiec618501: Is dynamic : <Yes|No>
WCCOAiec618501: Is persistent: <Yes|No> (only shown for dynamic datasets)
WCCOAiec618501: Members: <List of dataset members>
WCCOAiec618501: --------------
WCCOAiec618501:------------------ End IEC device -----------------
WCCOAiec618501:<<<<<<<<<<<<<<<<<< End IEC 61850 >>>>>>>>>>>>>>>>>>-dbg DEBUG_DRV_CONF
Provides information on
- creating devices and RCBs
- initializing routines of devices and RCBs
- requests for configuration and control of RCBs on the device
The following debug output also shows the startup routine of the driver:
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.665, DEBUG_DRV_CONF, "New server <OA device name> added"=> Device <OA device name> created
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.668, DEBUG_DRV_CONF, "Server connection <OA device name> initializing..."=> Initializing of device <OA device name> is started
WCCOAiec618502:WCCOAiec61850(2), 20152017.05.27 15:32:03.671, DEBUG_DRV_CONF, "New RCB: <RCB name> added for server <OA device name>"=> RCB < RCB name > created
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.681, DEBUG_DRV_CONF, "Server connection <OA device name> initialized"=> Initializing device <OA device name> is completed
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.685, DEBUG_DRV_CONF, " Check remote device <OA device name> , send request to <RCB name>"=> Query properties of device <OA device name> because of <RCB name> attribute
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.695, DEBUG_DRV_CONF, " Updating ResvTms data type for server <OA device name>"=> Update properties of device <OA device name>
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.697, DEBUG_DRV_CONF, "<OA device name> anvil_8102, Data type for resvTms could not be read from device, using default."=> <OA device name> does not support resvTms or a buffered RCB is configured
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.700, DEBUG_DRV_CONF, "<OA device name> Request: Get attribute settings for RCB: <RCB name>"=> Query configuration of RCB <RCB name>
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.720, DEBUG_DRV_CONF, " ----- Extract attribute settings of RCB: <RCB name> from server <OA device name> -----"=> Start evaluating the configuration of <RCB name> from server <OA device name>.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.722, DEBUG_DRV_CONF, " Received attribute settings <RCB Konfiguration>"=> Output of configuration settings
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:03.740, DEBUG_DRV_CONF, " <OA device name>, Request: Write <attribute name> [attribute value] for RCB <RCB name>"=> Write the value [attribute value] of attribute <attribute name> for <RCB name> of device <OA device name>. [attribute value] is not available for all attributes of an RCB.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:32:05.700, DEBUG_DRV_CONF, " <OA device name>: remove RCB <RCB name>"=> Removed RCB <RCB name> (via RCB Management Panel)
-dbg DEBUG_DRV_SENT
Shows messages sent to the server.
// Startup
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:38:56.426, DEBUG_DRV_SENT, "Identify request send to server <OA device name>"=> Sent on startup and as alive telegram
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:39:02.531, DEBUG_DRV_SENT, "Write <Boolean|String|Octet String|Integer|UInteger> value for <OA device name>/<LN>$<FC>$<RCB name>$<BufTm|DatSet|IntglPd|RptID|EntryID>"=> Write an attribute of <RCB name> when enabling the RCB
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:39:02.541, DEBUG_DRV_SENT, "Write Trigger Options for <OA device name>/<LN>$<FC>$< RCB name >$TrgOps"=> Write trigger settings of <RCB name> when enabling the RCB
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:39:02.545, DEBUG_DRV_SENT, "Write Optional Fields for <OA device name>/<LN>$<FC>$< RCB name >$ OptFlds"=> Write optional field settings of <RCB name> when enabling the RCB
// Device Browsing
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:40:56.433, DEBUG_DRV_SENT, "Logical device list request sent to server <OA device name>"=> Request a list of all LDs of <OA device name> =[Request 1]
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:40:66.429, DEBUG_DRV_SENT, "Send MMS tag list request for Logical device <LD> to server <OA device name>"=> Request a list of all DOs (tag list) from logical device <LD> of <OA device name> =[Request 2]
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:40:76.452, DEBUG_DRV_SENT, "Send dataset list request for Logical Device <LD> to server <OA device name>"=> Request list of all datasets configured for <LD> of <OA device name> =[Request 3]
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:40:56.595, DEBUG_DRV_SENT, "Send Dataset attribute request for <data set> to server <OA device name>"=> Request dataset attributes of dataset <data set> of <OA device name> =[Request 4]
// General write requests
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:41:13.035, DEBUG_DRV_SENT, "Write mms tag value for <OA device name>/<LN>$FC$<DO>$<DA>=> Sent value to the data attribute
// Commands
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:41:13.035, DEBUG_DRV_SENT, "Write Control Struct <OA device name>/<LN>$CO$<DO>$Oper"=> Send switching command (Control Structure) for controllable object <DO> of <OA device name>/<LN>
-dbg DEBUG_DRV_RCVD
Provides either the type of received message or the source address on the device for received telegrams.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.996, DEBUG_DRV_RCVD, " Identify response from server <OA device name>"=> Response to alive telegram of <OA device name>.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.998, DEBUG_DRV_RCVD, "Value received from <OA device name>.<LD>/<LN>$<FC>$<DO>$<DA>, write to OA"=> Response to poll request, received value for <OA device name>.<LD>/<LN>$<FC>$<DO>$<DA> and sent to the driver framework
// Device Browsing
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.354, DEBUG_DRV_RCVD, "Received Logical device list (class 9) from server <OA device name>"=> Received list of LDs from <OA device name>, response to Request 1
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.355, DEBUG_DRV_RCVD, "LD name <LD>"=> Logical Device <LD>, response to Request 1
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.688, DEBUG_DRV_RCVD, " Received MMS tag list for Logical device <LD> (class 0) from server <OA device name>"=> Received tag list of logical device <LD> from server <OA device name>, response to Request 2.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.690, DEBUG_DRV_RCVD, " Tag name <<LN>>"=> Logical node <LN>, response to Request 2
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.691, DEBUG_DRV_RCVD, " Tag name <<LN>$<FC>>"=> Functional Constraint <FC> of logical node <LN>, response to Request 2
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.691, DEBUG_DRV_RCVD, " Tag name <<LN>$<FC>$<DO>>"=> Data object <DO> of logical node <LN>, response to Request 2
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.692, DEBUG_DRV_RCVD, " Tag name <<LN>$<FC>$<DO>$<DA>>"=> Data attribute <DO>$<DA> of logical node <LN>, response to Request 2
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.705, DEBUG_DRV_RCVD, "Received dataset list for Logical device IED1LogicalDevice1 (class 2) from server <OA device name>"=> Received list of datasets of logical device <LD> from server <OA device name>, response to Request 3
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.711, DEBUG_DRV_RCVD, "Dataset name <DatSet>"=> Dataset <DatSet>, response to Request 3
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:25:51.715, DEBUG_DRV_RCVD, "Read attribute response for dataset <DatSet> from server <OA device name> is success"=> Reading dataset attributes of dataset <DatSet> from server <OA device name> was successful, response to Request 4
-dbg DEBUG_DRV_COMMAND
Provides information about service requests that use the control model.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:45:16.733, DEBUG_DRV_COMMAND, "Writing Controllable Object <LD>/<LN>$<FC>$<DO>$<DA> to the Server: <OA device name> with following values:
WCCOAiec618502:Control value: <value to be written>
WCCOAiec618502:Ctlnum value: <control number> WCCOAiec618502:Test: <0/1>
WCCOAiec618502:Check: <no-check|synchrocheck|interlocking|both>
WCCOAiec618502:Originator: <host name>_<project name>_<driver number>
WCCOAiec618502:Category: <originator category>"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:45:16.756, DEBUG_DRV_COMMAND, "Write Response for Controllable Object <LD>/<LN>$<FC>$<DO>$<DA> from Server: <OA device name> is Success"-dbg DEBUG_DRV_REPORT
Shows which values of an RCB are sent to WinCC OA. There is only output for configured addresses.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:50:47.528, DEBUG_DRV_REPORT, "Write data received through report to: <OA device name>.<LD>/<LN>$<FC>$<DO>$<DA>"-dbg DRV_REPORT_CONFIG
Enables tracking of the requirements for an RCB on the device (e.g. changes to the configuration and activation)
// Activation and configuration
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:43.403, DRV_REPORT_CONFIG, "<OA device name>, Start all RCBs at remote state: <remote state>"=> Starting enabling routines for all RCBs of <OA device name>. On startup, the device state is <remote state>. Possible states:
- REMOTE_UNKNOWN, // startup or retry if not checked
- REMOTE_UNREACHABLE, // tried but failed
- REMOTE_PENDING, // request sent
- REMOTE_CHECKED, // done
- REMOTE_CHECK_INCOMPLETE // Either rsvTmsDataType or iec edition could not be detected
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:43.608, DRV_REPORT_CONFIG, "<OA device name> , State change for <RCB name> reserve is <0|1>| enable is <0|1>"=> The driver received the request (DP interface or internal logic) to change the state of RCB <RCB name>. Which reserve or activation state is necessary depends on the values of „reserve is" and „enable is"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:45.379, DRV_REPORT_CONFIG, "<OA device name> , Request: configure dataset <dataset name> for RCB <report ID>"=> On enabling RCB <report ID> it is requested to configure the RCB with dataset <dataset name>
//Request: " Process RCB response" confirms that a request to the RCB is processed by the device. There is no indication whether the request was successful.
The "index" field shows the instance number for instanced RCBs. Otherwise the field is empty. The "is manual" field shows whether the request was triggered by data point interface (1) or driver logic (0).
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:43.363, DRV_REPORT_CONFIG, "Process RCB response: device: <OA device name>| report: <report ID>|index: | request: Reserve RCB| attribute: Resv| value: <0/1>1| is manual: 1"=> Request to reserve (1) the RCB <report ID> or cancel the reservation (0)
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:43.376, DRV_REPORT_CONFIG, "Process RCB response: device: <OA device name>| report: <report ID>| index: | request: Read RCB Attributes| attribute: <RCB name>| value: 1| is manual: 1"=> Request to read the attributes of RCB <report ID>
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:43.411, DRV_REPORT_CONFIG, "Process RCB response: device: <OA device name>| report: <report ID>| index: | request: Write RCB Attribute| attribute: <BufTm|DatSet|IntglPd|OptFlds|RptID|TrgOps>| value:1 is manual: 1"=> Request to write an attribute of RCB <report ID>
// Acknowledgements
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:43.412, DRV_REPORT_CONFIG, "OK: <BufTm|DatSet|IntglPd|OptFlds|RptID|TrgOps>"=> Writing the attribute was successful
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 15:59:43.379, DRV_REPORT_CONFIG, "Attribute read OK: <RCB name>"=> Reading an attribute of <RCB name> was successful
-dbg DRV_REPORT_RCV
Provides information about received reports. All elements are displayed, regardless of whether an address is configured.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:04:25.656, DRV_REPORT_RCV, "---------------- New report <report ID> received"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:04:25.659, DRV_REPORT_RCV, "Type: Unbuffered"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:04:25.659, DRV_REPORT_RCV, "Sequence Num: <number>"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:04:25.660, DRV_REPORT_RCV, "Reason: <DATA_CHANGE|DATA_FREEZE|GEN_INTER|INTEGRITY|QUALITY_CHANGE>"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:04:25.669, DRV_REPORT_RCV, "Element at index <0..n>: <logical device name>/<LN>$<FC>$<DO> WCCOAiec618502:"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:04:25.671, DRV_REPORT_RCV, " Attribute at index <0..n>: <LN>$<FC>$<DO>$<DA>"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:04:25.697, DRV_REPORT_RCV, "---------------- Report <report ID> done-dbg DRV_REPORT_PROCESS
Provides information about received reports. All elements are displayed, regardless of whether an address is configured.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:06:32.003, DRV_REPORT_PROCESS, "---------------- Start processsing report <report ID>"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:06:32.004, DRV_REPORT_PROCESS, "Element <LD>/<LN>$<FC>$<DO>"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:06:32.005, DRV_REPORT_PROCESS, " Attribute <LN>$<FC>$<DA>$<DO>"
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:06:32.022, DRV_REPORT_PROCESS, "---------------- report <report ID> done-dbg DRV_DATASET_CONFIG
Provides information on static and dynamic datasets.
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:09:38.077, DRV_DATASET_CONFIG, "<OA device name>: add new dataset <dataset name>"=> Added dataset <dataset name>" to the driver
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:09:38.406, DRV_DATASET_CONFIG, "<OA device name>: add dataset attributes for <dataset name>"=>Added attributes to data set elements of the data set <dataset name>" (this is only valid for datasets of type FC, i.e. datasets whose elements are data objects)
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:09:45.795, DRV_DATASET_CONFIG, "<OA device name>, Request: Write dynamic dataset <dataset name> triggered by RCB <RCB name>"=> Request to write the dataset <dataset name> (which is assigned to RCB <RCB name>) on the device
WCCOAiec618502:WCCOAiec61850(2), 2017.05.27 16:09:45.801, DRV_DATASET_CONFIG, "<OA device name> , Dataset <name> busy, RCB <report ID>"=> Dataset <dataset name> assigned to an RCB <RCB name> cannot be written. This message is displayed if several RCBs use the same dynamic data set. The data set is written when the first RCB is activated. During this process, the message is shown when the other RCBs are activated. The RCBs are enabled as soon as the dataset is written to the device.
-dbg DRV_FILE_TRANS
Provides information for tracing file transfer operations.