[NRF9151] Modem does not connect after SIM deactivate/reactivate

[Mlgr]

Hi,

I’m using the Thingy:91X board with the nRF9151 chip, modem firmware version 2.0.2, and SDK version 2.9.0.

We’re encountering a serious issue: the modem does not reconnect after the SIM has been deactivated and then reactivated.

I’ve tried:

• sys_reboot(SYS_REBOOT_COLD)

• Placing the modem offline (lte_lc_offline())

• Shutting down the modem library (nrf_modem_lib_shutdown())

• Forcing a hard reboot via the watchdog

None of these approaches has worked.

Do you have any suggestions for resolving this issue?

The only workaround so far (which isn’t acceptable) is to manually power the device off and on.

Regards,
Mathieu

[Achim Kraus]

Not sure, how you really tested that.

There may be two pitfalls:

- the reactivation of the SIM may take some time (in some cases more minutes, even longer, especially, if you deactivate and reactivate multiple times in just a few minutes)

- some rejection cause are treated "sticky" by the modem. That requires usually to wait some time or do a "lte_lc_power_off/lte_lc_normal" cycle (but I didn't retest that for a nRF9151)

So, let me propose, that you try to wait a minute or so after reactivate the SIM until you test to connect the modem again. If that results in rejected registrations, then try a "lte_lc_power_off/lte_lc_normal" cycle.

[Mlgr]

Hello Achim,

I let the card run for a few days, but it never reconnected to the network. However, I have a watchdog that reboots the card after “x” minutes without data. Should I disable it? Could it be causing a conflict with the modem in the new version?

I already tried the lte_lc_power_off/lte_lc_normal cycle, but it didn’t work (the watchdog still rebooted the card after a few minutes).

Best regards,
Mathieu

[Achim Kraus]

Mlgr said:

If I understand correctly, the calls to lte_lc_power_off and lte_lc_normal should work.

Yes, that was my experience with the nRF9160/mfw1.3.7 and is now the same in the retest with the nRF9151/mfw2.0.2. 

Mlgr said:

I’ll retry them and increase the watchdog timeout to give the modem enough time to reconnect without being reset during the process.

It should be at least worth to be tested.

Mlgr said:

I’ll let you know the results.

I'm looking forward.

[Mlgr]

I tried retesting using the lte_lc_power_off / lte_lc_normal cycle on disconnection, but now my device doesn’t connect at all, it just hangs after the “Searching” event (the same thing happens when I deactivate/reactivate the SIM but this SIM was always activated).

I enabled tracing as described here: https://docs.nordicsemi.com/bundle/ncs-2.9.0/page/nrf/libraries/modem/nrf_modem_lib/nrf_modem_lib_trace.html, but all I get are these logs:

[00:00:01.526,733] <inf> modem_trace_backend: Modem_trace RTT backend channel 1  
[00:00:01.526,733] <inf> nrf_modem_lib_trace: Trace thread ready  
[00:00:01.534,637] <inf> nrf_modem_lib_trace: Trace level override: 2  
[00:00:01.782,501] <err> nrf_modem_lib_trace: trace_backend.write failed with err: -63  
…  
[00:00:08.544,372] <err> nrf_modem_lib_trace: trace_backend.write failed with err: -63  
[00:00:13.396,179] <inf> lte_monitor: Network: Searching

I haven’t changed anything in this software version, and it was working fine two weeks ago. I’m really lost.

[Achim Kraus]

Mlgr said:

I haven’t changed anything in this software version, and it was working fine two weeks ago. I’m really lost.

You added the power_off/normal cycle and the modem trace via RTT.

I would start removing both and retest. If you use versioning, that may be easier to checkout a last working version and retest that.

And then adding one change step by step and see, if both stops the device from working or just one.

----------------------------------------------------------------------------------------

I'm used to trace the mode via UART and sometimes use the FLASH to keep a the trace for a time span (and afterward write that to the UART).

I never tried the RTT interface for the modem trace before, but at least using a nRF9151-DK, NCS 2.9.2, Ubuntu doesn't work for me either. I enabled it via the snippet, it start to report quite a lot of "trace_backend.write failed with err: -63". But using

nrfjprog --reset && JLinkRTTLogger -Device NRF9151_XXCA -If SWD -Speed 50000  modemtracesrtt.bin

(see How to capture nrf9160 modem traces using RTT? ) 

only reports:

SEGGER J-Link RTT Logger
Compiled Mar  5 2025 14:51:21
(c) 2016-2017 SEGGER Microcontroller GmbH, www.segger.com
         Solutions for real time microcontroller applications

Default logfile path: /home/achim/.config/SEGGER

------------------------------------------------------------ 


------------------------------------------------------------ 
Connected to:
  SEGGER J-Link (unknown)
  S/N: 1051240195

Searching for RTT Control Block...OK.
3 up-channels found:
0: Terminal
1: 
2: 
Selected RTT Channel description: 
  Index: 1
  Name:  
  Size:  0 bytes.

Output file: modemtracesrtt.bin

Getting RTT data from target. Press any key to quit.
------------------------------------------------------------ 

Transfer rate: 0 Bytes/s Data written: 0 Bytes 0

Not sure, may be this requires someone from Nordic to retest the modem trace via RTT. 

[Mlgr]

Achim Kraus said:

You added the power_off/normal cycle and the modem trace via RTT.

I would start removing both and retest. If you use versioning, that may be easier to checkout a last working version and retest that.

And then adding one change step by step and see, if both stops the device from working or just one.

That’s the problem: I flashed the same software that worked two weeks ago, but now this board won’t connect, even though it connects fine on another board. I think we received a defective batch, I’ve already thrown away five or six boards.

The modem sends a “Searching” event and then does nothing. That’s why I tried enabling modem tracing. But when I read its output over UART the data appears garbled, even though my DTS settings (baud rate, pins, etc.) are correct and I’m using 1,000,000 baud / 8 data bits / 1 start bit / 1 stop bit / no parity. I don’t know why the output isn’t legible, so I’m switching to RTT instead.

I really don’t understand why I’m having modem issues; I’ve never seen this with the Thingy:91 and I haven’t changed anything in my code.

On startup I call:

1. nrf_modem_lib_init()

2. modem_info_init()

3. modem_info_rsrp_register()

4. lte_lc_connect_async()

On shutdown I call:

• lte_lc_offline()

I have another board running exactly the same software and it works fine (I’d rather not deactivate/reactivate its SIM because I need it for something else).

Am I doing something wrong in my initialization sequence?

[dejans]

Hi,

Can you show how you enable tracing over UART and RTT?
You can read more about modem tracing and modem trace module in the documentation.

Best regards,
Dejan

[Achim Kraus]

I don't know, how Mathieu enabled the modem trace, in my test I did it with the snippets "west build -S nrf91-modem-trace-uart ..." and "west build -S nrf91-modem-trace-rtt ...".

With the UART it works, with RTT I wasn't able to get the trace and got only warnings in the logging console instead.

NCS 2.9.2, nRF9151-DK, mfw 2.0.2. 

Ubuntu, JLinkRTTLogger V8.18

nrfjprog --reset && JLinkRTTLogger -Device NRF9151_XXCA -If SWD -Speed 50000  modemtracesrtt.bin

(As already mentioned above.)

But the modem trace is rather a side issue.

[dejans]

Hi Mathieu,

Have you made some progress?

Have you been able to capture modem trace, possibly following Achim's suggestion using modem trace snippet?

Which mobile network operator does your device connect to?

Due to frequent rebooting via watchdog, it could be that reset loop restriction was triggered.

Best regards,
Dejan

[Jon]

Hi !

We were not really able to make some progress. 

We were not able to get modem traces. I was not able to do it with UART1, since the uart1 is used for other purposes, and the connectivy_bridge is not used anymore. That's why we redirect all our app uart to RTT.

So, i tried to use the RTT modem trace snippet. 
I also get the -63 error.



By the way, i get nothing on channel 2, about modem traces. It remains empty

Here is the command i used to build

of course, i used the link given for the snippet.

Well, it seems i won't be able to get some modem traces :)

About the operator, i tried with a Onomondo sim until now.   My device connects to Bouygues Telecom Network (by using onomondo or Tele2).

Tomorrow, i will check with some TELE2 sim, and a brand new Thingy91X. I'll give you more infos then.

[dejans]

Hi,

For additional information about capturing modem traces, you can refer to these links in documentation
modem tracing and capturing modem trace using Cellular Monitor.

Jon said:

Tomorrow, i will check with some TELE2 sim, and a brand new Thingy91X. I'll give you more infos then.

I am looking forward to your update.

Best regards,
Dejan

[Jon]

Hi,

Here are some news :)
We were not able to plug our app with the tracing tools. But we are really stuck, so we changed our approch.

We reproduced the problem by using the Nordic modem shell example.

You will find attach all the command we did.  At the beginning, we are able to reach the network, we generate the problem by deactivating the sim and reactivating it later after having  done a at+CFUN=0 and at+CFUN1 (2/3 minutes after), 

By the end of the file, you can see we tried several stuff to connect but it never work. 

THe only way to reach the network again is by power cycling the thingy91x

What are your thoughts ?

Fullscreen serial-terminal-06082025_165918.txt Download

> at AT+CFUN=1
at AT+CFUN=1
OK
mosh:~$ > at AT%XCONNSTAT=1
at AT%XCONNSTAT=1
OK
mosh:~$ > at AT%XCONNSTAT?
at AT%XCONNSTAT?
%XCONNSTAT: 0,0,0,0,0,0
OK
mosh:~$ > at AT+CMEE=1
at AT+CMEE=1
OK
mosh:~$ > at AT%XSIM=1
at AT%XSIM=1
OK
mosh:~$ > at AT+CEREG=5
at AT+CEREG=5
OK
mosh:~$ > at AT%MDMEV=1
at AT%MDMEV=1
OK
mosh:~$ > at AT%CESQ=1
at AT%CESQ=1
OK
mosh:~$ > at AT+CGSN=1
at AT+CGSN=1
+CGSN: "359404230274905"
OK
mosh:~$ > at AT+CGMM
at AT+CGMM
nRF9151-LACA
OK
mosh:~$ > at AT+CEMODE?
at AT+CEMODE?
+CEMODE: 2
OK
mosh:~$ > at AT+CMEE?
jH AT+CMEE?+SQ
mosh:~$ at AT+CNEC?> at AT+CNEC?
H+CNEC: 16
OK
mosh:~$ > at AT+CGEREP?
at AT+CGEREP?
+CGEREP: 1,0
OK
mosh:~$ > at AT+CIND=1,1,1
at AT+CIND=1,1,1
OK
mosh:~$ > at AT+COPS=3,2
at AT+COPS=3,2
OK
mosh:~$ > at AT+CGDCONT?
at AT+CGDCONT?
OK
mosh:~$ > at AT+CGACT?
at AT+CGACT?
OK
mosh:~$ > at AT+CESQ
at AT+CESQ
+CESQ: 99,99,255,255,255,255
OK
mosh:~$ > at AT%XSIM?
at AT%XSIM?
%XSIM: 1
OK
mosh:~$ > at AT+CPIN?
at AT+CPIN?H+CPIN: READY
OK
mosh:~$ > at AT+CIMI
at AT+CIMI
240075823634698
OK
mosh:~$ > at AT+CNEC=24
at AT+CNEC=24
OK
mosh:~$ > at AT+CEER
at AT+CEER
OK
mosh:~$ > at AT+CGEREP=1
at AT+CGEREP=1
Network registration status: searching
OK
Currently active system mode: LTE-M
RRC mode: Connected
mosh:~$ > at AT%XPOFWARN=1,30
at AT%XPOFWARN=1,30
LTE cell changed: ID: 25533958, Tracking area: 52644
OK
mosh:~$ > at AT%XVBATLVL=1
at AT%XVBATLVL=1
OK
mosh:~$ > at AT+CGMI
at AT+CGMI
Nordic Semiconductor ASA
OK
mosh:~$ > at AT+CGMR
at AT+CGMR
mfw_nrf91x1_2.0.2
OK
mosh:~$ > at AT+CGSN
at AT+CGSN
359404230274905
OK
mosh:~$ > at AT%XMODEMUUID
at AT%XMODEMUUID
%XMODEMUUID: 320176d5-9f40-45fc-923b-2661ec18d547
OK
mosh:~$ > at AT%XDATAPRFL?
at AT%XDATAPRFL?
%XDATAPRFL: 2
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 5,2,"CDA4","01859E06",7
OK
mosh:~$ > at AT+CFUN?
at AT+CFUN?
+CFUN: 1
OK
mosh:~$ > at AT%CESQ=1
at AT%CESQ=1
OK
mosh:~$ > at AT+CSCON=1
at AT+CSCON=1
OK
mosh:~$ > at AT+CSCON?
at AT+CSCON?
+CSCON: 1,1
OK
mosh:~$ > at AT+CPAS
at AT+CPAS
+CPAS: 0
OK
mosh:~$ > at AT+CEDRXRDP
at AT+CEDRXRDP
+CEDRXRDP: 0
OK
mosh:~$ > at AT%XTIME=1
at AT%XTIME=1
OK
mosh:~$ > at AT%CONEVAL
at AT%CONEVAL
%CONEVAL: 6
OK
mosh:~$ > at AT%XCBAND=?
at AT%XCBAND=?
%XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66,85)
OK
mosh:~$ > at AT%XCBAND
at AT%XCBAND
%XCBAND: 20
OK
mosh:~$ > at AT%HWVERSION
at AT%HWVERSION
%HWVERSION: nRF9151 LACA A0A
OK
mosh:~$ > at AT%XMODEMTRACE=1,2
at AT%XMODEMTRACE=1,2
OK
mosh:~$ > at AT%XSYSTEMMODE?
at AT%XSYSTEMMODE?
%XSYSTEMMODE: 1,1,1,3
OK
mosh:~$ > at AT%XICCID
at AT%XICCID
%XICCID: 89462038075015721859
OK
mosh:~$ > at AT%XEMPR?
at AT%XEMPR?
%XEMPR:
OK
mosh:~$ > at AT+CGDCONT?
at AT+CGDCONT?
+CGDCONT: 0,"","","",0,0
OK
mosh:~$ > at AT+COPS?
at AT+COPS?H+COPS: 0
OK
mosh:~$ > at AT%XMONITOR
at AT%XMONITOR
%XMONITOR: 2
OK
mosh:~$ > at AT+CPINR="SIM PIN"
at AT+CPINR="SIM PIN"
+CPINR: "SIM PIN",3
OK
mosh:~$ > at AT+CPINR="SIM PIN2"
at AT+CPINR="SIM PIN2"
+CPINR: "SIM PIN2",3
OK
mosh:~$ > at AT+CPINR="SIM PUK"
at AT+CPINR="SIM PUK"
+CPINR: "SIM PUK",10
OK
mosh:~$ > at AT+CPINR="SIM PUK2"
at AT+CPINR="SIM PUK2"
+CPINR: "SIM PUK2",10
OK
mosh:~$ > at AT%XSIM?
at AT%XSIM?H%XSIM: 1
OK
PDN event: PDP context 0 activated
PDN event: PDP context 0, PDN type IPv4 only allowed
Modem domain event: Search done
Network registration status: Connected - roaming
PSM parameter update: TAU: 3240, Active time: -1 seconds
Modem config for system mode: LTE-M - NB-IoT - GNSS
Modem config for LTE preference: LTE-M is preferred, but PLMN selection is more important
Currently active system mode: LTE-M
r׋e:       5046 mV
Modem temperature:     25 C
mosh:~$ Device ID:             nrf-359404230274905
Operator full name:   "Orange F"
Operator short name:  "Orange F"
Operator PLMN:        "20801"
Current cell id:       25533958 (0x01859E06)
Current phy cell id:   290
Current band:          20
Current TAC:           52644 (0xCDA4)
Current rsrp:          29: -112dBm
Current snr:           24: 0dB
Mobile network time and date: 25/08/06,14:34:44+08
PDP context info 1:
CID:                0
PDN ID:             0
PDP context active: yes
PDP type:           IP
APN:                m2m.tele2.com
IPv4 MTU:           1280
IPv4 address:       10.165.181.55
IPv6 address:       ::
IPv4 DNS address:   130.244.127.161, 130.244.127.169
IPv6 DNS address:   2a00:800:1000:3::1, 2a00:800:1000:4::1
RRC mode: Idle
RRC mode: Connected
Network registration status: not registered
PDN event: PDP context 0 network detach
RRC mode: Idle
[00:04:44.344,329] <wrn> lte_lc: Registration rejected, EMM cause: 7, Cell ID: 25533958, Tracking area: 52644, LTE mode: 7
mosh:~$ > at at+cfun=4
at at+cfun=4
Currently active system mode: None
OK
LTE cell changed: ID: -1, Tracking area: -1
mosh:~$ > at at+cfun=0
at at+cfun=0
OK
mosh:~$ > at at+cfun=1
at at+cfun=1
OK
PDN event: PDP context 0 activated
PDN event: PDP context 0, PDN type IPv4 only allowed
mosh:~$ > at AT%XSIM?
at AT%XSIM?H%XSIM: 1
OK
mosh:~$ > at AT%XSIM?H%XSIM: 1
at AT%XSIM?H%XSIM: 1
%XSIM: 1
OK
mosh:~$ >
mosh:~$ >
mosh:~$ > at AT%XMONITOR
at AT%XMONITOR
%XMONITOR: 5,"Orange F","Orange F","20801","CDA4",7,20,"01859E06",290,6400,31,28,"","11100000","11100000","01001001"
OK
mosh:~$ > at AT%XSIM=0
at AT%XSIM=0
ERROR
mosh:~$ > at AT%XSIM
at AT%XSIM
ERROR
mosh:~$ > at AT%XSIM=1
at AT%XSIM=1
OK
mosh:~$ > at AT+CFUN=1
at AT+CFUN=1
OK
mosh:~$ > at AT%XCONNSTAT=1
at AT%XCONNSTAT=1
OK
mosh:~$ > at AT%XCONNSTAT?
at AT%XCONNSTAT?
%XCONNSTAT: 0,0,0,0,0,0
OK
mosh:~$ > at AT+CMEE=1
at AT+CMEE=1
OK
mosh:~$ > at AT%XSIM=1
at AT%XSIM=1
OK
mosh:~$ > at AT+CEREG=5
at AT+CEREG=5
OK
mosh:~$ > at AT%MDMEV=1
at AT%MDMEV=1
OK
mosh:~$ > at AT%CESQ=1
at AT%CESQ=1
OK
mosh:~$ > at AT+CGSN=1
at AT+CGSN=1
+CGSN: "359404230274905"
OK
mosh:~$ > at AT+CGMM
at AT+CGMM
nRF9151-LACA
OK
mosh:~$ > at AT+CEMODE?
at AT+CEMODE?
+CEMODE: 2
OK
mosh:~$ > at AT+CMEE?
at AT+CMEE?
+CMEE: 1
OK
mosh:~$ > at AT+CNEC?
at AT+CNEC?H+CNEC: 16
OK
mosh:~$ > at AT+CGEREP?
at AT+CGEREP?
+CGEREP: 1,0
OK
mosh:~$ > at AT+CIND=1,1,1
at AT+CIND=1,1,1
OK
mosh:~$ > at AT+COPS=3,2
at AT+COPS=3,2
OK
mosh:~$ > at AT+CGDCONT?
at AT+CGDCONT?
+CGDCONT: 0,"IP","m2m.tele2.com","10.161.250.43",0,0
OK
mosh:~$ > at AT+CGACT?
at AT+CGACT?
+CGACT: 0,1
OK
mosh:~$ > at AT+CESQ
at AT+CESQ
+CESQ: 99,99,255,255,17,32
OK
mosh:~$ > at AT%XSIM?
at AT%XSIM?H%XSIM: 1
OK
mosh:~$ > at AT+CPIN?
at AT+CPIN?H+CPIN: READY
OK
mosh:~$ > at AT+CIMI
at AT+CIMI
240075823634698
OK
mosh:~$ > at AT+CNEC=24
at AT+CNEC=24
OK
mosh:~$ > at AT+CEER
at AT+CEER
+CEER: "ESM 50"
OK
mosh:~$ > at AT+CGEREP=1
at AT+CGEREP=1
OK
mosh:~$ > at AT%XPOFWARN=1,30
at AT%XPOFWARN=1,30
OK
mosh:~$ > at AT%XVBATLVL=1
at AT%XVBATLVL=1
OK
mosh:~$ > at AT+CGMI
at AT+CGMI
Nordic Semiconductor ASA
OK
mosh:~$ > at AT+CGMR
at AT+CGMR
mfw_nrf91x1_2.0.2
OK
mosh:~$ > at AT+CGSN
at AT+CGSN
359404230274905
OK
mosh:~$ > at AT%XMODEMUUID
at AT%XMODEMUUID
%XMODEMUUID: 320176d5-9f40-45fc-923b-2661ec18d547
OK
mosh:~$ > at AT%XDATAPRFL?
at AT%XDATAPRFL?
%XDATAPRFL: 2
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 5,5,"CDA4","01859E06",7,,,"11100000","11100000"
OK
mosh:~$ > at AT+CFUN?
at AT+CFUN?H+CFUN: 1
OK
mosh:~$ > at AT%CESQ=1
at AT%CESQ=1
OK
mosh:~$ > at AT+CSCON=1
at AT+CSCON=1
OK
mosh:~$ > at AT+CSCON?
at AT+CSCON?
+CSCON: 1,0
OK
mosh:~$ > at AT+CPAS
at AT+CPAS
+CPAS: 0
OK
mosh:~$ > at AT+CEDRXRDP
at AT+CEDRXRDP
+CEDRXRDP: 4,"","",""
OK
mosh:~$ > at AT%XTIME=1
at AT%XTIME=1
OK
mosh:~$ > at AT%CONEVAL
at AT%CONEVAL
%CONEVAL: 0,0,7,32,17,28,"01859E06","20801",290,6400,20,0,0,17,1,1,127
OK
mosh:~$ > at AT%XCBAND=?
at AT%XCBAND=?
%XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66,85)
OK
mosh:~$ at AT%XCBAND
> at AT%XCBAND
%XCBAND: 20
OK
mosh:~$ > at AT%HWVERSION
at AT%HWVERSION
%HWVERSION: nRF9151 LACA A0A
OK
mosh:~$ > at AT%XMODEMTRACE=1,2
at AT%XMODEMTRACE=1,2
OK
mosh:~$ > at AT%XSYSTEMMODE?
at AT%XSYSTEMMODE?%XSYSTEMMODE: 1,1,1,3
OK
mosh:~$ > at AT%XICCID
at AT%XICCID
%XICCID: 89462038075015721859
OK
mosh:~$ > at AT%XEMPR?
at AT%XEMPR?
%XEMPR:
OK
mosh:~$ > at AT+CGDCONT?
at AT+CGDCONT?
+CGDCONT: 0,"IP","m2m.tele2.com","10.161.250.43",0,0
OK
mosh:~$ > at AT+COPS?
at AT+COPS?+=AM2~",7
OK
mosh:~$ > at AT%XMONITOR
at AT%XMONITOR
%XMONITOR: 5,"Orange F","Orange F","20801","CDA4",7,20,"01859E06",290,6400,33,29,"","11100000","11100000","01001001"
OK
mosh:~$ > at AT+CPINR="SIM PIN"
at AT+CPINR="SIM PIN"
+CPINR: "SIM PIN",3
OK
mosh:~$ > at AT+CPINR="SIM PIN2"
at AT+CPINR="SIM PIN2"
+CPINR: "SIM PIN2",3
OK
mosh:~$ > at AT+CPINR="SIM PUK"
at AT+CPINR="SIM PUK"
+CPINR: "SIM PUK",10
OK
mosh:~$ > at AT+CPINR="SIM PUK2"
at AT+CPINR="SIM PUK2"
+CPINR: "SIM PUK2",10
OK
mosh:~$ > at AT%XSIM?
at AT%XSIM?H%XSIM: 1
OK
RRC mode: Connected
Currently active system mode: LTE-M
PDN event: PDP context 0 network detach
RRC mode: Idle
LTE cell changed: ID: 25533958, Tracking area: 52644
[00:08:51.386,901] <wrn> lte_lc: Registration rejected, EMM cause: 7, Cell ID: 25533958, Tracking area: 52644, LTE mode: 7
mosh:~$ > at+CFUN=0
at+CFUN=0
at+CFUN=0: command not found
mosh:~$ > at at+CFUN=0
at at+CFUN=0
Currently active system mode: None
OK
LTE cell changed: ID: -1, Tracking area: -1
mosh:~$ > at at+CFUN=1
at at+CFUN=1
OK
mosh:~$ > at at+reg?
at at+reg?
ERROR
mosh:~$ > at at+reg
at at+reg
ERROR
mosh:~$ > at at+creg?
at at+creg?ERROR
mosh:~$ > at at+creg
at at+creg
ERROR
mosh:~$ > at AT+CGDCONT?
at AT+CGDCONT?
+CGDCONT: 0,"","","",0,0
OK
mosh:~$ > at AT%XMONITOR
at AT%XMONITOR
%XMONITOR: 0
OK
mosh:~$ > at AT%XMONITOR
at AT%XMONITOR
%XMONITOR: 0
OK
mosh:~$ > at AT+CGDCONT?
at AT+CGDCONT?
+CGDCONT: 0,"","","",0,0
OK
mosh:~$ > at at+CFUN=0
at at+CFUN=0
OK
mosh:~$ > at at+CFUN=1
at at+CFUN=1
OK
mosh:~$ > at at+cfun=4
at at+cfun=4
OK
mosh:~$ > at at+cfun=0
at at+cfun=0
OK
mosh:~$ > at at+cfun=1
at at+cfun=1
OK
mosh:~$ > at at+cfun=4
at at+cfun=4
OK
mosh:~$ > at at+cfun=0
at at+cfun=0
OK
mosh:~$ > at at+cgatt=0
at at+cgatt=0
OK
mosh:~$ > at at+cfun=1
at at+cfun=1
OK
mosh:~$ > at at+creg=2
at at+creg=2
ERROR
mosh:~$ > at at+cereg=2
at at+cereg=2
OK
mosh:~$ > at at+csq
at at+csq
+CSQ: 99,99
OK
mosh:~$ > at at+csq
at at+csq
+CSQ: 99,99
OK
mosh:~$ > at at+csq
at at+csq
+CSQ: 99,99
OK
mosh:~$ > at at+cops
at at+cops
ERROR
mosh:~$ > at at+cops?
at at+cops?H+COPS: 0
OK
mosh:~$ > at at+cgdcont?
at at+cgdcont?
OK
mosh:~$ > at at+CFUN=0
at at+CFUN=0
OK
mosh:~$ > at at+CGATT=0
at at+CGATT=0
OK
mosh:~$ > at at+COPS=2
at at+COPS=2
ERROR
mosh:~$ > at at+CFUN=1
at at+CFUN=1
OK
mosh:~$ > at at+COPS=0
at at+COPS=0
OK
mosh:~$ > at AT+CGDCONT=1,\"IP",\"m2m.tele2.com\""
at AT+CGDCONT=1,\"IP",\"m2m.tele2.com\""
OK
mosh:~$ > at at+cereg=2
at at+cereg=2
OK
mosh:~$ > at+cereg?
at+cereg?
at+cereg?: command not found
mosh:~$ > at at+cereg?
at at+cereg?
+CEREG: 2,0
OK
mosh:~$ > at+cfun=0
at+cfun=0
at+cfun=0: command not found
mosh:~$ > at at+cfun=0
at at+cfun=0
OK
mosh:~$ > at at+cops=2
at at+cops=2
ERROR
mosh:~$ > at at+cgatt=0
at at+cgatt=0
OK
mosh:~$ > at AT+CGDCONT=1,"IP","m2m.tele2.com"
at AT+CGDCONT=1,"IP","m2m.tele2.com"
OK
mosh:~$ > at at+cfun=1
at at+cfun=1
OK
mosh:~$ > at at+cops=0
at at+cops=0
OK
mosh:~$ > at at+cereg=2
at at+cereg=2
OK
mosh:~$ > at at+cereg?
at at+cereg?
+CEREG: 2,0
OK
mosh:~$ > at AT%XSYSTEMMODE?
at AT%XSYSTEMMODE?
%XSYSTEMMODE: 1,1,1,3
OK
mosh:~$ > at AT%XSYSTEMMODE=1,0,0,0
at AT%XSYSTEMMODE=1,0,0,0
ERROR
mosh:~$ > at at+cfun=0
at at+cfun=0
OK
mosh:~$ > at AT%XSYSTEMMODE=1,0,0,0
at AT%XSYSTEMMODE=1,0,0,0
OK
mosh:~$ > at at+cfun=20
at at+cfun=20
OK
mosh:~$ > at AT%XSYSTEMMODE?
at AT%XSYSTEMMODE?
%XSYSTEMMODE: 1,0,0,0
OK
mosh:~$ > at at+cgatt=0
at at+cgatt=0
OK
mosh:~$ > at AT+CGDCONT=1,"IP","m2m.tele2.com"
at AT+CGDCONT=1,"IP","m2m.tele2.com"
OK
mosh:~$ > at AT+COPS=2
at AT+COPS=2
ERROR
mosh:~$ > at AT+CFUN=1
at AT+CFUN=1
OK
mosh:~$ > at AT+COPS=0
at AT+COPS=0
OK
mosh:~$ > at AT+CEREG=2
at AT+CEREG=2
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG=2,1
at AT+CEREG=2,1
OK
mosh:~$ > at AT+CEREG=2,2
at AT+CEREG=2,2
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT+CFUN=0
at AT+CFUN=0
OK
mosh:~$ > at AT+CGATT=0
at AT+CGATT=0
OK
mosh:~$ > at AT+CGDCONT=1,"IP","m2m.tele2.com"
at AT+CGDCONT=1,"IP","m2m.tele2.com"
OK
mosh:~$ > at AT%XSYSTEMMODE=1,0,0,0
at AT%XSYSTEMMODE=1,0,0,0
OK
mosh:~$ > at AT+CFUN=15
at AT+CFUN=15
ERROR
mosh:~$ > AT+CFUN=0
AT+CFUN=0
AT+CFUN=0: command not found
mosh:~$ > at AT+CFUN=4
at AT+CFUN=4
OK
mosh:~$ > at AT+CFUN=1
at AT+CFUN=1
OK
mosh:~$ > AT+COPS=0
AT+COPS=0
AT+COPS=0: command not found
mosh:~$ > at AT+COPS=0
at AT+COPS=0
OK
mosh:~$ > at AT+CEREG=2
at AT+CEREG=2
OK
mosh:~$ > at AT+CEREG?
at AT+CEREG?
+CEREG: 2,0
OK
mosh:~$ > at AT%XMONITOR
at AT%XMONITOR
%XMONITOR: 0
OK
mosh:~$ > at AT+COPS?
at AT+COPS?+COPS: 0
OK
mosh:~$ at AT+CGDCONT?
> at AT+CGDCONT?
+CGDCONT: 1,"IP","m2m.tele2.com","",0,0
OK
mosh:~$ > at AT+CPIN?
at AT+CPIN?+CPIN: READY
OK
mosh:~$ > at AT%SCANMODE=1
at AT%SCANMODE=1
ERROR
mosh:~$ > at AT%SCANCELL
at AT%SCANCELL
ERROR
mosh:~$