TLIN1029A-Q1: Operation in UV_sup<Vsup<Vsup(recommend)

Part Number: TLIN1029A-Q1

Hello team,

My customer would like to check two things in below Vsup situation. Could you check and feedback to them please?

a. Undifined area: UVsup(Max, 3.85V)<Vsup<Vsup(min, 4V), EN=high

  1. Is there possibility for unexpected data communication?
  2. Is there possibility for IC damage or current comsumption increase?

b. UVLO area: Vsup<UVsup(min, 2.9V), EN=high

  1. Is there possibility for unexpected data communication?(same question above)
  2. Is there possibility for IC damage or current comsumption increase?(same question above)

Regards,

Youhei MIYAOKA

  • Hi Youhei,

    Communication is mainly guaranteed when within the recommended operating conditions.

    Hence, there is a possibility for unexpected communication when outside the recommended conditions. However, damage is not expected (expected only when above the abs max rating). Furthermore, the UV conditions specified are mainly guarantying the min and max thresholds that the UV should trigger. However, would recommend to ensure you are within the recommended conditions for proper communication, thanks. 

    Best Regards,

    Michael. 

  • Hello Michael,

    Thank you. Can you support additional questions from customer?

    Is there a mode that forces the bus line to go recessive (bus line stuck high)?
    If so, is there any risk to go into the above mode due to power fluctuations?

    Regards,

    Youhei

  • Hi Youhei,

    No, there should not be a mode that forces LIN high. However, LIN may be high in any mode due to external pull-ups that may be used and if the power supply drops below the UV thresholds, then the device should be in an unpowered state as shown in figure 9-4.

    Hence, customer may double confirm which case below is applicable if they are observing a bus stuck high (recessive) after a power disturbance.

    • UV falling below the undervoltage threshold.
    • The device remaining in Sleep or Standby mode due to the control pins.
    • The MCU not asserting TXD because it has reset or entered a fault state.
    • The transmitter being disabled by the TXD dominant timeout after TXD was held low too long, thanks.

    Best Regards,

    Michael.