search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.13k stars 2.07k forks source link

FeedRate Limits - Suggestion. #3186

Closed Thisismydigitalself closed 1 year ago

Thisismydigitalself commented 6 years ago

I really like this FeedRate color map. Typo or slicing algorithm can lead to a higher speed one's printer/filament can handle. ask me how I know. It would be nice if this very nice feedrate color spectrum map be more like an audio VU meter where 0 DB is top level and higher than that will be clearly marked as /red/clipping/checkerboard/etc/ so it will be obvious that somewhere along the print top speed was exceeded. these days you can get to higher than 100mms which will stretch the color map accordingly. this does not give us a clear indication about possible issues along the print.

Just for reference - should follow Cura's current color scheme. 674523

A penny for your thoughts.

jackha commented 6 years ago

Thanks for your idea, nice VU meters ^^. However, we don't really know the actual top speed while 0 dB is a hard limit. Also high speeds are mostly not actually reached and that's influenced by acceleration.

Thisismydigitalself commented 6 years ago

"Speed" was a bad choice of term on my behalf - I meant Frequency. I wish for this meter to show me when and where my nozzle will vibrate most violently, e.g. where speed is confined to very short distances.

Ghostkeeper commented 6 years ago

Detecting vibrations occurring is quite hard though. It basically requires us to simulate the hardware. Doesn't it? The vibrations will be vastly different for every printer.

Thisismydigitalself commented 6 years ago

True and yet a unit-less color map showing the longest to shortest line's travel weighted time (red would be the shortest / HiFreq) should give us an idea of what will be going on. more often than not i see my printer's head, during action, moving violently while printing a small hole or trying to build a bridge support, etc.

Ghostkeeper commented 6 years ago

We could visualise the expected acceleration magnitude in a vertex. That would come close, right?

Ghostkeeper commented 6 years ago

Our project manager removed this from our planning. It has no priority now. Maybe we'll get back to it some time but that will take a while.

github-actions[bot] commented 1 year ago

Hi 👋, We are cleaning our list of issues to improve our focus. This feature request seems to be older than a year, which is at least three major Cura releases ago. It also received the label Deferred indicating that we did not have time to work on it back then and haven't found time to work on it since.

If this is still something that you think can improve how you and others use Cura, can you please leave a comment? We will have a fresh set of eyes to look at it.

If it has been resolved or don't need it to be improved anymore, you don't have to do anything, and this issue will be automatically closed in 14 days.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 14 days since being marked as stale. If you encounter this issue and still have a need for this, you are welcome to make a fresh new issue with an updated description.