Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-04-01 Thread Martin Braun
On 31.03.2015 14:25, Anderson, Douglas J. wrote: Marcus, That makes sense, I hadn't thought of the DSP tuning issue, though I think it would be infinitely more useful to make the stream tagging logic aware of LO/DSP tuning and tag the first usable block in either case. Slightly more involved

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-04-01 Thread Marcus Müller
-gnuradio-bounces+danderson=its.bldrdoc@gnu.org [discuss-gnuradio-bounces+danderson=its.bldrdoc@gnu.org] on behalf of Martin Braun [martin.br...@ettus.com] Sent: Wednesday, April 01, 2015 11:30 AM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] gr-uhd: rx_freq tag

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-04-01 Thread Anderson, Douglas J.
=its.bldrdoc@gnu.org [discuss-gnuradio-bounces+danderson=its.bldrdoc@gnu.org] on behalf of Martin Braun [martin.br...@ettus.com] Sent: Wednesday, April 01, 2015 11:30 AM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked On 31.03.2015 14:25, Anderson

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-04-01 Thread Anderson, Douglas J.
[marcus.muel...@ettus.com] Sent: Wednesday, April 01, 2015 12:34 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked Hi Doug, What about adding an lo_locked metadata tag to the stream of samples? You could send lo_locked value=False on the last

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-04-01 Thread Martin Braun
On 01.04.2015 10:49, Anderson, Douglas J. wrote: Martin, I think we could have the same effect with a much simpler solution: What about adding an lo_locked metadata tag to the stream of samples? This would require the FPGA to automatically send some kind of notification that the LO has

[Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-03-31 Thread Anderson, Douglas J.
Hi all, I've been working on a flowgraph that controls sweeping a USRP by retuning and then dumping samples until catching the sample tagged with rx_freq of the correct value. I was confused as to why I was still getting mountains of garbage samples (several hundred thousand at 10MS/s) after

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-03-31 Thread Anderson, Douglas J.
] Sent: Tuesday, March 31, 2015 2:15 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked Hi Doug, the rationale behind that is that these tags correspond to the stream metadata coming from the USRP, which tell the host when the tuning *operation* has

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-03-31 Thread Marcus Müller
@gnu.org [discuss-gnuradio-bounces+danderson=its.bldrdoc@gnu.org] on behalf of Marcus Müller [marcus.muel...@ettus.com] *Sent:* Tuesday, March 31, 2015 2:15 PM *To:* discuss-gnuradio@gnu.org *Subject:* Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked Hi Doug, the rationale behind

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-03-31 Thread Anderson, Douglas J.
: Tuesday, March 31, 2015 3:31 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked I must admit I don't know the exact reason, but the thing about the remaining DC offset is generally that it depends on many factors, including temperature, so it's very

Re: [Discuss-gnuradio] gr-uhd: rx_freq tag and lo_locked

2015-03-31 Thread Marcus Müller
Hi Doug, the rationale behind that is that these tags correspond to the stream metadata coming from the USRP, which tell the host when the tuning *operation* has taken place. Now, you're right, it's a problem to think you're tuned although your LO still hasn't settled, but since tunes could also