NFC tags unique ID -


i'm developing system including nfc tags , android phone , using unique id of nfc tags . don't know differences between 4 types nfc tag . i've found :

"nfc-compatible tags can of following technologies/standards , each of them has different notion of id:

nfc tag1 : topaz/jewel nfc tag2 : mifare ul (iso14443a-3) nfc tag3 : jis x 6319-4 (felica) nfc tag4 : iso14443-4a or iso14443-4b tag 

there unofficial support of mifare classic cards nfc tags. , each of them define identification number.

  • topaz/jewel has 4-byte id
  • mifare ul has 7-byte uid
  • mifare classic has 4 or 7-byte uid
  • felica has 8-byte id
  • iso14443-4a has 4, 7 or 11-byte uid
  • iso14443-4b has 4-byte pupi

do tests nfc-list, you'll see comes out depending on used tag. , code, see code of nfc-list.c how ids retrieved , displayed."

is true , thera else ? can me ?

just bits consideration:

topaz / juwel tags broadcom (previously innovision) getting hard find. seems broadcom no longer supporting them.

the mifare classic not included in nfc standard. devices protocol stack nxp (all android 4.1x) support them anyway, popular, because of large memory. since android 4.2 (e.g. nexus 4 or nexus 10) nfc stack broadcom , mifare classic ist not supported anymore.

felica tags hard find.

so safe route tags mifare ul or nxp ntag chips.


Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -

node.js - Bad Request - node js ajax post -