From 'frame slop' to 'not enough extend space'

Ruida 644XX, K40

Messing around trying to learn some more. Working on etching an empty bourbon bottle (Benchmark, same bottle as JD, flat sides so no roller needed). Came up with a faux name and logo, etc. Drew up my graphics, put some settings I thought might work (start somewhere anyway). Working space of about 45mm wide and 110 mm tall. Placed the bottle in…got a ‘frame slop’ error. Okay…so, I decided to move everything a little further out into the workspace, start from current position… got "not enough extend space’ error.
Took bottle out, got a piece of wood, selected one or two of the graphics. Worked fine. Added another graphic. Worked fine. After that, error.
I’ve used guides to help align the work (T1 layer). Are they interfering, even if I shut them off?
(image shows after I’d moved the graphics back to upper left ‘home’)

I don’t understand how this is happening… the ‘label’ area is certainly not even close to exceeding limits of work bed. What am I doing wrong?

Welcome to the site :tada:

Any tool layer is only for the users use, so that’s not an issue.

You can do alignment without lines

Reference lines, the kind of thing many of us are used to with cad/cam software. Generally are not needed here.


I suggest using preview to see if the head is doing what you think it should be doing
Might try moving your head away from the corner, like 20x20 and pressing origin on the Ruida controller… Change the start from value to user origin. The graphic should start at the set user origin.


Generally what causes these errors is you are attempting to drive the machine out of it’s working area.

You can see the green box on your preview if you back (zoom) out enough. Enable show transversal moves and the head movement (no lasing) will show up on the screen as a red trace.

Check your Ruida to see what kind of acceleration value you’re using for each axes. That could cause an issue.

This value is in the edit → machine settings → vendor settings for each axes.

We’ll be waiting … on the edge of our seats :face_with_spiral_eyes:

:smiley_cat:

Reference lines, the kind of thing many of us are used to with cad/cam software. Generally are not needed here

I’m accustomed to it in Photoshop/Illustrator. One of the things for me is, I’m trying to get more of a fix on where ‘home’ is (user origin or no), in relation to the laser, and the table…so stuff doesn’t get offset and off to the right or left.


I suggest using preview to see if the head is doing what you think it should be doing
Might try moving your head away from the corner, like 20x20 and pressing origin on the Ruida controller… Change the start from value to user origin. The graphic should start at the set user origin.

See above. I tried that. Except the Preview part. I do forget it’s there.


Generally what causes these errors is you are attempting to drive the machine out of it’s working area.

I’ve read that before, but that’s not the case, here.

You can see the green box on your preview if you back (zoom) out enough. Enable show transversal moves and the head movement (no lasing) will show up on the screen as a red trace.

Will investigate.

Check your Ruida to see what kind of acceleration value you’re using for each axes. That could cause an issue.

Good to know. Yet another variable! Yay.

Here’s what I’m seeing…




Did you load the values in the device settings → additional settings? I think that’s where it’s at. This is where Lightburn gets the values it uses to emulate.

Ensure you do a read so it updates.

How many files do you have on the Ruida?

Some of your axes are set to a pretty low value, such as Y acceleration value of 200mm/s^2.

:smiley_cat:

I’ve gotten it to do something although I’m not sure what I did in order for that to happen. I managed to get it to etch the whole file; it’s not aligned right and it doesn’t look great, but that’s better than a) giving me an error, and b) starting to do the file then suddenly stopping for no apparent reason, early on in the etching.

Can you supply us with the .lbrn2 file and photos of the results?

:smiley_cat:

Bourbon bottle test.lbrn2 (66.3 KB)

The photos are a tad harder to get, as they’re on clear glass. I got one; it revealed an issue that I thought I’d already addressed, that of ‘minimum power’.


I discovered a YouTube video covering that very topic, day before yesterday, and set about making sure I had power settings such that it would avoid the line gaps, seen above. It did fine on wood… glass, not so much.
I’ll try to get a couple more shots of the bottle, here, shortly.

If you use line as the mode, then the Ruida will use minimum power on the corners.

Only image or fill ignores the minimum… Since it’s scanning, the overscan is handled and no minimum is needed.

I’m thinking back that you have two layers that are done in line mode. This may be why you see it here.

:smiley_cat:

From the video I watched I figured that. I suspect though that I’m going to have to increase the minimum power, when working on glass. I’d really like to have lines on some designs, and not have everything filled in. The font pictured, for example, is something that I just chose out of the blue but the longer I look at it the more I like it.
So it’s correct to approach ‘minimum power’ as something that will differ, depending upon material used…?

So, asking again… what values would you recommend? Other than time-saving (I suppose), are there larger benefits to having faster acceleration times on axes?

Oh, and I meant to mention… I know you said the tool layer wouldn’t have any effect on the functionality, but I did have a moment where when I turned it on, I got “extend” message and when I turned it off, I got “slop” message.

How fast they can actually be accelerated and to what speed is dependent on the machine. Most of these you can keep increasing the acceleration until it starts to miss steps.

Here are some of my values. I wouldn’t use any of the specific acceleration values for X and the ones for Y might be a bit high also.



If you have any questions, ask…

Make sure you have your firmware backed up. You can do that in the machine settings using save to file. Keep it around as a backup and make sure you don’t overwrite them. I keep a few of them with different information.

:smiley_cat: