• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 152 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2642R: Bluetooth forum

Yolande Wang
Prodigy 540 points
Part Number: CC2642R
Other Parts Discussed in Thread: ENERGYTRACE

Hi team，

What are the specific manifestations of entering low-power mode? Customers currently use the simplePeripheral_oad_onchip routine with OAD, enable POWER_SAVING, turn off display, turn off periodic tasks, and turn off broadcasting, but still cannot achieve the power saving state that customers want. A brand new CR2450 battery can only provide power for about 1 month, and the Bluetooth main chip will no longer work properly.

POWER_SAVING is predefined. In this case, should it automatically enter the power saving state when idle? Still need to call sleep() separately?

The customer uses energytrace++ to monitor the power consumption, as shown in the figure below. Could you please explain what these parameters represent?

How can customer determine whether to enter low-power mode through the parameters of these pictures captured?

Thanks & Best regards,

Yolande

  • 0
    TI__Guru* 98060 points

    Hi Yolande,

    Thank you for reaching out.

    The BLEStack is configured to always set the device in the lowest power mode achievable, there is no need for the application to call "sleep" or any similar API.

    I understand the battery life achieved does not meet the expectations.

    The first element I would recommend is to check is the battery life estimated provided by EnergyTrace. Please note, EnergyTrace battery life estimations should always be run without debug mode. See here: https://software-dl.ti.com/simplelink/esd/simplelink_cc13xx_cc26xx_sdk/7.10.02.23/exports/docs/ble5stack/ble_user_guide/html/energy-trace/energy-trace.html#energytrace-stand-alone-instructions

    The second element I would recommend - and has already been checked apparently - is to ensure the device goes in the expected power states. Here, the screen-shots provided shows the device go into low power mode properly. Further analysis of these graphs could be considered to identify if unexpected behavior is noticed.

    The third element I would recommend is to see if Bluetooth configuration (Advertisement interval, advertisement duration, connection interval, etc.) could be changed.

    The last but not lest element to consider is a design review (see https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS). This step is especially recommended if the battery life estimation yield by EnergyTrace is significantly longer than the achieved battery life.

    I hope this will help,

    Bets regards,