The RC522 module stops reading cards after running for a long time, about two weeks.
After pressing the reset button of the ESP32 module, the module started reading cards again.
Is there a way to detect if module is unresponsive, or identify what caused this issue by reading a register in the RC522?
I think that periodically reset the mfrc522 could fix the problem, but I still have not tested this approach.
Affected file(s) or example(s):
DumpInfo.ino
Steps to reproduce:
Let the dumpInfo exemple running for a long period, in my case two weeks.
Test if module is still reading cards.
Observed Results:
No cards were being read, no output in serial monitor when cards were aproximated.
The module started reading cards again when the ESP32 board was resetted.
I already took a look in the issues section but wasn't able to find any similiar issues, but I think this might be a common issue.
Rotzbua
commented
3 years ago
Step 1: Describe your environment
Step 2: Describe the problem
The RC522 module stops reading cards after running for a long time, about two weeks. After pressing the reset button of the ESP32 module, the module started reading cards again. Is there a way to detect if module is unresponsive, or identify what caused this issue by reading a register in the RC522? I think that periodically reset the mfrc522 could fix the problem, but I still have not tested this approach.
Affected file(s) or example(s):
DumpInfo.ino
Steps to reproduce:
Observed Results:
No cards were being read, no output in serial monitor when cards were aproximated. The module started reading cards again when the ESP32 board was resetted.
I already took a look in the issues section but wasn't able to find any similiar issues, but I think this might be a common issue.