On 06/07/2019 12:29 PM, Mark Koenig via USRP-users wrote:
I am using a thunderbolt 3 interface, but only using it at 1Gig,
standard 1500 MTU. I am running at a sample rate of 25Msps.
If the problem is less-prevalent at lower sample rates, that suggests
that your interface is dropping packet
On 06/07/2019 03:05 PM, Jason Matusiak via USRP-users wrote:
OK, this is actually an E310 problem. The E310 always looks off
device first. A coworker reminded me that we spent a couple days years
back trying to figure out why the device was asking like it was
working, but we weren't seeing a
On 06/07/2019 03:17 PM, Jason Matusiak via USRP-users wrote:
> OK, I will keep an eye on that. No GR will kill us for now though. I've
> been playing with the build system for an E320 the last 2 weeks and have
> learned to build //some// extra things in (including GR, but I haven't moved
> tha
Hi,
I'm transmitting a signal and receiving it using USRPs and want to estimate the
frequency offset, but I'm getting something confusing.
I'm using 2.45GHz for the transmitting, and the sampling rate is 1MHz. The
signal consists of 5 repeated preambles, and each of them has 100 data points
(i
A good write-up, thanks Sulvain.
I forgot all about how they functioned. I worked on an SDR project a million
years ago (before SDR was a thing) that did this. I just used it and didn't
realize that it was a super-het, and then I forgot all about it once I started
using USRPs.
Thanks.
__
OK, I will keep an eye on that. No GR will kill us for now though. I've been
playing with the build system for an E320 the last 2 weeks and have learned to
build //some// extra things in (including GR, but I haven't moved that image
onto a device yet), so I could probably take a swag at it, bu
Hi Jason,
You could try running the new 3.15 MPM based file system for the E310, but
it has some caveats, more details here:
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2019-May/059897.html
Regards,
Nate Temple
On Fri, Jun 7, 2019 at 12:05 PM Jason Matusiak <
ja...@gardettoengi
OK, this is actually an E310 problem. The E310 always looks off device first.
A coworker reminded me that we spent a couple days years back trying to figure
out why the device was asking like it was working, but we weren't seeing any
results. It was because it was actually talking to an N2xx
OK, maybe based on my last email (which crossed yours I think). The addr flag
doesn't seem to work at all with the uhd_usrp_probe on the E310 (at least my
version).
From: Nate Temple
Sent: Friday, June 7, 2019 12:37 PM
To: Jason Matusiak
Cc: Marcus D Leech; Phi
I just realized that using the 127 and 102 addresses don't work with the probe
on the E310. It only works when I don't use the arg flag.
From: Jason Matusiak
Sent: Friday, June 7, 2019 12:22 PM
To: Nate Temple
Cc: Marcus D Leech; Philip Balister; Ettus Mail List
Hi Jason,
For what its worth, I haven't personally ran this exact combo (E310 w/ UHD
3.11 and E320 w/ 3.14) on the same subnet, but I have ran two N320's on the
same subnet (192.168.10.2 and 192.168.10.3, both with 3.14). I did run into
the issue where probing in embedded mode would pickup the oth
I am using a thunderbolt 3 interface, but only using it at 1Gig, standard 1500
MTU. I am running at a sample rate of 25Msps.
Mark
From: Neel Pandeya
Date: Thursday, June 6, 2019 at 2:00 PM
To: Mark Koenig
Cc: "usrp-users@lists.ettus.com"
Subject: Re: [USRP-users] UHD Comms Error
Hello Mark:
Howdy.
Nope, but it fails in a weird way. I disconnected the E320 to make sure this
issue wasn't due to it, but it still acts the same.
If I run: uhd_usrp_probe --args "addr=127.0.0.1"
root@ettus-e3xx-sg3:~# uhd_usrp_probe --args "addr=127.0.0.1"
[INFO] [UHD] linux; GNU C++ version 7.3.0; Bo
Hi Jason,
On the E310, if you pass the device arg addr with 127.0.0.1 does it work as
expected?
uhd_usrp_probe --args "addr=127.0.0.1"
Regards,
Nate Temple
On Fri, Jun 7, 2019 at 9:10 AM Jason Matusiak via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Darn, I was hoping that was it, but I
Darn, I was hoping that was it, but I don't think so.
Here is the result from my E310:
eth0 Link encap:Ethernet HWaddr 00:80:2F:25:44:46
and now the E320:
sfp0 Link encap:Ethernet HWaddr 00:80:2F:24:C2:FB
If I ping each device on my host, then run arp, I see this (the mac addresse
Check the MAC addresses.
I know that on some ARM platforms that has to be programmed in at boot and
perhaps these system images have it set to the same value.
Sent from my iPhone
> On Jun 7, 2019, at 11:52 AM, Jason Matusiak via USRP-users
> wrote:
>
> Philip,
>
> They have unique address
Philip,
They have unique addresses (10.95 and 10.45). It is really weird that when I
am on the E310, and set the ip-addr to himself, that he would even look off the
device
They both have hostnames and they are not similar to each other at all.
From: Phi
Check each ones ip address, likely by running ifconfig. In the back of
my mind, I recall something like this in the E100 days. Do they have the
same hostname?
Philip
On 06/07/2019 07:37 AM, Jason Matusiak via USRP-users wrote:
> It looks like I am misunderstanding something with how the E320 hand
Hi,
I am trying to stream one, and only one, channel from a LFRX inside a X310
using the rx_samples_to_file example, but haven't been fully successful.
It seems to always stream data for the second channel as well.
The command I am running is:
rx_samples_to_file -file=/path_to_file/file.da
OK, another E320 question. With my custom RFNoC image, only a Radio_0 shows
up. Shouldn't there be a Radio_1 as well?
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
It looks like I am misunderstanding something with how the E320 handles the
network.
I have my E320 on my subnet with the sfp0 assigned to 10.45 (instead of the
default 10.2). I can ssh into it and things seem to run fine in embedded mode.
Now, if I ssh onto an E312 that is on the same netwo
21 matches
Mail list logo
