Editing Oscilloscope
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 20: | Line 20: | ||
= Open Source Oscilloscopes = | = Open Source Oscilloscopes = | ||
− | Of course, you have to already have a working o'scope in order to build and test another o'scope, making this the same sort of chicken-and-egg problem as the [[Projects#RepRap | RepRap]] project, the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GCC project], and other projects | + | Of course, you have to already have a working o'scope in order to build and test another o'scope, making this the same sort of chicken-and-egg problem as the [[Projects#RepRap | RepRap]] project, the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GCC project], and other projects David Cary finds interesting. |
This problem in respect to oscilloscopes can be solved by incremental development. First start of working your way towards acquiring analog data using an ADC connected to some sort of processor or controller. Then build a cheap device that provides a somewhat defined test signal (simple timer works just fine). Now you can go to the next step of learning about and building an analog front-end that will be connected to the ADC. Then you'd start thinking about how data flows through the system, beyond the ADC and the processor (definitely to to memory and later on the display, maybe to non volatile storage like USB mass storage). That's basically it. Okay, you need to build and hookup a display and a keyboard but what you have is (at least in theory) the central parts of an oscilloscope. | This problem in respect to oscilloscopes can be solved by incremental development. First start of working your way towards acquiring analog data using an ADC connected to some sort of processor or controller. Then build a cheap device that provides a somewhat defined test signal (simple timer works just fine). Now you can go to the next step of learning about and building an analog front-end that will be connected to the ADC. Then you'd start thinking about how data flows through the system, beyond the ADC and the processor (definitely to to memory and later on the display, maybe to non volatile storage like USB mass storage). That's basically it. Okay, you need to build and hookup a display and a keyboard but what you have is (at least in theory) the central parts of an oscilloscope. | ||
Line 236: | Line 236: | ||
* DIY Arduino Oscilloscope using a cheap Nokia 3310 Screen [http://filear.com/?p=211] via [http://hackedgadgets.com/2012/01/30/diy-arduino-oscilloscope-using-a-nokia-3310-screen] | * DIY Arduino Oscilloscope using a cheap Nokia 3310 Screen [http://filear.com/?p=211] via [http://hackedgadgets.com/2012/01/30/diy-arduino-oscilloscope-using-a-nokia-3310-screen] | ||
* Michael Jay Geier. [http://spectrum.ieee.org/geek-life/hands-on/pocket-oscilloscope-review-roundup/0 "Pocket Oscilloscope Review Roundup"] 2012. ''(FIXME: make sure all the scopes mentioned are included on the above list)'' | * Michael Jay Geier. [http://spectrum.ieee.org/geek-life/hands-on/pocket-oscilloscope-review-roundup/0 "Pocket Oscilloscope Review Roundup"] 2012. ''(FIXME: make sure all the scopes mentioned are included on the above list)'' | ||
− | |||
− | |||
---- | ---- |