Merging modern software development with electrons and metal
Random header image... Refresh for more!

My Toolbox — Oscilloscope

Fluke 196 with Pelican Case

Fluke 196 with Pelican Case

Why do I have an oscilloscope?  The real answer is that scopes are cool, and many years ago, I couldn’t resist when Fry’s had Fluke Scopemeters on sale — at 50% off!  So I own a 100MHz dual trace Fluke 196 Scopemeter.  Later I bought the yellow the Pelican case for it; the two are a great combination.

Since software ties everything together, I’m also the “systems” guy, and thus I should be able to troubleshoot the entire machine.  I do use my multi-meter much more than my scope, but the oscilloscope is essential when troubleshooting encoders, hall sensors, and the occasional electrical glitch which won’t show up on a DMM.

I’ve used other scopes, such as the Tek THS720 handheld, the Tek TDS 210 desktop, Tek analog scopes, and a Heathkit analog scope.  Recently, I participated in a hands-on demo of the new Rhode and Schwartz RTO1014 1GHZ oscilloscope.  It’s quite impressive, even intimidating at first, with all the buttons and things it can do.  Fortunately, such high powered scopes aren’t needed for typical factory troubleshooting; a dual channel, 20-100MHz real time digital does fine most of the time.

There is uncommon feature that’s really handy: isolated channels (each channel’s ground is isolated from the others).  With a typical dual channel scope such as the TDS 210, I can only view one differential encoder signal (channel 1 probe on A+ signal, channel 2 on A- signal, display mode set to combine channels).  But with a dual isolated channels, I can view two differential signals (channel 1 probe on A+, channel 1 ground on A-, channel 2 probe on B+, channel 2 ground on B-).

Hand-held scopes, such as the Fluke 196 and Tek THS 720, typically have isolated channels, along with ruggedness, battery power, small size, and a hefty price tag.  However, a 4 channel desktop scope is often cheaper than a 2 channel isolated channel scope.

I once spent a lot of extra time because I was too enamored with isolated channels.  The system had a servo motor with the differential encoder output split, with one set of signals going to a motion controller and the other set going to a custom board.  The motion controller was counting correctly, but the custom board wasn’t.

I set up my Fluke 196 to look at the differential signals.  The B+/B- signal did look smaller (less voltage swing) than the A+/A- signal, but it had to be OK because the motion controller was picking it up.  So I started swapping out components — and kept getting the same problem.

I figured it out when I looked at each signal (A+, A-, B+, B-) individually; the B- signal was dead (because of a broken wire in the cable from the motor).  The motion controller worked because it was less sensitive, managing to count the smaller transitions.  My lesson learned: check everything, and don’t make unsupported assumptions.

3 comments

1 Vegard { 09.26.13 at 10:38 am }

Hello, I’m wondering what size is that peli case?

2 Tony { 09.26.13 at 12:05 pm }

It’s a Pelican 1500; they’re available starting at ~$100 online in various colors. It’s a really nice case.

3 Vegard { 09.26.13 at 1:04 pm }

Thanks. Yeah Pelican has a good quality feel over their cases. Already got one for some other instruments, but none for my 196B. :< Should get one. And a yellow one, makes you think it's fluke branded. 😛

Leave a Comment