|
New POTA Watch v25.1 posted.
POTA Watch v25.1 is posted and ready for download in the Files > Program Files section of this forum.
Thanks to Tony, NY2A, we found that POTA Watch was not logging frequency when using N3FJP's AC Log. This is now fixed.
While doing the above fix, it was discovered that the program was sending spots even if Auto-Spot was not selected in options, so this is fixed as well.
The Auto-spot thing is kind of critical, so please update to v25.1 if you're using POTA Watch.
?
As always, please report any problems or concerns.
Wishing you all the best in the New Year!
73,
Ed - W4ELP |
|
Re: Is there an issue with lookup today?
I think that means you're not getting a response from qrz, or your virus program is preventing Lookup from writing the data file. Make sure your qrz subscription hasn't expired. Also temporarily turn off your anti virus. Another thought is make sure your internet connection is ok. On Sun, Dec 15, 2024, 7:22?PM David-WB2HTO via <WB2HTO=[email protected]> wrote:
|
|
Re: QRZ Login Issue for Callsign Lookup in POTA Watch Version 25
¿ªÔÆÌåÓýTry using the Event viewer in windows.? If it is a permission issue it will show up. ? From: [email protected] <[email protected]>
On Behalf Of Dave Hamm, K4EET via groups.io
Sent: Wednesday, December 4, 2024 8:22 PM To: [email protected] Subject: Re: [W4ELP] QRZ Login Issue for Callsign Lookup in POTA Watch Version 25 ? Hi Ed, ? Well, I disabled everything in the anti-virus, firewall, and malware realms and I am still getting the same error dialogs. Must be something on my end with this new Dell XPS17 laptop running Microsoft Windows 11 Pro. I am going to do some troubleshooting to see what might be amiss here. Things worked fine on the old Dell XPS8700 desktop running Microsoft Windows 10 Home. Unfortunately that computer is currently not working. That is on the fix-it list too. I'll keep you posted about anything that I find amiss causing these error dialogs. For now, this issue seems to be caused by something on my end. I'll figure it out. Go back to writing your awesome software and don't spend any more time on this until I have a chance to thoroughly analyze my system. ? Thanks again for your time and assistance. Have a very Merry CHRISTmas if I don't post anything before then. ? 73, Dave K4EET |
|
Re: QRZ Login Issue for Callsign Lookup in POTA Watch Version 25
Hi Ed,
?
Well, I disabled everything in the anti-virus, firewall, and malware realms and I am still getting the same error dialogs. Must be something on my end with this new Dell XPS17 laptop running Microsoft Windows 11 Pro. I am going to do some troubleshooting to see what might be amiss here. Things worked fine on the old Dell XPS8700 desktop running Microsoft Windows 10 Home. Unfortunately that computer is currently not working. That is on the fix-it list too. I'll keep you posted about anything that I find amiss causing these error dialogs. For now, this issue seems to be caused by something on my end. I'll figure it out. Go back to writing your awesome software and don't spend any more time on this until I have a chance to thoroughly analyze my system.
?
Thanks again for your time and assistance. Have a very Merry CHRISTmas if I don't post anything before then.
?
73, Dave K4EET |
|
Re: QRZ Login Issue for Callsign Lookup in POTA Watch Version 25
Thanks Ed. I¡¯ll do some checking with Microsoft Defender and Norton 360. Defender should be turned off. I¡¯ll disable all of the antivirus, malware, etc. apps after we finish dinner and let you know the results later tonight. Thanks again and have a nice evening!
?
73, Dave K4EET |
|
Re: QRZ Login Issue for Callsign Lookup in POTA Watch Version 25
From what you described, it sounds like Windows Defender is causing the problem.
The 3 programs should be identical in the way they log into QRZ.?
1. A request is sent to QRZ for a session ID, using your QRZ ID and password
2. QRZ responds with a unique "session key". This response is saved in a file (same folder as the program) called SessionID.xml.
3. The program reads the file and uses the session key when doing a callsign lookup.
4. Lookup data is stored in a file called LookupData.xml.
?
T|he session ID is good for one hour, as I recall, so the program automatically requests a new one about every 50 minutes or so.
Check the setup menu on each of the programs and make sure your QRZ ID and password are being saved, along with other settings. Your virus program may be preventing writing files.
Check the program files for each of the programs and see if the SessionID.xml and/or LookupData.xml files are present, with a current date and time.
You can try temporarily turning off your virus program, then restart the W4ELP programs and see what happens.?
73,
Ed - W4ELP |
|
Re: QRZ Login Issue for Callsign Lookup in POTA Watch Version 25
Hi Ed,
?
Sorry about the delay in responding. My new Dell laptop had a Blue Screen crash for some reason just before I was ready to send the reply. I lost everything I wrote. Here is what I said...
?
1. With QRZ 2FA disabled, I still get the same three error dialogs.
?
2. In starting W4ELP Lookup Version 9.18, I get the same ERROR dialog:
?
Session ID Request
Username/password incorrect
?
3. In starting NetLog Version 1.3, I get the same ERROR dialog as point 2 above.
?
What/Where are are these programs pointing to for the Session ID Request? I probably set up the programs wrong on this new Dell laptop causing this ERROR dialog...
?
Thanks so much for your time and assistance!
?
73, Dave K4EET |
|
Re: QRZ Login Issue for Callsign Lookup in POTA Watch Version 25
Hi Dave,
Sorry about the problem. I'm not sure, but I'm thinking that the 2 factor authentication is the problem. I have not provided for that in the program.?
Did you run POTA Watch v24.0 successfully while using 2 factor authentication?? As far as logging into QRZ, there has been no change over the last few versions.
V25.0 is working ok on QRZ here, but I'm not using 2-factor. Can you temporarily shut off the 2-factor and try it?
73,
Ed - W4ELP |
|
QRZ Login Issue for Callsign Lookup in POTA Watch Version 25
Hi Ed,
?
For the QRZ login in POTA Watch Version 25, I know for certain that my Username is K4EET and the Password is **. I am getting this error dialog:
?
Session ID Request
Username/password incorrect
?
The "ERROR" dialog box above appears twice by hitting "OK" to close the first dialog box and then an identical "ERROR" dialog box appears.
?
Finally, upon pressing "OK" on the second dialog box, a third dialog pops up as "POTA Watch.exe" and simply shows my callsign (K4EET) which I was looking up.
?
The only thing that I can think of that may be causing these three error dialogs is that I have 2 Factor Authentication (2FA) turned on. Might that be what is causing these error dialogs versus having the wrong Username/password which I can use to successfully log into QRZ directly for a callsign lookup?
?
Thanks for your time. I would prefer to not turn off 2FA if at all possible.
?
73,?Dave K4EET
?
? |
|
New POTA Watch v25.0 available.
POTA Watch has been updated to v25.0 and is available for download in the Files > Program Files section of this forum.
This update is the result of a major rewrite of much of the program to allow it to run more effeciently and reliably.
. Added display of band as well as frequency of spots (band is optional in settings).
. Sort spots by spot age (default) or by frequency
. Added logging of time off in addition to time on. Since POTA QSOs are usually very short, time off is logged time + 1 minute.
. Cleaned up user interface when making QSOs, logging and spotting.
. Cleaned up New Station spotting and logging.
. Fixed display of "special" characters in park names.
. Fixed failure to log band on new station
. Fixed issue in Options window with newly-selected log file path not displaying correctly.
?
Thanks to Rainer, DO9RAI, for some great suggestions.
As always, there may be some issues or bugs that I have missed in testing. Please let us know of any problems, issues or suggestions.
73,
Ed - W4ELP
? |
|
POTA Watch new V24.0 posted for download
W4ELP's POTA Watch v24.0 has been updated with some new features, especialy for Ham Radio Deluxe users.
1. Selecting a spot by double click or right click will now set your radio to the spot frequency. You can select VFO A, B or none.
2. Your hunter logging now can go directly into your HRD Logbook or into N3FJP's AC Log. This is done instantly via API and can be selected on/off in options. For HRD's Logbook, POTA information is put into Comments as well as the SIG and SIG_INFO fields.
3. State/Province, Grid Square and DXCC Entity # are also now logged.
4. The visual and audio alarms are now extinguished when you have wroked the station. If he moves to another band or park, the alarm will reappear if appropriate. This help reduce screen clutter.
?
As always, there can be bugs that I missed in testing, so please post or email me with any comments or questions.
73,
Ed - W4ELP |
|
POTA Logger updated to V4.2
The POTA Logger for activators has been updated to v4.2.? It's mostly just a minor tweak - changing the order of the RST and SPC fields. After my first real activation recently, I realized the order of fields didn't match the flow of actual QSO's. This should work a bit smoother for those who log RSTs and/or State/Province.
Also added a text line to display the last callsign logged.?
?
As always, it's possible that I broke something with this fix, so please report any bugs or problems.
73,
Ed - W4ELP |
Ed - W4ELP
David
Stiv Ostenberg
Dave Hamm, K4EET