nRF Cloud - Not able to connct to it.

[dival]

Hi,

I'm currently using an nRF9160DK with an NB-IoT sim, and the problem I am currently having is that I cannot establish a connection with the nRF cloud. 

What have I tried?

1. I tried the following: https://infocenter.nordicsemi.com/pdf/nRF9160_DK_Getting_Started_Guide_v1.1.pdf section "Provisioning the nRF Connect for Cloud certificate" by opening the nRF connect, deselecting automatic requests, removed the sim card, entering AT+CFUN?4 to put the modem to offline state (and checked the state of the modem to ensure that it is off). I have loaded the JSON certificate and ensured that the security tag is set to "16842753" and then updated the certificate. The log message states "certificate updated completed.

2. Then I tried to power cycle the nRF9160DK and then inserted the SIM card to let the automatic requests run. It seems like it tries to connect to the nRF cloud but fails. I am not quite sure why this happens.

3. I also tried to add the LTE device to the nRF connection, but this was not working

The image that I have flashed to the board is nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db.

Additional things that I have tried

1. The SIM card supports NB-IoT, and there is coverage within my area.

3. I have tried another NB-IoT-supported IoT device to test out the sim card by doing a ping test to ensure that the connectivity is not the problem, and this seems to work fine. 

4. It seems like the nRF9160DK is able to connect to the eNB, and connect to the network, so that is not the problem. It seems to receive an IP address successfully, so this is not a problem.

3. I have tried to re-flash the nRF9160DK 

[dival]

Hi,

I have updated the topic. I will post more screenshots when it comes to the logs.

[Øyvind]

Hello, 

The official Getting Started guide can be found here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf9160_gs.html#getting-started-with-nrf9160-dk

What version of the nRF9160 Development Kit are you running? When generating new certificates, what device ID did you enter? 

You can test the connection to the LTE network by using the AT client, found in the precompiled package as well.

Please provide full log output from the application you are running on your device, as screenshots provide too little information. You can find the log output in the LTE link monitor on the bottom.

Kind regards,
Øyvind

[dival]

Hello, I'd like to say thanks for reaching back to me. You guys got back to me very quickly. I wasn't expecting that :)

In terms of the guide, that is the one I have followed to get started.

1) What version of the nRF9160 Development Kit are you running?: I assume you mean the FW version? I am running 2022-06-02_880c82db and I flashed nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db on the nRF9160 DK

2) When generating new certificates, what device ID did you enter: For the device ID, I used the IMEI that is given on the back side of the nRF9160DK. I tried entering nrf- at the start. In terms of the code, it is the same which is given on the backside.

3) You can test the connection to the LTE network by using the AT client, found in the precompiled package as well: I assume you mean the AT Client that is a part of the application and firmware?  I just want to clarify that it can connect to the NB-IoT network and receive an IP address during an attach procedure with the eNB.

4) In terms of the logs. I'll get back to you in a few with screenshots and various logs.

Thanks.

[Øyvind]

dival said:

I'd like to say thanks for reaching back to me. You guys got back to me very quickly. I wasn't expecting that :)

We try our best to get back to our customer as soon as possible :)

dival said:

I assume you mean the FW version? I am running 2022-06-02_880c82db and I flashed nrf9160dk_asset_tracker_v2_nbiot_2022-06-02_880c82db on the nRF9160 DK

I meant the HW itself. On the back the nRF9160DK you can find a sticker with version number under PCA10090

dival said:

For the device ID, I used the IMEI that is given on the back side of the nRF9160DK. I tried entering nrf- at the start. In terms of the code, it is the same which is given on the backside

Yes, this should be sufficient, along with the pin code or HWID (depending on what version you have). Make sure that you have entered correct IMEI number after "nrf-"

dival said:

I assume you mean the AT Client that is a part of the application and firmware? I haven't used Nordic before, but I assume you want me to try to run this on the VS code? I just want to make it clear that it is able to connect to the NB-IoT network and receive an IP address during an attach procedure with the eNB.

Yes, you can do that as well. In the precompiled package that you are using (2022-06-02_880c82db) you can also program a clean AT client which will only give you AT commands to test your connection to the network (not nRF Cloud). In LTE Link Monitor can you please issue AT command "AT+CFUN?", this will provide a lot of information. 

dival said:

In terms of the logs. I'll get back to you in a few with screenshots and various logs.

Yes, please. This should provide more information to us.

Kind regards,
Øyvind

[dival]

The version number is 1.1.0 (2022.23).

Regarding the AT+CFUN, here is the output of it:

2022-11-10T13:36:01.766Z DEBUG modem >> AT+CFUN?
2022-11-10T13:36:01.773Z DEBUG modem << +CFUN: 1
2022-11-10T13:36:01.775Z DEBUG modem << OK
2022-11-10T13:36:01.801Z DEBUG modem >> AT+CGSN=1
2022-11-10T13:36:01.807Z DEBUG modem << +CGSN: "351516172740326"
2022-11-10T13:36:01.809Z DEBUG modem << OK
2022-11-10T13:36:01.816Z DEBUG modem >> AT+CGMI
2022-11-10T13:36:01.824Z DEBUG modem << Nordic Semiconductor ASA
2022-11-10T13:36:01.827Z DEBUG modem << OK
2022-11-10T13:36:01.833Z DEBUG modem >> AT+CGMM
2022-11-10T13:36:01.839Z DEBUG modem << nRF9160-SICA
2022-11-10T13:36:01.840Z DEBUG modem << OK
2022-11-10T13:36:01.843Z DEBUG modem >> AT+CGMR
2022-11-10T13:36:01.851Z DEBUG modem << mfw_nrf9160_1.3.2
2022-11-10T13:36:01.853Z DEBUG modem << OK
2022-11-10T13:36:01.856Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.2] SerNr: 351516172740326
2022-11-10T13:36:01.859Z DEBUG modem >> AT+CEMODE?
2022-11-10T13:36:01.869Z DEBUG modem << +CEMODE: 0
2022-11-10T13:36:01.872Z DEBUG modem << OK.

[dival]

Here is some more logs:

2022-11-10T13:38:22.041Z DEBUG modem >> AT+CFUN?
2022-11-10T13:38:22.047Z DEBUG modem << +CFUN: 1
2022-11-10T13:38:22.063Z DEBUG modem << OK
2022-11-10T13:38:22.076Z DEBUG modem >> AT+CGSN=1
2022-11-10T13:38:22.090Z DEBUG modem << +CGSN: "351516172740326"
2022-11-10T13:38:22.092Z DEBUG modem << OK
2022-11-10T13:38:22.097Z DEBUG modem >> AT+CGMI
2022-11-10T13:38:22.104Z DEBUG modem << Nordic Semiconductor ASA
2022-11-10T13:38:22.105Z DEBUG modem << OK
2022-11-10T13:38:22.108Z DEBUG modem >> AT+CGMM
2022-11-10T13:38:22.115Z DEBUG modem << nRF9160-SICA
2022-11-10T13:38:22.123Z DEBUG modem << OK
2022-11-10T13:38:22.125Z DEBUG modem >> AT+CGMR
2022-11-10T13:38:22.132Z DEBUG modem << mfw_nrf9160_1.3.2
2022-11-10T13:38:22.133Z DEBUG modem << OK
2022-11-10T13:38:22.133Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.2] SerNr: 351516172740326
2022-11-10T13:38:22.137Z DEBUG modem >> AT+CEMODE?
2022-11-10T13:38:22.143Z DEBUG modem << +CEMODE: 0
2022-11-10T13:38:22.144Z DEBUG modem << OK
2022-11-10T13:38:22.148Z DEBUG modem >> AT%XCBAND=?
2022-11-10T13:38:22.156Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
2022-11-10T13:38:22.160Z DEBUG modem << OK
2022-11-10T13:38:22.165Z DEBUG modem >> AT+CMEE?
2022-11-10T13:38:22.169Z DEBUG modem << +CMEE: 1
2022-11-10T13:38:22.171Z DEBUG modem << OK
2022-11-10T13:38:22.175Z DEBUG modem >> AT+CNEC?
2022-11-10T13:38:22.179Z DEBUG modem << +CNEC: 24
2022-11-10T13:38:22.189Z DEBUG modem <<
2022-11-10T13:38:22.191Z DEBUG modem << OK
2022-11-10T13:38:22.195Z DEBUG modem >> AT+CGEREP?
2022-11-10T13:38:22.210Z DEBUG modem << +CGEREP: 1,0
2022-11-10T13:38:22.211Z DEBUG modem << OK
2022-11-10T13:38:22.215Z DEBUG modem >> AT+CIND=1,1,1
2022-11-10T13:38:22.220Z DEBUG modem << OK
2022-11-10T13:38:22.224Z DEBUG modem >> AT+CEREG=5
2022-11-10T13:38:22.230Z DEBUG modem << OK
2022-11-10T13:38:22.236Z DEBUG modem >> AT+CEREG?
2022-11-10T13:38:22.247Z DEBUG modem << +CEREG: 5,2
2022-11-10T13:38:22.249Z DEBUG modem << OK
2022-11-10T13:38:22.256Z DEBUG modem >> AT%CESQ=1
2022-11-10T13:38:22.269Z DEBUG modem << OK
2022-11-10T13:38:22.273Z DEBUG modem >> AT+CESQ
2022-11-10T13:38:22.286Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-11-10T13:38:22.288Z DEBUG modem << OK
2022-11-10T13:38:22.295Z DEBUG modem >> AT%XSIM=1
2022-11-10T13:38:22.305Z DEBUG modem << OK
2022-11-10T13:38:22.310Z DEBUG modem >> AT%XSIM?
2022-11-10T13:38:22.315Z DEBUG modem << %XSIM: 1
2022-11-10T13:38:22.316Z DEBUG modem << OK
2022-11-10T13:38:22.324Z DEBUG modem >> AT+CPIN?
2022-11-10T13:38:22.337Z DEBUG modem << +CPIN: READY
2022-11-10T13:38:22.339Z DEBUG modem << OK
2022-11-10T13:38:22.347Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-11-10T13:38:22.361Z DEBUG modem << +CPINR: "SIM PIN",3
2022-11-10T13:38:22.364Z DEBUG modem << OK
2022-11-10T13:38:22.373Z DEBUG modem >> AT+CIMI
2022-11-10T13:38:22.388Z DEBUG modem << OK
2022-11-10T13:38:23.918Z DEBUG modem >> AT+CESQ
2022-11-10T13:38:23.926Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-11-10T13:38:23.927Z DEBUG modem << OK