|
The local radio club is starting to get POTA active, and I am going to give it a try.? I own a few small rigs suitable for very lightweight work, including a small 40M monobander and a KX1.??
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
|
Hi Chuck.? ?is the best place to get started.? You can find all the details there.? I have really gotten into POTA over the last few years.? I use N1MM+ in the field.? There are a couple
of POTA specific UDCs available.? When I get home, I import the adif file I generate from N1MM into DXKeeper.? I have made a separate "MyQTH" entry, along with a new LoTW station location? for each POTA site I activate.? ?That is the only way to do it to keep
everything straight.? I always pay attention to the grid square and county for my activations so anyone that is chasing those can have that info.? I only use one radio for POTA, so that's not a thing for me.? The required adif fields for POTA can be found
at
It looks like you're mainly a CW op, but if you plan on doing any SSB, you will probably want a 100-watt radio in your kit.? Lots of POTA operators like the Yaesu FT-891.
Be careful, POTA is very addictive!
Let me know if you have any further questions.
73,
Ken, KJ9B
toggle quoted message
Show quoted text
The local radio club is starting to get POTA active, and I am going to give it a try.? I own a few small rigs suitable for very lightweight work, including a small 40M monobander and a KX1.??
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
|
+ AA6YQ comments below
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
?
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
+ Before importing a log of QSOs from your just-completed POTA activation, 1. define a new myQTH in your Main log; populate the Sig textbox with the activated park code, and appropriately fill in the Rig, Ant, and location-oriented textboxes like "Pri Name", "Sec Name", and Grid. This information can be included in QSL Notes and/or outgoing QSL cards using QSL Substitution commands, as described in https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSL%20Substitution%20Commands 2. when importing a log of QSOs from your just-completed POTA activation using the Main window's "Import QSOs" tab, check the "Substitution options" panel's "Substitute for missing myQTH IDs" box and select the ID of the myQTH you created in step 1 + Depending upon what information is included in the ADIF file exported by your POTA application, you may want to specify additional information in the panels on the "Import QSOs" tab
?
+ Ops here with actual experience activating POTA, SOTA, and/or WWFF sites may have more suggestions.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
?
|
Chuck
I do all?my SOTA and POTA logging on my phone. I use?Ham2K Portable Logger. It is a very useful tool. After the activation, it produces an ADI file that I import directly into DXKeeper and upload?to the POTA website. I have not had any errors doing this. Here is the link to?Ham2K Portable Logger. It works?on Apple and Android.
+ AA6YQ comments below
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
?
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
+ Before importing a log of QSOs from your just-completed POTA activation, 1. define a new myQTH in your Main log; populate the Sig textbox with the activated park code, and appropriately fill in the Rig, Ant, and location-oriented textboxes like "Pri Name", "Sec Name", and Grid. This information can be included in QSL Notes and/or outgoing QSL cards using QSL Substitution commands, as described in 2. when importing a log of QSOs from your just-completed POTA activation using the Main window's "Import QSOs" tab, check the "Substitution options" panel's "Substitute for missing myQTH IDs" box and select the ID of the myQTH you created in step 1 + Depending upon what information is included in the ADIF file exported by your POTA application, you may want to specify additional information in the panels on the "Import QSOs" tab
?
+ Ops here with actual experience activating POTA, SOTA, and/or WWFF sites may have more suggestions.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
?
|
Okay, looking back at the original?post, I did not answer the question.?
I have a separate?MYQTH?ID for each place I activate. The only things that I enter is the correct CQ and ITU zone and the correct Maidenhead?Grid. I do take it one step further. I also have a separate Station Location for each place I activate in TQSL. It is a small amount of work. I think there is a way in TQSL to skip this, but I don't do it. I like to have all the places I activate listed.?
Chuck
I do all?my SOTA and POTA logging on my phone. I use?Ham2K Portable Logger. It is a very useful tool. After the activation, it produces an ADI file that I import directly into DXKeeper and upload?to the POTA website. I have not had any errors doing this. Here is the link to?Ham2K Portable Logger. It works?on Apple and Android.
+ AA6YQ comments below
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
?
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
+ Before importing a log of QSOs from your just-completed POTA activation, 1. define a new myQTH in your Main log; populate the Sig textbox with the activated park code, and appropriately fill in the Rig, Ant, and location-oriented textboxes like "Pri Name", "Sec Name", and Grid. This information can be included in QSL Notes and/or outgoing QSL cards using QSL Substitution commands, as described in 2. when importing a log of QSOs from your just-completed POTA activation using the Main window's "Import QSOs" tab, check the "Substitution options" panel's "Substitute for missing myQTH IDs" box and select the ID of the myQTH you created in step 1 + Depending upon what information is included in the ADIF file exported by your POTA application, you may want to specify additional information in the panels on the "Import QSOs" tab
?
+ Ops here with actual experience activating POTA, SOTA, and/or WWFF sites may have more suggestions.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
?
|
Here is a link to a couple of screenshots of my DXKeeper my QTHs and my TQSL Station location tab. The hardest part of this process is figuring?out what county the location was in for TQSL.
Okay, looking back at the original?post, I did not answer the question.?
I have a separate?MYQTH?ID for each place I activate. The only things that I enter is the correct CQ and ITU zone and the correct Maidenhead?Grid. I do take it one step further. I also have a separate Station Location for each place I activate in TQSL. It is a small amount of work. I think there is a way in TQSL to skip this, but I don't do it. I like to have all the places I activate listed.?
Chuck
I do all?my SOTA and POTA logging on my phone. I use?Ham2K Portable Logger. It is a very useful tool. After the activation, it produces an ADI file that I import directly into DXKeeper and upload?to the POTA website. I have not had any errors doing this. Here is the link to?Ham2K Portable Logger. It works?on Apple and Android.
+ AA6YQ comments below
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
?
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
+ Before importing a log of QSOs from your just-completed POTA activation, 1. define a new myQTH in your Main log; populate the Sig textbox with the activated park code, and appropriately fill in the Rig, Ant, and location-oriented textboxes like "Pri Name", "Sec Name", and Grid. This information can be included in QSL Notes and/or outgoing QSL cards using QSL Substitution commands, as described in 2. when importing a log of QSOs from your just-completed POTA activation using the Main window's "Import QSOs" tab, check the "Substitution options" panel's "Substitute for missing myQTH IDs" box and select the ID of the myQTH you created in step 1 + Depending upon what information is included in the ADIF file exported by your POTA application, you may want to specify additional information in the panels on the "Import QSOs" tab
?
+ Ops here with actual experience activating POTA, SOTA, and/or WWFF sites may have more suggestions.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
?
|
Thanks, Kent - exactly what I was looking for.? I see the "Rig" field shows "KX3".? Did you have to create a KX3 entry in Commander's Multi-Rig to append to the MyQTH ID?? I'd rather avoid that route for radios I am unliekly to ever connect to my DXLabs computer.
Here is a link to a couple of screenshots of my DXKeeper my QTHs and my TQSL Station location tab. The hardest part of this process is figuring?out what county the location was in for TQSL.
Okay, looking back at the original?post, I did not answer the question.?
I have a separate?MYQTH?ID for each place I activate. The only things that I enter is the correct CQ and ITU zone and the correct Maidenhead?Grid. I do take it one step further. I also have a separate Station Location for each place I activate in TQSL. It is a small amount of work. I think there is a way in TQSL to skip this, but I don't do it. I like to have all the places I activate listed.?
Chuck
I do all?my SOTA and POTA logging on my phone. I use?Ham2K Portable Logger. It is a very useful tool. After the activation, it produces an ADI file that I import directly into DXKeeper and upload?to the POTA website. I have not had any errors doing this. Here is the link to?Ham2K Portable Logger. It works?on Apple and Android.
+ AA6YQ comments below
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
?
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
+ Before importing a log of QSOs from your just-completed POTA activation, 1. define a new myQTH in your Main log; populate the Sig textbox with the activated park code, and appropriately fill in the Rig, Ant, and location-oriented textboxes like "Pri Name", "Sec Name", and Grid. This information can be included in QSL Notes and/or outgoing QSL cards using QSL Substitution commands, as described in 2. when importing a log of QSOs from your just-completed POTA activation using the Main window's "Import QSOs" tab, check the "Substitution options" panel's "Substitute for missing myQTH IDs" box and select the ID of the myQTH you created in step 1 + Depending upon what information is included in the ADIF file exported by your POTA application, you may want to specify additional information in the panels on the "Import QSOs" tab
?
+ Ops here with actual experience activating POTA, SOTA, and/or WWFF sites may have more suggestions.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
?
|
Chuck
No, I don't?use the KX3 or KX2 with DXLabs.?
On Tue, May 6, 2025 at 11:05?AM Chuck, WS1L via <chandlerusm= [email protected]> wrote: Thanks, Kent - exactly what I was looking for.? I see the "Rig" field shows "KX3".? Did you have to create a KX3 entry in Commander's Multi-Rig to append to the MyQTH ID?? I'd rather avoid that route for radios I am unliekly to ever connect to my DXLabs computer.
Here is a link to a couple of screenshots of my DXKeeper my QTHs and my TQSL Station location tab. The hardest part of this process is figuring?out what county the location was in for TQSL.
Okay, looking back at the original?post, I did not answer the question.?
I have a separate?MYQTH?ID for each place I activate. The only things that I enter is the correct CQ and ITU zone and the correct Maidenhead?Grid. I do take it one step further. I also have a separate Station Location for each place I activate in TQSL. It is a small amount of work. I think there is a way in TQSL to skip this, but I don't do it. I like to have all the places I activate listed.?
Chuck
I do all?my SOTA and POTA logging on my phone. I use?Ham2K Portable Logger. It is a very useful tool. After the activation, it produces an ADI file that I import directly into DXKeeper and upload?to the POTA website. I have not had any errors doing this. Here is the link to?Ham2K Portable Logger. It works?on Apple and Android.
+ AA6YQ comments below
I would like to be able to import my logs from my POTA ops to my main log without causing LOTW errors due to mangled MyQTH's, LOTW station locations, Rig names etc.??
?
Is there a document of best practices for POTA logging?? I know it's been discussed before but I wasn't paying as much attention as I should have been!
+ Before importing a log of QSOs from your just-completed POTA activation, 1. define a new myQTH in your Main log; populate the Sig textbox with the activated park code, and appropriately fill in the Rig, Ant, and location-oriented textboxes like "Pri Name", "Sec Name", and Grid. This information can be included in QSL Notes and/or outgoing QSL cards using QSL Substitution commands, as described in 2. when importing a log of QSOs from your just-completed POTA activation using the Main window's "Import QSOs" tab, check the "Substitution options" panel's "Substitute for missing myQTH IDs" box and select the ID of the myQTH you created in step 1 + Depending upon what information is included in the ADIF file exported by your POTA application, you may want to specify additional information in the panels on the "Import QSOs" tab
?
+ Ops here with actual experience activating POTA, SOTA, and/or WWFF sites may have more suggestions.
? ? ? 73,
? ? ? ? ? ? ? Dave, AA6YQ
?
?
|
There are several apps you can use to find the county.
Where am I? - is available for both android an iphones
County Lines? - is available for iphone, not sure about android.
I know there is also a few others out there...
73
Bob, KA9JAC
toggle quoted message
Show quoted text
On 5/6/2025 12:50 PM, Kent N6WT via groups.io wrote: figuring?out what county the location was
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
|
Chuck
I forgot to mention, when I import the adi file from my logger into DXK, I make sure to check the box for "Substitute for missing myQTH IDs"? and choose the correct my QTH ID I made for that operation.?
Good luck and hope to work you P2P soon.
There are several apps you can use to find the county.
Where am I? - is available for both android an iphones
County Lines? - is available for iphone, not sure about android.
I know there is also a few others out there...
73
Bob, KA9JAC
On 5/6/2025 12:50 PM, Kent N6WT via wrote:
> figuring?out what county the location was
--
This email has been checked for viruses by AVG antivirus software.
|
On 5/6/2025 11:11 AM, KA9JAC via groups.io wrote: There are several apps you can use to find the county. Google will find county maps for a state, then search for the county that you think includes the QTH and click on the displayed map. Those of us old enough to have depended on paper road maps may still have them (or a road atlas) laying around. I do. :) They show county lines. DX Atlas is great shareware by VE3NEA, whose other gifts are the CW and RTTY scanners that power spotting networks. One of its overlays is grids. It doesn't do counties. Freeware aprs.fi, which maps aprs signals, will display the boundary of a grid entered as a location. 73, Jim K9YC
|
I basically do this (Dave's recommendation) and it works great. I use HAMRS in the field for pota and then import the adif files to DXKeeper.
?
To keep things simple and because I thought there was a limit to number of MYQTH IDs I could create, I have a MYQTH for each County in Florida from which I operate. Each one is defined with pri, sec (state and county), grid, cq, itu, etc as per the MYQTH panel. This works for me as each county has anywhere from 3 to 10 pota parks and we move around activating several. Also, some park numbers span multiple counties such as the Florida Scenic Trail and Everglades (or states...think Appalachian Trail) so the park number does not always match 1:1 to a qth (same pri/sec). I use one of the user defined fields to track My_Park for all my pota activations. This field is generated by hamrs automatically into its adif export file.
?
The pota awards page won't care, but this way, all my QSO's match to the actual state, county and grid from where I operated when submitted to lotw.?
?
Regards,
Al? KJ3Q
|
I have not done a POTA activation yet, but enjoying hunting. Although, I plan to begin activations soon. I have been playing with HAMRS PRO on a notebook for the field that I could then export an ADIF file to DXKeeper, if I desire.
?
I understand (I think) about creating individual My QTH's for each park/activation, but wouldn't that only "satisfy" DXKeeper, by keeping your log separated by TX locations? That alone would not satisfy LoTW for multiple TX locations, would it? Thinking that was the case, I was considering not uploading my POTA logs to LoTW since that is completely different from POTA credit. Which I understand is taken care of when the POTA activator uploads their log to the POTA website.?
?
Sorry if we are straying too far from DXLabs, but this seems to involve a little of both.
?
Thanks, and 73,
Pete WB4YDY
|
+ AA6YQ comments below
To keep things simple and because I thought there was a limit to number of MYQTH IDs I could create, I have a MYQTH for each County in Florida from which I operate.
+ At present, the maximum number of myQTHs supported by DXKeeper is 4096. Has anyone operated from more than 1000 different geographic locations?
Each one is defined with pri, sec (state and county), grid, cq, itu, etc as per the MYQTH panel. This works for me as each county has anywhere from 3 to 10 pota parks and we move around activating several. Also, some park numbers span multiple counties such as the Florida Scenic Trail and Everglades (or states...think Appalachian Trail) so the park number does not always match 1:1 to a qth (same pri/sec). I use one of the user defined fields to track My_Park for all my pota activations. This field is generated by hamrs automatically into its adif export file.
+ If, say, you're using user-defined field #2 for My_Park, then you can use the QSL Substitution Command
?
<userdefined_2>
+ to print the code of the park you activated on a QSL card or included it in a QSO's "QSL Message" item.
? ? ? 73,
?
? ? ? ? ? ?Dave, AA6YQ
|
+ AA6YQ comments below
I understand (I think) about creating individual My QTH's for each park/activation, but wouldn't that only "satisfy" DXKeeper, by keeping your log separated by TX locations? That alone would not satisfy LoTW for multiple TX locations, would it? Thinking that was the case, I was considering not uploading my POTA logs to LoTW since that is completely different from POTA credit. Which I understand is taken care of when the POTA activator uploads their log to the POTA website.?
+ DXKeeper assumes that all QSOs in your log were made from the same DXCC entity, and are thus valid for all DXCC awards. You can designate? operating locations that do not qualify for WAS or VUCC so that QSOs made from those locations are not counted towards your WAS or VUCC award progress, respectively.
+ Thus I recommend that you create both a myQTH and an LoTW "Station Location" for each geographic location from which you have made or will make QSOs. Each myQTH's LoTW selector should specify the appropriate LoTW "Station Location".
Sorry if we are straying too far from DXLabs, but this seems to involve a little of both.
?
+ This is mainstream DXLab territory. ? ? ? ?73, ? ? ? ? ? ? ?Dave, AA6YQ
|
Has anyone operated from more than 1000 different geographic locations?
Looks like I have a goal now ;-)
73,
Ken, KJ9B
toggle quoted message
Show quoted text
+ AA6YQ comments below
To keep things simple and because I thought there was a limit to number of MYQTH IDs I could create, I have a MYQTH for each County in Florida from which I operate.
+ At present, the maximum number of myQTHs supported by DXKeeper is 4096. Has anyone operated from more than 1000 different geographic locations?
Each one is defined with pri, sec (state and county), grid, cq, itu, etc as per the MYQTH panel. This works for me as each county has anywhere from 3 to 10 pota parks and we move around activating several. Also, some park numbers span multiple counties
such as the Florida Scenic Trail and Everglades (or states...think Appalachian Trail) so the park number does not always match 1:1 to a qth (same pri/sec). I use one of the user defined fields to track My_Park for all my pota activations. This field is generated
by hamrs automatically into its adif export file.
+ If, say, you're using user-defined field #2 for My_Park, then you can use the QSL Substitution Command
?
<userdefined_2>
+ to print the code of the park you activated on a QSL card or included it in a QSO's "QSL Message" item.
? ? ? 73,
?
? ? ? ? ? ?Dave, AA6YQ
|
A first cut at "Logging QSOs as a POTA Activator" is available here:
Corrections and suggested additions are welcome.
? ? ? 73,
? ? ? ? ? ? Dave, AA6YQ
|
On 5/6/2025 4:50 PM, Dave AA6YQ wrote: Has anyone operated from more than 1000 different geographic locations? Yes, Several county hunters have operated from all counties, current count of counties and equivalent areas - 3077 No need to worry about dxlab supporting that number though. 73 Bob, KA9JAC -- This email has been checked for viruses by AVG antivirus software. www.avg.com
|
+ AA6YQ comments below
Yes, Several county hunters have operated from all counties,
current count of counties and equivalent areas - 3077
No need to worry about dxlab supporting that number though.
+ 3077 "My QTHs"? No problem. DXKeeper supports 1000 more to spare. ? ? ? 73,
? ? ? ? ? ?Dave, AA6YQ
|
Dave, thanks very much for this information! DXLab continues to amaze me, and your willingness to help is always impressive and appreciated. Looks like I have more reading to do in preparation of my first POTA activation. I think this is one of those things that will be much better to get it correct before I start rather than trying to make it "right" on the back end. I will keep a close eye on this topic and the "Logging QSOs as a POTA Activator" page. This page already has loads of good info I wasn't aware of.
?
Thanks again, and 73!
Pete WB4YDY
|
Chuck, WS1L
Kent N6WT
Al