Fan confusiom

jens55

@phaedrux, I am using the third PWM port on the Duet2 wifi board which would be fan2. Fan1 has a dead mosfet and fan0 is used as the hotend cooling fan.
Thanks!
Now fan2 might also be blown but I do not know this for a fact. The last bit of experimenting has none of the PWM fans working
Both fans were tested against the always on fan outputs and are working.

jens55

So I have a sort-of working version:

M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0
M950 F2 C"nil" ; free up fan2 connector
M950 F1 C"fan2" Q500 ; create fan 1 on pin fan2
M106 P0 S1 H1 T45 ; set fan 1 value and Thermostatic control .
M950 F8 C"duex.fan8" ; declare fan 8 on the duex card - this is the fan output used for the automatic bed lights
M106 P8 S1 H1 T45 ; lights are turned on automatically when nozzle 1 is over 45C

; Tools

M563 S"Nozzle 0" P0 D0 H1 F1 ; define tool 0

What I have is the hot end fan and the lights acting like expected. The part cooling fan is not working but that is possibly a blown mosfet. Last but not least, the web interface lists 3 fans when I expect to see only one. It lists the 'tool fan', 'fan 1' and 'fan 2'.
Since the hot end fan is thermostatically controlled, I do not expect it to show up on the web interface. Since fan 2 was declared as 'nil' and fan 1 was assigned to the fan 2 port, I expect to see only 'fan 0'.
Why am I seeing 3 fan listings ?

jay_s_uk

@jens55 i dont think M950 F2 C"nil" is required and thats probably adding to one fan.
The tool fan is the part cooling fan of the current tool. This can be hidden

jens55

@jay_s_uk, the M950 F2 C"nil" is specifically needed to reassign fan connector two to be used as fan connector one.
As per gcode reference:
C"name" Pin name(s) and optional inversion status, see Pin Names. Pin name "nil" frees up the pin. A leading '!' character inverts the input or output. A leading '^' character enables the pullup resistor. The '^' and '!' characters may be placed in either order.

The pin needs to be freed up in order to assign it to fan1

I suppose one could specifically assign fan2 to heater 1 but for some reason or another that wasn't done on original setup and I didn't feel it necessary to redo more than what was absolutely necessary (and even then I got into trouble)

jay_s_uk

@jens55 nothing is preassigned in newer firmware

Phaedrux

Nil is only required now when you want to alter an existing definition. In RRF 3.1 and later there are no pre-defined assignments anymore. So you don't need to use Nil unless you've already defined a pin and want to re-assign it to something else.

Here's my fan setup as an example.

; Fans
M950 F0 C"fan0" Q100                               ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 B0.5                                ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q1000                              ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 B0.5                             ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q15000                             ; create fan 2 on pin fan2 and set its frequency
M106 P2 S0.33 H1:0 T45 B0.5 
; Tools
M563 P0 S"Titan Aero" D0 H1 F0

Let's modify it to use the fan headers you are using and add fan2 as a part cooling fan for tool0.

M950 F0 C"fan0" Q500                               ; create fan 0 on pin fan0 and set its frequency
M106 P0 S1.0 H1 T45                                  ; set fan 1 value. Thermostatic control is turned on. This fan turns on if heater1 is over 45 degrees
M950 F8 C"duex.fan8"                               ; declare fan 8 on the duex card - this is the fan output used for the automatic bed lights
M106 P8 S1 H1 T45                                  ; lights are turned on automatically when nozzle 1 is over 45C
M950 F1 C"fan2" Q100                               ; create fan 1 on pin fan2 and set its frequency
M106 P1 S0 H-1 B0.5                                ; set fan 1 value. Thermostatic control is turned off
M563 S"Nozzle 0" P0 D0 H1 F1                       ; define tool 0

It creates fan1 on the fan2 port and assigns it to tool0.

jens55

@phaedrux, thanks for the configuration example and thanks for confirming jay_s_uk's comment about the "nil" line not being necessary any more.

I replaced the Duet2Wifi board this morning and it did indeed have two of the PWM fan output ports blown up.

I am currently struggling with getting the new board on line and I will test things after that. It looks like the config file I came up with last night is the same as your suggestion so that looks promising.

More when I have things going again.

jens55

Things are looking good except for the 'Fan control' section of the DWC.
I show two fans - 'Tool Fan' and 'Fan 1'. Both selections control the single fan that cools the printed model.
I have removed the fan8 (lights) stuff in case it generated that second fan entry.

Any suggestions on what might cause this second phantom entry?

Phaedrux

It's not a phantom entry, it's the same fan.

The "tool fan" slider will control the fan of the currently selected tool. So if you had two tools with different fans it would control the fan of the selected tool.

If you only have a single tool, there's only one fan to control and it is a duplicate. You can use the "change visibility" button there to hide it if you wish.

jens55

Oh, go figure ..... I never noticed that before .... learn something new every day
Where would I find the visibility selector?

Thanks again for all help from both jay_s_uk and Phaedrux!

Phaedrux

The change visibility slider is only present on one of the pages that shows the fan sliders. The one that's on the right side. Sorry I can't recall which page that is though at the moment. Status or dashboard. It's been requested to add it to both places.

jens55

@phaedrux

Woohoo ... it was on the Status page and I never use that page.

Thanks!