Hello,
I have a question.
Why does Lightburn create such confusing programs or such a strange processing of layers?
If everything was processed properly one after the other, it would save time.
Is there a way to set this somewhere?
I haven’t found anything yet.
Thanks
Greetings Jan
You have some control using the Optimizations Settings button in the Laser window. [1] It still seems to do some random sequences when running. [2] It is pretty amazing that it can figure out all those moves at all.
Hello,
I have already made a few attempts with this, unfortunately without any significant success.
The confusing processing is only internal to the layer (in my case orange).
If there are several layers, then they are processed one after the other.
But each layer then shows such confusing processing.
Thanks
If you want it to do things in a very specific order, you can order by priority and set the priority of each selection in the shape properties window. This gives you very granular control.
If you undertake this manual optimization, I’d be most interested in hearing how much time it saved.
Because rapid motions (with the laser off) travel an order of magnitude (or more) faster than cutting motions, the time savings probably aren’t as large as they may appear.
For example, this layered paper job takes eight minutes:
The red lines show the rapid moves require two minutes, a third of the six minutes of actual cutting. Many of those moves are required, so there’s not much room for optimization.
Engraving all the layers as a single pattern takes three minutes total, with the rapid moves occupying only 30 seconds:
Cutting paper with a CO₂ laser runs nearly as fast as the rapid motions between cuts, so the results on a diode laser will be even more skewed toward cutting.
Your layout is even more complex, so I’d expect the rapid moves to occupy a small fraction of the cutting time. What does the Preview for that layout indicate?
If you haven’t updated the simulation parameters to match your machine, doing so will improve the estimate accuracy.
IMO, while improving the path planning would definitely reduce the overall time, it might not have enough payback to justify the programming effort compared to fixing more pressing problems.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
