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.

Sign up for GitHub

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

Jump to bottom

Rework fan handling #35

Open
PaulNokel opened this issue Jul 28, 2018 · 5 comments
Open

Rework fan handling #35

PaulNokel opened this issue Jul 28, 2018 · 5 comments
Labels
enhancement

Comments

@PaulNokel
Copy link

Hi,

I recently moved my part cooling fan to a pin header on the Duex and assigned it using M563 to the tool (from Fan 0 to Fan 6). I can change/see the speed in DWC. But the PanelDue is always showing 0% and it is not possible to change the speed.

Best regards,
Paul
@smoki3
Copy link

smoki3 commented Oct 24, 2018 •
edited
Loading

Yeah same here. It it also only showing the fan 0 speed and not the active tool fan speed

@dc42
Copy link
Collaborator

dc42 commented Oct 27, 2018 •
edited
Loading

I suspect you are using old PanelDue firmware. Version 1.22 is current. In that version, the speed can be changed even when the fan is mapped; however the current speed is not shown correctly.

@smoki3
Copy link

smoki3 commented Oct 28, 2018

@dc42 yes changing the speed is possible. but it is not showing the correct one.

@wilriker
Copy link
Contributor

wilriker commented Sep 29, 2020 •
edited
Loading

It's planned to improve fan control in version 3.3.

Currently only one fan can be controlled (Fan 0). This should be reworked into either

  • a simple fan popup to control all fans or
  • the fan control should be controlling the fan of the current tool

@wilriker wilriker modified the milestones: 3.2, 3.3 Sep 29, 2020
@wilriker wilriker changed the title Part cooling fan speed not adjustable when not using Fan 0 Rework fan handling Oct 13, 2020
@mfs12 mfs12 mentioned this issue May 7, 2021
Open
@mfs12
Copy link
Contributor

mfs12 commented May 7, 2021 •
edited
Loading

After discussion with team this issue will be part of #101 and not implemented for the upcoming milestone.

@mfs12 mfs12 removed this from the 3.3.0 milestone May 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mfs12 @wilriker @PaulNokel @dc42 @smoki3