On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that last an hour four times on Wednesdays. For example, this morning from 1300Z to 1400Z.
QSO_Begin between #2025-04-02 13:00# and #2025-04-02 14:00# should do the job for the first hour this morning.
That becomes QSO_Begin between #2025-04-02 19:00# and #2025-04-02 20:00# for this afternoon's run, etc.
Given the amount of changing (four times a week) and short duration, it would probably be just as easy to use the UTC filter in DXK Advanced Sorts, Filters & Modifiers. Select the After radio button, enter the same data as in the two examples above, and click "Filter" at the right end of the panel.
You will be in the Advanced Sorts, Filters and Modifiers window to change QSL_Sent to 'N' anyway.
73,
... Joe, W4TV
On 2025-04-02 10:49 AM, Bob Main via groups.io wrote:
Thanks Joe, no not using contest mode. It is the CWT contests that last an hour four times on Wednesdays. For example, this morning from 1300Z to 1400Z. There aren't that many, but if I can filter them out then I can change it. Then in the future I just modify the filter to fit the date and time frame. 73, Bob KB4CL -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV Sent: Wednesday, April 2, 2025 10:44 AM To: [email protected] Subject: Re: [DXLab] Change QSL Sent to "N" If you were using Contest mode, you could filter on CONTEST_ID. If you were not using contest mode, you would probably need to use a date filter QSO_Begin between #2025-01-01 16:00# and #2025-01-02 24:00# (use the appropriate date and times). For a date filter you can also use the UTC Filter in Advanced Sorts, Filters & Modifiers 73, ... Joe, W4TV On 2025-04-02 10:33 AM, Bob Main via groups.io wrote:
If I work a number of stations during a contest, but I don't plan to mail out QSL cards to everybody I worked and I want to change QSL Sent to "N" in one move how do I do it? I know that I go into the DXKeeper Advanced Sorts, Filters & Modifiers. Then create a Filter to isolate them. Finally, under "Modify QSOs in Log Play Display I set QSL_Sent to "N". The question is what would the filter look like?
Thanks Joe, no not using contest mode. It is the CWT contests that last an hour four times on Wednesdays. For example, this morning from 1300Z to 1400Z. There aren't that many, but if I can filter them out then I can change it. Then in the future I just modify the filter to fit the date and time frame.
-----Original Message----- From: [email protected] <[email protected]> On Behalf Of Joe Subich, W4TV Sent: Wednesday, April 2, 2025 10:44 AM To: [email protected] Subject: Re: [DXLab] Change QSL Sent to "N"
If you were using Contest mode, you could filter on CONTEST_ID.
If you were not using contest mode, you would probably need to use a date filter QSO_Begin between #2025-01-01 16:00# and #2025-01-02 24:00# (use the appropriate date and times).
For a date filter you can also use the UTC Filter in Advanced Sorts, Filters & Modifiers
73,
... Joe, W4TV
On 2025-04-02 10:33 AM, Bob Main via groups.io wrote:
If I work a number of stations during a contest, but I don't plan to mail out QSL cards to everybody I worked and I want to change QSL Sent to "N" in one move how do I do it? I know that I go into the DXKeeper Advanced Sorts, Filters & Modifiers. Then create a Filter to isolate them. Finally, under "Modify QSOs in Log Play Display I set QSL_Sent to "N". The question is what would the filter look like?
If you were using Contest mode, you could filter on CONTEST_ID.
If you were not using contest mode, you would probably need to use a date filter QSO_Begin between #2025-01-01 16:00# and #2025-01-02 24:00# (use the appropriate date and times).
For a date filter you can also use the UTC Filter in Advanced Sorts, Filters & Modifiers
On 2025-04-02 10:33 AM, Bob Main via groups.io wrote:
If I work a number of stations during a contest, but I don't plan to mail out QSL cards to everybody I worked and I want to change QSL Sent to "N" in one move how do I do it? I know that I go into the DXKeeper Advanced Sorts, Filters & Modifiers. Then create a Filter to isolate them. Finally, under "Modify QSOs in Log Play Display I set QSL_Sent to "N". The question is what would the filter look like? 73, Bob KB4CL
As best as I can recall, install a fresh copy of WSJTX on the new system then copy %LocalAppData%\WSJT-X from the system/install you want to move/clone to the same location on the new system.
That will move a lot of "junk" but it will get the WSJT-X.ini, wsjtx_log.adi, wsjtx.log and any ALL files.
If I work a number of stations during a contest, but I don’t plan to mail out QSL cards to everybody I worked and I want to change QSL Sent to “N” in one move how do I do it?? I know that I go into the DXKeeper Advanced Sorts, Filters & Modifiers.? Then create a Filter to isolate them.? Finally, under “Modify QSOs in Log Play Display I set QSL_Sent to “N”.? The question is what would the filter look like?
Hi Jim, I had similar unreliable email to sms service from Tmobile, and then Gmail. I found an Android app called Pushover. It costed like, $2.99 for lifetime use. I got an address to send my emails, and it sends me an SMS. It is nearly instantaneous and works very well. Don't know if there's an iPhone version. 73 Dean W8ZF
I had similar unreliable email to sms service from Tmobile, and then Gmail. I found an Android app called Pushover. It costed like, $2.99 for lifetime use. I got an address to send my emails, and it sends me an SMS. It is nearly instantaneous and works very well. Don't know if there's an iPhone version.
You can't simply copy an installation from one computer to another. However, if you follow the instructions here: <> you can reinstall on the new computer with all of your settings and intact.
Hello, I wanted to know if there is a way to copy a profile from 1 computer to another ? I had a crash and lost the laptop. I have a good working install on a desktop. Scott N2SAB
On Apr 2, 2025, at 06:55, scot via groups.io <n2sab@...> wrote:
Hello,
?
I wanted to know if there is a way to copy a profile from 1 computer to another ? I had a crash and lost the laptop. I have a good working install on a desktop.
I wanted to know if there is a way to copy a profile from 1 computer to another ? I had a crash and lost the laptop. I have a good working install on a desktop.
?
Scott
N2SAB
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
On Tue, Apr 1, 2025 at 2:55?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
# more AA6YQ comments below
?
? * Two QSOs show in the Log QSOs tab.??
?
? *? I also see an Error File notice and in the notice I see a long list of errors for 2025-04-01.? Examples below:
2025-04-01 21:01:40.892 > program error 52 in module Common.PrintField, theFile = 3: Bad file name or number
2025-04-01 21:01:40.895 > program error 52 in module ADIF.LotWImportError: Bad file name or number
? *? The errors are in about 82 sets of 7 of the first followed by 1 of the second.
?
# That's the result of a defect in the current version of DXKeeper when "Sync LoTW QSOs" reports an error - typically a QSO that LoTW is reporting as accepted but is not present in your log. This defect is corrected in the next version of DXKeeper, which i can send you, but before I do that, is the "Report unmatched QSOs and QSLs as error" box checked on the "QSL Configuation" window's LoTW tab? If so, uncheck it, and then invoke "Sync LoTW QSOs" again.
? ? ?73,
? ? ? ? ? ? Dave, AA6YQ
--
Richard Hill
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
I had noticed "something " going on. For the first time in many months, I turned SKIMMER on, on my spot sources.
It took a few hours, but I found all my spot sources indicators were yellow, and when I opened config, Prune, Compact, Clear and (I think) Recompute were all flashing. Spot Collector was locked up and I had to use Task Manager to kill it.
+ Spot Source status displayed as "yellow" means "disconnected, trying to reconnect".
Spot Database Entries was somewhere around 30K-40K entries.
+ That'd a big Spot Database during a popular contest with your own Skimmer running.
There is/wasn't error log.
+ I suggest checking the Windows Error Log:
73,
Dave, AA6YQ
\
Re: FW: [CC-User] Bogus DX Spot Attacks on Clusters
I had noticed "something " going on. For the first time in many months, I turned SKIMMER on, on my spot sources.
It took a few hours, but I found all my spot sources indicators were yellow, and when I opened config, Prune, Compact, Clear and (I think) Recompute were all flashing. Spot Collector was locked up and I had to use Task Manager to kill it.
Spot Database Entries was somewhere around 30K-40K entries.
There is/wasn't error log.
Turning Skimmer off and limiting the database size to 7K entries seems to have fixed whatever it was.
-------- Original Message -------- On 4/1/25 10:47 AM, Dave AA6YQ <aa6yq@...> wrote:
FYI:
From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io Sent: Tuesday, April 01, 2025 10:25 AM To: [email protected] Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters
What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer.
Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped.
My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through.
? *? I also see an Error File notice and in the notice I see a long list of errors for 2025-04-01.? Examples below:
2025-04-01 21:01:40.892 > program error 52 in module Common.PrintField, theFile = 3: Bad file name or number
2025-04-01 21:01:40.895 > program error 52 in module ADIF.LotWImportError: Bad file name or number
? *? The errors are in about 82 sets of 7 of the first followed by 1 of the second.
?
# That's the result of a defect in the current version of DXKeeper when "Sync LoTW QSOs" reports an error - typically a QSO that LoTW is reporting as accepted but is not present in your log. This defect is corrected in the next version of DXKeeper, which i can send you, but before I do that, is the "Report unmatched QSOs and QSLs as error" box checked on the "QSL Configuation" window's LoTW tab? If so, uncheck it, and then invoke "Sync LoTW QSOs" again.