When a Kinetix 5300 servo axis stops, the same event usually shows in three places: the four-character display on the drive, the MOD/NET status indicators, and the axis in Logix Designer. This article explains how to read each one, what the common codes mean and what to check before clearing the fault, based on Rockwell Automation user manual 2198-UM005E (September 2024).
Where the fault shows
The four-character display on the drive
In normal operation the display scrolls the CIP state and the IP address. When a fault occurs it shows the active fault code (2198-UM005E, chapter 6, p. 96). During startup it shows state numbers, and the number the drive stops at tells you which step it is stuck on (p. 100 and p. 136):
| Display | Drive is at this step |
|---|---|
| 8888 | Self-test |
| 00 | Waiting for a connection from the controller |
| 01 | Receiving its configuration |
| 02 | Waiting for group synchronization |
| 03 | Waiting for the DC bus to charge |
| 04 | Operational |
The leading letters tell you the fault group (Table 65, p. 136): F is a runtime axis fault, I is a fault during initialization, nF is a module-level fault that affects every axis, nA and A are alarms that are only reported to the controller, S is a condition that stops the drive from being enabled, and SF is a fault detected in the safety function. An added c (for example Fc05) marks a manufacturer-specific code.
MOD and NET indicators
| Indicator | State | Meaning |
|---|---|---|
| MOD | Flashing red | Recoverable major fault, for example an incorrect or inconsistent configuration |
| MOD | Steady red | Nonrecoverable major fault |
| NET | Flashing green | IP address obtained but no connection yet |
| NET | Flashing red | One or more connections to the drive have timed out |
| NET | Steady red | Duplicate IP address |
Source: Tables 67 and 68, p. 137. Rockwell notes that the status indicators are for diagnostics only and must not be used to judge the state of a safety function.
In Logix Designer
- The axis tags AxisFault and AxisState. Rockwell advises using only AxisState to decide whether the axis is faulted, because AxisFault can drop to 0 for a moment after a reset even when the fault is still there (p. 136).
- Bits in the Motion Fault Status and Motion Alarm Status words.
- How the axis reacts to each exception is set in Axis Properties, "Exceptions" category (Ignore, Alarm, Fault Status Only, Stop Planner, Disable, Shutdown); stopping actions such as "Connection Loss Stopping Action" are in the "Actions" category. From Logix Designer v32, "Disable" replaced "StopDrive" as the default. Exception actions cannot be changed online (pp.139–141, Figure 59).
- If the controller itself goes to a major fault because of the axis, 1756-RD001 lists CIP Motion faults as Type 18, for example "Type 18 Code 03" (standard axis fault), "Code 04" (manufacturer-specific axis fault) and "Code 08" (configuration fault). Each points you to the matching fault attributes of the axis for the cause. For module connection faults (16#0203, 16#0204 and so on) see ControlLogix I/O module faults.
The drive's web server
The Fault Log page shows major and minor faults. The web server is off by default; turn it on with "HTTP Access" on the drive display menu and cycle 24 V (Table 58, p. 97; p. 144).
Common fault codes
Fault names are kept in English as shown on screen. "Check first" gives initial checks from the general troubleshooting material in 2198-UM005E; Rockwell's official corrective actions are in the 2198-RD006 spreadsheet.
| Code | Fault name | Meaning | Check first |
|---|---|---|---|
| F05 | Motor Overtemperature Factory Limit Fault | Motor over temperature against the factory limit | Duty cycle, accel/decel profile, tuning gains too high, motor size against the load |
| F07 / F08 | Motor Thermal Overload (Factory / User Limit) | The motor thermal model exceeded the factory limit / the user-set limit | As for F05. "Motor Overload Action" can be set to Current Foldback |
| F09 | Motor Phase Loss | One motor phase carries no current. With torque proving enabled, the brake stays engaged | Motor power cable, connector, brake wiring (Appendix C, p. 224) |
| F10 | Inverter Overcurrent Fault | Inverter output current exceeded its limit | Motor power cable and connector. If it repeats, look up 2198-RD006 |
| F13 / F14 | Inverter Thermal Overload (Factory / User Limit) | The drive's inverter is thermally overloaded | Duty cycle, drive size against the current needed. "Inverter Overload Action" is available |
| F23 | AC Single Phase Loss Fault | One phase of the AC input is missing | Fuses/breaker, input terminals. Check that "AC Input Phasing" in Module Properties matches the actual supply (p. 110) |
| F25 | Pre-charge Failure Fault | The DC bus did not charge correctly | AC input wiring. A display stuck at 03 means the bus has not charged |
| F33 / F34 | Bus Undervoltage (Factory / User Limit) | DC bus voltage is low | AC input supply. Read "Bus Voltage" in the "Info" menu on the drive display. The AC voltage configured in Logix must match the hardware (p. 110) |
| F35 | Bus Overvoltage Factory Limit Fault | DC bus voltage is high | Power-up order: apply 24 V before AC so the shunt is enabled (p. 131). Internal or external shunt is connected and configured as the right type (pp.30, 110). Faults of the shunt itself (bus regulator) are F29–F31 |
| F43–F47 | Feedback Signal Loss / Motor Feedback Data Loss / Feedback Device Failure | Position feedback signal lost or faulty | Feedback cable, connector, grounding and shielding (Table 71) |
| F50 / F51 | Hardware Overtravel – Positive / Negative | The normally closed 24 V overtravel limit input has opened | Axis position, limit switch and wiring of the overtravel input |
| F54 / F55 | Excessive Position / Velocity Error Fault | The axis is not following the command | Jammed mechanics, coupling, brake, torque limits, profile, tuning. Loss of the A/B signals from a TTL encoder often shows up as this fault too |
| F61 | Enable Input Deactivated | The 24 V Enable input dropped | 24 V supply and wiring to the input assigned the Enable function (Table 21, p. 55) |
| Fc05 / Fc06 | Feedback Battery Loss / Low | Encoder battery | Applies only to Kinetix TLP or TLY-Axxxx-B encoders |
| nF06 | Lost Controller Connection Fault | Motion connection lost, for example module inhibited or network cable pulled | Ethernet cable, switch, NET indicator, controller state. The drive stops per the "Connection Loss Stopping Action" |
| nF09 | Duplicate IP Address Fault | Duplicate IP (NET steady red) | Change the IP address of the conflicting device |
| SF09 | Guard Stop Input Fault | The two STO inputs disagree | STO wiring, connector fully seated, 24 V supply, state of both inputs (Table 82, p. 157) |
Source: fault names from Tables 76–79 (pp.141–143); checks from Table 71 (pp.138–139), chapter 6 and chapter 9. For the full list with Rockwell's corrective actions, use the 2198-RD006 spreadsheet, Kinetix 5300 Fault Codes Reference Data. Knowledgebase QA59764 points to the same spreadsheet.
Order of checks
- Record before resetting (see the list at the end), and note the prefix: F/Fc is the axis, nF the network or module, SF the safety circuit.
- Power side: read the bus voltage on the display. If the bus does not reach the expected level, Rockwell says to check the AC input power connections (p. 131).
- Network side: NET indicator, cables, switch ports, duplicate IPs.
- Motor and feedback: wiring, connectors, grounding of shields. The hookup tests in Axis Properties ("Motor Feedback", "Motor and Feedback") help confirm the wiring. The "Motor and Feedback" test turns the motor, so remove the load first (pp.131–133).
- Mechanics: coupling, brake, obstruction, unusual friction.
Clearing the fault safely
- The drive removes the code from the display only when it receives a Fault Reset from the controller (for example an MAFR instruction) and the cause is gone. If the fault is still active it is posted again after a delay (p. 136).
- An exception set to the Shutdown action needs a separate Shutdown Reset (p. 140).
- Rockwell forbids defeating or overriding the drive's fault circuits: find and correct the cause before running again (p. 135).
- Clearing a fault can restart motion. Once the axis is enabled, the program may command motion straight away. Before resetting, make sure nobody is inside the hazard zone and follow the site's lockout and permit-to-work rules.
- On vertical loads, if the brake is controlled externally and is not set when the drive is disabled, the load can free-fall (Appendix C, p. 224).
- For SF09: the fault can be reset only after both STO inputs have been OFF for more than 1 second, and then an MAFR is needed. After work on the STO circuit, run the STO function to confirm it works correctly (pp.156–157).
- After switching power off, wait the 5 minutes given on the drive's warning label before working on the drive (p. 135).
When to suspect hardware
- MOD steady red: the drive reports a nonrecoverable fault.
- An STO discrepancy that remains after wiring and supply have been checked: Rockwell says to remove the drive from service immediately and return it to Rockwell (Table 82).
- A fault that returns after supply, wiring, network and mechanics are ruled out: check 2198-RD006 and contact technical support.
What to record before calling for support
- Drive catalog number (2198-C…-ERS) and firmware ("Info" > "Version" menu).
- Motor catalog number, feedback type, Logix Designer version.
- Fault code, AxisState, a screenshot of the Fault Log.
- When it happens: at power-up, on enable, while accelerating or while stopping.
- A copy of the project.
Need an engineer to check it on site: request support.
Frequently asked questions
What do F, nF and SF mean in Kinetix 5300 fault codes?
The leading letters give the fault group: F is a runtime axis fault, I a fault during initialization, nF a module-level fault that affects every axis, nA and A alarms only, S a condition that stops the drive from being enabled, and SF a fault detected in the safety function. An added c (for example Fc05) marks a manufacturer-specific code.
What does a Kinetix 5300 display stuck at 03 mean?
The drive is waiting for the DC bus to charge. If the bus does not charge correctly the drive reports F25 (Pre-charge Failure Fault); check the AC input wiring.
What should be checked for an F35 Bus Overvoltage fault on a Kinetix 5300?
Check the power-up order: apply 24 V before AC so the shunt is enabled. Check that the internal or external shunt is connected and configured as the right type; faults of the shunt itself are F29–F31.
How do you clear a fault on a Kinetix 5300?
The drive removes the code only when it receives a Fault Reset from the controller (for example an MAFR instruction) and the cause is gone; an exception set to Shutdown also needs a Shutdown Reset. Clearing a fault can restart motion, so make sure nobody is inside the hazard zone before resetting.
How do you handle SF09 Guard Stop Input Fault?
SF09 means the two STO inputs disagree: check the STO wiring, connector, 24 V supply and the state of both inputs. The fault can be reset only after both STO inputs have been OFF for more than 1 second, followed by an MAFR; if the discrepancy remains after wiring and supply have been checked, Rockwell says to remove the drive from service immediately and return it to Rockwell.
Sources
- Rockwell Automation, 2198-UM005E-EN-P, Kinetix 5300 Single-axis EtherNet/IP Servo Drives User Manual, 09/2024 — "Passive Shunt Considerations" (p. 30), chapter 6 (pp. 95–100, 110, 130–133), chapter 7 "Troubleshoot the Kinetix 5300 Drive System" (pp. 135–147), chapter 9 (pp. 155–157), Appendix C (p. 224), Table 21 (p. 55)
- Rockwell Automation, 1756-RD001, Logix 5000 Controller and I/O Fault Codes (spreadsheet), 09/2025 — Type 18 (CIP Motion)
- Rockwell Automation, 2198-RD006, Kinetix 5300 Single-axis EtherNet/IP Servo Drives Fault Codes Reference Data (spreadsheet referenced by the user manual and QA59764)
- Rockwell Automation Knowledgebase QA59764 (public), Kinetix 5300 Fault Codes, published 21 May 2024
Read 25 October 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system. Links open the latest edition in Rockwell's literature library; page numbers refer to the edition cited.