Spurious heater faults

[Phaedrux]

Can you try removing M307 H0 R0.246 K0.112:0.000 D30.62 E1.35 S1.00 B0 ; Bed, with enclosure tuned at 100c from your config.g and re-running the tuning process with M303 H0 S100 and this time take a screen shot of the tuning process after a while so we can see the graph?

Be sure to start the tuning process from ambient temp.

[ibash]

Thanks!

Still running the tuner, can post results when done. Just realized that my config.g has "B4240" for the bed thermistor, when I think it should be B3950. Could that be the cause?

[ibash]

I think the problem is that it is using the wrong thermistor value, as per the graph the keenovo thermistor vs bed thermistor are way different when they should be the same. This is my mistake.

Thank you Phaedrux!

[ibash]

Hmm, got another heater fault today despite having changed the thermistor value and retuning.

[Phaedrux]

Are you copy and pasting the results into your config?
Have you tried using M500 to save them to config-override.g and then adding M501 to the end of your config to load the values at startup?

It seems like the values aren't actually applied. Can you send M307 H0 in the gcode console and see what values it is actually using.

Is it perhaps your part cooling fan coming on and causing the temp to drop? Or is the enclosure temp different during a print versus when it's tuned?

[ibash]

@phaedrux

Yep I do copy/paste the line into config.g. It looks like the values are applied correctly too:

In my config.g:

M307 H0:

[Phaedrux]

What does the temp graph look like when the error occurs? It seems weird that it expects a rate of 0.28 but actually saw a rate of 0. Is the thermistor not making good contact?

[A Former User]

This post is deleted!

[Phaedrux]

@arnold_r_clark said in Spurious heater faults:

never reach the same conclusion twice

How much variation are you seeing?

[A Former User]

This post is deleted!

[ibash]

This post is deleted!