Read the mailing list of the GNU project right here! The information here is regarding the GNU radio project for USRP radios.
Monday, December 30, 2013
[Discuss-gnuradio] undocumented SBX behavior
Re: [Discuss-gnuradio] Playback
Dan CaJacob
Tom:What would you recommend if my data was recorded at 50M for about 15 seconds and I would like to double to playback time with a throttle. If I set the throttle to 25M, would that do the trick, or is it more complicated than that? I'm waiting for a new shipment of RAM, and once I have that I will be able to play around with things, but I just thought I would query the group to get a good starting point.Thanks.On Mon, Dec 30, 2013 at 8:52 AM, Paul B. Huter <paul.b.huter@gmail.com> wrote:
Sounds good, thanks.
Paul B. Huter
On Dec 30, 2013 8:51 AM, "Tom Rondeau" <tom@trondeau.com> wrote:On Thu, Dec 26, 2013 at 5:31 PM, Paul B. Huter <paul.b.huter@gmail.com> wrote:
> Is there a way to slow the playback of a data file through an FFT Sink? If I
> recorded at 50M and I set my FFT rate to 25M, would that result in playback
> twice as long?
>
> Thanks.
No, the sample rate of the FFT sink is just for display purposes: it
sets the range of the x-axis and nothing more.
If you want to slow down your display, assuming there is no hardware
in the loop, you can use a throttle block with a fairly low rate.
Tom
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Playback
Sounds good, thanks.
Paul B. Huter
On Dec 30, 2013 8:51 AM, "Tom Rondeau" <tom@trondeau.com> wrote:On Thu, Dec 26, 2013 at 5:31 PM, Paul B. Huter <paul.b.huter@gmail.com> wrote:
> Is there a way to slow the playback of a data file through an FFT Sink? If I
> recorded at 50M and I set my FFT rate to 25M, would that result in playback
> twice as long?
>
> Thanks.
No, the sample rate of the FFT sink is just for display purposes: it
sets the range of the x-axis and nothing more.
If you want to slow down your display, assuming there is no hardware
in the loop, you can use a throttle block with a fairly low rate.
Tom
[Discuss-gnuradio] Newbie quesion about building C++ blocks/SWIG/Python
/root/grc/DAB/lib:/root/grc/DAB/lib/.libs:/root/grc/DAB/swig:/root/grc/DAB/swig/.libs:/root/grc/DAB/python:/usr/local/lib/python2.7/dist-packages:/usr/local/lib/python2.7/dist-packages:
Traceback (most recent call last):
File "./qa_bondcut.py", line 25, in <module>
import howto_swig
File "/root/grc/DAB/swig/howto_swig.py", line 26, in <module>
_howto_swig = swig_import_helper()
File "/root/grc/DAB/swig/howto_swig.py", line 18, in swig_import_helper
import _howto_swig
ImportError: /root/grc/DAB/lib/.libs/libgnuradio-howto-3.3.0.so.0: undefined symbol: _ZTI8gr_block
Long story short: Install the missing package (apt-get install libfftw3-dev) and rebuild the gsm-receiver. Then it works."
Re: [Discuss-gnuradio] Bug: gr-qtgui: wrong design of variable-type blocks for GRC (category /GUI Widgets/QT)
> posted partial bugfix to github (pull request #122)
Artem,
Thanks. I've got this queued up with a few other patches and am just
waiting on confirmation on one more thing (holiday delays) before it
gets pushed.
Tom
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Successful installation of GNURadio 3.6.4.1 on Window XP and Windows 8
Thanks for your effort on not only getting GNU Radio working on
Windows but also providing us with the steps you took to get there.
That could be really helpful to a lot of people. I have made a link on
our WindowsInstall wiki to point to your email for other people
looking for help.
Please note, though, that we've tried to make it very clear that
Windows is not a fully supported OS. None of the core developers can
really test and build on Windows, and we rely on patches and feedback
like you've provided from the community. We do our best to keep things
working cross-platform, but as you've experienced, as versions change
(both GNU Radio and it's dependencies), this is a serious project.
Tom
On Thu, Dec 26, 2013 at 11:10 AM, Bhaskar11 <niceguy108@gmail.com> wrote:
> After much experimentation I have finally found a way to successfully
> install and fully run GRC 3.6.4.1 both under Windows XP and Windows 8. I
> presume it should therefore work equally well under Vista and 7.
>
> First a few comments on the common causes of problems that most people have
> had:
>
> a. It is critical to have the correct *matching* and *complete* versions of
> the various required libraries. Most installations instructions online fail
> because of this reason. The Ettus installation instructions officially
> recommended on GNURadio website and provided here fail now because many of
> the original binary versions referred to are no longer available. Hence
> those instructions are now outdated and should be replaced by the
> instructions provided in this email.
>
> b. Although it is possible to successfully install GNURadio binaries for
> versions 3.7.x, none of them include runtime DLLs for WX GUI blocks. Hence
> these blocks are not displayed, and so most of the example files available
> cannot be used as they need WX GUI blocks. Moreover, some of the QT GUI
> blocks do not work in certain versions. Since I do not know how to make
> these binaries, I request those who have created these version 3.7.x Windows
> binaries to repack them so that we can run the latest versions of GNURadio
> in Windows. Until that is done, there is no point trying to install those
> versions.
>
> c. Only GNURadio version 3.6.x binaries have WX GUI blocks. But versions
> 3.6.2 does not allow moving the blocks. Only 3.6.4.1 is usable, and works
> perfectly well for all available examples tested so far including all QT GUI
> and WX GUI blocks.
>
> d. The required Python libraries versions are available only for Python
> version 2.7.3 and are NOT all available for versions 2.7.6 or above, or at
> least I could not find them online. Hence we have to use libraries
> compatible only with Python 2.7.3.
>
> e. Some library versions have their quirks or bugs. For example PyGTK 2.24.0
> does not allow you to add blocks in GRC. Only version PyGTK 2.24.2 works ok.
> Also wxPython binary called "wxPython2.8-win32-unicode-2.8.12.1-py27" just
> does not work, but the same version but different binary called
> "wxPython-2.8.12.1.win32-py2.7" works correctly. Most online instructions do
> not mention the need for "wxPython-common" library, which is absolutely
> necessary. Also some odd problems such as this cease to exist when the
> correct libraries are matched.
>
> f. In the instructions below I have listed all the correct working libraries
> and binaries with links from which to download them. Please use only the
> binaries from these links and install them in the sequence provided. Other
> versions or binaries may not work. Keep all default options unless otherwise
> specified here. If you have problems working with the instructions below,
> check your binaries, and ensure that you are doing a clean install.
>
> Finally, please share your experiences with success and failures on this
> list so that others may benefit.
>
> Instructions to install GNURadio in Windows XP and Windows 8:
>
> 1. Uninstall all earlier installations and libraries of GNURadio and Python
> and their add-ons. Ensure that the GNURadio directory and Python directory
> are entirely removed by the uninstalls.
> For Windows XP GNURadio default directory is: C:\Program Files\gnuradio
> For Windows 8 it is: C:\Program Files (x86)\gnuradio
> For all platforms the Python default directory is: C:\Python27
> Both the GNURadio and Python directories should be non-existent. If they
> still exist, then delete them and reboot. We want as clean an install as
> possible.
>
> 2. Download "Microsoft Visual C++ 2010 Redistributable Package (x86)" from
> here and install "vcredist_x86".
> If it says a copy is already installed and offers to repair it, and accept
> to repair. If it says a later version is already installed, then accept to
> close.
>
> 3. Download and install "python-2.7.3.msi" from here.
>
> 4. Download and install "lxml-3.0.2.win32-py2.7" from here.
>
> 5. Download and install "numpy-1.7.1-win32-superpack-python2.7" from here.
>
> 6. Download and install "PyQt-Py2.7-x86-gpl-4.9.6-1" from here.
> (Note: Keep all default options. You do NOT need to change anything.)
>
> 7. Download and install "PyQwt-5.2.1-py2.7-x32-pyqt4.9.6-numpy1.7.1" from
> here.
>
> 8. Download and install "Cheetah-2.4.4.win32-py2.7" from here.
>
> 9. Download and install "PyOpenGL-3.1.0a1.win32-py2.7" from here.
>
> 10. Download and install "pygtk-all-in-one-2.24.2.win32-py2.7" from here.
>
> 11. Download and install "wxPython-2.8.12.1.win32-py2.7" from here.
> On Windows 8 you may get: Runtime error R6034 "An application has made an
> attempt to load the C runtime library incorrectly. Please contact the
> application's support team for more information." Ignore the message and
> continue.
>
> 12. Download and install "wxPython-common-2.8.12.1.win32-py2.7" from here.
> On Windows 8 you may get: Runtime error R6034 "An application has made an
> attempt to load the C runtime library incorrectly. Please contact the
> application's support team for more information." Ignore the message and
> continue.
>
> 13. Download and install "gnuradio_3.6.4.1_Win32" (stable version) from
> here.
> Select the option to "Add gnuradio to the system path for all users".
>
> On Windows 8 you may receive "Warning! PATH too long installer unable to
> modify PATH!" which seems to be a NSIS installer problem when it finds the
> total path to be longer than 1024. If you receive this message then you must
> manually add the installation bin directory to the system path.
> For Windows XP the PATH variable must include: "C:\Program
> Files\gnuradio\bin;"
> For Windows 8 the PATH must include: "C:\Program Files (x86)\gnuradio\bin;"
> The string can be added to the beginning of the PATH to ensure it gets
> priority. In any case manually verify that the Path has been correctly set
> as above whether by the installer or by you.
>
> 15. Manually add the PYTHONPATH environment variable.
> For Windows XP this is normally: "PYTHONPATH=C:\Program
> Files\gnuradio\lib\site-packages"
> For Windows 8 this is: "PYTHONPATH=C:\Program Files
> (x86)\gnuradio\lib\site-packages"
>
> 16. Check that the GRC_BLOCKS_PATH environment variable has been set to by
> GNURadio installer. Normally this should happen automatically. If it has not
> been set, then set it manually.
> For Windows XP this is: "GRC_BLOCKS_PATH=C:\Program
> Files\gnuradio\share\gnuradio\grc\blocks"
> For Windows 8 this is: "GRC_BLOCKS_PATH=C:\Program Files
> (x86)\gnuradio\share\gnuradio\grc\blocks"
>
> 17. Install any other hardware drivers that you need such as UHD, etc.
>
> 18. To run, in the command line type:
> gnuradio-companion.py
>
> If you like you can create a batch file to run this from a shortcut from the
> menu or the desktop.
>
> Hope this guide saves you many hours of wasted time so that you can fully
> enjoy the wonderful GNURadio experience!!
>
> B
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Playback
Sounds good, thanks.
Paul B. Huter
On Thu, Dec 26, 2013 at 5:31 PM, Paul B. Huter <paul.b.huter@gmail.com> wrote:
> Is there a way to slow the playback of a data file through an FFT Sink? If I
> recorded at 50M and I set my FFT rate to 25M, would that result in playback
> twice as long?
>
> Thanks.
No, the sample rate of the FFT sink is just for display purposes: it
sets the range of the x-axis and nothing more.
If you want to slow down your display, assuming there is no hardware
in the loop, you can use a throttle block with a fairly low rate.
Tom
Re: [Discuss-gnuradio] Playback
> Is there a way to slow the playback of a data file through an FFT Sink? If I
> recorded at 50M and I set my FFT rate to 25M, would that result in playback
> twice as long?
>
> Thanks.
No, the sample rate of the FFT sink is just for display purposes: it
sets the range of the x-axis and nothing more.
If you want to slow down your display, assuming there is no hardware
in the loop, you can use a throttle block with a fairly low rate.
Tom
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] how arrays work
> I wrote this array under the
> interp_ff_impl::work(int noutput_items,
> gr_vector_const_void_star &input_items,
> gr_vector_void_star &output_items)
>
> int f[m];
> I could not initialise by
> int f[m]={0};
> block is also not work can we write array like the above in gnuradio c++ code
This is really a C++ question and not a GNU Radio question. But,
anyways, without more information about 'm', I would say no, generally
this is not acceptable C++ code since you're trying to create an array
with a variable as the size of the array.
But look to the C++ forums and reask the question there if you cannot find it.
Tom
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] IEEE 802.11 a
> First of all thanks for your suggestion,
> I am using gnuradio 3.7 & started installation of ieee 802.11 from https://github.com/bastibl/gr-ieee802-11 During installation of log4cpp & IT++ for sudo port install log4cpp I was getting sudo:port:command not found. After successful installation of gr_ieee802.11, when I was running example ofdm_loopback.grc, it is not showing entire blocks & giving error
If either apt-get or port worked that's fine.
> <<< Welcome to GNU Radio Companion 3.7.1-52 >>>
>
> Loading: "/home/naveen/gr-ieee802-11/examples/ofdm_loopback.grc"
> >>> Error: Block key "blocks_ctrlport_monitor_performance" not found in Platform - grc(GNU Radio Companion)
You installed GNU Radio without performance counters. This block is only for profiling, so no problem. I will remove it from the flow graphs.
> >>> Error: Block key "ieee802_11_ofdm_parse_mac" not found in Platform - grc(GNU Radio Companion)
I guess you installed the module with a different CMAKE_INSTALL_PREFIX and thus, the blocks ended up in a different directory and GRC can't find them. I added this to the Readme, please see
https://github.com/bastibl/gr-ieee802-11/commit/cee6ec82a8356db8fad7496c2617a5d3fac4b0e5
> >>> Error: Block key "ofdm_phy_hier" not found in Platform - grc(GNU Radio Companion)
You did not install the hierarchical block as Kartik wrote.
> >>> Error: Block key "ieee802_11_ofdm_mac" not found in Platform - grc(GNU Radio Companion)
> >>> Error: Block key "foo_packet_pad" not found in Platform - grc(GNU Radio Companion)
> >>> Error: Block key "foo_wireshark_connector" not found in Platform - grc(GNU Radio Companion)
> >>> Error: Connection between foo_wireshark_connector_0(0) and blocks_file_sink_0(0) could not be made.
> source block id "foo_wireshark_connector_0" not in block ids
If the some ports are still unconnected after all blocks are found please check the mailing list. This came up several times. You just need to reconnect them in GRC (don't forget to check the hierarchical block too).
>
> Please reply me asap
>
Don't panic :-)
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Nand D flipflop in gnuradio
> Out of curiosity for implementing the digital circuits in gnuradio, I
> tried implementing nand D flipflop in gnuradio but stuck with it because
> gnuradio can't support loops.
>
> I'm attaching grc file of what I tried. Can someone tell me how to make it
> work.
It can't. It's not a bug, it's a design decision, just no way to
implement loop efficiently in the scheduler
The only way to support loops is inside the block itself (in it's work
function), there you can do anything.
Cheers,
Sylvain
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Fwd: Nand D flipflop in gnuradio
From: Stefano Banti <ik2yxt@gmail.com>
Date: Mon, Dec 30, 2013 at 1:12 PM
Subject: Re: [Discuss-gnuradio] Nand D flipflop in gnuradio
To: Sandhya G <sandhya4343@gmail.com>
Hi, perhaps you can try with virtual sink/source.
Stefano
_______________________________________________sandhyaThanks in advanceI'm attaching grc file of what I tried. Can someone tell me how to make it work.Hi,Out of curiosity for implementing the digital circuits in gnuradio, I tried implementing nand D flipflop in gnuradio but stuck with it because gnuradio can't support loops.
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Sunday, December 29, 2013
[Discuss-gnuradio] Nand D flipflop in gnuradio
Re: [Discuss-gnuradio] IEEE 802.11 a
First of all thanks for your suggestion,Please reply me asap
I am using gnuradio 3.7 & started installation of ieee 802.11 from https://github.com/bastibl/gr-ieee802-11 During installation of log4cpp & IT++ for sudo port install log4cpp I was getting sudo:port:command not found. After successful installation of gr_ieee802.11, when I was running example ofdm_loopback.grc, it is not showing entire blocks & giving error
<<< Welcome to GNU Radio Companion 3.7.1-52 >>>
Loading: "/home/naveen/gr-ieee802-11/examples/ofdm_loopback.grc"
>>> Error: Block key "blocks_ctrlport_monitor_performance" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "ieee802_11_ofdm_parse_mac" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "ofdm_phy_hier" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "ieee802_11_ofdm_mac" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "foo_packet_pad" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "foo_wireshark_connector" not found in Platform - grc(GNU Radio Companion)
>>> Error: Connection between foo_wireshark_connector_0(0) and blocks_file_sink_0(0) could not be made.
source block id "foo_wireshark_connector_0" not in block ids
>>> Error: Connection between foo_packet_pad_0(0) and blocks_multiply_xx_0(0) could not be made.
source block id "foo_packet_pad_0" not in block ids
>>> Error: Connection between ofdm_phy_hier_1(0) and foo_packet_pad_0(0) could not be made.
source block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between blocks_add_xx_0(0) and ofdm_phy_hier_1(0) could not be made.
sink block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between ofdm_phy_hier_1(mac_out) and ieee802_11_ofdm_parse_mac_0(in) could not be made.
source block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between blocks_message_strobe_0(strobe) and ieee802_11_ofdm_mac_0(app in) could not be made.
sink block id "ieee802_11_ofdm_mac_0" not in block ids
>>> Error: Connection between ofdm_phy_hier_1(mac_out) and ieee802_11_ofdm_mac_0(phy in) could not be made.
source block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between ieee802_11_ofdm_mac_0(phy out) and ofdm_phy_hier_1(mac_in) could not be made.
source block id "ieee802_11_ofdm_mac_0" not in block ids
>>> Error: Connection between ieee802_11_ofdm_mac_0(phy out) and foo_wireshark_connector_0(in) could not be made.
source block id "ieee802_11_ofdm_mac_0" not in block ids
>>> Done
Showing: "/home/naveen/gr-ieee802-11/examples/ofdm_loopback.grc"On Mon, Dec 23, 2013 at 2:30 PM, Activecat <activecat@gmail.com> wrote:
You may try your luck here:1. https://www.cgran.org/wiki/BBN80211but it runs on gnuradio version 3.1.12. MAC code by Uwicore lab http://www.uwicore.umh.es/is unfortunately for gnuradio version 3.3runs on gnuradio 3.7Let me know if you find more later.Thanks.On Mon, Dec 23, 2013 at 2:08 PM, Naveen Gupta <naveen.ec26@gmail.com> wrote:
_______________________________________________I need to design IEEE802.11 a model in GNU radio platform. How should I start, I am a beginner of GNU radio. Anyone please tell me?
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] IEEE 802.11 a
I am using gnuradio 3.7 & started installation of ieee 802.11 from https://github.com/bastibl/gr-ieee802-11 During installation of log4cpp & IT++ for sudo port install log4cpp I was getting sudo:port:command not found. After successful installation of gr_ieee802.11, when I was running example ofdm_loopback.grc, it is not showing entire blocks & giving error
<<< Welcome to GNU Radio Companion 3.7.1-52 >>>
Loading: "/home/naveen/gr-ieee802-11/examples/ofdm_loopback.grc"
>>> Error: Block key "blocks_ctrlport_monitor_performance" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "ieee802_11_ofdm_parse_mac" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "ofdm_phy_hier" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "ieee802_11_ofdm_mac" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "foo_packet_pad" not found in Platform - grc(GNU Radio Companion)
>>> Error: Block key "foo_wireshark_connector" not found in Platform - grc(GNU Radio Companion)
>>> Error: Connection between foo_wireshark_connector_0(0) and blocks_file_sink_0(0) could not be made.
source block id "foo_wireshark_connector_0" not in block ids
>>> Error: Connection between foo_packet_pad_0(0) and blocks_multiply_xx_0(0) could not be made.
source block id "foo_packet_pad_0" not in block ids
>>> Error: Connection between ofdm_phy_hier_1(0) and foo_packet_pad_0(0) could not be made.
source block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between blocks_add_xx_0(0) and ofdm_phy_hier_1(0) could not be made.
sink block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between ofdm_phy_hier_1(mac_out) and ieee802_11_ofdm_parse_mac_0(in) could not be made.
source block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between blocks_message_strobe_0(strobe) and ieee802_11_ofdm_mac_0(app in) could not be made.
sink block id "ieee802_11_ofdm_mac_0" not in block ids
>>> Error: Connection between ofdm_phy_hier_1(mac_out) and ieee802_11_ofdm_mac_0(phy in) could not be made.
source block id "ofdm_phy_hier_1" not in block ids
>>> Error: Connection between ieee802_11_ofdm_mac_0(phy out) and ofdm_phy_hier_1(mac_in) could not be made.
source block id "ieee802_11_ofdm_mac_0" not in block ids
>>> Error: Connection between ieee802_11_ofdm_mac_0(phy out) and foo_wireshark_connector_0(in) could not be made.
source block id "ieee802_11_ofdm_mac_0" not in block ids
>>> Done
Showing: "/home/naveen/gr-ieee802-11/examples/ofdm_loopback.grc"
You may try your luck here:1. https://www.cgran.org/wiki/BBN80211but it runs on gnuradio version 3.1.12. MAC code by Uwicore lab http://www.uwicore.umh.es/is unfortunately for gnuradio version 3.3runs on gnuradio 3.7Let me know if you find more later.Thanks.On Mon, Dec 23, 2013 at 2:08 PM, Naveen Gupta <naveen.ec26@gmail.com> wrote:
_______________________________________________I need to design IEEE802.11 a model in GNU radio platform. How should I start, I am a beginner of GNU radio. Anyone please tell me?
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Friday, December 27, 2013
Re: [Discuss-gnuradio] GNURadio on Zync: thanks for the excellent tutorial
> Is there any difference in using this stack compared to say, the
> Ubuntu distribution available on www.armhf.com, and compiling gnuradio
> from source?
Compiling GNU Radio from source on an embedded board takes much longer
than using a cross compiler. Also, during the compile on a low memory
embedded board, parts of the com[ile takes lots of memory and you may
need to nurse the build during this part of the build.
My i7 builds gnuradio loads faster than even a quad A15.
Both approaches work, I just do not like to wait :)
Philip
>
> Vanush
>
> On Fri, Dec 27, 2013 at 2:31 AM, Philip Balister <philip@balister.org> wrote:
>> On 12/26/2013 02:28 AM, Jean-Michel FRIEDT wrote:
>>> I have used the opportunity of the more relaxed days of this Christmas
>>> period to try and run the tutorial at
>>> http://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq
>>
>> We need to update the OE section of this page to use:
>>
>> https://github.com/balister/oe-gnuradio-manifest
>>
>> for managing the OE layers. I'd suggest not starting a new checkout if
>> you have something working until after I update UHD to 3.6.2 though :)
>>
>> Also, https://github.com/balister/meta-sdr/wiki/CrossCompile has
>> instructions for cross compiling GNU Radio and testing the result. We
>> need to verify this approach works for OOT module development also.
>>
>> Merry Christmas,
>>
>> Philip
>>
>>>
>>> Wonderful page, works nearly perfectly, thanks a lot.
>>>
>>> A few minor comments to the author or useful to other readers of the
>>> mailing
>>> list:
>>> 1/ using a brand new Debian/testing installation, it seems that the latest
>>> version of tar will not accept both -c and -s options in its command line.
>>> I hence edited all entries of openembedded-core/meta/lib/oe/ and replaced
>>> the -ps option of tar with -p. Same for the meta/classes entries.
>>> Apparently
>>> this has been patched in the latest release of openembedded, but indeed the
>>> zync script will not run out of the box on the latest openembedded release
>>> and, as advised on the web page, I git commited against a given older
>>> release,
>>> 2/ the note about Xilinx tools to Ubuntu users concerning gmake should
>>> be in
>>> bold, huge size, blinking fonts ;) I spent a while being concerned about
>>> licensing issues when the FPGA synthesis tool would not run. No
>>> seriously, just
>>> learning to read did the trick. As a side note, it all ran smoothly with
>>> the
>>> 14.7 release of ISE on a 32-bit x86 architecture. I believe there is a
>>> minor
>>> trivial error in the PATH to ISE in which xtclsh should not be included in
>>> the PATH definition.
>>>
>>> Anyway, thanks for the tutorial, just need to now understand what I did,
>>> but
>>> at least the whole thing is running smoothly.
>>>
>>> Best wishes for the new year, JM
>>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNURadio on Zync: thanks for the excellent tutorial
Hash: SHA1
Yes, armhf is a prepackaged distribution for specific boards (which I
don't think will fit the Zynq board), bringing desktop linux distros
to embedded devices (which is, in my eyes, a little dubiously
usefull), while OpenEmbedded is a method to roll your own embedded
linux for your special-purpose hardware.
Greetings,
Marcus
On 27.12.2013 09:38, Vanush Vaswani wrote:
> Is there any difference in using this stack compared to say, the
> Ubuntu distribution available on www.armhf.com, and compiling
> gnuradio from source?
>
> Vanush
>
> On Fri, Dec 27, 2013 at 2:31 AM, Philip Balister
> <philip@balister.org> wrote:
>> On 12/26/2013 02:28 AM, Jean-Michel FRIEDT wrote:
>>> I have used the opportunity of the more relaxed days of this
>>> Christmas period to try and run the tutorial at
>>> http://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq
>>
>> We need to update the OE section of this page to use:
>>
>> https://github.com/balister/oe-gnuradio-manifest
>>
>> for managing the OE layers. I'd suggest not starting a new
>> checkout if you have something working until after I update UHD
>> to 3.6.2 though :)
>>
>> Also, https://github.com/balister/meta-sdr/wiki/CrossCompile has
>> instructions for cross compiling GNU Radio and testing the
>> result. We need to verify this approach works for OOT module
>> development also.
>>
>> Merry Christmas,
>>
>> Philip
>>
>>>
>>> Wonderful page, works nearly perfectly, thanks a lot.
>>>
>>> A few minor comments to the author or useful to other readers
>>> of the mailing list: 1/ using a brand new Debian/testing
>>> installation, it seems that the latest version of tar will not
>>> accept both -c and -s options in its command line. I hence
>>> edited all entries of openembedded-core/meta/lib/oe/ and
>>> replaced the -ps option of tar with -p. Same for the
>>> meta/classes entries. Apparently this has been patched in the
>>> latest release of openembedded, but indeed the zync script will
>>> not run out of the box on the latest openembedded release and,
>>> as advised on the web page, I git commited against a given
>>> older release, 2/ the note about Xilinx tools to Ubuntu users
>>> concerning gmake should be in bold, huge size, blinking fonts
>>> ;) I spent a while being concerned about licensing issues when
>>> the FPGA synthesis tool would not run. No seriously, just
>>> learning to read did the trick. As a side note, it all ran
>>> smoothly with the 14.7 release of ISE on a 32-bit x86
>>> architecture. I believe there is a minor trivial error in the
>>> PATH to ISE in which xtclsh should not be included in the PATH
>>> definition.
>>>
>>> Anyway, thanks for the tutorial, just need to now understand
>>> what I did, but at least the whole thing is running smoothly.
>>>
>>> Best wishes for the new year, JM
>>>
>>
>> _______________________________________________ Discuss-gnuradio
>> mailing list Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
> _______________________________________________ Discuss-gnuradio
> mailing list Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSvWWSAAoJEAFxB7BbsDrLA68IAKoNr1jwvMmITkFmh27BGuAW
kMdyihFDTWUSMpTc2UeY2cZEe++oL3bIxONbcUty5cOY5BTul70z2Zx6nDtTMVnK
IrXBqpUawCOa9AhHYRuHkU8R+OU5A5rtD46OKvWFo31bB+ylaVkLDIVZcBpmT5CM
4XzpuGhAKctBrpRhfB12Vevj1SGv3ZAMGL8t0Oy6S7q0N6WkP1t/SGyaZlQadW2b
Rmy3QWgv2jMxjjCyMnOgpMI62I1qrqzVJjq77a7nZrp95zZXubRlT++UvnwU3zo2
TQ7HRsyrAVF74SzMoTcfFLa9LSc4zDUXey6Q6kNjFic9bZMKnmPV4AQ0fIIUibY=
=dzD+
-----END PGP SIGNATURE-----
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] how arrays work
interp_ff_impl::work(int noutput_items,
gr_vector_const_void_star &input_items,
gr_vector_void_star &output_items)
int f[m];
I could not initialise by
int f[m]={0};
block is also not work can we write array like the above in gnuradio c++ code
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GNURadio on Zync: thanks for the excellent tutorial
Ubuntu distribution available on www.armhf.com, and compiling gnuradio
from source?
Vanush
On Fri, Dec 27, 2013 at 2:31 AM, Philip Balister <philip@balister.org> wrote:
> On 12/26/2013 02:28 AM, Jean-Michel FRIEDT wrote:
>> I have used the opportunity of the more relaxed days of this Christmas
>> period to try and run the tutorial at
>> http://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq
>
> We need to update the OE section of this page to use:
>
> https://github.com/balister/oe-gnuradio-manifest
>
> for managing the OE layers. I'd suggest not starting a new checkout if
> you have something working until after I update UHD to 3.6.2 though :)
>
> Also, https://github.com/balister/meta-sdr/wiki/CrossCompile has
> instructions for cross compiling GNU Radio and testing the result. We
> need to verify this approach works for OOT module development also.
>
> Merry Christmas,
>
> Philip
>
>>
>> Wonderful page, works nearly perfectly, thanks a lot.
>>
>> A few minor comments to the author or useful to other readers of the
>> mailing
>> list:
>> 1/ using a brand new Debian/testing installation, it seems that the latest
>> version of tar will not accept both -c and -s options in its command line.
>> I hence edited all entries of openembedded-core/meta/lib/oe/ and replaced
>> the -ps option of tar with -p. Same for the meta/classes entries.
>> Apparently
>> this has been patched in the latest release of openembedded, but indeed the
>> zync script will not run out of the box on the latest openembedded release
>> and, as advised on the web page, I git commited against a given older
>> release,
>> 2/ the note about Xilinx tools to Ubuntu users concerning gmake should
>> be in
>> bold, huge size, blinking fonts ;) I spent a while being concerned about
>> licensing issues when the FPGA synthesis tool would not run. No
>> seriously, just
>> learning to read did the trick. As a side note, it all ran smoothly with
>> the
>> 14.7 release of ISE on a 32-bit x86 architecture. I believe there is a
>> minor
>> trivial error in the PATH to ISE in which xtclsh should not be included in
>> the PATH definition.
>>
>> Anyway, thanks for the tutorial, just need to now understand what I did,
>> but
>> at least the whole thing is running smoothly.
>>
>> Best wishes for the new year, JM
>>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Thursday, December 26, 2013
[Discuss-gnuradio] Playback
[Discuss-gnuradio] Successful installation of GNURadio 3.6.4.1 on Window XP and Windows 8
re-installation and searching - why supply it without the DLLs?
Mike
b. Although it is possible to successfully install GNURadio binaries for
versions 3.7.x, none of them include runtime DLLs for WX GUI blocks. Hence
these blocks are not displayed, and so most of the example files available
cannot be used as they need WX GUI blocks. Moreover, some of the QT GUI
blocks do not work in certain versions. Since I do not know how to make
these binaries, I request those who have created these version 3.7.x Windows
binaries to repack them so that we can run the latest versions of GNURadio
in Windows. Until that is done, there is no point trying to install those
versions.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Successful installation of GNURadio 3.6.4.1 on Window XP and Windows 8
Re: [Discuss-gnuradio] GNURadio on Zync: thanks for the excellent tutorial
> I have used the opportunity of the more relaxed days of this Christmas
> period to try and run the tutorial at
> http://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq
We need to update the OE section of this page to use:
https://github.com/balister/oe-gnuradio-manifest
for managing the OE layers. I'd suggest not starting a new checkout if
you have something working until after I update UHD to 3.6.2 though :)
Also, https://github.com/balister/meta-sdr/wiki/CrossCompile has
instructions for cross compiling GNU Radio and testing the result. We
need to verify this approach works for OOT module development also.
Merry Christmas,
Philip
>
> Wonderful page, works nearly perfectly, thanks a lot.
>
> A few minor comments to the author or useful to other readers of the
> mailing
> list:
> 1/ using a brand new Debian/testing installation, it seems that the latest
> version of tar will not accept both -c and -s options in its command line.
> I hence edited all entries of openembedded-core/meta/lib/oe/ and replaced
> the -ps option of tar with -p. Same for the meta/classes entries.
> Apparently
> this has been patched in the latest release of openembedded, but indeed the
> zync script will not run out of the box on the latest openembedded release
> and, as advised on the web page, I git commited against a given older
> release,
> 2/ the note about Xilinx tools to Ubuntu users concerning gmake should
> be in
> bold, huge size, blinking fonts ;) I spent a while being concerned about
> licensing issues when the FPGA synthesis tool would not run. No
> seriously, just
> learning to read did the trick. As a side note, it all ran smoothly with
> the
> 14.7 release of ISE on a 32-bit x86 architecture. I believe there is a
> minor
> trivial error in the PATH to ISE in which xtclsh should not be included in
> the PATH definition.
>
> Anyway, thanks for the tutorial, just need to now understand what I did,
> but
> at least the whole thing is running smoothly.
>
> Best wishes for the new year, JM
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Bug: gr-qtgui: wrong design of variable-type blocks for GRC (category /GUI Widgets/QT)
--
View this message in context: http://gnuradio.4.n7.nabble.com/Bug-gr-qtgui-wrong-design-of-variable-type-blocks-for-GRC-category-GUI-Widgets-QT-tp45538p45543.html
Sent from the GnuRadio mailing list archive at Nabble.com.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Wednesday, December 25, 2013
[Discuss-gnuradio] GNURadio on Zync: thanks for the excellent tutorial
period to try and run the tutorial at
http://gnuradio.org/redmine/projects/gnuradio/wiki/Zynq
Wonderful page, works nearly perfectly, thanks a lot.
A few minor comments to the author or useful to other readers of the mailing
list:
1/ using a brand new Debian/testing installation, it seems that the latest
version of tar will not accept both -c and -s options in its command line.
I hence edited all entries of openembedded-core/meta/lib/oe/ and replaced
the -ps option of tar with -p. Same for the meta/classes entries. Apparently
this has been patched in the latest release of openembedded, but indeed the
zync script will not run out of the box on the latest openembedded release
and, as advised on the web page, I git commited against a given older release,
2/ the note about Xilinx tools to Ubuntu users concerning gmake should be in
bold, huge size, blinking fonts ;) I spent a while being concerned about
licensing issues when the FPGA synthesis tool would not run. No
seriously, just
learning to read did the trick. As a side note, it all ran smoothly with the
14.7 release of ISE on a 32-bit x86 architecture. I believe there is a minor
trivial error in the PATH to ISE in which xtclsh should not be included in
the PATH definition.
Anyway, thanks for the tutorial, just need to now understand what I did, but
at least the whole thing is running smoothly.
Best wishes for the new year, JM
--
JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 32 av. observatoire,
25044 Besancon, France
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to best use new GR features for TDMA systems ?
I think GNU Radio apps should look a bit like this:
At the top (think "MAC") blocks pass data as PDUs. The further down you go
("PHY"), you'll eventually need regular blocks. Here, tagged streams will
do what you want.
I guess gr-easymac was an early demo of this principle, although its
functionality can now be reproduced with pure GNU Radio. At CEL, we've
developed a FHSS network using pure GNU Radio, which works quite well
(someone still needs to release some code, and I hope they're reading this
:). There will be a presentation on this at FOSDEM, btw.
Also, I've been working on a way to do TDMA using the OFDM blocks (on one
of my lower-priority branches, though, so don't get too excited right now).
In principle, the idea is:
* At MAC level, create a package with a tx time stamp as a PDU
* Pass this to the OFDM mod. The time stamp will propagate along with the
length tag, and stay at the front of the streamed packet (this feature was
merged into GNU Radio a while back and is available in the latest release).
* The hardware driver should take the streamed packet and the metadata in
the tags (the tx time, though it could also be the centre frequency for FH)
and tx accordingly.
* At the receive side, all we need to do is remember the rx time of samples
when we do a packet modulation.
There's a couple of things that are hard here: On the TX side, we just hope
that the packet will reach the hardware in time. What if it doesn't? Well,
bad luck.
Bottom line: GNU Radio has only recently become capable of doing these
things. This means we are still in the process of figuring out of how
exactly to write TDMA PHYs with corresponding MACs, which is a feature that
we've always wanted and now seems achievable. I guess the more we try out,
the more we will identify what's missing in order to do this.
MB
Tuesday, December 24, 2013
Re: [Discuss-gnuradio] IEEE 802.11 a
I need to design IEEE802.11 a model in GNU radio platform. How should I start, I am a beginner of GNU radio. Anyone please tell me?
Hi Naveen,
I recommend reading the manual pages for OFDM code, and work from there. Make sure you've fully understood all the examples in gr-digital/examples/ofdm.
MB
[Discuss-gnuradio] How to use FEC block in GRC?
[Discuss-gnuradio] Bug: gr-qtgui: wrong design of variable-type blocks for GRC (category /GUI Widgets/QT)
surprisingly found that GRC generates code making prohibited accesses to qt
gui objects from non-gui thread context. I'm not python guru, but I doubt
that python is smart enough to detect access to qt objects from different
threads and invoke them properly via qt-specific mechanisms. Similar problem
observed when widgets slots (executing in main thread context) call
variable-changer functions which in turn invoking callbacks of blocks*.
I suppose all blocks in /GUI Widgets/QT category aren't thread-safe and
shouldn't be used until this issue has been fixed.
* Block's external interfaces(callbacks) are expected to be guarded
internally, but I still didn't found no block in gr packages, I working
with, which follow this rule. Maybe swig-generated python interface guards
all accesses already? If not, GRC user should be so much careful, that one
have to check generated code. IMHO, it reduces GRC usefullness greatly...
--
View this message in context: http://gnuradio.4.n7.nabble.com/Bug-gr-qtgui-wrong-design-of-variable-type-blocks-for-GRC-category-GUI-Widgets-QT-tp45538.html
Sent from the GnuRadio mailing list archive at Nabble.com.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Monday, December 23, 2013
Re: [Discuss-gnuradio] A Couple Questions
Hello,If the buttons aren't working then the thing is probably locked up, try lowering the fft_rate parameter and see if that fixes things.AndrewOn Mon, Dec 23, 2013 at 3:10 PM, Paul B. Huter <paul.b.huter@gmail.com> wrote:
_______________________________________________I have a data file that was recorded to a RAMDisk and transferred to the hard drive on my Linux machine. When I run it through a throttle, a filter, and into an FFT, the file repeats. When I was running it off the RAMDisk, it only played for the ~15 seconds of the data. I was having the problem with repeating before I rebooted and lost the RAMDisk file (I thought maybe having it stored in RAM, too, was causing a problem). Also, the buttons on the FFT plot don't work (Autoscale, Stop) Can anyone provide any insight into why the file on my hard drive is repeating? "Repeat" is set to "No" on the file source block.Second question - On the FFT (same flow) how can I make it so it STARTS viewing all the data? The FFT shows up going from 0 to 100, and the majority of the data is negative. As mentioned, it only runs for about 15 seconds, and even if the Autoscale button worked, I have such a small window to view everything. It is my understanding that I can't get an Autoscale prior to viewing the plot, but is there a way to scale it with the parameters on the flow block (maybe set it to go from 0 to -100)?Thanks!
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] A Couple Questions
I have a data file that was recorded to a RAMDisk and transferred to the hard drive on my Linux machine. When I run it through a throttle, a filter, and into an FFT, the file repeats. When I was running it off the RAMDisk, it only played for the ~15 seconds of the data. I was having the problem with repeating before I rebooted and lost the RAMDisk file (I thought maybe having it stored in RAM, too, was causing a problem). Also, the buttons on the FFT plot don't work (Autoscale, Stop) Can anyone provide any insight into why the file on my hard drive is repeating? "Repeat" is set to "No" on the file source block.Second question - On the FFT (same flow) how can I make it so it STARTS viewing all the data? The FFT shows up going from 0 to 100, and the majority of the data is negative. As mentioned, it only runs for about 15 seconds, and even if the Autoscale button worked, I have such a small window to view everything. It is my understanding that I can't get an Autoscale prior to viewing the plot, but is there a way to scale it with the parameters on the flow block (maybe set it to go from 0 to -100)?Thanks!
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] A Couple Questions
Re: [Discuss-gnuradio] OOT enums
Hi,
For what it's worth, I have enums in fosphor and the way I had to
access them is :
from gnuradio.fosphor.fosphor_swig import base_sink_c
base_sink_c.REF_DOWN
Because the base_sink_c from gnuradio.fosphor directly isn't really
the SWIG object ... it's just the wrapper for the make() function that
creates the sptr and you can't access any of the members.
Cheers,
Sylvain
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Gnuradio 3.7.2 Windows?
Thanks Andrew – I had goggled it and not found anything helpful. I am not sure an earlier version of pyopengl would work but I suppose it is worth a try.
I don’t want an SDR like HDSDR, I want to use Gnuradio to do things most SDRs can not do – 3.6.5 worked but everyone has now moved on to 3.7 and I was hoping, perhaps naively, that it would be sensible to try to install it under windows.
Mike
<rant>
The problem with Gnuradio isn’t so much understanding the DSP side – it’s installing and getting the system to work and keeping it working. The main problem I find is the continuous changing of the basic framework often breaks many things in the process in a way that only an experienced python programmer can fathom how to fix. Even the supplied examples don’t work because the modules have been shuffled around, renamed etc. Instructions rapidly become outdated and the new user then has no clue why the advice they find on the Gnuradio site doesn’t work. Backwards compatibility isn’t a priority when developing a new framework, but Gnuradio in its present form has been around for 10 years so it should really have settled down and there shouldn’t be these big break everything changes with each new minor release. If it were truly stable I think it would be much more successful by now.
</rant>
From: Andrew Davis [mailto:glneolistmail@gmail.com]
Sent: 23 December 2013 16:11
To: Mike Willis
Cc: GNURadio Discussion List
Subject: Re: [Discuss-gnuradio] Gnuradio 3.7.2 Windows?
Hello,
>Has anyone actually managed to successfully install and run the latest gnuradio in Windows 7
Yes, but not using those instruction, building from source is much more fun :), but they look like they worked for you outside of that error.
Also If you Google your error other people are having that problem as well, so it's not Gnuradio related but something with pyopengl on certain windows systems. I'd say try installing an older version of pyopengl.
> I must admit to getting extremely frustrated with Gnuradio and its lack or usability for those of us who are not professional programmers.
While I agree it's not quite user friendly it is a software defined radio API and development system, so it's not gonna be like going to be like installing a program and listening to the radio, you will need some software savvyness to build a SDR. If you just want to use a SDR there are many already made programs for individual tasks.
Andrew
On Mon, Dec 23, 2013 at 4:47 AM, Mike Willis <willis.mj@gmail.com> wrote:
Has anyone actually managed to successfully install and run the latest gnuradio in Windows 7 based on these http://code.ettus.com/redmine/ettus/projects/uhd/wiki/GNURadio_Windows instructions?
I don’t believe this page is up to date as I just cannot get it to work. It was OK if something of a struggle with 3.6.
Although it nearly works, the gui modules do not work at all but produce a rather unhelpful error message. E.g. this is with a wxgui fft sink added to the dialtone example. The tone works fine but not with any gui.
“TypeError: ("No array-type handler for type <class 'ctypes.c_ulong'> (value: c_ulong(0L)) registered", <OpenGL.converters.CallFuncPyConverter object at 0x0482A3D0>)
”
How am I supposed to understand this? It looks to me like a problem with pyopengl but that has been installed as indicated in the instructions. Are the instructions wrong? Is this the wrong version? Does it just not work anyway?
I must admit to getting extremely frustrated with gnuradio and its lack or usability for those of us who are not professional programmers.
Mike
Here is the debug code.
self._initText()
File "C:\Program Files\gnuradio\lib\site-packages\gnuradio\wxgui\plotter\gltext.py", line 376, in _initText
self._centered)
File "C:\Program Files\gnuradio\lib\site-packages\gnuradio\wxgui\plotter\gltext.py", line 73, in __init__
self.createTexture()
File "C:\Program Files\gnuradio\lib\site-packages\gnuradio\wxgui\plotter\gltext.py", line 229, in createTexture
self._texture = glGenTextures(1)
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\latebind.py", line 61, in __call__
return self.wrapperFunction( self.baseFunction, *args, **named )
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\GL\exceptional.py", line 189, in glGenTextures
baseFunction( count, textures)
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\latebind.py", line 45, in __call__
return self._finalCall( *args, **named )
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\wrapper.py", line 571, in wrapperCall
pyArgs = tuple( calculate_pyArgs( args ))
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\wrapper.py", line 356, in calculate_pyArgs
yield converter(args[index], self, args)
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\converters.py", line 134, in __call__
return self.function( incoming )
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\arrays\arraydatatype.py", line 141, in asArray
return cls.getHandler(value).asArray( value, typeCode or cls.typeConstant )
File "C:\Python27\lib\site-packages\pyopengl-3.1.0a3-py2.7.egg\OpenGL\arrays\arraydatatype.py", line 52, in __call__
typ, repr(value)[:50]
TypeError: ("No array-type handler for type <class 'ctypes.c_ulong'> (value: c_ulong(0L)) registered", <OpenGL.converters.CallFuncPyConverter object at 0x0482A3D0>)
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


