PrusaSlicer 2.0 - Hot end not heating up?
So the new slicer is rather nice and i like how FAST it slices now as i tend to have huge models,
But i have noticed a problem, after slicing the model and sending it to octoprint, Octoprint
goes Shuts down after bed heating because it does not Turn on the hot end. I watched the temp
monitor and the line for Target hotend goes Straight up but the actual heat does not rise and
octoprint throws an error saying shutting down due to extruder below min temp because its not
heating it up, i have to reslice many times before it does work, Other Slicers do not have this problem
from the temp graph it shows it didnt even try, but the console window is showing otherwise that the target is 215.
anyone else with this problem? i can provide the GCODE that was sliced if anyone wants to look at it
RE: PrusaSlicer 2.0 - Hot end not heating up?
Have you tried printing the gcode without going through octoprint (via SD card). The hotend may be broken in which case its not software but hardware. If it works from SD card then that rules out an issue with the printer itself and leaves you debugging your octoprint setup.
RE: PrusaSlicer 2.0 - Hot end not heating up?
Just to note this happens only with prusa Slicer 2.0, not with cura or the old Slic3r. Hot end works fine, and sd card isnt configured. Right now im printing fine with a cura code.
RE: PrusaSlicer 2.0 - Hot end not heating up?
Not much point in trying to guess what the problem is without sufficient information.
So, can you please zip up the G-code file and attach it to a post.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
RE: PrusaSlicer 2.0 - Hot end not heating up?
alright here is the gcode! nana2_1
im not very good at looking Gcodes so hope it helps, its right after i heat the bed it fails to heat the hotend
RE: PrusaSlicer 2.0 - Hot end not heating up?
This is not the usual startup gcode generated for a Prusa printer. Where did your customized startup gcode come from? It looks like samples I've seen for Creality printers.
RE: PrusaSlicer 2.0 - Hot end not heating up?
Your startup gcode is a mess. For whatever reason, the nozzle temp isn't set until after the prime lines (2 in this case) are attempted.
; Filament gcode
M109 S215 ; set temperature and wait for it to be reached
I suspect octoprint is seeing it attempt to extrude those lines before the nozzle is up to print temp and throws the warning.
Try printing from SD to eliminate any octoprint weirdness but I'd still expect it to fail.
Copy over or install the correct startup gcode for your printer from a slicer that works.
RE: PrusaSlicer 2.0 - Hot end not heating up?
I suspect octoprint is seeing it attempt to extrude those lines before the nozzle is up to print temp and throws the warning.
No, this is a message from the printer which is then being displayed by Octoprint and (I would guess) on the LCD.
The printer will not allow extrusion below (I think) 170 degrees, although this can be changed with an M302 command.
So your investigation into the G-code is very relevant and it's the non-standard start G-code causing the problem.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
RE: PrusaSlicer 2.0 - Hot end not heating up?
thats odd cause i dont have a M109 in my Filament GCODE
this is all of my Gcode here
M117 Print Starting...
M75 ; Start Print Timer and Engage Fil Sensor if USB Printing
M84 E ; Disable E Motor for probe accuracy on direct drive systems
M117 Antiblob retract...
G92 E0 ; Reset Extruder distance to 0
G1 E-2 ; Retracts filament to prevent blobs during probing
G92 E0 ; Reset Extruder distance to 0
M117 Homing All...
G28 ; home all axes
M117 Homing Z Probe...
G28 Z ; home z again
M117 Generating mesh...
G29 T; auto bed leveling
M117 Heaters Recovering...
G4 S10; wait for heaters to recover
M420 Z0; Z fade
M117 Purging extruder...
G92 E0 ; reset extruder
G1 Z5.0 F3000 ; move z up little to prevent scratching of surface
G1 X10.1 Y20 Z0.3 F5000.0 ; move to start-line position
G1 X10.1 Y200.0 Z0.3 F1500.0 E15 ; draw 1st line
G1 X10.4 Y200.0 Z0.3 F5000.0 ; move to side a little
G1 X10.4 Y20 Z0.3 F1500.0 E30 ; draw 2nd line
G92 E0 ; Reset Extruder distance to 0
G1 E-2 ; Retracts filament to prevent blobs
G92 E0 ; Reset Extruder distance to 0
G1 Z1.0 F3000 ; move z up little to prevent scratching of surface
RE: PrusaSlicer 2.0 - Hot end not heating up?
might suspect that its the G4 S10; wait for heaters to recover thats causing it then.
RE: PrusaSlicer 2.0 - Hot end not heating up?
thats odd cause i dont have a M109 in my Filament GCODE
That explains your problem then. You are doing a lot of actions in your gcode that requires that the filament be heated up. You certainly need it up to print temp before doing your prime lines. PS, like most other slicers, will insert heatup commands if none are present, but it seems those are being inserted after your custom gcode instead of before. Just add the appropriate lines before you start extruding anything.
might suspect that its the G4 S10; wait for heaters to recover thats causing it then.
Some notes on your gcode:
- G4 just inserts a pause with the Prusa firmware. That line will simply wait 10 seconds.
- There is a better way to avoid filament blobs during probing with a 2-step nozzle warmup procedure.
- M117 won't do anything with the Prusa firmware (unfortunately).
- M84 turns off steppers and isn't required for Prusa mesh bed leveling. It's usually part of end gcode for Prusas.
You didn't mention the printer you're using or the origin of that gcode, and it's not typically what's used for a Prusa printer, so our ability to help is going to be limited. At this point, I'm going to assume you're using a different printer and gcode from "somewhere else". I certainly wouldn't use that sequence on a Mk3.
Try copying your startup gcode from the prior version of Slic3rPE/PrusaSlicer that you used and start there. If all else fails, slice in PS and one that works and compare the startup sequence.