Re: [Discuss-gnuradio] E310: Setting "master clock"

2018-07-12 Thread CEL
Hi Mike, Martin and Marcus, I'll argue that from a mile high that changing MCR at runtime of a GR flow graph is an *extreme* corner case: It de-facto requires teardown of the UHD streamer, right (when else would you need it)? And that really doesn't fit all too nicely with GNU Radio's streaming

Re: [Discuss-gnuradio] E310: Setting "master clock"

2018-07-12 Thread Marcus D. Leech
On 07/12/2018 01:49 PM, Martin Braun wrote: On 07/10/2018 01:40 PM, Marcus D. Leech wrote: It seems to work properly. I get indications during start up that the E310 is selecting the clock_rate per my settings, and it's also not throwing any decimation error when I deliberately mismanage the

Re: [Discuss-gnuradio] E310: Setting "master clock"

2018-07-12 Thread Martin Braun
On 07/10/2018 01:40 PM, Marcus D. Leech wrote: >> It seems to work properly. I get indications during start up that the >> E310 is selecting the clock_rate per my settings, and it's also not >> throwing any decimation error when I deliberately mismanage the >> clock-sample rate ratio. >> >> So,

Re: [Discuss-gnuradio] E310: Setting "master clock"

2018-07-10 Thread Marcus D. Leech
On 07/10/2018 04:18 PM, Mike Gilmer wrote: I've had no problem implementing several command line options using GNU Radio's parameters blocks. I can set sample rate, bandwidth, center frequency successfully. My command line looks like this: python E310_GP.py --samprate 20 --ctrfrq