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.

LDC1000: Step function response over temperature

Part Number: LDC1000

Hi,

I've recently inherited a design based on the LDC1000. Two queries.

Readings of the proximity data registers are highly sensitive to temperature. I understand this is due to the inherent temp co of our PCB based sensor winding.

As the temperature rises the LDC1000 responds in steps. Say I heat the equipment from 25degC to 30degC the proximity data increases roughly linearly with temperature, as I continue to heat it to 38degC the proximity data is stuck at 4764, then it rises linearly for a while then it gets stuck at 4992. Is this due to the LDC1000's operation ? The data sheet and the various application notes don't explain how precisely the external circuit is excited or measured by the LDC1000.

Secondly, we use LDC1000 TSSOP16 to measure RP (rather than inductance), it is going obsolete. Is there a drop in replacement ?

 

Regards

Richard

  • Hi Richard,

    Can you clarify how long the data is stuck at a single value? Just in case you haven't seen it, we do have an application note about temperature compensation with the LDC10xx devices: http://www.ti.com/lit/an/snaa212a/snaa212a.pdf

    We do have a drop-in replacement for the LDC1000, which is the LDC1001. The key difference is that the LDC1001 cannot drive an external crystal and needs an external clock input for L sensing. This does not affect Rp sensing at all, so you do not need to change your design. However, please note that we have many newer LDC devices in our portfolio that may be suitable for your application. These newer devices are higher resolution and lower power. I recommend looking through the LDC Device Selection Guide if you can still make changes to the part selection in your design.

    Best Regards,

  • Hi Kristin,

    Attached is an Excel spreadsheet which shows the response I describe. The x-axis is temperature in degC, recorded over a long duration while the equipment warms up. The y-axis is the proximity data value. There are 32 sensors connected to one LDC1000 by analogue mutiplexers. All sensor positions are empty, i.e. no targets are present. 

    The AppNote doesn't explain the plateaus in the response.

    Changing to LDC1001 has the least impact on the existing design. What’s its YTEOL ?

    Regards

    Richard

    /cfs-file/__key/communityserver-discussions-components-files/1023/variation-avec-temperature-TI.xlsx

  • Hi Richard,

    What are your RP_MIN and RP_MAX values? I'd like to look at the data in terms of actual resistance compared to the LSB resistance value.

    If you look at the Rs across temperature graph in the application note I shared, our data points are all ~20 degrees C apart. You have a much finer scale on your graph, and I wonder if it would look similar to our graph if you looked at a larger temperature step. 

    Do you see similar steps when you measure the Rp response versus target distance?

    We have no plans to EOL the LDC1001. You can find our EOL policy here: http://www.ti.com/support-quality/quality-policies-procedures/product-life-cycle.html

    Best Regards,

  • Hi Kristin,

    Rp response v distance.xlsx

    Apologies for my delayed response, I was side tracked onto another project. 

    RP_MIN=19h , RP_MAX=3Fh

    Yes, the Rp response versus target distance has a similar response with steps.

    I’ve done an experiment to show this. Please see the attached spreadsheet, in particular the second chart. Basically column A is distance, column N is proximity data. As a target is moved away from the sensor there are apparent steps in the proximity data values, at the same absolute values as the previous test over temperature. If proximity data is the output from an ADC why does it behave in this way ? (data sheet says « This range of RP can be viewed as the maximum input range of an ADC. ») Does the ADC have missing codes ?

    Best Regards

    Richard Kelly

  • Hi Richard,

    Thank you for providing the additional details. It looks like you are seeing similar effects as the person who posted this E2E question. If changing the RP_MAX values does not change the response, then the only solution for this problem is to use the LDC1101. It has specific design changes to address this issue.

    Best Regards,

  • Hi,

    I can do some experiments to determine whether changing the value of Rpmax fixes the issue. If the steps in the response and the non-monotonicities are no longer present then is that result valid for all LDC1000s we may receive in production, over temperature etc ? 

    Is there an erratum you can share so that I can actually define the problem I face?

    As my previous posts I am intending to replace the end-of-life LDC1000 with the LDC1001. Does LDC1001 have the same problem ?

    Best Regards

    Richard

  • Hi Richard,

    If changing your RP_MAX setting fixes the issue, then the issue is likely configuration related and not the issue shown in the E2E question linked above. In that case the LDC1000s you receive in production should all behave the same way. If changing RP_MAX does not change the behavior, then the issue may not be present across all devices.

    Unfortunately we do not have an erratum to share, and this issue would be present in the LDC1001 as well. This is one of the significant improvements made in the LDC1101.

    Best Regards,

  • Hi Kristin,

    Thanks for your assistance.

    Regards