alanh wrote:If you are going to pay that much for the component costs of everything else, go the extra inch and add a simple lcd+touch screen for $50. I would much rather run it in stand-alone mode anyway until I have something interesting to look at on bench PC screen.
Thanks for your thoughts. I can understand this, there would be less things to deal for sure. Could you get a nice screen for $50? Something like a Nexus 7 I'm thinking. On eBay, a replacement Nexus 7 screen is $68, no digitizer. Mainly I'm trying to leverage the volume pricing of a tablet to get a nice screen, and at least for me I own a few tablets so no need to buy something else. This also adds more to the hardware side of the project, both in terms of the mechanical packaging and the circuitry.
Have you ever wished for a remote screen on your scope? I've worked on a few machines that were very loud and I wished I could be in the other room while monitoring the DUT. Or the workbench has wires everywhere (especially using a logic analyzer) and you want easy access to the screen. Maybe keep the microphone close so you can say "Scope - single trigger". :P Some Tek, Agilent, R&S, etc. scopes have a "remote front panel" feature that runs on a PC. The Snap-On Verus Pro has a remote touch screen, the most similar to my idea.
The CPU burden of running Android vs pumping out IP is probably a wash. I don't know how much CPU I'll need for "digital phosphor", FFT, etc. but I would guess faster is better. The Android for Zynq is a few versions behind, I'm not sure how good the support will be in the future.
That said I've never used a scope with a remote screen, maybe it's stupid. Worst case I could add a real attached screen later, or just some double-sided tape! If the screen were used a ways away from the scope, the knobs wouldn't make much sense, but maybe the Android GUI will provide a compelling interface to supplement the knobs.