With the camera connected and cooling down, I watched the temperature dropping as shown on the temp module. I took a f/f image and checked the header. To my surprise it wrongly claimed that the file was not saved to disk (wrong, it was saved) and that it did not contain any fits data - wrong, it does. Is this a new bug in v3? The header data shows temp=0 which is rubbish because it is shown as -18C.
I can report further - but it is not encouraging!
Two nights back I waited for the camera to cool down (ambient 5C down to -18C). Then I waited for twilight to take flats - while taking sample images to monitor the light level. To my great concern, the temp display module showed the temp wandering back up ……! It reached -5C and continued wandering, causing great consternation. I started collecting the flats regardless at the right time while the monitor showed the temp all over the place (anywhere between 2C and -10C). I tried disconnecting the camera and then reconnecting - to cause the cooler to re-activate. It had little effect on the wander.
This morning, I have been looking at the FITS headers. Despite the temp monitor’s display all the temps recorded show -17.6C - -17.8C!
At least the camera is apparently OK even if the SGP temp monitor is now suspect.
Frame and Focus does not populate all of the fits headers. The F&F capture path is a little different than that of Sequence images. The save functionality is there more for troubleshooting so I would not be too surprised if some of the FITs headers are wrong.
As for the “Not saved” message. Yes, that is erroneous. But again because of the flow of the process. Sequence images get saved and then the data displayed on screen. F&F images get displayed and then saved. So the image misses that information. Not saying that’s right…just letting you know why.
Thanks Jared - that does clarify the mystery, although I’m not sure
whether it also affects the camera temperature readings experienced last