Lenze Drive PLC - Preface and General Information; About this Manual; Conventions Used in this Manual

System bus (CAN) with Servo PLC & Drive PLC
Preface and general information
1-1
l
PLC-Systembus EN 1.1
1 Preface and general information
1.1 About this Manual
This Manual contains information about the system bus interface of
the 9300 Servo PLC and Drive PLC.
Chapte
r
Contents
2 General information about the system bus (CAN) ^ 2-1
Configuration
3
Integrated system bus interface ^ 3-1
4
Optional system bus interface via automation interface (AIF)
and an appropriate fieldbus module (e.g. 2175)
^ 4-1
5
Optional system bus interface via function interface (FIF)
1
and an appropriate function module (e.g. system bus CAN I/O)
^ 5-1
System blocks
6
CAN objects (CAN1_IO ... CAN3_IO)
^
6
1
6
CAN synchronisation (CAN_Synchronization)
^ 6-1
CAN management (CAN_Management)
FIF CAN system blocks (Drive PLC only)
7
CAN objects (FIF_CAN1_IO ... FIF_CAN3_IO)
^ 7-1
7
CAN management (FIF_CAN_Management)
^
7
1
LenzeCanDrv.lib function library (free CAN objects)
8 Functions ^ 8-1
9 Function blocks ^ 9-1
1
Only with Drive PLC
1.1.1 Conventions used in this Manual
This Manual uses the following conventions to distinguish between different types of information:
Variable identifiers
are written in italics in the explanation:
• “Use wDrvNr ...”
Tip!
Information about the conventions used for the variables of theLenzesystem blocks, function blocks
and functions can be found in the appendix of the DDS online documentation “Introduction into
IEC1131-3 programming”. The conventions ensure universal and uniform labelling and make
reading the PLC program easier.
Lenze functions/function blocks
can be recognized by their names. They always begin with an “L_”:
• “The function L_CanInit...”
• “The FB L_CanPdoTransmit...”
Program listings
are written in “Courier”, keywords are printed in bold:
• “IF(ReturnValue < 0)THEN...”
Show/Hide Bookmarks