I have the problem: when I send a file to the controller it says its busy and fails. this happens with two different computers and pretty consistently over the last couple years. I have no idea if Lightburn caused this, but nothing changed with the controller. It is an old controller purchased from Light Object called LO-X7.
Recently I’m finding that when go to the CMD screen and ping the controller address it fails less.
So in the command prompt screen type ping 192.168.1.100 (whatever your address is) and sends some packets to the machine and displays its response. At least that what I think it does. anyway it seems to wake up something because it generally sends the file without error after I do that. Just FYI if you have a similar situation.
I have a t-link bridge on my Ruida. I can’t access it after a new OS install because the IP is behind the bridge. Once I ping it, it can be found by Lightburn.
Thanks for the heads up, didn’t think any of these worked via WIFI.
So I’m using a small blue Vonets bridge router Jack. It connects to my home router once I turn the machine on. So I don’t mess with that connection and my pc isn’t involved with the bridge router.
I just come up with some address that is not in use and match that address in both Lightburn and the controller. The pc has to be on the home router for this to work.
So my old laser controller only has an Ethernet port. I’m not sure why everyone wouldn’t set up a WiFi connection over a wired connection, as long as it works. So WiFi allows files to transmit but not fast enough for other controllers that receive coordinate moves from the pc. Like for CNC routers.
The basic use of a bridge is to connect two different domains, in networking terms. The Lightburn Raspberry PI actually does that as you keep the original 10.0.3.x address on your machine and it bridges that domain to your local network. The laser shouldn’t need to be on one of your local network, at least IP wise.
Many people run grbl machines and they get the data streamed to the device, so a WIFI connection can cause problems if it drops out or disconnects. Most DSP type controllers load the complete jobs code into the dsp memory, so speed isn’t of the essence. Most dsp types that use the internet have about a 100mb transfer rate, which is pretty fast.
Not sure what you mean by like cnc routers. CNC just means it’s computer numerical control and that is moving to about everything. My wife’s Subaru is a CNC machine, there is no steering shaft, it goes to an encoder that’s read by the computer which turns the wheels.
So pretty much everything in today’s world is a CNC machine.
One of the reasons Ethernet is used is that it’s had all the bugs worked out of it and there is no drivers that the user has to deal with, they are already in place for network availability.
