Hermes - Revision history

Frohro: /* dspserver */

2013-09-24T04:03:59Z

dspserver

← Older revision		Revision as of 04:03, 24 September 2013
Line 69:		Line 69:
	dspserver: unrecognized option '--?'		dspserver: unrecognized option '--?'
	Usage:		Usage:
	dspserver --server 0.0.0.0 (default 127.0.0.1)		dspserver --receiver (0-3)
			--server 0.0.0.0 (default 127.0.0.1)
	--soundcard (machine dependent)		--soundcard (machine dependent)
	--offset 0		--offset 0

Frohro: /* dspserver */

2013-09-24T03:59:33Z

dspserver

← Older revision		Revision as of 03:59, 24 September 2013
Line 69:		Line 69:
	dspserver: unrecognized option '--?'		dspserver: unrecognized option '--?'
	Usage:		Usage:
	dspserver ~~--receivers N (default 1)~~		dspserver --server 0.0.0.0 (default 127.0.0.1)
	--server 0.0.0.0 (default 127.0.0.1)
	--soundcard (machine dependent)		--soundcard (machine dependent)
	--offset 0		--offset 0

Frohro at 17:00, 26 August 2013

2013-08-26T17:00:57Z

← Older revision		Revision as of 17:00, 26 August 2013
Line 41:		Line 41:

	In this case either eth9 or wlan2 could be used because my Hermes is on the 192.168.2.x network. The eth9 is an ethernet connection and wlan2 is a wireless connection.		In this case either eth9 or wlan2 could be used because my Hermes is on the 192.168.2.x network. The eth9 is an ethernet connection and wlan2 is a wireless connection.
			Other hpsdr-server options can be seen by using the --? option.
			$ hpsdr-server --?
			hpsdr-server: unrecognized option '--?'
			Usage:
			server --receivers N (default 1)
			--samplerate 48000\|96000\|192000\|384000
			--dither off\|on
			--random off\|on
			--preamp off\|on
			--10mhzsource atlas\|penelope\|mercury
			--122.88mhzsource atlas\|penelope\|mercury
			--micsource janus\|penelope
			--class other\|E
			--timing 1
			--metis
			--interface if
			--fpga <file name>
			--ozyhex <file name>
			--hermes <power 0-255>

	====dspserver====		====dspserver====

Frohro at 16:57, 26 August 2013

2013-08-26T16:57:13Z

@@ Line 1: / Line 1: @@
-Thanks to Andrea for providing the Hermes backend for ghpsdr3-alex.  Here is how you start the server from the command line.
+Thanks to Andrea for providing the Hermes backend for ghpsdr3-alex.
   $ hpsdr-server --samplerate 48000 --hermes 16 --interface eth2
@@ Line 38: / Line 41: @@
 In this case either eth9 or wlan2 could be used because my Hermes is on the 192.168.2.x network.  The eth9 is an ethernet connection and wlan2 is a wireless connection.

Frohro at 16:29, 26 August 2013

2013-08-26T16:29:26Z

← Older revision		Revision as of 16:29, 26 August 2013
Line 18:		Line 18:
	RX bytes:881124281 (881.1 MB) TX bytes:3414696100 (3.4 GB)		RX bytes:881124281 (881.1 MB) TX bytes:3414696100 (3.4 GB)
	Interrupt:20 Memory:f6900000-f6920000		Interrupt:20 Memory:f6900000-f6920000

	lo Link encap:Local Loopback		lo Link encap:Local Loopback
	inet addr:127.0.0.1 Mask:255.0.0.0		inet addr:127.0.0.1 Mask:255.0.0.0
Line 27:		Line 27:
	collisions:0 txqueuelen:0		collisions:0 txqueuelen:0
	RX bytes:4143306543 (4.1 GB) TX bytes:4143306543 (4.1 GB)		RX bytes:4143306543 (4.1 GB) TX bytes:4143306543 (4.1 GB)

	wlan2 Link encap:Ethernet HWaddr 18:3d:a2:10:95:80		wlan2 Link encap:Ethernet HWaddr 18:3d:a2:10:95:80
	inet addr:192.168.2.250 Bcast:192.168.2.255 Mask:255.255.255.0		inet addr:192.168.2.250 Bcast:192.168.2.255 Mask:255.255.255.0

Frohro: Created page with "Thanks to Andrea for providing the Hermes backend for ghpsdr3-alex. Here is how you start the server from the command line. $ hpsdr-server --samplerate 48000 --hermes 16 --..."

2013-08-26T16:28:48Z

Created page with "Thanks to Andrea for providing the Hermes backend for ghpsdr3-alex. Here is how you start the server from the command line. $ hpsdr-server --samplerate 48000 --hermes 16 --..."

New page

Thanks to Andrea for providing the Hermes backend for ghpsdr3-alex. Here is how you start the server from the command line.

$ hpsdr-server --samplerate 48000 --hermes 16 --interface eth2

Note:
*you can use 48000, 96000, 192000, or 384000 for the --samplerate parameter.
*the --hermes parameter is how much power Hermes will put out on transmit. The values go from 0 to 255.
*the --interface parameter is the network interface that is connected to the same local area network that Hermes is connected to. It may be eth1, eth2, etc. or wlan1, wlan2, etc. You can figure out what it is by using the ifconfig command at the terminal as follows:

$ ifconfig
eth9 Link encap:Ethernet HWaddr 5c:26:0a:45:28:7b
inet addr:192.168.2.157 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::5e26:aff:fe45:287b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1877498 errors:0 dropped:0 overruns:0 frame:0
TX packets:2572794 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:881124281 (881.1 MB) TX bytes:3414696100 (3.4 GB)
Interrupt:20 Memory:f6900000-f6920000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:7758949 errors:0 dropped:0 overruns:0 frame:0
TX packets:7758949 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4143306543 (4.1 GB) TX bytes:4143306543 (4.1 GB)

wlan2 Link encap:Ethernet HWaddr 18:3d:a2:10:95:80
inet addr:192.168.2.250 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::1a3d:a2ff:fe10:9580/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3622385 errors:0 dropped:2 overruns:0 frame:0
TX packets:1970372 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4139564914 (4.1 GB) TX bytes:1254030073 (1.2 GB)

In this case either eth9 or wlan2 could be used because my Hermes is on the 192.168.2.x network. The eth9 is an ethernet connection and wlan2 is a wireless connection.