Issue NFC TagWriter Mass Encoding UID and Counter Mirroring failing on NTAG 21x CSV Importg

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Issue NFC TagWriter Mass Encoding UID and Counter Mirroring failing on NTAG 21x CSV Importg

441 Views
ptfg
Contributor I

I am experiencing a critical issue with the NFC TagWriter App when using the "Write from CSV" (Mass Encoding) feature with NTAG 213 and 216 tags.

While manual configuration works for single tags, the batch process via CSV fails to correctly trigger hardware mirroring bits.

Main Problems Observed:

  1. Static Data: Even when "UID mirror" and "Interaction counter mirror" columns are set to "yes" in the CSV, the app writes the placeholder (00000000000000) as static text. The hardware mirror bits are not being configured.

  2. URL Corruption: If I include a placeholder in my CSV URL, the app often appends a second string (e.g., ?m=00...) to the end, resulting in a corrupted link.

  3. Manual vs Batch: "Configure Mirroring Options" works perfectly in manual mode, but these settings are not applied during CSV import.

Goal: To import a CSV with unique Serial Numbers and automatically enable hardware UID and Counter mirroring for each tag.

Technical Data (CSV tested): 

Type: Link

Content:

URI type: URL

Description: 

Interaction counter: yes

UID mirror: yes

Interaction counter mirror: yes


Note: I have tested over 15 variations of placeholders like unique_tag_UID and 000000..., all failing to trigger the hardware offset.  In all cases, the text was written literally or the hardware mirroring was not activated.

Could you provide the exact CSV syntax or the specific workflow required to ensure that hardware Mirroring (UID and Counter) is enabled and offsets are correctly calculated during a CSV import session?

0 Kudos
Reply
0 Replies
%3CLINGO-SUB%20id%3D%22lingo-sub-2342204%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EIssue%20NFC%20TagWriter%20Mass%20Encoding%20UID%20and%20Counter%20Mirroring%20failing%20on%20NTAG%2021x%20CSV%20Importg%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2342204%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20am%20experiencing%20a%20critical%20issue%20with%20the%20NFC%20TagWriter%20App%20when%20using%20the%20%22Write%20from%20CSV%22%20(Mass%20Encoding)%20feature%20with%20NTAG%20213%20and%20216%20tags.%3C%2FP%3E%3CP%3EWhile%20manual%20configuration%20works%20for%20single%20tags%2C%20the%20batch%20process%20via%20CSV%20fails%20to%20correctly%20trigger%20hardware%20mirroring%20bits.%3C%2FP%3E%3CP%3E%3CSTRONG%3EMain%20Problems%20Observed%3A%3C%2FSTRONG%3E%3C%2FP%3E%3COL%3E%3CLI%3E%3CP%3EStatic%20Data%3A%20Even%20when%20%22UID%20mirror%22%20and%20%22Interaction%20counter%20mirror%22%20columns%20are%20set%20to%20%22yes%22%20in%20the%20CSV%2C%20the%20app%20writes%20the%20placeholder%20(00000000000000)%20as%20static%20text.%20The%20hardware%20mirror%20bits%20are%20not%20being%20configured.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EURL%20Corruption%3A%20If%20I%20include%20a%20placeholder%20in%20my%20CSV%20URL%2C%20the%20app%20often%20appends%20a%20second%20string%20(e.g.%2C%20%3Fm%3D00...)%20to%20the%20end%2C%20resulting%20in%20a%20corrupted%20link.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EManual%20vs%20Batch%3A%20%22Configure%20Mirroring%20Options%22%20works%20perfectly%20in%20manual%20mode%2C%20but%20these%20settings%20are%20not%20applied%20during%20CSV%20import.%3C%2FP%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%3CSTRONG%3EGoal%3A%3C%2FSTRONG%3E%20To%20import%20a%20CSV%20with%20unique%20Serial%20Numbers%20and%20automatically%20enable%20hardware%20UID%20and%20Counter%20mirroring%20for%20each%20tag.%3C%2FP%3E%3CP%3E%3CSTRONG%3ETechnical%20Data%20(CSV%20tested)%3A%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EType%3A%20Link%3C%2FP%3E%3CP%3EContent%3A%3C%2FP%3E%3CP%3EURI%20type%3A%20URL%3C%2FP%3E%3CP%3E%3CSPAN%3EDescription%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EInteraction%20counter%3A%26nbsp%3Byes%3C%2FP%3E%3CP%3EUID%20mirror%3A%20yes%3C%2FP%3E%3CP%3EInteraction%20counter%20mirror%3A%20yes%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ENote%3A%20I%20have%20tested%20over%2015%20variations%20of%20placeholders%20like%20unique_tag_UID%20and%20000000...%2C%20all%20failing%20to%20trigger%20the%20hardware%20offset.%26nbsp%3B%26nbsp%3BIn%20all%20cases%2C%20the%20text%20was%20written%20literally%20or%20the%20hardware%20mirroring%20was%20not%20activated.%3C%2FP%3E%3CP%3ECould%20you%20provide%20the%20exact%20CSV%20syntax%20or%20the%20specific%20workflow%20required%20to%20ensure%20that%20hardware%20Mirroring%20(UID%20and%20Counter)%20is%20enabled%20and%20offsets%20are%20correctly%20calculated%20during%20a%20CSV%20import%20session%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E