[DXBase] Kenwood TS-2000 users.
Jack
[email protected]
2002年12月28日 13:40:50 -0500
Hi Ron,
Well, merely switching to a USB connector on the radio isn't going to do
anyone any good if the same dumb command interface and constant changes
continue to occur. Yes, we too went to task with ICOM over the 756, then
there was the Yaesu 847, and now the TS2000. It's just ridiculous. But one
thing is for sure, dealing with these radio inconsistencies is costly and we
either have to change our design structure and charge accordingly to add
radio specific code for each radio, or the makers of radios are going to
have to get standard.
Maybe hams will help fix this the right way by taking the few minutes to
write to these manufacturers and tell them they are sick of it.
Will see what new methodology they implement via USB.. hihi
Jack
----- Original Message -----
From: "Ron Stordahl" <[email protected]>
To: "Jack" <[email protected]>; "Phil ON4VP" <[email protected]>;
<[email protected]>; "Brendan Minish" <[email protected]>
Sent: Saturday, December 28, 2002 1:27 PM
Subject: Re: [DXBase] Kenwood TS-2000 users.
> Jack
>> I went round and route with ICOM USA in California about the ICOM 756
series
> and then also with the same manager who was at the Dayton Hamvention. My
> conclusion was that he was also frustrated and himself couldn't get
answers
> from Japan himself.
>> I also posted my complaints about the ICOM 756 interface in a number of
> reflectors. I didn't think about e-Ham however, and maybe there is a
> similar posting forum at QRZ. So you have given me an idea.
>> My prediction..new rigs will be introduced with drop the serial interface
> completely and replace it with USB 2.0. It will be a lot better, but now
> your work will start over again.
>> Ron
> N5IN
>>>>> ----- Original Message -----
> From: "Jack" <[email protected]>
> To: "Phil ON4VP" <[email protected]>; <[email protected]>; "Brendan
> Minish" <[email protected]>
> Sent: Saturday, December 28, 2002 11:33 AM
> Subject: Re: [DXBase] Kenwood TS-2000 users.
>>> > Thanks for the info Brendan. Tony is also experimenting with a
> modification
> > to the radios.ini file that so far seems to work fine for setting the
mode
> > of VFOb, but he is not finished testing it.
> >
> > I'm curious about something:
> >
> > Is there anyone who has written to any of the makers of radios to
complain
> > to them about their lack of maintaining a standard RS232 interface set
of
> > commands, sequence, and structure? If so, what response did you get?
> >
> > Has anyone complained to them about the constant changing of the RS232
> > interface for no good reason except change itself, whenever a new radio
is
> > introduced? If so, what response did you get?
> >
> > Has anyone complained to the makers of radios that you are tired of
having
> > to obtain software changes to the programs that you use every time you
> > decide to purchase one of these new radios only to find that the RS232
> > interface is different than how it was in previous radios?
> >
> > Does anyone plan to write a letter of complaint to the makers of radios
> > about this topic? If not, why?
> >
> > Do you think that it is the obligation of the makers of software to
> > constantly modify their code each time a new radio comes out that
requires
> a
> > different RS232 interface? If so, are you willing to pay for this
> service?
> > How much, 30,ドル 50ドル?
> >
> > Have you ever posted a review for any of these radios such as on eHam
and
> > mentioned a complaint about the fact that this new radio might be the
> > greatest thing since sliced bread, but it has a deficient RS232
interface
> > and therefore you don't recommend it for others?
> >
> > I'd prefer not to clutter up the reflector with this topic but would
like
> to
> > know your opinions at least in direct email to:
> > [email protected]
> >
> > Imagine if every time a new automobile was introduced, the roads had to
be
> > modified in order for you to drive it. Imagine if every time you
> purchased
> > a new electrical appliance, you had to call an electrician to modify
your
> > wall plugs. Imagine if everytime you purchased a television set, you
had
> to
> > call your cable or satellite provider to change their signal in order
for
> > you to receive the TV stations? In our humble opinion, the problems
that
> we
> > constantly hear about involving all software, not just ours, could be
> easily
> > eliminated if the ham community would be a vocal about complaining to
the
> > source of the problem as they are in making demands of the software
> > companies to "do whatever" to make their new radio work. All it would
> take
> > is for hams to notify the makers of radios that they will no longer
> consider
> > purchasing a new radio unless the RS232 interface is consistent with
> > previous radios. If it isn't, then they will choose a radio that is
from
> > some other manufacturer.
> >
> > Anyway, so much for our soapbox. It's clear to us that this constant
> > vicious cycle has simply got to change. It can be fixed at the source
if
> > folks make this an issue to the makers of radios. All it takes is five
> > minutes to type a short and sweet letter and mail it. Or, we can deal
> with
> > it in software and charge a fee for the work that is required to support
> the
> > changes that come about all because makers of radios will not implement
> any
> > consistency in their products.
> >
> > We, along with many other makers of software have already complained to
> > these manufacturers but our cry has fallen on deaf ears. Probably we
only
> > represent a few potential sales to them. But, if the general ham
> population
> > voiced this issue, your collective purchasing power may just open those
> deaf
> > ears.
> >
> > Cheers,
> > Jack
> >
> > ----- Original Message -----
> > From: "Brendan Minish" <[email protected]>
> > To: "Phil ON4VP" <[email protected]>; <[email protected]>
> > Sent: Saturday, December 28, 2002 10:54 AM
> > Subject: Re: [DXBase] Kenwood TS-2000 users.
> >
> >
> > > I may have the answer to this one.
> > >
> > > DXB 2003 sends the mode before the frequency when setting the radio,
in
> > > some radios (like the elecraft k2 which uses the kenwood command set)
> that
> > > remember last used mode on a per band basis, this will on occasion
cause
> > > the wrong mode to be set because the software sets the VFO mode on the
> > band
> > > it is just LEAVING (hence the U in CW) and tunes to the new band with
> > > whatever mode was last used on that band.
> > >
> > > Some radios apparently need the commands sent in this order so it's
not
> > > really a bug.
> > >
> > > The fix is easy, you simply have to include the mode set command at
the
> > end
> > > of the frequency set line and set the mode set command to Null, the
mode
> > > set command is never sent to the radio without also setting the
> frequency
> > > so including the mode set Command in the VFO set line won't break
> > anything.
> > >
> > > Here is an extract from my file for the Elecraft K2 It may need some
> > > modifying for the TS2000 but hopefully you get the idea.
> > > showing how I have configured the radios.ini file to make it work
> > correctly
> > > with the K2
> > >
> > >
> > > SelectVFOA= eoc(100) asc( "FR0;" ) eoc(0)
> > > SetVFOA= asc( "FA" ) dec( %vfoa,11 ) asc( ";" ) asc("MD") dec(
%mode,1)
> > asc
> > > ( ";" ) eoc(0)
> > > GetVFOA= asc("FA;") rrs(14) eoc(0)
> > > PrsVFOA= asc("FA") dec(%vfoa,11) asc(";") eoc(0)
> > >
> > > SelectVFOB= eoc(0)
> > > SetVFOB= asc( "FB" ) dec( %vfob,11 ) asc( ";" ) eoc(0)
> > > GetVFOB= asc("FB;") rrs(14) eoc(0)
> > > PrsVFOB= asc("FB") dec(%vfob,11) asc(";") eoc(0)
> > >
> > > SetMode= eoc(0)
> > > GetMode= asc( "IF;" ) rrs(38) eoc(0)
> > > PrsMode= asc("IF") dec(%dummy,27) dec(%mode,1) dec(%dummy,7) asc(";")
> > eoc(0)
> > >
> > > I have put the entire K2 file at the very bottom of this e-mail for
> > > reference, NOTE there are no line breaks in the middle of lines.
> > > The K2 runs very happily here with pacing set to 1 and EOC(0) which
> makes
> > > for very fast responses to commands, Perhaps the ts200 can use similar
> > fast
> > > timings as it sure speeds things up.
> > >
> > > The eoc(100) in the first line
> > > SelectVFOA= eoc(100) asc( "FR0;" ) eoc(0)
> > > cures a 'radio not responding ' problem that crops up sometimes under
> > win2k
> > > on my machines.
> > >
> > >
> > > 73
> > > Brendan EI6IZ
> > >
> > > At 07:31 22/12/2002 +0100, Phil ON4VP wrote:
> > > >same here Tony, also having the two 'U's sent but mode not changed.
> > > >here intel PIII/1000, 512 Mb, XP pro, radio on com 2
> > > >
> > > >Phil ON4VP
> > > >
> > > >----- Original Message -----
> > > >From: "Tony Cash" <[email protected]>
> > > >To: "Al Bailey" <[email protected]>; <[email protected]>
> > > >Sent: Friday, December 20, 2002 6:07 AM
> > > >Subject: Re: [DXBase] Kenwood TS-2000 users.
> > > >
> > > >
> > > > > I just tried your exact spot and baud between computer and the
radio
> > > > > and it DOES NOT work here. VFO B mode never changes. The radio
> > > > > sends a U twice just like it should when changing both VFO's to
USB
> > > > > but VFO B does not change. I agree with Clark, This may be a
problem
> > > > > in the particular "order" in which the commands are sent.
> > > > > My setup is as follows
> > > > > Intel pentium IV 2.4 GHz.
> > > > > 512 meg. memory
> > > > > Radio on Com 1
> > > > > Operating system is XP Home
> > > > >
> > > > > 73 de Tony, KD4K
> > > > >
> > > > > My Weather Page
> > > > > http://home.adelphia.net/~tonycash/
> > > > > My Ham Radio Page
> > > > > http://home.adelphia.net/~tonycash/kd4k/radio.html
> > > > > Sawnee Mountain (WB4GQX 147.15 +.600) Repeater Page
> > > > > http://home.adelphia.net/~tonycash/sawnee/index.html
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Al Bailey" <[email protected]>
> > > > > To: <[email protected]>
> > > > > Sent: Thursday, December 19, 2002 11:49 AM
> > > > > Subject: [DXBase] Kenwood TS-2000 users.
> > > > >
> > > > >
> > > > > > 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
> > >
> > >
> > > The K2 file
> > >
> > > [ELECRAFT_K2]
> > > #Elecraft K2 revision 0.3 by Brendan Minish [email protected]
> > > P_LSB=1
> > > P_USB=2
> > > P_CW_USB=0
> > > P_CW_LSB=0
> > > P_AM=5
> > > P_FM=4
> > > P_FM_N=0
> > > P_DATA_LSB=0
> > > P_DATA_USB=0
> > > P_DATA_FM=0
> > > P_CW=3
> > > P_FSK=6
> > > P_RTTY=6
> > > P_PACKET=9
> > >
> > > LSB=1
> > > USB=2
> > > CW=3
> > > FM=4
> > > AM=5
> > > FSK=6
> > > RTTY=6
> > > HIGH=3
> > > MEDIUM=2
> > > LOW=1
> > > OFF=0
> > > ON=1
> > >
> > > FREQDIVIN=1
> > > FREQDIVOUT=1
> > > USEEXTENDEDMODES=0
> > > FREQSHIFT=0
> > > PACING=1
> > >
> > > DefaultCW=3
> > > DefaultAM=5
> > > DefaultFSK=6
> > > DefaultRTTY=6
> > > DefaultFM=4
> > >
> > > SelectVFOA= eoc(100) asc( "FR0;" ) eoc(0)
> > > SetVFOA= asc( "FA" ) dec( %vfoa,11 ) asc( ";" ) asc("MD") dec(
%mode,1)
> > asc
> > > ( ";" ) eoc(0)
> > > GetVFOA= asc("FA;") rrs(14) eoc(0)
> > > PrsVFOA= asc("FA") dec(%vfoa,11) asc(";") eoc(0)
> > >
> > > SelectVFOB= eoc(0)
> > > SetVFOB= asc( "FB" ) dec( %vfob,11 ) asc( ";" ) eoc(0)
> > > GetVFOB= asc("FB;") rrs(14) eoc(0)
> > > PrsVFOB= asc("FB") dec(%vfob,11) asc(";") eoc(0)
> > >
> > > SetMode= eoc(0)
> > > GetMode= asc( "IF;" ) rrs(38) eoc(0)
> > > PrsMode= asc("IF") dec(%dummy,27) dec(%mode,1) dec(%dummy,7) asc(";")
> > eoc(0)
> > >
> > > SetFilter= asc("K22;") asc( "FW0000" ) dec( %filter, 1 ) asc ( ";" )
> > eoc(0)
> > > GetFilter= asc("K22;") asc( "FW;" ) eoc(0)
> > > PrsFilter= asc("FW") dec(%dummy,4) dec( %filter, 1 ) asc ( ";" )
eoc(0)
> > >
> > > SetSplit= asc( "FT" ) dec( %split ) asc ( ";" ) eoc(0)
> > > GetSplit= asc( "IF;" ) rrs(38) eoc(0)
> > > PrsSplit= asc("IF") dec(%dummy,30) dec(%split,1) dec(%dummy,4)
asc(";")
> > eoc(0)
> > >
> > >
> > > _______________________________________________
> > > DXBase Reflector - Please visit us on the web at www.dxbase.com
> > > - - - - - - - - - - - - - - - - - - - - - - -
> > > To UNSUBSCRIBE please visit:
> > > http://mailman.qth.net/mailman/listinfo/dxbase
> >
> >
> > _______________________________________________
> > DXBase Reflector - Please visit us on the web at www.dxbase.com
> > - - - - - - - - - - - - - - - - - - - - - - -
> > To UNSUBSCRIBE please visit:
> > http://mailman.qth.net/mailman/listinfo/dxbase
> >
>> _______________________________________________
> DXBase Reflector - Please visit us on the web at www.dxbase.com
> - - - - - - - - - - - - - - - - - - - - - - -
> To UNSUBSCRIBE please visit:
> http://mailman.qth.net/mailman/listinfo/dxbase