IO Controller Common Status Block View

Parameter	Description
Communication state of change	The communication change of state register contains information about the current operating status of the communication channel and its firmware. Possible state changes (see below table for details) are: Restart Required Enable Restart Required Configuration New Configuration Locked Bus On Running Ready
Communication state	The communication state field contains information regarding the current network status of the communication channel. Depending on the implementation, all or a subset of the definitions below is supported: UNKNOWN NOT_CONFIGURED STOP IDLE OPERATE
Communication error	This field holds the current error code of the communication channel. If the cause of error is resolved, the communication error field is set to 0 (= RCX_SYS_SUCCESS) again. Not all of the error codes are supported in every implementation. Protocol stacks may use a subset of the error codes below: SUCCESS  0x00000000 Runtime Failures: WATCHDOG TIMEOUT  0xC000000C Initialization Failures: INITIALIZATION FAULT 0xC0000100 DATABASE ACCESS FAILED 0xC0000101 Configuration Failures NOT CONFIGURED  0xC0000119 CONFIGURATION FAULT 0xC0000120 INCONSISTENT DATA SET 0xC0000121 DATA SET MISMATCH  0xC0000122 INSUFFICIENT LICENSE 0xC0000123 PARAMETER ERROR  0xC0000124 INVALID NETWORK ADDRESS 0xC0000125 NO SECURITY MEMORY  0xC0000126 Network Failures NETWORK FAULT  0xC0000140 CONNECTION CLOSED  0xC0000141 CONNECTION TIMED OUT  0xC0000142 LONELY NETWORK  0xC0000143 DUPLICATE NODE  0xC0000144 CABLE DISCONNECT 0xC0000145
Version	The version field holds version of this structure. It starts with 1; 0 is not defined. Version should be 1.
Host Watchdog	This field holds the configured watchdog timeout value in milliseconds. The application may set its watchdog trigger interval accordingly. If the application fails to copy the value from the host watchdog location to the device watchdog location, the protocol stack will interrupt all network connections immediately regardless of their current state.
Error Count	This field holds the total number of errors detected since power-up, respectively after reset. The protocol stack counts all sorts of errors in this field no matter if they were network related or caused internally.
Number of configured slaves	The firmware maintains a list of Slaves to which the Master has to open a connection. This list is derived from the configuration database. This field holds the number of configured Slaves.
Slave state	The Slave state field indicates whether the Master is in cyclic data exchange to all configured Slaves. In case there is at least 1 Slave missing or if the Slave has a diagnostic request pending, the status is set to FAILED. For protocols that support non-cyclic communication only, the Slave state is set to OK as soon as a valid configuration is found. (UNDEFINED, NO_FAULT,FAILED)
Number of IO-Devices currently exchanging cyclic data	The firmware maintains a list of Slaves to which the Master has successfully opened a connection. Ideally, the number of active Slaves is equal to the number of configured Slaves. For certain fieldbus systems it could be possible that the Slave is shown as activated, but still has a problem in terms of a diagnostic issue. This field holds the number of active Slaves.
Number of configured IO-Devices not exchanging …	If a Slave encounters a problem, it can provide an indication of the new situation to the Master in certain fieldbus systems. As long as those indications are pending and not serviced, the field holds a value unequal 0. If no more diagnostic information is pending, the field is set to 0.

Communication Change of State Flags

Bit Definition	Description
Ready	0 - … 1 - The Ready flag is set as soon as the protocol stack is started properly. Then the protocol stack is awaiting a configuration. As soon as the protocol stack is configured properly, the Running flag is set, too.
Running	0 - … 1 - The Running flag is set if the protocol stack has been configured properly. Then the protocol stack is awaiting a network connection. Now both the Ready flag and the Running flag are set.
Bus On	0 - … 1 - The Bus On flag is set to indicate to the host system whether or not the protocol stack has the permission to open network connections. If set, the protocol stack has the permission to communicate on the network; if cleared, the permission was denied and the protocol stack will not open network connections.
Configuration Locked	0 - … 1 - The Configuration Locked flag is set, if the communication channel firmware has locked the configuration database against being overwritten. Re-initializing the channel is not allowed in this state. To unlock the database, the application has to clear the Lock Configuration flag in the control block.
Configuration New	0 - … 1 - The Configuration New flag is set by the protocol stack to indicate that a new configuration became available, which has not been activated. This flag may be set together with the Restart Required flag.
Restart Required	0 - … 1 - The Restart Required flag is set if the channel firmware requests to be restarted. This flag is used together with the Restart Required Enable flag below. Restarting the channel firmware may become necessary, if a new configuration was downloaded from the host application or if a configuration upload via the network took place.
Restart Required Enable	0 - … 1 - The Restart Required Enable flag is used together with the Restart Required flag above. If set, this flag enables the execution of the Restart Required command in the netX firmware (for details on the Enable mechanism see section 2.3.2 of the netX DPM Interface Manual).