Sorry for the delay, been super busy since the COVID lockdowns ended here, world's gone crazy!

I update my model probably no more than once a month and that's on a tripod pier, not a fixed/bolted pier - I image I could potentially go longer without an update. 

The Paramount is a nice box, it's not as cool as a 10Micron or a Planewave L350 direct drive, but it's really amazing for 20+ year old gear (with gears!)

I've been using Voyager recently and it has a the great ability to skip guiding if it can't find a guide star (without bombing the session) and it also has the ability to reacquire the target every N minutes specifically for unguided imaging sessions.

Very nice.


Here's a thought to help us debug this one. Let's trying switching the OTA/cameras around and guide with teh main OTA and use the guide scope as your imager.

Try running the whole thing again and let's see what happens. My guess is that this relates to how DirectGuide deals with commands. I ASSUME (small word, big consequcens) that you're NOT using an ST4 cable?


Glad to hear you're making progress. I seem to recall I had been using internal guiding without problems, but like you, I also stopped using guiding for a variety of reasons.

#1 - using a long local length telescope and an OAG it's still quite hard to find stars for every target, which due to the way EKOS handles errors means that a sequence is abandoned when guiding can't be started (rather than going unguided and capturing the best data it can) WHICH BRINGS ME TO #2
#2 - with mounts like the Paramount ME (and the APs, 10Microns, Planewaves etc) it's generally speaking easier to go without, perhaps with the occasional re-target part way through a sequence just to get back on target

So I've really stopped caring.

Having said that you remind me that I recall a similar issue where the Paramount was guiding fine for quite some time and then "lost its mind", but I can't recall if this was INDI or TheSkyX I was guiding with....


Hey Bob! Great news, the amazing and hard working @knro has updated the Paramount driver to fix a few bugs and minor problems and the dome slaving/pier side bug is now FIXED (I did 2 hours of testing, I could not fault it - perhaps others can!?)

The tracking bug is partially fixed - it's still behaving in a way that doesn't quite make sense to me - I will see if I can characterise the new behaviour, but the good news is that "custom rates" are no longer the default mode when tracking is initiated - it's now switching tracking off that seems to be problematic (or at least the GUI and TSX not keeping in synch).

Another minor glitch with the Home code showing error in teh log is now fixed, making that part one less distraction (and I hope ensures that indi_setprop returns 0 when homed, helpful for creating shutdown and startup scripts.

Keep testing, us Paramount folks need to stick together - especially on Linux/Raspberry Pi as there's not really an alternative automation tool out there that I can see.


Every astro program does it differently - pros and cons - almost all of them are like going from a Toyota with left hand indicators not a Volvo with a right hand indicator stalk - annoying but the way it is (the difference being it's open source if you wanna change it!)

The Ekos approach is that a sequence controls the parameters of the capture (which are often different by target) - that includes the camera temp settings, then Ekos scheduler simply runs the sequences without having to worry about what the mission parameters are for each sequence (that's the sequence designer's job). it's a flawed approach is some cases, but for the general use-case it works pretty well (error handling is a totally different matter and an area where Ekos needs work eg: pause and close shutter if cloudy but restart and reopen when clear, I've not figured out how to make that work).

There is a simple (if slightly annoying) workaround - use the "Indi_setprop" command at the end or start of your sequence to do all teh other things you need. It's a small amount of work, but if you pop it into a shell script, you can design it once and all your sequin eyes can reuse it - if you ever change your mind about the type of cemra etc, it's a simple tweak to one script.