Repository navigation
feat: protocol v2.2 tag index / count, catalogue, offline reference data, unified playground (1.3.0) - #1
Merged
Conversation
…ata, unified playground
Protocol v2.2
- Byte +39 (page 0x0D byte 3) is the tag index / tag count: high nibble =
index, low nibble = count, so 0x12 is tag 1 of 2. tag_info, tag_index,
tag_count; create(tag_count=, tag_index=), patch(), validate(), to_dict(),
pretty() and describe() ("Tag 1 of 2 on this filament."). Same in the
standalone parse_tigertag.py.
- to_bytes() and patch() refuse a measure_available above measure.
TigerTag+ catalogue
- TigerTag.from_catalog(product_id) builds a ready-to-burn TigerTag+ from the
official id_catalog.json (RFID_Data). load_catalog / refresh_catalog /
catalog_info / catalog_entry, with an ETag-aware disk cache.
Reference data
- The 7 tables and the catalogue (gzip) ship with the package and are used
offline. A daily check downloads only the tables that changed into the
user cache dir (or TIGERTAG_DATA_DIR); the newest of downloaded and
bundled wins per table. offline=True / TIGERTAG_OFFLINE=1 disables every
network call, db.update(force=True) and `tigertag update` update on
demand, and a custom db_path is used exclusively. Behaviour change: the
SDK now checks for updated reference data once a day unless offline.
- raw_api() uses certifi's CA bundle when installed (python.org macOS
builds ship without CA certificates).
Playground
- One playground page shared byte-for-byte with the JS SDK, against a common
server contract (docs/playground-api.md): ACR122U readers through pyscard
(optional extra tigertag[nfc]), Read / Burn modes, twin tag burning, SDK
Input (create(), HEX, Pages), chips-on-the-readers check, TigerTag+ product
loading (offline catalogue or online API), catalogue and table updates,
info bubbles, SVG icons. Burn always writes pages 0x04-0x27 with the
signature pages cleared; playgrounds never write a signature.
scripts/check_playground_sync.py guards the shared page.
Other
- Signature results and outputs no longer use emoji.
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.
Highlights
0x0Dbyte 3 (high nibble = index, low = count:0x12= tag 1 of 2). Spec: spec: chip count / chip index at page 0x0D byte 3 (v2.2) TigerTag-RFID-Guide#26, #27, #28.id_catalog.json(RFID_Data), with an ETag-aware cache.TIGERTAG_DATA_DIR);offline/TIGERTAG_OFFLINE=1disables all network calls; manualupdate(API + CLI); a custom folder is used exclusively. Behaviour change: one network check per day unless offline.tools/playground.htmlin the JS and Python SDKs, against a common server contract (docs/playground-api.md) — Read / Burn modes, twin-tag burning, SDK Input (create(), HEX, Pages), chips-on-the-readers check, TigerTag+ loading (offline catalogue or online API), catalogue and table updates, info bubbles, SVG icons. Burn always writes pages 0x04–0x27 with the signature pages cleared: playgrounds never write a signature.Tested
0x12/0x22, shared timestamp, signature pages00), single-reader burn, and cross-SDK burns read back byte-for-byte identically.Merge note
check_playground_synccompares this repo'stools/playground.htmlwith the other SDK's copy onmain. It passes locally; in CI it will pass once both SDK PRs are merged.