Kinetix 5500 Stuck in Precharge State: Why and How to Fix?

The axis sits in Precharge. No fault code, no red LED, no entry in the controller fault log. The machine just will not move, and a Run/Program/Run transition on the controller clears it as if nothing happened. A week later it comes back.

Start here: a drive that was already running does not fall back to Precharge. Precharge is the first state in the CIP Motion power-up sequence (Pre-charge → Stopped → Starting → Running). Seeing it again means the drive re-entered that sequence — either it decided the DC bus is not up, or the state machine was never allowed to leave Precharge cleanly in the first place. Those are two different faults with two different fixes.

Read the State Before You Reset It

The Run/Program/Run transition is the worst thing you can do first. It reinitializes every axis and destroys the evidence. Dropping the enable bit and letting the axis fall to Stopped, then re-enabling, tells you far more: if the drive comes back to Running and operates normally, the hardware precharge circuit works and the bus is capable of supporting the load. You are chasing a transient or a sequencing race, not a dead component.

Build a Logix trend before you touch anything else. Sample at the motion group coarse update period and log, for every axis on the string:

• Axis.AxisState
• Axis.DCBusVoltage
• Axis.ServoActionStatus
• Axis.AxisFault and Axis.StartInhibits
• Your enable bit and your move-request bit

Set the trend to capture on the transition into Precharge. The order of events in that capture decides which branch below you take.

Check 1: Verify Bus Configuration on Every Axis

Open Axis Properties → Power on all four drives and read the Bus Configuration setting. On a four-drive string with the H025 as the converter, it must read:

1. Position 1 (H025, first in line): Shared AC/DC
2. Position 2 (H025): Shared DC
3. Position 3 (H008): Shared DC
4. Position 4 (H008): Shared DC

A follower left at Standalone or Shared AC runs its own precharge logic and expects its own three-phase input on terminals that are not wired. It will sit waiting for a bus-up condition it can never validate on its own terms, and it will report Precharge intermittently as the shared bus voltage moves around. That is a five-minute check and it eliminates a whole branch. If the settings are correct, move on — do not keep re-downloading the project.

While you are in Power, confirm the converter drive is actually rated for the connected string. Cross-check total connected drives, total bus capacitance, and continuous bus power against the bus-sharing tables in the Kinetix 5500 user manual. An undersized converter shows up exactly as this symptom: fine most of the time, reverting to Precharge on the load peaks.

Check 2: Trend DC Bus Voltage Against the Rectifier Math

A reported 550 V bus is the single most useful number in this failure. Compare it to what the rectifier should produce:

• Loaded six-pulse bridge: Vdc ≈ 1.35 × V_LL
• Lightly loaded / no load: Vdc ≈ 1.414 × V_LL

On a 400 V line that gives roughly 540–566 V DC. 550 V is normal. On a 480 V line the same math gives roughly 648–679 V DC, and 550 V is badly low. Confirm your actual line-to-line RMS with a meter at the drive input terminals — do not take it from the drawing.

If the bus is low for your line voltage, there are three realistic causes:

• Lost or weak input phase on the converter drive. Single-phasing drops the average bus voltage and adds heavy ripple; the ripple troughs cross the bus-low threshold and kick the string back to Precharge. Meter all three phases under load, not just at rest, and check the input fuses individually.
• Precharge relay not bypassing. If the internal bypass never latches, the bus stays fed through the precharge resistor. Unloaded it charges to something that looks plausible; the moment an axis draws current the bus sags and every drive on the string re-enters Precharge. This is the failure described in Rockwell Automation Knowledgebase document 626724, Kinetix 5500 Drive: Stuck in Precharge with Main AC applied (TechConnect access level). If your trend shows bus voltage that sags in proportion to motor current, stop here and treat it as a hardware fault on the converter drive.
• Upstream contactor chatter. A control-circuit glitch that drops the main contactor for a few line cycles is enough. Trend the contactor auxiliary contact alongside the bus voltage.

Check 3: Control Power and the Bus Bar Path

The fact that positions 1 and 4 are the ones failing is a hardware clue, not a coincidence. Position 1 owns the precharge circuit. Position 4 is electrically the farthest point on both the DC bus links and the 24 V control power daisy chain.

1. Meter the 24 V DC control power at the terminals of drive 4, with all axes enabled and moving. Compare against the control input voltage range in the Kinetix 5500 manual. A dip below the minimum resets the drive's logic and restarts the power-up state machine — which is exactly a return to Precharge with no fault logged.
2. Torque every shared-bus connector and jumper bar to the manual's specification. A high-resistance link on the last drive produces voltage dips under load that only that drive sees.
3. Check the 24 V supply sizing. Add the control power draw of all four drives plus any brakes and safety relays sharing the supply. Brake release and drive enable happening in the same scan is a classic dip source.
4. Inspect the shared-bus connector seating on every drive. Partial insertion passes a static continuity check and fails under vibration.

If control power is solid and the links are tight, this branch is closed. That is not the fault. Move to the ladder.

Check 4: Fix the Enable-to-Motion Handshake

This is the branch most four-axis machines end up on. MSO is asynchronous. Its .DN bit means the controller accepted the command, not that the drive has taken servo action and reached Running. Gate a MAM or MDS on MSO.DN and you issue a position command while the axis is still in Starting, with the current loop not yet stable and the bus loaded by whatever the other three axes are doing.

Gate on the axis status bit instead, and add a settle delay:

Two more sequencing rules for a shared bus:

• Stagger the enables. Do not execute four MSO instructions in the same scan. Enable position 1, wait for ServoActionStatus, then position 2, and so on. Simultaneous enable across a shared bus stacks the magnetizing inrush onto one converter.
• Handle the disable path too. Your machine already demonstrates this: when the manual-mode timeout drops the enable, the drives leave Precharge and land in Stopped. A clean MAS-then-MSF sequence, rather than dropping the enable while motion is still commanded, keeps the state machine deterministic.

Verify the Fix and When to Escalate

1. Re-run the trend with the corrected sequence. Confirm every axis transitions Pre-charge → Stopped → Starting → Running once at power-up and never re-enters Precharge afterward.
2. Log DCBusVoltage across a full production cycle including the worst deceleration. The minimum must stay clear of the bus-low threshold with margin; a bus that only just holds up will fail again on a hot day.
3. Confirm Axis.StartInhibits reads zero on all four axes before each enable.
4. Run the machine for at least twice the historical fault interval — two to three weeks against a 1–2 per week rate — before calling it closed.
5. Leave the trend armed on a capture trigger so the next occurrence, if any, is recorded rather than reset away.

If the bus voltage sags in proportion to motor current, or the string re-enters Precharge with the ladder sequencing corrected and control power verified at the drive terminals, the precharge bypass in the converter drive is the remaining suspect and it is not a field repair. Open a ticket with Rockwell Automation Technical Support with the trend export, the catalog numbers and firmware revisions of all four drives, the measured line-to-line and DC bus voltages, and the Bus Configuration setting from each axis. Ask them to review Knowledgebase document 626724 against your capture.

FAQ