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.

TMP75: TMP75 Programming

Part Number: TMP75

Dear Team,

Is there any specific procedure to programming the TMP75? At present we have encountered a problem in the test, that is, when the software is doing the foot pin test of the OS, to modify the internal register of the TMP75, first set the temperature point for the Alert to trigger.
However, sometimes it takes two or three times to write Alert to react. What I want to know is, is there a certain program in the order of writing or is it only necessary to set the temperature point to trigger Alert?
At present, TMP75 is known to have only 4 register registers, which are 0x0~0x3, and 0x0 is the current temperature value of Senser, 0x1 is Config, 0x2 is Alert low temperature set point, and 0x3 is Alert high temperature set point.

Alert Trigger Low Setting:

        # write the register 0x2, value 0xD800

        # write the register 0x3, value 0xE200

 

Alert Trigger High Setting:

        # write the register 0x2, value 0x6900

        # write the register 0x3, value 0x6E00

BR

Kevin

  • Hello Kevin,

    There is no particular programming sequence. A write to the appropriate register must take effect. Can you please capture the programming on the I2C bus for the customer units and also capture the read back I2C bus waveforms for us to analyze.

    Is it happening on every device or only some devices behave this way. Schematic, pull up resistor/voltage information would also be helpful in analyzing the issue.