What happens
An incompatible controller, wrong address or failed communication interface prevents the intended nodes from exchanging valid information.
Typical symptoms
Communication fault persists with verified power and cable integrity, or appears after replacing a board or adding a zone.
Checks that distinguish this cause
Inventory controller and board part numbers, address settings and approved combinations. Use the model diagnostic tool to isolate nodes only through the permitted process; do not borrow another brand’s test box or signal voltage.
What can look similar
A cable segment may fail only under electrical interference or load, so a brief continuity check does not completely rule it out.
Repair direction
Correct the established compatibility or addressing defect, or replace a verified failed interface and perform required commissioning.
Verify the repair
Verify node discovery, fault history and all-zone operation without repeat communication errors.
Equipment-specific limits
Some interconnect terminals carry line voltage or line-referenced signals. Wire count, terminal numbers, polarity, shielding and permitted splices are model-specific; do not treat a bus as R/C/Y wiring.
Practice this diagnosis
This cause is a reference topic; it does not yet have a dedicated simulated call. Browse the practice board.
References and applicability
Original HVACSim explanations with manufacturer and instrument-maker references for further reading. These resources support the subject; their model-specific examples are not specifications for every system.
- GREE: GREE communication-fault diagnostic guidanceA GREE-specific example of wiring and board fault isolation; E6 is not a universal code.
- Haier: Arctic Next Gen service manualAW/1U EH2VHD model examples of inverter, motor, sensor and circuit diagnostics; obtain the installed model manual.
Editorial review: 2026-09-29. Verify the current manual for the installed model.