Application Status Register
The application status register is primarily used in SYNC applications. It is used in applications where the network in question supports the ability to indicate critical process data errors to the master. If the application sets an error status to the application status register, the module cannot operate in the PROCESS_ACTIVE state. The Anybus CompactCom will accept and handle the below listed status codes written by the application.
Value | Error | Description | Anybus CompactCom 40 PROFINET IRT IIoT Secure Response |
|---|---|---|---|
0000h | No error | Ready for transition to state PROCESS_ACTIVE (Default) | If Isochronous mode is active, the Anybus CompactCom monitors write process data updates according to the table below (Input time failure). |
0001h | Not yet synchronized | Not ready for transition to state PROCESS_ACTIVE | Alarm: Application not synchronized
|
0002h | Sync configuration error | A problem with the current attribute values in the Sync object prevents the transition to state PROCESS_ACTIVE | Alarm: Sync configuration error
|
0003h | Read process data configuration error | A problem with the current read process data mapping prevents the transition to state PROCESS_ACTIVE | Alarm: Output configuration error
|
0004h | Write process data configuration error | A problem with the current write process data mapping prevents the transition to state PROCESS_ACTIVE | Alarm: Input configuration error
|
0005h | Synchronization loss | The application has lost synchronization lock If the Anybus CompactCom is in the state PROCESS_ACTIVE, it will change to the state ERROR | Alarm: Application not synchronized
|
0006h | Excessive data loss | The application has detected a significant loss of process data from the network If the Anybus CompactCom is in the state PROCESS_ACTIVE, it will change to the state ERROR | |
0007h | Output error | Application malfunction If the Anybus CompactCom is in the state PROCESS_ACTIVE, it will change to the state ERROR | Alarm: Output disabled
|
The Anybus CompactCom produces synchronous mode related diagnosis as shown in the table below, where the cause is reported from the Application status register.
Cause | ChannelErrorType | ExtChannelErrorType | Description |
|---|---|---|---|
0007h | 0018h | - | Output disabled |
0001h or 0005h or 0006h | 7000h (vendor specific – “Isochronous mode error”) | 0001h | Application not synchronized |
0002h | 0002h | Sync configuration error | |
0003h | 0003h | Output configuration error | |
0004h | 0004h | Input configuration error | |
0000h | 8004h (Isochronous mode mismatch) | 8001h | Input time failure is reported if the application status register reports 0000h and Isochronous Mode is active and no new write process data update occurs before input processing. |
For GSDML entries, see the SYNC example GSDML file that is included in the configuration files package, that can be downloaded from the Anybus CompactCom 40 PROFINET IRT IIoT Secure page at www.anybus.com/technical-support.