Fact-checked by Grok 2 weeks ago

ARCNET

ARCNET, short for Attached Resource Computer Network, is a (LAN) technology developed by Datapoint Corporation and introduced in 1977 as the first commercially available networking system for microcomputers. It utilizes a to manage , enabling deterministic communication among devices in a shared . Originally designed for office automation and linking Datapoint's own terminals and computers, ARCNET gained popularity throughout the 1980s for its reliability and ease of installation, supporting heterogeneous systems in business and industrial settings. Key technical features include support for up to 255 nodes, data rates starting at 2.5 Mbps and scalable up to 20 Mbps via enhancements like ARCnet Plus, and flexible topologies such as star, bus, or tree configurations using (e.g., RG-62) or later fiber optics. The protocol incorporates error detection via CRC-16, variable packet sizes up to 507 bytes, and automatic reconfiguration for , making it suitable for real-time applications. Standardized under ANSI/ATA 878.1-1999 (previously ANSI/ATA 878.1-1992), which aligned with aspects of IEEE 802.4 for token bus networks, ARCNET emphasized and was promoted by the , founded in 1987. Despite its early dominance, ARCNET declined in the as Ethernet offered higher speeds, lower costs, and broader vendor support, though it persists in niche embedded applications like industrial control, , (e.g., as a ), and for its deterministic performance in noisy environments. The standard was withdrawn from ANSI in 2007 but remains freely available for legacy and specialized uses.

History

Development

ARCNET was invented by John A. Murphy in 1976 while working as a senior engineer at Datapoint Corporation, where he led the development of the hardware to address the need for connecting multiple intelligent terminals to shared resources, such as disk controllers. The project originated from internal requirements at Datapoint to enable resource sharing among terminals, evolving from concepts for terminal emulation into a dedicated networking solution. Datapoint Corporation publicly announced ARCNET on December 1, 1977, positioning it as the first commercial (LAN) designed for clustering computer systems in office settings. The key design motivations centered on creating a low-cost system that provided deterministic communication, suitable for tasks and enabling real-time data sharing among microcomputers without the complexities of synchronous timing. This approach emphasized simplicity, reliability, and ease of manufacturing, targeting networks of up to 250 nodes using 8-bit addresses. Early prototypes featured wire-wrap boards operating at a simulated 10% of full speed, with the initial Resource Interface Module (RIM) implemented as a unit containing around 100 integrated circuits. These prototypes incorporated a token-passing mechanism to avoid collisions, ran at an initial speed of 2.5 Mbit/s, and were tested using for connectivity. The first external installation took place in December 1977 at Chase Manhattan Bank in , marking the beginning of business deployments, with over 10,000 nodes in use by the late 1970s across various enterprise environments.

Adoption and Market Impact

Initially proprietary to Datapoint Corporation, ARCNET's technology opened to third-party manufacturers in the early 1980s, enabling broader hardware availability from companies such as , Compex, and Thomas-Conrad. This shift facilitated compatibility with diverse systems and spurred market expansion beyond Datapoint's original terminals. A pivotal partnership formed in December 1981 when , parent of , selected ARCNET as the standard networking solution for its , 12, 16, and 6000 computers, citing its low cost, 2.5 Mbps speed, ease of installation, and reliability for business and educational use. 's widespread retail distribution of ARCNET cards—priced at $299 in 1981—drove adoption among small businesses for tasks like word processing and , as well as in schools for networked setups. This significantly boosted ARCNET's visibility and integration into early ecosystems. By the end of the , ARCNET reached its market peak with an installed base exceeding 20 million nodes worldwide, particularly valued for its deterministic token-passing reliability in non-critical environments. Its competitive edge included per-node costs under $500, far lower than Ethernet interfaces which often exceeded $700 in the early , alongside simpler installation via flexible bus or star topologies compared to the more rigid wiring demands of networks. Standardization efforts commenced in the through the ARCNET , culminating in the ANSI/ 878.1 standard that formalized protocols for token bus access and physical layers, while third-party support extended to PC compatibles via affordable adapter cards from vendors like Standard Microsystems Corporation. This openness further entrenched ARCNET in small office and educational markets during its height.

Decline and Evolution

The decline of ARCNET as a dominant technology accelerated in the late due to Ethernet's dramatic price reductions, which made it more affordable for widespread adoption, alongside its standard speed of 10 Mbit/s compared to ARCNET's 2.5 Mbit/s. Ethernet's and alignment with the emerging / further propelled its growth, as these factors facilitated easier integration and scalability in diverse computing environments. ARCNET's market share, which had positioned it as a leader in the with annual chip production peaking at 800,000 units in , eroded significantly by the , shifting it to a niche status. provided brief competition during this period but ultimately shared ARCNET's fate, as Ethernet captured the majority of the market through superior marketing, vendor support, and standardization efforts. To counter these pressures, Datapoint introduced ARCnet Plus in 1992, increasing the speed to 20 Mbit/s while ensuring with existing ARCNET infrastructure. That same year, the ANSI/ATA 878.1 standard was ratified, establishing a for token bus operation that improved among vendors and devices. ARCNET's embedded reliability ensured its persistence in legacy systems long after Ethernet's dominance in general-purpose networking, with over seven million nodes deployed worldwide by the mid-1990s in applications demanding deterministic performance, such as factory automation, security systems, and building controls. Its token-passing mechanism provided guaranteed message delivery and automatic reconfiguration, making it a trusted choice for real-time embedded environments where upgrades were not feasible.

Technical Specifications

Network Topology and Architecture

ARCNET networks employ a logical bus topology for data transmission, where simulates a bus structure among nodes, while the physical implementation most commonly uses a wiring configuration with active or passive hubs to connect devices. This hybrid approach allows for flexible cabling, including options for bus or distributed topologies, enabling of faults and easier compared to pure bus systems. Hubs serve as central points, with passive hubs supporting shorter distances and active hubs providing signal regeneration for larger . Each in an ARCNET is assigned a unique 8-bit , supporting up to 255 nodes per , with address 0 reserved for broadcast purposes. This addressing scheme facilitates direct node-to-node communication and ensures efficient resource allocation in multi-node environments. The architecture adheres to the OSI model's Physical (Layer 1) and 2) layers, particularly emphasizing the (MAC) sublayer to deliver deterministic performance through token-based access, minimizing collisions and guaranteeing fair bandwidth sharing. Scalability is achieved through the use of multiple cascadable hubs, which extend to a maximum of 20,000 feet (approximately 6,096 meters) while maintaining . Active hubs, in particular, allow for up to 10 levels of cascading between nodes, accommodating distributed configurations for or settings. This design supports growth without requiring a complete rewiring. The network's is enhanced by an automatic reconfiguration process, which remaps active following additions, removals, or failures, typically completing in 20-30 milliseconds without manual intervention. During reconfiguration, a burst signal initiates polling to rebuild the node map, ensuring continued operation and rapid recovery from disruptions. This self-healing mechanism underscores ARCNET's reliability in mission-critical applications.

Protocol Mechanics

ARCNET utilizes a token-passing mechanism to coordinate access among nodes and avoid collisions, operating on a logical ring where the token—termed the Invitation to Transmit (ITT)—circulates sequentially based on node addresses ranging from 1 to 255. This ordered progression ensures each node receives the opportunity to transmit in turn, with fairness maintained by limiting the token hold time to the duration required for sending a single packet, preventing any node from dominating the network. The mechanism supports up to 255 nodes, and the token is passed to the next highest address after transmission or if no data is pending. The protocol defines key packet types to facilitate communication: the for token circulation, Free Buffer Enquiry (FBE) packets to probe destination availability, data packets () that carry up to 507 bytes of in either short (1-253 bytes) or long (257-507 bytes) formats, and short or NAK responses for confirmation. Data packets include source ID () and destination ID (DID) fields, which serve as identifiers for logical sequencing and reliable packet tracking within the structure. Broadcast packets to node 0 are unacknowledged to streamline dissemination. During transmission, a awaits the before attempting to send; upon receiving it, the issues an FBE broadcast to the intended recipient to confirm free buffers, waiting up to 75 µs for an response. If buffers are available ( received), the sends the with and DID for sequencing and reliability; if not (NAK or timeout), the is immediately passed onward without transmission. This inquiry step ensures efficient use of by avoiding buffer overflows at the destination. Error detection relies on a 16-bit appended to data packets, using the X^{16} + X^{15} + X^2 + 1 to verify integrity against transmission errors. Upon CRC failure, NAK receipt, or timeout during ACK wait, the sender discards the packet and retries on the subsequent token rotation, with up to 128 or 4 attempts configurable before exceptional handling. Flow control is inherently provided through the mechanism and FBE/ACK/NAK exchanges, without additional windowing or avoidance beyond these basics. The token-passing design yields deterministic , with each rotation completing in a predictable timeframe based on network size and traffic—typically under 10 ms even in larger setups (e.g., ~7 ms empty for 255 ), allowing maximum wait times calculable from ~28 µs token pass per plus transmission and propagation delays, enabling bounded delays for applications without probabilistic delays common in contention-based protocols.

Physical and Data Link Layers

The physical layer of ARCNET, as defined in the original ANSI/ATA 878.1 standard, operates at a data signaling rate of 2.5 Mbit/s with a tolerance of ±0.01%, utilizing signaling over . The primary medium is RG-62/U 93-ohm , which supports a topology through active hubs or a bus topology with multi-drop connections, enabling via Manchester-like dipulse encoding where a logical "1" is represented by a 200 ns pulse followed by 200 ns silence, and a "0" by 400 ns silence. Transceivers employ a antenna-like design for signal transmission, with impedance matched at 93 ohms (±4 ohms) to prevent reflections, and termination resistors of 93 ohms required at bus ends. In the configuration, maximum lengths reach 610 meters (2000 feet) between hubs, while bus s are limited to 305 meters (1000 feet) with up to eight nodes per segment to maintain and limit propagation delay to under 31 microseconds. Later adaptations of the extended support to twisted-pair cabling, such as Category 3 unshielded twisted-pair (UTP) like Type 3 media with 100-120 impedance, allowing bus segments up to 122 meters (400 feet) with similar node limits, and optic options using 62.5/125 μm multimode at 850 nm wavelength for distances up to 1825 meters (6000 feet) via ST or connectors. These media maintain the 2.5 Mbit/s rate and dipulse signaling, with receiver of at least 1.2 kΩ in bus mode and tolerances of ±50 ns cumulative or ±2.5 ns per transmitter. Daisy-chaining is supported in star topologies via active , allowing up to four nodes per port without additional termination, though bus configurations require careful to avoid signal degradation. At the data link layer, ARCNET employs a medium access control (MAC) sublayer that structures transmission into basic frames, each beginning with a 6-symbol start delimiter (SD) sequence of binary ones for synchronization, followed by frame-specific information symbols (FIS) up to 515 information symbol units (ISUs) in length, where each ISU encodes 8 data bits (least significant bit first) transmitted via dipulse-encoded bits at the physical layer. The primary data frame, known as the packet (PAC), supports a maximum of 512 bytes total, comprising a 1-byte control field (e.g., SOH at 0x01), 1-byte source ID, 2-byte destination ID, 1- or 2-byte continuation pointer, 1-byte system code, up to 507 bytes of user data, and a 2-byte frame check sequence (FCS) using CRC-16 (polynomial X¹⁶ + X¹⁵ + X² + 1). Control frames like invitation to transmit (ITT), free buffer enumeration (FBE), acknowledge (ACK), and negative acknowledge (NAK) are shorter, using 1-4 bytes in the FIS for token passing and error handling, ensuring reliable delivery over the physical medium.

Standards and Variants

Original Standards

The original ARCNET standard, ANSI/ATA 878.1-1992, established the foundational specifications for a 2.5 Mbit/s token-bus local area network, emphasizing coaxial cable topologies and deterministic access control to ensure reliable data transmission in office and early industrial environments. This standard formalized the protocol originally developed by Datapoint Corporation in 1977, defining frame formats, medium access methods, and physical layer interfaces to promote hardware compatibility across vendors. It supported both bus and star configurations using RG-62/U coaxial cabling, with active hubs enabling distributed star layouts for up to 255 nodes while maintaining signal integrity over distances up to 2,000 feet. While ARCNET's token-passing mechanism drew conceptual influences from the IEEE 802.4 token-bus standard for its logical ring maintenance and invitation-to-transmit sequences, the protocol remained proprietary in its implementation details, diverging from full IEEE conformance to prioritize simplicity and low-cost hardware. The ANSI/ATA 878.1-1992 specification outlined an 8-bit addressing scheme (ranging from 1 to 255, with 0 reserved for broadcast), a 2.5 MHz clock for dipulse signaling (400 ns per signal element), and a 16-bit (CRC) for error detection. Token circulation occurred sequentially in a logical ring ordered by address, with automatic reconfiguration to recover lost tokens or integrate new stations without central arbitration. The ARCNET Trade Association (ATA), formed in 1987, played a pivotal role in standardizing and verifying compliance through testing protocols embedded in ANSI/ATA 878.1-1992, ensuring that certified hardware from multiple manufacturers could seamlessly integrate into mixed networks. These tests focused on frame handling, timing synchronization, and , with the ATA accrediting implementations that met the standard's conformance classes (e.g., for and early twisted-pair variants). Original implementation guidelines stemmed from Datapoint's proprietary documentation, including the 1983 ARCNET Designer's Handbook, which detailed designs, cabling practices, and protocol timing for developers building compatible nodes. ATA supplements further refined these for broader adoption, emphasizing electrical characteristics and diagnostic features to minimize deployment issues.

ARCnet Plus and Enhancements

ARCnet Plus, introduced in 1992 by Datapoint Corporation, served as an upgraded version of the original ARCnet standard, boosting the data transmission rate from 2.5 Mbit/s to 20 Mbit/s. This enhancement was designed to address growing demands in local area networks while preserving compatibility with legacy infrastructure. By utilizing the same cabling types—such as RG-62 or twisted-pair wiring—ARCnet Plus networks could integrate original 2.5 Mbit/s nodes seamlessly, allowing mixed-speed operations where faster nodes communicated at reduced rates with slower ones to maintain . The core enhancements in ARCnet Plus focused on optimizing the physical and layers for higher without altering the fundamental token-passing . It employed an improved scheme, clocked at a higher frequency to accommodate the eightfold increase in speed, which minimized signal distortion over existing media while supporting reliable transmission. Packet sizes were expanded significantly, reaching up to 4224 bytes compared to the original's limit of around 508 bytes, which reduced overhead and improved for data-intensive tasks. Additionally, was lowered through tighter timing parameters and streamlined handling, enabling token rotation times under 4 across a fully loaded of up to 255 nodes, a substantial improvement over the original's typical 20-30 cycles. These changes collectively supported emerging applications like streaming, which required consistent low-delay . Standardization efforts integrated these features into revisions of the ANSI/ATA 878.1 specification, with the 1999 update formally incorporating support for alternate data rates up to 20 Mbit/s and enhanced media options. Dual-mode transceivers were developed to facilitate automatic speed negotiation, ensuring smooth coexistence of ARCnet and ARCnet Plus devices on the same topology. Hardware implementations, such as the SMC COM90C66 ARCnet Plus controller, became available for embedded systems, providing compact, low-power solutions for industrial and office automation environments. These controllers handled the higher-speed signaling and compatibility logic, making ARCnet Plus viable for real-time control applications.

Later Adaptations

In the 1990s, ARCNET adaptations extended support to unshielded twisted-pair cabling, including Category 3 and equivalent media, to leverage existing wiring infrastructure. The ANSI/ATA 878.1 standard defined the specifications for this medium, recommending 100-ohm impedance cables terminated with RJ11C or RJ45 connectors in bus or topologies. These configurations allowed segment lengths up to 100 in setups between nodes and active hubs, or 122 meters in bus arrangements with a maximum of eight nodes, enhancing flexibility for and light industrial deployments while maintaining the 2.5 Mbit/s data rate. Fiber optic variants emerged to address industrial requirements for longer distances and immunity, particularly in harsh environments like controls. Multimode implementations, using 50/125 μm, 62.5/125 μm, or 100/140 μm cores at 850 nm , supported the standard 2.5 Mbit/s rate over distances up to 2,740 meters with 100/140 μm , depending on rates of 4 dB/km. These duplex setups, often with or connectors, enabled point-to-point or star connections in modular hub systems, providing and suitability for geographically dispersed industrial networks. Protocol extensions in the included the Thomas-Conrad Network (TCNS), a software-compatible enhancement to ARCNET for industrial control applications. Developed by Thomas-Conrad Corporation, TCNS operated at 100 Mbit/s while retaining the token-passing mechanism for deterministic performance, making it viable for transaction-heavy embedded systems. This adaptation built on ARCNET's inherent priority handling in token circulation to support timely data exchange in control environments, though it did not achieve widespread standardization beyond proprietary implementations. Wireless adaptations of ARCNET remained rare and largely experimental, with short-range RF prototypes explored for niche applications but never reaching formal standardization. Open-source efforts have sustained ARCNET's relevance through modern firmware, notably the Linux kernel drivers (version 2.91 and later), which include Ethernet encapsulation support (arc0e protocol) for seamless integration and bridging with Ethernet networks. These drivers, compatible with chipsets like COM20020, facilitate embedded and legacy system interoperability without proprietary hardware.

Applications and Legacy

Historical Implementations

Datapoint Corporation pioneered ARCNET implementations with its proprietary hardware, beginning with the 2200 series terminals introduced in late 1977. These systems featured Resource Interface Modules (s), compact units that served as integrated controllers for networking multiple 2200 terminals, enabling shared access to peripherals like printers and storage devices. The RIM handled token-passing protocols over cabling in a star topology, supporting up to 255 nodes and facilitating early tasks such as and report generation. Later ARC systems, including the 5500 and 6600 models from the mid-1970s, incorporated enhanced ARCNET interfaces with 16-bit processors running at speeds up to 6.67 MHz and memory capacities reaching 256 KB, allowing for clustered configurations in business environments. Third-party vendors expanded ARCNET compatibility to popular microcomputers of the era. , through Tandy, offered ARCNET interface cards for the , Model 12, Model 16, and Tandy 6000 series starting in 1981, marketed as "Radio Shack ARCNET" for small business and educational networking. These cards connected via the system's expansion bus, supporting and printer access in multi-user setups. For the , third-party network interface cards from manufacturers like Microsystems Corporation enabled ARCNET connectivity, allowing integration into heterogeneous environments despite the platform's primary use of other protocols like . Software support for ARCNET proliferated in the 1980s, broadening its appeal for DOS-based systems. Early DOS drivers, developed by figures like , provided foundational s for file and print sharing on Datapoint hardware. , a dominant , offered robust ARCNET compatibility from its 1983 release, with Advanced 1.0 in 1985 supporting ARCNET adapters for client-server architectures; following the addition of ARCNET support in 1985, had sold over 300,000 units. Custom software stacks extended to productivity applications, including client-side support for , which leveraged ARCNET for collaborative document editing in office settings. 6 for Tandy systems included reserved ARCNET functions for seamless integration. ARCNET found notable adoption in clustered systems for banking and education during its peak. The first major out-of-house installation occurred in 1977 at Chase Manhattan Bank in , where ARCNET connected terminals for transaction processing and data management across branches. In education, large-scale deployments included the Michigan Education Data Network Association's network in the , supporting over 100 nodes in lab environments for administrative tasks and resource sharing among schools. These implementations highlighted ARCNET's , with configurations routinely exceeding 100 nodes in shared-terminal setups for cost-sensitive institutions.

Modern and Industrial Uses

In industrial control systems, ARCNET remains relevant for programmable logic controllers (PLCs) and supervisory control and data acquisition (SCADA) setups, leveraging its token-passing protocol to deliver deterministic timing essential for real-time operations in manufacturing automation. For example, Contemporary Controls offers ARCNET connectivity solutions that facilitate precise coordination in factory processes, such as welding controls and automated assembly lines, where predictable performance prevents disruptions. This reliability stems from ARCNET's embedded design, which supports up to 255 nodes over distances suitable for plant floors without the variable latency seen in more modern protocols. As of 2025, Contemporary Controls remains a primary vendor, offering ARCNET interface modules compatible with modern operating systems like Windows and Linux for legacy and new embedded deployments. ARCNET endures in embedded systems due to its robustness and low power requirements, particularly in legacy , medical devices, and point-of-sale () terminals. In medical applications, it enables communications within electronic equipment and networking for imaging systems like machines, ensuring fault-tolerant data exchange in critical environments. For avionics-related uses, ARCNET appears in space travel simulation equipment, including astronaut systems, where high reliability supports simulation of isolated network conditions. In POS contexts, it connects terminals to manager workstations, as seen in race track pari-mutuel wagering systems for handling bet processing and odds calculations. Current hardware sustains ARCNET's viability, with products like the ARCNET/PCI20 series network interface modules from Contemporary Controls providing bus compatibility for integration into contemporary systems running Windows or . These modules support and twisted-pair cabling, allowing seamless upgrades in existing industrial setups without requiring full network overhauls. In isolated networks, ARCNET offers advantages over Ethernet by avoiding congestion-related vulnerabilities through its orderly token-passing mechanism, while its 2.5 Mbps speed suffices for sensor data and control signals in low-bandwidth industrial scenarios. This positions ARCNET in a , primarily serving upgrades to legacy installations and specialized embedded deployments rather than broad-scale adoption. Standards from the ARCNET continue to underpin this longevity by ensuring compatibility with evolving hardware.

References

  1. [1]
    About the ARCNET Trade Association
    ARCNET has evolved into a mature, well-established LAN technology since its introduction as the first commercially available LAN on the market in 1977.
  2. [2]
    ARCnet - Viasat Internet | Satellite Internet Providers
    In the late 1970s, the Datapoint Corporation made a significant leap in computer networking by developing ARCnet (Attached Resource Computer Network).
  3. [3]
    Arcnet - A fast and real-time control network. - BH Automation
    Arcnet is a token-passing local area network ( LAN ) especially designed for embedded technologies. This standard offers up to 10 Mbps data rate, 255 nodes or ...
  4. [4]
    [PDF] Oral History of John Murphy
    Jun 3, 2004 · Murphy: Okay. I was born in Tulsa, Oklahoma in 1943. I was the youngest of five children, the youngest by a long shot.
  5. [5]
    [PDF] ARCNETworks - Bitsavers.org
    We bought the design in. 1986, which gave us another computer bus for ARCNET. Internally we started development of a PC Bus ARCNET card, since the PC Bus was ...Missing: invention | Show results with:invention
  6. [6]
    [PDF] ARCNET Tutorial - Contemporary Controls
    ARCNET was originally classified as a local area network or LAN. A LAN is defined as a group of nodes that communicate to one.
  7. [7]
    ARCNET - NETWORK ENCYCLOPEDIA
    ... ten thousand ARCNET LAN installations were in commercial use around the world, and Datapoint had become a Fortune 500 company. As microcomputers took over ...
  8. [8]
    [PDF] the datapoint arc - Bitsavers.org
    December 1977. Datapoint Corporation publicly announces the release of its new. Attached Resource Computer (ARC) network. The original press release states that ...
  9. [9]
    ARCNET - Matthew Reed's TRS-80.org
    Their implementation, known as “Radio Shack ARCNET,” consisted of hardware for the TRS-80 Model II/12/16/6000 series and later for the Model 2000 and Model 1000 ...
  10. [10]
    About ARCNET
    ARCNET, once quite popular in office automation, has reinvented itself into an embedded networking technology that is frequently found in applications such ...Missing: invention date
  11. [11]
    What happened to ARCnet - The Silicon Underground
    Feb 5, 2024 · ARCnet was the first commercially available local area network standard, beating both Ethernet and Token Ring to market.
  12. [12]
    [PDF] ARCNET Tutorial
    ▻ ANSI/ATA 878.1-1999 Standard. ▻ Ideally suited for an industrial network. What is ARCNET? Page 4. ▻ Broad Acceptance. ▻ Large Installed Base.
  13. [13]
    [PDF] COM20019I Cost Competitive ARCNET (ANSI 878.1) Controller with ...
    SMSC's COM20019I is a member of the family of Embedded ARCNET Controllers from Standard. Microsystems Corporation. The device is a general purpose ...<|separator|>
  14. [14]
    The LAN turns 30, but will it reach 40? - Computerworld
    Jan 31, 2008 · The first commercial network was based on ARCnet technology, but Ethernet emerged as the king of company LANs, which may soon become defunct ...
  15. [15]
    None
    ### Summary of ARCNET Historical Facts
  16. [16]
    Venture capital and the birth of the local area networking industry
    In 1977, Datapoint offered a LAN technology called ARCnet to integrate its small business computers into a homogeneous computing environment, allowing users to ...Venture Capital And The... · Introduction · Early Networking And The...<|separator|>
  17. [17]
    ARCnet for embedded control (Journal Article) | OSTI.GOV
    Oct 31, 1996 · has proven its reliability in the seven million nodes currently installed worldwide. ARCnet is used in hundreds of embedded applications ...Missing: legacy persistence
  18. [18]
    [PDF] ATA 878.1 - 1999 Local Area Network: Token Bus
    In order to comply with the basic data rate of 2.5Mbps, low capacitance twisted-pair cable is required. ... [30] ARCNET Designer's Handbook, 61610, Datapoint ...<|control11|><|separator|>
  19. [19]
    [PDF] ARCNET Local Area Network Protocols - Bitsavers.org
    ARCNET protocol requires that each node must be able to hear any other node, and there be only a single path between any two nodes. Signals must be able to pass.
  20. [20]
    [PDF] COM20022i 3V - Microchip Technology
    Using an ARCNET protocol engine is the ideal solution for embedded control applications because it provides a deterministic token-passing protocol, a highly ...
  21. [21]
    [PDF] ARCnet Designer's Handbook
    ARCNET is a token passing system. Control, including detection and re-creation of lost tokens, is completely dispersed among the nodes of the network.Missing: goals cost
  22. [22]
    History of Datapoint Corporation - FundingUniverse
    In 1992, Datapoint premiered an enhanced version of one of its leading products, the ARCnet Plus, a computer networking system. This introduction promised ...<|control11|><|separator|>
  23. [23]
    Networking Encyclopaedia - Big Documentation
    20-Mbps version of the ARCnet standard. ARCnet Plus has the following features: I Backward-compatibility with ARCnet ... Level 4 cable is used for ARCnet Plus, a ...
  24. [24]
    Chapter 4 - LAN Technologies - Scribd
    ARCnet Plus offers several improvements over traditional ARCnet: It has a maximum packet size of 4224 bytes versus 516 bytes of ARCnet. It is able to support ...
  25. [25]
    [PDF] ARCNETworks - Bitsavers.org
    This was all accomplished and on October 16, 1992, ANSI/ATA 878.1 1992. Local Area Network: Token Bus (2.5 MBPS) became an ANSI standard. Both Billy Cox and ...
  26. [26]
    ARCnet
    ARCnet uses a Token Passing bus structure much like IEEE802.4. It's most common speed is still 2.5 Mbps, but we know of versions runnig 20 Mbps (ARCnet plus ...Missing: early prototypes Mbit/
  27. [27]
    [PDF] APPLICATION NOTE - Contemporary Controls
    with ARCNET's 2.5 Mbps signaling. Multimode fibers have bandwidth specifications in frequency- distance units (Mhz-km) which depend upon the operating ...
  28. [28]
    ARCnet Hardware - The Linux Kernel documentation
    This file contains a quick introduction to ARCnet hardware, some cabling tips, and a listing of all jumper settings I can find.Missing: third- party Corvus
  29. [29]
    ARCnet — The Linux Kernel documentation
    These are the ARCnet drivers for Linux. This new release (2.91) has been put together by David Woodhouse <dwmw2@infradead.org>, in an attempt to tidy up the ...
  30. [30]
    [PDF] Datapoint - Bitsavers.org
    Introduction. 5. Chapter 1 The Debut: July 10, 1971. 9. Chapter 2 The Gathering: 1968. 17. Chapter 3 Tooling the Datapoint 3300: First Half of 1969.
  31. [31]
    NetWare 2.x Notes | OS/2 Museum
    May 9, 2019 · A dedicated NetWare 2.x server was installed in its own partition and did not require DOS to boot at all (in that regard it was like NetWare 6.0).
  32. [32]
    Novell NetWare - EDM2
    Oct 24, 2023 · NetWare became the predominant network operating system of the 80s ... NetWare/ARCnet; NetWare/G-Net; NetWare/SM. Advanced NetWare. 1.0 (1985) ...
  33. [33]
    ARC Control ARCNET for Control - Contemporary Controls
    The real-time performance of its token-passing protocol along with its simplicity of use makes it ideal for embedded applications. Contemporary Controls is the ...Missing: TCNS Transparent 1990s priority
  34. [34]
    ARCNET Resource Center
    ARCNET is a high-speed LAN for real-time control. The ARCNET Resource Center provides information to assist designers, integrators, and users of this ...Missing: deterministic office
  35. [35]
    ARCNET - Contemporary Controls
    Legacy ARCNET systems can still be retained while migration is being made to Ethernet networks. By using ARCNET servers, convenient access to ARCNET networks is ...Missing: persistence reliability
  36. [36]
    https://www.ccontrols.com/arccontrol/pci20.htm
  37. [37]
    ARCNET PCI20 Series - Contemporary Controls
    The PCI20 Series of network interface modules (NIMs) interfaces ARCNET with PCI bus computers. The high performance PCI bus allows for jumperless configuration.
  38. [38]
    Keeping Industrial Networks Secure with ARCNET and RS-485
    Feb 27, 2025 · Predictable, Reliable Communication With ARCNET's structured data transmission, there's no random congestion like in Ethernet-based networks.