We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi !!
I'm trying the pn532.py example : https://github.com/eclipse/upm/blob/master/examples/python/pn532.py
I've just changed line 31 myNFC = upmPn532.PN532(3, 2) to this one to match Respeaker specifications (https://github.com/respeaker/mraa/blob/master/docs/axolotl.md ) myNFC = upmPn532.PN532(0, 0, 0, 0x24)
myNFC = upmPn532.PN532(3, 2)
myNFC = upmPn532.PN532(0, 0, 0, 0x24)
But got systematically this error :
respeaker@v2:~$ python3 pn532.py sendCommandCheckAck: Not ready, timeout Could not identify PN532 Exiting
I'm using a Respeaker Core V2 : http://wiki.seeedstudio.com/ReSpeaker_Core_v2.0/#hardware-overview and this NFC card : http://wiki.seeedstudio.com/Grove_NFC/#grove-nfc-v11
I tried with LibNfc, got no problem to read a tag. What could be the error when using UPM lib ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi !!
I'm trying the pn532.py example : https://github.com/eclipse/upm/blob/master/examples/python/pn532.py
I've just changed line 31
myNFC = upmPn532.PN532(3, 2)
to this one to match Respeaker specifications (https://github.com/respeaker/mraa/blob/master/docs/axolotl.md )
myNFC = upmPn532.PN532(0, 0, 0, 0x24)
But got systematically this error :
I'm using a Respeaker Core V2 :
http://wiki.seeedstudio.com/ReSpeaker_Core_v2.0/#hardware-overview
and this NFC card :
http://wiki.seeedstudio.com/Grove_NFC/#grove-nfc-v11
I tried with LibNfc, got no problem to read a tag. What could be the error when using UPM lib ?
The text was updated successfully, but these errors were encountered: