Alert spotting error

Yes, sometimes it happens... Please report any bugs here
Post Reply
WA1SXK
Log4OM Beta Team
Posts: 8
Joined: 09 Apr 2017, 19:53

Alert spotting error

Post by WA1SXK » 08 Jul 2020, 18:55

I have been getting new DX alerts in Log4om V. 1.40.0.0 with the call sign 4U1A when spotted. Seems the mapping is not finding a country for this call, and LOG4om has no country mapping showing in the alert box, showing only [].
A (0) country should not send out an alert.

Note: QRZ finds this call in Austria, listed as a UN contest station.
Please let me know what the issue is that is causing this alert? Is this a call sign database or mapping issue?
(see attachment for spotting alert.
Regards,
Eric/wa1sxk
4U1A.JPG
4U1A.JPG (118.52 KiB) Viewed 2168 times

User avatar
DF5WW
Log4OM Alpha Team
Posts: 1563
Joined: 02 May 2013, 09:49
Location: Kraam, Rhineland Palatinate, Germany

Re: Alert spotting error

Post by DF5WW » 09 Jul 2020, 06:57

Hello Eric,

not longer using V1 of Log4OM since about 3 month so i can´t check. But please try the latest
1.41 of Log4OM V1. You will find it at the download page. If the error is still the same in 1.4.1
please report again.

;) ;)
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at CG-3000 autotuner, Ailunce HS2 (20W and 5W VHF/UHF) to LPDA´s and different vertical´s ...

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

Re: Alert spotting error

Post by WA1SXK » 11 Jul 2020, 15:08

Hi, Tested version the latest 1.41.0 and the same issue occurs with this call sign when a spot is reported.

Think I found it....QRZ is failing so the country is blank here....I would think in that case you would NOT want to send an alert.

It appears that Log4OM is not renewing the session key.

Source Cluster [Rule: DXCC Log4om]
Callsign: 4U1A
Country []
Spotted on 14003.5 (20m) on mode CW
Note CW 5 dB 38 WPM CQ
2020-07-11 14:43:36.3838 INFO: SharedFunctionsManagement: INTERNET CONNECTION ACTIVE
2020-07-11 14:46:10.6389 INFO: QrzComManagement: Begin search for 4U1A
2020-07-11 14:46:10.8458 WARN: QrzComManagement: QRZ.COM Lookup error: Invalid session key
2020-07-11 14:46:10.8477 INFO: QrzComManagement: Begin search for 4U1A
2020-07-11 14:46:10.8637 INFO: QrzComManagement: Begin logon
2020-07-11 14:46:11.0194 INFO: QrzComManagement: logon completed
2020-07-11 14:46:11.0803 INFO: QrzComManagement: search completed
2020-07-11 14:46:11.0832 INFO: Log4OMMainWindow: Updating QSO after QTH Lookup

The spotting info shows a blank country too.
Callsign: 4U1A
Country []
Spotted on 14003.5 (20m) on mode CW by WZ7I from NA [loc ]
Note: CW 5 dB 38 WPM CQ
Rule Matched: DXCC Log4om
2020-07-11 14:39:06.2033 INFO: #=qPG_ldpcQ64cuHrNLmTZ2PqBXPPpeVxJLd31KxvfXOsg=: Log4OM desk notification sent [7/11/2020 2:39:06 PM UTC]
Source Cluster [Rule: DXCC Log4om]
Callsign: 4U1A
Country []
Spotted on 14003.5 (20m) on mode CW
Attachments
Capture2.JPG
Capture2.JPG (27.57 KiB) Viewed 1572 times

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

Re: Alert spotting error

Post by WA1SXK » 28 Jul 2020, 15:35

Happen again with another special call sign, in Version 1.41.0. There is no country listed in the spotting system, see below photos of the issue. If you need anymore information feel free to let me know
Eric/wa1sxk
Beta tester Lot4om
Capture.JPG
Capture.JPG (29.38 KiB) Viewed 1499 times
Capture2.JPG
Capture2.JPG (21.32 KiB) Viewed 1499 times

Post Reply