I have the up addresses set up on the laser and in macOS. The Ethernet adapter shows connected in macOS.
The lan shows On in Ruida.
But in LightBurn the laser shows disconnected. I set it up manually with the ip address of the laser.
The only weird thing is that in the Ruida it says to enter the gateway. Is this actually the gateway or the subnet mask? I’ve tried both with the same result. Thanks.
It’s the gateway. But in most typical scenarios this value doesn’t actually matter.
Can you post screenshots/photos of the following:
- ethernet configuration on the Mac
- IP configuration on Ruida
- device configuration in LightBurn
- wifi configuration or other network on the same Mac
How is the laser physically connected to the network? Is it direct to the computer or are you going through a switch/hub?
A couple of issues at play.
- If you’re connected directly from computer to Ruida on Ethernet you won’t be able to share the same subnet as your wifi as this will cause routing issues. Remedy this by creating a separate network just for the laser.
- From what I know Ruida controllers are hard-coded to only work on 255.255.255.0 subnet. Routing with any other subnet will not work.
To remedy, I recommend IP on Ruida of 10.0.3.3 (default for Ruida), gateway 10.0.3.100; manual IP on Mac ethernet as 10.0.3.100, subnet 255.255.255.0, router 10.0.3.3.
In LightBurn, go to Edit->Device Settings and change the IP listed there for the controller to 10.0.3.3.
Wonder if a gateway is really needed considering the smarts level of the Ruida.
I haven’t experimented with it at all but it’s possible that the Ruida is capable of working across networks which would necessitate a proper gateway setting. In most common setups I have not seen this be relevant.
This was my reasoning…
well that worked. Really odd though about the subnet. But thanks!
Spoke too soon. Now it says disconnected and will not reconnect. I’ve tried usb and that doesn’t work either. I’ve tried a windows laptop and got the same results.
Did anything change from the time that it worked until it didn’t?
Can you provide updated screenshots/photos of the network configuration?
Also, try pinging 10.0.3.3 from a Terminal session. What is the output?
Nothing changed.
Is a crossover cable required because I’m connecting my laptop directly to the laser?
Basically all modern devices support auto crossover so not necessary. And since it worked for a while the issue is almost certainly elsewhere.
If you can provide the requested information we can narrow down where it’s failing.
In the mid to early 90’s all hardware can negotiate and determine the type of hardware connection. So unless your hardware is about three decades old… forget about turn around cables…
As @berainlb noted, it wouldn’t have worked at all with a bad or incorrect Ethenet cable…
Did your machine forget the configuration… did you reboot or something?
I can ping the laser from the Mac successfully. Even after LightBurn says it’s disconnected.
I hooked both up to a switch and it lasted longer than direct connection. Five jobs instead of two. Idk.
If you can ping the controller then the network is working correctly. This likely means something else is going on.
When does this occur? Does this occur spontaneously while you’re using LightBurn? Or after a period of being idle? Or after waking from sleep?
Try right-clicking on the Devices button when this occurs to see if you’re able to reconnect.
It happens while using lightburn. Right clicking devices didn’t help. Neither does closing and reopening lightburn.
And to confirm, while in that disconnected state, you’re able to ping the laser?
Can you run ping and traceroute to 10.0.3.3 from Terminal while LightBurn is showing disconnected and then copy/paste results here?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.