13 save as multisegment trace – Teledyne LeCroy Summit T28 PCIe Multi-lane Protocol Analyzer User Manual User Manual
Page 67
![background image](/manuals/353582/67/background.png)
Summit T28 PCI Express Multi‐Lane Protocol Analyzer User Manual
55
Save As MultiSegment Trace
Teledyne LeCroy
For example, if you set the Trigger Position to 90% Post‐Triggering Traffic, the Analyzer
records 10% pre‐trigger traffic and 90% post‐trigger traffic.
Trigger Position is only available when Manual Trigger or Event Trigger is selected.
5.13 Save As MultiSegment Trace
Divides the recording into segments so as to allow very large recordings to easily upload
and view. If you are planning to create a large recording, you might want to test this
option to see how it affects performance. Large CATC Trace files are easier to navigate but
slower to open (see
: 2G).
The PETracer application forces this option when the user selects a large buffer size for
recording. This is done to limit the size of individual trace files to a level that the PETracer
application can efficiently work with. The maximum size of the recording buffer that can
still be used for single trace recordings is 1024MB (1GB).
In Advanced Mode this option allows the Analyzer to segment the CATC Trace into 4 MB
to 128 MB files and to create an index file that summarizes the starting and finishing
frame for each segment.
Figure 5.10: Save As MultiSegment Trace
The index file has a default name of data.pem.
The index file and segmented CATC Trace files are stored in a directory named
data_pem_files. The directory is named after the index file. Below this directory
additional, sequentially numbered sub‐directories (up to 10,000) hold the segmented
CATC Trace files. These sub‐directories bear simple numerical names: 00000 to 00999.
Each of these subdirectories can hold up to 100 sequentially numbered segment files.
Example
A 1010 MB recording using the default file names creates the following sub‐directories
and files:
data.pem
(This is the index file.)
data_pem_files\00000\segment_00000.pex
data_pem_files\00000\segment_00001.pex
...
data_pem_files\00000\segment_00099.pex
data_pem_files\00001\segment_00100.pex
data_pem_files\00001\segment_00101.pex
The index file looks something like a CATC Trace file but contains packet‐like entities that
summarize each segment.