4 pin Fan cant be controlled

Im trying to use the FAN5 port 4 wire fan on my octopus max EZ ... created a fan_generic in my overrides but I cant control the fan ... only if I disconnect the blue cable the fan runs at 100% ... in my printer.cfg all fans are still with # ... what is my mistake here again
No description
No description
30 Replies
blacksmithforlife
please upload your printer.cfg and pictures of your wiring on your octopus max board
DOAmatrix
DOAmatrixOP11mo ago
as side info ... my toolboard USB is damaged that why I removed the toolbard sections for the moment
DOAmatrix
DOAmatrixOP11mo ago
FAN is connected like the Hotend Fan in the picture ...
blacksmithforlife
hotend fan or part cooling fan? because in your printer.cfg you have part cooling fan
DOAmatrix
DOAmatrixOP11mo ago
I used FAN 5... so it is using the hotend Fan connection because later the hotend Fan will be connected to the EBB42
blacksmithforlife
try heating up your hotend and see if it turns on. I suspect because you haven't changed the config for your hotend fan it is still using the FAN5 port for that
DOAmatrix
DOAmatrixOP11mo ago
I cant because my EBB is broken ... thats why the toolboard is with # ...
Luigivaba
Luigivaba11mo ago
Ok, I already did exactly that and here is how it looks:
Luigivaba
Luigivaba11mo ago
No description
Luigivaba
Luigivaba11mo ago
No description
Luigivaba
Luigivaba11mo ago
No description
Luigivaba
Luigivaba11mo ago
And so on. You cannot reuse pins that have already been designated in the aliases. This means: You have to mirrior ALL board aliases in use and #-out all the includes Then you have to go through all includes one at a time to understand what you have to put in the printer.cfg and # them all out. This is about 2h of work.
DOAmatrix
DOAmatrixOP11mo ago
Uff ... that sounds like a lot of work ... isnt there any work around ? part cooling fan is also connected cause I dont use the EBB42 pins ... i used 4 wires between toolhead and mainboard
Mietzekatzi
Mietzekatzi11mo ago
Can you send your klippy.log?
Mietzekatzi
Mietzekatzi11mo ago
Hmmm, that looks right. Have you tried a higher cycle_time?
Mietzekatzi
Mietzekatzi11mo ago
So, I just connected a 4pin Noctua to my mainboard and this works... I simply pasted it into the Override section. stare Also works if I place it inside a overrides.cfg, as you
No description
No description
Mietzekatzi
Mietzekatzi11mo ago
Have you verified, that the fan is okay? Maybe test it inside your PC (if you can control the PWM there)?
DOAmatrix
DOAmatrixOP11mo ago
OMG , i just double checked the connector and found the connection was bad ... thanks to everybody and sorry for my stupidity
Mietzekatzi
Mietzekatzi11mo ago
kek
DOAmatrix
DOAmatrixOP11mo ago
any recommendation for good 4 pin connectors ?
Mietzekatzi
Mietzekatzi11mo ago
I'm using regular 4 pin fan connectors, as used in PCs. Thats what the socket is made for. Got mine from here, but they might even be included in the Max EZ accessories? https://www.cable-sleeving.com/4-pin-fan-connector
MDPC-X
4-pin FAN Connector
This latest generation 4-pin fan connector is compatible to all fan connections on your PC motherboard. You can use these 4-pin FAN connectors with…
DOAmatrix
DOAmatrixOP11mo ago
Yes this i used for the Board... i mean like a cable to cable connector ... this is what i used
No description
Mietzekatzi
Mietzekatzi11mo ago
Ah interesting. I’m also using one for the wire-to-wire connection to the toolhead, but it’s wrapped with heatshrink to avoid it coming loose Yours looks better for this purpose! Maybe Microfit Jr might be an option
DOAmatrix
DOAmatrixOP11mo ago
bought them on amazon ... used the same on the toolbard for the part fan ... but is really big for this wire size
miklschmidt
miklschmidt11mo ago
Just a correction here. You can use any alias for the pin you want, and define as many aliases as you want, the only limitation is that you can only use one alias for the same pin in your config. So your actual use of the alias has to be unique, you can assign a pin to as many aliases as you want. For that reason all this copy pasting of code is very unfortunate and not necessary at all. In the includes & overrides section on the RatOS website it is recommended that you just use the pin names from your boards pinout diagram.
Luigivaba
Luigivaba11mo ago
This would not really help, as the previous aliases do not go away. Even if you use the pin he throws an error even if the prior use for the pin and its alias has expired (i.e. if you use a toolbord you cannot reuse the board fan pin for sth. Else until you decontruct every include).
miklschmidt
miklschmidt11mo ago
This would not really help, as the previous aliases do not go away.
They don't need to go away.
Even if you use the pin he throws an error even if the prior use for the pin and its alias has expired
I'm not sure what "expired" means. You should only use a pin for 1 single assignment. If you get an error when overriding that pin is used somewhere else in your config. Klipper config files are merged when loaded, no section and no parameter appear twice.
(i.e. if you use a toolbord you cannot reuse the board fan pin for sth. Else until you decontruct every include).
This is incorrect. I'll give you a practical example This is a valid config:
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2

[fan]
pin: my_pin

[fan]
pin: toolboard:my_pin

[fan]
pin: my_other_pin
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2

[fan]
pin: my_pin

[fan]
pin: toolboard:my_pin

[fan]
pin: my_other_pin
It results in
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2

[fan]
pin: my_other_pin
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2

[fan]
pin: my_other_pin
This is an invalid config:
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2


[fan]
pin: my_pin

[fan someotherfan]
pin: toolboard:my_pin

[fan somethird fan]
pin: my_other_pin
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2


[fan]
pin: my_pin

[fan someotherfan]
pin: toolboard:my_pin

[fan somethird fan]
pin: my_other_pin
This is an invalid config It results in:
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2


[fan]
pin: my_pin

[fan someotherfan]
pin: toolboard:my_pin

[fan somethird fan]
pin: my_other_pin
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2


[fan]
pin: my_pin

[fan someotherfan]
pin: toolboard:my_pin

[fan somethird fan]
pin: my_other_pin
And both my_pin and my_other_pin refer to PA0 This is also a valid config:
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2


[fan]
pin: PA0
[board_pins]
aliases:
my_pin=PA0, my_other_pin=PA0

[board_pins toolboard]
mcu: toolboard
aliases:
my_pin=PA2


[fan]
pin: PA0
(i edited my_other_pin to be PA0 in all cases to make it more clear) I think what might have thrown you off is the use of [multi_pin]. That section in particular has special snowflake status.
Luigivaba
Luigivaba11mo ago
Yeah. I see now. No worries: Printer is runnibg smoothely! Next large rebuild Ill think to fix that.
miklschmidt
miklschmidt11mo ago
Just for further information now that this stuff is getting indexed on the web, see the quirk about [multi_pin] here: https://discord.com/channels/582187371529764864/843098069200666634/998705954541551769
Want results from more Discord servers?
Add your server