Temperature Controllers Auto-Added

[nopick]

I prefer to run without temperature controllers so, I delete them from my processes. Since upgrading to V3, the controllers are added back to my processes every time I re-launch the application.

Is anyone else experiencing this? Have you found a way to prevent it?

Thanks.

Guy

[KeyboardWarrior]

If you go to your Scripts tab-->Starting G-Code and place in:

; [extruder0_temperature]

That commented out line will prevent the software from putting any heating commands in your g-code file (since the software will think that because you are referencing the [extruder0_temperature] you are in charge of your own heating commands, but since it's commented out it will have no effect on your print.

Using [extruder0_temperature] and [bed0_temperature] are traditionally used when you want to run commands prior to heating up.

[nopick]

Thanks. I will give that a try. It is just strange that the controller is added back to the process after I delete it. That is a change from the previous version.

Thanks again!!

[MichaelHerron]

Thanks. I will give that a try. It is just strange that the controller is added back to the process after I delete it. That is a change from the previous version.

Thanks again!!

I've reported this in another thread, but i've actually had it REMOVE temp controllers from my script. (and not add any back in, thus resulting in filament jams, etc)

I've seen it add temp commands BEFORE the start script, but removing from the middle of the script seems a bit extreme...

[nopick]

Adding ; [extruder0_temperature] at the top of the start gcode seems to work.

I would prefer that when I remove the temperature controller in the setup window, it does not get re-applied automagically. The previous version did not add them after I removed them. This version shouldn't do it either.