• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 456 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC2560 power consumption

Bryan Busacco
Expert 1215 points
Other Parts Discussed in Thread: CC2560

I have a few questions about the CC2560.

 

I am working with a customer caled Sensoron in Buffalo NY. They are making a very low power gas sensor and plan to use the PAN1315 or PAN1325 module.

 

They want to be able to transmit logged data via Bluetooth to a Smartphone/laptop/etc. The key to the application is battery life.

 

We are having issues understanding the power consumption of the CC2560. In looking at TI's website and Panasonic's we can not fully understand the following:

 

1) Wake-up time from sleep

2) Link time

3) transmit power consumption ( we see different values for the two Panasonic modules and do not understand why ).

4) TIme to ramp down and sleep

 

Is this information available?

  • 0
    TI__Mastermind 23565 points

    Hello Bryan,

         The PAN1315 and PAN1325 perform exactly the same from a current consumption point of view. The confusion may come since their specification's tables show some different scenarios e.g. PAN1315 shows full throughput  EDR TX 3-DH1/ RX 3-DH5 and PAN1325 shows full throughput GFSK TX DH1/ RX DH5.

          Regarding Wake-up time, it is in the order of microseconds. For going to sleep time, this can be fragmented in two steps: TX/RX phy go to idle mode first (in microseconds) and then it goes to deep sleep mode (in the order of ms - SW configurable).

          Transmit power consumption values shown above reflect a full data throughput scenario in the specific modulation (GFSK/EDRx) and packet types. However, these values depend on the use case. For example, during a connection in sniff mode (one attempt, 1.28secs), average current consumption will go as low as ~76-100uA.

           Link time is hard to predict. This depends on the environment and also on the peer device. Do you have any requirements?

     

    Regards,