I'm learning to use the Asset Tracker V2 example and planning to build a POC product on top the example. The biggest issue at the moment is with power consumption. On the Nordic web pages there are a lot of information on power consumption of different parts of nRF9160 SOC, but I haven't found any real numbers from an actual use case using Thingy:91 HW.
I'm running the following setup:
- Thingy:91, with nRF9160 V1 SOC, modem FW 1.3.0
- Asset Tracker V2 example from nRF Connect SDK 1.6.0
- modified SW to use eDRX with default value ("1001" / 163sek)
- using SUPL for AGPS
- configuration is "Normal" + CONFIG_LED_CONTROL=n copied from low_power_conf
- Device is connected to my own AWS deployment of "Cat Tracker" example
- Device parameters from Cat Tracker: Passive mode, movement res 120sek, movement timeout 3600 sek, GPS timeout 29sek
The modem is configured to use eDRX, because in my earlier test the Thingy logs with default SW requesting PSM got a response -1 from network (DNA / Finland). I assumed the response says no PSM.
My test setup has been running on battery for almost two weeks now and the battery level is currenly at 3.75V. On the first few days the Thingy was actually moving for about an hour per day. The rest of the days it has been standing still inside without GPS signal. I'm expecting that the battery won't last much more than two weeks with this setup.
Questions:
How long one should expect the Thingy can run on battery using default Asset Tracker V2 parameters?
What are the most power hungry parts in the application --> where to start optimizing?
Is the nRF52 part on the Thingy:91 using any power? I have not updated/changed the SW on the nRF52.
