It turns out there was a bug in the INDI Paramount driver, which would have affected even internal guiding with Ekos. I've updated the code to fix the bug:


I've been using Kstars/Ekos/INDI/PHD2 for a while with a Celestron CGX, and have just upgraded to a Paramount MX+.  I'm running Kstars 3.5.3 with PHD 2.6.9dev5 on Ubuntu 20, connecting to TheSkyX 10.5.0 (Build 12846) via TCP at the loopback address

Slewing works great, and it's been a seamless transition in general.  I've been able to successfully connect, calibrate and "sort of" guide.  

My problem is that PHD2 guiding feels glacial - and doesn't work that well.  Previously with the CGX, I had been able to guide with as short as 0.5s exposures and everything felt snappy.  With the Paramount via indi_paramount_telescope, even with 3s exposures, it seems like there's an extra second or two added between imaging, guiding and update activities, and sometimes updates come in bursts.  I tried updating the polling frequency to the mount (vs 0.5s then 0.25s) but that doesn't seem to make a difference.

Has anyone else experienced this problem?  I'd invest time in getting TSX guiding working, but it doesn't help with an automation workflow on Linux.


A followup to my post - upon connecting my Mac to a remote INDI session to the Ubuntu host (which is connected to the PPBA), the Mac instance of INDI connects the (remote) PPBA just fine. I did a ~4 hour session last night, with auto-dew heaters enabled, and everything seems to work as expect.

One item I don't recall seeing is the ability to control each of the 4 individual 12V ports, but will look again when I get back to my scope.


I see that Pegasus PPBA (indi_pegasus_ppba) v1.0 has been released in indi-full/focal 1.8.6~202007201351~ubuntu20.04.1

Unfortunately, I get a serial time-out error when trying to connect at 9600 baud with both of the available serial ports.

usbdevices on ubuntu sees this:

T: Bus=01 Lev=02 Prnt=09 Port=00 Cnt=01 Dev#= 10 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0403 ProdID=6015 Rev=10.00
S: Manufacturer=Pegasus Astro
S: Product=PPBADV revA
S: SerialNumber=PPBA4PSI91
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=90mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio


lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
|__ Port 4: Dev 6, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M
|__ Port 4: Dev 9, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 11, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 10, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M

The two attached ZWO cameras connect with no problems, but the driver attempts to connect to /dev/ttyUSB0 and immediately gets a Serial read error: Timeout error, and then trys /dev/ttyUSB1 and hangs. I don't seem to be able to input any other device paths, and the scan ports doesn't produce any alternatives.



I recently migrated to a Celestron CGX from an Orion ATLAS EQ-G via EQMOD, and am struggling with understanding the Celestron CGX driver.
I believe I am using "indi_celestron_gps" version 3.2 interface 5 as selected when I choose "Celestron CGX" from the mount time.

1) There appears no way to connect directly to the mount - you MUST connect via the hand controller USB. This would appear to be a limitation imposed by Celestron, and no one has cracked the proprietary mount USB yet.

2) The mount appears to be implementing some kind of hard-coded backlash compensation - every GOTO, no matter how small, or in what direction, results in the mount slewing away from the current position, and re-approaching it from the lower left in both axes. I can not find any parameters to tune or disable this. In Kstars/Ekos, this is especially annoying on Capture & Solve -> Slew to Target mode, as it requires about 6.5 seconds to do this dance in order to "settle" for the next try, and this technique still fails to completely solve mount model problems that the EQ5-G had in small moves through backlash.

3) There appears to be no way to slew to a position and "STOP". Slew / GOTO always results in entering "TRACK" mode regardless of whether it is to to "TRACK, SLEW, or SYNC" in the "On Set" INDI dialog. This has made manual points (for example, in surveying my horizon for creation of a horizon mask) more intensive, as I always have to tell it to manually STOP tracking.

Is there a better resource for documentation / setup than here (which does not yet mention the CGX in supported mounts)


I'm new to EKOS/INDI and have been thoroughly enjoying it with my AstroBerry configuration out at the scope, while I sit comfortably inside the house.

When I set up for the evening, I do a lot of my work on the laptop - close to the scope. However, once its set up, I like to transition to my iMac desktop.

Are there recommendations on synchronizing the configuration between two locations (iMac/Macbook)?

I tried a symlink in the ~/Library/Application Support/kstars folder to a common dropbox folder, but kstars does not appear to follow the sym link.

When I initially started using EKOS/INDI with the AstroBerry, my assumption was that all the configuration would be stored on it because its connected directly to the scope, but INDI appears to network well enough that I guess that doesn't matter.

Thanks for any suggestions!