I have setup OpenLTE successfully and now testing with UE, but having some issues scanning the network on my phone. I cannot see the network. Following are the specification for my setup
Host machine: Intel Core i7 with Ubuntu 16.04; the setup is configured on host system
Radio used: USRP N210 series with Ethernet connectivty
phone: Huawei mate 10 lite, SamSung Galaxy s3, Samsung Galaxy Note5; I have configured apn as 'openlte' 'www.openLTE.com'
current CPU frequency is 3.60 GHz.
We are not able to see the network on phone. After lots of debugging, the only improvement I observed is that error is changed into warning. Is there anyone who has suceeded in scanning the network on phone? Kindly guide me where am I worng. I have tried multiple ways out.
Also I want to know what IP address should be given in ip_addr_start. Is it my machine address or device address? I have tried on both but still no luck.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, Billy how are you? Could you make any progress in this regard? I have the same problem.
I'm using the USPR ettus b200 board and the Alcatel one touch UE. I recommend that you enter the engineering mode on your cell phone if you are using Android, as is your case, sometimes this requires having root permission. However, there is a code, in my case it is the * # * # 4636 # * # *, which allows you to see the LTE band and earfcn to which the cell will connect, see attached image of a screenshot. Then, load this data on the page http://niviuk.free.fr/lte_band.php, this will allow you to set the earfcn in LTE_fdd_enodeb.
In particular, I'm using band 4 and earfcn 2225, but the cell phone still can see the network. I share the current configuration that I have.
A detail about the USIM cards, I'm using sysmocom s1j1, I recommend you read the instruction manual to set each parameter, this is important to register a user in the network, with add_user. When programming the cards, set the code ki and OP (OPC), where the latter must be the same as the code "OP = 63bfa50ee6523365ff14c1f45f88737d" by default in OPENLTE, this you can find in the path <liblte src="" liblte_security.cc=""> The code OP, is generated from the code ki and OPC, this is explained well in detail in the aforementioned instruction manual.</liblte>
I comment, and also take the opportunity to ask if it is that at first you had to deal with these problems? After setting all the parameters, as mentioned above, on port 30001 these errors appear.
08/28/2018 10:24:40.639300 error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (10231) does not match PHY (1)
08/28/2018 10:24:40.640363 error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (10232) does not match PHY (2)
08/28/2018 10:24:40.641427 error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (10233) does not match PHY (3)
08/28/2018 10:24:42.839579 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive
08/28/2018 10:24:42.842559 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive
08/28/2018 10:24:42.848865 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive
08/28/2018 10:24:42.849064 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive
08/28/2018 10:24:42.849157 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive
08/28/2018 10:24:50.875368 info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (-10238), skipping 0 subframes
08/28/2018 10:24:50.876419 info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (-10239), skipping 0 subframes
08/28/2018 10:24:50.877487 info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (0), skipping 0 subframes
08/28/2018 10:24:50.878496 error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (10230) does not match PHY (0)
08/28/2018 10:24:50.878698 info mac LTE_fdd_enb_mac.cc 407 MAC_dl_tti - PHY_dl_tti != 2 (-1), skipping 4 subframes
08/28/2018 11:00:57.232266 error radio LTE_fdd_enb_radio.cc 456 RX old time spec 9625929598 9625929600
08/28/2018 11:00:57.232523 error radio LTE_fdd_enb_radio.cc 464 RX overrun 9625931518 9625929600
08/28/2018 11:00:57.233852 info radio LTE_fdd_enb_radio.cc 424 RX modifying recv_size to sync 9625944958 9625943040
<<<
Did you have any of these errors, in any instance? and if you had them like you could solve them?
I hope that this can help you in something and I would really appreciate it if you had any progress in this regard since I find myself stuck in the same spot.
Hello,
I have setup OpenLTE successfully and now testing with UE, but having some issues scanning the network on my phone. I cannot see the network. Following are the specification for my setup
Host machine: Intel Core i7 with Ubuntu 16.04; the setup is configured on host system
Radio used: USRP N210 series with Ethernet connectivty
phone: Huawei mate 10 lite, SamSung Galaxy s3, Samsung Galaxy Note5; I have configured apn as 'openlte' 'www.openLTE.com'
current CPU frequency is 3.60 GHz.
current config of Openlte is
System Parameters:
band = 3
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 = 1842200000
dl_earfcn = 1572
dns_addr = C0A80101
enable_pcap = 1
ip_addr_start = C0A80A03
mac_direct_to_ue = 0
mcc = 001
mnc = 01
n_ant = 1
n_id_cell = 0
p0_nominal_pucch = -96
p0_nominal_pusch = -70
phy_direct_to_ue = 0
q_hyst = 0
q_rx_lev_min = -140
rx_gain = 30
search_win_size = 0
sib3_present = 0
sib4_present = 0
sib5_present = 0
sib6_present = 0
sib7_present = 0
sib8_present = 0
tracking_area_code = 1
tx_gain = 86
ul_center_freq = 1747200000
ul_earfcn = 19572
use_cnfg_file = 1
use_user_file = 1
start
ok
Logs:
sudo telnet 127.0.0.1 30001
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
04/24/2018 10:36:51.867037 info iface LTE_fdd_enb_interface.cc 779 LTE FDD ENB DEBUG INTERFACE
04/24/2018 10:37:01.513445 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw circular buffer empty on receive
04/24/2018 10:37:03.473174 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive
04/24/2018 10:37:03.473271 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive
04/24/2018 10:37:03.473393 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer empty on receive
04/24/2018 10:37:03.473421 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive
04/24/2018 10:37:03.473441 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rlc circular buffer empty on receive
04/24/2018 10:37:03.473468 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_rlc circular buffer empty on receive
04/24/2018 10:37:03.473501 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_pdcp circular buffer empty on receive
04/24/2018 10:37:03.473538 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_pdcp circular buffer empty on receive
04/24/2018 10:37:03.473560 warning msgq LTE_fdd_enb_msgq.cc 234 gw_to_pdcp circular buffer empty on receive
04/24/2018 10:37:03.473580 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rrc circular buffer empty on receive
04/24/2018 10:37:03.473600 warning msgq LTE_fdd_enb_msgq.cc 234 mme_to_rrc circular buffer empty on receive
04/24/2018 10:37:03.473616 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_mme circular buffer empty on receive
04/24/2018 10:37:17.423584 info mac LTE_fdd_enb_mac.cc 409 MAC_dl_tti - PHY_dl_tti != 2 (1), skipping 0 subframes
04/24/2018 10:37:17.423834 info mac LTE_fdd_enb_mac.cc 409 MAC_dl_tti - PHY_dl_tti != 2 (1), skipping 0 subframes
04/24/2018 10:37:17.423852 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive
04/24/2018 10:37:17.424702 info mac LTE_fdd_enb_mac.cc 409 MAC_dl_tti - PHY_dl_tti != 2 (0), skipping 0 subframes
04/24/2018 10:37:17.425803 info mac LTE_fdd_enb_mac.cc 409 MAC_dl_tti - PHY_dl_tti != 2 (-1), skipping 4 subframes
04/24/2018 10:37:47.846613 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive
04/24/2018 10:37:54.117069 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive
04/24/2018 10:38:11.371375 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive
We are not able to see the network on phone. After lots of debugging, the only improvement I observed is that error is changed into warning. Is there anyone who has suceeded in scanning the network on phone? Kindly guide me where am I worng. I have tried multiple ways out.
Also I want to know what IP address should be given in ip_addr_start. Is it my machine address or device address? I have tried on both but still no luck.
Thanks
Hello, Billy how are you? Could you make any progress in this regard? I have the same problem.
I'm using the USPR ettus b200 board and the Alcatel one touch UE. I recommend that you enter the engineering mode on your cell phone if you are using Android, as is your case, sometimes this requires having root permission. However, there is a code, in my case it is the * # * # 4636 # * # *, which allows you to see the LTE band and earfcn to which the cell will connect, see attached image of a screenshot. Then, load this data on the page http://niviuk.free.fr/lte_band.php, this will allow you to set the earfcn in LTE_fdd_enodeb.
In particular, I'm using band 4 and earfcn 2225, but the cell phone still can see the network. I share the current configuration that I have.
A detail about the USIM cards, I'm using sysmocom s1j1, I recommend you read the instruction manual to set each parameter, this is important to register a user in the network, with add_user. When programming the cards, set the code ki and OP (OPC), where the latter must be the same as the code "OP = 63bfa50ee6523365ff14c1f45f88737d" by default in OPENLTE, this you can find in the path <liblte src="" liblte_security.cc=""> The code OP, is generated from the code ki and OPC, this is explained well in detail in the aforementioned instruction manual.</liblte>
I comment, and also take the opportunity to ask if it is that at first you had to deal with these problems? After setting all the parameters, as mentioned above, on port 30001 these errors appear.
Did you have any of these errors, in any instance? and if you had them like you could solve them?
I hope that this can help you in something and I would really appreciate it if you had any progress in this regard since I find myself stuck in the same spot.
Regards!!
Diego G.
Last edit: Diego Gutierrez 2018-11-08