nRF9160-DK unable to connect to LTE-M network in Tokyo

[calexr]

I followed the tutorial here:

https://devzone.nordicsemi.com/tutorials/b/getting-started/posts/getting-started-with-nrf9160-dk?CommentId=98ebb127-8333-4fca-8409-53845d1e1401

in getting my nRF9160-DK setup, no problem. I was unable to connect to the nRF Cloud so I installed the AT Client to debug as many others have on this forum. I have tried multiple locations outdoors and have been unable to see any towers. The iBasis eSim should work and there should be LTE-M coverage. I am in central Tokyo.

Here is the output from AT Client:

***** Booting Zephyr OS v1.13.99-ncs2 *****

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 200265f0

Secure Boot: prepare to jump to Non-Secure image

***** Booting Zephyr OS v1.13.99-ncs2 *****

The AT host sample started

AT+CFUN?

+CFUN: 4

OK

AT+CFUN=1

OK

AT+CFUN?

+CFUN: 1

OK

AT+CGSN=1

+CGSN: "352656100038853"

OK

AT+CGMI

Nordic Semiconductor ASA

OK

AT+CGMM

nRF9120

OK

AT+CGMR

mfw-m1_nrf9160_0.6.6-46.prealpha

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

204080813512661

OK

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

AT+COPS=?

+COPS: 

OK

AT+COPS?

+COPS: 2

OK

What should I try next? Thank you!

[Håkon Alseth]

Hi,

mfw-m1_nrf9160_0.6.6-46.prealpha

 There is an update available for the modem, which you can find on this page: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF9160-DK/Download#infotabs

The modem dfu tool can be installed via python pip:

pip install nrf9160_mdm_dfu-0.10.0+dev-py3-none-any.whl

 

Then run the modem update function in the folder you have the new modem firmware:

cd path\to\modem\firmware && nrf9160_mdm_dfu --update

 

Could you check if the connection issues still remain after the modem update?

 

Kind regards,

Håkon

[calexr]

Thanks for the response.

I updated the firmware and regretfully no improvement.

[iBasis Tech Support]

Hi, 

Yes, we have seen connectivity over Softbank and NTT DoCoMo in Japan.  We will investigate what is going on with your IMSI and get back to you as soon as possible. 

Kind Regards,

iBasis Tech Support

[iBasis Tech Support]

Hi Calexr,

Please try Band 3.  It should connect with NTT Docomo and Softbank.

Regards,

iBasis Tech Support

[calexr]

Thank you for getting back to me.

By default the device should be scanning band's 3, 4, 13 and 20. Regardless I set the device to band 3:

AT%XBANDLOCK=2,"100"
OK

verified here:

AT%XCBAND=?
%XCBAND: (3)
OK

Regretfully, the device still sees no towers. Should I try an antenna (a recommended part # would be appreciated)? Other ideas?

Thanks.

[iBasis Tech Support]

Hi Calexr,

Try using Band 31.  Please let me know what is the result. 

Regards,

iBasis Tech Support

[calexr]

According to the documentation: "The modem can only operate on four certified bands: 3, 4, 13, and 20. The application cannot override this restriction."

I tried with

AT%XBANDLOCK=2,"1000000000000000000000000000000"

but it threw an error. I'd be happy to try, but not sure it's possible with my access on the board. Could someone from Nordic advise on whether this is possible? (And if so, how to do so)

Thanks.

[calexr]

As a follow up, I see here:

https://www.nordicsemi.com/Products/Low-power-Cellular-IoT/nRF9160-Certifications

you are seeking certifications for Telec (Japan) on bands 1 and 8. Should I be using one of these? 

[Håkon Alseth]

Hi,

 

To get the supported bands you can issue this AT command:

AT%XCBAND=?

31 is not a supported band at this time.

Kind regards,

Håkon

[calexr]

Hi,

Yes, as I wrote above I am aware only bands 3, 4, 13 and 20 are supported.

Does this mean the device should or should not work in Japan?

I am happy to wait, but I am getting conflicting requests from you (Nordic) and iBasis.

[iBasis Tech Support]

Hi Calexr,

Nordic has replied that band 31 is not supported at this time.  We apologize the confusion.  Please try the following using band 3:

 Make sure you see

• UART green
• Modem Green
• UICC Green
• Then
• LTE and PDN, or PDN and LTE

 

By

• Restart nRF9x Link Monitor
• Unplug/plug SIM card
• Check signal Strength

 

And slowly …

Let me know if this works.

Regards,

iBasis Tech Support

[Yusuke]

I can't connect to LTE with nRF9160 DK too. I also want to know how to solve this. I live in Tokyo.