Please help
I have a Thunder Bolt Laser with a Ruida RDC6442G controller and a i7 windows 10 desktop. I have hard wired the laser to my network and set a static ip of 192.168.1.50. In Lightburn I have setup device and states READY. When I try to send a file it fails but i can move the laser head from my pc. When I Ping IP only laser has this address. Have tried same setting in RDWorks and all works ok. Am I missing a setting in Lightburn.
Many Thanks Steve
Have you cleared out all the old files stored in the controller’s flash memory? Ruida controllers descend into chaos when they get stuffed, so giving them some elbow room is a good first step.
To verify: you did the ping test with the laser turned off, right?
Hi
I have only had the laser 3 days, all works fine with a USB connection.
I have cleared memory on laser.
The laser is unreachable when turned off, so only device on that ip.
It does display ready and the laser is at the bottom of the page in Lightburn.
when you send a file it displays file transfer failed, then Busy or paused.
All works fine in RDWorks on network.
Makes my think i have a setting wrong in Lightburn.
Many Thanks
Steve
The Ruida has a static IP, so you need to tell your router not to give that IP to another device. This is what @ednisley was inquiring about. If the IP is being given to another device, Lightburn wouldn’t connect, so you might want to review how this is working.
Sometimes referred to as bind(ing) an IP to a Mac address… If you haven’t done this with your router, it’s likely the issue.
Ethernet is the best mode of communicating there is with these as there are no drivers or other pieces of software that can interfere with the transfer.
If it’s failing during a transmission of a complete file, I’d be looking at the Ethernet connection.
I’d fall back to @ednisley suggestion and ensure you have your router DHCP configured to allow only the lasers IP to be handled by the router based on the Mac address of the Ruida.
Good luck
AFAICT, LightBurn doesn’t have many network-specific settings: tell it you have a Ruida controller, fill in the IP address, and it’s good to go.
You’ve probably read through the doc:
Other folks have found the Ruida controller must be on the same Class C subnet as the PC, which is always the case except for big setups with hundreds of devices spread across multiple subnets. In your case, both the Ruida and your PC must have addresses like 192.168.1.x, because the Ruida won’t recognize traffic from a PC at 192.168.2.5.
You can plug the network cable directly into the controller, rather than into the jumper from the side panel to the controller, just to eliminate one possible problem. That shouldn’t affect anything, of course, but is worth trying.
I have nothing else to suggest, apart from previous discussions of Ruida network ills with various resolutions (or lack thereof):
https://forum.lightburnsoftware.com/search?q=ruida%20network
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.