Setting Nozzle Temp In PrusaSlicer Ignored By Mk3.5+
Hi -
I set the nozzle temp in PrusaSlicer in the Filament tab, like this:
I upload and run the bgcode file to my MK3.5 directly from PrusaSlicer via Prusa Connect.
It gets transferred to the printer just fine, but when I look at the front panel when it's warming up, it shows the default temp, not the temp I've set in PrusaSlicer:
The bed temp changes to the slicer setting, but the nozzle temp does not, it stays at the default value.
Funny thing is, the nozzle temp set in PrusaSlicer does show up in the Prusa Connect app details for the print:
I fix it by manually adjusting it on the front panel while it's warming up, and it prints with the temp I enter there, but not sure why it's ignoring the temp from the slicer.
Is there something else I have to set for the printer?
Thanks!
Best Answer by JoanTabb:
the printer does a two stage warmup to reduce chances of dots of filament during mesh bed levelling, if you wait, the printer will honour your print temperature
regards Joan
RE: Setting Nozzle Temp In PrusaSlicer Ignored By Mk3.5+
the printer does a two stage warmup to reduce chances of dots of filament during mesh bed levelling, if you wait, the printer will honour your print temperature
regards 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: Setting Nozzle Temp In PrusaSlicer Ignored By Mk3.5+
The 170 you see has nothing to do with the temperature you set in Slicer. It's what is set in your custom startup code for the warmup/mesh bed leveling process, to avoid leaking filament during that step. Once the bed has been leveled, the hotend will heat up to whatever temperature you have set in the filament settings for the first layer. It's similar to the load/unload process, which uses a given temperature for your filament type, not what is set in any specific profiles.
RE: Setting Nozzle Temp In PrusaSlicer Ignored By Mk3.5+
Oh, I didn't know that, thanks very much! 🙂