RV Tech · Power

The fault that started all of this

An inverter that tripped on every compressor start, a corroded lug hiding in a cable run, and how the cable became a sensor.

The MultiPlus tripped on "low battery" every single time the air conditioner compressor kicked on. With a full bank. It was not the batteries.

Not the battery — and not really the cable either

The battery run was dropping roughly 1.5 V under the compressor's ~135 A inrush — enough to pull the voltage at the inverter's own terminals below its low-voltage cutoff while the battery itself sat happily at full charge.

The obvious reading was "undersized cable", and that is what we assumed at first. It was wrong. The run was 4 AWG rather than the 6 we thought, and more importantly the copper was only about half the problem. The rest — roughly 2.6 mΩ of it — was sitting in one corroded connection where a 4 AWG cable landed on the bus bar.

Put a number on what that means. At 125 A, 2.6 mΩ in a single lug is 0.33 V dropped and 41 watts of heat being dissipated inside one connector. And it is self-accelerating: heat grows the corrosion, corrosion raises the resistance, higher resistance makes more heat.

The rebuild replaced the run with 1/0 and cleaned the joint. Both mattered; the joint mattered more.

If your inverter trips on startup surges, meter the DC voltage at the inverter's terminals during the surge — not at the battery. Then find out where along the path the voltage is disappearing, because a bad joint and a thin cable look identical from the ends.

Read the full battery upgrade →

Now the cable is a sensor

Rather than trusting that the repair holds, Home Assistant continuously computes the resistance of each battery cable run — voltage drop divided by current, in milliohms. A corroding lug or a pitted connector now announces itself as a slowly rising number, weeks before it can strand anyone.

10.7 mΩWhile broken
2.85 mΩAfter rebuild
3.04 mΩSecond pack

It only computes above 40 A. A voltage drop measured at 5 A is mostly rounding error wearing a convincing costume.

Home Assistant DC path resistance card under load, showing branch resistance in milliohms and voltage falling across each sense point
Mid-measurement, with the air conditioning pulling 87 A. The voltage falls as you move along the path: 13.13 V at the first pack's cells, 13.00 V at the shunt, 12.84 V at the inverter's terminals. The branch figures at the top come from the cells-to-shunt span divided by that pack's own current — (13.13 − 13.00) ÷ 42.8 A gives 3.04 mΩ — not from the full cells-to-inverter drop, which spans two separately measured sections. The negative return declines to answer at all because solar was injecting 15.5 A into the middle of it.

Cell spread, with a diagnosis attached

An alert fires if either pack's cell spread holds above 50 mV for half an hour — it sits around 2 mV at rest. The alert names the weakest cell, because the pattern is what matters. If the same cell is repeatedly the outlier under comparable charge, temperature and current, that points at a persistent imbalance, a sense-path problem, or a weakening cell — run the manufacturer's balancing procedure and escalate if it persists. If the identity wanders at small spreads, that is ordinary measurement variation. A single reading tells you very little; spread under an 87 A discharge means something different from spread near the top of charge.

Home Assistant rows showing cell spread of 3 and 4 millivolts for the two packs, with the weakest cell identified in each
At rest: 4 and 3 mV against a 50 mV threshold. Note the two packs name different weakest cells — and which cell they name moves between readings. At this spread that is noise, not a finding. The value is in whether a pattern holds over weeks, which is why the alert waits half an hour before believing anything.

"Your bank never actually finished charging"

If the effective charge voltage limit drops below nominal while current is actually flowing in, Home Assistant says so and names which of the two packs is holding the bank back. Without that, you simply stop reaching a full absorption cycle. Nothing alarms, your state-of-charge calibration quietly drifts, and balancing suffers for months.

Home Assistant rows showing effective charge voltage limit at 14.05 volts, both packs requesting 14.05, and the system ceiling at 14.40
Both packs are asking for 14.05 V and the system would happily allow 14.40. That 0.35 V gap is not something throttling the bank — it is the limit the battery driver is reporting on the packs' behalf, and it is why the alert triggers below 14.0 rather than comparing against the ceiling. Compare against the ceiling and it would fire constantly and mean nothing. A managed battery lowering its own limit is normal behaviour; what is worth knowing is when it drops further than usual while charging.