Unable to connect to Cloud using Asset Tracker on nRF9160 DK

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Thu, 08 Jul 2021 09:36:31 GMT

Hi, the trace file you provided was empty.

Did you make sure to enable CONFIG_NRF_MODEM_LIB_TRACE_ENABLED in your application?

You can also send AT%XMODEMTRACE=1,2 to the modem for good meaure, even though enabling the config should take care of that.

And then make sure that the file size of the trace increases in the Trace Collector application as the device is running.

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Mon, 05 Jul 2021 08:02:59 GMT

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_07_2D00_05T07_2D00_01_2D00_26.414Z.bin devzone.nordicsemi.com/.../2021_2D00_07_2D00_05T06_5F00_41_5F00_13.741Z_2D00_log.txt

Hello, please check the .bin and log in attachments. Modem FW is mfwnrf9160123 (mfw_nrf9160_1.3.0 does not work for unknow reason, log attached). NCS version 1.6.0; HW version 0.8.3 2019.1.

devzone.nordicsemi.com/.../mfw_5F00_nrf9160_5F00_1.3.0-DNW-2021_2D00_07_2D00_05T06_5F00_36_5F00_56.451Z_2D00_log.txt

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Wed, 30 Jun 2021 10:38:53 GMT

Thank you for the log!

To investigate the issue further, please use the Trace Collector application in nRF Connect for Desktop to capture a modem trace from the nRF9160 DK when using the China Telecom card to connect (see Collecting a modem trace for the nRF9160 DK).

Then provide me with the resulting .bin file and the corresponding log file from the application, as well as the modem FW version, NCS version and HW revision of the nRF9160 DK.

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Wed, 30 Jun 2021 08:12:28 GMT

Hello, Heidi. Thank you for your reply. The attachment is the log. I remove the device from my cloud, reinstall the hex file, and update modem firmware. Then I download and update the certificate from cloud. After that, I insert China Mobile NB card, turn on the dev kit and connect it back to my cloud.devzone.nordicsemi.com/.../2021_2D00_06_2D00_30T08_5F00_05_5F00_24.885Z_2D00_log.txt

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Wed, 30 Jun 2021 07:48:37 GMT

Hi, please attach the log when connecting with China Mobile NB-IoT card.

To investigate the issue further, we're going to need a modem trace from the China Telecom NB-IoT card.

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Wed, 30 Jun 2021 01:28:09 GMT

Hello, I'm afraid it's not a nrf cloud certificate issue as I can use China Mobile NB-IoT card without any problem now.

After confirming that I removed my devices from my account, downloaded the certificate again. Then made changes in proj.conf file, update the certificate on the dev kit, and start using China Telecom NB-IoT card. The log is as recorded: devzone.nordicsemi.com/.../2021_2D00_06_2D00_30T01_5F00_14_5F00_12.152Z_2D00_log.txt

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Tue, 29 Jun 2021 08:33:03 GMT

It looks like the issue is still your certificates.

Could you show me exactly what information you are putting in to nRF Connect for Cloud in the "Device Certificates" card before generating the certificates?

And show me the log output from when you are updating the certificates.

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Mon, 28 Jun 2021 07:45:58 GMT

Hello,Heidi,

I added "CONFIG_ZZHC=y" to the prj.conf file, but the dev kit is still unable to connect to nrf cloud. I tried to update the certificate as well. The attachment is the logdevzone.nordicsemi.com/.../2021_2D00_06_2D00_28T06_5F00_25_5F00_16.287Z_2D00_log.txt

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Fri, 25 Jun 2021 09:34:08 GMT

I see. Yes, that is a bit confusing.

You can just add "CONFIG_ZZHC=y" to the prj.conf file, no need to do anything with it in the Kconfig, since it's already defined here.

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Wed, 23 Jun 2021 08:51:23 GMT

Hello, I haven't not added it yet. I'm not sure the correct to do the following:

Configure the following option if you want to use this library:

CONFIG_TRUSTED_EXECUTION_NONSECURE

In Kconfig, enable CONFIG_ZZHC.

In other public posts, I saw others also raised similar questions

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Wed, 23 Jun 2021 07:32:11 GMT

Hi, it doesn't look like you've added "CONFIG_ZZHC=y" to the prj.conf file?

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Wed, 23 Jun 2021 03:51:02 GMT

Hello, please have a look, I have to put .txt as a suffix to get Kconfig uploaded:

devzone.nordicsemi.com/.../4237.prj.conf devzone.nordicsemi.com/.../Kconfig-_2D00_-copy.txt

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Tue, 22 Jun 2021 10:58:40 GMT

[quote user="AlbertSerica"]The asset tracker connected to the Internet after a few minutes. [/quote]

Not in the first log you provided. I thought those logs were from two different SIM cards.

[quote user="AlbertSerica"]The problem I encountered seems to be related to zzhc library, there is a page about zzhc but it's not clear about how to use it:[/quote]

Please provide your prj.conf file and Kconfig file and I will take a look.

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Tue, 22 Jun 2021 02:31:55 GMT

Hello,

China doesn't have LTE-M so only NB-IoT is used. CEREG returns 9.

Blinking in cross pattern (LED 1 and 4, LED 2 and 3): Communication error with the nRF Connect for Cloud.

The asset tracker connected to the Internet after a few minutes.

2021-06-15T01:56:50.457Z DEBUG modem << [00:00:10.103,912] [0m<inf> asset_tracker: Connected to LTE network.[0m

The problem I encountered seems to be related to zzhc library, there is a page about zzhc but it's not clear about how to use it:

developer.nordicsemi.com/.../zzhc.html

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Wed, 16 Jun 2021 09:29:53 GMT

Hi!

1. When using the Chine Mobile Cellphone SIM, is it connecting through LTE-M or NB-IoT? The +CEREG response field AcT will return 7 for LTE-M and 9 for NB-IoT.

2. You say LED1 and LED4 blinks at last, which isn't one of the defined application states (see Asset Tracker: User interface). Could you take a look at the documentation and tell me if the LED blinking pattern matches any of them?

3. From the iBasis log it doesn't look like it's done connecting to the network. Please wait at least 10 minutes as it can take a while for the device to connect to the network and to nRF Cloud.

[00:00:00.343,688] [0m<inf> asset_tracker: Connecting to LTE network.[0m
[00:00:00.350,280] [0m<inf> asset_tracker: This may take several minutes.[0m
+CEREG: 2,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
[00:00:58.980,285] [0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: 65534[0m

4. As for the issues with China Telecom NB-IoT SIM, we're going to need a modem trace to investigate further (see Collecting a modem trace for the nRF9160 DK).

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Tue, 15 Jun 2021 02:59:33 GMT

Hello, Heidi,

Thanks for your reply, but I'm afraid it's not a certificate issue.

I download the certificate this morning to do the test again. The result is the same. While using China Telecom IOT card, LED3 blinks first, then LED4 blinks, LED1 and LED4 blinks at last. While using China Mobile 4G cellphone card, the DK can connect to cloud. Below is the log when I use China Telecom IOT card:

devzone.nordicsemi.com/.../2021_2D00_06_2D00_15T01_5F00_55_5F00_56.334Z_2D00_log.txt

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

Heidi — Mon, 14 Jun 2021 13:17:42 GMT

First of all, please stop posting the logs like that, it makes the whole post really difficult to read. Use this button in LTE Link Monitor to get the log as a text file, and then you can either save the file or copy the text from there.

Here is the log you posted, cleaned up.

+CSCON: 1
[00:00:08.419,586][0m<inf> asset_tracker: RRC mode: Connected[0m 
+CEREG: 1,"765E","075D6450",9,,,"11100000","00111000"
[00:00:10.095,031][0m<inf> asset_tracker: Connected to LTE network.[0m
[00:00:10.101,623][0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8[0m
[00:00:10.109,039][0m<inf> asset_tracker: Cloud connection request sent.[0m 
[00:00:10.115,966][0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.[0m
[00:00:10.124,664][0m<inf> asset_tracker: Network registration status: Connected - home network[0m
[00:00:10.133,544][0m<inf> asset_tracker: PSM parameter update: TAU: 86400, Active time: -1[0m
[00:00:10.142,242][0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
[00:00:10.150,695][0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
[00:00:20.343,505][0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 54.166.31.114[0m
[00:00:20.351,715][0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 0[0m
[00:00:25.044,555][1;33m<wrn> date_time: sntp_query, error: -116[0m
[00:00:32.817,443][1;33m<wrn> date_time: sntp_query, error: -116[0m
[00:00:38.944,549][1;33m<wrn> date_time: sntp_query, error: -116[0m
[00:00:44.977,661][1;33m<wrn> date_time: sntp_query, error: -116[0m
[00:00:51.057,739][1;33m<wrn> date_time: sntp_query, error: -116[0m
[00:00:51.064,270][1;33m<wrn> date_time: Not getting time from any NTP server[0m
[00:00:51.072,357][0m<inf> asset_tracker: DATE_TIME_OBTAINED_MODEM[0m
+CSCON: 0 
[00:01:16.166,137][0m<inf> asset_tracker: RRC mode: Idle[0m
+CSCON: 1
[00:01:21.380,767][0m<inf> asset_tracker: RRC mode: Connected[0m
+CSCON: 0 
[00:01:43.162,567][0m<inf> asset_tracker: RRC mode: Idle[0m
+CSCON: 1
[00:02:13.541,534][0m<inf> asset_tracker: RRC mode: Connected[0m
+CSCON: 0
[00:02:35.173,370][0m<inf> asset_tracker: RRC mode: Idle[0m
[00:03:00.723,693][0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -22[0m
[00:03:00.732,025][0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
[00:03:00.740,509][0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
[00:03:00.746,582][1;31m<err> asset_tracker: Failed to connect to cloud, error -7[0m
[00:03:00.754,333][1;31m<err> asset_tracker: Ensure device has a valid private key[0m
[00:03:00.762,145][1;31m<err> asset_tracker: Device will reboot in 300 seconds[0m
[00:03:00.769,653][1;31m<err> asset_tracker: LTE link disconnect[0m
+CSCON: 1
[00:03:01.222,259][0m<inf> asset_tracker: RRC mode: Connected[0m
+CEREG: 0,"765E","075D6450",9,0,0,"11100000","11100000" 
+CSCON: 0
[00:03:06.757,415][0m<inf> asset_tracker: RRC mode: Idle[0m
[00:03:07.170,684][1;31m<err> asset_tracker: Shutdown modem[0m

From your logs, it looks like nRF Cloud isn't accepting the certificates that are on the device. Have you made sure to update the certificates?

Best regards,

Heidi

RE: Unable to connect to Cloud using Asset Tracker on nRF9160 DK

AlbertSerica — Thu, 10 Jun 2021 02:35:25 GMT

I tried to configure ZZHC in asset_tracker, but still not working and only LED3 is blinking:

*** Booting Zephyr OS build v2.4.99-ncs2  ***
[00:00:00.212,280] [0m<inf> asset_tracker: Asset tracker started[0m
[00:00:00.218,444] [0m<inf> watchdog: Watchdog timeout installed. Timeout: 60000[0m
[00:00:00.225,952] [0m<inf> watchdog: Watchdog started[0m
[00:00:00.231,262] [0m<inf> watchdog: Watchdog feed enabled. Timeout: 30000[0m
[00:00:00.239,044] [0m<dbg> nrf_cloud_transport.nct_settings_set: Settings key: p_sesh, size: 4[0m
[00:00:00.247,863] [0m<dbg> nrf_cloud_transport.nct_settings_set: Read setting val: 1[0m
[00:00:00.262,878] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100109613[0m
[00:00:00.271,972] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100109613/shadow[0m
[00:00:00.283,538] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100109613/shadow/get/accepted[0m
[00:00:00.294,921] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100109613/shadow/get/rejected[0m
[00:00:00.307,342] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100109613/shadow/update/delta[0m
[00:00:00.320,129] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100109613/shadow/update[0m
[00:00:00.331,848] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100109613/shadow/get[0m
[00:00:00.343,688] [0m<inf> asset_tracker: Connecting to LTE network.[0m
[00:00:00.350,280] [0m<inf> asset_tracker: This may take several minutes.[0m
+CEREG: 2,"FFFE","FFFFFFFF",7,0,0,"11100000","11100000"
[00:00:58.980,285] [0m<inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: 65534
[0m