Sometimes cura adds a .0 to the temperature, sometimes not

[luc_vienna 0]

It is hard for me to reproduce. After going to Cura 5.3.1, i started having a problem, an error when printing with Klipper. On ALL my printers (CR10 S pro, Ender 3 S1 pro)

It stopped printing before it had really started.

 

I found the error. In my printer start sequence I have added following line:

 

BED_MESH_PROFILE LOAD=default{material_bed_temperature_layer_0}

This used to translate in the gcode to:

BED_MESH_PROFILE LOAD=default62

as I have a Mesh profile called default62, it would load and use it and it would work fine.
Now i checked the gcode and it reads now: BED_MESH_PROFILE LOAD=default62.0

And that one does not exist.

So what I did is I created new profiles with the .0 at the end. default62.0 for PLA, default70.0 for PETG etc..
it worked for a day or two.. suddenly the same error:

I checked the gcode again.. and now it was back to default62 instead of default62.0 (in the meantime I had erased the profiles without the .0).

It seems that depending what printing profile i am using, it translates {material_bed_temperature_layer_0} to 62 or 62.0

 

As a momentary workaround i have now saved both mesh profiles, default62 and default62.0, but it is annoying not to know when it changes the output. (its probably a difference between float() and int() somewhere.

 

I had suspected that the printing profiles I had created in earlier versions of cura keep the 62, and that newly created profiles in cura 5.3.1 add the trailing .0

 

But it seems that i am wrong: i have just created a new profile, and it has NOT the trailing .0

Please help if someone knows what is going on.

 

YES I know i should write a completely different startup in a klipper macro, but as fast solution this has worked fine and was working for more than 6 months now. I can live with the doubled mesh profiles, but it would be a lot easier and give me a better feeling to know when it does one thing, and when the other.

 

Luc

Edited April 30 by luc_vienna