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
149
Chapter 3: Reference
The Trigger Tab
• Find 2 edges too close together
Becomes true when the second specified edge occurs within a specified
time after the first specified edge.
• Find 2 edges too far apart
Becomes true when the second specified edge does not occur within a
specified time after the first specified edge.
• Find pattern occurring too soon after edge
Becomes true when a specified pattern occurs within a specified time after
the first specified edge.
• Find pattern occurring too late after edge
Becomes true when a specified pattern does not occur within a specified
time after the first specified edge.
• Find glitch
Becomes true when the specified glitch occurs in one sample.
• Wait t seconds
Becomes true when the specified amount of time has expired.
• Wait for arm in
When the logic analyzer is armed by another instrument (as specified in
the Intermodule window), this trigger function becomes true when the
arm signal is received.
• Wait for second analyzer to trigger
When the logic analyzer's pods are assigned to two analyzers, this trigger
function becomes true when the other analyzer triggers.
• Wait for flag
Becomes true when the specified flag has the specified value. This trigger
function tests for a flag event.
• Set/clear/pulse flag
Becomes true on any sample and sets, clears, pulse sets, or pulse clears
the specified flag. This trigger function inserts a flag action.