1.407/2000Revised edition for the 9300 Servo PLC as of software version V1.0
2.007/2001Revised edition for the 9300 Servo PLC as of software version V2.0
3.001/2003Revised edition for the 9300 Servo PLC as of software version V6.0
4.0/4.1 08/2006Revised edition for the 9300 Servo PLC as of software version V7.0
5.010/2010Revised 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.
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.1Conventions used in this Manual
This Manual uses the following conventions to distinguish between different types of information:
Information typeDistinction (in text)Example
System block nameboldThe SB DIGITAL_IO...
System (block) variable identifieritalicsThe 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.2System 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.3Pictographs in this Manual
Pictographs
used
Warning of material
damage
More notesTip!
1.1.4Terminology used
TermIn this Manual used for
AIFAutomation interface
DDSDrive PLC Developer Studio
FIFFunction interface
GDCGlobal Drive Control (parameter setting program from Lenze)
SBSystem block
System busSystem 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.2System 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.1System 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.2Node numbers
The system blocks of the 9300 Servo PLC carry the following node numbers:
Node numberSystem blockNotes
1 DIGITAL_IODigital inputs/outputs
11 ANALOG1_IOAnalog inputs/outputs 1
12 ANALOG2_IOAnalog inputs/outputs 2
21 DFIN_IO_DigitalFrequencyDigital frequency input
22 DFOUT_IO_DigitalFrequencyDigital 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_IOState bus
60 OSC_OscilloscopeOscilloscope function
101 CAN_ManagementSystem bus (CAN) management
102 CAN_SyncronizationSystem bus (CAN) synchronisation
121 DCTRL_DriveControlDevice control
131 MCTRL_MotorControlMotor control
141 FCODE_FreeCodesFree codes
151 SYSTEM_FLAGSSystem flags
161 AIF_IO_ManagementAutomation interface management
171 VAR_PERSISTENTPersistent 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.3Access 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:
VariableData typeSignal typeAddressDisplay
DIGIN_bIn1_b
.........
DIGIN_bIn8_b%IX1.0.7C0443/8
Example: Table with SB DIGITAL_IO inputs of the Drive PLC
BoolBinary
%IX1.0.0C0443/1
1.2.4Access 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:
VariableData typeSignal typeAddressDisplay
DIGIN_bIn1_b
.........
DIGIN_bIn8_b%IX1.0.7C0443/8
Example: Table with SB DIGITAL_IO inputs of the Drive PLC
BoolBinary
%IX1.0.0C0443/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.5Definition of inputs/outputs
The application program is connected with the hardware by linking system blocks with program
organisation units (POUs):
SB-OutputSB-Input
POU-InputPOU-Output
SB
POU
Fig. 1−1Principle: 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−2Principle: 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.6Linking 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−3Example: 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.7Signal 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.
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.1AIF1_IO_AutomationInterface (node number 41)
2.1AIF1_IO_AutomationInterface (node number 41)
2.1.1Inputs_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.
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)
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.
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)
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, 6AIF1_bFDO0_b
...
AIF1_bFDO15_b
7, 8AIF1_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.2AIF2_IO_AutomationInterface (node number 42)
2.2AIF2_IO_AutomationInterface (node number 42)
2.2.1Inputs_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.
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)
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.
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)
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.3AIF3_IO_AutomationInterface (node number 43)
2.3AIF3_IO_AutomationInterface (node number 43)
2.3.1Inputs_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.
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)
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.
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)
AIF_bCe0CommErr_b
AIF_bFieldBusStateBit0_b%IX161.1.0Error number − bit 0
AIF_bFieldBusStateBit1_b%IX161.1.1Error number − bit 1
AIF_bFieldBusStateBit2_b%IX161.1.2Error number − bit 2
AIF_bFieldBusStateBit3_b%IX161.1.3Error number − bit 3
AIF_bFieldBusStateBit4_b%IX161.1.4Error number − bit 4
AIF_bFieldBusStateBit5_b%IX161.1.5Error number − bit 5
AIF_bFieldBusStateBit6_b%IX161.1.6Error number − bit 6
AIF_bFieldBusStateBit7_b%IX161.1.7Error number − bit 7
AIF_bFieldBusStateBit8_b%IX161.1.8Error number − bit 8
AIF_bFieldBusStateBit9_b%IX161.1.9Error number − bit 9
AIF_bFieldBusStateBit10_b%IX161.1.10Error number − bit 10
AIF_bFieldBusStateBit11_b%IX161.1.11Error number − bit 11
AIF_bFieldBusStateBit12_b%IX161.1.12Error number − bit 12
AIF_bFieldBusStateBit13_b%IX161.1.13Error number − bit 13
AIF_bFieldBusStateBit14_b%IX161.1.14Error number − bit 14
AIF_bFieldBusStateBit15_b%IX161.1.15Error number − bit 15
Boolbinary
%IX161.0.0Communication error "CE0"
format
Notes
Codes
CodeLCD
C0126 MONIT CE03
C2121 AIF: state
Possible settings
Lenze Selection
0TRIP
2Warning
3Off
G
0{dec}255
Decimal value is bit−coded:
Bit 0XCAN1_IN monitoring time
Bit 1XCAN2_IN monitoring time
Bit 2XCAN3_IN monitoring time
Bit 3XCAN bus−off
Bit 4XCAN operational
Bit 5XCAN pre−operational
Bit 6XCAN warning
Bit 7Internally 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
9300 Servo PLC
System blocks
2.4AIF_IO_Management (node number 161)
2.4.2Outputs_AIF_Management
This SB transfers commands and messages to a fieldbus module connected to an automation
interface (AIF).
For this purpose C2120 provides a control word. The commands are specified as numbers. Some
command numbers are universally applicable for all fieldbus modules, others apply only for special
modules. The total number of commands available can amount to up to 16.
Tip!
Read the documentation for the attached fieldbus module.
0−10 V ... + 10 V (master voltage)
1+4 mA ... +20 mA(master current)
2−20 mA ... +20 mA
Info
current
Please also observe the jumper position X3 at the front of the 9300 Servo PLC in this
connection (see terminal assignment).
Use as a 4 ... 20 mA master current input
If the input is used as a master current input (C0034 =1), then AIN1_bError_b = TRUE as long
as the absolute value of the master current is < 2 mA, otherwise it is FALSE.
C0598 can be used to set the response for the case that the absolute value of the master
current is < 2 mA:
2−18
CodeLCD
C0598 MONIT SD53Monitoring configuration:
Possible settings
LenzeSelection
0TRIP
2Warning
3Off
Info
Absolute master current value across
X6/1, 2 < 2 mA
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.5ANALOG1_IO (node number 11)
Terminal assignment
Set via C0034 whether the input is to be used for a master voltage or a master current.
Set jumper bar X3 according to setting in C0034:
Stop!
Do not plug the jumper on 3−4! The PLC cannot be initialised in this case.
TerminalUseJumper X3Measuring range
X6/1, 2
Differential input for
master voltage
Differential input for
master current
6
4
2
6
4
2
5
3
1
5
3
1
C0034 = 0
Level:
Resolution:
Scaling:
C0034 = 1
Level:
Resolution:
Scaling:
C0034 = 2
Level:
Resolution:
Scaling:
−10 V ... +10 V
5 mV (11 bits + sign)
10 V 16384 100 %
+4 mA ... +20 mA
20 A (10 bits without sign)
+4 mA 0 0 %
+20 mA +16384 +100 %
−20 mA ... +20 mA
20 A (10 bits + sign)
20 mA 16384 100 %
2.5.2Outputs_ANALOG1 (analog output)
The output can be used as a monitor output. Internal analog signals can be output as voltage signals
via terminal X6/62 and used, for instance, as display values or setpoints for slave drives.
The output can be used as a monitor output. Internal analog signals can be output as voltage signals
via terminal X6/63 and used, for instance, as display values or setpoints for slave drives.
AOUT2_nOut_a
Inputs_ANALOG2
AIN2_nIn_a
C0405
code
Level:
Resolution:
Scaling:
Outputs_ANALOG2
C0439
Display
format
−10 V ... +10 V
5 mV (11 bits + sign)
10 V 16384 100 %
−10 V ... +10 V (max. 2 mA)
20 mV (9 bits + sign)
10 V 16384 100 %
Note
L
9300 Servo PLC
System blocks
2.7DCTRL_DriveControl (node number 121)
2.7DCTRL_DriveControl (node number 121)
This SB controls the transition of the 9300 Servo PLC to certain states (e.g. TRIP, TRIP−RESET, quick
stop (QSP) or controller inhibit (CINH)).
The process image is created in the course of a fixed system task (interval: 2 ms).
DCTRL_wCAN1Ctrl
DCTRL_wAIF1Ctrl
DCTRL_bCInh1_b
DCTRL_bCInh2_b
DCTRL_bTripSet_b
DCTRL_bTripReset_b
DCTRL_bStateB0_b
DCTRL_bStateB2_b
DCTRL_b_bStateB3
DCTRL_b_bStateB4
DCTRL_bStateB5_b
DCTRL_bStateB14_b
DCTRL_bStateB15_b
C0878/1
C0878/2
C0878/3
C0878/4
16 Bit
16 Bit
C0135
C0136/1
16
C135.B3
C135.B8
C135.B9
X5/28
Bit10
Bit10
C135.B10
Bit11
Bit11
C135.B11
DCTRL_bImp_b
DCTRL_bNActEq0_b
DCTRL_bCInh_b
DCTRL_bStat1_b
DCTRL_bStat2_b
DCTRL_bStat4_b
DCTRL_bStat8_b
DCTRL_bWarn_b
DCTRL_bMess_b
Bit3
Bit3
Bit8
Bit8
Bit9
Bit9
DCTRL_DriveControl
QSP
>
1
DISABLE
>
1
>
1
CINH
TRIP-SET
>
1
TRIP-
>
1
RESET
>
1
STAT
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
DCTRL_bFail_b
DCTRL_bImp_b
DCTRL_bTrip_b
DCTRL_bQspIn_b
DCTRL_bRdy_b
DCTRL_bCwCCw_b
DCTRL_bNActEq0_b
DCTRL_bCInh_b
DCTRL_bStat1_b
DCTRL_bStat2_b
DCTRL_bStat4_b
DCTRL_bStat8_b
DCTRL_bWarn_b
DCTRL_bMess_b
DCTRL_bInit_b
DCTRL_bExternalFault_b
DCTRL_wFaultNumber
DCTRL_wStat
C0150
Fig. 2−13DCTRL_DriveControl
Tip!
The SB DCTRL_DriveControl only affects the motor control and drive control of the
9300 Servo PLC, i.e. motor control/drive control and application program of the PLC are completely
independent of each other as long as the signals are not queried in the application program.
If, for instance, the motor control initiates a TRIP, the application program will not be stopped!
If, however, a TRIP is caused by a task overflow, the application program of the PLC will be
stopped as well!
L
9300 Servo PLC EN 5.0
2−21
9300 Servo PLC
System blocks
2.7DCTRL_DriveControl (node number 121)
2.7.1Inputs_DCTRL
System variables
VariablesData type Signal typeAddressDisplay
DCTRL_bFail_b
DCTRL_bImp_b%IX121.0.1TRUE = power output stages with high
The QSP function is used to stop the drive independently of the selected setpoint within an adjustable
time interval.
Note!
Quick stop (QSP) will only be set if DCTRL_bQspIn_b is connected to MCTRL_bQspOut_b of
SB MCTRL_MotorControl:
DCTRL_bQspIn_b
Any Variable
OR
MCTRL_bQspOut_b
MCTRL_nHiMLim_a
MCTRL_nLoMLim_a
MCTRL_bNMSwt_b
C0907/3
C0906/4
C0906/3
C0907/2
The function can be controlled via the following 3 inputs (OR−linked):
– Control word CAN1_wDctrlCtrl of SB CAN1_IN
– Control word AIF_wDctrlCtrl of SB AIF1_IN
– Control word C0135, bit 3
C0136/1 indicates the control word C0135:
CodeLCD
C0136 CTRLWORD
1DCTRL_DriveControl
Possible settings
LenzeSelection
g
0{hex}FFFF
Info
Control word
Hexadecimal value is bit−coded.
Speed is reduced to 0 within the deceleration time set under C0105:
CodeLCD
C0105 QSP Tif0.000Deceleration time for quick stop (QSP)
Possible settings
LenzeSelection
0.000{0.001 s}999.900
Info
Referred to speed change
... 0
n
max
.
2.7.4Operation disabled (DISABLE)
This function sets "Operation disabled (DISABLE)" in the drive, i.e. the power output stages are
inhibited and all speed/current/position controllers are reset. With "Operation disabled", the drive
cannot be started with the "Controller enable" command.
The function can be controlled via the following 3 inputs (OR−linked):
– Control word CAN1_wDctrlCtr of SB CAN1_IN
– Control word AIF_wDctrlCtrl of SB AIF1_IN
– Control word C0135, bit 8
C0136/1 indicates the control word C0135. (^ 2−23)
L
9300 Servo PLC EN 5.0
2−23
9300 Servo PLC
System blocks
2.7DCTRL_DriveControl (node number 121)
2.7.5Controller inhibit (CINH)
This function sets "Controller inhibit (CINH)" in the drive, i.e. the power output stages are inhibited
and all speed/current/position controllers are reset.
The function can be controlled via the following 6 inputs (OR−linked):
– Terminal X5/28 (FALSE = controller inhibit active)
– Control word CAN1_wDctrlCtr of SB CAN1_IN
– Control word AIF_wDctrlCtrl of SB AIF1_IN
– Control word C0135, bit 9
– System variable DCTRL_bCInh1_b (TRUE = set controller inhibit)
– System variable DCTRL_bCInh2_b (TRUE = set controller inhibit)
C0136/1 indicates the control word C0135. (^ 2−23)
2.7.6Setting TRIP (TRIP−SET)
This function sets "TRIP" in the drive and signals an "external error" (error message "EEr").
The function can be controlled via the following 4 inputs (OR−linked):
– Control word CAN1_wDctrlCtr of SB CAN1_IN
– Control word AIF_wDctrlCtrl of SB AIF1_IN
– Control word C0135, bit 10
– System variable DCTRL_bTripSet_b (TRUE = set TRIP)
C0136/1 indicates the control word C0135. (^ 2−23)
The response to TRIP can be set under C0581:
CodeLCD
C0581 MONIT Eer0Monitoring configuration:
Possible settings
LenzeSelection
0TRIP
1Message
2Warning
3Off
Info
External error
2−24
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.7DCTRL_DriveControl (node number 121)
2.7.7Resetting TRIP (TRIP−RESET)
This function resets an active TRIP provided that the cause of malfunction is eliminated. If the cause
of malfunction is still active, there is no response.
The function can be controlled via the following 4 inputs (OR’d):
– Control word CAN1_wDctrlCtr of SB CAN1_IN
– Control word AIF_wDctrlCtrl of SB AIF1_IN
– Control word C0135, bit 11
– System variable DCTRL_bTripReset_b
Note!
The function can only be performed by the FALSE−TRUE edge of the signal resulting from the OR
operation!
A FALSE−TRUE edge cannot occur if one of the inputs is TRUE!
C0136/1 indicates the control word C0135. (^ 2−23)
2.7.8Output of digital status signals
Via DCTRL_wStat a status word is output which consists of the signals generated from the SBDCTRL_DriveControl and of signals from freely configurable SB inputs:
DCTRL_bStateB0_b
DCTRL_bStateB2_b
DCTRL_b_bStateB3
DCTRL_b_bStateB4
DCTRL_bStateB5_b
DCTRL_bStateB14_b
DCTRL_bStateB15_b
Fig. 2−14Output of the status word DCTRL_wStat
DCTRL_bImp_b
DCTRL_bNActEq0_b
DCTRL_bCInh_b
DCTRL_bStat1_b
DCTRL_bStat2_b
DCTRL_bStat4_b
DCTRL_bStat8_b
DCTRL_bWarn_b
DCTRL_bMess_b
DCTRL_DriveControl
STAT
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
DCTRL_wStat
C0150
L
9300 Servo PLC EN 5.0
2−25
9300 Servo PLC
System blocks
2.7DCTRL_DriveControl (node number 121)
With C0150 you can display the status word:
CodeLCD
C0150 Status word
Possible settings
LenzeSelection
g
Info
Status word DCTRL_wStat
FCODE_bC150Bit0_b ...
FCODE_bC150Bit15_b
0{1}65535
Decimal value is bit−coded:
Bit 00 Freely configurable 0
Bit 01 IMP(DCTRL_bImp_b)
Bit 02 Freely configurable 2
Bit 03 Freely configurable 3
Bit 04 Freely configurable 4
Bit 05 Freely configurable 5
Bit 06 n = 0(DCTRL_bNActEq0_b)
Bit 07 RSP(DCTRL_bCInh_b)
Bit 08 Status(DCTRL_bStat1_b)
Bit 09 Status(DCTRL_bStat2_b)
Bit 10 Status(DCTRL_bStat4_b)
Bit 11 Status(DCTRL_bStat5_b)
Bit 12 Warning(DCTRL_bWarn_b)
Bit 13 Message(DCTRL_bMess_b)
Bit 14 Freely configurable 14
Bit 15 Freely configurable 15
The system variables DCTRL_bStat1_b ... DCTRL_bStat8_b display the status of the drive in
binary−coded form:
DCTRL_bStat8_b DCTRL_bStat4_b DCTRL_bStat2_b DCTRL_bStat1_b Status
0000Initialisation after connection of the supply voltage
0001Protection against unexpected start−up active (C0142 = 0)
0011Drive inhibited (controller inhibit)
0110Drive enabled
0111The triggering of a monitoring function resulted in a "message"
1000The triggering of a monitoring function resulted in a TRIP
1010The triggering of a monitoring function resulted in a FailQSP
0 = FALSE1 = TRUE
2.7.8.1TRIP status (DCTRL_bExternalFault_b)
If a "TRIP" is initiated in the drive (e.g. via the system variable DCTRL_bTripSet_b, C0135/bit 10 or
keypad), the system variable DCTRL_bExternalFault_b is set to TRUE.
DCTRL_bExternalFault_b is reset to FALSE as soon as the error source is reset.
2−26
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.7DCTRL_DriveControl (node number 121)
2.7.9Transfer of status/control word via AIF
If the control and/or status word of SB DCTRL_DriveControl is to be assigned to SB AIF1_IO, the
following program in the IEC1131−3 programming language IL can, for instance, be used:
LD DCTRL_wStat
ST AIF1_wDctrlStat /* writing the status word */
LD AIF1_wDctrlCtrl
ST DCTRL_wAIF1Ctrl /* writing the control word */
Tip!
The assignment of the status/control word depends on the communication module used and on the
transmission profile set (e.g. DRIVECOM).
L
9300 Servo PLC EN 5.0
2−27
9300 Servo PLC
System blocks
2.8DFIN_IO_DigitalFrequency (node number 21)
2.8DFIN_IO_DigitalFrequency (node number 21)
2.8.1Inputs_DFIN
This SB can convert a pulse current at the digital frequency input X9 into a speed value and scale it.
The transmission is very precise without offset and gain errors.
In addition, this SB provides the phase correction value DFIN_dnIncLastScan_p which is
required within the calling task for phase processing of touch probe processes.
(^ 2−33)
Fig. 2−15DFIN_IO_DigitalFrequency
System variables
VariableData typeSignal typeAddressDisplay
DFIN_nIn_vIntegerVelocity%IW21.0C0426dec [rpm]Value in inc/ms
DFIN_bEncFaultCable_bBoolBinary%IX21.1.0−−TRUE = Monitoring
DFIN_bTPReceived_bBoolBinary%IX21.1.2−−Receive touch probe (TP)
DFIN_dnIncLastScan_p Double integerPosition%ID21.1−−inc between TP and task start
X9
E5
C0427
C0425
4V
(X9/8)MONIT_SD3
MP
C0431
0
1
C0428 C0429
0
1
DFIN_IO_DigitalFrequency
C0426
DFIN_bEncFaultCable_b
TP/MP
-Ctrl
DFIN_bTPReceived_b
DFIN_dnIncLastScan_p
Code
DFIN_nIn_v
Display
Format
Note
"FaultEncCable" has been
triggered because X9/8 is not
supplied with voltage and the
digital frequency coupling is thus
interrupted.
2−28
Stop!
The digital frequency input X9 cannot be used if
you use the digital frequency output X10 (C0540 = 0, 1, 2) and
an incremental encoder/sin−cos encoder!
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.8DFIN_IO_DigitalFrequency (node number 21)
Tip!
The process image is newly created for every task the SB is used in.
If DFIN_nIn_v, DFIN_dnIncLastScan_p and DFIN_bTPReceived_b are used in several tasks,
each task creates its own SB process image.
This process is different from the previous process image creation principle!
The digital frequency input X9 is dimensioned for TTL−level signals.
The input of a zero track is optional.
Configuration of the number of increments
The drive can be adapted to the connected encoder or upstream controller with digital
frequency cascade or digital frequency bus under C0425.
CodeLCD
C0425 DFIN const3Number of increments of the encoder
Possible settings
LenzeSelection
0256increments per revolution
1512increments per revolution
21024increments per revolution
32048increments per revolution
44096increments per revolution
58192increments per revolution
616384increments per revolution
Info
input
L
9300 Servo PLC EN 5.0
2−29
9300 Servo PLC
System blocks
2.8DFIN_IO_DigitalFrequency (node number 21)
Configuration of the digital frequency input signal
The type of the digital frequency input signal is configured under C0427:
CodeLCD
Possible settings
Info
LenzeSelection
C0427 DFIN function0Type of the digital frequency signal
02 phases
1A = Speed / B = Direction
2A or B = Speed or direction
C0427 = 0 (2 phases)
A
A
B
B
Z
Z
Track CW rotationCCW rotation
Aleads track B by 90º
(DFIN_nIn_v = positive value)
lags behind track B by 90º
(DFIN_nIn_v = negative value)
B−−
Signal sequence with phase shift (CW rotation)
C0427 = 1 (A = Speed / B = Direction)
A
A
B
B
Z
Z
Track CW rotationCCW rotation
Atransmits the speedtransmits the speed
B= FALSE
(DFIN_nIn_v = positive value)
= TRUE
(DFIN_nIn_v = negative value)
Control of the direction of rotation via track B
C0427 = 2 (A or B = speed or direction)
A
A
B
B
Z
Z
Track CW rotationCCW rotation
Atransmits the speed and the direction
= FALSE
of rotation
(DFIN_nIn_v = positive value)
B= FALSEtransmits the speed and the direction
of rotation
(DFIN_nIn_v = negative value)
Control of the speed and the direction of rotation
via track A or track B
2−30
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.8DFIN_IO_DigitalFrequency (node number 21)
Transmission function
DFIN_nIn_v + f[Hz] @
60
StrichzahlausC0425
@
15000
14
2
Example:
Input frequency = 200 kHz
C0425 = 3, this corresponds to 2048 increments/rev.
DFIN_nIn_v[rpm] + 200000Hz @
Signal adaptation
Finer resolutions can be achieved by adding a downstream FB (e.g. L_CONV from the
LenzeDrive.lib):
X9
(X9/8)
4V
MONIT_SD3
C0427
C0425
DF_IN
DFIN_nIn_v
C0426
DFIN_bEncFaultCable_b
60
+ 5859rpm
2048
nIn_anOut_a
NNumerator
Ndenominator
L_CONV
0
TP/MP
1
E5
Fig. 2−16Digital frequency input (DFIN_IO_DigitalFrequency) with downstream FB L_CONV for scaling
nOut_a + f[Hz] @
-Ctrl
C0428 C0429
StrichzahlausC0425
DFIN_bTPReceived_b
DFIN_dnIncLastScan_p
60
nNumerator
@
nDenominator
@
15000
14
2
L
9300 Servo PLC EN 5.0
2−31
9300 Servo PLC
System blocks
2.8DFIN_IO_DigitalFrequency (node number 21)
2.8.1.1Technical data for the connection of X9
B
B
A
A
Z
Z
l = max. 50 m
Lamp control
GND
B
B
A
A
Z
Z
X9
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
mm
0.14
0.5
0.14
0.5
0.14
2
AWG
26
20
26
20
26
X10
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
Fig. 2−17Connection of digital frequency output X10 with digital frequency input X9
Master drive
Slave drive
Cable cross−sections to be used
enable
GND
Note!
Digital frequency input (X8/X9) and digital frequency output (X10) cannot be used independently of
each other, i.e. either X8 or X9 is output to X10 (C0540 = 4, 5).
If the configuration under C0540 selects another output for X10 (C0540 = 0, 1, 2), the digital
frequency inputs X8/X9 are deactivated.
The connection is to be carried out as
shown in the wiring diagram:
Use cables which are twisted and
shielded in pairs.
Connect the shield at both ends.
Observe specified cable cross−sections.
Digital frequency input X9
Technical data
Connection:Sub−D male connector, 9−pole
Output frequency:0 − 500 kHz
Current consumption:max. 6 mA per channel
Possible input signals: Incremental encoder with two 5 V complementary signals (TTL encoders), shifted by 90°
Encoder simulation of the master drive
Properties
Two−track with inverse 5 V signals and zero track
PIN 8 (LC) monitors the cable / the upstream drive controller:
– When PIN 8 is LOW, the "FaultEncCable" ("SD3") monitoring is triggered.
– If the monitoring is not required, this input can be connected to +5 V.
The digital frequency input is switched off with C0540 = 0, 1 or 2.
Assignment of the Sub−D male connector (X9)
PIN123456789
SignalBAA+5 VGNDZZLCB
Digital frequency output X10
See SB DFOUT_IO_DigitalFrequency. (^ 2−35)
2−32
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.8DFIN_IO_DigitalFrequency (node number 21)
2.8.1.2Touch probe (TP)
Process: The current phase value (digital frequency input value) is saved by a quick interrupt in the
operating system when a signal change occurs at the TP activating input (e.g. X5/E5).
X9
Fig. 2−18Function chart of a TP
Time−equidistant start of an interval task
Angle signal
Touch probe configuration
CodeLCD
C0428 DFIN TP sel.0Touch probe selection
C0429 TP delay0Touch probe delay
C0431 DFIN TP EDGE0Touch probe activation
C0427
C0425
4V
MONIT_SD3
(X9/8)
0
X5
E5
TP/MP
1
-Ctrl
C0428 C0429
Possible settings
LenzeSelection
0Touch probe via zero pulse
1Touch probe through digital input X5/E5
−32767{1 inc}32767
0Activation with positive signal
1Activation with negative signal
C0426
DF_IN
DFIN_nIn_v
DFIN_bEncFaultCable_b
DFIN_bTPReceived_b
DFIN_dnIncLastScan_p
nIn_anOut_a
NNumerator
Ndenominator
L_CONV
Info
Compensation of delay times of
the TP signal source at X5/E5
For touch probe via digital input
X5/E5 (C0428 = 1)
L
9300 Servo PLC EN 5.0
2−33
9300 Servo PLC
System blocks
2.8DFIN_IO_DigitalFrequency (node number 21)
Functional sequence
1. The TP is activated via a signal change at the digital input X5/E5 or via a zero pulse (only if an
encoder is connected).
2. If a TP has occurred, DFIN_bTPReceived_b is set = TRUE.
3. After the start of the task, DFIN_dnIncLastScan_p indicates the number of increments [inc]
counted since the TP.
4. Then DFIN_bTPReceived_b is set = FALSE.
Note!
It is necessary that all three outputs (DFIN_nIn_v, DFIN_bTPReceived_b and
DFIN_dnIncLastScan_p) are processed in the task even if just one signal is required.
The polarity of the digital input X5/E5 configured under C0114/5 does not affect the edge
evaluation.
DFIN_nIn_v
The value DFIN_nIn_v is scaled in increments per millisecond.
(INT) 16384 corresponds to 15000 rpm. See chapter 1.2.7, "Signal types and scalings".
For every task in which DFIN_nIn_v is used the operating system creates an individual
integrator that is reset after every start of the task (task−internal process image).
For a safe TP generation, DFIN_nIn_v must not be used in the PLC_PRG.
Example (DFIN_nIn_v in a 10 ms task):
When the 10 ms task starts, the value of the integrator is stored in a local area of the task and
the integrator is reset. The value in the local area gives an average value in increments per 1
ms.
If a position value is to be derived from this value, then it must be multiplied by
SYSTEM_nTaskInterval / 4 to get the result in increments per 10 ms, as in the example.
Example: In a 1−ms task, SYSTEM_nTaskInterval has the value 4 (4 x 250 s = 1 ms).
In the Lenze FBs this process is already implemented.
2.8.1.3Encoder cable monitoring ("FaultEncCable")
PIN 8 (LC) of the digital frequency input X9 monitors the cable / the upstream drive controller:
When PIN 8 is LOW, the "FaultEncCable" ("SD3") monitoring is triggered and the system
variable DFIN_bEncFaultCable_b is set to TRUE.
If the monitoring is not required, this input can be connected to +5 V.
(^ 1−8)
2−34
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.9DFOUT_IO_DigitalFrequency (node number 22)
2.9DFOUT_IO_DigitalFrequency (node number 22)
2.9.1Inputs_DFOUT / Outputs_DFOUT
This SB converts internal speed signals into frequency signals and outputs them to X10.
The transmission is very precise with the remainder being considered (no offset and gain
errors).
DFOUT_nOut_vDFOUT_nIn_v
X7
X9
X8
Fig. 2−19Digital frequency output (DF_OUT)
System variables
VariableData typeSignal typeAddressDisplay
DFOUT_nOut_vIntegerVelocity%QW22.0C0547
DFOUT_nIn_vIntegerVelocity%IW22.0−−
C0540
DFOUT_IO_DigitalFrequency
C0030
C0540
C1799
0
1
2
4
5
C0549
C0547
n
ma x
CTRL
C0545
Code
C0540
0
1
2
4
5
Display
Format
X10
Note
dec [%]
C0549
dec [rpm]
L
Tip!
The process image is newly created for every task the SB is used in.
If DFOUT_nIn_v and DFOUT_nOut_v are used in several tasks, an own process image of the
SB is created for each of these tasks.
This process is different from the previous process image creation principle!
The signals of the digital frequency output X10 are TTL−compatible.
The output signal corresponds to the simulation of an incremental encoder:
– Track A, track B and the zero track (if necessary) as well as the corresponding inverted
tracks are output with tracks shifted by 90°.
9300 Servo PLC EN 5.0
2−35
9300 Servo PLC
System blocks
2.9DFOUT_IO_DigitalFrequency (node number 22)
Configuration of the digital frequency output signal
The type of the digital frequency output signal is configured under C0540:
CodeLCD
C0540 Function2Digital frequency output: Function
Possible settings
LenzeSelection
Info
X9 is inhibited if 0, 1, or 2 have
been selected.
DFOUT_nIn_v = 0 if 4 or 5 have
been selected.
The input signals are buffered
electrically.
0DFOUT_nOut_v as %
1DFOUT_nOut_v as rpm
2Incremental encoder simulation + zero pulse
4X9 is output on X10
5X8 is output on X10
C0540 = 0Output of an analog signal
FunctionThe input signal DFOUT_nOut_v is interpreted as an analog signal [%] and is output as a frequency signal on the
Scaling100 % (INT)16384 C0011 (n
Transmission function
Example
digital frequency output X10.
f[Hz] + DFOUT_nOut_v[%] @
DFOUT_nIn_v + f[Hz] @
DFOUT_nOut_v = 50 %
max)
StrichzahlausC0030
100
60
Strichzahl aus C0030
@
@
14
2
15000
C0011(n
60
max
)
C0030 = 3, this corresponds to a number of increments of 2048 increments/revolution
C0011 = 3000 rpm
2048
f[Hz] + 50% @
C0540 = 1Output of a speed signal
FunctionThe input signal DFOUT_nOut_v is interpreted as a speed signal [rpm] and is output as a frequency signal on the
Scaling15000 rpm (INT)16384
Transmission function
Example
digital frequency output X10.
f[Hz] + DFOUT_nOut_v[rpm] @
DFOUT_nOut_v = 3000 rpm
100
3000
@
+ 51200Hz
60
Strichzahl aus C0030
60
C0030 = 3, this corresponds to a number of increments of 2048 increments/revolution
f[Hz] + 3000rpm @
C0540 = 2Encoder simulation of the resolver with zero track in resolver position
Function The function is used if a resolver is connected to X7.
2048
60
+ 102400Hz
The encoder constant for the output X10 is set under C0030.
The output of the zero pulse referring to the rotor depends on how the resolver is attached to the motor.
The zero pulse can be shifted by +360 ° under C0545 (65536 inc = 360 °).
C0540 = 4Direct output of X9
FunctionUse of X9 as a digital frequency input.
The input signal at X9 is electrically amplified and is directly output to X10.
The signals depend on the assignment of input X9.
C0030 and C0545 have no function.
The zero track is only output if it is also connected to X9.
C0540 = 5Direct output of X8
FunctionUse of X8 as an input for incremental encoders or sin/cos encoders.
The input signal at X8 is electrically amplified and is directly output to X10.
The signals depend on the assignment of input X8.
C0030 and C0545 have no function.
The zero track is only output if it is also connected to X8.
2−36
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.9DFOUT_IO_DigitalFrequency (node number 22)
Configuration of the encoder constant
The encoder constant of the encoder simulation can be set under C0030:
CodeLCD
C0030 DFOUT const3Encoder constant
C1799 DFOUT fmax1250DF_OUT_DigitalFrequency:
Possible settings
LenzeSelection
0256increments per revolution
1512increments per revolution
21024increments per revolution
32048increments per revolution
44096increments per revolution
58192increments per revolution
616384increments per revolution
2.9.1.1Technical data for the connection of X10
B
B
A
A
enable
Z
Z
l = max. 50 m
Lamp control
GND
B
B
A
A
Z
Z
X9
2
mm
1
1
0.14
2
2
3
3
4
4
0.5
5
5
6
6
0.14
7
7
0.5
8
8
0.14
9
9
X10
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
GND
AWG
26
20
26
20
26
Info
Maximum output frequency at X10
Note: The limitation of the maximum
output frequency at DFOUT is highly
non−linear. Hence:
C0540 1: Upstream limitation of the
value "DFOUT_nOut_v"
C0540 >1: Limitation on the motor
side via C0011.
(The non−linear resolution of the
limitation has no effect on the transfer
function of the DfOut)
The connection is to be carried out as
shown in the wiring diagram:
Use cables which are twisted and
shielded in pairs.
Connect the shield at both ends.
Observe specified cable cross−sections.
Fig. 2−20Connection of digital frequency output X10 with digital frequency input X9
Master drive
Slave drive
Cable cross−sections to be used
Note!
Digital frequency input (X8/X9) and digital frequency output (X10) cannot be used independently of
each other, i.e. either X8 or X9 is output to X10 (C0540 = 4, 5).
If the configuration under C0540 selects another output for X10 (C0540 = 0, 1, 2), the digital
frequency inputs X8/X9 are deactivated.
L
9300 Servo PLC EN 5.0
2−37
9300 Servo PLC
System blocks
2.9DFOUT_IO_DigitalFrequency (node number 22)
Digital frequency output X10
Technical data
Connection:Sub−D female connector, 9−pole
Output frequency:0 − 500 kHz
Ampacity:Max. 20 mA per channel
Load capacity: With a parallel connection, a maximum of 3 slave drives can be connected.
Properties
Two−track with inverse 5 V signals and zero track
When PIN 8 (EN) is LOW, the master drive is being initialised (e.g. if the mains was disconnected in the meantime).
The slave drive can thus monitor the master.
Assignment of the Sub−D connector (X10)
PIN123456789
SignalBAA+5 VGNDZZENB
With a series connection, any number of slave drives can be connected.
A
A
B
B
Z
Z
Signal sequence with phase shift (CW rotation)
Track CW rotationCCW rotation
Aleads track B by 90º
(DFIN_nIn_v = positive value)
B−−
lags behind track B by 90º
(DFIN_nIn_v = negative value)
Note!
The digital frequency output X10 has a system−dependent delay time Td which can be calculated
using the following formula:
= Task cycle time (process image cycle) − 1 ms
T
d
Example: If DFOUT_nOut_v is written to in a "10−ms task", the signal at X10 has a delay time T
9 ms (10 ms − 1 ms).
Digital frequency input X9
See SB DFIN_IO_DigitalFrequency. (^ 2−28)
of
d
2−38
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.10DIGITAL_IO (node number 1)
2.10DIGITAL_IO (node number 1)
2.10.1Inputs_DIGITAL (digital inputs)
This SB reads in the signals at the terminals X5/E1 ... E5 and conditions them.
0 ... +4 V
+13 ... +30 V
Max. 50 mA per output
(external resistance 480 at 24 V)
300 s with rising edge
100 s with falling edge
2−40
CodeLCD
Possible settings
Info
LenzeSelection
C0118 DIGOUT polTerminal polarity
0HIGH active
1LOW active
10X5/A1
20X5/A2
30X5/A3
40X5/A4
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.11FCODE_FreeCode (node number 141)
2.11FCODE_FreeCode (node number 141)
At Lenze, controller parameters are called codes. The PLC can be adapted to your application
without additional programming by changing codes.
This SB provides several variables for directly reading out the assigned "free" codes of the PLC and
for processing them in the PLC program.
FCODE_FreeCodes
C0017
C0026/1
C0026/2
C0027/1
C0027/2
C0032
C0037
C0108/1
C0108/2
C0109/1
C0109/2
C0141
C0250
C0471
C0472/1...20
C0473/1...10
C0474/1...5
C0475/1
C0475/2
C0135
rpm TO INT
%TOINT
INT
rpm TO INT
%TOINT
BOOL
DWORD
TO
BIT/BOOL
%TOINT
INT
DINT
INT
16 Bit
FCODE_nC17_a
FCODE_nC26_1_a
FCODE_nC26_2_a
FCODE_nC27_1_a
FCODE_nC27_2_a
FCODE_nC32_a
FCODE_nC37_a
FCODE_nC108_1_a
FCODE_nC108_2_a
FCODE_nC109_1_a
FCODE_nC109_2_a
FCODE_nC141_a
FCODE_bC250_b
FCODE_bC471Bit0_b
FCODE_bC471Bit31_b
FCODE_nC472_1_a
FCODE_nC472_20_a
FCODE_nC473_1_a
FCODE_nC473_10_a
FCODE_dnC474_1_p
FCODE_dnC474_5_p
FCODE_nC475_1_v
FCODE_nC475_2_v
FCODE_bC135Bit0_b
FCODE_bC135Bit15_b
...
...
...
...
...
Fig. 2−23FCODE_FreeCodes
The PLC codes listed in the boxes () on the left−hand side are assigned to the variables
listed on the right−hand side.
Code values are converted into variable values according to a fixed scaling routine.
In the code table, you can find the options that can be set and the Lenze settings. (^ 3−20)
Example
You can enter a percentage value [%] in PLC code C0472/1 (e.g. via the keypad). This value is directly
assigned to the variable FCODE_nC472_1_a (data type "integer") via a fixed scaling routine and can
be processed in the PLC program.
The free code C0470 is stored under the same memory address as C0471 and can thus be read out
via the variables FCODE_bC471Bit0_b ... FCODE_bC471Bit31_b assigned to code C0471.
Unlike code C0471, which can contain a 32−bit value, code C0470 is divided into 4 subcodes with
8 bits each:
CodeLCD
C0470 FCODE 8bitFreely configurable code (digital
10C0470/1 = C0471, bit 0 ... 7
20C0470/2 = C0471, bit 8 ... 15
30C0470/3 = C0471, bit 16 ... 23
40C0470/4 = C0471, bit 24 ... 31
The process image is created in the course of a fixed system task (interval: 1 ms).
Exception: MCTRL_bActTPReceived_b, MCTRL_dnActIncLastScan_p and MCTRL_nNAct_v
are read into the process input image of the task in which they are actually used.
2.12.1Inputs_MCTRL
System variables
VariableData typeSignal typeAddressDisplay
MCTRL_bQspIn_bBoolBinary
MCTRL_nNSetIn_aIntegerAnalog%IW131.1C0050dec [%]
MCTRL_bMMax_bBoolBinary%IX131.0.2−−
MCTRL_nMSetIn_aIntegerAnalog%IW131.3C0056dec [%]
MCTRL_bIMax_bBoolBinary%IX131.0.1−−
MCTRL_nIAct_a
MCTRL_nDCVolt_a%IW131.6
MCTRL_nMAct_a%IW131.4
MCTRL_wMmaxC57Word−%IW131.16−−
MCTRL_bUndervoltage_b
MCTRL_bOvervoltage_b%IX131.0.4Monitoring: Overvoltage
MCTRL_bShortCiruit_b%IX131.0.5Monitoring: Short circuit
MCTRL_bEarthFault_b%IX131.0.6Monitoring: Earth fault
MCTRL_bIxtOverload_b%IX131.9.2Monitoring: I x t overload
MCTRL_bSpeedLoop
Fault_b
MCTRL_nPos_aIntegerAnalog%IW131.7−−
MCTRL_nNAct_vIntegerVelocity%IW131.8−−Actual speed value [inc/ms]
MCTRL_nNAct_aIntegerAnalog%IW131.2−−
MCTRL_dnPos_p
MCTRL_bNmaxFault_bBoolBinary%IX131.0.7−−
MCTRL_nNmaxC11Integer−%IW131.15−−Display of max. speed (C0011)
MCTRL_bActTP
Received_b
MCTRL_dnActIncLast
Scan_p
IntegerAnalog
BoolBinary
Double
Integer
BoolBinary%IX131.0.10−−Receive touch probe (TP)
Double
Integer
Position%ID131.5−−Rotor position of the motor
Position%ID131.6−−inc between TP and task start
%IX131.0.0.
0
%IW131.5
%IX131.0.3
%IX131.9.4
Code
C0042bin
−−
−−
Display
Format
Note
TRUE = Drive carries out quick stop
(QSP)
Speed setpoint
16384 100 % n
TRUE = Speed controller operates
within the limits.
MCTRL_nMAdd_a is − depending on the setting of MCTRL_bNMSwt_b − used as a torque setpoint
or as an additional torque setpoint.
Torque setpoint
With MCTRL_bNMSwt_b = TRUE, the torque control is active.
MCTRL_nMAdd_a acts as a torque setpoint.
The speed controllers have a monitoring effect.
The torque setpoint is selected in [%] of the max. possible torque.
– Negative values mean a torque with CCW rotation of the motor.
– Positive values mean a torque with CW rotation of the motor.
The max. possible torque is set under C0057:
CodeLCD
C0057 Max torque
Additional torque setpoint
With MCTRL_bNMSwt_b = FALSE, the speed control is active.
Possible settings
LenzeSelection
g
0.0{0.1 Nm}500.0
Info
Maximum possible torque of the drive
configuration
Dependent on C0022, C0086
MCTRL_nMAdd_a is added to the output of the speed controller.
The limits given by the torque limitation (MCTRL_nLoMLim_a and MCTRL_nHiMLim_a) cannot
be exceeded.
The additional torque setpoint can, for instance, be used for friction compensation or to add
acceleration (dv/dt).
L
9300 Servo PLC EN 5.0
2−49
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.5Torque limitation
Via MCTRL_nLoMLim_a and MCTRL_nHiMLim_a you can set an external torque limitation. This
means that different torques can be selected for the quadrants "driving" and "braking".
MCTRL_nHiMLim_a is the upper torque limit in [%] of the max. possible torque.
MCTRL_nLoMLim_a is the lower torque limit in [%] of the max. possible torque.
The max. possible torque is set under C0057. (^ 2−49)
Stop!
Only set positive values in MCTRL_nHiMLim_a and negative values in MCTRL_nLoMLim_a,
otherwise the speed controller may be unable to perform its intended control function. This can result
in an uncontrolled acceleration of the drive.
Tip!
If MCTRL_nHiMLim_a is not assigned (free), the upper torque limit automatically is 100 % of
the max. possible torque.
If MCTRL_nLoMLim_a is not assigned (free), the lower torque limit automatically is −100 % of
the max. possible torque.
At quick stop (QSP) the torque limitation is deactivated, i.e. the drive is operated with 100 %.
2−50
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.6Maximum speed
The maximum speed (n
) is set under C0011. This value is used as a reference for the absolute and
max
relative setpoints selected for the acceleration and deceleration times and for the upper and lower
speed limits.
n
CodeLCD
= 100 % (INT) 16384
max
Possible settings
LenzeSelection
C0011 Nmax3000Maximum speed
500{1 rpm}16000
Info
Reference value for the absolute and
relative setpoint selection for the
acceleration and deceleration times.
For parameterisation via interface:
Large changes in one step should
only be made when the controller
is inhibited.
Tip!
MCTRL_nNmaxC11 displays the maximum speed set under C0011.
Use this system variable for programming your own speed scalings.
Example: C0011 = 3000 rpm MCTRL_nNmaxC11 = 3000
L
9300 Servo PLC EN 5.0
2−51
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.7Speed controller
The speed controller is designed as an ideal PID controller.
Parameter setting
By selecting a motor under C0086 the parameters are preset, making most adaptations to the
application unnecessary.
The proportional gain V
– Enter approx. 50 % of the speed setpoint (100 % = 16384 = N
– Increase C0070 until the drive becomes unstable (pay attention to motor noise)
– Reduce C0070 until the drive runs stable again.
– Reduce C0070 to approx. half the value.
can be set under C0070:
p
max
).
CodeLCD
C0070 Vp speed CTRL
The reset time T
Possible settings
LenzeSelection
Proportional gain of speed controller
0.0{0.5}255.0
can be set under C0071:
n
Info
)
(V
pn
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze
setting.
– Reduce C0071 until the drive becomes unstable (pay attention to motor noise).
– Increase C0071, until the drive runs stable again.
– Increase C0071 to approx. twice the value.
CodeLCD
C0071 Tn speed CTRL
The derivative gain T
Possible settings
LenzeSelection
Reset time of speed controller (T
1.0{0.5 ms}600.0
>512 ms = switched off
can be set under C0072:
d
Info
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze
setting.
– Increase C0072 during operation until the drive reaches an optimum control performance.
If the drive outputs the maximum torque, the speed controller operates within the limitation.
The drive cannot follow the speed setpoint.
MCTRL_bMMax_b is set to TRUE.
Set integral action component
To select defined starting values for the torque, the integral action component of the speed controller
can be set externally (e.g. when using the brake control).
MCTRL_bILoad_b = TRUE
– The speed controller accepts the value at MCTRL_nISet_a for its integral action component.
– The value at MCTRL_nISet_a acts as a torque setpoint for the motor control.
MCTRL_bILoad_b = FALSE
– Function is switched off.
2.12.8Torque control with speed limitation
Set MCTRL_bNMSwt_b = TRUE to activate this function.
For limiting the speed, a second speed controller (auxiliary speed controller) is connected.
MCTRL_nMAdd_a acts as a bipolar torque setpoint.
The speed controller 1 generates the upper speed limit.
– The upper speed limit is passed to MCTRL_nNSet_a in [%] of n
(positive sign for CW direction of rotation).
max
The speed controller 2 (auxiliary speed controller) generates the lower speed limit.
– The lower speed limit is passed to MCTRL_nNStartLim_a in [%] of n
(negative sign for CCW direction of rotation).
n
is selected under C0011. (^ 2−51)
max
max
Stop!
Use
the upper speed limit only for CW rotation (positive values) and
the lower speed limit only for CCW rotation (negative values),
otherwise the drive can accelerate in an uncontrolled way!
L
9300 Servo PLC EN 5.0
2−53
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.9Speed setpoint limitation
The speed setpoint limitation can be set under C0909:
CodeLCD
C0909 speed limit
Select the speed setpoint via MCTRL_nNSet_a in [%] of n
n
is selected under C0011. (^ 2−51)
max
2.12.10Phase controller
The phase controller is needed, i.a., to ensure phase−synchronous operation and drift−free standstill.
Parameter setting
1. Assign MCTRL_nPosSet_a to a signal source which provides the phase difference between
set phase and actual phase.
2. Define a value > 0 for MCTRL_nPosLim_a.
3. Set MCTRL_bPosOn_b = TRUE.
4. Set the gain of the phase controller > 0 via C0254.
– Before setting C0254, select a proportional gain for the speed controller as high as possible
under C0070.
– Increase C0254 during operation until the drive shows the required control performance.
The output of the phase controller is added to the speed setpoint.
If the actual phase is lagging, the drive is accelerated.
If the actual phase is leading, the drive is decelerated until the desired phase synchronisation
is achieved.
The influence of the phase controller consists of:
Phase difference multiplied by the gain V
(C0254).
p
Additional influence via an analog signal at MCTRL_nPAdapt_a.
= C0254 MCTRL_nPAdapt_a / 16384)
(V
p
Limitation of the angle controller output to MCTRL_nPosLim_a.
Limitation of the phase controller output
This value limits the maximum compensation speed of the drive in the event of large phase
differences.
2−54
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.11Quick stop (QSP)
The QSP function is used to stop the drive independently of the selected setpoint within an adjustable
time interval.
The QSP function is active if MCTRL_bQsp_b is set = TRUE.
If the SB DCTRL_DriveControl is to trigger QSP, the QSP function must be programmed as
follows:
DCTRL_bQspIn_b
Any Variable
Fig. 2−25Programming of the QSP function if SB DCTRL_DriveControl is to trigger QSP
OR
MCTRL_bQspOut_b
MCTRL_nHiMLim_a
MCTRL_nLoMLim_a
MCTRL_bNMSwt_b
Function:
If torque control is selected, it will be deactivated. The drive is controlled by the speed
controller.
Speed is reduced to 0 within the deceleration time set under C0105:
CodeLCD
C0105 QSP Tif
Possible settings
LenzeSelection
0.000Deceleration time for quick stop (QSP)
0.000{0.001 s}999.900
The torque limits MCTRL_nLoMLim_a and MCTRL_nHiMLim_a are deactivated, i.e. the drive is
operated with
100 %. (^ 2−50)
The phase controller is activated. If the rotor position is shifted actively, the drive generates a
torque against this displacement if
– C0254 is set non−zero,
– MCTRL_nPosLim_a is triggered with a value > 0 %.
C0907/3
C0906/4
C0906/3
C0907/2
Info
Referred to speed change
... 0
n
max
.
L
Stop!
If the field is weakened manually (MCTRL_nFldWeak_a < 100 %), the drive cannot supply the
maximum torque.
9300 Servo PLC EN 5.0
2−55
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.12Field weakening
Adjusting the field weakening range is not required if the motor type has been set under C0086. In
this case all necessary parameters are set automatically.
The motor is operated in the field weakening range if
the output voltage of the controller exceeds the rated motor voltage set under C0090.
the controller cannot increase the output voltage with increasing speed because of the mains
voltage / DC−bus voltage.
Under C0575 you can set a factor between 1 ... 8 to limit the maximum field weakening. "8" means
that the maximum field weakening is 8−fold.
Manual field weakening
The field can be weakened manually via MCTRL_nFldWeak_a.
For maximum excitation MCTRL_nFldWeak_a must be actuated with +100 % (= 16384).
If MCTRL_nFldWeak_a is not assigned (free), the field weakening is automatically +100 %.
Stop!
The available torque is reduced by the field weakening.
2.12.13Switching frequency changeover
The following switching frequencies can be set for the inverter under C0018:
8 kHz for power−optimised operation maximum power output of the controller, but with
audible pulse operation.
16 kHz for noise−optimised operation inaudible pulse operation of the controller, but with
reduced power output (torque).
Automatic changeover between power−optimised and noise−optimised operation.
CodeLCD
C0018 fchop
Automatic switching frequency changeover
You can use the automatic switching frequency changeover if you want to operate the drive in the
noise−optimised range but the torque available in this mode is not high enough for acceleration
processes.
Possible settings
LenzeSelection
1Switching frequency
016/8 kHz automatic changeoverOptimum noise reduction with
)Controller operates with 16 kHz (noise−optimised)
r16
r16
M
(I
) < M < Mr8 (Ir8)Controller switches to 8 kHz (power−optimised)
r16
r16
M > M
max8
(I
)Controller operates with 8 kHz at its current limit
max8
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.14Feedback systems
The following codes can be used to configure the feedback systems for position and speed
controllers:
CodeLCD
[C0420] Encoder const
[C0490] Feedback pos
[C0495] Feedback n
C0497 Nact filter
Possible settings
LenzeSelection
512Encoder: Constant for encoder input
1{1 inc/rev}8192
0Feedback system for the position
IMPORTANT
X8
controller
C0490 = 0, 1, 2 can be mixed
with C0495 = 0, 1, 2.
C0490 = 3, 4 also sets C0495 to
the same value.
0Resolver at X7
1Encoder TTL at X8
2Sin/cos encoder at X8
3Absolute value encoder ST at X8
4Absolute value encoder MT at X8
0Feedback system for the speed
controller
C0495 = 0, 1, 2 can be mixed
with C0490 = 0, 1, 2.
C0495 = 3, 4 also sets C0490 to
the same value.
0Resolver at X7
1Encoder TTL at X8
2Sin/cos encoder at X8
3Absolute value encoder ST (single turn) at X8
4Absolute value encoder MT (multi turn) at X8
2.0Actual speed value filter time constant
0.0{0.1 ms}50.0
0 ms = switched off
PT1
L
9300 Servo PLC EN 5.0
2−57
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.15Touch probe (TP)
Process: The current phase value (digital frequency input value) is saved by a quick interrupt in the
operating system when a signal change occurs at the TP activating input (e.g. X5/E4).
TP
j
Fig. 2−26Function chart of a TP
Time−equidistant start of an interval task
Angle signal
Touch probe configuration
CodeLCD
C0910 TP Delay
C0911 MCTRL TP sel
C0912 MCTRL TP EDGE
The feedback system generating the zero pulse is set under C0490. (^ 2−57)
MCTRL_dnActIncLastScan_p
Possible settings
LenzeSelection
0Touch probe delay
−32767{1 inc}32767
0Touch probe selection
0Touch probe via zero pulse
1Touch probe through digital input X5/E4
0Touch probe activation
0Rising edge TP2
1Falling edge TP2
IMPORTANT
Compensation of delay times of
the TP signal source at X5/E4
For touch probe via digital input
X5/E4
(C0911 = 1)
2−58
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
Function sequence
1. The TP is activated via a signal change at a digital input (X5/E1 ... E4) or via a zero pulse at the
incremental encoder input X8 or the resolver input X7.
2. If a TP has occurred, MCTRL_bActTPReceived_b is set = TRUE.
3. After the start of the task MCTRL_dnActIncLastScan_p indicates the number of increments
[inc/ms] counted since the TP.
4. Then MCTRL_bActTPReceived_b is set = FALSE.
Note!
It is necessary that all three outputs (MCTRL_nNAct_v, MCTRL_bActTPReceived_b and
MCTRL_dnActIncLastScan_p) are processed in the task even if just one signal is required.
For more detailed information about the use of the digital inputs X5/E1 ... E3 for touch probe,
please refer to the "Function library LenzeTpDrv.lib" Manual.
MCTRL_nNAct_v
The value MCTRL_nNAct_v is scaled in increments per millisecond.
(INT) 16384 corresponds to 15000 rpm. See chapter 1.2.7, "Signal types and scalings".
(^ 1−8)
For every task in which MCTRL_nNAct_v is used the operating system creates an individual
integrator that is reset after every start of the task (task−internal process image).
For a safe TP generation, MCTRL_nNAct_v must not be used in the PLC_PRG.
Example (MCTRL_nNAct_v in a 10−ms task):
When the 10−ms task starts, the value of the integrator is saved in a local area of the task and
the integrator is reset. The value in the local area gives an average value in increments per
1 ms.
If a position value is to be derived from this value, then it must be multiplied by
SYSTEM_nTaskInterval / 4 to get the result in increments per
10 ms, as in the example.
Example: In a 1−ms task SYSTEM_nTaskInterval has the value 4 (4 x 0.250s = 1 ms)
In the Lenze FBs this process is already implemented.
L
9300 Servo PLC EN 5.0
2−59
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.16Manual adaptation of motor data
If you use a motor not listed in the selection under C0086, select a motor with similar data under
C0086 and adapt the motor data manually.
Note!
If the physical limit of the drive is considerably exceeded when a motor is configured via C0086 (e.g.:
EVS9321−EI with motor C0086=41 or C0086=42), this may cause a "No program" or "float sys−T.
error".
For more detailed information about commissioning, please refer to the Mounting Instructions for the
9300 Servo PLC!
The following codes help you to manually adapt the motor data:
Speed control with increased
speed control steadiness for
operation with incremental
encoder only (not resolver!).
2Servo async YServo control for asynchronous
3Servo PM−SM YServo control for synchronous motors
22Servo asyncServo control for asynchronous
31ASM Y − ESCServo control for asynchronous
32PM−SM Y − ESCServo control for synchronous motors
33ASM − ESCServo control for asynchronous
I
motors in star connection
in star connection
motors in delta connection
motors in star connection, ESC
in star connection, ESC
motors in delta connection, ESC
limit
max
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
(1.5 * Imotor)
0{0.01 A}1.50 I
0.25Gain of field controller (VpF)
0.00{0.01}15.99
15.0Reset time of field controller (TnF)
1.0{0.5 ms}8000.0
8000 ms = switched off
Rated motor power according to
r
nameplate
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
0.01{0.01 kW}500.00
2−60
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
CodeIMPORTANTPossible settingsLCDCodeIMPORTANT
LCD
[C0084] Mot Rs
SelectionLenze
Stator resistance of the motor
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
0.00{0.01 }100.00
[C0085] Mot Ls
Leakage inductance of the motor
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
0.00{0.01 mH}200.00
[C0087] Mot speed
Rated motor speed
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
300{1 rpm}16000
[C0088] Mot current
Rated motor current
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
0.5{0.1 A}500.0
[C0089] Mot frequency
Rated motor frequency
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
10{1 Hz}1000
[C0090] Mot voltage
Rated motor voltage
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
50{1 V}500
[C0091] Mot cos phi
Motor cos
Dependent on C0086
If C0086 is changed, the value is
reset to the assigned Lenze setting
Change sets C0086 = 0
0.50{0.01}1.00
C0111 Rr tune
100 %Adjustment of the rotor resistance
(Particularly recommended for
non−Lenze motors and high field
weakening.)
Adjustment in % of the rated rotor
resistance of the motor.
50.00{0.01 %}199.99
L
9300 Servo PLC EN 5.0
2−61
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17Monitoring
The 9300 Servo PLC comprises two independent sectors, the motor control and the PLC.
Schnittstellen
Systembus (CAN)
Feldbusse
Leitfrequenz
analoge/digitale I/O
Speicher
(FLASH, EEPROM, RAM)
SPS-Programm
(nach IEC 61131-3, veränderbar)
Technologiefunktionen
Betriebssystem
Antriebssteuerung
Kommunikation
CAN
3
Gleichrichter
mController
Wechselrichter
Motorregelung
DSP
Digital Signal Processor
Normmotor
Asynchronmotor
3~
Synchronmotor
mit Resolver/Encoder
SIN/COS-Geber
The motor control is provided with several monitoring functions which protect the drive from
impermissible operating conditions.
If a monitoring function is activated,
the response set for this monitoring function is triggered.
a corresponding system variable is set to TRUE as long as the trigger condition for the
monitoring function is fulfilled.
The system variables of the monitoring functions can be processed in the application program of
the PLC.
The current error number is also indicated in the variable DCTRL_wFaultNumber of the PLC program.
3
2−62
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
The fault memory (C0168/x) stores the error messages with an offset which indicates the type of the
response:
No. of the error messageType of response
0xxxTRIP
1xxxMessage
2xxxWarning
3xxxFAIL−QSP
Example: C0168/1 = 2061
x061:
The current error (subcode 1 of C0168) is a communication error (error message "CE0"/No.
"x061") between the AIF module and the PLC.
2xxx:
The response is a warning.
Tip!
Occurring faults generally do not affect the operating ability of the PLC!
For more detailed information about the error sources detected by the PLC as well as causes
& remedies, please refer to the appendix (chapter 3.5).
(^ 3−8)
L
9300 Servo PLC EN 5.0
2−63
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
Overview of system error messages of the motor control
Error
No.DisplayCodeTRIPMessage Warning FAIL−QSPOff
x011 OC1Short circuitMCTRL_bShortCircuit_b
x012 OC2Earth faultMCTRL_bEarthFault_b
x015 OC5I x t overloadMCTRL_bIxtOverload_b
x016 OC6I2 x t overloadMCTRL_bI2xtMotorloadOc6_b
x018 OC8I2 x t overloadMCTRL_bI2xtMotorloadOc8_bC0606
x020 OUOvervoltageMCTRL_bOvervoltage_b
x030 LUUndervoltageMCTRL_bUndervoltage_b
x032 LP1Motor phase failureMCTRL_bMotorphaseFail_bC0597
x050 OHHeatsink temperature (fixed)MCTRL_bKuehlGreaterSet−
x053 OH3Motor temperature (fixed)MCTRL_bMotorTempGreater−
x054 OH4Heatsink temperature
x057 OH7Motor temperature (adjustable)MCTRL_bMotorTemp−
x058 OH8Motor temperature (PTC)MCTRL_bPtcOverTemp_bC0585
x082 Sd2Resolver errorMCTRL_bResolverFault_bC0586
x086 Sd6Thermal sensor errorMCTRL_bSensorFaultC0594
x087 Sd7Absolute value encoder error 1)MCTRL_bEncoderFault_b
x088 Sd8Absolute value encoder error 1)MCTRL_bSinCosFault_bC0580
x089 PLError during rotor position
x190 nErrSpeed out of tolerance marginMCTRL_bSpeedLoopFault_bC0579
x200 NMAXMaximum speed exceededMCTRL_bNmaxFault_b
When the error has been eliminated: Deenergise the controller completely!
Monitoring functionSystem variable
Value_b
SetValue_b
MCTRL_bKuehlGreaterC0122_bC0582
(adjustable)
GreaterC0121_b
MCTRL_bRotorPositionFault_b
adjustment
Possible responses
Lenze setting Setting possible
C0583
C0584
2−64
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
Response and effect on the drive
Response Effect
TRIP
TRIP active: The power outputs U, V, W are switched to high resistance.
The drive is coasting (no control!).
TRIP reset: The drive runs to its setpoint along the set ramps.
Message
The drive restarts automatically when the message is no longer present!
Message active: The power outputs U, V, W are switched to high resistance.
0.5 s The drive is coasting (no control!).
0.5 s The drive is coasting (due to internal controller inhibit!). If required, restart program.
Message reset: The drive runs to its setpoint with the maximum torque.
Warning
The drive can be destroyed as a result of deactivated monitoring functions!
The failure merely is displayed, the drive runs on in a controlled manner.
FAIL−QSP−−−
The drive is decelerated to standstill along the QSP ramp (C0105).
Off−−−
The drive can be destroyed as a result of deactivated monitoring functions!
There is no response to the failure!
Keypad display
RDYIMPFAIL
= off = on
L
9300 Servo PLC EN 5.0
2−65
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.1OC1 − short−circuit monitoring
This monitoring function protects the drive controller.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x011 OC1Short circuitMCTRL_bShortCircuit_b
Monitoring functionSystem variable
Monitoring is actuated in the event of a short circuit in the motor phases. This can also be caused
by an interturn fault in the machine.
Monitoring can also respond during power−up if an earth fault occurs.
If monitoring responds, the drive controller has to be disconnected from the mains and the
short circuit has to be eliminated.
2.12.17.2OC2 − earth−fault monitoring
This monitoring function protects the drive controller.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x012 OC2Earth faultMCTRL_bEarthFault_b
The 9300 Servo PLC is equipped with earth−fault detection as standard.
If monitoring is actuated, the drive controller has to be disconnected from the mains and the
earth fault has to be eliminated.
Possible causes of an earth fault:
Short circuit to frame of the machine
Short circuit of a phase to the shield
Short circuit of a phase to PE
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
Possible responses
Lenze setting
Setting possible
2−66
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.3OC5 − I x t overload monitoring
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x015 OC5I x t overloadMCTRL_bIxtOverload_b
Monitoring functionSystem variable
Overcurrent diagram for OC5 fault message
The following diagram shows the maximum permissible overcurrent as a function of time:
Fig. 2−27Overcurrent diagram
The maximum permissible overcurrent is dependent on the I
I
limit sender under C0022 150 % IN:
max
Within a period of 180 s, the arithmetic mean value of the motor current may not exceed 100
% of the rated device current.
I[%]
Motor
200
150
100
75
44
1060120180
max
Possible responses
Lenze setting
Setting possible
t [s]
limit set under C0022. (^ 2−60)
Example: Arithmetic mean value to curve :
I
limit set under C0022 > 150 % Ir:
max
60 s @ 150 % ) 120 s @ 75 %
180 s
+ 100 %
Within a period of 60 s, the arithmetic mean value of the motor current may not exceed 70 %
of the rated device current.
Example: Arithmetic mean value to curve :
10 s @ 200 % ) 50 s @ 44 %
60 s
The current controller load is displayed in C0064:
CodeLCD
C0064 Utilization
Possible settings
LenzeSelection
g
0{1 %}150
+ 70 %
IMPORTANT
Controller load I x t during the last
180 seconds
C0064 >100 % trips OC5.
TRIP−RESET is only possible if
C0064 < 95 %.
L
9300 Servo PLC EN 5.0
2−67
9300 Servo PLC
Ȣ
ǒ
Ǔ
Ȥ
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.4OC6 − I2 x t overload monitoring
The I2 × t load of the motor is continuously calculated by the controller and displayed in C0066.
2
x t monitoring is dimensioned in such a way that it is triggered after 179 s in case of a motor with
I
a thermal motor time constant of 5 minutes, a motor current of 1.5 x I
100 %.
Two adjustable trigger thresholds serve to define different responses.
Adjustable response OC8 (TRIP, warning, off).
– The response is set in C0606.
– The trigger threshold is set in C0127.
– The OC8 response can be used for advance warning.
Fixed response OC6−TRIP.
– The trigger threshold is set in C0120.
Behaviour of the I2 x t monitoringCondition
I2 x t monitoring is deactivated.
C0066 = 0 % and
I2 x t monitoring is stopped.
The current value in C0066 is frozen.
I2 x t monitoring is deactivated.
The motor utilisation is displayed in C0066.
An error message OC6 or OC8 can only be reset if the I2 × t load has exceeded the set trigger
threshold by 5 %.
and a trigger threshold of
r
When C0120 = 0 % and C0127 = 0 %, set controller inhibit.
When C0120 = 0 % and C0127 = 0 %, activate controller enable.
Set C0606 = 3 (off) and C0127 > 0 %.
Calculate release time
IMActual motor current
IrRated motor current
yC0120 or C0127
t +*(C0128) @ ln
ȡ
ȧ
1 *
I
M
I
r
y ) 1
2
@ 100
ȣ
ȧ
The thermal loading capacity of the motor is expressed by the thermal motor time constant
(C0128). The value can be obtained from the rated motor data or contact the manufacturer of
the motor.
Read release time in the diagram
Diagram for detecting the release times of a motor with a thermal motor time constant of 5 min:
2
I t [%]
120
100
50
Fig. 2−28I2 × t monitoring: Release times with different motor currents and trigger thresholds
ImotMotor current
I
r
I2tI2t load
tTime
I=3 ×I
motr
0
0100200300400500600700800900
Rated motor current
I=2 ×I
motr
I=1.5 ×I
motr
I=1 ×I
motr
1000
t [s]
9300std105
2−68
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.5OU − overvoltage monitoring
This function monitors the DC bus and protects the controller.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x020 OUOvervoltageMCTRL_bOvervoltage_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
Monitoring is actuated if the DC bus voltage at the terminals +UG and −UG exceeds a switch−off
threshold dependent on C0173, and it remains active until the value falls below the respective
switch−on threshold again.
The DC−bus voltage is set under C0173:
CodeLCD
[C0173] UG limit1Adaptation of DC−bus voltage
Possible settings
LenzeSelection
0Mains < 400 V; with or without brake unit
1Mains = 400 V; with or without brake unit
2Mains = 460 V; with or without brake unit
3Mains = 480 V; without brake unit
4Mains = 480 V; with brake unit
IMPORTANT
thresholds
Check during commissioning and
adapt if necessary
All drive components in
interconnected drives must have
the same thresholds
The switch−off and switch−on thresholds dependent on C0173 can be gathered from the
following table:
Setting of C0173Switch−off thresholdSwitch−on threshold
0Mains < 400 V; with or without brake unit770 V755 V
1Mains = 400 V; with or without brake unit770 V755 V
2Mains = 460 V; with or without brake unit770 V755 V
3Mains = 480 V; without brake unit770 V755 V
4Mains = 480 V; with brake unit800 V785 V
The switch−off threshold defines the voltage level of the DC−bus voltage, at which the pulse
inhibit is activated.
L
9300 Servo PLC EN 5.0
2−69
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
Braking torque derating
Without a braking system being connected (934X power supply module or 935X braking unit), the
braking torque is automatically derated when the DC−bus voltage reaches the following value:
Schwelle für Bremsmomentreduzierung + Abschaltschwelle * OV reduce
The "OV reduce" value is set under C0172:
CodeLCD
[C0172] 0V reduce10Threshold for activating the braking
Example:
Possible settings
LenzeSelection
0{10 V}100
IMPORTANT
torque derating before OU trip
C0173 = 3 Switch−off threshold = 770 V
C0172 = 10 "OV reduce" = 10 V
Schwelle für Bremsmomentreduzierung + 770 V * 10 V + 760 V
The braking torque is derated as soon as the DC−bus voltage reaches or exceeds 760 V.
Braking with active braking torque derating generates clearly audible motor noise.
Tip!
If the monitoring system responds frequently, the drive dimensioning may be inappropriate (too
much braking energy being generated).
Remedy: Use 934X power supply module or (additional) 935X braking units.
When several controllers are operated simultaneously, a DC−bus connection may be useful. In
this way the braking energy generated by one drive can be used to drive another drive. Only
the energy difference is taken from the mains.
2−70
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.6LU − undervoltage monitoring
This function monitors the DC bus and protects the controller.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x030 LUUndervoltageMCTRL_bUndervoltage_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
The monitoring responds if the DC−bus voltage at the terminals +UG and −UG falls below a switch−off
threshold dependent on C0173 and it remains active until the corresponding switch−on threshold has
again been exceeded.
The DC−bus voltage is set under C0173 (^ 2−69).
The switch−off and switch−on thresholds dependent on C0173 can be gathered from the
following table:
Setting of C0173Switch−off thresholdSwitch−on threshold
0Mains < 400 V; with or without brake unit285 V430 V
1Mains = 400 V; with or without brake unit285 V430 V
2Mains = 460 V; with or without brake unit328 V473 V
3Mains = 480 V; without brake unit342 V487 V
4Mains = 480 V; with brake unit342 V487 V
The switch−off threshold defines the voltage level of the DC−bus voltage, at which the pulse
inhibit is activated.
Tip!
If the undervoltage lasts longer than 3 s or if the drive is powered up, this is entered into the fault
memory.
This can be the case if the control module is supplied externally via the terminals X5/39 and
X5/59 and the mains is switched off.
If the undervoltage has been eliminated (reconnection to the mains), the entry is not updated
in the fault memory but deleted because this is not an error but a controller status.
Undervoltages which last for less than 3 s are interpreted as a fault (e.g. power system fault) and
entered into the fault memory. In this case the fault memory is updated.
L
9300 Servo PLC EN 5.0
2−71
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.7LP1 − monitoring of the motor phases
This monitoring function checks if a motor phase has failed.
Note!
This monitoring function can only be used for asynchronous motors.
When this monitoring function is activated, the calculating time available for the user is
The monitoring limit is set under C0599.
The response is set under C0597.
CodeLCD
C0597 MONIT LP1
C0599 Limit LP1
Error acknowledgement
1. Check motor cables.
2. Execute TRIP−RESET.
Possible settings
LenzeSelection
3Configuration of motor phase
0TRIP
2Warning
3Off
5LP1 fault monitoring limit
0.01{0.01 %}10.00
IMPORTANT
monitoring (LP1)
2−72
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.8OH − heatsink temperature monitoring (fixed)
This monitoring function protects the drive controller.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x050 OHHeatsink temperature (fixed)MCTRL_bKuehlGreaterSet−
Monitoring functionSystem variable
Value_b
Possible responses
Lenze setting
Setting possible
MCTRL_bKuehlGreaterSetValue_b is derived from a comparator with hysteresis. The switch−off
threshold and the hysteresis are fixed:
The switch−off threshold is 85 °C
The hysteresis is 5 K, i.e. the value for switching on again is 80 ºC.
The following causes can bring about an actuation of the monitoring process:
CauseRemedy
The ambient temperature is too high.Mount a blower in the control cabinet.
The drive controller is overloaded in the arithmetic mean, i. e. overload
and recovery phase exceed 100%.
Mount a blower in the control cabinet.
Shorten overload phase.
Use a more powerful drive controller.
L
9300 Servo PLC EN 5.0
2−73
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.9OH3 − motor temperature monitoring (fixed)
This monitoring function protects the motor against overheating.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x053 OH3Motor temperature (fixed)MCTRL_bMotorTempGreater−
Monitoring functionSystem variable
SetValue_b
Possible responses
Lenze setting
Setting possible
MCTRL_bMotorTempGreaterSetValue_b is derived from a comparator with hysteresis. The
switch−off threshold and the hysteresis are fixed:
The switch−off threshold is 150 °C
The hysteresis is 15 K, i.e. the value for switching on again is 135 ºC.
This monitoring only applies to the temperature sensor specified by Lenze as it is, for instance,
included in the Lenze standard servo motor.
The Sub−D connectors X7 or X8 are available as inputs.
Stop!
The temperature sensor may either be connected to X7 or to X8; the respective other input for the
temperature sensor must be free!
This monitoring is active in the Lenze setting and is thus triggered when you use a non−Lenze servo
motor!
The response is set under C0583:
CodeLCD
C0583 MONIT OH3Monitoring configuration: Motor
Possible settings
LenzeSelection
0TRIP
3Off
IMPORTANT
temperature
(Motor temperature > fixed limit
temperature)
Dependent on C0086
2−74
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.10 OH4 − heatsink temperature monitoring (adjustable)
This monitoring function protects the drive controller.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x054 OH4Heatsink temperature (adjustable)MCTRL_bKuehlGreaterC0122_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
This monitoring function is designed as an early warning stage before final disconnection of the drive
controller by means of TRIP (OH) via the monitoring function "heatsink temperature (fixed)".
(^ 2−73)
With this function the process can be influenced to avoid a switch−off of the controller at an
unfavourable moment.
Furthermore, for instance, additional fans, which would cause an unacceptable noise in
continuous operation, can also be switched on and off.
MCTRL_bKuehlGreaterC0122_b is derived from a comparator with hysteresis.
The operating threshold is set under C0122.
Hysteresis is 5 K (fixed), i. e. monitoring is reset at 5 K below the operation threshold that has
been set.
The response is set under C0582.
CodeLCD
C0122 OH4 limit
C0582 MONIT OH4
Possible settings
LenzeSelection
85Temperature threshold for heatsink
45{1 °C}85
2Configuration of monitoring
2Warning
3Off
IMPORTANT
temperature prewarning
"Tht > C0122" (fault OH4)
L
9300 Servo PLC EN 5.0
2−75
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.11 OH7 − motor temperature monitoring (adjustable)
This monitoring function monitors the process.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x057 OH7Motor temperature (adjustable)MCTRL_bMotorTemp−
Monitoring functionSystem variable
GreaterC0121_b
Possible responses
Lenze setting
Setting possible
This monitoring function is designed as an early warning stage before final disconnection of the drive
controller by means of TRIP (OH3) via the monitoring function "motor temperature (fixed)".
(^ 2−74)
With this function the process can be influenced to avoid a switch−off of the motor at an
unfavourable moment.
Furthermore, for instance, additional fans, which would cause an unacceptable noise in
continuous operation, can be switched on and off.
MCTRL_bMotorTempGreaterC0121_bis derived from a comparator with hysteresis.
The operating threshold is set under C0121.
Hysteresis is 15 K (fixed), i. e. monitoring is reset at 15 K below the operation threshold that
has been set.
The response is set under C0584.
CodeLCD
C0121 OH7 limit150Temperature threshold for motor
C0584 MONIT OH7Monitoring configuration: Motor
Possible settings
LenzeSelection
45{1 °C}150
2Warning
3Off
IMPORTANT
temperature prewarning
"TMot > C0121" (fault OH7)
temperature
(Motor temperature > variable limit
temperature C0121)
Dependent on C0086
Temperature monitoring via
resolver input
2−76
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.12 OH8 − motor temperature monitoring via T1, T2
This monitoring function protects the motor.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x058 OH8Motor temperature (PTC)MCTRL_bPtcOverTemp_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
MCTRL_bPTCOverTemp_b is derived from the digital signal across the terminals T1, T2 next to the
power terminals UVW.
The switch−off threshold and the hysteresis depend on the encoder system (DIN 44081).
The response is set under C0585:
CodeLCD
C0585 MONIT OH83Monitoring configuration: Motor
Possible settings
LenzeSelection
0TRIP
2Warning
3Off
IMPORTANT
temperature
(Motor temperature across T1/T2 too
high)
Temperature monitoring via PTC
input
Stop!
If you use the inputs T1, T2 to protect the motor, the monitoring response should not be "Warning"
or "Off" since the motor could be damaged or destroyed in the event of more overload!
L
9300 Servo PLC EN 5.0
2−77
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.13 Sd2 − resolver monitoring for open circuit
This monitoring function monitors the resolver feed cable and the resolver for open circuits and
protects the motor.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x082 Sd2Resolver errorMCTRL_bResolverFault_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
Stop!
If the monitoring is switched off, the machine can reach very high speeds in the event of faults (e. g.
system cable is disconnected or not correctly screwed), which can result in the damage of the motor
and of the driven machine! The same applies if "warning" is set as a response.
For commissioning, always use the Lenze setting C0586 = 0 (TRIP).
Only use the configuration C0586 = 2 (warning) and C0586 = 3 (monitoring switched off) if
monitoring is triggered without any obvious reason (e.g. due to long cables or intense
interference injection caused by other devices). Despite faulty feedback, the pulses are
enabled.
If a fault has occurred in the actual speed detection, it is possible that the overspeed monitoring
(NMAX) does not respond as expected.
This monitoring
– is automatically activated if the resolver is selected as an actual speed value encoder under
C0025 (C0025 = 10).
– is automatically deactivated if another actual speed value encoder is selected.
2.12.17.14 Sd6 − motor temperature sensor monitoring
This monitoring function checks whether the motor temperature sensor supplies values within the
measuring range of −50 ... +250 °C.
If the values are out of this measuring range, monitoring is triggered.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x086 Sd6Thermal sensor errorMCTRL_bSensorFault
Monitoring functionSystem variable
The response is set under C0586:
CodeLCD
C0594 MONIT SD6Monitoring configuration: Motor
Possible settings
LenzeSelection
0TRIP
2Warning
3Off
2.12.17.15 Sd7 − absolute value encoder monitoring
This monitoring function repeatedly reads in the absolute value of the encoder when the PLC is
switched on to find out if the same value is transmitted to the drive.
If a deviation > 5 % is detected at the motor shaft, the monitoring (TRIP) is actuated.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x087 Sd7Absolute value encoder errorMCTRL_bEncoderFault_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
IMPORTANT
temperature sensor error
(X7 or X8)
Dependent on C0086
Possible responses
Lenze setting
Setting possible
L
9300 Servo PLC EN 5.0
2−79
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.16 Sd8 − sin/cos encoder monitoring during operation
This monitoring function performs a plausibility check to find out whether the encoder is available and
the sin/cos tracks supply plausible values with regard to each other.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x088 Sd8Absolute value encoder errorMCTRL_bSinCosFault_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
The following sin/cos encoder types are supported:
– Stegmann SCS 60/70 ST 512 single−turn absolute value encoder (512 inc/rev)
– Stegmann SCM 60/70 ST 512 multi−turn absolute value encoder (512 inc/rev)
The error "Sd8" can only be reset by mains switching.
It may be necessary that the encoder has to move a few angular degrees for triggering an
error.
The response is set under C0580:
CodeLCD
C0580 MONIT SD8
Possible settings
LenzeSelection
3Monitoring configuration: Sin/cos
0TRIP
3Off
IMPORTANT
encoder
Note!
If the encoder is to be monitored and, especially, if synchronous machines are used, the error
response should be set to "TRIP".
For further encoder reliability, the monitoring of following errors can, for example, additionally be
activated for positioning systems. This error response should also be set to "TRIP".
Apparent errorsHidden errors
Unplugged connectors, all encoder signals open.
Single open circuit, one of the following signals is missing:
– COS A
– RefCOS A
– SIN B
– RefSIN B
– GND
– VCC
Double open circuit with the following signal pairs:
– COS A and RefCOS A
– SIN B and RefSIN B
– COS A and SIN B
– RefCOS A and RefSIN B
– or all four signals (COS A, RefCOS A, SIN B, RefSIN B) open.
Short circuits, especially between the sine and cosine signals.
Cable/encoder interferences with intermediate values
"Semi"−short circuits (> 0 Ohm)
"Semi"−interruptions (< infinite)
2−80
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.17 PL − monitoring of the rotor position adjustment
This monitoring function monitors the correct execution of the rotor position adjustment.
Note!
The PL monitoring is only activated when a synchronous machine (C0006 = 3) is selected.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x089 PLError during rotor position adjustment MCTRL_bRotorPositionFault_b
Error triggering
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
If an Sd7 error occurs during the rotor position adjustment with an absolute value encoder, a
TRIP will occur after the subsequent mains switching.
If a rotor position adjustment with any encoder is aborted (e.g. by C0095 = 0 or switch−off), a
TRIP will occur.
Error acknowledgement
Note!
For acknowledging the error, a synchronous machine (C0006 = 3) must be selected.
1. Activate rotor position adjustment with C0095 = 1.
2. Execute TRIP−RESET.
3. Re−execute the rotor position adjustment with controller enable.
L
9300 Servo PLC EN 5.0
2−81
9300 Servo PLC
System blocks
2.12MCTRL_MotorControl (node number 131)
2.12.17.18 nErr − speed monitoring (speed out of tolerance margin)
This monitoring function compares the actual speed value supplied by the speed encoder to the
speed setpoint on the speed controller. If the difference between the two speed values exceeds the
tolerance margin set in C0576, the monitoring function is actuated.
Error
No.DisplayTRIPMessage Warning FAIL−QSPOff
x190 nErrSpeed out of tolerance marginMCTRL_bSpeedLoopFault_b
Monitoring functionSystem variable
Possible responses
Lenze setting
Setting possible
This monitoring function can be used to evaluate the speed following behaviour of the controller.
If the system deviation exceeds a certain value, this may indicate a drive problem. In this case,
the drive cannot follow the set speed setpoint for some reason. With operational controllers,
this may be caused by mechanical blockades on the load side, or by an insufficient motor
torque.
Furthermore, this monitoring function can be used for additional speed encoder protection in
speed−controlled operation. This monitoring function thus supplements the individual encoder
monitoring functions.
Errors on the encoder system bring about an incorrect actual speed value. This usually results
in a system deviation on the speed controller that is greater than that during normal operation.
The tolerance margin is set via C0576:
The response is set via C0579:
CodeLCD
C0576 nErr Window100Tolerance margin for speed
C0579 MONIT nErr3Speed monitoring configuration
Possible settings
LenzeSelection
0{1 %}100
0TRIP
1Message
2Warning
3Off
4FAIL−QSP
IMPORTANT
monitoring
Referred to n
100 % = lowest monitoring
sensitivity.
max
.
2−82
Note!
If the encoder is to be monitored, set the error response to "TRIP".
To ensure that there are no false alarms, it might be necessary to adapt the setpoint/quick
stop ramps (by means of longer time intervals) to the application.
The selected tolerance margin (C0576) should be at least twice as high as the system
deviation occurring during operation. The deviation can be determined by means of
appropriate tests during commissioning.
The monitoring responds when the current speed exceeds the upper speed limit of the system or the
double value of C0011 (n
max
).
Stop!
For active loads (e. g. hoists) ensure torque−free operation of the drive. Special
system−specific measures are required!
If the actual speed value encoder fails, the monitoring may fail to respond.
The upper system speed is set under C0596:
CodeLCD
C0596 NMAX limit
Possible settings
LenzeSelection
5500Monitoring configuration: Max. speed
0{1 rpm}16000
IMPORTANT
of the machine
L
9300 Servo PLC EN 5.0
2−83
9300 Servo PLC
System blocks
2.13MCTRL_AUX_HighResFeedback (node number 181)
2.13MCTRL_AUX_HighResFeedback (node number 181)
High−resolution encoder
Use this SB only after consulting with Lenze!
2.13.1Inputs_MCTRL_AUX_HighResFeedback
VariableData typeData typeAddressDisplay
MCTRL_AUX_
dnEncoderAngle
Double
integer
Position%ID181.0High−resolution encoder position
2.13.2Outputs_MCTRL_AUX_HighResFeedback
VariableData typeData typeAddressDisplay
MCTRL_AUX_
wEncoderMask
Word−%QW181.0
code
code
Display
format
Display
format
Note
Note
Mask for high−resolution encoder
position
2−84
9300 Servo PLC EN 5.0
L
9300 Servo PLC
System blocks
2.14STATEBUS_IO (node number 51)
2.14STATEBUS_IO (node number 51)
The state bus is a bus system specifically designed for Lenze controllers/PLCs.
This SB can set the state bus to LOW level and thus set all nodes connected to the state bus to a
previously selected status (e.g. TRIP, quick stop (QSP) or controller inhibit (CINH)).
The SB immediately detects when a node sets the state bus to LOW level and the corresponding
control signal can be processed in the PLC program.
Fig. 2−29STATEBUS_IO
Variable
STATEBUS_bOut_bBoolBinary%QX51.0.4C0441binLOW signal output
STATEBUS_bIn_bBoolBinary%IX51.0.6−−LOW signal detection
Every device connected to the state bus can set the state bus to LOW level (multi−master
operation).
A maximum of 20 devices (controllers/PLCs) can be networked via the state bus.
9300 Servo PLC / 932X / 933X
Data typeSignal typeAddressDisplay
L2L1L3PE+UG -UG
VUW ST 39 ST PE 28 A4PE
STATE_BUS_bOut_b
9300 Servo PLC / 932X / 933X
+10V
1
C0441
L2L1L3PE+UG -UG
VUW ST 39 ST PE 28 A4PE
STATEBUS_IO
STATE_BUS_bIn_b
code
ST
ST
X5
Display
format
L2L1L3PE+UG -UG
9300 Servo PLC / 932X / 933X
VUW ST 39 ST PE 28 A4PE
Note
Fig. 2−30Networking via the state bus
Stop!
Do not connect an external voltage to terminals X5/ST!
L
9300 Servo PLC EN 5.0
2−85
9300 Servo PLC
System blocks
2.15SYSTEM_FLAGS (system flags, node number 151)
2.15SYSTEM_FLAGS (system flags, node number 151)
System flags are global variables which are permanently integrated into the run−time system. They
include functions that facilitate programming.
2.15.1Inputs SYSTEM_FLAGS
The following system flags are included in the DrivePLC:
VariableData typeAddressNotes
SYSTEM_bClock01Hz
SYSTEM_bClock1Hz%IX151.0.81.0 Hz system clock
SYSTEM_bClock10Hz%IX151.1.010 Hz system clock
SYSTEM_bClock0100Hz%IX151.1.8100 Hz system clock
SYSTEM_bTogCycleTask%IX151.2.0Toggle flag cyclic task
SYSTEM_b1LoopCyclicTask%IX151.2.8First loop cyclic task
SYSTEM_b1LoopTask2%IX151.3.0First loop task ID2
SYSTEM_b1LoopTask3%IX151.3.8First loop task ID3
SYSTEM_b1LoopTask4%IX151.4.0First loop task ID4
SYSTEM_b1LoopTask5%IX151.4.8First loop task ID5
SYSTEM_b1LoopTask6%IX151.5.0First loop task ID6
SYSTEM_b1LoopTask7%IX151.5.8First loop task ID7
SYSTEM_b1LoopTask8%IX151.6.0First loop task ID8
SYSTEM_b1LoopTask9%IX151.6.8First loop task ID9
SYSTEM_nTaskInterval
SYSTEM_nTaskID%IW151.8ID−number of current task
Bool
Integer
%IX151.0.00.1 Hz system clock
%IW151.7Interval of current task
Tip!
The system variables are not generated in simulation mode.
SYSTEM_bClockxHz
These system flags output a fixed clock pulse with an equal pulse/pause ratio.
The flag is toggled in real time.
When you use this system flag, take care with the frequency used for polling the flag (aliasing
effect). You should use at least twice the toggle frequency.
Note!
The system flags SYSTEM_bClockxHz must not be used to trigger event−controlled tasks. Use
time−controlled tasks for this.
Example:
You would like to use the system flag SYSTEM_bClock100Hz as a clock for a counter.
The pulse/pause ratio is 5 ms/5 ms.
2−86
To avoid an aliasing effect, the counter must always be polled with an INTERVAL TASK < 5 ms.
9300 Servo PLC EN 5.0
L
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.