So Klipper was unable to set the chamber temperature…
However, if I select a temperature from the dropdown at the right side to the ‘heater chamber’ line, the command issued is:
…and this works fine!
So why not when I choose a preset?
It’s obvious that the preset method gives a wrong heater name “heater_generic heater_chamber” since the name is only “heater_chamber”
How to fix this? Is it a bug?
I’ve got no macro’s doing something with temperature…
Can I alter the way the commands are formed for this preset manually?
I see in the screen shot, the wrong name “heater_generic heater_chamber” is displayed…
That works, and I’ve unchecked the chamber temperature in the preset…
So it’s a bug then really?
Not to be able to set the chamber temperature in a normal fashion?
heater_generic tells Klipper, that the macro is one for heaters. heater_chamber is it’s name. So when the name occurs, Klipper knows that it is a heater macro.
If I know a person whose name is Fredrick, I do not call him “person Fredrick”. I just call him Fredrick.
Now you have a heater_generic whose name is heater_chamber. Do not call it “heater_generic heater_chamber.” Just use the name heater_chamber. So your commande would be
Well, if I understood @wd73_NL correctly, then the issue is not about building the command manually.
It is about using the built-in function in the web interface, which seems to be issuing the wrong command.
Well, if I understood @wd73_NL correctly, then the issue is not about building the command manually.
It is about using the built-in function in the web interface, which seems to be issuing the wrong command.
That is exactly the point!
And I didn’t think of it as a Mainsail bug when I posted it here on the group, so that’s my bad. I will post the bug for the Mainsail crew.
So indeed a bu, but not a Klipper bug… can be closed now