Scope of this technical record
Power-Module Replacement Precheck for qualified repair triage.
Only qualified personnel should implement any electrical test; high-voltage discharge and isolation are mandatory.
Purpose
An FR-A740 module failure must be treated as a possible cascading driver/supply event. Record module identification and prior damage, clean and inspect the board area, and verify that the external load path will not immediately reproduce the failure.
Investigation logic
Before powered output testing, compare auxiliary and isolated driver rails plus homologous gate channels. The reviewed FR-A740 drawing family provides the functional reference for this comparison.
Completion and stop conditions
A unit with uncertain module compatibility, missing protection evidence or asymmetric driver behaviour should not be energised merely to see whether it works.
The reason a module replacement needs a precheck
A destroyed power module is often the most visible damage, but it may not be the initiating cause. Driver damage, unstable gate support supply, current-feedback defects, braking/DC-link stress or a motor/cable short can destroy the replacement as soon as modulation is commanded. The precheck exists to prevent an expensive repeat event.
A sound record therefore ties the replaced module to the protection code, failed phase if identifiable, gate-driver board markings, auxiliary-supply evidence, output-circuit condition and any prior braking or overload history. The purpose is to create a go/no-go decision for specialist testing, not to instruct unsafe full-power experimentation.
Replacement release checklist
| Item | Evidence required | No-go finding |
|---|---|---|
| External output circuit | Qualified motor/cable assessment | Short or ground fault unresolved |
| Gate-drive branch | Channel comparison and damage check | One path damaged or unexplained |
| Support supply | Stable relevant supply/reference evidence | Rail collapse or instability |
| Cause history | Fault/load/brake context recorded | Original destruction mechanism unknown |
Practical branching record
A competent workflow records observations before making a replacement decision. First capture the displayed trip and operating instant. Next identify whether the fault can occur with the motor disconnected under manufacturer-approved conditions, whether deceleration/braking conditions are relevant, and whether prior module or board work was performed. Only after these branches are documented should the investigation move to board-level evidence.
The value of this sequence is that identical-looking trips can have entirely different root causes. An acceleration overcurrent may come from an output short or mechanical demand; a regenerative overvoltage may be caused by deceleration energy and braking configuration; a repeated immediate trip after output-stage repair may justify analysis of gate-drive or feedback circuitry.
Workflow result categories
| Finding | Interpretation | Next controlled action |
|---|---|---|
| Fault clears after external circuit is isolated | Investigate motor, cable or application side | Do not replace internal board on that evidence alone |
| Fault persists without external cause | Internal stage becomes credible | Preserve fault log and request board/module assessment |
| Fault depends on stopping profile | Regenerative energy path is relevant | Review deceleration/braking design before board work |
| Recent module replacement and repeat trip | Companion damage is possible | Verify driver/supply/protection before further power testing |
Stop conditions for a field technician
Stop further attempts when there is visible power-stage damage, a repeat protective trip with external causes excluded, unstable control supplies, evidence of carbonisation or flashover, or uncertainty about DC-bus discharge and safe isolation. Repeated reset-and-run attempts can convert a repairable board problem into a destroyed power module and collateral control-board damage.
A useful escalation request contains the exact model, trip history, whether the trip occurs before or after output command, motor/cable test status, brake-unit details where relevant, and clear photographs of affected board and module markings. This turns a vague fault inquiry into a diagnostic case that a specialist can evaluate.
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Circuit-function mapping prepared from reviewed drawing records; original schematic files are not redistributed.
Official FR-A700/FR-A740 operating, parameter and protective-function reference.
Linked records
Official FR-A700 protection logic activates E.OC1 when output current reaches or exceeds approximately 220% of rated current during acceleration. The investigation must separate load/ramp causes from output short circuits and internal driver or power-stage damage.
FR-A700 documentation states that E.THT protects the output transistors through an electronic thermal model when high current persists below the instantaneous overcurrent threshold; the cited overload capacity is 150% for 60 seconds with inverse-time behaviour.
A circuit-derived map of the FR-A740-37KW DB1 supply sheet: rectified input, flyback conversion, feedback regulation, ±15 V / +24 V services and isolated driver rails.
Maps the matched isolated drive stages, gate resistors/clamp paths and feedback connections visible across reviewed 7.5, 15 and 37 kW sheets.