Fix [#5]: Register errors are wrong

0x1D properly masks out the error bits in that register not 0x1B. 0x1B caused problems with parity bit error that was not valid in the use case.
ljos · Jan 14, 2015 · d427494 · d427494
1 parent 59d9053
commit d427494
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/MFRC522.cpp b/MFRC522.cpp
@@ -291,7 +291,7 @@ int MFRC522::commandTag(byte cmd, byte *data, int dlen, byte *result, int *rlen)
   clearBitMask(BitFramingReg, 0x80);  // StartSend=0
 
   if (i != 0) { // Request did not time out.
-    if(!(readFromRegister(ErrorReg) & 0x1B)) {  // BufferOvfl Collerr CRCErr ProtocolErr
+    if(!(readFromRegister(ErrorReg) & 0x1D)) {  // BufferOvfl Collerr CRCErr ProtocolErr
       status = MI_OK;
       if (n & irqEn & 0x01) {
         status = MI_NOTAGERR;