Skip to content

TigerTag: custom message and bed temperature (supersedes #18) - #32

Open
TigerTag-Project wants to merge 6 commits into
suchmememanyskill:mainfrom
TigerTag-Project:tigertag-message-bedtemp
Open

TigerTag-Project wants to merge 6 commits into
suchmememanyskill:mainfrom
TigerTag-Project:tigertag-message-bedtemp

Conversation

@TigerTag-Project

Copy link
Copy Markdown

This PR takes over #18 by @physicsG and adds the fixes it needed to pass the tests on the current main. @physicsG's commits are kept as-is, with their authorship.

From #18

  • New GenericFilament fields: bed_temp_max_c and message
  • The TigerTag parser now fills bed_temp_c (min) and bed_temp_max_c (max) instead of always returning 0.0
  • The 28-byte custom message (+48, pages 0x10-0x16) is read as UTF-8 text, for example a filament name
  • Updated TigerTag fixtures and a synthetic New Fields TigerTag fixture generated by test/scripts/build_tigertag_fixture.py

Fixes on top

  • Synthetic fixture header: the .bin had zeros where the NTAG capability container should be, so test_physical_dump_preserves_processor_output[New Fields TigerTag] (added with NTAG216 support) failed with KeyError: 0. The generator now writes a real NTAG215 header: a 7-byte UID with its BCC check bytes, plus the capability container E1 10 3E 00.
  • Nozzle temperatures: the fixture had min 230 / max 190. They are swapped to min 190 / max 230.
  • Comments: aligned with the current TigerTag spec. The custom message is 28 bytes of free UTF-8 text with no reserved emoji prefix, and +76..+78 holds Measure Available. The parsing code is unchanged, since it already matches the spec.

Tests

97 passed, 1 skipped once merged with current main.

Closes #18

Gordian-Alliander and others added 6 commits April 24, 2026 12:13
- Give the synthetic fixture a real NTAG215 header (UID with BCC bytes and
  capability container), so the reader's physical-size check can read it
- Swap the inverted nozzle temperatures (min 190, max 230)
- Update comments to match the current TigerTag spec: the custom message
  is 28 bytes of free UTF-8 text with no reserved emoji prefix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants