Arduino library for MFRC522 and other RFID RC522 based modules.

Read and write different types of Radio-Frequency IDentification (RFID) cards on your Arduino using a RC522 based reader connected via the Serial Peripheral Interface (SPI) interface.

Set the UID, write to sector 0, and unbrick Chinese UID changeable MIFARE cards.

This library is compatible to Teensy and ESP8266, but not all examples are available for every board. Also you have to change pins, see pin layout.

The following table shows the typical pin layout used:

There are three hardware components involved:

1. Micro Controller:

• An Arduino or compatible executing the Sketch using this library.
• Prices vary from USD 7 for clones, to USD 75 for "starter kits" (which might be a good choice if this is your first exposure to Arduino; check if such kit already includes the Arduino, Reader, and some Tags).

2. Proximity Coupling Device (PCD):

• The PCD is the actual RFID Reader based on NXP MFRC522 Contactless Reader Integrated Circuit).
• Readers can be found on eBay for around USD 5: search for "rc522".
• You can also find them at several web stores, they are often included in "starter kits"; so check your favourite electronics provider as well.

3. Proximity Integrated Circuit Card (PICC):

• The PICC is the RFID Card or Tag using the ISO/IEC 14443A interface, for example Mifare or NTAG203.
• One or two might be included with the Reader or "starter kit" already.

1. The micro controller and the reader use SPI for communication.

• The protocol is described in the NXP MFRC522 datasheet.
• See the Pin Layout section for details on connecting the pins.

2. The reader and the tags communicate using a 13.56 MHz electromagnetic field.

• The protocol is defined in ISO/IEC 14443-3:2011 Part 3 Type A.
  • Details are found in chapter 6 "Type A – Initialization and anticollision".
  • See http://wg8.de/wg8n1496_17n3613_Ballot_FCD14443-3.pdf for a free version of the final draft (which might be outdated in some areas).
  • The reader does not support ISO/IEC 14443-3 Type B.

This library only supports crypto1-encrypted communication. Crypto1 has been known as broken for a few years, so it does NOT offer ANY security, it is virtually unencrypted communication. Do not use it for any security related applications! This library does not offer 3DES or AES authentication used by cars like the Mifare DESFire, it may be possible to be implemented because the datasheet says there is support. We hope for pull requests :).

• I don't get input from reader or WARNING: Communication failure, is the MFRC522 properly connected?
  1. Check your connection, see Pin Layout .
  2. Check voltage. Most breakouts work with 3.3V.
  3. SPI only works with 3.3V, most breakouts seem 5V tollerant, but try a level shifter.
  4. According to reports #101, #126 and #131, there may be a problem with the soldering on the MFRC522 breakout. You could fix this on your own.
• Sometimes I get timeouts or sometimes tag/card does not work.
  1. Try other side of the antenna.
  2. Try to decrease distance between MFRC522.
  3. Increase antenna gain per firmware: mfrc522.PCD_SetAntennaGain(mfrc522.RxGain_max);
  4. Use better power supply.
  5. Hardware may be corrupted, most products are from china and sometimes the quality is really poor. Contact your seller.
• My tag/card doesn't work.
  1. Distance between antenna and token too large (>1cm).
  2. You got the wrong type PICC. Is it really 13.56 MHz? Is it really a Mifare Type A?
  3. NFC tokens are not supported. Some may work.
  4. Animal RFID tags are not supported. They use a different frequency (125 kHz).
  5. Hardware may be corrupted, most products are from china and sometimes the quality is really poor. Contact your seller.
  6. Newer versions of Mifare cards like DESFire/Ultralight maybe not work according to missing authentification, see security or different protocol.
• My mobile phone doesn't recognize the MFRC522 or my MFRC522 can't read data from other MFRC522
  1. Card simmulation is not supported.
  2. Communication with mobile phones is not supported.
  3. Peer to peer communication is not supported.
• I need more features.
  1. If software: code it and make a pull request.
  2. If hardware: buy a more expensive like PN532 (supports NFC and many more, but costs about $15)

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to http://unlicense.org/

The MFRC522 library was first created in Jan 2012 by Miguel Balboa (from http://circuitito.com) based on code by Dr. Leong (from http://B2CQSHOP.com) for "Arduino RFID module Kit 13.56 Mhz with Tags SPI W and R By COOQRobot".

It was translated into English and rewritten/refactored in the fall of 2013 by Søren Thing Andersen (from http://access.thing.dk).

It has been extended with functionality to alter sector 0 on Chinese UID changeable MIFARE card in Oct 2014 by Tom Clement (from http://tomclement.nl).