User's Manual
Table Of Contents
- Agilent Technologies 16750A/B Logic Analyzer
- Agilent Technologies 16750A/B Logic Analyzer
- Contents
- Getting Started
- Step 1. Connect the logic analyzer to the device under test
- Step 2. Choose the sampling mode
- Step 3. Format labels for the probed signals
- Step 4. Define the trigger condition
- Step 5. Run the measurement
- Step 6. Display the captured data
- For More Information...
- Example: Timing measurement on counter board
- Example: State measurement on counter board
- Task Guide
- Probing the Device Under Test
- Choosing the Sampling Mode
- To select transitional timing or store qualified
- Formatting Labels for Logic Analyzer Probes
- Setting Up Triggers and Running Measurements
- Displaying Captured Data
- Using Symbols
- Printing/Exporting Captured Data
- Cross-Triggering
- Solving Logic Analysis Problems
- Saving and Loading Logic Analyzer Configurations
- Reference
- The Sampling Tab
- The Format Tab
- Importing Netlist and ASCII Files
- The Trigger Tab
- The Symbols Tab
- Error Messages
- Must assign Pod 1 on the master card to specify actions for flags
- Branch expression is too complex
- Cannot specify range on label with clock bits that span pod pairs
- Counter value checked as an event, but no increment action specified
- Goto action specifies an undefined level
- Maximum of 32 Channels Per Label
- Hardware Initialization Failed
- Must assign another pod pair to specify actions for flags
- No more Edge/Glitch resources available for this pod pair
- No more Pattern resources available for this pod pair
- No Trigger action found in the trace specification
- Slow or Missing Clock
- Timer value checked as an event, but no start action specified
- Trigger function initialization failure
- Trigger inhibited during timing prestore
- Trigger Specification is too complex
- Waiting for Trigger
- Analyzer armed from another module contains no "Arm in from IMB" event
- Specifications and Characteristics
- Concepts
- Understanding Logic Analyzer Triggering
- Understanding State Mode Sampling Positions
- Getting Started
- Glossary
- Index

78
Chapter 2: Task Guide
Setting Up Triggers and Running Measurements
Editing Advanced Trigger Functions
After you break down a trigger function (if it didn't quite provide the
trigger capability you need), or after you select one of the advanced
trigger functions, you're ready to edit the advanced trigger function.
All trigger functions look for events and, if those events are found, take
actions.
Most often, the event is something that occurs on the probed signals
(label events), and the action is to trigger the logic analyzer. However,
events can also test timer, counter, and/or flag values that are set up in
the logic analyzer, and actions can include setting up timers, counters,
and flags as well as specifying special store actions.
• “To specify a duration or occurrence count for events (timing mode)” on
page 78
• “To insert a store action (state mode)” on page 79
• “To insert timer actions/events” on page 79
• “To insert counter actions/events” on page 80
• “To insert flag actions/events” on page 81
• “To insert a "reset occurrence counter" action” on page 83
• “To group events” on page 83
• “To use named events” on page 84
To specify a duration or occurrence count for events
(timing mode)
When working with advanced trigger functions or when you break
down other trigger functions, you can specify that an event be present
for a certain amount of time, or occur in a certain number of samples,
before the associated action is taken.
To specify a time duration for events
1. In the Trigger tab's Trigger Sequence area, if the present for > button is
not present, select the occurs button and choose present for >.