Firmware retraction retract/unretract independant feedrates
-
could you setup macros for that are executed for retract and unretract, that send gcodes for feedrate changes during the retract and unretract?
-
could you setup macros for that are executed for retract and unretract, that send gcodes for feedrate changes during the retract and unretract?
I don't think that would be wise, because there might be contention on accessing the SD card, so opening and reading of the macro file could get delayed if you are doing a file upload or download at the same time.
-
That's fantastic news! Thank you!
W3RDK, I have it already on my list to add another parameter to M207 to allow a different un-retract rate.
Tony, you can achieve the same effect by using M207 commands in your tpost#.g files, if all drives used by a tool need the same retraction parameters.
PS - M207 T parameter will be supported in the next 1.16 beta release, which will probably be beta 6.
-
could you setup macros for that are executed for retract and unretract, that send gcodes for feedrate changes during the retract and unretract?
If you use firmware retraction (G10) there is nothing to stop you sending M207 Sn.n Fnnnn from DWC during a print. In fact, it's the best way to to set your retraction IMO. I printed 2 "cubes" 4mm in X, 20mm in Y, and 20mm in Z spaced 100mm apart in X and simply played around with M207 until I had the minimum amount of retraction with no stringing. Repeat that with different speeds and temperatures and/or different filaments and you end up with the ideal retraction settings for every scenario in very little time.
-
Exactly. Although stringing is easily tuned out, it's zits left behind at the beginning of the next path after retraction completes that I find trickier to eliminate. In my case about -0.1mm un-retract does a good job reducing them for most PLA filaments I've tried.
Which brings up a good question…David, does RRF's implementation of M207 allow for a negative R parameter?
Here's an example, see the back of this Boon I recently printed on my Duet WiFi powered Kossel 250...there's a tiny bit of a zipper effect in some spots but for the most part, there's barely any sign of retractions. Absolutely no zits.
https://drive.google.com/file/d/0B4X2cVKW2B3sTUhKbUV2YS1mSUI2OUk3Zmg3eHdydWVRQmpv/view
-
Exactly. Although stringing is easily tuned out, it's zits left behind at the beginning of the next path after retraction completes that I find trickier to eliminate. In my case about -0.1mm un-retract does a good job reducing them for most PLA filaments I've tried.
Which brings up a good question…David, does RRF's implementation of M207 allow for a negative R parameter?
No, but I've just changed the code so that it does, down to minus the retract length.
-
Excellent, thank you! This firmware just keeps getting better and better.
I will be watching closely for the next 1.16 beta to come out. The last few betas have been working flawless for me on both my Delta and Cartesian printers.
-
I wonder if anyone else would agree, now that firmware retraction support is getting pretty configurable wouldn't it be nice to have GUI adjustments for it in the Print Status screen, similar to the feed rate, extrusion multiplier, and fan speed sliders?
Perhaps a section containing sliders for the retraction length, retract/advance speeds, and a little drop down/text field to enter the positive/negative un-retract length. Or is that a recipe for too much clutter?
-
1.16 beta 6 preview is at https://dl.dropboxusercontent.com/u/19369680/DuetWiFiFirmware.bin. Please note, the pin numbers used by M42 have changed in this release, see https://duet3d.com/wiki/Using_servos_and_controlling_unused_I/O_pins.
-
@ W3DRK Just out of curiosity, have you tried playing around with pressure advance (M572) and if so, did it do anything for you?
Ian
-
I did, briefly, with mixed results. The default setting of .1 seconds works splendidy on my Ord Bot, but I wasn't able to find a value that worked well with my Kossel so I ended up leaving it disabled.
-
I tested this on my Kossel last night and it worked perfectly. Thank you! Once it's released for the "legacy" Duets, I'll be using this on my Ord Bot as well.
1.16 beta 6 preview is at https://dl.dropboxusercontent.com/u/19369680/DuetWiFiFirmware.bin. Please note, the pin numbers used by M42 have changed in this release, see https://duet3d.com/wiki/Using_servos_and_controlling_unused_I/O_pins.
-
Update:
See David's post here: https://www.duet3d.com/forum/thread.php?pid=3931#p3931
