Neje laser not connected in lightburn

Neje laser cutter not recognized in lightburn
I have just acquired Lightburn (license key) 1.5.02. On the trial version I had no problems of recognise. However, it is impossible to connect my laser cutter to the licensed version. I get the following message: “Failed to open port - already in use?”
I read what I found on the forum and applied:

  • test my USB port: it is recognized with a USB key but does not recognize the machine.
  • test my USB cable: it does not present a problem in another configuration.
  • uninstall lightburn 1.5.02 and reinstall it: still does not recognize the machine.
  • delete the config, turn off the machine, close lightburn, turn off the PC, restart everything: still no recognition.
  • delete lightburn and reinstall lightburn with appimage but same problem
  • the ch340 driver is ok
  • the material is ok and work in neje application.
    note: lightburn keeps in memory a configuration called ttyS0 without it being linked to a machine or a type of config (grbl, etc.) and which cannot be erased.
    system: lubuntu 22.04
    laser : Neje master 2 max A40640 module

Thank you for your answers

can you confirm, or send a screenshot of lightburn, that you are selecting the correct com port on the laser panel?


in your console/terminal on linux can you type
With machine plugged in and powered on

lsusb
and post the export

or
ls /sys/class/tty/ttyUSB*

if laser is connected in usb02 :

Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 7392:a812 Edimax Technology Co., Ltd Edimax AC600 USB
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 009: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

if usb key is connected in usb2 
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 7392:a812 Edimax Technology Co., Ltd Edimax AC600 USB
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 010: ID 0781:5581 SanDisk Corp. Ultra
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Unplug laser and repeat?
Because i cant see it.

Granted i am not a Linux expert maybe i am missing it

if i connected an usbkey in usb2 I see it :

Bus 001 Device 010: ID 0781:5581 SanDisk Corp. Ultra

I connected the laser Neje on the same usb2 I dont see it with lsusb. but I verified my usb cable that it’s ok with other material.

i am really not an expert in linux so we might need some better brains on this

Lets see if others can help
But from what i can see your linux box is not seeing the laser at all

yes i verified the usb lightburn connect with the command

ls /dev/ttyUSB*
/dev/ttyUSB0

the ch340 driver is ok.
if I used in lightburn the grbl-lpc or grbl-m3 in device auto i see in lightburn console : “waiting for connection”
and if I connect to neje application to the laser the material is recognized and works correctly.

Neje - specially the latest ones - should be not under M3 or LPC but Top Grlb controller you should do it by hand
But Lightburn must be able to see it correct too

yes and in the lightburn test versus, my params was grbl 1.1 by usb mode and the neje laser material was working well…

if i read my lsusb the laser is here

Bus 001 Device 009: ID 1a86:7523 QinHeng Electronics CH340 serial converter

but not recognized in lightburn 1.5.2

I cant imagine any reason why your lightburn isnt - now that you enabled license your device
I sugest you delete your current profile, and add a grbl profile by hand

Then select the correct port, and connect

Remember that on Linux there are special instructions for giving $USER

sudo adduser $USER dialout && sudo adduser $USER tty

Reconfirm this

It’s done.
and it was a manual configuration that was done. the detection version does not find the neje laser either

I have no more ideas either

We would need someone with more experience on linux to help

I cant thikn of anything else

if i see the file lbset in machine settings folder :
“{
“Name”: “GRBL”,
“Settings”: [
]
}”
is this normal?

because i read that ubuntu 22.04 change the mouse driver, i am change usb for the mouse and reboot the pc and lightburn, remake my grbl config

i am seeing this :

"Waiting for connection…

Waiting for connection…

Grbl 1.1f [‘$’ for help]

ok

[VER:1.1f.20180715:]

[OPT:VML,35,254]

Target buffer size found

ok

Homing

ok"

now test if all works well :wink:

I write a new sujet because I have problem (homing) between lightburn and grbl controller that is not a problem on neje app, or for material reset

Homing is Software independent
This happens at the firmware level

What errors you getting in console?

the material now engraves in reverse (in x and y) and I ask to return in home on lightburn, it the machine tries to exceed the y and no stop. but if I press the reset button of the machine it returns correctly to the home of the machine and stop; if I test on neje app, return in home well. note : it is not possible to update the neje firmware on ubuntu (or I have not yet found the solution)

alarm 9 on lightburn

Waiting for connection…

Grbl 1.1f [‘$’ for help]

ok

[VER:1.1f.20180715:]

[OPT:VML,35,254]

Target buffer size found

ok

$0=10

$1=25

$2=0

$3=3

$4=0

$5=0

$6=0

$10=0

$11=0.010

$12=0.002

$13=0

$20=0

$21=0

$22=1

$23=1

$24=250.000

$25=1000.000

$26=250

$27=1.000

$30=1000

$31=0

$32=1

$100=80.000

$101=80.000

$102=80.000

$110=4000.000

$111=4000.000

$112=4000.000

$120=200.000

$121=200.000

$122=200.000

$130=810.000

$131=460.000

$132=150.000