• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 45 subscribers
  • Views 478 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.

ADS1261: RDATA command

Adrian Unkeles1
Prodigy 210 points
Part Number: ADS1261

On page 53 (section 9.5.5) of the datasheet for this part (http://www.ti.com/lit/ds/symlink/ads1260.pdf?ts=1590517885555) 

it specifies that "The ADC executes commands at completion of the 2nd byte (no CRC verification)". Then on page 54-55 it discusses the RDATA command and shows DIN as being 6-bytes long!? Bytes 1 and 2 are the expected command and echo byte, but then there are several "00h" bytes following. Is this a typo in the datsheet? When should I expect to start reading on DOUT after sending RDATA command?

This behavior conflicts with what's shown in table 16 (page 53). Please verify what the expected DIN and DOUT should be for RDATA.

Regards,

-Adrian

  • 0
    TI__Mastermind 45415 points

    Hello Adrian,

    The table 16 in the datasheet only shows the necessary bytes for sending RDATA command. However, after receiving RDATA command from DIN, the ADS1261 ADC requires associated SCLK pulses to shift out the data to DOUT line, in other words, the ADC shifts out the data corresponding to the SCLK pulses it has received. Hence, the purpose for sending four "00h" commands in table 21 is to send more SCLK pulses to the ADC so that the ADC can launch "STATUS" and "MSB", "MID" and "LSB" data to the DOUT line. For same reason, the timing in Figure 76 shows three "00h" commands required by the ADC to launch "MSB", "MID" and "LSB" to DOUT line without  "STATUS" as an timing example.

    If STATUS byte and CRC mode are disabled, you can get the data on DOUT from 17th SCLK to 40th SCLK.

    Best regards,

    Dale