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.

Bluetooth LE Power consumption

Other Parts Discussed in Thread: CC2564

Hi,

Im using PAN1323ETU module with Stellaris EK-LM4F232 board. I want to evaluate the power consumption of the PAN1323 module using a Bluetooth LE profile. I checked with Bluetopia ANP profile (LE enabled). I have done a Bluetooth LE scan from Nexus 7(Bluetooth 4.0 support) and it showed my device is Bluetooth 4.0 comfortable. I checked power consumption between two pins of J4_2 of PAN1323ETU module. But the power consumption is around 6-10mA range when advertising LE and after connecting with Nexus 7.

I have found that PAN1323ETU used Full-VBAT mode for power supply design. I have changed that to Full-DC2DC mode as shown in http://pideu.panasonic.de/pdf/174Datasheet.pdf. But still the power consumption does not changed. Is there anything i have to do to reduce power consumption of the module?

  • Hi Aruna,

    Sleep is not implemented from the stack in version 1.0 which is available presently for Stellaris. I think this is the reason why you are seeing high power consumption.

    NOTE: Stellaris EK-LM4F232 is no more supported(and Replaced by DK-TM4C123G)

    There is a new release for Tiva C around the corner, sleep is implemented as part of Bluetopia stack.

    But you can download the PAN1323 serves pack(latest 2.12) from http://processors.wiki.ti.com/index.php/CC256x_Downloads  and try.

  • I have noticed that even with eHCILL current consumption can sometimes be higher that expected. It seems that CC2564 wakes up host mcu always when connection event occurs even it does not have anything to send. Could this be fixed so that controller wakes up the host just when it has something to send?

  • Hi Juha,

    Whenever the controller receives an data/event, It will check if the host is awake(if not, sends WAKE_UP_IND),  and sends the data/event to the stack(on host) to process it.

    After processing If there is inactivity for 100 ms (over UART) then it goes back to sleep again(notifying the host with GO_TO_SLEEP_IND).