Cerbo GX corrupted, reinstalled, worked for a couple of days and now reboots

Hi all,

I installed a Cerbo GX in my camper van back in 2002. It worked fine for three years. Then, last week I touched the screen (GX Touch 50) and nothing happened.

Looking at the Cerbo, I saw flashing amber lights in a repeating three flash sequence - fast, fast, slow.

I tried power-cycling, no change.

I tried wiping the configuration (USB stick with blank config), no change.

I tried re-installing (SD card with install image written to it), it sprung into life and found all the attached devices with the exception of my Ruuvi Tags. After some searching, I found the issue with on-board Bluetooth (serial numbers before ā€œHQ2207ā€), ordered a TP-Link dongle and when it arrived, the Ruuvi Tags appeared.

The Cerbo then stayed working for four days. Today it started constantly rebooting. Sometimes the boot process would complete and you’d get, maybe, 5 seconds of uptime before it rebooted and then other times the boot process just hung and the unit did nothing until (presumably) a watchdog kicked in and rebooted it again.

After reading some of the other similar posts here, I can confirm that
a) Unplugging the GX Touch USB cable does not make it stop rebooting,
b) It is not configured to reboot when VRM is unavailable, however when it does reboot, it connects to VRM anyway.
c) It is definitely rebooting (pings fail, screen shows reboot animation etc.)

Given the need to completely re-flash it, I’m assuming that the on-board storage is dead or dying and as I’m just inside the five year warranty, I’m going to have to send it back. I’m posting here, however, just in case anybody has any ideas about what it could be. I don’t hold out much hope though - it’s been re-flashed and reset, so I don’t imagine there’s much else I can try, but…

Thanks in advance of your answers!

Cheers,

N.

1 Like

@NiccyB , you might want to check for water damage before you install the new one. I had a similar problem caused by water damage, and wished I had found and fixed that issue before installing the new unit!

Thank you for the suggestion but it’s in a place where if there was water, I’d have a whole load of other problems!

I think it may be heat related. It only got up to mid-20’s today, but now the temperature’s dropped off a bit, it’s stopped rebooting and seems to be working properly again. I wonder if this is related to the Bluetooth over-temperature problem. I did have a good feel around it when it was rebooting in case it was obviously overheating, but it was just slightly warm to the touch - certainly nothing I’d worry about.

I’ve ordered a new Mk2, so we’ll see how that goes and when this one’s repaired/replaced at least I’ll have a spare.

N.

A lot of mine are running in temperatures over 40, so if it’s heat related it’s still something Victron should replace. Hopefully you’ll be able to figure it out! Let us know what you find.

1 Like

Hate to be the bearer of bad news.
Electrical gear is all based around 25C optimal ambient temps.
The warranty specifically excludes high temps, so it is your responsibility to ensure proper airflow. From the warranty exclusion list:

Use in an inappropriate environment (dust, corrosive vapour, humidity, high temperature, biological infestation, etc.).

Installation or operation issues are not covered in any form, and too many people expect the manufacturer to cover them when a problem has been self-created.

That said, over temp results in constant rebooting of a GX, which would be a log entry on the device itself.

I have the same issue since I updated to the latest firmware today, except that if I unplug my touch 70 device it is stable. I do not have an SD card in the device. The device is brand new.

Hi,

Thank you for your comment, but I’m not sure you understood my post.

The ambient temperature was around 25C degrees (probably a little lower, but let’s say 25). The temperature was not ā€˜high’. There was plenty of air flow in the area, but even if this wasn’t the case (for emphasis, in this case there was plenty of airflow), the Cerbo is a plastic box with no vents and no heat-sink surfaces, so it likely wouldn’t benefit from airflow anyway unless it was really really really hot).

If you’re suggesting that the Cerbo isn’t appropriate for ambient temperatures higher than 25C, then given there’s no form of refrigerated cooling available for it, I’d question why it’s for sale in most of the world.

However, all that aside, it started rebooting again overnight when the ambient temperature was below 20C, so I can rule out temperature as a cause. Looking at it, it seems to go through phases of working for a period and then continually rebooting and then working for a period and then…

Anyway, the new Cerbo has arrived, I’ll get that plumbed in and put the old one on the workbench to try to work out exactly what causes it and if there’s anything in the logs.

N.

The comment wasn’t directed at your issue as it was towards another comment implying if something heat related happens to a GX Victron should replace it. Which is incorrect.

For your issue, there are many reasons a GX can restart, a common one is CPU load. if you ssh to the GX and review the entries in var/log it will report the cause when it has decided to restart itself.

It can also happen with a reboot on comms loss setting - some users forget this is set.
Where cpu is a trigger, it is typically due to modifications - additional drivers like Shelly etc.
If your system is modified, on a current GX version and the new UI, you can check on settings → general → support/modifications.