docs: Snapmaker U1 direct-mode integration#6
Merged
Conversation
- new installation/snapmaker-u1.md — full setup guide, references the web flasher for the v1.7.5+ requirement - new resources/workflow-snapmaker-u1.md — data flow + comparison table - compatibility.md — add U1 row to support matrix + new section - releases/scanner.md — v1.7.5 changelog entry - roadmap.md — move direct-Moonraker out of Exploring/In-Progress, add to Completed under v1.7.5; replace Exploring slot with U1 stage mode - mkdocs.yml — wire both new pages into nav (Installation + Workflow Diagrams) All six SpoolSense tag formats are called out as supported on the U1, matching the Voron / Klipper coverage. Stage mode flagged as the next phase (one scanner serving all 4 channels).
Pushes made with the default GITHUB_TOKEN don't trigger other workflows (anti-recursion guard). After we switched update-firmware.yml to use GITHUB_TOKEN, the manifest update commit no longer fires deploy.yml's `on: push` handler, so new firmware versions stayed in the repo but never went live on the site. Add an explicit `gh workflow run deploy.yml` after a successful manifest push so the chain reconnects. Skip the dispatch when the commit was a no-op so we don't waste a deploy run. Tested manually: v1.7.5 manifest landed without deploy firing; manual deploy trigger picked it up.
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.
Summary
Documentation for the Snapmaker U1 direct-mode integration shipping in scanner v1.7.5.
Changes
All 6 tag formats
The install guide and compatibility section both call out that all six SpoolSense tag formats are supported on the U1 — same coverage as the Voron / Klipper integration. OpenSpool / OpenPrintTag / TigerTag / OpenTag3D / Bambu UID / NFC+.
Stage mode
Flagged in both the install guide (admonition under "Multi-Scanner Setup") and the comparison table on the workflow page as the next phase: one scanner serving all 4 U1 channels via post-scan channel selection (keypad / web UI / motion-sensor auto-pick).
Companion to