Thanks for your kind words Jon. Right now I'm not sure if the light at the end of the tunnel is daylight or an oncoming train. Sam helped me the first time this happened but now he's dumped me over to customer support and I'm very concerned about what I'm hearing. I won't go into everything that they've said, but here is just one example:
"2. Now we think even if you send the camera back to us, we probably won't be able to figure it out.
And replace a camera won't make a difference if we do not find out where the problem is since you have replaced a camera before."
We are still in the middle of the discussion (at least they haven't shut me down yet,) but I believe that they are saying that it's not their problem. They are implying that the problem is with the controlling software, which in my case is MaximDL. I'm still experimenting to try to understand what is going on but the problem may be due to the way that the guiding loop is implemented in MaximDL. Something is going wrong, which causes the temperature control instructions to go into an infinite loop, which of course shuts down the camera. The folks at DL are not well know for customer support but I may have to try to get them to fix it. Otherwise, I may have to switch to another piece of control software like the SkyX or SGP. I'm caught in the middle and it's going to be difficult to find a suitable fix that works with my hardware implementation. Stay tuned and I'll provide an update when I know how to proceed. I've got an all-consuming meeting most of next week so it may take some time to sort out. In the meantime, my telescope only runs for random lengths of time before it hangs. Grabbing maybe 2 subs over an 8 hour stretch of clear, dark skies with excellent seeing is not a very efficient way to gather data. That's what was happening before the roof broke on the alpha observatory a few days ago.
I'm curious...are you cooling the ASI1600?