Re: [Discuss-gnuradio] Radio frequency range description list?

Hi, In the absence of any existing solution I am interested in trying to put something together, possibly as a GitHub project? Although a Wiki could be used, my focus is on a solution that is machine parsable, so any application could make use of it. I am not sure the best file format to use, bu

[Discuss-gnuradio] Data flow end up?

Hi, I have build up a transmitter which transmits frequencies to radio. I can swtich OFF and ON the transmitter. When flow graph runs the data is transmitted in the air by usrp and RF400 daughter board. The audio is a wav file saved on host or by direct input from mic. If i switched off the tran

Re: [Discuss-gnuradio] (no subject)

On Mon, Apr 1, 2013 at 2:46 PM, vamshi krishna dodla wrote: > I have some questions regarding the coastas loop implemented, does it also > consider the snr estimate too? like a Maximum Likelihood loop(tanh* snr). Hi Vamshi, No, the Costas loop does not account for SNR. This is among a series of

Re: [Discuss-gnuradio] SWIG issue with next

On Mon, Apr 1, 2013 at 5:35 PM, Peter Horvath wrote: > Hi, > > the most up-to-date 'next' fails to compile on my Ubuntu 12.10 (32 bit). Is > this the same issue as > http://gnuradio.org/redmine/issues/529 ? Well, as I've said before, during these (hopefully) last few days of us working to get to

Re: [Discuss-gnuradio] pktno ??!!

Hi, I put the following code in packet_utils.py n=0 while len(pkt)!= "": print "make_packet: len(pkt) =",len(payload) # n=n+1 print "pktno",n n=n+1 what it did is ,it kept incrementing until i stop it.Although i connect the usrp to the computer or not,it keeps incrementing.

[Discuss-gnuradio] SWIG issue with next

Hi, the most up-to-date 'next' fails to compile on my Ubuntu 12.10 (32 bit). Is this the same issue as http://gnuradio.org/redmine/issues/529 ? (gr_ctrlport has been disabled due to an unfortunate issue with GCC 4.7 and the pre-packaged ICE in Ubuntu; otherwise the same config that I use for

Re: [Discuss-gnuradio] Changing to "next" fails?

Oh, by the way, at 72 % building fails. Some unspecified error 2 or smth like that, no further information. Again I am in Windows now, can give the exact message when I boot Linux again, but I am afraid it said nothing more. Ralph. ___ Discuss-gnurad

Re: [Discuss-gnuradio] pktno ??!!

i get what you meant now..will give a try and let you know about it.. thanks. - Manjusha -- View this message in context: http://gnuradio.4.n7.nabble.com/pktno-tp40416p40480.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Dis

Re: [Discuss-gnuradio] Changing to "next" fails?

> I meant that "trying to build next" after a checkout was bit vague given that > there are 5 steps to be executed after a checkout. Well, what are those steps to the book? sudo make uninstall, git checkout xxx, cd xxx, cmake .., make. Did I miss something? AS I have mentioned, until now it did wo

Re: [Discuss-gnuradio] pktno ??!!

Hi Manu, Thanks for your reply data = file.read(pkt_size) means that we asking it to read a file name called pkt_size right??Is there any file with that name? Please correct me if i am wrong in any sense. I don't see any pktno defined anywhere in gnuradio files apart from benchmark_tx.py. Than

[Discuss-gnuradio] (no subject)

I have some questions regarding the coastas loop implemented, does it also consider the snr estimate too? like a Maximum Likelihood loop(tanh* snr). Also can you suggest me any interpolator for timing recovery and also polyphase bandedge filters implementation. This would be really helpful to me.As

Re: [Discuss-gnuradio] : RTL-SDR: Failed to open rtlsdr device

You need to use this line: sudo make install-udev-rules look at this link: http://sdr.osmocom.org/trac/wiki/rtl-sdr Karl Y Petrow Maritime Information Systems, Inc. http://www.maritimeinfosystems.com kpet...@maritimeinfosystems.com

[Discuss-gnuradio] Shifted samples from USRP1

Hi, I'm using the USRP1 and the UHD driver together with gnuradio. Often, especially at high sample rates (8MHz), the spectrum observed in the fftsink becomes distorted after a while. It becomes almost mirrored. Typically it happens after a couple of "overruns". I have tried finding out the reason

Re: [Discuss-gnuradio] error building next on osx

On Mon, Apr 1, 2013 at 1:26 PM, Michael Dickens wrote: > This is 007b401cf14fcfc067d11f5e4d2ca1730407803b, which according to my > git-foo is the latest commit to (aka HEAD of) this branch. Fixing it "right > now" is not a big deal IMHO: I just keep the gnuradio-next branch up to date > and if

Re: [Discuss-gnuradio] terminating benckmark_rx.py after TIMEOUT

If you are running ofdm benchmark_rx, then the TIMEOUT comes from digital_ofdm_sampler.cc. I think the timeout occurs, if the sampler does not get another preamble even after 1000 (this is the value set currently) symbols, then it declares TIMEOUT and enters STATE_PREAMBLE. thanks and regards --A

Re: [Discuss-gnuradio] error building next on osx

This is 007b401cf14fcfc067d11f5e4d2ca1730407803b, which according to my git-foo is the latest commit to (aka HEAD of) this branch. Fixing it "right now" is not a big deal IMHO: I just keep the gnuradio-next branch up to date and if it works that's great and if it does not then (as the descripti

Re: [Discuss-gnuradio] real time airplane data

Hi Bill, I hope you're doing well since your visit to the office. I've recently done some development on similar lines to demonstrate a multi-function transceiver (COM/NAV, ILS, GPS, ADS-B, etc.). I originally had the idea to integrate such a device, probably based on an embedded-series USRP, in

Re: [Discuss-gnuradio] error building next on osx

On Mon, Apr 1, 2013 at 12:44 PM, Michael Dickens wrote: > Carles points out that the next branch is failing on OSX (via the > "gnuradio-next" port). Here's the error log. Ideas? - MLD Is this the current HEAD on the next branch? As we've said, we're going through a lot of major changes on next

[Discuss-gnuradio] error building next on osx

Carles points out that the next branch is failing on OSX (via the "gnuradio-next" port). Here's the error log. Ideas? - MLD [ 6%] Building CXX object gnuradio-runtime/lib/CMakeFiles/gnuradio-runtime.dir/gr_basic_block.cc.o cd /opt/local/var/macports/build/_opt_MacPorts_trunk_dports_science_g

Re: [Discuss-gnuradio] macport switching between gnuradio and gnuradio-devel ports with installed gr-osmosdr?

Hi Michael, thank you very much for your great job with the gnuradio* and gr-osmosdr stuff in Macports, even keeping us updated about the progress! Just a comment: I've found that the gnuradio-next @3.7.0_20130326_0+python27+uhd build fails in my system. It didn't happen with previous versions. It

Re: [Discuss-gnuradio] macport switching between gnuradio and gnuradio-devel ports with installed gr-osmosdr?

This is taking longer than I expected, because I have to modify something other than the Portfile in order to get the functionality I need. I have to run that change past "the MacPorts powers that be"; they are usually pretty responsive, usually within a day or so. I'll post back when the chan

[Discuss-gnuradio] real time airplane data

I am a former Navy Test pilot, ham, and experimental airplane enthusiast. We found GNUradio last year as part of a course I teach on airborne software and Avionics.  We have access to packet streams, RS-232 and ARINC-429 in two experimental airplanes.  The data includes all the parameters sent t

Re: [Discuss-gnuradio] On tunnel.py

Hi Alex, you raise a lot of valid points, but I just have to add something for the record (and yes, I realize that's not what you said): Students are *not* to be blamed here. First, I know a lot of students who are doing brilliant work on GNU Radio (there's a lot of students at our lab working on

Re: [Discuss-gnuradio] Changing to "next" fails?

On Mon, Apr 1, 2013 at 3:43 PM, Ralph A. Schmid wrote: > >> The code hasn't changed for days and it builds fine so yes, you are >> probably doing something wrong. Without knowing what you do after the >> checkout it's hard to guess what it could be. > > I have done what I have described :) But the

Re: [Discuss-gnuradio] Source block for the funcube pro plus

On 31/03/13 23:29, Alexandru Csete wrote: On Thu, Mar 28, 2013 at 11:41 AM, Volker Schroer wrote: Just for your information: In imitation of the gr-fcd source I set up a gnuradio source for the funcube pro+ ( linux only) . To avoid the crashes depending on libusb I used the hidraw driver. Th

Re: [Discuss-gnuradio] Changing to "next" fails?

> Ralph, > > "git branch next" just moves you over to the next branch but doesn't > pull anything down. If there was an error doing "git pull next", then > just moving to that branch wouldn't have any effect. This seems to be the problem, as usually git checkout xxx did the job. > Also, you men

Re: [Discuss-gnuradio] Source block for the funcube pro plus

Hi Volker, You Wrote: I tested against 3.6.4, gentoo 64 bit. I'm not very familiar with cmake, so perhaps the cmake code may be improved. Can you send me the error message ? I think it was just my set of multiple/semi broken trees of various 3.6.x branches, precog etc that was confusing cmake

[Discuss-gnuradio] More GSoC opportunities

Hopefully these guys get accepted also: http://www.parallella.org/ideas/ See the GNU Radio ideas. As some of you know, I have a similar idea on the GNU Radio page for Xilinx Zynq systems. If both of these projects are accepted into GSoC there should be considerable overlap in the part of the sol

Re: [Discuss-gnuradio] Changing to "next" fails?

> The code hasn't changed for days and it builds fine so yes, you are > probably doing something wrong. Without knowing what you do after the > checkout it's hard to guess what it could be. I have done what I have described :) But the other tip seems to help, git pull origin... > ALex Ralph.

Re: [Discuss-gnuradio] macport switching between gnuradio and gnuradio-devel ports with installed gr-osmosdr?

Hi Mike - You're (all) welcome for the gr-osmosdr port. Seems like it is pretty well used as well as kept up, and so is a good candidate for being in MacPorts. That's a great suggestion! I'm doing a "port selfupdate" right now to get the latest of everything, and when that is done I will fix

Re: [Discuss-gnuradio] Changing to "next" fails?

On Mon, Apr 1, 2013 at 10:11 AM, Ralph A. Schmid, dk5ras wrote: > Hi, > > Maybe a stupid question...am I doing smth. wrong, or has there been some > change? When doing a "git checkout next" and trying to build next, it still > build master. Even completely deleting the gnuradio folder does not hel

[Discuss-gnuradio] Changing to "next" fails?

Hi, Maybe a stupid question...am I doing smth. wrong, or has there been some change? When doing a "git checkout next" and trying to build next, it still build master. Even completely deleting the gnuradio folder does not help. Also I get some error message when doing git checkout next, git branch