Date   

Re: Repeating entry for Note or Comment field when using Capture ?

Dave AA6YQ
 

+ AA6YQ comments below

As I still have a long way to go in grasping/understanding all the nuances of DXLab here is one that may have an easy explanation that I've not yet found.
So here goes:

DXK Capture panel open for logging a call.
I want to enter some repeating verbiage in either the Note or Comment field before I save the Q.

I know I can easily keep retyping the same information, but is it possible to have the information saved or ready for use on a repeating basis?

Events where I do such include: 13 Colonies, Route 66, SST, etc., etc..

I've created my own habit of entering "13 Colonies - 2021" in the Note or Comment field. Similar for "Route 66 - 2021", "SST", etc., etc..

Suggestions?

+ The Comment item is intended to record information specific to its QSO, so no "default Comment" capability is provided. There are three ways you could repeatedly record identical information in a sequence of QSOs made during the same "on-air activity":

1. the "Contest ID" item (specify default value on the Configuration window's Contest tab)

2. the "QSL Msg" item (specify default value on the Configuration window's Defaults tab)

3. a user-defined item (specify default value on the Configuration window's "User Items" tab)

+ My advice is to configure a user-defined item named "on-air activity":

https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#User%20Items%20tab

+ Set the item's "Style" to List, and create a text file containing the names of the on-air activities in which you participate. I recommend against including the year in the activity name, e.g. define

"13 Colonies"

+ rather than

"13 Colonies 2021".

+ Should you wish to filter the Log Page Display to contain only QSOs made during the 2021 "13 Colonies" activity, you'd use the SQL expression

(APP_DXKEEPER_USER_DEFINED_0 = '13 Colonies') and (YEAR(QSO_BEGIN)=2021)

73,

Dave, AA6YQ


Re: Launcher Question

Ben Coleman NJ8J
 

On 10/18/2021 12:46 PM, Pete W1RM wrote:
On my new PC I have launcher set to start by putting a shortcut in the windows startup folder.  When the PC boots, launcher is running in the background as I can see the process in Task Manager.  However, it seems to take nearly a minute before the launcher screen appears on my desktop.  I can’t find any setting in Launcher that might control this. Auto start is not selected so all I’m looking for is for Launcher to open fully.
While you've got Task Manager open, take a look at the Disk % in use (on the Processes tab). If you're like all the other Windows machines I've used, you'll probably see it pegged at 100% for several minutes after startup. Launcher is probably contending with all the other 'launch-on-startup' processes for disk access. I've pretty much gotten used to letting the computer sit for a few minutes after startup to let all of that settle out. If I'm in a hurry, I'll launch Task Manager and watch for Disk % to settle down to something more normal.

Ben
--
Ben Coleman nj8j@...
"I love the way Microsoft follows standards. In much the
same manner that fish follow migrating caribou."
Paul Tomblin


Re: Repeating entry for Note or Comment field when using Capture ?

dxradio33
 

One way would be to highlight the text and copy it to the clipboard then paste it into the box using control 'V'


Repeating entry for Note or Comment field when using Capture ?

 

As I still have a long way to go in grasping/understanding all the nuances of DXLab here is one that may have an easy explanation that I've not yet found.
So here goes:

DXK Capture panel open for logging a call.
I want to enter some repeating verbiage in either the Note or Comment field before I save the Q.

I know I can easily keep retyping the same information, but is it possible to have the information saved or ready for use on a repeating basis?

Events where I do such include:  13 Colonies, Route 66, SST, etc., etc..

I've created my own habit of entering "13 Colonies - 2021" in the Note or Comment field.  Similar for "Route 66 - 2021", "SST", etc., etc..

Suggestions?

--
73 - Nolan K.  -  ki5io


Re: Old Use - New Install

Dave AA6YQ
 

I had to re-install Windows 10 on my computer (PLEASE don't ask me why - Its done). I downloaded DXLauncher and proceeded to reinstall DXLab Suite per instructions for my IC-7300.

So, using DXLaubcher, I installed all modules. I checked with DXView for new versions and this is what I got:

+ DXView doesn't indicate whether new versions of applications are available; it only does that for databases.

+ This group does not convey attachments, so no one can see what you posted.

So far, so good. However when I launch DXCommander, it tells me this:

+ This group does not convey attachments, so no one can see what you posted.

So I go to the General tab and I get this list for radios while looking for the IC-7300:

As you can see, the 7300 isn't even listed.

What am I doing wrong?

+ If you look at the title bar of Commander's Main window, you'll likely see that you are running a long-obsolete version of Commander. The current public version of Commander is 15.2.0. If that's not the version that you are running, terminate Commander, and direct the Launcher to upgrade Commander - and any other DXLab applications that haven't been upgraded to their current versions.

+ If this post doesn't get you going, please let me know.

73,

Dave, AA6YQ


Old Use - New Install

n6rsh
 

Hi,

 I had to re-install Windows 10 on my computer (PLEASE don't ask me why - Its done). I downloaded DXLauncher and proceeded to reinstall DXLab Suite per instructions for my IC-7300. So, using DXLaubcher, I installed all modules. I checked with DXView for new versions and this is what I got:


So far, so good. However when I launch DXCommander, it tells me this:



So I go to the General tab and I get this list for radios while looking for the IC-7300:



As you can see, the 7300 isn't even listed.
What am I doing wrong? I have been using HRD but I like DXKeeper's logbook better so I am starting to migrate BACK to DXLabs and FLdigi.

Thanks for looking and 73,
Steve Panattoni N6RSH


Re: Low priority feature request

Björn SM7IUN
 

Wonderful. Very grateful.

Björn SM7IUN

Den tis 19 okt. 2021 kl 19:18 skrev Dave AA6YQ <aa6yq@...>:

+ AA6YQ comments below

DXKeeper uses the application specific key APP_DXKeeper_DOK for German DOK.
There is actually a standardized key for this, DARC_DOK. It would be nice if DXKeeper recognized and used this also.

+ Thanks, Björn! I forgot about the addition to DARC_DOK to ADIF. The next version of DXKeeper exports DARC_DOK to ADIF and TDF files, and imports DARC_DOK in addition to APP_DXKeeper_DOK.

       73,

               Dave, AA6YQ







Re: VPN interference

Dave AA6YQ
 

+ AA6YQ comments below
Love exploring the options in this suite.  Got it running on PC 1 in various schemes to ic7100 on PC 2.  Working with FLDigi & WSJT.  All on Win10.  Recently add Norton VPN to the mix.  Had to tunnel most of the programs.  All is working well.  Except Pathfinder.  I tunnelled Pathfinder, Patherfind439 and Pathfinder526.  Still PV can't reach out to the internet.  It does get the call sign from DxView but 'cant reach this page' being qrz.com.
     Any ideas how to gain access? 

+ Pathfinder is a thin layer of code on top of Microsoft's "web browser" control. I suggest that you ask Norton technical support why their VPN doesn't handle it correctly.

         73,

               Dave, AA6YQ

 


VPN interference

Rory Griffin, W4RJG
 

Hi All,
     Love exploring the options in this suite.  Got it running on PC 1 in various schemes to ic7100 on PC 2.  Working with FLDigi & WSJT.  All on Win10.  Recently add Norton VPN to the mix.  Had to tunnel most of the programs.  All is working well.  Except Pathfinder.  I tunnelled Pathfinder, Patherfind439 and Pathfinder526.  Still PV can't reach out to the internet.  It does get the call sign from DxView but 'cant reach this page' being qrz.com.
     Any ideas how to gain access?  Thnx,

73s Rory W4RJG


Re: User Defined Box for Winwarbler?

Scott
 

Thank you Dave! 

Thanks for the help. Got the POTA and the SKCC user defined boxes showing.

73 Scott
KN3A


Re: MSHV and DXlab

Henk Remijn PA5KT
 

MSHV has implemented a subset of the UDP communication of WSJT-X.

For me Spotcollector works fine with MSHV. Decoded stations show up in Spotcollector.
The automatic logging from MSHV through Spotcollector to DXlab also works fine.

But anyway that was not the question.

I have Commander running together with MSHV.

What do you mean by Commander and MSHV dont work together?

Do you get an error?

73 Henk

Op 19-10-2021 om 22:46 schreef Joe Subich, W4TV:


MSHV is a "hostile fork" of WSJTX.  MSHV has screwed up many of the
UDP messages and does not support many of the WSJTX interfaces.

I don't know if the screwed up UDP messages are responsible for
the issue or if it is the lack of support for some interface that
Commander relies on.  Suffice it to say that MSHV is not compatible
with many applications designed to work with WSJTX.

73,

   ... Joe, W4TV


On 2021-10-19 4:34 PM, Willem Angenent wrote:
I am running MSHV and DXkeeper and that is working just fine using UDP Broadcast.
Now I just tried to run Commander at the same time and that won't work.
What am I doing wrong???

Thanks,

Will
K6ND




Re: User Defined Box for Winwarbler?

Dave AA6YQ
 

+ AA6YQ comments below

In DXKeeper, I have a User defined POTA for logging those contacts. I am trying to enable the user defined name into Winwarbler, however I am not finding a way to enable those. I see the SOTA, which I will also use but would like to be able to add the POTA park reference if possible as well.

+ Click the red-highlighted button in this screen shot to expand the Main window's "Log QSOs" panel; each time you click. more items will become visible - including all 8 user-defined items:

http://www.dxlabsuite.com/Wiki/Graphics/WinWarbler/LogMaximal.jpg

For more information about logging QSOs from WinWarbler, see

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

73


User Defined Box for Winwarbler?

Scott
 

In DXKeeper, I have a User defined POTA for logging those contacts. I am trying to enable the user defined name into Winwarbler, however I am not finding a way to enable those. I see the SOTA, which I will also use but would like to be able to add the POTA park reference if possible as well.

Thanks in advance

Scott
KN3A


updated eQS: AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window.

73,

Dave, AA6YQ


WAS RTTY multi-band progress report

Dave AA6YQ
 

+ AA6YQ comments below

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Gordon LaPoint
Sent: Tuesday, October 19, 2021 7:31 AM
To: DXLab@groups.io
Subject: Re: [DXLab] what FT8 software interoperates best with DXLabs suite?

I have a RTTY WAS from 2008, would like to expand that to multiband RTTY, but hard to track right now.

I can get a list of worked states on each band by filtering the log on RTTY contacts only, but its hard to track on paper only.

+ Running the script appended below will generate a WAS RTTY progress report that includes progress for each band.

73,

Dave, AA6YQ


filter Mode='RTTY'
report us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='160m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='80m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='40m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='30m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='20m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='17m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='15m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='12m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='10m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='6m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

filter (Mode='RTTY') and (Band='2m')
AppendReport us_states <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt

Display <ReportsFolder><operator> <ISOdate> us_states_multiband_RTTY.txt


Re: MSHV and DXlab

Joe Subich, W4TV
 

MSHV is a "hostile fork" of WSJTX. MSHV has screwed up many of the
UDP messages and does not support many of the WSJTX interfaces.

I don't know if the screwed up UDP messages are responsible for
the issue or if it is the lack of support for some interface that
Commander relies on. Suffice it to say that MSHV is not compatible
with many applications designed to work with WSJTX.

73,

... Joe, W4TV

On 2021-10-19 4:34 PM, Willem Angenent wrote:
I am running MSHV and DXkeeper and that is working just fine using UDP Broadcast.
Now I just tried to run Commander at the same time and that won't work.
What am I doing wrong???
Thanks,
Will
K6ND


Re: MSHV and DXlab

Dave AA6YQ
 

+ AA6YQ comments below
I am running MSHV and DXkeeper and that is working just fine using UDP Broadcast.
Now I just tried to run Commander at the same time and that won't work.
What am I doing wrong???

+ There is no supported inter-operation bewteen MSHV and DXLab.

+ DXLab's inter-interoperation with WSJT-X relies on a set of programmatic interfaces (APIs) provided by WSJT-X. Unless a variant or fork of WSJT-X accurately implements those APIs, the inter-operation will not work.

       73,

             Dave, AA6YQ


MSHV and DXlab

Willem Angenent
 

I am running MSHV and DXkeeper and that is working just fine using UDP Broadcast.
Now I just tried to run Commander at the same time and that won't work.
What am I doing wrong???

Thanks,

Will
K6ND



Re: SC says 'Invalid Spot Frequency'

Dave AA6YQ
 

+ AA6YQ comments below
Yes, that is what the BandModes file has.  I see that is the same for all bands (bottom range .1 up from bottom of band).  Is there a particular reason for this, other than to discourage spots at band edges? 

+ That was the result of a 2009 discussion here about ignoring "bottom-of-band" spots, which often are broadcast messages rather than DX spots; see

https://groups.io/g/DXLab/message/65854

And why would it work for Local spots but not Cluster spots?

+ The above-mentioned "bottom-of-band spot" problem does not exist with local spots, so they don't reference the sub-band definition file to derive the band name from the frequency; anything between 24890 and 24990 (inclusive) is considered 12m.

       73,

             Dave, AA6YQ

 


Re: SC says 'Invalid Spot Frequency'

Scott Stembaugh
 

Thanks, Dave.

Yes, that is what the BandModes file has.  I see that is the same for all bands (bottom range .1 up from bottom of band).  Is there a particular reason for this, other than to discourage spots at band edges?  And why would it work for Local spots but not Cluster spots?

73,
--scott


On Tue, Oct 19, 2021 at 3:24 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below
I was trying to spot J5T on 24.890 and I get a pop up from SpotCollector,
 
"24890kHz is not a valid spot frequency".
 
Is this because it is right on the band edge? (He was working up 1.x).

+ What's the lower bound on that band segment in SpotCollector's sub-band definition file?

+ The sub-band definition file included with SpotCollector specifies this entry:

24890.1,24915,CW,12M

+ which makes 24890 invalid.

        73,

                Dave, AA6YQ

 

4741 - 4760 of 208692