Arduino Netduino: Oscilloscope and Logic Analyzer

Translate This Page

Arduino Netduino: Oscilloscope and Logic Analyzer

Rate This
  • Comments 2

I have been thinking about buying a nice Oscilloscope/Logic Analyzer ever since I bought that little cheapie one I bought a few weeks ago.  But then I thought that it would be cool to build one.  I know how they work, and usually my needs are pretty low tech and low bandwidth.  As a result I am going to try to build one using either an Arduino or Netduino.

Here are some of the plans I am reviewing, mainly since it will definitely be more expensive to build then to buy, but it would be cool to have the experience: , this one looks good!, fast, but complicated, if you have built out other kits or projects, this is for you. cheap, requires only an UNO board and a wire, cheap, not a true Oscilloscope, but close enough and simple.

I am definitely going to give one of the harder ones a try, but the last two are likely good enough to solve most problems that require an O-scope (Oscilloscope).

Leave a Comment
  • Please add 5 and 1 and type the answer here:
  • Post
  • Hey, I wrote the Arduino Oscilloscope article on MitchTech's blog. For what it's worth, I use the "Open Bench Logic Sniffer" for purposes of i2c and spi debugging. Definitely get the "Logic sniffer Probe Cable" with it. What I've learned to look for in a logic analyzer:

    * Ease of instrumentation. The Open Bench probe cable tweezers-style connectors are GREAT.

    * Software. Open Bench has software that works with it.

    * Resolution. Ensure probe device has a resolution that is capable of measuring your device under test. Using Nyquist-Shannon sampling theorem it's roughly 2*period of the device you are sampling.

  • That's really good!Arduino make this very simple for mcu i try to communication and control ws2812b led strip( with Arduino.

    so your information is  too important! thks!

Page 1 of 1 (2 items)
Generic Content

Legal Note:

  1. The author, Sam Stokes, is an employee of Microsoft
  2. There is no guarantee that anything I write is correct, I do try to make sure that what I write is correct.
  3. Use anything written in this blog at your own risk
  4. Test what I write about before using the information
  • Sometimes posts will disappear because I realized that they really don't fit with the total chaos of what I write about
  • Links are tested and available on date of publication, what others do with their links are out of my control


  • Whatever I write on this blog is unedited by management or anyone, which should be obvious from the randomness of the blog.  I simply write about things I like.
  • Microsoft does not restrict me in anyway, so I generallyblather about whatever I want to.
  • For personal reasons I will not write about:
    • Company confidential stuff, mainly because Microsoft is more transparent than any company I have ever worked for.
    • Other people unless they give me permission to write about them