Repository navigation
Conversation
… and weight handling in backend_klipper
…ag filament data management
…ment AFC integration
Restored and updated the section on Klipper printers with AFC, including setup instructions and command details.
Author
|
I will push some updates next days and restart Pull Request |
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
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.
What this changes
Add a Klipper backend for AFC printers (draft)
Closes #31 (as far as OpenCreator / AFC printers go).
A
PT_KLIPPERbackend that talks to Moonraker over a WebSocket, the sametransport the Snapmaker backend uses (
ws://<ip>:7125/websocket, noauthentication). It is written to fit the existing
PrinterBackendinterface andchanges nothing in it.
extruder0..extruder3as slots T0..T3: material,colour, remaining weight as a percentage, and the active tool.
TT_SET_LANEcall, then reads the lane backand reports
confirmed,sent, not confirmedafter 12 s, or Moonraker's ownerror text. This follows the comment on
refresh()that an acknowledgedcommand is not proof it landed.
Originheader that Moonraker's authorisation component needs.
The printer side is a small Klipper config,
tigertag.cfg(two macros,TT_SET_LANEandTT_LOAD).TT_SET_LANEcalls AFC'sSET_MATERIAL,SET_COLORandSET_WEIGHT, and keeps brand, variant, nozzle temperature andtag id in
save_variables, because AFC has no fields for them.Files
src/backend_klipper.h,src/backend_klipper.cppsrc/printer.hPT_KLIPPER = 7src/printer_budget.hPT_KLIPPERsrc/main.cpp#include,typeTag,ctrlPort, backend factory, link cost, brand namesrc/tigertag_cloud.cpp"klipper"inBRANDS/BRAND_TYPE,mapTypesrc/webcfg.cppklipper/tigertag.cfgREADME.mdTesting
Fill in before marking ready. Do not tick what was not done.
pio run -e tigerspoolbuilds without errors or new warningspio run -e tigerspool-benchbuildsconfirmedOpen points, where I would like a decision or a correction
extruder0..extruder3is handled. Printers with otherAFC lane names or counts would need the lane list read from the
AFCobject.with
g. The percentage shown is relative to AFC's owninitial_weight,which this code does not set.
tigertag.cfginklipper/. Move it ifthere is a better place.
main.cpp,tigertag_cloud.cppand
webcfg.cppwith scripts that are not part of this PR.Notes
The backend and the macros were written with an AI assistant (Claude) from the
existing Snapmaker backend, the repository's architecture notes and the data a
real printer reports. They were reviewed and tested by me as listed above.
Checklist
CHANGELOG.mdupdated for anything user-visible.