ADIF includes unnecessary info
Works fine with internal sound card of QrpLabs QMX. My only complaint is that the ADIF output from the log contains superfluous info which makes importing into another application problematic as it reports that there are too many characters. The complete qso exchanges are sent as “message” and latitude and longitude of both ends of the qso are included. I had to edit the adif to remove this but would like it to have not included the data in the first case.
Show less
Response from developer
Hi Gary, thank you very much for your constructive feedback. I fixed the longitude and latitude fields to comply with the ADIF standard and I added an option to exclude non-standard fields (application specific fields). The update will be available in a couple of days.
Now with POTA/SOTA!!
I have used this app successfully for about a dozen activations with nothing more than my phone, and my TruSdx using VOX. Pretty intuitive, and the log export is ADIF compliant. Well done!!
Response from developer
Thank you very much for your feedback, much appreciated. The recent update adds support for SOTA/POTA etc. activities.
So far not sure
I downloaded the app I can not get past putting in my call sign. I enter it and hit save it tells me “ enter call sign’ I’m stuck how to move forward. I click support and nothing comes up. Trying to find a email to ask for guidance. Can’t wait to use this. Once I get pass this problem.
Response from developer
Thank you very much for your feedback. Callsigns should consist of the characters A-Z, 0-9 and / up to 13 characters). A valid Maidenhead locator is also required, 4 or 6 characters long (e.g JN47 or JN47AB). Please get in touch with me at hb9zhk@uska.ch for further support.