Jump to content
Ultimaker Community of 3D Printing Experts
  • Sign Up
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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • Talking additive | The 3D printing podcast
      Why should we be the only ones asking questions? Join us and ask Jabil all your questions on September 22nd 5pm CET
        • Like
      • 2 replies
    • Ultimaker masterclass: Optimizing your Ultimaker Cura workflow
      Save your seat for either broadcast on September 23.
      What will you learn?
      · Best practices for iterative print preparation and every lesson you should learn from each print
      · The right way to use per-object settings and when they are most useful
      · Easy-to-use resources for anyone who wants to develop their own printer definitions, plugins, or print profiles
      · How to optimize print profile settings and whether to “keep” or “discard” changes
      · When is the right time to export your drawing from CAD? (Based on Ultimaker Cura’s surprising power as 3D control software)
      · And a whole lot more tips and tricks!
       
      How can I join?
      This free masterclass will take place twice:
      1. 11am CEST (5pm SGT, 5am EDT)
      2. 5pm CEST (11am EDT, 8am PDT, 11pm SGT)
        • Like
      • 0 replies
    • Do you use 3D printing at work? Let us know
      It doesn't matter if you are using 1 Ultimaker or 10, there is inspiration in everything. We're looking for ...
      • 1 reply
×
×
  • Create New...