When to use the 'overscanning' option?

If you want to engrave you have the option to use ‘overscanning’. Frankly I don’t know what it is and therefore don’t know when to use it. So the obvious question is; what is overscanning and when to use it?
Thanks in advance!


From our documentation: :slight_smile:

When engraving, the head is scanning back and forth. Because the laser has to accelerate and decelerate the head at the beginning and end of each line, on machines with limited power control this can cause darker edges than expected.

Overscanning generates extra moves, past the ends of each line, switching the laser off before it fully stops, or even before it begins to decelerate, allowing the entirety of the engraving to happen at the desired head speed and then decelerating while the laser is not burning. The overscan number is a percentage of your cut speed - the default setting is 2.5%, meaning a cut at 100mm/sec will move an additional 2.5mm past the last cut with the laser off.

Note, Overscan is applied automatically by DSP hardware, like Ruida and Trocen controllers. This setting is only available for gcode based systems which do not do this automatically.


1 Like

Thank you very much @Rick , that’s helpful information (and documentation link).

1 Like

Can you turn off overscan on a ruida control?

1 Like

You can’t, though if you set the scan angle to a non-multiple of 90 degrees (1 to 89) it doesn’t use the hardware supported raster path. The results won’t be quite as good on the edges, but it won’t overscan either.

:+1: Will have a try the weekend

I think that on Ruida, it’s calculated from the acceleration parameters. At least for me, when I decreased acceleration (because of skipping), overscan increased.