Search found 12 matches
- 20 Sep 2023, 14:26
- Forum: Feature suggestions
- Topic: Cluster Email Alert spotter Info.
- Replies: 0
- Views: 17444
Cluster Email Alert spotter Info.
Here in the US, I keep spots open to the entire country, but when I receive a email spot from Log4om, it only shows the spot info, without the REPORTER info. I live in the eastern coast of the USA and it would be very helpful to have a QRZ link to lookup the reporter's location. See EXAMPLE BELOW WI...
- 04 Feb 2022, 18:52
- Forum: Error reports
- Topic: Confirmed QSL Cards not showing correctly
- Replies: 2
- Views: 1885
Re: Confirmed QSL Cards not showing correctly
For my own I changed the confirmation to QSL only and validated to LOTW only. Now all my cards show C in the awards status like I want. The download from LOTW came up with 1129 entries (out of ~7000 QSOS processed from LOTW) that all said Paper QSO found.... What does that mean? I don't see anything...
- 11 Aug 2021, 14:00
- Forum: Error reports
- Topic: Confirmed QSL Cards not showing correctly
- Replies: 2
- Views: 1885
Confirmed QSL Cards not showing correctly
Under the Awards Status/DXCC it seems there is no way to see when you have cards that need to be submitted.
In the image is a 30M entry which only has QSL card received but the view shows Validated instead of Confirmed.
In the image is a 30M entry which only has QSL card received but the view shows Validated instead of Confirmed.
- 02 Apr 2021, 18:33
- Forum: General discussions
- Topic: QSO DATE AND TIME FORMAT
- Replies: 1
- Views: 1146
QSO DATE AND TIME FORMAT
I imported my Log ADIF from V1 to V2 and noticed that my QSO dates and QSO times are now combined under one label called "QSO Date". Is this a new standard that I am not familiar with to combine both the QSO date and time under one label heading all in one column? I find the combined viewi...
- 28 Jul 2020, 15:35
- Forum: Error Reports
- Topic: Alert spotting error
- Replies: 3
- Views: 11652
Re: Alert spotting error
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
Eric/wa1sxk
Beta tester Lot4om
- 11 Jul 2020, 15:08
- Forum: Error Reports
- Topic: Alert spotting error
- Replies: 3
- Views: 11652
Re: Alert spotting error
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. Sourc...
- 08 Jul 2020, 18:55
- Forum: Error Reports
- Topic: Alert spotting error
- Replies: 3
- Views: 11652
Alert spotting error
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 i...
- 22 Feb 2020, 16:31
- Forum: User Support
- Topic: Spotting Lookup TO4A WRONG
- Replies: 2
- Views: 3620
Re: Spotting Lookup TO4A WRONG
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 sh...
- 22 Feb 2020, 16:01
- Forum: User support
- Topic: Prefix lookup fails
- Replies: 1
- Views: 1332
Prefix lookup fails
Started a new V2 database. Tried typing some prefixes and they all failed country lookup. It appears the country xml lookup is not working.
Eric/wa1sxk
Eric/wa1sxk
- 18 Feb 2020, 16:22
- Forum: User Support
- Topic: Spotting Lookup TO4A WRONG
- Replies: 2
- Views: 3620
Spotting Lookup TO4A WRONG
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 iden...