Can't Send Downlink Configuration Data Reliably From AWS-IoT Cloud To nrf9160

[JLCIOT]

We are having issues sending downlink configuration data to our custom nrf9160 hardware from AWS-IoT Cloud.

The nrf9160 modem firmware version we are using is 1.3.4

The nrf9160 SDK version we are using is 1.7.0.

We are able to see the downlink data from within the AWS IoT mqtt console being executed from within AWS IoT mqtt console when we subscribe to a topic.

An example topic is:  $aws/things/352656106334272/shadow/get/accepted/desired/cfg

What we notice is when we our hardware publish time is set to 120 seconds, we have 95 percent success rate in being able to send downlink configuration data to our hardware and change parameters.  When the publish time is set to 900 seconds or larger which is our default publish time in most applications, our success rate is around 10 percent.  It takes multiple tries before we are able to send the downlink configuration data.

Please advise on how we can debug this issue.

James

[Hakon]

Hello,

do you have a modem trace from this?

[JLCIOT]

Hakan,

When we try to enable the trace functionality in prj.config 

#CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y 

it fails to create the project with the error message: shown below:

CMake Error at C:/Nordic/v1.7.0/nrf/cmake/partition_manager.cmake:274 (message):

  Partition Manager failed, aborting.  Command:

We are using SDK Version 1.7.0.  Any idea on how to fix this error?

[Hakon]

JLCIOT said:

Any idea on how to fix this error?

Do you get the same error when building other samples?

[JLCIOT]

We have not in the past, but I will have the software developer try another sample and will get back to you!!!

[JLCIOT]

We are able to build the V1.7.0 Asset Tracker Program without an error.

However when we set #CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y

we get the same partition manager failed aborting error.

Hope this helps.

James

[Hakon]

That sounds strange. I will ask about this internally.

[Hakon]

Can you reproduce with an SDK sample and show the build output log? It's hard to tell what's going in without a log.