Martin,
Sorry for the slow reply. It's a USRP N210. I'm running a pybombs build of UHD
and GNURadio that's about a month old.
Marcus,
Using "actual_rf_freq" and "actual_dsp_freq", I get:
about to issue tune command...
-- Successfully tuned to 800.000000 MHz
--
immediate tune result: 800.000000MHz RF, 0.000000 Hz DSP
get_center_freq before sleep: 800.000000 MHz
get_center_freq after sleep: 800.000000 MHz
-Doug
________________________________
From: discuss-gnuradio-bounces+danderson=its.bldrdoc....@gnu.org
[discuss-gnuradio-bounces+danderson=its.bldrdoc....@gnu.org] on behalf of
Marcus Müller [marcus.muel...@ettus.com]
Sent: Tuesday, April 28, 2015 1:38 AM
To: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Confirming uhd.set_command_time is working
Hi Doug,
I'm not 100%, but: Getting the center frequency might be a command which will
also end up in the timed command queue.
What happens if you:
u.set_command_time(u.get_time_now() + uhd.time_spec(2))
print("about to issue tune command...")
result = u.set_center_freq(800e6)
u.clear_command_time()
print("immediate tune result: {:f}MHz RF, {:f} Hz
DSP".format(result.rf_freq/1e6, result.dsp_freq))
print("get_center_freq before sleep: {:f} MHz".format(u.get_center_freq()/1e6))
time.sleep(2)
print("get_center_freq after sleep: {:f} MHz".format(u.get_center_freq()/1e6))
Greetings,
Marcus
On 04/28/2015 12:03 AM, Anderson, Douglas J. wrote:
Hi all,
I'm playing around with timed commands on the USRP, but I'm not sure I
understand them correctly.
I've got a usrp connected as "u" and set to center freq 700e6.
>>> u.set_command_time(u.get_time_now() + uhd.time_spec(2));
>>> u.set_center_freq(800e6); u.clear_command_time();
>>> print(u.get_center_freq()); time.sleep(2); print(u.get_center_freq())
-- Successfully tuned to 800.000000 MHz
--
<gnuradio.uhd.uhd_swig.tune_result_t; proxy of <Swig Object of type
'::uhd::tune_result_t *' at 0x7f1b75a3b930> >
800000000.0
[... 2 second pause is here ...]
800000000.0
It looks like it's changing the freq immediately... but I'm assuming as usual
there's more than meets the eye to this command. Any hints?
-Doug
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org<mailto:Discuss-gnuradio@gnu.org>
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
