Motion Rm003 en P
Motion Rm003 en P
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by
suitably trained personnel in accordance with applicable code of practice. If this equipment is used in a manner not specified by the manufacturer,
the protection provided by the equipment may be impaired.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this
equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated
with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and
diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this
manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to
personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic
loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence
Important: Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be
present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc
Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work
practices and for Personal Protective Equipment (PPE).
Summary of changes
Grammatical and editorial style changes are not included in this summary.
Global changes
This table contains a list of topics changed in this version, the reason for the
change, and a link to the topic that contains the changed information.
Chapter 1
Integrated Motion on the Integrated Motion Axis Control Modes and Methods .............................................. 20
Motion Control Modes ............................................................................................ 20
EtherNet/IP Network
Position Control Mode ..................................................................................... 21
Velocity Control Mode ..................................................................................... 23
Torque Control Mode ...................................................................................... 26
No Control Mode .............................................................................................. 26
Motion Control Methods ........................................................................................ 27
Motion Instruction Compatibility ......................................................................... 29
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Additional Resources Use the following resources to get additional information concerning related
products and technologies:
Kinetix 6200 and Kinetix 6500 Safe Torque Off Safety Provides information on wiring, configuring, and
Reference Manual, publication 2094-RM002 troubleshooting the safe torque-off features of your Kinetix
6200 and Kinetix 6500 drives.
Kinetix 5500 Servo Drives User Manual, publication Provides information on install, configure, and troubleshoot
2198-UM001 applications for your Kinetix 5500 drive.
Kinetix 5700 Servo Drives User Manual, publication Provides information on install, configure, and troubleshoot
2198-UM002 applications for your Kinetix 5700 drive.
Kinetix 350 Single-axis EtherNet/IP Servo Drives User Provides information on install, configure, and troubleshoot
Manual, publication 2097-UM002 applications for your Kinetix 350 Single-axis EtherNet/IP
Servo drive.
Kinetix Safe-off Feature Safety Reference Manual, Provides information on wiring and troubleshooting your
publication GMC-RM002 Kinetix 6000 and Kinetix 7000 servo drives with the safe
torque-off feature.
Logix5000™ Motion Controllers Motion Instructions Provides a programmer with details about motion
Manual, publication MOTION-RM002 instructions for motion control.
Logix5000 Controllers Common Procedures, publication Provides detailed and comprehensive information about
1756-PM001 how to program a Logix5000 controller.
Logix5000 Controllers General Instructions Reference Provides a programmer with details about general
Manual, publication 1756-RM003 instructions for a Logix-based controller.
Logix5000 Controllers Advanced Process Control and Drives Provides a programmer with details about process and
Instructions Reference Manual, publication 1756-RM006 drives instructions for a Logix-based controller.
You can view the Rockwell Automation End-User License Agreement ("EULA")
by opening the License.rtf file located in your product's install folder on your hard
drive.
Other Licenses
Trademark Notices
Other Trademarks
All other trademarks are the property of their respective holders and are hereby
acknowledged.
Warranty
This product is warranted in accordance with the product license. The product’s
performance may be affected by system configuration, the application being
performed, operator control, maintenance, and other related factors. Rockwell
Automation is not responsible for these intervening factors. The instructions in
this document do not cover all the details or variations in the equipment,
procedure, or process described, nor do they provide directions for meeting every
possible contingency during installation, operation, or maintenance. This
product’s implementation may vary among users.
This document is current as of the time of release of the product; however, the
accompanying software may have changed since the release. Rockwell Automation,
Inc. reserves the right to change any information contained in this document or
the software at any time without prior notice. It is your responsibility to obtain the
most current information available from Rockwell when installing or using this
product.
Environmental Compliance
Contact Rockwell
Review Motion Control Modes on page 20 for a reference for the Motion Control
Modes and Motion Control Methods that explains when you can use an axis
attribute in an individual control mode.
To learn about how the different control modes function with attributes review
the diagrams provided in Behavior models used in CIP Motion on page 31.
The Control Modes table lists the Motion Axis Attributes specific to the CIP
Drive data type. The table identifies the attribute implementation rule as either
Required, Optional, or Conditional. Drive replicated attributes are identified also.
Review the Interpret the Attribute Tables on page 93 section for an explanation of
how the data for the attributes are organized.
CIP Axis Attributes cover a wide range of drive types. The CIP Axis Attributes on
page 259 topics contain:
• Usage
• Access
• Data type
• Default, minimum, and maximum values
• Semantics of values
Attributes associated with components that are common to all axis instances of a
multi-axis CIP Motion device or module are detailed in Module Configuration
Attributes on page 639.
Integrated Motion Axis The Motion Control Axis Object covers the behavior of various motion control
system devices that includes feedback devices, drive devices, standalone
Control Modes and Methods regenerative and non-regenerative converters, and motion I/O devices. For drive
devices, the Motion Control Axis Object covers a wide range of drive types from
simple variable frequency (V/Hz) drives, to sophisticated position control servo
drives, with or without integral converters. Many commercial drive products have
axes that can be configured with instructions to operate in any one of these
different motion control modes depending on the specific application
requirements.
Based on the variations in Motion Control Mode and Motion Control Method, a
set of basic Device Function Codes have been defined that help organize the many
attributes of the Motion Control Axis. Each attribute has a unique identifier (ID).
See also
Motion Control Modes Motion control modes are organized around the general philosophy that position
control is the highest form of dynamic control. That is, position control implies
velocity control, and velocity control implies acceleration control.
changes with position or time, or when the torque/force constant changes due to
temperature change or motor flux variation.
Linear and rotary control applications can affect the control nomenclature. While
rotary applications speak of torque and inertia, linear applications speak of force
and mass. When we refer to rotary nomenclature, the defined behavior can
generally be applied to linear applications by substituting the terms, force for
torque and mass for inertia. With that understanding, we use torque rather than
force in the control mode diagrams without loss of generality.
See also
Position Control Mode In Position Control application mode either the application control program
(command execution function) or the motion planner (move trajectory control
function) provide a setpoint value to the CIP Motion device using the cyclic data
connection. The Position Control method can be either open loop or closed loop.
A device configured for open loop position control applies to a class of drive
devices called stepper drives. This type of drive is illustrated below.
A motor control device configured for closed loop position control is traditionally
referred to as position loop drive or position servo drive. A position servo drive
implies an inner velocity and torque control loop as shown in following diagram.
The presence of the torque/current control loop sometimes results in this kind of
drive being referred to as a vector drive.
See also
Velocity Control Mode In Velocity Control application mode the application control program and
motion planner provide a setpoint value to the CIP Motion device using the cyclic
data connection. The velocity control method can be either open loop or closed
loop.
A motor control device configured for open loop velocity control is traditionally
referred to as Variable Frequency, or V/Hz, or VFD, drive. This type of drive is
illustrated below.
A motor control device configured for closed loop velocity control is traditionally
referred to as velocity loop drive or velocity servo drive. A closed loop velocity
control drive implies an inner torque/current control loop and therefore is
sometimes referred to as a vector drive.
A feedback device for the velocity loop drive configuration is optional. You can
achieve tighter speed regulation when using a feedback device, particularly at low
speed. When the feedback device is included it may be used to return actual
position, velocity, and acceleration data to the controller using the cyclic data
connection. When the feedback device is not included, only estimated velocity can
typically be returned to the controller.
While not a mainstream control mode in the industry nor mentioned in the IEC
standard, the acceleration control mode is included here to complete the dynamic
progression from velocity control to torque control and because the Motion
Control Axis Object can support an Acceleration Command, potentially derived
from the controller's motion planner. In the acceleration control mode, the
application control program and motion planner provide acceleration set-point
values to the CIP Motion device using the cyclic data connection. The drive
converts the acceleration set-point into a torque command using the estimated
system inertia. Acceleration control works in concert with the inner
torque/current control loop as shown below.
A feedback device for the acceleration control configuration is mandatory and may
be used to return actual position, velocity, and acceleration data to the controller
using the cyclic data connection.
See also
Torque Control Mode In Torque Control application mode, the application control program or the
motion planner provide torque setpoint values to the device using the cyclic data
connection. Because motor current and motor torque are generally related by a
torque constant, Kt, torque control is often synonymous with current control.
A position feedback device for this control mode is optional. If a feedback device is
present it can be used to return actual position, velocity, and acceleration data to
the controller using the cyclic data connection.
See also
No Control Mode The Motion Control Axis Object supports a No Control application mode where
there is no dynamic motor control function. This mode is often used to support
Feedback Only or Master Feedback functionality where a feedback channel in a
CIP Motion Drive device is serving as a master feedback source to the rest of the
control system. This mode could also be applied to integrated CIP Motion
Encoder device types where the CIP Motion interface is applied directly to an
Encoder.
No Control mode also applies to other CIP Motion device types, such as
standalone Bus Power Converters and dedicated Motion I/O device types. Since
there is no feedback channel that is associated with these device types, no actual
position is returned to the controller.
See also
Motion Control Methods Within this basic motion control paradigm, there is latitude for different control
methods, both closed loop and open loop. By closed loop, it is implied that there is
a feedback signal that is used to drive the actual dynamics of the motor to match
the commanded dynamics by servo action.
In most cases, there is a literal feedback device to provide this signal, and in some
cases the signal is derived from the motor excitation, for example,
sensorless/encoderless operation.
The Control Method attribute is an 8-bit enumerated code that determines the
basic control algorithm. The device applies the algorithm to control the dynamic
behavior of the motor that is associated with an axis. The Control Methods
related to the Control Modes are listed in the following table.
1 R/F Frequency Control Frequency Control is an "open loop" control method that
applies voltage to the motor, generally in proportion to
the commanded frequency or speed. This control
method is associated with Variable Frequency Drives
(VFDs) or so called Volts/Hertz drives.
2 R/C PI Vector Control PI Vector Control is a "closed loop" control method that
uses actual or estimated feedback for closed loop
cascaded PI control of motor dynamics, that is, position,
velocity, acceleration, and torque, and always includes
independent closed loop PI control of Iq and Id
components of the motor current vector.
3...127 - Reserved -
128...255 - Vendor Specific -
Axis configuration
The Control Mode and Control Method are derived by the Axis Configuration
according to the following table.
See also
Motion Instruction The following table correlates the motion instructions with the compatible
control modes. The compatibility with integrated motion is based on the Axis
Compatibility
Configuration and feedback type settings. The motion instructions tables are
divided by type.
Symbol Meaning
x Control mode is compatible.
# MSO and MDS execution initiate mutually exclusive modes of operation and execution is conditional on
mode.
* Axis may be used as a master axis reference only for this instruction.
c Axis may conditionally use Motion Planner instructions if enabled with MSO instruction, otherwise, it
errors.
Shaded areas denote that Multi-Axis Coordination Motion is designed and tested for position mode
operation but not specifically restricted to that axis configuration.
Category Motion Instruction Name Abbr. Feedback Freq.Cntrl Pos. Vel. Loop Vel. Loop Torque
Only No Feedback Loop Feedback No Feedback Loop
State Control Motion Direct Drive On MDO
Motion Direct Drive Off MDF
Motion Servo On MSO # x # # #
Motion Servo Off MSF x x x x x
Motion Axis Fault Reset MAFR x x x x x x
Motion Axis Shutdown MASD x x x x x x
Motion Axis Shutdown Reset MASR x x x x x x
Motion Drive Start MDS # # # #
Event Control Motion Arm Watch Position MAW x x x x
Motion Disarm Watch Position MDW x x x x
Motion Arm Registration MAR x x x x
Motion Disarm Registration MDR x x x x
Motion Arm Output Cam MAOC x x x x
Motion Disarm Output Cam MDOC x x x x
Move Control Motion Redefine Position MRP x c x c c c
Motion Axis Home MAH x x c c
Motion Axis Jog MAJ c x c c
Motion Axis Move MAM c x c c
Motion Change Dynamics MCD c x c c
Motion Axis Stop MAS x x x x x x
Motion Axis Gear MAG * c x c c *
Category Motion Instruction Name Abbr. Feedback Freq.Cntrl Pos. Vel. Loop Vel. Loop Torque
Only No Feedback Loop Feedback No Feedback Loop
Motion Master Driven Axis Control MDAC * c x c c *
Motion Axis Position Cam MAPC * c x c c *
Motion Axis Time Cam MATC c x c c
Multi-Axis Coordinate Motion Coordinated Linear Move MCLM c x c c
Motion Coordinated Circular Move MCCM c x c c
Motion Coordinated Stop MCS x x x x x x
Motion Coordinated Shutdown MCSD x x x x x x
Motion Coordinated Shutdown Reset MCSR x x x x x x
Motion Coordinated Change Dynamics MCCD c x c c
Motion Coordinated Transform MCT c x c c
Motion Calculate Target Position MCTP x c x c c x
Motion Master Driven Coordinated Control MDCC * c x c c *
Motion Configuration Motion Run Axis Tuning MRAT x x x
Motion Apply Axis Tuning MAAT
Motion Run Hookup Diagnostic MRHD x x x x x x
Motion Apply Hookup Diagnostic MAHD
Group Control Motion Group Strobe Position MGSP x x x x x x
Motion Group Shutdown MGSD x x x x x x
Motion Group Shutdown Reset MGSR x x x x x x
Motion Group Stop MGS x x x x x x
See also
Control systems and algorithms are used to discuss the CIP motion attributes.
Conceptual diagrams and feature descriptions are provided to help orient you to
the various components of CIP motion.
Behavior models
Acceleration Control Behavior on page 31 Motor Attributes Model on page 64
Command Generation Behavior on page 34 Position Control Behavior on page 65
Current Control Behavior on page 41 State Behavior on page 68
Event Capture Behavior on page 44 Torque Control Behavior on page 78
Fault and Alarm Behavior on page 47 Velocity Control Behavior on page 86
Motion Control Axis Behavior Model on page 57
See also
Acceleration Control While dynamic motor control through an acceleration command is not common
in the industry, Acceleration Control completes the dynamic progression from
Behavior Velocity Control to Torque Control. The output of the velocity loop, Velocity
Loop Output, also has units of acceleration. The sum the contributions of the
Acceleration Command, Acceleration Trim, and Velocity Loop Output to form
the Acceleration Reference signal that serves as one of the primary inputs to
Torque Control behavior. Acceleration Control can optionally include a Load
Observer to compensate for mechanical backlash, mechanical compliance, and
various load disturbances.
See also
Acceleration Limiter The output of the acceleration command summing junction signal passes through
a limiter to produce the Acceleration Reference signal. The Accel Limiter applies a
directional acceleration limit, either the Acceleration Limit or the Deceleration
Limit, to the input command signal based on the sign of the signal.
See also
Load Observer Acceleration Control can optionally include a Load Observer. Feeding the
Acceleration Reference into a Load Observer, along with the velocity feedback
signal, has been found to be effective in compensating for mechanical backlash,
mechanical compliance, and various load disturbances.
The Load Observer's effectiveness in this regard can be thought of as a result of the
observer adding virtual inertia to the motor. When the observer is enabled, it
functions as an inner feedback loop, like the current loop, but unlike the current
loop in that the observer's control loop includes the motor mechanics.
Due to the work of the Load Observer, variations in load inertia, mass, and even
the motor's torque/force constant can be nearly eliminated as seen by the velocity
loop. In fact, because the Load Observer includes the Acceleration Reference
signal as an input, it can provide a velocity estimate signal that has less delay than
the velocity feedback estimate generated by the actual feedback device. Thus,
applying the Load Observer's velocity estimate to the velocity loop can be used to
improve the performance of the velocity loop.
The output of the Load Observer is the Acceleration Estimate signal that is
subsequently applied to the acceleration reference summing junction. When
configured for Load Observer operation, the Acceleration Estimate signal
represents the error between the actual acceleration. The signal is seen by the
feedback device and the acceleration is estimated by the Load Observer. This is
based on an ideal model of the motor and load.
Torque Estimate signal. This signal represents an estimate of the motor torque
disturbance.
The Load Observer can be configured in a variety of ways using the Load Observer
Configuration attribute. Standard Load Observer function is enabled by selecting
the Load Observer Only.
See also
See also
Command Data Sources Command data that impacts axis motion can come from a variety of sources. The
most common command data source is from a controller-based Motion Planner
using the CIP Motion C-to-D Connection. In this context, command data can
take the form of Controller Position, Velocity, Acceleration, and Torque
Commands generated by the Motion Planner. The command data elements
provided are specified by the Command Data Set attribute, which is based on the
selected Control Mode. The primary command data element can be augmented by
higher order command elements for the purposes of generating high quality
feedforward signals. Alternatively, these higher order command elements can be
derived by the device from the primary command data. In either case, a Fine
Another source of command data is a local Motion Planner resident within the
device. The Motion Device Axis Object defines a rich set of features associated
with a device based Motion Planner. These features include support for electronic
gearing, camming, moves, and jogs. Through use of the CIP Motion peer-to-peer
connection, the gearing and camming functions can be directly linked to a master
axis command reference from a producing peer device for high performance
line-shafting applications. Alternatively, the master axis command reference can be
derived from a local motion axis instance. To facilitate these features, the Motion
Planner also supports the ability to establish an absolute position reference to the
machine through homing and redefine position operations as well as perform
rotary unwind functionality. The device's Motion Planner is controlled by CIP
service requests.
Command Data, such as the Controller Velocity Command, can be set directly by
the user. In this context, the device must apply its own Ramp Generator function
to smoothly accelerate or decelerate the motor to the commanded velocity.
See also
Command Fine Interpolation For synchronized, high-performance applications using CIP Motion, command
data is received from the CIP Motion C-to-D Connection or the device's local
Motion Planner, and based on the connection's Command Target Update
element being set to 'Interpolate', processed by the Fine Interpolator functionality
of the Command Generator.
Because the polynomial is a function of time, a new fine command value can be
calculated any time the CIP Motion device needs to perform a control calculation.
As a result, it is not necessary that the device's control calculation period be
integrally divisible into the Controller Update Period.
order, and the acceleration and torque interpolators are both 1st order. Higher
order fine interpolators are possible and are left to the device vendor's discretion.
In these equations, time (t0), represents the Command Target Time for the
previous Motion Planner update such that when t = t0, the position (P), velocity
(V), acceleration (A), and torque (T) command values are equal to the values sent
in the previous Motion Planner update, for example, P–1, V–1, A–1, and T–1. This
establishes the 0th order coefficients of the polynomials.
• P(t 0 ) = P –1 = a 0
• V(t 0 ) = V –1 = b 0
• A(t 0 ) = A –1 = c 0
• T(t 0 ) = T –1 = d 0
The higher order polynomial coefficients are calculated such that by the next
Motion Planner update, corresponding to Command Target Time, t1, the
position, velocity, acceleration, and torque command values are the values sent in
the latest Motion Planner update, for example, P0, V0, A0, and T0.
• P(t 1 ) = P 0
• V(t 1 ) = V 0
• A(t 1 ) = A 0
• T(t 1 ) = T 0
Using the above polynomial interpolation equations, the CIP Motion device can
compute position, velocity, acceleration, and torque command values at any time
by plugging in the current System Time value of the device into the variable, t.
This allows the device's control calculation to be performed according to a
schedule that is independent of the controller's update schedule.
One thing that must be done, however, is to adjust the Command Target Time, t0,
if there is a shift in the System Time Offset for the device; t0 and t are always based
on the same System Time reference system. For example, assume the device's
System Time Offset when the control command timestamp, t0, was received as
Offset0. If the command interpolation equation is to be applied at t= t1 and the
Alternatively, the values for t, t0, and t1 can be based on local time rather than
system time by using the current System Time Offset to convert between System
Time to local time. This may be more convenient for the interpolator
implementation and is left to the device vendor's discretion.
The polynomial coefficients are computed based on standard formulas that are a
function of the history of command values over the last few updates. The number
of historical command values used in the formula depends on the order of the
polynomial. For example, the 3rd order command position polynomial uses the
three previous command position values. For convenience, the interpolator
polynomial coefficient formulas are provided in the following table:
data is always applied and never thrown away; late data still represents the freshest
data available from the controller and the extrapolation polynomial ensures that
the command data is applied in such a way as to maintain a smooth motion
trajectory despite variations in command data delivery.
When the update period of the Motion Planner is short enough relative to the
dynamics of the command trajectory, or is comparable to the device control
calculation period, fine interpolation may not be necessary. The Motion Planner
can make this determination by comparing the planner update period to that of
the device control calculation period. When fine interpolation is used, the planner
adds additional planner update periods to the planner time stamp, so it is
advantageous to eliminate this planner update period delay if interpolation is not
necessary.
Even though fine interpolation may not be necessary in some cases, it does not
mean that the command data is to be applied directly to the device's control
structure. It still may be necessary to calculate the above polynomials so the device
can extrapolate the command value when the device's control update occurs. That
is because, in general, the device's control update time stamp does not need to
match the time stamp of the command data.
Finally, there are applications and CIP Motion device types that do not require
the dynamic accuracy that time-stamped interpolation and extrapolation provide.
Various velocity and Torque Control applications, for example, may fall in this
category. In general, command data can also be applied to the control structures of
Variable Frequency drives without interpolation or extrapolation.
See also
Command Ramp Generator When operating in Closed Loop Velocity mode, the Ramp Generator feature of
the Velocity Fine Command Generator block is applied to the Controller
Velocity Command value sent by the controller when the Command Target
Update element of the connection is set to 'Immediate' mode. In Immediate
mode, the Command Data is applied immediately to the device's control
structure. Because there is generally no Motion Planner generating the Command
Data in this mode, the Command Data value from the controller can change
drastically from one update to the next. To address this condition, a Ramp
Generator function is needed to ramp the motor to the new Command Data value
within the dynamic limitations of the system. As an example of if the Controller
Velocity Command value suddenly changed from 0…30 revolutions per second in
Immediate Mode, the Ramp Generator would produce a Fine Velocity Command
signal that accelerates the motor to the Controller Velocity Command value based
on the configured Ramp Acceleration and Jerk Control attribute values. The
Ramp Jerk Control attribute determines what percentage of the acceleration or
deceleration ramp is S-Curve with the remaining portion of the ramp governed by
The Ramp Generator enforces directional velocity limits on the Command Data,
ensuring that the Velocity Command never exceeds the configured Maximum
Velocity Pos/Neg values.
The Ramp Generator also supports Flying Start functionality. When enabling the
drive while the motor is still moving, the Ramp Generator output is initialized to
the current speed of the motor. From there, the Ramp Generator smoothly
accelerates or decelerates the motor to the current Controller Velocity Command.
Finally, the Ramp Generator supports Skip Bands that are most frequently used in
Frequency Control applications when certain speeds excite mechanical resonance
frequencies of the motor and load. The Skip Band feature allows three separate
Skip Speeds to be defined that shift the Velocity Command signal to avoid, or
skip, these problematic speeds. The Skip Speed Band determines the range of
speeds centered on the three Skip Speeds that the device avoids:
• If the Velocity Command is within the Skip Band, but below the Skip
Speed, the Velocity Command output is set to the Skip Speed, minus half
the Skip Speed Band.
• If the Fine Velocity Command is within the Skip Band, but above the Skip
Speed, the Velocity Command output is set to the Skip Speed, plus half the
Skip Speed Band.
When operating in Frequency Control mode, the Skip Band function is integrated
into the Frequency Control system.
See also
Feedforward Signal Selection The Fine Command Generators can generate higher derivatives of the command
data input to serve as feedforward signals. The units for the velocity and
acceleration feedforward signals are generally different than the derivative units,
hence the derivative signals are scaled appropriately. Superior signal quality,
however, can be provided by the Motion Planner trajectory generators. The
feedforward selection blocks pick the best feedforward signal to apply based on the
bits set in the Command Data Set attribute. The best signal is defined as the signal
derived by using the fewest differencing operations.
The Fine command position is applied directly to the Position Control loop
without any of the typical de-referencing and offsets. It is assumed that these
operations are performed by the controller or device based Motion Planner.
Feedforward signals are only applicable for Closed Loop Position and Closed
Loop Velocity Control Modes.
See also
Command Notch Filter The position command that results from the command interpolation and
feedforward signals then pass through a position command notch filter. The
purpose of this set of filters is to reduce anti-resonance behavior of a compliant
motor load by filtering out any commanded motion around the anti-resonance
frequency.
See also
Current Control Behavior In general, motor torque is controlled by controlling the orientation and
magnitude of the motor stator current vector with respect to the rotor magnetic
flux vector. The Current control loop is responsible for providing this control and
is actually composed of two PI loops, one that controls the torque producing
current, Iq, and one that controls the flux producing current, Id. It is the
quadrature component of current, Iq, that is used for dynamic Torque Control.
In the case of an induction motor, the flux producing current, Id, is solely
responsible for generating rotor flux. In the case of permanent magnet motors,
rotor flux is generated by the rotor magnets and Id is used only in some cases to
extend the speed range of the motor by changing the angle of the stator field
relative to the rotor field. In this case, the angle of Iq relative to the rotor field
remains the same, for example, at quadrature. However, because the vector
combination of Iq and Id determines the stator flux angle relative to the rotor,
increasing amounts of Id can shift the stator flux away from quadrature to extend
the speed range of the motor at the expense of torque.
See also
Current Vector Limiter The Iq Current Command passes through a Current Vector Limiter before
becoming the Iq Current Reference signal. This limiter computes the combined
vector magnitude of the Iq Current Reference and the Id Current Reference
signals. The resultant current vector magnitude is compared to the Operative
Current Limit that represents the minimum current limit from among a set of
potential current limits of the drive device and motor.
If the vector magnitude exceeds the Operative Current Limit, the Iq Current
Reference is reduced so the vector magnitude equals the Operative Current Limit.
Potential current limit sources can be the Peak Current Limit ratings as well as the
Thermal Limits for the Motor and Drive Inverter. Another possible limit source is
the user-configurable Current Vector Limit attribute.
Some of these limits are conditional and dynamic, such as the Motor and Inverter
Thermal Current Limits derived from the thermal models for these devices. These
limits are active only when the corresponding Motor and Inverter Overload
Action attributes are set to provide current fold-back. The thermal current limits
in this case would decrease as the simulated temperature of the modeled devices
increases. The Bus Regulator Limit is applied only when the motor is regenerating
power onto the DC Bus and is based on the Regenerative Power Limit.
With all these potential current limit sources that could be operative, a Current
Limit Source attribute identifies the source of the active current limit.
See also
Voltage Output The output of each current loop is scaled by the motor inductance to generate a
voltage command to the vector transformation block. It is the job of the vector
transformation block to transform the torque producing, Vq, and flux producing,
Vd, command signals from the rotating synchronous reference frame to the
stationary stator reference frame. The resultant U, V, and W Output Voltage
values are then applied to the motor by Pulse Width Modulation (PWM). The
PWM Frequency is also a configurable attribute.
The magnitude of the Vq, Vd vector is calculated in real time as the total Output
Voltage signal. The maximum Output Voltage signal that can be applied to the
motor is ultimately limited by the DC Bus Voltage and enforced by the Voltage
Vector Limiter. Any attempt to exceed this value results in an Inverter Voltage
Limit condition.
See also
Current Feedback Current feedback signals to the current loop are provided by two or three current
sensors. The signals from these sensors are conditioned and corrected for device
specific offsets to become the U, V, and W Current Feedback signals associated
with the stationary motor stator frame. These three signals are transformed back
to the synchronous reference frame to generate the Iq and Id Current Feedback
signals. The magnitude of the Iq, Id current vector is calculated in real-time and
used as an input to the thermal models for the inverter and motor.
See also
Motor Commutation Motor commutation is critical to closed loop motor control. The orientation of
the motor rotor can be determined from a feedback source mounted to the motor.
The actual commutation source is the motor feedback device assigned to Feedback
1 or, possibly, the redundant feedback channel assigned to Feedback 1. Once the
feedback device is calibrated to the absolute orientation of the rotor by using the
Commutation Offset attribute, the commutation block can then generate the true
Electrical Angle of the rotor. This signal is used to perform the vector transforms
between the rotary and stationary motor frames and can also be used for any other
algorithms that require knowledge of rotor position.
See also
Event Capture Behavior Event capture behavior captures both the feedback position and time stamp
associated with specific state transitions of selected event input sources.
The following diagram provides an overview of the event capture behavior model.
See also
Event Input Sources The Motion Device Axis Object defines a mechanism to capture both the
feedback position and time stamp associated with specific state transitions of
selected event input sources. Event input sources currently supported by the object
are:
• Registration 1
• Registration 2
• Marker
• Home Switch.
See also
Event Latches To facilitate accurate capture of both feedback position and time, hardware event
latches are typically implemented.
Two independent latches are defined for each registration input, one latch to
capture positive edge transition events and one to capture negative edge transition
events. This design enables capture of both registration events in applications with
narrow registration pulses where the rising and falling edges occur nearly
simultaneously.
In addition to the registration latches, a separate latch is also defined for the home
event capture. The home input event that triggers the Home Event Latch can be
any of a number of different combinations of home switch and marker input
events, for example, marker transitions, switch transitions, or switch transitions
followed by a marker transition.
With hardware-based event latches, event capture accuracy is, in general, only
limited by the latency of the associated event input. Registration and Marker event
inputs are lightly filtered so event capture accuracy is on the order of 1
microsecond (µsec). In terms of position capture accuracy, that would be
calculated as the product of the event capture accuracy and the speed of the axis.
Home switch inputs are heavily filtered, in general, and therefore limited to an
event capture accuracy of 1 to 10 millisecond (msec). Thus, to get an accurate
position capture based on a home switch input transition, a homing sequence with
a slow homing speed is required.
See also
Event Time Stamps Because the registration time stamp is passed to the controller as part of the Event
Notification data, the controller can apply the event time stamp to the position
history of other axes in the system to interpolate their positions. This is
particularly useful in applications where it is necessary to determine the location of
several axes at the time of a single registration event. The more accurate the time
stamp, the more accurately the controller can determine these positions.
See also
Fault and Alarm Behavior The fault and alarm handling functionality addresses both the need for a large and
ever-expanding number of specific faults and alarms, the need for programmable
actions, and the need for timely reporting of those faults and alarms to the
controller. Additionally, no compromises are made to restrict the resolution of the
reported faults and alarms, so that the controller always has access to the unique
axis condition and a meaningful diagnosis. Numerous Fault and Alarm related
attributes can be included in the fixed portion of the cyclic Device-to-Controller
Connection so the controller can monitor the condition of the axis in real-time,
without cumbersome polling.
The CIP Axis Status attribute contains bits to indicate whether an alarm
condition is present. The CIP Axis State enumeration indicates when the axis has
a major fault, which could be a regular runtime CIP Axis Fault, Safety Fault, or an
Initialization Fault. The Axis Fault Code and related attributes are used to report
the specific fault condition, time stamp, and fault action to the controller for the
purposes of building a fault log.
See also
Exceptions on page 47
Exceptions Exceptions are runtime conditions that the device continually checks that might
indicate improper behavior of the axis or operation outside of an allowable range.
An exception can result in an alarm, a minor fault, or a major fault, depending on
how the associated Axis Exception Action has been configured – an exception can
even be configured to be ignored. Exceptions are automatically cleared by the
device when the underlying exception condition is no longer present.
Exception Actions
For each exception, the motion axis can be programmed for a variety of actions
using the Exception Action attribute. Exception Actions range from generating a
major fault that results in the stopping of the axis all the way to taking no action at
all. The CIP Axis Faults attribute allows the controller to have immediate access to
any exceptions that have been configured to generate a major or minor fault. The
CIP Axis Alarms attribute allows the controller to have immediate access to any
exceptions that have been configured to be reported as alarms.
Alarms
Alarms are runtime exception conditions for which the device is to take no action
other than to report as an alarm. Alarms and warnings, therefore, are basically
synonymous. On a given device product, some exception conditions may not be
able to simply be reported as an alarm without any associated action; for example
an IPM fault in which the power module automatically shuts off without software
intervention. Alarm conditions are automatically cleared when the underlying
exception condition is no longer present.
Faults
Faults can be initialization faults, configuration faults, safety faults, module faults,
group faults, motion faults, or runtime exception conditions that the axis has been
configured to regard as a fault. Fault conditions can occur in either the controller
or motion device. If a runtime fault occurs during an operational state, for
example, Running or Testing, it will result in the device stopping (or aborting) all
axis motion, either automatically or programmatically. Fault conditions ultimately
transition the axis state to the Faulted state. A Fault that results from an exception
condition is latched, and does not clear when the exception condition clears. A
fault can only be cleared with a Fault Reset. If the fault condition is classified as an
'unrecoverable fault', only a power cycle or a device reset can clear the fault
condition.
A Start Inhibit is a condition that inhibits the axis from starting, i.e. transitioning
to the Starting state for enabled axis operation. This condition does not generate
an exception if a start attempt is made. If the circumstances that led to the Start
Inhibit are no longer present, the start inhibit condition is automatically cleared
by the device, returning the axis to the Stopped State.
If the axis is in the Start Inhibit state it indicates that one or more conditions are
present that prevent the axis from transitioning to enabled operation. The Start
Inhibits attribute reports the specific condition that is inhibiting the axis.
See also
Absolute Position Recovery Absolute Position Recovery (APR) provides support for establishing and
maintaining absolute position referenced to a specific machine, commonly called
the machine referenced absolute position or just absolute position.
Since the homing procedure usually requires the machine to be taken offline and
placed in a manual operating mode, for example, not making product, anything
that would require you to rehome one or more axes on the machine is undesirable.
This is downtime and costs money. The APR feature maintains the machine
reference or absolute position through power cycles, program downloads, and even
firmware updates.
The absolute feedback device lets absolute position to be retained through a power
cycle. These devices take various forms, but they all are capable of maintaining
absolute feedback position while power to the drive and to the feedback device is
off.
When power is turned back on, the drive reads the feedback referenced absolute
position from the feedback device and, by applying a saved absolute offset to this
absolute feedback position, the motion control system can recover the machine
referenced absolute position.
Most drive products provide this capability. But what happens if the drive is
swapped out, or the drive firmware is updated? Absolute Position is generally lost.
CIP Motion lets you recover the absolute position not only through power cycles,
but also program downloads, and even firmware updates.
For a SERCOS axis with absolute feedback, the drive scaling function and
absolute position is maintained in the drive and therefore may be easily restored in
the control after a power cycle or download of a new project by simply reading the
position from the drive.
By contrast, a CIP Motion axis supports controller based scaling where absolute
position is maintained in the controller’s firmware. Without the work of the APR
feature, absolute position would be lost after a power cycle or project download.
See also
Absolute Position Loss without APR The Absolute Position Recovery is not retained after the following:
Faults
• A project is exported, saved as a .L5K or .L5X, and imported (downloaded).
• A major non-recoverable fault (MNRF).
• A power loss.
• On a Control Logix 5570 controller without an ESM
Tip: The APR can potentially be restored from a Secure Digital Card on a ControlLogix
5570 Controller (if a 1756-ESM is not present).
• A download of an axis that does not have its home bit set.
• Power cycling of an incremental encoder.
See also
APR Fault Conditions Absolute Position Recovery (APR) faults are generated during these events and
when one of the conditions defined below occurs.
In order for an APR Fault to occur, the axis must be in the homed state. The Axis
Homed Status Bit must be set.
Attribute Changes
A Motion Resolution or an Axis Feedback Polarity attribute has been changed and
downloaded to the controller. This can also happen during the execution of an
SSV.
The feedback device has been replaced. This creates an Axis Feedback Serial
Number mismatch.
Axis Feedback Mode has changed, for example, axis with feedback changed to axis
without feedback or vice versa and downloaded to the controller.
When an APR fault occurs, the actual position of the axis is set to the feedback
reference position of the axis. The values are read from the absolute encoder. This
clears the axis homed status bit.
• Axis Configuration
• Attribute Changes
• Offline edits of the axis attributes or configuration does not cause an
APR fault until after download occurs.
• Online edits of certain attributes will result in an immediate APR fault.
Changing the axis feedback device or feedback polarity without
downloading the project will also generate an immediate APR fault.
• Axis hardware change or malfunction
• Axis hardware resource insufficiency
• Hardware resource insufficiencies are only detected during download
or ControlFLASH firmware update and will result in an APR fault.
1. Existing Axis?
Changes to the following attributes do not impact the Scaling Signature or result
in the loss of the absolute machine reference and therefore do not generate an
APR Fault.
• Conversion Constant
• Position Unwind
• Travel Mode
Care must be taken when changing these values that the new values are rightly
related to the Position Unit of the product and the mechanics of the system. This
is typically done as part of a product recipe change.
If the Axis Homed status bit is clear, indicating that position has not been
absolutely referenced to the machine, the APR function is bypassed and there is no
attempt to restore absolute position.
See also
Changing the Scaling parameters can potentially generate an APR fault because
internal constants computed from these two parameters may generate a motion
resolution change. If this happens, an APR fault is generated.
Online Scaling
Any change or SSV message that results in a motion resolution change will
generate an APR fault.
See also
APR Recovery Scenarios The following tables provide detailed information on when the APR feature
recovers absolute position. The following assumptions need to be taken into
consideration. In each of these cases, the APR feature restores absolute position
and preserves the state of the Axis Homed bit, indicating that the axis has a
machine referenced absolute position.
• No, machine reference is not recovered (for Axes that have been homed).
Scenario Event Machine Reference
Retained
Controller Battery(1) Yes
Controller Power Cycle with Battery Yes
Controller Removal/Insertion Under Power (RIUP) with Battery Yes
Controller Firmware Update Yes
Controller CompactFlash Update Yes
Controller Swap (Same CF Card) Yes
Change Controller No
Change Controller without a CompactFlash Card No
Controller Power Cycle without Battery No
Controller Removal/Insertion Under Power (RIUP) without Battery No
Take the controllers out of two systems with a battery or energy storage No
module and swap controller. There are no CompactFlash or Secure
Digital cards on either controller
1. Controller remains powered. No
2. Power cycle drives.
3. Change feedback device but not motor
Controller Power Cycle or Removal and Insertion Under Power without a No
battery or energy storage module.
See also
Reset an APR Fault There are three ways to reset an APR Fault.
• Instruction Execution
Executing an MAFR
Executing an MGSR
Executing an MASR
Executing a MCSR
See also
Motion Control Axis The Motion Control Axis Behavior Model is based on elements of the S88 and
Pack/ML standard state models. The current state of the Motion Control Axis is
Behavior Model indicated by the CIP Axis State attribute. State transitions can be initiated either
directly using the Axis Control request mechanism or by conditions that occur in
either the controller or motion device during operation.
Review the diagram for the behavior model to see how the axis state maps to
identity object states.
When an axis is in the Major Faulted state, the axis may transition to one of several
different states in response to a Fault Reset event. Which state the axis transitions
to is dependent upon other state/status conditions of the axis.
It is possible for more than one state condition to be present at the same time, for
example. Shutdown, Start Inhibited, and so forth. Since the axis state model can
only represent one state at any given time, the state of the axis is determined
according to the following precedence:
1. Major Faulted
2. Shutdown
3. Pre-Charge
4. Start Inhibited
5. Stopped
See also
Exceptions on page 47
Active Control Axis Behavior The current state of the Motion Control Axis Object instance is indicated by the
CIP Axis State attribute. State transitions can be initiated either directly using the
Model
Axis Control request mechanism or by conditions that occur in either the
controller or motion device during operation.
The diagram illustrates the basic operating states of the Motion Control Axis
when actively controlling axis motion (Control Mode != No Control), or in the
case of a regenerative converter, when actively controlling power. Shaded regions
show mapping of Axis States to corresponding Identity Object states. State
transitions terminating on shaded boxes can transition to any axis state within the
box.
Tip: * Specific Standby State after a Fault Reset is determined by applying the Fault Reset State Transition Precedence
Rules.
** When an axis is in the Stopped or Major Faulted states with Holding torque (as a result of a Category 2 Stop), a Start
Inhibit condition, Disable Request, or Shutdown Request is used to execute the configured Stopping Action.
Valid transitions for the Axis State Model are defined in the following table:
See also
Exceptions on page 47
Feedback Only Axis Behavior When the Motion Control Axis is not actively controlling axis motion (Control
Mode = No Control), the state diagram reduces to the following for a Feedback
Model
Only axis or CIP Motion Encoder device type. Shaded regions show mapping of
Axis States to corresponding Identity Object states. State transitions terminating
on shaded boxes can transition to any axis state within the box.
Tip: Apply the Fault Reset State Transition Procedures rules to determine the
Specific Standby state.
Valid transitions for the Axis State Model of a Feedback Only axis or CIP Motion
Encoder are defined in the following table:
See also
Exceptions on page 47
CIP Motion Non-regenerative When the Motion Device Axis Object is associated with a CIP Motion
Non-regenerative Converter, the Active Control state diagram reduces to the
Converter Axis Behavior Model
following diagram. Shaded regions show mapping of Axis States to corresponding
Identity Object states. State transitions terminating on shaded boxes can
transition to any axis state within the box.
Tip: *Specific Standby state after a fault reset is determined by applying Fault Reset State Transition Precedence rules.
Valid transitions for the Axis State Model of a CIP Motion Non-regenerative
Converter axis are explicitly defined in the following table:
See also
Exceptions on page 47
Motor Attributes Model The Motor Attributes define the minimal set of required attributes to support
CIP Motion device interchangeability. This guarantees that there is sufficient
parametric data provided by the controller for any CIP Motion compliant device,
for example, a drive, to effectively control a given motor.
The Usage category for an attribute is based on the Motor Type. Where needed,
Required versus Optional is further differentiated by abbreviations for PM
(Permanent Magnet) and IM (Induction Motors). It is implied that these motor
attributes are applicable to all drive modes, F, P, V, and T, but not applicable for
the No Control axis configurations where there is no active motor control
function.
For induction motors, the Motion Control Axis leverages the IEEE recommended
phase-neutral equivalent circuit motor model based on "Wye" configuration.
Reactance values, X, are related to their corresponding Inductance values, L, by X
= ωL, where ω is the rated frequency of the motor. The prime notation, for
example, X2', R2', indicates that the actual rotor component values X2, and R2 are
referenced to the stator side of the stator-to-rotor winding ratio.
For permanent magnet motors, the Motion Control Axis assumes all motor
parameters are defined in the context of a phase-to-phase motor model.
See also
Position Control Behavior In Position Control mode, the only operative Control Method supported is
Closed Loop servo control. When performing closed loop Position Control, the
device applies the Position Command signal output of the Command Generator
to the position loop summing junction. In addition to the Position Command, a
Position Trim input is provided that can be used to provide an offset to the
position loop. The classic PI control loop generates a Position Loop Output signal
to an inner velocity loop.
The following diagram provides an overview of the closed loop position control
behavior model.
See also
Position Feedback Selection Feedback to the PI regulator can be derived from two different feedback channels.
This flexibility allows the position loop to operate with either a motor based
feedback device that is typically attached to the Feedback 1 channel or a load-side
feedback device that is connected to the Feedback 2 channel. Which feedback
source is used by the loop is governed by the Feedback Mode attribute.
When the Feedback Mode calls for Dual Feedback operation, the position loop
utilizes the Feedback 2 channel and the velocity loop uses the Feedback 1 channel.
Since the two feedback channels may not have the same feedback resolution, it is
necessary to convert position loop output from Feedback 1 units to Feedback 2
units prior to applying the output to the velocity loop summing junction. This is
done by scaling the position loop output using the Feedback Unit Ratio.
See also
Position PI Gains The Proportional Gain of the classic proportional-integral (PI) controller sets the
unity gain bandwidth of the position loop in radians/second, while the Integral
Gain is used to devise the Position Error signal to zero to compensate for the effect
of any static and quasi-static torque or forces applied to the load.
See also
Velocity Feedforward The inner velocity loop requires a non-zero command input to generate
steady-state axis motor velocity. To provide the non-zero output from the device
to the motor, a non-zero position loop output is required, which translates to a
non-zero position error.
This dynamic error between command position and actual position while moving
is often called "following error". Most closed loop motion control applications
require zero following error all of the time. This could be achieved to some extent
through use of the position integral gain control, but typically the response time of
the integrator action is too slow to be effective in high-performance motion
control applications. An alternative approach that has superior dynamic response
is to use Velocity Feedforward.
The Velocity Feedforward feature is used in Position Control mode to provide the
bulk of the Velocity Reference input necessary to generate the desired motor
velocity. It does this by scaling the Fine Velocity Command signal output of the
Command Generator by the Velocity Feedforward Gain and adding the resultant
Velocity Feedforward Command signal to the Position Loop Output generated by
the position loop to form the Velocity Reference signal. With this feature, the
position loop does not need to generate much effort to produce the required
velocity command level, hence the Position Error value is significantly reduced.
The Velocity Feedforward Command signal allows the following error of the
position control loop to be reduced to nearly zero when running at a constant
velocity. This is important in applications such as electronic gearing and
synchronization applications where it is necessary that the actual axis position not
significantly lag behind the commanded position at any time.
Theoretically, the optimal value for Velocity Feedforward Gain is 100%. In reality,
however, the value may need to be adjusted to accommodate velocity loops with
finite loop gain. One thing that may force a smaller Velocity Feedforward value is
that increasing amounts of feedforward tend to exacerbate axis overshoot. For this
reason feedforward is not recommended for point-to-point positioning
applications.
See also
Position Loop Output Filters A lead-lag filter is provided at the output of the position loop forward path. This
filter can be used in the lead configuration to boost position loop bandwidth and
increase the stiffness, for example, the ability to resist dynamic load disturbances.
In this equation, Kn represents the Lead-Lag Filter Gain, or high frequency gain of
the filter (the low frequency gain is always 1), and wn represents the Lead-Lag
Filter Bandwidth associated with the pole of the filter:
Finally, a notch filter is included that has been shown to be effective in solving
certain types mechanical compliance problems. The equation for this filter is as
follows:
In this equation, Q represents the sharpness of the notch, and A represents the
attenuation depth of the notch. In most implementations, the sharpness, Q, and
the attenuation depth, A, are hard-coded in the device. In PowerFlex drives the
value of Q is 0.62 and the depth is set to 30.
See also
State Behavior The Motion Control Axis state model includes the following the states and state
transitions.
Off State
This is the state of the Motion Control Axis with power off.
When power is applied to the controller, the controller typically goes through a
series of self-test diagnostics. These tests include checking whether the CIP
Motion axis is associated with an actual CIP Motion device and that the axis is
also properly included in a collection of axes called a Motion Group. All axes in
the Motion Group are processed synchronously by the controller's Motion Task.
If an associated CIP Motion device or Motion Group is not found for the axis, the
axis state in the controller reflects this condition as No Device, and Not Grouped,
respectively. The axis will remain in this state until the problem is corrected.
Similarly, when power is applied to the device, or the device is reset, the device also
goes through a series of self-test diagnostics and internal device parameters are set
to their power-up default values. If unsuccessful, the impacted axis instances
transition immediately to the Faulted state by declaring an Initialization Fault that
is classified as Un-recoverable according to the terminology defined by the Identify
Object. Clearing this fault can only be accomplished through a power cycle and is
most likely the result of a device hardware problem.
Once these self tests have been completed successfully by the CIP Motion
controller and the associated CIP Motion device, the axis state transitions to the
Initializing state where CIP Motion connections are created and the devices are
configured by the controller. From this point on, the Axis State value in the
controller is influenced by the Axis State value in the device using the CIP Motion
connection.
If the CIP Motion device supports stand-alone operation under local control with
local configuration data, the device is free to transition from the Self-test state to
the Pre-Charge state and on to the Stopped state. Should the device receive a
subsequent Forward Open service to open a CIP Motion connection, the device
will disable all axes and transition back to the Initializing state, following the state
sequence outlined below.
If the device does not support stand-alone operation and depends on remote
configuration data to be supplied over a CIP Motion connection, the device will
transition to the Initializing state and wait (Standby) for the Forward Open
service from the controller to open the CIP Motion Connection.
Initializing State
From the controller's perspective the Initializing state shown in the state models
consists of 4 different axis sub-states, Unconnected, Configuring, Synchronizing,
and Waiting for Group. While transitioning through these Initializing sub-states,
the controller has no access to current Axis State value in the drive. Only after the
controller's CIP Axis State completes the Initialization process, does the CIP Axis
State value reflect the current Axis State attribute value in the CIP Motion device.
During the Initializing state, the device waits for the CIP Motion connections to
the device to be established by the controller using a Forward Open service. Once
the Forward Open service is successfully processed, the device initializes all
attributes to their factory default values, resets all active faults, resets applicable
axis status conditions including the shutdown bit, in preparation for device
attribute configuration.
Once connections are established, the controller sends Set services to the device to
set the Motion Device Axis Object configuration attributes to values stored in the
controller. Any configuration error encountered during this process, such as "value
out of range" or "value not applicable", are handled by the device by erring the Set
service response. When the CIP Motion device is connected to one or more
intelligent motor and feedback components that contain non-volatile
configuration data associated with the component, this data will be read by the
device prior to responding to related Set services from the controller. This allows
the device the opportunity to validate the controller's motor and feedback related
configuration data against the configuration data stored in the motor or feedback
component. Any validation error encountered during this process will be handled
by erring the Set service response with an "Invalid Attribute Value" code (09).
Finally, reading the intelligent component data prior to completing the
configuration process also allows the serial number of the component to be read by
the controller to determine if the component has been replaced. The controller
does not complete the configuration process (Configuration Complete) until all
configuration attributes have been successfully acknowledged.
After the device is fully configured and synchronized with the controller, the
controller checks all other axes in the Motion Group to determine if they are also
configured and synchronized. During this time, the CIP Axis State is "Waiting for
Group". As soon as the controller determines that all axes in the Motion Group
are configured and synchronized, Initialization is complete and the CIP Axis State
value is thereafter derived directly from the Axis State value of the device in
accordance to the state model defined in the Motion Device Axis Object.
If a problem is found during this initialization process, for example, a process that
is beyond the scope of a Set service error, the device generates an Initialization
Fault. An Initialization Fault is viewed as an unrecoverable fault, only a power
cycle or a device reset can clear the fault condition.
If the CIP Motion connection is intentionally closed for any reason during
operation using a Forward Close service, the device clears all active faults and
returns to the Initializing State. If the CIP Motion connection is lost for any other
reason during operation, the device generates a Node Fault and transitions to the
Major Faulted state. In either case the device will wait for the CIP Motion
connections to the device to be re-established by the controller using a Forward
Open service. Once re-established the controller's CIP Axis State will transition
through the various Initialization sub-states.
Pre-Charge State
During the Pre-Charge state, when applicable, the device is waiting for the DC
Bus to fully charge (DC Bus Up status bit is clear). Once the DC Bus reaches an
operational voltage level (DC Bus Up status bit is set), the axis either transitions to
the Stopped state (drive axis or regenerative converter axis) or to the Running state
(non-regenerative converter axis). The device's power structure is always disabled
in this state (Power Structure Enabled status bit clear). Any attempt for the
controller to enable the axis using the Axis Control mechanism while it is in the
Pre-Charge state is reported back to the controller as an error in the Response
Status and the axis remains in the Pre-Charge state.
Stopped State
In the Stopped state the device's power structure will either be disabled (Power
Structure Enabled status bit clear) or, in the case of a drive axis, held in a static
condition using an active control loop (Power Structure Enabled status bit set).
No motion can be initiated by a drive axis in the Stopped State nor can a drive axis
respond to a planner generated command reference (Tracking Command status
bit clear). In general, the motor associated with the drive axis will be at rest, but if
an external force or torque is applied to the load, a brake may be needed to
maintain the rest condition. Similarly, no AC Line modulation can be applied by a
regenerative converter axis in the Stopped state, nor can any regenerative energy be
transferred to the AC Line. In the Stopped state, main power is applied to the
device and the DC Bus is at an operational voltage level. If there are any Start
Inhibit conditions detected while in this state, the axis transitions to the Start
Inhibited state. If an Enable request or one of the Run Test service requests is
applied to an axis in the Stopped state, the axis transitions to the Starting state.
Starting State
When an Enable request is given to an axis in the Stopped, or Stopping state when
performing a drive Flying Start, the axis immediately transitions to the Starting
state. In this state, the device checks various conditions before transitioning to the
Running state. These conditions for a drive axis can include Brake Release delay
time and Induction Motor flux level. The device control and power structures are
activated during the Starting state (Power Structure Enabled status bit set) but the
command reference is set to a local static value and will not track the command
reference derived from the controller (Tracking Command status bit clear). If all
the starting conditions are met, the axis state transitions to either the Running
state or the Testing state.
Running State
The Running state is where the work gets done. In this state, the device's power
structure is active (Power Structure Enabled status bit set). In the case of a drive
axis, the selected Control Mode is enabled and the device begins actively tracking
command data from the controller based or device based motion planner output
to impact axis motion (Tracking Command status bit set).
In the case of a Feedback Only Control Mode, the Running state simply indicates
that the feedback device is fully operational. The motion axis remains in the
Running state until either a fault occurs or it is explicitly commanded to stop using
an Axis Control request. n the case of a regenerative converter axis, the Converter
Control Mode is enabled and the device beings actively tracking the Voltage or
Current set point value from the controller (Tracking Command status bit set).
The axis remains in the Running state until either a fault occurs or it is explicitly
commanded to Shutdown using an Axis Control request.
Testing State
When any one of the Run Test request services is sent to the axis while in the
Stopped state, for example, services that require an active power structure to
execute, the axis immediately transitions to the Starting State (Power Structure
Enabled status bit set), and then once the Starting conditions are met, the axis
transitions to the Testing state. This Testing state is like the Running state in that
the device's power structure is active, but in the Testing state one of the device's
built-in test algorithms is controlling the motor (drive) or line energy flow
(regenerative converter), not command or set point data from the controller
(Tracking Command status bit clear). In the Testing state a drive excites the
motor in various ways while performing measurements to determine
characteristics of the motor and load. Similarly a regenerative converter device
applies current in various way to determine characteristics of the AC line and DC
bus. The drive or converter axis remains in this state for the duration of the
requested test procedure and then stops and returns to the Stopped state. The axis
can also exit the Testing state by either a fault or an explicit Axis Control request.
In all these exit cases, a drive executes a Category 0 Stopping Sequence.
The Start Inhibited state is the same as the Stopped state with the exception that
the axis has one or more 'start inhibit' conditions that prevent it from successfully
transitioning to the Starting state. These conditions can be found in the Start
Inhibits attributes. Once corrected, the axis state automatically transitions back to
the Stopped state.
For an axis with no active control function (Control Mode = No Control), an axis
in the Start Inhibited state is prevented from transitioning to the Running state by
one or more specific conditions, such as when the associated feedback device is not
fully configured for operation. Again, once corrected, the axis state automatically
transitions to the Running state.
The Start Inhibited State is classified as an Identity Object Standby state and,
therefore, requires that the associated power structure, if applicable, is disabled.
Stopping State
When a Disable request is issued to the Motion Device Axis Object in the
Starting, Running or the Testing states, the axis immediately transitions to the
Stopping state. In this state, the axis is in the process of stopping and is no longer
tracking command or set point data from the controller (Tracking Command
status bit clear). For a drive axis, a Disable Request executes the configured
Stopping Actions while a Shutdown Request executes the configured Shutdown
Action.
There are many different Stopping Actions supported by the Motion Device Axis
Object for a drive axis. Each of these Stopping Actions executes one of three
possible IEC60204-1 Category Stops or Stopping Sequences (Category Stop 0, 1,
and 2). Most of these Stopping Actions actively decelerate the axis to a stop
(Category Stop 1 and 2). The power structure may remain active (Power Structure
Enabled status bit set) as long as the Stopping Action procedure takes to complete.
Once the selected Stopping Action procedure has completed, the axis transitions
to the Stopped state. When the Stopping Action of "Disable and Coast" is
initiated by a Disable Request or a Shutdown Action, the power structure is
immediately disabled (Power Structure Enabled status bit clear) and the axis coasts
to a stop while in the Stopping state (Category 0 Stop). For all Stopping
Sequences, the device will wait until the axis has reached zero speed, or a timeout
occurs (as defined by the Stopping Time Limit and Coasting Time Limit
attributes), before transitioning to the Stopped state. In some cases, such as when
the axis is stationary, this transition can be immediate. The criteria for zero speed
is based on Velocity Feedback being less than 1% of motor rated speed or by
criteria set by optional Zero Speed and Zero Speed Time attribute values. In the
case of a Frequency Control drive device, the criteria are based on Velocity
Reference rather than Velocity Feedback.
When an Enable Request is given to a drive axis in the Stopping state with Flying
Start Enabled, the axis will immediately transition to the Starting state.
Aborting State
When a Major Fault occurs in the motion device while the axis is in either the
Starting, Running, Testing, or Stopping states, the axis immediately transitions to
the Aborting state. In this state, the axis is in the process of stopping and is no
longer tracking command or set point data from the controller (Tracking
Command status bit clear).
For a drive axis, a Major Fault executes the appropriate stopping action as specified
by the device vendor. When actively stopping the drive axis in the Aborting state,
the power structure remains active (Power Structure Enabled status bit set) as long
as the stopping action takes to complete. In some cases, the power structure must
be immediately disabled so the axis may coast to a stop while in the Aborting state.
In any case, the drive axis will wait until the axis has reached zero speed before
transitioning to the Major Faulted state. Once the stopping procedure is complete
and the axis has reached zero speed, the axis transitions to the Faulted state. The
criteria for zero speed is based on Velocity Feedback being less than 1% of motor
rated speed or by criteria set by optional Zero Speed and Zero Speed Time
attribute values. In the case of a Frequency Control drive axis, Velocity Reference
is used rather than Velocity Feedback. In some cases, such as when the axis is
stationary, this transition can be immediate.
When faults conditions are detected in the controller that are not visible to the
motion device, or when the motion device reports a Minor Fault condition, the
controller is responsible for bringing the axis to a stop, either directly using an Axis
Control state change request or, in the case of a drive axis, directly by a motion
planner stop, or indirectly using a fault handler in the user program. If the Axis
State reported by the motion device is Stopping, then the controller sets the CIP
Axis State to Aborting based on the presence of the fault condition.
When an Abort Request is issued to the Motion Device Axis Object a Controller
Initiated Exception is generated. If the associated Axis Exception Action is set to
generate a Major Fault the drive axis stops the axis according to the configured
Stopping Action before transitioning to the Faulted state.
Faulted State
The Motion Device Axis Object defines a Major Faulted state that is identical to
the Stopped state (or, if a Shutdown fault action was initiated, the Shutdown
state) with the exception that there are one or more Faults active. In other words, a
Major Faulted axis is a Stopped (or Shutdown) axis with a Major Fault condition
present. The Motion Device Axis Object also defines a Minor Fault as a fault that
allows device operation to continue and does not impact the Axis State in the
motion device.
There is no such distinction between Major Fault and Minor Fault in the
controller; both Major Faults and Minor Faults reported by the drive result in the
axis transitioning to the Faulted state in the controller. Thus, in the controller it is
not generally true that a Faulted axis is a Stopped (or Shutdown) axis with a Fault
condition present. When the motion device reports a Minor Fault condition, or
when fault conditions are detected in the controller that are not visible to the
motion device, the controller is responsible for bringing the axis to a stop, either
directly using an Axis Control state change request or motion planner stop, or
indirectly using a fault handler in the user program. Until this is done, the Axis
State in the motion device may be something other than the Major Faulted state,
perhaps even in the Running state. This is reasonable given that the motion device
is only one component in a much bigger motion control system. The CIP Motion
controller is responsible for rolling up all the conditions of the system into the
Axis State that is presented to you.
Since faults are latched conditions, a Fault Reset is required to clear the faults and,
assuming the original fault condition has been removed, the axis transitions to the
Axis State of motion device. There are many different sources of Faults: CIP
Initialization Faults, CIP Axis Faults, Motion Faults, Module Faults, Group
Faults, Safety Faults, and Configuration Faults. The following table describes the
sources of these faults:
Fault Source
CIP Initialization Faults These faults can only occur during the Initializing state. You cannot generate an Initialization
fault in any other state of the drive, for example, faults occurring during operation of the drive
after transitioning out of the Initializing state. Initialization Faults can apply to a specific axis or
to the entire drive, in which case all device axis instances would indicate the Initialization Fault.
The device power structure, if applicable, is disabled when there is a CIP Initialization Fault
present.
CIP Axis Faults As the name implies, CIP Axis Faults apply to a specific device axis instances. CIP Axis Faults are
the direct result of Axis Exceptions that are configured to generate a Fault response. These
exception conditions may apply to individual axis instances or to all axis instances. In any case,
applications may require the device be configured to handle these exceptions differently for
different axes. Run time conditions related to Motor, Inverter, Converter, Bus Regulator, and
Feedback components, in general, shall be handled as Axis Exceptions. The power structure if
applicable, may or may not be disabled when there is a CIP Axis Fault present depending on the
specific stopping action applied by the device in response to the fault condition.
Axis Safety Faults Axis Safety Faults also apply to specific axis instances. Axis Safety Faults are the direct results of
safety faults reported by the embedded Safety Core of the device when Safety Fault Action is
configured to generate a Fault response. The Safety Core of the device is responsible for
monitoring the condition of various critical safety functions associated with the axis. This
embedded Safety Core has a CIP Safety connection to an external Safety Controller. When an
Axis Safety Fault occurs, the safety system is responsible for forcing the axis into a Safe State.
Guard Faults These faults also apply to a specific axis instance. Guard Faults are generated by a fault
condition detected in the drive's "Hardwired" safety monitor functionality (SMSC). This
component of the drive is designed to monitor various critical safety functions of the drive and
put the axis in a safe state if any monitored condition fails to operate nominally.
Motion Faults These faults are generally associated with fault conditions generated by the motion planner
function. These faults can include conditions related to the input (for example, actual position)
and output (command position) signals to the motion planner. The device power structure, if
applicable, may or may not be disabled when there is a Motion Fault present depending on the
specific stopping action applied by the system in response to the fault condition.
Module Faults These faults apply to the entire motion device and affect all axes associated with that device.
These faults can occur at any time during device operation. Module Faults include all Node
Faults reported by the device, which are primarily communication faults, but can include
general hardware faults where these fault conditions are checked during run-time. A CPU
watchdog fault would be an example of a hardware CIP Node Fault. Module Faults also include
communication fault conditions detected on the controller side of the motion connection. An
example of a controller side Module Fault would be the Control Sync Fault. The device power
structure, if applicable, is disabled when there is a Module Fault present with the controller
initiating the equivalent of a shutdown fault action.
Group Faults These faults are related to the motion group object function and affect all axes associated with
the motion group. These faults can occur at any time during device operation. Group Fault
conditions are detected by controller and are generally associated with the time
synchronization function that is common to all axes in the motion group. The device power
structure, if applicable, of every axis associated with the motion group is disabled when there is
a Group Fault present with the controller initiating shutdown fault actions.
Fault Source
Configuration Faults A configuration fault is generated anytime there is an error in sending configuration data to the
motion device. Specifically, if the motion device responds to a Set Attribute service with an
error, the error condition is reflected as a Configuration Fault along with the Attribute Error
Code and Attribute ID. The device power structure, if applicable, is disabled when there is a
Configuration Fault present.
Shutdown State
In the case where a Shutdown fault action is initiated by the drive in response to
an exception condition that is configured to be a Major Fault, the device executes
the Shutdown action, but the axis goes to the Faulted state, not the Shutdown
state. Similarly, when the axis is in the Shutdown state and a major fault condition
occurs, the axis transitions to the Faulted state. In other words, the major fault
condition has precedence over the shutdown condition and the shutdown
condition can be considered a sub-state. In either of these cases a Fault Reset
request from the controller clears the fault and, assuming the original fault
condition has been removed, the axis then transitions to the Shutdown state. A
Shutdown Reset request from the controller, however, both clears the fault and
performs a shutdown reset so, assuming the original fault condition has been
removed, the axis transitions to the Pre-Charge state as described above.
In addition to the Shutdown action functionality, the Shutdown state can also be
used by the controller to disable any slave gearing or camming motion planner
functions that reference this device axis as a master axis. For this reason, the
Shutdown state is supported in the case of a Feedback Only Control Mode where
the axis instance is simply associated with a feedback device.
No Device State
If the CIP Motion axis instance in the controller is created, but not currently
associated with a CIP Motion device, the axis state indicates the No Device state.
A CIP Motion axis will be associated with a physical CIP Motion device to
function. This condition is checked during the controller Self Test state as
qualification for transition to the Initializing state. For this reason the No Device
state is considered a controller only sub-state of the Self Test state.
If a CIP Motion axis instance is created and not associated with a Motion Group,
the axis state is set to the Not Grouped state. A CIP Motion axis will be assigned
to a Motion Group in order for the axis instance to be updated by the periodic
Motion Task and carry out its function. This condition is checked during the
controller Self Test state as qualification for transition to the Initializing state. For
this reason, the Not Grouped state is considered a controller only sub-state of the
Self Test state.
If you Inhibit the axis instance for any reason, the associated instance in the CIP
Motion connection is eliminated and the axis state transitions to the Axis
Inhibited state. If this is the only instance supported by the CIP Motion
connection, the connection itself will be closed. The Axis Inhibited state is a
controller only sub state of the Self Test state. The Axis Inhibited condition is
checked during the controller Self Test state as qualification for transition to the
Initializing state. If currently Axis Inhibited, an Un-Inhibit operation will be
performed by you to transition to the Initializing state and restore axis function.
Configuring State
Once a CIP Motion I/O connection has been made to the device, the controller
begins to send configuration data using the connection's service channel. At this
time the axis state transitions from Unconnected to Configuring. The axis state
will remain in the Configuring state until the values of all applicable configuration
attributes in the device have been set for this axis instance, or until a configuration
fault occurs, in which case the axis state transitions to the Faulted state.
Synchronizing State
If the device has not been synchronized to the controller by the time the controller
has completed the axis configuration process, the axis state transitions to the
Synchronizing state. The axis state will remain in the Synchronizing state until the
device has been successfully synchronized as indicated by a successful Group_Sync
service response from the device, or a time limit (~60 seconds) is reached, in which
case the controller closes the connection and starts the Initialization process over
again.
After configuring the axis and synchronizing the device to the controller, the
controller checks the status of all other axes in the Motion Group. If there are any
other axes in the Motion Group that are still being configured or synchronized,
the Axis State will transition to Waiting for Group. Cyclic data exchange over the
CIP Motion connection does not occur until all axes in the Motion Group are
configured and synchronized. Once all axes in the Motion Group are configured
and synchronized, the CIP Axis State transitions to the current Axis State
attribute value in the device, typically Pre-Charge or Stopped.
See also
Exceptions on page 47
Torque Control Behavior Torque is generally proportional to acceleration and to the torque producing
motor current, Iq. The purpose of the Torque Control structure is to combine
input signals to create a Torque Reference. The Torque Reference, from a variety
of sources, is based on the Control Mode. It applies various filters and
compensation algorithms to the Torque Reference to create a Filtered Torque
Reference.
The Filtered Torque Reference signal is scaled by the reciprocal of the torque
constant, Kt, of the motor to become the Iq Current Command input to the
current loop. Because the motor current is also per unitized to the '% Rated'
current of the motor, the torque constant, Kt, is nominally 1. In other words, in
general it is assumed that 100% rated current produces 100% rated torque.
See also
Torque Input Sources The Torque Control model can take input from a variety of sources depending on
the Control Mode. Input to the Torque Reference path can come through the
cyclic Torque Command or Torque Trim signal in Torque Control mode. In
Position or Velocity Control mode, torque input is derived from the outer velocity
loop or acceleration loop by bringing in the resulting acceleration signals and
scaling these signals into equivalent torque.
Because the acceleration input signals into the Torque Control section are
expressed in units of acceleration, a scaling factor, Kj, is needed to convert
acceleration units to torque % Rated Torque units. This scaling factor, when
properly configured, represents the total System Inertia or mass of the system that
includes the motor and the load and has the effect of canceling the effects the
system inertia/mass has on control loop response and loop gain settings.
Because the torque units are expressed as % of Rated Torque of the motor, the
units for the System Inertia attribute are % Rated per Motor Units/Sec2.
See also
Inertia Compensation Inertia compensation features are included in the Torque Control behavior
model.
Backlash Compensation
If the Velocity Control loop is tuned for peak performance with the load applied,
the axis will be, at best, under-damped and, at worst, unstable in the condition
where the gear teeth are not engaged. In the worst case scenario, the motor axis
and the input gear oscillates wildly between the limits imposed by the output gear
teeth. The net effect is a loud buzzing sound when the axis is at rest, commonly
referred to as 'gearbox chatter'. If this situation persists, the gearbox will wear out
prematurely. To prevent this condition, the conventional approach is to de-tune
the velocity loop so that the axis is stable without the gearbox load applied.
Unfortunately, system performance suffers.
The reason for the tapered profile, as opposed to a step profile, is that when the
position error exceeds the backlash distance a step profile would create a very large
discontinuity in the torque output. This repulsing torque tends to slam the axis
back against the opposite gear tooth and perpetuate the buzzing effect. The
tapered profile can be qualified to run only when the acceleration command or the
velocity command to the control loop structure is zero, for example, when not
commanding motion that would engage the teeth of the gearbox.
Inertia Observer
The Inertia Observer, when enabled, monitors the acceleration of the axis in
relationship to the torque producing current command, Iq Current Reference,
and estimates the total motor inertia.
The Total Inertia Estimate for the Inertia Observer is fed back to the Kj gain to
provide automatic gain control (AGC) with respect to load inertia. This feature
can be used to compensate for inertia variation without compromising system
performance. The Inertia Observer works on the premise that the motor and load
are not subject to externally applied torques or forces that could impact the
acceleration of the load. By contrast, the Load Observer in the Acceleration
Control behavior model works on the premise that changes in acceleration are due
to externally applied torques/forces on the motor and load. Thus, the operation of
these two observers are mutually exclusive; they should not be enabled at the same
time.
See also
Friction Compensation Friction Compensation applies a compensating directional torque or force to the
motor to overcome the effects of friction in the mechanical system, thus
minimizing the amount of control effort required. Individual attributes have been
defined to support compensation for static friction, sliding (Coulomb) friction,
and viscous friction. A compensation window attribute is also provided to
mitigate motor dithering associated with conventional friction compensation
methods.
It is not unusual for an axis to have enough static friction, commonly called
'sticktion', in Position Control applications that even with a significant position
error, the mechanical system refuses to budge. Of course, position integral gain can
be used to generate enough output to the drive to correct the error, but this
approach may not be responsive enough for the application. An alternative is to
use Static Friction Compensation to break the sticktion in the presence of a
non-zero position error. This is done by adding, or subtracting, a fixed torque
level, as determined by the Static Friction Compensation attribute, to the Torque
Reference signal value based on its current sign. This form of friction
compensation is applied only when the axis is static, for example, when there is no
change in the position command.
The Static Friction Compensation value must be just under the value that would
overcome the sticktion. A larger value results in axis 'dither', a phenomena
describing a rapid back and forth motion of the axis centered on the commanded
position as it overcompensates for the sticktion.
A non-zero Friction Compensation Window has the effect of softening the Static
Friction Compensation as it's applied to the Torque Reference and reducing the
dithering and hunting effects that it can create. This feature generally allows
higher values of Static Friction Compensation to be applied, resulting in better
point-to-point positioning.
See also
Torque filters The following filters can be applied to provide additional compensation and
control to the torque value.
Lead-Lag Filter
A lead-lag filter is provided in the torque reference path. This filter can be used in
the lead configuration to boost velocity or acceleration loop bandwidth, or in the
lag configuration to compensate the high frequency gain boost associated with
compliant load mechanics.
In this equation, Kn represents the Lead-Lag Filter Gain, or high frequency gain of
the filter (the low frequency gain is always 1), and wn represents the Lead-Lag
Filter Bandwidth associated with the pole of the filter:
When used as a lag filter (Kn < 1), this filter can be effective in compensating for
the gain boosting effect of natural mechanical resonance frequencies that are
within the acceleration/velocity loop bandwidth.
The Low Pass Filter is effective in resonance control when the natural resonance
frequency is much higher (>5x) than the control loop bandwidth. This filter
works by reducing the amount of high-frequency energy in the device output that
excite the natural resonance. The Low Pass Filter design can be single pole or
multiple poles. Care should be taken, however, to limit the amount of phase lag
introduced by this filter to the control loop to avoid potential instability.
Notch Filter
The notch filters are effective in resonance control when the natural resonance
frequency is higher than the control loop bandwidth. Like the Low Pass filter, the
notch filter works by significantly reducing the amount of energy in the device
output that can excite the natural resonance. It can be used even when the natural
resonance frequency is relatively close to the control loop bandwidth. That is
because the phase lag introduced by the notch filter is localized around the notch
frequency. For the notch filter to be effective, the Notch Filter Frequency has to be
set very close to the natural resonance frequency of the load.
See also
Torque Limiter After undergoing friction compensation and filtering the Torque Reference signal
passes through a limiter to produce the Limited Torque Reference signal. The
Torque Limiter applies a torque limit to the signal that is based on the sign of the
torque reference signal input and the state of the axis.
During normal operation it is the Torque Limit – Positive and Torque Limit –
Negative attributes, set by the user, that are applied to the torque reference signal.
When the axis is commanded to stop as part of a disable request or major fault
condition, the device applies the Stopping Torque Limit.
Also included with the torque limiter is a built-in Torque Rate of Change Limit.
This feature limits the rate of change of the torque reference output.
See also
Torque to Current Scaling The final result of all this torque signal filtering, compensation, and limiting
functionality is the Filtered Torque Reference signal. When the signal is scaled by
the reciprocal of the Torque Constant of the motor, 1/Kt, it becomes the torque
producing Iq Current Command signal to the current loop.
Ideally, the relationship between motor torque and motor current is independent
of position, time, current, and environmental conditions, the 1/Kt scaling has a
nominal value of 1, so that 100% rated torque translates to 100% rated current. In
practice, this may not be the case. Compensation can be applied to the 1/Kt value
to address these issues at the drive vendors' discretion.
Cogging Compensation
See also
Velocity Control Behavior In Velocity Control mode, there are two operative control methods supported,
Closed Loop Velocity Control and Open Loop Frequency Control.
Targeted for applications that require tight speed regulation. The following
diagram provides an overview of this method.
Associated with drives that do not have a current control loop and typically drive
an induction motor, also known as Volts/Hertz or Variable Frequency Drives
(VFDs). The following diagram provides an overview of this method.
See also
Closed Loop Velocity Control The Closed Loop Velocity Control method is targeted for applications that
require tight speed regulation. The command input to the velocity loop can be
derived directly from the Velocity Command of the Command Generator when
configured for Velocity Control Mode or from the Position Loop Output when
configured for Position Control Mode.
When serving as an outer velocity loop in Velocity Control Mode, the device
applies the Velocity Command input to the velocity command summing junction
to generate the Velocity Reference signal into a PI regulator. Contributing to the
velocity command summing junction also is the Velocity Trim input, which can
When serving as an inner velocity loop in Position Control Mode, the device
applies the Position Loop Output signal to the input of the velocity command
summing junction. Input signals that are not applicable to the configured control
mode are generally set to zero.
Velocity Limiter
The output of the velocity command summing junction signal passes through a
limiter to produce the Velocity Reference signal into the velocity loop. The
Velocity Limiter applies a directional velocity limit, either Velocity Limit - Pos or
Velocity Limit - Neg, to the velocity command signal input that is based on the
sign.
Feedback to the PI regulator can be derived from either of the two available
feedback transducers, Feedback 1 or Feedback 2. Which feedback source is used by
the loop is governed by the Feedback Mode enumeration. If Feedback Mode is No
Feedback, indicating sensorless operation, the Velocity Feedback signal is
estimated by the Sensorless Velocity signal generated by the sensorless control
algorithm. If an optional Load Observer is configured for Velocity Estimate
operation, the Velocity Feedback signal is the Load Observer Velocity Estimate.
A low pass filter can be optionally applied to the velocity error signal generated by
the velocity loop summing junction. The output of this filter becomes the Velocity
Error signal that is subsequently operated on by the velocity loop PI control
algorithm. When used, the filter is typically set between 5 to 10 times the velocity
loop bandwidth. It is recommended that this filter be a two pole IIR filter to
maximum its effectiveness at quantization noise filtering.
Velocity Gains
The velocity loop generates a Velocity Loop Output signal to the next inner loop
through a PI control loop structure. The Proportional Gain of the controller sets
the unity gain bandwidth of the velocity loop in radians/second, while the Integral
Gain is used to drive the Velocity Error signal to zero to compensate for any static
and quasi-static torque or forces applied to the load. The integrator path includes a
Proportional Gain so that units of the Integral Gain represent the bandwidth of
the integrator in radians/second.
The integral section of the velocity regulator includes an anti-windup feature. The
anti-windup feature automatically holds the regulator's integral term when a limit
The integrator may also be configured for integrator hold operation. When the
Integrator Hold attribute is set true, the regulator holds the integrator from
accumulating while the axis is being commanded to move. This behavior is helpful
in point-to-point positioning applications.
An automatic preset feature of the velocity regulator's integral term occurs when a
transition is made from a Torque Control mode to speed control, by using the
Control Mode selection parameter. Upon transition to speed mode, the speed
regulator's integral term is preset to the motor torque reference parameter. If the
speed error is small, this provides a 'bumpless' transition from the last torque
reference value present just prior to entering speed mode.
Negative Feedforward
Aside from the normal PI control elements, a negative feedforward gain (Knff ) is
provided to adjust the time response of the velocity regulator. Knff has a range of
0…100%, where 0 disables the function. A value of 30% results in little noticeable
overshoot in the speed response to a step input. This can be easily observed when
the motor speed is ramped to zero. The effect of negative feedforward is to
eliminate backup of the motor shaft. The Knff gain setting has no effect on the
stability of the speed regulator. A disadvantage of by using negative feedforward is
that it results in a time lag in feedback response to a reference ramp input.
Velocity Droop
Another feature of the velocity regulator is the velocity droop function. The
velocity error input to the integral term is reduced by a fraction of the velocity
regulator's output, as controlled by the droop gain setting, Kdr. As torque loading
on the motor increases, actual motor speed is reduced in proportion to the droop
gain. This is helpful when some level of compliance is required due to rigid
mechanical coupling between two motors.
Acceleration Feedforward
The velocity loop requires a non-zero velocity loop output to generate steady- state
axis motor acceleration. To provide the non-zero output from the drive to the
motor, a non-zero velocity error is generally required. In Position Control
applications, this non-zero velocity error translates to a non-zero position loop
error.
Because many closed loop motion control applications require near zero control
loop error, this behavior is not desirable. Again, the position and velocity loop
error could be reduced by applying the velocity integral gain control as described
above, but the integrator action is still too slow to be very effective. The preferred
approach with superior dynamic response is to use Acceleration Feedforward.
See also
Open Loop Frequency Control Another Velocity Control method is the open loop Frequency Control method
associated with so called Volts/Hertz or Variable Frequency Drives (VFDs) that
do not have a current control loop and typically drive an induction motor.
Velocity control with this method is achieved by controlling the voltage and
frequency output of the drive device in some manner where voltage is generally
proportional to frequency. For an induction motor, the velocity of the motor is
determined by the Output Frequency of the drive device divided by the Motor
Pole count. This control method is applicable to Velocity Control applications
that do not require tight speed regulation and therefore do not require a feedback
device.
There are a number of attributes that are used to specify the relationship the drive
device uses between output frequency (speed) and output voltage for a given
(induction) motor.
The Break Frequency and Break Voltage attributes define the point on the
Volts/Hertz curve below which the Start Boost feature is applied. As the name
indicates, Start Boost is used to provide a non-zero output voltage to the motor at
stand-still to assist startup.
The contribution of Start Boost to the output voltage of the drive device tapers off
to zero when the motor reaches the Break Frequency. Above the break point,
output voltage and output frequency follow a linear slope to the point defined by
the Motor Rated Frequency and Motor Rated Voltage. From this point on, the
Volts/Hertz curve follows another linear slope to the point defined by the Max
Frequency and Max Voltage attributes. This segment of the Volts/Hertz curve
allows for operation above the rated frequency and voltage of the motor in
applications where that is required.
Sensorless Vector is an alternative Velocity Control Method that does not require
configuration of a Volts/Hertz curve. Instead, by knowing the Stator Resistance
and Leakage Inductance of the motor, the drive device can calculate the
appropriate Output Voltage required for a given Output Frequency. This method
provides better low speed Velocity Control behavior than by using the Basic
Volts/Hertz method.
Slip Compensation
Velocity Droop
Another feature defined for the Frequency Control method is the droop function.
The droop function reduces the velocity reference by a scaled fraction of the
torque producing current, Iq, as controlled by the droop gain setting, Kdr. As
torque loading on the motor is increased, actual motor speed is reduced in
proportion to the droop gain. This is helpful when some level of compliance is
required when performing torque sharing between two motors on a common load.
See also
Each attribute table begins with the attribute name as a heading. The tag,
GSV/SSV, and MSG names for each of these attributes are the same as the
attribute name listed, but with the spaces removed. For example, Inhibit Axis
would be InhibitAxis.
DB = Motion Database
Indicates that the default value comes from the database.
FD = Factory Default computed value
∞ = max float = 3.402.... x 1038
0+ = min float = 1.2.... x 10-38
maxpos = 231/Conversion Constant
maxspd = 1000 * maxpos
Default, Minimum, Maximum minspd = minfloat
Range Limits maxacc = 1000 * maxspd
minacc = minfloat
maxint = 215 - 1
maxdint = 231 - 1
- (dash) = Not Applicable
N/A = Not Applicable
Defaults = Unless otherwise specified, all optional attributes default to 0. All
reserved and otherwise unused bits and enumerations are set to 0.
See also
Attribute Units Attribute Units define the unit nomenclature found in the Semantics of Values
column for many of the Motion Control Axis Attributes. In general, attribute
values are specified in units that are relevant to motion control engineers.
See also
CIP Data Types This table provides descriptions of the CIP Data Types related to the CIP Motion
Control Axis.
See also
Device Function Codes The variations in Control Mode and Control Method result in a set of basic
Device Function Codes that help organize the many attributes of the Motion
Control Axis. Device Function Codes are designated by using a letter identifier or
a combination that you can use to determine what attributes are required for
implementation of a given CIP Motion device. The list of Device Function Codes
is as follows:
Using combinations of these letters, a specific class of CIP Motion devices can be
designated for the purposes of identifying applicable attributes. For example, 'FV'
would refer to the class of all velocity controlled drives, either vector controlled or
frequency controlled. Here are some combinations that appear frequently:
Conditional Implementations
See also
Required vs. Optional Axis In the attribute tables, attributes and services are defined as Required (R) or
Optional (O). Required attributes and services must be supported in the
Attributes implementation of the object. Optional attributes and services may or may not be
supported in the implementation and are left to the discretion of the device
manufacturer.
Required Implementation
If an attribute is marked as Required for a given Device Function Code then the
controller implementation, including configuration and programming the
software, support that attribute if the end device is intended to operate in that
mode. For example, an attribute marked as Required for Device Function Code 'V'
is supported by any controller that intends to interface to a CIP Motion device
that supports Velocity Loop operation.
In some cases an attribute or service may not even be applicable to a given Device
Function Code. This situation is implied when the attribute is defined as neither
Required nor Optional for that code. The Required and Optional classification of
a given attribute can therefore be used in configuration software design to
determine if the attribute is applicable and requires user entry.
Conditional Implementation
In some cases attributes have different rules for different conditions; a motor
attribute might be Required for Permanent Magnet Motors but Optional for
Induction Motors. For that case, a C would be placed under the supported Device
Function Codes and the Conditional Implementation column would show the
differentiation between the motor types.
For some attributes, there are conditional implementation rules that extend
beyond the Device Function Code. These rules are specified in the Conditional
Implementation column of the attribute table.
Velocity Control, or Torque Control and the device supports Permanent Magnet
motors. The attribute is not applicable "-" for a Bus Power Converter or a
Feedback Only device or a drive that does not support a PM motor.
To get details about how to specify the attribute, refer to the attributes list for the
functional category. For this example, PM Motor Resistance is a member of the
General Permanent Magnet Motor Attributes category. The following table
provides an example of the details information:
When you are reviewing the tables for an attribute remember that Vendor Specific
attributes, attribute enumerations, and bits, are Optional by definition. Attributes
that have Optional enumerations or bit maps are designated so in the Condition
Implementation column. Details about Optional and Required support for the
individual enumerations or bits for these attributes can be found in the detailed
attribute behavior tables.
The software queries the specific drive profile, Add-on Profile (AOP), to
determine if the Optional attributes listed in the table are supported. Attributes
that are marked with an AOP in the Conditional Implementation column have
semantics with additional, drive specific, optional behavior that is queried.
If the conditional implementation column reads "Derived", it means that the value
for an attribute is determined (derived) by the controller based on the value of
another attribute. In this case, the current attribute follows the conditional
implementation rules of the attribute from which it is derived. Derived attributes
do not need to be downloaded to the controller but do need to be supported by
setting the appropriate bits in the Drive Set Attribute Update Bits attribute, if
applicable.
The following table identifies the key abbreviations used in the conditional
column of the attributes tables and provides a description of the condition it
represents.
Key Description
AOP Add-on Profile. Logix Designer component that can be separately installed and used for
configuring one or more modules.
Co Controller only attribute (controller attribute that resides only in controller)
CScale Motion Scaling Configuration set to Controller Scaling
Derived Implementation rules follow another attribute
Drive Scaling Drive device supports drive scaling functionality
Dr Drive replicated attribute (controller attribute that is replicated in drive)
DScale Motion Scaling Configuration set to Drive Scaling
DSL Hiperface DSL (feedback type)
E Encoder-based control, a feedback device is present
!E Encoderless or sensorless control, a feedback device in not present
ED EnDat 2.1 and EnDat 2.2 (feedback type)
HI Hiperface (feedback type)
IM Rotary or Linear Induction Motor (motor type)
IPM Rotary or Linear Interior Permanent Magnet motor (motor type)
Linear Absolute Feedback Unit - meter; Feedback n Startup Method- absolute
Linear Motor Linear PM motor or Linear Induction motor (motor type)
LT LDT or Linear Displacement Transducer (feedback type)
NV Motor NV or Drive NV (motor data source)
O-Bits Optional bits associated with bitmapped attribute
O-Enum Optional enumerations associated with attribute
PM Rotary or Linear Permanent Magnet motor (SPM or IPM) (motor type)
Rotary Absolute Feedback Unit - rev; Feedback n Startup Method- absolute
Rotary Motor Rotary PM motor or Rotary Induction motor (motor type)
RS Resolver (feedback type)
Safety only Applicable to Integrated Motion on the EtherNet/IP network safety devices only
SC Sine/Cosine (feedback type)
SL Stahl SSI (feedback type)
SPM Rotary or Linear Surface Permanent Magnet motor (motor type)
SS SSI (feedback type)
TM Tamagawa (feedback type)
TP Digital Parallel (feedback type)
TT Digital AqB (feedback type)
See also
Identify Motion Axis The following table provides an alphabetical list of all Motion Axis Attributes
specific to the CIP Drive data type. The table identifies whether the attribute is
Attributes Based on Device Required (R), Optional (O), or Conditional (C), in implementation based on the
Function Codes Device Function Code. Attributes that are not applicable for a device function
code are denoted by a dash (-).
The C/D column states whether the attribute is replicated in the drive.
1350 Set Induction Motor Rotor Resistance - - - O O O O Yes Ind Motor only
1348 Set Induction Motor Stator Leakage Reactance - - - O O O O Yes Ind Motor only
1347 Set Induction Motor Stator Resistance - - - R R R R Yes Ind Motor only
20 Set Inhibit Axis R R R R R R R
60 Get T Interpolated Actual Position - - R - R R R E
101 Get T Interpolated Command Position - - - - R R - E
108 Set Interpolated Position Configuration - - R - R R R E
59 Set T Interpolation Time - - R - R R R E
636 Get T Inverter Capacity - - - R R R R Yes
647 Set Inverter Overload Action - - - O O O O Yes Optional Enumeration
699 Set Inverter Thermal Overload User Limit - - - O O O O Yes
1338 Set Linear Motor Damping Coefficient - - - O O O O Yes Linear Motor only
2313 Set Linear Motor Integral Limit Switch - - - O O O O Yes Linear Motor only
1336 Set Linear Motor Mass - - - - O O O Yes Linear Motor only
1337 Set Linear Motor Max Speed - - - O O O O Yes Linear Motor only
See also
Attribute Conversion from The following table illustrates the methods used to convert a L5K file from a
Logix Designer project that uses an existing Allen-Bradley® SERCOS drive to a
SERCOS to Integrated comparable CIP Motion compliant drive.
Motion on the Ethernet/IP
Network
SERCOS Attribute Name L5K Example CIP Axis Attribute Name Conversion Method
MotionGroup "MyGroup" MotionGroup Direct
MotionModule "SercosDrive:Ch13" MotionModule Direct
RotationalPosResolution 200000 MotionResolution Direct
ConversionConstant 200000 ConversionConstant Direct
OutputCamExecutionTargets 0 OutputCamExecutionTargets Direct
PositionUnits "Position Units" PositionUnits Direct
AverageVelocityTimebase 0.25 AverageVelocityTimebase Direct
RotaryAxis Linear RotaryAxis Direct
PositionUnwind 200000 PositionUnwind Direct
HomeMode Active HomeMode Direct
HomeDirection Bi-directional Forward HomeDirection Direct
HomeSequence Immediate HomeSequence Direct
HomeConfigurationBits 16#0000_0000 HomeConfigurationBits Direct
HomePosition 0 HomePosition Direct
HomeOffset 0 HomeOffset Direct
HomeSpeed 0 HomeSpeed Direct
HomeReturnSpeed 0 HomeReturnSpeed Direct
MaximumSpeed 70.833336 MaximumSpeed Direct
MaximumAcceleration 14025.113 MaximumAcceleration Direct
MaximumDeceleration 14025.113 MaximumDeceleration Direct
ProgrammedStopMode Fast Stop ProgrammedStopMode Direct
MasterInputConfigurationBits 1 MasterInputConfigurationBits Direct
MasterPositionFilterBandwidth 0.1 MasterPositionFilterBandwidth Direct
AxisConfiguration
AxisType Servo FeedbackConfiguration Enum Mapping
AxisConfiguration
ServoLoopConfiguration Position Servo FeedbackConfiguration Enum Mapping
FaultConfigurationBits 32 ExceptionAction Enum Mapping
Enum to Attr ID
AxisInfoSelect1 <none> CyclicReadUpdateList Element 0
SERCOS Attribute Name L5K Example CIP Axis Attribute Name Conversion Method
Enum to Attr ID
AxisInfoSelect2 <none> CyclicReadUpdateList Element 1
VelocityFeedforwardGain 0 VelocityFeedforwardGain Direct
AccelerationFeedforwardGain 0 AccelerationFeedforwardGain Direct
PositionProportionalGain 528.1571 PositionLoopBandwidth 1/2p
PositionIntegralGain 0 PositionIntegratorBandwidth 1/2p * 1000/Kpp
VelocityProportionalGain 1352.0822 VelocityLoopBandwidth 1/2p
VelocityIntegralGain 0 PositionIntegratorBandwidth 1/2p * 1000/Kpv
Conversion Const/Drive
TorqueScaling 0.01749257 SystemInertia Res
OutputLPFilterBandwidth 0 TorqueLPFilterBandwidth Direct
PositionIntegratorControl Bit 0 Mapping
IntegratorHoldEnable Enabled VelocityIntegratorControl Bit 0 Mapping
MaximumPositiveTravel 0 MaximumPositiveTravel Direct
MaximumNegativeTravel 0 MaximumNegativeTravel Direct
PositionErrorTolerance 0.3155627 PositionErrorTolerance Direct
PositionLockTolerance 0.01 PositionLockTolerance Direct
VelocityOffset 0 VelocityOffset Direct
TorqueOffset 0 TorqueOffset Direct
FrictionCompensation 0 FrictionCompensation Direct
FrictionCompensationWindow 0 FrictionCompensationWindow Direct
BacklashStabilizationWindow 0 BacklashStabilizationWindow Direct
BacklashReversalOffset 0 BacklashReversalOffset Direct
HardOvertravelFaultAction Disable Drive CIPAxisExceptionAction Enum Mapping
SoftOvertravelFaultAction Disable Drive MotionExceptionAction Enum Mapping
PositionErrorFaultAction Disable Drive CIPAxisExceptionAction Enum Mapping
FeedbackFaultAction Disable Drive CIPAxisExceptionAction Enum Mapping
FeedbackNoiseFaultAction Disable Drive CIPAxisExceptionAction Enum Mapping
TestIncrement 0 TestIncrement Direct
TuningTravelLimit 0 TuningTravelLimit Direct
TuningSpeed 0 TuningSpeed Direct
TuningTorque 100 TuningTorque Direct
DampingFactor 0.8 DampingFactor Direct
DriveModelTimeConstant 2.89E-04 DriveModelTimeConstant Direct
PositionServoBandwidth 84.058815 N/A
VelocityServoBandwidth 215.19055 N/A
TuningConfigurationBits 16#0000_0000 TuningConfigurationBits Direct
TorqueLimitSource Not Limited TorqueLimitSource Direct
DriveUnit Motor Rev MotionUnit Direct
PositionDataScaling 10 N/A
PositionDataScalingFactor 1 N/A
PositionDataScalingExp 0 N/A
SERCOS Attribute Name L5K Example CIP Axis Attribute Name Conversion Method
VelocityDataScaling 2 N/A
VelocityDataScalingFactor 1 N/A
VelocityDataScalingExp 0 N/A
AccelerationDataScaling 2 N/A
AccelerationDataScalingFactor 1 N/A
AccelerationDataScalingExp 0 N/A
TorqueDataScaling 0 N/A
TorqueDataScalingFactor 1 N/A
TorqueDataScalingExp 0 N/A
DrivePolarity Positive MotionPolarity Enum Mapping
MotorFeedbackType "SRM" Feedback1Type Enum Mapping
MotorFeedbackResolution 1024 Feedback1CycleResolution Direct
AuxFeedbackType "<NA>" Feedback2Type Enum Mapping
AuxFeedbackResolution 4000 Feedback2CycleResolution Direct
MotorFeedbackUnit Rev Feedback1Unit Enum Mapping
AuxFeedbackUnit Rev Feedback2Unit Enum Mapping
OutputNotchFilterFrequency 0 TorqueNotchFilterFrequecy Freq Unit Scaling
VelocityDroop 0 VelocityDroop Direct
VelocityLimitBipolar 83.333336 N/A
AccelerationLimitBipolar 33000.266 N/A
TorqueLimitBipolar 288.62973 N/A
VelocityLimitPositive 83.333336 VelocityLimitPositive Direct
VelocityLimitNegative -83.333336 VelocityLimitNegative Direct
VelocityThreshold 0 VelocityThreshold Direct
VelocityWindow 1 VelocityWindow Direct
VelocityStandstillWindow 1 VelocityStandstillWindow Direct
AccelerationLimitPositive 33000.266 AccelerationLimit Direct
AccelerationLimitNegative -33000.266 DecelerationLimit Direct
TorqueLimitPositive 288.62973 TorqueLimitPositive Direct
TorqueLimitNegative -288.62973 TorqueLimitNegative Direct
TorqueThreshold 0 TorqueThreshold Direct
DriveThermalFaultAction Disable Drive CIPAxisExceptionAction Enum Mapping
MotorThermalFaultAction Disable Drive CIPAxisExceptionAction Enum Mapping
DriveEnableInputFaultAction Disable Drive CIPAxisExceptionAction Enum Mapping
StoppingTorque 288.62973 StoppingTorque Direct
StoppingTimeLimit 10 StoppingTimeLimit Direct
BrakeEngageDelayTime 0 BrakeEngageDelayTime Direct
BrakeReleaseDelayTime 0 BrakeReleaseDelayTime Direct
PowerSupplyID "2094-AC05-M01" (Module Configuration)
BusRegulatorID "<none>" (Module Configuration)
PWMFrequencySelect High Frequency N/A
SERCOS Attribute Name L5K Example CIP Axis Attribute Name Conversion Method
LoadInertiaRatio 0 LoadInertiaRatio Direct
AmplifierCatalogNumber "2094-AC05-M01" (Module Configuration)
MotorCatalogNumber "MPL-A310P-M" MotorCatalogNumber Direct
AuxFeedbackRatio 1 FeedbackUnitRatio 1/x
ContinuousTorqueLimit 100 MotorOverloadLimit Direct
ResistiveBrakeContactDelay 0 ResistiveBrakeContactDelay Direct
MaximumAccelerationJerk 2776994.8 MaximumAccelerationJerk Direct
MaximumDecelerationJerk 2776994.8 MaximumDecelerationJerk Direct
DynamicsConfigurationBits 7 DynamicsConfigurationBits Direct
PhaseLossFaultAction Shutdown CIPAxisExceptionAction Enum Mapping
HomeTorqueLevel 0 HomeTorqueLevel Direct
InputPowerPhase Three-Phase (Module Configuration)
Drive Supported Optional The following tables describe the optional attributes that are supported for the
Kinetix 350, Kinetix 5500, Kinetix 5700, Kinetix 6500, PowerFlex 755 Standard,
Attributes and the PowerFlex 755 Safety drives.
Key Description
Y The attribute/enum/bit is supported.
Y# The attribute was not supported until the major revision of the drive.
(indicated by the # value)
N The attribute/enum/bit is NOT supported.
R The attribute is required.
O The attribute is optional.
G Regenerative (Active) AC/DC Converters (No Control Mode, No Control Method)
N Non-regenerative (Passive) AC/DC and DC/DC Converters (No Control Mode, No Control Method
E Encoder, Feedback Only (No Control Mode, No Control Method)
P Position Loop (Position Control Mode, Closed Loop Vector Control Method)
V Velocity Loop (Velocity Control Mode, Close Loop Vector Control Method)
T Torque Loop (Torque Control Mode, Closed Loop Vector Control Method)
F Frequency Control (Velocity Control Mode, Frequency Control Method)
C/D Controller/Device Replicated Attribute
AOP Special device specific semantics needed from AOP
Co Controller only attribute (controller attribute that resides only in controller)
C/D Yes = The attribute is replicated in the drive
CScale Motion Scaling Configuration set to Controller Scaling
Derived Implementation rules follow another attribute
Dr Drive replicated attribute (controller attribute that is replicated in drive)
Drive Scaling Drive device supports drive scaling functionality
DScale Motion Scaling Configuration set to Drive Scaling
ED EnDat 2.1 and EnDAT 2.2 (feedback type)
E Encoder-based control, a feedback device is present
!E Encoderless or sensorless control, a feedback device in not present
HI Hiperface (feedback type)
IM Rotary or Linear Induction Motor (motor type)
Linear Absolute Feedback Unit - meter; Feedback n Startup Method- absolute
Linear Motor Linear PM motor or Linear Induction motor (motor type)
LT LDT or Linear Displacement Transducer (feedback type)
Key Description
NV Motor NV or Drive NV (motor data source)
O-Bits Optional bits associated with bit mapped attribute
O-Enum Optional enumerations associated with attribute
PM Rotary or Linear Permanent Magnet motor (motor type)
Rotary Absolute Feedback Unit - rev; Feedback n Startup Method - absolute
Rotary Motor Rotary PM motor or Rotary Induction motor (motor type)
See also
Kinetix 350 Drive Module A Kinetix 350 drive module supports the following optional attributes and
corresponding control mode functionalities:
Optional Attributes
ID Access Attribute Name N E F P V T Conditional Implementation
Rule
367 Get Acceleration Fine Command - - Y Y Y
485 Set Acceleration Limit - N N N N
482 Get Acceleration Reference - - N N N
481 Set Acceleration Trim - - N N N
1376 Set Actuator Diameter N N N N N DScale
1377 Set Actuator Diameter Unit N N N N N DScale
1374 Set Actuator Lead N N N N N DScale
1375 Set Actuator Lead Unit N N N N N DScale
1373 Set Actuator Type N N N N N DScale
732/267 Get Analog Input 1 Y - N N N N
733/268 Get Analog Input 2 Y - N N N N
734 Set Analog Output 1 Y - N N N N
735 Set Analog Output 2 Y - N N N N
Kinetix 5500 Hardwired STO The hardwired Kinetix 5500 drive modules include the following catalog
numbers:
Drive Module Optional
Attributes • 2198-H003-ERS, Kinetix 5500, 1A, 195-528 Volt, Safe Torque Off Drive
• 2198-H008-ERS, Kinetix 5500, 2.5A, 195-528 Volt, Safe Torque Off Drive
• 2198-H015-ERS, Kinetix 5500, 5 A, 195 – 528 Volt, Safe Torque Off
Drive
• 2198-H025-ERS, Kinetix 5500, 8A, 195- 528 Volt, Safe Torque Off Drive
• 2198-H040-ERS, Kinetix 5500, 13 A, 192-528 Volt, Safe Torque Off Drive
• 2198-H070-ERS Kinetix 5500, 23 A,195–528 Volt, Safe Torque Off Drive
These drive modules support the optional attributes and corresponding control
mode functionality as indicated in the following table:
Kinetix 5500 Integrated STO The integrated Kinetix 5500 drive modules include the following catalog
numbers:
Drive Module Optional
Attributes • 2198-H003-ERS2, Kinetix 5500, 1A, 195-528 Volt, CIP Safe Torque Off
Drive
• 2198-H008-ERS2, Kinetix 5500, 2.5A, 195-528 Volt, CIP Safe Torque Off
Drive
• 2198-H015-ERS2, Kinetix 5500, 5 A, 195 – 528 Volt, CIP Safe Torque
Off Drive
• 2198-H025-ERS2, Kinetix 5500, 8A, 195- 528 Volt, CIP Safe Torque Off
Drive
• 2198-H040-ERS2, Kinetix 5500, 13 A, 192-528 Volt, CIP Safe Torque Off
Drive
• 2198-H070-ERS2 Kinetix 5500, 23 A,195–528 Volt, CIP Torque Off
Drive
These drive modules support the optional attributes and corresponding control
mode functionality as indicated in the following table:
Kinetix 5700 Safety Drive The Kinetix 5700 single-axis and dual-axis model drives include the following
catalog numbers:
Module Optional Attributes
• 2198-S086-ERS3, 43A, 458-747 Volt DC, Network Safety STO Drive
• 2198-S130-ERS3, 65A, 458-747 Volt DC, Network Safety STO Drive
• 2198-S160-ERS3, 85A, 458-747 Volt DC, Network Safety STO Drive
• 2198-D006-ERS3, 2.5A, 458-747 Volt DC, Network Safety STO Drive
• 2198-D0012-ERS3, 5A, 458-747 Volt DC, Network Safety STO Drive
• 2198-D020-ERS3, 8A, 458-747 Volt DC, Network Safety STO Drive
• 2198-D032-ERS3, 13A, 458-747 Volt DC, Network Safety STO Drive
• 2198-D057-ERS3, 23A, 458-747 Volt DC, Network Safety STO Drive
These drive modules support the optional attributes and corresponding control
mode functionality as indicated in the following table:
Kinetix 5700 Advanced Safety The Kinetix 5700 advanced safety drive modules include the following catalog
numbers:
Drive Module Optional
Attributes • 2198-S086-ERS4, 43A, Inverter, Advanced Safety Drive
• 2198-S130-ERS4, 65A, Inverter, Advanced Safety Drive
• 2198-S160-ERS4, 85A, Inverter, Advanced Safety Drive
• 2198-D006-ERS4, 2x2 5A, Dual-Axis Inverter, Advanced Safety Drive
These drive modules support the optional attributes and corresponding control
mode functionality as indicated in the following table:
Kinetix 5700 CIP Safety The Kinetix 5700 CIP Safety (EtherNet/IP) modules include these catalog
numbers:
(EtherNet/IP) Module Optional
Attributes • 2198-S263-ERS3 Kinetix 5700, 150A, 458-747 Volt DC, CIP Safety
(EtherNet/IP)
• 2198-S312-ERS3 Kinetix 5700, 192A, 458-747 Volt DC, CIP Safety
(EtherNet/IP)
These drive modules support the optional attributes and corresponding control
mode functionality as indicated in this table.
Kinetix 5700 CIP Advanced The Kinetix 5700 CIP Advanced Safety (EtherNet/IP) modules include these
catalog numbers:
Safety (EtherNet/IP) Module
Optional Attributes • 2198-S263-ERS4 Kinetix 5700, 150A, 458-747 Volt DC, CIP Advanced
Safety (EtherNet/IP)
• 2198-S312-ERS4 Kinetix 5700, 192A, 458-747 Volt DC, CIP Advanced
Safety (EtherNet/IP)
These drive modules support the optional attributes and corresponding control
mode functionality as indicated in this table.
Kinetix 5700 Regenerative Bus The Kinetix 5700 Regenerative Bus Supply modules include these catalog
numbers:
Supply Module Optional
Attributes • 2198-RP088 Kinetix 5700 Regenerative Bus Supply, 24kW, 35A / 88A
These drive modules support the optional attributes and corresponding control
mode functionality as indicated in this table.
Kinetix 6500 Drive Module The following table identifies the optional attributes and corresponding control
Optional Attributes mode functionality supported by a Kinetix 6500 drive module.
PowerFlex 527 Axis Instance The following table identifies the optional attributes and corresponding control
mode functionality supported by a PowerFlex 527 drive module.
Optional Attributes
ID Access Attribute N E F P V T Conditional Implementation
Rule
367 Get Acceleration Fine Command - - - Y Y N
485 Set Acceleration Limit - - N N N N
482 Get Acceleration Reference - - - N N N
481 Set Acceleration Trim - - - N N N
1376 Set Actuator Diameter - N N N N N DScale
1377 Set Actuator Diameter Unit - N N N N N DScale
1374 Set Actuator Lead - N N N N N DScale
1375 Set Actuator Lead Unit - N N N N N DScale
1373 Set Actuator Type - N N N N N DScale
836 Set Adaptive Tuning Configuration - - - N N N Vxx
844 Get Adaptive Tuning Gain Scaling Factor - - - N N N Vxx
732/267 Get Analog Input 1 N - Y Y Y N
733/268 Get Analog Input 2 N - Y Y Y N
734 Set Analog Output 1 N - Y Y Y N
735 Set Analog Output 2 N - N N N N
873 Set Auto Sag Configuration - - N N N N Vxx
874 Set Auto Sag Slip Increment - - N N N N Vxx
875 Set Auto Sag Slip Time Limit - - N N N N Vxx
876 Set Auto Sag Start - - N N N N Vxx
19 Set Axis Features R R R R R R O-Bits
0 = Fine Interpolation (Y)
1 = Registration Auto-rearm (Y)
2 = Alarm Log (Y)
5 = Hookup Test (Y)
6 = Commutation Test (Y)
7 = Motor Test (Y)
8 = Inertia Test (Y)
9 = Sensorless Control (Y)
10 = Drive Scaling (N)
11 = Ext. Event Block (N)
12 = Integer Cmd. Pos. (N)
13 = Ext. Motor Test (N)
763 Get Axis Safety Faults - N Y Y Y N V24
760 Get Axis Safety State - N Y Y Y N V24
761 Get Axis Safety Status - N Y Y Y N V24
825 Set Backlash Compensation Window - - - N - -
593 Set Brake Prove Ramp Time - - N N N N Vxx
594 Set Brake Slip Tolerance - - N N N N Vxx
PowerFlex 755 Standard Drive The following table identifies the optional attributes and corresponding control
mode functionality supported by a PowerFlex 755-EENET-CM drive module.
Module Optional Attributes
ID Access Attribute N E F P V T Conditional Implementation
367 Get Acceleration Fine Command - - - N N N
485 Set Acceleration Limit - - N N N N
482 Get Acceleration Reference - - - N N N
481 Set Acceleration Trim - - - N N N
1376 Set Actuator Diameter - N N N N N DScale
1377 Set Actuator Diameter Unit - N N N N N DScale
1374 Set Actuator Lead - N N N N N DScale
1375 Set Actuator Lead Unit - N N N N N DScale
1373 Set Actuator Type - N N N N N DScale
836 Set Adaptive Tuning Configuration - - - N N N V26/V27
844 Get Adaptive Tuning Gain Scaling Factor - - - N N N V26/V27
732/267 Get Analog Input 1 N - Y Y Y Y
733/268 Get Analog Input 2 N - Y Y Y Y
734 Set Analog Output 1 N - Y Y Y Y
735 Set Analog Output 2 N - Y Y Y Y
873 Set Auto Sag Configuration - - Y Y Y Y V26/V27
874 Set Auto Sag Slip Increment - - Y Y Y Y V26/V27
875 Set Auto Sag Slip Time Limit - - N N N N V26/V27
876 Set Auto Sag Start - - Y Y Y Y V26/27
PowerFlex 755 High Power, The following table identifies the optional attributes and corresponding control
Standard Drive Module Optional mode functionality supported by a PowerFlex 755-HiPwr-EENET-CM drive
Attributes module.
PowerFlex 755 Low Power, The following table identifies the optional attributes and corresponding control
Non-Network Safety Drive mode functionality supported by a PowerFlex 755-EENET-CM-S and PowerFlex
Module Optional Attributes 755-EENET-CM-S1 drive module.
PowerFlex 755 High Power, The following table identifies the optional attributes and corresponding control
Non-Network Safety Drive mode functionality supported by a PowerFlex 755-HiPwr-EENET-CM-S and
Module Optional Attributes PowerFlex 755-HiPwr-EENET-CM-S1 drive module.
PowerFlex 755 Low and High The following table identifies the optional attributes and corresponding control
mode functionality supported by a PowerFlex 755-EENET-CM-S3 and
Power, STO Only Network Safety
PowerFlex 755-HiPwr-EENET-CM-S3 drive module.
Drive Module Optional
Attributes
ID Access Attribute N E F P V T Conditional Implementation
Rule
367 Get Acceleration Fine Command - - - N N N
485 Set Acceleration Limit - - N N N N
482 Get Acceleration Reference - - - N N N
481 Set Acceleration Trim - - - N N N
836 Set Adaptive Tuning Configuration - - - N N N V26/V27
844 Get Adaptive Tuning Gain Scaling Factor - - - N N N V26/V27
732/267 Get Analog Input 1 N - Y Y Y Y
733/268 Get Analog Input 2 N - Y Y Y Y
734 Set Analog Output 1 N - Y Y Y Y
735 Set Analog Output 2 N - Y Y Y Y
873 Set Auto Sag Configuration - - Y Y Y Y V26/V27
874 Set Auto Sag Slip Increment - - Y Y Y Y V26/V27
875 Set Auto Sag Slip Time Limit - - N N N N V26/V27
876 Set Auto Sag Start - - Y Y Y Y V26/V27
19 Set Axis Features R R R R R R O-Bits
0 = Fine Interpolation (Y)
1 = Registration Auto-rearm (Y)
2 = Alarm Log (Y)
5 = Hookup Test (Y)
6 = Commutation Test (Y)
7 = Motor Test (Y)
8 = Inertia Test (Y)
9 = Sensorless Control (Y)
10 = Drive Scaling (N) Vxx
11 = Ext. Event Block (N) Vxx
12 = Integer Cmd. Pos (N) Vxx
13 = Ext. Motor Test (N) V29
14 = Control Mode Change (N) V26/V27
15 = Feedback Mode Change (N) Vxx
16 = Pass Bus Status (N) V26/V27
17 = Pass Bus Unload (N) V26/V27
18 = Ext. Speed for SPM (N)) V29
19 = Ext. Speed for IPM (N) V29
986 Get Axis Safety Data A - - N N N N V31
PowerFlex 755 Low and High The following table identifies the optional attributes and corresponding control
Power, Advanced Safety mode functionality supported by a PowerFlex 755-EENET-CM-S4 and
Network Safety Drive Module PowerFlex 755-HiPwr-EENET-CM-S4 drive module.
Optional Attributes
ID Access Attribute N E F P V T Conditional Implementation
Rule
MSG Instruction Access Only The following table lists the attributes that are available to a specific drive via
messaging. The P### references in the Conditional Implementation column refer
Attributes to the related PowerFlex drive parameter.
The CIP Axis Attributes let you configure motion-control system devices that
include feedback devices and drive devices. For drive devices, the CIP Axis
Attributes cover a wide range of drive types from simple variable frequency
(V/Hz) drives, to sophisticated position-control servo drives. Many commercial
drive products have axes that can be configured to operate in any one of these
different motion-control modes, depending on the specific application
requirements.
The CIP Axis Attributes are organized to address the broad range of functionality.
Because of the large number of attributes, they are organized by functional
category.
Acceleration Control Attributes on page 262 Frequency Control Configuration Attributes on page
279
Acceleration Control Configuration Attributes on page 264 Position Loop Attributes on page 281
Command Generator Configuration Attributes on page 266 Position Loop Configuration Attributes on page 284
Command Generator Signal Attributes on page 270 Torque/Force Control Configuration Attributes
on page 288
Command Reference Generation Attributes on page 266 Torque/Force Control Signal Attributes on page 298
Current Control Attributes on page 276 Velocity Loop Configuration Attributes on page 299
Current Control Configuration Attributes on page 276 Velocity Loop Signal Attributes on page 307
Frequency Control Signal Attribute on page 281
Data Attributes
Axis Info Attributes on page 312 CIP Axis Status Attributes on page 315
Axis Statistical Attributes on page 314 Event Capture Attributes on page 332
Drive Attributes
Drive General Purpose I/O Attributes on page 334 Power and Thermal Management Configuration
Attributes on page 342
Drive Output Attributes on page 341 Power and Thermal Management Status Attributes
on page 344
Autotune Configuration Attributes on page 354 Inertia Test Configuration Attributes on page 366
Hookup Test Configuration Attributes on page 363 Inertia Test Result Attributes on page 370
Hookup Test Result Attributes on page 364 Motor Test Result Attributes on page 373
APR Fault Attribute on page 376 Exception User Limit Configuration Attributes
on page 401
Axis Exception Action Configuration Attributes on page 378 Exception, Fault, and Alarm Attributes on page 405
Configuration Fault Attributes on page 386 Initialization Faults Attributes on page 408
Exception Factory Limit Info Attributes on page 392 Module/Node Fault and Alarm Attributes on page
411
Feedback Attributes
Feedback Attributes on page 415 General Feedback Info Attributes on page 432
Feedback Configuration Attributes on page 418 General Feedback Signal Attributes on page 433
Motion Control Configuration Attributes on page 433 Motion Dynamic Configuration Attributes on page
475
Motion Control Interface Attributes on page 440 Motion Homing Configuration Attributes on page
479
Motion Control Signal Attributes on page 448 Motion Planner Configuration Attributes on page 490
Motion Control Status Attributes on page 459 Motion Planner Output Attributes on page 495
Motion Database Storage Attributes on page 471 Motion Scaling Attributes on page 496
Motor Attributes
General Linear Motor Attributes on page 509 Interior Permanent Magnet Motor Attributes on page
529
General Motor Attributes on page 511 Linear PM Motor Attributes on page 526
General Permanent Magnet Motor Attributes on page 519 Load Transmission and Actuator Attributes on page
532
General Rotary Motor Attributes on page 522 Rotary PM Motor Attributes on page 534
Induction Motor Attributes on page 524
Safety Attributes
Axis Safety Status Attributes on page 537 Guard Safety Status Attributes on page 552
Start Inhibit Attributes on page 576 Stopping and Braking Attributes on page 556
Converter AC Line Monitoring Attributes on page 588 Converter AC Line Configuration Attributes on page
594
Converter AC Line Source Configuration Attributes on page 596 AC Line Condition Attributes on page 597
Converter Types on page 600 Converter Control Mode Attributes on page 601
Converter Bus Voltage Control Configuration Attributes Converter Bus Voltage Control Signal Attributes
on page 604 on page 607
Converter Current Reference Configuration Attributes on page Converter Current Reference Signal Attributes
610 on page 612
Converter Current Control Configuration Attributes on page Converter Current Control Signal Attributes on page
613 615
Converter Reactive Power Control Attributes on page 621 Converter Output Attributes on page 623
Keep the following items in mind while reviewing the attribute tables:
Item Description
SSV access rule If an attribute is marked with an SSV access rule, it is implied that the attribute
also supports GSV access.
Vendor specific bits Vendor specific bits, and enumerations provide space for drive vendors to provide
additional product features.
For Logix Designer software version 18, all defined vendor specific bits are
Rockwell Automation specific.
Optional attributes Unless otherwise specified, all optional attributes default to 0.
Attribute name The tag and GSV/SSV names for each of these attributes should be the same as the
attribute name but with spaces removed.
For example, Inhibit Axis would be InhibitAxis.
See also
Control Mode Attributes The following attribute tables contain control mode related attributes associated
with a Motion Control Axis Object instance.
Acceleration Control Attributes These are the acceleration related attributes associated with a Motion Control
Axis.
Acceleration Command
Command acceleration output from Fine Command Generator (if active) into
acceleration loop when configured for acceleration control.
Acceleration Trim
Acceleration Reference
Acceleration Feedback
Output of the Load Observer that, when the Load Observer block is enabled, is
applied to the acceleration reference summing junction. In the Load Observer
configuration, this signal compensates for disturbances to the load relative to an
ideal load model. When the Load Observer is configured to operate in
Acceleration Feedback Only mode, this signal is the estimated acceleration
feedback signal used to close the acceleration loop. When the Load Observer is
disabled, this signal is 0.
Product of the Load Observer Acceleration Estimate signal and the current
System Inertia value, Kj. In the Load Observer configuration, this signal represents
the estimated torque disturbances to the load relative to an ideal load model.
When the Load Observer is configured to operate in Acceleration Feedback Only
mode, this signal is an estimate of the applied motor torque. When the Load
Observer is disabled, this signal is 0.
See also
Acceleration Control These are the acceleration control configuration attributes associated with a
Motion Control Axis.
Configuration Attributes
Load Observer Configuration
The Load Observer Configuration attribute configures the operation of the Load
Observer. The Load Observer dynamically measures the active load torque applied
to the motor load for the purpose of load disturbance compensation. Selecting the
Velocity Estimate configures the observer to dynamically estimate velocity based
on an internal model of the motor and load. When Velocity Estimate is selected,
this signal is applied to the velocity loop to provide superior control loop
performance. The Velocity Estimate may be used in combination with the Load
Observer by selecting Load Observer with Velocity Estimate. The Acceleration
Feedback configuration applies acceleration feedback to the control loop structure
to improve stability and performance. In effect, Acceleration Feedback is like
adding virtual inertia to the motor thus reducing the Load Ratio.
The Load Observer Bandwidth attribute determines the proportional gain, Kop,
of the load observer. This value represents the unity gain bandwidth of the load
observer.
The Load Observer Integrator Bandwidth attribute determines the load observer
integral gain, Koi, that together with the Kop, multiplies the integrated error
signal within the observer. This value represents the bandwidth of the integrator
beyond which the integrator is ineffective. A value of 0 for this attribute disables
the integrator.
The Load Observer Feedback Gain attribute is a value that, when configured for
Acceleration Feedback, multiplies the Load Observer's acceleration output signal
before applying it as feedback to the acceleration reference summing junction. The
output of this gain term is the Load Observer Acceleration Estimate signal. If not
configured for Acceleration Feedback operation, this attribute has no effect.
Acceleration Limit
Deceleration Limit
Command Reference These are the command reference generation functionality of the device that
converts command position, velocity, acceleration, and torque data output from a
Generation Attributes
controller-based or device-based motion planner into corresponding command
references signals to the device's motor control structures. The command reference
generator functionality includes fine interpolators, signal selector switches,
dynamic limiters, command notch filters.
See also
Command Generator Configuration The following are the command generator configuration attributes associated
Attributes with a Motion Control Axis:
Skip Speed 1
The Skip Speed 1 attribute sets the central speed of a skip speed band within
which the device does not operate. The skip speed value is signed.
Skip Speed 2
The Skip Speed 2 attribute sets the central speed of a skip speed band within
which the device does not operate. The skip speed value is signed.
Skip Speed 3
The Skip Speed 3 attribute sets the central speed of a skip speed band within
which the device does not operate. The skip speed value is signed.
When operating in Closed Loop Velocity mode, the Fine Velocity Command
block also supports Skip Bands that are most frequently used in applications where
certain speeds excite mechanical resonance frequencies of the motor and load.
The Skip Speed Band attribute determines the speed window around a skip speed
that cannot be commanded. Any command set-point within this window is
adjusted by the Skip Speed block to fall at either the upper or lower Skip Speed
Band boundary value. The device can smoothly accelerate or decelerate through
the skip speed band based on the ramp generator block but may not operate at a
set speed within the band. The Skip Speed Band is distributed ½ above and ½
below the skip speed. This Skip Speed Band attribute applies to all skip speeds
supported in the device. A value of 0 for this attribute disables this feature.
The Ramp Velocity - Positive attribute is a positive value that defines the
maximum positive velocity command output of the Ramp Generator.
The Ramp Velocity - Negative attribute is a negative value that defines the
maximum negative velocity command output of the Ramp Generator.
Ramp Acceleration
The Ramp Acceleration attribute is a positive value that defines the maximum
acceleration (increasing speed) of the velocity command output by the Ramp
Generator.
Ramp Deceleration
The Ramp Deceleration attribute is a positive value that defines the maximum
deceleration (decreasing speed) of the velocity command output by the Ramp
Generator.
The Ramp Jerk Control attribute sets the percentage of accel or decel time that is
applied to the speed ramp as jerk limited S Curve based on a step change in
velocity. The S Curve time is added ½ at the beginning and ½ at the end of the
ramp. A value of 0 results in no S-Curve, for example, a linear acceleration or
deceleration ramp.
A value of 100% results in a triangular acceleration profile with the peak being the
configured ramp acceleration or deceleration.
As the Jerk Control value increases the derived accelerating jerk value decreases
based on:
and the decelerating Jerk limit value also decreases according to:
The Flying Start Enable attribute is used to enable or disable the Flying Start
feature of the device. When Flying Start Enable is true and the motion axis is
enabled, the device determines the current velocity of the motor, using either the
configured Flying Start Method or, if not supported, a method that is left to the
drive vendor's discretion. This operation is done as part of the Starting State
initialization activities. Just prior to transitioning to the Running state, the device
presets the output of the Ramp Generator to the current velocity. In this way, the
motor seamlessly ramps from its current velocity to the commanded velocity from
the controller. When Flying Start Enable is false, the motor velocity is irrelevant
and a preset of 0 is applied to the Ramp Generator output.
Some drive vendors do not allow the Flying Start feature to be disabled when
connected to a feedback device. To support this behavior, these drives do not
support the Flying Start Enable attribute, but do support the Flying Start Method
attribute.
The Flying Start Method attribute is an enumerated value which establishes the
method used to "catch" a moving motor when the drive is enabled. The configured
Flying Start Method is applied if Flying Start Enable is true or if the Flying Start
Enable attribute is not supported.
When Encoder Only is selected, the drive uses encoder feedback to determine the
current speed of the motor to initialize the Ramp Generator output. This method
is not applicable without a connected feedback device. If Encoder Only is selected
without a connected feedback device, the Flying Start function is effectively
disabled.
When Counter EMF is selected, the drive determines the speed of the motor by
measuring the motor's Counter EMF and applying the estimated speed to the
Ramp Generator output.
When Sweep Frequency is selected the drive applies an algorithm that excites the
motor at a predetermined frequency and, while "sweeping" the frequency to zero,
checks for the motor current to change sign when the frequency matches the speed
of the motor. The drive then applies this speed to the to the Ramp Generator
output.
See also
Command Generator Signal These are the command generator signal attributes associated with a Motion
Attributes Control Axis.
The Position Fine Command attribute is the output value from the Command
Position fine interpolator.
The Velocity Fine Command attribute is the output value from the Command
Velocity fine interpolator. When no Command Velocity signal is present when
performing position control, this signal can be derived by scaling the Differential
Position output value of the Command Position fine interpolator.
The Acceleration Fine Command attribute is the output value from the
Command Acceleration fine interpolator. When no Command Acceleration
signal is present when performing position or velocity control, this signal can be
derived by scaling the Differential Velocity output value of the Command
Velocity fine interpolator. If no Command Velocity signal is present, the
Interpolated Command Acceleration signal can be derived by scaling the 2nd
Differential Position output value of the Command Position fine interpolator.
See also
Current Control Configuration These are the current control configuration attributes associated with a Motion
Control Axis.
Attributes
Current Vector Limit
The Torque Loop Bandwidth attribute determines the Iq Proportional Gain value
that multiplies the Iq Current Error signal before applying it to the Iq decoupling
summing junction as part of the torque producing current loop. In cases where the
torque producing current loop is controlled by something other than the
traditional PI regulator, the Torque Loop Bandwidth is used by the drive to
provide single parametric control of the current loop bandwidth. If the Flux Loop
Bandwidth is not supported, the drive will use the Torque Loop Bandwidth for
tuning both the torque producing and flux producing current loops.
The Torque Integral Time Constant value determines the response time of the
torque producing current loop integrator. When used for Pole-Zero cancelation,
this value is set to the electrical time constant of the motor. A value of 0 for the
Torque Integral Time Constant disables the integrator.
Determines the Id Proportional Gain value that multiplies the Id Current Error
signal before applying it to the Iq decoupling summing junction as part of the flux
producing current loop. In cases where the flux producing current loop is
controlled by something other than the traditional PI regulator, the Flux Loop
Bandwidth is used by the drive to provide single parametric control of the current
loop bandwidth. If the Flux Loop Bandwidth is not supported, the drive will use
the Torque Loop Bandwidth for tuning both the torque producing and flux
producing current loops.
The Flux Integral Time Constant value determines the response time of the flux
producing current loop integrator. When used for Pole-Zero cancelation, this
value is set to the electrical time constant of the motor. A value of 0 for the Flux
Integral Time Constant disables the integrator.
Flux Up Control
Flux Up Time
The Flux Up Time attribute sets the amount of time the drive device allows to
build full motor flux before transitioning to the Running state.
This enumerated parameter is set to Controller Offset (1) when the motor
mounted absolute feedback device is to be aligned with the stator windings of the
PM motor according to the Commutation Offset value. In some cases the
Commutation Offset can be preset to a value established by factory alignment of
the motor feedback device relative to the motor stator windings.
A setting of Not Aligned (0) indicates that the motor is not aligned, and that the
Commutation Offset value is not valid. If the Commutation Offset is not valid, it
cannot be used by the drive to determine the commutation angle. Any attempt to
enable the drive with an invalid commutation angle will result in a Start Inhibit
condition.
Alignment can be achieved using a Commutation Test that measures and sets the
Commutation Offset for the motor or by direct user entry. If this attribute is set to
Motor Offset (2) the drive derives the commutation offset directly from the
motor. If set to Self-Sense (3) the drive automatically measures the commutation
offset when it transitions to the Starting state for the first time after a power cycle.
This generally applies to a PM motor equipped with a simple incremental
feedback device.
Commutation Offset
This algorithm applies a current to the motor stator to orient the rotor to establish
the motor commutation phasing.
Commutation Polarity
When a PM motor is using UVW signals for commutation start up, it is critical
that the UVW phases of the commutation device follow the phasing of the motor.
Normal polarity implies UVW phasing according to factory specification when
the commutation device is moving in the factory defined positive direction.
Inverted polarity effectively switches the UVW phasing to UWV thus reversing
the directional sense of the commutation device. If it is determined through a
Commutation Test that the phasing of the motor and the phasing of the
commutation device have opposite polarity, this attribute can be used to
compensate for the mismatch.
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
This value specifies the change in the Commutation Offset value in units of
electrical degrees as a linear function of current. When the Iq current is +100% of
rated continuous current, the Commutation Offset value is decreased by the value
of this attribute. When the Iq current is -100% the Commutation Offset is
increased by the value of the attribute. This attribute is used by the drive to
compensate for changes in the optimal Commutation Offset angle that can occur
as a function of motor current.
Commutation Alignment
The Default Commutation Alignment value used for the Feedback Commutation
Aligned and Commutation Alignment attributes depends on the associated
Feedback Type and whether or not the motor commutation device is Factory
Aligned. When the Motor Data Source is from Datasheet, it is assumed that the
motor is not Factory Aligned. When the Motor Data Source is from Database,
motor data in the database indicates if the motor is Factory Aligned.
The following table correlates the default commutation alignment with the valid
commutation alignment selections.
See also
Current Control Signal These are the current control signal related attributes associated with a Motion
Control Axis.
Attributes
Current Command
The Operative Current Limit attribute represents the operative current limit
based on multiple limit sources.
The Current Limit Source attribute represents the operative source of a current
limit when a current limit condition occurs.
The Motor Electrical Angle attribute is the calculated electrical angle of the motor
based on motor pole count, commutation offset, and selected feedback device.
Current Reference
The Current Reference attribute is the current reference signal, Iq, into the torque
current loop summing junction.
The Flux Current Reference attribute is the current reference signal, Id, into the
flux producing current loop summing junction.
Current Disturbance
Current Error
Error between commanded and actual current that is the output of the torque
producing, q-axis, current loop summing junction.
Error between commanded and actual current that is the output of the flux
producing, d-axis, current loop summing junction.
Current Feedback
Actual torque current applied to the axis based on current sensor feedback.
Actual flux current applied to the axis based on current sensor feedback.
See also
Frequency Control These are the Frequency Control Configuration attributes associated with the
Frequency Control method of operation of a Motion Control Axis.
Configuration Attributes
Frequency Control Method
The Basic Volts/Hertz control method applies voltage to the motor generally in
direct proportion to the commanded frequency or speed.
Sensorless Vector Economy applies the Sensorless vector algorithm but seeks to
reduce energy consumption when the applied load is less than 50% of rating.
Maximum Voltage
The Maximum Voltage attribute sets the highest phase-to-phase voltage the drive
device can output.
Maximum Frequency
The Maximum Frequency attribute sets the highest frequency the drive device can
output.
Break Voltage
The Break Voltage attribute sets the phase-to-phase output voltage of the drive
device at the Break Frequency where boost ends.
Break Frequency
The Break Frequency attribute sets the output frequency of the drive device at the
Break Voltage where boost ends.
Start Boost
The Start Boost attribute sets phase-to-phase voltage boost level for starting and
accelerating.
Run Boost
The Run Boost attribute sets the phase-to-phase voltage boost level for
steady-state speed or deceleration.
See also
Frequency Control Signal This attribute is the signal attribute associated with the Frequency Control
method of operation of a Motion Control Axis.
Attribute
Slip Compensation
See also
Position Loop Signal Attributes These are the position loop signal related attributes associated with a Motion
Control Axis.
Position Command
The Position Command attribute is the command position output from the Find
Command Generator (if active) into the position loop when configured for
position loop control.
Position Trim
Position Reference
The Position Reference attribute is the command position reference signal into
the position loop summing junction to be compared with a position feedback
signal.
Position Feedback
The Position Feedback attribute is a 32-bit position feedback value that when
configured for Position Control mode, is applied to the position proportional
control summing junction. In most cases the Position Feedback signal is derived
directly from the feedback device specified by the Feedback Mode selection. If,
however, axis Feedback Mode is configured for Master Feedback Position
Feedback represents the actual position of the feedback device specified by the
Feedback Master Select. If Feedback Master Select is not supported, the Feedback
1 channel is used.
This 64-bit position feedback value, when supported, extends the range of the
32-bit Position Feedback attribute. When configured for Position Control mode,
the lower 32-bits of this attribute becomes the Position Feedback signal that is
applied to the position proportional control summing junction. In most cases the
Position Feedback – 64 Bit signal is derived directly from the feedback device
specified by the Feedback Mode selection. If axis Feedback Mode is configured
for Master Feedback Position Feedback – 64 Bit represents the actual position of
the feedback device specified by the Feedback Master Select. If Feedback Master
Select is not supported, the Feedback 1 channel is used.
The Position Integral Feedback attribute is position feedback value channeled into
the position integral control summing junction.
Position Error
The Position Error attribute is the error between commanded and actual position
that is the output of the position loop summing junction.
The Position Loop Output attribute is the output of the position loop forward
path representing the total control effort of the position loop.
See also
Position Loop Configuration These are the position loop configuration attributes associated with a Motion
Control Axis.
Attributes
Velocity Feedforward Gain
The Position Loop Bandwidth attribute determines the proportional gain, Kpp, of
the position loop that multiplies the Position Error signal. This value represents
the unity gain bandwidth of the position loop beyond which the position loop is
ineffective.
The Position Lock Tolerance attribute establishes a window around the current
command position. When the actual position is within this window the Position
Lock status bit is set. When actual position falls outside this window, the Position
Lock status bit is cleared.
The Position Error Tolerance Time attribute determines the maximum amount of
time that the Position Error Tolerance can be exceeded without generating an
exception.
The Position Lead Lag Filter Bandwidth attribute sets the pole frequency for the
position regulator Lead-Lag Filter. A value of 0 disables the filter.
The Position Lead Lag Filter Gain attribute sets the high frequency gain of the
position regulator Lead-Lag Filter. A value greater than 1 results in a lead function
and value less than 1 results in a lag function. A value of 1 disables the filter.
The Position Notch Filter Frequency attribute controls the center frequency of
the notch filter that is applied to the velocity reference signal of the velocity loop
summing junction. A value of 0 for this attribute disables this feature.
The Position Integrator Control attribute controls the behavior of the position
loop integrator while commanding motion through the controller. When the
integrator hold enable bit is set, the integrator is held while motion is being
commanded with a non-zero velocity. When clear, the integrator runs without
qualification. When the auto-preset bit is set, the integrator preload value is
automatically loaded with the current velocity command when there is a control
mode change between velocity control and position control. If clear, the integrator
is loaded with the configured position integrator preload value.
The Position Limit - Positive attribute is a value that defines the most positive
position value. Exceeding the value while commanding motion in the positive
direction generate a Position Overtravel Positive exception.
This value defines the most negative position feedback value that when exceeded
while commanding motion in the negative direction, generates a Position
Overtravel Negative exception.
See also
Torque/Force Control These are the torque/force control configuration attributes associated with a
Motion Control Axis.
Configuration Attributes
Torque Offset
The Torque Offset attribute provides a torque bias when performing closed loop
control. This value is summed together with the Torque Trim value that can be
sent synchronously to the drive every connection update. Since the Torque Trim
value is available as a templated value, real time torque corrections can be done
using the Torque Trim attribute.
System Inertia
Torque or force scaling gain value that converts commanded acceleration into
equivalent rated torque/force. Properly set, this value represents the total system
inertia or mass.
The Backlash Reversal Offset attribute value is used to compensate for positional
inaccuracy introduced by mechanical backlash. Backlash manifests itself when an
axis is commanded to reverse direction. During such a reversal there is a small
Whenever the commanded velocity changes sign (a reversal), the Logix controller
will add, or subtract, the offset value from the current commanded position. This
causes the servo to immediately move the motor to the other side of the backlash
window and engage the load. It is important to note that the application of this
directional offset is completely transparent to the user; the offset does not have
any impact on the value of the Command Position attribute. If a value of zero is
applied to the Backlash Reversal Offset, the feature is effectively disabled. Once
enabled by a non-zero value, and the load is engaged by a reversal of the
commanded motion, changing the Backlash Reversal Offset can cause the axis to
shift as the offset correction is applied to the command position.
Defines a window around the command position. When the actual position is
within this window, the effective System Inertia gain is reduced by a factor of the
ratio of the Position Error and the Backlash Compensation Window. When the
actual position is outside the window, the configured System Inertia gain is
applied.
Value added to the current/torque command to offset the effects of static friction
(sometimes referred to "sticktion").
Defines a window around the command position. When the actual position is
within this window, the effective Friction Compensation value is reduced by a
factor of the ratio of the Position Error and the Friction Compensation Window.
When the actual position is outside the window, or when the axis is being
commanded to move, the normal friction compensation algorithm applies.
Sets the pole frequency for the torque reference Lead-Lag Filter. A value of 0
disables the filter.
Sets the high frequency gain of the torque reference Lead-Lag Filter. A value
greater than 1 results in a lead function and value less than 1 results in a lag
function. A value of 0 results in a first order low pass filter function. A value of 1
disables the filter.
Break frequency for the low pass filter applied to torque reference signal.
Center frequency of the notch filter instance applied to the torque reference
signal. Up to four torque notch filter instances connect in series. A value of 0 for
this attribute disables this filter.
This positive value determines the maximum positive torque that can be applied
to the motor. If the device attempts to exceed this value, the torque command is
clamped to this value.
This negative value determines the most negative torque value that can be applied
to the motor. If the device attempts to apply a more negative torque than this
limit, the torque command is clamped to this value.
Torque Threshold
Specifies the threshold for the Filtered Torque Reference signal magnitude that
when exceeded, results in the Torque Threshold status bit being set.
Overtorque Limit
Maximum limit for the torque producing Iq Current Feedback signal magnitude.
When the Iq Current Feedback signal is greater than this value for the duration
specified by Overtorque Limit Time attribute, the result is an Overtorque Limit
exception. This feature lets the device generate an exception if there is a sudden
increase in load torque during operation. This condition could occur if a bearing
fails, a hard stop is reached, or there is some other mechanical failure.
Undertorque Limit
Minimum limit for the torque producing Iq Current Feedback signal magnitude.
When the Iq Current Feedback is less than this value for the duration specified by
Undertorque Limit Time attribute, the result is an Undertorque Limit exception.
This feature lets the device generate an exception if there is a sudden decrease in
load torque during operation. This condition could occur, for example, if a load
coupling breaks or a tensioned web material breaks.
The Inertia Observer Filter Bandwidth attribute sets the frequency for the inertia
low pass filter applied to the Total Inertia Estimate.
Enumerated value that controls operation of the Adaptive Tuning function. This
function periodically collects axis torque data and analyzes this data to identify
resonances and closed loop instabilities in the system.
When Adaptive Tuning Configuration is Disabled the configured values for all
servo loop attributes of the associated axis are applied directly without
intervention of the Adaptive Tuning function.
When configured for Tracking Notch, the Torque Notch Filter Frequency
Estimate attribute value, determined by the Adaptive Tuning function, is applied
to the Torque Notch Filter as part of the control loop update. The configured
Torque Notch Filter Frequency attribute is not overwritten as a result of this
operation. All other servo loop attributes are applied directly without intervention
of the Adaptive Tuning function.
When configured for Gain Stabilization, the Load Observer Bandwidth, Load
Observer Integrator Bandwidth, Velocity Loop Bandwidth, Velocity Loop
Integrator Bandwidth, Position Loop Bandwidth, and Position Loop Integrator
Bandwidth attribute values are scaled by the Adaptive Tune Gain Scaling Factor as
part of the control loop update. The configured values of these attributes are not
overwritten as a result of this operation. The Torque Low Pass Filter Bandwidth
Estimate is also applied to the Torque Low Pass Filter Bandwidth. In this
configuration, the value of the Torque Notch Filter Frequency attribute is applied
directly to the notch filter without intervention of the Adaptive Tuning function
When configured for Notch Filter and Gain Stabilization, the Torque Notch
Filter Frequency Estimate attribute value, determined by the Adaptive Tuning
function, is applied to the Torque Notch Filter as part of the control loop update.
The configured Torque Notch Filter Frequency attribute is not overwritten as a
result of this operation. The Load Observer Bandwidth, Load Observer Integrator
Bandwidth, Velocity Loop Bandwidth, Velocity Loop Integrator Bandwidth,
Position Loop Bandwidth, and Position Loop Integrator Bandwidth attributes are
scaled by the Adaptive Tune Gain Scaling Factor as part of the control loop
update. The configured values of these attributes are not overwritten as a result of
this operation. The Torque Low Pass Filter Bandwidth Estimate is also applied to
the Torque Low Pass Filter Bandwidth.
Even if Disabled, the Adaptive Tuning function runs periodically to collect drive
data while the axis is in the Running state. When a resonance frequency is detected
that meets the configured Notch Tuning criteria, the frequency of the resonance is
loaded to the Torque Notch Filter Frequency Estimate attribute. The magnitude
of the resonance is also loaded to the Torque Notch Filter Magnitude Estimate.
The Adaptive Tuning status bits in the CIP Axis Status RA attribute are updated
each time the Adaptive Tuning function is executed.
The configured Notch Tuning criteria are that the magnitude of the resonance
frequency, not associated with the command, be above the configured Torque
Notch Filter Tuning Threshold and that the frequency of the resonance be
between the configured Torque Notch Filter Low Frequency Limit and Torque
Notch Filter High Frequency Limit.
The Adaptive Tuning function sets the Torque Notch Filter Frequency Estimate
to the identified resonant frequency with the largest magnitude that meets the
configured Notch Tuning criteria.
the Adaptive Tuning status bits of the CIP Axis Status RA attribute and the
Adaptive Tuning Configuration.
When the drive axis is in any other state besides the Running state, the Adaptive
Tuning function is turned off and does not collect data.
When the drive transitions out of the Running state, the present values of all the
Adaptive Tuning status bits and output estimates will persist. When the drive
transitions into the Running state, the values of all the Adaptive Tuning status bits
are set to 0 and output estimates will persist until they are updated by the
Adaptive Tuning feature.
This value sets the upper limit on the Torque Notch Filter Frequency Estimate
value for the Adaptive Tuning function. The frequency of an identified natural
resonance must be lower than this limit to be applied to the Torque Notch Filter
Frequency Estimate.
This value sets the lower limit on the Torque Notch Filter Frequency Estimate
value for the Adaptive Tuning function. The frequency of an identified natural
resonance must be higher than this limit to be applied to the Torque Notch Filter
Frequency Estimate.
This value represents the resonance frequency with the highest magnitude above
the Torque Notch Filter Tuning Threshold and between the Torque Notch Filter
Low Frequency Limit and the Torque Notch Filter High Frequency Limit as
identified by the Adaptive Tuning function.
The Torque Notch Filter Frequency Estimate value is initialized to zero when the
drive is power cycled or reset.
This value represents the maximum magnitude for resonant peaks found above the
Torque Notch Filter Tuning Threshold and between the Torque Notch Filter
Low Frequency Limit and the Torque Notch Filter High Frequency Limit as
identified by the Adaptive Tuning function.
The Torque Notch Filter Magnitude Estimate value is initialized to zero when the
drive is power cycled or reset.
This value represents the Bandwidth of the Torque Low Pass Filter when the
Adaptive Tuning Configuration is equal to Gain Stabilization or Tracking Notch
and Gain Stabilization. The value is modified by the Adaptive Tuning function.
The value is initialized to the Torque Low Pass Filter Bandwidth when the
Adaptive Tuning Configuration transitions from Disabled or Tracking Notch to
Gain Stabilization or Tracking Notch and Gain Stabilization. The Torque Low
Pass Filter Bandwidth Estimate value is initialized to zero when the drive is power
cycled or reset.
This value proportionally scales the servo loop gain attributes of the associated
axis. The value is modified by the Adaptive Tuning function. The value is reset to
1 any time the Adaptive Tuning Configuration is Disabled or set to Tracking
Notch. The value is initialized to 1 when the drive is power cycled or reset.
See also
Torque/Force Control Signal These are the torque/force signal related attributes associated with a Motion
Control Axis.
Attributes
Torque Command
Command torque output from fine interpolator (if active) into torque input
summing junction when configured for toque control.
Torque Trim
Torque Reference
The Total Inertia Estimate attribute is the estimated total inertia or mass of the
axis based on output of Inertia Observer. This value is directly applied to Kj to
adapt to changing load inertia or mass.
See also
Velocity Loop Configuration These are the velocity loop configuration attributes associated with a Motion
Control Axis.
Attributes
Velocity Offset
The Velocity Offset attribute can be used to provide a velocity bias when
performing velocity control. This value is summed together with the Velocity
Trim value that can be sent synchronously to the drive every Coarse Update
Period. Since the Velocity Trim value is available as a templated value, real time
velocity corrections can be done using the Velocity Trim attribute.
The Velocity Integrator Bandwidth attribute determines the velocity loop integral
gain, Kvi, which together with the Kvp, multiplies the integrated Velocity Error
300 Rockwell Automation Publication MOTION-RM003K-EN-P - July 2019
CIP Axis Attributes Chapter 4
signal. This value represents the bandwidth of the velocity integrator beyond
which the integrator is ineffective. A value of 0 for this attribute disables the
integrator.
Velocity Droop
The Velocity Error Tolerance Time attribute determines the maximum amount of
time that the Velocity Error Tolerance can be exceeded without generating an
exception.
The Velocity Integrator Control attribute controls the behavior of the velocity
loop integrator while commanding motion through the controller. When the
integrator hold enable bit is set, the integrator is held while motion is being
commanded with a non-zero velocity. When clear, the integrator runs without
qualification. When the auto-preset bit is set, the integrator preload value is
automatically loaded with the current torque command when there is a control
mode change between torque control and velocity control. If clear, the integrator
is loaded with the configured velocity integrator preload value.
The Velocity Low Pass Filter Bandwidth attribute controls the bandwidth of the
Low Pass Filter applied to the Velocity Error signal. Recommended
implementation is a two pole IIR filter. A value of 0 for this attribute disables this
feature.
Velocity Threshold
The Velocity Lock Tolerance attribute establishes a window around the unlimited
velocity reference signal. When the Velocity Feedback signal is within this window
the Velocity Lock status bit is set. When Velocity Feedback signals falls outside
this window, the Velocity Lock status bit is cleared.
The Velocity Limit - Positive attribute defines the most positive velocity reference
value into the velocity summing junction. If the signal entering the velocity limiter
exceeds this velocity limit value, the device responds by clamping the velocity
reference to this limit and sets the Velocity Limit status bit.
The Velocity Limit - Negative attribute is a negative value that defines the most
negative velocity reference value allowed into the velocity summing junction. If
the signal entering the velocity limiter exceeds this velocity limit value, the device
responds by clamping the velocity reference to this limit and sets the Velocity
Limit status bit.
Slat Configuration
The Slat Configuration attribute configures the Speed Limited Adjustable Torque
feature. The SLAT Configuration enumeration determines how the drive controls
torque for this axis instance. In order to support applications that require Speed
Limited Adjustable Torque (SLAT) control, the Min/Max torque control
enumerations provide a feature to automatically switch to and from speed control
under certain conditions. In either SLAT mode the drive will operate in one of
two min/max states - speed control off or on.
Speed Error level to switch from Speed control to Min/ Max control.
Time delay after SLAT Set Point is reached to switch from Speed control to Min/
Max control.
Time delay after SLAT Set Point is reached to switch from Speed control to Min/
Max control.
Min Mode
If the mechanical speed limitation is removed (example web break), the motor
accelerates and the Velocity Error becomes negative when the motor speed exceeds
the Velocity Command. At this time, an automatic transition to speed control
occurs and the Velocity Loop Output is selected as the Torque Reference,
regardless of the value of the Torque Command. Coincident with the transition
into speed control, a preset operation will occur within the velocity loop. This
preset will force the velocity loop integrator to match the internal torque reference
value, at the time of the mode transition.
In Min mode the drive remains in speed control until the Velocity Error exceeds
the configured SLAT Set-point attribute value for a period of time given by the
SLAT Time Delay attribute. When these two conditions are met, speed control is
turned off and the 'Min' select operation becomes active. This condition would
occur if the mechanical constraint was restored.
Max Mode
The active 'Max' select function will select the larger, or Max function, of the
Velocity Loop Output or the Torque Command. The Velocity Command value is
a negative quantity and so when the motor speed is mechanically limited, the
Velocity Error is a negative value, and the Velocity Loop Output is a saturated
(limited) to a negative value. The Torque Command is also negative, but smaller
in magnitude, so it becomes selected by the 'Max' operation.
The forced transition to speed control occurs when the Velocity Error value
becomes positive such as when the mechanical limitation is removed. A preset of
the velocity loop's integral term occurs, as before.
See also
Position Loop Attributes on page 281
Position Loop Configuration Attributes on page 284
Velocity Loop Attributes on page 307
Velocity Loop Signal Attributes These are the velocity control signal related attributes associated with a Motion
Control Axis.
Velocity Command
The Velocity Command attribute is the command velocity output from the Fine
Command Generator (if active) into velocity loop when configured for the
Velocity Loop control or frequency controller when configured for Frequency
Control operation.
Velocity Trim
Velocity Reference
Command velocity reference into velocity loop summing junction, or in the case
of Frequency Control, the signal that is scaled to become the Frequency Reference.
Velocity Feedback
Actual velocity of the axis applied to the velocity summing junction, if applicable,
based on Control Mode selection. In most cases the Velocity Feedback signal is
derived directly from the feedback device specified by the Feedback Mode
selection. If the axis is configured for Feedback Only mode, Velocity Feedback
represents the actual velocity of the feedback device. If the axis is configured for
Frequency Control, the Velocity Feedback signal is derived from the Velocity
Reference signal. If configured for Sensorless Velocity Loop operation, i.e.
Feedback Mode set to No Feedback, Velocity Feedback is estimated by the
sensorless control algorithm.
Velocity Error
Error between the velocity reference and velocity feedback value that is the output
of the velocity loop summing junction.
Output of velocity forward path representing the total control effort of the
velocity loop.
The Velocity Limit Source attribute is an enumerated value that specifies the
source of the operative velocity limit.
Field Weakening
When the drive applies field weakening to a PM motor to reach higher than rated
speed, the drive's motor current vector control algorithm effectively decreases the
motor Ke. This reduces the resulting Counter EMF (CEMF) voltage to be less
than the DC bus voltage. However, if this active current vector control is suddenly
removed, the Ke value would revert to the nominal value and the CEMF voltage
would increase rapidly. Active control of motor current is lost whenever the power
structure is disabled. So the concern is when the power structure is disabled with
the motor still spinning. This can be the case when the drive executes a Category 0
Stop due to a control initiated Disable Request, a Major Fault action, or a Safe
Torque Off activation.
Three speed values are shown in the preceding figure. As defined in the first figure,
the rated speed (S r ) corresponds to operation at rated voltage and continuous
torque. This is the maximum continuous torque that can be achieved without field
weakening. S OV is the speed at which the CEMF voltage from the nominal Ke
would be equivalent to the maximum DC Bus Voltage rating of the drive, or the
DC Bus Overvoltage Limit.
If active motor current control is removed while the motor is operating at speeds
above S OV , the CEMF voltage results in a DC Bus overvoltage condition that can
damage the drive and, possibly, other drives sharing the same DC Bus.
Major damage to devices connected to the DC Bus can occur when the PM motor
is allowed to run between S OV and S m and the drive's power structure is disabled.
The following diagram shows the extensions that have been added to the Velocity
Limiter to help manage the inherent risks of high speed PM motor operation. In
addition to the existing Velocity Limit - Positive/Negative attributes that can be
used to limit the Velocity Reference signal, two new limits have been defined based
on S OV and S m defined above. Specifically, the PM Motor Rotary - Bus
Overvoltage Speed and PM Motor Linear Bus Overvoltage Speed attributes
establish an absolute limit on the Velocity Reference signal that corresponds to
S OV . This speed limit can only be exceeded if the PM Motor Extended Speed
Permissive attribute is set to True. The PM Motor Rotary Max Extended Speed
and PM Motor Linear Max Extended Speed attributes establish an absolute limit
on the Velocity Reference signal that corresponds to S m . The Velocity Limit
function limits the Velocity Reference signal to the minimum of these attribute
values. The Velocity Limit Source attribute indicates the source of the velocity
limit.
Through these extensions to the Velocity Limiter function, a drive that supports
field weakening can be configured to safely manage extended speed operation, only
allowing operation above S OV by setting the PM Motor Extended Speed
Permissive attribute. Systems that can run safely above S OV are generally equipped
with a DC Bus Regulator or a Resistive Brake Module.
See also
Position Loop Signal Attributes on page 281
Position Loop Configuration Attributes on page 284
Velocity Loop Configuration Attributes on page 299
General Permanent Magnet Motor Attributes on page 519
Rockwell Automation Publication MOTION-RM003K-EN-P - July 2019 311
Chapter 4 CIP Axis Attributes
Data Attributes These attribute tables contain attributes associated with general data of Motion
Control Axis Object instance.
Axis Info Attributes These are the attributes that provide information about the associated hardware
capabilities of Motion Control Axis.
The Inverter Rated Output Voltage attribute is the drive inverter output voltage
rating. This value is hard coded in the device.
The Inverter Rated Output Current attribute is the drive inverter output current
rating. This value is hard coded in the device.
The Inverter Rated Output Power attribute is the drive inverter output power
rating. This value is hard coded in the device.
The Converter Rated Output Current attribute is the converter output current
rating.
The Converter Rated Output Power attribute is the converter output power
rating.
The Converter Rated Output Voltage attribute is the converter output voltage
rating.
The Converter Rated Input Current attribute is the converter input current
rating.
The Converter Rated Input Power attribute is the converter input power rating.
The Converter Rated Input Voltage attribute is the converter input voltage rating.
See also
Axis Statistical Attributes These are the attributes that provide useful statistics on motion axis operation.
Accumulated time that the axis has been powering the Running state.
Cumulative number of times motor shaft has turned. (Rotary Motors Only).
See also
CIP Axis Status Attributes These are the device status attributes associated with a Motion Control Axis. Any
status bits that are not applicable are set to 0.
The CIP Axis Status attribute is a 32-bit collection of standard bits indicating the
internal status conditions of the axis.
7 Optional/ Velocity Lock This bit is set if the velocity feedback signal is within the
PV Velocity Lock Tolerance of the unlimited velocity reference.
8 Required/ Velocity Standstill This bit is set if the velocity feedback signal is within
ED Velocity Standstill Window of 0. For a Frequency Control
drive this bit is set if the velocity reference signal is within
Velocity Standstill Window of 0.
9 Optional/ Velocity Threshold This bit is set if the absolute velocity feedback signal is
ED below Velocity Threshold. For a Frequency Control drive
this bit is set if the absolute velocity reference signal is
below the Velocity Threshold.
10 Optional/ Velocity Limit This bit is set if the velocity reference signal is currently
FPV being limited by the Velocity Limiter.
The naming convention for individual bits within the CIP Axis Status attributes is
to append a 'Status' suffix to the CIP Axis Status condition. This table lists the
resulting CIP Axis Status tags associated with the above status conditions.
Bit Tag
0 LocalControlStatus
1 AlarmStatus
2 DCBusUpStatus
3 PowerStructureEnabledStatus
4 MotorFluxUpStatus
5 TrackingCommandStatus
6 PositionLockStatus
7 VelocityLockStatus
8 VelocityStandstillStatus
9 VelocityThresholdStatus
10 VelocityLimitStatus
11 AccelerationLimitStatus
12 DecelerationLimitStatus
13 TorqueThresholdStatus
14 TorqueLimitStatus
15 CurrentLimitStatus
16 ThermalLimitStatus
17 FeedbackIntegrityStatus
18 ShutdownStatus
19 InProcessStatus
20 DCBusUnloadStatus
21 ACPowerLossStatus
22 PositionControlMode
23 VelocityControlMode
24 TorqueControlMode
The CIP Axis Status 2 attribute is a collection of standard bits indicating the
internal status conditions of the axis. This attribute provides a 32-bit extension to
the CIP Axis Status attribute.
The naming convention for individual bits within the CIP Axis Status 2 attributes
is to append a 'Status' suffix to the CIP Axis Status 2 condition. This table lists the
resulting CIP Axis Status 2 tags associated with the above status conditions.
Bit Tag
0 MotoringStatus
1 RegeneratingStatus
2 RideThruStatus
3 ACLineSyncStatus
4 BusVoltageLockStatus
5 ReactivePowerOnlyModeStatus
6 VoltageControlModeStatus
7 PowerLossStatus
8 ACLineVoltageSagStatus
9 ACLinePhaseLossStatus
10 ACLineFrequencyChangeStatus
11 ACLineSyncLossStatus
12 SinglePhaseStatus
13 BusVoltageLimit
14 BusVoltageRateLimit
15 ActiveCurrentRageLimit
16 ReactiveCurrentRateLimit
17 ReactivePowerLimit
18 ReactivePowerRateLimit
19 ActiveCurrentLimit
20 ReactiveCurrentLimit
21 MotoringPowerLimit
22 RegenerativePowerLimit
23 ConverterThermalLimit
The CIP Axis Status 2 - Mfg attribute is a collection of vendor specific bits
indicating the internal status of the axis.
The naming convention for individual bits within the CIP Axis Status RA
attributes is to append a 'Status' suffix to the CIP Axis Status RA condition. This
table lists the resulting CIP Axis Status RA tags associated with the above status
conditions.
Bit Tag
0 TorqueNotchFilterFreqDetectedStatus
1 TorqueNotchFilterTuneUnsuccessfulStatus
2 TorqueNotchFilterMultipleFreqStatus
3 TorqueNotchFilterFreqBelowLimitStatus
4 TorqueNotchFilterFreqAboveLimitStatus
5 AdaptiveTuneGainStabilizationStatus
The naming convention for individual bits within the CIP Axis Status 2 RA
attributes is to append a 'Status' suffix to the CIP Axis Status 2 RA condition.
This table lists the resulting CIP Axis Status 2 RA tags associated with the above
status conditions.
Bit Tag
0 -
The CIP Axis I/O Status attribute is a 32-bit collection of bits indicating the state
of standard digital inputs and outputs associated with the operation of this axis. A
value of zero for a given input bit indicates a logical 0 (false) value, while a value of
1 indicates a logical 1 (true) value. For example a value of 1 for the Positive
Overtravel OK Input indicates that Positive Overtravel OK is true and there is no
positive overtravel condition present. Conversely a value of 0 would indicate the
Positive Overtravel OK Input is false and there is a positive overtravel condition
present. Similarly, a value of 1 (true) for the Mechanical Brake Release Output
indicates that the mechanical brake is released. Any status bits that are not
applicable will be set to 0.
The naming convention for individual bits within the CIP Axis I/O Status
attributes is to append a 'Status' suffix to the CIP Axis Status condition. This table
lists the resulting CIP Axis I/O Status tags associated with the above status
conditions.
Bit Tag
0 EnableInputStatus
1 HomeInputStatus
2 Registration1InputStatus
3 Registration2InputStatus
4 PositiveOvertravelInputStatus
5 NegativeOvertravelInputStatus
6 Feedback1ThermostatInputStatus
7 ResistiveBrakeOutputStatus
8 MechanicalBrakeOutputStatus
9 MotorThermostatInputStatus
The naming convention for individual bits within the CIP Axis I/O Status - RA
attributes is to append a 'Status' suffix to the CIP Axis Status - RA condition. This
table lists the resulting CIP Axis I/O Status -RA tags associated with the above
status conditions.
Bit Tag
0 RegenerativePowerInputStatus
1 BusCapacitorModuleInputStatus
2 ShuntThermalSwitchInputStatus
3 ContactorEnableOutputStatus
Bit Tag
4 PreChargeInputStatus
5 ACLineContactorInputStatus
6 RegenerativePowerOutputStatus
7 BusConditioneerModuleInputStatus
8 ConverterInputStatus
9 ConverterOutputStatus
See also
Event Capture Attributes These are the event related attributes associated with a Motion Control Axis.
These include registration, marker, and homing events. The Event Capture
attributes are designed to support the possibility of up to 7 active events per
controller update period. The basis for all Time Stamp attributes is absolute
System Time and follows the CIP Sync standard with 0 corresponding to January
1, 1970. Within the Logix controller, the System Time for event time stamps are
converted to the local CST by applying the local System Time Offset to the event
time stamp. In general, these event related attributes are only applicable when
there is an associated position feedback device; if the axis is configured for
Encoderless or Sensorless operation, the event functionality is not applicable.
The Motion Control Axis supports two independent registration input channels
per device axis instance that can be triggered on either the rising or falling edges of
the signal. If the device hardware implementation allows, event time and position
data can be captured for all four event conditions simultaneously. The Event
Capture attributes also support Auto-rearm for registration events. This allows for
controller implementation of important features like Windowed Registration and
Registration Pattern Recognition.
The Motion Control Axis also supports Home Switch, Marker and
Switch-Marker events for homing functionality on a per axis basis. The Marker
events are typically generated by the configured position feedback device for the
associated device axis.
Registration Inputs
The Registration 1 Positive Edge Time attribute is the CST time stamp on the
rising edge of the Registration Input 1.
The Registration 1 Negative Edge Time attribute is the CST time stamp on the
falling edge of the Registration Input 1.
The Registration 2 Positive Edge Time attribute is the CST Time stamp on the
rising edge of the Registration Input 2.
The Registration 2 Negative Edge Time attribute is the CST Time stamp on the
falling edge of the Registration Input 2.
See also
Drive Attributes These attribute tables contain attributes associated with the drive. Drive attributes
reside both on the controller and on the drive.
Drive General Purpose I/O These are the attributes that provide to general purpose analog and digital I/O
associated with the Motion Control Axis.
Attributes
Digital Inputs
The Digital Inputs attribute is a 32-bit word with whose bits can be assigned by
the vendor to general purpose digital inputs.
Digital Outputs
The Digital Outputs attribute is a 32-bit word with whose bits can be assigned by
the vendor to general purpose digital outputs.
Analog Input 1
Analog Input 2
Analog Output 1
Analog Output 2
The Enable Input Checking attribute is a Boolean value used to control if the
drive or converter checks the state of the Enable Input. When enabling Enable
Input Checking, an inactive Enable Input triggers a Start Inhibit condition. If the
Enable Input deactivates when the drive or converter power structure is enabled,
an Enabled Input Deactivated exception is generated. If Enable Input Checking is
disabled, the device does not check the state of the Enable Input.
The AC Line Contactor Input Checking attribute is a value that controls whether
or not the AC/DC converter function checks for the presence and proper
operation of the AC Line Contactor using the AC Line Contactor OK input. If
AC Line Contactor Checking is Enabled, the presence of AC line voltage at the
device when the AC Line Contactor OK input is Inactive shall cause the converter
to generate an AC Line Contactor exception. If AC Line Contactor Checking is
Disabled then the device shall not check the AC Line Contactor OK input.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as an Enable function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as a Home function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as a Registration 1 function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as a Registration 2 function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as a Positive Overtravel function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as an Negative Overtravel function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as an Regeneration OK
function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as a Bus Capacitor OK function.
A floating point value that specifies the width of the pulse reject filter for a digital
input configured as an Shunt Thermal Switch OK function.
A float that specifies the width of the pulse reject filter for a digital input
configured as a Home & Registration 1 function.
The Motor Thermostat OK Input Pulse Reject Filter is A float that specifies the
width of the pulse reject filter for a digital input configured as a Motor
Thermostat function.
The Pre-Charge OK Pulse Reject Filter attribute is a float that specifies the width
of the pulse reject filter for a digital input configured as a Pre-Charge function.
The AC Line Contactor is a float value that specifies the width of the pulse reject
filter for a digital input configured as a AC Line Contactor OK function.
The Bus Conditioner OK Input Pulse Reject Filter attribute is a floating point
value that specifies the
width of the pulse reject filter for a digital input configured as a Bus Conditioner
OK function.
The Converter OK Input Pulse Reject Filter attribute is a floating point value that
specifies the width of the pulse reject filter for a digital input configured as a
Converter OK input function.
See also
Drive Output Attributes These are the inverter output related attributes associated with a Motion Control
Axis.
Output Frequency
The Output Frequency attribute is the time averaged output frequency applied to
motor. Frequency value is in terms of electrical cycles.
Output Current
The Output Current attribute is the total time averaged output current applied to
motor.
Output Voltage
The Output Voltage attribute is the total time averaged phase-to-phase output
voltage applied to motor.
Output Power
The Output Power attribute is the mechanical output power of the motor. This
value represents the product of applied motor torque/force and motor speed. If
the axis is configured for Frequency Control, the Velocity Feedback signal is
derived from the Velocity Reference signal.
See also
Power and Thermal These are the power and thermal configuration related attributes associated with a
Motion Control Axis.
Management Configuration
Attributes
The Motor Overload Action attribute selects the device's response to a motor
overload condition based on an I2T or motor thermal model based overload
protection method. When a motor thermal model is employed, the motor
overload condition occurs when the motor thermal model indicates that the
Motor Capacity has exceeded the Motor Overload Limit. In the case of the I2T
overload protection method, the motor overload condition occurs when the
motor current, in percent of rated continuous motor current, exceeds the Motor
Overload Limit. The Motor Overload Action provides opportunities to mitigate
the overload condition without stopping operation.
No explicit action is taken by the device in the overload condition if None is the
selected overload action. Selecting the Current Foldback action, however, results
in a reduction of the motor current command in proportion to the percentage
difference between Motor Capacity and the Motor Overload Limit,, or in the case
of the I2T overload protection method, in proportion to the difference between
the motor current, in percent of rated continuous motor current, and the Motor
Overload Limit.
The Inverter Overload Action attribute selects the device's response to an inverter
overload condition based on an I2t or inverter thermal model based overload
protection method. When an inverter thermal model is employed the inverter
overload alarm condition occurs when the inverter thermal model indicates that
the Inverter Capacity has exceeded the Inverter Overload Limit. In the case of the
I2T overload protection method, the inverter overload condition occurs when the
inverter current, in percent of rated continuous inverter current, exceeds the
Inverter Overload Limit.
An overload alarm condition can also be generated by exceeding the limits of the
device's power block thermal model that includes switching losses that have a
dependency on the PWM Frequency.
No explicit action is taken by the device in the overload condition if None is the
selected overload action. Selecting the Current Foldback action, however, results
in a reduction of the inverter current in proportion to the percentage difference
between Inverter Capacity and the Inverter Overload Limit, or in the case of the
I2T overload protection method, in proportion to the difference between the
inverter current, in percent of rated continuous inverter current, and the Inverter
Overload Limit.
If an inverter overload condition occurs due to the power block thermal model,
two additional overload actions can be applied. Selecting Reduce PWM Rate can
be used to reduce heat generated by switching losses in the inverter power
structure. When PWM - Foldback is selected the device first reduces the PWM
rate and then, if necessary, reduces the Inverter Thermal Current Limit.
See also
Power and Thermal These are the power and thermal management status related attributes associated
with a Motion Control Axis.
Management Status
Attributes Motor Overload Protection Method
Thermal Model motor overload protection applies the measured motor current to
an internal motor thermal model to detect a motor overload condition.
I2T Overload motor overload protection applies an I2T calculation once the motor
current exceeds the product of the Motor Overload Limit and the Motor Rated
Continuous Current that indicates a motor overload condition.
Thermal Model inverter overload protection applies the measured motor current
to an internal inverter thermal model to detect an inverter overload condition.
I2T Overload inverter overload protection applies an I2T calculation once the
inverter current exceeds the product of the Inverter Overload Limit and the
Inverter Rated Continuous Current that indicates an inverter overload condition.
I2T Overload converter overload protection applies an I2T calculation once the
converter current exceeds the converter overload current limit that indicates a
converter overload condition.
This enumerated value indicates what bus regulator overload protection method is
being used by the CIP Motion device.
Thermal Model converter overload protection applies the measured bus regulator
current to an internal bus regulator thermal model to detect a bus regulator
overload condition.
I2T Overload bus regulator overload protection applies an I2T calculation once the
bus regulator current exceeds the factory set bus regulator overload current limit
that indicates a bus regulator overload condition.
Motor Capacity
The Motor Capacity attribute is the real-time estimate of the continuous rated
motor thermal capacity utilized during operation based on the motor thermal
model. A value of 100% would indicate that the motor is being used at 100% of
rated capacity as determined by the continuous current rating of the motor.
If the drive device applies I2T overload protection rather than thermal model
based overload protection, the Motor Capacity value is zero until the motor
current exceeds the product of the Motor Overload Limit and the Motor Rated
Continuous Current. Once in an overload condition the Motor Capacity
increases from 0 according to the I2T calculation. A value of 100% in this case
indicates that the drive has used up 100% of the motor's I2T overload capacity.
The motor overload protection method applied by the drive device is indicated by
the Motor Overload Protection Method attribute.
Inverter Capacity
The Inverter Capacity attribute is the real-time estimate of the continuous rated
inverter thermal capacity utilized during operation based on the inverter thermal
model. A value of 100% would indicate that the inverter is being used at 100% of
rated capacity as determined by the continuous current rating of the inverter. If
the drive device applies I2T overload protection rather than thermal model based
overload protection, the Inverter Capacity value is zero until the inverter current
exceeds the product of the factory set Inverter Overload Limit and the continuous
current rating of the inverter. Once in an overload condition the Inverter Capacity
increases from 0 according to the I2T calculation. A value of 100% in this case
indicates that the drive has used up 100% of the inverter's I2T overload capacity.
The inverter overload protection method applied by the drive device is indicated
by the Inverter Overload Protection Method attribute.
Converter Capacity
The Converter Capacity attribute is the real-time estimate of the continuous rated
converter thermal capacity utilized during operation based on the converter
thermal model. A value of 100% would indicate that the converter is being used at
100% of rated capacity as determined by the continuous current rating of the
converter.
If the CIP Motion device applies I2T overload protection rather than thermal
model based overload protection, the Converter Capacity value is zero until the
converter current exceeds its factory set overload current rating. Once in an
overload condition the Converter Capacity increases from 0 according to the I2T
calculation. A value of 100% in this case indicates that the converter has used up
100% of its I2T overload capacity.
The Bus Regulator Capacity attribute is the real-time estimate of the continuous
rated bus regulator thermal capacity utilized during operation based on the bus
regulator thermal model. A value of 100% would indicate that the bus regulator is
being used at 100% of rated capacity as determined by the continuous current
rating of the bus regulator.
If the CIP Motion device applies I2T overload protection rather than thermal
model based overload protection, the Bus Regulator Capacity value is zero until
the bus regulator current exceeds its factory set overload current rating. Once in an
overload condition the Bus Regulator Capacity increases from 0 according to the
I2T calculation. A value of 100% in this case indicates that the bus regulator has
used up 100% of its I2T overload capacity.
The bus regulator overload protection method applied by the device is indicated
by the Bus Regulator Overload Protection Method attribute.
Converter Temperature
% = (T-Tmin)(Tmax-Tmin)
Where,
% = (T-Tmin)(Tmax-Tmin)
Where,
T = Heatsink temperature
% = (T-Tmin)/(Tmax-Tmin)
Where,
T=Heatsink temperature
AC Line 1 Capacity
The AC Line Capacity is the real-time estimate of the continuous rated converter
thermal capacity for AC Line (Phase R) utilized during operation based on the
If the CIP Motion device applies I2T overload protection instead of thermal
model based overload protection, the AC Line 1 Capacity value remains zero until
the converter current exceeds its factory set overload current rating.
AC Line 2 Capacity
If the CIP Motion device applies to I2T overload protection rather than
thermal-model based overload protection, the AC Line 2 Capacity value is zero
until the converter current exceeds its factory set overload current rating. Once in
an overload condition, the AC Line 2 Capacity increases from 0 according to the
I2T calculation.
A 100% value indicates the converter used up 100% of the I2T overload capacity
for this phase.
AC Line 3 Capacity
based on the converter thermal model. A 100% value indicates the converter
components on Line 3 are used at 100% of the rated thermal capacity for this
phase.
If the CIP Motion device applies to I2T overload protection rather than
thermal-model based overload protection, the AC Line 3 Capacity value is zero
until the converter current exceeds its factory set overload current rating. Once in
an overload condition, the AC Line 3 Capacity increases from 0 according to the
I2T calculation.
A 100% value indicates the converter used up 100% of the I2T overload capacity
for this phase.
Converter Capacity attribute value represents how much of the converter’s rated
thermal capacity, associated with the converter thermal model, has been utilized.
Once the Converter Capacity value exceeds the Converter Overload Limit, the
drive can optionally trigger a predetermined Converter Overload Action.
The Converter Overload Limit can also be used by the drive to determine the
absolute thermal capacity limit of the converter, i.e. the Converter Thermal
Overload Factory Limit, which if exceeded, generates an Converter Thermal
Overload FL exception. The configured Converter Overload Limit also applies to
Converter L1, L2, and L3 Capacity, any of which are exceeded also results in a
Converter Thermal Overload FL exception.
Motor Overload Limit. In the case of the I2T overload protection method, the
motor overload condition occurs when the motor current, in percent of rated
continuous motor current, exceeds the Motor Overload Limit.
No explicit action is taken by the device in the overload condition if None is the
selected overload action. Selecting the Current Foldback action, however, results
in a reduction of motor current in proportion to the percentage difference
between Motor Capacity and the Motor Overload Limit, or in the case of the I2T
overload protection method, in proportion to the difference between the motor
current, in percent of rated continuous motor current, and the Motor Overload
Limit.
For the I2T overload protection method, the inverter overload condition occurs
when the inverter current exceeds the Inverter Overload Limit. The inverter
current is measured in percent of rated continuous inverter current.
The Inverter Overload Action enables mitigating the overload condition without
stopping operation. Inverter Overload Action functionality is independent of the
motor overload exception action functionality. Also generate an overload alarm
condition by exceeding the limits of the device power block thermal model that
includes switching losses that depend on the PWM Frequency. Also generate an
overload alarm condition by exceeding the limits of the device power block
thermal model that includes switching losses that have a dependency.
The device in the overload condition takes no action if None is the overload
action. Selecting the Current Foldback action reduces the inverter current in
proportion to the percentage difference between Inverter Capacity and the
Inverter. Overload Limit, or in the case of the I2T overload protection method, in
proportion to the difference between the inverter current, in percent of rated
continuous inverter current, and the Inverter Overload Limit.
If an inverter overload condition occurs due to the power block thermal model,
two additional overload actions can be applied. Selecting Reduce PWM Rate can
be used to reduce heat generated by switching losses in the inverter power
structure. When PWM –Foldback is selected the device first reduces the PWM
rate and then, if necessary, reduces the Inverter Thermal Current Limit.
Converter Overload Limit, or in the case of the I2T overload protection method,
in proportion to the difference between the converter current, in percent of rated
continuous converter current, and the Converter Overload Limit. In addition to
the configured Converter Overload Action being triggered by a Converter
Overload condition, the configured Converter Overload Action can also be
triggered by Converter L1, L2, or L3 Overload conditions.
See also
Drive Commissioning and The attribute tables contain attributes associated with auto-tuning and test
services applied to a Motion Control Axis Object instance. These attributes are
Tuning Attributes unique to the controller and do not require replication in the Motion Control
Device Axis Object.
Auto-Tune Configuration These are the attributes that are associated with auto-tune configuration of a
Motion Control Axis.
Attributes
System Damping
A Set or SSV to the System Damping attribute value calculates and updates the
System Bandwidth based on the current Drive Model Time Constant value
(DMTC) and then calculates and updates the applicable loop gain attribute
values. The System Damping attribute is designed to be used to implement a single
'knob' Manual Tuning procedure.
A larger damping factor increases the ratio between the inner and outer Loop
Bandwidths. In general, the System Damping attribute controls the dynamic
response of the overall control loop.
• Load Coupling
If the Load Coupling is a 'Compliant' selection and the Use Load Ratio bit
is set in the Gain Tuning Configuration Bits attribute, then the resultant
System Bandwidth above is divided by the Load Ratio value.
System Bandwidth /= (Load Ratio + 1)
The value for this attribute can also be updated through a Set service to the
Damping Factor attribute. When derived from the Damping Factor attribute, no
calculations are performed; the System Damping attribute value is simply updated.
A Set or SSV to the System Damping attribute also updates the Damping Factor
attribute value.
System Bandwidth
A Set or SSV to the System Bandwidth attribute value calculates and updates the
applicable loop gain attribute values based on the current System Damping (Z).
The System Bandwidth attribute is designed to be used to implement a single
'knob' Manual Tuning procedure. If the drive is configured for Velocity Loop
operation, the System Bandwidth is equivalent to the bandwidth of the velocity
loop. If the drive is configured for Position Loop operation, the System Bandwidth
is equivalent to the bandwidth of the position loop. In addition to calculating and
updating the Loop Bandwidth attribute values, an update to this attribute also
updates the Integral Bandwidth attributes as well as the Feedforward attributes
according to the Gain Tuning Configuration Bits setting.
The following configurations impact the calculations for this attribute as follows:
The System Bandwidth value can also be updated through a Set service to the
Position Servo Bandwidth or Velocity Servo Bandwidth attributes depending on
Axis Configuration. If configured for Position Loop, System Bandwidth is
updated by a set to Position Servo Bandwidth. If configured for Velocity Loop,
System Bandwidth is updated by a set to Velocity Servo Bandwidth. When derived
from either of these attributes, no calculations are performed; the System
Bandwidth attribute value is simply updated.
A Set or SSV to the System Bandwidth attribute also updates Position Servo
Bandwidth or Velocity Servo Bandwidth attributes depending on Axis
Damping Factor
The Damping Factor attribute value is used in calculating the maximum Position
and Velocity Servo Bandwidth values during execution of the Motion Run Axis
Tune (MRAT) instruction. In general the Damping Factor attribute controls the
dynamic response of the drive axis. When gains are tuned using a small damping
factor (such as 0.7), a step response test performed on the axis would demonstrate
under-damped behavior with velocity overshoot. A gain set generated using a
larger damping factor (such as 1.0) would produce a system step response that has
no overshoot and works well for most applications.
A set to the Damping Factor attribute also updates the System Damping attribute
value to support Manual Tuning.
The value for the Position Servo Bandwidth represents the unity gain bandwidth
of the position loop that is to be used by software Autotune function to calculate
the position loop gains. The unity gain bandwidth is the frequency beyond which
the position servo is unable to provide any significant position disturbance
correction. In general, within the constraints of a stable servo system, the higher
the Position Servo Bandwidth the better the dynamic performance of the system.
A maximum value for the Position Servo Bandwidth is generated by the MRAT
instruction. Computing gains based on this maximum value software Autotune
procedure results in a dynamic response in keeping with the current value of the
Damping Factor.
A set to the Position Servo Bandwidth attribute while configured for Position
Loop operation also updates the System Bandwidth attribute value to support
Manual Tuning.
The value for the Velocity Servo Bandwidth represents the unity gain bandwidth
of the velocity loop that is to be used by the software Autotune function to
calculate the velocity loop gains. The unity gain bandwidth is the frequency
beyond which the velocity servo is unable to provide any significant position
disturbance correction. In general, within the constraints of a stable servo system,
the higher the Velocity Servo Bandwidth is the better the dynamic performance of
the system. A maximum value for the Velocity Servo Bandwidth is generated by
the MRAT instruction. Computing gains based on this maximum value using the
software's Autotune procedure results in a dynamic response in keeping with the
current value of the Damping Factor.
A set to the Velocity Servo Bandwidth attribute while configured for Velocity
Loop operation also updates the System Bandwidth attribute value to support
Manual Tuning.
The value for the Drive Model Time Constant represents a lumped model time
constant for the drive's current loop and is used to calculate the Velocity and
Position Servo Bandwidth values. The Drive Model Time Constant is the sum of
the drive's current loop time constant, the feedback sample period, calculation
delay, and the time constant associated with the velocity feedback filter. This value
is set by software based on the specific drive amplifier and motor feedback
selection.
Since the bandwidth of the velocity feedback filter is determined by the resolution
of the feedback device, the value for the Drive Model Time Constant is smaller
when high resolution feedback devices are selected.
The value for the Converter Model Time Constant represents lumped model time
constant for the converter’s current loop and used to calculate Bus Voltage loop
bandwidth values. The Converter Model Time Constant is the sum of the
converter’s current loop time constant, and the calculation delay. This value is set
by software based on the specific converter selection.
(A set to the Converter Model Time Constant attribute while configured for
Active Current Control operation also updates the System Bandwidth attribute
value to support Manual Tuning.)
Application Type
This attribute specifies the type of motion control application and is used by
configuration and auto-tune software to set the Gain Tuning Configuration Bits
attribute that establishes the appropriate gain set the application.
The relationship between Application Type and Gain Tuning Configuration Bits
is described in the following tables.
The first table shows which Integrator Bandwidth values are applicable based on
the Application Type. Separate bits are defined in the Gain Tuning Configuration
Bits attribute to enable tuning of Position Integrator Bandwidth, Kpi, and
Velocity Integrator Bandwidth, Kvi. The Integrator Hold, iHold, setting applies
to any active integrators.
The next table shows which Feedforward values are applicable based on the
Application Type. Separate bits are defined in the Gain Tuning Configuration
Bits attribute to enable tuning of Velocity Feedforward, Kvff, and Acceleration
Feedforward, Kaff.
Finally, the Torque Low Pass Filter bit enables tuning of the Torque Low Pass
Filter Bandwidth. This bit is set for all Application Types except Custom,
Loop Response
A High setting for Loop Response is best suited for systems that demand the
highest level of control performance. Generally these are rigid mechanical systems
with relatively light load inertia/mass, for example, Load Ratio < 3.
A Medium Loop Response setting is best suited for general purpose control
applications with modest loading, for example Load Ratio < 10. This setting can
accommodate both rigid and compliant mechanical systems.
A Low setting for Loop Response is best suited for systems that control heavy load
inertia/mass, for example, Load Ratio > 10. The heavy load inertia/mass of these
systems generally required lower position and velocity loop bandwidths to
maintain stability and minimize motor heating.
Overall system performance can be improved for a given Loop Response setting by
compensating for the load inertia/mass by setting the System Inertia value to the
Total Inertia of the mechanical system.
Load Coupling
This Gain Tuning Configuration Bits attribute value is a bit field attribute that
controls the loop gain-tuning calculations.
Bits 4-7 may not be updated programmatically by SSV instruction unless the
Application Type is set to Custom.
The following table provides detailed descriptions for the bits of this attribute:
Use Load Ratio This bit determines if Load Ratio is used in calculating Total Inertia and System
Bandwidth calculations. If this bit is set, Load Ratio will be used in these
calculations. If this bit is clear, Load Ratio will not have any impact on Total
Inertia or System Bandwidth.
Tune Position Integrator The Tune Position Integrator bit attribute determines whether or not the
auto-tuning algorithm calculates a value for the Position Integrator Bandwidth.
If this bit is clear (false) the value for the Position Integrator Bandwidth is set to
zero, disabling the integrator.
Tune Velocity Integrator The Tune Velocity Integrator bit attribute determines whether or not tuning
algorithms calculate a value for the Velocity Integrator Bandwidth. If this bit is
clear (false) the value for the Velocity Integrator Bandwidth is set to zero,
disabling the integrator.
Tune Velocity Feedforward The Tune Velocity Feedforward bit attribute determines whether or not tuning
algorithms calculate a value for the Velocity Feedforward Gain. If this bit is clear
(false) the value for the Velocity Feedforward Gain is set to zero.
Tune Acceleration Feedforward The Tune Acceleration Feedforward bit attribute determines whether or not
tuning algorithms calculate a value for the Acceleration Feedforward Gain. If
this bit is clear (false) the value for the Acceleration Feedforward Gain is set to
zero.
See also
Hookup Test Configuration These are the attributes that are associated with hookup test configuration applied
to a Motion Control Axis.
Attributes
Hookup Test Distance
The Hookup Test Distance attribute is used by the Hookup Test service to
determine the amount of motion that is necessary to satisfy selected hookup test
process.
The Test Time attribute is used by the Hookup Test service to determine the
duration of motion that is necessary to satisfy selected Hookup Test process. This
value is typically set to around 10 seconds.
The Test Feedback Channel attribute is used by the Hookup Test service when
the 'Feedback' test is selected to determine which feedback channel to test.
See also
Hookup Test Result Attributes These are the attributes that are associated with hookup result status applied to a
Motion Control Axis
The Hookup Test Status attribute returns status of the last Run Hookup Test
service on the targeted drive axis. The Hookup Test Status attribute can be used to
determine when the hookup test service has successfully completed. Conditions
may occur, however, that make it impossible for the drive to properly perform the
operation. When this is the case, the test process is automatically terminated and a
test error is reported that is stored in the Hookup Test Status output parameter.
The Hookup Test Commutation Polarity reports if the UVW phasing of the
Encoder or Hall Sensor match the phasing of the Motor. If the motor and UVW
commutation phasing do not match the Commutation Polarity is Normal. If it is
determined that the phasing for the motor and commutation device do not match,
this parameter reports that the Commutation Polarity is Inverted. This value can
be used to configure the Commutation Polarity attribute.
The Hookup Test Feedback 1 Direction attribute reports the direction of axis
travel during the last hookup test as seen by the drive's feedback 1 device. A value
of 0 (positive) indicates that the direction of motion as observed by the drive's
feedback 1 device was positive, for example, increasing counts. Note that the value
for Hookup Test Feedback 1 Direction, as determined by the hookup test, does
not depend on the current feedback, motor, or motion polarity attribute
configuration. This value, combined with the user's definition of forward
direction, can be used to configure the various polarity attributes for the correct
directional sense.
The Hookup Test Feedback 2 Direction attribute reports the direction of axis
travel during the last hookup test as seen by the drive's feedback 2 device. A value
of 0 (positive) indicates that the direction of motion as observed by the drive's
feedback 2 device was positive, for example, increasing counts. Note that the value
for Hookup Test Feedback 2 Direction, as determined by the hookup test, does
not depend on the current feedback, motor, or motion polarity attribute
configuration. This value, combined with the user's definition of forward
direction, can be used to configure the various polarity attributes for the correct
directional sense.
See also
Inertia Test Configuration These are the attributes that are associated with inertia test configuration applied
to a Motion Control Axis.
Attributes
Tuning Select
Tuning Direction
This enumerated value determines the direction of the motion profile initiated by
the Inertia Test service associated with the Motion Run Axis Tuning (MRAT)
instruction.
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
The Tuning Travel Limit attribute is used by the Inertia Test service, associated
with the MRAT instruction, to limit the excursion of the axis during the test. If,
while performing the Inertia Test motion profile, the drive determines that the
axis will not be able to complete the profile before exceeding the Tuning Travel
Limit, the drive will terminate the profile and report that the Tuning Travel Limit
was exceeded through the Tune Status attribute. This does not mean that the
Tuning Travel Limit was actually exceeded, but that had the tuning process gone
to completion that the limit would have been exceeded.
Tuning Speed
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
The Tuning Speed attribute value determines the maximum speed used by the
Inertia Test service initiated motion profile. This attribute should be set to the
desired maximum operating speed of the motor prior to running the test. The
tuning procedure will measure maximum acceleration and deceleration rates based
on ramps to and from the Tuning Speed. Thus, the accuracy of the measured
acceleration and deceleration capability is reduced by tuning at a speed other than
the desired operating speed of the system.
Tuning Torque
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
The Tuning Torque attribute value determines the maximum torque used by the
Inertia Test service initiated motion profile. This attribute will be set to the
desired maximum safe torque level prior to running the test. The default value is
100%, which yields the most accurate measure of the acceleration and deceleration
capabilities of the system. In some cases a lower tuning torque limit value may be
desirable to limit the stress on the mechanics during the tuning procedure. In this
case the acceleration and deceleration capabilities of the system are extrapolated
based on the ratio of the tuning torque to the maximum torque output of the
system. Note that the extrapolation error increases as the Tuning Torque value
decreases.
Load Ratio
The Load Ratio attribute's value represents the ratio of the load inertia or mass to
the motor inertia or mass.
The value for Load Ratio may be known by the user or may be measured as part of
a software initiated Autotune process.
When Use Load Ratio bit is set in the Gain Tuning Configuration Bits attribute,
configuration software uses the value of Load Ratio to compute Total
Inertia/Mass and System Inertia attributes.
The Load Ratio value may also be used in calculations associated with System
Damping attribute.
Total Inertia
Total Inertia represents the combined inertia of the rotary motor and load in
engineering units.
Total Mass
Total Mass represents the combined mass of the linear motor and load in
engineering units.
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
See also
Inertia Test Result Attributes These are the attributes that are associated with inertia result status applied to a
Motion Control Axis.
Tune Status
The Tune Status attribute returns status of the last run Inertia Test service that
initiates a process on the targeted drive axis. The Tune Status attribute can, thus,
be used to determine when the Inertia Test initiated operation has successfully
completed. Conditions may occur, however, that make it impossible for the drive
to properly perform the operation. When this is the case, the Inertia Test process
is automatically aborted and a failure reported that is stored in the Tune Status
output parameter.
The Tune Acceleration Time attribute returns acceleration time in seconds for the
last successful Inertia Test service. This value is used to calculate the Tune
Acceleration attribute.
The Tune Deceleration Time attribute returns deceleration time in seconds of the
last successful Inertia Test service. This value is used to calculate the Tune
Deceleration attribute.
Tune Acceleration
The Tune Acceleration attribute returns the measured peak acceleration of the
last successful Inertia Test service. This value is used to calculate the Tune Inertia
Mass value of the axis, and is also used to determine the tuned values for the
Maximum Acceleration attribute. The Tune Acceleration value represents the
estimated acceleration at the configured torque limit of the system.
Tune Deceleration
The Tune Deceleration attribute returns the measured peak deceleration of the
last successful Inertia Test service. This value is used to calculate the Tune Inertia
Mass value of the axis, and is also used to determine the tuned values for the
Maximum Deceleration attribute. The Tune Acceleration value represents the
estimated deceleration at the configured torque limit of the system.
The Tune Inertia Mass value represents the estimated inertia or mass for the axis
as calculated from the measurements made during the last Motion Run Axis Tune
(MRAT) initiated tuning process. This value may also be set directly by software
tuning tools or programmatically.
Tune Friction
This floating point value represents the amount of friction measured during the
last successful Inertia Test profile. This value can be used to configure the Friction
Compensation feature of the drive. This value may also be set directly by software
tuning tools or programmatically.
This floating point value represents the active load offset measured during the last
successful Inertia Test profile. This value can be used to set the Torque Offset of
the drive to cancel out the active load torque/force. This value may also be set
directly by software tuning tools or programmatically.
This floating point value represents the load ratio calculated by MRAT based on
the measurements made during the last successful Inertia Test profile. The Load
Inertia Ratio attribute's value represents the ratio of the load inertia to the motor
inertia. Or in the case of a linear motor, the load mass over the motor mass. This
value can be used to set the Load Ratio attribute value as part of an Autotune
process. This value may also be set directly by software tuning tools or
programmatically.
See also
Motor Test Result Attributes These are the attributes that are associated with result status applied to a Motion
Control Axis.
The Motor Test Status attribute returns status of the last Run Motor Test service
on the targeted drive axis. The Motor Test Status attribute can be used to
determine when the motor test service has successfully completed. Conditions
may occur, however, that make it impossible for the drive to properly perform the
operation. When this is the case, the test process is automatically terminated and a
test error is reported that is stored in the Motor Test Status output parameter.
This floating point value represents the motor flux current of an induction motor
as measured by the Motor Test procedure.
This floating point value represents the slip speed of an induction motor as
measured by the Motor Test procedure.
This floating point value represents the measured Counter EMF (CEMF) of a PM
motor at Rated Speed by the Motor Test procedure.
This floating point value represents the phase-to-phase q-axis motor inductance
measured by the Motor Test procedure.
This floating point value represents the phase-to-phase d-axis motor inductance
measured by the Motor Test procedure.
This floating point value represents the phase-to-phase q-axis stator inductance of
the motor as measured by the Motor Test procedure expressed as a percentage of
the measured Nominal Inductance, Lq, at 25%, 50%, 75%, 100%, 125%, 150%,
175% and 200% rated continuous current.
This floating point value represents the phase-to-phase d-axis stator inductance of
the motor as measured by the Motor Test procedure expressed as a percentage of
the measured Nominal Inductance, Ld, at 100% rated continuous current.
This floating point value represents the maximum speed of the motor without
exceeding the operational DC bus overvoltage limit, as determined by the Motor
Test procedure.
This floating point value represents the change in motor Commutation Offset at
rated continuous current as measured by the Motor Test procedure.
See also
Faults and Alarms The following attribute tables contain fault and alarm related attributes associated
with a Motion Control Axis Object instance.
Attributes
APR Fault Attributes The following attribute table contains all APR (Absolute Position Recovery) fault
related attributes associated with a Motion Device Axis, including standard APR
faults and Rockwell Automation specific APR faults. APR Faults are conditions
that can occur during the device initialization process when trying to restore the
absolute position of an axis. Unlike Initialization Faults, these faults are
recoverable and may be cleared with a Fault Reset request.
Data
Usage Access T Default Min Max Semantics of Values
Type
Optional - E Get/GSV T WORD - - - Bit map:
0 = Reserved
1 = Memory Write Error
2 = Memory Read Error
3 = Feedback Serial Number
Mismatch
4 = Buffer Allocation Fault
5 = Scaling Configuration Changed
6 = Feedback Mode Changed
7 = Feedback Integrity Loss
8-15 = Reserved
The CIP APR Faults attribute is a bit mapped value that represents the state of all
standard APR (Absolute Position Recovery) faults. An APR fault is generated
when the system fails to recover the absolute position of the axis after power cycle,
reset, or reconnection. APR faults are detected during the initial configuration or
initialization of the drive axis.
When an APR fault occurs, the actual position of the axis is no longer correlated
to the position of the axis prior to the power cycle, reset, or reconnect. Examples of
standard APR faults are feedback serial number mismatch, and scaling
configuration change. APR faults are recoverable and can be cleared with a Fault
Reset request.
Data
Usage Access T Default Min Max Semantics of Values
Type
Optional - E Get/GSV T WORD - - - Bit map:
0 = Reserved
1 = Persistent Media Fault
2 = Firmware Error
3 = Feedback Battery Loss
4-15 = Reserved
The CIP APR Faults - RA attribute is a bit mapped value that represents the state
of all Rockwell Automation specific APR (Absolute Position Recovery) faults. An
APR fault is generated when the system fails to recover the absolute position of the
axis after power cycle, reset, or reconnection. APR faults are detected during the
initial configuration or initialization of the drive axis. When an APR fault occurs,
the actual position of the axis is no longer correlated to the position of the axis
prior to the power cycle, reset, or reconnect. These faults are specific to Rockwell
Automation APR implementation. APR faults are recoverable and can be cleared
with a Fault Reset request.
The following table defines a list of standard faults associated with the APR Faults
attribute.
0 -- Reserved -- This bit cannot be used since the Fault Code is defined by the associated
exception bit number and Fault Code of 0 means no fault condition is present.
1 Memory Write Error Error in saving absolute position data to NV memory.
2 Memory Read Error Error in reading absolute position data from NV memory.
3 Feedback Serial Number Position Feedback Serial Number does not match saved Feedback Serial
Mismatch Number.
4 Buffer Allocation Fault Caused when there is not enough RAM memory left to save APR data.
5 Scaling Configuration Scaling attribute configuration for this axis has changed and does not match the
Changed saved scaling configuration.
6 Feedback Mode Changed Feedback Mode has changed and does not match the saved Feedback Mode
configuration.
7 Feedback Integrity Loss The Feedback Integrity bit of CIP Axis Status attribute has transitioned from 1 to
0 during device operation.
8-15 -- Reserved --
The following table defines a list of Rockwell Automation specific faults associated
with the APR Faults-RA attribute.
0 -- Reserved -- This bit cannot be used since the Fault Code is defined by the associated
exception bit number and Fault Code of 0 means no fault condition is present.
1 Persistent Media Fault (L6x) - Means that all 6 sectors reserved for APR in Persistent Memory (for
example, NAND flash) are marked as bad. This is not a recoverable fault
condition.
2 Firmware Error Used to trap firmware errors that should never happen.
3 Feedback Battery Loss Battery powered Absolute Feedback device has failed to maintain absolute
position through a power cycle due to low battery level or disconnected battery
power.
4-15 -- Reserved --
The APR Fault exception names in the preceding tables have corresponding Logix
Designer APR Fault tag names. The naming conventions for the tag names are to
remove the spaces from the fault bit name and then append the "APRFault" suffix.
For example "Memory Write Error" becomes "MemoryWriteErrorAPRFault".
See also
Axis Exception Action These configuration attributes control the action performed by the device as a
result of an exception condition. A unique exception action is defined for each
Configuration Attributes
supported exception condition.
Required - All Set USINT [64] 4 (D) - - Enumeration for Drive Modes (D)
2 (E) 0 = Ignore (O)
4 (B) 1 = Alarm (O)
2 = Fault Status Only (O)
3 = Stop Planner (O)
4 = Disable (R)
5 = Shutdown (R)
Enumeration for Feedback Only
(E)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (R)
3 = N/A
4 = N/A
5 = Shutdown (R)
Enumeration for Bus Power
Converters (B)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (O)
3 = N/A
4 = Disable (R)
5 = Shutdown (R)
6...254 = Reserved
255 = Unsupported (O)
Data
Usage Access Default Min Max Semantics of Values
Type
Required - G Set USINT [64] 4 (D) - - Enumeration for Drive Modes (D)
Optional - NED 2 (E) 0 = Ignore (O)
4 (B) 1 = Alarm (O)
2 = Fault Status Only (O)
3 = Stop Planner (O)
4 = Disable (R)
5 = Shutdown (R)
Enumeration for Feedback Only
(E)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (R)
3 = N/A
4 = N/A
5 = Shutdown (R)
Enumeration for Bus Power
Converters (B)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (O)
3 = N/A
4 = Disable (R)
5 = Shutdown (R)
6...254 = Reserved
255 = Unsupported (O)
Data
Usage Access Default Min Max Semantics of Values
Type
Required - All Set USINT 4 (D) - - Enumeration for Drive Modes (D)
[64] 2 (E) 0 = Ignore (O)
4 (B) 1 = Alarm (O)
2 = Fault Status Only (O)
3 = Stop Planner (O)
4 = Disable (R)
5 = Shutdown (R)
Enumeration for Feedback Only
(E)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (R)
3 = N/A
4 = N/A
5 = Shutdown (R)
Enumeration for Bus Power
Converters (B)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (O)
3 = N/A
4 = Disable (R)
5 = Shutdown (R)
6...254 = Reserved
255 = Unsupported
Data
Usage Access Default Min Max Semantics of Values
Type
Required - G Set USINT [64] 4 (D) - - Enumeration for Drive Modes (D)
Optional - NED 2 (E) 0 = Ignore (O)
4 (B) 1 = Alarm (O)
2 = Fault Status Only (O)
3 = Stop Planner (O)
4 = Disable (R)
5 = Shutdown (R)
Enumeration for Feedback Only
(E)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (R)
3 = N/A
4 = N/A
5 = Shutdown (R)
Enumeration for Bus Power
Converters (B)
0 = Ignore (O)
1 = Alarm (O)
2 = Fault Status Only (O)
3 = N/A
4 = Disable (R)
5 = Shutdown (R)
6...254 = Reserved
255 = Unsupported
See also
Axis Exception Action The Axis Exception Action attributes are 64-element array of enumerated bytes
that specify the action to take by the device for the associated standard or
manufacturer specific exception, respectively. For a given exception, certain
exception actions may not be supported. Attempting to do so results in an "Invalid
Attribute Value" service error code (0x09). Each device product must specify the
available actions for each exception that is supported. If a specific exception is not
supported by the device, the only valid exception action enumeration is
'Unsupported'. Attempting to write any other value to the element associated with
an unsupported exception results in an "Invalid Attribute Value" service error code
(0x09) that is generated while the project is online with the controller. For drives
that support Rockwell Automation specific axis exceptions, the 64-element CIP
Axis Exception Action - RA and CIP Axis Exception Action 2 - RA arrays ares
sent to the drive device.
0 Optional Ignore Ignore instructs the device to completely ignore the exception
condition. For some exceptions that are fundamental to the
operation of the axis, it may not be possible to Ignore the condition.
1 Optional Alarm Alarm action instructs the device to set the associated bit in the Axis
Alarm word but to otherwise not impact axis behavior. For some
exceptions that are fundamental to the operation of the device, it
may not be possible to select this action or any other action that
leaves device operation unaffected.
2 Optional (BD) Fault Status Only Fault Status Only instructs the device to set the associated bit in the
Required (E) Axis Faults word but to otherwise not impact axis behavior. It is up
to the controller to programmatically bring the axis to a stop in this
condition. For some exceptions that are fundamental to the
operation of the device, it may not be possible to select this action
or any other action that leaves device operation unaffected.
Converters (B) executing a Fault Status Only exception action
continue to supply DC Bus Power and do not set the DC Bus Unload
bit in Axis Status attribute and therefore do not disable drives in the
converter's Bus Sharing Group.
3 Optional (FPV) Stop Planner Stop Planner instructs the drive device (D) to set the associated bit
in the Axis Faults word and instructs the Motion Planner to perform
a controlled stop of all planned motion at the configured Max Decel
rate. For some exceptions that are fundamental to the operation of
the device, it may not be possible to select this action or any other
action that leaves device enabled.
4 Required (BD) Disable Disable action results in the drive device (D) both setting the
associated bit in the Axis Faults word and bringing the axis to a stop
based on the factory set "best" available stopping method. This
"best" stopping method includes both the method of decelerating
the motor to a stop and the final state of the power structure given
the expected level of control still available. The level of axis control
available depends on the specific exception condition and on the
configured control mode.
The available deceleration methods are defined by the Stopping
Action attribute. (See the Stopping Action section following this
table for additional information.)
If the application requires exception action that is a more severe
stopping action than the factory set "best" method, the controller
will initiate that action.
If the application requires an exception action that is less severe
than the factory set "best" method, the controller will configure the
device axis instance for a Minor Fault exception action and handle
the fault directly. This may put device and motor components at risk
and is only be allowed by the device when there is an opportunity
for the device to remain operational. This is important in
applications where the value of the product is higher than the value
of the motor or device.
When the Disable exception action is applied to a converter device
(B), stopping action is not applicable (0 = No Action). The final
states of Disable or Shutdown for the converter are applicable,
however, with Shutdown executing the configured Shutdown
Action. In the Shutdown case, the DC Bus Unload bit of the
converter's Axis Status attribute is set to generate a Bus Sharing
exception on all drives in the converter's Bus Sharing Group.
When multiple major faults occur with different stopping actions,
the most severe of the associated stopping actions is applied, that
is, the stopping action that requires the lowest level of control
functionality. This rule also applies to the Stopping Action
associated with a Disable Request.
5 Required (All) Shutdown While the final axis state after a Major Fault is the Major Faulted
state, the Shutdown Exception Action forces the power structure
into the Shutdown state, immediately disabling the drive's power
structure. If Shutdown Action is configured to do so, this action also
drops DC Bus power to the drive's power structure. Therefore, the
Shutdown action overrides the drive's best stopping method. An
explicit Shutdown Reset is required to restore the drive to an
operational state.
6-254 Reserved -
255 Unsupported The Unsupported Exception Action is the value assigned to
Exceptions that are not supported by the device. Trying to assign an
Exception Action other than Unsupported to an exception that is not
supported by the device results in an "Invalid Attribute Value"
service error code (0x09).
Stopping action
1. Ramp Decel
3. Coast
In general, the "best" stopping action is the most controlled deceleration method
still available given the exception condition.
The final state of the power structure in response to the Major Fault exception
action can be any one of the following states that are listed in decreasing levels of
control functionality:
The "best" final state of the power structure is the state with the most control
functionality still available given the exception condition.
In all these final states a fault reset must be executed before the axis can be restored
to enabled operation and commanded to move.
If a Start Inhibit condition is present at the time of the exception, the best final
state for the exception action can only be Disable or Shutdown.
The specific stopping action and final state associated with a given Disable
exception action is captured in the Axis Fault Action attribute that is included in
the Fault Log record. Axis Fault Action enumerations are as follows:
Enumeration Description
Stop Action Enumerations 0 = No Action
1 = (reserved)
2 = Ramped Stop
3 = Torque Limited Stop
4 = Coast
State Change Enumerations 0 = No Action
1 = Hold
2 = Disable
3 = Shutdown
See also
Exceptions on page 47
Configuration Fault Attributes These are the configuration fault related attributes associated with a Motion
Control Axis.
Data
Usage Access T Default Min Max Semantics of Values
Type
CIP Error code returned by the erred set list service to the module.
Attribute Error ID
Data
Usage Access T Default Min Max Semantics of Values
Type
See also
CIP Error Codes These are general CIP error codes that can be returned by the Attribute Error
Code.
See also
Exception Factory Limit Info These are the exception limit related attributes associated with a Motion Control
Axis. Exception Limit attributes define the conditions under which a
Attributes
corresponding exception is generated during motion axis operation that has the
potential of generating either a fault or alarm. They are typically associated with
temperature, current, and voltage conditions of the device that are continuous in
nature. Factory Limits (FL) for exceptions are usually hard coded in the device and
typically result in a major fault condition. User Limits (UL) for exceptions are
configurable and typically used to generate a minor fault, or alarm condition. For
this reason, the User Limits are generally set inside the corresponding Factory
Limits. Note that the triggering of a User Limit exception does not preclude
triggering of the corresponding Factory Limit exception; the two exception trigger
conditions are totally independent of one another.
Returns the Factory Limit for the Motor Overspeed Factory Limit exception
based on a factory set value determined by the Rotary Motor Rated Speed or
Rotary Motor Max Speed attribute values, or by operational speed limits enforced
by the drive vendor. The drive may take the minimum of any of these values as the
Factory Limit.
When PM Motor Rotary Bus Overvoltage Speed and PM Motor Rotary Max
Extended Speed attributes are supported and non-zero, the drive uses these values
to determine the Rotary Motor Overspeed Factory Limit. The PM Motor
Extended Speed Permissive value determines which limit to apply. If the PM
Motor Extended Speed Permissive is False, the Rotary Motor Overspeed Factory
Limit will be based on the PM Motor Rotary Bus Overvoltage Speed. If the PM
Motor Extended Speed Permissive is True, the Rotary Motor Overspeed Factory
Limit will be based on the PM Motor Rotary Max Extended Speed value.
The Operational Speed Limit on all Rockwell Automation drive products is 600
Hz. The following formula is used to calculate the operational speed limit:
Operational Speed Limit (RPM) = 590 (Hz) * 120 / Rotary Motor Poles
Returns the Factory Limit for the Motor Overspeed Factory Limit exception
based on a factory set value determined by the Linear Motor Rated Speed or
Linear Motor Max Speed attribute values, or by operational speed limits enforced
by the drive vendor. The drive may take the minimum of any of these values as the
Factory Limit.
When PM Motor Linear Bus Overvoltage Speed and PM Motor Linear Max
Extended Speed attributes are supported and non-zero, the drive uses these values
to determine the Linear Motor Overspeed Factory Limit. The PM Motor
Extended Speed Permissive value determines which limit to apply. If the PM
Motor Extended Speed Permissive is False, the Linear Motor Overspeed Factory
Limit will be based on the PM Motor Linear Bus Overvoltage Speed. If the PM
Motor Extended Speed Permissive is True, the Linear Motor Overspeed Factory
Limit will be based on the PM Motor Linear Max Extended Speed value.
The Motor Overtemperature Factory Limit attribute returns the Factory Limit
for the Motor Overtemperature FL exception based on a factory set value related
to the Motor Max Winding Temperature of the motor.
The Motor Thermal Overload Factory Limit attribute returns the Factory Limit
for the Motor Thermal Overload FL exception based on a factory set value related
to the Motor Overload Limit rating.
The Inverter Overtemperature Factory Limit returns the Factory Limit for the
Inverter Overtemperature FL exception.
The Inverter Thermal Overload Factory Limit returns the Factory Limit for the
Inverter Thermal Overload FL exception based on a factory set value related to the
Inverter Overload Limit rating.
The Converter Thermal Overload Factory Limit returns the Factory Limit for the
Converter Thermal Overload FL exception.
The Converter Ground Current Factory Limit attribute returns the Factory Limit
for the Converter Ground Current FL exception.
The Bus Regulator Overtemperature Factory Limit returns the Factory Limit for
the Bus Regulator Overtemperature FL exception.
The Bus Regulator Thermal Overload Factory Limit attribute returns the Factory
Limit for the Bus Regulator Thermal Overload FL exception.
The Bus Overvoltage Factory Limit returns the Factory Limit for the Bus
Overvoltage FL exception.
The Feedback Signal Loss Factory limit attribute returns the Factory Limit for the
Feedback Signal Loss FL exception.
The Feedback Data Loss Factory Limit attribute returns the Factory Limit for the
Feedback Data Loss FL exception.
The Control Module Overtemperature Factory Limit returns the Factory Limit
for the Control Module Overtemperature FL exception.
The Converter Pre-Charge Overload Factory Limit returns the Factory Limit for
the Converter Pre-Charge Overload FL exception.
The AC Line Overvoltage Factory Limit attribute returns the factory set high
voltage limit as a percent of Converter Rated Input Voltage for the AC line source.
The AC Line Undervoltage Factory Limit attribute returns the factory set low
voltage limit as a percent of Converter Rated Input Voltage for the AC line source.
The AC Line Undervoltage Factory Limit - Alternate returns the factory set low
voltage limit as a percent of Converter Rated Input Voltage for the alternate AC
line source.
The AC Line High Freq Factory Limit attribute returns the factory-set high
frequency limit as the difference from the nominal AC line frequency.
The AC Line Low Freq Factory Limit attribute returns the factory set low
frequency limit as the difference from the nominal AC line frequency.
The AC Line High Freq Factory Limit - Alternate attribute Returns the factory
set high frequency limit
Returns the factory set low frequency limit as the difference from the nominal
alternate AC line source frequency.
The Converter Heatsink Overtemp Factory Limit returns the Factory Limit for
the regenerative converter power structure heatsink temperature. Exceeding this
value generates a Converter Overtemperature FL exception.
The AC Line Overload Factory Limit attribute Returns the Factory Limit for
Line 1, 2, and 3 components as a percent of their rated thermal capacity.
Exceeding this value generates a Converter Thermal Overload FL exception.
The AC Line Resonance Factory Limit attribute Returns the Factory Limit for
the AC Line Resonance FL exception as a percentage of the Converter Output
Rated Current. The AC Line Resonance FL exception occurs when the current
flowing through the AC line filter in the resonant frequency band, exceeds the
factory limit for vendor specified period.
See also
Exceptions on page 47
Exception User Limit These are the exception user limit configuration related attributes associated with
a Motion Control Axis.
Configuration Attributes
Motor Phase Loss Limit
Sets the minimum motor phase current for the Motor Phase Loss exception. The
current in each motor phase must exceed this value during the motor phase loss
test or a Motor Phase Loss exception occurs. Decreasing this attribute's value
lowers sensitivity to phase loss conditions. A value of 0 will effectively disable the
motor phase loss test.
Sets the Overspeed User Limit relative to the Rotary Motor Rated Speed or Linear
Motor Rated Speed that is allowable before throwing a Motor Overspeed UL
exception.
Sets User Limit for the Feedback Noise Overload UL exception. Example of Noise
Counts would be simultaneous transitions of the A and B channel of a quadrature
encoder feedback device.
Sets User Limit for the Feedback Signal Loss UL exception. Feedback interface
hardware typically monitor average voltage levels on incoming signals. Feedback
Signal Loss conditions occur when the average voltage levels drop below a
percentage of voltage drop allowed by the Feedback Signal Loss Factory Limit.
Sets User Limit for the Feedback Data Loss UL exception. For digital feedback
devices, feedback interface hardware monitors the integrity of data transferred
over the serial connection to the feedback device. Feedback Data Loss conditions
occur when two or more consecutive data packets are lost or corrupted.
Sets the high voltage limit as a percent of Converter Rated Input Voltage for the
AC line source.
Sets the low voltage limit as a percent of Converter Rated Input Voltage for the
AC line source.
Sets the high voltage limit as a percent of Converter Rated Input Voltage for the
alternate AC line source.
Sets the low voltage limit as a percent of Converter Rated Input Voltage for the
alternate AC line source.
Sets the high frequency limit as the difference from the nominal AC line
frequency.
Sets the low frequency limit as the difference from the nominal AC line frequency.
Sets the high frequency limit as the difference from the nominal alternate AC line
source frequency.
Sets the low frequency limit as the difference from the nominal alternate AC line
source frequency.
Sets a User Limit for the regenerative converter power structure heatsink
temperature. Exceeding this value generates a Converter Overtemperature UL
exception.
Sets a User Limit for thermal overload of Line 1, 2, and 3 components as a percent
of their rated thermal capacity. Exceeding this value generates a Converter
Thermal Overload UL exception.
Sets the User Limit for the AC Line Resonance UL exception based on a
percentage of the Converter Output Rated Current. The AC Line Resonance UL
exception occurs when the current flowing through the AC line filter in the
resonant frequency band, exceeds the user limit for a vendor specified period.
See also
Exceptions on page 47
Exception, Fault and Alarm These are the exception, fault, and alarm related attributes associated with a
Motion Control Axis. Exceptions are conditions that can occur during axis
Attributes
operation that have the potential of generating faults or alarms based on the
Exception Action configuration.
A bit map that represents the state of all standard runtime faults. The bit map is
identical to that of the CIP Axis Exceptions attribute. Fault bits when set are
latched until a fault reset occurs. A fault reset clears the runtime fault bits, but the
bits set again immediately if the underlying exception condition is still present.
Any exceptions whose CIP Axis Exception Action is configured to ignore or
report as alarms do not appear in this attribute.
This attributes provides a 64-bit extension to the CIP Axis Faults attribute bit
map representing the state of all standard runtime faults. This bit map is identical
to that of the CIP Axis Exceptions 2 attribute. Fault bits when set are latched until
a fault reset occurs. A fault reset clears the runtime fault bits, but the bits set
again immediately if the underlying exception condition is still present.
A bit map that represents the state of all Rockwell Automation specific runtime
faults. Fault bits when set are latched until a fault reset occurs. A fault reset clears
the runtime fault bits, but the bits set again immediately if the underlying
exception condition is still present. Any exceptions whose CIP Axis Exception
Action is configured to ignore or report as alarms do not appear in this attribute.
This attributes provides a 64-bit extension to the CIP Axis Faults 2 attribute bit
map that represents the state of all Rockwell Automation specific runtime faults.
Fault bits when set are latched until a fault reset occurs. A fault reset clears the
runtime fault bits, but the bits set again immediately if the underlying exception
condition is still present. Any exceptions whose CIP Axis Exception Action is
configured to ignore or report as alarms do not appear in this attribute.
A bit map that represents the current state of all standard alarm conditions. The
bit map is identical to that of the CIP Axis Exceptions attribute. Only exception
conditions whose Axis Exception Action is configured to report as an alarm
appear in this attribute, and will not be reported in the CIP Axis Faults attribute.
Alarm bits when set are not latched and will clear as soon as the underlying
exception condition is corrected.
This attributes provides a 64-bit extension to the CIP Axis Alarms attribute bit
map representing the current state of all standard alarm conditions. The bit map is
identical to that of the CIP Axis Exceptions attribute. Only exception conditions
whose CIP Axis Exception Action is configured to report as an alarm appear in
this attribute, and will not be reported in the CIP Axis Faults attribute. Alarm bits
when set are not latched and will clear as soon as the underlying exception
condition is corrected.
A bit map that represents the current state of all Rockwell Automation specific
alarm conditions. Only exception conditions whose Axis Exception Action is
configured to report as an alarm appear in this attribute, and will not be reported
in the CIP Axis Faults attribute. Alarm bits when set are not latched and will clear
as soon as the underlying exception condition is corrected.
Rockwell Automation Publication MOTION-RM003K-EN-P - July 2019 407
Chapter 4 CIP Axis Attributes
This attributes provides a 64-bit extension to the CIP Axis Alarms 2 RA attribute
bit map that represents the current state of all Rockwell Automation specific
alarm conditions. Only exception conditions whose CIP Axis Exception Action is
configured to report as an alarm appear in this attribute, and will not be reported
in the CIP Axis Faults attribute. Alarm bits when set are not latched and will clear
as soon as the underlying exception condition is corrected.
See also
Exceptions on page 47
Initialization Faults Attributes These are the initialization fault related attributes associated with a Motion
Control Axis. Initialization Faults are conditions that can occur during the device
initialization process that prevent normal operation of the device.
A bit map that represents the state of all standard initialization faults. These faults
prevent any motion, and do not have configurable fault actions. Examples of
initialization faults are corrupted memory data, calibration errors, firmware
startup problems, or an invalid configuration attribute value. Initialization faults
cannot be cleared with a Fault Reset service, although a power-cycle provides a
new attempt at initialization.
A bit map that represents the state of all Rockwell Automation specific
initialization faults. These faults prevent any motion, and do not have
configurable fault actions. Examples of initialization faults are corrupted memory
data, calibration errors, firmware startup problems, or an invalid configuration
attribute value. Initialization faults cannot be cleared with a Fault Reset service,
although a power-cycle provides a new attempt at initialization.
See also
Standard Initialization Faults This table defines a list of standard faults associated with the Initialization Faults
attribute.
See also
Rockwell Automation Specific This table defines a list of Rockwell Automation specific faults associated with the
Initialization Faults Initialization Faults-RA attribute.
3 Feedback Communication Startup Communications with a smart encoder could not be established.
4 Feedback Absolute Overspeed Excessive speed was detected in the battery-backed encoder while
power was off.
5 Feedback Absolute Power Off Travel The power-off travel range of the battery-backed encoder has been
exceeded.
6 Feedback Absolute Startup Speed The absolute encoder was not able to accurately determine the
position after power-up due to speed greater than 100 RPM.
7 Commutation Offset Uninitialized The commutation offset stored in a third-party motor has not been
initialized.
8 Reserved -
9 Reserved -
10 Reserved -
11 Reserved -
12 Invalid FPGA Image The FPGA image is incompatible with hardware operation.
13 Invalid Board Support Package The board support package is incompatible with hardware operation.
14 Invalid Safety Firmware The safety firmware is not compatible with the drive firmware, or the
main safety firmware is missing.
15 Power Board Power Board checksum error.
16 Illegal Option Card The Main Control Board has detected an illegal option installed in the
port.
17 Option Storage Checksum Option data storage checksum failed.
18 Reserved -
19 Module Voltage Mismatch IAM detects a voltage rating mismatch on the modular backplane.
20 Unknown Module Unknown module is detected on the modular backplane.
21 Factory Configuration Error Factory Configuration Data is missing or invalid.
22 Illegal Address Invalid Ethernet IP Address configuration or device Node Address is
out of range (>254).
23 Series Mismatch SERCOS AMs have been detected by the CIP IAM.
24 Open Slot IAM detects an open slot on the modular backplane.
25-31 Reserved -
See also
Module/Node Fault and Alarm These are the module/node fault and alarm related attributes associated with a
Motion Control Axis.
Attributes
Module Fault Bits
This bit field is a roll-up of module scoped fault conditions that can include
synchronization faults detected on either side of the CIP Motion connection. All
defined Node Fault Codes are mapped into bits in this attribute. The controller
generally applies a shutdown fault action when a Module Fault occurs and
recovery generally requires module reconnection or reconfiguration.
The following table defines a list of conditions associated with the Module Fault
Bits attributes. While the Module Fault Bits attribute is marked as Required in the
CIP Motion device implementation, support for each of the individual fault
conditions therein is left Optional. In this table the terms motion module and
motion device are used synonymously.
4-6 Reserved -
7 Conn Format Fault Data Format Error This fault bit indicates that an error has occurred in the
data format between the controller and the device, for
example, a Format Revision mismatch.
8 Local Mode Fault - The Local Mode Fault is set when the controller is locked
in Local Mode operation.
9 CPU Watchdog Fault Processor Watchdog The Processor Watchdog Fault bit indicates that the
Fault processor associated with the device node has
experienced an excessive overload condition that has
tripped the associated processor watchdog mechanism.
10 Clock Jitter Fault - The Clock Jitter Fault bit is set when there is excessive
clock jitter between the controller and the motion device.
11 Cyclic Read Fault - The Cyclic Read Fault is set when the controller detects a
runtime error associated with the Cyclic Read mechanism.
12 Cyclic Write Fault - The Cyclic Write Fault is set when the controller detects a
runtime error associated with the Cyclic Write
mechanism.
18 Duplicate Address Duplicate Address Fault The Duplicate Address Fault bit indicates that a motion
Fault device node has been detected on the network that uses
the same Node Address as this device node. For Ethernet,
this address would be the IP Address of the device.
19-31 Reserved -
This bit field is a roll-up of module scoped alarm conditions that can include
synchronization alarms detected on either side of the CIP Motion connection. All
defined Node Alarm Codes are mapped into bits in this attribute.
The following table defines a list of conditions associated with the Module Alarm
Bits attributes. While the Module Alarm Bits attribute is marked as Required in
the CIP Motion device implementation, support for each of the individual fault
conditions therein is left Optional. In this table the terms motion module and
motion device are used synonymously.
See also
Exceptions on page 47
Feedback Attributes The following position feedback related attribute tables associated with a Motion
Control Axis apply to various feedback device and feedback interface
technologies.
Other modern feedback interfaces supported are: Hiperface and Hiperface DSL
(by Stegmann) and EnDat 2.1 and EnDat 2.2 (by Heidenhain). The Usage
column for a feedback attribute is based on the context of the Feedback Type.
Abbreviations for the various Feedback Types are defined in this table:
This section defines the minimal set of required attributes to support CIP Motion
device interchangeability. This guarantees that there is sufficient parametric data
provided by the controller for any CIP Motion compliant drive to effectively
interface to a wide range of feedback device types.
Multiple feedback device interfaces are currently defined by the Motion Control
Axis per axis to serve specific control or master feedback functions. These feedback
devices are accessed using their assigned logical channels, for example, Feedback 1
and Feedback 2. Each logical feedback channel is mapped to a physical feedback
interface port of the device, for example Port 1, and Port 2.
When the Control Mode is set to something other than No Control, Feedback 1
is associated with the motor mounted feedback device while Feedback 2 is
associated with the load-side or machine mounted feedback device. Feedback 1 is
always required for PM Motor commutation.
When Control Mode is set to No Control for a Motion Control Axis, different
logical feedback channels can be used as the master feedback source, for example,
Feedback 1 and Feedback 2. Generally, Feedback 1 is used.
To minimize the length of the feedback attribute tables below, the letter n in the
generic Feedback n attribute name is used to specify the associated feedback
channel number. Valid channel numbers for open standard feedback attributes of
the Motion Control Axis are 1, 2, 3 and 4.
Attribute IDs are assigned based on the channel number. Support for feedback
interface channels 1, 2, 3 and 4 are optional in the device implementation. If no
feedback interface channel is present in the device the associated set of feedback
channel attributes are not applicable.
See also
Feedback Configuration The Feedback Configuration attributes determines how the various available
feedback channels are used to implement the selected Control Mode.
Attributes
Feedback Configuration
The Feedback Configuration attribute sets the initial value for Feedback Mode.
This attribute contains a 4-bit enumerated value that determines how the various
logical feedback channels are used to implement the selected Control Mode for
this axis instance.
Feedback Mode
The Feedback Mode attribute determines how the various available feedback
channels are used to implement the selected Control Mode. Currently bits 0-3 are
used to enumerate the Feedback Mode configuration. Bits 4-5 are used to select
the position feedback data type. Bit 5-7 are reserved for future use.
This attribute is transferred to the device as part of the Cyclic data block.
This attribute contains the 4-bit enumerated Feedback Mode field derived from
the Feedback Configuration attribute that determines how the various logical
feedback channels are used to implement the the selected Control Mode for this
axis instance. The attribute also contains a 2-bit enumerated field, Feedback Data
Type, which determines the Actual Position data type that is to be included in the
Device-to-Controller connection Cyclic Data Block, with options for 32-bit or
64-bit signed integer representations. The Feedback Data Type field value is
determined by the Extended Position Feedback bit (bit 20) of the Axis Features
attribute, and is not user configurable in this implementation.
When modified programmatically, using SSV, only the Feedback Mode field value
can be changed, all other bits are ignored by the instruction. Furthermore, the
Feedback Mode field value, cannot be set to an enumeration that the Feedback
Configuration cannot support. Attempting to do so results in the SSV instruction
generating a Minor Fault. For example if the Feedback Configuration is set for
Motor Feedback, the Feedback Mode cannot be changed to Load Feedback since
that feedback channel has not been configured.
The Feedback Master Select attribute determines the Logical channel assigned to
this axis instance when setting the Feedback Mode to Master Feedback.
The Feedback Unit Ratio attribute is the number of Feedback 1 Units per
Feedback 2 Unit. This value is also used by the drive to convert between feedback
2 counts to feedback 1 counts when configured for load feedback or dual feedback
operation.
The Feedback N Resolution Unit attribute is the unit of measure for feedback
resolution used by the Feedback n Cycle Resolution attribute. If selecting
Units/Cycle, the Feedback n Cycle Resolution is expressed in Nanometers/Cycle
for linear feedback devices. This selection is not applicable to rotary devices. If
selecting Bits/Units, the Feedback n Cycle Resolution is expressed as 2n Cycles per
revolution of a rotary feedback device, where n is the number of bits in the binary
position representation of the device. This selection is not applicable for linear
devices.
Feedback n Unit
The Feedback n Unit attribute is a unit of measure for the designated feedback
device. The Feedback Unit for Feedback 1 and any redundant feedback device for
Feedback 1 must be scalable to the configured Motor Unit; if the Motor Unit is
set to Rev, Feedback 1 Unit must be set to Rev; if Motor Unit is set to Meter,
Feedback 1 Unit will be set to Meter. Feedback devices with a Feedback Unit of
Rev are considered "rotary" devices, while Feedback devices with a Feedback unit
of Meter are considered "linear" devices.
The Feedback n Port Select attribute maps the logical Feedback Channel n to a
physical Feedback Port ID. A Feedback Port ID is assigned to each feedback
interface port of the device by the drive vendor. If this attribute is not supported
by the drive, the drive vendor shall hardcode the feedback port mapping to the
logical Feedback Channels for each axis instance. Supporting the Feedback n Port
Select attribute allows flexibility to map the logical Feedback Channels to different
Feedback Ports.
Feedback n Type
The Feedback n Type attribute identifies the type of feedback device connected to
the associated Feedback interface. Drive support for any individual feedback types
In the case of a motor mounted feedback device, if Motor Data Source is Motor
NV or Drive NV, the Feedback 1 Type may not be known to the controller but is
known by the drive, so the drive can operate in this case without specifying the
Feedback 1 Type.
In the case of a motor mounted feedback device, if the Motor Data Source is
Datasheet or Database, an unspecified Feedback 1 Type, when received by the
drive device during configuration, indicates that the motor feedback configuration
has not been defined and therefore results in a Configuration Fault indicating an
Invalid Attribute Value.
Feedback n Polarity
user's definition of positive travel and can be used in conjunction with the Motor
Polarity bit to provide negative feedback, when this feedback channel is used for
closed loop control.
The Feedback n Startup Method attribute determines how the device applies the
feedback count value during drive startup. When configured for Incremental
mode, the device zeros the feedback count accumulator at power-up. The first
Actual Position value sent to the controller in the Cyclic Data Block of the
Device-to-Controller connection at power-up is zero. This is an indication to the
controller that the drive has been power-cycled and the drive axis needs to be
homed to establish a machine reference position.
When configured for Absolute mode, the device initializes the feedback count
accumulator at power-up to the absolute feedback position value read from the
feedback device. When the feedback device's absolute position range is less than
the 32-bit signed integer representation of the feedback count accumulator, the
absolute position is sign extended to a 32-bit signed value. While there are many
Feedback Types that support Absolute startup, there are a few strictly incremental
types that do not: Digital AqB, and Sine/Cosine.
Some device vendors tie the Feedback Startup Method to the Feedback Type
selection. In these cases, an attempt by the controller to incorrectly configure the
Feedback Startup Method will generate a General Status error of Invalid Attribute
Value.
The default Feedback Startup Method value depends on the associated Feedback
Type according to the following table:
Cycles for a Digital AqB device represent the 'line' resolution of the encoder.
Cycles for a Sin/Cos device represent the sinusoidal 'cycle' resolution of the
encoder. Cycles for a Resolver is the 'pole' count of the device. For digital serial
(e.g. SSI) or parallel absolute feedback devices, Cycles represent the 'step' or 'count'
resolution of the device.
The default Feedback Resolution value used for the Feedback Cycle Resolution
attributes depends on the associated Feedback Type and Feedback Unit selection
according to the following table:
Feedback n Turns
The Feedback n Turns attribute is the maximum number of shaft turns specified
for a rotary absolute feedback device to maintain its absolute position reference.
Typical rotary absolute feedback devices specify an absolute number of turns that
typically range from 1 to 4096 in powers of 2. This attribute can be used by the
control system to determine the maximum Feedback Count range of the absolute
feedback device, this being the product of the feedback cycle resolution,
interpolation, and turns.
Feedback n Length
The Feedback n Data Length attribute is the number of feedback data bits
transferred over the digital serial or parallel data interface channel of a feedback
device.
The Feedback n Data Code attribute is the type of feedback data bit encoding
used by designated serial or parallel data interface channel of a feedback device.
The Feedback n Resolver Cable Balance attribute adjusts the relative amplitude of
the Sine and Cosine signals from the resolver to compensate for impact of resolver
cable.
The Feedback n LDT Type determines the LDT type. Options are Start/Stop and
PWM. Start/Stop transducers accept an input (interrogate) signal to start the
measurement cycle and respond with two pulses on the Return line. Timing can be
based on either the Rising or Falling edge. The time between the pulses is
proportional to the position. PWM transducers respond to the interrogate signal
with a single long pulse on the Return line. The pulse width is proportional to the
position.
The Feedback n Loss Action attribute specifies the action taken in the event of a
loss of Feedback 1 signal. Valid actions are to simply handle as an Exception, or
automatically switch to Sensorless operation where feedback is estimated based on
motor current and voltage signals, or automatically switch to a scaled version of a
redundant feedback device. In the case of redundant feedback, Feedback 1 is called
the primary feedback source and the redundant channel is the called the secondary
feedback source.
The Feedback n Scaling Ration attribute is the number of Scaled Feedback Counts
per Feedback n Count. Use this value to convert between secondary feedback n
counts to the resolution of the associated primary feedback channel to support
dynamic switching between feedback channels.
The Feedback n Velocity Filter Taps attribute determines the number of delay
taps used in the FIR Filter differencing algorithm to estimate velocity from
Feedback n. A simple difference of 1 sample period is equivalent to a 1 delay tap.
The Feedback n Accel Filter Taps attribute determines the number of delay taps
used in the FIR Filter differencing algorithm to estimate acceleration from
Feedback n. The Acceleration FIR filter can be implemented as two cascaded FIR
filters each configured according to the Feedback n Acceleration Filter Tap
setting. A simple difference of 1 sample period is equivalent to 1 delay tap.
The Feedback n Accel Filter Bandwidth attribute controls the bandwidth of the
Low Pass Filter applied to the raw acceleration signal from Feedback n. A value of
0 for this attribute disables this feature.
See also
General Feedback Info These are the general feedback information attributes associated with a Motion
Control Axis.
Attributes
Feedback n Serial Number
The Feedback n Serial Number attribute is a 16-character string that specifies the
serial number of the device associated with Feedback n. If it is not possible for the
drive to read the Serial Number from the feedback device the drive sets this
attribute to a Null string.
See also
General Feedback Signal These are the general feedback signal attributes associated with a Motion Control
Axis.
Attributes
Position Feedback n
The Position Feedback n attribute is the actual position of the axis based on
Feedback n.
See also
Motion Control Attributes The following attribute tables contain motion control related attributes associated
with a Motion Control Axis Object instance.
Motion Control Configuration These are the basic motion control configuration attributes associated with a
motion control axis. These attributes govern the overall behavior of the motion
Attributes
control axis.
Axis features
The following table provides descriptions of the bit specified Axis feature attribute
values.
Axis configuration
* The default value can be specified by the specific drive profile (AOP).
The axis configuration attribute determines the general dynamic control behavior
of the motion device axis instance.
This attribute is used to set both the Control Mode and Control Method
attributes according to the following table:
Control Mode
instruction if the axis is in the Running state, for example the Tracking Command
bit of the CIP Axis Status attribute.
The Control Mode attribute determines the general dynamic control behavior of
the drive device axis instance and consists of a 4-bit enumeration. This value is
derived from the axis configuration attribute value during initialization. This
attribute is transferred to the device as part of the Cyclic data block.
When modified programmatically, using SSV, the Control Mode value cannot be
set to an enumeration that the current Axis Configuration cannot support. For
example if the axis configuration is set for Velocity Loop, the Control Mode
cannot be changed to Position Loop since position loop attributes have not been
configured. This table provides a list of valid Control Modes for a given axis
configuration:
The Control Mode attribute is a 4-bit enumeration that determines the specific
dynamic behavior of the motor that the device is to control for this axis instance.
The following table provides descriptions of valid Control Modes.
Control Method
This value is sent to the drive during initialization and cannot be changed during
operation.
See also
Motion Control Interface The Motion Control Interface attributes are used by the Logix Designer
application to support the interface to an axis. Interface attributes are used to
Attributes
customize what choices appear on the properties pages and help you structure a
motion axis.
Tip: Remember that the attributes that appear in the Logix Designer application are dependent on the current Control
Mode.
Axis Address
Absolute Address of Motion Control Axis Object data structure. The Axis
Address attribute is used to return the actual physical address in memory where
the axis instance is located.
Axis Instance
Instance Number assigned to this instance of the Motion Control Axis Object.
The Axis Instance attribute is used to return the instance number of an axis. An
example of using this attribute is responding to an axis major fault. Major fault
records contain the axis instance of the offending axis. Use this attribute to query
an axis instance and determine if the instance number matches the fault record.
The Axis Instance attribute is required when accessing an attribute using a MSG
instruction.
Group Instance
Instance Number of the Motion Group assigned to this instance of the Motion
Control Axis Object. Use the Group Instance attribute to determine what motion
group this axis is assigned to.
Map Instance
I/O Map Instance Number assigned to this instance of the Motion Control Axis
Object. The Map Instance attribute associates an axis to a specific motion
compatible module by specifying the I/O map entry representing the module.
This value is set to 0 for virtual and consumed data types.
Module Channel
Channel number of the module assigned to this instance of the Motion Control
Axis Object. The Module Channel attribute associates an axis to a specific channel
on a motion compatible module by specifying the Module Channel attribute.
Object class code of the motion engine in the module. The Module Class Code
attribute is the class code of the object in the motion module which is supporting
motion; for example 0xAF is the object ID of the Servo Module Axis residing in
the 1756-M02AE module.
Producer/Consumed axis's associated C2C map instance. When the Axis Data
Type attribute is specified to be 'Consumed' then this axis is associated to the
consumed data by specifying both the C2C Map Instance and the C2C
Connection Instance. For all other Axis Data Types if this axis is to be produced
then this attribute is set to 1 (one) to indicate that the connection is off of the
local controller's map instance.
Memory Use
Controller memory space where this instance of the Motion Control Axis Object
exists. This attribute is initialized as part of the create service when you create the
axis.
The Logix Designer programming application uses this attribute to create axis
instances in I/O memory for axes that are either to be produced or consumed.
The Memory Use attribute can only be set as part of an axis create service and is
used to control which controller memory the object instance is created in.
Memory Usage
Amount of memory consumed for this instance of the Motion Control Axis
Object. The Memory Use attribute can be used to determine the amount of
memory the created instance consumes in bytes.
Associated tag data type for this instance of the Motion Control Axis Object. This
attribute is initialized as part of the create service when you create the axis.
The Axis Data Type attribute and is used to determine which data template,
memory format, and set of attributes are created and applicable for this axis
instance. This attribute can only be set as part of an axis create service.
State of the configuration state machine for this instance of the Motion Control
Axis Object. The Axis Configuration State attribute is used for troubleshooting
purposes to indicate where in the axis configuration state-machine this axis
presently is. Even consumed and virtual axes will utilize this attribute. This
attribute is valid for all physical and non-physical data types.
Axis State
State of this instance of the Motion Control Axis. Indicates the operating state of
the axis. Examples of possible states include: axis-ready, drive enable, servo control,
axis faulted, axis shutdown, axis inhibited, and axis unassigned.
User Event Task that will be triggered to execute when a Watch event occurs.
This attribute is set through internal communication from the user Task object to
the Axis object when the Task trigger attribute is set to select this attributes of an
Axis. It cannot be set directly by an external device. It is available to be read
externally for diagnostic information.
The Watch Event Task attribute indicates which user Task will be triggered when
a watch event occurs. An instance value of 0 indicates that no event task has been
configured to be triggered by the Watch Event.
The user Task is triggered at the same time that the Process Complete bit is set for
the instruction that armed the watch event.
User Event Task that will be triggered to execute when a Registration 1 event
occurs.
This attribute is set through internal communication from the user Task object to
the Axis object when the Task trigger attribute is set to select this attributes of an
Axis. It cannot be set directly by an external device. It is available to be read
externally for diagnostic information.
The Registration 1 Event Task attribute indicates which user Task will be
triggered when a Registration 1 event occurs. An instance value of 0 indicates that
no event task has been configured to be triggered by the Registration 1 Event.
The user Task is triggered at the same time that the Process Complete bit is set for
the instruction that armed the registration event.
User Event Task that will be triggered to execute when a Registration 2 event
occurs.
This attribute is set through internal communication from the user Task object to
the Axis object when the Task trigger attribute is set to select this attributes of an
Axis. It cannot be set directly by an external device. It is available to be read
externally for diagnostic information.
The Registration 2 Event Task attribute indicates which user Task will be
triggered when a Registration 2 event occurs.An instance value of 0 indicates that
no event task has been configured to be triggered by the Registration 2 Event.
The user Task is triggered at the same time that the Process Complete bit is set for
the instruction that armed the registration event.
User Event Task that will be triggered to execute when a Home event occurs.
This attribute is set through internal communication from the user Task object to
the Axis object when the Task trigger attribute is set to select this attributes of an
Axis. It cannot be set directly by an external device. It is available to be read
externally for diagnostic information.
The Home Event Task attribute indicates which user Task will be triggered when
a home event occurs. An instance value of 0 indicates that no event task has been
configured to be triggered by the Home Event.
The user Task is triggered at the same time that the Process Complete bit is set for
the instruction that armed the home event.
Inhibit Axis
The on-line inhibit process is an intrusive operation in that it impacts all axes
associated to the same motion module as the one being inhibited. As such it is
expected that the users will trigger this operation with the machine in a safe,
non-operating, state. The inhibit process includes breaking connection to the
associated motion module and then allowing the module to be reconfigured with
or without (depending if you are inhibiting or un-inhibiting) this axis.
The inhibit/un-inhibit operation will also stop all motion on all axes associated to
the same motion module including breaking all gearing relationships. This stop
operation follows that of the shutdown fault action; servo action is immediately
disabled as is the drives power structure. Unless some external form of braking
capability is applied the axis will generally coast to a stop.
Axis ID
position data with the pre-existing axis and recover absolute position. Using the
saved data, absolute position will be recomputed to account for any motion that
occurred while the download was in process or while power was off.
The default schedule setting of Base results in the axis being updated with every
scan of Motion Task, or the Base Update Period of the Motion Group. Alternate
1 and Alternate 2 schedule selections result in the axis being updated at multiples
of the Base Update Period given by the Alternate 1 and Alternate 2 Update
Multiplier attribute values of the Motion Group, or Alternate 1 Update Period
and Alternate 2 Update Period, respectively.
Associated tag data type for this instance of the Motion Control Axis Object.
The Axis Data Type attribute and is used to determine which data template,
memory format, and set of attributes are created and applicable for this axis
instance.
See also
Motion Control Signal The Motion Control Signal Attributes associated with the axis provide access to
the current and historical position, velocity, and acceleration information of the
Attributes
axis. These values may be used as part of the user program to implement
sophisticated real-time computations associated with motion control applications.
Important: Configuration of Scaling page parameters is required for any attributes expressed in position,
velocity, or acceleration units to return meaningful values.
All Motion Control Signal Attributes support Direct Tag Access through the
Logix Designer application. Thus, a Motion Signal attribute may be directly
referenced in a program as <axis tag name>.<motion status tag name>. For
example, FeedAxis.ActualPosition.
• Actual Position
• Actual Velocity
• Actual Acceleration
• Master Offset
• Command Position
• Command Velocity
• Command Acceleration
• Average Velocity
The following are the signal attributes associated a Motion Control Axis:
Actual Position
The Actual Position attribute is the current absolute position of an axis, in the
configured Position Units of that axis. This value is based on data reported to the
Logix Processor as part of an ongoing synchronous data transfer process which
results in a delay of one Coarse Update Period. Thus, the Actual Position value
that is obtained is the actual position of the axis one Coarse Update Period ago.
Tag access supported but value is valid only when Auto Tag Update of the Motion
Group Object is enabled.
Strobe Actual Position and Strobe Command Position attributes are used to
simultaneously store a snap-shot of the actual, command position, and master
offset position of an axis when the MGSP (Motion Group Strobe Position)
instruction is executed. The values are stored in the configured Position Units of
the axis.
Since the MGSP instruction simultaneously stores the actual and command
positions for all axes in the specified group of axes, the resultant Strobe Actual
Position and Strobe Command Position values for different axes can be used to
perform real-time calculations.
For example, the Strobe Actual Positions can be compared between two axes to
provide a form of slip compensation in web handling applications.
Whenever a new motion planner instruction starts for an axis (for example, using
a MAM instruction), the value of the axis command position and actual position
is stored at the precise instant the motion begins. These values are stored as the
Start Command Position and Start Actual Position respectively in the configured
Position Units of the axis.
Start Positions are useful to correct for any motion occurring between the
detection of an event and the action initiated by the event. For instance, in coil
winding applications, Start Command Positions can be used in an expression to
compensate for overshooting the end of the bobbin before the gearing direction is
reversed.
If you know the position of the coil when the gearing direction was supposed to
change, and the position at which it actually changed (the Start Command
Position), you can calculate the amount of overshoot, and use it to correct the
position of the wire guide relative to the bobbin.
Average Velocity
The Average Velocity attribute is the current speed and direction of an axis in the
configured Position Units per second of the axis.
Unlike the Actual Velocity attribute value, it is calculated by averaging the actual
velocity of the axis over the configured Average Velocity Timebase for that axis.
Average velocity is a signed value with the sign indicating the direction the axis is
currently moving.
The resolution of the Average Velocity variable is determined by the current value
of the Averaged Velocity Timebase parameter, and the configured Conversion
Constant (feedback counts per Position Unit) for the axis. The Average Velocity
Timebase determines the length over which the Average Velocity is computed.
The greater the Average Velocity Timebase value, the better the speed resolution,
but the slower the response to changes in speed.
The Average Velocity resolution in Position Units per second may be calculated
using this equation.
For example, on an axis with position units of inches and a conversion constant
(K) of 20000, an averaged velocity time-base of 0.25 seconds results in an average
velocity resolution of:
The minimum Average Velocity Timebase value is one Coarse Update Period
defined by the associated Motion Group Object.
Tag access supported but value is valid only when Auto Tag Update of the Motion
Group Object is enabled.
Actual Velocity
The Actual Velocity attribute is the current instantaneously measured speed and
direction of an axis, in the configured axis Position Units per second. It is
calculated as the current increment to the actual position per coarse update
interval.
Tag access supported but value is valid only when Auto Tag Update of the Motion
Group Object is enabled.
Actual Acceleration
Actual Acceleration is a signed floating-point value. Its resolution does not depend
on the Averaged Velocity Timebase, but rather on the Conversion Constant of the
axis and the fact that the internal resolution limit on actual velocity is 1 feedback
count per Coarse Update Period2.
Tag access supported but value is valid only when Auto Tag Update of the Motion
Group Object is enabled.
Watch Position
The Watch Position attribute is the current set-point position of an axis, in the
configured axis Position Units, as set up in the last, most recently executed, MAW
(Motion Arm Watch) instruction for that axis.
This figure shows how the registration position is latched by the registration input
when a registration event occurs. The latching mechanism can be implemented in
the controller software (soft registration) or, for greater accuracy, in physical
hardware (hard registration).
Use the formula given above to calculate the maximum registration position error
for the expected axis speed. Alternatively, you can calculate the maximum axis
speed for a specified registration accuracy by re-arranging this formula:
The two Registration Time values contain the lower 32-bits of CST time at which
their respective registration events occurred. Units for this attribute are in
microseconds.
Interpolation Time
The Interpolation Time attribute is the 32-bit CST time used to calculate the
interpolated positions. When this attribute is updated with a valid CST value, the
Interpolated Actual Position and Interpolated Command Position values are
automatically calculated.
Command Position
The figure below shows the relationship between Actual Position, Command
Position, and Position Error for an axis with an active servo loop. Actual Position
is the current position of the axis as measured by the feedback device, for example
an encoder. Position error is the difference between the Command and Actual
Positions of the servo loop, and is used to drive the motor to make the actual
position equal to the command position.
Tag access supported but value is valid only when Auto Tag Update of the Motion
Group Object is enabled.
Strobe Actual Position, Strobe Command Position and Strobe Master Offset
attributes are used to simultaneously store a snap-shot of the actual, command
position, and master offset position of an axis when the MGSP (Motion Group
Strobe Position) instruction is executed. The values are stored in the configured
Position Units of the axis.
Since the MGSP instruction simultaneously stores the actual and command
positions for all axes in the specified group of axes, the resultant Strobe Actual
Position, Strobe Command Position and Strobe Master Offset values for different
axes can be used to perform real-time calculations. For example, the Strobe Actual
Positions can be compared between two axes to provide a form of slip
compensation in web handling applications.
Whenever a new motion planner instruction starts for an axis (for example, using
a MAM instruction), the value of the axis command position and actual position
is stored at the precise instant the motion begins. These values are stored as the
Start Command Position and Start Actual Position respectively in the configured
Position Units of the axis.
Start Positions are useful to correct for any motion occurring between the
detection of an event and the action initiated by the event. For instance, in coil
winding applications, Start Command Positions can be used in an expression to
compensate for overshooting the end of the bobbin before the gearing direction is
reversed.
If you know the position of the coil when the gearing direction was supposed to
change, and the position at which it actually changed (the Start Command
Position), you can calculate the amount of overshoot, and use it to correct the
position of the wire guide relative to the bobbin.
Command Velocity
The Command Velocity is the commanded speed and direction of an axis, in the
configured axis Position Units per second, as generated by any previous motion
instructions. It is calculated as the current increment to the command position per
coarse update interval. Command Velocity is a signed value—the sign (+ or -)
depends on which direction the axis is being commanded to move.
Rockwell Automation Publication MOTION-RM003K-EN-P - July 2019 455
Chapter 4 CIP Axis Attributes
Command Velocity is a signed floating-point value. Its resolution does not depend
on the Averaged Velocity Timebase, but rather on the conversion constant of the
axis and the fact that the internal resolution limit on command velocity is 0.00001
feedback counts per coarse update.
Tag access supported but value is valid only when Auto Tag Update of the Motion
Group Object is enabled.
Command Acceleration
Tag access supported but value is valid only when Auto Tag Update of the Motion
Group Object is enabled.
Command Torque
Command Torque has no effect on the axis unless the axis is configured for
Torque Loop operation. In order for the this attribute's value to be applied as the
torque command, a Motion Drive Start instruction will be executed, which in turn
sets the Direct Torque Control Status bit of the Motion Status Bits attribute. If
this bit is not set, the Command Torque value has no effect on axis motion. Only
CIP Drive Axis data types currently support this capability.
Master Offset
The Master Offset attribute is the position offset that is currently applied to the
master side of the position cam. The Master Offset is returned in master position
units. The Master Offset shows the same unwind characteristic as the position of a
linear axis. Tag access is supported but the tag value is valid only when Auto Tag
Update of the Motion Group Object is enabled
The Strobe Master Offset attribute is the position offset that was applied to the
master side of the position cam when the last Motion Group Strobe Position
(MGSP) instruction was executed. The Strobe Master Offset is returned in master
position units. The Strobe Master Offset shows the same unwind characteristic as
the position of a linear axis.
The Start Master Offset attribute is the position offset that was applied to the
master side of the position cam when the last Motion Axis Move (MAM)
instruction with the move type set to Absolute Master Offset or Incremental
Master Offset was executed. The Start Master Offset is returned in master
position units. The Start Master Offset shows the same unwind characteristic as
the position of a linear axis.
The Direct Command Velocity attribute provides tag access to the velocity
command for the specified axis. This can be used to directly control the speed of a
motor when an associated drive is configured for velocity control mode. In order
for this attribute's value to be applied as the velocity command, a Motion Drive
Start instruction will be executed, which in turn sets the Direct Velocity Control
Status bit of the Motion Status Bits attribute. If this bit is not set, the Direct
Command Velocity value has no effect on axis motion. Only CIP Drive Axis data
types currently support this capability.
This bit mapped attribute configures the interpolation algorithm used to calculate
Interpolated Actual Position and Interpolated Command Position based on axis
position history based on the current value of Interpolation Time.
The 2nd Order Actual Position Interpolation bit controls the order of the
interpolation algorithm used to calculate Interpolated Actual Position based on
Interpolation Time. If the bit is set, 2nd order interpolation is used. If the bit is
clear, 1st order interpolation is used. Generally, 2nd order interpolation results in
more accurate estimates of position, but if the actual position signal has high levels
of quantization noise, 1st order interpolation gives better results.
The 2nd Order Command Position Interpolation bit controls the order of the
interpolation algorithm used to calculate Interpolated Command Position based
on Interpolation Time. If the bit is set, 2nd order interpolation is used. If the bit is
clear, 1st order interpolation is used. Generally, 2nd order interpolation results in
more accurate estimates of position, but if the command position signal has high
levels of quantization noise, 1st order interpolation gives better results.
See also
Motion Control Status These are the motion control status attributes associated with a Motion Control
Axis. The Axis Event Bits are located in Event Capture Attributes.
Attributes
This table provides descriptions of the various Motion Axis Status Bits:
The Axis Status Bits attribute is a collection of basic status conditions associated
with the axis. These represent key status conditions used by the system in
executing motion control instructions.
5 Direct Control Status When the Direct Control Status bit is set, axis motion is driven by the Direct Velocity
Control and Direct Torque Control functions. In this mode, the Motion Planner
functionality is disabled. So if you attempt to move the axis with a Motion Planner
instruction, for example, MAM, MAJ, and MAG, a ran instruction error occurs.
In Direct Control, you do not have to establish or maintain absolute reference position.
So, when you attempt to execute the MAH and MRP instructions, an instruction error
occurs.
When the Direct Control Status bit is clear, axis motion is controlled by the Motion
Planner. If you attempt to move the axis in this mode with a Direct Control instruction,
for example, an MDS, an instruction error occurs. This bit only applies to CIP Drive axis
types.
The illustration describes the following behavior.
The Direct Control Status bit is set by the Motion Drive Start instruction (MDS) and once
set, can only be cleared by executing an MSO instruction from the Stopped or Stopping
State. Similarly, once the Direct Control Status bit is cleared by the Motion Servo On
instruction (MSO), the bit can only be set again by executing an MDS instruction from the
Stopped or Stopping State.
6 Axis Update Status The Axis Update bit indicates whether or not this axis instance was updated in last
execution of Motion Task. In general, axis instances are updated in Motion Task according
to their Axis Update Schedule. Thus, a given axis instance may or may not be updated
during Motion Task execution. When inspected as part of an Event Task triggered by
Motion Group Execution, the Axis Update bit can be used to qualify program instructions
based on whether or not the axis was updated by the preceding Motion Task.
The Axis Fault Bits attribute is a collection of basic fault types associated with the
axis. Each valid axis fault type is assigned a bit in this word. Any fault condition
associated with a given fault type will result in the setting of the appropriate fault
bit.
Each bit in the Axis Fault Bits attribute represents a roll-up of the associated fault
types. One or more faults of a given fault type result in the associated bit of the
Axis Fault Bits attribute being set.
The Axis Event Bit attributes are a collection of basic event conditions. This
attribute is for use primarily by the system during execution of various Motion
Event instructions.
The Output Cam Status bit is set when an Output Cam has been initiated. The
Output Cam Status bit is reset when the cam position moves beyond the cam start
or cam end position in "Once" execution mode with no Output Cam pending or
when the Output Cam is terminated by a Motion Disarm Output Cam (MDOC)
instruction.
The Output Cam Pending Status bit is set if an Output Cam is currently pending
the completion of another Output Cam. This would be initiated by executing an
Motion Arm Output Cam (MAOC) instruction with Pending execution selected.
As soon as this output cam is armed, being triggered when the currently executing
Output Cam has completed, the Output Cam Pending bit is cleared. This bit is
also cleared if the Output Cam is terminated by a Motion Disarm Output Cam
(MDOC) instruction.
The Output Cam Lock Status bit is set when an Output Cam has been armed.
This would be initiated by executing a Motion Arm Output Cam (MAOC)
instruction with Immediate execution selected, when a pending output cam
changes to armed, or when the axis approaches or passes through the specified axis
arm position. As soon as this output cam current position moves beyond the cam
start or cam stop position, the Output Cam Lock bit is cleared. This bit is also
cleared if the Output Cam is terminated by a Motion Disarm Output Cam
(MDOC) instruction.
The Output Cam Transition Status bit is set when a transition between the
currently armed and the pending Output Cam is in process. Therefore, each
Output Cam controls a subset of Output Bits. The Output Cam Transition
Status bit is reset, when the transition to the pending Output Cam is complete or
when the Output Cam is terminated by a Motion Disarm Output Cam (MDOC)
instruction.
See also
Exceptions on page 47
Motion Database Storage The following are the Motion Database Storage attributes associated with a
Motion Control Axis.
Attributes
System Acceleration Base
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - C Set REAL 0 0 Motor Units/sec2 @ 100 % Rated
DB
This floating point value represents the acceleration of the selected unloaded
motor based on 100% Rated current and used to compute System Inertia. This
attribute is used to store the original System Acceleration value for subsequent
upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - C Set REAL .0015 0 Sec
DB
This floating point value represents the lumped model time constant associated
with the drive device for the purposes of computing loop gains. This attribute is
used to store the original Drive Model Time Constant value for subsequent
upload. The Drive Model Time Constant Base (DMTC_Base) is computed based
on the current loop bandwidth, the velocity loop update time and the feedback
sample period according to the following formula:
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - C Set REAL 0 0 Amps
DB
This floating point value represents the peak current rating associated with the
drive device and used to compute peak torque and acceleration limits. This
attribute is used to store the original Drive Rated Peak Current value for
subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Optional - C Set REAL 0 0 Volts
DB
This floating point value represents the maximum DC Bus voltage level that can
be sustained during drive operation, which is used to calculate the factory default
value for PM Motor Rotary Bus Overvoltage Speed or the PM Motor Linear Bus
Overvoltage Speed associated with PM motor types. This attribute is used to store
the Bus Overvoltage Operational Limit value used in this calculation for
subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Optional - C Set REAL 0.001 0 Seconds
DB
This floating point value represents the lumped model time constant associated
with the regenerative converter device for the purposes of computing loop gains.
This attribute is used to store the original Converter Model Time Constant value
for subsequent upload. The Converter Model Time Constant Base is computed
based on the converter current loop bandwidth, the bus voltage loop update time
and the bus voltage feedback sample period according to the following formula:
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - G Set REAL 0 0 Hz
DB
This floating point value represents the default bandwidth for the active and
reactive current loops for the regenerative converter. This attribute is used to store
the original default Converter Current Loop Bandwidth value that was used to
compute the Converter Model Time Constant that is the basis for tuning the
converter.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - G Set REAL 0 0 Amps
DB
This floating point value represents the continuous output current rating
associated with the regenerative converter and used to compute the System
Capacitance scaling attribute value from the Total Capacitance of the DC Bus.
This attribute is used to store the original Converter Rated Current value for
subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - G Set REAL 0 0 Amps
DB
This floating point value represents the peak output current rating associated with
the regenerative converter and used together with the Converter Rated Current to
compute the default Converter Current Vector Limit attribute value. This
attribute is used to store the original Converter Rated Peak Current value for
subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - G Set REAL 0 0 Volts (RMS)
DB
This floating point value represents the input voltage rating associated with the
regenerative converter and used to compute the Bus Voltage Set Point attribute
value. This attribute is used to store the original Converter Rated Voltage value for
subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - G Set REAL 0 0 F (Amps)
DB
This floating point value represents the internal bus capacitance of the
regenerative converter and is used to compute the System Capacitance scaling
attribute. This attribute is used to store the original Converter DC Bus
Capacitance value for subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - G Set REAL 0 0 kVA
DB
This floating point value represents the power rating of the converter. This
attribute is used to estimate the default AC Line Source Power value.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - C Set REAL 0 0
DB
This floating point value represents the scaling factor, based on motor type, which
is used to set the factory default value for Torque Loop Bandwidth. This attribute
is used to store the original Current Loop Bandwidth Scaling Factor value for
subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - D Set REAL 0 0 V rms
DB
This floating point value represents the RMS voltage rating of the drive that is
used to set the factory default value for the Break Voltage associated with V/Hz
drives. This attribute is used to store the original Drive Rated Voltage value for
subsequent upload.
Data
Usage Access T Default Min Max Semantics of Values
Type
Required - D Set REAL 0 0 Hz
DB
This floating point value represents the maximum frequency rating of the drive
that is used to set the factory default values for Velocity Limits. This attribute is
used to store the original Max Output Frequency value for subsequent upload.
See also
Motion Dynamic Configuration These are the motion dynamic configuration attributes associated with a Motion
Control Axis.
Attributes
Maximum Speed
The value of the Maximum Speed attribute is used by various motion instructions
to determine the steady-state speed of the axis. These instructions all have the
option of specifying speed as a percent of the Maximum Speed attribute value for
the axis. This value is typically set to ~85% of the maximum speed rating of the
motor. This provides sufficient 'head-room' for the axis to operate at all times
within the speed limitations of the motor.
Setting the Maximum Deceleration to zero with a SSV command will generate a
minor fault. Motion on an axis cannot start with a deceleration of zero, so this
value will not be accepted.
The Programmed Stop Mode attribute determines how a specific axis will stop
when the Logix processor undergoes a critical processor mode change or when an
explicit MGS (Motion Group Stop) instruction is executed with its stop mode set
to 'programmed'.
There are currently four modes defined for the Logix processor: Program Mode,
Run Mode, Test Mode, and Faulted Mode. Any mode change into or out of
program mode (prog - >run, prog->test, run->prog & test->prog) will initiate a
programmed stop for every axis owned by that processor.
Method Description
Fast Stop When the Programmed Stop Mode attribute is configured for Fast Stop, the axis is decelerated to
a stop using the current configured value for Maximum Deceleration. Servo action is maintained
after the axis motion has stopped.
Fast Disable When the Programmed Stop Mode attribute is configured for Fast Disable, the axis is decelerated
to a stop using the current configured value for Maximum Deceleration. Servo action is
maintained until the axis motion has stopped at which time the axis is disabled, for example,
Drive Enable disabled, and Servo Action disabled.
Hard Disable When configured for Hard Disable, the axis is immediately disabled, for example, Drive Enable
disabled, Servo Action disabled, but the OK contact is left closed. Unless the drive is configured to
provide some form of dynamic braking, this results in the axis coasting to a stop.
Fast Shutdown When configured for Fast Shutdown, the axis is decelerated to a stop as with Fast Stop but, once
the axis motion is stopped, the axis is placed in the Shutdown state, for example, Drive Enable
disabled, Servo Action disabled, and the OK contact opened. Recovering from the Shutdown state
requires execution of one of the axis or group Shutdown Reset instructions (MASR or MGSR).
Hard Shutdown When configured for Hard Shutdown, the axis is immediately placed in the Shutdown state, for
example, Drive Enable disabled, Servo Action disabled. Unless the drive is configured to provide
some form of dynamic braking, this results in the axis coasting to a stop. To recover from the
Shutdown state requires execution of one of the axis or group Shutdown Reset instructions
(MASR or MGSR).
This attribute is a collection of bits that control the operation of the motion
planner dynamics.
See also
Motion Homing Configuration Use Homing functionality to establish a machine reference position or Home
Position for the associated axis. Homing configuration attributes are often only
Attributes
applicable when there is an associated position feedback device. If the drive is
configured for Encoderless or Sensorless operation, the homing function is not
applicable.
Home Mode
The Home Mode attribute determines if homing actively moves the axis to
generate the homing event or if the axis is to be moved by some external agent to
generate the homing event.
There Motion axis supports active and passive homing modes. Active homing is
the most common homing procedure for physical servo axes but does not apply
when Axis Configuration is Feedback Only since it requires active control of the
axis.
Home Direction
Home Sequence
Determines the motion sequencing used to trigger the desired homing events.
Filtering of optional enumerations based on available hardware support and
feedback interface hardware.
If the controller detects that the state of the home switch at the start of the homing
sequence is active, the controller immediately reverses the homing direction and
begins the return leg of the homing sequence.
Neglecting the mechanical uncertainty of the home limit switch, the accuracy of this
homing sequence depends on the time uncertainty in detecting the home limit switch
transitions. The position uncertainty of the home position is the product of the
maximum time for the control to detect the home limit switch (~10 milliseconds) and
the specified Home Return Speed. For this reason, the Home Return Speed is often
made significantly slower than the Home Speed.
For example, if a Home Return Speed of 0.1 inches per second (6 IPM) is specified, the
uncertainty of the home position is calculated as shown below:
Uncertainty = 0.1 Inch/Sec * 0.01 Sec = 0.001 Inch.
The accuracy of this homing sequence depends only on the time delay in detecting the
marker transition. The position uncertainty of the home position is the product of the
maximum delay for the control to detect the marker pulse (~1 microsecond) and the
specified Home Speed.
For example, if a Home Speed of 1 inches per second (60 IPM) is specified, the
uncertainty of the home position is calculated as shown below:
Uncertainty = 1 Inch/Sec * 0.000001 Sec = 0.000001 Inch.
Active Bidirectional Home to This is the most precise active homing sequence available. When this sequence is
Switch then Marker performed, the axis moves in the specified Home Direction at the specified Home Speed
and Home Acceleration until the home limit switch is detected. The axis then
decelerates to a stop at the specified Home Deceleration and moves in the opposite
direction at the specified Home Return Speed and Home Acceleration until the home
limit switch is cleared. After clearing the home limit switch, the axis continues in the
same direction at the Home Return Speed until the first encoder marker is detected.
The Home Position is assigned to the axis position at the moment that the marker is
detected, and the axis then decelerates to a stop at the specified Home Deceleration. If
Home Offset is non-zero, then the Home Position will be offset from the point where
the marker is detected by this value. The controller then moves the axis back to the
Home Position at the specified Home Return Speed and Home Acceleration using a
trapezoidal move profile.
If the axis is configured in Cyclic Travel Mode, the move back to the Home Position takes
the shortest path (for example, no more than ½ revolution). Axis behavior for this
active homing sequence is depicted in the following diagram:
If the controller detects that the state of the home switch at the start of the homing
sequence is active, the controller immediately reverses the homing direction and
begins the return leg of the homing sequence.
Active Unidirectional Home to This active homing sequence is useful for single turn rotary and linear encoder
Marker applications when unidirectional motion is required.
When this sequence is performed in the Active Homing Mode, the axis moves in the
specified Home Direction at the specified Home Speed and Home Acceleration until the
marker is detected. If the Home Offset is zero, the Home Position is assigned to the axis
position at the moment that the marker is detected and the axis decelerates to a stop at
the specified Home Deceleration.
If Home Offset is non-zero, then the Home Position will be offset from the point where
the marker was detected by this value. The controller then continues to move the axis
to the Home Position at the specified Home Speed and Home Acceleration using a
trapezoidal move profile.
The axis position is updated based on the Home Position and Home Offset. Even if the
Home Offset is zero, the position is updated. Zero is a valid number.
By setting a Home Offset greater than the deceleration distance, unidirectional motion
to the Home Position is insured. However, if the Home Offset value is less than the
deceleration distance, then the axis is simply decelerated to a stop at the specified
Home Deceleration. The axis does not reverse direction to move to the Home Position.
In this case, the PC-bit leg of the associated MAH instruction is not set when the IP-bit
leg is cleared.
In the case where this homing sequence is performed on a cyclic axis and the Home
Offset value is less than the deceleration distance when the home event is detected, the
control automatically adds one or more revolutions to the move distance. This
guarantees the resulting move to the Home Position is unidirectional.
The Home to Torque sequence is similar to Home to Switch, with the exception that the
torque level is used instead of the home switch input. When this sequence is
performed, the axis moves in the specified Home Direction at the specified Home Speed
and Home Acceleration until a hard stop is detected, such as when motor torque has
exceeded the Home Torque Threshold for a period equal to Home Torque Time. At this
point, Home Position is calculated. The axis then decelerates to a stop at the specified
Home Deceleration. If Home Offset is non-zero and would not place the Home Position
of the axis further into the hard stop, the axis moves to the Home Position at the Home
Return Speed and Home Acceleration and Home Deceleration using a trapezoidal move
profile. Finally, the controller restores overridden drive attributes to their saved original
values. Axis behavior for this homing sequence is depicted in the following diagram:
Passive Immediate Home This is the simplest passive homing sequence type. When this sequence is performed,
the controller immediately assigns the Home Position to the current axis actual
position. This homing sequence produces no axis motion.
Passive Home with Switch This passive homing sequence is useful when an encoder marker is not available or a
proximity switch is being used.
When this sequence is performed in the Passive Homing Mode, an external agent
moves the axis until the home switch is detected. The Home Position is assigned to the
axis position at the moment that the limit switch is detected. If Home Offset is
non-zero, then the Home Position will be offset from the point where the switch is
detected by this value.
The Home Configuration Bits attribute determines homing related behavior such
as the sense of the home switch contacts.
The Home Switch Normally Closed bit attribute determines the normal state of
the home limit switch used by the homing sequence. The normal state of the
switch is its state prior to being engaged by the axis during the homing sequence.
For example, if the Home Switch Normally Closed bit is set (true) then the
condition of the switch prior to homing is closed. When the switch is engaged by
the axis during the homing sequence, the switch is opened, which constitutes a
homing event.
Home Position
The Home Position is the desired absolute position for the axis after the specified
homing sequence has been completed. After an active homing sequence has
completed, the axis is left at the specified Home Position.
Otherwise, the axis is not at the home position and the axis position is based on
the Home Position.
In most cases, Home Position is set to zero, although any value, within the
Maximum Positive and Negative Travel limits of the axis (if enabled), may also be
used. (A description of the Maximum Positive and Negative Travel configuration
attributes may be found in the Servo and Drive Axis Object specifications.) For a
cyclic axis, the Home Position is constrained to be a positive number less than the
Position Unwind value divided by the Conversion Constant.
Home Offset
After an active bidirectional homing sequence has completed, the axis is left at the
specified Home Position. If the Home Offset is non-zero, the axis will then be
offset from the marker or home switch event point by the Home Offset value. If
the Home Offset is zero, the axis will sit right on top of the marker or home switch
point.
Home Speed
The Home Speed attribute controls the speed of the jog profile used in the first leg
of an active homing sequence as described in the above discussion of the Home
Sequence Type attribute.
This is valid for non-immediate cases of active Home Mode. Only valid for
position and velocity control.
The Home Return Speed attribute controls the speed of the jog profile used after
the first leg of an active bidirectional homing sequence as described in the above
discussion of the Home Sequence Type attribute.
This is valid for non-immediate cases of active Home Mode. Only valid for
position and velocity control.
Home Acceleration
The Home Acceleration attribute controls the acceleration of the velocity profile
used in an active Home Sequence attribute.
Home Deceleration
The Home Deceleration attribute controls the deceleration of the axis as it comes
to a stop in an active homing sequence as described in the Home Sequence
attribute.
The Home Deceleration attribute controls the deceleration of the axis as it comes
to a stop in an active homing sequence as described in the Home Sequence
attribute.
See also
Motion Control Configuration Attributes on page 433
Motion Control Status Attributes on page 459
Motion Planner Configuration These are the motion planner attributes associated with a Motion Control Axis.
Attributes Output Cam Execution Targets
1
This attribute can be set only when the axis instance is created.
The Output Cam Execution Targets attribute is used to specify the number of
Output Cam nodes attached to the axis. This attribute can only be set as part of an
axis create service and dictates how many Output Cam Nodes are created and
associated to that axis. Each Output Cam Execution Target requires
approximately 5.4k bytes of data table memory to store persistent data. With four
Output Cam Execution Targets per axis, an additional 21.6k bytes of memory is
required for each axis.
The ability to configure the number of Output Cam Execution Targets for a
specific axis reduces the memory required per axis for users who do not need
Output Cam functionality, or only need 1 or 2 Output Cam Execution Targets
for a specific axis. Each axis can be configured differently.
This attribute controls the master axis input signal feeding the gearing and
camming functions of the motion planner, including the Master Position Filter
and Master Delay Compensation.
Minimum Range limits based on Coarse Update Period are ultimately enforced
(1)
for Master Position Filter Bandwidth attribute by clamping to limit rather than
generating a value out of range error. Only if the value is outside the fixed
Min/Max limits is an out of range error given. This was done to avoid
implementing complex range limit code based on the Coarse Update Period in the
Logix Designer application.
The Master Position Filter Bandwidth attribute controls the activity of the
single-poll low-pass filter that filters the specified master axis position input to the
slave's gearing or position camming operation. When enabled, this filter has the
effect of smoothing out the actual position signal from the master axis, and thus
smoothing out the corresponding motion of the slave axis. The trade-off for
smoothness is an increase in lag time between the response of the slave axis to
changes in motion of the master.
If the Master Position Filter is disabled, the Master Position Filter Bandwidth has
no effect.
This table defines the actions that may be taken by the controller in response to
the exception condition.
This attribute determines if the system should check for software overtravel
condition based on current settings for Soft Travel Limit - Positive, and Soft
Travel Limit - Negative.
When the Soft Overtravel Checking is set to true the motion planner checks the
current Actual Position of the axis and issues an exception condition if the Soft
Travel Limits in either direction are exceeded while commanding motion in that
direction. The travel limits are determined by the configured values for the
Maximum Positive Travel and Maximum Negative Travel attributes. Soft Travel
Limit checking is not a substitute, but rather a supplement, for hardware
overtravel fault protection that uses hardware limit switches to directly stop axis
motion at the drive and deactivate power to the system.
If the Soft Travel Limit Checking value is set to false (default), then no software
travel limit checking is done by the planner. For CIP Drive axis data types, Soft
Travel Limit Checking has no affect if the Travel Mode is configured for Cyclic
(Rotary) operation.
Soft Travel Limit Checking has no impact until the Axis Homed Status bit is set
in the Motion Status Bits attribute; there is no point in checking absolute position
of the axis if an absolute position reference frame has not been established for the
machine.
The Soft Travel Limit - Positive attribute sets the maximum positive travel limit
for actual position when Soft Travel Limit Checking is enabled. If this value is
exceeded while commanding motion in the positive direction, a Soft Travel Limit
- Positive exception is generated.
The Soft Travel Limit - Negative attribute sets the maximum negative travel limit
for actual position when Soft Travel Limit Checking is enabled. If this value is
exceeded while commanding motion in the negative direction, a Soft Travel Limit
- Negative exception is generated.
This attribute provides configurable software travel limits through the Soft Travel
Limit - Positive and Soft Travel Limit - Negative attributes. If the axis is
configured for Soft Travel Limit Checking, and the axis passes outside these travel
limits, a Software Travel Limit exception condition occurs. In the case of a
controlled axis, when the axis is outside the travel limits and no motion is being
commanded or motion is being commanded to bring the axis back within the soft
travel range, the Soft Travel Limit exception is NOT generated. This facilitates
recovery from an existing Soft Travel Limit condition. In this case, a Fault Reset
can be executed to clear the fault, allowing the axis to be enabled, and then simply
commanded back inside the travel limits. For an uncontrolled axis, such as
Feedback Only axis, a Soft Travel Limit exception is always generated when the
axis is outside the travel limits. In this case the axis must be moved back inside the
Travel Limits by some other means. Any attempt to clear the Travel Limit fault in
the uncontrolled axis case while outside the travel limits results in an immediate
re-issue of the Soft Travel Limit exception.
When Soft Travel Limit Checking is enabled, appropriate values for the maximum
travel in both the Soft Travel Limit Positive and Soft Travel Limit Negative
attributes need to be established with Soft Travel Limit - Positive value always
greater than Soft Travel Limit - Negative value. Both of these values are specified
in the configured Position Units of the axis.
Use the Command Update Delay Offset attribute to introduce a time offset to the
command as part of the Master Delay Compensation feature of the control system
used by gearing and camming functions. Generally this value should be set to 0
since the device applies the command position according to the associated time
stamp. A non-zero value would have the effect of phase advancing or retarding the
axis position relative to a master axis.
See also
Motion Planner Output These are the motion planner output attributes associated with a Motion Control
Axis.
Attributes
Planner Command Position - Integer
represented internally as a 64-bit floating point value that Motion Task restricts to
a signed 32-bit integer range. The resulting range restricted Double Floating point
value can therefore be expressed as two 32-bit attributes to preserve precision. This
is accomplished by representing the command position (compos) as x + y, where x
is the signed integer component (this attribute) and y is the signed floating point
fractional component. x and y are defined using the following equations:
x = (int)compos
y = (float)(compos – x)
x = (int)compos
y = (float)(compos – x).
This attribute value is the Motion Planner generated actual position in planner
counts. The internal 64-bit signed integer representation of actual position is
range limited by Motion Task to a signed 32-bit integer.
See also
Motion Scaling Attributes These are the basic motion scaling configuration attributes associated with a
Motion Control Axis. These attributes are involved in conversion between
position, speed, and acceleration expressed in Motion Counts and Motion Units,
496 Rockwell Automation Publication MOTION-RM003K-EN-P - July 2019
CIP Axis Attributes Chapter 4
and the user-defined Position Unit of the axis. The motion scaling function is also
involved in conversion of Motion Counts to/from Feedback Counts, and Motion
Units to/from Feedback Units.
The Drive Scaling selection configures the control system to perform the scaling
calculations in the drive device. In this mode, the controller interacts with the
drive in terms of Motion Counts or Motion Units and the drive is responsible for
conversion to equivalent Feedback Counts and Motor Units. Also, in Drive
Scaling mode the drive is responsible for Position Unwind (Cyclic Unwind)
operations associated with Cyclic Travel Mode (Cyclic Unwind Control).
Scaling Source
Enumerated attribute used to determine whether the scaling factors are going to
be entered directly from the user or calculated based on Position Scaling, Position
Unwind, and Travel Range values. When entered directly, the scaling factors, for
example, Conversion Constant, Position Unwind, and Motion Resolution are
expressed in units of "counts". When using the scaling calculator, the scaling
factors are calculated based on values entered by the user in the preferred units of
the application without requiring any knowledge of "counts".
Important: Configuration of Scaling page parameters is required for any attributes expressed in position,
velocity, or acceleration units to return meaningful values.
Cyclical Travel:
Limited Travel:
Unlimited Travel:
When Scaling Calculations are performed, Logix Designer application sets the
Scaling Source to "from calculator". If any of the Scaling Factor attributes is
changed directly by the user either through Logix Designer or through
programmatic access, Scaling Source is set to "direct entry". The "direct entry"
setting indicates that the Scaling Factors are no longer consistent with the current
Scaling attribute values.
Travel Mode
A floating point value used by the scaling calculator to determine the number of
Position Units per Position Scaling Denominator units (Motion Units).
A floating point value used by the scaling calculator to determine the number of
Motion Units per Position Scaling Numerator units (Position Units).
A floating point value used by the scaling calculator to determine the number of
Position Units per Position Unwind Denominator units (Unwind Cycles). This
value is only used by the calculator if cyclic Travel Mode is selected.
A floating point value used by the scaling calculator to determine the number of
Unwind Cycles per Position Unwind Numerator units (Position Units). This
value is only used by the calculator if cyclic Travel Mode is selected.
Travel Range
A floating point value used by the scaling calculator to determine the maximum
travel range in Position Units for a limited Travel Mode position scaling
calculation.
Motion Unit
The Motion Unit attribute determines the unit of measure used to express the
Motion Resolution used by motion planner functions. A Motion Unit is the
standard engineering unit of measure for motion displacement. Motion Units may
be configured as Revs, Inches, or Millimeters depending on the specific
application.
Motion Resolution
The Motion Resolution attribute is an integer value that determines the number
of Motion Counts per Motion Unit used by the scaling function to convert
between Motion Counts and Feedback Counts. This attribute determines how
many Motion Counts there are in a Motion Unit. A Motion Count is the
fundamental unit of displacement used by the Motion Planner and a Motion Unit
is the standard engineering unit of measure for motion displacement. Motion
Units may be configured as Revs, Inches, or Millimeters depending on the specific
application.
All command position, velocity, and acceleration data is scaled from the user's
preferred Position Units to Motion Units for the Motion Planner based on the
Motion Resolution and Conversion Constant. The ratio of the Conversion
Constant to Motion Resolution determines the number of Position Units in a
Motion Unit as described using the following formula.
Conversely, all actual position, velocity, and acceleration data from the Motion
Planner is scaled from Motion Units to the user's preferred Position Units based
on the Motion Resolution and Conversion Constant. The ratio of Motion
Resolution and the Conversion Constant determines the number of Position
Units in a Motion Unit as described using the following formula:
The Default Motion Resolution value used for scaling factors, Motion Resolution,
Conversion Constant, and Position Unwind, depends on the Motion Unit
selection according to the following table:
Because the position parameters are sometimes internally limited to signed 32-bit
representation, the Motion Resolution parameter impacts the travel range. In such
a case, the equation for determining the maximum travel range based on Motion
Resolution is as follows:
Based on a default value of 1,000,000 Motion Counts per Motion Unit, the range
limit is 2,147 Motion Units. When the axis position exceeds this value, the
position accumulators roll-over, essentially flipping the sign of the axis position
value. Motion continuous smoothly through the roll-over but the position values
are obviously not contiguous. This is nominal operation in Unlimited Travel
Mode. While it is relatively rare for this travel range limitation to present a
problem, say in point-to-point positioning applications, it is a simple matter to
lower the Motion Resolution to increase the travel range. The downside of doing
so is that the position data is then passed with lower resolution that could impact
the smoothness of motion. Selecting Limit Travel Mode sets the Motion
Resolution value close to the maximum value that complies with the specified
Travel Range of the application.
Fractional Unwind
In some cases, however, you may also want to specifically configure Motion
Resolution value to handle fractional unwind applications or multi-turn absolute
applications requiring cyclic compensation. In these cases where the Position
Unwind value for a rotary application does not work out to be an integer number
of Motion Counts, the Motion Resolution attribute may be modified to a value
that is integer divisible by the Position Unwind value. This is done automatically
when selecting the Cyclic Travel Mode.
Motion Polarity
When Motion Scaling Configuration is set for Drive Scaling, Motion Polarity can
be used to switch the directional sense of the motion control system. A Normal
setting leaves the sign of the motion control command and actual signal values
unchanged from their values in the drive control structure. An Inverted setting
flips the sign of the command signal values to the drive control structure and flips
the sign of the actual signal values coming from the drive control structure.
Motion Polarity can therefore be used to adjust the sense of positive direction of
the motion control system to agree with the positive direction on the machine.
When the Motion Scaling Configuration is set to Drive Scaling, the Motion
Polarity inversion is performed between the CIP Motion Connection interface
and the drive control structure. When the Motion Scaling Configuration is set to
Controller Scaling, the Motion Polarity inversion is performed exclusively by the
controller.
To maintain directional consistency, the signs of all Signal Attribute values read
from the drive control structure or being written to the drive control structure are
determined by Motion Polarity. A comprehensive list of these Signal Attributes
and their access rules is defined in the following table:
A comprehensive list of these Directional Limit Attributes and their access rules is
defined in the following table:
Position Units
The Position Units string attribute allows user-defined engineering units rather
than "counts" to be used for measuring and programming all motion-related values
(position, velocity, acceleration, etc). Position Units can be different for each axis
and should be chosen for maximum ease of use in the machine application. For
example, linear axes might use Position Units of "Inches", "Meters", or "mm" while
rotary axes might use Position Units of "Revs" or "Degrees".
This attribute determines the period of time over which the system computes
Average Velocity for this axis instance.
Range limits based on coarse update period and history array size are ultimately
enforced for Average Velocity Timebase attribute by clamping to limit rather than
generating a value out of range error. Only if the value is outside the fixed
Min/Max limits is an out of range error given.
Conversion Constant
This attribute is used as a scaling factor allowing axis position, velocity, and
acceleration attributes to be displayed or configured in the user's preferred units
specified by the Position Unit string attribute. Specifically, the Conversion
Constant, is used by the motion system to scale the axis position units into motion
planner counts and vice versa. The Conversion Constant represents the number of
counts of the motion planner per Position Unit.
Position Unwind
If the axis is configured for cyclic Travel Mode, a value for the Position Unwind
attribute is required. This is the value used to perform electronic unwind of the
cyclic axis' position. Electronic unwind operation provides infinite position range
for cyclic axes by subtracting the position unwind value from both the actual and
command position every time the axis completes a machine cycle. To avoid
accumulated error due to round-off with irrational conversion constants, the
unwind value is expressed as an integer number of feedback counts per cycle.
See also
Motion Resolution Value Examples Motion Resolution is one of the Motion Scaling attributes. These examples
demonstrate how the Motion Resolution value may be used together with the
Conversion Constant to handle various machine applications.
Because the Conversion Constant is now a clean rational number, this system
scales without any loss of mechanical precision, for example, a move of three
Products would move the output shaft exactly one revolution. By setting the
Travel Mode to Cyclic, entering Position Scaling of three Products per Motor
Rev, and a Position Unwind value of one Product per Cycle, appropriate values for
scaling factors, Motion Resolution, Conversion Constant, and Rotary Unwind are
automatically calculated.
The control system is responsible for scaling Motion Counts into equivalent
Motor Feedback Counts. In this case, because the motor is directly coupled to the
load, one rotation of the shearing drum translates to one revolution of the motor
feedback device. Assuming that the motor feedback device is a typical optical
encoder with 4000 Feedback Counts/rev, a displacement of 300,000 Motion
Counts would be scaled by the control system to be 4000 Feedback Counts.
Instead of the motor directly driving the rotary shear drum, in this application
example the motor is driving the shearing drum through a 3:1 gearbox. Since the
Motion Unit is tied to the load, for example, Load Rev, the Motion Resolution,
Conversion Constant, and Rotary Unwind determined in the example above
apply equally well to this application.
The scaling of Motion Counts to Motor Feedback Counts, however, is not the
same due to the presence of the gearbox. In this case, one revolution of the
shearing mechanism translates to three revolutions of the motor. Nevertheless, the
control system has a count scaling feature that performs this scaling automatically.
This is done by selecting a Rotary Transmission as the Load Type, and setting the
Transmission Ratio Output to 1, and the Transmission Ratio Input to 3. In this
way, 300,000 Motion Counts per Load Rev is scaled exactly to 12,000 Motor
Feedback Counts, or three Motor Revs.
The motor feedback would, however, be rotary and resolution expressed in Motor
Feedback Counts per Motor Rev, in our case 4000 Feedback Counts per Motor
Rev. The default Motion Resolution is 1,000,000 Motion Counts per millimeter
and if the Position Unit is, say, centimeters, the Conversion Constant would be
10,000,000 Motion Counts per centimeter. This would be automatically
calculated by entering a Position Scaling of 1 centimeter per 10 millimeters.
Given that our application uses a 4:1 gearbox and a 5 mm pitch ball-screw, 5 mm
of ball-screw travel translates to 4 revolutions of the motor, or 16,000 Feedback
Counts. Again, the control system's count-scaling feature performs this scaling
automatically. This is done by selecting Linear Actuator as the Load Type, setting
the Transmission Ratio Output to 1, and the Transmission Ratio Input to 4,
setting the Actuator Type to be "Screw", and the Lead to 5 mm/rev. In this way,
5,000,000 Motion Counts, or 5 mm worth of screw displacement, is scaled exactly
to 16,000 Motor Feedback Counts, or exactly 4 Motor Revs.
See also
Motor Attributes These are the motor configuration attributes associated with a Motion Control
Axis that apply to various motor technologies. These motor technologies include
three-phase motor rotary, linear, permanent magnet and induction motors. Motor
attributes are organized according to the various motor types.
General Linear Motor Attributes These are the motor configuration attributes that apply specifically to linear
motor types.
The Linear Motor Pole Pitch attribute is a floating point value that specifies the
pole pitch of a linear motor in units of meters, and is equivalent to the electrical
cycle length.
The Linear Motor Rated Speed attribute is a floating point value that specifies the
nameplate rated speed of a linear motor. For PM motors, this is generally specified
at rated voltage based on either rated current, rated force, or rated power. For
induction motors this value is the speed of the motor driven at rated frequency
under rated force load. This value is synonymous with the term base speed.
The Linear Motor Mass attribute is a floating point value that specifies the
unloaded moving mass of a linear motor.
The Linear Motor Max Speed attribute is a floating point value that specifies the
absolute maximum operating speed of a linear motor in units of m/s. This speed
may be determined by the limitations of the motor, limitations of the drive power
structure, or by limitations of the mechanical system, whichever is less. Specifically,
this value can represent the maximum safe operating speed, maximum continuous
no-load speed, maximum continuous encoder speed, or maximum continuous
bearing speed of the motor. This value can be used by the drive to determine the
Linear Motor Overspeed Factory Limit.
The Linear Motor Damping Coefficient attribute is a floating point value that
specifies the damping, or viscous friction, associated with a linear motor.
The Linear Motor Integral Limit Switch attribute specifies if the motor has
integral limit switches.
See also
General Motor Attributes These are the general motor attributes that apply to all motor technologies.
The Motor Serial Number attribute is a 16-character string that specifies the serial
number of the motor. If the Motor Catalog Number is not available, the drive sets
this attribute to a Null string.
The Motor Data Source attribute specifies the source of motor data for the drive.
In both Drive NV and Motor NV cases, the specific motor and motor feedback
attributes that are sent or not sent to the drive during configuration are identified
in the CIP Drive Set Attr Update Bits attribute table.
Motor and motor feedback attributes sent to the drive device in Drive NV or
Motor NV are merely to confirm that the controller and the drive have the
agreement on the values of attributes critical to scaling operation. If the NV
attribute values in the drive differ from the values set by the controller, the drive
will reject the values with General Status indicating an Invalid Attribute Value.
The current list of motor and motor feedback attributes sent to the drive in the
NV modes are as follows:
1. Motor Unit
2. Feedback 1 Unit
3. Feedback 1 Type
7. Feedback 1 Turns
8. Feedback 1 Length
DB
The Motor Device Code attribute is a unique number assigned to a motor catalog
number. This value is used to insure that the motor and integral motor mounted
feedback device configuration data delivered from the controller matches the
actual motor and feedback data connected to the drive.
This comparison is only valid in the case where the Motor Data Source is
Datasheet or Database driven and the motor is equipped with a smart feedback
device. If the codes do not match, a negative acknowledge is given by the drive.
Motor Device Codes are assigned by the motor manufacturer. A value of 0 for the
Motor Device Code will be accepted by the drive without comparison.
Motor Type
The Motor Type attribute is an enumeration that specifies the motor technology.
When Motor Type is set to Not Specified, all motor configuration attribute values
associated with the motor are considered Not Applicable and will not be set by
configuration software nor will they be sent to the drive.
If Motor Data Source is Motor NV or Drive NV, the Motor Type may not be
known to the controller but is known by the drive, so the drive can operate in this
case without specifying the Motor Type. In this case, the Motor Type is not sent
to the drive.
Motor Unit
The Motor Unit attribute is a unit of measure for motor displacement. This
attribute is also used for sensorless operation since the Feedback Unit in that case
is not known. Motor Unit selection is based on Motor Type.
Motor Polarity
* Indicates the attribute cannot be set while the drive power structure is enabled (Power Structure Enable bit in CIP Axis Status
is true).
You can use the Motor Polarity attribute to make the direction of travel agree with
the user's definition of positive travel. It can be used in conjunction with the
Feedback Polarity bit to provide negative feedback, when closed loop control is
required. When commutating a PM motor, it is imperative that the commutation
phase sequencing match the motor phase sequencing to properly control the
motor.
The Motor Rated Voltage attribute is a floating point value that specifies the
nameplate AC voltage rating of the motor. This represents the phase-to-phase
voltage applied to the motor to reach rated speed at full load.
The Motor Rated Continuous Current attribute is a floating point value that
specifies the nameplate AC continuous current rating of the motor. This
represents the current applied to the motor under full load conditions at rated
speed and voltage. Any positive number. This is a database number and should not
be changed.
The Motor Rated Peak Current attribute is a floating point value that specifies the
peak or intermittent current rating of the motor. The peak current rating of the
motor is often determined by either the thermal constraints of the stator winding
or the saturation limits of PM motor magnetic material.
The Motor Rated Output Power attribute is a floating point value that specifies
the nameplate rated output power rating of the motor. This represents the power
output of motor under full load conditions at rated current, speed and voltage.
The Motor Overload Limit attribute is a floating point value that specifies the
maximum thermal overload limit for the motor. This value is typically 100%,
corresponding to the power dissipated when operating at the continuous current
rating of the motor, but can be significantly higher if, for example, cooling options
are applied. How the Motor Overload Limit is applied by the drive depends on the
overload protection method employed.
For induction motors, this attribute is often related to the Service Factor of the
motor. The Service Factor is defined in the industry as a multiplier which, when
applied to the rated power or current of the motor, indicates the maximum power
or current the motor can carry without entering an overload condition.
Regardless of the Motor Type, if the drive applies an I2T motor overload
protection method, then exceeding the specified Motor Overload Limit results in
an overload condition and activates I2T overload protection. While the motor is
overloaded, the Motor Capacity attribute value increases to indicate how much of
the motor's available I2T overload capacity has been utilized. When Motor
Capacity reaches 100% of its rated capacity, the drive can optionally trigger a
Motor Overload Action.
The Motor Overload Limit can also used by the drive to determine the absolute
thermal capacity limit of the motor, for example, the Motor Thermal Overload
Factory Limit, that if exceeded, generates a Motor Thermal Overload FL
exception.
The Motor Integral Thermal Switch attribute specifies if the motor has an integral
thermal switch to detect a Motor Overtemperature condition. Connection to the
motor thermal switch can be through the motor feedback interface, associated
with Axis I/O Status bit, Feedback 1 Thermostat, or through a discrete digital
input to the drive, associated with Axis I/O Status bit, Motor Thermostat. The
method of interface to the thermal switch is left to the drive vendor's discretion.
The Motor Max Winding Temperature attribute is a floating point value that
specifies the maximum winding temperature of the motor.
See also
General Permanent Magnet These are the motor configuration attributes that apply to Permanent Magnet
motor types in general.
Motor Attributes
PM Motor Resistance
The PM Motor Resistance attribute is a floating point value that specifies the
phase-to-phase, resistance of a permanent magnet motor.
PM Motor Inductance
The PM Motor Inductance attribute is a floating point value that specifies the
phase-to-phase, inductance of a permanent magnet motor.
The PM Motor Flux Saturation attribute is an array of floating point values that
specify the amount of flux saturation in the motor as a function of current. The
units for the nominal inductance values are percent, such that a value of 100%
means no saturation, and 90% means the inductance is 90% of its value at zero
current.
The first array entry specifies the flux saturation value at 12.5% of the Peak
Current Rating; the second entry specifies the value at 25%, and so on up to the
last entry, which specifies the value at 100% of the Peak Current Rating. (At zero
current, the motor is assumed to have no saturation, for example, an implied value
of 100%.)
PM Motor Lq Inductance
The PM Motor Lq Inductance attribute is a floating point value that specifies the
phase-to-neutral, q-axis, inductance of an interior permanent magnet motor.
PM Motor Ld Inductance
The PM Motor Ld Inductance attribute is a floating point value that specifies the
phase-to-neutral, d-axis, inductance of an interior permanent magnet motor.
The first array entry specifies the flux saturation value at 25% of the Continuous
Current Rating; the second entry specifies the value at 50%, and so on up to the
last entry, which specifies the value at 200% of the Peak Current Rating. (At zero
current, the motor is assumed to have no saturation, for example, an implied value
of 100%.)
The PM Motor Ld Flux Saturation value specifies the d-axis saturation at 100% of
the Continuous Current Rating.
The PM Motor Extended Speed Permissive value also determines the values of the
Motor Overspeed Factory Limit and Motor Overspeed User Limit that provide
overspeed protection. If the PM Motor Extended Speed Permissive is False, the
Motor Overspeed Limits will be based on the Bus Overvoltage Speed. If the PM
Motor Extended Speed Permissive is True, the Motor Overspeed Limits will be
based on the Max Extended Speed value.
See also
General Rotary Motor These are the motor configuration attributes that apply specifically to rotary
motor types.
Attributes
Rotary Motor Poles
The Rotary Motor Poles attribute is an integer that specifies the number of poles
per revolution for rotary motors. This value is always an even number, as poles
always exist in pairs.
The Rotary Motor Inertia attribute is a floating point value that specifies the
unloaded inertia of a rotary motor.
The Rotary Motor Rated Speed attribute is a floating point value that specifies the
nameplate rated speed of a rotary motor. For PM motors, this is generally specified
at rated voltage based on either rated current, rated torque, or rated power. For
induction motors this value is the speed of the motor driven at rated frequency
under rated torque load. This value is synonymous with the term base speed.
The Rotary Motor Max Speed attribute is a floating point value that specifies the
absolute maximum operating speed of a rotary motor in units of RPM. This speed
may be determined by the limitations of the motor, limitations of the drive power
structure, or by limitations of the mechanical system, whichever is less. Specifically,
this value can represent the maximum safe operating speed, maximum continuous
no-load speed, maximum encoder speed, maximum continuous motor bearing
speed, or maximum motor speed based on the drive power structure voltage limit.
This value can be used by the drive to determine the Rotary Motor Overspeed
Factory Limit.
The Rotary Motor Damping Coefficient attribute is a floating point value that
specifies the damping, or viscous friction, associated with a rotary motor.
The Rotary Motor Fan Cooling Speed attribute selects the output speed of the
motor below which the Motor Rated Continuous Current is derated due to the
reduced effectiveness of an integral fan cooling system.
The Rotary Motor Fan Cooling Derating attribute selects the % derating of the
motor when the motor is operating at a speed below the specified Motor Fan
Cooling Speed. A value of 70% would indicate that the motor can only run at 70%
rated continuous current when operating below the Motor Fan Cooling Speed.
See also
Induction Motor Attributes These are the motor configuration attributes that apply specifically to induction
motor types.
The Induction Motor Rated Frequency attribute is a floating point value that
specifies the nameplate frequency rating of an induction motor.
* Indicates the attribute cannot be set while the drive power structure is enabled (Power Structure Enable bit in CIP Axis
Status is true).
The Induction Motor Stator Resistance attribute is a floating point value that
specifies the Y circuit, phase-neutral, winding resistance of the stator as shown as
R 1 in the IEEE motor model.
The Induction Motor Stator Leakage Reactance attribute is a floating point value
that specifies the Y circuit, phase-neutral, leakage reactance of the stator winding,
at rated frequency, as shown as X 1 in the IEEE motor model.
The Induction Motor Rotor Resistance attribute is a floating point value that
specifies the phase-neutral equivalent stator-referenced winding resistance of the
rotor as shown as R 2 ' in the IEEE motor model.
The Induction Motor Rotor Leakage Resistance attribute is a floating point value
that specifies the Y circuit, phase-neutral, equivalent stator-referenced leakage
inductance of the rotor winding, at rated frequency, as shown as X 2 ' in the IEEE
motor model.
The Induction Motor Rated Slip Speed attribute represents the amount of slip at
motor rated current (full load) and motor rated frequency.
See also
Linear PM Motor Attributes These are the motor configuration attributes that apply specifically to linear PM
motor types.
The PM Motor Rated Force attribute is a floating point value that specifies the
nameplate continuous force rating of a linear permanent magnet motor in
Newtons (N).
The PM Motor Force Constant attribute is a floating point value that specifies the
force constant of a linear permanent magnet motor in Newtons per RMS Amp.
The PM Motor Linear Voltage Constant attribute is a floating point value that
specifies the voltage, or back-EMF, constant of a linear permanent magnet motor
in phase-to-phase RMS Volts per meter/sec.
If the optional PM Motor Force Constant, Kf, is not explicitly supported in the
implementation, the value may be computed from the PM Motor Linear Voltage
Constant, Ke, according to this equation: Kf (N/A rms ) = 1.732 * Ke (V rms /(m/s))
The PM Motor Linear Bus Overvoltage Speed attribute value corresponds to the
linear motor speed at which the back-EMF of the motor equals the maximum
operational bus voltage of the drive. When the extended speed range of a PM
motor is not permitted (PM Motor Extended Speed Permissive is False), this value
can be used to limit motor speed to protect the drive from damage due to bus
overvoltage conditions that can occur when disabling a PM motor at high speed.
When configured for Position Loop or Velocity Loop operation, this bus
overvoltage protection includes limiting the magnitude of the velocity reference
value allowed into the velocity summing junction to the Bus Overvoltage Speed
Limit value using the velocity limiter function. If the signal entering the velocity
limiter exceeds this velocity limit value, and the PM Motor Extended Speed
Permissive is False, the velocity limiter clamps the velocity reference to this value
and sets the Velocity Limit status bit. If the PM Motor Extended Speed Permissive
is True, or the value of this attribute is 0, this limit is not applied.
When the extended speed range of a PM motor is permitted (PM Motor Extended
Speed Permissive is True) the PM Motor Linear Max Extended Speed attribute
value can be used to limit the speed of a linear motor to protect the motor or load
from damage due to an overspeed condition.
When configured for Position Loop or Velocity Loop operation, this overspeed
protection includes limiting the magnitude of the velocity reference value allowed
into the velocity summing junction using the velocity limiter function. If the
signal entering the velocity limiter exceeds this velocity limit value, the velocity
limiter clamps the velocity reference to this value and sets the Velocity Limit status
bit. If the value of this attribute is 0, this limit is not applied.
If the related optional attribute, Rotary or Linear Motor Max Speed, is supported,
software will apply this maximum speed value as the Max Value for this attribute.
See also
Interior Permanent The following attribute tables list the motor configuration attributes that apply
only to Interior Permanent Magnet (IPM) motor types.
Magnet Motor Attributes
PM Motor Lq Flux Inductance
An array of floating point values that specify the amount of d-axis flux saturation
in the motor at rate current. The units for d-axis flux saturation values are
percent of Nominal Inductance, such that a value of 100% means no saturation,
and 90% means the inductance is 90% of its value at zero current given by the PM
Motor Ld Inductance attribute. The PM Motor Ld Flux Saturation value specifies
the d-axis flux saturation at 100% of the Continuous Current Rating.
An array of floating point values that specify the amount of d-axis flux saturation
in the motor at rate current. The units for d-axis flux saturation values are
percent of Nominal Inductance, such that a value of 100% means no saturation,
and 90% means the inductance is 90% of its value at zero current given by the PM
Motor Ld Inductance attribute. The PM Motor Ld Flux Saturation value specifies
the d-axis flux saturation at 100% of the Continuous Current Rating.
This value specifies the change in the Commutation Offset value in units of
electrical degrees as a linear function of current. When the Iq current is +100% of
rated continuous current, the Commutation Offset value is decreased by the value
of this attribute. When the Iq current is -100% the Commutation Offset is
increased by the value of the attribute. This attribute is used by the drive to
compensate for changes in the optimal Commutation Offset angle that can occur
as a function of motor current.
This floating point value represents the phase-to-phase q-axis motor inductance
measured by the Motor Test procedure.
This floating point value represents the phase-to-phase d-axis motor inductance
measured by the Motor Test procedure.
This array of floating point values represents the phase-to-phase q-axis stator
inductance of the motor as measured by the Motor Test procedure expressed as a
percentage of the measured Nominal Inductance, Lq, at 25%, 50%, 75%, 100%,
125%, 150%, 175% and 200% rated continuous current.
This floating point value represents the phase-to-phase d-axis stator inductance of
the motor as measured by the Motor Test procedure expressed as a percentage of
the measured Nominal Inductance, Ld, at 100% rated continuous current.
This floating point value represents the maximum speed of the motor as
determined by the Motor Test procedure.
This floating point value represents the change in motor Commutation Offset at
rated continuous current as measured by the Motor Test procedure.
See also
Load Transmission and Actuator These are the motor configuration attributes that apply specifically to rotary
transmission and linear actuator mechanisms associated with the axis.
Attributes
Load Type
The Load Type attribute is used to determine how the load is mechanically linked
to the motor. Direct enumerations indicate that the motor is directly coupled to
the load. Rotary enumerations indicate that the load is rotating and load dynamics
are measured using a rotary system of units. Linear enumeration indicate that the
load is moving linearly and load dynamics are measured using a linear system of
units.
Actuator Type
The Actuator Type attribute indicates the type of mechanism used for linear
actuation.
Actuator Lead
The Actuator Lead attribute is a floating point value that represents the lead or
pitch of a screw actuator that is a measure of the linear movement of the screw
mechanism per revolution of the screw shaft.
The Actuator Lead Unit attribute indicates the units of the Actuator Lead
attribute.
Actuator Diameter
The Actuator Diameter attribute is a floating point value that represents the
diameter of the pulley, sprocket, or pinion used to convert rotary motion into
tangential linear displacement of the load. The Actuator Diameter is internally
The Actuator Diameter Unit attribute is a value that indicates the units of the
Actuator Diameter attribute.
See also
Rotary PM Motor Attributes These are the motor configuration attributes that apply specifically to rotary
motor types.
The PM Motor Rated Torque attribute is a float that specifies the nameplate
continuous torque rating of a rotary permanent magnet motor.
The PM Motor Torque Constant attribute is a float that specifies the torque
constant, Kt, of a rotary permanent magnet motor in Newton-meters per RMS
Amp.
The PM Motor Rotary Voltage Constant attribute is a float that specifies the
voltage, or back-EMF, constant of a rotary permanent magnet motor in
phase-to-phase RMS Volts per KRPM.
If the optional PM Motor Torque Constant, Kt, is not explicitly supported in the
implementation the value may be computed from the PM Motor Rotary Voltage
Constant, Ke, according to this equation: Kt (N-m/A rms ) = 0.01654 * Ke
(V rms /Krpm).
This value corresponds to the rotary motor speed at which the back-EMF of the
motor equals the maximum operational bus voltage of the drive. When the
extended speed range of a PM motor is not permitted, this value can be used to
limit motor speed to protect the drive from damage caused from bus overvoltage
conditions that occur when disabling a PM motor at high speed.
When configured for Position Loop or Velocity Loop operation, this bus
overvoltage protection includes limiting the magnitude of the velocity reference
value allowed into the velocity summing junction to the Bus Overvoltage Speed
Limit value using the velocity limiter function. If the signal entering the velocity
limiter exceeds this velocity limit value, and the PM Motor Extended Speed
Permissive is False, the velocity limiter clamps the velocity reference to this value
and sets the Velocity Limit status bit. If the PM Motor Extended Speed Permissive
is True, or the value of this attribute is 0, this limit is not applied.
detection is the only source of protection when the axis is configured for Torque
Loop operation.
When the extended speed range of a PM motor is permitted (PM Motor Extended
Speed Permissive is True), this value can be used to limit the speed of a rotary
motor to protect the motor or load from damage due to an overspeed condition.
When configured for Position Loop or Velocity Loop operation, this overspeed
protection includes limiting the magnitude of the velocity reference value allowed
into the velocity summing junction using the velocity limiter function. If the
signal entering the velocity limiter exceeds this velocity limit value, the velocity
limiter clamps the velocity reference to this value and sets the Velocity Limit status
bit. If the value of this attribute is 0, this limit is not applied.
If the related optional attribute, Rotary or Linear Motor Max Speed, is supported,
software will apply this maximum speed value as the Max Value for this attribute.
See also
Safety Attributes The following attributes tables contains attributes associated with safety
functionality.
Axis Safety attributes are used with integrated CIP Safety functionality associated
with a Motion Device Axis Object instance included in a CIP Motion Safety
Drive. These attributes reflect the current state of an embedded Safety Core
within for a CIP Motion Safety Drive device that is designed to interoperate with
an external Safety Controller using a CIP Safety network connection. For this
reason, integrated safety functions are also referred to as "networked safety".
Guard Safety attributes are used with built-in Safety functionality associated with
a Motion Device Axis Object instance. These built-in safety attributes relate to the
behavior of a configurable Safety Core (SMSC) within the drive that executes
basic drive safety functions using hardwired safety inputs and safety outputs
without the services of a CIP Safety network connection.
Axis Safety Status Attributes The following attribute tables contains axis attributes used with the integrated
Safety functionality associated with a Motion Device Axis Object instance
included in a CIP Motion Safety Drive. These attributes reflect the current state
of an embedded Safety Core within for a CIP Motion Safety Drive device that is
designed to interoperate with an external Safety Controller using a CIP Safety
connection.
In the Logix Integrated Architecture, many of the safety functions can be executed
either in the drive or in the associated safety controller. A unique feature of the
architecture is that regardless of where the safety function is executed, the Axis
Safety Status and Axis Safety Fault information reported by these safety functions
is the same. This is achieved by the Safety Status Pass Thru feature where safety
functions executing in the safety controller transmit their fault and status
information to the drive via the Safety Output Assembly where this information is
combined with the fault and status information of safety function executing in the
Safety Core of the drive. The combined safety function fault and status data is
then "Passed Thru" to the associated Motion Device Axis Object instance
attributes.
SS1 Safe Stop 1 Yes Yes Monitors Category 1 Stop followed by STO.
SS2 Safe Stop 2 Yes No Monitors Category 2 Stop followed by SOS.
SOS Safe Operating Stop Yes No Monitor standstill condition for movement.
The Axis Safety State, Axis Safety Status, and Axis Safety Fault attributes defined
below are based on the values read from attributes resident in objects associated
with the Safety Core and are used by the motion control system to monitor the
behavior of the Safety Core via the CIP Motion connection.
Data
Usage Access T Default Min Max Semantics of Values
Type
Optional - DE Get/GSV T UINT - - - Enumeration:
Safety only 0 = Unknown (No Motion
Connection)
1 = Self-Testing
2 = Configured (No Safety
Connection)
3 = Self-Test Exception
4 = Running
5 = Recoverable Fault
6 = Unrecoverable Fault
7 = Configuring
8 = Not Configured
9-50 = Reserved by CIP
51 = Not Configured (Torque
Permitted)
52 = Running (Torque
Permitted)
53-99 = Device Specific
100-255 = Vendor Specific
The Axis Safety State attribute is an 8-bit enumerated value that indicates the state
of the associated Safety Supervisor object of the device as it applies to this axis
instance. There is only one Safety Supervisor object servicing the CIP Motion
device so its state generally applies to all applicable Axis instances of the device.
This means that all instances of this object generally have the same state for this
attribute.
The two exceptions to this general state behavior are the Waiting for TUNID
with Torque Permitted (state=51) and Executing with Torque Permitted
(state=8) states that have axis specific qualification. When the Safety Supervisor
State is Waiting for TUNID with Torque Permitted, if the Axis Safety Status bit,
Safe Torque Disabled, is set, the Axis Safety State is set to Waiting for TUNID.
When the Safety Supervisor State is Executing with Torque Permitted, if the Axis
Safety Status bit, Safe Torque Disabled, is set, the Axis Safety State is Executing.
The Axis Safety Status attribute is a collection of bits indicating the status of the
standard safety functions for the axis as reported by the embedded Safety Core of
the device. The Axis Safety Status word is a concatenation of two 16-bit safety
status attributes. The lower 16-bits are the current Safety Stop Status attribute
value of the Safety Stop Functions object associated with this axis instance. The
upper 16-bits are the current Safety Limit Status attribute value of the Safety
Limit Functions object associated with this axis instance with the exception of the
two most significant bits that are masked off to accommodate two Safety Output
Connection status bits. Specifically, the Safety Output Connection Closed bit,
when set, indicates that the Safety Output Connection has either not been opened
or has been closed. The Safety Output Connection Idle bit, when set, indicates
that the Safety Output Connection's Run/Idle bit has been set to Idle.
For Rockwell Automation safety drive devices, the safety status data from the
drive's Safety Core may include safety status from the Safety Controller through
the Pass Thru data included in the Safety Output assembly. This allows the Axis
Safety Status attribute to reflect safety function status conditions regardless of
where the safety function is executed, be it in the Safety Controller, or the drive's
Safety Core.
The Axis Safety Status - RA attribute is a collection of bits indicating the status of
the Rockwell Automation specific safety functions for the axis as reported by the
embedded Safety Core of the device. For Rockwell Automation safety drive
devices, the safety status data from the drive's Safety Core may include safety status
from the Safety Controller through the Pass Thru data included in the Safety
Output assembly. This allows the Axis Safety Status RA attribute to reflect safety
function status conditions regardless of where the safety function is executed, be it
in the Safety Controller, or the drive's Safety Core.
The Axis Safety Faults attribute is a collection of bits indicating the safety fault
status of the axis associated with standard safety functionality as reported by the
embedded Safety Core of the device. When a safety fault condition occurs, the
Safety Core forces the axis into a Safe State and if the Safety Fault Action is set to
Major Fault or Minor Fault, the corresponding bit is set in the Axis Safety Faults
attribute. An active axis safety fault bit remains latched even if the underlying
safety fault condition is cleared by the Safety Core. A Fault Reset Request to the
associated axis clears the axis safety fault bits, but the bits immediately set again if
the underlying safety fault conditions are still present. The Axis Safety Faults
bitmap is a concatenation of two 16-bit safety fault attributes. The lower 16-bits is
the current Safety Stop Faults attribute value of the Safety Stop Functions object
associated with this axis instance. The upper 16-bits is the current Safety Limit
Faults attribute value of the Safety Limit Functions object associated with this axis
instance. Bits 30 and 31 are used to indicate two safety faults conditions that are
not tied to the drive safety functions. Bit 30 indicates that the Safety Validator
object (0x3A) has detected a safety connection fault. Bit 31 indicates that the
Safety Supervisor object (0x39) has detected a recoverable fault and transitioned to
the Abort state.
For Rockwell Automation safety drive devices, the safety fault status data from the
drive's Safety Core may include safety faults from the Safety Controller through
the Pass Thru data included in the Safety Output assembly. This allows the Axis
Safety Faults attribute to reflect safety function fault conditions regardless of
where the safety function is executed, be it in the Safety Controller, or the drive's
Safety Core.
The Axis Safety Faults - RA attribute is a collection of bits indicating the safety
fault status of the axis associated with Rockwell Automation specific safety
functionality as reported by the embedded Safety Core of the device. When a
safety fault condition occurs, the Safety Core forces the axis into a Safe State and if
the Safety Fault Action is set to Major Fault or Minor Fault, the corresponding bit
is set in the Axis Safety Faults RA attribute. An active axis safety fault bit remains
latched even if the underlying safety fault condition is cleared by the Safety Core.
A Fault Reset Request to the associated axis clears the axis safety fault bits, but the
bits immediately set again if the underlying safety fault conditions are still present.
For Rockwell Automation safety drive devices, the safety fault status data from the
drive's Safety Core may include safety faults from the Safety Controller through
the Pass Thru data included in the Safety Output assembly. This allows the Axis
Safety Faults RA attribute to reflect safety function fault conditions regardless of
where the safety function is executed, be it in the Safety Controller, or the drive's
Safety Core.
The Axis Safety Alarms attribute is a collection of bits indicating the safety alarm
status of the axis associated with standard safety functionality as reported by the
embedded Safety Core of the device. When a safety fault condition occurs, the
Safety Core forces the axis into a Safe State and, if the Safety Fault Action is set to
Alarm, the corresponding bit is set in the Axis Safety Alarms attribute. An active
axis safety alarm bit shall remain set as long as the underlying safety fault condition
is present in the Safety Core.
The Axis Safety Alarm bitmap is a concatenation of two 16-bit safety fault
attributes. The lower 16-bits is the current Safety Stop Faults attribute value
(Attribute 41) of the Safety Stop Functions object associated with this axis
instance. The upper 16-bits is the current Safety Limit Faults attribute value
(Attribute 41) of the Safety Limit Functions object associated with this axis
instance. Bit 30 indicates that the Safety Validator object (0x3A) has detected a
safety connection fault. Bit 31 indicates that the Safety Supervisor object (0x39)
has detected a recoverable fault and transitioned to the Abort state.
For Rockwell Automation safety drive devices, the safety fault status data from the
drive’s Safety Core may include safety faults from the Safety Controller via the
Pass Thru data included in the Safety Output assembly. This allows the Axis
Safety Alarms attribute to reflect safety function fault conditions regardless of
where the safety function is executed, be it in the Safety Controller, or the drive’s
Safety Core.
The Axis Safety Alarms - RA attribute is a collection of bits indicating the safety
alarm status of the axis associated with RA specific safety functionality as reported
by the embedded Safety Core of the device. When a safety fault condition occurs,
the Safety Core forces the axis into a Safe State and, if the Safety Fault Action is set
to Alarm, the corresponding bit is set in the Axis Safety Alarm RA attribute. An
active safety alarm bit remains set as long as the underlying safety fault condition is
present in the Safety Core.
For Rockwell Automation safety drive devices, the safety fault status data from the
drive’s Safety Core may include safety faults from the Safety Controller via the
Pass Thru data included in the Safety Output assembly. This allows the Axis
Safety Alarms RA attribute to reflect safety function fault conditions regardless of
where the safety function is executed, be it in the Safety Controller, or the drive’s
Safety Core.
The Safety Fault Action attribute is an enumerated value that specifies the action
when the Safety Core reports a safety fault condition.
The Safe Torque Off Action attribute determines the stopping method for the
motor when:
• The drive detects a Safe Torque Off (STO) Active condition that the Safe
Stop 1 (SS1) Active condition does not initiate. The embedded Safety Core
through the Axis Safety Status attribute reports the condition.
• The Safe Torque Off Action Source is set to Connected Drive.
Each Safe Torque Off Action enumeration initiates one of the two defined
Stopping Sequences, Category 0 Stop, or Category 1 Stop. Each enumeration
definition follows the same enumerations defined for the Stopping Action
attribute.
Category 1 Stop enumerations of Current Decel & Disable or Ramped Decel &
Disable are also used with a configured delay between the STO Active condition
and Safe Torque Disabled. This allows the drive to bring the motor to a controlled
stop and engage a brake before disabling the power structure. Vertical load
applications use this feature.
Tip: An example of a configured delay between the STO Active condition and the Safe
Torque Disabled condition is STO to Safe Brake C=Control (SBC) Delay or STO delay.
Start Inhibited or Major Fault State occurs after applying the Stopping Sequence.
For either final state, the inverter power structure of the device is disabled with
integrity. The is enforced by the STO safety function of the Safety Core.
The Safe Torque Off Action Source attribute determines whether the drive or the
controller initiates the stopping sequence in response a STO Active condition in
the Axis Safety Status attribute that was not initiated by an SS1 or Safe Stop 2
(SS2) Active condition.
When configured for Connected Drive (default), the drive will initiate the
stopping sequence according to the selected Safe Torque Off Action. However,
the drive must have an open connection to the controller for the configured
stopping action to occur. If the drive is not connected, the drive would have
already initiated the configured Connection Loss Stopping Action.
When an SS1 or SS2 Active condition occurs, as indicated by the Axis Safety
Status attribute, and the Axis Safety Stopping Source is set to Connected Drive,
this value determines the stopping method the drive is to apply to the motor. The
selected stopping method is applied while in the Stopping state and the final state
after the stopping method completes is the Stopped state. In this final state the
device's inverter power structure will either be Disabled and free of torque, if
initiated by an SS1 Active status bit, or actively held (Hold selection) in a static
condition if initiated by an SS2 Active status bit.
This attribute determines whether the drive or the controller initiates the
stopping sequence in response to an SS1 or SS2 Active bit transition in the Axis
Safety Status attribute.
When configured for Connected Drive (default), the drive will initiate the
stopping sequence according to the selected Safe Stopping Action. However, the
drive must have an open connection to the controller for the configured stopping
action to occur. If the drive is not connected, the drive would have already
initiated the configured Connection Loss Stopping Action.
A 32-bit container holding general purpose Safety Data passed from the Safety
Controller thru the Safety Pass Thru object attribute, Safety Pass Thru Data A.
A 32-bit container holding general purpose Safety Data passed from the Safety
Controller thru the Safety Pass Thru object attribute, Safety Pass Thru Data B.
See also
Guard Safety Attributes These are the attributes associated with the built-in Safety functionality of an axis.
These attributes relate to the behavior of a configurable Safety Core within the
drive that executes basic drive safety functions using hardwired safety inputs and
safety outputs. These functions do not require the services of a CIP Safety network
connection. This safety functionality covers the following safety functions as
defined by IEC-61800-5-2, EN-954-1, and IEC-60204 standards:
• Safe Restart
• Safe Stop
• Safe Limited Speed
• Safe Speed Monitoring
• Safe Maximum Speed
• Safe Direction Monitoring
• Safe Door Monitoring
• Safe Door Monitoring
The Guard Status and Guard Fault attributes are defined in the axis to monitor
the behavior of built-in Drive Safety functionality. The term Guard is used for
these status attributes to differentiate these attributes from the Safety status
attributes associated with the integrated Safety functionality provided by a CIP
Safety connection.
See also
Guard Safety Status Attributes The Guard Status attribute is a collection of bits indicating the safety status of the
motion axis.
Guard Status
3 Guard Stop Input Indicates the current state of the Safe Stop input.
4 Guard Stop Request Indicates if a safe stop operation has been requested. The safe stop
request can be initiated by the Safe Stop Input or in response to a
Safety Fault. The bit is only cleared by a successful safety reset.
5 Guard Stop In Progress Indicates if the Safe Stop (SS) function of the safety core is in
progress. This bit is set when the Safe Stop input transitions from on
to off and clears at the end of the stop delay or when a safety fault
occurs.
6 Guard Stop Decel Indicates if the Safe Stop (SS) function of the safety core is actively
decelerating the axis. This bit is set after the monitoring delay expires
and clears at the end of the stop delay or when a fault occurs.
7 Guard Stop Standstill Indicates if the Safe Stop (SS) function of the safety core is in the safe
stopped mode, for example, when it has successfully stopped the axis
and is performing zero speed monitoring. This bit is set after the stop
delay expires and clears when a fault occurs.
8 Guard Stop Output Indicates the current state of the Safe Stop output.
9 Guard Limited Speed Input Indicates the current state of the Safe Limited Speed (SLS) input.
10 Guard Limited Speed Request Indicates if a safe speed operation has been requested. The safe stop
request can be initiated by the Safe Limited Speed input. The bit is
only cleared by a successful safety reset.
11 Guard Limited Speed Monitor In Indicates if the Safe Speed (SLS/SSM) monitoring function of the
Progress safety core is actively checking speed. This bit is set when the Safe
Limited Speed input transitions from on to off and the associated
monitoring delay has expired.
12 Guard Limited Speed Output Indicates the current state of the Safe Limited Speed (SLS) output.
13 Guard Max Speed Monitor In Indicates if the Safe Max Speed (SMS) monitoring function of the
Progress safety core is in progress.
14 Guard Max Accel Monitor In Progress Indicates if the Safe Max Accel (SMA) monitoring function of the
safety core is in progress.
15 Guard Direction Monitor In Progress Indicates if the Safe Direction Monitoring (SDM) function of the safety
core is in progress.
16 Guard Door Control Lock Indicates if the Door Control Output is being commanded to the
Locked state.
17 Guard Door Control Output Indicates the current state of the Safe Door Control output.
18 Guard Door Monitor Input Indicates the current state of the Door Monitor (DM) input.
19 Guard Door Monitor In Progress Indicates if the Safe Door Monitoring (DM) function of the safety core
is in progress.
20 Guard Lock Monitor Input Indicates the current state of the Safe Lock Monitoring input.
21 Guard Enabling Switch Input Indicates the current state of the Safe Enabling Switch Monitor input.
Guard Faults
The Guard Faults attribute is a collection of bits indicating the safety faults of the
drive axis. When a safety fault condition occurs the safety core processor always
requests a Safe Stop operation and notifies the drive controller to set the
appropriate Guard Faults bit. This bit remains latched even if the safety fault
condition is cleared in the safety core. A Fault Reset Request to the associated axis
clears the safety fault bits, but the bits set again immediately if the underlying
safety fault condition is still present.
1 Guard Internal Fault An internal fault has been detected by the Safety Core
hardware. This can includes safety processor faults,
inter-processor communications faults, safety power supply
faults, and gate drive circuitry.
3 Guard Gate Drive Fault Indicates that the Gate Drive (MP OUT) circuit used to disable
the drive power structure has detected an error.
4 Guard Reset Fault The Safety Reset input was ON at power up.
5 Guard Feedback 1 Fault A problem has been detected with the feedback 1 device.
6 Guard Feedback 2 Fault A problem has been detected with the feedback 2 device.
7 Guard Feedback Speed Compare Fault A speed miss-compare was detected between the two
feedback devices.
8 Guard Feedback Position Compare Fault A position discrepancy was detected between the two
feedback devices.
9 Guard Stop Input Fault A fault has been detected on the Safe Stop input(s).
10 Guard Stop Output Fault A fault has been detected on the Safe Stop cascading
outputs.
11 Guard Stop Decel Fault A speed fault was detected during the deceleration
monitoring.
12 Guard Stop Standstill Fault Zero speed was not detected by the end of the stop delay.
13 Guard Stop Motion Fault Motion was detected after stop was detected and the door
unlocked.
14 Guard Limited Speed Input Fault A fault has been detected on the Safe Limited Speed input(s).
15 Guard Limited Speed Output Fault A fault has been detected on the Safe Limited Speed outputs.
16 Guard Limited Speed Monitor Fault The Safe Limited Speed has been exceeded.
17 Guard Max Speed Monitor Fault The Safe Maximum Speed has been exceeded.
18 Guard Max Accel Monitor Fault The Safe Maximum Acceleration has been exceeded.
19 Guard Direction Monitor Fault Motion in the restricted direction has been detected.
26 Guard Enabling Switch Monitor Fault The Enabling Switch Monitor (ESM) Inputs were detected as
OFF when they should have been ON.
27 Guard Feedback 1 Voltage Monitor Fault Monitored voltage level for the Feedback 1 device is out of
allowed range for operation.
28 Guard Feedback 2 Voltage Monitor Fault Monitored voltage level for the Feedback 2 device is out of
allowed range for operation.
29 Reserved (RLM Reset Fault)
30...31 Reserved
See also
Stopping and Braking These are the active stopping and braking related attributes associated with a
Motion Control Axis.
Attributes
Stopping Action
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
• In the case of a Disable Request, the stopping method is applied while in the
Stopping state and the final state after the stopping method is completed is
the Stopped state.
• In the case of an Abort Request, the stopping method is applied while in the
Aborting state and the final state after the stopping method completes is the
Major Faulted state.
In either final state the device's inverter power structure will either be Disabled
(Disable selection) and free of torque or actively held (Hold selection) in a static
condition. This attribute has no impact or relationship to the planner generated
acceleration and deceleration profiles. This attribute does not, in any way,
determine the stopping actions applied in response to fault conditions.
# Indicates the attribute cannot be set while the tracking command (Tracking Command bit in CIP Axis Status is true).
When a CIP Motion connection loss is detected, this value determines the
stopping method to apply to the motor. Each supported Stopping Action initiates
the associated Stopping Sequence (IEC60204-1 Category Stops 0, 1, and 2). If the
connection is closed intentionally using a Forward Close service, the selected
stopping method is applied while in the Stopping state and the final state after the
stopping method completes is the Initializing state. If the connection is
unintentionally lost and the resulting Node Fault generated (Node Fault Codes 1
or 6), the selected stopping method is applied while in the Aborting state and the
final state after the stopping method completes is the Major Faulted state. In
either final state the device’s inverter power structure will either be Disabled
(Disable selection) and free of torque or actively held (Hold selection) in a static
condition.
Stopping Torque
When disabling or aborting an axis, this value determines the maximum amount
of torque producing current available to stop the motor when the Stopping Action
is set to Current Decel. If this attribute is not supported, the drive device will use
the configured Positive and Negative Peak Current Limits.
When an external resistive brake is used, the Resistive Brake Contact Delay can be
set to delay the enabling of the device power structure until after the resistive
brake has had time to connect the motor to the drive device. When an external
resistive brake is used, an external contactor switches the UVW motor leads from
the inverter power structure to an energy dissipating resistor to stop the motor.
Note that this switching does not occur instantaneously and so enabling the power
structure too early can cause electrical arcing across the contactor. To prevent this
condition, the Resistive Brake Contact Delay can be set to the maximum time that
it takes to fully close the contactor across the UVW motor lines so when the axis is
enabled, the inverter power structure is not enabled until after the Resistive Brake
Contact Delay Time has expired. Resistive Brake operation is only applicable to
PM Motor types.
The following sequence further defines how the Resistive Brake Contact Delay
factors into the overall Enable Sequence that may also include the operation of a
Mechanical Brake.
Enable Sequence:
3. Wait for "Resistive Brake Contact Delay" while Resistive Brake contacts
close.
The Mechanical Brake Control attribute governs the operation of the drive's
Mechanical Brake Output that controls the mechanical brake mechanism. When
set to Automatic, the Mechanical Brake is under the control of the axis state
machine. The sequencing for the brake is described in detail by the Mechanical
Brake Engage Delay and Mechanical Brake Release Delay attributes. When set to
Brake Release, the brake is unconditionally released, and no longer under the
control of the axis state machine.
When enabling the axis, the Mechanical Brake Release Delay value determines the
amount of time the device will delay transition from the Starting state to the
Running or Testing states. This delay prevents any commanded motion of the
motion axis until the external mechanical brake has had enough time to disengage.
If supported, a Torque Proving operation is included in this sequence prior to
releasing the brake.
Enable Sequence:
3. Wait for "Resistive Brake Contact Delay" while Resistive Brake contacts
close.
When disabling the motion axis using a Category 1 Stopping Action, the
Mechanical Brake Engage Delay value determines the amount of time the device
power structure will remain enabled after the axis has decelerated to standstill.
This attribute allows time for an external mechanical brake to engage. The
configured Stopping Action determines the type of stopping sequence applied. If
supported, a Brake Proving operation is included in the Category 1 stopping
sequence prior to disabling the power structure.
Zero Speed
This attribute sets the speed threshold associated with the zero speed criteria of
the stop sequence. Zero Speed is specified as a percent of motor rated speed. When
Zero Speed Time attribute is supported, this attribute sets the speed threshold
where the zero speed timer starts. When the axis speed has been below the Zero
Speed threshold for Zero Speed Time the axis has satisfied the zero speed criteria.
In all but Category 2 stops, this results in action to engage the mechanical brake. If
this attribute is not supported, the zero speed threshold is left to the vendor’s
discretion and typically set to 1% of motor rated speed. Axis speed in the above
description is based on the Velocity Feedback signal, or in the case of a Frequency
Control drive, axis speed is based on Velocity Reference signal.
When supporting a Load Observer, the zero speed criteria is not based on the
Velocity Estimate since that signal can differ considerably from the actual speed of
the motor. When the Load Observer is configured to apply the Velocity Estimate
to the velocity loop summing junction as Velocity Feedback, the zero speed criteria
must be based on the velocity feedback signal input to the Load Observer.
This attribute sets the amount of time that the axis speed must be below the zero
speed threshold, set by the Zero Speed attribute or established by the drive vendor,
before satisfying the zero speed criteria. In all but Category 2 stops, when this
attribute is set it results in action to engage the mechanical brake. If this attribute
is not supported, the amount of time needed to satisfy the zero speed criteria is left
to the vendor’s discretion and typically is immediate (0). Axis speed in the above
description is based on the Velocity Feedback signal, or in the case of a Frequency
Control drive, axis speed is based on Velocity Reference signal.
When supporting a Load Observer, the zero speed criteria is not based on the
Velocity Estimate since that signal can differ considerably from the actual speed of
the motor. When the Load Observer is configured to apply the Velocity Estimate
to the velocity loop summing junction as Velocity Feedback, the zero speed criteria
must be based on the velocity feedback signal input to the Load Observer.
This enumerated value allows the drive to tailor motor control behavior for
vertical load applications. When the Enabled enumeration is selected, the drive
attempts, whenever possible, to avoid applying Category 0 stop actions in response
to Major Fault conditions. The drive may tailor other aspects of its behavior to
best handle vertical loads.
Proving Configuration
This attribute enables the operation of the drive's Torque Proving and Brake
Proving functions that work in conjunction with mechanical brake control. When
Proving is enabled, the mechanical brake must be set as soon as the drive is
disabled. When the brake is under the control of the axis state machine this is
automatic. But when controlled externally, failure to set the brake when the drive
is disabled can cause a free fall condition on a vertical application.
When enabled, the drive performs a Torque Prove test of the motor current while
in the Starting state to "prove" that current is properly flowing through each of the
motor phases before releasing the brake. Should the Torque Prove test fail, a
Motor Phase Loss exception is generated.
While Torque Proving functionality is applicable to drive Control Modes that are
not capable of generating reliable holding torque based on a feedback device, such
as Frequency Control and Sensorless Velocity Control, Torque Proving should
not be used in these modes for applications where holding torque is critical to safe
operation, such as in a typical lift or crane application.
If the optional Brake Test Torque attribute is supported, the Torque Prove test
also includes a proactive Brake Test to ensure the mechanical brake is functioning
properly. Should the Brake Test detect brake slip, a Brake Slip exception is
generated.
When Proving is enabled, the drive also performs a Brake Prove test while in the
Stopping or Aborting states to "prove" proper mechanical brake function before
the drive power structure is disabled. Should the Brake Prove test detect brake slip
a Brake Slip exception is generated.
Unless another vendor specific method is used to address a Brake Slip condition in
the Stopping or Aborting state, the appropriate Fault Action for the Brake Slip
exception is Torque Limited Stop and Hold. This Fault Action applies holding
torque to arrest the brake slip and transitions the axis to the Major Faulted state.
When Proving is enabled, and the Auto-Sag feature is supported, upon detection
of a brake slip condition, the drive has the capability of safely lowering the load to
the ground in a controlled series of increments. The Auto Sag Configuration
attribute is used to enable this feature. In addition to Brake Slip initiating a Brake
Slip exception, the drive also generates a Brake Malfunction start inhibit when the
Auto Sag feature is enabled.
When Proving, Auto Sag, and Auto Sag Start are all enabled, the drive also
monitors for brake slip in the Stopped or Faulted states. If brake slip is detected,
the drive power structure is automatically started to arrest the slip allowing the
Auto Sag function to safely lower the load to the ground. Upon detection of brake
slip, a Brake Slip exception is generated along with a Brake Malfunction start
inhibit.
The sequencing of the torque and brake "prove" tests are described in detail by the
Mechanical Brake Engage Delay and Mechanical Brake Release Delay attributes.
Proving tests are performed when enabling or disabling the drive axis. During
these state transitions a series of operations are performed by the drive to ensure
the proper function of the motor (Torque Proving) and the brake (Brake
Proving).
This attribute sets the percent of motor rated torque applied to the motor by the
Torque Prove test as part of the Torque Proving function executed in the Starting
state. The Torque Prove test applies current to the motor to "prove" that current is
properly flowing through each of the motor phases before releasing the brake.
This attribute sets the percent of motor rated torque applied to the motor by the
Brake Test as part of the Torque Proving function executed in the Starting state.
This Brake Test proactively tests the ability of the mechanical brake to hold the
maximum anticipated load before releasing the brake and allowing operation.
Should the Brake Test detect brake slip, a Brake Slip exception is generated.
If the Brake Test Torque attribute value is 0 the Brake Test is not performed in
the Starting state.
This attribute determines the amount of time the drive will take to ramp the
applied torque of the motor down to zero during the Brake Proving test in the
Stopping or Aborting state. The Brake Prove Ramp Time determines the ramp
down rate of the applied torque output by dividing the Torque Limit by the Brake
Prove Ramp Time. The Torque Limit in this case is the maximum of the
configured Torque Limit Positive and Torque Limit Negative values. The Brake
Prove test is performed to check for brake slip before the power structure is
disabled.
This attribute determines the amount of brake slip allowed after the brake is
engaged. If this tolerance is exceeded while the brake is engaged, a Brake Slip
exception is generated. Brake slip can therefore be monitored in any axis state
where the brake is engaged.
The DC Injection Brake Current attribute defines the brake current level injected
into an induction motor stator when DC Injection Brake is selected as the
Stopping Action. This attribute is specified as a percent of motor rated speed.
The DC Injection Brake Time attribute defines the amount of time that the DC
brake current is injected into an induction motor stator when DC Injection Brake
is selected as the Stopping Action. This attribute is specified in seconds.
The Flux Braking Enable attribute value determines if the drive device is to apply
additional flux current to the induction motor in an effort to increase motor losses
and reduce the deceleration time while in the Stopping state. This feature is useful
when there is no Shunt Regulator or Regenerative Brake available.
This attribute is used to enable the optional Auto Sag feature that, in the event of
detected a brake slip condition, safely lowers the load to the floor in a series of
controlled Auto Sag Slip Increments. When a brake slip condition is detected and
Auto Sag is enabled, the drive not only sets the standard Brake Slip exception, but
the drive also sets the Brake Malfunction start inhibit. This prevents the drive
from restarting after the load has been safely lowered to the floor.
This attribute sets the incremental amount of brake slip allowed by the drive's
optional Auto Sag function before restoring holding torque. When brake slip
occurs, the drive allows this amount of displacement and then automatically
enables the power structure and applies holding torque to arrest the slip. The drive
then ramps the motor torque to zero based on the Brake Prove Ramp Time while
checking for slip. Should brake slip continue, the cycle repeats. In crane and lift
applications, this repeating "Auto Sag" cycle is designed to lower the load in a
controlled series of Auto Sag Slip Increments until the load reaches the ground.
This attribute sets the time limit over which the drive checks for brake slip as
performed by the Auto Sag function before restoring holding torque. When brake
slip occurs, the drive allows this amount of time before automatically enabling the
power structure and applying holding torque. The drive then ramps the motor
torque to zero based on the Brake Prove Ramp Time while checking for slip.
Generally, in a brake slip situation, the Auto Sag Slip Time Limit expires when the
load reaches the ground after one or more Auto Sag Slip Increment cycles. With
no further slip occurring while the motor torque is ramping to zero, the Auto Sag
feature transitions the axis to the Major Faulted state and the drive power
structure is disabled.
The optional Auto Sag Slip Time Limit attribute is not required by the Auto Sag
feature. If not supported, a vendor specific value for the Auto Sag Slip Time is
applied, typically 0.25 seconds.
When the Auto Sag Configuration attribute is set to Enabled, this attribute is used
to enable the Auto Sag function in the Stopped or Faulted state. When Auto Sag
Start is enabled, the drive monitors the load for possible brake slip and should the
amount of brake slip exceed the Brake Slip Tolerance a Brake Slip exception is
generated, along with a Brake Malfunction start inhibit. When this occurs, the
drive power structure is enabled (Started) without holding torque and the axis
transitions to the Aborting State. The drive continues to monitor brake slip and
when the amount of slip exceeds the Auto Sag Slip Increment holding torque is
applied to the motor to arrest the brake slip. The drive then ramps the motor
torque to zero based on the Brake Prove Ramp Time while again checking for slip.
Should brake slip continue and exceed the Auto Sag Slip Increment, holding
torque is applied and the cycle repeats. In crane and lift applications, this repeating
"Auto Sag" cycle is designed to lower the load in a controlled series of Auto Sag
Slip Increments until the load reaches the ground.
See also
Stopping Sequences There are three different stopping sequences defined for stopping and braking
related attributes. These three stopping sequences align with the following
IEC-60204-1 Stop Categories:
All actions initiated by the control or the drive to stop the axis or disable its
associated inverter power structure must execute one of these three stopping
sequences. Category 0 and Category 1 Stop sequences coordinate the disabling of
the drive power structure with brake operation and in some cases, optional Brake
Proving functionality.
The above stopping sequences are listed in order of precedence should a stopping
sequence be initiated while another stopping sequence is in progress. For example,
a Category 0 stopping sequence shall preempt a Category 1 stopping sequence in
progress, but a Category 1 stopping sequence shall not supersede a Category 0
stopping sequence in progress. This rule of precedence holds true regardless of the
source that initiated the stopping sequence.
The following stopping sequences are defined in the context of a Disable Request
generated stop, where the stopping methods are applied in the Stopping state and
the stopping sequences ends up in the Stopped state. In the context of a Major
Fault action, these same stopping methods are applied in the Aborting state and
the stopping sequences end up in the Major Faulted state. In the context of a
Shutdown Request, the Category 0 stopping method below is applied in the
Stopping state and the stopping sequence ends up in Shutdown state.
4. Wait for zero speed or "Coasting Time Limit" or a factory set timeout,
whichever occurs first.
Torque applied to stop the motor before the inverter is disabled. Brake Proving is
applicable.
3. Wait for zero speed or 'Stopping Time Limit' or a factory set timeout,
whichever occurs first.
Torque is applied to stop the motor and inverter is left enabled to provide holding
torque. The mechanical brake is not used. Brake Proving is not applicable. A
Category 2 Stop is only allowed in no Start Inhibit condition is present.
3. Wait for zero speed or "Stopping Time Limit" or a factory set timeout,
whichever occurs first.
Tip: Recommended criteria for Zero Speed is based on Velocity Feedback, or in the case of Frequency Control drive, based
on Velocity Reference. Zero Speed criteria can be established explicitly through optional Zero Speed and Zero Speed
Time attributes or implicitly as 1% of motor rated speed or left to the drive vendor’s discretion.
See also
Proving Operational Proving tests are performed when enabling or disabling the drive axis. During
these state transitions a series of operations are performed by the drive to ensure
Sequences
the proper function of the motor (Torque Proving) and the brake (Brake
Proving).
The following flow charts define these operational sequences in the context of a
drive enable transition and a drive disable or abort transition.
See also
Start Inhibits Attributes These are the Start Inhibit related attributes associated with a Motion Control
Axis Object instance. Start Inhibits are conditions that prevent transition of the
axis from the Stopped State into any of the operational states.
A bit map that specifies the current state of all standard conditions that inhibits
starting of the axis.
A bit map that specifies the current state of all Rockwell Automation specific
conditions that inhibits starting of the axis.
See also
Standard Start Inhibits on page 576
Rockwell Automation Specific Start Inhibits on page 578
CIP Axis Attributes on page 259
Standard Start Inhibits
This table defines the list of standard start inhibits associated with the Start
Inhibits attribute.
0 -- Reserved -- This bit cannot be used since the Start Inhibit Code is defined by the
associated bit number and Start Inhibit Code of 0 means no fault
condition is present.
1 Axis Enable Input The Enable Input is not active.
2 Motor Not Configured The associated motor has not been configured for use.
3 Feedback Not Configured The associated feedback device has not been configured. The offending
feedback channel is encoded in the associated Fault/Alarm Sub Code.
4 Commutation Not Configured The associated PM motor commutation function has not been configured
for use.
5 Safe Torque Off Active The integrated Safe Torque Off safety function is active based on the Safe
Torque Off Active bit (bit 3) of the Axis Safety Status attribute being set.
6 Converter Bus Unload The Converter Bus Unload bit (bit 3) of the Control Status attribute from
the controller is set, indicating that the converter supplying power to
this drive axis has requested that it not draw power from the DC Bus.
7-15 --Reserved--
This table maps the Standard Start Inhibit bits with their Logix Designer Start
Inhibit tag names. Start Inhibit bit names always end with an Inhibit suffix.
Bit Tag
0 NA
1 AxisEnableInputInhibit
2 MotorNotConfiguredInhibit
3 FeedbackNotConfiguredInhibit
4 CommutationNotConfiguredInhibit
5 SafeTorqueOffActiveInhibit
6 ConverterBusUnload
See also
Rockwell Automation Specific The following table defines a list of standard start inhibits associated with
Start Inhibits the Start Inhibits attribute.
0 -- Reserved -- This bit cannot be used because the Start Inhibit Code is defined by the associated
bit number and Start Inhibit Code of 0 means no fault condition is present.
1 Volts Hertz Curve Conflict exists in the V/Hz curve definition.
Definition
2 Motor Feedback Cannot run using the selected motor control mode with Primary Feedback or
Required Alternate Feedback set as open loop.
3 Speed Limit Speed Ref Limit Conflict, either Minimum Forward Speed Limit exceeds Maximum
Configuration Forward Speed Limit, or Minimum Reverse Speed Limit exceeds Maximum Reverse
Speed Limit.
4 Torque Prove When Torque Prove Configuration is enabled, Control Mode, Feedback Mode,
Configuration Motor Feedback Type and Motor Option Configuration must be properly set.
5 Safe Torque Off The safety function has disabled the power structure.
6 Safety Reset Required The safety reset input needs to be toggled before the safety board will allow
motion again.
7 Safety Not Configured The embedded safety function of the drive has not been configured.
8 Stop Command Active There is an active Stop Command present. For example, the Stop button on the
drive is behind held active. This inhibit condition prevents the drive from starting
when the Stop Command is active.
9 Feedback Device The feedback device is being reset. A feedback device reset process is typically
Reset performed after a Feedback Loss condition. This inhibit condition prevents the
drive from Starting until the feedback reset process is completed.
10 Brake Malfunction The start inhibit is set when the Auto Sag function is enabled, and the brake slip is
detected based on motor movement exceeding the configured Brake Slip
Tolerance while the mechanical brake is engaged. This typically indicates that the
mechanical brake may not be capable of holding the load.
11 AC Line Contactor This start inhibit is set when the state of the AC Line Contactor OK digital input
Input differs from the state of Contactor Enable Digital Output. When this start inhibit is
set it generally indicates that AC Line Contactor is not working correctly and is not
capable of charging the dc bus. This start inhibit is checked only when the AC Line
Contactor OK digital inputs is available and AC Line Contactor Input Checking is
Enabled.
12-15 --Reserved--
This table maps the Start Inhibit bits with their Logix Designer Start Inhibit tag
names. Start Inhibit bit names always end with an Inhibit suffix.
Bit Tag
0 NA
1 VoltsHertzCurveDefinitionInhibit
2 MotorFeedbackRequiredInhibit
3 SpeedLimitConfigurationInhibit
4 TorqueProveConfigurationInhibit
5 SafeTorqueOffInhibit
6 SafetyResetRequiredInhibit
7 SafetyNotConfiguredInhibit
8 StopCommandActiveInhibit
9 FeedbackDeviceResetInhibit
10 BrakeMalfunctionInhibit
11 ACLineContactorInputInhibit
See also
DC Bus Condition Attributes These are Motion Control Axis attributes associated with the DC Bus including
functionality to address both under-voltage and over-voltage conditions.
DC Bus Voltage
Measured DC Bus Voltage. For inverters and DC Converter Types, the DC Bus
measured is an input to the device. For all other Converter Types, the DC Bus
measured is an output of the device.
Tip: If the device does not support this bus voltage averaging concept, hard code this value.
For inverters and DC Converter Types, the DC Bus measured is an input to the
device. For all other Converter Types, the DC Bus measured is an output of the
device.
The Bus Regulator Reference attribute returns the current turn on voltage
threshold for the bus regulator.
Bus Configuration
The Bus Configuration attribute is an enumerated selection that specifies how the
DC Bus is used.
Standalone. Specifies that DC Bus power supplied by the converter section of the
drive is applied only to the drive power structure.
Shared AC/DC. Specifies that the converter associated with this CIP Motion
device is to supply and share DC Bus power with other drives. This would
typically result in de-rating of the converter’s continuous current rating when
there are multiple converter devices paralleled in a bus sharing group. Shared DC
specifies that this drive is sharing DC bus power generated by another Shared
Shared DC. Non CIP Converter specifies that this drive is receiving DC bus
power generated by an external AC/DC converter that is not CIP Motion
compliant and distributing its DC bus power to other CIP Motion drives. A drive
configured for Shared DC - Non CIP Converter is responsible for communicating
the status of the external converter to the control system as if the external
converter were integrated with the drive. Specifically, this communication
includes the DC Bus Up and DC Bus Unload status bits reflecting the current
state of associated external converter.
Shared DC/DC specifies that the converter associated with this CIP Motion
device supplies and shares DC bus power with other Shared DC devices. DC/DC
converters may convert input DC bus power from a Shared AC/DC converter to
a different DC Bus output voltage level to supply one or more Shared DC drives.
It may also simply distribute DC bus power from a Shared AC/DC converter to
multiple Shared DC drives without any conversion. A Shared DC/DC converter
has a unique capability in that it can be both a bus master for a bus group and a bus
slave in a different bus group.
The Bus Voltage Select value indicates the expected bus voltage level of the drive
application. High bus voltage selection is usually associated with drive running on
the North American power grid, while operating in Europe a Low Bus Voltage
selection would be appropriate. This parameter can be used to compensate for
these different bus voltage levels in the current loop.
The Bus Regulator Action attribute controls the method of operation of the DC
Bus Regulator that addresses the regenerative over-voltage conditions that occurs
when decelerating a motor. If Disabled, no regulation is applied to the DC Bus
level by this device to control regenerative energy sourced by the motor. When
Shunt Regulator is selected the associated shunt regulation hardware is applied to
the DC Bus to dissipate. regenerative energy via an internal or external resistor.
The Bus Regulator Action attribute controls the method of operation of the DC
Bus Regulator that addresses the regenerative over-voltage conditions that can
occur when decelerating a motor. If Disabled, no regulation is applied to the DC
Bus level by this device to control regenerative energy sourced by the motor. When
Shunt Regulator is selected the associated shunt regulation hardware is applied to
the DC Bus to dissipate regenerative energy via an internal or external resistor.
When controlling Induction Motors, additional bus regulation methods are
available that do not require a shunt regulator. When Adjust Frequency is selected,
the output frequency of the device is controlled relative to the speed of the motor
to control the amount of regenerative energy pumped into the DC Bus. Different
sequential application of shunt regulation and frequency control can be applied to
motor. When Bus Follower is selected, the DC Bus is generated by an external
converter rather than an integral converter. No bus regulation is applied to the
DC Bus level and the drive does not generate an exception if the DC Bus is still
active when the DC Bus contactor of the integrated converter is open. In this
context, the integral converter is not connected to AC power.
The Regenerative Power Limit attribute limits the amount of power allowed to
transfer between the motor and the DC Bus during regenerative braking of the
motor load. Since this is regenerative power, the value of the limit is negative.
The Converter Motoring Power Limit attribute limits the amount of motoring
power allowed to transfer from the AC Line to the motor via the DC Bus.
Converter Rated is defined as the Converter Rated Input Power attribute value.
The Shunt Regulator Resistor Type defines using either the Internal or External
Shunt resisto.
The External Shunt Regulator ID is the Rockwell specific identifier for the
External Shunt Regulator. A value of 0 indicates use of a custom shunt regulator
that requires user configuration.
Use the External Shunt Power attribute after configuring the external shunt
resistor. The External Shunt Power attribute value specifies the power rating of
the external shunt resistor, in Kilowatts.
Use the External Shunt Pulse Power attribute after configuring the external shunt
resistor. The attribute value specifies the power for delivering to the external shunt
resistor for one second, without exceeding the rated element temperature. There
are approximations to help determine this attribute if this information is not
available
from your vendor. Shunt Pulse Power (Kilowatts) = 75,000 * lbs, where lbs is the
weight of the resistor wire element.
Another is that the thermal time constant = Shunt Pulse Power (Kilowatts) /
'Shunt Power’ (Kilowatts) sometimes referred to as thermal mass.- the time for the
resistor element to reach 63% of rated temperature with applied rated Kilowatts.
A third method for determining this value: The pulse Kilowatts for 1 second is
twice the watt rating of a 2 second pulse. In other words, the watt*sec rating is a
constant if the pulse duration is short compared to the thermal time constant of
the resistor and is a function of the element mass.
The External Bus Capacitance attribute also is applicable with standalone drives
that allow connection to an external capacitor. This attribute is not applicable
when the Bus Regulator Action is set to Bus Follower.
The External Shunt Resistance attribute represents the resistance of the External
Shunt Regulator resistor.
The Power Loss Action attribute sets the reaction to a DC Bus under-voltage
condition when the DC Bus voltage or AC Line RMS voltage drops below a
hard-coded threshold in the device or the configured Power Loss Threshold. This
provides a specific (configured) response to an incoming power loss while the
drive/motor is running.
A Continue action selection configures the drive to ignore the power loss
condition and continue to run for as long as possible. A Bus Undervoltage
exception may occur if the DC Bus Voltage falls below the Factory or User Limits.
Otherwise, operation will continue until the low voltage power supplies drop out.
There may be concerns operating the power structure below the point where the
gate drives start to lose power potentially resulting in damage to the device. The
Bus Undervoltage Exception Actions will be set accordingly.
A Coast Thru action selection configures the drive to zero the PWM output of
the drive while leaving the axis in the Running state. For a drive, this effectively
disable power flow to the motor through the devices power structure. If the
incoming power returns before the timeout period, given by the Power Loss Time,
the drive automatically starts to control the motor again. If, however, the power
doesn't return before Power Loss Timeout period expires, a Bus Power Loss
exception is generated.
A Decel Regen action selection configures the drive to regeneratively charge the
DC bus by decelerating the motor using the bus regulator to regulate the bus
voltage at a predetermined level. When incoming power is restored the drive
returns to normal operation. If, however, the drive reaches zero speed or the Power
Loss Time period expires before the incoming power has restored, the drive power
structure is disabled and a Bus Power Loss exception is generated.
A Ride Thru action selection configures the device to zero the PWM output of
the device while leaving the axis in the Running state. For a regenerative converter,
this disables regenerative power flow through the devices power structure to the
AC line. If the incoming power returns before the timeout period, given by the
Power Loss Time, the device automatically restarts PWM modulation. If,
however, the power does not return before Power Loss Timeout period expires, a
Converter AC Power Loss exception is generated.
Sets the Level for Power Loss as percent of nominal DC Bus Voltage or nominal
AC Line Voltage.
Shutdown Action
Shutdown Action selects the action for the device when a Shutdown Request
initiates.
Disable, the default action for a drive, immediately disables the device's power
structure according to the Category 0 Stop Sequence. For a regenerative converter,
this action immediately disables the converter’s power structure to stop
regenerative power flow.
If Drop DC Bus is selected, action can be taken to drop the DC Bus voltage as
well. This is generally done by opening an AC Contactor Enable output provided
by the device that controls power to the converter.
The Shutdown Action executes the Category 0 Stop Sequence for a drive.
When the Power Loss Action is set to Coast Thru, Ride Thru, or Decel Regen,
this attribute sets the timeout value before a Bus Power Loss exception is
generated by the drive, or a Converter AC Power Loss exception is generated by
the converter, in response to a Power Loss condition. For details, see the Power
Loss Action attribute table earlier in this topic.
See also
Converter AC Line Input The following attribute tables contain attributes related to the AC Line input to a
Converter.
Attributes
Converter AC Line Monitoring These are the converter AC line monitoring attributes associated with the AC
Line input to a Converter.
Attributes
AC Line Frequency
AC Line Current
The AC Line Current attribute represents the average RMS AC line current for
all three phases as measured over an AC cycle.
AC Line Voltage
The AC Line Voltage - Nominal attribute represents the filtered average RMS AC
line-to-line voltage based on a time constant. The low pass filter time constant is
factory set or configurable using the optional AC Line Voltage Filter Time
Constant.
The AC Line Voltage Time Constant attribute sets the low pass filter time
constant applied to the AC Line Voltage to determine the AC Line Voltage
Nominal attribute value.
The AC Line Active Power attribute represents the measured active AC Line
power. A positive value indicates motoring power and a negative value indicates
regenerative power. See diagram below.
The AC Line Reactive Power attribute represents the measured reactive AC Line
power. A positive value indicates lagging power is consumed by the converter and
negative value indicates leading power is produced by the converter. See diagram
below.
The following diagram illustrates the definition for Leading and Lagging Power
Factor, Active Power, and Reactive Power for Regenerative Converters.
Apparent Power, Sc, is the vector sum of active and reactive power and is always a
positive value. It is specified in Volt-Amperes. Active power, Pc, is the real or
active component of apparent power delivered to the load and can be positive
(motoring) or negative (regenerating). Reactive power, Qc, is the imaginary or
reactive component of apparent power delivered to the AC line. A positive
value of reactive power indicates that reactive power is absorbed (lagging reactive
power) from the line by the converter. A negative value of reactive power indicates
that reactive power is delivered (leading reactive) to the AC line from the
converter.
The AC Line Power Factor attribute represents the measured input power factor
defined as the ratio of active power over apparent power. The value ranges from -1
to +1. A positive value indicates motoring power and a negative value indicates
regenerative power.
AC Line 1 Current
AC Line 2 Current
AC Line 3 Current
Where:
I avg = (I L1 +I L2 +I L3 )/3
I L#(max) = Max(I L1 ,I L2 ,I L3 )
The AC Line Ground Current attribute represents the ground current typically
measured as the instantaneous sum of the AC Line currents for all three phases.
AC Line 1 Voltage
AC Line 2 Voltage
AC Line 3 Voltage
Where:
V LL ( avg) = (V L1 +V L2 +V L3 )/3
V LL(max) = Max(V L1 ,V L2 ,V L3 )
The AC Line Sync Error attribute represents the phase error associated with the
AC line synchronization function of the regenerative converter.
The AC Line Filter Derating attribute indicates the percent derating applied to
the converter power when the AC Line Filter is operating above its rated thermal
capacity and the converter’s Bus Voltage Reference Source is set to Manual.
Derating shall not be applied when Bus Voltage Reference Source is set to
Automatic. When applied in an AC Line filter overload condition, the AC Line
Filter Derating value directly impacts attribute values for Reactive Power
Available, Converter Rated Output Power, Converter Rated Input Power, and
Converter Capacity.
The AC Line Filter Derating value is calculated based on the time averaged voltage
difference between the DC Bus Voltage and the optimal Bus Voltage Reference
determined by the Converter based on AC line input voltage and the thermal
limits of the AC Line Filter. For example, a value of 70% indicates that the
converter can only run at 70% rated continuous power when the AC line filter has
reached its rated thermal capacity. If converter power exceeds the 70% derating,
the converter’s thermal overload protection function is activated leading to the
configured Converter Overload Action or a Converter Thermal Overload FL or
UL exception.
Converter Rated is defined as the Converter Rated Input Power attribute value.
See also
Converter AC Line Configuration These are the regenerative converter AC Line configuration attributes associated
with the AC Line input to a converter.
Attributes
Converter AC Input Frequency
The Converter AC Input Voltage attribute configures the converter for the
intended AC line voltage during normal operation.
The AC Line Voltage Unbalance Limit attribute sets the maximum allowed
voltage unbalance between the AC line phases. Exceeding this limit results in a
Converter AC Unbalance exception. Nominal voltage is defined by the AC Line
Voltage Nominal attribute.
The AC Line Current Unbalance Limit attribute sets the maximum allowed
current unbalance between the AC line phases. Exceeding this limit results in a
Converter AC Unbalance exception. Rated current is defined by the Converter
Rated Input Current attribute.
The AC Line Sync Error Tolerance attribute sets the maximum allowed phase
error associated with the AC line synchronization function of the regenerative
converter. Exceeding this limit results in an AC Line Sync Loss exception.
See also
Converter AC Line Source These are the converter AC Line source configuration attributes associated with
the AC Line input to a Converter.
Configuration Attributes
AC Line Source Select
The AC Line Source Select attribute determines which AC Line source is active
for the converter and applies the configured impedance and power rating of that
source to the converter's control structure.
The AC Line Source Power attribute sets the power rating of the transformer or
generator feeding power to the converter as a percentage of the converter's power
rating.
The AC Line Source Power - Alternate attribute selects the power rating of the
alternate transformer or generator feeding power to the converter as a percentage
of the converter's power rating.
See also
AC Line Condition Attributes These are the Motion Control Axis attributes pertaining to various conditions of
the AC Line input primarily for a Regenerative Converter.
The AC Line Voltage Sag Action attribute sets the reaction to a Voltage Sag
condition when any one of the AC Line phase voltages drops below a hard-coded
threshold in the device or the configured AC Line Voltage Sag Threshold. This
provides a specific (configured) response to an incoming AC Line Voltage Sag
condition while the device is running.
The AC Line Voltage Sag Threshold attribute sets the level for AC Line Voltage
Sag as percent of nominal AC Line Voltage. Nominal voltage is defined by the AC
Line Voltage Nominal attribute. Measured AC Line Voltage values less than this
threshold indicate an AC Line Voltage Sag condition.
When the AC Line Voltage Sag Action is set to Ride Thru, this attribute sets the
timeout value before an AC Line Voltage Sag exception is generated by the device
in response to a Voltage Sag condition. A value of 0 in this case results in an
immediate exception.
The Converter Input Phase Loss Action attribute sets the reaction to an AC input
phase loss condition. This provides a specific (configured) response to an
incoming phase loss while the converter is running.
When the Converter Input Phase Loss Action is set to Ride Thru, this attribute
sets the timeout value before a Converter AC Phase Loss Exception is generated
by the device in response to the Converter Input Phase Loss condition. A value of
0 in this case results in an immediate exception.
The AC Line Frequency Change Action attribute sets the converter’s reaction
when the rate of change of the AC line frequency exceeds a hard-coded threshold
or the configured Frequency Change Threshold.
The AC Line Frequency Change Threshold attribute sets the level of AC line
frequency change that results in the AC Line Frequency Change condition.
When the AC Line Frequency Change Action is set to Ride Thru, this attribute
sets the timeout value before an AC Line Frequency Change exception is
generated by the converter in response to an AC Line Frequency Change
condition. A value of 0 in this case results in an immediate exception.
The AC Line Sync Loss Action attribute sets the reaction to a loss of AC line
synchronization by the converter’s line synchronization function (for example,
PLL). This provides a specific (configured) response to an incoming line
synchronization loss condition while the converter is running.
When the AC Line Sync Loss Action is set to Ride Thru, this attribute sets the
timeout value before an AC Line Sync exception is generated by the converter in
response to an AC Line Sync Loss condition. A value of 0 in this case results in an
immediate exception.
See also
Converter Control These are the Motion Device Axis Object attributes related to the Converter
function of a CIP Motion device.
Attributes
Converter Types The Converter function of a CIP Motion device covers a wide range of power
conversion technologies from simple non-regenerative AC/DC converters,
typically known as diode rectifiers, to sophisticated regenerative AC/DC
converters that provide closed loop control of DC bus voltage as well as active and
reactive current flow back to the grid. This also includes support for DC/DC
power converters.
The following attribute table is used to identify the type of Converter function.
Converter Type
The term Converter applies to any device function that converts AC or DC input
power to DC Bus output power that may be used by Inverter power structures to
drive motors.
Passive AC/DC represents the class of devices that convert AC input power to
DC output power using passive electronics. A diode bridge rectifier is an example
of a Passive AC/DC converter. They do not have the capability to transfer energy
back to the AC main supply.
Active AC/DC represents the class of devices that transfer power between AC
and DC sources using active electronics. For example, Active AC/DC converters
include both regenerative converters that regulate bi-directional power transfer
between AC and DC sources and low harmonic converters that regulate power
flow from the AC source to the DC bus.
DC/DC represents the class of devices that convert power between a primary DC
input source and one or more secondary DC buses using active electronics, or
simply distribute primary DC input power to secondary DC buses. DC/DC
converters with active electronics are capable of transferring energy between a
primary DC input source and one or more secondary DC buses, each with
different voltage levels.
See also
Converter Control Mode The attribute table contains attributes that govern the overall control behavior of
a converter in the Motion Control Axis.
Attributes
Converter Configuration
* The default value can specified by the specific drive profile (AOP).
When modified programmatically, via SSV, the Converter Control Mode value
cannot be set to an enumeration that the current Converter Configuration cannot
support. For example, if the Converter Configuration is set for Active Current
Control, the Converter Control Mode cannot be changed to Bus Voltage Control
since bus voltage loop attributes have not been configured. Refer to the following
table for a list of valid Converter Control Modes for a Converter Configuration:
The Converter Control Mode attribute determines the basic mode of operation
for the regenerative converter.
When Bus Voltage Control is selected, the converter controls the DC bus voltage
output of the converter. The output of the DC bus control loop drives an inner
Active AC Line current control loop to maintain the commanded DC bus voltage
level established by the Bus Voltage Set Point.
When Active Current Control is selected, the converter disables DC bus voltage
regulation and directly controls the Active AC Line current component based on
the Active Current Command. During initial configuration, the controller derives
this value from the the Converter Configuration attribute value.
The Converter Startup Method attribute specifies the method to use to initiate
transition of the regenerative converter axis from the Stopped state to the Starting
state.
See also
Converter Bus Voltage These are the bus voltage control configuration attributes associated with a
regenerative converter.
Control Configuration
Attributes Bus Voltage Set Point
The Bus Voltage Set Point attribute sets the reference voltage used to actively
regulate the DC Bus Voltage of the converter when in the Running state and the
Bus Voltage Reference Source is set to Manual.
The Bus Voltage Reference Source attribute selects between Automatic and
Manual source for the Bus Voltage Reference. Automatic (default) allows the
converter to optimize the Bus Voltage Reference for best converter performance.
When Manual, the converter uses the user configured Bus Voltage Set Point value
for the Bus Voltage Reference signal.
The Bus Voltage Loop Bandwidth attribute value determines the proportional
gain, Kbp, of the bus voltage loop that multiplies the Bus Voltage Error signal.
This value represents the unity gain bandwidth of the bus voltage loop.
The Bus Voltage Integrator Bandwidth attribute value determines the bus voltage
loop integral gain, Kbi, which together with the Kbp, multiplies the integrated Bus
Voltage Error signal. This value represents the bandwidth of the bus voltage
integrator beyond which the integrator is ineffective. A value of 0 for this attribute
disables the integrator.
The Bus Voltage Rate Limit attribute sets the DC Bus rate limit for the Bus
Voltage Set Point that becomes the DC Bus Reference signal when the Bus
Voltage Reference Source is set to Manual.
The Bus Voltage Error Tolerance attribute determines the absolute maximum Bus
Voltage Error value that can be tolerated without causing an Excessive Bus Voltage
Error exception.
The Bus Voltage Error Tolerance Time attribute determines the maximum
amount of time that the Bus Voltage Error Tolerance can be exceeded without
generating an exception.
current applied to the DC Bus for the purpose of bus impedance compensation.
Selecting the Voltage Estimate configures the observer to dynamically estimate
voltage based on an internal model of the DC Bus. When Voltage Estimate is
selected, this signal is applied to the voltage loop to provide superior control loop
performance. The Voltage Estimate may be used in combination with the Bus
Observer by selecting Bus Observer with Voltage Estimate.
The Bus Observer Bandwidth attribute value determines the proportional gain,
Kbop, of the Bus Observer. This value represents the unity gain bandwidth of the
Bus Observer.
The Bus Observer Integrator Bandwidth attribute value determines the Bus
Observer integral gain, Kboi, that together with the Kbop, multiplies the
integrated error signal within the observer. This value represents the bandwidth of
the integrator beyond which the integrator is ineffective. A value of 0 for this
attribute disables the integrator.
See also
Converter Bus Voltage These are the attributes of the bus voltage control loop associated with a
regenerative converter.
Control Signal Attributes
Bus Voltage Reference
The Bus Voltage Reference attribute is the converter DC bus voltage reference
signal into the bus voltage regulation summing junction to be compared with the
bus voltage feedback signal. When the Bus Voltage Reference Source is set to
Manual, the Bus Voltage Reference value shall equal the rate limited Bus Voltage
Set Point when the axis is in the Running state. In all other axis states, or when the
Bus Voltage Reference Source is set to Automatic, the Bus Voltage Reference is
under local control of the Converter and typically derived from the AC Line
Voltage.
The Bus Voltage - High Limit attribute is the high limit for the Bus Voltage
Reference signal established by the regenerative converter.
The Bus Voltage - Low Limit attribute is the low limit for the Bus Voltage
Reference signal established by the regenerative converter. This limit is typically
derived from the AC Line Voltage Nominal attribute value.
The Bus Voltage Feedback attribute is the measured DC bus voltage of the
converter output that is applied to the bus voltage summing junction.
The Bus Voltage Error attribute is the error between the Bus Voltage Reference
and Bus Voltage Feedback signals that is the output of the bus voltage loop
summing junction.
The Bus Voltage Loop Output attribute is the output of the bus voltage loop
forward path representing the total control effort of the bus voltage control loop.
The Bus Observer Voltage Rate Estimate attribute is the output of the Bus
Observer that, when the Bus Observer block is enabled, is applied to the voltage
rate summing junction. When the Bus Observer is enabled, this signal
compensates for disturbances to the DC Bus relative to an ideal DC Bus model
with fixed capacitance. When the Bus Observer is disabled, this signal is 0.
The Bus Observer Current Estimate attribute is the product of the Bus Observer
Voltage Rate Estimate signal and the current System Capacitance value, Kc. In the
Bus Observer configuration, this signal represents the estimated current
disturbances to the DC Bus relative to an ideal DC Bus model. When the Load
Observer is disabled, this signal is 0.
See also
Converter Current These are the current reference configuration attributes associated with a
Regenerative Converter.
Reference Configuration
Attributes System Capacitance
The System Capacitance attribute is the scaling gain value that converts voltage
rate commanded by the bus voltage control loop into equivalent active current,
expressed as a percent of the converter's current rating. Properly set, this value
represents the total system capacitance of the DC bus.
The Active Current Command attribute sets the reference current used to actively
regulate the Active Current of the converter when in the Running state and
configured for AC Line Current Control mode. A positive value implies motoring
current. A negative value implies regenerative current.
The Reactive Current Command attribute sets the reference current used to
actively regulate the Reactive Current of the converter when in the Running state
and configured for AC Line Current Control mode. A positive value implies
The Active Current Trim attribute is the additional current command added to
the active current reference summing junction.
The Active Current Low Pass Filter Bandwidth attribute is the break frequency
for the low pass filter applied to active current reference signal. A value of 0 for this
attribute disables this feature.
The Active Current Notch Filter Frequency attribute is the center frequency of
the notch filter applied to the active current reference signal. A value of 0 for this
attribute disables this feature.
The Active Current Rate Limit attribute sets the magnitude limit on the rate of
change of the converter's active current reference signal. This attribute applies only
when configured for AC Line Current Control mode.
The Reactive Current Rate Limit sets the magnitude limit on the rate of change of
the converter's reactive current reference signal. This attribute applies only when
configured for AC Line Current Control mode.
See also
Converter Current Reference These are the current reference signal attributes associated with a Regenerative
Converter.
Signal Attributes
Active Current Reference
See also
Converter Current Control These are the current control configuration attributes for the Regenerative
Converter.
Configuration Attributes
Converter Current Loop Bandwidth
The Converter Current Loop Bandwidth attribute is the AC Line Current Loop
Proportional Gain value that multiplies the active and reactive AC Line Current
Error signals. This value directly determines the bandwidth of the active and
reactive AC line current loops.
The Converter Current Vector Limit attribute sets the value applied to current
vector limiter to provide a configurable limit to the magnitude of the converter's
active and reactive current reference signals.
Use the Converter Current Loop Tuning Method attribute to configure the
responsiveness of the active and reactive current loops.
With the Direct method, the current loop response is determined directly by the
Converter Current Integrator Bandwidth value that maps to the integral gain, Kci,
of the converter’s current loop. When configured for the Direct tuning method,
the Converter Current Loop Damping attribute value has no effect on the current
control loops.
With the Calculated method, the loop response is determined by the Converter
Current Loop Damping value. The converter uses this value to calculate the
appropriate internal current loop integral gain, Kci, based on the Converter
Current Loop Bandwidth and known load characteristics of the AC Line. When
configured for the Calculated tuning method, the Converter Current Loop
Integrator Bandwidth attribute value has no effect on the current control loops.
The Converter Current Loop Damping attribute is the Damping factor that,
together with the specified Converter Current Loop Bandwidth value, determines
responsiveness of the active and reactive AC line current loops. This attribute may
be used as an alternative to directly setting the Kci gain value for the current loops.
A damping factor of 1 results in a critically damped current loop.
See also
Converter Current Control These are the active and reactive current control attributes for the associated
Motion Device Axis of a Regenerative Converter.
Signal Attributes
Converter Operative Current Limit
The Converter Operative Current Limit attribute represents the current limit
value applied to the magnitude of the compensated current reference vector,
consisting of Active and Reactive components. This value represents the
minimum of all Converter Current Limit Sources.
The Active Power Limit attribute is the current limit that corresponds to the
maximum active power transfer between the AC Line and the converter. This
value is calculated by the converter based on the value of the source impedance
between the converter and the AC Line, and the DC Bus Voltage level.
The Reactive Power Limit attribute is the current limit that corresponds to the
maximum reactive power transfer between the AC Line and the converter. This
value is calculated by the converter based on the value of the source impedance
between the converter and the AC Line, and the DC Bus Voltage level.
The Converter Current Limit Source attribute represents the operative source of a
converter current limit when a current limit condition occurs.
The Active Current Error attribute is the error between active current reference
and active current feedback signals that is the output of the active power
producing current loop summing junction. % Rated is defined as percent of the
Converter Rated Input Current.
The Reactive Current Error attribute is the error between reactive current
reference and reactive current feedback signals that is the output of the reactive
power producing current loop summing junction. % Rated is defined as percent of
the Converter Rated Input Current.
The Active Decoupling Voltage attribute is the voltage signal added to the active
current control loop output to compensate for the effects of reactive current and
apply an active feedforward signal.
The Reactive Decoupling Voltage attribute is the voltage signal added to the
reactive current control loop output to compensate for the effects of active current
and apply a reactive feedforward signal.
The Active Voltage Output attribute is the active power producing output voltage
from the active current control loop.
The Reactive Voltage Output attribute is the reactive power producing output
voltage from the reactive current control loop.
The Active Current Feedback attribute is the measured active power producing
current of the AC line based on transformed AC Line Current Feedback from the
three phases. A positive value indicates motoring current and negative value
indicates regenerative current.
The Reactive Current Feedback attribute is the reactive power producing current
of the AC line based on transformed AC Line Current Feedback from the three
phases. A positive value indicates lagging current and negative value indicates
leading current.
The Active Voltage Feedback attribute is the active power producing voltage of
the AC line based on transformed AC Line Voltage Feedback from the three
phases.
The Reactive Voltage Feedback attribute is the reactive power producing voltage
of the AC line based on transformed AC Line Voltage Feedback from the three
phases.
The AC Line Electrical Angle attribute is the estimated electrical angle of the AC
line voltage.
See also
Converter Reactive Power These are the reactive power control attributes for the Motion Device Axis Object
for a Regenerative Converter.
Control Attributes
Reactive Power Set Point
The Reactive Power Set Point attribute sets the reference current used to actively
regulate the AC Line Reactive Power of the converter when in the Running state.
Attribute units are expressed in percent for Converter Rated Output Power (Attr
ID 724).
Positive value indicates lagging kVAR and negative value indicates leading kVAR.
The Reactive Power Reference attribute is the rate limited reference signal into the
Reactive Power Control function. Attribute units are expressed in percent for
Converter Rated Output Power (Attr ID 724).
The Reactive Power Available attribute represents available Reactive Power based
on the converter rating and the load on the converter. Attribute units are
expressed in percent for Converter Rated Output Power (Attr ID 724).
The Reactive Power Rate Limit attribute sets the active current rate limit for AC
Line Reactive Power Set Point input. The output of the Reactive Power Rate
Limit function is the AC Line Reactive Power Reference signal. Attribute units
are expressed in percent for Converter Rated Output Power (Attr ID 724) per
second.
See also
Converter Output Attributes These are the converter output related attributes associated with Motion Control
Axis.
The Converter Output Current attribute is the output current generated by the
Bus Converter. A positive value indicates current flow out of the converter, where
the converter is supplying DC bus power to attached loads. A negative value
indicates current flow into the converter, where the converter is absorbing
“regenerative” power from attached loads.
The Converter Output Power attribute is the output power generated by the Bus
Converter. This value is based on the product of the Converter Output Current
and DC Bus Voltage. A positive value indicates power flow out of the converter,
where the converter is supplying DC bus power to attached loads. A negative value
indicates power flow into the converter, where the converter is absorbing
"regenerative" power from attached loads.
See also
Exceptions The various motion attributes can result in exceptions that can be configured to
present either a fault or alarm.
Standard Exceptions The following table lists the standard exception conditions associated with the
CIP Axis Exceptions, CIP Axis Faults, and CIP Axis Alarms attributes and their
extension attributes, Axis Exceptions 2, Axis Faults 2, and Axis Alarms 2. While
the CIP Axis Exceptions, CIP Axis Faults, and CIP Axis Alarms attributes and
their extensions are all required in the CIP Motion device implementation,
support for each individual exception condition is optional.
The Rule column in the following table indicates the Device Function Codes
where the associated exception is applicable.
• B = Converters
• D = Frequency, Position, Velocity, and Torque Control modes
• E = Feedback Only
• 0 = Ignore (All)
• 1 = Alarm (All)
• 2 = Fault Status Only (B, D)
• 3 = Stop Planner (D)
Standard exceptions
17 BD Converter Ground Current UL Ground Current has exceeded user-defined limit given by the
Converter Ground Current User Limit.
18 BD Converter Overtemperature FL Converter temperature has exceeded its factory set temperature
limit given by the Converter Overtemperature Factory Limit.
19 BD Converter Overtemperature UL Converter temperature has exceeded the user-defined
temperature limit given by the Converter Overtemperature User
Limit.
20 BD Converter Thermal Overload FL Converter thermal model or I2T overload value has exceeded its
factory set thermal capacity limit given by the Converter Thermal
Overload Factory Limit.
21 BD Converter Thermal Overload UL Converter thermal model or I2T overload value has exceeded its
user-defined thermal capacity given by the Converter Thermal
Overload User Limit.
27 BD Bus Regulator Overtemperature Bus Regulator temperature has exceeded its factory set
FL temperature limit given by the Bus Regulator Overtemperature
Factory Limit.
28 BD Bus Regulator Overtemperature Bus Regulator temperature has exceeded the user-defined
UL temperature limit given by the Bus Regulator Overtemperature
User Limit.
29 BD Bus Regulator Thermal Bus Regulator thermal model or I2T overload value has exceeded
Overload FL its factory set thermal capacity limit given by the Bus Regulator
Thermal Overload Factory Limit.
30 BD Bus Regulator Thermal Bus Regulator thermal model or I2T overload value has exceeded
Overload UL its user-defined thermal capacity given by the Bus Regulator
Thermal Overload User Limit.
31 BD Bus Regulator Failure The bus regulator (shunt) module in a multi-axis system has a
failed.
32 BD Bus Module Failure The bus module failed. Fault/Alarm Sub Code identifies the
specific type of bus module that failed.
33 BD Bus Undervoltage FL DC Bus voltage level is below the factory set limit given by the
Bus Undervoltage Factory Limit.
34 BD Bus Undervoltage UL DC Bus voltage level is below user-defined limit given by the Bus
Undervoltage User Limit.
35 BD Bus Overvoltage FL DC Bus voltage level is above the factory set limit given by the Bus
Overvoltage Factory Limit.
36 BD Bus Overvoltage UL DC Bus voltage level is above user-defined limit given by the Bus
Overvoltage User Limit.
37 BD Bus Power Loss DC Bus voltage level is below the Bus Power Loss Threshold for
more than the timeout period specified by the Bus Power Loss
Time value.
38 BD Bus Power Fuse Blown DC bus power loss due to blown fuse.
See also
Standard CIP Axis Fault and Based on the Exception Action configuration, Exception conditions can become
Faults or Alarms. The naming convention for Faults is to append a 'Fault' suffix to
Alarm Names
the Exception name. Similarly, the convention for Alarms is to append an 'Alarm'
suffix to the Exception name.
This table lists the resulting Fault names associated with the Standard Exception
conditions.
0 --Reserved--
1 Motor Overcurrent Alarm
2 Motor Commutation Alarm
3 Motor Overspeed FL Alarm
4 Motor Overspeed UL Alarm
5 Motor Overtemperature FL Alarm
6 Motor Overtemperature UL Alarm
7 Motor Thermal Overload FL Alarm
8 Motor Thermal Overload UL Alarm
9 Motor Phase Loss Alarm
10 Inverter Overcurrent Alarm
11 Inverter Overtemperature FL Alarm
12 Inverter Overtemperature UL Alarm
13 Inverter Thermal Overload FL Alarm
14 Inverter Thermal Overload UL Alarm
15 Converter Overcurrent Alarm
16 Converter Ground Current FL Alarm
17 Converter Ground Current UL Alarm
18 Converter Overtemperature FL Alarm
19 Converter Overtemperature UL Alarm
20 Converter Thermal Overload FL Alarm
21 Converter Thermal Overload UL Alarm
22 Converter AC Power Loss Alarm
23 Converter AC Single Phase Loss Alarm
24 Converter AC Phase Short Alarm
25 Converter Pre-Charge Alarm
26 --Reserved--
27 Bus Regulator Overtemperature FL Alarm
28 Bus Regulator Overtemperature UL Alarm
29 Bus Regulator Thermal Overload FL Alarm
30 Bus Regulator Thermal Overload UL Alarm
31 Bus Regulator Alarm
32 Bus Module Alarm
33 Bus Undervoltage FL Alarm
34 Bus Undervoltage UL Alarm
35 Bus Overvoltage FL Alarm
36 Bus Overvoltage UL Alarm
37 Bus Power Loss Alarm
38 Bus Power Blown Fuse Alarm
39 Bus Power Leakage Alarm
See also
Standard Exceptions on page 623
Rockwell Automation Specific Exceptions on page 634
Rockwell Automation Specific This table defines a list of Rockwell Automation specific exception conditions
associated with the CIP Axis Exceptions-RA, CIP Axis Faults-RA, and CIP Axis
Exceptions
Alarms-RA attributes and their extension attributes, Axis Exceptions 2 Mfg, Axis
Faults 2 Mfg, and Axis Alarms 2 Mfg attributes. While the CIP Axis Exceptions -
RA, CIP Axis Faults - RA, and CIP Axis Alarms - RA attributes and their
extensions are all Required in the CIP Motion device implementation, support for
each of the individual exception conditions therein is left Optional.
The Rule column in the following table indicates the Device Function Codes
where the associated exception is applicable.
• B = Converters
• D = Frequency, Position, Velocity, and Torque Control modes
• E = Feedback Only
• 0 = Ignore (All)
• 1 = Alarm (All)
• 2 = Fault Status Only (B, D)
• 3 = Stop Planner (D)
2 D Motor Voltage Mismatch The motor voltage is incompatible with the applied drive
voltage.
3 - -- Reserved --
4 E Feedback Filter Noise Excessive levels of noise have been detected by the digital
feedback filter.
5 E Feedback Battery Loss The battery charge level is too low and encoder power has
been removed possibly resulting in loss of absolute position.
6 E Feedback Battery Low The battery charge level is too low but encoder power has not
yet been removed. This is intended as a warning that if
encoder power is lost absolute feedback position could be lost.
7 E Feedback Incremental Count The periodic check of the incremental encoder position against
Error the absolute encoder position or Hall edges indicates they are
out of tolerance.
8 - -- Reserved --
11 --Reserved--
12 BD Converter Pre-Charge Overload Converter estimates that the pre-charge circuit has exceeded
FL its factory limit due to excessive power cycling.
13 --Reserved--
14 BD Excessive Current Feedback Current in one or more phases has been lost or remains below
Offset a preset level.
15 BD Regenerative Power Supply The hardware Regeneration OK input was deactivated while
Failure the drive was enabled.
16 D PWM Frequency Reduced Carrier Frequency foldback due to excessive Junction
Temperature.
17 D Current Limit Reduced Current Limit reduced due to excessive Junction Temperature
or due to Overload Protection.
See also
Rockwell Automation Specific Based on the Exception Action configuration, Exception conditions can become
Faults or Alarms. The naming convention for Faults is to append a Fault suffix to
CIP Axis Fault Names
the Exception name. Similarly, the convention for Alarms is to append an Alarm
suffix to the Exception name. This table lists the resulting Fault names associated
with the above exception conditions.
See also
Rockwell Automation The following table lists the resulting Alarm names associated with the Rockwell
Automation specific exception conditions.
Specific CIP Axis Alarm
Names Bit Object CIP Axis Alarm Name
See also
Category Usage
Module Configuration Block Attributes Used to configure elements of the Configuration Block sent in the CIP Motion
on page 639 Forward_Open.
Module Class Attributes on page 641 Used to configure Motion Device Axis Object class attributes associated with
the device.
Module Axis Attributes on page 642 Used to configure Motion Device Axis Object axis attributes that apply to a
common device component.
Module Feedback Port Attributes on page Used to configure the mapping of feedback ports to feedback channels for
656 each axis instance.
Module Timing Attributes on page 657 Used to configure various time related aspects of the CIP Motion device.
Module Support Attributes on page 659 Used to determine the size and content of the configuration data needed by
the CIP Motion device.
See also
Module Configuration The following collection of Module Class Attributes are stored in the controller
and sent to the module as part of the Configuration Block of the Forward_Open
Block Attributes service.
Configuration Bits
• 'Verify Power Structure' bit is used to control whether the drive performs an
"extended key" check against its Drive Class ID.
• 'Networked Safety Bit Valid' bit determines if the 'Allow Networked Safety'
bit (bit 2) of this attribute is valid and is enforced by the drive.
• 'Allow Networked Safety' bit determines if the drive is allowed to accept a
Propose_TUNID service request from a Safety Controller to establish
safety ownership and subsequent safety connections.
If power structure varies with the axis instances of a multi-axis drive device then a
value of 0 is applied to this attribute and the controller uses the Drive Power
Structure Axis ID to verify matching power structure associated with each axis.
See also
Module Class Attributes The following collection of Module Class Attributes are stored in the controller
and used to configure Motion Device Axis Object Class attributes associated with
the CIP Motion device. These attributes generally apply to the CIP Motion
connection behavior. If these Module Class attributes are included in the CIP
Motion Control Axis Object implementation, the attribute values are the same for
all axis instances associated with the module. In such an implementation, the
controller need only apply the Module Class attribute value for one of the axis
instances to configure the corresponding Motion Device Axis Object Class
attribute of the device.
Represents the high limit delay threshold for a Controller to Device (C-to-D)
Connection update. This delay is specified in units of Controller Update Periods.
Exceeding this limit results in a Control Connection Update Fault.
Represents the low limit delay threshold allowed for a Controller to Device
(C-to-D) Connection update. This delay is specified in units of Controller
Update Periods. Exceeding this limit results in a Control Connection Update
Alarm.
Sync Threshold
Determines the threshold for the Observed Variance of System Time below which
the Motion Device Axis Object is considered synchronized. The Group_Sync
service uses this as a criterion for a successful response.
See also
Module Axis Attributes on page 642
Module Configuration Attributes on page 639
Module Axis Attributes Module Axis attributes are used to configure common components of a CIP
Motion device, for example the Bus Converter, Bus Regulator, and so on, that
apply to all axis instances of the device. If these Module Class attributes are
included in the CIP Motion Control Axis Object implementation, the attribute
values are the same for all axis instances associated with the device. This is
generally enforced by configuration software.
If the value for a given Module Configuration attribute is not the same for each
axis instance of the device, the Module Configuration attribute value for instance
1 determines the configuration of the device component.
The element values of this array represent an ID assigned by the drive vendor that
identifies the power structure associated to a given axis instance. This allows
different power structures to be applied to specific axis instances of a multi-axis
drive. By contrast, if power structure hardware is the same for all axis instances of
the drive (excluding master feedback axes) the power structure can be identified by
simply using the Drive Power Structure Class ID attribute. For multi-axis drives,
the Drive Power Structure Axis ID can be included as part of the data segment in
the CIP Motion connection’s Forward Open service to confirm that the power
structure for a given axis instance matches the configuration in the controller. The
indexed elements of this array correspond to axis instances 1 thru 8. Individual
elements of this attribute are only applicable to axis instances whose associated
Inverter Support bit is set. Array elements that are not applicable are set to 0. Axis
instances with power structures that are not configured are set to 0, indicating to
the drive that the Drive Power Structure Axis ID for these axis instances do not
need to be checked.
PWM Frequency
This 8-element array sets the carrier frequency for the Pulse Width Modulation
output to the motor. Drive derating is required at higher PWM frequencies due to
switching losses. Current loop update time is tied directly to the PWM frequency
so loop performance generally increases with increasing PWM rate. Note that each
drive instance in a multi-axis drive module can have an independently configured
PWM frequency. The indexed elements of this array correspond to axis instances
1 thru 8. Individual elements of this attribute are only applicable to axis instances
whose associated Inverter Support bit is set. Array elements that are not applicable
or not configured are set to 0.
Bus Configuration
instances and with other drives. This may result in de-rating of the
converter's continuous current rating when there are multiple Shared
AC/DC converter devices paralleled in a bus sharing group. Shared
AC/DC axes generally participate in a bus sharing group.
• Shared DC specifies that this drive axis instance is sharing DC bus power
generated by another Shared AC/DC or Shared DC/DC CIP Motion
drive, or external CIP Motion Converter. Shared DC axes generally
participate in a bus sharing group.
• Shared DC - Non CIP Converter specifies that this drive axis instance is
receiving DC bus power generated by an external AC/DC converter that is
not CIP Motion compliant and distributing its DC bus power to other CIP
Motion drives. A drive configured for "Shared DC - Non CIP Converter" is
responsible for communicating the state of the external converter to the
control system as if the external converter were integrated with the drive.
Specifically, this communication includes the Bus Up and DC Bus Unload
status bits reflecting the current state of associated external converter.
Shared DC - Non CIP Converter axes generally participate in a bus sharing
group.
• Shared DC/DC specifies that the converter associated with this CIP
Motion device supplies and shares DC bus power with other Shared DC
devices. DC/DC converters may convert input DC bus power from a
Shared AC/DC converter to a different DC Bus output voltage level to
supply one or more Shared DC drives. It may also simply distribute DC bus
power from a Shared AC/DC converter to multiple Shared DC drives
without any conversion. A Shared DC/DC converter has a unique
capability in that it can be both a bus master for a bus group and a bus slave
in a different bus group. Shared DC/DC axes generally participate in a bus
sharing group.
This value indicates the expected bus voltage level of the drive application. High
bus voltage selection is usually associated with drive running on the North
American power grid, when operating in Europe a Low Bus Voltage selection
would be appropriate. This parameter can be used to compensate for these
different bus voltage levels in the current loop.
This 8-element array controls the method of operation of the DC Bus Regulator
that addresses the regenerative over-voltage conditions that can occur when
decelerating a motor associated with a given axis instance.
Note that each drive instance in a multi-axis drive module can have an
independently configured Bus Regulator Action. The indexed elements of this
array correspond to axis instances 1 thru 8. Array elements that are not applicable
or not configured are set to 0.
This 8-element array limits the amount of power allowed to transfer between the
motor and the DC Bus during regenerative braking of the motor load for a given
axis instance. Since this is regenerative power, the value of the limit is negative.
Note that each drive instance in a multi-axis drive module can have an
independently configured Regenerative Power Limit. The indexed elements of this
array correspond to axis instances 1 thru 8. Individual elements of this attribute
are only applicable to axis instances whose associated Inverter Support bit is set.
Array elements that are not applicable or not configured are set to 0.
This attribute is used when an external shunt resistor has been configured. This
attribute value specifies the power that can be delivered to the external shunt
resistor for one second, without exceeding the rated element temperature.
Another method is that the thermal time constant = 'Shunt Pulse Power'
(Kilowatts) / 'Shunt Power' (Kilowatts) sometimes referred to as thermal mass.-
the time for the resistor element to reach 63% of rated temperature with applied
rated Kilowatts.
A third method for determining this value: The pulse Kilowatts for 1 second is
twice the watt rating of a 2 second pulse. In other words, the watt*sec rating is a
constant if the pulse duration is short compared to the thermal time constant of
the resistor ad is a function of the element mass.
This attribute represents the external DC Bus capacitance when the associated
converter or drive is acting as a Common Bus Leader Master, supplying DC Bus
power to one or more Common Bus Followers. This attribute may also be
applicable to standalone drives that allow connection to an external capacitor.
This attribute is not applicable when the Bus Regulator Action is set to Common
Bus Follower. The attribute is applicable when the Bus Regulator Action is set to
Disable or Shunt Regulator.
This attribute represents the resistance of the External Shunt Regulator resistor.
This enumerated selection indicates the Bus Sharing Group the drive is assigned
to. Physically, a Bus Sharing Group represents a collection of drives that are wired
together in a Shared AC/DC or Shared DC Bus Configuration. Assignment to a
Bus Sharing Group limits the DC Bus Unload action initiated by a converter in
the group, and the resultant Bus Power Sharing exceptions, to Shared AC/DC
and Shared DC drives in the converter's assigned Bus Group. Drives assigned to
other Bus Groups are, therefore, unimpacted.
If the drive's Bus Configuration indicates Standalone operation, the only valid
enumeration for the Bus Sharing Group is Standalone.
If the drive supports the optional Bus Configuration attribute, the Bus Sharing
Group is required in the drive profile implementation.
Duty Select
This 8-element array indicates the duty level of the drive application and balances
the continuous and intermittent overload capacity of the drive and motor
accordingly. Since this value is tied to a specific drive inverter and motor, the
setting can vary for each axis instance supported by a multi-axis drive module. The
indexed elements of this array correspond to axis instances 1 thru 8. Array
elements that are not applicable or configured are set to 0.
Specification for the continuous and overload ratings under Normal, Heavy, and
Light Duty are left to the discretion of the drive vendor.
Duty Select is used to determine the level of thermal protection for the motor and
the inverter during drive operation.
This value configures the drive for the intended AC line voltage applied to the
converter.
This attribute sets the user limit for the Converter Overtemperature UL
exception.
This attribute sets the user limit for the Converter Thermal Overload UL
exception.
This attribute sets the user limit for the Converter Ground Current UL
exception.
This attribute sets the user limit for the Bus Regulator Overtemperature UL
exception.
This attribute sets the user limit for the Bus Regulator Thermal UL exception.
This attribute sets the user limit for the Bus Overvoltage UL exception. Unlike the
corresponding Factory Limit, which is specified in Volts, the User Limit is based
on the percentage of Nominal Bus Voltage during operation.
This attribute sets the user limit for the Bus Undervoltage UL exception. Unlike
the corresponding Factory Limit, which is specified in Volts, the User Limit is
based on the percentage of Nominal Bus Voltage during operation
This attribute sets the user limit for the Control Module Overtemperature UL
exception.
This attribute sets the user limit for the Converter Pre-Charge Overload UL
exception.
Functions that are not mapped to a digital input are not checked by the drive, and
do not generate associated exceptions or events. Associated exception actions in
this case are accepted by the device and ignored.
This attribute sets the reference voltage used to actively regulate the DC Bus
Output Voltage output of Bus Converter power structure instance n when in the
Running state.
Power structure instance attributes are only applicable when supporting multiple
converter power structure generated DC Bus outputs per axis object instance
This attribute sets the User Limit for the Bus Overvoltage UL exception
associated with the DC Bus output of DC converter power structure instance n
when supporting multiple converter power structure generated DC Bus outputs
per axis object instance. Unlike the corresponding Factory Limit, which is
specified in Volts, the User Limit is based on percent of the corresponding DC
Bus Voltage Set Point n during operation.
This attribute sets the User Limit for the Bus Undervoltage UL exception
associated with the DC Bus output of DC converter power structure instance n
when supporting multiple converter power structure generated DC Bus outputs
per axis object instance. Unlike the corresponding Factory Limit, which is
specified in Volts, the User Limit is based on percent of the corresponding Bus
Voltage Set Point n during operation.
See also
Module Feedback Port Module Axis attributes are used to configure the feedback ports of the device
module. Each device module may be equipped with multiple feedback ports that
Attributes can be freely mapped to the various feedback channels of a CIP Motion axis
instance.
See also
Module Timing Attributes The following attributes configure various time related aspects of CIP Motion
device.
Controller firmware only enumerated parameter (does not go to the drive) which
reflects the time synchronization capability of the device.
• No Sync: This enumeration indicates that the device does not support CIP
Sync time synchronization and therefore cannot interpret or generate time
stamps.
• Low Quality: This enumeration indicates that the device has a low quality
implementation of CIP Sync time synchronization protocol. Latency
associated with the software time sync algorithm limits time stamp accuracy
Time Diagnostics
Controller firmware only parameter (does not go to the drive) which controls
whether timing diagnostic data is requested from the drive.
See also
Module Support Attributes The following AOP Module C-tag parameters are used by configuration software
to determine the size of various array data needed to configure the CIP Motion
device and whether attributes associated with the converter function will be sent
to the CIP Motion device. These parameters are not attributes of any object and
are not sent to the CIP Motion device.
Inverter Support
Firmware only parameter (does not go to the device) that controls how much of
the Digital Input Configuration array is sent to the device for a given axis instance.
The number of configurable inputs can vary for each axis instance supported by a
multi-axis drive module. The indexed elements of this array correspond to axis
instances 1 thru 8. Array elements that are not applicable or configured are set to
0.
Firmware only parameter (does not go to the device) that specifies the axis
instance that sources the configurable digital inputs for a given axis of the device.
While axis instances generally provide their own set of configurable inputs, in
some cases axis instances, like feedback only axis instances, utilize the digital inputs
from another axis instance. The Source of Configurable Inputs element can be
used to identify another axis instance as the source for its digital inputs. The
indexed elements of this array correspond to axis instances 1 thru 8. Array
elements that are not applicable or configured are set to 0.
See also
D
device function codes 97
Drive supported optional attributes 123
E
Event Capture Behavior 44
exceptions 623
F
Fault and Alarm Behavior 47
I
identify motion axis attributes based on device function codes 102
Integrated Motion Axis Control Modes and Methods 20
Documentation feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
How Are We Doing? form at http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf
Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.
Allen-Bradley, Rockwell Automation, and Rockwell Software are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.