Persistent busy signal?

Hello. I’m running GRBL software on a Universal Laser Engraver machine (not the best, I know), and Mac OS X 11.2.3. Everything was running OK yesterday (months with no issues, actually), and today after the Mac OS X update it still worked. But then Lightburn got stuck on “Busy”. The console says “Port opened, waiting for response.”

I updated LightBurn and it hasn’t corrected the issue. Tried unplugging the laser for 10 minutes to stop the data transfer but as soon as I plug it back in I get the “whirring” noise. I don’t even touch the software and it starts acting up again. Can I go back to an older version of LightBurn? What else would fix this issue?

I’ll add that it specifically started when I tried to frame the project.

Debug log:
21:25:11.044 D: “LightBurn 0.9.16” “Wed Mar 10 2021”
21:25:17.544 D: “starting” busy: false state: 0
21:25:17.544 D: EV: 1001 took 28 uS
21:25:17.544 D: Enumerating ports:
21:25:17.545 D: Port: “cu.Bluetooth-Incoming-Port”
21:25:17.545 D: Valid Candidate: false
21:25:17.545 D: PID: 0 VID: 0
21:25:17.545 D: Manufacturer: “”
21:25:17.545 D: Description: “incoming port - Bluetooth-Incoming-Port”
21:25:17.545 D: System Loc: “/dev/cu.Bluetooth-Incoming-Port”
21:25:17.545 D: Serial: “”
21:25:17.545 D:
21:25:17.545 D: Port: “tty.Bluetooth-Incoming-Port”
21:25:17.545 D: Valid Candidate: false
21:25:17.545 D: PID: 0 VID: 0
21:25:17.545 D: Manufacturer: “”
21:25:17.545 D: Description: “incoming port - Bluetooth-Incoming-Port”
21:25:17.545 D: System Loc: “/dev/tty.Bluetooth-Incoming-Port”
21:25:17.545 D: Serial: “”
21:25:17.545 D:
21:25:17.545 D: Port: “cu.usbserial-1440”
21:25:17.545 D: Valid Candidate: true
21:25:17.545 D: PID: 29987 VID: 6790
21:25:17.545 D: Manufacturer: “”
21:25:17.545 D: Description: “USB Serial”
21:25:17.545 D: System Loc: “/dev/cu.usbserial-1440”
21:25:17.545 D: Serial: “”
21:25:17.545 D:
21:25:17.545 D: Port: “tty.usbserial-1440”
21:25:17.545 D: Valid Candidate: false
21:25:17.545 D: PID: 29987 VID: 6790
21:25:17.545 D: Manufacturer: “”
21:25:17.546 D: Description: “USB Serial”
21:25:17.546 D: System Loc: “/dev/tty.usbserial-1440”
21:25:17.546 D: Serial: “”
21:25:17.546 D:
21:25:17.596 D: Found port: PID 29987 VID 6790
21:25:17.596 D: Manufacturer: “”
21:25:17.596 D: Product: “USB Serial”
21:25:17.596 D: Name: “cu.usbserial-1440”
21:25:17.603 D: Port open succeeded
21:25:17.646 D: “starting” busy: false state: 0
21:25:17.647 D: EV: 1001 took 29 uS
21:25:18.627 D: “Attempting to connect” busy: false state: 1
21:25:18.627 D: “Connecting…” busy: false state: 1
21:25:18.630 D: O: “0a”
21:25:31.804 D: EV: 1018 took 5 uS
21:25:31.812 D: EV: 1003 took 8153 uS
21:25:31.870 D: “starting” busy: false state: 0
21:25:31.870 D: EV: 1001 took 20 uS
21:25:31.870 D: Enumerating ports:
21:25:31.871 D: Port: “cu.Bluetooth-Incoming-Port”
21:25:31.871 D: Valid Candidate: false
21:25:31.871 D: PID: 0 VID: 0
21:25:31.871 D: Manufacturer: “”
21:25:31.871 D: Description: “incoming port - Bluetooth-Incoming-Port”
21:25:31.871 D: System Loc: “/dev/cu.Bluetooth-Incoming-Port”
21:25:31.871 D: Serial: “”
21:25:31.871 D:
21:25:31.871 D: Port: “tty.Bluetooth-Incoming-Port”
21:25:31.871 D: Valid Candidate: false
21:25:31.871 D: PID: 0 VID: 0
21:25:31.871 D: Manufacturer: “”
21:25:31.871 D: Description: “incoming port - Bluetooth-Incoming-Port”
21:25:31.871 D: System Loc: “/dev/tty.Bluetooth-Incoming-Port”
21:25:31.871 D: Serial: “”
21:25:31.871 D:
21:25:31.871 D: Port: “cu.usbserial-1440”
21:25:31.871 D: Valid Candidate: true
21:25:31.871 D: PID: 29987 VID: 6790
21:25:31.871 D: Manufacturer: “”
21:25:31.871 D: Description: “USB Serial”
21:25:31.871 D: System Loc: “/dev/cu.usbserial-1440”
21:25:31.871 D: Serial: “”
21:25:31.871 D:
21:25:31.871 D: Port: “tty.usbserial-1440”
21:25:31.871 D: Valid Candidate: false
21:25:31.871 D: PID: 29987 VID: 6790
21:25:31.871 D: Manufacturer: “”
21:25:31.871 D: Description: “USB Serial”
21:25:31.871 D: System Loc: “/dev/tty.usbserial-1440”
21:25:31.871 D: Serial: “”
21:25:31.871 D:
21:25:31.921 D: Found port: PID 29987 VID 6790
21:25:31.921 D: Manufacturer: “”
21:25:31.921 D: Product: “USB Serial”
21:25:31.921 D: Name: “cu.usbserial-1440”
21:25:31.928 D: Port open succeeded
21:25:31.971 D: “starting” busy: false state: 0
21:25:31.971 D: EV: 1001 took 14 uS
21:25:31.971 D: EV: 1019 took 159310 uS
21:25:31.972 D: Clipboard data present:
21:25:31.972 D: ()
21:25:32.947 D: “Attempting to connect” busy: false state: 1
21:25:32.947 D: “Connecting…” busy: false state: 1
21:25:32.947 D: O: “0a”

No help? Really?

What do you mean by “the whirring noise”?

We have done very minimal testing on Big Sur at this point, and it seems like with each new update to it they break something new. We will be getting a new development machine to install and use it, to make sure it doesn’t completely mess up the machine we use for legacy macOS builds.

The log is showing that the device is not responding back to you when LightBurn sends the ping (the equivalent of pressing Enter). If everything has been working up to this point, and neither LightBurn or the laser have changed, I think we have a pretty strong indication that it’s the Big Sur update that broke it.

All older versions of LightBurn are available here: Releases · LightBurnSoftware/deployment · GitHub

As a test, try 0.9.16 - there was a change made after that version which caused connection issues on some machines, and has been fixed for 0.9.21. If the 9.16 release works, there’s a decent chance that the upcoming 9.21 release will too.

OK, thanks, I tried version 0.9.18 since that what I was using before this happened, but I’ll try 0.9.16 later today. Going back to 0.9.18, the message in the console changed from “Waiting for connection” to “Port opened, waiting for response”. So a little progress. Maybe I’ll go back one version of Mac OS X, too.

By “whirring” noise, I meant the laser motors. They’re never totally silent, but when I would move the laser, they’d make a bit more noise (normal and expected). Ever since the change, they’re always stuck on that louder noise.

Carlos, the sound changes as the speed changes, could it be that the settings for your speeds in the settings are a little different than before? (also acceleration)

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.