Rather, I think it was introduced by the latest INDI, Previously, all devices connected without issue.

Unfortunately, the workaround mentioned here:
indilib.org/support/tutorials/157-persis...al-port-mapping.html
doesn't work.

My workaround is currently to plug in the usb cables one at a time -the mount must be the first connected- and hit connect for each device on the indi control panel. This is the only reliable way I can connect our eq6. Not elegant, but may help rescue a session.

If the devs need anything testing or if we could revert this section of the code to the stable version immediately before 3.5.3, please don't hesitate to ask.
Cheers and clear skies,
Steve


 

cat 99-observatory.rules
#EqmodMount
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="PGB1MMQ", MODE="0666", SYMLINK+="mount"

ls -l /dev/mount
lrwxrwxrwx 1 root root 15 jun 15 14:44 /dev/mount -> bus/usb/003/003

indi screenshot attached
TIA
 

[2021-06-15T14:55:53.109 CEST DEBG ][           org.kde.kstars.indi] - CCD Simulator : "[DEBUG] Toggle Debug Level -- Driver Debug "
[2021-06-15T14:55:53.112 CEST DEBG ][           org.kde.kstars.ekos] - "EQMod Mount"  is disconnected.
[2021-06-15T14:55:53.083 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2021-06-15T12:55:52: Client 9: new arrival from 127.0.0.1:34518 - welcome!"
[2021-06-15T14:55:53.083 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2021-06-15T12:55:53: Driver indi_simulator_ccd: snooping on EQMod Mount.EQUATORIAL_EOD_COORD"
[2021-06-15T14:55:53.083 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2021-06-15T12:55:53: Driver indi_simulator_ccd: snooping on EQMod Mount.TELESCOPE_INFO"
[2021-06-15T14:55:53.083 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  "2021-06-15T12:55:53: Driver indi_simulator_ccd: snooping on EQMod Mount.GEOGRAPHIC_COORD"
[2021-06-15T14:55:53.083 CEST DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2021-06-15T14:55:53.108 CEST INFO ][           org.kde.kstars.indi] - EQMod Mount :  "[ERROR] Failed to connect to port (/dev/serial/by-id/usb-Pegasus_Astro_EQDIR_v.1.2_PGB1MMQ-if00-port0). Error: Port failure Error: Not a directory. Check if device is connected to
[2021-06-15T14:55:53.113 CEST INFO ][           org.kde.kstars.ekos] - "EQMod Mount failed to connect.\nPlease ensure the device is connected and powered on."

Thanks Steve, I was certain there was an issue here. I have played with udev rules but probably got the syntax wrong since the ttyUSBx permissions came out wrong. with your example I can most likely make it work. In frustration I removed the astroberry Pi this morning and have reverted to USB + Windows until I get this fixed.

However this is just a work around.  The issue needs a proper and definitive fix.  I saw that modemmanager grabbed ttyUSB0 as soon as it was created by plugging in my mount and then it seemed that gpsd enter the arena.  Reluctantly I removed the gpsd file from /etc/init.d but it still did not fix this issue.  I think it likely that this may well be a Raspberry Pi only problem since I know others who run Linux on other platforms and they do not seem to have this problem.

Question: Is there a command I can issue that will return the currently installed indi library? I think I have installed 1.9.0 but I'd like that confirmed. What's the magic command please?

Hi
Not just a pi issue. This is with Ubuntu 20.04 on a Dell laptop. Same symptoms. The connection sometimes works, sometimes doesn't.

eqmod only. All other hardware connects fine first time..

To find the indi version just issue: indiserver
Cheers

Even with the workaround suggested by Steve, plugging thinks in one at a time, mine still does not work, I plug the mount in, and it’s connects, then the Pegasus UPB this does not connect and the mount then disconnected and neither will work, also I normally have the mount plugged into the UPB, but that is not an issue if I could get them both to connect….
The  mount connects to USB0 then the UPB searches USB1 can’t connect so try’s USB0 which is already being used, this then causes the mount to disconnect and back to square 1….
so have had to ditch the Mount EQMOD cable and use the Bluetooth dongle as that works, as it connects to rfcomm0 and the UPB connects to USB0…and all good…. No idea why this has happened as all was good three days ago before latest updates….

@Steve, Whilst I hate these kind of bugs, in a way I am glad it is not just a Raspberry Pi problem. It now means that devs can use almost any architecture to find the problem. Thanks for the update.

@astronerd, I am using astroberry on a Pi4/8GB. Mine too used tp connect. Now it NEVER does no matter what I do.

I am sure a fix will come. These guys are good and know what they are about.

Pete

@pete
same set up as me, I also have Stellarmate and it’s the same on that too, and the serial port mapper does not work on there anymore, so can’t even use that…..

So it's a bug then. Trust me a a neophyte astroberry user to trip right over it. AT least the bug is now out in the open and nobody is saying it is a user error. For that alone I am pleased.

On a related subject I issued "indiserver" and it says that I have "INDI Library: 1.8.9" I did "sudo apt upgrade && sudo apt update" and I still have 1.8.9. How can I get to 1.9.0 please?

Thanks again.
Pete

Hi everyone
I tested with the newest versions and working OK with the latest git:

~/Projects/indi$ git log
commit e5494e1c868720e1aa6451b74ab2c6aaba3bb831

~/Projects/indi-3rdparty$ git log
commit b77182ffc13372446d855bc8f42859648ad1793e

~/Projects/kstars$ git log
commit 286aea8cf8ad1a1981d2c6a404489bb0a23b2c6e

So you don't have to build everything, as well as the latest kstars, I tested with the stable kstars and the indi from git. Still worked OK.
HTH

@pete, you can’t using those commands until @radek upgrades the Astroberry PPA on his side….you will have to build INdI from source for the very latest…

Ha! I though that is what you would say. I think I shall wait until radek updates the files. I cannot use astroberry with my rig right now anyway so I may as well wait for the fik and then new files. This is not a problem. Thank you for telling me. I have a LOT to learn here.

Pete