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.

ADS1298 Multi-Byte Commands

Other Parts Discussed in Thread: ADS1298

Dear All,

The datasheet for ADS1298 (under section Sending Multi-Byte Commands on page 42 SBAS459H –JANUARY 2010–REVISED MAY 2011) imposes a delay of 1.96uS (for Fclk=2.048MHz) between consecutive bytes of a multi-byte command. The same is depicted in timing diagrams for RDATA Usage (Fig 48) and Serial Interface Timing (Fig 1). However it is not clear from the timing diagram of RDATAC Usage (Fig 47) that there be a delay between two bytes when reading the 216 bit long conversion result.

Is Tsdecode applicable while reading conversion results in RDATAC mode?

  • Hi Horizon,

    The delay associated with the SPI interface on the ADS1298 is only needed between the OPCODE and the second byte - for instance after RREG and before 000n nnnn.  If your SCLK speed is up at the 16MHz rate, you would need the 4tCLK delay after RDATAC, but you do not need to insert any delays when reading the 216 bits of data from the STATUS and the 8 channels of data.