On Thu, Aug 23, 2012 at 5:54 PM, Samuel Ibarra wrote:
> Hello,
>
> Thank you for your help Frederick. The problem that I am having is that I
> don't really understand how I can get the read_gpio() value into my python
> code. Once I get the value to my python code, then I will be able to create
>
On Tue, Aug 21, 2012 at 3:45 PM, Frederick Lee wrote:
>
>
> On Tue, Aug 21, 2012 at 2:53 PM, Frederick Lee wrote:
>
>>
>>> Frederick,
>>>
>>> You will have to recompile and reinstall, but not everything. If you
>>> are modifying a singl
On Tue, Aug 21, 2012 at 2:53 PM, Frederick Lee wrote:
>
>> Frederick,
>>
>> You will have to recompile and reinstall, but not everything. If you
>> are modifying a single block, you can just rebuild from that
>> components directory. You want to do the entire
HI,
I wanted to modify a block and use it. Will I have to recompile everything
or can I just use it without compiling?
I'm still new to Linux, so if I need to compile can someone provide a link
to some instructions to do so?
Thanks,
Frederick
___
Discu
Hi,
I was looking at the gri_control_loop.cc file and notices the
set_frequency() function seemed a little odd. Here's what it looked like.
void
gri_control_loop::set_frequency(float freq)
{
if(freq > d_max_freq)
d_freq = d_min_freq;
else if(freq < d_min_freq)
d_freq = d_max_freq;
e
Swig stuff are python bindings to C or C++ code. So in your example
pfb_clock_sync_ccf() has been coded in C++, and
_digital_swig.pfb_clock_sync_ccf() is the generated python wrapper to
access the C++ pfb_clock_sync_ccf() from a python script.
> The C++ code is in include/ and lib/, swig bindings
Hi GNURadio community,
I'm looking into how the modulation and demodulation blocks work.
Specifically the BPSK mod and demod blocks. Here is a list of the files I
looked through and the location:
generic_mod_demod.py - */gr-digital/python
modulation_utils.py - */gr-digital/python
bpsk.py - */gr-d
>
> Frederick,
>
> all kinds of stuff can go wrong.
>
> When you say you see 'nothing' on the FFT sink, do you mean you see only
> noise, or literally nothing?
>
> Here's a typical ist of things I do when debugging such a link:
>
> 1) Use a spectral analyzer to see if the transmitter is actually
>
On Thu, Jul 26, 2012 at 12:06 PM, Ben Hilburn wrote:
> You said you replaced the channel model block with a USRP sink and source?
> Are you trying to TX / RX using a loopback? If so, remember to use
> attenuators so that you don't blow out your RX chain.
When I said "replaced the channel model b
On Thu, Jul 26, 2012 at 2:08 PM, Daniel Labarowski
wrote:
> Sorry for the quick response, but I tried opening GRC using the terminal and
> got the error below. Any ideas?
>
>> Error reading file
>> '/usr/local/share/gnuradio/grc/blocks/gr_tagged_file_sink.xml': failed to
>> load external entit
Hi,
I recently updated my GNU Radio using the build-gnuraido script. Now
when I start gnuradio-companion, I get a warning saying:
Warning: Block key "gr_message_burst_source" not found when loading
category tree.
linux; GNU C++ version 4.6.3 20120306 (Red Hat 4.6.3-2); Boost_104700;
UHD_003.004.0
I figured out why the low pass filter was making the square wave look
like a sine wave. The square was represented by a Fourier series. In
other words, it was made up of many sine waves with different
frequencies. The Fourier Series for a square wave is: 4k/pi(sinx +
1/3*sin3x + 1/5*sin5x + ... ) W
> Perhaps you are seeing a small frequency offset between RX and TX. I
> recommend experimenting a little more in simulation:
>
> * What happens you pass the same square wave through that low pass
> filter you mentioned. Whats it look like?
>
When I pass the square wave through the low pass filte
13 matches
Mail list logo
