[hpsdr] New Mercury block diagram

[CHARLES HUTTON]

>Date: Tue, 17 Apr 2007 09:17:44 +0200
>From: "Henry Vredegoor" <henry.vredegoor at gmail.com>
>Subject: [hpsdr] New Mercury block diagram
>To: <hpsdr at hpsdr.org>
>Message-ID: <019801c780c0$7f2cb120$6402a8c0 at Blues>
>Content-Type: text/plain; charset="us-ascii"
>
>Hi All, Phil & Phil,
>
>
>When studying the new block diagram of Mercury on the Wiki pages, I noticed
>that the configuration of the analog HF input path has changed.
>
>Would it be an idea to bring the input to the ADC out on a separate
>connector, bypassing the on-board filtering, HF amps etc. and enabling it 
>to
>be used as a "bare"  ADC board for e.g.. under sampling of 2 meter (0,7 cm)
>VHF etc. (The input bandwidth of the ADC going up to 700 MHz) or with a
>complete different set of HF amps, filters etc?
>Maybe include a (bypassable) 1:4 broadband transformer to step up from 50 
>to
>the ADC's 200 Ohm impedance?
>
>Sorry if this is already mentioned before, could not find it in the
>archives.
>
>73's,
>
>Henry.
>


Thanks for pointing out the new diagram, Henry. I hadn't been aware of it.

I have a request to make for the block diagrams. It really doesn't help me 
too much to just see a block labelled "FPGA". Could we make the diagram more 
of a functional diagram? I'd love to see labels like "programmable 
decimation (x to y)", CIC filter width, compensation filter, etc.

It would be good to know what aspects are controllable via the Atlas bus 
from whatever is hooked to the USB port on other cards.

Bottom line: it's tough to figure out what the system is actually doing from 
the block diagram.


Chuck



 1176834031.0