Hello, I am not one for digital logging in the field and use PoLo after a SOTA or POTA activation. Everything works really well and the UI and overall design are excellent. One point that slows me down is the time entry when logging after the fact. The logger wants to predict the next entry time, which usually means me deleting the seconds and minutes and entering the correct minute for each entry. This is not the end of the world, but logging would be improved bit if there was a setting to turn off seconds and to keep the time at the last entry. Then it would usually only require a single back space and a new number. At the very least just turning off seconds would be helpful.
I don’t think I see a setting that controls that in the manual or settings, so I thought I would suggest it.
Hi Douglas,
Thanks for the post.
I have to say that PoLo was not designed from the ground up for post log entry. It has had a lot or work put into it to make it the best real time entry logger you can get.
I’m not suggesting that your idea does not have merit, but I wonder if you have ever used Fast Log Entry for post logging. It’s definitely faster than using PoLo could ever be.
Alan
Thanks Alan and that all makes sense. To be clear, the Polo is great for after the fact logging as it is. I am really just noting a small detail/wish (though knowing such a change may be quite large and unrealistic).
I treat most of my POTA activations like SOTA, in that I am usually hiking, biking or paddling to a more report location in the park. Simple paper logging works well for me and I am rarely on air much more than an hour. Polo is great back at home, on the sailboat or wherever I am for digital logging and uploading later.
@K1GC there are some less obvious features that might make it easier to enter your manual log.
There are multiple shortcuts you can enter in the “Callsign” field where you usually log.
You can type “14:55” and it will change the time. You can type “-1m” or “+3m” and it will adjust the time one minute back or 3 minutes forward. You can also do this with “h” or “d” for hours or days.
You can also enter frequencies as “7200” or “7.200”, bands like “20m” and modes like “CW”.
I’m not really happy with how the “auto advance” works when entering manual times. What would be the ideal process in your case?
Thanks for the info on the shortcuts, I will try them out shortly. That could be all that I need to smooth things out. I just notice with the time auto advance, I end up back spacing and correcting most entries. I don’t think there is any perfect, as I was realizing even if the time does not advance, you would still need to delete one number rather than 2-3. Maybe slightly faster, but probably not worth any great effort changing anything.
I was just out and I have a small log to enter, so I will test out the shortcuts and report back.
I only had 24 log entries to make and using the shortcut works really well for me. It was very quick to quickly adjust the time with the + or - minutes shortcut. I am guessing that was somewhere in the documentation and I glossed over it. Thank you for pointing that out. For my use, I don’t know that there would be any quicker solution now that I know to use that.
Much appreciate the app. One of these days I will try direct logging with it when I am somewhere fairly close to the car.
I have written this up in the Tips and Tricks section…
I’d forgotten about the -1m +3d etc
I’m not sure you can mimic the minute setting and callsign entry in one hit
e.g. “12 KI2D” because the spacebar will kill it.
But I have suggested that the minutes adjustment doesn’t have to be perfect. You just need to correct it when you move outside say 5 minutes from your record.
Alan
PS - I know there will be resistance to this inaccuracy.
