RFID module RC522 interfaced to Pico results in various Uncaught Error MFRC522 Request Errors

...btw, cannot see the #XX post...

Did look at some boards hanging around and at the RC522 chip... to try to derive the rational for the sequence of the signals on the pin header. Routing (most of) the (significant) signal lines straight forward to the pin header is a good rational for the signal pin sequence

• RST
  
• MISO
  
• MOSI
  
• SCK
  
• CS/SSN/SDA
  
• IRQ
  
  

as you can take from attached screen shot. Usually there is not much variation... taking a closer you can actually visually trace the routing / traces from the chip pins to the header pins. Take a closer look at your board and you can confirm. Zoom into the attached picture and you the fine, dotted, orange lines marking the routing for MISO, MOSI, SCK, and CS/SSN/SDA, and the yellow ones indicating the pin and pin function silk screen. (I know that you have a different board... but I' confident that it is not a high-tech (4..6 layer) board hat has front and back top planes covered with all ground for RF reasons and 'hiding' the routing of the signal lines in between these two outermost layers...

Something I noticed in many of the usages is connecting the RST to a pin and do a software driven reset before talking to the board... You might do that too. Usually though, an open reset is pulled up by the chip itself. You can take any PICO pin you have left, connect it and use this code:

function onInit() {
var resetPin = <yourResetPinChoice> // for example A0
resetPin.reset();
setTimeout(function(){
  resetPin.set();
  setTimeout(function(){
    // here goes all your code
  }, 100);
}, 10 );

There are better ways to do this for permanent implementation, but it is good enough for figuring out.

Something from your post #5 raises concerns:

... Vdd rail is 3.2v and the 5v rail is 4.8v. I switched USB ports and found all three are 4.8v

Why could you read 4.8V on all three? I hope the VCC (3.3v) pin of the MFRC522 break out board was not a member of all three. This could have fried something... for example happened to with a different device specified for 3.3v, when a bread board cable got loose and hit the 5V (4.8V / USB) supplied rail. Interestingly, only a part of the chip was gone - unfortunately it was the essential one. I still could read/write registers, read the configuration info and chip id, but the core function of the chip was enjoying freedom from commands in lala land... :x[. I hope it is just a misreading of your post.

1 Attachment