Hello, perhaps this is already been addressed, but I’d like to know if there is a way for the WRL logger to automatically split QSOs when operating from, and communicating with, expedition operators that need to log more than one state/county code.
Here’s an example. I plan to operate the 7QP at a location within 500’ of the borders of 4 counties. That means every time I log a QSO there should be four different log entries for the four counties that I’m activating. This is why the Expedition class was created… to allow multi-county simultaneous operations.
Take that a step further… if I’m operating four counties, and I make contact with someone that is operating two counties, I will now need eight log entries for each of my counties associated with each of his/hers.
The N1MM Logger software does this QSO splitting automatically for you when configured correctly, but there is no portable logger function. To get to the spot 500’ from the corner of the four counties I plan to operate, I have to hike to the spot and operate like it’s a SOTA summit with minimal gear. I cannot bring my laptop with me up to that site. Being able to log with a mobile device is much more practical.
I see you have a 7QP log, but after playing with it I found that I will have to log each county code separately. Or perhaps I’m not understanding all the functions of your logger. Please let me know if I’m missing something, or if this is a feature that can be added to you QSO party loggers.
You are correct, currently we don’t have that functionality added. I’m happy to add this as a feature request though. Also, while you can log the QSO party contests on a mobile device the mobile app isn’t really geared towards contesting currently. We will be adding additional features to do mobile contest logging though. There are just certain features that aren’t enabled on mobile like on the web app such as the “auto complete” county abbreviation drop down in the exchange filed.
I’ll add your use case as a feature request and see if we can roll that update in with some of the other mobile contesting updates. Being transparent, with the 7QP being in two days those changes wont be ready in time though.
Ok so after thinking about this some more and thinking about how we handle the Cabrillo export. I have a solution that will be easier on you.
Since each callsign you log needs to have your exchange (your county) be logged essentially 4 times (1 for each county) and the way our ‘My Exchange’ field (underneath the log contact button) works, and it wont currently support that, my solution would be (at least for this contest, since the situation is unique) is for you to just set one county abbreviation in the ‘My Exchange’ field and log your contacts like you are only at that one county.
Then when the contest is over just shoot me a message or ping me with an @ my callsign here and let me know the other 3 county abbreviations you were at.
What I’ll do is go in and export your logbook and manually duplicate the QSO records and update the county abbreviations for each QSO for you. That way you only need to double log any other operator that is operating at multiple counties. This should save you a considerable amount of time logging.
This will also give me time to talk to the team and have them implement some updates not only to the mobile app but to the underlying contest settings throughout WRL and create the ability to handle these types of situations easier.