Scope of this technical record
ATV61 / ATV71 OCF routing for users deciding whether overcurrent is created by load inertia, brake release, motor data, ramp settings, motor/cable fault, current sensing or output power bridge damage.
Do not repeatedly reset OCF into a high-current condition. Secure the machine, isolate hazardous voltage and separate the motor/cable boundary before internal inspection.
ATV61 / ATV71 OCF route
OCF is first a motor-data and load timing question before internal current-path repair.
ATV61 / ATV71 OCF timing image
Searcher intent coverage
OCF users need to know whether the drive hit current limit because of setup, load or a real power path issue.
| Observed situation | Decision needed | Evidence that satisfies the search |
|---|---|---|
| At start | Motor data or output path | Nameplate/settings and insulation boundary |
| During acceleration | High inertia or ramp | Acceleration time and load evidence |
| After repair | Driver/output path | Previous repair and channel evidence |
What OCF users are trying to solve
An OCF search usually comes from a machine that trips at start, during acceleration, or when the load changes. Schneider public guidance points to hardware current limitation, motor parameters, high inertia, overloading or mechanical locking. The page must therefore start with the machine event, not the power board.
ATV71’s common application base—hoist, conveyor, packaging and high-inertia machinery—makes this especially important. A brake that releases late, a jammed conveyor, a heavy lift, a pump blockage or a too-short ramp can all produce a current fault while the drive is working correctly.
OCF timing map
| When OCF appears | Most likely first boundary | Evidence to record |
|---|---|---|
| Instant at enable | Output wiring, motor cable, phase/ground fault or power bridge | Motor/cable isolation, terminal inspection, whether SCF also appears |
| During acceleration | Ramp, high inertia, brake release, motor data, load torque | Acceleration time, motor current, brake status, load condition |
| Only under process load | Mechanical jam, overloaded machine, pump/fan blockage | Load event, current trend, mechanical inspection |
| After parameter work | Motor nameplate mismatch, control mode, current limit | Old/new parameters, motor plate photo, autotune history |
| After module repair | Driver/current feedback/cause not corrected | Static bridge and driver evidence before another run |
Field checking sequence
Record the exact trip timing first. If OCF occurs immediately at enable, stop and prove the output wiring and motor/cable boundary. If it occurs during acceleration, review load, brake release, acceleration ramp, motor data and control mode. If it occurs only during production, inspect the mechanical process before blaming the drive electronics.
When external evidence is not enough, move inward: output bridge static evidence, gate-drive path, current sensing and control-board interpretation. This inward movement should only happen after the motor/cable/load route is documented. Otherwise a replacement power board may be destroyed by the same external cause.
OCF decision table
| Evidence | External/machine route | Drive-side route |
|---|---|---|
| Brake not fully released | Strong external route | Drive may simply be responding to load |
| Acceleration too short for load inertia | Strong setup route | Power hardware not proven |
| Motor data inconsistent with nameplate | Parameter route | Board replacement premature |
| Fault clears after motor/cable isolation | External output route | Internal fault not proven |
| Fault remains with external route proven | External route weaker | Output bridge/current sense/driver route stronger |
Repair request standard
A useful OCF request includes the ATV type code, application, motor data, trip timing, acceleration/deceleration settings, brake/load evidence, motor/cable insulation result and whether SCF or other codes appear. If the drive was already repaired, include what power or driver assemblies were changed and whether the original motor/cable was tested.
Do not describe the case as “OCF board fault” unless the external route has been proven. The strongest article outcome is a clear next decision: adjust ramp/load/motor data, repair motor/cable/brake, or escalate to output stage/current sensing with evidence.
OCF stop conditions
| Condition | Reason | Next action |
|---|---|---|
| Mechanical load not checked | Drive may be protecting itself | Secure and inspect machine load |
| Motor/cable insulation unknown | External fault may destroy bridge | Isolate and test correctly |
| Brake release unknown | Held load can cause instant current rise | Verify brake command and physical release |
| Prior module repair undocumented | Repeat failure risk | Collect driver/module repair evidence |
Field record checklist
- ATV61/ATV71 type code and application
- OCF timing: enable, acceleration, load, reversing or heat soak
- Motor nameplate data and parameter values
- Brake release, mechanical load and ramp settings
- Motor/cable insulation and terminal evidence
- Output bridge/current-sense evidence only after external route is proven
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Public FAQ describes OCF as hardware current limitation and points to motor parameters, high inertia, overload and mechanical locking.
Used for application context and protection-family routing.