Duet Wifi - how to set cooling fan?

eranglr

This post is deleted!

droftarts

@eranglr Can you send M122 and post the reply?

Ian

eranglr

@jay_s_uk yes, it is.
Could it be a jumper or something like that?

eranglr

@droftarts
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L4MSJ-6J1FL-3SN6T-TV16Q
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73136 of which 40 recycled
Never used RAM 15444, free system stack 182 words
Tasks: NETWORK(ready,188) HEAT(blocked,308) MAIN(running,379) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:43 ago, cause: power up
Last software reset at 2021-02-24 17:24, reason: User, GCodes spinning, available RAM 15444, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 35.1, current 38.2, max 38.5
Supply voltage: min 26.8, current 26.9, max 27.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-02-24 17:40:35
Cache data hit count 51187488
Slowest loop: 4.02ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 16.13ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address bc:dd:c2:31:9f:e7
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24208
WiFi IP address 192.168.202.42
WiFi signal strength -64dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0

jay_s_uk

@eranglr my guess is you've blown the fan mosfet.
Can you take a high quality close up photo of the area around the connector, specifically the area between the fan connectors and the two LCD headers

eranglr

@jay_s_uk This is a brand new card, so I doubt if I blow the MOSFET.

jay_s_uk

ok then, i'll let someone else step in and support

eranglr

@jay_s_uk Just for fun, where's the mosfet, and are there 3 mosfet (one for each fan)?

droftarts

@eranglr And it would be very unlucky if it's blown all the mosfets, as he said it was the same for FAN1 and FAN2.

Is there any chance the fan you are using is shorting out to ground somewhere else? Is it wired directly to the fan pin, or does it go through something else?

The MOSFETs work on the negative side of the fan, so the fan gets +ve volts all the time, so if there is a short on the negative side, it will always be on.

If you can post a photo of your wiring, that may help.

Ian

jay_s_uk

they are here for reference

eranglr

@jay_s_uk Doesn't look burnt.

eranglr

@droftarts The fan should be connected directly, but I'll check again to make sure.

eranglr

@droftarts Well, you were right!!
I connected a different fan directly and it worked perfectly.
I guess that the fan minus is touching the ground somewhere.. I'll need to check where.
Thank you!!

droftarts

@eranglr You're welcome!

Ian

eranglr

@droftarts Is there a smart solution to the wiring on my printer:
I have two fans that their negative is shared.
Is there a way to control the cooling fan somehow, or do I have to re-wire the fan to have an isolated ground?

droftarts

@eranglr I don't really see a way. Fan polarity is important; see https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans#Section_Caution
You could wire the positives together, but to switch them individually, you need the negative side connected to individual fan (or heater) MOSFETs. You may also have problems if the fans draw different current. Best to wire them separately.

Ian

jay_s_uk

@eranglr is it an anycubic printer?
I ended up fully rewiring mine

eranglr

@droftarts Ok, I'll rewire the fans.

eranglr

@jay_s_uk No, it's a custom build 3d printer made a long time ago.