Hello,
I am having trouble using FAN2 as my part cooling fan. I had FAN0 as my part cooling fan, but i switched to magball arms and accidentally had both poles too close to the fan and it apparently burned out my FAN0 PWM channel because it no longer works. I swapped the arms so North and South are next to each other and now the fan works if I use FAN2, but only when i set it up as its own fan using M106. I want to set it up as my part cooling fan using M563 and mapping to the FAN2 output, but my DUET wifi does not seem to recognize this mapping. If I do this the fan never turns on. If I map it just using M106 it works just fine, but then i need to manually control when it is on/off rather than using my part cooling slicer settings. i have copy and pasted this section of my config.g file below. Can anyone please help me understand what I am doing wrong?

Thank you in advance!

; Fans
;M106 P2 S1 I0 F500 H-1 ; FAN0 channel fried use FAN2 instead. set fan value, PWM signal inversion and frequency. Thermostatic control is turned off
;M106 P1 S1 I0 F500 H1 T45 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 S"Hot End" D0 H1 F2 ; define tool 0. FAN0 channel fried use FAN2 instead.
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

@droftarts Oh also, I tried adding the command to my config.g in the probe section, but it didn't do anything either. How ever all other commands worked fine. I.e. home, delta auto-calibration, mesh bed leveling, etc. Of course i had to run those commands with the fan off so I wouldn't have interference.

@droftarts Thanks for letting me know Ian! I got mine around September, so I might need to download that update. As far as the issue being intermittent, I don't think it's wiring because I can send other commands just fine. The M672 is the only command I've tried that didn't get accepted. I'm wondering if there is an order of operations that I am missing here, like home first than blah then run command?

Hi all,

I've browsed this forum for a while an can almost always find a solution from a previous post. However, I have not been able to find a good answer for this one, so I'm hoping this post and the eventual answer will not only help myself but other users in the future. Thanks in advance for you time and all the great work!

I have a Kossel Delta Printer running a Duet WiFi and using a smart effector with carbon rods. The thing runs great! However, my part cooling fan causes interference so the Z-probe always triggers.

I found on the duet site that sending command M672 S105:aaa:bbb (with the appropriate values in place for those variables) will fix this issues. I've had success by setting aaa to 100 and bbb to 155. The issue is I am only able to send this command intermittently, and the printer will not save this sensitivity setting so i need to run it every time. Some days the command is accepted and everything is fine, other days I need to turn the fan off for any calibration or z-probed activities.

I would really appreciate any help in understanding why the printer won't accept this command most of the time and how to fix that, and also how to make the printer store this sensitivity setting so I don't need to do this every time I turn it on.

Thanks again in advance!

Andy