dgotc
New member
Hello all,
My 2.4r2 has been a great workhorse for a few years now. It had klicky/z-cal and kamp running smoothly for a long time. I was recently away for several months, came back, did some prints just fine, then did a full update of every software component. Now when I start a print, all of the kamp functionality is skipped (adaptive mesh, purge next to print, etc...). I tried an old SD image from early 2024, updated from there and it did the exact same thing. I also just noticed that the sb led's aren't changing from the normal rainbow cycling to the orange logo and white printhead lights like it used to. Maybe all the extensions aren't working? I also noticed that when my end_print macro is called the bed is not cooling down. It all used to work flawlessly... I'm not sure where to start with this.
I followed the kamp install closely and made sure PusaSlicer had label objects set to firmware-specific and Klipper was the selected g-code flavor. Klicky works perfectly for z-offset and QGL. Here's an example of what is in the console when a print is started:
9:26 AM
probe: TRIGGERED
9:26 AM
probe: TRIGGERED
9:26 AM
Probe already docked
9:26 AM
probe: TRIGGERED
9:26 AM
Homing Z
9:26 AM
Homing Y
9:26 AM
Homing X
9:26 AM
File selected
9:26 AM
File opened:stealthburner_printhead_rapido_v2_rear_cw2 _2.gcode Size:4316940
No errors, just nothing related to kamp
What do I look for from here?
My 2.4r2 has been a great workhorse for a few years now. It had klicky/z-cal and kamp running smoothly for a long time. I was recently away for several months, came back, did some prints just fine, then did a full update of every software component. Now when I start a print, all of the kamp functionality is skipped (adaptive mesh, purge next to print, etc...). I tried an old SD image from early 2024, updated from there and it did the exact same thing. I also just noticed that the sb led's aren't changing from the normal rainbow cycling to the orange logo and white printhead lights like it used to. Maybe all the extensions aren't working? I also noticed that when my end_print macro is called the bed is not cooling down. It all used to work flawlessly... I'm not sure where to start with this.
I followed the kamp install closely and made sure PusaSlicer had label objects set to firmware-specific and Klipper was the selected g-code flavor. Klicky works perfectly for z-offset and QGL. Here's an example of what is in the console when a print is started:
9:26 AM
probe: TRIGGERED
9:26 AM
probe: TRIGGERED
9:26 AM
Probe already docked
9:26 AM
probe: TRIGGERED
9:26 AM
Homing Z
9:26 AM
Homing Y
9:26 AM
Homing X
9:26 AM
File selected
9:26 AM
File opened:stealthburner_printhead_rapido_v2_rear_cw2 _2.gcode Size:4316940
No errors, just nothing related to kamp
What do I look for from here?
Last edited:
