From: Tom Ivar Helbekkmo via COFF <coff@minnie.tuhs.org>
To: coff@tuhs.org
Subject: [COFF] DEC terminal line driver chips?
Date: Thu, 29 Apr 2021 09:02:01 +0200 [thread overview]
Message-ID: <m28s51h8uu.fsf@thuvia.hamartun.priv.no> (raw)
I've got a number of DEC terminals, ranging from the VT220 to the VT520
(sadly, I got rid of my VT100 and VT102 many years ago, before I started
collecting DEC equipment instead of just using it), and some of them
have one or more burned out serial ports. Before I start taking them
apart to find out what chips were used, I figured I'd check if any of
you folks happen to know. I'd like to order a stash of replacements,
and it would be nice to have them handy before I clear the work bench to
start dismantling terminals...
Oh, and for the record: the Q-bus PDP-11/23 uses 9636ACP and 9637ACP for
output and input, respectively, while the VAX-11/630 substitutes a
9639ATC optocoupler for the 9637ACP differential receiver. (I have a
couple of spare CPU boards with damaged ports, as well, so these are all
on my shopping list already.)
-tih
--
Most people who graduate with CS degrees don't understand the significance
of Lisp. Lisp is the most important idea in computer science. --Alan Kay
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next reply other threads:[~2021-04-29 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 7:02 Tom Ivar Helbekkmo via COFF [this message]
2021-04-29 12:21 ` Brad Spencer
2021-04-30 7:34 ` Dave Horsfall
2021-04-30 11:55 ` Tom Ivar Helbekkmo via COFF
2021-04-29 13:17 ` Clem Cole
2021-04-30 7:42 ` Dave Horsfall
2021-04-30 12:12 ` Tom Ivar Helbekkmo via COFF
2021-04-30 16:49 ` Derek Fawcus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m28s51h8uu.fsf@thuvia.hamartun.priv.no \
--to=coff@minnie.tuhs.org \
--cc=coff@tuhs.org \
--cc=tih@hamartun.priv.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).