Anycubic Kossel Klipper configuration
This article will guide you through Anycubic Kossel Klipper configuration.
Follow the steps and create your own configuration.
Klipper uses printer.cfg configuration file which is something similar to Marlin configuration and configuration_adv files.
This file can be easily modified with text editors, such as Pspad, or NotePad and uploaded to Raspberry via SFTP in Total Commander.
This article is about stock setup – stock A4988 drivers and Trigorilla board, but you can also download configuration file prepared for UART TMC drivers or for a SKR board.
1. Download one of these configuration files
Download configuration file for your printer.
I do not have every driver type or board, but I consider Trigorilla, SKR, A4988, TMC2208/TMC2209 as a standard these days.
You can learn more about configuration files HERE on Klipper GIT
If you have TMC2209, download some of the TMC2208 configuration files and just simply rename all TMC2208 definitions to TMC2209.
Download configuration file:
2. Check your pin/port definition
Here is a simplified pin schematic for a standard Trigorilla board.
If you want to use UART, follow this guide CLICK HERE
3. Modify configuration file (optional)
These steps are optional.
If you have the same configuration as one of my configuration files, you can skip these steps.
If you want to learn more about Klipper configuration files, open the printer.cfg file with a text editor such as NotePad+, PSPad.
I have tried to make this as simple as possible.
On the left side you will see a configuration from printer.cfg file and description on the right side.
3.1. Probe type
This part is configured for original autoleveling Z probe type 2.
Older Kossels can be equipped with type 1 probe which is NO – normally open type which means that you have to invert logic:
pin: !ar18
printer.cfg
Description
pin– probe is connected to pin 18, which is a standard Z probe pin
z offset – Z height of your probe (when it triggers)
samples – how many times will be each leveling point measured
speed – probing speed
sample_retract_dist – Z probe retraction distance between samples
If you are not sure about your probe type, check it with a multimeter:
Probe 2 is a NC – normally closed which means that it is normally switched on, so you will read a very low resistance or you can beep the contacts – if it beeps without touching the probe, it is type 2.
3.2. Stepper driver
Klipper defines pins and all other stepper settings in each stepper driver block.
The code you can see below is a stepper definition for standard A4988 drivers and Trigorilla board.
printer.cfg
Description
step_pin – step pin
dir_pin – direction pin
enable_pin – enable pin
step distance – mm/s per one step
endstop_pin – end stop pin for each axis
3.3. Stepper driver
This is a standard configuration for a stock extruder.
printer.cfg
Description
step_distance – mm / step, magic number
heater_pin – board pin for heating element
sensor_type – thermistor type
sensor_pin – thermistor pin
control – type of control
pid values – hot end PID values
min_extrude_temp – extruder can move only above this temperature
min_temp – minimal hot end temperature
max_temp – maximal hot end temperature
3.4. Bed heater
printer.cfg
Description
heater_pin – bed heater pin
sensor_type – thermistor type
sensor_pin – thermistor pin
control – type of control
min_temp – minimal bed temperature
max_temp – maximal bed temperature
3.5. Cooling fan
printer.cfg
Description
pin – Trigorilla fan pin (in this case fan 0 = D9 = ar9)
kick_star_time – start fan after 0.2 s of printing
3.5. Heater (hot end / heatsink) fan
If you want your extruder fan to be quieter, you have two options:
Follow this fan upgrade guide CLICK HERE
Or set the speed to a lower value and perform a PID calibration.
printer.cfg
Description
pin – Trigorilla fan pin
heater – what heater does the fan cool down
heater_temp – fan starts working at this heater temperature
fan_ speed – 1.0 means 100% of the maximal fan speed
3.6. Output pins
You can use more output pins, you only need to define them.
printer.cfg
Description
You can define another output pins.
In this case:
[output_pin BEEPER_pin] – beeper pin
3.7. MCU - board type
printer.cfg
Description
Trigorilla is basically a modified Arduino Mega
3.8. Printer configuration
As you can see below, our printer has a delta kinematics with a 120 mm radius (240 mm bed) and the maximal values for velocity, acceleration and z velocity are defined here.
printer.cfg
Description
kinematics – printer type
max_velocity – maximal velocity failsafe
max_accel – maximal acceleration failsafe
max_z_velocity – maximal Z axis velocity failsafe
delta_radius – bed radius
minimum_z_position – maximal deviation from the printer height
3.9. Delta calibration
printer.cfg
Description
radius – bed calibration radius
speed – calibration speed
horizontal move_z – z move between probing points
3.10. Bed mesh
printer.cfg
Description
speed – travel speed between probing points
horizontal_move_z – z move between calibration points
mesh_radius – calibration radius
mesh_origin – where the center of the bed is
round_probe_count – how many points will be measured
3.11. Driver cooling fan
printer.cfg
Description
pin – fan pin, in this case ar7 = D7 = FAN1 connector
max_power – PWM value 0-1.0
kick_start_time – start after xx seconds
idle_timeout – end after xx seconds
heater – in this example extruder – it starts heating up, fan starts working
hi lukas,
i’ve uploaded the printer.cfg file, extruder work, hotend work, bed work, but when i’ve tried to home the axis the steppers make a big noise and a lot of vibration (VRRRRR) and they doesn’t stop at the switch. where i’m wrong? is a stepper problem?
Hi, provide more informations.
I have 2-3 different printer.cfg files on this website for different motherboard and driver configuration.
I do not now which one you used and what parts you have in your printer.
I use your Stock board (Trigorilla) and TMC2208 DIY drivers but added [controller_fan my_controller_fan]. But I got a conflict [output_pin my_pin]. Do this serve the same function? Which one should I use?
Hi, what conflict?
hi,
im a bit confused about z probe configuration. a month ago i crushed my original (old type) z probe because of no reaction. now i have type 2, everything configured as described, but when i start DELTA_CALIBRATE and try to hit the probe with my finger to avoid breaking it again, nothing happens.
any idea?
It is possible that Klipper ignores the probe some part of the height.
But I am not really sure, I have never tried it.
Hi there,
thank you for the great tutorial. Two Questions/Comments:
1. In 2.2 is written “dir_pin: ar55”. Your config says “dir_pin: !ar55”. Maybe a typo?
2. In 2.2 is written “round_probe_count: 9”. Your downloadable config uses “round_probe_count: 5”. A probe_count of 5 seems a bit low…
Sorry, got the number in my posting wrong: the probe count value is in 2.10 🙂
NP
Hi, thank you!
Yes, those are typos, I have about 5 different configs right know…
This is correct for stock drivers: dir_pin: !ar55.
For TMC drivers: dir_pin: ar55.
I have used 5 points, because it is enough for most of these printers.
So I’ve got this working except the z-probe doesn’t trigger Klipper to stop when using assisted bed leveling. I have probe version 2. Any help would be greatly appreciated.
Stop what?
Does it crash into the bed or?…
Also there are 3 different configuration files on my page…
Which one do you use?
And also always use only DELTA_CALIBRATE with delta printers.
I see. Sorry, I was being silly; I just assumed you could use the assisted bed leveling to level the bed.
It usually does, but with delta printers, it is always better to use only a delta calibration.