Important User Information Because of the variety of uses for the products described in this publication, those responsible for the application and use of this

control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.

The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for the

Application, Installation and Maintenance of Solid-State Control

(available from your local Allen-Bradley office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in whole or part, without written permission of Rockwell Automation, is prohibited.

Throughout this manual we use notes to make you aware of safety considerations:

!death, property damage or economic loss

Attention statements help you to:

???identify a hazard

???avoid a hazard

???recognize the consequences

Allen-Bradley is a trademark of Rockwell Automation

Publication 1761-UM006A-EN-P - February 2001

Table of Contents ii

Glossary

Index

Publication 1761-UM006A-EN-P - February 2001

Preface

Publication 1761-UM006A-EN-P - January 2001

Preface P-2

Related Documentation

The following documents contain additional information concerning

Rockwell Automation products. To obtain a copy, contact your local

Rockwell Automation office or distributor.

Publication 1761-UM006A-EN-P - January 2001

Preface P-3

Publication 1761-UM006A-EN-P - January 2001

Preface P-4

Publication 1761-UM006A-EN-P - January 2001

Chapter 1

Publication 1761-UM006A-EN-P - February 2001

1-2 Product Overview

Publication 1761-UM006A-EN-P - February 2001

Default Settings

The ENI???s RS-232 port has the following default settings:

Table 1.1 RS-232 Settings

(1) The ENI receives NAKs and ACKs, but does not generate them.

Publication 1761-UM006A-EN-P - February 2001

1-4 Product Overview

Publication 1761-UM006A-EN-P - February 2001

Using a Web Browser with the ENI

You can access information about the ENI via your web browser. Simply enter the ENI???s TCP/IP address into the address field of your browser.

Publication 1761-UM006A-EN-P - February 2001

1-6 Product Overview

Publication 1761-UM006A-EN-P - February 2001

Chapter 2

Installation and Wiring

This product is tested to meet the Council Directive 89/336/EC Electromagnetic Compatibility (EMC) by applying the following standards, in whole or in part, documented in a technical construction file:

???EN 50081-2 EMC ??? Generic Emission Standard, Part 2 ??? Industrial Environment

???EN 50082-2 EMC ??? Generic Immunity Standard, Part 2 ??? Industrial Environment

This product is intended for use in an industrial environment.

Low Voltage Directive

This product is tested to meet Council Directive 73/23/EEC Low Voltage, by applying the safety requirements of EN 61131-2 Programmable Controllers, Part 2 - Equipment Requirements and

Publication 1761-UM006A-EN-P - February 2001

2-2 Installation and Wiring

Use only the following communication cables and replacement connectors in Class I Division 2 Hazardous Locations.

Publication 1761-UM006A-EN-P - February 2001

Publication 1761-UM006A-EN-P - February 2001

2-4 Installation and Wiring

Panel Mounting

Template

See Appendix A for panel mounting template.

Installation

3.Drill holes through the template.

4.Remove the mounting template.

5.Mount the unit.

Publication 1761-UM006A-EN-P - February 2001

ENI Port Identification

ETHERNET

RS232

FAULT

IP

Write-on area for

CABLE

EXTERNAL

Publication 1761-UM006A-EN-P - February 2001

2-6 Installation and Wiring

Publication 1761-UM006A-EN-P - February 2001

Ethernet Cables

Shielded and non-shielded twisted-pair 10Base-T cables with RJ45 connectors are supported. The maximum cable length between an ENI Ethernet port and a 10Base-T port on an Ethernet switch (without repeaters or fiber) is 100 meters (323 feet). However, in an industrial application, the cable length should be kept to a minimum.

With media converters or Ethernet switches, you can also connect to the following media:

???fiber optic

???broadband

???thick-wire coaxial cable (10Base-5)

???thin-wire coaxial cable (10Base-2)

Maintain ENI Connections

The unshielded twisted pair (UTP) patch cable on a switch should be labeled and treated as dedicated. Be careful when moving any cables, as port identity may be effected. If you are using a switch and must move the ENI to a new port for any reason, power-cycle the ENI. The power cycle forces a new Address Resolution Protocol (ARP) sequence which should immediately associate the ENI???s IP address with the port it is connected to.

You should also discourage any field personal from treating the ports of a switch as ???all the same???. This helps to prevent any problems with network communications being effected by moving cables.

Publication 1761-UM006A-EN-P - February 2001

2-8 Installation and Wiring

Table 2.1 RS-232 Connector Pin Assignments

124V dc

2ground (GND)

3no connection

4ENI input data, RxD

5no connection

6no connection

7ENI output data, TxD

8ground (GND)

RS-232 Cables

Port 2 of the ENI is an 8-pin mini-DIN RS-232 port that provides connection to DF1 compatible RS-232 devices. The table below describes the RS-232 compatible cables.

See page 2-2 for the list of cables that can be used in a hazardous environment.

Publication 1761-UM006A-EN-P - February 2001

Chapter 3

Publication 1761-UM006A-EN-P - February 2001

3-2 Operation

RSLinx on Ethernet (PC Connected to Ethernet)

Follow these steps to configure RSLinx for Ethernet operation.

1. Open RSLinx and open the driver configuration dialog.

Publication 1761-UM006A-EN-P - February 2001

Operation 3-3

2.The ???Configure Dialog??? will open, select Ethernet devices from the available drivers, and then click ???OK??? to load the driver into RSLinx.

Once the Ethernet driver is loaded, either highlight and select ???Configure??? or simply double click on the Ethernet driver.

Publication 1761-UM006A-EN-P - February 2001

3-4 Operation

At that point the station mapping screen will appear as illustrated here. Double click on the row below ???Host Name???, and enter the TCP/IP addresses that match the devices on your network that you will need access to.

When you are done entering the stations, click OK to close the station mapping window.

Publication 1761-UM006A-EN-P - February 2001

Operation 3-5

3.Open the AB_ETH-1 tree on your computer, autobrowse should be running and any active device that you have configured should be shown on the screen as illustrated below.

RSLogix 500

1. Open RSLogix 500 and select ???Comms???

Publication 1761-UM006A-EN-P - February 2001

3-6 Operation

2. Select ???AB_ETH-1, Ethernet.

3.Either expand the tree (select the + in the box, or select the device from the table to the right. From this point, you can then either go online or perform an upload or download.

Publication 1761-UM006A-EN-P - February 2001

Chapter 4

ENI Configuration (Node 248 to 254)

Publication 1761-UM006A-EN-P - February 2001

4-2 ENI Configuration (Node 248 to 254)

COM Port Settings

Use the Utility Settings screen to set the following:

???COM Port - The PC???s RS-232 port that the communications cable is plugged into.

???Baud Rate - Select a baud rate or choose Autobaud. See page 4-15 for more information.

???Parameter Upload Behavior and Parameter Download Behavior - This setting controls which parameters will be saved or loaded when you use the Load From or Save To buttons.

RS-232 Baud Rate and TCP/IP Parameters

Use the ENI IP Addr screen to set the following:

???232 Baud Rate - Select a baud rate or choose Autobaud. See page 4-15 for more information.

???TCP/IP Parameters - See page 4-12 for more information on valid addresses.

Publication 1761-UM006A-EN-P - February 2001

Save to ENI RAM or ENI ROM

You must save the configurations you have set. Click ENI RAM for temporary setups or ENI ROM to permanently save your settings. If you do not save the settings, they will revert to ???out-of-box??? on the next power-up.

E-Mail Settings

Use the Email screen to fill in the information for e-mail messages. E-mail servers are described on page 4-15. See chapter 6 for information on the ???To??? and ???From??? strings.

Publication 1761-UM006A-EN-P - February 2001

4-4 ENI Configuration (Node 248 to 254)

Message Routing

Use the Message Routing screen to fill in the destination addresses for DF1 messaging. Message routing is described in chapter 5.

Reset

Use the Reset screen to issue reset commands and to set the type of behavior that will occur at reset. The reset behavior options are described on page 4-11.

Publication 1761-UM006A-EN-P - February 2001

Publication 1761-UM006A-EN-P - February 2001

4-6 ENI Configuration (Node 248 to 254)

Publication 1761-UM006A-EN-P - February 2001

3.Open the message instruction and enter the appropriate variables. The variables are described in Table 4.1.

Table 4.1 Message Instruction Variables for Configuring ENI Data Parameters

4.With the controller in Run, initiate the message. The new TCP/IP information is transmitted to the ENI.

!248 information on page 4-11 for instructions.

Publication 1761-UM006A-EN-P - February 2001

4-8 ENI Configuration (Node 248 to 254)

Publication 1761-UM006A-EN-P - February 2001

2.Create your message logic using whatever conditional instructions you may need. This example uses bit B3:0/7 to condition the MSG instruction and message file 10, element 16 to manage the message session.

3.Open the message instruction and enter the appropriate variables. The variables are described in Table 4.2.

Table 4.2 Message Instruction Variables for Configuring ENI String Parameters

Publication 1761-UM006A-EN-P - February 2001

4-10 ENI Configuration (Node 248 to 254)

(1)See page 4-11 for more information on Save/Reset.

(2)The ENI address, ???0.0.0.0??? will be replaced by the IP address assigned to the ENI. For example, the string may be ENI191.225.181.52@eni1761.org. If the ENI does not have an assigned IP address, the string will be read as ENI0.0.0.0@eni1761.org.

(3)Changes to the Baud Rate take effect when the ENI power is cycled, or the configuration is saved to flash.

(4)Autodetect of CRC/BCC also occurs when autobaud is selected.

These parameters are described in more detail in the following sections.

Publication 1761-UM006A-EN-P - February 2001

Node 248 - Save/Reset Function

Depending on the value of the Save/Reset option, the ENI performs the following operations when receiving a PCCC Unprotected Write message of one element (integer) to Node 248.

Node 249 - From String

Node 249 holds the ASCII string that is sent with any e-mail message initiated by the ENI. Criteria for a valid E-mail From String include:

???The From String remains at the default value unless changed by the user. See page 4-10 for default information.

???The From String must contain an ???@??? symbol.

???The From String cannot contain any spaces or special ASCII characters.

???The maximum length of the From String is 64 characters. Any additional characters are ignored.

???The From String is sent from a String Table consisting of 84 characters.

???To configure the From String, initiate a message with a string element as the data. The message instruction procedure is shown on page 4-8.

Publication 1761-UM006A-EN-P - February 2001

4-12 ENI Configuration (Node 248 to 254)

Node 250 - TCP/IP Configuration

This procedure describes configuration for the TCP/IP parameters. The TCP/IP parameters are configured by sending a message instruction to the ENI (or by using the ENI Configuration Utility).

1.Configure a 485CIF write message in the Allen-Bradley controller.

2.Set the destination (target) node to 250. Using node address 250 directs this message to the TCP/IP configuration function.

3.The local integer file must be set up for at least 4 integer locations. The first 4 words define the IP address and are required. All remaining variables are optional.

The table below describes the TCP/IP functions that can be configured. The sections following the table describe the functions in more detail.

Table 4.3 TCP/IP Configuration Parameters

(1) The IP address must be configured. All other functions are optional.

Publication 1761-UM006A-EN-P - February 2001

ENI Configuration (Node 248 to 254) 4-13

Subnet Mask

A subnet mask is used to interpret IP addresses when the network is divided into subnets. If your network is not divided into subnets, then leave the subnet mask at the default or allow the ENI Configuration Utility to assign a default.

The subnet mask defaults to auto-detect mode ???out-of-box???. As long as the subnet mask is not manually set, the auto-detect mode follows the rules as shown below:

Table 4.4 Subnet Mask Auto-Detect Operation

Subnet Mask Auto-Detect Rules:

???Reading the subnet mask when the IP address is 0.0.0.0 returns a value of 0.0.0.0.

???When you manually configure the subnet mask, auto-detect is switched off and the configured mask is used.

???The ENI validates the configured subnet mask and if:

???The first octet is not equal to 255, the ENI returns status 0x10 and reverts to the previous mask, or

???The first octet is 255, but the remaining mask is not proper, the ENI returns status 0x10 and reverts to the previous mask.

???The definition of ???proper??? is that the mask must be a contiguous series of 1???s with no zeroes in between (i.e. 255.0.0.0 or 255.224.0.0 or 255.192.0.0 are valid, but 255.160.0.0 is not).

Security Mask

The Security Mask, when configured, allows you to restrict controller access to sources with IP addresses that are within some prescribed range. For example, if you wanted to restrict all message sources to be from within a company???s allocated IP address range, a Security Mask could be configured that would block any IP address outside that range. This only applies to messages to the controller. Web page access, for example, is not restricted.

Publication 1761-UM006A-EN-P - February 2001

4-14 ENI Configuration (Node 248 to 254)

The security masks default value is 0.0.0.0 out-of-box, which is defined as ???accept all register session requests???. A Security Mask of 255.255.255.255 is also defined as ???accept all register session requests???.

The follow examples illustrate the behavior of the security masks:

Table 4.5 Security Mask Behavior

You can use one or two security masks. If you wish to use only one security mask, use Security Mask 1 because it takes precedence over Security Mask 2 (for example, if Security Mask 1 is accepted, Security Mask 2 is not evaluated). Details of the relationship between the two masks are shown in the following table.

Table 4.6 Using Security Mask 1 and Security Mask 2

Security masks 1 and 2 are evaluated using the following logic:

Publication 1761-UM006A-EN-P - February 2001

Node 251 - E-Mail Server

The TCP/IP address stored in this location defines the mail server. The ENI sends all e-mail requests to this server, which then sends the e-mail message to the destination.

Node 252 - BOOTP Configuration

The ENI allows the BOOTP request to be disabled by clearing the

BOOTP Enable parameter in the channel Configuration File. BOOTP

Enable behaves as follows:

???0 = BOOTP configuration

???1 = soft configuration

When BOOTP Enable is disabled, the ENI will wait for a manual configuration.

The BOOTP enable/disable setting is only evaluated on power-up. Changes to the BOOTP configuration will not take effect until the next power cycle.

See Appendix B for information on using BOOTP.

Node 253 - Baud Rate

The first time the ENI is powered-up (out-of-the-box), it is set to Autobaud so that it can synchronize to the attached controller. The baud rate can be changed by sending a message to address 253 with one of the configuration values shown in the table below. Changes to the baud rate take effect when the ENI power is cycled or when a Save configuration to flash command (write to node 248) is received. The configuration value is sent as a 2-byte integer (1 element from an integer file).

The ENI also performs a CRC/BCC check when autobaud is operational. It reads a test PCCC_Diagnostic Status Request to determine if CRC or BCC is being used and adjusts to it.

Publication 1761-UM006A-EN-P - February 2001

4-16 ENI Configuration (Node 248 to 254)

Table 4.7 ENI Baud Rate Options

(1) All CompactLogix devices must be configured to use two stop bits when communicating with the ENI at 38.4K.

Publication 1761-UM006A-EN-P - February 2001

Chapter 5

Peer-to-Peer Messaging

Publication 1761-UM006A-EN-P - February 2001

5-2 Peer-to-Peer Messaging

The table below illustrates the relationship between messages and their corresponding configuration addresses.

Table 5.1 Message Routing

If the received data matches the current configuration, the ENI closes any open communications with the destination device.

If the ENI receives a PCCC read message to any of its configuration addresses (nodes 100 to 149), the ENI responds with the current configuration of that node/address.

Using the configuration shown in Table 5-2; if the controller initiates a read or write message to node 0, the ENI forwards the request to the TCP/IP address at Node 100 (111.222.233.200).

Publication 1761-UM006A-EN-P - February 2001

Table 5.2 Peer-to-Peer Message Routing

(1) See IMPORTANT note below about assigning Nodes to various devices.

Node addresses 0 through 44 are to be used for all other Ethernet devices, such as other 1769-L20 controllers connected to ENI modules and SLC 5/05 controllers.

To configure the route address (nodes 100 to 149), write a 485CIF message with 4 integer data words. An example is shown in the next section of this chapter.

Publication 1761-UM006A-EN-P - February 2001

5-4 Peer-to-Peer Messaging

Publication 1761-UM006A-EN-P - February 2001

Open the message instruction and enter the appropriate variables. The variables are described in Table 5.4.

Table 5.4 Message Instruction Variables for Sending a Message to a Destination

Controller

Publication 1761-UM006A-EN-P - February 2001

5-6 Peer-to-Peer Messaging

Publication 1761-UM006A-EN-P - February 2001

Chapter 6

E-Mail Messages (Node 50 to 99)

Publication 1761-UM006A-EN-P - February 2001

6-2 E-Mail Messages (Node 50 to 99)

Publication 1761-UM006A-EN-P - February 2001

Destination Addresses

The ENI stores e-mail addresses; it does not store the e-mail messages. To store a destination address, write a message to a specific node number (nodes 150 to 199). The message data must be a string element that contains a valid e-mail ASCII text string address, as illustrated in ST15:0 through ST15:5 in the example below.

Message Text

To send the actual e-mail message, the controller generates a write message, with a string element as the data (see ST15:7 to ST15:9 in the example above) to a node number (50 to 99) that correlates to the e-mail address (150 to 199).

The following table shows the relationship between the e-mail message and the e-mail address. The maximum size of the message is 1 string element of 84 bytes.

Publication 1761-UM006A-EN-P - February 2001

6-4 E-Mail Messages (Node 50 to 99)

Message Fields (to, from, subject)

The ENI includes the ???to???, ???from???, and ???subject??? fields in the body of the message.

The default ???from??? text is ENI0.0.0.0@eni1761.org. This can be changed in the ENI configuration, Node 249. See page 6-2 or Chapter 4.

The standard format of the ???subject??? line is:

Subject: 1761ENI.MSG(plus the first 32 characters of text)

For example, if the message text was ???The quick brown fox jumped over the lazy dog???s back???, the ???subject??? line would read:

Subject 1761ENI.MSG(The quick brown fox jumped over )

Publication 1761-UM006A-EN-P - February 2001

1. Start by configuring a MSG instruction.

Publication 1761-UM006A-EN-P - February 2001

6-6 E-Mail Messages (Node 50 to 99)

2.Open the message instruction and enter the appropriate variables. The variables are described in Table 6.1.

Table 6.1 Message Instruction Variables for Sending an E-Mail Message

Publication 1761-UM006A-EN-P - February 2001

Chapter 7

Connecting 1769-L20 CompactLogix Controllers on Ethernet

The chapter contains an example of using the ENI on an Ethernet network. It is arranged as follows:

???System Diagram

???Purpose

???Scope

???General Ethernet Information

???Configuring 1761-NET-ENI #1

???Configuring 1761-NET-ENI #2

???Configure RSLINX and Download The Program To The 1769-L20

???Create MSG Programs for the SLC 5/05 and the 5550 Controllers

???Configuring an Ethernet Driver in RSLINX

Publication 1761-UM006A-EN-P - February 2001

7-2 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Publication 1761-UM006A-EN-P - February 2001

Publication 1761-UM006A-EN-P - February 2001

7-4 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Figure 7.2 Throttling Message Instructions

Publication 1761-UM006A-EN-P - February 2001

For this example, we will be using 38400 baud on all serial connections. We will also assign IP addresses to all Ethernet products rather than using BOOTP.

Two tabs in the ENI software tool must be modified for the purposes of this example, the ???ENI IP Addr??? tab and the ???Message Routing??? tab. The IP address for the ENI connected to the 1769-L20 controller (ENI #2) is the only address we need to add to the ENI #1 Message Routing table. The other two Ethernet devices are accessed by the computer via the computer???s Ethernet card. Make the two ENI #1 tabs look like the following:

Figure 7.4 ENI #1 Configuration - ENI IP Addr Screen

Figure 7.5 ENI #1 Configuration - Message Routing Screen

Before we download our configuration to ENI #1, we must configure the ???Utility Settings??? tab in the ENI configuration tool. Make this tab look like the following.

Figure 7.6 ENI #1 Configuration - Utility Settings Screen

Publication 1761-UM006A-EN-P - February 2001

7-6 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Table 7.2 Message Routing

At this point we could merely configure ENI #2 as we did ENI #1. Or, we could use the method outlined in Chapter 5 to configure ENI #2. This method sends configuration Messages from the L20 controller via the DF1 link. If for any reason this ENI would need to be replaced, it could then be easily and quickly configured via messages from the L20 controller. A ladder program to accomplish this is as follows:

Publication 1761-UM006A-EN-P - February 2001

Figure 7.7 ENI #2 Configuration - RSLogix 5000 Ladder Program

The above ladder rungs, 2 through 7 and the rungs, 0 and 1 shown earlier in this application example, make up the ladder program for the L20 controller. Details of each MSG Instruction will follow.

In the above program, Rung 2 initiates the string of configuration messages with input instruction ???Reconfig_ENI???. This could be an alias to an input connected to a pushbutton for example, for quick configuration of the ENI module.

Publication 1761-UM006A-EN-P - February 2001

7-8 Connecting 1769-L20 CompactLogix Controllers on Ethernet

The 5 rungs used to configure ENI #2 are defined as follows:

Table 7.3 ENI #2 Configuration - Rung Descriptions

Rung Function

Rung 2 This rung initiates the process and configures the ENI module???s Serial port for 38400 Baud.

Rung 3 This rung is initiated by the Done bit of the previous MSG and it disables

BOOTP.

Rung 4 This rung configures the ENI with its own IP address.

Rung 5 This rung adds the IP address of the SLC 5/05 controller to the ENI module???s Message Routing table at DF1 node 1. This means that any message sent by the -L20 controller with a DF1 destination address of 1, will be sent to the SLC 5/05 controller on Ethernet.

Rung 6 This rung adds the IP address of the 1756-ENET module to the ENI module???s Message Routing table at DF1 node 45. This means that any message sent by the -L20 controller with a DF1 destination address of 45, will be sent to the 5550 controller in slot 0, via the 1756-ENET module on Ethernet.

Rung 7 This rung instructs the ENI module to save the configuration data sent to it in non-volatile memory.

The following table contains the information needed to send messages to the ENI to configure it for this example. For a complete list of ENI configurable features, please refer to Chapters 4 and 5.

Table 7.4 ENI #2 Configuration - Message Instructions Parameters

Publication 1761-UM006A-EN-P - February 2001

For this example, as mentioned earlier, we will assign the following IP addresses to the devices on Ethernet:

Table 7.5 Example IP Addresses for Ethernet Devices

The Message Instructions for the L20 controller, Rungs 2 through 7, used to configure the ENI module, must be ???PLC2 Unprotected Write??? Message Type. The ???Destination Element??? can be any valid PLC2 command value. ???010??? is used in this example because it is the first available valid value. This parameter is not used by the ENI, but must be a valid value for RSLOGIX5000 to accept it.

An example of the MSG Configuration tab and the Communication tab for the MSG Instruction used to configure the IP address for the ENI (Rung 4) are as follows:

Publication 1761-UM006A-EN-P - February 2001

7-10 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Figure 7.8 ENI #2 Configuration - Message ConfigurationTab

Figure 7.9 ENI #2 Configuration - Message CommunicationTab

Note that the MSG length is 8 bytes or 4 integer words. These 4 words contain the IP address for ENI #2 and are stored in tag ENI_IP_VALUE, which is a tag address containing 4 integer words. This is shown in

Publication 1761-UM006A-EN-P - February 2001

the L20 controller???s tag database shown below. On the MSG Instruction???s Communication tab above, the path is ???2,250???, where the 2 represents the L20 controllers serial port and the 250 tells the ENI module that the 4 words of data contain its IP address.

Figure 7.10 L20 Controller???s Tags

Per Table 7.4, The MSGs in Rungs 2, 3 and 7 are 2 bytes or 1 integer word in length. Their Paths are ???2,253???, ???2,252??? and ???2,248??? respectively; where 253 represents Baud Rate, 252 represents BOOTP Enable/Disable, and 248 represents the Save function.

The single integer data value for these messages is shown in Table 7.4. ???0??? is the value for the Save MSG data tag (ENI_SAVE_TO_FLASH_VALUE), which instructs the ENI to save its configuration to non-volatile memory. ???6??? is the value for the Baud Rate MSG data tag (ENI_BAUD_VALUE) which instructs the ENI to begin communicating on its RS-232 port at 38400 Baud. ???1??? is the value to disable BOOTP (BootP_disable_value).

Per Table 7.4, The MSGs in Rungs 5 and 6 assign IP addresses to node numbers in the ENI module???s Message Routing Table. These two MSG Instructions are the same as the MSG Instruction in Rung 3, except the paths are 2,101 and 2,145 and the data tags have different names; this time containing the IP addresses of the SLC 5/05 and 1756-ENET module.

Publication 1761-UM006A-EN-P - February 2001

7-12 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Enter your 1769-L20 ladder program per Rungs 0 through 7 as shown and described above. Be sure to enter your IP addresses for ENI #2, the SLC 5/05, and the 1756-ENET into the proper tags in the controller???s tag database. Before saving your program, enter the Controller Properties window by clicking on the Edit pull-down menu and select Controller Properties. Click on the System Protocol tab and change Error Detection from BCC to CRC and the Baud Rate from 19200 to 38400. Click APPLY, then OK. The ENI modules use CRC Error Detection.

If you do not change this parameter in your -L20 controller, it will not be able to communicate with the ENI. The Baud Rate of 38400 is being used to increase the upload/download speed.

Finally, since Logix controllers do not use the structured data table addressing scheme used by PLC and SLC controllers, we must map file numbers used in the commands sent to any Logix controller to tag names within them. For example, a MSG sent by an SLC 5/05 controller to the L20 controller uses a PLC-5 Typed Write command. The target data table address used is N12:0. This file 12 must be mapped to a valid tag name in the L20. Since the MSG is 20 integer words in length, a tag in the L20 controller called ???Data_From_505??? was created as a 20 integer word tag.

While offline in the L20 controller project, click on the Logic pull-down menu and select ???Map PLC/SLC Messages???. The following screen appears:

Figure 7.11 File Mapping in RSLogix 5000

Publication 1761-UM006A-EN-P - February 2001

Publication 1761-UM006A-EN-P - February 2001

7-14 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Figure 7.13 Modify DF1 Parameters Using RSLInx

It is very important that the ???Station Number??? match the ???Destn??? number in ENI #1, assigned to the IP address for ENI #2. In this example, we arbitrarily used Destn address 2 to represent IP address 131.200.50.94, which is the IP address of ENI #2.

DO NOT click on the ???Auto Configure??? button on this screen.

When you have properly modified the parameters on this screen, click OK. Then close the Configure Drivers screen.

Open the WHO Active screen by clicking on the Communications pull-down menu and select Who Active. If your system is properly connected, you should be able to click on the + sign left of the AB_DF1-1 driver you created and the CompactLogix controller should appear beneath the driver. Minimize, but do not close RSLINX.

Start RSLOGIX5000. Open the 1769-L20 program created earlier. Click on the Communications pull-down menu and select Who Active. From the Who Active screen. Click on the + sign left of ???AB_DF1-1, DF1???. The CompactLogix controller should appear. Single-click on it to highlight it, then click Download. Your program should download to the controller. You should be online with the controller when the download is complete. The software will soon time out, placing your computer in the offline mode. At this point, if you are still online, you may click on the Communications pull down menu and select offline. Online monitoring of the -L20 controller via two ENI modules is not supported at this time.

Publication 1761-UM006A-EN-P - February 2001

Publication 1761-UM006A-EN-P - February 2001

7-16 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Figure 7.15 SLC 5/05 Rung 0 MSG ???General??? Tab

Figure 7.16 SLC 5/05 Rung 0 MSG ???Multihop??? Tab

Publication 1761-UM006A-EN-P - February 2001

Figure 7.17 SLC 5/05 Rung 1 MSG ???General??? Tab

Figure 7.18 SLC 5/05 Rung 1 MSG ???Multihop??? Tab

Publication 1761-UM006A-EN-P - February 2001

7-18 Connecting 1769-L20 CompactLogix Controllers on Ethernet

The following is the MSG ladder program for the 5550 controller, developed with RSLOGIX5000. Following the ladder program are four additional screens showing the two tabs for each MSG Instruction. As part of your program, you must configure your 1756-ENET module with the proper IP address.

Figure 7.19 ControlLogix 5550 Controller Ladder Program

Publication 1761-UM006A-EN-P - February 2001

Figure 7.20 ControlLogix 5550 Rung 0 Message Configuration Tab

Figure 7.21 ControlLogix 5550 Rung 0 Message Communication Tab

Publication 1761-UM006A-EN-P - February 2001

7-20 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Figure 7.22 ControlLogix 5550 Rung 1 Message Configuration Tab

Figure 7.23 ControlLogix 5550 Rung 1 Message Communication Tab

The 1761-NET-ENI modules do not support CIP commands. Therefore, all commands between controllers used in this application example are PLC_5 Typed Write commands. These commands require a PLC-5 type address to send the data to the receiving controller. Such

Publication 1761-UM006A-EN-P - February 2001

Publication 1761-UM006A-EN-P - February 2001

7-22 Connecting 1769-L20 CompactLogix Controllers on Ethernet

Figure 7.25 Configure Ethernet Driver Using RSLinx

From the RSLOGIX500 programming software, you should now be able to download your SLC 5/05 program. Then, from the RSLOGIX5000 software you should now be able to download your 5550 controller program.

Once all programs are downloaded to their respective controllers, place each controller into the RUN mode and a MSG from each controller will be sent to each of the other controllers. Each controller will only send one MSG at any given time. Go online with the SLC 5/05 and 5550 controllers to verify the successful completion of their Messages.

Publication 1761-UM006A-EN-P - February 2001

Chapter 8

Troubleshooting

This chapter covers the following Troubleshooting topics:

???Network Troubleshooting

???LED Sequence at Power-Up

???Troubleshooting Using the LED Indicators

???Error Codes Generated by the ENI

???Message Instruction Error Codes

LED Sequence at Power-Up The following LED test is performed at power-up.

Publication 1761-UM006A-EN-P - February 2001

8-2 Troubleshooting

Publication 1761-UM006A-EN-P - February 2001

Troubleshooting 8-3

Publication 1761-UM006A-EN-P - February 2001

8-4 Troubleshooting

Publication 1761-UM006A-EN-P - February 2001

Troubleshooting 8-5

Publication 1761-UM006A-EN-P - February 2001

8-6 Troubleshooting

Publication 1761-UM006A-EN-P - February 2001

Appendix A

Specifications

Physical Specifications

Publication 1761-UM006A-EN-P - February 2001

A-2 Specifications

Publication 1761-UM006A-EN-P - February 2001

Appendix B

BOOTP Configuration Method (default)

BOOTP (Bootstrap protocol) is a low-level protocol that provides configuration information to other nodes on a TCP/IP network with DOS, Microsoft Windows, Windows NT, Windows 9x, VMS, and HP-UNIX platforms. BOOTP configuration files let you automatically assign IP addresses to the ENI. You can also set Subnet Masks and Gateway addresses using BOOTP.

To use BOOTP, a BOOTP Server must exist on the local Ethernet Subnet. The server is a computer that has BOOTP Server software installed and running which reads a text file containing network information for individual nodes on the network.

When the ENI receives a configuration message via BOOTP, it uses the data within the message to configure its TCP/IP parameters.

Table 2.1 TCP/IP Parameters

(1)Depending upon whether your BOOTP server allows these optional fields to be included, you might not be able to configure these parameters using the BOOTPTAB file. If that is the case, configure them using the soft configuration method. See page 4-1 for more information. If you do not need to define a Subnet Mask or Gateway, simply ignore these parameters.

Publication 1761-UM006A-EN-P - February 2001

B-2 BOOTP Configuration Method (default)

Install the BOOTP Server

To install the DOS BOOTP server:

1.Unzip the software to a known directory.

2.Change to that directory.

3.Type install, and press [Enter].

4.The software is installed in C:\ABIC\BIN. If you are using DOS, put this directory in the path statement of your AUTOEXEC.BAT file.

Publication 1761-UM006A-EN-P - February 2001

Edit the BOOTP Configuration File

The boot-server configuration file, BOOTPTAB, is located in the

C:\ABIC\BIN directory. BOOTPTAB is an ASCII file that looks like:

#Legend:gw -- gateways #ha -- hardware address #ht -- hardware type(1) #ip -- host IP address #sm -- subnet mask

#vm -- BOOTP vendor extensions format(2) #tc -- template host

#Default string for each type of Ethernet client defaults5E: ht=1:vm=rfc1048

#Entries for SLC 5/05 processors:

sigma1: tc=defaults5E:ip=12.34.56.1:ha=0000BC1D1234

sigma2: tc=defaults5E:ip=12.34.56.2:ha=0000BC1D5678

sigma3: tc=defaults5E:ip=12.34.56.3:ha=0000BC1D9012

This file contains the information needed to boot the ENI.

You must edit the BOOTPTAB file to include the name, IP address, and hardware address for each ENI you want the server to boot. To edit this file:

1.Open the BOOTPTAB file using a text editor such as Notepad or Wordpad.

The file contains text that look like this:

#Default string for each type of Ethernet client

defaults5E: ht=1:vm=rfc1048

These are the default parameters for the ENI and must always precede the client lines in the BOOTPTAB file.

The file also contains a line that looks like this:

#Entries for SLC 5/05 processors: sigma1:tc=defaults5E:ip=12.34.56.1:ha=0000BC1D 1234

The ???#??? character defines the line as information, not configuration data.

(1)1 = 10 MB Ethernet

(2)Use rfc 1048.

Publication 1761-UM006A-EN-P - February 2001

B-4 BOOTP Configuration Method (default)

Publication 1761-UM006A-EN-P - February 2001

BOOTP Configuration Method (default) B-5

Based on this configuration, the BOOTPTAB file looks like:

#Legend:gw -- gateways #ha -- hardware address #ht -- hardware type(1) #ip -- host IP address #sm -- subnet mask

#vm -- BOOTP vendor extensions format(2) #tc -- template host

#Default string for each type of Ethernet client defaults5E: ht=1:vm=rfc1048

#Entries for SLC 5/05 processors:

sigma1: tc=defaults5E:ip=12.34.56.1:ha=0000BC1D1234

sigma2: tc=defaults5E:ip=12.34.56.2:ha=0000BC1D5678

sigma3: tc=defaults5E:ip=12.34.56.3:ha=0000BC1D9012

Run the Boot Server Utility You can run either the DOS-based utility or the Windows-based BOOTP utility, but not both.

If you have BOOTP enabled and the message BOOTP response not received appears, check the cabling connections and the BOOTP server system.

Both utilities are located in the C:\ABIC\BIN directory and use the information contained in the BOOTPTAB file.

Be sure to place the BOOTPTAB file in the directory from which you are running the BOOTP utility. If this file is not found in that directory, the utility will try to find the file in the directory specified by the environment variable ABIC_CONFIG.

(1)1 = 10 MB Ethernet

(2)Use rfc 1048.

Publication 1761-UM006A-EN-P - February 2001

B-6 BOOTP Configuration Method (default)

Running the DOS-Based Utility

To run the boot-server utility, DTLBOOTD.EXE, follow these steps:

1.At the DOS prompt, type:

DTLBOOTD [-D] [-T <timeout>] [-B <numboots>] [-F <numfiles>] [configfile] [logfile]

Once you invoke the utility, it runs until the specified exit parameter is satisfied. Exit any time by pressing [Esc].

2.Apply power to all ENIs. At power-up, each ENI broadcasts a BOOTP request (if BOOTP was enabled). The Ethernet boot server compares the hardware address with those listed in the BOOTPTAB file and responds by sending the corresponding IP

address and other configuration data to the client via a BOOTP reply.

Running the Windows-Based Utility

To run the boot-server utility, DTLBOOTW.EXE, follow these steps:

1.Start Microsoft Windows??, if it is not already running.

2.Start the utility. It will run until you terminate it by closing the DTLBOOTW.EXE window and exiting from Windows.

3.Apply power to all ENIs. At power-up, each ENI broadcasts a BOOTP request. The Ethernet boot server compares the hardware address with those listed in the BOOTPTAB file and responds by sending the corresponding IP address and other configuration data to the client via a BOOTP reply.

Publication 1761-UM006A-EN-P - February 2001

Glossary

ASA (Advanced System Architecture)

Autobaud

A feature that allows a communications port to automatically synchronize to the device or network that it is attached to. This feature typically minimizes the amount of configuration required, and also makes is easier to replace devices.

Auto BCC/CRC

Sends a test message during autobaud to detect which Error Detecting setting to use, BCC or CRC. This will not occur for fixed baud rate settings. The ENI uses CRC for fixed baud rates.

Baud Rate

The speed of communication between devices on a network. All devices must communicate at the same baud rate. For example, the DH-485 network devices default to 19,200 baud.

CIP (Control and Information Protocol)

DNI (DeviceNet Network Interface)

Allen-Bradley catalog number 1761-NET-DNI. The DNI allows you to connect DF1 devices to DeviceNet networks.

DF1 Full-Duplex

DF1 is a standard (open) point-to-point communication protocol. Virtually all Allen-Bradley controllers (PLC-3, PLC-5, SLC, MicroLogix) that have an RS-232 communications port support DF1.

DF1 Protocol

A peer-to-peer link-layer protocol that combines features of ANSI X3.28-1976 specification subcategories D1 (data transparency) and F1 (two-way simultaneous transmission with embedded responses).

ENI (Ethernet Network Interface)

Allen-Bradley catalog number 1761-NET-ENI. The ENI allows you to connect DF1 devices to Ethernet networks.

Ethernet Network

A local area network with a baseband communication rate of 10M bits per second.

Publication 1761-UM006A-EN-P - February 2001

Glossary 2

Full-duplex

A high-performance protocol that allows simultaneous two-way data transmission. For point-to-point applications only.

IP (Internet Protocol)

IP specifies the format of packets and the addressing scheme. Most networks combine IP with a higher-level protocol called Transport Control Protocol (TCP), which establishes a virtual connection between a destination and a source.

IP by itself is something like the postal system. It allows you to address a package and drop it in the system, but there's no direct link between you and the recipient. TCP/IP, on the other hand, establishes a connection between two hosts so that they can send messages back and forth for a period of time.

IP Address

A 32-bit address assigned to hosts that want to participate in a TCP/IP internet. IP addresses are the abstraction of physical hardware addresses, with a network and host partition which makes routing efficient.

NetLinx Services

The NetLinx services occur over the well-known port 0xAF12 and define a connection protocol that exists after a TCP/IP connection is established. It also defines a set of services and packet formats to support the protocol. Also implied by this protocol is that the end devices have implemented some portion of the ASA CIP addressing architecture.

Network

A series of stations (nodes) connected by some type of communication medium. A network may be made up of a single link or multiple links.

Node

Also called a station. An address or software location on the network.

MTA (Mail Transfer Agent)

The software function responsible for delivering outgoing mail to its final destination.

Publication 1761-UM006A-EN-P - February 2001

Glossary 3

PCCC (Programmable Controller Communications Commands)

RS-232

An EIA standard that specifies electrical, mechanical, and functional characteristics for serial binary communication circuits.

Security Mask

The Security Mask, when configured, allows you to restrict incoming TCP/IP and/or UDP messages to have source IP addresses that are within some prescribed range. For example, if you wanted to restrict all message sources to be from within a company???s allocated IP address range, a Security Mask could be configured that would block any IP address outside that range.

SMTP (Simple Mail Transfer Protocol)

This protocol defines the interface and commands with the Mail Transfer Agent and defines how the ENI will deliver the outgoing mail.

Single-Hop/ Multi-Hop

Term that refers to how many ???different??? networks a message must traverse to reach its destination. For the ENI, a single-hop message is one whose source and destination nodes are both TCP/IP end points.

TCP (Transmission Control Protocol)

TCP is one of the main protocols in TCP/IP networks. Whereas the IP protocol deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and also guarantees that packets will be delivered in the same order in which they were sent.

TCP/IP (Transmission Control Protocol/Internet Protocol)

The suite of communications protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP. TCP/IP is built into the UNIX operating system and is used by the Internet, making it the de facto standard for transmitting data over networks. Even network operating systems that have their own protocols, such as Netware, also support TCP/IP.

UCMM (Unconnected Message Manager)

The UCMM is an object defined in the CIP protocol. This object is responsible for handling connection requests and unconnected message traffic.

Publication 1761-UM006A-EN-P - February 2001

Glossary 4

UTP (Unshielded Twisted Pair)

The type of cable used in 10BaseT systems.

Publication 1761-UM006A-EN-P - February 2001

Index

Publication 1761-UM006A-EN-P - February 2001

2 Index

Publication 1761-UM006A-EN-P - February 2001

Index 3

Publication 1761-UM006A-EN-P - February 2001

4 Index

Publication 1761-UM006A-EN-P - February 2001

Publication 1761-UM006A-EN-P - February 2001

?? 2001 Rockwell International Corporation. Printed in the U.S.A.