-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
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
🐛 | RC522 irq not working properly #2387
Comments
Can you post the log here? |
the error.log is empty. the app.log1 showing the delay between reading a card beeing in place all the time:
and after the change
|
Just to understand your problem: could you also post your As I don’t have a rc522 reader, others may have more experience. |
I use a fresh system |
To clarify: |
Can confirm, I have the same issue with a fresh install from master on a Raspberry 3B+ with RFID-RC522 connected to the default pins. It hangs at If I comment out that line, tag IDs get read. |
Did it work correctly beforhand on the 3b+? 9month ago the rc522.py library was updated to include a timeout during |
i addad a fix with an additional config param |
Unfortunately with |
From my point of view the original problem is tracked in #2373 |
Version
3.5.3
Branch
"future3/main", "v2/main"
OS
Bullseye lite 32bit
Pi model
Zero 2w
Hardware
Mfrc522
What happened?
The Reader is reading just from time to time, so it sometimes takes a looong time to read a card. Sometimes its fast.
I started having this issue after upgrading to a zero2 with some v3 Version half a year ago. Now i found the time to dig into it. Restarting with a plan v2 Version. Still haveing the issue.
What I tied:
Checking the soldering -> unchanged
Stopping almost all jobs -> unchanged
Starting daemon by hand -> rst pin already in use -> change to unused -> issue persists
Using my previous Version of phoniebox v2 from. 2 years ago -> issue persists
trying v3 with bullseye instead of bookworm -> issue persists
During that time I got the feeling the irq is not working.
Changing irq pin -> issue persists
Reading irq pin by hand -> interrupts appear randomly -> changing mfrc522 board -> interrupts appear randomly -> issue persists
Changing cables - issue persists
I got the feeling that for some reason, the irq is not working (maybe anymore) as planned by the designer of the underlying rc522.py library
Using another library without irq -> uid is read at hand
Digging into the Reader component of phoniebox again, I commented out the line "self.waiting_for_tag()"
Now I directly get the uid. -> ISSUE SOLVED
However, y am I the only one with this issue?
Will it cause more trouble?
Should an option "skip_irq" for rc522 readers be integrated.
Maybe someone has the time and hardware to dig into it.
Logs
No response
Configuration
No response
More info
issue solved but see above
The text was updated successfully, but these errors were encountered: