The controller is a source of danger which may cause death or serious personal injury.
In order to ensure protection against this danger, observe the safety instructions before
switching on the controller.
Please read the safety instructions in the mounting instructions and hardware manual
of the Servo-Inverter 9400 HighLine. Both instructions are included in the scope of
supply.
Target group
This documentation addresses to all persons who want to parameterise, configure, and diagnose
the 9400 HighLine controller by means of the engineering software L-force »Engineer« and the
keypad.
Validity
The information in this documentation are valid for the following standard devices:
Product seriesType designationfrom software version
9400 Servo DrivesE94AxHExxxx1.5
Screenshots/application examples
All screenshots in this documentation are application examples. Depending on the firmware
version of the 9400 HighLine and the software version of the engineering tools installed
(»Engineer« or » Easy Starter«), the screenshots in this documentation may deviate from the screen
representation.
Engineering toolsSoftware solutions for easy engineering in all project stages
»EASY Navigator« – provides a good guide to the user
• All convenient Lenze engineering tools at a glance
• Tools can be selected quickly
• The clear structure simplifies the engineering process from the start
»EASY Starter« – easy-to-use tool for service technicians
• Specially designed for the commissioning and maintenance of Lenze
devices
• Graphical user interface with just a few buttons
• Easy online diagnostics, parameterisation, and commissioning
• No risk of an unintended change in applications
• Loading of ready-to-use applications to the device
»Engineer« – multi-device engineering
• For all products in our L-force portfolio
• Practical user interface
• Graphic interfaces make it easy to navigate
• Can be applied in every phase of a project (project planning,
commissioning, production)
• Parameter setting and configuration
L-force ControllerThe L-force controller is the central component of the automation system which (by
means of the runtime software) controls the Logic and Motion functionalities.
The L-force Controller uses the fieldbus to communicate with the field devices.
Engineering PCThe Engineering PC and the engineering tools installed on it serve to configure and
parameterise the system.
The Engineering PC uses Ethernet to communicate with the L-force Controller.
Code"Container" for one or several parameters used for controller parameter setting or
monitoring.
SubcodeIf a code contains several parameters, the individual parameters are stored under
"subcodes".
This Manual uses a slash "/" as a separator between code and subcode (e.g. "C00118/3").
Function block editorGraphical interconnection tool which is provided for controllers in the MotionControl
HighLevel and TopLevel license level in the »Engineer« on the FB editor tab and by means
of which the technology applications supplied can also be reconfigured and extended by
individual functions.
Function blockA function block (FB) can be compared with an integrated circuit that contains a specific
control logic and delivers one or several values when being executed.
• A n in stan ce ( repro ducti on, co py) of the f unc tion b lock i s alw ays inser ted in the ci rcuit .
• It is also possible to insert several instances of a function block in a circuit.
• Each instance has an unequivocal identifier (the instance name) and a processing
number which defines the position at which the function block is calculated during
the task cycle.
The basis of every L-force application is an easy and quick parameter setting of prepared technology
applications and solutions*.
This chapter contains basic information on the runtime software model of L-force and on how you
can establish an online connection between the PC and controller for parameter setting with
»Engineer« very easily.
At the end of this chapter you will find an overview of the different signal types & scaling which
serve to process physical values (e.g. a speed or position) within the application.
* In preparation!
2.1Parameter setting, configuring, or programming?
The graded runtime software model of L-force provides a simple and consistent solution for motion
and process tasks as well as for complex machine functions:
Runtime software
PLC levelProgramming*
Freely programmable open and closed
loop control functions*
Technology levelConfiguring
Motion Control TopLevel
Additional motion and process control
modes for complex drive tasks.
Motion Control HighLevel
Individual extensibility of the basic
functions & technology applications by
means of the function block editor and
the comprehensive function library.
The HighLevel and TopLevel licenses enable you to
extend the provided technology applications by
individual functions using the graphic function block
editor of »Engineer«. Here you can access the
comprehensive function libraries of Lenze which
among other things contain process controllers,
arithmetic functions, logic blocks, and ramp
generators and integrators.
Parameter setting
The StateLevel license includes a range of technology
applications which can be put into operation easily
with a keypad or via dialogs in »Engineer«.
Important basic drive functions and further basic functions are implemented in the firmware of the
controller and thus are always provided, irrespective of the runtime software licence available.
Firmware
Motion Control basic drive functionsFurther basic functionalities
• Stop
• Quick stop
• Manual jog
• Homing
• Positioning
• Position follower
• Speed follower
• Torque follower
• Limiter
• Brake control
• Drive interface
• Motor interface
• Encoder evaluation
• I/O terminals
• Safety engineering
• Logbook
• Oscilloscope
2.1.2Technology applications
Technology applications (TAs) are applications prepared by Lenze which can serve as a basis for
solving typical applications.
• The technology applications available for the Servo Drives 9400 can be selected in »Engineer«
from the application catalogue.
The following interfaces/communication modules can be used to establish communication
between the PC and controller:
• Diagnostic interface X6/Going online via diagnostic adapter
• CAN on board interface/Going online via system bus (CAN on board) ( 20)
• Optional interfaces which are provided by corresponding communication modules in the
module slots MXI1/MXI2 of the controller.
Note!
For communication with the controller, at least the control electronics of the controller
must be supplied with 24 V low voltage via plug X2. For detailed information, please see
the Mounting Instructions for the controller.
Stop!
If you change parameters in the »Engineer« while the controller is connected online, the
changes will be directly accepted by the controller!
Tip!
Detailed information about the individual interfaces can be found in the corresponding
Communication Manuals (KHB).
2.2.1Going online via diagnostic adapter
For initial commissioning of the controller you can for instance use the diagnostic adapter offered
by Lenze:
Note!
Please observe the documentation for the diagnostic adapter!
If no communication path was configured yet for the controller selected, the
Communication path dialog box is shown after the update has been carried out:
• The "Diagnostic adapter" bus connection is already preset.
3. Click on Connect.
• The dialog box is closed and the online connection with the controller is built up.
•In the Project view a yellow icon indicates the online connection with the controller:
Now you can use the icons and to easily build up and end a connection with the controller.
The communication settings are only required when communication with a controller is built up for
the first time.
• If you want to change the configured communication path, select the command Online Set
communication path and go online to open the Communication path dialog box and change the
settings.
• When an online connection has been established, the »Engineer« displays the current
parameter settings of the controller with a yellow background colour.
As an alternative to the diagnostic adapter, you can use the integrated system bus interface (CAN on
board, terminal X1) of the controller for communication.
• Lenze offers the following communication accessories for connection to the PC:
Communication accessoriesPC interface
PC system bus adapter 2173
incl. connection cable and voltage supply adapter
• for DIN keyboard connection (EMF2173IB)
• for PS/2 keyboard connection (EMF2173IBV002)
• for PS/2 keyboard connection with electrical isolation (EMF2173IBV003)
PC system bus adapter 2177
incl. connection cable (EMF2177IB)
Parallel interface
(LPT port)
USB
(Universal Serial Bus)
Note!
• For detailed information about the PC system bus adapter, please see the "CAN
Communication Manual".
• Please observe the documentation for the PC system bus adapter!
• The online connection is established as described in the previous chapter "Going
online via diagnostic adapter", only that this time the entry "CAN system bus" is to be
selected in the Bus connection list field of the Communication path dialog box.
( 18)
2.2.3Use of other communication interfaces
The controller can be extended by further communication interfaces, if required, e.g. Ethernet,
ETHERNET Powerlink, or PROFIBUS.
• For this the controller is provided with the module slots MXI1 and MXI2 for accepting
communication modules.
• Detailed information on this subject can be found in the Hardware Manual and Communication
Manual for the corresponding communication system.
It is very helpful for the parameterisation & configuration of the controller to know the signal types
and their scaling listed below, which serve to process physical quantities (e.g. a speed or position)
within the function block interconnection.
Note!
From software version V3.0 the resolution of an encoder revolution can be
This documentation contains detailed information on parameter setting and configuration of the
controller. Sequential reading is not required.
In order to obtain the information relevant for initial commissioning, this chapter describes
different commissioning scenarios which can also be used as a guide through this manual:
A. Initial commissioning
• Target: Adapting the controller to the electromechanics and the control system.
B. Standard set-up
• Target: Taking over the application and parameter set of an already preconfigured "Engineer"
project into several controllers.
( 25)
( 26)
C. Controller replacement
• Target: Replacing a controller which has failed in a running system by a replacement device
using the "old" memory module.
D. Motor replacement
• Target: Replacing a motor which has failed in a running system.
Some parameters of the controller have a setting range depending on the device type.
If parameterisation is carried out offline or if the memory module is exchanged between
different 9400 HighLine device types, always check the settings of the parameters listed
in the following table and adapt them, if required, to prevent a parameter error after the
parameter set download or module change!
ParameterInfoLenze setting
C00018
C00022
C00173
C00174
Switching frequency8 kHz variable
Maximum current
Accepting/adapting plant parameters
Mains voltage and undervoltage threshold (LU)
Machine parameters
( 29)
( 124)
0.00 A
400/415 V, LU = 285 V
Tip!
The rated data of the different device types can be found in the Hardware Manual in the
"Rated data" chapter.
Term definition of "Plant parameters"
The term "plant parameters" which is frequently used in the following chapters summarises all
parameters which result from the combination of motor and load. They characterise the transfer
behaviour of the entire controlled system including the desired monitoring functions. The plant
parameters depend on the application in which the controller and motor are used.
• A display of the plant parameters offered by ENP via keypad is not provided. The plant
parameters must be edited and optimised individually.
• To avoid that the motor starts unintentionally without adjusting the plant parameters, the
maximum current in the Lenze setting is set to "0 A" in C00022
• After setting the plant parameters, they have to be saved on the memory module of the
controller with mains failure protection, just as the motor data that have been read out from
the ENP (C00002
For a motor without an electronic nameplate (ENP)
• The motor data and plant parameters must be edited and set individually.
• To avoid that the motor starts unintentionally without adjusting the plant parameters, the
maximum current is set to "0 A" in C00022
• After setting the motor data and plant parameters, they have to be saved on the memory
module of the controller with mains failure protection (C00002
= "11: Save start parameters").
by the factory.
.
= "11: Save start parameters").
Commissioning of the application
• The application must already be stored on the memory module of the controller. Otherwise
commissioning by only using the keypad is not possible.
• All application parameters which deviate from the factory adjustment have to be edited
individually. For this the project planner has to provide a corresponding list to the commissioner
(including the motor and plant data).
• In the case of a standard set-up, a pole position identification may have to be carried out for
synchronous motors of a third party manufacturer or Lenze synchronous motors with a
Stegmann absolute value encoder.
• After setting the parameters, they have to be saved on the memory module of the controller
with mains failure protection (C00002
= "11: Save start parameters").
Tip!
Detailed information on the individual technology applications can be found in the
corresponding Software Manual for the technology application and the »Engineer« online
help in the chapter "L-force Servo Drives 9400 Technology applications".
1. Read out the motor data of the controller or select them via the »Engineer« motor catalogue.
• If the motor connected to the controller is provided with an electronic nameplate (ENP), all motor
data are automatically read out from the ENP and a selection in the motor catalogue is not required.
Reading out motor data from the controller
• If a motor without ENP or a motor by a third-party manufacturer is used, the selection is carried out
via the »Engineer« motor catalogue. Selecting a motor from the motor catalogue in the »Engineer«
( 118)
2. Select motor control
• Servo control is preset for the synchronous motor.
3. Adjusting motor and controller to each other
4. Carry out settings for selected motor control.
• For this see description for the corresponding motor control:
• Servo control (SC)
• Sensorless vector control (SLVC) (from software version V3.0)
• V/f control (VFCplus)
• V/f control (VFCplus)
Parameterise/configure application:
5. Load & parameterise technology application.
Detailed information on the individual technology applications can be found in the corresponding
Software Manual for the technology application and the »Engineer« online help in the chapter "L-force
Servo Drives 9400 Technology applications".
6. If required, reconfigure the interconnection of the technology application with the function block editor.
Optimise control mode:
7. Optimise control mode of the selected motor control.
• By means of traversing profile from the application and oscilloscope.
• For this see description for the corresponding motor control:
• Servo control (SC)
• Sensorless vector control (SLVC) (from software version V3.0)
• V/f control (VFCplus)
• V/f control (VFCplus)
Save project and parameter set:
8. Execute device command C00002
9. Save »Engineer« project.
. ( 121)
(from software version V3.0)
(from software version V3.0)
(from software version V3.0)
(from software version V3.0)
= "11: Save start parameters".
( 117)
( 123)
More (optional) worksteps
Worksteps
Establish network:
1. Insert network and machine application into the »Engineer« project.
2. Interconnect port blocks reasonably to each other within the machine application.
3. Configure network (set addresses, baud rate, and process data channels in a reasonable manner).
4. Establish communication with the control system.
5. Establish communication with other drive components (e.g. HMIs, I/O extensions and other controllers).
Scenario: The controller has failed in a running system.
Note!
For the procedure described in the following it is assumed that the memory module and
possibly available extension modules in the controller, as well as the motor are not
affected by the failure and that all parameters have been saved with mains failure
protection.
Worksteps
Replacement of the controller:
1. Replace controller.
See Mounting Instructions for the controller!
2. Insert the memory module of the failed controller into the replacement device.
3. If further extension modules are plugged into the failed controller, they must be inserted into the
replacement device as well.
Further steps are not required since all data required are on the memory module.
3.6Motor replacement
Scenario: The motor has failed in a running system.
Note!
For the procedure described in the following it is assumed that the controller is not
affected by the failure.
Worksteps
Replacement of the motor:
1. Replace the motor.
See Mounting Instructions for the controller!
Note:
The motor connection on the controller is accessible without having to remove the standard device
from the installation backplane.
For a motor with an electronic nameplate (ENP):
2. Restart controller with connected motor to read out the motor data from the electronic nameplate.
• Either by switching off/switching on again the voltage supply or by means of device command
C00002
• See chap. Motor interface
3. Execute device command C00002
For a motor without an electronic nameplate (ENP):
Note:
The motor is operated with the motor data and plant data from the memory module.
= "11000: Restart controller".
Reading out motor data from the controller ( 117)
This chapter provides you with information on the drive interface via which you can control the
drive controller into specific states and call different pieces of status information of the controller.
Furthermore the machine constants for the motor end are entered via the drive interface.
How to get to the dialog for setting the drive interface parameters:
1. Go to the Project view of the »Engineer« and select the 9400 HighLine controller.
2. Select the Application parameters tab from the Workspace.
3. Click the following button of the Overview dialog level:
Parameterisation dialog in the »Engineer«
• The white buttons indicate the configuration of the drive interface inputs. Internal interfaces
| "LS_DriveInterface" system block ( 110)
• The assignment is predefined by the technology application selected (in the example
"Actuating drive – speed"). If required, this assignment configuration can be changed by
clicking the corresponding buttons.
• If you click a button marked with the symbol, you go one level deeper in the corresponding
parameterisation dialog.
The global machine constants ("machine parameters") are set in the »Engineer» on the Application
parameters tab in the dialog level Overview Drive interface Machine parameters:
Tip!
Detailed information on the different machine parameters can be obtained from the
following subchapters.
Via the Mains voltage list field (C00173) the mains voltage for the controller is set.
• If you set a mains voltage with an adjustable threshold for undervoltage ("LU adjustable"), this
undervoltage threshold can be set in the Undervoltage threshold (LU) input field (C00174
•In the Resp. to DC-bus overvoltage list field (C00600
effected when a DC-bus overvoltage occurs.
) you can select the response that is to be
).
Note!
Changing the setting in C00173 also affects the permissible device utilisation!
Tip!
In the chapter "Rated data" of the hardware manual the device types and their permissible
device utilisation at a certain mains voltage and switching frequency are specified.
See also:Monitoring of the device utilisation ( 108)
The gearbox ratio indicates the number of revolutions of the motor axis it takes for exactly one
revolution of the load axis (e.g. spindle or drive roll) to take place.
[4-1]Schematic diagram of gearbox ratio
• In the example shown in illustration [4-1] one revolution of the spindle is carried out at exactly
58,667 revolutions of the motor axis.
Specification of the gearbox ratio
• The gearbox ratio is to be defined in the form of a quotient (numerator/denominator); the data
required can be found in the technical data for the gearbox:
[4-2]Example: Technical data relating to the gearbox (from gearbox catalogue)
Tip!
In order to specify the gearbox ratio exactly, use the number of teeth indicated on the data
sheet or in the catalogue, if possible, instead of the information on the nameplate (see
following calculation).
In C02531/1
Example calculation on the basis of the technical gearbox data:
[4-3]Calculation example
the gearbox factor is displayed in decimal format.
Depending on the motor mounting position, you can carry out an inversion of the direction of
rotation via the Motor mounting direction list field (C02527
), if required:
• C02527
• C02527
4.1.4Feedback configuration
In most cases the system only has one motor encoder, i.e. no separate position encoder is installed
on the load side. The motor position (angle of rotation) and motor speed are detected via the motor
encoder selected in C00495
Motor encoder
[4-4]Schematic diagram - feedback with position encoder = motor encoder
The actual position and speed values on the machine side result from the conversion via the
Gearbox ratio
Tip!
= "0": Clockwise rotating motor ≡ positive machine direction.
= "1": Counter-clockwise rotating motor ≡ positive machine direction.
on the motor side and the Feed constant.
Detailed information on the parameterisation of the feedback systems for the motor
control can be found in the chapter "Encoder evaluation
Via these machine parameters you define the real unit of the machine in which the feed constant
and the parameters for a travel profile must be specified (e.g. position, speed, acceleration, and
deceleration).
• If you for instance set the unit "mm" for a linear axis, the position must be specified in [mm] and
the speed in [mm/s].
• By means of the user-defined unit, significant production units, like for example "bottles" can
also be set.
• For this, select the "User-defined" entry as unit in C02525
defined unit in C02526
.
and then enter the desired user-
Note!
In this documentation the term "unit" in the parameter unit data only serves as a
wildcard for the real unit of the machine.
The feed constant corresponds to the movement of the machine during one revolution of the
gearbox output shaft.
• The entry in the Feed constant field (C02524
one revolution.
• In the case of a conveyor drive, the feed constant is obtained from the drive roll's circumference,
which, in the following example, is calculated on the basis of the indicated diameter:
d = diameter
[4-8]Schematic diagram: Feed constant for a conveyor driver
• In the case of a spindle drive (linear axis), the feed constant is derived from the leadscrew pitch.
The feed constant indicates the distance the slide travels during one revolution of the spindle
(in the following example: 5.023 mm).
) is made in the unit defined in C02525 relating to
h = leadscrew pitch (can be obtained from the technical data of the linear axis)
[4-9]Schematic diagram: Feed constant for a spindle drive
• In the case of a rotary table and its specification as an angle, the feed constant is = 360°/
revolution.
The following applies to software versions lower than V3.0:
The resolution of an encoder revolution and hence of a position value is constantly set to 16 bits/
revolution, which corresponds to 65536 increments/revolution. At this resolution, the traversing
range comprises ±32767 revolutions.
The following applies from software version V3.0:
C00100
Sign bit
Number of revolutions: 15 bits ≡ ±32767 revolutions
Resolution of one encoder revolution: 16 bits ≡ 65536 increments/revolution
serves to adjust the resolution to the application.
• The default resolution of 16 bits/revolution is sufficient for standard applications.
[4-10] Example: standard resolution (16 bits/revolution)
• For more significant applications, a higher resolution of the position values can clearly improve
the control properties and positioning accuracies:
• Finer resolution of the position targets improved positioning accuracy
• Finer quantisation of setpoints and actual values better control quality
• Higher loop gain adjustable less following errors
• However, a higher resolution at the same time causes a restricted number of encoder
revolutions, and only smaller traversing distances can be displayed.
Sign bit
Number of revolutions: 9 bits ≡ ±512 revolutions
Resolution of one encoder revolution: 22 bits ≡ 4194304 increments/revolution
[4-11] Example: Higher resolution (22 bits/revolution) with a restricted traversing range
Tip!
In the following subchapter "Determining the optimum resolution
how you can determine the optimum resolution of the position values.
The position values (e.g. setpoints, actual values, parameters, …) in the signal flow
always use the resolution set in C00100
resolution is delivered directly by the encoder.
Multi-axis systems
In an interconnection via the electrical shaft, at least two measuring systems (master
and slave) are available in the drive.
• Each measuring system is provided with an individual setting of the resolution.
• The machine parameters (gearbox factors, feed constants, encoder resolution and
cycle) for the master measuring system or master value must be set identically for all
drives in the system.
Technology applications "Electronic gearbox" and "Synchronism"
For these two technology applications the machine parameters of the master measuring
system are defined on the Application parameters tab in the "Master value scaling"
dialog level.
Electronic cam
The machine parameters of the master measuring system for electronic cams can be
defined on the Measuring systems tab for the electrical shaft.
This function extension is available from software version V3.0!
How to determine the optimum resolution:
In the dialog level Overview Drive interface Machine parameters:
1. Set gearbox factors.
2. Set real unit of the machine.
3. Set feed constant.
4. Press the Optimum positional resolution button.
•The Optimum positional resolution dialog box is displayed:
5. Go to the Max. presentable position input field and enter the highest position which is to
be entered in a parameter during operation.
• If required, set a reserve in the Overshoot input field to take into account possible
following errors (overshoot of actual values).
Then the maximum resolution for the position entered is shown in the Maximum resolution for encoder revolution field.
6. Click Accept value to accept the displayed resolution in C00100
7. Click Close to close the dialog box again.
.
Tip!
In order to display the position that can be maximally represented for a defined resolution,
activate the second option Determine max. presentable position. Then you can set the
resolution for which the maximally presentable position is to be displayed in the Maximum resolution for encoder revolution input field.
4.1.9Max. position, speed, and acceleration that can be displayed internally
By setting the following machine parameters, the connection between the real units (application
units) of the machine and the internal units in the controller is described:
• Gearbox ratio (C02520
• Feed constant (C02524
• Resolution of an encoder revolution (C00100
Possibly the defined values for position, speed, and acceleration cannot be represented in the
internal units by the numerical 32-bit format used.
• The following display parameters show the values that can be maximally displayed:
ParameterInfoLenze setting
C02539Max. presentable position- Unit
C02540Speed that can be maximally displayed- Unit/s
C02541Acceleration that can be maximally displayed- Unit/s
Greyed out = display parameter
Response if a value that cannot be displayed internally is entered
If a position, speed, or acceleration which cannot be represented internally is defined via
parameters, the value defined is limited to the maximum value that can be represented internally
(±2147483647).
The following only applies to software version V3.0:
• If a position, speed, or acceleration which cannot be represented internally is defined via
parameters, the value defined is rejected.
• If an internal counter overflow of a parameter value due to a subsequent change of the machine
parameters for the gearbox ratio, feed constant, or resolution of an encoder revolution is
detected, the "Fault" error response is triggered and a corresponding error message is entered
in the logbook of the controller:
In the following subchapters the device commands of the controller are described, which are
provided in C00002
keypad when an online connection has been established.
and which can be executed by means of the »Engineer« or alternatively with the
Note!
Before switching off the supply voltage after a device command has been executed,
check the successful execution of the device command via the status display in C00003
!
The meaning of the status display in C00003
the corresponding device command.
Activating frequently required device commands via the toolbar
The simplest way to execute the frequently required device commands is directly via the Toolbar of
»Engineer« when an online connection has been established.
IconFunction
Enable controller
Inhibit controller
Start application
Inhibit controller and Stop application
can be obtained from the subchapter for
Note!
Device commands that can be executed via the Toolbar of the »Engineer« always affect
the element currently selected in the Project view including all subelements!
• If no controller but a system module is selected in the Project view, the corresponding
device command will be activated in all lower-level controllers having an online
connection with the »Engineer«.
Before the desired action is carried out, a confirmation prompt appears first, asking
whether the action is really to be carried out.
The C00002 = "0: Load Lenze setting" device command is used to reset the parameters of the active
application to the Lenze setting, which is stored in the controller firmware:
[4-12] "Load Lenze setting" function
• Only possible when the application has stopped and the controller is inhibited.
• All parameter changes made since the last saving of the parameter set will get lost!
• This device command only affects the settings of the operating system, application and module
parameters, the active application or the configuration selected with the function block editor
remains unchanged.
Via C00002 = "1: Load start parameters" the start parameters of the active application can be
reloaded from the memory module to the controller:
* In this example, application 1 is the active application
[4-13] "Load start parameters" function
• Only possible when the application has stopped and the controller is inhibited.
• All parameter changes made since the last saving of the parameter set will get lost!
• This device command only affects the settings of the operating system, application and module
parameters, the active application or the configuration selected with the function block editor
remains unchanged.
Possible status displays for this device command
Status (C00003)Meaning
99586 Device command in process
65536 Device command executed successfully
65537 General fault
99371 Fault while reading the parameter set partition
If the Lenze motor connected to the controller is provided with an electronic nameplate (ENP), all
motor data are automatically read out from the electronic nameplate of the motor when the
controller is switched on for the first time and are temporarily stored in the controller at first.
With the device command C00002
the electronic nameplate (ENP) of the motor.
• Only possible when the application has stopped and the controller is inhibited.
• For a permanent acceptance of the motor data, the parameter set must be saved.Save start
parameters ( 49)
• The following plant data are read out from the ENP:
ParameterInfo
C00022
C00070Speed controller gain
C00071
C00596
Maximum current
Speed controller reset time
Threshold max. speed reached
= "2: ENP: Load plant data" the motor data can be reread from
Note!
The two pieces of plant data C00011 and C00497 listed in the following table are not
read out from the ENP and thus have to be checked and, if required, set manually after
this device command has been executed!
If several applications are available on the memory module, the C00002 = "5: Activate application"
device command can be used to activate the application the number of which has been set in
C00005
* In this example, application selection "2" is set in C00005
[4-14] "Activate application" function
.
• Only possible when the application has stopped and the controller is inhibited.
• Whether the application is started at the same time, depends on the auto-start setting selected
in C02104
.
• After mains switching, the preset application will be loaded into the controller.
• If after mains switching another application than the one preset by Lenze is to be loaded, it must
be activated first and then the selected application must be saved with the device command
"Save selected application
• The number of the currently active application is displayed in C00007
". ( 48).
.
Note!
When the application is activated, the corresponding start parameter set is loaded
automatically and parameter settings executed before will get lost unless the parameter
set was saved before!
After mains switching the controller always loads the preset start application from the memory
module, even if a different application has been active before.
With the device command C00002
= "7: Save selected application" the active application can be
defined as start application.
* In this example, the active application 2 is defined as start application
[4-15] "Save selected application" function
• When this device command is executed, the parameter set is also saved automatically.
• The number of the currently active application is displayed in C00007
Controller parameter changes made via »Engineer« or keypad will get lost after mains switching of
the controller or loading of another application unless the settings have been explicitly saved.
With the device command C00002
the active application can be saved with mains failure protection in the memory module of the
controller:
* In this example, application 1 is the active application
[4-16] "Save start parameters" function
= "11: Save start parameters" the current parameter settings of
Tip!
With the keypad this device command can be executed via the left function key if it is
currently assigned with the function.
Note!
The saving process can take several seconds. Before you switch off the supply voltage
after having executed this device command, therefore be absolutely sure to check via
the status display in C00003
successfully!
From software version V4.0, this device command also includes the powerfail-proof
saving of the cam data on the memory module.
• The saving process is only carried out if the cam data in the controller and the memory
module differ from each other (based on the time stamp/GUID of the cam data).
• For saving the cam data, you do not need to enter a possibly existing user password
(C02900
•The C00002
data ( 89)
).
= "502: Save Cam Data" device command remains available.Save cam
The C00002 = "34: Delete program" device command is used to delete the application program in
the controller and reset the controller to its original state.
• All variables are reset to their initialisation value.
When the application is started, the controller continuously carries out a runtime measurement for
the interval-controlled application task, the interval-controlled user task, and the free-running idle
task and displays the current and maximum task runtimes via parameters.
The C00002
measurement, i.e. the memory for the maximum values is reset to "0".
Possible status displays for this device command
Status (C00003)Meaning
= "36: Reset runtime measurement" device command is used to reset the runtime
2393346 Device command in process
2359296 Device command executed successfully
2359297 General fault
Note!
The runtime measurement is also reset by the following actions:
The C00002 = "41: Inhibit controller" device command is used to inhibit the controller ("controller
inhibit"), i.e. the power output stages in the controller are inhibited and the speed/current and
position controllers of the motor control are reset. The motor becomes torqueless and coasts unless
it is already at standstill.
• The controller can also be inhibited by other sources, e.g. via the digital input RFR or through the
application.
• C00158
provides a bit coded representation of all active sources/triggers of a controller inhibit.
Note!
This device command has no status display in C00003, i.e. the display remains
unchanged showing the previous device command status.
Tip!
This device command can also be activated via the icon in the Toolbar.
The C00002 = "43: Reset error" device command is used to acknowledge an error message if the
error cause has been eliminated and the error is thus no longer pending.
Tip!
An error message can also be acknowledged by activating the Reset error button in the
Diagnostics tab.
Further information on error messages can be found in the chapter "Diagnostics & fault
analysis". ( 598)
Note!
This device command has no status display in C00003, i.e. the display remains
unchanged showing the previous device command status.
The C00002 = "45: Activate quick stop" device command is used to activate the basic function
"Quick stop", i. e. the drive is brought to standstill within the deceleration time set, irrespective of
the setpoint defined.
• Quick stop can also be activated by other sources, e.g. by the application.
• C00159
displays a bit code of active sources/causes for the quick stop.
Note!
The activation of quick stop may cause following errors in superimposed controls (e.g.
synchronous or position control). If several drives execute a coordinated movement, the
quick stop function should therefore only be used for the motion master (master drive)
in order to maintain the coordination.
This device command has no status display in C00003
unchanged showing the previous device command status.
, i.e. the display remains
Tip!
In contrast to the "stop" function, quick stop is required for a stop in the event of an error.
Thus, quick stop can also be set as an error response ("quick stop by trouble) for many
monitoring functions. Detailed information on this can be found in the chapter
"Diagnostics & fault analysis
If no absolute value encoder is connected, or a synchronous motor of a third-party manufacturer is
driven by the controller, the C00002
determine the pole position with regard to the motor encoder currently activated in C00495
• The function can only be activated if the controller is inhibited. Then the execution of the
function starts automatically as soon as the controller inhibit is deactivated again.
• During the pole position identification, the motor carries out one electrical revolution. This
leads to a mechanical rotation of the motor shaft.
• The determined pole position is indicated under code C00058
= "51: Identify pole position (360°)" device command is used to
.
.
Note!
From software version V4.0 the response parameterised in C00640 (Lenze setting:
"Fault") is triggered and the error message "Pole position identification cancelled" is
entered in the logbook of the controller if the pole position identification process is
aborted.
Tip!
Detailed information on the pole position identification can be found in the chapter "Motor
interface", subchapter "Pole position identification
Possible status displays for this device command
Status (C00003)Meaning
3376386 Device command in process
3342336 Device command executed successfully
3342337 General fault
3382023 Pole position identification cannot be executed because of wrong motor type (asynchronous
motor).
3382024 Pole position identification has been aborted
3382025 Pole position identification cannot be executed because another identification is already
active.
3382026 Identification of pole position cannot be executed because U-rotation or I-rotation test
mode is active.
3382027 Identification of pole position cannot be executed because current controller optimisation
mode is active.
3382033 Pole position identification cannot be executed because the motor is blocked (e.g. by a
mechanical brake), a motor phase is not connected, or a phase shifter is in the motor cable.
3382047 Pole position identification cannot be executed because an error or trouble is active.
3382065 Pole position identification cannot be executed because either the entire motor or a motor
phase is not connected.
• This error message is only available from software version V3.0 onwards.
If no absolute value encoder is connected, or a synchronous motor of a third-party manufacturer is
driven by the controller, the C00002
used to determine the pole position with respect to the motor encoder currently activated in
C00495
.
• The function can only be activated if the controller is inhibited. Then the execution of the
function starts automatically as soon as the controller inhibit is deactivated again.
• During the pole position identification, the rotor aligns itself. This is compensated by a position
control.
= "52: Identify pole position (min. motion)" device command is
• The determined pole position is indicated under code C00058
.
Note!
From software version V4.0 the response parameterised in C00640 (Lenze setting:
"Fault") is triggered and the error message "Pole position identification cancelled" is
entered in the logbook of the controller if the pole position identification process is
aborted.
Tip!
Detailed information on the pole position identification can be found in the chapter "Motor
interface", subchapter "Pole position identification
Possible status displays for this device command
Status (C00003)Meaning
3441922 Device command in process
3407872 Device command executed successfully
". ( 128)
66
3407873 General fault
3447559 Pole position identification cannot be executed because of wrong motor type (asynchronous
motor).
3447560 Pole position identification has been aborted
3447561 Pole position identification cannot be executed because another identification is already
active.
3447562 Identification of pole position cannot be executed because U-rotation or I-rotation test
mode is active.
3447563 Identification of pole position cannot be executed because current controller optimisation
mode is active.
3447569 Pole position identification cannot be executed because the motor is blocked (e.g. by a
mechanical brake), a motor phase is not connected, or a phase shifter is in the motor cable.
• This error message is only available from software version V4.0 onwards.
3447583 Pole position identification cannot be executed because an error or trouble is active.
3447597 Identification of pole position cannot be executed because the rotor has moved too strongly.
3447601 Pole position identification cannot be executed because either the entire motor or a motor
phase is not connected.
• This error message is only available from software version V3.0 onwards.
This function extension is available from software version V7.0!
The C00002
which are caused when sine and cosine tracks do not magnetise orthogonally. The identified
resolver errors serve to compensate the resolver errors.
Detailed information on the resolver error compensation can be found in the chapter
"Encoder evaluation" in the subchapter "Resolver error compensation
Possible status displays for this device command
Status (C00003)Meaning
3900674 Device command in process
3866624 Device command executed successfully
3866625 General fault
3906358 Resolver error identification cannot be executed since the wrong control type is active (no
3906359 Resolver error identification cannot be executed since an error or trouble is active.
3906360 Resolver error identification cannot be executed because another identification is already
3906361 Resolver error identification cannot be executed because of too small speed (< 500 rpm).
This function extension is available from software version V4.0!
If determination of the so-called "inverter error characteristic" is not possible with the device
command "Calculate inv. characteristic
C00002
the device in question.
= "70: Load Lenze INV characteristic" can be used to load a characteristic which is typical of
• Only possible when the controller is inhibited.
" or leads to incorrect results, the device command
Tip!
Detailed information about the determination of the inverter error characteristic can be
found in the chapter "Motor interface" in the subchapter "Optimising the switching
If a motor of a third-party manufacturer with unknown motor parameters is driven by the
controller, the C00002
determine the so-called "Inverter error characteristic" for optimising the inverter switching
performance.
= "71: Determine inverter characteristic" device command can be used to
Tip!
Detailed information about the determination of the inverter error characteristic can be
found in the chapter "Motor interface" in the subchapter "Optimising the switching
performance of the inverter". ( 135)
From software version V4.0: If the inverter error characteristic cannot be determined by
means of this device command, or if the results of the determination are incorrect, the
device command "Load Lenze INV characteristic
of the device.
( 69)
" can be used to load a characteristic typical
Possible status displays for this device command
Status (C00003)Meaning
4687106 Device command in process
4653056 Device command executed successfully
Related device commands
4653057 General fault
4692754 The calculation of the inverter characteristic cannot be started since the current controller
test mode is active.
4692755 The calculation of the inverter characteristic cannot be started since the V/f test mode is
active.
4692756 The calculation of the inverter characteristic cannot be started since the pole position
identification is active.
4692757 Calculation of the inverter characteristic has been aborted.
4692758 Calculation of the inverter characteristic has been interrupted by error.
The C00002 = "72: Determine motor parameters" device command is used to automatically
determine the motor parameters for a third-party motor that are listed in the following table – if
they are not known:
ParameterInfoASMSM
C00079
C00082
C00084
C00085
C00091
C00092
Mutual motor inductance
Motor rotor resistance
Motor stator resistance
Motor stator leakage inductance
Motor cosine phi
Motor magnetising current
Tip!
Detailed information about the automatic determination of the motor parameters can be
found in the chapter "Motor interface" in the subchapter "Determining the motor
parameters". ( 138)
Possible status displays for this device command
Status (C00003)Meaning
4752642 Device command in process
4718592 Device command executed successfully
4718593 General fault
4758290 Motor identification cannot be started since the current controller test mode is active.
4758291 Motor identification cannot be started since the V/f test mode is active.
4758292 Motor identification cannot be started because pole position identification is active.
4758293 Motor identification has been aborted.
4758294 Motor identification has been aborted by fault.
4758332 Motor identification aborted due to inconsistent motor parameters.
• This error message is only available from software version V7.0 onwards.
This function extension is available from software version V5.0 onwards!
The device command C00002
the gain and the reset time of the current controller for a third-party motor.
Precondition:
inductance" (C00085
information before, or have been determined automatically via the device command "Determine
motor parameters".
The two motor parameters "stator resistance" (C00084) and "stator leakage
) either have been parameterised manually on the basis of the manufacturer
= "77: Calculate current controller parameters" is used to calculate
Note!
For a Lenze motor the calculation and the subsequent optimisation of the current
controller parameters is not
accepted from »Engineer« motor catalogue.
The device command is no
controller parameters!
• The calculation is carried out according to the following formulas:
required, as the correct current controller parameters are
identification procedure for determining the current
• After the device command has been executed successfully (see status in C00003
calculated values are set in C00075
optimisation of the current controller in the test mode.
• In the event of an error, codes C00075
and C00076. They serve as starting values for a subsequent
and C00076 are not altered.
Tip!
Detailed information on the optimisation of the current controller in the test mode can be
found in the chapter "Motor interface" in the subchapter for the respective motor control:
•Servo control (SC)Optimising the current controller
• Sensorless vector control (SLVC)Optimising the current controller
• V/f control (VFCplus) Optimising the current controller
The C00002 = "91: CAN on board: reset node" device command is used to reinitialise the CANopen
system bus interface of the controller ("CAN on board"), which is required, for instance, after the
data transfer rate, node address, or identifiers have been changed.
Tip!
For detailed information about the "CAN on board" CANopen system bus interface, please
see the "CAN" Communication Manual.
The C00002 = "92: CAN module: reset node" device command is used to reinitialise the CANopen
interface of a CANopen communication module in module slot MXI1 or MXI2, which is required, for
instance, after the data transfer rate, node address, or identifiers have been changed.
Tip!
Detailed information on the CANopen communication module (E94AYCCA) can be found in
the "CAN" Communication Manual.
The C00002 = "93: CAN on board: Pred.Connect.Set" device command is used to set the basic
identifiers for the CANopen system bus interface of the controller ("CAN on board") according to the
"Predefined Connection Set" (DS301V402).
Tip!
For detailed information about the "CAN on board" CANopen system bus interface, please
see the "CAN" Communication Manual.
The C00002 = "94: CAN module: pred.connect.set" device command is used to set the basic
identifiers for the CANopen system bus interface of a CANopen communication module in module
slot MXI1 or MXI2 according to the "Predefined Connection Set" (DS301V402).
Tip!
Detailed information on the CANopen communication module (E94AYCCA) can be found in
the "CAN" Communication Manual.
The C00002 = "95: CAN on board: identify node" device command is used to determine the nodes
connected to the CANopen system bus interface of the controller ("CAN on board").
• The result of the CAN bus scan is displayed in C00393
Tip!
For detailed information about the "CAN on board" CANopen system bus interface, please
see the "CAN" Communication Manual.
The C00002 = "96: CAN module: identify node" device command is used to determine the nodes
connected to the CANopen system bus interface of a CANopen communication module in module
slot MXI1 or MXI2.
• The result of the CAN bus scan is displayed in C13393 (for MXI1) or in C14393 (for MXI2).
Tip!
Detailed information on the CANopen communication module (E94AYCCA) can be found in
the "CAN" Communication Manual.
The C00002 = "101: Unbind/bind Ethernet module: MXI1" device command is used to reinitialise
the Ethernet interface of an Ethernet communication module in module slot MXI1, e. g. to accept a
newly set IP or gateway address without mains switching.
Tip!
Detailed information on the Ethernet communication module (E94AYCEN) can be found in
the "Ethernet" Communication Manual.
The C00002 = "102: Unbind/bind Ethernet module: MXI2" device command is used to reinitialise
the Ethernet interface of an Ethernet communication module in module slot MXI2, e. g. to accept a
newly set IP or gateway address without mains switching.
Tip!
Detailed information on the Ethernet communication module (E94AYCEN) can be found in
the "Ethernet" Communication Manual.
In addition to the start parameters, up to four further parameter sets can be stored in the memory
module for each application. Like this you can for instance define different controller settings for an
application, which are then simply activated via device command, if required.
The following device commands can be used to activate the parameter set 1 ... 4 for the active
application (if available on the memory module):
C00002
C00002
= "201: Activate parameter set 1"
= "202: Activate parameter set 2"
C00002
C00002
* In this example, application 1 is the active application
[4-20] Example: "Activate parameter set 1" function
= "203: Activate parameter set 3"
= "204: Activate parameter set 4"
• Only possible when the application has stopped and the controller is inhibited.
• All parameter changes of the previously active parameter set carried out since the last saving
will get lost!
• These device commands only affect the settings of the operating system, application, and
module parameters; the active application, or a configuration selected with the function block
editor remain unchanged.
In addition to the start parameters, up to four further parameter sets can be stored in the memory
module for each application. Like this you can for instance define different controller settings for an
application, which are then simply activated via device command, if required.
The following device commands are used to archive the current parameter settings of the controller
for the active application in the memory module as parameter set 1 ... 4:
C00002
C00002
= "301: Archive parameter set 1"
= "302: Archive parameter set 2"
C00002
C00002
* In this example, application 1 is the active application
[4-21] Example: "Archive parameter set 1" function
= "303: Archive parameter set 3"
= "304: Archive parameter set 4"
• Previously archived parameter settings will be overwritten with the current parameter settings!
This function extension is available from software version V3.0!
The C00002
module into the controller.
= "501: Load cam data" device command serves to reload cam data from the memory
Note!
If you transfer the parameter set or the application from »Engineer« to the controller,
the cam data are also transferred automatically to the controller.
• The new/altered cam data are accepted in the controller according to the online
change mode set.
• Thus, normally this device command does not need to be executed manually.
[4-22] "Load cam data" function
• Only possible when the application has stopped and the controller is inhibited.
• If the cam data are provided with an access protection, the user password has to be entered in
C02900
first.
Tip!
Detailed information on the online change mode and the access protection can be found in
the chapter "Basic drive functions", subchapter "Cam data management
Sequence
1. The cam data are completely loaded from the memory module into the main memory of the
controller.
2. The present cam data in the application unit are converted to the internal unit [increments] and
are reorganised.
3. The processed cam data are stored in a separate main memory that can be accessed by the cam
application.
This function extension is available from software version V3.0!
The C00002
memory of the controller to the internal format and makes them available to the application. This,
for instance, is necessary if one or more machine parameters affecting the internal scaling of cam
data have been changed.
• The status signal bNewDataAvailable of the basic drive function "Cam data management
(LS_CamInterface system block) is set to TRUE and the cam data are accepted automatically or
manually depending on the online change mode set. After successful data acceptance, the
status signal bNewDataAvailable is automatically reset to FALSE.
• The user password does not have to be entered in C02900
• While the function is executed, no online change and no change of the cam data via parameters
can be carried out.
• This function is executed in the background and can also be activated when the controller is
enabled and the application is running.
= "503: Calculate cam data" device command converts the cam data stored in the main
"
.
Tip!
Detailed information on the cam functionality can be found in the chapter "Basic drive
functions", subchapter "Cam data management
This function extension is available from software version V3.0!
The C00002
checksum of the cam data available in the main memory of the controller. This is required if the cam
data in the main memory of the controller have been changed via parameters. Afterwards the cam
data can be converted to the internal format using the "503: Calculate cam data" device command,
or they can be saved with mains failure protection in the memory module using the "502: Save cam
data" device command.
• The user password does not have to be entered in C02900
• This function is executed in the background and can also be activated when the controller is
enabled and the application is running.
= "504: Calculate cam data checksum" device command is used to recalculate the
.
Tip!
Detailed information on the cam functionality can be found in the chapter "Basic drive
functions", subchapter "Cam data management
The C00002 = "1040: Restore file system" device command is used to execute a low level formatting
of the file system in the memory module.
Note!
By means of this device command all folders and files in the file system of the memory
module and all pieces of internal information for the management of the file system are
irrevocably deleted!
This device command has no status display in C00003
unchanged showing the previous device command status.
, i.e. the display remains
Stop!
The low level formatting of the file system by the user is only intended for the
exceptional case when the standard formatting of the file system via the
C00002
damaged internal management information.
= "1030: Format file system" device command is no longer possible, e.g. due to
The state control of the drive is controlled internally via a state machine which can adopt the
following "device states":
, From all states
[4-24] Device state machine
"Warning active" or "Warning locked active" contradicts the definition of a device status. It is a message
which is intended to draw attention to a device status for which there is a reason for a warning.
"Warning active"/"Warning locked active" can occur simultaneously with other states.
Note!
The device states of the controller must not be confused with the function states of the
Basic drive functions
• In the device state "Operation" the Basic drive functions
the drive.
(status word 1) the current device state is shown in a bit coded manner via
bits 8 ... 11:
Bit 11Bit 10Bit 9Bit 8Meaning
0000"Initialisation active" state
0001"Device is ready to switch on" state
0010-
0011"Device is switched on" state
0100-
0101-
0110"Operation" state
0111"Trouble active" state
1000-
1001-
1010"Quick stop by trouble active" state
1011"Safe torque off active" state
Observe LED on the safety module!
1100"Fault active" state
1101-
1110-
1111-
xxxxDisplayed message "Warning active"
The displayed message can occur at the same time as the device
states "Device is ready to switch on", "Device is switched on" and
"Operation", if a monitoring component responds for which the error
response "Warning" has been parameterised.
or "Warning locked active"
• C02530
displays the active function state.
LED status displays
The control of the two LEDs "DRIVE READY" and "DRIVE ERROR" in the middle of the controller's front
panel depends on the device state. LED status displays for the device state
This device state becomes active if the controller receives the "Safe torque off" request by the safety
module.
• "Drive is torqueless" (0x00750003) is entered in the logbook.
• If no corresponding request by the safety module is available, a change to the subsequent state
"Device is ready to switch on" is effected.
Note!
The "Safe torque off active" status is also passed through after an error has been
acknowledged (see illustration [4-24]
).
4.3.3"Device is ready to switch on" state
LED DRIVE READYLED DRIVE ERRORDisplay in C00183
OFF"Device is ready to switch on"
This is the device state of the controller directly after the initialisation has been completed and
where no DC-bus voltage is applied yet.
• The bus systems are running and the terminals and encoders are evaluated.
• The monitoring functions are active.
• The controller can be parameterised and device commands can be executed to a limited extent.
• The functions of the user task can be used.
• Precondition: The application has started (status display in C02108
• The basic drive functions cannot be used yet.
Note!
The "Device is ready to switch on" status is not only activated after mains connection but
also after reset of "Trouble", "Fault", or "Safe torque off active".
• In order to change from the "Device is ready to switch on" to the "Device is switched
on" status when C00142
must be active.
• When C00142
changes to the "Device is switched on" status.
= "1: Enabled", the "Device is ready to switch on" status directly
).
= "0: inhibited", at least one of the controller inhibit sources