Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request - Fan Alias #2005

Closed
dfbpurcell opened this issue Sep 10, 2024 · 1 comment
Closed

Feature request - Fan Alias #2005

dfbpurcell opened this issue Sep 10, 2024 · 1 comment
Labels
💡 Type: FR Requests a new feature

Comments

@dfbpurcell
Copy link

Requested feature:

It would be great to be able to assign an alias to the pins in the miscellaneous tab. I renamed them in the printer.cfg, which renames them in the mainsail interface but they are still referenced elsewhere whether it be in gcode or in the printer files im not sure. And I'm too stupid to figure out how to fix it. This means they no longer work when printing if you rename them.
image

Solves the following problem:

Allows you to name the pins without messing up the functionality. Avoids confusion between fans, allows for easy remote control without having to go back and forth to see if you activated the right fan.

Additional information:

No response

@dfbpurcell dfbpurcell added the 💡 Type: FR Requests a new feature label Sep 10, 2024
@meteyou
Copy link
Member

meteyou commented Sep 10, 2024

Thank you very much for your feature request, but unfortunately, I have to reject it. one of our main principles is that the hardware in Mainsail is named exactly as in the config, making it easier to find the corresponding config. This question is being asked more often, but only in connection with current new vendor printers (mostly Creality k1). Here, the vendors should provide clean configurations. When I see your screenshot above, I notice several incorrect configurations here (all output_pin modules instead of LEDs or fans).

But if you want to clean/fix your config and need help, please join our Discord server or open a post in the discussions area here on GitHub.

@meteyou meteyou closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 Type: FR Requests a new feature
Projects
None yet
Development

No branches or pull requests

2 participants