[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] how to stop the top_block and restart signal tran

From: Yan Nie
Subject: Re: [Discuss-gnuradio] how to stop the top_block and restart signal transmission
Date: Wed, 23 Feb 2011 19:26:49 -0500

I run the flow graph as an infinite loop, so the flow graph will be restart after the unlock() finished. It seems that the lock/unlock method cannot influent the whole system, and the carrier wave still keep transmitting without any stop. Could you please help me see if the method message source and insert_tail to feed the code into the flow graph is correct or not. I'm concerning if the problem is causing by the wrong use of the method to feed in the code.


On 02/23/11, Guanbo Zheng <address@hidden> wrote:
Hi Yan

I did it as well, but it seem wait for infinite time before it is finished.....
But without the lock() and unlock(), everything returns to normal.


On Wed, Feb 23, 2011 at 5:55 PM, Yan Nie <address@hidden <address@hidden>> wrote:
Hi Guanbo,

In my case,  I added a tb.wait() after the tb is unlock to wait for the unlock action finished, so that the last line shows. However, it still gives the carrier wave on the oscilloscope. I also tried top_block._u._subdev.set_enable(False) to completely disable the transmitter then set_enable(True) to re-enable the transmitter based on hardware consideration, but it still doesn't work 

On 02/23/11, Guanbo <address@hidden <address@hidden>> wrote:

Hi, Yan

I tried the similar python code as yours, as follows:

send_pkt("payload", eof=False)
print "before lock()"
print "after lock()"
print "before unlock()"
print "after unlock()"

I found out that, the last print is not showing up.

Do you have idea regarding to this issue?

Yan Nie wrote:
> Hi Jason,
> I really appreciate your help about the problem that I got. The info
> related to the GNURadio and the USRP that I'm using is listed in the
> following.
>> Please confirm that you just see the carrier, not your modulated
>> signal when using the lock()/unlock()
> I checked the result of using lock()/unlock() by correlating the down
> converted signal with the Barker code, at the transmission pause interval,
> there is no correlation peak. Therefore, it turned out there is no code
> transmitted during the transmission pause interval. Is it a right way to
> test if there is Barker code transmitted during the transmission pause
> interval? Is lock/unlock working for completely turning off the signal
> transmission for 5ms? However, I'm sure when using lock/unlock method
> still gives at least carrier signal in the pausing interval, which is
> observed on the oscilloscope.
>> Also, please tell us:
>> What version of GNUradio are you using?
> The version of GNUradio that I'm using is GNURadio 3.2svn
>> What hardware are you using? USRP?  which daughterboard?
> I'm using USRP1 with LFTX daughterboard plug-in. (similarly, at the
> receiver side,USRP1 with LFRX plug-in is utilized. )
>> Are you using UHD?
> I'm not using UHD.
> Thank you so much for all of your help!
> Thanks,
> Yan
> begin:vcard
> n:;
> adr:;;;;;;
> version:2.1
> end:vcard
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden <address@hidden>
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

View this message in context: http://old.nabble.com/how-to-stop-the-top_block-and-restart-signal-transmission-tp30982478p30999857.html
Sent from the GnuRadio mailing list archive at Nabble.com.

Discuss-gnuradio mailing list
address@hidden <address@hidden>


Attachment: ynie3.vcf
Description: Card for "Yan Nie" <ynie3@uwo.ca>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]