¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. DXLab
  2. Topics

Spotcollector frozen (well sorta)

 

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 related to the problem I'm seeing.? After the update when everything was up and running, I launched Commander, DXKeeper, DXView, and Spotcollector.? Several hours later I noticed spots were not showing up in the band spread window and not on my FLEX6400 display.? The Spotcollector window was not capturing new spots.? It is displaying the last spots captured before the Windows update on 5/21 @ 1413z.? Symptoms include, I can initiate and send a spot to the DXcluster but it would not be captured in the Spotcollector screen or the bandspread etc.? Going into the individual cluster windows, I see that Spots are coming in from the clusters I monitor, but nothing "new" was showing in the spotcollector window. SH/DX inquiries to the clusters stream the latest spots right back.? I tried doing a restore to Spotcollector but that did not change anything.? ?
?
? ?I'm not sure what else to try. Thoughts and/or suggestions would be appreciated.
?
Thanks, Mike K9MK
?
PS: PC is a i9 gaming platform running W10_Pro.
?
?
 

On 2025-05-23 9:57 AM, K9MK wrote:

I'm not sure what else to try. Thoughts and/or suggestions would be appreciated.
See:
<>

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 zone is set to the correct local time
zone and thus the offset from GMT it not correct.

73,

... Joe, W4TV


On 2025-05-23 9:57 AM, K9MK wrote:
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 related to the problem I'm seeing.? After the update when everything was up and running, I launched Commander, DXKeeper, DXView, and Spotcollector.? Several hours later I noticed spots were not showing up in the band spread window and not on my FLEX6400 display.? The Spotcollector window was not capturing new spots.? It is displaying the last spots captured before the Windows update on 5/21 @ 1413z.? Symptoms include, I can initiate and send a spot to the DXcluster but it would not be captured in the Spotcollector screen or the bandspread etc.? Going into the individual cluster windows, I see that Spots are coming in from the clusters I monitor, but nothing "new" was showing in the spotcollector window. SH/DX inquiries to the clusters stream the latest spots right back.? I tried doing a restore to Spotcollector but that did not change anything.
? ?I'm not sure what else to try. Thoughts and/or suggestions would be appreciated.
Thanks, Mike K9MK
PS: PC is a i9 gaming platform running W10_Pro.
 

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 from Prune @ 7 days to setting below, setting a database file size at 30K QSO's and it kicked everything loose.? Spots are once again flying in and populating the bandspreads etc.?
?
I have no idea what or why, but it appears that we're good now.?
?
Thanks for the help.? Back to DXing...
?
73, Mike? K9MK
?
 

+ AA6YQ comments below
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 from Prune @ 7 days to setting below, setting a database file size at 30K QSO's and it kicked everything loose.? Spots are once again flying in and populating the bandspreads etc.?
?
I have no idea what or why, but it appears that we're good now.?
+ 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 number of entries inthe Spot Database and keep it pruned to a manageable size.

? ? ? ? ? ? 73,

? ? ? ? ? ? ? ? ? Dave, AA6YQ
?
 

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 background. That's why I am a bit mystified that by selecting a change to "Prune Spot Database" corrected my issue.
?
73, Mike K9MK
?
?
? ? ??
?
??
 

+ AA6YQ comments below
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 background. That's why I am a bit mystified that by selecting a change to "Prune Spot Database" corrected my issue.
+ You reported that the new misbehavior first occurred after a Windows update, so the initial hypothesis is that this update reduced your system's ability to handle the compute/memory load generated by your previous SpotCollector configuration. I suggest that you check Windows' virtual memory configuration, and confirm that your DXLab applications are each considered "safe" by Windows Defender and by any other anti-malware you have installed.
?
? ? ?73,

? ? ? ? ?Dave, AA6YQ
?

1 - 6 of 6