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: disable ALERT pin react to OC/OV/OP/UV warning/fault

Part Number: INA233

Hi team,

My customer is attempting to block ALERT pin react towards OC/OV/OP/UV condition. I saw the thread https://e2e.ti.com/support/amplifiers-group/amplifiers/f/amplifiers-forum/710174/ina233-over-current-limit-alert-pin-always-low. We wrote Reg_0xD2h = 0x6F, but it was always read back as default 0xF0. It seems the write to this register address was not successful, but we can write other registers successfully. Could you pls show me how to disable ALERT pin?

Thanks.

  • Hello Jerry,

    That is odd... I believe you are doing it correctly....  Can you please send a scope shot of you writing the register 0xD2 with 0x6F followed by a scope shot of you reading register 0xD2.  In between the write and read, make sure that the device remains powered on, and monitor the scope to make sure that no other registers are written to or read from.

  • Hi Mitch,

    Customer would like to freely disable and re-enable alert pin action after power-on. Now, we can disable ALERT at the first time by writing Reg_0xD2=0x9F. But after that when we set Reg_0xD2=0x90 to re-enable it, the ALERT action doesn't act according to the register setting. How to handle the 4 MSB of this register (0xD2[7:4]) properly?  I saw there is error in datasheet in below answer.

    Thanks.

    https://e2e.ti.com/support/amplifiers-group/amplifiers/f/amplifiers-forum/710174/ina233-over-current-limit-alert-pin-always-low 

  • Hello Jerry,

    So writing 0x6F is working now? I believe writing 0x90 should work as well.  Maybe 0x90 isn't working for the same reason 0x6F wasn't working? Meaning, maybe there is a problem with the communication or something.  When you read the register back, do you see 0xF0? If not, you could try writing 0xF0, but that shouldn't be necessary. If the register reads back what you expect, then it should behave properly.

  • Hello Jerry,

    It's been a while since you replied so I'm going to guess that you got this figured out and presume that it was a communication error or similar. I'll mark this thread as resolved, but feel free to reply if you have any more questions.