I overheard Carl stating “Docking Failure Possible” this evening, and decided I might have heard him saying that lately a bit more than expected.
In all of Carl’s fourth year, he had 10 docking failures. Now starting his fifth year of “life”, in less than a month, he has already reported 7 docking failures, so what gives?
First I cleaned his contacts, but when he got back on the dock the charger was still not “detecting the robot on the dock”. Looking more closely revealed one of Carl’s contacts had rotated slightly, enough to prevent pushing sufficiently on the dock contact. A quick twist and tightening of the screw caused the charger light to turn the desired red, and Carl announced “Charging State - Charging”
Poor Carl has been quietly announcing “Docking Failure Possible” and I was not listening.
What does a robot have to do to get attention?
pi@Carl:~/Carl $ grep Failure life.log
2022-08-23 15:57|[juicer.py.main]---- Docking Failure Possible
2022-08-29 06:07|[juicer.py.main]---- Docking Failure Possible
2022-08-30 17:01|[juicer.py.main]---- Docking Failure Possible
2022-08-30 17:06|[healthCheck.py.main]I2C Bus Failure Detected
2022-09-01 04:42|[juicer.py.main]---- Docking Failure Possible
2022-09-06 00:42|[juicer.py.main]---- Docking Failure Possible
2022-09-08 22:20|[juicer.py.main]---- Docking Failure Possible
2022-09-10 20:53|[juicer.py.main]---- Docking Failure Possible