2/25/2023 0 Comments Ham radio deluxe setup templates![]() If you do have some simple P2P QSOs in there (one park contacting another single park, no double activations), the POTA database will attempt to identify these contacts by comparing the logs of the two POTA activators. ![]() ![]() ![]() The filename will indicate the park you are operating from and must meet the standard POTA format. The ADIF file for POTA needs to have the usual logging information but the special POTA fields (MY_SIG_INFO, SIG_INFO) can be left blank. POTA refers to these contacts as Park-to-Park or P2P, while SOTA refers to them as Summit-to-Summit or S2S. I wrote about the different ADIF fields that POTA and SOTA use here:įor an activation that does not involve making contact with other parks or summits, the logging requirements are simple. If you are using a different logging program, you can probably still benefit from this post. HAMRS still has a few quirks on entering callsigns and timestamps, but I am hopeful those things will get addressed in the fullness of time. HAMRS provides useful templates for both SOTA and POTA, but not both simultaneously. I’ve decided to use HAMRS for this, whether it is real-time logging or transcribing a paper log after the event. ![]() Here in Colorado, many of the SOTA peaks are in national forests or national parks, making them an ideal double activation.Ĭreating one file for logging both programs can be a challenge but I’ve settled in on an approach that works for me. There is a lot of crossover between the two programs. Doing a simultaneous activation of a Summits On The Air (SOTA) summit and a Parks On The Air (POTA) park is becoming more common. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |