Skip to main content
3D Printing

Return to Question

Typo's
Source Link
0scar ♦
0scar ♦
  • 37.1k
  • 12
  • 67
  • 155

I am using Pretty PETG"Pretty PETG" along with PrusaSlicer's consecutive print mode.

What I am noticing is that upon finishing the first print, the printer hits MINTEMP BED Fixed. I'm not sure if it's immediate because I let the prints run overnight but I assume the bed cools down and then the error is hit.

I'm just starting to learn gcodeG-code and my initial thought was there's an errant bed temperature instruction but the only M140 S0 instructions I see are in the end_gcode and near the bottom of the file. Maybe there a goto in gcodeG-code which may be running after M140 S0 which then causes the MINTEMP BED issue? Perhaps there's something else going on?

I am using Pretty PETG along with PrusaSlicer's consecutive print mode.

What I am noticing is that upon finishing the first print, the printer hits MINTEMP BED Fixed. I'm not sure if it's immediate because I let the prints run overnight but I assume the bed cools down and then the error is hit.

I'm just starting to learn gcode and my initial thought was there's an errant bed temperature instruction but the only M140 S0 instructions I see are in the end_gcode and near the bottom of the file. Maybe there a goto in gcode which may be running after M140 S0 which then causes the MINTEMP BED issue? Perhaps there's something else going on?

I am using "Pretty PETG" along with PrusaSlicer's consecutive print mode.

What I am noticing is that upon finishing the first print, the printer hits MINTEMP BED Fixed. I'm not sure if it's immediate because I let the prints run overnight but I assume the bed cools down and then the error is hit.

I'm just starting to learn G-code and my initial thought was there's an errant bed temperature instruction but the only M140 S0 instructions I see are in the end_gcode and near the bottom of the file. Maybe there a goto in G-code which may be running after M140 S0 which then causes the MINTEMP BED issue? Perhaps there's something else going on?

Source Link
wonton
wonton
  • 123
  • 1
  • 6

MINTEMP BED Fixed error when running consecutive print

I am using Pretty PETG along with PrusaSlicer's consecutive print mode.

What I am noticing is that upon finishing the first print, the printer hits MINTEMP BED Fixed. I'm not sure if it's immediate because I let the prints run overnight but I assume the bed cools down and then the error is hit.

I'm just starting to learn gcode and my initial thought was there's an errant bed temperature instruction but the only M140 S0 instructions I see are in the end_gcode and near the bottom of the file. Maybe there a goto in gcode which may be running after M140 S0 which then causes the MINTEMP BED issue? Perhaps there's something else going on?