[hpsdr] Multiple Rx instances on HPSDR

[dave powis]

Thanks John,

At least this begins to answer my questions, although it also opens more up, of course!

From reading the HPSDR decsriptions, I was looking to try and use a Mercury Rx, with a Magister Interface on the 
Atlas backplane.  But if I read your reply correctly, the 8Rx functionality is only in Ozy at the moment - and it seems that it is this that is the issue of capacity, rather than the Mercury board?  Is it planned to migrate this across to the Magister FPGA at some point?  I assume that the FPGA's are re-programmable with new firmware?

In my application, the segments monitored will remain fixed once the system is running, so upstream control requirements will be minimal.  My objective at the moment is to identify the architecture for the SDR and the PC that will provide the necessary Rx's

Thanks & 73,
Dave




________________________________
From: John Melton <john.d.melton at googlemail.com>
To: dave powis <g4hup at btinternet.com>
Cc: hpsdr at lists.openhpsdr.org
Sent: Monday, 21 June, 2010 20:43:30
Subject: Re: [hpsdr] Multiple Rx instances on HPSDR

Hi Dave,

currently the FPGA code is only supporting 3 receivers.  The code needs
some more work to squeeze all the receivers in.  The Ozy code can
support 8 receivers.  I have only been able to test this on Mercury/Ozy.

Currently, PowerSDR does not support the multiple receivers.  There is
some work going on to put multiple receivers in KISS Console.

As far as I know only my Linux software will support multiple receivers.

The architecture is a server that interfaces to the HPSDR hardware and
splits out the RX I/Q data streams into separate UDP data streams with a
TCP control connection for sending frequency and control commands.  I
have a version of my ghpsdr software that is a receiver only client that
works with this server.  The server can run on the same machine as the
clients or on different machines.

I also have a dspserver that I am playing with for internet access to
the HPSDR hardware.  The dspserver acts as a client for a receiver
connected to the HPSDR hardware server.  It handles all the DSP
processing and allows an internet client (Java Applet) to connect to it
and it will stream audio and spectrum data to the client at a much lower
data rate than streaming I/Q data.  Currently it is about 100Kb/sec if
the spectrum is updated 15 times per second.  You can run multiple
dspservers, one for each receiver.

I am currently running the HPSDR server and 3 dspservers along with the
Apache web server on an Atom 330 system with 2GB memory.  It does not
seem to have any problems with running these.

I have 2 availabel on the internet and the third allows me to always
have access.

You can try this out by going to:

http://g0orx.homelinux.net/jmonitor.html

Let me know if you need any more information.

Regards,

John g0orx/n6lyt

On Mon, 2010-06-21 at 19:10 +0000, dave powis wrote:
> ***** High Performance Software Defined Radio Discussion List *****
> 
> Hi all,
> 
> I'm looking for a monitoring solution that will allow multiple
> independent Rx's to run on one piece of SDR hardware.  The
> descriptions for the HPSDR Mercury Rx and Hermes Tcvr seem to indicate
> that they can indeed operate up to 8 independent Rx's off a single
> common antenna input.  This will suit my application ideally.
> 
> However, what is not clear from the hardware descriptions is what the
> software requirements and PC limitations are.  
> What SDR apps will allow up to 8Rx's to be configured?  
> Or is it a case of running multiuple instances of the same SDR
> software simultaneously - eg PowerSDR?
> Are there any recommendations for the PC performance required to
> support this?
> 
> 
> Thanks for any help in answering these questions!
> 
> 73,
> Dave, G4HUP
> 
> 
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20100621/0b81159f/attachment-0004.htm>