9300 Servo PLC
9300 Servo PLC
L
Manual
Global Drive
9300 Servo PLC
Show/Hide Bookmarks
This Manual for the Drive PLC Developer Studio as from V01.00 is valid for the following
Lenze automation systems:
Automation system Type as from hardware version as from software version
9300 Servo PLC EVS93XX-xl 2l 02
9300 Servo PLC EVS93XX-xT 2K 10
Important Note :
The software is made available to the user in the currently existing form. All risks with regard to the quality and the results arising from its
use remain the responsibility of the user. The user must implement the appropriate security precautions against possible erroneous
application.
We do not accept any responsibilty for direct or consequential damages, such as loss of profits, loss of orders, or effects on the course of
business of any kind.
9300ServoPLC EN 1.4 i
Show/Hide Bookmarks
ii 9300ServoPLC EN 1.4
Show/Hide Bookmarks
3 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 System bus (CAN) in the Lenze drive system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.1 Contact assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.2 Wiring of the system bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.1.2.1 System bus wiring complying to EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.1.3 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.1.3.1 General data of the system bus network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.1.3.2 Feasible bus length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.1.3.3 Communication times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.1.4 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.1.5 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.1.5.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3.1.5.2 Parameter channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.1.5.3 Process data channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3.2 System blocks for the system bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.2.1 System bus (CAN1_IO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.2.1.1 Inputs_CAN1 (CAN1_IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.2.1.2 Outputs_CAN1 (CAN1_OUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.2.2 System bus (CAN2_IO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3.2.2.1 Inputs_CAN2 (CAN2_IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3.2.2.2 Outputs_CAN2 (CAN2_OUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
3.2.3 System bus (CAN3_IO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3.2.3.1 Inputs_CAN3 (CAN3_IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3.2.3.2 Outputs_CAN3 (CAN3_OUT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
3.2.4 Systembus Management (CAN_Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
3.3 Synchronization of control program cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
3.3.1 CAN_Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
3.4 Application example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
3.4.1 Programming the application example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
3.4.2 Description of the codes for the system bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.4.2.1 Baud-rate setting C0351 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.4.2.2 Defining a master in a drive group C0352 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.4.2.3 General address assignment C0350 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
3.4.2.4 Selective addressing of the individual process-data objects C0353, C0354 . . . . . . 3-34
3.4.2.5 Display code of the resulting identifier C0355 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
3.4.2.6 Boot-Up setting C0356/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
3.4.2.7 Diagnosis codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
3.4.2.8 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
3.4.3 Communication profile of the system bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
3.4.3.1 Data description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
3.4.3.2 Addressing the drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
3.4.4 The communication phases of the CAN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
3.4.5 Parameterization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
3.4.5.1 Example: Write a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
3.4.5.2 Example: Read a parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
3.4.6 Process data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
3.4.6.1 Cyclical process-data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
3.4.6.2 Event-controlled process-data objects, optionally with adjustable cycle time . . . . . 3-52
4 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 PLC functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 System POUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.3.1 Reactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.3.2 Possible settings for error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.4 Tripping (L_FWM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.6 Fault analysis with the history buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.6.1 Structure of the history buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.6.2 Working with the history buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.7 Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
4.8 Reset of fault messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.9 Code table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.10 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
iv 9300ServoPLC EN 1.4
Show/Hide Bookmarks
Tip!
Information on
• DC bus connection
• Use of brake units
• Automation (field bus modules)
• Accessories and motors
• and selection help
for controllers of the 9300 series can be found in the Manual 9300 Planning,
which you can order separately from Lenze.
Variable names
are shown in the explanatory texts in italics:
• “The signal at nIn_a ...”
The concept for the new automation system does not use direct codes in the
programming. The IEC1131-3 standard is used instead.
• This standard is based on a structure of variable names.
• If the user applies variables in his project, then he can name the variables as he chooses.
In order to avoid the growth of a multitude of different conventions for naming variables in existing
and future projects and function libraries that are programmed by Lenze personnel, we have set up
software guidelines that must be followed by all Lenze staff.
In this convention for creating variable names, Lenze keeps to the Hungarian Notation, that has been
specifically expanded by Lenze.
If you make use of Lenze-specific functions or function blocks, you will immediately be able to see,
for instance, which data type you must transfer to a function block, and which type of data you will
receive as an output value.
Variable names
consist of
• a prefix (optional)
• a data-type entry
• and an identifier
The prefix and data-type entry are usually formed by one or two characters. The identifier (the
“proper” name) should indicate the application, and is therefore usually somewhat longer.
Prefix examples
Prefix Meaning
a array (combined type), field
p pointer
Examples:
Array of integers anJogValue[10];
Bool bIsEmpty;
Word wNumberOfValues;
Integer nLoop ;
Byte byCurrentSelectedJogValue;
Example
for a global array of type integer, that includes fixed setpoints (analog) for a speed setting:
g_anFixSetSpeedValue_a
Tip!
Normalizing to signal type phase-angle difference/speed: 16384 (INT) 15000 rpm
Normalizing to signal type analog: 16384 100 % value under [C0011] = Nmax
Normalizing to signal type angle or position: 65536 1 motor turn
Examples:
Examples:
AIN1_nIn_a
CAN1_bCtrlTripSet_b
DIGIN_bIn3_b
2 System blocks
2.1 Introduction
For a long time, Lenze has followed the principle of describing inverter functions with the aid of
function blocks (FB’s). This principle may also be found in the IEC1131-3 standard.
• The function library includes functions that you can apply as software functions in your
project.
• In addition, quasi-hardware functions are available, as system blocks. (SBs).
CPU x x x x x x
• The CPU can access the inserted cards directly, and process the resulting information.
• The individual expansion cards each have a fixed address for access.
With the Lenze Automation System, the system blocks correspond to these inserted cards!
System blocks are thus special (quasi-hardware)function blocks that are permanently integrated into
the run-time system (e.g. 9300 Servo PLC, Drive PLC).
• These function blocks can also partially address real hardware.
• The assignment/identification of the system blocks is made through module numbers.
• The access to the inputs/outputs of the system blocks is made directly through I/O-variables
or fixed memory addresses.
Example:
On example of a system block is the digital I/O-function block “DIGITAL_IO”.
• Access to the digital input 1 of this SB can be made through the absolute address
(e.g. %IX1.0.1) or via the corresponding I/O-variable (DIGIN_bIn1_b ).
POE-Input POE-Output
SB-Output SB-Input
SB POE SB
Tip!
The assignments as inputs and outputs are always made from the program viewpoint!
This means that logical system-block outputs are seen by the POEs as hardware-side inputs, and
system-block inputs are seen as outputs.
Access to the digital input 1 can only be made through the absolute address %IX1.0.1 or through
the system-variable names DIGIN_bIn1_b :
%IX1.0.1 POE DIGIN_bIn1_b POE
Tip!
According to IEC1131, only one copy of the digital input can be transferred, and this system variable
must be of type VAR_INPUT
Tip!
Please observe the corresponding Operating Instructions for the fieldbus module that is plugged in.
A IF 1 _ IN 1 6 B it
A I F 1 _ w D c t r lC tr l
A IF 1 _ b C tr lQ u ic k s to p _ b
A I F 1 _ b C tr lD is a b le _ b
A IF 1 _ b C tr lC In h ib it_ b
A IF 1 _ b C tr lT r ip S e t_ b
B it 0
A IF 1 _ b C tr lT r ip R e s e t_ b
A IF 1 _ b C tr lB 0 _ b
A IF 1 _ b C tr lB 1 _ b
A IF 1 _ b C tr lB 2 _ b
1 6
A IF 1 _ b C tr lB 4 _ b
B y te 1 ,2
b in a r y
s ig n a ls A IF 1 _ b C tr lB 5 _ b
A IF 1 _ b C tr lB 6 _ b
A IF 1 _ b C tr lB 7 _ b
A IF 1 _ b C tr lB 1 2 _ b
B it 1 5 A IF 1 _ b C tr lB 1 3 _ b
A IF 1 _ b C tr lB 1 4 _ b
A IF 1 _ b C tr lB 1 5 _ b
C 0 1 3 6 /3
3 ,4
A IF 1 _ n In W 1 _ a
B y te
1 6 B it
C 0 8 5 6 /1 A IF 1 _ n In W 2 _ a
A u to m a tio n 1 6 B it
In te rfa c e C 0 8 5 6 /2
A IF 1 _ n In W 3 _ a
1 6 B it
C 0 8 5 6 /3 A IF 1 _ b In B 0 _ b
C 0 8 5 5 /1 A IF 1 _ b In B 2 _ b
...
5 ,6
1 6
b in a r y A IF 1 _ b In B 1 4 _ b
B y te
s ig n a ls
A IF 1 _ b In B 1 5 _ b
A IF 1 _ b In B 1 6 _ b
C 0 8 5 5 /2 A IF 1 _ b In B 1 7 _ b
...
1 6
b in a r y A IF 1 _ b In B 3 0 _ b
s ig n a ls
A IF 1 _ b In B 3 1 _ b
7 ,8
B y te
1 6 B it
L o w W o rd
A IF 1 _ d n In D 1 _ p
1 6 B it
C 0 8 5 7
H ig h W o r d
Function
The input signals of the 8 byte user data of the AIF-object are converted into corresponding signal
types.
Byte 1 and 2
Byte 1,2 can be used simultaneously as
• binary information (up to 16 bits),
• as word (e.g. as control word)
Bytes 3 and 4
Bytes 3-4 form the signal for AIF1_nInW1_a.
Tip!
Please observe the corresponding Operating Instructions for the fieldbus module that is plugged in.
A IF 1 _ O U T B it 0
A IF 1 _ w D c tr lS ta t
B y te 1 ,2
1 6 B it
A IF 1 _ n O u tW 1 _ a B it 1 5
C 0 8 5 8 /1
A IF 1 _ n O u tW 2 _ a
3 ,4
C 0 8 5 8 /2 A u to m a tio n
B y te
A IF 1 _ n O u tW 3 _ a
In te rfa c e
C 0 8 5 8 /3
A IF 1 _ b F D O 0 _ b
5 ,6
1 6 B it
...
A IF 1 _ b F D O 1 5 _ b L o w W o rd
B y te
A IF 1 _ b F D O 1 6 _ b
1 6 B it C 0 1 5 1 /4
...
A IF 1 _ b F D O 3 1 _ b H ig h W o r d
7 ,8
1 6 B it
L o w W o rd
B y te
A IF 1 _ d n O u tD 1 _ p
1 6 B it
C 0 8 5 9 H ig h W o r d
Function
The input signals of this function block are copied to the 8 byteuser data of the AIF object and applied
to the plugged-in fieldbus module.
Byte 1 and 2
Byte 1, 2 can be used as word information.
Bytes 3 and 4
You can freely link bytes 3 and 4 with variables of the corresponding data type, as a 16-bit data word
(quasi-analog signal).
Example:
If you write to bytes 3-4, using the variables AIF1_nOutW3_a and AIF1_dnOutD1_p then bytes 7-8
will be rewritten every time a variable is processed. The data in bytes 7-8 are thus not unambiguous.
Byte Address
1, 2 %QB41.0 and %QB41.1
3, 4 %QB41.2 and %QB41.3
Tip!
Please observe the corresponding Operating Instructions for the fieldbus module that is plugged in.
A IF 2 _ IN
A IF 2 _ n In W 1 _ a
1 6 B it
A IF 2 _ n In W 2 _ a
B it 0 1 6 B it
A IF 2 _ b In B 0 _ b
A IF 2 _ b In B 1 _ b
B y te 1 ,2
1 6
...
b in a r y
A IF 2 _ b In B 1 4 _ b
s ig n a ls
A IF 2 _ b In B 1 5 _ b
A IF 2 _ b In B 1 6 _ b
B it 1 5
A IF 2 _ b In B 1 7 _ b
1 6
...
b in a r y A IF 2 _ b In B 3 0 _ b
B y te 3 ,4
s ig n a ls A IF 2 _ b In B 3 1 _ b
1 6 B it
L o w W o rd
A u to m a tio n A IF 2 _ d n In D 1 _ p
In te rfa c e
1 6 B it
H ig h W o r d
A IF 2 _ n In W 3 _ a
B y te 5 ,6
1 6 B it
A IF 2 _ n In W 4 _ a
B y te 7 ,8
1 6 B it
Function
The input signals of the 8 byte user data of the AIF-object are converted into corresponding signal
types.
Byte 5 and 6
Bytes 5, 6 form the signal for AIF2_nInW3_a.
Bytes 7, 8
Bytes 7, 8 form the signal for AIF2_nInW4_a.
Byte Address
1, 2 %IB42.0 and %IB42.1
3, 4 %IB42.2 and %IB42.3
5, 6 %IB42.4 and %IB42.5
7, 8 %IB42.6 and %IB42.7
Tip!
Please observe the corresponding Operating Instructions for the fieldbus module that is plugged in.
A IF 2 _ O U T
B it 0
A IF 2 _ n O u tW 1 _ a
A IF 2 _ n O u tW 2 _ a B y te 1 ,2
B it 1 5
A IF 2 _ b F D O 0 _ b
1 6 B it
...
A IF 2 _ b F D O 1 5 _ b L o w W o rd
A IF 2 _ b F D O 1 6 _ b
B y te 3 ,4
1 6 B it
...
A IF 2 _ b F D O 3 1 _ b H ig h W o r d
1 6 B it A u to m a tio n
L o w W o rd B it 3 1
A IF 2 _ d n O u tD 1 _ p In te rfa c e
B it 0
1 6 B it
H ig h W o r d
A IF 2 _ n O u tW 3 _ a
B y te 5 ,6
B it 1 5
B it 0
A IF 2 _ n O u tW 4 _ a
B y te 7 ,8
B it 1 5
Function
The input signals of this function block are copied to the 8 byte user data of the AIF object and applied
to the plugged-in fieldbus module.
Example:
If you write to bytes 3-4, using the variables AIF2_nOutW2_a and AIF2_dnOutD1_p then bytes 3-4
will be rewritten every time a variable is processed. The data in bytes 3-4 are thus not unambiguous.
Byte 5 and 6
You can freely link bytes 5 and 6 with variables of the corresponding data type, as a 16-bit data word
(quasi-analog signal).
Bytes 7, 8
You can freely link bytes 7 and 8 with variables of the corresponding data type, as a 16-bit data word
(quasi-analog signal).
Byte Address
1, 2 %QB42.0 and %QB42.1
3, 4 %QB42.2 and %QB42.3
Tip!
Please observe the corresponding Operating Instructions for the fieldbus module that is plugged in.
A IF 3 _ IN
A IF 3 _ n In W 1 _ a
1 6 B it
A IF 3 _ n In W 2 _ a
B it 0 1 6 B it
A IF 3 _ b In B 0 _ b
A IF 3 _ b In B 1 _ b
B y te 1 ,2
1 6
...
b in a r y
A IF 3 _ b In B 1 4 _ b
s ig n a ls
A IF 3 _ b In B 1 5 _ b
A IF 3 _ b In B 1 6 _ b
B it 1 5
A IF 3 _ b In B 1 7 _ b
1 6
...
b in a r y A IF 3 _ b In B 3 0 _ b
B y te 3 ,4
s ig n a ls A IF 3 _ b In B 3 1 _ b
1 6 B it
L o w W o rd
A u to m a tio n A IF 3 _ d n In D 1 _ p
In te rfa c e
1 6 B it
H ig h W o r d
A IF 3 _ n In W 3 _ a
B y te 5 ,6
1 6 B it
A IF 3 _ n In W 4 _ a
B y te 7 ,8
1 6 B it
Function
The input signals of the 8 byte user data of the AIF-object are converted into corresponding signal
types.
Byte 5 and 6
Bytes 5, 6 form the signal for AIF3_nInW3_a.
Bytes 7, 8
Bytes 7, 8 form the signal for AIF3_nInW4_a.
Byte Address
1, 2 %IB43.0 and %IB43.1
3, 4 %IB43.2 and %IB43.3
5, 6 %IB43.4 and %IB43.5
7, 8 %IB43.6 and %IB43.7
Tip!
Please observe the corresponding Operating Instructions for the fieldbus module that is plugged in.
A IF 3 _ O U T
B it 0
A IF 3 _ n O u tW 1 _ a
B y te 1 ,2
A IF 3 _ n O u tW 2 _ a
B it 1 5
A IF 3 _ b F D O 0 _ b
1 6 B it
...
A IF 3 _ b F D O 1 5 _ b L o w W o rd
A IF 3 _ b F D O 1 6 _ b
B y te 3 ,4
1 6 B it
...
A IF 3 _ b F D O 3 1 _ b H ig h W o r d
1 6 B it A u to m a tio n
L o w W o rd B it 3 1
A IF 3 _ d n O u tD 1 _ p In te rfa c e
B it 0
1 6 B it
H ig h W o r d
A IF 3 _ n O u tW 3 _ a
B y te 5 ,6
B it 1 5
B it 0
A IF 3 _ n O u tW 4 _ a
B y te 7 ,8
B it 1 5
Function
The input signals of this function block are copied to the 8 byte user data of the AIF object and applied
to the plugged-in fieldbus module.
Example:
If you write to bytes 3-4, using the variables AIF3_nOutW2_a and AIF3_dnOutD1_p then bytes 3-4
will be rewritten every time a variable is processed. The data in bytes 3-4 are thus not unambiguous.
Byte 5 and 6
You can freely link bytes 5 and 6 with variables of the corresponding data type, as a 16-bit data word
(quasi-analog signal).
Bytes 7, 8
You can freely link bytes 7 and 8 with variables of the corresponding data type, as a 16-bit data word
(quasi-analog signal).
Byte Address
1, 2 %QB43.0 and %QB43.1
3, 4 %QB43.2 and %QB43.3
2.5 AIF_IO_Management
Tip!
Please observe the corresponding Operating Instructions for the fieldbus module that is plugged in.
AIF_IO_Management
AIF AIF_bCe1CommErr_b
Communication Error
AIF AIF_bFieldBusStateBit0_b
Field Bus State
AIF_bFieldBusStateBit1_b
AIF_bFieldBusStateBit2_b
AIF_bFieldBusStateBit3_b
AIF_bFieldBusStateBit4_b
AIF_bFieldBusStateBit5_b
AIF_bFieldBusStateBit6_b
AIF_bFieldBusStateBit7_b
Function
Monitoring for communication errors through a field bus module connected to the automation
interface. (Communication error CE0; LECOM-Nr.: 61; Reaction: TRIP)
X 6
C 0 0 3 4 A IN 1
1 A IN 1 _ n In _ a
2 C 0 4 0 0
A IN 1 _ b E rro r_ b
Function
• C0034 can be used to insert a dead-time section into the output signal. The function 4 ... 20
mA as a current master value can be achieved together with the jumper setting X2 (at the front
of the controller).
• Settings through C0598:
– C0598 = 0: if the master current < 2 mA, the TRIP (SD5) message appears.
– C0598 = 2: if the master current < 2 mA, the warning mesage appears.
– C0598 = 3: no message appears.
• Processing time required for the SB: 10 µsec.
Jumper X3
Differential master-current input -20 mA to +20 mA Resolution:
6 5
4 3 20 µA (10 Bit + sign)
2 1
Function
• A voltage of 10 V is given out at terminal X6/62, if the signal on AOUT1_nOut_a = 16384 =
100 %
• Processing time required for the SB: 12 µsec.
X 6 A IN 2
3 A IN 2 _ n In _ a
4 C 0 4 0 5
C 0 1 3 5 D C T R L
1 6
D C T R L _ w C A N 1 C trl
1 6 B it B it3
B it3
≥1
D C T R L _ w A IF 1 C trl Q S P
1 6 B it C 1 3 5 .B 3 D C T R L _ b Q s p In _ b
B it8
B it8
≥1 D IS A B L E D C T R L _ b R d y _ b
C 1 3 5 .B 8
D C T R L _ b C In h _ b
B it9
B it9
C 1 3 5 .B 9 D C T R L _ b Im p _ b
X 5 /2 8
D C T R L _ b C In h 1 _ b ≥1 C IN H D C T R L _ b T r ip _ b
D C T R L _ b W a rn _ b
C 0 8 7 8 /1
D C T R L _ b C In h 2 _ b D C T R L _ b M e s s _ b
≥1
C 0 8 7 8 /2 D C T R L _ b F a il_ b
B it1 0 D C T R L _ w F a u ltN u m b e r
B it1 0
C 1 3 5 .B 1 0 ≥1 T R IP -S E T C 0 1 6 8
D C T R L _ b T r ip S e t_ b
D C T R L _ b C w C C w _ b
C 0 8 7 8 /3 D C T R L _ b E x te r n a lF a u lt _ b
B it1 1 D C T R L _ b N A c tE q 0 _ b
B it1 1
C 1 3 5 .B 1 1 ≥1 > T R IP -R E S E T
D C T R L _ b S ta t1 _ b
D C T R L _ b T r ip R e s e t_ b D C T R L _ b S ta t2 _ b
D C T R L _ b S ta t4 _ b
C 0 8 7 8 /4 C 0 1 3 6 /1
D C T R L _ b S ta t8 _ b
D C T R L _ b In it_ b
D C T R L _ b S ta te B 0 _ b
0 S T A T
D C T R L _ b Im p _ b
1
D C T R L _ b S ta te B 2 _ b
2
D C T R L _ b S ta te B 3 _ b
3
D C T R L _ b S ta te B 4 _ b
4
D C T R L _ b S ta te B 5 _ b
5
D C T R L _ b N A c tE q 0 _ b
6
D C T R L _ b C In h _ b
7 D C T R L _ w S ta t
D C T R L _ b S ta t1 _ b
8
D C T R L _ b S ta t2 _ b C 0 1 5 0
9
D C T R L _ b S ta t4 _ b
1 0
D C T R L _ b S ta t8 _ b
1 1
D C T R L _ b W a rn _ b
1 2
D C T R L _ b M e s s _ b
1 3
D C T R L _ b S ta te B 1 4 _ b
1 4
D C T R L _ b S ta te B 1 5 _ b
1 5
Tip!
A task overflow triggers a TRIP which also stops the application program of the PLC!
Motor control/drive control and PLC application program are otherwise completely separated unless
there is a polling of the signals in the application program.
The SB DCTRL only affects the motor or drive control of the controller.
For instance, the application program will not be stopped when the motor control has triggered a
TRIP.
Range of functions
• Operation inhibited (DISABLE)
• Controller inhibit (CINH)
• TRIP-SET
• TRIP-RESET
• Controller state
• Output of digital status signals
Tip!
QSP is only set if MCTRL_bQspOut_b is linked to DCTRL_bQspIn_b
DCTRL_bQspIn_b OR MCTRL_bQspOut_b
C0907/3
Any Variable
MCTRL_nHiMLim_a
C0906/4
MCTRL_nLoMLim_a
MCTRL_bNMSwt_b C0906/3
MCTRL_bILoad_b C0907/2
2.8.4 TRIP-SET
The drive is operated in the state selected under C0581, and signals “ExternalFault”.
• The function can be operated via 4 inputs:
– Control word CAN1_wDctrlCtr from SB CAN1_IN
– Control word AIF_wDctrlCtrl from SB AIF1_IN
– Control word C0135.B10
– System variables DCTRL_bTripSet_b (VAR_INPUT)
• All inputs are linked by an OR-operation.
• C0136/1 displays the control word C0135
2.8.5 TRIP-RESET
TRIP-RESET resets an active TRIP, provided that the cause of the fault has been removed. If the
cause of the fault is still active, there is no reaction.
• The function can be operated via 4 inputs:
– Control word CAN1_wDctrlCtr from SB CAN1_IN
– Control word AIF_wDctrlCtrl from SB AIF1_IN
– Control word C0135.B11
– System variables DCTRL_bTripReset_b (VAR_INPUT)
• All inputs are linked by an OR-operation.
• The function can only be performed by a FALSE-TRUE transition of the signal resulting from
the OR operation.
• C0136/1 displays the control word C0135
Tip!
If TRUE is present at one of the inputs, no FALSE-TRUE transition can occur in the resulting signal.
2.8.6 DCTRL_wFaultNumber
An existing fault can be read using the system variable DCTRL_wFaultNumber = C0168.
For the assignment of the error numbers refer to chapter ”Monitoring” of the description of the
automation system.
2.8.7 DCTRL_bExternalFault_b
If DCTRL_bTripSet_b triggers a TRIP, then the state changes from DCTRL_bExternalFault_b to TRUE.
DCTRL_bExternalFault_b remains TRUE, until either DCTRL_bTripSet_b , keypad, GDC or codes
reset the TRIP.
0 FALSE
1 TRUE
The bitwise assignment of the status word can be found in the diagram for the SB DCTRL (see
Abb. 2-15).
LD AIF1_wDctrlCtrl
ST DCTRL_wAIF1Ctrl
LD CAN1_wDctrlCtrl
ST DCTRL_wCAN1Ctrl
Module number: 21
This SB can convert and normalize a pulse current at the digital frequency input X9 into a speed and
phase-angle setpoint. The transmission of a digital frequency is very precise (without offset and gain
errors).
X 9
C 0 4 2 7 D F _ IN
D F IN _ n In _ v
C 0 4 2 5 C 0 4 2 6
4 V
(X 9 /8 ) M O N IT -S D 3 D F IN _ b E n c F a u ltC a b le _ b
M P 0
T P /M P D F IN _ b T P R e c e iv e d _ b
-C trl
E 5 D F IN _ d n In c L a s tS c a n _ p
1
C 0 4 2 8 C 0 4 2 9
Range of functions
• Digital frequency input X9
• Technical data for the connection of X9 and X10
• Touch-probe
C0427 = 0 (2-phase)
A
A
B
B
Z
Z
• CW rotation:
– Track A leads track B by 90 ° (positive value at DFIN_nIn_v ).
• CCW rotation:
– Track A lags track B by 90 ° (negative value at DFIN_nIn_v ).
A
A
B
B
Z
Z
• CW rotation:
– Track A transmits the speed.
– Track B = FALSE (positive value at DFIN_nIn_v ).
• CCW rotation:
– Track A transmits the speed.
– Track B = TRUE (negative value at DFIN_nIn_v ).
C0427 = 2 (pulse = A or B)
A
A
B
B
Z
Z
Abb. 2-20 Control of speed and direction of rotation via track A or track B
• CW rotation:
– Track A provides the speed and the direction (positive value at DFIN_nIn_v ).
– Track B = FALSE
• CCW rotation:
– Track B provides the speed and the direction (negative value at DFIN_nIn_v ).
– Track A = FALSE
Transmission function
DFIN_nIn_v f [Hz] ô 60 ô 2
14
Signal adaptation
Finer resolutions can be achieved by adding a following FB (e.g. L_CONV).
Example:
X 9 L _ C O N V 3
C 0 4 2 7 D F _ IN L _ C O N V
D F IN _ n In _ v n In _ a n N u m e ra to r n O u t_ a
n D e n o m in a to r
C 0 4 2 5 C 0 4 2 6
4 V
(X 9 /8 ) M O N IT -S D 3 D F IN _ b E n c F a u ltC a b le _ b
M P 0
T P /M P D F IN _ b T P R e c e iv e d _ b
-C trl
E 5 D F IN _ d n In c L a s tS c a n _ p
1
C 0 4 2 8 C 0 4 2 9
Abb. 2-21 Digital frequency input (DF_IN) with following FB for normalization
Stop!
If C0540 = 0, 1, 2 (signal at X10, see SB DFOUT) and feedback system C0025 > 10 you must not use
the digital frequency input X9.
M a s te r S la v e
X 1 0 X 9
∅
B B m m 2 A W G
1 1 F o r C W r o t a t io n
A 2 2 A 0 .1 4 2 6
A
A 3 3 A
A
4 4
B
G N D 5 5 G N D 0 .5 2 0
B
Z 6 6 Z
0 .1 4 2 6 Z
Z 7 7 Z
L a m p Z
e n a b le
8 8 c o n tro l 0 .5 2 0
B 9 9 B 0 .1 4 2 6
C a b le le n g t h m a x . 5 0 m
9 p o le S u b - D c o n n e c to r 9 p o le S u b - D m a le c o n n e c to r
T P
D F IN _ d n In c L a s tS c a n _ p
ϕ
Abb. 2-22 Function diagram of a TP
Functional sequence
1. The TP is triggered by a FALSE-TRUE edge at the digital input X5/E5 or by a zero pulse from
X9 (only if an encoder is attached).
– Use C0428 to select whether the TP should be carried out by the MP (marker pulse “zero
pulse from encoder”) or from the X5/E5 input.
– Use C0429 to set a delay (unit: incr.) for a TP. This means that the TP/MP-Ctrl has a delyed
response to a TP.
– Through C0431 you can set up whether the TP from E5 should be triggered by a rising or
falling edge(0 = rising edge, 1 = falling edge).
2. If a TP has occurred, then DFIN_bTPReceived_b switches immediately = TRUE.
3. After the start of the task, DFIN_dnIncLastScan_p gives the number of increments [inc/ms]
that have been counted since the TP.
4. Following, DFIN_bTPReceived_b = FALSE is set.
Note!
It is also necessary that DFIN_nIn_v is processed in the task, so that the SB DFIN is read in.
DFIN_nIn_v
• The value DFIN_nIn_v is scaled in increments per millisecond.
(INT) 16384 cirresponds to 15000 rpm.
• For every task in which DFIN_nIn_v is used, the operating system creates an individual counter
that is reset after every start of the task.
Module number: 22
Converts internal speed signals into frequency signals and outputs them, for example, to following
drives. The transmission is very precise (without offset and gain errors).
D F _ O U T
C 0 0 3 0
C 0 5 4 0
C 0 5 4 0
D F O U T _ n In _ v
0
1 C 0 5 4 7
D F O U T _ n O u t_ v 2
n C 0 5 4 9
m a x
4
5 C T R L C 0 5 4 0
0 X 1 0
C 0 5 4 5
1
X 9 2
4
X 8 5
Range of functions
• Output signals on X10
• Output of an analog signal
• Output of a speed signal
• Encoder simulation of the resolver with zero track in resolver zero position
• Direct output of X8
• Direct output of X9
• Technical data for the connection of X9 and X10
Note!
The DF_OUT system block operates with residual values.
Rechtslauf
A
A
B
B
Z
Z
Note!
C0540 = 0 ... 2 is not possible if the connection has been made to digital frequency input DFIN X9
^
and C0025 > 10 has been selected. ( 2-48, selection of the feedback system)
Selection: C0540 = 0
The input signal DFOUT_nOut_v is interpreted as an analog signal [% ] and given out as a frequency
signal at the master frequency output X10.
• 100 % ≡ (INT)16384 ≡ C0011 (nmax)
Transmission function
no. of incr._from C0030 C0011 (n max)
f [Hz] DFOUT_nOut_v [% ] ô ô
100 60
Example:
• DFOUT_nOut_v = 50 %
• C0030 = 3, this corresponds to 2048 inc/rev.
• C0011 = 3000 rpm
f [Hz] 50 % ô 2048 ô 3000 51200 Hz
100 60
Selection: C0540 = 1
The input signal DFOUT_nOut_v is interpreted as a speed (rpm) signal [% ] and given out as a
frequency signal at X10.
• 15000 rpm ≡ (INT)16384
Transmission function
no. of incr._from C0030
f [Hz] DFOUT_nOut_v [rpm] ô
60
Example:
• DFOUT_nOut_v = 3000 rpm
• C0030 = 3, this corresponds to 2048 inc/rev.
f [Hz] 3000 rpm ô 2048 102400 Hz
60
2.10.4 Encoder simulation of the resolver with zero track in resolver zero position
Selection: C0540 = 2
• The function is used if a resolver is connected to X7.
• The encoder constant for output X10 is set under C0030.
• The output of the zero pulse referring to the motor depends on how the resolver is attached to
the motor.
– The zero pulse can be shifted by +360° under C0545 (65536 inc = 360°).
Selection: C0540 = 5
Use: X8 as input for incremental encoder or Sin-Cos encoder
• The signal at input X8 is amplified electrically and is output directly to X10.
• The signals depend on the assignment of input X8.
• C0030 and C0545 have no function.
• The zero track is output only if it is connected to X8.
Selection: C0540 = 4
Use: X9 as digital frequency input
• The signal at input X9 is amplified electrically and is output directly to X10.
• The signals depend on the assignment of input X9.
• C0030 and C0545 have no function.
• The zero track is output only if it is connected to X9.
M a s te r S la v e
X 1 0 X 9
∅
B B m m 2 A W G
1 1 F o r C W r o ta t io n
A 2 2 A 0 .1 4 2 6
A
A 3 3 A
A
4 4
B
G N D 5 5 G N D 0 .5 2 0
B
Z 6 6 Z
0 .1 4 2 6 Z
Z 7 7 Z
L a m p Z
e n a b le
8 8 c o n tro l 0 .5 2 0
B 9 9 B 0 .1 4 2 6
C a b le le n g t h m a x . 5 0 m
9 p o le S u b - D c o n n e c to r 9 p o le S u b - D m a le c o n n e c to r
X5
DIGIN DCTRL -X5/28
DIGIN_bCInh_b
28
DIGIN_bIn1_b
E1 C0114/1...5 DIGIN_bIn2_b
E2 DIGIN_bIn3_b
0
DIGIN_bIn4_b
E3 1
1 DIGIN_bIn5_b
E4
E5 C0443
Function
• Electrical data of the input terminals:
Terminal Use Data
X5/28 Controller enable (RFR) LOW:
O 0 0 +4 V
X5/E1 freely assignable HIGH: +13 0 +30 V
X5/E2 freely assignable
Inputt ccurrent
Inp rrent at 24 V:
X5/E3 freely assignable 8 mA per input
inp t
X5/E4 freely assignable
X5/E5 freely assignable
• You can use X5/E1 ... X5/E3 as real interrupt inputs. The references to the hardware interrupt
inputs are in the task configuration.
• Reaction time of the interrupt task < 250 µs
• The level for every input can be inverted. For this, proceed as follows:
– Select code C0114 with corresponding subcode (e.g. subcode3 for inputX5/E3)
– Enter the desired level as a parameter:
0 = level not inverted (HIGH active)
1 = level inverted (LOW active)
DIGOUT
DIGOUT_bOut1_b
C0118/1...4 X5
DIGOUT_bOut2_b
A1
DIGOUT_bOut3_b 0
DIGOUT_bOut4_b 1 A2
1
C0444/1 A3
C0444/2
C0444/3 A4
C0444/4
Function
• Electrical data of the output terminals:
Terminal Use (Lenze setting in bold print) Data
X5/A1 freely assignable LOW:
O 0 0 +4 V
X5/A2 freely assignable HIGH: +13 0 +30 V
X5/A3 freely assignable
Output
O tp t ccurrent:
rrent:
X5/A4 freely assignable max. 50 mA per output
o tp t
X5/39 Ground of the digital inputs and outputs (external resistance at least 480 Ω at 24 V)
X5/59 Supply input for the control module:
24 V external (I > 1A)
• Delay times:
– For DIGOUT_bOut1_b ... DIGOUT_bOut4_b it lies in the range from 100 µs ... >300 µsec.
• The level for every output can be inverted. For this, proceed as follows:
– Select code C0118 with corresponding subcode (e.g. subcode 3 for output X5/A3)
– Enter the desired level as a parameter:
0 = level not inverted (HIGH active)
1 = level inverted (LOW active)
FCODE
FCODE_nC17_a
C0017 rpm TO INT
FCODE_nC26_1_a
C0026/1 % TO INT
FCODE_nC26_2_a
C0026/2 % TO INT
FCODE_nC27_1_a
C0027/1 % TO INT
FCODE_nC27_2_a
C0027/2 % TO INT
FCODE_nC32_a
C0032 INT
FCODE_nC37_a
C0037 rpm TO INT
FCODE_nC141_a
C0141 % TO INT
FCODE_nC108_1_a
C0108/1 % TO INT
FCODE_nC108_2_a
C0108/2 % TO INT
FCODE_nC109_1_a
C0109/1 % TO INT
FCODE_nC109_2_a
C0109/2 % TO INT
FCODE_bC135Bit0_b
.
.
C0135 16 Bit .
FCODE_bC135Bit15_b
FCODE_nC141_a
C0141 % TO INT
FCODE_bC250_b
C0250 BOOL
FCODE_bC471Bit0_b
DWORD FCODE_bC471Bit1_b
TO .
C0471 .
BIT/BOOL .
FCODE_bC471Bit1_b
FCODE_nC472_1_a
C0472/1 % TO INT
.
.
.
FCODE_nC472_20_a
C0472/20 % TO INT
FCODE_nC473_1_a
C0473/1 INT
.
.
.
FCODE_nC473_10_a
C0473/10 INT
FCODE_dnC474_1_p
C0474/1 DINT
.
.
.
FCODE_dnC474_5_p
C0474/5 DINT
FCODE_nC475_1_v
C0475/1 INT
FCODE_nC475_2_v
C0475/2 INT
Function
• In Abb. 2-27 you will find code names in You can configure these codes. Their
values are assigned directly to the corresponding variables.
– A fixed scaling routine relates the codes to the variable values.
– In the code table, you can find the options that can be set, and the Lenze settings. ( 4-15) ^
• Example:
– You can enter a defined speed (rpm) through C0017. This value is assigned to the variables
FCODE_nC17_a with the data type “Integer”.
Important:
The code C0470 is not available as a system variable. This code occupies the same memory address
as code C0471. The double-word is divided into 4 bytes (C0470/1...4). Code C0470 can be written
to via the keypad/GDC.
M C T R L
M C T R L _ b Q s p O u t_ b M C T R L _ b Q s p In _ b
C 0 9 0 7 /3 C 0 0 4 2
M C T R L _ n H iM L im _ a
M C T R L _ n L o M L im _ a C 0 9 0 6 /4
M C T R L _ n N S e tIn _ a
M C T R L _ b N M S w t_ b C 0 9 0 6 /3
C 0 0 5 0
C 0 9 0 7 /2 M C T R L _ b M M a x _ b
M C T R L _ b IL o a d _ b
M C T R _ n M S e tIn _ a
M C T R L _ n IS e t_ a C 0 9 0 7 /4
C 0 0 5 6 M C T R L _ b IM a x _ b
C 0 1 0 5 C 0 9 0 6 /8
M C T R L _ n IA c t_ a
M C T R L _ n D C V o lt_ a
C 0 9 0 9
M C T R L _ n M A c t_ a
± 1 0 0 %
1 1
+ + + 0 V E C T -C T R L P W M
M C T R L _ n N S e t_ a 0 0
+ - + 1
C 0 9 0 6 /1
C 0 2 5 4 C 0 0 7 2
M C T R L _ P A d a p t_ a C 0 0 7 0
C 0 0 0 6 C 0 0 1 8
C 0 0 7 1
C 0 0 2 2
C 0 9 0 6 /9
C 0 0 7 5
M C T R L _ d n P o s S e t_ p -
1 C 0 0 7 6
C 0 9 0 8 + C 0 0 7 7
M C T R L _ n P o s L im _ a C 0 0 8 6 C 0 0 7 8
C 0 0 8 1
M C T R L _ b P o s O n _ b C 0 9 0 6 /5 C 0 0 8 4
C 0 0 8 5
M C T R L _ n N S ta r tM L im _ a C 0 9 0 7 /1
C 0 0 8 7
C 0 9 0 6 /6 C 0 0 8 8
M C T R L _ n M A d d _ a
C 0 0 8 9
C 0 9 0 6 /2 C 0 0 9 0
M C T R L _ n F ld W e a k _ a
C 0 0 9 1
C 0 9 0 6 /7
U G -V O L T A G E
M O N IT -L U M C T R L _ b U n d e r v o lta g e _ b
C 0 0 5 3
C 0 1 7 3
M O N IT -O U M C T R L _ b O v e r v o lta g e _ b
c o n s t
Im o to r M O N IT -O C 1 M C T R L _ b S h o r tC ir u it_ b
c o n s t
M O N IT -O C 2 M C T R L _ b E a r th F a u lt_ b
C O N S T
M C T R L _ n P o s _ a
R E S O L V E R M C T R L _ n N A c t_ v
X 7
M C T R L _ n N A c t_ a
C 0 5 9 6 M C T R L _ d n P o s _ p
C 0 0 5 1
E N C O D E R
X 8 C 0 4 2 0
C 0 0 1 1 C 0 4 9 7 M O N IT -N M A X M C T R L _ b N m a x F a u lt_ b
C 0 4 9 0 C 0 0 2 5
C 0 4 9 5 c o n s t
M O N IT -S d 2 M C T R L _ b R e s o lv e r F a u lt_ b
M C T R L _ b F r e q E n a b le _ b M C T R L _ b A c tW a itF o r T P _ b
M P T P /M P M C T R L _ b A c tT P R e c e iv e d _ b
0
-C trl
E 4 M C T R L _ d n A c tIn c L a s tS c a n _ p
1
M C T R L _ n N m a x C 1 1
C 0 9 1 1 C 0 9 1 0 T E M P -M O T O R
1 5 0 0C
(X 7 o r X 8 )
M O N IT -O H 3 M C T R L _ b T M o tG T S e tV a lu e _ b
C 0 0 6 3 C 0 1 2 1
M O N IT -O H 7 M C T R L _ b T M o tG T C 0 1 2 1 _ b
D IN 4 4 0 8 1
T e r m in a l( T 1 /T 2 ) M O N IT -O H 8 M C T R L _ b P T C O v e rT e m p _ b
Function range
• Current controller
• Torque limiting
• Additional torque setpoint
• Speed controller
• Torque control with speed limit
• Limiting of speed setpoint
• Phase controller
• Rapid stop (Quickstop, QSP)
• Field weakening
• Chopping frequency changeover
• Touch-probe
• Monitoring
Tip!
Set a suitable motor from the motor selection list (see Operating Instructions for the drive controller)
in C0086. This automatically sets the correct parameters for the current controller.
Stop!
In MCTRL_nHiMLim_a set only positive values, and in MCTRL_nLoMLim_a only negative values,
otherwise the speed controller may lose control.The drive may accelerate out of control.
Parameter setting
When a motor from the table is selected under C0086, the parameters are set so that only very few
adaptations to the application are required.
• Parameterize proportional-gain Vp in C0070:
– Enter approx. 50% setpoint speed (100% = 16384 = nmax)
– Increase C0070, until the drive becomes unstable (observe motor noises).
– Reduce C0070, until the drive becomes stable again.
– Reduce C0070 to approx. 50%
Signal limit
When the drive outputs the maximum torque, the speed controller is at its limit.
• The drive cannot follow the speed setpoint.
• With MCTRL_bMMax_b = TRUE, this state is shown.
Tip!
Select a configuration with digital frequency coupling (*.lpc), since this allows an automatic
connection of all important signals. On this basis, you can optimize the system.
DCTRL_bQspIn_b OR MCTRL_bQspOut_b
C0907/3
Any Variable
MCTRL_nHiMLim_a
C0906/4
MCTRL_nLoMLim_a
MCTRL_bNMSwt_b C0906/3
MCTRL_bILoad_b C0907/2
Function:
• If torque control is selected, this will be deactivated. The drive is controlled by the speed
controller.
• The speed decelerates to zero, with the deceleration time set under C0105.
• The torque limiting MCTRL_nLoMLim_a and MCTRL_nHiMLim_a are switched to inactive.
• The phase controller is activated. If the rotor position is shifted actively, the drive generates a
torque against this displacement, if
– C0254 is not zero
– MCTRL_nPosLim_a triggered with a value > 0% .
Stop!
If the field is weakened manually (MCTRL_nFldWeak_a < 100% ), the drive cannot supply the
maximum torque.
Stop!
The available torque is reduced by the field weakening.
T P
M C T R L _ d n A c tIn c L a s tS c a n _ p
ϕ
Abb. 2-30 Function diagram of a TP
Functional sequence
1. The TP is triggered by a FALSE-TRUE edge at the digital input X5/E4 or by a zero pulse from
X8 or X7.
– Use C0911 to select whether the TP should be carried out by the MP (marker pulse input X8
or zero pulse from resolver) or from the X5/E4 input.
– Use C0910 to set a delay (unit: increments) for a TP. This means that the TP/MP-Ctrl has a
delayed response to a TP.
– Through C0912 you can set up whether the TP from E4 should be triggered by a rising or
falling edge (0 = rising edge, 1 = falling edge).
– Use C0490 to select the feedback system that generates the zero pulse.
2. If a TP has occurred, then MCTRL_bActTPReceived_b = TRUE.
3. After the start of the task, MCTRL_dnActIncLastScan_p gives the number of increments
[inc/msec] that have been counted since the TP.
4. Following, MCTRL_bActTPReceived_b = FALSE is set.
Tip!
It is also necessary that MCTRL_nNAct_v is processed in the task, so that the SB MCTRL is read in.
MCTRL_nNAct_v
• The value MCTRL_nNAct_v is scaled in increments per millisecond.
(INT 16384 ≡ 15000 rpm)
• For every task in which MCTRL_nNAct_v is used, the operating system creates an individual
counter that is reset after every start of the task.
2.13.13 Monitoring
Various monitoring functions protect the drive from impermissible operating conditions.
If a monitoring function is activated,
• the corresponding set reaction is triggered,
• boolean (logic) variables are set to TRUE. You can use these variables in the PLC application
program.
Function
The monitoring reacts if the DC-bus voltage (terminal +UG and -UG) goes below the threshold
(switch-off level) that was set by C0173.
The message is reset if the voltage goes above the switch-off threshold again.
The switch-off threshold determines the voltage level of the DC-bus voltage at which the pulse inhibit
is activated.
The input variable MCTRL_bUndervoltage_b can be processed in the PLC application program.
The selection number is also effective for the overvoltage monitoring OU. ( 2-58) ^
Adapt the setting of the codes to the available mains voltage (also for operation
via+UG/-UG-terminals). When the controller is operated in a network of drives, all controllers must
have the same setting.
If the undervoltage (LU) message is present for more than 3 seconds or if the event is a power-on,
this is entered into the history buffer. This can be the case if the control module is supplied externally
by terminals X5/39 and X5/59 and the mains is switched off.
If the signal is reset (mains is reconnected) this is not entered in the history buffer, but only deleted
(this is not a fault, but acontroller state).
If the events are low voltage messages appearing only for less than 3 seconds, this is interpreted as
interference (e.g. mains supply fault)and entered into the history buffer. In this case, the history buffer
is continued.
Features:
• LECOM no.: 1030
• Reaction: MESSAGE (cannot be modified)
Function
The monitoring reacts if the DC-bus voltage (terminal +UG and -UG) goes above the threshold
(switch-off level) that was set by C0173.
The message is reset if the voltage falls below the switch-off threshold again.
The table above shows the setting of the switching thresholds according to the selection number.
The switch-off threshold determines the voltage level of the DC-bus voltage at which the pulse inhibit
is activated.
^
The selection number is also effective for the undervoltage monitoring (LU). ( 2-57)
Features:
• LECOM no.: 1020
• Reaction: MESSAGE (cannot be modified)
A frequent overvoltage message indicates an incorrect dimensioning of the drive (the braking energy
is excessive).
Remedy:
• Use supply module 934X or
• Use (additional) brake choppers type 935X
When several controllers are operated simultaneously, an operation as DC bus connection may be
useful.
Here, the generated brake energy of one drive can serve as drive energy for another drive.
The mains connections only supply the energy difference.
Function
The controllers of the 93XX series are equipped with an earth fault detection as a standard.
If the monitoring is triggered, the drive controller must be disconnected from the mains power and
the earth fault must be removed.
Features:
• LECOM no.: 12
• Reaction: TRIP (cannot be modified)
Function
This monitoring is triggered by a short-circuit of the motor phases. It can also be a short-circuit of the
windings in the machine.
This monitoring however, also reacts during mains connection (power-on), if there is an Earth fault
present.
If the monitoring is triggered, the drive controller must be disconnected from the mains power and
the earth fault must be removed.
Features:
• LECOM no.: 11
• Reaction: TRIP (cannot be modified)
Function
The signal TMot>SetValue is derived from a comparator with hysteresis. The switch-off threshold is
150°C, and is fixed. The hysteresis is also fixed and amounts to15°C ( i.e. the reclosing point is
135°C.This monitoring is only effective for the thermal sensor specified by Lenze as it is included in
the standard Lenze servo motor. The Sub-D connectors X7 or X8 serve as inputs.
Stop!
You can only use X7 or X8. The other input must not be assigned (must remain open). This monitoring
is activated by default setting. This means that the monitoring reacts if no Lenze servo motor is used.
Features:
• LECOM no.: 53
• Reaction: TRIP or OFF
Function
The signal TMot>C0121 is derived from a comparator with hysteresis.
The same conditions apply here as for the monitoring TMot>SetValue (motor-temperature
monitoring OH3), since the same inputs are used.
The threshold is set under code C0121. The hysteresis is fixed and amounts to 15 K. The signal is
thus reset below a threshold of 15 K.
Features:
• LECOM no.: 2057
• Reaction: WARNING or OFF
Function
The signal PTCOverTemp is derived from the digital signal via the terminalsT1, T2 next to the power
terminals UVW. The threshold and the hysteresis depend on the encoder system (DIN44081).
Stop!
When using this input as a motor protection: If the monitoring is set to WARNING or OFF, the motor
can be destroyed by any further overload.
Features:
• LECOM no.: 58, 2058
• Reaction: TRIP, WARNING or OFF
200%
150%
$
100% thermal continuous current100%
for Imotor 150 Iratedx
70% thermal continuous current 70%
for Imotor 150% Iratedx
time
10s 60s 120s 180s
* rated controller current 100%
x depending on the chopping frequency of the inverter
K35.0151
Purpose
• Motor protection
• Monitors the cable and the resolver for wire breakage.
Function
Warning!
During commissioning this monitoring should not be switched off, since the machine may reach very
high speeds (potential destruction of the motor and the driven machine) in the event of a fault (e.g.
system cables disconnected or incorrectly bolted). The same applies if this monitoring is changed
to WARNING. The possibility of disconnection should only be used if the monitoring reacts without
obvious reasons (very long cables, strong noises of other devices).
• This monitoring is activated automatically if the resolver is selected as actual speed encoder
(C0025).
• This monitoring is deactivated automatically if another actual speed encoder is selected.
Stop!
If there is a fault in the actual speed detection, it is not ensured that the monitoring reacts to
overspeed NMAX.
Features:
• LECOM no.: 82, 2082
• Reaction: TRIP, WARNING or OFF
Purpose
Controller protection
This monitoring is designed as a warning before the disconnection of the controller via the OH-TRIP.
Thus, the process can be influenced to avoid a switch-off of the controller at an inconvenient time.
Additionally, blowers which would cause an unacceptable noise incontinuous operation, can also be
switched on and off.
Function
MCTRL_bKuehlGreaterC0122_b is derived from a comparator with hysteresis. The threshold can be
set under code C0122. The hysteresis is fixed and amounts to 5 K. The signal is thus reset below a
threshold of 5 K.
Features:
• LECOM no.: 2054
• Reaction: WARNING or OFF
Purpose
Controller protection
Function
MCTRL_bKuehlGreaterSetValue_b is derived from a comparator with hysteresis. The switch-off
threshold is 85 °C and is fixed. The hysteresis is also fixed and amounts to 5 °C, i.e. the reclosing point
is 80 °C.
Features:
• LECOM no.: 50
• Reaction: TRIP (cannot be modified)
Tripping can have the following causes:
• The ambient temperature is too high.
Remedy:
– Install a blower into the switch cabinet.
• The controller is overloaded in its arithmetic mean, i.e. overload and recovery phase exceed
100 % .
Remedy:
– Shorten overload phase.
– use a more powerful drive controller.
Purpose
Process monitoring
Function
A maximum plant speed can be entered under code C0596, independent of the direction of rotation.
The monitoring is released, if:
• the actual speed exceeds the limit C0596
• the actual speed is more than twice the value of C0011(nmax).
Stop!
• For active loads (e.g. hoists) make sure that no torque is applied atthe drive. Special,
plant-specific measures are required.
• If the actual speed encoder fails, it is not ensured that this monitoring reacts.
Features:
• LECOM no.: 200
• Reaction: TRIP (cannot be modified)
Module number: 51
The SB steers a group of controllers to specified states (e.g. TRIP, QSP or controller inhibit).
+10V STATE_BUS
STATE_BUS_bIn_b
STATE_BUS_bOut_b 1
ST
C0441 ST
X5
Function
The statebus is a device-specific bus system which is designed for Lenze controllers only. The SB
STATEBUS acts on the terminals X5/ST or reacts to a LOW signal at these terminals (multimaster
capability).
• Steers all networked drives to the preselected state.
• Every controller that is connected can set these terminals to a LOW signal.
• All drive controllers that are connected can evaluate the signal levels at these terminals and
process them internally in the programs.
• Up to 20 drive controllers can be connected
Stop!
Do not apply an external voltage across terminals X5/ST.
K1
L1
L2
L3
N
PE
F1 F1 F1
OFF
K1 Z1 Z1 Z1
ON
K1
F2 F3 F2 F3 F2 F3
L1 L2 L3 PE +UG -UG L1 L2 L3 PE +UG -UG L1 L2 L3 PE +UG -UG
K1 K1 K1
K35.0122
Z1 Mains filter
F1...F5 Fuses
K1 Main contactor
Note!
Further information on the statebus as well as possible applications and commissioning can be
found in the System Manual for the 9300, Project Planning, Part F.
Note!
The system variables are not generated in simulation mode.
Function
SYSTEM_bClockxHz
• These system markers output a fixed clock with equal pulse/pause ratios.
• The marker is toggled in real time.
• If you use this system marker, take care with the frequency that is used for polling the marker
(aliasing effect). You should use at least twice the toggle frequency.
Example:
You would like to use the systen marker SYSTEM_bClock100Hz as a clock for a counter. The
pulse/pause ratio is 5 msec/5 msec.
To avoid an aliasing effect, the counter must always be polled with an INTERVAL-TASK <5msec.
SYSTEM_bTogCycleTask
• This system marker toggles with the cyclical task:
1. cycle = FALSE
2. cycle = TRUE
3. cycle = FALSE
4. cycle = TRUE
etc.
SYSTEM_nTaskInterval
• This system marker shows the interval for the current task, with a resolution of 250 µsec.
– If, for instance, a 10-millisecond task is being processed, the system marker indicates 40
(10 msec = 40 x 250 µsec).
– If a different type of task is being processed, instead of an interval task, the system marker
indicates 0.
SYSTEM_nTaskID
• This system marker shows the task-ID for the current task.
SYSTEM_b1LoopCyclicTask/SYSTEM_b1Loop Task X
• These system markers only have the state TRUE during the first cycle of the particular task.
– After the first cycle of the specific task, the system variable is set to FALSE.
– A change back to the TRUE stae will occur after a reset, or a fresh start of the program in the
target system.
3 Networking
8200DPL001
The production factor ”information” becomes increasingly important for the networking of
production plants. This applies particularly to a drive network and automation of decentralized
drives.
Drives of the Lenze range can easily be networked and implemented into a comprehensive
automation concept.
The control and parameterization of the devices can be carried out, depending on the task, using
different communication interfaces:
• terminals (analog, digital, digital master-frequency)
• built-in system bus interface (CAN)
• plug-in field module for the following bus systems or communication profiles
– RS232/485 {LECOM-A/B/LI} with or without optical fibres (type 2102)
– INTERBUS (type 2111)
– INTERBUS-Loop (type 2112)
– PROFIBUS-DP (type 2131 and 2133)
– DeviceNet/CANopen (type 2175)
• plug-in operating module (keypad).
The communication to higher-level hosts is possible via a simple plug&play interface at the front side
of the device.The above figure shows such a communication with fieldbus modules 2133
PROFIBUS-DP.
In an existing connection via field bus modules to a higher-level master system the system bus (CAN)
can additionally be used for communication between Lenze devices. Time-critical data such as
setpoint and actual values, can be exchanged in real-time using the system bus.
Special handling features of the system bus (CAN):
• simple communication
• no special knowledge of bus systems required.
Terminal X4
HI
Terminal X3
GND LO
CG LO HI CG LO HI
Drive PLC
Terminal X5
GND LO HI
GND LOW HI GG LO HI GG LO HI GG LO HI GG LO HI
120 120
PES PES plc014
Comments on wiring
We recommend the following signal cable for the wiring:
Specification system bus cable Total length up to 300 m Total length up to 1000 m
Cable type LIYCY 2 x 2 x 0.5 mm2 CYPIMF 2 x 2 x 0.5 mm2
(twisted pairs, with screening) (twisted pairs, with screening)
Cable resistance ≤ 40 Ω/km ≤ 40 Ω/km
Capacitance per unit length ≤ 130 nF/km ≤ 60 nF/km
Connection Pair 1 (white/brown): LO and HI
Pair 2 (green/yellow): GND
Tip!
• A terminating resistor of R = 120Ω must be connected to the first and last physically
connected device (see Abb. 3-1).
• Connect cable screen over a large surface to PE potential (PES).
O F F F 1 F 2 F 3 F 1 F 2 F 3 F 1 F 2 F 3
K 1 Z 1 Z 1 Z 1
O N
K 1
L 1 L 2 L 3 P E + U G -U G L 1 L 2 L 3 P E + U G -U G L 1 L 2 L 3 P E + U G -U G
7 9 3 2 X - 9 3 3 X 7 9 3 2 X - 9 3 3 X 7 9 3 2 X - 9 3 3 X
P E P E P E W P E P E W P E
U V W H I L O G N D 2 8 A 4 U V H I L O G N D 2 8 A 4 U V H I L O G N D 2 8 A 4
R A 1 R A 2
R F R R F R R F R
9300PLC123
K35.0021
Strip cable in the contact area of the clamp and make a large-surface contact to the clamp
and to PE.
5. Connect terminating resistor RA = 120Ω at the physical bus ends.
6. Separate control and fieldbus cables from the motor cable!
7. The CAN-GND cable must also be separated from the motor cable.
8. Connect terminal 7 with the screen plate of the controller.
9. Avoid stubs
3.1.4 Commissioning
1. Switch on the controller or PLC (main supply or external 24 V supply).
2. If necessary, change the transmission speed (C0351) using the operating module 9371 BB or
the PC (default setting 500 kBaud).
– This setting must be identical for all participating bus devices.
3. Set the CAN address (C0350) using the operating module 9371BB or the PC ( 3-34) ^
– This CAN address must be unique for every bus device.A multiple assignment of the same
address results in a BUS-OFF (error code CE4, error number 65; see chapter Monitoring
^ ^
( 4-3) and chapter Error messages ( 4-11)).
The default setting of the controllers is C0350 = 1.
4. The communication of all devices connected to the system bus is possible now. You can read
all codes and change all codes which can be written.
3.1.5 Programming
3.1.5.1 General
The integrated system bus provides a considerable extension of the bus device functionality. These
are, among others:
• Parameter entries
• Data exchange between drive controllers
The connection of other modules is easily possible. These are, among others:
• decentralized terminals
• controls and input devices
• external controls and control systems
The user can, for example, implement an exchange of data between one drive controller and another,
with digital control, speed and torque signals, without having knowledge of the bus system.
A total of 5 input signals and 5 output channels are available for data communication, that can all be
used independently.
They include 2 parameter channels (SDO = Service Data Object).
write write
Parameters
(Code)
HMI PC
With 2 parameter channels it is possible to connect of 2 different devices for parameter setting, e.g.
the simultaneous connection of a PC and an operating unit (see Abb. 3-2).
CAN1_IN
CAN1_OUT
Control system
Two event-controlled process data channels with selectable and adjustable cycles(PDOs)
CAN2_IO, CAN3_IO
These process data channels are intended for exchanging data between one drive controller and
another. Another application of these process data is for decentralised input and output terminal.
Higher-level control systems can also use these channels.
CAN2_IN CAN2_OUT
CAN2_OUT CAN2_IN
CAN3_OUT CAN3_IN
CAN1_bCtrlQuickstop_b
CAN1_bCtrlDisable_b
CAN1_bCtrlCInhibit_b
CAN1_bCtrlTripSet_b
Bit 0 CAN1_bCtrlTripReset_b
CAN1_bCtrlB0_b
CAN1_bCtrlB1_b
CAN1_bCtrlB2_b
Controlword
16
CAN1_bCtrlB4_b
binary
signals CAN1_bCtrlB5_b
CAN1_bCtrlB6_b
CAN1_bCtrlB7_b
CAN1_bCtrlB12_b
Bit 15 CAN1_bCtrlB13_b
CAN1_bCtrlB14_b
CAN1_bCtrlB15_b
C0136/2
Byte 3,4
CAN1_nInW1_a
16 Bit
C0866/1
CAN1_nInW2_a
16 Bit
SYSTEMBUS C0866/2
CAN1_nInW3_a
X4 16 Bit
C0866/3 CAN1_bInB0_b
C0863/1 CAN1_bInB2_:b
Byte 5,6
...
16
binary CAN1_bInB14_b
signals
CAN1_bInB15_b
CAN1_bInB16_b
CAN1_bInB17_b
C0863/2
...
16
binary CAN1_bInB30_b
signals
CAN1_bInB31_b
Byte 7,8
16 Bit
LowWord
CAN1_dnInD1_p
16 Bit C0867/1
HighWord
Function
8 bytes are available for data communication with the drive controller.
Byte Notes Address
1, 2 The device-internal control word is fixed to bytes 1-2. You can apply any boolean variable to a selection of %IB31.0 and %IB31.1
the free binary/logic signals of the control word.
The signals for the functions Quickstop (QSP), DISABLE, CINH, TRIP-SET and TRIP-RESET can be written to
the SB DCTRL via the control word. To do this, connect the variables CAN1_wDctrlCtrl and
DCTRL_wCAN1Ctrl .
These functions are also available through the variable CAN1_bCtrlQuickstop_b, CAN1_bCtrlDisable_b,
CAN1_bCtrlCInhibit_b, CAN1_bCtrlTripSet_b and CAN1_bCtrlTripReset_b. You can read out these signals
and apply further processing to them.
The other 11 bits can be used to control further function blocks.
3, 4 Bytes 3-4 can be selected as a 16-bit data word with the individual signals for quasi-analog signals. %IB31.2 and %IB31.3
5, 6 Bytes 5-6 and bytes 7-8 can be used simultaneously as two quasi-analog values and as phase-angle %IB31.4 and %IB31.5
information with upp to 32 bits of binary information (value
information, (val e 1 or 0).
0) The functional
f nctional assignment is made
7, 8 through variables of the appropriate data type. %IB31.6 and %IB31.7
C A N 1 _ O U T B it 0
S ta tu s w o rd
C A N 1 _ w D c tr lS ta t
1 6 B it
C A N 1 _ n O u tW 1 _ a
B it 1 5
C 0 8 6 8 /1
C A N 1 _ n O u tW 2 _ a
C 0 8 6 8 /2
3 ,4
C A N 1 _ n O u tW 3 _ a
B y te
C 0 8 6 8 /3 S Y S T E M B U S
X 4
C A N 1 _ b F D O 0 _ b
5 ,6
1 6 B it
...
C A N 1 _ b F D O 1 5 _ b L o w W o rd
B y te
C A N 1 _ b F D O 1 6 _ b
1 6 B it
C 0 1 5 1 /1
H ig h W o r d
...
C A N 1 _ b F D O 3 1 _ b
7 ,8
1 6 B it
C A N 1 _ d n O u tD 1 _ p L o w W o rd
B y te
1 6 B it
C 0 8 6 9 /1
H ig h W o r d
Function
8 bytes are available for data communication with the drive controller.
Byte Notes Address
1, 2 Bytes 1 and 2 form the control word for the controller. %QB31.0 and %QB31.1
The signals for functions such as IMP, CINH etc. can be written from SB DCTRL to the SB CAN1_OUT by
using the status word from SB DCTRL. To do this, connect the variables DCTRL_wStat and
CAN1_wDctrlStat.
Several bits in SB DCTRL are freely assignable. They are configured through the variables
DCTRL_bStatB0_b, DCTRL_bStatB1_b, DCTRL_bStatB2_b, DCTRL_bStatB3_b, DCTRL_bStatB4_b,
DCTRL_bStatB5_b, DCTRL_bStatB14_b and DCTRL_bStatB15_b
3, 4 You can freely link bytes 3 and 4 with variables of the corresponding data type, as a 16-bit data word %QB31.2 and %QB31.3
(quasi-analog signal).
5, 6 It iss poss
possible,
b e, us
usingg ddifferent
e e variables,
a ab es, too writee simultaneously
s u a eous y too bytes
by es 55-6
6 oor by
bytes
es 7-8.
8 Avoid
o d thiss %QB31.4 and %QB31.5
7, 8 situation,
it ti sincei th
the ddatat iin bbytes
t 55-66 or bbytes
t 77-8 8 are th
then nott unambiguous.
bi %QB31.6 and %QB31.7
C A N 2 _ IN 1 6 B it C A N 2 _ n In W 1 _ a
C 0 8 6 6 /4
1 6 B it C A N 2 _ n In W 2 _ a
B it 0 C 0 8 6 6 /5
C A N 2 _ b In B 0 _ b
C 0 8 6 3 /3 C A N 2 _ b In B 1 _ b
B y te 1 ,2
...
1 6
b in a r y C A N 2 _ b In B 1 4 _ b
s ig n a ls C A N 2 _ b In B 1 5 _ b
B it 1 5
C A N 2 _ b In B 1 6 _ b
C A N 2 _ b In B 1 7 _ b
C 0 8 6 3 /4
S Y S T E M B U S
3 ,4
X 4 1 6
...
B y te
b in a r y
C A N 2 _ b In B 3 0 _ b
s ig n a ls
C A N 2 _ b In B 3 1 _ b
1 6 B it
L o w W o rd
C A N 2 _ d n In D 1 _ p
5 ,6
B y te
1 6 B it C 0 8 6 7 /2
H ig h W o r d
C A N 2 _ n In W 3 _ a
1 6 B it
C 0 8 6 6 /6
C A N 2 _ n In W 4 _ a
7 ,8
1 6 B it
B y te
C 0 8 6 6 /7
Function
For data communication with the drive controller, 8 bytes are available.
Byte Notes Address
1, 2 You can use byte 1, 2 and byte 3, 4 simultaneously as %IB32.0 and %IB32.1
• bbinary
a y information
o a o (up too 32
3 bits),
b s),
3, 4 • 2 values of data type Integer, %IB32.2 and %IB32.3
• 1 value of data type Double Integer.
5, 6 %IB32.4 and %IB32.5
Bytes 5-6
5 6 and bytes 7-8
7 8 can be selected to be a 16
16-bit
bit data word (data type Integer)
Integer).
7, 8 %IB32.6 and %IB32.7
CAN2_OUT Bit 0
CAN2_nOutW1_a
Byte 1,2
C0868/4
CAN2_nOutW2_a
C0868/5
CAN2_bFDO0_b
Bit 15
...
16 Bit
CAN2_bFDO15_b LowWord
CAN2_bFDO16_b
16 Bit
Byte 3,4
C0151/2
...
CAN2_bFDO31_b HighWord
16 Bit
LowWord SYSTEMBUS
CAN2_dnOutD1_p X4
16 Bit
C0869/2
HighWord
Byte 5,6
CAN2_nOutW3_a
C0868/6
Byte 7,8
CAN2_nOutW4_a
C0868/7
Function
For data communication with the drive controller, 2 ⋅ 8 bytes are available.
Byte Notes Address
1, 2 You can freely link bytes 1-2 and 3-4 with variables of the corresponding data type, as a 16-bit data word %QB32.0 und %QB32.1
(data type Integer).
Integer)
3, 4 It is possible, using different variables, to write simultaneously to bytes 1-2 or bytes 3-4. Avoid this %QB32.2 und %QB32.3
situation, since the data in bytes 1-2 or bytes 3-4 are then not unambiguous.
5, 6 It iss poss
possible,
b e, us
usingg ddifferent
e e variables,
a ab es, too writee simultaneously
s u a eous y too bytes
by es 55-6
6 oor by
bytes
es 7-8.
8 Avoid
o d thiss %QB32.4 und %QB32.5
7, 8 situation,
it ti sincei th
the ddatat iin bbytes
t 55-66 or bbytes
t 77-8 8 are th
then nott unambiguous.
bi %QB32.6 und %QB32.7
C A N 3 _ IN 1 6 B it C A N 3 _ n In W 1 _ a
C 0 8 6 6 /8
1 6 B it C A N 3 _ n In W 2 _ a
B it 0 C 0 8 6 6 /9
C A N 3 _ b In B 0 _ b
C 0 8 6 3 /5 C A N 3 _ b In B 1 _ b
B y te 1 ,2
...
1 6
b in a r y C A N 3 _ b In B 1 4 _ b
s ig n a ls C A N 3 _ b In B 1 5 _ b
B it 1 5
C A N 3 _ b In B 1 6 _ b
C A N 3 _ b In B 1 7 _ b
C 0 8 6 3 /6
S Y S T E M B U S
3 ,4
X 4 1 6
...
B y te
b in a r y
C A N 3 _ b In B 3 0 _ b
s ig n a ls
C A N 3 _ b In B 3 1 _ b
1 6 B it
L o w W o rd
C A N 3 _ d n In D 1 _ p
5 ,6
B y te
1 6 B it C 0 8 6 7 /3
H ig h W o r d
C A N 3 _ n In W 3 _ a
1 6 B it
C 0 8 6 6 /1 0
C A N 3 _ n In W 4 _ a
7 ,8
1 6 B it
B y te
C 0 8 6 6 /1 1
Function
For data communication with the drive controller, 8 bytes are available.
Byte Notes Address
1, 2 You can use byte 1, 2 and byte 3, 4 simultaneously as %IB33.0 and %IB33.1
• bbinary
a y information
o a o (up too 32
3 bits),
b s),
3, 4 • 2 values of data type Integer, %IB33.2 and %IB33.3
• 1 value of data type Double Integer.
5, 6 %IB33.4 and %IB33.5
Bytes 5-6
5 6 and bytes 7-8
7 8 can be selected to be a 16
16-bit
bit data word (data type Integer)
Integer).
7, 8 %IB33.6 and %IB33.7
CAN3_OUT Bit 0
CAN3_nOutW1_a
Byte 1,2
C0868/8
CAN3_nOutW2_a
C0868/9
CAN3_bFDO0_b
Bit 15
...
16 Bit
CAN3_bFDO15_b LowWord
CAN3_bFDO16_b
16 Bit
Byte 3,4
C0151/3
...
CAN3_bFDO31_b HighWord
16 Bit
LowWord SYSTEMBUS
CAN3_dnOutD1_p X4
16 Bit
C0869/3
HighWord
Byte 5,6
CAN3_nOutW3_a
C0868/10
Byte 7,8
CAN3_nOutW4_a
C0868/11
Function
For data communication with the drive controller, 2 ⋅ 8 bytes are available.
Byte Notes Address
1, 2 You can freely link bytes 1-2 and 3-4 with variables of the corresponding data type, as a 16-bit data word %QB33.0 and %QB33.1
(data type Integer).
Integer)
3, 4 It is possible, using different variables, to write simultaneously to bytes 1-2 or bytes 3-4. Avoid this %QB33.2 and %QB33.3
situation, since the data in bytes 1-2 or bytes 3-4 are then not unambiguous.
5, 6 It iss poss
possible,
b e, us
usingg ddifferent
e e variables,
a ab es, too writee simultaneously
s u a eous y too bytes
by es 55-6
6 oor by
bytes
es 7-8.
8 Avoid
o d thiss %QB33.4 and %QB33.5
7, 8 situation,
it ti sincei th
the ddatat iin bbytes
t 55-66 or bbytes
t 77-8 8 are th
then nott unambiguous.
bi %QB33.6 and %QB33.7
CAN_Management
C0358 ≥1
CAN_bResetNode_b CAN_ResetNode
CAN1_IN CAN_bCe1CommErrCanIn1_b
Communication Error
CAN2_IN CAN_bCe2CommErrCanIn2_b
Communication Error
CAN3_IN CAN_bCe3CommErrCanIn3_b
Communication Error
CAN CAN_bCe4BusOffState_b
Bus Off State
CAN_bTxCan2Synchronized_b
CAN2_OUT CAN_SYNC
CAN_bTxCan3Synchronized_b
CAN3_OUT CAN_SYNC
Function CAN_bResetNode_b
A reset-node is atcivated by setting C0358 = 1 or CAN_bResetNode_b switches immediately =
TRUE.
Tip!
Even if the SB has not been assigned to the control configuration, code C0358 can still be used to
activate a reset-node.
3.3.1 CAN_Synchronization
CAN_Synchronization
CAN_bResetSyncForInterpolatord_b
CAN_bSyncForInterpolator_b CAN_bSyncInsideWindow_b
CAN_nSyncDeviation
Synchronizes the control program cycle of the drives to the cycle of a higher-level control. This can
also be a Lenze Servo controller of the 9300 series.
Variable Name Data Type Signal Type Address DIS DIS format Note
CAN_b Bool binary %IX102.0.0 TRUE:
SyncInsideWindow_b Sync-Telegram/signal within the
time window (C1123)
FALSE:
• Synchronization left
• no Sync-telegram/signal
• Time window (C1123) too small
CAN_b Bool binary %IX102.0.1 TRUE:
SyncForInterpolator_b Sync-telegram/signal recognized.
CAN_n Integer %IX102.1 current sync difference
SyncDeviation
CAN_b Bool binary %QX102.0.0 TRUE:
ResetSyncForInterpolator_b Reset CAN_bSyncForInterpolator_b
Range of functions
• Possible axis synchronizations
• Sync cycle time (SYNC CYCLE)
• Phase shift (SYNC PHASE)
• Time window (SYNC WINDOW)
• Display, CAN sync cycle (Sync cycle)
• Correction value phase controller (SYNC CORRECT)
• CAN sync reaction (Sync Response)
• CAN sync identifier (Sync Rx ID, Sync Tx ID)
• CAN sync Tx transmission cycle (Sync Tx Time)
• Application examples
Tip!
• The system block CAN_Synchronization must previously be entered into the control
configuration.
• Synchronization via system bus:
– The system bus must previously be correctly installed (see Part 3, Automation).
• Synchronization via terminal:
– The system block DIGITAL_IO must be entered into the control configuration.
Control mode
Code LCD
C Possible settings IMPORTANT
O
Lenze Choice
[C1121] Sync mode 0 0 {1} 2 CAN Sync source
0: Off 0: Synchronization deactivated
1: CAN Sync 1: Synchronizes the controllers on
2: Terminal Sync the sync telegram of the system
bus
2: Synchronizes the controllers on
the sync signal of terminal X5/E5.
Synchronization time
After mains connection and the initialization time of the controller, additional time is needed for
synchronization.
The synchronization time depends on
• the baud rate of the system bus,
• the start time (input of the first sync telegram/signal),
• the time between the sync telegrams/signals,
• the sync correction factor (C0363),
• the control mode (C1120)
Phase shift
Code LCD
C Possible settings IMPORTANT
O
Lenze Choice
[C1122] Sync phase 0 0 {0.001 ms} 6.5 Synchronization phase
Phase shift between the sync
telegram/signal and the start of the
internal control program.
Time window
The variable CAN_bSyncInsideWindow_b can be used for synchronization monitoring.
Code LCD
C Possible settings IMPORTANT
O
Lenze Choice
[C1123] Sync-window 0 0 {0.001 ms} 6.5 Synchronization window
If the sync telegram/signal from the
master is within this ”time window”,
CAN_bSyncInsideWindow_b = switch
es to TRUE.
Sync-Window
Sync-Signal
SyncCycle SyncCycle
Abb. 3-12 ”Time window” for the LOW-HIGH edges of the sync signal
Tip!
A jitter* up to +200 µs on the LOW-HIGH edges of the sync signal is permissible. The size of the jitter
affects the parameterization of the ”time window”.
*) Jitters are time differences of the signal frequencies. These are differences of fixed times (e.g. the
transition time from one signal amplitude to another) of a digital signal. Jitter occurs mainly with high
frequencies and can result in loss of data.
Code LCD
C Possible settings IMPORTANT
O
Lenze Choice
C0362 Sync cycle g 0 {1 msec} 30 Time between two sync telegrams
on the system bus
Code LCD
C Possible settings IMPORTANT
O
Lenze Choice
C0363 Sync corr 1 0 {1} 5 CAN Sync correction
Change correction value until
CAN_nSyncDeviation has reached a
minimum.
1 = 0.2 µs/ms
2 = 0.4 µs/ms
3 = 0.6 µs/ms
4 = 0.8 µs/ms
5 = 1.0 µs/ms
Code LCD
C Possible settings IMPORTANT
O
Lenze Choice
C0366 Sync Response 1 0 no sync response CAN sync. response
1 sync response When C366 = 1, the controller
reacts on a sync telegram by
sending the CAN1_OUT object.
Code LCD
C Possible settings IMPORTANT
O
Lenze Choice
C0369 Sync Tx Time 0 0 {1} 65000 CAN sync transmit telegram
cycle time
A sync telegram with the identifier
of C0368 is sent with the set cycle
time (C369 = 0, off).
Settings:
Drive controller 1 Drive controller 2
C0350 = 1 Node = 1; C0350 = 2 Node = 2;
so that output address for CAN2_OUT = C0350 + 1 so that input address for CAN2_IN = C0350 + 1 =
=2 2
C0352 = 2 Master - -
CAN2_IN CAN2_nInW1_a
CAN2_OUT Bit 0 16 Bit
MCTRL_nNSet_a
CAN2_nOutW1_a
C0866/4
16 Bit CAN2_nInW2_a
Byte 1,2
C0868/4
CAN2_nOutW2_a Bit 0 C0866/5
CAN2_bInB0_b
C0868/5
Controlword
16 Bit
...
CAN2_bFDO15_b LowWord 16
CAN2_bFDO16_b binary CAN2_bInB14_b
16 Bit signals CAN2_bInB15_b
Byte 3,4
C0151/2
...
HighWord Bit 15
CAN2_bFDO31_b
CAN2_bInB16_b
LowWord
CAN2_dnOutD1_p
...
16
16 Bit binary
C0869/2 X4 X4 CAN2_bInB30_b
HighWord signals
CAN2_bInB31_b
Byte 5,6
CAN2_nOutW3_a
C0868/6
16 Bit
LowWord
Byte 5,6
CAN2_dnInD1_p
16 Bit C0867/2
HighWord
Byte 7,8
CAN2_nOutW4_a
CAN2_nInW3_a
C0868/7 16 Bit
C0866/6
Byte 7,8
CAN2_nInW4_a
16 Bit
C0866/7
dnTir L_RFG
dnTif
nIn nOut
nSet 1
bLoad_b
MCTRL_nNSet_a
A1 Drive controller 1
A2 Drive controller 2
In addition, you can define a Boot-Up time for the master during the initialisation phase.
^ 3-35 Boot-Up setting C0356/1)
(
Example:
• The process output image of the SB CAN2_OUT is created at the end of a 10 msec task.
• C0356/2 = 3
• ⇒ The Process Data Object is transmitted every 30 msec (3 * 10 msec)
Tip!
Þ Þ
Check in DDS, above the dialog field Process image creation , in which task the process image was
created (Object Organizer Register card Resources Object Process image).
The data transmission has limitations that are given by the number of telegrams per time interval and
the data transmission rate.
You can establish these limits for data exchange within a pure drive group, by adding the code
C0361/1 values for all the participating drives.
Example:
3 drives are grouped together through the system bus.
C0361/1 for drive controller 1 23.5% bus loading
C0361/1 for drive controller 2 12.6% bus loading
C0361/1 for drive controller 3 16.0% bus loading
52.1% total bus loading
Tip!
• The bus loading for all participating devices should not exceed 80% .
• If other devices are connected, such as decentralised inputs and outputs, then their telegrams
must also be taken into account.
• A bus-overloading can, for instance, be caused by the event-controlled transmission of
contninuously changing signals.
– Remedy: set the cycle time for the system blocks that are involved (CAN2_OUT and
CAN3_OUT) under C0356/2 and C0356/3 to an appropriate value, such that the sum of all
the bus loadings is not excessive.
3.4.2.8 Monitoring
Monitoring times C0357
Each individual process-data object can monitor whether a telegram has arrived within the time
defined here. If a telegram has arrived, then the corresponding monitoring time is restarted
(retrigerrable monostable function).
The following assignments are valid:
C0357/1 Monitoring time CAN1_IN
C0357/2 Monitoring time CAN2_IN
C0357/3 Monitoring time CAN3_IN
Bus Off
If the drive controller has decopled itself from the bus, because of faulty telegrams, the signal
“BusOffState” (CE4) is set.
Just like the signals “commErrCANIN1” (CE1), “commErrCANIN2” (CE2), “commErrCANIN3” (CE3),
this signal can trigger a TRIP or warning, or you can switch it off. The response is set with C0595. It
is also possible to assign a terminal output in this case.
Reset-Node C0358
Entries of altered transmission rates or changed addresses for the process-data objects or device
addresses will only become effective after a Reset-Node.
A Reset-Node can be made by:
• A fresh power-on
• Reset-Node through the bus system (^ 3-22, CAN_ResetNode)
• Reset-Node through C0358 (^ 3-22, CAN_ResetNode)
User data
There are 3 distinctions made for the application of user data:
• Initialisation
– User data for establishing communication across the CAN-bus.
• Parameterization
– User data for the parameterization of the drive controller. For Lenze drive controllers, the
parameters are stored under the code positions or the variables.
• Process data
– User data intended for rapid, often cyclical, procedures (e.g. speed setpoint and actual
value)
To be able to change over between the various communication phases, telegrams are used with an
Identifier 0 and 2 bytes of user data.
For communication purposes, the drive recognizes three states:
State Explanation
a State ”Initialisation”
The drive is not participating in the data traffic on the bus. This state is achieved after the drive controller is switched on. It is still
possible to repeat the whole or a part of the initialisation, by transmitting various telegrams. In this case, all the parameters that
have already been set will be overwritten by the default/standard values. After initialisation is completed, the drive goes automati-
cally into the ”Pre-Operational” state.
b State ”Pre-Operational”
The drive can receive parameterization data. The process data are ignored.
c State ”Operational”
The drive can receive parameterization and process data.
The changeover between the communication phases is controlled by one bus participant (the
network master) for the entire network.
This can also be carried out by a 93XX drive controller. To do this, set up this drive controller as the
master (C0352 = 1).
A telegram is transmitted once after switching on the power, after a delay. This sets the entire drive
group to the ”Operational” state.
The delay time can be set under C0356/1.
The following applies to the assignment of the bytes marked by ”xx” in the column:
• xx = 00hex
– With this assignment, the telegram applies to all connected devices. A change of state can
be made for all devices at the same time.
• xx = device address
– If a device address is given, then the change of state is only carried out for the device with
the corresponding address.
Tip!
Communication of the process data is only possible when the state is changed to Operational !
3.4.5 Parameterization
Two separate software channels are available for parameterization, which are defined by the
controller address.
The structure of the telegram for parameterization is as follows:
Command code:
In the command code, the services must be entered, or services are entered such as transmitting or
writing a parameter, and how long these data are.
Structure of the command code:
Bit 7 (MSB) Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Command Specifier (cs) 0 Length e s
cs Length e s
Write Request 0 0 1 0 x x 1 1
Write Response 0 1 1 0 x x 0 0
Read Request 0 1 0 0 x x 0 0
Read Response 0 1 0 0 x x 1 1
Error Response 1 0 0 0 0 0 0 0
The length of the user data for these services are coded in Bit 2 and Bit 3 as follows:
• 00 = 4-byte
• 01 = 3-byte
• 10 = 2-byte
• 11 = 1-byte
The most frequent parameters are data with 4 bytes (32-bit) and 2 bytes (16-bit) data length.
So the following values result in the command code for these parameters:
Services 4-byte (32-bit) data 2-byte (16-bit) data Meaning
hex dec hex dec
Write Request 23hex 35 2Bhex 43 Transmit parameter to drive
Write Response 60hex 96 60hex 64 Reponse of the drive controller to the write request (acknowledge-
ment)
Read Request 40hex 64 40hex 64 Request to read a parameter from the drive controller
Read Response 43hex 67 4Bhex 75 Response to the read request with the actual value
Error Response 80hex 128 80hex 128 The drive controller reports a communication error
Subindex
A subindex is a table position of a parameter under the index.
Example:
Terminal X5/A1, Subcode 1 unter dem Parameter C0117 soll angesprochen werden.
Index = 24575 - 117 = 24458 = 5F8Ahex (Index LOW-byte = 8A, Index HIGH-byte = 5F)
Subindex = 1
If a parameter is addressed, that does not have a subindex, then 0 must be entered here.
Fault
Command code = 128 = 80hex
If a fault occurs, an error-response is generated by the drive. In this case, the user-data section of
the transmission always has a 6 in Data 4 and an error code in Data 3.
Possible error-codes:
Command code: Data 3 Data 4 Meaning
80hex 6 6 wrong index
80hex 5 6 wrong subindex
80hex 3 6 Access denied
F3 5F 40 0D 03 00
Index = 5F F3 Value = 00 03 0D 40
Calculation of identifier:
Identifier from parameter channel 1 to drive controller = 1536 + device address = 1536 + 1 = 1537
Command code = Write Request (transmit parameter to drive) = 23hex
1537 23 F3 5F 00 40 0D 03 00
1409 60 F3 5F 00 00 00 00 00
Identifier for parameter channel 1 from drive controller: 1408 + device address = 1409
Command code = Write Response (response of the drive controller (acknowledgement)) = 60hex
Calculation of identifier:
Identifier from parameter channel 1 to drive controller = 1536 + device address = 1536 + 5 = 1541
Command code = Read Request (request to read a parameter from the drive controller) = 40hex
1541 40 C2 5F 00 00 00 00 00
1413 43 C2 5F 00 B0 8F 06 00
Identifier for parameter channel 1 from drive controller= 1408 + device address = 1413
Command code = Response to the read request with the actual value = 43hex
Index of the read request = 5FC2hex
Subindex = 0 (no subindex available for C0061)
Data 1 ... Data 4 = 43 °C ⋅ 10.000 = 430.000 = 00068FB0hex
Sync-telegram Sync-telegram
After a sync-telegram, the cyclical process-data are transmitted by the drive controllers. The data
transfer to the drive controllers follows next, that is again accepted by the individual controllers with
the next sync-telegram.
All other telegrams, such as parameters or the event-controlled process-data, are accepted
asynchronously by the drive controllers after the transmission has taken place.
The asynchronous data are not considered in Abb. 3-22.
Identifier
Identifier
Identifier
Bytes 1-2 and bytes 3-4 can be simultaneously used as 32 individual binary/logic signals, as 2
separate 16-bit data-words (”quasi-analog signal”) or as one double-word (32-bit).
^ 3-10, CAN1_IN)
(
Identifier
Bytes 1-2 and bytes 3-4 can be simultaneously used as 32 individual binary/logic signals, as 2
separate 16-bit data-words (”quasi-analog signal”) or as one double-word (32-bit).
^ 3-14, CAN2_IN)
(
Identifier
Identifier
^ 3-16, CAN2_OUT)
(
Identifier
^ 3-20, CAN3_OUT)
(
4 Appendix
The PLC provides a number of system POUs.These POUs have defined features (see table) and are
called only once per polling.
POU name Program Feature POU starts, if ...
PLC_TaskOverrun Task overflow the task monitoring time is exceeded
PLC_RealError Floating point error a floating point error occurred
PLC_FailTripping TRIP a trip has been caused
PLC_WarningTripping WARNING a warning was output
PLC_MessageTripping MESSAGE a message was output
PLC_FailQspTripping *) FAIL- QSP a FAIL-QSP has been caused
max 1000 statements
max.
PLC_CANError CAN-BUS error a CAN bus error occurs, e.g. BUS-OFF, Cex warning
PLC_AIFError AIF-BUS error a AIF-Bus error has been caused
PLC_Restart Start after a STOP the START command has been activated
PLC_ColdStart Cold start after a RESET/program download the START command has
been activated.After the execution of these POU the CAN/AIF
bus is ready.
*) not available for Drive PLC
POUs are created, as for the cyclic task ”PLC_PRG”, by creating a PROGRAM-POE with the
symbolic POU name.
System POUs are supported as from hardware version 1.0.
4.3 Monitoring
System interfaces
• System bus (CANopen) CAN
• Field buses
• Digital frequency,
analog and digital I/O Rectifier
Memory
(FLASH, EEPROM, RAM) Microcontroller
• PLC application program
to IEC 1131-3
(can be changed)
Inverter
Technology functions
SIN/COS encoder
Tip!
In general, faults do not affect the serviceability of the PLC!
Different monitoring functions of the motor control protect the drive from unpermissible operating
conditions.
After the monitoring function has been triggered
• the corresponding set reaction is released (see chapter 4.3.1).
• a digital output of a system block is set.
In the event of undervoltage at the PLC, for instance, the output MCTRL_bUndervoltage_b of
the system block MCTRL_MotorControl (internal motor control) is set to TRUE (see(^ 2-57)).
• the error code is entered in the history buffer.
• the current error number is displayed under DCTRL_wFaultNumber.
If a reaction on a motor control error is required, the error can be requested (see description of the
individual system blocks). The system blockDCTRL_DriveControl displays that an error has occured
and shows the current error code.
4.3.1 Reactions
Depending on the interference, one or more of the following reactions of the monitoring function are
possible:
• TRIP (highest priority)
• Meldung
• FAIL-QSP
• Warning
• OFF = no reaction (lowest priority)
Tip!
For some of the faults you can determine the reaction of the drive (see chapter 4.3.2)
Reaction Effects on the drive and controller Danger notes Status messages at the operating
module
offs:oon:n
RDY IMP FAIL
TRIP • Switches one of the power outputs U, V, W to a high
resistance until the trip is reset.
• The drive is coasting (no control!). o n n
• After TRIP reset, the drive accelerates to its setpoint along
the setramps.
Meldung • Switches one of the power outputs U, V, W to a high
resistance as long as the message is active.
• Short The drive is coasting (no control!) as long as the
message message is active.
The drive restarts
≤ 0.5 s If the message is no longer valid, the drive
accelerates with maximum torque to its setpoint.
automatically if the o n n
fa lt is eliminated.
fault eliminated
• Long The drive is coasting (because of internal
message controller inhibit!) as long as the message is
> 0.5 s active.
Restart positioning program, if necessary.
FAIL-QSP Brakes the drive via the QSP ramp (code C0105) to standstill.
• The time for the QSP ramp is set in the dialog box ”Basic
- - -
settings”.
• Default setting of FAIL-QSP:
Warning • Fault display only
• The drive continues to operate in a controlled way. The drive may be n o n
destroyed because of
OFF • No reaction on interference! deactivated monitoring
Monitoring is deactivated. functions! - - -
w Default setting 1)
á possible Adjustable in the DDS under ”Project” + ”Exception handling”
- not possible
Tip!
This function block is described in the function library LenzeDrive.lib.
This FB is used to transmit error messages to the PLC.This means that TRIP, Fail-QSP, message or
warning can be activated in the PLC while the PLC program is running. The transmitted error number
is stored in the history buffer of the PLC (C0168/x).
4.5 Troubleshooting
• You can recognize immediately whether a fault has occurred from the display elements or
status information. ^ 4-7, chapter “Troubleshooting”)
(
3 : on P : off ★ : blinking
Display in Global-Drive-Control
Double-click ”Dialog Diagnostic” in the parameter menu of the GDC to open the dialog box
Diagnostic 9300 .
• The dialog box Diagnostic 9300 informs about the controller status:
History buffer
ó ì
ú
ö
Please note:
• For faults occurring at the same time with different reactions:
– Only the reaction with the highest priority is entered in the history buffer
(Priority = TRIP " Message " FAIL-QSP " Warning).
• For faults occurring at the same time with the same reaction (e. g. 2 messages):
– Only the fault which occurred first is entered in the history buffer.
Time ó
• Contains the times when the faults occurred.
– e.g. ”1234567 s”
– Reference time is the mains switch-on time (see dialog box Diagnostic 9300 , field top right)
Please note:
• If a fault is immediately followed by another fault for several times, only the time of the last
occurrence is stored.
Frequency ì
• Contains the frequency of a fault immediately followed by the same fault. The time of the last
occurrence is stored.
Reset fault ö
• Click the TRIP reset button to reset the fault.
Tip!
If the error message is requested by a fieldbus, the fault indication is represented by a fault number
(C0168/x). See column 2and the footnote at the end of this table.
Error no.:
qxxx
- TRIP
Display Error Cause Remedy
- Message
- Warning
- FAIL-QSP
Error no.:
qxxx
- TRIP
Display Error Cause Remedy
- Message
- Warning
- FAIL-QSP
2& q012 Earth fault One of the motor phases has earth contact. • Check motor
• Check supply module
Excessive capacitive charging current of the motor Use motor cable which is shorter or of lower
cable. capacitance.
2& q015 I x t overload Frequent and too long acceleration with overcurrent Check drive dimensioning.
Continuous overload with Imotor > 1.05 x Irx.
2+ q050 Heat sink temperature is Ambient temperature Tamb > 40 5C or 50 5C. • Allow controller to cool and ensure better
higher than the value set ventilation.
in the controller • Check ambient temperature in the control cabinet.
Heat sink very dirty. Clean heat sink
Incorrect mounting position. Change mounting position.
2+ q053 Heat sink temperature is Motor too hot because of excessive current or Check drive dimensioning.
g than the value set
higher frequent and too long acceleration
i th
in the controller
t ll No PTC connected. Connect PTC or switch-off monitoring (C0583= 3).
2+ q054 Heat sink temperature is Ambient temperature Tamb > 40 5C or 50 5C. • Allow controller to cool and ensure better
higher than the value set ventilation.
under C0122. • Check ambient temperature in the control cabinet.
Heat sink very dirty. Clean heat sink
Incorrect mounting position. Change mounting position.
Value set under C0122 was too low. Enter higher value.
2+ q057 Motor temperature is Motor too hot because of excessive current or Check drive dimensioning.
g than the value set
higher frequent and too long acceleration
under
d C0121
C0121. No PTC connected. Connect PTC or switch-off monitoring (C0584= 3).
Value set under C0121 was too low. Enter higher value.
2+ q58 PTC at terminals T1, T2 Motor too hot because of excessive current or Check drive dimensioning.
indicates motor overheat. frequent and too long acceleration
Terminals T1, T2 are not assigned. Connect PTC or thermostat or switch off monitoring
(C0585= 3).
3(5 q074 Program fault A fault in the program was detected. Send controller with data (on diskette) to Lenze.
3, q079 Initializing error • A fault was detected during transfer of parameter Correct parameter set.
set between the controllers
• Parameter set does not match the controller (e.g.
when data were transmitted from a controller
with more performance to a controller with less
performance.)
35 q075 Parameter set error • Fault when loading a parameter set.
35 q072 CAUTION: The Lenze default setting is loaded • Set the required parameters and store them under
automatically. C0003.
• Interrupt during the transmission of PS with the • For PRO the supply voltage must be switched off
keypad (e.g. by disconnecting the keypad), if additionally.
necessary.
The saved parameters do not match the loaded
Before acknowledging the error, first save all
software version.
parameter sets manually under C0003.
The Lenze default setting is loaded automatically.
6' q082 Resolver fault Resolver cable interrupted. • Check the resolver cable for open circuit
• Check resolver.
• or switch off monitoring (C0586 = 3).
6' q083 Encoder fault at X9/8
/ Cable interrupted. Check cable for open circuit.
Input X9 PIN 8 not assigned. Assign input X9 PIN 8 with 5V or switch off
monitoring (C0587 = 3).
6' q085 Master current source Master current at X6/1 X6/2 < 2mA. • Check cable for open circuit.
defective • Check master current source.
6' q086 Sensor fault Encoder of the motor temperature detection at X7 or Check supply cable for firm connection.
X8 indicates indefinite values. Switch off monitoring with C0594 = 3 if necessary.
Error no.:
qxxx
- TRIP
Display Error Cause Remedy
- Message
- Warning
- FAIL-QSP
6' q087 Encoder fault Absolute encoder with RS485 interface does not Check supply cable.
transmit data. Check encoder.
Check voltage supply C0421.
No Stegmann encoder connected.
OTF5 5 q201 Time-out task with Id.2
81 (see task configuration)
7$6.
)/2$7 q209 Floating point error (REAL) Error in the real calculation
6<6 7 in the system task The fault is eliminated as in a task overflow.
The task in which the error occurred was incorrectly NOTE: Please check your
yo r real calc
calculation
lation before
)/2$7 q210 Floating point error (REAL) calculated. acknowledging the trip.
&<&/ 7 in the system task A real error can occur when dividing by 0.
)/2$7 q211 Floating point error (REAL)
7$6. in the task with Id2
)/2$7 q212 Floating point error (REAL)
7$6. in task with Id.3
)/2$7 q213 Floating point error (REAL)
7$6. in task with Id.4
)/2$7 q214 Floating point error (REAL)
7$6. in task with Id.5
Division by 0 Browse program code
)/2$7 q215 Floating point error (REAL)
7$6. in task with Id.6
)/2$7 q216 Floating point error (REAL)
7$6. in task with Id.7
)/2$7 q217 Floating point error (REAL)
7$6. in task with Id.8
)/2$7 q218 Floating point error (REAL)
7$6. in task with Id.9
1O7 ). q220 Insufficient units on the The system attempts to load a program with
7 &5(', target system technology functions on a Servo PLC with insufficient Extend the instance of your Servo PLC
7 units.
^
9300”.
4-10, (“Working with the history buffer”)
If a TRIP source is still active, TRIP cannot be
– Keypad 9371 BB:
reset.
Press STOP key. Then press RUN to enable the controller again.
– Fieldbus module: Set C0043 = 0
– Control word C0135
– Terminal X5/E5 (default setting) or “DCTRL-TRIP-RESET”
– Control word AIF
– Control word system bus (CAN)
Message • After eliminating the fault, the message is reset automatically.
The drive restarts automatically if the fault is
eliminated.
C0042 QSP g 0
1
QSP inactive
QSP active
– reads the controller status
Quick stop status ^ 2-48
C0043 Trip reset Reset of an active trip:
• Set C0043 = 0
0 no/trip reset reset latest trip
C0050 nNsetIn_a gg 1
-100.00
trip active
{0.01 %}
active fault TRIP
100.00 rset at the speed controller input ^ 2-48
^ 2-48
C0051 mctrl-nact
C0052 MCTRL-Umot gg -30000
0
{1 rpm}
{1 V}
30000 Actual speed
800 Actual motor voltage ^ 2-48
^ 2-48
C0053 Ug-voltage
C0054 IMot g 0
0.0
{1 V}
{0.1 A}
900 DC-bus voltage
500.0 Actual motor current ^ 2-48
C0056 nMSetIn_a g
Lenze Choice
-100.00 {0.01 %} 100.00 Torque setpoint ^ 2-48
C0057 Max Torque g 0.0 {0.1 Nm}
(output of the speed controller)
500.0 Maximum possible torque of the drive
configuration
^ 2-48
• depending on C0022, C0086
C0058 Rotor diff 0.0 -180.0 E
{0.1 } 179.9 Zero phase of the rotor for synchronous
93xx 93xx
C0094 Password 0 0 9999 Password
• Parameter-access protection for the
operating module. When the
password is activated, only
user-menu codes can be accessed.
For further selection options, see
C0096.
C0157
1 DCTRL_bStateB0_b
g 0
bit states
1 Status of the free bits of the status
word
^ 2-25
2 DCTRL_bStateB2_b
3 DCTRL_bStateB3_b
4 DCTRL_bStateB4_b
5 DCTRL_bStateB5_b
6 DCTRL_bStateB14_b
7 DCTRL_bStateB15_b
C0161 Act trip
C0167 Reset failmem
g
0
All error messages
0 No reset
Latest error message (as in C0168/1)
C0168
1 Fail no. act
g 1 Reset
(History buffer)
clears the history buffer
All occuring faults
now active
2 Fail no. old1 latest
3 Fail no. old2 last but one
4 Fail no. old3 last but two
5 Fail no. old4 last but three
6 Fail no. old5 last but four
7 Fail no. old6 last but five
C0169
8 Fail no. old7
g (History buffer)
last but six
Sequence of the faults saved under
C0168
• referred to C0179
1 Failtime act now active
2 Failtime old1 latest
3 Failtime old2 last but one
4 Failtime old3 last but two
5 Failtime old4 last but three
6 Failtime old5 last but four
7 Failtime old6 last but five
8 Failtime old7 last but six
C0170 g
Lenze Choice
corresponding power switch-on time error frequency
History buffer
• List of how often the faults have
occurred consecutively under C0168
1 Counter act now active
2 Counter old1 latest
3 Counter old2 last but one
4 Counter old3 last but two
5 Counter old4 last but three
6 Counter old5 last but four
7 Counter old6 last but five
8 Counter old7 last but six
[C0172] OV reduce 10 0 {10 V} 100 Threshold to activate the brake torque
reduction before OU fault
[C0173] UG limit 1 Adaptation of DC-bus voltage ^ 2-48
thresholds
0 Mains< 400V+ -B Operation on mains < 400 V with or
without brake unit
1 Mains= 400V+ -B Operation on 400 V mains with or
without brake unit
2 Mains= 460V+ -B Operation on 460 V mains with or
without brake unit
3 Mains= 480V-B Operation on 480 V mains without
brake unit
4 Mains= 480V+ B Operation on 480 V mains with brake
unit
• check during commissioning, and
adapt if necessary
• All drive components in DC-bus
C0183 Diagnostics g
Lenze Choice
Drive diagnostics
• Indicates fault or status information
• If several items or fault or status
information are simultaneously
present, the information with the
lowest number is displayed
0 OK No fault
10 Init Initialization phase
91 Trip-Set C135
92 Trip-Set AIF
93 Trip-Set CAN
102 Trip TRIP active
103 RFG P-OFF Emergency stop was released
104 IMP Message Message active
105 Power off
111 BSP C135 Operation inhibited
112 BSP AIF
113 BSP CAN
121 CINH term 28 Controller inhibited via X5/28
122 CINH int 1 DCTRL-CINH1
123 CINH int 2 DCTRL-CINH2
124 CINH C135/STP STOP key of 9371BB
125 CINH AIF Controller inhibited via AIF
126 CINH CAN Controller inhibited via CAN
141 Lock mode Restart protection active
142 IMP Power outputs with high resistance
151 QSP ext term QSP via MCTRL-QSP
152 QSP C135/STP QSP via STOP key
153 QSP AIF QSP via AIF
154 QSP CAN QSP via CAN
2
3
4
C0203 Comm.-No. gg x / xxxx / xxxxx Commission number
C0204 Serial-No.
C0206 Product date gg 0 {1} 65535 Serial number
Production date
C0207 DL info 1
C0208 DL info 2
C0209 DL info 3
gg Download-Info 1
Download-Info 2
Download-Info 3
C0250 FCODE_nC250_a ^ 2-45
C0254 Vp angle-CTRL 0.2000 0.0000 {0.0001} 3.9999 Vp Phase controller ^ 2-48
[C0350] CAN address 1 1 {1} 63 CAN bus node address ^ 3-32
[C0351] CAN baud rate 0 0 500 kbit/s CAN bus baud rate ^ 3-32
1 250 kbit/s
2 125 kbit/s
3 50 kbit/s
4 1000 kbit/s
[C0352] CAN mst 0 0 slave Install CAN bus master operation ^ 3-32
1 Master
C0353 0 C350 Source for CAN bus IN/OUT addresses ^ 3-10
1 CAN addr sel1 0 1 C354
2 CAN addr sel2 0
3 CAN addr sel3 0
CAN1_IN Id
g
386
0 {1} 2047 CAN bus identifier ^ 3-10
2 CAN1_OUT Id
3 CAN2_IN Id
4 CAN2_OUT Id
5 CAN3_IN Id
6 CAN3_OUT Id
C0356 0 {1 msec} 65000 CAN bus time settings ^ 3-10
1 CAN boot up 3000 • CANx_OUT T:
^
2 CAN2_OUT T 0 Factor on the task time for sending
3 CAN3_OUT T 0 the process data object. 3-35
4 CAN delay 20
[C0357] 0 {1 msec} 65000 CAN bus monitoring time for Iratedx ^ 3-10
1 CE1monit time 3000
2 CE2monit time 3000
3 CE3monit time 3000
C0358 Reset node 0 0 no function Install the CAN bus reset-node ^ 3-32
C0359 CAN state g 1
0
1
CAN reset
Operational
Pre-Operat
CAN-bus status: ^ 3-32
2 Warning
C0360 g 3
0
Bus off
{1} 65535 Telegram counter
(number of telegrams)
^ 3-32
• for values > 65535, the counting
restarts with 0
1 Message OUT all sent
2 Message IN all received
3 Message OUT1 sent to CAN-OUT1
4 Message OUT2 sent to CAN-OUT2
5 Message OUT3 sent to CAN-OUT3
6 Message POUT1 sent to parameter channel 1
7 Message POUT2 sent to parameter channel 2
8 Message IN1 received from CAN-IN1
9 Message IN2 received from CAN-IN2
10 Message IN3 received from CAN-IN3
11 Message PIN1 received from parameter channel 1
12
C0361
Message PIN2
g 0 {1 %}
received from parameter channel 2
100 CAN bus load
• To ensure a perfect operation, the
^ 3-32
total bus load (all connected
devices) should be less than 80%
1 Load OUT all sent
2 Load IN all received
3 Load OUT1 sent to CAN-OUT1
4 Load OUT2 sent to CAN-OUT2
5 Load OUT3 sent to CAN-OUT3
6 Load POUT1 sent to parameter channel 1
7 Load POUT2 sent to parameter channel 2
8 Load IN1 received from CAN-IN1
9 Load IN2 received from CAN-IN2
10 Load IN3 received from CAN-IN3
11 Load PIN1 received from parameter channel 1
12 Load PIN2 received from parameter channel 2
1
1
0
0 no sync response
{1} 5 Sync correction
1 Input signal CAN active
CAN Sync Response
^ 3-32
^ 3-32
1 sync response
C0367 Sync Rx ID 128 1 {1} 256 CAN Sync Rx ID ^ 3-32
C0368 Sync Tx ID 128 1 {1} 256 CAN Sync Tx ID ^ 3-32
^ 3-32
C0369 Sync Tx Time
C0400 AIN1_aIn_a
C0405 AIN2_aIn_a
gg
0 0
-199.99
-199.99
{1 msec}
{0,01 %}
{1 %}
65000 CAN Sync Tx Time
199.99 Output of AIN1
199.99 Output of AIN2
^ 2-21
^ 2-21
[C0416] Resolver adj 0 0 {1} 99999999 Correction of the resolver error
With Lenze motors:
• Read resolver error from the
nameplate
[C0420] Encoder const 512 256 {1 inc/rev} 8192 Encoder constant for encoder input X8 ^ 2-48
in increments per revolution
[C0421] Encoder volt 5.00 5.00 {0.1V} 8.00 Set supply voltage for the encoder used ^ 2-48
• WARNING: incorrect input may
destroy the encoder
C0425 DFIN const 3 0 256 inc/rev Constant for digital frequency input in ^ 2-31
1 512 inc/rev increments per revolution
2 1024 inc/rev
3 2048 inc/rev
4 4096 inc/rev
5 8192 inc/rev
C0426 OUT g 6
-32767
16384 inc/rev
{1 rpm} 32767 Output signal ^ 2-31
C0427 Function 0 Type of the digital frequency signal ^ 2-31
0 2-phase 0 = Quadrature
1 A puls / B dir 1 = Pulse / Direction
2 Pulse A or B 2 = Pulse A / Pulse B
C0428 TP select 0 0 Touch-Probe through zero-pulse (only with Touch probe selection ^ 2-31
encoder)
1 Touch-Probe through digital input X5/E5
C0429 TP-Delay 0 -32767 {1 inc} 32767 Delay for Touch-Probe ^ 2-31
C0431 TP edge 0 0 Activation with positive signal Setting of the touch probe activation ^ 2-31
C0434 AOUT1_nOut_a gg 1
-199.99
Activation with negative signal
{0.01 %}
with digital input X5/E4 (C0428 = 1)
199.99 Input signals of AOUT1 ^ 2-21
^ 2-21
C0439 AOUT2_nOut_a
C0441 STATE_BUS_bOut_b
C0443 DIGIN_bInx_b
gg -199.99
0
{0.01 %}
{1}
199.99 Input signals of AOUT2
Monitoring signal
255 Signals at X5/E1 to X5/E5
^ 2-65
^ 2-43
decimal value
• Binary interpretation indicates
C0444
1 DIGOUT_bOut1_b
g 0
terminal signals
1 Signals at X5/A1 to X5/A4 ^ 2-44
2 DIGOUT_bOut2_b
3 DIGOUT_bOut3_b
4 DIGOUT_bOut4_b
[C0469] Fct STP key Function of the STOP key of the
operating module
• Function is activated when pressing
the STOP key.
C0855
1 AIF1_bInB0_b
g 3
0
Off
FFFF Process input words hexadecimal for
automation interface X1 of AIF1_IN
^ 2-4
...
AIF1_bInB15_b
2 AIF1_bInB16_b
...
C0856
AIF1_bInB31_b
1 AIF1_nInW1_a
g -199.99 {0.01%} 199.99 Process input words decimal from
AIF1_IN
^ 2-4
2 AIF1_nInW2_a • 100% = 16384
3 AIF1_nInW3_a
C0857 AIF1_dnInD1_p g -2147483648 {1} 2147483647 32 bit phase-angle information from ^ 2-4
g
AIF1_IN
C0858 -199.99 {0.01 %} 199.99 Process output words from AIF1_IN ^ 2-4
1 AIF1_nOutW1_a • 100% = 16384
2 AIF1_nOutW2_a
3 AIF1_nOutW3_a
C0863
1 CAN1_BInB0_b
g
Lenze Choice
0 FFFF Process input words hexadecimal for
system bus (CAN)
^ 3-10
...
CAN1_BInB15_b
2 CAN1_BInB16_b
...
CAN1_BInB31_b
3 CAN2_BInB0_b
...
CAN2_BInB15_b
4 CAN2_BInB16_b
...
CAN2_BInB31_b
5 CAN3_BInB0_b
...
CAN3_BInB15_b
6 CAN3_BInB16_b
...
C0866
1
CAN3_BInB31_b
CAN1_nInW1_a
g -199.99 {0.01 %} 199.99 Process input words for system bus
(CAN)
^ 3-10
2 CAN1_nInW2_a • 100% = 16384
3 CAN1_nInW3_a
4 CAN2_nInW1_a
5 CAN2_nInW2_a
6 CAN2_nInW3_a
7 CAN2_nInW4_a
8 CAN3_nInW1_a
9 CAN3_nInW2_a
10 CAN3_nInW3_a
11
C0867
CAN3_nInW4_a
1 CAN1_dnInD1_p
g -2147483648 {1} 2147483647 32-bit phase information for system
bus (CAN)
^ 3-10
2 CAN2_dnInD1_p
3 CAN3_dnInD1_p
C0868
1 CAN1_nOutW1_a
g -199.99 {0.01 %} 199.99 Process output words system bus (CAN)
• 100% = 16384
^ 3-10
2 CAN1_nOutW2_a
3 CAN1_nOutW3_a
4 CAN2_nOutW1_a
5 CAN2_nOutW2_a
6 CAN2_nOutW3_a
7 CAN2_nOutW4_a
8 CAN3_nOutW1_a
9 CAN3_nOutW2_a
10 CAN3_nOutW3_a
11
C0869
CAN3_nOutW4_a
1 CAN1_dnOutD1_p
g -2147483648 {1} 2147483647 32-bit phase information for system
bus (CAN)
^ 3-10
2 CAN2_dnOutD1_p
3 CAN3_dnOutD1_p
C0878
1 DCTRL_bCInh1_b
g Digital input signals of DCTRL ^ 2-25
2 DCTRL_bCInh2_b
3 DCTRL_bTripSet_b
4 DCTRL_bTripReset_b
C0879 0 no reset Reset of control words ^ 2-25
1 Reset C135 1 reset • C0879 = 1 performs one reset
2 Reset AIF
3 Reset CAN
C0906
1 MCTRL_nNSet_a
g
Lenze Choice
-199.99 {0.01 %} 199.99 Analog input signals ^ 2-48
2 MCTRL_nNAdd_a
3 MCTRL_nLoMLim_a
4 MCTRL_nHiMLim_a
5 MCTRL_nPosLim_a
6 MCTRL_nNStartMLim_a
7 MCTRL_nFldWeak_a
8
C0907
1
MCTRL_nISet_a
MCTRL_bPosOn_b
g Digital input signals ^ 2-48
2 MCTRL_bNMSwt_b
3 MCTRL_bQspOut_b
4 MCTRL_bILoad_b
C0908 MCTRL_dnPosSet_p g -2147483647 {1 inc} 2147483647 Set phase-angle signal
• 1 turn = 65536 inc
^ 2-48
C0909 speed limit 1 1 + /- 175 % Limitation of direction of rotation for ^ 2-48
2 0 .. + 175 % the speed setpoint
3 -175 .. 0 %
C0910 TP-Delay 0 -32767 {1 inc} 32767 Delay for Touch-Probe ^ 2-48
C0911 TP select 0 0 Touch probe via zero pulse Touch probe selection ^ 2-48
1 Touch-Probe through digital input X5/E4
C0912 TP edge 0 0 Activation with positive signal Setting of the touch probe activation ^ 2-48
1 Activation with negative signal with digital input X5/E4 (C0911 = 1)
C1120 Sync mode off 0 off ^
1 CAN Sync
2 Terminal Sync
C1121 Sync cycle 2 1 {1 msec} 13 ^
C1122 Sync phase 0.000 0.000 {0.001 ms} 6.500 ^
C1123 Sync-Window 0.000 0.000 {0.001 ms} 6.500 ^
C1190 Mot. PTC-Sel. 0 0 standard PTC selection for motor
1 Characterist.
C1191 0 {1 °C} 255 Selection of PTC temperature
1 Char.: temp 1 100 characteristic
2 Char.: temp 2 150
C1192 0 {1 W} 30000 Selection of PTC temperature
1 Char.: OHM 1 1670 characteristic
2 Char.: OHM 2 2225
C1799 DFOUT fmax 1250 20 {1 kHz} 1250 Maximum output frequency in kHz at ^ 2-38
C1810 S/W Id Keypad
C1811 S/W date Keyp
gg X10
^
^
C2100 Time slice 13 6 {0.1 ms} 26 ^
C2102 Task switch 2 0 Change-over only after the time disk has elapsed ^
1 Change-over end of cycl. task
2 Change-over end of cyclic task and end of sys.
task
C2104 PLC Autorun 0 0 does not start Automatic start of the PLC program
1 starts after power switch-on
C2106 Downl. protect 0 0 new download not possible write protection for the PLC program
1 new download possible
C2107 PwDownlProt. 0 0 {1} 4294967295 ^
C2108 PLC run/stop 1 0 no function PLC program will be ...
1 run 1: started
` stop 2: stopped (with simultaneous
3 reset setting of quick stop {QSP})
3: reset
C2111 GDC Id g
Lenze Choice
Compiling time / date of the PLC
C2121
C2350 XCAN Address
g
1
15
1
not assigned
{1}
AIF-Status
63 XCAN node address
^
^
C2351 XCAN baudrate 500 0 500 kBit/s XCAN baud rate ^
1 250 kBit/s
2 125 kBit/s
3 50 kBit/s
4 1000 kBit/s
C2352 CAN mst. 0 0 slave XCAN master operation ^
1 Master
C2353 CAN address sel1 0 CAN-Open, Node ID: DIP switch/C2350 ^
1 0 1 LENZE, selective addr. C2354 1: XCAN IN1/OUT1 addr.
2 0 2 LENZE, Node ID: DIP switch/C2350 2: XCAN IN2/OUT2 addr.
3 0 3: XCAN IN3/OUT3 addr.
C2354 XCAN sel. addr 1 {1} 513 ^
1 129 1: XCAN IN 1 selective addr.
2 1 2: XCAN OUT 1 selective addr.
3 257 3: XCAN IN 2 selective addr.
4 258 4: XCAN OUT 2 selective addr.
5 385 5: XCAN IN 3 selective addr.
6
C2355 XCAN Id
1
g
386 6: XCAN OUT 3 selective addr.
1: XCAN IN 1 Idenifier
^
.. 2: XCAN OUT 1 Identifier
6 3: XCAN IN 2 Identifier
4: XCAN OUT 2 Identifier
5: XCAN IN 3 Identifier
6: XCAN OUT 3 Identifier
C2356 CAN boot up 0 [1 ms} 65535 ^
1 300 1 XCAN Boot Up
2 0 2 XCAN Out1 cycle
3 0 3 XCAN Out2 cycle
4 0 4 XCAN Out3 cycle
5 3000 5 XCAN Cync Tx cycle
C2357 CE1 monit time 0 [1 ms} 65535 ^
1 3000 1 XCAN CE11 monitoring
2 3000 time
3 3000 2 XCAN CE12 monitoring
4 1 time
3 XCAN CE13 monitoring
time
4 XCAN CE14 monitoring
4.10 Index
A CANopen
Adressing the drives , 3-40
absolute addresses, 2-2 Communication profile of the system bus , 3-39
Data description , 3-39
Additional torque setpoint, 2-51 Identifier, 3-39
Addresses, absolute , 2-2 Selective identifier definition, 3-40
User data , 3-39
Analog inputs
Chopping frequency changeover , 2-55
Inputs_ANALOG1 (AIN1), 2-21
Inputs_ANALOG2 (AIN2), 2-23 Code number, Index, 3-31
CAN-bus
Baud-rate setting , 3-32 D
Boot-Up setting , 3-35 Data-type entry, Explanation of, 1-4
Bus load, 3-37
Definitions, 1-2
Bus Off, 3-38
Bus status, 3-36 Diagnosis codes , for CAN-bus, 3-36
Codes (description), 3-32 Digital frequency input (DF_IN), 2-31
Defining a master in a drive group , 3-32 Technical data for connection, 2-35
General address assignment , 3-33 Touch-probe, 2-36
Identifier, 3-35
Digital frequency output (DF_OUT), 2-38
Monitoring, 3-38
Technical data for connection, 2-42
Monitoring times , 3-38
Parameterization, 3-43 Drive control (DCTRL_DriveControl), 2-25
Example of a data format, 3-45
Index LOW/HIGH-byte, 3-44 DS 301, 3-39
Read a parameter (example), 3-47
Reset-Node, 3-38 E
selective addressing, 3-34
Telegram counter, 3-36 EarthFault, 2-59
Write a parameter (example), 3-46 Error messages, 4-11
CAN_Management, 3-22 Event-controlled process-data objects, 3-52
M
I
MCTRL_MotorControl, 2-48
Identifier, Explanation of, 1-4 MCTRL_nNmaxC11, 2-57
Monitoring functions R
Heatsink monitoring OH (fixed), 2-63
Heatsink monitoring OH4 (adjustable), 2-63 Rapid stop (Quickstop), 2-54
Plant speed monitoring NMax, 2-64 Reset, Fault message, 4-14
Motor control, 2-48
S
O Safety information, Layout
Operation inhibited(DISABLE), 2-27 Other notes, 1-1
Warning of damage to material, 1-1
Outputs_AIF1 (AIF1_OUT), 2-7
Set integral component, 2-52
Outputs_AIF2 (AIF2_OUT), 2-12
ShortCircuit, 2-59
Outputs_AIF3 (AIF3_OUT), 2-17
Signal type, Explanation of, 1-5
Outputs_ANALOG1 (AOUT1), 2-22
Speed controller, 2-51
Control terminals, Assignment, 2-22
Set integral component, 2-52
Outputs_ANALOG2 (AOUT2), 2-24
Statebus (STATEBUS_IO), 2-65
Control terminals, Assignment, 2-24
Status messages, 4-8
Outputs_CAN2 (CAN2_OUT), 3-16
Status signals, digital output, 2-29
Outputs_CAN3 (CAN3_OUT), 3-20
Status word, 4-8
Outputs_DIGITAL (DIGOUT), 2-44
Sync-Management, 3-25
Overcurrent diagram, 2-61
Synchronization of control program cycles, 3-25
Overvoltage, 2-58
System blocks
absolute addresses, 2-2
P Analog inputs and outputs (ANALOG_IO), Outputs_ANALOG2_IO
(AOUT2), 2-24
Parameter channels, 3-7
Automation interface (AIF1_IO), 2-4
Parameterization, CAN-bus, 3-43 Automation interface (AIF2_IO), 2-10
Automation interface (AIF3_IO), 2-15
Phase controller, Phase controller influence, 2-53
CAN_Management, 3-22
Plant speed monitoring NMax, 2-64 Digital frequency input (DF_IN), 2-31
Technical data for connection, 2-35
PLC functionality, 4-1
Digital frequency output (DF_OUT), 2-38
Prefix, Explanation of, 1-3 T, 2-42
Drive control (DCTRL_DriveControl), 2-25
Process data, 3-48 Controllerinhibit (CINH), 2-28
Operation inhibited(DISABLE), 2-27
Process data channels, 3-8 output digital status signals, 2-29
cyclic, 3-8 Quickstop (QSP), 2-27
event-controlled, 3-9 TRIP-RESET, 2-28
TRIP-SET, 2-28
Process-data objects, 3-49 Free codes (FCODE), 2-45
event-controlled, 3-52 Inputs_ANALOG1 (AIN1), 2-21
PTCOverTemp, 2-61 Inputs_ANALOG2 (AIN2), 2-23
Inputs_DIGITAL (DIGIN), 2-44
Module numbers, 2-2
Q Outputs_AIF2 (AIF2_OUT), 2-12
Outputs_ANALOG1 (AOUT1), 2-22
Quick stop (QSP), 2-54
Statebus (STATEBUS_IO), 2-65
Quickstop (QSP), 2-27 System markers (SYSTEM_FLAGS), 2-67
T
Temporary codes, 4-15
TMot>C0121, 2-60
TMot>SetValue, 2-60
Torque control, with speed limit, 2-52
Torque limiting, 2-51
Touch-probe
with SB DF_IN, 2-36
with SB MCTRL, 2-56
TRIP, 4-4
TRIP-RESET, 2-28
TRIP-SET, 2-28
Troubleshooting, 4-7