Although we can control the fan speed manually with the slider, there is no feedback to show what the current speed actually is.
If the Gcode changes the fan speed - the slider does not change, nor is there any indication anywhere else I can find.
Percentage numbers for the current fan speed would also be really nice.
Re: Fan speed feedback
The slider does not show where the fan speed is because that is an override for what is in your process setting. There could be a display that would show the current setting of the M106 command but if your looking for active feedback like on a pc cpu fan etc then you need 3 wire fans. The 3rd wire is an rpm feedback signal that can be read.
Re: Fan speed feedback
All I'm looking for is a display of the fan speed set by the program. Either the slider, or Gcode - in percent. In many cases all I want to know is if it's on or not. Right now it's impossible to tell without looking - and on some machines the layer cooling fan isn't easily visible.
Next to the slider would actually be a convenient place to put the display.
If the Gcode changed the fan speed, then the slider would also move in addition to the display changing. The manual override slider would still function normally if you moved it with the mouse.
It would also be nice to have an override checkbox that would allow ignoring Gcode changes in the fan speed. This would prevent the user from having to fight the Gcode settings every time the fan speed changed if they decided they wanted manual control for an extended period of time.
This is important because the operator might sometime want to make a change in fan speed in a specific section of the part that the slicer hasn't generated a change for.
Next to the slider would actually be a convenient place to put the display.
If the Gcode changed the fan speed, then the slider would also move in addition to the display changing. The manual override slider would still function normally if you moved it with the mouse.
It would also be nice to have an override checkbox that would allow ignoring Gcode changes in the fan speed. This would prevent the user from having to fight the Gcode settings every time the fan speed changed if they decided they wanted manual control for an extended period of time.
This is important because the operator might sometime want to make a change in fan speed in a specific section of the part that the slicer hasn't generated a change for.
Re: Fan speed feedback
3.0 now has basic fan speed feedback. That's a step in the right direction - thank you!
As in the previous suggestion, a percentage value indication would still be nice.
More importantly, a way to temporarily override G-code changes would be very helpful. If the override button were selected, any M106 commands would be ignored (except for any that might be present in the ending script). The fan would remain at the speed that the user set it at.
The way it is now, I can increase the fan speed in the middle of a print, but the G-code can keep changing it back with every new layer. Fighting the program this way in certain critical areas of the print is not fun. It currently not possible, or at least not easy , to get the program to generate fan speed G-code for fan speed changes in many areas where it is needed/desired.
I'd suggest a more sophisticated way to define fan speed changes is needed. Overhangs, bridges, and small island layers all need to be detected and extra cooling be made available with some level of control.
The additional coloring displays for various features in the preview display is very good.... How about adding one for fan speed ?
As in the previous suggestion, a percentage value indication would still be nice.
More importantly, a way to temporarily override G-code changes would be very helpful. If the override button were selected, any M106 commands would be ignored (except for any that might be present in the ending script). The fan would remain at the speed that the user set it at.
The way it is now, I can increase the fan speed in the middle of a print, but the G-code can keep changing it back with every new layer. Fighting the program this way in certain critical areas of the print is not fun. It currently not possible, or at least not easy , to get the program to generate fan speed G-code for fan speed changes in many areas where it is needed/desired.
I'd suggest a more sophisticated way to define fan speed changes is needed. Overhangs, bridges, and small island layers all need to be detected and extra cooling be made available with some level of control.
The additional coloring displays for various features in the preview display is very good.... How about adding one for fan speed ?
