I was VERY pleased with WRL in the NYS QSO Party yesterday ! I am using WRL for first time in about a year , so had some learning to do but not much of a learning curve. I was with my local club at a POTA location and introduced club members to the simplicity of WRL logging. We used the web interface via a wifi connection to a Tmobile modem. We did not have CAT control because we used an old rig but I must say that WRL’s logger is FAR easier to type in a band and frequency than most of the geek-designed logging programs where you have to do gymnastics to manually enter a date, band, frequency.
I learned that a user needs to carefully manage the number of logs in our own WRL logbook because at first I was logging to the wrong one.
I tried spotting our POTA activation from WRL but WRL kept prompting me to add some park info but would not accept what I typed in . As I was the logger of the QSO’s I did not have time to figure that out , so another club member spotted us on the POTA pages.
I was expecting some sort of “dupe” alert but turns out it does not do that . I realized afterwards that I could have used a search function in the log area . I know this not really a contesting application but a dupe alert when in a WRL contest module would be nice.
Overall, it was superb !
Andy K3UK (W2SB club call in the contest )
That’s great to hear! So a couple of things when entering the park you have to wait until the drop down shows up and then select the park from that list. Its a little counter-intuitive currently and we have plans to change this very VERY soon.
As far as the dupe logic is concerned it should be working BUT there is a chance that something isn’t working correctly after the database upgrade. I’ll try and replicate it and confirm and then reach out to the team to push some fixes there.
Either way SOOOO glad you had an enjoyable experience and things overall worked well for you!
Thanks . I did not spend time on looking into dupe alerts, I just noted that nothing obvious popped up when I entered a dupe . If it did work as intended, what does it look like on the web interface scree?
I take that back . I just created a dupe and an DUPE alert does pop up. I probably did not see it on the small laptop screen in sunlight at the park/qsp QTH on Saturday.
Andy
Even outside of a contest, I would be happy if it showed me that I had already been in contact with this person in the last 48 hours. Because, first of all, it would be embarrassing if I spoke to him as if I didn’t know him and he then explained to me that we had already spoken yesterday. And secondly, I can then freely decide whether I want to consciously have another QSO with him or whether I want to turn the frequency knob and look for another conversation partner.
Please always display a colored “Dupe” below the call sign field if there has been a log entry in the last 48 hours. This should also be independent of explicit contest logs.
And if the recent contact was not on the same band, please also display this, e.g., “2d ago on 40m.” This makes it easier to start a conversation. (I know that further down the page, I can see whether this call sign already appears in my logs. But then I always have to look downwards. It would make much more sense if this information were displayed close to the input field, and I only had to scroll down for further information (What is his name? How many times already? etc.).
Please no pop-ups that you have to click away. Very impractical.
We have some similar already, once you enter the callsign if you’ve made previous QSO’s with that callsign it will show ‘# X QSOs’ and a view button. If you click that view button it will open a list of the previous dates, RST info, Frequency, etc for those QSO’s.
Hi Brad @K4AZE
Yes, I know this section and I appreciate it.
My feature request is on top:
Calling CQ and someone is answering, my eyes are on the input fields, filling out “call sign”, “their name”, “their grid”. In this hectic situation it would help me, if it would show me - when the callsign is already in my logs - a short info below the call sign field. So I would realize to look downwards to the section, which already exists.
If a contact is already in my logbooks, I don’t need the info “Callsign match”, but I would love messages like this at the same place:"
“44h ago: SSB 10m”
“3d ago FT8 20m”
Until 48h in hours (relevant also for contests), afterwards in d(day, m(month) or y(years).
