Date   

Re: Confirming 2X QSO

Mike Flowers
 

Means ‘two way QSO’.

 

- 73 and good DX de Mike, K6MKF, NCDXC Vice-President 2021-2022 - In pursuit of DXCELLENCE!

 

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Greg W0GAS
Sent: Sunday, May 08, 2022 07:25
To: DXLab@groups.io
Subject: [DXLab] Confirming 2X QSO

 

Why does the text say "Confirming a 2X QSO" when printing a card when only one QSO is listed?


Confirming 2X QSO

Greg W0GAS
 

Why does the text say "Confirming a 2X QSO" when printing a card when only one QSO is listed?


Re: DXKeeper Script questions

Joe Subich, W4TV
 

DXKeeper does not define a "DATA" mode. You will need to add it to
your "MODES.TXT" file in the DxKeeper\Databases directory. Since
you have (obviously) already added VARA as a user defined mode,
duplicate that line as DATA.

See: DXKeeper Help -> Configuration -> Defining or Eliminating Modes

73,

... Joe, W4TV

On 2022-05-08 6:37 AM, Gordon LaPoint wrote:
I'm trying a new mode VarAC.  The mode logs with the mode set to "VARA" . I add an exception to TQSL so it uploads to LOTW as DATA.  So far it all is good.  When I update from LOTW I get an error "No matching QSO in log" , expected because the modes don't match.
I wrote a script to change the mode to 'DATA' and put the "VARA" in user_defined_3 so I can find all the VARA contacts in the future when (If) the mode is added to the ADIF specs.
The script does not work.
Script:
// Find MODE VARA and change mode to DATA and put VARA in USER DEFINED #4 (VARA) //
Filter MODE='VARA'
Modify MODE 'DATA'
Modify APP_DXKeeper_USER_DEFINED_3 'VARA'
Log output:
// Find MODE VARA and change mode to DATA and put VARA in USER DEFINED #4 (VARA) //
Filter MODE='VARA'
   Selected 3 QSOs
Modify MODE 'DATA'
   'DATA' is not a valid value for the QSO item mode; no QSOs modified
   script terminated
What did I do wrong?
Thanks,
Gordon - N1MGO


DXKeeper Script questions

Gordon LaPoint N1MGO
 

I'm trying a new mode VarAC.  The mode logs with the mode set to "VARA" . I add an exception to TQSL so it uploads to LOTW as DATA.  So far it all is good.  When I update from LOTW I get an error "No matching QSO in log" , expected because the modes don't match.

I wrote a script to change the mode to 'DATA' and put the "VARA" in user_defined_3 so I can find all the VARA contacts in the future when (If) the mode is added to the ADIF specs.

The script does not work.

Script:

// Find MODE VARA and change mode to DATA and put VARA in USER DEFINED #4 (VARA) //
Filter MODE='VARA'
Modify MODE 'DATA'
Modify APP_DXKeeper_USER_DEFINED_3 'VARA'

Log output:

// Find MODE VARA and change mode to DATA and put VARA in USER DEFINED #4 (VARA) //
Filter MODE='VARA'
   Selected 3 QSOs

Modify MODE 'DATA'
   'DATA' is not a valid value for the QSO item mode; no QSOs modified

   script terminated

What did I do wrong?

Thanks,

Gordon - N1MGO


Re: LoTW Question

Dave AA6YQ
 

+ AA6YQ comments below
I am in a similar situation and followed the link  below.  On trying to acquire my DXCC account number I got pretty much the expression as noted:

https://lotw.arrl.org/lotwuser/awardaccount?awardaccountcmd=status&awg_id=DXCC&ac_acct=n&bingo=1#list

The only difference in the expression:  as_acct=1&bingo=1#list

This is from the URL that shows when I hover over "View Award Credit Matrix"

I don't believe my account can be number 1??
+ Yes, it can.

     73,

             Dave, AA6YQ


Re: LoTW Question

w0rx - David Willis
 

I am in a similar situation and followed the link  below.  On trying to acquire my DXCC account number I got pretty much the expression as noted:

https://lotw.arrl.org/lotwuser/awardaccount?awardaccountcmd=status&awg_id=DXCC&ac_acct=n&bingo=1#list

The only difference in the expression:  as_acct=1&bingo=1#list

This is from the URL that shows when I hover over "View Award Credit Matrix"

I don't believe my account can be number 1??

Or can it:

vy 73, Dave, w0rx

On 5/7/2022 12:06 AM, Dave AA6YQ wrote:

+ AA6YQ comments below
I am cleaning up my 26K+ database.  I ran all the options in Check Progress and cleaned up a lot of Q's.  Most of my band-mode slots are V's now, but I have about 400 QSOs from 1982 to 2017 which are tagged as LoTW Rcvd "S" which says that they are confirmed and I submitted them to LoTW for possible credit.    I am careful and do not submit QSOs which do not count.  Would it be the right thing to do to set them all of them back to "Y" or to "V"?

+ As a next step, I suggest that you invoke this function:

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

     73,

              Dave, AA6YQ

 



Re: Add Requested Fails to Add last QSO

w6de
 

Just a suggestion,  I never delete a QSO in my logbook, in DXKeeper I preface the call sign with an exclamation (!) point.  That removes the QSO from consideration for Awards, but leaves open the possibility of resurrecting the QSO should the QSO magically appear in the other stations log. 

 

For rare DX and some band and/or mode QSOs, I wait a while and send an email to the operator or QSL manager with all the details of the QSO and have him look in the log to see if there was a busted QSO.  I have had several rare needed QSOs resurrected using this approach.  The reason you wait to send the request later (as in a year or two later) is to see if the date/time/mode/frequency “slot” for that QSO was already granted to another operator.  My previous call sign was KE6ZE and I had a few busted QSOs where the operator copied C6ZE for a CW QSO ( _._  .  vs  _._. ).  There have been other cases where a QSL manager found other distortions of w6de and ke6ze.  And, of course they found some where I really wasn’t there.

 

73,

Dave, w6de

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of John Samuels K2CIB via groups.io
Sent: Saturday, May 07, 2022 04:38
To: DXLab@groups.io
Subject: Re: [DXLab] Add Requested Fails to Add last QSO

 

Dave, I did a submittal again today and did not see that problem.  It turns out that I was not in the VU4W log so I had to delete the contact anyway.  A LoTW "Add Requested" worked fine with a few new contacts.  Gremlins?


Re: 2022-05-07 20:00:05.615 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow

Dave AA6YQ
 

+ AA6YQ comments below

recently noticed that my spotcollector was sluggish, and today for awhile spots were CW only. I did some searching and noticed this error in the error log.
Not sure what I may have done to cause this. The first record start on 05:05 @ 03:10z, so there are thousands in the errorlog. Thoughts or suggestions?
Thanks Mike K9MK

<snip> Last 10 lines in the error log.


2022-05-07 20:00:05.601 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.602 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.605 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.607 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.608 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.610 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.611 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.612 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.614 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.615 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow

+ What version of SpotCollector are you running? You'll find this information in the Main window's title bar.

73,

Dave, AA6YQ


2022-05-07 20:00:05.615 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow

K9MK
 

Greetings to the Group, 
I recently noticed that my spotcollector was sluggish, and today for awhile spots were CW only.  I did some searching and noticed this error in the error log.  
Not sure what I may have done to cause this.  The first record start on 05:05 @ 03:10z, so there are thousands in the errorlog.  Thoughts or suggestions?
Thanks  Mike K9MK

 <snip> Last 10 lines in the error log.

2022-05-07 20:00:05.601 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.602 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.605 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.607 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.608 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.610 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.611 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.612 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.614 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
2022-05-07 20:00:05.615 > program error 6 in module SpotDatabaseModule.EnqueueSpot: Overflow
 
 


Re: DXView Translations Window

Dave AA6YQ
 

@ AA6YQ comments below

## I"ve always run DXView with the translation enabled as I stated before. Based on the paragraph above, if the translation window is not minimized, but in fact closed, then the Registry should show that window in a closed state and not minimized or visible.

@ You have jumped to an incorrect conclusion.

@ If the Translation panel's Enable box is checked and the Translation window has been closed, terminating and then restarting DXView will display the Translation window.

@ If the Translation panel's Enable box is checked and the Translation window has been minimized, terminating and then restarting DXView will not display the Translation window.

73,

Dave, AA6YQ


Re: SC disconnected from Launcher and other modules

Dave AA6YQ
 

+ AA6YQ comments below

It launches very slowly from Launcher but is never confirmed in Launcher and doesn’t work with Commander either. Radio is Flex 6600m.

+ As Joe W4TV pointed out, that's a classic sign of interference from another application, most likely your anti-malware. See

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

73,

Dave, AA6YQ


Re: Assemble Submission Problem

Dave AA6YQ
 

+ AA6yQ comments below

When I performed a LoTW submission, it included ten previously verified cards.

+ Now that you have resolved all the discrepancies between your log's DXCC status and your DXCC status as maintained by the ARRL, I suggest that you

1. view and then reset the DXCC LoTW submission

2. view and then reset the DXCC QSL card submission

3. generate a DXCC LoTW submission

4. generate a DXCC QSL card submission

+ Reverse the order of steps 3 and 4 if when there's a choice, you'd prefer to submit a QSL card rather than an LoTW confirmation.

+ None of the above steps require employing the "Modify QSOs" panel; they can all be accomplished from the "DXCC Submission" window.

73,

Dave, AA6YQ


Re: LoTW Question

K2CIB John
 

Thank you.  I did look at about ten records in LoTW and none of the "S" records had received credit.  I backed up the records concerned and modified those back to "Y" before creating a new submittal.  The db is looking good.  I was a programmer in a previous lifetime and used SQL extensively.


Assemble Submission Problem

K2CIB John
 

When I performed a LoTW submission, it included ten previously verified cards.  I can change the LoTW Received on those records from "S" to "Y", but it will not change the Planning Report or Create LoTW Sheets.  I will have to edit the sheets to remove those QSOs.  Small bug -and (.....AND QSL_Rcvd <> "V").


Re: LoTW Question

Dave AA6YQ
 

+ AA6YQ comments below

Thanks, Dave, good idea. I cleaned all of them up. But, still have about 400 "S"s to modify before I do the next submission. "Y" or "V" - They are all in LoTW but I can't tell which ones were used for credit or not.

+ A QSO whose QSL_Rcvd or LoTW_QSL_Rcvd items are set to 'S' is considered "confirmed".

+ If you invoked the "DXCC Compare" function and have eliminated all discrepancies, then none of those 400 QSOs with 'S' have been granted DXCC award credit -- so you should change them all to 'Y'.

+ I assume that you're familiar with using the "Advanced Sorts, Filters, and Modifiers" window's "Modify QSOs" panel to do this en masse; be sure to backup your log first!

73,

Dave, AA6YQ


Re: Flex6600

dxradio33
 

Perfect!

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, May 06, 2022 23:20
To: DXLab@groups.io
Subject: Re: [DXLab] Flex6600

# more AA6YQ comments below

I actually had two thoughts going when I responded to the post Dave. As I was typing the "YES" response it dawned on me that being able to return the first copy command slice to the original frequency and mode would also be beneficial. Hence the added remark. In thinking about it, this would be something that would functionally resemble swap slice B A or A B in addition to the copy commands. So in this scenario, to answer your question, it would take , for example, the frequency and mode of Slice A and swap it with frequency and mode of Slice C. Once accomplished, you would just initiate a swap back of Slice C to A if so desired. This , in my mind, would eliminate the need to copy Slice 'n' to Slice 'n' and just use swap instead.

+ Implementing a "swap" instead of a "copy" would eliminate the need to save VFO A's state (frequency, mode, passband, antenna selection, etc.), but I fear this would confuse users.

+ The objective is to make it easy to log a QSO with a station being worked via slice C, D, E, F, G, or H.

+ To work a station via one of those slices, that slice has to be "selected" in SmartSDR. Commander can detect that to be the case. Thus the objective can be accomplished by providing two new button-activated functions:

1. "Activate slice X", where X is the currently selected slice: saves VFO A's and VFO B's state, and copies slice X's state to both VFO A and VFO B. If the user wishes to operate split, he or she can click one of Commander's Up or Down buttons, or manually check the split box and adjust VFO B's frequency.

2. "Restore": restores VFO A's and VFO B's state as of the last time the "Activate slice X" function was invoked.

+ When controlling a Flex Signature transceiver, the Mode panel on Commander's Main window can be shortened to make room for the above two buttons.

+ Comments? Better ideas?

# I'm going to give this a shot - after I track down and correct an unrelated defect.

73,

Dave, AA6YQ


Re: SC disconnected from Launcher and other modules

Joe Subich, W4TV
 

Check for interference from your anti-malware software.

73,

... Joe, W4TV

On 2022-05-07 11:32 AM, Tyler Stewart via groups.io wrote:
It launches very slowly from Launcher but is never confirmed in Launcher and doesn’t work with Commander either.  Radio is Flex 6600m.
Ty K3MM


SC disconnected from Launcher and other modules

Tyler Stewart
 

It launches very slowly from Launcher but is never confirmed in Launcher and doesn’t work with Commander either.  Radio is Flex 6600m.

Ty K3MM 


Re: LoTW Question

K2CIB John
 

Thanks, Dave, good idea.  I cleaned all of them up.  But, still have about 400 "S"s to modify before I do the next submission.  "Y" or "V" - They are all in LoTW but I can't tell which ones were used for credit or not.


Re: LoTW Question

K2CIB John
 

I only have one like that - a credit for one band-mode combo for which I do not have a QSO in my log.  Otherwise, after a lot of scrubbing, they agree.  I found 155 QSL cards to submit but need to take care of the existing 400 "S"s first.  I waffle as to changing them to "Y" or "V".  They are in LoTW but I can't tell which ones were applied for credit or not.