docs: list BambuTagger among the community integrations - #23
Merged
Conversation
Two open-hardware ESP32 builds that read and write TigerTag: a handheld reader/writer/cloner with a touchscreen, and a four-slot reader that sits on a Bambu Lab AMS and feeds the printer. They are the first third-party hardware in this list — everything else here is software. The compatibility claim was checked against the source rather than taken from the product page. Their parser reads the user block at the offsets this specification defines — material at +8, aspects at +10 and +11, diameter at +13, brand at +14, colour at +16, measure at +20 with the unit conversion, temperatures from +24 to +31 — and accepts both type ids, which is right. What it does not read is worth stating for anyone deciding whether to build one: no Transmission Distance, no custom message, no signature, so the device makes no authenticity claim, and its reference tables are compiled in as a snapshot rather than synced, so new brands need a firmware update. Cloning gets a line too, since the device offers it and a reader of §3 may wonder: copying a signed chip reproduces the payload, not the signature's validity.
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
1 participant
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.
Adds §6.4 for bambutagger.de — the first
third-party hardware in this list; everything else in §6 is software.
What it is
touchscreen, one RC522, battery, local storage for 2 000+ tags.
displays live slot data and pushes tag data to the printer/BMCU. Web
configuration, OTA updates.
Both are DIY from off-the-shelf modules with printed cases and published
PCB files. AGPL-3.0.
The compatibility claim was verified, not repeated
The product page says "TigerTag" among the formats it handles. Rather
than take that at face value, the parser in
src/main.cppwas read against §2 of this specification. Every offset matches:
id_measure_unit.json)It accepts both
0x5BF59264and0xBC0FCB97, which is correct.And the limits are stated
Because someone reading §6 may be deciding whether to build one:
signature — so it makes no authenticity claim, and none should be read
into it.
database/, so newly catalogued brands and materialsresolve only after a firmware update.
Cloning gets a line as well, since the device offers it and a reader of
§3 may wonder: copying a signed chip reproduces the payload, not the
signature's validity — the attestation-not-a-lock property this project
already documents.
The section's existing disclaimer covers it: community projects, not
maintained or endorsed by TigerTag Project.