Closed fire1ce closed 1 year ago
I'm not sure I understand the request. Are you asking for two additional parameters for unloading speed and length? If so, I guess I'm not clear on what value there is in having them different for unloading versus loading. Or maybe I'm missing something?
@jschuh about the differents for unloading/loading is not critical. the value that im realy missing is "variable load unload temperature" that i can predefined as a default. right now it usses the minimum temp + 5. is that posable to add?
Let me think about it. It would be easy enough to add, but my concern is that it doesn't really make sense for multi-extruder setups and that the number of config parameters keeps growing unbounded.
Let me think about it. It would be easy enough to add, but my concern is that it doesn't really make sense for multi-extruder setups and that the number of config parameters keeps growing unbounded.
Sure. By the way, you can maintain the same logic with the minimum temperature. For example, if the default temperature is set to 0 (below the minimum) in globals.cfg, it will execute the same logic as it does now. If the value in the overriding config is above the minimum temperature, then it will use that value.
Yes, that's how all the options that derive their defaults from config settings work. The issue in this specific case is that it introduces a potential discontinuity between having a single global option versus behavior derived from per-extruder settings.
I decided to land it as 8c13bd30a5aeb839ff1d76fcbccf087c682058bf along with some other changes today.
thanks. much appreciated!
Hey @jschuh thanks for your work!
I would like to ask if it's possible to add the ability to set the following (example provided at the bottom) parameters for the Load/Unload filament? The issue I have is that I can't set the desired parameters as default values right now, and when using KlipperScreen, it's a pain to enter the values via the "macros" menu, since it already has "load" and "unload" menus built-in which will execute the macro with the "minimum" calculated parameters.
Example for globals.cfg (part of them already exists)