Several issues encountered with nrf9160 to AWS IOT

RE: Several issues encountered with nrf9160 to AWS IOT

Didrik Rokhaug — Wed, 09 Oct 2019 15:00:12 GMT

Hi, and again, sorry for the late reply. There has been a lot to do lately, but it looks like things have calmed down a bit.

First, you should avoid writing certificates on every reboot. They get stored in non-volatile memory in the modem, so there is no reason to write them every single time. If you write them on every reboot, you wear out the flash, and if you take a modem trace, the certificates would be present in the trace.

Second, if you disable PSM, do you still get the same connection stability issues?

What are the PSM values the network grants you? They may not be what you requested. You can check the PSM values with the %XMONITOR AT command.

Do you get any warnings when running CMake? If you are using SEGGER Embedded Studio, CMake warnings should pop up when loading the project in a window called "JavaScript Alert".

Are you still using NCS v1.0.0?

A modem trace might be helpful to see if there is anything wrong happening on the modem side. If you do not know how to capture a modem trace, you can follow this guide: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect

Best regards,

Didrik

RE: Several issues encountered with nrf9160 to AWS IOT

Panda H — Tue, 01 Oct 2019 16:51:59 GMT

As you can see from the log, after mqtt link is established, there is no more debugging information send out from nrf_cloud_transport and net_mqtt. I have set "NRF_CLOUD_LOG_LEVEL 4" and "MQTT_SOCKET_LOG_LEVEL 4". it seems like the main thread printk overrides the debug level log

RE: Several issues encountered with nrf9160 to AWS IOT

Didrik Rokhaug — Fri, 20 Sep 2019 08:04:44 GMT

Hi. Sorry for the long delay

Regarding my earlier comments, when using the newest modem firmware, a reset after setting the modem in "power off" should not be necessary, as it no longer powers off the AT command interface.

Regarding your point number 5, can you send me your log-related configurations, along with the log, and tell me what you were expecting to see?

Best regards,

Didrik

RE: Several issues encountered with nrf9160 to AWS IOT

Didrik Rokhaug — Tue, 17 Sep 2019 15:11:10 GMT

The new modem firmware works with both NCS v1.0.0 and master.

If the modem is set to power off, the only way to restart it is to do a reboot. Depending on your error handling, you might want to do that regardless of what error you receive, as they do in lte_ble_gateway.

If you do not want to reboot, just disconnect from the network/disable LTE-M/NB-IoT/GPS functionality what you want is to set the modem in offline-mode.

RE: Several issues encountered with nrf9160 to AWS IOT

Panda H — Tue, 17 Sep 2019 14:49:31 GMT

Shall I use modem firmware V1.0.1 with NCS master branch, or with NCS 1.0.0 tag?

Regarding to number 4, it is called when there is ERROR_NRF_CLOUD, as shown in lte_ble_gateway sample. But you are right, I shall set it to offline at least before modem is power on again.

RE: Several issues encountered with nrf9160 to AWS IOT

Didrik Rokhaug — Tue, 17 Sep 2019 14:05:49 GMT

Hi.

Can you try to update to the newest modem firmware version (v1.0.1) and see if that helps?

Regarding your point number 4. Does the modem automatically enter power off when losing connection, or are you setting it in power off?

When the modem enters power off, you have to reboot for it to turn on again. If you are setting it to power off, you probably want to set it to offline instead.

Best regards,

Didrik