Disable heater fault
-
@rowow as mentioned disabling them is not a good idea. If you tune the heater then it should operate without producing faults.
what heater are you trying to disable faults for? -
@t3p3tony I tuned the heater however there are two fundamental flaws with the duet software
1: Any sort of environmental change such as difference in temperature or a fan turned on will cause the firmware to fault due to "heating too slowly". Why is this setting set so tight is beyond my understanding.
I have been able to fix this problem by changing the heating parameter2: I upgraded to a volcano hotend and the temperature delay is somewhat significant and even though it shuts off the heater the temperature still rises and a "temperature exceeds 15c" error comes up. idk what the issue with this is and am simply frustrated with the countless problems I am getting with this board.
If you have any suggestions I would be glad to hear, otherwise im about to throw away this junk controller.
Ive already burnt my fingers significantly trying to change some things to figure out the problem and am very frustrated with this entire platform. I am about to return back to a ramps board as the duet software is the biggest missed opportunity and loaded with so much crap. seems like nothing can be made with quality anymore and every single little thing needs to be DIY'ed.
-
@rowow first question, which firmware are you using( Type in the console M115 )? Which duet Board ? Did you do a PID Tuning for the heaters ( https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control )?
Can you Post your config.g file here
-
@siam Yes I did the PID tuning. Ill be honest I might have missed something so just to be sure I did it right here is what I did:
1: type "M303 H1 S240" in console
2: type "M303" in console
3: Copy results
4: Post results at the end in #configI am using a duet wifi
firmware 3.2 -
@rowow From firmware 3.2 and later, the right command is
M308 T0 S240 ; Tuning tool T0
for the heated bed
M308 H1 S80 ; Tuning Heatbed (change H1 to fit to your Printer)
After a PID Tuning, you can save these settings with M500, so you don't have to alter your config.g file, but you must have a M501 at the end of your config.g file to load the stored settings.
And Please post your config.g file, maybe there are other issues
-
@rowow A couple of things which might help.
-
If you tune the tool rather than the heater, it will do an extra tuning step with the fan on. This will generate the parameters for the control algorithm to adjust the PID to compensate for deflected part cooling air when the fan comes on. It's best to do that with the hot end close to the bed. Use M303 Tn instead of Hn. If you only have one tool and you want to set the temperature to 240deg C, then use M303 T0 S240
-
The heater fault detection parameters aren't hard coded (almost nothing is in RepRap firmware). To adjust them, use M570. e.g. if you hot end heater is H1 then use something like M570 P30 T20 S180. This would mean that the temperature excursion has to be more than 20 deg C and last for more then 30 seconds before a fault is flagged, and if it persisted for 180 seconds (3 minutes) than the print would cancel. Be aware that the wider the tolerances, the less "safe" it would be but there is nothing stopping you from setting it to (say) 100 deg C for (say) 1800 secs (30 minutes) or more.
-
-
@siam M308 gives a error of "sensor number out of range"
my H0 is the bed, and H1 is the extruder.; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 03 2020 10:18:18 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E220.00 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X1500 Y1500 Z1500 E1500 ; set motor currents (mA) M84 S0 ; Disable motor idle current reduction ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X300 Y300 Z220 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 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M558 P5 C"^!zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds G31 P500 X45 Y-12 Z3 M557 X30:260 Y15:300 S20 ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; 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 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; 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 ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; 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 M307 H0 A100 ; Heater Bed Temp Setting to avoid heating too slow error M307 H1 A100 C302 D5.8 B1 ; Heater Extruder Temp Setting M143 H1 S420 ; extruder max temp
-
@deckingman I appreciate that was more of what I was looking for. I am aware of the risks and am not worried about that. Ill try tweaking around with the parameters more in the upcoming days
-
@rowow Disable the bang-bang mode for your heat bed because the heating is more accurate as with bang bang
M307 H0 B0 S1.00
How you get these settings?
; Custom settings are not defined M307 H0 A100 ; Heater Bed Temp Setting to avoid heating too slow error M307 H1 A100 C302 D5.8 B1 ; Heater Extruder Temp Setting
For example, It should normally look like this
M307 H0 R0.466 C285.252:285.252 D0.89 S1.00 V24.3 B0 I0 M307 H1 R4.010 C189.689:86.279 D3.56 S1.00 V24.2 B0 I0
M308 gives a error of "sensor number out of range"
can you post the complete command
and also the result of M98 P"config.g"
-
@rowow said in Disable heater fault:
@deckingman I appreciate that was more of what I was looking for. I am aware of the risks and am not worried about that. Ill try tweaking around with the parameters more in the upcoming days
As a long term user of Duet products, I distinctly remember the events which led up to the introduction of heater fault protection. IIRC it was a user who posted on the RepRap forum that his heater cartridge had fallen out of the hot end onto the printed part. This meant that the hot end itself started to cool which was detected by the sensor so the heater got hotter and hotter. Fortunately, the user was close to his machine so no major damage ensued but it could easily have resulted in a fire.
I these days of litigation, that could have been bad for Duet as a company. So I have some sympathy with their position that heater fault detection should not be disabled. As a retired engineer, I prefer mechanical solutions so I design my hot ends so that a heater cannot fall out, and never use over powered heaters which could reach dangerously high temperatures if a MOSFET failed. So I'm comfortable with using wide fault detection parameters but for the reasons given, the Duet team could never condone it.