Global Link 520 and Blue Smart IP22 Charger 12/30 (1) issues after loss of shore power

Bit of a niche one this but curious if anyone else has run into similar grief.

Running a Global Link 520 alongside a Blue Smart IP22 12/30 on the boat, and I keep getting weird behaviour when shore power drops — either at the marina or when I'm testing off-grid running. The IP22 seems to take an age to properly hand off, and occasionally the GL520 just... loses the plot. Shows incorrect state of charge for a good while after.

My suspicion is it's a VE.Smart networking sync issue between the IP22 and my SmartSolar MPPT 100/20 — the chargers aren't playing nicely when one source disappears suddenly. Anyone using the Victron Connect app seeing similar discrepancies in the data after a shore power drop?

I know Victron's ecosystem is supposed to sort all this out automatically but in practice it doesn't always feel that seamless. Particularly when the battery is mid-absorption and then shore power yanks away — the MPPT seems confused about where to pick up.

A few things I'm considering:

• Checking VE.Smart network assignments in the app
• Adjusting the re-bulk offset settings
• Whether the GL520 firmware is actually current (it's been flaky before)

Running Fogstar Drift lithium so the BMS cutoffs add another layer of complexity if charging gets interrupted badly.

Anyone had this sorted properly? Feels like there should be a clean answer but I'm going round in circles with it. Would be especially interested if anyone's using a similar multi-charger setup on a narrowboat or liveaboard situation.

@BMS_Geek you've cut off mid-sentence but I'll have a stab at where this is going — shore power dropout causing the GL520 to lose comms with the IP22 and either the charger hanging in absorption or dropping to storage mode prematurely?

Seen this on a similar setup. The GL520 relies on VE.Direct polling and when mains drops, the IP22 resets its internal state. On reconnect, the GL520 doesn't always re-initialise the handshake cleanly — particularly on firmware prior to v2.19 on the 520 side.

Worth checking:

• GL520 firmware — update via VictronConnect
• VE.Direct cable seating — boats vibrate, connections work loose
• Charger algorithm setting — if it's on Li preset, dropout behaviour differs significantly from AGM

What battery chemistry are you running? That'll change the diagnosis considerably. Also, is this a single-bank setup or are you feeding multiple banks through the IP22's single output?

@BMS_Geek the IP22 going into a sulk after shore power drops is basically a Victron rite of passage — check whether the GL520 is sending a false "bulk complete" signal via VE.Direct that confuses the charger's state machine on reconnect.

@BMS_Geek yeah the GL520 loses comms briefly when shore power drops and the IP22 doesn't always recover cleanly from that — seen it on my motorhome setup.

The fix that actually worked for me: go into VictronConnect and manually set the charger back to "charger only" mode, save it, then switch back to your normal profile. Forces it to re-initialise properly.

Also worth checking your VE.Direct cable isn't loose — vibration does them in over time, and a dodgy connection makes the whole thing flaky.

@RetiredSquaddie is probably right about the GL520 side of things too. The two issues can compound each other and make diagnosis a nightmare.

Hey @BMS_Geek, worth checking your VE.Direct cable connection between the GL520 and the IP22 — I had almost identical grief on my narrowboat and it turned out the charger wasn't properly re-initialising after the comms dropout @OffGridMax mentioned. What sorted it for me was enabling the "Charge current control" input in the IP22 settings via the Victron Connect app, which let the GL520 reassert control more cleanly on reconnect. Also double-check your AC input current limit settings haven't been defaulting to something daft after the dropout. If you're on an older firmware on either device, definitely update both — there were some known handshaking bugs patched a good while back. What firmware versions are you running? Might help narrow it down.