TenTec
[Top] [All Lists]

[TenTec] RX-350??

To: <tentec@contesting.com>
Subject: [TenTec] RX-350??
From: n9dg@yahoo.com (Duane Grotophorst)
Date: Sun, 9 Dec 2001 18:26:30 -0800 (PST)
I too have both an RX-320 and a Pegasus, I concur with
Jim, W7ANF. Without question the Pegasus RX is better
than the 320, and I also have no doubt that the 350
shares more in common with the Pegasus/Jupiter than it
does with the 320. BTW the Jupiter's core RF/IF/DSP is
for all practical purposes identical to the Pegasus.

As for the RX-350 it is definitely not just a hopped
up RX-320, looking at the pictures on the TT website
the circuit boards are completely different looking.
In addition while it may share much in common with the
Pegasus/Jupiter in terms of specifications, it too has
different looking circuit boards than the
Pegasus/Jupiter. This should come as no real surprise
since it is only an RX and simply doesn't need any of
the TX parts.

>From what I can see I think you can break the HARDWARE
lineage?s for the TT DSP IF radios into 5 basic
groups.

1. RX-320, ADSP2101 DSP processor, designed for
aggressive price point.
2. Pegasus/Jupiter ADSP2181 DSP, processor, designed
for aggressive price point.
3. RX-350. ADSP 2181?, processor, designed for
aggressive price point.
4. RX-330/331/340 ADSP2181 ADSP processor, designed
for high performance.
5. 526/516? ADSP2181, designed for aggressive price
point.

I don?t have any schematics other than the one for the
RX-320, so I can?t really speculate too much about the
DSP processors used or the clock speeds. However I
have seen references to the specific DSP processor
used for most of the models listed above, the ones
with ??? are not for sure/educated guesses.

As for the SOFTWARE/FIRMWARE lineage, it gets a bit
murkier, though I think it can be broken down into
about 3 different groups.

1. RX-320, Pegasus/Jupiter, RX-350. I would estimate
that on a DSP code level they are within 70-80% of
each other.
2. RX-330/331/340 again 70-80% commonality.
3. 526/516 the same 70-80% between the two.

Now for even more fun consider what the DSP IF code
difference is likely to be between any two radios in
the above two sets of groupings. I would estimate that
there is not more than 50% difference between any of
them in terms of core DSP code. Once again these
estimates are only for the signal processing parts of
the designs not for any front panel control
software/firmware that there may be.

N9DG


--- Jim FitzSimons <cherry@getnet.net> wrote:
> Rick, the RX-350 is a better receiver than the
> RX-320.
> I have the RX-320 and the Pegasus. I also have the
> schematics
> for the RX-320, the Pegasus, and RX-330. The RX-340
> is also
> similar, but it is a much better receiver than the
> Pegasus.
> Jim W7ANF
> 
> ----- Original Message -----
> From: "Rick Williams" <ve7asr@telus.net>
> To: "TenTec List" <TenTec@contesting.com>
> Sent: Sunday, December 09, 2001 16:46 PM
> Subject: [TenTec] RX-350??
> 
> 
> > There was a discussion on the TenTec users net
> today concerning the RX-350
> > vs the Jupiter.
> >
> > The consensus was that the RX-350 receiver is the
> same as the Jupiter
> > receiver.  It's my understanding that the Jupiter
> is a Pegasus in a box
> > without the need for computer and with a power
> supply.  Finally, isn't the
> > Pegasus receiver an really an RX-320 receiver?
> >
> > So if my logic is correct (and I've been wrong
> before -- just ask Jay)
> then
> > isn't the RX-350 receiver an RX-320 receiver in a
> box without the need for
> a
> > computer and with a built in power supply?
> >
> > 73,
> >
> > Rick
> > VE7ASR
> >
> > _______________________________________________
> > TenTec mailing list
> > TenTec@contesting.com
> >
> http://lists.contesting.com/mailman/listinfo/tentec
> >
> 
> _______________________________________________
> TenTec mailing list
> TenTec@contesting.com
> http://lists.contesting.com/mailman/listinfo/tentec


__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com

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