[TRLog] What the....?

[k8do]

I agree on Ten Tec, Tree... I have been a rabid supporter of "Buy American",
forever... As  a result I have shelves full of forty years worth of
Heathkit, Drake, and Ten Tec, HF gear... However, getting back into
contesting after a layoff I was ready for a new run radio and I took  a
long, hard look at every offering... After wrestling with my conscience for
weeks <I literally sweated bullets over buying foreign> I chose the Yaseau
MKV with a full load of filters... I used it in CQWW, ssb and cw , with
TR-Log... I had zero problems that I know of, both with the radio and with
the interface to TR-Log...
I feel really bad over abandoning Ten Tec, but they are surrendering their
position in the top of the line, contest radio ranks, and putting their
dollars into the volume driven, computer radios... Probably, a good business
decision, but not one that helps me...

Cheers  ...  Denny
----- Original Message -----
From: <n6tr@teleport.com>
To: <trlog@contesting.com>
Sent: Thursday, December 14, 2000 11:13 AM
Subject: Re: [TRLog] What the....?


>
> > I can't beleive the manufacturers haven't gotten a clue on this
> > already. We've had radios capable of computer interface for what,
> > at least 15 years? (the FT757GX, not a II, in my car is rudimentarily
> > capable). In that time I have been involved with LOGic (my regular
> > logging software), brand C, Brand N, and of course TR, as a user,
> > and it just amazes me hearing what I have heard. It appears that
> > Kenwood is a dream to write code for, Yaesu okay but doesn't do a couple
> > of things well, Icom sucks, and Ten-Tec, having the choice of the 3
> > to adapt, picks the worst one to emulate.
>
> That sums it up pretty well.  From my perspective, Kenwood implemented
> a nice instruction set - that is easy to program - and it is very
> consistent between radios.
>
> Yaesu has been unable to have the same command set for any of their
> two radios.
>
> There are basically two different Icom formats.  The Ten-Tec I had
> here a few years ago seemed to have some firmware problems (in the
> radio), but any attempt I made to try and work with them didn't go
> anywhere.  One idea I had for Ten-Tec, was to implement two
> differnet formats - the current one, and one that emulated Kenwood.
> While they seemed to think that might be a good idea - they didn't
> have the resources to do the programming.  I even offered to do the
> work, but they weren't interested.
>
> One of the strange thing with the Icoms - is that you have to ask for
> frequency and mode in separate commands - and depending on the radio,
> you need to give the radio a big rest between the two commands, or it
> won't respond.  I have a hunch that some of the problem here might be
> that the firmware in the radio is "out to lunch" and the commands are
> too close.
>
> However, with the right amount of experimentation, I should be able
> to fix it - but it is hard without a radio.  I did just pick up an
> IC-729 and haven't hooked it up yet (but will soon).  Hopefully, I
> will be able to see something to work on.
>
> In the mean time - please send me any RADIO.DBG files that demonstrate
> the problem.  Make sure you tell me which program version you are using
> and what the radio type is.
>
> I can also put more protection against NONCW being displayed - like
> using a previous value until there are several of them in a row (digital
> filtering).
>
> Tree
>
> --
> FAQ on WWW:               http://www.contesting.com/FAQ/trlog
> Submissions:              trlog@contesting.com
> Administrative requests:  trlog-REQUEST@contesting.com
> Problems:                 owner-trlog@contesting.com
> Feature Wishlist:   http://web.jzap.com/n6tr/trwish.html
>



--
FAQ on WWW:               http://www.contesting.com/FAQ/trlog
Submissions:              trlog@contesting.com
Administrative requests:  trlog-REQUEST@contesting.com
Problems:                 owner-trlog@contesting.com
Feature Wishlist:	  http://web.jzap.com/n6tr/trwish.html