Re: [USRP-users] b210 and x310 synchronisation from non-GPSDO external clock

[BERTOLINI Rodolphe via USRP-users]

Thank you for your reply and for the information, Marcus.

In my setup, there are :
- 2 base stations : one b210, one x310
- 1 UE : one b210

So in OAI there is a procedure at UE side that checks for downlink offset 
around a specified carrier frequency before attaching to base station. 
Base stations are asked to transmit around a carrier at 2.68Ghz
When using internal clock source, UE detects an offset of :
- roughly -5.3kHz around 2.68GHz for x310 base station;
- roughly +0.9kHz around 2.68GHz for b210 base station

When using my external clock source, UE detects an offset of :
- roughly -54kHz around 2.68GHz for x310 base station;
- roughly +20kHz around 2.68GHz for b210 base station

When I sent the email yesterday, UE wasn't checking offset more than |10kHz| so 
this is why it wasn't detecting base stations broadcasts.
You said that " the internal clocks are already pretty good" so I had the idea 
that if mine is less good, then offset would likely be further than when using 
internal clock. And it seems to be the case.
Thank you for the hint.

Now, UE cannot attach to base station, basically it doesn't decode anything 
except synchronisation signals and MIB. I think it is because of the poor 
quality clock.

Do you think that using the Ettus OctoClock-G can enable base station time 
synchronisation while reducing carrier offset and without breaking everything 
as my poor clock does?

Thank you again.
Regards,
Rodolphe

-Message d'origine-
De : USRP-users  De la part de Marcus D. 
Leech via USRP-users
Envoyé : lundi 7 décembre 2020 18:35
À : usrp-users@lists.ettus.com
Objet : Re: [USRP-users] b210 and x310 synchronisation from non-GPSDO external 
clock

On 12/07/2020 11:24 AM, BERTOLINI Rodolphe via USRP-users wrote:
> Dear all,
>
> I put both mailing list (OAI and USRP) because both may have something to do 
> with my problem. I apologize if it is not appropriate.
>
> I would like to synchronize a b210 and an x310 using a square signal 
> generated by a function generator. It has a 10MHz ref output, so I generate a 
> 1Hz square clock through a regular front output.
> Except the output voltage, is there something I should care about ? I use 
> them with OAI, and they both are used as LTE base stations. When the base 
> station is on external ref, UE doesn't detect the base station. When the base 
> station is on internal ref, UE detects base station broadcasts and connects 
> to the base station.
>
> Note 1 : PPS and REF are well detected by the USRP, when I change for example 
> PPS frequency, x310 led changes respectively.
> Note 2 : only one USRP is used at the same time, I want to make it 
> work first with only one base stations, and then when base stations are both 
> on and synchronised Note 3 : in OAI code, there is something like :
>
> usrp_master_clock = 30.72e6;
> args += boost::str(boost::format(",master_clock_rate=%f") % 
> usrp_master_clock); args += ",num_send_frames=256,num_recv_frames=256, 
> send_frame_size=7680, recv_frame_size=7680" ;
>
> Is this master clock related to the sampling rate, or should it be changed to 
> 10MHz?
The master clock rate is related to the available sampling rates, and not the 
external reference frequency, which is 10MHz.  The B210 is
   quite flexible in its master clock rate, but the X310 is much more limited 
in the master-clock rates it supports.



>
> Note 4 : I looked at the spectrum of signal sent by base station, I 
> don't see any difference between the setup with external clock and the 
> setup with internal clock
Unless you have your spectrum analyser set-up for very-fine resolution, you 
likely won't see much difference--the internal clocks are
   already pretty good.


>
> Any pointer would be much appreciated
> Thank you.
>
> Regards,
> Rodolphe
> ___
> USRP-users mailing list
> USRP-users@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com


___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] b210 and x310 synchronisation from non-GPSDO external clock

[BERTOLINI Rodolphe via USRP-users]

Dear all,

I put both mailing list (OAI and USRP) because both may have something to do 
with my problem. I apologize if it is not appropriate.

I would like to synchronize a b210 and an x310 using a square signal generated 
by a function generator. It has a 10MHz ref output, so I generate a 1Hz square 
clock through a regular front output.
Except the output voltage, is there something I should care about ? I use them 
with OAI, and they both are used as LTE base stations. When the base station is 
on external ref, UE doesn't detect the base station. When the base station is 
on internal ref, UE detects base station broadcasts and connects to the base 
station.

Note 1 : PPS and REF are well detected by the USRP, when I change for example 
PPS frequency, x310 led changes respectively.
Note 2 : only one USRP is used at the same time, I want to make it work first 
with only one base stations, and then when base stations are both on and 
synchronised
Note 3 : in OAI code, there is something like :

usrp_master_clock = 30.72e6;
args += boost::str(boost::format(",master_clock_rate=%f") % usrp_master_clock);
args += ",num_send_frames=256,num_recv_frames=256, send_frame_size=7680, 
recv_frame_size=7680" ;

Is this master clock related to the sampling rate, or should it be changed to 
10MHz?

Note 4 : I looked at the spectrum of signal sent by base station, I don't see 
any difference between the setup with external clock and the setup with 
internal clock

Any pointer would be much appreciated
Thank you.

Regards,
Rodolphe
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] X310: HG image, both link were functional until this morning

[BERTOLINI Rodolphe via USRP-users]

Hi again,

Sorry, followed https://kb.ettus.com/X300/X310_Device_Recovery and it now works 
like a charm.

Regards,
Rodolphe

De : USRP-users [usrp-users-boun...@lists.ettus.com] de la part de BERTOLINI 
Rodolphe via USRP-users [usrp-users@lists.ettus.com]
Envoyé : vendredi 4 septembre 2020 11:55
À : USRP list
Objet : [USRP-users] X310: HG image, both link were functional until this 
morning

Hello,

I work with an X310 and OpenAirInterface. I use HG image, and switch from times 
to times between 10Gb (when connected to a server) and 1Gb interface (when 
connected to a laptop).
It worked very fine during one year, and since this morning link leds don't 
light up, neither port 1 nor port 2 
(https://kb.ettus.com/Troubleshooting_X300/X310_Device_Discovery_Issues)

I didn't change anything between yesterday (working) and this morning (not 
working).
I triple-checked IP configurations, they are fine.

Any hint?

Thank you.
Regards,
Rodolphe
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] X310: HG image, both link were functional until this morning

[BERTOLINI Rodolphe via USRP-users]

Hello,

I work with an X310 and OpenAirInterface. I use HG image, and switch from times 
to times between 10Gb (when connected to a server) and 1Gb interface (when 
connected to a laptop).
It worked very fine during one year, and since this morning link leds don't 
light up, neither port 1 nor port 2 
(https://kb.ettus.com/Troubleshooting_X300/X310_Device_Discovery_Issues)

I didn't change anything between yesterday (working) and this morning (not 
working).
I triple-checked IP configurations, they are fine.

Any hint?

Thank you.
Regards,
Rodolphe
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] DPDK runtime error

[BERTOLINI Rodolphe via USRP-users]

Hello again,

There seemed to have wrong rights on file, because after changing rights and 
editing the file I had this error:


[INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501; 
UHD_3.15.0.HEAD-0-gaea0e2de
EAL: Detected 28 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device :00:1f.6 on NUMA socket 0
EAL:   probe driver: 8086:15b9 net_e1000_em
EAL: PCI device :17:00.0 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL:   using IOMMU type 1 (Type 1)
EAL: Ignore mapping IO port bar(2)
EAL: PCI device :17:00.1 on NUMA socket 0
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: Ignore mapping IO port bar(2)
EAL: PCI device :45:00.0 on NUMA socket 0
EAL:   probe driver: 8086:1563 net_ixgbe
EAL: PCI device :45:00.1 on NUMA socket 0
EAL:   probe driver: 8086:1563 net_ixgbe
EAL: Error - exiting with code: 1
  Cause: Requested inactive lcore 3 for port 0


I solved this error by editing again the conf file (it seems that I had to 
remove dpdk-io-core lines)

Now I have again the IPv4 assignement error, with the following configuration :

[use-dpdk=1]
dpdk-mtu=9000
;dpdk-driver=/usr/local/lib/dpdk-pmds/
dpdk-driver=/usr/lib/x86_64-linux-gnu/dpdk-17.11-drivers/
dpdk-corelist=2-4
dpdk-num-mbufs=4096
dpdk-mbuf-cache-size=316
[dpdk-mac=f8:f2:1e:29:c5:14]
dpdk-lcore = 3
;dpdk-io-cpu = 3
dpdk-ipv4 = 192.168.30.2/24
[dpdk-mac=f8:f2:1e:29:c5:15]
dpdk-lcore = 4
;dpdk-io-cpu = 4
dpdk-ipv4 = 192.168.40.2/24
;dpdk-num-desc=4096

It tells me :

EAL: Please set IPv4 address for port 0 before opening socket

I don't get what is wrong. Must both SFP ports of the USRP be plugged, to the 
host?

Regards,
Rodolphe


De : USRP-users [usrp-users-boun...@lists.ettus.com] de la part de BERTOLINI 
Rodolphe via USRP-users [usrp-users@lists.ettus.com]
Envoyé : jeudi 6 février 2020 11:47
À : usrp-users@lists.ettus.com
Objet : Re: [USRP-users] DPDK runtime error

Hello,
Sorry if I had better to create an other thread.

I am trying also to reach better stability in OpenAirInterface, and to use USRP 
through DPDK.
I face the exact same error, however I don't have /etc/uhd folder :

$ locate uhd.conf
/etc/security/limits.d/uhd.conf
/etc/security/limits.d/uhd.conf.dpkg-new

The content of those files is :
@usrp-   rtprio  99

I manually created folder ~/.uhd/, and put a uhd.conf file here (I have read 
somewhere that there are different places where uhd conf file can be located 
depending on system wide or user wide configuration). No success.
Later I also created /etc/uhd folder and copy-pasted the conf file there, still 
no success.

The word separator I used is "-" as you suggested to Florian.

Any thought ?

Also @Florian, do you see any improvement in OAI stability using DPDK with UHD 
3.15?

Thank you.
Regards,
Rodolphe


Hi Aaron,

thanks for spotting this! Indeed that was a mistake. I also had to
adjust the dpdk-num-mbufs=4059 and dpdk-mbuf-cache-size=315 like in the
example configuration file for uhd 3.15.0 and then it worked! Yay!

Now lets see if OpenAirInterface runs more stable with this! :)

Florian.

On 1/8/2020 17:31, Aaron Rossetto via USRP-users wrote:

> Hello Florian,
>
> I believe in UHD 3.15, the keys in the uhd.conf file use dashes (-), not 
> underscores between words, e.g.:
>
> [dpdk-mac=00:11:22:33:44:55]
> dpdk-io-cpu = 1
> dpdk-ipv4 = 192.168.10.1/24
>
> Hope that helps,
> Aaron
>
>
>
> From: USRP-users  lists.ettus.com<http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com>>
>  On Behalf Of Florian Kaltenberger via USRP-users
> Sent: Wednesday, January 8, 2020 10:10 AM
> Subject: [EXTERNAL] Re:DPDK runtime error
>
> Hi,
> we now installed DPDK 17.11 but I still have exactly the same problem.
> I have a feeling the problem is that I am not addressing the device 
> correctly. Here is what I did:
> The USRP is connected to ethernet interfaces "p1p2" (mac_addr 
> 64:9d:99:b1:1e:8d) and "p1p4" (mac_addr 64:9d:99:b1:1e:8f) which are 
> originally configured with IP addresses 192.168.10.1 and inet_addr 
> 192.168.20.1. This configuration works fine without dpdk.
> Then I deactivate these two interfaces using "ifconfig p1p2 down" "ifconfig 
> p1p4 down"and do "dpdk-devbind --bind=vfio-pci 01:00.1" and "dpdk-devbind 
> --bind=vfio-pci 01:00.3". The status of "dpdk-devbind -s" is below.
> In the file /etc/uhd/uhd.conf I specify
> [dpdk_mac=64:9d:99:b1:1e:8d]
> dpdk_io_cpu = 1
> dpdk_ipv4 = 192.168.10.1/24
>
> [dpdk_mac=64:9d:99:b1:1e:8f]
> dpdk_io_cpu = 2
> dpdk_ipv4 = 192.168.20.1/24
> Is this the correct way of specifying it? What surprises me is that DPDK 
> requires to address the device

Re: [USRP-users] DPDK runtime error

[BERTOLINI Rodolphe via USRP-users]

Hello,
Sorry if I had better to create an other thread.

I am trying also to reach better stability in OpenAirInterface, and to use USRP 
through DPDK.
I face the exact same error, however I don't have /etc/uhd folder :

$ locate uhd.conf
/etc/security/limits.d/uhd.conf
/etc/security/limits.d/uhd.conf.dpkg-new

The content of those files is :
@usrp-   rtprio  99

I manually created folder ~/.uhd/, and put a uhd.conf file here (I have read 
somewhere that there are different places where uhd conf file can be located 
depending on system wide or user wide configuration). No success.
Later I also created /etc/uhd folder and copy-pasted the conf file there, still 
no success.

The word separator I used is "-" as you suggested to Florian.

Any thought ?

Also @Florian, do you see any improvement in OAI stability using DPDK with UHD 
3.15?

Thank you.
Regards,
Rodolphe


Hi Aaron,

thanks for spotting this! Indeed that was a mistake. I also had to
adjust the dpdk-num-mbufs=4059 and dpdk-mbuf-cache-size=315 like in the
example configuration file for uhd 3.15.0 and then it worked! Yay!

Now lets see if OpenAirInterface runs more stable with this! :)

Florian.

On 1/8/2020 17:31, Aaron Rossetto via USRP-users wrote:

> Hello Florian,
>
> I believe in UHD 3.15, the keys in the uhd.conf file use dashes (-), not 
> underscores between words, e.g.:
>
> [dpdk-mac=00:11:22:33:44:55]
> dpdk-io-cpu = 1
> dpdk-ipv4 = 192.168.10.1/24
>
> Hope that helps,
> Aaron
>
>
>
> From: USRP-users  lists.ettus.com>
>  On Behalf Of Florian Kaltenberger via USRP-users
> Sent: Wednesday, January 8, 2020 10:10 AM
> Subject: [EXTERNAL] Re:DPDK runtime error
>
> Hi,
> we now installed DPDK 17.11 but I still have exactly the same problem.
> I have a feeling the problem is that I am not addressing the device 
> correctly. Here is what I did:
> The USRP is connected to ethernet interfaces "p1p2" (mac_addr 
> 64:9d:99:b1:1e:8d) and "p1p4" (mac_addr 64:9d:99:b1:1e:8f) which are 
> originally configured with IP addresses 192.168.10.1 and inet_addr 
> 192.168.20.1. This configuration works fine without dpdk.
> Then I deactivate these two interfaces using "ifconfig p1p2 down" "ifconfig 
> p1p4 down"and do "dpdk-devbind --bind=vfio-pci 01:00.1" and "dpdk-devbind 
> --bind=vfio-pci 01:00.3". The status of "dpdk-devbind -s" is below.
> In the file /etc/uhd/uhd.conf I specify
> [dpdk_mac=64:9d:99:b1:1e:8d]
> dpdk_io_cpu = 1
> dpdk_ipv4 = 192.168.10.1/24
>
> [dpdk_mac=64:9d:99:b1:1e:8f]
> dpdk_io_cpu = 2
> dpdk_ipv4 = 192.168.20.1/24
> Is this the correct way of specifying it? What surprises me is that DPDK 
> requires to address the device by its PCI address while UHD still requires to 
> set the IP addresses.
> Florian.
>
> ___
> USRP-users mailing list
> USRP-users at 
> lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
--
Follow us on Google+ ,
LinkedIn , or Twitter
!
-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: florian_kaltenberger.vcf
Type: text/x-vcard
Size: 274 bytes
Desc: not available
URL: 

___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] X310 and N310: using multiple RF

[BERTOLINI Rodolphe via USRP-users]

Hello USRP-users mailing list,

We are using an X310 for OpenAirInterface (OAI). It has one RF card.
I wonder the following:


  *   With the following configuration:
 *   USRP X310, HG image, one RF card
 *   host connected to USRP through 1*10Gbps and 1*1Gbps
  *   I run OAI on the 10Gbps ethernet interface, and while it is running I 
tried to run an other instance via the 1Gbps ethernet interface. I didn't 
expect it to work, but I didn't expect neither the error message: uhd tells me 
that no USRP was found (I made sure it looks-up through the 1Gbps interface).
 *   My interpretation is that once that all of the available RF cards have 
an established link with the host, USRP closes all of the free interfaces 
(PCIe, ethernet...)
 *   Thus, if I put an other RF card, and tell the USRP to use only one 
ethernet interface per RF card, then I would be able to run one OAI instance 
through an ethernet interface + an RF card, and an other instance through the 
other ethernet interface + the other RF card. Is it correct?
 *   Now if we consider the N310, its 4 RF cards and its 2 ethernet 
interfaces: (ignoring limitation from OAI bandwidth requirements) is it 
possible to run two instances of OAI through a single ethernet interface, so 
that I could run four instance through two ethernet interfaces?
 *   If all of the above is correct, do you have any idea on how to achieve 
this?

Thank you
Regards,
Rodolphe
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com