| 0x0000 |
No eror No error
|
0x0001
|
Unspecified error General Error which is not defined in the following list
|
0x0002
|
No Memory Local Application runs out of memory
(e.g. dynamic memory allocation for emergency messages
|
0x0011
|
Invalid requested state change Requested state change is invalid(e.g. IS, IO, PO, PB, SB, OB)
|
0x0012
|
Unknown requested state Requested state change is unknown(e.g. if the requested state code is not 1, 2, 3 4, 8)
|
0x0014
|
No valid firmware The downloaded file is no valid firmware file
|
0x0013
|
Bootstrap not supported The device doesn't support Bootstrap state
|
0x0015
|
Invalid mailbox configurationThe maibox SyncManger configuration is not valid in Bootstrap state
|
0x0016
|
Invalid mailbox configurationThe mailbox SyncManger configuration is not valid in PREOP state
|
0x0017
|
Invalid sync manager configuration Sync manager configuration is not valid
|
0x0018
|
No valid inputs available Slave application cannot provide valid inputs
|
0x0019
|
Slave applicaton cannot receive valid outputs
|
0x001A
|
Synchronization eror Multiple synchronization errors. Device is not synchronized any more(shall be used d no specific Synchronization error can be distinguished)
|
0x001B
|
Sync manager watchdogNo process data recerved yet (s->O)or not received within a specifed timeout value
|
0x001C
|
Invalid Sync Manager Types
|
0x001D
|
Invalid output Configuration SyncManger configuration for output process data is invalid
|
0x001E
|
Invalid Input configurator SyndManger configuration for mput process data is invalid
|
0x001F
|
Invalid watchdog configuration watchdog Settings are invalid (e.g. SyndManger watchdog trigger is enabled but no watchdog timeout is defined)
|
0x0020
|
Slave needs cold start evice requires a power off-power on reset
|
0x0021
|
Slave needs INIT pplication requests INIT state
|
0x0022
|
Slave needs PREOP Slave application requests PREOP state
|
0x0023
|
Slave needs SAFEOP Slave application requests SAFEOP state
|
0x0024
|
Invalid Input Mapping Input process data mapping do not match to expected mapping
|
0x0025
|
Invalid Output Mappingoutput process data mapping do not match to expected mapping
|
0x0026
|
Inconsistent Settings General settings mismatch
|
0x0027
|
Freerun not supported
|
0x0028
|
Synchronization not supported
|
0x0029
|
Freerun needs 3 Buffer ModeFreeRun Mode, sync manager has to run in 3-Bufler Mode
|
0x002A
|
Background Watchdog
|
0x002B
|
No Valid Inputs and Outputs
|
0x002C
|
Fatal Sync Error Fatal Sync Error Synco or Sync1 are not received any more
|
0x002D
|
No Sync Eror ync not receed: In SAFEOP the slave waits for the firstSyncorSync1 events before switching to OP if these events were not received during the SAFEOP to OP- Timeout time the ecode should refuse the state transition to oP with this al status(SystemTimeottset too big. no DC event received
|
0x0030
|
Invalid DC SYNC Configuration Distributed Clocks configuraton is invalid due to applicaton requirements
|
0x0031
|
Invalid DC Latch Configuration DC Latch connguration is invalld due to application requirements
|
0x0032
|
PLL ErTor Master not synchronized at least one DC event received
|
0x0033
|
DC Sync IO Error Mutuple synchronization errors. IO is not synchronized any more
|
0x0034
|
DC Sync Timeout ErrorMufuple synchronization errors. Too much SM Events missed
|
0x0035
|
DC Invalid Sync Cycle Time
|
0x0036
|
DC Synco Cyde Time DC Synco Cycle time does not fit to applicaton requrements
|
0x0037
|
DC Sync1 Cycle Time DC Sync1 cyde time does not nt to application requirements
|
0x0041
|
MBX_ AOE
|
0x0042
|
MBX EOE
|
0x0043
|
MBX COE
|
0x0044
|
MBX FOE
|
0×0045
|
MBX SOE
|
0x004F
|
MBX VOE
|
0x0050
|
EEPROM No Access EEPROM not assigned to PDI
|
0x0051
|
EEPROM Error EEPROM access error
|
0x0060
|
Slave Restarted Locally
|
0x0061
|
Device ldentification value updated The device identifcation value was updated and is now valid
|
0x00F0
|
Application Controler avalable The local application releases the appcation controller which snow avadable and services the ethercAt state machine and all other device features
This optional AL Status Code shall onty be used for devices that have a different power suppl for the ESC and the application controller and which cannot define a maximum timeout value for transition|→P
NOTE: Use case can be if ESC is powered before applicaton controller. Err Indication can be used by Master to indicate that stave is ready for boot-up (instead of cchc polling)
|
