Date   

Re: Indicates wrong mode only on CW FTDX3000

Steve
 

Thanks, Joe. I missed that when I "thought" I checked the menu items.

73,
Steve W1LV


Avery 8161 Settings

Dave Tucker Nu4N <dwtucker19@...>
 

What are the settings for the Avery 8161 ?
--
73's de NU4N Dave


Re: Indicates wrong mode only on CW FTDX3000

Joe Subich, W4TV
 

By default the FTdx3000 operates CW in USB mode on all bands
(Menu 60 CW BFO = USB). If you want the rig to operate in
CW LSB on all bands, set menu 60 to LSB. If you want the
rig to operate CW in LSB on 160/80/40 and USB on 30 M and
above set menu 60 to Auto.

Commander will report either CW (normal) or CW-R as reported
by the transceiver. The transceiver does not directly report
CW USB or CW LSB.

73,

... Joe, W4TV

On 2021-03-05 7:34 AM, Steve wrote:
Commander tracks frequency and mode, expect that it shows 'CW' when the rig shows 'CW USB' on 40 meters. Similar results on other bands. Reversing the mode on the rig shows 'CW-R' when the rig shows 'CW LSB'
I searched this forum and found a similar problem, but it seemed to involve interaction with Spot Collector, which is not running when my problem occurs.
I have checked the rig menu items and they seem to be in order.
What am I missing?
Thanks and 73,
Steve W1LV


Indicates wrong mode only on CW FTDX3000

Steve
 

Commander tracks frequency and mode, expect that it shows 'CW' when the rig shows 'CW USB' on 40 meters. Similar results on other bands. Reversing the mode on the rig shows 'CW-R' when the rig shows 'CW LSB'

I searched this forum and found a similar problem, but it seemed to involve interaction with Spot Collector, which is not running when my problem occurs.

I have checked the rig menu items and they seem to be in order.

What am I missing?

Thanks and 73,

Steve W1LV


Re: DXLab Commander connection to HF-AUTO SW

Jon Gefaell
 
Edited

The USB <-> Serial cable I ordered arrived today. I excitedly routed it from the Palstar to the computer and started the HFAUTO SW and Voila, it works a charm. How fantastic. Thank you again, Norm. And Dave for baking in support in DX Lab Suite. What a great upgrade for my shack.


Re: DX Marathon Progress report

Dave AA6YQ
 

+ AA6YQ comments below

 

Thanks Phil.  I did all those things and it still did not populate.  After further digging this morning I figured it out.
 
It started because I believe I changed to a different log incorrectly and somehow hosed my settings in my primary call.
 
Here is what I found that fixed it.
 
If the Include QSOs with no propagation mode box is unchecked, QSOs whose propagation mode is unspecified will not be included. 
 
I do not have a propagation mode checked for HF qsos.   I had to go into Config under the Awards tab and click on "inlcude QSOs with no prop mode" for the report to work properly.  When I changed logs my registration entries changed (probably because I had not updated them or from the 2nd log change) and that was no longer clicked.
 
It is now working again.

+ The  CQ DX Marathon Progress report has been working correctly all along. 

+ CQ DX Marathon rules prohibit QSOs made with terrestrial repeaters. To enable ops who log such QSOs to generate accurate Marathon Progress reports, these QSOs must be excluded. Each QSO's "Propagation Mode" item is employed to do that. If your QSOs don't specify a "Progagation Mode" item, you can quickly compensate by enabling the "include QSOs with no prop mode" option.

+ However, the proper solution is to

1. Update your logged QSOs without a Propagation Mode to specify the (likely) correct value in their "Prop Mode" items.

1a. Backup your log (Configuration window, Backup button)

1b. Update any QSOs you made via Backscatter (BS)

1c. Update any 10m QSOs you made via Sporadic E (ES), Transequatorial propagation (TEP). Repeaters (RPT)

1d. Update any 6m QSOs you made via Meteor Scatter (MS), Earth-Moon-Earth (EME), Repeaters (RPT) or F2

1e. Filter the Log Page Display to contain all QSOs whose "Prop Mode" items are empty and whose frequencies are less than 30 mHz

1f. Use the "Advanced Sorts, Filters, and Modifiers" window's "Modify QSOs" panel to set the "Prop Mode" items in all logged QSOs to F2

1g. Filter the Log Page Display to contain all QSOs whose "Prop Mode" items are empty and whose frequencies are less than 54 mHz

1f. Use the "Advanced Sorts, Filters, and Modifiers" window's "Modify QSOs" panel to set the "Prop Mode" items in all logged QSOs to Sporadic E (ES)

2. On the Configuration window's Defaults tab, set the "Propagation Mode" selector to the propagation mode you most frequently employ (likely F2). 

+ When you're likely to make a set of QSOs using a propagation mode other than your default, temporarily change the default propagation mode, and restore it when finished. Alternatively, log those QSOs with your default propagation mode, backup your log, filter the Log Page Display to select those QSOs, and use the "Modify QSO" panel to correct their "Prop Mode" items; f you have automatic uploading to eQSL or LoTW enabled, re-upload those QSOs.

      73,

           Dave, AA6YQ

 


Re: DX Marathon Progress report

Mike KC7V
 

Thanks Phil.  I did all those things and it still did not populate.  After further digging this morning I figured it out.

It started because I believe I changed to a different log incorrectly and somehow hosed my settings in my primary call.

Here is what I found that fixed it.

If the Include QSOs with no propagation mode box is unchecked, QSOs whose propagation mode is unspecified will not be included. 

I do not have a propagation mode checked for HF qsos.   I had to go into Config under the Awards tab and click on "inlcude QSOs with no prop mode" for the report to work properly.  When I changed logs my registration entries changed (probably because I had not updated them or from the 2nd log change) and that was no longer clicked.

It is now working again.
73,
Mike
KC7V



Re: Exporting from DX4WIN to DXLab

Dave AA6YQ
 

+ AA6YQ comments belo
Yes The ARRL Verified Honor Roll Countries in the DXCC Progress Report.  this section in the report has no data, all zeros.
 
In DX4WIN, when i get a confirmation for a QSO (Card or LoTW), i set the flag to "C" as in Confirmed.  If its a confirmation for a new DXCC country, band or mode, after i submit to the ARRL for credit and it gets approved, i set the corresponding flag for that award (DXCC) to C as in Checked which means it has been checked and accepted by the ARRL.  
 
Based on what i think you are explaining, DXLab should have used the DXCC "C" flag in the imported log for the DXCC Honor roll? 
 

+ No. ADIF defines an CREDIT_GRANTED field to to indicated that DXCC award credit has been granted. See

http://adif.org.uk/311/ADIF_311.htm#QSO_Field_CREDIT_GRANTED

+ DXKeeper does have the ability to handle the non-compliant ADIF generated by some logging applications. If DX4WIN exports DXCC award credit in a non-compliant manner, I'm not aware of it, and thus did not equip DXKeeper handle it.

      73,

            Dave, AA6YQ

 

 

 

 

 


Re: Exporting from DX4WIN to DXLab

Saad Mahaini
 

Thanks Dave

Yes The ARRL Verified Honor Roll Countries in the DXCC Progress Report.  this section in the report has no data, all zeros.

In DX4WIN, when i get a confirmation for a QSO (Card or LoTW), i set the flag to "C" as in Confirmed.  If its a confirmation for a new DXCC country, band or mode, after i submit to the ARRL for credit and it gets approved, i set the corresponding flag for that award (DXCC) to C as in Checked which means it has been checked and accepted by the ARRL.  

Based on what i think you are explaining, DXLab should have used the DXCC "C" flag in the imported log for the DXCC Honor roll?  It seems that it did use it for the DXCC credit but not the Honor roll credit?

73 Saad N5FF

 



On Wednesday, March 3, 2021, 8:44:28 PM CST, Dave AA6YQ <aa6yq@...> wrote:


I have imported the log, and setup the myQTH , and so far everything checks out as far as total contries worked, bands modes, etc .

Also, got the commander interfaced to microham devices, controlling the radios, etc so that piece is all setup and working properly

I believe i'm now officially and successfully migrated, and slowly getting more familiar with the logging suite as well as the other suites

One discrepancy i noticed when i ran the DXCC progress report.  The totals are accurate, but the Honor roll list is not, for example the DXCC count is accurate at 336 but my honor roll total is 0.  Is that something that i should have flagged before importing the log, or something i need to configure in DXKeper afterwards

+ Are you referring to the "ARRL-verified Honor Roll Countries" section of the DXCC progress report? That section only counts QSOs that are marked as having been granted DXCC Award Credit. For a QSO confirmed via QSL card, that means its "QSL Rcvd" item is set to 'V'; for a QSO confirmed via LoTW, that means its "LoTW QSL Rcvd" item is set to 'V'.

+ If your QSOs have been granted DXCC Award credit but this wasn't indicated in the ADIF file you imported from DX4WIN, DXKeeper can update your logged QSOs to reflect DXCC Credits granted by downloading your DXCC Award Credit (HTML),  and "scraping" it to extract the credits. This isn't a fully automatic process because of the data entry errors and shortcuts taken when ARRL staff enter data from submitted QSL cards. See "Managing DXCC Credits" in

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

    73,

            Dave, AA6YQ









Re: Weird radio behavior with WSJT-X

Dave AA6YQ
 

+ AA6YQ comments below
the default K3 configuration (CONFIG:PTT-KEY) has external PTT and FSK keying disabled, that applies to both the RS-232 port and the virtual USB serial port. So although it is correct to not configure Commander to try and PTT the rig via RTS or DTR if CAT PTT is being used, it will only have an effect if the rig's CONFIG:PTT-KEY option is also set to something like RTS-DTR as opposed to the default OFF-OFF

+ That makes an assumption about where the K3's "PTT lockup" defect lies. Setting Commander's RTS and DTR selectors to "OFF" eliminates any possible source of external PTT assertion.

+ If RX-TX switching via CAT command is reliable - first with Commander standalone, and then with WSJT-X - the user can then if desired change to using PTT for RX-TX switching instead of using CAT commands for that purpose. This maintains a "change only one thing at a time"  approach to debugging.

      73,

           Dave, AA6YQ


Re: Weird radio behavior with WSJT-X

g4wjs
 

On 04/03/2021 03:34, Dave AA6YQ wrote:
@ more AA6YQ comments below

+ I suggest that you first configure Commander to reliably switch your K3 between RX and TX using CAT commands.

1. To avoid the lockup defect, disconnect the external interface that is generating the backpanel PTT signal.

2. Uncheck the "Suppress CAT" box in the PTT panel on the 
Configuration window's General tab

3. Lower your K3's RF ouput power to 0, and tune to a clear amateur 
frequency

4. Using the TX and RX buttons in the PTT panel on the Configuration window's General tab, repeatedly switch between RX and TX. Does the K3 obey these commands without locking up?
item (1) is tricky since with the K3S, or any K3 with a USB connection, the PTT signals are on the same virtual serial port as the CAT traffic. 
The RS-232 and USB virtual serial port RTS and DTR connections on a K3 are effectively in parallel.

@ Thanks, Bill! I should have included an additional step 2.5 in the instructions above:

2.5 For A K3S, or any K3 with a USB connection, On the Configuration window's Ports tab,  set the DTR and RTS selectors in the "Primary CAT Serial Port" panel to "Off".

       73,

                  Dave, AA6YQ

Hi Dave,

the default K3 configuration (CONFIG:PTT-KEY) has external PTT and FSK keying disabled, that applies to both the RS-232 port and the virtual USB serial port. So although it is correct to not configure Commander to try and PTT the rig via RTS or DTR if CAT PTT is being used, it will only have an effect if the rig's CONFIG:PTT-KEY option is also set to something like RTS-DTR as opposed to the default OFF-OFF.


--
73

Bill

G4WJS.


Re: Weird radio behavior with WSJT-X

Dave AA6YQ
 

@ more AA6YQ comments below

+ I suggest that you first configure Commander to reliably switch your K3 between RX and TX using CAT commands.

1. To avoid the lockup defect, disconnect the external interface that is generating the backpanel PTT signal.

2. Uncheck the "Suppress CAT" box in the PTT panel on the
Configuration window's General tab

3. Lower your K3's RF ouput power to 0, and tune to a clear amateur
frequency

4. Using the TX and RX buttons in the PTT panel on the Configuration window's General tab, repeatedly switch between RX and TX. Does the K3 obey these commands without locking up?
item (1) is tricky since with the K3S, or any K3 with a USB connection, the PTT signals are on the same virtual serial port as the CAT traffic.
The RS-232 and USB virtual serial port RTS and DTR connections on a K3 are effectively in parallel.

@ Thanks, Bill! I should have included an additional step 2.5 in the instructions above:

2.5 For A K3S, or any K3 with a USB connection, On the Configuration window's Ports tab, set the DTR and RTS selectors in the "Primary CAT Serial Port" panel to "Off".

73,

Dave, AA6YQ


Re: Weird radio behavior with WSJT-X

g4wjs
 

On 04/03/2021 03:02, Dave AA6YQ wrote:
+ I suggest that you first configure Commander to reliably switch your K3 between RX and TX using CAT commands.

1. To avoid the lockup defect, disconnect the external interface that is generating the backpanel PTT signal.

2. Uncheck the "Suppress CAT" box in the PTT panel on the Configuration window's General tab

3. Lower your K3's RF ouput power to 0, and tune to a clear amateur frequency

4. Using the TX and RX buttons in the PTT panel on the Configuration window's General tab, repeatedly switch between RX and TX. Does the K3 obey these commands without locking up?

73,

Dave, AA6YQ
Hi Dave,

item (1) is tricky since with the K3S, or any K3 with a USB connection, the PTT signals are on the same virtual serial port as the CAT traffic. The RS-232 and USB virtual serial port RTS and DTR connections on a K3 are effectively in parallel.



--
73

Bill

G4WJS.


Re: Weird radio behavior with WSJT-X

Dave AA6YQ
 

+ AA6YQ comment sbelow
sounds like you do not have the K3 menu option CONFIG:PTT-KEY set correctly for RTS keying via RS-232/USB. You said you have Commander set to key the rig using the CAT port RTS line. You probably need to select CONFIG:RTS-DTR to match your Commander configuration, or the default OFF-OFF and let Commander use CAT commands for PTT by unchecking "Suppress CAT".

It also seems you so not have multiple PTT sources, unless something like DATA-VOX is also enabled, so the initial diagnosis may be wrong.

+ There are two ways to switch an Elecraft K3 between RX and TX:

1. by sending it the appropriate CAT command

2. by directing an external interface to assert or de-assert the PTT signal on the K3's backpanel

+ As Bill G4WJS has pointed out, a longstanding defect in the K3 can cause it to lock up if both of the above techniques are applied simultaneously.

+ I suggest that you first configure Commander to reliably switch your K3 between RX and TX using CAT commands.

1. To avoid the lockup defect, disconnect the external interface that is generating the backpanel PTT signal.

2. Uncheck the "Suppress CAT" box in the PTT panel on the Configuration window's General tab

3. Lower your K3's RF ouput power to 0, and tune to a clear amateur frequency

4. Using the TX and RX buttons in the PTT panel on the Configuration window's General tab, repeatedly switch between RX and TX. Does the K3 obey these commands without locking up?

73,

Dave, AA6YQ


Re: Exporting from DX4WIN to DXLab

Dave AA6YQ
 

I have imported the log, and setup the myQTH , and so far everything checks out as far as total contries worked, bands modes, etc .

Also, got the commander interfaced to microham devices, controlling the radios, etc so that piece is all setup and working properly

I believe i'm now officially and successfully migrated, and slowly getting more familiar with the logging suite as well as the other suites

One discrepancy i noticed when i ran the DXCC progress report. The totals are accurate, but the Honor roll list is not, for example the DXCC count is accurate at 336 but my honor roll total is 0. Is that something that i should have flagged before importing the log, or something i need to configure in DXKeper afterwards

+ Are you referring to the "ARRL-verified Honor Roll Countries" section of the DXCC progress report? That section only counts QSOs that are marked as having been granted DXCC Award Credit. For a QSO confirmed via QSL card, that means its "QSL Rcvd" item is set to 'V'; for a QSO confirmed via LoTW, that means its "LoTW QSL Rcvd" item is set to 'V'.

+ If your QSOs have been granted DXCC Award credit but this wasn't indicated in the ADIF file you imported from DX4WIN, DXKeeper can update your logged QSOs to reflect DXCC Credits granted by downloading your DXCC Award Credit (HTML), and "scraping" it to extract the credits. This isn't a fully automatic process because of the data entry errors and shortcuts taken when ARRL staff enter data from submitted QSL cards. See "Managing DXCC Credits" in

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

73,

Dave, AA6YQ


Re: Uploading to LOTW

Dave AA6YQ
 

+ AA6YQ comments below

I have LOTW linked up and I see R on my QSO from the stations I worked.Do I have to set all the LOTW stations before I up load them to LOTW?


+ What does "see R on my QSO from the stations I worked" mean, exactly?

+ Step-by-step instructions for configuring DXKeeper for interaction with LoTW are here:

https://www.dxlabsuite.com/dxlabwiki/ConfigureLotW


+ Step-by-step instructions for submitting QSOs to LoTW are here:

https://www.dxlabsuite.com/dxlabwiki/UploadLoTWAddRequested

+ If DXKeeper is properly configured, these boil down to the following steps on the Main window's QSL tab:

1. set the "QSL Via" panel to LoTW

2. click the "Add Requested" button

3. click the "Upload to LoTW" button


+ You can also configure DXKeeper to automatically upload each QSO to LoTW as you log it:

https://www.dxlabsuite.com/dxlabwiki/AutomaticLotWUpload

73,

Dave, AA6YQ


Re: Help on state column

Dave AA6YQ
 

+ AA6YQ comments below

I went into ADV tab and tried filtering QSO's for a state.

+ An SQL filter for a particular state - say Florida - would look like this:

(DXCCPREFIX='K') and (STATE = 'FL')


So I used Modify QSO's in log display and now all my states are erased.

+ The "Modify QSOs" function makes changes you specify to all QSOs in the Log Page Display. What led you to believe that this was the appropriate function to use to view all QSOs with a particular state?

Is there an easy way to get them back?I tried the CBA and that did work.Normally I would just save as "save as" and create a new file then reload my old file back in.I have some QSO that aren't saved to back up yet.

+ Yes:

1. Filter the Log Page Display (by date range) to contain only the QSOs not present in your most recent backup

https://www.dxlabsuite.com/dxkeeper/Help/FilterLog.htm#Filtering%20for%20Time%20Intervals

2. Export the QSOs in the (filtered) Log Page Display to an ADIF file

3. On the Configuration window's Files tab, click the Recover button, and select your most recent log backup file

4. Import the ADIF file you created in step 2


+ I strongly recommend reviewing the documentation for any DXLab function that you previously have not used - before you use it!

73,

Dave,


Uploading to LOTW

Rich KB1FGC <marzo7088@...>
 

I have LOTW linked up and I see R on my QSO from the stations I worked.Do I have to set all the LOTW stations before I up load them to LOTW?
Rich


Re: DX Marathon Progress report

Phil Deaver
 

Dave sent this procedure previously.
Phil WR7T

Resetting Realtime CQ DX Marathon Award Tracking at the Beginning of Each Year

At the beginning of a new calendar year, reset DXLab's Realtime Award Tracking for CQ DX Marathon by performing these actions in the specified order:

  1. In the "Marathon Bands & Modes" panel on the Awards tab of DXKeeper's Configuration window, select the bands and modes on which an active DX station should be highlighted and announced by SpotCollector as needed for CQ DX Marathon during the new year

    1. check the Mixed box if you're considering submitting a Mixed Category Score Sheet at the end of the year

    2. check the box for each Band for which you're considering submitting a single-band Category Score Sheet at the end of the year
    3. check the box for each Mode for which you're considering submitting a single-mode Category Score Sheet at the end of the year
    4. if the Realtime Award Progress box is not already checked, terminate SpotCollector, and then check it

    5. click the Year, Category, Score Sheet Info button to display the Marathon Year, Category, and Score Sheet Information window; in this window,

      1. set the Current year to the new year (e.g. 2021)

      2. download the new CQ Marathon Excel Scoresheet into DXKeeper's Databases folder (or any other folder you prefer)

      3. click the Select button to select the pathname into which you downloaded the new Excel Scoresheet

      4. confirm that the correct version is displayed beneath the Excel Scoresheet pathname.

  2. On the Check Progress tab of DXKeeper's Main window, click the Recompute button

  3. On the Spot Database tab of SpotCollector's Configuration window, click the Recomputation panel's Recomp button

To generate a Marathon Progress report for a year other than the current year specified in the Marathon Year, Category, and Score Sheet Information window, depress the CTRL key while clicking the CQ DX Marathon panel's Progress button, and you'll be able to specify the year for which the Progress Report is generated.

To generate a Marathon Submission for a year other than the current year specified in the Marathon Year, Category, and Score Sheet Information window, depress the CTRL key while clicking the CQ DX Marathon panel's Submission button, and you'll be able to specify the year for which the Submission is generated.


DX Marathon Progress report

Mike KC7V
 

I believed I may have messed up my registration entries when trying to switch between two logs.  I hope I have that straightened out.  However, now when I run the Marathon report for 2021 I do not get any data.  I have over 3,000 qsos in the log since Jan 1.  I've done the recompute but no difference.

What am I missing?
Mike
KC7V

3301 - 3320 of 203451