<aside> ⚠️

I strongly advise not modifying the stock printer configuration. Rinkhals offers additional protection you don't have while modifying directly your printer configuration. I won't offer any support and your printer might not work properly or not boot anymore.

</aside>

Many users want to change their Klipper printer configuration (the printer.cfg file).

Please note that Anycubic and thus Rinkhals use GoKlipper, a Go reimplementation of Klipper that does not support the same level of tweaking that you would be able to do with vanilla Klipper. If you modify the printer.cfg, your printer might not boot properly or show error 11407 (meaning GoKlipper could not start, usually because of a broken configuration).

Before starting, here is a link to known stock printer configurations: https://github.com/jbatonnet/Rinkhals/tree/master/files/3-rinkhals/home/rinkhals/printer_data/config

And here is a link to stock firmwares you can flash to restore your printer:

https://rinkhals.meowcat285.com/

Stock firmware configuration

If you break something, restore the configuration or reflash stock firmware using the links above.

Rinkhals configuration system

<aside> ⚠️

I provided the ability to use custom configuration because people asked for it, but I'm not responsible for what you do or how you brick your printer this way! I personally don't use customizations and I'm quite happy this way. You are now warned!

</aside>

The first one is the printer default with a [include printer.rinkhals.cfg] at the end The second has Fluidd customizations with a [include /useremain/home/rinkhals/printer_data/config/printer.custom.cfg] at the end The third one will be able to be used for user customizations. This is the only one that will be persisted accross Firmware and Rinkhals versions.

I got 11407 or my printer doesn't boot anymore

First read all the warnings everywhere, and the information above provide ways to restore your printer.

Error 11407 is GoKlipper not being able to start on your printer. There are two main reasons for this issue to appear: