Printer stopping mid-print
So, my printer just started stopping mid print for no apparent reason, and always stops at the same spot.
At first I thought it was something to do with the sd card but I bought a new one and nothing changed.
There is no errors, no warnings, and the print acts like it still going on but no flow or speed obviously (see image).
The printer was working the day before, no changes in slicer settings or anything.
Any suggestions?
59 Replies
"printer just stops"
"print acts like it is still going"
Not sure i understand, do you meant the webpage still shows progress, but the physical printer isn't moving at all?
Exactly. Sorry for the misunderstanding
And I can’t actually click pause nor cancel, only emergency stop works in that case.
Attached klippy.log, moonraker.log and the actual gcode
if the webpage is still up and progressing, then the raspi is still powered and communicating with the octopus. hm
Instead of individual files can you just drop your debug.zip in here?
Oh, sure thing.
here you go
Great. That has all the logs and cfg files, way easier 🙂
wait, that debug.zip is missing everything
What is your ratos version?
v2.1.0-RC3-26-g33980992
Where did that debug.zip come from?
nvm my bad
how do i get that from lmao
click 'Configurator' on left side, then you'll see a download button for "Debug Zip" on the left
ok now that makes sense lmao, sorry
no worries
So weird. Got a pic of where the printer stopped?
And have you tried slicing a different object and see if it halts?
Yup
It does halt
same layer height?
it stops right here
yes
T0 is white T1 is black
ah, I don't know much about the IDEX ecosystem, that reads like something is going weird with the toolhead change macro
I gotta take a cat to the vet for a checkup, but I'll think about it while I'm out. Think REAL hard about any changes like update to the slicer software, filament settings, anything
I did updated the slicer. Rolled back to original but still the same
When you say "print acts like it is still going", does it act like more filament is going down, like more layers are counting up?
Cause this really seems like it is stopping the print waiting for you to do something
No. It literally stops but the estimate time keeps increasing (check image for reference)
At this point the printer stopped at the specific point
The estimate time kept increasing but no flow nor speed
estimate time keeps increasing, like its going to take longer and longer? that makes sense as it isn't making progress and it knows it
Yup!
Triple check your printhead change macros, I'd guarantee the issue is there. I haven't messed with IDEX or filament changes before so can't offer any specific advice.
No, the thing is it gives the print as completed. I have added a message to end print gcode to debug it, and it actually deliveres that message
wow, thats seems extra weird then
100% lol
Gonna have to have someone else chime in, maybe @blacksmithforlife 🇺🇸 has some ideas
might be a bug in the idex post processor. Otherwise it sounds similar to when a slicer puts a pause in the code and the person isn't aware
It started happening out of nowhere, that’s why I’m finding it really strange
Ok so I think I got something @blacksmithforlife 🇺🇸 @TheTik
Moves exceeds maximum extrusion (4.527mm^2 vs 0.640)
See the ‘max_extrude_cross_section’ config for details
I enabled debug on console
just dont know its happening or how to fix it
does it happen if you try a print that only uses one printhead?
Same model single toolhead works perfectly fine
Just tested
So it is something with your change macro. I don't know enough to help with that specifically
Yup! Anyways
The max_extrude_cross_section didn’t showed up anymore but i still stops mid-print with Idex
I don’t know what else to try tbh
@miklschmidt @Helge Keck sorry for the ping guys. Mind to give me an hand here or what to look for?
Thanks a lot for the help @TheTik
sorry I couldn't help more, will monitor any answers so I can help the next guy
try to disable exclude objects
Tried it, didn't worked either
Thought it could be sd card but i bought a new one, cloned the old one to the new and issue remained
Update:
single color:
if I print only with T0 it works.
If I print only with T1 it works.
Doesn’t work with multicolor/idex
idk if it's something with toolchange or not, can't understand
I see you're using spoolman, any chance your spoolman instance is down?
I'd definitely start by disabling EXLCUDE_OBJECT (in your slicer), fix your skew profile loading (currently you load it manually in your start print, don't do that, set the profile in RatOS using
variable_skew_profile on gcode_macro RatOS), and remove the spoolman commands from you custom gcode.
The fact that it's pausing at the toolshift makes it smell like a spoolman issue.Sorry @miklschmidt I was installing the titanium tube and tuning everything.
I’ve done everything you told me to, and unfortunately didn’t worked.
That made sense to me theoretically, but didn’t worked unfortunately
But appreciate your time
I'll leave this here if someone wants to take a look
just generated that one again right now
Please try PrusaSlicer, you're running a beta version of Orca 2.3
There's a ton of invalid crap in your gcode, you have timelapse enabled in your slicer, but not configured so you're getting constant macro errors, you also have neopixels that fail to update all the time.
you're also triggering _ON_TOOLHEAD_FILAMENT_SENSOR_CLOG on both toolheads
I was using 2.3.0 beta and was working perfectly fine, this happened out of nowhere, with no apparent reason.
I've removed all gcode crap, timelapse etc, neopixel and sensor clog, still doesn't work.
This has to be an sd card issue
I cloned the old one to the new one.
Should I have had formated it in a specific format or..?
And don’t you think it’s strange only happening on tool changes? Running single completes the print @miklschmidt
@miklschmidt sorry for the ping again. works with prusa slicer.
but it was working with orca before, i've only used orca since i have this printer.
maybe you can guide me trough what should i look for here?
sorry again for the ping
If it was an "sd card issue", you would've just copied the corrupted file system to the new card.
sorry for the ping again. works with prusa slicer.Yeah thought so, it's definitely related to slicer configuration on tool changes. I don't know, you have a lot of custom stuff. Disable all of it, then add in one at a time until it breaks again?
slicer config is wrong
you have a M600 and the actual toolchange
M600 pauses the print
Exactly what I thought while doing it ahaha :kekw:
Well now that’s interesting!
Ahhhh
os.ratrig.com -> slicer config
:sadpepe:
I have exactly all the settings shown there
Don’t really know where does the M600 gets called
I mean, what setting calls M600
please share a 3mf
Here @Helge Keck
update:
I can now print with two toolheads on orca 2.3.0 beta 2
It seems like it was a bug or something leaving my gcode "cached"
Saving the machine profile with a different name as well as filaments did the trick.