Include after AFC, link scripts/ into the config folder
- bd_pa_spoolman.cfg renames AFC's SET_SPOOL_ID, so klipper-macros.cfg must be included after [include AFC/*.cfg]; the README said otherwise. - install.sh links scripts/ as ~/printer_data/config/klipper-macros-scripts so the scripts can be edited in Mainsail/Fluidd. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9dc733b5bb
commit
179bd0991b
5 files changed
+40
-17
No files matched your search
@@ -30,8 +30,10 @@ check runs with `motion_check: False`), iHeater chamber heater.
|
||||
## Repo layout
|
||||
|
||||
- `macros/klipper-macros.cfg` is the only file `printer.cfg` includes; it
|
||||
includes everything else. On the Pi, `macros/` is linked as
|
||||
`~/printer_data/config/klipper-macros/`.
|
||||
includes everything else. It must be included after `[include AFC/*.cfg]`
|
||||
(a `rename_existing` of an AFC command only works if AFC loaded first).
|
||||
On the Pi, `macros/` is linked as `~/printer_data/config/klipper-macros/`
|
||||
and `scripts/` as `~/printer_data/config/klipper-macros-scripts/`.
|
||||
- `extras/*.py` are linked into `~/klipper/klippy/extras/`.
|
||||
- `scripts/` MCU firmware update scripts (printer-specific IDs).
|
||||
- `tools/effective_config.py` expands the includes like Klipper and compares
|
||||
|
||||
Reference in new issue
Block a user