I've been asked to add more details about the dirty experiment we did: I would like to keep clear that I don't know if reading an NFC Tag with a Mifare Ultralight RFID reader is a supported feature/standard: I just tried, and it worked. So, if you plan to write the NFC tag with a RFID reader/writer, and the read it back with a smartphone, then you need to work out the data format standard used to define the kind of data, the string termination/size, and this kind of things. I don't know how NFC Tag delimit the string/data, but the Galaxy S4 knew that there were just X bytes of data on the NFC tag. We programmed the NFC tag with a Samsung Galaxy S4, then we read it with a PC+RFID reader, then we wrote some data on one page of the nfc tag with the RFID reader, then we re-read the NFC tag with the Galaxy S4. So it seem that the memory effectively accessible with a RFID ISO 14443-A Mifare Ultralight reader amount to 4*12 bytes = 48 Bytes. With this setup we seem to be able to read (and write) only the first 16 pages of the NFC tag, the first 4 pages seem to be reserved, so it seem that the usable pages range from 4 to 15 (zero-based page number). The NFC Tag used are NFC NTAG203 Type 2, with 137 bytes of usable memory. We used a RFID reader able to read the ISO 14443-A standard, the reader has been configured to read Mifare Ultralight. Keep in mind that this is some 'dirty' experiment done 'as is' in a few minutes just to see if it's possible. We have been able to use a RFID reader to read an NFC tag. We just did some dirty experiment, and it seem it can be done.
0 Comments
Leave a Reply. |