I see that GRC had an "embedded python" block. I'd like to take a
np.complex64 input, process it in Python, and return a np.float64. When I
try to modify the python code to do this I get the error:
Param - Code(_source_code):
> Can't map dtype('float64') to GRC port type
>
>
Can having a
I am having issues getting some components installed for gnuradio. I am
trying to install gr-baz and op25.
My OS is Debian 8, and I installed gnuradio from the standard repository
with
sudo apt-get build-dep gnuradio
sudo apt-get install gnuradio gnuradio-dev gr-osmosdr librtlsdr-dev
libuhd-dev
On 06/04/2017 06:07 PM, Qurat-Ul-Ann Akbar wrote:
It does detect the correlation and start of frames in sync_Short
block but data is not decoded probably because of high noise.
If there are no overruns and your SNR is so incredibly bad that you
cannot even detect the autocorrelation at the
Hi all,
tx_ofdm.grc
Description: Binary data
I was trying out tx_ofdm.grc (flow graph that comes with the OFDM examples in Gnuradio).Specifically, I am trying to transfer a picture of a cat from a file source and see whether it gets transmitted correctly.However I noticed that some bytes (exactly
I have been doing this for a long time now and I have changed all these
parameters that you just mentioned in order to understand whats going on. I
have changed both the transmitter and receiver gain and set different
values but gain is not changing the SNR for some reason. It only works till
2.5
On 06/04/2017 05:35 PM, Qurat-Ul-Ann Akbar wrote:
Then what could be the problem for a low SNR. The average power I see at
the receiver is -100 to -120 db and the signal is too distorted within
noise.
This can have many reasons (including gain, interference, DC offsets, LO
leakage, etc
Then what could be the problem for a low SNR. The average power I see at
the receiver is -100 to -120 db and the signal is too distorted within
noise.
And I watched your video on YouTube in which you were showing a demo of the
WiFi receiver. In that video you had big antennas and I don't think
On 06/04/2017 05:16 PM, Qurat-Ul-Ann Akbar wrote:
I understand. But you didnt connect them directly to the USRP. You used
some cable to connect the two and had a stand for your antenna. Can you
tell me which cable was that ?
I have no idea what you are talking about. When I used the Vert
I understand. But you didnt connect them directly to the USRP. You used
some cable to connect the two and had a stand for your antenna. Can you
tell me which cable was that ?
On Jun 4, 2017 11:13 AM, "Bastian Bloessl" wrote:
> Hi,
>
>
> On 06/04/2017 04:25 PM, Qurat-Ul-Ann
Hi,
On 06/04/2017 04:25 PM, Qurat-Ul-Ann Akbar wrote:
Thank you for the explanation. Can you tell me which antennas did you
use for your experiments when you wrote your paper? Because I think a
major problem with my receiver is a very low SNR because everything
works fine with simulations.
I'll be speaking about the DARPA Bay Area Hackfest in two venues around the
DC area over the next couple of weeks. I'll be at Nova Labs in Reston on
Tuesday the 6th at 7pm and HacDC on the 14th at 7:30. If you want to hear
more about DARPA and the Hackfest we're putting together with NASA Ames,
Thank you for the explanation. Can you tell me which antennas did you use
for your experiments when you wrote your paper? Because I think a major
problem with my receiver is a very low SNR because everything works fine
with simulations. Currently I am using Vert 2450 antenna with my USRP N210.
Hello,
Last week I started the implementation of the SigMF JSON C++ API.
Please take a look at my blog[1] and the gr-sigmf repo[2].
Thanks!
Links:
--
[1] http://ixion.csd.uoc.gr/ctriant/?p=227
[2] https://github.com/ctriant/gr-sigmf/tree/dev
Hi,
On 6/3/2017 9:11 PM, Qurat-Ul-Ann Akbar wrote:
Hello,
How is the timing offset being handled in the 802.11 module. I see that
the sync_long block does frequency offset correction and the
frame_equalizer block does the phase correction but I dont understand
where is the timing offset
14 matches
Mail list logo