Spotting Lookup TO4A WRONG

Need help? - Post here and we will find a solution for you.
Post Reply
WA1SXK
Log4OM Beta Team
Posts: 8
Joined: 09 Apr 2017, 19:53

Spotting Lookup TO4A WRONG

Post by WA1SXK » 18 Feb 2020, 16:22

I have been getting a cluster spot from T04A for days now. Can someone explain what is the Log4om protocol for a spot lookup when a spot is received? I am trying to figure out who I can contact to fix this issue and where the database lookup bug is. I see in the debug trace in Log4om, but can't identify what database does it uses 1st, seems Log4om lookup does not find a internal mapping for the call, then Log4om is going out to QRZ ? for the lookup, QRZ does not find a Prefix lookup for TO4. If you go to QRZ site and type in the TO4A call in full it shows a country listed for this call. There is a blank wanted DX red box (see below) as a country DX alter needed with nothing listed in the country window on the cluster spot, so this might be a log4om bug too, when no country is found, Log4om makes a false wanted DXCC alert.
TO4A IMAGE.JPG
TO4A IMAGE.JPG (27.16 KiB) Viewed 1110 times
Trace log:

2020-02-18 14:01:25.5433 TRACE: Log4OMMainWindow: Validating callsign
2020-02-18 14:01:25.5683 TRACE: Log4OMMainWindow: Callsign match TO4 -> TO4 Outside Country: False
2020-02-18 14:01:26.5984 INFO: QrzComManagement: Begin search for TO4
2020-02-18 14:01:26.5984 DEBUG: QrzComManagement: url https://xmldata.qrz.com/xml/1.27/?s=73b ... ent=Log4OM
2020-02-18 14:01:26.8284 WARN: QrzComManagement: QRZ.COM Lookup error: Not found: TO4
2020-02-18 14:01:26.8284 INFO: Log4OMMainWindow: Updating QSO after QTH Lookup
2020-02-18 14:01:26.8683 INFO: SharedFunctionsManagement: Checking External information. Initial values: DXCC COUNTRY
2020-02-18 14:01:26.8982 INFO: SharedFunctionsManagement: Check Country got
2020-02-18 14:01:26.9282 DEBUG: SharedFunctionsManagement: Clublog zone exception: 0
2020-02-18 14:01:26.9432 DEBUG: DXCCControl: RefreshDXCCCombo CountriesList count is 340
2020-02-18 14:01:26.9432 TRACE: Log4OMMainWindow: Checking worked before status
2020-02-18 14:01:26.9982 TRACE: Log4OMMainWindow: Checking worked before status completed
2020-02-18 14:01:26.9982 DEBUG: Log4OMDataGrid: Initializing grid QSO Lookup
2020-02-18 14:01:27.1832 TRACE: Log4OMMainWindow: Validating callsign
2020-02-18 14:01:27.2132 TRACE: Log4OMMainWindow: Callsign match TO4A -> TO4A Outside Country: False
2020-02-18 14:01:28.2432 INFO: QrzComManagement: Begin search for TO4A
2020-02-18 14:01:28.2432 DEBUG: QrzComManagement: url https://xmldata.qrz.com/xml/1.27/?s=73b ... ent=Log4OM
2020-02-18 14:01:28.2984 TRACE: QrzComManagement: <Callsign xmlns="http://xmldata.qrz.com"><call>TO4A</call><dxcc>227</dxcc><fname>Yuri</fname><name>Onipko</name><addr1>QSL via VE3DZ (QRZ.COM)</addr1><addr2>Martinique</addr2><country>Martinique</country><lat>48.835797</lat><lon>2.351074</lon><grid>JN18eu</grid><ccode>166</ccode><land>France</land><u_views>5108</u_views><moddate>2020-02-04 11:24:36</moddate><eqsl>0</eqsl><cqzone>8</cqzone><ituzone>11</ituzone><user>VE3DZ</user><geoloc>dxcc</geoloc></Callsign><Session xmlns="http://xmldata.qrz.com"><Key>73b47cd445736372545fa2cf25d70a99</Key><Count>91703</Count><SubExp>Thu Dec 10 17:49:02 2020</SubExp><GMTime>Tue Feb 18 14:01:28 2020</GMTime><Remark>cpu: 0.023s</Remark></Session>
2020-02-18 14:01:28.2984 INFO: QrzComManagement: search completed
2020-02-18 14:01:28.3132 INFO: Log4OMMainWindow: Updating QSO after QTH Lookup
2020-02-18 14:01:28.3132 INFO: SharedFunctionsManagement: Checking External information. Initial values: DXCC 227 COUNTRY France
2020-02-18 14:01:28.3282 DEBUG: SharedFunctionsManagement: Clublog zone exception: 0
2020-02-18 14:01:28.3532 TRACE: Log4OMMainWindow: Checking worked before status
2020-02-18 14:01:28.4132 TRACE: Log4OMMainWindow: Checking worked before status completed

User avatar
KD0ZV
Log4OM Alpha Team
Posts: 637
Joined: 04 Mar 2015, 13:42
Location: Ankeny, Iowa
Contact:

Re: Spotting Lookup TO4A WRONG

Post by KD0ZV » 18 Feb 2020, 17:25


WA1SXK
Log4OM Beta Team
Posts: 8
Joined: 09 Apr 2017, 19:53

Re: Spotting Lookup TO4A WRONG

Post by WA1SXK » 22 Feb 2020, 16:31

I don't think you quite understand the problem...I have email alerts going on and was awoken at 0300 with a text about TO4A with a blank country.
The problem is apparently a failed lookup returns DXCC=0 and of course, I have no such DXCC in my log and it triggers a false alert.

Clublog update now shows the TO4A exception but TO4A shows a blank DXCC again. I think this may be because the TO4 prefix is not in country.xml.
Log4OM needs to ignore blank DXCC's for alerts.

Eric

Post Reply