My printer has several fans and in Fluidd they show as “Fan 1”, “Fan 2”, etc… I’d like to name them something meaningful (exasut, etc).
Searched all CFG files but that exact text is not anywhere.
Does Klipper reformat output_pins names before passing to Mainsail?
or do i need to enter a feature request for adding a CFG parameter ‘display_name’?
I searched for ‘fan1’ and Klippy log has nothing the CFG doesnt have. There is nothing in there that helps answer "can we set a name in for fan1 without changing the macro
If you want to help please do I would appreciate it… but your answers are nothing informative, just snarky.
Not even close to snarky and I’m very much tempted to answer snarky since you are just burning our time that we spend in our free time to support folks like you:
If you can rename a fan depends on the type of fan you have configured
Your configuration can be seen from the klippy.log
A solid advice can only be given when seeing how you configured things
I read G-Codes - Klipper documentation before asking my question. If there is a different section to see please LMK I didnt any other info in the docs or after several web searches.
Klippy.log attached. Please let me know ‘what’ we are looking for in the log (teach a man to fish)
Looking at the documentation " I didnt see anything about alternate display naming (different display name in the UI vs the CFG)
And thus asking “can we have a different display name show in the UIs” . If it is not currently possible I will put in a feature request because I think it is better (for everyone) to see Extruder Fan / Exhaust Fan / Cooling Fan and not Fan 1 / Fan 2 / Fan 3
From your log, it looks like you named these output_pins fan0, fan1, and fan2. I think Fluidd is parsing these names to add the capitalization and the space before the number. You are certainly free to rename them to make them more helpful to you.
@Sineos ability to create an ‘alias’ for any output_pin name would be helpful in a few ways at least. For this use case I want to have it named something meaningful in the GUI and not need to change existing macros by the manufacturer.
Something to consider… Klipper is awesome and has mainly been DIY. As more manufacture’s integrate it, its becoming the standard, and having more non-techie, user friendly features would be of great benefit to all.