Setting the Fast Whitespace Scan
speed changes the speed of the G0
motions, which is necessary because Marlin does not follow the standard G-Code definition of G0
moving as fast as possible to the destination coordinates.
Perhaps you misunderstand how G-Code works.
By definition, each vector in the layout has a starting point and and an ending point.
In cases where the vectors are contiguous, you’ll find successive G1
commands, such as these along the first curved part of the layout:
G1 X264.207 Y54.008F300
G1 X265.415 Y54.051
G1 X266.621 Y54.124
G1 X267.825 Y54.226
G1 X269.026 Y54.357
Notice that those distances are very small, but that’s what the layout calls for.
However, if the vectors are not contiguous, then a G0
command moves from the end of one vector to the start of the next, with the laser turned off. For example, these are the straight-line moves at the start of the layout:
G0 X232.998 Y3.991 F4000
; Layer Schneiden
M106 S80
G1 Y53.992F300
M106 S0
G0 X232.998 Y53.992 F4000
M106 S80
G1 X262.999F300
M106 S0
G0 X262.999 Y53.992 F4000
M106 S80
G1 X264.207 Y54.008F300
The second G0
command appears to move to the same coordinate as the endpoint of the previous G1
command, which will produce no motion with the laser turned off.
You didn’t upload the *lbrn2
file producing that G-Code, so I can’t verify this, but I think you’ll find those straight-line segments are not joined, so LightBurn must consider them to be separate segments that require intervening G0
positioning commands.
If you apply Edit → Auto-join selected shapes
and perhaps Edit → Close selected paths with tolerance
, that may align the vectors properly.
However, none of that matters, because zero-distance G0
commands turn the laser off, so they cannot burn the material.
Have you run a Material Test
to verify the speeds and powers you are using?