Maestro bed sensor broken after update?
-
I've just updated from 3.0.0beta-12 (I think?) to 3.3, going via 3.0, and my bed thermistor is now reading 2000...
I've verified that the thermistor is working (~94.6kOhms) and that it's still plugged in and didn't somehow get pulled out during the firmware update, rebuilt and verified my config.g with the config tool.
I've tried to downgrade back to 3.0 to verify it still works in that, but uploading the firmware just results in an error (Error: M997: In-application programming binary "0:/firmware/Duet2_SDiap32_Maestro.bin" not found)
Have I missed something stupid? Or could this be a bug in 3.3, in which case how can I downgrade to get a usable machine?
-
@astusvis post your config and your board type, along with the type of thermistor and where it's plugged in
-
Sorry, didn't mention in the post but Duet Maestro 1.0, bog standard NTC thermistor plugged into the bed thermistor socket.
Looks like it has been connected to/is pretending to be a PWM output of some sort? (Red being extruder temp heater 1, blue being bed temp heater 0)
; Configuration file for Duet Maestro (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu Jul 08 2021 17:30:11 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Printer" ; set printer name ; Network M552 P192.168.1.245 S1 ; enable network and set IP address M553 P255.255.255.0 ; set netmask M554 P192.168.1.254 ; set gateway M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S0 ; physical drive 3 goes backwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.80 Y80.40 Z403.00 E409.00 ; set steps per mm M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E900 I50 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-30 Y-20 Z0 S1 ; set axis minima M208 X205 Y215 Z260 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X0:200 Y0:195 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T98801 B4185 C2200 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S80 ; set temperature limit for heater 0 to 80C M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S250 ; set temperature limit for heater 1 to 250C ; Fans M950 F0 C"fan0" Q20 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H1 T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"fan1" Q20 ; create fan 1 on pin fan1 and set its frequency M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off M950 F2 C"fan2" ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H T30 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0:1 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
-
@astusvis config looks fine.
I suggest its a wiring from the graph -
@jay_s_uk I would love to agree, but this setup was happily printing only an hour ago on a previous firmware, and if I place the hot-end thermistor in the bed thermistor socket I get the same issue. (And equally the bed thermistor in the hot-end socket works)
-
@astusvis it could also be a board issue but it's not a firmware issue.
Why not map the bed thermistor to e1temp for the time being? That way you can rule out the thermistor (if the issue doesn't follow) and move on to inspecting the board. -
@jay_s_uk the issue is definitely firmware, or at least config, because it seems to be following sensor 0
With the following config, I still get the issue as previously described, albeit now always at -273 rather than +2000, recorded for the bed. Bed thermistor still plugged into bedtemp, hotend thermistor still plugged into e0temp. Also reproducible using e1temp.
M308 S0 P"e0temp" Y"thermistor" T98801 B4185 C2200 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S80 ; set temperature limit for heater 0 to 80C M308 S1 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S250 ; set temperature limit for heater 1 to 250C
-
@jay_s_uk Config was bad...
Default value for C on https://configtool.reprapfirmware.org/Heaters read the value I had for R and I didn't question the several orders of magnitude difference
C is now set to a more reasonable value of 0.
-
@astusvis aha. Yes, missed that one. Good spot