Closed marksteward closed 5 years ago
Happened on bell, too, while Jasper was playing with the 16-seg display.
921c72eb8b5a38ec48873ce8c6a64860a5b5ab3f now means we exit when we lose the card reader. We rely on monit restarting us. seems to work?
Now we're using RFUID, the error is:
Feb 12 21:42:33 hamming Doorbot[1483]: CRITICAL Unexpected error during poll: Unable to connect with protocol: T0 or T1. Card is unresponsive.
For reference, as it's not in here yet, you can trigger this kind of behaviour by asking the pn532 to shut itself down (see https://github.com/marksteward/RFUID/blob/master/rfid.py#L363). The only way to fix this seems to be to cut power to the hub, and a Pi rebooting won't work.
Need to look at the ACR to see if it has any pins we could use to reset the pn532.
Refers to old install, irrelevant to any current install
pscsd restarted a couple of times with no luck, and then a second copy of doorbot was started simultaneously. After killing both, replugging the USB and restarting pcscd in foreground mode (after a 5 minute or so wait), it worked again.
It's probably replugging the USB that fixes it, and therefore either Linux or the reader getting into a persistently broken state. Unfortunately, killing pcscd while doorbot's running also triggers the PC01 error, so we need better diagnostics.