Lenze Drive PLC - Monitoring System Bus Inputs

System bus (CAN) with Ser vo PLC & Drive PLC
Configuration
3-7
l PLC-Systembus EN 1.1
3.10 Monitoring
3.10.1 Time monitoring for CAN1_IN ... CAN3_IN
Via C0357 you can configure a time monitoring for the inputs of process data objects CAN1_IN ...
CAN3_IN:
Code LCD
Possible settings
Info
Lenze Choice
C0357
1
2
3
CE1monit time
CE2monit time
CE3monit time
3000
3000
3000
0 {1 msec} 65000 Monitoring time for process data
input objects
If there was no telegram received in the defined monitoring time, you can configure the
corresponding reaction in codes C0591 ... C0593:
Code LCD
Possible settings
Info
Lenze Choice
C0591 MONIT CE1 3 0Trip
2 Warning
3Off
Configuration monitoring: CAN1_IN
error “CommErrCANIN1” (CAN1
CE1)
C0592 MONIT CE2 3 0Trip
2 Warning
3Off
Configuration monitoring: CAN2_IN
error “CommErrCANIN2” (CAN2
CE2)
C0593 MONIT CE3 3 0Trip
2 Warning
3Off
Configuration monitoring CAN3_IN
error “CommErrCANIN3” (CAN3
CE3)
3.10.2 Bus off
If the PLC has decoupled itself from the system bus because too many of the received telegrams
were faulty, the signal “BusOffState” (CE4) is set.
The reaction to this can be configured via code C0595:
Code LCD
Possible settings
Info
Lenze Choice
C0595 MONIT CE4 3 0Trip
2 Warning
3Off
Configuration monitoring
“BusOffState” (CE4)
Tip!
Possible reasons for faulty telegrams may be:
• A missing bus termination
• Insufficient screening
• Potential differences in the grounding of the control electronics
• the bus load is too high
Show/Hide Bookmarks