• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 301 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.

MSP430FR2633: Don't call CAPT_appHandler() for 500ms

rei
Mastermind 6155 points
Part Number: MSP430FR2633

Hi,

My customers want to make CAPT_appHandle () time not to call 500ms due to product specification.

Question:
CAPT_appHandle () should be executed regularly, but is it okay if you don't call 500ms?

Regards,

Rei

  • 0
    TI__Guru 64916 points

    Good question.

    If the delay is needed at power up, the CAPT_appStart() can be delayed until its time to start scanning the sensors.

    If the delay is needed later in the application the simplest method to temporarily halt the scanning is turn off the Captivate timer, then restart it when needed.

    MAP_CAPT_stopTimer();

    MAP_CAPT_clearTimer();

    MAP_CAPT_startTimer();

    Now, customer must understand that while the scanning is delayed the LTA (long term average) filter tracking is temporarily halted.  Since this is primarily used for tracking changes due to temperature, that shouldn't have much impact due to the short length of time.

  • 0 in reply to Dennis Lehman
    Mastermind 6155 points

    Thank you!

    I send this information to my customers.

**Attention** This is a public forum