SOFTWARE

Network Integration

Windows NT 4.0 Server

Netzwerkeinbindung KR C1 07.99.01 en

1 of 28

e Copyright

KUKA Roboter GmbH

This documentation or excerpts therefrom may not be reproduced or disclosed to third parties without the express permission of the publishers. Other functions not described in this documentation may be operable in the controller. The user has no claim to these functions, however, in the case of a replacement or service work. We have checked the content of this documentation for conformity with the hardware and software described. Nevertheless, discrepancies cannot be precluded, for which reason we are not able to guarantee total conformity. The information in this documentation is checked on a regular basis, however, and necessary corrections will be incorporated in subsequent editions. Subject to technical alterations without an effect on the function.

PD Interleaf

2 of 28

Contents

1.1 1.2 1.3 1.4 1.4.1 1.4.2 1.4.2.1

Networking.

Types of network (hardware). Types of network (software). Network structure. Procedure. Hardware. Software. Configuration of the LAN Controller on the MFC.
2.1 2.1.1 2.1.2 2.1.3 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5

Network installation.

Installation. Network service. Previous network driver. New network driver. Settings. Network service. TCP/IP address. User information. Access control. Hardware settings.

3.1 3.2

Central archiving.
Introduction. User--defined systems.

4.1 4.2 4.3

Remote diagnosis and maintenance.
Introduction. Remote diagnosis. Remote maintenance.

3 of 28

4 of 28

Networking

This chapter describes how to network KUKA robots, what hardware conditions must be met and how to activate the network facility under Windows95.
Types of network (hardware)
The prerequisite for networking robots is the network facility of the Windows95 system. operating
The networking of computers has a long history that stretches back to the earliest days of the computer age. It is therefore not surprising that a number of different types of networks have been devised over the years. In the field of PC networking, but also in other heterogeneous networks, the so--called Ethernet plays an important role. For this reason, Ethernet is the only sensible method for networking KUKA robots. In order to describe the relationships in communication between two or more computers, the OSI 7--layer model is used. A detailed description of this reference model is beyond the scope of this documentation. The only important thing to know is that communication between two computers occurs via seven logical levels. Ethernet (the more precise name is IEEE 802.3) occupies the second level (data link layer). The first level is the physical layer. It is responsible for physical transmission of data (electrical or optical) to and from the network.

2nd layer 1st layer

Data Link Layer Physical Layer
Reliable data transfer; Ethernet Interface to the transmission medium
Table 1 OSI reference model It can be noted from this model that a wide range of physical technologies can be used in the first layer. The main thing is that there is a gateway between the first and second levels. Cables are also assigned to layer 1. The following illustration shows the different types of cable that can be used with Ethernet.
Coaxial Cable type: RG--58A/U Char. impedance: 50 ohms 10 Mbit/s

Copper Twisted pair

Shielded Different cable types Char. impedance between 100 and 150 ohms 10--100 Mbit/s Unshielded
Transmission rates > 100 Mbit/s Fiberglass Fiber--optic cable No electromagnetic interference

1Illustration

adapted from Dictionary of PC Hardware and Data Communication Terms

Fig. 1 Types of cable1

5 of 28
Network Integration Coaxial cables: A coaxial cable consists of two concentrically aligned conductors. The outer conductor is usually grounded and thus serves as a shield. As this conductor is also used for data transmission, however, it is at extremely high risk from electromagnetic interference. Coaxial cables are poorly suited to networking over long distances, or across several buildings, as so--called ground loops can easily arise. A network set up using coaxial cables is also known as a 10Base--2 or ThinWire network. A coaxial cable is highly suitable for a small network linking computers in close proximity to one another, as it can be used quickly without the need for additional hardware. The coaxial cable is out of place in industrial settings, where electromagnetic interference has to be taken into consideration. Twisted pair cables: Twisted pair cables comprise paired strands twisted together. Twisting the strands helps to reduce electromagnetic interference. With this type of cable, a distinction is made between unshielded twisted pair cables (UTP) and shielded twisted pair cables (STP). Whereas in UTP cables several strand pairs are shielded together, an STP cable contains strand pairs which are individually shielded as well as sharing a common external shield. Unshielded twisted pair cables are usually used in so--called 10Base--T networks. This kind of network supports a data transfer rate of 10 Mbit/s with UTP cables. Unshielded twisted pair cables (UTP) are extremely suitable for small to medium-sized networks with a data transfer rate of 10 Mbit/s (10Base--T). Because of the twisting of the strand pairs and the external shield, interference does not have such a major effect as with coaxial cables. A hub is required (see below). Shielded twisted pair cables guarantee a data transfer rate of up to 100 Mbit/s (100Base--T). They can, of course, also be used in a 10Base--T network. Shielded twisted pair cables (STP) are ideally suited for use in medium--sized to large networks. They are used particularly under industrial conditions because of their low susceptibility to electromagnetic interference. In a 100Base--T network, data are transmitted at a speed of 100 Mbit/s. A hub is required (see below). Unlike coaxial cables, which are connected to their respective computers using a tee coupler, twisted pair cables are always connected using a point--to--point connection (both connectors on a cable are plugged directly into the respective devices). In order to network several computers together, an additional device is required: a so--called hub. This device acts as a concentrator for the computer data.

6 of 28

1 Fiber--optic cables:

Networking (continued)

The use of fiber--optic cables also allows a transfer rate of 100 Mbit/s. As the data are transferred via an optical medium, electromagnetic radiation has no effect. The damping effect of a fiber--optic cable is several times lower than that of a copper wire. This allows transmission over long distances (up to 2 km). Data transfer using fiber--optic cables is very expensive. The electrical signal must first be converted into light using an additional device (media interface connector). Fiber--optic cables are also very expensive compared with copper cable. Use of fiber--optic cables is only recommended where no other cable type works. This would be the case, for example, in the proximity of welding systems (strong electromagnetic radiation) or to connect networks over long distances or over several buildings. The type of cable used depends on the circumstances. It is not possible to make a hard and fast rule.
Types of network (software)
As KUKA robots are fitted with the operating system Windows95, and only Windows computers are being networked, use of the so--called Microsoft Network suggests itself. This makes it possible, using operating system functions, to access other computers in the network. There remains the question of the choice of transmission protocol. The three most commonly used protocols are discussed below. Only three protocols are usually used in PC networks: G G G NetBEUI IPX/SPX TCP/IP
NetBEUI comes from Microsoft and is the transmission protocol for the Microsoft Network referred to above. For this reason it would seem a natural choice to use this protocol. However, it does have one decisive disadvantage: it is not capable of routing (see below). IPX/SPX is the very fast transmission protocol primarily used in Novell networks. Novell has announced that it is dropping this protocol and will be using TCP/IP in future. TCP/IP is the most widely distributed transmission protocol. Originally developed for military use, it now represents the central core of the global network known as the Internet. TCP/IP is capable of routing. As all nodes (computers) can access the network at the same time with Ethernet, this leads to ever greater data traffic the more computers are connected to the network. The probability of a collision (simultaneous access by two or more computers) thus also increases, thereby diminishing the effective data transfer rate. For this reason it is sensible to establish subnetworks, so--called network segments. If a computer addresses a communication partner which is not located in the same segment, a so--called router assumes the task of forwarding the data to a different network segment. With the right network design, you can get the network segments to work at the best possible speed. Use of the TCP/IP transmission protocol is strongly advised for networking KUKA robots. This makes it possible for individual robot networks to grow and/or merge together. Furthermore, a TCP/IP network offers very high performance. TCP/IP can be used in conjunction with the Microsoft Network.

7 of 28

Network structure
As previously mentioned, the robots are integrated in a Microsoft Network. Depending on the applications in the network (this is covered later), it is worth considering whether or not to provide a computer to carry out central network tasks (server). The introduction of such a computer is highly recommended, as this relieves the robot controllers of network tasks. If a further computer is already planned, it is a good idea to install the operating system WindowsNT for which there is a server version. This NT server software ensures the best integration of Windows95 computers in a Microsoft Network (domain concept). Furthermore, it offers significantly more security features. The following network structure thus results:

Ethernet

Robot 1 (Windows95)

Robot 2 (Windows95)

Server (WindowsNT)

Robot 3 (Windows95)

Robot n (Windows95)

Fig. 2 Network structure

8 of 28

Procedure

Hardware
First of all, of course, it is necessary to check the requirements and decide on the optimum type of cable to use. Twisted pair (UTP or STP) is often chosen. Depending on the number of computers to be networked, a suitable hub must be selected (check suitability for UTP or STP). The positioning and location of the computers must be recorded. It is best to draw a plan with the cable routing included. This will give you the respective cable lengths. You can now start on the physical networking of the robots, with one end of a cable connected to a hub and the other end to the robots network card. The KUKA multi--function card (MFC) already has a network card integrated on it, which can be used for this purpose. Once the computers are physically networked, the network must be configured.

Software

As the control computers are not delivered set up for operation in a local network, a number of manual settings must be made. First check the type of multi--function card used (MFC 1 or MFC 2). The type of multi--function card must be made known to the operating system (Win95). This is done by means of the network settings in the Control Panel. The driver corresponding to the type of MFC used must be selected here. The network protocol TCP/IP is used, as described above. This must also be entered via the network settings in the Control Panel. Enter a valid IP address under Properties. With TCP/IP, each computer receives an address which identifies it unambiguously (IP address). These addresses are subdivided into classes and consist of one part which designates the network segment and one part which designates a computer within this segment. An introduction to the IP address system is beyond the scope of this documentation. Once these settings have been made, the computer is then in the position to be able to participate in network traffic.

9 of 28

Network Integration 1.4.2.1 Configuration of the LAN Controller on the MFC Configuring the network card G G G Switch on controller During the run--up sequence, press the key F8 when the message Starting Windows 95. is displayed, then select item 7 (Safe mode command prompt only). Start C:\TOOLS\MFC\EZSTART.EXE (the CD drive cannot be addressed in this mode so copy the TOOLS directory to the hard disk beforehand); the following settings should be displayed: ------G I/O Base: 340 IRQ: 11 RAM Window: None ROM Window: None Network Interface: Auto Media Detection Other Settings: I/O Mapped, PnP -- Disabled
If one or more of these settings is incorrect, alter them using the buttons Custom/ Setup.
Key codes: Move between buttons or input windows=TAB, Make a selection in an input box=UP/DOWN, Activate a radio button=SPACE. Remember to press Save. It is then possible to move back using the Previous button. G G G An adapter test can be carried out by means of Custom/Basic. Quit the program using the Exit button. Switch off and reboot the controller.
If Plug--and--Play (PnP) is enabled on the MFC, another driver will be loaded for the LAN card when the MFC is exchanged because Windows thinks that two network cards are now installed. It is imperative for this to be avoided.

10 of 28

Network installation
Click on Start, select Settings, then click on Control Panel.
Double--click the Network icon.

Installation

Network service

Click on Add.

11 of 28
Network Integration Click on Service and then on Add.
Click on Microsoft. Confirm the selection File and printer sharing for Microsoft Network, then click OK.

Previous network driver

If there is already an SMC EtherEZ (8416) multi--function card on your computer, it must be replaced with an up--to--date version.

Click on Remove.

12 of 28
Network installation (continued)

New network driver

Click on Adapter and then on Add.
Select the manufacturer SMC and the adapter SMC EtherEZ (8416). Click on Have Disk.
Insert the installation software from the manufacturer into the drive. Click on Browse and then, depending on the specific adapter, enter: e:\internat\tools\network\mfc or e:\internat\tools\network\mfc2

13 of 28

Network Integration Network driver for MFC: Click on OK.

Click on OK.

Select SMC EtherEZ (8416). Click on OK.

14 of 28

Network installation (continued) Network driver for MFC2: Click on OK.
Select SMC 9000 Ethernet Adapter. Click on OK.

15 of 28

Settings
The following settings serve merely as an example. Consult your system administrator for further information if required.
Click on Client for Microsoft Networks and then on Properties.
Click on Log on to Windows NT domain and enter a Windows NT domain1). Select Quick logon. Click on OK.
1) Ask your system administrator!

16 of 28

TCP/IP address
In the Network dialog box click on TCP/IP--> SMC EtherEZ (8416) or TCP/IP--> SMC 9000 Ethernet Adapter, and then on Properties.
Click on Specify an IP address and enter the TCP/IP address1). The entry in the Subnet Mask is made automatically. Click on OK.

Example

Click on the Advanced tab, and there select the entry Set this protocol to be the default protocol. Click on OK.

17 of 28

User information
Select the Identification tab in the Network dialog box.
Enter the following: Computer name1) Workgroup1) Computer Description1) This information is visible to other users if you select to be able to view your computer across the network.

18 of 28

Access control
Select the Access Control tab in the Network dialog box.
Click on User--level access control and enter a domain1). Click on OK.

19 of 28

Hardware settings
Click on SMC EtherEZ (8416) in the Network dialog box. Click on Properties.
Click on the Resources tab. Using BY select: I/O address range: Interrupt (IRQ): Memory address: Click on OK. 340-35F 11 D8000-DBFFF
The necessary data are copied from the hard drive.

20 of 28

Network installation (continued) Click on Yes to restart your computer.
Enter the following: User name1) Password1) Domain Click on OK.

21 of 28

22 of 28

Central archiving

The primary aim of this chapter is to highlight the possibilities which arise when robot controllers are working in a network.

Introduction

Networking computers allows you to access the file system of a remote computer via the network. This in turn makes it possible to exchange the files thus reached. This is, of course, not unconditionally possible. As a rule, each user in a local network can determine which files and directories should be accessible to whom. This makes it possible, for example, to share a special directory containing data that are to be collected in a central computer. This idea can now be pursued in a wide range of different directions.

User--defined systems

The possibilities afforded by file access via the network are manifold. It is thus difficult to describe a universal application. In order to avoid time and money being invested in the development of functions that are not even required, we suggest the production, after consultation with the customer/user, of an individually tailored solution which will guarantee 100% satisfaction. Possible solutions could include: G a backup system, running on the server, which regularly downloads data from the clients, or a backup system, running partly on the clients, which only saves altered data on the server, or a data management system which makes it possible to manage different versions of the data on the server. A defined version of the data could then be copied back onto the client from a central location. or many others.

23 of 28

24 of 28
Remote diagnosis and maintenance
If suitable software is used, it is possible to monitor and operate individual robot controllers remotely. Networking the computers facilitates this process.
It is possible to access a computer remotely using the so--called remote management software. Two options can be selected here: G G file transfer between two computers remote operation of a computer
As previously described, it is sensible for the KUKA control PCs already to be linked together in a local network. In this way, file transfer capability is already ensured in any case (as described). It is not, however, possible to operate one computer in the network from another. An additional piece of software is required for this, which must be installed on both computers. This remote management software is able to relay the display of one computer over the local network onto another computer. The local computer (host) can even be operated via the keyboard and mouse of the remote computer (remote control). There are usually several methods for doing this: G G G Simple monitoring of the host computer; keyboard and mouse input from the remote control is not possible. Normal remote control of the host computer; keyboard and mouse input is equally possible from either computer. Administration mode; keyboard and mouse input can be blocked on the host; in addition to this, the display can also be switched off on the host computer (useful for concealing administrative tasks from ordinary users).

Here also, of course, unconditional access at any time to the host computer is again not possible. The host application of the remote management software must first be activated. Only then can the remote control computer establish a link to the host. If the host application is installed on all the control computers in the local network, it is possible to access all these computers from another one in the network via the remote control software. This process can be taken a stage further by bringing a distant computer into the local network via Dial--Up Networking. This procedure is known as Remote Access Service (RAS) in WindowsNT/Windows95 and requires a modem or ISDN connection. This RAS facility is admirably implemented in WindowsNT. Settings can be made on the NT server defining which computers and which people are authorized access to the local network via RAS. If the NT server is also used as a domain controller (see above), unauthorized access can be filtered out very easily. Anyone now wishing to access the local network via the RAS facility must first log onto the domain controller. A valid identification must be used for this (user name and password). The RAS facility also offers another interesting feature: Callback G G on a preset number on a user--defined number

25 of 28

Network Integration Callback on a preset number: A callback number can be preset for each identification. As soon as the RAS facility on the NT server receives a call, it checks the user name that has been used. If a callback number exists for this name, the server breaks off the connection and calls this number back. In this way, unauthorized access from an unknown location can be prevented (because the RAS server always calls back on the preset number). This process provides the ultimate in security; by the same token, however, it is also rather inflexible. Callback on a user--defined number: This procedure is selected if the connection costs are not to be borne by the caller. This feature must be entered on the NT server for each identification. Now, if a remote computer calls the RAS server, the user name is again checked. If the callback on a user--defined number function is activated for this identification, the RAS server opens a window in which the caller can enter the desired callback number. If no number is entered here, the RAS connection is made nonetheless; i.e. the caller decides which party should meet the cost of the connection. When configuring the RAS facility, it is possible to decide which domain identification gets RAS access rights and which does not. In this way you can ensure that only certain identifications (e.g. Support) can access the local network via RAS. If a caller is confirmed by the NT domain controller, the whole network is available to him as if he were connected via a network card. Access via Dial--Up Networking requires the use of communications hardware. Depending on the type of telephone connection, this can be a modem or an ISDN adapter. A connection between an analog modem and a digital ISDN adapter is, of course, not possible. A single modem or ISDN adapter (in the NT server) is enough to enable remote access to all computers in the local network.

Remote diagnosis

Using the facilities described above, errors on a KUKA control computer can be detected very quickly. If a customer calls the KUKA Customer Support department because of an error, the person in Support can immediately examine the computer in question. Using Dial--Up Networking on his computer, he logs onto the relevant NT server, to which the affected computer is also connected. His computer is then a node of the robot network. With the aid of the remote management software he can then access the faulty computer and, in certain circumstances, thanks to the display, provide an error diagnosis. A further application for this feature is monitoring. It is often interesting to monitor the status of computers/robots from a central position. This can be accomplished easily using a remote management software application. This, however, is a very basic method, as only the current screen contents are displayed. Professional monitoring is best carried out using the Simple Network Management Protocols (SNMP). SNMP is part of TCP/IP and offers the possibility of transporting status information between computers and other network components (e.g. hubs, switches, routers, etc.). This makes it possible to monitor all the important components of a robot network from a central position. Using SNMP requires additional development expenditure. Using TCP/IP when networking robots allows the use of SNMP for monitoring.

26 of 28

Remote diagnosis and maintenance (continued)

Remote maintenance

Use of RAS and remote management software makes it significantly easier to look for and eliminate errors in a remote computer and likewise facilitates administration. Support can react very quickly to a customer call and, under certain circumstances, eliminate the robot controller error remotely. This helps to reduce costs and downtime. Furthermore, software maintenance and system administration can be carried out remotely.

27 of 28

28 of 28

FactSheet

ETS Supported Network Interface Cards
The tables below list the NIC drivers that are provided with the ETS release. Note that you can write your own custom drivers for NICs that are not included in this document. As of version 14.1, ETS support three different network stacks. Within the VSB they are called TCP/IP, TCP/IPv2, and TCP/IPv3. Each stack uses a different set of driver libraries to support the listed NICs. Driver libraries keep the same base name but add version numbers to the end, 7 for TCP/IPv2 and 8 for TCP/IPv3. Take the Intel driver for example TCP/IP uses Eth-igig.lib, TCP/IPv2 uses Eth-igig-7.lib, and TCP/IPv3 uses Ethigig-8.lib.

Tested Cards

The following Network Interface Cards (NICs) have been tested. Cards have been tested for IPv4 operation.
Driver Eth-amdp.lib supports TCP/IP (Vendor ID 0x1022)
Device ID 0x2000 Device Description Am79C970/1/2/3/5, PCnet LANCE PCI Ethernet Controller, Advanced Micro Devices
Driver Eth-cs89.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Vendor Crystal Semiconductor)
Device ID Device Description CS90x0 - Crystal LAN CS8900A Ethernet controller
Driver Eth-dec.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Vendor ID 0x1011, 0x1385, 0x11AD, 0x10D9, 0x1282, 0x1317)
Device ID 0x0009 Device Description DC21140, Digital DE500 PCI Fast Ethernet Controller
Driver Eth-i855.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Vendor ID 0x8086)
Device ID 0x1229 0x1209 Device Description 82557/8/9/0/1, Fast Ethernet LAN Controller, Intel PRO/100 S Server Adapter (82550EY ) 82559ER (8255xER/IT) Fast Ethernet Controller
ETS Supported Network Cards - 2009 IntervalZero, Inc
Ref#: DOC-ETS-002 7.22.2009
Driver Eth-igig.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Intel Corporation - Vendor ID 0x8086)
Device ID 0x100e 0x1010 0x107D 0x109A Device Description 82540EM, Gigabit Ethernet Controller, Intel Pro 1000 MT Desktop 82546EB, Dual Port Gigabit Ethernet Controller (Copper), Intel PRO/1000 MT Dual Port Gigabit Ethernet Adapter 82572EI, , Gigabit Ethernet Controller (Copper), Intel 82572 PT Gigabit Ethernet Adapter 82573L Intel Motherboard D975XBX. Intel PRO/1000 PL Network Adaptor Found on IBM ThinkPads T60s and X60s 82574L Intel Gigabit Ethernet Controller

0x10D3

Driver Eth-ne2k.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3
Device ID ISAPNP\AXE2201 NE2000 ISAPNP Device Description ISA card NEC 2000
Driver Eth-ns15.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Vendor ID 0x100b)
Device ID 0x0020 Device Description DP83815/16, MacPhyter 10/100 Mb/s Ethernet MAC & PHY
Driver Eth-rtl.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Vendor ID 0x10EC, 0x1211, 0x1113, 0x1186)
Device ID 0x8139 0x8169 Device Description RTL-8139/8139C/8139C+, Realtek RTL8139 Family PCI Fast Ethernet NIC RTL8119, Single Gigabit LOM Ethernet Controller
Driver Eth-via.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Vendor ID 0x1106)
Device ID 0x3106 Device Description VT6105M/LOM, Rhine III PCI Fast Ethernet Controller

Additional Cards

The following Network Interface cards (NICs) have not been tested, but based on their chipset they should work correctly with ETS v14.1. Driver Eth-3com.lib supports: (Vendor ID 0x10B7) ETS Supported Network Cards - 2009 IntervalZero, Inc
FactSheet Device ID Device Description 3COM EtherLink III 3C589/D/E Series Network card, PCMCIA
Device ID 0x2000 Device Description AMD 79C961/a, PCNet LANCE ISA Ethernet Controller, Advanced Micro Devices
Device ID 0x0014 0x0019 0x0002 0x8169 0xC115 0x9102 0x0531 0x0985 Device Description DC21041, Tulip Plus Ethernet Adapter DC21142 PCI/CardBus 10/100 Mbit Ethernet Ctlr LC82C169C, NETGEAR FA310TX Fast Ethernet PCI Adapter, (k82c168) GA311, Gigabit Ethernet Adapter LC82C115, PNIC II PCI MAC/PHY, LNE100TX Dual Fast Ethernet Adapter DM9102/A/AF, 10/100 Mbps Fast Ethernet Controller MX98715/25, Single Chip Fast Ethernet NIC Controller an983, FastNIC 10/100 Fast Ethernet Adapter

Device ID 0x1030 0x2449 0x1039 0x103a 0x103b 0x1059 Device Description 825593, PCI Networking device 82559ER, Integrated 10Base-T/100Base-TX Ethernet Controller 10011734, LAN Controller with 82562ET/EZ PHY 82801DB, LAN Controller with 82562ET/EZ (CNR) PHY 82801DB , LAN Controller with 82562EM/EX PHY 82551QM, Intel Fast Ethernet PCI/CardBus Controller
Driver Eth-igig.lib supports TCP/IP, TCP/IPv2, and TCP/IPv3 (Intel Corporation - Vendor ID 0x8086) ETS Supported Network Cards - 2009 IntervalZero, Inc
FactSheet Device ID 0x1015 0x1017 0x1016 0x101e 0x1000 0x1001 0x1008 0x100f 0x1026 0x1079 0x1013 0x1075 0x1078 0x1019 0x1051 (default, not GI) Device Description 82540EM, Gigabit Ethernet Controller(LOM), Intel PRO/1000 MT Mobile Connection 82540EP, Intel Gigabit Ethernet Controller 82540EP, Intel Gigabit Ethernet Controller (LOM) 82540EP, Intel Gigabit Ethernet Controller (Mobile) 82542, Intel Gigabit Ethernet Controller 82543GC, 10/100/1000 Ethernet Controller (Fiber), Intel PRO/1000 F Sever Adapter 82544EI/GC, Gigabit Ethernet Controller (Copper), PRO/1000 XT Gigabit Ethernet Adapter 82545EM, Gigabit Ethernet Controller (copper), PRO/1000 MT Gigabit Ethernet Adapter 82545EP, Gigabit Ethernet Controller, Intel PRO/1000 MT Server Adapter 82546GB, Dual Port Gigabit Ethernet Controller 82541EI, Gigabit Ethernet Controller (Copper), PRO/1000 MT Gibabit Ethernet Adapter 82547EI, Gigabit Ethernet Controller, PRO/1000 CT Network Connection 82541ER, Gigabit Ethernet Controller 82547EI Gigabit Ethernet Controller (LOM) 82801EB/ER, PRO/100 VE Network Connection
Device ID Device Description DP83905, AT/LANTIC AT Local Area Network Twisted-Pair DP8390D/NS32490D, Network Interface Controller
Device ID 0x8129 0x1300 0x1211 Device Description RTL8139d, 10/100 Fast Ethernet Controller DL10038C or DL10038, Fast Ethernet Adapter, DFE-538TX mpx en5038a1, 0A422T1 118F, network card EN-1207D EtherCard PLUS (8003), ISA EtherCard Elite16 Ultra (8216) ISA SMC EtherEZ (8416), ISA SMC 83C690, ISA
FactSheet SMC 83C790, ISA SMC 83C795, ISA SMC 91C92, PCMCIA SMC 91C94, PCMCIA
Driver Eth-s24hr.lib supports TCP/IP (Vendor ID 0x1562)
Device ID Device Description Symbol Wireless Networker 802.11b
Driver Eth-s24.lib supports TCP/IP (Vendor ID 0x1562)
Device ID Device Description Spectrum S24 Wireless
Device ID 0x3043 0x6100 0x3065 0x3053 Device Description VT86C100A, Rhine 10/100 Ethernet Adapter VIA VT86C100A, Rhine II PCI Fast SATA and Ethernet controller VT6102, Rhine II PCI Fast Ethernet Controller VT6105M, Rhine III Management Adapter