>> It looks like the only code affected is in gr-filter. I suggest Tom take
>> a second look at the usage of volk_32fc_x2_dot_prod_32fc. Whether or not
>> we take the changeset, it might be good to verify that the following
>> code isnt being bitten by this usage:
>>
>>> ./gr-filter/lib/fir_filter
Isabella,
If you are looking for a LTE modulator/demodulator, I have a project
called openLTE (sourceforge.net/projects/openlte) that accomplishes
much of this. It does not currently support all of the LTE
specifications, but might be enough to get you going.
Regards,
Ben
On Mon, Jul 2, 2012 at
On 07/02/2012 06:34 PM, sibar002 wrote:
>
> Hello,
>
> I would like to be able to control pins 5, 7, 9,... , and 35 on the J401
> component on the N210 (Pins G4, F5, H6, ..., and K6 on the FPGA). From the
> Basic_Tx/Rx daughterbaord schematic, I was able to see that some of these
> pins are not
On Mon, Jul 2, 2012 at 6:34 PM, Josh Blum wrote:
> Hey VOLK enthusiasts,
>
> It looks like in just a few kernels we use num_bytes as the length
> parameter rather than num_points. I think this may have been a source of
> confusion and perhaps a few test failures.
Yes, this has been bugging me, to
On Mon, Jul 02, 2012 at 08:27:01PM -0400, Andrew Davis wrote:
>
> Really cool presentation! Thanks for the info. Now i'm running into
> another problem, I sample at about 4MSPS for a bit and try to capture
> the signal as it passes though my window, but I never seem to get it,
> just a huge mess o
Hello,
I would like to be able to control pins 5, 7, 9,... , and 35 on the J401
component on the N210 (Pins G4, F5, H6, ..., and K6 on the FPGA). From the
Basic_Tx/Rx daughterbaord schematic, I was able to see that some of these
pins are not really used on the daughterboard. I am working on imple
Really cool presentation! Thanks for the info. Now i'm running into
another problem, I sample at about 4MSPS for a bit and try to capture
the signal as it passes though my window, but I never seem to get it,
just a huge mess of noise, aliasing and ghosts.
http://i.imgur.com/w3oBP.jpg as you can se
Hey VOLK enthusiasts,
It looks like in just a few kernels we use num_bytes as the length
parameter rather than num_points. I think this may have been a source of
confusion and perhaps a few test failures.
See, we pass random number of points into these kernels for test. But,
when random numbers o
Hello Josh,
JH> -- Dependency PYGTK_FOUND = TRUE
JH> -- Dependency NUMPY_FOUND = FALSE
JH> -- Disabling gnuradio-companion support.
JH> -- Override with -DENABLE_GRC=ON/OFF
JB> The build environment is just trying to import
JB> numpy. Are you able to run python -c "import
JB> numpy" from the s
Isabella,
I do not believe the OFDM mod block will provide you with what you need, both
DVB-T and LTE follow a highly defined structure that defines pilot symbols and
resource scrambling/user mapping that I doubt the OFDM block can emulate
without significant modification. If this only has to b
On 07/01/2012 05:37 PM, Julio Hector Aguilar Renteria wrote:
> DSP Freq 0 o negative why?
>
I am very unsure as to what you are asking.
Perhaps you will find this information helpful:
http://files.ettus.com/uhd_docs/manual/html/general.html#two-stage-tuning-process
-josh
On 07/02/2012 04:41 AM, Jared Harvey wrote:
> Hello,
>
> I'm having a problem getting GRC to install. It appears it thinks
> numpy is not installed, however synaptic claims it is. Also the log
> files notes
>
> python-numpy is already the newest version.
>
> Yet I also see in the log file
>
>
Hello Nick,
Thanks for your reply, I want to know about the parameters for my bandpass
filter block?
So what parameters should give to my band_pass_filter as follows
high_cut_off=?
low_cut_off=?
sampling_rate should be less than 6.25MHz
transition band=?
Yes I want to use usrp2 source how do I
Hi,
I have to generate DVB-T and LTE signals using gnuradio companion.
I'm in trouble because I don't know how to set some parameters in the OFDM
modulator block.
LTE signal:
transmission bandwith: 5MHz
FFT size: 512
Cyclic prefix length: 128
occupied subcarriers:300
My questions concerning LTE s
Umer,
You have a filter with a sample rate of 1.7GHz. This is obviously
incorrect. Your filter must operate at the baseband rate; in the case of
USRP2 with decimation 16, as you have it set up, the filter will operate at
100Msps/16=6.25Msps. The filter cutoff frequencies must be similarly
relative
I'm not really sure about whether you can get a work function to be called at a
set interval. One thing comes to mind though. I suppose you could make this
block into a data sink that's in parallel with your actual data flow. Then you
can just use the size of each incoming buffer when work() is
I have attached my GRC file with this email. I am getting the following error?
gr_buffer::allocate_buffer: failed to allocate buffer of size 43852 KB
Umer
band_pass.grc
Description: band_pass.grc
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.
17 matches
Mail list logo
