Network issue to work with nRF9160 in INDIA

[Nikunj]

Hello,

I followed getting started guide given in the link below,

https://devzone.nordicsemi.com/tutorials/b/getting-started/posts/getting-started-with-nrf9160-dk

I started with "asset_tracker" default example and also activated iBasis SIM on nRF cloud. LED3 started flashing but LED4 not even after wait of 30 minutes.

I setup SDK successfully then flashed "at_client" for debugging I observed it stucks at LTE network searching.

I also tried with local operator's LTE SIM but it shows the same.

Thanks and Regards,

Nikunj Panchani

[Nikunj]

Hello Nordic community,

iBASIS sim connection comes into handheld mobile but in nRF9160 dk board it shows searching mode always for that reason I do contact with iBASIS they said that "We have checked and found SIM is activated at our end and also we are seeing uses.  Please refer attached screen shot and for NRF9160 board issue please check with your board provider."

help to solve this issue

Thanks and regards,

Nikunj

[Martin Lesund]

Hi Nikunj,

Based on iBasis network coverage it does not mention India, or more importantly that LTE-M or NB-IoT support has not yet been deployed in India: https://www.gsma.com/iot/deployment-map/

So when using the iBasis SIM in your smartphone it was using another technology than LTE-M/NB-IoT to communicate.

---

If the first things I mentioned where not the case I would have recommended: 

You to to update to the latest modem firmware version: https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs

Then I would really like you to run the at_client with LTE Link Monitor, and if it still has issues please provide the log from the output terminal.

Best Regards,

Martin L.

[Nikunj]

I flashed modern device firmware and at_client example to debug. I found that LTE in screen always shows yellow that means it is in LTE network searching mode but network is not coming even after wait of 30 minutes.

I posted logs below:

***** Booting Zephyr OS v1.13.99-ncs1-5025-g745326266d9c ****

 

Secure Boot: configure flash

Secure Boot: SPU: set region 0 as Secure

Secure Boot: SPU: set region 1 as Secure

Secure Boot: SPU: set region 2 as Secure

Secure Boot: SPU: set region 3 as Secure

Secure Boot: SPU: set region 4 as Secure

Secure Boot: SPU: set region 5 as Secure

Secure Boot: SPU: set region 6 as Secure

Secure Boot: SPU: set region 7 as Secure

Secure Boot: SPU: set Flash region 8 as Non-Secure

Secure Boot: SPU: set Flash region 9 as Non-Secure

Secure Boot: SPU: set Flash region 10 as Non-Secure

Secure Boot: SPU: set Flash region 11 as Non-Secure

Secure Boot: SPU: set Flash region 12 as Non-Secure

Secure Boot: SPU: set Flash region 13 as Non-Secure

Secure Boot: SPU: set Flash region 14 as Non-Secure

Secure Boot: SPU: set Flash region 15 as Non-Secure

Secure Boot: SPU: set Flash region 16 as Non-Secure

Secure Boot: SPU: set Flash region 17 as Non-Secure

Secure Boot: SPU: set Flash region 18 as Non-Secure

Secure Boot: SPU: set Flash region 19 as Non-Secure

Secure Boot: SPU: set Flash region 20 as Non-Secure

Secure Boot: SPU: set Flash region 21 as Non-Secure

Secure Boot: SPU: set Flash region 22 as Non-Secure

Secure Boot: SPU: set Flash region 23 as Non-Secure

Secure Boot: SPU: set Flash region 24 as Non-Secure

Secure Boot: SPU: set Flash region 25 as Non-Secure

Secure Boot: SPU: set Flash region 26 as Non-Secure

Secure Boot: SPU: set Flash region 27 as Non-Secure

Secure Boot: SPU: set Flash region 28 as Non-Secure

Secure Boot: SPU: set Flash region 29 as Non-Secure

Secure Boot: SPU: set Flash region 30 as Non-Secure

Secure Boot: SPU: set Flash region 31 as Non-Secure

Secure Boot: configure SRAM

 

 

Secure Boot: SPU: set SRAM region 0 as Secure

Secure Boot: SPU: set SRAM region 1 as Secure

Secure Boot: SPU: set SRAM region 2 as Secure

Secure Boot: SPU: set SRAM region 3 as Secure

Secure Boot: SPU: set SRAM region 4 as Secure

Secure Boot: SPU: set SRAM region 5 as Secure

Secure Boot: SPU: set SRAM region 6 as Secure

Secure Boot: SPU: set SRAM region 7 as Secure

Secure Boot: SPU: set SRAM region 8 as Non-Secure

Secure Boot: SPU: set SRAM region 9 as Non-Secure

Secure Boot: SPU: set SRAM region 10 as Non-Secure

Secure Boot: SPU: set SRAM region 11 as Non-Secure

Secure Boot: SPU: set SRAM region 12 as Non-Secure

Secure Boot: SPU: set SRAM region 13 as Non-Secure

Secure Boot: SPU: set SRAM region 14 as Non-Secure

Secure Boot: SPU: set SRAM region 15 as Non-Secure

Secure Boot: SPU: set SRAM region 16 as Non-Secure

Secure Boot: SPU: set SRAM region 17 as Non-Secure

Secure Boot: SPU: set SRAM region 18 as Non-Secure

Secure Boot: SPU: set SRAM region 19 as Non-Secure

Secure Boot: SPU: set SRAM region 20 as Non-Secure

Secure Boot: SPU: set SRAM region 21 as Non-Secure

Secure Boot: SPU: set SRAM region 22 as Non-Secure

Secure Boot: SPU: set SRAM region 23 as Non-Secure

Secure Boot: SPU: set SRAM region 24 as Non-Secure

Secure Boot: SPU: set SRAM region 25 as Non-Secure

Secure Boot: SPU: set SRAM region 26 as Non-Secure

Secure Boot: SPU: set SRAM region 27 as Non-Secure

Secure Boot: SPU: set SRAM region 28 as Non-Secure

Secure Boot: SPU: set SRAM region 29 as Non-Secure

Secure Boot: SPU: set SRAM region 30 as Non-Secure

Secure Boot: SPU: set SRAM region 31 as Non-Secure

Secure Boot: configure peripherals

Secure Boot: MSP_NS 200247e0

Secure Boot: prepare to jump to Non-Secure image

***** Booting Zephyr OS v1.13.99-ncs1-5025-g745326266d9c *****

The AT host sample started

AT

Ok

AT+CFUN?

+CFUN: 4

OK

AT+CFUN=1

Ok

AT+CFUN?

+CFUN: 1

Ok

AT+CGSN=1

+CGSN: "352656100031908"

OK

AT+CGMI

Nordic Semiconductor ASA

OK

AT+CGMM

nRF9160

OK

AT+CGMR

mfw-m1_nrf9160_0.6.8-131.alpha

OK

AT+CEMODE?

+CEMODE: 2

OK

AT%XCBAND=?

%XCBAND: (3,4,13,20)

OK

AT+CMEE?

+CMEE: 0

OK

AT+CMEE=1

OK

AT+CNEC?

+CNEC: 0

OK

AT+CNEC=24

OK

AT+CGEREP?

+CGEREP: 0,0

OK

AT+CGDCONT?

OK

AT+CGACT?

OK

AT+CGEREP=1

OK

AT+CIND=1,1,1

OK

AT+CEREG=2

Ok

AT+CEREG?

+CEREG: 2,4,"FFFE","FFFFFFFF",7

OK

AT%CESQ=1

OK

AT+CESQ

+CESQ: 99,99,255,255,255,255

OK

AT%XSIM=1

OK

AT%XSIM?

%XSIM: 1

OK

AT+CPIN?

+CPIN: READY

OK

AT+CPINR="SIM PIN"

+CPINR: "SIM PIN",3

OK

AT+CIMI

204080813513443

OK

 

[Martin Lesund]

As I stated in my previous post:

There is no current network for LTE-M or NB-IOT yet in India.

If you want to talk to someone local for more detailed information I would recommend to contact your distributor. 

I think that would be SM Electronics in your case.

[Nikunj]

Hello Martin,

Greetings of the day!!!

According to the thread:

https://www.gsma.com/iot/long-term-evolution-machine-type-communication-lte-mtc-cat-m1/

"LTE-M networks will co-exist with 2G, 3G, and 4G mobile networks and benefit from all the security and privacy features of mobile networks, such as support for user identity confidentiality, entity authentication, confidentiality, data integrity, and mobile equipment identification."

does it mean that it is not co-existed with current 4G mobile network in INDIA??

if it is not then do we have any MACRO in code that can convert LTE-M to existing 4G network?

Regards,

Nikunj