question about the power consumption of nRF52832 in BT connected and advertising mode

[PYC]

the power consumption is about 6.12mW in BT connected, and consumption is about 7.75mW in advertising mode.

is it normal or has possibility to reduce it to extend the battery life?

thanks in advance.

[awneil]

It will depend very much on your settings - connection interval, advertising interval, etc ...

you can explore it with the online Power Profiler:

https://devzone.nordicsemi.com/nordic/power/w/opp

[PYC]

https://devzone.nordicsemi.com/nordic/power/w/opp/2/online-power-profiler-for-ble

excuse me, here is result by our setting, may you review it to see there is any setitng could improve the power consumption?

Thanks.

[Stian Røed Hafskjold]

The file just contains the same default parameters as when you refresh the page. With these settings you can expect an average current consumption of 89 uA in advertising mode. This is very far from the 7.76mW (= 2.6 mA, assuming 3V input) reported consumption. So yes, there should be plenty of room for improvement here to extend the battery life.

[PYC]

yes, the supply voltage is 3V, may i have your suggestion to extend the battery life more?

Thanks in advance.

[PYC]

excuse me, may i have your suggestion to modify the parameter to extend the battery life? Thanks.

[Stian Røed Hafskjold]

Sorry, I don't know anything about your application, so it's hard for me to give any suggestions. You can start out with the ble_app_pwr_profiling example in the SDK, it should compare well with the online power profiler. Use that to verify your measurement setup, custom HW, etc. Then add stuff one by one to figure out where it goes wrong.

[awneil]

PYC said:

may i have your suggestion to modify the parameter to extend the battery life?

Go on - in the online tool, you can just adjust the settings, and see what differences they make!

It's just a simple matter of moving the sliders, and clicking the buttons:

Once you've got a feel for what difference those settings make, you can think about how they impact on your applications performance.

As always, it's going to be a trade-off between performance & power consumption - only you know how that's going to fit with your applications requirements.

[PYC]

Here is the quesiton on EE design, there is one crystal of 32Mhz on EVM board, could we save it, and disable it by internal setting? what is the impact if save the external crystal?

thanks.

[Stian Røed Hafskjold]

You need an external 32MHz crystal to run the radio peripheral.

[PYC]

use external 32MHz crystal could be lower power consumption than use internal, is it correct?thanks.

[awneil]

it's not an option - as Stian Røed Hafskjold said, you need it for the radio to work.

[Stian Røed Hafskjold]

The internal and external clocks are used in two different ways, and not really comparable. The internal clock is started whenever it is needed by the peripherals automatically, e.g. the CPU. It has a very short startup time and cannot be controlled by the application. The external crystal has to be started manually, and will consume current after being started even though it's not actually being used. The startup time is a lot longer, and you will typically not use this unless you need the increased accuracy provided by the crystal, which in fact the radio does. If you just look at the run current for the CPU when running from the external crystal versus the internal clock, it's almost the same.