WSJT-X log time always 00:00:00
Re: WSJT-X log time always 00:00:00
times at 00:00:00 are end qso times, what does the start qso time show??? I don't see that
Re: WSJT-X log time always 00:00:00
Both seem the same.
How can I show you that part that you are asking for not missing anything?
How can I show you that part that you are asking for not missing anything?
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: WSJT-X log time always 00:00:00
if you enable DEBUG MODE in log4om help menu you should be able to see what JT message contains (from program log in help menu) when it's sent to Log4OM...
just send a QSO and check what is contained in the log file, and eventually share that with us
just send a QSO and check what is contained in the log file, and eventually share that with us
Daniele Pistollato - IW3HMH
Re: WSJT-X log time always 00:00:00
Seems like this:
- Attachments
-
- Yeni Resim (1).jpg (130.28 KiB) Viewed 1242 times
-
- Yeni Resim.jpg (128.86 KiB) Viewed 1242 times
Re: WSJT-X log time always 00:00:00
The problem finally seems to be solved,
The issue is probably due to the Turkish version of Windows. Thanks to TA9J (Ismail Cakmak), who found that changing the region type to English ( UK) in time and date settings solved the problem. So far Log4OM takes WSJT-X reports correctly and reports to TQSL without an issue.
The issue is probably due to the Turkish version of Windows. Thanks to TA9J (Ismail Cakmak), who found that changing the region type to English ( UK) in time and date settings solved the problem. So far Log4OM takes WSJT-X reports correctly and reports to TQSL without an issue.
Re: WSJT-X log time always 00:00:00
Fahri,ta2bny wrote: ↑12 Jul 2023, 17:52 The problem finally seems to be solved,
The issue is probably due to the Turkish version of Windows. Thanks to TA9J (Ismail Cakmak), who found that changing the region type to English ( UK) in time and date settings solved the problem. So far Log4OM takes WSJT-X reports correctly and reports to TQSL without an issue.
Tnx for the update. Most appreciated.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX