cloud_connect failed: -95

[bensterl15]

Hello,

I am trying to run the asset tracker example on an nRF9160-DK and I get the following errors from the LTE Link Monitor:

2020-02-06T21:00:59.964Z DEBUG modem << cloud_connect failed: -95\x0D\x0A
2020-02-06T21:00:59.966Z DEBUG modem << LTE link disconnect\x0D\x0A

I followed the directions in the "Getting Started Assistant" and tried several board/SIM card combinations, but still cannot seem to fix this.

Also for the future, are these error codes documented anywhere? I checked the nRF Cloud Library documentation but could not find any error codes.

Thanks in advance!

[Heidi]

Hi, it looks like there's something wrong with the nRF Cloud certificates on the modem. Can you run through this tutorial and then try again?

Here is an application that supports long AT commands: nrf91dk_at_client_long_at_commands.hex

Yes, all errors are documented. However, there are two different error-libraries utilized, so you have to be aware of which one the application is using.

The asset_tracker application (which is what all the devices come shipped with) uses newlib, with the error codes found here. This is because the configuration NEWLBI_LIBC is enabled in this sample, as seen here.

If this config is not enabled in a sample, then it uses the minimal library, with error codes found here.

 

Hope this cleared up any confusion!

Best regards,

Heidi

[bensterl15]

Hi Heidi,

Thank you for your quick response! I successfully flashed the at_client_long_at_commands firmware you sent me and tried to go through the tutorial, but as soon as I try to input the device ID/HWID, I get the following error:

"There was an error adding your device. You might be trying to upgrade an older nRF91 development kit. Unless you update your device, you will have to click the "Have an old devkit without a PIN?" link below."

I tried to follow the instructions on the following page, but I can't connect to an LTE tower because cloud_connect fails with -95 anytime I try that. My board version is 0.8.2, but I got the same error on a 0.9.0 as well.

Please let me know how you suggest to proceed.

Thanks again,

Ben