Hi, I'm using HackRF with Surface Pro 3 and I have no problem at all.
What I did: Install SDR Sharp on c:/app/ folder, run zadig and that's it! I also found a script that updates automatically SDR# and all the plugins, so I made an archive you can find here (password protected: use "hackrf" as password): http://dl.free.fr/t1xgvUydy 1. Extract the rar file (using the password "hackrf") 2. Put the folder sdrsharp extracted to a folder on your computer (like c:/app/) 3. Then go to c:/app/sdrsharp/ SDR#-Update/ 4. Launch the setup.bat, => sdrsharp will be updated with the latest version, and the plugins from http://www.rtl-sdr.ru too. Hope this wil help someone! Regards Cedrick -----Message d'origine----- De : HackRF-dev [mailto:[email protected]] De la part de [email protected] Envoyé : vendredi 12 septembre 2014 07:32 À : [email protected] Objet : HackRF-dev Digest, Vol 21, Issue 17 Send HackRF-dev mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://nine.pairlist.net/mailman/listinfo/hackrf-dev or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of HackRF-dev digest..." Today's Topics: 1. Re: Testing a new HackRF One (Simon Brown) 2. hackrf antenna choices (Jeremy Young) 3. Re: hackrf antenna choices (n0p [Luis Bernal]) 4. hackrf-dev (foxtail) 5. Minimum Interface in Windows ([email protected]) 6. PyBOMBS Install (Rich Sanders) 7. favorite Broadcast FM radio on GNU radio? (Duane Snider) 8. Re: hackrf-dev (Michael Ossmann) 9. Re: favorite Broadcast FM radio on GNU radio? (Michael Ossmann) 10. Powering an external LNA via the Antenna port in GRC (Douglas Theriault) 11. PyBombs Install (Rich Sanders) 12. Re: favorite Broadcast FM radio on GNU radio? (Larry DiGioia) 13. Re: PyBombs Install (Rich Sanders) 14. Just got mine. (David Hickman) 15. Re: Just got mine. (Zezrum Ironforge) 16. Re: PyBombs Install (West, Nathan) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Sep 2014 06:37:39 +0100 From: "Simon Brown" <[email protected]> To: "'Dave Smith'" <[email protected]>, <[email protected]> Subject: Re: [Hackrf-dev] Testing a new HackRF One Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Dave, 1) The hackRF is only 8 bits, remember this. 2) In the SDR Console there?s a display adjustment, I usually set this to -20dB. 3) You could be overloading the front end, with only 8 bits resolution you have to be very careful. 4) Post screenshots! Simon Brown G4ELI http://v2.sdr-radio.com From: HackRF-dev [mailto:[email protected]] On Behalf Of Dave Smith Sent: 11 September 2014 01:12 To: [email protected] Subject: Re: [Hackrf-dev] Testing a new HackRF One On Tue, Aug 12, 2014 at 22:59:34PM EDT, Jon B wrote: > I'm not sure my new HackRF One works. I'm having exactly the same problem, with SDR# I see a noise floor at about -70-75dB and almost nothing else. I've checked drivers, LNA/VGA settings, and so on as other people have suggested, and used a log-periodic and generic monopole and get the same results. With SDR Console I get better results (signals are visible), but I can't demodulate any of the signals I see. The results are really strange, AM signals in various places on the FM band (you can tell it's AM from both the waterfall diagram and trying to demodulate). They're unlikely to be images because they only appear in the FM band (it looks like there's a marker every 10MHz, I assume there's some clock in the HackRF that's doing that). I've also found SDR# to be pretty flaky, it wants to write its config into its install location under %ProgramFiles% and then dies with an exception when it can't, and after pressing start/stop a few times first the spectrum display freezes (although the waterfall continues) and then the waterfall goes as well, at which point I need to reset the HackRF to restore operation. SDR Console doesn't have this problem so I'm not sure if it's SDR# messing up the HackRF config or SDR# screwing itself up. Dave. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140911/8c14da97 /attachment-0001.html> ------------------------------ Message: 2 Date: Wed, 10 Sep 2014 22:50:34 -0700 From: Jeremy Young <[email protected]> To: [email protected] Subject: [Hackrf-dev] hackrf antenna choices Message-ID: <cagkomabcj5tmsfjqybsb7ka+15mywjf7kavznz8umhjpp34...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" The ant500 is a 50 ohm antenna, there are some DIY adsb antenna plans out there, is it safe to use one of these with the hackrf? what do I need to look out for when choosing antenna? Thanks Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140910/f845bd99 /attachment-0001.html> ------------------------------ Message: 3 Date: Thu, 11 Sep 2014 08:40:57 +0200 From: "n0p [Luis Bernal]" <[email protected]> To: Jeremy Young <[email protected]> Cc: [email protected] Subject: Re: [Hackrf-dev] hackrf antenna choices Message-ID: <CAOKTV6=gKYj_mi2A6rpBnCH=cXAQE=rbyhqad77f4exetl9...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" If you are only going to receive, impedance is not critical. But txing is another story, impedances should be matched or you can blow up something. Although the hackrf has very little power and shouldn't have any problem dissipating reflected power from an impedance mismatch. You should be looking for antennas tuned to the part of the spectrum you want to work with and consider what polarization (vertical, horizontal, RHCP/LHCP) and if you want directionality. 2014-09-11 7:50 GMT+02:00 Jeremy Young <[email protected]>: > The ant500 is a 50 ohm antenna, there are some DIY adsb antenna plans > out there, is it safe to use one of these with the hackrf? what do I > need to look out for when choosing antenna? > > Thanks > Jeremy > > _______________________________________________ > HackRF-dev mailing list > [email protected] > http://nine.pairlist.net/mailman/listinfo/hackrf-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140911/9294aa4f /attachment-0001.html> ------------------------------ Message: 4 Date: Wed, 10 Sep 2014 21:04:46 -0400 From: foxtail <[email protected]> To: <[email protected]> Subject: [Hackrf-dev] hackrf-dev Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" I see that the P9 connector has the baseband. Is this like a tap of the discriminator In a vhf/uhf scanner? I tried it with a 10k res. on the + out to a pc based sound card. Nothing appeared on that output. Just wondering how to make that happen if so. Should I try with the res. removed and see if anything changes? Thanks for your time! Thank you, [email protected] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140910/ba9fbebc /attachment-0001.html> ------------------------------ Message: 5 Date: Thu, 11 Sep 2014 06:13:26 -0700 From: "[email protected]" <[email protected]> To: <[email protected]> Subject: [Hackrf-dev] Minimum Interface in Windows Message-ID: <B672806F39344C01B4D37927E9DC7C53@Zeke> Content-Type: text/plain; charset="utf-8" Is anyone working on a minimum open source interface to HackRF for Windows? Something in C++ or C#? Marcus ? Thanks for pointing me to the Git for the DLL Jim W6KYP www.SETI.Net -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140911/d46c2e77 /attachment-0001.html> ------------------------------ Message: 6 Date: Thu, 11 Sep 2014 09:43:08 -0400 From: Rich Sanders <[email protected]> To: [email protected] Subject: [Hackrf-dev] PyBOMBS Install Message-ID: <CACcO=ewth5qy3d+37ww+-avzxw7qr-ddewqio6ykx73dd9c...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" If anyone feels like giving PyBOMBS a go. Reportedly, the gnurdio-install script is going to lose support in favor of PyBOMBS. Installing Pybombs The general disclaimer?..This technique/approach has worked for me various times, it is the method I prefer, it may not work for you. You might prefer other steps. I assume no liability. Pybombs is not perfect, some recipes do not work. I always start with a fresh Ubuntu load, this one is based on Ubuntu 14. After install, perform the typical: apt-get update apt-get dist-upgrade Pybombs will by default try to install all dependencies, but I have found the install goes much smoother if I install some packages in advance: type* sudo apt-get -y install git-core cmake g++ python-dev swig pkg-config libfftw3-dev libcppunit-dev libgsl0-dev libusb-dev libsdl1.2-dev python-wxgtk2.8 python-numpy python-cheetah python-lxml doxygen libxi-dev python-sip libqt4-opengl-dev libqwt-dev libfontconfig1-dev libxrender-dev python-qwt5-qt4 python-sip python-sip-dev cmake xorg-dev libglu1-mesa-dev* reboot terminal into your home directory type* git clone git://github.com/pybombs/pybombs <http://github.com/pybombs/pybombs>* type *cd pybombs* type *./pybombs config* In the configuration setup you can press enter for every option, I changed the install prefix location because this helps prevent errors when I manually install non pybombs packages later on, if you are only going to use pybombs ?recipes? leave the default location. If you change to "/usr/local" you'll have to run "sudo ./pybombs config" after the config files run Output of ./pybombs config Initializing config file... Username for GIT access gituser [user]: Install Prefix prefix [/home/user/target]:/usr/local/ Order in which to attempt installations when available, options are: src, rpm, deb satisfy_order [deb,src]: Comma seperated list of package names to assume are already installed forcepkgs []: Time the monitor thread waits (in seconds) before retrying downloads timeout [30]: CMAKE_BUILD_TYPE args to pass to cmake projects, options are: Debug, Release, RelWithDebInfo, MinSizeRel, cmakebuildtype [RelWithDebInfo]: Build doxygen while compiling packages? options are: ON, OFF builddocs [OFF]: C Compiler Executable [gcc, clang, icc, etc] cc [gcc]: C++ Compiler Executable [g++, clang++, icpc, etc] cxx [g++]: Concurrent make threads [1,2,4,8...] makewidth [4]: done Settled on prefix: /usr/local [Errno 13] Permission denied: '/usr/local/lib64' Error! Configured install prefix requires root privileges. Please re-run as sudo! This error is normal if you ran sudo ./pybombs config, rerun the config typing *sudo ./pybombs config* Output of ./pybombs config Settled on prefix: /usr/local Initializing environmental variables... /usr/local//python/:/usr/local//lib/python2.6/site-packages/:/usr/local//lib 64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-packages/:/usr/lo cal//lib64/python2.6/dist-packages/:/usr/local//lib/python2.7/site-packages/ :/usr/local//lib64/python2.7/site-packages/:/usr/local//lib/python2.7/dist-p ackages/:/usr/local//lib64/python2.7/dist-packages/:/usr/local//python/:/usr /local//lib/python2.6/site-packages/:/usr/local//lib64/python2.6/site-packag es/:/usr/local//lib/python2.6/dist-packages/:/usr/local//lib64/python2.6/dis t-packages/:/usr/local//lib/python2.7/site-packages/:/usr/local//lib64/pytho n2.7/site-packages/:/usr/local//lib/python2.7/dist-packages/:/usr/local//lib 64/python2.7/dist-packages/ no existing inventory found, creating an empty one... ---------- loading recipes ------------------- Loading recipes ... Loading recipes ... done ---------- loading recipes finished ---------- gituser = user prefix = /usr/local/ satisfy_order = deb,src forcepkgs = timeout = 30 cmakebuildtype = RelWithDebInfo builddocs = OFF cc = gcc cxx = g++ makewidth = 4 *from this point forward, you only need "sudo" if you installed into a custom directory instead of the default /home/user/target* type *sudo ./pybombs install gnuradio* THIS WILL TAKE A WHILE When it is done type *sudo ./app_store.py* Click on the packages you want to install, you can only install one at a time. The app_store may go dark. You can monitor the progress in the terminal window that you launched app_store in. If everything installs correctly, the app_store will brighten and your terminal window will display "installation ok via: src" if it errored out, the app_store will close and your terminal window will have some information. I suggest starting with gr-osmosdr (<--- this will install many of your app_store blocks such as hackrf and osmosdr) and gr-pyqt By default, the Ettus block will load, however, some minor configuration is required to get the B200 and B210 running correctly, if there is interest, I will update this to include. Click the "X" to exit the app_store. type *sudo ./pybombs env* Using the Ubuntu file manager, navigate to the location listed after running ./pybombs env. Open setup_env.sh and copy everything below the following line: # WARNING: This file is auto-generated by pybombs, any manual changes to it may be overwritten! It should look similar to: export PATH="/usr/local//bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sb in:/bin:/usr/lib64/qt4/bin/" export PYTHONPATH="/usr/local//python/:/usr/local//lib/python2.6/site-packages/:/us r/local//lib64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-packa ges/:/usr/local//lib64/python2.6/dist-packages/:/usr/local//lib/python2.7/si te-packages/:/usr/local//lib64/python2.7/site-packages/:/usr/local//lib/pyth on2.7/dist-packages/:/usr/local//lib64/python2.7/dist-packages/:/usr/local// python/:/usr/local//lib/python2.6/site-packages/:/usr/local//lib64/python2.6 /site-packages/:/usr/local//lib/python2.6/dist-packages/:/usr/local//lib64/p ython2.6/dist-packages/:/usr/local//lib/python2.7/site-packages/:/usr/local/ /lib64/python2.7/site-packages/:/usr/local//lib/python2.7/dist-packages/:/us r/local//lib64/python2.7/dist-packages/" export LD_LIBRARY_PATH="/usr/local//lib/:/usr/local//lib64/:" export PKG_CONFIG_PATH="/usr/local//lib/pkgconfig/:/usr/local//lib64/pkgconfig/:" In the termianl window, CD to your home directory type *sudo nano .bashrc *(the SUDO is needed here or the file will not save) scroll to the bottom and paste the copied lines, then Ctrl X, Yes, Enter After adding new recipes, you need to re-run the ./pybombs env command and update your .bashrc type *git clone https://github.com/mossmann/hackrf.git <https://github.com/mossmann/hackrf.git>* type *cd hackrf/host/libhackrf*/ type *mkdir build* type *cd build* type *cmake ..* type *make* type *sudo make install* type *sudo ldconfig* copy /home/hackrf/host/libhackrf/53-hackrf.rules to /etc/udev/rules.d type *sudo udevadm control --reload-rules* reboot type *hackrf_info* You should see something SIMILAR to: Found HackRF board. Board ID Number: 2 (HackRF One) Firmware Version: git-44df9d1 Part ID Number: 0xa000cb3c 0x004d4f3f Serial Number: 0x00000000 0x00000000 0x457863c8 0x2f1b511f type *gnuradio-companion* Gnu-radio should open If you need to update the firmware, follow Mike's directions at: https://github.com/mossmann/hackrf/wiki/Updating-Firmware You should be good to go! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140911/3431e7ef /attachment-0001.html> ------------------------------ Message: 7 Date: Thu, 11 Sep 2014 09:04:17 -0700 From: Duane Snider <[email protected]> To: "[email protected]" <[email protected]> Subject: [Hackrf-dev] favorite Broadcast FM radio on GNU radio? Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 I'm seeing signs of life with HackRF on GNU radio with the Ubuntu Live DVD and the OsmoSDR source. Is there a favorite FM radio example out there? So far I'm seeing these two: http://www.stargazing.net/david/GNUradio/RTLFMstations.html http://www.oz9aec.net/index.php/grc-examples I'd like to document some simple methods of get receiving a weather station and an FM radio station. ------------------------------ Message: 8 Date: Thu, 11 Sep 2014 10:02:38 -0600 From: Michael Ossmann <[email protected]> To: foxtail <[email protected]> Cc: [email protected] Subject: Re: [Hackrf-dev] hackrf-dev Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii On Wed, Sep 10, 2014 at 09:04:46PM -0400, foxtail wrote: > > I see that the P9 connector has the baseband. Is this like a tap of > the discriminator In a vhf/uhf scanner? No, it is not. It provides access to the raw analog inputs and outputs from the ADC/DAC. I strongly suggest getting very familiar with the schematic diagram and reading the MAX5864 datasheet before plugging things into P9. Mike ------------------------------ Message: 9 Date: Thu, 11 Sep 2014 10:05:29 -0600 From: Michael Ossmann <[email protected]> To: Duane Snider <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [Hackrf-dev] favorite Broadcast FM radio on GNU radio? Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii On Thu, Sep 11, 2014 at 09:04:17AM -0700, Duane Snider wrote: > > Is there a favorite FM radio example out there? http://greatscottgadgets.com/sdr/1 ------------------------------ Message: 10 Date: Thu, 11 Sep 2014 09:17:25 -0700 From: Douglas Theriault <[email protected]> To: [email protected] Subject: [Hackrf-dev] Powering an external LNA via the Antenna port in GRC Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii I see on the schematic and in options under hackrf_transfer -p a means to provide 3.3v out the antenna port. I am wondering if there is means to turn this on via the osmosdr source block in GRC or is this limited to only using the hackrf_transfer utility. The properties under the osmosdr source block in GRC shows option for ch 0: antenna that I've tried with value 1 or 0 but didn't seem to toggle the power on. Has anyone been successful in powering an external LNA using the 3.3v from the antenna port on HackRF ONE via GRC? thanks, Doug ------------------------------ Message: 11 Date: Thu, 11 Sep 2014 13:43:27 -0400 From: Rich Sanders <[email protected]> To: [email protected] Subject: [Hackrf-dev] PyBombs Install Message-ID: <CACcO=ExmMYRig1zr-NO-=1wKpcKwV3PvgJviVPQtnBrU61xu=w...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Apologies if I sent this out twice. If anyone feels like giving PyBOMBS a go. Reportedly, the gnurdio-install script is going to lose support in favor of PyBOMBS. Installing Pybombs The general disclaimer?..This technique/approach has worked for me various times, it is the method I prefer, it may not work for you. You might prefer other steps. I assume no liability. Pybombs is not perfect, some recipes do not work. I always start with a fresh Ubuntu load, this one is based on Ubuntu 14. After install, perform the typical: apt-get update apt-get dist-upgrade Pybombs will by default try to install all dependencies, but I have found the install goes much smoother if I install some packages in advance: type* sudo apt-get -y install git-core cmake g++ python-dev swig pkg-config libfftw3-dev libcppunit-dev libgsl0-dev libusb-dev libsdl1.2-dev python-wxgtk2.8 python-numpy python-cheetah python-lxml doxygen libxi-dev python-sip libqt4-opengl-dev libqwt-dev libfontconfig1-dev libxrender-dev python-qwt5-qt4 python-sip python-sip-dev cmake xorg-dev libglu1-mesa-dev* reboot terminal into your home directory type* git clone git://github.com/pybombs/pybombs <http://github.com/pybombs/pybombs>* type *cd pybombs* type *./pybombs config* In the configuration setup you can press enter for every option, I changed the install prefix location because this helps prevent errors when I manually install non pybombs packages later on, if you are only going to use pybombs ?recipes? leave the default location. If you change to "/usr/local" you'll have to run "sudo ./pybombs config" after the config files run Output of ./pybombs config Initializing config file... Username for GIT access gituser [user]: Install Prefix prefix [/home/user/target]:/usr/local/ Order in which to attempt installations when available, options are: src, rpm, deb satisfy_order [deb,src]: Comma seperated list of package names to assume are already installed forcepkgs []: Time the monitor thread waits (in seconds) before retrying downloads timeout [30]: CMAKE_BUILD_TYPE args to pass to cmake projects, options are: Debug, Release, RelWithDebInfo, MinSizeRel, cmakebuildtype [RelWithDebInfo]: Build doxygen while compiling packages? options are: ON, OFF builddocs [OFF]: C Compiler Executable [gcc, clang, icc, etc] cc [gcc]: C++ Compiler Executable [g++, clang++, icpc, etc] cxx [g++]: Concurrent make threads [1,2,4,8...] makewidth [4]: done Settled on prefix: /usr/local [Errno 13] Permission denied: '/usr/local/lib64' Error! Configured install prefix requires root privileges. Please re-run as sudo! This error is normal if you ran sudo ./pybombs config, rerun the config typing *sudo ./pybombs config* Output of ./pybombs config Settled on prefix: /usr/local Initializing environmental variables... /usr/local//python/:/usr/local//lib/python2.6/site-packages/:/usr/local//lib 64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-packages/:/usr/lo cal//lib64/python2.6/dist-packages/:/usr/local//lib/python2.7/site-packages/ :/usr/local//lib64/python2.7/site-packages/:/usr/local//lib/python2.7/dist-p ackages/:/usr/local//lib64/python2.7/dist-packages/:/usr/local//python/:/usr /local//lib/python2.6/site-packages/:/usr/local//lib64/python2.6/site-packag es/:/usr/local//lib/python2.6/dist-packages/:/usr/local//lib64/python2.6/dis t-packages/:/usr/local//lib/python2.7/site-packages/:/usr/local//lib64/pytho n2.7/site-packages/:/usr/local//lib/python2.7/dist-packages/:/usr/local//lib 64/python2.7/dist-packages/ no existing inventory found, creating an empty one... ---------- loading recipes ------------------- Loading recipes ... Loading recipes ... done ---------- loading recipes finished ---------- gituser = user prefix = /usr/local/ satisfy_order = deb,src forcepkgs = timeout = 30 cmakebuildtype = RelWithDebInfo builddocs = OFF cc = gcc cxx = g++ makewidth = 4 *from this point forward, you only need "sudo" if you installed into a custom directory instead of the default /home/user/target* type *sudo ./pybombs install gnuradio* THIS WILL TAKE A WHILE When it is done type *sudo ./app_store.py* Click on the packages you want to install, you can only install one at a time. The app_store may go dark. You can monitor the progress in the terminal window that you launched app_store in. If everything installs correctly, the app_store will brighten and your terminal window will display "installation ok via: src" if it errored out, the app_store will close and your terminal window will have some information. I suggest starting with gr-osmosdr (<--- this will install many of your app_store blocks such as hackrf and osmosdr) and gr-pyqt By default, the Ettus block will load, however, some minor configuration is required to get the B200 and B210 running correctly, if there is interest, I will update this to include. Click the "X" to exit the app_store. type *sudo ./pybombs env* Using the Ubuntu file manager, navigate to the location listed after running ./pybombs env. Open setup_env.sh and copy everything below the following line: # WARNING: This file is auto-generated by pybombs, any manual changes to it may be overwritten! It should look similar to: export PATH="/usr/local//bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sb in:/bin:/usr/lib64/qt4/bin/" export PYTHONPATH="/usr/local//python/:/usr/local//lib/python2.6/site-packages/:/us r/local//lib64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-packa ges/:/usr/local//lib64/python2.6/dist-packages/:/usr/local//lib/python2.7/si te-packages/:/usr/local//lib64/python2.7/site-packages/:/usr/local//lib/pyth on2.7/dist-packages/:/usr/local//lib64/python2.7/dist-packages/:/usr/local// python/:/usr/local//lib/python2.6/site-packages/:/usr/local//lib64/python2.6 /site-packages/:/usr/local//lib/python2.6/dist-packages/:/usr/local//lib64/p ython2.6/dist-packages/:/usr/local//lib/python2.7/site-packages/:/usr/local/ /lib64/python2.7/site-packages/:/usr/local//lib/python2.7/dist-packages/:/us r/local//lib64/python2.7/dist-packages/" export LD_LIBRARY_PATH="/usr/local//lib/:/usr/local//lib64/:" export PKG_CONFIG_PATH="/usr/local//lib/pkgconfig/:/usr/local//lib64/pkgconfig/:" In the termianl window, CD to your home directory type *sudo nano .bashrc *(the SUDO is needed here or the file will not save) scroll to the bottom and paste the copied lines, then Ctrl X, Yes, Enter After adding new recipes, you need to re-run the ./pybombs env command and update your .bashrc type *git clone https://github.com/mossmann/hackrf.git <https://github.com/mossmann/hackrf.git>* type *cd hackrf/host/libhackrf*/ type *mkdir build* type *cd build* type *cmake ..* type *make* type *sudo make install* type *sudo ldconfig* copy /home/hackrf/host/libhackrf/53-hackrf.rules to /etc/udev/rules.d type *sudo udevadm control --reload-rules* reboot type *hackrf_info* You should see something SIMILAR to: Found HackRF board. Board ID Number: 2 (HackRF One) Firmware Version: git-44df9d1 Part ID Number: 0xa000cb3c 0x004d4f3f Serial Number: 0x00000000 0x00000000 0x457863c8 0x2f1b511f type *gnuradio-companion* Gnu-radio should open If you need to update the firmware, follow Mike's directions at: https://github.com/mossmann/hackrf/wiki/Updating-Firmware You should be good to go! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140911/913600f0 /attachment-0001.html> ------------------------------ Message: 12 Date: Thu, 11 Sep 2014 14:30:39 -0400 From: Larry DiGioia <[email protected]> To: Duane Snider <[email protected]>, [email protected] Subject: Re: [Hackrf-dev] favorite Broadcast FM radio on GNU radio? Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed I also personally had the most success with this, compared to all other methods... but I was using GQRX. I was able to actually pull in 3 or 4 FM stations instead of only one, and the frequencies were correct for the first time... but still no signals to speak of anywhere else - no 10 or 15MHz WWV, no 2-meter FM, etc. On 9/11/2014 12:04 PM, Duane Snider wrote: > I'm seeing signs of life with HackRF on GNU radio with the Ubuntu Live > DVD and the OsmoSDR source. > > Is there a favorite FM radio example out there? > > So far I'm seeing these two: > http://www.stargazing.net/david/GNUradio/RTLFMstations.html > http://www.oz9aec.net/index.php/grc-examples > > > I'd like to document some simple methods of get receiving a weather > station and an FM radio station. > > > _______________________________________________ > HackRF-dev mailing list > [email protected] > http://nine.pairlist.net/mailman/listinfo/hackrf-dev ------------------------------ Message: 13 Date: Thu, 11 Sep 2014 19:11:26 -0400 From: Rich Sanders <[email protected]> To: Assaf mischari <[email protected]> Cc: [email protected] Subject: Re: [Hackrf-dev] PyBombs Install Message-ID: <CACcO=Eyb9Xm14qyp8R+O3ngBcnnL=kyFbX=zk93xxcbav+6...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" It sounds like a driver or firmware conflict. Could you provide some more details? What version of Ubuntu? What firmware is your Hackrf? try resetting hackrf try reinstalling libhackrf try a different usb port try ./pybombs clean hackrf and then ./pybombs install hackrf On Thu, Sep 11, 2014 at 4:01 PM, Assaf mischari <[email protected]> wrote: > Hi all > > GnuRadio was working well , and then i upgraded to release 1.8.2014 + > re-installed everything with pybombs to get the latest . > Now - gqrx is working , but gnuradio has this error : > > FATAL: No supported devices found to pick from > > also hackrf_info works every other time .... > > what am i doing wrong ? > assaf > (ubuntu 14.04) > > On Thu, Sep 11, 2014 at 8:43 PM, Rich Sanders <[email protected]> > wrote: > >> Apologies if I sent this out twice. >> >> If anyone feels like giving PyBOMBS a go. Reportedly, the >> gnurdio-install script is going to lose support in favor of PyBOMBS. >> >> Installing Pybombs >> >> The general disclaimer?..This technique/approach has worked for me >> various times, it is the method I prefer, it may not work for you. >> You might prefer other steps. I assume no liability. >> >> Pybombs is not perfect, some recipes do not work. >> >> I always start with a fresh Ubuntu load, this one is based on Ubuntu 14. >> >> After install, perform the typical: >> >> apt-get update >> apt-get dist-upgrade >> >> Pybombs will by default try to install all dependencies, but I have >> found the install goes much smoother if I install some packages in advance: >> >> type* sudo apt-get -y install git-core cmake g++ python-dev swig >> pkg-config libfftw3-dev libcppunit-dev libgsl0-dev libusb-dev >> libsdl1.2-dev >> python-wxgtk2.8 python-numpy python-cheetah python-lxml doxygen >> libxi-dev python-sip libqt4-opengl-dev libqwt-dev libfontconfig1-dev >> libxrender-dev >> python-qwt5-qt4 python-sip python-sip-dev cmake xorg-dev >> libglu1-mesa-dev* >> >> reboot >> >> terminal into your home directory >> >> type* git clone git://github.com/pybombs/pybombs >> <http://github.com/pybombs/pybombs>* >> type *cd pybombs* >> type *./pybombs config* >> >> In the configuration setup you can press enter for every option, I >> changed the install prefix location because this helps prevent errors >> when I manually install non pybombs packages later on, if you are >> only going to use pybombs ?recipes? leave the default location. If >> you change to "/usr/local" you'll have to run "sudo ./pybombs config" >> after the config files run >> >> Output of ./pybombs config >> >> Initializing config file... >> Username for GIT access >> gituser [user]: >> Install Prefix prefix [/home/user/target]:/usr/local/ Order in which >> to attempt installations when available, options are: src, rpm, deb >> satisfy_order [deb,src]: >> Comma seperated list of package names to assume are already installed >> forcepkgs []: >> Time the monitor thread waits (in seconds) before retrying downloads >> timeout [30]: >> CMAKE_BUILD_TYPE args to pass to cmake projects, options are: Debug, >> Release, RelWithDebInfo, MinSizeRel, cmakebuildtype [RelWithDebInfo]: >> Build doxygen while compiling packages? options are: ON, OFF >> builddocs >> [OFF]: >> C Compiler Executable [gcc, clang, icc, etc] cc [gcc]: >> C++ Compiler Executable [g++, clang++, icpc, etc] cxx [g++]: >> Concurrent make threads [1,2,4,8...] makewidth [4]: >> done >> Settled on prefix: /usr/local >> >> [Errno 13] Permission denied: '/usr/local/lib64' >> Error! Configured install prefix requires root privileges. Please >> re-run as sudo! >> >> This error is normal if you ran sudo ./pybombs config, rerun the >> config typing *sudo ./pybombs config* >> >> Output of ./pybombs config >> >> Settled on prefix: /usr/local >> Initializing environmental variables... >> >> /usr/local//python/:/usr/local//lib/python2.6/site-packages/:/usr/loc >> al//lib64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-pac >> kages/:/usr/local//lib64/python2.6/dist-packages/:/usr/local//lib/pyt >> hon2.7/site-packages/:/usr/local//lib64/python2.7/site-packages/:/usr >> /local//lib/python2.7/dist-packages/:/usr/local//lib64/python2.7/dist >> -packages/:/usr/local//python/:/usr/local//lib/python2.6/site-package >> s/:/usr/local//lib64/python2.6/site-packages/:/usr/local//lib/python2 >> .6/dist-packages/:/usr/local//lib64/python2.6/dist-packages/:/usr/loc >> al//lib/python2.7/site-packages/:/usr/local//lib64/python2.7/site-pac >> kages/:/usr/local//lib/python2.7/dist-packages/:/usr/local//lib64/pyt >> hon2.7/dist-packages/ no existing inventory found, creating an empty >> one... >> ---------- loading recipes ------------------- Loading recipes ... >> Loading recipes ... done >> ---------- loading recipes finished ---------- >> >> gituser = user >> prefix = /usr/local/ >> satisfy_order = deb,src >> forcepkgs = >> timeout = 30 >> cmakebuildtype = RelWithDebInfo >> builddocs = OFF >> cc = gcc >> cxx = g++ >> makewidth = 4 >> >> *from this point forward, you only need "sudo" if you installed into >> a custom directory instead of the default /home/user/target* >> >> type *sudo ./pybombs install gnuradio* >> >> THIS WILL TAKE A WHILE >> >> When it is done type *sudo ./app_store.py* >> >> Click on the packages you want to install, you can only install one >> at a time. The app_store may go dark. You can monitor the progress >> in the terminal window that you launched app_store in. If everything >> installs correctly, the app_store will brighten and your terminal >> window will display "installation ok via: src" if it errored out, >> the app_store will close and your terminal window will have some information. >> >> I suggest starting with gr-osmosdr (<--- this will install many of >> your app_store blocks such as hackrf and osmosdr) and gr-pyqt >> >> By default, the Ettus block will load, however, some minor >> configuration is required to get the B200 and B210 running correctly, >> if there is interest, I will update this to include. >> >> Click the "X" to exit the app_store. >> >> type *sudo ./pybombs env* >> >> Using the Ubuntu file manager, navigate to the location listed after >> running ./pybombs env. Open setup_env.sh and copy everything below >> the following line: >> >> # WARNING: This file is auto-generated by pybombs, any manual changes >> to it may be overwritten! >> >> It should look similar to: >> >> export >> PATH="/usr/local//bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sb in:/bin:/usr/lib64/qt4/bin/" >> export >> PYTHONPATH="/usr/local//python/:/usr/local//lib/python2.6/site-packages/:/us r/local//lib64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-packa ges/:/usr/local//lib64/python2.6/dist-packages/:/usr/local//lib/python2.7/si te-packages/:/usr/local//lib64/python2.7/site-packages/:/usr/local//lib/pyth on2.7/dist-packages/:/usr/local//lib64/python2.7/dist-packages/:/usr/local// python/:/usr/local//lib/python2.6/site-packages/:/usr/local//lib64/python2.6 /site-packages/:/usr/local//lib/python2.6/dist-packages/:/usr/local//lib64/p ython2.6/dist-packages/:/usr/local//lib/python2.7/site-packages/:/usr/local/ /lib64/python2.7/site-packages/:/usr/local//lib/python2.7/dist-packages/:/us r/local//lib64/python2.7/dist-packages/" >> export LD_LIBRARY_PATH="/usr/local//lib/:/usr/local//lib64/:" >> export >> PKG_CONFIG_PATH="/usr/local//lib/pkgconfig/:/usr/local//lib64/pkgconfig/:" >> >> In the termianl window, CD to your home directory >> >> type *sudo nano .bashrc *(the SUDO is needed here or the file will >> not >> save) >> >> scroll to the bottom and paste the copied lines, then Ctrl X, Yes, >> Enter >> >> After adding new recipes, you need to re-run the ./pybombs env >> command and update your .bashrc >> >> type *git clone https://github.com/mossmann/hackrf.git >> <https://github.com/mossmann/hackrf.git>* >> >> type *cd hackrf/host/libhackrf*/ >> >> type *mkdir build* >> >> type *cd build* >> >> type *cmake ..* >> >> type *make* >> >> type *sudo make install* >> >> type *sudo ldconfig* >> >> copy /home/hackrf/host/libhackrf/53-hackrf.rules to /etc/udev/rules.d >> >> type *sudo udevadm control --reload-rules* >> >> reboot >> >> type *hackrf_info* >> >> You should see something SIMILAR to: >> >> Found HackRF board. >> Board ID Number: 2 (HackRF One) >> Firmware Version: git-44df9d1 >> Part ID Number: 0xa000cb3c 0x004d4f3f Serial Number: 0x00000000 >> 0x00000000 0x457863c8 0x2f1b511f >> >> type *gnuradio-companion* >> >> Gnu-radio should open >> >> If you need to update the firmware, follow Mike's directions at: >> >> https://github.com/mossmann/hackrf/wiki/Updating-Firmware >> >> You should be good to go! >> >> _______________________________________________ >> HackRF-dev mailing list >> [email protected] >> http://nine.pairlist.net/mailman/listinfo/hackrf-dev >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140911/c2e81422 /attachment-0001.html> ------------------------------ Message: 14 Date: Thu, 11 Sep 2014 18:37:42 -0500 From: David Hickman <[email protected]> To: "[email protected]" <[email protected]> Subject: [Hackrf-dev] Just got mine. Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii I can not get it to work with sdr# on a surface 3 windows 8.1. Sdr sharp is current from last week and works great with my rtl dongle. I ran zadig and installed the driver. Ideas? Sent from my iPhone ------------------------------ Message: 15 Date: Thu, 11 Sep 2014 21:43:19 -0600 From: Zezrum Ironforge <[email protected]> To: David Hickman <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Re: [Hackrf-dev] Just got mine. Message-ID: <caavizrrifvgczypm1ig3nfpz-o-j_u1vhuu496nx5d+4ynt...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Can you be more descriptive on what isn't working? (SP3 user here) On Thu, Sep 11, 2014 at 5:37 PM, David Hickman <[email protected]> wrote: > I can not get it to work with sdr# on a surface 3 windows 8.1. > > Sdr sharp is current from last week and works great with my rtl dongle. > > > I ran zadig and installed the driver. > > Ideas? > > Sent from my iPhone > _______________________________________________ > HackRF-dev mailing list > [email protected] > http://nine.pairlist.net/mailman/listinfo/hackrf-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://nine.pairlist.net/pipermail/hackrf-dev/attachments/20140911/7ff9fad6 /attachment-0001.html> ------------------------------ Message: 16 Date: Thu, 11 Sep 2014 22:49:59 -0500 From: "West, Nathan" <[email protected]> To: Rich Sanders <[email protected]> Cc: [email protected] Subject: Re: [Hackrf-dev] PyBombs Install Message-ID: <CALkxiLJweSHqqvt=9lahg2wkqckxnvwn07gvjznpy2yaoa5...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On Thu, Sep 11, 2014 at 12:43 PM, Rich Sanders <[email protected]> wrote: > Apologies if I sent this out twice. > > If anyone feels like giving PyBOMBS a go. Reportedly, the > gnurdio-install script is going to lose support in favor of PyBOMBS. > > Installing Pybombs > > The general disclaimer?..This technique/approach has worked for me > various times, it is the method I prefer, it may not work for you. > You might prefer other steps. I assume no liability. > > Pybombs is not perfect, some recipes do not work. Can you report these as bugs to either pybombs or module author as appropriate? > > I always start with a fresh Ubuntu load, this one is based on Ubuntu 14. > > After install, perform the typical: > > apt-get update > apt-get dist-upgrade > > Pybombs will by default try to install all dependencies, but I have > found the install goes much smoother if I install some packages in advance: > > type sudo apt-get -y install git-core cmake g++ python-dev swig > pkg-config libfftw3-dev libcppunit-dev libgsl0-dev libusb-dev > libsdl1.2-dev > python-wxgtk2.8 python-numpy python-cheetah python-lxml doxygen > libxi-dev python-sip libqt4-opengl-dev libqwt-dev libfontconfig1-dev > libxrender-dev > python-qwt5-qt4 python-sip python-sip-dev cmake xorg-dev > libglu1-mesa-dev > > reboot > > terminal into your home directory > > type git clone git://github.com/pybombs/pybombs > type cd pybombs > type ./pybombs config > > In the configuration setup you can press enter for every option, I > changed the install prefix location because this helps prevent errors > when I manually install non pybombs packages later on, if you are only > going to use pybombs ?recipes? leave the default location. If you change to "/usr/local" > you'll have to run "sudo ./pybombs config" after the config files run > > Output of ./pybombs config > > Initializing config file... > Username for GIT access > gituser [user]: > Install Prefix prefix [/home/user/target]:/usr/local/ Order in which > to attempt installations when available, options are: src, rpm, deb > satisfy_order [deb,src]: > Comma seperated list of package names to assume are already installed > forcepkgs []: > Time the monitor thread waits (in seconds) before retrying downloads > timeout > [30]: > CMAKE_BUILD_TYPE args to pass to cmake projects, options are: Debug, > Release, RelWithDebInfo, MinSizeRel, cmakebuildtype [RelWithDebInfo]: > Build doxygen while compiling packages? options are: ON, OFF builddocs > [OFF]: > C Compiler Executable [gcc, clang, icc, etc] cc [gcc]: > C++ Compiler Executable [g++, clang++, icpc, etc] cxx [g++]: > Concurrent make threads [1,2,4,8...] makewidth [4]: > done > Settled on prefix: /usr/local > > [Errno 13] Permission denied: '/usr/local/lib64' > Error! Configured install prefix requires root privileges. Please > re-run as sudo! > > This error is normal if you ran sudo ./pybombs config, rerun the > config typing sudo ./pybombs config > > Output of ./pybombs config > > Settled on prefix: /usr/local > Initializing environmental variables... > /usr/local//python/:/usr/local//lib/python2.6/site-packages/:/usr/loca > l//lib64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-packa > ges/:/usr/local//lib64/python2.6/dist-packages/:/usr/local//lib/python > 2.7/site-packages/:/usr/local//lib64/python2.7/site-packages/:/usr/loc > al//lib/python2.7/dist-packages/:/usr/local//lib64/python2.7/dist-pack > ages/:/usr/local//python/:/usr/local//lib/python2.6/site-packages/:/us > r/local//lib64/python2.6/site-packages/:/usr/local//lib/python2.6/dist > -packages/:/usr/local//lib64/python2.6/dist-packages/:/usr/local//lib/ > python2.7/site-packages/:/usr/local//lib64/python2.7/site-packages/:/u > sr/local//lib/python2.7/dist-packages/:/usr/local//lib64/python2.7/dis > t-packages/ no existing inventory found, creating an empty one... > ---------- loading recipes ------------------- Loading recipes ... > Loading recipes ... done > ---------- loading recipes finished ---------- > > gituser = user > prefix = /usr/local/ > satisfy_order = deb,src > forcepkgs = > timeout = 30 > cmakebuildtype = RelWithDebInfo > builddocs = OFF > cc = gcc > cxx = g++ > makewidth = 4 > > from this point forward, you only need "sudo" if you installed into a > custom directory instead of the default /home/user/target > > type sudo ./pybombs install gnuradio > > THIS WILL TAKE A WHILE > > When it is done type sudo ./app_store.py > > Click on the packages you want to install, you can only install one at > a time. The app_store may go dark. You can monitor the progress in > the terminal window that you launched app_store in. If everything > installs correctly, the app_store will brighten and your terminal > window will display "installation ok via: src" if it errored out, the > app_store will close and your terminal window will have some information. > > I suggest starting with gr-osmosdr (<--- this will install many of > your app_store blocks such as hackrf and osmosdr) and gr-pyqt > > By default, the Ettus block will load, however, some minor > configuration is required to get the B200 and B210 running correctly, > if there is interest, I will update this to include. > > Click the "X" to exit the app_store. > > type sudo ./pybombs env > > Using the Ubuntu file manager, navigate to the location listed after > running ./pybombs env. Open setup_env.sh and copy everything below > the following > line: > > # WARNING: This file is auto-generated by pybombs, any manual changes > to it may be overwritten! > > It should look similar to: > > export > PATH="/usr/local//bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sb in:/bin:/usr/lib64/qt4/bin/" > export > PYTHONPATH="/usr/local//python/:/usr/local//lib/python2.6/site-packages/:/us r/local//lib64/python2.6/site-packages/:/usr/local//lib/python2.6/dist-packa ges/:/usr/local//lib64/python2.6/dist-packages/:/usr/local//lib/python2.7/si te-packages/:/usr/local//lib64/python2.7/site-packages/:/usr/local//lib/pyth on2.7/dist-packages/:/usr/local//lib64/python2.7/dist-packages/:/usr/local// python/:/usr/local//lib/python2.6/site-packages/:/usr/local//lib64/python2.6 /site-packages/:/usr/local//lib/python2.6/dist-packages/:/usr/local//lib64/p ython2.6/dist-packages/:/usr/local//lib/python2.7/site-packages/:/usr/local/ /lib64/python2.7/site-packages/:/usr/local//lib/python2.7/dist-packages/:/us r/local//lib64/python2.7/dist-packages/" > export LD_LIBRARY_PATH="/usr/local//lib/:/usr/local//lib64/:" > export > PKG_CONFIG_PATH="/usr/local//lib/pkgconfig/:/usr/local//lib64/pkgconfig/:" > > In the termianl window, CD to your home directory > > type sudo nano .bashrc (the SUDO is needed here or the file will not > save) > > scroll to the bottom and paste the copied lines, then Ctrl X, Yes, > Enter > > After adding new recipes, you need to re-run the ./pybombs env command > and update your .bashrc > > type git clone https://github.com/mossmann/hackrf.git > > type cd hackrf/host/libhackrf/ > > type mkdir build > > type cd build > > type cmake .. > > type make > > type sudo make install > > type sudo ldconfig > > copy /home/hackrf/host/libhackrf/53-hackrf.rules to /etc/udev/rules.d > > type sudo udevadm control --reload-rules > > reboot > > type hackrf_info > > You should see something SIMILAR to: > > Found HackRF board. > Board ID Number: 2 (HackRF One) > Firmware Version: git-44df9d1 > Part ID Number: 0xa000cb3c 0x004d4f3f > Serial Number: 0x00000000 0x00000000 0x457863c8 0x2f1b511f > > type gnuradio-companion > > Gnu-radio should open > > If you need to update the firmware, follow Mike's directions at: > > https://github.com/mossmann/hackrf/wiki/Updating-Firmware > > You should be good to go! > > _______________________________________________ > HackRF-dev mailing list > [email protected] > http://nine.pairlist.net/mailman/listinfo/hackrf-dev > ------------------------------ Subject: Digest Footer _______________________________________________ HackRF-dev mailing list [email protected] http://nine.pairlist.net/mailman/listinfo/hackrf-dev ------------------------------ End of HackRF-dev Digest, Vol 21, Issue 17 ****************************************** _______________________________________________ HackRF-dev mailing list [email protected] http://nine.pairlist.net/mailman/listinfo/hackrf-dev
