Really appreciate your reply, Jason! I tried the approach recommended by using
grc_usrp.simple_sink_s to take the place of usrp.sink_s. Then, I called the
set_enable() function on simple_sink_s at the scheduler part to disable the
transmitter after the top_block starts to run. An attributeError
> The version of GNUradio that I'm using is GNURadio 3.2svn
>
I think there was some work in 3.3 for this sort of issue, but thats
just from memory, as I mostly use UHD these days.
Things you might look for:
python -c "from grc_gnuradio import usrp as grc_usrp;
help(grc_usrp.simple_usrp.simple_si
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 an
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.
Thanks,
Guanbo
On Wed, Feb 23, 2011 at 5:55 PM, Yan Nie wrote:
> Hi Guanbo,
>
> In my case, I added a tb.wait() after the tb is unlock to w
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 s
Hi, Yan
I tried the similar python code as yours, as follows:
tb.start()
send_pkt("payload", eof=False)
print "before lock()"
tb.lock()
print "after lock()"
time.sleep(1)
print "before unlock()"
tb.unlock()
print "after unlock()"
I found out that, the last print is not showing up.
Do you have
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 us
On Wed, Feb 23, 2011 at 9:25 AM, Yan Nie wrote:
> Dear all,
> I'm really sorry about the last uncompleted email. I elaborated the method
> lock() and unlock() to completely pause the flow graph without transmitting
> any signal, even if the carrier wave, but the continuous carrier wave still
> sh
Dear all,I'm really sorry about the last uncompleted email. I elaborated the method lock() and unlock() to completely pause the flow graph without transmitting any signal, even if the carrier wave, but the continuous carrier wave still shows on the oscilloscope. I'm trying to transmit 13-bit Barke
Sorry about the last uncompleted email. I tried the method lock() and unlock()
to completely pause the flow graph without transmitting any signal, but the
continuous carrier wave still showed on the oscilloscope. I'm trying to
transmit 13-bit Barker code carried by a 4MHz sinusoid wave. After th
Hi Tom,
Sorry about the question. I tried the method lock() and unlock() to pause the
flow graph that I built, but still shows the continuous signal wave on the
oscilloscope. I cannot see the pause between the signal waves. The code related
to the top_block scheduling is as followed. Could you
On Mon, Feb 21, 2011 at 9:50 PM, Yan Nie wrote:
> Dear all,
> I'm trying to stop top_block implementing the signal transmission for 5
> milliseconds and then restart the signal transmission at the transmitter
> side, by using the tb.stop() then time.sleep(0.005) to suspend the system
> for 5 milli
12 matches
Mail list logo
