There is the "WX DOA Compass" in gr-baz
https://github.com/balint256/gr-baz
https://github.com/balint256/gr-baz/blob/master/grc/doa_compass.xml
-- Nate
> On Jun 15, 2016, at 10:44 AM, Philip Balister wrote:
>
> On 06/15/2016 01:06 PM, Nick Foster wrote:
>> You ought to
I noticed that my Python unit tests were running twice. Using PyCharm's
debugger I was able to figure out that the culprit is the following snippet
from gr_unittest.py:
# use the xmlrunner if we can write the the directory
if(xmlrunner is not None):
xmlrunner.run(suite)
main()
The primary design decision was to use the FFT filter instead of the
interpolating FIR filter for performance. The FFT filter is considerably
faster, especially at the 100 taps used in the flow graph. However, (as
far as I know) the FFT filter does not have an interpolation option,
just
Ok I will try that. Just for your information, throttle or not, it works in
both cases on the Nutaq Zepto
Le 2016-06-15 17:15, "Nick Foster" a écrit :
> One clue for you is already being printed out for you in the TX flowgraph
> image. Get rid of the throttle block.
>
> The
Hi to all! Specially to Ron Economos! (and thanks for sharing your work)
I was trying to understand the example *dvbs2_tx.grc* and, after putting
graphical sinks after many blocks, I noticed that the one called "Physical
Frame Layer" outputs one complex zero after each constellation point (see
One clue for you is already being printed out for you in the TX flowgraph
image. Get rid of the throttle block.
The RX time domain plot looks actually pretty healthy. It's showing a
frequency offset, which is normal for unsynchronized devices.
The constellation plot needs to happen after timing
I'm giving a copy of the email I just sent to Ettus Research. I think that
it's been a hardware problem since the beginning but i'm waiting for their
response.
Check it out, maybe some of view have already seen this kind of bug
On 15 June 2016 at 20:17, Andrew Back wrote:
> Hi All,
>
> Apologies to those who may have already seen this, but just wanted to
> share details of a new low cost SDR hardware platform that is
> currently crowdfunding, the LimeSDR. Main specifications are as
> follows:
>
Hi All,
Apologies to those who may have already seen this, but just wanted to
share details of a new low cost SDR hardware platform that is
currently crowdfunding, the LimeSDR. Main specifications are as
follows:
* 100kHz-3.8GHz 2x2 MIMO (LMS7002M)
* Bandwidth: 61.44 MHz
* Power Output (CW): up
Hi Avinash,
when you attach a "tag debug" after the "ofdm channel estimation" block,
you'll see stream tags containing CSI estimates flying by.
For more information on stream tags and how to handle them, I'd refer
you to the Guided Tutorials [1], chapter 1-5.
Best regards,
Marcus
[1]
Ah rookie mistake on my part!
I went ahead and made the sample rates consistent (40.96k) across the
schematic and an interesting thing happened.
So I set these parameters:
frequency to recover: 100Hz
fft size: 4096
sample rate: 40.96k Sps
to have a nice FFT bin number at 10
The interesting thing
Hi Olivier,
what does this mean:
> The 1st file contains only '1' and the other only '0'.
How did you generate these files. Without knowing better, I'd say this
is a case for our File Format FAQ:
On 06/15/2016 01:06 PM, Nick Foster wrote:
> You ought to be able to use PyQwt's compass widget:
Qwt is OK, but please do not use PyQwt. It is unmaintained. See:
https://sourceforge.net/p/pyqwt/mailman/message/30352623/
Philip
>
> http://qwt.sourceforge.net/class_qwt_compass.html
>
> I used
You ought to be able to use PyQwt's compass widget:
http://qwt.sourceforge.net/class_qwt_compass.html
I used it for gr-air-modes and, while ugly, it does work. There's no
integration into GRC so the Python to integrate the widget will, of course,
be your responsibility.
--n
On Wed, Jun 15,
Meny,
no, we don't. A compass was one of the suggestions for this year's GSoC,
but no one signed up for that.
M
On 06/15/2016 04:34 AM, Meny Sidar wrote:
> Hi guys
>
> I'm looking for a nice GUI that can plot my AoA calculations in a some
> kind of a compass looking GUI.
> Does anything like
Or try this:
tr = uhd.tune_request(900e6, 0)
tb.usrp.set_center_freq(tr)
tr = uhd.tune_request(901e6, -1e6)
tb.usrp.set_center_freq(tr)
M
On 06/14/2016 07:47 PM, Marcus D. Leech wrote:
> On 06/14/2016 09:39 PM, Richard Bell wrote:
>> I think I have a misunderstanding about the DSP tune,
Hello all,
Could you please let me know how I can get channel-frequency response (like
channel state information (CSI) ) for an OFDM transmission? I am looking at
rx_ofdm.grc to capture the phase and amplitude at each of the 64
sub-carriers.
Would connecting the OFDM Channel Estimation Block of
Apologies for the double mail. I had accidentally sent the previous
response, even before compiling the complete mail.
That said, I am working on finishing the gui part and integration with
the pybombs API by this weekend, before the mid-term evaluation
period.
[1]
Hi Ben,
Thanks for the feedback.
1. I have created a new repo for the Pybombs frontend on Gitlab [1]
recently. During my weekly interaction sessions with Martin, we have
decided to make the gui-frontend installable from pybombs-cli itself.
Initially, I had plans on integrating the gui-frontend
Hey Wayne,
You are right, a check would be good. The same issue can occur for variable
blocks.
Thanks,
Sebastian
Sent from BlueMail
On Jun 14, 2016, 15:28, at 15:28, Wayne Roberts wrote:
>It would seem that the ID entered into options block of gnuradio
>companion
Hi guys
I'm looking for a nice GUI that can plot my AoA calculations in a some kind
of a compass looking GUI.
Does anything like that exists? or do i have to build one of my own?
Don't really know how, and would prefer not to start learning Python right
now (on a deadline).
Any help would be
21 matches
Mail list logo