osbock wrote:3. What's wrong with my 20 mHz el-cheapo analog scope? Aside from it's size, and lack of storage/digital features, the triggering is unreliable/finicky, the trace is fuzzy/hard to read (and yes, I've used the focus control)
It doesn't even have to be a cheap one. I did an A/B compare once against a really nice Philips 60-MHz traditional scope. We were measuring a system's processing time. A little timer circuit strobed an input at about 10Hz (realistic for the application), and we triggered on input and scoped the input and associated output. We wanted to see transit time and jitter. Even with the persistence turned all the way up and the focus tuned, reading the analog trace was an exercise in visual memory-- "Is that where it was before?" Grease pencil on the screen could have helped, but overall the measurement depended totally on reaction time, guesswork and subjective judgment.
On the DSO, the persistence control was "show me the last 5, or 10, or whatever traces." They all showed up on the screen where they were meant to be, all together, for as long as we wanted to look at them. !!!. The analog scope still does most things very well. They're still using it, but applications like this one fall outside.
osbock wrote:I am thinking of getting one of the cheap logic analyzers. I borrowed a Salae Logic from a friend and found it good (though the software bogs down a bit with a lot of samples). I have the DP logic sniffer in my cart at Seeed right now, though I have managed to crash (badly) the open source software it uses when using it with the IRToy.
jawi welcomes bug reports, if it crashed coherently enough that you can give one. Besides that, I have an alternative OBLS client written in Python http://dangerousprototypes.com/forum/viewtopic.php?f=57&t=2476
. At the very least, it should crash differently. AFAIK it's never been run with the IRToy. My next move, when I get some time, is to get RLE workng and run it with the Bus Pirate.