WSJT-X Integration

V2 error reports
Post Reply
TA3AS
Novice Class
Posts: 7
Joined: 04 Nov 2023, 17:03

WSJT-X Integration

Post by TA3AS »

Hi,
This is my first post. I installed LOG4OM yesterday. It is communicating with WSJT-X at 2237 port.
Weird, all of the QSO's time is 00:00:00 . I'm attaching picture. Am I missed something?
LOG4OM ver is 2.29.0.0
WSJT-X ver 2.61 (WSJT-Z Mod V1.33)
Your help will be appreciated.

TA3AS
Attachments
LOG4OM.png
LOG4OM.png (129.75 KiB) Viewed 14079 times
Top
TA3AS
Novice Class
Posts: 7
Joined: 04 Nov 2023, 17:03

Re: WSJT-X Integration

Post by TA3AS »

Hi Again,
I'm attaching a log. As you can see time is 00:00:00

Code: Select all

14:38:34.499 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process started...
14:38:34.51 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] found 1 qso
14:38:34.521 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process completed
14:38:42.326 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER] : Award Management - Parse callsign started on PA3GEG
14:38:42.334 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER - 9 ms] : Award Management - Parse callsign terminated on PA3GEG
14:38:42.492 Info:          [dje_zEHDN3JQDFZ5AUASE2P7SNRFLJVAA_ejd] : [VOACAP] Calculating VOACAP data for JO22
14:38:42.525 Info:        * [dje_zEHDN3JQDFZ5AUASE2P7SNRFLJVAA_ejd][32 ms] : [VOACAP] VOACAP data calculated for JO22
14:39:15.601 Info:          [dje_zYGJVYAU4QW5CJKR8ZRHXJ232K7KA_ejd] : Begin ADIF QSO import
14:39:15.619 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on PA3GEG|11.11.2023 00:00:00|10m|FT8
14:39:15.834 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 215 ms] : Award Management - Parse qso terminated on PA3GEG|11.11.2023 00:00:00|10m|FT8
14:39:15.839 Info:          [dje_zFLNKT3A92LGYUEUF7285229LTF6A_ejd] : [JT MESSAGE] Received JT Message 12 (ADIF) containing  Callsign: PA3GEG Date: 11.11.2023 00:00:00 Band: 10m Mode: FT8 (grid: )
14:39:15.843 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : ############### ADD QSO  Callsign: PA3GEG Date: 11.11.2023 00:00:00 Band: 10m Mode: FT8
14:39:15.866 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on PA3GEG|11.11.2023 00:00:00|10m|FT8
14:39:16.109 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 243 ms] : Award Management - Parse qso terminated on PA3GEG|11.11.2023 00:00:00|10m|FT8
14:39:16.128 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : QSO  Callsign: PA3GEG Date: 11.11.2023 00:00:00 Band: 10m Mode: FT8 Saved
14:39:16.136 Info:          [AdifManagement] : Begin export single QSO to ADIF string
14:39:16.144 Info:          [AdifManagement] : Export QSO to ADIF file completed
14:39:34.734 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process started...
14:39:34.743 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] found 1 qso
14:39:34.749 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process completed
14:40:14.399 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER] : Award Management - Parse callsign started on PD1ADA
14:40:14.407 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER - 8 ms] : Award Management - Parse callsign terminated on PD1ADA
14:40:33.021 Info:          [LogViewerForm] : %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
14:40:33.023 Info:          [LogViewerForm]
14:40:33.026 Info:          [LogViewerForm] : %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
14:40:34.162 Info:          [LogViewerForm] : %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
14:40:34.164 Info:          [LogViewerForm]
14:40:34.167 Info:          [LogViewerForm] : %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
14:40:34.87 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process started...
14:40:34.875 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] found 1 qso
14:40:34.88 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process completed
14:40:45.279 Info:          [dje_zYGJVYAU4QW5CJKR8ZRHXJ232K7KA_ejd] : Begin ADIF QSO import
14:40:45.312 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on PD1ADA|11.11.2023 00:00:00|10m|FT8
14:40:45.525 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 212 ms] : Award Management - Parse qso terminated on PD1ADA|11.11.2023 00:00:00|10m|FT8
14:40:45.528 Info:          [dje_zFLNKT3A92LGYUEUF7285229LTF6A_ejd] : [JT MESSAGE] Received JT Message 12 (ADIF) containing  Callsign: PD1ADA Date: 11.11.2023 00:00:00 Band: 10m Mode: FT8 (grid: )
14:40:45.53 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : ############### ADD QSO  Callsign: PD1ADA Date: 11.11.2023 00:00:00 Band: 10m Mode: FT8
14:40:45.548 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on PD1ADA|11.11.2023 00:00:00|10m|FT8
14:40:45.784 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 236 ms] : Award Management - Parse qso terminated on PD1ADA|11.11.2023 00:00:00|10m|FT8
14:40:45.798 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : QSO  Callsign: PD1ADA Date: 11.11.2023 00:00:00 Band: 10m Mode: FT8 Saved
14:40:45.809 Info:          [AdifManagement] : Begin export single QSO to ADIF string
14:40:45.813 Info:          [AdifManagement] : Export QSO to ADIF file completed
Top
User avatar
KI5IO
Log4OM Alpha Team
Posts: 1807
Joined: 16 Aug 2015, 16:30
Location: Plano, TX

Re: WSJT-X Integration

Post by KI5IO »

Serdar,

This has come up before and was answered in this Forum post:

https://forum.log4om.com/viewtopic.php?t=7505&start=10

It is due to the Turkish version of the Windows O/S.

.
73 - Nolan Kienitz - KI5IO
Plano, TX
Top
TA3AS
Novice Class
Posts: 7
Joined: 04 Nov 2023, 17:03

Re: WSJT-X Integration

Post by TA3AS »

Nolan,
Thank you very much for your great support. I changed the regional setting to US and after it worked.
Where does this problem come from? From Log4OM or WSJT-X?

Code: Select all

17:58:59.539 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER] : Award Management - Parse callsign started on UR4QWW
17:58:59.543 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER - 3 ms] : Award Management - Parse callsign terminated on UR4QWW
17:58:59.693 Info:          [dje_zEHDN3JQDFZ5AUASE2P7SNRFLJVAA_ejd] : [VOACAP] Calculating VOACAP data for KN77
17:58:59.729 Info:        * [dje_zEHDN3JQDFZ5AUASE2P7SNRFLJVAA_ejd][34 ms] : [VOACAP] VOACAP data calculated for KN77
18:00:00.191 Info:          [dje_zYGJVYAU4QW5CJKR8ZRHXJ232K7KA_ejd] : Begin ADIF QSO import
18:00:00.249 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.47 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 220 ms] : Award Management - Parse qso terminated on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.472 Info:          [dje_zFLNKT3A92LGYUEUF7285229LTF6A_ejd] : [JT MESSAGE] Received JT Message 12 (ADIF) containing  Callsign: UR4QWW Date: 11/11/2023 5:58:45 PM Band: 20m Mode: FT8 (grid: KN77)
18:00:00.478 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : ############### ADD QSO  Callsign: UR4QWW Date: 11/11/2023 5:58:45 PM Band: 20m Mode: FT8
18:00:00.5 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.711 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 211 ms] : Award Management - Parse qso terminated on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.733 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : QSO  Callsign: UR4QWW Date: 11/11/2023 5:58:45 PM Band: 20m Mode: FT8 Saved
18:00:00.753 Info:          [AdifManagement] : Begin export single QSO to ADIF string
18:00:00.782 Info:          [AdifManagement] : Export QSO to ADIF file completed
18:00:02.824 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process started...
18:00:02.828 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] found 1 qso
18:00:02.831 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process completed
73!

Serdar
Top
User avatar
KI5IO
Log4OM Alpha Team
Posts: 1807
Joined: 16 Aug 2015, 16:30
Location: Plano, TX

Re: WSJT-X Integration

Post by KI5IO »

TA3AS wrote: ↑11 Nov 2023, 18:07 Nolan,
Thank you very much for your great support. I changed the regional setting to US and after it worked.
Where does this problem come from? From Log4OM or WSJT-X?

Code: Select all

17:58:59.539 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER] : Award Management - Parse callsign started on UR4QWW
17:58:59.543 Info:        * [dje_z7WP55WGMKN4DPAD3WZTFQAMX2NNMYZD9XQ_ejd] [AWARDCALLPARSER - 3 ms] : Award Management - Parse callsign terminated on UR4QWW
17:58:59.693 Info:          [dje_zEHDN3JQDFZ5AUASE2P7SNRFLJVAA_ejd] : [VOACAP] Calculating VOACAP data for KN77
17:58:59.729 Info:        * [dje_zEHDN3JQDFZ5AUASE2P7SNRFLJVAA_ejd][34 ms] : [VOACAP] VOACAP data calculated for KN77
18:00:00.191 Info:          [dje_zYGJVYAU4QW5CJKR8ZRHXJ232K7KA_ejd] : Begin ADIF QSO import
18:00:00.249 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.47 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 220 ms] : Award Management - Parse qso terminated on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.472 Info:          [dje_zFLNKT3A92LGYUEUF7285229LTF6A_ejd] : [JT MESSAGE] Received JT Message 12 (ADIF) containing  Callsign: UR4QWW Date: 11/11/2023 5:58:45 PM Band: 20m Mode: FT8 (grid: KN77)
18:00:00.478 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : ############### ADD QSO  Callsign: UR4QWW Date: 11/11/2023 5:58:45 PM Band: 20m Mode: FT8
18:00:00.5 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER] : Award Management - Parse qso started on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.711 Info:        * [dje_zY7T9MUBS7JTDSXJ7X65P9S77UGCA_ejd] [AWARDPARSER - 211 ms] : Award Management - Parse qso terminated on UR4QWW|11/11/2023 5:58:45 PM|20m|FT8
18:00:00.733 Info:          [dje_zL76SXYXNYVKE3RZR7QZPA_ejd] : QSO  Callsign: UR4QWW Date: 11/11/2023 5:58:45 PM Band: 20m Mode: FT8 Saved
18:00:00.753 Info:          [AdifManagement] : Begin export single QSO to ADIF string
18:00:00.782 Info:          [AdifManagement] : Export QSO to ADIF file completed
18:00:02.824 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process started...
18:00:02.828 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] found 1 qso
18:00:02.831 Info:          [dje_zHNEUQRRJ3W7EXFE3WTGYCEDD9DBA_ejd] : [DELAYED SEND QSO ASYNC] Aligning QSO process completed
73!

Serdar
Sedar,

Windows O/S is the culprit with the Turkish version Windows.

Something between your language and the English translations has a hiccup somewhere.
73 - Nolan Kienitz - KI5IO
Plano, TX
Top
TA3AS
Novice Class
Posts: 7
Joined: 04 Nov 2023, 17:03

Re: WSJT-X Integration

Post by TA3AS »

Hi Nolan,
I tried different logging softwares.
There is no problem on Swisslog, HRD, N1MM, N3FJP AC Log.
So I'm starting to think that the problem lies to Log4OM.
In fact, my windows is English. Region is Turkey only.
I'm attaching a screen capture.
I want to use this great software. Your help will be appreciated.
Best Regards,

Serdar
Attachments
region.png
region.png (102.54 KiB) Viewed 13734 times
Top
User avatar
IW3HMH
Site Admin
Posts: 2927
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:
Contact IW3HMH

Re: WSJT-X Integration

Post by IW3HMH »

Can you enable TRACE MODE in HELP menu and search in the log for the ADIF string coming from WSJT when using your regional settings?
Search for this string in the log to find, nearby, the ADIF string:

"Received inbound UDP message from service"

The expected format for QSO date is defined in the ADIF protocol as:

8 Digits representing a UTC date in YYYYMMDD format, where
YYYY is a 4-Digit year specifier, where 1930 <= YYYY
MM is a 2-Digit month specifier, where 1 <= MM <= 12 [use leading zeroes]
DD is a 2-Digit day specifier, where 1 <= DD <= DaysInMonth(MM) [use leading zeroes]

while the TIME is defined as

6 Digits representing a UTC time in HHMMSS format or 4 Digits representing a time in HHMM format, where
HH is a 2-Digit hour specifier, where 0 <= HH <= 23 [use leading zeroes]
MM is a 2-Digit minute specifier, where 0 <= MM <= 59 [use leading zeroes]
SS is a 2-Digit second specifier, where 0 <= SS <= 59 [use leading zeroes]

There should be no issues on ADIF import...
Daniele Pistollato - IW3HMH
Top
TA3AS
Novice Class
Posts: 7
Joined: 04 Nov 2023, 17:03

Re: WSJT-X Integration

Post by TA3AS »

Hi Daniele,
Thank you for your respones.
I think that the log is what you want.
Best Regards,

Serdar

Code: Select all

023-11-20 10:22:56.8323 DEBUG:       [dje_zXSC6KQQ9JMHCP2W7CFGCQG64FEMA_ejd][MoveNext] : ##### UDP MESSAGE RECEIVED ##### :
                                      ????         WSJT-X    ?`   FT8   YL3ANR   9   FT8   ?  ?   TA3AS   KM38MJ   KO35 ????  ????????   Default   %YL3ANR TA3AS R+09                    
                                       on UDP port 2237 (INCOMING JT MESSAGE/JT_MESSAGE) from 127.0.0.1:62599
                                      ##### 
2023-11-20 10:22:56.8332 TRACE:       [dje_zA4AMTV3K62X8LGB3YLTLFPUMSZU35L233X_ejd][MoveNext] : Received inbound UDP message from service INCOMING JT MESSAGE of type JT_MESSAGE with internal message ID: a2eee3a8-97b9-40a7-8da0-09fcd1ee0878:
                                      ????         WSJT-X    ?`   FT8   YL3ANR   9   FT8   ?  ?   TA3AS   KM38MJ   KO35 ????  ????????   Default   %YL3ANR TA3AS R+09                     
2023-11-20 10:22:56.8332 DEBUG:       [dje_zTR58E9TKEZH7634M6LPUN7JYHKTA_ejd][MoveNext] : ????         WSJT-X    ?`   FT8   YL3ANR   9   FT8   ?  ?   TA3AS   KM38MJ   KO35 ????  ????????   Default   %YL3ANR TA3AS R+09                     
2023-11-20 10:22:56.8342 TRACE:       [dje_zTR58E9TKEZH7634M6LPUN7JYHKTA_ejd][MoveNext] : [JT MESSAGE] {a2eee3a8-97b9-40a7-8da0-09fcd1ee0878} Decoding message from WSJT-X 
2023-11-20 10:22:56.8993 TRACE:       [dje_zBQVXQRKDWUZTZXYMC8HC2_ejd][MoveNext] : Executing planned scheduler... 
2023-11-20 10:22:56.9003 TRACE:       [LogWriter][DumpProcess] : ## DUMP MODULES ## 
2023-11-20 10:22:56.9003 TRACE:       [LogWriter][DumpProcess] : ## DUMP ##SearchCallsign Countries 1 
2023-11-20 10:22:56.9013 TRACE:       [dje_zBQVXQRKDWUZTZXYMC8HC2_ejd][MoveNext] : Planned scheduler executed... 
2023-11-20 10:22:57.1235 DEBUG:       [dje_zXSC6KQQ9JMHCP2W7CFGCQG64FEMA_ejd][MoveNext] : ##### UDP MESSAGE RECEIVED ##### :
                                      ????         WSJT-X:%   
          ?   ~   TA3AS YL3ANR RR73  
                                       on UDP port 2237 (INCOMING JT MESSAGE/JT_MESSAGE) from 127.0.0.1:62599
                                      ##### 
2023-11-20 10:22:57.1245 TRACE:       [dje_zA4AMTV3K62X8LGB3YLTLFPUMSZU35L233X_ejd][MoveNext] : Received inbound UDP message from service INCOMING JT MESSAGE of type JT_MESSAGE with internal message ID: ca059540-042f-4b8a-a0a1-cc53cc852934:
                                      ????         WSJT-X:%   
          ?   ~   TA3AS YL3ANR RR73   
2023-11-20 10:22:57.1255 DEBUG:       [dje_zTR58E9TKEZH7634M6LPUN7JYHKTA_ejd][MoveNext] : ????         WSJT-X:%   
          ?   ~   TA3AS YL3ANR RR73   
2023-11-20 10:22:57.3642 DEBUG:       [dje_zXSC6KQQ9JMHCP2W7CFGCQG64FEMA_ejd][MoveNext] : ##### UDP MESSAGE RECEIVED ##### :
                                      ????         WSJT-X:%   ?????     ?   ~   7Q6M LA7MTA JP77  
                                       on UDP port 2237 (INCOMING JT MESSAGE/JT_MESSAGE) from 127.0.0.1:62599
                                      ##### 
2023-11-20 10:22:57.3642 TRACE:       [dje_zA4AMTV3K62X8LGB3YLTLFPUMSZU35L233X_ejd][MoveNext] : Received inbound UDP message from service INCOMING JT MESSAGE of type JT_MESSAGE with internal message ID: d3aa7e85-1889-4ead-ab50-d9cb5d46e19f:
                                      ????         WSJT-X:%   ?????     ?   ~   7Q6M LA7MTA JP77   
2023-11-20 10:22:57.3652 DEBUG:       [dje_zTR58E9TKEZH7634M6LPUN7JYHKTA_ejd][MoveNext] : ????         WSJT-X:%   ?????     ?   ~   7Q6M LA7MTA JP77   
2023-11-20 10:22:57.4748 DEBUG:       [dje_zXSC6KQQ9JMHCP2W7CFGCQG64FEMA_ejd][MoveNext] : ##### UDP MESSAGE RECEIVED ##### :
                                      ????         WSJT-X:%   
          	c   ~   
CQ ES6DO KO27  
                                       on UDP port 2237 (INCOMING JT MESSAGE/JT_MESSAGE) from 127.0.0.1:62599
                                      ##### 
2023-11-20 10:22:57.4758 TRACE:       [dje_zA4AMTV3K62X8LGB3YLTLFPUMSZU35L233X_ejd][MoveNext] : Received inbound UDP message from service INCOMING JT MESSAGE of type JT_MESSAGE with internal message ID: 0293efe2-b163-44e4-8c79-2585cb086274:
                                      ????         WSJT-X:%   
          	c   ~   
CQ ES6DO KO27   
2023-11-20 10:22:57.4758 DEBUG:       [dje_zTR58E9TKEZH7634M6LPUN7JYHKTA_ejd][MoveNext] : ????         WSJT-X:%   
          	c   ~   
CQ ES6DO KO27   
2023-11-20 10:22:57.5832 DEBUG:       [dje_zXSC6KQQ9JMHCP2W7CFGCQG64FEMA_ejd][MoveNext] : ##### UDP MESSAGE RECEIVED ##### :
                                      ????         WSJT-X:%   ?????     ?   ~   
CQ DO2DC JO31  
                                       on UDP port 2237 (INCOMING JT MESSAGE/JT_MESSAGE) from 127.0.0.1:62599
                                      ##### 
2023-11-20 10:22:57.5832 TRACE:       [dje_zA4AMTV3K62X8LGB3YLTLFPUMSZU35L233X_ejd][MoveNext] : Received inbound UDP message from service INCOMING JT MESSAGE of type JT_MESSAGE with internal message ID: 7e5efcc6-10bd-468f-82be-e4038decee83:
                                      ????         WSJT-X:%   ?????     ?   ~   
CQ DO2DC JO31
Top
TA3AS
Novice Class
Posts: 7
Joined: 04 Nov 2023, 17:03

Re: WSJT-X Integration

Post by TA3AS »

Hi Again,
My region format in windows is like that:
Attachments
region-format-2.png
region-format-2.png (40.8 KiB) Viewed 13689 times
region-format-1.png
region-format-1.png (33.78 KiB) Viewed 13689 times
Top
TA3AS
Novice Class
Posts: 7
Joined: 04 Nov 2023, 17:03

Re: WSJT-X Integration

Post by TA3AS »

Hi Daniele,
It is me again :-)
I logged WSJT-X UDP port with another program. I can log and see Time and date correct.
I logged UDP port while my windows region is Turkish.
There is a small log for your information.

Best Regards,

Serdar

Code: Select all

Listening on UDP port 2333 this machine only
 <call:6>VE3ARF <gridsquare:4>FN25 <mode:3>FT8 <rst_sent:3>-01 <rst_rcvd:3>-17 <qso_date:8>20231122 <time_on:6>125230 <qso_date_off:8>20231122 <time_off:6>125230 <band:3>10m <freq:9>28.076629 <station_callsign:5>TA3AS <my_gridsquare:6>KM38MJ <comment:25>FT8  Sent: -01  Rcvd: -17 <eor>
 <call:4>OG6S <gridsquare:4>KP11 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>-06 <qso_date:8>20231122 <time_on:6>125530 <qso_date_off:8>20231122 <time_off:6>125730 <band:3>10m <freq:9>28.075627 <station_callsign:5>TA3AS <my_gridsquare:6>KM38MJ <comment:25>FT8  Sent: +08  Rcvd: -06 <eor>
 <call:6>PA3HGE <gridsquare:4>JO21 <mode:3>FT8 <rst_sent:3>+12 <rst_rcvd:3>+05 <qso_date:8>20231122 <time_on:6>131000 <qso_date_off:8>20231122 <time_off:6>131000 <band:3>10m <freq:9>28.076883 <station_callsign:5>TA3AS <my_gridsquare:6>KM38MJ <comment:25>FT8  Sent: +12  Rcvd: +05 <eor>
Top
Post Reply

Return to “Error reports”