DXLab@groups.io | Messages

Re: Using Multiple Flex Radios in Commander Setup

Dave AA6YQ

#186774

+ AA6YQ comments below

Between the information both of you gave me, I have been able to get the "MultiRadio" tap of Commander working. I configured the "Control" section, including the Flex radios "Select" button with the radios serial numbers. I'm not sure if I need them or not, but it works, so for now I'm leaving them in there. Under the "Cat Serial port" section, I set up the Port # with the "-" (I assume it means "no port selected") and then filled in the "Baud, Word, Parity, Stop, DTR and RTS boxes. I was then able to check the "Enable" boxes in the "Control" section, which gave then gave me the "radio names" on the main Commander screen and the ability to switch between them.

Thank you Al and Dave! I don't think I would have figured that one out, without your help.

+ The current version of Commander only requires a primary radio's serial port parameters to be set on the Configuration window's MultiRadio tab if the radio uses a serial port to interact with Commander. In the Radios.txt file that Commander consults to see which radios use a serial port to interact with Commander, only the Kachina and the TenTec Pegasus are designated as "no serial port required". Because Flex Signature radios can interact with Commander via a serial port, they are not designated as "no serial port required".

Rather than designate all Flex Signature radio's as "no serial port require", I have modified the next version of Commander to drop the "serial port and its parameters must be specified in order to check Enable" requirement, as it's doing more harm than good. If you're controlling multiple primary transceivers, have a primary transceiver that interacts with Commander via a serial ,  but fail to specify the serial port parameters on the Configuration window's MultiRadio tab, then when you select that radio, the "Primary CAT Serial Port" panel on the Configuration window's Ports tab will not be correctly configured, which should be easy to notice and correct.

       73,

               Dave, AA6YQ

Re: Using Multiple Flex Radios in Commander Setup

Henry Boze

#186773

Al and Dave,

Between the information both of you gave me, I have been able to get the "MultiRadio" tap of Commander working. I configured the "Control" section, including the Flex radios "Select" button with the radios serial numbers. I'm not sure if I need them or not, but it works, so for now I'm leaving them in there. Under the "Cat Serial port" section, I set up the Port # with the "-" (I assume it means "no port selected") and then filled in the "Baud, Word, Parity, Stop, DTR and RTS boxes. I was then able to check the "Enable" boxes in the "Control" section, which gave then gave me the "radio names" on the main Commander screen and the ability to switch between them.

Thank you Al and Dave! I don't think I would have figured that one out, without your help.

73,

Henry, N4HB

Show quoted text

On Wed, Jul 17, 2019 at 10:57 AM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

AL, K0VM wrote:

?? One think I have noticed, it that for multi radio & flex, the commander MultiRadio setup screen still needs to have com ports specified for each radio even though they are not used..

+ That's not correct, Al.

+ I have a Flex 6500 configured as Radio #2. On the MultiRadio tab of Commander's Configuration window, the "CAT Serial Port" panel's "Port #" selector for Radio #2 is set to - (meaning no serial port specified).

73,

Dave, AA6YQ

wsjtx 2.1.0 broke auto-logging

N6MZ Michael Mraz

#186772

Auto-logging via SpotCollector had been working FB until I switched from wsjtx 2.0.1 to 2.1.0 today. SpotCollector still receives spots but DXKeeper doesn't see any log data. I think the bullet item "Improved UDP messaging for inter-program communication" on the wsjtx web site may be a clue. 73

Re: Error auto uploading to Clublog #poll

Carl - WC4H

#186771

Mine seems to be fixed now.

73.
Carl - WC4H

Re: DXKeeper - ERROR:crash_report_database_win.cc(469)] failed to stat report

Dave Corio

#186770

Thanks, Dave! I naturally assumed being in the DXKeeper directory it was created by that program. I do have Chrome in use as the browser for DXKeeper, so will attack it from that direction!

Tnx es 73
Dave - KB3MOW

Show quoted text

On 7/17/2019 11:02 AM, Dave AA6YQ wrote:
+ AA6YQ comments below
This error began showing up last night. It is actually named "debug.log" in the DXKeeper folder, although the actual ErrorLog.txt is empty.
This morning I ran 5 QSOs in FT4 mode, and the debug.log now contains 5 entries of
[0717/092548.978:ERROR:crash_report_database_win.cc(469)] failed to stat report
With all five QSOs I was able to upload to LotW and eqsl, as well as uploading to ClubLog.
I verified that Debug Mode is turned off and have no idea why this has started. I looked up the "469" error in the forum, but what I found didn't help, as I'm using the current version of 15.0.0.
Any help appreciated!
+ There is no DXLab application that creates a file named debug.log
+ Direct your web browser to search for
crash_report_database_win
+ and you'll find multiple results indicating that Google Chrome is the source of the error messages. There are several recommendations for corrective action, but I recommend that you first contact Google Technical Support.
73,
Dave, AA6YQ

Re: Help with WW and Commander setup for Elecraft K3S

Mike Flowers

#186769

Have you begun your macro sequence with a ‘ character, as in:

'FA00014074000;VX0;MD6;DT0;XF2;MN255;MN053;UP;UP;MG003;ML002;MN255;#CTF+00014075500;#SPN000040;

This macro works FB on my K3.

- 73 and good DX de Mike, K6MKF, NCDXC Secretary

Show quoted text

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Daryl Popowitch
Sent: Wednesday, July 17, 2019 08:48
To: DXLab@groups.io
Subject: [DXLab] Help with WW and Commander setup for Elecraft K3S

Have a K3s and trying to use WinWarbler through Commander to run the K3S. My macros, which I have used for years in a stand alone fashion, do not PTT the rig, nor execute. Commander reads the rig frequency, allows Tx and Rx by clicking on the buttons. Watching messages through Commander, nothing is sent to the rig when clicking on a macro, but Tx and Rx button clicking shows messages going to the rig.

Commander shows messages for mode changes, and WW changes when clicking on those Commander buttons. Commander frequency display changes with VFO frequency change.

By running WW, DXKeeper, DXView, and Commander together, something in the setup must have been missed by me, but I cannot find it.

Thanks for any help.

73,

Daryl - N8AID

Help with WW and Commander setup for Elecraft K3S

Daryl Popowitch

#186768

Have a K3s and trying to use WinWarbler through Commander to run the K3S. My macros, which I have used for years in a stand alone fashion, do not PTT the rig, nor execute. Commander reads the rig frequency, allows Tx and Rx by clicking on the buttons. Watching messages through Commander, nothing is sent to the rig when clicking on a macro, but Tx and Rx button clicking shows messages going to the rig.

Commander shows messages for mode changes, and WW changes when clicking on those Commander buttons. Commander frequency display changes with VFO frequency change.

By running WW, DXKeeper, DXView, and Commander together, something in the setup must have been missed by me, but I cannot find it.

Thanks for any help.

73,

Daryl - N8AID

Re: DXKeeper - ERROR:crash_report_database_win.cc(469)] failed to stat report

Dave AA6YQ

#186767

+ AA6YQ comments below

This error began showing up last night. It is actually named "debug.log" in the DXKeeper folder, although the actual ErrorLog.txt is empty.

This morning I ran 5 QSOs in FT4 mode, and the debug.log now contains 5 entries of

          [0717/092548.978:ERROR:crash_report_database_win.cc(469)] failed to stat report

With all five QSOs I was able to upload to LotW and eqsl, as well as uploading to ClubLog.

I verified that Debug Mode is turned off and have no idea why this has started. I looked up the "469" error in the forum, but what I found didn't help, as I'm using the current version of 15.0.0.

Any help appreciated!

+ There is no DXLab application that creates a file named debug.log

+ Direct your web browser to search for 

crash_report_database_win

+ and you'll find multiple results indicating that Google Chrome is the source of the error messages. There are several recommendations for corrective action, but I recommend that you first contact Google Technical Support.

       73,

               Dave, AA6YQ

Re: Using Multiple Flex Radios in Commander Setup

Dave AA6YQ

#186766

+ AA6YQ comments below

AL, K0VM wrote:

?? One think I have noticed, it that for multi radio & flex, the commander MultiRadio setup screen still needs to have com ports specified for each radio even though they are not used.. 

+ That's not correct, Al.

+ I have a Flex 6500 configured as Radio #2. On the MultiRadio tab of Commander's Configuration window, the "CAT Serial Port" panel's "Port #" selector for Radio #2 is set to -  (meaning no serial port specified).

      73,

             Dave, AA6YQ

Re: Using Multiple Flex Radios in Commander Setup

Dave AA6YQ

#186765

* AA6YQ comments below

Yes, I can control each radio by itself when I select the Flex model and then fill in the radios serial number in "Radio Selection" field under the "General" tab. Controlling one radio at a time works fine.

* Good!

* Please do the following on the Configuration window's MultiRadio tab:

1. in the "Radio 1" row

1a. set the Model selector to SDR-6600

1b. set the Name to 6600M

1c. click the Select button to the right of the Model selector, and specify your 6600M's serial number in the "Flex Signature Selection" window that appears

1.d set the Interval to 100

1.e check the Interrogate box

1.f check the Enable box

2. in the "Radio 2" row

2a. set the Model selector to SDR-6400

2b. set the Name to 6400

2c. click the Select button to the right of the Model selector, and specify your 6400's serial number in the "Flex Signature Selection" window that appears

2.d set the Interval to 100

2.e check the Interrogate box

2.f check the Enable box

* On Commander's Main window, you should see selection buttons labeled 6600M and 6400 beneath the XFC button in the VFO panel. Clicking one of them should connect Commander to that radio.

         73,

                    Dave, AA6YQ

Show quoted text

On Tue, Jul 16, 2019 at 9:49 PM Dave AA6YQ <@AA6YQ> wrote:

    + AA6YQ comments below
    
    I'm just getting started with DXLab and am in the process of configuring "Commander" to communicate with my Flex 6600M and 6400 radios. I'm trying to create the ability to switch between the two using the "MultiRadio" tab in the "Commander" config section. I'm on an internal IP network, not using any CAT or Serial control ports. Under the "Control" section of the setup, I selected SDR-6600 as Radio #1, checked "Interrogate", gave it an "Interval" of 200 and gave it a "Name". Under "Radio #2, I selected SDR-6400 and repeated the above selections for it.  When I went to check the "Enable" box, I was unable to do so. The boxes stayed unchecked. There is no option on the "Commander" main screen to select the different radios, which I assume if it were "Enabled" would be. I can only control the Flex 6600, which was selected on the "General" Tab under Radio Selection, which I filled in with the radios Serial Number and IP Address. Another DXLab user told me that I should have been able to check the "Enable" boxes in the Control window of the "MultiRadio" config, but I cannot. I also tried to fill in the "Select" windows of each radio, where it asks for each radios "Serial Number, IP Address and IP Port, but that did not work either. In reading the "Help" files concerning those particular tabs, it appears they don't have to be filled in using the radios that I am using, only the Flex 6300, 6500 and 6700 series of radios. What am I missing? Thanks in advance for any help you can give me!
    
    + Before attempting to configure Commander to control one of several Primary Transceivers using the Configuration window's MultiRadio tab, you should first configure the General tab of Commander's Configuration window to successively control each of your Primary Flex Transceivers; the only difference should be the Model selector setting and the "Serial Number" in the "Radio Selection" panel. Is Commander able to control each of your transceivers if you manually set these to the correct value?
    
            73,
    
                   Dave, AA6YQ
    
 <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>      Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: Using Multiple Flex Radios in Commander Setup

Al Groff

#186764

Correction .. needs to have CAT serial ports specified...
AL, K0VM

Show quoted text

On 7/17/2019 9:49 AM, Al K0VM wrote:

Harry,
?? One think I have noticed, it that for multi radio & flex, the commander MultiRadio setup screen still needs to have com ports specified for each radio even though they are not used..
AL, K0VM

On 7/17/2019 7:30 AM, Henry Boze wrote:

Yes, I can control each radio by itself when I select the Flex model and then fill in the radios serial??number in "Radio Selection" field under the "General" tab. Controlling one radio at a time works fine.

Henry, N4HB

On Tue, Jul 16, 2019 at 9:49 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I'm just getting started with DXLab and am in the process of configuring "Commander" to communicate with my Flex 6600M and 6400 radios. I'm trying to create the ability to switch between the two using the "MultiRadio" tab in the "Commander" config section. I'm on an internal IP network, not using any CAT or Serial control ports. Under the "Control" section of the setup, I selected SDR-6600 as Radio #1, checked "Interrogate", gave it an "Interval" of 200 and gave it a "Name". Under "Radio #2, I selected SDR-6400 and repeated the above selections for it.?? When I went to check the "Enable" box, I was unable to do so. The boxes stayed unchecked. There is no option on the "Commander" main screen to select the different radios, which I assume if it were "Enabled" would be. I can only control the Flex 6600, which was selected on the "General" Tab under Radio Selection, which I filled in with the radios Serial Number and IP Address. Another DXLab user told me that I should have been able to check the "Enable" boxes in the Control window of the "MultiRadio" config, but I cannot. I also tried to fill in the "Select" windows of each radio, where it asks for each radios "Serial Number, IP Address and IP Port, but that did not work either. In reading the "Help" files concerning those particular tabs, it appears they don't have to be filled in using the radios that I am using, only the Flex 6300, 6500 and 6700 series of radios. What am I missing? Thanks in advance for any help you can give me!

+ Before attempting to configure Commander to control one of several Primary Transceivers using the Configuration window's MultiRadio tab, you should first configure the General tab of Commander's Configuration window to successively control each of your Primary Flex Transceivers; the only difference should be the Model selector setting and the "Serial Number" in the "Radio Selection" panel. Is Commander able to control each of your transceivers if you manually set these to the correct value?

?? ?? ?? ?? 73,

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

Re: Using Multiple Flex Radios in Commander Setup

Al Groff

#186763

Harry,
?? One think I have noticed, it that for multi radio & flex, the commander MultiRadio setup screen still needs to have com ports specified for each radio even though they are not used..
AL, K0VM

Show quoted text

On 7/17/2019 7:30 AM, Henry Boze wrote:

Yes, I can control each radio by itself when I select the Flex model and then fill in the radios serial??number in "Radio Selection" field under the "General" tab. Controlling one radio at a time works fine.

Henry, N4HB

On Tue, Jul 16, 2019 at 9:49 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I'm just getting started with DXLab and am in the process of configuring "Commander" to communicate with my Flex 6600M and 6400 radios. I'm trying to create the ability to switch between the two using the "MultiRadio" tab in the "Commander" config section. I'm on an internal IP network, not using any CAT or Serial control ports. Under the "Control" section of the setup, I selected SDR-6600 as Radio #1, checked "Interrogate", gave it an "Interval" of 200 and gave it a "Name". Under "Radio #2, I selected SDR-6400 and repeated the above selections for it.?? When I went to check the "Enable" box, I was unable to do so. The boxes stayed unchecked. There is no option on the "Commander" main screen to select the different radios, which I assume if it were "Enabled" would be. I can only control the Flex 6600, which was selected on the "General" Tab under Radio Selection, which I filled in with the radios Serial Number and IP Address. Another DXLab user told me that I should have been able to check the "Enable" boxes in the Control window of the "MultiRadio" config, but I cannot. I also tried to fill in the "Select" windows of each radio, where it asks for each radios "Serial Number, IP Address and IP Port, but that did not work either. In reading the "Help" files concerning those particular tabs, it appears they don't have to be filled in using the radios that I am using, only the Flex 6300, 6500 and 6700 series of radios. What am I missing? Thanks in advance for any help you can give me!

+ Before attempting to configure Commander to control one of several Primary Transceivers using the Configuration window's MultiRadio tab, you should first configure the General tab of Commander's Configuration window to successively control each of your Primary Flex Transceivers; the only difference should be the Model selector setting and the "Serial Number" in the "Radio Selection" panel. Is Commander able to control each of your transceivers if you manually set these to the correct value?

?? ?? ?? ?? 73,

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

FW: [Club Log] Cloudflare note

Dave AA6YQ

#186762

Message from Michael G7VJR re ClubLog's new use of Cloudflare:

-----------------------
Hi all

As of yesterday, Club Log is using Cloudflare, which is an internet service that stops malicious traffic. As part of Cloudflare's functionality, it blocks traffic which looks suspicious or doesn't comply with the normal standards. However, there is a chance that these decisions can be false positives. I am looking through a list of which requests have been blocked and why, and making some exceptions. If you see an error, if you could let me know the date/time (to a few seconds) when you see the error, I'll look at the log here for the specifics.

Thanks for the feedback and help!

73
Michael G7VJR

PS. Yes, Club Log does get attacked pretty much around the clock. Miserable sods.

-----------------------

If you encounter a Cloudfare error message when uploading to Clublog, please send the information requested above to Michael via

michael (at) wells.org.uk

       73,

              Dave, AA6YQ

DXKeeper - ERROR:crash_report_database_win.cc(469)] failed to stat report

Dave Corio

#186761

This error began showing up last night. It is actually named "debug.log" in the DXKeeper folder, although the actual ErrorLog.txt is empty.

This morning I ran 5 QSOs in FT4 mode, and the debug.log now contains 5 entries of

[0717/092548.978:ERROR:crash_report_database_win.cc(469)] failed to stat report

With all five QSOs I was able to upload to LotW and eqsl, as well as uploading to ClubLog.

I verified that Debug Mode is turned off and have no idea why this has started. I looked up the "469" error in the forum, but what I found didn't help, as I'm using the current version of 15.0.0.

Any help appreciated!

Tnx es 73
Dave - KB3MOW

Re: Using Multiple Flex Radios in Commander Setup

Henry Boze

#186760

Yes, I can control each radio by itself when I select the Flex model and then fill in the radios serial number in "Radio Selection" field under the "General" tab. Controlling one radio at a time works fine.

Henry, N4HB

Show quoted text

On Tue, Jul 16, 2019 at 9:49 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I'm just getting started with DXLab and am in the process of configuring "Commander" to communicate with my Flex 6600M and 6400 radios. I'm trying to create the ability to switch between the two using the "MultiRadio" tab in the "Commander" config section. I'm on an internal IP network, not using any CAT or Serial control ports. Under the "Control" section of the setup, I selected SDR-6600 as Radio #1, checked "Interrogate", gave it an "Interval" of 200 and gave it a "Name". Under "Radio #2, I selected SDR-6400 and repeated the above selections for it. When I went to check the "Enable" box, I was unable to do so. The boxes stayed unchecked. There is no option on the "Commander" main screen to select the different radios, which I assume if it were "Enabled" would be. I can only control the Flex 6600, which was selected on the "General" Tab under Radio Selection, which I filled in with the radios Serial Number and IP Address. Another DXLab user told me that I should have been able to check the "Enable" boxes in the Control window of the "MultiRadio" config, but I cannot. I also tried to fill in the "Select" windows of each radio, where it asks for each radios "Serial Number, IP Address and IP Port, but that did not work either. In reading the "Help" files concerning those particular tabs, it appears they don't have to be filled in using the radios that I am using, only the Flex 6300, 6500 and 6700 series of radios. What am I missing? Thanks in advance for any help you can give me!

+ Before attempting to configure Commander to control one of several Primary Transceivers using the Configuration window's MultiRadio tab, you should first configure the General tab of Commander's Configuration window to successively control each of your Primary Flex Transceivers; the only difference should be the Model selector setting and the "Serial Number" in the "Radio Selection" panel. Is Commander able to control each of your transceivers if you manually set these to the correct value?

73,

Dave, AA6YQ

Re: Error auto uploading to Clublog #poll

John Bastin

#186759

On 16Jul 2019, at 20:53, Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

Same, still broken here 

+ I have alerted Michael G7VJR, who operates Club Log.This morning at 05:21 according to my mail client, I received an email from Michael that he apparently sent out to all Club Log users regarding the start of using CloudFlare for additional security, and the possibilities of failures thereof.

I sent him a screenshot of my failure message, and hopefully he is working on the problem and will be successful getting it corrected.

73,

John K8AJS
jbastin1@...
CWOps 1694
Ten-X 11306

Re: QSL queue Count Down after LoTW Upload (gets slower and slower)

Dave AA6YQ

#186758

+ AA6YQ comments below

Hi, thanks for the responses... Carl, it's not that LoTW is bogged down, it's after the upload has taken place.  And the speed / slowdown is consistent regardless if I upload right after a contest or a few days later.  It's definitely, not a scale issue of the LoTW website.

For Dave further review, I have noticed this on several PC's over the years.  The current PC is a 8700K 6 core 12 thread machine with 16 gigs of ram and a crazy fast M.2 Samsung fastest SSD you can buy right now. 

+ With enough load and/or suboptimal Windows virtual memory configuration, any machine can be made to thrash. If I had to guess, I'd attribute this behavior to the Jet Database Engine having to update 1000+ logged QSOs.

I'm curious now. :)  I'll make a video next time of an import and capture some of the other details... in the video, ram / CPU etc... show the disk usage. 

+ There's no need to send me a video; I believe your report.

 I realize this is VB6 32 bit single threaded code correct?, so the process would be limited to less than 4gb of ram, but more likely around 3.5gb of ram.

+ VB6 generated 32-bit code. I don't know what threading model it uses.

Again, far from a show stopper, but I have always wondered why the DB updates (I assumed) after the upload to LoTW would progressively get slower and slower.

I'll let you know when I gather some more details to diagnose this.

+ If it bothers you, you can use TQSL to digitally sign and upload your 1000+ QSO contest log (specifying the correct "Station Callsign" and "Station Callsign") and then import that same contest log into DXKeeper. After giving LoTW enough time to process your upload, invoking "Sync LoTW QSOs" on the QSL tab of DXKeeper's Main window will update your contest QSOs in DXKeeper to reflect acceptance by LoTW, as if you'd submitted them from DXKeeper. 

        73,

              Dave, AA6YQ

Re: DXCC award. questions before the inevitable

Dave AA6YQ

#186757

Finally I got the "slip" from lotw and did a CTRL update qsl from lotw and almost 900 qso were promoted to V status.

But, while checking , i found out that those V qso's belong to the DXCC award application only, although I did apply to, and paid for, WAS and WAZ awards.
The funny thing is that on LOTW site, when i click on the WAS and WAZ awards, I see an asterisk near Mixed, FT8 and some other categories, showing that "AWARD has been issued".

currently, on my WAX and WAS tab in RAT I only have W and C but not a single V, which is not the case in DXCC tab where I have W, C and V

My question is, should I promote those qso's in DXK as V? should it be promoted  under QSL, or WAS vfy or WAZ vfy according to the award purpusoe.? My guess is that it should be promoted to V both in qsl and corresponding award.
Am I correct?

please note that the WAZ award verifcation was sent to CQ award manager, John, and payment was effected to CQ for 2 awards.

+ The ARRL provides no programmatic means by which an application like DXKeeper can determine whether a QSO has been granted WAS or VUCC award credit.

+ CQ provides no programmatic means by which an application like DXKeeper can determine whether a QSO has been granted WAZ or WPX award credit.

+ For IOTA, you can obtain a tab-delimited file containing your IOTA award progress and direct DXKeeper to update your logged QSOs to reflect the status specified in this file.

+ For DXCC, DXKeeper can determine which QSOs have been granted DXCC award credit by downloading HTML from the web page showing your DXCC award status, extracting DXCC award credit information from the HTML, and then downloading each DXCC award credit, and attempting to associate it with a logged QSO. The DXKeeper Credit Manager provides this functionality:

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

+ Also for DXCC,  the LoTW API that DXKeeper invokes when you click "Sync LoTW QSLs" reports DXCC award credit granted to LoTW confirmations, as well as confirmations. However, this API does not report DXCC award credit granted to QSL card confirmations.

+ What users want is the ability to apply for DXCC, IOTA, VUCC, WAS, WAZ, or WPX awards, and then after receiving an "all ok" report from the award sponsor, be able to update their logged QSOs with a mouse click or two to indicate "award credit granted".

+ DXKeeper does this by maintain award status items in every logged QSO:

For DXCC: "QSL RCVD" and "LOTW QSL Rcvd"

For IOTA: IOTAVerified

For VUCC: VUCCVerified

for WAS: WASVerified

for WAZ: WAZVerified

for WPX: WPXVerified

+ Each of these items is described in <https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

+ All of these items except "LoTW QSL Rcvd" are accessible via the QSL panel on the Main window's "Log QSOs" tab. "LoTW QSL Rcvd" is accessible via the "Online QSL" panel on the Main window's "Log QSOs" tab.

+ When you direct DXKeeper to select a set of QSOs to be submitted for an award - a process the documentation refers to as "assembling a submission" -- DXKeeper chooses the optimum set of confirmed QSOs, and in each chosen QSO changes the appropriate award status item from Y (confirmed) to S (submitted). For example, if you direct DXKeeper to generate a WAS submission, it will change the WASVerified item of each chosen QSO from 'Y' to 'S'. When you click the "View Submission" button on DXKeeper's "WAS Submission" window, it filters the Log Page Display with

WASVerified='S'

+ When you click the "Create Submission Report" button on DXKeeper's "WAS Submission" window, DXKeeper generates creates a submission report in the correct format the includes all QSOs whose WASVerified items are set to 'S'.

+ When after submitting your WAS application, you receive a report from the ARRL saying "all QSOs submitted were granted WAS award credit", clicking the "Verify Submission" button on DXKeeper's "WAS Submission" window causes DXKeeper to update each QSO whose WASVerified item is set to 'S' by changing that WASVerified item to 'V', meaning "award credit granted. If the report from the ARRL indicated that WAS credit was withheld from two QSOs, you would manually change the "WASVerified" items in those two QSOs from 'S' to 'Y' - or maybe from 'S' to 'I' (invalid) if the QSOs will never count fro WAS credit - before clicking the "Verify Submission" button.

+ This workflow

1. assemble submission
2. review submission
3. create submission report
4. send application to award sponsor
5. receive results from award sponsor
6, verify submission

+ is provided for DXCC, IOTA, VUCC, WAS, WAZ, and WPX awards. It only works, however, if the QSOs you plan to submit have their award status items set to 'S' - either because you invoked the "Assemble Submission" function (step 1), or because you manually chose the QSOs to be submitted and manually set their award progress items to 'S'.  For example, if you know you have one newly confirmed QSO to submit to complete 160m WAS, you could simply set its WASVerified item to 'S', and then invoke "Create Submission Report" (step 3) to generate the paperwork.

+ The DXCC Credit Manager and the ability of "Sync LoTW QSLs" to update logged QSOs to reflect award credit granted to LoTW confirmations give you additional options for DXCC awards. Similarly, the "IOTA Update" function gives you an additional option for IOTA. 

+ My advice is to use the workflow described above for all awards.

+ So if you used DXKeeper's Submission generator to assemble your WAS and WAZ submissions, and if each award sponsor's report was "award credit granted to all submitted QSOs", then clicking the "WAS Submission" window's "Verify Submission" button and the 'WAZ Submission" window's "Verify Submission" button is the right next step. If you're at all unsure, direct DXKeeper to create a log backup before performing these actions, and then invoke "View Submission" in the  "WAS Submission" window and in the "WAZ Submission" window to confirm that the QSOs shown in the Log Page Display are indeed those to which award credit was granted.

           73,

                 Dave, AA6YQ

Re: QSL queue Count Down after LoTW Upload (gets slower and slower)

Max NG7M

#186756

Hi, thanks for the responses... Carl, it's not that LoTW is bogged down, it's after the upload has taken place. And the speed / slowdown is consistent regardless if I upload right after a contest or a few days later. It's definitely, not a scale issue of the LoTW website.

For Dave further review, I have noticed this on several PC's over the years. The current PC is a 8700K 6 core 12 thread machine with 16 gigs of ram and a crazy fast M.2 Samsung fastest SSD you can buy right now.

I'm curious now. :) I'll make a video next time of an import and capture some of the other details... in the video, ram / CPU etc... show the disk usage. I realize this is VB6 32 bit single threaded code correct?, so the process would be limited to less than 4gb of ram, but more likely around 3.5gb of ram.

Again, far from a show stopper, but I have always wondered why the DB updates (I assumed) after the upload to LoTW would progressively get slower and slower.

I'll let you know when I gather some more details to diagnose this.

Thanks! Max NG7M

Re: Using Multiple Flex Radios in Commander Setup

Dave AA6YQ

#186755

+ AA6YQ comments below

I'm just getting started with DXLab and am in the process of configuring "Commander" to communicate with my Flex 6600M and 6400 radios. I'm trying to create the ability to switch between the two using the "MultiRadio" tab in the "Commander" config section. I'm on an internal IP network, not using any CAT or Serial control ports. Under the "Control" section of the setup, I selected SDR-6600 as Radio #1, checked "Interrogate", gave it an "Interval" of 200 and gave it a "Name". Under "Radio #2, I selected SDR-6400 and repeated the above selections for it.  When I went to check the "Enable" box, I was unable to do so. The boxes stayed unchecked. There is no option on the "Commander" main screen to select the different radios, which I assume if it were "Enabled" would be. I can only control the Flex 6600, which was selected on the "General" Tab under Radio Selection, which I filled in with the radios Serial Number and IP Address. Another DXLab user told me that I should have been able to check the "Enable" boxes in the Control window of the "MultiRadio" config, but I cannot. I also tried to fill in the "Select" windows of each radio, where it asks for each radios "Serial Number, IP Address and IP Port, but that did not work either. In reading the "Help" files concerning those particular tabs, it appears they don't have to be filled in using the radios that I am using, only the Flex 6300, 6500 and 6700 series of radios. What am I missing? Thanks in advance for any help you can give me!

+ Before attempting to configure Commander to control one of several Primary Transceivers using the Configuration window's MultiRadio tab, you should first configure the General tab of Commander's Configuration window to successively control each of your Primary Flex Transceivers; the only difference should be the Model selector setting and the "Serial Number" in the "Radio Selection" panel. Is Commander able to control each of your transceivers if you manually set these to the correct value?

        73,

               Dave, AA6YQ