+ AA6YQ comments below

Except that means it is still necessary to use the APP_DXKeeper_ form
when writing SQL queries/scripts which is a PITA and makes reading or
debugging queries/scripts more difficult.

+ Database field names are not required to be ADIF-compliant. I did not change the database field names because I didn't want to break existing filters or scripts, and because I didn't want to accept two different names for the same database field.

+ You can overcome this "difficulty" by copying

APP_DXKeeper_ 

to the Windows Clipboard when specifying a filter or script that will use these fields; then just type CTRL-V when needed.

     73,

             Dave, AA6YQ

 

 

+ 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

 

+ Note that the database field names did not change, but importing
and exporting ADIF and TDF has long been updated.

Except that means it is still necessary to use the APP_DXKeeper_ form
when writing SQL queries/scripts which is a PITA and makes reading or
debugging queries/scripts more difficult.

73,

... Joe, W4TV


On 2021-10-19 1:24 PM, Dave AA6YQ wrote:

+ AA6YQ comments below
There are also ADIF defined fields for EQSL_QSLSDATE EQSL_QSLRDATE EQSL_QSL_SENT, EQSL_QSL_RCVD, LOTW_QSLRDATE, LOTW_QSLSDATE, LOTW_QSL_SENT, and LOTW_QSL_RCVD where DXKeeper uses equivalent APP_DXKeeper_ tags. It would be nice if DXKeeper dropped the APP_DXKeeper_ (application defined) tag in favor of the equivalent standard tag.
+ That was done back when those fields were added to ADIF, Joe. See the "ADIF Field Name" column in the "Online QSL Items" section of
https://www.dxlabsuite.com/dxkeeper/Help/Items.htm
+ Note that the database field names did not change, but importing and exporting ADIF and TDF has long been updated.
73,
Dave, AA6YQ

+ AA6YQ comments below

There are also ADIF defined fields for EQSL_QSLSDATE EQSL_QSLRDATE EQSL_QSL_SENT, EQSL_QSL_RCVD, LOTW_QSLRDATE, LOTW_QSLSDATE, LOTW_QSL_SENT, and LOTW_QSL_RCVD where DXKeeper uses equivalent APP_DXKeeper_ tags. It would be nice if DXKeeper dropped the APP_DXKeeper_ (application defined) tag in favor of the equivalent standard tag.

+ That was done back when those fields were added to ADIF, Joe. See the "ADIF Field Name" column in the "Online QSL Items" section of

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

+ Note that the database field names did not change, but importing and exporting ADIF and TDF has long been updated.


73,

Dave, AA6YQ

+ AA6YQ comments below

This morning after startup I launched Launcher. It was running but hung. I had to quit the process and restart then it came right
up.

Normal startup on this machine is very fast -- think light speed.

+ The first thing the Launcher does is attempt to download a file showing what versions of DXLab applications are available. Perhaps
some component of your system decided to prevent that. See

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

73,

Dave, 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

I'm using the <log_qso> command in a macro.

As Dave has pointed out to you previously, to force LotW and eQSL
uploads on logging you must use <log_eqsl_lotw_qso>. To upload
only to LotW you must use <log_lotw_qso> and to upload only to
eQSL you must use <log_eqsl_qso>.

Using <log_qso> will not result in any uploading regardless of the
"upload" settings in the QSO Info box in Config -> Log.

73,

... Joe, W4TV


On 2021-10-19 5:16 AM, Gordon LaPoint wrote:

Joe,
  I'm using the <log_qso> command in a macro. I use the same script to log all digital mode contacts in WinWarbler.
Gordon  N1MGO
On 10/18/2021 14:54 PM, Joe Subich, W4TV wrote:

How are you logging?  Are you clicking the "Log" button in the QSO Info
panel or are you using a script command in one of your macros?

Are you using the same method for RTTY and PSK31/64/126?

Are your macros the same for Phone, CW, RTTY and Digital (PSK) or do
you have different sets?  Are you sure the correct set is being loaded
for each mode (group)?

73,

   ... Joe, W4TV


On 2021-10-18 2:31 PM, Gordon LaPoint wrote:

When I log a contact from winWarbler, in psk31 mode, DXKeeper does not upload to LOTW or eQSL, even though they are checked on the WinWarbler window, and in the config for WinWarbler.

If I log a RTTY contact from WinWarbler DXKeeper DOES upload to LOTW and eQSL.

What is the difference and where should I look?

Thanks,

Gordon - N1MGO

There are also ADIF defined fields for EQSL_QSLSDATE EQSL_QSLRDATE
EQSL_QSL_SENT, EQSL_QSL_RCVD, LOTW_QSLRDATE, LOTW_QSLSDATE,
LOTW_QSL_SENT, and LOTW_QSL_RCVD where DXKeeper uses equivalent
APP_DXKeeper_ tags. It would be nice if DXKeeper dropped the
APP_DXKeeper_ (application defined) tag in favor of the equivalent
standard tag.

73,

... Joe, W4TV

This morning after startup I launched Launcher. It was running but hung. I
had to quit the process and restart then it came right up.

Normal startup on this machine is very fast -- think light speed.


Pete Chamalian, W1RM
W1RM@...

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.

Gordon - N1MGO

Dave,

    Sorry, Thought I had changed the macro, I have changed it now.  I will test later today, or tomorrow, depending on time and finding signals on air.

Thanks!

Gordon - N1MGO

Joe,
  I'm using the <log_qso> command in a macro. I use the same script to log all digital mode contacts in WinWarbler.

Gordon  N1MGO

information overload, too busy...too much stuff, too many colors.....sometimes I thought I was going to get a seizure, from watching the screen

FYI,

Information overload can be managed by applying filters. On very busy bands, filtering out non-alerting callsignsns greatly reduces the number of callsigns displayed. I personally go one further on very busy bands and filter out any Callsigns that are non-Lotw users. Reducing the types of alerts displayed helps reduce the info overload. Not everyone wants to see every triggered alert type, prefix, grid, zones, states, etc.

As for the many colors, that is true, but easily altered for each alert type. There is no need to embrace the default colors. Each distinct color represent a distinct triggered alert per the needs you have enabled.

de Laurie VK3AMA

+ AA6YQ comments below

I don't so much care about WAS "Endorsement BINGO" but do think that DXKeeper/SpotCollector should support the basic awards including RTTY (rule 9e) in the same way it supports the other modes - Mixed (rule 9a), Phone (9b), CW (9c), Digital (9d), and SSTV (9p).

+ The "WAS Bands & Modes" panel on DXKeeper's Configuration window's Awards tab includes a RTTY option that is distinct from its Digital option. Are you saying that this RTTY option does not work correctly?

+ Remember that after changing your objectives on DXKeeper's Configuration window's Awards tab, you must direct DXKeeper to Recompute, and then direct SpotCollector to Recompute.

73,

Dave, AA6YQ

+ AA6YQ comments below

As soon as I log a qso on 60M, the display of DXV goes blank.
All entries in the progress field are empty.
Logging is done with N1MM-DXK gateway 1.2.1

Pressing 'GO' has no effect.

Switching to another DXCC restores the progress fields for that DXCC.
And when I enter the DXCC where I just logged a 60M qso in the callsign field of DXV, all is OK.

+ The N1MM-DXKeeper Gateway will send a callsign to DXView when it receives a  <lookupinfo> directive from N1MM; typing a callsign into N1MM's Main window and striking your keyboard's spacebar generates a <lookupinfo> directive. This works correctly on 60m.

      73,

             Dave, AA6YQ

     

 

+ AA6YQ comments below

BTW, <http://www.arrl.org/files/file/Awards/WAS_Rules_August_2021.pdf>
makes *no mention* of "QRP" WAS - nor does LotW (although "Power
Endorsement" appears on the paper ARRL WAS Application Form
<www.arrl.org/files/file/Awards/WAS_Application_Form_August_2021.pdf>).
How does an award (endorsement) not permitted by the rules appear on
the application?

+ Either a previous version of the WAS rules specified a QRP endorsement, or someone here asked for this capability. I don't have a problem with providing capabilities beyond an award's rules: DXLab has supported a PSK "extension" to the DXCC award for the past 20 years.

        73,

              Dave, AA6YQ