ESP connection problem with linux

Support
1 
meshtastic --info
Traceback (most recent call last):
  File "/usr/local/bin/meshtastic", line 8, in <module>
    sys.exit(main())
  File "/home/tomasz/.local/lib/python3.9/site-packages/meshtastic/__main__.py", line 933, in main
    common()
  File "/home/tomasz/.local/lib/python3.9/site-packages/meshtastic/__main__.py", line 709, in common
    client = meshtastic.serial_interface.SerialInterface(args.port, debugOut=logfile, noProto=args.noproto)
  File "/home/tomasz/.local/lib/python3.9/site-packages/meshtastic/serial_interface.py", line 57, in __init__
    StreamInterface.__init__(self, debugOut=debugOut, noProto=noProto, connectNow=connectNow)
  File "/home/tomasz/.local/lib/python3.9/site-packages/meshtastic/stream_interface.py", line 50, in __init__
    self.connect()
  File "/home/tomasz/.local/lib/python3.9/site-packages/meshtastic/stream_interface.py", line 74, in connect
    self._waitConnected()
  File "/home/tomasz/.local/lib/python3.9/site-packages/meshtastic/mesh_interface.py", line 402, in _waitConnected
    raise Exception("Timed out waiting for connection completion")
Exception: Timed out waiting for connection completio

Can anyone help me and possibly paste some links how to get started?

2

Maybe user had no rights to access usb ports.
Searching for the combination ’ usb rights user ’ may help you.

https://www.xmodulo.com/change-usb-device-permission-linux.html

3

Unfortunately, after doing the action, I still don’t have the last option as read / write:

ls -al /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 04-25 11:55 /dev/ttyUSB0
4

sudo adduser $USER dialout

Logout or reboot after

5

The user “tomasz” is already a member of the “dialout” group.

1 Like
6

Check if you use a good USB cable. Try another one.

7

I was able to flash ESP with this cable, so I don’t think it is broken.

Picocom said:

sd$ܟ|�l�|

         �
          l�
            c|����{�c�
                      #��'o�dog���
                                  bx�l{lsd�r��g�c�'c8�

So I conclude that ESP works and communication is there too.

8

Sorry to post under the post, but I changed the software and it didn’t change anything.

9

Different cable - no difference

10

Do a ‘lsusb’ command in a monitor window.
First WITHOUT the node and right after that WITH the node.

The difference is the usb chip in the node.
Maybe you need another driver for that chip ?

It’s also possible you did not follow the instructions like explained here.

I had difficulties on an older linux laptop to get the meshtastic client running well.
The problem was with python and had to install several python stuff before it worked.
I cannot remember exact what I had to install but every time I got some clues from error-messages in the terminal window about what was missing.

11

There was no module on one cable, on the other (what I was uploading the firmware):

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

So the cable is OK.
I am also convinced that it is the fault of softwarre, but I do not know python so that I know what is wrong with it.