On Tue, Aug 03, 2010 at 02:02:28PM -0700, Eric Blossom wrote:
> All block factories should always use gnuradio::get_initial_sptr instead
> of instantiating the shared pointer directly. For blocks that derive
> from gr_block, the old way works OK, but when applied to blocks that
> derive from gr_hi
hi all:
I recently run the test_usrp_standard_tx/rx.cc to do some test.and after
I run the test_usrp_standard_tx.cc, I got the follow information:
which:0
interp: 64
rf_freq: 2.5e+09
amp: 3.00
nsamples: 3.2e+07
Subdevice name is Flex 2400 Tx
Subdevice freq range: (2.3e+
That is an awesome amount of LO suppression in an SSB mixer based system
(I mean the power 1/33-th of the LO). A more interesting number
given this level of LO suppression would be the introduction of a tone
(say) above the LO at LO+F and to see what the power is at LO-F (the image).
Bob
The SECOND ORDER Costas loop produces foptr(n) and poptr(n) which is the
frequency and phase estimate for the carrier.
sin(poptr(n)) is the estimated carrier.
If S(n)*sin(poptr(n) is the spreading code modulating the estimated
carrier, then
S(n)*P(n) * complex_conjugate(S(n)*sin(poptr(n)) s
I tested the usrp2 using uhd_usrp_probe, why is there a warning about unknown
dboard-id or dboard-id combination and Unknown value for RX Subdev and TX
Subdev (antenna?)?is there some miss when I assembled the device?or it's needed
to configure through software?
[r...@fedora12 host]# /usr/loca
On 03.08.2010 23:39, Marc Epard wrote:
>> did anybody manage to get this combination working together?
> Yes, after updating the EEPROM (using the USRP2 firmware) and moving the
> resister, this combination is working fine for us.
>
> OS: Ubuntu 10.04
> GNU Radio: 3.0.3
> FPGA: u2_rev3-2010060
Hi all,
The gnuradio git-source (and also the current 3.3.0 release)
is not compatible with a current GCC 4.5.0 compiler.
I changed the source to make it work, omitting the "usrp2::" prefix in 3 cases.
The diff patch to the current trunk is attached to this mail.
Maybe the developers understand
Hi,
Thank you for your answer. However I am not sure to understand how you changed
your ant-alias filter because this is something that is implemented in the USRP
FPGA isn't it ?
As I said when monitoring the baseband IQ signal produced by the modulator
beofre going to USRP, I don't see these
Hi list,
if anyone has an idea about the gr-trellis module, perhaps you can help
me: It seems the trellis_viterbi*-blocks are only suitable for
packetized data (with 'K' symbols). Is there a way to use them in a
streaming fashion, e.g. like gr_ccsds_decode_fb?
Thanks,
MB
--
Karlsruhe Institute
>
> Moeller
>
>
>
Moeller:
You're familiar with:
http://gnuradio.org/doc/doxygen/index.html
And:
http://gnuradio.org/doc/doxygen/modules.html
The Gnu Radio developers are fond of Doxygen as well...
--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www
On Aug 3, 2010, at 8:42 PM, Ashish Bansal wrote:
> I am using USRP2. The newer version of GNU 3.3 contains timestamp code.
> 1. What do you exactly mean by timestamp. Does it mean it will output the 64
> bit timer value with each sample. What is the command on the host side to see
> these time
line 990: g++: command not found
make[4]: *** [_howto_la-howto.lo] Error 1
make[4]: Leaving directory `/home/mahboob/Desktop/myblocks/src/lib'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/mahboob/Desktop/myblocks/src/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directo
Hello MB,
I implemented a viterbi application and I realized this problem somehow
identical to the ofdm-streaming block for grc. I took packet_sink that
waits until enough samples have arrived. These packets can be used as
packet in the rest of your code. It's not that much work.
Tobias
A
Thanks for your reply, Josh. I do not need qt for now. Could you please tell
me how to disable it in configure, build and install?
Thanks,
Brook
Josh Blum-2 wrote:
>
> Unless you had a specific use in mind for the qt stuff, you probably
> wont need it. I would just disable it in the configure
Oh sorry, thanks for the hint.
Apparently I only visited those source files without doxygen comments.
Anyway, instead of the long GPL legal advices, I'm missing
at least a tiny little comment on top about the meaning of a certain
source file. For that I'm using the \brief doxygen-tag after \file
Hi,
I'm using my own large Matlab toolbox for signal analysis, searching for
signals below noise floor. All is compatible with Octave.
It would be too much effort to port all that stuff to Python, so I want to keep
my working environment.
However, it would be interesting to achieve a coupling wi
Hi all,
Now I try to make full-duplex program on one USRP1 and 2 daughterboards.
(daughterboard is RFX400)
I tested benchmark_tx/rx.py(in example/digital).
For example, I use these command.
--
TX-PC $ sudo python benchmark_tx.py -f 420M -T A
RX-PC $ sudo python benchmark_rx.py -f 420M -R B
--
Bu
On 09.04.2008 18:08, Eric Blossom wrote:
>
> I have no interest in supporting an interface to MATLAB, or any other
> proprietary software for that matter. I'd be much more interested in
> working with Octave, or better yet, working up an excellent
Why making a difference? Most code is compatible
Mr ninja,
The dbsrx is not yet supported under UHD. That is why dboard id 0x0002
is not recognized. Our daughterboard engineer is working on it this very
day; though I cannot make promises as to its release.
Regardless, if you intend to use the dbsrx with a usrp2, it will require
the clock m
Is my impression right, that the dboard id 2 is for the original dbsrx variant
and the dboard id 13 ist for the usrp2 patched variant?
I was wondering if the programming was successful or not.
The modification instructions have no comment about this.
With the id 13 now it's working with the ursp2
On Wed, Aug 04, 2010 at 05:08:44PM +0800, intermilan wrote:
>
> hi all:
>I recently run the test_usrp_standard_tx/rx.cc to do some test.and
> after I run the test_usrp_standard_tx.cc, I got the follow information:
> which:0
> interp: 64
> rf_freq: 2.5e+09
> amp: 3.00
>
On Wed, Aug 04, 2010 at 02:05:18PM +0200, Moeller wrote:
>
> Btw, the current git sources of gnuradio are defective too
> with the current gcc 4.5.0 compiler. I had to change the sources.
> I will provide a patch for that later.
>
> Moeller
Looking forward to your patch. Basing it on the maint
On Wed, Aug 04, 2010 at 02:46:21PM +0200, Moeller wrote:
> Hi all,
>
> The gnuradio git-source (and also the current 3.3.0 release)
> is not compatible with a current GCC 4.5.0 compiler.
>
> I changed the source to make it work, omitting the "usrp2::" prefix in 3
> cases.
> The diff patch to t
On Wed, Aug 04, 2010 at 05:35:01PM +0200, Moeller wrote:
> Oh sorry, thanks for the hint.
> Apparently I only visited those source files without doxygen comments.
FWIW, the doxygen comments are in the .h files
Eric
___
Discuss-gnuradio mailing list
Di
On Wed, Aug 04, 2010 at 06:16:44PM +0200, Moeller wrote:
> On 09.04.2008 18:08, Eric Blossom wrote:
> >
> > I have no interest in supporting an interface to MATLAB, or any other
> > proprietary software for that matter. I'd be much more interested in
> > working with Octave, or better yet, workin
I got it. Everything works fine. Thanks, Josh.
Brook
Josh Blum-2 wrote:
>
> Unless you had a specific use in mind for the qt stuff, you probably
> wont need it. I would just disable it in the configure, build, install.
>
> -JOsh
>
> On 08/03/2010 02:15 PM, Brook Lin wrote:
>>
>> Hi All,
>>
>
On 04.08.2010 19:35, Eric Blossom wrote:
>> Why making a difference? Most code is compatible between Octave and Matlab.
>> Even Matlab C++ MEX functions compile very well in Octave.
>> The Octave scripts in gnuradio are not working in Matlab, because they use
>> Octave-specials (comments as ## ins
Hello,
I'm working now with peak_detector block and find out that some functions
don't really work.
I've used the following 2 blocks:
- Peak Detector (gr_peak_detector): the parameter "look ahead" seems have no
function. I gave "look ahead" many values but the peak value did not change.
I've se
On 08/04/2010 09:41 AM, Moeller wrote:
Is my impression right, that the dboard id 2 is for the original dbsrx variant
and the dboard id 13 ist for the usrp2 patched variant?
Yes
I was wondering if the programming was successful or not.
The modification instructions have no comment about th
Hi Josh,
Thanks for the info.
I just understand the different of UHD based and USRP2-gnuradio, so tried using
non-uhd firmware and fpga (txrx_raw_eth_20100608.bin, u2_rev3-20100603.bin) on
sd card, and run usrp2_fft.py, it works as gui is shown up. But I still see
0x002 displayed there (in bo
Hey Guys,
I got this error when I tried to run grc:
jaco...@godfather-desktop:~/gnuradio-3.3.0$ grc
The program 'grc' can be found in the following packages:
* gnuradio-companion
* grc
Try: sudo apt-get install
However, when I ran ./configure it states that it will make grc. I don't
know ho
we had to rename the executable for some reason
try to run gnuradio-companion
-Josh
On 08/04/2010 12:51 PM, sirjanselot wrote:
Hey Guys,
I got this error when I tried to run grc:
jaco...@godfather-desktop:~/gnuradio-3.3.0$ grc
The program 'grc' can be found in the following packages:
* gn
Hi Jan, for my Ubuntu system I used this series of commands:
./bootstrap
./configure
./make
./make check
sudo make install
--
my problems were all in finding the missing modules that the
configure spit out as not compiled. Some of them are un-necessary,
others I don't know.
I foun
Yup this works.
That was pretty confusing.
Jan
Josh Blum-2 wrote:
>
> we had to rename the executable for some reason
>
> try to run gnuradio-companion
>
> -Josh
>
> On 08/04/2010 12:51 PM, sirjanselot wrote:
>>
>> Hey Guys,
>>
>> I got this error when I tried to run grc:
>>
>> jaco...@g
Hi,
I just entered into the world of GNU Radio. I bought an USRP + WBX +
LP0410 (400MHz - 1GHz). I managed to install GNU Radio (v. 3.2.2) on a Windows
XP SP3 (with MinGW, msys, numpy, wxpython and others), but what to do from now
on? What I want to do is: I made some modules (PIC microco
On Wed, Aug 4, 2010 at 1:47 PM, Florian Eugen wrote:
> I just entered into the world of GNU Radio. I bought an USRP + WBX +
> LP0410 (400MHz - 1GHz). I managed to install GNU Radio (v. 3.2.2) on a
> Windows XP SP3
Florian,
Welcome. Unfortunately, your next step will be to upgrade to GNU
R
Hi All,
The free USRP1 has suddenly decided to stop communicating. We suspect (from the
output)
that it might be an USB problem?
It runs for about 30 - 60 secs and then freezes. The led on the motherboard is
still blinking though.
We've tried to plug into other USB ports and using different cab
On Wed, Aug 4, 2010 at 3:30 PM, Patrik Tast wrote:
> Hi All,
>
> The free USRP1 has suddenly decided to stop communicating. We suspect (from
> the output)
> that it might be an USB problem?
Very likely.
> It runs for about 30 - 60 secs and then freezes. The led on the motherboard
> is still blin
From: tianxia...@hotmail.com
To: e...@comsec.com
Subject: RE: [Discuss-gnuradio] doubt about the tune()
Date: Thu, 5 Aug 2010 09:10:50 +0800
Thank you for the answer.then I have another quertion.why the value is
4M? why not other values like 3M or 5M?and can you tell me where is
2010/8/2 shanki :
> thanks Thomas,
> in order to test these two calls, i write some test codes: i put a rxpath
> and a txpath in one topblock, my daughterboard is RFX2400, and i want to
> perform receiving while transmiting.
> Firstly, i used set_auto_tr(True), but i did't receive anything
Hi all !
I want to make a slider circling on a frequency band automatically.
This is the code of original slider, a very simple slider generated by grc.
class top_block(grc_wxgui.top_block_gui):
def __init__(self):
grc_wxgui.top_block_gui.__init__(self, title="Top Block
Thanks for the help, Matt. I never actually knew what DC offset was until
now ;) Learning as I go!
>From what I understand, the USRP2 scales between -1.0 and 1.0. I am trying
to boost my transmit power well over the power of the DC offset. I think
that if I increase the gain, the DC offset is a
Hi Jason,
thank you for the reply, I updated the GNU Radio to version 3.3.0, but there
is not working. If I want to start a script by double clicking the cmd line
window is opened and closed and nothing happens. The USB driver is installed,
everything seems to be OK but it's not.
Florian.
Hello,
Can one USRP connected with multiple PCs, each of PC runs a GNU Radio, so as to
formulate a distributed system?
And on the other side, can one PC running GNU Radio be connected with multiple
USRP?
Thanks
Zhen
___
Discuss-gnuradio mai
44 matches
Mail list logo
