nfcpy

Listen.py PN532v1.6 at /dev/ttyAMA0 timeout waiting for ACK

Asked by Pacific Redwood on 2015-11-17

Greetings.
Many thanks for this tool. A couple issues on RPi B+ running a Sunfounder with PN532 chip (nfcpy v10.2)

Success:
pi@raspberrypi ~/nfcpy/trunk/examples $ python tagtool.py --device tty:AMA0:pn532
[nfc.clf] searching for reader on path tty:AMA0:pn532
[nfc.clf] using PN532v1.6 at /dev/ttyAMA0
** waiting for a tag **
Type2Tag 'NXP NTAG216' ID=04FDE39A793280

Fail:
pi@raspberrypi ~/nfcpy/trunk/examples $ python listen.py tt2 --device tty:AMA0:pn532
687 ms [nfc.clf] searching for reader on path tty:AMA0:pn532
1407 ms [nfc.clf] using PN532v1.6 at /dev/ttyAMA0
4081 ms [nfc.clf.pn532] input/output error while waiting for ack

Fail:
pi@raspberrypi ~/nfcpy/trunk/examples $ python listen.py tt2 --device tty:AMA0:pn53x
859 ms [nfc.clf] searching for reader on path tty:AMA0:pn53x
1031 ms [nfc.clf.pn53x] pn53x is not a driver module, use pn531, pn532, or pn533
no device found on path 'tty:AMA0:pn53x'

Question information

Language:
English Edit question
Status:
Answered
For:
nfcpy Edit question
Assignee:
No assignee Edit question
Last query:
2015-11-17
Last reply:
2015-11-25
Stephen Tiedemann (stephen-tiedemann) said : #1

Thanks for the report. I could reproduce this with a USB converter and fixed by a one millisecond delay when cancelling the timed-out pn53x listen command. Would be nice if you could verify with your setup (the tty:AMA0 typically runs at 115.2 kbps compared to tty:USB at 922.6 kbps). The fix appeared on trunk revision 267, just grab latest.

Can you help with this problem?

Provide an answer of your own, or ask Pacific Redwood for more information if necessary.

To post a message you must log in.