2.5.3 release Changelog Question

42 views
Skip to first unread message

Ryan Hitcho

unread,
May 21, 2024, 11:29:13 AM5/21/24
to IceSL
First off, I am extatic that IceSL continues to develop! So thank you for this!!!
Certainly going to learn some python to see how pyicesl can expand capabilities.

In the changelog it is mentioned that the post-processing plugin gained a layer height and thickness setting. I did build the samplePostProcessingPlugin from your latest source.

Is there something I must do to expose these settings in the GUI?

Going to investigate further in the meantime.

Thank you!

Re-try WhenDown

unread,
May 22, 2024, 1:08:17 AM5/22/24
to IceSL
Hi Ryan. Thank you for your kind words. Allow me to clarify this entry in the changelog.

Layer thickness is already a base parameter in the UI. You can find it by the internal name ‘z_layer_height_mm’. This particular parameter can be set “per-layer”, which in the end means the layer thickness does not have to be constant. In other words, layer thickness varies throughout the geometry’s height; in some interval (say, the first 2cm of height) it’s one value and in the next interval is another and so on.

Now, the C++ interface for the post-processing plugin has a function (the most important one) that is called and executed on every layer. At this point, these layers represent deposition trajectories -unlike say, shape contours for infill plugins-. This is the last stage before these deposition trajectories are translated to machine code; which is GCode in this case.

This “important” function is now called with two extra parameters for the layer thickness and its height w.r.t. the building plate of the printer. With these parameters, the user (that is coding the plugin) can use this precise information.

Why were they added? When I was doing a post-processing plugin for an internal project here I found out that I could not correctly query the value of a per-layer setting for the currently post-processed layer when the layer thickness was itself set “per-layer” (i.e., different values across the height of the geometry). But now, with these changes, it is perfectly possible.

I hope this clarifies your comment. Let me know if there is need for more details.

Salim.


Le 21 mai 2024 à 17:29, Ryan Hitcho <ryan....@gmail.com> a écrit :

First off, I am extatic that IceSL continues to develop! So thank you for this!!!
--
You received this message because you are subscribed to the Google Groups "IceSL" group.
To unsubscribe from this group and stop receiving emails from it, send an email to icesl+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/icesl/2600735a-49b2-4d32-b788-19ad1270094en%40googlegroups.com.

Ryan Hitcho

unread,
May 22, 2024, 10:39:43 AM5/22/24
to IceSL
Thank you Salim. I appreciate the time you took to explain everything in detail! Going to work my way towards learning LUA and Python in an effort to utilize IceSL in a fuller capacity.
Reply all
Reply to author
Forward
0 new messages