Linux does not connect to CNC

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, Port: ttyUSB0, Baud: 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

Google AI suggested adjusting the ‘connection timeout’, but I cant find the appropriate settings.

Thanks

Baud rate is probably wrong… probably 115,200.

Thanks,

Same problem.

Baud 9600 or 115200, produces the same result.

I’m sure folks here will do their best to assist, but these forums generally focus on machines and controller designed and sold by V1 Engineering.

Having said that, are you sure you’ve got a USB cable that supports data transfer? A lot of cables are “charging only” and don’t have the wires for data transmit and receive. You can use the dmesg command in the Linux terminal to see what USB info is identified when you plug in the device. If you don’t get anything in dmesg, try a different cable.

Edit to add - PROVerXL 4030 V2 Resource Page - SainSmart Resource Center seems to indicate special drivers are needed for Windows and Mac OS to talk to the controller. I don’t know if the controller requires drivers for Linux as well. There’s no mention of Linux on the linked page. You may need to work with the machine’s producer to get things connected.

The Software Setup section on page 26 of the downloadable manual states

Step 2: If it does not recognize automatically select the "Baud” drop down menu and select 115200.

So, start with the dmesg command (or the command posted by @MakerJim which will narrow down the results you have to wade through). If Linux doesn’t see the controller, try a different cable. If it does and still won’t connect, contact SainSmart or Genmitsu vendor support and see what drivers they recommend for Linux.

Second edit - https://genmitsu.s3.us-east-1.amazonaws.com/CH341SER/How_to_Install_CH340_Drivers.pdf does mention Linux Ubuntu and provides links for downloading updated drivers. Doesn’t appear the linux drivers are on the provided USB stick.

I’d start by seeing what Linux sees.

Make sure the cable is not plugged in to the Linux box, then plug it in.

Then use the command below and let’s see what the last few lines tell you about what the Linux kernel saw after you made the connection

sudo cat /var/log/syslog | grep -i  usb

Hi, Tom…

thanks for your time. Yes, it is a high quality heavy gauge USB cable I have used for a printer. It is 12 ft long (the garage is freezing, the adjacent office isn’t) but every now and then I’ll take the laptop out and connect directly to the machine with the cable (with ferrite choke) that came with it. Identical result. I’ve tryed Baud rates of 115200, 9600 & 57600, it trys but wont connect.

Below is an excerpt from the end of the ‘sudo cat…’ command.

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
chris@user-Latitude-E5550:~$

As you can see it is seeing the ch341-uart on the USB0 port, but I think without the MT protocol it can’t complete the handshake?

Time for a SWAG (scientific wild-a$$ guess). A little extra googling show me MTP = Media Type Protocol. Is there an SD card in the device? If not, maybe the driver is expecting to find a file system and giving up when it can’t find it.

Last time I ran into something like this, it was because a chineseum controller had misappropriated the USB VID of a different device rather than go through the minor expense of registering their own. In that case, they copped the VID of an assistive device - a braile reader- and it ws necessary to blacklist the kernel modules for that device before it would function right as a generic UART serial port.

If you can’t connect a terminal program to the ttyUSB0 interface at any baud rate and get a prompt then you’re going to have to figure out what the supplier has done.

I’d walk all available data rates in the terminal program first. You have a bunch of valid rates to try.