Multiple boilers in cascade: communication fault

Larger homes, multi-unit buildings and light commercial spaces sometimes run two or more boilers linked in a cascade: one controller decides how many boilers fire and at what rate as the load changes, and the boilers talk to each other over a wired network. The group is meant to act like one modulating boiler, with the first unit covering small loads and others stepping in as demand grows.

The wiring and control settings that link the boilers are as much a part of the system as the heat exchangers, and when the network fails the boilers may refuse to start, run at the wrong rates, or fall back to uncoordinated operation. A communication fault often shows up as an alert naming the network, or as one boiler that will not answer the controller.

Read the display on each boiler and write down every alert, noting which boiler shows which code, then look the codes up on this site's brand error-code pages. Note whether the building still heats in some form, such as one boiler running while others stay off, and whether the fault appeared after electrical work or a power event, because network faults often follow disturbances. If the displays themselves disagree with each other, such as one boiler calling while another sits idle, write that down too.

Do not open the control cabinets, unplug network wiring or change addressing and configuration settings; cascade setup is installer work, documented in the manual's commissioning sections. The observations that help are which units are running, what each display says, and when the trouble started.

Network faults have mechanical and electrical causes: a communication wire that has worked loose, been damaged or been run too close to power cabling, a failed communication card or port on one boiler, and a controller that has lost its configuration. Electrical events are frequent triggers, since surges can reset or corrupt the settings that tell the group how to behave.

Firmware and configuration drift cause the rest: boilers in a cascade must share compatible software and consistent settings, and an update, or a replacement unit that does not match the others, can make the network refuse to synchronise. The fault may also be intermittent, appearing only when the group tries to step from one boiler to two, which makes the diagnosis depend on watching the group through a load change.

Call when the cascade shows a communication fault, when some boilers refuse to start while others run, or when the group misbehaves after a power event or after one unit was serviced or replaced. An uncoordinated cascade can leave parts of the building short of heat while the group as a whole looks busy.

Report which boiler shows what, and whether the building heated normally before the fault appeared. Call ROMA Heating & Cooling at 778-909-5731 during business hours; cascade faults are diagnosed from the network and the settings, not from swapped parts.

A technician reads the fault history from each boiler and from the cascade controller, then checks the network link itself: wiring continuity and routing, communication cards and ports, and the addressing and configuration stored in each unit against the manual's cascade section. The group is then watched through a load change to see whether the boilers hand load between themselves correctly.

The fix is whatever the checks prove: reseating or replacing a communication card, repairing wiring, restoring configuration, or updating a unit so the group shares compatible software. Each boiler is confirmed running, and the group is confirmed handing load, before the technician leaves.