Last night for the first time in a long time I was able to run a virtually flawless PLAN imaging session. I wanted to take advantage of as much as the rare clear moonless night as I could. Because of the various obstructions that limit how long I can view an object, I imaged four different targets before ending my PLAN around 2 AM. Everything went perfectly. The Go To's for each object were all dead on, EAF worked perfectly, the guiding as good as I have ever had. Out of the 70 or so, 5 and 10 minute subs, that were taken of the 4 targets all but just a few were keepers. This is my definition of "As Simple as 1,2,3". :-))))))
My only issue came at the very end of the PLAN session. I had set the ASIAir Pro to turn off the cooling, stop tracking, go to home position, and then shut down. When I checked this morning the mount had NOT returned to the home position........ Instead it was positioned where it was last imaging.
The time stamps in my run log shows that the Go To Home command, and the ASIair Shut Down command, were issued at exactly the same time. Both at 01:58:08. I power my mount from the ASIair so I assume that since the command to Shut Down the ASIair was given at the same moment, as the command to Return to Home, that the mount simply was left powerless in it's last position........ I have noticed this in the past, but I never thought to check my logs to before. When I checked them today as well as some past ones I see that this seems to be ( in may case anyway ) the normal pattern. Both commands are always issued at the same time.
I'm just wondering if anyone else has experienced this? If so, has anyone found some work around so that the final command to shut down the ASIair is not delivered until the mount has had time to reach it's home position? If this is the currently normal sequence of operations perhaps ZWO might consider some programming change here to resolve this minor issue?
Thanks for any help or ideas Al
