Ultimaker uses functional, analytical and tracking cookies. Tracking cookies enhance your experience on our website and may also collect your personal data outside of Ultimaker websites. If you agree with the use of tracking cookies, click “I agree, continue browsing”. You can withdraw your consent at any time. If you do not consent with the use of tracking cookies, click “Refuse”. You can find more information about cookies on our Privacy and Cookie Policy page.

Share this post

Link to post

Share on other sites

I'm confused too. I usually do all-at-once. The 2 or 3 times I didn't it "primed" right over part of my second print and made a bit of a scary mess and dragged it around while I tried to grab it with my fingers.

The gcode shows retract only. Maybe look at some more gcode before and after this bit?

Other (competing) printers/slicers do the start of the "skirt" near the front edge of the printer - a line maybe 50mm long to clean the nozzle before starting the skirt.

I don't want to always have to grab the initial prime with my fingers. Especially yesterday when I was trying to talk to people at a show at the same time.

Share this post

Link to post

Share on other sites

Oh! Yes! Genius. It's probably a software endstop. What a stupid feature for the E axis. There are other solutions such as put it in "relative" mode.

Can you verify this fix? I'm away from home until late tonight. If you verify it we should alert Daid. This bug has been around for a long time but "one-at-a-time" is not done all that often - probably because of this bug!

Share on other sites

I also tried inserting an extra G1 command with no effect. edit: I probably should have made the first G1 command "G1 F2400 E0" and the second "G1 F2400 E-4.5" edit: still didn't work. (BTW, based on the results of my last trial, I don't think it is a soft stop issue.)

IIRC correctly, there is a command console in Cura for manually entering G-Code. I think I need to spend some time playing with that to see if I can figure out what the problem might be. However, right now I have some other tasks I need to do.

I just made a quick test with my UM1 with two simple objects 'one at a time'. The GCODE (sliced with Cura 14.01) included the retract and priming command as posted above. The UM performed both retract and priming when changing from one object to the other. It's the same directly via USB and via SDCard/Ulticontroller.

Do you use the standard Marlin or a personalized version?

Share this post

Link to post

Share on other sites

I just made a quick test with my UM1 with two simple objects 'one at a time'. The GCODE (sliced with Cura 14.01) included the retract and priming command as posted above. The UM performed both retract and priming when changing from one object to the other. It's the same directly via USB and via SDCard/Ulticontroller.

Do you use the standard Marlin or a personalized version?

I use the standard Marlin.

I patched it when I first got the UM sometime in late Nov or early Dec.

However, it did just occur to me that I had to install Cura on a new computer to try printing directly and when I did that, I went ahead and updated the firmware again. It seems possible that may have solved the problem. Perhaps it wasn't flashed correctly the first time, or there was an update between then and now. That might explain why the last bit of code ran without issue.

Edit: I ran the original code again this morning and it now seems to be doing retractions between parts. I guess I will never know for sure what the problem was, but I am guessing the firmware flash fixed it.