-
|
When using JTDX, the message “Received broken ADIF” appears when logging a contact in the status tab of WLgate. For some reason, the UDP data record does not seem to be compatible—is this a known issue, and can I do anything to fix it? Copying the corresponding record from the ADI file written by JTDX and importing it individually into WaveLog is working without any issue. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
I analyzed what JTDX and WSJT-X is sending via UDP. The following snippets are grabbed from real-world qso´s I made today for comparision (destination callsigns are set to XX1XX): JTDX - NOK:
WSJT-x - OK:
The JTDX data set is slightly longer because it also contains “TX_PWR”. Otherwise, the only difference between the two is the element order and that JTDX sends the field names in uppercase letters. |
Beta Was this translation helpful? Give feedback.
-
|
hi dk5sm. the library we're using at wavelogGate is very picky when it comes to the ADIF-Standard. The Power is defined at the ADIF without the "W" for "Watts". Simply remove it at JDTX and it should work. BTW: You did perfect research! |
Beta Was this translation helpful? Give feedback.
-
|
@int2001 good eye!! I was starring at both adif for minutes without seeing an issue xD
|
Beta Was this translation helpful? Give feedback.
-
|
Fabian, I almost suspected this, but couldn't find the power setting anywhere in the JTDX settings. Solution: I finally removed the “W” from the JTDX.ini (located in the last section [LogQSO]), and then it worked immediately! Just one more comment: in wsjtx_log.adi, the illegal “W” appears in <tx_pwr> in exactly the same way, and although it contains the unauthorized char, I can import these data records using the Wavelog import function (!) without any issue. I guess you use a different parser for this function? By the way, it was an excellent Wavelog demonstration on Saturday at Hamradio. I would have liked to stay for another hour ;-) Thanks so much for your really great work - really appreciated! 73! Stefan, |
Beta Was this translation helpful? Give feedback.
-
|
wavelog itself isn't that picky than the lib used within the gate. however: the "W" shouldn't be part of the TX_PWR. it may produce problems at other software as well. best practice is: no "W" at that field, even if wavelog itself accepts it. PS: Tnx 4 the flowers. it was also great for us to see all those happy hams in the audience! |
Beta Was this translation helpful? Give feedback.
-
|
@dk5sm I'll see if I can parse it in wlgate somehow so it behaves similar to wavelog. Isn't that easy in this case but we'll see |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
hi dk5sm.
the library we're using at wavelogGate is very picky when it comes to the ADIF-Standard.
The Power is defined at the ADIF without the "W" for "Watts". Simply remove it at JDTX and it should work.
BTW: You did perfect research!