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
Wrong State coming from Log4OM
Wrong State coming from Log4OM
Last edited by KD0ZV on 09 Feb 2018, 17:22, edited 1 time in total.
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Wrong stete coming from Log4OM
What was the call sign?? Helps if we have all the info.
K7PT-Chuck "#1 Top of the Honor Roll"
Re: Wrong State coming from Log4OM
Sorry, should have added that.
K7RE
Rich
K7RE
Rich
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Wrong State coming from Log4OM
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>
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>
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Wrong State coming from Log4OM
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.
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.
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
- G4POP
- Log4OM Alpha Team
- Posts: 10807
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Wrong State coming from Log4OM
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 !
So log4OM changing it to AZ was correct even though manually entering it into Log4OM still shows SD !
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team
Re: Wrong State coming from Log4OM
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
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
Thats right. I emailed with him and he is in AZ for sure.
73,
Rich
KD0ZV
Log4OM Alpha Team
Rich
KD0ZV
Log4OM Alpha Team