X Slop Over Error

LightBurn Hardware Compatibility Ruida controllers
,
1

I recently discovered Lightburn has an image trace option and decided to start testing it out with the purpose of building maps based on road networks. I had previously been using Illustrator for this task but I dislike their image trace tool and find Lightburn’s to run more smoothly, accurately, and much more quickly.

The issue I’m encountering is that once I attempt to trace the image area before cutting, I get an X or Y slope over error. I’ve been trying to troubleshoot the issue since it has happened repeatedly in over 10 attempts but never once happened before when using Illustrator files that used the Image Trace Tool. I have a 20x28" bed and am cutting on 12x12" wood with the origin of the laser, Omtech MF2028-100W, set to the middle of the bed. Once I frame the file it is showing the boundaries to be MUCH larger than the actual file, at least 18" on each side, and naturally going out of bounds on either X/Y axis.

I’ve been troubleshooting this for days and I can’t determine if this is user error, Lightburn, a random setting I overlooked/changed, or a controller error. I had successfully cut multiple maps using the image trace tool on Illustrator without this issue happening and once I switched to using Lightburn’s Image Trace tool, I start getting the X or Y Slope Over error repeatedly. Last night I attempted to cut one of the files, traced the area and it appeared normal! I didn’t have time to cut at that time, came back a few hours later and THEN it throws the error message. Why would the SAME file with zero tweaks appear to work correctly and then not with no settings changed?

I’ll upload the most recent test file and supply any additional info or screenshots if requested. Thank you for some guidance in advance.

MRW02.rd (359.2 KB)

Edit: After multiple subsequent tests since posting, any image trace file created in Lightburn seems to be the culprit of my X,Y bounding errors.

2

The RD file is considerably less informative than the LightBurn lbrn2 file that produced it, as we can’t see the various LightBurn settings.

With a big CO₂ laser, using Absolute Coordinates will save you a considerable amount of hassle, because the screen layout exactly matches the physical layout.

Set that, put the pattern in the middle, and see if the situation improves.

1 Like
3

I just edited a couple test files to Absolute Coordinates, which I hadn’t actually used so far, and the files are now framing correctly! I knew there had to be a setting that could fix the issue. Thanks for saving the day!

This was only happening from Image Traced files generated in Lightburn. Possibly a bug? I still find it weird identical files were framing out of bounds.

4

Ruida controllers manage the origin internally, so unless you’re very carefully positioning the laser head before pressing the Origin button on the machine display, with all that synchronized with LightBurn’s User Origin green pip, the origin used by the controller is most likely not where you think the origin is.

Reviewing the doc may help:

But, IMO, just using Absolute Coordinates and slapping the material down where it obviously should go eliminates a whole bunch of futzing around that sometimes ends with heartache & confusion.

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.