开云体育

I recently uploaded my four QSO's that I had with VP8PJ from DXKeeper to LoTW. The upload went fine and a couple of days later when I logged into my LoTW account I saw that they were showing as

+ AA6YQ comments below Since yesterday, my DXKeeper recompute function has suddenly slowed down dramatically. It used to work almost instantaneously - probably taking a few milliseconds. Now it takes

Tnx Dave, there were a ton of them left over from 2001 satellite qsos. 73, N0AN Hasan

Understand (on dupes). The error logs are so superb that it was easy to catch and fix. 73, N0AN Hasan

+ AA6YQ comments below I had a LOT of these when I brought old 2001 year satellite qsos in with a sloppy *.adi file. The grid squares looked "good", but until I went into EDIT and deleted the grid

+ AA6YQ comments below It turns out that even one error in an upload to LoTW, prevented all the good qsos from uploading. (which is in the documentation) When editing the log I found if I had 50 qsos

Good morning, Since yesterday, my DXKeeper recompute function has suddenly slowed down dramatically.? It used to work almost instantaneously - probably taking a few milliseconds.? Now it takes about

I had a LOT of these when I brought old 2001 year satellite qsos in with a sloppy *.adi file. *The grid squares looked "good"*, but until I went into EDIT and deleted the grid square, and then

Lesson Learned: Don't Give Up I imported > 20,000 QSOs a few weeks ago when I "converted" from several different logs (*.adi imports) to a unified DXKeeper log. The "combined" log was a real mess.

+ AA6YQ comments below KQ40ck is working all right. JO28tp on the other hand is not. But when I delete the locator in grid1 field and rewrite it, it looks OK. I am new to this logging program, so I

Den 11.03.2020 01.28, skrev Dave AA6YQ: KQ40ck is working all right. JO28tp on the other hand is not. But when I delete the locator in grid1 field and rewrite it, it looks OK. I am new to this logging

+ AA6YQ comments below I have some broken QSOs with LA9VFA. Error message: invalid gridsquare. This ham operated from two different locators, but call was the same, as an /A or is not recommended in

I have some broken QSOs with LA9VFA. Error message: invalid gridsquare. This ham operated from two different locators, but call was the same, as an /A or is not recommended in Norway. What is the fix

Club Log's call tester is a goo resource for these. https://clublog.org/test.php 73, Mike ND9G

+ AA6YQ comments below I still have some qsos where the DXCC ID is blank, mostly TO#x entities from N1MM.....how can I find those? Are all TO3Z qsos FG? Are all TO0A qsos FS? + No. Any TO or TM

Thanks for your log file and spot database, Markku. The Spot Database entry for KD6DW does not specify a CQ zone, thus SpotCollector did not highlight it as "needed" for WAZ. Take the steps

I still have some qsos where the DXCC ID is blank, mostly TO#x entities from N1MM.....how can I find those? Are all TO3Z qsos FG? Are all TO0A qsos FS?

+ AA6YQ comments below thanks Dave, fixed all 556 broken qsos in a record amount of time !!!! + Good! DXKeeper will help you avoid creating new broken QSOs. 73, Dave, AA6YQ

+ AA6YQ comments below In Spotcollector I have noticed that some callsigns does not have info about their DXGrid (Locator). Why not? + See the " Determining the Location of each Active DX Station"

thanks Dave, fixed all 556 broken qsos in a record amount of time !!!!