Date   

Re: DXAtlas

Dave AA6YQ
 

+ AA6YQ comments below

Almost 12000, hence the question when I clicked the "Plot" button I noticed a lot that weren't plotted.

+ I DX Atlas plots the ~26K QSOs in my log.

+ To plot all QSOs in your log,

- remove all Log Page Display filtering by clicking the X button in the Filter panel at the bottom of DXKeeper's Main window's "Log QSOs" tab

- in the Selection panel at the top of the "Plot Settings" tab of DXView's Configuration window, check the Unworked, Unconfirmed, Confirmed, and Verified boxes at the right side of the panel

+ DXView cannot plot a QSO that doesn't specify a grid square and whose location cannot be determined from its callsign and DXCC entity.

+ If you have a logged QSO that you think should be plotted but isn't being plotted, please let me know.

73,

Dave, AA6YQ


Re: Entering incomplete QSO info in DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

In DXKeeper -> Config -> Awards ... lower left check "Credit only QSO Creation".

Unfortunately, "Credit only QSO Creation" is not documented in the Help File.

+ Not true. Credit-only QSO Creation" is described in the reference documentation here:

<https://www.dxlabsuite.com/dxkeeper/Help/Progress.htm#Generating%20Credit-only%20QSOs>;

+ Alternatively, click one of DXKeeper's Help buttons, and navigate to

Checking and Managing Award Progress > Generating Submissions and Managing Award Credits > DXCC > Managing DXCC Credits > Generating Credit-only QSOs

+ I doubt that the learning curve required to master the downloading of DXCC credits is justified by the automated creation of ~30 QSOs.

73,

Dave, AA6YQ


QSRE: [DXLab] Entering incomplete QSO info in DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

I recently applied for DXCC via a LOTW request. LOTW also let me link in a previous callsign and I received an additional 30 countries credit from the 1970's. The 1970's countries are listed as MIXED (in LOTW) but have no band or mode data, only a date and no time is listed either. I was trying to enter them in DXKeeper (to track them) and even though I uncheck the box "Flag Invalid Callsigns", I still get flashing red messages next to mode and TX band windows. Is there a way to track these countries in DXKeeper? (maybe just make up band and mode info?)

+ Yes:

1. In the "Log Settings" panel on the Configuration window's Log tab, check the "Partial DXCC Credit" box

2. For each QSO for which you have Mixed DXCC credit, but not Entity-Band or Entity-Mode DXCC credit

2a. if you don't remember the QSO's band, set it to a band on which you've already confirmed (or at least worked) the QSO's entity; this will prevent DXLab from considering a needed entity-band as "already worked"

2b. if you don't remember the QSO's mode, set it to a mode in which you've already confirmed (or at least worked) the QSO's entity; this will prevent DXLab from considering a needed entity-mode as "already worked"

2c. if you didn't remember the QSO's band or mode, note this is the QSO's Comment item to help reduce future confusion (accessible via the Details panel on the Main window's "Log QSOs" tab)

2d. set the QSO's QSL_RCVD item to E (which means "Entity-only DXCC credit granted)

73,

Dave, AA6YQ


Re: DXAtlas

W7HPW Radio
 

Almost 12000, hence the question when I clicked the "Plot" button I noticed a lot that weren't plotted.


Real Radios Glow in the Dark

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Wednesday, August 26, 2020 5:55 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXAtlas

+ AA6YQ comments below

Is there a limit to how may QSO’s cam be ploted?

+ If DX Atlas imposes a limit, no one here has ever reported encountering it.

+ How many QSOs are present in your log?

73,

Dave, AA6YQ


Re: Entering incomplete QSO info in DXKeeper

Joe Subich, W4TV
 

In DXKeeper -> Config -> Awards ... lower left check "Credit only
QSO Creation".

Unfortunately, "Credit only QSO Creation" is not documented in the
Help File.

See: http://www.dxlabsuite.com/dxlabwiki/CreateCreditOnlyQSOs in
the DXLab Wiki

73,

... Joe, W4TV

On 2020-08-26 6:41 PM, Phil Deaver wrote:
I recently applied for DXCC via a LOTW request. LOTW also let me link in a previous callsign and I received an additional 30 countries credit from the 1970's. The 1970's countries are listed as MIXED (in LOTW) but have no band or mode data, only a date and no time is listed either. I was trying to enter them in DXKeeper (to track them) and even though I uncheck the box "Flag Invalid Callsigns", I still get flashing red messages next to mode and TX band windows. Is there a way to track these countries in DXKeeper? (maybe just make up band and mode info?)
73,
Phil WR7T


Re: DXAtlas

Dave AA6YQ
 

+ AA6YQ comments below

Is there a limit to how may QSO’s cam be ploted?

+ If DX Atlas imposes a limit, no one here has ever reported encountering it.

+ How many QSOs are present in your log?

73,

Dave, AA6YQ


Re: Computer lockup when I click on Upload to LotW

Dave AA6YQ
 

+ AA6YQ comments below

Reboot at least every morning, usually more than that. RAM 32GB. I will look at Windows Task Manager next time -- if it will let me :-)

+ Your reboot frequency and available RAM should be more than sufficient, unless you are running multiple protein folding or Bitcoin mining applications in the background.

+ Two other possibilities:

1. interference from a firewall or anti-malware application not configured to consider DXKeeper to be "safe"

2. misconfigured Windows Virtual Memory

+ The typical way to test for anti-malware interference is to reboot Windows into "safe mode with networking", as this does not start your firewall and anti-malware. I know it'll be a pain, but each time you have QSOs to upload, reboot Windows into "safe mode with networking", start the Launcher, direct the Launcher to start DXKeeper, and then direct DXKeeper to upload your QSOs to LoTW. If you do this 5 times in succession without the "can't run other applications while uploading" symptom appearing, then we'll have gained an important clue.

73,

Dave, AA6YQ


Entering incomplete QSO info in DXKeeper

Phil Deaver
 

I recently applied for DXCC via a LOTW request. LOTW also let me link in a previous callsign and I received an additional 30 countries credit from the 1970's. The 1970's countries are listed as MIXED (in LOTW) but have no band or mode data, only a date and no time is listed either. I was trying to enter them in DXKeeper (to track them) and even though I uncheck the box "Flag Invalid Callsigns", I still get flashing red messages next to mode and TX band windows. Is there a way to track these countries in DXKeeper? (maybe just make up band and mode info?)
73,
Phil WR7T


Re: DXAtlas

W7HPW Radio
 

Is there a limit to how may QSO’s cam be ploted?

 

Mark

W7HPW

 

 

Real Radios Glow in the Dark

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Monday, August 24, 2020 5:40 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXAtlas

 

+ AA6YQ comments below

After installing a Windows 10 update, when I click “plot” in DXKeeper, the only QSO that populates on DXAtlas is the QSO currently selected. In the past, all my QSO’s appeared.  I imagine that this is just a settings issue, but I am stumped. Any suggestions would be appreciated. 

+ Please review the step-by-step instructions in

<https://www.dxlabsuite.com/dxlabwiki/QSOPlottingDXAtlas>

+ If those don't get you going, let me know.

         73,

                Dave, AA6YQ


Re: Computer lockup when I click on Upload to LotW

Steve K8JQ
 

Reboot at least every morning, usually more than that. RAM 32GB. I will look at Windows Task Manager next time -- if it will let me  :-)

Thanks.

Steve, K8JQ


On 8/26/2020 12:57 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

For about half of the occasions when I click on Upload to LotW, my desktop computer locks up until the upload process is completed. The mouse still moves the cursor around the screen, but the computer is otherwise unresponsive. 

+ That's not a "lockup". That sounds like your system sometimes doesn't have sufficient resources to execute additional applications while the upload is underway. 

+ How frequently do you reboot Windows? 

+ How much RAM is installed in your system?

+ The next time your system slows when uploading to LoTW, start the Windows Task Manager and check to see which applications are consuming memory, and how much is being consumed.

       73,

                 Dave, AA6YQ






Re: Commander Multi Radio Secondary cat Port

Adrian Fewster
 

Dave, not sure if they vary in design but with the 1.5KFA when you switch to 2nd txcr input,

the required CAT connection shifts to the 2nd CAT connector also, which I have setup to PC, and it is on a different PC comport.

I am following the primary CAT with the SPE secondary Commander cat connection for both profiles, mainly for the 101 so it will also follow

SUB freq (on direct SPE<>Yaesu 101 cat conn, sub freq read is not possible), and it is also convenient with the KX3, no extra cables/adaptors needed.

So on your SPE amp how do you make one of the two CAT connectors work with both inputs? Perhaps your model SPE only has one CAT connection ?


Mine has two, one for each radio.


Thanks for the quick response.


Adrian Fewster

On 27/8/20 2:54 am, Dave AA6YQ wrote:
+ AA6YQ comments below

Dave, I use a SPE amp > PC connected to Commander 2nd cat following a FTDX101MP (radio 1), and a KX3 (radio 2),

also connected to the SPE in the same way, on a 2nd cat connection.

On Commander I can switch between 101 and KX3 in operation and toggle input 1 and 2 on the SPE to match.

However i have to manually reconfigure the secondary cat connection to the SPE for KX3 operation.

+ Manually reconfigure the secondary CAT port in what way?

+ I have Commander controlling my two primary transceivers (IC-7800 and Flex 6500), and my SPE amp connected to the secondary CAT port configured to "follow" the current primary transceiver. No reconfiguration is required when I switch primary transceivers.

73,

Dave, AA6YQ




Re: Computer lockup when I click on Upload to LotW

Dave AA6YQ
 

+ AA6YQ comments below

For about half of the occasions when I click on Upload to LotW, my desktop computer locks up until the upload process is completed. The mouse still moves the cursor around the screen, but the computer is otherwise unresponsive.

+ That's not a "lockup". That sounds like your system sometimes doesn't have sufficient resources to execute additional applications while the upload is underway.

+ How frequently do you reboot Windows?

+ How much RAM is installed in your system?

+ The next time your system slows when uploading to LoTW, start the Windows Task Manager and check to see which applications are consuming memory, and how much is being consumed.

73,

Dave, AA6YQ


Re: Commander Multi Radio Secondary cat Port

Dave AA6YQ
 

+ AA6YQ comments below

Dave, I use a SPE amp > PC connected to Commander 2nd cat following a FTDX101MP (radio 1), and a KX3 (radio 2),

also connected to the SPE in the same way, on a 2nd cat connection.

On Commander I can switch between 101 and KX3 in operation and toggle input 1 and 2 on the SPE to match.

However i have to manually reconfigure the secondary cat connection to the SPE for KX3 operation.

+ Manually reconfigure the secondary CAT port in what way?

+ I have Commander controlling my two primary transceivers (IC-7800 and Flex 6500), and my SPE amp connected to the secondary CAT port configured to "follow" the current primary transceiver. No reconfiguration is required when I switch primary transceivers.

73,

Dave, AA6YQ


Computer lockup when I click on Upload to LotW

Steve K8JQ
 

For about half of the occasions when I click on Upload to LotW, my desktop computer locks up until the upload process is completed. The mouse still moves the cursor around the screen, but the computer is otherwise unresponsive. On the other hand, for the other occasions when I click on Upload to LotW I can use the computer for other things while the upload process is in progress -- email, web browser, spreadsheet, etc.

I began using LotW in the spring of this year. No computer lock-up's until last month (July). While not the end of the world, the lock-up's are inconvenient and I'd like to avoid them.

Anyone have insight as to why the lock-up's happen sometimes and sometimes not? Are there configuration settings in DXLabs or Windows 10 that might help?

DXKeeper 15.7.2, Windows 10 Home 1909.

Thanks.

Steve, K8JQ



Commander Multi Radio Secondary cat Port

Adrian Fewster
 

Dave, I use a SPE amp > PC connected to Commander 2nd cat following a FTDX101MP (radio 1), and a KX3 (radio 2),

also connected to the SPE in the same way, on a 2nd cat connection.

On Commander I can switch between 101 and KX3 in operation and toggle input 1 and 2 on the SPE to match.

However i have to manually reconfigure the secondary cat connection to the SPE for KX3 operation.

Is there a way in MultiRadio section to provide a secondary cat list 1-4 CAT type & port settings to match radio 1-4, so

when radio is changed, the matching secondary CAT profile with its settings is auto set with the radio change ?


Thankyou for any consideration or remedy for this


Adrian Fewster


Re: WinWarbler

Joe Subich, W4TV
 

On 2020-08-25 2:34 PM, Dave AA6YQ wrote:

+ If one is emulating hardware and only expects to employ a single application with that emulation, then it is reasonable to determine
what subset of the hardware specification must be implemented to
"satisfy" that application, and limit the emulation to that
functionality to avoid spending time implementing emulation
functionality that the application will not use. However, if you
intend to use multiple applications with that emulation, then it is
generally better to emulate the hardware's full functionality.
Here's the rub ... Bo says his application (a WinKeyer emulator) works
fine with one application - K1EL's WK3 Demo (but he doesn't say which
version of WK3 Demo - there have been at least three released) but
fails with WinWrbler. Thus he has not implemented a sufficiently
complete version of the WinKey emulation to satisfy the multiple
applications.

I have no doubt that K1EL deigned WK3 to be tolerant of WK1/WK2
compliant applications - that is I can use WK Demo (for WK1/WK2)
to "talk to" WK3 and control those features that are common to
WK2 and WK3. *HOWEVER*, I can not use WK3 Demo to "talk to" or
control WK1 or WK2 as WK3 Demo (v.41) will fail to open either
WK1 or WK2 devices.

73,

... Joe, W4TV


On 2020-08-25 2:34 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
I'm trying to understand the documentation for WK3 but
obviously I'm
failing.
You can not limit yourself to WK3. There are significant issues in
maintaining backward compatibility with WK 1 and WK 2. Study the
documentation on *ALL THREE* versions to understand the full range
of requirements for "WinKey compatibility".
Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.
+ No one has reported any problems with WinWarbler interoperating with any version of WinKey. If a defect is reported, I will of course correct it.
+ If one is emulating hardware and only expects to employ a single application with that emulation, then it is reasonable to determine what subset of the hardware specification must be implemented to "satisfy" that application, and limit the emulation to that functionality to avoid spending time implementing emulation functionality that the application will not use. However, if you intend to use multiple applications with that emulation, then it is generally better to emulate the hardware's full functionality.
+ Bo, I've been unable to help because none of the strings you have posted are valid WinKey commands, so I can't tell what your emulator is doing.
       73,
              Dave, AA6YQ


Re: WinWarbler

Joe Subich, W4TV
 

Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.
Because WK3 does not require the CMD MODE OFF command when starting.
WK3 fores command mode off whenever the serial port is closed - that
was not the case with WK1 (and perhaps WK2 - I'd have to go back to
the developers/programmers documentation). There are other subtle
differences in behavior (e.g. the behavior of PTT tail and a difference
PTT delay for paddle vs. ASCII data) among the three WK families (as
well as among firmware versions *within* families).

The "WK" protocol is not monolithic and can't be treated as such.

73,

... Joe, W4TV


On 2020-08-25 1:12 PM, iain macdonnell - N6ML wrote:
On Tue, Aug 25, 2020 at 5:05 AM Joe Subich, W4TV <lists@subich.com> wrote:


On 2020-08-25 3:14 AM, sm6fpg wrote:
I'm trying to understand the documentation for WK3 but obviously I'm
failing.
You can not limit yourself to WK3. There are significant issues in
maintaining backward compatibility with WK 1 and WK 2. Study the
documentation on *ALL THREE* versions to understand the full range
of requirements for "WinKey compatibility".
Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.
73,
~iain / N6ML

On 2020-08-25 3:14 AM, sm6fpg wrote:
I'm trying to understand the documentation for WK3 but obviously I'm failing.
I'll see if I can find any source code for some programs to try to understand it all better!
Thank you for your commitment!

73,
SM6FPG/Bo


Re: WinWarbler

iain macdonnell - N6ML
 

On Tue, Aug 25, 2020 at 11:34 AM Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

I'm trying to understand the documentation for WK3 but obviously I'm
failing.

You can not limit yourself to WK3. There are significant issues in
maintaining backward compatibility with WK 1 and WK 2. Study the
documentation on *ALL THREE* versions to understand the full range
of requirements for "WinKey compatibility".

Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.

+ No one has reported any problems with WinWarbler interoperating with any version of WinKey. If a defect is reported, I will of course correct it.

+ If one is emulating hardware and only expects to employ a single application with that emulation, then it is reasonable to determine what subset of the hardware specification must be implemented to "satisfy" that application, and limit the emulation to that functionality to avoid spending time implementing emulation functionality that the application will not use. However, if you intend to use multiple applications with that emulation, then it is generally better to emulate the hardware's full functionality.
Agreed. I was just noting that there's no need for Bo to emulate
WinKeyer v1, unless he needs to interoperate with some application
that only supports v1.


+ Bo, I've been unable to help because none of the strings you have posted are valid WinKey commands, so I can't tell what your emulator is doing.
Same. That's why I asked for detail on the exchange up to the point of
failure (at the raw byte value level).

73,

~iain / N6ML


Re: WinWarbler

Dave AA6YQ
 

+ AA6YQ comments below

I'm trying to understand the documentation for WK3 but obviously I'm
failing.
You can not limit yourself to WK3. There are significant issues in
maintaining backward compatibility with WK 1 and WK 2. Study the
documentation on *ALL THREE* versions to understand the full range
of requirements for "WinKey compatibility".
Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.

+ No one has reported any problems with WinWarbler interoperating with any version of WinKey. If a defect is reported, I will of course correct it.

+ If one is emulating hardware and only expects to employ a single application with that emulation, then it is reasonable to determine what subset of the hardware specification must be implemented to "satisfy" that application, and limit the emulation to that functionality to avoid spending time implementing emulation functionality that the application will not use. However, if you intend to use multiple applications with that emulation, then it is generally better to emulate the hardware's full functionality.

+ Bo, I've been unable to help because none of the strings you have posted are valid WinKey commands, so I can't tell what your emulator is doing.

       73,

              Dave, AA6YQ

 


Re: WinWarbler

iain macdonnell - N6ML
 

On Tue, Aug 25, 2020 at 5:05 AM Joe Subich, W4TV <lists@subich.com> wrote:


On 2020-08-25 3:14 AM, sm6fpg wrote:
I'm trying to understand the documentation for WK3 but obviously I'm
failing.
You can not limit yourself to WK3. There are significant issues in
maintaining backward compatibility with WK 1 and WK 2. Study the
documentation on *ALL THREE* versions to understand the full range
of requirements for "WinKey compatibility".
Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.

73,

~iain / N6ML


On 2020-08-25 3:14 AM, sm6fpg wrote:
I'm trying to understand the documentation for WK3 but obviously I'm failing.
I'll see if I can find any source code for some programs to try to understand it all better!
Thank you for your commitment!

73,
SM6FPG/Bo


3141 - 3160 of 199058