61 on a Hitachi heat pump: No cascade messages - unit configured for YUTAKI Cascade Controller but no messages received for 180 s or since start
Short answer
On a Hitachi heat pump, 61 means: No cascade messages - unit configured for YUTAKI Cascade Controller but no messages received for 180 s or since start. The heat pump stops until the fault clears or is reset. An engineer is needed to fix the cause.
Reviewed 23 September 2026 · 1 source
What it means
The manual says: No cascade messages - unit configured for YUTAKI Cascade Controller but no messages received for 180 s or since start.
Part involved: cascade controller link.
Likely causes:
- Loose, disconnected, broken or short-circuited connector; software stops indoor and outdoor operation until communication restored.
Is it safe?
| Does the heat pump stop? | Yes |
|---|---|
| Severity | Fault — needs a manual reset once the cause is fixed |
| Engineer needed? | Yes |
The heat pump stops until the fault clears or is reset.
No need to switch off — call an engineer if it comes back.
Resetting itself: no.
Manual reset: After cause fixed.
What you can check
- Read and note the alarm code and any retry code (e.g. P70) shown on the unit controller.
- Check the heat pump supply breaker/isolator at the consumer unit is ON.
- Restart once via the unit controller (or switch off/on at the isolator) - the manual states the unit must be stopped to release most alarms; if the code returns, call an engineer.
What the engineer will check
- Follow SMGB0146 section 6.7 troubleshooting flowchart for alarm 61.
- Check H-Link / transmission wiring polarity, continuity and terminal tightness.
- Check PCB fuses and DIP-switch/address settings.
- Check power to the other unit (outdoor/indoor/controller).
Who to ask for: Heat pump installer / service engineer (controls wiring).
Certification: None specific.
What you might notice
Sources
- Installation & Operation Manual - YUTAKI series and YUTAKI Cascade Controller (R410A series / R32 series) ↗ · PMML0510 rev.1 - 10/2019 · page p.146 (PDF p.157) · Reviewed 23 September 2026
A code explains what the controller detected, not a confirmed root cause.
Reviewed: 23 September 2026