Date   

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


QSL Date Format

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


Re: QSL question

Dave AA6YQ
 

+ AA6YQ comments below

Thanks all.I wasn't sure how deep I was going to get into it but at some point I may get into printing cards and all.I'll check the sections you described.

+ In the mean time, if your QSO partner asks you to send a QSL card,

- if you're logging via DXKeeper's Capture window, check the "QSL Requested" box before clicking the Log button

- if you're logging via the "Log QSOs" tab of DXKeeper's Main window, click the QSL panel's RR button (if you want a card in return) or set the QSL panel's Sent selector to 'R' (if you don't want a card in return) before clicking the "Log" button

- if you're logging via WinWarbler's "Log QSO" panel, check its QSL box before clicking the "Log" button

- if you're logging via another application, then after the QSO has been logged in DXKeeper, on the "Log QSOs" tab of DXKeeper's Main window, click the QSL panel's RR button (if you want a card in return) or set the QSL panel's Sent selector to 'R' (if you don't want a card in return) and then click the "Save" button.

73,

Dave, AA6YQ


Re: QSL question

Rich KB1FGC <marzo7088@...>
 

Thanks all.I wasn't sure how deep I was going to get into  it but at some point I may get into printing cards and all.I'll check the sections you described.
73
Rich


Re: QSL question

Joe Subich, W4TV
 

Please see the topic "Getting Started with QSLing" in the DXLab Suite
WiKi. The WiKi is: <http://www.dxlabsuite.com/dxlabwiki/GettingStarted>

The specific article "Getting Started with QSLing" is:
<http://www.dxlabsuite.com/dxlabwiki/QSLing>

73,

... Joe, W4TV

On 2021-03-02 8:15 PM, Rich KB1FGC via groups.io wrote:
Thanks Joe,I may not have explained it well or I am  not  understanding what you have said.It sounds like the R won't work for marking as "Have to send."I wrote a definition based on help about another thing and I finally got it to work.When I click on the userd efined button it will search for only what I intend to send out but haven't yet.I'll try what you have said and see if it works for me.
Thanks
Rich
73


Re: QSL question

ND9G Mike
 

What Joe described is exactly what you want. As you work someone you can set that if you want to send a QSL card. That way when you go to the QSl tab and select your option for QSl cards or label, when you click the add requested button it will add all QSOs for which you have it set to "R".

This also covers you for response cards, when you receive a card that asks for a QSL card, you can set it to "R" (either manually or via some of the automated methods), and the next time you prepare to print cards/labels, it will be included for printing.

After you have printed your cards/labels you would then click the Update Log button on the QSL queue and DXKeeper wouldupdate all of those records from R to Y indicating that you have sent the card.


You may also want to check out this getting started article: http://www.dxlabsuite.com/dxlabwiki/QSLing


73,
Mike ND9G


On Tue, Mar 2, 2021 at 7:15 PM Rich KB1FGC via groups.io <marzo7088=yahoo.com@groups.io> wrote:
Thanks Joe,I may not have explained it well or I am  not  understanding what you have said.It sounds like the R won't work for marking as "Have to send."I wrote a definition based on help about another thing and I finally got it to work.When I click on the userd efined button it will search for only what I intend to send out but haven't yet.I'll try what you have said and see if it works for me.
Thanks
Rich
73


Re: QSL question

Dave AA6YQ
 

+ AA6YQ comments below
Thanks Joe,I may not have explained it well or I am  not  understanding what you have said.It sounds like the R won't work for marking as "Have to send."I wrote a definition based on help about another thing and I finally got it to work.When I click on the userd efined button it will search for only what I intend to send out but haven't yet.I'll try what you have said and see if it works for me.

+ Rich, DXKeeper supports several workflows for generating QSL cards and labels, and provides automation for those workflows. I suggest that you review

https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm

       73,

             Dave, AA6YQ

3321 - 3340 of 203452