Hi Larry. The easiest approach is just to use PHD2 for both guiding and dithering, lots of people do that and get excellent results. You’d still use TSX for camera and general mount control as well as planetarium functions. You just need to configure the TSX mount driver according to this document:
https://github.com/OpenPHDGuiding/phd2/wiki/SkyX-Settings
If you’re just getting started, please take a look at the PHD2 Help doc section on Basic Use, especially the Equipment Connection area:
https://openphdguiding.org/manual/?section=Basic_use.htm
Also, you can probably save yourself some time and trouble if you also review the Best Practices document:
https://openphdguiding.org/phd2-best-practices/
Have fun,
Bruce
--
You received this message because you are subscribed to the Google Groups
"Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/57e3ee09-55e6-4d81-8058-1e66ca78acc5%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/602BC29391064D8597EB99D2BCDA7EF4%40HomeDesktop.
https://github.com/OpenPHDGuiding/phd2/wiki/SkyX-Settings
I must turn on Enable Tracking Offsets and pulse drive.
Otherwise it complains that it can't do pulse drive.
It never seems to do direct drive.
This sort of makes sense to me because I remember reading that direct drive was not part of the Ascom mount definition.
I was using a ST402ME and taking darks for the guide images, and 25 15 second frames for the dead pixel and hot pixel removel.
This worked very well. The frames were very clean and I was able to guide through the clouds.
Well, good night, goto roll the roof back on.
I think I'm good to go.
I won't know if dither is working until much later.
Larry
This is a SkyX question. Reasonable, sensible automation/camera control apps – going clear back to MaximDL – have a facility for synchronously running a batch script at various points in the imaging plan. They do this because they understand that people need to use diverse software packages for various purposes and don’t subscribe to the “my way or the highway” model. The imaging app doesn’t know what the script does, it doesn’t matter, but it will wait for the script to complete execution before proceeding with the imaging plan. Whether Software Bisque did this is the question that needs to be answered.
Good luck,
Bruce
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/3e43089d-a52c-4979-acdf-e7b1bd8244b1n%40googlegroups.com.