In the file odf_SL_plugin.err this message appears continuously: Data has been successfully received, fatal condition resolved. No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data. This is a fatal condition and should be investigated if this condition persists!
And with this command: zgrep -a -i “Under-voltage detected!” /var/log/syslog*
I get this: /var/log/syslog:Dec 29 13:10:05 raspberryshake kernel: [70691.417278] Under-voltage detected! (0x00050005) /var/log/syslog:Dec 29 13:10:13 raspberryshake kernel: [70699.737295] Under-voltage detected! (0x00050005) /var/log/syslog:Dec 29 13:10:25 raspberryshake kernel: [70712.217310] Under-voltage detected! (0x00050005) /var/log/syslog:Dec 29 13:11:17 raspberryshake kernel: [70764.217652] Voltage normalised (0x00000000) /var/log/syslog:Dec 29 13:11:28 raspberryshake kernel: [70774.617807] Voltage normalised (0x00000000) /var/log/syslog:Dec 29 13:11:40 raspberryshake kernel: [70787.097923] Voltage normalised (0x00000000)
I can access the Raspberry Pi remotely through a router via VPN, but at the moment I cannot go to the place where it is located.
The gap problems started a week ago. Before that date, it worked fine.
According to the log files, there’s low voltage, but the device is connected to a solar panel, batteries, and a DC-DC converter. I’m communicating with the Raspberry Pi via VPN through a router that operates on 12 volts.
Unfortunately, the device is in a rural area, and I can’t access it for a few months.
Is there anything I can try remotely to troubleshoot this?
Give the additional details, as my colleague stated, all symptoms point to a newly developed power instability. We can see that by the Raspberry Pi detecting repeated under-voltage events, which in turn causes the Shake MCU to stop transmitting temporarily, resulting in gaps. This is almost certainly related to the solar/battery/DC-DC chain rather than software.
A system can work fine for months and then fail without any configuration changes because of:
Battery degradation (which can be common after seasonal changes)
Solar charge controller behavior changing with daylight length
It’s even possible that nothing has been “broken”, per se, and just that the voltage margins that were present before are now disappearing, going below the required 5.1V value.
There’s not much that can be done remotely in this case, as a permanent fix will require on-site power measurements and likely component maintenance/replacement/update.
