Honour destring trigger conditions when using firmware retraction (G10/G11 in marlin)

[Len Trigg]

I have recently switched to using firmware retraction in Marlin, which allows the prime and suck distances to have independent speeds and to be fine tuned mid-print. KISSlicer has an option to enable this in Printer -> Firmware -> Mark Path Start/Stop -> G10/11, so I though I would try it out.  However I was surprised to find that KISSlicer seems to issue these commands *every* time the extruder stops/starts, rather than only those times when destring would be triggered. That is, it ignores the destring Min Jump and Trigger parameters, and results in more retractions than are needed. 

I guess it probably isn't quite right to call the current behaviour a bug but it would seem to make more sense if firmware retractions were able to follow those trigger settings. Perhaps this could be considered a request for enhancement for 1.5+ :-)

Cheers,

Len.

[Rick Zehr]

Thanks for pointing this out - I'll give it a try with my Ultimaker 2, to enable on-the-fly tuning...

[Rick Zehr]

Doesn't seem to work very well. When I turned G10/11 on, it double-retracted and left a big blob. I set retraction settings on Material to 0 retraction, and got inadequate retraction - a smaller blob.

Looks like the retraction settings on the Material tab work much better than Marlin's.

[Len Trigg]

I'm not sure what version of marlin you are running in the ultimaker 2 or how you have configured your firmware retraction, but it sounds like it's just not set up properly. I'm using the main github Marlin from a few months ago, and have had no problems with firmware retraction, but am only using it with Slic3r and Skeinforge, not KISSlicer due the problem I mentioned in the original post. Assuming your version of the firmware supports it, did you set the retraction speeds and distances, either in gcode or via the LCD?

Cheers,

Len.