AZ-DF-S01
Monza R6-P + NTAG213 Dual-Frequency Tag, AZ-DF-S01
- Chips (UHF + HF)
- Monza R6-P + NTAG213
- Antenna size
- On request
Tag family
Short-range phone interactions and dedicated HF workflows, matched to the right chip protocol.
NFC and HF RFID tags operate at 13.56 MHz, but frequency alone does not establish compatibility. The protocol and NFC Forum tag type determine which reader or phone can communicate with the chip. This collection covers NTAG213 and MIFARE Ultralight EV1 designs using ISO/IEC 14443-A and NFC Forum Type 2, plus ICODE SLIX and SLIX2 designs using ISO/IEC 15693 and NFC Forum Type 5. Select the protocol your system supports before comparing antenna shapes or ordering formats.
For consumer interactions, an NFC phone can read a compatible tag at short range. A common payload is an NDEF record containing a web address, which can point to product information, registration or a brand-owned verification service. The tag stores the data you encode; it does not automatically create an authentication platform. If anti-counterfeiting is part of the project, define how the identifier, server-side validation and physical packaging work together rather than assuming a static URL prevents copying.
Dedicated HF readers are often used for library circulation, pharmaceutical items and document workflows. ICODE designs should be matched to the ISO 15693 system in use, including its inventory and data requirements. Do not substitute a phone-oriented Type 2 chip simply because both chips work at the same frequency. Different chip families also provide different user-memory capacities and features, so check the relevant datasheet and the amount of data your payload actually needs.
Dry inlay, wet inlay and finished label formats allow the same HF antenna design to fit different converting processes. A wet inlay works as a sticker; a finished label adds a face stock for printing. The antenna area, the reader’s antenna and nearby material influence reading behaviour. Validate phone models or dedicated readers with samples applied to the intended object. Share the payload, locking policy, available footprint and surrounding materials so the sample configuration reflects the final application. Confirm the encoding and the user experience before volume production.
Read distances are reference values; validate on your own items and reader setup.
Showing 15 of 15 products
AZ-DF-S01
AZ-UL-S01
AZ-UL-S02
AZ-UL-S03
No product matches these filters.
Ask an engineer for a custom optionShare target devices and the longest content to be written for protocol and data review. Use the catalogue as a starting point; confirm the actual chip, dimensions and supply construction before quotation.
| Protocol & target devices | Chip or system protocol, phone models and OS versions, reader and application versions. Describe the tap, dedicated read/write or inventory workflow and the expected display or action. |
|---|---|
| Data type & complete content | For NDEF, supply record types, order and complete payloads, including the longest URL, serial identifier and query parameters. For raw HF memory, supply field and address mapping. Identify the target application and service owner. |
| Chip & usable capacity | Confirm the actual chip, supply/lifecycle status and usable area for its format. Count the complete encoded bytes. For NDEF, include record and applicable storage-format overhead such as TLV; check user memory and available NDEF space separately. |
| Encoding, mapping & access duties | Assign data supply, encoding, unique-content/item/printed-ID mapping and read-back checks. Use the actual chip’s datasheet to agree rewritable areas, access protection or locks, the operator and approver. Apply settings after sample validation. |
| Mounting, printing & environment | Item and packaging materials, curves, metal or foil, available footprint, position and environment. Supply artwork, print equipment and requirements for dry/wet inlay or finished label construction, adhesive and rolls. |
| Samples, quantity & acceptance | Sample quantity, expected volume and target date. Agree separate criteria for content read-back, device actions, unique mapping, access state, print and adhesion. Cost and delivery terms are confirmed in the quote. |
Define the expected result on each target phone or reader, then validate on the actual item. Keep early samples rewritable; approve content and workflow before applying the agreed lock settings.
Record actual chip, SKU, lot and sample identifier; confirm format and capacity. Encode the longest planned content using the approved data rules. Keep the expected message or raw bytes and the mapping to item and printed identifiers.
Apply samples to the final item or packaging and record position, orientation and conditions. Repeat reads on each target phone or reader with the named application. Check the full message, identifier mapping and expected action; for a URL, check the page actually reached. Record print and adhesion separately.
After content, device workflow and mapping pass review, approve and apply access or lock settings using the actual chip’s datasheet. Check the effect on agreed validation samples first; confirm the scope before any irreversible lock. Read back again and check the intended write restrictions. The reviewer signs each acceptance criterion.
Check NDEF format, device handling and chip access settings separately. NTAG21x is a chip-family example; the selected chip’s datasheet determines the final configuration.
Section 2.1 describes NDEF message and record structure; section 3 explains differences in mobile-platform handling of tag content.
Section 8.5 separates memory areas, CC and lock bits; section 8.8 covers password access protection. Check these settings for the specific chip.
Use editable worksheets to prepare specifications and test results for selection, quotation and sample approval before volume orders.
Record the application, materials, dimensions, equipment, rolls, printing, encoding and purchasing requirements. Leave undecided specifications blank.
Excel (.xlsx) · English / 中文
Document the actual equipment and test conditions, read counts, unintended reads, and print and encoding checks. Record acceptance separately.
Excel (.xlsx) · English / 中文
Each Excel workbook contains English and Chinese worksheets. Complete one worksheet and keep the file for later comparisons.
Email completed worksheets to our sales team, or paste the key requirements into the inquiry form.
sales@antenza.comPrepare the complete payload, device models, item photos and read/write requirements to review candidate chips, supply construction and a sample plan.
Share surface, read distance, chip preference and volume. We shortlist tags that fit.
Receive sample tags of the shortlisted designs to try in your own setup.
Test on your items, readers and printers. We adjust chip, size or format if needed.
Volume production with 100% inline electrical test, then export shipping.
Compare NTAG213, NTAG215 and NTAG216 by actual NDEF size. Check usable memory, locking and finished-tag performance before requesting NFC label samples.
Build an NFC brand-protection brief around threats, tag security and a verification service. A copied URL or static UID is not proof of authenticity.
Compare RFID frequencies by reading workflow, phone compatibility and tagged material. Choose a practical shortlist before testing tags on your items.
Talk to an RFID engineer
Send the surface, read distance and volume. An engineer replies within 24 hours with a recommendation and a sample plan.
Email us: sales@antenza.com