🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.dcom.lans.misc
5 messages
5 total messages Started by Rob Warnock Sat, 23 Jan 1993 06:02
Re: Multi-drop Serial Protocol Wanted (RS-232)
#323
Author: Rob Warnock
Date: Sat, 23 Jan 1993 06:02
34 lines
2018 bytes
jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
+---------------
| We're looking for sources or references for a "multi-drop serial protocol"
| i.e. one that allows multiple devices to be attached to the same serial line.
| Our goal is to have data exchanged between a host cpu and any number of
| ( well ok, 8 :) attached slave devices. ... Any help (even remote references
| from 15 years ago) would be most welcome.
+---------------

Well, 15-year-old stuff (or 20-yr-old) is indeed where you should look! ;-}

Many "ancient" serial protocols allowed multi-drop: BSC ("BiSync"), SDLC,
DDCMP, to name just a few. And the phone company provided leased lines
in multi-dropped configurations. It was quite common to have a central
location in, say, Chicago, with a multi-drop line that hit Kansas City,
Dallas, Abilene, and another one that hit Atlanta, Jacksonville, Miami, &c.

As far back as 1973 or -4, at Dig. Comm. Assoc. we were shipping statistical
multiplexers that could multi-drop off a single sync phone line (e.g., using
Bell 208 or 209 modems). That is, each multi-dropped mux could have multiple
local terminals, all running to the same host via a "head end" mux. The muxes
used our own implementation of DEC's DDCMP as the link-layer protocol (as
we'd call it today), but if I did it again today, I'd probably use HDLC (only
because so few current programmers are familiar with DDCMP, which is really
quite nice).


-Rob

-----
Rob Warnock, MS-9U/510		rpw3@sgi.com
Silicon Graphics, Inc.		(415)390-1673
2011 N. Shoreline Blvd.
Mountain View, CA  94043
Re: Multi-drop Serial Protocol Wanted (RS-232)
#325
Author: Peter Desnoyers
Date: Sun, 24 Jan 1993 03:15
22 lines
1585 bytes
jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
+---------------
| We're looking for sources or references for a "multi-drop serial protocol"
| i.e. one that allows multiple devices to be attached to the same serial line.
| Our goal is to have data exchanged between a host cpu and any number of
| ( well ok, 8 :) attached slave devices. ... Any help (even remote references
| from 15 years ago) would be most welcome.
+---------------

If you can run sync instead of async and you're willing to do some
coding, Localtalk would be a good protocol for this sort of thing -
it's fast (in comparison to async), it only needs an 8530 and some
simple driver hardware, and you can take advantage of an existing base
of machines that talk it.

If you need to do async (e.g. your host only has async ports) then any
poll-response protocol would do - you just need to ensure that each
poll has an address in it, and require that slave devices only
transmit in response to a poll.

				Peter Desnoyers
-- 
Re: Multi-drop Serial Protocol Wanted (RS-232)
#326
Author: William Hawkins
Date: Sun, 24 Jan 1993 18:14
16 lines
1293 bytes
>jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
>+---------------
>| We're looking for sources or references for a "multi-drop serial protocol"
>| i.e. one that allows multiple devices to be attached to the same serial line.

RS-232 is not a multi-drop protocol *electrically* because it holds
the line at the mark (or space) state.  You need the RS-485 protocol
to multi-drop devices, because it lets the line float if a device
has nothing to say.  There are 232 to 485 converters available (or
there were 7 years ago).  Then you can implement a master-slave
software protocol for the universe of devices attached to the line.

In ISO terms, RS-232/485 is barely a physical layer specification.
You get to do anything you want with the rest of the layers.

Bill Hawkins
Re: Multi-drop Serial Protocol Wanted (RS-232)
#327
Author: Dave Olson
Date: Sun, 24 Jan 1993 22:18
28 lines
2130 bytes
In <1993Jan24.181433.26225@rosevax.rosemount.com> bill@texan.rosemount.com (William Hawkins) writes:

| >jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
| >+---------------
| >| We're looking for sources or references for a "multi-drop serial protocol"
| >| i.e. one that allows multiple devices to be attached to the same serial line.
| 
| RS-232 is not a multi-drop protocol *electrically* because it holds
| the line at the mark (or space) state.  You need the RS-485 protocol
| to multi-drop devices, because it lets the line float if a device
| has nothing to say.  There are 232 to 485 converters available (or
| there were 7 years ago).  Then you can implement a master-slave
| software protocol for the universe of devices attached to the line.
| 
| In ISO terms, RS-232/485 is barely a physical layer specification.
| You get to do anything you want with the rest of the layers.

Wyse makes (made?) both 485 terminals, and 485 drops to rs232 protocol
boxes (2 and 8 232 ports per box).  I don't remember if they ever made
the controller boards.  This was done about 5 years back, originally as
a joint project with Altos.  I did a lot of the driver work, and it
worked pretty well (we ran 64 terminals at full speed both directions
off a 286 box).  As I recall, the datarate was about 1.4 Mbits/sec on
the multidrop wire. 
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
Re: Multi-drop Serial Protocol Wanted (RS-232)
#335
Author: Michael Burke
Date: Thu, 28 Jan 1993 14:28
30 lines
1779 bytes
In article <1993Jan24.181433.26225@rosevax.rosemount.com> bill@texan.rosemount.com (William Hawkins) writes:
>>jdc@isis.cs.wayne.edu (Jon Cardwell) writes:
>>+---------------
>>| We're looking for sources or references for a "multi-drop serial protocol"
>>| i.e. one that allows multiple devices to be attached to the same serial line.
>
>RS-232 is not a multi-drop protocol *electrically* because it holds
>the line at the mark (or space) state.  

Hogwash...

RS232 has been used for years with BSC 3270 multi-drop circuits. Generally,
the trick is to use the fastest modem turn around time possible to get best
results. The "poll-ack" protocols are above this physical standard.

Remember, multi-drop does not mean a "bus architecture" in the strictest
sense. One orders a multi-drop circuit from the Telco. I have not been
involved with BSC 3270 circuits for many years (about 15) so I have no idea
how one would go about building an in-house multi-drop circuit....


-- 
---
Michael Burke

Sea Change Corporation
6695 Millcreek Drive, Unit 8 
Mississauga, Ontario, Canada L5N 5R8
Tel: 416-542-9484  Fax: 416-542-9479
UUCP: ...!uunet!uunet.ca!seachg!burke
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads