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.

TMP461-SP: Can this part constantly stream data?

Part Number: TMP461-SP
Other Parts Discussed in Thread: TMP461

Tool/software:

If this part interfaces to an FPGA, does the FPGA need to actively read the entire time or is there an option for the TMP to have a continuous stream mode so the FPGA can just "receive"?
Does this question make sense?

  • All I2C transactions are initiated by the host controller (formerly master.) While it is possible to have a multi-master implementation, it is not common. The TMP products are target-only (formerly slave-only) devices. This means they cannot act as controller, and cannot initiate I2C transactions on their own. 

    By default, the TMP461-SP makes 16 temperature measurements per second. The most recent temperature result can be queried at any time via I2C. This makes the sensor very easy to use. It is possible to change the rate to save power, or to command the TMP461 into a shutdown mode where it stops making measurements. 

    It is also possible to configure temperature limits that trigger an ALERT or THERM output. These are ways the TMP461 can communicate status without being queried. At the end of every temperature measurement, the sensor will compare the result to the current limits, and assert the ALERT and THERM output pins as appropriate. 

    thanks,

    ren

  • Thanks Ren, however TMP461-SP is smbus protocol, not i2c, correct? It's my understanding these are only compatible below a certain frequency (100kHz).

  • TMP461 supports both I2C and SMBus. My statements apply to both I2C and SMBus. There is a nice summary of the differences in the SMBus spec, if you are interested. https://smbus.org/

    thanks,

    ren