Heater Fault Troubleshooting

[jgbowman]

@dc42 It says movement before homing is not permitted. All of the firmware is updated to 1.21 except for the paneldue, could that be the problem?

[jgbowman]

@mrehorstdmd Not sure where my boss got the sensors, but I've tried to switch out a couple of them, so i'm pretty sure it's either a wiring or configuration issue. I ordered a new daughterboard because that seems like the most likely fix. For now i have got it working with regular thermistors though.

[mrehorstdmd]

@jgbowman

Do they have Teflon insulation on the wires?

[jgbowman]

@mrehorstdmd i believe so

[mrehorstdmd]

@jgbowman

Teflon breaks down at ABS print temperatures. If the Teflon breaks down inside the casing, it will short to the case and that will cause erratic behavior. Check the resistance between the wires and the metal casing of the sensor- any noninfinite reading is bad.

I had the same problem a week ago. Swapping in a new PT100 of the same type will fix it temporarily, until the Teflon breaks down.

PT100 sensors that are going to be used in the hot-end should have fiberglass insulation on the leads. E3D's PT100 sensor does.

[jgbowman]

@mrehorstdmd Thank you, although switching out the pt100s doesn't even temporarily fix the problem for me, so I'm sure i'm having another issue. Will definitely look into the E3D sensors though.

[dc42]

@jgbowman said in Heater Fault Troubleshooting:

@dc42 It says movement before homing is not permitted.

Then the M564 H0 command in config.g isn't working. Try retyping it.

[jgbowman]

@dc42 I tried moving it around a bit, but to no effect. Even though I put 1.20 and later in the configuration settings, config.g still says 1.17-1.19. Could this have something to do with my issues?

[T3P3Tony]

@jgbowman the header at the top of config.g is just a comment written by the configurator.

If you go into the gcode console screen and type M564 H0, send that and then type M564. What does it report?

[jgbowman]

@t3p3tony That got it working, thank you

[T3P3Tony]

@jgbowman ok thats interesting. So it works is entered directly, but not in config.g? Maybe try a reboot with it in config.g and see if it continues to work after the reboot.