Exclude object still tries to extrude but without moves

[trxgt05]

Basic Information:

Printer Model: Makertech Proforge4
MCU / Printerboard: BTT Octopus_MAX_EZ
Host / SBC: RPi 5 8gb
Can post log later if needed but don’t have access rn

Describe your issue:

I’ve noticed that when I exclude an object, even though the printer avoids printing that object, it appears to try and purge the amount of filament it would have used on that object. Not only is that messy, it also kills prints if that amount exceeds the max extrude only setting.

Is this a bug in klipper or do I have bad settings somewhere? I’m using prusa slicer and I have it configured to use relative extrusions so it shouldn’t be a case where a later extrude command tries to extrude all that distance at once.

[lucaciresearch]

This might be a slicer misconfiguration. If the slicer is using extruder absolute positioning, this exact thing can happen.

Can you post an example gcode so we can check if absolute positioning is used? The setting might be overriden by another.

[trxgt05]

Good thought. There is an M83 at the beginning of the gcode, but there are not M82s anywhere so it stays as relative extrusion

[lucaciresearch]

I see you have multiple tools. I’m just wondering, can M82/M83 setting be on a pertool basis? Meaning you have to configure it for each tool?

Also, even if you have a single M83, remember that this setting is saved when doing SAVE_GCODE_STATE and similar. It could be that a state that has absolute positioning is restored at some point, esp. when doing a exclude object. Check your gcode macros for such a possibility.

[trxgt05]

I’m not 100% certain how klipper implements M82/M82, but I suspect it just applies to the active tool because I’m not aware of any extrude commands that work for non-active tools. Being an M code means it’s a machine code so it should affect any extrude commands which would be given to the active tool.

Interesting thought on the save states though. I’m thinking if something like that was the case, all subsequent extrusion would be messed up since the gcode is giving it increments and those interpreted as absolute would pretty much keep the extruder stuck in a 0-1mm range. Unless klipper does something weird with entering and exiting exclude object that I have no control over.

But regardless absolute extrudes interpreted as relative could possibly reproduce this, but in my case I have relative extrudes and those interpreted any other way would give different results than what I see

[NiXXiN]

I have a similar issue. Whenever I have a multipart print job with color changes sometimes after the color change when I resume the job the extruder goes to the location of the first part and extrudes on the way.

[EddyMI3D]

@NiXXiN

I have a similar issue.

Either it is the same or it is not.
In your case it is not. So please open a new thread with all the requested information.