Date   

Re: No matching QSO in log-Finding the Mismatch

Dave AA6YQ
 

+ AA6YQ comments below

Dave, as always, thank you for providing a detailed and comprehensive explanation. The next time I get a "No Matching QSO in Log" I'll be better prepared to research and deal with it.

+ There are two ways to cause a "No Matching QSO in Log" report from the "Sync LoTW QSOs" or "Sync LoTW QSLs" operations:

1. Forgetfulness:

1a. Log a QSO,

1b. Submit the QSO it to LoTW

1c. Subsequently modify the logged QSO's callsign, date, time, band, mode, submode, or station callsign

1d. Fail to resubmit the modified QSO to LoTW


2. Multiple inconsistent sources: submit QSOs to LoTW from more than one application that are inconsistent with respect to time (e.g. "to the second" vs "to the minute")


+ To prevent forgetfulness, check the "Prompt on change to logged QSO already uploaded to eQSL.cc and/or LoTW" box on the "QSL Configuration" window's General tab.

+ To prevent trouble from multiple inconsistent sources, only submit QSOs to eQSL and LoTW from DXKeeper.

73,

Dave, AA6YQ


Re: Question about SpotCollector performance [8.9.2]

Dave AA6YQ
 

+ AA6YQ comments below

As I’m going through the optimization checklist, the webpage “Addictive Tips” on how to set the “affinity to an application” doesn’t cover Windows 10.

In Windows 10, to check or change the affinity setting, go to Task Manager, then Details. Right Click on SpotCollector and then “Set Affinity. All eight cores were already selected on my computer. In that same open window you can select the Priority setting.

+ Thanks! I've updated

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

+ accordingly.

73,

Dave, AA6YQ


Re: Question about SpotCollector performance [8.9.2]

Dave AA6YQ
 

+ AA6YQ comments below
As I’m going through the optimization checklist, the webpage “Addictive Tips” on how to set the “affinity to an application” doesn’t cover Windows 10.

In Windows 10, to check or change the affinity setting, go to Task Manager, then Details. Right Click on SpotCollector and then “Set Affinity. All eight cores were already selected on my computer. In that same open window you can select the Priority setting.

In “Changing Mouse Cursor Theft, Windows 10 is again different than previous versions. To get to this setting, Open the Run window, (Windows key + R) and type SystemPropertiesPerformance.exe. Under “Visual Effects” select “Adjust for best performance” and click “Apply”.

+ The simpler instructions in

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

+ work correctly on my Windows 10 system; do they not work on yours?

73,

Dave, AA6YQ


Re: No matching QSO in log-Finding the Mismatch

Jim McPhee
 

Dave, as always, thank you for providing a detailed and comprehensive explanation. The next time I get a "No Matching QSO in Log" I'll be better prepared to research and deal with it.

73,
--
Jim McPhee
Placitas, NM
W5ABA


Re: Skimmer-to-Commander with Commander - strange behaviour

Dave AA6YQ
 

I was referring to the email I sent to AA6YQ(at)ambersoft.com

+ To minimize delays, I frequently read and respond to messages posted to this group via

https://groups.io/g/DXLab/messages

+ before heading to my shack, where I can read email sent to AA6YQ(at)ambersoft.com

73,

Dave, AA6YQ


Re: Incorrect ITU country prefix logged

Dave AA6YQ
 

+ AA6YQ comments below

I did not need to disable automatic uploading, as I don't use it. I always upload to LOTW manually.

Using the Capture window, I logged a QSO with MI0HOZ in the new Test database. It automatically filled in "GI" in the DXCC field, which is the correct value for Northern Ireland.

Note that when I logged the QSO that prompted my original posting on 10/23/2021, I had used the main Log QSOs tab instead of the Capture window. So I created a second test database called Test2 and repeated the experiment, this time logging the QSO from the main Log QSOs tab. The result was the same: "GI" was automatically filled in the DXCC field.

+ Thanks, Steve. If you find a way to replicate the earlier behavior or if it recurs, please let me know.

73,

Dave, AA6YQ


Re: No matching QSO in log-Finding the Mismatch

Dave AA6YQ
 

+ AA6YQ comments below

I am trying to resolve a QSO that was reported in a "No matching QSO in log" message. Following the instructions at "https://www.dxlabsuite.com/dxlabwiki/LoTWNoMatchingQSOInLog", I get to the "Finding the Mismatch" section. I have opened the "LoTW_UpdateSingle_ADI.txt" file as instructed. However, the text displayed only matches the top part of the example in the Wiki. The lower section, outlined in red in the example, does not appear.

+ That means the QSO from whose Log Page Display entry you initiated an "Update from LoTW" operation is not present in LoTW. In the "LoTW_UpdateSingle_ADI.txt" file, the line just above the <eoh> is

<APP_LoTW_NUMREC:1>0

+ correct? That means "no records found".


The instructions under the example reads:
"The section outline in red contains information being reported by LoTW. The 7 ADIF fields underlined in green contain information that should exactly match information in the logged QSO. " and goes on to say "Carefully compare these ADIF fields in the LoTW_UpdateSingle_ADI.txt file with the information in the logged QSO to identify the discrepancy."

+ The instructions assume that the QSO for which you invoked "Update from LoTW" was submitted to LoTW, and accepted by LoTW. A QSO that has not been submitted to and accepted by LoTW can't be the cause of a "No Matching QSO in Log" report.

73,

Dave, AA6YQ


Re: Time out on Logging

Dave AA6YQ
 

+ AA6YQ comments below

Tried the Safe Boot process a couple of times, and had problems with that.

1. Commander running under Safe Boot would not recognize my COM port 8 as installed by my IC-7600. Device manager said it was there and working.
2. WSJT-X running under Safe Boot would not recognize my Audio Input Device as installed by my IC-7600. Device Manager said it was there and working.
3. When starting all the DXLab Suite applications (from Launcher) under Safe Boot, they took much longer to start than when running Win10 normally (ie, not under Safe Boot).

+ #3 is unexpected. Did you boot Windows into "Safe mode", or into "Safe mode with Networking"?

73,

Dave, AA6YQ


Re: Question about SpotCollector performance [8.9.2]

Jim - KR9U
 

As I’m going through the optimization checklist, the webpage “Addictive Tips” on how to set the “affinity to an application” doesn’t cover Windows 10. 

In Windows 10, to check or change the affinity setting, go to Task Manager, then Details.  Right Click on SpotCollector and then “Set Affinity.  All eight cores were already selected on my computer.  In that same open window you can select the Priority setting.   

 

In “Changing Mouse Cursor Theft, Windows 10 is again different than previous versions. To get to this setting, Open the Run window, (Windows key + R) and type SystemPropertiesPerformance.exe.   Under “Visual Effects” select “Adjust for best performance” and click “Apply”.

 

Jim – KR9U

 


Re: Skimmer-to-Commander with Commander - strange behaviour

Wolf, DK1FW
 


I was referring to the email I sent to AA6YQ(at)ambersoft.com


Am 01.11.2021 um 18:06 schrieb Dave AA6YQ:

+ AA6YQ commentsb elow
I have followed your recommendation by sending the more detailed test description and results
to both yourself and Dick, W3OA. You could see that you were both addressees of my e-mail.

+ I read your message here:

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

+ As you can see, your other email destinations are not shown.

       73,

             Dave, AA6YQ



Re: Skimmer-to-Commander with Commander - strange behaviour

Dave AA6YQ
 

+ AA6YQ commentsb elow
I have followed your recommendation by sending the more detailed test description and results
to both yourself and Dick, W3OA. You could see that you were both addressees of my e-mail.

+ I read your message here:

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

+ As you can see, your other email destinations are not shown.

       73,

             Dave, AA6YQ


Re: Skimmer-to-Commander with Commander - strange behaviour

Wolf, DK1FW
 

Dave,

I have followed your recommendation by sending the more detailed test description and results
to both yourself and Dick, W3OA. You could see that you were both addressees of my e-mail.

Of course I do not know, which application holds the root-cause of the problem.

For the time being I am doing fine with Skimmer-to-Commander and Commander 14.6.2. I could probably live with that to the end of my days in ham-radio.

73 de Wolf, DK1FW


Am 01.11.2021 um 16:04 schrieb Dave AA6YQ:

+ AA6YQ comments below
unfortunately I did not identify, which version of Commander I was using when I reported the problem in interoperation of my FT5000 with CW Skimmer/Skimmer--to-Commander and Commander last year. It probably was Commander 14.7.1.

So I have done some (hopefully exhaustive) testing with Commander 12.1.8 (used by W3OA when testing his program), Commander 14.5.8 (oldest version still on my PC), Commander 14.6.2 and Commander 14.6.5.
Modes of relevance are CW-Split (find a listening frequency in a CW pile-up) and RTTY-Split (find a free spots in an RTTY pile-up).
I have put the details of the test into an EXCEL file, which I will send to AA6YQ(at)ambersoft.com and also to Dick, W3OA.

Summary:
Commander 12.1.8 / 14.5.8 and 14.6.2 and Skimmer-to-Commander show identical behaviour:

Whichever mode the FT5000 was set to before switching to CW-Split or RTTY-Split
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode - FINE

When the FT-5000 is in PKT-Split  (e.g for WSJT or PSK) regardless of the previously used mode
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and changes VFO-A and VFO-B mode to USB.
As it makes no sense to use CW Skimmer/Skimmer-to-Commander in PSK or WSJT  this misbehaviour is irrelevant..

The problem comes up when Skimmer-to-Commander is used with Commander 14.6.5:

When the FT5000 is commanded from SSB to CW-Split and PKT-Split or RTTY-Split have NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode

When the FT5000 is commanded from SSB or CW to RTTY-Split and PKT-Split has NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency without changing VFO-B mode

When the FT5000 is commanded from RTTY-Split  to CW-Split and PKT-Split has NOT been used before
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and VFO-B mode is changed from CW to RTTY

When the FT5000 is commanded to CW-Split or RTTY-Split and PKT-Split has been used before at any time
Clicking the Skimmer waterfall QSYs VFO-B to the click-frequency and VFO-B mode is changed CW/RTTY to USB

So reverting to Commander 14.6.2, which more than satifies my needs, will solve my problem.

Hope this helps.

+ Wolf, I investigated this issue when you first raised it two years ago. My recommendation then was

"It's clear from your description above that incorrect commands are being sent to the radio while "CW Skimmer to Commander" is running. I do not have the source code to this application. Thus I suggest that you report the above behavior to its author Dick W3OA; I will be happy to assist Dick if he needs help."

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

+ Your recitation above does not change this recommendation.

      73,

              Dave, AA6YQ

 



Re: Incorrect ITU country prefix logged

Steve, N5EP
 

Dave, sorry it took me a few days to run your experiment. 

I did not need to disable automatic uploading, as I don't use it.  I always upload to LOTW manually.

Using the Capture window, I logged a QSO with MI0HOZ in the new Test database.  It automatically filled in "GI" in the DXCC field, which is the correct value for Northern Ireland. 

Note that when I logged the QSO that prompted my original posting on 10/23/2021, I had used the main Log QSOs tab instead of the Capture window.  So I created a second test database called Test2 and repeated the experiment, this time logging the QSO from the main Log QSOs tab.  The result was the same:  "GI" was automatically filled in the DXCC field.

Steve, N5EP


No matching QSO in log-Finding the Mismatch

Jim McPhee
 

I am trying to resolve a QSO that was reported in a "No matching QSO in log" message. Following the instructions at "https://www.dxlabsuite.com/dxlabwiki/LoTWNoMatchingQSOInLog", I get to the "Finding the Mismatch" section. I have opened the "LoTW_UpdateSingle_ADI.txt" file as instructed. However, the text displayed only matches the top part of the example in the Wiki. The lower section, outlined in red in the example, does not appear. The instructions under the example reads:
"The section outline in red contains information being reported by LoTW. The 7 ADIF fields underlined in green contain information that should exactly match information in the logged QSO. " and goes on to say "Carefully compare these ADIF fields in the LoTW_UpdateSingle_ADI.txt file with the information in the logged QSO to identify the discrepancy."
Although the discrepancy appears to be a time difference, it would be valuable to be able to see the details referenced in this section. Is there an alternative way to see it?

Thanks,

Jim McPhee
Placitas, NM
W5ABA


Re: WARNING about Windows 11

Kurt Cathcart
 

If you go into the Bitlocker console, there is an option to back up the key.


-Kurt, KR2C

On 11/1/2021 9:46 AM, g4wjs wrote:
On 01/11/2021 12:45, Gilbert Baron W0MN wrote:

Microsoft has decided to automatically turn on data encryption in Windows! 11. Not sure if on home but I read an article by the  reporter on Minneapolis paper that it did on his home edition. THEY DO NOT TELL YOU WHERE THE KEY IS OR WHAT IT IS. If your system fails you have just lost your data. Go to settings and TURN IT OFF

.

Outlook LT Gil W0MN

Gil,

that may be an over-reaction. BitLocker has been around since Windows 8 and is a good thing if you want to protect your personal data. I believe MS announced some time ago that it would be enabled by default for Windows 11. What matters is where the decryption and recovery keys are stored. If I understand correctly, if you use a microsoft account (MSA) to log in to your PC then the keys are stored there, but if you PC has an enabled TPM chip then they are stored there thus allowing you to operate without being tied to a MSA. I have not researched this in depth so may be slight off on the details.

Is there a Windows 11 Home edition? Home editions of 8, 8.1, and 10 did not have BitLocker available by default.


--
73

Bill

G4WJS.


Re: Time out on Logging

Rod Greene
 

FYI,

Tried the Safe Boot process a couple of times, and had problems with that.

1. Commander running under Safe Boot would not recognize my COM port 8 as installed by my IC-7600. Device manager said it was there and working.
2. WSJT-X running under Safe Boot would not recognize my Audio Input Device as installed by my IC-7600. Device Manager said it was there and working.
3. When starting all the DXLab Suite applications (from Launcher) under Safe Boot, they took much longer to start than when running Win10 normally (ie, not under Safe Boot). I did not use a stop watch to time them but it appeared it took at least twice as long to start the applications under Safe Boot. Normal start times under normal start up are in the range of seconds (less than a minute) for all of them with SC being the longest.

I am running Win10 Home 21H1 version 19043.1288 (all current updates). I followed the directions for Safe Boot as explained in your link below.

Since the applications would not recognize my com or audio connections I was not able to perform any application tests under Safe Boot.

Thanks for your help and support! I will continue to experiment with my settings and report anything significant.

73, Rod/w7zrc



On Friday, October 29, 2021, 03:06:52 PM MDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below
Thanks! This started several months ago, but I can't remember exactly when. It happened very minimally at first but has gotten worse to the point now it's happening over 50% of the time. Your questions below prompted me to do some checking with Task Manager to see what else was running on my desktop. I did have a couple of other applications running, so I stopped them and then did some tests with only DXLabs Suite and WSJT-X running. Still have the same error message so maybe something else is consuming CPU resources or other. I'll run some more tests while looking at the CPU performance (if I can remember where to find it). BTW, I don't run any virus protection software other than what is built in to Win 10. CPU is an older i5 with 8gB of RAM and a 256gB SSD. Performance has not been a problem even tho this is an older system.

+ Slowing of the communication among DXLab applications could the result of interference from an anti-malware application. See

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

      73,

            Dave, AA6YQ


Re: DXKeeper Filter and Batch Modify ?

w2eck
 

Dave & Mike
Thanks much for replies and instruction. Got the sort an update done successfully.

73 Paul w2eck


Re: Spotcollector 8.9.2 and Telnet Clusters

Dave AA6YQ
 

+ AA6YQ comments below
It looks that the problem is somehow related to the way how SC is handling spot sources from the own pc (localhost or 127.0.0.1 with port 7300) and / or another source from the local network. I don't find any other explanation why rbn.dr4w.de is displayed in SC's telnet cluster all the time but not in SC's database window, and this is depending on enabling either localhost:7300 or 192.168.2.133 (internal ip-address): 7373 or not.

+ So that I can see what's going on, please do the following:


1. on the Configuration window's General tab, check the "Log debugging info" box

2. wait until 5 new spots from  rbn.dr4w.de have appeared in SpotCollector's "spot source" window


3. on the Configuration window's General tab, uncheck the "Log debugging info" box

4. attach the errorlog.txt file from your SpotCollector folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

         73,

               Dave, AA6YQ


Re: WARNING about Windows 11

Peter Laws / N5UWY
 

On Mon, Nov 1, 2021 at 10:38 AM Peter Laws / N5UWY via groups.io
<plaws0@...> wrote:


Hopefully, Bitlocker works as smoothly/silently as Apples unbranded
disk encryption. Good luck! :-D
Actually, it's apparently branded "FileVault". ¯\_(ツ)_/¯

--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Spotcollector 8.9.2 and Telnet Clusters

dl8le
 

Hello Dave,

thank you for your immediate reply.

Your configuration comments are not applicable here (nothing is checked in the special callsign tab and the spots are not older than the standard 15 min you have set as default value.

It looks that the problem is somehow related to the way how SC is handling spot sources from the own pc (localhost or 127.0.0.1 with port 7300) and / or another source from the local network. I don't find any other explanation why rbn.dr4w.de is displayed in SC's telnet cluster all the time but not in SC's database window, and this is depending on enabling either localhost:7300 or 192.168.2.133 (internal ip-address): 7373 or not.

Anyway, I have contacted the author of sparksdr2dxc via the SparkSDR group and hope that there is some explanation for this strange behaviour (Info: I am using SparkSDR for my Hermes Lite II for skimming purposes).

73

Juergen, DL8LE

4561 - 4580 of 208691