nRF9160 real network power profile

[Willem21]

I trying to match the nrf9160DK current consumption measured with the "power Profiler kit II" with the "online power profiler".

I watched the nordic youtube video "How to power profile your cellular IoT application".

In the video a total average current of 83uA is archived for the UDP example.

When I execute the same UDP example on the nrf9160DK I get a total average current of 579uA. See picture with the red circle.

Maybe the difference is due the part within the red circle which is much longer than the "cDRX inactivity timer" from the video.

What is the name of the part within the red circle and how can I enter this part in the "online power profiler"?

 

nRF9160DK PCA10090 1.1.0

Modem firmware: mfw_nrf9160_1.3.4.zip

Measured PSM floor current: 3.73uA

NRF Connect SDK V2.2.0

[Øyvind]

Hello, 

Are you able to provide any log output from the device during the measurements, along with a modem trace? This will tell us what is going on in the background. What SIM card are you using? What is you location?

Note that there are several settings that differ from network to network, e.g. is the roaming SIM allowed on the network. 

Thanks!

Kind regards, 
Øyvind

[Willem21]

Hello, 

Below you can find the log output and modem trace file.

I'm using the IBASIS eSIM (I get simular results with a simpoint SIM)

My location: The Netherlands, Drenthe, Emmen, 7812VA

Fullscreen log output.txt Download

[2023-02-16 13:45:35.841] I: Trace thread ready
[2023-02-16 13:45:35.851] I: Trace level override: 2
[2023-02-16 13:45:35.853] *** Booting Zephyr OS build v3.2.99-ncs1 ***
[2023-02-16 13:45:35.857] UDP sample has started
[2023-02-16 13:45:37.216] LTE cell changed: Cell ID: 4152588, Tracking area: 33201
[2023-02-16 13:45:37.298] RRC mode: Connected
[2023-02-16 13:45:37.884] Network registration status: Connected - home network
[2023-02-16 13:45:37.890] PSM parameter update: TAU: 3600, Active time: 0
[2023-02-16 13:45:37.895] Transmitting UDP/IP payload of 38 bytes to the IP address 8.8.8.8, port number 2469
[2023-02-16 13:45:48.572] RRC mode: Idle
[2023-02-16 13:45:48.574] 

trace-2023-02-16T12-45-32.766Z.bin

Kind regards, 

Willem

[Øyvind]

Willem, 

The modem trace and logs are too small. How long did you leave them running?

Kind regards,
Øyvind

[Willem21]

For approximately the duration seen in the power profiler screenshot.

I could open the trace file in the "Trace Collector V2 preview" and in wireshark.

[Willem21]

Øyvind,

I executed the modem trace and logs once more.

Now the.bin file is a little bigger.

I also included the log file found in the "logs" directory

Hopefully it's now large enough.

trace-2023-02-16T14-01-00.016Z.bin

Fullscreen 2023-02-16T13_59_37.224Z-log.txt Download

2023-02-16T13:59:37.375Z DEBUG Application data folder: C:\Users\WIJO\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector-preview
2023-02-16T13:59:37.437Z DEBUG Lib module versions:
2023-02-16T13:59:37.438Z DEBUG - nrfml library version () 0.10.5
2023-02-16T13:59:37.438Z DEBUG - @nordicsemiconductor/nrf-monitor-lib-js 0.7.6
2023-02-16T13:59:37.455Z DEBUG App pc-nrfconnect-tracecollector-preview v0.3.7 local
2023-02-16T13:59:37.455Z DEBUG App path: C:\Users\WIJO\.nrfconnect-apps\node_modules\pc-nrfconnect-tracecollector-preview
2023-02-16T13:59:37.455Z DEBUG nRFConnect 4.0.0, required by the app is (>=4.0.0)
2023-02-16T13:59:37.455Z DEBUG nRFConnect path: C:\Users\WIJO\AppData\Local\Programs\nrfconnect\resources\app.asar
2023-02-16T13:59:37.455Z DEBUG HomeDir: C:\Users\WIJO
2023-02-16T13:59:37.455Z DEBUG TmpDir: C:\Users\WIJO\AppData\Local\Temp
2023-02-16T13:59:37.713Z INFO Using nrf-device-lib-js version: 0.5.0
2023-02-16T13:59:37.713Z INFO Using nrf-device-lib version: 0.13.11
2023-02-16T13:59:37.713Z INFO Using nrfjprog DLL version: 10.18.2
2023-02-16T13:59:37.714Z INFO Using JLink version: JLink_V7.80c
2023-02-16T13:59:37.946Z INFO Installed JLink version does not match the provided version (V7.66a)
2023-02-16T13:59:40.232Z INFO Selected device with s/n 000960094437
2023-02-16T13:59:42.395Z DEBUG Client Id: 2d0f0703-1d97-435d-9730-7fe275cd0bcd
2023-02-16T13:59:42.601Z INFO Started tracefile
2023-02-16T13:59:43.611Z DEBUG Google Analytics for category pc-nrfconnect-tracecollector-preview-dev has initialized
2023-02-16T14:00:12.116Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Starting Raw trace"}
2023-02-16T14:00:12.118Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Getting OPP params"}
2023-02-16T14:00:12.119Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"architecture","label":"ia32"}
2023-02-16T14:00:12.120Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Stopping trace"}
2023-02-16T14:00:12.126Z INFO Finished tracefile
2023-02-16T14:00:15.080Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Starting Raw trace"}
2023-02-16T14:00:15.081Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Getting OPP params"}
2023-02-16T14:00:15.082Z INFO Started tracefile
2023-02-16T14:00:28.235Z INFO Detected modem firmware with UUID f6e3bd7b-7df3-4b88-b43a-a7a9766a04ad
2023-02-16T14:00:28.236Z INFO Using trace DB C:\Users\WIJO\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector-preview\trace_db_cache\nRF9160\1.3.4\f6e3bd7b-7df3-4b88-b43a-a7a9766a04ad\mfw_nrf9160_1.3.4_trace-db.json
2023-02-16T14:00:48.316Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Stopping trace"}
2023-02-16T14:00:48.321Z INFO Finished tracefile
2023-02-16T14:01:00.016Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Starting Raw trace"}
2023-02-16T14:01:00.018Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Getting OPP params"}
2023-02-16T14:01:00.019Z INFO Started tracefile
2023-02-16T14:01:09.125Z INFO Detected modem firmware with UUID f6e3bd7b-7df3-4b88-b43a-a7a9766a04ad
2023-02-16T14:01:09.125Z INFO Using trace DB C:\Users\WIJO\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector-preview\trace_db_cache\nRF9160\1.3.4\f6e3bd7b-7df3-4b88-b43a-a7a9766a04ad\mfw_nrf9160_1.3.4_trace-db.json
2023-02-16T14:01:37.804Z DEBUG Sending usage data {"category":"pc-nrfconnect-tracecollector-preview-dev","action":"Stopping trace"}
2023-02-16T14:01:37.812Z INFO Finished tracefile

Fullscreen 1464.log output.txt Download

[2023-02-16 15:01:09.089] I: Trace thread ready
[2023-02-16 15:01:09.099] I: Trace level override: 2
[2023-02-16 15:01:09.102] *** Booting Zephyr OS build v3.2.99-ncs1 ***
[2023-02-16 15:01:09.105] UDP sample has started
[2023-02-16 15:01:10.342] LTE cell changed: Cell ID: 4152588, Tracking area: 33201
[2023-02-16 15:01:10.562] RRC mode: Connected
[2023-02-16 15:01:11.726] Network registration status: Connected - home network
[2023-02-16 15:01:11.732] PSM parameter update: TAU: 3600, Active time: 0
[2023-02-16 15:01:11.737] Transmitting UDP/IP payload of 38 bytes to the IP address 8.8.8.8, port number 2469
[2023-02-16 15:01:22.838] RRC mode: Idle
[2023-02-16 15:01:22.840] 

With best regards,

Willem

[Øyvind]

Willem, 

I'm not able to reproduce this on my side. What settings did you add in the Online Power Profiler?

Here is my test with my iBasis (seemingly not getting PSM).

And with my local SIM from Telia

[Willem21]

Øyvind,

I didn't use settings from the Online Power Profiler.

I executed the SDK V2.2.0 example "nrf/samples/nrf9160/udp" with the modifications "CONFIG_NRF_MODEM_LIB_TRACE=y" and "CONFIG_SERIAL=y". And I observed the large average current difference with the video.