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
Index
12−4
L
PLC−Systembus EN 2.0
M
Mapping indexes to codes, CAN interface, 3−8
Monitoring mechanisms, 2−21
"Heartbeat", 2−21
"Node Guarding", 2−22
Monitoring processes
AIF interface, 4−8
bus off, 4−9
fault messages, 4−9
time monitoring, 4−8
CAN interface, 3−11
bus−off, 3−11
fault messages, 3−12
time monitoring, 3−11
time−out during activated remote parameterisation, 3−12
CAN−AUX interface, 6−9
bus−off, 6−9
fault messages, 6−10
time monitoring, 6−9
FIF interface, 5−9
bus−off, 5−9
fault messages, 5−10
time monitoring, 5−9
N
Network management (NMT), 2−6
command, 2−6
device address, 2−6
Netwotk status, 2−6
Node address (node ID)
AIF interface, 4−3
CAN interface, 3−3
CAN−AUX interface, 6−3
FIF interface, 5−3
Node Guarding, 2−22
Node ID, 2−3 , 6−3
P
Parameter data, 2−5 , 2−11
addressing (index/subindex), 2−13
command code, 2−12
data format, 2−14
identifiers, 2−11
reading parameters, 2−17
telegram structure, 2−11
transmission, 2−11
writing parameters, 2−15
PDOs, 2−5
Phase displacement, 7−25
Process data, 2−5
identifier, 2−10
sync telegram, 2−9
telegram structure, 2−10
transmission, 2−7
user data, 2−10
Process data channels, 2−7
Process Data Objects, 2−5
R
Read request, 2−12
Read response, 2−12
Reading parameters, 2−17
Receive status, 10−13
Remote parameterisation (gateway function), CAN interface,
3−10
Reset node
AIF interface, 4−8
CAN interface, 3−8
CAN−AUX interface, 6−8
FIF interface, 5−8
S
Safety information, layout, More notes, 1−4
Safety instructions, layout, warning of material damage, 1−4
SDOs, 2−5
Service Data Objects, 2−5
Subindex, 2−13
Sync telegram, 2−9
Synchronisation
AIF interface, 4−7
CAN interface, 3−7
CAN sync identifiers, 3−7
CAN sync response, 3−7
CAN sync Tx transmission cycle, 3−7
CAN−AUX interface, 6−7
CANaux sync identifiers, 6−7
CANaux sync response, 6−7
CANaux sync Tx transmission cycle, 6−7
FIF interface, 5−7
FIF−CAN sync identifier, 5−7
FIF−CAN sync response, 5−7
FIF_CAN sync Tx transmission cycle, 5−7
XCAN sync identifier, 4−7
XCAN sync response, 4−7
XCAN sync Tx transmission cycle, 4−7
Synchronisation cycle, 7−25
Synchronisation time, 7−24