nrf9160 modem get stuck in LTE seaching

[ced27]

Hello,

for some days now, my modem is unable to connect to the network, it gets stuck in searching and i don't know why?. I am using an eSIM card from iBasis and i am trying to connect over LTE-M or NB-Iot to the californium server, but it just gets stuck.

Note: The modem hasn't been doing this in the past, it just started getting stuck some days ago until now

Can someone please help me .

Fullscreen 2021-11-04T10_28_46.368Z-log.txt Download

2021-11-04T10:28:46.891Z INFO Application data folder: C:\Users\tcheced\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-11-04T10:28:46.971Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2021-11-04T10:28:46.971Z DEBUG App path: C:\Users\tcheced\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-11-04T10:28:46.971Z DEBUG nRFConnect 3.8.0 is not supported by the app (^3.8.0)
2021-11-04T10:28:46.971Z DEBUG nRFConnect path: C:\Users\tcheced\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-11-04T10:28:46.971Z DEBUG HomeDir: C:\Users\tcheced
2021-11-04T10:28:46.971Z DEBUG TmpDir: C:\Users\tcheced\AppData\Local\Temp
2021-11-04T10:28:50.873Z INFO Modem port is opened
2021-11-04T10:28:55.793Z DEBUG modem << *** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
2021-11-04T10:28:55.807Z DEBUG modem << Flash regionsDomainPermissions
2021-11-04T10:28:55.811Z DEBUG modem << 00 01 0x00000 0x10000 Securerwxl
2021-11-04T10:28:55.814Z DEBUG modem << 02 31 0x10000 0x100000 Non-Securerwxl
2021-11-04T10:28:55.815Z DEBUG modem << Non-secure callable region 0 placed in flash region 1 with size 32.
2021-11-04T10:28:55.859Z DEBUG modem << SRAM regionDomainPermissions
2021-11-04T10:28:55.862Z DEBUG modem << 00 07 0x00000 0x10000 Securerwxl
2021-11-04T10:28:55.866Z DEBUG modem << 08 31 0x10000 0x40000 Non-Securerwxl
2021-11-04T10:28:55.868Z DEBUG modem << PeripheralDomainStatus
2021-11-04T10:28:55.872Z DEBUG modem << 00 NRF_P0               Non-SecureOK
2021-11-04T10:28:55.879Z DEBUG modem << 01 NRF_CLOCK            Non-SecureOK
2021-11-04T10:28:55.881Z DEBUG modem << 02 NRF_RTC0             Non-SecureOK
2021-11-04T10:28:55.888Z DEBUG modem << 03 NRF_RTC1             Non-SecureOK
2021-11-04T10:28:55.890Z DEBUG modem << 04 NRF_NVMC             Non-SecureOK
2021-11-04T10:28:55.897Z DEBUG modem << 05 NRF_UARTE1           Non-SecureOK
2021-11-04T10:28:55.900Z DEBUG modem << 06 NRF_UARTE2           SecureSKIP
2021-11-04T10:28:55.905Z DEBUG modem << 07 NRF_TWIM2            Non-SecureOK
2021-11-04T10:28:55.908Z DEBUG modem << 08 NRF_SPIM3            Non-SecureOK
2021-11-04T10:28:55.913Z DEBUG modem << 09 NRF_TIMER0           Non-SecureOK
2021-11-04T10:28:55.918Z DEBUG modem << 10 NRF_TIMER1           Non-SecureOK
2021-11-04T10:28:55.920Z DEBUG modem << 11 NRF_TIMER2           Non-SecureOK
2021-11-04T10:28:55.922Z DEBUG modem << 12 NRF_SAADC            Non-SecureOK
2021-11-04T10:28:55.930Z DEBUG modem << 13 NRF_PWM0             Non-SecureOK
2021-11-04T10:28:55.931Z DEBUG modem << 14 NRF_PWM1             Non-SecureOK
2021-11-04T10:28:55.933Z DEBUG modem << 15 NRF_PWM2             Non-SecureOK
2021-11-04T10:28:55.934Z DEBUG modem << 16 NRF_PWM3             Non-SecureOK
2021-11-04T10:28:55.939Z DEBUG modem << 17 NRF_WDT              Non-SecureOK
2021-11-04T10:28:55.943Z DEBUG modem << 18 NRF_IPC              Non-SecureOK
2021-11-04T10:28:55.948Z DEBUG modem << 19 NRF_VMC              Non-SecureOK
2021-11-04T10:28:55.950Z DEBUG modem << 20 NRF_FPU              Non-SecureOK
2021-11-04T10:28:55.958Z DEBUG modem << 21 NRF_EGU1             Non-SecureOK
2021-11-04T10:28:55.968Z DEBUG modem << 22 NRF_EGU2             Non-SecureOK
2021-11-04T10:28:55.970Z DEBUG modem << 23 NRF_DPPIC            Non-SecureOK
2021-11-04T10:28:55.971Z DEBUG modem << 24 NRF_REGULATORS       Non-SecureOK
2021-11-04T10:28:55.980Z DEBUG modem << 25 NRF_PDM              Non-SecureOK
2021-11-04T10:28:55.981Z DEBUG modem << 26 NRF_I2S              Non-SecureOK
2021-11-04T10:28:55.986Z DEBUG modem << 27 NRF_GPIOTE1          Non-SecureOK
2021-11-04T10:28:55.987Z DEBUG modem << SPM: NS image at 0x10000
2021-11-04T10:28:55.988Z DEBUG modem << SPM: NS MSP at 0x2001e3a0
2021-11-04T10:28:55.989Z DEBUG modem << SPM: NS reset vector at 0x147f1
2021-11-04T10:28:55.991Z DEBUG modem << SPM: prepare to jump to Non-Secure image.
2021-11-04T10:28:56.215Z DEBUG modem << *** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
2021-11-04T10:28:56.227Z DEBUG modem <<  CoAP/UDP sample started..
2021-11-04T10:28:56.230Z DEBUG modem << Verbindung zum LTE-Netz wird hergestellt
2021-11-04T10:28:56.234Z DEBUG modem << Das kann ein paar Minuten dauern..
2021-11-04T10:28:56.355Z DEBUG modem << Mit LTE-Netz verbunden
2021-11-04T10:28:57.540Z DEBUG modem << +CEREG: 2,"63AE","01A3F802",7
2021-11-04T10:28:57.555Z DEBUG modem << LTE veränderte Zelle: Zelle ID: 27523074, Tracking area: 25518
2021-11-04T10:28:57.557Z DEBUG modem << Active LTE Modus: LTE-M

BR,

Cedric

[Håkon Alseth]

Hi,

 

Could you try to connect with at_client firmware, in combination with LTE Link Monitor (from nRF Connect for Desktop) and issue these commands?

AT+CEREG=5
AT+CFUN=1
AT+CFUN?

 

Let it run for 10 minutes and post the log here.

 

Kind regards,

Håkon

[ced27]

Hi Hakon,

Thanks for your reply.

Here is what i got:

Fullscreen 2021-11-04T12_08_09.044Z-log.txt Download

2021-11-04T12:08:09.686Z INFO Application data folder: C:\Users\tcheced\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-11-04T12:08:09.780Z DEBUG App pc-nrfconnect-linkmonitor v2.0.0 official
2021-11-04T12:08:09.780Z DEBUG App path: C:\Users\tcheced\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-11-04T12:08:09.780Z DEBUG nRFConnect 3.8.0 is not supported by the app (^3.8.0)
2021-11-04T12:08:09.780Z DEBUG nRFConnect path: C:\Users\tcheced\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-11-04T12:08:09.780Z DEBUG HomeDir: C:\Users\tcheced
2021-11-04T12:08:09.780Z DEBUG TmpDir: C:\Users\tcheced\AppData\Local\Temp
2021-11-04T12:08:12.255Z INFO Modem port is opened
2021-11-04T12:08:17.250Z DEBUG modem << *** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
2021-11-04T12:08:17.274Z DEBUG modem << Flash regionsDomainPermissions
2021-11-04T12:08:17.283Z DEBUG modem << 00 01 0x00000 0x10000 Securerwxl
2021-11-04T12:08:17.290Z DEBUG modem << 02 31 0x10000 0x100000 Non-Securerwxl
2021-11-04T12:08:17.296Z DEBUG modem << Non-secure callable region 0 placed in flash region 1 with size 32.
2021-11-04T12:08:17.316Z DEBUG modem << SRAM regionDomainPermissions
2021-11-04T12:08:17.322Z DEBUG modem << 00 07 0x00000 0x10000 Securerwxl
2021-11-04T12:08:17.334Z DEBUG modem << 08 31 0x10000 0x40000 Non-Securerwxl
2021-11-04T12:08:17.337Z DEBUG modem << PeripheralDomainStatus
2021-11-04T12:08:17.341Z DEBUG modem << 00 NRF_P0               Non-SecureOK
2021-11-04T12:08:17.352Z DEBUG modem << 01 NRF_CLOCK            Non-SecureOK
2021-11-04T12:08:17.355Z DEBUG modem << 02 NRF_RTC0             Non-SecureOK
2021-11-04T12:08:17.357Z DEBUG modem << 03 NRF_RTC1             Non-SecureOK
2021-11-04T12:08:17.361Z DEBUG modem << 04 NRF_NVMC             Non-SecureOK
2021-11-04T12:08:17.373Z DEBUG modem << 05 NRF_UARTE1           Non-SecureOK
2021-11-04T12:08:17.384Z DEBUG modem << 06 NRF_UARTE2           SecureSKIP
2021-11-04T12:08:17.387Z DEBUG modem << 07 NRF_TWIM2            Non-SecureOK
2021-11-04T12:08:17.391Z DEBUG modem << 08 NRF_SPIM3            Non-SecureOK
2021-11-04T12:08:17.395Z DEBUG modem << 09 NRF_TIMER0           Non-SecureOK
2021-11-04T12:08:17.399Z DEBUG modem << 10 NRF_TIMER1           Non-SecureOK
2021-11-04T12:08:17.401Z DEBUG modem << 11 NRF_TIMER2           Non-SecureOK
2021-11-04T12:08:17.402Z DEBUG modem << 12 NRF_SAADC            Non-SecureOK
2021-11-04T12:08:17.403Z DEBUG modem << 13 NRF_PWM0             Non-SecureOK
2021-11-04T12:08:17.405Z DEBUG modem << 14 NRF_PWM1             Non-SecureOK
2021-11-04T12:08:17.414Z DEBUG modem << 15 NRF_PWM2             Non-SecureOK
2021-11-04T12:08:17.417Z DEBUG modem << 16 NRF_PWM3             Non-SecureOK
2021-11-04T12:08:17.418Z DEBUG modem << 17 NRF_WDT              Non-SecureOK
2021-11-04T12:08:17.422Z DEBUG modem << 18 NRF_IPC              Non-SecureOK
2021-11-04T12:08:17.423Z DEBUG modem << 19 NRF_VMC              Non-SecureOK
2021-11-04T12:08:17.425Z DEBUG modem << 20 NRF_FPU              Non-SecureOK
2021-11-04T12:08:17.426Z DEBUG modem << 21 NRF_EGU1             Non-SecureOK
2021-11-04T12:08:17.432Z DEBUG modem << 22 NRF_EGU2             Non-SecureOK
2021-11-04T12:08:17.433Z DEBUG modem << 23 NRF_DPPIC            Non-SecureOK
2021-11-04T12:08:17.439Z DEBUG modem << 24 NRF_REGULATORS       Non-SecureOK
2021-11-04T12:08:17.442Z DEBUG modem << 25 NRF_PDM              Non-SecureOK
2021-11-04T12:08:17.447Z DEBUG modem << 26 NRF_I2S              Non-SecureOK
2021-11-04T12:08:17.449Z DEBUG modem << 27 NRF_GPIOTE1          Non-SecureOK
2021-11-04T12:08:17.450Z DEBUG modem << SPM: NS image at 0x10000
2021-11-04T12:08:17.451Z DEBUG modem << SPM: NS MSP at 0x2001c788
2021-11-04T12:08:17.452Z DEBUG modem << SPM: NS reset vector at 0x12ead
2021-11-04T12:08:17.454Z DEBUG modem << SPM: prepare to jump to Non-Secure image.
2021-11-04T12:08:17.637Z DEBUG modem << *** Booting Zephyr OS build v2.6.0-rc1-ncs1  ***
2021-11-04T12:08:17.642Z DEBUG modem << The AT host sample started
2021-11-04T12:08:37.953Z DEBUG modem >> AT+CEREG=5
2021-11-04T12:08:37.964Z DEBUG modem << OK
2021-11-04T12:08:58.768Z DEBUG modem >> AT+CFUN=1
2021-11-04T12:08:58.809Z DEBUG modem << OK
2021-11-04T12:09:00.059Z DEBUG modem << +CEREG: 2,"63AE","01A3F802",7
2021-11-04T12:09:09.246Z DEBUG modem >> AT+CFUN?
2021-11-04T12:09:09.258Z DEBUG modem << +CFUN: 1
2021-11-04T12:09:09.266Z DEBUG modem << OK
2021-11-04T12:27:10.011Z DEBUG modem << +CEREG: 5,"63AE","01A3F802",7,,,"11100000","11100000"

Best regards,

Cedric

[Håkon Alseth]

Hi Cedric,

 

Could it be that your SIM is out of data?

The behavior is then different from network-to-network, in some networks all looks good, but you get no connectivity at all, like in your case.

 

Could you also query "at+cops?" so I can see which network you're currently connected to?

iBasis' roaming agreement only covers telefonica in germany, so it could be useful to check out other vendors (Arkessa for instance).

 

Kind regards,

Håkon

[ced27]

Håkon Alseth said:

Could it be that your SIM is out of data?

I got a response from iBasis and that is what they said, i quote: "The eSIM in the kit is meant as a test sim card, so you will not be able to connect it over the internet"

what does that mean for me?

Håkon Alseth said:

Could you also query "at+cops?" so I can see which network you're currently connected to?

Here is what i got:

AT+COPS=?
+COPS: (1,"","","26202",7),(1,"","","26201",7)
OK
AT+COPS?
+COPS: 0
OK

Screenshot:

[Håkon Alseth]

Hi,

 

ced27 said:

I got a response from iBasis and that is what they said, i quote: "The eSIM in the kit is meant as a test sim card, so you will not be able to connect it over the internet"

what does that mean for me?

I am not sure what iBasis means here, you should ask them for a clarification.

Do you have a solder-able eSIM, or a "normal" nano SIM card like this (ie. the same that comes with the nRF9160 DK)?

 

ced27 said:

Here is what i got:

This shows that you have two networks available in your area, but which one were you successfully connected to in the previous log (where it took 20 minutes)?

 

Kind regards,

Håkon

[ced27]

Håkon Alseth said:

Do you have a solder-able eSIM, or a "normal" nano SIM card like this (ie. the same that comes with the nRF9160 DK)?

I am using the normal nano SIM card, that came with the nRF9160 DK

My SIM card hat the EID: 8949320005262167085

Håkon Alseth said:

This shows that you have two networks available in your area, but which one were you successfully connected to in the previous log (where it took 20 minutes)?

 

It was Telekom Deutschland GmbH

[Håkon Alseth]

Hi,

 

I had a chat with our local sales director in your area. If you have a iBasis, it should roam towards Telefonica, which should be reported back with mcc/mnc 262 03. The reception can be spotty in some areas, so you should consider getting a Arkessa sim in addition, which roams towards other network providers as well.

 

If you log into nrfcloud, you should be able to see the status of your SIM card in the cloud view, under "sim cards" - could you check if this still shows that you have data left?

 

Kind regards,

Håkon

[ced27]

Håkon Alseth said:

I had a chat with our local sales director in your area. If you have a iBasis, it should roam towards Telefonica, which should be reported back with mcc/mnc 262 03. The reception can be spotty in some areas, so you should consider getting a Arkessa sim in addition, which roams towards other network providers as well.

Thanks for your suggestions.

Håkon Alseth said:

If you log into nrfcloud, you should be able to see the status of your SIM card in the cloud view, under "sim cards" - could you check if this still shows that you have data left?

i still have like 0.22Mb left. Here is a screenshot:

Do you think is because of that? if yes, what can i do, buy Data i suppose?

[Håkon Alseth]

Hi,

 

It seems that you're out of data, yes. You can buy more if you click the "buy data" button.

 

Kind regards,

Håkon

[ced27]

Håkon Alseth said:

It seems that you're out of data, yes. You can buy more if you click the "buy data" button.

Hi Håkon Alseth,

i have found that my modem get stuck in searching not because i am out of data. Despite the fact that I bought some data,  i still got the same issue. What do you think will be the appropriate solution?

As soon as i get a connection to the server and that a DTLS handshake has been done and my payload was sent, the connection to the server will then be stopped and the cycle continuous. How can i make sure, that the connection to server stays?

Best regards,

Cedric

[Håkon Alseth]

Hi,

 

ced27 said:

i have found that my modem get stuck in searching not because i am out of data. Despite the fact that I bought some data,  i still got the same issue. What do you think will be the appropriate solution?

As soon as i get a connection to the server and that a DTLS handshake has been done and my payload was sent, the connection to the server will then be stopped and the cycle continuous. How can i make sure, that the connection to server stays?

Is this due to the network connectivity, or the connection to the server?

Is the communication still unstable with other samples, like mqtt_simple?

 

Kind regards,

Håkon

[ced27]

Hi Hakon,

Thanks for your reply.

Håkon Alseth said:

Is this due to the network connectivity, or the connection to the server?

I think it is due to the network NAT timeout. Can that be the case? what do you think?

Håkon Alseth said:

Is the communication still unstable with other samples, like mqtt_simple?

Yes, the same think with udp_sample and coap_sample.

Best regards,

Cedric