SGPro v2.4 - 2773
PHD2, v2.4.1i - r1594
I snuck in some imaging last night between the clouds. Four observations from the session:
The second target (NGC3718) failed initially to “center on”. The first time it got to step 4, failed, and attempted to abort. This was around 1:14am. I instructed it to run sequence and it failed at step 2. After 3 or 4 attempts, it succeeded (I think around 1:26am) and moved on to imaging the target.
During the failures, the target was right where it should have been. No clouds, no dew. Guiding picked up once SGPro successfully centered.
Autofocus was set to operate with a filter change. Autofocus filter is Lum. Autofocus did not actuate between the first target (NGC2903, Ha) and the second (NGC3718, Lum). This was slightly after the 1:14am time mentioned above.
I saw no settling time for the first image of NGC3718. It appeared that imaging started immediately even though the PHD2 guiding was reporting values substantially above my 1.0 preset. Something is going on around 1:26:40am.
Telescope is set to stop tracking when sequence completes. Last night was the second time that feature was used and it works like a champ. However, both times I’ve found that the dome is no longer slaved to the scope. This is true even though both show to still be “connected” and “slaved” in SGPro. Not a problem, just curious.
Drop box attached with logs, sequence, etc. Any and all comments are appreciated.
12" LX200 Classic, 2182mm (f/7.16)
Atik 383L+ mono camera, Atik EFW2 filter wheel
SX Lodestar guide camera, 1091mm (f/3.58)
Starizona MicroTouch for FT focuser
Starizona SCT corrector