| Bus and master main errors |
TIMEOUT-ERROR |
The DEVICE has detected an overstepped timeout supervision time of at least one CAN message to be sent. The transmission of this message was aborted. The data ist lost. It is an indication that no other CAN device was connected or responsive at this time to acknowledge the sent messages requests. The number of detected timeouts is fixed in the Msg_Time_Out variable. The bit will be sent when the first timeout was detected and will not be deleted anymore. |
| |
HOST-NOT-READY-NOTIFICATION |
Indicates if the HOST program has set its state to operate or not. If the bit is set the HOST program is not ready to communicate. |
| |
EVENT-ERROR |
The DEVICE has detected transmission errors. The number of detected events are fixed in the Bus_Error_Cnt and Bus Off Cnt variables. The bit will be sent when the first event was detected and will not be deleted anymore. |
| |
NON-EXCHANGE-ERROR |
At least one node hast not reached the data exchange state and no process data is exchanged with it. |
| |
AUTO-CLEAR-ERROR |
Device stopped the communication to all nodes and reached the autoclear end state. |
| |
CONTROL-ERROR |
Parameterization error or severe run time error. |
| Master main state |
Offline |
In OFFLINE state, there is no communication (data transfer) permitted at all. This is the state after initialization. This means, the master is waiting for a signal to start and does not participate in the token ring of the PROFIBUS access control mechanism |
| |
Stop |
In STOP state, there is no data transfer permitted between master and slaves. Data transfer to other masters in multi-master system is allowed, however. The bus parameter set has been loaded successfully in order to get into STOP state. |
| |
Clear |
In CLEAR state, the master is able to read the input data from the DP slaves. The master forces the outputs to the slaves to be in a safe state (i.e. they contain only the value 0). For instance, incorrect data transfer of a slave can cause the PROFIBUS DP master to fall back from OPERATE state to CLEAR state. Parameterization and configuration checks are possible in this state. |
| |
Operate |
In OPERATE state, unrestricted data transfer is possible. This data transfer is cyclic, i.e. periodically, the input values are read from the slaves and the output data are written to the slaves. |
| Location of error |
0..125 |
Address of the slave with error |
| Error event |
|
not used currently |
| Bus error counter |
|
Counter for the bus error events |
| Number of bus timeouts |
|
Counter for bus timeouts |
