Hello!
I’m trying to play a bit with gnuradio and a funcube dongle pro but I’m
having problems making gnuradio work. I’m using a fresh ubuntu 11.04
install and gnuradio 3.4.0 built from sources.
Everytime a fft display is used, I get the same error. For example,
using FunCube Dongle Pro example:
eoz@waterhole:~$ FCDongle/gr-fcd/apps/fcd_fft_wx.py
Traceback (most recent call last):
File
“/usr/local/lib/python2.7/dist-packages/gnuradio/wxgui/plotter/plotter_base.py”,
line 158, in _on_paint
GL.glClearColor(*BACKGROUND_COLOR_SPEC)
File “/usr/lib/pymodules/python2.7/OpenGL/error.py”, line 208, in
glCheckError
baseOperation = baseOperation,
OpenGL.error.GLError: GLError(
err = 1280,
baseOperation = glClearColor,
cArguments = (1, 0.976, 1, 1)
)
And testing this little GUI example from
http://www.funwithelectronics.com/?id=10
eoz@waterhole:~./simplegui.py
Traceback (most recent call last):
File
“/usr/local/lib/python2.7/dist-packages/gnuradio/wxgui/plotter/plotter_base.py”,
line 158, in _on_paint
GL.glClearColor(*BACKGROUND_COLOR_SPEC)
File “/usr/lib/pymodules/python2.7/OpenGL/error.py”, line 208, in
glCheckError
baseOperation = baseOperation,
OpenGL.error.GLError: GLError(
err = 1280,
baseOperation = glClearColor,
cArguments = (1, 0.976, 1, 1)
)
And so on… Any ideas? I’m totally lost.
Thank you in advance!
Miguel A. Vallejo, ea4eoz
if you cd to /usr/local/bin and then plug for example
./usrp_fft.py -R A -f 435e6
If the above doesnt work, then reconsider
Patrik
----- Original Message -----
From: “Miguel A. Vallejo, EA4EOZ” [email protected]
To: [email protected]
Sent: Monday, July 18, 2011 3:47
Subject: [Discuss-gnuradio] plotter_base.py problem
Patrik T. wrote:
if you cd to /usr/local/bin and then plug for example
./usrp_fft.py -R A -f 435e6
If the above doesnt work, then reconsider
Patrik
No, it does not work because I don’t have any USRP hardware. Only
funcube dongle and the usual sound card.
Miguel A. Vallejo, ea4eoz
On 07/18/2011 06:16 AM, Miguel A. Vallejo, EA4EOZ wrote:
funcube dongle and the usual sound card.
Miguel A. Vallejo, ea4eoz
It sounds like perhaps one of your pre-requisites isn’t installed
properly on your Ubuntu system,
possible OpenGL or py-opengl, or one of those.
You might consider using the build-gnuradio script to
fetch/build/install everything, including
the pre-requisites:
http://www.sbrac.org/files/build-gnuradio
–
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
On 07/17/2011 08:47 PM, Miguel A. Vallejo, EA4EOZ wrote:
err = 1280,
Traceback (most recent call last):
cArguments = (1, 0.976, 1, 1)
)
Just on a hunch, try:
export LIBGL_ALWAYS_INDIRECT=1
Before you start any of the above applications.
OpenGL has, in my opinion, become a festering sore of incompatibilities
and weird edge conditions. It used to work reliably on just about
anything, but not anymore. Newer version of OpenGL require various
extensions in your display hardware, and will fail in weird ways
if your display hardware doesn’t have what it expects. The above
environment variable is supposed to instruct OpenGL to use
software-based
rendering and ignore the hardware. For the simple 2-D stuff we do in
Gnu Radio, Software-Based rendering is just fine.
–
Marcus L.
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
Marcus D. Leech wrote:
Just on a hunch, try:
export LIBGL_ALWAYS_INDIRECT=1
Before you start any of the above applications.
Yes!, It works!
OpenGL has, in my opinion, become a festering sore of incompatibilities
and weird edge conditions. It used to work reliably on just about
anything, but not anymore. Newer version of OpenGL require various
extensions in your display hardware, and will fail in weird ways
if your display hardware doesn’t have what it expects. The above
environment variable is supposed to instruct OpenGL to use software-based
rendering and ignore the hardware. For the simple 2-D stuff we do in
Gnu Radio, Software-Based rendering is just fine.
Completely agree. Why use a monster like OpenGL to make simple 2D
graphics?
Thnak you for your tip.
Try,
./usrp_nbfm_rcv.py -R A -f 435.3e6 -O plughw:0,0
The -O switch tells which audio device to use.
Patrik
----- Original Message -----
From: “Patrik T.” [email protected]
To: [email protected]
Sent: Monday, July 18, 2011 5:01
Subject: Re: [Discuss-gnuradio] plotter_base.py problem
On 07/19/2011 08:50 AM, Miguel A. Vallejo, EA4EOZ wrote:
OpenGL has, in my opinion, become a festering sore of incompatibilities
and weird edge conditions. It used to work reliably on just about
anything, but not anymore. Newer version of OpenGL require various
extensions in your display hardware, and will fail in weird ways
if your display hardware doesn’t have what it expects. The above
environment variable is supposed to instruct OpenGL to use software-based
rendering and ignore the hardware. For the simple 2-D stuff we do in
Gnu Radio, Software-Based rendering is just fine.
Completely agree. Why use a monster like OpenGL to make simple 2D graphics?
I’d love to see gnuradio lose the opengl requirement. I makes things a
nuisance getting the qt stuff built on the E100 also.
Philip
On 19/07/2011 8:50 AM, Miguel A. Vallejo, EA4EOZ wrote:
Completely agree. Why use a monster like OpenGL to make simple 2D
graphics?
Gnu Radio swallowed the OpenGL monster “by proxy” when we opted to use
WxPython, and the plotting/graphing widgets
in WxPython happen to use OpenGL for rendering.
The Qt stuff that is being worked on uses a different rendering
machinery, I believe, so once it’s fleshed out and made at least as
functional as the WxPython stuff we use, then perhaps we won’t run
into weird OpenGL rendering issues anymore.