A trigger is the condition that tells an oscilloscope exactly when to start drawing a waveform on screen. Without a stable trigger, a repetitive signal looks like a smear of overlapping traces rather than a clean, readable picture. Understanding trigger modes is one of the first skills that separates a confident oscilloscope user from someone fighting the instrument.
What a trigger actually does
An oscilloscope continuously samples the incoming signal, but it can only display a fixed window of time at once. The «trigger» defines the reference point inside that window: typically, the moment the signal crosses a chosen voltage level, moving in a chosen direction, rising or falling. Once that condition is met, the oscilloscope aligns every new acquisition to the same reference point, so repetitive waveforms appear stationary on screen instead of drifting.
Edge trigger: the starting point
The «edge trigger» is the simplest and most common mode. You set a voltage level and a slope, rising, falling, or either, and the oscilloscope starts the acquisition the instant the signal crosses that level in that direction. It is the right choice for most clock signals, simple digital lines, and general purpose debugging.
Pulse width trigger: catching glitches
A «pulse width trigger» fires only when a pulse is shorter or longer than a specified duration. This is the mode to reach for when hunting an intermittent glitch: a narrow spike caused by crosstalk, a bounce on a switch, or a timing violation on a digital bus that only shows up occasionally and would otherwise be invisible on a simple edge trigger.
Pattern and logic trigger: multiple conditions at once
When the event you care about depends on the state of several signals together, for example a specific combination of address lines, or a control signal that is high while a clock is low, a «pattern trigger» or «logic trigger» lets you define that combination directly, instead of trying to catch it by chance with a single edge condition.
Serial bus trigger: decoding protocols
Modern oscilloscopes, including entry level models such as the Rigol DHO900, can trigger directly on the content of a serial protocol: a specific I2C address, a particular CAN identifier, or a UART byte value. This turns the oscilloscope into a protocol aware instrument, letting you isolate the one transaction that matters out of thousands on the bus.
Choosing the right trigger for the job
| Trigger mode | Best suited for |
|---|---|
| Edge | Clocks, simple digital signals, general debugging |
| Pulse width | Glitches, intermittent faults, timing violations |
| Pattern or logic | Multi signal conditions, bus states |
| Serial bus | I2C, SPI, CAN, UART and similar protocol level events |
As a rule of thumb: start with an edge trigger to get a stable picture, then move to a more specific mode only once you know exactly which event you are trying to isolate.
ALLdata's role
Choosing the right oscilloscope for a given triggering task depends on bandwidth, the number of channels, and the protocols you need to decode, not only on price. ALLdata's engineering team helps laboratories and production departments match the instrument to the application, from entry level bench oscilloscopes to high bandwidth models for signal integrity work.
Not sure which trigger capability your application actually needs? Talk to an ALLdata engineer, or browse our oscilloscope and test instrumentation range.