KH6M

[YO4DG]

Hello to all !

Unfortunately, Log4OM does not take QRA Locator into account.
Example with the KH6M station operating from Florida, from EL96 locator. In the log it was saved as Hawaii. A friend who uses Logger32 told me that he was saved in the United States, not Hawaii. Maybe this issue will be resolved in the future, to take into account the QRA locator.

Happy holidays and A Happy New Year!

[KI5IO]

Hello to all !

Unfortunately, Log4OM does not take QRA Locator into account.
Example with the KH6M station operating from Florida, from EL96 locator. In the log it was saved as Hawaii. A friend who uses Logger32 told me that he was saved in the United States, not Hawaii. Maybe this issue will be resolved in the future, to take into account the QRA locator.

Happy holidays and A Happy New Year!

Gabi,

KH6M resolves properly in my installation. Are you using the most current version of Log4OM V2? You didn't indicate that in your message. The version ID is located in top left of the Main UI Title Bar. I am using V 2.18.0.0

Your resolutions of callsigns can/will be affected by the settings you have chosen in the Information Providers in Configuration. I've included a screen clip of my current settings for those and I do change them from time to time.

The current programming is working ... it is how you have things configured in your installation.

[YO4DG]

Hi Nolan,

thanks for the reply.
I use the same version of the Log4OM (2.18.0.0 - always I use the latest update) and the settings page, in Configurations, looks exactly like yours.

I observe, if I manually enter the KH6M callsign, shows Hawaii (the Grid box is empty!), but if I manually enter the QRA locator in the Grid box (EL96), then it shows Florida. (maybe need another setting to get Grid when I put the callsign in the main box).



What I forgot to mention is that KH6M was automatically imported, via UDP, from the JTDX program (FT8 mode).
In this situation the QRA locator (EL96) was introduced automatically but the station still in Hawaii shows it to be.
It was needed to do a manual edit to change the DXCC country.

The problem can be verified only if KH6M will be worked with JTDX, and automatically (via UDP) imported to the log.

Best regards and Merry X-mas !

[KI5IO]

Gabi,

Maybe there is a toggle in JTDX that could be switched and impact such data/information transfer?

You could also possibly recheck the JTDX to Log4OM V2 settings in the current User Guide.

Are you using JTDX 'directly' to Log4OM V2 or are you using JTAlert or Gridtracker in the mix as well?

I've not run JTDX in many months, but one/two others on our Alpha team do use JTDX and they might be able to offer an observation as well. I tend to use WSJTx when running FTxx mode.

Thanks for using Log4OM V2 and Merry Christmas to you as well.

[DF5WW]

Hi Nolan,

first of all a merry christmas to you and all other users, think that your answere is on the right way.
Don´t use digitals since 1 year ago (back to the roots) but could be possible that JTDX/WSJT-x sending
a wrong country to Log4OM. If so it will be not overwritten.

My idea is to check the wsjtx.log (think the name is identical in both softwares) to check what country
is logged. If Gabi find out that the wrong country is logged by JTDX/WSJT-X it´s not a Log4OM Problem.
Means he/she has to call the JTDX/WSJT-X owners or the groups of it.

[G4POP]

Could be your using QRZ for lookup but are not a paid subscriber ?

[YO4DG]

Hello to all

Merry X-mas and thanks for answers.

Indeed, I use QRZ lookup and I am not paid subscriber (yet). But a friend of mine using JTDX and Logger32 combination, also not paid subscriber but he don't have this problem.

My lines in JTDX adif log looks like that:

<call:4>KH6M <gridsquare:4>EL96 <mode:3>FT8 <rst_sent:3>-09 <rst_rcvd:3>-19 <qso_date:8>20210401 <time_on:6>050745 <qso_date_off:8>20210401 <time_off:6>050829 <band:3>40m <freq:8>7.075697 <station_callsign:5>YO4DG <my_gridsquare:6>KN43gt <eqsl_qsl_sent:1>Y <eor>

I observe grid EL96 generate by JTDX (in Florida state). So, the problem is not there.

As I said, KH6M was imported from JTDX with correct grid, but DXCC country remain Hawaii in Log4OM. Even when I logged manually KH6M, DXCC country remain Hawaii (see the previously images).

I do not use JTAlert but JTDirect. I put a screenshot with my settings.



Nolan, tell me more about Gridtracker. In my Log4OM is not active.

Best regards !

[G4POP]

Change to HAMQTH or pay QRZ and your problem will probably be resolved

[KI5IO]

Gabi,

Do as Terry has noted a couple times. Change your main source from QRZ to HAMQTH. At least until you sign up for a paid account at QRZ. It will be an alternative test.

As for Gridtracker it is just another APP in the realm of available APPs for the FTxx data modes.

Here are some links:

Gridtracker overview: https://qrznow.com/gridtracker-wsjt-x-or-jtdx-decodes/

Gridtracker website: https://gridtracker.org/

[YO4DG]

Thanks Terry and Nolan

I change to HAMQTH lookup and problem solved !

I will pay QRZ someday to upload qso automatically, but not today.

Best regards and A Happy New Year!