Session Control Pane

Use the Session Control pane to start and stop a recording. There is also a session status pane that shows the current status of the session.

session_control_pane.png
Session Control Pane

Snapshot Mode is the default mode of operation of the analyzer; Event Trigger Mode allows the user to set an Event Trigger and allows control over the timing of the recording of data.

Snapshot Mode Recording

When Idle displays in the Session Status Pane (SSP), the analyzer is waiting to start recording and is not recording or saving data.

  1. Click Record. You might see a warning message depending on the state of the analyzer.

    att_0_for_526811150.jpeg
    Warning Message
  2. Click Yes to Start Recording a Trace.

  3. Wait for the buffer to fill with raw data.

In Snapshot mode, when Record is clicked, the analyzer is automatically triggered, the Record button turns into a Stop button, and the status is Recording (the analyzer is storing the data in a local buffer).

status_pane_recording.png
Analyzer While Recording Data

Note: The Cancel button terminates recording. No trace data is stored.

The Stop button makes the analyzer stop recording data and move automatically to the next step in the sequence, Indexing.

  1. When the buffer is full, the analyzer processes the data and the SSP displays Indexing.

Recording continues within the limits set by the buffer size. When the buffer is full, recording stops and the analyzer starts turning the raw data into a meaningful database.

When Indexing displays, it means the application is creating an index of the captured Trace data while it still resides in the recording memory buffer. This functionality is a necessary preparation stage for opening the Trace in Quick View mode.

ssp_while_indexing.png
SSP While Host is Indexing Recorded Data from the Analyzer’s Memory

After the data is Indexed, the Record button turns on, but the Session Status Panel says Trace is not Saved. When Trace is Not Saved displays, this means that the trace is opened for viewing in Quick View mode, but it has not been saved to disk.

trace_not_saved.png
Trace Data Not Saved

You can store the processed data for later use or discard the trace by starting a new recording.

To save the trace:

  1. Go to File > Save Trace As. The Save As window opens, where you can name the file and choose where to save it.

    save_trace_as_2.png
    Saving a Trace File on the Host Computer
  1. The analyzer saves Trace data to the Host Computer. When Saving is displayed, this means the trace is being saved from the analyzer recording memory buffer to a file on the host PC.

saving_trace.png
Analyzer Saving Data Trace to Host Computer
  1. Once the trace is saved, you can start the process over again.

Event Trigger Mode Recording

The sequence for Event Trigger Mode is:

  1. Define an Event Trigger (define an event and define where in the buffer memory it will occur).

Recording continues in a circular manner within the limits set by the buffer size until an Event Trigger is detected that meets the conditions specified in the Triggering Options and the defined amount of data has been recorded after the Event Trigger.

  1. The analyzer is waiting to start recording (Idle). Click the Record button.

  2. Wait for the Event Trigger to occur. While it is waiting for the Event Trigger, the analyzer is recording raw data and the Status Pane displays Waiting for Trigger.

Note: If Stop is clicked, the analyzer ignores the Event Trigger, stops recording data, and moves automatically to the next step in the sequence, Indexing.

The Cancel button terminates recording. No trace data is stored.

att_3_for_526811150.jpeg
SSP While Analyzer is Waiting for Trigger
  1. The Event Trigger occurs. Trigger LEDs turn on and the analyzer records data after the trigger. The analyzer continues recording raw data until the buffer is full.

  2. When the buffer is full, the analyzer processes the data, and the display shows Indexing. This means the application is creating an index of the captured trace data while it still resides in the analyzer’s recording memory buffer. This prepares the trace to be opened in Quick View mode.

  3. After the data is indexed, the Session Status Panel shows Trace is not Saved. This means that the trace is opened for viewing in Quick View mode, but it has not been saved to disk.

You can choose to store the processed data for later use, or to discard the trace by starting a new recording.

Recording Status as Buffer Fills

You can see the buffer being filled in the following images.

trigger_25.png
Buffer Filled Up About 25% of Triggering Position
trigger_100.png
Buffer Filled Up About 100% of Triggering Position

Save Trace As

  1. To save the Trace, click File > Save Trace As.

  2. The save window opens. Rename the file and choose where you want to save it, if needed.

  3. When you are finished, click Save.

    save_trace_as_2.png
    Save Trace As File on Host Computer
  1. The analyzer saves trace data to the host computer.

  2. You can then start the process over again.

Event Trigger Recording Progress

A red vertical line illustrates the location of the Trigger Position you have selected in Trigger and Filter Settings.

Pre-Trigger progress is indicated by Waiting for Trigger in the field to the left of the Trigger Position.

att_6_for_526811150.png
Pre-Trigger

After the trigger occurs, Recording displays in the field to the left of the Trigger Position indicating the progress of the recording.

att_7_for_526811150.png
Post-Trigger

To save the file for later use, select File > Save.

Interrupting the Recording Process (Unplugging Cables)

When a captured trace is not saved and the USB cable is removed, the software displays an error message that unsaved traces will be closed. If you ignore the message and again plug in and unplug the USB cable, the software might get into an unstable state.

When the Ethernet cable is removed, the application detects the event after a delay of approximately 2.5 to 3 minutes. During this delay the device status remains ready and an attempt to capture a trace might result in error messages such as: “PCI configuration failed”, or “HAL error”. If this occurs, you need to power cycle the analyzer to allow detecting the device in the device list and continue capturing.