Hi, I’m getting an issue repeatedly with an UR10. The robot was left ON, but next day we found it off. When we tried to turn on the robot polyscope gets stuck at boot. The only solution was to reinstall polyscope and our programs. We see power button pressed at the end of the log in /root/log_history.txt :
3.5 :: 0002d19h37m26.071s :: 2024-04-19 15:44:43.532 :: -3 :: C0A0:7 :: null :: 1 :: headsetcal_2023_10 :: Program headsetcal_2023_10 started :: null
3.5 :: 0002d19h37m52.625s :: 2024-04-19 15:45:10.059 :: -3 :: C0A0:7 :: null :: 1 :: headsetcal_2023_10 :: Program headsetcal_2023_10 stopped :: null
3.5 :: 0002d21h53m06.517s :: 2024-04-19 18:00:24.063 :: -3 :: C0A0:7 :: null :: 1 :: headsetcal_2023_10 :: Power button pressed: headsetcal_2023_10 :: null
******** Log end (2024-04-19 18:00:25) ********
Is it possible that someone pressed the button (while the robot was idle) and it caused the kind of corruption that requires to reinstall polyscope? This is not the 1st time that we need to reinstall polyscope, and it’s becoming a cumbersome process that we have to do every 2-3 weeks due to the same problem above. Is there a good way to track down this failure so that we can avoid it?
The system shouldn’t get that corrupted from a “wrong” shutdown. Maybe you could try replacing the system memory (CF card or USB drive)? It isn’t too expensive and if you have to reinstall PolyScope anyhow… 