Hi, I have also this problem how SGP handles UTC and local time conversions in image file data field DATE-LOC.
Here is one SGP log example of one image download:
[09.13.18 00.27.19.962][DEBUG] [Sequence Thread] Collecting FITs headers…
[09.13.18 00.27.19.969][DEBUG] [Sequence Thread] QSI Camera - Camera reports last image start time as: 2018-09-12T21:26:35.850 UTC
[09.13.18 00.27.19.969][DEBUG] [Sequence Thread] DATE-LOC time provided by camera…
[09.13.18 00.27.19.973][DEBUG] [Sequence Thread] GatherFitsHeaders: Writing header info from UI…
[09.13.18 00.27.19.977][DEBUG] [Sequence Thread] Clearing timed monitoring events…
[09.13.18 00.27.19.984][DEBUG] [Sequence Thread] Created full file name (file does not exist): D:\Astro\QSI\2018-09-13\Light\Alpheratz_30sec_1x1_G_frame1.fit
Timedates in brackets are actual local times (EEST=UTC+3).
And here is the information in FITS-file header after SGP has generated and saved it:
OBJECT = ‘Alpheratz’ / Object name
DATE-LOC= ‘2018-09-12T21:26:35’ / Local observation date
DATE-OBS= ‘2018-09-12T18:26:35’ / UTC observation date
IMAGETYP= 'LIGHT ’ / Type of frame
CREATOR = ‘Sequence Generator Pro v126.96.36.199’ / Capture software
My camera QSI690 define the unit of image DATE-LOC timestamp as UTC, but SGP uses this UTC timestamp as local time. Then SGP convert this already UTC timestamp again to UTC in field DATE-OBS which is error.
Is this bug in SGP how it take into account the UTC unit information in the “Camera image start time”/DATE-LOC data field ?
Or is this bug in QSI690 because it is using DATE-LOC timedate field as UTC, although defining it’s unit is UTC ?