Error Handling: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
| Zeile 34: | Zeile 34: | ||
CANopen devices compliant to the application profile CiA417 shall support the additional error codes | CANopen devices compliant to the application profile CiA417 shall support the additional error codes | ||
defined in Table 2. | defined in Table 2. | ||
{| cellspacing="0" cellpadding="2" border="1" | |||
|- | |||
! scope="col" | eec | |||
! scope="col" | Description | |||
|- | |||
| F001h | |||
| <tbd> | |||
|- | |||
| F002h | |||
| <tbd> | |||
|- | |||
| F003h | |||
| <tbd> | |||
|} | |||
Table 2 - Structure of the Emergency message | |||
Version vom 4. Januar 2012, 12:18 Uhr
Introduction
CANopen devices compliant to this application profile shall support the Emergency service and the Emergency protocol as specified in /CiA301/.
Emergency messages are triggered by internal errors in the device. They are structured as specified in /CiA301/. The manufacturer-specific error field (msef) shall be reserved for future use. The structure of the Emergency message is specified in /CiA301/ and shown in Figure 1.
| Byte 7 | Byte 6 | Byte 5 | Byte 4 | Byte 3 | Byte 2 | Byte 1 | Byte 0 |
|---|---|---|---|---|---|---|---|
| msef | er | eec | |||||
Figure 1 - Structure of the Emergency message
- eec: Emergency error code
- er: Error register (see object 1001h)
- msef: Manufacturer-specific error code
Additional error codes
CANopen devices compliant to the application profile CiA417 shall support the additional error codes defined in Table 2.
| eec | Description |
|---|---|
| F001h | <tbd> |
| F002h | <tbd> |
| F003h | <tbd> |
Table 2 - Structure of the Emergency message