googlearchive/chrome-nfc

It cannot support ACR122U-A9 on Windows

Closed this issue · 13 comments

peter279k commented

I tried to connect device and ran sample chrome app but their Name,vendorId and productId did not displayed. I saw their vendorId and productId were same as ACR122U's.
What should I do?

cyrus-za commented

I have the same issue. Running on Windows 8.1 and installed the default drivers for the ACR122U-A9.

tutchmedia commented

I have this same issue - Has anyone found a solution?

zyxzhsh commented

好像A9就是不行 谁有解决办法？

beaufortfrancois commented

Can you confirm that you're all running Windows?
If that's the case, you might want to follow #3 discussion.

  • Install Zadig at http://zadig.akeo.ie/
  • Run Zadig
  • Plug your NFC Reader, select it
  • Choose "libusb-win32", click on "Replace Driver" button
  • Unplug your NFC Reader
  • Give another try to the chrome.nfc library.

This trick just worked for me minutes ago on Window 8.1.

  • 👍1
tutchmedia commented

Just tried your steps and after installing the "libusb-win32" driver and removing the device, when i plug it back in it doesn't do anything. Even the light doesn't come on.

Any other ideas?

beaufortfrancois commented
  1. Can you tell me which version of Window you're running?
  2. If you no longer see the red light up, I believe this means Windows is no longer taking control of the device, which is a good thing since it should let Chrome take over this device.
  3. "It doesn't do anything" doesn't help me much. Do you run the sample app or do you run the library by yourself in a chrome app?
  4. Did you have a chance to try the ACR122U-A9 device on another device (MacOS, Linux, ChromeOS)?
gregoryhenry commented

Hey Francois,

Greg here. I just tried the Zadig 'fix' on my windows 7 64-bit machine with no luck. I tried running your sample app with it after I replaced the driver with the 'libusb-win32' version.

It does show in my Windows Device Manager as a libusb-win32 device, FYI.

I will test it on the Pixel when it arrives and see if it works. I'll document my findings in this issue so we can have it for future reference.

Thanks for looking into this,

gregoryhenry commented

Hey Francois,

Me again. The ACR122U-A9 device works on Chrome OS using your sample app.

Thanks,

Greg

jarios86 commented

Hi everyone!!

I use ACR122U-A9 and I have tried to test the sample app in chrome, but it doesn't work. In the Device windows on the chome.nfc app, name, vendor ID and product ID are empties. The red light is on and it sounds when I pass a nfc card near the device.

I have tested this device from other apps and it works fine.

Could anyone help me?
Thanks,
Antonio

jordaofranca commented

Just tryed from ubuntu, and windows, and its not working.

rene1997 commented

for me zadig works great on windows 10. After installation make sure the check-mark at
options> list all devices is on. And follow the steps of francios.
If you don't see the led after all, you can open the reader from your chrome application.

shahbazali commented

Hi @beaufortfrancois

Would you please help, how to get Card Type & UID ? in my business logic i wants to check either its a card or emulated phone? if its a card i need its UID, if its a phone i need NDEF for the Emulated Phone.

Looking Forward.

beaufortfrancois commented

@shahbazali Can you file a separate issue for that please?