This is my klipper_config that uses custom gcode macros extensively to enhance the 3d printing experience.
It was originally envisioned to allow data to be communicated from the Slicer to Klipper and then stored in variables for use by other macros during/before/after the print but I would like eventually for it to be a much more extensive project that truly takes advantage of what gcode macros can do!
There is now quite a large selection of macros!
From filament changes to maintenance positioning to heat soaks and print-area-meshing. There's something for everyone! And I've done my best to make the user experience as clean as possible.
Additionally, this config now utilizes:
- Multiple temperature/humidity/environment sensors
- Monitors chamber, ambient, and spool temp/humidity and VOC levels
- WLED-controlled addressable LED strips
- Directly-controlled addressable LEDs
- KlipperScreen on a 7-inch HDMI touchscreen
- Two SSH1306 OLED displays with custom display data
- A BTT Mini12864 display hosted by a custom STM32 controller board for easy usb connectivity
- Rotary encoder and several physical buttons
- Multi-pitch beeper
- Smart plug for printer power
- Smart plug for Filter power
- Nevermore Carbon Filter
- A controllable fan-enhanced desiccant box
- MAX31865/PT-1000 extruder thermistor
- Several controller boards: SKR-Pico, Pi Host, EBB42 CANbus Toolhead, Pico, and two QTPY-rp2040
- All of the toolhead components have been moved to the CANbus board
- Speed-controlled cooling fans for Nevermore, bed fans, and part-cooling
- Temperature-controlled fans for hotend, exhaust, SKR-Pico, and Pi host.
- Smart filament sensor with automated filament change procedure
- Two ADXL accelerometers for resonance tuning and input shaping
- An extensive collection of custom macros
If you are looking for guides on calibrating or setting up a new Klipper printer, those are found here:
I'm working on, breaking, changing, and using this daily! I strongly suggest nobody use this full config for anything more than reference/inspiration at this time.
It is likely to fail/crash on your system in its current state!
Many of these macros work as great examples of using scripting and other Klipper features to perform different tasks.
Many may even work on your printer as-is.
But a lot of them won't.
So consider this more of a selection of examples that will likely need to be tailored to fit your unique system. Use it as a resource to see how you could do something, not necessarily how you should. Feel free to message me with questions if you have them.
This may be just because they conflict with other existing macros I already use, or they are there as samples/examples. But they aren't included on my personal system.
The machine folder is included by the printer.cfg file and the rest are included through zippy.cfg
Its only contents (aside from automated overrides) are:
# Rootiest Zippy Klipper config
# Machine directory
[include machine/*.cfg]
This way we can have full access to modify any parts of the config without risking overwriting the automated overrides.
The zippy.cfg file contains the includes for the macros directory as well as some other files used by extensions. This allows the paths of those files to be preserved to maintain compatibility with extension updates.
A snapshot of the printer.cfg file is available to see here:
- mooncord.json
- telegram.conf
- telegram_conf.conf
- moonraker_secrets.ini
Sanitized examples can be seen here:
This helps to prevent accidental syncing of your private passwords or tokens as well as reducing clutter from backup files.
You can reach me on Discord at rootiest#5668
Many parts of this project were borrowed quite heavily from other people's work.
I am compiling a list of acknowledgements to include in this README before posting publicly.
Klipper is a 3d-Printer firmware. It combines the power of a general purpose computer with one or more micro-controllers. See the features document for more information on why you should use Klipper.
To begin using Klipper start by installing it.
Klipper is Free Software. See the license or read the documentation.