#[SOLVED] Tried my hand at printing two different colors on separate objects and it went badly...

1 messages · Page 1 of 1 (latest)

twin stirrup
#

Using Black ABS in leg1 and Grey ABS in leg2 I was printing two objects in black and two objects in grey. One of the objects failed bed adhesion, so I excluded the object. The Turtle went for the color change and instead of moving to the good object of the same color, it errored out on the excluded object and made some interesting noises as it failed out.

10:18 PM Move exceeds maximum extrusion (1.894mm^2 vs 1.440mm^2) 10:18 PM Move exceeds maximum extrusion (1.894mm^2 vs 1.440mm^2) See the 'max_extrude_cross_section' config option for details 10:18 PM leg1 is now loaded in toolhead

Was I dumb and missed something in the RTFM about excluding objects? Did I forget a setting change somehow to prevent the oopsie? <@&1304550334839918672>?

gritty harness
#

Not sure if anyone has tried printing different color objects during the same print yet and use exclude object to exclude one of the parts that messed up.

#

Were you printing by layer or object?

barren herald
#

Can you share a screenshot of the model(s) in the slicer for reference?

twin stirrup
gritty harness
#

I feel like this would of been better to print by object, would be way less waste. so it would print the first in one color then move to the second change color and print the other object in another color

#

Still don't know about excluding objects since I have not tried it yet with multicolor

twin stirrup
gritty harness
#

Its all good.

#

We all learning together

barren herald
#

This is an interesting situation to bring up. Something new

twin stirrup
barren herald
#

It’s good to see just have to understand what’s going on and work through it for the future

opal goblet
#

@twin stirrup Can you DM me the gcode you used and which object you tried to cancel?

#

You're correct that it would be better to print these seperately if they're completely different colors. As for the error, the exclude object code isn't able to ignore the now unneeded color change. What that message says to me is that upon starting the next object, klipper didn't have the correct previous and/or new position of the filament and tried to extrude too much. I have some ideas what it could be, but that would need some investigation and I won't say too much speculative here.

#

As for your setup, I wouldn't worry about changing anything. This is an interesting edge case with exclude object.

twin stirrup
sour current
#

I have had it do something similar when cancelling an object of another color. I think it's a slicer issue though. As mine still did a color swap, goes to the cancelled object, and then skipped back to the other object for another color swap. So even though the other color object was cancelled, it still did the filament changes between them. Which just made me cancel the entire print, because I figured that was pretty damn pointless. It didn't error out on me though.

twin stirrup
#

Mine did the color change, and immediately went to the canceled object. I cant tell if it was the BT or the Printer that made the gears grinding on filament noise, but it was screechy like a stepper motor under EXTREME strain. Then it failed out.

opal goblet
#

The behavior around excluding an object is a combination of klipper and how the slicer annotates the gcode. If you look in the file, you'll see EXCLUDE_OBJECT_START and EXCLUDE_OBJECT_END around the parts on each layer. Klipper can only ignore moves within those blocks and will execute everything else (like around layer changes, purges, color changes, etc.) and the actions performed by the AFC extension and macros.

candid badger
#

is this resolved now?

opal goblet
#

I think this can be marked as resolved or something indicating it's closed. It's not a box turtle issue.

candid badger
#

thanks.

#

[SOLVED] Tried my hand at printing two different colors on separate objects and it went badly...

broken dust
#

I've been having bad bad problems with this <@&1304550334839918672>

candid badger
#

you can for sure

broken dust
rapid idol
#

You can exclude object as normal

dense venture
#

Was that ever fixed?

#

There was a known issue at one point.

#

The issue wasnt in AFC.

rapid idol
#

The issue is only if you are doing single objects in one color and there’s a change between them

#

Normal multi color stuff works fine afaik

broken dust
# rapid idol You can exclude object as normal

ive tried it twice..... the first time it messed up the xcarriage and the second time was also really bad. it does weird stuff when you try to exclude a object in a multi color print.... like it loses calculations or something and ends up drill into the prime tower or something.... bad results considering whats happened

rapid idol
#

I think @opal goblet had something to do with that

broken dust
rapid idol
#

Scroll up in your thread, Troy explains the issue. It’s something with the exclude object stuff and not AFC

candid badger
#

i think the case was cancelling an object where that is the primary location of where the toolchanges happened

broken dust
rapid idol
#

You should be able to exclude an object that has changes as long as you aren’t print per object

#

That is my understanding of this

broken dust
dusk rivet
#

@zinc moss so should we be printing sequentially then instead of regular print all objects in order to cancel them?

zinc moss
#

@dusk rivet wrong tag i think Jimmy just said @opal goblet

dusk rivet
#

@opal goblet I want to pass this information off to AtomicVectorPlotter (mjonuschat) who has forked prusaslicer to prusaslicer BOSS edition. But I do not really understand the issue. If possible can you provide more information on what you believe is happening with the cancel object on multi-color multi-object plates please