This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CC2640R2F: Simple broadcaster power consumption problem

Part Number: CC2640R2F

Tool/software: Code Composer Studio

Hi, 

We have a custom beacon using CC2640R2F with a problem of power consumption:

- The project is based on SimpleBroadcaster example

- Uses internal RSOSC_LF (no LF xtal on board)

- CR2032 battery

- We have made a test of 40 units with advertising period of 100ms and the battery lasts >50 days (above the expected)

- We have 500 units of our product out in the field with advertising period of 3000ms. Some units are draining the battery in a much shorter time than expected:

1. The first units with an empty battery appear after ONLY 40 days of use (SHORTER THAN 100ms period!!!!)

2. After 4 months, 20% of units have an empty battery

3. The unit with the longest duration is now 11 months and still running (the theoretical expected time is 4 years)

Is it possible that some PCBs are not entering the sleep mode correctly? could it be related to the 3000ms period?  Could you give us any inputs to solve this problem?

Best Regards,

Carlos Flores

  • Hello Carlos,

    Have you measured the actual current consumption on these units according to the procedures listed in app note SWRA478? That would be a good first order debug step.

    Also, have you characterized the actual capacity of your CR2032 batteries? We have heard of some "economically sourced" batteries not having the nominal 230 mAh capacity, so this is one item to check.

    Do you have other components on the board that consume current?

    Best wishes 

  • Hi JXS,

    We have been analyzing this problem for some months now. We carried the measurements and they were as expected. The batteries used were Duracell on the beggining and now we are using Maxwell. There are no more components consuming on the PCB. 

    The most relevant data is: with same hardware, same firmware, same battery at 100ms period we get >50 days on all 40 units testing. Just changing the period to 3000ms we find some of them have an empty battery in <40 days.

    We have a demand for the next 1000 units batch but we are can't produce it until we solve the problem. How you would advise us to proceed?

    Best Regards,

  • Hi Carlos,

    Without any quantitative data it's difficult for me to provide any specific guidance. I suggest taking one of your 3000ms devices that is showing unexpected battery depletion and measuring the current consumption in accordance to the procedure in app note SWRA478. Perhaps there are unexpected leakages or MCU wake ups - this would all be evident with a proper power analysis.

    Best wishes