Free Shipping Across the USA — Worldwide Delivery Available!
PALM Parts Solution
AccountQuote

FAULT CODE LIBRARY

PowerFlex 755 Fault F36 — SW OverCurrent

Is your Allen-Bradley PowerFlex 755 VFD tripping on Fault F36? Learn how to diagnose software overcurrent, optimize drive parameters, and resolve load issues fast.

Worldwide Shipping
Fast Dispatch
Warehouse Pickup
1-Year Warranty

In short

Is your Allen-Bradley PowerFlex 755 VFD tripping on Fault F36? Learn how to diagnose software overcurrent, optimize drive parameters, and resolve load issues fast.

Overview

An F36 'SW OverCurrent' (Software Overcurrent) fault on an Allen-Bradley PowerFlex 755 variable frequency drive (VFD) indicates that the drive's firmware has detected an output operating current that exceeds the software-defined threshold limit. Unlike a hardware-initiated instantaneous trip (such as Fault 12 HW OverCurrent, which is triggered by an analog comparator to protect physical hardware), the F36 fault is managed programmatically by the drive's digital signal processor (DSP). It warns that the system is drawing excessive current relative to the programmed motor nameplate limits, tuning parameters, or application curves before physical damage occurs.

Symptoms

When a PowerFlex 755 encounters an F36 fault, the drive exhibits several distinct behaviors:

  • Sudden Stop: The drive immediately ceases output power modulation to the motor, allowing the motor to coast to a stop unless configured otherwise.
  • HMI Display Warning: The Human Interface Module (HIM) displays 'Fault - F36' along with a flashing red status ('STS') LED on the main control capsule.
  • Intermittent Tripping during Ramps: The fault frequently presents itself during changes in speed—specifically during acceleration or deceleration transitions.
  • Connected Components Workbench (CCW) Flag: Active faults read as Fault 36 in the diagnostic buffer of CCW or Studio 5000 Logix Designer.
  • Mechanical Strain: Audible groaning or structural vibration from the motor frame immediately preceding the trip.

Possible Causes

Understanding what triggers an F36 fault is key to focusing your physical diagnostic efforts. The most frequent causes include:

  • A mechanical jam or overload: A physical blockage, worn bearing, or seized transmission elements in the driven machine (e.g., pump, fan, conveyor, extruder).
  • Improperly configured motor nameplate parameters: Incorrect entries in Port 0 for Parameter 413 [Motor NP Amps], Parameter 421 [Rated Amps], or Parameter 422 [Current Limit 1].
  • Overly aggressive acceleration/deceleration rates: Ramp times (Parameter 140 [Accel Time x] or Parameter 142 [Decel Time x]) set too short for the inertia of the connected load.
  • Inadequate motor tuning: Incorrect stator resistance (Rs) or stator inductance (Ld/Lq) estimates stored in the drive's motor model when running in Sensorless Vector or Flux Vector control modes.
  • Excessive capacitive cable charging current: Very long motor lead runs (typically greater than 50 meters or 150 feet) paired with high carrier frequencies (Parameter 40), causing false software-side overcurrent measurements.
  • Mechanical brake sequencing issues: The motorized mechanical brake failing to release before the drive attempts to ramp output frequency and torque.
  • Phase-to-phase or phase-to-ground leaks: Developing insulation breakdown in the motor windings or output cables that is not clean enough to trip hardware limits but triggers software limits.

Step-by-Step Troubleshooting

Follow these sequential diagnostics to isolate, identify, and repair the cause of an F36 fault on your PowerFlex 755:

Step 1: Isolate the Drive from the Motor

Perform a 'no-load' diagnostic test to rule out internal drive failure. Lock out and tag out (LOTO) incoming power to the drive. Disconnect the motor output leads from terminals U/T1, V/T2, and W/T3 at the bottom of the power module. Change the motor control mode in Parameter 35 [Motor Ctrl Mode] to 'V/Hz'. Re-energize the drive and command a run.

  • If the drive immediately trips on F36 even with no output wires connected, the internal current-sensing Hall effect transducers or the main gate driver board are faulty and must be replaced.
  • If the drive runs successfully without tripping, the issue resides in the cabling, the motor, the configuration parameters, or the mechanical load.

Step 2: Audit and Correct Motor Nameplate Parameters

Access Parameter Group 4 (Motor Data) via your HIM or configuration software. Verify that the programmed settings match the physical nameplate of your motor exactly:

  • Parameter 413 [Motor NP Amps]: Must match the motor FLAs (Full Load Amps) for the corresponding voltage configuration.
  • Parameter 422 [Current Limit 1]: Typically set between 110% and 150% of the motor FLAs depending on the duty cycle (Normal Duty vs. Heavy Duty). Ensure this is not set too low, which can provoke early software trips.

Step 3: Run an Autotune Routine

Incorrect electrical representation of the motor model causes the drive's vector control algorithms to miscalculate voltage vectors, leading to localized current spikes.

  1. Navigate to Parameter 70 [Autotune].
  2. If the motor can safely rotate decoupled from the load, select 'Rotate Tune' (option 2).
  3. If decoupling is not possible, select 'Static Tune' (option 1).
  4. Press start. The drive will measure winding characteristics and dynamically update its internal slip and stator resistance values, stabilizing the current signature.

Step 4: Examine Accel and Decel Times

A motor trying to change velocity faster than physics allows will draw excess current. Locate Parameter 140 [Accel Time 1] and Parameter 142 [Decel Time 1].

  • Increase these values by 30% to 50% (e.g., from 3.0 seconds to 6.0 seconds). Run the application again to monitor if the current spike during start-up is flattened below the F36 threshold.

Step 5: Check Mechanical Brake Interlocks

If your mechanical system uses a brake shoe or electromagnetic brake caliper, ensure the drive is controlling the brake release circuit properly. Verify Parameter 370 [Stop Mode] configuration and ensure torque proving is active if performing vertical lifting. A common failure mode is the brake remaining physically clamped for the first 500ms of operation while the drive attempts to reach target frequency.

Step 6: Cable Length and Carrier Frequency Inspections

Long output runs act like capacitors, leaking high-frequency current currents to ground across the insulation surface.

  • Read Parameter 40 [Carrier Frequency]. If it is configured to 8 kHz or higher, reduce it to 4 kHz or 2 kHz to reduce physical charging currents.
  • Ensure output cabling does not run parallel to high-EMI conductors without proper shielding.

Step 7: Perform High-Voltage Insulation Testing

Using a digital multimeter to check resistance is insufficient for high-voltage insulation tracking. Disconnect the motor cables entirely from the drive terminals. Use a modern Megohmmeter (Megger) to apply a 500V DC or 1000V DC test. Test phase-to-phase (U to V, V to W, W to U) and phase-to-ground. Standard industrial motors should register at least 100 Megohms. Anything below 10 Megohms suggests deteriorating winding insulation or water in the terminal box.

To prevent the reoccurrence of software overcurrent conditions on your production line, implement the following engineering controls:

  • Implement a Line or Load Reactor: Installing a 3% or 5% impedance load reactor between the PowerFlex 755 output terminals and your motor will smooth out rapid current transitions and damp high-frequency cable charging spikes.
  • Enable Overcurrent Limit Profiling: Use Connected Components Workbench to log trend charts of the output current (Parameter 9 [Output Current]) during normal production cycles to determine how close the system operates near the F36 limit.
  • Schedule Periodic Lubrication: Often, gradual mechanical wear on gearboxes and conveyor bearings creeps the baseline motor draw upward over several months until it repeatedly hits the F36 boundary.

If diagnostic step 1 reveals that the drive is tripping independently of an external load, specific internal components require replacement:

  • Main Control Board (MCB): Part Number 20-750-MCB1. This unit manages firmware-level protection limits and current measurement interpretation.
  • Current Transducer (CT) Kit: Replacement Hall-effect sensors matching your respective PowerFlex 755 Frame Size (Frame 1 through Frame 7 options vary by amperage rating).
  • IGBT Power Module Assembly: If internal shorting has occurred within the power switches, replacing the power module or the complete internal power structure is critical.

FAQ

Q: Can I disable the F36 SW Overcurrent fault to keep production running?

A: No, F36 is a critical safety fault intended to prevent winding destruction and controller failure. While you can adjust the current boundaries slightly via parameters like Parameter 422 [Current Limit 1], setting this threshold above your drive or motor capabilities will cause permanent components to burn out or create a fire hazard.

Q: What is the primary operational difference between F36 (SW Overcurrent) and F12 (HW Overcurrent)?

A: F12 is an instantaneous hardware trip triggered directly by solid-state circuitry bypassing the main firmware logic—it is designed to instantly shut down the drive during catastrophic events like a direct short-circuit. F36 is a software-calculated trip that occurs when current values exceed safe operational curves tracked over milliseconds by the firmware's control loops.

Q: Why does the drive trip on F36 only when starting up a high-inertia load?

A: High-inertia loads require substantial torque to overcome static friction, demanding high amounts of starting current. If the acceleration ramp time is too short, the drive must produce extensive current to force the change in velocity, causing the software envelope to flag an overcurrent event. Increasing the acceleration time resolves this.

Q: Does keeping my carrier frequency high benefit the drive in any way concerning F36?

A: A high carrier frequency (e.g., 12 kHz or 16 kHz) makes the motor run more quietly by keeping the switching noise above the range of human hearing, but it generates considerably more internal heat in the VFD and creates higher capacitive cable charging currents that feed directly into F36 faults. Lowering it to 2 kHz or 4 kHz is mechanically and electrically safer for heavy industrial environments.

Shop the parts in this guide

Browse in-stock inventory for the products covered by this article.

Need a specific part?

Send us your part numbers — we'll respond the same business day with pricing and availability.

Are you an Electrical Distributor?Learn more about our distributor program

PALM Parts Solution sells used surplus products. PALM Parts Solution is not an authorized distributor, affiliate, or representative for the brands we carry. Products sold by PALM Parts Solution come with PALM Parts Solution's 1-Year Warranty and do not come with the original manufacturer's warranty. Designated trademarks, brand names and brands appearing herein are the property of their respective owners. This website is not sanctioned or approved by any manufacturer or tradename listed.

Read full disclaimer →