Forum › MIFARE general topics and applications › UID vs alternative ID (barcode) and how readers work › Reply To: UID vs alternative ID (barcode) and how readers work
Hello Cath,
I cannot say anything about barcode readers, sorry but this is not my business.
Each NFC device has a unique serial number which is 7 bytes long. This serial number also contains a vendor code. 4 bytes serial number was used for the MIFARE Classic products in the past. But 4 byte is not an option today.
A NFC tag contains memory space which can be used to store more information on the tag, e.g.: internal booking codes, product or catalog IDs, expiring dates etc. Please have a look to this datasheets:
https://www.nxp.com/documents/data_sheet/NTAG213_215_216.pdf
http://www.nxp.com/documents/data_sheet/SL2S2002_SL2S2102.pdf
So, in a real world application you would store the article number on the tag to identify an article. The UID is unique, so the tag could be removed or changed, but the article number will usually not change.
Regards,
The TapLinx team
I cannot say anything about barcode readers, sorry but this is not my business.
Each NFC device has a unique serial number which is 7 bytes long. This serial number also contains a vendor code. 4 bytes serial number was used for the MIFARE Classic products in the past. But 4 byte is not an option today.
A NFC tag contains memory space which can be used to store more information on the tag, e.g.: internal booking codes, product or catalog IDs, expiring dates etc. Please have a look to this datasheets:
https://www.nxp.com/documents/data_sheet/NTAG213_215_216.pdf
http://www.nxp.com/documents/data_sheet/SL2S2002_SL2S2102.pdf
So, in a real world application you would store the article number on the tag to identify an article. The UID is unique, so the tag could be removed or changed, but the article number will usually not change.
Regards,
The TapLinx team
+ 0
|
- 0