• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 79 subscribers
  • Views 643 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Info on Captivate Settings

David J Schmidt
Intellectual 365 points
Other Parts Discussed in Thread: CAPTIVATE-BSWP

My customer is looking at the CapTIvate EVM. They are showing a avg. current of .6uA. This looks to be sleep mode 3.5. When they change conversion count and gain t, they don’t see a significant difference. Can you give me the details for these two settings and let me know what current should be expected when executing a conversion.

 

Note: this is wake on Proximity only.

 

In addition: I was wondering about the relationship of Conversion Count and the Conversion Gain associated with the proximity sensor in the CapTIvate. Changing them doesn't seem to make much difference. I would really appreciate any information you have.

  • 0
    TI__Mastermind 49692 points

    Hi David,

    In the CapTIvate Technology Guide, take a look at Expected Power Consumption table found under Design Guide -> Ultra Low Power -> Expectations. In Wake-on-Proximity mode with 4 buttons, the average current was observed to be 3.0 uA. As you can see for the 4 button configuration, a longer base scan time and higher scan rate increased the average current consumption.

    Lowering the Conversion Count reduces the measurement time. So, the goal should be to minimize the measurement time so that the analog is only enabled for a brief period of time. When the CapTIvate™ analog IP is operational, it draws several 100 uA of current. Read through the Optimization Steps section in the CapTIvate Technology Guide (under the Ultra Low Power section) to see how much power each step lowers.

    For more information about the Conversion Count and Gain, the Glossary section in the CapTIvate Technology Guide talks about both these terms and their relationships in more detail.

    Regards,

    James

    MSP Customer Applications

  • 0 in reply to James Evans
    TI__Mastermind 49692 points

    Hi again David,

    To follow-up, keep in mind that CapTIvate should be used with LPM3, not LPM3.5. If your customer is using LPM3.5, then perhaps this is why a significant change in current consumption was not observed and why only an average current of 0.6 uA was observed (much lower than 3.0 uA average current mentioned above, which may indicate that the analog IP isn't waking up).

    The CAPTIVATE-BSWP project demonstrates the Wake-on-Proximity feature using the CAPTIVATE-BSWP sensing panel, as discussed here. This would be a good starting point for the customer.

    Regards,

    James

    MSP Customer Applications

**Attention** This is a public forum