Re: [Discuss-gnuradio] Constant carrier digital transmission

On 8/16/16 11:28 PM, Inspire Me wrote: Hi Ed Much appreciated. You mentioned latency due to queued flags. This has potential to cause us issues. I was wondering if it is possible to build a block as a sort of switch that takes input from the standard HDLC Framer but executues continuously, ie

Re: [Discuss-gnuradio] Constant carrier digital transmission

In a GnuRadio block that is derived from a "sync" block, the number of input and output items are the same, so the work function is supplied with a single value called "nitems". The normal control flow of a typical work function uses a loop that iterates over nitems, taking one item from the

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

You could try by creating a symbolic link to /dev/null somewhere you can create arbitrary files; eg. ln -s /dev/null /tmp/nirvana and use that instead of /dev/null On 16.08.2016 23:40, Derek Kozel wrote: > Hello Michael, > > Unfortunately we've reached past my depth in the file sinks and tags.

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

Hello Michael, Unfortunately we've reached past my depth in the file sinks and tags. Hopefully someone with more experience can step in at this point. My guess with the detached headers is that Nate's trick with the filenames and /dev/null fails because there's a suffix being added for the

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

Derek, Funny you should mention the file meta sink block... originally that was what we had implemented using a copy block to create the push button recording functionality, but that introduced errors in the alignment between headers and the IQ data since the copy block did not play nice with

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

I'd recommend leaving the filenames as is. The call to the mboard sensor will cause delays and doesn't reflect the time that the samples actually were acquired. Instead change to using a File Meta Sync which will store the timestamp tags produced by the USRP and gr-uhd. These contain the USRP's

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

Derek, Thanks for responding, that is indeed very close to the functionality I'm after. However there is one small(?) deviation from what I'm after and that is that I'm trying to use GPS time stamps with the intent of synchronized acquisitions between separate X310 units at a later time. To that

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

Marcus, Thanks for getting back to me so quickly. I'm currently using an Ettus X310 with a UBX-160 daughterboard, and the output of uhd_usrp_probe is as follows: linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.git-156-g2d68f228 Thanks again, Mike G On Tue, Aug 16, 2016 at 12:11 PM

Re: [Discuss-gnuradio] Illegal sub-command when installing

On 08/16/2016 09:45 AM, Jason Matusiak wrote: > Attempted to install gnuradio on a tablet and had a problem with > rtl-sdr. I blew away my install directory as well as .pybombs. Now > when I run the recipe add command from the instructions, I get and error: > PyBOMBS.recipes - ERROR - Illegal

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

I created an hier block that does exactly that: run it once, reload your blocks, and then use the "QT GUI Record Button" block as a sink in other flowgraphs. Thank you Derek for sharing Nate's flowgraph - my block had been using a selector block, and created a 0-byte file every time a flowgraph

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

Hello Mike, Here is a simple, but clever, flowgraph put together by Nate Temple which does exactly what you describe. It isn't an answer to the time errors you've seen, but I hope it is useful anyways. Regards, Derek On Tue, Aug 16, 2016 at 9:08 AM, Marcus Müller

[Discuss-gnuradio] Illegal sub-command when installing

Attempted to install gnuradio on a tablet and had a problem with rtl-sdr. I blew away my install directory as well as .pybombs. Now when I run the recipe add command from the instructions, I get and error: PyBOMBS.recipes - ERROR - Illegal sub-command: `add' PyBOMBS.recipes - ERROR - Valid

Re: [Discuss-gnuradio] Time errors using burst tagger and tagged file sink

Hi Michael, what USRP are you using, and which version of UHD? Best regards, Marcus On 16.08.2016 17:41, Michael Giallorenzo wrote: > Hi everyone, > > I'm currently trying to develop a gui for recording selected samples > of data while viewing the spectrum (the user can watch a waterfall >

[Discuss-gnuradio] Time errors using burst tagger and tagged file sink

Hi everyone, I'm currently trying to develop a gui for recording selected samples of data while viewing the spectrum (the user can watch a waterfall display of the readings being taken on an Ettus x310, and press and hold a button to record data when the spectrum looks interesting). The

Re: [Discuss-gnuradio] qa_polar_xxx and qa_zeromq_xxx failed in the make test!

Same fix for the zeromq errors. sudo apt-get install python-zmq BTW, the detailed error log is in gnuradio/build/Testing/Temporary/LastTest.log Ron On 08/16/2016 12:31 AM, Johannes Demel wrote: Hi all, for clarification. Scipy is an optional dependency. Thus, the tests might fail. All

Re: [Discuss-gnuradio] qa_polar_xxx and qa_zeromq_xxx failed in the make test!

Hi all, for clarification. Scipy is an optional dependency. Thus, the tests might fail. All polar tests import 'polar.channel_construction', which imports 'polar.channel_construction_awgn', which in turn uses 'scipy.optimize.fsolve' and 'scipy.special.erfc'. When I wrote this peace of code, I