Hi
I ran the example " ble_app_hrs ". the consumption is 1.5mA, when I hold SWCLK and nRESET low,the consumption is fall to 0.9mA. how I could reduce the consumpion??
Hi
I ran the example " ble_app_hrs ". the consumption is 1.5mA, when I hold SWCLK and nRESET low,the consumption is fall to 0.9mA. how I could reduce the consumpion??
Hi
I suggest you lookt at these threads, thread 1, thread 2,thread 3.This thread also contains low frequency clock guide. This thread might also be helpful. Hopefully that will make it more clear what to do. The first thread is the most relevant.
Just to point out. The nAN-36 application note on our web site is a good starting point to get to know BLE and our nRF51 SDK. The nrf51-ble-app-lbs is also available for nRF51 SDK 5.2.0 here.
Hi:
I want to know whether the 1.5mA is correct ? By those ways, the consumption reduce a little bit.
Hi
After programming the chip you need to power cycle the chip to get it to normal mode. Pin reset will not do the job. After you flash it it will stay in debug mode.
I do not remember what the current consumption is in the heart rate example exactly. It depends on the connection interval. When are you measuring the current? If you connect with Master Control Panel, the connection interval will start off with 20ms, as this is the default setting in the MCP. After a few seconds, there will be connection parameter update request sent from nRF51 to the central (MCP in this case) to request a connection interval of 500ms. With the new connection interval current consumption is drastically redused. 0.9mA sounds a bit high for 500ms connecton interval, but could be normal for 20ms connection interval.
Furthermore, the documentation for the example states that it is not power optimized , as described here:
http://devzone.nordicsemi.com/documentation/nrf51/5.2.0/html/a00074.html#project_hrs_intro
Well actually, the heart rate example for the development kit is not power optimized, but the heart rate example for the evaluation kit is power optimized, [url=http://devzone.nordicsemi.com/documentation/nrf51/5.2.0/html/a00075.html]see here[/url]
As the documentation states, the difference lies in compiler optimization. When you have the compiler optimization on, the example will have the lowest current consumption. When the compiler optimization is off, you will be able to debug.