Computer Old Farts Forum
 help / color / mirror / Atom feed
From: stewart at serissa.com (Lawrence Stewart)
Subject: [COFF] 52-pin D-Sub?
Date: Thu, 27 Feb 2020 20:37:00 -0500	[thread overview]
Message-ID: <905CE999-5601-4521-847B-B2146C60B564@serissa.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2002281050090.1121@aneurin.horsfall.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]

Huh.  New to me too, but Digikey links to the datasheets, and they really do mean DB.
They go up to DD100.  They are called “double density”.

This reminds me of the circa 1990 “HIPPI” interface, or high performance parallel interface.  They typically ran at 50 MB/sec.  The connectors were two-row 100-pin D style.  See http://www.elpeus.com/scsi-cables/100pin-scsi-cable-hippi/3m-100pin-male-to-100pin-male-scsi-cable-hippi/ <http://www.elpeus.com/scsi-cables/100pin-scsi-cable-hippi/3m-100pin-male-to-100pin-male-scsi-cable-hippi/> for example.

We used these cables and connectors on the first Alpha machines at Digital to connect the 3Max front end processor to the ECL based Alpha Demonstration Units, although the protocol was different.  The connector was about the biggest that would fit on a TurboChannel I/O card.


> On 2020, Feb 27, at 7:04 PM, Dave Horsfall <dave at horsfall.org> wrote:
> 
> On Thu, 27 Feb 2020, Adam Thornton wrote:
> 
>> I recently have pulled out of the trash a plugboard with a male and a female D-Sub 52 connector.  3 rows of pins, 17-18-17.  I took the connectors off the board: there's nothing back there, so this thing only ever existed so you could plug the random cable you found into it and its friends to see what the cable fit.
> 
> That would be something like a DD-52P (certainly not a DB-52P!).
> 
>> I can't find much evidence that a 52-pin D-Sub ever existed.
> 
> Well, Digikey seem to have them:
> 
>    http://www.digikey.com/product-detail/en/itt-cannon-llc/2DB-52P/2DB-52P-ND/4734668
> 
> No photo, though...
> 
> -- Dave_______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200227/776a2924/attachment.html>


  reply	other threads:[~2020-02-28  1:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 23:37 athornton
2020-02-28  0:04 ` dave
2020-02-28  1:37   ` stewart [this message]
2020-02-28  2:12     ` athornton
2020-02-28  4:12     ` dave
2020-02-28  4:18       ` dave
2020-02-28 14:11         ` clemc
2020-02-28 14:34           ` athornton
2020-02-28 21:23             ` dave
2020-02-28 16:35           ` krewat
2020-02-28 21:28             ` dave
2020-02-28 21:44               ` clemc
2020-02-28 21:58                 ` dave
2020-02-28 22:20                   ` clemc
2020-02-28 23:22                     ` pechter
2020-02-29 13:12                       ` emu
2020-02-29 15:45                         ` krewat
2020-02-29 15:49                           ` clemc
2020-02-28 22:38                   ` pechter
2020-02-28 22:05                 ` drb
2020-02-28 22:28                   ` clemc
2020-02-28 22:26                 ` pechter
2020-02-28 22:36                   ` clemc
2020-02-28 23:40                     ` pechter
2020-02-29 16:52                       ` clemc
2020-02-28 23:54                     ` pechter
2020-02-29  9:59 rudi.j.blom

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=905CE999-5601-4521-847B-B2146C60B564@serissa.com \
    --to=coff@minnie.tuhs.org \
    /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).