RE: Temperature not saved to gcode
via Prusa Slicer Git Hub.
If you open an issue there they may look at it, however since the prusa slicer 2.6.0 Alpha 6 firmware performed as you would like, I suspect they have alrady addressed the issue.
why don't you give 2.6.0 alpha8 a try, it will live on your PC, alongside the 2.5.2, because they use different directories.
Try the links at the bottom of this page
https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.6.0-alpha6
Regard Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Temperature not saved to gcode
Not a bug. You have ooze prevention active, which drops the temperature by 5 degrees.
Formerly known on this forum as @fuchsr -- until all hell broke loose with the forum software...
RE: Temperature not saved to gcode
Fuchsr, When I saw your comment knew that had to be it. I read the popup help for that setting. States it is applied when extruder is not active. Don't understand how that affects the initial temp and other overall temps. I'll keep it in mind. Thanks.
RE: Temperature not saved to gcode
Also, I checked gcode from 2.6. The temp is correct. So it is considered a fix. Used the generate gcode with verbose option enabled.
However, I did a quick search in the gcode to determine how ooze control was handled. This all I saw. standby_temperature_delta = -5 is part of the comments at end of gcode. That variable isn't used anywhere else.