@cleoqc
I have noticed an interesting artifact with GoPiGo3 on Trixie, that might be a bug.
With Raspberry Pi O/S Trixie installed, using installation method “B”, shutting down the robot doesn’t work as intended.
-
shutdown -h nowcauses an orderly system shutdown and after the O/S is shut down it waits for a button press to shut down the rest of the robot. This process takes from 30 to 60 seconds depending on what is running at the time. -
Pressing the power button causes the robot to power-down almost immediately - NOT performing an orderly shutdown with - apparently - no regard for the filesystem’s integrity or any other necessary shutdown steps.
These systems worked correctly on Buster. They do NOT work on Trixie.
Please advise.
P.S.
I am attaching a modified version of the Trixie gopigo3_power.py that duplicates the correct Buster behavior. (Ignore releasing the “running” pin until the O/S dies.)
new_gopigo3_power.py.txt (1.5 KB)
I would appreciate if someone who knows more about this than I do would examine this and let me know if there is an “official” fix, or should I submit a pull request.