Unexplained Laser Stoppage During Cutting Process

[MisterOo (Pierre)]

I am encountering a strange behavior with my laser, which stops mid-cut without any error message.

Yesterday, while I was cutting, my laser stopped for no apparent reason in the middle of a design cut, again without any error message. The laser head (60W CO2) no longer moves or cuts, and it does not return to its initial position either.

I tried to restart the design several times, but it always stops at the same place, it seems (at first it was on another part of the design) . Strangely, 10 minutes earlier, I was making these same cuts without any problems.

If I remember correctly, I made a slight change in LightBurn where I added an extra layer to have a kerf in certain areas (but the cuts do not stop on these lines, but later on). Moreover, it’s not a particularly complex file as we only have 4 layers and it’s a cut that takes something like 1 minute…

I think the issue stems from the relationship between LightBurn managing the laser because if I upload the file via LightBurn to the laser and start the cut from it, there are no issues in the design cut.

I run LightBurn on my Mac, and I am using version 1.4.05. I have already performed several checks on the computer, the laser, and the USB cable, but nothing seems abnormal.

Tomorrow, I will try to start the cut while keeping the console open to see if any specific element displays, but I must say that for now, I am close to a dead end.

So, I have the workaround of working with file uploads, but it’s not ideal for my workflow. If you have any suggestions that could help me resolve this situation, I am all ears.

Thank you.

[jkwilborn (Jack Wilborn)]

@MisterOo

upload the file via LightBurn to the laser and start the cut from it, there are no issues in the design cut.

You didn’t mention if it’s USB or Ethernet, which can be important. If you load the file, like in your statement, it works fine. If you start the file, it will be streaming a majority of the data then attempt to execute the file. If your communications fail, the Ruida is waiting for more data that isn’t coming.

When the Ruida completes a job it beeps, since that’s not occurring, it indicates a communications failure while the Ruida is waiting for the rest of the file.

---

Suggest you dump USB, go Ethernet which is better and requires no specific drivers. Store the file on the Ruida and run it from the machines console. If you want to stick with USB, at least store the file on the Ruida and run it from the console.

There is no easy way to determine what happened if/when streaming fails.

Good luck

[woodango (Eric Mathews)]

I am experiencing the same issue running from a windows 11 laptop.