( @Matt )
Some questions about GoPiGo3 power management
I have not previously let battery voltage drop below 8v which is when egpg.volt() returns 7.4v on my GoPiGo3. In fact, I usually shutdown with 15 - 45 minutes of power left (egpg.volt() returning 8.1 volts.)
Today I was running without my safety shutdown code thinking that gopigo3_power.py would safely force a shutdown before the 5v rail sags.
Just before my wireless remote shell went down:
- egpg.volt() returned 4.92v
- egpg.get_voltage_5v() returned 4.01v,
- the processor was screaming “THROTTLED!!! = 0x50005”
Q1) Was my SD card at risk of corruption at this supply voltage?
Q2) When does gopigo3_power.py kick in?
Q3) Can too frequent calls or requests from multiple processes to egpg.volt() return erroneous values?
Q4) Can egpg.volt() calls interfere/collide with the GoPiGo3 board supply voltage protection measurements?
root 361 1 0 20:13 ? 00:00:00 bash /home/pi/Dexter/GoPiGo3/Install/gpg3_power.sh root 723 361 0 20:14 ? 00:00:00 sudo python /home/pi/Dexter/GoPiGo3/Software/gopigo3_power.py root 727 723 0 20:14 ? 00:00:00 python /home/pi/Dexter/GoPiGo3/Software/gopigo3_power.py while True: if GPIO.input(22): os.system("shutdown now -h") time.sleep(0.1)
Carl’s last words before the world ended:
********* CARL Basic STATUS ***** 2019-03-31 17:15:35 up 7:24, 2 users, load average: 0.11, 0.05, 0.01 Battery Voltage: 4.92 5v Supply: 4.01 Estimated Life Remaining: 0 h -31 m Processor Temp: 43.5'C Clock Frequency: 600.0 MHz throttled=0x50005 Distance Sensor: nothing within 90 inches Juicer Values: lastReading 5.08 volts num of readings 45 shortPeakVolts 6.60 volts shortMeanVolts 5.84 volts shortMinVolts 5.49 volts longPeakVolts 7.73 volts longMeanVolts 7.24 volts longMinVolts 5.08 volts Traceback (most recent call last): File "./juicer.py", line 110, in <module> packet_write_wait: Connection to 10.0.0.225 port 22: Broken pipe
(longXvolts is the last 5 minutes, shortXvolts is the last 1 minute.)