Skip to content

Compatibility: Moonraker on Snapmaker does not mean Klipper support #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
saucissefarciehumaine-prog wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Compatibility: Moonraker on Snapmaker does not mean Klipper support #50

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/compatibility/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ How TigerSystem works with each printer ecosystem. Two independent axes:
| [OpenSpool](./openspool.md) | n/a (tag standard, not a printer) | NFC Type 2, NDEF JSON | None — open standard | Spec documented |
| Qidi | Not integrated | Mifare Classic 1K | Default key | [Spec documented](https://github.com/TigerTag-Project/TigerTag-Studio-Manager/blob/main/docs/rfid-vendors/qidi.md) |

> **Note:** the Snapmaker link happens to use Moonraker; that does not make
> other Moonraker machines work — generic [Klipper](./klipper.md) printers are
> not supported today.

> **Note:** the per-vendor RFID sheets (read-only decoding specs, derived from
> the [OpenRFID](https://github.com/suchmememanyskill/OpenRFID) project) are
> maintained in the Tiger Studio repo under
Expand Down
4 changes: 4 additions & 0 deletions docs/compatibility/klipper.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ integration today**. However, Tiger Studio's Snapmaker link already speaks
Moonraker WebSocket/JSON-RPC — the natural foundation for a
vendor-neutral Klipper integration.

Sharing the transport does not mean sharing the support: the Snapmaker link
happens to use Moonraker, and a generic Klipper machine is **not supported**
today, even though it exposes the same API.

| Aspect | Status |
|---|---|
| Moonraker transport | Exists (used by the Snapmaker integration) |
Expand Down
6 changes: 5 additions & 1 deletion i18n/fr/compatibility/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sourceHash: a12992e7b500e2dde8a21443c09a157093fbf40e589c4ad4dc960c7acde2ce6f
sourceHash: 75e2e06ba62fa0ebfe1c2c5ada15e34d9c0e071b58e0882c82c8847319441e2a
sourcePath: docs/compatibility/README.md
---

Expand Down Expand Up @@ -31,6 +31,10 @@ Comment TigerSystem fonctionne avec chaque écosystème d'imprimante. Deux axes
| [OpenSpool](./openspool.md) | n/a (standard de tag, pas une imprimante) | NFC Type 2, JSON NDEF | Aucun — standard ouvert | Spécification documentée |
| Qidi | Non intégré | Mifare Classic 1K | Clé par défaut | [Spécification documentée](https://github.com/TigerTag-Project/TigerTag-Studio-Manager/blob/main/docs/rfid-vendors/qidi.md) |

> **Note :** la liaison Snapmaker passe par Moonraker, ce qui ne fait pas
> fonctionner les autres machines Moonraker — les imprimantes
> [Klipper](./klipper.md) génériques ne sont pas prises en charge aujourd'hui.

> **Note :** les fiches RFID par constructeur (spécifications de décodage en lecture
> seule, dérivées du projet [OpenRFID](https://github.com/suchmememanyskill/OpenRFID))
> sont maintenues dans le dépôt Tiger Studio, sous
Expand Down
6 changes: 5 additions & 1 deletion i18n/fr/compatibility/klipper.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sourceHash: 6a70119833796c9aad3bd09cf54863a7572f174fd87f0f0f4d3a948ea25fe24a
sourceHash: 03e3a29ecc9d4b7e4a787c9c13318492f06c90566ba309c9be928d03f94979b6
sourcePath: docs/compatibility/klipper.md
---

Expand All @@ -12,6 +12,10 @@ l'objet d'une intégration officielle à ce jour**. En revanche, la liaison
Snapmaker de Tiger Studio parle déjà le WebSocket/JSON-RPC de Moonraker — la
base naturelle d'une intégration Klipper neutre vis-à-vis des constructeurs.

Partager le transport ne veut pas dire partager la prise en charge : la liaison
Snapmaker passe par Moonraker, et une machine Klipper générique **n'est pas
prise en charge** aujourd'hui, même si elle expose la même API.

| Aspect | Statut |
|---|---|
| Transport Moonraker | Existe (utilisé par l'intégration Snapmaker) |
Expand Down
Loading