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.

TMP392: After POR, OUTA/B

Part Number: TMP392
Other Parts Discussed in Thread: LMR23630

Hi,

Please give us some advice on the complaints of our customers.

OUT A / B may go low only once after power-on reset. The actual temperature should not have tripped as it will soon become HI.

When the on-board power supply is disconnected from the TMP392 and an external DC power supply is plugged in, OUTA works fine, but OUTB sometimes outputs a Low pulse.

The circuit is below.
SETA / B = 680k

Blue : Power supply 

Pink:  OutA

Yellow: OutB

I'm investigating this error, does TI have any insights?

Best regards,
Hiroshi

  • Hi Hiroshi-San,

    Thank you for your post.

    Does the customer only see this behavior when starting up with the DC Power supply, and never with the onboard power? Are these tests being performed at room temperature? 

    Can you share a bit more of the schematic, specifically I would like to see what OUTA and OUTB are connected to, and what the pullup values are. 

    Also, if possible, can they probe the SETB pin during one of these events?

    Best Regards,
    Brandon Fisher

  • Hi Brandon-san,

    Thank you for your reply.

    LMR23630 is used as the on-board power supply.
    In this case, both OUTA and B frequently output low pulses (only after POR).

    As a result of removing "L1", "R40", and "C27" and using an external power supply to isolate the problem, only OUTB output a low pulse.

    ・ 8 x TMP392
    ・ 8 x OUT A / B is wired OR connection & 10k ohm Pull up

    Therefore, which TMP392 is outputting the pulse? It's difficult to judge.
    Also, since it is not possible to monitor 8 SET Bs at the same time, the customer has started to modify the circuit.

    The results will be posted at a later date.

    Best regards,

    Hiroshi

  • Thank you Hiroshi-San,

    I would suggest checking the tolerance values of the used resistors (1% at room and 100ppm/C over the temperature range) and then taking a measurement of them with an Ohmmeter or digital multi-meter to verify they are compliant. 

    This type of behavior is possible if the resistor values are not being properly decoded at POR. This can happen if the set resistors are outside the 1% tolerance, or if there is significant board noise at startup (please see this thread for reference). 

    Best Regards,
    Brandon Fisher

  • Hi Brandon-san,

    The result of the customer's test using EVM is attached.

    TMP392 EVM .xlsx


    It seems that the noise caused by the power supply is the cause, but customers feel that the noise immunity of this product is weak.

    However, I think it is a very problem that it does not work properly in the environment of the attached file [Test 2].

    If a stronger noise filter is inserted, the probability of starting failure will decrease, but it seems that it will occur depending on the environment even with the configuration of [Test 3]. I don't know when and when the output goes low due to noise, not just at startup.

    [Test 1]-[Test 6] All of them should start normally, but why does it malfunction due to noise?
    Or how to use it? Please let me know if you have any countermeasures.

    Best  regards,

    Hiroshi

  • Hi Hiroshi-San,

    Thank you for sharing the updated data. I am checking with our design team to see if they have any other possible causes. At first glance, it does seem to me like the TMP392 is having trouble decoding the resistor values at startup when under their power supply conditions.

    I will update you here as soon as I have some feedback from our designers on this. 

    Best Regards,
    Brandon Fisher

  • Brandon-san,

    Thank you for your support.

    We look forward to hearing back from you.

    Best Regards,

    Hiroshi

  • Hi Hiroshi-San,

    Thank you for your patience. After checking with our team they agree the most likely cause here has to be the supply noise. In the presence of enough environmental noise you could see the TMP392 trip like this. This is because the TMP392 samples the resistors twice at startup, and pulls down as an indication of an issue when the resistor values it decodes do not match. 

    The best option here would be additional supply filtering (as you've noted). If their power supply performs better under lighter load, or if they have other components generating significant noise, it may also be beneficial to stagger startup of the TMP392 and other components. 

    Best Regards,
    Brandon Fisher

  • HI Brandon-san, TI team,

    Thank you for your review.
    I have reported the results to the customer.

    I would like to close this thread.
    Thank you again.

    Best Regards,

    Hiroshi