Hi..
Yesterday's image shows date..
DATE-OBS= '1970-01-01T01:22:00' / UTC start date of observation
and a image taken 21/1-16 have a correct date..
DATE-OBS= '2016-01-21T17:11:24' / UTC start date of observation

Br
/Markku

What device was the camera hooked up to. Looks to me like it's the default startup time for a small embedded device that has no clock on board, and it has not updated time from the network.

I have a RaspberryPi in the observatory and time on that was correct yesterday so I don't find the problem there, and the date was correct in all the fitsheaders by any date before.. but I will doublecheck when I'm home again.
Br
/Markku

Well, I maybe have a idea why the fitsheader got wrong date, maybe a failure to resolve with astrometry ??
I could'nt do a new try today because of bad weather but looking at the headers from two different sessions may clear things up.. just a guess..

Here is the last lines I normally get when not resolving with astrometry :
DATE-OBS= '2016-01-21T17:39:05' / UTC start date of observation
COMMENT Generated by INDI
END

Here is from yesterday when astrometry failed a couple of times :
DATE-OBS= '1970-01-01T00:43:09' / UTC start date of observation
COMMENT Generated by INDI
DATE = '2016-01-31T17:16:22' / file creation date (YYYY-MM-DDThh:mm:ss UT)
HISTORY Modified by KStars on 2016-01-31T18:16:22
END

I'll do a new try next time when weather clears up.. so no problem for now

Br
/Markku