GPIB state machine info WTD
philpem at dsl.pipex.com
Sun Sep 11 08:00:23 CDT 2005
In message <m1EECCS-000IyXC at p850ug1>
ard at p850ug1.demon.co.uk (Tony Duell) wrote:
> Actaully, a PERQ centronics interface, but I can't see any good reason
> why it wouldn't work with a PET (although it doesn't do any kind of code
That's the one! A couple of 16V8s and a 20V8, right?
> No, you misunderstood me. There is no CPU involved in this serial
> adapter. The EPROM is the logic for the GPIB handashake. It's the GPIB
> timing that's way out. It works with a PET as the other side of the link
> because the PET does all the handshaking in software, so it's pretty
> forgiving about timing problems. But this seiral adapter will _not_ with,
> say, a 9914 as the other device on the bus..
Ah. Probably better to use that as an example of how not to design a GPIB
interface, I guess.
Phil. | Acorn RiscPC600 SA220 64MB+6GB 100baseT
philpem at philpem.me.uk | Athlon64 3200+ A8VDeluxe R2 512MB+100GB
http://www.philpem.me.uk/ | Panasonic CF-25 Mk.2 Toughbook
... Multitasking causes schizophrenia..
More information about the cctech