From: Bakul Shah <bakul@bitblocks.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Floppy to modern files for Usenet maps
Date: Sun, 23 Jun 2019 18:40:13 -0700 [thread overview]
Message-ID: <20190624014020.D24AD156E40C@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 23 Jun 2019 20:53:19 -0400." <c9ca5a7f-4ba4-0273-6f49-57ba0ee61a06@kilonet.net>
On Sun, 23 Jun 2019 20:53:19 -0400 Arthur Krewat <krewat@kilonet.net> wrote:
> Both the AT&T and the USB cable will be "DTE" (Data Terminal Equipment -
> ala terminal) vs. "DCE" (Data Communication Equipment - ala modem) -
> you'll need a null-modem cable to correct that mismatch. Basically, if
> not using hardware handshake, swap pin 2 and 3. ;)
Since mid 80s I have used Dave Yost's wiring scheme that
converts a DB-25 or DB-9 adapter to an RJ-45 socket:
http://yost.com/computers/RJ45-serial/
You wire any DB-25 or DB-9 DCE or DTE male or female adapter
so that the RJ-45 socket has the above pinout. You figure
out which device needs what kind of adapter and permanently
attach the adapter. Now you can use a standard "half-twist"
phone cable with 4, 6 or 8 wires and connect anything to
anything.
My last device with a real RS-232 interface (a CP-290 X10
controller) where I used this died 4-5 years ago. I still use
serial ports on RaspberryPis but talk to them via serial<->USB
adapters (these are 3.3V uarts).
next prev parent reply other threads:[~2019-06-24 1:46 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 23:10 Mary Ann Horton Gmail
2019-06-23 23:52 ` Arthur Krewat
2019-06-24 0:02 ` Grant Taylor via TUHS
2019-06-24 0:35 ` Mary Ann Horton Gmail
2019-06-24 0:53 ` Arthur Krewat
2019-06-24 0:56 ` Larry McVoy
2019-06-24 1:12 ` Arthur Krewat
2019-06-24 1:31 ` William Pechter
2019-06-24 1:51 ` Arthur Krewat
2019-06-24 1:40 ` Bakul Shah [this message]
2019-06-24 3:20 ` Grant Taylor via TUHS
2019-06-24 0:50 ` Arthur Krewat
2019-06-24 21:07 ` Michael Kjörling
2019-06-24 21:30 ` Steve Nickolas
2019-06-24 21:59 ` Gregg Levine
2019-06-23 23:57 ` Grant Taylor via TUHS
2019-06-24 0:40 ` Mary Ann Horton Gmail
2019-06-24 1:37 ` William Pechter
2019-06-24 3:17 ` Jason Stevens
2019-06-24 1:57 ` Steve Nickolas
2019-06-24 2:09 ` pechter
2019-06-24 0:03 ` Theodore Ts'o
2019-06-24 0:19 ` Seth Morabito
2019-06-24 0:33 ` Larry McVoy
2019-06-24 1:58 ` Steve Nickolas
2019-06-25 3:54 ` Jonathan Gevaryahu
2019-06-25 11:21 ` ckeck
2019-07-09 16:28 ` Mary Ann Horton Gmail
2019-07-09 16:53 ` KatolaZ
2019-07-09 17:12 ` Henry Bent
2019-07-09 17:25 ` Seth Morabito
2019-07-09 17:34 ` Henry Bent
2019-07-09 19:19 ` Henry Bent
2019-07-09 19:41 ` Richard Salz
2019-07-09 20:09 ` Grant Taylor via TUHS
2019-07-09 20:58 ` Henry Bent
2019-07-09 20:54 ` Mary Ann Horton Gmail
2019-07-09 21:30 ` Grant Taylor via TUHS
2019-07-09 21:35 ` Grant Taylor via TUHS
2019-07-09 21:37 ` Grant Taylor via TUHS
2019-07-09 21:46 ` Henry Bent
2019-07-09 22:02 ` Henry Bent
2019-07-09 23:23 ` Mary Ann Horton Gmail
2019-07-10 0:06 ` Dan Cross
2019-07-10 0:26 ` Grant Taylor via TUHS
2019-07-10 0:38 ` Dan Cross
2019-07-10 0:49 ` Larry McVoy
2019-07-10 0:57 ` Clem Cole
2019-07-10 1:26 ` [TUHS] V0 B Compiler Warren Toomey
2019-07-10 1:29 ` Clem Cole
2019-07-10 1:32 ` [TUHS] Plot 10 Sources Clem Cole
2019-07-10 2:51 ` Charles Anthony
2019-07-10 3:00 ` Charles Anthony
2019-07-10 3:01 ` Clem Cole
2019-07-10 12:51 ` Nelson H. F. Beebe
2019-07-10 14:34 ` Clem cole
2019-07-10 1:02 ` [TUHS] Floppy to modern files for Usenet maps Arthur Krewat
2019-07-10 1:19 ` Larry McVoy
2019-07-10 1:34 ` Dave Horsfall
2019-07-10 0:28 ` Mary Ann Horton Gmail
2019-07-09 22:01 ` Mary Ann Horton Gmail
2019-07-09 22:44 ` Grant Taylor via TUHS
2019-07-09 23:14 ` Mary Ann Horton Gmail
2019-07-10 0:24 ` Grant Taylor via TUHS
2019-07-10 1:13 ` Mary Ann Horton Gmail
2019-07-09 17:33 ` Clem Cole
2019-07-15 3:21 ` [TUHS] Historical " Mary Ann Horton Gmail
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=20190624014020.D24AD156E40C@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=tuhs@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).