[Dx4win] Another Issue with Kenwood in 7.03.16

Tom LeClerc W1TJL w1tjl at arrl.net
Thu Jun 7 17:26:57 EDT 2007


Hi Paul, Steve, Gang,

Here's another issue I discovered today with the 7.03.16 version that
worked properly with 7.02. It is in the same area - when I am on a VFO
and click on a spot with a split the split occurs normally and all
appears well.  However if I then click on a spot that is not a split,
the radio remains in split mode and the VFO-B is still on it's
previous frequency.  This occurs even if the mode changes from CW to
SSB or vice versa.  Also it happens on both my TS-690SAT as well as
the TS-950SDX.

Has there been any progress on figuring out what the cause of this anomoly is??

Thanks in advance for your help and of course for such a great
program!  BTW, if you need me to do any testing I'd be glad to...

73, Tom W1TJL

---------- Forwarded message ----------
From: Tom LeClerc W1TJL <w1tjl at arrl.net>
Date: May 12, 2007 12:06 PM
Subject: Issue with Kenwood in 7.03.16
To: dx4win <Dx4win at mailman.qth.net>


Hi Guys,

Here is something I just stumbled across with the newest version of DX4Win:

My Kenwood TS-950SDX has always been perfect when being controlled by
all previous versions of DX4Win (after I upgraded the bios in the
radio).  With the latest version I have run into an issue when
listening to a memory and clicking on a spot, the radio will change to
the mode of the spot and stay on the memory frequency and indicate it
is still in memory mode.  If I switch to the VFO, the frequency is set
to the spot correctly.  The radio no longer switches to the VFO
automatically.

I launched the previous version of DX4Win (7.02.15) and it again works
perfectly, switching to the VFO as it should.

Next I tried my TS-690SAT (on radio 2 connection) and found exactly
the same thing happened.  So it appears something has changed in the
control of the radio.

I then copied the driver from the older version (after renaming the
driver in the new version and shut down and restarted DX4Win.  This
did not resolve the problem.  So it appears the issue is not the
driver itself.

Anyone else notice this???

Paul??  Thoughts??

73, Tom W1TJL

--
Tom LeClerc, Amateur Radio Station W1TJL
(past calls WB1CBY, /VE8,XL8,VO1)

         LeClerc Consulting
        email: w1tjl at arrl.net
       PC/Network Consulting


-- 
Tom LeClerc, Amateur Radio Station W1TJL
 (past calls WB1CBY, /VE8,XL8,VO1)

          LeClerc Consulting
         email: w1tjl at arrl.net
        PC/Network Consulting


More information about the Dx4win mailing list