RE: Thingy 91. Failure to connect to nRF Cloud using Asset Tracker V2 NB-IoT

Øyvind — Tue, 15 Feb 2022 18:49:02 GMT

Petra, happy to hear that you were able to connect to nRF Cloud!

RE: Thingy 91. Failure to connect to nRF Cloud using Asset Tracker V2 NB-IoT

Petrified0110 — Tue, 15 Feb 2022 18:43:41 GMT

Hi Øyvind! Thank you for your quick response!

I managed to get my Thingy 91 connected to nRFCloud.

When I first added the APN using the AT+CGDCONT I kept on adding it to any CID besides the "0" one. I presume the application only checks if the first APN from the list works, and if it doesn't, it sends the error message.

Thank you for your help!

Petra

RE: Thingy 91. Failure to connect to nRF Cloud using Asset Tracker V2 NB-IoT

Øyvind — Tue, 15 Feb 2022 17:19:53 GMT

Hello Petra,

Thanks for providing the information that you have.

Edit: Can you please retry with programming the "legacy PCO" image?

[quote user=""]I am using NB-IoT by default since that is the only thing that my provider supports in my area[/quote]

Yes, this seems correct according to the GSMA Coverage Map.

That said, your device is receiving reject causes 14 and 19:

2022-02-14T15:18:27.895Z DEBUG modem << +CNEC_EMM: 14
2022-02-14T15:18:27.907Z DEBUG modem << +CEREG: 2,"3714","0144024D",9,0,14

2022-02-14T15:18:41.198Z DEBUG modem << +CNEC_ESM: 27,0
2022-02-14T15:18:41.220Z DEBUG modem << +CNEC_EMM: 19
2022-02-14T15:18:41.230Z DEBUG modem << +CEREG: 2,"0064","0DF52B5B",9,0,19

According to Network registration status notification +CEREG, the reject cause is defined as EPS Mobility Management (EMM) cause value, described in 3GPP TS 24.301 Annex A.

Cause #14 – EPS services not allowed in this PLMN
This EMM cause is sent to the UE which requests service, or if the network initiates a detach request, in a PLMN
which does not offer roaming for EPS services to that UE.
NOTE 2: Since only one list of forbidden PLMNs for packet services is maintained in the UE, then the "forbidden
PLMNs for GPRS service" is the maintained list and the forbidden PLMNs for EPS service is equivalent
to it.

Cause #19 – ESM failure
This EMM cause is sent to the UE when there is a failure in the ESM message contained in the EMM message.

The CNEC_ESM, EPS Session Management error:

Cause #27 – Missing or unknown APN
This ESM cause is used by the network to indicate that the requested service was rejected by the external packet
data network because the access point name was not included although required or if the access point name
could not be resolved.

Please inform your network provider about the errors and check if you have valid APN information.

Kind regards;
Øyvind