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

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

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

+ AA6YQ comments below

Good afternoon, The following occurs here. I work with the yaesu FTdx101MP and when I work with commander and I set my filter in Commander to narrow it automatically goes to 450Hz Can I set the filter narow myself or is it always 450Hz?

+ Yaesu's CAT documentation for the NA (NARROW) command does not describe its actual function. I suspect that it controls the "IF NOTCH WIDTH" mentioned on page 99 of the Operator's manual, but that's a guess. If all else fails, contact Yaesu support.

73,

Dave, AA6YQ

Have you thought about a good, powered USB hub, and if needing RS232 connections, good USB adapters?     This will work,  but don't use a cheap hub nor cheap adapters.

Neil, KN3ILZ

Thanks all. Fresh install is running ok now.  Only issue left is loss of four com ports using new PC. I need to learn how to create some Com ports.

Jim K7EG

+ AA6YQ comments below

Yes Dave.  Brought over obsolete radio.txt

+ By that, I assume you mean that when you didn't see K3S in Commander's Radio Model selector, you incorrectly assumed you had an obsolete Radios.txt file, and "brought over" one that really was obsolete.

I will try to find current list. 

+ You'll find it here:

http://www.dxlabsuite.com/commander/Radios.txt

When I reinstalled DXL Suites, I thought any file like that would get an update. 

+ Directing the Launcher to install Commander provisions it with an up-to-date Radios.txt file. If that were not the case, there would be lots of posts here from new DXLab users unable to find a recent radio in Commander's Model selector.

I will search web for current file.  Wonder how many other brought over files are obsolete? 

+ None reported in years.

May need to delete it all and start over

+ That would be an exceptionally bad idea.

       73,

               Dave, AA6YQ

+ AA6YQ comments below

I just performed and upgrade from DXLab Launcher and one of them was a log update now my log won't open I get this messages ( Existing fields were not successfully updated due to an error noted in the errorlog.txt file the specified log cannot be opened) and second (unable to open log database: C:\DXKeeper\Database\nk4l.mdb).

Any ideas how I can recover my log

+ You could continue to use your log by reverting to the previous version of DXKeeper, but if you place your log file in a zip archive, attach the zip archive to an email message, and send the message to me via

aa6yq (at) ambersoft.com

+ I will "upgrade" it and send it back to you.

       73,

             Dave, AA6YQ

--
jose gonzalez

I reported here on two threads that GridTracker was the culprit. Yes.

Yes Dave.  Brought over obsolete radio.txt.  I will try to find current list.  When I reinstalled DXL Suites, I thought any file like that would get an update.  I will search web for current file.  Wonder how many other brought over files are obsolete?  May need to delete it all and start over

yes. All suites installed and up to date. Cannot find K3s in Commander>config>rGeneral>radio dropdown.

+ K3 is the correct entry to select. There has never been a K3S entry.

73,

Dave, AA6YQ

yes.  All suites installed and up to date.  Cannot find K3s in Commander>config>rGeneral>radio dropdown.

+ AA6YQ comments below

Hi. Suffered a fatal hd crash. Installing DXL on new PC. Rig is K3s. I do not see it in DXK Radio Config drop down. I see KENWOOD option. Since Elecraft choice is KENWOOD,or K2 is that the right Radio or else why don't I se K3s in dropdown?. Radio is not responding to that choice.

+ It sounds like you're not running the current version of Commander, which is 15.0.9. Either that, or your Commander folder contains an obsolete Radios.txt file.

73,

Dave, AA6YQ

Thanks, Leo! I will issue an updated Pathfinder search for 425 DX News.

Dave

Did you direct Launcher to update the other applications?

Hi.  Suffered a fatal hd crash.  Installing DXL on new PC.  Rig is K3s.  I do not see it in DXK Radio Config drop down.  I see KENWOOD option.  Since Elecraft choice is KENWOOD,or K2 is that the right Radio or else why don't I se K3s in dropdown?.  Radio is not responding to that choice.

Jim K7EG