Not connecting to nRFCloud

[Yano]

Hi, we have an nRF9160DK (0.8.3) and it does not connect to the nrfcloud.

We have updated to the latest firmware 1.0.0

We only have nb-iot here so we  didn't use the iBasis sim, instead using a vodafone V-Sim (which is active). 

Are we missing a step here?

Thanks

[Martin Lesund]

Hi Ian,

That's strange.

Could you confirm that you wait at least ~5mins after turning ON the modem and then send the AT+CFUN? command?

The first time connecting to an nb-IoT network can take some time.

[Yano]

Hi Martin,

just to be clear we are able to connect to the internet (we get all green LEDS and and IP address) also we have in log "Connected to LTE network".

Does that not show the fault is with connecting to server not the internet?

Ian

[Didrik Rokhaug]

Hi.

-111 usually indicates that something is wrong with your certificates.

Can you try to follow the steps Hellesvikis describing in his comment here: https://devzone.nordicsemi.com/f/nordic-q-a/49650/asset_tracker-does-not-work-with-firmware-v1-0-0/199421#199421 and tell me the result?

Best regards,

Didrik

[Yano]

Hi Didrik,

Currently AT%CMNG=1 old gives an OK response (no data).

We have set CONFIG_AT_CMD_RESPONSE_MAX_LEN=2560 however we can no longer upload the code to the DK. The "build and run" option is grayed out. And when we get the error "Active project is not an executable"

So we are stuck :( The Jlink is there plus we can connect to device.

Do you have any idea what is causing this problem?  

Thanks 

[Didrik Rokhaug]

Hi.

Is it only when you have CONFIG_AT_CMD_RESPONSE_MAX_LEN =2560 in your prj.conf you have problems connecting to the device?

If so, I would not worry too much about it or try a lower number.

It looks like you are missing your nRF Cloud certificates. If you have previously registered the device to your nRF Cloud user, you can use the steps explained here to recover them.

Best regards,

Didrik

[Yano]

HI Didrik,

No putting back the setting has no affect.

Any ideas how I can get it to connect (we've tried re-starting the machine etc).

I can't find any documentation on this error.

Thanks

[Yano]

Hi Didrik,

I have no idea why it stopped working but we re-installed Segger and the project, this worked and it can connect / build+run etc again :)

We use Kiel here and are not familiar with Segger, it seems complex and buggy or maybe we just are not used to it.

We have never registered the device on the cloud so how would we have certificates?

Also how exactly do we get the certificates?

Using the URLs with our API Key in the Chrome window doesn't seem to work (we just get search results).

Here are the actual commands we are putting into URL text box: 

http api.nrfcloud.com/.../devices Authorization:"Bearer b8c3ad8b60e4abb110bb67421346f274586306e2"

POST api.nrfcloud.com/.../<device ID>/certificates Authorization:"Bearer b8c3ad8b60e4abb110bb67421346f274586306e2"

Are they formatted OK?

If we remove the http and POST we get this for both.

{
    "message": "Missing Authentication Token",
    "type":  "MISSING_AUTHENTICATION_TOKEN",
    "resourcePath":  "",
    "statusCode": "'404'"
}

Any ideas?

Ian

[Didrik Rokhaug]

Hi.

The "http" commands should be run in the command line after installing httpie. <device ID> should be replaced with the device ID you get from the first command.

However, if your device is not registered to your account in nRF Cloud you will not get any devices. I am working on what to do in that case and will come back to you as soon as I have an answer.

Best regards,

Didrik