AD7682 and AD7688 busy indicator

Question 1. I am using AD7682 and AD7688 components. I do accesses through a PLD and I am wondering how using the busy indicator. In the AD7682 datasheet, in the paragraph "General timing with a busy indicator", it is written: "At the EOC, if CNV is low, the busy indicator is enabled". As EOC is at the end of tCONV, and tCONV is equal to 2.2 us max, I thought I had to set CNV high during less than 2.2 us. But when I do board test, there is a problem, the busy indicator is not generated. Is there something I misunderstand in the datasheet? Do I have to set CNV high during more than 2.2 us? With the AD7688, tCONV is defined with min 0.5 us and max 1.6 us. The sentence in /CS mode 3-wire with busy indicator is "CNV must be returned low before the minimum conversion time and heldlow until the maximum conversion time to guarantee the generation of the busy indicator". With the sentence of this datasheet I understand that I have to set CNV high during less than 0.5 us and keep it to low until the 1.6 us. Do I misunderstand the datasheet? 2. I have implemented a communication with the AD7682 and I have observed its behaviour. Is there a possibility the SDO is not set in high impedance after the 17th clock cycle? I have a pull up on SDO and I have observed sometimes a value '1', sometimes a value '0' on SDO after the protocol, whereas I have set 17 rising edges. I have joined the chronogrammes with their titles. Note: the tCNVH has been set to 1 us and the tCK has been set to 5.5 us. tSCK is equal to 800 ns. Answer 1. First for the AD7682, to generate a busy indicator on the SDO line, the CNV signal must be returned low prior to the end of conversion (EOC). The EOC signal (busy signal) is what we use to determine the conversion time of the ADC. In busy indicator mode, the busy indicator is generated when a conversion is complete. The 2.2 uS conversion time that is specified in the data sheet is a guard banded number that tells you regardless of supply voltage, temperature, process skew, etc. that the conversion will always be finished within 2.2 uS. However, the EOC is most likely less than 2.2 uS under normal operating conditions. Therefore, to enter busy indicator mode, you will most likely need to bring CNV low well before 2.2 uS has elapsed since a rising edge is observed on CNV. The guard banded minimum conversion time is actually also specified in the data sheet and is listed as tDATA. This is the safe data access during conversion time and is listed as 1.2 uS. This basically says that the part is still guaranteed to be converting at 1.2 uS after a conversion is initiated. So in conclusion, on the AD7682, as long as CNV is brought low prior to tDATA, the device will enter busy indicator mode and will require an SCLK to clear the busy indicator before data is available. As for the AD7688, the same basic explanation for busy indicator mode that I just presented for the AD7682 holds true for this device also. The only difference will be the specific numbers. Instead of having 1.2 uS to bring CNV low and still enter busy indicator, the AD7688 only provides the user 500 nS. For our Automatic Test Equipment programs, we use a CNV high time of only 10 nS (which is the minimum tCNVH time) for entering busy indicator mode and keep CNV low for the rest of the conversion period. Another thing you will want to keep in mind is that you should implement and pull-up resistor on SDO and you will need to provide the 17th falling edge to place the SDO pin back in high impedance. If you only use 16 falling edges, SDO will keep the state of the LSB and could potentially stay driven low. 2. With busy indicator enabled, a total of 17 SCK falling edges are required to return SDO to high-Z while CNV is low. If CFG readback is enabled, a total of 31 SCK falling edges are required to return SDO to high-Z, so you should see the SDO high-Z after the 17th SCK falling edge. I'd like to see all four signals (CNV, SCK, SDO and SDI) on the same scope plot and see how these edges are lined up. Did you mean the time between conversions (tcyc) is 5.5µs? Make sure that you are not violating any of the data sheet timing specifications. There is always a one deep delay when writing the CFG register. From power-up, in any read/write mode, the first three conversion results are undefined because a valid CFG does not take place until the 2nd EOC; thus two dummy conversions are required. The AD7682 clocks out bits on the falling edge of SCLK starting with MSB-1, but you need to wait the tDSDO time before attempting to read a certain bit. The data can potentially be read on both the rising edge or falling edge of SCLK, but this obviously depends upon the SCLK frequency that is implemented. In this case, your SCK is fairly slow- 1.25MHz. For the fastest SCLK rates, it would be recommended to read the SDO data on the falling edge of SCLK.

AD7682 and AD7688 busy indicator usage

Question I am using AD7682 and AD7688 components. I do accesses through a PLD and I am wondering how using the busy indicator. In the AD7682 datasheet, in the paragraph "General timing with a busy indicator", it is written: "At the EOC, if CNV is low, the busy indicator is enabled". As EOC is at the end of tCONV, and tCONV is equal to 2.2 us max, I thought I had to set CNV high during less than 2.2 us. But when I do board test, there is a problem, the busy indicator is not generated. Is there something I misunderstand in the datasheet? Do I have to set CNV high during more than 2.2 us? With the AD7688, tCONV is defined with min 0.5 us and max 1.6 us. The sentence in /CS mode 3-wire with busy indicator is "CNV must be returned low before the minimum conversion time and heldlow until the maximum conversion time to guarantee the generation of the busy indicator". With the sentence of this datasheet I understand that I have to set CNV high during less than 0.5 us and keep it to low until the 1.6 us. Do I misunderstand the datasheet? Answer First for the AD7682, to generate a busy indicator on the SDO line, the CNV signal must be returned low prior to the end of conversion (EOC). The EOC signal (busy signal) is what we use to determine the conversion time of the ADC. In busy indicator mode, the busy indicator is generated when a conversion is complete. The 2.2 uS conversion time that is specified in the data sheet is a guard banded number that tells you regardless of supply voltage, temperature, process skew, etc. that the conversion will always be finished within 2.2 uS. However, the EOC is most likely less than 2.2 uS under normal operating conditions. Therefore, to enter busy indicator mode, you will most likely need to bring CNV low well before 2.2 uS has elapsed since a rising edge is observed on CNV. The guard banded minimum conversion time is actually also specified in the data sheet and is listed as tDATA. This is the safe data access during conversion time and is listed as 1.2 uS. This basically says that the part is still guaranteed to be converting at 1.2 uS after a conversion is initiated. So in conclusion, on the AD7682, as long as CNV is brought low prior to tDATA, the device will enter busy indicator mode and will require an SCLK to clear the busy indicator before data is available. As for the AD7688, the same basic explanation for busy indicator mode that I just presented for the AD7682 holds true for this device also. The only difference will be the specific numbers. Instead of having 1.2 uS to bring CNV low and still enter busy indicator, the AD7688 only provides the user 500 nS. For our Automatic Test Equipment programs, we use a CNV high time of only 10 nS (which is the minimum tCNVH time) for entering busy indicator mode and keep CNV low for the rest of the conversion period. Another thing you will want to keep in mind is that you should implement and pull-up resistor on SDO and you will need to provide the 17th falling edge to place the SDO pin back in high impedance. If you only use 16 falling edges, SDO will keep the state of the LSB and could potentially stay driven low.

English

Forums
Popular Forums
Product Forums
View All
Application Forums
Design Center Forums
Learn
Highlighted Webinar

Fast-Track Certification: Leveraging IC Safety App Notes for Functional Safety Designs
Stop guessing, start certifying. Learn how to use IC safety application notes to streamline your FMEDA and meet IEC 61508 and ISO 13849 standards with...
Places
Libraries
Community Hub
Challenge Yourself!
View All
What's Brewing
View All
Places
Resources
View All
ContentZone
Visit ContentZone
Search content by industry or technology.

Blogs

Technical Articles

Tutorials

Videos

Webinars

Your ADI content all in one place.
View ContentZone
The Latest Read

A Systematic Checklist for RF Transceiver Testing
RF transceiver bring-up is the initial process of powering, configuring, and verifying a transceiver on new hardware to ensure basic functionality and...

New Release

Signal Chain Designer: DC Error Simulation
This video covers the DC error calculation capabilities of Signal Chain Designer. DC error is unique in that often requires calibration and has so many...

Recent Technical Insights

Phase Sync in Digital Phased Arrays Through Direct RF SamplingPart 1: The Basics
This article presents a methodology to synchronize multiple modular circuit boards, equipped with high speed data converters, to build a concept of a scalable...

EngineerZone

Precision ADCs

Log In

User
Site
Search

OR

Ask a Question

Data Converters

Precision ADCs

Documents AD7682: FAQ

Q&A
File Uploads
FAQs/Docs
Help Articles
Members
Tags
Cancel

Products Mentioned

AD7682 Production
The AD7682/AD7689 are 4-channel/8-channel, 16-bit, charge redistribution successive approximation register (SAR) analog-to-digital converters (ADCs) that...
Datasheet
AD7682 on Analog.com

Table of Contents

+Documents
+General: FAQ
+AD1139: FAQ
+AD7091R Conversion Result Change
+AD1556: FAQ
+AD1580: FAQ
+AD1582: FAQ
+AD2S1200: FAQ
+AD2S1205: FAQ
+AD2S1210: FAQ
+AD2S75: FAQ
+AD2S80: FAQ
+AD2S80A: FAQ
+AD2S82A: FAQ
+AD2S83: FAQ
+AD2S90: FAQ
+AD2S99: FAQ
+AD4110-1: FAQ
+AD411x: FAQ
+AD5940: FAQ
+AD598: FAQ
+AD650: FAQ
+AD652: FAQ
+AD654: FAQ
+AD7091: FAQ
+AD7091R-X: FAQ
+AD711: FAQ
+AD7124-4: FAQ
+AD7124-8: FAQ
+AD7134: FAQ
+AD713: FAQ
+AD7142: FAQ
+AD7147: FAQ
+AD7148: FAQ
+AD7150: FAQ
+AD7151: FAQ
+AD7175-2: FAQ
+AD7176-2: FAQ
+AD7176: FAQ
+AD717x: FAQ
+AD7190: FAQ
+AD7192: FAQ
+AD7193: FAQ
+AD7195: FAQ
+AD719x: FAQ
+AD7265: FAQ
+AD7266: FAQ
+AD7280: FAQ
+AD7291: FAQ
+AD7298: FAQ
+AD7305: FAQ
+AD7321: FAQ
+AD7323: FAQ
+AD7328: FAQ
+AD7366-5: FAQ
+AD7367: FAQ
+AD736ARZ: FAQ
+AD737: FAQ
+AD738x : FAQ
+AD7398: FAQ
+AD7400A: FAQ
+AD7401: FAQ
+AD7403: FAQ
+AD74111: FAQ
+AD7415: FAQ
+AD7416: FAQ
+AD7417: FAQ
+AD7418: FAQ
+AD7450: FAQ
+AD7475: FAQ
+AD7484: FAQ
+AD7490: FAQ
+AD7492: FAQ
+AD75019: FAQ
+AD7503: FAQ
+AD7541A: FAQ
+AD7546: FAQ
AD7547: FAQ
+AD7568: FAQ
+AD7578: FAQ
+AD7606-4: FAQ
+AD7606: FAQ
+AD7606B: FAQ
+AD7606C: FAQ
+AD7608: FAQ
+AD7616 FAQ
+AD7616-P: FAQ
+AD7621: FAQ
+AD7625: FAQ
+AD7626: FAQ
+AD7631: FAQ
+AD7653: FAQ
+AD7654: FAQ
+AD7655: FAQ
+AD7656: FAQ
+AD7657-1: FAQ
+AD7663: FAQ
+AD7674: FAQ
+AD7675: FAQ
+AD7678: FAQ
-AD7682: FAQ
- AD7682 and AD7688 busy indicator
- AD7682 and AD7688 busy indicator usage
+AD7683: FAQ
+AD7684: FAQ
+AD7685: FAQ
+AD7688: FAQ
+AD7689: FAQ
+AD7690: FAQ
+AD7691: FAQ
+AD7705: FAQ
+AD7706: FAQ
+AD7707: FAQ
+AD7708: FAQ
+AD7709: FAQ
+AD7710: FAQ
+AD7711A: FAQ
+AD7712: FAQ
+AD7713: FAQ
+AD7714: FAQ
+AD7714YN: FAQ
+AD7715: FAQ
+AD7716: FAQ
+AD7718: FAQ
+AD7719: FAQ
+AD7720: FAQ
+AD7722: FAQ
+AD7725: FAQ
+AD7730: FAQ
+AD7731: FAQ
+AD7732: FAQ
+AD7738: FAQ
+AD7740: FAQ
+AD7741: FAQ
+AD7745: FAQ
+AD7746: FAQ
+AD7747: FAQ
+AD7760: FAQ
+AD7763: FAQ
+AD7766: FAQ
+AD7768: FAQ
+AD777x: FAQ
+AD7780: FAQ
+AD7785: FAQ
+AD7787: FAQ
+AD7788: FAQ
+AD7790: FAQ
+AD7792: FAQ
+AD7793: FAQ
+AD7794: FAQ
+AD7795: FAQ
+AD7798: FAQ
+AD7799: FAQ
+AD7805: FAQ
+AD7808: FAQ
+AD7809: FAQ
+AD780: FAQ
+AD7811: FAQ
+AD7812: FAQ
+AD7817: FAQ
+AD7819: FAQ
+AD7821: FAQ
+AD7825: FAQ
+AD7829: FAQ
+AD7835: FAQ
+AD7849: FAQ
+AD7851: FAQ
+AD7854: FAQ
+AD7856: FAQ
+AD7858: FAQ
+AD7859: FAQ
+AD7864: FAQ
+AD7865 : FAQ
+AD7872: FAQ
+AD7874: FAQ
+AD7879: FAQ
+AD7887: FAQ
+AD7888: FAQ
+AD7891-1: FAQ
+AD7891: FAQ
+AD7893-2: FAQ
+AD7895: FAQ
+AD7896: FAQ
+AD7899: FAQ
+AD7912: FAQ
+AD7921: FAQ
+AD7924: FAQ
+AD7927: FAQ
+AD7938: FAQ
+AD7942: FAQ
+AD7949: FAQ
+AD7960: FAQ
+AD7961: FAQ
+AD797: FAQ
+AD7980: FAQ
+AD7982: FAQ
+AD7984: FAQ
+AD7986: FAQ
+AD7988-1: FAQ
+AD7993: FAQ
+AD7994: FAQ
+AD7997: FAQ
+AD7998: FAQ
+ADA2200: FAQ
+ADAS1000: FAQ
+ADAS3022: FAQ
+ADAS3023: FAQ
+ADC: FAQ
+ADVFC32: FAQ
+EVAL-AD7719-EB: FAQ
+EVAL-ADAS3022EDZ: FAQ
+RDC1740: FAQ
+AD4030-24: FAQ
+AD4114: FAQ
+AD4116: FAQ
+AD4130-8 FAQ
+AD4131-8: FAQ
+AD4134 FAQ
+AD4170: FAQ
+AD4858
+AD674BBD: FAQ
+AD7172-2: FAQ
+AD7175-8: FAQ
+AD7191: FAQ
AD73360: FAQ
+AD73360AR: FAQ
+AD73360L: FAQ
+AD7357: FAQ
+AD7386-4: FAQ
+AD738x-4: FAQ
AD7398 SPI Voltage vs VCC
+AD7457: FAQ
+AD7606C-16: FAQ
+AD7609: FAQ
+AD7656-1: FAQ
AD7660: FAQ
+AD7665: FAQ
+AD7680: FAQ
+AD7686: FAQ
+AD7764: FAQ
+AD7778: FAQ
AD7892: FAQ
+AD7980SRMZ-EP: FAQ
+AD7991: FAQ
+AD9243: FAQ
+AD9260: FAQ
+AD9261: FAQ
+AD9262: FAQ
+AD974: FAQ
+AD976A: FAQ
+AD977A: FAQ
+ADAQ4003: FAQ
+ADAQ7768-1: FAQ
+ADAQ8092 FAQ
+DC590, DC2026, QuikEval: FAQs
+EVAL-AD7768-4FMCZ: FAQ
+Legacy LTC - Sigma Delta ADCs FAQ
+LTC2408: FAQ
+LTC2497: FAQ
+MAX1028: FAQ
+MAX1036: FAQ
+MAX1037EKA+: FAQ
+MAX11040GUU+: FAQ
+MAX11043: FAQ
+MAX11045: FAQ
+MAX11046 16-BIT AD: FAQ
+MAX11048: FAQ
+MAX11100EUB+: FAQ
+MAX11101: FAQ
+MAX11103: FAQ
+MAX11108: FAQ
MAX11125: FAQ
+MAX11125ATI+: FAQ
+MAX11130: FAQ
+MAX11131ATI+: FAQ
+MAX11136ATI+: FAQ
+MAX11150EVKIT#: FAQ
+MAX11154: FAQ
MAX11156: FAQ
+MAX11156ETC+: FAQ
+MAX11158: FAQ
+MAX11163: FAQ
+MAX11168EUB+: FAQ
+MAX11169EUB+: FAQ
+MAX11190: FAQ
+MAX11190ATE+: FAQ
MAX11192: FAQ
+MAX11192EVKIT#: FAQ
+MAX11200: FAQ
+MAX11200EEE+: FAQ
+MAX11201: FAQ
+MAX11203EEE+: FAQ
+MAX11206: FAQ
+MAX11207EEE+: FAQ
MAX11210: FAQ
+MAX11210EEE+: FAQ
+MAX11213EEE+T: FAQ
MAX11214: FAQ
MAX11214EUG+: FAQ
+MAX11214EUG+_T1: FAQ
+MAX11216: FAQ
+MAX11254ATJ+: FAQ
+MAX11254EVKIT#: FAQ
+MAX11259AWX+T: FAQ
+MAX11259PMB#: FAQ
+MAX11261BOB#: FAQ
+MAX11261ENX+: FAQ
+MAX11270EUG+: FAQ
+MAX11337ATJ+: FAQ
+MAX11410ATI+: FAQ
+MAX11608: FAQ
+MAX11609EEE+: FAQ
+MAX11612EUA+: FAQ
+MAX11612EVSYS: FAQ
+MAX11614EEE+: FAQ
+MAX11615EEE+C78: FAQ
+MAX11615EWE+: FAQ
+MAX11616EEE+: FAQ
+MAX11617EWE+: FAQ
+MAX11625: FAQ
+MAX11629EEE+: FAQ
+MAX11645EWC+T: FAQ
+MAX11647EUA+: FAQ
+MAX11900: FAQ
MAX11905: FAQ
+MAX11905EVKIT#: FAQ
+MAX1202AEAP+: FAQ
+MAX1220: FAQ
+MAX1229: FAQ
+MAX1230BCEG+: FAQ
+MAX1231AEEG+: FAQ
+MAX1239EEE+: FAQ
+MAX1239KEEE+: FAQ
+MAX1239LEEE+: FAQ
+MAX1258: FAQ
+MAX1271ACNG+: FAQ
MAX1300: FAQ
+MAX1300BEUG+: FAQ
+MAX1301AEUP+: FAQ
+MAX13171: FAQ
+MAX13204EALT+: FAQ
MAX1343: FAQ
+MAX1343BETX+: FAQ
+MAX13487: FAQ
+MAX13488: FAQ
+MAX1379ATP+: FAQ
+MAX1383: FAQ
+MAX1447ECJ+: FAQ
MAX14571: FAQ
+MAX14571EUD+: FAQ
MAX14574EWL+: FAQ
+MAX14574EWL+T: FAQ
+MAX14578: FAQ
+MAX14579EEVKIT#: FAQ
+MAX14588ETE+T: FAQ
+MAX145ACPA+: FAQ
+MAX1474: FAQ
+MAX14783: FAQ
+MAX14805: FAQ
+MAX14807ECB+: FAQ
+MAX14900D: FAQ
+MAX15090BEWI+: FAQ
+MAX1645AEEI+: FAQ
+MAX16600GGN+: FAQ
+MAX17823AGCB+: FAQ
MAX17823AGCB/V+: FAQ
+MAX17823AGCB/V+T: FAQ
+MAX17823GCB+: FAQ
+MAX182BEWI+T: FAQ
+MAX19777AZA+: FAQ
+MAX31865: FAQ
+MAX31865AAP+: FAQ
+Precision Technology Learning Modules
Programming FMC FRU ID EEPROM on Linux