Indefinite capture using EVAL-AD7606C16FMCZ (and SDP-H1)

Hi Knath 

You're absolutely right — the ACE software, while user-friendly and great for initial evaluation, is not intended for seamless, indefinite data capture. Even with scripting workarounds like DataCaptureToFile or AsyncRawCaptureToFile, users often encounter 10–20% data gaps due to file I/O and session metadata overhead.

If you're using ACE with SDP-H1:

You can reduce data loss with the following optimized settings for AsyncRawCaptureToFile:

• ExportSessionFile = false → skips writing session metadata

• MergeMode = "Append" → continuously writes to the same file

• Use binary format instead of CSV → improves write speed significantly

Additionally, remote scripting is supported via MATLAB and Python.
Refer to this useful guide:

 How to Quickly Evaluate Data Converters Using ACE with Python or MATLAB | Analog Devices

Even with these optimizations, ~0.12s data gaps are typical — this appears to be the practical limit with ACE.

For true continuous/high-throughput capture:

 1: SDP-K1 + No-OS Drivers 

The SDP-K1 platform is better suited for indefinite capture using ADI’s no-OS drivers, offering:

• Continuous data streaming via SPI or parallel interface

• Capture of all channels at up to 200 ksps

• Flexibility to implement your own buffering and logging solution

Resources:

• AD7606 IIO Application Wiki
  Includes:

  • Hardware setup

  • Jumper settings (VIO_ADJUST → 3.3V)

  • Firmware flashing via Mbed Online Compiler

  • Streaming to IIO Oscilloscope

• AD7606C-16 Driver Page – ADI Developer Portal

• AD7606 No-OS Driver on GitHub

• EVAL-AD7606 Mbed Example

2: FPGA Platform (e.g., ZedBoard)

Some users have integrated the AD7606C-16 with ZedBoard + HDL + no-OS drivers, enabling:

Support for the ZedBoard path is currently limited, as we're still working on this internally.

Hope this helps.

Best regards,
Red