Posts made by Cassiopeia

@achrn thanks for your detailed reply but as described above the fan starts spinning at M106 S0.4
if it would have started at M106 S0.2 I wouldnt have wondered.

I remember in klipper you could define some sort of starting current to give the fan some sort of "kick"

as you see by my language my knowledge in this area is very limited

Nevertheless even starting with M106 S.04 the lowest i can go afterwards is to M106 S0.3 but i cant start the fan with M106 S0.3

So i guess I will operate in the range of S0.4 - 1.0 which is fine for me. I just wanted to know if i can do something else in the configuration since the only thing i read about the fan PWM is that it should start at 20% (M106 S0.2)

@dc42 said in configuring a PWM 4 wire fan:

According to page 6 of the document you linked to, the fan should work down to 20% PWM or lower. The extract you posted refers to the tacho output signal, not the PWM input signal.
You said it is a 24V fan. Do you definitely have the VOUTLC jumper for that output block set to 24V not 12V?

yes the jumper is set on the left to VIN (24V)

the 20% in that document refers to some info from INTEL so i am not sure if it is ment in general.

so on Q25000 once i go over 40-45% i can go back down to 30% and its still spinning - it stops on 25% then

just FYI on Q500 it takes 85% to start - dont know if that info helps

i mean i will live with it just curious if i could improve someting in the settings

FYI thats the FAN
https://noctua.at/de/nf-a14-industrialppc-24v-3000-q100-ip67-pwm/specification

so i have a duet 3 6hc board a just connected a 24v noctua PWM fan to it.

My problem is the Fan starts first spinning at 45% is this normal or connected to the configuration of the fan?

config is

M950 F2 C"!out6" Q25000
M106 P2 S0.0 H-1

only info i could find on the PWM settings was

https://noctua.at/pub/media/wysiwyg/Noctua_PWM_specifications_white_paper.pdf

which doesnt make much sense to me since the max RPM is 3.000 that would mean by that formula 100 Hz?
or are we talking about 100.000Hz so in config <M950 Q100000>

@dc42 ok thanks..this is what initially thought. And i did a quick test with 2 dupont cables..and nothing happened, which was kinda confusing..so i guess ill try again with proper wiring.

so either the documentation is not clear on this or I am just not understanding it.
But how would I wire a physical reset button to duet 3 MB 6HC RESET_EXT ?
1 Pin is GND 1 is RESET they dont need to be shortened, do they?

so to just let everyone know who lands here with his heater fault problem:

I turned out that my fan duct position might cool the nozzle too much since i took off the silicon sock from the heater block.
On 100% fan speed the heater cant really get past 220C if the nozzle is 1mm away from the bed.

@jay_s_uk thank you.. i think i was to quick last night used:

M303 H1 S240 ; auto tune heater 1, default PWM (100%), 240C target

as I read instructions now i should use "M303 T0 SS40" and move the heater close to the bed which i didnt either...

was wondering why fans werent turned on but i saw tuning message fan off will do the PID again once everything cooled down

@jay_s_uk i think u might be on the right track..as i myself just thought of what else happens on layer 2 :)... so for tuning with M303 i need to turn on the part cooling 100% (which i didnt)??

can the cooling cause this problem?
2nd layer usually print cooling fan starts.
And i had for space issues turned my heat block 180 degree (dragon hotend) so the thermistor is at the backside.

unfortunatly that wasnt it.. the heater fault happend again!

Odly it happens when the 2nd layer starts.

1st layer is 40mms
2nd layer 200mms.

These settings have been working for PLA 200C
can this be a problem on PETG 230C?

@cassiopeia ok i just saw my self when I tuned the new heater i accidentally exchanged the PID falues for the bed heater not the extruder heater. I will change it and see if the fault happens again.

So i get the following fault:

Error: Heater 1 fault: temperature rising much more slowly than the expected 0.9°C/sec

m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-08-03 12:42:44

config.g

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sun May 23 2021 20:32:54 GMT+0200 (Central European Summer Time)

; General preferences
G90                                                          ; send absolute coordinates...
M83                                                          ; ...but relative extruder moves
M550 P"Duet 3"                                               ; set printer name
M669 K1                                                      ; select CoreXY mode

; Drives
M569 P0.0 S1                                                 ; physical drive 0.0 goes forwards
M569 P0.1 S1                                                 ; physical drive 0.1 goes forwards
M569 P0.2 S1                                                 ; physical drive 0.2 goes forwards
M569 P0.3 S1                                                ; physical drive 0.3 goes forwards
M569 P0.4 S1                                                 ; physical drive 0.4 goes forwards
M569 P0.5 S1                                                 ; physical drive 0.5 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3:0.4 E0.5                             ; set drive mapping
M671 X-33.188:143.021:319.23 Y-20.717:307.493:-20.717 S50
M350 X16 Y16 Z16 E16 I1                               		; configure microstepping with interpolation
M92 X160.00 Y158.60 Z803.80 E700.00							; set steps per mm
M566 X600.00 Y600.00 Z50.00 E1000.00						; JERK set maximum instantaneous speed changes (mm/min) /was X1800 Y1800 /quality 600
M203 X30000.00 Y30000.00 Z1800.00 E5400.00					; set maximum speeds (mm/min)
M201 X10000.00 Y10000.00 Z100.00 E2000.00					; set accelerations (mm/s^2) /was X1600 Y1600 /quality 4000
M906 X1400 Y1400 Z1600 E350 I30								; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                     ; Set idle timeout


; Axis Limits
M208 X0 Y0 Z0 S1                                             ; set axis minima
M208 X290 Y290 Z290 S0                                       ; set axis maxima

; Endstops
M574 X1 S1 P"io0.in"                                         ; configure active-high endstop for low end on X via pin io0.in
M574 Y1 S1 P"io1.in"                                         ; configure active-high endstop for low end on Y via pin io1.in
M574 Z1 S2   

; Z-Probe
M558 P9 C"^io7.in" H20 F800 T9000                            ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"io7.out"                                           ; create servo pin 0 for BLTouch
G31 P1000 X35.913 Y5.235 Z1.4;Z1.58;Z1.64;Z1.68;Z1.831       ; set Z probe trigger value, offset and trigger height //5015 self design G31 P500 X22.775 Y5.21 Z1.58
M557 X25:290 Y25:290 S50                                     ; define mesh grid /long X25:285 Y25:285 S20 

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950                 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                           ; create bed heater output on out0 and map it to sensor 0
M307 H1 B0 R2.463 C172.6 D6.62 S1.00 V24.0					 ;24V 50W
;M307 H0 B0 R0.850 C254.0 D1.74 S1.00 V24.0					 ;24V 40W
;M307 H0 B0 S1.00                                             ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                      ; map heated bed to heater 0
M143 H0 S140                                                 ; set temperature limit for heater 0 to 140C
M308 S1 P"temp1" Y"pt1000" R2200                             ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1                                           ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 R1.940 C350.0:238.3 D6.55 S1.00 V24.0
;M307 H1 B0 S1.00                                             ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                                 ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"out7"  ;Q100                                         ; create fan 0 on pin out4 and set its frequency
M106 P0 S0.0 H-1                                               ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out4" ;Q500                                          ; create fan 1 on pin out5 and set its frequency
M106 P1 T80 S1.0 H1                                           ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out2" Q500
M106 P2 S0.0 H-1 

; Tools
M563 P0 D0 H1 F0                                             ; define tool 0
M572 D0 S0.024												 ; pressure advance /was 0.06 /was 0.04 /was 0.034 /was 0.028 /now 0.02 300ms
M593 P"ei3" F50.2 											 ; Dynamic Acceleration (Input Shaping)
G10 P0 X0 Y0 Z0                                              ; set tool 0 axis offsets
G10 P0 R0 S0                                                 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M501                                                         ; load saved parameters from non-volatile memory
M911 S22 R23.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"         ; set voltage thresholds and actions to run on power loss
M955 P0 C"io4.out+io4.in"								     ;Accelerometer LIS3DSH
M81															 ;ATX/PSU Default OFF

I had a 24V 40W Heater which I switched to a 24V 50W heater when i had the same message the yesterday since then i did about 1-2hours of printing (PLA / ABS / TPU). So prints between 200-240C.

Both heaters where tuned using M303. S240

Now mit print printing PETG with 225C i get the heater failure again. Honestly i dont understand the problem after switching the hardware. Can it be the BETA??

BTW. when switching the new heater i renewed the wiring as well.

Any thoughts?

@phaedrux THX.. i should have asked earlier would have saved me couple of hours ...well i followed the unstable wiki and changed the branch and apt update & upgrade now DWC is working again. Didnt even had to flash 3.3 again. BIG THX

@phaedrux thx for your quick response i will try this next. (and give feedback)

FYI for everyone else reading this thread. Just for completion of troubleshooting:
The standalone mode works fine with the Beta.bin in /sys and the provided "Beta" DWC files in /www

So I had a perfectly running Duet3 when i tried to update to RRF3.4beta2 through the DWC. (From Stable 3.3)

Result was a loop of DWC saying its installing the Firmware. Honestly: I dont remember if it finished or if i killed the power. But it was at least running for 10-15 minutes.

So now i am stuck with:

my setup is a Duet 3 6HC with a Rpi4 connect (so SBC mode) the following log is created by 5V -> SBC by the Duet3

sudo journalctl -u duetcontrolserver

gives me the following

-- Logs begin at Mon 2021-08-23 18:41:58 BST, end at Mon 2021-08-23 20:08:11 BST. --
Aug 23 19:11:08 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:10 duet3 DuetControlServer[421]: Duet Control Server v3.3.0
Aug 23 19:11:10 duet3 DuetControlServer[421]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:10 duet3 DuetControlServer[421]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:10 duet3 DuetControlServer[421]: [info] Settings loaded
Aug 23 19:11:11 duet3 DuetControlServer[421]: [info] Environment initialized
Aug 23 19:11:11 duet3 DuetControlServer[421]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:11 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling resta
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 1.
Aug 23 19:11:11 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:11 duet3 DuetControlServer[558]: Duet Control Server v3.3.0
Aug 23 19:11:11 duet3 DuetControlServer[558]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:11 duet3 DuetControlServer[558]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Settings loaded
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Environment initialized
Aug 23 19:11:12 duet3 DuetControlServer[558]: [warn] Restarting transfer because the Duet received a bad respon
Aug 23 19:11:12 duet3 DuetControlServer[558]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:12 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling resta
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 2.
Aug 23 19:11:12 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:13 duet3 DuetControlServer[570]: Duet Control Server v3.3.0
Aug 23 19:11:13 duet3 DuetControlServer[570]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:13 duet3 DuetControlServer[570]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Settings loaded
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Environment initialized
Aug 23 19:11:14 duet3 DuetControlServer[570]: [fatal] Could not connect to Duet (Timeout while waiting for tran
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:14 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling resta
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 3.
Aug 23 19:11:14 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:15 duet3 DuetControlServer[590]: Duet Control Server v3.3.0
Aug 23 19:11:15 duet3 DuetControlServer[590]: Written by Christian Hammacher for Duet3D
lines 1-41...skipping...
-- Logs begin at Mon 2021-08-23 18:41:58 BST, end at Mon 2021-08-23 20:08:11 BST. --
Aug 23 19:11:08 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:10 duet3 DuetControlServer[421]: Duet Control Server v3.3.0
Aug 23 19:11:10 duet3 DuetControlServer[421]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:10 duet3 DuetControlServer[421]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:10 duet3 DuetControlServer[421]: [info] Settings loaded
Aug 23 19:11:11 duet3 DuetControlServer[421]: [info] Environment initialized
Aug 23 19:11:11 duet3 DuetControlServer[421]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:11 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:11 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 1.
Aug 23 19:11:11 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:11 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:11 duet3 DuetControlServer[558]: Duet Control Server v3.3.0
Aug 23 19:11:11 duet3 DuetControlServer[558]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:11 duet3 DuetControlServer[558]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Settings loaded
Aug 23 19:11:12 duet3 DuetControlServer[558]: [info] Environment initialized
Aug 23 19:11:12 duet3 DuetControlServer[558]: [warn] Restarting transfer because the Duet received a bad response (header)
Aug 23 19:11:12 duet3 DuetControlServer[558]: [fatal] Could not connect to Duet (Invalid protocol version 6)
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:12 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:12 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 2.
Aug 23 19:11:12 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:12 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:13 duet3 DuetControlServer[570]: Duet Control Server v3.3.0
Aug 23 19:11:13 duet3 DuetControlServer[570]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:13 duet3 DuetControlServer[570]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Settings loaded
Aug 23 19:11:13 duet3 DuetControlServer[570]: [info] Environment initialized
Aug 23 19:11:14 duet3 DuetControlServer[570]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:14 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:14 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 3.
Aug 23 19:11:14 duet3 systemd[1]: Stopped Duet Control Server.
Aug 23 19:11:14 duet3 systemd[1]: Starting Duet Control Server...
Aug 23 19:11:15 duet3 DuetControlServer[590]: Duet Control Server v3.3.0
Aug 23 19:11:15 duet3 DuetControlServer[590]: Written by Christian Hammacher for Duet3D
Aug 23 19:11:15 duet3 DuetControlServer[590]: Licensed under the terms of the GNU Public License Version 3
Aug 23 19:11:15 duet3 DuetControlServer[590]: [info] Settings loaded
Aug 23 19:11:15 duet3 DuetControlServer[590]: [info] Environment initialized
Aug 23 19:11:16 duet3 DuetControlServer[590]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
Aug 23 19:11:16 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
Aug 23 19:11:16 duet3 systemd[1]: Failed to start Duet Control Server.
Aug 23 19:11:16 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
Aug 23 19:11:16 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 4.
lines 1-49

The log shows the same when i power Duet 3 and the RPi4 both with external 5V. Duet via EXT 5V pin ( I am using PS_ON with an SSR to turn 24V PSU on and OFF)

If have been searching the forum for hours now...have reinstalled the SD card several times nothing helps. (including apt get update/upgrade etc...)

I have flashed the board succesfully via bossa (Windows USB)
M115 gives me:

m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-08-03 12:42:44<LF>ok<LF>

I dont know what else i can do?
The Diag light flashes with 1hz which it also has been when the duet was working..

The only thing i havent done is operating the board in Standalone mode.

@dc42
thanks for your quick response. upon further research the VSR pin takes 0-5V or PWM for the speed input of the fan. so i guess this will work with out9?!

HI all. so i have finished my first CoreXY printer with an duet3 6hc controller and id like to install a big centrifugal fan/blower as part cooling fan. Its a brushless 7040 fan (https://www.aliexpress.com/item/10000048326249.html?spm=a2g0o.cart.0.0.45413c00nJsmPg&mp=1) which needs to be connect with an extra driver.

So I have 2 questions
(I started with an Ender 3 V2 a year ago and well I have constantly been learning )

1. Do i need any extra precautions connecting the driver and blower to the duet3 board? (its rated max. 3A /peak 6A which should be covered by out_1-out_3 right? (Please screenshots for specs)

2. is the wiring correct? (Please screenshots for specs)
   a) 24v from either OUT_1,OUT_2 or OUT_3
   b) driver control from 5v PWM (out9)
   driver --> Duet3 (5V PWM(out9))
   +5V --> 5V_EXT
   VSR --> out9
   GND --> GND

What do i need to add to the config.g anything special or just like every other fan?

Your help is appreciated. Thanks