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.

TPL5110: M_DRV Reset Time Interval

Expert 6030 points
Part Number: TPL5110

Team,

Quick confirmation question for TPL5110.  If a manual power ON is issued while the DRV line is already low, is the counter reset?  The datasheet says this signal is ignored, but it was unclear if the counter is reset in this situation.  In other words, can the timer be extended if a manual power ON is issued during the DRV low time?

Thanks,

Phil 

  • Hi Phil,

    The timer is not reset if the manual power ON is issued when the line is already low. Refer to figure 11 of the datasheet, reproduced here:

    The blue outlined box shows a valid M_DRV pulse- in this case the timer is reset and time interval TIP restarts after TDB.

    The red outlined box shows the case where M_DRV is ignored since DRV is already low. In this case the timer (and the time interval TIP) is not reset.

    Regards,

    -Tim

  • Hi Tim,

    Thanks for the response! Per our discussion, this thread made me question whether or not the counter gets reset:

    e2e.ti.com/.../1492876

    Let me know when you confirm on the EVM so we can close this out.

    Thanks!

    Phil
  • Hi Phil,

    I tested this on an EVM and I was correct- M_DRV does not reset the timer when it is ignored.

    There is another way to extend the DRV cycle. In section 8.5.2.1 of the datasheet, it states ‘An extended assertion of a logic HIGH at the DELAY/M_DRV pin will turn on the MOSFET for a time longer than the programmed time interval.’ Essentially, if you pull M_DRV high for a while, it will roughly extend the DRV cycle by however long you hold it, since the timer interval only resets after the M_DRV goes back low. This could be one way to extend the cycle, but it would require knowing in advance that the cycle needs to be extended- you can’t let M_DRV go low, then decide that the interval needs to be longer and try to pull M_DRV high again to do so since it would be ignored.

    Regards,
    -Tim