Release Notes

ControlLogix Redundancy System Revision 13

Cat. No. 1756-CNB/D, -CNBR/D, -ENBT, -EWEB, -L55, -L55M12, -L55M13, -L55M14, -L55M16, -L55M22, -L55M23, -L55M24, -L61, -L62, -L63, 1757-SRM/A, -SRM/B
IMPORTANT If you have a 1756-L55 controller, you must install a memory board. For more information, see the ControlLogix Controller and Memory Board Installation Instructions, publication 1756-IN101.

When to Use These Release Notes

IMPORTANT

These release notes correspond to the following modules when used in a ControlLogix redundancy system:

For a module in a redundant controller chassis, make sure the catalog revision of the module is greater than or equal to the catalog revision shown in the following table. Otherwise, the secondary chassis will not synchronize with the primary chassis.
ControlLogix
CAT. NO./SERIES

Ethernet/IP 10/100 Mb/s COMMUNICATIONS BRIDGE

CAT. REV.

To determine the catalog revision of a module, look at the label on the side of the module or box.

1756-ENBT/A

E01

catalog revision

Module: ControlLogix5555 controller ControlLogix5561 controller ControlLogix5562 controller ControlLogix5563 controller ControlNet bridge module 1756 10/100 Mbps EtherNet/IP Bridge, Twisted Pair Media

Catalog number: 1756-L55Mxx 1756-L61 1756-L62 1756-L63 1756-CNB/D or -CNBR/D 1756-ENBT

Catalog revision (or greater) any any any any any E01 (e.g., E01, E02, , F01, etc.) any any

Firmware revision: 13.53 13.53 13.53 13.53 5.44 3.3 2.2 3.37

1756 10/100 Mbps EtherNet/IP 1756-EWEB Bridge w/ Enhanced Web Services redundancy module
1

1757-SRM/A or -SRM/B

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

Compatible Revisions
Update this software: RSLinx

To use this revision, update your system as follows:

Notes: This revision of RSLinx software automatically installs 1757-SRM System Redundancy Module Configuration tool revision 2.5. See Restrictions on page 8. Required only for certain HMI software. See Restrictions on page 8. If you install: RSLinx software revision 2.42 Then: Before you install 1757-SRM System Redundancy Module Configuration tool revision 2.6, see Restrictions on page 8. To install 1757-SRM System Redundancy Module Configuration tool revision 2.6, see Knowledgebase document G92234770. To access Rockwell Automations Knowledgebase, go to http://support.rockwellautomation.com RSLinx software RSLinx software revision 2.43 automatically installs revision 2.43 1757-SRM System Redundancy Module Configuration tool (available in the future) revision 2.6.

To this revision or later: 2.42

RSLinx Enterprise 1757-SRM System Redundancy Module Configuration Tool

2.0 2.6

To see which revision of the 1757-SRM System Redundancy Module Configuration tool is currently installed: 1. In RSLinx software, browse to a SRM module. 2. Right-click the SRM module and choose Module Configuration.

3. Right-click the title bar of the configuration tool and choose About RSLogix 5000 RSNetWorx for DeviceNet 13.0 4.21 RSNetWorx for ControlNet 4.21

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

What Is In These Release Notes

For information about: order in which to update your system new features restrictions that no longer apply restrictions to your redundancy system

These release notes provide the following information about the components of the redundancy system:

See this section: How to Update Your Firmware Enhancements Corrected Anomalies Restrictions

On this page: 3 4 7 8

For more information on the ControlLogix redundancy system, see the ControlLogix Redundancy System User Manual, publication 1756-UM523.

How to Update Your Firmware

ATTENTION

Update your firmware in the following order:

1. Update the SRM module firmware. It takes several minutes to update a 1757-SRM/A or -SRM/B module. Do not interrupt the process. Make sure you wait until the SRM module displays REV 3.37 on its four-character display. If you interrupt the process, the module may become inoperative. When you update the module, it performs the following sequence: Two downloads (ERAS/PROG on display twice) Reset to rev. 2.20 (FLSH UPDT REQD) Two more downloads (ERAS/PROG on display twice) Second reset before the update is complete If the OK LED on the SRM module is red flashing and the 4-character display is blank, then the firmware update has failed. Do not cycle the power to the module. Leave the power on and update the firmware of the module again. 2. Update the CNB, ENBT, and EWEB module firmware. 3. Update the controller firmware.

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

Enhancements

This revision contains the following enhancements that are specific to a redundant system. For the list of enhancements that apply to both redundant and non-redundant systems, see the following release notes: ControlLogix Controller Revision 12 Release Notes, publication 1756-RN601 ControlLogix Controller Revision 13 Release Notes, publication 1756-RN603

ControlLogix5555, 5561, 5562, 5563 Rev 13.53

Enhancement: Sequential Function Charts More Stable Scan Times Description: This revision lets you use the sequential function chart (SFC) programming language to program your redundancy system. This revision reduces the jumps in program scan time that may have occurred in previous revisions. The jumps were caused by programs with fast scan times or large crossloads that flooded the 1757-SRM module with data, which increased the crossload time. This revision lets you place a ControlLogix5561, 5562, or 5563 controller in a redundant chassis: Use only 1 ControlLogix5561, 5562, or 5563 controller in a redundant chassis Use an identical controller in the same slot in the partner chassis. Do not mix ControlLogix5561, 5562, or 5563 controllers in the same chassis with ControlLogix5555 controllers. The program scan time improvement when using one of these controllers in a redundant system is less than in a non-redundant system. Even though the ControlLogix5561, 5562, and 5563 controllers execute logic faster, they must still crossload data. Given the same project and redundant system, a ControlLogix5561, 5562, or 5563 controller is up to 30% faster than a ControlLogix5555 controller. Up to 2 ControlLogix5555 Controllers in the Same Redundant Chassis 1756-EWEB module in a local redundant chassis This revision lets you place up to 2 ControlLogix5555 controllers in a redundant chassis: Use identical controllers in the same slots in the partner chassis. Do not mix ControlLogix5555 controllers in the same chassis with ControlLogix5561, 5562, or 5563 controllers Place 1756-EWEB modules in a redundant chassis pair: Important: If you use RSLinx Enterprise software revision 2.0, we recommend that you place your 1756-ENBT or 1756-EWEB modules in a non-redundant chassis and bridge the communication over a ControlNet network to the redundant chassis. See Restrictions on page 8. Place an EWEB module in the same slot in each redundant chassis. (The modules in each redundant chassis must match each other slot-by-slot.) Place up to 2 EtherNet/IP modules in each redundant chassis. Use any mix of ENBT or EWEB modules. The remaining communication modules must be either 1756-CNB or -CNBR modules, for a total of 5 communication modules per redundant chassis. In a redundant system, use an EtherNet/IP network only for HMI/workstation communication and messaging. Do not use an EtherNet/IP network for: communication with I/O modules communication between devices via produced/consumed tags

One ControlLogix5561, 5562, 5563 Controller in a Redundant Chassis

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

Enhancement: Duplicate IP Address Detection

Description: 1756-ENBT and 1756-EWEB modules now detect if their IP address conflicts with another device on the EtherNet/IP network. How the modules respond to the conflict depends on the following conditions: If: Both devices have duplicate IP address detection. And: One of the devices is in a redundant chassis. The: The device in the redundant chassis uses the IP address. The other device stops communicating on the network. Both devices are outside of a redundant chassis. The second device to access the network uses the IP address. The other device stops communicating on the network. One of the devices does not have duplicate IP address detection. The other device is in a redundant chassis. Both devices are outside of a redundant chassis. Both devices try to communicate at that IP address. The device without duplicate IP address detection uses the IP address. The other device stops communicating on the network. In a redundant chassis, an ENBT or EWEB module uses duplicate IP address detection to swap its IP address with its partner during a switchover. See Automatic IP Address Swapping on page 5.

Automatic IP Address Swapping During a switchover, 1756-ENBT and 1756-EWEB modules now swap their IP addresses with their partner modules in the other redundant chassis. This lets you use the same IP address to communicate with a primary module regardless of which chassis is primary. Typically, you no longer need to use ControlLogix Redundancy Alias Topic Switcher software to manage the IP addresses. If your application still requires alias topics to manage IP addresses, see ControlLogix Redundancy System User Manual, publication 1756-UM523. During a switchover, communication over an EtherNet/IP network with other controllers or HMI may freeze for up to a minute, depending on network topology. If you need bumpless communication with controllers/HMIs, use a separate ControlNet network that is dedicated to communication with those devices. Important: Make sure to connect the 1757-SRCx cable to both 1757-SRM modules of the redundant chassis pair. Otherwise, the ENBT and EWB modules will show a duplicate IP address. To let the modules swap IP addresses during a switchover: 1. Allocate 2 consecutive IP addresses for each set of ENBT or EWEB modules (one in each chassis). For example, 10.10.10.10 and 10.10.10.11. 2. Give the same IP address, gateway address, and subnet mask to both modules in the redundant pair. (E.g., Set both IP address = 10.10.10.10.) The module in the primary chassis uses the IP address to which it is configured (e.g., 10.10.10.10). The module in the secondary chassis uses the IP address of the primary +1 in the last address segment (e.g., 10.10.10.11).

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

Enhancement: Set the Clock of a 1757-SRM Module to the Workstation Clock

Description: Requires 1757-SRM System Redundancy Module configuration tool, revision 2.6 or later. See Restrictions on page 8.

To send the currently running workstation (PC) time to the SRM module, click this button. Event Log Provides More Information Requires 1757-SRM System Redundancy Module configuration tool, revision 2.6 or later. See Restrictions on page 8. Export file includes extended information in text format

See events in both SRM modules at the same time

See extended information in text format

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

Corrected Anomalies

This revision corrects the following anomalies:

ControlLogix5555, 5561, 5562, 5563 Rev 13.53

Anomaly: Online Memory Information Was Incorrect Description: While online, RSLogix 5000 software showed incorrect values for the memory usage of the controller.

Lgx00042913 Modules Incorrectly Indicated Primary A module in a primary chassis incorrectly indicated Primary with Disqualified Secondary under the with Disqualified Secondary After the following conditions: Secondary Module Was Removed 1. The secondary module was present but disqualified 2. While the secondary module was disqualified, you removed it from the chassis. Both the software and hardware showed the incorrect redundancy state of the module. Lgx00045469 Connections Prematurely Timed-Out A connection prematurely timed-out under the following combination of circumstances: RPI of the connection was approximately 15 to 25 ms. CPU usage of the CNB module was close to 98 - 100%. Lgx00045470 If the period of a periodic task expired during a switchover, the task might have delayed its execution 2 times the specified period. After this extended period, it returned to its specified period. Lgx00045661 After a switchover, a periodic task might have shown a maximum interval time that was approximately 1 second longer than the actual value. Lgx00046215 If the period of a periodic task expired during a switchover, the watchdog timer for the task might not have been active during the first execution after the switchover. On subsequent executions, the timer became active again. Lgx00046229

Switchover Extended Task Period

After a Switchover, the Maximum Interval Time for a Periodic Task Might Have Been Incorrect After a Switchover, Watchdog Timer May Have Been Temporarily Inactive

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

Restrictions
IMPORTANT

This revision contains the following restrictions:

In a redundant system, use an EtherNet/IP network only for HMI/workstation communication and messaging. Do not use an EtherNet/IP network for: communication with I/O modules communication between devices via produced/consumed tags

Restriction: 1757-SRM System Redundancy Module Configuration Tool Revision 2.5 Does Not Recognize Some Devices

Description: If you use revision 2.5 of the 1757-SRM System Redundancy Module Configuration Tool in a revision 13.x redundancy system, the event log lists any 1756-L6x controller or 1756-EWEB module as Unknown Device Code 5.. This does not affect the operation of the redundant system.

If you also connect your computer to ControlLogix redundancy systems revision 11.x or earlier, do Do Not Use 1757-SRM System Redundancy Module Configuration not install 1757-SRM System Redundancy Module Configuration Tool revision 2.6. Tool Revision 2.6 with ControlLogix Revision 2.6 is compatible only with revision 13.x or later ControlLogix redundancy Redundancy Systems Revision 11.x or systems. Using revision 2.6 of the tool with an earlier revision of ControlLogix redundancy earlier systems could cause the 1757-SRM module to fault. Keep in mind that the following enhancements are available only in revision 2.6 or later of the configuration tool: Set the Clock of a 1757-SRM Module to the Workstation Clock, listed on page 6 Event Log Provides More Information, listed on page 6 When RSLinx software revision 2.43 becomes available, it will contain revision 2.6 of the configuration tool. RSLinx Enterprise Software Revision 2.0 Is Not Recommended for Local Ethernet Modules If you use RSLinx Enterprise software revision 2.0, we recommend that you place your 1756-ENBT or 1756-EWEB modules in a non-redundant chassis and bridge the communication over a ControlNet network to the redundant chassis. Do not place the modules in the redundant chassis pair. When RSLinx Enterprise software revision 3.0 is available (fourth quarter 2004), this restriction no longer applies. That revision will let you put your 1756-ENBT or 1756-EWEB modules in the redundant chassis pair. Under the following combination of conditions (all must apply), duplicate IP addresses on your EtherNet/IP network will cause you to lose communication with a redundant chassis pair over that EtherNet/IP network: You have multiple pairs of redundant chassis on the same EtherNet/IP network. For example, pair 1 and pair 2. The IP addresses of one pair of redundant chassis is the same as another pair of redundant chassis. For example, pair 1 = 10.10.10.10 and pair 2 = 10.10.10.10. A redundant chassis pair with the conflict (both chassis that make up the pair) simultaneously powers up. For example, both chassis of pair 2 power up at the same time. When this occurs the newly powered up chassis use the IP address. The redundant chassis pair that was previously communicating at that IP address stops communicating on the network. For example, when pair 2 powers up at 10.10.10.10, pair 1 stops communicating on the network.

Simultaneous Power of Redundant Chassis Pair May Bump Another Redundant Chassis Pair Off the EtherNet/IP Network

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

Restriction: Recommended Minimum Scan Time

Description: The minimum attainable scan time for a ControlLogix redundancy project is approximately 20 milliseconds. At very low scan times, the processing of crossload data causes a greater performance burden; this burden effectively limits the minimum scan time. In a redundant controller, do not configure a task as an Event task.

Do Not Use Event Tasks in the Redundant Controllers

Do Not Inhibit Any Tasks in the Redundant Controllers

In a redundant controller, leave all your tasks uninhibited.

Publication 1756-RN608C-EN-E - September 2004

10

ControlLogix Redundancy System Revision 13

Restriction:

Description:

In a Tag of a User-Defined Data Type, If you write too much data to an array that is within a user-defined data type, some instructions an Instruction May Write Past the write beyond the array and into other members of the tag. End of an Array. Example 1: Instruction If the length is greater than the number Stops at the End of the Array of elements in the destination array

the instruction stops at the end of the array.

Example 2: Instruction Writes Beyond the Array

If the length is greater than the number of elements in the destination array

the instruction writes data beyond the end of the array into other members of the tag. Regardless of the length specified for the instruction, it stops writing if it reaches the end of the tag. The following instructions write beyond the array into other members of the tag: BSL BSR COP CPS DDT FBC FFL FFU FLL GSV LFL LFU SQL SRT SSV

This restriction also applies to all previous revisions. To prevent writing beyond the limits of the destination array, make sure the length operand of the instruction is less than or equal to the number of elements in the array. Lgx00033747

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

11

Restriction: Switchover Always Triggers an Event Task in a Remote, Non-Redundant Controller

Description: A switchover triggers an event task under the following combination of circumstances: The event task is in non-redundant controller. (An Event task is not permitted in a redundant controller.) A redundant controller triggers the event task via a produced tag. This occurs regardless of how you configure the produced tag.

Both configurations always trigger an event task during a switchover.

Lgx00045349 If You Finalize All Edits in a Program and the Edits Produce a Major Fault, both the Primary and Secondary Controller Experience the Fault. When you finalize all edits in a program, the controller automatically removes the original logic. If the changes cause a switchover due to a major fault, the new primary controller also faults. This occurs because there in no original logic to revert back to. (I.e., The new primary cannot untest the edits.) Finalize All Edits in Program

This occurs even if you configure the controller to untest edits on a switchover. Lgx00044659

Publication 1756-RN608C-EN-E - September 2004

12

ControlLogix Redundancy System Revision 13

Restriction: Store a Redundant Project to NonVolatile Memory

Description: Use the following procedure to store a project to the nonvolatile memory of a pair of redundant controllers. (Otherwise, the project may not correlate when you go online after the store operation.) 1. Place the primary controller in program mode (program or remote program). 2. In the Module Configuration properties for one of the 1757-SRM modules, set the Auto-Synchronization option = Conditional. 3. Disqualify the secondary chassis. 4. In the primary controller, store the project. Important: Do not go back online to the primary controller until you complete the rest of the steps in this procedure. For step-by-step procedures on how to store a project, see Logix5000 Controllers Common Procedures, publication 1756-PM001. 5. Go online to the secondary controller and store the project. 6. Synchronize the controllers. 7. In the Module Configuration properties for one of the 1757-SRM modules, set the Auto-Synchronization option = the desired option. Lgx00044659

Simultaneous Branch Delays the Execution of a Higher Priority Task In an SFC, each path of a simultaneous branch delays the execution of a higher priority task by 25 s.

Lgx00045471 Communication Module Occasionally Uses a Duplicate Address After a switchover or simultaneous power cycle (both chassis cycle power at the same time), a 1756-CNB, 1756-ENBT, or 1756-EWEB module may try to use a duplicate address. When this occurs, the module displays DUPL NODE or DUPLICATE IP ADDRESS. This condition prevents you from communicating with the module and leaves the secondary chassis disqualified (unsynchronized). Sometimes, an ENBT or EWEB module may show a duplicate IP address due to this condition but the chassis still synchronize. If this occurs cycle the power to the chassis with the module that has the duplicate address. Lgx00047086

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

13

Restriction: HMIs May Stop Communicating with the Controller via EtherNet/IP Network After Several Switchovers

Description: Occasionally, HMIs that connect to a redundant controller via a 1756-ENBT or 1756-EWEB module may stop communicating with the controller after several switchovers. To recover, either: If the secondary chassis is synchronized, switchover to that chassis. If the ENBT or EWEB module is in your RSLogix 5000 project, use the Properties window for the module to reset the module. Remove the ENBT or EWEB module from the primary chassis and reinsert it into the primary chassis. Lgx00050497

High CNB Module Usage May Prevent a Store to Nonvolatile Memory

You may not be able to store a project to the nonvolatile memory of a redundant controller under the following conditions: Your computer is connected to the controller via a CNB module. The CPU usage of the CNB module is greater than 75%. In some instances, RSLogix 5000 software may not let you perform additional online edits of a function block, SFC, or structured text routine. This may occur if you edit the routine while online and the system is switching over and synchronizing. If this occurs: 1. Close and then open RSLogix 5000 software. 2. Upload the RSLogix 5000 project from the primary controller.

Online Editing During a Switchover

Deleting a Task Online Motion Control

If you delete a task while online with the controller, the secondary chassis may disqualify and then synchronize. You cannot use the ControlLogix redundancy system in applications that require motion control. (I.e., You cannot use a 1756-HYD02, 1756-M02AE, 1756-M02AS, 1756-M03SE, 1756-M08SE, or 1756-M16SE module.) After you download a project that contains ASCII instructions (e.g., ABL, ACB) to a pair of redundant controllers, the secondary controller may disqualify and fail to synchronize. If this occurs, turn off both controllers (primary and secondary) and then turn the controllers back on. In rare instances, if a tap to a 1756-CNB module is disconnected or breaks, the primary controller may momentarily drop its connection to a digital I/O module in local or remote chassis. The connection automatically re-establishes. To minimize this, use redundant ControlNet media. Redundant ControlNet media prevents a loss of communication if a trunkline or tap is severed or disconnected.

ASCII Instructions May Prevent the Secondary Controller From Synchronizing Controller May Momentarily Drop Its Connection to a Digital I/O Module

Publication 1756-RN608C-EN-E - September 2004

14

ControlLogix Redundancy System Revision 13

Restriction: Communication Loss When Bridging Through a 1756-CNB/B or -CNBR/B Module

Description: The following combination of modules in a remote chassis could cause a temporary communication loss with the chassis: 1756-CNB/B or -CNBR/B module 1756-DHRIO module that is connected to a remote I/O network.
redundant chassis pair
L C 5 N 5 B M x S R M

1756-CNB/B or -CNBR/B module remote chassis

C N B / B D H R I O

other modules

remote I/O

On the first switchover after you download a project to the controller, you may temporarily lose communications with these devices.

The loss of communication occurs on the first switchover after you download the project to the redundant controller. You lose communication with the remote chassis and any devices to which you were bridging via the chassis, such as the remote I/O modules. During the communication loss, the I/O modules go to their configured state for a communication fault. The communication loss is temporary. Communications restore themselves. To prevent this situation, use 1756-CNB/D or -CNBR/D modules.

Publication 1756-RN608C-EN-E - September 2004

ControlLogix Redundancy System Revision 13

15

Restriction: If the Lowest Node Is a 1756-CNB/B or -CNBR/B Module, Removing a Tap or Breaking a Cable Could Stop All Communications over the Network

Description: If the lowest node on a ControlNet network is a 1756-CNB/B or -CNBR/B module, all communications over the network could stop if: A tap to the 1756-CNB/B or -CNBR/B module is disconnected or breaks and then is replaced while power is still applied to the 1756-CNB/B or -CNBR/B module If a tap to a 1756-CNB/B or -CNBR/B module becomes disconnected or broken, take these actions: 1. Turn off the power to the 1756-CNB/B or -CNBR/B module. 2. Replace the tap. If a communication failure occurs because of a disconnected or broken tap, cycle power to each primary controller on the network. To prevent this situation, use a 1756-CNB/D or -CNBR/D module as your lowest node on the network.

1756-L55M16 controllers Guidelines for the Size of Routines

You cannot download a project that has very large routines to a 1756-L55M16 controller. During the download, RSLogix 5000 software indicates that the controller is out of memory. (While online, you may be able to create a very large routine, but once offline you will be unable to download the project.) To avoid creating routines that are too large, take these precautions: Limit the number of rungs in a routine to less than 2500. (Use a series of smaller routines.) If you are entering a large number of rungs in a routine, do this offline. As you enter rungs, periodically download the project. If the project successfully downloads, then your routines are within limits.

1756-L55M16 controllers3.5M Byte Limit of Tags

You cannot download a project that has more than 3.5M bytes of tags to a 1756-L55M16 controller. During the download, RSLogix 5000 software indicates that the controller is out of memory. To stay within the 3.5M byte limit, use the Memory tab of the Controller Properties window.:

In general, the data and logic memory represents the 3.5M byte limit for tags. As you develop your project, periodically go to this tab and click the Estimate button. Keep your used memory within the green area. Once the used memory is in the yellow, the controller may not have enough memory for runtime communication. For a detailed description of how the controller organizes its memory, see Logix5000 Controllers Common Procedures, publication 1756-PM001.

Publication 1756-RN608C-EN-E - September 2004

Rockwell Automation Support

Rockwell Automation provides technical information on the web to assist you in using our products. At http://support.rockwellautomation.com, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools. For an additional level of technical phone support for installation, configuration and troubleshooting, we offer TechConnect Support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://support.rockwellautomation.com.

Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation, please review the information that's contained in this manual. You can also contact a special Customer Support number for initial help in getting your module up and running: United States Outside United States 1.440.646.3223 Monday Friday, 8am 5pm EST Please contact your local Rockwell Automation representative for any technical support issues.

New Product Satisfaction Return

Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned: United States Outside United States Contact your distributor. You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process. Please contact your local Rockwell Automation representative for return procedure.
ControlNet is a trademark of ControlNet International, Ltd. DeviceNet is a trademark of the Open DeviceNet Vendor Association. Back Cover

Publication 1756-RN608C-EN-E - September 2004 16

Supersedes Publication 1756-RN608B-EN-E - June 2004

PN 957928-22
Copyright 2004 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.