project (here’s just a part of it) I noticed that the laser started from the outside, I moved the line to another layer and it was solved.
But I had the urge to go and see what was going on, so in the original version if I change the priority of the shapes everything works as expected. I haven’t changed any settings. I’ve now tested it with Lightburn 1.7.00 and it’s still wrong.
Yes, there is a special test group for BSL/SeaCAD lasers (galvo lasers), particularly the Gweike G2 galvo. Some xTool S1 features are in early testing as well.
I selected the inner shapes first and the cutting started with the outer shapes, I just changed the priority and everything was fine.
This also happened with 1.4.05.
Following this topic, in my speed tests I went to test larger movements, with the same file I’ve been using for a few days, I duplicated the shapes and moved them to the end of the bed, and BAM the laser turned on, the layer had power. Undo repeated but I couldn’t replicate, a GLITCH? I think there must be a problem in cleaning values from memory, some stay resident, because when the operation is not as expected, closing and opening Lightburn everything is “normal”.
I still have to tinker with the options, but using a CUSTOM GCODE profile:
Changing the Fast Whitspace Scan values or turning them off doesn’t affect the (non-cut)speed.
Turning Return to Finish Position on doesn’t work, although if it’s on, if I set User End Script to a different position, it wraps up the movements.
The priorities were 0 (default?) then I changed top egg to 1 and bottom egg to 2.
Edit: I’ve looked at it now and it’s still not perfect, starting with the top egg Lightburn cut out the inner shapes and before finish go to the outer shapes and then back to the inside.
I posted the .lbrn2, alternately showing only the image or only the rectangles within the 80cm x 55 cm area, the image was produced by placing an image (image snip capturing text) next to it, duplicating the rectangles, moving them above the image, mask flatten deleting the first rectangles and moving the result produced to x=50 y=150, to have consistency in my tests.
Can you state the actual problem that you’re observing with images and what you’re trying to demonstrate? It’s not obvious based on what you’ve posted thus far.
A new machine, following this topic I’ve conducted a series of tests/configurations to optimize the speeds, but in the meantime I’ve noticed some problems, e.g. in the last case of images, it starts engraving outside the limits and ends within the limits. Is this to be expected?
I tried it in Win7, Lightburn already has the ALT toggle but in other applications it doesn’t, it must have become standard from Win10 and I missed that info.
