[srslte-users] Having troubles to connect srsUE with srsENB
Justin Tallon
justin.tallon at softwareradiosystems.com
Fri Jun 14 11:53:13 UTC 2019
Hey Mohammed,
Since you cannot even see the enodeb transmission with pdsch_ue, I suggest
trying to transmit with the basic pdsch_enodeb example and attempt to
receive this first.
Do you have access to a spectrum analyzer of any kind to check the
at node 1: ./pdsch_enodeb -f <freq> -p 6 -g 80
at node 2: ./pdsch_ue -f <freq>
share the results here.
Thanks,
Justin
____
Justin Tallon Ph.D.
Software Radio Systems (SRS)
http://www.softwareradiosystems.com
+353-86-067-0753 | justin.tallon at softwareradiosystems.com
On Thu, Jun 13, 2019 at 12:25 PM Mohammed Jabi <mohammed.jabi.mj at gmail.com>
wrote:
> Hi,
>
> No, I did not find any solution yet. I have also tried to connect enb;
> running over BladeRf; and real UEs. Unfortunatly, UEs are not even capable
> of detecting the created srslte network. I have tried 3 different phones:
> Samsung Galaxy 7 and 8 and Huawei (I do not remember the model but it is a
> new one).
>
> One additional remark is that when I have srsUE running on BladeRf too,
> not only it can not detect enb but the network interface "tun_srsue" is not
> created.
>
> After going throughout many srslte related discussions/forums, I have the
> impression that usrp was most tested/used as enb than BladeRf. So, I
> suspect that my problem is related to hardware.
>
> Please let me posted if you come up with a solution.
>
> Thanks
> Mohammed
>
>
>
> On Thu, Jun 13, 2019, 3:52 AM Saimanoj Katta, <saimanoj.katta at cumucore.com>
> wrote:
>
>> Hi Justin and Mohammed,
>>
>> Mohammed: Did you figure any solution for this? I am encountering the
>> same problem.
>> Justin: In my case, the cell tries to decode the SIB1 and MIB from the
>> eNB (I got this information from logs). I checked the UI console of eNB and
>> it doesn't have SIB1 configured. I am not able to add it either there. Any
>> suggestions on how to proceed? Radio level works correctly for me!
>>
>> On further note, I tried to eNB and EPC on USRP and connect it via UE(
>> real mobile). I configured the IMSI, K, OPC in EPC db. The mobile could not
>> figure the created network either. Is something wrong with my setup of the
>> hardware?
>>
>> I would appreciate any leads. Thank you very much for your time and
>> consideration
>>
>> Here's my output in the radio level:
>> ubuntu at ubuntu-Zephyrus-GX501GI:~/srsLTE/build$ ./lib/examples/pdsch_ue
>> -f 2680e6
>> Opening RF device with 1 RX antennas...
>> [INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501;
>> UHD_3.15.0.git-1-gf83faf28
>> [INFO] [LOGGING] Fastpath logging disabled at runtime.
>> Opening USRP with args: type=x300,master_clock_rate=184.32e6
>> [INFO] [X300] X300 initialization sequence...
>> [INFO] [X300] Maximum frame size: 1472 bytes.
>> [INFO] [X300] Radio 1x clock: 184.32 MHz
>> [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
>> [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID:
>> 0xF1F0D00000000000)
>> [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1305 MB/s)
>> [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1305 MB/s)
>> [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001)
>> [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001)
>> [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000000)
>> [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000000)
>> [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0000000000000)
>> [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0000000000000)
>> Starting AGC thread...
>> Tunning receiver to 2680.000 MHz
>> Searching for cell...
>> *Found Cell_id: 12 FDD, CP: Normal , DetectRatio=100% PSR=7.37,
>> Power=-84.1 dBm
>> Found Cell_id: 0 FDD, CP: Normal , DetectRatio= 0% PSR=0.00,
>> Power=-inf dBm
>> Found Cell_id: 0 FDD, CP: Normal , DetectRatio= 0% PSR=0.00,
>> Power=-inf dBm
>> Decoding PBCH for cell 12 (N_id_2=0)
>> Setting sampling rate 23.04 MHz
>> Gtk-Message: 10:43:57.467: Failed to load module "canberra-gtk-module"
>> - Type: FDD 7,3, FrameCnt: 0, State: 1
>> - PCI: 12
>> - Nof ports: 2
>> - CP: Normal
>> - PRB: 100
>> - PHICH Length: Normal
>> - PHICH Resources: 1/6
>> - SFN: 892
>> Decoded MIB. SFN: 892, offset: 0
>> CFO: +626,52 Hz
>> RSRP: +14,1 dBm | +3,2 dBm
>> SNR: +10,6 dB
>> TM: 2
>> Rb: 0,01 / 0,17 / 0,39 Mbps (net/maximum/processing)
>> PDCCH-Miss: 0,00%
>> PDSCH-BLER: 0,00%
>> TB 0: mcs=6; tbs=176
>> TB 1: mcs=0; tbs=0
>> Press enter maximum printing debug log of 1 subframe.
>>
>> CFO: +585,82 Hz
>> [DEBUG]: ---- Receive 23040 samples ----
>> [INFO]: SYNC TRACK: sf_idx=4, ret=1, next_state=1
>> CFO: +565,50 Hz
>> [DEBUG]: ---- Receive 23040 samples ----
>> [INFO]: SYNC TRACK: sf_idx=7, ret=1, next_state=1
>> CFO: +565,50 Hz
>> RSRP: +13,1 dBm | +3,2 dBm
>> SNR: +10,6 dB
>> TM: 2
>> Rb: 0,08 / 0,18 / 0,78 Mbps (net/maximum/processing)
>> PDCCH-Miss: 0,00%
>> PDSCH-BLER: 0,00%
>> TB 0: mcs=6; tbs=176
>> TB 1: mcs=0; tbs=0
>> Press enter maximum printing debug log of 1 subframe.
>>
>> CFO: +565,50 Hz
>> RSRP: +13,1 dBm | +3,2 dBm
>> SNR: +10,7 dB
>> TM: 2
>> Rb: 0,08 / 0,18 / 0,78 Mbps (net/maximum/processing)
>> PDCCH-Miss: 0,00%
>> PDSCH-BLER: 0,00%
>> TB 0: mcs=6; tbs=176
>> TB 1: mcs=0; tbs=0
>> Press enter maximum printing debug log of 1 subframe.
>>
>> ^Z
>> [5]+ Stopped ./lib/examples/pdsch_ue -f 2680e6
>>
>> Regards,
>> Manu
>>
>> On Thu, Jun 6, 2019 at 11:15 AM Justin Tallon <
>> justin.tallon at softwareradiosystems.com> wrote:
>>
>>> Hey Mohammed,
>>>
>>> As a first step, why don't you try to receive your enb signal with a
>>> pdsch_ue to ensure everything is working properly at a radio level.
>>>
>>> To do this cd to your build folder at your ue machine and run the
>>> following "./lib/examples/pdsch_ue -f <freq>"
>>>
>>> where <freq> is the downlink frequency of the enb you currently have
>>> running.
>>>
>>> Let me know what the output looks like.
>>>
>>> Regards,
>>>
>>> Justin
>>> ____
>>> Justin Tallon Ph.D.
>>>
>>> Software Radio Systems (SRS)
>>> http://www.softwareradiosystems.com
>>>
>>> +353-86-067-0753 | justin.tallon at softwareradiosystems.com
>>>
>>>
>>> On Thu, Jun 6, 2019 at 10:02 AM Mohammed Jabi <
>>> mohammed.jabi.mj at gmail.com> wrote:
>>>
>>>> Hi everyone,
>>>>
>>>> I am totally new to srsLTE and any help would be appreciated. I am
>>>> trying to connect srsue with srsenb. I have followed all steps described in
>>>> the github page but ue is not able to detect enb.
>>>>
>>>> I am using 2 BladeRFx40; one for ue and the other for enb. I am also
>>>> adopting the configuration provided without any changes. Both machines run
>>>> ubuntu 18.04.2 LTS and their CPUs are:
>>>> UE machine: Dual core Intel Core i7-4500U (-MT-MCP-) cache: 4096 KB
>>>> clock speeds: max: 3000 MHz 1: 1151 MHz 2: 1101 MHz 3: 1078
>>>> MHz
>>>> 4: 1093 MHz
>>>> enB machine: Quad core Intel Core i7-3770 (-MT-MCP-) cache: 8192 KB
>>>> clock speeds: max: 3900 MHz 1: 1774 MHz 2: 1922 MHz 3: 1797
>>>> MHz
>>>> 4: 1769 MHz 5: 1818 MHz 6: 2006 MHz 7: 1929 MHz 8: 1889 MHz
>>>>
>>>> You find attached log files when I run: "sudo srsue
>>>> --log.all_level=info". When I run"
>>>> sudo srsenb --log.all_level=info", the enb.log is always empty. Below
>>>> the outputs in terminals:
>>>>
>>>> XXXXXXXXXXXXXXX
>>>> sudo srsepc
>>>>
>>>> Built in Release mode using commit 5343b33f on branch master.
>>>>
>>>>
>>>> --- Software Radio Systems EPC ---
>>>>
>>>> Reading configuration file /home/remi/.config/srslte/epc.conf...
>>>> HSS Initialized.
>>>> MME S11 Initialized
>>>> MME GTP-C Initialized
>>>> MME Initialized. MCC: 0xf001, MNC: 0xff01
>>>> SPGW GTP-U Initialized.
>>>> SPGW S11 Initialized.
>>>> SP-GW Initialized.
>>>> Received S1 Setup Request.
>>>> S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b
>>>> S1 Setup Request - MCC:001, MNC:01, PLMN: 61712
>>>> S1 Setup Request - TAC 7, B-PLMN 0
>>>> S1 Setup Request - Paging DRX 2
>>>> Sending S1 Setup Response
>>>> SCTP Association Shutdown. Association: 12
>>>> Deleting eNB context. eNB Id: 0x19b
>>>> Releasing UEs context
>>>> No UEs to be released
>>>> ^CDeleting UE context in HSS. IMSI: 001010123456780
>>>> Deleting UE context in HSS. IMSI: 001010123456789
>>>>
>>>> XXXXXXXXXXXXXXX
>>>> sudo srsenb --log.all_level=info
>>>>
>>>> Built in Release mode using commit 5343b33f on branch master.
>>>>
>>>> --- Software Radio Systems LTE eNodeB ---
>>>>
>>>> Reading configuration file /home/remi/.config/srslte/enb.conf...
>>>> Opening bladeRF...
>>>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>>>> Setting frequency: DL=2685.0 Mhz, UL=2565.0 MHz
>>>> set TX frequency to 2684999936
>>>> set RX frequency to 2564999936
>>>> Setting Sampling frequency 11.52 MHz
>>>> Set RX sampling rate 11.52 Mhz, filter BW: 10.00 Mhz
>>>>
>>>> ==== eNodeB started ===
>>>> Type <t> to view trace
>>>> ^CStopping srsENB... Press Ctrl+C 9 more times to force stop
>>>> Warning could not stop properly PHY
>>>> --- exiting ---
>>>>
>>>> XXXXXXXXXXXXXXX
>>>> sudo srsue --log.all_level=info
>>>> Reading configuration file /home/moe/.config/srslte/ue.conf...
>>>>
>>>> Built in Release mode using commit 5343b33f on branch master.
>>>>
>>>> --- Software Radio Systems LTE UE ---
>>>>
>>>> Opening 1 RF devices with 1 RF channels...
>>>> Opening bladeRF...
>>>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>>>> Waiting PHY to initialize...
>>>> ...
>>>> Attaching UE...
>>>> Searching cell in DL EARFCN=3400, f_dl=2685.0 MHz, f_ul=2565.0 MHz
>>>> set RX frequency to 2685000000
>>>> set TX frequency to 2565000000
>>>> Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz
>>>> ............................................^CStopping srsUE... Press
>>>> Ctrl+C 9 more times to force stop
>>>> .--- exiting ---
>>>>
>>>> please let me if you do need any necessary additional files. Thank you
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> srslte-users mailing list
>>>> srslte-users at lists.softwareradiosystems.com
>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>
>>> _______________________________________________
>>> srslte-users mailing list
>>> srslte-users at lists.softwareradiosystems.com
>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20190614/2ebb2f28/attachment.htm>
More information about the srsran-users
mailing list