discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] [USRP-users] get_rx_sensor exceptions


From: Martin Braun
Subject: Re: [Discuss-gnuradio] [USRP-users] get_rx_sensor exceptions
Date: Tue, 26 Jan 2016 16:53:37 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0

Can you please also answer the 2nd part? Just so we understand what kind
of app you're running.

M

On 01/26/2016 02:54 PM, address@hidden wrote:
> Ahh, sorry, X310 with WBX-120 daughtercards.
> 
> Similar to Rx, Tx is also doing the same thing, but an exception on the
> Tx side does not happen when polling the tx sensor lo_locked flag...
> 
> Just some side observations, not sure I can really tell, but these
> commands seem to be serialized by looking at times that the retunes take
> to complete...
> 
> ------------------------------------------------------------------------
> *From: *"Martin Braun via USRP-users" <address@hidden>
> *To: *"usrp-users" <address@hidden>
> *Sent: *Tuesday, January 26, 2016 3:33:42 AM
> *Subject: *Re: [USRP-users] get_rx_sensor exceptions
> 
> Which device was this on? Also, just to confirm...
> 
> On 01/25/2016 08:45 PM, tilla--- via USRP-users wrote:
>> Hello,
>>
>> I have an app that retunes its receiver ~10 times per second., so 100
>> milli-seconds per re-tune...
>>
>> Lets say all is well wrt tracking when it is safe to get samples for a
>> particular freq after settling.
>>
>> What happens is I get an assertion error from the usrp->get_rx_sensor(
>> "lo_locked" , channel ).to_bool() quite often (every run, 10 to 20 times
>> per run, 5 minutes of rx time per run).
> 
> ...this means you do 10-20 calls to get_rx_sensor() in 5 minutes? Or
> more often?
> 
> M
>>
>> Environmental Error mapped to the packet_count Assertion in
>> radio_ctrl_core_3000.cpp line 264 using UHD 3.9.2 on win7 64 bit.
>>
>> I poll the flag in similar manners as I have seen in a while loop until
>> it is set to true, pretty vanilla stuff...
>>
>> Any thoughts or suggestions?
>>
>> The app continues to run, but I am not sure that things are still good
>> after seeing the error or if there is a graceful way of handling it.
>>
>> Thanks,
>>
>>
>> _______________________________________________
>> USRP-users mailing list
>> address@hidden
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
> 
> 
> _______________________________________________
> USRP-users mailing list
> address@hidden
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> 




reply via email to

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