Jump to content
billplate

why is layer height omitted from per a model settings

Recommended Posts

Posted · why is layer height omitted from per a model settings

I'm glad that Cura now has per a model settings.  It is something it has lacked for a long time.

 

But i'm surprised to see we still can't have different layer heights (when printing one at a time) as this would surely be one of the most used setting.

dose any one know why its been omitted?

Share this post


Link to post
Share on other sites
Posted · why is layer height omitted from per a model settings

Cura has had per model settings for quite some time (since 2.1), but we've never supported multiple layer heights. This is an intentional "omission". Having multiple layer heights makes the slicing process orders of magnitude harder. It's doable if you only use magnitudes of a layer (eg; one object with 0.1 and the other with 0.2), but even that would require large parts of our architecture to be re-written and a load of extra features to be added.

Share this post


Link to post
Share on other sites
Posted (edited) · why is layer height omitted from per a model settings

Thanks for the reply nallath.

I'm not familiar with the structure of gcode so i only get jist of what your saying. 

Forgive me if this is a stupid question, but could problems u mention not be bypassed by treating the per-model-layer-height setting almost like separate prints in a queue? so it would effectively be loading  a new gcode for each object? A compound-gcode as it were :)

Edited by billplate

Share this post


Link to post
Share on other sites
Posted · why is layer height omitted from per a model settings

Well I suspect that is how it works, i.e. if you are printing 4 copies one at a time then there will be 4 copies of almost the same code, to print a copy, following each other except that the x/y axis positions will be different but the extrusion amount will be the same for each line of code. But apart from having to do work on the user interface, in the background you then have to deal with issue of different copies having different heights and avoiding collisions during printing etc.

Share this post


Link to post
Share on other sites
Posted (edited) · why is layer height omitted from per a model settings

@ yellowshark

what u describe is, as i understand it, how the slicer works, not the gcode,  which is simpler and dost have a  concept of objects or copies.

What I'm saying is, if having multiple layer heights is an issue for the printer.  

Crate a "compound_gcode" which contains multiple objects (each with their own gcode)  which automatically load in sequence, without resetting the nozzle position. Collisions wouldn't be an issue as it would be calculated the same way as a normal one-at-a-time print. the only difference is that each object is treated like a separate gcode before being packaged as this  "compound_gcode".

 

Edited by billplate

Share this post


Link to post
Share on other sites
Posted · why is layer height omitted from per a model settings

Note that layer height is available as a Per Model Setting if the Print Sequence is set to One at a Time.

Share this post


Link to post
Share on other sites
Posted · why is layer height omitted from per a model settings
30 minutes ago, ahoeben said:

Note that layer height is available as a Per Model Setting if the Print Sequence is set to One at a Time.

 

No its not!

And according to nallath, who sounds like he knows his stuff, it never has been available.

Share this post


Link to post
Share on other sites
Posted · why is layer height omitted from per a model settings

I stand corrected. I agree though that it should be possible in One at a Time printing to do this (and I also know my stuff).

Share this post


Link to post
Share on other sites
Posted · why is layer height omitted from per a model settings

Theoretically it could be possible to have layer height available if you're printing multiple models in one at a time, but we also have some legacy issues, which make some things harder to build than they actually should be. As we always have more features than we have people to build them, the stuff that isn't used that much tends to not get picked up.

 

Compounding the g-code is theoretically possible, but it does create quite a few issues with avoidance paths.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Ultimaker Cura 4.0 | Stable available!
      Ultimaker Cura 4.0 is mainly focused on the improved user interface and cloud integration.
      As always, we want to collect your user feedback for this release. If there are any improvements you can think of, feel free to mention it here and help us to shape the next release.
      • 98 replies
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!