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.

CC3220: Clarification about "power consumption App report - SWRA502A (Feb 2018)" and AA vs AAA battery consideration?

Part Number: CC3220

Team,

I am looking at the SWRA502A application report from Feb 2018:
http://www.ti.com/product/CC3220/technicaldocuments#doctype1
Could you please clarify the below:

Page 20: Fig 1-3 seems just for illustration as there is no color code.
-What is the amount of data exchanged in E4 (ie application traffic) for this use case?
-Is the TX power consumption of table 1-6 page 18 taken into account in the use case?

Page 21:
-From the Energy consumption point of view, in the scenario of using 1 single AAA (1.5V @ 1000mAh), is the formula still valid?
Of course a DCDC Boost converter will be needed to provide a valid VBAT/VIO.
-If I take a cycle time of 15 minutes this would give:
1.5*1000*15/0.044/400 = 1278 days
But I guess that section "1.1.9 Battery Powered System Considerations" is only valid for AA and using AAA would induce some limitation.
Have we done some tests with AA?
What would be a realistic lifetime when using 1 single AAA battery for section 1.1.10.1 Intermittently Connected Test Case?

Page 20: section 1.1.10.1 Intermittently Connected Test Case mentions CC3120. Would would be the influence of using CC3220?
What consumption would be added for running a basic application on the MCU?

Thanks in advance,

Anthony

  • Hi Anthony,

    The test cases described in the application report are taken from the power_measurement example in the SDK. The illustration and the power consumption calculations are done while that example app is running in the specified test mode, and provide a benchmark of what sort of power consumption to expect in each test case. While each test case is modeled off of typical usage patterns, a specific application which transmits more data or sleeps longer etc. will alter the measured power.

    For the intermittently connected case described on page 20, the application will transmit one packet with size 1000B during E4. After that, it spends 5s in E5, the hibernate state. As the application and network processor is active in E4, you can transmit as much as 2MB in a second. However, in the test case illustrated, E4 lasts much shorter than 1s.

    If you have a specific use case in mind, I suggest you modify the power_measurement example to match your test case and then measure the power consumption used while running your modified example.

    Regards,
    Michael
  • Michael,

    Thanks for the answer. It helped to understand better.

    Regarding one of my previous questions:
    Page 21:
    -From the Energy consumption point of view, in the scenario of using 1 single AAA (1.5V @ 1000mAh), is the formula still valid?
    Of course a DCDC Boost converter will be needed to provide a valid VBAT/VIO.
    -If I take a cycle time of 15 minutes this would give:
    1.5*1000*15/0.044/400 = 1278 days
    But I guess that section "1.1.9 Battery Powered System Considerations" is only valid for AA and using AAA would induce some limitation.
    Have we done some tests with AA?
    What would be a realistic lifetime when using 1 single AAA battery for section 1.1.10.1 Intermittently Connected Test Case?
    Any input you could provide about this?

    Thanks in advance,

    A.

  • Hi Anthony,

    The assumptions for the typical average current draw in the intermittently-connected case estimate that 0.044J is consumed during each cycle. The equation you solved to get you 1278 days lifetime seems correct to me.

    The only limitation with AA vs AAA is, how much current can your AAA battery output? For the CC3220, typical wifi TX requires ~270mA, while the peak calibration current can be up to 450mA at Vin = 3.3V. Assuming that you have a capacitor which can provide the required energy when needed, then it should be possible to use the AAA battery.

    Regards,
    Michael