I was hoping one of the folks with more detailed knowledge will jump in,
but lacking that...
The RX888 has an LT2208 16 bit ADC. It's a single ADC, not quadrature,
so Dr. Nyquist says the sample rate has to be twice the receiver
bandwidth. The "stock" RX888 runs at 122.88 msps, giving a bandwidth
from near DC to about 60 MHz. There is no FPGA in the receiver, so what
comes down the USB3 link is raw samples. I *believe* that the data is
sent down the USB3 interface with two bytes per sample to support the 16
bit ADC.
That's about 2 gbit/second data rate, which is well below the minimium 5
gpbs that USB3 can handle.
Because of concerns about heat dissipation, most of the RX888s in the
HamSci community have been running with a 64 MHz clock generated by a
GPSDO-controlled clock. The slower sample rate allows coverage to 30
MHz, and the ADC doesn't get quite so hot. (There is now doubt whether
the heat really is a concern, but most folks continue to run this way.)
At 64 msps, the data rate down the USB3 is about 1 gbps.
USB3 can easily handle either of these data rates; the issue is whether
the PC can process that firehose fast enough. The general experience is
that a Raspberry Pi 5 is not quite able to handle 122.88 msps, but can
deal with 64 msps. Something like an i5 PC can handle the full data
rate and do some useful work besides.
A couple more notes --
* The internal antialiasing filter cuts off somewhere above 70 MHz,
which is fine for the 64 MHz bandwidth at 122.88 msps. When running at
64 msps, you need an additional low pass filter at around 32 MHz or you
will get aliases from low-VHF band and 6M transmitters.
* The above is all talking about using the "HF" antenna input which is
directly sampled in the ADC. The RX888 also has a VHF/UHF input that
can be software selected (the hardware is similar to that in the Airspy,
RTLSDR, etc. radios). It covers something like 60 to 1700 MHz. Its
tunable-front end filter is only about 8 MHz wide which limits the
useful bandwidth even though the sample rate would support more. The
tuner is locked to the same clock as the ADC, so the frequency
accuracy/stability at VHF is the same as at HF.
Hope this helps, and also hope that someone with deeper technical
knowledge will correct any errors I've made above.
73,
John
----
On 7/26/24 20:02, 'Terry Bullett' via HamSCI wrote:
> I would like to know about the data rates and dropped samples too. As
> W0LEV points out the virtual audio cables are problematic (VBCAble being
> the worst I have tried, VAC being the best, for a reasonable license
> fee) But dropped audio packets are real and destroy the SFDR, phase
> noise and the entire statistical nature of the data.
>
> The performance of an Airsspy R2 at 10 MHz under USB is really limited
> because of the internal downconverter issues:
>
> here are all the warts when looking at 1420 MHz (hydrogen line) into a
> relatively dark sky. From Little Thompson Observatory:
>
>
>
>
> <
http://hamsci.org/hamsci-community-participation-guidelines>.
> ---
> You received this message because you are subscribed to the Google
> Groups "HamSCI" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
hamsci+un...@googlegroups.com
> <mailto:
hamsci+un...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/hamsci/3478f7d6-bf37-4606-8752-85cac9f47af8%40noaa.gov <
https://groups.google.com/d/msgid/hamsci/3478f7d6-bf37-4606-8752-85cac9f47af8%40noaa.gov?utm_medium=email&utm_source=footer>.