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

Speed is in wrong units (travel in mm/s instead of extruded volume of cubic millimeters per second) - hot-ends can only melt so much - melt capability should determine travel speed instead of hard-coding some guess in mm/s. #10894

Closed
gitcnd opened this issue Nov 21, 2021 · 1 comment
Labels
Status: Duplicate Duplicate of another issue. Type: New Feature Adding some entirely new functionality.

Comments

@gitcnd
Copy link

gitcnd commented Nov 21, 2021

Is your feature request related to a problem?

All the speed settings need to be laboriously fixed when the nozzle size or filament chemistry is changed... this makes no sense... my hot-end can only melt so much filament, irrespective of the nozzle size, is the same amount.

Cura should know this, and work out it's own speed to suit.

mm/s makes no sense when missing the context of how much plastic is being melted.

Describe the solution you'd like

Split all speed inputs so we can provide our flow-rate (and perhaps an optional max-speed-not-to-exceed) - ideally, some kind of printer hot-end setting combined with the selected filament would be ideal - so Cura re-computes all the speeds properly and automatically when we change either of those.

Describe alternatives you've considered

Laboriously re-test everythign every time I change nozzles or fillament

Affected users and/or printers

Everyone

Additional information & file uploads

No response

@gitcnd gitcnd added the Type: New Feature Adding some entirely new functionality. label Nov 21, 2021
@gitcnd gitcnd changed the title Speed is in wrong units (travel in mm/s instead of extruded volume of cubic millimeters per second) - hot-ends can only melt so much - this should determine travel speed instead of hard-coding it. Speed is in wrong units (travel in mm/s instead of extruded volume of cubic millimeters per second) - hot-ends can only melt so much - melt capability should determine travel speed instead of hard-coding some guess in mm/s. Nov 21, 2021
@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented Nov 29, 2021

Duplicate of #5248.

Aside from a volumetric rate limit, you'd still need a velocity limit (X/Y/Z) because the printer is not just limited by how much it can extrude, but also by the processing speed, motor capability and the stiffness of the frame. Going too fast would cause vibrations resulting in ringing in the print, and cause buffer underruns in the motion planner. It's also what most users are used to; it's easier to visualise for novices and thus easier to adjust for them.

That thread discusses the integration of both of them, indeed pretty much for the reasons you describe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate Duplicate of another issue. Type: New Feature Adding some entirely new functionality.
Projects
None yet
Development

No branches or pull requests

2 participants