thing related to the field of free software radio, please
head to:
https://penta.fosdem.org/submission/FOSDEM21
and submit your short abstract! We're looking very much forward to your
submission.
For the committee,
Nicolas
On Sat, Dec 5, 2020 at 11:36 AM Nicolas Cuervo Benavides &l
is stream-ready. When complete,
the recording will be located into the streaming system, and Bob's your
uncle.
Don't forget that you **must** be available during the allocated timeslot
of your talk for live Q&A.
** Steering Committee
The track committee consists of:
*
free software radio, please
head to:
https://penta.fosdem.org/submission/FOSDEM20
and submit your short abstract! We're looking very much forward to your
submission.
For the committee,
Nicolas Cuervo
On Wed, Oct 16, 2019 at 8:19 PM Nicolas Cuervo Benavides <
cuervonico...@gma
Hi all,
I've been recently working on porting gr-radar to work to GNU Radio 3.8.
These changes can be found in my fork here:
https://github.com/primercuervo/gr-radar
If you'd like to play around with it, please checkout the "maint-3.8"
branch and install in on top of a working GNU Radio 3.8.
I'v
we were always full to the brim with presentations, so if
you want to present, please make sure to submit your abstracts soon!
** Steering Committee
The track committee consists of:
* Phil Balister - "Crofton"
* Sylvain Munaut -"tnt"
* Derek Kozel - "dkozel"
* Nicol
Hey Arpit,
thanks for your answer. As if you should proceed using both the tools: if
you think it's worth it, go for it. But be careful about the timeframe of
the program. You might don't want to spend a significant portion of the
already limited coding time into doing the parsing twice. Here I ha
icolas,
> Thank you for your valuable response.
> As per your suggestion, I again read the information in all the links you
> mentioned and made some necessary changes. Also, tried my best to correct
> all the typos along with fixing grammatical errors.
>
> Regards,
> Arpit Gupta
>
Hi Arpit,
It's great that you've come up with a complete proposal. There are,
however, a couple of things that you might want to consider and add/correct
before you get any significant review from our side:
- Please be sure to read *all* the information that we provide to
applicants (below I'll l
Hi Arpit!
allow me to give you this time a warm welcome to the mailing list and to
the GSoC application process! I'm very glad to see the enthusiasm you've
been putting the last few weeks into your preparation and the project.
I can also see that you've taken the right idea from the comments from
Hi Grecia,
I'm very glad to hear that you're interested in GSoC and, ultimately, in
contributing to the free software community! Given your interests and
experience, GNU Radio is without a doubt the right project where you'll be
able to share your knowledge while learning from those who are sharin
Hello Alejandra,
please set up the USB udev triggers so that non-root users can have access
to the device. Follow the instructions that can be found in our manual [1].
Remember to unplug and plug your device after you have followed the
required steps.
Regards,
-Nicolas
[1] https://files.ettus.c
Hello Vikenesh,
could you run PyBOMBS with a higher verbosity level and send us the output?
You can do so by adding the `-vv` flag just after `pybombs`.
Cheers,
- Nicolas
On Wed, May 23, 2018 at 2:49 PM, Coundjidapadame Vikenesh <
vikenesh.coundjidapad...@gmail.com> wrote:
> Hi everybody,
>
>
You can see to which UHD image it corresponds in our application note on
"Mapping between ER USRP and NI-USRP product numbers" [1]
You can use the uhd_image_downloader.py to get the FPGA images directly
into your computer, and then load the corresponding to the N210 using the
uhd_image_loader as p
Hi all!
congratulations to Luca and Swapnil for being accepted for this year's
GSoC! Both had very good proposals but also have been active in the
community which is fantastic.
I am very excited to be part of the mentors this year. I'm looking forward
working with Swapnil on this project :)
All
gt;>>> Regarding Python compatibility - I will work upon version independent
>>>> compatibility using information from the following links:
>>>> Link[1] <http://python3porting.com/noconv.html> Link[2]
>>>> <http://python-future.org/compatible
Hello Luca!
Thank you for showing interest in GSoC (once again! :) )
Your idea sounds very cool and also very useful for users that want to have
a first approach to MIMO, and you did your homework checking where this
idea fits in the tree, and propose reuse of code, which is fantastic. As
you men
Hello Valian,
Thank you for your interest in GNU Radio and GSoC!
that compass you put together seems like a good start for what we'd like to
have. Answering your question: optimally we'd like to have all the ones
that are listed (and probably even more if we see the necessity or
applicability of
Hello Swapnil Negi,
Thank you for your proposal! This project has been in the pipeline for long
and I'm very excited to see your interest in working on it. I have very few
comments for now, but the discussion can definitely continue open:
So the timeline that you are proposing is:
1) Python3 Comp
Hi there!
We are very glad that you find interest in contributing to GNU Radio and
GSoC! You are definitely on the right road by getting familiarized with the
software and its perks by installing it and following the guided tutorials.
If you have any question regarding functionality that you want
Hello Sakthivel,
did the installation run to completion without any warning/error? Which OS
are you using?
assuming a linux-based machine, did you run the following command after
installation?
$ sudo ldconfig
please try to do so and tell us if it worked.
-Nicolas
On Thu, Dec 28, 2017 at 12
Hi Kyeong,
I see only one gr-doa around [1]. Could you point out which other
implementation is called gr-doa? I would agree that these conflicts would
be better addressed properly instead of hacky approaches.
Regards,
- Nicolas
[1]https://github.com/EttusResearch/gr-doa
On Fri, Nov 3, 2017 at
Hello Richard,
I believe the best way (so far) would be to actually go to the repository
that you want to rebuild and checkout to the different specific branch/tag
and then trigger the rebuild with
$ pybombs -p *your_prefix* rebuild *uhd*
You can rebuild faster by adding the '-k' flag at the
Hello George,
this question would be better posted in the USRP-usrs list. However, the
answer to this is "yes". There is a known issue on the B210 when using
GPSDOs and it's report of PLL lock. Are you using the clock reference only
from the GPSDO mounted on each of the USRPs? or are you also expo
Hello Hadhami,
did you give a look at this thread [1]? You can see that you are maybe
having the exact same problem, i.e. you are not linking against the ITPP
library (libs such as libitpp.so.* are not listed as linked).
Try running:
$ sudo ldconfig
then try again. If the problem persists,
inux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import a1System
> >>> from a1System import TargetDetector_cf
> Traceback (most recent call last):
> File "", line 1, in
> ImportError
inux-gnu/libboost_thread.so.1.58.0
> (0x7fc09d92d000)
>
> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1
> (0x7fc09d725000)
>
> /lib64/ld-linux-x86-64.so.2 (0x55ff2d4b7000)
>
> liborc-0.4.so.0 => /usr/lib/x86_64-li
Hello Sinta,
This specific question is handled in the GNURadio FAQ [1]. Please try to
use the scipy.fromfile() method and check if the output agrees with your
expectations.
Regards,
- Nicolas
[1]
https://wiki.gnuradio.org/index.php/FAQ#What_is_the_file_format_of_a_file_sink.3F_How_can_I_read_fil
Hi,
it is nice that you look for the error before posting, but does your module
actually need the ITPP libraries? because that might have been something
specific for the case that you quoted.
To check if your problem is linking, first run the following command:
$ sudo ldconfig
and then try
Hello Ann,
This question might be best addressed in the [USRP-users] list, as it might
be device specific, and you are not explicitly stating if you are using
GNURadio for your application.
Before moving your post there, have the following questions in
consideration:
* Are you still seeing this
Hello Yang,
it is true that each block will have its own thread in GNURadio, but, in
any case, your resources are limited when it comes to CPU processing. What
seems to be happening is that one of your paths is demanding resources and,
when it gets them, leaves the other path without enough resour
Hello Tellrell,
the description that you are making as a possible solution to your problem
sounds very reasonable in many ways. As an informative example for the
command messages. you can check the "uhd_msg_tune.grc" example in
gnuradio/gr-uhd [1] where the uhd control over message is shown.
A se
released? Is there a link?
>
> Thanks a lot
>
> 2017-01-26 16:26 GMT+01:00 Nicolas Cuervo :
>
>> Hi Tschuls,
>>
>> This problem has been found, reported and there is already a fix for it.
>> It will come soon for gnuradio:master and maint.
>>
>>
Hi Tschuls,
This problem has been found, reported and there is already a fix for it. It
will come soon for gnuradio:master and maint.
regards,
-Nicolas
On Thu, Jan 26, 2017 at 4:02 PM, Tschuls Lebarski <
tschuls.lebar...@gmail.com> wrote:
> Hi
> I'm a newbee and trying to run gr-uhd/examples/g
>>
>>> Best regards,
>>>
>>> Marcus
>>> On 01/16/2017 12:55 PM, Usman Haider wrote:
>>>
>>> Hello Nicolas,
>>>
>>> Thanks for your reply. I have sufficient disk space, more than 400 GB,
>>> so that is not an issue.
Hello Usman,
uhm, this is odd. So far I can see the command is correct. Although error
128 means that git did not exit cleanly, and I just run it and it ran fine.
Just some guesses for now:
1. Do you have enough disk space? the recipes do not require a lot of disk
space, though, but not enough sp
cause gnuradio-companion wasn't running
> (command not found error) when I tried to execute it from the command line.
>
> Thanks,
> Vishwesh
>
>
>
> On Mon, Dec 12, 2016 at 2:04 AM, Nicolas Cuervo
> wrote:
>
>> Hello Vishwesh,
>>
>> that recipe inst
/setup_env.sh
>
> and gnuradio using apt-get install...
>
> Thanks,
> Vishwesh
>
>
>
> On Mon, Dec 12, 2016 at 1:26 AM, Nicolas Cuervo
> wrote:
>
>> Hello Vishwesh,
>>
>> I believe that in this case it is only a matter of where the blocks are
>> in
Hello Vishwesh,
I believe that in this case it is only a matter of where the blocks are
installed, and where grc is looking for them. When you install OOT modules
(gr-ettus is itself an OOT module for RFNoC) it also has an installation
path, where GRC is going to be looking for the blocks that are
ght I could instantiate my block as
> noc_block_fir #(USE_HLS=1) inst_noc_block_fir (...);
> in rfnoc_ce_auto_inst_x310.v and bypass that step
> But that gave me a syntax error.
>
> So I guess I need to figure out how to write my own noc_block_fir.v
> If there indeed is an alternat
ock_fir_filter.v to add the USE_HLS in there."
>
> Currently the noc_block_addsub.v file has USE_HLS = 0. Does this mean it
> isn't using the HLS sources?
>
> Just to clarify, I want to add my own custom 'fir' block written in HLS, I
> don't want to use the
h 8-285] failed synthesizing module 'x300_core'
> [/home/vrege/rfnoc/src/uhd-fpga/usrp3_rfnoc/top/x300/x300_core.v:2]
> ERROR: [Synth 8-285] failed synthesizing module 'x300'
> [/home/vrege/rfnoc/src/uhd-fpga/usrp3_rfnoc/top/x300/x300.v:15]
>
Hello Vikesh,
Please take a look at this section of our "Getting started with RFNoC
Development" guide, specifically the "wiring CE" section [1]. As Marcus
stated, NoC blocks start with "noc_block_", and this is the way to identify
them in the sources.
On 12/06/2016 10:37 PM, Vishwesh Rege wrote:
Hello Jason,
I just ran the same line that you ran and I see gnuradio-companio in
prefix/bin/ and I can also run it after setting up the environment.
Could you please update the recipes and see if this solves this:
pybombs recipes update
Also, you can also update pybombs to see if it also he
Hey all,
I've noticed that gr_modtool eventually segfaults on shutdown while running
'newmod' and/or 'add' (with the other options it may come up, but I don't
use them as often and I also don't have a way to consistently replicate
this behavior).
I ran a backtrace, in this case for 'gr_modtool ad
Hi Tom,
Did you, after you install your OOT module, run the following in your
terminal?:
sudo ldconfig
Cheers,
- Nicolas
On Fri, Nov 11, 2016 at 9:43 PM, Tom Early wrote:
> Sorry, me again.
>
> Recently did a fresh install of ubuntu 16.10 and did a apt install of
> gnuradio.
>
> A few da
Hello Sean,
after you built and install your OOT block, did you ran:
$ sudo ldconfig
?
Cheers,
-Nicolas
On Wed, Oct 12, 2016 at 1:42 PM, Sean Horton wrote:
> I have followed the following example, the only difference being:
> step 1) I didn't use tutorial as the name,
> step 2) I named
the signal source block like the
> parameters would suggest, is it?
> My expectation with forcing a long period was it'd stream high for 10s and
> low for 10s.
>
> On Tue, Sep 6, 2016 at 1:24 PM, Nicolas Cuervo
> wrote:
>
>> Hi Santos,
>>
>> inside the n
Hi Santos,
inside the number sink there is a field called "Update Period", which you
can reduce to a value that suits your needs. For what I understand of your
setup, maybe you have a rather big number here in comparison with the
update rate of the sink. Try reducing this value and let us know if
Hi Berat,
I might be wrong, but it appears to be an autotools problem, as it doesn't
seem to find the aclocal. You can try running:
sudo apt-get install autotools-dev
sudo apt-get install automake
maybe you'd have to install also aclocal via apt-get. I tried installing
the gnss recipe via pybom
Hi Berat,
Could you tell us what type of failure are you getting? You could copy and
paste the error here to the mailing list.
Also, after sourcing the setup_env.sh you should be able to run the in the
same shell the following command:
$ gnuradio-companion
to open the grc. Are you able to?
Hi all,
So far I've been installing all from source and everything had been
(almost) fine. However I wanted to check what was all the buzz about
PyBombs so I gave it a try. Now I'm getting the same output that Mike was
getting.
ERROR - Could not run pip list. Hm.
ERROR - Command '['pip', 'list']'
In particular, does the detector detect anything? Basically, is
> anything happening pre-CRC-check?
>
> M
>
> On 02/11/2016 06:30 AM, Nicolas Cuervo Benavides wrote:
> > Hi list!
> >
> > I've been playing around with the OFDM TX/RX for a while, and I thought
&
Hi list!
I've been playing around with the OFDM TX/RX for a while, and I thought it
would be interesting to send over the air custom messages and display the
waveform at the receiver. For that purpose, I took the chat sanitizer and
receiver block that I came across from [1]. The OFDM header modula
Hi Sylvain,
Sorry for reviving a relatively old issue. I see that you mentioned some
tweaking to be done on the fft block when the signal are weak. I'm
currently working on an application using this RFNoc blocks and I'm having
that problem: I'm calculating the power received at my radio and below
h, because you're placing additional
> constraints on the scheduler. I try to avoid it unless I find I really need
> it. I almost never need it.
>
> Hope that helps,
> Rich
>
> On Thu, Sep 10, 2015 at 9:37 AM, Martin Braun
> wrote:
>
>> On 10.09.2015 07:25,
Hi all,
I've been trying to create a block that helps me comparing two signals, and
in order to achieve that I want to take a snapshot of one of them to
characterize it in terms of mean and maximum value. The inputs are always
positive and greater than zero. That part of the code goes as follows:
Hi all,
I have a question regarding the timed packets with UHD. Basically I'm
sending packets from a burst tagger into my UHD sink with a tx_time tag,
but after a while I'm getting L's (late packet, if I'm not wrong) at the
output.
I tried changing both the packet size and the sample rate of my f
Hi all,
Right now I'm implementing tx and rx on the same device (USRP b210), and
I'm trying to synchronize the two in order to determine the exact moment
when a message is sent by the Tx. The purpose of this synchronization is to
add an idle state for tx right after the "sending state", so the Rx
t; These should also include ${GNURADIO_ALL_LIBRARIES}.
>
> Best regards,
> Marcus
>
>
>
> On 05/19/2015 10:40 AM, Nicolas Cuervo Benavides wrote:
>
> Hi all,
>
> I'm having right now problems with a implementation of a time tag in a
> block that I'
Hi all,
I'm having right now problems with a implementation of a time tag in a
block that I'm writing. I'm basically writing a burst tagger with SOB, EOB
and TX_TIME tags. The first two are working, but the third (the one that
uses a UHD function), is giving me problems.
I recognized that the pa
Solved.
I needed just to type "sudo ldconfig" and afterwards it works like a charm.
Thanks to all who read the problem.
On Thu, May 14, 2015 at 10:02 PM, Nicolas Cuervo Benavides <
cuervonico...@gmail.com> wrote:
> Hello all,
>
> I was woking debuging an error that
Hello all,
I was woking debuging an error that appear in my application, and in order
to do that I intended to create a really simple block that basically just
connected the output with the input as a bypass, and then I was going to
modify it with more features to understand the error. All the bui
Hi all!
Im trying to implement a system that should change it's normal functioning
when another system with higher priority comes into play. For that, we have
thought of two ways: changing the central frequency of our system of
interest and/or stopping the sending process automaticaly.
Im in char
Hello all,
I'm new in GNURadio and right now I am understanding a little bit on how
the pmt work and how can it be read.
For that I'm taking this project as a base:
https://github.com/bastibl/gr-ieee802-15-4, working on the MAC layer
(modifying mac.cc and mac.h so far) and from here I want to ext
64 matches
Mail list logo
