开云体育

Hi Dave, FYI only: Prune was set to 7 days.? It had been set to that value for years. I learned long ago to manage the size of the spot database.? Task manager did not show anything churning in the

+ AA6YQ comments below + Neither LoTW nor eQSL provide "POTA credit". What matters is that an activator correctly submit QSOs to POTA so that chasers will get credit. 73, Dave, AA6YQ

Since POTA hunters don't submit logs to the POTA system, any POTA awards are contingent upon the activator submitting their log for any "awards" to be issued. For that reason, especially when I'm

How is all this going to be affected when an activator goes home znd uploads to LotW, eQSL, etc, as if he was at home and not in a park? This is just about as common as breathing. Earl / KD5XB Sent

+ AA6YQ comments below + Thanks for your comments, Dennis!

+ AA6YQ comments below + Your Spot Database was evidently so large that the resulting load was more than your PC could handle. Preventing this is why SpotCollector provides the ability to monitor the

Thanks Joe, all four spot sources are showing green status. Pre Filtering is off. Oh, I just found it (or something that got it going).? I had size control set to 7 days.? I changed that setting

A bit late to the party but here is my .02 on the matter.? FWIW, I have 5500+ total contacts with POTA activators and ~2200 confirmed parks. The first issue is that the POTA database is very dynamic

See: <https://www.dxlabsuite.com/dxlabwiki/EmptyDatabase> In particular, check your computer clock and make sure the spot sources are all "green" (fully logged in). I would bet your computer's time

Greetings to the Group, Two days ago, I did a PC reboot to capture the latest Windows update. Like dozens of times before I did not see any issue.? To be candid I'm not sure this update and reboot is

+ AA6YQ comments below So it's 0715Z, I just woke up and checked Spot Collector. I'm receiving about 37 spots per minute with all skimmers turned off. Is this normal? Seems kinda low. + At 2033Z, I'm

So it's 0715Z, I just woke up and checked Spot Collector. I'm receiving about 37 spots per minute with all skimmers turned off. Is this normal? Seems kinda low. Spot sources are: n6ws.ddns.net

I tried by TCP/IP. Current log4OM manual says to use with slicemaster. Unable to get it to work. Using Omnirig was the only way I could get it to work. Greg AB7R Sent with [Proton

+ AA6YQ comments below + see /g/DXLab/message/229295 73, Dave, AA6YQ

Good idea. I meant to include this in my original message, but forgot -- my checklist is at https://www.dxlabsuite.com/dxlabwiki/OptimizeSCPerformance Vy 7 3 Earl / KD5XB e e Sent with [Proton

+ AA6YQ comments below + When you are making QSOs with WSJT-X, you must log them by clicking WSJT-X's Log button - not by using DXKeeper's Capture window. If you've been doing this in the past, then

+ AA6YQ comment sbelow + With that setting, each time a new spot arrived that was not a duplicate of a recently-received spot (e.g. from another cluster), SpotCollector was searching through the last

HI THERE, I AM USING DXLAB FROM 2007 AND IT IS FOR ME THE BEST. A FEW DAYS AGO AND I AM NOT SURE IF IT WAS AFTER THE INSTALATION OF THE LATEST VERSION OF DXKEEPER 18.1.4 DXKEEPER STARTED DOING THIS,

For MONTHS now, I've been having an on-again off-again problem. If I let my spot database get too large (around 10,000 entries is when I start noticing it), it gets slower & slower processing spots,

Joe, can you share how W9MBB is/was connected to Log4OM.? I ask because I could not find any reference to his call sign on the Log4OM site or forum. Chip - W6MY