Did you run the 2 tests from my post above? Can you take screenshots of both results?
Yes I’ve added it manually to LB, and also verified it isn’t detected when connected (also tried three different cables).
Usually lack of terminal device is due to missing driver.
What do you get in System Report?
No love there either …
Does ‘lsusb’ give you anything useful? You might have to install it… it might give you similar results to your ‘usb tree’…
jack@Kilo:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 056a:0011 Wacom Co., Ltd ET-0405A [Graphire2 (4x5)]
Bus 003 Device 003: ID 1af3:0001 Kingsis Peripherals ZOWIE Gaming mouse
Bus 003 Device 015: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
jack@Kilo:~$
The “QinHeng” entry is my led laser…
As @berainlb pointed out, this is usually indicative of a driver issue…
Good luck
If the device is not showing in System Report then that means the computer is not seeing the hardware at all.
Can you confirm the machine was turned on when you check System Report? If so, then you may have a more fundamental problem. Either bad controller, bad cable, or bad USB port.
Can you confirm the port works for other devices? How are you connecting the laser to the computer?
Do you have any other computer which you can use to confirm that the controller gets recognized?
Yes I the machine was turned on at the time. I’ve tried 3 separate cables, USB-C to USB-C. The port does work, as I type this I’m connected to both power and an external display in the same port (when trying the laser it’s the only thing I have connected).
Sadly I don’t currently have another machine to use for testing.
This pretty much leaves the drivers for that usb port.
Maybe someone with one of these machine can check the module (driver) that is loaded and compare them.
Did you by chance leave the TF card in the machine while trying to plug into USB? I’m wondering if the presence of the TF card disables USB mode.
Nope, I actually tried it both with and without, same result.
I just got my Falcon laser today.
I have the same problem with a 10W Falcon Laser and my M1 Macbook Pro Monterey (OS 12.6). LightBurn would not see the laser. Mac did not see the USB device.
I pulled out my old 2012 Intel Macbook Pro running Catalina (OS 10.15) and connected it. LightBurn recognized the laser immediately and it works perfectly.
Based on that, I’m going to guess that either Apple Silicon Macs or the current Mac OS is incompatible with the Falcon Laser.
I’m thankful I have a mac to use, otherwise I’d probably return the laser.
This issue with macs seems to be mostly related to the proper driver, might double check that…
I had an issue with the JL1 and, to my surprise, it was a driver, fortunately it was not a drunk driver 
not used to that with Linux.
Good luck
I’ve had that issue with my Creality CV-30 Laser Falcon and another Laser that has a USB-C port.
But I found a solution:
Use a USB-C to USB-A hub or dock and from there a USB-A to USB-C cable.
This way the controller on the laser is found as a USB-Serial port on the Mac.
There’s no need to install any USB-Serial driver on current versions of macOS, it’s all included!
PS: The baud rate of the Creality CV-30 Laser Falcon is 250000 bps.
1 Like
Tried this, no luck unfortunately.
Hi Everyone,
Having exactly the same issue here albeit with the Falcon 10W. Not showing up in terminal or LB regardless of anything suggested above. Happening on a MBP running Catalina.
Really hoping someone might find a workaround for this soon.
Thanks for the support,
Ian
I don’t have a mac or that machine, but I have Linux and some of the commands might help.
“lsusb” will list what devices are ‘hanging’ off the usb ports.
jack@Kilo:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 056a:0011 Wacom Co., Ltd ET-0405A [Graphire2 (4x5)]
Bus 003 Device 002: ID 1af3:0001 Kingsis Peripherals ZOWIE Gaming mouse
Bus 003 Device 066: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
jack@Kilo:~$
This entry from lsusb if from my Chinese led laser and yours might be the same or very similar.
Bus 003 Device 066: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
There is a file where system messages are logged. I plugged in my ‘dragon’ and here’s how it shows in the log file…
dmesg usually requires root privilege … it’s also very long … pipe it though ‘tail’ to only get the ‘tail’ end of it…
jack@Kilo:~$ sudo dmesg | tail
[1537511.362953] audit: type=1400 audit(1664892520.980:309): apparmor="DENIED" operation="capable" profile="snap.chromium.hook.configure" pid=2048438 comm="fc-cache" capability=2 capname="dac_read_search"
[1537511.362964] audit: type=1400 audit(1664892520.980:310): apparmor="DENIED" operation="capable" profile="snap.chromium.hook.configure" pid=2048438 comm="fc-cache" capability=1 capname="dac_override"
[1537519.686375] audit: type=1400 audit(1664892529.304:311): apparmor="DENIED" operation="capable" profile="snap.chromium.hook.configure" pid=2048438 comm="fc-cache" capability=2 capname="dac_read_search"
[1539020.890769] usb 3-2: USB disconnect, device number 64
[1539025.295774] usb 3-2: new full-speed USB device number 65 using xhci_hcd
[1539025.445229] usb 3-2: New USB device found, idVendor=03eb, idProduct=2107, bcdDevice= 1.00
[1539025.445243] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1539025.445248] usb 3-2: Product: AVRDRAGON
[1539025.445252] usb 3-2: Manufacturer: ATMEL
[1539025.445256] usb 3-2: SerialNumber: 00A200063403
jack@Kilo:~$
At least you should be able to ID the device and acertain if the OS is accepting it…
If the dmesg shows ‘disconnected’, it’s not talking properly…
I hope this makes some sense to you…
Good luck
I’ve been trying to use Lightburn with my new iMac and Atomstack a20, but I’ve had the same sort of problem that others have mentioned here.
I’ve run through the recommended actions, including buying a new cable. My iMac recognises the device, but I have had to input the device details manually. However, it remains ‘Disconnected’ in Lightburn’s Laser window.
Also - in the console window, I get the message:
Waiting for connection…
Port failed to open - already in use?
How do I ensure the relevant port is open so Lightburn can function?
I’d be really grateful for help with this, as I’m new to this technology and it’s been a steep learning curve to even get to this stage.
Relevant info:
iMac specs: 24 inch, M1, 2021
MacOS Monterey 12.6
Atomstack a20 Pro
Mac System Report shows the Atomstack is on USB Serial
USB Serial:
Product ID: 0x7523
Vendor ID: 0x1a86
Version: 81.33
Speed: Up to 12 Mb/s
Location ID: 0x02400000 / 1
Current Available (mA): 500
Current Required (mA): 102
Extra Operating Current (mA): 0
Terminal response:
Last login: Tue Oct 4 17:18:29 on console
paulfretwell@Pauls-iMac ~ % ls /dev/usb
/dev/cu.usbserial-240 /dev/tty.usbserial-240
paulfretwell@Pauls-iMac ~ %
There have been some users that experienced similar troubles with the falcon:Creality CV-30 Laser Falcon - #21 by tundrwd
They remedied it with a firmware update, the info is in that thread.
1 Like
Thanks. Also tried this but I can’t even get the firmware to update (as far as I can tell). Laser goes into a repeating beep cycle that never ends. I’ve reached out to support but still no solution. Works fine offline, just annoyed I can’t get it to work with my Mac.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.