Output_pin display name in GUI?

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’?

thx

Where is the template gone?

It asked for the klippy.log

There we could have shown you what you may can do…

1 Like

This is not a bug report or a “problem” (something is not working, etc)

I’m asking if the ‘Fan’ labels can be changed without renaming the macros in the CFG

It seems to be a “problem” because you want to have a different name for the fans.

Those can be set in the printer.cfg. And this appears in the klippy.log

2 Likes

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:

  1. If you can rename a fan depends on the type of fan you have configured
  2. Your configuration can be seen from the klippy.log
  3. A solid advice can only be given when seeing how you configured things
  4. @EddyMI3D pointed out exactly this fact

So, since it is a problem for you to follow a well meant advice: Read the official documentation here: Configuration reference - Klipper documentation and you will find your answer

2 Likes

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

klippy.zip (2.6 MB)

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.

1 Like

Your case is not a trivial one, and it would have been clearer from the beginning if you had followed the required template

  • You seem to be using a Creality K1
  • Creality is using a modified Klipper version
  • Your fans are deeply embedded into macros
  • As @theophile pointed out, they are defined as PWM out pins:
[output_pin fan0]
pin = !nozzle_mcu: PB8
pwm = True
cycle_time = 0.0100
hardware_pwm = false
value = 0.00
scale = 255
shutdown_value = 0.0
  • You can rename them, but it likely requires renaming every occurrence of fan0 etc or otherwise your macros will no longer work
  • If you give them a name like My_Cool_Fan then the webinterfaces are clever enough to rename them to My Cool Fan

To make it clear: This is not a Klipper limitation but comes from the special way Creality chose to define this

Thanks for the answers here…Creality strikes again!

To make it a little simpler for Klipper newbs like myself

[output_pin Your_Fan_Name]

Usual format rules of no spaces, underscores converted to space by Fluidd/Mainsail

@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.

This is kind of a chicken-egg argument:

  • Klipper allows for proper naming
  • Creality chose to implement the functionality in a non-standard way that obfuscates the functionality for inexperienced users
  • Creality is violating Klipper’s license

Why should Klipper invest work to tidy up behind such a manufacturer, even more so when the relevant functionality is given?

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.