MINTEMP Frustrations
I'm really at my wit's end - I'm really hopeful that someone on here has a solution. Thank you in advance! I've had my MK3S for about 2 months, and it's printed perfectly. My setup is totally stock (3.8.1) + Octoprint.
About a week ago, I switched to PETG (from PLA) and I got my first error - the printer just stopped. On the printer, the screen showed a bunch of weird glyphs. In Octoprint, I got an error "Temperature heated bed switched off. MINTEMP triggered" This began to happen about once or twice a day - with different gcode and at different bed placements.
I contacted support and they had me do a jiggle test: try and mess with the thermistor cable to see if I could get it to short out or trigger, but I just can't get it to happen. I've taken the bed off and inspected the thermistor cable and everything looks perfect. No matter what I try, I still get the same error (every now and then).
The weird thing is I'm not seeing any temp fluctuations inside Octoprint... I don't see the temp drop out and actually trigger the error.
Things I've tried:
- Jiggle test bed/hotend
- Upgrade firmware to 3.9.0
- Checked connections inside the case
- Confirmed the printer is far enough from a wall / nothing is in contact
RE: MINTEMP Frustrations
I'm really at my wit's end - I'm really hopeful that someone on here has a solution. Thank you in advance! I've had my MK3S for about 2 months, and it's printed perfectly. My setup is totally stock (3.8.1) + Octoprint.
About a week ago, I switched to PETG (from PLA) and I got my first error - the printer just stopped. On the printer, the screen showed a bunch of weird glyphs. In Octoprint, I got an error "Temperature heated bed switched off. MINTEMP triggered" This began to happen about once or twice a day - with different gcode and at different bed placements.
I contacted support and they had me do a jiggle test: try and mess with the thermistor cable to see if I could get it to short out or trigger, but I just can't get it to happen. I've taken the bed off and inspected the thermistor cable and everything looks perfect. No matter what I try, I still get the same error (every now and then).
The weird thing is I'm not seeing any temp fluctuations inside Octoprint... I don't see the temp drop out and actually trigger the error.
Things I've tried:
- Jiggle test bed/hotend
- Upgrade firmware to 3.9.0
- Checked connections inside the case
- Confirmed the printer is far enough from a wall / nothing is in contact
Hello and welcome here in the Prusaforum!
That's annoying, of course!
Have you ever measured the resistance of thermistors? These should have an internal resistance of about 100kohms at 25 degrees C.
The ambient temperature during printing should also not be below 18 degrees C.
I would also try to omit octoprint and print from the SD card.
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.
RE: MINTEMP Frustrations
Hey - appreciate the suggestions! I should have added that I've now removed Octoprint and am printing just from the SD card. I'm still getting the same problem (though the screen on the printer now gives a more descriptive error, "MINTEMP fixed" instead of just being a bunch of glyphs like it was using Octoprint).
When I talked to the support team over the weekend, they mentioned the same thing: ambient temp. I'm in my basement office which is around 68-72F. I've brought in my dehumidifier which now has the temp around 74-78F and I'm still getting the same results.
I don't have a multimeter (or know how to use one) but I suppose I could probably figure that out if that's the next step.
RE: MINTEMP Frustrations
@hospadam
Tools that you could occasionally use quite well if you own a Prusa (some of them...) 👍 : https://forum.prusa3d.com/forum/english-forum-general-discussion-announcements-and-releases/tools-what-do-you-recommend/
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.