Hi, Newbee to the community, I’ve been using LB now for almost a year and was on an older Macbook Pro (2015) using LB 1.7.08 with almost no issue, I installed 2.0.02 and lets just say a few of my cuts were wayyyy off. I reinstalled the older version and was working. I just updated my computer set up to a M4 MBP and thought it should be ok to install LB 2.0.02 and just ran a couple of test runs and well looks like the same thing is happening again. Please take a look at the pics, 1st is the file, 2nd is the actual cut, and 3rd is whats on the controller (similar to what was cut). Is it the controller? Any help would be amazing
A screenshot (not a cellphone picture, please) of the LightBurn Preview will help determine what LightBurn sent to the machine, which may differ from all of the above.
Just did another test and this is what I got, preview looks fine, print came out similar to first post (actually worst). I did run this print from my old set up to see if anything was going on and those prints came out fine.
That tells you there’s a communication problem between the PC and the laser controller, which typically happens due to USB dropouts.
Some previous discussions cover the problem & solution, in particular with Apple products:
What on the machines console displays is what was received, not necessarily what was sent.
I’d say it’s a communication issue. Can you implement a connection with the Ruida to your lan?
@ednisley @jkwilborn Thank you both! I connected via ethernet/lan and seems to be working fine now, I’ve only ran a couple cuts but seems to be doing what I want it to do
1 Like
I recon you are on the right track with USB/communication being the cause — that matches what others have suggested. These kinds of random “extra” lines usually aren’t from LightBurn itself, but from noise or dropouts between the PC and controller.
A few things you can try:
- Swap to a short, good-quality shielded USB cable (ideally with ferrite beads).
- Avoid USB hubs; connect directly to the PC.
- Plug laser and computer into the same outlet to reduce grounding noise.
- Keep the Console tab open during a job to watch for errors.
- If possible, test from another PC or OS to rule out a driver/host issue.
That should help narrow down whether it’s really communication or something mechanical.
If you haven’t already done so, make sure the laser’s IP address is not within the range the router hands out with DHCP to avoid having another device pop up with the same address.
The discussions I pointed to include some details, with more here:
An IP address collision will cause intermittent failures at some future date, long after you’ve forgotten what you did yesterday. 
Since it arrives at the Ruida, showing incorrect on the console and another send shows the correct version, I think it has to be a communication error of some type.
I think with these, USB is so crappy, that the best advice is to use Ethernet, even though it’s UDP and static.
Ruida might be good controllers, but they do not speak so well to other devices. I rarely get failures from Ethernet, but it does happen..
Normal TCP/IP Ethernet I would expect failed packets to be resent, too bad it’s UDP.
Just MHO.
1 Like
I’ll be frank, I rarely get errors via USB either. 
One thing you might try is clearing the controller’s stored files. In LightBurn, open the Files tab (right-side window), select any files listed there, and delete them. A full memory can sometimes cause odd behavior.
I don’t with the fiber, as a general rule. I also have no choice about how I talk to it.
The USB standard is great, differentiated signals take all kinds of interference without showing up on the integrated data side.
If this engineering was adhered too we wouldn’t have so many usb issues that are the cable… Somethings running at the edge of it’s design to cause this.
Have a Windows machine? Did you have to load drivers for the machine to operate.
Mac, state of the art, has to be forced to use the proper USB or it won’t talk.
USB is supposed to eliminate a need for the user to configure anything… however we see them pretty frequently having issues over things, such as baud rate.
USB is supposed to have same type connectors… if you buy all the things you want from the same computer manufacturer, maybe…
I have a wall of different types of connectors that are USB.
These are all benefits of the USB system.
How many communications issues does support deal with that are purely related to USB?
With a Ruida you can use USB or Ethernet.
I’d pick the one that the most dependable and the least work, that would be Ethernet, not USB. Even if it is UDP.