OCF: overcurrent on ATV320
The drive signals an excessive current. The code does not show itself a failure of the Drives: it is necessary to distinguish start, regime and stop.
The case in 60 seconds
The drive signals an excessive current. The code does not show itself a failure of the Drives: it is necessary to distinguish start, regime and stop.
Transcribe the code and indicate if it appears before the rotation, during the speed or machine climb already started.
The code or symptom directs research, but does not show the fault component alone.
Diagnostic map
Follow the rows in order. Each phase must produce evidence before moving to the next.
| Phase | Controls | Evidence to obtain | Next decision |
|---|---|---|---|
| 01Recognize and collect |
| Event context and complete initial data. | If a data is missing, do not reset to attempts: complete the initial picture first. |
| 02Check and separate hypotheses |
| External causes, configuration, circuit and separate process. | If the data does not match, return to the correct schema and revision before changing parameters. |
| 03Interpret and demonstrate |
| Cause supported by repeatable data and authorized evidence. | If the cause is not proven, stop changes and involve manufacturer, OEM or machine manager. |
Reading and observation
Recognize and collect
- Transcribe the code and indicate if it appears before the rotation, during the speed or machine climb already started.
- Collect engine plate, complete drive reference and load description; Don't repeat the warnings.
Event context and complete initial data.
If the result does not matchIf a data is missing, do not reset to attempts: complete the initial picture first.
Qualified technician
Check and separate hypotheses
- Compare engine data configured with the license plate and the engine/drive combination provided by the project.
- With secure installation, check any mechanical impediments; separates the condition of the refrigerator process from the electrical data.
External causes, configuration, circuit and separate process.
If the result does not matchIf the data does not match, return to the correct schema and revision before changing parameters.
Specialist deepening
Interpret and demonstrate
- Compare current trend, reference and frequency in the same cycle. Store initial configuration and test conditions.
- A change to the current limit requires verification of the sizing and protections; is not an automatic remedy to OCF.
Cause supported by repeatable data and authorized evidence.
If the result does not matchIf the cause is not proven, stop changes and involve manufacturer, OEM or machine manager.
What to avoid
- Use repeated resets as a diagnostic test.
- Transfer codes, thresholds or parameters from one Drives family to another.
- Change a protection before connecting symptoms, measurement and phase of the cycle.
- Stop the tests if there is mechanical block, abnormal noise or immediate occurrence. Do not increase the limits to make the code disappear.
When the problem is really solved
It documents the identified cause and an authorized cycle without recurrence, under conditions that generated the event.
- The cause is supported by data and not only by the momentary absence of the alarm.
- The cycle that generated the problem has been repeated in authorized conditions.
- Final configuration, measurements and outcome are consistent with applicable machine, drive and documentation.
Applicable documents
Always check size, firmware, options and revision. These sources do not extend the case to other families.
- Primary source of the caseOpen the official source la
- Schneider Electric · Programming and DiagnosticManual · EN · NVE41295 · Official PDF
- Schneider Electric · InstallationManual · EN · NVE41289 · Official PDF