DigiView™ Logic Analyzer Capture

Capturing Data with DigiView™

Analyzer Data Searching
DigiView hardware is always capturing and storing data in a circular queue. While you are looking at the last capture, the hardware is pre-filling the buffer to the pre-fill size selected.

When the buffer reaches the pre-fill setting, the hardware continues capturing and storing data in a circular queue fashion so that the most recent data is always available while waiting on the trigger condition.


Once signals and triggers are defined, you can capture a new buffer of data at any time by pressing the 'Run' or 'Auto Run' buttons.

If you tire of waiting on a trigger or it triggers but you tire of waiting for it to fill up the buffer, you can stop the capture at any time to transfer the capture buffer to the screen.

When transferred to the screen, the capture is also stored in the capture history for later analysis.

On-line User's Guide: Capturing ...  more info...


DigiView provides the following Capture features:

  • Long capture times - Our logic analyers have deep memory & Real-time, hardware based compression which combine to allow maximum capture times, regardless of signal activity. Achieve high resolution and long capture times at the same time, eliminating resolution vs. time trade-offs.

    Each capture can store over 46,000 ASYNC or 10,000 I2C characters at full sample-rate resolution, regardless of BAUD RATE or gaps between characters*

     See: Hardware Compression...  more info...

  • Automation - Have a very rare, elusive problem that can't be caught with a typical trigger setup or a typical logic analyzer? Use DigiView's Automation to help catch it in the act.

    If you are on a fishing expedition, you can use Auto-Run and Capture History to repeatedly capture and store data for later analysis. If you know in advance exactly what you are looking for, you can set up an auto-search before starting the capture and configure it to HALT on match. DigiView will tirelessly capture, search and repeat until it finds it.


  • Capture History storage can be limited by Number of Captures, Storage Size and Free Disk Space.

    Capture History - As data for a project is captured and transferred to the PC, it is stored on the Hard Drive as a history buffer and maintained according to the settings configured in Acquisition Options. Each project maintains its own history buffer in a sub folder using the same name as the project file.

    However, the project file does not require the history buffer to be present when opened. This allows the project file to operate as a 'stand-alone' file for sharing or archival purposes. When saving the project file, the currently loaded capture will be the data stored in the project.

    The history buffer can be accessed utilizing the History Menu, the Browse button or the bar graph. When browsing the history, the data for that history item will be loaded and all Signals, Auto Searches, Lists, Tables, etc. will refresh as if the data had just been captured.

    You have full control of the Capture History storage settings. Maximum storage for a single project is 999 Terabytes.



  • Select any defined search (including complex sequential Frame/Field searches) and have it process the entire capture history and halt when a match occurs or if a specific number of matches occur within a capture. When halting, the history search will load the matching capture for further analysis.

    Capture History Searching - With the Capture History Search feature, any search can be selected to search the entire capture history and load the file that meets the selected match count criteria. Searching can be continued forward or backward from the position matched.

  • Capture Preview - This Capture mode will automatically transfer data to the PC repeatedly even if a trigger condition has not been defined. This mode is very useful to Monitor signals while making connections and only utilizes a small portion of the hardware buffer.

    In this mode, the Hardware buffer size and duration of data collection is adjusted automatically to provide a "peek" of the logic activity and is not intended for normal data analysis. The result is a virtual "LIVE" mode that does not try to search the data (Auto Search windows) or store the data in the capture history. The data displayed will be discarded when the results of a normal Run (single shot) or Auto Run are displayed.