Diagnostic Counter - Lenze i55AE125B Manual

Configuring the network
CANopen
Error responses
Parameter Name / value range / [default setting]
0x1029:001 Error behavior: Communication error
0 Status -> Pre-operational
1 No status change
2 Status -> Stopped
0x2857:001 CANopen monitoring: RPDO1-Timeout
• For further possible settings, see parameter
0x2D45:001
3 Fault
0x2857:002 CANopen monitoring: RPDO2-Timeout
• For further possible settings, see parameter
0x2D45:001
3 Fault
0x2857:003 CANopen monitoring: RPDO3-Timeout
• For further possible settings, see parameter
0x2D45:001
3 Fault
0x2857:005 CANopen monitoring: Heartbeat-Timeout Consumer 1
• For further possible settings, see parameter
0x2D45:001
3 Fault
0x2857:006 CANopen monitoring: Heartbeat-Timeout Consumer 2
• For further possible settings, see parameter
0x2D45:001
3 Fault
0x2857:007 CANopen monitoring: Heartbeat-Timeout Consumer 3
• For further possible settings, see parameter
0x2D45:001
3 Fault
0x2857:008 CANopen monitoring: Heartbeat-Timeout Consumer 4
• For further possible settings, see parameter
0x2D45:001
3 Fault
0x2857:010 CANopen monitoring: "Bus-off" state change
• For further possible settings, see parameter
0x2D45:001
2 Trouble
0x2857:011 CANopen monitoring: Warning
• For further possible settings, see parameter
0x2D45:001
1 Warning
9.4.12

Diagnostic counter

The following parameters serve to diagnose the communication activities between the inver-
ter and the CANopen network. The counters are free-running, i. e. when the maximum value
has been reached, the respective counter starts at 0 again.
Parameter Name / value range / [default setting]
0x230A:000 CANopen statistics: Highest subindex
• Read only
0x230A:001 CANopen statistics: PDO1 received
(P580.01) (CAN statistics: PDO1 received)
• Read only
276
(P310.01).
^ 223
(P310.01).
^ 223
(P310.01).
^ 223
(P310.01).
^ 223
(P310.01).
^ 223
(P310.01).
^ 223
(P310.01).
^ 223
(P310.01).
^ 223
(P310.01).
^ 223
Info
Selection of the NMT state to which the inverter is to change automati-
cally if a failure of a CANopen node or an internal error is detected in the
"Operational" state.
These also include the following communication errors:
• Change-over of the CAN interface to the "Bus-off" state.
• Occurrence of a "Heartbeat Event".
In the "Pre-operational" state, network management, sync, and emer-
gency telegrams as well as parameter data can be received; process
data, however, are ignored.
In the "Stopped" state, only network management telegrams can be
received.
Selection of the response to triggering the RPDO1 time monitoring.
Associated error code:
33425 | 0x8291 - CAN: RPDO1 time-out
•
Selection of the response to triggering the RPDO2 time monitoring.
Associated error code:
33426 | 0x8292 - CAN: RPDO2 time-out
•
Selection of the response to triggering the RPDO3 time monitoring.
Associated error code:
33427 | 0x8293 - CAN: RPDO3 time-out
•
Selection of the response with "Heartbeat Event" in consumer 1.
Associated error code:
33156 | 0x8184 - CAN: heartbeat time-out consumer 1
•
Selection of the response with "Heartbeat Event" in consumer 2.
Associated error code:
33157 | 0x8185 - CAN: heartbeat time-out consumer 2
•
Selection of the response with "Heartbeat Event" in consumer 3.
Associated error code:
33158 | 0x8186 - CAN: heartbeat time-out consumer 3
•
Selection of the response with "Heartbeat Event" in consumer 4.
Associated error code:
33159 | 0x8187 - CAN: heartbeat time-out consumer 4
•
Selection of the response to changing to the "Bus off" state.
Associated error code:
33154 | 0x8182 - CAN: bus off
•
Selection of the response that is executed in the case of too many incor-
rectly sent or received CAN telegrams (> 96).
Associated error code:
33155 | 0x8183 - CAN: warning
•
Info
Number of frame and error counters.
Display of the number of PDO1 telegrams received.