+ AA6YQ comments below

Commander won't respond no matter what I try

+ What does "Commander won't respond" mean, exactly. Does it's Main window appear on-screen after you direct the Launcher to start it? Is there an errorlog.txt file in your Commander folder?

+ Have you reviewed the Icom configuration steps in

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

+ and

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

?

     73,

           Dave, AA6YQ

Hello all..Can some one tell me which header I need to add to my
spotcollector window to monitor US state names with the
US calls that are posted with FT8?? Is this even possible?? Does
spotcollector check callsigns against a database to fill in the
Proper state??? Any help is appreciated.
73 Ted VE3SS

Hello all….Can some one tell me which header I need to add to my spotcollector window to monitor US state names with the

US calls that are posted with FT8?? Is this even possible?? Does spotcollector check callsigns against a database to fill in the

Proper state??? Any help is appreciated.

73 Ted VE3SS

+ AA6YQ comments below

Well it was worth a shot.  In any event, you have a work around and I am sure at some point this will be resolved.

+ DXKeeper does not autonomously change the locations of the windows it displays - information that is stored in the WIndows Registry. Either you inadvertently moved the LoTW download progress display window, or a latent defect in Windows caused the Registry entry to be modified. If the latter, any resolution would have to come from Microsoft.

+ The DXLab Launcher can save and restore a DXLab application's settings from the Windows Registry to a file (in a Workspace), and restore those settings from a file (in a Workspace), but it doesn't modify any of those settings in the process.

       73,

             Dave, AA6YQ

Hello:
Please forward this info to the maintainer of the Primary Administrative Subdivision table for DXKeeper.  Provinces Mayabeque and Artemisa are missing and La Habana dropped for Cuba.  Station example: CO3LY.
Thank you and 73,
Neil W3ZQI
*Mayabeque Province* is one of two new provinces created from the former La Habana Province ( https://en.wikipedia.org/wiki/La_Habana_Province ) , whose creation was approved by the Cuban National Assembly ( https://en.wikipedia.org/wiki/Cuban_National_Assembly ) on August 1, 2010, the other being *Artemisa* Province ( https://en.wikipedia.org/wiki/Artemisa_Province ). [3] ( https://en.wikipedia.org/wiki/Mayabeque_Province#cite_note-3 ) [4] ( https://en.wikipedia.org/wiki/Mayabeque_Province#cite_note-4 ) The new provinces came in to existence on January 1, 2011. https://en.wikipedia.org/wiki/Mayabeque_Province

+ Compare that to the LoTW confirmation rate for your QSOs made in 2022: filter DXKeeper's Log Page Display to contain only QSOs made in 2022, and then click the "QSL Stats" button along the bottom of the Main window's "Check Progress" tab.

      73,

             Dave, AA6YQ

Thanks, I will use the above from now on.

N8XI QSL Statistics Report 22-Dec-2022

Filter: QSO_Begin BETWEEN #2022-01-01 # and #2022-12-24#

            LotW upld   LotW cfm  LotW cfm%

      Phone   54         18        33%   

         CW   1424        671        47%   

       DIGI    296        217        73%   

        PSK      0          0          0              

       160M      4          2        50%   

        80M    165         90        55%   

        40M    945        446        47%   

        30M     18         10        56%   

        20M    556        305        55%   

        17M      6          4        67%   

        15M     54         32        59%   

        12M      2          2       100%   

        10M      5          2        40%   

         6M     19         13        68%   

         2M      0          0          0              

      Total   1774        906        51%   

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

I found one SATNAME in error. The error was it was in lower case, but
didn't always display that way, only in the main window. So it was
hard to find.

I don't know that DXKeeper values are case sensitive - at least I've
never found that to be the case when using  SQL filtering.

When I get back I will try filtering , and searching through the sat
data again. It would be a lot easier if the QSO in error was saved
somewhere in an error file.

The built-in "Broke" filter (Filter panel at the bottom of the main
page) should fine any QSO that (from the Help file):

specify a Satellite name but to not specify a Propagation mode of SAT

You could also write your own filter for valid Satellite Names:
   SAT_NAME in (list of valid satellite names)

Note: if you are using satellites not defined in "DefaultSatellites.txt"
in DXKeeper's Databases folder, be sure to create your own
"Satellites.txt" file in the databases folder containing the new
satellite names (See DXKeeper/Help/Configuration.htm).

73,

   ... Joe, W4TV


On 2022-12-22 10:13 AM, Jeff KB2M wrote:

I did that, and saw nothing wrong. All the sat contacts show 'SAT' . I did find another error earlier, when going through several hundred sat contacts I was holding till ARRL added the two new sats to LoTW. I found one SATNAME in error. The error was it was in lower case, but didn't always display that way, only in the main window. So it was hard to find.

  FYI.  These errors are from me typing in all the sat info manually as the SatPC32ISS version doesn't connect to LoTW. I have a doctors appointment. When I get back I will try filtering , and searching through the sat data again. It would be a lot easier if the QSO in error was saved somewhere in an error file. I'm also CCing this to  Erich to see if he is willing to add the connect to DXLab function to SatPC32ISS..

73 Jeff kb2m


On 12/22/2022 9:42 AM, Joe Subich, W4TV wrote:

Try this filter:

  SAT_NAME<>'' and Prop_Mode <> 'SAT'

Or you can enable the Propagation panel and step through each QSO
until you find the offending one.

73,

   ... Joe, W4TV

On 2022-12-22 9:30 AM, Jeff KB2M wrote:

It looks like my screen capture was stripped off . When I do a QSL , Add Requested  I get  a message.....

  'at least one QSO was not added to the QSL Queue because it specifies a satellite name item but its propagation mode item is not set to SAT'




On 12/22/2022 9:09 AM, Jeff KB2M wrote:

How do I find this guy? I went through my contacts since this appeared and can't find any issue. Is there some way to list the callsign of the offending contact so I can locate and correct it?

Thanks

73 Jeff kb2m