I am not sure but if your streaming at 10-million samples per second and
each sample is 32-bit (two 16-bit components; I/Q) then your total needed
bandwidth is 40 million bytes which means you need a 320-megabit network
connection.
You might need a gigabit network?
On Fri, Sep 8, 2017 at 3:04 PM,
Guys,
I got to doing some calculations and I realized that exceeding -15dBm on
the receiver circuitry could be a lot easy than it seems to amateurs like
me. So, I wanted to run this by some of you because I know that you guys
have far more radio engineering knowledge than me.
So, lets take a situ
You guys can ignore this but your welcome to reply. I found the archives
for this list and was able to locate a couple subjects that are giving me
some information.
But, feel free to reply, but also feel free to ignore it because I believe
I am asking the same question you guys have likely answers
This is connected to me investigating power level but the question is
specifically about the number of bits per RX and TX channel between the
N200 and B200. However, I fell into the rabbit hole that Alice went into
and I seem to be stuck for the moment in determining what I am missing.
I looked at
complex pair or two real
> valued channels.
>
> Regards,
> Derek
>
>
>
> On Fri, Oct 13, 2017 at 5:21 AM, Kevin McGuire via USRP-users <
> usrp-users@lists.ettus.com> wrote:
>
>> This is connected to me investigating power level but the question is
>> s
My knowledge is limited, therefore, read this with a grain of salt.
However, I wanted to try to help and if something I say does not make sense
then double-check it or someone else may come along and correct me.
I had this same problem when I started with these types of systems. I had
trouble unde
Hey,
I am used to the B200 over USB3. So with the N200 and uhd_rx_cfile utility
I *finally* realized that it reports dropped packets as the letter D to the
terminal output. I guess I was thinking it was D for data and yes the
thought did cross my mind that its not quite enough Ds for a 2000 sample
Make this question fairly low priority.
Just realized the N200 supports gigabit ethernet. I think that might be
what happened. I calculated it in my pre-planning phase then did not
realize my network here is limited to 100MBit, but that is an easy fix so
not worries.
On Tue, Oct 31, 2017 at 11:31
I have noticed that neon support for the converter is not enabling. The
CMakeError.log has this output. I am not certain as I am not really
familiar with ARM and NEON, but I checked my CPU and it does support it.
Also, the error message below is saying it is just a matter of passing
certain flags.
I was able to get the compiler flags passed in so that the check for the
header arm_neon.h passes. I added it to the CMakeList root file with
SET(CMAKE_CXX_FLAGS, "${CMAKE_CXX_FLAGS} -mfloat-abi=softfp -mfpu=neon").
Then, it would detect neon. However, I spent considerable time cleaning up
whateve
com> wrote:
> Hello,
>
> maybe this : https://github.com/EttusResearch/uhd/pull/135
> will help you
>
> Gwen
>
> On Fri, 10 Nov 2017 00:29:25 -0600
> Kevin McGuire via USRP-users wrote:
>
> > I was able to get the compiler flags passed in so that the check for
&g
11 matches
Mail list logo
