nRF9160 Multi cell location evaluation giving error -77

[Jason Jantzi]

Hi,

I am using nRF9160 multi cell location code on nRF9160-DK  PCA10090 version 0.15.0.

Modem FW has been updated to the latest 1.3.1 binary.

I am using LTE-M with AT&T SIM roaming on Rogers LTE-M network Band 12.

I am getting error -77 which I can't explain and neither can local AE.

I have Service Evaluation token enabled on nrfcloud which expires 12/31/2021.

The code has been modified with the following changes to prj.conf

CONFIG_MULTICELL_LOCATION_SERVICE_NRF_CLOUD=y

CONFIG_MULTICELL_LOCATION_SAMPLE_DEV_ID_IMEI=y

CONFIG_NRF_CLOUD=y

CONFIG_NRF_CLOUD_REST=y

CONFIG_MODEM_JWT=y

# Jason added

CONFIG_MULTICELL_LOCATION_LOG_LEVEL_DBG=y

CONFIG_NRF_CLOUD_REST_LOG_LEVEL_DBG=y

Here are the relevant lines of code which show the error.

2021-12-01T21:27:08.018Z DEBUG modem << [00:00:05.491,149] [0m<dbg> nrf_cloud_rest.do_connect: getaddrinfo() 18.204.124.14[0m
2021-12-01T21:27:08.021Z DEBUG modem << [00:00:05.500,122] [0m<dbg> nrf_cloud_rest.do_connect: Connecting to api.nrfcloud.com[0m
2021-12-01T21:27:11.528Z DEBUG modem << [00:00:09.011,901] [0m<dbg> nrf_cloud_rest.http_response_cb: HTTP: All data received, status: 403 Forbidden[0m
2021-12-01T21:27:11.555Z DEBUG modem << [00:00:09.022,705] [0m<dbg> nrf_cloud_rest.http_response_cb: Content/Total: 47/288[0m
2021-12-01T21:27:11.557Z DEBUG modem << [00:00:09.032,775] [1;31m<err> multicell_location_sample: Failed to acquire location, error: -77[0m

This appears to be a similar issue to other user at this case: https://devzone.nordicsemi.com/f/nordic-q-a/82229/case-about-example-multicell_location-multicell_location_sample-failed-to-acquire-location-error--77

I will attach full logs to this case.

[Øyvind]

Hello, 

And thank you for reporting this. Yes, a full log output and modem trace would be very good. I have forwarded this internally, and will get back to you when I have more answers. 

Edit: Can you please verify that you authentication / certificates are correct? "403 Forbidden" is often an indication that there is an issue with these. Please see the nRF Cloud documentation on Location Services

Kind regards,
Øyvind

[Jason Jantzi]

Have you been able to get any more answers internally?

I have done the certificates and authentication as below:

To generate an evaluation token in the portal:

1. Log in to the nrf Cloud portal.
2. Click the drop-down menu in the top right corner.
3. Click Account.
4. Under REST API Authentication Management, find Service Evaluation Token.
5. Click Generate Token. A window opens asking for confirmation.
6. Click OK to generate the token.
7. The token appears in the text field to the left of the Generate Token button. You can copy and paste it using your mouse or keyboard, or copy it by clicking the clipboard button next to the text field. The token no longer appears once it has expired.

My token is still active on nrfcloud, so not sure what else could be causing the issue.

Thanks,
Jason Jantzi

[Øyvind]

Hi Jason, 

My apologies for the late reply. 

From the Account menu, did you also update your certificates?

This process is still being improved, however, you will need to update the certificates and then delete the device from nRF Cloud interface. Afterwards you can ensure that certificates are updated and re-register your device to nRF Cloud. 

Let me know how this works for you

Kind regards,
Øyvind

[Jason Jantzi]

Hi,

I updated the certificate on the device successfully, then I erase the device from the nRFcloud.  However, upon provisioning new LTE device I get Troubleshoot nRF Code 40412.

Add LTE Device

×

There was an error adding your device: No device found for this id. The device has not yet been provisioned. Troubleshoot nRF Code 40412

To add a device to your account, enter the device ID and PIN or HWID. For Nordic hardware like the nRF91DK or Thingy:91, the device ID is "nrf-" followed by the 15 digit IMEI. Example: "nrf-123456789012345"

It no longer is able to find this device id.   LTE link monitor still yield -77 error.

[00:00:04.420,745] 

[0m<inf> multicell_location_sample: Device ID: nrf-352656106124657

[0m

[00:00:04.429,443] 

[0m<inf> multicell_location_sample: Current cell:

[0m

[00:00:04.436,584] 

[0m<inf> multicell_location_sample: 

MCC: 302

[0m

[00:00:04.443,359] 

[0m<inf> multicell_location_sample: 

MNC: 720

[0m

[00:00:04.450,134] 

[0m<inf> multicell_location_sample: 

Cell ID: 8889095

[0m

[00:00:04.457,672] 

[0m<inf> multicell_location_sample: 

TAC: 29600

[0m

[00:00:04.464,660] 

[0m<inf> multicell_location_sample: 

EARFCN: 5060

[0m

[00:00:04.471,801] 

[0m<inf> multicell_location_sample: 

Timing advance: 144

[0m

[00:00:04.479,644] 

[0m<inf> multicell_location_sample: 

Measurement time: 4122

[0m

[00:00:04.487,762] 

[0m<inf> multicell_location_sample: 

Physical cell ID: 360

[0m

[00:00:04.495,758] 

[0m<inf> multicell_location_sample: 

RSRP: 58

[0m

[00:00:04.502,563] 

[0m<inf> multicell_location_sample: 

RSRQ: 17

[0m

[00:00:04.509,338] 

[0m<inf> multicell_location_sample: *** No neighbor cells found ***

[0m

[00:00:04.518,188] 

[0m<inf> multicell_location_sample: Sending location request..

[0m

[00:00:04.602,447] 

[0m<dbg> nrf_cloud_rest.nrf_cloud_rest_cell_pos_get: URL: /v1/location/cell

[0m

[00:00:04.614,929] 

[0m<dbg> nrf_cloud_rest.nrf_cloud_rest_cell_pos_get: Payload: {"lte":[{"eci":8889095,"mcc":302,"mnc":720,"tac":29600,"earfcn":5060,"rsrp":-83,"rsrq":-11,"adv":144}]}

[0m

[00:00:04.827,941] 

[0m<dbg> nrf_cloud_rest.do_connect: getaddrinfo() 18.204.223.123

[0m

[00:00:04.837,005] 

[0m<dbg> nrf_cloud_rest.do_connect: Connecting to api.nrfcloud.com

[0m

[00:00:08.968,719] 

[0m<dbg> nrf_cloud_rest.http_response_cb: HTTP: All data received, status: 403 Forbidden

[0m

[00:00:08.979,522] 

[0m<dbg> nrf_cloud_rest.http_response_cb: Content/Total: 47/288

[0m

[00:00:08.989,654] 

[1;31m<err> multicell_location_sample: Failed to acquire location, error: -77

[0m

Let me know how to proceed?

[Øyvind]

Hi, and sorry for missing one important detail. You will need to program the Asset Tracker application in order for the device to provision