The latest beta version (November pre-3) has some fixes for keeping the spot connection alive.
Will hopefully test it next weekend.
Also SOTA chaser support is available. Start a new general operation and add the SOTA (and/or POTA) reference fields to the entry form. The exported adif should work fine for import as chaserlog.
Hi Joe, I was able to test the spotting behavior in Prev 3 yesterday and noticed that I could spot multiple times without having to log in again. It seems to have improved, let’s see what feedback others have.
Ive tried to do electronic logging for the first time in my life as an activator, this program was perfect, it was the operator that was pressing the wrong button. I reverted back to paper logging in the middle of my activity as quickly as I could.
no problem with the app, just me and big fingers
need to get me a 10" tablet instead of my Samsung Mobile
Hi Joe, yes I switched to one of those on the other end of my pen, but still kept pressing the wrong button, I am hoping a bigger screen will allow more space between each button??
One of the best parts of the logging section is, enter a callsign and the ops name appears, that’s good for us poor memory operators!
I will report back when I have set up a tablet with the app,
The latest “prerelease” has support for the new APIs and SSO. If all goes well, it will be published as the “November '24” release in a couple of weeks.
And I might release a minor upgrade to the current official release, “October '24”, in a couple of days too. If I get positive feedback from the prerelease version.
In future developement have you in mind to implement post qso entry (like VKPORTALOG). During the activity the app is very very fine and easy to use but sometimes I’ve to log my qsos hours after the activation, so it is difficult to insert hours and minutes for any qso. 73
Claudio IX1IHR
Hi Claudio,
I’m using Ham 2K (October 24 version) and there you can post QSO edit!
Simply clic over a logged QSO and modify what you want. callsign, freq, or even the hour,
If you clic in the required field. Edit is enabled, and after the modification is done, then select the Save icon to resume.
73 Ignacio
I’d like to log my qso’s from a paper log, not edit logged qso’s on the device.
In VKPORTALOG you can do so (I use this feature when I don’t have my PC. If I’m at home I use FastLogEntry).
Nevertheless thanks for info Ignacio. 73
Sebastian, you’re awesome — like those who say they’ll do it in a month but get it done right away, unlike those who say they’ll do it right away but end up taking a month.
This morning, I was greeted by an update, along with the ability to log into SOTAwatch.
There are some features already in place to help with manual entry afterwards.
You can type “21:33” in the callsign entry field and then press “send” or enter to set the time to 9pm Zulu, or “10/30” to set the date to October 30 (yes, month first, sorry… might add a setting for this in the future).
This will change the time, and also freeze the clock. It will also increase the time by 1 minute (or the difference between the last two manual QSOs) after you enter a new QSO. You can then manually enter a new time if you need.
UPDATE: (1/Nov/24) I am currently downloading the SOTA “All summits” data on my 3GB LG K43 Android 13 Smartphone - this is further than it has got before.
One slight “glitch” while still downloading (now at over 90,000 references), the panel says 100% - 0.0 seconds left, where the numbers are still rising - now 120,000 and rising. (it finished at just over 152,000)
For SOTA, I’m still a VK port-a-log user, but have been testing some cool features of PoLo, especially for spotting and logging a POTA activation.
For VK port-a-log and other loggers, I maintain a names.csv file that is updated with new calls every few months, as it was today. It now contains 73,221 calls. Today I also adapted my merger software to export a so-called Callsign Notes file which can be imported into PoLo.
The format of this file is simply {call} {firstname} and can be useful if the contacted ham is a) not on QRZ.com or b) you have no mobile phone data.
I have tested it locally with the latest beta version 24.11.2 and PoLo prefers the local file for the name. If the call is not found locally, the name from QRZ.com is used instead.
Later, if you are looking for an updated names.csv or names.txt file, please start at my HB9SOTA page as the WordPress upload path changes every month.
Is anyone else no longer getting precise locations for the QSO’s and the lines showing the short path? My activation maps are just showing a green dot centered on the state/county.
