+ AA6YQ comments below Hi Dave, I am running the current version of DXKeeper 14.6.2. and the path is C:\DXLab\DXKeeper\DXKeeper.exe Wondering if I should save my log and delete all and do a fresh

I’m connected to both the ve7cc..net and foc.dj1yfk.de clusters. But I’m not seeing any spots from the foc.dj1yfk.de cluster in Spot Collector. Both clusters have Enable and Auto check in the

Hi Dave, I am running the current version of DXKeeper 14.6.2. and the path is C:\DXLab\DXKeeper\DXKeeper.exe Wondering if I should save my log and delete all and do a fresh install ? Thank you Garry

Thanks Dave for this new information. I'm eager to test your proposed new Spot Collector version when it's ready. 73, John W1JA

Dave – I am working toward a particular award and need just 4 stations to complete that quest. I’ve created a special call sign list of those 4 stations and an accompanying alarm.wav file,

The correct port setting for W9PA-5 (FT8 skimmer) is 7374. 73, Steve K2SN

Correction: W9PA generates ~1000 new Spot Database Entries per minute, only 2X more than the RBN. 73, Dave, AA6YQ

With W9PA's CW and FT8 skimmers configured as its spot sources, SpotCollector on my Windows 10 test system created more than 10,000 new Spot Database Entries in the last 60 minutes; most of these

Thanks, Joe! I added the information you provided below to a "Printer-specific Configurations" sections at the end of < https://www.dxlabsuite.com/dxlabwiki/GeneratingQSLLabels> 73,

+ AA6YQ comments below Where did you find the solution? I have the same issue + Here: <https://www.dxlabsuite.com/dxlabwiki/WinWarblerActivationOnCWSSBSpotDatabaseEntryDoubleClick> 73,

Oh, I see. Thanks for the clarification. 73 Stan KM4HQE

+ AA6YQ comments below I leave it running 24x7. Sounds like high volume spot sources cause problems though? + It would be more accurate to say that the current version of SpotCollector is not

It's clearly stated at https://vp6d.com/index.php/dxpedition/qsl-policy under "OQRS" : "LotW upload will be processed within 48 hours for unlimited confirmations." 73, ~iain / N6ML

I leave it running 24x7.  Sounds like high volume spot sources cause problems though?  I don't use RBN or W9PA as spot sources. 73 Stan KM4HQE

Until the change described below is publicly released, anyone with SpotCollector running 24x7 and connected to a high-volume spot source like the remote beacon network (RBN) or W9PA or a local skimmer

John W1JA, my speculation that there is something wrong with the Jet Database Engine on your system was likely incorrect. I've had SpotCollector on my Windows 8 test system running unattended for

+ AA6YQ comments below Thank you Dave for the response, much appreciated and hopefully I can explain what seems to be going on. The "failed" message was coming from WSJT-X, a confirmation of the qso.

My confirmations for Q's with VP6D showed up on LoTW today. But, I've seen that happen on more than one occasion where a day or so after I request a card and make a donation the confirmations show up

+ AA6YQ comments below Okay. Yesterday morning I stopped using W9PA and substituted NN1D. So I have 3 sources, NN1D, W1NR and CQDX. Since these changes, SC consumes very low CPU, has no unresponsive

+ AA6YQ comments below Hi all, subject radio Yaesu FT-920. When pushing the A=B button on Commander, the B VFO gets set to A minus 1.5 kHz, a second push sets A=B. This is new behavior, and I am