Date   

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


Re: Exporting from DX4WIN to DXLab

Saad Mahaini
 

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

73 Saad N5FF 



On Monday, February 8, 2021, 12:05:07 AM CST, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ omments below:
I've been getting my feet wet with DXLab over the last few months and got everything installed and working well now.
 
I have not yet moved my log, but i believe I'm ready for the final step and to make the move now
 
I read the instructions on importing the ADIF and i assume DX4WIN exporting the log to ADIF should be straight forward also
 
I have one log for Qs i made with two call signs and four different QTHs.  I also have another log with different call and QTH. 
 
Anything i should be aware of before i start the process? 

+ QSOs made with different "station callsigns"  and/or from different locations within the same DXCC entity can be store in the same log, each with a "myQTHID" the referencing the "myQTH" from which is was made. That's because DXKeeper considers all QSOs within a log to count towards the same DXCC awards.

+ Review "Switching to DXKeeper from Another Logging Application" in 

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

+ noting in particular step 4.b.

+ An intermediate step you could take is to export your log from DX4Win into DXKeeper, setup each "myQTH", and update your logged QSOs (en masse) to reflect the correct "myQTHID" - while continuing to log QSOs in DX4WIN. Format the log page display to your taste, and try generating progress reports. When you're comfortable with that functionality, delete the QSO from your DXKeeper log, leaving the "myQTH" definitions in place. Export your logged QSOs from DX4WIN, import them into DXKeeper, and repeat the modifications en masse to make your logged QSOs reference the correct "myQTHIDs". 

+ This approach does cause some work to be done twice, but better to familiarize yourself with more of DXKeeper before making the cut-over.



         73,


               Dave, AA6YQ

 

 


Re: Weird radio behavior with WSJT-X

g4wjs
 

Hi Rick,

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.

73
Bill
G4WJS.

On 03/03/2021 18:12, Rick via groups.io wrote:
Bill: I unchecked the "suppress CAT" box, as per the instructions and found the radio no longer keys -- even when using the "TX" button on the main screen of Commander. Curious. I'm wondering it the issue lays elsewhere.


On Wednesday, March 3, 2021, 12:44:12 PM EST, g4wjs <bill.8@classdesign.com> wrote:


On 03/03/2021 17:40, Rick via groups.io wrote:
For example do you have "Suppress CAT" unchecked
in the Commander PTT panel?

Bill, that box is not checked.
I feel fairly certain this is something *I* have screwed up -- I don't
exactly hear a flood of folks with the same issue. And, there are a
LOT of folks using this excellent software (DXLab and WSJT) with K3s.

Rick
Hi Rick,

that'll probably be the issue. Note item 4(d) here:
http://www.dxlabsuite.com/dxlabwiki/TranceiverControlElecraft

I don't have any ideas on the similar issue with your Flex Radio 6300.
--
73

Bill

G4WJS.


Re: Weird radio behavior with WSJT-X

Rick
 

Bill: I unchecked the "suppress CAT" box, as per the instructions and found the radio no longer keys -- even when using the "TX" button on the main screen of Commander. Curious. I'm wondering it the issue lays elsewhere.


On Wednesday, March 3, 2021, 12:44:12 PM EST, g4wjs <bill.8@...> wrote:


On 03/03/2021 17:40, Rick via groups.io wrote:
> > For example do you have "Suppress CAT" unchecked
> in the Commander PTT panel?
>
> Bill, that box is not checked.
> I feel fairly certain this is something *I* have screwed up -- I don't
> exactly hear a flood of folks with the same issue. And, there are a
> LOT of folks using this excellent software (DXLab and WSJT) with K3s.
>
> Rick

Hi Rick,

that'll probably be the issue. Note item 4(d) here:
http://www.dxlabsuite.com/dxlabwiki/TranceiverControlElecraft

I don't have any ideas on the similar issue with your Flex Radio 6300.


Re: Weird radio behavior with WSJT-X

Rick
 

Ahhh. OK, TU Bill. I'll give that a try. Very helpful.
Fortunately, the Flex is gone now so I won't have to concern myself with that. :<)

Rick


On Wednesday, March 3, 2021, 12:44:12 PM EST, g4wjs <bill.8@...> wrote:


On 03/03/2021 17:40, Rick via groups.io wrote:
> > For example do you have "Suppress CAT" unchecked
> in the Commander PTT panel?
>
> Bill, that box is not checked.
> I feel fairly certain this is something *I* have screwed up -- I don't
> exactly hear a flood of folks with the same issue. And, there are a
> LOT of folks using this excellent software (DXLab and WSJT) with K3s.
>
> Rick

Hi Rick,

that'll probably be the issue. Note item 4(d) here:
http://www.dxlabsuite.com/dxlabwiki/TranceiverControlElecraft

I don't have any ideas on the similar issue with your Flex Radio 6300.

--
73


Bill


G4WJS.


Re: Weird radio behavior with WSJT-X

g4wjs
 

On 03/03/2021 17:40, Rick via groups.io wrote:
For example do you have "Suppress CAT" unchecked
in the Commander PTT panel?

Bill, that box is not checked.
I feel fairly certain this is something *I* have screwed up -- I don't exactly hear a flood of folks with the same issue. And, there are a LOT of folks using this excellent software (DXLab and WSJT) with K3s.

Rick
Hi Rick,

that'll probably be the issue. Note item 4(d) here: http://www.dxlabsuite.com/dxlabwiki/TranceiverControlElecraft

I don't have any ideas on the similar issue with your Flex Radio 6300.



--
73

Bill

G4WJS.


Re: Weird radio behavior with WSJT-X

Rick
 

> For example do you have "Suppress CAT" unchecked
in the Commander PTT panel?

Bill, that box is not checked.
I feel fairly certain this is something *I* have screwed up -- I don't exactly hear a flood of folks with the same issue. And, there are a LOT of folks using this excellent software (DXLab and WSJT) with K3s.

Rick



Re: Spot Collector Email Alarm ?

w2eck
 

Dave
Thank you for the additional explanation.

73 Paul w2eck


Re: Weird radio behavior with WSJT-X

g4wjs
 

On 03/03/2021 12:56, Rick via groups.io wrote:

Hi Bill. TU, PTT method in WSJT-X is "CAT" and using "DX Lab Suite Commander." In Commander DTR is "off;" RTS is "TX." On the "General" tab "PTT: Rcving" box is not checked.


you need to give us more information. Let;s start with just the K3. What
do you have checked for "Settings->Radio->PTT Method" in WSJT-X? What
PTT method are you using in Commander for your K3?
--
73
Bill
G4WJS.
Hi Rick,

thanks for that. K3s are prone to locking up in SEND mode if multiple sources of PTT are enabled, AFAIK this issue is not resolved by firmware updates. Do you have any other sources of PTT other than the mic connected to your K3? For example do you have "Suppress CAT" unchecked in the Commander PTT panel?



--
73

Bill

G4WJS.


Re: Weird radio behavior with WSJT-X

Rick
 


Hi Bill. TU, PTT method in WSJT-X is "CAT" and using "DX Lab Suite Commander." In Commander DTR is "off;" RTS is "TX." On the "General" tab "PTT: Rcving" box is not checked.


>you need to give us more information. Let;s start with just the K3. What
>do you have checked for "Settings->Radio->PTT Method" in WSJT-X? What
>PTT method are you using in Commander for your K3?

--
73
Bill
G4WJS.


Re: Weird radio behavior with WSJT-X

g4wjs
 

On 03/03/2021 12:30, Rick via groups.io wrote:
When using WSJT-X with my K3S I occasionally see very bizarre behaviors. Occasionally the radio remains in TX and can only be shut down by powering off the radio. Once in a while the radio goes into TX normally but there is no modulation. A "tune" produces no power -- occasionally.

What I've done to work with this:
1. Reviewed all available documentation. (There is a lot of very good documentation. I think all settings have been checked and are as recommended.)
2. Changed radios. (This exact problem also occurred with the Flex 6300 that was in use at this location before I changed back to Elecraft.)
3. Exited and re-entered WSJT-X. (This will solve the problem temporarily.)
4. Ensured the correct "sound cards" are elected. (They are -- even though Windoze occasionally tampers with them.)
5. Updated all software. (These events occurred with prior versions of Commander and WSJT-X and persist with the current versions.)
6. Checked other modes. (The lack of control occurred once while using RTTY, never with CW and never with phone.)
7. Checked all connections. (All OK. The K3S is connected to the computer via USB.)
8. Changed power. (Occurs at exciter power as well as when driving the KPA500 hard.)

Anyone have any suggestions as to where to go from here?
Rick,

you need to give us more information. Let;s start with just the K3. What do you have checked for "Settings->Radio->PTT Method" in WSJT-X? What PTT method are you using in Commander for your K3?



--
73

Bill

G4WJS.


Weird radio behavior with WSJT-X

Rick
 

When using WSJT-X with my K3S I occasionally see very bizarre behaviors. Occasionally the radio remains in TX and can only be shut down by powering off the radio. Once in a while the radio goes into TX normally but there is no modulation. A "tune" produces no power -- occasionally.

What I've done to work with this:
1. Reviewed all available documentation. (There is a lot of very good documentation. I think all settings have been checked and are as recommended.)
2. Changed radios. (This exact problem also occurred with the Flex 6300 that was in use at this location before I changed back to Elecraft.)
3. Exited and re-entered WSJT-X. (This will solve the problem temporarily.)
4. Ensured the correct "sound cards" are elected. (They are -- even though Windoze occasionally tampers with them.)
5. Updated all software. (These events occurred with prior versions of Commander and WSJT-X and persist with the current versions.)
6. Checked other modes. (The lack of control occurred once while using RTTY, never with CW and never with phone.)
7. Checked all connections. (All OK. The K3S is connected to the computer via USB.)
8. Changed power. (Occurs at exciter power as well as when driving the KPA500 hard.)

Anyone have any suggestions as to where to go from here?


Re: QSL Date Format

Dave AA6YQ
 

+ AA6YQ comments below

I just would like to ask whether it is possible to change the QSL Date Format to be printed on cards to dd-mmm-yyyy (4 digit year), of course English month abbreviation.
So far this is only possible when you use the ISO 8601 format yyyy-mm-dd.

+ That would unleash a never-ending cascade of requests for idiosyncratic changes to QSL cards and labels. If you want more flexibility in generating QSL cards or labels than what DXKeeper provides, see

"QSLing via ADIF or tab-delimited files: Generating QSL cards via an external application or service by way of the QSL Queue" in

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20via%20ADIF

73,

Dave, AA6YQ


Re: QSL Date Format

Kenneth Johansson
 

That is, ideed, the only proper and safe way to do it- Kudos Gary!
73
Ken/SM4EMO

2021-03-03 09:11 skrev Gerhard "Gary" Jaeger, DF2RG:

Good morning Dave,
I just would like to ask whether it is possible to change the QSL Date
Format to be printed on cards to dd-mmm-yyyy (4 digit year), of course
English month abbreviation.
So far this is only possible when you use the ISO 8601 format yyyy-mm-dd.
As an old fashioned European, I would like to use "03 Mar 2021", which
makes clear that it is not 21 March (20)03 ...
By the way, WHO is actually using LOCAL month abbreviations? Can just
be the local VHF/UHF guy talking to locals from town only 😉
73 de Gary, DF2RG

3361 - 3380 of 203498