Just wondering if the choice to use absolute or incremental Gcode is user settable. I couldn’t find it if it does exist. (I’m using a Cohesion3D LaserBaord with Smoothieware.) I know from looking at the Gcode the particular job I’m doing, (a power scale test with a grid of filled boxes), does a G90 absolute mode move to the start position and then switches to G91 incremental to scan the lines. A reasonable choice but the problem I have is that very occasionally some kind of communication issue causes a single line to be lost. This will throw the rest of the job out by the length of that particular line, (if using the recommended buffer transfer mode). If this was running in absolute mode entirely then the missed line would cause an imperfection, but would likely be unnoticeable.
I’ve read a good explanation of LightBurn buffered vs synchronized transfer modes, and the Smoothieware and GRBL sites, but then the choice becomes speed vs reliability. I haven’t yet found an answer to what happens if LightBurn sends a line in synchronized mode but never receives an acknowledgement. In buffered mode it just runs to the end of the program and then remains Busy as it’s still waiting for the one missed acknowledgement. Switching to synchronized isn’t going to ensure that lines don’t drop but will handle them differently and it would be nice to know how.
EDIT: So it looks like G90/G91 moving to start is dependent on Start From being Absolute Coords or Current Position. I always use the latter. And the scanning is done using G91 regardless.