[Dx4win] K3 / Split / DX cluster

[Bob Thompson - N9SF]

Hi Bruce,
You are certainly NOT ALONE!  This defect has been brought up 
numerous times over the years but for the Kenwood radios as the 
commands are the same for Elecraft radios.  Is it on the list to be 
fixed?  Well, if it is on the fix-it list the priority has been pretty low.

I have loyal to DX4WIN for over 10 years.  There are a lot of good 
features about DX4WIN.  But, there have been a few things that 
irritate me.  This is a major irritant.

With the Kenwood radios it was a quick button push on the radio to 
get split operation.  But, that is only after clicking the spot 
twice, in some cases, to get both frequencies loaded.  With the way 
the K3 buttons are setup, getting set for split is a little more bother.

Actually, the K3 gets put into the SPLIT mode but on the previous 
band, the one it came from.  Using the BAND button, scroll back to 
the previous band and you will see.  Basically, the commands for 
mode, split, and frequencies are sent to the radio in the wrong order.

Paul has done pretty good at keeping up with many of the fixes needed 
over the years.  Why he hasn't fixed this long standing bug is a 
mystery.  BUT, I wish he would find some motivation to get it 
done.  Please, Paul.

73,
Bob - N9SF


At 22:12 8/6/2008, you wrote:
>I will ask again..
>
>The first time I asked I did get a couple off reflector replys that I was
>not alone seeing this bug in DX4Win and . one responder also pointed out
>that not only did DX4win not put the K3 into SPLIT mode, but it also did not
>change the mode of VFO B.
>
>As asked before -
>
>Tonight I was testing DX4Win version 7.04.04 to see how it worked with the
>K3.  Everything I tested seemed to be fine except for how it managed the DX
>Cluster with split frequency spots.   I sent a test spot for two freqs on 80
>with the K3 set to split op.  The spot appeared to be correct in the cluster
>display.   I then cleared the log window and changed the band of the K3 to
>40.  After clicking on the spot the frequencies were correct but the K3 did
>not go into split mode.  The TX focus stayed on VFO A.    I then closed
>DX4win and opened Write-Log and tried the same test using the spot sent from
>DX4Win.   Write-Log worked fine, going to the correct frequencies and TX
>focus was on VFO B as it should be.
>
>Is this BUG on the list to be addressed?
>
>73,
>Bruce - N1LN
>(aka: NC4KW)
>
>K3 #1062
>K3 #1193
>
>_______________________________________________
>Dx4win mailing list
>Dx4win at mailman.qth.net
>http://mailman.qth.net/mailman/listinfo/dx4win