A big part my New Year’s Resolution to improve my overall design process was better testing. Better testing is an important part of better and more intentional design, but it means having tools that you can trust and that can consistently give you the results you need.
While I’ve built up a decent little collection of toys over the years, I spent quite a bit of time late 2011 figuring out what I wanted to add or replace on my workbench in 2012 to be able to improve projects I’m working on. At the top of the list was a faster mixed-signal oscilloscope, followed by a more reliable bench-top multi-meter, and a decent function generator rounding the big ticket items out.
After spending quite a bit of time selecting a scope that matched my budget and requirements, and looking (importantly!) at the ecosystem around that scope, I settled on Agilent’s new MSOX2000/3000 series — specifically, the Adafruit Christmas Elves picked out an MSOX2024a (the screenshot above was taken on this scope). These scopes (in my opinion) are an excellent value for a mid-range scope, and really raise the bar for the competition in the $2-5K range. I’d like to write a few blog posts on the reason behind that choice and the thinking behind the whole list of items above, but as a first foray into that I thought I’d try to explain some of the details you should keep in mind if you’re thinking about a scope yourself (probably the most useful tool on any EEs workbench after a multimeter).
The most obvious factor when choosing an oscilliscope is bandwidth. 50MHz is better than 20MHz, and 100MHz is definitely better than 50MHz, etc., but what does that number really mean, and how fast is fast enough for your needs? There are already some good resources out there that go into exhaustive details on this … but for the executive summary read on.
The biggest influence on the price of a scope is it’s bandwidth (50MHz, 100MHz, 200MHz, 350MHz, … 2GHz, etc.) and the number of analog samples per second that it can read (1Gs/s, etc.). These two numbers are related, and most people know that the samples per second needs to be at least 3-5 higher than the bandwidth for accurate results (meaning a 100MHz scope should have ~500Ms/s, or even better 1GS/s for reliable results).
But what does the 50MHz or 100MHz really mean? If I purchase a 50MHz scope can I accurately capture and measure 50MHz worth of data? The answer (like everything else in engineering) is: it depends. You should be able to measure frequency up to and even beyond the maximum rated value, so if determining frequency is all that matters (checking how accurate the output of an oscillator is, the pixel clock on an LCD controller, etc.) you can safely go up to the maximum. Where things become more fuzzy is amplitude (the upper and lower voltage values measured by the scope).
The bandwidth of an oscilloscope actually indicates the point at which the measured amplitude on an amplitude/frequency chart has decreased by -3dB (or 70.7%) of the original value! Your frequency will be good up to and perhaps even slightly beyond the maximum rating of the scope, but at the maximum rated frequency, the amplitude will be ~70% the actual value so you’re 5V signal will actually show up as ~3.5V, and 3.3V will show up as ~2.3V! This can cause you to panic and think you have a bad oscilloscope, or that your PCB or circuit is rubbish, simply because you might not have been aware of this principle.
As an example, have at look at the screenshots below. They’re both capturing the 3.3V 40MHz pixel clock of a large (800×480) TFT LCD, and the frequency is the same, but the peak to peak voltage on them is very different. The Tektronix image is from a 350MHz oscilloscope (using a 500MHz probe since this is also important!), and the other is from a 50MHz Rigol scope (sw ‘upgraded’ to 100MHz) using the probes in 1x mode (which is limited to 7MHz bandwidth). The peak to peak voltage (VPP) on the Tektronix scope is accurate (it says 3.4V since there is a slight peak on the rising edge), but the Rigol only shows 1.4V, though both capture the 40MHz frequency correctly!
Why is that, you ask? The 1.4V is so low because you also need to pay attention to the maximum bandwidth of the probes you’re using with the scope, since the same effect applies to them as well as the bandwidth on the scope itself! Use a slow probe on even the most expensive scope and you’ll be throwing all of that resolution (and money) out the window. In the case of the Rigol scope I was using the probes in 1x mode (you can select between 1x and 10x directly on the probes), which is limited to 7MHz (at 10x they are much more useful with 150MHz bandwidth). Make sure you know the bandwidth of not only your oscilloscope, but of the probes you have attached to them as well. Unless you are measuring fairly slow signals with the Rigol scopes, you should always use the 10x mode since the probes will perform much better than in 1x mode, though you need to remember to multiply all the displayed values by ten after the fact (so 300mV is actually 3V, etc.).
The following chart (from Tektronix “ABCs of Probes Primer”, p.35) illustrates the relationship between bandwidth and amplitude:
What does this have to do with selecting an oscilloscope? The biggest take away is that if you need to accurately measure not just frequency on your oscilloscope, but amplitude as well, you need to make sure that the rated bandwidth of both the scope and the probe attached to it are well above the signal you need to accurately capture. If you need the amplitude to be accurate to ~1%, you need to derate your scope by a factor of 0.1x, meaning that on your 100MHz scope you can only capture 10MHz with a 1% error in amplitude. If you require 3% accuracy, you need to derate it by a factor of ~0.3x, so a 100MHz scope can accurately measure 30MHz to 3%.
Does this mean you need a $15K 500MHz scope to accurately measure anything, and the entry-level 50MHz scopes out there are useless? Absolute not! I’m still convinced the entry level digital scopes out there (Rigol, etc.) are an absolutely amazing deal and an exceptionally smart investment for any budding young engineer … but you do need to understand the table above to get the most from them. This table allows you to measure signals at the maximum bandwidth of your scope … you might just need to do a bit of math to scale them up after the fact.
Oscilloscopes are incredibly useful tools and one of the best investments you can make, but it does take time to understand the limitations of this type of test equipment. As with anything else in electronics, you really need to understand where the weakest links in your system are, and if you can’t replace those weak links, you at least need to fully understand them and compensate for that in the best way possible. I wouldn’t hesitate to recommend any serious newcomer to electronics picks up an entry-level Rigol oscilloscope. It’s a far better investment than any of the toys on eBay, and an exceptional value for the money … but it is important to learn your tools, and to know where their limits are.
The moral of the story: for the least amount of work on your part, always buy the best tools you can afford. If your means are limited, still buy the best tools you can afford, but make sure you understand what you are measuring and the limitations of your tools, and find creative ways to work around them.
If you’re new to oscilloscopes or just looking for a bit more information on this or other subjects, the following links might be useful to you:
- Evaluating Oscilloscope Bandwidth for your Application (Agilent)
- ABCs of Probes Primer (Tektronix … registration required)
- Evaluating Oscilloscope Fundamentals (Agilent)
- XYZs of Oscilloscopes (Tektronix … registration required)
Have an amazing project to share? Join the SHOW-AND-TELL every Wednesday night at 7:30pm ET on Google+ Hangouts.
Join us every Wednesday night at 8pm ET for Ask an Engineer!
Learn resistor values with Mho’s Resistance or get the best electronics calculator for engineers “Circuit Playground” – Adafruit’s Apps!
Maker Business — Bunnie working with Snowden on phone tracking and also taking on the DMCA Section 1201 with the EFF
Wearables — Gluing gloves
Electronics — Code like everyone’s watching
Biohacking — Melatonin Hacking – Avoiding Blue Light Near Bedtime
Sorry, the comment form is closed at this time.