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
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 1, it will artificially inc
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
Marcus D. Leach wrote:
> You have nothing in your baudline directory, other than the usual "." and
".." housekeeping links.
Yeah,
I just created it myself as told in initial posting. I thought it was a
directory needed by the pipe.
Judging from Nate's suggestion i need to install an executable t
I just changed PYTHONPATH to python2.7. It was pointing to python3.4.
Didn't help, though :(
BR,
Nikos
On Wed, Mar 9, 2016 at 6:59 AM, Nikos Balkanas wrote:
> Hi Nate,
>
> I imagine you refer to baudline.py which is in the error trace.
>
> > baudline
> baudline: command not found
>
> For baud
On 03/08/2016 11:59 PM, Nikos Balkanas 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
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 shou
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/b
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 wrote:
>
> Hi Marcus,
>
> I imagine you mean the top_block.p
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 wrote:
> On 03/08/2016 11:10 PM, Nikos Balkanas wr
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
correctl
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
On Wed, Mar 9,
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 wrote:
>
> Hi Nate,
>
> Thank you for your fast reply. I tried your suggestions, but i seem to still
> get the same error:
>
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/baudli
Hi Nikos,
- You should use the UHD: USRP Source block with the x300, instead of the
Osmocom Source
- Try setting a higher sample rate to start with, 1e6 instead of 32e3
- You need to add the location of baudline to your $PATH variable, you can do
so by adding the line below to your ~/.bashrc fil
Hi,
This is my first attempt at gnuradio flows. I'm trying to run some of the
tutorials i have found around. I use Ubuntu 14.04 x64, gnuradio 3.7.1, usrp
x300 with latest uhd. I have a very simple flow with an Osmosdr Source
connected to a Baudline Sink. I get the following error on execurion:
UH
Hi,
This is my first attempt at using gnuradio flows with gnuradio-companion. I
am trying to run some flow tutorials i have found around.
I use Ubuntu 14.04 x64, with grc 3.7.1, X300 usrp and latest uhd. Using a
simple flow of an Osmosdr Source connected to a Baudline Sink I get the
following erro
17 matches
Mail list logo
