1) I created two named PIPEs:

$ mkfifo pipe_in
$ mkfifo pipe_out

2) Then connected pipe_in to pipe_out with the following GNU radio flowgraph:

enter image description here

File Source config:

  • Repeat: No
  • Vec Length: 1 (default setting)
  • Add begin tag: pmt.PMT_NIL (default setting)

File Sink config:

  • Unbuffered: Off
  • Vec Length: 1 (default setting)
  • Append file: Overwrite

3) Finaly, I start running the flowgraph, then write a string to pipe_in hoping to see it reach pipe_out by running the following two commands in separate terminals:

TERM2 $ tail -f pipe_out


TERM1 $ echo 'hello world!' > pipe_in

Unfortunately the string never reaches pipe_out. Can someone shed some light please?

  • $\begingroup$ Can you upload a higher resolution image? $\endgroup$ – rmagno Mar 11 at 11:59
  • $\begingroup$ @rmagno, unfortunately that is currently not possible, afaik. It's a GNU Radio limitation... $\endgroup$ – fmagno Mar 11 at 12:09
  • $\begingroup$ @rmagno are you and OP related? Yep, on GNU Radio 3.7, the GNU Radio Companion tool has a fixed rendering size, i.e. can't zoom (the picture would still be easier to read if it wasn't scaled up, but that's a different story) $\endgroup$ – Marcus Müller Mar 11 at 12:10
  • 1
    $\begingroup$ @gmagno yep! The current development version on git does exactly that. Also, Qt5 instead of Qt4 for visualization widgets, and Py3 instead of Python2 (optional), better build system, you know, stuff like that :) $\endgroup$ – Marcus Müller Mar 11 at 12:15
  • 1
    $\begingroup$ @rmagno an rmagno answering to an fmagno, I just liked that :) $\endgroup$ – Marcus Müller Mar 11 at 13:56

That's how tail works, it waits until the end to print the last n lines. If you use cat instead, it should work.

I hope it helps.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.