From sohaib1110 at yahoo.co.uk Tue Oct 1 12:52:56 2013 From: sohaib1110 at yahoo.co.uk (Sohaib Khan) Date: Tue, 1 Oct 2013 13:52:56 +0100 (BST) Subject: Runtime:error Message-ID: <1380631976.10592.YahooMailBasic@web172703.mail.ir2.yahoo.com> I am using DVB-T dongle RTLSDR2832U with gnu radio, i have installed all the required files, but when i compile my flowgraph I get an error. Runtime Error:Failed to open rtlsdr device. What is the problem and its solution?? I cannot install udev rules also, i also face errors at it.... should i uninstall my ubuntu and start from the very begining. Sohaib bin Altaf pakistan From sohaib1110 at yahoo.co.uk Tue Oct 1 18:41:37 2013 From: sohaib1110 at yahoo.co.uk (Sohaib Khan) Date: Tue, 1 Oct 2013 19:41:37 +0100 (BST) Subject: Runtime Error Message-ID: <1380652897.32128.YahooMailBasic@web172706.mail.ir2.yahoo.com> i have captured a file (FM file), using rtlsdr2832u.... i.e cap.bin. How can i play it or open it??? Kindly help Sohaib Bin Altaf Pakistan From yo3ggx at gmail.com Sun Oct 6 20:15:26 2013 From: yo3ggx at gmail.com (Dan) Date: Sun, 06 Oct 2013 23:15:26 +0300 Subject: Problems on CentOS 6 64 bit Message-ID: <5251C4DE.4020902@gmail.com> Hi all, I have compiled and installed rtl-sdr on CentOS 6 following instructions. Everything compiles without errors, but: - when I run rtl_test I get the following errors: Found 1 device(s): 0: ezcap USB 2.0 DVB-T/DAB/FM dongle Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle Found Rafael Micro R820T tuner Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6 Info: This tool will continuously read from the device, and report if samples get lost. If you observe no further output, everything is fine. Reading samples in async mode... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... cb transfer status: 5, canceling... Library error 0, exiting... If I run rtl_tcp I get the following errors when the client tries to connect: Found 1 device(s). Found Rafael Micro R820T tuner Using ezcap USB 2.0 DVB-T/DAB/FM dongle Tuned to 100000000 Hz. listening... Use the device argument 'rtl_tcp=192.168.33.99:8767' in OsmoSDR (gr-osmosdr) source to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...). client accepted! set freq 145000000 cb transfer status: 5, canceling... cb transfer status: 5, canceling... rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set sample rate 1024000 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 set freq correction 4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 rtlsdr_demod_write_reg failed with -4 rtlsdr_demod_read_reg failed with -4 worker cond timeout Signal caught, exiting! comm recv bye Signal caught, exiting! all threads dead.. listening... The same client connects without errors to another rtl_tcp instance on a Windows 7 computer, with the same module. Any help is greatly appreciated. Thanks, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From sylvain.azarian at gmail.com Sun Oct 6 20:37:34 2013 From: sylvain.azarian at gmail.com (Sylvain AZARIAN) Date: Sun, 6 Oct 2013 22:37:34 +0200 Subject: Problems on CentOS 6 64 bit In-Reply-To: <5251C4DE.4020902@gmail.com> References: <5251C4DE.4020902@gmail.com> Message-ID: This message looks coming from libusb. Maybe you check that lib source to understand what error code 5 stands for.... Have you tried to run app as root ? Le 6 oct. 2013 22:34, "Dan" a ?crit : > Hi all, > > I have compiled and installed rtl-sdr on CentOS 6 following instructions. > Everything compiles without errors, but: > - when I run rtl_test I get the following errors: > Found 1 device(s): > 0: ezcap USB 2.0 DVB-T/DAB/FM dongle > > Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle > Found Rafael Micro R820T tuner > Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 > 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 > 43.9 44.5 48.0 49.6 > > Info: This tool will continuously read from the device, and report if > samples get lost. If you observe no further output, everything is fine. > > Reading samples in async mode... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > > Library error 0, exiting... > > If I run rtl_tcp I get the following errors when the client tries to > connect: > Found 1 device(s). > Found Rafael Micro R820T tuner > Using ezcap USB 2.0 DVB-T/DAB/FM dongle > Tuned to 100000000 Hz. > listening... > Use the device argument 'rtl_tcp=192.168.33.99:8767' in OsmoSDR > (gr-osmosdr) source > to receive samples in GRC and control rtl_tcp parameters (frequency, gain, > ...). > client accepted! > set freq 145000000 > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > set sample rate 1024000 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > set freq correction 4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > worker cond timeout > Signal caught, exiting! > comm recv bye > Signal caught, exiting! > all threads dead.. > listening... > > > The same client connects without errors to another rtl_tcp instance on a > Windows 7 computer, with the same module. > > Any help is greatly appreciated. > > Thanks, > Dan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex_stani at yahoo.it Tue Oct 8 06:49:02 2013 From: alex_stani at yahoo.it (Alessandro Staniscia) Date: Tue, 8 Oct 2013 07:49:02 +0100 (BST) Subject: No subject Message-ID: <1381214942.45315.YahooMailMobile@web171204.mail.ir2.yahoo.com> Hi all, I have built my antenna and now I wont evaluate my work, so, in your opinions can I use the rtl_sdr software to accomplish it? Someone have a suggestion or is it impossible? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex_stani at yahoo.it Tue Oct 8 07:06:17 2013 From: alex_stani at yahoo.it (Alessandro Staniscia) Date: Tue, 8 Oct 2013 08:06:17 +0100 (BST) Subject: Can I use rtl_sdr to evaluate my antenna? Message-ID: <1381215977.35519.YahooMailMobile@web171201.mail.ir2.yahoo.com> Hi all, I have built my antenna and now I wont evaluate my work, so, in your opinions can I use the rtl_sdr software to accomplish it? Someone have a suggestion or is it impossible? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From lababidi at gmail.com Tue Oct 8 16:38:42 2013 From: lababidi at gmail.com (Mahmoud Lababidi) Date: Tue, 8 Oct 2013 12:38:42 -0400 Subject: Can I use rtl_sdr to evaluate my antenna? In-Reply-To: <1381215977.35519.YahooMailMobile@web171201.mail.ir2.yahoo.com> References: <1381215977.35519.YahooMailMobile@web171201.mail.ir2.yahoo.com> Message-ID: Alessandro The software can allow you to grab a variety of parameters and information, such as IQ (inphase quadrature). So the question is what do you need the software to do? What type of information are you looking to get? On Tue, Oct 8, 2013 at 3:06 AM, Alessandro Staniscia wrote: > Hi all, > I have built my antenna and now I wont evaluate my work, so, in your > opinions can I use the rtl_sdr software to accomplish it? Someone have a > suggestion or is it impossible? > > Thanks > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex_stani at yahoo.it Wed Oct 9 10:41:14 2013 From: alex_stani at yahoo.it (Alessandro) Date: Wed, 09 Oct 2013 12:41:14 +0200 Subject: rtl_tcp.c:112:10: error: invalid suffix "Ui64" on integer constant Message-ID: <525532CA.2030002@yahoo.it> Hi All, Just been trying to compile rtl-sdr on my Windows7x64; so I have cloned the trunk repository, download mingw64, download cmake, get libusb-1.0 for windows and get pthreads-win32. After all I have configured cMake with the parameter show below: CMAKE_RC_FLAGS:STRING= CMAKE_VERBOSE_MAKEFILE:BOOL=0 CMAKE_RC_COMPILER:FILEPATH=C:/Program Files/mingw-builds/x64-4.8.1-posix-seh-rev5/mingw64/bin/windres.exe CMAKE_AR:FILEPATH=C:/Program Files/mingw-builds/x64-4.8.1-posix-seh-rev5/mingw64/bin/ar.exe CMAKE_C_FLAGS:STRING= CMAKE_C_FLAGS_DEBUG:STRING= CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING= CMAKE_USE_RELATIVE_PATHS:BOOL=1 CMAKE_C_STANDARD_LIBRARIES:STRING=-lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 -lstdc++ CMAKE_C_COMPILER:FILEPATH=C:/Program Files/mingw-builds/x64-4.8.1-posix-seh-rev5/mingw64/bin/x86_64-w64-mingw32-gcc.exe CMAKE_CODEBLOCKS_EXECUTABLE:FILEPATH=C:/Program Files/mingw-builds/x64-4.8.1-posix-seh-rev5/mingw64/bin/mingw32-make.exe LIBUSB_INCLUDE_DIR:PATH=E:/Staniscia/PRIVATO/RTL_SDR/libusbx/include/libusbx-1.0 LIBUSB_LIBRARIES:FILEPATH=E:/Staniscia/PRIVATO/RTL_SDR/libusbx/MinGW64/static/libusb-1.0.a THREADS_PTHREADS_INCLUDE_DIR:PATH=E:/Staniscia/PRIVATO/RTL_SDR/pthreads-win32/Pre-built.2/include THREADS_PTHREADS_WIN32_LIBRARY:FILEPATH=E:/Staniscia/PRIVATO/RTL_SDR/pthreads-win32/Pre-built.2/lib/x64/libpthreadGC2.a and I don't have any warning from cMake but when I make the project I have this: ---------------------- E:\Staniscia\PRIVATO\RTL_SDR\repo\rtl-sdr\build>mingw32-make.exe clean E:\Staniscia\PRIVATO\RTL_SDR\repo\rtl-sdr\build>mingw32-make.exe [ 5%] Building C object src/CMakeFiles/libgetopt_static.dir/getopt/getopt.c.obj Linking C static library liblibgetopt_static.a [ 5%] Built target libgetopt_static [ 10%] Building C object src/CMakeFiles/rtlsdr_shared.dir/librtlsdr.c.obj [ 15%] Building C object src/CMakeFiles/rtlsdr_shared.dir/tuner_e4k.c.obj [ 21%] Building C object src/CMakeFiles/rtlsdr_shared.dir/tuner_fc0012.c.obj [ 26%] Building C object src/CMakeFiles/rtlsdr_shared.dir/tuner_fc0013.c.obj [ 31%] Building C object src/CMakeFiles/rtlsdr_shared.dir/tuner_fc2580.c.obj [ 36%] Building C object src/CMakeFiles/rtlsdr_shared.dir/tuner_r820t.c.obj Linking C shared library librtlsdr.dll [ 36%] Built target rtlsdr_shared [ 42%] Building C object src/CMakeFiles/rtl_adsb.dir/rtl_adsb.c.obj Linking C executable rtl_adsb.exe [ 42%] Built target rtl_adsb [ 47%] Building C object src/CMakeFiles/rtl_eeprom.dir/rtl_eeprom.c.obj Linking C executable rtl_eeprom.exe [ 47%] Built target rtl_eeprom [ 52%] Building C object src/CMakeFiles/rtl_fm.dir/rtl_fm.c.obj Linking C executable rtl_fm.exe [ 52%] Built target rtl_fm [ 57%] Building C object src/CMakeFiles/rtl_sdr.dir/rtl_sdr.c.obj Linking C executable rtl_sdr.exe [ 57%] Built target rtl_sdr [ 63%] Building C object src/CMakeFiles/rtl_tcp.dir/rtl_tcp.c.obj ..\..\src\rtl_tcp.c: In function 'gettimeofday': ..\..\src\rtl_tcp.c:112:10: error: invalid suffix "Ui64" on integer constant tmp -= 11644473600000000Ui64; ^ src\CMakeFiles\rtl_tcp.dir\build.make:57: recipe for target 'src/CMakeFiles/rtl_tcp.dir/rtl_tcp.c.obj' failed mingw32-make.exe[2]: *** [src/CMakeFiles/rtl_tcp.dir/rtl_tcp.c.obj] Error 1 CMakeFiles\Makefile2:319: recipe for target 'src/CMakeFiles/rtl_tcp.dir/all' failed mingw32-make.exe[1]: *** [src/CMakeFiles/rtl_tcp.dir/all] Error 2 Makefile:115: recipe for target 'all' failed mingw32-make.exe: *** [all] Error 2 ---------------------- Someone can help me? From a.nielsen at shikadi.net Wed Oct 9 11:03:48 2013 From: a.nielsen at shikadi.net (Adam Nielsen) Date: Wed, 9 Oct 2013 21:03:48 +1000 Subject: rtl_tcp.c:112:10: error: invalid suffix "Ui64" on integer constant In-Reply-To: <525532CA.2030002@yahoo.it> References: <525532CA.2030002@yahoo.it> Message-ID: <20131009210348.47e55b3e@korath.teln.shikadi.net> > Just been trying to compile rtl-sdr on my Windows7x64; so I have > cloned the trunk repository, download mingw64, download cmake, get > libusb-1.0 for windows and get pthreads-win32. > ..\..\src\rtl_tcp.c:112:10: error: invalid suffix "Ui64" on integer > constant tmp -= 11644473600000000Ui64; > > Someone can help me? It looks like the "i64" suffix is specific to Microsoft VC++. I guess since you're compiling for Windows it's assumed you'll be using the MS compiler. Try changing the "Ui64" at the end of the number to the standard "ULL" instead and see if that lets you finish compiling. Cheers, Adam. From keenerd at gmail.com Wed Oct 9 11:58:43 2013 From: keenerd at gmail.com (keenerd) Date: Wed, 9 Oct 2013 07:58:43 -0400 Subject: rtl_tcp.c:112:10: error: invalid suffix "Ui64" on integer constant In-Reply-To: <20131009210348.47e55b3e@korath.teln.shikadi.net> References: <525532CA.2030002@yahoo.it> <20131009210348.47e55b3e@korath.teln.shikadi.net> Message-ID: Take a look at my mingw build script: http://kmkeen.com/tmp/mingw32.sh.txt -Kyle http://kmkeen.com From alex_stani at yahoo.it Wed Oct 9 13:25:00 2013 From: alex_stani at yahoo.it (Alessandro) Date: Wed, 09 Oct 2013 15:25:00 +0200 Subject: rtl_tcp.c:112:10: error: invalid suffix "Ui64" on integer constant In-Reply-To: <20131009210348.47e55b3e@korath.teln.shikadi.net> References: <525532CA.2030002@yahoo.it> <20131009210348.47e55b3e@korath.teln.shikadi.net> Message-ID: <5255592C.9030505@yahoo.it> It sounds good, thanks! Now I have compiled rtl_sdr_x64 on Windows7x64 arch and it shows only Ui64 problem. I didn't do other 'sed-operation' on C files ( useful script keenerd!!! ) but I have added -lws2_32 to resolve the undefined reference (it's a known fail on mingws user community) Thanks On 09/10/2013 13:58, keenerd wrote: > Take a look at my mingw build script: > http://kmkeen.com/tmp/mingw32.sh.txt > > -Kyle > http://kmkeen.com > On 09/10/2013 13:03, Adam Nielsen wrote: >> Just been trying to compile rtl-sdr on my Windows7x64; so I have >> cloned the trunk repository, download mingw64, download cmake, get >> libusb-1.0 for windows and get pthreads-win32. > >> ..\..\src\rtl_tcp.c:112:10: error: invalid suffix "Ui64" on integer >> constant tmp -= 11644473600000000Ui64; >> >> Someone can help me? > > It looks like the "i64" suffix is specific to Microsoft VC++. I guess > since you're compiling for Windows it's assumed you'll be using the MS > compiler. Try changing the "Ui64" at the end of the number to the > standard "ULL" instead and see if that lets you finish compiling. > > Cheers, > Adam. > From yo3ggx at gmail.com Thu Oct 10 13:32:03 2013 From: yo3ggx at gmail.com (Dan) Date: Thu, 10 Oct 2013 16:32:03 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: References: <5251C4DE.4020902@gmail.com> Message-ID: <5256AC53.7030603@gmail.com> Hi, I have tried to install rtlsdr for 64bit using a different procedure, from here: http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#42c.rtlsdr with the same resuit. I really don't now what to do .... Best regards, Dan On 10/6/2013 11:37 PM, Sylvain AZARIAN wrote: > > This message looks coming from libusb. Maybe you check that lib source > to understand what error code 5 stands for.... > > Have you tried to run app as root ? > > Le 6 oct. 2013 22:34, "Dan" > a ?crit : > > Hi all, > > I have compiled and installed rtl-sdr on CentOS 6 following > instructions. > Everything compiles without errors, but: > - when I run rtl_test I get the following errors: > Found 1 device(s): > 0: ezcap USB 2.0 DVB-T/DAB/FM dongle > > Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle > Found Rafael Micro R820T tuner > Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 > 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 > 40.2 42.1 43.4 43.9 44.5 48.0 49.6 > > Info: This tool will continuously read from the device, and report if > samples get lost. If you observe no further output, everything is > fine. > > Reading samples in async mode... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > > Library error 0, exiting... > > If I run rtl_tcp I get the following errors when the client tries > to connect: > Found 1 device(s). > Found Rafael Micro R820T tuner > Using ezcap USB 2.0 DVB-T/DAB/FM dongle > Tuned to 100000000 Hz. > listening... > Use the device argument 'rtl_tcp=192.168.33.99:8767 > ' in OsmoSDR (gr-osmosdr) source > to receive samples in GRC and control rtl_tcp parameters > (frequency, gain, ...). > client accepted! > set freq 145000000 > cb transfer status: 5, canceling... > cb transfer status: 5, canceling... > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > set sample rate 1024000 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > set freq correction 4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > rtlsdr_demod_write_reg failed with -4 > rtlsdr_demod_read_reg failed with -4 > worker cond timeout > Signal caught, exiting! > comm recv bye > Signal caught, exiting! > all threads dead.. > listening... > > > The same client connects without errors to another rtl_tcp > instance on a Windows 7 computer, with the same module. > > Any help is greatly appreciated. > > Thanks, > Dan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.nielsen at shikadi.net Thu Oct 10 20:47:54 2013 From: a.nielsen at shikadi.net (Adam Nielsen) Date: Fri, 11 Oct 2013 06:47:54 +1000 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <5256AC53.7030603@gmail.com> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> Message-ID: <20131011064754.602e548e@korath.teln.shikadi.net> > I really don't now what to do .... You're using CentOS. This is an enterprise Linux system, designed for running servers. This means the software is chosen because it is known to be stable, so it is usually missing the latest features. As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August 2010. This is over three years old! A *lot* of bug fixes and improvements happen in three years. The problem you are experiencing has likely been fixed at some point within this time, so your solutions are to install a newer libusb version, or better yet, switch to a Linux distro that is more suited to this kind of work. CentOS is great if you want to run a database server, but not so good if you want to experiment with the very latest gadgets! Cheers, Adam. From zaitcev at kotori.zaitcev.us Thu Oct 10 20:58:55 2013 From: zaitcev at kotori.zaitcev.us (Pete Zaitcev) Date: Thu, 10 Oct 2013 14:58:55 -0600 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011064754.602e548e@korath.teln.shikadi.net> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> Message-ID: <20131010145855.388fed9b@lembas.zaitcev.lan> On Fri, 11 Oct 2013 06:47:54 +1000 Adam Nielsen wrote: > As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August > 2010. This is over three years old! A *lot* of bug fixes and > improvements happen in three years. Age has nothing to do with it. The libusb 1 existed when RHEL 6 was composed, but users weren't clamouring for it, so it didn't make the cut. AFAIK it's missing from EPEL too. My suggestion would be to grab an old libusb1 RPM and rebuild it. It should be trivial and the result is installable alongside the old libusub. http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/14/Fedora/source/SRPMS/libusb1-1.0.8-1.fc14.src.rpm -- Pete From lababidi at gmail.com Thu Oct 10 21:17:33 2013 From: lababidi at gmail.com (Mahmoud Lababidi) Date: Thu, 10 Oct 2013 17:17:33 -0400 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131010145855.388fed9b@lembas.zaitcev.lan> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> Message-ID: forget rpm, just install libusb by downloading the tarball at http://www.libusb.org/ configure make make install just my two cents On Thu, Oct 10, 2013 at 4:58 PM, Pete Zaitcev wrote: > On Fri, 11 Oct 2013 06:47:54 +1000 > Adam Nielsen wrote: > > > As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August > > 2010. This is over three years old! A *lot* of bug fixes and > > improvements happen in three years. > > Age has nothing to do with it. The libusb 1 existed when RHEL 6 was > composed, but users weren't clamouring for it, so it didn't make the cut. > AFAIK it's missing from EPEL too. > > My suggestion would be to grab an old libusb1 RPM and rebuild it. > It should be trivial and the result is installable alongside the > old libusub. > > http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/14/Fedora/source/SRPMS/libusb1-1.0.8-1.fc14.src.rpm > > -- Pete > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.nielsen at shikadi.net Thu Oct 10 21:19:59 2013 From: a.nielsen at shikadi.net (Adam Nielsen) Date: Fri, 11 Oct 2013 07:19:59 +1000 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131010145855.388fed9b@lembas.zaitcev.lan> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> Message-ID: <20131011071959.0e384ccb@korath.teln.shikadi.net> > > As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in > > August 2010. This is over three years old! A *lot* of bug fixes > > and improvements happen in three years. > > Age has nothing to do with it. So you're saying no useful work was done on libusb in three years? Granted I haven't looked at the commit history but it seems a bit unlikely. > My suggestion would be to grab an old libusb1 RPM and rebuild it. > It should be trivial and the result is installable alongside the > old libusub. I'm not sure how rebuilding a version of libusb that doesn't work will help... Cheers, Adam. From lababidi at gmail.com Thu Oct 10 21:36:22 2013 From: lababidi at gmail.com (Mahmoud Lababidi) Date: Thu, 10 Oct 2013 17:36:22 -0400 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011071959.0e384ccb@korath.teln.shikadi.net> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> Message-ID: What he's saying is CENTOS uses libusb.0.1.12, upgrade to libusb1.0. On Thu, Oct 10, 2013 at 5:19 PM, Adam Nielsen wrote: > > > As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in > > > August 2010. This is over three years old! A *lot* of bug fixes > > > and improvements happen in three years. > > > > Age has nothing to do with it. > > So you're saying no useful work was done on libusb in three years? > Granted I haven't looked at the commit history but it seems a bit > unlikely. > > > My suggestion would be to grab an old libusb1 RPM and rebuild it. > > It should be trivial and the result is installable alongside the > > old libusub. > > I'm not sure how rebuilding a version of libusb that doesn't work will > help... > > Cheers, > Adam. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yo3ggx at gmail.com Fri Oct 11 03:52:45 2013 From: yo3ggx at gmail.com (Dan) Date: Fri, 11 Oct 2013 06:52:45 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011064754.602e548e@korath.teln.shikadi.net> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> Message-ID: <5257760D.7010307@gmail.com> Hi Adam, On 10/10/2013 11:47 PM, Adam Nielsen wrote: >> I really don't now what to do .... > You're using CentOS. This is an enterprise Linux system, designed for > running servers. This means the software is chosen because it is known > to be stable, so it is usually missing the latest features. > > As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in August > 2010. This is over three years old! A *lot* of bug fixes and > improvements happen in three years. I have the following libusv1 libraries installed: libusb1-1.0.9-0.6.rc1.el6.i686 libusb1-1.0.9-0.6.rc1.el6.x86_64 > The problem you are experiencing has likely been fixed at some point > within this time, so your solutions are to install a newer libusb > version, or better yet, switch to a Linux distro that is more suited to > this kind of work. CentOS is great if you want to run a database > server, but not so good if you want to experiment with the very latest > gadgets! I will try to build a newer version of the library. > Cheers, > Adam. Thank you, Dan From a.nielsen at shikadi.net Fri Oct 11 04:05:11 2013 From: a.nielsen at shikadi.net (Adam Nielsen) Date: Fri, 11 Oct 2013 14:05:11 +1000 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <5257760D.7010307@gmail.com> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <5257760D.7010307@gmail.com> Message-ID: <20131011140511.505d4925@teln.shikadi.net> > I will try to build a newer version of the library. No worries - don't forget a recent kernel version too as things change quite a bit there too, especially if you're on recent hardware. Cheers, Adam. From alancorey at yahoo.com Fri Oct 11 04:14:50 2013 From: alancorey at yahoo.com (Alan Corey) Date: Thu, 10 Oct 2013 21:14:50 -0700 (PDT) Subject: rtl_sdr and lysdr? Message-ID: <1381464890.70912.YahooMailBasic@web161501.mail.bf1.yahoo.com> I found this program yesterday: https://github.com/gordonjcp/lysdr It's the GUI part of a minimal HDSDR/SDR# type program but it needs an IQ stream from something. It seems to be mostly intended for use with Softrocks but I wonder if anyone's been able to feed something like the output from rtl_sdr into it? It's got some Python and some C, requires Jackaudio. I was able to build it and run it under OpenBSD 5.2 without much trouble. Only does USB/LSB as written, Googling doesn't find me anything connecting it with any Osmocom stuff. rtl_tcp through Netcat might work better because it seems to want to control the frequencies. I've only got a couple of $20 dongles. ----- Radio Astronomy - the ultimate DX From peter at stuge.se Fri Oct 11 04:15:09 2013 From: peter at stuge.se (Peter Stuge) Date: Fri, 11 Oct 2013 06:15:09 +0200 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011071959.0e384ccb@korath.teln.shikadi.net> References: <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> Message-ID: <20131011041509.28982.qmail@stuge.se> Mahmoud Lababidi wrote: > forget rpm, just install libusb by downloading the tarball at > http://www.libusb.org/ > configure make make install > > just my two cents I'd recommend avoiding the libusbx tarball which has been linked from there and instead getting the http://git.libusb.org/libusb.git code. Adam Nielsen wrote: > > > As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in > > > August 2010. This is over three years old! A *lot* of bug fixes > > > and improvements happen in three years. > > > > Age has nothing to do with it. > > So you're saying no useful work was done on libusb in three years? It's complicated, but yes libusb.git code hasn't changed in about a year. I expect it to work reliably, and indeed one or two bugs have been fixed since the 1.0.9 release. (Before you say it, no, I can not simply make a 1.0.10 release. As I wrote, it is complicated. If you'd like to help out feel free to let me know and I'll explain until your ears fall off.. :) > Granted I haven't looked at the commit history but it seems a bit > unlikely. Please do look into the facts (it's very easy) rather than speculating. Thanks //Peter From martin at windycitysdr.com Fri Oct 11 04:43:48 2013 From: martin at windycitysdr.com (Martin) Date: Thu, 10 Oct 2013 23:43:48 -0500 Subject: rtl_sdr and lysdr? In-Reply-To: <1381464890.70912.YahooMailBasic@web161501.mail.bf1.yahoo.com> References: <1381464890.70912.YahooMailBasic@web161501.mail.bf1.yahoo.com> Message-ID: <8E875B55-B5EC-4A69-992F-F5DCC7C49F7C@windycitysdr.com> Alan, Good find! Especially since there is talk of a new USB stock, Mirimacs, or something like that, that *could* be used for providing I/Q data. Sent from my iPhone On Oct 10, 2013, at 11:14 PM, Alan Corey wrote: > I found this program yesterday: https://github.com/gordonjcp/lysdr > > It's the GUI part of a minimal HDSDR/SDR# type program but it needs an IQ stream from something. It seems to be mostly intended for use with Softrocks but I wonder if anyone's been able to feed something like the output from rtl_sdr into it? It's got some Python and some C, requires Jackaudio. I was able to build it and run it under OpenBSD 5.2 without much trouble. Only does USB/LSB as written, Googling doesn't find me anything connecting it with any Osmocom stuff. rtl_tcp through Netcat might work better because it seems to want to control the frequencies. I've only got a couple of $20 dongles. > ----- > Radio Astronomy - the ultimate DX > From ka2rrz at yahoo.com Fri Oct 11 04:49:58 2013 From: ka2rrz at yahoo.com (Ron Hayes) Date: Thu, 10 Oct 2013 21:49:58 -0700 (PDT) Subject: rtl_sdr and lysdr? In-Reply-To: <1381464890.70912.YahooMailBasic@web161501.mail.bf1.yahoo.com> References: <1381464890.70912.YahooMailBasic@web161501.mail.bf1.yahoo.com> Message-ID: <1381466998.40416.YahooMailNeo@web125501.mail.ne1.yahoo.com> I never heard of that one or any mention of it in the groups?? I got the DDS ad9850 wired to the arduino and the encoder, guessing on the encoder some with the pin outs, may have to change 2 wires if it counts the wrong way. In the morning I will start with the code oh boy can't wait for that, you know how much I like code. I am going to start with a fresh arduino download maybe that will help??? On Thursday, October 10, 2013 11:30 PM, Alan Corey wrote: I found this program yesterday: https://github.com/gordonjcp/lysdr It's the GUI part of a minimal HDSDR/SDR# type program but it needs an IQ stream from something.? It seems to be mostly intended for use with Softrocks but I wonder if anyone's been able to feed something like the output from rtl_sdr into it?? It's got some Python and some C, requires Jackaudio.? I was able to build it and run it under OpenBSD 5.2 without much trouble. Only does USB/LSB as written, Googling doesn't find me anything connecting it with any Osmocom stuff.? rtl_tcp through Netcat might work better because it seems to want to control the frequencies.? I've only got a couple of $20 dongles. ----- Radio Astronomy - the ultimate DX -------------- next part -------------- An HTML attachment was scrubbed... URL: From osmocom at gustad.com Fri Oct 11 05:45:39 2013 From: osmocom at gustad.com (Petter Gustad) Date: Fri, 11 Oct 2013 07:45:39 +0200 (CEST) Subject: rtlsdr_read_reg failed with -7 Message-ID: <20131011.074539.1193846385705287514.petter@gustad.com> I keep getting the message "rtlsdr_read_reg failed with -7" whenever I run any of the rtl_ commands. When I run the command after re-plugging the stick it usually works (except the lost samples): rtl_test Found 1 device(s): 0: ezcap USB 2.0 DVB-T/DAB/FM dongle Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle Found Fitipower FC0013 tuner Supported gain values (23): -9.9 -7.3 -6.5 -6.3 -6.0 -5.8 -5.4 5.8 6.1 6.3 6.5 6.7 6.8 7.0 7.1 17.9 18.1 18.2 18.4 18.6 18.8 19.1 19.7 Info: This tool will continuously read from the device, and report if samples get lost. If you observe no further output, everything is fine. Reading samples in async mode... lost at least 84 bytes But if I run any of the rtl_ commands after breaking any previous running command I get: rtl_test Found 1 device(s): 0: ezcap USB 2.0 DVB-T/DAB/FM dongle Using device 0: ezcap USB 2.0 DVB-T/DAB/FM dongle rtlsdr_read_reg failed with -7 rtlsdr_write_reg failed with -7 rtlsdr_read_reg failed with -7 rtlsdr_write_reg failed with -7 rtlsdr_read_reg failed with -7 rtlsdr_write_reg failed with -7 Is there a way to completely reset the driver other than re-plugging it? I'm running Gentoo Linux (3.2.1 kernel) Thanks! //Petter From martin at windycitysdr.com Fri Oct 11 08:41:08 2013 From: martin at windycitysdr.com (Martin O'Shield) Date: Fri, 11 Oct 2013 03:41:08 -0500 Subject: rtl_sdr and lysdr? In-Reply-To: <1381466998.40416.YahooMailNeo@web125501.mail.ne1.yahoo.com> References: <1381464890.70912.YahooMailBasic@web161501.mail.bf1.yahoo.com> <1381466998.40416.YahooMailNeo@web125501.mail.ne1.yahoo.com> Message-ID: Alan, On Thu, Oct 10, 2013 at 11:49 PM, Ron Hayes wrote: > I never heard of that one or any mention of it in the groups?? > Has anyone tried the Mirics-based SDR dongles? They seem to have some interesting specs vs. the RTLs (blog.palosaari.fi ) submitted 3 days ago by oldmaninohio http://www.reddit.com/r/RTLSDR/comments/1ny4s0/has_anyone_tried_the_miricsbased_sdr_dongles_they/ Here is a comment from the above page: "You can buy the reference design right from the manufacturer:" http://www.mirics.com/node/31 Antti's LinuxTV Blog 2013-08-17 Mirics MSi3101 SDR Linux driver http://blog.palosaari.fi/2013/08/mirics-msi3101-sdr-linux-driver.html And since Osmocom is becoming the "middleware" for many SDR capable devices, this might be a good addition. Sincerely, Martin > I got the DDS ad9850 wired to the arduino and the encoder, guessing on the > encoder some with the pin outs, may have to change 2 wires if it counts the > wrong way. In the morning I will start with the code oh boy can't wait for > that, you know how much I like code. I am going to start with a fresh > arduino download maybe that will help??? > > > On Thursday, October 10, 2013 11:30 PM, Alan Corey > wrote: > I found this program yesterday: https://github.com/gordonjcp/lysdr > > It's the GUI part of a minimal HDSDR/SDR# type program but it needs an IQ > stream from something. It seems to be mostly intended for use with > Softrocks but I wonder if anyone's been able to feed something like the > output from rtl_sdr into it? It's got some Python and some C, requires > Jackaudio. I was able to build it and run it under OpenBSD 5.2 without > much trouble. Only does USB/LSB as written, Googling doesn't find me > anything connecting it with any Osmocom stuff. rtl_tcp through Netcat > might work better because it seems to want to control the frequencies. > I've only got a couple of $20 dongles. > ----- > Radio Astronomy - the ultimate DX > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Fri Oct 11 09:32:24 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 11 Oct 2013 11:32:24 +0200 Subject: rtl_sdr and lysdr? In-Reply-To: References: <1381464890.70912.YahooMailBasic@web161501.mail.bf1.yahoo.com> <1381466998.40416.YahooMailNeo@web125501.mail.ne1.yahoo.com> Message-ID: > And since Osmocom is becoming the "middleware" for many SDR capable devices, > > this might be a good addition. Osmocom has had a driver for like 1 year ... http://git.osmocom.org/libmirisdr/ and if the lib is found, support will be built in the gr-osmosdr source as well ... AFAIK one of their big downside is that each RF range has a different input and most dongles only have 1 wired in ... restricting the range a lot. But steve would know better. Cheers, Sylvain From sohaib1110 at yahoo.co.uk Fri Oct 11 10:39:24 2013 From: sohaib1110 at yahoo.co.uk (Sohaib Khan) Date: Fri, 11 Oct 2013 11:39:24 +0100 (BST) Subject: Boost required to build gr-osmosdr Message-ID: <1381487964.95056.YahooMailBasic@web172706.mail.ir2.yahoo.com> Boost required to build gr-osmosdr I get this error... how can i solve it Sohaib bin altaf From yo3ggx at gmail.com Fri Oct 11 14:37:56 2013 From: yo3ggx at gmail.com (Dan) Date: Fri, 11 Oct 2013 17:37:56 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011041509.28982.qmail@stuge.se> References: <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> Message-ID: <52580D44.5090609@gmail.com> Hi all, On 10/11/2013 7:15 AM, Peter Stuge wrote: > Mahmoud Lababidi wrote: >> forget rpm, just install libusb by downloading the tarball at >> http://www.libusb.org/ >> configure make make install >> >> just my two cents > I'd recommend avoiding the libusbx tarball which has been linked from > there and instead getting the http://git.libusb.org/libusb.git code. I have tried to compile both the one from www.libusb.org and the one from git. After recompiling rtl-sdr with the new libraries the errors are the same.... Any other hints? Thank you, Dan > > Adam Nielsen wrote: >>>> As far as I can tell, CentOS 6.4 uses libusb 0.1.12, released in >>>> August 2010. This is over three years old! A *lot* of bug fixes >>>> and improvements happen in three years. >>> Age has nothing to do with it. >> So you're saying no useful work was done on libusb in three years? > It's complicated, but yes libusb.git code hasn't changed in about a > year. I expect it to work reliably, and indeed one or two bugs have > been fixed since the 1.0.9 release. (Before you say it, no, I can not > simply make a 1.0.10 release. As I wrote, it is complicated. If you'd > like to help out feel free to let me know and I'll explain until your > ears fall off.. :) > > >> Granted I haven't looked at the commit history but it seems a bit >> unlikely. > Please do look into the facts (it's very easy) rather than speculating. > > > Thanks > > //Peter > From peter at stuge.se Fri Oct 11 16:46:44 2013 From: peter at stuge.se (Peter Stuge) Date: Fri, 11 Oct 2013 18:46:44 +0200 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <52580D44.5090609@gmail.com> References: <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> Message-ID: <20131011164644.19514.qmail@stuge.se> Dan wrote: >> I'd recommend avoiding the libusbx tarball which has been linked from >> there and instead getting the http://git.libusb.org/libusb.git code. > > I have tried to compile both the one from www.libusb.org and the one > from git. > After recompiling rtl-sdr with the new libraries the errors are the > same.... Did you make sure that the rtl-sdr programs are in fact also using the new libraries, as opposed to what is installed by CentOS which is what will be used by default, when running them? > Any other hints? Only to use the latest kernel code. If you see the problem with the latest kernel (from Linus' git - the latest packaged by CentOS is irrelevant) and using code from git.libusb.org/libusb.git by way of e.g. LD_LIBRARY_PATH then I would be interested in seeing a libusb debug log. See http://libusb.org/wiki/debug for a copypaste-able instruction on how to generate one. Thanks! //Peter From yo3ggx at gmail.com Fri Oct 11 17:27:57 2013 From: yo3ggx at gmail.com (Dan) Date: Fri, 11 Oct 2013 20:27:57 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011164644.19514.qmail@stuge.se> References: <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> Message-ID: <5258351D.1030803@gmail.com> Hi Peter, On 10/11/2013 7:46 PM, Peter Stuge wrote: > Dan wrote: >>> I'd recommend avoiding the libusbx tarball which has been linked from >>> there and instead getting the http://git.libusb.org/libusb.git code. >> I have tried to compile both the one from www.libusb.org and the one >> from git. >> After recompiling rtl-sdr with the new libraries the errors are the >> same.... > Did you make sure that the rtl-sdr programs are in fact also using > the new libraries, as opposed to what is installed by CentOS which > is what will be used by default, when running them? Before this I've fully uninstalled the previous version and set the environment variables: LIBUSB_LIBS and LIBUSB_CFLAGS before running ./configure for rtl-sdr Dan From yo3ggx at gmail.com Fri Oct 11 17:36:58 2013 From: yo3ggx at gmail.com (Dan) Date: Fri, 11 Oct 2013 20:36:58 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011164644.19514.qmail@stuge.se> References: <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> Message-ID: <5258373A.3030500@gmail.com> Hi, On 10/11/2013 7:46 PM, Peter Stuge wrote: >> Any other hints? > Only to use the latest kernel code. > I cannot change the kernel on the system I intend to use the dongle, as it provides other services which cannot be interrupted.. > If you see the problem with the latest kernel (from Linus' git - the > latest packaged by CentOS is irrelevant) and using code from > git.libusb.org/libusb.git by way of e.g. LD_LIBRARY_PATH then I would > be interested in seeing a libusb debug log. See > http://libusb.org/wiki/debug for a copypaste-able instruction on how > to generate one. Thanks! I will try to generate a debug log to see... Thanks, Dan > > //Peter > -- 73 Dan YO3GGX http://www.yo3ggx.ro From zaitcev at kotori.zaitcev.us Fri Oct 11 21:52:29 2013 From: zaitcev at kotori.zaitcev.us (Pete Zaitcev) Date: Fri, 11 Oct 2013 15:52:29 -0600 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <5258351D.1030803@gmail.com> References: <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258351D.1030803@gmail.com> Message-ID: <20131011155229.74764597@lembas.zaitcev.lan> On Fri, 11 Oct 2013 20:27:57 +0300 Dan wrote: > LIBUSB_LIBS and LIBUSB_CFLAGS > before running ./configure for rtl-sdr That's a bit indirect. The best way is to run ldd ./myapp I continue to maintain that all this advice about installing "latest" without knowing what's up is not likely to work. The stock libusb1 rpm from Koji works just fine, I would not even bother rebuilding it, just pull off an F14 repo. Find what the problem is by running strace ./rtl-sdr and matching ioctls to the code. -- Pete From peter at stuge.se Sat Oct 12 07:34:17 2013 From: peter at stuge.se (Peter Stuge) Date: Sat, 12 Oct 2013 09:34:17 +0200 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011155229.74764597@lembas.zaitcev.lan> <5258351D.1030803@gmail.com> <5258373A.3030500@gmail.com> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258373A.3030500@gmail.com> Message-ID: <20131012073417.17055.qmail@stuge.se> Dan wrote: >>> Any other hints? >> Only to use the latest kernel code. > > I cannot change the kernel on the system I intend to use the dongle, > as it provides other services which cannot be interrupted.. I can understand that you can not upgrade kernel on the final system, but it would be very helpful if you could test on a separate system, with similar hardware, with a new kernel, to see if the problem persists. >> Did you make sure that the rtl-sdr programs are in fact also using >> the new libraries, as opposed to what is installed by CentOS which >> is what will be used by default, when running them? > > Before this I've fully uninstalled the previous version and set the > environment variables: > LIBUSB_LIBS and LIBUSB_CFLAGS > before running ./configure for rtl-sdr That sounds good. It is important that you have uninstalled the version provided by the CentOS package. Pete Zaitcev wrote: > > LIBUSB_LIBS and LIBUSB_CFLAGS > > before running ./configure for rtl-sdr > > That's a bit indirect. The best way is to run ldd ./myapp ldd is a good way to see what libraries will actually be loaded by a given program. If indeed the CentOS package has been uninstalled then ldd should confirm that the correct library file is being loaded. > I continue to maintain that all this advice about installing "latest" > without knowing what's up is not likely to work. It's not about what will likely make things work, it's about doing debugging with the current state of the code, so that I know that I haven't already fixed the problem in libusb.git and so that I know exactly what code is being used when the error occurs. > The stock libusb1 rpm from Koji works just fine, I would not even > bother rebuilding it, just pull off an F14 repo. Since there are commits in libusb.git which are not included in those binaries it is significantly more helpful to use the git code for testing. > Find what the problem is by running strace ./rtl-sdr and matching > ioctls to the code. Please don't do that, it is not helpful. Please focus on creating a debug log as described on http://libusb.org/wiki/debug since that's very useful for those of us who know the libusb code. Thanks //Peter From yo3ggx at gmail.com Sat Oct 12 07:50:29 2013 From: yo3ggx at gmail.com (Dan) Date: Sat, 12 Oct 2013 10:50:29 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011155229.74764597@lembas.zaitcev.lan> References: <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258351D.1030803@gmail.com> <20131011155229.74764597@lembas.zaitcev.lan> Message-ID: <5258FF45.7000506@gmail.com> Hi Pete, On 10/12/2013 12:52 AM, Pete Zaitcev wrote: > On Fri, 11 Oct 2013 20:27:57 +0300 > Dan wrote: > >> LIBUSB_LIBS and LIBUSB_CFLAGS >> before running ./configure for rtl-sdr > That's a bit indirect. The best way is to run ldd ./myapp > > I continue to maintain that all this advice about installing "latest" > without knowing what's up is not likely to work. The stock libusb1 rpm > from Koji works just fine, I would not even bother rebuilding it, > just pull off an F14 repo. The version of libusb1 in F14 is 1.0.8-1, but in CentOS 6.2 is newer (1.0.9-0.6.rc1). I think now that I have another issue as I have tested with several libusb1-devel libraries, but without uninstalling original libusb1 from CentOS because of multiple dependencies. > Find what the problem is by running strace ./rtl-sdr and matching ioctls > to the code. I need to read as I'm not familiar with this... > -- Pete Thank you, Dan From yo3ggx at gmail.com Sat Oct 12 07:57:44 2013 From: yo3ggx at gmail.com (Dan) Date: Sat, 12 Oct 2013 10:57:44 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131011155229.74764597@lembas.zaitcev.lan> References: <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011071959.0e384ccb@korath.teln.shikadi.net> <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258351D.1030803@gmail.com> <20131011155229.74764597@lembas.zaitcev.lan> Message-ID: <525900F8.6010902@gmail.com> Hi Peter, On 10/12/2013 12:52 AM, Pete Zaitcev wrote: > I continue to maintain that all this advice about installing "latest" > without knowing what's up is not likely to work. The stock libusb1 rpm > from Koji works just fine, I would not even bother rebuilding it, just > pull off an F14 repo. I have tried to install both libusb1 and usb1-devel from F14 repo. The problem remain the same. -- 73 Dan YO3GGX http://www.yo3ggx.ro From yo3ggx at gmail.com Sat Oct 12 08:24:22 2013 From: yo3ggx at gmail.com (Dan) Date: Sat, 12 Oct 2013 11:24:22 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131012073417.17055.qmail@stuge.se> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258373A.3030500@gmail.com> <20131012073417.17055.qmail@stuge.se> Message-ID: <52590736.9030905@gmail.com> Hi Peter, On 10/12/2013 10:34 AM, Peter Stuge wrote: > I can understand that you can not upgrade kernel on the final system, > but it would be very helpful if you could test on a separate system, > with similar hardware, with a new kernel, to see if the problem persists. As I don't have a similar system with Linux (but I have a similar one with Windows where the rtlsdr library works perfect), I intend to install it on a virtual machine on the same hardware just to see if I still get the same errors. Is this a good ideea? What Linux version do you recommend to try with? > ldd is a good way to see what libraries will actually be loaded by a > given program. If indeed the CentOS package has been uninstalled then > ldd should confirm that the correct library file is being loaded. When I try 'ldd -v rtl_test' I get the message "not a dynamic executable" >> Find what the problem is by running strace ./rtl-sdr and matching >> ioctls to the code. > Please don't do that, it is not helpful. Please focus on creating a > debug log as described on http://libusb.org/wiki/debug since that's > very useful for those of us who know the libusb code. I'll do it. > > Thanks > > //Peter > Thanks, Dan From yo3ggx at gmail.com Sat Oct 12 09:19:38 2013 From: yo3ggx at gmail.com (Dan) Date: Sat, 12 Oct 2013 12:19:38 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131012073417.17055.qmail@stuge.se> References: <5251C4DE.4020902@gmail.com> <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258373A.3030500@gmail.com> <20131012073417.17055.qmail@stuge.se> Message-ID: <5259142A.9050105@gmail.com> Hi, I've done the following: - uninstall CentOS distribution libusb1 and libusb1-devel - download the latest libusb1 from git: http://git.libusb.org/libusb.git - automake.sh - make - make install - use the latest rtlsdr code from git - set the env variables as follows: export LIBUSB_LIBS="-L/usr/local/lib -lusb-1.0" export LIBUSB_LIBS="-L/usr/local/lib" - ./configure - make - make install Trying to run rtl_test I get a lot of debug messages. The full answer can be seen here: http://www.yo3ggx.ro/rtlsdr/rtltest.txt Thanks Dan On 10/12/2013 10:34 AM, Peter Stuge wrote: > Dan wrote: >>>> Any other hints? >>> Only to use the latest kernel code. >> I cannot change the kernel on the system I intend to use the dongle, >> as it provides other services which cannot be interrupted.. > I can understand that you can not upgrade kernel on the final system, > but it would be very helpful if you could test on a separate system, > with similar hardware, with a new kernel, to see if the problem persists. > > >>> Did you make sure that the rtl-sdr programs are in fact also using >>> the new libraries, as opposed to what is installed by CentOS which >>> is what will be used by default, when running them? >> Before this I've fully uninstalled the previous version and set the >> environment variables: >> LIBUSB_LIBS and LIBUSB_CFLAGS >> before running ./configure for rtl-sdr > That sounds good. It is important that you have uninstalled the > version provided by the CentOS package. > > > Pete Zaitcev wrote: >>> LIBUSB_LIBS and LIBUSB_CFLAGS >>> before running ./configure for rtl-sdr >> That's a bit indirect. The best way is to run ldd ./myapp > ldd is a good way to see what libraries will actually be loaded by a > given program. If indeed the CentOS package has been uninstalled then > ldd should confirm that the correct library file is being loaded. > > >> I continue to maintain that all this advice about installing "latest" >> without knowing what's up is not likely to work. > It's not about what will likely make things work, it's about doing > debugging with the current state of the code, so that I know that I > haven't already fixed the problem in libusb.git and so that I know > exactly what code is being used when the error occurs. > > >> The stock libusb1 rpm from Koji works just fine, I would not even >> bother rebuilding it, just pull off an F14 repo. > Since there are commits in libusb.git which are not included in those > binaries it is significantly more helpful to use the git code for > testing. > > >> Find what the problem is by running strace ./rtl-sdr and matching >> ioctls to the code. > Please don't do that, it is not helpful. Please focus on creating a > debug log as described on http://libusb.org/wiki/debug since that's > very useful for those of us who know the libusb code. > > > Thanks > > //Peter > -- 73 Dan YO3GGX http://www.yo3ggx.ro From peter at stuge.se Sun Oct 13 06:21:46 2013 From: peter at stuge.se (Peter Stuge) Date: Sun, 13 Oct 2013 08:21:46 +0200 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <5259142A.9050105@gmail.com> References: <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258373A.3030500@gmail.com> <20131012073417.17055.qmail@stuge.se> <5259142A.9050105@gmail.com> Message-ID: <20131013062146.18023.qmail@stuge.se> Dan wrote: > Hi, > > I've done the following: > - uninstall CentOS distribution libusb1 and libusb1-devel > - download the latest libusb1 from git: http://git.libusb.org/libusb.git > - automake.sh > - make > - make install > - use the latest rtlsdr code from git > - set the env variables as follows: > export LIBUSB_LIBS="-L/usr/local/lib -lusb-1.0" > export LIBUSB_LIBS="-L/usr/local/lib" > - ./configure > - make > - make install > Trying to run rtl_test I get a lot of debug messages. The full answer can > be seen here: > http://www.yo3ggx.ro/rtlsdr/rtltest.txt Thanks! I'll take a look at this and get back to you. //Peter From yo3ggx at gmail.com Sun Oct 13 07:07:55 2013 From: yo3ggx at gmail.com (Dan) Date: Sun, 13 Oct 2013 10:07:55 +0300 Subject: Problems on CentOS 6.4 (64 bit) In-Reply-To: <20131013062146.18023.qmail@stuge.se> References: <5256AC53.7030603@gmail.com> <20131011064754.602e548e@korath.teln.shikadi.net> <20131010145855.388fed9b@lembas.zaitcev.lan> <20131011041509.28982.qmail@stuge.se> <52580D44.5090609@gmail.com> <20131011164644.19514.qmail@stuge.se> <5258373A.3030500@gmail.com> <20131012073417.17055.qmail@stuge.se> <5259142A.9050105@gmail.com> <20131013062146.18023.qmail@stuge.se> Message-ID: <525A46CB.1080205@gmail.com> Hi Peter, On 10/13/2013 9:21 AM, Peter Stuge wrote: > Dan wrote: >> Hi, >> >> I've done the following: >> - uninstall CentOS distribution libusb1 and libusb1-devel >> - download the latest libusb1 from git: http://git.libusb.org/libusb.git >> - automake.sh >> - make >> - make install >> - use the latest rtlsdr code from git >> - set the env variables as follows: >> export LIBUSB_LIBS="-L/usr/local/lib -lusb-1.0" >> export LIBUSB_LIBS="-L/usr/local/lib" >> - ./configure >> - make >> - make install >> Trying to run rtl_test I get a lot of debug messages. The full answer can >> be seen here: >> http://www.yo3ggx.ro/rtlsdr/rtltest.txt > Thanks! I'll take a look at this and get back to you. > By the way... I've done nothing specific to generate this debug info. Is this the default build option in git code? > //Peter > Many thanks, Dan From skip.tavakkolian at gmail.com Mon Oct 21 17:57:46 2013 From: skip.tavakkolian at gmail.com (Skip Tavakkolian) Date: Mon, 21 Oct 2013 10:57:46 -0700 Subject: API for forwarding remote control commands Message-ID: Hi, Since all DVB-T receivers come with an IR remote control, I'm wondering if there is an API that can be used to receive the remote commands? Thanks, -Skip -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.jacobowitz at gmail.com Tue Oct 22 00:28:54 2013 From: david.jacobowitz at gmail.com (David Jacobowitz) Date: Mon, 21 Oct 2013 17:28:54 -0700 Subject: odd results working at 250ksp/s Message-ID: Hi, I've been working on a project the involves tuning VOR signals. They are narrow band signals. > 25 kHz. For that, the wide bandwidth of the RTL dongles isn't that helpful to me. (and actually a hindrance when two signals are inside the sample range but widely different strengths) Anyway, the lowest I can get my dongles (R820T) to go is 250ksps, which is fine. I've been working at that frequency for awhile, but getting some strange results. For example, if I tune in to 116.8 MHz, which should be the OAK VOR, it works fine. But if I tune to 115.8 MHz, which should be the SFO VOR I get ... the OAK VOR. That is, there is a perfect copy of the OAK signal 1 MHz shifted down. If I switch the sample rate to 1.024Msps or 900ksps, I don't get this problem. I don't understand what is happening here. 1 MHz is an even multiple of 250kHz, so maybe I'm getting an image of OAK overpowering the relatively weaker SFO signal. But should there not be filters that manage this? I guess I was expecting that if the device is set to 250ksps, then it would "close down" filters appropriately to reject signals out of that band. But maybe the filters don't work properly below a certain sample rate? Like the rtl2832 can sample down to 250ksps, but the 820T tuner was not designed for it? Or perhaps I'm doing something wrong? Can I control the filters directly? I'm glad I find this issue because I was going nuts thinking my software had some mysterious bug. But I can reproduce this issue just with SDR# or whatever. :-) Regards. Dave J -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Oct 22 08:29:28 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 22 Oct 2013 10:29:28 +0200 Subject: odd results working at 250ksp/s In-Reply-To: References: Message-ID: Hi, > I don't understand what is happening here. 1 MHz is an even multiple of > 250kHz, so maybe I'm getting an image of OAK overpowering the relatively > weaker SFO signal. But should there not be filters that manage this? Yes most likely an image. > I guess I was expecting that if the device is set to 250ksps, then it would > "close down" filters appropriately to reject signals out of that band. But > maybe the filters don't work properly below a certain sample rate? Like the > rtl2832 can sample down to 250ksps, but the 820T tuner was not designed for > it? The filters you'd need wouldn't be in the R820T anyway (it has filters but not that narrow). IIRC, the rtl2832 always sample at a fixed high frequency but it has an internal downconverter + FIR filter inside to convert the sample rate down. But that FIR probably can't handle such a big reduction ... > Can I control the filters directly? If you find out, let us know, but AFAIK all attempts so far didn't succeed to get it more narrow than this. Cheers, Sylvain From ralph at schmid.xxx Tue Oct 22 08:44:13 2013 From: ralph at schmid.xxx (Ralph A. Schmid, dk5ras) Date: Tue, 22 Oct 2013 10:44:13 +0200 Subject: odd results working at 250ksp/s In-Reply-To: References: Message-ID: <001801cecf02$e25f6570$a71e3050$@schmid.xxx> > The filters you'd need wouldn't be in the R820T anyway (it has filters but not > that narrow). > IIRC, the rtl2832 always sample at a fixed high frequency but it has an internal > downconverter + FIR filter inside to convert the sample rate down. But that > FIR probably can't handle such a big reduction ... Still we must not forget that we're talking about some piece of silicon with nm structures, and therefrom no extraordinarily sharp filtering can be expected. When analog meets digital, it is important that the analog part protects the ADC from being overwhelmed by strong signals that are not in the scope of interest. All those silicon-only broadband receiver concepts drastically fail when being directly connected to a real good antenna in urban vicinity. They are good for a rubber duck style antenna sitting on your table, but that's it. There's a reason for all the solid silver and brass stuff in real world receivers :) > Cheers, > > Sylvain Ralph. From david.jacobowitz at gmail.com Tue Oct 22 08:45:10 2013 From: david.jacobowitz at gmail.com (David Jacobowitz) Date: Tue, 22 Oct 2013 01:45:10 -0700 Subject: odd results working at 250ksp/s In-Reply-To: References: Message-ID: Thank you. You and another forum member have helped me understand the situation. I am beginning to see the attraction of SDR platforms that integrate an FPGA immediately after the ADC. You can have wide analog filtering going to an ADC running fast, and then apply digital filters in the FPGA before downsampling to a lower rate for consumption by what-have-you. I can accomplish the same completely in software; I'll set the sample rate high, then filter and decimate, probably in a few stages to keep the filters reasonable. I tried it this evening with some raw IQ recordings I made this afternoon and it works pretty well -- on a modern PC. Regards, Dave J On Tue, Oct 22, 2013 at 1:29 AM, Sylvain Munaut <246tnt at gmail.com> wrote: > Hi, > > > I don't understand what is happening here. 1 MHz is an even multiple of > > 250kHz, so maybe I'm getting an image of OAK overpowering the relatively > > weaker SFO signal. But should there not be filters that manage this? > > Yes most likely an image. > > > > I guess I was expecting that if the device is set to 250ksps, then it > would > > "close down" filters appropriately to reject signals out of that band. > But > > maybe the filters don't work properly below a certain sample rate? Like > the > > rtl2832 can sample down to 250ksps, but the 820T tuner was not designed > for > > it? > > The filters you'd need wouldn't be in the R820T anyway (it has filters > but not that narrow). > IIRC, the rtl2832 always sample at a fixed high frequency but it has > an internal downconverter + FIR filter inside to convert the sample > rate down. But that FIR probably can't handle such a big reduction ... > > > > Can I control the filters directly? > > If you find out, let us know, but AFAIK all attempts so far didn't > succeed to get it more narrow than this. > > > Cheers, > > Sylvain > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ralph at schmid.xxx Tue Oct 22 09:00:42 2013 From: ralph at schmid.xxx (Ralph A. Schmid, dk5ras) Date: Tue, 22 Oct 2013 11:00:42 +0200 Subject: odd results working at 250ksp/s In-Reply-To: References: Message-ID: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> Effective filtering must occur between antenna and receiver. All the problems that a saturated preamp and ADC cause can't be repaired by software. Never. Ralph. From: osmocom-sdr-bounces at lists.osmocom.org [mailto:osmocom-sdr-bounces at lists.osmocom.org] On Behalf Of David Jacobowitz Sent: Tuesday, October 22, 2013 10:45 AM To: Sylvain Munaut Cc: osmocom-sdr at lists.osmocom.org Subject: Re: odd results working at 250ksp/s Thank you. You and another forum member have helped me understand the situation. I am beginning to see the attraction of SDR platforms that integrate an FPGA immediately after the ADC. You can have wide analog filtering going to an ADC running fast, and then apply digital filters in the FPGA before downsampling to a lower rate for consumption by what-have-you. I can accomplish the same completely in software; I'll set the sample rate high, then filter and decimate, probably in a few stages to keep the filters reasonable. I tried it this evening with some raw IQ recordings I made this afternoon and it works pretty well -- on a modern PC. Regards, Dave J -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Oct 22 09:08:12 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 22 Oct 2013 11:08:12 +0200 Subject: odd results working at 250ksp/s In-Reply-To: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> References: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> Message-ID: > Effective filtering must occur between antenna and receiver. All the > problems that a saturated preamp and ADC cause can?t be repaired by > software. Never. But his original problem is not with saturated preamps or ADC ... it's aliasing ... and that can be solved in the digital domain provided fast enough ADC. Cheers, Sylvain From ralph at schmid.xxx Tue Oct 22 09:17:51 2013 From: ralph at schmid.xxx (Ralph A. Schmid, dk5ras) Date: Tue, 22 Oct 2013 11:17:51 +0200 Subject: odd results working at 250ksp/s In-Reply-To: References: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> Message-ID: <002e01cecf07$957bc3c0$c0734b40$@schmid.xxx> > But his original problem is not with saturated preamps or ADC ... it's aliasing ... > and that can be solved in the digital domain provided fast enough ADC. Yep - if this really is the problem. Aliasing-alike effects also often come from nonlinearities in the overdriven input stages...BTST, GTTS :) The RTL2832 shows this all the time, copies of strong signals show up in expected (from aliasing, proven by simply doing the maths) and not-so-expected areas of the spectrum. > Cheers, > > Sylvain Ralph. From 246tnt at gmail.com Tue Oct 22 09:37:46 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 22 Oct 2013 11:37:46 +0200 Subject: odd results working at 250ksp/s In-Reply-To: <002e01cecf07$957bc3c0$c0734b40$@schmid.xxx> References: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> <002e01cecf07$957bc3c0$c0734b40$@schmid.xxx> Message-ID: > Yep - if this really is the problem. From david.jacobowitz at gmail.com Tue Oct 22 15:07:04 2013 From: david.jacobowitz at gmail.com (David Jacobowitz) Date: Tue, 22 Oct 2013 08:07:04 -0700 Subject: odd results working at 250ksp/s In-Reply-To: <52664E0E.40400@earthlink.net> References: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> <52664E0E.40400@earthlink.net> Message-ID: I originally posted about 115.8 and 116.8 MHz, both square in the VOR band of 108 to 117.95. I might have sent something else in a PM, but if so it was a typo. :-) I am definitely only interested in the VOR band right now -- though, as you say, it is adjacent to commercial FM with its high power. My application is simple in concept: A fully auomatic VOR-based positioning system, a fallback from GPS. I want to scan the entire VOR band, looking for signals in the standard VOR format that can be demodulated. I do the initial scan with a fast sample rate and FFT, just looking for peaks. From those, I examine the signals to see if it looks like a VOR signal. From that list, I will "park" on each signal long enough (~30s) to decode the VOR's morse code station ID. From that, I will have a short list of VORs that I can currently receive. From those, if the geometry is appropriate (I know the VORs positions from a database) I can calculate a position. The software then just round-robin tunes the VORs in range and continually tries to calculate positions. If too many drop out, it returns to the initial scan mode. Not being able to receive this VOR or that VOR is not generally a problem, but obviously, the more the better. With extra VORs I have better options for choosing the closest ones or the ones with the best geometry. This is actually quite difficult to test, because VORs can generally only be received line-of-sight -- which means in the air. I'm a private pilot but I found that flying and noodling with a laptop is too much trouble. From jdowjunkmail at earthlink.net Tue Oct 22 19:17:22 2013 From: jdowjunkmail at earthlink.net (jdowjunkmail at earthlink.net) Date: Tue, 22 Oct 2013 12:17:22 -0700 Subject: odd results working at 250ksp/s In-Reply-To: References: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> <52664E0E.40400@earthlink.net> Message-ID: <5266CF42.9040401@earthlink.net> Use a 2.4 ksps sample rate and receive both of them. In general you want to stay away from the teat in the middle of the FFT, which is zero frequency on the input. That is a noisy spot due to semi-conductor physics. You can set then up with say a 250 kHz "IF" and a 750 kHz "IF" and in principle receive both at the same time. Of course you are going to graduate from this to receiving GPS, aren't you? {^_-} Joanne On 2013/10/22 08:07, David Jacobowitz wrote: > I originally posted about 115.8 and 116.8 MHz, both square in the VOR band of > 108 to 117.95. I might have sent something else in a PM, but if so it was a > typo. :-) I am definitely only interested in the VOR band right now -- though, > as you say, it is adjacent to commercial FM with its high power. > > My application is simple in concept: A fully auomatic VOR-based positioning > system, a fallback from GPS. I want to scan the entire VOR band, looking for > signals in the standard VOR format that can be demodulated. I do the initial > scan with a fast sample rate and FFT, just looking for peaks. From those, I > examine the signals to see if it looks like a VOR signal. From that list, I will > "park" on each signal long enough (~30s) to decode the VOR's morse code station > ID. From that, I will have a short list of VORs that I can currently receive. > From those, if the geometry is appropriate (I know the VORs positions from a > database) I can calculate a position. > > The software then just round-robin tunes the VORs in range and continually tries > to calculate positions. If too many drop out, it returns to the initial scan mode. > > Not being able to receive this VOR or that VOR is not generally a problem, but > obviously, the more the better. With extra VORs I have better options for > choosing the closest ones or the ones with the best geometry. > > > This is actually quite difficult to test, because VORs can generally only be > received line-of-sight -- which means in the air. I'm a private pilot but I > found that flying and noodling with a laptop is too much trouble. From my office > window, on a high floor in Oakland, CA, I can receive one VOR from the Oakland > airport. And I have now discovered a ridge near my home with a scenic overlook > from which I can receive two. > > I've tested the software enough to know that the initial scan function seems to > work, and the morse decoding kind of works, but I am not confident I'll get it > to work very well. (One transmitter's dit looks a lot like another's dah.) The > nav signal decoding is simple. (A 30 Hz AM modulated tone is phase compared with > a 30 Hz tone FM modulated at 9960 Hz. The phase obtained is the azimuth to the > station.) > > > If I ever get this working, I looking forward to sharing it with the community. > In the process of building this, I created a simple SDR toolkit of DSP > functions. It's like Gnuradio in concept, but 16b fixed-point, and has no > external dependencies, and C89, so is easier to build on weird and limited > platforms. It also has perl bindings. Compared to GR, it looks like the work of > a rank amateur just learning DSP, but I do like the concept of there being a > GR-like library out there, lightweight and embedded-friendly. > > > Regards, > Dave J > > > On Tue, Oct 22, 2013 at 3:06 AM, jdow > wrote: > > He sent me two frequencies in private email. These were in the FM > broadcast band (in the US). He probably needs to notch them out > in order to get adequate response. > > As for wanting narrow bandwidth - I am not quite sure why he thinks > that is a benefit. I use a large FFT (about 10 Hz per bin) and use > the zoom control to see fine detail. (Different FFT settings suite > different uses. This one seems to be a good compromise with my two > needs. I'm too lazy to change it.) > > {^_^} > > > > On 2013/10/22 02:08, Sylvain Munaut wrote: > > Effective filtering must occur between antenna and receiver. All the > problems that a saturated preamp and ADC cause can?t be repaired by > software. Never. > > > But his original problem is not with saturated preamps or ADC ... it's > aliasing ... and that can be solved in the digital domain provided > fast enough ADC. > > Cheers, > > Sylvain > > > From pashdown at xmission.com Wed Oct 23 23:28:35 2013 From: pashdown at xmission.com (Pete Ashdown) Date: Wed, 23 Oct 2013 17:28:35 -0600 Subject: rtl_fm stereo? Message-ID: <09C1DFBF-DFF2-45EE-B1AF-7F1DE6F87558@xmission.com> Tried searching on this and didn't find much. Is rtl_fm stereo capable? When I encode with lame's "-m s" flag the output is at half the sample rate (ie: speeded up). Do I need to feed it double the sample rate, or am I barking up the wrong tree entirely? Thank you. From stu at spacehopper.org Wed Oct 23 23:44:51 2013 From: stu at spacehopper.org (Stuart Henderson) Date: Thu, 24 Oct 2013 00:44:51 +0100 Subject: rtl_fm stereo? In-Reply-To: <09C1DFBF-DFF2-45EE-B1AF-7F1DE6F87558@xmission.com> References: <09C1DFBF-DFF2-45EE-B1AF-7F1DE6F87558@xmission.com> Message-ID: <20131023234451.GC8847@symphytum.spacehopper.org> On 2013/10/23 17:28, Pete Ashdown wrote: > Tried searching on this and didn't find much. Is rtl_fm stereo capable? When I encode with lame's "-m s" flag the output is at half the sample rate (ie: speeded up). Do I need to feed it double the sample rate, or am I barking up the wrong tree entirely? > > Thank you. There's a diff adding stereo support in the list archives, http://comments.gmane.org/gmane.comp.mobile.osmocom.sdr/299 From keenerd at gmail.com Wed Oct 23 23:53:33 2013 From: keenerd at gmail.com (keenerd) Date: Wed, 23 Oct 2013 19:53:33 -0400 Subject: rtl_fm stereo? In-Reply-To: <09C1DFBF-DFF2-45EE-B1AF-7F1DE6F87558@xmission.com> References: <09C1DFBF-DFF2-45EE-B1AF-7F1DE6F87558@xmission.com> Message-ID: On 10/23/13, Pete Ashdown wrote: > Tried searching on this and didn't find much. Is rtl_fm stereo capable? > When I encode with lame's "-m s" flag the output is at half the sample rate > (ie: speeded up). Do I need to feed it double the sample rate, or am I > barking up the wrong tree entirely? > > Thank you. > Nope, rtl_fm is not capable of stereo. -Kyle From jdow at earthlink.net Tue Oct 22 10:05:24 2013 From: jdow at earthlink.net (jdow) Date: Tue, 22 Oct 2013 03:05:24 -0700 Subject: odd results working at 250ksp/s In-Reply-To: <001801cecf02$e25f6570$a71e3050$@schmid.xxx> References: <001801cecf02$e25f6570$a71e3050$@schmid.xxx> Message-ID: <52664DE4.70207@earthlink.net> Sample rate is 28.8 MHz. That is your basic bandwidth starting point. With the E4000 delivering I and Q data for the sampler you have a starting bandwidth of 28.8 MHz. The R820T converts to around 3 MHz I only. That means the bandwidth is 0 to 14.4 MHz with the dongle slicing out up to 2.4 Msps of I/Q data. The R820T potentially has some interesting image issues if it is really delivering 3 MHz to the RTL chip and not 7 MHz. These are TV devices. That means any analog filtering they may or may not have is 6 to 8 MHz wide. So up front it has that is the bandwidth to worry about for strong signals. The RTL chip delivers as little as 250 ksps. The word I've heard from people who test the chip is that it's not very good for image (alias) rejection much below 1 Msps. So I simply live with the 2.4 Msps and learn to like it. SDRSharp more or less properly (more compromises than some) decimates this down to something usable. But there's no way to tell SDRSharp, "Really, Essdee, I'm only interested in this 200 kHz so please only show that in the FFT window." It could be done. The code would be only a little more complex. I don't worry about it. I use the zoom slider and Bob's my uncle. The fellow who posted the question indicates he's interested in VOR reception. That's a 10 MHz band between 108 MHz and 118 MHz. I have a hunch there is a small band near the FM broadcast band that's more or less useless. So 4 dongles with appropriate tuning could get all but about 400 kHz of that range all at once on a suitable computer. 5 could do it with considerable overlap. But one, really, could do the job if it knew what frequencies to tune to. One of the scanner tools would maybe make that a little easier. He'll likely want to use some 1/4 wave coax notch's since he indicated two frequencies that had huge signals were 1 MHz apart up around 106 MHz. That would make a big difference for his weak signal work. {^_^} On 2013/10/22 01:44, Ralph A. Schmid, dk5ras wrote: >> The filters you'd need wouldn't be in the R820T anyway (it has filters but not >> that narrow). >> IIRC, the rtl2832 always sample at a fixed high frequency but it has an internal >> downconverter + FIR filter inside to convert the sample rate down. But that >> FIR probably can't handle such a big reduction ... > > Still we must not forget that we're talking about some piece of silicon with nm > structures, and therefrom no extraordinarily sharp filtering can be expected. > When analog meets digital, it is important that the analog part protects the > ADC from being overwhelmed by strong signals that are not in the scope of > interest. > > All those silicon-only broadband receiver concepts drastically fail when being > directly connected to a real good antenna in urban vicinity. They are good for > a rubber duck style antenna sitting on your table, but that's it. > > There's a reason for all the solid silver and brass stuff in real world receivers :) > >> Cheers, >> >> Sylvain > > Ralph. > > > From jdow at earthlink.net Tue Oct 22 10:06:06 2013 From: jdow at earthlink.net (jdow) Date: Tue, 22 Oct 2013 03:06:06 -0700 Subject: odd results working at 250ksp/s In-Reply-To: References: <001c01cecf05$30435bf0$90ca13d0$@schmid.xxx> Message-ID: <52664E0E.40400@earthlink.net> He sent me two frequencies in private email. These were in the FM broadcast band (in the US). He probably needs to notch them out in order to get adequate response. As for wanting narrow bandwidth - I am not quite sure why he thinks that is a benefit. I use a large FFT (about 10 Hz per bin) and use the zoom control to see fine detail. (Different FFT settings suite different uses. This one seems to be a good compromise with my two needs. I'm too lazy to change it.) {^_^} On 2013/10/22 02:08, Sylvain Munaut wrote: >> Effective filtering must occur between antenna and receiver. All the >> problems that a saturated preamp and ADC cause can?t be repaired by >> software. Never. > > But his original problem is not with saturated preamps or ADC ... it's > aliasing ... and that can be solved in the digital domain provided > fast enough ADC. > > Cheers, > > Sylvain > > From lightningbolts at gmail.com Mon Oct 28 19:41:01 2013 From: lightningbolts at gmail.com (Chris Hanson) Date: Mon, 28 Oct 2013 15:41:01 -0400 Subject: rtl_fm.exe issue or an I doing something wrong? Message-ID: I just downloaded the RelWithDebInfo precompiled windows software that was posted on Oct 24th. I am using an E4000 dongle which has a PPM of +30. I am trying to listen to 424.175MHz and I'm using this: rtl_fm -p 30 -d 1 -N -o 4 -f 424.175M -s 16k -C|sox -r 16000 -t .raw -e signed-integer -b 16 -c 1 -V1 - -d everything is playing fine. I can hear 424.175MHz. The issue is that I'm hearing another station 50KHz higher on 424.225Mhz in addition to the frequency I want. So it looks as if it's not using a 16Khz filter. Am I doing something wrong or is there an issue with rtl_fm.exe? Thanks Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From keenerd at gmail.com Mon Oct 28 22:19:31 2013 From: keenerd at gmail.com (keenerd) Date: Mon, 28 Oct 2013 18:19:31 -0400 Subject: rtl_fm.exe issue or an I doing something wrong? In-Reply-To: References: Message-ID: On 10/28/13, Chris Hanson wrote: > I am trying to listen to 424.175MHz and I'm using this: > > rtl_fm -p 30 -d 1 -N -o 4 -f 424.175M -s 16k -C|sox -r 16000 -t .raw -e > signed-integer -b 16 -c 1 -V1 - -d That looks correct. > The issue is that I'm > hearing another station 50KHz higher on 424.225Mhz in addition to the > frequency I want. So it looks as if it's not using a 16Khz filter. Am I > doing something wrong or is there an issue with rtl_fm.exe? Thanks It is a minor issue with rtl_fm. The (very fast) downsample filter tends to leak in places. Soon this will be replaced with better filters. There is a better/slower filter that can be enabled with -F. Check your --help and confirm that -F is present and says 'hamming' in the description. -Kyle From m0zjo at qsl.net Wed Oct 30 19:14:36 2013 From: m0zjo at qsl.net (Jonathan Rawlinson) Date: Wed, 30 Oct 2013 19:14:36 +0000 Subject: RTL-SDR Error code -3 Message-ID: Hello all I am trying to get the python wrapper "pyrtlsdr" working on Windows, it works fine on Linux The dongle works fine in SDR-SHARP.exe It imports correctly but prints the following error when I try to initialize the Dongle: Traceback (most recent call last): File "C:\Users\M0ZJO\Desktop\RA_Astro\FFTPrint Test.py", line 4, in sdr = RtlSdr() File "build\bdist.win32\egg\rtlsdr\rtlsdr.py", line 60, in __init__ % (result, device_index)) IOError: Error code -3 when opening SDR (device index = 0) RTL_FM also returns the same error. Can anyone help? I would be very grateful! Many thanks Jonathan/M0ZJO -------------- next part -------------- An HTML attachment was scrubbed... URL: From pelletier.michel at gmail.com Wed Oct 30 19:53:11 2013 From: pelletier.michel at gmail.com (Michel Pelletier) Date: Wed, 30 Oct 2013 12:53:11 -0700 Subject: RTL-SDR Error code -3 In-Reply-To: References: Message-ID: libusb docs indicate that -3 is: http://libusb.sourceforge.net/api-1.0.16/group__misc.html#ggab2323aa0f04bc22038e7e1740b2f29efa131f3c2f6f2bb40bc6fb60ccb6f3152f LIBUSB_ERROR_ACCESS Access denied (insufficient permissions) Sounds like you have a permission problem? Best I can do to help you, I've never even seen a windows machine. :) -Michel On Wed, Oct 30, 2013 at 12:14 PM, Jonathan Rawlinson wrote: > > Hello all > > I am trying to get the python wrapper "pyrtlsdr" working on Windows, it works fine on Linux > > The dongle works fine in SDR-SHARP.exe > It imports correctly but prints the following error when I try to initialize the Dongle: > > Traceback (most recent call last): > File "C:\Users\M0ZJO\Desktop\RA_Astro\FFTPrint Test.py", line 4, in > sdr = RtlSdr() > File "build\bdist.win32\egg\rtlsdr\rtlsdr.py", line 60, in __init__ > % (result, device_index)) > IOError: Error code -3 when opening SDR (device index = 0) > > RTL_FM also returns the same error. > Can anyone help? I would be very grateful! > > Many thanks > > Jonathan/M0ZJO -------------- next part -------------- An HTML attachment was scrubbed... URL: From skip.tavakkolian at gmail.com Thu Oct 31 19:17:36 2013 From: skip.tavakkolian at gmail.com (Skip Tavakkolian) Date: Thu, 31 Oct 2013 12:17:36 -0700 Subject: I/Q data for dummies Message-ID: I'm not an RF engineer and know enough of the physics of it to be dangerous. My approach to rtl-sdr is purely utilitarian -- i.e. using it to develop applications. The following tutorial, by Mikael Q Kuisma, on I/Q data was very useful to me and might benefit others on the list. http://whiteboard.ping.se/SDR/IQ -Skip -------------- next part -------------- An HTML attachment was scrubbed... URL: