Improper grids stored

V2 error reports
Post Reply
User avatar
K0HB
Old Man
Posts: 239
Joined: 12 Jun 2013, 20:32

Improper grids stored

Post by K0HB »

Starting sometime in January of this year, suddenly it seems that the program is recording improper grids.

Three examples are shown below.

AA3B up to 12/29/2022 is correctly recorded in grid FN20ei. After that date in FM19.
K0AD up to 12/14/2022 is correctly recorded in grid EN35ga. After that date in EN11.
K7SV up to 12/15/2022 is correctly recorded in grid FM18ef. After that date in FM17.

As far as I can tell, all contacts are now being recorded in nearby, but incorrect grids. But see below for a variation on the theme.

Image

Image

Image

FT8 QSO's are correctly recorded. See the CO8NMN records below.

Image
DE Hans, KØHB
--
"Just a boy and his radio"
--
Superstition Trails ----> http://OldSlowHans.com
User avatar
KD0ZV
Log4OM Alpha Team
Posts: 730
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Improper grids stored

Post by KD0ZV »

Hans,

How are the contacts entered in Log4OM on CW. I realize you are having issues with other modes but trying to do some troubleshooting with the team. Are those contacts you have issues entered directly in the Main user interface or have them been imported from ADIF possibly from working a contest with another program?

Rich
73,
Rich
KD0ZV
Log4OM Alpha Team
User avatar
K0HB
Old Man
Posts: 239
Joined: 12 Jun 2013, 20:32

Re: Improper grids stored

Post by K0HB »

The CW QSO's mostly come to Log4OM via UDP from N1MM+.
DE Hans, KØHB
--
"Just a boy and his radio"
--
Superstition Trails ----> http://OldSlowHans.com
User avatar
K0HB
Old Man
Posts: 239
Joined: 12 Jun 2013, 20:32

Re: Improper grids stored

Post by K0HB »

As a test to see if N1MM+ might be introducing the error, I ran a little test.

I looked up on QRZ a call that I've never worked (N2UY) so that Log4OM has no "previously worked" info to harvest from.

From a fresh boot, I launched ONLY Log4OM.

I entered the call N2UY directly (not via UDP) in the data entry box on Log4OM. From the screen clips below you can see that somehow the correct grid is not being gathered by Log4OM. QRZ gives EM48to, and Log4OM displays FN21. All the remaining detail about N2UY seems faithfully copied.

Image

Image
DE Hans, KØHB
--
"Just a boy and his radio"
--
Superstition Trails ----> http://OldSlowHans.com
User avatar
KD0ZV
Log4OM Alpha Team
Posts: 730
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Improper grids stored

Post by KD0ZV »

Thanks for the feedback on this Hans.

Lele has identified the issue with incoming connections and we are testing the final beta release today so we can go public with it. Your direct entry test issue is probably related to your personal Info provider order which we will be resolving as well.

As a work around for now go to your settings>Info Providers>Configuration and set the historic to None in the right column for all three. This will verify you are not picking up bad grid data from a previous QSO. In the left column set Priority 1 to External Source, Priority 2 to Club log and do not use the CTY.

The new version will have a new streamlined connections setup and will be changes with the info providers.

I would expect a release of that soon. You will want to rebuild your incoming connection when that release comes out. Lele has done a really nice job at streamlining that with some presets that should make everything work easier without setup error.

Rich
73,
Rich
KD0ZV
Log4OM Alpha Team
User avatar
K0HB
Old Man
Posts: 239
Joined: 12 Jun 2013, 20:32

Re: Improper grids stored

Post by K0HB »

Thanks, Rich, for the quick work and great communications.
DE Hans, KØHB
--
"Just a boy and his radio"
--
Superstition Trails ----> http://OldSlowHans.com
Post Reply