You beat me to it, I was confused by that too...
Maybe when it’s all up and running use the serial port assistant to set the ports, so it uses the same one each time, it sounds like it’s no and conflicting with another device...also if you are using a proper EQMOD cable, is it one with an FTDI chipset (preferred) or the Prolific chipset ( not preferred )

Hi Chris,
if you are running linux, you can plug your device in and get the vendor and product codes with lsusb.
Use that information to create a udev ruleset as described here:
hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/
You can use a more descriptive port name instead of ttyUSB*
I used the same instructions to connect my HEQ5 via eqmod usb cable and ASI ccd camera via usb 2.

HTH,
Dean

Thanks Astronerd.
Everything works great immediately after I use Serial Port Assistant, until I restart the RPi, then I'm unable to connect. However, if I pull out all the devices, delete all the Serial Port Assistant entries and reallocate then I working again until the next restart.

I'm using a EQmod cable directly to the mount, rather than via the handset. Not sure if it's FTDI or Prolific, or how to tell the difference.

lsusb returns the following

Bus 001 Device 004: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 006: ID 1546:01a7 U-Blox AG
Bus 001 Device 005: ID 0471:0329 Philips (or NXP) SPC 900NC PC Camera / ORITE CCD Webcam(PC370R)
Bus 001 Device 007: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The first entry is the USB-serial adapter connected to the mount.

Thanks, Chris

Don’t recognise that EQMOD cable..
So have to set permanent COM ports for your devices so the same ones are used every time, as it sounds like that is the issue, also try with just one device connected at a time, and restart and if it works try another until you hit the problem on re start, GPS dongles can be troublesome..

Hi Chris,

if you are still having port issues, here is one way to do persistent naming.
I havent tried this on an rpi (mine just arrived in the mail yesterday),
but tried it on two different laptops running ubuntu OS. Note that when lsusb lists connected
devices the ID portion shows productId:vendorId in that order in the form XXXX:YYYY.

*open a terminal on your rpi, change to root user, cd to the udev rules folder, list existing rules
sudo su
cd /etc/udev/rules.d
ls -l

*create a new rules file (eg., 95-cygeqmod.rules) and enter the following line. This should assign your eqmod cable
to be recognized as port /dev/ttyUSB.CYG (CYG for Cygnus, but you can call it anything as long
as it is unique). Based on your lsusb posting:

ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK+="ttyUSB.CYG"

*save the file, unplug your cable, plug it into any usb port and list with lsusb to ensure
the symbolic link works. Try plugging into a different usb port and list. Start up kstars and see
if it recognizes the device. I had the same issue with a conflict between my ASI camera and my eqmod cable:
once unique port names were persistently assigned under udev rules, no more issues. You may notice that
in the rules.d directory, there are other rules placed there by your install of indi/kstars.

further overview of how udev rules works:
linuxconfig.org/tutorial-on-how-to-write...-udev-rules-in-linux

- Dean

Thanks Dean,

I have created a udev rule as you suggest. Trying to connect generates a different error.

Trying to connect from Kstars generates the following...

2019-05-18T15:47:31: [ERROR] Failed to connect to port (/dev/NEQ6). Error: Port failure Error: Inappropriate ioctl for device. Check if device is connected to this port.

After a restart, if I enter ls -l /dev/NEQ6 in the terminal I get
lrwxrwxrwx 1 root root 15 May 18 16:38 /dev/NEQ6 -> bus/usb/001/008

Any more ideas. This is driving me nuts.

Chris

There was an issue in the port mapping quite a while ago, are you on StellarMateOS v1.3.5?

At any rate, if you can wait. SM OS v1.4.0 will be released tomorrow or Monday.

Thanks Jasem,

I'm am using 1.3.5 but I'll wait until 1.4.0 no problem.
It's forecast cloudy the next couple days so no problem.

Chris

can you change your rules file to include
MODE="0666", KERNEL=="ttyUSB*"

you can put it between commas just before the SYMLINK+=

-Dean

Thanks for your suggestions Dean,

This is what I have at the moment...

#EQmod
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", KERNEL="ttyUSB", MODE="0666", SYMLINK+="NEQ6"

Have I made any errors??

Chris

wild card on the ttyUSB ... ttyUSB*
and try "ttyUSB.NEQ6". if you unplug and run lsusb and then plug in and
run lsusb is your puter registering a signal? If so, its not a hardware issue,
its a software issue.

Many many thanks to everyone for all the advice offered. I very much appreciate the support.

I have finally found success!!!
I just need some clear skies and a good target.

I though it would be worth posting with my findings.
After update to StellarMate 1.4.0 I still had no success with the usb-serial connection. In addition, the update seems to have broken the web manager.
So I'm back to 1.3.5 again which is working well.
I have a new USB-Serial cable, this time with a genuine FTDI chip, and this has worked "out of the box". Since it has a different vendor/product ID from my GPS then I don't even have to use the Serial assistant or any UDEV rules.
It would seem that the CP210x chip does not play well with StellarMate.

Hope this info is useful for others.

Chris