AT commands on nRF9160 DK Asset Tracker Example

[iotlight]

I followed http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker/README.html#asset-tracker

to perform "Testing".  I successfully completed steps 1 thru 14, but not step 15: send AT commands from the terminal, and observe that the reponse is received.

I got Errors for every AT commands I input.  I also attached the log file

Fullscreen 2019-02-27T07_19_33.810Z-log.txt Download

2019-02-27T07:19:38.862Z INFO Application data folder: C:\Users\advanchip\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2019-02-27T07:19:39.746Z DEBUG App pc-nrfconnect-linkmonitor v0.7.0 official
2019-02-27T07:19:39.746Z DEBUG App path: C:\Users\advanchip\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2019-02-27T07:19:39.746Z DEBUG nRFConnect 2.6.2 is supported by the app (^2.4.0)
2019-02-27T07:19:39.747Z DEBUG nRFConnect path: C:\Users\advanchip\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-02-27T07:19:39.747Z DEBUG HomeDir: C:\Users\advanchip
2019-02-27T07:19:39.747Z DEBUG TmpDir: C:\Users\ADVANC~1\AppData\Local\Temp
2019-02-27T07:19:46.758Z INFO Modem port is opened
2019-02-27T07:19:46.764Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-02-27T07:21:13.167Z DEBUG modem >> AT+CMD=?\x0D\x0A
2019-02-27T07:21:14.169Z ERROR Error: 'AT+CMD=?
' timed out
2019-02-27T07:22:15.071Z DEBUG modem >> +CGMI\x0D\x0A
2019-02-27T07:22:16.073Z ERROR Error: '+CGMI
' timed out
2019-02-27T07:22:37.286Z DEBUG modem >> AT+CGMI\x0D\x0A
2019-02-27T07:22:38.288Z ERROR Error: 'AT+CGMI
' timed out
2019-02-27T07:23:28.831Z DEBUG modem >> +CGMM\x0D\x0A
2019-02-27T07:23:29.833Z ERROR Error: '+CGMM
' timed out
2019-02-27T07:23:53.420Z DEBUG modem >> AT+CGMM\x0D\x0A
2019-02-27T07:23:54.420Z ERROR Error: 'AT+CGMM
' timed out
2019-02-27T07:24:05.631Z DEBUG modem >> AT\x0D\x0A
2019-02-27T07:24:06.632Z ERROR Error: 'AT
' timed out
2019-02-27T07:24:24.566Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-02-27T07:24:25.566Z ERROR Error: 'AT+CFUN?
' timed out
2019-02-27T07:24:58.032Z DEBUG modem >> AT+CGMR\x0D\x0A
2019-02-27T07:24:59.032Z ERROR Error: 'AT+CGMR
' timed out
2019-02-27T07:25:45.002Z DEBUG modem >> AT+CGSN\x0D\x0A
2019-02-27T07:25:46.004Z ERROR Error: 'AT+CGSN
' timed out
2019-02-27T07:26:08.520Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2019-02-27T07:26:09.520Z ERROR Error: 'AT+CGSN=1
' timed out
2019-02-27T07:27:13.068Z DEBUG modem >> AT+CIMI\x0D\x0A
2019-02-27T07:27:14.069Z ERROR Error: 'AT+CIMI
' timed out
2019-02-27T07:28:28.179Z DEBUG modem >> AT+CLAC\x0D\x0A
2019-02-27T07:28:29.181Z ERROR Error: 'AT+CLAC
' timed out
2019-02-27T07:32:35.440Z DEBUG modem >> AT+CMD=1\x0D\x0A
2019-02-27T07:32:36.441Z ERROR Error: 'AT+CMD=1
' timed out
2019-02-27T07:33:10.495Z DEBUG modem >> AT+CMD?\x0D\x0A
2019-02-27T07:33:11.497Z ERROR Error: 'AT+CMD?
' timed out
2019-02-27T07:33:26.737Z DEBUG modem >> AT+CMD?\x0D\x0A
2019-02-27T07:33:27.739Z ERROR Error: 'AT+CMD?
' timed out
2019-02-27T07:34:40.726Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2019-02-27T07:34:41.726Z ERROR Error: 'AT+CFUN=1
' timed out

I followed the nRF91 AT Commands Reference Guide AT command syntax

nrf91_at_commands_v0.7.pdf

Please advise.  Thanks

[Bjørn Kvaale]

The asset tracker example does not include the AT module for sending & receiving AT commands. Could you please follow the testing guideline here? In step 6, you can use a tool such as tera term to see the logging of the nRF91 DK. Make sure to open up three terminal windows & connect to each of the three COM ports. In the example below, this would be COM 103, COM 104 & COM 105:

Are you able to connect to the nRF Cloud?

[iotlight]

I followed your testing guideline "here" which is same as the link http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker/README.html#asset-tracker I posted in this question.

I can successfully completed from steps 1 thru 14 including connect to the nRFCloud

I also followed your instruction to connect to the Tera Term and LTE Link Monitor as the testing guideline suggested in step 2.

However, I don't know how to perform "step 15: Optionally send AT commands from the terminal, and observe that the reponse is received. " as suggested in the testing guideline.  Please guide me if this step 15 can be tested.  Thanks.

[Bjørn Kvaale]

Looking at the code difference between the at_client example & the asset_tracker example, it seems the at commands functionality from the at_client example (i.e. at_host_init() & at_host_process()) has not been added to the asset_tracker example. Therefore, it seems as of now that this step cannot be tested.

[Bjørn Kvaale]

Your documentation was using the tag v0.3.99, which is a newer SW than the one I am using. I noticed that in the v0.3.0 documentation, step 15 is missing. Most likely, you are running the v0.3.0 FW on your board & therefore you cannot send AT commands yet. I would wait until the stable v0.3.99 tag is released here.