ARCNET

1
ARCNET
Attached Resource Computer NETwork (abbreviated ARCNET or ARCnet) is a communications protocol for
local area networks. ARCNET was the first widely available networking system for microcomputers; it became
popular in the 1980s for office automation tasks. It was later applied to embedded systems where certain features of
the protocol are especially useful.
History
ARCNET was developed by principal development engineer John Murphy at Datapoint Corporation in 1976 under
Victor Poor, and announced in 1977.
[1]
It was originally developed to connect groups of their Datapoint 2200
terminals to talk to a shared 8" floppy disk system. As microcomputers took over from the Datapoint, ARCNET was
re-purposed as LAN. It was the first loosely-coupled LAN-based clustering solution, making no assumptions about
the type of computers that would be connected. This was in contrast to contemporary larger and more expensive
computer systems such as DECnet or SNA, where a homogeneous group of similar or proprietary computers were
connected as a cluster.
The token-passing bus protocol of that I/O device-sharing network was subsequently applied to allowing processing
nodes to communicate with each other for file-serving and computing scalability purposes. An application could be
developed in DATABUS, Datapoint's proprietary COBOL-like language and deployed on a single computer with
dumb terminals. When the number of users outgrew the capacity of the original computer, additional 'compute'
resource computers could be attached via ARCNET, running the same applications and accessing the same data. If
more storage was needed, additional disk resource computers could also be attached. This incremental approach
broke new ground and by the end of the 1970s (before the first cassette-based IBM PC was announced in 1981) over
ten thousand ARCnet LAN installations were in commercial use around the world, and Datapoint had become a
Fortune 500 company. As microcomputers took over the industry, well-proven and reliable ARCNET was also
offered as an inexpensive LAN for these machines.
ARCNET remained proprietary until the early-to-mid 1980s. This did not cause concern at the time, as most network
architectures were proprietary. The move to non-proprietary, open systems began as a response to the dominance of
International Business Machines (IBM) and its Systems Network Architecture (SNA). In 1979, the Open Systems
Interconnection Reference Model (OSI model) was published. Then, in 1980, Digital, Intel and Xerox (the DIX
consortium) published an open standard for Ethernet that was soon adopted as the basis of standardization by the
IEEE and the ISO. IBM responded by proposing Token Ring as an alternative to Ethernet but kept such tight control
over standardization that competitors were wary of using it. ARCNET was less expensive than either, more reliable,
more flexible, and by the late 1980s it had a market share about equal to that of Ethernet. Tandy/Radio Shack offered
ARCNET as an application and file sharing medium for their TRS-80 Model II/12, Model 16/6000, Tandy 2000,
Tandy 1000 and Tandy 1200 computer models.
When Ethernet moved from co-axial cable to twisted pair and an "interconnected stars" cabling topology based on
active hubs, it became much more attractive. Easier cabling, combined with the greater raw speed of Ethernet (10
Mbit/s, as compared with 2.5 Mbit/s for ARCnet) helped to increase Ethernet demand, and as more companies
entered the market the price of Ethernet started to falland ARCNET (and Token Ring) volumes tapered off.
In response to greater bandwidth needs, and the challenge of Ethernet, a new standard called ARCnet Plus was
developed by Datapoint, and introduced in 1992. ARCnet Plus ran at 20 Mbit/s, and was backward compatible with
original ARCnet equipment. However, by the time ARCnet Plus products were ready for the market, Ethernet had
captured the majority of the network market, and there was little incentive for users to move back to ARCnet. As a
result, very few ARCnet Plus products were ever produced. Those that were built, mainly by Datapoint, were
expensive, and hard to find.
ARCNET
2
ARCNET was eventually standardized as ANSI ARCNET 878.1. It appears this was when the name changed from
ARCnet to ARCNET. Other companies entered the market, notably Standard Microsystems who produced systems
based on a single VLSI chip, originally developed as custom LSI for Datapoint, but later made available by Standard
Microsystems to other customers. Datapoint eventually found itself in financial trouble and eventually moved into
video conferencing and (later) custom programming in the embedded market.
Even though ARCNET is now rarely used for new general networks, the diminishing installed base still requires
support - and it retains a niche in industrial control.
[2]
Description
Original ARCNET used RG-62/U coaxial cable of 93 impedance and either passive or active hubs in a star-wired
bus topology. At the time of its greatest popularity, this was a significant advantage of ARCNET over Ethernet. A
star-wired bus was much easier to build and expand (and was more readily maintainable) than the clumsy linear bus
Ethernet of the time. The "interconnected stars" cabling topology made it easy to add and remove nodes without
taking the whole network down, and much easier to diagnose and isolate failures within a complex LAN.
Another significant advantage ARCNET had over Ethernet was cable distance. ARCNET coax cable runs could
extend 610m (2,000ft) between active hubs or between an active hub and an end node, while the RG-58 (50) 'thin'
Ethernet most widely used at that time was limited to a maximum run of 180m (600ft) from end to end.
ARCNET had the disadvantage of requiring either an active or passive hub between nodes if there were more than
two nodes in the network, while thin Ethernet allowed nodes to be spaced anywhere along the linear coax cable.
However, ARCNET passive hubs were very inexpensive, being composed of a simple, small, unpowered box with
four ports, wired together with nothing more than four discrete resistors, so the disadvantage was not significant.
Passive hubs limited the distance between a node and an active hub to 30m (100ft). A passive hub could not be
connected directly to another passive hub. Unused ports on both types of hubs had to be terminated with a special
connector.
To reduce costs, while still allowing coverage over a wide area, a common practice was to use one or more
interconnected active hubs, each of which provided coverage for nodes no more than 60m (200ft) away. Cable was
run from each port of the active hubs to a different location no more than 30m (100ft) away. A passive hub would
then be attached to the end of the cable, and cables would be run locally from the passive hub, allowing connection
of up to three nodes. In this way, a single 8-port active hub could be used to connect 24 networked devices over an
area not exceeding 120m (400ft) in diameter.
ARCNET allowed only 255 nodes per network. Node IDs for LAN workstations were typically set by DIP switches
on the network interface card. Larger networks would have to be split into smaller networks, and bridged. The small
number of possible nodes and the need to manually configure IDs was a disadvantage compared with Ethernet,
particularly as large enterprise networks became common.
To mediate access to the bus, ARCNET, like Token Ring, uses a token passing scheme, rather than the carrier sense
multiple access approach of Ethernet. When peers are inactive, a single "token" message is passed around the
network from machine to machine, and no peer is allowed to use the bus unless it has the token. If a particular peer
wishes to send a message, it waits to receive the token, sends its message, and then passes the token on to the next
station. Because ARCNET is implemented as a distributed star, the token cannot be passed machine to machine
around a ring. Instead, each node is assigned an 8 bit address (usually via DIP switches), and when a new node joins
the network a "reconfig" occurs, wherein each node learns the address of the node immediately above it. The token is
then passed directly from one node to the next.
Historically, each approach had its advantages: ARCNET added a small delay on an inactive network as a sending
station waited to receive the token, but Ethernet's performance degraded drastically if too many peers attempted to
broadcast at the same time, due to the time required for the slower processors of the day to process and recover from
ARCNET
3
collisions.Wikipedia:Citation needed ARCNET had slightly lower best-case performance (viewed by a single
stream), but was much more predictable. ARCNET also has the advantage that it achieved its best aggregate
performance under the highest loading, approaching asymptotically its maximum throughput. While the best case
performance was less than Ethernet, the general case was equivalent and the worst case was dramatically better. An
Ethernet network could collapse when too busy due to excessive collisions. An ARCNET would keep on going at
normal (or even better) throughput. Throughput on a multi-node collision-based Ethernet was limited to between
40% and 60% of bandwidth usage (depending on source). Although 2.5 Mbit/s ARCNET could at one time
outperform a 10 Mbit/s Ethernet in a busy office on slow processors, ARCNET ultimately gave way to Ethernet as
improved processor speeds reduced the impact of collisions on overall throughput, and Ethernet costs dropped.
Wikipedia:Citation needed
In the early 1980s ARCNET was much cheaper than Ethernet, in particular for PCs. For example in 1985 SMC sold
ARCNET cards for around US$300 whilst an Ungermann-Bass Ethernet card plus transceiver could cost US$500.
Another significant difference is that ARCNET provides the sender with a concrete acknowledgment (or not) of
successful delivery at the receiving end before the token passes on to the next node, permitting much faster fault
recovery within the higher level protocols (rather than having to wait for a timeout on the expected replies). ARCnet
also doesn't waste network time transmitting to a node not ready to receive the message, since an initial inquiry
(done at hardware level) establishes that the recipient is able and ready to receive the larger message before it is sent
across the bus.
One further advantage that ARCNET enjoyed over collision-based Ethernet is that it guarantees equitable access to
the bus by everyone on the network. Although it might take a short time to get the token depending on the number of
nodes and the size of the messages currently being sent about, you will always receive it within a predictable
maximum time; thus it is deterministic. This made ARCNET an ideal real-time networking system, which explains
its use in the embedded systems and process control markets. Token Ring has similar qualities, but is much more
expensive to implement than ARCNET.
In spite of ARCNET's deterministic operation and historic suitability for real-time environments such as process
control, the general availability of switched gigabit Ethernet and Quality of service capabilities in Ethernet switches
has all but eliminated ARCNET today.
At first the system was deployed using RG-62/U coaxial cable (commonly used in IBM mainframe environments to
connect 3270 terminals and controllers), but later added support for twisted pair and fibre media. At ARCNET's
lower speeds (2.5 Mbit/s), Cat-3 cable is good enough to run ARCNET. Some ARCNET twisted-pair products
supported cable runs over 2000' on standard Cat-3 cable, far beyond anything Ethernet could do on any kind of
copper cable.
In the early 1990s, Thomas-Conrad Corporation developed a 100 Mbit/s topology called TCNS based on the
ARCNET protocol, which also supported RG-62, twisted-pair, and fiber optic media. TCNS enjoyed some success
until the availability of lower-cost 100 Mbit/s Ethernet put an end to the general deployment of ARCNET as a LAN
protocol.
However, because of its simple, robust nature, ARCNET controllers are still sold and used in industrial, embedded,
and automotive applications.
ARCNET
4
References
[1] "History", ARCNET Trade Association (http:/ / www. arcnet. com/ abtarc. htm#history)
[2] "ARCNET for Control" (http:/ / www.ccontrols.com/ arccontrol/ index. htm), ccontrols.com
External links
ARCNET Trade Association (http:/ / www. arcnet. com/ )
History of Datapoint, including ARCnet / ARCnet Plus Development (http:/ / www. fundinguniverse. com/
company-histories/ Datapoint-Corporation-Company-History. html)
Article Sources and Contributors
5
Article Sources and Contributors
ARCNET Source: http://en.wikipedia.org/w/index.php?oldid=601348237 Contributors: 74s181, Aldie, Alecv, Andy Dingley, Anss123, Bombsaway123, Brian Wowk, Bryan Derksen, Btilm,
Bumm13, Casey Abell, Crissov, Csigabi, Dennis Brown, Derek Ross, Diego bf109, Dmsar, Dogcow, Electron9, Engineerism, Gundark, Guy Harris, HarisM, Hu12, IIXII, Intgr, JLDBooth,
JoDonHo, JonHarder, Jsmaye, Karl Andrews, Matusz, Maury Markowitz, Michael B. Trausch, Miciah, Mild Bill Hiccup, Mindmatrix, Mintleaf, Mmtmmt, NickW557, Northamerica1000,
Npeters22, Olivier, Optichan, Pak21, Pjacobi, PseudoSudo, Ringbang, Rjwilmsi, Rsduhamel, SarahEmm, Skeetch, Snori, Stepho-wrs, Suruena, Surv1v4l1st, Thunderboltz, Tobias Bergemann,
Torchwoodwho, Trident13, Vanished user lkdfj39u3mfk4, Wmngreer, Zvar, 77 anonymous edits
License
Creative Commons Attribution-Share Alike 3.0
//creativecommons.org/licenses/by-sa/3.0/