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
General information
2−5
l
PLC−Systembus EN 2.0
2.4.2 User data
Via the user data area of the CAN telegram, three different types of data are transported:
Data type Information
Network management data Information on the structure of communication via the CAN network. Chapter 2.5(^ 2−6)
Process data Process data are data for control−oriented concerns, e. g. setpoints and actual
values.
· Process data are transmitted as so−called PDOs (Process Data Objects) with a
high priority.
· Process data are processed more quickly by the PLC as parameter data.
· The transmission and reception of the process data is effected by the use of
specific system blocks or the free CAN objects:
Chapter 2.6(^ 2−7)
CAN
(integrated
system bus interface)
SB CAN1_IO for cyclic process data (sync−controlled)
9300 Servo PLC:
Drive PLC:
ECSxA:
Chapter 7.1(^ 7−1)
Chapter 7.2(^ 7−6)
Chapter 7.2(^ 7−6)
SB CAN2_IO for event− or time−controlled process data Chapter 7.4(^ 7−14)
SB CAN3_IO for event− or time−controlled process data Chapter 7.5(^ 7−17)
XCAN
(automation interface)
SB AIF1_IO_AutomationInterface
for cyclic process data (sync−controlled)
See Manual
· 9300 Servo PLC
· Drive PLC
· ECSxA
SB AIF2_IO_AutomationInterface
for event− or time−controlled process data
SB AIF3_IO_AutomationInterface
for event− or time−controlled process data
FIF−CAN
(function interface,
Drive PLC only!
SB FIF_CAN1_IO for cyclic process data (sync−controlled) Chapter 8.1(^ 8−1)
SB FIF_CAN2_IO for event− or time−controlled process data Chapter 8.2(^ 8−1)
SB FIF_CAN3_IO for event− or time−controlled process data Chapter 8.3(^ 8−1)
CAN−AUX
(integrated
system bus interface,
ECSxA only)
SB CANaux1_IO for cyclic process data (sync−controlled) Chapter 9.1(^ 9−1)
SB CANaux2_IO for event− or time−controlled process data Chapter 9.2(^ 9−1)
SB CANaux3_IO for event− or time−controlled process data Chapter 9.3(^ 9−1)
Free CAN objects By using the functions/function blocks of the LenzeCanDrv.lib function
library, so−called "free CAN objects" additionally can be added to the
fixedly integrated CAN objects.
Chapter 10(^ 10−1)
Parameter data For Lenze devices, parameter data are the so−called codes.
· Parameter settings for instance are carried out in the case of a one−time
setting of the system during commissioning, or in the case of a material
change of the production machine.
· Parameter data are transferred as so−called SDOs (Service Data Objects) via
the CAN network and are acknowledged by the receiver, i. e. the transmitter
receives a feedback on whether the transmission was successful.
Chapter 2.7(^ 2−11)