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.

TMP117 sensor NIST registers and unique ID serial number

TMP 117 unique NIST # for example is Presented as Serial Number 0xD6510F8416F1 EEPROM1 contains 0xD651 EEPROM2 contains 0x0F84 EEPROM3 contains 0x16F1 Presented as Serial Number 0xD6510F8416F1 The answer confirms that these are the correct three bytes to include for the complete Serial Number (Unique ID), but it does not confirm that this is the correct Serial Number representation (byte order, endian-ness etc)? If you could provide a reference description for the Serial Number format that would be great, but confirmation of this example's correctness would also be very useful

  • Hi,

    Welcome to E2E and thanks for posting to the sensing forum!

    As mentioned in this post: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1000579/tmp117-tmp117-nist-byte-order-and-eeprom4-address

    "There's no public documentation on the decoding of the ID. We must manually look up the production data associated with the ID. Since this is a manual process, we are only doing it for our internal investigation and quality control. We are not providing any additional information to customers based on their IDs at this time."

    and

    "In a scenario where TI decoded your ID, you would have to tell us the contents of the 3 registers. Therefore, you can store the bytes however you like, as long as you can retrieve the information. I2C, as well as our own datasheet, specifies leading bit as the most significant bit in every frame. Our datasheet also shows that our 16 bit registers are read/written with the most significant 8 bits first. See Figure 7-10."

    Best regards,

    Jesse