nRF9160 modem stuck in searching

RE: nRF9160 modem stuck in searching

Martin Lesund — Thu, 27 Aug 2020 13:48:06 GMT

Hi Mike,

note: mfw 1.2.1 is released: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF9160-DK/Download#infotabs

1. I do not know how many networks can be remember, but I have not heard any issues that this "has run out of space". (Please make sure that after a successful connect using the two different networks that you at least issue the AT+CFUN=0 command one time so that the history is stored in the NVM in the modem)

2. You can start the modem again by AT+CFUN=1 (correct, older mfw did not support this after a AT+CFUN=0)

Best regards,
martin L.

RE: nRF9160 modem stuck in searching

miked531 — Tue, 25 Aug 2020 20:57:28 GMT

Can you please expand on your response.

* The modem quickly connects with lte-m, then is not able to quickly reconnect. If it can do it quickly once, it would seem that the modem flash already has the network data stored. Does it get replaced? Is there a limited number of networks remembered? Also note that after a power reset, the modem returns to the quick connect.

* I thought AT+CFUN=0 turns the modem off after updating it's flash. I played with this some time ago (pre-mfw 1.0) and don't recall any command that could turn it back on. How do I turn it back on?

RE: nRF9160 modem stuck in searching

Martin Lesund — Thu, 20 Aug 2020 13:47:00 GMT

Hi Mike,
I think I've figured out why it took so long in your cases.

The modem is missing the historical network data in it's flash for some of your use cases, and therefore it will use more time to search and connect.

So what you need to do is to save this data to the modem by issuing the command AT+CFUN=0.

You issue this command after a successful connection, then the next time you try that network in that area it should get a much quicker connection.

RE: nRF9160 modem stuck in searching

miked531 — Fri, 31 Jul 2020 20:44:11 GMT

I'm finally back on this. I got the requested modem trace along with the log from the link monitor. The steps I did:

power on
connect lte-m (got quick connect as I had connected to lte-m prior to power off)
attempt nb-iot connection (didn't succeed after a few minutes)
connect lte-m (took a "long" time as I would expect based on your previous explanations)
connect lte-m (took a "long" time again, but would have expected quick connect)

Mike

devzone.nordicsemi.com/.../modem_2D00_trace.zip

RE: nRF9160 modem stuck in searching

Martin Lesund — Mon, 15 Jun 2020 13:33:13 GMT

Hi Mike,
The only way forward for me to investigate this would be to take a modemtrace while you go through the step by step:

1. Establish initial connect to cat-m1 (for me, it takes < 5 seconds from AT+CFUN=1)
2. Disconnect AT+CFUN=4
3. set systemmode to try nb-iot
4. AT+CFUN=1 fails to connect as expected
5. disconnect AT+CFUN=4 (This step was missing from your list)
6. set systemmode to cat-m1
7. Try to connect AT+CFUN=1

So I could analyze what is going on in the modem.
(As for now there is no command to clear the modem flash settings, I will forward your feature request)

RE: nRF9160 modem stuck in searching

miked531 — Wed, 03 Jun 2020 15:29:02 GMT

Understood about using params from flash upon reset. For my testing, I do take the effort to verify or set %xsystemmode before any at+cfun=1 and in the case of 'reset fixes it', the system mode is the same both before and after reset. In my tests, I have not used any other commands, aside from what the LTE link monitor inserts.

I'm running out of suggestions for how you could replicate what I am seeing.

In my application (and in testing), I don't want to rely on what's stored in the modem flash so I don't use at+cfun=0 and instead issue all of the AT commands required by the app. Is there a way to clear or reset the modem flash settings? Does updating the mfw do that? If there is no way to reset the modem flash, I'd like to suggest adding that as a feature.

Mike

RE: nRF9160 modem stuck in searching

Martin Lesund — Wed, 03 Jun 2020 14:47:00 GMT

Hi Mike,

Tested with both. In my area there are two carriers and one supports both technologies and one supports only LTE-M.
I tested with the local SIMs and was able to replicate the same "scenario" as you. (having LTE-M support but not nb-iot)

Note, the modem will first try to use the network information that is saved in the modem flash (at+cfun=0)
So it would make sense that when you power cycle the device it would do a quick connect since it utilizes data in the flash that has proven to work before.

(I updated my last post since there was some incorrect information)

RE: nRF9160 modem stuck in searching

miked531 — Mon, 01 Jun 2020 18:59:54 GMT

Based on the behavior I assumed something like the last connect params being stored across resets, but thanks for the clarification. I am using mfw 1.2.0.

In your testing, were you able to successfully connect to nbiot? I would like to know if there is a difference if the nbiot connects or not. I apparently don't have it in my area (Maryland, USA).

One other data point for you.. during my subsequent (after failing on nbiot) cat-m1 attempts, it will eventually connect after ~40 seconds, however after resetting the board it will connect within a few seconds.

RE: nRF9160 modem stuck in searching

Martin Lesund — Thu, 28 May 2020 11:27:12 GMT

Hi Mike,

I followed the steps you mentioned in the direct message:

1. Establish initial connect to cat-m1 (for me, it takes < 5 seconds from AT+CFUN=1)
2. Disconnect AT+CFUN=4
3. set systemmode to try nb-iot
4. AT+CFUN=1 fails to connect as expected
5. disconnect AT+CFUN=4 (This step was missing from your list)
6. set systemmode to cat-m1
7. Try to connect AT+CFUN=1

I tried this several times and sometimes it takes longer times

UPDATE

Remember when you issue the command AT+CFUN=4 the modem will not save the last network settings/info in the modem flash (AT+CFUN=0 however will do this).
So if you set the systemmode to nbiot and try to connect and issue the at+cfun=4 then power off/reset nrf9160 it will use the parameters saved in the flash when you turn on the modem to normal mode (AT+CFUN=1).

If you have a successful connection with the network on CAT-m1 and issue the command AT+CFUN=0 it will save those network parameters in the modem flash.

The configuration made with an AT command can 
be stored to NVM memory using AT+CFUN=0 if the
option is mentioned in the description of the command. 
This is useful if the command relates to a permanent 
hardware configuration, because it avoids the need to 
give the command every time in the beginning of the application.

and later on, you would issue the AT+CFUN=1 or resetting the device (and then issuing the AT+CFUN=1 command), the modem will use the last known parameters saved in its flash and search for the last known network/band etc. that worked --> which should connect you in seconds.

If it takes much longer times than e.g. 30 seconds that means that the modem does not find network right away through it's search algorithm and is checking each band available etc. one trick to decrease search time is to restrict bands to search on (use AT%XBANDLOCK) this will increase the speed of connection.

From your comment: "The connection in the last step takes > 60 seconds (~90 if I remember correctly). it does successfully connect. All future cat-m1 connections take the 90-ish seconds to connect."

I was not able to reproduce this. After a successful connection with cat-m1 and then issuing AT+CFUN=4 and then later on issuing the command AT+CFUN=1 it connected in seconds. Did this ON and OFF >10 times and it still connected in seconds.

Note: I used modem firmware version 1.2.0 when I tested this,

Please state which Modem Firmware version you are using.

Best regards,
Martin L.

RE: nRF9160 modem stuck in searching

miked531 — Sun, 01 Mar 2020 04:00:20 GMT

I am aware that I cannot connect to NB-IoT in my area. I'm OK with that. In fact, I am happy that I am not able to connect as I need to ensure my application functions in all cases. My concern is that things get wonky after the connection fails... AT+CEREG reports that it is still in searching mode (status 2). Additionally, all subsequent LTE-M connections take an inordinate amount of time (~80 seconds), and if I did NOT attempt NB-IoT connection, the LTE-M connection would succeed in <5 seconds.

The current solution in my application is to reset the device after a NB-IoT connection fails. I can deal with that but it's not a good solution.

I appreciate the support you have been providing, but after a month, I don't feel we are any closer to identifying what's happening. I don't know what is going on, but something doesn't seem right. I would appreciate a willingness from Nordic to accept that there something is maybe a little off. I'm even fine with guidance that tells me that I am doing something wrong, or that I should expect the results that I am seeing. Telling me repeatedly that NB-IoT is not connecting is not helping. I know that. Please help me so I can make a solid product.

RE: nRF9160 modem stuck in searching

Martin Lesund — Mon, 24 Feb 2020 14:48:39 GMT

Using the T-Mobile SIM when you try to connect on the LTE-M network, you are Roaming on the AT&T network.
Using the T-Mobile SIM when you try to connect to the NB-IoT network you are not finding the T-Mobile network.

Please check with T-Mobile if you have NB-IoT coverage in your area.

RE: nRF9160 modem stuck in searching

miked531 — Mon, 24 Feb 2020 04:35:25 GMT

Martin Lesund is there any update?

RE: nRF9160 modem stuck in searching

miked531 — Mon, 17 Feb 2020 18:32:36 GMT

devzone.nordicsemi.com/.../1104.traces.zip

includes logs+traces for successful catm1 connection and failed nbiot connection

RE: nRF9160 modem stuck in searching

Martin Lesund — Thu, 13 Feb 2020 14:41:39 GMT

Awaiting modem trace for further analysis.

RE: nRF9160 modem stuck in searching

miked531 — Tue, 11 Feb 2020 01:37:22 GMT

Tried and got the same results. Also tried AT%XEPCO=1 and no difference

RE: nRF9160 modem stuck in searching

Martin Lesund — Mon, 10 Feb 2020 14:52:48 GMT

Try to run the AT%XEPCO=0 before turning on the modem when selecting NB-IoT (AT%XSYSTEMMODE).

RE: nRF9160 modem stuck in searching

miked531 — Sat, 08 Feb 2020 01:40:56 GMT

I can't seem to find a way to attach the logs, so here they are inline. One diff between what you are getting is that I never get connected in NB-IoT mode.

First log is a successful LTE-M connection:

2020-02-08T01:24:56.852Z INFO Application data folder: /home/michael/.config/nrfconnect/pc-nrfconnect-linkmonitor
2020-02-08T01:24:56.913Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
2020-02-08T01:24:56.913Z DEBUG App path: /home/michael/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2020-02-08T01:24:56.913Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
2020-02-08T01:24:56.913Z DEBUG nRFConnect path: /tmp/.mount_nrfconwP3uvx/resources/app.asar
2020-02-08T01:24:56.913Z DEBUG HomeDir: /home/michael
2020-02-08T01:24:56.913Z DEBUG TmpDir: /tmp
2020-02-08T01:24:57.155Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2020-02-08T01:24:57.156Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2020-02-08T01:24:57.157Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2020-02-08T01:24:57.158Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2020-02-08T01:24:57.158Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2020-02-08T01:24:57.158Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2020-02-08T01:24:57.158Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2020-02-08T01:24:57.158Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2020-02-08T01:24:57.158Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2020-02-08T01:24:57.158Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2020-02-08T01:25:03.721Z INFO Modem port is opened
2020-02-08T01:25:03.733Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-08T01:25:03.766Z DEBUG modem << +CFUN: 0\x0D\x0A
2020-02-08T01:25:03.768Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:18.365Z DEBUG modem >> AT%XSYSTEMMODE?\x0D\x0A
2020-02-08T01:25:18.387Z DEBUG modem << %XSYSTEMMODE: 1,0,0,0\x0D\x0A
2020-02-08T01:25:18.397Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:21.200Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-08T01:25:21.227Z DEBUG modem << +CFUN: 0\x0D\x0A
2020-02-08T01:25:21.281Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:22.888Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2020-02-08T01:25:22.933Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.783Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-08T01:25:24.793Z DEBUG modem << +CFUN: 1\x0D\x0A
2020-02-08T01:25:24.820Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.833Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2020-02-08T01:25:24.845Z DEBUG modem << +CGSN: "352656100038754"\x0D\x0A
2020-02-08T01:25:24.854Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.867Z DEBUG modem >> AT+CGMI\x0D\x0A
2020-02-08T01:25:24.874Z DEBUG modem << Nordic Semiconductor ASA\x0D
2020-02-08T01:25:24.877Z DEBUG modem << \x0A
2020-02-08T01:25:24.880Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.888Z DEBUG modem >> AT+CGMM\x0D\x0A
2020-02-08T01:25:24.892Z DEBUG modem << nRF9160-SICA\x0D
2020-02-08T01:25:24.894Z DEBUG modem << \x0A
2020-02-08T01:25:24.896Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.903Z DEBUG modem >> AT+CGMR\x0D\x0A
2020-02-08T01:25:24.908Z DEBUG modem << mfw_nrf9160_1.1.0\x0D\x0A
2020-02-08T01:25:24.910Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.913Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.1.0] SerNr: 352656100038754
2020-02-08T01:25:24.917Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2020-02-08T01:25:24.924Z DEBUG modem << +CEMODE: 2\x0D\x0A
2020-02-08T01:25:24.925Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.937Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2020-02-08T01:25:24.948Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,14,17,18,19,20,25,26,28,66)\x0D\x0A
2020-02-08T01:25:24.950Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.959Z DEBUG modem >> AT+CMEE?\x0D\x0A
2020-02-08T01:25:24.969Z DEBUG modem << +CMEE: 0\x0D\x0A
2020-02-08T01:25:24.971Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.974Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2020-02-08T01:25:24.978Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.985Z DEBUG modem >> AT+CNEC?\x0D\x0A
2020-02-08T01:25:24.989Z DEBUG modem << +CNEC: 0\x0D
2020-02-08T01:25:24.990Z DEBUG modem << \x0A
2020-02-08T01:25:24.991Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:24.994Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2020-02-08T01:25:25.001Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.005Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2020-02-08T01:25:25.009Z DEBUG modem << +CGEREP: 0,0\x0D
2020-02-08T01:25:25.015Z DEBUG modem << \x0A
2020-02-08T01:25:25.019Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.022Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-02-08T01:25:25.025Z DEBUG modem << OK\x0D
2020-02-08T01:25:25.032Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-02-08T01:25:25.037Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.039Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2020-02-08T01:25:25.042Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.048Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2020-02-08T01:25:25.053Z DEBUG modem << OK\x0D
2020-02-08T01:25:25.055Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2020-02-08T01:25:25.058Z DEBUG modem << OK\x0D
2020-02-08T01:25:25.061Z DEBUG modem >> AT+CEREG?\x0D\x0A
2020-02-08T01:25:25.067Z DEBUG modem << +CEREG: 2,4,"FFFE","FFFFFFFF",7\x0D\x0A
2020-02-08T01:25:25.069Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.082Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2020-02-08T01:25:25.086Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.089Z DEBUG modem >> AT+CESQ\x0D\x0A
2020-02-08T01:25:25.094Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D
2020-02-08T01:25:25.101Z DEBUG modem << \x0A
2020-02-08T01:25:25.103Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.109Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2020-02-08T01:25:25.115Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:25.119Z DEBUG modem >> AT%XSIM?\x0D\x0A
2020-02-08T01:25:25.123Z DEBUG modem << %XSIM: 0\x0D
2020-02-08T01:25:25.124Z DEBUG modem << \x0A
2020-02-08T01:25:25.126Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:26.785Z DEBUG modem << %XSIM: 1\x0D\x0A
2020-02-08T01:25:26.812Z DEBUG modem >> AT+CPIN?\x0D\x0A
2020-02-08T01:25:26.822Z DEBUG modem << +CPIN: READY\x0D\x0A
2020-02-08T01:25:26.829Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:26.846Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2020-02-08T01:25:27.094Z DEBUG modem << +CPINR: "SIM PIN",3\x0D
2020-02-08T01:25:27.095Z DEBUG modem << \x0A
2020-02-08T01:25:27.096Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:27.105Z DEBUG modem >> AT+CIMI\x0D\x0A
2020-02-08T01:25:27.110Z DEBUG modem << 262017740075598\x0D
2020-02-08T01:25:27.111Z DEBUG modem << \x0A
2020-02-08T01:25:27.113Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:27.114Z INFO IMSIdentity: 262017740075598
2020-02-08T01:25:27.685Z DEBUG modem << %CESQ: 54,2,14,2\x0D\x0A
2020-02-08T01:25:27.706Z DEBUG modem << +CEREG: 2,"121F","01123911",7\x0D\x0A
2020-02-08T01:25:29.388Z DEBUG modem << +CGEV: ME PDN ACT 0,0\x0D\x0A
2020-02-08T01:25:29.422Z DEBUG modem << +CNEC_ESM: 50,0\x0D\x0A
2020-02-08T01:25:29.443Z DEBUG modem << +CEREG: 5,"121F","01123911",7\x0D\x0A
2020-02-08T01:25:29.460Z DEBUG modem << +CIND: "service",1\x0D\x0A
2020-02-08T01:25:29.468Z DEBUG modem << +CIND: "roam",1\x0D\x0A
2020-02-08T01:25:29.473Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-02-08T01:25:29.482Z DEBUG modem << +CGDCONT: 0,"IP","internet.m2mportal.de","10.129.140.125",0,0\x0D
2020-02-08T01:25:29.484Z DEBUG modem << \x0A
2020-02-08T01:25:29.485Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:29.493Z DEBUG modem >> AT+COPS=3,2\x0D\x0A
2020-02-08T01:25:29.496Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:29.504Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-02-08T01:25:29.509Z DEBUG modem << +CGACT: 0,1\x0D\x0A
2020-02-08T01:25:29.510Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:29.515Z DEBUG modem >> AT+COPS?\x0D\x0A
2020-02-08T01:25:29.520Z DEBUG modem << +COPS: 0,2,"310410",7\x0D\x0A
2020-02-08T01:25:29.523Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:29.529Z DEBUG modem >> AT%XCBAND\x0D\x0A
2020-02-08T01:25:29.537Z DEBUG modem << %XCBAND: 17\x0D\x0A
2020-02-08T01:25:29.539Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:29.545Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-02-08T01:25:29.554Z DEBUG modem << +CGDCONT: 0,"IP","internet.m2mportal.de","10.129.140.125",0,0\x0D\x0A
2020-02-08T01:25:29.555Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:29.562Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-02-08T01:25:29.570Z DEBUG modem << +CGACT: 0,1\x0D\x0A
2020-02-08T01:25:29.572Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:36.642Z DEBUG modem << %CESQ: 54,2,9,1\x0D\x0A
2020-02-08T01:25:41.629Z DEBUG modem << %CESQ: 54,2,14,2\x0D
2020-02-08T01:25:53.810Z DEBUG modem >> AT+CFUN=4\x0D\x0A
2020-02-08T01:25:54.041Z DEBUG modem << +CGEV: ME PDN DEACT 0\x0D\x0A
2020-02-08T01:25:54.072Z DEBUG modem << +CEREG: 0,"121F","01123911",7\x0D\x0A
2020-02-08T01:25:54.097Z DEBUG modem << +CIND: "service",0\x0D\x0A
2020-02-08T01:25:54.111Z DEBUG modem << +CIND: "roam",0\x0D\x0A
2020-02-08T01:25:54.130Z DEBUG modem << +CGEV: ME DETACH\x0D\x0A
2020-02-08T01:25:55.499Z DEBUG modem << %CESQ: 255,0,255,0\x0D\x0A
2020-02-08T01:25:56.564Z DEBUG modem << %XSIM: 0\x0D
2020-02-08T01:25:56.593Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:56.598Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-02-08T01:25:56.613Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:56.616Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-02-08T01:25:56.629Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:56.631Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-02-08T01:25:56.644Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:25:56.648Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-02-08T01:25:56.661Z DEBUG modem << OK\x0D\x0A

And this is the failed NB-IoT:

2020-02-08T01:27:01.247Z INFO Application data folder: /home/michael/.config/nrfconnect/pc-nrfconnect-linkmonitor
2020-02-08T01:27:01.334Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
2020-02-08T01:27:01.334Z DEBUG App path: /home/michael/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2020-02-08T01:27:01.334Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
2020-02-08T01:27:01.334Z DEBUG nRFConnect path: /tmp/.mount_nrfconwP3uvx/resources/app.asar
2020-02-08T01:27:01.335Z DEBUG HomeDir: /home/michael
2020-02-08T01:27:01.335Z DEBUG TmpDir: /tmp
2020-02-08T01:27:01.627Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2020-02-08T01:27:01.627Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2020-02-08T01:27:01.627Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2020-02-08T01:27:01.628Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2020-02-08T01:27:01.629Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2020-02-08T01:27:01.629Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2020-02-08T01:27:01.629Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2020-02-08T01:27:01.629Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2020-02-08T01:27:03.168Z INFO Modem port is opened
2020-02-08T01:27:03.176Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-08T01:27:03.179Z DEBUG modem << **** Booting Zephyr OS build v2.0.99-ncs1 *****\x0D\x0A
2020-02-08T01:27:03.180Z DEBUG modem << Flash region\x09\x09Domain\x09\x09Permissions\x0D\x0A
2020-02-08T01:27:03.182Z DEBUG modem << 00 0x00000 0x08000 \x09Secure\x09\x09rwxl\x0D\x0A
2020-02-08T01:27:03.211Z DEBUG modem << 01 0x0800+CFUN: 0\x0D\x0A
2020-02-08T01:27:03.214Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:12.268Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-08T01:27:12.287Z DEBUG modem << +CFUN: 0\x0D\x0A
2020-02-08T01:27:12.332Z DEBUG modem << OK\x0D
2020-02-08T01:27:23.497Z DEBUG modem >> AT%XSYSTEMMODE=0,1,0,0\x0D\x0A
2020-02-08T01:27:23.515Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:29.667Z DEBUG modem >> AT%XSYSTEMMODE?\x0D\x0A
2020-02-08T01:27:29.699Z DEBUG modem << %XSYSTEMMODE: 0,1,0,0\x0D\x0A
2020-02-08T01:27:29.706Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:32.332Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2020-02-08T01:27:32.379Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:33.851Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-08T01:27:33.871Z DEBUG modem << +CFUN: 1\x0D\x0A
2020-02-08T01:27:33.908Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:33.927Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2020-02-08T01:27:33.939Z DEBUG modem << +CGSN: "352656100038754"\x0D
2020-02-08T01:27:33.953Z DEBUG modem << \x0A
2020-02-08T01:27:33.955Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:33.960Z DEBUG modem >> AT+CGMI\x0D\x0A
2020-02-08T01:27:33.969Z DEBUG modem << Nordic Semiconductor ASA\x0D\x0A
2020-02-08T01:27:33.972Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:33.976Z DEBUG modem >> AT+CGMM\x0D\x0A
2020-02-08T01:27:33.986Z DEBUG modem << nRF9160-SICA\x0D\x0A
2020-02-08T01:27:33.990Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:33.992Z DEBUG modem >> AT+CGMR\x0D\x0A
2020-02-08T01:27:34.000Z DEBUG modem << mfw_nrf9160_1.1.0\x0D\x0A
2020-02-08T01:27:34.003Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.005Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.1.0] SerNr: 352656100038754
2020-02-08T01:27:34.006Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2020-02-08T01:27:34.015Z DEBUG modem << +CEMODE: 0\x0D\x0A
2020-02-08T01:27:34.018Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.025Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2020-02-08T01:27:34.033Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)\x0D
2020-02-08T01:27:34.036Z DEBUG modem << \x0A
2020-02-08T01:27:34.037Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.051Z DEBUG modem >> AT+CMEE?\x0D\x0A
2020-02-08T01:27:34.056Z DEBUG modem << +CMEE: 0\x0D
2020-02-08T01:27:34.058Z DEBUG modem << \x0A
2020-02-08T01:27:34.059Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.066Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2020-02-08T01:27:34.071Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.074Z DEBUG modem >> AT+CNEC?\x0D\x0A
2020-02-08T01:27:34.083Z DEBUG modem << +CNEC: 0\x0D\x0A
2020-02-08T01:27:34.085Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.088Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2020-02-08T01:27:34.091Z DEBUG modem << OK\x0D
2020-02-08T01:27:34.100Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2020-02-08T01:27:34.109Z DEBUG modem << +CGEREP: 0,0\x0D\x0A
2020-02-08T01:27:34.110Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.120Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-02-08T01:27:34.124Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.127Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-02-08T01:27:34.134Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.137Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2020-02-08T01:27:34.142Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.149Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2020-02-08T01:27:34.154Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.156Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2020-02-08T01:27:34.160Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.170Z DEBUG modem >> AT+CEREG?\x0D\x0A
2020-02-08T01:27:34.177Z DEBUG modem << +CEREG: 2,4,"FFFE","FFFFFFFF",9\x0D
2020-02-08T01:27:34.180Z DEBUG modem << \x0A
2020-02-08T01:27:34.183Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.210Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2020-02-08T01:27:34.216Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.220Z DEBUG modem >> AT+CESQ\x0D\x0A
2020-02-08T01:27:34.227Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D
2020-02-08T01:27:34.239Z DEBUG modem << \x0A
2020-02-08T01:27:34.241Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.258Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2020-02-08T01:27:34.263Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:34.275Z DEBUG modem >> AT%XSIM?\x0D\x0A
2020-02-08T01:27:34.281Z DEBUG modem << %XSIM: 0\x0D\x0A
2020-02-08T01:27:34.292Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:36.332Z DEBUG modem << %XSIM: 1\x0D\x0A
2020-02-08T01:27:36.368Z DEBUG modem >> AT+CPIN?\x0D\x0A
2020-02-08T01:27:36.374Z DEBUG modem << +CPIN: READY\x0D
2020-02-08T01:27:36.377Z DEBUG modem << \x0A
2020-02-08T01:27:36.380Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:36.392Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2020-02-08T01:27:36.642Z DEBUG modem << +CPINR: "SIM PIN",3\x0D\x0A
2020-02-08T01:27:36.661Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:36.696Z DEBUG modem >> AT+CIMI\x0D\x0A
2020-02-08T01:27:36.707Z DEBUG modem << 262017740075598\x0D\x0A
2020-02-08T01:27:36.711Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:27:36.720Z INFO IMSIdentity: 262017740075598
2020-02-08T01:27:58.583Z DEBUG modem << %CESQ: 62,3,22,3\x0D\x0A
2020-02-08T01:27:58.620Z DEBUG modem << +CEREG: 2,"131B","0112393B",9\x0D\x0A
2020-02-08T01:27:59.370Z DEBUG modem << +CNEC_EMM: 15\x0D\x0A
2020-02-08T01:27:59.395Z DEBUG modem << +CEREG: 4,"131B","0112393B",9\x0D\x0A
2020-02-08T01:27:59.762Z DEBUG modem << %CESQ: 255,0,255,0\x0D
2020-02-08T01:27:59.771Z DEBUG modem << +CEREG: 4,"FFFE","FFFFFFFF",9\x0D\x0A
2020-02-08T01:28:09.452Z DEBUG modem << %CESQ: 56,2,18,2\x0D\x0A
2020-02-08T01:28:09.481Z DEBUG modem << +CEREG: 2,"6D82","01AAD61E",9\x0D\x0A
2020-02-08T01:28:12.368Z DEBUG modem << +CNEC_ESM: 32,0\x0D\x0A
2020-02-08T01:28:12.389Z DEBUG modem << +CNEC_EMM: 19\x0D\x0A
2020-02-08T01:28:13.216Z DEBUG modem << %CESQ: 255,0,255,0\x0D
2020-02-08T01:28:13.241Z DEBUG modem << +CEREG: 2,"FFFE","FFFFFFFF",9\x0D\x0A
2020-02-08T01:28:38.262Z DEBUG modem << %CESQ: 58,2,18,2\x0D\x0A
2020-02-08T01:28:38.287Z DEBUG modem << +CEREG: 2,"6D82","01AAD61E",9\x0D\x0A
2020-02-08T01:29:43.746Z DEBUG modem << %CESQ: 53,2,18,2\x0D\x0A
2020-02-08T01:31:56.870Z DEBUG modem << %CESQ: 58,2,18,2\x0D\x0A
2020-02-08T01:32:22.286Z DEBUG modem << %CESQ: 49,2,18,2\x0D\x0A
2020-02-08T01:32:22.336Z DEBUG modem << %CESQ: 49,2,23,3\x0D\x0A
2020-02-08T01:32:22.358Z DEBUG modem << +CEREG: 2,"EE0B","00C526D4",9\x0D\x0A
2020-02-08T01:32:23.155Z DEBUG modem << +CNEC_EMM: 11\x0D\x0A
2020-02-08T01:32:23.207Z DEBUG modem << %CESQ: 255,0,255,0\x0D\x0A
2020-02-08T01:32:23.244Z DEBUG modem << +CEREG: 2,"FFFE","FFFFFFFF",9\x0D\x0A
2020-02-08T01:32:27.392Z DEBUG modem << %CESQ: 62,3,21,3\x0D\x0A
2020-02-08T01:32:27.420Z DEBUG modem << +CEREG: 4,"131B","0112393B",9\x0D\x0A
2020-02-08T01:32:34.091Z DEBUG modem << %CESQ: 62,3,26,3\x0D\x0A
2020-02-08T01:32:36.127Z DEBUG modem >> AT+CFUN=4\x0D\x0A
2020-02-08T01:32:36.151Z DEBUG modem << %CESQ: 255,0,255,0\x0D\x0A
2020-02-08T01:32:36.385Z DEBUG modem << %XSIM: 0\x0D\x0A
2020-02-08T01:32:36.415Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:32:52.223Z DEBUG modem >> AT+CEREG?\x0D\x0A
2020-02-08T01:32:52.247Z DEBUG modem << +CEREG: 2,4,"131B","0112393B",9\x0D\x0A
2020-02-08T01:32:52.271Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:32:57.996Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-02-08T01:32:58.021Z DEBUG modem << +CFUN: 4\x0D\x0A
2020-02-08T01:32:58.047Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:32:58.070Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2020-02-08T01:32:58.114Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:33:01.967Z DEBUG modem << %XSIM: 1\x0D\x0A
2020-02-08T01:33:02.001Z DEBUG modem >> AT+CPIN?\x0D\x0A
2020-02-08T01:33:02.012Z DEBUG modem << +CPIN: READY\x0D\x0A
2020-02-08T01:33:02.015Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:33:02.059Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2020-02-08T01:33:02.273Z DEBUG modem << +CPINR: "SIM PIN",3\x0D
2020-02-08T01:33:02.277Z DEBUG modem << \x0A
2020-02-08T01:33:02.280Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:33:02.316Z DEBUG modem >> AT+CIMI\x0D\x0A
2020-02-08T01:33:02.326Z DEBUG modem << 262017740075598\x0D
2020-02-08T01:33:02.333Z DEBUG modem << \x0A
2020-02-08T01:33:02.337Z DEBUG modem << OK\x0D\x0A
2020-02-08T01:33:02.340Z INFO IMSIdentity: 262017740075598

RE: nRF9160 modem stuck in searching

Martin Lesund — Thu, 06 Feb 2020 14:36:26 GMT

Hi Mike,
Please share the log from LTE link monitor when you are getting this CEREG response after AT+CFUN=4.

e.g. This is what happens on my side:

RE: nRF9160 modem stuck in searching

miked531 — Thu, 06 Feb 2020 14:17:48 GMT

Martin,

I feel like we are going down the wrong path by contacting the carrier. Going back to my original issue, I see that AT+CFUN=4 does not seem to completely turn off the modem as expected. AT+CEREG continues to report status 2 (searching for network) after +CFUN=4, and does not change. Additionally, the modem behaves differently after a failed attempt to connect to NB-IoT, where future Cat-M1 connects take 80 seconds vice 5 seconds if I didn't attempt NB-IoT.

I hope to get the modem trace for you by this weekend.

RE: nRF9160 modem stuck in searching

Martin Lesund — Wed, 05 Feb 2020 13:42:26 GMT

Please contact DT on how to get connected to their NB-IoT network, and if you have the correct DT SIM for that.
When using DT SIM on LTE-M network, do you then roam on the verizon/AT&T network?

RE: nRF9160 modem stuck in searching

miked531 — Tue, 04 Feb 2020 13:29:41 GMT

I am using the DT and iBasis SIMs on an AT&T network (and occaisionally Verizon, depending where I am [again, same beharior]), which we hare already established does not support NB-IoT. Does that change your thinking at all?

RE: nRF9160 modem stuck in searching

Martin Lesund — Tue, 04 Feb 2020 10:16:57 GMT

Hi Mike,
It would make sense that the iBasis SIM card would have the same behavior if the DT network has not allowed roaming SIMs onto their NB-IoT network.
So I recommend that you get in contact with DT and get an update on which type of SIM card that would allow you on their NB-IoT network.

RE: nRF9160 modem stuck in searching

miked531 — Tue, 04 Feb 2020 04:59:00 GMT

I will get a modem trace and see what I can find about the SIM, but it may be a few days until I can get that done. Another point to consider is that the same behavior is observed with the iBasis SIM that comes with the DK.

I didn't realize turning on the modem also turned on the SIM, but that makes sense.

Mike

RE: nRF9160 modem stuck in searching

Martin Lesund — Mon, 03 Feb 2020 12:22:34 GMT

Hi Mike,
Thanks for confirming that everything works fine on the LTE-M network.

The information from the SIM card cannot be extracted unless the modem has been turned ON, because the SIM card is initialized when the Modem turns ON.

From your log when testing Nb-IoT network using DT SIM:

+CGEV: RESTR 2,2

You get a response from the modem "Requested Procedure restricted" with the "Restriction cause" being "Throttling. Procedure restricted by 3GPP or operator-specific throttling" and the "Validity of the restriction" being "Temporary restriction. Enabling requires e.g. back-off timer expiry" according to the documentation.

I would recommend you to contact DT with regards to the specification of your SIM card, if it actually gives you access to their NB-IoT network or if it only supports the LTE-M access.

For us to dig deeper into my suspicion that this is an issue with the SIM card not giving access to the network you could do a modem trace that we could analyze.

Best regards,
Martin L.

RE: nRF9160 modem stuck in searching

miked531 — Sat, 01 Feb 2020 02:24:23 GMT

I programmed the at_client example and ran the LTE link monitor and here's the results...

The AT+CIMI command returns ERROR until I have turned the modem on for the first time with AT+CFUN=1. This happens with both the DT SIM and iBasis SIM I have. Neither SIM has a PIN code set (AT+CPIN? responds with READY). I can understand the error, but didn't expect it.

After a fresh reboot, the AT+CPIN? command times out at which time the LTE link monitor no longer processes any AT commands (they all report timed out, also). AT+CPIN? works only after AT+CFUN=1. This remains until I reset the device (nrf9160 DK).

I should also point out that everything works just fine with xsystemmode=1,0,0,0