Log4OM

FURTHER INFORMATION BY WAY OF EDIT.... When I type my own callsign in to Log4OM it shows my grid as QE37 which is incorrect, it should be, as is in qrz, QE38. To confirm this bug, I also typed in VK7AC and his grid is also shown incorrectly by Log4OM
---------------------
EDIT NO 2... I have now reverted back to 2.25.0.0 and edited all todays contacts so that the grids are correct, 2.26.0.0 grids area is a bug for sure

-------------ORIGINAL MESSAGE BELOW ------------------------

I have this morning installed the subject version and immediately noticed that it is no longer displaying nor recording 6 character grids.... All grids are now displaying and recording as only 4 characters.

Personally, I like to record 6 characters for grids....

Regards
John
VK7XX

John,

I am running V 2.26.0 and I entered in your call and vk7ac and I got the proper grid IDs.

I've attached my Information Provider arrangement as that can have a play in how that data is recovered.

My External Source is QRZ.com as well.

Try that arrangement and see if that makes any difference.

Also ... make sure you force an update to the Clublog and Country d/b's.

RE: 4 or 6 digit Grid Squares - Did you accidentally change the Gridsquare length at: Configuration / User Preferences ?? Also there are now two options for either a 4 or 6 digit grid square "column" display in your many/various data grids like the Recent QSO (F7) tab. See image below.

Hi all,

I have the same problem and reviewed my settings but mine was correct and compared with your captures and still happen the same.

Furder more, I use WSJT-X and Gridtracker and until the 2.25.0.0 version this was working perfect when I log any QSO, but not now.

VK7XX wrote: 22 Jan 2023, 19:59 FURTHER INFORMATION BY WAY OF EDIT.... When I type my own callsign in to Log4OM it shows my grid as QE37 which is incorrect, it should be, as is in qrz, QE38. To confirm this bug, I also typed in VK7AC and his grid is also shown incorrectly by Log4OM
---------------------
EDIT NO 2... I have now reverted back to 2.25.0.0 and edited all todays contacts so that the grids are correct, 2.26.0.0 grids area is a bug for sure

John,
Its working fine but I notice your only a 'Ham member' of QRZ not an XML paid subscriber which means that you dont get the locator from QRZ lookup so Log4OM is selecting the 'Country' grig locator

I have this morning installed the subject version and immediately noticed that it is no longer displaying nor recording 6 character grids.... All grids are now displaying and recording as only 4 characters.

Personally, I like to record 6 characters for grids....

Have you got the setting for 6/4 digit grids set correctly - see below

With all the anterior versions the log from WSJT-X store the 6 caracters that I put on it but not now with the new version, so I think that this is not a problem over the external data downloaded by Log4OM but from the storing process and reading data from logging a QSO from other app...

Sorry, I'm not an expert...

well, this beats me. I have reinstalled 2.26.0.0 and double checked all the settings shown above however I still get only 4 characters in the GRID box on the log4om main screen and I still get QE37 instead of QE38 for my own grid. I typed in other known station calls and their displayed grid is also wrong. Once again I revert back to 2.25.0.0 and everything displays correct and records correct. I guess that 2.26.0.0 just does not like me.

John
VK7XX

Trouble solved on logging!!

After all the reviewing the communication port from Gridtracker to log on Log4OM was changed, probably on yesterday when this updated too her program. I don't know why...

Now all the gridsquares are saved with 6 caracters.


Thank you so much and sorry if I have disturbed...

I have same problem incorrect data entered into grid box only shows 4 digits checked config file and all correct. have read all messages and my setup is exactly same but incorrect data being entered into grid box still

just typed in G$POP came up as IO.92

I also had to revert back to the 2.25 version. All of the azimuthal coordinates are inaccurate. Not only the coordinates are incorrect the map also takes you to the wrong state/location. Every call sign I enter gives the wrong coordinates.