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.

ADS1015-Q1: I2C problem

Part Number: ADS1015-Q1
Other Parts Discussed in Thread: ADS1015

Hi Expert,

Our customer shares an interesting topic with me. They use ADS1015 and another I2C device, called I2C_deviceB, together. Two devices share the same pullup resistor. Our customer suddenly finds that they made a mistake. On ADS1015, they connect SCL signal to SDA pin, and connect SDA signal to SCL pin. And I2C_deviceB has the right connection with MCU. They try to use communicate I2C_deviceB and MCU via I2C. But I doesn't work. It's quite clear that it's because of the wrong connection with ADS1015. But we don't really understand why. Could you please how does this wrong connection affect the communication between MCU and I2C_deviceB? Thanks a lot for you help!

BR,

Elec Cheng

  • Hi Elec,

    If the ADS1015 and DeviceB share the same I2C bus, then I would expect the SCL and SDA line would be corrupt. SCL is the clock, so if connected to SDA of the ADS1015, and the ADS1015 is powered on and sending data, there will be some bus contention. The same goes when SDA is connected to SCL on the ADS1015 and there will be bus contention between the two devices. 

    Regards,
    Aaron Estrada

  • Hi Aaron,

    Thanks for reply! 

    If ADS1015 has no action on I2C, that is ADS1015 doesn't send data and MCU doesn't read ADS1015's data, will  I2C_deviceB and MCU work well? And ADS1015 works as slave, how can it send data if MCU doesn't read it? Thanks for clarifying.

    the ADS1015 is powered on and sending data

    BR,

    Elec Cheng

  • Hi Elec,

    I still think there may be contented issues even if one of the ADC's isn't sending/receiving data. Bad wording on my part. 

    Regards,
    Aaron