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.

CC2651R3SIPA: Power Calculator for beacon scenario

Part Number: CC2651R3SIPA
Other Parts Discussed in Thread: ENERGYTRACE

Hi,

This is additional questions to the original post (above link).
My customer wants to know power consumption for below two scenarios.
Scenario a) CC2651R3SIPA receives BLE beacon
Scenario b) CC2651R3SIPA sends beacon with 10sec interval

From the original post, I understood Power Calculator can be used to estimate rough power consumption.
https://www.ti.com/tool/BT-POWER-CALC
But it is not clear how to configure each parameter for each scenario.

Q1)
I guess for scenario a), CC2651R3SIPA acts as Central.
For scenario b), CC2651R3SIPA acts as Peripheral. Correct?

Q2)
For each scenario, how to configure parameters like advertising interval, connection interval, scanning duration/window/interval etc.?

Thanks and regards,
Koichiro Tashiro

  • Hi,

    Q1) This is correct

    Q2) I'll let you review the customer's requirements and fill these elements

    In the end, given the pretty straight forward requirements of the customer, I wonder if it would worth modifying the simple_peripheral and simple_central examples in order to run power measurements using EnergyTrace. These results would be more accurate, and in case the customer also requires support to implement his/her code, you will already have this ready.

    Best regards,

  • Hi Clement,

    Customer first wants to estimate the power with the tool before touching the board.

    I'll let you review the customer's requirements and fill these elements

    Let me ask one more question.
    I guess BLE beacon is connection less, so parameters related to connection (connection interval, connection data length) can be ignored.
    And power consumption of "Connected as Central" and "Connected as Peripheral" are "don't cares", correct?

    Thanks and regards,
    Koichiro Tashiro

  • Hi,

    Of course, if the device is not expected to form a connection, the parameters and values of connection interval, connection data length, power consumption of "Connected as Central" and "Connected as Peripheral" can be ignored.

    In case the beacon never enters a connection, power consumption can be significantly improved by using non-connectable-non-scannable advertisements. That way, the device will skip the listening operations included in each advertisement. The power calculator does not take into account this case and then significantly overestimates the power consumption.

    For these reasons, I recommend you review with the customer if non-connectable-non-scannable advertisements are suitable. Then, you can have a first overestimated power consumption using the power calculator. If this power consumption does not match customer's expectations, actual measurements will be required.

    I hope this will help,

    Best regards,