This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRFCloud not accepting nrf9160 DK connection

I started a new ticket since I got a solution to not connecting to the cellular network. Apparently the iBasis sim is not working so I acquired a Hologram sim. I now can connect to the cellular network but the nrfcloud will not allow connection to the nrf9160 DK board. (see log below). I reflashed the asset tracker firmware, the modem firmware and created new certificates and successfully loaded the certificates into the nrf9160 DK.  I then installed the Hologram SIM. I also did a "reset device" in the NRFCloud before I generated the certificates since I did have this board working and connecting last July. 

I would appreciate any suggestions.

Following are the hardware software specifics I have.

nrf9160 DK  Hardware: PCA10090, 0.9.0,  2019 19

Asset tracker firmware: "\Nordic\nrf9160dk_fw_2021-03-01_8e8c6089\img_app_bl\nrf9160dk_asset_tracker_ltem_2021-03-01_8e8c6089.hex"

Modem Firmware: "\Nordic\nrf9160dk_fw_2021-03-01_8e8c6089\mfwnrf9160123.zip"

NRFConnect Programmer: v1.4.11

NRFConnect LTE Link Monitor: v1.1.10

Log file:

2021-06-18T04:00:19.297Z DEBUG modem << [00:00:02.062,957] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-06-18T04:00:19.994Z DEBUG modem << +CEREG: 5,"800B","07551811",7,,,"11100000","11100000"
2021-06-18T04:00:20.005Z DEBUG modem << [00:00:02.766,754] [0m<inf> asset_tracker: Connected to LTE network.[0m
2021-06-18T04:00:20.064Z DEBUG modem << [00:00:02.773,345] [0m<inf> asset_tracker: Connecting to cloud, attempt 1 of 8[0m
2021-06-18T04:00:20.067Z DEBUG modem << [00:00:02.780,731] [0m<inf> asset_tracker: Cloud connection request sent.[0m
2021-06-18T04:00:20.070Z DEBUG modem << [00:00:02.787,658] [0m<inf> asset_tracker: Connection response timeout is set to 30 seconds.[0m
2021-06-18T04:00:20.073Z DEBUG modem << [00:00:02.796,325] [0m<inf> asset_tracker: Network registration status: Connected - roaming[0m
2021-06-18T04:00:20.076Z DEBUG modem << [00:00:02.804,779] [0m<inf> asset_tracker: PSM parameter update: TAU: -1, Active time: -1[0m
2021-06-18T04:00:20.079Z DEBUG modem << [00:00:02.813,201] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2021-06-18T04:00:20.081Z DEBUG modem << [00:00:02.821,655] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
2021-06-18T04:00:20.923Z DEBUG modem << [00:00:03.688,995] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 address: 52.201.133.155[0m
2021-06-18T04:00:20.959Z DEBUG modem << [00:00:03.697,296] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: MQTT clean session flag: 1[0m
2021-06-18T04:00:20.962Z DEBUG modem << [00:00:03.714,111] [0m<inf> asset_tracker: DATE_TIME_OBTAINED_NTP[0m
2021-06-18T04:00:21.944Z DEBUG modem << [00:00:04.709,289] [0m<dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect failed -95[0m
2021-06-18T04:00:21.982Z DEBUG modem << [00:00:04.717,620] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTING[0m
2021-06-18T04:00:21.984Z DEBUG modem << [00:00:04.726,104] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTING[0m
2021-06-18T04:00:21.990Z DEBUG modem << [00:00:04.732,177] [1;31m<err> asset_tracker: Failed to connect to cloud, error -8[0m
2021-06-18T04:00:21.992Z DEBUG modem << [00:00:04.739,929] [1;31m<err> asset_tracker: Ensure device has a valid CA and client certificate[0m
2021-06-18T04:00:22.029Z DEBUG modem << [00:00:04.748,992] [1;31m<err> asset_tracker: Device will reboot in 300 seconds[0m
2021-06-18T04:00:22.032Z DEBUG modem << [00:00:04.756,469] [1;31m<err> asset_tracker: LTE link disconnect[0m
2021-06-18T04:00:22.090Z DEBUG modem << +CEREG: 0,"800B","07551811",7,0,0,"11100000","11100000"
2021-06-18T04:00:23.651Z DEBUG modem << +CSCON: 0
2021-06-18T04:00:23.685Z DEBUG modem << [00:00:06.425,415] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-06-18T04:00:23.899Z DEBUG modem << [00:00:06.667,022] [1;31m<err> asset_tracker: Shutdown modem[0m

Parents
  • Thanks for the feedback, Eric!

    Instead of resetting the device in the nRF Could, could you just remove it and create new certificates afterwards. Before downloading them to the device, I would recommend you to delete all remaining certificates using the %CMNG AT command.

    The following command example deletes a client certificate with tag 123:
    AT%CMNG=3,123,1 OK

    You can add the device again afterwards following this procedure.

    Before running the Asset Tracker, you might wanna run through the AT client Testing procedure and check if your device can connect to the network without any problems.

    I hope this will solve your problem!

    Regards,

    Markus

Reply
  • Thanks for the feedback, Eric!

    Instead of resetting the device in the nRF Could, could you just remove it and create new certificates afterwards. Before downloading them to the device, I would recommend you to delete all remaining certificates using the %CMNG AT command.

    The following command example deletes a client certificate with tag 123:
    AT%CMNG=3,123,1 OK

    You can add the device again afterwards following this procedure.

    Before running the Asset Tracker, you might wanna run through the AT client Testing procedure and check if your device can connect to the network without any problems.

    I hope this will solve your problem!

    Regards,

    Markus

Children
Related