402
Logic Analyzer Concepts
Configuration Translation Between Agilent Logic Analyzers
The configuration translator needs to account for many aspects of the
analyzer architecture. Some of the considerations are as follows:
•When a range term is split across multiple pods, the term must span
adjacent odd/even pairs, starting with 1. Thus, terms could span pods 1
and 2, 3 and 4, 5 and 6, or 7 and 8, but not 2 and 3. Again, the translator
may display messages asking you to reconnect cables in a different
configuration.
•When loading a configuration into an analyzer with fewer pods than the
one on which the configuration was saved, the translator must remove pod
assignments. Which pods are removed from the configurati on will depend
on the widths of each pod in the original analyzer and new analyz er.
The configuration translation also needs to account for many
differences in the format and trace menus between the analyzers,
including label names, polarities, thresholds, symbols, clocking,
number of sequence levels, branch conditions, and patterns, among
others.
To ensure that trace measurements act as expected when you move
configuration files from one analyzer to another, follow these
recommendations:
•Ensure that the analyzer pods are hooked up as required by the
configuration translation and the new analyzer. The onscreen messages
given by the translator will help you identify which analyzer pods must be
swapped. If you are using an Agilent Technologies analysis probe, the
Analysis Probe User's Guide may contain information showing the cable
connections for different analyzer models.
•Review all trace format and trigger menu settings to verify that they will
meet your measurement requirements. You should check label
assignments, channel masks, pattern and range definitions, se quencer
setup, and general analyzer configuration (which pods are mapped to each
analyzer).
NOTE: When you move a configuration file from one analyzer to another, the trace
data from previous measurements is not moved. If you need to store trace
data for future reference, see "To save a trace list in ASCII fo rmat" on page
140.