[explained] not BUG on temperature settings

fcwilt

@c310 I believe it is working as designed since you can have more than one tool.

Simply setting the temperature and activating that tool might not be appropriate.

However since there is only one bed it is safe to activate it.

Frederick

dc42

That's correct, in RepRapFirmware setting a tool temperature is a separate operation from activating the tool.

c310

ok, perhaps if there is only one tool, it can activate than

dc42

@c310 said in [explained] not BUG on temperature settings:

ok, perhaps if there is only one tool, it can activate than

Users of printers with only one tool often put a T0 command at the end of config.g.

Danal

@dc42 said in [explained] not BUG on temperature settings:

Users of printers with only one tool often put a T0 command at the end of config.g.

Because NOT having any tool active causes a lot more weird things than temp not "activating itself". Like no moves, etc. Therefore... very important to have an "active" tool, even on printers that only have one... in short: Last command in /sys/config.g should be "T0".

DocTrucker

Wouldn't it be better to have T0 in your start gcode, or setup macro if you have it?

dc42

@doctrucker said in [explained] not BUG on temperature settings:

Wouldn't it be better to have T0 in your start gcode, or setup macro if you have it?

Yes, that's what I do.

wilriker

@doctrucker said in [explained] not BUG on temperature settings:

Wouldn't it be better to have T0 in your start gcode, or setup macro if you have it?

But slicers (at least some of them) will heat up to temp before calling the start codes. So in case there is no tool selected wouldn't this fail then?

dc42

@wilriker said in [explained] not BUG on temperature settings:

But slicers (at least some of them) will heat up to temp before calling the start codes. So in case there is no tool selected wouldn't this fail then?

That's correct; although if you put your own temperature-setting commands in the start GCode, most slicers will spot this and not insert their own.

To help work around the problem of tools not being selected, if M109 is received with no tool selected, RRF automatically selects the tool referred to in the M109 command if there is one, or the lowest-numbered tool if there isn't.

wilriker

@dc42 said in [explained] not BUG on temperature settings:

That's correct; although if you put your own temperature-setting commands in the start GCode, most slicers will spot this and not insert their own.

They would - if my start code would not be just a

M98 /sys/print_start.g

To help work around the problem of tools not being selected, if M109 is received with no tool selected, RRF automatically selects the tool referred to in the M109 command if there is one, or the lowest-numbered tool if there isn't.

OK, that one might come in handy then, thanks!

Danal

@doctrucker said in [explained] not BUG on temperature settings:

Wouldn't it be better to have T0 in your start gcode, or setup macro if you have it?

As vs having T0 at the end of config.g?

Well... slicer provided start G-Code would be an OK place for T0, as long as you never issue any commands, say with DWC, prior to printing something...

IMHO, config.g covers more ground in terms of typical "use cases". ("User Stories"?)

DocTrucker

...but it leaves the heater permanently active.

I've never had T0 in my config and it's caused me no trouble.

Phaedrux

@doctrucker what's wrong with leaving it active? It's still off as long as no temp is set.