Maestro Mainboard Thermostatic Cooling



  • Re: M305 P101 and P102 for Maestro

    I am trying to get fan 2 providing thermostatic cooling for the MCU / drivers. While I can get the fan enabled, the thermostatic control isn't working yet. I am running RRF3.0 and this is my fan config:

    ; Fans
    M950 F0 C"fan0" Q500                                   ; create fan 0 on pin fan0 and set its frequency
    M106 P0 S0 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 T40                                      ; set fan 1 value. Thermostatic control is turned on
    M950 F2 C"fan2" Q500                                   ; create fan 2 on pin fan2 and set its frequency                        
    M106 P2 S2 T35:38 H100:101:102                         ; set fan 2 value. Thermostatic control is turned on for MCU / Drivers
    

    I was under the impression that H100:101:102 were reserved, but do I need to define them myself?



  • The drivers don't really report temperature. They only warn when they are about to overtemp.

    I'd either run the fan from MCU temp only, or just run it all the time.



  • @Danal said in Maestro Mainboard Thermostatic Cooling:

    The drivers don't really report temperature. They only warn when they are about to overtemp.

    I'd either run the fan from MCU temp only, or just run it all the time.

    That code comes right from the dozuki:

    M106 P2 T45:65 H100:101:102
    

    "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 put the 'S2' on my fan definition line, mistakenly following a pattern that wasn't there. I see now that it defines a PWM value. But if I set it to 'S1' like my thermostatically controlled hot end fan, it just turns on to that speed regardless of MCU temp , while the hot end fan correctly remains off until the setpoint is reached.

    Maybe an issue with H100?



  • With the following config:

    ; Fans
    M950 F0 C"fan0" Q500                                   ; create fan 0 on pin fan0 and set its frequency
    M106 P0 S0 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 T40                                      ; set fan 1 value. Thermostatic control is turned on
    M950 F2 C"fan2" Q500                                   ; create fan 2 on pin fan2 and set its frequency                        
    M106 P2 S1 H100 T100                                   ; set fan 2 value. Thermostatic control is turned on for MCU
    

    The case fan comes on at full speed, even though the MCU is 39*

    Fan 2 shows up in the dashboard control, shows 100% and allows me to manually turn it off there.

    Fans 0 and 1 show up also, but both sliders control Fan 0. Fan 1 is purely on thermostatic control. (so I'm not sure why it is listed)


  • Moderator

    I don't think H100:101:102 are used in RRF3. I think you'd need to define a sensor using "mcu-temp" and "drivers"

    https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M308_Create_or_modify_sensor_or_report_sensor_parameters

    The documentation for the MCU fan control will need to be updated. Sorry about that.



  • @Phaedrux said in Maestro Mainboard Thermostatic Cooling:

    I don't think H100:101:102 are used in RRF3. I think you'd need to define a sensor using "mcu-temp" and "drivers"

    https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M308_Create_or_modify_sensor_or_report_sensor_parameters

    The documentation for the MCU fan control will need to be updated. Sorry about that.

    Good call. So, something like this to define the sensor?

    M308 S100 Y"mcu-temp" 
    

    How to I link the fan thermostatic control to that sensor now? In M106 or M950? The S term seems used for things other than "sensor number" in those.



  • I found another thread with some good info: https://forum.duet3d.com/topic/13730/duet-2-wifi-reprap-3-mpu-fan-thermal-control/6

    M308 S2 Y"drivers" A"DRIVERS"    ; configure sensor 2 as temperature warning and overheat flags on the TMC2660 on Duet
    M308 S3 Y"mcu-temp" A"MCU"       ; configure sensor 3 as thermistor on pin e1temp for left stepper
    
    M950 F2 C"fan2" Q100                             ; create fan 2 on pin fan2 and set its frequency                        
    M106 P2 H2:3 L0.15 X1 B0.3 T40:70                ; set fan 2 value
    

  • administrators

    @Phaedrux said in Maestro Mainboard Thermostatic Cooling:

    I don't think H100:101:102 are used in RRF3. I think you'd need to define a sensor using "mcu-temp" and "drivers"

    https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M308_Create_or_modify_sensor_or_report_sensor_parameters

    The documentation for the MCU fan control will need to be updated. Sorry about that.

    That's all correct. In RRF2, a sensor can only be configured as part of a heater, using M305. So we introduced "virtual heaters" with heater numbers starting from 100, to use as dummy heaters when you are just interested in a temperature reading. In RRF3, sensors are configured separately from heaters, using M308, so we on longer use that workaround.


Log in to reply