The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michael@kjorling.se (Michael Kjörling)
Subject: [TUHS] PDP 11/34a Serial Communications Problem
Date: Sun, 5 Feb 2017 20:36:38 +0000	[thread overview]
Message-ID: <20170205203638.GJ21797@yeono.kjorling.se> (raw)
In-Reply-To: <CAF12ZDTmuCk-9AdRU1nD1xrKihchB5=ntAukP1TDa7L7VZTLqw@mail.gmail.com>

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

On 5 Feb 2017 15:03 -0500, from markhare at buffalo.edu (Mark Hare):
> Since this is a straight-through ribbon cable, I don't see what could be
> causing this problem. I have checked the continuity of each wire in the
> cable, and there doesn't appear to be a problem. I'd appreciate any advice
> that anyone has to offer.

Have you checked to make sure that there aren't any connections
between the individual wires? I'm not particularly familiar with the
hardware of the PDP-11, but a signal going out on one wire and showing
up also on some should-be unrelated wire could conceivably cause all
kinds of weird behavior depending on exactly which wires are involved
and what they are used for.

The fact that merely leaving the ribbon cable connected causes the
problem to appear definitely points to the PDP-11 not agreeing with
the cable (or connections) for some reason. My first suspect in that
case would be an electrical problem with the cable itself _versus what
the PDP-11 wants it like_. Maybe the cable is operating to
specifications, but the '11 wants something different.

-- 
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
                 “People who think they know everything really annoy
                 those of us who know we don’t.” (Bjarne Stroustrup)


  reply	other threads:[~2017-02-05 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 20:03 Mark Hare
2017-02-05 20:36 ` Michael Kjörling [this message]
2017-02-05 20:38 Noel Chiappa
2017-02-05 20:58 ` Mark Hare
2017-02-05 22:01 Noel Chiappa

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=20170205203638.GJ21797@yeono.kjorling.se \
    --to=michael@kjorling.se \
    /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).