Error on winter time change (Sunday 25 October).

V2 error reports
Post Reply
IU0LFQ
Novice Class
Posts: 4
Joined: 03 Feb 2020, 11:13

Error on winter time change (Sunday 25 October).

Post by IU0LFQ »

Hi,

It seems all log entries between Sunday 25 October 00:00 and 00:59 UTC have been automatically changed (even if the log timezone should be always UTC and not referred to the local OS clock).

In other words, no log entries in the time-frame 00:00-00:59, when the winter time was automatically applied locally, because the logger added one hour automatically.

Example: QSO made on Oct 25 2020 at 00:30 UTC automatically reports 01:30 UTC when saved.
The problem is replicated by deleting the QSOs and importing a corrected ADIF, the logger automatically modifies the entries creating a 1hr gap (please see attached image). Also corrections made by using the single QSO edit dialog are reverted after saving the object.


Could you please share a quick solution (if any) for this problem?

Best73,
-A
Attachments
Log4OM Time Error.JPG
Log4OM Time Error.JPG (18.37 KiB) Viewed 1736 times
User avatar
G4POP
Log4OM Alpha Team
Posts: 10815
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Error on winter time change (Sunday 25 October).

Post by G4POP »

Seems your windows time zone is incorrect
73 Terry G4POP
IU0LFQ
Novice Class
Posts: 4
Joined: 03 Feb 2020, 11:13

Re: Error on winter time change (Sunday 25 October).

Post by IU0LFQ »

Hi,

thanks for your reply - unfortunately this is not the case since my TimeZone in the OS is correct (I double-checked and is correctly set to UTC+01 - Rome) with auto daylight saving adj.

Local (and UTC) time are correctly displayed in the OS clock.

Other loggers installed in the same PC not had this behaviour.

Best,
-A
Post Reply