Interesting issue.
Omtech Red and Black with Ruida controller. Connected to a wired network.
On my windows 10 system running a registered version lightburn 1.0.04 I get this error.
"There was a problem sending data to the Laser, The machine may be busy or paused"
On my other windows 10 system running a trial copy of lightburn V 1.0.04 the same file is sent to the laser and runs correctly.
The lightburn settings on both computers are identical. Device time out is the same on both.
Could this be a windows networking issue? Where do I start??
The Ruida is not the most consistent with communications. It has to be in an idle state for it to receive anything.
If you sitting in a menu on the control panel it won’t load or communicate. If you can move the head around with the console, it should receive. Mine works great, but now and then it fails to get the data to the machine. Is this a consistent failure? I.E. will nothing load from that computer?
Had that problem happen just this week.
I found I was not set up correctly in the table size and was starting from current position.
The machine thought I was out of bounds I think and would not start.
It gave me the same mess sage.
Home your machine.
Watch the move panel to make sure it says you are home.
Then move to where you want to start.
Set origins and go for it.
I often use the center position for a start position.
If you are doing that change to upper left and see if it starts OK that way.
This week I have set up the lightburn bridge. Once again it works flawless with one computer. But the other computer nothing but errors. However when connected to the problematic computer and I get the dreaded error sending message, I found if I clocked the home button and reposition the head I can start the job.
This has to be a Windows 10 Network issue. Just don’t know where to start
I have this same issue when I send a design to the laser. I’m running Windows 11, same LB version, OMTech Red and Black 60Watt. Sometimes I have to send the design up to 3 times for it to actually send, but inevitably, there is something running on the controller and I either need to wait for it to finish or I just need to exit out of it. Rarely I’ll have to reset the controller.
I am running a Ruida6442 on Win10 with a wired USB from computer to laser and I found the quickest and easiest for me was to first make sure there was nothing running on the controller (sometimes there was a paused job) but if nothing wrong there, just disconnected and reconnected the computer(laptop) USB cord and the problem went away every time. I’ve never managed to figure out what it is that causes that - but it’s not very frequent so I just live with it!
