[Discuss-gnuradio] Problem writing custom null sync block

2013-02-22 Thread maiconkist
Hi list, I'm writing a custom null sync block called file_writer. What I want to do is dump (to file or screen) what my null sync is receiving). The problem is that if I use the file_writer in a flow graph, after the work function is executed a few times it starts to receive the same input

Re: [Discuss-gnuradio] Problem writing custom null sync block

2013-02-22 Thread Tom Rondeau
On Fri, Feb 22, 2013 at 8:42 AM, maiconkist maiconk...@gmail.com wrote: Hi list, I'm writing a custom null sync block called file_writer. What I want to do is dump (to file or screen) what my null sync is receiving). The problem is that if I use the file_writer in a flow graph, after the

Re: [Discuss-gnuradio] Problem writing custom null sync block

2013-02-22 Thread Martin Braun (CEL)
On Fri, Feb 22, 2013 at 09:09:19AM -0500, Tom Rondeau wrote: class file_writer(gr.sync_block): ## CTOR # def __init__(self, filename, vec_size): gr.sync_block.__init__( self,

Re: [Discuss-gnuradio] Problem writing custom null sync block

2013-02-22 Thread maiconkist
Hi, you're right. Using return len(in0) solve my problem. Thanks -- View this message in context: http://gnuradio.4.n7.nabble.com/Problem-writing-custom-null-sync-block-tp39796p39805.html Sent from the GnuRadio mailing list archive at Nabble.com.