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.

INA226: Need Latency Specification of SMBus Alert of INA226

Part Number: INA226

HI Sirs,

Would you please advise the latency between OCP/OVP event and the INA226 can send SMBus Alert event? ADC's conversion time is not included.

Thank you and Best regards,

Wayne Chen
11/26/2018  

  • Hello Wayne,

    Thanks for using our forum. The latency is contingent upon your master and the SMBus clock rate. Your master needs to recognize that the ALERT pin was pulled low and subsequently broadcast the Alert response slave address, 0001 100. The amount of time your master needs to recognize the ALERT status is based upon the master internal clock, how the master was programmed, and how many clock cycles it takes to execute the necessary commands. Upon your master initiating the ALERT response slave address transmission, the SMBus clock rate will dictate how long it takes before the slave can respond.
  • Thanks for your concern, Patrick. Addition, what is the latency between the OCP or OVP events were determined after data conversation completed and the INA226’s ALERT# signal be asserted?

    Wayne Chen

    11/27/2018

  • Hello Wayne,

    The respective flag for each conversion result is set at the same time the result is updated. Thus it is instant. However, the logic mosfet driving the ALERT pin does have some resistance and capacitance. With those I would expect the decay to 0V would be in the tens of pico-seconds range assuming your board layout does not add a lot of parasitic capacitance in parallel.