Instruction Manual
Table Of Contents
- System bus (CAN) for Lenze PLC devices
- This documentation is valid for ...
- Contents
- 1 Preface and general information
- 2 General information on the system bus (CAN)
- 2.1 Introduction
- 2.2 Interfaces of the Lenze PLCs for system bus connection
- 2.3 Identification of the nodes
- 2.4 Structure of the CAN telegram
- 2.5 Network management (NMT)
- 2.6 Transmission of process data
- 2.7 Transmitting parameter data
- 2.8 Free CAN objects
- 2.9 Application recommendations for the different CAN objects
- 2.10 Monitoring mechanisms
- 3 Configuration (system bus - CAN interface)
- 3.1 CAN baud rate
- 3.2 CAN boot-up
- 3.3 Node address (node ID)
- 3.4 Identifiers of the process data objects
- 3.5 Cycle time (CAN2_OUT/CAN3_OUT)
- 3.6 Delay time (CAN2_OUT/CAN3_OUT)
- 3.7 Synchronisation
- 3.8 Reset node
- 3.9 System bus management
- 3.10 Mapping indexes to codes
- 3.11 Remote parameterisation (gateway function)
- 3.12 Monitoring processes
- 3.13 Diagnostics
- 4 Configuration (AIF interface)
- 5 Configuration (FIF interface)
- 6 Configuration (CAN-AUX system bus interface)
- 7 CAN system blocks
- 8 FIF-CAN system blocks (only Drive PLC)
- 9 CAN-AUX system blocks (only ECSxA)
- 10 LenzeCanDrv.lib function library
- 10.1 Overview
- 10.2 Version identifiers of the function library
- 10.3 L_CanInit - initialising the CAN driver
- 10.4 L_CanClose - deactivating the CAN driver
- 10.5 L_CanGetStatus - querying the driver status
- 10.6 L_CanGetRelocCobId - querying the COB-ID range
- 10.7 L_CanPdoTransmit - transmitting a CAN object
- 10.8 L_CanPdoReceive - receiving a CAN object
- 11 LenzeCanDSxDrv.libfunction library
- 11.1 Overview
- 11.2 Version identifiers of the function library
- 11.3 L_CanDSxInitIndexCode - Configuration of index mapping
- 11.4 L_CanDSxOpen - initialising the CanDSx driver
- 11.5 L_CanDSxClose - deactivating the index mapping
- 11.6 L_CanDSxOpenHeartBeat - initialising a "Heartbeat"
- 11.7 L_CanDSxHeartBeat - carrying out a "Heartbeat"
- 11.8 L_CanDSxCloseHeartBeat - deactivating the "Heartbeat"
- 11.9 L_CanDSxOpenNodeGuarding - initialising the "Node Guarding"
- 11.10 L_CanDSxNodeGuarding - carrying out a "Node guarding"
- 11.11 L_CanDSxCloseNodeGuarding - deactivating the "Node Guarding"
- 12 Index
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