This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-sdr@lists.osmocom.org/.
Simon PurplePlaNET simon at purpleplanet.orgAh, OK - I've got you. You also need to run the script once you have launched rtl_tcp using the command in step 3) below. The simplest way to do this would be to add a step: 6) Sign in to rPi with a new terminal session, leaving the old one open for now. cd to the directory where you created the script and then run it using this command: ./rtl-robot (or whatever you called the script) You could run the script from the same terminal that you launched rtl_tcp from if you used & to force rtl_tcp to detach from the console and run in the background. I'll edit the comments on the script to make that a bit clearer... Thanks! Simon ----- Original Message ----- From: "Favati" <smile_k at libero.it> To: osmocom-sdr at lists.osmocom.org Sent: Saturday, 11 May, 2013 20:14:36 GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: Raspberry Pi based remote SDR head > Could you describe exactly the steps you have taken? 1) installed wiringpi (and tested as described on the developer site) 2) created your script 3) launched this command: stdbuf --output=0 rtl_tcp -a 192.168.2.15 -p 1234 > rtl.data 4) used sdrsharp to connect to my raspberry (192.168.2.15, and it connect ok, i can use sdrsharp ok) 5) nothing is displayed on the console of my raspy except the first 2 lines of rtl_tcp output The rtl_data is created ok and looking inside that file i can see the normal output of "rtl_tcp" (set freq blablablabla, etc...) At the moment i've taken another approach...i've patched the rtl_tcp.c to set the gpio directly...i'll post my "project" asap somewhere...