Re: [Discuss-gnuradio] [ Calculating the amplitude of a signal source ]

2012-12-17 Thread Marcus D. Leech

** (i)  How many *bytes* does each I or Q component take?





--
Ashish

For complex samples, the file-sink writes native, IEEE-754 
single-precision floating-point values into the file, with I and Q 
interleaved.


IEEE-754 single-precision is 32-bits, and is the native binary format 
used by most CPUs.




--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] New to list, trying portaudio under OpenBSD

2012-12-17 Thread Tom Rondeau
On Sat, Dec 15, 2012 at 12:15 AM, Alan Corey alan01...@gmail.com wrote:

 I've got my disabled list down to:
 --   * gr-comedi
 --   * gr-qtgui
 --   * gr-uhd
 --   * gr-shd
 --   * gr-fcd
 --   * gr-wxgui
 But mostly I've just been finding dependancies and installing them.

 I think I'm going to have to give up on gr-fcd because there seems to
 be some thread stuff in there that OpenBSD doesn't do.  OpenBSD's
 pthread.h is quite a bit different than Debian's pthread.h.  OpenBSD's
 had thread issues for a while.

 I found it does have Jack audio in ports so I don't need portaudio to work.

 I don't think I need fcd because my dongle isn't a Funcube but I think
 I do need either wxgui or qtgui to work.  I'm completely new to
 Gnuradio so I'm not sure what I need.

   Alan


Unless you want to prove that you can get all components working under
OpenBSD, you definitely don't need to stress about all of them. gr-comedi,
gr-fcd, gr-shd, and gr-uhd are specific to certain hardware systems. Just
focus on the ones you are actually interested in.

You'll probably want one of the GUI components, though. I prefer gr-qtgui,
but most of the GR apps and examples in the source code are based on
gr-wxgui, so that might be the one you want to focus on.

Tom



 On 12/14/12, Tom Rondeau t...@trondeau.com wrote:
  On Fri, Dec 14, 2012 at 1:54 AM, Alan Corey alan01...@gmail.com wrote:
 
  I'm working on installing gnuradio under OpenBSD, just got GRC
  working.  I have no audio, since gnuradio doesn't handle OpenBSD's
  native audio and it also doesn't recognize my existing portaudio
  which works with Audacity.
 
  I can set it up in my cmake cache but it still doesn't find it.  I'm
  running the standard OpenBSD port portaudio-svn-1406p1 built from
  sources.  I've had a little experience writing things in C that work
  with native audio but I don't know much about portaudio except it's
  working for other things like Fldigi.
 
  I see NetBSD has gnuradio-audio-portaudio which may be different than
  their normal portaudio but I don't find source for it, only binaries.
  OpenBSD audio is very similar to NetBSD's having borrowed a lot
  including audio manpages.
 
  I'll have other questions, right now I've also got no working gui.
  But I've only had my dongle since Monday.  It's an RTL2832 with a
  R820T tuner.  I'm trying to get some software for it working, I try
  Gnuradio, osmocom, sdr#, hdsdr in round robin fashion working on one
  until I hit a stopping point then on to another.  Osmocom's rtl_fm is
  the only thing even partly working so far.  I get little bursts of
  audio about 1 per minute.
 
Alan, ab1jx
 
  --
  Credit is the root of all evil.  - AB1JX
 
 
 
  Hi Alan,
  I can't really help you or give much advice to working on GNU Radio in
  OpenBSD. But I if you make progress in getting things set up, please help
  us by updating the wiki's notes for building. And if there are specific
  issues that can be addressed by patches to the build system, please send
  them along (by using the Issues tracker on gnuradio.org).
 
  Tom
 


 --
 Credit is the root of all evil.  - AB1JX

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] QT GUI FFTSINK in C++ Flowgraph

2012-12-17 Thread Tom Rondeau
On Sun, Dec 16, 2012 at 5:23 PM, Daniel Labarowski
labarowsk...@gmail.comwrote:

  I've been toying around with this a bit more. I added #include
 QWidget to the top of my program. I also added QWidget* parent = new
 QWidget; before my call to qtgui_make_sink_c and replaced QWidget
 *parent=NULL white parent. I am now getting the following error

 top_block.cc:(.text+0x8cd): undefined reference to
 `QWidget::QWidget(QWidget*, QFlagsQt::WindowType)'
 top_block.cc:(.text+0x94f): undefined reference to `qtgui_make_sink_c(int,
 int, double, double, std::basic_stringchar, std::char_traitschar,
 std::allocatorchar  const, bool, bool, bool, bool, QWidget*)'


 I've double checked what little documentation I can find on
 qtgui_make_sink_c and I think that I am passing appropriate parameters. Any
 thoughts on what might be wrong?

 -Dan


This suggests that you are not linking against libgnuradio-qtgui.so. Make
sure you are (-lgnuradio-qtgui should be used when linking).

You probably also want to use NULL for the parent. As it is now, you're
using an empty QWidget, and I'm not sure what will happen with that, but it
probably won't work as expected.

From your first email, it looks like you are passing QWiget* parent=NULL
as the last parameter. Just say NULL here, instead.

I've never tried to use QTGUI in C++ apps, so I'm curious to know if you
can get it to work.

Tom





 On 12/15/2012 02:07 AM, Daniel Labarowski wrote:

 Hello,
 I am attempting to use qt gui widgets in a C++ flowgraph. I managed to get
 all of the build dependencies figured out, which was no easy task in itself
 and required a lot of direct includes. Anyway, the error that I am getting
 now deals directly with the make function. The line that is giving me
 trouble is as follows

 qtgui_sink_c_sptr qtsink = qtgui_make_sink_c (fftsize,
 gr_firdes::WIN_HAMMING, 0, 1.0, Spectrum Display, true, true, true, true,
 QWidget *parent=NULL);


 Information on this function is available 
 here.http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsQTGUIThe 
 error that I am getting is that parent is undefined. I really don’t
 know what to put for this. Note that I have also tried putting just NULL or
 just 0 and it throws an undefined reference error (for the function call).
 I was wondering if someone could give me some pointers on what to use for
 parent? While I would eventually like to have both an fft and a time domain
 view in a single window, I am currently just trying to get the fft to show
 in its own window. Thanks ahead of time!

 -Dan



 ___
 Discuss-gnuradio mailing list
 Discuss-gnuradio@gnu.org
 https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] QT GUI FFTSINK in C++ Flowgraph

2012-12-17 Thread Marcus D. Leech
I've never tried to use QTGUI in C++ apps, so I'm curious to know if 
you can get it to work.


Tom

I believe that gqrx is an instance of an app that uses both QtGUI, and 
Gnu Radio, and is largely written in C++, and is open source.  Valuable

  hints might be gleaned by looking at that source code.


--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] QT GUI FFTSINK in C++ Flowgraph

2012-12-17 Thread Alexandru Csete
On Mon, Dec 17, 2012 at 4:47 PM, Marcus D. Leech mle...@ripnet.com wrote:
 I've never tried to use QTGUI in C++ apps, so I'm curious to know if you
 can get it to work.

 Tom

 I believe that gqrx is an instance of an app that uses both QtGUI, and Gnu
 Radio, and is largely written in C++, and is open source.  Valuable
   hints might be gleaned by looking at that source code.


Hi Marcus,

The initial gqrx was a python application that used gr-qtgui. Since
then I have started from scratch and created a new application using
C++ and Qt for gui but not the gr-qtgui component.

Alex

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] FSK performance as a function of Fd?

2012-12-17 Thread Joanna Rutkowska
On 12/17/12 06:13, Matt Ettus wrote:
 On Sun, Dec 16, 2012 at 2:27 PM, Joanna Rutkowska 
 joa...@invisiblethingslab.com wrote:
 

 This is an FSK receiver from Atmel. Even though it apparently supports
 only data rates between 1-20 kbps, its supported Fd is within a range of
 18kHz-50kHz. This seems to contradict your theory above -- why would
 Atmel use such a wide bandwith if they could just use no more than 20kHz
 for 20kbps?

 
 
 Joanna,
 
 
 Increasing deviation beyond the deviation of MSK (i.e. the minimum) does
 not help performance, but it can help ease receiver design.
 
 The reason to use a very high deviation at a low data rate is to make it
 easier to deal with frequency error with low cost crystals.  If you have
 low cost 50ppm crystals on both ends, you could have 100 ppm total error.
  100 ppm at 450 MHz is 45kHz.  Spreading the 2 tones further apart allows
 you to guarantee that one will always have positive deviation and the other
 will have negative deviation.
 
 The FSK demodulation method with 2 filters is almost never used.  This chip
 likely uses either direct frequency measurement (derivative of phase) or a
 PLL.
 
 Matt
 


Thanks Matt. This makes sense.

joanna.




signature.asc
Description: OpenPGP digital signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] hiiii gudmng fnds,

2012-12-17 Thread sivakumar reddy
Hi all,

I have recorded a sinusoidal USRP signal (generated by a vector signal
generator) in its complex form in a file_sink. I understand that the
file_sink will have the I-Q data of the signal.

Can anyone tell me in what format that I-Q data will be stored i.e
(i)  How many bites does each I or Q component take?
(ii) What will be their pattern in the file_sink i.e whether they would be
in (I1, Q1, I2, Q2 ... Ik, Qk) form OR (I1, Q1, I1, Q1, I2, Q2, I2, Q2 ..)
sequence OR any other sequence?

My purpose is to parse the I-Q data from the file_sink.

Have attached the WX_GUI_Sink plot of the signal received in complex form
(in GRC).
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] gr-howto-write-a-block build fails

2012-12-17 Thread Tommy Tracy II
Dear List,

I'm looking to write c++ gnuradio blocks using the 
gr-howto-write-a-block code that comes with gnuradio.  Unfortunately, when I do 
the build with the existing code, the tests fail. Has anyone else seen this?
I'm running Ubuntu 12.10.

--
ttracy@ubuntu:~/Documents/src/gnuradio/gr-howto-write-a-block/build$ sudo cmake 
../
-- The CXX compiler identification is GNU 4.7.2
-- The C compiler identification is GNU 4.7.2
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Build type not specified: defaulting to release.
-- Boost version: 1.49.0
-- Found PkgConfig: /usr/bin/pkg-config (found version 0.26) 
-- checking for module 'gruel'
--   found gruel, version 3.6.3git
-- Found GRUEL: /usr/local/lib/libgruel.so  
-- checking for module 'gnuradio-core'
--   found gnuradio-core, version 3.6.3git
-- Found GNURADIO_CORE: /usr/local/lib/libgnuradio-core.so  
-- Boost version: 1.49.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Found SWIG: /usr/bin/swig2.0 (found version 2.0.7) 
-- Found PythonLibs: /usr/lib/python3.2/config/libpython3.2.so (found version 
2.7.3) 
-- Found PythonInterp: /usr/bin/python (found version 2.7.3) 
-- Found Doxygen: /usr/bin/doxygen (found version 1.8.1.2) 
-- Configuring done
-- Generating done
-- Build files have been written to: 
/home/ttracy/Documents/src/gnuradio/gr-howto-write-a-block/build
ttracy@ubuntu:~/Documents/src/gnuradio/gr-howto-write-a-block/build$ sudo make
Scanning dependencies of target gnuradio-howto
[  5%] Building CXX object 
lib/CMakeFiles/gnuradio-howto.dir/howto_square_ff.cc.o
[ 10%] Building CXX object 
lib/CMakeFiles/gnuradio-howto.dir/howto_square2_ff.cc.o
Linking CXX shared library libgnuradio-howto.so
[ 10%] Built target gnuradio-howto
Scanning dependencies of target qa_howto_square2_ff
[ 15%] Building CXX object 
lib/CMakeFiles/qa_howto_square2_ff.dir/qa_howto_square2_ff.cc.o
Linking CXX executable qa_howto_square2_ff
[ 15%] Built target qa_howto_square2_ff
Scanning dependencies of target qa_howto_square_ff
[ 20%] Building CXX object 
lib/CMakeFiles/qa_howto_square_ff.dir/qa_howto_square_ff.cc.o
Linking CXX executable qa_howto_square_ff
[ 20%] Built target qa_howto_square_ff
Scanning dependencies of target _howto_swig_swig_tag
[ 25%] Building CXX object 
swig/CMakeFiles/_howto_swig_swig_tag.dir/_howto_swig_swig_tag.cpp.o
Linking CXX executable _howto_swig_swig_tag
[ 25%] Built target _howto_swig_swig_tag
Scanning dependencies of target _howto_swig_doc_tag
[ 30%] Building CXX object 
swig/CMakeFiles/_howto_swig_doc_tag.dir/_howto_swig_doc_tag.cpp.o
Linking CXX executable _howto_swig_doc_tag
[ 30%] Built target _howto_swig_doc_tag
[ 35%] Generating doxygen xml for howto_swig_doc docs
[ 40%] Generating howto_swig_doc.i
[ 45%] Generating howto_swig.tag
[ 50%] Swig source
Scanning dependencies of target _howto_swig
[ 55%] Building CXX object 
swig/CMakeFiles/_howto_swig.dir/howto_swigPYTHON_wrap.cxx.o
Linking CXX shared module _howto_swig.so
[ 55%] Built target _howto_swig
Scanning dependencies of target pygen_swig_cc723
[ 60%] Generating howto_swig.pyc
[ 65%] Generating howto_swig.pyo
[ 85%] Built target pygen_swig_cc723
Scanning dependencies of target pygen_python_257bc
[ 90%] Generating __init__.pyc
[ 95%] Generating __init__.pyo
[ 95%] Built target pygen_python_257bc
Scanning dependencies of target pygen_apps_58acf
[100%] Shebangin howto_square.py
[100%] Built target pygen_apps_58acf
ttracy@ubuntu:~/Documents/src/gnuradio/gr-howto-write-a-block/build$ sudo make 
test
Running tests...
Test project /home/ttracy/Documents/src/gnuradio/gr-howto-write-a-block/build
Start 1: qa_howto_square_ff
1/3 Test #1: qa_howto_square_ff ...   Passed0.01 sec
Start 2: qa_howto_square2_ff
2/3 Test #2: qa_howto_square2_ff ..   Passed0.01 sec
Start 3: qa_howto
3/3 Test #3: qa_howto .***Failed0.14 sec

67% tests passed, 1 tests failed out of 3

Total Test time (real) =   0.15 sec

The following tests FAILED:
  3 - qa_howto (Failed)
Errors while running CTest
make: *** [test] Error 8
--


   Sincerely,
  Tommy James Tracy II
  PhD Student
High Performance Low Power Lab 
   University of Virginia

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio