Date   

DXKeeper 15.0.4 is available

Dave AA6YQ
 

This release

- when importing a tab-delimited file, accepts DXCC as the column name for the DXCC country code; when exporting a tab-delimited
file, uses DXCC (not DXCCID) in the column header (thanks to Mike N6MZ)

- remembers the location of the "LoTW Upload" window, if moved (tnx to Jon KM8V)

- if when directed to lookup callsign X, QRZ XML returns information for callsign Y, checks to see if QRZ specifies Y as an alias
for X and if so, reports only location-independent information

- notifies the user if a QSO received from another application can't be logged (tnx to Kevin K9KDS)

- when importing an ADIF file, accepts a comma-delimited list of grid squares specified in the VUCC_GRIDS ADIF tag (tnx to Bob N7ZO)

- update the Secondary Subdivision Database for Alaska to match ADIF (tnx to Michael N1EN)

- adds a "Copy to Windows Clipboard" command to the Log Page Display's right-mouse menu (tnx to Max NG7M)

- updates the CaptureItems.htm, Configuration.htm, ConfigureLogPageDisplay.htm, Contesting.htm, DoubleClick.htm, Export.htm,
FilterLog.htm, Initialization.htm, Items.htm, KeyboardShortcuts.htm, LogNewCapture.htm, ModifLog.htm, MultipleQTH.htm, Progress.htm,
QSL.htm, QSLConfiguration.htm, Scripts.htm, and ViewEditLog.htm documentation files (tnx to Mike K9UW for reporting many
typographic, spelling, and grammatical errors)


Notes:

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

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

3. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



DXKeeper 15.0.4 is available via the DXLab Launcher and via

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


DXView 4.5.5 is available

Dave AA6YQ
 

This release

- prevents modification of entity names in the Override List's Entity column (tnx to Björn SM7IUN)

- adds FT4 to the "Mode Filter" panel on the Configuration window's "Plot Settings" tab



Notes:

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

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

3. After upgrading, to revert to the previous version of DXView, see <http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>


DXView 4.5.5 is available via the DXLab Launcher or via

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


73,

Dave, AA6YQ


Re: Scheduled backups

CJ Johnson - WT2P <wt2p@...>
 

I switched to Macrium Reflect (one of the products on the DXL wiki that AA6YQ linked to) and have a daily snapshot done to my local network attached storage device around 11PM. I do a full disk image backup automatically every Sunday night as well.

I also have DXK's log backup pointed to Dropbox on shutdown.

I have not had to use the Macrium recovery process thus far, knock on wood. I'm sure there's programs out there that will do a backup of your DXLab folder on a specified interval basis, but I haven't tested it. I used one of Macrium's free products to make a full image of this PC's disk from a traditional hard disk to clone it on a SSD, put the SSD in place of the old HD and it worked perfectly.

Hope this helps a bit.

73,
WT2P


Re: Scheduled backups

Dave AA6YQ
 

+ AA6YQ comments below

Is there a way to schedule or trigger backups periodically in DXKeeper, other than doing it manually or the option to drop a backup “on shutdown”?

+ I drew the "don't reinvent the wheel" line at "automatic log backup on shutdown".

+ Everyone should be using a backup-and-recovery product to make both local backups and cloud-based backups of their log file(s) and all other critical files, as well as application installers. See steps 4 and 5 in

<https://www.dxlabsuite.com/dxlabwiki/BackupRecovery>

73,

Dave, AA6YQ


Re: Commander talks but doesn't listen

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for your suggestions. I should have tried some of those steps to begin with. The only reason I was splitting the COM port was so MTTY could run with N1MM+ during RTTY contests.

+ That's not necessary; N1MM can directly interoperate with MMTTY. I'm not a contester and so can't provide you with specifics; if no one else here can do so, contact Rick N2AMG.

73,

Dave, AA6YQ


Scheduled backups

Jon KM8V
 

Is there a way to schedule or trigger backups periodically in DXKeeper, other than doing it manually or the option to drop a backup “on shutdown”?

I usually leave DXKeeper running for extended periods and I’d like to make sure I have backups. 


Thanks & 73 de KM8V 


Re: Commander talks but doesn't listen

Daryl - WT3K
 

Bruce,

Another thing I should have checked. I downloaded the latest and it works with my setup. Thanks everyone for all the help.

73,
Daryl - AC3BU

On Wed, Jul 31, 2019 at 6:53 PM rcktscientist64 <bruce.mclain@...> wrote:
Daryl,

VSPE had some issues with a recent Windows 10 update and issued a new version.  Are you running the latest version of VSPE?

Bruce - K5WBM

Dave,

Thanks for your suggestions. I should have tried some of those steps to begin with. The only reason I was splitting the COM port was so MTTY could run with N1MM+ during RTTY contests. All other communications went through DXLab. Anyway, I stopped VSPE, connected to the original COM port and now Commander is communicating with the radio with no problems. I guess a recent Windows update changed something VSPE was relying on. I'll have to come up with another solution for RTTY when the time comes.

73,
Daryl - AC3BU

On Wed, Jul 31, 2019 at 5:17 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

My current setup is Windows 10->VSPE (split COM port so it can be shared)->DXLab->IC7300. 

+ Any configuration in which two transceiver control applications can simultaneously send commands to the same radio is unreliable, and cannot be supported.


This setup has worked well for over a year until very recently. The symptoms now are that most commands that are issued through Commander or WinWarbler will be executed by the radio (change frequencies, modes, etc) but it will not display the new settings nor will they be updated when I change frequencies manually.

With this setup I also have N1MM->DXLab->IC7300 and it was displaying the same symptoms. I could change bands, modes, and frequencies but it wasn't reading anything from the radio.

The error log shows no messages since the 29th and "Commander Messages" is totally blank. Even when I try Interrogation. The Reset button takes it back to some previous configuration with VFO B as primary. I have rebooted the computer and radio several times.

My system was recently patched so that could be the root of the problem but I don't understand how it would affect communication in only one direction.

+ I suggest that you reboot Windows, and start with the simplest possible configuration: your radio connected to your computer via a USB A-B cable, with Commander directly connected to your radio. If Commander still can't track the radio's frequency or mode, disconnect the A-B cable from your computer and plug it in to a different USB port. If Commander still can't track the radio's frequency or mode, then you should engage Icom Technical support, as the problem is most likely the radio's device driver or its USB interface.

      73,

             Dave, AA6YQ
Bruce McLain - K5WBM
bruce.mclain@...


Re: Commander talks but doesn't listen

Bruce - K5WBM
 

Daryl,

VSPE had some issues with a recent Windows 10 update and issued a new version.  Are you running the latest version of VSPE?

Bruce - K5WBM

Dave,

Thanks for your suggestions. I should have tried some of those steps to begin with. The only reason I was splitting the COM port was so MTTY could run with N1MM+ during RTTY contests. All other communications went through DXLab. Anyway, I stopped VSPE, connected to the original COM port and now Commander is communicating with the radio with no problems. I guess a recent Windows update changed something VSPE was relying on. I'll have to come up with another solution for RTTY when the time comes.

73,
Daryl - AC3BU

On Wed, Jul 31, 2019 at 5:17 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

My current setup is Windows 10->VSPE (split COM port so it can be shared)->DXLab->IC7300. 

+ Any configuration in which two transceiver control applications can simultaneously send commands to the same radio is unreliable, and cannot be supported.


This setup has worked well for over a year until very recently. The symptoms now are that most commands that are issued through Commander or WinWarbler will be executed by the radio (change frequencies, modes, etc) but it will not display the new settings nor will they be updated when I change frequencies manually.

With this setup I also have N1MM->DXLab->IC7300 and it was displaying the same symptoms. I could change bands, modes, and frequencies but it wasn't reading anything from the radio.

The error log shows no messages since the 29th and "Commander Messages" is totally blank. Even when I try Interrogation. The Reset button takes it back to some previous configuration with VFO B as primary. I have rebooted the computer and radio several times.

My system was recently patched so that could be the root of the problem but I don't understand how it would affect communication in only one direction.

+ I suggest that you reboot Windows, and start with the simplest possible configuration: your radio connected to your computer via a USB A-B cable, with Commander directly connected to your radio. If Commander still can't track the radio's frequency or mode, disconnect the A-B cable from your computer and plug it in to a different USB port. If Commander still can't track the radio's frequency or mode, then you should engage Icom Technical support, as the problem is most likely the radio's device driver or its USB interface.

      73,

             Dave, AA6YQ
Bruce McLain - K5WBM
bruce.mclain@...


Re: Commander talks but doesn't listen

Daryl - WT3K
 

Dave,

Thanks for your suggestions. I should have tried some of those steps to begin with. The only reason I was splitting the COM port was so MTTY could run with N1MM+ during RTTY contests. All other communications went through DXLab. Anyway, I stopped VSPE, connected to the original COM port and now Commander is communicating with the radio with no problems. I guess a recent Windows update changed something VSPE was relying on. I'll have to come up with another solution for RTTY when the time comes.

73,
Daryl - AC3BU

On Wed, Jul 31, 2019 at 5:17 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

My current setup is Windows 10->VSPE (split COM port so it can be shared)->DXLab->IC7300.

+ Any configuration in which two transceiver control applications can simultaneously send commands to the same radio is unreliable, and cannot be supported.


This setup has worked well for over a year until very recently. The symptoms now are that most commands that are issued through Commander or WinWarbler will be executed by the radio (change frequencies, modes, etc) but it will not display the new settings nor will they be updated when I change frequencies manually.

With this setup I also have N1MM->DXLab->IC7300 and it was displaying the same symptoms. I could change bands, modes, and frequencies but it wasn't reading anything from the radio.

The error log shows no messages since the 29th and "Commander Messages" is totally blank. Even when I try Interrogation. The Reset button takes it back to some previous configuration with VFO B as primary. I have rebooted the computer and radio several times.

My system was recently patched so that could be the root of the problem but I don't understand how it would affect communication in only one direction.

+ I suggest that you reboot Windows, and start with the simplest possible configuration: your radio connected to your computer via a USB A-B cable, with Commander directly connected to your radio. If Commander still can't track the radio's frequency or mode, disconnect the A-B cable from your computer and plug it in to a different USB port. If Commander still can't track the radio's frequency or mode, then you should engage Icom Technical support, as the problem is most likely the radio's device driver or its USB interface.

      73,

             Dave, AA6YQ





SpotCollector 8.3.8 is available

Dave AA6YQ
 

In this release

- changes made to email parameters on the Configuration window's "Email Alarm" tab will correctly persist when made via the right
mouse menu's Paste command (tnx to Ronald W4RJF)

- stations operating on 60m are not shown as "needed" for Leaderboard (tnx to Björn SM7IUN)

- when logging a QSO based on information from WSJT-X, a duplicate <gridsquare> tag is not erroneously added [DXKeeper ignores this
duplicate tag]


Notes:

1. Consistent with the ARRL's policy of not encouraging DXing on the narrow 60m band, SpotCollector never provided Realtime Award
Tracking for Leaderboard pursuit on this band. However, a defect caused some stations operating on 60m to erroneously be flagged as
"needed for Leaderboard". That defect is corrected in this version.

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

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

4. After upgrading, to revert to the previous version of SpotCollector, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



SpotCollector 8.3.8 is available via the DXLab Launcher, and via

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


73,

Dave, AA6YQ


Re: Commander talks but doesn't listen

Dave AA6YQ
 

+ AA6YQ comments below

My current setup is Windows 10->VSPE (split COM port so it can be shared)->DXLab->IC7300.

+ Any configuration in which two transceiver control applications can simultaneously send commands to the same radio is unreliable, and cannot be supported.


This setup has worked well for over a year until very recently. The symptoms now are that most commands that are issued through Commander or WinWarbler will be executed by the radio (change frequencies, modes, etc) but it will not display the new settings nor will they be updated when I change frequencies manually.

With this setup I also have N1MM->DXLab->IC7300 and it was displaying the same symptoms. I could change bands, modes, and frequencies but it wasn't reading anything from the radio.

The error log shows no messages since the 29th and "Commander Messages" is totally blank. Even when I try Interrogation. The Reset button takes it back to some previous configuration with VFO B as primary. I have rebooted the computer and radio several times.

My system was recently patched so that could be the root of the problem but I don't understand how it would affect communication in only one direction.

+ I suggest that you reboot Windows, and start with the simplest possible configuration: your radio connected to your computer via a USB A-B cable, with Commander directly connected to your radio. If Commander still can't track the radio's frequency or mode, disconnect the A-B cable from your computer and plug it in to a different USB port. If Commander still can't track the radio's frequency or mode, then you should engage Icom Technical support, as the problem is most likely the radio's device driver or its USB interface.

73,

Dave, AA6YQ


an updated USAP Database is available...

Dave AA6YQ
 

...via the Databases tab of DXView's Configuration window. If you have DXKeeper or SpotCollector running, terminate them; then
direct DXView to upgrade its USAP database.

The USAP database specifies a US State and Grid Square for 821,527 stations licensed by the US Federal Communications Commission
(FCC).

Many thanks to Tom KQ5S for preparing this update!

73,

Dave, AA6YQ


Commander talks but doesn't listen

Daryl - WT3K
 

My current setup is Windows 10->VSPE (split COM port so it can be shared)->DXLab->IC7300. This setup has worked well for over a year until very recently. The symptoms now are that most commands that are issued through Commander or WinWarbler will be executed by the radio (change frequencies, modes, etc) but it will not display the new settings nor will they be updated when I change frequencies manually.

With this setup I also have N1MM->DXLab->IC7300 and it was displaying the same symptoms. I could change bands, modes, and frequencies but it wasn't reading anything from the radio.

The error log shows no messages since the 29th and "Commander Messages" is totally blank. Even when I try Interrogation. The Reset button takes it back to some previous configuration with VFO B as primary. I have rebooted the computer and radio several times.

My system was recently patched so that could be the root of the problem but I don't understand how it would affect communication in only one direction.

Thanks,
Daryl - AC3BU


Re: Pathfinder

Dave AA6YQ
 

+ AA6YQ comments below

Using your fantastic DXLabSuite daily, sometimes i observe some peticular issue that i do not understand fully.

Or i look at the wrong page, or my English is to bad to fully understand what i've been reading.

In Pathfinder i only use QRZ.com to populate my capture or Log.

In the upper left side i notice '2017" in the box. There is a pulldown menu, and it is possible to select "2019".

What and when there is something changing if i do set "2019"?

I noticed no direct effect doing it. So i selected "2017" again, as it was before.

In the middle of the start page of PF, there is a message saying: <Last search Library update 14-08-2017 >

I suppose there is a correlation between those two, but i don't understand the mechanism.

Maybe the <helpfiles> i once downloaded and printed are outdated ?

+ Pathfinder was developed in 2000, a time when sources of online QSL information were a new phenomenon that appeared, evolved, and disappeared like flowers in a summer garden. To enable the creation of custom searches for these sources, Pathfinder provides a small set of "substitutions" that can be included in a source's URL. One of them is {SearchYear}, which is replaced by the contents of the Year selector in the upper-left corner of Commander's Main window. Consider an online QSL source that requires a callsign and year to be specified, e.g.

http://www.qslinfo.de/default.aspx?call=P5DX&year=2003

+ Pathfinder's search would specify

http://www.qslinfo.de/default.aspx?call={targetcallsign}&year={SearchYear}

+ Before processing the URL, {targetcallsign} would be replaced by the callsign specified in the callsign box on Pathfinder's Main window, and {SearchYear} would be replaced by the contents of the Year selector.

+ When you are using searches like QRZ that don't include a reference to {SearchYear}, the Year selector setting is irrelevant.

73,

Dave, AA6YQ


Pathfinder

eddy on5jk
 

Dave,

Using your fantastic DXLabSuite daily, sometimes i observe some peticular issue that i do not understand fully.

Or i look at the wrong page, or my English is to bad to fully understand what i've been reading.

In Pathfinder i only use QRZ.com to populate my capture or Log.

In the upper left side i notice '2017" in the box. There is a pulldown menu, and it is possible to select "2019".

What and when there is something changing if i do set "2019"?

I noticed no direct effect doing it. So i selected "2017" again, as it was before.

In the middle of the start page of PF, there is a message saying: <Last search Library update 14-08-2017 >

I suppose there is a correlation between those two, but i don't understand the mechanism.

Maybe the <helpfiles> i once downloaded and printed are outdated ?

Thanks for illuminating my grey cells.

Eddy ON5JK


---
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com


Re: FT4 questions

Dave AA6YQ
 

+ AA6YQ comments below

It's the best part of this group that it has no tolerance for people belittling someone for asking a question no matter how often it was asked or how searchable it is.

+ There is no tolerance here for belittling someone for any reason. We're all Elmers in this group.

73,

Dave, AA6YQ


Re: LOTW download?

CSM&#92;(r&#92;) Gary Huber - AB9M
 

Well I did have DXKeeper backups running, but it appears that stopped when on the conversion to Windows 10 Pro (64 bit). I had ACRONIS doing backups and had completed a full backup just before the crash and Reset files were supposed to be kept but non Windows 10 applications were deleted.

I am still trying to recover the ACRONIS backed up files but at this point have NOT found AB9M.mdb.from 7/28/2019. 

Since there was no DXLab Suite folder after the reset, I reinstalled everything and loaded the latest backup file I could find for DXKeeper (which turned out to be dated 12-06-18). When I follow the instructions from <http://www.dxlabsuite.com/dxlabwiki/LotWRecoveringLostQSOs> the download fails and there is a message stating "LoTW_QSLs.ADI is already open". If I try to import a N1MM adi file to DXkeeper, I get the same message. Importing adi files used to work, so I need to know what I'm doing wrong before I can import files again or recover from LoTW. 

Obviously I have leaned much from this crash, among them, files disappear on physical connected drives and the cloud when you reinstall apps and it is best to take a breath recover files and put them in "safe storage" before starting to reload the computer.

73,
Gary~AB9M


Re: FT4 questions

Tom Schaefer NY4I
 

It’s the best part of this group that it has no tolerance for people belittling someone for asking a question no matter how often it was asked or how searchable it is.

Tom NY4I


Re: Updating DX Keeper

Dave AA6YQ
 

+ AA6YQ comments below

Every time I try to upgrade DX Keeper I get an error message, ... extraction error .....

Have I messed something up, or should I uninstall it and run a fresh install?

It worked fine on my old hard drive, but that fell over so had to put in a new SSD and reinstall win10 then reinstall everything else.

+ Is there an errorlog.txt file in the Launcher's folder? If so, please attach it to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: FT4 questions

Dave AA6YQ
 

+ AA6YQ comments below

My apologies for not finding the answer in the documents and posting here.

+ You have no need to apologize, Norman. All questions are welcome here.

73,

Dave, AA6YQ

23301 - 23320 of 210327