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.
Sometimes cleaning stringing residures takes longer than printing itself. I use Paul&Florian's (great) settings with small changes. And those settings have all antioozing parameters in material definitions/jumps section zeroed. Sure low temp settings decreases ooze but doesn't eliminate it. It would be great to see this updated and have ooze-free printouts.
As to the problem you described I assume you play with push-on speed, pull-back speed and travel RPM settings. And push-on does not extrude enough material after the jump. Right?
The Pull-back Speed and the Push-On Speed determine the RPM rate with which the material is pulled back before the jump and pushed forwards again after the jump.
I started to wonder what does it mean "before" and "after" the jump. For how long are those RPMs executed? After all the jump is executed immediatly after extrusion ends.
I thought that maybe that is the time when Z-Jump is executed? So if the Z-offset is set to zero pull-back and push-on are effectively ignored and only travel RPM works.
To verify this I created in Netfabb two small cubes with a gap between them to make jumps and generated g-code (standard quality, hollow object) for them with the following settings:
You can clearly see z-offset before and after the jump (Z2.2500 -> Z3.2500 and back). But correct me if I'm wrong: extruder did not pull any filmanet. Pull-back value was ignored!
I did the same code for no z offset with the same result - no fiament retracting.
The only way I could make E values decrease was to set negative Travel RPM. At Travel RPM = -2 RPM code looks like this:
Fiament is retracted during the jump. But since there is no push-on after the jump extrusion starts with smaller E values than before the jump and thus with void in the nozzle.
That would explain the situation you describe, wouldn't it?
It's late and I might be missing something huge but it seems that push-on and pull-back settings are ignored altogether. That would be bug that makes restart of extrusion after a negative travel RPM jump impossible :-( Can anybody check my reasoning?
On top of that there is no comb feature in Netfabb - that makes stringing even worse.
Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more.
S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
(Sorry, was out of office when this released)
This update is for...
All UltiMaker S series
New features
Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
Recommended Posts
konrad 0
Hi Makerswamp,
Sometimes cleaning stringing residures takes longer than printing itself. I use Paul&Florian's (great) settings with small changes. And those settings have all antioozing parameters in material definitions/jumps section zeroed. Sure low temp settings decreases ooze but doesn't eliminate it. It would be great to see this updated and have ooze-free printouts.
As to the problem you described I assume you play with push-on speed, pull-back speed and travel RPM settings. And push-on does not extrude enough material after the jump. Right?
Netfabb's very laconic manual here
http://wiki.netfabb.com/Material_Settin ... for_RepRap
says:
I started to wonder what does it mean "before" and "after" the jump. For how long are those RPMs executed? After all the jump is executed immediatly after extrusion ends.
I thought that maybe that is the time when Z-Jump is executed? So if the Z-offset is set to zero pull-back and push-on are effectively ignored and only travel RPM works.
To verify this I created in Netfabb two small cubes with a gap between them to make jumps and generated g-code (standard quality, hollow object) for them with the following settings:
Jump speed 180mm/s
z-jump speed 20 mm/s
pull-back speed 400 RPM
z offset 1mm
push-on speed 400 RPM
Travel RPM 0 RPM
The result for one of the middle layers:
You can clearly see z-offset before and after the jump (Z2.2500 -> Z3.2500 and back). But correct me if I'm wrong: extruder did not pull any filmanet. Pull-back value was ignored!
I did the same code for no z offset with the same result - no fiament retracting.
The only way I could make E values decrease was to set negative Travel RPM. At Travel RPM = -2 RPM code looks like this:
Fiament is retracted during the jump. But since there is no push-on after the jump extrusion starts with smaller E values than before the jump and thus with void in the nozzle.
That would explain the situation you describe, wouldn't it?
It's late and I might be missing something huge but it seems that push-on and pull-back settings are ignored altogether. That would be bug that makes restart of extrusion after a negative travel RPM jump impossible :-( Can anybody check my reasoning?
On top of that there is no comb feature in Netfabb - that makes stringing even worse.
Edit: Only after writing the above I found confirmation from noone else but Paul http://groups.google.com/group/ultimaker/browse_thread/thread/7511401e952b586c/2c7df6ff0e8dca94?show_docid=2c7df6ff0e8dca94&pli=1. Note to self: use more Google BEFORE. It wouldn't hurt, though, if Netfabb manual didn't describe features that aren't implemented/are not working.
Link to post
Share on other sites