Re: [Discuss-gnuradio] Companion flow error

[Nikos Balkanas]

Hi Nate,

Baudline was my first software spectrum analyzer, 2 yrs ago, until gr-fosphor came out and I switched. Used it close to a year. Right now I'm building gnuradio 3.7.9.1 since 3.7.6.1 has a few blocks missing. Then i plan to continue with my RFNoC work, while Xilinx evaluation licenses are still valid. I'm not really interested in baudline anymore, but will play with the apperture and Const block when gnuradio installation finishes :)

BR,

Nikos

On Wed, Mar 9, 2016 at 8:36 AM, Nate Temple <address@hidden> wrote:

Hi Nikos,

Glad to hear that it is working. As far as it displaying a black screen, that is because baudline isn't representing enough dynamic range for the USRP. A little trick, if you add a Multi Const block before the baudline sink, and enter a value of 1000 or 10000, it will artificially increase the signal magnitude to where baudline will display.

You can also adjust the Color Aperture [1] , which may or may not help.

[1] http://www.baudline.com/manual/color_picker.html#color_aperture

- Nate

> On Mar 8, 2016, at 9:45 PM, Nikos Balkanas <address@hidden> wrote:
>
> That did it.
>
> Thank you all very much. I didn't get any real spectrum out of it, just a black screen, but at least i know that my companion flow setup works:)
> I prefer gr-fosphor to baudline:)
> I hope that other blocks include more documentation (baudline sink has none), and that error messages are more specific (i.e. filename in missing file error)
>
> BR,
> Nikos
>
> On Wed, Mar 9, 2016 at 7:08 AM, Nate Temple <address@hidden> wrote:
> Hi Nikos,
>
> You need the baudline binary which is here [1]. It will unpack to the folder baudline_1.08_linux_x86_64/. Put the contents in the folder baudline_1.08_linux_x86_64/ in your home directory. You should then be able to call the command "baudline" and if that works, the GR sink block should work.
>
> [1] - http://www.baudline.com/baudline_1.08_linux_x86_64.tar.gz
>
>
> - Nate
>
>
> > On Mar 8, 2016, at 8:59 PM, Nikos Balkanas <address@hidden> wrote:
> >
> > Hi Nate,
> >
> > I imagine you refer to baudline.py which is in the error trace.
> >
> > > baudline
> > baudline: command not found
> >
> > For baudline.py to run, I would have to have /usr/local/lib/python2.7/... part of my PATH, which i don't.
> >
> > > echo $PATH
> > /opt/AMDAPPSDK-3.0:/opt/AMD/CodeXL:/home/nikos/bin:/home/nikos/baudline_1.08_linux_x86_64:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:.
> > Is this smt i should add to my PATH?
> >
> > > ls -la baudline_1.08_linux_x86_64
> > total 8
> > drwxrwxr-x 2 nikos nikos 4096 Mar 9 04:31 .
> > drwxr-xr-x 54 nikos nikos 4096 Mar 9 06:52 ..
> >
> > BR,
> > Nikos
> >
> > On Wed, Mar 9, 2016 at 6:51 AM, Nate Temple <address@hidden> wrote:
> > Hi Nikos,
> >
> > Does baudline start if you just run the command "baudline" from the terminal?
> >
> > Can you send the output of this command:
> >
> > ls -al /home/nikos/baudline_1.08_linux_x86_64 ​
> >
> >
> > - Nate
> >
> >
> > > On Mar 8, 2016, at 8:33 PM, Nikos Balkanas <address@hidden> wrote:
> > >
> > > Hi Marcus,
> > >
> > > I imagine you mean the top_block.py generated by the flow.
> > >
> > > The output is much longer, includes all x300 initialization sequences, but eventually I get the same error as before:(
> > >
> > > Nikos
> > >
> > > On Wed, Mar 9, 2016 at 6:22 AM, Marcus D. Leech <address@hidden> wrote:
> > > On 03/08/2016 11:10 PM, Nikos Balkanas wrote:
> > >> Hi Nate,
> > >>
> > >> Not really. I added line to .profile (that's where I maintain PATH) and reexported PATH with the new value, b4 starting the companion. It shouldn't make a difference.
> > >> I then rebooted my PC, just to make sure that PATH was updated correctly, same error as before.
> > >>
> > >> BR,
> > >> Nikos
> > > If you just try to execute the generated .py file, from a window that apparently has correct PATH, what happens?
> > >
> > >
> > >>
> > >> On Wed, Mar 9, 2016 at 5:45 AM, Nate Temple <address@hidden> wrote:
> > >> Hi Nikos,
> > >>
> > >> Did you restart gnuradio-companion from a new terminal after adding the line to your ~/.bashrc file?
> > >>
> > >>
> > >> - Nate
> > >>
> > >>
> > >> > On Mar 8, 2016, at 7:09 PM, Nikos Balkanas <address@hidden> wrote:
> > >> >
> > >> > ​Hi Nate,
> > >> >
> > >> > Thank you for your fast reply. I tried your suggestions, but i seem to still get the same error:
> > >> >
> > >> > > echo $PATH
> > >> > /opt/AMDAPPSDK-3.0:/opt/AMD/CodeXL:/home/nikos/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:.:/home/nikos/baud:/home/nikos/baudline_1.08_linux_x86_64 ​
> > >> >
> > >> > > ls -ld baud*
> > >> > drwxrwxr-x 2 nikos nikos 4096 Mar 9 04:31 baudline_1.08_linux_x86_64
> > >> >
> > >> > >['baudline', '-stdin', '-record', '-spacebar', 'recordpause', '-samplerate', '40000000', '-channels', '2', '-format', 'le32f', '-quadrature', '-basefrequency', '2100000000.0']
> > >> > [Errno 2] No such file or directory
> > >> > Traceback (most recent call last):
> > >> > File "/home/nikos/Desktop/top_block.py", line 116, in <module>
> > >> > tb = top_block()
> > >> > File "/home/nikos/Desktop/top_block.py", line 84, in __init__
> > >> > **{})
> > >> > File "/usr/local/lib/python2.7/dist-packages/baz/baudline.py", line 146, in __init__
> > >> > self.p = subprocess.Popen(baudline_exec, stdin=subprocess.PIPE)       # , stdout=subprocess.PIPE, stderr=subprocess.PIPE, bufsize=16384 or -1
> > >> > File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
> > >> > errread, errwrite)
> > >> > File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
> > >> > raise child_exception
> > >> > OSError: [Errno 2] No such file or directory
> > >> >
> > >> > >>> Done
> > >> >
> > >> > Attaching new flowgraph and top_block.py.
> > >> >
> > >> > BR
> > >> > Nikos
> > >> >
> > >> >
> > >> >
> > >> > <Tutorial.grc><top_block.py>
> > >>
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> Discuss-gnuradio mailing list
> > >>
> > >> address@hidden
> > >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > >
> > >
> > > _______________________________________________
> > > Discuss-gnuradio mailing list
> > > address@hidden
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > >
> > >
> > > _______________________________________________
> > > Discuss-gnuradio mailing list
> > > address@hidden
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
> >
>
>