IBM CTI 2572 manual Local Area Network Overview, Master/Slave vs. Local Area Networks

Page 13

CHAPTER 2. LOCAL AREA NETWORK OVERVIEW

Local Area Networks (LANs) grew from the need to interconnect many intelligent devices in a non-proprietary manner. Today, the most widely used LAN standards are Token-Ring (IEEE 802.5) and Ethernet (IEEE 802.3). Token Bus (IEEE 802.4), was proposed by GM in the late 80’s as a part of the Manufacturing Automation Protocol (MAP). Token Bus has seen limited use, primarily due to cost and installation difficulty. It is briefly discussed in this document to provide a more complete perspective of factory networking alternatives.

2.1 Master/Slave vs. Local Area Networks

Master/slave networks are commonly used in factory floor communications. These networks use a master station (computer or /controller) and multiple slave devices (such as controllers, terminals, or readers). The master station polls each slave unit on the network in turn, requesting services or information. After the slave performs the task (or indicates that it cannot), the master polls the next slave. This scheme works reasonably well when there are few devices on the network. However, as the size of the network grows, more and more master processor resources and network bandwidth must be devoted to the "overhead" of polling. This overhead limits throughput and lengthens response time, especially since most master/slave networks operate at a data rate of 115 K bits/sec or less.

Local area networks (LANs), on the other hand, do not have a master station. All stations on the network can initiate a message. Standard rules for media access determine when a given station may send a message. Media access rules usually involve passing a token or listening for traffic on the line. As a result, the overhead of a typical local area network is much lower than a master/slave network. This characteristic, coupled with much higher signalling rates (10 - 16 Mb) provides much higher throughput and allows many more devices to be connected to the network. Because there is no master station, there is no single point of failure.

Each master/slave network tends to use a different protocol, partially because there is no generally accepted standard. The protocol is typically determined by the primary equipment manufacturer and in some cases the protocol may be proprietary, subject to copyright or patent laws. As a result, most master/slave networks have very poor multi-vendor inter-operability. Conversely, LANs such as Ethernet and Token-Ring have protocols that are well specified and documented by standards bodies such as IEEE and are supported by a wide number of vendors.

CTI 2572 Technical Overview Manual

3

Image 13
Contents Ethernet TCP/IP Adapter Module Technical Overview Page Document Disclaimer Statement Page Preface Page Table of Contents Page 802.3 Frame w/ Snap Header 10Base5 Thick Coax TopologyPage Description IntroductionClient Mode Server Mode2572 Functions Serial RedirectMaster/Slave vs. Local Area Networks Local Area Network OverviewToken Ring Topology Ieee 802.5 Token-RingEthernet Topology Coax Ethernet and IeeeFuture Technologies Ieee 802.4 Token BusSummary Page ISO Reference Model Ethernet OverviewEthernet Topologies and Media Physical Layer 10BaseT Unshielded Twisted Pair UTP Bridges Foirl Fiber OpticEthernet Protocol Data Link Layer Mixed MediaEthernet Version 2 and Ieee 802.3 Packet Ethernet Version 2 standard defines the packet as follows Requirement for Higher Level Protocols Ethernet AddressesPage Connectionless vs. Connection Oriented Protocols Network ProtocolsConnectionless Protocols Common LAN Protocols Connection-Oriented ProtocolsIPX/SPX Page TCP/IP Components TCP/IP OverviewIP Address Internet ProtocolSubnet Address Mask Internet Control Message Protocol Icmp Address Resolution Protocol ARPUser Datagram Protocol UDP Transmission Control Protocol TCP That other network nodes can accessStream Orientation Connection-Oriented CommunicationsTCP Segment Reliable Data Transfer2572 TCP/IP Support Berkeley SocketsPage Non Intelligent Terminal Protocol PLC Command InterfaceTask Codes