ASSET TRACKER V2 Modem problems:

[Paul Oberauer]

ASSET TRACKER V2 Modem problems:

 

I have set up asset tracker V2 for nRF9160 and it sends the messages (GPS, Temp, Hum, etc) and the corresponding timestamps, which I can also receive in AWS Iot. However, the current battery level is not sent. Did I miss something in the configuration or what could be the cause of this problem?

I have configured the project according to developer.nordicsemi.com/.../README.html

LTE-link monitor shows the following:

DEBUG modem << [00:16:00.385,803] [1;31m<err> modem_info_params: Link data not obtained: 20 -5[0m

DEBUG modem << [00:16:00.393,188] [1;31m<err> modem_info_params: Network data not obtained: -5[0m

DEBUG modem << [00:16:00.400,695] [1;31m<err> modem_module: mo> event_manager: MODEM_EVT_MODEM_DYNAMIC_DATA_NOT_READY[0m

DEBUG modem << [00:16:00.427,368] [1;31m<err> modem_info_params: Link data not_params: Network data not obtained: -5[0m

DEBUG modem << [00:16:00.442,291] [1;31m<err> modem_module: modem_info_params_get, error: -11[0m

DEBUG modem << DATA_NOT_READY[0m

[Markus Tacker (he/him)]

Can you confirm that device is actually connected to the cloud? It looks like the modem is not connected and therefore battery data is not available (it's part of them modem info).

[Paul Oberauer]

Hello Markus, thank you for your answer, the device is indeed not connected to the cloud. But how can it be that it is not connected? In the AWS IoT Core I receive the mqtt messages and the shadow object is also updated. I followed the following instructions to set up AWS IoT.

https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/software-and-protocols/posts/connecting-to-aws-cloud-services-using-the-nrf9160

I use the DynamoDB instead of S3.

Do you have a hint or reference what I am doing wrong? I would be very grateful for some help on how to connect the device to the cloud properly.

regards Paul

[Markus Tacker (he/him)]

The document you are referring to is for another sample attached in that document, configuration for the Asset Tracker v2 could be different: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker_v2/README.html#configuration

However, since you are getting data from the device to the cloud, I believe the setup is correct, so it could be an issue with the device.

Are you running the latest version of the modem firmware?

Which application (and version) are you running?

[Paul Oberauer]

I am using the Asset Tracker V2 which is included in nRF SDK v1.5.0 Toolchain Manager and the modem firmware mfwnrf9160123.zip.

I found the cause of the problem, the reason is Read the real-time clock value from the modem (CONFIG_MODEM_INFO_ADD_DATE_TIME). If I configure CONFIG_MODEM_INFO_ADD_DATE_TIME = 0 I also get the data from the modem.

[Markus Tacker (he/him)]

I see, as the docs state, if the network does not provide time information, the readout may fail: github.com/.../Kconfig