Record facts
Service notes
- Record whether the fault appears at enable, acceleration, steady running, deceleration or only when a HIM/DPI device is connected.
- F12/F13 cases should not be treated as module failures until motor cable, motor insulation, output accessories and trip timing are documented.
- F5/F4 cases require input voltage, DC bus, braking and load-inertia evidence before a control-board conclusion.
- DPI port-loss cases can be caused by noise, cable routing, HIM/adapter issues or internal communication hardware, so preserve port number and device context.
Related technical records
PowerFlex drive reports F12 / HW Overcurrent, often at start, acceleration or during a sudden load event.
PowerFlex reports F13 ground fault, sometimes intermittently and sometimes followed by a hardware-overcurrent trip.
PowerFlex reports F5 during deceleration, fast stop, lowering load or high line condition.
PowerFlex 750-class drive trips on a DPI port-loss fault or loses communication with HIM, TCOMM, adapter or peripheral device.
Routes F12 and F13 evidence through output bridge, current sensing, motor cable, motor insulation, grounding/shielding and mechanical load conditions.
Routes F4 and F5 evidence through input phases, fuses/contactors, precharge, DC-link capacitors, brake chopper/resistor, load inertia and line voltage.
Routes F81-F86 port-loss evidence through HIM, DPI cable, TCOMM/adapter, port number, electrical noise, grounding and control-board communication context.
PowerFlex drive reports F12 hardware overcurrent, F13 ground fault, or both around the same start/run event.
PowerFlex trips on F5 DC bus overvoltage or F4 undervoltage during power-up, line sag, acceleration or deceleration.
PowerFlex reports DPI port loss, HIM loss or communication loss to a connected port device.