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.

CCS/TPS65987D: same peakcurrent setting on the applicaton configuration tool,the the effect different between V5.13 and V6.11

Part Number: TPS65987D

Tool/software: Code Composer Studio

HI,TI's team:

there is a question for the source capabilities(register 0x32) peakcureent setting on FW tool,

they are setting same as(see the below capture) ,but the effect different on OCP.

i am setting 20V/5A,the peakcurrent setting is 150%,

it can enter ocp mode if using the E-load 5.6A after on the V6.1.1 version;

test condition:using the Power-Z PDO meter trig the 20V ,the Vbus connect to E-load directly

but the V5.13 version can't OCP mode if same as test condition(E-load 5.6A after),

it's load above 8A ,didn't enable the protect mechnism.

waiting for 4mins after,enter OTP mode automatcially.

what ae they different? and which version(between V5.13 and V6.1.1) be normal?

BTW:

  about the peakcurrent setting, if setting it (0x32) is 100%,then setting the peakcurrent1(0x77) 300%@20ms@15duty.

are they have any relateship? are they have any help for the PD inrush?

above them,could you help me confirm and add your suggestion?

thanks!

  • Hello,

    The behavior for v6.1.1 is expected behavior and should be used going forward. You can refer to the TPS65987DDH Power Path Performance and Protection App note. Table 1 of this app note shows the different OCP settings, and the tolerance range for the OCP setting. The largest current setting has a range of 5.697A to 6.963A, which the 5.6A load could fall into.

    Hope this helps answer your question.

  • Hi,Gaffin:

     thank your reply quickly.

    your meaning is said ,the behavior is incorrect on  peakcurrent of V5.13 version ,should be 5.6A shutdown if setting Maximum current is 5A.

    hence,the V6.1.1 version is right.

    but i have an other question, if using the V6.1.1 version FW tool,peakcurrent setting 150%,is it can cover some NBs above the inrush 8A?

    becuause some NBs(special the HP brand)inrush can reach to above 9A.

    and we tested their behavior between V5.13 and V6.1.1.

      on same as peakcurrent setting(150%)after,using the V5.13 can support the HP_Elite_850,ohterwise the V6.1.1 doesn't handshake.

    for the 2 kinds version PD FW, could you give us a good suggestion if cover somes NB of HP(inrush above 8A).

    thanks!

  • Hi,Gaffin:

     just now i checked the document" Power Path Performance and Protection",it doesn't described more information on the table1 when setting 5A with peakcurrent 150%. how much is it?

    do you have another talbe for it?

    another:

    from the PD standard,the table 6-10 said,

     " Peak current equals IOC (default)
    or look at extended Source capabilities (send Get_Source_Cap_Extended Message)"

    if cover more NBs of  higer inrush ,can it follow the PD spec setting on our applicatoin configuration tool

      on the register 0x77 setting peakcurrent1 is 300% when the source capabilities setting(0x32) 100% of peakcurrent.

      could you help me check it?

    thanks!

  • Hi,Gaffin:

    above these questions ,do you have any updated?

  • Hello Jianping,

    No there is not other table. Table 1 of the power path app note shows all of the configurable OCP settings. When you program the device to have a current threshold of 150% of 5A, it will put the PD controller into the  5.697A to 6.963A setting highlighted below

    For the inrush current, as long as the current doesn't exceed the hardware current limit of 20A, then your application should be fine.

  • Hi,Gaffin:

     Regarding the inrush issue,thank your explain for me .

    but the peakcurrent, as you show the table,it's for 5V Iocc only, doesn't support  current of higher voltage.

    you can refer the link:

    e2e.ti.com/.../775148.


    in theory ,the value of current is 7.5A(5*1.5=7.5) when i setting the 5A with 150% on application configuration tool.

    but it'sn't show any the value(above 7A) from you show the table.

    could you help me clarify it for the peakcurrent of higher voltage.

    thanks!

     

  • Hello,

    Yes you are correct, apologies for the confusion.

    After confirming with my team, for a 20V contract, if you program a setting of 5A with a 150% tolerance, the trip point will be set to 7.5A.

    Hope this helps answer your question.

  • Hi,Gaffin:

    do you have any updated for the range of peak current (when setting 150% or 130%)?

    meanwhile, i tested the OCP value by Power-Z with E-load, their value same as reach 8A when i setting 130% and 150%.

    like this,what's it  difference betweeen the 130% and 150%?

    PS: this result from V5.13 FW application configuration tool.

    how to choose the setting among the 130% and 150% ? i am very confuse the setting?

    kindly advise you explain it to me or show more document to me study.

    thanks!

  • Hello,

    The functionality from v6.1.1 is correct so please use this version of the tool since it is the latest version.

  • HI,Gaffin:

       i am build in the FW from the V6.1.1 already,test it on our docking ,the OCP point both touch 5.6A when i  setting the peakcurrent 130% and 150%.

    but build in the V5.13's PD FW test after,the OCP point same as touch 8A around when i setting the peakcurrent as upon.

    in this cause,which one Version is correct for the OCP corresponed peakcurrent setting?

    and i hope cover more NBs for inrush ,special the HP brand.

    if the OCP  point is 5.6A only,i am afraid the PD compatibiility .

    hence,kindly hope you provide some comment to me .

    thanks!

  • Hello,

    Apologies for the late reply, have been out of office for business travel.

    You can refer to the following table within the Type-C PD spec for peak current capabilities. The implementation for the latest FW version aligns with the PD spec.

    You can also reference the following E2E post for a more in depth explanation of the table. The relevant sections start around February 7th

    https://e2e.ti.com/support/interface/f/138/t/874161