• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 41 subscribers
  • Views 405 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.

Power consumption of typical applications

Rami Friedlander
Prodigy 90 points

Can you provide peak and average power consumption numbers for one or few typical applications?

Thanks in advance,

  • 0
    Expert 1385 points

    Hi Rami,

    The MSP430FRAM DataLogger application is a great example of a low power WiFi solution.  This demo does some data logging to FRAM and then wakes up the CC3000 periodically and sends the data to a host.

    I measured the CC3000 Transmit current around 200mA and the CC3000 shutdown current around 2-3uA. The actual demonstration application idle current is a little over 2mA but this could be reduced significantly.

  • 0 in reply to Mathieu Schneider
    Prodigy 90 points

    Thanks for your prompt feedback.

    I see the current requirements - 200mA durign activ time and 2-3uA during shutdown - thanks!

    Can you also provide the active time that the 200mA was consumed, so that I'll be able to calculate the average power over time?

    Rami

  • 0 in reply to Mathieu Schneider
    Prodigy 90 points

    Thanks for your prompt feedback.

    I see the current requirements - 200mA durign active time and 2-3uA during shutdown - thanks!

    Can you also provide the active time that the 200mA was consumed, so that I'll be able to calculate the average power over time?

    Rami

  • 0 in reply to Rami Friedlander
    Expert 1385 points

    The active time is set with a 2 second software delay.  This is because the UDP packet is not guaranteed to be sent immediately after sending.  I found this delay needs to be longer (2 seconds) for secured networks compared to open (about 1 second).  There are a couple of things that could be done to reduce this time.  One would be to add some handshaking so the client is notified once the server has received the packet, the other is to use TCP instead since it inherently has handshaking.  the send function actually blocks until sent conformation has been made.  There is a third option but I have never tried it; in theory the CC3000 buffers up to 4 UDP messages,  by sending 4 UDP messages the CC3000 will be forced to send the message buffer immediately.   

    Are you just making a general inquiry or do you have a specific application in mind?