Out of bounds due to overscan error

Apologies if this has been answered, but in all the similar topics I found the thread timed out without a solution or the provided solution did not work.


When I frame the project it goes to the correct space, but when I hit Start it gives me the overscan warning. If I hit continue the laser jogs off to the left and grinds against the side until I tell it to stop. One common answer I saw was that the speed might have the laser exceeding the workspace, but if I’m understand the preview correctly it looks like the laser is well within my work area? I’m very new to this stuff, so apologies if I’m missing something obvious.

I’m using absolute coordinates and home the laser to the rear left by having it start there when I power the machine on. I’ve tried adjusting speeds and disabling ‘Enable pointer offset’ in settings, but neither of those worked.

I am using an Xtool D1 10w with the extension kit along with Lightburn with the latest update.

Thanks for specifying your laser type. The controller in the D1 needs to be configured to be made aware of the longer Y-axis. For xTool machines this can only be done from XCS. Have you done this part yet?

Then on the LightBurn side, you need to make sure you’re using the lbdev file that your laser manufacturer has provided in their tutorial, but edit your working size: Operate xTool D1 Pro with LightBurn - xTool Support Center

2 Likes

You might just try moving the image up, so it’s within the default working area… that would be easy.

:smile_cat:

I’ve moved it all around the work area, doesn’t seem to change anything.

I will double check those things, but I should have also mentioned I’ve done other projects before. This is the first time I’m trying engraving/using images though. Other projects where I was just cutting lines have use the extended work area just fine.

Might do a ^A to select everything. Then you can see if there are fragments around that may be causing issues. Many times you will do some operation, read data from another piece of software and have residual very small items that you can’t see.

Use select all then the zoom to selection…

Since you’ve used this before on vectors, I don’t follow the problem either. The only difference being overscan, which should show up on your preview.

I’d expect more overscan running as fast as you are. 9350mm/m is the same as 368mm/s… can you actually run that fast? I’d expect much more overscan to reach that speed.

:smile_cat:

In Absolute Coordinates.
It seems you have an image set to output and not apparent in your design.

Thank you everyone for your suggestions so far.

I tried the suggestion of selecting everything and zooming to see if there were any small parts in the work area I was missing, but I couldn’t find anything.

The image is the Snoopy (Dog) on top of the words there. After messing with settings and changing the letters to offset fill I was able to get it to start, but eventually it started jogging into the left again. After toggling layers to try and restart it, with the letters on Offset Fill it seems that the Snoopy is the only thing left causing the issues.

I’m adding the lightburn file in case that will help anyone. Thanks again.

LBForum.lbrn2 (195.0 KB)

1 Like

Your file seems ok, test this one I traced Snoopy and now is vector.
LBForum_edited.lbrn2 (201.3 KB)

1 Like

What does it do if you run the file from XCS?

Haha, beat me to it. Mine cuts the speeds in half and runs in the same time (38 minutes Preview estimate0.

Retired Snoopy.lbrn2 (224.7 KB)