LTE Link Monitor Timing out

[always]

I have a nRF9160 DK that I am trying to get on a network. The iBasis sim does not appear to be in the coverage area, the SIM activated, but has not had both LEDs 3 & 4 blinking at any point. I have installed nRF connect 2.6.2 on Windows 10, followed by the LTE Link Monitor, in an attempt to see what the modem is doing and change sims as needed. However, when I try to run any AT command it gives me Error: 'command' timed out. 

It has also started spewing the following after 10min:

***** Booting Zephyr OS kitprod_w49 *****

Application started

LTE LC config ...

[00:00:00.941,589] 

[1;31m<err> net_if.net_if_init: There is no network interface to work with!

[0m

nrf_cloud_connect failed: 60

***** Booting Zephyr OS v1.13.99-ncs1-1823-g715d2df3dd *****

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 2002c790

Secure Boot: prepare to jump to Non-Secure image

***** Booting Zephyr OS kitprod_w49 *****

Application started

LTE LC config ...

[00:00:00.940,063] 

[1;31m<err> net_if.net_if_init: There is no network interface to work with![0m

nrf_cloud_connect failed: 60

On a separate note, is there a way to access the ATI commands using screen or something equivalent. 

Thanks!

[Martin Lesund]

Hi always,

The asset_tracker application that comes with the nrf91 DK does not support AT-Commands by default.

You either need to flash the at_client sample or the newest asset_tracker sample from master branch (which has the AT host library included) to use the LTE Link Monitor.

I am adding the precompiled hex files, then you can choose which of them you want to run.

• asset_tracker.hex
• at_client.hex

You can use nrfjprog to flash (command line based) or nrf Connect Programmer to flash the .hex file to the device.

To use nrfjprog use the command: nrfjprog --program asset_tracker.hex -f nrf91 --sectorerase -r --verify

---

example; running the asset_tracker and pairing with nrf_cloud and then send some simple AT commands:

---

Best regards,

Martin L.

[rkguy]

Martin:
I have been trying to issue cesq automatically when the gps is triggered so I can send the signal strength to the cloud every 60 seconds.

I have been working with the master branch and trying to do this the right way but it isn't working. Supposedly I should be doing this but I my pointer is null, there is never any data there.
modem_info_short_get(MODEM_INFO_RSRP, your_data_buffer)

What is a better way of doing this? I basically just need a very very simple tracker_application that only sends the current signal strength, and nothing else.

This question relates to the one I asked here: devzone.nordicsemi.com/.../quick-way-to-send-signal-strength-to-nrfcloud-by-hacking-tracker_update-application