RogerWilco486
Posts: 2
Joined: Tue Jul 25, 2017 10:54 am

Re: Request: Firmware Retraction

Mon Jan 07, 2019 11:00 am

OP here, still waiting for this feature.

Eddiie
Posts: 6
Joined: Wed Sep 27, 2017 11:42 pm

Re: Request: Firmware Retraction

Fri Jan 11, 2019 12:17 pm

+100 for a checkbox that does the search/replace behind the scenes.
Why is this so difficult to add this?

alexspeller
Posts: 1
Joined: Wed Jan 23, 2019 5:50 pm

Re: Request: Firmware Retraction

Wed Jan 23, 2019 5:56 pm

I found, at least on the latest version, that the M101/102/103 generated more retracts than would otherwise be the case.

I fixed this by using some bogus retraction settings and replacing that instead, e.g. 0.1mm at 6666mm/min. Make sure not to set Z hop as that will come out as a separate move.

Then I replaced the actual retraction gcodes with this script:

Code: Select all

{REPLACE "G1 E-0.1000 F6666" "G10"}
{REPLACE "G1 E0.1000 F6666" "G11"}
This resulted in 25% less G10 calls in a sample test print, which came out looking better for it.

smoki3
Posts: 13
Joined: Thu Apr 19, 2018 3:28 pm

Re: Request: Firmware Retraction

Wed Feb 13, 2019 3:41 am

1+

Would be great if they can support this

Wallabear
Posts: 8
Joined: Wed Feb 13, 2019 4:33 pm

Re: Request: Firmware Retraction

Wed Feb 13, 2019 4:44 pm

I would really, really, REALLY like to see this feature add as well

dwallersv
Posts: 3
Joined: Tue Apr 16, 2019 12:17 pm

Re: Request: Firmware Retraction

Sat Jun 01, 2019 9:40 am

Another vote for a firmware retraction option.

The problem with post-processing substitution
--------------------------------------------------------------------

Can't use wiping and coasting features. With these enabled, the retraction is not always contained in a single extrusion G1 with the set filament length and feedrate. It often (most of the time) will be split among more than one G1 line, with the retraction distance split between them. These are the coasting and wiping moves.

So while the unretracts can be found easily (say, 1mm 20mm/s search for and replace "G1 E1.0000 F1200" with "G11"). You'll find there are very few matching "G1 E-1.0000 F1200" lines, but a ton of things like "G1 E-1.6667 F1200" a few lines back, combining a retract with a coast/wipe. Problem is, the retraction amount is not always the same.

Haven't tried the M101/2/3 approach -- will try it today. However, I'm curious as to how that will interact with coasting and wiping -- could end up with insufficient extrusion after extraction (G11 won't account for extra retract from coasting). Maybe it doesn't matter.

Leary
Posts: 3
Joined: Tue Apr 15, 2014 3:13 pm

Re: Request: Firmware Retraction

Mon Jun 03, 2019 8:51 am

+1 Please add support for FW retraction

maker2
Posts: 85
Joined: Sun Jul 19, 2015 8:05 am

Re: Request: Firmware Retraction

Thu Jun 06, 2019 11:55 am

+1 from me (and +several from my friends)

doing it with scripts is messy because you have to modify every single profile which inevitably leads to errors.

But Firmware Retraction is wonderful and is there really any other way to dial your hotend/filament combination in?

th0mpy
Posts: 1
Joined: Sun Jun 09, 2019 8:58 am

Re: Request: Firmware Retraction

Sun Jun 09, 2019 9:00 am

+1 for me too. I thought this would be kind of a standard thing.

Return to “Feature Requests”