Date   

Re: User Defined Controls with Multi Radio Set Up

Dave AA6YQ
 

+ AA6YQ comments below
Thanks Dave. I think I got it pretty close. I know the HEX for the 7300 is 94, however I'm not sure what to put in for they Yaesu 891. I have the User-Defined Control set working on the 7300. 

+ Only Icom transceivers have a CI-V address. It's not necessary to specify one for other manufacturer's models like your Yaesu FT-891.

       73,

            Dave, AA6YQ


Re: User Defined Controls with Multi Radio Set Up

Scott
 

Thanks Dave. I think I got it pretty close. I know the HEX for the 7300 is 94, however I'm not sure what to put in for they Yaesu 891. I have the User-Defined Control set working on the 7300. 

Thanks again!
73 Scott
KN3A


Re: User Defined Controls with Multi Radio Set Up

Dave AA6YQ
 

+ AA6YQ comments below

I've configured both my IC 7300 and FT 891 as Multi Radios in Commander. It was simple enough to do. I haven't found a way to have User Defined Profiles for each radio when I switch back and forth. The only solution I can think of is to hit 'Alt' and use those additional User-defined Controls for the FT 891. Is there another way?

+ Yes: specify a "user-defined control set" for each primary transceiver; see the 4th paragraph in the "Primary CAT Port Switching" section of

<https://www.dxlabsuite.com/commander/Help/ControllingMultipleRadios.htm#User-defined%20Control%20Set>

73,

Dave, AA6YQ


User Defined Controls with Multi Radio Set Up

Scott
 

I've configured both my IC 7300 and FT 891 as Multi Radios in Commander. It was simple enough to do. I haven't found a way to have User Defined Profiles for each radio when I switch back and forth. The only solution I can think of is to hit 'Alt' and use those additional User-defined Controls for the FT 891. Is there another way?

Thanks,
Scott KN3A


Re: DXLab QSO Import Issue

Barry Priddy
 

Thanks Iain. I missed the "consider gridsquares" check box, but it's checked now.

I only import .adi contest logs from N1MM+ into DXKeeper, so I set the time span to whatever the length of the contest was.

73, Barry Priddy - K5VIP/KG4BP


Re: US states and DXlabs

Dave AA6YQ
 

+ AA6YQ comments below

Hi guys.....I am busy importing paper logs into DXlabs and I am wondering when I log a US station,

where can I input the state abbreviation so that I can see it in the "state" column of the DXkeeper Screen??

+ If you're manually entering "already completed" QSOs from a paper log, then should be using the Main window's "Log QSOs" tab, as
described in

<https://www.dxlabsuite.com/dxkeeper/Help/LogCompletedMain.htm>

+ To be able to specify a US state when logging QSOs from the "Log QSOs" tab, make the Award panel visible by checking the Award
box in the "Log Panels" panel on the Configuration window's Log tab.

+ On the Main window's "Log QSOs" tab, when you click the New button to create an empty new QSO, the Award panel will display a pair
of items labeled "pri sub" and "sec sub", abbreviations for "primary administrative subdivision" and "secondary administrative
subdivision" respectively. When you type a callsign into the QSO panel's call item and then strike the Tab or Enter key, DXKeeper
will analyze the callsign to determine its DXCC entity. If the callsign is located in the continental US, Alaska, or Hawaii, the
labels on the "pri sub" and "sec sub" items will change to state and county respectively; both will provide a down-facing black
triangle that lets you choose a valid state for the callsign's DXCC entity, and a valid county for the callsign's DXCC entity and
selected state.

How does DXlab determine a stations state for the purpose of the WAS report if its not entered anywhere?

+ Just because you haven't made the Award panel visible doesn't mean that the State has not been entered by one of DXkeeper's
automatic mechanisms that you have enabled:

1. In DXView, you can define an override for a callsign, specifying the details of its current location -- including its US State:

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


2. DXView can install the USAP database, which knows the state each US callsign has specified to the FCC as its current station
location:

< https://www.dxlabsuite.com/dxview/Help/Operation.htm#Databases>


3. DXKeeper can be configured to query online or local callbooks that report a US station's state:

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


There is no actual State input line on the DXkeeper screen.

+ That's because you haven't made the Award panel visible. I suggest that you review

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

+ and then take a look at this table

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

+ which lists and describes the 119 items of information that DXKeeper can record with each QSOs, and shows which "Log panel" to
enable so you can specify/view each item of information.



If I worked W3ABC/W7, How does the WAS report determine which state in zone 7 he is in?

+ See my explanation above.

+ As Gil W0MN noted, relying on the USAP database or a callbook lookup to determine the location of your QSO partner in QSO
completed long ago may not produce an accurate result, as the op may have subsequently moved, or may have been temporarily operating
from a location other than home when you had your QSO. Asking your QSO partner is one way to know for sure. An LoTW confirmation
with a US station will generally include your QSO partner's specification of their location; DXKeeper's "Sync LoTW QSLs" function
will inform you if what you logged and what your QSO partner specified are different; see

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


73,

Dave, AA6YQ


Re: DXLab Restore Problem

Alan Swinger
 

Roger. I think I would have been up fairly quickly as well had I not let the Staples Techs move DXLab files from what was supposed to be a Clone backup drive to the computer after they had to reinstall the OS after a new HD install. It turned out that a Clone of a Dell Laptop does not "Clone" to an HP machine, and that clones only work to same brand machines . .  or so the story goes from the local Techs.
73, Alan K9MBQ

On Tue, Sep 15, 2020 at 3:20 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Dave - Tks. Took care of the PF Script error message problem and will pursue the Blank Button issue per the web site suggested. Also re-did the Launcher paths as you advised and all seems OK. I think the DXLab system is back up  and running as designed except for the monitor item mentioned.

+ What's "the monitor item"?

Sorry to absorb so much of your and the site's time, but am very appreciative of your assistance to help me get this system back on line w/ DXLab. I thank you very much for your tutoring. and responses to my sometimes bad assumptions and queries, but perhaps others may have learned a bit as well.

+ the primary lesson learned is to follow the instructions in

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

+ Björn SM7IUN recently reported that after a catastrophic failure, he had all of his DXLab applications running and configured 15 minutes after re-installing Windows.

       73,

            Dave, AA6YQ






Re: US states and DXlabs

Gilbert Baron W0MN
 

All true but it could be very wrong. If you are entering manually and especially if old contacts you had better enter this information actually since the lookup is the current or  latest updated data which often is not even close. People move and call signs often do not change.

 

Outlook Laptop Gil W0MN

Hierro candente, batir de repente

44.08226N 92.51265W EN34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of ND9G Mike
Sent: Tuesday, September 15, 2020 18:37
To: DXLab@groups.io
Subject: Re: [DXLab] US states and DXlabs

 

Hello Ted,

 

The state is stored in the primary subdivision field (pri sub). The display will change the field label based on the DXCC entity of the call entered. The secondary subdivision would be used for county.

 

If you're using the capture window, you can click the lookup button and it will use the configured lookup database to populate the state and county. If you're working on the log page display, then you can click the CBA button to pull the information from configured callbooks. It may also pull information from LoTW if you sync with that.

 

If you want to see the state field in the log page display, you can edit that to display the column you see fit. You can select state to add them to the field you've elected to display.

 

 

73,

Mike ND9G

 

 

On Tue, Sep 15, 2020 at 6:27 PM Ted Boerkamp <tboerkamp@...> wrote:

Hi guys.....I am busy importing paper logs into DXlabs and I am wondering when I log a US station,

where can I input the state abbreviation so that I can see it in the “state” column of the DXkeeper

Screen?? How does DXlab determine a stations state for the purpose of the WAS report if its not entered anywhere?

There is no actual State input line on the DXkeeper screen.

If I worked W3ABC/W7, How does the WAS report determine which state in zone 7 he is in?

Any help in understanding this is most welcome.

Thanks for a great program!!

73  Ted VE3SS

 


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: US states and DXlabs

ND9G Mike
 

Hello Ted,

The state is stored in the primary subdivision field (pri sub). The display will change the field label based on the DXCC entity of the call entered. The secondary subdivision would be used for county.

If you're using the capture window, you can click the lookup button and it will use the configured lookup database to populate the state and county. If you're working on the log page display, then you can click the CBA button to pull the information from configured callbooks. It may also pull information from LoTW if you sync with that.

If you want to see the state field in the log page display, you can edit that to display the column you see fit. You can select state to add them to the field you've elected to display.


73,
Mike ND9G


On Tue, Sep 15, 2020 at 6:27 PM Ted Boerkamp <tboerkamp@...> wrote:

Hi guys.....I am busy importing paper logs into DXlabs and I am wondering when I log a US station,

where can I input the state abbreviation so that I can see it in the “state” column of the DXkeeper

Screen?? How does DXlab determine a stations state for the purpose of the WAS report if its not entered anywhere?

There is no actual State input line on the DXkeeper screen.

If I worked W3ABC/W7, How does the WAS report determine which state in zone 7 he is in?

Any help in understanding this is most welcome.

Thanks for a great program!!

73  Ted VE3SS

 


US states and DXlabs

Ted Boerkamp
 

Hi guys.....I am busy importing paper logs into DXlabs and I am wondering when I log a US station,

where can I input the state abbreviation so that I can see it in the “state” column of the DXkeeper

Screen?? How does DXlab determine a stations state for the purpose of the WAS report if its not entered anywhere?

There is no actual State input line on the DXkeeper screen.

If I worked W3ABC/W7, How does the WAS report determine which state in zone 7 he is in?

Any help in understanding this is most welcome.

Thanks for a great program!!

73  Ted VE3SS

 


Re: DXLab Restore Problem

Dave AA6YQ
 

+ AA6YQ comments below

Dave - Tks. Took care of the PF Script error message problem and will pursue the Blank Button issue per the web site suggested. Also re-did the Launcher paths as you advised and all seems OK. I think the DXLab system is back up and running as designed except for the monitor item mentioned.

+ What's "the monitor item"?

Sorry to absorb so much of your and the site's time, but am very appreciative of your assistance to help me get this system back on line w/ DXLab. I thank you very much for your tutoring. and responses to my sometimes bad assumptions and queries, but perhaps others may have learned a bit as well.

+ the primary lesson learned is to follow the instructions in

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

+ Björn SM7IUN recently reported that after a catastrophic failure, he had all of his DXLab applications running and configured 15 minutes after re-installing Windows.

73,

Dave, AA6YQ


Re: DXLab Restore Problem

Alan Swinger
 

Dave - Tks. Took care of the PF Script error message problem and will pursue the Blank Button issue per the web site suggested. Also re-did the Launcher paths as you advised and all seems OK. I think the DXLab system is back up  and running as designed except for the monitor item mentioned.
Sorry to absorb so much of your and the site's time, but am very appreciative of your assistance to help me get this system back on line w/ DXLab. I thank you very much for your tutoring. and responses to my sometimes bad assumptions and queries, but perhaps others may have learned a bit as well. 
I think I am back to a whole Up system.
All the best and 73, 
Alan K9MBQ

On Tue, Sep 15, 2020 at 1:37 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Dave - apparently I am doing something wrong w/ the Workspace. When I select Folder in the Workspace box and click Load Settings I get a Registry Editor Box with a question: Do you want to allow this app to make changes to your device? Whether I click Yes or No, the Box does not go away.
I tried to create a new Workspace from my Laptop DXLab system, get the same result.

+ Evidently, your security settings are preventing the Launcher from loading a file containing Windows Registry settings. If you can't correct this, you'll have to manually re-establish your Pathfinder searches. See

< http://www.dxlabsuite.com/pathfinder/AssignSearchButton.htm>

I compared contents of the PF files on the laptop (working OK) w/ the DT we are working on and the only File Folder missing on the latter is the INSTALL file. Is it possible to simply copy it to a thumb drive and put into the PF folder on the DT?

+ The Install folder is not needed after installation is complete

The Script Error that pops uo says:
Script Error with a message that says an error has occurred in the script on this page and the shows:
Line   0
Char   0
Error   Script Error
Code   0
URL: https://pagead2.googlesyndication.com/pagead/show_ad.js

+ See

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


Re the instructions you gave me to fix the DXLab App paths in the Launched Config window, the executable files I selected were the latest version of the several that showed in each of the Explorer DXLab app files  . .  in which the .exe is not shown. In the updated Launcher Config list, the .exe is shown after each. I assume that when the inevitable updates come, these will all update OK.

+ No, they will not.

Sent a screen shot of the Launcher Config list to you separately so yuou can see what I am saying.

+ The example I provided in

<https://groups.io/g/DXLab/message/196275>

+ was to select the file

CI-V Commander.exe

+ in your Commander folder. Your screen shot shows that you instead selected

CI-V Commander1465.exe

+ That means that after a new Commander upgrade becomes available and you direct the Launcher to upgrade, the Launcher will continue to start Commander version 14.6.5.

+ You made the same error with DXKeeper, DXView, Pathfinder, PropView, SpotCollector, and WinWarbler. I suggest that you select the correct .exe files.

        73,

              Dave, AA6YQ





Re: Grid Glitch

AE7AP
 

Dave:
I am referring to the Grid Computation on the "my QTHs" tab (after pushing the "New" button).  Lat/Long can be entered in a Decimal-Degree format (which is very nice).  The grid is then computed in real-time (also very nice).  The Decimal-Degree Lat/Long is then correctly converted to DDD-MM-SS in the summary table lower on the page.  It is only the Grid location that is incorrect & the grid is only incorrect if the 4th significant digit is included with the Decimal-Degree.  It works fine with three significant digits.  It is minor - but I thought I would bring it to your attention.

I am not (in this example) importing an ADIF file.

Thank you for everything you do & 73,
Rob - AE7AP


Re: WinWarbler macro suggestion

Dave AA6YQ
 

+ AA6YQ comments below

Apologies, I fell behind on following my own suggestion. But the comments are correct. POTA and the park reference go into the special interest group fields of the MyQTH and I create a new MyQTH for each park I activate. Pulling the MY_SIG_INFO field into a WW function key definition as a macro would eliminate the embarrassment of forgetting to update the definition as making sure I have the QTH set correctly is one of the first steps I do when setting up.

I do use a User Defined field for POTA as it shows up in the capture window as well as transfer any received park info into the Details pane SIG fields through a script.

+ If you employ a user-defined field for POTA in DXKeeper, it will also be available in the "QSO Info" panel on WinWarbler's Main window.

+ Since no one responded to my query in

<https://groups.io/g/DXLab/message/196271>

+ I've sent you a new version of DXKeeper that makes the default myQTH's Sig and "Sig Info" items accessible to other applications, and a new version of WinWarbler that provides <myqthsig> and <myqthsiginfo> macros, as you requested.

+ Please let me know how it goes.

73,

Dave, AA6YQ


Re: Grid Glitch

Dave AA6YQ
 

+ AA6YQ comments below

I note an apparent glitch with the Grid computation from Lat/Long. It can be replicated as follows:

Lat: 45.9997
Long: -115.0808
Should be: DN25lx
DXKeeper: DN26la

It correctly computes if the significant digits for Lat are limited to 45.999

+ Latitudes in DXKeeper are specified with degrees, minutes, and seconds -- not with signed decimal numbers. Where in DXKeeper are you specifying the latitude as 45.9997 ?

+ If you are importing an ADIF record, please post this record's LAT field.

73,

Dave, AA6YQ


Re: DXLab Restore Problem

Dave AA6YQ
 

+ AA6YQ comments below

Dave - apparently I am doing something wrong w/ the Workspace. When I select Folder in the Workspace box and click Load Settings I get a Registry Editor Box with a question: Do you want to allow this app to make changes to your device? Whether I click Yes or No, the Box does not go away.
I tried to create a new Workspace from my Laptop DXLab system, get the same result.

+ Evidently, your security settings are preventing the Launcher from loading a file containing Windows Registry settings. If you can't correct this, you'll have to manually re-establish your Pathfinder searches. See

< http://www.dxlabsuite.com/pathfinder/AssignSearchButton.htm>

I compared contents of the PF files on the laptop (working OK) w/ the DT we are working on and the only File Folder missing on the latter is the INSTALL file. Is it possible to simply copy it to a thumb drive and put into the PF folder on the DT?

+ The Install folder is not needed after installation is complete

The Script Error that pops uo says:
Script Error with a message that says an error has occurred in the script on this page and the shows:
Line 0
Char 0
Error Script Error
Code 0
URL: https://pagead2.googlesyndication.com/pagead/show_ad.js

+ See

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


Re the instructions you gave me to fix the DXLab App paths in the Launched Config window, the executable files I selected were the latest version of the several that showed in each of the Explorer DXLab app files . . in which the .exe is not shown. In the updated Launcher Config list, the .exe is shown after each. I assume that when the inevitable updates come, these will all update OK.

+ No, they will not.

Sent a screen shot of the Launcher Config list to you separately so yuou can see what I am saying.

+ The example I provided in

<https://groups.io/g/DXLab/message/196275>

+ was to select the file

CI-V Commander.exe

+ in your Commander folder. Your screen shot shows that you instead selected

CI-V Commander1465.exe

+ That means that after a new Commander upgrade becomes available and you direct the Launcher to upgrade, the Launcher will continue to start Commander version 14.6.5.

+ You made the same error with DXKeeper, DXView, Pathfinder, PropView, SpotCollector, and WinWarbler. I suggest that you select the correct .exe files.

73,

Dave, AA6YQ


Re: WinWarbler macro suggestion

MARK KEMPISTY
 
Edited

Apologies, I fell behind on following my own suggestion.  But the comments are correct.  POTA and the park reference go into the special interest group fields of the MyQTH and I create a new MyQTH for each park I activate.  Pulling the MY_SIG_INFO field into a WW function key definition as a macro would eliminate the embarrassment of forgetting to update the definition as making sure I have the QTH set correctly is one of the first steps I do when setting up.

I do use a User Defined field for POTA as it shows up in the capture window as well as transfer any received park info into the Details pane SIG fields through a script

73,
Mark AA3K


Grid Glitch

AE7AP
 

I note an apparent glitch with the Grid computation from Lat/Long.  It can be replicated as follows:

Lat:  45.9997
Long: -115.0808
Should be: DN25lx
DXKeeper:  DN26la

It correctly computes if the significant digits for Lat are limited to 45.999

73,
Rob - AE7AP


Re: DXLab QSO Import Issue

iain macdonnell - N6ML
 

On Tue, Sep 15, 2020 at 6:41 AM Barry Priddy via groups.io
<nbpriddy=aol.com@groups.io> wrote:

During the ARRL VHF contest this past weekend, I worked a rover on 2 metersin two different grid squares.=C2=A0 I have the DXLab import function set to delete duplicate QSOs. When I imported my contest log from N1MM+, one of the 2 meter QSOs was deleted even though the contacts were in different grid squares. Apparently, the import function in DXLab doesn't check QSOs to that level of detail before deleting.
On the "Import QSOs" tab, "Duplicate Checking" panel, do (did) you
have "Consider gridsquares" enabled?

You may also want to lower the time range for duplicate matching (same panel).

73,

~iain / N6ML


DXLab QSO Import Issue

Barry Priddy
 

During the ARRL VHF contest this past weekend, I worked a rover on 2 metersin two different grid squares.=C2=A0 I have the DXLab import function set to delete duplicate QSOs.  When I imported my contest log from N1MM+, one of the 2 meter QSOs was deleted even though the contacts were in different grid squares. Apparently, the import function in DXLab doesn't check QSOs to that level of detail before deleting.

Barry Priddy - K5VIP/KG4BP