[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [N8VEM-S100:907] oscilloscope recommendation



I second Mike's recommendation of Logic.  I purchased one when they first came out, and participated in the software beta process for the OSX version of the software.  A great company and an excellent multi-platform product.

Ian

On 2012-07-10, at 8:29 AM, mike wrote:

> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Are you sure you want a scope and not a logic analyzer?
> 
> A pretty good, and modestly priced logic analyzer
> http://www.sparkfun.com/products/8938
> http://www.saleae.com/logic/
> 
> The software can run in demo mode so you can test drive before you buy.
> 
> I find I use my logic analyzer far more often than I use my scope.
> 
> Of course there are times when you need an analog scope. Personally I
> have a antique Tektronix RM 565 ( like this one -
> http://www.wrljet.com/tektronix/RM565/565_01_RJP.jpg ) that I keep
> wishing will die so I can get something new (and weighs less than 50
> pounds), but the darned thing just keeps going, and I have a spare CRT
> and vertical amp module, so I'll probably die before it will.
> 
> - --Mike
> 
> On 07/10/2012 12:59 AM, norwestrzh wrote:
>> My old scope was sold by JDR (San Jose, CA.).  It was cheaply made
>> (in Korea), and that is why I could afford it.  It was 35 MHz, dual
>> trace.  Probably had way more capability than I'd ever need.  I
>> would be using a scope to troubleshoot the S-100 cards produced by
>> John and Andrew.  Probably 10 to 12 MHz would be the fastest signal
>> I'd ever be looking at.  For example, I was trying to get the ZFDC
>> card working.  The enables on the two bus interface LS244s (U16 and
>> U25) remained high during I/O even though the LS682 (U23) and the
>> LS139 (U19) appeared to be working as expected (using a logic
>> probe).  I tracked this problem back to the LS32 (U20).  The two
>> inputs to the gate were wiggling (as expected), but the output
>> remained high.  The chip was OK, so I was going to look at the
>> relative timings of the two inputs.  That's when my scope died.
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQEcBAEBAgAGBQJP/EpfAAoJEA7EcEr0emgf7/wIALcuXCnzSffy7u/LU2ApRMqB
> Av7PAfOGvLfrNg6BF5/NgRpNuxMvbXDPpLiBa7ibNb7jGixDJRJxTI0QMie6RbiC
> w0naDa4EKVCrUyjl/RvCos9V5HrzovQ9LbkiS5xibYToRd0dwVsFfQOCl8U/6kHU
> nstVgmu02IvfV53wWxxw2EW00SDaop4OEo0dIuzhFoqdbRcA7gXiL02dCEhUezwF
> UdRVUZcM4krMhcJ9cn23U9SVqqp+qJNE2hGoYemjqz2LbR3hMMiN4PPKdcRtqI3w
> xJRc7kgDwjNMwrON2tIHrZGmM9wFc2AtZ6wnsYqvdrWqyS3cJ9pkNlzvkZcEM1I=
> =ukm7
> -----END PGP SIGNATURE-----
> 
> 
> ---
> Filter service subscribers can train this email as spam or not-spam here:   http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=3863F24CCAA411E1B2BCFF6F93ED0201