Another xTool D1 Pro that won't connect

I believe the following output will afirm that I have read other posts and how-to’s about connecting the xTool D1 Pro:

myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ groups $USER | grep ‘tty|dialout’
myd0j0 : myd0j0 adm tty dialout cdrom sudo dip plugdev lpadmin lxd sambashare
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ lsusb | grep CH340
Bus 002 Device 008: ID 1a86:7523 QinHeng Electronics CH340 serial converter
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ grep -E ‘1a86:7523’ *.rules
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ ls -1 | grep 1a86:7523
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ ls -1 /dev | grep USB
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ uname -r
6.2.0-36-generic
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$

Can someone point out what is missing now? TIA

Run sudo dmesg with the laser off, then run again after turning on. Can you capture and upload all the messages created after turning on?

Thanks for the quick response!

messages.txt (130.7 KB)

Definitely activity going on… Which is better than none I am guessing. :slight_smile:

This is your problem:

[698011.614603] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input17

It looks like you tried searching for an entry but may have missed it.

Try running grep 1e86 * in the rules.d directory and look for an entry and file that includes that.

Just to double check… you truncated the device id to everything before the colon (‘:’) and advise searching on that. I think your reply may have been a typo because I did not find 1e86, but I did find this:

myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ grep 1e86 *
myd0j0@myd0j0-Satellite-C75D-B:/usr/lib/udev/rules.d$ grep 1a86 *
85-brltty.rules:ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"

That’s the line I commented out and have connected. I ran a framing sequence just to be certain.

Thanks for you help!

Indeed you’re correct. Sorry for the miss.

Glad you were able to work past that and solve the issue!

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