• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 47 subscribers
  • Views 371 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

INA233: INA233

Van Do
Prodigy 10 points
Part Number: INA233

Hi Team Member

What happens to the INA233 when a register overflow condition occurs due to an improperly sized CURRENT_LSB and max expected cuurent?

Regards
Van

  • 0
    TI__Expert 4720 points

    Hello,

    There will be a conversion overflow flag thrown and the result will be the max register number so 0xFFFF if the register is 16 Bits. For your specific circuit it might only be the current register but if you were to also go above the Vshunt max of the part this would also happen in the Vshunt register.

    Regards,

    Cas

  • 0 in reply to Castrense Nigrelli
    Prodigy 10 points

    Thank you Cas.
    When the conversion overflow flag/condition occurs, does it prevent the INA233 from responding to further READ_IIN transactions. We suspect this is happening but we have not been able to capture this instance.

    Regards
    Van

  • 0 in reply to Van Do
    TI__Expert 4720 points

    Hello,

    I am investigating this my first reaction is no. Are you running the device in continuous mode? Could you get an overload condition and then have a known non-overload condition. While reading the current register you will see if it changes.

    Regards,

    Cas

  • 0 in reply to Castrense Nigrelli
    TI__Expert 4720 points

    Hello,

    Are you running the device in continuous mode? Could you get an overload condition and then have a known non-overload condition. While reading the current register you will see if it changes.

    Regards,

    Cas

  • 0 in reply to Castrense Nigrelli
    Prodigy 10 points

    Hi Cas
    We troubleshoot more and discovered that the overload condition does not lock up the INA233. The apparent lock-up appears to be our host.
    In our case, the host is using an I2C controller/driver to talk to the INA233. In the case of glitches on the SCL lines, the host became confused and did not shift SCLs correctly in read transcations. The host was essentially sending read transactions with 0 bytes. To the host driver it looked like the INA233 was unresponsive but it was actually the host that somehow became confused.

    Regards

  • 0 in reply to Van Do
    TI__Expert 4720 points

    Okay thank you for the feedback. Glad you found the problem.

    Regards,

    Cas