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
I am experiencing inconsistent read and write issues when using multiple RCC522-RFID modules. The setup includes eight RCC522-RFID modules, all connected with a common MOSI, MISO, and SCLK, but each having its own unique chip select line.
Problem Description
Modules Used: Eight RCC522-RFID modules
Tags Used: NTAG 213
Connections:
Common MOSI(GPIO-10), MISO(GPIO-9), and SCLK (GPIO-11) lines on raspberry pi connected to each RC522-RFID modules.
Individual chip select lines for each RCC522 module
Read Failures: Intermittent failures when attempting to read data from NTAG 213 tags. Write Failures: Inconsistent write operations, where some data writes are not successful or result in corrupted data Additional Information: Scoped MOSI, MISO, SCLK, and CS lines; there is no crosstalk between lines.
Seeking guidance on how to resolve these read and write consistency issues, particularly in environments with multiple RCC522-RFID modules sharing common communication lines. Any insights or suggestions for troubleshooting and resolving these issues would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I am experiencing inconsistent read and write issues when using multiple RCC522-RFID modules. The setup includes eight RCC522-RFID modules, all connected with a common MOSI, MISO, and SCLK, but each having its own unique chip select line.
Problem Description
Connections:
Read Failures: Intermittent failures when attempting to read data from NTAG 213 tags.
Write Failures: Inconsistent write operations, where some data writes are not successful or result in corrupted data
Additional Information: Scoped MOSI, MISO, SCLK, and CS lines; there is no crosstalk between lines.
Seeking guidance on how to resolve these read and write consistency issues, particularly in environments with multiple RCC522-RFID modules sharing common communication lines. Any insights or suggestions for troubleshooting and resolving these issues would be greatly appreciated.
The text was updated successfully, but these errors were encountered: