The purpose of this programming guide is to describe the
programming of the VLT® Integrated Servo Drive ISD® 510
System.
This programming guide contains information about:
Software installation
•
Programming
•
Operation
•
Applications
•
Troubleshooting
•
This programming guide is intended for use by qualied
personnel. Read the document in full in order to use the
servo system safely and professionally, and pay particular
attention to the safety instructions and general warnings.
This programming guide is an integral part of the ISD 510
servo system so keep it available with the servo system at
all times.
Compliance with the information in this document is a
prerequisite for:
Trouble-free operation
•
Recognition of product liability claims
•
Therefore, read this document before working with the
servo system.
Additional Resources
1.2
Available manuals for the VLT® Integrated Servo Drive ISD
510 System:
Software
1.4
The software for the ISD 510 servo system comprises:
The rmware of the VLT® Integrated Servo Drive
•
ISD® 510 that is already installed on the device.
rmware of the VLT® Servo Access Box that is
The
•
already installed on the device.
A package of PLC libraries for Automation
•
Studio™ for operating the ISD 510 devices (see
chapter 6.4.1 Programming with Automation
Studio™ for further information).
A PLC library for TwinCAT® 2 for operating the
•
ISD 510 devices (see chapter 6.3.1 Programming
®
with TwinCAT
ISD Toolbox: A Danfoss PC-based software tool for
•
commissioning and debugging the devices.
for further information).
1.4.1 Software Version
This programming guide can be used for the following
software versions onwards:
ISD 510 Servo Drive: Version 1.4.0
•
Servo Access Box (SAB): Version 1.2.0
•
ISD Toolbox: Version 2.0
•
PLC libraries (Powerlink / EtherCAT): Version 1.0
•
The software version number can be read from object
0x4000 (see chapter 7.22.4 Parameters 15-40, 15-41, and15-43: Version log (0x4000)).
®
1.4.2 Firmware Updates
11
DocumentContents
VLT® Integrated Servo Drive
ISD® 510 System Operating
Instructions
VLT® Integrated Servo Drive
ISD® 510 System Design
Guide
VLT® Integrated Servo Drive
ISD® 510 System
Programming Guide
Table 1.1 Available Manuals for the ISD 510 Servo System
Technical literature for Danfoss drives is also available
online at drives.danfoss.com/knowledge-center/technical-documentation/.
Copyright
1.3
VLT®, ISD®, and SAB® are Danfoss registered trademarks.
Information about the installation,
commissioning, and operation of
the ISD 510 servo system.
Information about the set-up of
the ISD 510 servo system and
detailed technical data.
Information about the
programming of the ISD 510 servo
system.
Firmware updates may be available. When rmware
updates are available, they can be downloaded from the
danfoss.com website. Use the ISD Toolbox software to
install the rmware in the servo drives.
Approvals and Certications
1.5
The ISD 510 servo system fullls the standards listed in
Table 1.2.
IEC/EN 61800-3Adjustable speed electrical power drive
systems.
Part 3: EMC requirements and specic test
methods.
IEC/EN 61800-5-1 Adjustable speed electrical power drive
systems.
Part 5-1: Safety requirements – Electrical,
thermal and energy.
Introduction
VLT® Integrated Servo Drive ISD® 510 System
11
IEC/EN 61800-5-2 Adjustable speed electrical power drive
systems.
Part 5-2: Safety requirements – Functional.
IEC/EN 61508Functional safety of electrical/electronical/
programmable electronic safety-related
systems.
EN ISO 13849-1Safety of machinery – Safety-related parts of
control systems.
Part 1: General principles for design.
EN ISO 13849-2Safety of machinery – Safety-related parts of
control systems.
Part 2: Validation.
IEC/EN 60204-1Safety of machinery – Electrical equipment of
machines.
Part 1: General requirements.
IEC/EN 62061Safety of machinery – Functional safety of
safety-related electrical, electronic, and
programmable electronic control systems.
IEC/EN 61326-3-1 Electrical equipment for measurement,
control, and laboratory use – EMC
requirements.
Part 3-1: Immunity requirements for safetyrelated systems and for equipment intended
to perform safety-related functions (functional
safety) – General industrial applications.
UL508CUL Standard for Safety for Power Conversion
Equipment.
Terminology
1.6
ISDIntegrated servo drive
ISD 510 Servo
Drive
VLT® Servo Access
Box (SAB)
PLCExternal device for controlling the ISD 510
Loop cableHybrid cable for connecting drives in daisy-
Feed-in cableHybrid cable for connection from the SAB to
Table 1.3 Terminology
Decentral servo drive
Unit that generates the DC-link voltage and
passes the U
signals to the ISD 510 servo drives via a
hybrid cable.
servo system.
chain format.
the 1st servo drive.
, Real-Time Ethernet, and STO
AUX
An explanation of all terminology and abbreviations can be
found in chapter 10.1 Glossary.
1.7 Safety
The following symbols are used in this guide:
WARNING
Indicates a potentially hazardous situation that could
result in death or serious injury.
2006/42/ECMachinery Directive
CE
2014/30/EUEMC Directive
2014/35/EULow Voltage Directive
RoHS
(2002/95/EC)
EtherCAT
Ethernet
POWERLINK
PLCopen
®
®
Table 1.2 Approvals and Certications
Restriction of hazardous substances.
Ethernet for Control Automation Technology.
Ethernet-based eldbus system.
Ethernet-based eldbus system:
®
Technical specication.
Function blocks for motion control (formerly
Part 1 and Part 2) Version 2.0 March 17, 2011.
CAUTION
Indicates a potentially hazardous situation that could
result in minor or moderate injury. It can also be used to
alert against unsafe practices.
NOTICE
Indicates important information, including situations that
can result in damage to equipment or property.
The following safety instructions and precautions relate to
the ISD 510 servo system.
Read the safety instructions carefully before starting to
work in any way with the ISD 510 servo system or its
components.
Pay particular attention to the safety instructions in the
relevant sections of this manual.
WARNING
HAZARDOUS SITUATION
If the servo drive, SAB, or the bus lines are incorrectly
connected, there is a risk of death, serious injury, or
damage to the unit.
Always comply with the instructions in this manual and
national and local safety regulations.
The ground leakage current is >3.5 mA. Improper
grounding of the ISD 510 servo system components may
result in death or serious injury.
For reasons of operator safety, ground the
•
components of the ISD 510 servo system
correctly in accordance with national or local
electrical regulations and the information in this
manual.
WARNING
HIGH VOLTAGE
The ISD 510 servo system contains components that
operate at high voltage when connected to the electrical
supply network.
A hazardous voltage is present on the servo drives and
the SAB whenever they are connected to the mains
network.
There are no indicators on the servo drive or SAB that
indicate the presence of mains supply.
Incorrect installation, commissioning, or maintenance can
lead to death or serious injury.
Installation, commissioning, and maintenance
•
may only be performed by qualied personnel.
WARNING
UNINTENDED START
The ISD 510 servo system contains servo drives and the
SAB that are connected to the electrical supply network
and can start running at any time. This may be caused
by a eldbus command, a reference signal, or clearing a
fault condition. Servo drives and all connected devices
must be in good operating condition. A decient
operating condition may lead to death, serious injury,
damage to equipment, or other material damage when
the unit is connected to the electrical supply network.
Take suitable measures to prevent unintended
•
starts.
WARNING
DISCHARGE TIME
The servo drives and the SAB contain DC-link capacitors
that remain charged for some time after the mains
supply is switched o at the SAB. Failure to wait the
specied time after power has been removed before
performing service or repair work could result in death
or serious injury.
To avoid electrical shock, fully disconnect the
•
SAB from the mains and wait for at least the
time listed in Table 1.4 for the capacitors to fully
discharge before carrying out any maintenance
or repair work on the ISD 510 servo system or
its components.
NumberMinimum waiting time (minutes)
0–64 servo drives10
Table 1.4 Discharge Time
NOTICE
Never connect or disconnect the hybrid cable to or from
the servo drive when the ISD 510 servo system is
connected to mains or auxiliary supply, or when voltage
is still present. Doing so damages the electronic circuitry.
Ensure that the mains supply is disconnected and the
required discharge time for the DC-link capacitors has
elapsed before disconnecting or connecting the hybrid
cables or disconnecting cables from the SAB.
NOTICE
Full safety warnings and instructions are detailed in the
VLT® Integrated Servo Drive ISD 510 System Operating
Instructions.
11
WARNING
UNINTENDED MOVEMENT
Unintended movement may occur when parameter
changes are carried out immediately, which may result in
death, serious injury, or damage to equipment.
When changing parameters, take suitable
•
measures to ensure that unintended movement
cannot pose any danger.
The CiA CANopen standard DS402 Drives and MotionControl Device Prole is supported by both Ethernet
POWERLINK® and EtherCAT®.
2.2 Firmware Update
The products are delivered with the most recent
version. See chapter 1.4.2 Firmware Updates for information
on upgrading.
The servo drive rmware can be updated via the eldbus.
The download of new rmware is only allowed in the
unpowered drive state Switch on disabled. If the servo drive
is in another state, the transfer is refused. While the update
is in progress, the servo drive signals the warning Firmwareupdate in progress. After nishing, the servo drive signals
the warning Firmware update occurred. Power cycle the
servo drive to resume normal operation.
If the servo drive state machine is switched to another
state than Switch on disabled after the rmware update has
begun (that is, during le transfer or after ashing without
a power-cycle), the servo drive switches to state Fault. This
error indicates that a power-cycle is needed before the
servo drive can resume operation. If, for example, a power
failure occurs during upgrading, the servo drive remains in
a state that allows the update process to resume. The
currently installed version can be read from object 0x4000
(see chapter 7.22.4 Parameters 15-40, 15-41, and 15-43:Version log (0x4000)).
rmware
NOTICE
To change the supported eldbus, update to the
corresponding rmware. After changing the eldbus, the
original product code is no longer valid.
The servo drive uses the state machine described in the CiA DS402 standard. The state machine is operated either locally via
the LCP or remotely via the network.
The state machine is operated by local signals and by the Controlword sent over the eldbus. The state of the state machine
is reported by the Statusword produced by the servo drive.
A single state represents a special internal or external behavior. The state of the state machine also determines which
commands are accepted.
Illustration 2.1 shows the state machine of the servo drive with regard to control of the power electronics as a result of
commands and internal servo drive faults.
22
Illustration 2.1 DS402 State Machine
The states support the functions shown in Table 2.1. The Start state is a pseudo state indicating the start when the state
machine is activated during the start-up sequence of the device drives application software.
Function
Brake applied, if presentYesYesYesYesNoNoNoYes
Low-level power appliedYesYesYesYesYesYesYesYes
High-level power appliedYes/noYes/noYes/noYesYesYesYesYes/no
Drive function enabledNoNoNoNoYesYesYesNo
Conguration allowedYesYesYesYesYesYesYesYes
Table 2.1 DS402 States and Supported Functions
Quick stop active state is implemented, which is optional according to the standard. When entering this state, the behavior
of the servo drive is according to the option code
Option Code (0x605A)).
dened in object 0x605A (see chapter 7.20.6 Parameter 50-46: Quick Stop
Fault
reaction
active
Fault
Servo Drive Operation
VLT® Integrated Servo Drive ISD® 510 System
The transition from state Quick stop active to state Operation enabled (Transition 16 in Illustration 2.1) is not available, as
recommended by the standard.
22
The servo drive supports the transitions and actions as given in Table 2.2. The events initiate the transition. The transition is
terminated after the action has been performed.
High-level power applied means that UDC is applied at the input of the servo drive. Yes/No means that it is allowed but not
necessary.
Conguration allowed means that the following conguration is allowed:
Changes to the option code objects (see chapter 7.20 Option Code Objects).
•
Changes to the mode of operation object (see chapter 7.5.1 Parameter 52-00: Modes of Operation (0x6060)).
•
Transition EventAction
0Automatic transition after power-on or reset
application.
1Automatic transition.Communication is activated.
2Shutdown command received from control device.–
3Switch on command received from control device.High-level power is switched on, if possible.
4Enable operation command received from control
device.
5Disable operation command received from control
device.
6Shutdown command received from control device.The congured shutdown reaction function is executed (see
7Quick stop or disable voltage command received
from control device.
8Shutdown command received from control device.The servo drive function is disabled and high-level power is switched
9Disable voltage command received from control
device.
10Disable voltage or quick stop command received
from control device.
11Quick stop command received from control device.The quick stop function is started.
12Automatic transition when:
13Fault signal.The congured fault reaction function is executed (see
14Automatic transition.The servo drive function is disabled and high-level power is switched
15Fault reset command received from control device.If no fault exists on the servo drive, the fault condition is reset. After
16Not supported.–
Servo drive self-test and self-initialization are performed.
The servo drive function is enabled and all internal setpoints are
cleared.
If the servo drive is rotating when the command to carry out transition
4 is received, the behavior is dened by option code
chapter 7.20.4 Parameter 50-44: Enable in Positioning Option Code
(0x2052).
The congured disable operation reaction function is executed (see
If a state transition is requested, the related actions are processed completely before transitioning to the new state. For
example, in state Operation enabled, when the disable operation command is received, the servo drive remains in state
Operation enabled until the disable operation function (see chapter 7.20.9 Parameter 50-49: Disable Operation Option Code
(0x605C)) is completed.
Drive function is disabled means that no energy is supplied to the motor. Target or setpoint values (for example, torque,
velocity, position) are not processed. Drive function is enabled means that energy is supplied to the motor. Target or setpoint
values are processed.
If a fault is detected in the servo drive, a transition to state Fault reaction active takes place. In this state, the state machine
executes a special fault reaction (see chapter 7.20.1 Parameter 50-41: Fault Reaction Option Code (0x605E)). After the execution
of this fault reaction, the servo drive automatically switches to state Fault. This state can only be left by using the fault reset
command, but only if the fault is no longer active.
22
If a fatal error occurs, the servo drive is no longer able to control the motor, so the servo drive must be switched
immediately. If a fatal error has occurred, the servo is trip-locked and cannot be reset via eldbus.
The behavior of drive disabling, quick stop, halt, and fault reaction functions are congurable via the objects dened in
chapter 7.20 Option Code Objects.
If a brake is present, the high-level power is switched o after a delay time in order to apply the brake.
2.3.2 Factor Group
Use the factor group to set the user-dened units required
in the application.
The user-dened units are:
Position units
•
Velocity units
•
Acceleration units
•
These units are used for all objects that support userdened units (for example, position actual value, prole
velocity, and prole acceleration).
Changing the objects in the factor group has an
immediate eect on all objects that support user-dened
units. Their numerical values stay the same, but they are
interpreted dierently (according to the new scaling factors
of the factor group). All numerical values are interpreted
using the current settings of the factor group.
Position units:
The position value is calculated as:
Position value means all objects containing values in user-dened position units.
Position internal value is given in encoder increments.
Velocity units:
The velocity value is calculated as:
Velocity internal value is the position internal value(s),
resulting in the following formula:
o
NOTICE
If the factor group is changed, then the default values
are interpreted dierently.
The formulae in this chapter show the calculation of the
units. Objects, whose values are not dependent on the
factor group, have xed units specied with the objects.
The objects of the factor group can be found in
chapter 7.4 Factor Group Objects.
Velocity value means all objects containing values in user-dened velocity units.
Acceleration value =x acceleration factor
velocity value
s
Internal Encoder Position
(-)
TRC_ROTOR_POS_RAW
[increments]
Physical (Absolute) Position
(-)
TRC_ROTOR_POS
[increments]
Drive Position
(0x2022)
[user-dened position unit]
TRC_POS_ACT_REAL
[revolutions]
Position Actual Value
(0x6064)
TRC_POS_ACT_ABS
[user-dened position unit]
Logical CAM Position
(0x2020)
TRC_CAM_POS
[revolutions]
Only up to date if CAM
mode is active;
otherwise, the last value
remains
Position Actual Internal
Value
(0x6063)
[increments]
Encoder oset
(set during callibration)
Position oset
(set during homing)
Factor
group
Factor group +
Position range limit
(0x6078)
CAM osets
130BF158.10
Position
Hardware
limit switch
Velocity
Quick-stop
deceleration
130BF159.10
Servo Drive Operation
VLT® Integrated Servo Drive ISD® 510 System
Acceleration units:
The acceleration value is calculated as:
2.3.4 Position Limits
2.3.4.1 Hardware Limit Switch
22
One method to limit the positions of the servo drive is to
use limit switches (left/negative or right/positive), which
are also referred to as hardware limit switches. The limit
Acceleration value means all objects containing values in
user-dened acceleration units. The acceleration unit is also
used for deceleration.
2.3.3 Positions and Osets
Inside the servo drive, there are several logical positions.
Illustration 2.2 shows the relationships between them.
switches must be congured using object 0x200F (see
chapter 7.21.3 Parameter: Dual Analog User Inputs Conguration (0x200F)). When the servo drive reaches the Left
(Right) Limit switch, it ramps down to standstill using the
value set in object 0x6085 (see chapter 7.5.9 Parameter50-13: Quick Stop Deceleration (0x6085)). It is possible to
command the servo drive out of the limit switch in the
opposite direction. The states of the limit switches are
indicated in object 0x2006 (see chapter 7.22.12 Parameter50-08: Motion and Input Status (0x2006)).
The servo drive remains in state Operation enabled. If a
motion command is issued that would direct the servo
drive further in the wrong direction, the command is
rejected by setting the command error bit in the
Statusword. The monitoring of the limit switch is edgetriggered because the signal does not need to remain high
for the duration of the servo drive ramp-down time.
The hardware limit switch is monitored in all modes of
operation.
Illustration 2.2 Servo Drive Logical Positions
The object index is given in round brackets. The positions
oset is the oset that is calculated during a
without index numbers are not available in the object
dictionary but are used internally in the rmware of the
servo drive. The units are given in square brackets.
The Position
homing procedure (see chapter 2.4.4 Homing Mode). For
applications where the zero position only needs to be set
once during the lifetime of the servo drive, this oset can
be saved to non-volatile memory (see
chapter 7.7.8 Parameters 51-02, 52-04, and 52-49: Application
Settings (0x2016)).
The valid positions of the servo drive can also be limited
using software position limits (object 0x607D: Software
position limit). This object indicates the congured
maximum and minimum software position limits and is
used to monitor the position limits in all available modes
of operation.
Supervision of software position limits requires a dened
home position (the Is homed bit in the Statusword must be
set).
The behavior of the servo drive in a position-controlled
mode of operation diers to other modes. In a positioncontrolled mode of operation, the drive does not pass over
the software position limit. The target position is limited to
Position
Software
position limit
Velocity
Quick-stop
deceleration
Prole
deceleration
130BF160.10
Position
controlled
Velocity
controlled
Target
reached
Position
Command
Error
Positive software
limit active
Done
PLC
Fieldbus
Busy
Error
Positioning
command
Time
Software
position limit
Target
position
130BF161.10
Target
reached
Position
Command
Error
Positive software
limit active
Done
PLC
Fieldbus
Busy
Error
Positioning
command
Positioning only to
Software position limit
Time
Target
position
Software
position limit
130BF162.10
Target
reached
Position
Command
Error
Positive software
limit active
Done
PLC
Fieldbus
Busy
Error
Positioning
command
Software
position limit
Target
position
Time
130BF163.10
Servo Drive OperationProgramming Guide
the software position limit. In all other modes of operation,
the servo drive immediately ramps down using the Quick
stop deceleration value (see chapter 7.5.9 Parameter 50-13:
Quick Stop Deceleration (0x6085)) when the software
position limit is passed. This means that the servo drive
always stops after the Software position limit.
Illustration 2.4 Software Position Limit
Illustration 2.5 to Illustration 2.9 show the behavior of the
servo drive around the position limits.
22
Illustration 2.6 Position Command: Target Position is Behind
the Software Position Limit
Illustration 2.5 Normal Positioning: Target Position is in the
Valid Position Range
Illustration 2.7 Servo Drive is Outside the Valid Position Limit
automatically lifts the brake. The servo drive reports the
new state after the brake is lifted.
When the servo drive leaves state Operation enabled, it
automatically releases the brake so that the axis cannot
sag down. The servo drive reports the new state after the
brake is unreleased.
The brake state can be overwritten using the digital output
object (see chapter 7.21.4 Parameter 16-66: Digital Outputs(0x60FE)). This is only allowed in unpowered state. The
valid commands and the reactions are shown in
Illustration 2.10.
WARNING
UNINTENDED MOTION
Releasing the brake in an unpowered state may result in
unintended motion leading to death, serious injury,
damage to equipment, or other material damage.
Do not release the brake in an unpowered state.
When the servo drive enters state Operation enabled, it
Illustration 2.8 Servo Drive is Outside the Valid Position Limit
and the Target Position is in the Wrong Direction
•
Illustration 2.10 Valid Brake Commands and Reactions
It is not possible to have an energized motor with a closed
brake. For further information about the current state, see
chapter 7.22.8 Parameter 50-09: STO Voltage and Brake Status
(0x2007).
2.3.6 Control Loops
Servo motor control takes place using 3 cascaded control
loops (position controller, speed controller, and current
controller) with trajectory generators for position and
velocity. The control loops run synchronously with the
eldbus cycles. The cycle times shown in Table 2.3 are
possible with Ethernet POWERLINK® and EtherCAT®:
Fieldbus cycle
[µs]
Illustration 2.9 Servo Drive is Outside the Valid Position Limit.
The Target Position is Still Not in a Valid Area, but is Nearer to
Application torque limit (0x2053)
Max torque (0x6072)
Max motor speed (0x6080)
Feed forward torque
Feed forward velocity
Position demand
Internal value (0x60FC)
Controlword (0x6040)
Position controller parameters (0x2013)
Speed controller parameters (0x2012)
Position controller parameters 2 (0x2015)
Speed controller parameters 2 (0x2014)
+
+
+
+
–––
+
P D
P D
Notch
Inertia
M
S
130BF167.10
I
Servo Drive OperationProgramming Guide
Fieldbus cycle
[µs]
1000250250125
Table 2.3 Ethernet POWERLINK® and EtherCAT® Cycle Times
Position control
cycle
[µs]
Speed control
cycle
[µs]
Current control
cycle
[µs]
Linear blending occurs from the parameter of the currently
active set to the new one. The blending time is dened in
object 0x201B (see chapter 7.6.2 Parameter 51-01: ControlParameter Blending Time (0x201B)).
No blending takes place when writing to a value of the
currently active control parameter set. The new value is
The used cycle times can be read using object 0x201D (see
used immediately, which could cause a jerk on the shaft.
chapter 7.6.1 Parameter 51-07 to 51-09: Used Task Cycle
Times (0x201D)). The values are given in microseconds.
Blending is used when updating a whole set of parameters
at the same time (for example, when activating CAM mode,
There are 2 control parameter sets in the servo drive,
which uses its own sets of control parameters).
however only 1 of them can be active at any time. Use bit
15 (cs) in the Controlword to switch from 1 set to the other.
2.3.6.1 Position Controller
The controller uses PD control. The D constant is the derivative time constant. The controller provides 2 sets of control
parameters that can be switched during operation (see chapter 7.7.8 Parameters 51-02, 52-04, and 52-49: Application Settings(0x2016) and chapter 7.6.4.2 Parameters 51-26 and 51-27: Position Controller Parameters 2 (0x2015)).
Both sets are available as read-write objects in the object dictionary. Use a manufacturer-specic bit in the Controlword to
switch between the 2 sets of parameters.
Application torque limit (0x2053)
Max torque (0x6072)
Max motor speed (0x6080)
Feed forward torque
Feed forward velocity
Controlword (0x6040)
Position controller parameters (0x2013)
Speed controller parameters (0x2012)
Position controller parameters 2 (0x2015)
Speed controller parameters 2 (0x2014)
++
+
––
P D
Notch
Inertia
M
S
130BF168.10
I
Servo Drive Operation
2.3.6.2 Speed Controller
VLT® Integrated Servo Drive ISD® 510 System
22
that can be parameterized (center frequency/bandwidth) to suppress resonance. The controller provides 2 sets of control
parameters (see chapter 7.6.5.1 Parameters 51-10 to 51-15: Speed Controller Parameters (0x2012) and chapter 7.6.5.2 Parameters51-20 to 51-25: Speed Controller Parameters 2 (0x2014)) that can be switched spontaneously.
Both sets are available as read-write objects in the object dictionary. Use a manufacturer-specic bit in the Controlword to
switch between the 2 sets of parameters.
The controller uses PID control. The D constant is the derivative time constant. The speed controller has a Notch-Filter (IIR)
Illustration 2.12 Speed Control Loop
2.3.6.3 Current Controller
The current controller runs synchronous to the eldbus cycle time. It cannot be parameterized.
Operating Modes
2.4
The servo drive implements several modes of operation. The behavior of the servo drive depends on the activated mode of
operation. It is possible to switch between the modes while the servo drive is enabled. The supported modes of operation
are according to CANopen® CiA DS402 and there are also ISD-specic modes of operation. All supported modes of
operation are available for EtherCAT® and Ethernet POWERLINK®.
2.4.1 Prole Position Mode
In Prole position mode, the servo drive is operated under position control and executes absolute and relative movements.
Parameters such as velocity, acceleration, and deceleration can be parameterized. The servo drive provides a buer to queue
a following move while another move is already executing.
This functionality can be commanded using the function blocks MC_MoveAbsolute_ISD51x (see chapter 6.5.5.4 MC_MoveAb-solute_ISD51x) and MC_MoveRelative_ISD51x (see chapter 6.5.5.5 MC_MoveRelative_ISD51x). This functionality can also be
used via the LCP (see section Position mode in chapter 4.3.5.1 Servo Drive).
When switching to Prole position mode from Prole velocity mode, CAM mode, Gear mode, or Prole torque mode, the servo
drive continues rotating with the current velocity. As soon as there is a new setpoint (handed over using the handshaking
between Controlword and Statusword), the new setpoint is processed with the corresponding parameters.
Max torque (0x6072)
Application torque limit (0x2053)
Torque limit
Position demand
internal value
(0x60FC)
Feed forward
velocity
Feed forward
torque
Max deceleration (0x60C6)
quick-stop deceleration
Target position
Velocity limit
or End velocity
130BF169.10
Servo Drive OperationProgramming Guide
When switching from a torque or velocity controlled mode to Prole position mode, the last target position is set to the
position actual value. This is relevant when starting a relative movement from the last target position after switching to this
mode, because no last target position from the previous mode is available. If the previous mode ended with a velocity
unequal to 0, the last target position is the position actual value at the time of the mode switch.
If the trajectory is completed (target position is reached) and the end velocity (see chapter 7.10.2 Parameter 52-16: EndVelocity (0x6082)) is unequal to 0, the servo drive continues rotating at the specied end velocity until a further trajectory is
set.
22
Illustration 2.13 Prole Position Mode Control Function
Target position activation
The activation of a setpoint is controlled by the timing of:
The new setpoint bit and the change set immediately bit in the Controlword.
•
The setpoint acknowledge bit in the Statusword.
•
If the Change set immediately bit of the Controlword is set to 1, a potentially ongoing motion is interrupted and the new
setpoint is used immediately. If the Change set immediately bit of the Controlword is set to 0, the ongoing positioning
command is nishedrst and the new setpoint is executed afterwards.
After a setpoint is applied to the servo drive, the control device signals that the setpoint is valid by a rising edge of the newsetpoint bit in the Controlword. The servo drive sets the setpoint acknowledge bit in the Statusword to 1. Afterwards, the
servo drive with the setpoint acknowledge bit set to 0 signals its ability to accept new setpoints. An example is shown in
Illustration 2.14.
Illustration 2.14 Handshaking Procedure for Setpoint
Activation
The servo drive supports 2 setpoints: a setpoint that is currently being processed, and a buered setpoint. If a setpoint is
still in progress (has not been reached) and a new setpoint is activated by the new setpoint bit in the Controlword, 2
methods of handling are supported. The new setpoint is activated immediately if the Change set immediately bit of the
Controlword is set to 1. If the Change set immediately bit of Controlword is set to 0, the currently active setpoint is nished
rst and the new setpoint is started afterwards.
Illustration 2.15 Setpoint Handling for 2 Setpoints
New setpoints are buered as long as a free setpoint buer is available in the axis. If no setpoint is in progress, the new
setpoint becomes active immediately (case 1 in Illustration 2.15). If a setpoint is in progress, the new setpoint is stored in the
setpoint buer (cases 2 and 3 in Illustration 2.15).
If all setpoint buers are busy (Setpoint acknowledge bit is set to 1), the reaction depends on the Change set immediately bit.
If the Change set immediately bit is set to 0, the new setpoint is rejected (case 4 in Illustration 2.15). If the Change setimmediately bit is set to 1, the new setpoint is processed immediately. The currently running setpoint prole is discarded
(case 5 in Illustration 2.15).