On 07/30/2014 07:40 AM, Daniele Nicolodi wrote:
On 29/07/2014 19:29, mle...@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
On 29/07/2014 19:29, mle...@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 dr
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 controll
http://gnuradio.org/doc/doxygen/page_python_blocks.html
$ git grep self.set_msg_handler **/*.py[19:20:26]
gr-blocks/python/blocks/qa_python_message_passing.py
M
On 07/29/2014 05:02 PM, Daniele Nicolodi wrote:
> On 29/07/2014 16:57, Martin Braun wrote:
>> Daniele,
>>
>> there's loads of blocks th
On 29/07/2014 16:57, Martin Braun wrote:
> Daniele,
>
> there's loads of blocks that use messages, as well as manual pages for
> that. And I would recommend you use them for this case. Create a block
> that talks to the serial port, and give it a message port.
Hello Martin,
thank for your answer
Daniele,
there's loads of blocks that use messages, as well as manual pages for
that. And I would recommend you use them for this case. Create a block
that talks to the serial port, and give it a message port.
M
On 07/29/2014 02:55 PM, Daniele Nicolodi wrote:
> Hello,
>
> I need to control a RF
