Date   
Re: What Computer Speed/Memory needed to fully and rapidly decode over 40 stations on a crowded band????

HamApps Support (VK3AMA)
 

On 19/04/2019 12:18 am, ve3ki wrote:
That being said, on a busy band I think it is reasonable and normal to see it take a couple of seconds into the next receive period before all of the decoding and JTAlert processing is completed. There is a lot of heavy number-crunching involved in decoding these signals.

73,
Rich VE3KI
Also, the OP mentioned JTDX which can be a real CPU hog if it hasn't been configured correctly. JTDX has an extended set of decoding options (compared to WSJT-X) in an effort to pull out more weak decodes. These additional decoding options  involving number of threads and cpu cores used, if not configured correctly for the PC hardware/software involved, can significantly impact performance to the detriment of the response times (time to deliver decodes) and excessive cpu load, made worse if on a very busy band like 40m & 20m where 40+ decodes per period are now common.

de Laurie VK3AMA

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Jim McPhee
 

Dave (W6DE),

I can see how that can become the case. DXCC Challenge, at 1000 QSLs? I should live that long!!!!

Right now I only do SSB on 40, 20 15, and 10 meters. Those are the only bands I have antennas for. (Well, except VHF/UHF). So far I have two awards, the WAS, and a NM QSO Party award from last year, NM Mobile-Multi Operator, the honor of earning I share with a couple of buddies.

I depend so much on Commander, DXKeeper and SpotCollector, that I want to know everything I can about them so I can extract the maximum benefit from my use of them.

Dave (AA6YQ) is such a Saint when it comes to explaining the inner workings and benefits of his apps. If I were him I would have thrown in the towel thousands of times by now, saying: "What's wrong with these people?!?! How many times do I have to explain how to extract even the minimum performance from of my apps?!?! In addition, what are they paying for the apps and the support I provide? Zip, nada, zero, nothing!" I mean, those Help files alone must have taken years to create, and a similar amount of effort to maintain. Like I said, a Saint!

73,

Jim McPhee
Placitas, NM
W5ABA

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of w6de
Sent: Thursday, April 18, 2019 3:38 PM
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

It is addictive. There is always the next award. First mixed-DXCC, then SSB-DXCC, then Digital, then CW-DXCC. Then your next award: DXCC by Band which leads you to 5-Band DXCC which puts you well on the way to the DXCC Challenge, which starts at 1000 QSLs. In the end it'll keep you on the air for several years.

Good hunting,
Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jim McPhee
Sent: 18 April, 2019 16:18
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Dave,

Fantastic explanation of the Realtime Award Tracking service design and implementation differences between SpotCollector and DXKeeper. Thank you again for taking your valuable time to help me understand why each works the way it does!

And for describing the steps to take to " filter the Log Page Display to show only QSOs whose confirmation would advance your award progress." I'm going to print this email out and put it in my "Quick Reference" folder.

For my first DXCC Award I've been focusing almost entirely on stations that participate in LoTW. I think if I can get some of the "DX LoTW participants" that I have unconfirmed QSOs with to confirm those QSOs, I might reach the required number quite soon.

73,

Jim McPhee
Placitas, NM
W5ABA

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Wednesday, April 17, 2019 8:00 PM
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

+ AA6YQ comments below

Thanks again for taking the time to provide that explanation.

If I may go back to the original question, because it appears I did not explain myself very well:

For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector <https://www.dxlabsuite.com/spotcollector> to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

SpotCollector does do that "Realtime", without having to run a filtered report, by displaying "Unworked DX Band or Mode" in one colored font, and "Unconfirmed DX" in another colored font.

Is there a way to configure DXKeeper to, in Realtime, "immediately identify QSOs whose confirmation would advance your award progress", similar to the way that SpotCollector does?

+ No. The CPU consumption required to do that in SpotCollector is well-justified, but there is no justification for doing that in DXKeeper.

+ In general, the reason you'd want to identify logged QSOs whose confirmation would advance your award progress is so you can generate outgoing QSL cards requesting those confirmation - an action you might take once a day if you're being aggressive about it. That's what the "Add Needed" function does.

+ If you'd like to filter the Log Page Display to show only QSOs whose confirmation would advance your award progress, you can take advantage of the fact that when adding a needed QSO to the "QSL Queue", the "Add Needed" function sets that QSO's Select item to 'Y'. So

1. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the X button to remove all filtering from the Log Page Display

2. On the Main window's "Check Progress" tab, click the "Clear Select" button at the bottom of the tab; this will clear the Select item in every logged QSO

3. Invoke the "Add Needed" function as previously suggested; if you're not going to be generating QSL cards, click the Clear button on the Main window's QSL tab

4. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the Sel button; the Log Page Display will be filtered to contain only those QSOs whose confirmation would advance your award progress.

+ It should be noted that CQ DX Marathon does not require submission of confirmed QSOs. Thus while SpotCollector highlights active DX stations needed for CQ DX Marathon on the bands and modes you're pursuing, DXKeeper's "Add Needed" does not populate the QSL Queue with QSOs that you'll be submitting for CQ DX Marathon at the end of the year unless they are also needed for an award like DXCC or WAZ that requires confirmation.

73,

Dave, AA6YQ







--
Jim McPhee
Placitas, NM
W5ABA










--
Jim McPhee
Placitas, NM
W5ABA

Re: Remove R from QSL sent box

Julio Peralta
 

I'm thinking otherwise since I do LOTW exclusively. Unless someone sends me
a QSL with a Pls QSL on it.

Julio

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Thursday, April 18, 2019 5:12 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Remove R from QSL sent box

+ AA6YQ comments below

Yes the QSO were logged by DXLab in the last 24 months. Neither of the boxes
you mentioned were checked.

+ The question is whether they were checked - intentionally or otherwise -
while you were logging those 8 QSOs.

73,

Dave AA6YQ

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

w6de
 

It is addictive. There is always the next award. First mixed-DXCC, then SSB-DXCC, then Digital, then CW-DXCC. Then your next award: DXCC by Band which leads you to 5-Band DXCC which puts you well on the way to the DXCC Challenge, which starts at 1000 QSLs. In the end it'll keep you on the air for several years.

Good hunting,
Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jim McPhee
Sent: 18 April, 2019 16:18
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Dave,

Fantastic explanation of the Realtime Award Tracking service design and implementation differences between SpotCollector and DXKeeper. Thank you again for taking your valuable time to help me understand why each works the way it does!

And for describing the steps to take to " filter the Log Page Display to show only QSOs whose confirmation would advance your award progress." I'm going to print this email out and put it in my "Quick Reference" folder.

For my first DXCC Award I've been focusing almost entirely on stations that participate in LoTW. I think if I can get some of the "DX LoTW participants" that I have unconfirmed QSOs with to confirm those QSOs, I might reach the required number quite soon.

73,

Jim McPhee
Placitas, NM
W5ABA

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Wednesday, April 17, 2019 8:00 PM
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

+ AA6YQ comments below

Thanks again for taking the time to provide that explanation.

If I may go back to the original question, because it appears I did not explain myself very well:

For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector <https://www.dxlabsuite.com/spotcollector> to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

SpotCollector does do that "Realtime", without having to run a filtered report, by displaying "Unworked DX Band or Mode" in one colored font, and "Unconfirmed DX" in another colored font.

Is there a way to configure DXKeeper to, in Realtime, "immediately identify QSOs whose confirmation would advance your award progress", similar to the way that SpotCollector does?

+ No. The CPU consumption required to do that in SpotCollector is well-justified, but there is no justification for doing that in DXKeeper.

+ In general, the reason you'd want to identify logged QSOs whose confirmation would advance your award progress is so you can generate outgoing QSL cards requesting those confirmation - an action you might take once a day if you're being aggressive about it. That's what the "Add Needed" function does.

+ If you'd like to filter the Log Page Display to show only QSOs whose confirmation would advance your award progress, you can take advantage of the fact that when adding a needed QSO to the "QSL Queue", the "Add Needed" function sets that QSO's Select item to 'Y'. So

1. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the X button to remove all filtering from the Log Page Display

2. On the Main window's "Check Progress" tab, click the "Clear Select" button at the bottom of the tab; this will clear the Select item in every logged QSO

3. Invoke the "Add Needed" function as previously suggested; if you're not going to be generating QSL cards, click the Clear button on the Main window's QSL tab

4. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the Sel button; the Log Page Display will be filtered to contain only those QSOs whose confirmation would advance your award progress.

+ It should be noted that CQ DX Marathon does not require submission of confirmed QSOs. Thus while SpotCollector highlights active DX stations needed for CQ DX Marathon on the bands and modes you're pursuing, DXKeeper's "Add Needed" does not populate the QSL Queue with QSOs that you'll be submitting for CQ DX Marathon at the end of the year unless they are also needed for an award like DXCC or WAZ that requires confirmation.

73,

Dave, AA6YQ







--
Jim McPhee
Placitas, NM
W5ABA

Re: Remove R from QSL sent box

Dave AA6YQ
 

+ AA6YQ comments below

Yes the QSO were logged by DXLab in the last 24 months. Neither of the boxes you mentioned were checked.

+ The question is whether they were checked - intentionally or otherwise - while you were logging those 8 QSOs.

73,

Dave AA6YQ

Re: Sound Card Issue?

Dave AA6YQ
 

+ AA6YQ comments below

On Thu, Apr 18, 2019 at 11:41 AM, John Plaster wrote:

A little off topic but has anyone ever run across this message "unable to start sound card - Unknown Error (33)". I get audio from a mic, mp3 or internet. Can't figure it out because all digital modes worked perfectly before. I even changed the sound card but no difference. The rig is a FT-5000.

+ Which application is displaying the error message, John?

        73,

             Dave, AA6YQ

Sound Card Issue?

John Plaster
 

A little off topic but has anyone ever run across this message "unable to start sound card - Unknown Error (33)". I get audio from a mic, mp3 or internet. Can't figure it out because all digital modes worked perfectly before. I even changed the sound card but no difference. The rig is a FT-5000.
Any suggestions?
John
K1VOI

Re: Remove R from QSL sent box

Julio Peralta
 

Yes the QSO were logged by DXLab in the last 24 months. Neither of the boxes
you mentioned were checked. As I said there were only 8 that needed
correcting. I've gone back about 100 Q's in my log and don't see any other
incidences of the R appearing.

Julio

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Thursday, April 18, 2019 12:56 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Remove R from QSL sent box

+ AA6YQ comments below

Thanks for the info Dave, however neither box was checked. There were only 8
so not a big deal.

+ Were those QSOs originally logged by DXKeeper, or imported from another
application?

+ Note that DXKeeper's Capture window provides a "QSL requested" box and
WinWarbler's "QSO Info" panel provides a QSL box. If
checked, these boxes will result in the logged QSO having its "QSL Sent"
item set to 'R'; this is typically used when your QSO
partner asks for a QSL card during the QSO.

73,

Dave, AA6YQ

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Dave AA6YQ
 

+ AA6YQ comments below

Fantastic explanation of the Realtime Award Tracking service design and implementation differences between SpotCollector and DXKeeper. Thank you again for taking your valuable time to help me understand why each works the way it does!

And for describing the steps to take to " filter the Log Page Display to show only QSOs whose confirmation would advance your award progress." I'm going to print this email out and put it in my "Quick Reference" folder.

For my first DXCC Award I've been focusing almost entirely on stations that participate in LoTW. I think if I can get some of the "DX LoTW participants" that I have unconfirmed QSOs with to confirm those QSOs, I might reach the required number quite soon.

+ One more point to be made.

+ Say you have P5 unconfirmed, with 3 logged P5 QSOs, each with a different station. Which one will "Add Needed" choose to add to the QSL Queue? The answer is "the most recent one".

+ While that's the right default behavior, you may be aware that one of those P5 stations is a better QSLer than that other two. Or you may wish to send QSL cards to all three in order to improve your chances for a rapid response.

+ Before invoking "Add Needed", click the RAT button on DXKeeper's Main window's "Log QSO" tab to display the "Realtime Award Tracking" window. On this window's DXCC tab, scroll down to the P5 row, and double-click the W in the Entity column; DXKeeper will filter the Log Page Display to show your three P5 QSOs. Right-click each one, and select "Add to QSL Queue".

+ You can repeat this procedure this for specific entities, entity-bands, entity-modes, zones, grids, states, IOTA tags, or prefixes that merit an extra effort to obtain a confirmation. When done, click "Add Needed", and DXKeeper will populate the QSL Queue with entries for the other QSOs whose confirmation would advance your award progress.

+ As your award totals rise, the opportunities to request multiple confirmations in parallel will decrease to the point where clicking "Add Needed" is all that's necessary.

73,

Dave, AA6YQ

Re: Remove R from QSL sent box

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the info Dave, however neither box was checked. There were only 8 so not a big deal.

+ Were those QSOs originally logged by DXKeeper, or imported from another application?

+ Note that DXKeeper's Capture window provides a "QSL requested" box and WinWarbler's "QSO Info" panel provides a QSL box. If
checked, these boxes will result in the logged QSO having its "QSL Sent" item set to 'R'; this is typically used when your QSO
partner asks for a QSL card during the QSO.

73,

Dave, AA6YQ

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Jim McPhee
 

Dave,

Fantastic explanation of the Realtime Award Tracking service design and implementation differences between SpotCollector and DXKeeper. Thank you again for taking your valuable time to help me understand why each works the way it does!

And for describing the steps to take to " filter the Log Page Display to show only QSOs whose confirmation would advance your award progress." I'm going to print this email out and put it in my "Quick Reference" folder.

For my first DXCC Award I've been focusing almost entirely on stations that participate in LoTW. I think if I can get some of the "DX LoTW participants" that I have unconfirmed QSOs with to confirm those QSOs, I might reach the required number quite soon.

73,

Jim McPhee
Placitas, NM
W5ABA

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Wednesday, April 17, 2019 8:00 PM
To: DXLab@groups.io
Subject: Re: [DXLab] "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

+ AA6YQ comments below

Thanks again for taking the time to provide that explanation.

If I may go back to the original question, because it appears I did not explain myself very well:

For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector <https://www.dxlabsuite.com/spotcollector> to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

SpotCollector does do that "Realtime", without having to run a filtered report, by displaying "Unworked DX Band or Mode" in one colored font, and "Unconfirmed DX" in another colored font.

Is there a way to configure DXKeeper to, in Realtime, "immediately identify QSOs whose confirmation would advance your award progress", similar to the way that SpotCollector does?

+ No. The CPU consumption required to do that in SpotCollector is well-justified, but there is no justification for doing that in DXKeeper.

+ In general, the reason you'd want to identify logged QSOs whose confirmation would advance your award progress is so you can generate outgoing QSL cards requesting those confirmation - an action you might take once a day if you're being aggressive about it. That's what the "Add Needed" function does.

+ If you'd like to filter the Log Page Display to show only QSOs whose confirmation would advance your award progress, you can take advantage of the fact that when adding a needed QSO to the "QSL Queue", the "Add Needed" function sets that QSO's Select item to 'Y'. So

1. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the X button to remove all filtering from the Log Page Display

2. On the Main window's "Check Progress" tab, click the "Clear Select" button at the bottom of the tab; this will clear the Select item in every logged QSO

3. Invoke the "Add Needed" function as previously suggested; if you're not going to be generating QSL cards, click the Clear button on the Main window's QSL tab

4. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the Sel button; the Log Page Display will be filtered to contain only those QSOs whose confirmation would advance your award progress.

+ It should be noted that CQ DX Marathon does not require submission of confirmed QSOs. Thus while SpotCollector highlights active DX stations needed for CQ DX Marathon on the bands and modes you're pursuing, DXKeeper's "Add Needed" does not populate the QSL Queue with QSOs that you'll be submitting for CQ DX Marathon at the end of the year unless they are also needed for an award like DXCC or WAZ that requires confirmation.

73,

Dave, AA6YQ







--
Jim McPhee
Placitas, NM
W5ABA

Re: What Computer Speed/Memory needed to fully and rapidly decode over 40 stations on a crowded band????

ve3ki
 

This question has nothing to do with DXLab Suite. You'd probably be better off posing this question on the HamApps group.

That being said, on a busy band I think it is reasonable and normal to see it take a couple of seconds into the next receive period before all of the decoding and JTAlert processing is completed. There is a lot of heavy number-crunching involved in decoding these signals.

73,
Rich VE3KI



On Wed, Apr 17, 2019 at 07:49 PM, Hugh Valentine wrote:
When a band is crowded with greater than 40 stations to decode I experience a delay of a couple of seconds to fill the screen in JTDX Alert.
Is this a function of CPU Speed or memory? 
What is the minimum Chip speed/memory necessary to speed this screen fill?  Or is INet speed the limiting factor here???

I5 chip on my computer/8GB memory.....Would a SSD Drive help?  Or do I need a new computer?

any insight would help steer me in the proper direction.....

Val
N4RJ

Re: Remove R from QSL sent box

Julio Peralta
 

Thanks for the info Dave, however neither box was checked. There were only 8
so not a big deal.

Julio

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Wednesday, April 17, 2019 9:47 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Remove R from QSL sent box

+ AA6YQ comments below

I guess that the (R)equested value is a default, but I don't remember if
there is a setting modifiable by the user.

+ There is: the "Preset QSL Requested" option on the "QSL Configuration"
window's General tab.

+ WinWarbler provides a similar "preset QSL checkbox" option in the "QSO
Info" panel on its Configuration window's Log tab.

73,

Dave, AA6YQ

Re: Remove R from QSL sent box

Salvatore Besso
 

ah, that's it! I had seen that checkbox in DXKeeper, but it's for the
capture window that I don't use because I use only WinWarbler and I
forgot that it has a similar setting.

73 de
Salvatore (I4FYV)

Re: What Computer Speed/Memory needed to fully and rapidly decode over 40 stations on a crowded band????

Dave AA6YQ
 

+ AA6YQ comments below

When a band is crowded with greater than 40 stations to decode I experience a delay of a couple of seconds to fill the screen in JTDX Alert.

+ I am not at all familiar with "JTDX Alert", but before considering hardware upgrades I suggest that you reboot Windows into "Safe Mode with Networking", and re-assess performance. It performance has substantially improved, then one or more applications that Windows is starting automatically when booted "normally" is interfering with "JTDX Alert". The usual culprit is a misconfigured firewall or anti-malware application.

Is this a function of CPU Speed or memory?
What is the minimum Chip speed/memory necessary to speed this screen fill? Or is INet speed the limiting factor here???

I5 chip on my computer/8GB memory.....Would a SSD Drive help? Or do I need a new computer?

+ If performance doesn't change when Windows is in "Safe Mode with Networking", then I suggest that you run the Windows Task Manager while you are running your amateur radio applications. Sorting by "CPU %" and then by "Memory" will indicate whether your CPU is "too busy", or whether your applications are consuming more RAM than is available. Assuming you have open slots, adding RAM is usually the least expensive way to improve performance - but if the problem is that your CPU is too slow for the applications you're trying to run simultaneously, adding RAM may not help much.

73,

Dave, AA6YQ

Re: SWL

Dave AA6YQ
 

+ AA6YQ comments below

After you print SWL labels and click on the Update Log button does it make any change to the log entry for that QSO?

+ No changes are made to a logged QSO for which an SWL report was generated.

73,

Dave, AA6YQ

Re: "which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

Dave AA6YQ
 

+ AA6YQ comments below

Thanks again for taking the time to provide that explanation.

If I may go back to the original question, because it appears I did not explain myself very well:

For seven of these award families, DXKeeper provides Realtime Award Tracking (RAT) service, which enables SpotCollector <https://www.dxlabsuite.com/spotcollector> to immediately identify active DX stations with whom a QSO would advance your award progress, and which enables DXKeeper to immediately identify QSOs whose confirmation would advance your award progress:"

SpotCollector does do that "Realtime", without having to run a filtered report, by displaying "Unworked DX Band or Mode" in one colored font, and "Unconfirmed DX" in another colored font.

Is there a way to configure DXKeeper to, in Realtime, "immediately identify QSOs whose confirmation would advance your award progress", similar to the way that SpotCollector does?

+ No. The CPU consumption required to do that in SpotCollector is well-justified, but there is no justification for doing that in DXKeeper.

+ In general, the reason you'd want to identify logged QSOs whose confirmation would advance your award progress is so you can generate outgoing QSL cards requesting those confirmation - an action you might take once a day if you're being aggressive about it. That's what the "Add Needed" function does.

+ If you'd like to filter the Log Page Display to show only QSOs whose confirmation would advance your award progress, you can take advantage of the fact that when adding a needed QSO to the "QSL Queue", the "Add Needed" function sets that QSO's Select item to 'Y'. So

1. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the X button to remove all filtering from the Log Page Display

2. On the Main window's "Check Progress" tab, click the "Clear Select" button at the bottom of the tab; this will clear the Select item in every logged QSO

3. Invoke the "Add Needed" function as previously suggested; if you're not going to be generating QSL cards, click the Clear button on the Main window's QSL tab

4. In the Filter panel at the bottom of the Main window's "Log QSOs" tab, click the Sel button; the Log Page Display will be filtered to contain only those QSOs whose confirmation would advance your award progress.

+ It should be noted that CQ DX Marathon does not require submission of confirmed QSOs. Thus while SpotCollector highlights active DX stations needed for CQ DX Marathon on the bands and modes you're pursuing, DXKeeper's "Add Needed" does not populate the QSL Queue with QSOs that you'll be submitting for CQ DX Marathon at the end of the year unless they are also needed for an award like DXCC or WAZ that requires confirmation.

73,

Dave, AA6YQ

Re: Remove R from QSL sent box

Dave AA6YQ
 

+ AA6YQ comments below

I guess that the (R)equested value is a default, but I don't remember if there is a setting modifiable by the user.

+ There is: the "Preset QSL Requested" option on the "QSL Configuration" window's General tab.

+ WinWarbler provides a similar "preset QSL checkbox" option in the "QSO Info" panel on its Configuration window's Log tab.

73,

Dave, AA6YQ

Re: What Computer Speed/Memory needed to fully and rapidly decode over 40 stations on a crowded band????

Peter Laws
 

On Wed, Apr 17, 2019 at 7:56 PM Email Service <jfriend31@...> wrote:

I have an i3 w 16 GB RAM SSD drive. No delays with screen full of traces. Running W10.
73 jack AK7O
Same config here (in an Intel NUC, which I really like) and have no
issues with FT8 (WAS on 30m/FT8 in 30 days :-)). I attribute any
delay to the software doing it's thing. I suppose a faster CPU would
make it go faster, but there is enough "think time" in the FT8 QSO
cycle that it hasn't been an issue.

Not sure I'd try it on a 90 MHz Pentium.



--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!

Re: What Computer Speed/Memory needed to fully and rapidly decode over 40 stations on a crowded band????

Email Service
 

I have an i3 w 16 GB RAM SSD drive. No delays with screen full of traces. Running W10.
73 jack AK7O

Sent from XFINITY Connect App



------ Original Message ------

From: Hugh Valentine
To: DXLab@groups.io
Sent: April 17, 2019 at 5:49 PM
Subject: [DXLab] What Computer Speed/Memory needed to fully and rapidly decode over 40 stations on a crowded band????

When a band is crowded with greater than 40 stations to decode I experience a delay of a couple of seconds to fill the screen in JTDX Alert.
Is this a function of CPU Speed or memory? 
What is the minimum Chip speed/memory necessary to speed this screen fill?  Or is INet speed the limiting factor here???

I5 chip on my computer/8GB memory.....Would a SSD Drive help?  Or do I need a new computer?

any insight would help steer me in the proper direction.....

Val
N4RJ