Have you seen Gabriel's video? As soon as you attach probes from the scope to your circuit, your wrist is tied to it unless you have very long probe leads. What happens if you move? You either break the probes or yank the circuit with you.
I have a proper (well full sized anyway) ARB and have often needed to generate test signals. What I do is do some testing while capturing input waveforms with my DSO and when I get a fail I take that captured input waveform and download it to the ARB and replay it creating the fail conditions which I can use to understand the failure mode. Also I can create special waveforms that reflect boundary conditions most effectively and test my designs that way. I don't use the ARB as often as my DSO but it's a great tool. I'm thinking of going with a Tek 2-ch ARB next time as this really opens up possibilities.
I own two of Gabriel's little masterpieces. The larger one sits on my test setup at work, wired into the power. I have a pair of TEK probes, and have provided BNC connections to the appropriate pins. There is nothing better for verifying sensors and switch bounce. In my line of work, sensor signals can often be something they shouldn't be, but an O'scope is considered overkill. The O'scope watch should find a place on any Field Service Engineer's or Technician's wrist.
The important things are always power and probes. If Gabriel makes an interface module with good buffering/grounding, there's no reason not to have it on a cable to a more secure location (utility belt anyone?) allowing battery augmentation and a clean probe attachment. It doesn't even _have_ to look geeky...until deployed. As for battery power, Gabriel is quite aware of current draw, and has FAQs on it for his other scopes. No reason to suppose he'll drop the ball on the watch. There are a lot of cell phone rechargers out there that can keep a watch like this going without having to leave it behind to recharge for hours. And as a scope, it'd just make sense to always have one on hand to ensure that the battery hasn't been drained in watch mode to the point where it won't work for a heavy troubleshooting session.
The number of problems I've tested and proven with the mini and micro boards justifies some real interest in the watch. Something not mentioned here, also , is that they are not program-fixed: you can get the (free) atmel studio and reprogram them to do anything you want, within the limits of the processor core. That's a lot.
I can't recommend them highly enough.
Yeah that would be cool. So Gabriel better build in a radio (or an MP3 player) to provide said music signal. I guess you could have it displaying the output of the generator but music would look way cooler. :-)
Gabriel's stuff is very cool. I have one of his older boards that I am going to build into a breadboard (when I get the time....)
As per the above posters, i wonder how useful a scope watch would really be - apart from anything else it would limit the use of the hand you were wearing it on. Maybe the strap could become a stand? The limited battery life will put a lot of people off. So maybe make a hinged cover with a solar cell on it to act as a dual-purpose charger and screen protector. or build solar cells into the strap, or sell it with a stand to sit it on overnight that acts as a charger...??
But I think Gabriel could make his money on this selling them to geeks like Max and me :-)
I can't see that many uses for a handheld CRO and signal generator, HOWEVER, there are many IT and installer folk who could use a TDR, which requires almost the same hardware. TDR's are used to send a tiny blip down a wire and look for reflections caused by breaks, joins, taps and ends of wires. It's quite easy to measure to within a few centimetres where a cable join is, for example. They can also be used for optical fibre.
This is probably a larger market for the designer than the plain old oscilloscope, as extreme portability is of concern for the installers/IT folks.
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...