Major INDI Library release v1.9.0 bring significant internal changes championed by @pawel-soja to modernize core INDI Library drivers and clients. New drivers for DeepSkyDad Flat Panel & Pegasus devices plus further improvements to PCM8 drivers.
Your mount will only connect with a baud rate of 115200 (provided you have the version that connects directly with USB) just ensure that this is set in the indi connection GUI rescan and it should pick up the connection and connect. If this still fails remove everything else that is connected and use the camera simulator with your mount in a test profile to ensure nothing confuses the connection and it should see the mount and connect. Then start adding your other gear. Other connection issues can occur if using a non powered USB3 hub. If you are still experiencing problems you will need to post some logs.
I've had issues with the EQ6-R Pro with ttyUSB port mappings. In Linux you can't be guaranteed what a serial USB would be mapped to in the /dev/ttyUSB, which means you can't store in your Ekos profile what serial port the mount is connected to. You should look at creating udev rules but as a Linux newbie I would recommend the StellarMate Serial Port Assistant. If you haven't mapped the ports to a logical thing then do what I used to do: a) have profile not autoconnect, b) launch INDI Manager, c) find a 'scan ports' in a 'Connection' tab and click it, d) find the port you need or make sure you have 'Auto Search' enabled. Before port mapping I had the EQ6-R Pro and my GPS dongle conflicting and I didn't know what serial port what what.
If you do
ls -l /dev/ |grep -i usb
you should get something like (ignore the mappings):
If you see any ttyUSB's then try to found out out which USB port it connects to:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ID 2109:3431 VIA Labs, Inc. Hub
|__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtl88x2bu, 480M
ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
|__ Port 3: Dev 4, If 0, Class=Mass Storage, Driver=uas, 480M
ID 0bc2:231a Seagate RSS LLC Expansion Portable
|__ Port 4: Dev 5, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M
ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P
Here I know the I have my GPS USB in port 4 of the RPI, but it doesn't tell me what ttyUSB it is mapped to but this information is stored in the kernel ring buffer that can be accessed by dmesg
dmesg |grep -i usb
[7.306045] usbcore: registered new interface driver pl2303
[7.306169] usbserial: USB Serial support registered for pl2303
[7.314548] usb 1-1.4: pl2303 converter now attached to ttyUSB0
So I can see that my GPS dongle is mapped to ttyUSB0
You also might have a permissions issue of not being in the correct group to read from the device. From the listing of the /dev from above I do have ttyUSB0, it's owned by root and given to the group uucp (that group is specific to Linux OS you're running) but what you should be able to do is make sure your Linux account is in that group as it might be a permissions
Do groups if the list provided doesn't have the group listed for the ttyUSB then do:
sudo usermod -a -G <group-name> <user-name>
Then if you run groups again then you should see the group listed. If this has been the issue I would suggest rebooting and try again.
RPI 4 B (4Gb) running Manjaro ARM
SkyWatcher Esprit 80ED
ZWO ASI1600MM Pro
PrimaLuceLab Sesto Senso 2