The SVN (need to show link) has the following folders:
<pre>
Folder Contents
bin Executables and all files needed to run
dist java files for jmonitor (you'll need to have installed java)
dspserver source for dspserver, with solution/project files
DttSP source for DSP package, with solution/project files to create .dll
LoadMercuryFirmware all files needed to load Mercury FPGA with V3.0
server source for server, with VS2003 solution/project files
</pre>
Two of the parts of John Melton's ghpsdr3 have been ported to Windows (tested on XP 32 bit)
The two pieces are "server" and "dspserver".

These two, with Mercury FPGA version 3.0 and the corresponding Ozy code (version 1.8),
provide for four simulteneous independent receivers for a single Mercury board, using John's
jmonitor as the (minimal) receiver graphical user interface. The controls available for
each receiver are fewer than with PowerSDR or KK, but are quite adequate for monitoring
up to four 96kHz segments in the frequency range 0 to 55 MHz simultaneously.

No transmit capability is provided.

Both parts are written in pure C (no C++). The files include project (solution) files for
Visual Studio 2003. You'll probably have no trouble using VS2005 or VS2008.
I've added #ifdef ... #endif so that (hopefully) the same code may be compiled on Windows
and on Linux. Once any problems have been ironed out, the merged code will be placed in the
SVN trunk, rather than branch, so that further development will simultaneously apply to both
Windows and Linux.

In the future, additional options will be explored / implemented. These include using the fully-
featured ghpsdr3 receiver user interface, other receiver interfaces, connections to digital mode
software, and special communication software, such as WSPR. Transmit capability may also be possible.
(Of course WSPR needs to transmit. I'd hope that one could run WSPR on four bands simultaneously,
with the software setting Penelope frequency as needed.)

The server part loads Ozy FX2 and FPGA via the USB, sends I & Q samples to dspservers 0 thru 3,
and sends demodulated audio (for receiver 0 only) back to Ozy and Mercury. Each jmonitor sends
demodulated audio to computer's sound card. When more than one receiver is active, the sound
card output is the sum of audio from all active receivers. If you want to listen to only one,
reduce the AFGain to zero on other instances of jmonitor. The server does not read the 55 MHz wide
spectrum samples from Ozy / Mercury (USB endpoint 4).

Each functional receiver uses its own instances of dspserver and jmonitor. dspserver provides the
passband filtering, demodulation, AGC, and noise reduction.

server and dspserver are launched from a command window ("DOS window"), and each is started with
some command-line arguments, or options.

For the server, the options are--
<pre>
receivers 1, 2, 3, or 4 the number of simultaneous receivers to be supported
samplerate # one of 48000, 96000, 192000 (only tested with 96000)
dither on / off Setting for Mercury ADC
random on / off Setting for Mercury ADC
preamp on / off Setting for Mercury
10mhzsource atlas / penelope / mercury
122.8mhzsource penelope / mercury
micsource penelope / janus
class other / E
timing

The default settings are
receivers 1
samplerate 96000
dither off
random off
preamp off
10mhzsource mercury
122.88mhzsource mercury
micsource penelope
class other
</pre>

You only need to specify the options whose values need to be different from the defaults.

For the dspserver, the options are--
<pre>
dspserver options:
soundcard SANTA_CRUZ, AUDIGY_2_ZS, MP3_PLUS, EXTIGY, DELTA_44, FIREBOX, EDIROL_FA_66, HPSDR
receiver 0 - 3
server IP address
offset ?

default values:
soundcard HPSDR
server 127.0.0.1 (this is "localhost")
receiver 0
offset 0
</pre>

To make it easy to launch multiple receivers, make a folder with a short path name, such as
C:\MultiRx

Into this folder place the following--
<pre>
libfftw3f-3.dll
pthreadVC2.dll
jmonitor.jar
ozyfw-sdr1k.hex
Ozy_Janus.rbf
server.exe
dspserver.exe
folder "lib" from the java dist folder
</pre>

Here's how to start the system--
<pre>
First command window
cd to the folder containing the required files and type--
server --receivers 4

2nd command window
dspserver --receiver 0

3rd command window
java -jar "jmonitor.jar" --server 127.0.0.1 --receiver 0
</pre>

Now you have one receiver running.

To use more than one simultaneous receiver,
* When launching server, use a value greater than 1 for the number of receivers.
* Launch multiple copies of dspserver and jmonitor, each from their own command window,
using different receiver numbers--ie 0, 1, 2, 3
(Only one instance of server is needed--it supplies connection to the hardware for
all receivers.)

With 4 receivers running, you'll have 9 command windows open.

When server starts it says--
(socket numbers and buffer addresses will be different on your system):
<pre>
Listening for TCP connections on port 11000
(a few seconds delay while Ozy FX2 and FPGA are loaded)
... (hex dumps of 9 USB frames)
server configured for 4 receivers at 96000
Ozy Software version 18
Mercury Software version 30

client_socket 1832
client connected 127.0.0.1:12000
client connected: 127.0.0.1:12000
parse_command(Rx-842150451): 'attach 0'
response(Rx0): OK 96000'
parse_command(Rx0): 'start iq 13000'
response(Rx0): 'OK'
audio_thread port=15000
listening for rx 0 audio on port 15000
</pre>

When dspserver starts it says--
<pre>
hHPSDR rx 0 (Version 0.6)
getSoundcardID: HPSDR id=8
setSoundcard: 8
setSoundcard -11 000000 -25 000000
setup_system_audio: sdr-5044-0
setup_system_audio: sdr-5044-1
client_init audio_buffer_size=2000 audio_buffer=9736336
client_thread
client_thread: listening on port 8000
ozy_init: command bound to port 12000 socket 1808
ozy_init: server 127.0.0.1
connect: sampleRate=96000
setSpeed 1
ozy_init: iq bound to port 13000 socket=1776
iq_thread: socket 1784
output_sample_increment=2
</pre>

(when jmonitor for Rx 0 starts, dspserver says:)
<pre>
26/06/2010 23:48:29 RX0: client connection from 127.0.0.1:2995
client message: setFrequency 7048000
client message: setMode 0
client message: setFilter -2850 -150
client message: SetRXOutputGain 30
client message: start AudioStream 480
</pre>

As you start additional receivers, and make changes to the state of each of the receivers,
you'll see more output from server and the dspservers.

Please post your comments and questions to the openhpsdr email reflector.

Multiple independent receivers - how to set up on Windows

2010-07-16T15:27:28Z

WA8YWQ: Added page with information about running ghpsdr3 on Windows

<pre>
Folder Contents
bin Executables and all files needed to run
server source for server, with VS2003 solution/project files
dspserver source for dspserver, with solution/project files
dist java files for jmonitor (you'll need to have installed java)
</pre>
Two of the parts of John Melton's ghpsdr3 have been ported to Windows (tested on XP 32 bit)
The two pieces are "server" and "dspserver".

These two, with Mercury FPGA version 3.0 and the corresponding Ozy code (version 1.8),
provide for four simulteneous independent receivers for a single Mercury board, using John's
jmonitor as the (minimal) receiver graphical user interface. The controls available for
each receiver are fewer than with PowerSDR or KK, but are quite adequate, for monitoring
up to four 96kHz segments in the frequency range 0 to 55 MHz simultaneously.

No transmit capability is provided.

Both parts are written in pure C (no C++). The files include project (solution) files for
Visual Studio 2003. You'll probably have no trouble using VS2005 or VS2008.
I've added #ifdef ... #endif so that (hopefully) the same code may be compiled on Windows
and on Linux. Once any problems have been ironed out, the merged code will be placed in the
SVN trunk, rather than branch, so that further development will simultaneously apply to both
Windows and Linux.

In the future, additional options will be explored / implemented. These include using the fully-
featured ghpsdr3 receiver user interface, other receiver interfaces, connections to digital mode
software, and special communication software, such as WSPR. Transmit capability may also be possible.
(Of course WSPR needs to transmit. I'd hope that one could run WSPR on four bands simultaneously,
with the software setting Penelope frequency as needed.)

The server part loads Ozy FX2 and FPGA via the USB, sends I & Q samples to dspservers 0 thru 3,
and sends demodulated audio (for receiver 0 only) back to Ozy and Mercury. Each jmonitor sends
demodulated audio to computer's sound card. When more than one receiver is active, the sound
card output is the sum of audio from all active receivers. If you want to listen to only one,
reduce the AFGain to zero on other instances of jmonitor. The server does not read the 55 MHz wide
spectrum samples from Ozy / Mercury (USB endpoint 4).

Each functional receiver uses its own instances of dspserver and jmonitor. dspserver provides the
passband filtering, demodulation, AGC, and noise reduction.

server and dspserver are launched from a command window ("DOS window"), and each is started with
some command-line arguments, or options.

For the server, the options are--
<pre>
receivers 1, 2, 3, or 4 the number of simultaneous receivers to be supported
samplerate # one of 48000, 96000, 192000 (only tested with 96000)
dither on / off Setting for Mercury ADC
random on / off Setting for Mercury ADC
preamp on / off Setting for Mercury
10mhzsource atlas / penelope / mercury
122.8mhzsource penelope / mercury
micsource penelope / janus
class other / E
timing

The default settings are
receivers 1
samplerate 96000
dither off
random off
preamp off
10mhzsource mercury
122.88mhzsource mercury
micsource penelope
class other
</pre>

You only need to specify the options whose values need to be different from the defaults.

For the dspserver, the options are--
<pre>
dspserver options:
soundcard SANTA_CRUZ, AUDIGY_2_ZS, MP3_PLUS, EXTIGY, DELTA_44, FIREBOX, EDIROL_FA_66, HPSDR
receiver 0 - 3
server IP address
offset ?

default values:
soundcard HPSDR
server 127.0.0.1 (this is "localhost")
receiver 0
offset 0
</pre>

To make it easy to launch multiple receivers, make a folder with a short path name, such as
C:\MultiRx

Into this folder place the following--
<pre>
libfftw3f-3.dll
pthreadVC2.dll
jmonitor.jar
ozyfw-sdr1k.hex
Ozy_Janus.rbf
server.exe
dspserver.exe
folder "lib" from the java dist folder
</pre>

Here's how to start the system--
<pre>
First command window
cd to the folder containing the required files and type--
server --receivers 4

2nd command window
dspserver --receiver 0

3rd command window
java -jar "jmonitor.jar" --server 127.0.0.1 --receiver 0
</pre>

Now you have one receiver running.

To use more than one simultaneous receiver,
* When launching server, use a value greater than 1 for the number of receivers.
* Launch multiple copies of dspserver and jmonitor, each from their own command window,
using different receiver numbers--ie 0, 1, 2, 3
(Only one instance of server is needed--it supplies connection to the hardware for
all receivers.)

With 4 receivers running, you'll have 9 command windows open.

When server starts it says--
(socket numbers and buffer addresses will be different on your system):
<pre>
Listening for TCP connections on port 11000
(a few seconds delay while Ozy FX2 and FPGA are loaded)
... (hex dumps of 9 USB frames)
server configured for 4 receivers at 96000
Ozy Software version 18
Mercury Software version 30

client_socket 1832
client connected 127.0.0.1:12000
client connected: 127.0.0.1:12000
parse_command(Rx-842150451): 'attach 0'
response(Rx0): OK 96000'
parse_command(Rx0): 'start iq 13000'
response(Rx0): 'OK'
audio_thread port=15000
listening for rx 0 audio on port 15000
</pre>

When dspserver starts it says--
<pre>
hHPSDR rx 0 (Version 0.6)
getSoundcardID: HPSDR id=8
setSoundcard: 8
setSoundcard -11 000000 -25 000000
setup_system_audio: sdr-5044-0
setup_system_audio: sdr-5044-1
client_init audio_buffer_size=2000 audio_buffer=9736336
client_thread
client_thread: listening on port 8000
ozy_init: command bound to port 12000 socket 1808
ozy_init: server 127.0.0.1
connect: sampleRate=96000
setSpeed 1
ozy_init: iq bound to port 13000 socket=1776
iq_thread: socket 1784
output_sample_increment=2
</pre>

(when jmonitor for Rx 0 starts, dspserver says:)
<pre>
26/06/2010 23:48:29 RX0: client connection from 127.0.0.1:2995
client message: setFrequency 7048000
client message: setMode 0
client message: setFilter -2850 -150
client message: SetRXOutputGain 30
client message: start AudioStream 480
</pre>

As you start additional receivers, and make changes to the state of each of the receivers,
you'll see more output from server and the dspservers.

Please post your comments and questions to the openhpsdr email reflector.

Ghpsdr3

2010-07-16T14:52:27Z

WA8YWQ:

[[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: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.

The software is being developed on the Ubuntu version of Linux (specifically version 9.10).

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===
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).

'''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:

* [[ghpsdr3 FAQ|Frequently Asked Questions]]
* [http://www.tapr.org/pdf/2010-G0ORX-N6LYT-Putting-HPSDR-on-Internet.pdf John Melton's 2010 Dayton presentation on ghpsdr3]
* [http://www.n9vv.com/N6LYT-Online-Mercury-Receiver.pdf Ken Hoppers N9VV online documentation of the online multi-receiver setup.]
* [[How to set up on Windows]]
* Features List [[ghpsdr3 Requests|requests]]
* Programmers Notes
* - [[ghpsdr3 Ports|Ports]]
* Known [[ghpsdr3 Bugs|bugs]]

[[Category:ghpsdr3| ]]