I just started working with openlte a few days ago and I noticed that most of the people trying to have it work are facing some problems such as too many warnings and errors appearing in the log and most of the time the enodeb is not visible to the phone. From what I have experienced, this is mostly a software issue rather than a hardware one, so no need to upgrade your PC, you should know what software to run.
I first tested openlte with the following configurations:
- ubuntu 15.10
- gnuradio 3.7.12
- UHD 3.10
- openlte 20.5
I tried the USRP B210 and the bladerf and both did not work !
then I tried the following:
- ubuntu 14.04.3 LTS
- gnuradio 3.7.11
- UHD 3.10
- openlte 20.5
with this configuration only the bladerf worked. Both test were done one the same PC using a VM.
From this I can say that most issues could be caused by the softwares versions that we are using. Also I encourage all those who were able to have their enodeb running to share their configuration with the rest so that we could all contribute to this awesome project.
Best regards,
Robert,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Would you mind sharing more info about bladeRF firmware and FPGA image (and libbladeRF version)?
I have bladeRF x115 but still can't make if work.
Also, I'd like to know how to make some tests with my existing phone. I know my IMEI and IMSI
but don't know the K? Is it possible to add subscriber without K?
Thanks,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I understand, it is not possible to have a user without the key. it is a two way authentication and both the basestation and the phone should have matching creds.
Have a look here - https://sourceforge.net/p/openlte/wiki/Programming%20you%20own%20USIM%20card/
openLTE supports only 'milenage',as you can see in the hss authentication/lte library code of openLTE
Thanks Robert. I've managed to match suggested version and got the enb running. I don't see excessive issue as I've seen before but I'm still not able to see the netwrok on my phone.
I'm getting a lot of these warnings:
warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive
warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive
And errors like this:
info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (0), skipping 0 subframes
error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (5254) does not match PHY (5264)
info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (-1), skipping 4 subframes
error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (5255) does not match PHY (5265)
Here's whay I have in configuration:
band = 20
bandwidth = 5
cell_id = 1
debug_level = radio phy mac rlc pdcp rrc mme gw user rb timer iface msgq
debug_type = error warning info debug
dl_center_freq = 811000000
dl_earfcn = 6350
I've used test and commercial mcc and mnc - none worked.
Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I suggest the following:
- if you are using a bladeRF stick with Bandwidth = 10
- try different bands as not all phones might be able to operate on all LTE bands
- try different values of dl_earfcn, I don’t know why but sometimes if I stay on the same band but slightly change the dl_earfcn the phone doesn’t detect the network. I had success with band 1, dl_earfcn 25.
hope this helps.
band = 20
bandwidth = 5
cell_id = 1
debug_level = radio phy mac rlc pdcp rrc mme gw user rb timer iface msgq
debug_type = error warning info debug
dl_center_freq = 811000000
dl_earfcn = 6350
I've used test and commercial mcc and mnc - none worked.
Robert thanks one more time. I've managed to get it to work with dl_earfcn 25. I've used bandwidth 5. Maybe you should update your first post with proposed ENB configuration.
I need to mention few more things. I've noticed that ENB is pretty much unstable. I guess that's because of bladeRF, same thing happens to me with srsLTE. Test PLMN 4G network just dissapears after two network scans in a row.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you pls provide the LTE configration software for bladeRF40. I need complete set of codes. i have loaded the same ver
bladeRF-cli version: 1.5.0-git-6116d09
libbladeRF version: 1.8.0-git-6116d09
Firmware version: 1.9.0
FPGA version: 0.6.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I still can't say why it crashes but what I know is that if you try the same configuration on a more powerful PC you should get better results for both bladeRF and USRP B2XX.
here are the results of my experiments:
- on a normal laptop:
--using bladeRF: phone can detect network but when I try to connect nothing happens as if the network is not receiving anything.
--using USRP B210: nothing detected, too many errors and warnings.
on a desktop with intel core i7 7700:
--using bladRF: phone detects the network and can connect to it.
--using USRP B210: phone detects the network and can connect to it.
hope this helps.
best regards,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OpenLTE 20.5 under Ubuntu 14.04.5 (Polarssl) and B210 runs better than under Ubuntu 16.04. It lasts longer until the SEGMENTATION FAULT. The OpenLTE host pings the UE for a while before the SEGMENTATION FAULT.
The ping from the EnodeB to UE (10.0.0.2) lasts for some seconds.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm glad you were able to detect and connect to OpenLTE under Ubuntu 14.04 and B210.
I'm using the same OS and hardware but have not succeeded with OpenLTE, even have not yet detected the network in my phone. Please help me.
The following is the system setup I am using:-
Processor: Intel Xeon(R)W-2145 CPU @ 3.70Ghz x 14 (It is a 8 core CPU)
Memory : 32 GB
OS : Ubuntu 14.04 LTS
OS type : 64 bit
USRP : NI USRP-2901 (the daughter board is same as B210)
OpenLTE : openlte_v00-20-05
I straight away followed the instructions given in the wiki to install, configure and run the OpenLTE. Still I had few issues in building gr-osmosdr and bladeRF drivers. But somehow going through certain other forums and articles, solved the issues and I successfully built the OpenLTE, and was able run the eNodeB. But again, the sad part, the network is not at all getting detected in my phone.
Could you please share the details of following you have used:-
1) Instructions followed to build the drivers (gnuradio, uhd,...) and OpenLTE.
2) OpenLTE configuration like the MCC, MNC, bandwidth, band, dl_earfcn, rx_gain, tx_gain, etc
3) Your system configuration (I dont know, if my Xeon PC doesnt support then which system should I go for)
4) The Antenna you have used ( Please provide the name/ manufacturer too)
5) The handset used to detect and connect to OpenLTE network.
Please provide me the details and save me from this frustration.
Thanks for your consideration.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I just started working with openlte a few days ago and I noticed that most of the people trying to have it work are facing some problems such as too many warnings and errors appearing in the log and most of the time the enodeb is not visible to the phone. From what I have experienced, this is mostly a software issue rather than a hardware one, so no need to upgrade your PC, you should know what software to run.
I first tested openlte with the following configurations:
- ubuntu 15.10
- gnuradio 3.7.12
- UHD 3.10
- openlte 20.5
I tried the USRP B210 and the bladerf and both did not work !
then I tried the following:
- ubuntu 14.04.3 LTS
- gnuradio 3.7.11
- UHD 3.10
- openlte 20.5
with this configuration only the bladerf worked. Both test were done one the same PC using a VM.
From this I can say that most issues could be caused by the softwares versions that we are using. Also I encourage all those who were able to have their enodeb running to share their configuration with the rest so that we could all contribute to this awesome project.
Best regards,
Robert,
Hello Robert,
Thanks for sharing this useful information.
Would you mind sharing more info about bladeRF firmware and FPGA image (and libbladeRF version)?
I have bladeRF x115 but still can't make if work.
Also, I'd like to know how to make some tests with my existing phone. I know my IMEI and IMSI
but don't know the K? Is it possible to add subscriber without K?
Thanks,
As I understand, it is not possible to have a user without the key. it is a two way authentication and both the basestation and the phone should have matching creds.
Have a look here - https://sourceforge.net/p/openlte/wiki/Programming%20you%20own%20USIM%20card/
openLTE supports only 'milenage',as you can see in the hss authentication/lte library code of openLTE
https://www.ebay.com/itm/LTE-Base-Station-Network-Test-SIM-Card-Blank-USIM-support-Milenage-algorithm-/121546310640?pt=LH_DefaultDomain_0&hash=item1c4cb983f0
Last edit: cynthiya 2017-10-29
I might be able to extract keys using modem commands so I'll try that.
Still can't get the network to be visible by my phone.
Hi,
these are info about bladeRF x40:
bladeRF-cli version: 1.5.0-git-6116d09
libbladeRF version: 1.8.0-git-6116d09
Firmware version: 1.9.0
FPGA version: 0.6.0
best regards,
Thanks Robert. I've managed to match suggested version and got the enb running. I don't see excessive issue as I've seen before but I'm still not able to see the netwrok on my phone.
I'm getting a lot of these warnings:
warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive
warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive
And errors like this:
info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (0), skipping 0 subframes
error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (5254) does not match PHY (5264)
info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (-1), skipping 4 subframes
error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (5255) does not match PHY (5265)
Here's whay I have in configuration:
band = 20
bandwidth = 5
cell_id = 1
debug_level = radio phy mac rlc pdcp rrc mme gw user rb timer iface msgq
debug_type = error warning info debug
dl_center_freq = 811000000
dl_earfcn = 6350
I've used test and commercial mcc and mnc - none worked.
Any ideas?
Hi,
I suggest the following:
- if you are using a bladeRF stick with Bandwidth = 10
- try different bands as not all phones might be able to operate on all LTE bands
- try different values of dl_earfcn, I don’t know why but sometimes if I stay on the same band but slightly change the dl_earfcn the phone doesn’t detect the network. I had success with band 1, dl_earfcn 25.
hope this helps.
Thanks for fast reply. Let me try that and I'll post an update.
Robert thanks one more time. I've managed to get it to work with dl_earfcn 25. I've used bandwidth 5. Maybe you should update your first post with proposed ENB configuration.
I need to mention few more things. I've noticed that ENB is pretty much unstable. I guess that's because of bladeRF, same thing happens to me with srsLTE. Test PLMN 4G network just dissapears after two network scans in a row.
Can you pls provide the LTE configration software for bladeRF40. I need complete set of codes. i have loaded the same ver
bladeRF-cli version: 1.5.0-git-6116d09
libbladeRF version: 1.8.0-git-6116d09
Firmware version: 1.9.0
FPGA version: 0.6.0
Thanks Mr. Robert Steve for your valuable information.
The OpenLTE 20.5 isn't working with USRP B210, it crashes with segmentation fault.
Is there anybody with a succesful running 20.5 with USRP B210 config?
Thanks
Erik
I still can't say why it crashes but what I know is that if you try the same configuration on a more powerful PC you should get better results for both bladeRF and USRP B2XX.
here are the results of my experiments:
- on a normal laptop:
--using bladeRF: phone can detect network but when I try to connect nothing happens as if the network is not receiving anything.
--using USRP B210: nothing detected, too many errors and warnings.
--using bladRF: phone detects the network and can connect to it.
--using USRP B210: phone detects the network and can connect to it.
hope this helps.
best regards,
I tried mbedtls and the UE just connects. With no traffic at all there will be no SEGMENTATION FAULT.
I will install an older UBUNTU with Polarssl and the newest release toc check the SEG FAULT.
OpenLTE 20.5 under Ubuntu 14.04.5 (Polarssl) and B210 runs better than under Ubuntu 16.04. It lasts longer until the SEGMENTATION FAULT. The OpenLTE host pings the UE for a while before the SEGMENTATION FAULT.
The ping from the EnodeB to UE (10.0.0.2) lasts for some seconds.
Hi Erik
I'm glad you were able to detect and connect to OpenLTE under Ubuntu 14.04 and B210.
I'm using the same OS and hardware but have not succeeded with OpenLTE, even have not yet detected the network in my phone. Please help me.
The following is the system setup I am using:-
Processor: Intel Xeon(R)W-2145 CPU @ 3.70Ghz x 14 (It is a 8 core CPU)
Memory : 32 GB
OS : Ubuntu 14.04 LTS
OS type : 64 bit
USRP : NI USRP-2901 (the daughter board is same as B210)
OpenLTE : openlte_v00-20-05
I straight away followed the instructions given in the wiki to install, configure and run the OpenLTE. Still I had few issues in building gr-osmosdr and bladeRF drivers. But somehow going through certain other forums and articles, solved the issues and I successfully built the OpenLTE, and was able run the eNodeB. But again, the sad part, the network is not at all getting detected in my phone.
Could you please share the details of following you have used:-
1) Instructions followed to build the drivers (gnuradio, uhd,...) and OpenLTE.
2) OpenLTE configuration like the MCC, MNC, bandwidth, band, dl_earfcn, rx_gain, tx_gain, etc
3) Your system configuration (I dont know, if my Xeon PC doesnt support then which system should I go for)
4) The Antenna you have used ( Please provide the name/ manufacturer too)
5) The handset used to detect and connect to OpenLTE network.
Please provide me the details and save me from this frustration.
Thanks for your consideration.