Sacrasang
commented
1 week ago I am experiencing the same behavior in version 2.2.0 with a different printer (a modified Ender 5 S1 running Klipper and using the klipper gcode flavor).
I think the issue is related to this machine's start gcode not including any specific instructions for temperature and is only a graphical error in the gcode reader.
My machine start gcode is:
start_print BED_TEMP=[bed_temperature_initial_layer_single] EXTRUDER_TEMP=[nozzle_temperature_initial_layer]
The absence of any start gcode defining the first or subsequent layer temps appears to cause the gcode reader to ignore subsequent temperature commands - representing the extruder temperature with whatever is defined in the start gcode, or 0 if otherwise not defined. The called in bed and extruder temps I am using are not registered by the gcode reader. When I send this print to the machine it heads up to the appropriate temperature defined by the filament profile and successfully prints.
I tested adding M104 S150 before my start gcode and this caused the gcode preview to represent the entire print as 150C. This also had no adverse impact on printer execution of the print. Changing the gcode flavor had no impact on the gcode preview or machine behavior.
The temperatures reported in the gcode preview do not accurately reflect the temperature instructions present in the gcode.
Is there an existing issue for this problem?
OrcaSlicer Version
2.2.0
Operating System (OS)
Windows
OS Version
Windows 11
Additional system information
No response
Printer
Creality K1, K1C, K1Max, K1SE
How to reproduce
Actual results
In dropdown menu print(nozzle) Temperature shows 0. Same steps with Creality Print not give this issue.
Expected results
The temperature dropdown menu in slicer preview screen must show the set temperature in the material profile. Printer must use the slicer temperature values.
Project file & Debug log uploads
Cube.zip
Checklist of files to include
Anything else?
Related issue: https://github.com/SoftFever/OrcaSlicer/issues/5491