Hi!
I’m investigating the possibilities of LB before purchasing the license and I’ve a question on the automated Test Material which is very handy and convenient.
it is said here:
I really wish it could travel this way so I can stop before burning
The only difference in your images is the order of when your blocks get burned. Your diagonal build only does more unburned ones first… You do not have to use minimum speed of your laser or maximum power. In fact, you should ballpark the ranges instead of going 0 to 100% of everything.
Also be aware those tiny squares may not be translated into your project, unless you are doing tiny burns or cutouts. I often use fewer squares 25mm on a side, or even rectangles. The Material Test tool is adjustable for your benefit.
You can build your own test grid that will give you control over which shape burns in which order using the shape properties dialog and cut order priority settings. Like this.
Yes if I don’t stop it manually before the end (on visual clues), it would do no differences, I agree.
But what I like is to stop the material test when I see it’s becoming to hot. (because I’m not a arsonist and don’t like the prospect of fire or lens cleaning appealing )
At the moment, I’m launching several material tests by upping the limits successively. That’s time consuming and that’s different for each material. So a really progressive test would be handy.
I just made these 2 videos after seeing your thread. They are not posted publicly yet, but you can watch them. The first one shows how to make the test grid with your choice of graphic, the second one shows how to use it in your situation.
This is a great idea - we made the change to the material test to go cold > hot to try and make the tool safer, and this is a good next possible step there. I’ve bumped the idea in our internal chats Thanks for submitting it!
100% power at 10000 mm/min “deposits” the same amount of heat as 50% power going 5000 mm/min, or 25% power going 2500 mm/min, so it’s not just a zig-zag, it actually fans out in a non-linear way, like this:
To support this, I’ve had to add code to compute the “heat” amount for a cut layer, and even that has limits - If you do a Multi-layer, for example, I’m ignoring all but the first sub-layer. There would be no meaningful way to compare Line + Fill layers with different power settings.
Heat is computed from power, speed, interval, and pass count. Higher speed or a larger interval gives you less heat. Higher power or pass count gives you more heat. I’m ignoring frequency and Q-pulse (for galvos) mostly because those are non-linear, and hardware dependent.