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.

TS5A3166-Q1: IN pin input leakage measurement higher than spec

Part Number: TS5A3166-Q1

Hi Experts

I am trying to verify the Input leakage current spec in the datasheet. 

I am applying 5.5V to the V+ supply pin and then sending +5.5V and/or 0V to IN (pin 4). 

I see leakage of 89nA at V_IN = 5.5V, and 123nA with V_IN = 0V.

Can someone provide guidance on why I see these results or how to measure this more accurately?

Thanks in advance for your help.

Best regards,

Jim B

  • Hello Jim,

    1.I wanted to ask if you what is your setup for the leakage current test?

    2.Also what measurement tool are you using for this test?

    Let me contact our validation team to see how we measure very precise leakage currents like your are seeing.

    Please respond at your earliest convince!

    Regards,

    Kameron

  • Hi Kameron

    Please let me know if you have more details on how the validation team measure this parameter.

    Our setup is all pin NO, COM, INPUT and Vcc pin connected to BNC connectors on PCB.

    We used Keysight B2912A precision source/measurement unit to test leakage current.

    For input leakage current, we connected output of this equipment to INPUT pin of the device.

    Thanks for your help.

    Best regards,

    Jim B

  • Ok  Jim will update this forum soon with more info!

  • Hello Jim,

    I have an update for you on this issue. After talking with the validation team here is what I found.

    This issue you are seeing could be setup related and also board related. The validation team uses boards that are made to have less parasitic leakage.

    One thing you could do is take the same measurement with out the unit and do an open socket calibration of your setup. Basically you do the same test with and without the device and the delta in the measurement is what is actually caused by the device.

    Regards