FAN 0 & FAN 1 allways ON

Gixxerfast

@cozyp Can you run m98 P"/sys/config.g" and post whatever shows in the console?

As far as I can see right now, the last M106 is still referencing a heater that prpbably doesn't exists. H100 ?

So just to make it clear:

Fan 0 is part cooling fan, which is controlled by slicer GCode commands
Fan 1 is the extruder fan which is controlled by the temp of heater 1 and should turn on whenever thet temp is over 45
Fan 2 is the controller fan which is controlled by sensor MCU temp that you have probably defined that somewhere?

Here's mine:

; Define MCU sensors which will be available in DWC Extra View
M308 S3 A"MCU" Y"mcu-temp" 				; Officially NOT supported on Mini 3 5+ however seem to work
M308 S4 A"Duet Drivers" Y"drivers" 		; This is not really working as it is just a threshold crossing

And I'm referring to those with:

; ==================================
; MCU fan
; ==================================
M950 F2 C"!0.out4+0.out4.tach" Q25000              ; create fan 2 on pin out4 and set its frequency
M106 P2 H3:4 L0.2 X1.0 T30:50 C"Controller fan 1"  ; controlled by Sensor 3&4 - MCU& Drivers

fcwilt

@gixxerfast said in FAN 0 & FAN 1 allways ON:

@cozyp Can you run m98 P"/sys/config.g" and post whatever shows in the console?

As far as I can see right now, the last M106 is still referencing a heater that prpbably doesn't exists. H100 ?

H100 refers to the "virtual heater" and is used to monitor the processor chip temperature. That could be used for the fan cooling the board.

Frederick

Gixxerfast

@fcwilt Edit: No it isn't ~~Is H100 predefined as MCU temp?~~

fcwilt

@gixxerfast said in FAN 0 & FAN 1 allways ON:

@fcwilt Edit: No it isn't ~~Is H100 predefined as MCU temp?~~

From the documentation:

The fourth example sets up an electronics cooling fan that starts to turn on when the MCU temperature (virtual heater 100) reaches 45C and reaches full speed when the MCU temperature reaches 65C or if any TMC2660 drivers (virtual heaters 101 and 102) report that they are over-temperature

I can only assume the documentation is correct.

Frederick

Gixxerfast

@fcwilt Yes, that sound reasonable which made me try it as I set it up explicitly.

I changed my config to:

M106 P2 H100 L0.2 X1.0 T30:50 C"Controller fan 1"

When I run that config I get:

Error: Sensor number out of range

Also, when I look in the code I see nothing that suggests that there exists predefined sensor numbers

The sensor number list that s set via the H flag is checked with this:

if (hnum < (int)MaxSensors)
					{
						sensorsMonitored.SetBit((unsigned int)hnum);
					}
					else
					{
						reply.copy("Sensor number out of range");
						error = true;
					}

And as far as I can see the MaxSensors is between 32 or 56 depending on board. I am very likely reading something wrong here as it's not very quickly easy to see what MaxSensors is defined to in this case.

Phaedrux

@fcwilt said in FAN 0 & FAN 1 allways ON:

@gixxerfast said in FAN 0 & FAN 1 allways ON:

@fcwilt Edit: No it isn't ~~Is H100 predefined as MCU temp?~~

From the documentation:

The fourth example sets up an electronics cooling fan that starts to turn on when the MCU temperature (virtual heater 100) reaches 45C and reaches full speed when the MCU temperature reaches 65C or if any TMC2660 drivers (virtual heaters 101 and 102) report that they are over-temperature

I can only assume the documentation is correct.

Frederick

Yes it is correct in RRF2. And in RRF3 you can target the virtual heaters by name now. mcu-temp

Is that text from the cooling the board page?

Yes. And it does show both RRF2 and RRF3 options.

https://duet3d.dozuki.com/Wiki/Mounting_and_cooling_the_board#Section_Notes

Gixxerfast

@phaedrux It's from here as far as I can see: https://duet3d.dozuki.com/Wiki/M106

But can you really refer to it via number >=100 in the H parameter ?

I see nothing that implies that.

OK, so with RRF V3 you cannot use +100 to refer to the MCU or other sensor (virtual heater) as I initally wrote far above here somewhere.

fcwilt

@phaedrux said in FAN 0 & FAN 1 allways ON:

Is that text from the cooling the board page?

It was from the M106 documentation page:

M106

It mentions v3 firmware and references M308 which is where there are references to virtual heater names.

The H parameter relates to the sensor number(s) created by M308, not the temperature sensor pin number on the board.

Perhaps that could be expanded a little to provide a bit more info as to the connection between M308 and virtual heaters, etc.

Frederick

Phaedrux

Maybe just a link to this?

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Temperature_configuring_mcu_temp

In RRF2 the virtual heater number would go directly into the M106 command. But in RRF3 it's a bit more abstracted with M308 creating the sensor first. The entire example is almost out of scope for the normal usage of M106, especially in RRF3.

fcwilt

@phaedrux said in FAN 0 & FAN 1 allways ON:

Maybe just a link to this?

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Temperature_configuring_mcu_temp

In RRF2 the virtual heater number would go directly into the M106 command. But in RRF3 it's a bit more abstracted with M308 creating the sensor first. The entire example is almost out of scope for the normal usage of M106, especially in RRF3.

That looks fine.

It took me to a site that I was not aware of. Is that the current site for documentation?

Is the "Gcode dictionary" site obsolete?

Thanks.

Frederick

Phaedrux

@fcwilt said in FAN 0 & FAN 1 allways ON:

Is the "Gcode dictionary" site obsolete?

It's back like it was before!

https://docs.duet3d.com/en/User_manual/Reference/Gcodes

@fcwilt said in FAN 0 & FAN 1 allways ON:

It took me to a site that I was not aware of. Is that the current site for documentation?

The new documentation site went is live now.

https://docs.duet3d.com/

The old dozuki site will be archived and retired at some point I believe.

fcwilt

@phaedrux said in FAN 0 & FAN 1 allways ON:

The new documentation site went is live now.

I didn't even know it was planned.

Thanks.

Frederick

droftarts

@fcwilt it hasn’t been announced formally as we’re still tinkering with it, and there’s still a few pages to add, but it’s live and what we are generally using now. We’ll be formally announcing it and posting messages on the Dozuki pages to redirect people to the new site in the next couple of days. It’s taken quite a few months to migrate and update it! That’s why I haven't been around on the forum as much.

Ian

fcwilt

@droftarts said in FAN 0 & FAN 1 allways ON:

@fcwilt it hasn’t been announced formally as we’re still tinkering with it, and there’s still a few pages to add, but it’s live and what we are generally using now. We’ll be formally announcing it and posting messages on the Dozuki pages to redirect people to the new site in the next couple of days. It’s taken quite a few months to migrate and update it! That’s why I have been around on the forum as much.

Ian

At first glance it looks grand.

Thanks much for your efforts.

Frederick

CozyP

@fcwilt

hELLO

I updated fan 2.

However I haven't managed to make fan 1, which is the extruder cooler fan stop and turn on when the heater turns on.

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
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
M308 S10 Y"mcu-temp" A"MCU" ; defines sensor 10 as MCU temperature sensor
M308 S11 Y"drivers" A"Duet stepper drivers" ; defines sensor 11 as stepper driver temperature sensor

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S1 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q100 ; create fan 2 on pin fan2 and set its frequency
M106 P2 H10:11 T40:70 ; set fan 2 value

fcwilt

@cozyp

If configure that fan to non-thermostatic control can you then set it's speed using it's DWC fan speed slider?

Frederick

Phaedrux

Or send M106 P1 S1 H-1 That should turn it on full blast.

CozyP

@fcwilt I have connected this fan in the non PWM fan output

CozyP

@phaedrux That's the problem. The extruder fan, NOT the part cooling fan is running full blast. Allways. Usually these fans turn on after T45celcius automatically

Phaedrux

Sorry, can you clarify which fan is connected where?

What happens when you send M106 P1 S1 H-1 ?