Red Pitaya Remote Receiver Station - Versionsgeschichte

Dl8rds: /* Without the crappy Chinese preamps */

2019-04-20T19:36:52Z

‎Without the crappy Chinese preamps

Dl8rds: /* Images */

2019-04-07T15:47:47Z

‎Images

Dl8rds: /* SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya */

2019-04-07T15:44:02Z

‎SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya

Dl8rds: /* SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya */

2019-04-07T15:23:02Z

‎SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya

Dl8rds: /* SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya */

2019-04-07T15:22:03Z

‎SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya

Änderungen zeigen

Dl8rds: /* SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya */

2019-04-07T15:17:27Z

‎SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya

Dl8rds: /* UNSUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya */

2019-04-07T15:08:06Z

‎UNSUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya

Dl8rds: /* Getting OpenWebRX to connect to the Red Pitaya */

2019-04-07T15:07:40Z

‎Getting OpenWebRX to connect to the Red Pitaya

Dl8rds am 7. April 2019 um 15:06 Uhr

2019-04-07T15:06:48Z

Dl8rds am 4. September 2017 um 08:02 Uhr

2017-09-04T08:02:45Z

← Nächstältere Version		Version vom 20. April 2019, 19:36 Uhr
Zeile 599:		Zeile 599:

	(to be added soon)		(to be added soon)
		+
		+	=== Another Red Pitaya receiver in preparation... ===
		+
		+	[[Image:2019-04-20-RedPitaya-DL8RDS.jpg\|400px]]

@@ Zeile 584: / Zeile 584: @@
 == Images ==
 [[Image:2017-07-23-RedPitaya1.jpg|400px]]
@@ Zeile 593: / Zeile 595: @@
 [[Image:2017-07-23-RedPitaya5.jpg|400px]]
 [[Image:2017-07-23-RedPitaya6.jpg|400px]]

← Nächstältere Version		Version vom 7. April 2019, 15:44 Uhr
Zeile 550:		Zeile 550:

	Besides that, accessing the Red Pitaya is also quite simple. We are also using GQRX to connect to it. See below.		Besides that, accessing the Red Pitaya is also quite simple. We are also using GQRX to connect to it. See below.
		+
		+	Here is how the perspective on the processes looks like:
		+
		+	<pre>
		+	root 2883 1 0 Mar20 ? 00:00:07 tmux new -d -s openwebrx-session bash -c "cd /usr/local/git/openwebrx; ./openwebrx.py; bash"
		+	root 2884 2883 0 Mar20 pts/0 00:00:00 bash -c cd /usr/local/git/openwebrx; ./openwebrx.py; bash
		+	root 2886 2884 0 Mar20 pts/0 00:52:39 /usr/bin/python2 ./openwebrx.py
		+	root 2887 1 0 Mar20 ttyS0 00:00:00 /sbin/agetty -L 115200 ttyS0 linux
		+	root 2888 1 0 Mar20 tty1 00:00:00 /sbin/agetty --noclear tty1 linux
		+	root 2891 2 0 Mar20 ? 00:00:13 [kworker/u9:2]
		+	root 2904 2886 0 Mar20 pts/0 00:00:00 /bin/sh -c ./osmocat.py --args redpitaya=44.225.41.10:1001 --auto --freq 7030000 --rate 500000\| nmux --bufsize 126976 --bufcnt 394 --port 4951
		+	root 2905 2904 4 Mar20 pts/0 19:37:29 /usr/bin/python2.7 ./osmocat.py --args redpitaya=44.225.41.10:1001 --auto --freq 7030000 --rate 500000
		+	root 2906 2904 1 Mar20 pts/0 05:49:09 nmux --bufsize 126976 --bufcnt 394 --port 4951 --address 127.0.0.1
		+	root 2912 2886 0 Mar20 pts/0 00:00:00 /bin/sh -c nc -v 127.0.0.1 4951 \| csdr fft_cc 4096 55555 \| csdr logpower_cf -70 \| csdr fft_exchange_sides_ff 4096 \| csdr compress_fft_adpcm_f_u
		+	root 2913 2912 2 Mar20 pts/0 09:20:43 nc -v 127.0.0.1 4951
		+	root 2914 2912 2 Mar20 pts/0 10:31:10 csdr fft_cc 4096 55555
		+	root 2915 2912 0 Mar20 pts/0 01:11:13 csdr logpower_cf -70
		+	root 2916 2912 0 Mar20 pts/0 00:34:13 csdr fft_exchange_sides_ff 4096
		+	root 2917 2912 0 Mar20 pts/0 00:40:53 csdr compress_fft_adpcm_f_u8 4096
		+	</pre>

	=== Observations ===		=== Observations ===

@@ Zeile 549: / Zeile 549: @@
 </pre>
+Besides that, accessing the Red Pitaya is also quite simple. We are also using GQRX to connect to it. See below.
 === Observations ===

← Nächstältere Version		Version vom 7. April 2019, 15:17 Uhr
Zeile 239:		Zeile 239:


		+
		+	=== SUCCESSFUL: Getting the interface right ===
		+
		+	After the lacking success of the above approach, and after around a year of inactivity I finally succeeded after Johannes DO6JS helped me to find out the real tricks.
		+
		+	==== Running the right firmware ====
		+
		+	The correct firmware that's required to run on the RedPitaya is Pavel Demin's SDR transceiver code.
		+
		+	<pre>
		+	root@rp-fxxxxx:/etc# cat rc.local
		+	#!/bin/sh -e
		+	#
		+	# rc.local
		+	#
		+	# This script is executed at the end of each multiuser runlevel.
		+	# Make sure that the script will "exit 0" on success or any other
		+	# value on error.
		+	#
		+	# In order to enable or disable this script just change the execution
		+	# bits.
		+	#
		+	# By default this script does nothing.
		+
		+
		+	dir=/opt/redpitaya/www/apps/sdr_transceiver
		+	cat $dir/sdr_transceiver.bit > /dev/xdevcfg
		+	. $dir/start.sh
		+
		+	exit 0
		+	</pre>
		+
		+	This file will start an FPGA data interface on the port 1001, whenever the Red Pitaya boots up.
		+
		+	<pre>
		+	root@rp-fxxxxx:/etc# netstat -tulpen
		+	Active Internet connections (only servers)
		+	Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
		+	tcp 0 0 0.0.0.0:1001 0.0.0.0:* LISTEN 0 4679 1609/sdr-transceive
		+	tcp 0 0 0.0.0.0:1002 0.0.0.0:* LISTEN 0 5153 1610/sdr-transceive
		+	</pre>
		+
		+	After a reboot, the Pitaya should come up and have the sdr transceiver up and running. This is all that needs to be done to the Red Pitaya.

	=== SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya ===		=== SUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya ===
		+
		+	On the Raspberry Pi, accessing the Red Pitaya is also quite simple.
		+
		+
		+	=== Observations ===
		+
		+	It is obvious, that the Red Pitaya cannot serve different clients on different frequencies and different sampling speeds at the same time. So it is necessary to make sure that only one client connects to it simultaneously.
		+
		+	It is also obvious that modifying the operation mode in the Pitaya's web interface is also not beneficial. For this reason it is a good piece of advice to ban other users from accessing it. I decided to use a firewall rule in my station's router to keep unwanted users out.
		+
		+	Accessing it with GQRX is really fantastic and will give us a great RF insight.
		+
		+	The configuration of the GQRX address therefore is simple:
		+
		+	[[Image:2019-04-07-gqrx-config.png\|600px]]

	== Images ==		== Images ==

@@ Zeile 237: / Zeile 237: @@
   WARNING: sync read failed. -5
   WARNING: sync read failed. -5
 == Images ==

@@ Zeile 194: / Zeile 194: @@
     remote:driver = redpitaya
-=== Getting OpenWebRX to connect to the Red Pitaya ===
+=== UNSUCCESSFUL: Getting OpenWebRX to connect to the Red Pitaya ===
 Since we now can access the Pitaya via a standard interface, it's time to configure OpenWebRX accordingly:

@@ Zeile 8: / Zeile 8: @@
 The final goal is to have a recording / monitoring receiver that can fully be remote-controlled. The Pitaya can be switched on and off with the remote control switch described here: [[A relay box for control from Linux]] and [[A remote Ethernet switch for my relay box]]
 == Component List ==
@@ Zeile 75: / Zeile 77: @@
-=== Getting the interface right ===
+=== UNSUCCESSFUL: Getting the interface right ===
 Firstly, unless there is some special configuration on the Pitaya, you should be able to detect ot from another machine.

← Nächstältere Version		Version vom 4. September 2017, 08:02 Uhr
Zeile 41:		Zeile 41:

	== Software Stuff ==		== Software Stuff ==
		+
		+	=== Accessing the amplifier ===
		+
		+	First detect the preamp:
		+
		+	i2cdetect -y -r 0
		+	0 1 2 3 4 5 6 7 8 9 a b c d e f
		+	00: -- -- -- -- -- -- -- -- -- -- -- -- --
		+	10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
		+	20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
		+	30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
		+	40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
		+	50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
		+	60: 60 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
		+	70: -- -- -- -- -- -- -- --
		+
		+	60h is the address of the preamp.
		+
		+	Now read out the dac register as word:
		+
		+	i2cget -y 0 0x60 0 w
		+	0x80c0
		+
		+	Set the amplification to max:
		+
		+	i2cset -y 0 0x60 0 0xC0 0x0f 0xff i
		+
		+	Set the amplification to min:
		+
		+	i2cset -y 0 0x60 0 0xC0 0x0 0x0 i
		+
		+	Values between 0 and 4095 are possible. Convert to hex.
		+

	=== Getting the interface right ===		=== Getting the interface right ===