Skip to content

snapmaker.md

Latest commit

 

History

History
48 lines (36 loc) · 2.15 KB

snapmaker.md

File metadata and controls

48 lines (36 loc) · 2.15 KB
Raw

Snapmaker

Printer link — Live

Aspect Detail
Protocol Moonraker WebSocket (JSON-RPC), port 7125 + proprietary extensions
Discovery HTTP scan
Filament 4 slots — per-slot filament edit (RRGGBBAA color model)
Control Live control panel (axes, temps, light, fan, speed, load/unload)
Telemetry Temperatures, job progress

Native RFID — spec documented, in-app read planned

Snapmaker spool tags are Mifare Classic 1K with HKDF-derived per-sector keys and an RSA-2048 PKCS#1 v1.5 + SHA-256 signature — the most heavily locked format documented so far. Read-only decoding spec: docs/rfid-vendors/snapmaker.md.

The workflow

  1. Add the printer — HTTP scan on the LAN or Add by IP; Tiger Studio talks Moonraker (JSON-RPC over WebSocket).
  2. Scan a spool — phone or desktop reader; it lands in your inventory.
  3. Assign it to a slot — per-slot filament edit (Snapmaker's RRGGBBAA color model handled transparently).
  4. Live & control — telemetry, job progress, and a control panel: axes, temperatures, light, fan, speed mode, load/unload per slot.

Limitations

  • Native Snapmaker tags are not read in-app yet — the spec is documented, and the current work aims at converting vendor tag data into TigerData spools (see Compatibility).

The first printer to read TigerTag natively

The community's Snapmaker U1 Extended Firmware (independent, GPL-3.0) adds SSH, camera streaming, metrics — and with it, the Snapmaker U1 reads TigerTags natively, on the machine itself. That makes the U1 the first printer where a TigerTag spool is recognized without any app in between — the future the collective play aims at, arrived early via the community. See third-party integrations.

◀ Previous: Anycubic · ▲ Documentation index · Next ▶ Klipper