If you have a laptop with an ethernet port turn the laptop on and connect directly to the Omtech with that to see if the Ruida panel changes to Lan ON, it doesn’t matter about IP address or subnet for this test because the Lan ON simply detects a physical connection.
There might be a problem with the short network extension cable that runs between the internal Ruida controller and the external port on the Omtech chassis. Try this - turn the machine off, open the side panel where the Ruida controller is, and connect the LB bridge directly to the ethernet port at the ruida controller. Turn on the machine and recheck the connection.
I can boot the PI and I will see a connection indicated on the Ruida that the lan is on (hardware wise)… Without a local network.
This all seems to indicate the PI isn’t booting properly… Although it does show up in the network view… doesn’t mean the wifi → Ethernet is actually working.
I’d at least set the gateway properly… There seems a proven record of the Ruida not being too smart when it comes to Ethernet. The Ruida should acknowledge the Bridge is connected via hardware.
I tried manually creating a new device, Ruida, LightBurn Bridge. I tried using, one at a time, both the 192.168.0.17 and 192.168.42.1 addresses. Setting up Ruida/LightBurn Bridge in LightBurn was successful, but neither address could send a file to the Ruida.
On the Ruida Controller I changed the gateway to 10.0.3.1
I’m not sure why I’m using 10.0.3.1, I don’t think there is any gateway there. But it works for you so I’m giving it a try.
I then restarted the controller. I restarted the LightBurn software. Alternately using the two possible addresses (192.168.42.1 and 192.168.0.17) and using the new Bridge device created manually, I was unable to move the laser head nor to send a file.
I tried to use the LightBurn Bridge Discovery Wizard, but it was unable to find my Bridge.
Where are you seeing that message? Based on your earlier message you indicated that you created a wifi.txt file. After successful connection Bridge will rename the file to wifi.txt.loaded.
That indicates that the Bridge is connecting to the wifi network specified.
In that case, you will not need to configure through the browser at 192.168.42.1.
If you’re now getting a light from the controller when connected to the Bridge then that’s likely the biggest hurdle.
Can you open 192.168.0.17 in a browser? That should show you a dashboard. What does it indicate? Can you take a screenshot?
I see that message when I try to use the Bridge Wizard to create a new Bridge/Device. That doesn’t work anyway.
[quote]Can you open 192.168.0.17 in a browser? That should show you a dashboard. What does it indicate? Can you take a screenshot?
[/quote]
No. When I try to open 192.168.0.17 in a browser it times out.
I cannot connect to the Bridge using a browser, either at 192.168.42.1 where Bridge wants me to configure Bridge, nor at 192.168.0.17 where my gateway says lightburnbridge is on the local network. I’ve since changed the gateway on the Ruida Controller to 198.168.0.1 (the gateway on my network).
I was unable to configure the Bridge using the Wizard. I was able to manually create a Bridge device.
The network cable leaving the Bridge has a green light on the left and an amber light on the right.
Using my computer, I am unable to find the Bridge listed as a Wifi network. I’m not sure I should be able to find it there.
The boot volume micro SD card has a wifi.txt.loaded file.
The bridge uses the values for the Ruida IP that I showed… machines gateway is on the 10.0.3.1 and the machine itself is on 10.0.3.3
Set both of these on the machine and then leave them alone. The PI will find this separate local network … The 10.0.3.x is a subnet for the Ruida…
The PI translates from your local network to the Ruida, so you can’t see the Ruida directly.
Boot the PI, it should get an ip address from your router, you won’t have to change this, but it’s smart to bind the PI’s IP with it’s Mac address so it will not change in the future.
You should be able to see the PI on your network, however you look…
These are pretty much plug and play, you shouldn’t have to modify anything…
If there’s any hope of connecting to the 192.168.42.1 you will need to change the wifi network to which you’re connected. So go to your wifi network settings and connect to the wifi network that the Bridge is broadcasting. It should be named something like “LightBurn Bridge” with possibly some letters/numbers appended to the end.
This assumes that the Bridge is in the network setup mode, however. But based on other things you’ve said it should already be configured to the network. So something is off.
If that doesn’t work you may want to reflash the SD card and start from the beginning.
