Select an NFC tag

The initial tag format selected by the NFC forum is applicable to the widest range of applications and device performance:

Type 1 is based on 3A and is currently exclusively supplied by Innovision research and technology companies (TopazTM). It has 96-byte memory, low cost, and is widely used.

Type 2 is also based on a. Currently, it is exclusively supplied by Philips (MIFARE UltraLight), and the memory is half of the class 1 tag.

Type 3 is based on FeliCa and is exclusively supplied by Sony. It has a large memory size (currently 2 kb) and a high transmission rate (212KB per second), which is suitable for more complex applications.

Type 4 is fully compatible with 3A/B, and many manufacturers produce it, including Philips (typical products such as MIFAREDESFire ). The memory is larger and the read speed is between kilobytes kb and kilobytes KB per second. It is suitable for multiple applications.

It is worth noting that Class 1 and Class 2 tags differ greatly from the memory of Class 3 and Class 4 tags, and thus constitute two categories. There is basically no overlap in various possible application types.

 

Class and Class 2 labels are in the dual state, that is, they can be read/written or read-only (1 ). Category 3 and Category 4 labels are in a single State, that is, they can only be read-only, which is similar to the officially released CD or DVD. This means that only Class 1 or Class 2 can be used in the apps such as the labels included in the mobile phone box mentioned above, because Class 3 and Class 4 labels cannot be customized by users.

Double status

Read/write

For example, users or companies customize tags.

Read-Only

For example, after a user writes data, the user "locks" label to make it "read-only"

------------------

Whether NFC is fully compatible with these devicesWhat about labels?The answer is "YES ". Any NFC tags that comply with the NFC Forum protocol can be compatible with them, and there are still many of these tags! But the larger the storage space, the higher the price.

■ NTAG203 Tag: 137 bytes memory

■ Topaz 512 Tag: 450 bytes memory

Although they are much less than the Mifare Classic 1K labels with 700 bytes of memory, these memory is sufficient for most applications, and these applications only need to write a small amount of information into the labels, enable the tag to open a specific application and store various settings and tasks for the application.

NTAG203 is currently the most popular NFC Forum tag and can be used for most startup tasks. The Topaz 512 tag space is more than enough for business cards, but the price is slightly higher.These tags are called "common" NFC tags because they can be compatible with all NFC devices.

Therefore, if you want anyone to read your tags, NTAG203 or Topaz 512 NFC tags are recommended because they are compatible with all NFC devices. If you are using a Samsung Tectile application, you 'd better not use these two tags, because the memory of NTAG203 cannot meet the space required by Tectile.

How can we know the data size required to write a tag?NFC Smart Q and other NFC applications allow you to write tags (in fact, you do not need to write data into tags) to know the size of the space required to complete a specific task.

So far, only Nexus 4, Nexus 10, Galaxy S4, and Nexus 7 (version 2013) have the compatibility issues mentioned above, however, it is not ruled out that in the future, there will be other devices that do not use the NFC hardware of XP.

------------------------

NFC tag type
1st class tags (Tag 1 Type ):
This type is based on the standard. This type of label can be read-only and re-written, and can be configured as read-only. The storage capacity is 96 bytes, which is used to store URLs or other small amounts of data. However, the memory can be expanded to 2 K bytes. The communication speed of these NFC tags is 106 kbit/s. This type of tag is simple, so it is cost-effective and suitable for many NFC applications.
2nd class tags (Tag 2 Type ):
This type of label is also based on 3A and can be read-only and re-written. You can configure it as read-only. The basic memory size is 48 bytes, but can be expanded to 2 K bytes. The communication speed is also 106 kbit/s.
3rd class tags (Tag 3 Type ):
These tags are based on the Sony FeliCa system. Currently, it has 2 K bytes of memory capacity and the data communication speed is 212 kbit/s. Therefore, class labels are more suitable for complex applications, despite the high cost.
4th class tags (Tag 4 Type ):
This type of label is defined as compatible with and B standards. It is pre-configured as readable, rewritable, or read-only during manufacturing. The memory size can reach 32 KB, and the communication speed is between 106 kbit/s and 424 kbit/s.

NFC tags
Copper coated paper, PET, PVC, etc.
Dimensions can be customized by customers
Four-color printing or blank
The surface form can be waterproof with a membrane, without adding
Special process write url, custom read-only.
Encapsulation chip Tag 1 Type: Innovision Topaz, Broadcom BCM20203
Tag 2 Type: nxp mifare Ultralight/Ultralight C, NTAG203
Tag 3 Type: Sony FeliCa
Tag 4 Type: NXP DESFire, SmartMX-JCOP

 

Refer:

Http://bbs.tianya.cn/post-develop-1194688-1.shtml

 

Mifare Classic 1 k nfc tag compatibility problems-Nexus 4, Nexus 10, Galaxy S4 and 2013 Nexus 7 cannot fully read the tag for the reason http://www.rfid-blog.com /? P = 2247 & lang = zh