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.

LDC1614: DataSheet I2C question

Part Number: LDC1614

Hi Everyone

I have a question about
LDC1614 Datasheet Description on page 14: "7.5.2 Pulses on I 2 C"
"A STOP condition or other early termination occurring before the normal end of a transaction (ACK) is not
supported and may corrupt that transaction and / or the following transaction."
About this description, there are two questions below.
Q1: In fact, what kind of problem will it cause?
Q2 If problems occur, will they become discrete values when reading the MSB or LSB register?

If you have any information then please let me know.

Best Regards

Shing

  • Hi Shing,

    I do not believe that we have data available that details the specific ways that this can corrupt the I2C data, but I will investigate to see if I can find some. I'll reply this thread once I have an update for you.

    Regards,
  • Hi Kristin

    Thank you for your reply.

    Please let me know if you find detail of described "DATA SHEET".

    Best Regards

    Shing

  • Hi Shing,

    Unfortunately I wasn't able to find any data that details the specific ways the I2C transactions could be corrupted. We only specify the behavior with properly formatted I2C transactions, and cannot speculate on all possible responses to improper stimuli.

    Regards,
  • Hello Kristin-san,

    Thank you for your support.
    The background of this question from Shing-san is that customer sometimes sees inpluse-like noise on the output data and would like to confirm sensitiveness of pulses on SDA like datasheet mentions can cause the output behavior.
    Do you think it induces inpulse-like noise on output data?

    Best regards,
  • Hi Sato-san,

    If the customer is seeing spikes in the output data, this is most likely not caused by I2C errors. Typically this error is caused by EMI from long, unshielded cables or noise if the sensor's Q value or oscillation amplitude are too low. The quick fixes for these problems are shielding any long cables, increasing the sensor drive current to increase its oscillation amplitude, and modifying the sensor coil to improve its Q value (by decreasing the Rs). If none of these methods work to eliminate the spikes, please feel free to post again and we can continue debugging.

    Regards,