Thanks, Jasem. So should I enter there 'iEQ' or 'indi_ieq_telescope'? I presume that's under Snoop Devices where it currently shows the Simulator?
I am not certain that that is the root of the problem, however, since I also imaged M42 during the same evening session and there the coordinates are stated correctly:
www.dropbox.com/s/1e2dwbi80rdxzq7/M42_Li...-28-23_183.fits?dl=0
Please note in the FITS header that it also lists the 'Telescope Simulator' there.
There must be something else that has happened between imaging the California Nebula (link to FITS file in my first post) and M42 (next target of the evening) that affects how the coordinates are written to the FITS file.
I wonder whether the coordinates of Polaris have carried over somehow from polar alignment which was done just prior to imaging the California Nebula. What I also noticed was that when I was trying to fine adjust the position of the image frame in the dashboard window using the crosshairs to move the center of the image by a few arc minutes to center the nebula that the mount took off and went pointing to Polaris. In both cases the solver had run successfully and positioned the telescope to point towards the California Nebula and M42, respectively, and the correct coordinates were shown in the solver module in both cases. Yet, the coordinates of Polaris where retained in memory when imaging the first target, but no longer when I imaged the second target.
I hope this description helps reproducing the problem. The wrong coordinates are not a problem when stacking and processing the images, but they make it impossible to use a FITS image to precisely center the frame when imaging the same target over multiple nights, which is how I noticed it. The solver invariably fails then for obvious reasons.
Jo