hacktv icon indicating copy to clipboard operation
hacktv copied to clipboard

SoapySDR?

Open neo7530 opened this issue 6 years ago • 8 comments

Hi, i have an adalm-pluto now and would like to use it with hacktv. How is the syntax for using it?

neo7530 avatar Jan 06 '20 15:01 neo7530

At a minimum:

$ hacktv -o soapysdr

Assumes you have the soapysdr driver installed correctly.

fsphil avatar Jan 06 '20 16:01 fsphil

yep, that is okay. didn't know the device-args :( "tried -o soapysdr="device=plutosdr,ip=192.168.2.1" so hacktv will run, but no Output from Pluto...

neo7530 avatar Jan 06 '20 18:01 neo7530

You may need to select an antenna. I don't have one so I can't really help - I do believe it works though.

fsphil avatar Jan 06 '20 22:01 fsphil

Any progress?

fsphil avatar Jan 13 '20 14:01 fsphil

The pluto will be found if I start hacktv as root, but it won't transmit anything. I can see the frequency setup in spectrum monitor via hackrf, then no more carrier in rf spectrum.

neo7530 avatar Jan 16 '20 08:01 neo7530

Edit: I forgot to mention. The make file does not seem to work correctly. I had to manually comment out the SoapySDR check on line 9 and 10, to force compilation for SoapySDR. #SOAPYSDR := $(shell $(PKGCONF) --exists SoapySDR && echo SoapySDR) #ifeq ($(SOAPYSDR),SoapySDR)

After that I had some success using hacktv with the plutosdr. I've managed to transmit a glitchy NTSC stream on UHF channel 28 with the following:

hacktv -o soapysdr -f 555250000 -s 1000000 -v -m m -g 89 test

similarly, I get a glitchy stream with a test.mkv video:

hacktv -o soapysdr -f 555250000 -s 1000000 -v -m m -g 89 test.mkv

Make sure that the plutosdr registers with SoapySDR, it should show up with the following command: SoapySDRUtil --probe

I've tried playing around with a few sample rates and it seems that the plutosdr only works with HackTV at 1Msps. The plutosdr should work all the way up to 10Msps. Do you have any thought on why this might be? Also do you know what the limit is for reliable NTSC replay?

fitzdoingprojects avatar Jan 18 '20 23:01 fitzdoingprojects

The soapysdr build checks did work for me running ubuntu 18.04 (with all the required soapy tools and dev libraries installed). My experiences with the soapysdr (running with HackRF and LimeSDR) is that it takes an extra hit on the CPU (uses 1 thread) compared to when I run it with a HackRF connected, so maybe it is cpu-related on your machine as well. I was using a Intel i5 8500 CPU at the time, and using soapy with both devices I had 100% load on one thread and a glitchy image. Hackrf directly had <100% load and a clear image.

Extra parameters (for me: switching between devices) worked for me with the following syntax -o soapysdr:driver=lime.

sidenote: my experiences are with the hacktv sources of 2-3 months ago.

vdveer avatar Feb 15 '20 15:02 vdveer

It sounds like the soapysdr output needs to be in its own thread. I had naively thought it wouldn't need to be.

fsphil avatar Feb 15 '20 23:02 fsphil