Wednesday, July 30, 2014

Re: [Discuss-gnuradio] Slow control external hardware

On 07/30/2014 07:40 AM, Daniele Nicolodi wrote:
> On 29/07/2014 19:29, mleech@ripnet.com wrote:
>> There are rather a lot of ways to choke this particular cat, writing a
>> block is just one of them.
>>
>> I do "control external device" things from within GRC without custom
>> blocks, using "helper code" and a polling function at a low rate
>> that drives a simple state machine. I use this for controlling a
>> serial device that turns calibration sources on/off. It can get data
>> out of the flow-graph if it needs to, with low-rate "probe" blocks.
>>
>> Some might call this inelegant, I call it saving the headache of
>> writing/maintaining custom blocks when the functionality doesn't
>> really require real-time access to the sample stream....
> Hello,
>
> well, writing a block that listens to messages or that emits messages
> takes less than 20 lines of python all included. I would hardly call
> this an "headache" to maintain :)
>
> Cheers,
> Daniele
>
It's a big universe, there's room for different design choices....

--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org


_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

No comments:

Post a Comment