Hi,

I understand the you create the job with a given ISO, say 1600, and the manually change it to a different value on the machine. Since the header of a FITS image is just a hash map of texts, I’d think that the job values applies so you see that problem. Did you try to edit the job setting the correct ISO before starting it or create a new job with the correct ISO? If so: is the issue still present?
I use the same camera and never encounter this issue, but I never had the need to set different ISOs for the camera and for Ekos either.

regards

Read More...