Possible z height jump on a filament load failure query
 
Notifications
Clear all

Possible z height jump on a filament load failure query  

  RSS
Bazzalight
(@bazzalight)
Active Member
Possible z height jump on a filament load failure query

Have only been running the MMU3 for a week now (upgrade from MMU2) and on the rare occurrence (twice in about 1500 tool changes) of a filament load to extruder failure which required a manual fault clearance I am ending up with what appears to be a layer skip/jump on the restart.  I am just posting in case others have observed this happening. I will continue to investigate to see if a slicer/octoprint or other factor is at play. Probably just chance but both failures at about 50mm object height (filament load failure should be independent of z height).

Otherwise the MMU3 has been working really well !

cheers Barry

Posted : 02/11/2023 8:24 am
NotJannet
(@notjannet)
Eminent Member
RE: Possible z height jump on a filament load failure query

I've experienced this multiple times now, except it's been going down.

I've been getting a lot of load failures (some are just due to the filament slipping out the back of the MMU during printing, others I believe it's getting stuck in the PTFE tube leading to the hot end, but past the extruder gears so the filament sensor says its loaded fine) and 4 times this week, after successfully completing a filament load with my help it has then buried the nozzle into the purge block when it tried to continue printing.

The only thing I can imagine causing this is a bug in the firmware. I have now made an issue report: issue 4504

Posted : 19/11/2023 11:26 am
Bazzalight
(@bazzalight)
Active Member
Topic starter answered:
RE: Possible z height jump on a filament load failure query

I haven't had a further problem since I first posted (as I have had no load fails to check the recovery).  I have also since upgraded from 3.13.1 (3.0.0) firmware the latest 3.13.2 (3.0.1) . I think my load fails were more due to bad filament (old and brittle) however it was the recovery from the load failure that caused the problem. 

Also my machine config may be a little different to others as when I upgraded from MMU2S to MMU3 I did not change the extruder chimney stack from the Mk3S hardware (I did not upgrade to the Mk3S+ version which looked to me was reverted to the MK3S type in the MMU3 conversion instructions).

Will post again if the problem reoccurs.

cheers

 

Posted : 19/11/2023 11:47 am
Bazzalight
(@bazzalight)
Active Member
Topic starter answered:
RE: Possible z height jump on a filament load failure query

I have attached an example of what appears to be a layer skip in a MMU3 print.  I wasn't watching the printer at the time so I am hypothesising that there was a loading problem which was automatically recovered by the printer but skipped the layer.  (In the pic the light brown had the load fail, skipped the layer, perhaps tried to print the next light brown layer, changed tool head to the dark brown which printed Ok and continued on.) 

I will reprint just to make sure it is not a gcode issue...

Posted : 22/11/2023 3:17 am
BaconFase
(@baconfase)
Estimable Member
RE: Possible z height jump on a filament load failure query

That usually means you had some sort of tangle in your spool so it couldn't pull filament in to extrude for a partial layer or more. Then at some point the printer literally pulled through the tangle and resumed as normal.

.Printables.

MK3S MMU2S, XL-5T

Posted : 22/11/2023 5:05 am
Bazzalight
(@bazzalight)
Active Member
Topic starter answered:
RE: Possible z height jump on a filament load failure query

Thanks but no tangle in this case. MMU3 firmware has automatic re tries to load the filament (different to MMU2) which is what I assume it did for this case. if it doesn't succeed it stops and prompts for manual intervention (which has happened in the previous occurrences of the issue)

Posted : 22/11/2023 5:13 am
BaconFase
(@baconfase)
Estimable Member
RE:

I'm not claiming a feed error. What I'm saying it loaded fine, but at some point afterwards, while printing that layer, filament stopped flowing. In my experience usually a filament tangle (or filament sticking to itself) because nozzle clogs would affect everything afterwards not just a single color on a single layer. But since the filament sensors are on or off rather than detecting flow, the print continued on "without error" resulting in a skipped layer. That layer's filament retracted fine and when it was its turn again to be fed the speed/acceleration was able to pull through the "tangle" and resume as normal.

Its very possible that it was something else. But I've never experienced anything similar which only affects one color (one spool) for just a partial, or more, layer.

The MMU will never just skip a layer esp if there was an error. It will wait for hours and hours requesting manual intervention.

 

.Printables.

MK3S MMU2S, XL-5T

Posted : 22/11/2023 8:48 pm
Share: