[Discuss-gnuradio] Timing Analysis of Blocks
Hi, I was wondering if it is possible to do timing analysis for GNU Radio blocks? If so, what is the mechanism for finding time usage by an individual block in a flowgraph? Thanks in advance. Yours thankfully, Shashank Sinha ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] ColtrolPort IC Timeout
On Fri, May 23, 2014 at 1:06 PM, Dan CaJacob wrote:
> Hey Tom,
>
> Yes, it was definitely pulling the correct endpoint. Even though it is
> backgrounded, I have a log for everything that ran.
>
> Very Respectfully,
>
> Dan CaJacob
>
Hey Dan,
Bit of a holiday this weekend, mostly away from my computers. I'd like to
try to solve this problem with you, but I'm not sure where to begin. I'm
wondering if it's related to the intermittent/infrequent QA failures I've
seen when ControlPort is turned on. Is there any chance you can provide a
simple program that we can use to exercise the problem for me to help debug?
Tom
> On Fri, May 23, 2014 at 11:26 AM, Tom Rondeau wrote:
>
>> On Thu, May 22, 2014 at 11:09 AM, Dan CaJacob wrote:
>>
>>> I have a gui-less flowgraph that runs in the background with sudo
>>> privileges. While I can run ControlPort normally from GRC, it doesn't seem
>>> to work properly with my backgrounded FG - I get timeout errors. My config
>>> files are setup so that both FGs do actually call ControlPort and Perf Mon
>>> (verified in log files). The FG and the monitoring apps are all running on
>>> the same PC.
>>>
>>> Setup is Ubuntu 12.04 x64 with GR 3.7.4, built on the weekend.
>>>
>>> Attempting to run Perf Mon, I get:
>>>
>>> $ gr-perf-monitorx 127.0.0.1 23456
>>>
>>
>>
>> Hey Dan,
>>
>> When you're running the flowgraph that you're trying to connect to over
>> ControlPort, can you verify that they are setting up the correct endpoint?
>> If you run it yourself, not as a background task, it should print out
>> information about the endpoints. That will tell you the port number. Just
>> want to check to make sure your config file is getting read correctly and
>> setting it up on port 23456 like you specified.
>>
>> We really should move the endpoint information to be sent out by the
>> gr-log system so you can redirect the info to a file and see the info
>> without requiring you to have access to stdout.
>>
>> Tom
>>
>>
>>
>>
>>> 2014-05-22 11:01:54.450720 /usr/bin/gr-perf-monitorx: error: Traceback
>>> (most recent call last):
>>> File "/usr/lib/pymodules/python2.7/Ice.py", line 984, in main
>>> status = self.doMain(args, initData)
>>> File "/usr/lib/pymodules/python2.7/Ice.py", line 1031, in doMain
>>> return self.run(args)
>>> File
>>> "/usr/lib/python2.7/dist-packages/gnuradio/ctrlport/IceRadioClient.py",
>>> line 102, in run
>>> ex = self.parentClass(radio, port, self)
>>> File "/usr/bin/gr-perf-monitorx", line 74, in __init__
>>> self.newCon(radio, port)
>>> File "/usr/bin/gr-perf-monitorx", line 88, in newCon
>>> child = MForm(radio, port, len(self.conns), self)
>>> File "/usr/bin/gr-perf-monitorx", line 696, in __init__
>>> knobs = self.radio.get([])
>>> File "/usr/lib/python2.7/dist-packages/gnuradio_ice.py", line 1221, in
>>> get
>>> return
>>> _M_gnuradio.ctrlport.GNURadio.ControlPort._op_get.invoke(self, ((knobs, ),
>>> _ctx))
>>> ConnectTimeoutException: exception ::Ice::ConnectTimeoutException
>>> {
>>> }
>>>
>>> Attempting to run Ctrl Port Mon, I get:
>>>
>>> A blank canvas screen like this: http://i.imgur.com/8N88fcU.png
>>>
>>> and console output like:
>>>
>>> $ gr-ctrlport-monitor 127.0.0.1 23456
>>> X Error: BadAccess (attempt to access private resource denied) 10
>>> Extension:129 (MIT-SHM)
>>> Minor opcode: 1 (X_ShmAttach)
>>> Resource id: 0x421
>>> X Error: BadShmSeg (invalid shared segment parameter) 128
>>> Extension:129 (MIT-SHM)
>>> Minor opcode: 5 (X_ShmCreatePixmap)
>>> Resource id: 0x4200012
>>> X Error: BadDrawable (invalid Pixmap or Window parameter) 9
>>> Major opcode: 62 (X_CopyArea)
>>> Resource id: 0x4200013
>>> X Error: BadDrawable (invalid Pixmap or Window parameter) 9
>>> Major opcode: 62 (X_CopyArea)
>>> Resource id: 0x4200013
>>> ctrlport-monitor: radio.get threw exception (exception
>>> ::Ice::ConnectTimeoutException
>>> {
>>> }).
>>> ...
>>>
>>> My ctrlport.conf file has just one uncommented line:
>>>
>>> ControlPort.Endpoints = tcp -t 5000 -h 127.0.0.1 -p 23456
>>>
>>> I had extended the timeout, attempting to resolve the problem, but had
>>> no luck.
>>>
>>> Very Respectfully,
>>>
>>> Dan CaJacob
>>>
>>> ___
>>> 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] Git cloned, errors in Portaudio during cmake
On 05/26/2014 10:24 PM, Sid Boyce wrote: On 27/05/14 02:01, Marcus D. Leech wrote: On 05/26/2014 08:40 PM, Sid Boyce wrote: Check if portaudio19-dev installed. root@sdrbox:~# dpkg -l|grep portaudio ii libportaudio2:amd64 19+svn20140130-1 amd64Portable audio I/O - shared library ii libportaudiocpp0:amd64 19+svn20140130-1 amd64Portable audio I/O C++ bindings - shared library ii portaudio19-dev 19+svn20140130-1 amd64Portable audio I/O - development files 73 ... Sid. [mleech@marcus2 ~]$ rpm -qa |grep portaudio portaudio-19-11.fc14.x86_64 portaudio-devel-19-11.fc14.x86_64 H... a very old version of Fedora. When a new version comes out I upgrade to the latest using yum - likewise with openSUSE, Ubuntu and Ubuntu ARM. I crawl from one version to the next and only do a fresh install if I upgrade HD's. Problem comes when new code requires something that is a level or several higher than you have installed - upgrade beyond one or 2 versions probably doesn't work and you are forced to do a fresh install then all the other packages required after that, plus fresh setups. You get changes like systemd replacing sysvinit which is seamless if you are one or 2 levels back. With a fresh install there are many new things you are presented with suddenly, more to deal with when you are trying to get up and working. 73 ... Sid. I removed portaudio from the system, which cured this particular problem, since i only had 1 package that depended on it, and I'm not using it. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Git cloned, errors in Portaudio during cmake
On 27/05/14 02:01, Marcus D. Leech wrote: On 05/26/2014 08:40 PM, Sid Boyce wrote: Check if portaudio19-dev installed. root@sdrbox:~# dpkg -l|grep portaudio ii libportaudio2:amd64 19+svn20140130-1 amd64Portable audio I/O - shared library ii libportaudiocpp0:amd64 19+svn20140130-1 amd64Portable audio I/O C++ bindings - shared library ii portaudio19-dev 19+svn20140130-1 amd64Portable audio I/O - development files 73 ... Sid. [mleech@marcus2 ~]$ rpm -qa |grep portaudio portaudio-19-11.fc14.x86_64 portaudio-devel-19-11.fc14.x86_64 H... a very old version of Fedora. When a new version comes out I upgrade to the latest using yum - likewise with openSUSE, Ubuntu and Ubuntu ARM. I crawl from one version to the next and only do a fresh install if I upgrade HD's. Problem comes when new code requires something that is a level or several higher than you have installed - upgrade beyond one or 2 versions probably doesn't work and you are forced to do a fresh install then all the other packages required after that, plus fresh setups. You get changes like systemd replacing sysvinit which is seamless if you are one or 2 levels back. With a fresh install there are many new things you are presented with suddenly, more to deal with when you are trying to get up and working. 73 ... Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Git cloned, errors in Portaudio during cmake
On 05/26/2014 09:56 PM, Sid Boyce wrote: On 27/05/14 02:01, Marcus D. Leech wrote: On 05/26/2014 08:40 PM, Sid Boyce wrote: Check if portaudio19-dev installed. root@sdrbox:~# dpkg -l|grep portaudio ii libportaudio2:amd64 19+svn20140130-1 amd64Portable audio I/O - shared library ii libportaudiocpp0:amd64 19+svn20140130-1 amd64Portable audio I/O C++ bindings - shared library ii portaudio19-dev 19+svn20140130-1 amd64Portable audio I/O - development files 73 ... Sid. [mleech@marcus2 ~]$ rpm -qa |grep portaudio portaudio-19-11.fc14.x86_64 portaudio-devel-19-11.fc14.x86_64 OK, it's Fedora. slipstream:/usr/src/gnuradio # ls -l cmake/Modules/FindPortaudio.cmake -rw-r--r-- 1 lancelot users 786 May 3 2012 cmake/Modules/FindPortaudio.cmake In the gnuradio/build directory run "ccmake .." "t" to toggle advanced mode. Scroll down to the lines PORTAUDIO_INCLUDE_DIRS PORTAUDIO_LIBRARIES Hit Enter and type /usr/include (Enter) Scroll down to the PORTAUDIO_LIBRARIES line and hit Enter Type where libportaudio.so lives, e.g /usr/lib64/libportaudio.so and hit Enter. Type "c" to configure. Then "g" to generate. Then "cmake .." 73 ... Sid. That yields the same results. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Git cloned, errors in Portaudio during cmake
On 27/05/14 02:01, Marcus D. Leech wrote: On 05/26/2014 08:40 PM, Sid Boyce wrote: Check if portaudio19-dev installed. root@sdrbox:~# dpkg -l|grep portaudio ii libportaudio2:amd64 19+svn20140130-1 amd64Portable audio I/O - shared library ii libportaudiocpp0:amd64 19+svn20140130-1 amd64Portable audio I/O C++ bindings - shared library ii portaudio19-dev 19+svn20140130-1 amd64Portable audio I/O - development files 73 ... Sid. [mleech@marcus2 ~]$ rpm -qa |grep portaudio portaudio-19-11.fc14.x86_64 portaudio-devel-19-11.fc14.x86_64 OK, it's Fedora. slipstream:/usr/src/gnuradio # ls -l cmake/Modules/FindPortaudio.cmake -rw-r--r-- 1 lancelot users 786 May 3 2012 cmake/Modules/FindPortaudio.cmake In the gnuradio/build directory run "ccmake .." "t" to toggle advanced mode. Scroll down to the lines PORTAUDIO_INCLUDE_DIRS PORTAUDIO_LIBRARIES Hit Enter and type /usr/include (Enter) Scroll down to the PORTAUDIO_LIBRARIES line and hit Enter Type where libportaudio.so lives, e.g /usr/lib64/libportaudio.so and hit Enter. Type "c" to configure. Then "g" to generate. Then "cmake .." 73 ... Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Git cloned, errors in Portaudio during cmake
On 05/26/2014 08:40 PM, Sid Boyce wrote: Check if portaudio19-dev installed. root@sdrbox:~# dpkg -l|grep portaudio ii libportaudio2:amd64 19+svn20140130-1 amd64Portable audio I/O - shared library ii libportaudiocpp0:amd64 19+svn20140130-1 amd64Portable audio I/O C++ bindings - shared library ii portaudio19-dev 19+svn20140130-1 amd64Portable audio I/O - development files 73 ... Sid. [mleech@marcus2 ~]$ rpm -qa |grep portaudio portaudio-19-11.fc14.x86_64 portaudio-devel-19-11.fc14.x86_64 -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Git cloned, errors in Portaudio during cmake
On 27/05/14 00:21, Marcus D. Leech wrote: On 05/26/2014 07:07 PM, Johnathan Corgan wrote: On 05/26/2014 03:57 PM, Marcus D. Leech wrote: transfer closed with 88647 bytes remaining to read error: Unable to find 404ce04347b132e963564099f18345c19e2685c6 under http://gnuradio.org/git/gnuradio.git Cannot obtain needed blob 404ce04347b132e963564099f18345c19e2685c6 while processing commit 69dcaa75b629af4ebc465a073f54af84b7c75a11. error: Fetch failed. I just tried this, it worked. It could be an intermittent CloudFlare problem, as that "transfer closed" would have been when your system was connected to them, not gnuradio.org. Yup, came back up. But then, cmake fails tonight on my system, in an area it has never failed before: -- checking for module 'portaudio-2.0' -- found portaudio-2.0, version 19 CMake Error at cmake/Modules/FindPortaudio.cmake:37 (include): include could not find load file: CMakePushCheckState Call Stack (most recent call first): gr-audio/lib/CMakeLists.txt:135 (find_package) CMake Error at cmake/Modules/FindPortaudio.cmake:38 (cmake_push_check_state): Unknown CMake command "cmake_push_check_state". Call Stack (most recent call first): gr-audio/lib/CMakeLists.txt:135 (find_package) -- Configuring incomplete, errors occurred! Check if portaudio19-dev installed. root@sdrbox:~# dpkg -l|grep portaudio ii libportaudio2:amd64 19+svn20140130-1 amd64Portable audio I/O - shared library ii libportaudiocpp0:amd64 19+svn20140130-1 amd64Portable audio I/O C++ bindings - shared library ii portaudio19-dev 19+svn20140130-1 amd64Portable audio I/O - development files 73 ... Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Git cloned, errors in Portaudio during cmake
On 05/26/2014 07:07 PM, Johnathan Corgan wrote: On 05/26/2014 03:57 PM, Marcus D. Leech wrote: transfer closed with 88647 bytes remaining to read error: Unable to find 404ce04347b132e963564099f18345c19e2685c6 under http://gnuradio.org/git/gnuradio.git Cannot obtain needed blob 404ce04347b132e963564099f18345c19e2685c6 while processing commit 69dcaa75b629af4ebc465a073f54af84b7c75a11. error: Fetch failed. I just tried this, it worked. It could be an intermittent CloudFlare problem, as that "transfer closed" would have been when your system was connected to them, not gnuradio.org. Yup, came back up. But then, cmake fails tonight on my system, in an area it has never failed before: -- checking for module 'portaudio-2.0' -- found portaudio-2.0, version 19 CMake Error at cmake/Modules/FindPortaudio.cmake:37 (include): include could not find load file: CMakePushCheckState Call Stack (most recent call first): gr-audio/lib/CMakeLists.txt:135 (find_package) CMake Error at cmake/Modules/FindPortaudio.cmake:38 (cmake_push_check_state): Unknown CMake command "cmake_push_check_state". Call Stack (most recent call first): gr-audio/lib/CMakeLists.txt:135 (find_package) -- Configuring incomplete, errors occurred! -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Muthaspewka!
On 05/26/2014 03:57 PM, Marcus D. Leech wrote: > transfer closed with 88647 bytes remaining to read > error: Unable to find 404ce04347b132e963564099f18345c19e2685c6 under > http://gnuradio.org/git/gnuradio.git > Cannot obtain needed blob 404ce04347b132e963564099f18345c19e2685c6 > while processing commit 69dcaa75b629af4ebc465a073f54af84b7c75a11. > error: Fetch failed. I just tried this, it worked. It could be an intermittent CloudFlare problem, as that "transfer closed" would have been when your system was connected to them, not gnuradio.org. -- Johnathan Corgan, Corgan Labs SDR Training and Development Services http://corganlabs.com <> signature.asc Description: OpenPGP digital signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Muthaspewka!
git clone --progress http://gnuradio.org/git/gnuradio.git Cloning into gnuradio... error: Unable to get pack file http://gnuradio.org/git/gnuradio.git/objects/pack/pack-f226f3ea8e0b1778c849c7ac2c27532d22f0fefd.pack transfer closed with 88647 bytes remaining to read error: Unable to find 404ce04347b132e963564099f18345c19e2685c6 under http://gnuradio.org/git/gnuradio.git Cannot obtain needed blob 404ce04347b132e963564099f18345c19e2685c6 while processing commit 69dcaa75b629af4ebc465a073f54af84b7c75a11. error: Fetch failed. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Build on ubuntu 14.04
Or if building on low memory systems like ARM, specify 4GB of swap. 73 ... Sid. On 26/05/14 22:30, Michael Hartje wrote: Thank You all for the hints. Thanks to Marcus, Sid, Bob! Yes, it works now! I think, the observation from Sid was the way of success. So the reason was: too low (1GB!) RAM for the VM! After increase up to e.g. 3,5 GB RAM for the VM the buildscript.sh gave no errors anymore. Thanks in advance May be it is already done, but If not, I recommend a recommendation in the wiki "Build from source": Use a lot of RAM and / or swap best to avoid a quiet termination of compiling gnuradio. Michael Hartje -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Build on ubuntu 14.04
Thank You all for the hints. Thanks to Marcus, Sid, Bob! Yes, it works now! I think, the observation from Sid was the way of success. So the reason was: too low (1GB!) RAM for the VM! After increase up to e.g. 3,5 GB RAM for the VM the buildscript.sh gave no errors anymore. Thanks in advance May be it is already done, but If not, I recommend a recommendation in the wiki "Build from source": Use a lot of RAM and / or swap best to avoid a quiet termination of compiling gnuradio. Michael Hartje -- Prof. Dr.-Ing. Michael Hartje Labor Hochspannungstechnik / Labor elektrische Messtechnik Neustadtswall 30; D-28199 Bremen Tel +49 421 5905-3444 FAX +49 421 5905-3476 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] tx_ofdm and rx_ofdm
Hi Martin: Thank you so much for your help.It can run.Thanks. Best regards xianda At 2014-05-26 20:40:08,"Martin Braun" wrote: >On 26.05.2014 13:03, xianda wrote: >> Hi: >> Now I run the example(tx_ofdm and rx_ofdm) through two usrps.(The >> version of my gnuradio is 3.7.4). >> 1.But in the receive part I receive two many things like this: >> INFO: Detected an invalid packet at item 139632 >> INFO: Parser returned #f > >Xianda, > >this questions pops up a lot on this list, and 99% of the time it means >your RF settings are distorting your signal. Try reducing gain and >multiplier, and make sure you get a nice spectrum before you try and >receive (i.e. check it with uhd_fft and make sure it's rectangular). > >> UHD Warning: >> The hardware does not support the requested TX sample rate: >> Target sample rate: 0.10 MSps >> Actual sample rate: 0.195312 MSps >> And the device I use is USRP N210.And I set the sample rate is 100k. >> Some days ago,someone tell me set the sample rate 100M/even number.And >> the 100k seems right,why this UHD warning?Can someone tell me what is >> the appropriate sample rate for USRP N210?Thank you very much. > >If you want 100K, you need to resample on the host. A stock N210 can go >down to 100e6/512 (i.e. what you're seeing). But that's OK, resampling >from 200k to 100k is not too CPU-intensive if you have a decent hardware. > >M > > >___ >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] tx_ofdm and rx_ofdm
Hi Jawad: Thank you so much for your help.Now it can run.Thanks. Best regards At 2014-05-26 20:44:13,"Jawad Seddar" wrote: First of all, I removed the OFDM receiver part from tx_ofdm and replaced it by a USRP sink and added a tag debugger to know when the data was generated from the transmitter. I also removed the OFDM transmitter part from rx_ofdm and replaced it by a USRP source. You can see all of this in the files attached. Change the frequencies and sample rates according to your needs. As long as there is data being sent and received, you shouldn't see any of the warning messages from the receiver. Regarding the sampling rate problem, I believe there is a minimal sample rate and you can't go below it. Regards, Jawad 2014-05-26 14:22 GMT+02:00 xianda : Hi Jawad: Thank you so much for your kindly reply. But the first problem still exist.Can you send me your test document and I test.Thank you. And the second problem is solved.Can you tell me why 200k is ok while 100k failed?(they are all 10M/(even number)).Thank you. Best regards, xianda At 2014-05-26 19:42:28,"Jawad Seddar" wrote: Hi xianda, I found out that using a factor of 0.05 in the multiply const works best for me, with USRPs about 50 - 100 cm appart and rx and tx gains set to 0. Try using a sample rate of 200k and you shouldn't get that sample rate error again. Regards, Jawad ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Error: /media/Softwares & Data/UBUNTU DOWNLOADS/top_block.py:1:1:FATAL:PARSER:ERR_DOCUMENT_EMPTY: Start tag expected, '<' not found
Yes, it is the *generated python* not the *GRC file* itself. You can't open the python code with GRC. You should open the GRC file. On Mon, May 26, 2014 at 9:41 AM, jason sam wrote: > Hi Marcus, > This python code is generated from GRC. > > > On Mon, May 26, 2014 at 11:52 AM, Marcus Müller > wrote: > >> Hi Ali, >> >> we're always thankful for feedback; the information you supply is a >> little sparse. >> Usually, I'd ask you to refer to >> http://gnuradio.org/redmine/projects/gnuradio/wiki/ReportingErrors , but >> in this case, things are easy enough to guess just from your wording: >> >> > When i execute a GRC file >> >> GRC files are just saved representations of your flow graph (in XML). You >> can't execute them. >> What you do is let the companion generate a python file out of them and >> execute that. >> You tried to load such a python file like it was a GRC file; this can't >> work. >> >> Greetings, >> Marcus >> >> >> On 26.05.2014 08:42, jason sam wrote: >> >> The code is as attached. >> >> >> On Mon, May 26, 2014 at 9:42 AM, jason sam >> wrote: >> >> >> When i execute a GRC file i get the following error.Any info about that? >> Regards, >> Ali >> >> >> >> >> ___ >> Discuss-gnuradio mailing >> listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> >> >> >> ___ >> 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] tx_ofdm and rx_ofdm
On 26.05.2014 13:03, xianda wrote: Hi: Now I run the example(tx_ofdm and rx_ofdm) through two usrps.(The version of my gnuradio is 3.7.4). 1.But in the receive part I receive two many things like this: INFO: Detected an invalid packet at item 139632 INFO: Parser returned #f Xianda, this questions pops up a lot on this list, and 99% of the time it means your RF settings are distorting your signal. Try reducing gain and multiplier, and make sure you get a nice spectrum before you try and receive (i.e. check it with uhd_fft and make sure it's rectangular). UHD Warning: The hardware does not support the requested TX sample rate: Target sample rate: 0.10 MSps Actual sample rate: 0.195312 MSps And the device I use is USRP N210.And I set the sample rate is 100k. Some days ago,someone tell me set the sample rate 100M/even number.And the 100k seems right,why this UHD warning?Can someone tell me what is the appropriate sample rate for USRP N210?Thank you very much. If you want 100K, you need to resample on the host. A stock N210 can go down to 100e6/512 (i.e. what you're seeing). But that's OK, resampling from 200k to 100k is not too CPU-intensive if you have a decent hardware. M ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Mouse and keyboard don't work on usrp e110 ?
Hi, I connected the usrp e110 to usb hub(with usb host) which is connected to a keyboard, a mouse and a pen drive( for swap memory). When I try to login the mouse pointer doesn't work. I'm sure that the mouse works well. Is there any driver to install on usrp e 110 to make the mouse(the keyboard) works in order to get access to gnuradio on usrp e110 ? Best regards, Wafa HAJ HMIDA ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] tx_ofdm and rx_ofdm
Hi Jawad: Thank you so much for your kindly reply. But the first problem still exist.Can you send me your test document and I test.Thank you. And the second problem is solved.Can you tell me why 200k is ok while 100k failed?(they are all 10M/(even number)).Thank you. Best regards, xianda At 2014-05-26 19:42:28,"Jawad Seddar" wrote: Hi xianda, I found out that using a factor of 0.05 in the multiply const works best for me, with USRPs about 50 - 100 cm appart and rx and tx gains set to 0. Try using a sample rate of 200k and you shouldn't get that sample rate error again. Regards, Jawad ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] tx_ofdm and rx_ofdm
Hi xianda, I found out that using a factor of 0.05 in the multiply const works best for me, with USRPs about 50 - 100 cm appart and rx and tx gains set to 0. Try using a sample rate of 200k and you shouldn't get that sample rate error again. Regards, Jawad ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] tx_ofdm and rx_ofdm
Hi: Now I run the example(tx_ofdm and rx_ofdm) through two usrps.(The version of my gnuradio is 3.7.4). 1.But in the receive part I receive two many things like this: INFO: Detected an invalid packet at item 139632 INFO: Parser returned #f INFO: Detected an invalid packet at item 139680 INFO: Parser returned #f INFO: Detected an invalid packet at item 139728 INFO: Parser returned #f INFO: Detected an invalid packet at item 139776 INFO: Parser returned #f INFO: Detected an invalid packet at item 139824 INFO: Parser returned #f INFO: Detected an invalid packet at item 139872 INFO: Parser returned #f INFO: Detected an invalid packet at item 139920 INFO: Parser returned #f INFO: Detected an invalid packet at item 139968 INFO: Parser returned #f INFO: Detected an invalid packet at item 140016 INFO: Parser returned #f INFO: Detected an invalid packet at item 140064 And I search the maillist and I find someone encounter the same problem like me.(http://lists.gnu.org/archive/html/discuss-gnuradio/2013-11/msg00082.html)And I see"As long as the receive SNR is high enough, the problem does not show up."And I try to increase the "Multiply Const" to increase the snr.But it failed.And I try to increase the receive gain.And also failed.Can someone help me?Thank you very much. 2.And in the transmit part: UHD Warning: The hardware does not support the requested TX sample rate: Target sample rate: 0.10 MSps Actual sample rate: 0.195312 MSps And the device I use is USRP N210.And I set the sample rate is 100k. Some days ago,someone tell me set the sample rate 100M/even number.And the 100k seems right,why this UHD warning?Can someone tell me what is the appropriate sample rate for USRP N210?Thank you very much. Any advices will be appreciated.Thank you. Best regards xianda___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Build on ubuntu 14.04
Cython? On Sun, May 25, 2014 at 9:48 PM, Robert McGwier wrote: > And what is the size of the VM disk limited to and how much RAM have you > allowed it? The step you are showing as exiting in (SWIG) requires lots of > resources in building gnuradio. I hate SWIG, but have no idea what in the > world we would do without it. > > > On Sun, May 25, 2014 at 6:16 AM, Marcus Müller > wrote: > >> Hi Michael, >> >> build-grc.sh is not known to me; I think you're referring to >> build-gnuradio? (grc is short for GNU Radio Companion, the graphical >> Flowgraph Designer included in GNU Radio). >> >> There have been problems with builds on Ubuntu 14.04. >> >> However, your output indicates no error; so I'm not quite sure how to >> help you. Maybe put the complete log somewhere on pastebin or >> gist.github.com? >> By the way, pybombs is the recommended way to go for modern systems. >> >> If you really just want a running Linux VM with GNU Radio installed, try >> the LiveDVD images: >> http://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD >> >> Greetings, >> Marcus >> >> >> On 25.05.2014 11:29, Michael Hartje wrote: >> > Dear list, >> > >> > I try to compile the new GR 3.7.4-git. >> > >> > But it breaks with pybombs as well as with the script build-grc.sh >> > The job is done inside of a virtualbox-environment. host: win8.1, guest >> > ubuntu 14.04 + updates >> > >> > Mem 1600 MB >> > >> > cut of the script build-grc.sh log >> > -8< >> > -- CPU missing cvtpi32_ps, Overruled arch avx >> > -- Check size of void*[8] >> > -- Check size of void*[8] - done >> > -- CPU width is 64 bits, Overruled arch 32 >> > -- Available architectures: >> > >> generic;64;3dnow;abm;popcount;mmx;sse;sse2;orc;norc;sse3;ssse3;sse4_a;sse4_1;sse4_2 >> > -- Available machines: >> > >> generic_orc;sse2_64_mmx_orc;sse3_64_orc;ssse3_64_orc;sse4_a_64_orc;sse4_1_64_orc;sse4_2_64_orc >> > -- BUILTTYPERELWITHDEBINFO >> > -- Base cflags = -O2 -g -DNDEBUG >> > -- BUILD INFO ::: generic_orc ::: GNU ::: -O2 -g -DNDEBUG >> > -- BUILD INFO ::: sse2_64_mmx_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 >> > -mmmx -msse -msse2 >> > -- BUILD INFO ::: sse3_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx >> > -msse -msse2 -msse3 >> > -- BUILD INFO ::: ssse3_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx >> > -msse -msse2 -msse3 -mssse3 >> > -- BUILD INFO ::: sse4_a_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx >> > -msse -msse2 -msse3 -msse4a -mpopcnt >> > -- BUILD INFO ::: sse4_1_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx >> > -msse -msse2 -msse3 -mssse3 -msse4.1 >> > -- BUILD INFO ::: sse4_2_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx >> > -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -mpopcnt >> > -- Compiler Version: cc (Ubuntu 4.8.2-19ubuntu1) 4.8.2 >> > Copyright (C) 2013 Free Software Foundation, Inc. >> > This is free software; see the source for copying conditions. There is >> NO >> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> PURPOSE. >> > -- Loading build date Thu, 22 May 2014 18:56:46 into constants... >> > -- Loading version 0.1 into constants... >> > -- Using install prefix: /usr/local >> > -- ENABLE_GR_LOG set to ON. >> > -- HAVE_LOG4CPP set to False. >> > -- LOG4CPP_LIBRARIES set to . >> > -8< >> > and some lines down during config of gnuradio >> > -8< >> > -- Boost version: 1.54.0 >> > -- Found the following Boost libraries: >> > -- date_time >> > -- program_options >> > -- filesystem >> > -- system >> > -- thread >> > -- Enabling use of known bad versions of Boost. >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > > > -- > Bob McGwier > Co-Owner and Technical Director, Federated Wireless, LLC > Professor Virginia Tech > Senior Member IEEE, Facebook: N4HYBob, ARS: N4HY > Faculty Advisor Virginia Tech Amateur Radio Assn. (K4KDJ) > > ___ > 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] Build on ubuntu 14.04
On ARM it was with 4 threads initially then re-running with 1 thread gave the same error. That 3.0.6x distro kernel was built without swap so I had to build and install a new kernel with swap. The first go with 2GB swap also failed and I had to make another 2GB swap file and add it with swapon. The base memory is 1GB and with a 4GB swapfile enabled in /etc/fstab I have had no more problems building gnuradio 3.6.5 and a while back 3.7.3git. 73 ... Sid. On 26/05/14 09:08, Martin Braun wrote: Hi Michael and Sid, how many compiler threads are you spawning? When you use 1 (i.e. make -j1), is this still a problem? M On 25.05.2014 11:29, Michael Hartje wrote: Dear list, I try to compile the new GR 3.7.4-git. But it breaks with pybombs as well as with the script build-grc.sh The job is done inside of a virtualbox-environment. host: win8.1, guest ubuntu 14.04 + updates Mem 1600 MB cut of the script build-grc.sh log -8< -- CPU missing cvtpi32_ps, Overruled arch avx -- Check size of void*[8] -- Check size of void*[8] - done -- CPU width is 64 bits, Overruled arch 32 -- Available architectures: generic;64;3dnow;abm;popcount;mmx;sse;sse2;orc;norc;sse3;ssse3;sse4_a;sse4_1;sse4_2 -- Available machines: generic_orc;sse2_64_mmx_orc;sse3_64_orc;ssse3_64_orc;sse4_a_64_orc;sse4_1_64_orc;sse4_2_64_orc -- BUILTTYPERELWITHDEBINFO -- Base cflags = -O2 -g -DNDEBUG -- BUILD INFO ::: generic_orc ::: GNU ::: -O2 -g -DNDEBUG -- BUILD INFO ::: sse2_64_mmx_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -- BUILD INFO ::: sse3_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -- BUILD INFO ::: ssse3_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -mssse3 -- BUILD INFO ::: sse4_a_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -msse4a -mpopcnt -- BUILD INFO ::: sse4_1_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -- BUILD INFO ::: sse4_2_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -mpopcnt -- Compiler Version: cc (Ubuntu 4.8.2-19ubuntu1) 4.8.2 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Loading build date Thu, 22 May 2014 18:56:46 into constants... -- Loading version 0.1 into constants... -- Using install prefix: /usr/local -- ENABLE_GR_LOG set to ON. -- HAVE_LOG4CPP set to False. -- LOG4CPP_LIBRARIES set to . -8< and some lines down during config of gnuradio -8< -- Boost version: 1.54.0 -- Found the following Boost libraries: -- date_time -- program_options -- filesystem -- system -- thread -- Enabling use of known bad versions of Boost. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] pfb_arb_resampler test fail (3.7.3)
Hi all guys, I am experiencing error when testing 3.7.3. The error report is following: OK Using Volk machine: avx_64_mmx -- Process completed Passed 95/177 Testing qa_pfb_arb_resampler Test command: /bin/sh /home/savi_ne/tools/gnuradio-3.7.3/build/gr-filter/python/filter/qa_pfb_arb_resampler_test.sh Test timeout computed to be: 9.99988e+06 ...F. == FAIL: test_ccf_001 (__main__.test_pfb_arb_resampler) -- Traceback (most recent call last): File "/home/savi_ne/tools/gnuradio-3.7.3/gr-filter/python/filter/qa_pfb_arb_resampler.py", line 153, in test_ccf_001 self.assertComplexTuplesAlmostEqual(expected_data[-Ntest:], dst_data[-Ntest:], 2) File "/home/savi_ne/tools/gnuradio-3.7.3/gnuradio-runtime/python/gnuradio/gr_unittest.py", line 74, in assertComplexTuplesAlmostEqual self.assertComplexAlmostEqual (a[i], b[i], places, msg) File "/home/savi_ne/tools/gnuradio-3.7.3/gnuradio-runtime/python/gnuradio/gr_unittest.py", line 47, in assertComplexAlmostEqual (msg or '%s != %s within %s places' % (`first`, `second`, `places` )) AssertionError: (-0.32564974754236342-0.94549047690899302j) != (-0.56183856725692749-0.82724255323410034j) within 2 places The processor is Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz. I use RHEL6. Has anybody experienced this prolem? Best, -- Nemanja Savić ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to set a master clock rate on USRP B200
Thank you, In GRC, I changed Clock Rate (Hz) by giving a value of 28e6 and it works now. Date: Sun, 25 May 2014 23:41:01 -0400 From: mle...@ripnet.com To: user0...@gmail.com CC: raf...@hotmail.fr; Discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] How to set a master clock rate on USRP B200 On 05/25/2014 11:39 PM, jason sam wrote: "device args" parameter is not in the UHD USRP source/sink block?There is only 'Device addr' Sorry, I meant Device Addr On Fri, May 23, 2014 at 9:39 PM, Marcus D. Leech wrote: On 05/23/2014 12:23 PM, raf raf wrote: Hello All Gnu Radio user, To use a 2 TX, I want to change a clock rate to an accepted one, under 30.72 MHz. I use the API with uhd_usrp_probe and it works only for this command. Can you give me the idea or python code to use this argument parameter with a python flowgraph? --args="master_clock_rate=28" Thanks. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio In GRC, where it has a "device args" parameter, that's wher this master_clock_rate=28e6 should go. I assume you meant 28e6, rather than 28. Everything is in Hz, and there's no way the B200 can go down to a clock rate of 28Hz. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ 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] Build on ubuntu 14.04
Hi Michael and Sid, how many compiler threads are you spawning? When you use 1 (i.e. make -j1), is this still a problem? M On 25.05.2014 11:29, Michael Hartje wrote: Dear list, I try to compile the new GR 3.7.4-git. But it breaks with pybombs as well as with the script build-grc.sh The job is done inside of a virtualbox-environment. host: win8.1, guest ubuntu 14.04 + updates Mem 1600 MB cut of the script build-grc.sh log -8< -- CPU missing cvtpi32_ps, Overruled arch avx -- Check size of void*[8] -- Check size of void*[8] - done -- CPU width is 64 bits, Overruled arch 32 -- Available architectures: generic;64;3dnow;abm;popcount;mmx;sse;sse2;orc;norc;sse3;ssse3;sse4_a;sse4_1;sse4_2 -- Available machines: generic_orc;sse2_64_mmx_orc;sse3_64_orc;ssse3_64_orc;sse4_a_64_orc;sse4_1_64_orc;sse4_2_64_orc -- BUILTTYPERELWITHDEBINFO -- Base cflags = -O2 -g -DNDEBUG -- BUILD INFO ::: generic_orc ::: GNU ::: -O2 -g -DNDEBUG -- BUILD INFO ::: sse2_64_mmx_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -- BUILD INFO ::: sse3_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -- BUILD INFO ::: ssse3_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -mssse3 -- BUILD INFO ::: sse4_a_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -msse4a -mpopcnt -- BUILD INFO ::: sse4_1_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -- BUILD INFO ::: sse4_2_64_orc ::: GNU ::: -O2 -g -DNDEBUG -m64 -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -mpopcnt -- Compiler Version: cc (Ubuntu 4.8.2-19ubuntu1) 4.8.2 Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Loading build date Thu, 22 May 2014 18:56:46 into constants... -- Loading version 0.1 into constants... -- Using install prefix: /usr/local -- ENABLE_GR_LOG set to ON. -- HAVE_LOG4CPP set to False. -- LOG4CPP_LIBRARIES set to . -8< and some lines down during config of gnuradio -8< -- Boost version: 1.54.0 -- Found the following Boost libraries: -- date_time -- program_options -- filesystem -- system -- thread -- Enabling use of known bad versions of Boost. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to set a master clock rate on USRP B200
On 26.05.2014 08:43, Marcus Müller wrote: There is a device args field in the current version of GNU Radio, so this might be where the confusion comes from. Yes, for the record: In UHD, 'args' and 'addr' (address) are the same thing. So, this is an addr: "type=b200,master_clock_rate=28e6". Clearly, this is *both* an address and an argument, which is where confusion can come from. - Martin ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Error: /media/Softwares & Data/UBUNTU DOWNLOADS/top_block.py:1:1:FATAL:PARSER:ERR_DOCUMENT_EMPTY: Start tag expected, '<' not found
Hi Marcus, This python code is generated from GRC. On Mon, May 26, 2014 at 11:52 AM, Marcus Müller wrote: > Hi Ali, > > we're always thankful for feedback; the information you supply is a little > sparse. > Usually, I'd ask you to refer to > http://gnuradio.org/redmine/projects/gnuradio/wiki/ReportingErrors , but > in this case, things are easy enough to guess just from your wording: > > > When i execute a GRC file > > GRC files are just saved representations of your flow graph (in XML). You > can't execute them. > What you do is let the companion generate a python file out of them and > execute that. > You tried to load such a python file like it was a GRC file; this can't > work. > > Greetings, > Marcus > > > On 26.05.2014 08:42, jason sam wrote: > > The code is as attached. > > > On Mon, May 26, 2014 at 9:42 AM, jason sam > wrote: > > > When i execute a GRC file i get the following error.Any info about that? > Regards, > Ali > > > > > ___ > Discuss-gnuradio mailing > listDiscuss-gnuradio@gnu.orghttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > ___ > 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
