Hi, having a problem connecting to a brand new machine, never before connected/run.
LAPTOP: Dell Latitude 5550, i5-5200U CPU @ 2.20GHz x 2
OPERATING SYSTEM: Linux Mint 21, Cinnamon 5.4.12, Kernel: 5.15.0-164-generic
APPLICATION: Universal G-Code Sender, Ver. 20251130
Firmware: GRBL (1.1h), Port: ttyUSB0, Baud: 115200/9600
MACHINE: Sainsmart Genmitsu PROVer XL 4030 v2
Computer setup & operated as Single User with full system Permissions and Dialout group membership, ‘Brltty’ file deleted.
PROBLEM: Attempting to connect to machine -
***Connecting to jserialcomm://ttyUSB0: 9600
***Fetching device status
>>>?
***Fetching device status (2 of 10)…
>>>?
.
.
.
***Fetching device status (10 of 10)…
>>>?
***Connection closed
A baud of 9600 or 11500 produces denticle results. Google AI suggested adjusting the ‘connection timeout’, but I cant find the appropriate settings.
Thanks
Dos the host machine/OS see anything on USB0?
What is the output if lsusb?
Hi,
Thanks for your time. Yes, V1 engineering had me run the command “sudo cat /var/log/syslog | grep -i usb”, which returned (excerpt):
Jan 26 08:47:51 user-Latitude-E5550 systemd[1069]: Started VTE child process 1788 launched by gnome-terminal-server process 1763.
Jan 26 08:50:41 user-Latitude-E5550 kernel: [ 233.835331] usb 2-1: new full-speed USB device number 3 using xhci_hcd
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 233.984795] usb 2-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 233.984808] usb 2-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 233.984814] usb 2-1: Product: USB Serial
Jan 26 08:50:42 user-Latitude-E5550 mtp-probe: checking bus 2, device 3: “/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1”
Jan 26 08:50:42 user-Latitude-E5550 mtp-probe: bus: 2, device: 3 was not an MTP device
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 234.009821] usbcore: registered new interface driver usbserial_generic
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 234.009838] usbserial: USB Serial support registered for generic
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 234.012215] usbcore: registered new interface driver ch341
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 234.012693] usbserial: USB Serial support registered for ch341-uart
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 234.012867] ch341 2-1:1.0: ch341-uart converter detected
Jan 26 08:50:42 user-Latitude-E5550 kernel: [ 234.014869] usb 2-1: ch341-uart converter now attached to ttyUSB0
Jan 26 08:50:42 user-Latitude-E5550 mtp-probe: checking bus 2, device 3: “/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1”
Jan 26 08:50:42 user-Latitude-E5550 mtp-probe: bus: 2, device: 3 was not an MTP device
Command “lsusb” returned:
Bus 001 Device 004: ID 1bcf:2b8d Sunplus Innovation Technology Inc. Integrated_Webcam_HD
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 8087:8001 Intel Corp. Integrated Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 002 Device 003: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
/webserial.io/ returned “CONNECTED - CH340 serial converter (1a86:7523)” (Please note the same ID’s)
As you can see it is seeing the ch340 / 341-uart on the USB0 port, but I think without the MT protocol it can’t complete the handshake?
SOLVED: It turns out that communications is disconnected when the Emergency Stop is down and locked, this fact is not mentioned anywhere in readily available documentation. I had the E-stop down as a safety. Thank you for time and assistance.
1 Like