Hitachi Industrial Drives fault record

E07: DC-bus overvoltage during deceleration, regeneration or high-line operation

The SJ300 / L300P trips E07 when the internal DC bus exceeds the overvoltage threshold. The trip may appear during deceleration, stop commands, descending or overhauling loads, high incoming AC voltage, or braking resistor / braking unit duty problems.

Fault-code evidence page11 min read

Scope of this technical record

Fault-level explanation for SJ300 / L300P E07 overvoltage that separates high-line voltage, regeneration, deceleration ramp, braking resistor / BDU duty and DC-bus sensing boundaries.

Safety boundary

E07 means the DC link has exceeded a protection threshold. Do not access brake resistor, DC-bus or power-board areas until isolation and discharge are verified.

Hitachi E07 overvoltage route

1Trip timing
2Line / load
3DC link
4Brake route
5Sensing boundary

E07 is routed through line voltage, regeneration and braking evidence before board conclusions.

What E07 is really asking

E07 is often treated like a one-line fault code. In service, the useful question is why the DC link rose above threshold. The answer can be supply-side, machine-side, braking-side or sensing-side.

A stop-time E07 usually points to energy returning from the motor into the DC link. A power-up or idle E07 with normal machine load points elsewhere: high line, wrong voltage class, measurement/sensing evidence or a control interpretation problem. This page keeps those routes separate.

Deceleration overvoltage is not automatically a failed drive

When a high-inertia machine stops quickly, the motor becomes a generator and sends energy back to the drive. If the ramp is too aggressive or the braking route cannot absorb energy, the DC link rises and E07 follows. In that case, replacing a board can leave the real problem untouched.

The evidence package should include ramp settings, load behaviour, resistor value, duty cycle, thermal switch state and whether the fault disappears when the machine coasts or uses a longer deceleration time.

  • Trip at stop or decel: start with regeneration and brake route.
  • Trip at idle: start with line and sensing evidence.
  • Trip after repeated stops: check resistor duty and heat evidence.
  • Trip after a retrofit: verify resistor selection and braking-unit arrangement.

Repair boundary

Only after line voltage, load inertia, ramp profile and brake resistor route have been closed should the case move to DC-bus sensing or control-board repair. That boundary is important because SJ300 / L300P drives are old enough that used-board replacement is common and mis-matched donor boards can introduce new faults.

A useful E07 request therefore needs the model suffix, voltage class, frame, braking hardware and machine duty. Without that, the case remains a symptom report rather than a repair decision.

Field record checklist

  • Photo of display with E07 and timing notes
  • Incoming line voltage and voltage class
  • Deceleration time and stop mode
  • Load inertia or overhauling-load evidence
  • Brake resistor value, duty and thermal switch evidence
  • Braking unit / BDU identity if external

Technical basis and reference documents

This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.

SJ300 Troubleshooting and Maintenance, Chapter 6AutomationDirect / Hitachi manual mirror

Defines the status-at-trip context and links E07 to DC-bus overvoltage evidence.

L300P Series Inverter Quick Reference GuideHitachi Industrial Equipment Systems

Lists E06 braking resistor overload and E07 overvoltage protection caused by regenerative motor energy.

SJ300 Dynamic Braking Selection ChartHitachi AC Drive

Shows that braking capability, resistor value, duty cycle and external braking units vary by rating.

SJ300 & L300P Series Inverters Service ManualHitachi America / public service-manual mirror

Describes overvoltage detection by regenerated motor energy or high incoming AC voltage and highlights BRD-duty context.

Diagnostic workflow

Evidence intake

Turn this record into a qualified service request

A repair decision is much more reliable when the request includes the exact identity of the drive, the first fault evidence and the machine condition when the symptom appeared.

  • Complete drive type code / MLFB or nameplate model
  • Fault code, fault value and first event before reset
  • When the event appears: power-up, enable, ramp, run, decel or stop
  • Motor/cable connected or isolated during the symptom
  • Visible board, option-card, module and connector identifiers
  • Previous repair history, replacement parts and repeat-failure pattern
Prepare request →