Hello,
When an OL (open load) flag is cleared by SPI while the OL condition persists, does it take tOL (open load detection time) to latch a flag again?
Best regards,
Shinichi Yokota
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.
Hello,
When an OL (open load) flag is cleared by SPI while the OL condition persists, does it take tOL (open load detection time) to latch a flag again?
Best regards,
Shinichi Yokota
Hi Yokota-san,
The data sheet says the fault will be cleared when the open load condition is cleared and the clear faults flag is set. I will the verify the open load detection logic is latched until the condition is removed and will reply back shortly.
Regards,
Mike
Yokota-san,
It looks like I was replying as Wang was writing his response :)
He is correct - nFAULT will remain asserted until the OL condition is removed.
Regards,
Mike
Wang-san, Mike-san,
Thanks for your help.
By the way, does the DRV8889-Q1 have an internal delay when an OL condition is removed? If yes, how long is it?
Best regards,
Shinichi Yokota
Mike-san,
If Wang-san's answer is correct, tOL should be inserted for every clear faults command until the OL condition is removed. But, your answer gives me an impression that no tOL will be added for an OL flag. Could you make it clear?
Best regards,
Shinichi Yokota
Hi Yokota-san,
I think Wang's answer may not be completely accurate - I checked directly with the design team and the the fault is not cleared through SPI until the fault condition is removed. This was their exact response: "If CLR_FLT bit is asserted, while the OLD condition still remains, the fault is not cleared. OL flags and nFAULT remain low. Only when the fault condition is removed, the fault is cleared after CLR_FLT is sent. OL flags and nFAULT are released."
Regards,
Mike
Hi Yokota-san,
Your drawing is very helpful! Yes, this is the correct behavior.
Regards,
Mike