[Discuss-gnuradio] Synchronizing data transmission and reception

2013-10-14 Thread kt7
Hello Everyone, I am transmitting data from one PC (with SDR) to another PC (with another SDR). The data is a IQ stream of 1s and 0s which will be read from a file and modulated(QAM, QPSK or any other). The data will be received at the other PC, demodulated and dumped into a file for further an

[Discuss-gnuradio] i got warning message

2013-10-14 Thread Maheshkumar Pandit
hello !all i use gnuradio 3.7.2 but i face sucha message when open gnuradio-companion like this mahesh@HP:~$ gnuradio-companion Warning: Block key "blocks_ctrlport_monitor_performance" not found when loading category tree. Warning: Block key "blocks_ctrlport_monitor_performance" not found when

Re: [Discuss-gnuradio] why the code in gnuradio in 3.6 cannot work in 3.7?

2013-10-14 Thread Martin Braun (CEL)
On Fri, Oct 11, 2013 at 10:47:27PM -0700, Yingjie Chen wrote: > Thanks for your reply, Martin. I have read the website about the change > before. > But still nothing change when I run benchmark example in terminal, even though > I delete some original code in C++ block(for test). That means my add

[Discuss-gnuradio] uninstall error

2013-10-14 Thread Nemanja Savic
Hello guys, every time I want to install new version of gnuradio i do uninstall, but there is always the same error: . . . -- Uninstalling "/usr/local/include/volk/volk_config_fixed.h" -- Uninstalling "/usr/local/include/volk/volk_typedefs.h" -- Uninstalling "/usr/local/lib64/libvolk.so.0.0.0" --

Re: [Discuss-gnuradio] uninstall error

2013-10-14 Thread Ralph A. Schmid, dk5ras
Did you try the uninstall with su/sudo? Ralph. From: discuss-gnuradio-bounces+ralph=schmid@gnu.org [mailto:discuss-gnuradio-bounces+ralph=schmid@gnu.org] On Behalf Of Nemanja Savic Sent: Monday, October 14, 2013 10:57 AM To: GNURadio Discussion List Subject: [Discuss-gnuradio]

Re: [Discuss-gnuradio] uninstall error

2013-10-14 Thread Nemanja Savic
Yes, for sure. The pattern is more or less repeatable. For example, modul wavelet, has 4 files that needs to be deleted: /usr/local/lib64/libgnuradio-wavelet-3.7.1git.so.0.0.0 /usr/local/lib64/libgnuradio-wavelet-3.7.1git.so /usr/local/lib64/libgnuradio-wavelet.so /usr/local/lib64/libgnuradio-wave

[Discuss-gnuradio] missing gruel module when installing current

2013-10-14 Thread Nemanja Savic
After building and installing current version on my RHEL6 system, I was unable to compile my module and the following error appeared: -- checking for module 'gruel' -- package 'gruel' not found -- Could NOT find GRUEL (missing: GRUEL_INCLUDE_DIRS) -- checking for module 'gnuradio-core' -- pa

Re: [Discuss-gnuradio] missing gruel module when installing current

2013-10-14 Thread Ethan Trewhitt
Nemanja, Gruel and GNURADIO_CORE are both elements of GnuRadio 3.6 that went away in 3.7. If you want to use your module as-is, you'd need to revert back to 3.6, otherwise you'll need to update your module to work with 3.7. There's a guide here: http://gnuradio.org/redmine/projects/gnuradio/wiki/

Re: [Discuss-gnuradio] missing gruel module when installing current

2013-10-14 Thread Nemanja Savic
Hi, I must check in order to be 100 % sure, but complete module was written for 3.7.0 that I have on other machine. I'll post when I check. On Mon, Oct 14, 2013 at 3:42 PM, Ethan Trewhitt wrote: > Nemanja, > > Gruel and GNURADIO_CORE are both elements of GnuRadio 3.6 that went away > in 3.7. If

[Discuss-gnuradio] FOSDEM '14 - Call for Participation

2013-10-14 Thread Martin Braun (CEL)
Dear friends and colleagues, next year's FOSDEM (the free and open source developer's meeting in Brussels, Europe) will feature a new track on Software Defined Radio. Therefore, we invite developers and users from the free software radio community and to join us for this track and present your t

[Discuss-gnuradio] R: R: Re: R: R: Re: around empty subcarrier in 802.11n implementation

2013-10-14 Thread xe...@libero.it
Hi guys, just for letting you know. No offset correction is needed. The problem was elsewhere in my implementation of 802.11. It was how I was calling the ifft function in the transmitter side. By putting the correct parameters, I obtained a perfect spectrum. Regards Francesca Messa

Re: [Discuss-gnuradio] R: R: Re: R: R: Re: around empty subcarrier in 802.11n implementation

2013-10-14 Thread Matt Ettus
Thanks for the update! I know that getting the exact right bins in the right place can be hard since every FFT inplementation is slightly different. Matt On Mon, Oct 14, 2013 at 8:43 AM, xe...@libero.it wrote: > Hi guys, > > just for letting you know. No offset correction is needed. The probl

Re: [Discuss-gnuradio] Async Packet Transmission with Unmodulated Carrier

2013-10-14 Thread Michael Berman
What I am attempting to do is build a transmitter and receiver unit for what the BBC is using for sending broadcast information in association with their AM broadcasts. This is called Amplitude Modulation System Signalling (AMSS). I would like to be a bit more generic than the BBC standards (allo

Re: [Discuss-gnuradio] GRC problems

2013-10-14 Thread Sebastian Koslowski
Hi Johannes, try this for #2: https://github.com/skoslowski/gnuradio/commit/a79d235053df5ec697f393a21d1d37ea2967b9ed Sebastian On 10/12/2013 07:17 PM, Johannes Demel wrote: > Hi list, > > I discovered 2 problems with GRC recently. > > 1. I have a custom block with a message port (with a fixed

[Discuss-gnuradio] Idea for gr-osmosdr

2013-10-14 Thread Marcus D. Leech
In developing simple_ra, I've run up against the issue that GRC doesn't really allow run-time reconfiguration of flow-graphs, but I have an emerging need to support slightly-different hardware configurations, involving either one or two input devices. This is both for interferometer support,

Re: [Discuss-gnuradio] Idea for gr-osmosdr

2013-10-14 Thread Ethan Trewhitt
Marcus, What about the "selector" and "valve" blocks in GRC? You could build your single top_block in GRC then instantiate and call it within an external Python script that switches the selector/valves based on the radio choice you want to make. Then you have a top_block that is still maintainable