Lightburn Bridge - Laser timeout error

LightBurn Hardware Compatibility LightBurn Bridge
1

Hi there, I have a Raspberry Pi 3b+ with LightBurn Bridge v1.0.0-RC3 running on it.
I have the following:

  • The bridge connects my home WiFi on 192.168.0.71 (static IP)
  • I have set the Laser IP to 10.0.3.3 on the Ruida controller
  • When connecting, I have the laser on and running
  • The controller ethernet is connected directly between the controller and the pi
  • My laptop running Lightburn is currently set to use 192.168.0.217

It looks to me from the logs, that the Pi is connected to the WiFi network, and the internal ethernet port is registered at 10.0.3.1, and I know the printer ip is set to 10.0.3.3, however it looks to me like there is some sort of issue when the Bridge tries to talk to the controller.

What else can I do to get this working? Am I missing something?

I have not been able to SSH into the pi - I cannot workout what the username and password is set to (I’ve tried things like pi/raspberry, admin/root etc.).

-- Logs begin at Tue 2021-09-14 17:59:29 SAST, end at Wed 2025-05-07 11:26:53 SAST. --
May 07 08:02:03 lightburn systemd[1]: Started LightBurn Bridge Relay.
May 07 08:02:03 lightburn python3[443]: 2025-05-07 08:02:03,906 | INFO - {'device_type': 'ruida', 'laser_ip': '10.0.3.3', 'ap_name': 'LightBurn Bridge 695C'}
May 07 08:02:03 lightburn python3[443]: 2025-05-07 08:02:03,907 | INFO - Setting up ethernet...
May 07 08:02:03 lightburn python3[443]: 2025-05-07 08:02:03,909 | INFO - No relay loaded
May 07 08:02:03 lightburn python3[443]: 2025-05-07 08:02:03,911 | INFO - Running: nmcli -g GENERAL.CONNECTION device show wlan0
May 07 08:02:04 lightburn python3[443]: 2025-05-07 08:02:04,834 | INFO - Running: nmcli -g IP4.ADDRESS device show wlan0
May 07 08:02:04 lightburn python3[443]: 2025-05-07 08:02:04,912 | INFO - Running: nmcli -g ipv4.addresses con show LBBDirect
May 07 08:02:04 lightburn python3[443]: 2025-05-07 08:02:04,983 | INFO - $> 10.0.3.1/24
May 07 08:02:04 lightburn python3[443]: 2025-05-07 08:02:04,989 | INFO - Requested eth0 IP of 10.0.3.1 is already configured. Skipping setup.
May 07 08:02:04 lightburn python3[443]: 2025-05-07 08:02:04,989 | INFO - Starting ruida relay
May 07 08:02:04 lightburn python3[443]: 2025-05-07 08:02:04,991 | INFO - ruida 1.0
May 07 08:02:04 lightburn python3[443]: 2025-05-07 08:02:04,992 | INFO - Ruida relay started, laser IP: 10.0.3.3
May 07 08:13:06 lightburn python3[443]: 2025-05-07 08:13:06,991 | INFO - Connection from: 192.168.0.217:63034
May 07 08:13:07 lightburn python3[443]: 2025-05-07 08:13:07,341 | INFO - Ruida command complete
May 07 08:13:07 lightburn python3[443]: 2025-05-07 08:13:07,364 | INFO - Connection from: 192.168.0.217:63065
May 07 08:13:13 lightburn python3[443]: 2025-05-07 08:13:13,537 | ERROR - Laser timeout error
May 07 08:13:13 lightburn python3[443]: 2025-05-07 08:13:13,538 | INFO - Ruida command complete```
2

Are you saying you want us to guess the Pi login for you? Unless you bought the Pi from Lightburn, and you did not mess with it, I doubt we will have any better luck than you are having.

If it was bought from LB, contacting support@lightburnsoftware.com may get you the answer you need.

3

I lost two PI’s to thunderstorms and with covid, they became to expensive.

I’ve probably forgotten most of this, but read through this link and see if it helps… If not sing out.

Seems there wasn’t a password or it was the users password, but I thought you can sudo passwd. As far as I remember, it was so simple I forgot it…

:smiley_cat:

4

Hi there, thank you for your suggestion. I’ve managed to get SSH access now (I had to specify the user/pass when flashing the image. I’ve looked at the Bridge setup and can confirm my Bridge IP is set to 10.0.3.1, and I’ve set the controller IP to 10.0.3.3 as per the instructions. I can ping the iP too.

When I scan for a bridge setup, I end up with this:

image
image1586×846 77.5 KB

It looks like somehow the bridge is not able to communicate with the controller. I have had a look at the other thread you suggested, but I cannot see any resolution to the issue. If you do have any other ideas, I’m all ears :slight_smile:

5

The console of your machine shows the Internet link status. Does it show active? This is only an indicator of if the hardware is connected and doesn’t show an actual software connection. There is also a red led on the controller, labeled as LINK that also shows a hardware connection.

Not sure what else to advise you with this. I don’t use their bridge, I just use a wifi with an Ethernet connection. I have used it, but never really did any poking around on the PI.

Maybe @Rick could advise us with this.

You can use the Lightburn search (upper right) and enter something similar to your title here.. there have been a few of these pop up.

Good luck

:smiley_cat:

6

Are you pinging the laser from the Pi itself?

Can you confirm that you are able to control the laser via Ethernet when connected directly to PC? If so, are you using the same ethernet cable from Pi to Ruida?

What kind of Ruida controller do you have?

Do you see link indicator lights on both sides of the Pi <> Ruida jacks?

2 Likes