Lenze DDS System bus CAN for PLC - Manual (Page 45)

System bus (CAN) for Lenze PLC devices
"CAN" system bus interface configuration
3−11
l
PLC−Systembus EN 2.0
3.12 Monitoring processes
3.12.1 Time monitoring for CAN1_IN ... CAN3_IN
For the inputs of the CAN1_IN ... CAN3_IN process data objects a time monitoring can be configured
via C0357:
Code LCD Possible settings Information
Lenze Selection
C0357
1
2
3 CE1monit time
CE2monit time
CE3monit time 3000
3000
3000
0 {1 ms} 65000 Monitoring time for process data
input objects
The response for the case that no telegram has been received within the defined monitoring time can
be configured via codes C0591 ... C0593:
Code LCD Possible settings Information
Lenze Selection
C0591 MONIT CE1 3 0 TRIP
2 Warning
3 Off
Configuration of the monitoring for
CAN1_IN error "CommErrCANIN1"
(CAN1 CE1)
C0592 MONIT CE2 3 0 TRIP
2 Warning
3 Off
Configuration of the monitoring for
CAN2_IN error "CommErrCANIN2"
(CAN2 CE2)
C0593 MONIT CE3 3 0 TRIP
2 Warning
3 Off
Configuration of the monitoring for
CAN3_IN error "CommErrCANIN3"
(CAN3 CE3)
3.12.2 Bus−off
If the PLC has disconnected from the system bus due to too many incorrectly received telegrams,
the signal "BusOffState" (CE4) is set.
The response to this can be configured via C0595:
Code LCD Possible settings Information
Lenze Selection
C0595 MONIT CE4 3 0 TRIP
2 Warning
3 Off
Configuration of the monitoring for
"BusOffState" (CE4)
Tip!
Possible causes for incorrectly received telegrams can be:
·
Missing bus termination
·
Non−sufficient shielding
·
Differences in potential with regard to the earth connection of the control electronics
·
Bus load too high