Date   

Control-LoTW filter in DXK - add needed filter?

Jon Gefaell
 

When I heard Dave mention this at the start of his talk I was very excited. What I wonder is how to take that result and further refine it by asking 'Which of these QSOs fulfills an award goal if confirmed?". I suppose that's the same as 'needed'? 

I'm 18 short of my 200 endorsement, and I'm certain there are a few or more entities that I've worked but haven't received their QSL. I'd like to send them an email asking them to please check their log, and if that doesn't work, perhaps send cards.

Thank you.


Re: Log vs LoTW mismatch.

Jon Gefaell
 

Thank you, sir! I've moved past that hurdle now with your patient assistance. 

FWIW, in this case, I didn't have to correct the QSOs in the log, rather the county specified in the LoTW certificate. 

 


Re: QSOs Not sent To LOTW

Dave AA6YQ
 

+ AA6YQ comments below

How do I make a filter for LOTW QSOs not sent after making corrections to log?

+ You posted that same question earlier today. My response is here:

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

73,

Dave, AA6YQ


QSOs Not sent To LOTW

Jim K9TF <jim.gmforum@...>
 

How do I make a filter for LOTW QSOs not sent after making corrections to log?

 

Jim K9TF

 

Sent from K9TF Fixed station CPU

 

 


Re: Log vs LoTW mismatch.

Dave AA6YQ
 

+ AA6YQ comments below

I set the "Permit uploading of QSLs already uploaded to LoTW" and was able to upload that QSO successfully. Then updated the other log, and it made the expected adjustment. Wonderful!

There are 6 others that must be corrected. Each time, I find that the option has become unchecked, and I must go back to check it, upload the QSO in question, then repeat for each QSO. It seems setting this option is not 'sticky'?

+ That's intentional.

I suppose this is done to be protective

+ Exactly.

and I understand completely. I assume that I would need to filter the log display to contain the QSOs I intend to correct, then how would I re-upload those collectively at once?

+ On the bottom of the Main window's "Check Progress" tab, click the "Clear Select" button.

+ As you correct each QSO, set its Select item to 'Y' - it's available via the Auxiliary panel on the Main window's "Log QSOs" tab - and then click the Save button.

+ After all QSOs have been corrected, Click the Sel button in the Filter panel at the bottom of the Main window's "log QSOs" tab; this will filter the Log Page Display to contain only the QSOs whose Select items are set to 'Y'. Then on the Main window's QSL tab, click the "Add All" button to populate the QSL Queue with the QSOs you corrected. Finally, click "Upload to LoTW".

+ Note that there's also a command at the top of the Log Page Display's right-mouse menu that will set the selected QSO's Select item to 'Y'.

73,

Dave, AA6YQ


defect reports, requests for assistance, and suggested enhancments

Dave AA6YQ
 

When posting here, please use standard English to the best of your ability, optimizing for precision over entertainment value. To
increase the probability that I and other readers here will understand your post, please avoid slang and non-standard abbreviations.

Users for whom English is not their first language of course have additional flexibility.

73,

Dave, AA6YQ


Re: Log vs LoTW mismatch.

Jon Gefaell
 

Sorry, "ID-10T" is an old joke, I thought certainly you'd encountered it before. It means "IDIOT" ;) Sorry, just some gentle self-deprecation. 

I set the "Permit uploading of QSLs already uploaded to LoTW" and was able to upload that QSO successfully. Then updated the other log, and it made the expected adjustment. Wonderful

There are 6 others that must be corrected. Each time, I find that the option has become unchecked, and I must go back to check it, upload the QSO in question, then repeat for each QSO. It seems setting this option is not 'sticky'?

I suppose this is done to be protective, and I understand completely. I assume that I would need to filter the log display to contain the QSOs I intend to correct, then how would I re-upload those collectively at once?  


Re: Log won't open after upgrade

nk4l
 

Since I had made a Backup copy what I found easier to do was re-install the log and uploaded my backup copy then re-synk LOTW qsl's and a took 5 hours but it looks like everything is now back to normal, thanks Dave....
--
jose gonzalez


Re: Log vs LoTW mismatch.

Ben Coleman NJ8J
 

On 6/11/2021 6:03 PM, Dave AA6YQ wrote:
I threw an ID-10T error.
+ What's an ID-10T error? Which application reported it?
That's a wetware error, not a software error.

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


Re: Log vs LoTW mismatch.

Dave AA6YQ
 

+ AA6YQ comments below

Sometimes...SMH

So, I realized I need to do a upload to LoTW operation, not a "update FROM LoTW" on the other station's log.

+ Correct!

I just did this and got a report that said the location information would be updated, and to be certain this is what I wanted, then that it aborted because it's a duplicate.

+ That's TQSL protecting the LoTW Server from users who lazily resubmit all of their logged QSOs each time they log a few more.

What do I do to let the process know I want it to proceed to correct the QSO?

+ On the "QSL Configuration" window's LoTW tab, check the "Permit uploading of QSOs already uploaded to LoTW" box.

73,

Dave. AA6YQ


Re: Waterfall Bandmap

Dave AA6YQ
 

Dave .. et al. can I assume this is the reason I can not currently find the the place you check to turn on the "Waterfall Bandmap" ? Not a big problem except I was going nuts looking for it.

+ No, you just have to follow the instructions in Note 1 of the Commander 15.1.6 release note:

Step-by-step instructions for enabling interoperation with the Waterfall Bandmap application are available via https://www.dxlabsuite.com/dxlabwiki/WaterfallBandmap

73,

Dave, AA6YQ


Re: Log vs LoTW mismatch.

Jon Gefaell
 

Sometimes...SMH

So, I realized I need to do a upload to LoTW operation, not a "update FROM LoTW" on the other station's log.

I just did this and got a report that said the location information would be updated, and to be certain this is what I wanted, then that it aborted because it's a duplicate. What do I do to let the process know I want it to proceed to correct the QSO?

Thanks always for your kind patience! 


On Fri, Jun 11, 2021 at 02:52 PM, Jon Gefaell wrote:

performed an 'update to LoTW' operation


Re: Log vs LoTW mismatch.

Dave AA6YQ
 

+ AA6YQ comments belopw.

I threw an ID-10T error.

+ What's an ID-10T error? Which application reported it?

The log I'm managine for another station, I put the wrong station location information in the TQSL settings for the new certificate.

+ The only location information associated with a Callsign Certificate is the callsign's DXCC entity - as shown in this TQSL screenshot:

https://lotw.arrl.org/lotw-help/data/uploads/certreqcopy.bmp

I have been testing with just a literal handful of QSOs to make sure any PEBKAC issues don't cause a big problem when all QSOs are uploaded, and I'm glad I did.

So, the QSL update from *my* station came back with a mismatch for the county.

+ Is that because your log contains a QSO with the station you're managing?

I changed that in TQSL on the managed station's log, and performed an 'update to LoTW' operation. The updates on both ends said "1 log entry updated". I gave that about 5 minutes, and did the same operation on my station, hoping it would change to the correct county. It has not. I just did it again, 20 minutes later and the grid didn't change to the expected, corrected in TQSL result.

+ If what you did was specify the wrong County in the Station Location used to submit a QSO to LOTW, you must correct that Station Location, and then resubmit the QSO to LoTW with the corrected Station Location.

+ You can determine how long it will likely take for LoTW to process a newly submitted QSO by clicking the "Check LoTW Queue" button on the QSL tab of DXKeeper's Main window with the "QSL Via" panel set to LoTW. At top of the current hour, it was about a minute.

73,

Dave, AA6YQ


Re: Waterfall Bandmap

Jim
 

Dave .. et al.    can I assume this is the reason I can not currently find the the place you check to turn on the "Waterfall Bandmap" ?  Not a big problem except I was going nuts looking for it.  

Jim K3YBN


Log vs LoTW mismatch.

Jon Gefaell
 

I threw an ID-10T error. The log I'm managine for another station, I put the wrong station location information in the TQSL settings for the new certificate. I have been testing with just a literal handful of QSOs to make sure any PEBKAC issues don't cause a big problem when all QSOs are uploaded, and I'm glad I did.

So, the QSL update from *my* station came back with a mismatch for the county. I changed that in TQSL on the managed station's log, and performed an 'update to LoTW' operation. The updates on both ends said "1 log entry updated". I gave that about 5 minutes, and did the same operation on my station, hoping it would change to the correct county. It has not. I just did it again, 20 minutes later and the grid didn't change to the expected, corrected in TQSL result.

Should I be more patient for LoTW, or am I not doing the right thing?

 


Waterfall Bandmap

Dave AA6YQ
 

As stated in the release note for Commander 15.1.6, the current interoperation with the Waterfall Bandmap is a work in progress. It's author, Steve N2IC, is providing radio support to wildfire fighting teams in Arizona; his responsibilities have not left him much time to collaborate with me. Steve's work in Arizona is far more important than anything we do here, so please be patient.

    73,

             Dave, AA6YQ

    


Commander 15.1.6 is available

Dave AA6YQ
 

If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions

before installing or upgrading to Commander 15.1.6


This release

- only displays a warning message when controlling a Kenwood or Yeasu transceiver that requires RTS set to 'On' when directly
connected and no data has been received from the transceiver after 5 seconds if the Primary CAT Port's RTS selector is set to 'Off'
(tnx to Saad N5FF, Joe W4TV, and Bill G4WJS))

- correctly reports Network Service UDP address and port errors (tnx to Jon K6OJ)

- when selecting an Icom transceiver that only supports a single data sub-mode, automatically selects that data mode (tnx to Steve
NS4P)

- interoperates with Steve N2IC's "Waterfall Bandmap" application; please see note 1 below (tnx to Steve N2IC and Dick K6PBF)

- when an Elecraft K3, K3S, KX3, or KX2 is first selected, directs it to report its firmware versions and records them to the
errorlog.txt file if error logging is enabled (tnx to Mike K6MKF)

- supports the Icom IC-275, IC-475, and IC-575 (tnx to Larry W1SIM)

- enables tracking of the Primary transceiver's frequency and mode on a TenTec Argonaut V, Argonaut VI, Eagle, Jupiter, or Omni VII
connected to the Secondary CAT port (tnx to Howard K7JNX)

- updates the Configuration.htm, NetworkService.htm, and TXMeter.htm documentation files


Notes

1. Step-by-step instructions for enabling interoperation with the Waterfall Bandmap application are available via
https://www.dxlabsuite.com/dxlabwiki/WaterfallBandmap

- this is a work-in-progress, not a completed capability; tighter interoperation is planned

- the Waterfall Bandmap application can only display the most recent active callsign on a frequency

- known defect: the Waterfall Bandmap application sometimes erroneously displays two or more callsigns on top of each other, making
the callsigns unreadable


2. In this version, the Secondary CAT Port's "CAT Protocol" selector can be set to "FlexRadio PGXL", but this is not yet working
correctly with a FlexRadio PGXL amplifier.


3. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe"

- 0 of 68 antivirus scanners accessible via Virus Total detected malware <https://www.virustotal.com/gui/home/upload>

- 0 of 15 antivirus scanners accessible via Jotti detected malware <https://virusscan.jotti.org/>

- submitted for online analysis by Microsoft Windows Defender: no malware detected


4. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking


5. After upgrading, to revert to the previous version of Commander, see
http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion



Commander 15.1.6 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ


GridTracker

Dave AA6YQ
 

Has anyone who experienced "Invalid request" errors after invoking DXKeeper's "Sync LoTW QSOs" or "Sync LoTW QSLs" function with
Grid Tracker running continued to experience these errors after no longer running GridTracker while DXKeeper is running?

73,

Dave, AA6YQ


Re: Filter not Sent LOTW QSOs

Dave AA6YQ
 

How do I make a filter for LOTW QSOs not sent after making corrections to log?

+ Use the SQL expression

APP_DXKEEPER_LOTW_QSL_SENT <> 'Y'

+ Documentation of every item stored with each QSO is here:

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

+ Documentation for how to filter the Log Page Display using SQL expressions is here:

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

+ If you configured DXKeeper to interact with LoTW as documented here:

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

+ the to submit QSOs to LoTW that have not yet been sent, do the following on the Main window's QSL tab:

1. set the "QSL Via" panel to LoTW

2. click the "Add Requested" button

3. click the "Upload to LoTW" button

+ See

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

73,

Dave, AA6YQ


Filter not Sent LOTW QSOs

Jim K9TF <jim.gmforum@...>
 

How do I make a filter for LOTW QSOs not sent after making corrections to log?


--
Jim K9TF

2761 - 2780 of 204605