There are some other factors here in play,
not just displaying the waveform or triggering,
as we say here in this metric.
The best triggering helps you see more of your signal.
In this case, we're about 200 times faster with the EXR Series, specifically.
We can also do faster hardware averaging.
If you're looking at averaging out noise out of a signal
or things like that,
we can do that over 100 times faster.
We can even do onscreen measurements faster.
We can also plot eye diagrams faster.
For those of you working on high-speed digital designs,
you probably know the pain of sitting there and waiting
for that unit interval count to accumulate
so you can have confident accuracy in your eye diagrams and things like that.
We can plot 50 times faster using this ASIC technology
in our new Infiniium line of oscilloscopes.
The next tool I'm going to show you
is a new tool that we've developed for our Infiniium products
called Fault Hunter.
This takes some of the guesswork out for you.
The issue we're looking at is about 1 in 200,000 or so,
which means at 200,000 waveforms per second,
the EXR Series is showing it on screen about once per second.
Imagine for a moment you had a problem
that was one in a billion,
or one in hundreds of millions or something like that.
You do a little bit of math there, and it may take minutes
for even the fastest oscilloscopes on the planet
to find this fault.
With Fault Hunter,
we've developed a tool that automates this fault-finding process for you.
I'm going to enable it,
and then we'll jump back to this slide.
I'll explain what the tool does.
I'm going to under the Analyze Quick Fault Hunter.
One great thing here is we do have a lot of quick hits.
If you're doing eye diagrams, jitter measurements,
Fault Hunter, we saw the quick measurements already.
We have a lot of one-click actions that let you jump into an advanced tool
which helps with repeatability and finding the tool to begin with.
As you can see, we've designed our menu structure
so everything you need is a click or two away.
There are a lot of things oscilloscopes can do nowadays.
Having quick-jump setups is pretty helpful.
I'm going to get that rolling.
Let's talk about what Fault Hunter does.
What it's doing is, first, you set it up.
You tell it what channel you'd like to analyze.
There are a couple different modes here.
We're going to use the Default Triggering mode,
which helps find rare faults.
What it's doing is using hardware triggers
to look for common signal problems.
You can tell it how long you'd like to run.
We selected 1 minute,
but you can run this test for up to 48 hours.
With hardware triggering enabled,
200,000 triggers per second for 48 hours,
it's something like 34 billion waveforms you can test,
and Fault Hunter can find a single error,
that single needle in the haystack, for you reliably
because of that ASIC triggering technology.
One you tell it that,
it begins its automatic setup and starts running tests.
The automatic setup it's doing,
it's using some common measurements,
like amplitudes and frequencies, data rates, and things like that.
It's trying to determine what's normal for the signal statistically.
It's capturing a mean and a standard deviation
for a number of different measurements.
Then, it's applying that to find glitches, slow edges, and runts.
To be very specific here,
the automatic setup is looking for glitches that are
50% of the data rate of the signal.
Whether it's a clock signal or a digital data signal,
data rate determines the smallest fundamental frequency of the signal,
then looks for anything half that size.
For the rising edges and the falling edges,
it's looking for anything three standard deviations slower
than the mean edge speed.
For the runts, it's using the top and base voltages
and some timing measurements to determine what a runt would be
in this signal statistically.
That being said, you can defeat or override
whatever Fault Hunter automatically determines on your behalf,
and you can come in here and manually modify
what you consider acceptable for your design.
Once all that's set up,
it can now run hardware triggering tests to look for these problems.
In this case, to find a glitch,
it was looking for anything less than roughly 70 ns, in this case.
If it was less than 70 ns, the oscilloscope would trigger.
It would fail that test,
and then we would have the ability to either rerun that test,
view a copy of that failure condition that got saved into memory,
or copy that failure condition into the trigger,
which I'll show next, which is pretty powerful
and helps you skip to the next step of debugging.
For this signal, it found some problems,
some slow edges, a runt, and a glitch.
We click View.
We can see a copy of that glitch pulse was saved into memory slot #1.
There are a number of waveform memories that the oscilloscope can save traces into
for either further review or to use as a comparison
versus a live waveform, for example.
Found that glitch there pretty readily.
While I was off perhaps getting a cup of coffee,
I come back, and the oscilloscope has found the problem for me.
That being said,
what Fault Hunter is doing here can be done manually
on any oscilloscope that may not have the Fault Hunter tool.
It just of course requires some extra setup
and may impact the repeatability of the process.
I can show you how to do that now.
I'll use a little bit of a shortcut here.
One of the other great features of Fault Hunter
is this Copy-to-Trigger button.
Triggering, for those oscilloscope pros in the audience,
is definitely the best way to go about finding problems.
Even if you have a slower waveform update rate,
if you set up the correct trigger condition,
you can always find the fault that you're looking for.
The problem is, you have to know the fault is there
and know how to characterize it to set up the trigger condition properly.
Let me show you what I mean by that.
I'm going to copy the glitch condition to the trigger,
close out of here,
and close out the math function--
or, sorry, the memory here.
Got to get back to where we were.
Now I'm going to go ahead and run the oscilloscope.
You can see, since I've clicked Copy to Trigger,
now the oscilloscope has been instructed
to only trigger and display information when that glitch is found.
What does that look like?
Up here, I can shortcut into this Trigger menu.
On Infiniium, this is what it looks like.
We get a list of triggers to select from--
edge, glitch, pulse width, various different ways
to describe the shape of a waveform.
In this case,
if we wanted to find this problem on our own,
we would have to know that we're looking for problems
on Channel 1,
that a pulse that crosses 1.05 volts up and down
in less than 69.8 ns.
Again, I could have set this up when I had the oscilloscope
in its slow mode,
and it would look just like this,
but I didn't even know to look for this problem,
because it wasn't appearing on screen.
It's a chicken-and-egg situation,
where the triggers work fantastic,
but only if you know what to look for,
and you only know what to look for
if the oscilloscope can show it to you.
That being said,
things like glitches are very common to look for in signals,
so the glitch trigger is fairly easy to set up.
You can come in here and just play around
with the time criteria until you find what you're looking for.
We also make it pretty easy for you to find the trigger that you need.
We have little shortcut buttons here within the Trigger menu itself,
but in this dropdown box, you can find shortcuts.
I can verbally describe what I'm looking for.
Maybe I'm looking for a pulse that is too narrow, a glitch.
I can click on this,
and it would automatically snap me into the pulse width.
Pulse width is a superset of the glitch trigger
that gives you a few more things to tinker around with.
It jumps you to that trigger for you to begin setting it up.
In this case, it's not set up correctly,
so the scope stopped triggering, but that's the idea.
We also have a gallery
so you can click in here and pictorially see
all the different types of trigger conditions
and hopefully find the kind of problem that you're looking for
using hardware triggers.
This is fantastic if you're looking for physical layer faults.
Again, an oscilloscope with a fast display speed
and waveform update rate helps you readily visualize problems
to help you set up a trigger condition to lock in on it.
Now that I'm triggered on it, I can take a screenshot.
I can make measurements specifically on the problem.
I can turn on other channels in my design
to see if this glitch correlates with something else.
Another great tool built into this oscilloscope,
and many oscilloscopes nowadays,
is a frequency counter.
I can measure the frequency of a channel,
but I can also measure the frequency of a trigger-qualified event.
I can turn this on, and down here,
it's covered up by my face a little bit, but you can see it, 23.809 Hz.
This is telling me this glitch is occurring roughly 23.8 times per second.
I can also do a period.
I can also totalize it.
Again, another great troubleshooting tool
built into oscilloscopes
to help you further not only identify the problem
but try to figure out what's causing it.
Ultimately, the oscilloscope can't solve that for you,
but we try to give you as many tools as possible
for you to put on that engineering hat
and figure it out.