Closed GoogleCodeExporter closed 9 years ago
Original comment by romu...@libnfc.org
on 30 Jul 2010 at 1:27
For the record, I add a note about ATQA collisions here.
When a PN53x chip list tags with colliding ATQAs, it sets this field to 0x0000
before returning the tag information. As far as I could experiment on this, any
tag which is not selected by the PN53x when a REQA command is send will reply
with it's ATQA so since the PN53x cannot handle more than 2 tags
simultaneously, collecting the ATQA of 3 tags with colliding ATQAs is not
possible.
Original comment by romain.t...@gmail.com
on 4 Aug 2010 at 5:57
Fix status. It has not been accepted yet while some tests have been made by
Romuald and I but with no success, and the previous comment should be a good
reason to set the status to Feedback.
Original comment by romain.t...@gmail.com
on 6 Aug 2010 at 9:29
Yeah Romain, I experiment the same issues during my tests... maybe we should
give up about ATQA collision and clean up the code: my lastest test remains in
comment and tag collision detection is not needed anymore. What do you think
about that suggestion ?
Original comment by romu...@libnfc.org
on 16 Aug 2010 at 4:09
I definitivelly agree! Please remove this.
Original comment by romain.t...@gmail.com
on 16 Aug 2010 at 7:07
Done in r533.
Original comment by romu...@libnfc.org
on 17 Aug 2010 at 10:12
Original issue reported on code.google.com by
romu...@libnfc.org
on 30 Jul 2010 at 1:27