ACH580 ready but not part: permissive and interlock
The codes indicate run enable, run permissive or start interlock missing: the drive can be healthy but correctly blocked by the logic machine.
The case in 60 seconds
The codes indicate run enable, run permissive or start interlock missing: the drive can be healthy but correctly blocked by the logic machine.
It records hexadecimal code, command source, local/remote state and cycle phase.
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
- It records hexadecimal code, command source, local/remote state and cycle phase.
- Recovers the scheme and locates the external permissive or fieldbus provided without piercing it.
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
- For AFEB test source and parameter status 20.12; for AFED use 20.40; for AFEE–AFF1 compares 20.41–20.44 with real inputs.
- Check signal, power, wiring and master status while keeping intact STO and interlocking.
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 state words and PLC/BMS logic with saved configuration and behavior required by the project.
- Perform only one supervised test after showing that machine and process can leave safely.
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.
- Do not bridge consensus, permissive, interlocking or STO. If it is not clear the function of an input, stop and consult schema, OEM or security manager.
When the problem is really solved
The permissive comes back for the intended cause, the drive only leaves in the authorized sequence and the correction is also confirmed by the supervision system.
- 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
- ABB · HVAC firmware manualProgramme · EN · 3AXD50000027537 · Official PDF
- ABB · HVAC firmware manualProgramming · IT · 3AXD50000027596 · Official PDF