LTE Link Monitor Issue with 9160

RE: LTE Link Monitor Issue with 9160

Benjamin — Thu, 04 Aug 2022 20:39:23 GMT

Thank you! That helped me figure things out.

RE: LTE Link Monitor Issue with 9160

Charlie — Thu, 04 Aug 2022 10:18:20 GMT

Hi Benjamin,

The AT client sample does not use functions from the nRF91 LTE Link control library. As I mentioned, you need to manually send commands. Even the LTE Link Monitor Automatic requests options do is just help you send check commands. We have many nRF9160 samples to demo how to use LTE link controller, the simplest one is the UDP sample if you want to learn how to use it, please pay attend to the connect_to_lte and lte_handler functions.

Best regards,

Charlie

RE: LTE Link Monitor Issue with 9160

Benjamin — Wed, 03 Aug 2022 16:09:45 GMT

Ok, when I use those commands, it works! However, when I rebuild and reflash, it doesn't work again. I went through my kconfig for the nrf91 modem and it seems to be the same *except* I have the "nRF91 LTE Link control library" enabled on my own build. I have the LTE-M selected as my network mode, but it just keeps pulsing that it's searching, but if I run the commands you mentioned:

AT+CFUN=4
AT%XSYSTEMMODE=1,0,0,0
AT+CFUN=1

Then it works fine. What would I have wrong in the kconfig? That seems to be where my issue is, but I can't quite spot it.

RE: LTE Link Monitor Issue with 9160

SoTXhelp — Wed, 03 Aug 2022 13:59:16 GMT

Hello Benjamin,

In the Systemmode command you can instruct the modem that You want to have a primary selection of Cat M1, you could enable or disable GNSS as an option and lastly you can tell the instuction that you only want Cat M1 Mode or have the option to search both networks.

If you will only be in M1 then I suggest

AT%SYSTEMMODE=1,0,0,1

As Charlie points out, The clue was the CEREG with the indication of NB selected "9".

Helping decipher what we see in the log that aids in the diagnostic for us.

< +CEREG: 2,"F1D4","016186CB",9,0,11

We see the still searching "2", "TAC"=0xF1D4, "CellID"= 0x016186 CB, "9" = NB,"0",EMM Error code "11" Cause #11 – PLMN not allowed

Tmobile Network PLMN = 310260

Cellmapper Tmobile Tower Location

< %CESQ: 36,1,20,2 - Signal quality -104

< %CESQ: 255,0,255,0 - Switching tower reselection: indicated by no signal

< %CESQ: 47,2,11,1

New tower selected

< +CEREG: 2,"9C14","06E9E03B",9

We are still searching for the network "2", Tracking Area "0x9C14", CellID 0x06E9E0 3B

ATT PLMN 310410

Cellmapper AT&T Tower Location

< +CNEC_EMM: 15 - We are receiving an EMM Error "15" Cause #15 – No suitable cells in tracking area

< +CEREG: 2,"9C14","06E9E03B",9,0,15

Repeat from above with additional EMM 15 error (No Suitable cells in tracking area.

< %CESQ: 255,0,255,0

Reselection Still searching

< +CEREG: 2

< +CEREG: 2,"0D92","0034571E",9

New Network, Tracking Area "0x0D92", CellID 0x003457 1E

Verizon PLMN 311480

Cellmapper Verizon Tower Location Link

< +CNEC_ESM: 32,0

ESM Error 32 = Cause #32 – Service option not supported

< +CNEC_EMM: 19

EMM Error 19 = Cause #19 – ESM failure

< +CEREG: 2,"0D92","0034571E",9,0,19

< +CEREG: 2

RE: LTE Link Monitor Issue with 9160

Charlie — Wed, 03 Aug 2022 08:58:17 GMT

Hi Benjamin,

The log "+CEREG: 2,"0D92","0034571E",9,0,19" shows your device is trying to attach to an NB-IoT network, which may be not supported by iBasis.

Can you try setting the device to connect to the LTE-M network with the following commands?

AT+CFUN=4
AT%XSYSTEMMODE=1,0,0,0
AT+CFUN=1

Best regards,

Charlie

RE: LTE Link Monitor Issue with 9160

Benjamin — Tue, 02 Aug 2022 20:32:38 GMT

I'm running on an M1 Mac.

I ran those commands after the device had been on for over 10min I believe, here is the resulting log file. Thank you for your help!

2022-08-02T20:16:50.919Z DEBUG Application data folder: /Users/user/Library/Application Support/nrfconnect/pc-nrfconnect-linkmonitor
2022-08-02T20:16:52.075Z INFO Using nrf-device-lib-js version: 0.4.11
2022-08-02T20:16:52.076Z INFO Using nrf-device-lib version: 0.11.8
2022-08-02T20:16:52.077Z INFO Using nrfjprog DLL version: 10.15.4
2022-08-02T20:16:52.077Z INFO Using JLink version: JLink_V7.64e
2022-08-02T20:16:52.226Z DEBUG App pc-nrfconnect-linkmonitor v2.0.1 official
2022-08-02T20:16:52.226Z DEBUG App path: /Users/user/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2022-08-02T20:16:52.226Z DEBUG nRFConnect 3.11.1, required by the app is (^3.8.0)
2022-08-02T20:16:52.226Z DEBUG nRFConnect path: /Applications/nRF Connect for Desktop.app/Contents/Resources/app.asar
2022-08-02T20:16:52.226Z DEBUG HomeDir: /Users/user
2022-08-02T20:16:52.226Z DEBUG TmpDir: /var/folders/0l/h7c0fmrn2s99zfj4sb1qlk_r0000gn/T/
2022-08-02T20:16:52.244Z INFO Installed JLink version does not match the provided version (V7.58b)
2022-08-02T20:17:01.826Z INFO Modem port is opened
2022-08-02T20:17:01.853Z DEBUG modem >> AT+CFUN?
2022-08-02T20:17:01.917Z DEBUG modem << +CFUN: 0
2022-08-02T20:17:01.920Z DEBUG modem << OK
2022-08-02T20:17:08.002Z DEBUG modem >> AT+CFUN=1
2022-08-02T20:17:08.040Z DEBUG modem << OK
2022-08-02T20:17:09.590Z DEBUG modem >> AT+CFUN?
2022-08-02T20:17:09.595Z DEBUG modem << +CFUN: 1
2022-08-02T20:17:09.611Z DEBUG modem << OK
2022-08-02T20:17:09.617Z DEBUG modem >> AT+CGSN=1
2022-08-02T20:17:09.629Z DEBUG modem << +CGSN: "351358811117313"
2022-08-02T20:17:09.635Z DEBUG modem << 
2022-08-02T20:17:09.696Z DEBUG modem << OK
2022-08-02T20:17:09.704Z DEBUG modem >> AT+CGMI
2022-08-02T20:17:09.710Z DEBUG modem << Nordic Semiconductor ASA
2022-08-02T20:17:09.731Z DEBUG modem << 
2022-08-02T20:17:09.747Z DEBUG modem << OK
2022-08-02T20:17:09.772Z DEBUG modem >> AT+CGMM
2022-08-02T20:17:09.790Z DEBUG modem << nRF9160-SICA
2022-08-02T20:17:09.801Z DEBUG modem << OK
2022-08-02T20:17:09.827Z DEBUG modem >> AT+CGMR
2022-08-02T20:17:09.831Z DEBUG modem << mfw_nrf9160_1.3.2
2022-08-02T20:17:09.834Z DEBUG modem << 
2022-08-02T20:17:09.837Z DEBUG modem << OK
2022-08-02T20:17:09.838Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.2] SerNr: 351358811117313
2022-08-02T20:17:09.839Z DEBUG modem >> AT+CEMODE?
2022-08-02T20:17:09.867Z DEBUG modem << +CEMODE: 0
2022-08-02T20:17:09.888Z DEBUG modem << OK
2022-08-02T20:17:09.944Z DEBUG modem >> AT%XCBAND=?
2022-08-02T20:17:09.957Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
2022-08-02T20:17:09.966Z DEBUG modem << 
2022-08-02T20:17:09.967Z DEBUG modem << OK
2022-08-02T20:17:09.998Z DEBUG modem >> AT+CMEE?
2022-08-02T20:17:10.005Z DEBUG modem << +CMEE: 0
2022-08-02T20:17:10.010Z DEBUG modem << OK
2022-08-02T20:17:10.018Z DEBUG modem >> AT+CMEE=1
2022-08-02T20:17:10.022Z DEBUG modem << OK
2022-08-02T20:17:10.029Z DEBUG modem >> AT+CNEC?
2022-08-02T20:17:10.032Z DEBUG modem << +CNEC: 0
2022-08-02T20:17:10.037Z DEBUG modem << OK
2022-08-02T20:17:10.057Z DEBUG modem >> AT+CNEC=24
2022-08-02T20:17:10.061Z DEBUG modem << OK
2022-08-02T20:17:10.068Z DEBUG modem >> AT+CGEREP?
2022-08-02T20:17:10.092Z DEBUG modem << +CGEREP: 0,0
2022-08-02T20:17:10.094Z DEBUG modem << 
2022-08-02T20:17:10.099Z DEBUG modem << OK
2022-08-02T20:17:10.105Z DEBUG modem >> AT+CGDCONT?
2022-08-02T20:17:10.113Z DEBUG modem << OK
2022-08-02T20:17:10.115Z DEBUG modem >> AT+CGACT?
2022-08-02T20:17:10.118Z DEBUG modem << OK
2022-08-02T20:17:10.120Z DEBUG modem >> AT+CGEREP=1
2022-08-02T20:17:10.124Z DEBUG modem << OK
2022-08-02T20:17:10.136Z DEBUG modem >> AT+CIND=1,1,1
2022-08-02T20:17:10.140Z DEBUG modem << OK
2022-08-02T20:17:10.142Z DEBUG modem >> AT+CEREG=5
2022-08-02T20:17:10.145Z DEBUG modem << OK
2022-08-02T20:17:10.147Z DEBUG modem >> AT+CEREG?
2022-08-02T20:17:10.151Z DEBUG modem << +CEREG: 5,4
2022-08-02T20:17:10.159Z DEBUG modem << OK
2022-08-02T20:17:10.190Z DEBUG modem >> AT%CESQ=1
2022-08-02T20:17:10.195Z DEBUG modem << OK
2022-08-02T20:17:10.197Z DEBUG modem >> AT+CESQ
2022-08-02T20:17:10.202Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-08-02T20:17:10.209Z DEBUG modem << OK
2022-08-02T20:17:10.213Z DEBUG modem >> AT%XSIM=1
2022-08-02T20:17:10.218Z DEBUG modem << OK
2022-08-02T20:17:10.225Z DEBUG modem >> AT%XSIM?
2022-08-02T20:17:10.228Z DEBUG modem << %XSIM: 1
2022-08-02T20:17:10.237Z DEBUG modem << 
2022-08-02T20:17:10.243Z DEBUG modem << OK
2022-08-02T20:17:10.247Z DEBUG modem >> AT+CPIN?
2022-08-02T20:17:10.252Z DEBUG modem << +CPIN: READY
2022-08-02T20:17:10.260Z DEBUG modem << OK
2022-08-02T20:17:10.318Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-08-02T20:17:10.336Z DEBUG modem << +CPINR: "SIM PIN",3
2022-08-02T20:17:10.338Z DEBUG modem << OK
2022-08-02T20:17:10.357Z DEBUG modem >> AT+CIMI
2022-08-02T20:17:10.361Z DEBUG modem << 204080813694050
2022-08-02T20:17:10.362Z DEBUG modem << 
2022-08-02T20:17:10.363Z DEBUG modem << OK
2022-08-02T20:17:10.364Z INFO IMSIdentity: 204080813694050
2022-08-02T20:18:46.318Z DEBUG modem << %CESQ: 34,1,19,2
2022-08-02T20:18:46.352Z DEBUG modem << +CEREG: 2,"F1D4","016186CB",9
2022-08-02T20:18:46.389Z DEBUG modem << %CESQ: 36,1,25,3
2022-08-02T20:18:46.605Z DEBUG modem << +CNEC_EMM: 11
2022-08-02T20:18:46.614Z DEBUG modem << +CEREG: 2,"F1D4","016186CB",9,0,11
2022-08-02T20:18:46.939Z DEBUG modem << %CESQ: 36,1,20,2
2022-08-02T20:18:46.981Z DEBUG modem << %CESQ: 255,0,255,0
2022-08-02T20:18:48.959Z DEBUG modem << %CESQ: 47,2,11,1
2022-08-02T20:18:48.968Z DEBUG modem << +CEREG: 2,"9C14","06E9E03B",9
2022-08-02T20:18:50.106Z DEBUG modem << +CNEC_EMM: 15
2022-08-02T20:18:50.156Z DEBUG modem << +CEREG: 2,"9C14","06E9E03B",9,0,15
2022-08-02T20:18:51.246Z DEBUG modem << %CESQ: 255,0,255,0
2022-08-02T20:18:51.260Z DEBUG modem << +CEREG: 2
2022-08-02T20:19:00.527Z DEBUG modem << %CESQ: 49,2,16,2
2022-08-02T20:19:27.295Z DEBUG modem << %CESQ: 48,2,9,1
2022-08-02T20:19:30.419Z DEBUG modem << %CESQ: 48,2,15,2
2022-08-02T20:19:32.462Z DEBUG modem << %CESQ: 255,0,255,0
2022-08-02T20:19:37.557Z DEBUG modem << %CESQ: 44,2,13,1
2022-08-02T20:19:37.572Z DEBUG modem << +CEREG: 2,"0D92","0034571E",9
2022-08-02T20:19:37.896Z DEBUG modem << +CNEC_ESM: 32,0
2022-08-02T20:19:37.906Z DEBUG modem << +CNEC_EMM: 19
2022-08-02T20:19:37.912Z DEBUG modem << +CEREG: 2,"0D92","0034571E",9,0,19
2022-08-02T20:19:38.327Z DEBUG modem << %CESQ: 255,0,255,0
2022-08-02T20:19:38.608Z DEBUG modem << %CESQ: 48,2,15,2
2022-08-02T20:19:38.617Z DEBUG modem << +CEREG: 2
2022-08-02T20:20:14.293Z DEBUG modem << %CESQ: 255,0,255,0
2022-08-02T20:20:14.766Z DEBUG modem << %CESQ: 44,2,14,2
2022-08-02T20:20:16.250Z DEBUG modem << %CESQ: 44,2,21,3
2022-08-02T20:20:34.171Z DEBUG modem << %CESQ: 42,2,15,2
2022-08-02T20:20:59.771Z DEBUG modem << %CESQ: 44,2,20,2
2022-08-02T20:21:30.490Z DEBUG modem << %CESQ: 41,2,14,2
2022-08-02T20:21:38.171Z DEBUG modem << %CESQ: 43,2,20,2
2022-08-02T20:27:28.891Z DEBUG modem << %CESQ: 42,2,15,2
2022-08-02T20:27:46.810Z DEBUG modem << %CESQ: 45,2,23,3
2022-08-02T20:27:51.932Z DEBUG modem << %CESQ: 45,2,18,2
2022-08-02T20:28:24.401Z DEBUG modem >> AT+CEREG=5
2022-08-02T20:28:24.414Z DEBUG modem << OK
2022-08-02T20:28:35.486Z DEBUG modem >> AT+CNEC=24
2022-08-02T20:28:35.499Z DEBUG modem << OK
2022-08-02T20:28:46.857Z DEBUG modem >> AT%CESQ=1
2022-08-02T20:28:46.869Z DEBUG modem << OK
2022-08-02T20:28:54.402Z DEBUG modem >> AT+CSCON=3
2022-08-02T20:28:54.412Z DEBUG modem << OK
2022-08-02T20:29:02.220Z DEBUG modem >> AT+CMEE=1
2022-08-02T20:29:02.232Z DEBUG modem << OK
2022-08-02T20:29:09.603Z DEBUG modem >> AT%XMODEMTRACE=1,2
2022-08-02T20:29:09.618Z DEBUG modem << OK
2022-08-02T20:29:19.786Z DEBUG modem >> AT+CEINFO=1
2022-08-02T20:29:19.804Z DEBUG modem << +CEINFO: 1,1,I,8,1,-97,1
2022-08-02T20:29:19.806Z DEBUG modem << OK
2022-08-02T20:29:30.638Z DEBUG modem >> AT%MDMEV=1
2022-08-02T20:29:30.649Z DEBUG modem << OK
2022-08-02T20:29:40.403Z DEBUG modem >> AT%XMONITOR
2022-08-02T20:29:40.423Z DEBUG modem << %XMONITOR: 2
2022-08-02T20:29:40.424Z DEBUG modem << OK
2022-08-02T20:29:42.403Z DEBUG modem >> AT+CFUN?
2022-08-02T20:29:42.414Z DEBUG modem << +CFUN: 1
2022-08-02T20:29:42.421Z DEBUG modem << OK
2022-08-02T20:29:42.422Z DEBUG modem >> AT+CGSN=1
2022-08-02T20:29:42.433Z DEBUG modem << +CGSN: "351358811117313"
2022-08-02T20:29:42.435Z DEBUG modem << 
2022-08-02T20:29:42.436Z DEBUG modem << OK
2022-08-02T20:29:42.438Z DEBUG modem >> AT+CGMI
2022-08-02T20:29:42.452Z DEBUG modem << Nordic Semiconductor ASA
2022-08-02T20:29:42.455Z DEBUG modem << 
2022-08-02T20:29:42.459Z DEBUG modem << OK
2022-08-02T20:29:42.465Z DEBUG modem >> AT+CGMM
2022-08-02T20:29:42.480Z DEBUG modem << nRF9160-SICA
2022-08-02T20:29:42.481Z DEBUG modem << 
2022-08-02T20:29:42.482Z DEBUG modem << OK
2022-08-02T20:29:42.490Z DEBUG modem >> AT+CGMR
2022-08-02T20:29:42.513Z DEBUG modem << mfw_nrf9160_1.3.2
2022-08-02T20:29:42.514Z DEBUG modem << 
2022-08-02T20:29:42.515Z DEBUG modem << OK
2022-08-02T20:29:42.516Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.2] SerNr: 351358811117313
2022-08-02T20:29:42.523Z DEBUG modem >> AT+CEMODE?
2022-08-02T20:29:42.537Z DEBUG modem << +CEMODE: 0
2022-08-02T20:29:42.539Z DEBUG modem << OK
2022-08-02T20:29:42.546Z DEBUG modem >> AT%XCBAND=?
2022-08-02T20:29:42.561Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
2022-08-02T20:29:42.562Z DEBUG modem << OK
2022-08-02T20:29:42.570Z DEBUG modem >> AT+CMEE?
2022-08-02T20:29:42.578Z DEBUG modem << +CMEE: 1
2022-08-02T20:29:42.579Z DEBUG modem << OK
2022-08-02T20:29:42.585Z DEBUG modem >> AT+CNEC?
2022-08-02T20:29:42.596Z DEBUG modem << +CNEC: 24
2022-08-02T20:29:42.598Z DEBUG modem << 
2022-08-02T20:29:42.603Z DEBUG modem << OK
2022-08-02T20:29:42.605Z DEBUG modem >> AT+CGEREP?
2022-08-02T20:29:42.615Z DEBUG modem << +CGEREP: 1,0
2022-08-02T20:29:42.617Z DEBUG modem << OK
2022-08-02T20:29:42.624Z DEBUG modem >> AT+CIND=1,1,1
2022-08-02T20:29:42.634Z DEBUG modem << OK
2022-08-02T20:29:42.641Z DEBUG modem >> AT+CEREG=5
2022-08-02T20:29:42.645Z DEBUG modem << OK
2022-08-02T20:29:42.647Z DEBUG modem >> AT+CEREG?
2022-08-02T20:29:42.655Z DEBUG modem << +CEREG: 5,2
2022-08-02T20:29:42.656Z DEBUG modem << OK
2022-08-02T20:29:42.662Z DEBUG modem >> AT%CESQ=1
2022-08-02T20:29:42.672Z DEBUG modem << OK
2022-08-02T20:29:42.674Z DEBUG modem >> AT+CESQ
2022-08-02T20:29:42.685Z DEBUG modem << +CESQ: 99,99,255,255,18,43
2022-08-02T20:29:42.686Z DEBUG modem << 
2022-08-02T20:29:42.687Z DEBUG modem << OK
2022-08-02T20:29:42.690Z DEBUG modem >> AT%XSIM=1
2022-08-02T20:29:42.705Z DEBUG modem << OK
2022-08-02T20:29:42.710Z DEBUG modem >> AT%XSIM?
2022-08-02T20:29:42.715Z DEBUG modem << %XSIM: 1
2022-08-02T20:29:42.716Z DEBUG modem << 
2022-08-02T20:29:42.717Z DEBUG modem << OK
2022-08-02T20:29:42.720Z DEBUG modem >> AT+CPIN?
2022-08-02T20:29:42.728Z DEBUG modem << +CPIN: READY
2022-08-02T20:29:42.729Z DEBUG modem << OK
2022-08-02T20:29:42.732Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-08-02T20:29:42.748Z DEBUG modem << +CPINR: "SIM PIN",3
2022-08-02T20:29:42.750Z DEBUG modem << 
2022-08-02T20:29:42.750Z DEBUG modem << OK
2022-08-02T20:29:42.753Z DEBUG modem >> AT+CIMI
2022-08-02T20:29:42.763Z DEBUG modem << 204080813694050
2022-08-02T20:29:42.764Z DEBUG modem << 
2022-08-02T20:29:42.765Z DEBUG modem << OK
2022-08-02T20:29:42.765Z INFO IMSIdentity: 204080813694050
2022-08-02T20:31:38.071Z DEBUG modem << +CEINFO: 1,1,R,8,1,-98,0
2022-08-02T20:31:38.270Z DEBUG modem << +CSCON: 1,7,4
2022-08-02T20:31:38.329Z DEBUG modem << +CEINFO: 1,1,C,2,1,-98,0
2022-08-02T20:31:38.403Z DEBUG modem << +CNEC_ESM: 32,0
2022-08-02T20:31:38.430Z DEBUG modem << +CNEC_EMM: 19
2022-08-02T20:31:38.435Z DEBUG modem << +CEREG: 2,"0D92","0034571E",9,0,19
2022-08-02T20:31:38.482Z DEBUG modem << +CSCON: 0,7,4
2022-08-02T20:31:38.772Z DEBUG modem << +CEINFO: 1,1,I,8,1,-97,-3
2022-08-02T20:31:38.810Z DEBUG modem << %CESQ: 255,0,255,0
2022-08-02T20:31:38.826Z DEBUG modem << +CEINFO: 1,1,I,0,0,255,127
2022-08-02T20:31:39.253Z DEBUG modem << %CESQ: 46,2,12,1
2022-08-02T20:31:39.261Z DEBUG modem << +CEINFO: 1,1,I,2,1,-95,0
2022-08-02T20:31:39.269Z DEBUG modem << +CEREG: 2

RE: LTE Link Monitor Issue with 9160

SoTXhelp — Tue, 02 Aug 2022 19:40:40 GMT

Benjamin,

It appears that you are having issues with your SIM connecting to the tower. The CEREG:2 indicates that the UE is still searching for a network to attach to. The RSRP levels show good signal. In your screen shot it looks like you are averaging -94 dBm. Then you see the -255 where the board lost the connection and then the signal level is then -100 dBm. At this point you get the CEREG:2 indicating the UE is searching for the network still.

Can you add these AT commands to help provide more information?

AT+CEREG=5

AT+CNEC=24

AT%CESQ=1

AT+CSCON=3

AT+CMEE=1

AT%XMODEMTRACE=1,2

AT+CEINFO=1

AT%MDMEV=1

AT%XMONITOR

The LTE Link Monitor application only polls during the Automatic update when you send AT+CFUN?. If any of the display buttons change after the initial script the condition won't be updated until the next auto script.

Are you using Linux or Apple ? The screen shows the board as a logical device. The Windows version is not similar.

The screen shots limit what we can see compared to posting the Log File. The log file is much more helpful. The binary trace file is even better to help troubleshoot the issue you may be having.

Regards,

Don

RE: LTE Link Monitor Issue with 9160

Benjamin — Tue, 02 Aug 2022 15:37:15 GMT

With the at_client I still have issues when trying to follow the main at commands. I did double check I have plenty of available data on the iBasis sim card, which I know at least used to connect to LTE-M and I could send data to the cloud. This is what I'm seeing now. I'm confused as to why the UART one is red, but the LTE one just keeps pulsing yellow and red.

RE: LTE Link Monitor Issue with 9160

Charlie — Tue, 02 Aug 2022 09:00:41 GMT

Hi Benjamin,

This is as expected.

at_client and serial_lte_modem examples are designed for developers to set up and run the device with commands manually, run "AT+CFUN=1" will connect the device with the cellular network. It will take some time before the device finds a network and all labels turn green. The "Automatic requests" SETTINGS will run some commands following your "AT+CFUN?" to check current network states.

Best regards,

Charlie