Cardbus Capturing:

The Cardbus analyzer provides 2 predefined capture
configurations:

1. Timing Mode (Store all transitions)
2. State Mode – Store All Events (Default)

Cardbus Triggering:

The Cardbus Analyzer provides high-level trigger configurations for most of the common trigger scenarios. The high-level triggers each provide drop-down boxes so the user can select specific access types, commands, addresses, etc from a list without memorizing codes or positions. The user can also create and save custom triggers.

Cardbus Analyzer Trace Filtering:

The Cardbus Analyzer provides commonly used high-level
filter configurations. Some of the high-level filters
provide drop-down boxes for configuration options. The user
can also create and save custom filters.

Cardbus Statistics:

The Real-Time Monitor can be easily configured by the user
for almost any type of Statistical or Bit Error Rate
measurement desired.

• PROTOCOLS & STANDARDS:
  • Cardbus
  • ATA / ATAPI 6.0

• SPEEDS:
  
  • 1.5 Mbytes/sec

Also check out: 

MultiBus is a Protocol Analyzer capable of taking multiple traces from different types of busses at the same time using the same reference clock. This product provides a new class of analysis tools for design, verification, and field engineers who work with networking, sub-systems, SAN, NAS, complex systems, and other multiple communication bus applications.

.............................

.............................

The analyzer allows for examining captured data at the Command, State, and Signal levels. The different display formats can be individually displayed or simultaneously displayed. When displayed simultaneously, each display can be automatically synchronized with the others, or used independently. A histogram provides a graphical summary of trace activity for the entire trace and makes it easy to point and click to any position within the trace.

The MPAX's Capture Engine pushes protocol recording to new limits with the following features: Transitional Timestamping, Bandwidth-4.5 Gbytes/sec, Depth-Stores up to 4 Gbytes, Segmentable Trace Buffer     More Information 

Custom Capture States

Triggering is used to stop the trace when a specific event or sequence of events occurs. The analyzer also provides for stopping when the buffer is full, or looping endlessly until the user manually stops the trace. High-Level triggering options are provided for each bus. The user can also create custom triggers using the powerful Trigger Sequencer. More Information

Custom Triggering

Pre-configured filters for each bus allow the user to conserve buffer space and reduce the stored data to those items that are of interest. Custom filters can also be created. More Information

Custom Filters

Dedicated hardware is provided for counting events. Software processes this data providing simple totals, or ratios of events per time or per other events, such as Transfers per Second, Transfers per Command, Errors per Second, or Data Transfers per Error.  These ratios are shown as Current Values, Average Values, and Peak Values, providing a summary of the changes over time.

The analyzer decodes many of the high-level protocols that are transmitted on each bus. The Command listing is typically used for displaying high-level protocols which may be transferred across a bus, while the State Listing typically displays native, low-level protocols.