![]() I really wish this was more common.įor Cura you'd have to add it to the start gcode of the printer config and change it to suit every print since it doesn't have any filament specific settings unfortunately. In Prusa Slicer it's easy to configure this in the filaments tab in the custom gcode section. ![]() I don't think I can configure a slicer to send the proper M207 command (to configure retract lengths/speeds/z-hop) even with macros when it's set to do G10/G11 for firmware retract.) For other slicers, I don't said in retracts over Firmare or PrusaSlicer?: If there's a way to have Cura (the slicer I use) send it's profile configured retraction distances/speeds/zhop via M207, AND to use firmware retraction, but to NOT actually also do software retraction/zhop, then I'm not aware of it. Please note that I typed that I don't THINK its possible. That implies that for each print, I'd have to configure some filament specific things in the slicer, and different filament specific things via printer macros or console - which is just one more thing for me to forget. (In other words, I don't think I can configure a slicer to send the proper M207 command (to configure retract lengths/speeds/z-hop) even with macros when it's set to do G10/G11 for firmware retract.) ![]() I don't think it's possible to configure a slicer to send per filament retraction distances/speed/zhop in the header of a gcode file, and then only to use firmware retraction while printing the actual model. This includes nozzle/bed temperatures, speeds, and retraction distance/speeds. My reason is that when I slice a model, I have a group of settings tailored to a type of filament. I'll throw a different opinion into the mix: I prefer slicer retractions to firmware retractions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |