The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] Teletype
Date: Fri, 15 Aug 2014 18:01:04 -0400	[thread overview]
Message-ID: <20140815220103.GE16978@mercury.ccil.org> (raw)
In-Reply-To: <20140815214726.EA12118C14B@mercury.lcs.mit.edu>

Noel Chiappa scripsit:

> First, I think most Teletypes used what is called '20mA current loop' serial
> line electrical interface standard (although some of the later ones could use
> 'EIA' - the now-usual, although fast disappearing, serial line electrical
> interface standard). They are logically (i.e. at the framing level) the same,
> but the voltages/etc are different.

Current loop to EIA RS-232 (which is the relevant standard) converters
are readily available, saith Google.  There are also RS-232 to USB
converters for the other end.

> So that means that first, if you plug into a computer, your serial interface
> has to be able to go that slow. Second, if you're dialing up, you need to find
> a dial-up port that supports 110 baud. (I would be seriously amazed if any are
> left...)

I dialed up The World's local dialup line for my area, and heard a large
variety of tones including Bell 103-compatible FSK, which is 300 baud.
I suspect that anything that can do Bell 103 can fall back to Bell 101,
which was 110 baud.  I admit to never trying it.

Note that it's 110 baud because there are a start bit and two stop bits,
so it's really 10 cps.  300 baud has only one of each, hence 30 cps.

> Of course, if you go with a DecWriter, some of these issues go away, but be
> careful: some older DecWriters were 20mA too, and the speeds were almost as
> slow on many (probably 300 baud, but I don't know much about DecWriters).

The LA36, the only one I ever used personally, was 30 cps, ergo 300 baud.
(Note that it buffered and could print faster to catch up after a long
carriage return.) There was also an LA120 at 120cps.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan at ccil.org
        "Not to know The Smiths is not to know K.X.U."  --K.X.U.



  parent reply	other threads:[~2014-08-15 22:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 21:47 Noel Chiappa
2014-08-15 21:53 ` Warner Losh
2014-08-15 22:01 ` John Cowan [this message]
2014-08-16  1:56   ` Lyndon Nerenberg
2014-08-16  2:12     ` Lyndon Nerenberg
2014-08-16 21:28       ` Ronald Natalie
  -- strict thread matches above, loose matches on Subject: below --
2014-08-18 13:56 Noel Chiappa
2014-08-17 17:33 Noel Chiappa
2014-08-16 14:35 Noel Chiappa
2014-08-15 21:55 ckeck
2014-08-15 18:04 Brian Zick
     [not found] ` <99C03A20-7BC3-44CA-946D-6CFD56B9346F@orthanc.ca>
2014-08-15 18:52   ` Brian Zick
2014-08-15 19:05     ` Ed Skinner
2014-08-15 19:13       ` Lyndon Nerenberg
2014-08-15 21:07     ` Clem Cole
2014-08-15 21:23       ` Hoskins, Matthew E.
2014-08-18  5:54       ` Brian Zick
2014-08-16 10:25     ` Dario Niedermann
2014-08-15 19:08 ` John Cowan
2014-08-15 19:16   ` Lyndon Nerenberg
2014-08-16 20:42   ` Ernesto Celis
     [not found] ` <CAEvOwxW=G+g3dtSGaN=P7QmovgOygfANxacmcUo9Devn6v6B1Q@mail.g mail.com>
2014-09-15 15:13   ` John Foust
2014-09-15 19:38     ` Dave Horsfall
2014-09-15 19:51     ` Cory Smelosky

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=20140815220103.GE16978@mercury.ccil.org \
    --to=cowan@mercury.ccil.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).