[srslte-users] radios don't hear each other

Andre Puschmann andre.puschmann at softwareradiosystems.com
Thu Nov 16 09:30:38 UTC 2017


Hi,

there are many lates and underflows on the eNB console. They are very
likely messing up the transmitted signal. Please make sure you are
configuring frequency scaling accordingly and use a potent enough CPU.

Once you fixed those, please try again the UE. In case it still doesn't
work, please send the ue.log.

Hope that helps!

Cheers
Andre



On 16/11/17 01:19, Spencer Sevilla wrote:
> Hi all,
> 
> I'm trying to get a very very basic testbed setup, but no matter what I
> do, srsue and srsenb don't want to talk to each other. Here's my setup
> and logs:
> 
> eNB:
> 
> Running Ubuntu 17.04, hardware is a USRP B200, local EPC based on OAI
> (openair-cn). I'm just using the standard sample config files,
> {enb,rr,drb,sib}.conf.example. Terminal output for starting the eNB is
> as follows:
> 
> spencer at spencertower:~/Desktop/srsLTE$ sudo ./build/srsenb/src/srsenb enb.conf
> linux; GNU C++ version 6.3.0 20170406; Boost_106200; UHD_003.010.002.000-3-g122bfae1
> 
> ---  Software Radio Systems LTE eNodeB  ---
> 
> Reading configuration file enb.conf...
> Opening USRP with args: type=b200,master_clock_rate=30.72e6
> -- Detected Device: B200
> -- Operating over USB 3.
> -- Initialize CODEC control...
> -- Initialize Radio control...
> -- Performing register loopback test... pass
> -- Performing CODEC loopback test... pass
> -- Asking for clock rate 30.720000 MHz... 
> -- Actually got clock rate 30.720000 MHz.
> -- Performing timer loopback test... pass
> Setting frequency: DL=2630.0 Mhz, UL=2510.0 MHz
> -- Asking for clock rate 23.040000 MHz... 
> -- Actually got clock rate 23.040000 MHz.
> -- Performing timer loopback test... pass
> Setting Sampling frequency 5.76 MHz
> 
> ==== eNodeB started ===
> Type <t> to view trace
> t
> Enter t to stop trace.
> ULULLLLLLLLLLLLLLLLULLLLLLLLLLLLLLLL^C^C^CU^C^C^C---  exiting  ---
> 
> 
> Once the "eNodeB started" comes up, I can see both green and red lights
> (TX and RX) on the SDR stay constantly lit. This goes on for about a
> minute until I control-C.
> 
> 
> UE:
> 
> Running Ubuntu 17.04, hardware is a USRP B210. Again, I'm just using the
> standard sample config file ue.conf.example. Terminal output for the UE
> (which I starts after the eNB) is as follows:
> 
> Reading configuration file ./srsue/ue.conf.example...
> ---  Software Radio Systems LTE UE  ---
> 
> Opening RF device with 1 RX antennas...
> Opening USRP with args: type=b200,master_clock_rate=30.72e6
> -- Detected Device: B210
> -- Operating over USB 3.
> -- Initialize CODEC control...
> -- Initialize Radio control...
> -- Performing register loopback test... pass
> -- Performing register loopback test... pass
> -- Performing CODEC loopback test... pass
> -- Performing CODEC loopback test... pass
> -- Asking for clock rate 30.720000 MHz... 
> -- Actually got clock rate 30.720000 MHz.
> -- Performing timer loopback test... pass
> -- Performing timer loopback test... pass
> Waiting PHY to initialize...
> ...
> Searching cell in DL EARFCN=2850, f_dl=2630.0 MHz, f_ul=2510.0 MHz
> ...........................................................
> RRC PLMN Search: timeout expired. Searching again
> ...........................................................
> RRC PLMN Search: timeout expired. Searching again
> ..........................................................
> RRC PLMN Search: timeout expired. Searching again
> ..................................................^C---  exiting  ---
> 
> 
> After it boots, it just keeps searching for the PLMN (with the green
> light on the SDR blinking to indicate RX) to no avail; this goes on
> until I control-C.
> 
> I double-checked the clock-rates, and made sure that downlink and uplink
> frequencies are the same (2630.0 MHz  and 2510.0 MHz, respectively). I
> was also able to get the exact same behavior using the OAI eNodeB, so
> I'm sure I'm doing something wrong here. Any thoughts/wisdom/advice? Are
> there good other things for me to look into, or to make sure I'm doing
> right? Any great way to debug the SDRs and make sure they're doing what
> they're supposed to? I'd appreciate any advice or leads anyone might
> have, cause I'm pretty stumped at the moment.
> 
> Thanks!!!
> Spencer
> 
> 
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
> 




More information about the srsran-users mailing list