Idle 4028 part cooling fan
Hello! I'm back with another question on my setup (now that I have a brand-new-and-working ebb42 :D)
I'm using a 4028 fan for part cooling.
Problem is: 4028 fan is not starting with M106 255 gcode command. It moves a mm but that's it. And no reading on the tachymeter either.
I've followed the RatOS guide for wiring the 4028 fan (model FFB0412EN-00 from Delta, wiring guide in the pic).
https://os.ratrig.com/docs/guides/4028/
You can see the config attached, with my wiring and the associated pinouts.
I've overridden the aliases from the octopus 1.1 board to be able to add naming for the usage of the new pins.
You can see a commented section and a non-commented one I've tried without any luck.
Is there something I've missed? Thanks a lot 🙂
Connecting a 4028 fan | RatOS
4028 server fans are becoming a popular option for part cooling because of their light weight and great pressure and flow rates. In this guide we'll go over how to connect one and use it for part cooling. 4-pin fans usually aren't used in 3d printers, and many boards only provide 2-pin ports, but fear not! There's always a way.
14 Replies
you only changed the fans in the custom aliases.
this is not what you are supposed to do, just override the pin definitions in the
USER OVERRIDES sectionI've searched to do that with the custom_aliases.cfg loaded instead of the octopus alias declaration.
When I directly created my aliases in the user_override sections, I wasn't able to make klipper accept the conf
So basically, I've created my own aliases file with these additions
Then instead of loading the board definition, I load mine here
And then, I expected the aliases to be available to use (klipper is not crashing, whereas it does when I wrote unloaded aliases)
If I declare the custom aliases in the section overrides, it's KO, but maybe I'm doing it wrong...
Also, I was wondering if you had some kind of debug/console.log abilities
Don't use the aliases in the USER OVERRIDES section. Use the actual pin names
Okey thanks. I thought I could be smart with this hahaha. I'll do it without, and keep you posted. Thanks
I've reverted back to using the pin names. Nothing had changed.
The fan is doing 1mm move every 5s or so.
upload new printer.cfg
I've found one of the issue 😄
4028 are server fans. As a safety feature, if not PWM is provided, the fan is at full speed. So an IDLE fan that is not responding to any PWM command can only mean that the power line is faulty and that it's an electrical issue.
So I've investigated the circuit and one JST was cut. Now the fan is properly powered and at 100%.
It's not solving the PWM and tachymeter issue, but at least, we have somewhere to go 🙂
(printer.cfg on the way)
The fan is behaving as there is no pwm. Meaning it's either bad conf, bad electronic or incompatibility with the signal.
The conf is directly copy pasted from the doc (I've had a hard time understanding how you can PWM only using the ground pin, but it's clearer now).