{Solved} Part cooling fan won't run with gcode D3+3.2b2
-
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2-beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-10-05b2
M115 B121
Board TOOL1LC firmware 3.1.0 (2020-05-15b1)Part cooling fan will only run when activated with the sliders in DWC. Won't run on the paneldue (3.2.0). Just goes back to 0%. Won't run when printing. Won't run with M106 S255 in the console in DWC or paneldue.
M98 P"0:/sys/config.sys" show no errors.
The config tool sets the tool board id to 1, had to change it to 121. Reported as an issue to github.
; Fans
M950 F0 C"121.out2" Q500 ; create fan 0 on pin 1.out1 and set its frequency
M106 P0 C"Part Cooling" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"121.out1" Q500 ; create fan 1 on pin 1.out2 and set its frequency
M106 P1 C"Hotend" S1 H1 T45 ; set fan 1 name and value. Thermostatic control is turned on -
Can you post your tool definition as well?
-
@Phaedrux As defined by the config tool:
; Tools
M563 P0 D0 H1 F-1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C -
@Stephen6309 said in Part cooling fan won't run with gcode D3+3.2b2:
M563 P0 D0 H1 F-1
F-1 would mean unmap all fans.
You need to tell it which fans to use for your tool. Based on your M106 P0 C"Part Cooling" you should have F0
M563 P0 D0 H1 F0
-
Found another bug in the config tool.
-
@Stephen6309 said in {Solved} Part cooling fan won't run with gcode D3+3.2b2:
Found another bug in the config tool.
Can you post the config.json file from the configurator that produced the fan mapping result?
-
@Phaedrux That tool list is from my config file. The CAN ID for the tool board was edited to 121, the boards default. The M582 and M522 are commented since the SBC complains about them. The PWM output was changed to 121.io0.out due to the config tool only allows temp0 and temp1. The config.json has been edited with the IO changes, so that the tool board IO comes up blank on the config tool.
