Date   

Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Dave AA6YQ
 

+ AA6YQ comments below

I tried running DXView along side DXKeeper, and have the option clicked on the Rotor Tab, since I don't use rotor control.
When I tried making two QSOs, I noticed that DXView does indeed show short and long path headings to the remote station.
But the column in DXKeeper for ANT_AZ is not populating.

Is there some additional setting that needs to be made?

+ All of the required settings are described in

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

+ If a careful review of this article doesn't get you going, please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper

4. temporarily disable any automatic uploading of QSOs to Club Log, eQSL.cc, and LoTW

5. log a test QSO with AA6YQ with its grid square populated

6. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

7. re-enable the automatic uploading of QSOs to Club Log, eQSL.cc, and LoTW that you disabled in step 4

8. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

        73,

              Dave, AA6YQ

 


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Neal Pollack
 

Hi Dave:

I tried running DXView along side DXKeeper, and have the option clicked on the Rotor Tab, since I don't use rotor control.
When I tried making two QSOs, I noticed that DXView does indeed show short and long path headings to the remote station.
But the column in DXKeeper for ANT_AZ is not populating.

Is there some additional setting that needs to be made?

Cheers,

Neal
N6YFM


Re: Issue with uploading to LoTW

Dave AA6YQ
 

+ AA6YQ comments below

I took part in the Michigan QSO Party this last Saturday. I live in Michigan but, thinking my W5DT call sign might confuse people, especially those out of state, I used W5DT/8 for the period of the contest. The pass through of my contacts from N1MM to DXKeeper worked fine but the contacts did not upload to LoTW and I assume that is because I used the /8 on my call sign. A group upload didn't work either. Would the correct thing to do be to get another LoTW certificate for W5DT/8 or is there something else I should do? There are over 200 contacts.

+ If a logged QSO's "Station Callsign" is W5DT/8, DXKeeper's "Upload to LoTW" function will skip it if you specified a "Callsign Certificate" of W5DT. This prevents inadvertently submitting QSOs with the wrong "Callsign Certificate".

+ If you used W5DT/8 over the air, then your QSO partners will submit QSOs with W5DT/8 - which would only match QSOs submitted with a W5DT/8 "Callsign Certificate".

+ So yes, you must request a W5DT/8 "Callsign Certificate", and use it to submit the QSOs you made as W5DT/8.

+ Instructions are here:

https://lotw.arrl.org/lotw-help/addcertreq/

+ You should receive your new "Callsign Certificate" within a few days of requesting it.

73,

Dave, AA6YQ


Issue with uploading to LoTW

Marv Stasak
 

Dave,

I took part in the Michigan QSO Party this last Saturday.  I live in Michigan but, thinking my W5DT call sign might confuse people, especially those out of state,  I used W5DT/8 for the period of the contest.  The pass through of my contacts from N1MM to DXKeeper worked fine but the contacts did not upload to LoTW and I assume that is because I used the /8 on my call sign. A group  upload didn't work either.  Would the correct thing to do be to get another LoTW certificate for W5DT/8 or is there something else I should do?  There are over 200 contacts.

73,
Marv, W5DT


67 new modes!

Dave AA6YQ
 

ADIF 3.1.2 was approved yesterday. It defines the 67 new sub-modes listed below, most of them supported by FLDigi.

In ADIF, modes and submodes are unique. DXKeeper exploits this by treating submodes as if they were modes. For example, ADIF
represents FT8 as

<MODE:4>MFSK <SUBMODE:3>FT8

but to manually log a QSO in FT8, you simply set the Capture window's Mode selector to FT8. When exporting an ADIF file, DXKeeper
automatically emits the correct ADIF mode-and-submode representation for each QSO's Mode item. When importing an ADIF file or an
ADIF QSO record from another application), DXKeeper automatically converts the ADIF mode-and-submode representation to its internal
"mode only" representation. This eliminates the need for users to be aware of ADIF's mode-submode distinction.

The current version of DXKeeper handles Mode items up to 8 characters in length. Several of the new submodes defined in ADIF 3.1.2
are 11 characters in length. Thus the next version of DXKeeper will automatically expand the width of its Mode items to 12 when you
open a log file whose Mode items are limited to 8 characters. This expansion will fail if DXView, JT-Alert, SpotCollector, or
SpotSpy are running, so it will be necessary to terminate these applications before the automatic Mode item expansion can be
completed; DXKeeper will inform you if that's the case.

SpotCollector has long supported a wider Mode field, so it requires no change to handle the new submodes.

The DefaultModes.txt file included with the next version of DXKeeper will include all 67 of the new submodes. If you don't want
these to appear in DXKeeper's mode selectors, you can create a Modes.txt file in DXKeeper's Databases folder that includes the
subset of entries from DefaultModes.txt that you want present in DXKeeper's Mode selectors. If you've already defined a Modes.txt
file in DXKeeper's Databases folder and want DXKeeper's Mode selectors to include one or more of the 67 new modes, copy their
entries from the new DefaultModes.txt file to your Modes.txt file. After making any change to your DefaultModes.txt or Modes.txt
files, terminate and restart DXKeeper after saving those changes.

Why the mode-submode representation in ADIF? The thinking was that new submodes of an existing mode could be quickly added by the
person serving as "Secretary of ADIF", bypassing a multi-week discussion and vote. In practice, disagreements over submode names
have left the Secretary unwilling accept new submode proposals without a vote.

73,

Dave, AA6YQ


DOM-M
DOM4
DOM5
DOM8
DOM11
DOM16
DOM22
DOM44
DOM88
HELLX5
HELLX9
SLOWHELL
FST4W
JTMS
MFSK64L
MFSK128L
Q65
8PSK125
8PSK125F
8PSK125FL
8PSK250
8PSK250F
8PSK250FL
8PSK500
8PSK500F
8PSK1000
8PSK1000F
8PSK1200F
PSK63RC20
PSK63RC32
PSK63RC4
PSK63RC5
PSK63RC10
PSK125RC10
PSK125RC12
PSK125RC16
PSK125RC4
PSK125RC5
PSK250RC2
PSK250RC3
PSK250RC5
PSK250RC6
PSK250RC7
PSK500RC2
PSK500RC3
PSK500RC4
PSK800RC2
PSK1000RC2
THOR-M
THOR4
THOR5
THOR8
THOR11
THOR16
THOR22
THOR25X4
THOR50X1
THOR50X2
THOR100
THRBX1
THRBX2
THRBX4
THROB1
THROB2
THROB4
NAVTEX
SITORB


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Dave AA6YQ
 

+ AA6YQ comments below

I am running the latest DXKeeper, v16.0.7.  I added a new column today for ANT_AZ in my log display.
I am hoping to record/display the bearing to the other station in my log.

I next went to the DXKeeper CONFIG button, DEFAULTS tab, and made sure that "Antenna Path" said "S".
On this DEFAULTS tab, my QTH LAT and LONG are set.  Format is like 33 48' 45" N.
All of my QSO's from today do show a value in the "GRID 1" field on the log award sub-panel.

But, the ANT_AZ column does not populate.    I searched previous topics here and can't find
what I am missing?
Please note I am only using DXKeeper and WSJT-X, and do not have other DXLABs apps open
due to screen real estate.

+ As described in the "Azimuth and Antenna Path" section of

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

+ DXView must also be running. You can keep its windows minimized (off-screen) to conserve screen space.

       73,

               Dave, AA6YQ

 


DXKeeper: How to log azimuth? ANT_AZ not populating in log

Neal Pollack
 

Hi:

I am running the latest DXKeeper, v16.0.7.  I added a new column today for ANT_AZ in my log display.
I am hoping to record/display the bearing to the other station in my log.

I next went to the DXKeeper CONFIG button, DEFAULTS tab, and made sure that "Antenna Path" said "S".
On this DEFAULTS tab, my QTH LAT and LONG are set.  Format is like 33 48' 45" N.
All of my QSO's from today do show a value in the "GRID 1" field on the log award sub-panel.

But, the ANT_AZ column does not populate.    I searched previous topics here and can't find
what I am missing?
Please note I am only using DXKeeper and WSJT-X, and do not have other DXLABs apps open
due to screen real estate.

Thanks,
Neal  N6YFM


Re: How to "Abort Update from LoTW"

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the quick response Dave, however don't see a small "DXKeeper Update from LoTW" window.

+ Did you try closing or minimizing each of the windows currently on your monitor?

I misread/misunderstood the "depressing CTRL while clicking Sync LotW QSLs will certainly be faster" msg.

Is there anything else to try?

+ The only other alternative is to terminate DXKeeper.

73,

Dave, AA6YQ


Re: How to "Abort Update from LoTW"

n7bv@...
 

Thanks for the quick response Dave, however don't see a small  "DXKeeper Update from LoTW" window.

I misread/misunderstood the "depressing CTRL while clicking Sync LotW QSLs will certainly be faster" msg.

Is there anything else to try?

=============
73, Chuck N7BV


Re: Commander 15.0.9 is available

Dave AA6YQ
 

+ AA6YQ comments below

K3 MCU 5.66 / DSP 2.88 / FPF 1.26, 11-28-2018

 

* ADDED SWR READ COMMAND:  "SW;" returns the most recent SWR reading in transmit or TUNE mode, e.g. "SW023;" for an SWR of 2.3:1. Max value returned is "SW99;" (SWR = 99.9:1).

+ When controlling a capable K3-family transceiver, Commander displays any SWR value greater than 3.8:1 as "3.9+:1".

      73,

             Dave, AA6YQ


Re: Commander 15.0.9 is available

Daniel Violette
 

Need at least v 5.66:

 

K3 MCU 5.66 / DSP 2.88 / FPF 1.26, 11-28-2018

 

* ADDED SWR READ COMMAND:  "SW;" returns the most recent SWR reading in transmit or TUNE mode, e.g. "SW023;" for an SWR of 2.3:1. Max value returned is "SW99;" (SWR = 99.9:1).

 

/Dan KI6X


Re: Commander 15.0.9 is available

Dave AA6YQ
 

+ AA6YQ comments below

I've sent you an email off list with the 2019 version of the K3S, etc. programmers reference.

It appears to have a GET command for firmware revisions (versions).

+ Thanks, Mike! I will incorporate this in the next version of Commander, which will aid debugging.

73,

Dave, AA6YQ


Re: Commander 15.0.9 is available

Mike Flowers
 

Hi Dave,

I've sent you an email off list with the 2019 version of the K3S, etc. programmers reference.

It appears to have a GET command for firmware revisions (versions).

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

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Saturday, April 17, 2021 13:45
To: DXLab@groups.io
Subject: Re: [DXLab] Commander 15.0.9 is available

+ AA6YQ comments below

Just as a point of reference:

I’m running my K3 with Commander 15.0.9 via a serial port and the following
K3 firmware:

MCU 05.67

FPF 01.26

DSP1 02.88

DSP2 02.88

These versions appear to be the latest from Elecraft.

Commander reports SWR during TX.

+ thanks, Mike. It would be nice if Elecraft provided a CAT command that
reports the K3's current firmware versions.

73,

Dave, AA6YQ






Re: Commander 15.0.9 is available

Ed W2LCQ
 

Dave,

The Commander Transmission Meter Display documentation is awesome. Thanks a lot!

All best, Ed

73, de W2LCQ, Ed Jones

The feeling is constantly growing on me that I had been the first to hear the greeting of one planet to another.” —-Nicola Tesla

On Apr 17, 2021, at 5:27 PM, Ed W2LCQ <w2lcq@...> wrote:

Thank you Dave!

All best, Ed

73, de W2LCQ, Ed Jones

The feeling is constantly growing on me that I had been the first to hear the greeting of one planet to another.” —-Nicola Tesla

On Apr 17, 2021, at 4:45 PM, Larry Christensen <ncelarry@...> wrote:

Thank you Mike my mistake I checked a few weeks ago but there is newer FW then I have.
I’m uploading right now.
Larry NA0F






Re: Commander 15.0.9 is available

Ed W2LCQ
 

Thank you Dave!

All best, Ed

73, de W2LCQ, Ed Jones

The feeling is constantly growing on me that I had been the first to hear the greeting of one planet to another.” —-Nicola Tesla

On Apr 17, 2021, at 4:45 PM, Larry Christensen <ncelarry@...> wrote:

Thank you Mike my mistake I checked a few weeks ago but there is newer FW then I have.
I’m uploading right now.
Larry NA0F






Re: Commander 15.0.9 is available

Larry Christensen
 

Dave that was problem, Elecraft updated the FW which I had not checked in the few week. I updated the SWR is working fine now. 


Sorry I wasted you time. 

Larry NA0F


Re: Commander 15.0.9 is available

Larry Christensen
 

Thank you Mike my mistake I checked a few weeks ago but there is newer FW then I have.
I’m uploading right now.
Larry NA0F


Re: Commander 15.0.9 is available

Dave AA6YQ
 

+ AA6YQ comments below

Just as a point of reference:

I’m running my K3 with Commander 15.0.9 via a serial port and the following K3 firmware:

MCU 05.67

FPF 01.26

DSP1 02.88

DSP2 02.88

These versions appear to be the latest from Elecraft.

Commander reports SWR during TX.

+ thanks, Mike. It would be nice if Elecraft provided a CAT command that reports the K3's current firmware versions.

73,

Dave, AA6YQ


Re: Commander 15.0.9 is available

Dave AA6YQ
 

Are SWR and keying speed available to IC 7300 users? I have the box unchecked but don’t see either on my DXC display.

+ As shown in the IC-7300 entry in the table in

https://www.dxlabsuite.com/commander/Help/TXMeter.htm

+ Commander's VFO panel can display RF power, SWR, ALC, Compression, final amplifier voltage, or final amplifier current when transmitting. Use the "Xmit Meter" selector on the Configuration window's General tab to choose the parameter you wish to monitor while transmitting.

+ When your IC-7300 is in CW mode, the Mode panel on Commander's Main window displays the current keyer speed.

73,

Dave, AA6YQ


Re: Commander 15.0.9 is available

Ed W2LCQ
 

Are SWR and keying speed available to IC 7300 users? I have the box unchecked but don’t see either on my DXC display. Not a major issue. Thanks. 

73, de W2LCQ, Ed Jones

The feeling is constantly growing on me that I had been the first to hear the greeting of one planet to another.” —-Nicola Tesla

On Apr 17, 2021, at 4:15 PM, Larry Christensen <ncelarry@...> wrote:

Usb to ser.
Yes on SW.
This is the only “issue” I’ve had with any of the DX Lab. Other than not knowing what I’m doing.😁

Larry NA0F





1801 - 1820 of 202667