From: "Russell McMahon" Sent: Tuesday, September 28, 2004 1:48 AM > I see some merit in making a "wish list", assigning each a resource cost and > then seeing how people rate them. I don't see a 100 MSPS sampling rate as > overly difficult (I may be wrong :-) ). IF the A2D, memories and control > logic can handle this rate then it's not tooo much harder than say 20 MSPS > or even 1 MSPS and may cost little more. There's nothing wrong with a wish list, but it seems like these are all basic design criteria. It's true that "overly difficult" is a relative term, but 100 MSPS involves having to deal with a very large amount of bandwidth. Would firewire even be fast enough or we have to start dealing with data compression? The probes also get a lot more expensive and the circuitry handling the signal inside has to be much more precise to avoid introducing noise. > People talking about 100 KSPS and 100 MSPS are talking about completely > different devices (shopping basket vs rally car). Good analogy. I might make a shopping basket in my garage, but I don't have the skill or tools to make a rally car, even from someone else's plans or kit. > Things like ethernet interfaces could be handled in an add on modular manner > (both in hardware and software). Agreed, as long as the project concentrates on getting the basic unit working before designing the add-ons. The add-ons are useless if the basic unit is never finished. It seems that things like ethernet interfaces are becoming part of the basic design though. > If all people want is 100 KSPS then all you need is a bare PIC :-) > (Or maybe a bare PIC plus a deepish widish memory that you can stuff sample > data into rapidly enough). You can buy "scopes" that do this at very modest > prices. That's actually what I thought the project was originally. Jason _______________________________________________ http://www.piclist.com View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist