RRF2.05.1 - M206 commands not turning on any fans
-
I have recently upgraded my (authentic, not cloned) Duet Wifi to RRF2.05.1 and in the process I was also trying to eliminate a lot of the ringing coming from my part cooler fan (2-wire, on P0) by raising the PWM (F parameter) to 32768, which is half of the max allowed value. I figure that way if it does produce a carrier frequency from the motor at least it's above the range of human hearing. Once I did that I was able to adjust the motor speed and not hear any extra sound from it. A few test prints later, I now see no movement from the motor, even when I lowered the PWM frequency back down to F500. I see zero voltage on the wire, but the motor itself moves easily with an external 5v source.
I dread to think about it, but what's the likelihood that I have some kind of failed component on the board from this?
Thanks in advance!
-Brendan -
Here's my config.g file which shows what I'm doing
config.gI use two fan outputs for the case fan so that it turns on either in response to the extruder being on, or if the CPU is warm. That combination was working fine in the previous firmware (and in this version also, until it just stopped working.) I otherwise haven't made any changes to wiring or otherwise.
-
Can you send M122 and post the results?
Does your duet have a fan fuse? If so, check to see if it's intact or not.
are you running the fans at 5v, 12v, 24v? Since you mention 5v source to test the fan, I assume 5v?
Does the always on fan header work?
Does the hotend fan still come on when the temp goes above 45c? -
Presumably the topic title is a typo as M206 is for "offset axis" while M106 is for fan control?
-
I assume so, his config.g does have M106 commands...
-
Thanks @Phaedrux and @bearer! The fans are all actually 12v but I figured 5v was a safer test for a basic dumb 2-wire fan. The always-on fan is running a 12v Noctura without any issues, but the case fan (P1) and the part cooler (P0) do not turn on at all, sadly. You're right - I mistyped and we are talking about M106, sorry. Neither P0 or P1 come on for any reason, even if I set them with a H-1 parameter and their speeds to full (tried both S1.0 and S255, no dice on either attempt.)
How do I locate the fan fuse? I'm not terribly gifted with surface mount soldering, but is there a guide on testing/replacing the fuse if it is gone?
M122 reports the following:
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J9D8-3SN6K-T3V3Y
Used output buffers: 3 of 24 (6 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93176 of which 0 recycled
Exception stack ram used: 272
Never used ram: 11912
Tasks: NETWORK(ready,628) HEAT(blocked,1232) MAIN(running,3800) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:00:43 ago, cause: power up
Last software reset at 2020-04-03 16:31, reason: User, spinning module GCodes, available RAM 11912 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 13.1, current 18.0, max 18.1
Supply voltage: min 12.3, current 12.3, max 12.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2020-04-03 19:42:56
Cache data hit count 123108018
Slowest loop: 8.41ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 41.53ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 5c:cf:7f:76:6d:f6
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22008
WiFi IP address 192.168.1.224
WiFi signal strength -60dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@badvision said in RRF2.05.1 - M206 commands not turning on any fans:
How do I locate the fan fuse?
that'll be the 1A mini blade fuse. ref https://duet3d.dozuki.com/Wiki/Hardware_Overview
-
It's a fuzzy picture but I think I have a 1.03 rev board. Only the 1.04 has fan fuses, no?
-
@badvision said in RRF2.05.1 - M206 commands not turning on any fans:
It's a fuzzy picture but I think I have a 1.03 rev board. Only the 1.04 has fan fuses, no?
my bad, missed you had an older board.
1.03 has a blade fuse
1.02 does not have a fuse.
revision is printed in the yellow circle, and the fuse may or may not be under the wiring in the red circle. looks like there could be a fuse, but hard to tell from picture.
-
Assuming that it is a blown fuse, is it possible that a high PWM rate would have caused that? If so, what is a good value for the F parameter for 2-wire fans that does not result in high-pitch squeals? Low value (like the default F500) with a capacitor to smooth the output?
-
@badvision said in RRF2.05.1 - M206 commands not turning on any fans:
Assuming that it is a blown fuse, is it possible that a high PWM rate would have caused that?
doubt it, them blade fuses are quite slow. just pull it out and look at it, you should see if its good or not.
-
@badvision said in RRF2.05.1 - M206 commands not turning on any fans:
Assuming that it is a blown fuse, is it possible that a high PWM rate would have caused that? If so, what is a good value for the F parameter for 2-wire fans that does not result in high-pitch squeals? Low value (like the default F500) with a capacitor to smooth the output?
Low value, but do not use a capacitor to smooth the output.
-
@dc42 Understood, but is there no other way to avoid the PWM carrier frequency from turning the fans (usually somewhat quiet at full) into screeching weasels at 50% speeds?
-
suppose one option is buying fans that support speed control, or even adapting to use 4wire fans which all support it.
-
Can confirm, the fuse is blown to hell. Thanks so much you guys! Very relieved that I don't have to replace the board. What a great design!!!
-
@bearer good idea but rewriting my part fan would require too many wires. I already configured around a db25 connection for low-amp and motors and 6-pin mil-spec din for the high-amp stuff. Thanks for helping me know all my options.
-
@dc42 -- Using F50 for the part fan it is throttling using a low PWM frequency and is doing just fine. Not sure why I missed the bleeding obvious. Thanks again!
-
Old filament so I'm not surprised by the zits on the print but the cooling fan was definitely not an issue here. Woo! Thanks a million you guys!