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.

ADS8584S: How do I detect ADC conversion error?

Part Number: ADS8584S
Other Parts Discussed in Thread: ADS8588S

Tool/software:

Dear Technical Support Team,

What happens when ADS8584S or ADS8588S fails in AD conversion due to Conversion Error?

For example, is the user notified of an error by output signals such as BUSY not being set to '1' or FRSTDATA not asserting '1'?
Or, is there no notification by output signals, and the data of the channel that failed AD conversion remains abnormal value or fixed value is output?

I am wondering if it is possible to detect errors and take countermeasures on the FPGA side when an error occurs in the ADC.

Best Regards,

ttd

  • Hi ttd,

    The BUSY or FRSTDATA signals would let you know when a conversion is complete (or read for CH1) - if the BUSY got stuck, that would be an indication of a potential issue, but would not necessarily tell you that any conversion value is wrong, if that is what you are looking for.  If BUSY were stuck, it would potentially indicate a communication error or an issue with the CONVSTx inputs.  In the end, these devices do not have any 'smart' detection capabilities for error checking.  We do have a few parts with CRC capabilities if that is what you are looking for - just let us know!

  • Hi Tom,

    Thank you for your reply.

    I have additional questions.

    Although ADS8584S or ADS8588S does not have the function to formally detect conversion errors such as CRC, does BUSY or FRSTDATA get stuck or have a shorter assertion period if some problem may have occurred?
    Also, does it behave in a way that deviates from the tD_CSFD or tCONV specified in the datasheet?

    Best Regards,

    ttd

  • Hi ttd,

    No, there is no deviation in delay and the conversion time does not change.

  • Hi Tom,

    Thank you for your reply.

    Am I correct in understanding that BUSY can be stuck Low but not High? Once the conversion starts and changes from Low to High and then Low after tCONV.
    (it doesn't gets stuck on High, so the conversion time(tCONV) doesn't change as you mentioned)

    Best Regards,

    ttd

  • No - if no conversion was actually started, BUSY would remain low.  If a conversion was started and for some reason did not complete, BUSY would stay high.