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.

Compiler/TMP102-Q1: TMP102-Q1 Interrupt is not getting generated for T(low)

Part Number: TMP102-Q1

Tool/software: TI C/C++ Compiler

Hi,

In our custom design we are using TMP102-Q1 temperature sensor for measuring the ambient temperature, which is interfaced to the SPC560B50L1 microcontroller through I2C. I have successfully configured the temperature sensor in the interrupt mode. The conversion of temperature is working fine. But I am facing trouble in getting the ALERT at the threshold levels.

Consider the threshold values as T(low) = 20 *C and T(high) = 60 *C. The ambient temperature while starting the board is (say) 37 *C.

step:1 Now I am trying to decrease the room temperature to 20* C and below. The sensor appropriately reads and converts the exact temperature which I confirmed by reading the temperature register. But the problem is there is NO interrupt alert has generated even after the configured number of faults.

Step:2 However, if I try to increase the temperature 60*c and above the interrupt alert has successfully occurred after configured number of faults of T(high) and then ALERT pin has cleared after register read since configured in interrupt mode.

Step:3 Once the T(high) interrupt has occurred and alert pin has got cleared after the register read, then if I again try to decrease the temperature below T(low) I can I see there is an interrupt ALERT for T(low).

So, the problem in brief is, T(low) interrupt will occur if and only if the T(high) interrupt has occurred earlier.

Pictorially the only working scenario is

T(High)->T(Low)->T(High)->T(Low)-> and so on....

Facing trouble in the below scenarios

T(Low)->T(High)->T(Low)->T(High)-> and so on....

T(High)->T(High)->T(High)->T(High)-> and so on....

T(Low)->T(Low)->T(Low)->T(Low)-> and so on...

someone please help me in overcoming the issue.

Thanks and Regards,

R.Santhamurthy