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]

I'll have to check that out. Regarding the modem trace, I am looking at the documentation right now, Is it possible to run the LTE link monitor and the modem tracer simultaneously? 

No, but it is quite similar. I'll try to see if I can get a local NB-IoT sim card for testing. In terms of the other microcontroller, it is one with a BG96 modem. (Not Nordic). 

If it is indeed the network connection, I will need to investigate further. Previously, I mentioned that when it connected to the network, attempted to establish a connection to the cloud, and then failed, it would automatically disconnect from the network.

Thanks for the help so far.

[Øyvind]

dival said:

Regarding the modem trace, I am looking at the documentation right now, Is it possible to run the LTE link monitor and the modem tracer simultaneously?

Yes, this is possible. The modem trace uses it's own UART port. You can program the nrf9160dk_asset_tracker_v2_debug_nbiot_2022-06-02_880c82db.hex, which has modem trace enabled. 

After doing that you can open Trace Collector v2 from nRF Connect for Desktop

After clicking start, make sure to reset you nRF9160DK, then you should see the size of the file increase as it tries to connect. 

dival said:

terms of the other microcontroller, it is one with a BG96 modem. (Not Nordic). 

Please note that BG96 is not the same as nRF9160 as the latter does not support EDGE and GPRS. Did you verify that you connected via NB-IoT and not EDGE or GRPS? 

dival said:

If it is indeed the network connection, I will need to investigate further. Previously, I mentioned that when it connected to the network, attempted to establish a connection to the cloud, and then failed, it would automatically disconnect from the network.

As you are on a test network, please verify your setup in the gateway. 

[dival]

Øyvind said:

As you are on a test network, please verify your setup in the gateway. 

Thanks for letting me know. That is correct. However, I am not using CMW500, but an SDR to be more specific. I think it is best to try out the modem trace, gather some debug logs, and then move on to scenario 2. For now I don't think the setup is the issue.

Øyvind said:

Yes, this is possible. The modem trace uses it's own UART port. You can program the nrf9160dk_asset_tracker_v2_debug_nbiot_2022-06-02_880c82db.hex, which has modem trace enabled. 

After doing that you can open Trace Collector v2 from nRF Connect for Desktop

After clicking start, make sure to reset you nRF9160DK, then you should see the size of the file increase as it tries to connect. 

I'll give that a try, thanks for letting me know. So if I understand correctly, I need to flash an asset tracker debug, and I will be able to run trace collection v2 and change AT commands simultaneously? Please confirm if this is correct.

Øyvind said:

Please note that BG96 is not the same as nRF9160 as the latter does not support EDGE and GPRS. Did you verify that you connected via NB-IoT and not EDGE or GRPS? 

That is correct. Quectel BG96 also supports both LTE-M and NB-IoT as well. I did verify that it was connected to the NB-IoT. 

[Øyvind]

dival said:

I'll give that a try, thanks for letting me know. So if I understand correctly, I need to flash an asset tracker debug, and I will be able to run trace collection v2 and change AT commands simultaneously? Please confirm if this is correct.

Yes, I tested here, and seemingly work out of the box. Note that have captured modem traces on my kit before which may have enabled features. Please try and verify on your side. Best to leave it running for 15 - 30 minutes.

With the modem trace running you should be able to issue AT commands without any problems through the LTE Link Monitor.

dival said:

but a radio unit (SDR to be more specific). I think it is best to try out the modem trace, gather some debug logs, and then move on to scenario 2. I don't think it is the setup that is the issue.

Is there a reason for using this and not a standard network/SIM? 

[dival]

I Made a private ticket, Case ID: 298702

Because its another issue. Thanks. Please close this topic.