Funny, that’s what it looked like to me when I noticed it had been waiting for 3+ hours. (I had just woken up, it was around 4am), but my first thought was it looked like the temp had been reset to -35, which was the profile cool down value. I thought I went to sleep with it set to -28 which is really all the 533 would cool down to at that time. I also have seen this behavior in a prev release of 3.1 in December where the when I checked on the sequence midway through the night, it was waiting and this was well after it had acquired many subs, and not after a restart that I did. I don’t know if that was actually the case last night. Because it was a new camera and I “touched” usb devices, Windows in it’s infinite wisdom always re-enables Power Management on USB hubs/devices which is not good cause many hours into the sequence, I noticed that SGP was stuck Downloading a sub. I forgot about the power management stuff. and just tried to restart SGP, and then i couldn’t connect to the focuser, and that’s when i remembered the USB stuff, I forgot to uncheck PM for all the USB devices, and they were all checked, so i disabled them (didn’t reboot) maybe i should have, and then started SGP again and connected everything ok and continued the sequence. So last night I did actually start up SGP after many hours, got things going and went to bed. It may very well had been set to -35 and I ignored it when starting the sequence, but I’m pretty sure I waited till I saw it capturing subs before I left it to go to sleep. I did see a Bad happenings message, it looks like it recovered from losing a guide star a little after 1am, would that restart the sequence?
GNS was running and I didn’t get an alert that it was waiting for temp, maybe that’s a setting I don’t have checked, I didn’t look into that yet.
My question in this thread was in 3.0 and 2.7, temp change would never stop a sequence midway and wait for a temp, at least I never saw it and I have been using SGP for a couple of years. Is there a way to disable this new 3.1 feature?
Here is the log, in case anyone wants to see that.