Date   

Re: ADIF import for Rovers

Dave AA6YQ
 

+ AA6YQ comments below

Yes, it is best that N1MM+ export *ALL DATA* in ADIF standard format rather than APP_N1MM_EXCHANGE# as it does presently. Unfortunately, with State QSO Parties one has the additional complexity of handling exchanges that are, themselves, not ADIF compliant - specifically "independent cities" in Virginia, Maryland, and Nevada which are not included in the ADIF enumerated counties.

+ The USACA award rules for independent cities state that they "count" for adjacent counties. One way to handle this would be to add the independent city names to the County selectors for Virginia, Maryland, and Nevada.

+ When running the USACA progress report, QSOs with independent cities would be reported as errors, enabling the user to change each of them to an adjacent county.

+ When exporting an ADIF or tab-delimited file, a QSO whose County item specifies an independent city would not include a CNTY field in its exported ADIF record, as required for ADIF compliance.

+ Better ideas?

73,

Dave, AA6YQ


Re: ADIF import for Rovers

Dave AA6YQ
 

+ AA6YQ comments below

Actually there are 4 QPs that weekend, 7qp, inqp, neqp, and Delaware qp.

From a rover perspective, which is what this discussion is about, it really doesn't matter how many QSO parties are on the same day. If a rover is near enough that he could operate from two different QSO parties on the same day a different log will be used for each, whether you're using N1MM+ or another logging program. Thus any overlap of abbreviations doesn't matter.

It seems to me the best solution is for N1MM+ to make the conversion from QSO party county abbreviation to correct ADIF CNTY tag when the log is exported to ADIF. That ADIF log can then be easily uploaded to LOTW.

DXLab could take that ADIF and on import create a myQTHID if one doesn't exist for that state/county.


+ There are two independent challenges here:

1. importing a rover's ADIF log and automatically assigning myQTHIDs

2. importing a state QSO party ADIF log and converting each imported QSO's "county code" to a State and County item for ops pursuing WAS and/or USACA awards

+ Challenge #1 does not require unique "county codes". A missing myQTHID can be fabricated from the QSO's MY_GRIDSQUARE, which ideally N1MM will provide in all contests, as it facilitates accurate submissions to LoTW.

+ As for Challenge #2, the N1MM folks have stated that they will not take on the conversion of "county codes" to State and County items; I am working with Jim AD1C on enabling DXKeeper to provide this function.

73,

Dave, AA6YQ


Re: Intermitent Rig Control Errors to my ICOM 7610

Dave AA6YQ
 

+ AA6YQ comments below

I moved it to 25ms as suggested and have yet to see the error, so this change seems to be helping.

+ With a USB connect, the primary CAT baud rate set to 115200, and the "Verify CI-V command acceptance" enabled in the Radio panel on the Configuration window's General tab, my IC-7300 works reliably with a "Command interval" of 10 ms. I suspect that your IC-7610 would do the same.

+ My ancient IC-7800, limited to a primary CAT baud rate of 19200, works reliably with a "Command interval" of 25 ms.

73,

Dave, AA6YQ


ft857

Joe K2UF
 

Any one using commander control for a Yeasu ft857  xcvr.  I have tried using straight thru and cross over adapter just in case.  I am using a CT62 cable I got on EBay(ugh!).
 
Any help.
 
Thanks es 73
 
Joe K2UF


Re: ADIF import for Rovers

Joe Subich, W4TV
 

It seems to me the best solution is for N1MM+ to make the conversion from QSO party county abbreviation to correct ADIF CNTY tag when the
log is exported to ADIF. That ADIF log can then be easily uploaded
to LOTW.
Yes, it is best that N1MM+ export *ALL DATA* in ADIF standard format
rather than APP_N1MM_EXCHANGE# as it does presently. Unfortunately,
with State QSO Parties one has the additional complexity of handling
exchanges that are, themselves, not ADIF compliant - specifically
"independent cities" in Virginia, Maryland, and Nevada which are not
included in the ADIF enumerated counties.

73,

... Joe, W4TV


On 2021-03-18 10:25 AM, Alan Sewell wrote:
On Thu, Mar 18, 2021 at 09:00 AM, Scott Stembaugh wrote:
Actually there are 4 QPs that weekend, 7qp, inqp, neqp, and Delaware
qp.
>From a rover perspective, which is what this discussion is about, it
really doesn't matter how many QSO parties are on the same day.  If a rover is near enough that he could operate from two different QSO parties on the same day a different log will be used for each, whether you're using N1MM+ or another logging program.  Thus any overlap of abbreviations doesn't matter.
It seems to me the best solution is for N1MM+ to make the conversion from QSO party county abbreviation to correct ADIF CNTY tag when the log is exported to ADIF.  That ADIF log can then be easily uploaded to LOTW.
DXLab could take that ADIF and on import create a myQTHID if one doesn't exist for that state/county.
73, Alan N5NA


Re: Any DXLab issues w/ WIN 10 V20H2?

Alan Swinger
 

Tks, Norm. - Alan K9MBQ


On Thu, Mar 18, 2021 at 9:25 AM Norm - KC1BMD <noka@...> wrote:
I installed DXLab Suite about two months ago (WinWarbler installed but not using it presently) and 20H2 has been running since May 2020.
-> No issues that I can detect.

--
73, Norm/KC1BMD


Re: ADIF import for Rovers

Alan N5NA
 

On Thu, Mar 18, 2021 at 09:00 AM, Scott Stembaugh wrote:
Actually there are 4 QPs that weekend, 7qp, inqp, neqp, and Delaware qp. 
From a rover perspective, which is what this discussion is about, it really doesn't matter how many QSO parties are on the same day.  If a rover is near enough that he could operate from two different QSO parties on the same day a different log will be used for each, whether you're using N1MM+ or another logging program.  Thus any overlap of abbreviations doesn't matter.

It seems to me the best solution is for N1MM+ to make the conversion from QSO party county abbreviation to correct ADIF CNTY tag when the log is exported to ADIF.  That ADIF log can then be easily uploaded to LOTW.  

DXLab could take that ADIF and on import create a myQTHID if one doesn't exist for that state/county.

73, Alan N5NA


Re: ADIF import for Rovers

Dave AA6YQ
 

+ AA6YQ comments below
Actually there are 4 QPs that weekend, 7qp, inqp, neqp, and Delaware qp. 
7qp and inqp use state/county, neqp uses county/state, and DEQP uses a completely different exchange - NDE (New Castle), KDE (Kent County), and SDE (Suffix county)

+ So then there's no ambiguity. Thanks, Scott!

      73,

           Dave, AA6YQ


Re: Intermitent Rig Control Errors to my ICOM 7610

Mike Wasserburger - WF0M
 

I moved it to 25ms as suggested and have yet to see the error, so this change seems to be helping.

thanks,

Mike/WF0M



Re: DX Atlas Not Showing DX Keeper QSO’s

Dave AA6YQ
 

+ AA6YQ comments below

After further experimentation, I found that now, DX ATAS is now opening twice when I run DX Launcher. The first DX Atlas map that loads does show QSO’s when I click “Plot” in DX Keeper, but the second DX Atlas map (that immediately loads on top of the first) does not.

In neither case does terminating DXLABs applications in DX Launcher close either DX Atlas map  

So, I guess my problems are now: 1) How do I prevent the second incidence of DX Atlas from loading and 2) How do I get DX Launcher to automatically close DX Atlas with the the DX Labs applications.

+ On the DXLab Launcher's Configuration window, remove the two entries you created that start DXAtlas from the "Apps Started Before DXLab Apps" and "Apps Started After DXLab Apps" tab.

+ With DXView configured to use DX Atlas as its world map, starting DXView will start DX Atlas, and terminated DXView will terminate DX Atlas.

       73,

             Dave, AA6YQ


DX Atlas Not Showing DX Keeper QSO’s

Brian Deuby
 

After further experimentation, I found that now, DX ATAS is now opening twice when I run DX Launcher. The first DX Atlas map that loads does show QSO’s when I click “Plot” in DX Keeper, but the second DX Atlas map (that immediately loads on top of the first) does not.

In neither case does terminating DXLABs applications in DX Launcher close either DX Atlas map  

So, I guess my problems are now: 1) How do I prevent the second incidence of DX Atlas from loading and 2) How do I get DX Launcher to automatically close DX Atlas with the the DX Labs applications.

 Thanks, Brian K8GRR 

 


DX Keeper Won’t Plot QSO’s on DX Atlas Map

Brian Deuby
 

Recently I found that when I click “Plot” on DX Keeper it does not plot my QSO’s on DX Atlas. After experimenting with various settings without success, I uninstalled and reinstalled DX Atlas. 


DX Labs launcher launches the reinstalled DX Atlas but when I click “Plot” in DX Keeper, it briefly says “Plotting 440 QSO’s (and shows the horizontal progress bar)  - but nothing shows up on the DX Atlas map. Also, unlike was previously the case, DX Atlas no longer closes when I terminate DX Labs launcher. 


I’m guessing that I’m overlooking a setting in DX Keeper and/or DX Atlas, but right now, I’m stumped. Any guidance would be appreciated. 

Thanks, Brian K8GRR 

 


Re: ADIF import for Rovers

Scott Stembaugh
 

Actually there are 4 QPs that weekend, 7qp, inqp, neqp, and Delaware qp. 
7qp and inqp use state/county, neqp uses county/state, and DEQP uses a completely different exchange - NDE (New Castle), KDE (Kent County), and SDE (Suffix county)  

On Thu, Mar 18, 2021, 09:04 Joe Subich, W4TV <lists@...> wrote:

 > + During the weekend you cite, would operators QRV from counties in
 > different states give the same county code?

The 7QP participants use a county code/exchange that includes state
and county.  I have not researched if there is any overlap between
the other two states.

73,

    ... Joe, W4TV


On 2021-03-17 10:59 PM, Dave AA6YQ wrote:
> + AA6YQ comments below
>
>     There are multiple examples of overlapping state QSO parties. One
>     can not count on the Contest ID to define the state. I know of one
>     weekend that has a regional QSO party (7QP) plus two other states -
>     Maryland and Indiana, IIRC.
>
> + During the weekend you cite, would operators QRV from counties in
> different states give the same county code?
>
>         73,
>
>                 Dave, AA6YQ







Re: Any DXLab issues w/ WIN 10 V20H2?

neil_zampella
 

The entire suite works great under the latest Win10.  

Neil, KN3ILZ

On 3/18/2021 6:59 AM, Alan Swinger wrote:
Getting messages from MS about updating WIN 10 to V20H2. Has anyone done so and were their any subsequent problems with DXLab apps?
Thanks - Alan K9MBQ


Re: Any DXLab issues w/ WIN 10 V20H2?

Norm - KC1BMD
 

I installed DXLab Suite about two months ago (WinWarbler installed but not using it presently) and 20H2 has been running since May 2020.
-> No issues that I can detect.

--
73, Norm/KC1BMD


Re: ADIF import for Rovers

Joe Subich, W4TV
 

+ During the weekend you cite, would operators QRV from counties in
different states give the same county code?
The 7QP participants use a county code/exchange that includes state
and county. I have not researched if there is any overlap between
the other two states.

73,

... Joe, W4TV


On 2021-03-17 10:59 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
There are multiple examples of overlapping state QSO parties. One
can not count on the Contest ID to define the state. I know of one
weekend that has a regional QSO party (7QP) plus two other states -
Maryland and Indiana, IIRC.
+ During the weekend you cite, would operators QRV from counties in different states give the same county code?
       73,
               Dave, AA6YQ


Any DXLab issues w/ WIN 10 V20H2?

Alan Swinger
 

Getting messages from MS about updating WIN 10 to V20H2. Has anyone done so and were their any subsequent problems with DXLab apps?
Thanks - Alan K9MBQ


Re: ADIF import for Rovers

Dave AA6YQ
 

+ AA6YQ comments below
There are multiple examples of overlapping state QSO parties. One
can not count on the Contest ID to define the state. I know of one
weekend that has a regional QSO party (7QP) plus two other states -
Maryland and Indiana, IIRC.

+ During the weekend you cite, would operators QRV from counties in different states give the same county code?

       73,

               Dave, AA6YQ


Re: DXK: QSO could not be logged

Dave AA6YQ
 

+ AA6YQ comments below
Thank you Dave, I have sent the pop-up and the error logfile.
+ Thanks, Bernd. I sent you a new version of DXKeeper with diagnostics and with the ability to automatically retry when a new log entry cannot be created due to lack of resources. Please let me know how it goes...

       73,
            
            Dave, AA6YQ


Re: DXK: QSO could not be logged

Bernd - KB7AK
 

On Wed, Mar 17, 2021 at 02:41 PM, Dave AA6YQ wrote:
aa6yq (at) ambersoft.com
Thank you Dave, I have sent the pop-up and the error logfile.

73,
Bernd - KB7AK

3021 - 3040 of 203452