Siemens MICROMASTER 420 Operating Instructions Manual page 51

Issue 01/05
Optimizing EMERGENCY telegrams
In order to better handle Emergency telegram that are sent non-synchronously
when high bus load levels exist, there are various optimization methods.
Emergency messages can be suppressed by setting bit 31 in object 1014H (COB-
ID EMCY). Then, faults that occur are only displayed in the status word and can be
read-out of object 1003H.
Object 1014H also allows the COB-ID to be changed, which can then be used to
modify the priority of the message. Using the object 1015H (Inhibit Time EMCY), it
is possible to set a delay time for sending the EMCY message.
MICROMASTER 420/430/440 sends an Emergency message if an fault has
occurred in either the option module or in the inverter.
Table 3-13 EMERGENCY messages that are not generated by the drive
Error Code Meaning
(Bytes 1/ 2)
(Hex)
6300H Dataset update failed
7600H ResetCommunication
or
ResetNode failed
7600H ResetCommunication
or
ResetNode not possible
8000H CAN sync error
8000H Drive running
8110H CAN overrun
8130H CAN lifeguarding failure
8140H Busoff cleared
CANopen Option Module Operating Instructions
6SE6400-5BC00-0BP0
Additional Description
code
(Bytes 3/4)
1 Failed to change to new drive dataset. Further
information in diagnostic parameter P2054[0].
Note that this message does not have a
corresponding reset-emergency message!!!
2 Tried to execute ResetNode, or ResetCommunication
after data has been saved to EEPROM.
Note that this message does not have a
corresponding reset-emergency message!!!
2 ResetNode, or resetCommunication failed. Further
information in diagnostic parameter P2054[0].
Note that this message does not have a
corresponding reset-emergency message!!!
0 CAN sync object not received within communication
cycle period 1006H x 1.5
1 Tried to execute ResetNode, or ResetCommunication
whilst drive running.
Note that this message does not have a
corresponding reset-emergency message!!!
0 Data Overrun has occurred
(unable to process data before next message arrived).
0 RTR frame was not received within the time: Node
Guard time x Node Lifetime factor
0 Busoff condition has been cleared.
Note that this message does not have a
corresponding reset-emergency message!!!
Data transfer using CANopen
51