10 monitoring processes, 1 time monitoring for fif-can1_in ... fif-can3_in, 2 bus-off – Lenze DDS System bus CAN for PLC User Manual
Page 69: Time monitoring for fif−can1_in ... fif−can3_in, Bus−off, System bus (can) for lenze plc devices, Configuration (fif interface), 1 time monitoring for fif−can1_in ... fif−can3_in, 2 bus−off
System bus (CAN) for Lenze PLC devices
Configuration (FIF interface)
5−9
l
PLC−Systembus EN 2.0
5.10
Monitoring processes
5.10.1
Time monitoring for FIF−CAN1_IN ... FIF−CAN3_IN
For the inputs of the process data objects FIF−CAN1_IN ... FIF−CAN3_IN a time monitoring can be
configured via C2457:
Code
LCD
Possible settings
Information
Lenze
Selection
C2457
1
2
3
CE11monit time
CE12monit time
CE13monit 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 C2481 ... C2483:
Code
LCD
Possible settings
Information
Lenze
Selection
C2481 MONIT CE11
3
0
TRIP
2
Warning
3
Off
Configuration of the monitoring for
FIF−CAN1_IN error (CE11)
C2482 MONIT CE12
3
0
TRIP
2
Warning
3
Off
Configuration of the monitoring for
FIF−CAN2_IN error (CE12)
C2483 MONIT CE13
3
0
TRIP
2
Warning
3
Off
Configuration of the monitoring for
FIF−CAN3_IN error (CE13)
5.10.2
Bus−off
If the PLC has disconnected from the system bus due to too many incorrectly received telegrams,
the signal "BusOffState" (CE14) is set.
The response to this can be configured via C2484:
Code
LCD
Possible settings
Information
Lenze
Selection
C2484 MONIT CE14
0
0
Off
1
Controller inhibit
2
Quick stop (QSP)
Configuration of the monitoring for
"BusOffState" (CE14)
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. See chapter 3.13.3, "Bus load by the PLC".
(
^ 3−15)