- osmocom-sdr - lists.osmocom.org

Mailing list moderation/administration
by Harald Welte 17 Apr '16

17 Apr '16

Dear Osmocom SDR community, as one of the Osmocom.org admins, it has come to my attention that nobody seems to be handling the moderator queue ofr the osmocom-sdr mailing list. There's currently 267 held postings, most are spam, but there are also quite some legitimate posts held in the queue. Is there anyone involved in related projects interested in checking the mailman moderation queue regularly and approving good postings while rejecting the bad ones? Explanation: All mails from non-members are moderated to keep the list mostly spam free. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 1

fosphor benchmark result
by Geof Nieboer 14 Apr '16

14 Apr '16

All, >From the wiki, I understand you are looking for some additional benchmarks for fosphor, here's what I received: Intel i7-5930X CPU (6-core w/ HT, 3.5 GHz OC to ~4.4 GHz) 2 x Radeon 270 3GB GDDR5 video cards Intel 750 SSD, 400GB NVMe Windows 10 64-bit Compiled using MSVC + AMD App SDK Average: 325 MSps I've also submitted two pull requests to the Github repo with the patches I needed to use to get it compile in MSVC 2015. Pretty minor stuff. Cheers, Geof

1 1

patch for supporting multiple airspy by serial number in gr-osmosdr
by Lawrence Glaister 13 Apr '16

13 Apr '16

Hello all, I have completed additions to airspy_source_c.cc to support using multiple airspy devices. This is done by specifying the serial number for the device (i.e. airspy=0x644064DC317C1FCD). The current behaviour of opening the first device when no serial number is specified is still maintained. Specifying airspy=0 will also open the first device found. The serial number format is a 64bit hex number with or without a leading "0x". I have attached a patch file based on the current git source, a copy of the whole CC file as patched ( see lines 93 to 112 and 122 to 129), and a screen shot of the grc block for selecting by s/n. This patch has been tested with gnuradio 3.7.9 and 0, 1 and 2 airspy devices connected. I hope this can be placed into the current sources as I know of several requests for this have shown up on various discussion boards. I place no copyright restrictions on the code... please release it however you desire. This is my first attempt at contributing to gnu radio, so please excuse any blunders in protocol I may have made. Thank you for your fine work Lawrence Glaister VE7IT Nanoose Bay BC Canada

1 0

patch for supporting multiple airspy by serial number in gr-osmosdr
by Lawrence Glaister 09 Apr '16

09 Apr '16

Hello all, I have completed additions to airspy_source_c.cc to support using multiple airspy devices. This is done by specifying the serial number for the device (ie airspy=0x644064DC317C1FCD). The current behaviour of opening the first device when no serial number is specified is still maintained. Specifying airspy=0 will also open the first device found. The serial number format is a 64bit hex number with or without a leading "0x". I have attached a patch file based on the current git source, a copy of the whole CC file as patched ( see lines 93 to 112 and 122 to 129), and a screen shot of the grc block for selecting by s/n. This patch has been tested with gnuradio 3.7.9 and 0, 1 and 2 airspy devices connected. I hope this can be placed into the current sources as I know of several requests for this have shown up on various discussion boards. I place no copyright restrictions on the code... please release it however you desire. This is my first attempt at contributing to gnu radio, so please excuse any blunders in protocol I may have made. Thankyou for your fine work Lawrence Glaister VE7IT Nanoose Bay BC Canada

1 0

Segfault bug and solution
by Eric Jesse 29 Mar '16

29 Mar '16

Hey all, I've been looking into a seg fault bug appearing after asynchronous reads, and I wanted to put forward my thoughts, and a potential solution, perhaps for the official release. I looked into the C source code and have ultimately determined that problem lies in the rtlsdr_read_async function in librtlsdr.c, which usually (if not always) returns a -5. I've traced this error back to the libusb_cancel_transfer function. My proposed solution is to change the following condition, "if (r < 0)" to "if (r < 0 && r != LIBUSB_ERROR_NOT_FOUND)". Why? It's been noted that the new transfer status from the libusb_cancel_transfer function does not propagate immediately (and to be honest, I'm not sure when exactly it propagates). As it is now, if the function returns successfully (r=0), the function runs through the while loop again, and checks all the functions to see if they are cancelled. If not, (i.e. the status hasn't propagated) the libusb_cancel_transfer function is called again, but this time it returns LIBUSB_ERROR_NOT_FOUND, which according to the function description in the libusb documentation means "the transfer is not in progress, already complete, or already cancelled" and is treated as an error. This does not sound to me like an error, but something that can be ignored to give time for the already "cancelled" signal to obtain the "CANCELED" status. I've implemented the change personally, and everything seems to work fine. I don't know if others have seen the same seg fault problem I have, but this seems to be a working, minimal solution. Let me know if I'm interpreting the "transfer is not in progress, already complete, or already cancelled" wrong, since I don't want to ignore any actual problems. Thanks, Eric Jesse AMDG

1 0

DC spike remove ???
by a c 29 Mar '16

29 Mar '16

Hi, I just started experimenting with rtl-fm with a DVB-T stick and a raspberry pi 2. It's really very simple to use but I currently have a problem by setting a frequency in NBFM mode. When I slightly shifts the frequency of the true frequency , it appears intermodulation with DC spike even with the dc -E parameters and offset -E ??? The problem does not exist with automatic gain. IQ balance dont work with a fixed gain (ex -g 30) or i made mistake in my command line ??? Have you ever encountered this problem? Thanks, Arnaud F6GNJ

1 1

[PATCH] drop option -a and be independent from interface ip-address
by Hannes Petermaier 29 Mar '16

29 Mar '16

From: Hannes Schmelzer <oe5hpm(a)oevsv.at> It is very inconvenient to have some RTL-stick on a machine with multiple network interfaces if it is bound to a specific one. So we break up this and make this dynamically. The -a option therefore is not needed any longer. Signed-off-by: Hannes Schmelzer <oe5hpm(a)oevsv.at> --- src/rtl_tcp.c | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/src/rtl_tcp.c b/src/rtl_tcp.c index 317e0f3..39d7c3e 100644 --- a/src/rtl_tcp.c +++ b/src/rtl_tcp.c @@ -31,6 +31,7 @@ #include <sys/socket.h> #include <sys/time.h> #include <netinet/in.h> +#include <netdb.h> #include <fcntl.h> #else #include <winsock2.h> @@ -365,10 +366,10 @@ static void *command_worker(void *arg) int main(int argc, char **argv) { int r, opt, i; - char* addr = "127.0.0.1"; - int port = 1234; + char* port = "1234"; uint32_t frequency = 100000000, samp_rate = 2048000; - struct sockaddr_in local, remote; + struct addrinfo hints, *res; + struct sockaddr_in remote; uint32_t buf_num = 0; int dev_index = 0; int dev_given = 0; @@ -391,7 +392,7 @@ int main(int argc, char **argv) struct sigaction sigact, sigign; #endif - while ((opt = getopt(argc, argv, "a:p:f:g:s:b:n:d:P:")) != -1) { + while ((opt = getopt(argc, argv, "p:f:g:s:b:n:d:P:")) != -1) { switch (opt) { case 'd': dev_index = verbose_device_search(optarg); @@ -406,11 +407,8 @@ int main(int argc, char **argv) case 's': samp_rate = (uint32_t)atofs(optarg); break; - case 'a': - addr = optarg; - break; case 'p': - port = atoi(optarg); + port = optarg; break; case 'b': buf_num = atoi(optarg); @@ -502,16 +500,20 @@ int main(int argc, char **argv) pthread_cond_init(&cond, NULL); pthread_cond_init(&exit_cond, NULL); - memset(&local,0,sizeof(local)); - local.sin_family = AF_INET; - local.sin_port = htons(port); - local.sin_addr.s_addr = inet_addr(addr); + memset(&hints, 0, sizeof(hints)); + hints.ai_family = AF_INET; + hints.ai_socktype = SOCK_STREAM; + hints.ai_flags = AI_PASSIVE; /* fill in my IP for me */ + hints.ai_protocol = IPPROTO_TCP; + getaddrinfo(NULL, port, &hints, &res); + + listensocket = socket(res->ai_family, + res->ai_socktype, res->ai_protocol); - listensocket = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP); r = 1; setsockopt(listensocket, SOL_SOCKET, SO_REUSEADDR, (char *)&r, sizeof(int)); setsockopt(listensocket, SOL_SOCKET, SO_LINGER, (char *)&ling, sizeof(ling)); - bind(listensocket,(struct sockaddr *)&local,sizeof(local)); + bind(listensocket, res->ai_addr, res->ai_addrlen); #ifdef _WIN32 ioctlsocket(listensocket, FIONBIO, &blockmode); @@ -522,11 +524,11 @@ int main(int argc, char **argv) while(1) { printf("listening...\n"); - printf("Use the device argument 'rtl_tcp=%s:%d' in OsmoSDR " + printf("Use the device argument 'rtl_tcp=%s:%s' in OsmoSDR " "(gr-osmosdr) source\n" "to receive samples in GRC and control " "rtl_tcp parameters (frequency, gain, ...).\n", - addr, port); + "yourip", port); listen(listensocket,1); while(1) { -- 1.9.1

3 2

[notifications@github.com: [rtl-sdr] drop option -a and be independent from interface ip-address (#2)]
by Harald Welte 28 Mar '16

28 Mar '16

somebody sending pull requests to a mirror of the official repository... -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 2

Time to rename projects.osmocom.org to osmocom.org
by Holger Freyther 21 Mar '16

21 Mar '16

Hi, I think we all liked tnt's proposal to just call it osmocom.org. Are we ready to make the redmine available as osmocom.org (and redirect www.osmocom.org, projects.osmocom.org to it)? As first step of redirects I propose: http://bb.osmocom.org/ -> http://osmocom.org/projects/baseband http://openbsc.osmocom.org/ -> http://osmocom.org/projects/openbsc http://tetra.osmocom.org/ -> http://osmocom.org/projects/tetra http://simtrace.osmocom.org/ -> http://osmocom.org/projects/simtrace http://security.osmocom.org/ -> http://osmocom.org/projects/security http://gmr.osmocom.org/ -> http://osmocom.org/projects/gmr http://sdr.osmocom.org/ -> http://osmocom.org/projects/sdr any objections or corrections to that? kind regards holger

5 7

AirSpy & sdr tools ?
by Jean-Paul Le Fèvre 04 Mar '16

04 Mar '16

Hi, After having played with a DX-Patrol device for a while using the sdr tools (sdr_tcp, sdr_fm, etc.) I've purchased an AirSpy and I would like to experiment with it. However reading the GrOsmoSDR page I see that AirSpy is supposed to be supported by the gr-osmosdr library but on the other hand the wiki page rtl-sdr does not mention it. I've recompiled the file librtlsdr.c after having added the id product and vendor of the AirSpy in the code. But I figure out that it is not sufficient and even maybe that it does not make sense. Is there a way to make the sdr tool set (sdr_*) compatible with the AirSpy ? -- Jean-Paul Le Fèvre - CEA Saclay Irfu Svom Scientific Ground Segment project manager

2 1