Operating Instructions

SINAMICS G120 CU230P-2 Control Units
List Manual, 04/2018, A5E33838102
819
4 Faults and alarms
4.2 List of faults and alarms
2: The master no longer interrogated the CAN node status longer than for its "life time". The "life time" is obtained
from the "guard time" (p8604[0]) multiplied by the "life time factor" (p8604[1]).
- bus cable interrupted.
- bus cable not connected.
- incorrect baud rate.
- incorrect bit timing.
- master fault.
Note:
The fault response can be set as required using p8641.
See also: p8604 (CAN life guarding), p8641 (CAN Abort Connection Option Code)
Remedy: - check the bus cable
- check the baud rate (p8622).
- check the bit timing (p8623).
- check the master.
The CAN controller must be manually restarted with p8608 = 1 after the cause of the fault has been resolved!
See also: p8608 (CAN Clear Bus Off Error), p8622 (CAN bit rate), p8623 (CAN Bit Timing selection)
F08701 CAN: NMT state change
Message class: Communication error to the higher-level control system (9)
Reaction: OFF3
Acknowledge: IMMEDIATELY
Cause: A CANopen NMT state transition from "operational" to "pre-operational" or after "stopped".
Fault value (r0949, interpret decimal):
1: CANopen NMT state transition from "operational" to "pre-operational".
2: CANopen NMT state transition from "operational" to "stopped".
Note:
In the NMT state "pre-operational", process data cannot be transferred and in the NMT state "stopped", no process
data and no service data can be transferred.
Remedy: Not necessary.
Acknowledge the fault and continue operation.
F08702 (A) CAN: RPDO Timeout
Message class: Communication error to the higher-level control system (9)
Reaction: OFF3 (NONE, OFF1, OFF2)
Acknowledge: IMMEDIATELY
Cause: The monitoring time of the CANopen RPDO telegram has expired because the bus connection was either interrupted
or the CANopen Master was switched-off.
See also: p8699 (CAN: RPDO monitoring time)
Remedy: - check the bus cable
- check the master.
- If required, increase the monitoring time (p8699).
A08751 (N) CAN: Telegram loss
Message class: Communication error to the higher-level control system (9)
Reaction: NONE
Acknowledge: NONE
Cause: The CAN controller has lost a receive message (telegram).
Remedy: Reduce the cycle times of the receive messages.