and the configuration option page?
Yes, the Pi Bridge has been configured per the instructions on that section of the page.
If it’s up and your happy, I’ll cease and desist… and you can skip the rest 
Their docs say if you leave the laser set to it’s default ip then it should just connect. It claims it will provide a wifi access point… Do you see some wifi connection associated with lightburn?
There is something about that address you’re using that, well, looks bad… Not sure what, but…
As long as you’re going through the Ethernet of the laser. My Ruida controller shows when mine is on-line, I think it says ‘lan on’ or something on the bottom of the display.
If you want to try and change it, I’d would go back to ground zero (as far back as possible) and try the procedure again. They have had very few problems, considering what they are doing. I haven’t found mine yet, so I’m not much help, but I use Linux pretty much exclusively.
Hank: Incorrect. The Pi wired connection absolutely does not need to be the same subnet as your WIFI. They actually have to be different for it to work.
1 Like
I’ve never had an issue with getting the Pi to connect to the Bridge, and have not had to change the gateway mask either - I’m not even sure that’s used, as I’ve never touched that on any controller I’ve owned.
The connection between the Pi and the laser is completely independent of your local network, with the only caveat being that they must be on a different subnet. So, if by some chance your WIFI router is set to use 10.0.3.xx as your net, you’d need to change the bridge config to use a different subnet to connect to the laser, or the Pi will try to route the traffic through the WIFI instead of to the laser.
Something you can try - browse to the Pi on a browser - Since yours is 192.168.86.28, plug that into a browser and you should get a status dashboard telling you some simple info. There are logs you can check, just in case anything crashed or threw an exception.
I would try connecting a network cable directly to the Ethernet port on the Ruida controller itself, not just the plug in the case - sometimes those short extension cables are faulty, or not connected internally, so going straight to the controller is a good way to check. Also, try a different network cable from the Pi to the laser, just in case it happens to be bad.
1 Like
I am also having the issue of it connecting but says no laser connected. Was there a fix figured out in this topic?
A little confused - looks like you have a WiFi network called OMTech2. Is this the WiFi network that both your computer and the bridge is configured to connect to? Mostly the name is throwing me off, like it’s one of those Ruida WiFi relay devices (the ones that are just AP mode WiFi dongles).
Same message (No Laser Connected) as in picture at the top of thread, but probably completely different issue. I have a NEJE Master 2s, but no ethernet connection–only USB. So LB sees the bridge (on a RPi 4), at IP 192.168.7.234, but not the laser. Google and forums have vague references to this for NEJE, but I thought I had seen somewhere that LB Bridge on a Raspberry Pi 4 should allow a USB connection between the Pi and the laser. I (in my own simple brain) thought the Pi would translate the ethernet messages over to the USB path. Thoughts?
May have my own answer:
I’m guessing my problem is that the LB Bridge is really just for Ruida controllers? Not GRBL?
I know there is a layer of code in the pi to deal with the udp issue in Ethernet. I feel pretty confident it’s been tested with USB, but don’t know. Don’t remember anyone mentioning it…
Yes, I do remember, now that you reminded me… I try and forget usb…
No need guessing. 
The first sentence from our documentation on the LightBurn Bridge:
The LightBurn Bridge was created by LightBurn to get around some of the limitations of Ruida controllers. - LightBurn Bridge - LightBurn Software Documentation
Hi everyone! Sorry I disappeared for a bit — thank you all for your suggestions!
I have it working now! Thanks to @LightBurn for your in-depth response. You clarified that I was on the right track initially, setting the laser_ip field in bridge.json to 10.0.3.3 and setting the laser’s IP address to 10.0.3.3. Just for good measure, I also set the gateway address in the machine to my subnet (192.168.86.1).
What ended up being the fix was plugging the ethernet cable directly into the port on the controller, the external port’s adapter must not be connected/working on my fiancée’s machine.
Thanks again everyone, I hope this helps someone else as well!
1 Like
thanks for the gentle response. when I first set about trying to put this together, I thought I had done enough research that I believed that Ruida was not only a specific piece of hardware, but it also sounded like a comm standard of its own–and SOMEWHERE, I swear, I saw that the Bridge helped mimic that interface (I forget the term I mean–emulate, maybe?). Anyway, now I know. Learning curve is steeper than i thought! (for me, anyway). Cheers!
No worries, we appreciate the enthusiasm!
We would like to support more devices in the future and gcode controllers like yours are definitely on that list. But the original reason for this was to fix communication issues specifically between recent versions of Mac OS and Ruida controllers. So we started with that and are moving from there.
2 Likes
More like an overhang
1 Like
Hi Adam, i have just received my pi from lightburn tried to hook up and have no luck, maybe my lack of knowledge, changed up address on the controller to 10.0.3.3 connected Ethernet cable that came with the pi and it does not reconise controller, put back usb and that connects okay, any advice would be appreciated
Have you used ethernet on that machine before? Sometimes the external port is not actually connected. So that would be my first thing to check.
And I assume that you can connect to the bridge but you are getting the “No laser connected to bridge” message?
No have not connected by Ethernet,will try your suggestion tomorrow, thanks for the suggestion
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.