The anti🚫-derailment🚃 & thread🧵 hijacking🔫 thread🧵 ⁉

As usual! ^^

Yeah, had to do the same here, but then it borks up my other readers (i.e. I need to manually start them, and that does bork up the ACR122U).

I’ve just given up on that reader for Linux. or most things with enforced PCSCD stuff. =/

That error seems similar to one I used to encounter even on older revisions.
repeatedly calling the ACR to do stuff over short intervals seemed to always lead it to time out after a while (and not recover even restarting the script).

I tried many things but the best results I had were from AUR’s version of nfcpy wich goes down the pyserial route instead.
But even then ACR122U was still flaky, so I switched to a Teensyduino connected to an Adafruit’s PN532 and got much happier.

1 Like