Chapter 7 Troubleshooting

When the drive enters a fault or

inhibit scenario, the fault INIT FLT M12 INVALID FPGA REV
information will be shown and
scrolled across the LCD display. Fault type
Fault description
Fault code

Fault Codes
The fault code tables are designed to help you determine the source of the fault or
exception. When a fault condition is detected, the drive performs the appropriate
fault action, the fault is displayed, and the fault is added to a persistent fault log
(along with diagnostics data). The earlier faults have priority to be displayed.

The drive removes the fault text from the display when a Fault Reset service is
sent from the controller and the fault is no longer active. If a fault is still active
following a Fault Reset service, the fault is again posted to the display and written
to the fault log.
Fault Code Summary
Fault Code Type Description
FLT Sxx Standard runtime axis exceptions.
FLT Mxx
INIT FLT Sxx Exceptions that prevent normal operation and occur during the initialization process.
INIT FLT Mxx
INHIBIT Sxx Exceptions that prevent normal operation and indicate whenever the drive is active.
INHIBIT Mxx
NODE FLTxx Exceptions that prevent normal operation of the drive.
NODE ALARM xx Exceptions that prevent normal operation of the drive, but do not result in any action other
than reporting the alarm to the controller.

See Troubleshoot the Safe Torque-Off Function on page 96 for information on

troubleshooting SAFE FLT fault codes.

TIP Fault codes triggered by conditions that fall outside factory set limits are
identified by FL at the end of the display message. For example, FLT S07 – MTR
OVERLOAD FL.
Fault codes triggered by conditions that fall outside user set limits are
identified by UL at the end of the display message. For example, FLT S08 – MTR
OVERLOAD UL.

FLT Sxx Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
FLT S03 – MTR OVERSPEED FL Motor Overspeed Factory Limit Fault Motor speed has exceeded 590 Hz. Check control loop tuning.
FLT S04 – MTR OVERSPEED UL Motor Overspeed User Limit Fault Motor speed has exceeded the user defined Check control loop tuning.
speed limit given by Motor Overspeed User
Limit.
FLT S07 – MTR OVERLOAD FL Motor Thermal Overload Factory Limit Fault The motor thermal model has exceeded its Modify the command profile to reduce speed
factory set thermal capacity limit of 110%. or increase time.
FLT S08 – MTR OVERLOAD UL Motor Thermal Overload User Limit Fault The motor thermal model has exceeded the • Modify the command profile.
thermal capacity limit given by Motor • Increase the Motor Thermal Overload UL
Thermal Overload User Limit. attribute value.

120 Rockwell Automation Publication 520-UM002A-EN-E - May 2015

 Troubleshooting Chapter 7

FLT Sxx Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
FLT S10 – INV OVERCURRENT Inverter Overcurrent Fault Inverter current has exceeded the • Check motor power cable for shorts.
instantaneous current limit (determined by • Verify motor windings are not shorted.
hardware). • Verify motor power wire gauge.
• Operate within the continuous power
rating.
• Reduce acceleration times.
FLT S11 – INV OVERTEMP FL Inverter Overtemperature Factory Limit The measured inverter temperature has • Modify the command profile to reduce
Fault exceeded the factory set temperature limit. speed or increase time.
• Reduce drive ambient temperature.
• Verify airflow through drive is not
obstructed.
FLT S13 – INV OVERLOAD FL Inverter Thermal Overload Factory Limit The thermal model for the power transistors Modify the command profile to reduce speed
Fault indicates that the temperature has exceeded or increase time.
the factory set thermal capacity rating of
110%.
FLT S16 – GROUND CURRENT Ground Current Factory Limit Fault The sensing circuitry in the power stage has • Check motor power wiring; check power
detected excessive ground current. cable for shorts.
• Replace motor if the fault persists.
FLT S23 – AC PHASE LOSS AC Single Phase Loss Fault A single AC input phase was lost while the Check AC input voltage on all phases.
drive was enabled.
FLT S25 – PRECHARGE FAILURE Pre-charge Failure Fault The pre-charge circuit monitoring algorithm • Check AC input voltage on all phases.
detected that the DC bus did not reach a • Check input power wiring.
factory set voltage level after charging for a • Replace drive if fault persists.
period of time.
FLT S29 – BUS OVERLOAD FL Bus Regulator Thermal Overload Factory The shunt thermal model has exceeded its • Modify the duty cycle of the application.
Limit Fault factory set thermal capacity limit. • Add external shunt for additional
capacity.
• Add capacitor module if needed.
FLT S34 – BUS UNDERVOLT UL Bus Undervoltage User Limit Fault DC Bus voltage level is below the user set • Verify voltage level of the incoming AC.
limit as given by Bus Undervoltage User • Monitor AC power source for glitches or
Limit. line droop.
• Install UPS on AC input.
• Decrease Bus Undervoltage UL attribute
value.
FLT S35 – BUS OVERVOLT FL Bus Overvoltage Factory Limit Fault DC Bus voltage level is above the factory set • Change the deceleration or motion
limit as determined by the configured input profile of all drives connected to the DC
voltage. bus.
• Unplug the shunt connector and measure
the resistance of the shunt.
• Replace drive if shunt resistor is open.
FLT S37 – BUS POWER LOSS Bus Power Loss DC Bus voltage level is below the Bus Power • Verify voltage level of the incoming AC.
Loss Threshold for more than the timeout • Monitor AC power source for glitches or
period specified Bus Power Loss Time value. line droop.
• Install UPS on AC input.
FLT S41 – FDBK SIGNAL NOISE FL Feedback Signal Noise Fault Noise induced A/B channel state changes • Check motor feedback cable and
(illegal states) from a feedback device were connector.
detected by the drive. Specifically, the • Cycle power.
number of these noise events that have • Check feedback shield connection.
occurred on this channel has exceeded the • Reduce shock and vibration to motor.
Feedback Noise Factory Limit. The offending • Replace motor if fault continues.
feedback channel number is encoded in the
associated Fault/Alarm Sub Code.
FLT S45 – FDBK COMM FL Motor Feedback Data Loss Factory Limit The number of consecutive missed or • Check motor feedback cable and
Fault corrupted serial data packets from the connector.
intelligent feedback device has exceeded a • Check motor power cable and feedback
factory set limit. wire shields are secured correctly.
• Check motor frame is grounded correctly.
FLT S50 – HARDWARE OVERTRAVEL POSITIVE Hardware Overtravel Positive Axis moved beyond the physical travel limits • Check wiring.
in the positive direction and activated the • Verify motion profile.
Negative Overtravel limit switch. • Verify axis configuration in software.
FLT S51 – HARDWARE OVERTRAVEL Hardware Overtravel Negative Axis moved beyond the physical travel limits • Check wiring.
NEGATIVE in the negative direction and activated the • Verify motion profile.
Negative Overtravel limit switch. • Verify axis configuration in software.

Rockwell Automation Publication 520-UM002A-EN-E - May 2015 121

Chapter 7 Troubleshooting

FLT Sxx Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
FLT S54 – POSN ERROR Excessive Position Error Fault The position error of the position control • Check position loop tuning.
loop has exceeded the value given by • Increase the feedforward gain.
Position Error Tolerance for a time period • Verify sizing of the drive and motor.
given by Position Error Tolerance Time. • Check motor power wiring.
• Increase Position Error Tolerance and/or
Position Error Tolerance Time attribute
values.
FLT S55 – VEL ERROR Excessive Velocity Error Fault The velocity error of the velocity control loop • Check velocity loop tuning.
has exceeded the value given by Velocity • Reduce acceleration.
Error Tolerance for a time period given by • Verify sizing of the drive and motor.
Velocity Error Tolerance Time. • Check motor power wiring.
• Increase Velocity Error Tolerance and/or
Velocity Error Tolerance Time attribute
values.
FLT S56 – OVERTORQUE LIMIT Overtorque Limit Fault Motor torque has risen above user defined • Verify Torque Trim value.
maximum torque level given by Overtorque • Verify motion profile.
Limit for a time period given by Overtorque • Verify sizing of the drive and motor.
Limit Time. • Increase Overtorque Limit and/or
Overtorque Limit Time attribute values.
FLT S57 – UNDERTORQUE LIMIT Undertorque Limit Fault Motor torque has dropped below user • Verify motion profile.
defined minimum torque level given by • Verify sizing of the drive and motor.
Undertorque Limit for a time period given by • Decrease Undertorque Limit and/or
Undertorque Limit Time. Undertorque Limit Time attribute values.
FLT S61 – ENABLE INPUT DEACTIVATED Enable Input Deactivated Enable Input has been deactivated while the • Verify Enable Input level.
axis power structure is in Running state, • Check Enable Input wiring.
enabled, and supplying current to the DC
Bus or motor.

FLT Mxx Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
FLT M10 – CONTROL MODULE Control Module Overtemperature Fault The temperature sensor on the Main Control • Reduce drive ambient temperature.
OVERTEMPERATURE FL Board detected excessive heat. • Verify airflow through drive is not
obstructed.
• Check control module internal fan.
Replace if error persists.
FLT M19 – DECEL OVERRIDE Decel Override The drive is not following a commanded • Reprogram Bus Regulator Action to
deceleration because it is attempting to limit eliminate any “Adjustable Freq”
bus voltage. selection.
• Reprogram Bus Regulator Action to
Shunt Regulator and add external shunt.
• Correct AC input line instability or add an
isolation transformer.
• Reset drive.
FLT M21 – MOTOR TEST FAILURE Motor Test Failure The Motor Test procedure has failed. • Verify sizing of the drive and motor.
• Verify motor data.
• Check motor power wiring.
FLT M26 – RUNTIME ERROR Runtime Error The drive firmware encountered an • Cycle power.
unrecoverable runtime error. • Reset the drive.
• Return drive for repair if fault continues.
FLT M28 – SAFETY MODULE COM ERROR Safety Module Communication Error Error in communicating to the Safety • Cycle power.
module. • Replace module.

122 Rockwell Automation Publication 520-UM002A-EN-E - May 2015

 Troubleshooting Chapter 7

INIT FLT Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
INIT FLT S03 – NVMEM CHKSUM Nonvolatile memory checksum error Data in the nonvolatile memory has a • Cycle power.
checksum error. • Reset the drive.
• Return drive for repair if fault continues.
INIT FLT M14 – INVALID SAFETY FIRMWARE Invalid Safety Firmware The safety firmware is not compatible with • Cycle power.
the drive firmware, or the main safety • Upgrade drive firmware.
firmware is missing. • Return drive for repair if fault continues.
INIT FLT M15 – POWER BOARD Power Board Checksum Error The power board has a checksum error. • Cycle power.
• Reset the drive.
• Return drive for repair if fault continues.

INHIBIT Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
INHIBIT S01 – AXIS ENABLE INPUT Axis Enable Input Axis Enable Input is not active. • Verify Enable Input level.
• Check Enable Input wiring.
INHIBIT S02 – MOTOR NOT CONFIGURED Motor Not Configured The motor has not been properly configured Verify motor configuration in the Logix
for use. Designer application.
INHIBIT M05 – SAFE TORQUE OFF Start Inhibit – Safe Torque Off The safety function has disabled the power • Check safety input wiring.
structure. • Check state of safety devices.

NODE FLT Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
NODE FLT 01 – LATE CTRL UPDATE Control Connection Update Fault Several consecutive updates from the • Remove unnecessary network devices
controller have been lost. from the motion network.
• Change network topology so that fewer
devices share common paths.
• Use high performance network
equipment.
• Use shielded cables.
• Separate signal wiring from power
wiring.
NODE FLT 02 – PROC WATCHDOG nn Processor Watchdog Fault The processor on the power board or control • Cycle power.
board failed to update in a certain amount of • Update the drive firmware.
time. • Return drive for repair if fault continues.
The nn sub-codes 00…05 are internal and
result in the same possible solution.
NODE FLT 03 – HARDWARE 00 Hardware Fault -PwrIF Communication with the power board could • Cycle power.
not be established. • Update the drive firmware.
• Return drive for repair if fault continues.
NODE FLT 03 – HARDWARE 01 Hardware Fault - Piccolo HW DSP chip on the power board failure. • Cycle power.
• Return motor for repair if fault continues.
NODE FLT 03 – HARDWARE 02 Hardware Fault - DSL Communication with the encoder could not • DSL feedback wiring is incorrect (check
be established. against wiring diagram).
• DSL feedback wiring is shorted or open.
• DSL feedback cable is defective.
• Bulletin VPL motor feedback device is
defective.
• Cycle power.
• Return drive for repair if fault continues.
NODE FLT 03 – HARDWARE 03 DSL External Memory Interface Fault Errors were detected by the DSL external • Check DSL feedback device, wiring, and
memory interface. cable.
• Cycle power.
• Return drive for repair if fault continues.
NODE FLT 05 – CLOCK SKEW FLT Clock Skew Fault The controller time and the drive's system • Cycle power.
time are not the same. • Check controller and Ethernet switch
operation.

Rockwell Automation Publication 520-UM002A-EN-E - May 2015 123

Chapter 7 Troubleshooting

NODE FLT Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
NODE FLT 06 – LOST CTRL CONN Lost Controller Connection Fault Communication with the controller has been • Check Ethernet connection.
lost. • Check controller and Ethernet switch
operation.
NODE FLT 07 – CLOCK SYNC Clock Sync Fault Drive's local clock has lost synchronization • Check Ethernet connection.
with controller's clock and was not able to • Check controller and Ethernet switch
resynchronize within allotted time. operation.
NODE FLT 09 – DUPLICATE IP ADDRESS Duplicate IP Address Fault Several consecutive updates from the Select an IP address not already in use on
controller have been lost. the network.

NODE ALARM Fault Codes

Exception Code on Display Exception Text Problem Possible Solutions
NODE ALARM 01 – LATE CTRL UPDATE Control Connection Update Alarm Updates from the controller have been late. • Remove unnecessary network devices
from the motion network.
• Change network topology so that fewer
devices share common paths.
• Use high performance network
equipment.
• Use shielded cables.
• Separate signal wiring from power
wiring.
NODE ALARM 03 – CLOCK JITTER Clock Jitter Alarm The sync variance has exceeded the sync • Check the Ethernet connection.
threshold while the device is running in sync • Check controller and Ethernet switch
mode. operation.
NODE ALARM 04 – CLOCK SKEW ALARM Clock Skew Alarm The controller time and the drive's system • Check the Ethernet connection.
time are not the same. • Check controller and Ethernet switch
operation.
NODE ALARM 05 – CLOCK SYNC ALARM Clock Sync Alarm Drive's local clock has lost synchronization • Check the Ethernet connection.
with controller's clock for a short time • Check controller and Ethernet switch
during synchronous operation. operation.

PowerFlex 527 Drive Status Indicators

The fault status indicator is located between the LCD display and keypad. There
are also four status indicators located at the bottom right of the drive and can be
seen through the front cover of the control module.

Fault status

Module status
Network status
Link A status (Ethernet port 1)
Link B status (Ethernet port 2)

124 Rockwell Automation Publication 520-UM002A-EN-E - May 2015

 Troubleshooting Chapter 7

Fault Status Indicator

Condition Safety Supervisor State CIP Motion Axis State Governing Object Identity State
Steady Red Any State(1) Aborting Motion Axis Major Recoverable or
Major Unrecoverable
Steady Red Any State(1) Major Faulted Motion Axis Major Recoverable or
Major Unrecoverable
Steady Red Abort Any State(1) Safety Supervisor Major Recoverable
Steady Red Critical Fault Any State(1) Safety Supervisor Major Unrecoverable
(1) “Any State” means any state that has lower precedence.

Module Status Indicator

Condition Safety Supervisor State CIP Motion Axis State Governing Object Identity State
Flashing Green/Red Self-Testing Any State(1) Safety Supervisor Device Self-Testing
Flashing Green/Red Any State(1) Self-Testing Motion Axis Device Self-Testing
Steady Red Self-Test Exception Any State(1) Safety Supervisor Major Unrecoverable
Flashing Green/Red Waiting for TUNID(2) Any State(1) Safety Supervisor Standby
Flashing Green/Red Configuring Any State(1) Safety Supervisor Standby
Flashing Green Idle Any State(1) Safety Supervisor Standby
Flashing Green • Waiting for TUNID with Torque • Initializing Motion Axis Standby
Permitted(2)(3) • Pre-Charge
• Executing • Shutdown
• Executing with Torque • Start Inhibit
Steady Green Permitted(4) • Stopped Motion Axis Operational
• Stopping
• Starting
• Running
• Testing
Flashing Red or Steady Red Any State(1) Aborting Motion Axis Major Recoverable or
Major Unrecoverable
Flashing Red Any State(1) Major Faulted Motion Axis Major Recoverable or
Major Unrecoverable
Flashing Red Abort Any State(1) Safety Supervisor Major Recoverable
Steady Red Critical Fault Any State(1) Safety Supervisor Major Unrecoverable
(1) “Any State” means any state that has lower precedence.
(2) After Propose_TUNID service request, the Network Status indicator flashes Green/Red (fast flash) until successful Apply_TUNID.
(3) Unlike many Safety I/O devices, a CIP Motion Safety Drive is free to operate in its “Out of Box” state. This behavior is made explicit by the device specific Safety Supervisor state, Waiting for TUNID with
Torque Permitted. In this “Out of Box” state, operation of the CIP Motion Safety Drive is the same as that of a CIP Motion Drive to facilitate commissioning.
(4) Unlike many Safety I/O devices, a CIP Motion Safety Drive may be operated when the Safety Output assemblies Run/Idle bit is set to Idle. If in the Executing state, the Run/Idle bit is set to Idle, the device
is forced to a Safe State. However, if in this condition, the Safety Controller sends a Mode_Change service request with Torque Permitted to the Safety Stop Functions object, drive operation is permitted
while the Run/Idle bit remains Idle. See the Safety Stop Function object for details on the Mode_Change service.

Network Status Indicator

Condition Status
Off No power applied to the drive or IP address is not configured.
Flashing Green Drive connection is not established, but has obtained an IP address.
Steady Green Drive is online and has connections in the established state.
Flashing Red One or more Exclusive Owner connections has timed out.
Steady Red Duplicate IP address. IP address specified is already in use.
Flashing Green/Red (slow flash) The drive performs self-test during powerup.
Flashing Green/Red (fast flash) Safety Supervisor is waiting for “Apply TUNID” service request.

Rockwell Automation Publication 520-UM002A-EN-E - May 2015 125

Chapter 7 Troubleshooting

Link A Status Indicator (Ethernet Port 1)

Condition Status
Off Drive is not connected to the network.
Steady Green Drive is connected to the network but not transmitting data.
Flashing Green Drive is connected to the network and transmitting data.

Link A Status Indicator (Ethernet Port 2)

Condition Status
Off Drive is not connected to the network.
Steady Green Drive is connected to the network but not transmitting data.
Flashing Green Drive is connected to the network and transmitting data.

General Troubleshooting These conditions do not always result in a fault code, but can require
troubleshooting to improve performance.
General Troubleshooting
Condition Potential Cause Possible Resolution
Axis or system is unstable. The position feedback device is incorrect or open. Check wiring.
Motor tuning limits are set too high. Run Tune in the Logix Designer application.
Position loop gain or position controller accel/decel rate is improperly set. Run Tune in the Logix Designer application.
Improper grounding or shielding techniques are causing noise to be Check wiring and ground.
transmitted into the position feedback or velocity command lines, causing
erratic axis movement.
Motor Data is incorrectly set (induction motor is not matched to axis module). • Check setups.
• Run Motor Test in the Logix Designer application.
Mechanical resonance. Notch filter or output filter can be required (refer to Axis
Properties dialog box, Output tab in the Logix Designer
application).
You cannot obtain the motor Torque Limit limits are set too low. Verify that torque limits are set properly.
acceleration/deceleration that you Incorrect motor selected in configuration. Select the correct motor and run Tune in the Logix Designer
want.
application again.
The system inertia is excessive. • Check motor size versus application need.
• Review induction system sizing.
The system friction torque is excessive. Check motor size versus application need.
Available current is insufficient to supply the correct accel/decel rate. • Check motor size versus application need.
• Review induction system sizing.
Acceleration limit is incorrect. Verify limit settings and correct them, as necessary.
Velocity Limit limits are incorrect. Verify limit settings and correct them, as necessary.
Motor does not respond to a The motor wiring is open. Check the wiring.
command. The motor cable shield connection is improper. • Check feedback connections.
• Check cable shield connections.
The motor has malfunctioned. Repair or replace the motor.
The coupling between motor and machine has broken (for example, the Check and correct the mechanics.
motor moves, but the load/machine does not).
Primary operation mode is set incorrectly. Check and properly set the limit.
Velocity or torque limits are set incorrectly. Check and properly set the limits.
Brake connector not wired Check brake wiring

126 Rockwell Automation Publication 520-UM002A-EN-E - May 2015

 Troubleshooting Chapter 7

General Troubleshooting
Condition Potential Cause Possible Resolution
Presence of noise on command or Recommended grounding per installation instructions have not been • Verify grounding.
motor feedback signal wires. followed. • Route wire away from noise sources.
• See System Design for the Control of Electrical Noise,
publication GMC-RM001.
Line frequency can be present. • Verify grounding.
• Route wire away from noise sources.
Variable frequency can be velocity feedback ripple or a disturbance caused by • Decouple the motor for verification.
gear teeth or ballscrew, and so forth. The frequency can be a multiple of the • Check and improve mechanical performance, for example,
motor power transmission components or ballscrew speeds resulting in the gearbox or ballscrew mechanism.
velocity disturbance.
No rotation The motor connections are loose or open. Check motor wiring and connections.
Foreign matter is lodged in the motor. Remove foreign matter.
The motor load is excessive. Verify the induction system sizing.
The bearings are worn. Return the motor for repair.
The motor brake is engaged (if supplied). • Check brake wiring and function.
• Return the motor for repair.
The motor is not connect to the load. Check coupling.
Motor overheating The duty cycle is excessive. Change the command profile to reduce accel/decel or increase
time.
The rotor is partially demagnetized causing excessive motor current. Return the motor for repair.
Abnormal noise Motor tuning limits are set too high. Run Tune in the Logix Designer application.
Loose parts are present in the motor. • Remove the loose parts.
• Return motor for repair.
• Replace motor.
Through bolts or coupling is loose. Tighten bolts.
The bearings are worn. Return motor for repair.
Mechanical resonance. Notch filter can be required (See Axis Properties dialog box,
Output tab in the Logix Designer application).
Erratic operation - Motor locks into Motor power phases U and V, U and W, or V and W reversed. Check and correct motor power wiring.
position, runs without control or with
reduced torque.

Logix5000 Controller and By using the Logix Designer application, you can configure how the
PowerFlex 527 drives respond when a drive fault/exception occurs.
Drive Behavior
TIP The INIT FLT xxx faults are always generated after powerup, but before the
drive is enabled, so the stopping behavior does not apply.
NODE ALARM xxx faults do not apply because they do not trigger stopping
behavior.

The drive supports fault action for Ignore, Alarm, Minor Fault, and Major Fault
as defined in PowerFlex 527 Drive Exception Action Definitions on page 128.
See the drive behavior tables beginning on page 129 for information on how the
fault and stopping actions apply to each of the exception fault codes.

The drive supports these configurable stopping actions:

• Disable and Coast
• Current Decel and Disable
• Ramped Decel and Disable

Rockwell Automation Publication 520-UM002A-EN-E - May 2015 127

Chapter 7 Troubleshooting

PowerFlex 527 Drive Exception Behavior

For PowerFlex 527 drives, you can configure exception behavior in the
Logix Designer application from the Axis Properties dialog box, Actions
category.
PowerFlex 527 Drive Exception Action Definitions
Exception Action Definition
Ignore The controller completely ignores the exception condition. For some exceptions that are
fundamental to the operation of the planner, Ignore is not an available option.
Alarm The controller sets the associated bit in the Motion Alarm Status word, but does not
otherwise affect axis behavior. Like Ignore, if the exception is so fundamental to the
drive, Alarm is not an available option. When an exception action is set to Alarm, the
Alarm goes away by itself when the exceptional condition has cleared.
Fault Status Only – Minor Fault Like Alarm, Fault Status Only instructs the controller to set the associated bit in the
Motion Fault Status word, but does not otherwise affect axis behavior. However, unlike
Alarm an explicit Fault Reset is required to clear the fault once the exceptional condition
has cleared.
Like Ignore and Alarm, if the exception is so fundamental to the drive, Fault Status Only
is not an available option.
Stop Planner – Minor Fault The controller sets the associated bit in the Motion Fault Status word and instructs the
Motion Planner to perform a controlled stop of all planned motion at the configured
maximum deceleration rate and holds at zero speed. An explicit Fault Reset is required
to clear the fault once the exceptional condition has cleared. If the exception is so
fundamental to the drive, Stop Planner is not an available option.
Stop Drive – Major Fault When the exception occurs, the associated bit in the Fault Status word is set and the
axis comes to a stop by using the stopping action defined by the drive for the particular
exception that occurred. There is no controller based configuration to specify what the
stopping action is, the stopping action is device dependent.
Shutdown – Major Fault When the exception occurs, the drive brings the motor to a stop by using the stopping
action defined by the drive (as in Stop Drive) and the power module is disabled. An
explicit Shutdown Reset is required to restore the drive to operation.

Only selected drive exceptions are configurable. In the fault behavior tables, the
controlling attribute is given for programmable fault actions.

128 Rockwell Automation Publication 520-UM002A-EN-E - May 2015