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.

Another CC3000 startup question

Other Parts Discussed in Thread: CC3000

A customer uses a competitors module in a battery application that transmits very little data.  Key for the application is low power.  To achieve low power they only apply power to the module when they want to transmit data; from power on (this is just the module), connect to the network, transmit the data (maybe 10 bytes?), to power down takes about 2 seconds.  Any idea what the CC3000 can do?  Another option might be to leave the CC3000 in low power standby and do the same thing from there, any idea how long that would take?

  • Hi Terry,

    CC3000 is a perfect fit for this use case. The CC3000 module have an ultra low leakage switch that can be controlled from the microcontroller in the system. With that switch turned off the module current consumption goes below 5uA. Turning off the module after data transmit can be really quick. We did not measure the turn-off time but I expect it to be in the order of magnitude of milliseconds.

    Do you how often do they transmit data and what is the battery that they are using? If you send out this info we can help you estimate the battery life.



  • Our use case is 10 transmissions every 24 hours.

    We normally use a CR123 lithium battery with 1500Mah capacity.

    We try to get at least 3 years of operation with this configuration.







  •  Greg,

    With 10 short transmissions every 24 hours CC3000 is not going to be the dominate factor in battery lifetime. Other components in the system will.

    The CC3000 power consumption alone for this use case allows way over 10 years of opperation with 1500mAh. The major contributor for the energy consumption is the shut down leakage which is very low.



  • Hi Greg, 

    As Gil said, the CC3000 is a perfect solution for you. The init sequence is very fast, so the CC3000 will be off most of the time.

    Another cool feature the CC3000 has is the fast-connection: where once the CC3000 had a connection, it's memorize the AP connection details, so next connection will be very very fast - The CC3000 just send "Auth" packets without doing any scan. 

    Using the fast-connection setting at power up sequence, can shorten the duration of the ON mode, so the power consumption will be as little as possible.

    - Elad.

  • Gil, Elad,

    This is very valuable information. Will you be able to specify the power sonsumption for each transmission of the CC3000, using the above assumptions of very short data transmission and "fast connection" mode?


    Thanks, Rami

  • Rami,

    Each transmission, including wakeup and connection will consume about 3.6 uAh from the battery.

    With Battery capacity of 1500mAh you can do ~400,000 transmissions (excluding leakage current). With leakage current of 5uA, you need to solve for the battery life time given the freqeuncy of the transmissions. For the use case described in this thread, the transmissions are so rare that the leakage current becomes the main factor. If you are transmitting once a minute, the leakage current and the transmission have similar contribution to battery life, which becomes around 280 days.




  • Thanks Gil. This is really helpful information!

  • Hi Gil, 

    Do you have a spreadsheet available for us to estimate the battery life for the cc3000 for changing the transmission rates, power levels, leakage currents?


  • Sorry Ben, we don't have a spreadsheet availble yet. Please look at the power consumption numbers in the module data sheet.

    Power consumption changes between 11b and 11g. This is covered in the module data sheet as well as the leakage current. Transmit power level within the 11b and 11g rates does not impact power consumption.



  • Hi Gil, 

    Could you provide the link to the module datasheet(s)?  When I go to the wiki, I am only getting the 1 page datasheet briefing not the fully datasheet for the module.  

    Another question, I would like to get access to the SPI commands setting to program the cc3000 but I can't find it on the wiki.  Could you provide that link?


  • Ben,

    Murata and LSR each have their own datasheets:

    Please note that there are no SPI commands to program the MSP430. All CC3000 configuration is done through the host driver that is provided. Are you looking to do something specific?


  • Gustavo,

    I am looking for the SPI register definition of the cc3000.  As I would like to modify the tx data rate, power level, sensitivity, modulation, etc.. to better optimize battery life.  


  • Hi Ben,

    This API is not exported and not implemented in the chip.

    - Elad.

  • Hi Assaf,

    1. Elad took the ( (init time * init power consumption) + (Tx time * Tx power consumption) + (Rx time * Rx power consumption) ) / 3600sec = number of uAH

    2. Listen power consumption is 70mA

    3. Receive is 85 mA and transmit is 170mA, For that you need to:
      3.1 Add TCP\IP headers + WLAN header + Phy headers
      3.2 Know\Guess which transmit\receive rate you are using most commonly.
      3.3 calculate the time it takes to transmit\receive the data including headers in these rates.

    4. The wake up time + connection time, takes ~850ms, for the amount of data you are sending (very small) it looks like it would be better for you to shut down the CC3000 and wake up every time you want to transmit & receive.
    Please note that longer the shut down times are the more battery power you will save.


  • Hi Assaf,

    1. My numbers are less accurate than the ones supplied to you by muRata. Please use the ones from muRata.

    2. The overhead for TCP Rx\Tx is approximately 66 Bytes.


  • Hello Alon,

    I can't find in the datasheet (from either Murata or LS) a mode called "listen" as you mentioned in your answer. Where can I find this? My customer has an application that requires the radio to listen 99.9% of the time for a request to Tx.

    I am also searching for a clever way to consume as little as possible while listening. If you have additional pointers besides what was discussed in this post, please let me know. The 70mA you mentioned above for the listen mode is still way too high for my customer's application.

    Thanks a bunch

  • Hi Gil,

    I have similar question:

    the standby power drain is small (<5uA), but it's still considerable comparing with the less than 1uA standby drain of the MS430FR5969. (wifi is only needed once a day)

    May I just simply turn off the VBAT when the wifi is not needed? Do you know which power switch chip has the very small leak current (<1uA)? Thanks.

  • Hi, 

    I also need to estimate battery life time of my product. Even though I have been through the post multiple times, i am bit lost. To avoid burdening the reader(community member who want to help me), here I am quoting some reference  numbers  again to help me. I hope this reference example will be helpful to others as well

    1) Our product need to be in listen mode for most of the time as our product gets perioidc requests (tx packets from other module). So please assume our device is in listen mode through out day

    2) Once it recieves say 50 Byte data packets , it then responds to it by transmitting back again 50 Byte data packet.

    3) For simplicity, I can say our device receives requests 20 times a day.

    So technically our product receive 20 times , 50 Byte data packet and our product responds to it by transmitting again 50Byte data packet.

    4) Assume I use 110mAH LiPo battery.

    5) Also assume I am using TI CC3000 module. TI module spec says  200mA consumption in TX mode and 100mA in RX mode.

    Please consider best possible scenario in giving  rough estimation of battery life time ( sleep mode, fast connection and always in listening mode).

    Appreciate your comments in responding to this query.

    THank you.