Slashdot Mirror


Oscilloscopes For Modern Engineers?

Every few years someone asks this community for advice on oscilloscopes. Reader dawning writes "I've just graduated with a degree in Computer Engineering (and did a Comp Sci one while I was at it) and I'm finding myself woefully under-equipped to do some great hardware projects. I'm in major need of a good oscilloscope. I'm willing to put down $2,000 for a decent one, but there are several options and they all seem so archaic and limited. I'm happy to use something that must be controlled through a PC if that gives me more measuring features. What would you, my esteemed Slashdot colleagues, get for yourself?"

67 of 337 comments (clear)

  1. An old Tektronix is fine for a modern engineer by NixieBunny · · Score: 3, Interesting

    I use an R7704 at home, and a 7633 at the office.

    --
    The determined Real Programmer can write Fortran programs in any language.
    1. Re:An old Tektronix is fine for a modern engineer by stevenvi · · Score: 3, Informative

      A new Tektronix oscilloscope will work as well. When I was an undergrad my colleagues were convinced that you need analog ones to make proper measurements, but I've had great success using digital ones. I actually prefer them.

      Without a definition of what "good" means or what your needs are, I don't think that anyone can give you any sort of advice. I personally would never use one that had to be controlled through a PC. Having to drag a laptop or something all around the electronics of an experiment would be a major pain. (I've only used them in the context of the detector and apparatus signals in physics experiments.)

    2. Re:An old Tektronix is fine for a modern engineer by Dreadflint · · Score: 2, Funny

      My Tektronix 585 is fine for a modern end table. I got it for free and it still works. :)

    3. Re:An old Tektronix is fine for a modern engineer by harrkev · · Score: 5, Informative

      I work for Agilent. Trust me. They still call them scopes...

      And for the original poster, be sure to check out how many waveform per second the scope can store. That is the reason that some people do NOT like digital scopes is that they first used a digital scope that cannot trigger and re-arm again in a reasonable period of time. Let's assume that you have a waveform that has an occasional glitch, but you can't set a trigger for it, so you have to catch it by chance. If your scope can capture 10,000 waveform per second, you stand a 10x greater chance than one that can only capture 1,000 waveforms per second. I believe that Agilent wins in this category.

      --
      "-1 Troll" is the apparently the same as "-1 I disagree with you."
    4. Re:An old Tektronix is fine for a modern engineer by Lord+Ender · · Score: 4, Insightful

      Ah, but you are likely working as an electrical engineer. This fine young man will most likely get a job in IT. My suggestion to him is to hold off on the hobby scope for a couple years. By that time, his soul should be crushed sufficiently that he gives up on ambition entirely and has no need for the device.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    5. Re:An old Tektronix is fine for a modern engineer by altzone · · Score: 4, Informative

      $2000 is a LOT to spend on a scope if you have to ask such a question. Depends on the specs you need, but I'd get a cheaper one and spend the rest of your money on some other gear. The Rigol DS1052E at $400 is by far the best bang-per-buck. I have a review of it, a teardown, and info on how to hack it to a 100MHz version here: http://www.eevblog.com/2010/03/31/eevblog-70-turn-your-rigol-ds1052e-oscilloscope-into-a-100mhz-ds1102e/ http://www.eevblog.com/2010/04/18/eevblog-77-rigol-ds1052e-ds1102e-oscilloscope-hack-update/ http://www.eevblog.com/2009/10/12/eevblog-37-rigol-ds1052e-oscilloscope-teardown/ http://www.eevblog.com/2009/07/19/eevblog-19-rigol-caught-with-their-pants-down/ http://www.eevblog.com/2009/04/05/eevblog-1-rigol-ds1052e-oscilloscope-reviwed/ I also compare PC based and bench oscilloscopes here: http://www.eevblog.com/2009/06/17/eevblog-13-part-1-of-2-digital-storage-oscilloscope-tutorial/ and http://www.eevblog.com/2009/06/17/eevblog-13-part-2-of-2-pc-based-digital-storage-oscilloscope-comparison/ There is no need to get a PC based oscilloscope unless you have a specific need for one. Regards Dave EEVblog

    6. Re:An old Tektronix is fine for a modern engineer by John+Miles · · Score: 2, Informative

      I like the Tek 2430/2432/2440 scopes a lot, and used one for years in conjunction with a 2467, for those cases where analog-scope performance was needed. Apart from a few considerations like record length, this combination could easily stand up to any DSO costing less than several thousand dollars.

      With the 2430-series scopes, the key points to watch out for are 1) make sure it passes its power-up self tests, as the CCD chips used for acquisition are no longer available; 2) avoid the original 2430s with no GPIB port if you think you will ever want to record screenshots from it; and 3) always use an external fan to cool the chips on the main board when servicing it. These scopes seriously stretched the performance envelope available at the time, and those custom chips can be replaced only by buying a parts mule.

      Of course, if good ones are going for $200 with probes, it's probably a good idea to just go ahead and spend another $50-$100 on a parts unit to go with it...

      --
      Dahlmann tightly grips the knife, which he may have no idea how to use, and steps out into the plain.
    7. Re:An old Tektronix is fine for a modern engineer by Andy+Dodd · · Score: 2, Informative

      Despite the rather "textblock"ish formatting of the above post, I do believe that the Rigol DS1052E is one of the best entry-level choices right now, and is GREAT bang-for-the-buck. I have one and it has proven very useful. My only regret is that I purchased it before it got price-dropped to $400. (I paid around $530 plus New York State sales tax from Saelig.)

      FYI, Rigol is the manufacturer of Agilent's entry-level units at this point.

      To the article poster: You indicate you've done some looking and have been unhappy with what you've found. What have you looked at and in what way have you found it lacking? What are your requirements?

      Strangely enough, the "PC-only" units, while you would expect them to provide more bang for the buck, almost universally are inferior. There's a horrible trend in that market to advertise high analog bandwidths without the samplerate to back up that bandwidth. General rule of thumb is that a good scope needs 10x its analog bandwidth in samplerate to capture transients. You're probably OK with only 5x. Many of the PC-based scopes don't even meet the Nyquist criterion! (The Nyquist criteria pretty much lets you capture a sine wave at the analog bandwidth. Keep in mind the analog bandwidth is usually a cutoff frequency, and it can get information from higher frequencies.)

      --
      retrorocket.o not found, launch anyway?
  2. Heathkit of course, bitch! by LibertineR · · Score: 2, Funny
    Just kidding. Memories...... Built two Heathkid O-Scopes as a child.

    As for your question, who the fuck knows?

    1. Re:Heathkit of course, bitch! by lightneo · · Score: 2, Funny

      ive got a working heathkit o-12 i would be willing to part with for 2 grand!

  3. outsource it to india by Anonymous Coward · · Score: 2, Funny

    have them take the measurements for you.

    itll give you great experience in The Real World.

  4. Kazkek by Anonymous Coward · · Score: 5, Informative

    May I suggest you get a DAQ usb card and Labview from National Instruments. Probably some of the best investments you can do. You can do many things with a DAQ card and Labview including building your own digital Oscilloscope.

    1. Re:Kazkek by Anonymous Coward · · Score: 3, Informative

      While I'm a gigantic LabVIEW fanboy, those USB DAQs don't have the bandwidth of a real oscilloscope. IIRC, most of those USB ones sample at 50 - 500 kS/s. Your low end digital scope will have a bandwidth of 20 MHz or more.

    2. Re:Kazkek by f16c · · Score: 2, Interesting

      Bullshit!
      Unless the OP uses LabVIEW at work or school (and is allowed to take a copy home to play with) it's a hell of a lot more money than a decent Tek o-scope. Daq cards are fine for some things but troubleshooting isn't one of them. Stay away from used HP scopes since the damn things never triggered right even when they were new.

      --
      bob@Osprey:~>
    3. Re:Kazkek by SupplyMission · · Score: 5, Informative

      By all means, buy National Instruments hardware. It is fantastic. I have deployed it on a number of production systems that run for days and days and days without a glitch.

      As for Labview, stay the fuck away from that steaming pile of dogshit. It is a great way to waste lots of time and give up your sanity (and possibly your anal virginity) unless you feel like fucking around at your lab bench and drag-n-dropping some blinky lights and text boxes to impress your PHB. Oh yeah, and it's also great if you enjoy having fresh-out-of-college, inexperienced National Instruments tech support fuckwads (i.e. never having done any actual work with data acquisition or signal processing in their lives) repeatedly tell you, "OMG, change the way you think! You're so wrapped up in the text-based language tunnel vision! LOL!" whenever you get frustrated because Labview actually slows you down and doesn't help you get your results.

      Oh yeah, I almost forgot, it will also cost you an arm and a leg. A hardware and software (i.e. Labview) package will let you look at signals in the 10MHz range and above will probably run you at least $10-15k.

      In my day to day work, I prefer to remain in the "text-based language tunnel vision." That is, I prefer to use a well-designed C or C++ API to write programs that actually work in a predictable and reliable manner. (The NI-DAQmx API is actually very powerful and easy to use.) That way, I don't have to scroll around in a blinding maze of brightly colored connector lines and boxes and stuff, just because some National Instruments fucktard decided that "text-based languages" are just too, like, texty and complicated and not very much fun, yay! Yuck.

    4. Re:Kazkek by dargaud · · Score: 4, Informative
      I've long used LabWindows at work and stayed away from LabView. For those who don't know, they both share the same libraries but the former is pure ANSI C while the latter is boxes+spaghetti connectors. 3 years ago I did a data acquisition project that was also given to another team to do in LabView in parallel. After 3 months I was done and the project went into operational mode. The LV project was hitting some snags so I made some DLLs with all my underlying code for them and they would only need to add some pretty boxes on top. After 3 years their project still doesn't work properly. LV is impossible to debug (retroactive timings anyone ?). And while you can write spaghetti code in C, when you do so in LV it actually LOOKS like a plate of spaghetti !!!

      And don't get me started on the fuckwads who recently tried to convert me to UML as a better way to do real-time programming. What a crock of shit dreamed up by computer theorists who've never actually run one of their programs.

      --
      Non-Linux Penguins ?
    5. Re:Kazkek by Anonymous Coward · · Score: 2, Informative

      I've long used LabWindows at work and stayed away from LabView. For those who don't know, they both share the same libraries but the former is pure ANSI C while the latter is boxes+spaghetti connectors. 3 years ago I did a data acquisition project that was also given to another team to do in LabView in parallel. After 3 months I was done and the project went into operational mode. The LV project was hitting some snags so I made some DLLs with all my underlying code for them and they would only need to add some pretty boxes on top. After 3 years their project still doesn't work properly. LV is impossible to debug (retroactive timings anyone ?). And while you can write spaghetti code in C, when you do so in LV it actually LOOKS like a plate of spaghetti !!!

      I've been using LabView professionally for a few years now. While I hate LabView with a passion I have to clarify a few things:

      Many people who insist on using LabView don't come from a strong programming background, so their project turning out horribly was probably in part because they just aren't very good programmers. Unfortunately for some reason they think LabView somehow changes this.

      LabView actually isn't bad at debugging unless you're trying to do multi-threaded stuff. In which case you should probably just punch yourself in the face instead. I would say LabView is about on par with any decent debugger.

      So for anyone really considering LabView: don't. I've thought about this and really can't find anything it does well. Except what it was designed to do, which is to make certain people feel less awkward using it because hey it looks kind of like a circuit diagram.

      I could go on for hours about LabView but let me just leave with this fun tidbit:

      It stores your code in a proprietary binary file. Think about how well this is going to work with any sort of software management system. By the way when you change a file any file that calls it will re-compile itself and store the compiled version into that same binary file, prompting you to save on exit. Hello, conflict nightmare! Also, it re-compiles and asks you to save all the time when you move it to other computers or look at it funny. Oh and forget about automated merging. Technically it can sort of merge but you still have to clean up the code manually afterward. Also, have fun maintaining legacy code when you upgrade to a new version of LabView for the next project. If you save the old files with a newer version of LabView they can no longer be opened with the old version. And it's not like any other editors can open those files!

    6. Re:Kazkek by Dragoon235 · · Score: 3, Informative

      I will say this. Labview is great for a quick-and-dirty setup or small application. If you need to do anything more complicated, you will find that the entire development environment is incredibly lacking and highly tedious, and there is no meaningful literature on application design in Labview (90% of Labview books are "hurf-a-durf you connect one box to another and it does things, think outside the c++ box man").

      As someone who writes VHDL, Verilog, C++, and Matlab on a daily basis, I understand both control flow and data flow programming, Labview is some perverted amalgamation of the two. It lures you in under the guise that you will not need to learn any GUI programming, and then screws you over in anything more than the basics. For example, in a data flow paradigm, pointers have no meaning, as all data is by value. Nearly every complex data type is handled with pointers, and "magical pointer functions" which make life hell, as they do not fit into the paradigm. So then they add "classes", which is a way for them to say that they somehow trump C++ and Java. Upon reading the fine print, one discovers that the class system is similarly FUBAR'd. Then there's the issue of inserting something into code. In a text based language, hit enter, and begin typing. In labview, delete a shit-ton of wires, drag and drop portions of the diagram, put in new bright colored squares, connect even more wires, make everything look readable (see: drag 'n drop ad nausium).

      But, if you need a quick and dirty state machine to control something, and you don't mind a polling architecture, I can implement that in about a day...

    7. Re:Kazkek by Andy+Dodd · · Score: 2, Informative

      In one of my previous jobs, I had the task of getting a test setup controlled by LabView working in our facility.

      Tiny little differences in our setup completely broke LabView, and the "point, click, drool" GUI really insulated you from what was going wrong and how to fix it.

      I was able to almost rewrite the whole damn thing in Perl, including adding new test instrument classes to Jeff Mock's long-unmaintained Perl GPIB modules, in less time than it took to try and fix that thing.

      Even though Jeff's libraries are long unmaintained, they're still a great place to start. Perl is great for test equipment automation IMO. (However, Jeff's libraries aren't so hot for trying to interface with modern interfaces such as USB-TMC. USB-TMC is just plain not well supported in Linux right now, don't know about Windows.)

      --
      retrorocket.o not found, launch anyway?
  5. dumpster diving by iveygman · · Score: 2, Insightful

    Back in graduate school, my roommate and I would dumpster dive and repair broken ones. More often than not, it's a pretty simple fix.

    1. Re:dumpster diving by Anonymous Coward · · Score: 3, Funny

      its funny that electronics engineers throw out their broken electronics.

    2. Re:dumpster diving by Ungrounded+Lightning · · Score: 3, Interesting

      Not really.

      If they need it accurate and traceable they'd have to pay a lab to calibrate it after it was fixed. Such a lab would reject it due to it being fixed (and charge a pretty penny with no calibrated scope at the end of the process.) So they're stuck.

      (This reminds me of a story my wife tells about a lab PC that had a bad case of infant mortality. The local techs wanted to fix it themselves. She pointed out it was still in warranty - so the thing to do was send it back for fix-or-replace for free, rather than void the warranty and maybe end up with a broken machine and nothing (but wasted engineer time) to show for it.

      Fixing a scope adequately for home use is another matter. Then, if you ever need serious accuracy, you can do the same sort of compensation hacks that were done back in the tube days, when stuff drifted all the time and you couldn't just have a lab tune up anything complicated and expect it to stay tuned.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    3. Re:dumpster diving by vlm · · Score: 4, Insightful

      What lab will reject an instrument "due to it being fixed"?!

      You used a 10% resistor that seems "close enough" the original was 1%. The calibration lab is used to making "minor tweaks" but having to twist all those trimmers practically all the way is going to take forever and piss them off. On the other hand, in Moms Basement, watching a Star Trek movie marathon while calibrating a scope is considered fun, not a waste of time.

      You used inductive metal film resistor which screws up the high frequency performance instead of the specified non-inductive carbon comp resistor. It'll never work above 90 MHz again. The calibration lab will throw a fit because it won't calibrate at 100 MHz. However in Moms Basement you are thrilled to own a "90 MHz scope" even if the front panel label claims its a 100 MHz scope, especially since the highest clock frequency you'll likely subject the thing to anyway is probably low double digits.

      You used the totally wrong temperature comp capacitors, and trimmed the rest of the scope so it'll work fine at 70 F. Unfortunately the industrial specs say it has to be calibrated from 32 F to 125 F so it simply can't pass calibration. The calibration lab will throw a fit, although it works fine in Mom's temperature controlled Basement.

      That's before you start trying to mix old Tektronix scope silver bearing solders with traditional Pb/Sn and with modern lead free. I understand old fashioned Pb/Sn solder will corrode the plating off the Tek silver solder ceramic things.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
    4. Re:dumpster diving by tibit · · Score: 2, Interesting

      I completely understand what you're saying, but you list some very specific circumstances. A cal lab nominally is supposed to calibrate, not repair, so they'll simply give up when they use up the adjustment range and they're still out of spec. That's hardly rejecting "due to it being fixed" -- any number of things, including simple passage of time, can make an instrument do this. They won't try to understand why it doesn't work, just that following the cal procedure (usually with lots of in-house clarifications/improvements) the tech gets stuck at a point and that's that.

      For older equipment, some cal labs offer calibration bundled with repairs, so that they'll try to fix precisely what you're talking about (when it's still fixable).

      Quite often it's very obvious that someone was "working" on an instrument, and you end up undoing most of such "fixes" -- I agree there. This can potentially take many billable hours, so if they are given a go to repair, they can love such jobs.

      --
      A successful API design takes a mixture of software design and pedagogy.
    5. Re:dumpster diving by GizmoToy · · Score: 2, Informative

      Our calibration company seals up all edges of the device that give access to its insides after it has been calibrated. Break those seals, and you're in trouble... they'll refuse to calibrate it in the future because of the risk it's been altered. This is forgiven if you provide paperwork from the OEM that they themselves did the repair on the unit.

      I don't know that all calibration houses are this strict, though. You could probably find one that would pass your modified instrument if you really wanted.

  6. modern engineers solve problems. by larry+bagina · · Score: 2, Funny

    Like: How am I going to stop some big mean mother hubbard from tearing me a structurally superfluous new behind?

    You, sir, are no engineer.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  7. What do you need it for? Frequency range by line-bundle · · Score: 3, Funny

    Without know what frequency range, voltage range, connectivity requirements (is computer connection USB or serial port?) I cannot help you in your selection.

    OTOH you can give me the $2000 and I can give you my blessing.

    1. Re:What do you need it for? Frequency range by joe_frisch · · Score: 2, Insightful

      Not just funny, also correct. What is your application?
      Digital or analog?
      What speed signals?
      how many channels?
      Do you need any fancy triggering (often needed for digital)?
      Are you using to for data acquisition or to debug circuits?

      I'm not trying to make this tough, but the more you know about your application the better you can do at buying what you need and not a lot more.

    2. Re:What do you need it for? Frequency range by Tigersmind · · Score: 2, Funny

      Forget him!
      I will give you my blessing for $1000.

  8. O-scope experiences. by gwdoiron · · Score: 2, Informative

    What you should buy depends on what you plan to do, obviously. I've used several of the korean imports (Owon, Rigol) and although the feature set on those is incredible for the price, the units themselves have strange firmware problems that can be maddening when they strike. Also, the knockoff scopes can't seem to get "Automatic" triggering correct (they only sweep 3 or 4 times a second, no matter how fast you crank up the sweep rate, and that can be annoying when you are monitoring a signal), the Tektronix scopes are much better with regard to this feature.

  9. Tek 1012B by DoctorNathaniel · · Score: 3, Insightful

    I'm rather fond of the low-end Tek scopes. The LCD screen is a little slow, and there's only 2 channels, but these are not huge limitations for most basic work. I use these teaching physics and intro electronics to undergraduates - they're easy to use, lightweight, and can store data through USB or pen drives. 100 MHz for about $1200, which is OK for general use.

    1. Re:Tek 1012B by marcansoft · · Score: 4, Interesting

      Or you can get a $370 Rigol DS1052E, and software-hack it to enable 100MHz mode. Not quite as good as a Tek, but significantly cheaper and well worth the money, especially if you're on a smaller budget. I recently got one (it's about time I bought a scope) and I've been quite happy with it for my purposes.

      Info on the hack here.

    2. Re:Tek 1012B by bushing · · Score: 2, Informative

      It's also worth pointing out that Rigol apparently makes some of Agilent's low-end scopes for them, so the fact that they aren't a household name doesn't mean all that much.

      The Rigol scope has a lot of nice features that you wouldn't expect to find on a cheap scope -- it can take screenshots and store them to a USB thumb drive or print them to a USB printer, you can connect it to your computer to control it or acquire data via USB or RS-232, etc. It actually oversamples at 1 Gigasample/second -- there have been a number of EEVblog shows about it, talking about its performance, the parts that go into it (and the corners they did cut to get the price down!), etc. Google "eevblog rigol" to find the rest of them.

  10. See Slashdot circa 2001 by Qubit · · Score: 3, Informative

    Building a Cheap Oscilloscope Using Your PC?

    There are some interesting suggestions there.

    I'm thinking that some of the more adventurous open hardware folks might think about working on a completely open hardware scope. I mean, what's better than being able to use open tools to build open projects?

    --

    coding is life /* the rest is */
  11. Ebay by Charliemopps · · Score: 3, Insightful

    Got mine on ebay for a ridiculously low price... but like someone else mentioned, what you use it for is rather important.

  12. Get a Digital Radio by tibit · · Score: 2, Interesting

    Probably the best deal would be to get a digital radio. If you can live with ~150Ms/s (a tad slow, but hey), then a cheap thing to do would be to get a digital radio (SDR) system. Say Mercury SDR. Those things typically have a good, 16 bit 100+Ms/s ADC front end, feeding into an FPGA that can do a lot of processing goodies, with low noise, and you should be able to hook up a Tek 7k plugin as a front-end after a few tweaks (simply to get going). You can get everything for $700. You have open source software, full documentation, and you can put a lot of very interesting signal processing on the FPGA. Keeping sampler's speed limitations in mind, you can otherwise easily match performance of many lower-end spectrum analyzers, and $20k+ scopes.

    There are no $2k digital scopes with any decent feature set to speak of, even second-hand ones.

    If you're into tweaking analog, then a Tektronix 7k mainframe with proper plugins gives you everything you may need. Heck, you can even get a simple logic analyzer for those. With *analog* zoom, no less.

    --
    A successful API design takes a mixture of software design and pedagogy.
    1. Re:Get a Digital Radio by FilthCatcher · · Score: 2, Funny

      Building it wouldn't be too hard as long as he's got a decent sco... oh. wait. never mind.

    2. Re:Get a Digital Radio by tibit · · Score: 2, Interesting

      To get the basics going, you need a working SDR receiver -- you just buy the thing. My coworker recently got one -- the post-processor card with USB output (Cyclone II based), the sampler card with Cyclone III and 16 bit 160 MSPS LTC ADC, and a backplane and power supply. The first two were assembled.

      This is quite a decent *receiver*, it has a dynamic range that's pretty much unheard of on oscilloscopes. Would make a half-decent spectrum analyzer, too. Once you add a DC-coupled front end, you may as well have an attenuator with two or three settings (say 10V/div, 1V/div, 0.1V/div), the ADC's resolution is enough to deal with it. Testing it can be done using itself -- the proof is in the pudding, I mean in the stuff you acquire.

      Repurposing say a 7A13 plugin for input conditioner can be done without an oscilloscope, a DVM is all you need to get operating points right, and then you watch the signals using the device itself.

      --
      A successful API design takes a mixture of software design and pedagogy.
  13. Scopemeter 199C by mpoulton · · Score: 2, Insightful

    I am lucky enough to have a Scopemeter 199C. It rules. If you can possibly swing the cost, I'd highly recommend it. This model has remained Fluke's top of the line portable DSO for almost a decade, and the price has not changed for years. Portability is a great advantage for all sorts of applications, and the scope itself includes a full complement of great features including spectrum analysis, cross-channel math functions, and full DMM capabilities separate from the scope hardware. The computer interface and software is nice too. Probes and accessories are extremely expensive though, so keep that in mind.

    --
    I am a geek attorney, but not your geek attorney unless you've already retained me. This is not legal advice.
  14. Don't settle for USB scopes by gardyloo · · Score: 2, Informative

    The USB scopes are maddeningly horrible at triggering, at sample rates, and at aliasing. You're much, MUCH better off going with a stand-alone scope (LeCroy, Tektronix, Agilent) than any of the ones run by PC. LeCroy doesn't seem to provide much in the way of repair schematics, but Tektronix and Agilent are pretty good in that respect. I'd spring for one of the nicer Agilent/HP or Tektronix scopes, frankly, or even a LeCroy, but never something which is limited to being run by PC solely.

  15. What are you looking for? by Cylix · · Score: 2, Informative

    This is a bit light on the requirements, but there wasn't exactly a defined need.

    So generally speaking you should form some criteria.

    Number of inputs, frequency spectrum, what comparative features do you need.

    Next, if you are willing to purchase something used and have it tuned/repaired there can be considerable savings. Up one level from this is a direct refurbishing company that guarantees a functional and re-tuned unit.

    Now, we all enjoy new and shiny toys, but the trick is being honest with yourself.If it's going to be used for hobby grade activities then don't fall into the trap of wanting the same things you might use at the office. While I would like some of the severs I actually have at work I would not spend the several thousand it would take to actually purchase one of them.

    That said I would generally avoid ebay because most refurb shops will sale you the same thing on their site without the wait.

    --
    "You should always go to other people's funerals; otherwise, they won't come to yours." -- Yogi Berra
  16. USBee by bsDaemon · · Score: 2, Informative

    USBee has usb-based, software-driven oscilloscopes and logic analyzers to plug up with your computer. Not exactly the old, free-standing devices, but it might work for you. The price looks about right, too.

  17. My take by Andrew+Sterian · · Score: 5, Insightful

    Don't skimp. Get a good one, name brand (Tek, Agilent, LeCroy, etc.) at least 100 MHz bandwidth (the higher the better), 4 channels if you can afford it, some way to get data off the scope and onto a USB drive/network. Everything else is fluff and you can pay for it if you want, but I'd say the above are non-negotiable.

    Don't even think about a PC-based scope. A scope is a standalone instrument, always has been, always will be.

    1. Re:My take by scribblej · · Score: 2, Insightful

      I disagree about "Don't skimp". I've got a 100MHz 2-channel scope from Owon in China, and it is great. Only set me back $300. I could buy ten of them for the price of a single Tek. I also have an old analog Tek but it never gets used.

    2. Re:My take by schwep · · Score: 3, Informative

      I agree with Andrew. I like having a stand alone instrument that data can be sent to the PC. It really depends on what you're going to be doing as to what you should buy... For $2k you can get a great deal on a used one (like from ebay) but you'll need to do some research first.

      Dave does some good reviews here:
      http://www.eevblog.com/episodes/

    3. Re:My take by tlhIngan · · Score: 3, Interesting

      "Don't even think about a PC-based scope. A scope is a standalone instrument, always has been, always will be."

      I hate to break it to you but most scopes already are PC-based.

      Yeah, but the 'scope is a dedicated application with dedicated front panel controls. Windows is merely a widget provider. I've used them, and they're very nice as they support modern hardware and printouts/screenshots are a breeze. But you have to buy the ones with the full front panels - the ones that are just PCs are just... useless and you spend way too much time mousing around clicking virtual knobs. Painful.

      $2k can get you a nice basic scope. That's all you need. For the rare times you need something fancy, there are many places that'll rent you the high end scopes for days or weeks. Sure you're paying a good chunk of money for someone else's loan, but unless you can ante up the $10-100K+ for those things, it's far more economical. Get what you can (surely you should be able to find a nice 500MHz scope used?) with what you have to do most of the debugging. When it comes time to debug that obscure thing, rent it.

      This way you'll get a good scope for normal use, rent a oh-so-beautiful GHz level scope when you need it or even the fancy-smancy "analog digital" combined scope plus logic analyzer. Those let you analyze bus signals in standard 0's and 1's, while seeing actual signals at the same time. Plus, they can capture the analog signals with the digital, so you can trigger on some oddball logic condition on the bus and see any odd analog waveforms at the same time. But those are expensive - your best bet is renting until you can afford to buy one 10+ years from now.

      And if your scope only collects dust instead of signal, you've avoided wasting a pile of money.

  18. Handheld by aero2600-5 · · Score: 4, Informative

    I used to be a certified electronics calibration technician, and I've never noticed a difference between the analog and the digital.

    If $2k is your budget, and not having any idea what you're going to be using it for, I highly recommend a handheld Fluke. They were just as reliable as the old analog ones, but with more features.

    This is the model I'm referring to:

    Fluke 125
    Official Fluke 125 page

    aero2600

    --
    Please stop hurting America -- Jon Stewart
  19. It depends on what you're designing. by gmarsh · · Score: 5, Informative

    I'm an EE who does electronics design for a living, and I've done audio, SMPS, digital, FPGA, you name it. And in each case, the "best scope to use" was different:

    - For analog work, or for simple microcontroller debugging, something like a USBee will work great.

    - If you're doing higher speed analog, lower-frequency RF or switching power supply design, I'm a huge fan of the Tektronix DPO series. I use a TDS3032.

    - For digital work (debugging serial/parallel interfaces and whatnot) I use an old 100MHz "Mega Zoom" HP logic analyzer.

    - If I'm doing a design with a big FPGA, bringing lots of extra signals to the FPGA during layout time and using something like Chipscope Pro (on Xilinx FPGAs) to watch what's going on has been extremely handy. No test equipment required!

    1. Re:It depends on what you're designing. by vlm · · Score: 3, Insightful

      - If you're doing higher speed analog, lower-frequency RF or switching power supply design, I'm a huge fan of the Tektronix DPO series. I use a TDS3032.

      If you're doing RF you're going to want a spectrum analyzer sooner rather than later.

      If you're doing low freq / high power discrete analog (aka SMPS) you're going to want a curve tracer sooner or later, to fool around with if nothing else.

      The original article poster has it all wrong, in that a lab that has nothing but an empty desk and a $2K scope simply can't handle the jobs that are easy in a lab with a $500 spectrum analyzer, $250 scope, $750 worth of Hakko (de-)soldering gear, a universal eprom/uC programmer, a logic analyzer, maybe a low end HP protocol analyzer... etc. Don't forget the "obvious" material handling equipment like $500 worth of lights on arms, magnifying glass on arm, low power binoc microscope, ESD protection gear, etc.

      --
      "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  20. Get a used Analog Scope by Old+time+hacker · · Score: 2, Interesting

    I picked up a used Tektronix 7904 for under $100. Of course, the four probes that I needed cost rather more than the scope, but that's life. The 7904 (with the modules that I have) is a 350MHz unit -- which is great for doing radio work. This setup could easily have cost $10k new.

    Buy one of these online and the shipping will kill you. You need to find someone local who wants to get rid of one.

  21. Answering myself... by Qubit · · Score: 2, Informative

    Actually, there's at least company with open hardware oscilloscopes:

    http://www.bitscope.net/.

    --

    coding is life /* the rest is */
  22. Re:Buy a cheap digital scope and a good analog sco by petermgreen · · Score: 2, Informative

    Personally I find traditional non-storage analog scopes pretty much useless for digital stuff. Really you can only use them if you can arrange for the signal in question to output a simple pattern that repeats infinitely.

    Never used an analog storage scope but from what I hear they aren't exactly great for high speed stuff either.

    One exception: if you can stretch your budget to get a used TDS3000 or TDS3000B series scope, that would be a good way to go.
    There is one listed on ebay buy it now right now for the original posters budget of $2000

    http://cgi.ebay.com/Tektronix-TDS3014-Digital-Oscilloscope-100MHz-w-HPIB-/300450756657?cmd=ViewItem&pt=BI_Oscilloscopes&hash=item45f442b831

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  23. After almost forty years in the business by overshoot · · Score: 3, Insightful

    What would you, my esteemed Slashdot colleagues, get for yourself?

    An employer. Seriously. Every piece of test equipment I've ever owned (some costing upwards of $5000 1978 dollars) was a lousy investment.

    Especially when you consider that I have a lab at $WORK with scores of tools costing more than I make in a year, it's stupid to spend my own money on them.

    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
  24. $200-300, not $2000... used Tek scope on ebay by neurocutie · · Score: 2

    You should be able to buy a decent used Tektronix scope on ebay for $200-300, not $2000. Something in the 2200 series, or 400 series. Digital storage scope with 2 channels, A delay B horizontal, 100Mhz bandwidth.

  25. For what it's worth! by cmdrbrooks · · Score: 3, Informative

    I've been engineering for over 30 years and in my opinion there's nothing like a good old 7000 series Tektronix scope. You can pick one up on ebay and configure it with modules to do just about anything you would want a scope to do. They're old, use some power and oh by the way...they are analog. But they are great scopes. A lot will depend on what the projects you are talking about require, but as a good general purpose scope they are great. You can get all the manuals and work on the equipment yourself. And you will see electronics build the way no one builds it anymore, including Tek. I have a complete bench full of Tek and HP gear and it serves me well for projects ranging from audio designs to the latest single chip controller applications. Good luck in your search.

  26. Solved (Courtesy of Peter Hiscocks at TLUG) by davecb · · Score: 4, Informative

    ... at http://gtalug.org/wiki/Meetings:2005-12, Peter demonstrated the virtual oscilloscope and virtual function generator applications, which are available as open source.

    The hardware unit (approx 3 x 6 x 1" thick) is available at http://www.syscompdesign.com/CGR101.html

    --dave

    --
    davecb@spamcop.net
  27. Triggering is the gold standard by Anonymous Coward · · Score: 5, Informative

    The difference between a 'scope that is a joy to use and one that is useless and frustrating is triggering. Good triggering is what gives you ease-of-use. You can't see it if the 'scope can't trigger on it. This is especially true when you are trying to catch a glitch.

    In my experience, Tektronix 'scopes have always been easier to use because they triggered better than the competition. We got a bunch of money once and decided to buy new oscilloscopes. Since we worked for the government, we had to write up a tender so there could be a fair competition. It drove us nuts. The specifications for the other brands were as good as those of the Tek 'scopes. We had used the competing 'scopes and hated them. We had to bend like pretzels to get a specification that would ensure that we got the 'scopes we wanted. The specifications just don't do a good job of describing how usable an oscilloscope is. (ditto for spectrum analyzers)

    The Tek 'scopes were bullet proof. I could throw my 'scope in the back of a station wagon, drive to the airport, hop on a rented plane, fly five hundred miles, hike up a mountain and the Tek 'scope would ALWAYS work when I got to the job site.

    These days, with digital 'scopes, a good test is to throw a nasty waveform at the 'scope and press the autoset button. If you're looking at something useful, the 'scope is good. If you're looking at garbage, the 'scope is garbage.

    These days, I have an ancient Tek (circa 1970) 'scope on my bench at home. It works great for most of my home projects. At work, I have access to 'scopes that will do 1 GHz. My buds at the NRC have a 'scope that does 6 GHz. Somehow all the 'scopes are Tektronix.

    Since I started in the industry in 1974, Tektronix has made the best oscilloscopes. Some of their other stuff is crap IMHO but nobody else can touch their 'scopes. I'm teaching college now and we prefer to buy as cheap as possible. Whenever we've tried something other than Tek, we've regretted it. The Tek 'scopes have the advantage of being student proof!

    For other test equipment, I would choose other manufacturers. HP/Agilent would be my choice for almost everything else that isn't an oscilloscope.

  28. Re:Buy a cheap digital scope and a good analog sco by postbigbang · · Score: 3, Insightful

    Before plunking down good $$, I'd wait and see what sort of equipment is *really* needed. Scopes are a nice tool, but there are other tools like good spectrum analyzers (with waveform analysers) and other gear that can add up quickly. I'd say, let the need present itself, then invest to the need.

    --
    ---- Teach Peace. It's Cheaper Than War.
  29. Complete setup for under $1200 by aarggh · · Score: 2, Informative

    I would strongly recommend a good second hand analog one like the Tektronix 465 series which are rock solid and very cheap, and a for digital a DSO such as the Rigol (who make some of Agilent's stuff) DS1052E, this is a 50MHz 1Gs/rate and beautifully manufactured. The upside of this is that is the exact same model as the 100MHz version, so with a very trivial software hack you can turn this sub $500 DSO into a $1000 100MHz version! I would then recommend a good Digital Logic Analyser, for around $400 you can get the Intronix LA1032 (I think is the model) which is possbily the best unit on the market under $1500! View the EEVBLOG's (google it) to see the problems with DLA's and DSO's. So for under $1200 you get a 100MHz new DSO, a 100MHz S/H CRO, and a 32 Channel DLA!

  30. Not really... by Grog6 · · Score: 4, Interesting

    I have a very nice, for me, rackmount 350MHz 4 channel Tek scope with some very killer plugins.

    The scopes I used at work today are really beyond anything needed for home use, unless you're into some extremely expensive hobbies.

    The portable scope is a 3054B; 500MHz x4 channels. (~$10k, with options) The good one is an 11GHz x2ch Lecroy ($ almost 6 digits), I made picosecond-order measurements with it today.

    The differential probe was $5k each; (wasn't that what gov. spitzer paid? lol.) our newb has killed two. (4Vmax) $2k each to fix.

    If you can afford it for home use, I'd recommend the Tek 3054 or a lower bandwidth cousin. They're very easy to use.

    If you can get surplus scopes coming out of downsized companies, you can get a deal; that's how I got my rackmount and a stack of plugins for $130. It was a production fixture at a missle plant in the 90s. :)

    Digital is great, as long as you realize the limitations; digital displays lie sometimes. If you're going to base a paper on it, use multiple measurements with different equipment. :) I've seen fresh engineers embarrassed by artifacts.

    --
    Truth isn't Truth - Guliani
  31. Define what you need, go to ebay by smellsofbikes · · Score: 4, Informative
    I have a sort of side-business buying LeCroy 9400-series oscilloscopes off ebay, fixing them, and reselling them. They're great machines and you can find operator and service manuals, and you can get yourself a 400MHz scope for under $400. Likewise, the older Tektronix scopes, like the 2465, are truly excellent and in the same general bandwidth range.

    One reason I mention these is because newer scopes, particularly the Tek 3000-series, while incredibly useful because of their size, weight, and connectivity (they have a linux-based OS that includes a webserver so you can plug one in with a cat5 and control it from your desk remotely: pure awesome!) are just about impossible to repair. Everything, *everything* is in custom silicon. On a LeCroy you can swap out the input amps if you burn one, swap out the timebase card or the A/D cards for each channel. It's like working with an old PC, as opposed to an ipod.

    Also, budget for probes. Get probes rated for at least 1.5 times the scope's bandwidth: usually people ship probes that have the same bandwidth as the scope's max, but the spec on them actually means they're at something like -3dB and pretty fuzzy at that bandwidth. I got 500's for my 350mhz scope and they're beautiful. A lot of people sell broken probes and I've found, in the three I've purchased, that in every case it was a broken solderjoint where the probe cable met the board that attaches to the scope BNC. I reflowed it (no added solder for fear it'd mess with the tuning) and got three new probes for cheap.

    There are people selling vintage scopes on ebay that have NIST certification, if that's important to you, but you can also get it independently certified if you need it. Newark.com has cal services, to my surprise. (They're who we use at work.)

    I personally dislike Yokogawa scopes because their interface doesn't make sense to me. I can sit down at an Agilent or Tek or LeCroy and get it to do what I want pretty quickly (digital LeCroys are weird about horizontal offset) but Yokogawas I spend a lot of time reading the manual. But they're nicely engineered.

    The USB scopes I've used were disappointments to me: the $ per mhz isn't competitive with a used scope, and they're typically pretty tied to the company software, which might not do what you want.

    --
    Nostalgia's not what it used to be.
  32. go for 4 channels by CaptainPhoton · · Score: 5, Informative

    If you're a C.S. person, it's likely that you are a digital person, and you will most frequently use the oscilloscope to troubleshoot digital busses. Don't skimp on the channel count, go for 4! For things like serial busses (RS-232, SPI, I2C, etc.) you will want to watch clock, tx, and rx simultaneously. For a parallel bus, you can get your clock, chip select, and a couple addy or data lines. For most problems on your board, you can get by with the scope instead of an expensive logic analyzer if the scope has enough channels. The scope is better than the logic analyzer in many ways as you can watch for issues with noise, bus contention, etc.

    Every engineer has their bias, I say go for Tek! LabVIEW and DAQ are cool for repetetive measurements under automation, but there's just no substitute for a physical front panel interface with knobs and buttons when you just want to spend a couple minutes looking at a few levels.

    Try to find something with Ethernet or USB. Many of the used scopes on ebay have the old 3.5" floppy, and that becomes annoying when noone in the office remembers floppy disks and you need to get a plot off the scope to send to an FAE! :)

     

  33. Got One! The Memory is the Key by EETech1 · · Score: 2, Informative

    I have one of those sitting on my bench, and I can tell you that the Agilent MSO's are awesome. You can add acquisition memory (up to 256 million points) There's nothing like being able to zoom in on 3-4 seconds of data at a decent acquisition rate to see what is going on. Look for a good used one, and then save up and upgrade the acquisition memory as you see fit later. Many scopes have a very limited amount of acquisition memory (under 1 million samples), and it really limits how much you can zoom in and analyze the data you've just taken. You'll spend lots of time wishing you had a "better picture" otherwise. Either too zoomed out to get enough detail later, or too zoomed in to have enough to see what happened. The acquisition memory is the key. 1 million data points at 100 million samples a second does not give you a very long snapshot of what happened and going down in sample rate is not always an option. Any time you have to actually make something really work where there's multiple processors communicating and bus level interfacing, and lots of stuff going on there will be that once in a day, or week, or hour that something doesnt go quite right, and the shit starts piling up, and getting late that is what you (and your fancy scope) cant afford to miss, and you sit there with an incomplete picture, go damn I wish i could zoom in, go back 100 milliseconds or a second, and see what really happened. But I guess I'll wait ANOTHER day, week, hour whatever for it to happen again, and hope I can catch it. Many times you cant set a trigger to catch this stuff reliably, and you just cant let it go if you want your stuff to work (right). Look at the MegaZoom examples on Agilent's website to see what I mean. BTW it is also second to none at displaying data, and showing you little irregularities that appear in the signal, as well as allowing you to zoom in on that portion with (quite literally) a couple flicks of the knob. It amazes my coworkers how I can pan and zoom to all of the glitches, but the scope really does all the hard work if you do it right. It literally sticks to the edges and such when it detects you stopping close to them. Excellent piece of equipment. But the acquisition memory makes it all possible!

  34. Scope is a thing of the past by viking80 · · Score: 2, Interesting

    I hate to say this as a former Tektronix engineer, but you seldom need a scope, and if you do it is typically application targeted and expensive. So the general purpose scope that all self respecting EE's used to have on the lab desk is a thing of the past.
    All digital work either has debuggers or with FPGAs, Chipscope Pro or other. No scope needed. And if you really need to see how the eye diagram looks with your 10GB Ethernet, the best scope may be your receiver chip. Hard to find a 40GHz scope anyway.

    I actually had a Tek 2440 300MHz Digital Storage for at least a decade, but used it less and less. Became more a educational thing to show kids how AC looked. All serial interfaces are running at muli GHz speed, and RF development is more in the 5.7GHz range and higher (802.11n) Not many scope sampling at 4x or more at those frequencies.

    --
    don't cut it off www.mgmbill.org
    1. Re:Scope is a thing of the past by Andy+Dodd · · Score: 2

      I disagree. My basic Rigol DS1052E has solved many weird problems with microcontroller projects over the past months.

      Without the scope I would never have figured out that my I2C master and I2C slaves for a project were playing "Bus Fighter I2C: Noncompliant Master". (I thought the firmware on the master was using hardware I2C mode, but it was actually using a bad software I2C implementation that actively drove the clock and data lines high. Bad Things happened if a slave tried to do clock holdoff.) I might have eventually noticed the issue in the firmware source code, but having the scope saved me a HUGE amount of time in knowing where to look.

      Also, for the above problem, a logic analyzer (like the Open Workbench Logic Sniffer) would not have helped, since it wouldn't have shown that the clock line was entering a state where it was about 1/3 of the way between ground and Vcc (a clear sign that two devices were trying to drive the bus to different states simultaneously, which should not be possible on an standard speed I2C bus since nothing should actively drive it high.)

      --
      retrorocket.o not found, launch anyway?
  35. Did you ever bother to learn properly? by Interfacer · · Score: 2, Informative

    I've been a LabVIEW programmer for close to 10 years. I have also been a C and C++ programmer for quite a long time now. I did large projects using both, sometimes using both in the same project. I can call myself a qualified programmer using both languages.

    It is perfectly possible to create very large applications, using multi threading and proper design patterns. However, just like you had to spend years learning to write powerful and correct C++, you need quite some time to learn to program LabVIEW correctly.

    Once you can do that, writing test and measurement applications can be as efficient or even better than with text based languages. I have the confidence to say that I wrote large data acquisition systems that performed well with very large datasets and high acquisition speeds.

    But you have to understand data flow programming, and that is not something you acquire easily, just like you probably sucked at your first text based language projects.

    Don't blame the tools for your failure to use them properly.

  36. Textronix Type 547 -- aka "the chick magnet" by hey! · · Score: 2, Funny

    The 547 is the Barry White of bench top instruments. Its muscular aluminum frame is massive, yet understated. Dual independent time bases tells the ladies you've got a light but agile touch on the trigger circuits.

    Truly, this is a scope for a discerning bachelor geek. When you meet an interesting woman, casually mention you've got a type 547 back in your apartment and she's bound to fish for an invitation. Then if later she cannot, in an intimate moment, resist playing with the plug-in unit, propose marriage on the spot.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.