Error Handling: Unterschied zwischen den Versionen

Aus CANopen-Lift
Zur Navigation springen Zur Suche springen
(Die Seite wurde neu angelegt: „== Introduction == CANopen devices compliant to this application profile shall support the Emergency service and the Emergency protocol as specified in /CiA301/.…“)
 
Zeile 7: Zeile 7:
specified in /CiA301/. The manufacturer-specific error field (msef) shall be reserved for future
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.
use. The structure of the Emergency message is specified in /CiA301/ and shown in Figure 1.
{| cellspacing="0" cellpadding="2" border="1"
|-
! scope="col" | Byte 7
! scope="col" | Byte 6
! scope="col" | Byte 5
! scope="col" | Byte 4
! scope="col" | Byte 3
! scope="col" | Byte 2
! scope="col" | Byte 1
! scope="col" | Byte 0
|-
| align = "center" colspan="5" | msef
| er
| align = "center" colspan="2" | eec
|}
Figure 1 - Structure of the Emergency message

Version vom 4. Januar 2012, 12:09 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