Fan0 wont turn off.

JKaechler

yeah i keep checking that over and over. i swapped Fan1 and Fan0, and the behavior stays with the one plugged into the Fan0 pins. Fan1 is the one that comes on at 45 degrees.

Phaedrux

If you add back a normal Fan0 config can you control it using the slider in the DWC?

JKaechler

the slider says Fan1 on it? I didnt know i was supposed to control Fan0 with that slider. How do I add it?

Phaedrux

Well Fan0 is typically used as the part cooling fan and is Gcode controlled with M106 commands by the slicer. The DWC slider can control it as well, and you can pin it to a set speed to override whatever the slicer has set.

Your config.g should have something like this:
M106 P0 S0 H-1 C"Part Cooling" ; Set fan 0 (Part cooling blower) G-code controlled. Thermostatic control is turned off

https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans

If it's still running all the time and the DWC slider can't control it, then I'm not sure what could be wrong.

JKaechler

Oh, interesting side fact.
Fan0 is still running, but only at a fraction of its speed. This whole time i didnt realize that it was turning well below top speed. when i hook it to Fan1 it revs up all the way (assuming the temp is up).
I tried something else based on a tip that DC42 gave somebody else, that is to remove all the M106 commands from the config.g

still running!
and Fan1 still kicks on at 45 degrees like it should.

This is weird

Phaedrux

If you send M106 P0 to the console, what does it send back?

JKaechler

my output from the M106 P0 command:
Fan 0 pin: F0; frequency 250hz; speed: 0%; min: 10%; max: 100%; blip: 0.10; inverted: no

Phaedrux

Well if the min speed is set to 10% that would explain why it won't turn off.

Are you using the M106 command I posted above? Do you have another M106 P0 command in config.g or elsewhere that would be overriding it?

JKaechler

So I am trolling thru these files looking for a stray M106 command. What is the priority of the code being executed? what files get run first, or which ones supercede others?

Phaedrux

gcodes are purely sequencial, so whatever was executed last gets applied and stays applied until a new command is sent to replace it.

Config.g gets run at startup. If you have M501 at the end of config.g it will then load config-override.g. Which acts kind of like EEPROM on 8-bit boards.

Then any macro that gets called. Like the homing files, or bed.g, start.g, stop.g, pause.g, cancel.g, etc.

Can you post the M106 P0 command you have in config.g and the result of sending M106 P0 in the console right after a startup. They should correspond.

JKaechler

I dont have an M106 command in my config.g They are all removed at this point.

the output from the M106 P0 command is:
1:17:55 PMM106 P0
Fan 0 pin: F0, frequency: 250Hz, speed: 0%, min: 10%, max: 100%, blip: 0.10, inverted: no

I have been looking for an M106 that i missed. I have not found it yet.

Phaedrux

@jkaechler add the m106 command I posted above to your config and try again.

dc42

@jkaechler said in Fan0 wont turn off.:

I dont have an M106 command in my config.g They are all removed at this point.

the output from the M106 P0 command is:
1:17:55 PMM106 P0
Fan 0 pin: F0, frequency: 250Hz, speed: 0%, min: 10%, max: 100%, blip: 0.10, inverted: no

I have been looking for an M106 that i missed. I have not found it yet.

If Fan0 was running when M106 P0 returned that message, then I suspect that the Fan0 mosfet on your board is blown.

JKaechler

@dc42

Thats a bummer. This board has been in a mounted in a project on hold for a few months, not in use but also way past a warranty exchange.

So, can I reprogram things to use the Fan2 output for the parts fan? I bet there is a guide on how to do that somewhere. I will start searching.

Phaedrux

@jkaechler https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans

You've got a few options.

JKaechler

Just for grins, i moved my part fan to the Fan2 header. its off. when i send M106 P2 i get:

Fan 2 pin: F2, frequency: 250Hz, speed: 0%, min: 10%, max: 100%, blip: 0.10, inverted: no

When i send M106 P2 S255, i happily spins up to full speed.
When i send M106 P2 S0, it comes to a full stop.

This is the expected behavior, and probably also a confirmation of what dc42 says about a blown mosfet. =(

Thats not something that can be fixed by the end user is it?
I bought my Duet Wifi from Filastruder quite some time ago.

I just need to tell my slicer that Fan2 is the part fan and i should be fine.

dc42

You can also use the F2 parameter in your M563 tool definition command to tell the firmware that the print cooling fan is fan 2 when that tool is selected.