had my first full attempt last night at setting up SGP to automate a quick sequence.
After a few false starts (couldn’t locate PHD Profile etc) I worked out this was a recent bug, and upgraded to 2.4.3beta and PHD2 v2.5.0dev5.
My Setup is an EQ6 Mount, running eqmod, mount hub pro running ascom focuser drivers to a Feathertouch Focuser on a William Optics Megrez 90scope. There is a Pyxis rotator involved, and an SBIG ST11000m camera attached. Guiding is through an external finder guider, and a Lodestar Guide Cam.
I started the sequence on the Helix Nebula. SGP was able to resume the mount from park, slew to target, platesolve to verify and resync using PlateSolve2. From here it rotated the rotator to the correct framing position nominated, and platesolved to verify.
It then started the train sequence in PHD2 - watching from where i was sitting PHD2 did it’s thing - bumped the guide star around and measured it’s movements, verified the directions etc, and locked onto the guide star and started guiding … magic I thought!.
Here is where it all went awry … it cited an error which I neglected to write down (cloudy now so can’t re-verify) but basically implied it was unable to start guiding, and aborted the sequence.
I’m assuming that SGP was waiting for a confirmation command back from PHD2 and wasn’t receiving one.
Can I get a couple of pointers on where best to look - as all started well, but ended quite badly … and I’d dearly love to get SGP out and put it though it’s paces properly …
Please let me know the next steps.