|
Paul,
this is an "out there" thought but here it is, FWIW.
I have noticed that when I image with Nebulosity and guide with PHD on the same computer, there is always a time during which Nebulosity announced that it is "Not Responding". I think this is usually during download and loading the image in Nebulosity. During that time, it seems that Nebulosity is using pretty well all the clock ticks that the CPU of the computer can provide - i.e. PHD struggles for resources to continue doing what it does for that short interval between subs. Is it possible that the slip occurs during these short periods when guiding is not able to get access to the CPU cycles it needs to send the necessary corrections to the mount and does not resume doing that for sufficient time for the image to slip?
Others with better knowledge of how PHD uses CPU cycles could no doubt tell me I'm barking mad and many who lack that knowledge will probably do so anyway. But what the heck!
peter
|