[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: re[Discuss-gnuradio] configuring with usrp2 src present
From: |
Andy_Long |
Subject: |
Re: re[Discuss-gnuradio] configuring with usrp2 src present |
Date: |
Fri, 16 Apr 2010 13:56:12 -0700 (PDT) |
Hello, Firas,
Yes. I have tried it like that:
def main():
t = my_top_block()
while 1:
t.start()
print t.c2mag.level()
time.sleep(3)
t.stop()
t.wait()
The maxmum records of USRP2 output is five. After that usrp2 collapses. I
used "head" block to limit the number of samples I want to colloct. It will
returns a -1 to stop the flow graph. Maybe it caused the problem? But I do
not know how to limit the samples without this block
Thank you.
best regards,
Andy
Error message:
>>> StdErr: usrp2: failed to enable realtime schedulingStdErr:
2.51469463974e-07
StdErr: S2.75961855481e-07
StdErr: S2.76194623337e-07
StdErr: S2.76736606134e-07
StdErr: S2.67613864975e-07
StdErr: usrp2: channel 0 not receiving
usrp2::rx_samples() failed
2.67613864975e-07
StdErr: usrp2: channel StdErr: 0StdErr: not receivingStdErr:
StdErr: usrp2::rx_samples() failedStdErr:
Firas A. wrote:
>
> Hi,
>
> The xxx.stop() and xxx.wait() should be called after time.sleep(xxx)
>
> see:
> http://gnuradio.org/redmine/wiki/gnuradio/TutorialsWritePythonApplications
>
>
>
>
> Best Regards,
>
> Firas
>
>
> ----- Original Message ----
>> From: Andy_Long <address@hidden>
>> To: address@hidden
>> Sent: Fri, April 16, 2010 11:52:57 AM
>> Subject: Re: re[Discuss-gnuradio] configuring with usrp2 src present
>>
>>
> Hi Firas,
>
> But it shows the same error as before. I am doing tests
>> like that:
>
> def main():
> t =
>> my_top_block()
>
>
>> t.start()
>
>> t.wait()
> t.stop()
>
>> print t.c2mag.level() #print power
>
>> time.sleep(3)
>
>>
>
>> m = my_top_block()
>
>>
> m.start()
>
>> m.wait()
>
>> m.stop()
> print m.c2mag.level() #print
>> power
> time.sleep(3)
>>
>
>>
> n =
>> my_top_block()
>
>
>> n.start()
>
>> n.wait()
> n.stop()
>
>> print n.c2mag.level() #print power
>
>> time.sleep(3)
>>
>>
>
> r =
>> my_top_block()
>
>
>> r.start()
>
>> r.wait()
> r.stop()
>
>> print r.c2mag.level() #print power
>
>> time.sleep(3)
>>
>
>>
> Or I am doing the while loop like that
>
> def
>> main():
>
> while
>> 1:
> t =
>> my_top_block()
>
>> t.start()
>
>> t.wait()
>
>> t.stop()
> print
>> t.c2mag.level() #print power
>
>> time.sleep(3)
>
>
> error
>> message
>
>>>>
>> StdErr: usrp2: failed to enable realtime
>> scheduling
> 1.43518970096e-07
> StdErr: S1.41236599021e-07
> StdErr: usrp2:
>> channel 0 not receiving
> usrp2::rx_samples() failed
> 0.0
> StdErr: usrp2:
>> channel 0 not receiving
> usrp2::rx_samples() failed
> 0.0
>
>
>
> The
>> thing is that the first output is always fine to print the received
> power.
>> After that it will print the power again as expected, however with
> error
>> message "StdErr: S". It sometimes can print the power for third time,
> then
>> usrp2 collapses with "StdErr: usrp2: channel 0 not
>> receiving
> usrp2::rx_samples() failed". However,most of time usrp2 collapses
>> in the
> second loop rather than third loop.
>
> If it is the problem of
>> setting the loop of flow graph, I think I can't get
> the second output or even
>> third output. Am I right? For example, if I
> changed the usrp2 source with
>> constant sine wave, the program runs fine.
>
>
> If it is the problem of
>> usrp2, I guess I will face the same problem even I
> am writing my own block
>> simliary like message sink or gr-bin_statistics
> sink.
>
> Another
>> question is that can I change the tune delay time in
> gr-bin_statistics block
>> to do the same thing such as time.sleep(3)? I just
> throw all the samples in
>> next 3 seconds
>
>
> thank you
> best
>> regards,
> Andy
>
>
>>
>
>
>
>
>
> Firas A. wrote:
>>
>> Hi,
>>
>>
>> Replace all xxx.run with xxx.start() and put xxx.wait()
>> followed by
>> xxx.stop() to stop the flowgraph
>>
>> Best
>> Regards,
>>
>> Firas
>>
>>
>>
>>
>>
>> ----- Original Message ----
>>> From: Andy_Long <
>> ymailto="mailto:address@hidden"
>> href="mailto:address@hidden">address@hidden>
>>>
>> To:
>> href="mailto:address@hidden">address@hidden
>>>
>> Sent: Thu, April 15, 2010 10:50:39 AM
>>> Subject: Re:
>> re[Discuss-gnuradio] configuring with usrp2 src present
>>>
>>>
>>
>> Hello,Johnathan
>>
>> Did I have some misunderstanding about
>> it? I still
>>> think the problem is from
>> USRP2 rather than
>> flow graph.
>> For example, I
>>> made some tests to change the
>> while loop such as:
>>
>> def main():
>>
>>
>>>
>> t = my_top_block()
>>
>> t.run()
>>
>>> print t.c2mag.unmuted():
>> #show exceed threshold or not
>>
>>> time.sleep(3)
>>
>>
>> m = my_top_block()
>>
>> m.run()
>>>
>> print m.c2mag.unmuted(): #show
>> exceed threshold or not
>>>
>> time.sleep(3)
>>
>>
>> n = my_top_block()
>>>
>>
>> n.run()
>> print n.c2mag.unmuted(): #show
>>
>>> exceed threshold or not
>> time.sleep(3)
>>
>>
>>
>> As same
>>> condition as before, after two
>> correct outputs, the third one start
>> to show
>>> the
>> error.
>>
>> Thank you.
>> regards,
>> Andy
>>
>>
>>
>>
>> Johnathan
>>> Corgan-2 wrote:
>>>
>>
>>> On Wed, Apr 14, 2010 at 12:27, Andy_Long <
>>>
>> ymailto="mailto:
>> href="mailto:address@hidden">address@hidden"
>>
>>> href="mailto:
>> href="mailto:address@hidden">address@hidden">
>> ymailto="mailto:address@hidden"
>> href="mailto:address@hidden">address@hidden>
>>
>>> wrote:
>>>
>>>> I have faced the same problem.
>> I try to received the
>>> limited samples from
>>>> USRP2 by
>> using "head"block. It should return a
>>> -1 and the flow graph
>> will
>>>> stop, am I right?
>>>
>>> The
>>>
>> flowgraph will not only stop, but will end its lifetime. Once
>>>
>>
>>> run() has returned, the flowgraph is no longer usable, or as we
>> like
>>> to
>>> say, further operations on it are
>> "undefined."
>>>
>>> In general,
>>> starting and
>> stopping an individual flowgraph should occur
>>> at the same
>>
>>> level of processing as application startup and
>> shutdown.
>>> Anything else
>>> is usually a sign of incorrect
>> design (though not
>>> always.) The
>>> run() method on a
>> top block is really just a convenient
>>> way of telling
>>>
>> GNU Radio your application has nothing else to do until
>>> the
>> flowgraph
>>> exits.
>>>
>>> Can you describe what you
>> are trying to do?
>>>
>>>
>>> Johnathan
>>>
>>
>>>
>>>
>>>
>> _______________________________________________
>>> Discuss-gnuradio
>> mailing
>>> list
>>>
>>> href="mailto:
>> ymailto="mailto:address@hidden"
>> href="mailto:address@hidden">address@hidden">
>> ymailto="mailto:address@hidden"
>> href="mailto:address@hidden">address@hidden
>>>
>>
>>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>
>>>
>>>
>>
>> --
>> View this message in
>> context:
>>>
>> http://old.nabble.com/reconfiguring-with-usrp2-src-present-tp27615622p28252256.html
>>
>> Sent
>>> from the GnuRadio mailing list archive at
>>>
>> href="http://Nabble.com">
>> href="http://Nabble.com">Nabble.com.
>>
>>
>>
>>
>> _______________________________________________
>> Discuss-gnuradio
>>
>>> mailing list
>>
>>> href="mailto:
>> ymailto="mailto:address@hidden"
>> href="mailto:address@hidden">address@hidden">
>> ymailto="mailto:address@hidden"
>> href="mailto:address@hidden">address@hidden
>>
>>
>>> href="
>> href="http://lists.gnu.org/mailman/listinfo/discuss-gnuradio"
>> target=_blank
>> >http://lists.gnu.org/mailman/listinfo/discuss-gnuradio"
>>>
>> target=_blank
>>> >
>> href="http://lists.gnu.org/mailman/listinfo/discuss-gnuradio"
>> target=_blank
>> >http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>>
>> _______________________________________________
>>
>> Discuss-gnuradio mailing list
>>
>> ymailto="mailto:address@hidden"
>> href="mailto:address@hidden">address@hidden
>>
>> href="http://lists.gnu.org/mailman/listinfo/discuss-gnuradio"
>> target=_blank
>> >http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>>
>
> --
> View this message in context:
>> http://old.nabble.com/reconfiguring-with-usrp2-src-present-tp27615622p28264537.html
> Sent
>> from the GnuRadio mailing list archive at
>> Nabble.com.
>
>
>
> _______________________________________________
> Discuss-gnuradio
>> mailing list
>
>> href="mailto:address@hidden">address@hidden
>
>> href="http://lists.gnu.org/mailman/listinfo/discuss-gnuradio"
>> target=_blank
>> >http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
--
View this message in context:
http://old.nabble.com/reconfiguring-with-usrp2-src-present-tp27615622p28271684.html
Sent from the GnuRadio mailing list archive at Nabble.com.
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Andy_Long, 2010/04/14
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Johnathan Corgan, 2010/04/14
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Andy_Long, 2010/04/14
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Andy_Long, 2010/04/15
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Firas Abbas, 2010/04/16
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Andy_Long, 2010/04/16
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Firas Abbas, 2010/04/16
- Re: re[Discuss-gnuradio] configuring with usrp2 src present,
Andy_Long <=
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Johnathan Corgan, 2010/04/16
- Re: re[Discuss-gnuradio] configuring with usrp2 src present, Andy_Long, 2010/04/16