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.

  • Resolved

INA260: AD conversion time and averaging

Prodigy 40 points

Replies: 3

Views: 50

Part Number: INA260

I wrote 62DDh to Configuration Register (00h) (4 times average, conversion time 588us, shunt current mode) and I wrote 0640h to Alert Limit Register (set threshold to 2.0A).
Then, a constant current of 2.1A is applied to verify current detection.
After passing a constant current of 2.1A, the Alert pin falls to L in about 1ms, but since it is an average of 4 times, it will take more time than 588us ✕ 4 = 2.352ms.
Why is it detected earlier than expected?
  • Hi,

    The Alert comparison is made after every single conversion. Therefore if the first conversion produces a result that is over the threshold, then the Alert is flagged. See below timing diagram showing when such comparison is made regardless of a large number of averaging samples:

    Regards, Guang

  • In reply to Guang Zhou:

    Hi.
    Thank you for your reply.

    Is it true that the Alert is not compared to the averaged data, but is output the moment the threshold is exceeded?

    Does the averaged data role as read data? (Is it a function used in measuring instruments, etc.)

  • In reply to user5812606:

    Hi,

    The comparison is made every time when a conversion completes. The average value is returned as the final value and not used in the comparison, nor is it used in any other measurement.

    Regards, Guang

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.