Hot End fan not being controlled by temp
-
I've had a recent issue where the hot end fan is no longer being controlled by the hot end temp.
Note: This is a somewhat new board about 1 month ago. Everything has been working until just a couple days ago. I didn't figure out the fan wasn't working until today, but I have not tried to print since 2 days ago when the last print failed. I initially thought I had filament with too much moisture, but since changed out to filament that has been drying for 3-4 days.
Board: Duet 3 Mini 5+ Wi-Fi
I have (3) fans on my system.
H0 = Part Cooling on out3
H1 = Hot End on out5
H2 = Board cooling fan on out6I have not knowingly made any changes to config.g or anything else.
I found the error during a print. Filament was not extruding properly or at all.
All fans have been tested and operate.
If I swap fans H1 and H2, I can turn on the fan at the hot end, but the board fan does not come on.
If I swap them to normal position, hot end fan does not turn on, but board fan can be controlled.I have tested all 3 board connections with a multimeter.
Is there a way to force out5 on to test regardless of temp reading at hot end?Config.g file attached.
Please let me know if you need any other info.
Thanks in advance for any help/advice.
David -
I solved this issue.
I'm not sure why, but running the RRF tool and uploading the files did the trick. -
@davidewen I think the problem was here:
; Hot End Fan ;M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency M950 H1 F1 C"out5" Q65535 ; create fan 1 on pin out5 and set its frequency M106 P1 C"Hot End" S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
Your M959 line has both H and F parameters. This will cause it to throw an error and not be executed. Unfortunately, errors raised while executing config.g are not reported. It's a good idea to run M98 P"config.g" after making changes to config.g, then they will usually be reported.
-
-
-
@dc42 said in Hot End fan not being controlled by temp:
Your M950 line has both H and F parameters. This will cause it to throw an error and not be executed. Unfortunately, errors raised while executing config.g are not reported. It's a good idea to run M98 P"config.g" after making changes to config.g, then they will usually be reported.
Thank you for that info. I will run the suggested M98 P"config.g" after making changes from now on.
-
Per your suggestion, I ran M98 P"config.g".
I have (2) errors. How do I find out what they are and where in the code they are located?
Here's the result of M98 P
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: bad model parameters
Error: Sensor number out of rangeHere's my config.g file
config-2.gThank you.
-
@davidewen I would guess it's the M106 line got the fan 2. h100:101:102 isn't valid for RRF3
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Temperature_configuring_mcu_temp
-
Thank you.
That was line 98 of the code. I removed it and re-ran M98 P"config.g", and the error "Sensor number out of range" is gone.The only error left is "bad model parameters"
-
@davidewen that would almost certainly be from line 74, the M307 command with the very small R parameter.
-
@dc42 said in Hot End fan not being controlled by temp:
@davidewen that would almost certainly be from line 74, the M307 command with the very small R parameter.
Thank you for the feedback.
I'm working to get my chamber heater functional again.
I have another forum post going for that here.https://forum.duet3d.com/topic/30954/unable-to-tune-chamber-heater
I have modified line 74 (now line 72) and I'm still getting the "bad model parameters" response.
Here's the new code for line 72. Let me know if you want the entire config.g file uploaded again.
Since the chamber heats up and cools down so slowly, should I just ignore this error?
M307 H2 R0.01 K0.200:0.000 D60 E1.35 S1.00 B1