nRF9160 not connecting to LTE-M network

[AlinP]

Hi,

Last week we received Nordic's Thingy:91 development kit and prototyping platform for nRF9160.

The kit also included 1x iBasis SIM card. According to iBasis, LTE-M is the local cellular standard in Bucharest, Romania.

We've went trough registering the device on the nrfcloud and failed with the following error:

---

There was an error adding your device: No device found with id 'nrf-352656100830366'. Verify you are passing a valid device id and not a device name. Also ensure that your device is powered on and its LED(s) indicate that it is connected to nRFCloud. If the LED(s) do not indicate a connection, there may be a problem with your device certificate. In that case, search Nordic DevZone for "certificate update" for a possible solution.

---

So, we've then went troguht the certificate update process described over here. Since LTE-M cellular connectivity is not available with the pre-compiled thingy91_at_client and, since that is the only up-to-date binary file that supports long AT commands (3kB or higher), we had no choice but to go trough the hassle of installing all the necessary (God knows how many) tools for compiling our own binaries from the up-to-date releases.

As described in the Thingy:91 Firmware Update using MCUboot tutorial we've pre-compiled the v1.1.0 nRF Connect SDK with the following 2 modifications made to the source code:

1.  the CONFIG_AT_CMD_RESPONSE_MAX_LEN was modified from a default value of 2700 to a value of 3074
2.  the AT_HOST_STACK_SIZE was modified from a value of 512 to a value of 1024. This was done because the modem (Zephyr RTOS) was crashing with a stack overflow error with only the first modification made (CONFIG_AT_CMD_RESPONSE_MAX_LEN set to 3074)

From the obtained build directory, we've uploaded the app_update.bin via mcumgr app and then succesfully updated the certificates via LTE Link Monitor.

After all this steps, the board still refuses to connect to the LTE-M network. I'll attach some of the terminal monitor printscreens bellow.

Any help regarding the issue would be greatly appreciated!

[Øyvind]

Hello, 

According to iBasis, LTE-M is the local cellular standard in Bucharest, Romania.

Yes, this is correct, however with limited coverage. I would ask iBasis what limited coverage means. 

There was an error adding your device: No device found with id 'nrf-352656100830366'. Verify you are passing a valid device id and not a device name. Also ensure that your device is powered on and its LED(s) indicate that it is connected to nRFCloud. If the LED(s) do not indicate a connection, there may be a problem with your device certificate. In that case, search Nordic DevZone for "certificate update" for a possible solution.

There is currently a bug in nRF Cloud that we are working with. Your issue seems to be related to this issue. I will forward your IMEI information

Since LTE-M cellular connectivity is not available with the pre-compiled thingy91_at_client 

LTE-M or NB-IoT is irrelevant for the AT Client. You can configure both using AT client and the %XSYSTEMMODE command. Make sure to issue AT+CFUN=4 first, to turn off modem.

After all this steps, the board still refuses to connect to the LTE-M network. I'll attach some of the terminal monitor printscreens bellow.

Can you please provide full output from the LTE Link Monitor? Please issue the command AT%XMONITOR (as the example in the bottom of page) as well.

Thanks!

Kind regards,

Øyvind

[dvm_orbey]

Hi, I have the same problem when I try to connect the Thingy91. Here the message:

There was an error adding your device: No device found with id 'nrf-352656100766727'. Verify you are passing a valid device id and not a device name. Also ensure that your device is powered on and its LED(s) indicate that it is connected to nRFCloud. If the LED(s) do not indicate a connection, there may be a problem with your device certificate. In that case, search Nordic DevZone for "certificate update" for a possible solution.

[Øyvind]

Hello dvm_orbey,

Yes, there is an issue that we are working to solve. As soon as I have more information I will post an answer here.

Kind regards,
Øyvind