Hi Marcus, I have now tried exactly that and it works. Thanks. One thing I am trying now is to implement the command times over the message ports but if you say time commands are not supported in gr-uhd I maybe stuck. I see the functions are in a ifdef.
Thanks, Nigel From: [email protected] [mailto:[email protected]] On Behalf Of Marcus D. Leech Sent: 02 March 2016 02:08 To: [email protected] Subject: Re: [Discuss-gnuradio] UHD Source Block and N210/SBX Synchronisation On 03/01/2016 10:43 AM, Marcus D. Leech wrote: The only thing really missing in gr-uhd is the ability to do timed commands. You can force integer-N mode by constructing your own tune_request that includes the integer-N option. You'd use a feature from the latest Gnu Radio to help you with this, because it involves getting into the internal structure of a tune_request blob. So, use the "Python module" block, and in that Python do something like: def integer_N_tune_me(freq): r = uhd.tune_request(freq) r.args = {"mode_n" : "integer"} return r Then, in your UHD source/sink block, instead of using your target frequency directly, use: your_module_name.integer_N_tune_me(desired_freq) Martin could probably comment on the feasibility of adding timed commands to gr-uhd. What I actually meant wasn't that gr-uhd doesn't have timed-command support, but rather, the GRC scaffolding for this doesn't really exist. If you write your own Python, you can of course use timed-commands with gr-uhd, and in fact if you're willing to edit the output of GRC (generated Python) you can wire-in timed-commands fairly easily, it's just that there's no way to set this up with the existing UHD blocks for GRC (yet). _______________________________________________ Discuss-gnuradio mailing list [email protected]<mailto:[email protected]> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
