Re: [Discuss-gnuradio] GRC Reacting Slowly

2015-05-27 Thread Richard Bell
Andreas, No I'm not using an embedded system to develop on. I'm using an HP Core i7 laptop with 16Gig of RAM, Ubuntu 14.04 with GNU Radio 3.7.8. The delay also occurs everytime I want to make a change to a blocks paramters. I have to wait >2 seconds for the blocks paramter window to open and then

Re: [Discuss-gnuradio] Is file sink block resetting USRP?

2015-05-27 Thread Marcus D. Leech
On 05/27/2015 05:52 PM, Carl Olsson wrote: Hi all, I use a file sink block in my flow graph to record samples from a USRP N210. I start the flow graph and then after some time starts to record using the file sink block by switching it on using a selector block. My question is, when the file

Re: [Discuss-gnuradio] Is it possible to create a block from other blocks?

2015-05-27 Thread Carl Olsson
Thank you for all the answers! I will try the different solutions. Best regards, Carl On 27 May 2015 at 00:42, Douglas Geiger wrote: > Scrolling back I see I missed a little bit of the earlier discussion - so > to elaborate a little: > > Simple 'merging of blocks' (i.e. I have several blocks

Re: [Discuss-gnuradio] GRC Reacting Slowly

2015-05-27 Thread Murray Thomson
I had this problem for a while when using a large number of blocks. The cause, I think, is that the companion checks if the flowgraph is correct after every change. You will only be able to compile if it's correct (blocks are connected, variable names exist...). If this is really the reason, It wou

[Discuss-gnuradio] Integration of python's time.time() and work() calls

2015-05-27 Thread Anil Kumar Yerrapragada
Hi I'm writing a custom block in python. The application goes like this: I specify the minimum number of samples I need by using the forecast function. This ensures that I have that many samples available in the in-buffer of the block every time work is called. Once I have as many samples as I ne

Re: [Discuss-gnuradio] Choose thread

2015-05-27 Thread marco Ribero
Il giorno mer 27 mag 2015 alle ore 16:29 Marcus Müller < marcus.muel...@ettus.com> ha scritto: > Yes. The Thread-per-Block-scheduler gets its name from the fact that > every block gets its own thread. > You should really use it -- using STS will probably kill the performance > you can gain by acce

Re: [Discuss-gnuradio] Buffer Overflow Debug

2015-05-27 Thread Richard Bell
Martin, I'll update you on this in a new thread soon. We had been running into the age old problem of plugging one hole and having two more leaks spring up. We are finally onto something that seems to be fixing everything. It's a simple code change in HPD. Rich Sent from my iPhone > On May

Re: [Discuss-gnuradio] GRC Reacting Slowly

2015-05-27 Thread Andreas Ladanyi
Hi rich, on which hardware platform are you working ? Is this a PC or embedded device ? cheers, Andy Am 27.05.2015 um 01:09 schrieb Richard Bell: GNU Radio 3.7.8, Ubuntu 14.04 I have an admittedly large number of blocks in my current flow graph because I'm in the middle of some hardcore de

Re: [Discuss-gnuradio] Choose thread

2015-05-27 Thread Marcus Müller
Dear Marco, > I need that different blocks run under the same thread(because CUDA > require to make everything inside a single thread..each thread is > associated to a different GPGPU)..so,without the usage of STS > scheduler,is not possible to run different blocks with same thread? Yes. The Thread

Re: [Discuss-gnuradio] Choose thread

2015-05-27 Thread marco Ribero
Il giorno dom 24 mag 2015 alle ore 19:52 Tom Rondeau ha scritto: > Don't use the STS scheduler. It is, after all, the Single-Threaded > Scheduler. And setting the thread affinity under that condition is a nop. > That will only work with the default TPB scheduler. > > Tom > > I need that different

Re: [Discuss-gnuradio] Buffer Overflow Debug

2015-05-27 Thread Martin Braun
Hey Richard, I'm going to need some time, peace and quiet to get to the bottom of this. Which means not in the very near future :) But I'm very interested in getting this to work. Can you post some failing codes/OOTs somewhere for me to start testing? M On 22.05.2015 15:22, Richard Bell wrote: >