Fans not working after updating to RRF3.2

fcwilt

@GPetropoulos said in Fans not working after updating to RRF3.2:

One thing I can note for the installation of BLtouch that did not really make sense,
But it does not respond to M280 P3 S10 as I expected for the config,
but it responds to M280 P0 S10.

Well if it worked before you added the BLTouch I would, as a test, comment out all of the commands related to the BLTouch.

I see one that is wrong for v3.2: M307 H3 A-1 C-1 D-1

As to the M280: When you used this M950 S0 C"exp.heater3" the servo index parameter for M280 is P0 - as you have discovered. The P3 is for v2 firmware.

Frederick

GPetropoulos

@jay_s_uk 15:15:15
M950 P1
GPIO/servo port 1 has no pin
15:15:10
M950 P0
GPIO/servo port 0 pin (exp.heater3,exp.8) frequency 50Hz
15:15:04
M950 F1
Fan 1 pin fan1 frequency 500Hz
15:14:56
M950 F0
Fan 0 pin fan0 frequency 500Hz

GPetropoulos

@fcwilt Why is the M307 wrong?

jay_s_uk

@GPetropoulos its setting the fan pin up correctly.
Can you send

M106 P0 
M106 P1

GPetropoulos

@jay_s_uk 15:18:26
M106 P1
Fan 1, speed: 100%, min: 10%, max: 100%, blip: 0.10, temperature: 45.0:45.0C, sensors: 1, current speed: 0%:
15:18:19
M106 P0
Fan 0, speed: 0%, min: 10%, max: 100%, blip: 0.10

jay_s_uk

That shows that they are definitely being setup correctly in the firmware then.
Can I suggest reverting the installation of the BLTouch to confirm that hasn't caused an issue?

fcwilt

@GPetropoulos said in Fans not working after updating to RRF3.2:

@fcwilt Why is the M307 wrong?

That is only used with v2 firmware - v3 firmware uses a different approach - M950 - to assign pin function.

It's also likely the cause of the heater 3 error message.

Frederick

GPetropoulos

@jay_s_uk @fcwilt I went back to the stock config g from the config tool.
But it was not a solution. Then I decided I should check the wiring. Turns out one cable from each connector of the fans was loose and I easily removed them.

I put them back. The tool fan works now.
The other one does not.

I guess only way to find out is to check another fan/wiring directly on the board and see.

Phaedrux

I think you've gotten mostly sorted out on the config.g side. Post your current config if you want another check over.

The heatsink fan is set to thermostatic control, so it would only come on when at temp. To test it manually you can send M106 P1 H-1 S1 in the console. That should turn off thermostatic control and set the speed to full power.

Phaedrux

@fcwilt said in Fans not working after updating to RRF3.2:

Perhaps the firmware treats 1 as a special case - I don't know

Basically, yes. I suppose the best way to say it would be that 0 is always off and 1 is full power. Decimal values between 0 and 1 act as percentages. For 0-255 it would really start at 2 instead of 1. I don't know how best to explain that in documentation without getting incredibly long winded, but the point is probably moot since few fans would actually spin at 2/255?

fcwilt

@Phaedrux said in Fans not working after updating to RRF3.2:

Basically, yes. I suppose the best way to say it would be that 0 is always off and 1 is full power. Decimal values between 0 and 1 act as percentages. For 0-255 it would really start at 2 instead of 1. I don't know how best to explain that in documentation without getting incredibly long winded, but the point is probably moot since few fans would actually spin at 2/255?

Well I was curious and tested it under 3.2. I verified all this by using the Object Model viewer in DWC to check all fan values.

For a thermostatic fan S1 is mapped (so to speak) to S255.

The range S2 to S127 is mapped to S128 which is the 0.5 minimum mentioned in the docs.

The range S128 to S255 is used directly.

So really the only thing missing for the docs for a thermostatic fan is the special case of S1.

To confuse things further in the M106 used to configure the fan a missing S parameter seems to be treated as S255 but I would ignore documenting that.

Thanks.

Frederick

GPetropoulos

So I replaced the fan with a new one. Either that fan was bricked or it's cable.
Now everything seems to work right.

After all it was a wiring issue as no major changes to files were made.

Thank you all!