Lenze Drive PLC Developer Studio 9300 User Manual
L
Manual
Global Drive
PLC Developer Studio
Global Drive
9300 Servo PLC
This documentation applies to the following Lenze PLC devices:
Type designation As from hardware version As from software version
9300 Servo PLC EVS93XX−xl 7A 8.0
9300 Servo PLC EVS93XX−xT 7A 8.0
What’s new?
Version Changes
1.4 07/2000 Revised edition for the 9300 Servo PLC as of software version V1.0
2.0 07/2001 Revised edition for the 9300 Servo PLC as of software version V2.0
3.0 01/2003 Revised edition for the 9300 Servo PLC as of software version V6.0
4.0/4.1 08/2006 Revised edition for the 9300 Servo PLC as of software version V7.0
5.0 10/2010 Revised edition for the 9300 Servo PLC as of software version V8.0
Important note:
The software is supplied to the user as described in this document. Any risks resulting from its quality or use remain the responsibility of the
user. The user must provide all safety measures protecting against possible maloperation.
We do not take any liability for direct or indirect damage, e.g. profit loss, order loss or any loss regarding business.
2010 Lenze Drive Systems GmbH
No part of this documentation may be copied or made available to third parties without the explicit written approval of Lenze Drive Systems
GmbH.
All information given in this documentation has been carefully selected and tested for compliance with the hardware and software described.
Nevertheless, discrepancies cannot be ruled out. We do not accept any responsibility or liability for any damage that may occur. Required
correction will be included in updates of this documentation.
All product names mentioned in this documentation are trademarks of the corresponding owners.
Version 5.0 10/2010
9300 Servo PLC
Contents
1 Preface and general information 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 About this Manual 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Conventions used in this Manual 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 System block descriptions 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.3 Pictographs in this Manual 1−2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4 Terminology used 1−2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 System block introduction 1−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 System block principle 1−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Node numbers 1−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3 Access via system variables 1−5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4 Access via absolute addresses 1−5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.5 Definition of inputs/outputs 1−6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6 Linking of system blocks with DDS 1−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.7 Signal types and scalings 1−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 System blocks 2−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 AIF1_IO_AutomationInterface (node number 41) 2−2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Inputs_AIF1 2−2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Outputs_AIF1 2−5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 AIF2_IO_AutomationInterface (node number 42) 2−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Inputs_AIF2 2−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Outputs_AIF2 2−9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 AIF3_IO_AutomationInterface (node number 43) 2−11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 Inputs_AIF3 2−11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 Outputs_AIF3 2−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 AIF_IO_Management (node number 161) 2−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Inputs_AIF_Management 2−15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Outputs_AIF_Management 2−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 ANALOG1_IO (node number 11) 2−18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1 Inputs_ANALOG1 (analog input) 2−18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.2 Outputs_ANALOG1 (analog output) 2−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 ANALOG2_IO (node number 12) 2−20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1 Inputs_ANALOG2 (analog input) 2−20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.2 Outputs_ANALOG2 (analog output) 2−20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CAN1_IO (node number 31) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CAN2_IO (node number 32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CAN3_IO (node number 33) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CAN_Management (node number 101) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CAN_Synchronization (node number 102) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
See "System bus (CAN) for Lenze PLCs" Manual.
L 9300 Servo PLC EN 5.0
i
9300 Servo PLC
Contents
2.7 DCTRL_DriveControl (node number 121) 2−21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.1 Inputs_DCTRL 2−22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.2 Outputs_DCTRL 2−22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.3 Quick stop (QSP) 2−23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.4 Operation disabled (DISABLE) 2−23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.5 Controller inhibit (CINH) 2−24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.6 Setting TRIP (TRIP−SET) 2−24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.7 Resetting TRIP (TRIP−RESET) 2−25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.8 Output of digital status signals 2−25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.9 Transfer of status/control word via AIF 2−27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8 DFIN_IO_DigitalFrequency (node number 21) 2−28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8.1 Inputs_DFIN 2−28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9 DFOUT_IO_DigitalFrequency (node number 22) 2−35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9.1 Inputs_DFOUT / Outputs_DFOUT 2−35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10 DIGITAL_IO (node number 1) 2−39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10.1 Inputs_DIGITAL (digital inputs) 2−39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10.2 Outputs_DIGITAL (digital outputs) 2−40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11 FCODE_FreeCode (node number 141) 2−41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12 MCTRL_MotorControl (node number 131) 2−44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.1 Inputs_MCTRL 2−45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.2 Outputs_MCTRL 2−47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.3 Current controller 2−48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.4 Torque setpoint / additional torque setpoint 2−49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.5 Torque limitation 2−50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.6 Maximum speed 2−51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.7 Speed controller 2−52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.8 Torque control with speed limitation 2−53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.9 Speed setpoint limitation 2−54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.10 Phase controller 2−54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.11 Quick stop (QSP) 2−55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.12 Field weakening 2−56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.13 Switching frequency changeover 2−56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.14 Feedback systems 2−57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.15 Touch probe (TP) 2−58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.16 Manual adaptation of motor data 2−60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.17 Monitoring 2−62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.17.7 LP1 − monitoring of the motor phases 2−72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.17.17 PL − monitoring of the rotor position adjustment 2−81 . . . . . . . . . . . . . . . . . . . . . . . . .
2.13 MCTRL_AUX_HighResFeedback (node number 181) 2−84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.13.1 Inputs_MCTRL_AUX_HighResFeedback 2−84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.13.2 Outputs_MCTRL_AUX_HighResFeedback 2−84 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.14 STATEBUS_IO (node number 51) 2−85 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15 SYSTEM_FLAGS (system flags, node number 151) 2−86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15.1 Inputs SYSTEM_FLAGS 2−86 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15.2 Outputs SYSTEM_FLAGS 2−87 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
9300 Servo PLC EN 5.0
L
9300 Servo PLC
Contents
3 Appendix 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 PLC functionality 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Extendability/networking 3−2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Memories 3−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 Retain memory 3−4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 Persistent memory 3−5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3 Downloading data 3−6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 System POUs 3−7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 System error messages 3−8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 Overview of system error messages, error sources and responses 3−9 . . . . . . . . . . . . . . . . . . . . . .
3.5.2 Response and its effects on the drive 3−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3 System error message reset 3−12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.4 Causes and remedies 3−13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.5 Fault analysis via the fault memory 3−17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.6 Fault analysis via the LED display of the PLC 3−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.7 Fault analysis via the 9371BB keypad 3−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.8 Fault analysis via the LECOM status word C0150 3−19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Code table 3−20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.1 Temporary codes 3−52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.2 RAM access via codes 3−52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7 Attribute table 3−55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 Index 4−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L 9300 Servo PLC EN 5.0
iii
9300 Servo PLC
Contents
iv
9300 Servo PLC EN 5.0
L
Preface and general information
1 Preface and general information
1.1 About this Manual
This Manual describes the system block functions which can be selected and parameterised in the
control configuration of the Drive PLC Developer Studio (DDS) for 9300 Servo PLC.
1.1.1 Conventions used in this Manual
This Manual uses the following conventions to distinguish between different types of information:
Information type Distinction (in text) Example
System block name bold The SB DIGITAL_IO...
System (block) variable identifier italics The input DIGIN_bIn1_b...
9300 Servo PLC
Tip!
Information about the conventions used for variable names of Lenze system blocks, function blocks
and functions can be obtained from the appendix of the DDS online documentation "Introduction
into IEC 61131−3 programming". The conventions ensure universal and uniform naming and support
the readability of PLC programs.
1.1.2 System block descriptions
All system block descriptions given in this Manual have the same structure:
Headline with SB identifier
SB function and node number
Short description of the SB and its most important features
System block chart including all corresponding variables
Input variables
Output variables
Table giving information about input and output variables:
Identifier
Data type
Signal type
Address
Display code
Display format
Info
l
Detailed SB description
9300 Servo PLC EN 5.0
1−1
9300 Servo PLC
Preface and general information
1.1.3 Pictographs in this Manual
Pictographs
used
Warning of material
damage
More notes Tip!
1.1.4 Terminology used
Term In this Manual used for
AIF Automation interface
DDS Drive PLC Developer Studio
FIF Function interface
GDC Global Drive Control (parameter setting program from Lenze)
SB System block
System bus System bus (CAN): Lenze standard bus system similar to CANopen
Signal words
Stop! Warns of potential damage to material.
Note!
Possible consequences if disregarded:
Damage of the PLC or its environment
Indicates a tip or note.
.
1−2
9300 Servo PLC EN 5.0
l
1.2 System block introduction
For a long time, Lenze has followed the principle of describing controller functions with the aid of
function blocks (FBs). This principle can also be found in the IEC 61131−3 standard.
Functions which can be used as software functions in projects are stored in function libraries
as function blocks or functions.
In addition, quasi−hardware functions are available as system blocks (SBs).
1.2.1 System block principle
The system−block principle can be explained by means of a PLC system in a rack:
The rack contains the CPU, digital I/Os, analog I/Os, counter card, positioning card, etc. as
additional cards:
9300 Servo PLC
Preface and general information
CPU
The CPU can directly access the additional cards and process the resulting information.
Additional cards have fixed addresses for access.
With Lenze PLC controllers, system blocks can be compared with these additional cards!
System blocks are special (hardware) function blocks permanently integrated into the
run−time system of the PLC.
SBs can address real hardware.
SBs are assigned/identified through so−called node numbers. (^ 1−4)
SB inputs and outputs are accessed via system variables or absolute memory addresses.
(^ 1−5)
Inputs/outputs are always classified from the program’s point of view. (^ 1−6)
Required SBs must be explicitly linked to the project via the control configuration of DDS.
(^ 1−7)
xxxxxx
x = Additional cards
l
9300 Servo PLC EN 5.0
1−3
9300 Servo PLC
Preface and general information
1.2.2 Node numbers
The system blocks of the 9300 Servo PLC carry the following node numbers:
Node number System block Notes
1 DIGITAL_IO Digital inputs/outputs
11 ANALOG1_IO Analog inputs/outputs 1
12 ANALOG2_IO Analog inputs/outputs 2
21 DFIN_IO_DigitalFrequency Digital frequency input
22 DFOUT_IO_DigitalFrequency Digital frequency output
31 CAN1_IO
32 CAN2_IO
33 CAN3_IO
41 AIF1_IO_AutomationInterface
42 AIF2_IO_AutomationInterface
43 AIF3_IO_AutomationInterface
51 STATEBUS_IO State bus
60 OSC_Oscilloscope Oscilloscope function
101 CAN_Management System bus (CAN) management
102 CAN_Syncronization System bus (CAN) synchronisation
121 DCTRL_DriveControl Device control
131 MCTRL_MotorControl Motor control
141 FCODE_FreeCodes Free codes
151 SYSTEM_FLAGS System flags
161 AIF_IO_Management Automation interface management
171 VAR_PERSISTENT Persistent variables
1
SBs for system bus (CAN) are described in the "System bus (CAN) for Lenze PLC devices" manual.
The node number is part of the absolute SB address (see chapter 2). (^ 1−5)
181 MCTRL_AUX_HighResFeedback High−resolution encoder signal
System bus (CAN)
Automation interface
1
1
1
1−4
9300 Servo PLC EN 5.0
l
1.2.3 Access via system variables
You can use the system variables of a system block in your project after the system block has been
integrated into the control configuration of the DDS.
Open the input assistance in the DDS editors via <F2> to get a listing of all available system
variables:
9300 Servo PLC
Preface and general information
This Manual lists the system variables in the table for the corresponding system block:
Variable Data type Signal type Address Display
DIGIN_bIn1_b
... ... ...
DIGIN_bIn8_b %IX1.0.7 C0443/8
Example: Table with SB DIGITAL_IO inputs of the Drive PLC
Bool Binary
%IX1.0.0 C0443/1
1.2.4 Access via absolute addresses
System block inputs and outputs can also be accessed via absolute addresses according to the
IEC61131−3 standard:
For inputs use: For outputs use:
%IXa.b.c %QXa.b.c
This Manual lists the absolute addresses in the table for the corresponding system block:
Variable Data type Signal type Address Display
DIGIN_bIn1_b
... ... ...
DIGIN_bIn8_b %IX1.0.7 C0443/8
Example: Table with SB DIGITAL_IO inputs of the Drive PLC
Bool Binary
%IX1.0.0 C0443/1
code
code
Display
format
bin
Display
format
bin
Note
a = node number
b = word address
c = bit address
Note
l
9300 Servo PLC EN 5.0
1−5
9300 Servo PLC
Preface and general information
1.2.5 Definition of inputs/outputs
The application program is connected with the hardware by linking system blocks with program
organisation units (POUs):
SB-Output SB-Input
POU-Input POU-Output
SB
POU
Fig. 1−1 Principle: Linking of system blocks with a program organisation unit (POU)
Tip!
Inputs and outputs are always classified from the program’s point of view.
Logic SB inputs are hardware outputs of the PLC.
Logic SB outputs are hardware inputs of the PLC.
Example: System block DIGITAL_IO of the 9300 Servo PLC
If you want to use the digital input 1 and the digital output 1 of the 9300 Servo PLC, proceed as
follows:
1. Link the SB DIGITAL_IO explicitly with the DDS control configuration.
2. Access to digital input 1:
Assign the system variable DIGIN_bIn1_b to a POU input.
3. Access to digital output 1:
Assign the system variable DIGOUT_bOut1_b to a POU output.
POU
POU-OUT
SB-IN
SB-OUT
POU-IN
0
1
DCTRL -X5/28
DIGIN_bCInh_b
DIGIN_bIn1_b
DIGIN_bIn2_b
DIGIN_bIn3_b
DIGIN_bIn4_b
DIGIN_bIn5_b
C0443
DIGIN
X5
28
E1
C0114/1...5
E2
E3
1
E4
E5
DIGOUT_bOut1_b
DIGOUT_bOut2_b
DIGOUT_bOut3_b
DIGOUT_bOut4_b
SB
(^ 1−7)
C0444/1
C0444/2
C0444/3
C0444/4
DIGOUT
C0118/1...4
0
1
1
X5
A1
A2
A3
A4
Fig. 1−2 Principle: Linking of the 9300 Servo PLC system block DIGITAL_IO with a POU
Tip!
According to the IEC61131−3 standard, only one copy of the digital input 1 and the digital output 1
may be transferred.
1−6
9300 Servo PLC EN 5.0
l
1.2.6 Linking of system blocks with DDS
The system blocks required must be explicitly linked to the project via the control configuration of the
DDS.
The control configuration is placed as an object in the Resources tab in the Object organiser.
The control configuration lists all inputs and outputs including the identifiers of the
corresponding I/O variable, the absolute address and the data type of the I/O variable for
every linked SB.
9300 Servo PLC
Preface and general information
Identifier of the I/O variable
Absolute address
Data type of the I/O variable
Fig. 1−3 Example: Control configuration for 9300 Servo PLC with linked SB DIGITAL_IO
Tip!
The control configuration provides a context menu for adding and deleting SBs which can be
activated via the right mouse key.
l
9300 Servo PLC EN 5.0
1−7
9300 Servo PLC
Preface and general information
1.2.7 Signal types and scalings
Most inputs and outputs of Lenze function blocks/system blocks can be assigned to a certain signal
type. We distinguish between digital, analog, position and speed signals.
The identifier of the corresponding input/output variable has an ending (starting with an underscore).
It indicates the signal type.
Signal type Ending Memory
Analog _a (analog) 16 bits 100 % 16384 H
Digital _b (binary) 8 bits 0 FALSE; 1 TRUE G
Phase difference or speed
Phase−angle or position _p (position) 32 bits 1 motor revolution 65536 E
_v (velocity) 16 bits 15000 rpm 16384 F
Phase difference/speed ref. to 1 ms
Scaling example:
Speed (on motor side) + 15000 [rpm] +
1 motor revolution + 65536 [inc]
Variable value (..._v) +
space
Direction (0 clockwise rotation; 1 counter−clockwise rotation)
No. of motor revolutions (0 ... 32767)
Phase angle or position (0 ... 65535)
Scaling
(external value º internal value)
15000
60 [s]
15000
@ 65536 [inc] +
60 [s]
High Word Low Word 031
15000
60000 [ms]
@ 65536 [inc] + 16384
Previous
identification
inc
ƪ
ƫ
ms
Note!
Due to their scaling, analog signals have an asymmetrical resolution range (−200 % ... +199.99 %):
External value: −200 % −100 % 0 +100 % +199.99 %
Internal value: −32768 −16384 0 +16384 +32767
1−8
9300 Servo PLC EN 5.0
l
2 System blocks
The following sections inform about the system blocks of the basic unit.
9300 Servo PLC
System blocks
L
9300 Servo PLC EN 5.0
2−1
9300 Servo PLC
System blocks
2.1 AIF1_IO_AutomationInterface (node number 41)
2.1 AIF1_IO_AutomationInterface (node number 41)
2.1.1 Inputs_AIF1
This SB is used as an interface for input signals (e.g. setpoints/actual values) from attached fieldbus
modules (e.g. INTERBUS, PROFIBUS−DP).
The process image is
– created in the cyclic task in a fixed time interval of 10 ms.
– created in an interval task within the time set for this task.
– read at the beginning of the task and written at its end.
Tip!
Please observe the Operating Instructions for the attached fieldbus module.
Automation
Interface
Inputs_AIF1
Byte
1
Controlword
Byte
2
Byte
3
Byte
4
Byte
5
Byte
6
Byte
7
Byte
8
16 Bit
16 binary
signals
16 Bit
16 Bit
C0855/1
16 binary
signals
16 Bit
C0855/2
16 binary
signals
C0856/1
C0856/2
C0856/3
AIF1_wDctrlCtrl
AIF1_bCtrlB0_b
AIF1_bCtrlB1_b
AIF1_bCtrlB2_b
AIF1_bCtrlQuickstop_b
AIF1_bCtrlB4_b
AIF1_bCtrlB5_b
AIF1_bCtrlB6_b
AIF1_bCtrlB7_b
AIF1_bCtrlDisable_b
AIF1_bCtrlCInhibit_b
AIF1_bCtrlTripSet_b
AIF1_bCtrlTripReset_b
AIF1_bCtrlB12_b
AIF1_bCtrlB13_b
AIF1_bCtrlB14_b
AIF1_bCtrlB15_b
AIF1_nInW1_a
AIF1_nInW2_a
AIF1_bInB0_b
…
AIF1_bInB15_b
AIF1_nInW3_a
AIF1_bIn16_b
…
AIF1_bIn31_b
Fig. 2−1 Inputs_AIF1
2−2
16 Bit
LowWord
16 Bit
HighWord
9300 Servo PLC EN 5.0
AIF1_dnInD1_p
C0857
L
9300 Servo PLC
System blocks
2.1 AIF1_IO_AutomationInterface (node number 41)
System variables
Variable Data type Signal type Address Display
AIF1_wDctrlCtrl Word − %IX41.0 C0136/3 hex
AIF1_bCtrlB0_b
AIF1_bCtrlB1_b
AIF1_bCtrlB2_b
AIF1_bCtrlQuickstop_b
AIF1_bCtrlB4_b
AIF1_bCtrlB5_b
AIF1_bCtrlB6_b
AIF1_bCtrlB7_b
AIF1_bCtrlDisable_b
AIF1_bCtrlCInhibit_b
AIF1_bCtrlTripSet_b
AIF1_bCtrlTripReset_b
AIF1_bCtrlB12_b
AIF1_bCtrlB13_b
AIF1_bCtrlB14_b
AIF1_bCtrlB15_b
AIF1_nInW1_a
AIF1_nInW2_a
AIF1_nInW3_a
AIF1_bInB0_b
...
AIF1_bInB15_b
AIF1_bInB16_b
...
AIF1_bInB31_b
AIF1_dnInD1_p Double integer Position %ID41.1 C0857 dec [inc]
Bool Binary
Integer Analog
Bool Binary
%IX41.0.0
%IX41.0.1
%IX41.0.2
%IX41.0.3
%IX41.0.4
%IX41.0.5
%IX41.0.6
%IX41.0.7
%IX41.0.8
%IX41.0.9
%IX41.0.10
%IX41.0.11
%IX41.0.12
%IX41.0.13
%IX41.0.14
%IX41.0.15
%IW41.1 C0856/1
%IW41.2 C0856/2
%IW41.3 C0856/3
%IX41.2.0
...
%IX41.2.15
%IX41.3.0
...
%IX41.3.15
code
C0136/3 bin
C0855/1
C0855/2
Display
format
dec [%]
hex
Note
L
9300 Servo PLC EN 5.0
2−3
9300 Servo PLC
System blocks
2.1 AIF1_IO_AutomationInterface (node number 41)
User data
The received 8 bytes of user data are assigned to several variables of different data types
simultaneously. Thus the data can be evaluated in the PLC program as
binary information (1 bit)
control word/quasi−analog value (16 bits)
phase information (32 bits)
according to the requirements.
Byte Variable (1 bit) Variable (16 bits) Variable (32 bits)
1, 2
Notes:
3, 4
AIF1_bInB0_b
AIF1_bInB1_b
AIF1_bInB2_b
AIF1_bCtrlQuickstop_b
AIF1_bInB4_b
...
AIF1_bInB7_b
AIF1_bCtrlDisable_b
AIF1_bCtrlCInhibit_b
AIF1_bCtrlTripSet_b
AIF1_bCtrlTripReset_b
AIF1_bInB12_b
...
AIF1_bInB15_b
Drive PLC:
All variables assigned to byte 1/2 can be freely used in the PLC program.
9300 Servo PLC:
The assignment of the controller−internal control word to byte 1/2 is not a fixed assignment.
Byte 1/2 can, however, be used to write the signals for the quick stop (QSP), DISABLE, CINH, TRIP−SET and
TRIP−RESET functions to the SB DCTRL_DriveControl.
– To do this, connect the variable AIF1_wDctrlCtrl with the variable DCTRL_wAIF1Ctrl of the SB
DCTRL_DriveControl.
The signals can also be read and processed via the following variables:
– AIF1_bCtrlQuickstop_b
– AIF1_bCtrlDisable_b
– AIF1_bCtrlCInhibit_b
– AIF1_bCtrlTripSet_b
– AIF1_bCtrlTripReset_b
AIF1_wDctrlCtrl
AIF1_nInW1_a
2−4
5, 6 AIF1_bInB0_b
...
AIF1_bInB15_b
7, 8 AIF1_bInB16_b
...
AIF1_bInB31_b
AIF1_nInW2_a
AIF1_nInW3_a
9300 Servo PLC EN 5.0
AIF1_dnInD1_p
L
9300 Servo PLC
System blocks
2.1 AIF1_IO_AutomationInterface (node number 41)
2.1.2 Outputs_AIF1
This SB is used as an interface for output signals (e.g. setpoints/actual values) to attached fieldbus
modules (e.g. INTERBUS, PROFIBUS−DP).
The process image is
– created in the cyclic task in a fixed time interval of 10 ms.
– created in an interval task within the time set for this task.
– read at the beginning of the task and written at its end.
Tip!
Please observe the Operating Instructions for the attached fieldbus module.
Outputs_AIF1
Fig. 2−2 Outputs_AIF1
AIF1_wDctrlStat
AIF1_nOutW1_a
AIF1_nOutW2__a
AIF1_bFDO0_b
…
AIF1_bFDO15_b
AIF1_nOutW3_a
AIF1_bFDO16_b
…
AIF1_bFDO31_b
AIF1_dnOutD1_p
C0858/1
C0858/2
C0858/3
C0859
16 Bit
16 Bit
16 Bit
C0151/4
16 binary
signals
16 Bit
C0151/4
16 binary
signals
16 Bit
LowWord
16 Bit
HighWord
Byte
Byte
Byte
Byte
Byte
Byte
Byte
Byte
1
2
3
4
5
6
7
8
Automation
Interface
L
9300 Servo PLC EN 5.0
2−5
9300 Servo PLC
System blocks
2.1 AIF1_IO_AutomationInterface (node number 41)
System variables
Variable Data type Signal type Address Display
AIF1_wDctrlStat Word − %QW41.0 − −
AIF1_nOutW1_a
AIF1_nOutW2_a %QW41.2 C0858/2
AIF1_nOutW3_a %QW41.3 C0858/3
AIF1_bFDO0_b
.. ...
AIF1_bFDO15_b %QX41.2.15
AIF1_bFDO16_b %QX41.3.0
.. ...
AIF1_bFDO31_b %QX41.3.15
AIF1_dnOutD1_p Double integer Position %QD41.1 C0859 dec [inc]
Integer Analog
Bool Binary
%QW41.1 C0858/1
%QX41.2.0
code
C0151/4 hex
Display
format
dec [%]
Note
Display code in hex
as double word
User data
The 8 bytes of user data to be sent can be written to via several variables of different data types
simultaneously. Thus the data can be transferred by the PLC program as
binary information (1 bit)
status word/quasi−analog value (16 bits)
phase information (32 bits)
according to the requirements.
Byte Variable (1 bit) Variable (16 bits) Variable (32 bits)
1, 2
AIF1_wDctrlStat
Notes:
Drive PLC:
All variables assigned to byte 1/2 can be written to by the PLC program.
9300 Servo PLC:
Bytes 1 and 2 can be used to transfer the status word from the SB DCTRL_DriveControl.
To do this, connect the variable DCTRL_wStat of the SB DCTRL_DriveControl with the variable AIF1_wDctrlStat.
In addition to signals such as IMP and CINH, the SB DCTRL_DriveControl status word contains some freely
assignable signals which can be written to via the variables DCTRL_bStateB.._b of the SB DCTRL_DriveControl.
3, 4
5, 6 AIF1_bFDO0_b
...
AIF1_bFDO15_b
7, 8 AIF1_bFDO16_b
...
AIF1_bFDO31_b
AIF1_nOutW1_a
AIF1_nOutW2_a
AIF1_dnOutD1_p
AIF1_nOutW3_a
Tip!
Avoid simultaneous overwriting via different variable types to ensure data consistency.
Thus bytes 5 and 6 should only be written to
– by the variable AIF1_dnOutD1_p,
– by the variable AIF1_nOutW2_a or
– by the variables AIF1_bFDO0_b ... AIF1_bFDO15_b.
2−6
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.2 AIF2_IO_AutomationInterface (node number 42)
2.2 AIF2_IO_AutomationInterface (node number 42)
2.2.1 Inputs_AIF2
Automation interface (node number 42)
This SB is used as an interface for input signals (e.g. setpoints/actual values) from attached fieldbus
modules (e.g. INTERBUS, PROFIBUS−DP).
The process image is
– created in the cyclic task in a fixed time interval of 10 ms.
– created in an interval task within the time set for this task.
– read at the beginning of the task and written at its end.
Tip!
Please observe the Operating Instructions for the attached fieldbus module.
Fig. 2−3 Inputs_AIF2
Automation
Interface
Inputs_AIF2
Byte
1
Byte
2
Byte
3
Byte
4
Byte
5
Byte
6
Byte
7
Byte
8
16 Bit
16 binary
signals
16 Bit
16 binary
signals
16 Bit
LowWord
16 Bit
HighWord
16 Bit
16 Bit
AIF2_nInW1_a
AIF2_bInB0_b
...
AIF2_bInB15_b
AIF2_nInW2_a
AIF2_bInB16_b
...
AIF2_bInB31_b
AIF2_dnInD1_p
AIF2_nInW3_a
AIF2_nInW4_a
L
9300 Servo PLC EN 5.0
2−7
9300 Servo PLC
System blocks
2.2 AIF2_IO_AutomationInterface (node number 42)
System variables
Variable Data type Signal type Address Display code Display
AIF2_nInW1_a
AIF2_nInW2_a %IW42.1
AIF2_nInW3_a %IW42.2
AIF2_nInW4_a %IW42.3
AIF2_bInB0_b
... ...
AIF2_bInB15_b %IX42.0.15
AIF2_bInB16_b %IX42.1.0
... ...
AIF2_bInB31_b %IX42.1.15
AIF2_dnInD1_p Double integer Position %ID42.0
Integer Analog
Bool Binary
%IW42.0
%IX42.0.0
format
Note
User data
The 4 first bytes of the received 8 bytes of user data are assigned to several variables of different data
types simultaneously. Thus the data can be evaluated in the PLC program as
binary information (1 bit)
quasi−analog value (16 bits)
angle information (32 bits)
according to the requirements.
Byte Variable (1 bit) Variable (16 bits) Variable (32 bits)
1, 2 AIF2_bInB0_b
...
AIF2_bInB15_b
3, 4 AIF2_bInB16_b
...
AIF2_bInB31_b
5, 6
AIF2_nInW1_a
AIF2_dnInD1_p
AIF2_nInW2_a
AIF2_nInW3_a
7, 8
AIF2_nInW4_a
2−8
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.2 AIF2_IO_AutomationInterface (node number 42)
2.2.2 Outputs_AIF2
This SB is used as an interface for output signals (e.g. setpoints/actual values) to attached fieldbus
modules (e.g. INTERBUS, PROFIBUS−DP).
The process image is
– created in the cyclic task in a fixed time interval of 10 ms.
– created in an interval task within the time set for this task.
– read at the beginning of the task and written at its end.
Tip!
Please observe the Operating Instructions for the attached fieldbus module.
Outputs_AIF2
AIF2_nOutW1_a
AIF2_bFDO0_b
...
AIF2_bFDO15_b
AIF2_nOutW2_a
AIF2_bFDO16_b
...
AIF2_bFDO31_b
AIF2_dnOutD1_p
AIF2_nOutW3_a
AIF2_nOutW4_a
16 Bit
16 binary
signals
16 Bit
16 binary
signals
16 Bit
LowWord
16 Bit
HighWord
16 Bit
16 Bit
Byte
Byte
Byte
Byte
Byte
Byte
Byte
Byte
1
2
3
4
5
6
7
8
Automation
Interface
Fig. 2−4 Outputs_AIF2
L
9300 Servo PLC EN 5.0
2−9
9300 Servo PLC
System blocks
2.2 AIF2_IO_AutomationInterface (node number 42)
System variables
Variable Data type Signal type Address Display code Display
AIF2_nOutW1_a
AIF2_nOutW2_a %QW42.1
AIF2_nOutW3_a %QW42.2
AIF2_nOutW4_a %QW42.3
AIF2_bFDO0_b
... ...
AIF2_bFDO15_b %QX42.0.15
AIF2_bFDO16_b %QX42.1.0
... ...
AIF2_bFDO31_b %QX42.1.15
AIF2_dnOutD1_p Double integer Position %QD42.0
Integer Analog
Bool Binary
%QW42.0
%QX42.0.0
format
Note
User data
The first 4 bytes of the 8 bytes of user data to be sent can be written to via several variables of different
data types at the same time. Data can therefore be transferred by the PLC program as
binary information (1 bit)
quasi−analog value (16 bits)
angle information (32 bits)
according to the requirements.
Byte Variable (1 bit) Variable (16 bits) Variable (32 bits)
1, 2 AIF2_bFDO0_b
...
AIF2_bFDO15_b
3, 4 AIF2_bFDO16_b
...
AIF2_bFDO31_b
5, 6
AIF2_nOutW1_a
AIF2_dnOutD1_p
AIF2_nOutW2_a
AIF2_nOutW3_a
7, 8
AIF2_nOutW4_a
Tip!
Avoid simultaneous overwriting via different variable types to ensure data consistency.
Thus bytes 1 and 2 should only be written to
– by the variable AIF2_dnOutD1_p,
– by the variable AIF2_nOutW1_a or
– by the variables AIF2_bFDO0_b ... AIF2_bFDO15_b.
2−10
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.3 AIF3_IO_AutomationInterface (node number 43)
2.3 AIF3_IO_AutomationInterface (node number 43)
2.3.1 Inputs_AIF3
This SB is used as an interface for input signals (e.g. setpoints/actual values) from attached fieldbus
modules (e.g. INTERBUS, PROFIBUS−DP).
The process image is
– created in the cyclic task in a fixed time interval of 10 ms.
– created in an interval task within the time set for this task.
– read at the beginning of the task and written at its end.
Tip!
Please observe the Operating Instructions for the attached fieldbus module.
Fig. 2−5 Inputs_AIF3
Automation
Interface
Inputs_AIF3
Byte
1
Byte
2
Byte
3
Byte
4
Byte
5
Byte
6
Byte
7
Byte
8
16 Bit
16 binary
signals
16 Bit
16 binary
signals
16 Bit
LowWord
16 Bit
HighWord
16 Bit
16 Bit
AIF3_nInW1_a
AIF3_bInB0_b
...
AIF3_bInB15_b
AIF3_nInW2_a
AIF3_bInB16_b
...
AIF3_bInB31_b
AIF3_dnInD1_p
AIF3_nInW3_a
AIF3_nInW4_a
L
9300 Servo PLC EN 5.0
2−11
9300 Servo PLC
System blocks
2.3 AIF3_IO_AutomationInterface (node number 43)
System variables
Variable Data type Signal type Address Display code Display
AIF3_nInW1_a
AIF3_nInW2_a %IW43.1
AIF3_nInW3_a %IW43.2
AIF3_nInW4_a %IW43.3
AIF3_bInB0_b
... ...
AIF3_bInB15_b %IX43.0.15
AIF3_bInB16_b %IX43.1.0
... ...
AIF3_bInB31_b %IX43.1.15
AIF3_dnInD1_p Double integer Position %ID43.0
Integer Analog
Bool Binary
%IW43.0
%IX43.0.0
format
Note
User data
The 4 first bytes of the received 8 bytes of user data are assigned to several variables of different data
types simultaneously. Thus the data can be evaluated in the PLC program as
binary information (1 bit)
quasi−analog value (16 bits)
angle information (32 bits)
according to the requirements.
Byte Variable (1 bit) Variable (16 bits) Variable (32 bits)
1, 2 AIF3_bInB0_b
...
AIF3_bInB15_b
3, 4 AIF3_bInB16_b
...
AIF3_bInB31_b
5, 6
AIF3_nInW1_a
AIF3_dnInD1_p
AIF3_nInW2_a
AIF3_nInW3_a
7, 8
AIF3_nInW4_a
2−12
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.3 AIF3_IO_AutomationInterface (node number 43)
2.3.2 Outputs_AIF3
This SB is used as an interface for output signals (e.g. setpoints/actual values) to attached fieldbus
modules (e.g. INTERBUS, PROFIBUS−DP).
The process image is
– created in the cyclic task in a fixed time interval of 10 ms.
– created in an interval task within the time set for this task.
– read at the beginning of the task and written at its end.
Tip!
Please observe the Operating Instructions for the attached fieldbus module.
Outputs_AIF3
AIF3_nOutW1_a
AIF3_bFDO0_b
...
AIF3_bFDO15_b
AIF3_nOutW2_a
AIF3_bFDO16_b
...
AIF3_bFDO31_b
AIF3_dnOutD1_p
AIF3_nOutW3_a
AIF3_nOutW4_a
16 Bit
16 binary
signals
16 Bit
16 binary
signals
16 Bit
LowWord
16 Bit
HighWord
16 Bit
16 Bit
Byte
Byte
Byte
Byte
Byte
Byte
Byte
Byte
1
2
3
4
5
6
7
8
Automation
Interface
Fig. 2−6 Outputs_AIF3
L
9300 Servo PLC EN 5.0
2−13
9300 Servo PLC
System blocks
2.3 AIF3_IO_AutomationInterface (node number 43)
System variables
Variable Data type Signal type Address Display code Display
AIF3_nOutW1_a
AIF3_nOutW2_a %QW43.1
AIF3_nOutW3_a %QW43.2
AIF3_nOutW4_a %QW43.3
AIF3_bFDO0_b
... ...
AIF3_bFDO15_b %QX43.0.15
AIF3_bFDO16_b %QX43.1.0
... ...
AIF3_bFDO31_b %QX43.1.15
AIF3_dnOutD1_p Double integer Position %QD43.0
Integer Analog
Bool Binary
%QW43.0
%QX43.0.0
format
Note
User data
The first 4 bytes of the 8 bytes of user data to be sent can be written to via several variables of different
data types at the same time. Data can therefore be transferred by the PLC program as
binary information (1 bit)
quasi−analog value (16 bits)
angle information (32 bits)
according to the requirements.
Byte Variable (1 bit) Variable (16 bits) Variable (32 bits)
1, 2 AIF3_bFDO0_b
...
AIF3_bFDO15_b
3, 4 AIF3_bFDO16_b
...
AIF3_bFDO31_b
5, 6
AIF3_nOutW1_a
AIF3_dnOutD1_p
AIF3_nOutW2_a
AIF3_nOutW3_a
7, 8
AIF3_nOutW4_a
Tip!
Avoid simultaneous overwriting via different variable types to ensure data consistency.
Thus bytes 1 and 2 should only be written to
– by the variable AIF3_dnOutD1_p,
– by the variable AIF3_nOutW1_a or
– by the variables AIF3_bFDO0_b ... AIF3_bFDO15_b.
2−14
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.4 AIF_IO_Management (node number 161)
2.4 AIF_IO_Management (node number 161)
2.4.1 Inputs_AIF_Management
This SB monitors the communication of a communication module connected to the automation
interface (AIF).
In the event of an error, AIF_bCe0CommErr_b is set to TRUE and the communication error
"CE0" (LECOM no. 61) is set. The response to this can be configured under C0126 (Lenze
setting: off).
New AIF communication modules (e.g. 2133 and 2175) also use
AIF_bFieldBusStateBit0_b ... AIF_bFieldBusStateBit15_b to transfer an error number from the
communication module.
C2121 displays the status.
Tip!
Please observe the documentation for the attached communication module.
Automation
interface
Fig. 2−7 System block "Inputs_AIF_Management"
AIF
Communication
Error
AIF
Fieldbus State
Inputs_AIF_Management
AIF_bCe0CommErr_b
AIF_bFieldBusStateBit0_b
AIF_bFieldBusStateBit1_b
AIF_bFieldBusStateBit2_b
AIF_bFieldBusStateBit3_b
AIF_bFieldBusStateBit4_b
AIF_bFieldBusStateBit5_b
AIF_bFieldBusStateBit6_b
AIF_bFieldBusStateBit7_b
AIF_bFieldBusStateBit8_b
AIF_bFieldBusStateBit9_b
AIF_bFieldBusStateBit10_b
AIF_bFieldBusStateBit11_b
AIF_bFieldBusStateBit12_b
AIF_bFieldBusStateBit13_b
AIF_bFieldBusStateBit14_b
AIF_bFieldBusStateBit15_b
L
9300 Servo PLC EN 5.0
2−15
9300 Servo PLC
System blocks
2.4 AIF_IO_Management (node number 161)
System variables
Variable Data type Signal type Address Display code Display
AIF_bCe0CommErr_b
AIF_bFieldBusStateBit0_b %IX161.1.0 Error number − bit 0
AIF_bFieldBusStateBit1_b %IX161.1.1 Error number − bit 1
AIF_bFieldBusStateBit2_b %IX161.1.2 Error number − bit 2
AIF_bFieldBusStateBit3_b %IX161.1.3 Error number − bit 3
AIF_bFieldBusStateBit4_b %IX161.1.4 Error number − bit 4
AIF_bFieldBusStateBit5_b %IX161.1.5 Error number − bit 5
AIF_bFieldBusStateBit6_b %IX161.1.6 Error number − bit 6
AIF_bFieldBusStateBit7_b %IX161.1.7 Error number − bit 7
AIF_bFieldBusStateBit8_b %IX161.1.8 Error number − bit 8
AIF_bFieldBusStateBit9_b %IX161.1.9 Error number − bit 9
AIF_bFieldBusStateBit10_b %IX161.1.10 Error number − bit 10
AIF_bFieldBusStateBit11_b %IX161.1.11 Error number − bit 11
AIF_bFieldBusStateBit12_b %IX161.1.12 Error number − bit 12
AIF_bFieldBusStateBit13_b %IX161.1.13 Error number − bit 13
AIF_bFieldBusStateBit14_b %IX161.1.14 Error number − bit 14
AIF_bFieldBusStateBit15_b %IX161.1.15 Error number − bit 15
Bool binary
%IX161.0.0 Communication error "CE0"
format
Notes
Codes
Code LCD
C0126 MONIT CE0 3
C2121 AIF: state
Possible settings
Lenze Selection
0 TRIP
2 Warning
3 Off
G
0 {dec} 255
Decimal value is bit−coded:
Bit 0 XCAN1_IN monitoring time
Bit 1 XCAN2_IN monitoring time
Bit 2 XCAN3_IN monitoring time
Bit 3 XCAN bus−off
Bit 4 XCAN operational
Bit 5 XCAN pre−operational
Bit 6 XCAN warning
Bit 7 Internally assigned
Info
Configuration for communication
error "CE0" with automation
interface
AIF−CAN: Status
Detailed information can be
found in the documentation for
the corresponding
communication module.
2−16
9300 Servo PLC EN 5.0
L
Loading...