<p>The bed minimum temperature is defined in your configuration file, e.g.:</p>
<pre><code>#define BED_MINTEMP        5
</code></pre>
<p>If the error is displayed, it means that the measured temperature drops below this level.</p>
<blockquote>
<p>What I am noticing is that upon finishing the first print</p>
</blockquote>
<p>This could hint to a faulty heatbed connector where the connection is lost because the bed moves to the end positions (hard to say without seeing the end G-code).</p>
<p>Basically, you could have a connection to bed thermistor that is intermittently failing, or a bad bed thermistor. If connection is lost the temperature defaults to 0 °C or a lower setting.</p>

CC BY-SA 4.0
2020-09-18T17:33:13.943Z
yes, the issue turned out to be hardware and not gcode. there was a defect with the bed thermistor cable which only faults at the far back corner. my consecutive prints occur at these corners which is why I incorrectly suspected enabling consecutive printing as the cause.
wonton
CC BY-SA 4.0
2020-09-16T11:08:42.950Z
2020-09-16T11:08:42.950Z
0scar
<p>This is most likely a hardware problem, namely the <a href="https://help.prusa3d.com/en/guide/4-heatbed-assembly_51736#52400" rel="nofollow noreferrer">heat bed thermistor cable</a>.</p>
<p>To confirm this as the root cause, here's what you can try</p>
<ul>
<li>Reboot the printer</li>
<li>Move the y axis around to make sure there is freedom of movement at both ends</li>
<li>Jigger the thermistor cable around in multiple directions at multiple points on the cable</li>
</ul>
<p>If you hit <code>BED MINTEMP</code> or <code>BED_MINTEMP fixed</code> then you have found a cable angle/position that causes the issue. You may need to replace the cable.</p>
<p>The issue could also happen at the connection with Einsey. If the wrapped cable going into Einsey is moved, the connection may be faulty.</p>
<ul>
<li>Ground yourself</li>
<li>Open Einsy</li>
<li>Ground yourself</li>
<li>Reboot the printer</li>
<li>Jigger the connection to Einsey</li>
</ul>
<p>If you hit <code>BED MINTEMP</code> or <code>BED_MINTEMP fixed</code> then the connection is bad. Try unplugging and replugging the cable. Look at the connectors on both sides to try to determine if the source is the cable or Einsey. You may need to replace the cable or repair the Einsey connector.</p>

CC BY-SA 4.0
2020-09-18T18:01:02.897Z
2020-09-18T18:01:02.897Z
wonton
<p>I am using &quot;Pretty PETG&quot; along with PrusaSlicer's consecutive print mode.</p>
<p>What I am noticing is that upon finishing the first print, the printer hits <code>MINTEMP BED Fixed</code>. 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.</p>
<p>I'm just starting to learn G-code and my initial thought was there's an errant bed temperature instruction but the only <code>M140 S0</code> instructions I see are in the <code>end_gcode</code> and near the bottom of the file. Maybe there a <code>goto</code> in G-code which may be running after <code>M140 S0</code> which then causes the <code>MINTEMP BED</code> issue? Perhaps there's something else going on?</p>

CC BY-SA 4.0
2020-09-16T11:01:07.640Z
Maybe you could add the "end G-code"? Note that `goto` is not a G-code command.
0scar
<prusa-i3><g-code><petg><prusaslicer><prusa-research>
MINTEMP BED Fixed error when running consecutive print
wonton
# MINTEMP BED Fixed error when running consecutive print

(Asked by: username_0 on 2020-09-15)

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?

**Tags:** prusa-i3, g-code, petg, prusaslicer, prusa-research

> **Comments:**
> **username_1**: Maybe you could add the "end G-code"? Note that `goto` is not a G-code command.  

---

## 2 answers

### Answer by username_1 on 2020-09-16. Score: 1 | Accepted answer

The bed minimum temperature is defined in your configuration file, e.g.:

```
#define BED_MINTEMP        5

```

If the error is displayed, it means that the measured temperature drops below this level.

> What I am noticing is that upon finishing the first print

This could hint to a faulty heatbed connector where the connection is lost because the bed moves to the end positions (hard to say without seeing the end G-code).

Basically, you could have a connection to bed thermistor that is intermittently failing, or a bad bed thermistor. If connection is lost the temperature defaults to 0 °C or a lower setting.

> **Comments:**
> **username_0**: yes, the issue turned out to be hardware and not gcode. there was a defect with the bed thermistor cable which only faults at the far back corner. my consecutive prints occur at these corners which is why I incorrectly suspected enabling consecutive printing as the cause.  

---

### Answer by username_0 on 2020-09-18. Score: 1

This is most likely a hardware problem, namely the [heat bed thermistor cable](https://help.prusa3d.com/en/guide/4-heatbed-assembly_51736#52400).

To confirm this as the root cause, here's what you can try

* Reboot the printer
* Move the y axis around to make sure there is freedom of movement at both ends
* Jigger the thermistor cable around in multiple directions at multiple points on the cable

If you hit `BED MINTEMP` or `BED_MINTEMP fixed` then you have found a cable angle/position that causes the issue. You may need to replace the cable.

The issue could also happen at the connection with Einsey. If the wrapped cable going into Einsey is moved, the connection may be faulty.

* Ground yourself
* Open Einsy
* Ground yourself
* Reboot the printer
* Jigger the connection to Einsey

If you hit `BED MINTEMP` or `BED_MINTEMP fixed` then the connection is bad. Try unplugging and replugging the cable. Look at the connectors on both sides to try to determine if the source is the cable or Einsey. You may need to replace the cable or repair the Einsey connector.


---

