nRF9160 DK Asset Tracker not reliably finding network

[ERIK]

I am having trouble getting the nRF9160 DK to find a network running the Asset Tracker than came in the device.  It appears to reset after 15 seconds of LED 3 blinking.  I can connect the LTE Link Monitor and watch it do that.  Secure Boot boots to Zephyr and then about 15 seconds approx later it says it failed (nrf_cloud_connect failed: 60) and starts all over again.  Really difficult and unreliable to get to the state of LED 3 and LED 4 both blinking.  Sometimes just stops with LED 3 lit solid.

I have had it connected a number of times, but not reliably. The SIM is registered.  This is making it difficult to get the things linked to my nRF Cloud account when I am having trouble even getting to the pattern entry portion of setting this up.

Is there an issue with the asset tracker that came in the device such that it won't connect?  Something else I might have going on?  I have not loaded anything different into the DK than what it came with.

Thanks,

Erik

[Øyvind]

Hello Erik,

Can you please verify that you have the latest modem FW? The latest version can be found here. 

You can check the modem FW using the AT Command  AT+CGMR. AT Commands are available using the AT Client example, found here, and running the LTE Link Monitor will run the command for you (Follow this video).

Best regards,

Oeyvind

[ERIK]

Any additional thoughts on this?

[Øyvind]

Hi again Erik, 

Can you please load the AT Client project and copy/paste the output in log and terminal here?

Thanks!
Oeyvind

[ERIK]

Thanks, Oetvynd.  

I can get the terminal capture but not sure how to get the log (was just trying to figure out the debug log from the code last night).  Instructions would be very helpful.

FYI I noticed in the code in main.c that error_handler() won't give the LED flash patterns described in the documentation for asset_tracker unless CONFIG_DEBUG is defined.  If I definitely that I get different results.  Then it gets the nrf_cloud_connect_failed: 60 followed by "Error of type ERROR_BSD_RECOVERABLE: 3".  However, the error handler then goes into an infinite loop flashing the LEDs and, supposedly, never gets a chance to recover.

If CONFIG_DEBUG is not defined, the error handler calls sys_reboot(SYS_REBOOT_COLD), according to the code I'm looking at, which fits what I'm seeing with the reset.

So, not sure if CONFIG_DEBUG is intended to be defined in the sample, but it looks like that may be only part of the problem if so, with the cloud connect failed 60 and the BSD recoverable 3.

I won't be able to send the log until late today.  Thank you for your help.

[ERIK]

Oh, the LTE link monitor output is captured above.  That is with CONFIG_DEBUG undefined.

[Øyvind]

Please do not edit the example code before we know what the reason of failure is. I have tested the examples here, and I know they work "out of the box". Make sure you are using an unmodified example from the SDK.

Can you please load the AT Client project and copy/paste the output in log and terminal here? When you have loaded the AT Client project, following the given tutorial instructions, please take a screenshot of the LTE Link Monitor window, and capture output as above. It is important that you do this so we can compare output and talk to our developers.

Thanks again,
Oeyvind

[ERIK]

I have undone any modifications to the code.

I am pasting output from the LTE Link Monitor below, with a screenshot.  I don't know if there is other logging information that would be helpful to you.  Please provide further instructions if so.

I hope this is what you need.

The LTE Link Monitor output repeats as long as I let the asset_tracker application run.  Here are a couple of iterations:

***** Booting Zephyr OS v1.13.99-ncs2 *****

Secure Boot: configure flash

Secure Boot: SPU: set region 0 as Secure

Secure Boot: SPU: set region 1 as Secure

Secure Boot: SPU: set region 2 as Secure

Secure Boot: SPU: set region 3 as Secure

Secure Boot: SPU: set region 4 as Secure

Secure Boot: SPU: set region 5 as Secure

Secure Boot: SPU: set region 6 as Secure

Secure Boot: SPU: set region 7 as Secure

Secure Boot: SPU: set Flash region 8 as Non-Secure

Secure Boot: SPU: set Flash region 9 as Non-Secure

Secure Boot: SPU: set Flash region 10 as Non-Secure

Secure Boot: SPU: set Flash region 11 as Non-Secure

Secure Boot: SPU: set Flash region 12 as Non-Secure

Secure Boot: SPU: set Flash region 13 as Non-Secure

Secure Boot: SPU: set Flash region 14 as Non-Secure

Secure Boot: SPU: set Flash region 15 as Non-Secure

Secure Boot: SPU: set Flash region 16 as Non-Secure

Secure Boot: SPU: set Flash region 17 as Non-Secure

Secure Boot: SPU: set Flash region 18 as Non-Secure

Secure Boot: SPU: set Flash region 19 as Non-Secure

Secure Boot: SPU: set Flash region 20 as Non-Secure

Secure Boot: SPU: set Flash region 21 as Non-Secure

Secure Boot: SPU: set Flash region 22 as Non-Secure

Secure Boot: SPU: set Flash region 23 as Non-Secure

Secure Boot: SPU: set Flash region 24 as Non-Secure

Secure Boot: SPU: set Flash region 25 as Non-Secure

Secure Boot: SPU: set Flash region 26 as Non-Secure

Secure Boot: SPU: set Flash region 27 as Non-Secure

Secure Boot: SPU: set Flash region 28 as Non-Secure

Secure Boot: SPU: set Flash region 29 as Non-Secure

Secure Boot: SPU: set Flash region 30 as Non-Secure

Secure Boot: SPU: set Flash region 31 as Non-Secure

Secure Boot: configure SRAM

Secure Boot: SPU: set SRAM region 0 as Secure

Secure Boot: SPU: set SRAM region 1 as Secure

Secure Boot: SPU: set SRAM region 2 as Secure

Secure Boot: SPU: set SRAM region 3 as Secure

Secure Boot: SPU: set SRAM region 4 as Secure

Secure Boot: SPU: set SRAM region 5 as Secure

Secure Boot: SPU: set SRAM region 6 as Secure

Secure Boot: SPU: set SRAM region 7 as Secure

Secure Boot: SPU: set SRAM region 8 as Non-Secure

Secure Boot: SPU: set SRAM region 9 as Non-Secure

Secure Boot: SPU: set SRAM region 10 as Non-Secure

Secure Boot: SPU: set SRAM region 11 as Non-Secure

Secure Boot: SPU: set SRAM region 12 as Non-Secure

Secure Boot: SPU: set SRAM region 13 as Non-Secure

Secure Boot: SPU: set SRAM region 14 as Non-Secure

Secure Boot: SPU: set SRAM region 15 as Non-Secure

Secure Boot: SPU: set SRAM region 16 as Non-Secure

Secure Boot: SPU: set SRAM region 17 as Non-Secure

Secure Boot: SPU: set SRAM region 18 as Non-Secure

Secure Boot: SPU: set SRAM region 19 as Non-Secure

Secure Boot: SPU: set SRAM region 20 as Non-Secure

Secure Boot: SPU: set SRAM region 21 as Non-Secure

Secure Boot: SPU: set SRAM region 22 as Non-Secure

Secure Boot: SPU: set SRAM region 23 as Non-Secure

Secure Boot: SPU: set SRAM region 24 as Non-Secure

Secure Boot: SPU: set SRAM region 25 as Non-Secure

Secure Boot: SPU: set SRAM region 26 as Non-Secure

Secure Boot: SPU: set SRAM region 27 as Non-Secure

Secure Boot: SPU: set SRAM region 28 as Non-Secure

Secure Boot: SPU: set SRAM region 29 as Non-Secure

Secure Boot: SPU: set SRAM region 30 as Non-Secure

Secure Boot: SPU: set SRAM region 31 as Non-Secure

Secure Boot: configure peripherals

Secure Boot: MSP_NS 2002ab70

Secure Boot: prepare to jump to Non-Secure image

***** Booting Zephyr OS v1.13.99-ncs2 *****

Application started

LTE LC config ...

nrf_cloud_connect failed: 60

***** Booting Zephyr OS v1.13.99-ncs2 *****

Secure Boot: configure flash

Secure Boot: SPU: set region 0 as Secure

Secure Boot: SPU: set region 1 as Secure

Secure Boot: SPU: set region 2 as Secure

Secure Boot: SPU: set region 3 as Secure

Secure Boot: SPU: set region 4 as Secure

Secure Boot: SPU: set region 5 as Secure

Secure Boot: SPU: set region 6 as Secure

Secure Boot: SPU: set region 7 as Secure

Secure Boot: SPU: set Flash region 8 as Non-Secure

Secure Boot: SPU: set Flash region 9 as Non-Secure

Secure Boot: SPU: set Flash region 10 as Non-Secure

Secure Boot: SPU: set Flash region 11 as Non-Secure

Secure Boot: SPU: set Flash region 12 as Non-Secure

Secure Boot: SPU: set Flash region 13 as Non-Secure

Secure Boot: SPU: set Flash region 14 as Non-Secure

Secure Boot: SPU: set Flash region 15 as Non-Secure

Secure Boot: SPU: set Flash region 16 as Non-Secure

Secure Boot: SPU: set Flash region 17 as Non-Secure

Secure Boot: SPU: set Flash region 18 as Non-Secure

Secure Boot: SPU: set Flash region 19 as Non-Secure

Secure Boot: SPU: set Flash region 20 as Non-Secure

Secure Boot: SPU: set Flash region 21 as Non-Secure

Secure Boot: SPU: set Flash region 22 as Non-Secure

Secure Boot: SPU: set Flash region 23 as Non-Secure

Secure Boot: SPU: set Flash region 24 as Non-Secure

Secure Boot: SPU: set Flash region 25 as Non-Secure

Secure Boot: SPU: set Flash region 26 as Non-Secure

Secure Boot: SPU: set Flash region 27 as Non-Secure

Secure Boot: SPU: set Flash region 28 as Non-Secure

Secure Boot: SPU: set Flash region 29 as Non-Secure

Secure Boot: SPU: set Flash region 30 as Non-Secure

Secure Boot: SPU: set Flash region 31 as Non-Secure

Secure Boot: configure SRAM

Secure Boot: SPU: set SRAM region 0 as Secure

Secure Boot: SPU: set SRAM region 1 as Secure

Secure Boot: SPU: set SRAM region 2 as Secure

Secure Boot: SPU: set SRAM region 3 as Secure

Secure Boot: SPU: set SRAM region 4 as Secure

Secure Boot: SPU: set SRAM region 5 as Secure

Secure Boot: SPU: set SRAM region 6 as Secure

Secure Boot: SPU: set SRAM region 7 as Secure

Secure Boot: SPU: set SRAM region 8 as Non-Secure

Secure Boot: SPU: set SRAM region 9 as Non-Secure

Secure Boot: SPU: set SRAM region 10 as Non-Secure

Secure Boot: SPU: set SRAM region 11 as Non-Secure

Secure Boot: SPU: set SRAM region 12 as Non-Secure

Secure Boot: SPU: set SRAM region 13 as Non-Secure

Secure Boot: SPU: set SRAM region 14 as Non-Secure

Secure Boot: SPU: set SRAM region 15 as Non-Secure

Secure Boot: SPU: set SRAM region 16 as Non-Secure

Secure Boot: SPU: set SRAM region 17 as Non-Secure

Secure Boot: SPU: set SRAM region 18 as Non-Secure

Secure Boot: SPU: set SRAM region 19 as Non-Secure

Secure Boot: SPU: set SRAM region 20 as Non-Secure

Secure Boot: SPU: set SRAM region 21 as Non-Secure

Secure Boot: SPU: set SRAM region 22 as Non-Secure

Secure Boot: SPU: set SRAM region 23 as Non-Secure

Secure Boot: SPU: set SRAM region 24 as Non-Secure

Secure Boot: SPU: set SRAM region 25 as Non-Secure

Secure Boot: SPU: set SRAM region 26 as Non-Secure

Secure Boot: SPU: set SRAM region 27 as Non-Secure

Secure Boot: SPU: set SRAM region 28 as Non-Secure

Secure Boot: SPU: set SRAM region 29 as Non-Secure

Secure Boot: SPU: set SRAM region 30 as Non-Secure

Secure Boot: SPU: set SRAM region 31 as Non-Secure

Secure Boot: configure peripherals

Secure Boot: MSP_NS 2002ab70

Secure Boot: prepare to jump to Non-Secure image

***** Booting Zephyr OS v1.13.99-ncs2 *****

Application started

LTE LC config ...

nrf_cloud_connect failed: 60

[Øyvind]

I'm sorry, but this is still the output of the asset_tracker example code. I need the output of the AT_Client example code, which gives more information about the board. Please program using this file: at_client.hex

-Oeyvind

[ERIK]

Sorry, misread your request.

Here is with AT client.

Note that below the AT client first seemed to stop responding with the LTE indicator on LTE monitor flashing.  But I reset the DK board and then it worked.  You can see where that happened in the log below where it shows AT+CFUN? sent multiple times in a row right before booting Zephyr.

AT+CFUN?
***** Booting Zephyr OS v1.13.99-ncs2 *****
Secure Boot: configure flash
Secure Boot: SPU: set region 0 as Secure
Secure Boot: SPU: set region 1 as Secure
Secure Boot: SPU: set region 2 as Secure
Secure Boot: SPU: set region 3 as Secure
Secure Boot: SPU: set region 4 as Secure
Secure Boot: SPU: set region 5 as Secure
Secure Boot: SPU: set region 6 as Secure
Secure Boot: SPU: set region 7 as Secure
Secure Boot: SPU: set Flash region 8 as Non-Secure
Secure Boot: SPU: set Flash region 9 as Non-Secure
Secure Boot: SPU: set Flash region 10 as Non-Secure
Secure Boot: SPU: set Flash region 11 as Non-Secure
Secure Boot: SPU: set Flash region 12 as Non-Secure
Secure Boot: SPU: set Flash region 13 as Non-Secure
Secure Boot: SPU: set Flash region 14 as Non-Secure
Secure Boot: SPU: set Flash region 15 as Non-Secure
Secure Boot: SPU: set Flash region 16 as Non-Secure
Secure Boot: SPU: set Flash region 17 as Non-Secure
Secure Boot: SPU: set Flash region 18 as Non-Secure
Secure Boot: SPU: set Flash region 19 as Non-Secure
Secure Boot: SPU: set Flash region 20 as Non-Secure
Secure Boot: SPU: set Flash region 21 as Non-Secure
Secure Boot: SPU: set Flash region 22 as Non-Secure
Secure Boot: SPU: set Flash region 23 as Non-Secure
Secure Boot: SPU: set Flash region 24 as Non-Secure
Secure Boot: SPU: set Flash region 25 as Non-Secure Secure Boot: SPU: set Flash region 26 as Non-Secure
Secure Boot: SPU: set Flash region 27 as Non-Secure
Secure Boot: SPU: set Flash region 28 as Non-Secure
Secure Boot: SPU: set Flash region 29 as Non-Secure
Secure Boot: SPU: set Flash region 30 as Non-Secure
Secure Boot: SPU: set Flash region 31 as Non-Secure
Secure Boot: configure SRAM
Secure Boot: SPU: set SRAM region 0 as Secure
Secure Boot: SPU: set SRAM region 1 as Secure
Secure Boot: SPU: set SRAM region 2 as Secure
Secure Boot: SPU: set SRAM region 3 as Secure
Secure Boot: SPU: set SRAM region 4 as Secure
Secure Boot: SPU: set SRAM region 5 as Secure
Secure Boot: SPU: set SRAM region 6 as Secure
Secure Boot: SPU: set SRAM region 7 as Secure
Secure Boot: SPU: set SRAM region 8 as Non-Secure
Secure Boot: SPU: set SRAM region 9 as Non-Secure
Secure Boot: SPU: set SRAM region 10 as Non-Secure
Secure Boot: SPU: set SRAM region 11 as Non-Secure
Secure Boot: SPU: set SRAM region 12 as Non-Secure
Secure Boot: SPU: set SRAM region 13 as Non-Secure
Secure Boot: SPU: set SRAM region 14 as Non-Secure
Secure Boot: SPU: set SRAM region 15 as Non-Secure
Secure Boot: SPU: set SRAM region 16 as Non-Secure
Secure Boot: SPU: set SRAM region 17 as Non-Secure
Secure Boot: SPU: set SRAM region 18 as Non-Secure
Secure Boot: SPU: set SRAM region 19 as Non-Secure
Secure Boot: SPU: set SRAM region 20 as Non-Secure
Secure Boot: SPU: set SRAM region 21 as Non-Secure
Secure Boot: SPU: set SRAM region 22 as Non-Secure
Secure Boot: SPU: set SRAM region 23 as Non-Secure
Secure Boot: SPU: set SRAM region 24 as Non-Secure
Secure Boot: SPU: set SRAM region 25 as Non-Secure
Secure Boot: SPU: set SRAM region 26 as Non-Secure
Secure Boot: SPU: set SRAM region 27 as Non-Secure
Secure Boot: SPU: set SRAM region 28 as Non-Secure
Secure Boot: SPU: set SRAM region 29 as Non-Secure
Secure Boot: SPU: set SRAM region 30 as Non-Secure
Secure Boot: SPU: set SRAM region 31 as Non-Secure
Secure Boot: configure peripherals
Secure Boot: MSP_NS 200265f0
Secure Boot: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.13.99-ncs2 ***** The AT host sample started
AT+CFUN?
+CFUN: 4
OK
AT+CFUN=1
OK
AT+CFUN?
+CFUN: 1 OK
AT+CGSN=1
+CGSN: "352656100049587"
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9120
OK
AT+CGMR
mfw-m1_nrf9160_0.6.8-30.alpha
OK AT+CEMODE?
+CEMODE: 2
OK
AT%XCBAND=?
%XCBAND: (3,4,13,20)
OK
AT+CMEE?
+CMEE: 0
OK
AT+CMEE=1
OK
AT+CNEC?
+CNEC: 0
OK
AT+CNEC=24
OK
AT+CGEREP?
+CGEREP: 0,0
OK
AT+CGDCONT?
OK
AT+CGACT?
OK
AT+CGEREP=1
OK
AT+CIND=1,1,1
OK AT+CEREG=2
OK
AT+CEREG?
+CEREG: 2,2,"BF3F","02EA5B01",7
OK
AT%CESQ=1
OK AT+CESQ
+CESQ: 99,99,255,255,255,38
OK
AT%XSIM=1
OK
AT%XSIM?
%XSIM: 1
OK
AT+CPIN?
+CPIN: READY
OK
AT+CPINR="SIM PIN"
+CPINR: "SIM PIN",3
OK
AT+CIMI
204080813513522
OK
+CGEV: ME PDN ACT 0,0
AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.173",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
+CGEV: ME PDN DEACT 0
AT+CGDCONT?
+CNEC_EMM: 10
+CEREG: 2,"BF3F","02EA5B01",7
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
+CGEV: ME PDN ACT 0,0
AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.175",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
AT+CFUN?
AT+CFUN?
AT+CFUN?
AT+CFUN?
***** Booting Zephyr OS v1.13.99-ncs2 *****
Secure Boot: configure flash
Secure Boot: SPU: set region 0 as Secure
Secure Boot: SPU: set region 1 as Secure
Secure Boot: SPU: set region 2 as Secure
Secure Boot: SPU: set region 3 as Secure
Secure Boot: SPU: set region 4 as Secure
Secure Boot: SPU: set region 5 as Secure
Secure Boot: SPU: set region 6 as Secure
Secure Boot: SPU: set region 7 as Secure
Secure Boot: SPU: set Flash region 8 as Non-Secure
Secure Boot: SPU: set Flash region 9 as Non-Secure
Secure Boot: SPU: set Flash region 10 as Non-Secure
Secure Boot: SPU: set Flash region 11 as Non-Secure
Secure Boot: SPU: set Flash region 12 as Non-Secure
Secure Boot: SPU: set Flash region 13 as Non-Secure
Secure Boot: SPU: set Flash region 14 as Non-Secure
Secure Boot: SPU: set Flash region 15 as Non-Secure
Secure Boot: SPU: set Flash region 16 as Non-Secure
Secure Boot: SPU: set Flash region 17 as Non-Secure
Secure Boot: SPU: set Flash region 18 as Non-Secure
Secure Boot: SPU: set Flash region 19 as Non-Secure
Secure Boot: SPU: set Flash region 20 as Non-Secure
Secure Boot: SPU: set Flash region 21 as Non-Secure
Secure Boot: SPU: set Flash region 22 as Non-Secure
Secure Boot: SPU: set Flash region 23 as Non-Secure
Secure Boot: SPU: set Flash region 24 as Non-Secure
Secure Boot: SPU: set Flash region 25 as Non-Secure
Secure Boot: SPU: set Flash region 26 as Non-Secure
Secure Boot: SPU: set Flash region 27 as Non-Secure
Secure Boot: SPU: set Flash region 28 as Non-Secure
Secure Boot: SPU: set Flash region 29 as Non-Secure
Secure Boot: SPU: set Flash region 30 as Non-Secure
Secure Boot: SPU: set Flash region 31 as Non-Secure
Secure Boot: configure SRAM
Secure Boot: SPU: set SRAM region 0 as Secure
Secure Boot: SPU: set SRAM region 1 as Secure
Secure Boot: SPU: set SRAM region 2 as Secure
Secure Boot: SPU: set SRAM region 3 as Secure
Secure Boot: SPU: set SRAM region 4 as Secure
Secure Boot: SPU: set SRAM region 5 as Secure
Secure Boot: SPU: set SRAM region 6 as Secure
Secure Boot: SPU: set SRAM region 7 as Secure
Secure Boot: SPU: set SRAM region 8 as Non-Secure
Secure Boot: SPU: set SRAM region 9 as Non-Secure
Secure Boot: SPU: set SRAM region 10 as Non-Secure
Secure Boot: SPU: set SRAM region 11 as Non-Secure
Secure Boot: SPU: set SRAM region 12 as Non-Secure
Secure Boot: SPU: set SRAM region 13 as Non-Secure
Secure Boot: SPU: set SRAM region 14 as Non-Secure
Secure Boot: SPU: set SRAM region 15 as Non-Secure
Secure Boot: SPU: set SRAM region 16 as Non-Secure
Secure Boot: SPU: set SRAM region 17 as Non-Secure
Secure Boot: SPU: set SRAM region 18 as Non-Secure
Secure Boot: SPU: set SRAM region 19 as Non-Secure
Secure Boot: SPU: set SRAM region 20 as Non-Secure
Secure Boot: SPU: set SRAM region 21 as Non-Secure
Secure Boot: SPU: set SRAM region 22 as Non-Secure
Secure Boot: SPU: set SRAM region 23 as Non-Secure
Secure Boot: SPU: set SRAM region 24 as Non-Secure
Secure Boot: SPU: set SRAM region 25 as Non-Secure
Secure Boot: SPU: set SRAM region 26 as Non-Secure
Secure Boot: SPU: set SRAM region 27 as Non-Secure
Secure Boot: SPU: set SRAM region 28 as Non-Secure
Secure Boot: SPU: set SRAM region 29 as Non-Secure
Secure Boot: SPU: set SRAM region 30 as Non-Secure
Secure Boot: SPU: set SRAM region 31 as Non-Secure
Secure Boot: configure peripherals
Secure Boot: MSP_NS 200265f0
Secure Boot: prepare to jump to Non-Secure image
***** Booting Zephyr OS v1.13.99-ncs2 *****
The AT host sample started
AT+CFUN?
+CFUN: 4
OK
AT+CFUN=1
OK
AT+CFUN?
+CFUN: 1
OK
AT+CGSN=1
+CGSN: "352656100049587"
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9120
OK
AT+CGMR
mfw-m1_nrf9160_0.6.8-30.alpha
OK
AT+CEMODE?
+CEMODE: 2
OK
AT%XCBAND=?
%XCBAND: (3,4,13,20)
OK
AT+CMEE?
+CMEE: 0
OK
AT+CMEE=1
OK
AT+CNEC?
+CNEC: 0
OK
AT+CNEC=24
OK
AT+CGEREP?
+CGEREP: 0,0
OK
AT+CGDCONT?
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.180",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
AT+CGEREP=1
OK
AT+CIND=1,1,1
OK
AT+CEREG=2
OK AT+CEREG?
+CEREG: 2,5,"BF3F","02EA5B01",7
OK
AT+COPS=3,2
OK
AT+COPS?
+COPS: 0,2,"311480",7
OK
AT%XCBAND
%XCBAND: 13
OK
AT+CGDCONT?
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.180",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
AT%CESQ=1
OK
AT+CESQ
+CESQ: 99,99,255,255,255,38
OK
AT%XSIM=1
OK AT%XSIM?
%XSIM: 1
OK
AT+CPIN?
+CPIN: READY
OK
AT+CPINR="SIM PIN"
+CPINR: "SIM PIN",3
OK
AT+CIMI
204080813513522
OK
+CGEV: ME PDN DEACT 0
+CNEC_EMM: 10
+CEREG: 2,"BF3F","02EA5B01",7
AT+CGDCONT?
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
+CGEV: ME PDN ACT 0,0 AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.183",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
+CGEV: ME PDN DEACT 0
AT+CGDCONT?
+CNEC_EMM: 10
+CEREG: 2,"BF3F","02EA5B01",7
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
AT+CFUN?
+CFUN: 1
OK
AT+CGSN=1
+CGSN: "352656100049587"
OK
AT+CGMI
Nordic Semiconductor ASA
OK
AT+CGMM
nRF9120
OK
AT+CGMR
mfw-m1_nrf9160_0.6.8-30.alpha
OK
AT+CEMODE?
+CEMODE: 2
OK
AT%XCBAND=?
%XCBAND: (3,4,13,20)
OK
AT+CMEE?
+CMEE: 1
OK
AT+CNEC?
+CNEC: 24
OK
AT+CGEREP?
+CGEREP: 1,0
OK
AT+CIND=1,1,1
OK
AT+CEREG=2
OK
AT+CEREG?
+CEREG: 2,2,"BF3F","02EA5B01",7
OK
AT%CESQ=1
OK
AT+CESQ
+CESQ: 99,99,255,255,255,38
OK
AT%XSIM=1
OK
AT%XSIM?
%XSIM: 1
OK
AT+CPIN?
+CPIN: READY
OK
AT+CPINR="SIM PIN"
+CPINR: "SIM PIN",3
OK
AT+CIMI
204080813513522
OK
+CGEV: ME PDN ACT 0,0
AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.185",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
+CGEV: ME PDN DEACT 0
AT+CGDCONT?
+CNEC_EMM: 10
+CEREG: 2,"BF3F","02EA5B01",7
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
AT+CGDCONT?
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.187",0,0
OK
AT+COPS=3,2
OK
AT+CGACT?
+CGACT: 0,1
OK
AT+COPS?
+COPS: 0,2,"311480",7
OK
AT%XCBAND
%XCBAND: 13
OK
AT+CGDCONT?
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.187",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
+CGEV: ME PDN DEACT 0
+CNEC_EMM: 10 AT+CGDCONT?
+CEREG: 2,"BF3F","02EA5B01",7
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
%CESQ: 43,2
%CESQ: 37,1
+CGEV: ME PDN ACT 0,0
AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.190",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
+CGEV: ME PDN DEACT 0
AT+CGDCONT?
+CNEC_EMM: 10
+CEREG: 2,"BF3F","02EA5B01",7
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
%CESQ: 42,2
+CGEV: ME PDN ACT 0,0
AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.192",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
%CESQ: 37,1
%CESQ: 42,2
+CGEV: ME PDN DEACT 0
+CNEC_EMM: 10 AT+CGDCONT?
+CEREG: 2,"BF3F","02EA5B01",7
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
+CGEV: ME PDN ACT 0,0 AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.197",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK
%CESQ: 37,1
+CGEV: ME PDN DEACT 0
AT+CGDCONT?
+CNEC_EMM: 10
+CEREG: 2,"BF3F","02EA5B01",7
+CIND: "service",0
+CIND: "roam",0
+CGEV: NW DETACH
OK
AT+CGACT?
OK
%CESQ: 42,2
+CGEV: ME PDN ACT 0,0
AT+CGDCONT?
+CNEC_ESM: 50,0
+CEREG: 5,"BF3F","02EA5B01",7
+CIND: "service",1
+CIND: "roam",1
%CESQ: 37,1
+CGDCONT: 0,"IP","ibasis.iot","10.160.214.199",0,0
OK
AT+CGACT?
+CGACT: 0,1
OK

[Øyvind]

Thank you, Erik! This is exactly what I needed. I will have a look at the output with a colleague. 

Can you please try the solution given by Bjorn in the related support task: https://devzone.nordicsemi.com/support-private/support/222766
Let me know if that helped with anything, if not we will continue with at_client output.

Thanks!
-Oeyvind

[ERIK]

Tried Bjorn's suggestion, using the .hex files he attached.  Same results.  I posted the LTE Link Monitor terminal text in that thread.

Could there be some HW quirk with this nRF9160 DK board or with the SIM card, where I'd be better off trying another dev kit instead of continuing with this back and forth?  Maybe you could work with a vendor like DigiKey and have them ship another to me?

Thanks,

Erik

[Øyvind]

ERIK said:

I posted the LTE Link Monitor terminal text in that thread

 The output tells us that the modem is working as it should, as the board is receiving an IP address. I presume this was before Bjorn's suggestion. We need to figure out one last thing before shipping a new board, please see my answer in case #222768. There might be a problem with the board's certificates. 

-Oeyvind