Cerbo not storing (all) installation data when disconnected from internet

CerboGX with 3.55 firmware here. “Everything” seems to work ok so far except a few accounting hiccups (Wrong accounting of solar charger in a VE.Bus/VE.Can system · Issue #1450 · victronenergy/venus · GitHub).
However, yesterday ~12:30 I accidentally turned off the ethernet switch the Cerbo is connected to, and through it to the internet/VRM. Cerbo continued to run fine monitoring the system.

Today ~12:00 I turned the eth switch on again, so the Cerbo had internet/VRM connection again. I was expecting the Cerbo to store the data during the connection outage in its memory. And apparently it did - mostly:

However there is a gap of ~ 7 hours yesterday 12:30-19:00, which I am not sure as of why.
If I interpret it correctly, there should be ~1GB of free space, so certainly that should do it
for 24hours?

Does it state how many records are outstanding on the GX?
If it is 0, then it may just be a case of it requiring time to properly sync.

@nickdb It shows 0 on the GX, but how long would that syncing time be? It has been now over 2 hours.

The short answer is that it can vary.
I would be patient and give it some time.

Where can I find that info ?

VRM settings section on the GX.

1 Like

It depends on how many and what components are connected and how the interval is configured.

Fit a micro sd card then you know you will be OK for days with the info stored on the card.

No dice. However, I think it might have been “me”. Probably during the resync of the data I rebooted the Cerbo as it was quite unresponsive. If the records are kept in memory only, or if there is no transaction monitoring (like delete stored records only if rcv ack from vrm), then of course the reboot may have slashed these 7 hours.

If - I assume, but it would make sense - it sends the newest first it would explain why the first 7 hours of the outage are gone. Still, I’d wish for a more robust resync of internally stored data.
I mean my naive reboot could have been some kind of external outage.

Data is written to a dedicated space on either internal or external media. So it shouldn’t disappear, unless the gx had hung up beforehand.

The gx can appear to he unresponsive if it is restarted while purging logs, so always a good idea to just wait, or try ssh to it.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.