Re: [Discuss-gnuradio] Segmentation fault due to thread unsafety?

2015-07-05 Thread Jeroen Boschma
is only done in case of new data in order to save CPU time), then the segmentation fault comes back again. I'll see if I can find out what the underlying problem is, then I'll post again. Best regards and thanks for your support, Jeroen On 4-7-2015 9:29, Marcus Müller wrote: Hi

[Discuss-gnuradio] Segmentation fault due to thread unsafety?

2015-07-03 Thread jeroen
solution? Sorry if I ask much, but I've spent many hours on this problem already and an expert may just have a simple solution for me :-) hanks and best regards, Jeroen ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://

Re: [Discuss-gnuradio] Trouble getting GNUradio/UHD working (with PyBombs)

2015-06-29 Thread jeroen
should probably uninstall those items. Sent from my iPhone On Jun 27, 2015, at 12:45 PM, Jeroen Boschma wrote: Hi all, I picekd up GNU Radio again and tried to get a simple plain C++ project working, but no success. Details below, hopefully somebody can set my nose in the right direction.

[Discuss-gnuradio] Trouble getting GNUradio/UHD working (with PyBombs)

2015-06-27 Thread Jeroen Boschma
build 'simultaneously' using exact the same resources I guess... Best regards, Jeroen Boschma ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Help to get control over USRP from custom block

2015-01-26 Thread Boschma, J.J. (Jeroen)
nters that have all functionality implemented from the original Ettus library? I am completely stuck... It may be an ugly hack, but I just need to get things done now. Regards, Jeroen This message may contain information that is not intended for you. If you are not the addressee or if t

[Discuss-gnuradio] Help needed with hacking through SWIG / Python / custom block

2014-11-18 Thread Boschma, J.J. (Jeroen)
Maybe something in the __init__.py file? If so, how do I generate the corresponding .pyc and .pyo files? Best regards, Jeroen This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested

[Discuss-gnuradio] How to access UHD from within my own OOT block?

2014-10-08 Thread Boschma, J.J. (Jeroen)
req(whatever); I there an easy interface/API available to do this? Or do I have to download the gr-uhd, modify it (maybe add a method to get a pointer to the USRP out of it?) and rebuild? Unfortunately I just could not find a starting point yet. Regards, Jeroen Dit bericht kan informa

Re: [Discuss-gnuradio] Cannot add an additional parameter to custom block

2014-01-21 Thread jeroen
Koslowski, Sebastian (CEL) schreef op 2014-01-21 15:16: Hi Jeroen, On 01/21/2014 01:57 PM, jer...@boschma.com wrote: * I changed the XML file to reflect the additional parameter ... It boils down to top_block.py, where I see a call to my block with only 3 parameters while in all files I can

[Discuss-gnuradio] Cannot add an additional parameter to custom block

2014-01-21 Thread jeroen
rror. Somewhere a file resides which still has the previous definition of the block with only 3 parameters instead of the new one with 4 parameters and GRC relies on that. Any ideas how to solve this are very welcome :-) Jeroen ___

Re: [Discuss-gnuradio] Cannot see my custom blocks in GRC

2014-01-19 Thread Jeroen Boschma
On 18-1-2014 16:45, Martin Braun wrote: On 01/17/2014 05:05 PM, jer...@boschma.com wrote: For some reason I can't get it to work... I added the env var manually: export GRC_BLOCKS_PATH=/usr/local/share/gnuradio/grc/blocks which did not seem to work (although that folder contains my xml-fil

Re: [Discuss-gnuradio] Cannot see my custom blocks in GRC

2014-01-17 Thread jeroen
Martin Braun schreef op 2014-01-17 16:31: On 01/17/2014 03:20 PM, jer...@boschma.com wrote: Hi all, After having problems in version 3.6.5 I decided to move to 3.7. So I reinstalled Ubuntu to start with a clean OS without 'loose ends' pointing to old GNU radio versions, then installed UHD and G

[Discuss-gnuradio] Cannot see my custom blocks in GRC

2014-01-17 Thread jeroen
TNO_jamming' in the list with my blocks). Any ideas? Jeroen ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Problem using FFT-class in my own written block (part II)

2013-12-06 Thread jeroen
Marcus Müller schreef op 2013-12-06 13:38: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hej Jeroen, 2) In the top-level CMakeLists.txt I modified/added (just guessing what to do...): I wouldn't call your method "guessing"; you used strong indications! :D Ok, now I see what

Re: [Discuss-gnuradio] Problem using FFT-class in my own written block (part II)

2013-12-06 Thread jeroen
Marcus Müller schreef op 2013-12-06 08:02: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jeroen, it's not advisable to use the 3.7 Out of tree-module directory architecture with GR 3.6. However, gr_modtool should be generating modules that fit exactly your installed version. You shou

Re: [Discuss-gnuradio] Problem using FFT-class in my own written block

2013-12-05 Thread jeroen
jer...@boschma.com schreef op 2013-12-05 11:40: Jeroen, That tutorial you mentioned doesn't give you the whole picture about configuring your OOT module with different needs like yours. Also read through this one: http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModulesConfig

Re: [Discuss-gnuradio] Problem using FFT-class in my own written block

2013-12-05 Thread jeroen
Jeroen, That tutorial you mentioned doesn't give you the whole picture about configuring your OOT module with different needs like yours. Also read through this one: http://gnuradio.org/redmine/projects/gnuradio/wiki/OutOfTreeModulesConfig And note the subtle change between 3.7.2 versus

[Discuss-gnuradio] USRP + wbx-fe-simple board + WA5VJB antenna.

2012-08-02 Thread Slobbe, Jeroen (NL - Amstelveen)
lution for this problem? Great tnx in advantage! Kind Regards, Jeroen Slobbe - This e-mail message and its attachments are subject to the disclaimer published at the following website of Deloitte: http://www.deloi