• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 46 subscribers
  • Views 1056 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.

ADS1293: ADS1293 SPI read/write question

Wei Ken Ting
Prodigy 210 points
Part Number: ADS1293


Hello

Our project system design is as below :

MCU will write ADS1293 per 1/256 sec then read three ECG channel data.

If MCU stop one time to write ADS1293 , we find MCU read form ADS1293 data is 0000 but MCU still have write action to ADS1293.

How to avoid MCU write ADS1293 abnormal happen ,  ADS1293 can re-initial let MCU read data is correct ? 

  • 0
    TI__Guru 66816 points

    Hello Wei,

    Thank you for your post and welcome to our forum!

    I'm sorry but I do not understand your question. Can you try to restate your question more clearly? Below I will ask for some details that may help clarify the question:

    1. The MCU is writing to ADS1293 every 1/256 sec. Are you monitoring the DRDYB interrupt? 
    2. What is the source driving DRDYB? (DRDYB_SRC register, Addr. 0x27)
    3. When you stop reading and you write to the ADS1293, what are you writing?

    Please share a table of your register settings in address (hex) | value (hex) format. Also, can you please summarize the sequence of commands and values sent to the ADS1293?

    Best regards,

  • 0 in reply to Ryan Andrews
    Prodigy 210 points

    Hi Ryan ,

    Thanks for your reply , Attached file is our ADS1293 application register setting table.

    And I have two question as below :

    What happen on ADS1293 , If we don't use DRDYB interrupt pin ?

    Could you also help propose SPI ESD protect components on ADS1293 ? 

    ADS1293 setting Table.xlsx

  • 0 in reply to Wei Ken Ting
    TI__Guru 66816 points

    Hello Wei,

    Are you still looking into this issue?

    When you do not monitor DRDYB, the MCU has no method of determining when new data is available. If the old data is not completely read when new data arrives, the old data will be overwritten and lost immediately.

    By default, the DRDYB pin is not asserted after power-up. You must select the source of DRDYB to enable the interrupt.

    Best regards,