nrf9160 DK asset_tracker loaded on board but not running

RE: nrf9160 DK asset_tracker loaded on board but not running

SuperAbe — Mon, 04 Feb 2019 17:43:02 GMT

That worked. Thank you.

I'm really loving nrf9160

RE: nrf9160 DK asset_tracker loaded on board but not running

stevenminnick — Mon, 04 Feb 2019 15:35:19 GMT

SuperAbe,

If you are running the asset tracker tool there is no service listening to the serial port and forwarding the commands to the radio. When you use the link monitor, you are seeing the output from any printf's in the code, but when you send an AT command something has to be listening (and nothing is). The asset tracker code has all the AT commands baked into it and send those to the radio to connect.

If you open the at_client software you can see how that is listening on the serial port and just passing data back and forth between the computer and the radio module. You need to load the at_client software if you want to send AT commands and get a response. Otherwise if you are running the asset tracker all you are seeing is output debug messages.

Steve

RE: nrf9160 DK asset_tracker loaded on board but not running

SuperAbe — Fri, 01 Feb 2019 19:57:36 GMT

Thank you, Martin.

My board is behaving blinking and connecting to NRF cloud. Now I'm back to my first issue.

AT commands always 'Error: 'AT+CFUN=1' timed out'

RE: nrf9160 DK asset_tracker loaded on board but not running

Martin Lesund — Fri, 01 Feb 2019 13:45:36 GMT

Hi SuperAbe,

First of I would highly recommend that you check out the "Getting started guide" on Devzone.

It could be that you find your answer in that tutorial.

Remember that when you connect the nRF91 to a computer it gives you access to three Virtual COM ports:

VCOM0 – Connected to nRF9160 (default)
VCOM1 – Connected to nRF52840 (nonconfigurable)
VCOM2 – Not connected to nRF9160 (default)

So if you use a serial terminal you should make sure you are connected to the correct COM port so you are getting the correct data.

It is usually the least incremented COM port that is for the nrf91, but you can confirm this also by checking in "Device manager", right click the COM port and select "properties" and go to the "Events" tab and look in the "information" box to see that it includes: MI_00.

This is something that you don't have to think about if you are using the Terminal in the "LTE Link Monitor" application in "nRF Connect for Desktop".

That terminal selects the correct COM port for you:

If you want to use that Terminal as a regular terminal you need to deselect the "Automatic requests" in the down-right corner:

Or else it will begin to send AT-commands automatically and update the information shown on the right tab.

With regards to that the kit is not blinking, it sounds like you may be missing the secure_boot sample as well.

This is all covered in the tutorial mentioned in the beginning of this post.

Let me know if something is unclear and I will happily help.

Best Regards,

Martin L.