• State Verified Answer
  • Replies 2 replies
  • Subscribers 73 subscribers
  • Views 1524 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 125261
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Estimating the battery life with NRF51-1822

pavan

Estimate battery life for FOB CR 2032 -240 mAh

We are developing remote with CR2032 battery and using Nordic nrf51-1822 BLE, 960 m sec connection interval, RX 1 packet per interval, TX 1 packet per interval, 16 bytes per packet (includes base current +radio RX + radio TX + 16MHz crystal startup and run current + RTC + 32 kHz crystal) by consider smart mode ,

consider the Smart Mode, Smart mode uses advanced adaptive algorithms to automatically optimize power usage. If there is no one around, remote with Smart Mode enabled will broadcast data less often, to save battery. When a user appears in range, the remote will go back to broadcasting at a normal rate, defined by its Advertising Interval setting.

Can anybody suggest for finding current consumption to calculate the battery life ?

Parents
  • 0

    Well with batter life estimations it's usually very inaccurate to predict. I would say don't waste your time on computing because you don't have any clue what are real consumption values of your specific HW, what is battery leakage etc. If you want to blindly use values from data sheets then you can be off by 50% or more without knowing it (then you build the thing and cry or need to explain to the rest of the team why you were so off).

    The best way (also from the perspective of your time and effort) is to simply implement PoC FWs on two boards and measure it. That will give you very good understanding how close or far are you from your target (which typically is one billion years on single coin cell battery, right?) and if you won't be satisfied (which is very likely;) you will again need to go back to HW an FW design to solve it. So these mock up computations on the back of the envelope won't really help you (that's my experience).

Reply
  • 0

    Well with batter life estimations it's usually very inaccurate to predict. I would say don't waste your time on computing because you don't have any clue what are real consumption values of your specific HW, what is battery leakage etc. If you want to blindly use values from data sheets then you can be off by 50% or more without knowing it (then you build the thing and cry or need to explain to the rest of the team why you were so off).

    The best way (also from the perspective of your time and effort) is to simply implement PoC FWs on two boards and measure it. That will give you very good understanding how close or far are you from your target (which typically is one billion years on single coin cell battery, right?) and if you won't be satisfied (which is very likely;) you will again need to go back to HW an FW design to solve it. So these mock up computations on the back of the envelope won't really help you (that's my experience).

Children
No Data
Related
Terms of service