Difference between revisions of "Ghpsdr3"

From HPSDRwiki
Jump to: navigation, search
(Architecture)
(move images closer to referring content)
Line 1: Line 1:
 +
===Server/Client version of ghpsdr===
 
[[Image:ghpsdr4.png|thumb|400px|right|Screenshot of the ghpsdr3 GUI on 20 meters. (Click to enlarge)]]
 
[[Image:ghpsdr4.png|thumb|400px|right|Screenshot of the ghpsdr3 GUI on 20 meters. (Click to enlarge)]]
 
[[Image:Screenshot-JMonitor - Mozilla Firefox.png|thumb|400px|right|Screenshot of the java in a web browser GUI on 40 meters. (Click to enlarge)]]
 
[[Image:Screenshot-JMonitor - Mozilla Firefox.png|thumb|400px|right|Screenshot of the java in a web browser GUI on 40 meters. (Click to enlarge)]]
[[Image:ghpsdr3.png|thumb|400px|right|Architecture of the server/dspserver/client configuration. (Click to enlarge)]]
 
 
===Server/Client version of ghpsdr===
 
 
 
'''ghpsdr3''' is a software defined radio server/client or server/dspserver/client format program written specifically for HPSDR by John Melton, G0ORX/N6LYT.  
 
'''ghpsdr3''' is a software defined radio server/client or server/dspserver/client format program written specifically for HPSDR by John Melton, G0ORX/N6LYT.  
  
Line 32: Line 29:
  
 
===Architecture===
 
===Architecture===
The image on this page illustrates the architecture of the ghpsdr3 software chain.  The software works with either the single receiver verilog code (Mercury 2.9) or the multiple receiver verilog code or (Mercury 3.0 experimental).  If Mercury 2.9 is install only one receiver can be accessed.  (Please not that there is a matching ozyfw-sdr1k.hex and Ozy_Janus.rbf file to go with the different versions of the Mercury code).
+
[[Image:ghpsdr3.png|thumb|400px|right|Architecture of the server/dspserver/client configuration. (Click to enlarge)]]
 +
The image illustrates the architecture of the ghpsdr3 software chain.  The software works with either the single receiver verilog code (Mercury 2.9) or the multiple receiver verilog code or (Mercury 3.0 experimental).  If Mercury 2.9 is install only one receiver can be accessed.  (Please not that there is a matching ozyfw-sdr1k.hex and Ozy_Janus.rbf file to go with the different versions of the Mercury code).
  
 
'''HPSDR''' box represented the hardware and the Mercury/Ozy,Penelope, Mercury/Magister,Penelope, or Mercury/OzyII,Penelope  
 
'''HPSDR''' box represented the hardware and the Mercury/Ozy,Penelope, Mercury/Magister,Penelope, or Mercury/OzyII,Penelope  

Revision as of 14:48, 7 August 2010

Server/Client version of ghpsdr

Screenshot of the ghpsdr3 GUI on 20 meters. (Click to enlarge)
Screenshot of the java in a web browser GUI on 40 meters. (Click to enlarge)

ghpsdr3 is a software defined radio server/client or server/dspserver/client format program written specifically for HPSDR by John Melton, G0ORX/N6LYT.

The software is being developed on the Ubuntu version of Linux (specifically version 9.10). The server and dspserver have been ported to run on Windows--

This version of ghpsdr3 allows for the server and client to be on the same machine or separate machines. The servers are written in C and run on linux machines. John and others are working on a full set of clients to run on multiple machines connecting to the servers through TCP/IP protocals.

To follow the development of this code look at John's Blog http://g0orx.blogspot.com/

SVN

The software is available from SVN and includes a precompiled executable in the bin directory. There are now a compiled version of the 64-bit linux version, 32-bit linux version and the MacOS version. The README explains how to compile the source if you wish to modify the code.

Since this code does not currently run on Windows here is the Linux svn command,

 svn co svn://64.245.179.219/svn/repos_sdr_hpsdr/trunk/N6LYT/ghpsdr3

Libraries

It uses a modifed version of DttSP that is ported from the Windows version. DttSP is built as a static library that is linked with the GUI code. The DttSP code is provided with the SVN distribution.

You will need a couple of libraries to run this code, they include:

  • libfftw3 - FFTW is a C subroutine library for computing the discrete Fourier transform (DFT) in one or more dimensions, of arbitrary input size, and of both real and complex data (as well as of even/odd data, i.e. the discrete cosine/sine transforms or DCT/DST).
  • libgtk2 - GTK+ is a highly usable, feature rich toolkit for creating graphical user interfaces which boasts cross platform compatibility and an easy to use API.
  • libusb-1.0 - libusb is an open source library that allows you to communicate with USB devices from userspace.

These can be obtain with your package installer.

Architecture

Architecture of the server/dspserver/client configuration. (Click to enlarge)

The image illustrates the architecture of the ghpsdr3 software chain. The software works with either the single receiver verilog code (Mercury 2.9) or the multiple receiver verilog code or (Mercury 3.0 experimental). If Mercury 2.9 is install only one receiver can be accessed. (Please not that there is a matching ozyfw-sdr1k.hex and Ozy_Janus.rbf file to go with the different versions of the Mercury code).

HPSDR box represented the hardware and the Mercury/Ozy,Penelope, Mercury/Magister,Penelope, or Mercury/OzyII,Penelope

Link between HPSDR and Server uses the communication protocol documented in USB Protocol v1.27 at the link on this page or in the SVN in the Documentation directory.

Server box is a software multiplexer. It takes the multiple receiver communication protocol and divides it in to single receiver channels.

Link between Server and Receiver clients output is the same IQ signal format as the single receiver USB format except the data is sent over UDP link. The commands are handled as TCP protocol format to allow acknowledgement of the command.

Receiver Clients can be in many forms and it was designed to foster experimentation. The first client is the same interface used in ghpsdr. The second interface is a simple waterfall called monitor used to keep track of activity on other bands. Both of these programs the DSP code in in the GUI program. These programs usually will be with a short distance of the server as the bandwidth is quite large for most home network connections.

In an effort to demonstrate world wide access to your receiver a third approach was developed. In this method the receiver client is a dspserver that take the output of the server and creates a low bandwidth version of the spectrum in 8 bit data, the audio data 8-bit ALAW audio format at only 480 sample size at 10 times a second. The dspserver also accepts commands from the client. To run multiple low bandwidth clients you must run a separate copy of dspserver for each client.

The base code for the current jmonitor is written in java. It can be run as a program on a computer or within a webbrowser. This code has also been ported to the iphone and Android platforms so that you can monitor your radios on the go. At the 2010 Dayton Hamvention, John Melton monitored his receiver in England from the TAPR booth on the Hamvention floor.


Links to other pages: