I created a device manually. but it doesn’t respond when I try to move the laser in lightburn.
Can you pull down the Ports field in Laser window and take a screenshot?
You mean to say that you pushed the button currently showing as “(Auswählen)” and there are no choices there?
If so, I think that confirms that for some reason you’re not getting a Serial device setup. So looks like the device is detected, LightBurn is setup but you don’t have a Serial device.
Let’s try to figure out why.
Can you run these commands in Terminal and return results??
lsb_release -a
lsmod | grep ch341
dmesg | grep ch341
Yes, i pushed the byutton down and there are no choices
anna@anna-Inspiron-15-3567:~$ lsb_release -a
LSB Version: core-11.1.0ubuntu4-noarch:printing-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
anna@anna-Inspiron-15-3567:~$ lsmod | grep ch341
ch341 24576 0
usbserial 57344 1 ch341
anna@anna-Inspiron-15-3567:~$ dmesg | grep ch341
dmesg: read kernel buffer failed: Operation not permitted
anna@anna-Inspiron-15-3567:~$ sudo dmesg | grep ch341
[sudo] password for anna:
Sorry, try again.
[sudo] password for anna:
[ 709.383563] usbcore: registered new interface driver ch341
[ 709.383610] usbserial: USB Serial support registered for ch341-uart
[ 709.383638] ch341 1-1:1.0: ch341-uart converter detected
[ 709.384302] usb 1-1: ch341-uart converter now attached to ttyUSB0
[ 713.231022] usb 1-1: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1
[ 713.232059] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0
[ 713.232132] ch341 1-1:1.0: device disconnected
Looks like there’s a device conflict which is hijacking the terminal. This is a known issue.
Information here for reference:
Can you run this in Terminal:
grep 7523 /usr/lib/udev/rules.d/*
~$ grep 7523 /usr/lib/udev/rules.d/*
/usr/lib/udev/rules.d/85-brltty.rules:# Device: 1A86:7523
/usr/lib/udev/rules.d/85-brltty.rules:ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"
anna@anna-Inspiron-15-3567:~$
Is this the same, or should I look for the device ID?
It’s the same. No worries there.
Edit this file and comment out the line that matches the second line from the grep command:
Add a # symbol to the start of the line.
Once you do that, save the file and then run in Terminal;
udevadm control --reload-rules
This will reload the rules.
Then rerun:
dmesg | grep ch341
ls /dev/*usb*
There should now be a terminal device listed.
If not, try rebooting and retest.
Hurra! It seems tobe working now!
the laser is moving now with the Move panel!
here the output:
anna@anna-Inspiron-15-3567:~$ sudo dmesg | grep ch341
[sudo] password for anna:
[ 25.709170] usbcore: registered new interface driver ch341
[ 25.709554] usbserial: USB Serial support registered for ch341-uart
[ 25.710612] ch341 1-1:1.0: ch341-uart converter detected
[ 25.714275] usb 1-1: ch341-uart converter now attached to ttyUSB0
anna@anna-Inspiron-15-3567:~$ ls /dev/*usb*
ls: cannot open directory '/dev/vboxusb': Permission denied
anna@anna-Inspiron-15-3567:~$ sudo ls /dev/*usb*
001
anna@anna-Inspiron-15-3567:~$
thank you so much! tomorrow I try to do some cuts
That’s great. Hope you get to have some fun now.
I though we went over this … lol
What? No. This one is surely okay or am I missing something?
usb should be USB
Ah… this wouldn’t have occurred to me. It’s been a while since I’ve used Linux as my daily driver. The convention is lowercase for Mac OS which I’ve had more recent exposure to but that explains why nothing was retrieved in this case.
I usually don’t use upper case either, it was a disappointment that lots of these devices set up with all caps addition such as /dev/ttyACM0 and S0 … I think they’re in udev somewhere… I know I modified mine for the Atmel Dragon programmer.
I need to send you a ‘shock collar’ for a little re-training… lol
Well it’s already been demonstrated that apparently i don’t respond well to conditioning but it’s worth a shot.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.