nRF9160 NB-IoT signal strength polling

[danielClark]

Hi,

So I am trying to poll the signal strength of the nRF9160 DK and at first everything seems okay, the device gains connection and all the boxes in the LTE Link Monitor go green and can deliver RSRP values but after approximately 1 minute, it loses the ability to read the signal strength(RSRP -> 255). Then I have to reset the device again to read new signal strength values.

I am using a 1NCE sim card and am located in Germany and I have the NB-IoT firmware installed. I am using the AT+CESQ command to retrieve the signal strength information. The screenshots of the LTE link monitor output are below.

thanks in advance!

Dan

[Øyvind]

Hi Dan, 

Are you running the standard AT_Client or a customized version? Please load the standard AT_Client and let it run for some minutes in LTE Link Monitor. Then, from the LTE Link Monitor, click Open Log File in the bottom part of the window (see image below):

Please provide a screenshot of the LTE Link Monitor as well. Can you please contact 1NCE and ask what band they support in NB-IoT? From the screenshot you have provided, the command %XCBAND shows the supported band for the modem.

Thank you!

Kind regards,
Øyvind

[danielClark]

Hi Øyvind,

I am running the standard AT_Client and can confirm(as KnutS says) that 1NCE is provided by Deutsche Telekom on Band 8 in Germany.

kind regards,

Dan

Fullscreen 2019-03-27T13_23_45.675Z-log.txt Download

2019-03-27T13:23:48.375Z INFO Application data folder: C:\Users\XXXXXXXX\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2019-03-27T13:23:48.472Z DEBUG App pc-nrfconnect-linkmonitor v0.7.0 official
2019-03-27T13:23:48.472Z DEBUG App path: C:\Users\XXXXXXXXX\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2019-03-27T13:23:48.472Z DEBUG nRFConnect 2.6.2 is supported by the app (^2.4.0)
2019-03-27T13:23:48.472Z DEBUG nRFConnect path: C:\Users\XXXXXXXX\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-03-27T13:23:48.472Z DEBUG HomeDir: C:\Users\XXXXXXXX
2019-03-27T13:23:48.472Z DEBUG TmpDir: C:\Users\XXXXXXXX~1.COM\AppData\Local\Temp
2019-03-27T13:23:48.474Z VERBOSE Could not fetch serial number for serial port at COM3
2019-03-27T13:23:53.914Z INFO Modem port is opened
2019-03-27T13:23:53.921Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-03-27T13:23:56.210Z DEBUG modem << ***** Booting Zephyr OS v1.13.99-ncs2 *****\x0D
2019-03-27T13:23:56.222Z DEBUG modem << Secure Boot: configure flash\x0D\x0A
2019-03-27T13:23:56.231Z DEBUG modem << Secure Boot: SPU: set region 0 as Secure\x0D\x0A
2019-03-27T13:23:56.235Z DEBUG modem << Secure Boot: SPU: set region 1 as Secure\x0D\x0A
2019-03-27T13:23:56.239Z DEBUG modem << Secure Boot: SPU: set region 2 as Secure\x0D\x0A
2019-03-27T13:23:56.255Z DEBUG modem << Secure Boot: SPU: set region 3 as Secure\x0D\x0A
2019-03-27T13:23:56.258Z DEBUG modem << Secure Boot: SPU: set region 4 as Secure\x0D\x0A
2019-03-27T13:23:56.261Z DEBUG modem << Secure Boot: SPU: set region 5 as Secure\x0D\x0A
2019-03-27T13:23:56.265Z DEBUG modem << Secure Boot: SPU: set region 6 as Secure\x0D\x0A
2019-03-27T13:23:56.267Z DEBUG modem << Secure Boot: SPU: set region 7 as Secure\x0D\x0A
2019-03-27T13:23:56.271Z DEBUG modem << Secure Boot: SPU: set Flash region 8 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.278Z DEBUG modem << Secure Boot: SPU: set Flash region 9 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.285Z DEBUG modem << Secure Boot: SPU: set Flash region 10 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.288Z DEBUG modem << Secure Boot: SPU: set Flash region 11 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.291Z DEBUG modem << Secure Boot: SPU: set Flash region 12 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.296Z DEBUG modem << Secure Boot: SPU: set Flash region 13 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.308Z DEBUG modem << Secure Boot: SPU: set Flash region 14 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.312Z DEBUG modem << Secure Boot: SPU: set Flash region 15 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.316Z DEBUG modem << Secure Boot: SPU: set Flash region 16 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.321Z DEBUG modem << Secure Boot: SPU: set Flash region 17 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.324Z DEBUG modem << Secure Boot: SPU: set Flash region 18 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.327Z DEBUG modem << Secure Boot: SPU: set Flash region 19 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.331Z DEBUG modem << Secure Boot: SPU: set Flash region 20 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.340Z DEBUG modem << Secure Boot: SPU: set Flash region 21 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.348Z DEBUG modem << Secure Boot: SPU: set Flash region 22 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.352Z DEBUG modem << Secure Boot: SPU: set Flash region 23 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.358Z DEBUG modem << Secure Boot: SPU: set Flash region 24 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.361Z DEBUG modem << Secure Boot: SPU: set Flash region 25 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.368Z DEBUG modem << Secure Boot: SPU: set Flash region 26 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.372Z DEBUG modem << Secure Boot: SPU: set Flash region 27 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.383Z DEBUG modem << Secure Boot: SPU: set Flash region 28 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.386Z DEBUG modem << Secure Boot: SPU: set Flash region 29 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.389Z DEBUG modem << Secure Boot: SPU: set Flash region 30 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.394Z DEBUG modem << Secure Boot: SPU: set Flash region 31 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.400Z DEBUG modem << Secure Boot: configure SRAM\x0D\x0A
2019-03-27T13:23:56.403Z DEBUG modem << Secure Boot: SPU: set SRAM region 0 as Secure\x0D\x0A
2019-03-27T13:23:56.407Z DEBUG modem << Secure Boot: SPU: set SRAM region 1 as Secure\x0D\x0A
2019-03-27T13:23:56.409Z DEBUG modem << Secure Boot: SPU: set SRAM region 2 as Secure\x0D\x0A
2019-03-27T13:23:56.412Z DEBUG modem << Secure Boot: SPU: set SRAM region 3 as Secure\x0D\x0A
2019-03-27T13:23:56.415Z DEBUG modem << Secure Boot: SPU: set SRAM region 4 as Secure\x0D\x0A
2019-03-27T13:23:56.426Z DEBUG modem << Secure Boot: SPU: set SRAM region 5 as Secure\x0D\x0A
2019-03-27T13:23:56.430Z DEBUG modem << Secure Boot: SPU: set SRAM region 6 as Secure\x0D\x0A
2019-03-27T13:23:56.434Z DEBUG modem << Secure Boot: SPU: set SRAM region 7 as Secure\x0D\x0A
2019-03-27T13:23:56.437Z DEBUG modem << Secure Boot: SPU: set SRAM region 8 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.438Z DEBUG modem << Secure Boot: SPU: set SRAM region 9 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.440Z DEBUG modem << Secure Boot: SPU: set SRAM region 10 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.441Z DEBUG modem << Secure Boot: SPU: set SRAM region 11 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.443Z DEBUG modem << Secure Boot: SPU: set SRAM region 12 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.444Z DEBUG modem << Secure Boot: SPU: set SRAM region 13 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.454Z DEBUG modem << Secure Boot: SPU: set SRAM region 14 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.457Z DEBUG modem << Secure Boot: SPU: set SRAM region 15 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.460Z DEBUG modem << Secure Boot: SPU: set SRAM region 16 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.462Z DEBUG modem << Secure Boot: SPU: set SRAM region 17 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.466Z DEBUG modem << Secure Boot: SPU: set SRAM region 18 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.468Z DEBUG modem << Secure Boot: SPU: set SRAM region 19 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.479Z DEBUG modem << Secure Boot: SPU: set SRAM region 20 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.483Z DEBUG modem << Secure Boot: SPU: set SRAM region 21 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.486Z DEBUG modem << Secure Boot: SPU: set SRAM region 22 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.490Z DEBUG modem << Secure Boot: SPU: set SRAM region 23 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.494Z DEBUG modem << Secure Boot: SPU: set SRAM region 24 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.502Z DEBUG modem << Secure Boot: SPU: set SRAM region 25 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.517Z DEBUG modem << Secure Boot: SPU: set SRAM region 26 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.522Z DEBUG modem << Secure Boot: SPU: set SRAM region 27 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.525Z DEBUG modem << Secure Boot: SPU: set SRAM region 28 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.529Z DEBUG modem << Secure Boot: SPU: set SRAM region 29 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.534Z DEBUG modem << Secure Boot: SPU: set SRAM region 30 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.537Z DEBUG modem << Secure Boot: SPU: set SRAM region 31 as Non-Secure\x0D\x0A
2019-03-27T13:23:56.540Z DEBUG modem << Secure Boot: configure peripherals\x0D\x0A
2019-03-27T13:23:56.543Z DEBUG modem << Secure Boot: MSP_NS 200265f0\x0D\x0A
2019-03-27T13:23:56.561Z DEBUG modem << Secure Boot: prepare to jump to Non-Secure image\x0D\x0A
2019-03-27T13:23:57.228Z DEBUG modem << ***** Booting Zephyr OS v1.13.99-ncs2 *****\x0D\x0A
2019-03-27T13:23:57.239Z DEBUG modem << The AT host sample started\x0D\x0A
2019-03-27T13:24:00.230Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-03-27T13:24:00.247Z DEBUG modem << +CFUN: 4\x0D\x0A
2019-03-27T13:24:00.265Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:00.276Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2019-03-27T13:24:00.293Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.574Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-03-27T13:24:06.581Z DEBUG modem << +CFUN: 1\x0D\x0A
2019-03-27T13:24:06.587Z DEBUG modem << OK\x0D\x0A
2019-03-27T13:24:06.597Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2019-03-27T13:24:06.605Z DEBUG modem << +CGSN: "352656100033854"\x0D\x0A
2019-03-27T13:24:06.609Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.626Z DEBUG modem >> AT+CGMI\x0D\x0A
2019-03-27T13:24:06.642Z DEBUG modem << Nordic Semiconductor ASA\x0D\x0A
2019-03-27T13:24:06.646Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.651Z DEBUG modem >> AT+CGMM\x0D\x0A
2019-03-27T13:24:06.664Z DEBUG modem << nRF9120\x0D
2019-03-27T13:24:06.668Z DEBUG modem << \x0A
2019-03-27T13:24:06.673Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.683Z DEBUG modem >> AT+CGMR\x0D\x0A
2019-03-27T13:24:06.697Z DEBUG modem << mfw-nb1_nrf9160_0.3.0-94.prealpha\x0D\x0A
2019-03-27T13:24:06.700Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.708Z INFO Nordic Semiconductor ASA nRF9120 [mfw-nb1_nrf9160_0.3.0-94.prealpha] SerNr: 352656100033854
2019-03-27T13:24:06.717Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2019-03-27T13:24:06.732Z DEBUG modem << +CEMODE: 0\x0D\x0A
2019-03-27T13:24:06.735Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.752Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2019-03-27T13:24:06.768Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,20,25,26,28,66)\x0D\x0A
2019-03-27T13:24:06.773Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.791Z DEBUG modem >> AT+CMEE?\x0D\x0A
2019-03-27T13:24:06.805Z DEBUG modem << +CMEE: 0\x0D\x0A
2019-03-27T13:24:06.809Z DEBUG modem << OK\x0D
2019-03-27T13:24:06.821Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2019-03-27T13:24:06.836Z DEBUG modem << OK\x0D
2019-03-27T13:24:06.851Z DEBUG modem >> AT+CNEC?\x0D\x0A
2019-03-27T13:24:06.867Z DEBUG modem << +CNEC: 0\x0D\x0A
2019-03-27T13:24:06.870Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.884Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2019-03-27T13:24:06.908Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.925Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2019-03-27T13:24:06.946Z DEBUG modem << +CGEREP: 0,0\x0D\x0A
2019-03-27T13:24:06.950Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:06.954Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2019-03-27T13:24:06.970Z DEBUG modem << +CGDCONT: 0,"IP","iot.1nce.net.MNC040.MCC901.GPRS","10.205.180.1",0,0\x0D
2019-03-27T13:24:06.987Z DEBUG modem << \x0A
2019-03-27T13:24:06.992Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.013Z DEBUG modem >> AT+CGACT?\x0D\x0A
2019-03-27T13:24:07.042Z DEBUG modem << +CGACT: 0,1\x0D\x0A
2019-03-27T13:24:07.045Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.056Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2019-03-27T13:24:07.074Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.092Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2019-03-27T13:24:07.113Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.117Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2019-03-27T13:24:07.123Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.143Z DEBUG modem >> AT+CEREG?\x0D\x0A
2019-03-27T13:24:07.166Z DEBUG modem << +CEREG: 2,5,"CB34","019DBF0A",9\x0D\x0A
2019-03-27T13:24:07.170Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.199Z DEBUG modem >> AT+COPS=3,2\x0D\x0A
2019-03-27T13:24:07.219Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.242Z DEBUG modem >> AT+COPS?\x0D\x0A
2019-03-27T13:24:07.264Z DEBUG modem << +COPS: 0,2,"26201",9\x0D\x0A
2019-03-27T13:24:07.268Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.289Z DEBUG modem >> AT%XCBAND\x0D\x0A
2019-03-27T13:24:07.313Z DEBUG modem << %XCBAND: 8\x0D\x0A
2019-03-27T13:24:07.318Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.339Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2019-03-27T13:24:07.363Z DEBUG modem << +CGDCONT: 0,"IP","iot.1nce.net.MNC040.MCC901.GPRS","10.205.180.1",0,0\x0D\x0A
2019-03-27T13:24:07.368Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.389Z DEBUG modem >> AT+CGACT?\x0D\x0A
2019-03-27T13:24:07.412Z DEBUG modem << +CGACT: 0,1\x0D\x0A
2019-03-27T13:24:07.417Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.438Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2019-03-27T13:24:07.461Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.480Z DEBUG modem >> AT+CESQ\x0D\x0A
2019-03-27T13:24:07.516Z DEBUG modem << +CESQ: 99,99,255,255,255,54\x0D\x0A
2019-03-27T13:24:07.520Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.545Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2019-03-27T13:24:07.570Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.592Z DEBUG modem >> AT%XSIM?\x0D\x0A
2019-03-27T13:24:07.618Z DEBUG modem << %XSIM: 1\x0D
2019-03-27T13:24:07.625Z DEBUG modem << \x0A
2019-03-27T13:24:07.630Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.658Z DEBUG modem >> AT+CPIN?\x0D\x0A
2019-03-27T13:24:07.687Z DEBUG modem << +CPIN: READY\x0D\x0A
2019-03-27T13:24:07.693Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.724Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2019-03-27T13:24:07.754Z DEBUG modem << +CPINR: "SIM PIN",3\x0D\x0A
2019-03-27T13:24:07.759Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.785Z DEBUG modem >> AT+CIMI\x0D\x0A
2019-03-27T13:24:07.816Z DEBUG modem << 901405100335449\x0D\x0A
2019-03-27T13:24:07.822Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:07.827Z INFO IMSIdentity: 901405100335449
2019-03-27T13:24:28.590Z DEBUG modem << %CESQ: 49,2\x0D\x0A\x00
2019-03-27T13:24:52.881Z DEBUG modem << %CESQ: 44,2\x0D\x0A\x00
2019-03-27T13:24:54.400Z DEBUG modem << %CESQ: 255,0\x0D\x0A
2019-03-27T13:24:54.583Z DEBUG modem << %XSIM: 1\x0D\x0A\x00
2019-03-27T13:24:54.603Z DEBUG modem >> AT+CPIN?\x0D\x0A
2019-03-27T13:24:54.629Z DEBUG modem << +CPIN: READY\x0D\x0A
2019-03-27T13:24:54.633Z DEBUG modem << OK\x0D\x0A\x00
2019-03-27T13:24:54.658Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2019-03-27T13:24:54.683Z DEBUG modem << +CME ERROR: 0\x0D\x0A\x00

[Øyvind]

Thank you, Dan.

Can you also provide a modem trace from your board? Follow these instructions:

1. Program the hex file zephyr_at_client.hex with this command
   nrfjprog.exe --program zephyr_at_client.hex -f nrf91 --sectorerase --verify  zephyr_at_client.hex
2. Reset the board.
3. Install "Trace Collector" in nRF Connect 2.6.2, then open and connect to the nRF91 board.
   1. Click "Start capture"
4. Open LTE Link Monitor and connect to nRF91.
   1. Reset the board once more.
   2. Enter the AT command AT%XMODEMTRACE=1,2 and click send. Should return OK.
      
5. Start AT_client application with AT+CFUN?

6. In the Trace Collector keep your eyes on the trace size, if the size is increasing then it is working.

7. When AT_client has reached its end, you can stop the Trace Collector and click "Show in folder".

   1. Then attach the trace file here, so that I can forward to our internal team. 
      
      

I will forward both trace file and log file to our internal team. 

Thank you!

Best regards,
Øyvind

[danielClark]

Hi Øyvind,

Attached is the trace file.

trace-2019-03-29T15-04-49.777Z.bin

kind regards,

Dan

[Øyvind]

Thank you. I have forwarded the modem trace and log file to our internal team and will get back to you as soon as I have an answer.

-Øyvind