[Discuss-gnuradio] Web features: RSS, Issues, Twitter
Hi everyone, I'd like to point out a couple of online features you might be unaware of: == RSS feeds == Our Redmine website offers the option to subscribe to RSS feeds filtered by whatever you're interested in. For example, the current state of the issue tracker can be subscribed to here: http://gnuradio.org/redmine/projects/gnuradio/issues.atom You can also subscribe to individual issue's feeds (simply open an issue and scroll to the bottom), or get one large feed on everything happening, filtered by whatever you're interested in at the Activity tab: http://gnuradio.org/redmine/projects/gnuradio/activity (Again, find the feed URL at the end of the page.) This includes commits, news etc. == Issue tracker == Although you've probably seen this, I'd like to remind everyone that we've changed our habits concerning the issue tracker, which you can find at: http://gnuradio.org/redmine/projects/gnuradio/issues All bugs and feature requests run through here, so please, if you have something to report, post it there (you need to sign up for spambot-related reasons, read this: http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#How-can-I-post-on-this-wiki-use-the-bug-tracker). == Twitter, Blogs etc. == There are two Twitter feeds dedicated to GNU Radio: https://twitter.com/gnuradio https://twitter.com/GNURadioWaves Also, Tom has a blog documenting the ongoings of GNU Radio: http://www.trondeau.com/ Of course, while we're on social media web 2.0 fancy shiny stuff, you can follow and fork us on github: https://github.com/gnuradio MB -- Karlsruhe Institute of Technology (KIT) Communications Engineering Lab (CEL) Dipl.-Ing. Martin Braun Research Associate Kaiserstraße 12 Building 05.01 76131 Karlsruhe Phone: +49 721 608-43790 Fax: +49 721 608-46071 www.cel.kit.edu KIT -- University of the State of Baden-Württemberg and National Laboratory of the Helmholtz Association pgp8LMldJ0twq.pgp Description: PGP signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Can I add timesamples to tx samples
2013/2/22 11:44, Josh Blum wrote: On 02/21/2013 09:20 PM, Gong Zhang wrote: Hi, Considering we can get timesamples of rx samples from UHD in metadata,can I add timesamples to tx samples,which would be send together. Thanks. Sure thing! This link points to some of the examples: http://code.ettus.com/redmine/ettus/projects/uhd/wiki/GNU_Radio_UHD#Using-UHD-Software-with-GNU-Radio And here is a project that uses the timestamps to do TDMA: https://github.com/jmalsbury/pre-cog/wiki -josh Do the timesamples record the time rx/tx samples going through AD/DA in USRP(FPGA)? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Problem writing custom null sync block
Hi list, I'm writing a custom null sync block called "file_writer". What I want to do is dump (to file or screen) what my null sync is receiving). The problem is that if I use the file_writer in a flow graph, after the "work" function is executed a few times it starts to receive the same input forever. I created a simple flow graph in gnuradio-companion that shows the FFT of the signal received in a USRP source. When I modify the generated python code and insert the file_writer right after a stream_to_vector block, the flow graph "hangs" and process the same data over and over again. Any suggestions of what is missing ? Here's the code of my simple block: class file_writer(gr.sync_block): ## CTOR # def __init__(self, filename, vec_size): gr.sync_block.__init__( self, "file name block", in_sig = [np.dtype((np.float32, vec_size))], out_sig = None ) self._fd = open(filename, 'w') self._filename = filename def work(self, input_items, output_items): in0 = input_items[0] print "## ", len(in0) print in0 return len(output_items) -- View this message in context: http://gnuradio.4.n7.nabble.com/Problem-writing-custom-null-sync-block-tp39796.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
[Discuss-gnuradio] AttributeError: 'module' object has no attribute 'square_ff'.
hi everyone,i have made my own block in gnuradio name square_ff from out of tree module.i hsvr successfully interfaced it with gnuradio.but problem is when i want to use that block in gnuradio then the following error i get in terminal. AttributeError: 'module' object has no attribute 'square_ff'. kindly help me ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem writing custom null sync block
On Fri, Feb 22, 2013 at 8:42 AM, maiconkist wrote: > Hi list, > > I'm writing a custom null sync block called "file_writer". What I want to do > is dump (to file or screen) what my null sync is receiving). > > The problem is that if I use the file_writer in a flow graph, after the > "work" function is executed a few times it starts to receive the same input > forever. > > I created a simple flow graph in gnuradio-companion that shows the FFT of > the signal received in a USRP source. > When I modify the generated python code and insert the file_writer right > after a stream_to_vector block, the flow graph "hangs" and process the same > data over and over again. > > Any suggestions of what is missing ? > > Here's the code of my simple block: > > > class file_writer(gr.sync_block): > ## CTOR > # > def __init__(self, filename, vec_size): > gr.sync_block.__init__( > self, > "file name block", > in_sig = [np.dtype((np.float32, vec_size))], > out_sig = None > ) > > self._fd = open(filename, 'w') > self._filename = filename > > > def work(self, input_items, output_items): > in0 = input_items[0] > > print "## ", len(in0) > print in0 > > return len(output_items) What is the length of output_items? Because you don't have an output buffer attached to this block, I'd be concerned that len(output_items) == 0, so you're telling the scheduler that you aren't consuming any data. Maybe just replace that last line with 'return len(input_items)'? Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] AttributeError: 'module' object has no attribute 'square_ff'.
On Fri, Feb 22, 2013 at 9:02 AM, Omer Omer wrote: > hi everyone,i have made my own block in gnuradio name square_ff from out > of tree module.i hsvr successfully interfaced it with gnuradio.but problem > is when i want to use that block in gnuradio then the following error i get > in terminal. > > *AttributeError*: 'module' *object* has no attribute '*square_ff*'. > > kindly help me** > > ** > Have you run 'make install'? Where are you installing it to? You can check your python2.7/dist-packages directory (in whatever install prefix you used) to make sure that it's there. Then make sure PYTHONPATH is pointing to that directory so Python knows where to find it. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Is git repository down today?
On Fri, Feb 22, 2013 at 2:52 AM, Songsong Gee wrote: > I've tried to install GNU Radio with build-gnuradio script. > > But every time it fails and says 'could not find gnuradio-core after > checkout git checkout' something Try again. I just checked and everything appears to be working normally. Might have just hit it during some network outage or some other transient issue. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] RRC Polyphase Filter in generic modulator
Thanks martin for your explanation. I modified the dbpsk_loopback.grc example to where my input sampling frequency is 16khz and instead of looping back i'm using a uhd sink block with a sampling rate of 256khz. Looking at the constellation on my spectrum analyzer i'm getting a dbpsk signal with a symbol rate of 128khz. Since the flowgraph seems to be working i'm expecting an interpolation factor of 16 somewhere i originally was trying to do it with a FIR filter before sending it to the usrp but then i found out that modulation block itself has an internal rrc filter. Now I am trying to figure out where the interpolation factor of 16 is occurring in the polyphase filter. I'm confused how things are working without an explicit interpolation factor of 16. I'm not sure if the issue is my lack of understanding of polyphase filters or I didn't see where the interpolation factor is calculated internally. Thanks On Feb 22, 2013 2:39 AM, "Martin Braun (CEL)" wrote: > Almohanad, > > perhaps the examples in gr-digital/examples/demod are more suitable to > understand the internals. > > A couple of notes: > > > On Thu, Feb 21, 2013 at 08:58:42PM -0500, Almohanad Fayez wrote: > > I've been trying to understand what's happening under the hood with the > > polyphase filter bank in the generic_mod_demod.py. > > > > > > Here's what I think is happening, since nfilt=32 which is also used the > > sampling rate of the firdes.root_raised_cosine filter means that the > highest > > rate the polyphase filter will see is an interpolation factor of 32 from > the > > basic inputted signal sampling frequency? > > PFB filter taps operate on what you could think of as 'fractional' > time, i.e. the sampling time is 1/32th (or whatever) of the original > sampling time. If you have a cutoff frequency in your low pass, that > must be taken care of in the filter taps (i.e. reduced by factor 32). > If you're specifying absolute frequencies, just increase the sampling > frequency (hm, I'm not sure this is really clear...). > > > the default case is =2 ... does this mean that the polyphase filter is > > interpolating by a factor of 2? > > When going from symbols to samples, you always have to interpolate. > Usual values are 2 (as used here) or 4. > > > If I am inputting data at a sampling rate of 16kHz and I'm trying to > > interpolate them to 256kHz before sending them to the user how is the > 256kHz > > and the desired interpolation factor of 16 taken into account in the RRC > filter > > in the generic modulator block. > > I don't understand this Q. The answer is probably, you'll need an extra > interpolation block, depending on how your FG looks like. > > > I've read the gnuradio pfb page but I think I'm missing something > important > > here. > > Just to be clear, you do know what an FIR does and how filter taps are > defined? Or is this the information you're lacking? > > MB > > -- > Karlsruhe Institute of Technology (KIT) > Communications Engineering Lab (CEL) > > Dipl.-Ing. Martin Braun > Research Associate > > Kaiserstraße 12 > Building 05.01 > 76131 Karlsruhe > > Phone: +49 721 608-43790 > Fax: +49 721 608-46071 > www.cel.kit.edu > > KIT -- University of the State of Baden-Württemberg and > National Laboratory of the Helmholtz Association > > ___ > 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] RRC Polyphase Filter in generic modulator
On Fri, Feb 22, 2013 at 9:29 AM, Almohanad Fayez wrote: > Thanks martin for your explanation. I modified the dbpsk_loopback.grc > example to where my input sampling frequency is 16khz and instead of looping > back i'm using a uhd sink block with a sampling rate of 256khz. Looking at > the constellation on my spectrum analyzer i'm getting a dbpsk signal with a > symbol rate of 128khz. > > Since the flowgraph seems to be working i'm expecting an interpolation > factor of 16 somewhere i originally was trying to do it with a FIR filter > before sending it to the usrp but then i found out that modulation block > itself has an internal rrc filter. Now I am trying to figure out where the > interpolation factor of 16 is occurring in the polyphase filter. > > I'm confused how things are working without an explicit interpolation factor > of 16. I'm not sure if the issue is my lack of understanding of polyphase > filters or I didn't see where the interpolation factor is calculated > internally. > > Thanks How many samples/symbol are you using? And I would actually print this number out from inside generic_mod_demod.py. There's some calculations that are done early on to help you match your specified bit rate with the sample rate required by the USRP (if you ask for 16 kbps, it will automatically set the sps high to match what the USRP tells you it's closest sample rate is). Tom > On Feb 22, 2013 2:39 AM, "Martin Braun (CEL)" wrote: >> >> Almohanad, >> >> perhaps the examples in gr-digital/examples/demod are more suitable to >> understand the internals. >> >> A couple of notes: >> >> >> On Thu, Feb 21, 2013 at 08:58:42PM -0500, Almohanad Fayez wrote: >> > I've been trying to understand what's happening under the hood with the >> > polyphase filter bank in the generic_mod_demod.py. >> > >> > >> > Here's what I think is happening, since nfilt=32 which is also used the >> > sampling rate of the firdes.root_raised_cosine filter means that the >> > highest >> > rate the polyphase filter will see is an interpolation factor of 32 from >> > the >> > basic inputted signal sampling frequency? >> >> PFB filter taps operate on what you could think of as 'fractional' >> time, i.e. the sampling time is 1/32th (or whatever) of the original >> sampling time. If you have a cutoff frequency in your low pass, that >> must be taken care of in the filter taps (i.e. reduced by factor 32). >> If you're specifying absolute frequencies, just increase the sampling >> frequency (hm, I'm not sure this is really clear...). >> >> > the default case is =2 ... does this mean that the polyphase filter is >> > interpolating by a factor of 2? >> >> When going from symbols to samples, you always have to interpolate. >> Usual values are 2 (as used here) or 4. >> >> > If I am inputting data at a sampling rate of 16kHz and I'm trying to >> > interpolate them to 256kHz before sending them to the user how is the >> > 256kHz >> > and the desired interpolation factor of 16 taken into account in the RRC >> > filter >> > in the generic modulator block. >> >> I don't understand this Q. The answer is probably, you'll need an extra >> interpolation block, depending on how your FG looks like. >> >> > I've read the gnuradio pfb page but I think I'm missing something >> > important >> > here. >> >> Just to be clear, you do know what an FIR does and how filter taps are >> defined? Or is this the information you're lacking? >> >> MB >> >> -- >> Karlsruhe Institute of Technology (KIT) >> Communications Engineering Lab (CEL) >> >> Dipl.-Ing. Martin Braun >> Research Associate >> >> Kaiserstraße 12 >> Building 05.01 >> 76131 Karlsruhe >> >> Phone: +49 721 608-43790 >> Fax: +49 721 608-46071 >> www.cel.kit.edu >> >> KIT -- University of the State of Baden-Württemberg and >> National Laboratory of the Helmholtz Association >> >> ___ >> 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 > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem writing custom null sync block
On Fri, Feb 22, 2013 at 09:09:19AM -0500, Tom Rondeau wrote: > > > > class file_writer(gr.sync_block): > > ## CTOR > > # > > def __init__(self, filename, vec_size): > > gr.sync_block.__init__( > > self, > > "file name block", > > in_sig = [np.dtype((np.float32, vec_size))], > > out_sig = None > > ) > > > > self._fd = open(filename, 'w') > > self._filename = filename > > > > > > def work(self, input_items, output_items): > > in0 = input_items[0] > > > > print "## ", len(in0) > > print in0 > > > > return len(output_items) > > What is the length of output_items? Because you don't have an output > buffer attached to this block, I'd be concerned that len(output_items) > == 0, so you're telling the scheduler that you aren't consuming any > data. Maybe just replace that last line with 'return > len(input_items)'? It's probably 'len(in0)', as len(input_items) would return the number of input ports. 'len(output_items[0])' would probably also work. MB -- Karlsruhe Institute of Technology (KIT) Communications Engineering Lab (CEL) Dipl.-Ing. Martin Braun Research Associate Kaiserstraße 12 Building 05.01 76131 Karlsruhe Phone: +49 721 608-43790 Fax: +49 721 608-46071 www.cel.kit.edu KIT -- University of the State of Baden-Württemberg and National Laboratory of the Helmholtz Association pgplM2AJCzzNL.pgp Description: PGP signature ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How can I patch UCSBJello files to my existing gnuradio version?
On Thu, Feb 21, 2013 at 4:34 PM, Nazmul Islam wrote: > Hello, > > I am trying to patch UCSBJello files to my (already installed) gnuradio > version. I installed the latest version of gnuradio a couple of days ago > using the build-gnuradio script. > > The UCSBJello project page in CGRAN (https://cgran.org/wiki/UCSBJello) tells > to download the tarball, patch the files and then run the build gnuradio > command. Since, I have gnuradio running in my laptop already, how can I > patch the UCSB Jello files to my existing gnuradio version? I can download > each file of UCSB Jello one-by-one and see if that works. However, that will > take a long time and I wonder if there is any shortcut. > > I am sorry if this sounds a very novice question. Any feedback will be very > appreciated. > > Thanks, > > Nazmul Nazmul, I don't think there's really a short-cut. I'm not sure exactly what you mean by downloading each file, but then again, I'm not familiar with that UCSB project. I would just download the project, extract it, then try to build by hand and see where the compiler tells you there are problems. If this was written against another version of GNU Radio, there are probably going to be some API changes between the versions that affect you. Just work through these until the compiler is happy. Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem writing custom null sync block
Hi, you're right. Using "return len(in0)" solve my problem. Thanks -- View this message in context: http://gnuradio.4.n7.nabble.com/Problem-writing-custom-null-sync-block-tp39796p39805.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
[Discuss-gnuradio] Detecting a carrier
Hi list.. I'm implementing a FHSS and i have some trouble detecting my carriers, i was triying to use the example usrp_spectrum_sense.py to see how they do it but i'm still in the same trouble, does anyone knows a good reference or have an explanation about how the detect the level of interference o carriers? i can see mi carriers on the uhd_fft without any troubles, but how can i extract that value? and use it for my demod process? Thanks -- Ing. Gonzalo Flores De La Parra Electrónica en Comunicaciones Universidad Autónoma Metropolitana ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] How to automaticly segment span when exceeds USRP limit
Hi everyone, I need to implement a mechanism that splits the span when is bigger than the USRP limit. While I was looking for an example I found "usrp_spectrum_sense.py". This script is old, so I want to know if there is an updated way of spliting the span, or if I can rely in this example. Juan Daniel Fernandez M Este documento puede contener información privilegiada o confidencial. Por tanto, usar esta información y sus anexos para propósitos ajenos a los de la Universidad Icesi, divulgarla a personas a las cuales no se encuentre destinado este correo o reproducirla total o parcialmente, se encuentra prohibido en virtud de la legislación vigente. La universidad no asumirá responsabilidad sobre información, opiniones o criterios contenidos en este correo que no estén directamente relacionados con la Icesi. Si usted no es el destinatario autorizado o por error recibe este mensaje, por favor informe al remitente y posteriormente bórrelo de su sistema sin conservar copia del mismo. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Out of the loop
For anyone expecting answers from me about build-gnuradio and other of my apps over the next few days, I'll be out of the loop. My father is gravely ill and I'm busy making arrangements. -- 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] Out of the loop
Marcus, God bless you and your Family! Sincerely, Martin On Fri, Feb 22, 2013 at 11:06 AM, Marcus D. Leech wrote: > For anyone expecting answers from me about build-gnuradio and other of my > apps over the next few days, I'll be out of the loop. > > My father is gravely ill and I'm busy making arrangements. > > -- > 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
[Discuss-gnuradio] usrp_spectrum_sense.py newer version
Hi everyone, There is a new version of usrp_spectrum_sense.py that works with UHD instead of USRP? Thanks for your attention :) Este documento puede contener información privilegiada o confidencial. Por tanto, usar esta información y sus anexos para propósitos ajenos a los de la Universidad Icesi, divulgarla a personas a las cuales no se encuentre destinado este correo o reproducirla total o parcialmente, se encuentra prohibido en virtud de la legislación vigente. La universidad no asumirá responsabilidad sobre información, opiniones o criterios contenidos en este correo que no estén directamente relacionados con la Icesi. Si usted no es el destinatario autorizado o por error recibe este mensaje, por favor informe al remitente y posteriormente bórrelo de su sistema sin conservar copia del mismo. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Can I add timesamples to tx samples
Maybe my last replay is ambiguous.In metadata,the the time value of rx_sample tags was get by the command "time.time()".Does it mean that the actual time recorded in tags refer to when the sample goes through AD in USRP with the clock in USRP? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] What is IF data header?
Hi, I found the following notes in file metadata.hpp in UHD: /*! * RX metadata structure for describing sent IF data. * Includes time specification, fragmentation flags, burst flags, and error codes. * The receive routines will convert IF data headers into metadata. */ Are the IF data header ethernet packet header?Or anything else? Thanks. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
