Page 1 of 1

Wrong State coming from Log4OM

Posted: 09 Feb 2018, 16:00
by KD0ZV
Trying to figure out where Log4OM pulled wrong data from so I can run down issue. I dont think it happens often but want to make sure I dont have something wrong.

Finally saw a South Dakota "SD" station on 17 meters Ft8. Its the last state I need on 17 meters. I worked him and logged it. I noticed on QRZ it was not showing as worked under SD awards. I checked QRZ log and he was showing as AZ.

So I checked log4om and sure enough it was listed as AZ. JTAlert had it correct at SD.

So what is the lookup sequence as I think Log4OM is pretty intelligent and checks many ways.

Thanks and 73

Rich

Re: Wrong stete coming from Log4OM

Posted: 09 Feb 2018, 16:13
by K7PT
What was the call sign?? Helps if we have all the info.

Re: Wrong State coming from Log4OM

Posted: 09 Feb 2018, 17:23
by KD0ZV
Sorry, should have added that.

K7RE

Rich

Re: Wrong State coming from Log4OM

Posted: 09 Feb 2018, 17:28
by KD0ZV
Might have figured it out.

Just looked at WSJT and it was logged as DM22 which is a AZ grid.

<call:4>K7RE <gridsquare:4>DM22 <mode:3>FT8 <rst_sent:3>+05 <rst_rcvd:3>+10 <qso_date:8>20180209 <time_on:6>153945 <qso_date_off:8>20180209 <time_off:6>154045 <band:3>17m <freq:9>18.101788 <station_callsign:5>KD0ZV <my_gridsquare:6>EN31eq <eor>

Re: Wrong State coming from Log4OM

Posted: 09 Feb 2018, 17:29
by G4POP
kd0zv wrote: 09 Feb 2018, 17:23 Sorry, should have added that.

K7RE

Rich

Well it looks it up as SD using QRZ lookup in Log4OM for me!

Capture.JPG
Capture.JPG (61.53 KiB) Viewed 5293 times

Re: Wrong State coming from Log4OM

Posted: 09 Feb 2018, 17:46
by KD0ZV
Yea me too Terry.

Not sure what information that is used from JTAlrert to Log4OM but appears that JTAlert has state correct but grid wrong. When LOG4OM logged it, it showed as AZ.

Re: Wrong State coming from Log4OM

Posted: 09 Feb 2018, 17:54
by G4POP
kd0zv wrote: 09 Feb 2018, 17:46 Yea me too Terry.

Not sure what information that is used from JTAlrert to Log4OM but appears that JTAlert has state correct but grid wrong. When LOG4OM logged it, it showed as AZ.
Perhaps JTAlert sent the wrong state?

Re: Wrong State coming from Log4OM

Posted: 10 Feb 2018, 00:46
by KD0ZV
Not sure how it happened. JTAlert had him as SD but correct grid in AZ. He is in AZ even though everything online with FCC points to SD.

So log4OM changing it to AZ was correct even though manually entering it into Log4OM still shows SD !

Re: Wrong State coming from Log4OM

Posted: 10 Feb 2018, 22:17
by N6VH
I think this was resolved on the JTAlert list. For those who didn't see it, here's the answer.

K7RE is most likely a snowbird in AZ for the winter. JTAlert wouldn't have that information, only his home state of SD. The grid that JTAlert sent to Log4OM is the grid that K7RE transmitted.

73,

Jim N6VH

Re: Wrong State coming from Log4OM

Posted: 11 Feb 2018, 13:57
by KD0ZV
Thats right. I emailed with him and he is in AZ for sure.