Sorry if I'm stating the obvious, but I see it's trying to connect at 9600 baud. Did you try 115200 baud?

@kevin,
the correct baud rate is 9600, for EQMOD, unless you are connecting with a direct USB port on the mount…then it’s the higher one….

A simple diagnostic step is to open miniterm on the correct tty port, and type the following:

:e1

and press enter. You won't be able to see what you're typing, this is normal. This is just a simple command to query the firmware version. On my system, it responds with:

=030723

If you get back some type of response like the above, then you know communication is working.

It’s no using a tty port, this I think is the issue, it’s using a “by ID” port name, this has changed recently….they used to connect with tty ports…..

Yes, those are normally symlinks back to the /dev/ttyUSBx device names. I believe INDI switched to using these "by-id" names because those names are theoretically more stable than the /dev/ttyUSBx names.

I see this error:

EQMod Mount : "[ERROR] Failed to connect to port (/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AM00M7QG-if00-port0). Error: Port failure Error: No such file or directory. Check if device is connected to this port. "

What files do you actually have in /dev/serial/by-id? They will be symlinks. Do the device files that they point to actually exist?

No, there is only one there for the Pegasus hub, but I think they are only created at first connect, this have never connected….

Those files in /dev/serial/by-id are created by the kernel, and should be created as soon as you plug in the device.

Are there any messages in dmesg when plugging in the cable, either errors or any kind of status indication?

Oh, one more thought. There was a bug in Raspbian, which was resolved a few months ago, where serial devices plugged into a USB hub would cause problems like this. Plugging all the serial devices (mount, Pegasus hub) into the ports on the Pi instead of a hub was the solution. Just wondering if you're running an old version of Raspbian with this bug still present.

Well, this started when I moved to a Bluetooth EQMOD adapter and it worked well, but I did notice a bit of lag, so moved back to the EQMOD cable, now this cable had worked before without issue, and there was a file in the /dev/by ID folder for this from when it worked, but now it had stopped working and I thought it was the cable after days of trying.
So I bought a new one, and this does not work either, but also has never been connected as of yet. I deleted the current “by ID” file and there has not been a new one created from the new cable, but as you can see it does show an ID in the INdI panel, but just will not connect.
both cables work on windows with Ascom no problem 

I have latest “sudo apt update && sudo apt dist-upgrade” so will assume I have latest kernel..
also my cable is plugged directly into the RPI

BTW your help is much appreciated
 

Go to a terminal and type "dmesg". That will show you a log of kernel messages. Unplugging and plugging the cable should cause some messages to get added. For example:


The first few lines happened when I unplugged my mount. The following lines were added when I plugged it back in.

Ok, will try this in the morning, cheers… 

Ok, tried the dmseg, and it does show the port as you say it’s trying to connect to ttyUSB0
so tried that in the port box but still no good…
it says port in use by another device, so tried ttyUSB1 and same, yet there are only two devices and ports found….