Tony,
Thanks for the new Kenwood TS-2000 "Radio.ini" file. It looks like
you have solved the mode problem when clicking on spots with QSX in them.
I played with it a bit today and found that, as you sent it, the
speed was too much for my radio. When the TS-2000 changes modes, it sends
the mode in Morse Code through the speaker and the faster speed caused the
CW to be garbled. It was trying to send the second mode indicator before
it had finished sending the first mode indicator.
Computer: Celeron 366 MHz, Windows 98
No parity, 8 bits and 1 stop bit, 9600 baud
I'm sure my computer can talk to the radio faster but it takes a
certain amount of time to send the mode indicator in Morse Code. So, I
increased the PACING to 20 (from your "1") and I increased the EOC's from
your "1" to "50" and the SETMODE EOC to "100" and that seemed to work fine
for me.
My TS-2000 now correctly changes the frequency AND mode on both VFO's
on spots with QSX in them. Here is my test setup:
Began with the radio set to this:
VFO A: 28525.00 USB
VFO B: 146520.00 FM
Split: OFF
VFO A was the active VFO
Clicked on this spot: 7012.9 S21YY QSX 7013.50
The TS-2000 QSY'd to the following:
VFO A: 7012.90 CW
VFO B: 7013.50 CW
Split: ON
Active VFO = A
I then tried it with the same initial radio set-up except for making
VFO B the Active VFO. And got exactly the same result except VFO A was now
the Active VFO. So, no matter which VFO is active when you click on a spot
with a QSX in it, you end up with the A VFO being on the DX's transmit
frequency and the B VFO on the DX's receive frequency. AND, both VFO's are
on the correct mode it seems. This is probably just fine for split QSO's
because you need to use both VFO's for the current contact and you need to
log your transmit frequency in the log (and the QSX frequency in the Notes
column.)
On further testing, I clicked on this spot: 18142.2 P49RM
When the TS-2000 was set up like this:
VFO A: 28525.00 USB
VFO B: 146520.00 FM
Split: OFF
VFO A was the active VFO
I got this result:
VFO A: 18142.2 USB
VFO B: 146520.00 FM
Split: OFF
VFO A was the active VFO
BUT, if I did the same test EXCEPT the TS-2000 had the B VFO as the
Active VFO before clicking on the spot, then this was the result:
VFO A: 18142.2 USB
VFO B: 146520.00 FM
Split: OFF
VFO A was the active VFO
On first glance it looks like that is what should happen. It is the
exact same result from the prior test where VFO A was the Active VFO to
start with. However, if I was listening to a station on 28525.0 that I
wanted to work later, and went to VFO B before clicking on the spot, I
would loose the frequency I had in VFO A when DXBase changed the frequency
of the A VFO to match that of the spot. I would expect DXBase to first
determine that VFO B was the Active VFO and change it's frequency instead
of VFO A's.
It may be arranged to work this way because DXBase logs the frequency
from VFO A regardless of what VFO is active. DXBase will always pick the
frequency of VFO A to enter into the log, even if you made the QSO on VFO
B. For example:
With the radio set as follows:
VFO A: 28525.00 USB
VFO B: 7031.00 CW
If you make a contact using the B VFO as the active VFO (that is you
worked the station on 40-M CW) and you type in his call into DXBase and hit
"Tab", the log will record your contact on 28525.00 kHz as a CW QSO. Ooops,
it logged the WRONG band and frequency for the QSO! MAJOR problem!
My version of WriteLog will log the correct frequency no matter which
VFO is Active. The WriteLog software knows to look for the Active VFO and
then take the frequency from that VFO for the log.
We are definitely making progress with DXBase and the
TS-2000! However, I still would like to see DXBase determine which VFO is
the Active VFO before it determines what frequency it will enter in the
log. When you are working stations at a high rate, it is a real pain to
have to move the DX station's frequency into the A VFO before you can log
the contact. DXBase does get the mode from the radio before it logs it but
it just ASSUMES you are using VFO A and gets that frequency without
checking which VFO is Active.
Of course I must mention that I am running DXBase 2002 (2003 bought
at Dayton but not yet installed.) If the above situation of logging the
Active VFO works differently in DXB2003, please let me know.
Here is how I "think" DXBase should work when determining what
frequency to log:
1. Check which VFO is Active
2. Get the frequency from the Active VFO
3. Log that in the "Frequency" column
4. Check to see if "Split" is "On"
5. If "Split" is "On" then get the frequency from the non-Active VFO
6. Log the non-Active VFO frequency in the "Notes" column
When working with a non-QSX spot from VHF or Internet Packet spots:
1. Check which VFO is Active
2. Change the frequency of THAT VFO to the Spot frequency
I can send anyone who wants it a copy of my current TS-2000 Radio.ini
file upon request.
Best Wishes in 2003 for everyone!
At 01:46 AM 1/1/03 -0500, you wrote:
>Well Guys, here it is.
>Break it if you can.
>I have attached the modified "Radios.ini" file that I have been using
>flawlessly for several days now and hope it cures the problem for
>everybody. I have the speed between my TS-2000 and the computer
>set to 56700 8 N 1. My computer is a 2.4 GHz Pentium 4. It may be
>possible that some with really slow computers may have to up the
>"Pacing" and the "eoc". I have the "Pacing" set to 1 (one) and also
>the "eoc" where they were set to 200 now set to 1 (one). If you have
>problems then set the "Pacing" back to 50 and the "eoc" back to 200
>(where I have them set to 1 (one)) then start lowering the numbers for
>the "pacing" and "eoc" (where they are 200) until you get it working as
>fast as it will work. Leave all the "eoc" that are set to 0 (zero) alone
>(they
>have not been messed with). All these changes only refer to the TS-2000
>part of the "Radios.ini" file.
>Hope you all had a Merry Christmas and hope that this file will give you
>a Happy New Year (I know it will help mine a lot)
>
>73 de Tony, KD4K
CUL, 73, Clark, W8TN
email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
Webpage: <http://www.w8tn.com>
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
The reason this message is shown is because the post was in HTML
or had an attachment. Attachments are not allowed.
Please post in Plain-Text only.---
