Getting Started Issues with the nRF9160, not connecting to LTE, Failed example builds

[AaronS]

Hey anyone,

Going through the 'getting started' process for the nRF 9160 DK I'm having some issues. 

I've followed the steps to install nRF connect etc. suggested in the nordic documentation as well as followed along in the unboxing instructional video provided by nordic (https://www.youtube.com/watch?v=rMvW3HXLErk).

However when I try to test the 'asset tracker' application to verify the LTE/GPS functionality it doesn't seem to work and I'm running into the following issue:

 - The reset button appears to have no impact when it is pressed

 - LED 3 and LED 4 never light up to indicate any action regarding the LTE connection process

 - I'm thus unable to add my device in the nRF cloud solution

I've also tried to build and run an example program in the segger embedded studio IDE (I've updated the modem firmware to the latest using the programmer tool and I'm using nrf connect sdk version 1.4.0, should I be using a newer one?) and even the example programs fail, getting the following terminal output:

Im extremely new to nordic devices and the nRF SDK etc. so any help is greatly appreciated!

[Marte Myrvold]

Hi,

You should be fine with using v1.4.0. The latest official release right now is v1.4.2, and if you want to, you can check out the release notes for v1.4.1 and v1.4.2 here and here to see the changes between the releases. You can also see a list of known issues in v1.4.0 here.

How did you install NCS? Did you do it manually, or with either the Toolchain Manager or Getting Started Assistant in nRF Connect for Desktop? Which example did you try to build?

Could you please download the LTE Link Monitor application in nRF Connect for Desktop and open your nRF9160 DK there? It should print the log from the device, as well as show you the status of the modem and LTE connection in the upper right corner.

Best regards,

Marte

[AaronS]

I installed it via the toolchain manager (idk if it matters but my current OS is windows 10). Also I don't remember why it stuck out to me when I was installing everything but I believe there was a popup for the segger J-link installation that didn't seem as seamless as the rest of the process, is it possible that this was installed improperly and could be causing the issues?

The example that I tried to build was the 'at.client' project.

The LTE link Monitor was another thing that was giving me issues. I've tried using it previously to see if it could provide any insight into what was wrong however

 - the modem status says power off

 - the terminal has nothing printed out to it even after I try to reset the device via the onboard reset button

 - all of the preset command buttons (ie AT, AT+CFUN?, etc. return a timed out error in the log.

Thanks,

Aaron

[Marte Myrvold]

Hi,

If you install it with the Toolchain Manager on Windows 10 it should work out of the box. How did you open SES (SEGGER Embedded Studio)? When you install it with the Toolchain Manager you have to open it there as well, using the "Open IDE" button.

Could you open the Asset Tracker application in SES and try to build it? Please make sure to select the correct configurations when you open the project, such as the board name, which should be nrf9160dk_nrf9160ns. If you're able to build it, please flash it to your board and see whether this affects anything.

You already mention that you've updated the modem firmware, and I assume you updated it to v1.2.3. NCS v1.4.0 has been tested with modem firmware v1.2.2, as you can see here, but it should work with v1.2.3 as well. You could also update to NCS v1.4.2, which has been tested with modem firmware v1.2.3.

Are you using the iBasis SIM card provided with the DK or are you using a SIM card from another provider? If the former, have you added the SIM card to your account in nRF Cloud?

Best regards,

Marte

[AaronS]

I've been opening SES through the toolchain manager via the Open IDE button.

I've been using v1.2.3 for the modem firmware however just tried updating the board with v1.2.2 to see if it would make a difference. When trying to build the asset tracker application the build still fails with the following terminal output

Also I am using the provided iBasis sim card and it has already been added to my account in the nRF Cloud

Thanks,

Aaron

[Marte Myrvold]

Hi Aaron,

This might be a problem with the path length, as I've seen several cases where a too long path might cause problems in Windows. I would recommend reinstalling the SDK under C:/ncs/ instead. You can change the default installation directory in the settings in Toolchain Manager, or you can choose another directory when installing. As I mentioned before, installing it with the Toolchain Manager should install all necessary tools, so you shouldn't be missing any. Another thing you can try is to update the toolchain by pressing the arrow facing down next to "Open IDE" and selecting "Update toolchain". Another option is to install the SDK manually. This does however require more work, but it's an option if you run into problems during the installation using Toolchain Manager, or for those who prefer to install it manually. I would recommend first trying the two Toolchain Manager options I mentioned, installing it in another location and updating toolchain, before installing it manually.

Since the modem says powered off in LTE Link Monitor and the terminal window doesn't print any logs, it's hard to say why you're unable to connect. With both Asset Tracker, which is what new nRF9160 DKs are programmed with, and AT Client, you should get some logs when the device starts up.

Since you're having problems building applications in SES, I have created some precompiled firmware images you can try to program to your device, so we can try to figure out why you're unable to connect to nRF Cloud. You can program them with the Programmer application in nRF Connect for Desktop. I've attached the AT Client sample and Asset Tracker application. Both of them are from v1.4.0 of NCS since that's what you said you've been using. If you want another version of NCS, please let me know and I'll share that as well.

5287.at_client_merged.hex

asset_tracker_merged.hex

If you're able to program these to your device and get logs in LTE Link Monitor, please share the logs. You can download the log file from LTE Link Monitor by clicking the "Open log file" button.

Best regards,

Marte

[AaronS]

The precompiled firmware images you sent work perfectly and I'm able to connect to the cloud and see current data perfectly which seems weird as the LTE Link monitor is showing the same status values in the upper right corner of the UI. I've also attached the log file from the LTE Link monitor below as requested.

I've attached the log file from the LTE Link monitor below

However,

The issues still persist with the IDE not building any sample applications without failing even after trying different IDE versions and shortening the path length to C:/ncs/.

Although IDE version 1.5.0 seems to make it much farther in the build process before failing than the other IDEs it still ends up failing.

Here is the log file from the LTE Link monitor while flashed with the asset_tracker image:

 

Fullscreen 2021-02-25T15_34_25.493Z-log.txt Download

2021-02-25T15:34:28.881Z INFO Application data folder: C:\Users\aaron\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-02-25T15:34:29.061Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2021-02-25T15:34:29.062Z DEBUG App path: C:\Users\aaron\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-02-25T15:34:29.062Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-02-25T15:34:29.062Z DEBUG nRFConnect path: C:\Users\aaron\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-02-25T15:34:29.062Z DEBUG HomeDir: C:\Users\aaron
2021-02-25T15:34:29.063Z DEBUG TmpDir: C:\Users\aaron\AppData\Local\Temp
2021-02-25T15:35:19.152Z INFO Modem port is opened
2021-02-25T15:35:19.845Z DEBUG modem << [00:04:22.491,119] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 16: not used,     healthy[0m
2021-02-25T15:35:20.350Z DEBUG modem << [00:04:22.500,518] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  4: not used,     healthy[0m
2021-02-25T15:35:20.355Z DEBUG modem << [00:04:22.509,857] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 26: not used,     healthy[0m
2021-02-25T15:35:20.358Z DEBUG modem << [00:04:22.519,226] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 22: not used,     healthy[0m
2021-02-25T15:35:20.361Z DEBUG modem << [00:04:22.528,594] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 32: not used,     healthy[0m
2021-02-25T15:35:20.363Z DEBUG modem << [00:04:22.537,963] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  3: not used,     healthy[0m
2021-02-25T15:35:20.365Z DEBUG modem << [00:04:22.547,302] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 29: not used,     healthy[0m
2021-02-25T15:35:20.368Z DEBUG modem << [00:04:22.556,671] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 31: not used,     healthy[0m
2021-02-25T15:35:20.371Z DEBUG modem << [00:04:22.566,040] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  9: not used,     healthy[0m
2021-02-25T15:35:20.374Z DEBUG modem << [00:04:22.575,378] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 9 Using: 0 Unhealthy: 0[0m
2021-02-25T15:35:20.376Z DEBUG modem << [00:04:22.584,411] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 262[0m
2021-02-25T15:35:20.844Z DEBUG modem << [00:04:23.490,814] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 16: not used,     healthy[0m
2021-02-25T15:35:20.853Z DEBUG modem << [00:04:23.500,183] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  4: not used,     healthy[0m
2021-02-25T15:35:20.872Z DEBUG modem << [00:04:23.509,521] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 26: not used,     healthy[0m
2021-02-25T15:35:20.879Z DEBUG modem << [00:04:23.518,859] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 22: not used,     healthy[0m
2021-02-25T15:35:20.883Z DEBUG modem << [00:04:23.528,198] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 32: not used,     healthy[0m
2021-02-25T15:35:20.897Z DEBUG modem << [00:04:23.537,536] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  3: not used,     healthy[0m
2021-02-25T15:35:20.900Z DEBUG modem << [00:04:23.546,905] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 29: not used,     healthy[0m
2021-02-25T15:35:20.911Z DEBUG modem << [00:04:23.556,243] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 31: not used,     healthy[0m
2021-02-25T15:35:20.917Z DEBUG modem << [00:04:23.565,612] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  9: not used,     healthy[0m
2021-02-25T15:35:20.929Z DEBUG modem << [00:04:23.574,951] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 9 Using: 0 Unhealthy: 0[0m
2021-02-25T15:35:20.940Z DEBUG modem << [00:04:23.583,953] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 263[0m
2021-02-25T15:35:21.843Z DEBUG modem << [00:04:24.490,814] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 16: not used,     healthy[0m
2021-02-25T15:35:21.857Z DEBUG modem << [00:04:24.500,152] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  4: not used,     healthy[0m
2021-02-25T15:35:21.862Z DEBUG modem << [00:04:24.509,490] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 26: not used,     healthy[0m
2021-02-25T15:35:21.881Z DEBUG modem << [00:04:24.518,859] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 22: not used,     healthy[0m
2021-02-25T15:35:21.883Z DEBUG modem << [00:04:24.528,198] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 32: not used,     healthy[0m
2021-02-25T15:35:21.893Z DEBUG modem << [00:04:24.537,536] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  3: not used,     healthy[0m
2021-02-25T15:35:21.898Z DEBUG modem << [00:04:24.546,905] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 29: not used,     healthy[0m
2021-02-25T15:35:21.910Z DEBUG modem << [00:04:24.556,243] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 31: not used,     healthy[0m
2021-02-25T15:35:21.917Z DEBUG modem << [00:04:24.565,582] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  9: not used,     healthy[0m
2021-02-25T15:35:21.927Z DEBUG modem << [00:04:24.574,951] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 9 Using: 0 Unhealthy: 0[0m
2021-02-25T15:35:21.934Z DEBUG modem << [00:04:24.583,953] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 264[0m
2021-02-25T15:35:22.843Z DEBUG modem << [00:04:25.491,027] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 16: not used,     healthy[0m
2021-02-25T15:35:22.866Z DEBUG modem << [00:04:25.500,396] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  4: not used,     healthy[0m
2021-02-25T15:35:22.874Z DEBUG modem << [00:04:25.509,735] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 26: not used,     healthy[0m
2021-02-25T15:35:22.884Z DEBUG modem << [00:04:25.519,073] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 22: not used,     healthy[0m
2021-02-25T15:35:22.902Z DEBUG modem << [00:04:25.528,411] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 32: not used,     healthy[0m
2021-02-25T15:35:22.907Z DEBUG modem << [00:04:25.537,780] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  3: not used,     healthy[0m
2021-02-25T15:35:22.909Z DEBUG modem << [00:04:25.547,119] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 29: not used,     healthy[0m
2021-02-25T15:35:22.916Z DEBUG modem << [00:04:25.556,457] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 31: not used,     healthy[0m
2021-02-25T15:35:22.919Z DEBUG modem << [00:04:25.565,795] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  9: not used,     healthy[0m
2021-02-25T15:35:22.935Z DEBUG modem << [00:04:25.575,164] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 9 Using: 0 Unhealthy: 0[0m
2021-02-25T15:35:22.938Z DEBUG modem << [00:04:25.584,167] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 265[0m
2021-02-25T15:35:23.843Z DEBUG modem << [00:04:26.491,119] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 16: not used,     healthy[0m
2021-02-25T15:35:23.863Z DEBUG modem << [00:04:26.500,457] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  4: not used,     healthy[0m
2021-02-25T15:35:23.868Z DEBUG modem << [00:04:26.509,796] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 26: not used,     healthy[0m
2021-02-25T15:35:23.871Z DEBUG modem << [00:04:26.519,165] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 22: not used,     healthy[0m
2021-02-25T15:35:23.880Z DEBUG modem << [00:04:26.528,503] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 32: not used,     healthy[0m
2021-02-25T15:35:23.903Z DEBUG modem << [00:04:26.537,841] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  3: not used,     healthy[0m
2021-02-25T15:35:23.908Z DEBUG modem << [00:04:26.547,180] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 29: not used,     healthy[0m
2021-02-25T15:35:23.921Z DEBUG modem << [00:04:26.556,549] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 31: not used,     healthy[0m
2021-02-25T15:35:23.923Z DEBUG modem << [00:04:26.565,887] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  9: not used,     healthy[0m
2021-02-25T15:35:23.933Z DEBUG modem << [00:04:26.575,225] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 9 Using: 0 Unhealthy: 0[0m
2021-02-25T15:35:23.935Z DEBUG modem << [00:04:26.584,228] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 266[0m
2021-02-25T15:35:24.844Z DEBUG modem << [00:04:27.491,912] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 16: not used,     healthy[0m
2021-02-25T15:35:24.858Z DEBUG modem << [00:04:27.501,251] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  4: not used,     healthy[0m
2021-02-25T15:35:24.863Z DEBUG modem << [00:04:27.510,620] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 26: not used,     healthy[0m
2021-02-25T15:35:24.885Z DEBUG modem << [00:04:27.519,958] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 22: not used,     healthy[0m
2021-02-25T15:35:24.900Z DEBUG modem << [00:04:27.529,296] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 32: not used,     healthy[0m
2021-02-25T15:35:24.903Z DEBUG modem << [00:04:27.538,635] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  3: not used,     healthy[0m
2021-02-25T15:35:24.917Z DEBUG modem << [00:04:27.547,973] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 29: not used,     healthy[0m
2021-02-25T15:35:24.918Z DEBUG modem << [00:04:27.557,312] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 31: not used,     healthy[0m
2021-02-25T15:35:24.920Z DEBUG modem << [00:04:27.566,680] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  9: not used,     healthy[0m
2021-02-25T15:35:24.933Z DEBUG modem << [00:04:27.576,019] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 9 Using: 0 Unhealthy: 0[0m
2021-02-25T15:35:24.936Z DEBUG modem << [00:04:27.585,021] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 267[0m
2021-02-25T15:35:25.885Z DEBUG modem << [00:04:28.533,508] [0m<dbg> nrf9160_gps.gps_thread: PVT: Position fix[0m
2021-02-25T15:35:25.904Z DEBUG modem << [00:04:28.540,222] [0m<inf> asset_tracker: GPS_EVT_PVT_FIX[0m
2021-02-25T15:35:25.921Z DEBUG modem << [00:04:28.545,959] [0m<inf> asset_tracker: DATE_TIME_OBTAINED_EXT[0m
2021-02-25T15:35:25.924Z DEBUG modem << [00:04:28.552,276] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 16:     used,     healthy[0m
2021-02-25T15:35:25.928Z DEBUG modem << [00:04:28.561,645] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  4:     used,     healthy[0m
2021-02-25T15:35:25.951Z DEBUG modem << [00:04:28.570,983] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 26:     used,     healthy[0m
2021-02-25T15:35:25.953Z DEBUG modem << [00:04:28.580,352] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 22:     used,     healthy[0m
2021-02-25T15:35:25.954Z DEBUG modem << [00:04:28.589,691] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 32:     used,     healthy[0m
2021-02-25T15:35:25.955Z DEBUG modem << [00:04:28.599,060] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  3:     used,     healthy[0m
2021-02-25T15:35:25.969Z DEBUG modem << [00:04:28.608,398] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 29:     used,     healthy[0m
2021-02-25T15:35:25.981Z DEBUG modem << [00:04:28.617,767] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV 31:     used,     healthy[0m
2021-02-25T15:35:25.984Z DEBUG modem << [00:04:28.627,136] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking SV  9:     used,     healthy[0m
2021-02-25T15:35:25.988Z DEBUG modem << [00:04:28.636,474] [0m<dbg> nrf9160_gps.print_satellite_stats: Tracking: 9 Using: 9 Unhealthy: 0[0m
2021-02-25T15:35:26.003Z DEBUG modem << [00:04:28.645,507] [0m<dbg> nrf9160_gps.print_satellite_stats: Seconds since last fix 0[0m
2021-02-25T15:35:26.017Z DEBUG modem << [00:04:28.653,839] [0m<dbg> nrf9160_gps.gps_thread: NMEA: Position fix[0m
2021-02-25T15:35:26.019Z DEBUG modem << [00:04:28.660,583] [0m<inf> asset_tracker: Position fix with NMEA data[0m
2021-02-25T15:35:26.020Z DEBUG modem << [00:04:28.667,358] [0m<inf> asset_tracker: GPS will be started in 351 seconds[0m
2021-02-25T15:35:26.117Z DEBUG modem << %CESQ: 58,2,17,2
2021-02-25T15:35:26.631Z DEBUG modem << %CESQ: 51,2,11,1
2021-02-25T15:35:26.661Z DEBUG modem << +CSCON: 1
2021-02-25T15:35:26.663Z DEBUG modem << [00:04:29.289,184] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-02-25T15:35:33.713Z DEBUG modem << +CSCON: 0
2021-02-25T15:35:33.745Z DEBUG modem << [00:04:36.369,659] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-02-25T15:35:37.371Z DEBUG modem << %CESQ: 56,2,15,2
2021-02-25T15:35:46.259Z DEBUG modem << +CSCON: 1
2021-02-25T15:35:46.277Z DEBUG modem << [00:04:48.916,992] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-02-25T15:35:53.394Z DEBUG modem << +CSCON: 0
2021-02-25T15:35:53.412Z DEBUG modem << [00:04:56.050,689] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-02-25T15:35:56.170Z DEBUG modem << +CSCON: 1
2021-02-25T15:35:56.189Z DEBUG modem << [00:04:58.827,301] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-02-25T15:36:03.593Z DEBUG modem << +CSCON: 0
2021-02-25T15:36:03.615Z DEBUG modem << [00:05:06.251,007] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-02-25T15:36:19.595Z DEBUG modem << %CESQ: 255,0,255,0
2021-02-25T15:36:26.172Z DEBUG modem << %CESQ: 58,2,23,3
2021-02-25T15:36:26.759Z DEBUG modem << +CSCON: 1
2021-02-25T15:36:26.782Z DEBUG modem << [00:05:29.418,212] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-02-25T15:36:26.785Z DEBUG modem << %CESQ: 52,2,15,2
2021-02-25T15:36:33.813Z DEBUG modem << +CSCON: 0
2021-02-25T15:36:33.846Z DEBUG modem << [00:05:36.473,388] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-02-25T15:36:42.650Z DEBUG modem << %CESQ: 57,2,15,2
2021-02-25T15:36:46.269Z DEBUG modem << +CSCON: 1
2021-02-25T15:36:46.289Z DEBUG modem << [00:05:48.929,870] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-02-25T15:36:46.871Z DEBUG modem << %CESQ: 52,2,11,1
2021-02-25T15:36:53.666Z DEBUG modem << +CSCON: 0
2021-02-25T15:36:53.701Z DEBUG modem << [00:05:56.327,514] [0m<inf> asset_tracker: RRC mode: Idle[0m
2021-02-25T15:36:56.229Z DEBUG modem << +CSCON: 1
2021-02-25T15:36:56.257Z DEBUG modem << [00:05:58.890,106] [0m<inf> asset_tracker: RRC mode: Connected[0m
2021-02-25T15:37:03.741Z DEBUG modem << +CSCON: 0
2021-02-25T15:37:03.747Z DEBUG modem << [00:06:06.402,832] [0m<inf> asset_tracker: RRC mode: Idle[0m

[Marte Myrvold]

Hi,

Great to hear that you're able to connect to cloud and send data, then we know that your nRF9160 DK works as expected and that there are no problems connecting to the network.

The reason LTE Link Monitor shows modem off might be because there hasn't been sent any AT commands to the modem yet. I'm sorry if my previous replies has been confusing regarding this, but LTE Link Monitor doesn't know the status of the modem unless the device has tried to communicate with it, so if there hasn't been sent any AT commands after you connected to the nRF9160 DK in LTE Link Monitor, then the program won't know the status of the modem. You can get the current functional mode of the modem with AT+CFUN?. This should return +CFUN: 1 if the modem is in normal mode, and this will also let LTE Link Monitor know the status of the modem. You should have Automatic requests turned on for this (can be found in the lower right of the LTE Link Monitor).

I've tried to reproduce the issue you're experiencing when building, but so far I've been unable to do so. What are you selecting as toolchain version when you open the projects? Have you made any changes to the installation? Could you check what the environment variables are set to in SES? You can do this by going to Tools > Options > nRF Connect. Since you installed NCS with Toolchain Manager, you should have the following:

GNU ARM Embedded Toolchain Directory = C:\ncs\<ncs_version>\toolchain\opt

Zephyr Base = C:\ncs\<ncs_version>\zephyr

Also let me know if any of the other fields are something other than None.

Best regards,

Marte

[AaronS]

Marte, 

Apologies for not responding sooner, it turns out the issue was that SES needed administrative access to run the cmd commands. opening the nRFconnect app as administrator fixed my issues