Jim,
The firmware for the jupiter, Omni VII, Orion and OII are completely
different. One will not run at all on the other. Just like the computer
systems in a Ford will not work in a Chevy.
It is a clear issue of just poor programming, testing (following a very
detailed test plan)) and in general poor management of the development
process. I am in the business...and that's why this happens.
There are, I'm sure, plenty of SUPERB mico-code/firmware programmers
that have experience with RF systems available out there looking for
work.
If they handled things like that with the Military projects...theywould
no longer be a supplier.
I hope John Henry sorts it out.
73,
Lee. KC9CDT
-----Original Message-----
From: jmiller1706@cfl.rr.com
To: tentec@contesting.com
Cc: tentec-request@contesting.com
Sent: Thu, Apr 15, 2010 10:33 am
Subject: Re: [TenTec] Orion2 Firmware Update
I'm going to give the benefit of the doubt now. Could be a number of
things
other than inadequate testing before release.
I am wondering if the firmware is finding some uninitialized residual
parameter
data in our O2's that isn't in the test radio they have that's causing
our loads
to go crazy? I assume a power reset should clear memory completely but
maybe
not? Some data values got relocated in flash memory and when you load
it into
our radios there is some uncleared data that's hosing things?
Are they trying to make the software work for both the O2 and the other
radio
(Jupiter?). Maybe it works fine for the other one but not the O2?
If it is indeed poor quality control and testing, then that needs to be
cleaned
up. If TT does work for the government/defense, they should know that
rigorous,
meticulous testing is normally required by the DoD, sometimes taking
weeks and
months to complete. Some of that discipline should carry over to their
commercial products.
And someone commented that it takes a good hot-shot programmer. Yes
that's
partly true, but with software-defined radio technology, it almost
takes PhD
level theoretical/math understanding of digital signal processing
concepts.
Then be able to translate that to firmware. But in reality it takes
many: A
math/DSP guru, a hot shot coder but one who has discipline to craft
good code,
and then a good independent test team to wring out the bugs.
I notice that the download appears to be reposted on the TT page...back
to the
previous version?
73 Good luck - Jim N4BE
_______________________________________________
TenTec mailing list
TenTec@contesting.com
http://lists.contesting.com/mailman/listinfo/tentec
|