Read fails after some time

[zloKOMAtic]

Hi,

i got two problems.

1. wait_for_tag is not working for me - it just hangs there waiting. However i can read tags after commenting out the wait_for_tag bit
2. After like 40 reads in a row ( not a specific number it just happens after some time ) not tags can be read anymore. It always errors out after rdr.request()

System is a fresh raspian on a raspberry zero w

[Stefan]

Hey @zlokomatic,

can you please check whether #49 fixes the issue for you? Thanks!

[ac-ask]

@layereight I am experiencing these symptoms as well. I tried the patch (I think) but it had no effect. I can double-check soon for you. I think I applied the patch incorrectly, as I am not seeing the same symptoms after applying it.

[Stefan]

@ac-astuartkregor meaning #49 fixes the issue for you now as well? Just asking for explicit confirmation.

[ac-ask]

I believe that to be the case, yes. It's the only significant thing I changed in terms of how my RFID setup works.
Edit: And yes it's working continuously now.

[Stefan]

Happy to hear that.

[Peter Kling]

I ran into a similar problem and the patch from @layereight helped, thanks!

Interestingly enough, the problem does not occur with every RFID tag. I have two different types (tokens and cards). While the tokens work flawlessly without the patch, the cards always result in failing reads when left on the RFID reader. Once the reads start to fail, none of the cards can be read anymore but the tokens can be read. Once a token was read, a card can again be read again (again, resulting in errors when left on the RFID reader for too long).

Anyway, with the patch everything seems to work, thanks again!

[Wyphorn]

same problem. Same fix worked. thank you!

[keans]

Hm, strange with fix #49 the wait_for_tag() blocks only once i.e. until the first time a tag is read. Afterwards there is no waiting for tag i.e. no blocking increasing the CPU usage to 100%.
However, activating #self.irq.clear() in line 399 again makes it work for me on a Pi Zero.