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.

TMP102: high byte and low byte update problem check

Part Number: TMP102

Hi, 

My customer is wondering if we will have issue for the updating time. 

Because they had seen that our competitor's part will have sync problem of the high and low byte, which will causing error during reading value from the register. 

Can you help to confirm if TMP102 will have the same problem or not? 

Please help to let us know how TMP102 update the high and low byte.

Thanks for your help.

  • Can you tell me which competitor device has the problem? I'm not sure I understand the problem.

    Thanks,

    Ren

  • Hi Ren, 

    Thanks for your reply, i had send the part number through mail. 

    Let me describe the question for one more time, 

    because there are high byte and low byte of the result register for this part. 

    There is one problem that it may not get both high byte and low byte update before reading the result. 

    And this will cause customer read wrong value some times. 

    So customer would like to know if our TMP102 may have the same problem or not? 

    Or we can make sure that we are able to update both high and low byte before reading the result from the register?

    Let us know if it's not clear enough. 

    Thanks for your help.

    Thanks for your help.

  • Thanks for sending the part number. Unfortunately, the competitor's datasheet does not describe the registers or data format for the device. For this reason, I won't be able to comment on software compatibility with TMP102.

    The 16 bit contents of TMP102's four registers can only be received by performing an I2C read transaction with two read byte frames. See Figure 9 in the datasheet. For this reason, it's not possible for the high and low bytes to be out of sync with one another.

    When EM=0 in the configuration register, the temperature data is in a 12 bit format with the range -55C to 127.9375C shown in Table 2. If only one byte is read while in this mode, that byte will contain the integer temperature without any fractional temperature. This is sufficient for many applications. EM=0 is the default setting on power-up.

    When EM=1 in the configuration register, the temperature data is in a 13 bit format with the range -55C to 150C shown in Table 3. If only one byte is read while in this mode, that byte will contain temperature with 2C LSB size. For this reason, it's not desirable to read only one byte in this mode.

    Thanks,

    Ren