Heater fault in 3.01
That is what I get for my E3D after I updated to fw 3.01. I tried for hours to solve this. But with no success...
I managed to get the heated bed running. But not the hotend.
This is the heaters config out of the config tool:
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 Q5 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S85 ; set temperature limit for heater 0 to 85C
M307 H0 A486.1 C2320.7 D16.5 S1.00 V24.0 B0 ; PID-parameters for heated bed
M140 H0 ; map heated bed to heater 0
M308 S1 P"spi.cs2" Y"rtd-max31865" ; configure sensor 1 as thermocouple via CS pin spi.cs2
M950 H1 C"e0_heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S265 ; set temperature limit for heater 1 to 265C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
Any suggestions? Somebody?
What response do you get if you send the whole M308 H1 command from the console?
I suspect that you may need to use the cs0 or cs1 pin in that command instead of cs2.
M308 H1 S1
Sensor 1 type PT100 (MAX31865) using pin spi.cs2, reading 2000.0, last error: sensor short to other wiring, 2/4 wires, reject 50Hz, reference resistor 400 ohms
Not sure, but it looks like the spi.cs2 is correct?
last error: sensor short to other wiring
Please try disconnecting the PT100 cable where it connects to the daughter board, and connect the 100 ohm reference resistor in its place. That should give a reading close to 0C.
EDIT: you have configured a PT100, but the comment says it is a thermocouple. Which is it?
It is actually a PT100 (orig new E3D Titan Aero). Connested directly to the e0thermistor input on the Duet 2 Maestro. The the thermocouple came from the config tool. If I select E3D there, then it sets the thermocouple. But doesn't matter. Even if I put in all parameters manually - it fails in the same way.
I connect the hotend thermistor to the bed thermistor input - the hotend temp was shown.
DocTrucker last edited by
@Fritz-We didn't think PT100 aren't supported direct ro the board, only via daughter board.