Repository navigation
Guides: add Buy and encode TigerTag chips - #19
Closed
saucissefarciehumaine-prog wants to merge 5 commits into
Closed
saucissefarciehumaine-prog wants to merge 5 commits into
saucissefarciehumaine-prog wants to merge 5 commits into
Conversation
First page of the guides section: the wrong purchases that only reveal themselves after delivery - chip references, sealed PN532 dongles, the 3.5 vs 3.5B screen, unpowered USB hubs, metric screws, CF filament. Sources: Tiger-Scale-V3 README (sealed dongles, BOM), the TigerTag chip concept page (NTAG213/215), the compatibility matrix (MIFARE Classic), team and builder reports on the Discord (3.5 vs 3.5B, hub write failures, screws). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Chip-level problems ordered by frequency: detection checks, blank/Init chips, wrong data, printer-side support, TigerTag+ verification failures (fixable vs by-design), interrupted writes, and what to include when asking in #help-and-support. Stacked on the buying-pitfalls branch: cross-references it twice instead of duplicating the hub-power and on-metal explanations. Sources: the TigerTag chip concept page, the TigerTag+ product page, the compatibility matrix and Snapmaker page, builder reports on the Discord (marked as reported). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
From the #help-and-support history (Aug 2025): a write failing on a chip carrying non-TigerTag data, where a blank chip works first try. Documents the convert path and the community wipe workaround. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The signature now belongs to the TigerTag+ Certified tier, per the updated tigertag-plus product page on main. Section retitled, and the rewritten-after-signing row now says the chip stays readable, simply no longer certified. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The foundational how-to from the guides TODO list: which chips to buy, which reader, encoding from phone or desktop, Twin Tag pairs, encoding in series, and what home encoding cannot do (Certified). Stacked on the guides stack; cross-references buying-pitfalls and troubleshooting instead of restating them. Removes the matching line from the README TODO block. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
@saucissefarciehumaine-prog is attempting to deploy a commit to the Tiger-Project Team on Vercel. A member of the Team first needs to authorize it. |
Collaborator
|
Closing with #2, #20 and #21 — the full reasoning and the rules for redoing these are in #2, please read that one first. In short: these four are a stack, this branch carries Specific to this one, because it is the closest to landing of the four: The structure is right — which chips, which reader, encode from the phone, encode as a pair — and it matches what the apps actually do. The step-3 detail is accurate: a blank chip offers a new TigerTag, a chip holding non-TigerTag data offers a conversion. The "fill in the temperatures even if you know them by heart" tip is the kind of advice that only comes from someone who has done it. Two things to settle when you bring it back as a single page:
Rebased onto current |
This was referenced Sep 6, 2026
BenGlut
pushed a commit
that referenced
this pull request
Sep 7, 2026
The end-to-end Twin Tag guide flagged in #19 as the genuinely new material: pick the tool (phone with Dual NFC, TigerPOD with two readers, single reader), do it, check that the pair reads as one spool, and what the surviving chip is for when one dies. Routes to the pages that own each fact instead of restating them: concepts/tigertag-chip (why two), tutorials/first-smart-spool (Dual NFC), products/tigerpod (two readers vs one), developers/ttag-format (twins are atomic). No "Link to twin Spool" - the undocumented repair steps are a TODO. Sidebar entry and French translation included; both gates green. Co-authored-by: Zaerog <318722065+saucissefarciehumaine-prog@users.noreply.github.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Guides TODO #1 (of the four in
guides/README.md): buying and encoding chips.Foundational how-to — which chips, which reader, encoding from phone or desktop, Twin Tag pairs, encoding in series, and what home encoding can't do (Certified).
Stacked on the guides stack (buying-pitfalls → troubleshooting → this). It cross-references both instead of restating them, and removes the matching line from the README TODO block. Merge the earlier ones first and this diff shrinks to its one new page + one index line.
Sources:
concepts/tigertag-chip.md(NTAG213 minimum, two chips per spool),tutorials/first-smart-spool.md(the encode flow), Twin Tag / Dual Link and the desktop-only chipless burn from #help-and-support answers,products/tigertag-plus.md(home encoding can't sign).🤖 Generated with Claude Code