Hi,
I managed to get the board to transmit at the frequency I want by
reverting to the db_xcvr2450 code existing before Changeset 10853
(r10400, r10165) [see http://gnuradio.org/trac/changeset/10853].
--
Posted via http://www.ruby-forum.com/.
___
Di
I would also like to report that when running
>>> � $ usrp_sigggen.py -f 2.45G --const -a 8000
I get a big peak at 2.58GHz when looking at the plug connected to subdev
(0,0) on the spectrum analyzer, and a smaller peak at 2.58Ghz when
looking at (0,1). The mux setting the program automatically
OK I just did a full fresh reinstall of 3.2 (redownloaded from
http://gnuradio.org/trac/wiki/Download
ftp://ftp.gnu.org/gnu/gnuradio/gnuradio-3.2.tar.gz) onto my NetBSD
machine and I still get:
Johnathan Corgan wrote:
> On Mon, Jun 22, 2009 at 14:08, William Sherman
>
Johnathan Corgan wrote:
> Can you elaborate on how you installed 3.2, and whether there was a
> prior installation before that? If so, did you uninstall it first
> before installing 3.2?
Previously I had v3.1.3 installed. This was uninstalled (all packages
removed) before installing v3.2 followi
Eric Blossom wrote:
> On Mon, Jun 22, 2009 at 06:30:26AM +0200, William Sherman wrote:
>> The xcvr transmits at the incorrect frequency. I just looked at it with
>> a wider span of the spectrum analyser. Asking it to transmit at 2.45GHz,
>> it instead transmits signals at 2
The xcvr transmits at the incorrect frequency. I just looked at it with
a wider span of the spectrum analyser. Asking it to transmit at 2.45GHz,
it instead transmits signals at 2.58GHz. What could be causing this?
--
Posted via http://www.ruby-forum.com/.
__
Here is my console output for a transmit program:
The XCVR2450 doesn't transmit.
python rx2_pu_tx.py -f 2.4G
xcvr2450: Setting reg 2 to 30072
xcvr2450: Setting reg 5 to 38225
xcvr2450: Setting reg 5 to 38A25
xcvr2450: Setting reg 6 to 4006
xcvr2450: Setting reg 7 to 627
xcvr2450: Setting reg 8 to
Hi I am using Gnuradio v3.2 and usrp1.
I was using modified examples\digital\transmit_path, receive_path to
send and receive packets on the RFX2400. This was working alright.
I wanted more transmit power (+ adjustable gain) so I exchanged the
RFX2400 boards for XCVR2450 boards. However when I run
William Sherman wrote:
> Ok the problem was I set my decimation too high (256), even though on
> the faq it says I can go [8, 256]. I tried it with 128 and it worked.
Yet I am able to receive packets generated by my own usrp (usrp
transmits and receives its own packet) correctly
Ok the problem was I set my decimation too high (256), even though on
the faq it says I can go [8, 256]. I tried it with 128 and it worked.
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lis
I'm encountering the same problem over where I am, and have come to the
same conclusion.
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Bump
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Hi.
1)
I have modified benchmark_rx.py/receive_path.py to allow it to receive
two channels from two RFX2400 daughterboards (I aim to use the second
channel for sensing).
As suggested by the examples/mailing list, I inserted a deinterleave
block after the source to retrieve streams from each chann
no I don't understand this either.
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Ling Huang wrote:
> set.mux(0x32103210)
Dude, how do you calculate the Mux value you need?
For instance what's the maths behind calculating the mux for two RFX2400
daughterboards?
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailin
Hmm:
I have a working program which has a USRP perform TX & RX on the one
radio, using transmit_path & receive_path. With two USRPs I can do
RTS/CTS and transmit a packet with ACK. My receive_path was not picking
up its own transmit_path's packet transmissions erroneously. This was
even though
and how are you supposed to use these mblocks
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
The more I think about the more I think how impossible it is.
David Tisza wrote:
> And there are more efficient ways to determine where the packet started
> and where it ended in a stream than just appending 0-s at the end, if
> you still want to use the conventional streaming concept of the gnura
David Tisza wrote:
> You could, but how do you define your concept of a packet "had been
> transmitted" ?
This:
> is it when your signal waveform's end is converted into electromagnetic
> wave at the antenna
>
--
Posted via http://www.ruby-forum.com/.
_
Well that certainly makes things trickier.
Thinking through the problem: couldn't you detect when the packet had
been transmitted by inserting a packet of 'voltage 0's' after your real
packet into transmit_path's flowgraph. Then you could poll the msgq in
message_source until the queue is empty
transmit_path as in from gnuradio-examples/transmit_path.py used in
benchmark_tx.py.
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Hi,
My question is:
is there a way in gnuradio to know if transmit_path has finished
transmitting a packet?
I was just reading a thesis by Alice Crohas where she implements a
cognitive radio. Her transmitter uses transmit_path to transmit packets
in Gnuradio. A power detector is used to detect pr
never mind just realized
--
Posted via http://www.ruby-forum.com/.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Hi,
Where did he get this equation from? (What is this equation f?)
> Hi Eric:
>
> I have already read that paper before. As that paper mentions, the USB
> delay
> is according to the equation
>
> f(512, fusb_block_size*fusb_nblock)
> -
> fs*sample_size
Hi.
I am having a similar problem getting two USRPs to run on one computer
on NetBSD. gnuradio can only run one USRP at a time. It can only run
USRP #0 and when I create a usrp source/sink with which=1 it says
"Unable to find USRP #1".
Are you saying more needs to be done than specifying which
I also have been having trouble trying to dynamically change the
parameter of a block.
In this case the amplitude of the sine wave in usrp_siggen.py
(gr.sig_source_f).
I use the set amplitude function of the top_block to change the
amplitude in my main loop. However, observing the spectrum usi
George Nychis wrote:
> On Fri, Apr 17, 2009 at 1:09 AM, William Sherman
> wrote:
>
>> Do I need to building gr-howto-write-a-block-3.1.3 from inside the
>> gnuradio directory instead of just some random directory where it is
>> currently located?
>>
>
> Th
OK I fixed the error in my Makefile which was giving me the make error.
However I have run into another problem. python doesn't pick up the new
block when I try to run a python program.
I use,
from gnuradio import howto
but the new block is not recognised.
Why would this be?
Do I need to buildi
ting. Googling this it appears to be related with where make
tries to locate libraries / directory it makes the library to?
Does anyone know why the make install fails and I can't make a new
block?
Martin Braun wrote:
> On Thu, Apr 02, 2009 at 04:55:39AM +0200, William Sherman wrote:
>&
Michael Dickens wrote:
> Hi Ali - Check out the following MS thesis, by a ex-colleague of mine
> here at ND:
>
> Practical Implementation of a Cognitive Radio System for Dynamic
> Spectrum Access
>
> < http://etd.nd.edu/ETD-db/theses/available/etd-07252008-162749/ >
>
> It sounds similar to what
Hi,
I have been trying to create a new block
"howto_ren_bin_statistics_mean_f" using the howto example as the base.
I have created a .cc, .h, edited the howto.i and edited the Makefile.am.
The block successfully "compiles" after calling automake -> ./configure
-> make, and .la, howto.cc, howto.p
Thank you, I understand there can only be one top block, but it can have
multiple flowgraphs inside it.
What if I wanted to change the parameters of just one of the flowgraphs
during runtime? Would I need to kill off the whole top block, create
another one with changes made to the one flowgraph
Hi,
I want to use one USRP to transmit and receive. I tried setting up two
flowgraphs (top_blocks), one that will be a receiver "thread" and
another a transmitter "thread". However the program complains:
RuntimeError: gr_top_block_impl: multiple simultaneous gr_top_blocks not
allowed
Is there no
Hi,
I am interested in using USRP + Gnuradio as a Cognitive Radio. I wish to
apply learning algorithms to an 802.11 style MAC and evaluate the
response of the radio for using unused spectra.
Is there an 802.11 style MAC protocol (i.e. RTS/CTS) for Gnuradio out
there? I could begin using this as a
Hi,
I am planning to modify benchmark_xx to send and receive custom packets
(similar to 802.11 packets).
I have been rooting around these two files. I would like to know: in
benchmark_rx how does the radio "know" when it has received a packet
(and call rx_callback). rx_callback is called by pkt.p
I am working with a USRP1. I eventually will want to transmit and
receive data packets between USRP1s, but right now I am getting to grips
with the system.
I am currently trying out the benchmark_tx, benchmark_rx programs.
I call benchmark_rx on my USRP1's LFRX-LF daughterboard and leave it
runni
36 matches
Mail list logo
