Ruida controller, "no enough extend space" error

I know there are already topics about this, but I don’t think the problem is well understood. I’m trying to engrave a large image on my BOSS 1420.

If I choose true grayscale, the software seems to want to send the entire file, and the laser throws the error as soon as transmission starts.

On the exact same file, it started to burn the job once, but then stopped after a few lines. Usually it doesn’t even start before the controller gives the error. At this point, you have to hit ESC on the controller.

Note that LB does not have any way to abort the transmission of the job, so you either must wait until it’s finished, or kill LB with taskmgr.

Here’s the thing: if I switch to a dithered method it works better, but evetually the controller gives the error. Exact same image in the exact same position.

So I don’t believe that this issue is strictly related to position and acceleration of the head. It feels more like local memory limitations on the Ruida to me.

Rather than try to understand the details on the Ruida, I’d suggest that a nice LB feature would allow the user to tile the image and etch it in sections. I could obviously do this in Photoshop and then import multiple images into separate LB layers, but seems like a very useful feature to make it easy in LB.

@HillBillyLabs. Welcome to our forum.

How large is your file? Is it an 8bit BW?



‘Not enough extend space’ is the controller telling you that the head is going to travel out of bounds when it overshoots the edge of the image to decelerate and change direction. It has nothing to do with the overall size of the image - it’s just that part of it is too close to the edge of the work area for the speed you are running it at. If you tiled it, but positioned it identically, you’d get the same error.

To fix the error you can:

  • Reduce the speed, which will reduce the amount of overscan required
  • Move the image inward, away from the edge of the machine
  • Increase the engraving acceleration, which will also reduce the overshoot, but may cause steppers to skip if it’s too high

The reason you get the error sooner in grayscale is that grayscale engraves all pixels, including the white, ignoring only transparent areas, where dithering only touches the dots, and skips white areas entirely.

1 Like

@LightBurn this is what made me think that the file size was suspect. It ran better in dithered .



As I said, I’m having trouble squaring this answer with my observations.

If it had to do with the position of the image and the movement of the tool, I would expect NO lines to be rendered. And I would expect it to make no difference when the laser was on. Instead I get some, and then an error. Which feels an awful lot more like buffer / memory.

There is exactly one thing that causes the “not enough extend space” error: when the system determines that the line to be drawn would go out of bounds during overscan.

When running a grayscale image, all non-transparent pixels are burned, and therefore the first line of the image is the same as any other if no transparency is present, and the first line would cause the error.

If the image is dithered, only black dots are burned, so if the image is narrower at the bottom, the processor might not know right away.

This is your issue.

Hrm. After much experimenting, I now believe it. It’s… weird.

As LB notes, it is indeed very cool, but hard to dial in.

I suspect quite a few people mess around with it for a while and then find some other thing to do.

You might edit the note to mention that speed leads to controller errors.

I am a big fan of informative notes sprinkled throughout software like this.

For the record, on my LS1420 I finally settled on 150mm/sec, which let me get within 10mm of the edge.

Awesome product, by the way. And thanks for patiently replying.

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