Hi.
I using cananalyzer and it’s can’t connect to it.
Not with root not with user not as dialout group.
with screen it works.
Under Windows works.
[ 368.745946] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd
[ 368.852197] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33
[ 368.852271] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 368.852290] usb 1-1.1: Product: USB Serial
[ 368.856992] ch341 1-1.1:1.0: ch341-uart converter detected
[ 368.862415] usb 1-1.1: ch341-uart converter now attached to ttyUSB0
Anybody got this issue nowdays?
Thanks
Do you install drivers?
and autorize chmod +x
What driver is it need and why need +x?
crw-rw---- 1 root dialout 188, 0 Mar 13 03:49 /dev/ttyUSB0
Bus 001 Device 003: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Reinstalled drivers, nothing changed
[ 33.169601] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[ 33.275533] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33
[ 33.275570] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 33.275587] usb 1-1.3: Product: USB Serial
[ 33.348194] usbcore: registered new interface driver usbserial_generic
[ 33.348267] usbserial: USB Serial support registered for generic
[ 33.352937] usbcore: registered new interface driver ch341
[ 33.353059] usbserial: USB Serial support registered for ch341-uart
[ 33.353216] ch341 1-1.3:1.0: ch341-uart converter detected
[ 33.364677] usb 1-1.3: ch341-uart converter now attached to ttyUSB0
I feel like this is something RealDash problem because at CAN Monitor it works. Sometimes timeouts…
@realdashdev
If not sending anything for a while:

on the main dash still getting

Looks like RealDash have timout problem.
Timeout is normal when there is no data from CAN bus for a few seconds.
Don’t know really what the problem could be. We use Seeedstudio CAN adapter on 2M baud on Windows and Linux daily with no issues.
I think it works but gives me bad information. Connecting to /dev/ttyUSB0 (interface) is not same as Waiting Canbus data. I thought there is problem with the interface but not. It’s just waiting for Canbus message.