Hi Philip,
Converting real valued signal to I-Q is a simple transformation:
1. Pick an LO frequency, F_lo, greater than 200Hz, the signal bandwidth
2. Pick a sample interval, deltaT, smaller than 1/(2*F_lo)
3. Generate I-Q digital local oscillator signal: [cos(2*pi*F_lo*i*deltaT),
Hi Ivo,
The binary format depends on what you have set as the "Input Type" in the file
sink. The default is "Complex" in which case the values are 32-bit float I
followed by 32-bit float Q. The order of the 4-bytes in the float likely
depends on the endianness of your host system.
--Patrick
You can look at usrp_spectrum_sense script. This sweeps a specified frequency
range, does an FFT, and outputs one line for every bin where the magnitude
exceeds a specified limit.
You could modify it to just write the samples to a file/pipe like uhd_rx_cfile.
--Patrick
Try this instead:
const std::vector inputs{4000,4000,4000,4000,4000,4000,4000,4000};
and make sure you compile with c++11 enabled.
--Patrick
From: Discuss-gnuradio on
behalf of Ali <03do...@gmail.com>
Sent:
ps.google.com
Posted 7/15/12 10:52 AM, 25 messages
--Patrick
From: Discuss-gnuradio <discuss-gnuradio-bounces+wpats=hotmail....@gnu.org> on
behalf of Patrick Sathyanathan <wp...@hotmail.com>
Sent: Thursday, June 1, 2017 11:22 PM
To: discuss-
--Patrick
____
From: Patrick Sathyanathan <wp...@hotmail.com>
Sent: Thursday, June 1, 2017 6:41 PM
To: kazunori miura
Subject: Re: Fw: ORDER: RTL-SDR Soft66Q 3kHz to 1.7GHz RTL2832U with RF anp 4
band filter R820T2, VLF
Thanks, Kazunori. The device works very w
nesday, March 15, 2017 5:20 PM
To: Patrick Sathyanathan
Cc: Marcus Müller; GNURadio Discussion List
Subject: Re: [Discuss-gnuradio] Global namespace Errors with Complex and xlocNum
Hey Patrick,
That is correct, is the current version wrong or causing incompatibility issues?
Should be noted im a novic
Hi Melvin,
>From the error message it appears you are using version 14.10.25017 headers
>with MSVC17. Why is this ? Were these part of the MSVC17 distribution ?
c:\program files (x86)\microsoft visual
studio\2017\community\vc\tools\msvc\14.10.25017\include
--Patrick
Hi Marc,
You could take a look at osmocom_spectrum_sense which is part of the gr-osmosdr
package. It does exactly what you seem to want to do. Running it with "--help"
lists the command line options. It is a python script so should be relatively
easy to figure out.
--Patrick
Try running "nm -u -C libgnuradio-ins_blocks.so" and search for any class
methods that are supposed to be defined in the module.
--Patrick
Date: Wed, 1 Jun 2016 12:01:04 -0700
From: richard.be...@gmail.com
To: discuss-gnuradio@gnu.org
Subject: [Discuss-gnuradio] OOT Module Issue
Hi,
This is
>From the log below it may be because SWIG version check failed:
> -- Disabling SWIG because version check failed
and
> -- Configuring python-support support...
> -- Dependency PYTHONLIBS_FOUND = TRUE
> -- Dependency SWIG_FOUND = FALSE
> -- Dependency SWIG_VERSION_CHECK = FALSE
> --
Any suggestions ?
Thanks,
--Patrick
From: wp...@hotmail.com
To: discuss-gnuradio@gnu.org
Date: Wed, 30 Mar 2016 00:03:10 -0700
Subject: [Discuss-gnuradio] Setting cmake variable with pyBOMBS
Hi,
I installed gnuradio and gr-osmosdr using the latest pyBOMBS from source.
However none of
Hi,
I installed gnuradio and gr-osmosdr using the latest pyBOMBS from source.
However none of the hardware directories got configured with
-DINSTALL_UDEV_RULES=ON. Is there a pybombs config command that I can use to
set this cmake option globally ? I do not want to cd into each of the build
Sorry, typo "...as Marcus D. Leech points out..."
--Patrick
From: wp...@hotmail.com
To: rfeng...@me.com; discuss-gnuradio@gnu.org; hup...@gmail.com
Date: Wed, 16 Mar 2016 20:44:23 -0700
Subject: Re: [Discuss-gnuradio] dive into gnu-radio
Hi Desmond,
I have a similar CS background
Hi Desmond,
I have a similar CS background combined with a youthful interest in radios from
the distant past. I initially approached GNUradio with a similar attitude, i.e.
it's just software, I can figure out what it does. But sadly that is not true,
and as Martin Leech points out in a
Hi Michael,
To get GNUradio to build correctly from source on the RPi2 you need to do a
couple of things:
1. Increase the swap space on the device
2. Build single threaded (make -j 1)
3. Make a source fix in one of the volk ARM asm files. Did you run into this
error when you tried your build
connection of spyverter damage it ?
To: wp...@hotmail.com
CC: discuss-gnuradio@gnu.org
It it quite possible that you damaged it. You should contact the airspy folks
to be sure though - http://airspy.com/contact/
On Tue, Dec 15, 2015 at 4:18 PM, Patrick Sathyanathan <wp...@hotmail.com> wrote:
Hi,
I recently purchased the airspy/spyverter combo. The spyverter did not have any
markings indicating antenna input and output. Assuming that the lettering on
the top of the two devices lined up I initially wrongly connected the antenna
input of spyverter to the input of the airspy and ran
gt; On Mon, Oct 26, 2015 at 6:10 PM, Patrick Sathyanathan
> <wp...@hotmail.com<mailto:wp...@hotmail.com>> wrote:
> Hi,
>
>
> I managed to build gnuradio from source using pybombs on a raspberry pi
> 2 machine running raspbian. It took many tries and the build
Hi,
I managed to build gnuradio from source using pybombs on a raspberry pi 2
machine running raspbian. It took many tries and the build itself took a day
and only worked after increasing the swapfile size to 2GB.
I am able to run osmocom_fft at 2.4Msps sample rate with an rtl-sdr dongle
Hi David,
Making the parameter vary at runtime is simple and just needs some extra XML
and python code. The parameter should be an argument to the __init__ method
(constructor) of your block and should have a "" declaration in the matching
XML file. Let's say the parameter name is
Attaching reply as text since outlook.com insists on eating XML and formatting.
--Patrick
> From: mcqui...@sfu.ca
> Date: Thu, 24 Sep 2015 10:35:34 -0700
> To: david.ha...@toshiba-trel.com
> CC: discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio]
Retrying in plain text, since browser/outlook ate the XML I had typed:
Hi David,
Making the parameter vary at runtime is simple and just needs some extra XML
and python code.
The parameter should be an argument to the __init__ method (constructor) of
your block and should
have a ""
(Electromagnetics)
On Wed, Aug 19, 2015 at 5:06 PM, Patrick Sathyanathan wp...@hotmail.com wrote:
Hi Logan,
I have faced the same error twice recently in my OOT module and finally tracked
it down to two causes. The basic reason for the 'object has no attribute' error
is that Python's import of your module
Hi Logan,
I have faced the same error twice recently in my OOT module and finally tracked
it down to two causes. The basic reason for the 'object has no attribute' error
is that Python's import of your module failed. In the two cases that I saw it
was due to undefined symbols in the shared
Hi,
This device is marketed as a Real Time Spectrum Analyzer but can also function
as a general purpose SDR. Is there GNUradio support for this device ?
Or is any source block under development ? Any info appreciated...
--Patrick
++ blocks is that people add public methods to
their _impl, but forget to declare these same methods in their public
non-impl class.
Have you done the same expand magic with the header in your
include/CMakeLists.txt?
Best regards,
Marcus
On 07/06/2015 04:09 AM, Patrick Sathyanathan wrote
Hi,
I have worked my way through the Guided Tutorials on gnuradio.org. I have
written OOT blocks in Python and managed to expose some set methods in the
block as callbacks. Now I have written an OOT C++ block sweeper_cpp_f and I
want to expose a couple of setter methods in my block's class as
28 matches
Mail list logo