Re: [Discuss-gnuradio] Flowgraph stopped after few minutes

2012-08-01 Thread Pol Henarejos
Dear Tom, I will give it a try. I will keep you in touch. Thanks for your answer. Pol Henarejos Research Engineer, MSc pol.henare...@cttc.es Centre Tecnològic de Telecomunicacions de Catalunya (CTTC) Engineering Unit Parc Mediterrani de la Tecnologia Av. Carl Friedrich Gauss, 7 08860 Castellde

Re: [Discuss-gnuradio] Flowgraph stopped after few minutes

2012-07-30 Thread Tom Rondeau
On Mon, Jul 30, 2012 at 4:18 AM, Pol Henarejos wrote: > Dear Tom, > > All blocks are written by me. B and C produce 40 and 80 samples, > respectively. They have set_output_multiple to 40 and 80. Both forecast > have in0=noutput/40 and in0=noutput/80. A block does not have nor > set_output_multiple

Re: [Discuss-gnuradio] Flowgraph stopped after few minutes

2012-07-30 Thread Pol Henarejos
Dear Tom, All blocks are written by me. B and C produce 40 and 80 samples, respectively. They have set_output_multiple to 40 and 80. Both forecast have in0=noutput/40 and in0=noutput/80. A block does not have nor set_output_multiple nor forecast. D block (2 inputs 1 output) has set_output_multiple

Re: [Discuss-gnuradio] Flowgraph stopped after few minutes

2012-07-29 Thread Tom Rondeau
On Thu, Jul 19, 2012 at 4:54 AM, Pol Henarejos wrote: > Dear list, > > I have a simple flowgraph with two branches, with different delays that > are joined at the end. Imagine a topblock with A,B,C,D blocks. A is > connected to B and C. B and C are connected to D. A and D are sink and > source res

[Discuss-gnuradio] Flowgraph stopped after few minutes

2012-07-19 Thread Pol Henarejos
Dear list, I have a simple flowgraph with two branches, with different delays that are joined at the end. Imagine a topblock with A,B,C,D blocks. A is connected to B and C. B and C are connected to D. A and D are sink and source respectively. B and C produce packets (header and payload) from the i