Al,

      I gave your experiment a quick try with my TS-2000.  Here was the set-up:

DXBase 2002 (bought DXB2003 at Dayton, haven't installed it yet)
Tools | Options | User Options then on the HF Radio Tab
      Radio: Kenwood TS-870 (No TS-2000 option in DXB2002)
      No parity, 8 bits and 1 stop bit, 9600 baud.
      Menu Number 56 of the TS-2000 to 9600 baud.
Radio: Kenwood TS-2000 (direct interface from Serial Port)
Computer: Celeron 366 MHz, Windows 98, COM2

Here is the spot I clicked on:  7052.0 LX1KC QSX 7283.0

Began with the radio set to this:
VFO A:  28.525 USB
VFO B:  146.520 FM
Split:  OFF
VFO A was the active VFO


The TS-2000 QSY'd to the following:

VFO A:  7052.0 CW
VFO B:  7283.0 FM  -  Notice the WRONG mode!
Split: ON

      Tried again starting with B as the active VFO:

The TS-2000 QSY'd to the following:

VFO A:  7052.0 USB  -  Notice the WRONG mode!
VFO B:  7283.0 CW
Split: OFF   -   Notice the Split did not Turn on.

      Both times the TS-2000 sent "CW" in Morse twice, indicating the mode 
had been changed on each VFO to CW but on the non-active VFO, it had 
not.  This may be a problem in the particular "order" in which the commands 
are sent.  I'm not sure.  Maybe I need to install DXB2003 and see what happens.

      However, the problem I have complained about before with the Kenwood 
interface to DXBase is that when you log a contact, 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:  28.525 USB
VFO B:  7.031 CW

      If you make a contact with the B VFO active (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 28.525 MHz as a CW QSO.  Ooops, it logged 
the WRONG band for the QSO!

      WriteLog does NOT have this problem.  It logs the correct frequency 
regardless of which VFO I use.  I think DXBase needs to poll the radio to 
see which VFO is active before it logs the contact.

      After the holidays I'll load up DXBase 2003 and see what it does.  In 
the meantime, you might check it out at your end, paying particular 
attention to the mode of the non-active VFO when you click on a spot.  And, 
you might check the problem of making a QSO on the B VFO and see what band 
DXBase logs for your contact.

      Happy Holidays to you and yours and all the best in 2003!

At 11:49 AM 12/19/02 -0500, Al Bailey wrote:
>I noticed some users are having problems with DXBase 2003 and the
>Kenwood TS-2000. I decided to try using a spot which incorporated
>both VFO's and this is the spot I used.
>
>VE3WQ     28496.7 TI9JJP      qsx 28501 Cocos Is            1411 19 Dec
>
>
>Once I clicked on it both VFO's responded as they are supposed to. In
>VFOa I had 28496.7 USB and VFOb I had 28501.0 USB which is exactly
>as it is supposed to do. Prior to the spot I had 50125.0 in VFOa and in
>VFOb I had 432.100 FM.
>
>I am using a Lavaport serial board and COM:3 with settings of 4800 baud
>No parity, 8 bits and 2 stop bits. I have also went into my Kenwood TS2000
>and set the baud rate using Menu Number 56 to 4800 baud.
>
>My operating system is Windows 98SE and the PC is a Gigabyte GA-8HIXP
>and Intel Pentium IV at 2.4 gig.
>
>I hope this helps others clear this up but from where I am sitting I see no
>problem with DXBase regarding rig control with the TS2000X.
>
>Best wishes for the holidays and best 73 de K8SIX


CUL, 73, Clark, W8TN

email:  [EMAIL PROTECTED]  or  [EMAIL PROTECTED]
Webpage:  <http://www.w8tn.com>

Reply via email to