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.

CC3000 Average Current Consumption

Expert 2260 points

Hello,

I'm considering using a CC3000 in a low power project and was hoping for some information on the average current the CC3000 when transmitting a data sample, This would involve:

  1. wake from sleep
  2. connect to ap
  3. setup TCP connection
  4. transmit payload ~50 bytes
  5. close TCP connection
  6. sleep

This is, I assume, a fairly typical scenario.

I was consulting the data sheet  and seen the typical and max currents but was more interested in the times the CC3000 would be in each of them modes to calculate the average current required to transmit one sample.

i.e. does anyone have any estimates on how long would it take in the above example to go from step 1 to 6?

Presumably the TX current would only be observed very briefly, but RX current would be observed from startup until TCP session is closed, so the average current wouldn't be that much higher than the typical/max RX current?

I also expect that a UDP connection would reduce the active time by a considerable amount?

  • Hi Alan,

    We cant provide numbers for AP connection and socket setup time because the amount of time to connect to an AP and set up a socket depends on many things not under the control of CC3000. The only number I can give you here besides what you have probably seen on the datasheet is an initialization time of about 60 ms. You could get a cheap MSP430 G-series launchpad and CC3000 Boosterpack if you wanted to characterize your algorithm.

    Regards,

    Aaron

  • Hi Alan,

    I can give you some numbers from observations in my system.  I am not putting the CC3000 in sleep so I can't provide anything for step 1.  Step 2 has been typically taking around 6 seconds in our environment.  I have moved from TCP to UDP and can't remember exactly what it was before but I believe it was on the order of 2 - 4 seconds.  Step 4 is very minor but could depend on the loading on the system.  But typically, it will be much less than 1 second and in the noise of the other times.  Step 5 is very quick - much less than 1 second.  Step 6 - I don't have any data for. 

    For UDP, the biggest time spent in our environment is the binding call which can take up to 3 seconds before the socket can be used.  I don't think there is a large difference in time between TCP and UDP.

     

    Hope this can help some,

    Brent

  • Cheers for the responses guys.I will likely end up purchasing and testing this myself, but was after a ball park figure.