|
From: | Marcus Müller |
Subject: | Re: [Discuss-gnuradio] Higher Accuracy Metadata Header? |
Date: | Mon, 25 Apr 2016 16:31:24 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 |
Hi Michael, I think I see a bug in gr-uhd there! So point is that the python code generated by this is (example): [...] ################################################## # Blocks ################################################## self.uhd_usrp_sink_0 = uhd.usrp_sink( ",".join(("", "")), uhd.stream_args( cpu_format="fc32", channels=range(1), ), ) self.uhd_usrp_sink_0.set_time_source("external", 0) self.uhd_usrp_sink_0.set_time_unknown_pps(uhd.time_spec()) self.uhd_usrp_sink_0.set_samp_rate(4e6) self.uhd_usrp_sink_0.set_center_freq(1.5e9, 0) [...]Now, what GRC generates here means that you first set your time, then you set your sampling rate – and on B2xx, that might have the side effect of changing your master clock rate. The MCR is the speed at which the internal time counter is incremented. You can avoid that auto-MCR behaviour by explicitely setting the master clock rate first – could you add "master_clock_rate=30e3" to your device Address or device Arguments? Best regards, Marcus On 04/25/2016 04:09 PM, Michael Skaggs
wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |