Some of your statements I have questions about.
Do you change the IP on the Ruida to 10.0.3.3?
Do you just plug this into your Ethernet plug directly into your computer and it works?
You don’t need the PI Bridge, it just has code to assist in talking to the Ruida, but I did run and have run with only a wireless bridge from Amazon. So it should work.
Does the Ruida show you are connected, at least hardware wise?
Yes the Ruida IP is set to 10.0.3.3
Yes if I plug my laptop directly to the laser via Ethernet cable then lightburn works.
I’m not sure how to tell if the Ruida knows it’s connected when using the lightburn bridge. The Ethernet lights are on.
I’m using the lightburn bridge so I can connect to the laser over my home network wirelessly. Are you saying you used a different kind of bridge or access point off of Amazon and it worked? If so what kind?
Ethernet is a standard communication medium. So you don’t have to have a PI, but there is software to handle the UDP that the Ruida speaks. UDP is a pretty primitive mechanism.
I have had both of my PI destroyed by weather, I’m back to my Amazon TP-Link wireless router or bridge.
You issue appears to be with the link between the PI and your laser. If the console shows a link, it should be connected, at least via the hardware.
It’s been a while since I messed with a PI, when the price for them skyrocketed I stopped buying them… Ended up back using my wireless router.
Is your home machine on a 10.0.3.x domain?
I had to set the router to give my wireless bridge a static address. This is based on the wireless bridges MAC address. That way it doesn’t change when something is added or you have a partial power failure.
What is the signal level of your home wifi like where the Pi is?
This example shows that a weak wifi signal at the pi might affect the relay, maybe this is why you also had no luck with the Vonets?
Use your phone to check the wifi strength … if you place your phone near where the bridge is? Is it a 2.4GHZ network? (might work better).
He appears to be seeing the PI on his network. I think the PI is working and the issue is at or after the PI.
His logs seem to indicate it’s working, along with a connection to his laser.
Are you setting Lightbun device to the bridge or the lasers IP? If I recall I set it to the bridge IP, which I set to static or it would change.
Thank you for the responses. My home network is a 192.168.0.xxx type, my laser is set to 10.0.0.3 per the guide on the lightburn bridge setup. I am going to try a accesspoint/bridge i purchased off amazon and see if i get a different result, i do think the issue is between the lightburn bridge and the laser, thought still not sure what one is the problem. I will report back once i try a different bridge. I was using the Lightburn Bridge Setup wizard to add the device and never made it past the part where it scanned for the laser and only found the bridge with no laser device. I tried the device i setup for hardwired ethernet connect just for fun but it couldn’t connect either.
If you plugged it into your PC then it likely won’t connect. Besides them existing in different domains. They have a protocol that’s expected. A Ruida has a static address.
I have directly connected my Linux box to the Ruida via Ethernet. I got away with it because I set up one of my Ethernet ports for the Ruida domain.
I used the PI configuration a number of times had one hic-up between the two, but it worked correctly.
If you have a wireless router, I set mine up to be a bridge… but my Ruida is set for a local address, I’m not really using it in bridge mode that I know of.
Good luck
Is this a typo? This should be 10.0.3.3 for default configuration.
Also, in reviewing the screenshots for the bridge logs. It looks like your latest configuration is timing out whereas your previous log shows a connection.
Can you open a browser and point to Bridge IP that’s on the local network? That should show a dashboard. Can you take a screenshot of that?
Yes that is a typo, it was set to 10.0.3.3. As far as the bridge logs go idk, i never had a successful connection in lightburn. Ill set the bridge back up and connect to the dashboard and take a snap.
I ran a test today to see if I could get a laser timeout error in my bridge relay log as some kind of a downstream-knock-on effect from having a weak wifi network but it seemed to be impossible to do even with a very poor connection (signal -87dBM and SNR 9dB), so please ignore the troubleshooting suggestion I made in post#24 - it was a long shot, and I’ve concluded there must have been other factors involved in resolution of the referred topic which will have to remain a mystery.
So I still have yet to get the lightburn bridge raspberry pi to work. However I may now have the built in Vonets bridge working. I had to reset and make some changes to the vonets but I may have that device working, need to test.
The Raspberry is a bridge between 2 networks, your 192.168.0.0 network and the 10.0.30. network. Log into the Pi and at the command prompt type in “ping 10.0.3.3”. The ping should return “Reply from 10.0.3.3: bytes=32 time=1ms TTL=64” If this works the then there is no networking issue and the problem is probably with Lightburn. If on the other hand you get aa destination unreachable message then there is a problem with the Pi of the laser. This should at least get you trouble shooting in the right direction.
Wanted to give an update. I never was able to get Lightburn Bridge to work, I have a feeling it was an incompatibility with my laser controller and the bridge/lightburn software. I was however able to turn that same raspberry pi into a virtual USB hub and connect to the laser over the network. The advange of this is I can also use the camera, though when thats connected lightburn is a bit lagggy. For anyone interested here is what I did. Hardware | VirtualHere
This doesn’t sit well. I don’t see how the Bridge wouldn’t work when LB works directly. Also, we have the data point of the other OneLaser user getting it to work. It still seems most likely that something else is going on.
Had you tried anything not already documented in this Topic or since the last update?
I have tried everything posted in this topic and many other things. While I don’t know exactly why it isn’t working, that was my conclusion. And though I’m not saying the other onelaser user didn’t get it working, I would love to see a video of it working. Either way I have already spent too much time trying to get it working and moved on to something that so far is.
I feel the same.
I was thinking I probably should have asked Brett to generate some more traffic for the bridge prior to asking for the relay logs, since there is that single entry which does appear to show the connection working:
Traffic can be forced by clicking the ‘Get Position’ button (Move Window) a few times…or better…for instant feedback - using ‘Position Laser:’ 
