This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hi
i am running venusOS on a raspberry pi 4.
connected is a smartshunt which monitors my solar batteries.
the raspberry pi is powered by main power.
when the battery runs flat the raspberry starts to reboot ever minute or so.
powering the connected bluesmart charger on the raspberry is stable.
could this be a timeout issue of the ve.direct connect to the smartshunt?
what can i do to solve it?
Nothing in Venus OS would cause a reboot except the command from the General Settings menu. I don't believe there is a timer running anywhere that would cause a reboot but there is the reboot on loss of VRM connection.
I would investigate power to the RPI as a possible casue. You are either running an AC to 5 volt adapter or a DC-DC converter off of battery power. If the battery feeding the DC-DC converter is low enough voltage for the converter to shut down then its 5 volt output will also most likely drop causing the PI to shutdown. Then, maybe the batter voltage creeps up and the PI reboots.
the raspberry is powered by ac not the battery, like i mentioned in the starting post.
the network is wired and stable.
the reboots only happen when the battery is flat and there is no response anymore from the smartshunt
See if this is switched on, possibly switch the function off to see if it makes any difference.
that setting is already off on my device
@PVTex Are you using an original victron veDirect to usb cable, or a homemade one?
Possibly there is a ground loop, so if you have other things than power and network, disconnect them and if possible run the pi from a battery powered supply (MAX 5v) and wifi to test. I have experienced a lot of strange things because of this after dozens of mounted pi4s
i have only 2 original ve.direct cables and network conneted.
the power supply is an industrial 5V 10A one the same model i have many rasp running on without problems.
@PVTex ok, if the pi reboots you need to check your log files. If the pi crashes there can be many different reasons that do not appear in the log.
