Hi,
If you read Training_04_sleep_modes_current_measurement_v1.0.pdf file, you can know current consumption is just 1.4uA when sleep mode is extended sleep mode.
And if sleep mode is deep sleep mode, current consumption is 800nA. So, I also measured current consumption with the project is used in above file.
But in my case, i used extended sleep mode and current consumption was 8~9uA.
When i use example that is ble_examples\ble_app_sleepmode, current consumption was 2.5mA~3.3mA...;;
It is same to other projects don't use sleep mode. I did the same process is used in the above pdf file.
I want to know whether my measurement is wrong or not and whether I can get 1.4uA current consumption.
In my project, the power consumption is so important. Plz help me.
Thank you
Hi posljh,
The measurments for extended sleep and deep sleep modes are standard for energy consumption. Please check if you have anything else connected in your board(peripherals), maybe this is the cause of the larger energy consumption. In the case of deep sleep mode did you burn the otp?
Thanks,
STS_Dialog.
Hi,
Did you mean additional connected boards?? I'm using just development kit-pro board only. And I'm doing that with extended sleep mode.
I measured current sleep mode and security example. In the case of sleep mode example, the current was 2.8mA. By the way security example's current was 0.7mA.
I'm finding the differences between these projects. But I don't know the reason yet..;;
I think if ble's state is sleep mode, current should be small and RAM, XTAL(32.468kHz), LDO RET, BLE Timer, wake up timer, quad decoder, PMU are just working.
Is it wrong..?? I don't know why current is so high..;;
你从flash引导吗any chance? I am asking because that would lead to about 2-3mA of current draw.
Hi, MHv_Dialog
Thank you so much:) I solved the problem. By the way are sleep mode & disconnection related??
I want to go sleep mode when I don't use BLE. But, in my experiment, I can get 1.5uA current consumption when I should disconnect.
Then, should I command disconnection from central for low power..?? I think it is strange..;;
Hi,
Sleep mode can be set globally in the SDK (in user_config.h) and the SDK will automatically go into this mode when the following conditions are met:
Before the device goes to sleep, it calculates how many low-power clock cycles it should remain asleep and sets a timer to wake it up for the next scheduled event. This event can be one of your application timers, or it can be an advertising event, or even a connection event. This means that the device can go to sleep inbetween events and still maintain an active connection. With the right connection parameters (connection interval length and slave latency) a connection can be maintained at a very low power consumption. Each connection event (without data - just enough to maintain the conneciton) consumes below 6uC. If you have one connection event every second, this translates into 6uA average on top of the sleep current.
Disconnection can be initiated by both the slave and the master at any time.
To avoid the extra power consumption from your flash, you should make sure that you keep the SPI enable (defaults to P0_3) as an output held logically high - this will reduce the power consumption of the flash dramatically.
/MHv