Skip to content
Battery fault · All brands

Battery communication fault

Your inverter is reporting that it cannot communicate with the battery — a CAN bus fault, BMS error, or battery not seen on the communication bus. This disables battery operation as a safety measure.

The battery hardware may be perfectly fine. The fault is often in the communication path — a firmware mismatch, a loose cable connector, or a BMS that needs resetting.

Battery hardware is often fine Firmware mismatch is a common cause Do not open battery enclosure
Communication faults often need firmware work

Firmware mismatches and BMS resets usually require remote or on-site engineer access. A diagnostic session identifies the exact cause and the correct fix route.

Book a Remote Diagnostic — from £75 → System repair service

Safety: do not open battery or inverter enclosures. Internal DC voltage is dangerous even with AC supply isolated.

What is a CAN communication fault?

CAN (Controller Area Network) is the communication protocol that most solar battery systems use to allow the inverter and battery to talk to each other. Over this link the inverter sends charge and discharge commands; the battery returns state of charge, voltage, temperature, and cell health data.

When this communication path breaks down, the inverter cannot safely control the battery. As a protection measure, it disables battery operation entirely and raises a communication fault alarm.

The break can be in the physical cable, the communication ports on either device, the protocol version (caused by firmware mismatches), or a locked BMS that isn't responding to communication attempts.

Do not open your battery or inverter enclosures. Battery packs contain high-voltage DC — typically 48V to 400V depending on system type. This voltage is present even when the AC supply is isolated. There are no user-serviceable components inside. All physical inspection of internal components must be carried out by a qualified engineer.

Common causes

Listed from most to least commonly encountered.

Firmware version mismatch

Inverter and battery firmware updated to incompatible versions — typically after a cloud-pushed update that updates one side but not the other. The CAN protocol versions no longer align.

Loose or damaged communication cable

The BMS cable between inverter and battery is not fully seated, has been pulled under tension, or the RJ45 clip has broken. Causes intermittent or persistent communication loss.

BMS protection lock

The battery BMS has entered a protection state — from over-discharge, cell imbalance, over-temperature, or a hard fault — and is not responding to communication attempts.

Incorrect BMS protocol setting

Many inverters require the BMS communication protocol to be manually set to match the battery brand (e.g. Pylon, BYD, GivEnergy, custom). An incorrect protocol setting means the two devices transmit on different 'dialects' and cannot understand each other.

Communication port hardware fault

Less common. The CAN communication port on the inverter or battery has failed — from power surge, physical damage, or hardware defect. Requires component replacement.

CAN bus termination issue

In multi-battery systems, the CAN bus requires correct termination resistors at each end of the daisy chain. Missing or incorrect termination causes communication instability across all batteries in the stack.

What you can check safely

These are the checks you can make without opening any enclosures.

1
Note the exact fault code

Open the event log in your monitoring portal and record the exact fault code and the time it first appeared. Different codes indicate different parts of the communication path. For GivEnergy faults, see the GivEnergy fault codes guide. The code and timing are the most useful information you can bring to a diagnostic session.

2
Check when the fault first appeared

Look at the event log timeline. Did the fault appear immediately after a firmware update notification? After a power cut? After a particularly cold or hot period? The timing often points directly at the cause — firmware mismatch, protection trip, or environmental trigger.

3
Check the external communication cable

Without opening any enclosures, look at the communication cable between the inverter and battery — typically an RJ45 cable going into a BMS or CAN port on the side or bottom of each unit. Check it is firmly plugged in at both ends and hasn't been disturbed. A partially seated connector can cause persistent faults.

4
Perform a controlled power cycle

Turn off the inverter via its AC and DC isolation switches. Turn off the battery using its own shutdown button or circuit breaker. Wait 2 full minutes. Turn the battery on first, wait 30 seconds, then turn the inverter back on. Allow 5 minutes for the communication to re-establish. Check whether the fault has cleared in the portal.

5
Check the battery's own status lights

Look at the battery unit itself for status LED indicators. A red or amber light on the battery (separate from the inverter) suggests the battery BMS has its own fault or is in a protection state. Note what colour and pattern of lights you see — this informs whether the battery needs a BMS reset rather than a communication cable fix.

Frequently asked questions

The inverter can no longer communicate with the battery's BMS over the CAN bus or RS485 link. The battery hardware may be fine — the fault is in the communication path between the two devices. The inverter disables battery operation as a protection measure until communication is restored.

The inverter's response — disabling battery operation — is a protection measure. The system should continue generating to the grid or house loads. Do not attempt to open battery or inverter enclosures. If you see physical damage, smell burning, or the battery feels hot, isolate the system and call an engineer immediately.

Yes — this is one of the most common causes. An over-the-air update that updates the inverter but not the battery can cause protocol incompatibility. Resolving this requires updating the battery firmware to the compatible version, which typically needs engineer access.

Intermittent faults are usually caused by a loose communication cable connector, a connector that is partially seated, or a faulty port. Temperature cycling can cause connectors to expand and contract, making faults appear at certain times of day. Check all external cable connections are firmly seated.

The safe self-help steps are: recording the fault code, checking external cable connections, and performing a controlled power cycle. Firmware updates, BMS resets, and internal component inspection require qualified engineer access. Do not open battery or inverter enclosures.

Book

Need help diagnosing this fault?

Communication faults are one of the more complex fault types — the exact cause determines whether it is a cable fix, a firmware update, or a hardware replacement. A remote diagnostic session reviews your event log, firmware versions, and fault history to give you a clear answer.

Independent — not affiliated with any manufacturer
Remote session from £75
Written report included

By submitting you agree to be contacted about your enquiry.