I don’t want to start running on the same frequency as a station I can’t hear because he’s in my skip zone. Jim N7US

It is not about a clear frequency. If you are trying to get a good run going it is about making sure enough stations hear you. Stations in a skip zone won’t hear you and therefore not answer your

If those spots are from your same general geographic are like you state, you should already know what frequencies are clear to run on. If not true, you may need better antennas. BAA

When contesting, I get spots from K/VE so I see spots of stations in my skip zone so I know to avoid those frequencies when looking for a run frequency. Jim N7US Sent from my Verizon, Samsung Galaxy

+ AA6YQ comments below It's probably worth reminding people that geography of the Telnet node you connect to is no longer a big deal. I routinely use nc7j.com:7373 in Utah from my QTH in MD.

+ AA6YQ comments below I am missing something. I enabled Marathon in DXK Config Awards for all HF bands. I enabled Realtime. I did a Recompute and the result is zero Q's. Can someone point me to

I am starting a small project to see if it makes any significant difference in how PropView works depending on my antenna choice. Propview offers some setup options related to that: 1. Band specific

It's probably worth reminding people that geography of the Telnet node you connect to is no longer a big deal. I routinely use nc7j.com:7373 in Utah from my QTH in MD.

Do you have the checkbox to "Include QSOs with no prop" checked? It's on Awards tab of Config. 73, Mike ND9G

I am missing something. I enabled Marathon in DXK Config Awards for all HF bands. I enabled Realtime. I did a Recompute and the result is zero Q's. Can someone point me to the wiki so I can discover

+ AA6YQ commentsb elow I used to make use of DXUSA.net as a spot source, but seem unable to connect to them or to their website... Any idea what happened to them? + I don't recall anyone posting a

I used to make use of DXUSA.net as a spot source, but seem unable to connect to them or to their website... Any idea what happened to them? Any suggested alternate sources? Thanks and 73 de Dave,

Use the file creation date(s) of those files ... filter your log for QSLSDATE, QSL_SENT_VIA = 'E' (assuming you set that) and QSL_SENT ='Y' That should give you the same QSOs. Then "ADD ALL" to

+ AA6YQ comments below + You could create an empty new log, import those .adi files into that log, and then direct DXKeeper to print QSL cards. 73, Dave, AA6YQ

I found some of the old .adi files I have sent to globalqsl. Is it possible to (re-)load them in DXK for local printing? Aart PA3C

+ AA6YQ comments below + Welcome to DXLab! + I suggest that you begin by reviewing https://www.dxlabsuite.com/dxlabwiki/GettingStarted + and following the advice given there. Don't try to traverse

I have run each module in the suite and tried to configure all the obvious things like call sign and grid square, radio type, etc. I got the com port talking to the radio. Now the rest is very

Hi Aart and the group, Also, the other co-founder of GlobalQSL, Paul Gross is a SK as well. You could also look at dcl.darc.de where you can upload contacts to your logbook, and there is a print

+ AA6YQ comments below + This defect has been present in LoTW since inception: when you direct it to report all QSLs newly created since YYYY-MM-DD at HH:NN:SS, it reports all QSLs newly created since

Dave, thank you. In fact it is strange. Yesterday I got the wrong information for that QSO and I manually edited the QSO to restore the correct primary subdivision. Today, after another QSL Sync, I