Thingy:91 Asset Tracker v2: nrfcloud not connecting

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

Håkon Alseth — Wed, 16 Feb 2022 08:29:28 GMT

Hi,

Could you send me a private message with your address + phone number, so I can ship a replacement device to you?

Kind regards,

Håkon

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

beshan — Tue, 15 Feb 2022 08:28:06 GMT

Yes, I tried multiple USB cables and multiply PCs. Same result, doesnt turn on.

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

Håkon Alseth — Tue, 15 Feb 2022 07:47:56 GMT

Hi,

Does the same behavior occur if you change the usb cable, and/or test with another PC?

Kind regards,

Håkon

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

beshan — Sun, 13 Feb 2022 13:27:33 GMT

Thank you for the lengthy reply. Sadly my Thingy91 doesn't get recognized anymore. When I plug in with the USB and turn it on, the serial port doesn't open, Nordic Desktop doesn't see it. I have verified that the switch and the voltages from USB and Battery work, but the 1v8 and 3v3 rails are showing zero. It was working fine and I was running an experiment debugging MQTT when it just suddenly stopped working. Any way I can get it to boot again or debug any hardware failures ?

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

Håkon Alseth — Wed, 09 Feb 2022 12:37:47 GMT

Hi,

I think you're mixing different ways of fetching the certificates for your device.

The below is essentially these two guides:

https://infocenter.nordicsemi.com/topic/ug_nrf91_dk_gsg/UG/nrf91_DK_gsg/downloading_certificate.html?cp=2_0_4_2_3_0

https://infocenter.nordicsemi.com/topic/ug_nrf91_dk_gsg/UG/nrf91_DK_gsg/provisioning_certificate.html?cp=2_0_4_2_3_1

If you log in to your nrfcloud account, then navigate to:

* Device Management -> provision devices

Then you click on the cog-wheel and press "generate JITP certificates"

Then input your details on the back of the thingy91

Now it should provide you with a nrf-<>.cert.json file which you can load in the LTE Link Monitor -> Certificate Manager part:

Be sure to first place the device in flight mode (AT+CFUN=4) before clicking "update certificates".

Go back to the "terminal" tab to see that the certificates were loaded correctly, ie. modem returned "OK" for each.

Note: if you already have certs loaded on this sec_tag, you have to first check "delete".

Now, reset your device, it should try to connect and this should be present in the serial output:

...
[00:00:06.266,784] [1;31m<err> nrf_cloud_transport: MQTT input error: -128
[00:00:06.273,803] [1;31m<err> nrf_cloud_transport: Error disconnecting from cloud: -128
...

Now you click the large + sign in nrfcloud frontend, upper left corner, and input the imei + pin:

When the device tries to reconnect now, it should successfully connect to nrfcloud and show data similar to this:

Could you try this and see if it connects properly now?

Kind regards,

Håkon

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

beshan — Mon, 07 Feb 2022 15:17:18 GMT

Same result with the following two set via the Config NRF Menu in Segger. Does not connect. Any extra logs that I can enable to see why the connection is refused ?

CONFIG_PDN=y
CONFIG_PDN_LEGACY_PCO=y

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

beshan — Mon, 07 Feb 2022 14:23:32 GMT

Thank you for your reply, really appreciate it. Please see attached log file from reset onwards. I will try the PCO now and report back as soon as I am done.

devzone.nordicsemi.com/.../2022_2D00_02_2D00_07T13_5F00_56_5F00_01.373Z_2D00_log_2D00_send2.txt

RE: Thingy:91 Asset Tracker v2: nrfcloud not connecting

Håkon Alseth — Mon, 07 Feb 2022 13:31:47 GMT

Based on the timestamps, your firmware has been running for quite some time. How does the initial log look like from reset?

Based on the CESQ behavior, it seems that the initial connection to the cloud server is refused/disconnected, but it is hard to say without looking at the full log.

[quote user=""]I recompiled the Asset Tracker V2 with nbiot, and changed the URL to an IP address as the DNS translation is not working with my operator. Not sure why that is, but that needs further debug assistance. But for now I put this IP : 34.193.110.244. Is that the correct IP address ? Is that acceptable to change the URL to an IP ? [/quote]

Yes, this is one of the IPs to the nrf cloud aws.

Have you tried to use legacy PCO and see if DNS is then provided?

This is done by setting these configurations:

CONFIG_PDN=y
CONFIG_PDN_LEGACY_PCO=y

Kind regards,

Håkon