I am no longer able to connect to my GRBL machine with Lightburn, using Bluetooth serial.
This was working fine, and still work with other software, like GRBL controller.
The point is the bluetooth is not listed (as a serial port ) in lightburn ONLY.
I removed BT audio driver (as I did before), rebooted the whole rig several times…
I still can’t connect to anything else than USB …What do I miss???
What changed on the system? Did you recently update LightBurn? The OS? Install a new Bluetooth device? Any hardware or cabling changes?
I have updated grbl, but I checked everything and for now, it’s fine.
I don’t think there has been an update for a while, ether for the MacOs or Lightburn… (so it’s the last LB). And I can connect to the machine regularly with Grbl Controller.
I have nothing to "Choose " for the connection, and the console prints " waiting connection " or so…
LB is no longer listing the bluetooth serial, in other words…
How do I force that , if possible?
What does “fine” and “latest” mean? Using numbers and settings is a better way to provide insight so we can help diagnose your issues.
Try and run the ‘Find my Laser’ again to create a new profile. The one you currently have may have been corrupted in some way. Let us know the results and we can go from there.
Sorry… and Hi Rick !
LightBurn 0.9.11
GRBL 1.1.h (I did not a firmware upgrade, I changed the setup, same version, proved to workalready. Anyway Bluetooth is not related to Grbl…).
Fine mean, here: I can connect Lightburn to the machine using USB . Grbl is responding to commands.I also can connect the machine using bluetooth on an other software using bluetooth as a serial port.
“Find my laser” finds void.
Is there a file i could try to trash to reset the connection settings?
LightBurn explicitly filters out Bluetooth devices on MacOS because practically all of them are things like Bluetooth headphones that will crash the framework system we use when I try to talk to them.
You say, “I can no longer…” - as in, it worked before, but now it doesn’t. What did you change?
no changes… same all… I just took a one month break.
Yes, it used to work, smoothly…
using usb, the connection works instantly.
But no mention of a Bluetooth serial port in LightBurn anymore, anywhere.
The laser is the only BT device paired at that time.
The problem appears to be in LightBurn itself,
the BT connection works , Grbl works, and I am able to connect with BT using an other software.
prefs.ini doesn’t appear to contain anything about serial port (am i wrong?),
therefore, what file should I delete to reset LightBurn to a fresh default state?
thx
the only change might be the last LightBurn update (0.9.11)…
Is that possible? --like a change in the BT handling, or a too-tight “filtering”?–
I already deleted and re-created a device profile in LB,
trashed prefs and .ini
rebooted
repaired authorisations, …
and so on.
Roll back to 0.9.10 (or even 0.9.9) could be the option,
if only I had a backup… 
All previous versions of LightBurn are available in our version archive, here: Releases · LightBurnSoftware/deployment · GitHub
thank you for the link !
I’ll give a shoot right now !
THAT’S IT!
0.9.10 connects right away… still reply" error9" but everything works fine*…
Again, thank you for the link…
So just to know: Does 0.9.11 ignore Bluetooth Serial Port definitely, or is it a temporary bug?
Cheers
No, LightBurn is not ignoring BlueTooth Serial Ports, it is filtering them at this point as @LightBurn described above.
While understanding this is not what you want, nor what you were able to do in previous releases, this is not a bug as this is the intended behavior at this point.
It’s absolutely not a bug, but if you’re willing to do a test for me, I might be able to add this specific device to an “allow” list so it isn’t filtered in the future. Do this:
- Run LightBurn
- Go to Help > Enable Debug Logging
- Right-click the ‘Devices’ button to force LightBurn to reconnect to the machine
- Quit
Post the file called “LightBurnLog.txt” from your Documents folder. You can delete the file after that.
2 Likes
Great !
Here is the log:
15:17:51.582 D: “LightBurn 0.9.11” “ven. mai 29 2020”
15:17:58.728 D: EV: 1018 took 8 uS
15:17:58.737 D: EV: 1003 took 10566 uS
15:17:58.892 D: “starting” busy: false state: 0
15:17:58.892 D: EV: 1001 took 7 uS
15:17:58.892 D: Enumerating ports:
15:17:58.893 D: Port: “cu.Bluetooth-Incoming-Port”
15:17:58.893 D: Valid Candidate: false
15:17:58.894 D: PID: 0 VID: 0
15:17:58.894 D: Manufacturer: “”
15:17:58.894 D: Description: “incoming port - Bluetooth-Incoming-Port”
15:17:58.894 D: System Loc: “/dev/cu.Bluetooth-Incoming-Port”
15:17:58.894 D: Serial: “”
15:17:58.894 D:
15:17:58.894 D: Port: “tty.Bluetooth-Incoming-Port”
15:17:58.894 D: Valid Candidate: false
15:17:58.894 D: PID: 0 VID: 0
15:17:58.894 D: Manufacturer: “”
15:17:58.894 D: Description: “incoming port - Bluetooth-Incoming-Port”
15:17:58.894 D: System Loc: “/dev/tty.Bluetooth-Incoming-Port”
15:17:58.894 D: Serial: “”
15:17:58.894 D:
15:17:58.894 D: Port: “cu.GRBL_BT-DevB”
15:17:58.894 D: Valid Candidate: false
15:17:58.894 D: PID: 0 VID: 0
15:17:58.894 D: Manufacturer: “”
15:17:58.894 D: Description: “outgoing port - GRBL_BT-DevB”
15:17:58.894 D: System Loc: “/dev/cu.GRBL_BT-DevB”
15:17:58.894 D: Serial: “”
15:17:58.894 D:
15:17:58.894 D: Port: “tty.GRBL_BT-DevB”
15:17:58.894 D: Valid Candidate: false
15:17:58.894 D: PID: 0 VID: 0
15:17:58.894 D: Manufacturer: “”
15:17:58.895 D: Description: “outgoing port - GRBL_BT-DevB”
15:17:58.895 D: System Loc: “/dev/tty.GRBL_BT-DevB”
15:17:58.895 D: Serial: “”
15:17:58.895 D:
15:17:58.895 D: EV: 1019 took 157197 uS
15:17:58.895 D: Clipboard data present:
15:17:58.895 D: ()
15:18:05.281 D: EV: 1018 took 8 uS
15:18:05.289 D: EV: 1003 took 9505 uS
15:18:05.432 D: “starting” busy: false state: 0
15:18:05.432 D: EV: 1001 took 6 uS
15:18:05.432 D: Enumerating ports:
15:18:05.434 D: Port: “cu.Bluetooth-Incoming-Port”
15:18:05.434 D: Valid Candidate: false
15:18:05.434 D: PID: 0 VID: 0
15:18:05.434 D: Manufacturer: “”
15:18:05.434 D: Description: “incoming port - Bluetooth-Incoming-Port”
15:18:05.434 D: System Loc: “/dev/cu.Bluetooth-Incoming-Port”
15:18:05.434 D: Serial: “”
15:18:05.434 D:
15:18:05.434 D: Port: “tty.Bluetooth-Incoming-Port”
15:18:05.434 D: Valid Candidate: false
15:18:05.434 D: PID: 0 VID: 0
15:18:05.434 D: Manufacturer: “”
15:18:05.434 D: Description: “incoming port - Bluetooth-Incoming-Port”
15:18:05.434 D: System Loc: “/dev/tty.Bluetooth-Incoming-Port”
15:18:05.434 D: Serial: “”
15:18:05.434 D:
15:18:05.434 D: Port: “cu.GRBL_BT-DevB”
15:18:05.435 D: Valid Candidate: false
15:18:05.435 D: PID: 0 VID: 0
15:18:05.435 D: Manufacturer: “”
15:18:05.435 D: Description: “outgoing port - GRBL_BT-DevB”
15:18:05.435 D: System Loc: “/dev/cu.GRBL_BT-DevB”
15:18:05.435 D: Serial: “”
15:18:05.435 D:
15:18:05.435 D: Port: “tty.GRBL_BT-DevB”
15:18:05.435 D: Valid Candidate: false
15:18:05.435 D: PID: 0 VID: 0
15:18:05.435 D: Manufacturer: “”
15:18:05.435 D: Description: “outgoing port - GRBL_BT-DevB”
15:18:05.435 D: System Loc: “/dev/tty.GRBL_BT-DevB”
15:18:05.435 D: Serial: “”
15:18:05.435 D:
15:18:05.435 D: EV: 1019 took 145750 uS
15:18:05.435 D: Clipboard data present:
15:18:05.436 D: ()
15:18:08.497 D: “starting” busy: false state: 0
15:18:08.498 D: EV: 1001 took 12 uS
15:18:08.498 D: Enumerating ports:
15:18:08.499 D: Port: “cu.Bluetooth-Incoming-Port”
15:18:08.499 D: Valid Candidate: false
15:18:08.499 D: PID: 0 VID: 0
15:18:08.499 D: Manufacturer: “”
15:18:08.499 D: Description: “incoming port - Bluetooth-Incoming-Port”
15:18:08.499 D: System Loc: “/dev/cu.Bluetooth-Incoming-Port”
15:18:08.499 D: Serial: “”
15:18:08.499 D:
15:18:08.499 D: Port: “tty.Bluetooth-Incoming-Port”
15:18:08.499 D: Valid Candidate: false
15:18:08.500 D: PID: 0 VID: 0
15:18:08.500 D: Manufacturer: “”
15:18:08.500 D: Description: “incoming port - Bluetooth-Incoming-Port”
15:18:08.500 D: System Loc: “/dev/tty.Bluetooth-Incoming-Port”
15:18:08.500 D: Serial: “”
15:18:08.500 D:
15:18:08.500 D: Port: “cu.GRBL_BT-DevB”
15:18:08.500 D: Valid Candidate: false
15:18:08.500 D: PID: 0 VID: 0
15:18:08.500 D: Manufacturer: “”
15:18:08.500 D: Description: “outgoing port - GRBL_BT-DevB”
15:18:08.500 D: System Loc: “/dev/cu.GRBL_BT-DevB”
15:18:08.500 D: Serial: “”
15:18:08.500 D:
15:18:08.500 D: Port: “tty.GRBL_BT-DevB”
15:18:08.500 D: Valid Candidate: false
15:18:08.500 D: PID: 0 VID: 0
15:18:08.500 D: Manufacturer: “”
15:18:08.500 D: Description: “outgoing port - GRBL_BT-DevB”
15:18:08.500 D: System Loc: “/dev/tty.GRBL_BT-DevB”
15:18:08.500 D: Serial: “”
15:18:08.500 D:
15:18:14.878 D: EV: 1018 took 9 uS
15:18:14.878 D: EV: 1013 took 35 uS
15:18:14.880 D: EV: 1018 took 8 uS
15:18:14.880 D: EV: 1009 took 2341 uS
I’ve added code to 0.9.12 to allow this device through.
1 Like
Wonderful ! 
Thank you very much!
G.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.