Hi all,
I am new to USRP and I started by trying to calibrate the received power in
USRP by giving a known sine signal. I gave a signal of *100.2 MHz at -30 dBm
* to USRP which sampled it at 1MHz then passed it to a 1024 point FFT scope
in Gnu Radio Companion. I saw a level of about* -52 dB at 10
On Tue, Oct 16, 2012 at 6:34 PM, Tom Hendrick wrote:
> Hello,
>
> I have ubuntu 12.04 and GNURadio 3.6.2. I was trying to run some older
> scripts which uses the USRP. These scripts were made with GNURadio
> Companion about 3 years ago, and then I added some extra menu options by
> manually edit
Ok, I suppose the best and fastest way to learn gnuradio is by exploring
simple existing blocks, like adder for example.
I was first thinking about adder and the opened gr_add_cc.h.
I was immediately stuck in the constructor part
gr_add_cc::gr_add_cc (size_t vlen)
: gr_sync_block ("add_cc",
Hm, I see now, and don't get, how you specifu number of inputs, and what
exactly means Vec Length (vlen)
and what could be wrong with implementation like this:
int
gr_add_cc::work (int noutput_items,
gr_vector_const_void_star &input_items,
gr_vector_void_star
On Wed, Oct 17, 2012 at 08:45:21AM -0700, nexy_sm wrote:
> Hm, I see now, and don't get, how you specifu number of inputs, and what
> exactly means Vec Length (vlen)
Read this:
http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsCoreConcepts
> and what could be wrong with implementation l
On Wed, Oct 17, 2012 at 11:13 AM, nexy_sm wrote:
> Ok, I suppose the best and fastest way to learn gnuradio is by exploring
> simple existing blocks, like adder for example.
> I was first thinking about adder and the opened gr_add_cc.h.
>
> I was immediately stuck in the constructor part
>
> gr_ad
On 10/17/2012 05:21 AM, Hemant Saggar wrote:
> Hi all,
>
> I am new to USRP and I started by trying to calibrate the received power in
> USRP by giving a known sine signal. I gave a signal of *100.2 MHz at -30 dBm
> * to USRP which sampled it at 1MHz then passed it to a 1024 point FFT scope
> in
Hello list,
Just shooting out a quick update. I wrote a simple wrapper for pyserial to
provide a serial port block for use with GNU Radio/GRC. The objective here
was to support a legacy command generation program that would typically
output to an external, hardware-based transmitter via RS-232.
Hi Community,
Just tried to write a couple of scripts for the new comers on GNU Radio and
USRP. I have given detailed explanation step by step on how to quickly get
data from USRP by writing your own program , without any knowledge of python
or C++
I have posted them on my blog, here are the links
Hi,
I installed pre-cog following the last section of
https://github.com/buoyboy/pre-cog/wiki/Installation only. I already had
working GNUradio with grextras installed, which I did by simply running the
installation script http://www.sbrac.org/files/build-gnuradio . Now
strangely I see that many b
Ok, thanks for the explanation and link with more information.
Is there any benefit of using for example adder block which calculates
output using input vectors, then using single flat or whatever.
I expect that for calculating for example FFT one usually need packets of
512 or 256, etc samples, a
On Wed, Oct 17, 2012 at 2:21 PM, sumitstop
wrote:
> Hi Community,
> Just tried to write a couple of scripts for the new comers on GNU Radio and
> USRP. I have given detailed explanation step by step on how to quickly get
> data from USRP by writing your own program , without any knowledge of pytho
On 10/17/2012 01:13 PM, Sakib Chowdhury wrote:
> Hi,
>
> I installed pre-cog following the last section of
> https://github.com/buoyboy/pre-cog/wiki/Installation only. I already had
> working GNUradio with grextras installed, which I did by simply running the
> installation script http://www.sbr
Hi Josh,
I noticed that actually all block files (xml) are still there
in /usr/local/share/gnuradio/grc/blocks/ . What GRC is not displaying are
the blocks whose names start with gr_*.xml . I'll try to reinstall.
Thanks.
On Wed, Oct 17, 2012 at 5:17 PM, Josh Blum wrote:
>
>
> On 10/17/2012 01
On Wed, Oct 17, 2012 at 2:30 PM, Sakib Chowdhury wrote:
> I noticed that actually all block files (xml) are still there
> in /usr/local/share/gnuradio/grc/blocks/ . What GRC is not displaying are
> the blocks whose names start with gr_*.xml . I'll try to reinstall.
>
This was a recently fixed bu
Let me know if you're interested...
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Thanks for the appreciation Tom !!
Will keep these basic things posting...
btw whom shall I contact so that these links get included on gnuradio.org
...
--
View this message in context:
http://gnuradio.4.n7.nabble.com/Quick-Dirty-for-Beginners-tp38039p38047.html
Sent from the GnuRadio mail
I have gnuradio version 3.6.2-13-g65ea256f
Q1 : In the directory */usr/local/share/gnuradio/examples/digital/ofdm* I
tried to run ofdm_mod_demod_test.py
but it threw the error * 'module' object has no attribute
'ofdm_bpsk_mapper'*
I tried to locate ofdm_bpsk_mapper but couldn't find it in my syst
Hi John,
Yes, I also checked the examples in your branch. In regards to your
questions.
*1.* BLOCK 2 is processing the data from BLOCK 1, but only when BLOCK 1 has
finished the routine "N times". Let me post a piece of code from BLOCK 1:
int work(
const InputItems &,
const Outpu
Can you send me the files?
-John
On Wed, Oct 17, 2012 at 4:16 PM, Jose Torres Diaz wrote:
> Hi John,
>
> Yes, I also checked the examples in your branch. In regards to your
> questions.
>
> *1.* BLOCK 2 is processing the data from BLOCK 1, but only when BLOCK 1
> has finished the routine "N t
akes the messages from the message queue. However, this implementation is
not useful for me. BLOCK 1 should post a message downstream and then, BLOCK
2 takes the message and work with the packet.
Any suggestion is welcome, thanks a lot for your time,
Regards,
Jose
-- next part
21 matches
Mail list logo
