[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Clarification of lock() and unlock() in Dynamic F
From: |
Eric Blossom |
Subject: |
Re: [Discuss-gnuradio] Clarification of lock() and unlock() in Dynamic Flow-Graph Reconfiguration |
Date: |
Sun, 29 Aug 2010 20:05:58 -0700 |
User-agent: |
Mutt/1.5.20 (2009-12-10) |
On Sun, Aug 29, 2010 at 07:27:21PM -0500, Venkat Vinod wrote:
> Hello All,
>
> I am having some difficulties implementing a cognitive receiver program that
> involves dynamically reconfiguring the USRP between sensing the spectrum and
> acting as a receiver based on the results of the spectrum sensing. The
> program I am developing is mostly based on the usrp_spectrum_sense.py for
> the sensing part and benchmark_rx.py for the receiving part. The
> specifications for our platform are at the end of the e-mail.
>
> The general logic of my program is to run one flow graph which is connected
> in the same way as in the usrp_spectrum_sense program. After obtaining the
> results from the spectrum sensing, I wish to reconfigure the flow graph to
> connect the USRP to receive and demodulate a user-defined number of packets
> just as in the benchmark_rx program whenever we deem the spectrum to be
> free, after which we could revert to the configuration in the first flow
> graph and continue until the program is terminated.
>
> Here is some code of the most relevant parts of the program:
>
>
>
> #################################################################
>
> CODE :
>
>
> else:
> print "Receiver Mode : USRP to Switch to Receiving Packets "
> self.tb.stop()
Don't call stop. Just call lock.
> self.tb.lock() # THIS IS
> WHERE WE WANT TO RECONFIGURE TO RECEIVE
> #
> PACKETS
>