Grid Square logging

[k1io]

First of all, I did look at the manual. It was not clear at all about how to prioritize JTDX/WSJT-X input. I thought "ExternalSource" as Priority 1 might do it, in which case flipping choices 2 and 3 shouldn't matter. But it doesn't. I also did flip 2 and 3 as you suggested (Clublog ahead of CTY) and it STILL ignores the grid square in the CQ and puts JH97 there for D2UY.

So what did I not do? I opened the manual to page 53. I tried multiple arrangements of Info Provider Configuration. I made sure Import QSO from JT Message 12 was checked. I upgraded to the latest beta. It still think I'm working CW (or any other mode that does not provide the grid square, and thus needs the logger to look it up) and it thinks I want the program to guess where the user is, not take the grid square from JTDX Message 12. Log4OM is thus not in sync with the ADI file when the user is not in the grid square that Log4OM's lookup guesses he's in.

[k1io]

BTW I just worked TF1EM. He's in HP94. JTDX logged HP94. Log4OM says he's in IP04. Oops.

[k1io]

Also interesting is that the manual (the edition dated today) shows, on page 55, a somewhat unclear note (commas are your friend!)

PLEASE NOTE
When a QSO is in progress in an external program like WSJT etc the Log4OM lookup is only displayed it is not what is saved when the QSO is completed by the WSJT software sending the QSO via UDP
UNLESS the user elects to update the data received in the QSO sent from the external program in the Program Configuration menu shown below:

Now if I parse that right, I think I am in the "unless" camp, where I want to use the data from the "external program" which I think includes JTDX. In any case, there is a picture of a page showing "UDP Inbound parameters" which are not explained. "Use external data" might be correct in this case. HOWEVER, that whole portion of the page is absent from the latest version (beta) of the program!

Log4OMConnections.png (42.69 KiB) Viewed 1388 times

[G4POP]

BTW I just worked TF1EM. He's in HP94. JTDX logged HP94. Log4OM says he's in IP04. Oops.

But what grid did Log4OM log for the QSO not what is displayed in input window?

[k1io]

Yes, Log4OM logged what was in the QSO manual-input window. Which is correct behavior on SSB and CW. It looked that up somewhere. Which in this case was wrong.

Again, when doing FT modes, you do not enter this yourself and do not want the logger to replace what it is told. I keep Log4OM minimized; it is fed by JTDX. I do not even see the QSO window. I was looking at it this time because I'm trying to debug Log4OM. I don't have enough screen real estate to keep everything open at once.

So while Log4OM does show me what grid square it guessed and saves that, it does not show me the canonical grid square, which is the one from JTDX. It should only look up the grid square if it doesn't get one. And since JTDX usually looks it up itself if it is not provided (as with a / callsign or answering an RR73 when it didn't hear a CQ first), that is rare.

[G4POP]

Did you install beta 2.26.0.03?

[k1io]

Yes, I installed the beta.

[k1io]

What's fairly clear is that either
a) Log4OM is not getting the full ADIF message from JTDX and the grid square is missing (which is very doubtful),
b) Log4OM is prioritizing its own lookup of the callsign over whatever comes in from JTDX, ignoring any settings to the contrary (likely), or
c) The documentation or labeling is very confused and the method of prioritizing input from JTDX is hidden or obscure.

Of course the formal definition of "bug" in software is "undocumented feature".

[ei3grb]

Having the same issues as k1io but I* have given up[ asking for help here or on facebook as I have been treated badly in the past. Not all bad as it saved me pulling the trigger on a 3 figure donation.



"But what grid did Log4OM log for the QSO not what is displayed in input window?"
yes NOT what is displayed in the inp. win.

"UDP Inbound parameters" which are not explained."

Ditto, no such window in screen

VERSION 2.26.0.3

[G4POP]

"But what grid did Log4OM log for the QSO not what is displayed in input window?"
yes NOT what is displayed in the inp. win.

I think this is where the confusion arrises

The grid shown in the normal input window of Log4OM is retrieved from the external source selected by the user (QRZ, HamQTH etc) NOT what is received from the FT software (JTDX, WSJT, Gridtracker etc) its purely a visual display and not saved with the incoming FT QSO

Regardless of what is displayed in the input window its the grid received from the FT software that is/should be logged.

That said there was an earlier release of Log4OM that logged the grid found from the external source (QRZ etc) as shown in the normal input window - Thats why we are so insistant on asking for the version number being used!

"UDP Inbound parameters" which are not explained."

Ditto, no such window in screen

Sorry dont quiet understand this comment please expand