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.

TMP006 Measurement behaviour during FOV Disruption

Other Parts Discussed in Thread: TMP006

The TMP006 evaluation kit and associated software/firmware is exhibiting an instantaneous overshoot reported temperature change from room temp to 40C followed by a slow decay to a new static value of 32C over the course of 5-10 seconds when the Field of View is disrupted with an new temperature object.

This behaviour exists for both continuous and power down modes of operation, and still present with transient operation selected in the GUI.

Is this type of behaviour expected?  Operator error in our setup or usage?

If yes, is there anything that can be done to change the configuration / minimize or filter this out without waiting 10+ seconds for the new steady state to establish?

If no, what is the guidance for configuring / using the TMP006 to avoid this type of system response?

Thank you for any help or suggestions.

  • Hi Clark,

    Does the new temperature object remain in the field of view of the TMP006 for the entire duration of this test? Or is the object placed in the field of view and then removed? The TMP006 is essentially integrating all of the infrared energy within its field of view, although there is a weighting factor depending on where the object falls within the field of view:

    Therefore, any object radiating infrared energy within the field of view will affect the measured temperature, even if it is not the object the part is directly pointed at.