STUCK LTE Connection

[nardoz-dev]

Hi all, i have some problem while i try to estabilish an LTE connection . 

I'm using nordic n9160dk. 

I just search through the site, and i see a lot of topic like this, or like this, or  this .. but none of them resolve my issue .. 

This problem happen only with Pelion SIM, with others from different operator i don't have any kind of problem.

I'm using modem fw 1.3.5 with AssetTracker_v2, then i open LTE Link Monitor v2.0.4

This is what i got from LTE Link Monitor.

AT+CFUN?
+CFUN: 1
OK
AT+CGSN=1
+CGSN: "350457791747379"
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9160-SICA
OK
AT+CGMR
mfw_nrf9160_1.3.5
OK
AT+CEMODE?
+CEMODE: 2
OK
AT%XCBAND=?
%XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
OK
AT+CMEE?
+CMEE: 1
OK
AT+CNEC?
+CNEC: 24
OK
AT+CGEREP?
+CGEREP: 1,0
OK
AT+CIND=1,1,1
OK
AT+CEREG=5
OK
AT+CEREG?
+CEREG: 5,2
OK
AT%CESQ=1
OK
AT+CESQ
+CeSQ: 99,99,255,255,3,40
OK
AT%XSIM=1
OK
AT%XSIM?
%XSIM: 1
OK
AT+CPIN?
+CPIN: READY
OK
AT+CPINR="SIM PIN"
+CPINR: "SIM PIN",3
OK
AT+CIMI272023132133352
OK
%CESQ: 42,2,6,0
+CEREG: 2,"7D1B","010BFD2A",7
%NCELLMEAS: 0,"010BFD29","22210","7D1B",0,525,480,46,26,1890117,525,369,43,19,0,525,326,30,-7,0,1685502
[00:30:01.732,055] [1;31m<err> modem_info_params: Link data not obtained: 5 -22[0m
[00:30:01.732,086] [1;31m<err> modem_module: modem_info_params_get, error: -22[0m
+CEREG: 2,"7D1B","010BFD2A",7,0,19
[00:30:01.732,147] [0m<inf> app_event_manager: MODEM_EVT_BATTERY_DATA_NOT_READY[0m
[00:31:31.626,892] [1;33m<wrn> location: GNSS timed out possibly due to too short GNSS time windows[0m
[00:31:31.641,296] [0m<inf> app_event_manager: LOCATION_MODULE_EVT_CLOUD_LOCATION_DATA_READY[0m
[00:31:31.641,784] [0m<inf> app_event_manager: LOCATION_MODULE_EVT_INACTIVE[0m
[00:31:31.642,364] [0m<inf> app_event_manager: DATA_EVT_DATA_READY[0m
%CESQ: 58,2,21,3
%CESQ: 59,2,34,4
%CESQ: 255,0,255,0
%CESQ: 40,2,8,1
+CEREG: 2,"7D1B","010BFD29",7
+CNEC_ESM: 29,0
+CNEC_EMM: 19
+CEREG: 2,"7D1B","010BFD29",7,0,19
+CEREG: 2,"7D1B","010BFD2A",7

I'm missing something ?

Kind regards
Andrea

[Hakon]

Hello,

the network is giving the error code ESM 29 (user authentication failed). This could be caused by a number of reasons so the best option is to contact Pelion support and ask why your device is being rejected. And if you still aren't able to identify the cause, you can capture a modem trace and upload it in this ticket.

[nardoz-dev]

Hello, thanks for the reply..

Okay I will contact them,
Meanwhile this is what I captured through the cellular monitor program.

analysis-pelion_v1.pcapng

Where can i find the documentation about the meanings of esm error ? 

Kind regards
Andrea

[Hakon]

nardoz-dev said:

Where can i find the documentation about the meanings of esm error ? 

I believe you can find it in the 3GPP specification.

[nardoz-dev]

Thanks, any news about the modem trace ?

[Hakon]

Not yet. Have you contacted Pelion support team? What did they say?

[nardoz-dev]

Yes I am waiting for an answer

[Hakon]

While you are still waiting for the answer you can try to provide a raw trace file, in the .bin or .mtrace format.

[nardoz-dev]

Yes of course, this the .mtrace !

trace-2024-05-08T13-19-08.002Z.mtrace

[Hakon]

Modem mentioned;

The only LTE-M network found was 222 10 and the network rejected Attach with ESM cause #29 “User authentication failed”. Later modem was reactivated and then at first Attach Accept was not received from network but the second Attach attempt resulted again with reject and cause #29.

From NB-IoT modem attempted Attach to network 222 10, which rejected Attach with EMM cause #17 “Network failure”. After that, there is a gap in traces, but it based on other traces I can see that modem is deactivated. Therefore, the other found NB-IoT networks are not attempted (222 88 & 222 01).

In summary, it seems like the SIM card subscription is not valid for network 222 10 or there are some kind of problem in the network. The other found networks (in NB-IoT) were not tried to Attach because the modem was deactivated just before the attempts. Customer can try to select the networks one by one with %COPS to see whether the subscription allows the Attach. The reject causes can be seen by subscribing +CNEC (both EMM and ESM error codes).