Open amrbt opened 3 years ago
Possibly related to #666.
With #678 applied on top of 42de50f2b7bd4c43e3b92f5c9d6a996fd5300e4f:
Please note that the device appears to be working just fine with pcscd
and https://github.com/Flowtter/py-acr122u:
However, shutting down the daemon doesn't seem to be "resetting" the device as it just goes into timeout upon relaunching, with the green LED stuck.
I acquired another seemingly identical device, this time with a mini CD included. Here's the SDK that is provided: ACR122U_SDK.zip
The problem is that this other device works just fine with #678 applied. I wonder whether we're dealing with a defective and/or fake chip batch...
Alternatively, it could have different factory settings. On the device that is working the LED never turns on, on the other one it's red and turns to green when it detects an NFC tag.
Is the mentioned error resolved? I'm experiencing the same issue.
Same problem here. I've tried using my ACR122U on 4 diffirents OS, 2 different machines:
All with the same problem, "error libnfc.driver.acr122_usb Wrong reply" Hopefully the problem comes from the device and getting another one will fix my issue.
Update: I've bought a new one and I don't have the error anymore. Either the other guy sold me a fake or it was damaged.
Could you send here a picture of the device's back, please?
Could you send here a picture of the device's back, please?
Same back as the old one I had
Interesting... in that case there may be no easy way to determine whether a specific reader is going to work.
Hello!
I'm stucked at this point with the libnfc 1.8.0 and do not find information about this error: