ATV630 ready, but RUN on the terminal does not start
A ready drive does not necessarily receive the command from the terminal. The ATV630 FAQ distinguishes control from clamps and HMI control; the local/remote key may not be enabled.
The case in 60 seconds
A ready drive does not necessarily receive the command from the terminal. The ATV630 FAQ distinguishes control from clamps and HMI control; the local/remote key may not be enabled.
Read the displayed status and the indication of the control channel; write down the controller's request.
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
- Read the displayed status and the indication of the control channel; write down the controller's request.
- Before trying RUN, check that the machine can start safely and that the operation is authorized.
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 the active command source with the schema and operating mode.
- The channel selection must comply with interlocks, automation and business procedure: do not force a local start.
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
- See Command and Reference and configuration of the HMI command in the applicable revision.
- Document the local/remote passage and return to automatic management; check separately command and reference.
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 if it's not clear who can start the car. A channel change can change system behavior.
When the problem is really solved
The command source and the reference must be those provided even after the automatic return.
- 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 · EAV64318 · Official PDF
- Schneider Electric · Programming and DiagnosticManual · IT · EAV64323 · Official PDF