You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when waiting for a tag, the task is put to sleep for 100ms and then activated again. The MFRC522 module has a IRQ pin and we could use an interrupt when the tag is present.
The text was updated successfully, but these errors were encountered:
Thank you for the comment. I recall from past research that implementing interrupt-driven tag detection with the MFRC522 can be challenging due to certain limitations, so I initially opted for polling. I will revisit the details to assess if there's a viable way to integrate interrupt handling in the current setup.
Currently, when waiting for a tag, the task is put to sleep for 100ms and then activated again. The MFRC522 module has a IRQ pin and we could use an interrupt when the tag is present.
The text was updated successfully, but these errors were encountered: