Windows 10, Ruida less than a year old connected via USB. Has been reliable for quite a while, successfully cut a job just before this issue happened…nothing has been changed between that job and the problem I have now.
UPDATE. Not sure that it means anything but I can save the file onto a USB stick and I can plug it into the laser just fine. Also, wondering what may be the BEST way to connect the laser to the PC? USB, Ethernet or WiFi and are other methods of connection likely to fix the issue?
Are you running more than one copy of LightBurn? Often when I see this it’s because someone launched another copy to work on their next design, then try to run from that one when the laser is done. Only the first running instance of LightBurn will talk to the laser.
Find My Laser doesn’t work if you’re already connected to it for the same reason.
Nope. Went through several boots of both the laser and the PC to no avail.
Right-clicking the devices button as Anthony suggested will reset the connection. It’s possible a Windows Update has done something to the driver, or you have USB sleep enabled.
Check these suggestions:
1 Like
I do have this problem from the beginning. What i do now is hit the “Device” buttom right click and direct after it click the start button. 96% of the time it will work. I try to find out what the problem is but i can’t find it. So, if someone find a solution is very welkom!
Johan
Thanks, running Windows 10 but will dig deeper in the morning. Not sure what I did but I’m back up and running again. Played with the move arrows in LB and the laser responded as it should. I will add that I did try this earlier without success…go figure!
I would try a different USB cable, and connect via Ethernet rather than USB.
Okay…back to square one. If I hit ESC or RESET on the Ruida keypad the PC will “see” the laser via Lightburn and I can move the laser gantry around with the LB MOVE commands but as soon as I try to send a cut job from LB I get the same old error message.
By all appearances the USB cable is fine, I’ve cut plenty of jobs with it including two just yesterday.
Weird. Looking at LCD window on the Ruida display: when I try to send a cut job the laser beeps to tell me there’s a problem and the display on the laser reads: “Frame slop. Work paused. Continue press ENTER. Cancel press ESC.” I’ve tried both and neither make any difference.
Frame slop means there is something in the drawing that is outside the working area of the laser. Check to make sure there are no stray objects in the outer edges of you LightBurn file.
1 Like
Thanks Anthony. New file, start from scratch…same result. Nothing out of frame.
Messed around trying different START POINTS. Cutting now but I have no idea how I got here.
If the laser is giving you an error, that would certainly do it. Also, pressing reset on the laser itself does drop the connection to the software. LightBurn should be smart enough to pick it up again, but I’ll double check that.
Regarding the frame slop issue, make sure you’re within bounds, and have the job origin set properly. If you don’t have a lot of experience with the job origin settings, this should help: https://github.com/LightBurnSoftware/Documentation/blob/master/CoordinatesOrigin.md#coordinates-and-job-origin
Thanks again Oz for your help. I’ll give that a read!
In my case there is no difference between USB and Ethernet connection. In both cases is the outcom the same.
my unit is a SH-G350. I have bypassed the cable to my controller and I still have this issue. I could use some help. I can select the device and I can frame but can’t send the data. I could before the thanksgiving break. UGGGGGGGGGAAAH
How long is the cable connecting the laser to your PC?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
The latest release of LightBurn has a user-configurable timeout value in the Device Settings. I’ve been playing with the AWC today, forcing it to drop packets, and I noticed that LaserCAD software never times out - it simply won’t give up, ever. If you unplug the network cable you actually have to force-kill the program.
LightBurn will let you set a network timeout up to 20 seconds (20000 ms) which should be long enough to give you gray hair if it actually fails for real. Try increasing that number to 10000 and see if it helps your case. It’s possible your controller is just doing some internal memory shuffling and taking longer than my default timeout.