[Top] [All Lists]

Re: [TenTec] [Orion] Orion I firmware

To: "'Discussion of Ten-Tec Equipment'" <tentec@contesting.com>
Subject: Re: [TenTec] [Orion] Orion I firmware
From: "RM" <royalct@inr.net>
Reply-to: Discussion of Ten-Tec Equipment <tentec@contesting.com>
Date: Sun, 19 Feb 2006 14:38:49 -0500
List-post: <mailto:tentec@contesting.com>
A maintenance contract for a few hundred dollars a year; I'll go back to
buying legacy radios like the upcoming FT-2000.  Do the code correct the
first time.

Software can mature early on, later on, or never.  I've successfully managed
software projects in the past.

I've learned that when one uses light duty processors/memory combined with
elegant programming, bugs fit into the last category; that is, fix one thing
break several other things resulting in code that never gets fixed.

I am not a software engineer, thank goodness, but an engineer, project and
program manager that was taught the systems engineering and design
process.............One cannot end up with 'elegant' code when following a
disciplined management/design approach, and bugs usually fit into the first
category (that is fix one thing, and nothing else breaks.  Been there, Done
it......it works, but the investment up front is large.

Please do not get me wrong, I've upgraded my Orion to the Orion II.  Love
the radio. 

Ron, NU1U 

-----Original Message-----
From: tentec-bounces@contesting.com [mailto:tentec-bounces@contesting.com]
On Behalf Of Martin, AA6E
Sent: Sunday, February 19, 2006 14:07
To: Discussion of Ten-Tec Equipment
Subject: Re: [TenTec] [Orion] Orion I firmware

I don't think I've seen an "inherent flaw" in v2.  From all that has
been said, v2 has a much better technical base than v1 did.  (Of
course, you can still run v1 forever if you want.) And v2 has to work
for the Orion 2, at least.  The DSP code is probably highly similar
between the O1 and O2, so things like the SP and AN problems should be
fixable.  Only the control code should (?) differ.

Without knowing the details at TT (and I'm sure they mean to do well
by us), I'd say the problem is likely just that there are not enough
man-hours allocated for ongoing Orion 1 work (and Orion 2, probably). 
That's the danger of SDR products - they get shipped before the
software has stabilized.  After product has shipped, it's hard to
motivate investment in software development, since it's a money loser.
 They have to look toward the next wave of products.

Tell me it isn't so!

Why not offer a maintenance contract for a few hundred dollars a year,
if that would keep the ball rolling?  That would change the economics
quite a bit.

73 Martin AA6E

On 2/19/06, Toby Pennington <toby423@earthlink.net> wrote:
> V2.0 has been a bear for Gary and company,  with many hours and weekends
> spent trying to get it right.  But they seem to be caught in a loop in
> when one thing gets fixed three other problem pop up,  and they seem to be
> unable to escape the loop or trap they are caught in.
> This still leads me to wonder if V2.0  if the right way to go,  and that
> perhaps revisiting 1.xxx with new insight and direction could pay off in a
> more stable firmware without losing the fine functions of the Orion we now
> enjoy.  AS it is,  the new firmware is unusable, except for a small group
> guys who operate the rig in a narrow and confined manner.
> Based on what I have heard and experienced,   I really don't expect to see
> any rapid resoution of the multiple problems associated with 2.0.  It will
> be more of the same in the future unless some new approach is taken to
> correct perhaps what could be called "inherent flaws" in the 2.0 core
> which weaken or nullify the fine features we enjoy in the 1.xxx versions.
> Toby  W4CAK
TenTec mailing list

TenTec mailing list

<Prev in Thread] Current Thread [Next in Thread>