Current consumption too high while advertising (running the Blinky demo on the nRF52 DK)

RE: Current consumption too high while advertising (running the Blinky demo on the nRF52 DK)

Frederic — Mon, 11 Jun 2018 08:26:23 GMT

This problem is no more a concern. Thanks.

RE: Current consumption too high while advertising (running the Blinky demo on the nRF52 DK)

Stian Røed Hafskjold — Thu, 07 Jun 2018 14:06:28 GMT

Hi, sorry for the late reply. If you post your hex file I can analyze it here to see what consumes current.

RE: Current consumption too high while advertising (running the Blinky demo on the nRF52 DK)

Frederic — Thu, 03 May 2018 08:33:45 GMT

Thanks very much, it works!!! I have now around 2µA, a real low power application.

I have another problem which is very close to the one I have describe here. In my company, we have a product using a nRF51822. I have noticed the same "problems" as with the Blinky app on the nRF52:

- The advertising is, in my opinion, taking too much current, showing pulses of 12mA for the TX (at 0 dbm ?) and 17mA for the RX. My feeling is that the DC-DC has not been turned on (like on the nRF52). Can you give me your feeling?

- The current between two advertising is 36µA. I think it should be between 3 and 4µA. Do you have an idea of what has not been turned off? (Debug log, like the nRF52? something else?...)

Best regards,

Frédéric

RE: Current consumption too high while advertising (running the Blinky demo on the nRF52 DK)

Stian Røed Hafskjold — Wed, 02 May 2018 12:57:41 GMT

Since not everyone are using HW with DCDC components we choose to not enable DCDC by default so that the examples will run on all designs. If DCDC was enabled by default we would get a ton of support cases from people with "bricked" chips ;)

200uA between advertising is probably because of debug logging. Go to sdk_config.h and turn of logging by setting NRF_LOG_ENABLED to 0.

Debug logging is turned on by default in most example applications. In the power profiling example (ble_app_pwr_profiling) logging is not turned on by default because of the power consumption.