5.11.1Setting and optimising the current controller _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 105
0x2941 | 0x3141 - Current controller: Feedforward control
0x2942 | 0x3142 - Current controller: Parameter
0x2943 | 0x3143 - Motor: Current setpoint - filter time
0x2980 | 0x3180 - Position controller: Gain
0x2981 | 0x3181 - Position controller: Gain - adaptation
0x2982 | 0x3182 - Position controller: Output signal limitation
0x2983 | 0x3183 - Position: Select a new actual position
0x2984 | 0x3184 - Determine target position: Mode
0x29C0 | 0x31C0 - Field controller: Parameter
0x29E0 | 0x31E0 - Field weakening controller: Parameter
0x29E1 | 0x31E1 - field: Field set value limitation
0x29E2 | 0x31E2 - DC link circuit voltage: Filter time
0x29E3 | 0x31E3 - motor: Actual voltage - filter time
0x29E4 | 0x31E4 - Voltage reserve range
7.6Parameters for actuation of the position control _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 192
0x6062 | 0x6862 - Position demand value
0x6063 | 0x6863 - Position actual internal value
0x6064 | 0x6864 - Position actual value
0x6065 | 0x6865 - Following error window
0x6066 | 0x6866 - Following error time out
0x6067 | 0x6867 - Position window
0x6068 | 0x6868 - Position window time
0x60F4 | 0x68F4 - Following error actual value
0x60FA | 0x68FA - Control effort
0x60FC | 0x68FC - Position demand internal value
0x2D4E | 0x354E - Motor utilisation (I²xt): Motor overload warning threshold
0x2D4F | 0x354F - Motor utilisation (I²xt): Actual utilisation
0x2D50 | 0x3550 - motor utilisation (I²xt): Motor overload error
0x2D4C | 0x354C - Motor utilisation (I²xt): Parameter for the thermal model
0x2D4D | 0x354D - Motor utilisation (I²xt): User-definable characteristic
8.4.1Example of how to enter the characteristic for standard and servo motors _ _ _ _ _ _ _ 246
Error code 0x0000: No error
Error code 0x2320: Short circuit or earth leakage on motor side
Error code 0x2340: Short circuit on motor side
Error code 0x2351: Motor utilisation (I²xt) > [value] %
Error code 0x2380: Fault - utilisation of the power section (Ixt) too high
Error code 0x2381: Warning - Utilisation of the power section (Ixt) too high
Error code 0x2382: Fault - device utilisation (Ixt) too high
Error code 0x2383: Warning - device utilisation (Ixt) too high
Error code 0x2384: Ultimate motor current reached
Error code 0x2385: Output current > [value] A (maximum device current)
Error code 0x2386: Clamp is active
Error code 0x2387: Clamp responded too often
Error code 0x3210: DC link circuit - overvoltage [value] V
Error code 0x3220: DC link circuit - undervoltage [value] V
Error code 0x4210: Module temperature too high, [value]
Error code 0x4280: Internal fault - module temperature monitoring
Error code 0x4310: Motor temperature too high, [value]
Error code 0x4380: Motor temperature sensor
Error code 0x5112: 24-V supply
Error code 0x6010: Watchdog reset
Error code 0x6310: Incorrect parameter set download
Error code 0x6320: Parameter error in object [value]
Error code 0x7121: PLI - motor blocked
Error code 0x7303: Error in feedback system
Error code 0x7380: Hiperface communication error
Error code 0x7381: Hiperface: Invalid absolute value - motor speed too high
Error code 0x8180: ECAT DC - synchronisation required
Error code 0x8181: EtherCAT communication
Error code 0x8280: Sync Manager - address [value]
Error code 0x8281: Sync Manager - actual size [value]
Error code 0x8282: Sync Manager - settings [value]
Error code 0x8283: PDO Mapping: Object unknown (index [value])
Error code 0x8284: No PDO mapping object (index [value])
Error code 0x8285: Too many mapped objects (max. number = [value])
Error code 0x8286: PDO mapping - error
Error code 0x8700: Sync controller
Error code 0x8701: Time-out during synchronisation with EtherCAT Sync signal
Error code 0xFF00: Fatal internal error
Error code 0xFF01: Fatal internal communication error, cycle [value]
Error code 0xFF02: Brake
Error code 0xFF03: Fatal internal error - overflow task [value]
Error code 0xFF04: PLI - motor movement too large
Error code 0xFF05: STO inhibited
Error code 0xFF06: Max. speed reached
Error code 0xFF07: Impermissible during identification or in the test mode
Error code 0xFF08: Impossible during identification
Error code 0xFF09: Motor phase failure
Error code 0xFF0A: Motor phase failure - phase U
Error code 0xFF0B: Motor phase failure - phase V
Error code 0xFF0C: Motor phase failure - phase W
Error code 0xFF0D: No resolver connected --> command cannot be executed.
Error code 0xFF0E: Speed too low --> command cannot be executed.
Error code 0xFF0F: No resolver connected --> command cannot be executed.
Error code 0xFF10: Time-out
Error code 0xFF11: Numerical problem
Error code 0xFF12: Inverter error too big
Error code 0xFF13: Identification aborted
Error code 0xFF14: Not allowed in state 'operation enabled' or 'quick stop active'
Error code 0xFF15: No Hiperface absolute value encoder connected --> command cannot be executed
Error code 0xFF16: Connected Hiperface absolute value encoder is not supported
Error code 0xFF17: Connected Hiperface absolute value encoder is not supported --> command cannot be executed
Error code 0xFF18: Communication timeout in the manual control mode
Error code 0xFF19: Internal error during identification
The controller is a source of danger which may lead to death or severe injury of persons.
To protect yourself and others against these dangers, observe the safety instructions
before switching on the controller.
Please read the safety instructions in the mounting instructions and in the hardware manual for the i700 servo inverter. Both instructions are included in the scope of supply
of the drive controller.
Target group
This documentation addresses to all persons who want to parameterise, configure, and diagnose
the i700 servo inverter.
Validity
The information in this documentation are valid for the following standard devices:
Product seriesType designationFrom software version
i700 servo inverterE70ACM...01.00
Screenshots/application examples
All screenshots in this documentation are application examples. Depending on the firmware
version of the i700 servo inverter and the software version of the engineering tools installed (»PLC
Designer« or »EASY Starter«), the screenshots in this documentation may deviate from the screen
representation.
Document history
VersionDescription
1.503/2014TD05Extensions & corrections; Adaptation to software version V01.06
1.410/2013TD05Extensions & corrections;
Adaptation to software versions V01.04 and V01.05
1.303/2013TD05Extensions & corrections; Adaptation to software version V01.03
1.210/2012TD05Extensions & corrections; Adaptation to software version V01.02
1.107/2012TD05First edition
Tip!
Information and tools regarding the Lenze products can be found in the Internet:
Engineering ToolsSoftware solutions for simple engineering at all stages
»EASY Navigator« – Ensures easy operator guidance
• All practical Lenze engineering tools at a glance
• Tools can be selected quickly
• Clearly arranged, simplifying the engineering process from the start
»EASY Starter« – Simple tool for service technicians
• Especially developed for the commissioning and maintenance of Lenze
devices
• Graphical user interface with few buttons
• Simple online diagnostics, parameterisation and commissioning
• No risk of accidentally changing the application
• Ready applications can be loaded to the device
»PLC Designer« – for process programming
• Creation of individual programs
• Programming of Logic & Motion in accordance with IEC 61131-3 (IL, LAD,
FBD, ST, SFC, and CFC editor), is based on CoDeSys V3
• Certified function blocks according to PLCopen Part 1 + 2
• Graphical DIN 66025 editor (G-code) with DXF import
• Integrated visualisation for an easy process representation
• All important pieces of information at a glance during commissioning
Lenze ControllerThe Lenze Controller (abbreviated: "Controller") is the central component of the
Engineering PCUse the Engineering PC and the engineering tools installed to configure and
HIPERFACE®HIPERFACE® stands for High Performance Interface and is a universal interface between
Object"Container" for one or several parameters which can be used to parameterise or monitor
IndexFor the purpose of addressing, each object is provided with a unique index.
SubindexIf an object contains several parameters, the individual parameters are stored under
Touch probeA "Touch probe" is an event which can for instance be actuated in an edge-controlled
automation system which (by means of the runtime software) controls the Logic and
Motion functionalities.
The Lenze Controller communicates with the field devices via the fieldbus.
parameterise the system.
The Engineering PC communicates with the Lenze Controller via Ethernet.
EtherCAT® is a real-time capable Ethernet system with top performance.
EtherCAT® is a registered trademark and patented technology licensed by Beckhoff
Automation GmbH, Germany.
motor feedback system and inverter.
HIPERFACE® is a registered trademark of the SICK STEGMANN GmbH.
the i700 servo inverter.
In this documentation the index is represented as a hexadecimal value and is identified
by a prefixed "0x", e.g. "0x1000".
"subindexes".
In this documentation the colon is used as a separator between the index and the
subindex, e.g. "0x1018:1".
manner via a digital input to detect an actual value (that changes quickly) at the time of
activation and to process it further within the program afterwards.
All parameters which you can use to parameterise or monitor the i700 servo inverter are stored
within "objects".
• For the purpose of addressing, each object is provided with a unique index. In this
documentation the index is represented as a hexadecimal value and is identified by a prefixed
"0x", e.g. "0x1000".
• If an object contains several parameters, they are stored in "subindexes". In this documentation
the colon is used as a separator between the index and the subindex, e.g. "0x1018:1".
Note!
This documentation is valid for the i700 servo inverter in the single axis version (single
inverter) and also as double axis (double inverter).
For parameters referring to one axis, both indexes (for axis A and axis B) are listed in the
parameter description. For a single axis, only the first index is relevant in this case.
Each parameter description is structured according to the following pattern:
Example: Structure of the parameter descriptions in this documentation
Object index for axis A
Object index for axis B (only relevant for double axis)
Parameter or object name
If the object contains several parameters: Overview table with list of all subindexes
Table with detailed information about the corresponding parameter:
• Explanations & references (optional)
• Display options/possible settings, Lenze setting, attributes (for the meaning see the following table)
During the acceleration of the system, the controller and the controllers exchange configuration
data (e.g. bus cycle and PDO mapping). With regard to this, observe the following particular features
for the i700 servo inverter:
Parameter download
The i700 servo inverter itself does not
settings deviating from the i700 servo inverter "Lenze setting" (default) are maintained centrally in
the controller and are stored there permanently (persistently). During the initialisation at run-up,
only these deviations are transferred to the i700 servo inverter by the controller. Like this it is
ensured that the i700 servo inverter works with the parameter settings provided for it.
Firmware download (optional)
store parameter settings safe against mains failure. All
If required, the firmware of the i700 servo inverter can be stored together with the »PLC Designer«
project. During the run-up, the controller then checks whether the firmware version in the i700
servo inverter complies with the firmware version stored in the project for this device. If this is not
the case, the controller loads the firmware version stored in the project to the i700 servo inverter.
Like this, it can be ensured for "Device replacement" service work that the replacement device also
works with the same firmware version as the original device.
2.2Storage parameter set (par001.*) and total parameter set (par000.*)
For the storage of the i700 servo inverter parameters, two different parameter sets are provided,
which are stored in different parameter set files in the higher-level controller:
Storage parameter set (par001.i7psf)
• Only contains the parameters of the i700 servo inverter which are writable and identified with
the "P" attribute (persistent).
• Parameters can be read out from the i700 servo inverter and saved to the file. Conversely, the
parameters stored can be written to the i700 servo inverter again.
• Recommended for storage and archiving of the controllers settings.
Total parameter set (par000.i7psf)
• Contains all parameters of the i700 servo inverter, including the mere display parameters which
vary permanently during operation.
• The total parameter set can only be read from the i700 servo inverter.
• Use for purposes of service and diagnostics.
The structure of the parameter set file is described in the appendix.
2.2.1Saving a parameter set from the i700 to a file (export)
Reading out and storing the parameters from the i700 servo inverter is initiated and controlled from
the higher-level controller. For reading out a parameter set, the corresponding parameter values are
summarised in a parameter set file (par001.* or par000.*) in the i700 servo inverter and are then
transferred as a file to the controller via EtherCAT.
2.2.2Loading the stored parameter set to the i700 (import)
Loading a stored parameter set file to the i700 servo inverter is initiated and controlled from the
higher-level controller, just like in the case of the read-out. The storage parameter set file is
transferred to the i700 servo inverter as a file via EtherCAT, and the parameter settings are loaded
(imported).
For logical reasons, it is only possible to transfer "storage parameter set files" (par001.*) to the i700
servo inverter. Display parameters are updated under normal operating conditions and do not need
to be loaded.
Note!
In the case of Lenze controllers, the parameter set files are transferred as "files" via GCI
("Generic Communication Interface").
• GCI is a Lenze-specific application protocol which uses CoE ("CANopen over
EtherCAT").
• Other control manufacturers may also use FoE ("File Access over EtherCAT") for the
transfer.
2.2.3Monitoring of the parameter import (error report)
When the parameter import has been completed, the "parErr.i7psf" error report file is created. This
file is recreated automatically during every import.
On the basis of the error report it can be determined whether errors have occurred during the
parameter import:
• Parameters that have been transferred with errors are listed there together with their index,
subindex, and error code (SDO abort code).
• If no errors have occurred, this data area of the file is blank. However, the headers including the
checksum are available and valid nevertheless.
2.3Cyclic redundancy check (CRC) - parameter set comparison on the basis of the checksum
Each parameter set features an individual checksum (CRC32), which is composed of the settings of
all storable indexes (P-flag) of the parameter set. When a setting changes, there is also a change in
the checksum.
Cyclic redundancy check (CRC):
By comparison of the checksums of parameter sets it can be determined very quickly whether
parameter sets are identical or not. In particular, it is thus determined for the i700 servo inverter
whether the parameter set stored in the controller is identical to that in the i700 servo inverter and
therefore does not have to be loaded again.
0x2030 - Parameter set: Validity check (CRC)
Checksum for quick comparison of the storage parameter set (par001.i7psf)
• If the checksum shown here is identical to the checksum of the parameter set file stored in the Lenze Controller,
it is not necessary to write the parameter set file to the i700 servo inverter.
• If the checksums are different, however, there are deviations between the parameter set available in the Lenze
Controller and that in the i700 servo inverter.
• The checksum cannot be used for comparison of the total parameter set (par000.i7psf).
Display area (min. value | unit | max. value)Initialisation
"EtherCAT control technology" communication manual
Here you will find detailed information on the EtherCAT configuration and
commissioning of Lenze devices in the EtherCAT network.
Objects described in this chapter
ObjectNameData type
Axis AAxis B
0x2020EoE informationRECORD
0x2824
0x2830
0x2831
0x2833
0x3024Device control via PDO: ActivationUNSIGNED_8
0x3030Lenze control wordUNSIGNED_16
0x3031Lenze status wordUNSIGNED_16
0x3033Lenze statusword 2UNSIGNED_16
Tip!
The communication objects important for the integration of the controller with external
control are described in the appendix.
Communication objects
( 313)
3.1Acceleration of the system (initialisation)
Stop!
Before switching on the i700 servo inverter for the first time, check the entire wiring with
regard to completeness, short circuit, and earth fault.
To establish communication, the i700 servo inverter must be supplied with voltage. During the
acceleration of the system, the controller and the drive exchange configuration data.
The controller transmits the following configuration data to the i700 servo inverter:
•Bus cycle
• This is the basic cycle within which the EtherCAT bus is actuated. The bus cycle is given as a
multiple of 125 μs.
• The bus cycle equals the communication cycle within which the process data are exchanged
cyclically. New process data are only accepted and generated in the Servo-Inverter i700
maximally every 250 μs.
22
• Parameter set determined during commissioning.
• Among other things, it includes information about feedforward control values, the mains
voltage and the switching frequency as well as controller parameters adapted to the motor
module which are used for the motor control.
• Configuration of the process data transmitted cyclically via EtherCAT (PDO mapping)
If no data for the initialisation of the controller are transmitted, the i700 servo inverter
uses the "Lenze setting" for the parameters.
Power up/Power down
In the case of "Power up" and "Power down", no undefined states can occur that cause
damage to the device or motor movements which are not requested or not braked.
In the case of a voltage failure/dip, there is no immediate response by the i700 servo
inverter. The functionality is to be maintained for as long as possible.
24-V supply voltage monitoring
Persistent data storage
A complete, persistent storage of the drive configuration which remains the same even
though the controller is switched off from time to time is carried out in the higher-level
controller instead of in the i700 servo inverter. Hence, the controller needs to transmit
the configuration data again to the i700 servo inverter after a power up.
( 235)
However, in the case of a power down, the following device data are stored persistently
in the i700 servo inverter:
3.2Process data (cyclic PDO transfer) and PDO mapping
"EtherCAT control technology" communication manual
Here you will find some detailed information on the configuration of the process data
objects (PDO mapping) with the »PLC Designer«.
Cyclic process data are transferred cyclically between the controller (master) and the controllers
(slaves) as so-called Process Data Objects (PDOs).
• The i700 servo inverter supports the following bus cycle times of the EtherCAT:
0.125 ms*
0.250 ms
0.500 ms
1.000 ms
...(only integer multiple of 1 ms)
10.000 ms (max. cycle time)
* Note: With a bus cycle time of 0.125 ms, the process data is updated only every 0.250 ms, as
this is the fastest control cycle for the setpoint and actual value transfer.
• The processing time of a process date through the drive is t=max[bus cycle, 0.250 ms]. If the
entire chain from the control via the drive back to the control is considered, a process data needs
2 bus cycles in addition (for Lenze C3200) . Thus, the turnaround time for a PDO can be indicated
with 3 bus cycles.
• For the process data communication, the i700 servo inverter supports the mapping of max. 32
process data objects (PDOs) with a total max. size of 100 bytes per direction of transmission.
• A fixed PDO mapping preconfigured by Lenze is available for every CiA402 operating mode
supported by the i700 servo inverter. Every PDO mapping includes of several objects from the
Object directory
• For every axis, further fixed, preconfigured PDO mappings can be used for touch probe
functionality.
• In addition to the fixed, preconfigured PDO mappings, freely configurable PDO mappings are
available for every axis which can be used for individual PDO mapping. A maximum of 8 objects
from the Object directory
.
can be configured per direction of transmission.
24
• The configuration of the PDOs actually transmitted between the controller and the i700 servo
inverter is carried out via the »PLC Designer«.
• Experience shows that most i700 servo inverters are operated in one of the available CiA402
operating modes (csp, csv, cst or vl). We therefore recommend to use and activate the fixed
PDO mapping preconfigured by Lenze for the selected operating mode. In doing so all
parameters that usually need to be replaced during a cyclic PDO transfer can be accessed.
• If you wish to use touch probe functionality in addition, optionally and additionally activate
the fixed, preconfigured PDO mapping for touch probe functionality.
• Moreover, the PDO mappings that can be freely configured by the user can be optionally
activated. However, we recommend to use these freely configurable PDO mappings in special
cases only, if no standard PDO mapping is suitable for the case of application at hand. Special
thought should be given to the aspect of traceability in case of service.
3.2.1Synchronisation with "Distributed clocks" (DC)
The "Distributed clocks" (DC) function enables an exact time adjustment for applications where
several auxiliary axes carry out a coordinated movement at the same time. The data is accepted
synchronously with the PLC program. In the case of the DC synchronisation, all slaves are
synchronised with a reference clock, called the "DC master".
"EtherCAT control technology" communication manual
Here you will find some detailed information about DC synchronisation.
In addition to the cyclic process data transfer, parameter data can be transferred as so-called SDOs
(Service Data Objects) in a non-cyclic manner within an individual datagram between the controller
(master) and the controllers (slaves).
• SDO communication is implemented according to the EtherCAT-CoE protocol, using a mailbox.
• SDO communication enables read or write access to all indices contained in the object directory
of the i700 servo inverter.
• The turnaround time for an SDO (request by the control, transport via the bus, processing in the
drive, transport of the response back to the control) is between 1ms and 100ms plus 2*bus
cycle time (typically 10 ms).
3.3.1Object directory
The object directory contains the specific indices for all axes. The object directory is structured
according to specifications of the EtherCAT Technology Group (ETG):
0x0606 0000Access has failed because of hardware errors.
0x0607 0010Wrong data type or parameter length.
0x0607 0012Wrong data type (parameter length is too large).
0x0607 0013Wrong data type (parameter length is too small).
0x0609 0011Subindex does not exist.
0x0609 0030The value range for parameters is too large (only for write access).
0x0609 0031The parameter value is too high.
0x0609 0032The parameter value is too low.
0x0800 0000General error
0x0800 0020Data cannot be transferred or saved to the application.
0x0800 0021Data cannot be transferred or saved to the application because of local control.
0x0800 0022Data cannot be transferred/saved to the application because of current device state.
3.3.3ESI: EtherCAT Slave Information file (device description)
The EtherCAT Slave Information file (EtherCAT Device Description file) contains all information
about the device (operating modes, parameters, …).
• The EtherCAT Slave Information file is integrated by the EtherCAT network configuration tool in
order to be able to configure and commission the devices.
• Part of the information contained in the EtherCAT Slave Information file can be uploaded online
by the EtherCAT master by accessing the EtherCAT EEPROM of the device. The description of the
object directory can also be identified online.
Bit 0 Flying restart: CompletedVia this bit, the control reports the acceptance of the
Bit 1 Flying restart: Blocked"1" ≡ Block flying restart process
Bit 2 Reserved
Bit 3 Reserved
Bit 4 Speed controller: Load I component"1" ≡ Set starting value of the torque
Bit 5 Position: Traverse to new actual
Bit 6 Activate DC-injection braking or
Bits 7-15 Reserved
position
short-circuit braking
speed found to the "Flying restart" function. The flying
restart process is now completed.
• In case of servo control, this corresponds to the I
component of the speed controller, in case of V/f
operation to the modulation of the slip
compensation.
• As long as this bit is set to "1", the I component and
the slip compensation are set to the starting value set
in 0x2902
"1" ≡ Set/relatively shift actual position
• Axis A: Set the actual position (0x6064
consideration of the set resolution (0x608F
value set in 0x2983
value set in 0x2983
• Axis B: Set the actual position (0x6864
consideration of the set resolution (0x688F
value set in 0x3183
value set in 0x3183
"1" ≡ Trigger DC-injection braking for asynchronous
motor or short-circuit braking for synchronous motor
(or 0x3102 for axis B).
) under
) to the
(0x2984 = 0), or shift it by the
(0x2984 = 1).
) under
) to the
(0x3184 = 0), or shift it by the
(0x3184 = 1).
In case of servo control for asynchronous motor (ASM):
• Bit is set if the difference between setpoint and actual
• Bit is reset if the difference has increased to 15 % of
In case of V/f operation:
• Bit is set if the rotor time constant has been passed
Motor phase failure detection is active
expired. The remaining delay time is displayed in 0x2840
(or 0x3040
is active
or 0x3146:1 for axis B)
or 0x3146:2 for axis B)
flux is smaller than 10 % of setpoint flux.
setpoint flux.
seven times, calculated from the time the controller
has been enabled and no restart on the fly has been
active and the total motor current has reached 20 %
of the rated motor current for the first time.
Otherwise 0.