ArduinoLab?

I had this thought after looking at a thread on an oscilloscope made from an arduino, and finally decided to mention it. Basically, I'd think an oscilloscope and frequency generator are the harder parts of an electronics lab to get, since the oscilloscope at least is rather expensive, and the freq generator probably similar. Fortunately, in the amateur realm, you don't need a whole lot, and as the arduinoscope shows, the level needed is hardly professional quality, though I'd imagine that's certainly possible with work and money.

Something I saw though was that the arduino can probably do some multimeter functions as well, with some outside help, and a few other things can be mounted on the same board, though probably separate for the sake of isolating them. So, the ArduinoLab concept is to build an arduino based "lab" containing all of the major devices you might need for electronics work, built into one package. Here's what I was seeing:

An Arduino, probably one of the bigger ones, would be mated to one of the LCD screen shields. This is the core.

An Arduinoscope variant would display on the screen in scope mode.

A multimeter would be in there, again using the screen for display, and probably with quite a bit more function than a normal MM.

A frequency generator, possibly run by the Arduino, but might actually be separate, with the Arduino tapping it to show information on what you're doing.

A power supply would probably be isolated completely, but that's not too much trouble. It would be a variable voltage regulator and potentiometer with a three digit LED, since you'd probably max it out at 12 or 24 volts. While the other stuff would use the Arduino more, I'm thinking you'd want to keep this isolated due to the larger potential voltages, so some way would need to be found to set up a reader so the LED display can show what you're getting, down to a tenth of a volt.

I'm thinking some sort of logic probe/serial monitor might be useful, with the serial simply showing a bunch of bits at a time. Not sure how useful something like that would be though. I'm sure some other people might think of interesting things to use, too. It would also need a decent battery, say an extended version of the power shields.

The real fun would be that using something like a Mega would allow multiple readings of all sorts of stuff. You could monitor several points in a circuit to see if all of them are working right at the same time.

Would something like this be of interest? With all the stuff you'd need, I can't see it being a whole lot less than used equipment, but it's a fun project and provides usability that's hard to find in one place.

Any thoughts?

If you look back at some of my earlier posts (like, from the beginning), you'll see some postings where I discussed just this sort of idea. I had the idea, though, of making it with multiple ATMega328s, and a 128x64 KS0108 screen. Three or four 328s would be sufficient; one would be for driving the screen (with a RAM graphics buffer in 1K - so you can have page-flip graphics to cut down flicker, and maybe improve speed and do other things you couldn't do otherwise or as easily), one would be for keypad/joypad/stick input, one would be for sound, and the final would be the "master controller" for the other three; comms would be done via I2C (and possibly multi-master, too).

Such a custom system could certainly become your "ArduinoLab" device; the master could sample or do DDS for waveform output, count frequency, etc. It would coordinate updating the screen (which would have its own custom interface library for it, overlaying the KS0108 lib, and also providing the page-flip 1K buffer), taking input from the keypad/input module, etc.

Perhaps the sound output ATMega could do the frequency generation? Maybe the i/o module could do the sampling on its ADC to act as a frequency counter, digital logic analyzer, etc? Maybe it also has an SDCard interface, and theres some kind of custom bootloader on the master that can read .hex files on the SDCard? Reloads itself (so separate sketches for the master to be different things!). Maybe it could store other resources as well.

Don't want the ArduinoLab? A different set of code for the master CPU off the SDCard, and now you have a handheld gaming system!

I swear, if I didn't already have the project I have, I would be putting something like this together today!

I swear, if I didn't already have the project I have, I would be putting something like this together today!

I know how that goes. Parts of this kind of project are well above my current skill level, but I also have things to do that take priority.

Good idea I reckon.

As for the UI, what about an LCD with touch panel? Save having all those buttons, knobs etc and can be modified according to what devices you have and you can get them for about $80 these days. (OLED is better but 2x the price)

See these http://www.4dsystems.com.au/prod.php?id=113

These 4DS displays have on-board processors that can handle all the UI, although you can just use serial control if you like.

Also, at the risk of making this bigger than Ben Hur...

What about plugin modules, each with a processor, say one for an MM, pulse/pattern generator, logic analyser, CRO (oscilloscope), PSU, freq counter, protocol analyser (serial/SPI/i2c) etc etc.

This way you don't have to design one large PCB and hope you got it right and have the instruments everyone wants, just start with a MM for example and add gadgets over time. If the interface is well defined maybe people will start making their own instruments for it.

Parts of this kind of project are well above my current skill level

This solves that problem :), I'll do the logic analyser.

Something like this?
http://www.embedds.com/coma-the-incredible-all-in-one-instrument-that-youre-looking-for/

I'm almost waiting 3 months to receive an 240x160 lcd that doesnt want to cross the ocean to europe to start creating one of those "mini-labs", and using a separate/dedicated dds chip seems smarter than using the timers, but hey, timers and avr remember me about chip tunes!!

That COMA posting is from 2008, did anything ever eventuate? Also I can't find any tech details.

Found this

But still can't see if anything eventuated.

As for the UI, I would add a couple of knobs using shaft encoders who's function varies according to the instrument selected. There's no substitute for turning a knob for adjusting values.

You have all the schematics and source code, its easy to port it to arduino c++ code, or more efficient avr c code.