• State
  • Replies 3 replies
  • Subscribers 80 subscribers
  • Views 106 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSP430FR2633: Captivate calibration data lost?

Viktor Schneigelberger
Intellectual 1310 points

Part Number: MSP430FR2633

Hello,

We observed an issue with our design using MSP430FR2633IRHB. The system contains two identical touch controller units (handle) that have the same error. Included is an MSP430FR2633IRHB in each handle - If the handle is touched, it functions briefly (a few seconds) - Then the handle will not work for about 30 seconds. - After that, the handle works as expected. The error always occurs when the device is not being operated for a long time (several days) and so far only on 1 out of 100 units.

The microcontrollers are in LPM4 mode when they are not operated. Any clues to what error could be present here are appriciated.

Can the MSP430FR2633IRHB lose the CapTIvate settings in LPM4 mode when not being used for an extended period of time, so the capTIvate unit would have to recalibrate itself when it wakes up, which could take 30 seconds?

How does calibration work? Can the capTIvate unit calibrate in LPM4/LPM3 mode or does it need to switch to active mode? Would the change take place automatically from time to time? How long does the calibration take? 

 

Regards,

  • 0
    TI__Mastermind 40135 points

    Can you try to reduce the wakeup interval? The captouch will wake up and track the environment change after certain proximity scan times. If it is too long, the environment track will not be very good.

    Please also check if you can log the data. Than we can give more deaper analysis.

  • 0
    Prodigy 10 points

    The design is very energy-sensitive. The board needs to operate for approximately 7 to 10 years on a single lithium battery. Therefore, we must keep it in LPM4 mode for as long as possible. The microcontroller should not switch to active mode without any user input. Normally, there are one or more user actions every day. However, in this specific error case, user actions are very rare (> 10 days).

    Unfortunately, data logging is not possible.

  • 0 in reply to Erwin Hirtreiter
    TI__Mastermind 40135 points

    Hi Erwin,

    OK. It seems that the problem is hard to recreate. Another method is to record the calibration times in FRAM. Than that can give us some information if this issue is related to calibration. 

**Attention** This is a public forum