Applies to All ViewComm II Models |
|
Find Criteria |
|
|
Find in Decode Pane |
 |
Set up to locate the string in yellow below: Locate the first time that Van Jacobson Compression is broken. |
|
|
Results: Click Find Next to see the resulting string located in the Decode Pane.
It occurs in frame number 24.
You can click Find Next to search for more occurrences.
|
 |
|
|
Find a Byte Pattern |
 |
Here we are searching for the name of a particular computer in the capture file. |
And here is the partial content of the first packet that contains the search string.
Note that we could have used hex, binary, control characters, wildcards... |
 |
|
|
Find Frame at Specified Time |
 |
Notice that you can specify time to the nearest microsecond. |
if you captured with microsecond timestamp resolution, you will see that as shown at right. |
 |
|
|
Go To Specified Frame Number |
 |
Here we've selected the Go To tab and set up to find Frame Number 347. Note the other options. |
Found it! Frame View, Frame Summary Pane |
 |
|
|
Find Special Events |
 |
This time we have so few really bizarre events that we will just show the first End of Frame in the capture file.
There are about 25 other kinds of things we can search for. You can select multiple kinds so that you will see the first time any of the selected types occurs.
|
|
This is not very exciting, but it does show the special symbol for End of Frame. There are many more special symbols, each representing a special event that you can search for. |
 |
|
|
Find based on Signal Configuration or Change |
 |
Here we're set up to Find (the next) event where RTS is ON, CTS is OFF, and the remaining signals are "don't-care."
Note in the views below, there are several ways the event, if found, is displayed.
|
|
Looking at the Signal View and pressing the Zoom In button a few times, we can clearly see that our conditions are matched. The yellow highlight was placed there automatically by the Find software. |
 |
|
 |
Additional indications of this signal condition are found in the data area of the Event View and in the Status Bar, where the condition of all signals is indicated, keyed to the event marker (arrows in the top image) |
 |
|
Is this Awesome or what? |
Find Error Conditions
Example 1 |
 |
In the first example, we're searching for an event marking the occurrence of a Parity Error. Other error conditions are "don't care." |
|
In the Event View we see that the highlighted character, hex 23, is displayed in red to indicate an error. Note the flag marker (we colored it light blue) at the left. These are clues we can use to hunt for a trouble spot. |
 |
|
Looking in the Status Bar region of the Event View, we see an indication of a Parity Error and the timestamp appears above that. |
 |
|
|
Referring now to the Frame View for further information about the Parity Error, we see that it occurred in Frame 10 and is shown
as Parity in red below the Errors portion of the Protocol Pane tree.
These indications reveal different kinds of information about the error event.
|
 |
|
|
Find Error Conditions
Example 2 |
 |
In this example, we're searching for an occurrence (event) where either or both of an Overrun or Framing error has occurred.
We will see this in several views after clicking Find Next.
|
|
In Event View, we see the first occurrence of one of these errors printed in red and highlighted. |
 |
|
 |
Again we see the type and timestamp of the above error in the Status Bar on the Event View. |
|
 |
And finally, the Decode Pane of Frame View reveals the frame number and a lot more information (if you look at it).
Objective: Hunt and Eliminate Enemy Errors by first finding them among the thousands of events. Sold on Find yet?
|
|
|
