You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to issue a M190 command in the start Gcode so that it waits until the bed is 1 or 2C lower than [first_layer_bed_temperature], then issue a M140 to let it heat up the rest of the way while my hotend gets up to temp.
Near as I can tell, this behavior isn't supported in Slic3r.
The text was updated successfully, but these errors were encountered:
I have considered implementing arithmetics. I have also considered implementing custom variables that you could associate to print and filament presets, so that you could call them in your Start G-code like [my_custom_temporary_bed_temperature].
Yes, that is a beautiful idea, @alexrj!
This would enable us to set a custom "chamber_temperature" in filament presets to use in the start gcode - a feature that isn't needed for the majority of the other 3D printers and therefore probably won't justify its own native parameter.
I really like the custom variable idea - sleek solution that can integrate well into the UI
I'd like to be able to issue a M190 command in the start Gcode so that it waits until the bed is 1 or 2C lower than [first_layer_bed_temperature], then issue a M140 to let it heat up the rest of the way while my hotend gets up to temp.
Near as I can tell, this behavior isn't supported in Slic3r.
The text was updated successfully, but these errors were encountered: