Wrong FAN configuration on ressurect.g

Phaedrux

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip

Can you upload that zip file to the system tab in DWC?

Not sure if the .2 update would make a difference or not. If not, it's probably a bug for @dc42

Cartola

@phaedrux said in Wrong FAN configuration on ressurect.g:

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip

Can you upload that zip file to the system tab in DWC?

Not sure if the .2 update would make a difference or not. If not, it's probably a bug for @dc42

I will make the 2 tests you suggested today I will return with the results. Thanks for the help!

Cartola

@phaedrux said in Wrong FAN configuration on ressurect.g:

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip

Can you upload that zip file to the system tab in DWC?

Not sure if the .2 update would make a difference or not. If not, it's probably a bug for @dc42

I did the test where I added the S1 parameter to M106 P1 H1 T45 C"Fan Extruder" ; Set fan 1 value. Thermostatic control is turned on, but it didn't worked.

I uploaded the firmware 3.2.2 and now I cannot connect to DWC. I checked my router and it seems the board cannot connect to the wifi.

Cartola

@phaedrux I could connect to the board and I had the same result. Do you think it is a bug?

New firmware:

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2.2 (2021-02-11)
Duet WiFi Server Version: 1.25

Phaedrux

Yes possibly a bug. Will need to have DC42 confirm.

dc42

@cartola, I confirm that this is a bug. It's saving the settings of the thermostatic fans instead of the non-thermostatic ones. The fix will be in 3.3beta3.

Cartola

@dc42 Thanks! Do you want me to open a bug on github or something like that? By your response it seems it is a known bug already, but let me know if I need to do something.

Thank you again for the great work!

Phaedrux

@cartola Thanks for the offer, but in this case I think the fix is already in.

Cartola

@phaedrux cool

Thanks, I think this topic can be closed.

Phaedrux

@cartola Well once beta3 is out you could test it to see if it resolves the issue then close it as solved.

Cartola

@phaedrux Sounds good.

dc42

@cartola, I will mark this as solved. Feel free to revert it if you still think it's still not right in beta 3.