• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 46 subscribers
  • Views 530 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

ADS131A02: ADS131A02

Dian Mladenov
Prodigy 10 points
Part Number: ADS131A02


Hello,

I am using ADS131A02 in my design to read two analog values. M1 is connected to ground (24bits device word length), by default ADS131 is in dynamic-frame mode with CRC disabled. To read the ADC conversion data I am using NULL command. At SPI clock I have a 56 cycles to read 9bytes, according the manual. Because the word length is 24bits for status I have 24bits. According the manual the response have to be REG(STAT_1), but STAT_1 is 8bits long? The inputs are connected together for a test, The ADC conversion data from channel_1 is the data I expected, but the second one is different. When I go up and down, the reading from second channel also going accordingly, but is off. What is the right way to read continuously the ADC conversion data? Please see attached screenshot from my analyzer.

Thank you in advance for your answer,

Dian

  • 0
    Prodigy 10 points

    Hello,

    I found the problem with discrepancy between two ADC channels. Simply ADC chip was bad. I replaced ADS131A02 with new one (see new attached), but I still need to know what I am reading as a status.

    Regards,

    Dian

  • 0 in reply to Dian Mladenov
    TI__Guru 67016 points

    Hello Dian,

    Welcome to our forum and thank you for your post!

    Please refer to Table 14. The STATUS response is actually 16 bits. The first byte contains 001a aaaa, where "a aaaa" is the register address. The second byte contains the 8-bit register value ("dddd dddd"). When sending the NULL command, the STATUS automatically provides the STAT_1 register contents at address 02h. Therefore, 0x22 seems like a valid response.

    Regards,

    Ryan