Need help configuring KAMP

[mbunjes]

Hi, I installed KAMP and all went well, no errors. However it doesn't work  I'm a bit at a loss what exactly to put in my PRINT_START macro .
I read somewhere that the only thing you need is bed_mesh_calibrate but that's exactly what it does : it calibrates the whole bed.

I would like to know what exactly to put in my printer.cfg. 
I have include KAMP_Settings.cfg and eclude_object

I uncommented the features I want in kamp_settings_cfg

What else do I need ?

[claudermilk]

Did you turn on the label objects option in your slicer?

In my print_start I just have calls to BED_MESH_CLEAR, then BED_MESH_CALIBRATE. Later I call the SMART_PARK to position the nozzle while doing final heating and finally LINE_PURGE (for whatever reason VORON_PURGE stopped sticking much and goobered up my first layer as often as not).

[mbunjes]

9 minutes ago, claudermilk said:

Did you turn on the label objects option in your slicer?

Yes, I did. And I have exactly the same calls. Aren't they supposed to turn orange when you've entered them ?

[Dirk]

I had to follow the 'manual'.

First get the 'exclude objects' to work (add [exclude_object] somewhere below the include lines in printer.cfg.

Then add [include KAMP_Settings.cfg].

Open the file KAMP_Settings.cfg and customise if necessary.

All you need to do to activate the script, is to call BED_MESH_CALIBRATE in your print_start macro.

This is overridden in their code, to recalibrate according to the objects you want to print.

Ah... I also had to add M117 somewhere before the start GCODE. I believe it is sometimes necessary to 'wake up' klipper? so it starts the exclude_object recognition.

Mine is right there in superslicer in custom_g_code under printer settings. Until I added M117 there, exclude objects wouldnt work for me

_________________

M117 
print_start EXTRUDER={first_layer_temperature[initial_extruder] + extruder_temperature_offset[initial_extruder]} BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature]

_________________

hope it helps

 

[mbunjes]

Alright, going to try the M117 now.

[mbunjes]

Unfortunately, it's not working. It's just doing a regular bed mesh.

In the Fluidd console I saw the line "No objects detected! Check your gcode and make sure that EXCLUDE_OBJECT_DEFINE is happening before BED_MESH_CALIBRATE is called. Defaulting to regular meshing.

I do not have EXCLUDE_OBJECT_DEFINE in my printer.cfg, only EXCLUDE_OBJECT. What does it mean ?

And it's here right at the beginning of my printer.cfg and BED_MESH_CALIBRATE is somewhere in my print_start macro 

[Dirk]

KAMP works apparently by using the exclude_objects system from Klipper... It is explained in their documentation.

I wrote also in my previous post: add [exclude_object] in printer.cfg

mine looks like this:

 

-----------------------

[include mainsail.cfg]

[include stealthburner_leds.cfg]
[include NozzleScrub.cfg]
[include lcd_tweaks.cfg]
[include KAMP_Settings.cfg]

#enable object exclusion
[exclude_object]
----------------------

make sure you enable labeling in superslicer.

And done.

Oh, do not leave out the m117  

Good luck

 

 

[mbunjes]

Yes, mine looks exactly like that.

Labels is enabled in SS.

I have added M117

It does not work

[Dirk]

Hmm.... the error message you get (defaulting to regular meshing) suggests object exclusion did not work.

When I did it, I had the same until I added m117 and a restart of the printer.

I just checekd the KAMP github again.. 

- [exclude_object] in printer.cfg - you have

- SSlicer object labeling is enabled.

- did you also add the section:

 

[file_manager]
enable_object_processing: True

in moonraker.conf?

 

 

 

If you did all this and object exclusion is still not working, then I am out of ideas (except looking online to similar cases).

 

 

 

[mbunjes]

It could be as simple as shutting everything down and restarting. I'll try that in a minute.

[mbunjes]

Egg on face  That was the solution. It's working flawlessly now.

One question : In Fluidd's gcode proview there's a difference: there's a blue line around the model and a blue spot in the middle that when clicked asks whether I would like to exclude this object.
 

What's the meaning of this ?

[mbunjes]

And line purge is not working. Smart park is.

[Dirk]

Yeah... The first thing a helpdesk worker tells you to do: did you plug the cable in, second is: did you restart the computer?

I do not use fluid. I assume it is similar to mainsail. Slice multiple objects, more than a few and then see what happens. I guess you need the experiment. The whole idea of object exclusion is, to 'stop printing spaghetti'. So when there is a failed object (during the print you see it warping or losening from the plate) , and the rest is printing well, you have the chance to stop this object only from printing.

This is the API KAMP uses to have a small part of the bed meshed.

Line purge did not work for me either. I use the voronpurge. much cooler. You have to play with the settings. For me initially it was too thick and too close to the printing area: the stealthburner would hit the purge during printing of the skirt.

So... I would say, experiment a bit

Good luck

[mbunjes]

Thanks, I will of course, have been experimenting for the past 10 years 

[claudermilk]

23 hours ago, mbunjes said:

Egg on face  That was the solution. It's working flawlessly now.

One question : In Fluidd's gcode proview there's a difference: there's a blue line around the model and a blue spot in the middle that when clicked asks whether I would like to exclude this object.
 

What's the meaning of this ?

"Reboot fix everything!" 

That blue outline shows the defined object. The slashed circe in the middle is where you click to exclude the object. It's such a valuable addition to Klipper; I've lost count of the plates saved from failure due to one or two small parts.

For the line purge, did you uncomment the include for line_purge.cfg? Line and Voron purge are different files.

[mbunjes]

Thanks, I understand

Yes, I uncommented line_purge.cfg

Edited December 16, 2023 by mbunjes

[claudermilk]

That's kind of weird on the purge not working. For me KAMP operated as advertised: make the settings changes as directed and then it just works. I even decommissioned an earlier, more complex config, adaptive bed mesh to switch to KAMP.

[PFarm]

On 12/16/2023 at 1:24 PM, mbunjes said:

Yes, I uncommented line_purge.cfg

Did you remove the space between the number sign and text, the text needs to turn green.

Edited December 18, 2023 by PFarm

[mbunjes]

14 hours ago, PFarm said:

Did you remove the space between the number sign and text, the text needs to turn green.

yes, I did.

I get the following message in my console :

max_extrude_cross_section is insufficient for purge, please set it to 5 or greater. Purge skipped.

It would be great if they would tell where to set that, as it is it just baffles me ?

 

[PFarm]

2 hours ago, mbunjes said:

max_extrude_cross_section is insufficient for purge, please set it to 5 or greater. Purge skipped.

It is in your printer.cfg under the extruder section.

[mbunjes]

Ah great, thanks

[claudermilk]

20 hours ago, PFarm said:

It is in your printer.cfg under the extruder section.

It's the last line, max_extrude_cross_section, you want to look at there, not the underlined microsteps. 

[mbunjes]

Yeah, I got that. It wasn't in my printer.cfg so I had to add it.

[AcidNight]

 

Hello, I came across your post and I have exactly the same problem except that everything is ok...

The bed Mesh is done over the entire bed, but the purge line is well placed next to the impression at the distance that I put it...

- [exclude_object]
   In printer.cfg => OK

- [file_manager]
   enable_object_processing: True
   In moonraker.conf => OK

- labeling objects is active
   In Orcasliser => OK

- M117
   In Orcasliser => OK

- [include KAMP_Settings.cfg]
  [include ./KAMP/Adaptive_Meshing.cfg]
  [include ./KAMP/Line_Purge.cfg]
    => OK

- BED_MESH_CALIBRATE
   In the start_print macro => OK

No error message and the first layer is perfect, just that it is not the adaptive part of the bed

 

[MrSprinklz]

5 hours ago, AcidNight said:

Hello, I came across your post and I have exactly the same problem except that everything is ok...

The bed Mesh is done over the entire bed, but the purge line is well placed next to the impression at the distance that I put it...

- [exclude_object]
   In printer.cfg => OK

- [file_manager]
   enable_object_processing: True
   In moonraker.conf => OK

- labeling objects is active
   In Orcasliser => OK

- M117
   In Orcasliser => OK

- [include KAMP_Settings.cfg]
  [include ./KAMP/Adaptive_Meshing.cfg]
  [include ./KAMP/Line_Purge.cfg]
    => OK

- BED_MESH_CALIBRATE
   In the start_print macro => OK

No error message and the first layer is perfect, just that it is not the adaptive part of the bed

Have you rebooted the pi since adding the adaptive meshing? Not just a firmware restart, a full reboot or power down cycle?

[AcidNight]

On 22/03/2024 at 19:54, MrSprinklz said:

Avez-vous redémarré le pi depuis l'ajout du maillage adaptatif ? Pas seulement un redémarrage du micrologiciel, un redémarrage complet ou un cycle de mise hors tension ?

 

Yes and quite a few times xD

I see in the console that everything arrives well as well as the print size data but directly leaves in full without any other error message or anything...