ProcessLinx OPC Server to Server Software 1757-PROCESSLINX User Manual
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.
Preface Introduction This document provides an overview of the ProcessLinx application. ProcessLinx allows two OPC servers to communicate. Normally a server talks to a client and visa versa. A server cannot talk to another server because the interfaces are incompatible. ProcessLinx is specilized software that allows two servers to communicate. Overview The OPC (OLE for Process Control) Interface within ProcessLinx acts as an OPC Client to a ProcessLogix OPC Server as well as to another OPC server.
P-2 • Tag Map configurations are stored in a serialized compact binary file. • Supports ability to easily import and export ProcessLinx Tag Map configurations to/from comma delimited (*.csv) ASCII files, which can be created and/or edited with Microsoft Excel, Microsoft Access or any text editor. • Error and informational messages displayed in the main window in runtime along with optional user-configurable specification maintaining this data in daily log files.
P-3 Rockwell Automation Technical Support Rockwell Automation offers support services worldwide, with over 75 sales/support offices, 512 authorized distributors, and 260 authorized systems integrators located throughout the United States alone, plus Rockwell Automation representatives in every major country in the world.
P-4 Conventions Terms and Type Representations The following table summarizes the terms and type representation conventions used in this Guide. Publication 1757-UM002B-EN-P - January 2003 Term/Type Representation Meaning Example click, click on, click [button name] Click left mouse button once. (Assumes cursor is positioned on object or selection.) Click Apply. double-click Click left mouse button twice in quick succession. (Assumes cursor is positioned on object or selection.
Table of Contents Preface Chapter1 Setup Procedures Chapter 2 Getting Started Chapter 3 ProcessLinx TagMap Configuration i Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rockwell Automation Technical Support . . . . . . . . . . . . . . . . . . . . . .
Table of Contents ii Chapter 4 ProcessLinx Runtime Operation Chapter 5 Import/Export Chapter 6 Error Diagnosis and Debugging Chapter 7 Using DCOM OPC Servers Publication 1757-UM002B-EN-P - January 2003 Monitoring Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading OPC Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Writing OPC Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1 Setup Procedures Installation This chapter contains an overview of the setup procedure and the steps you need to take to set up a configuration prior to using ProcessLinx. Configuring DCS Components IMPORTANT You are required to configure the DCS components before installing ProcessLinx. If the DCS components are not configured correctly, server communications will not succeed. All DCS Components must be configured first in the setup procedure.
1-2 Setup Procedures In order for ProcessLinx to connect to the ProcessLogix OPC Server over the network, the OPC Server Connect option must be installed on the client PC. Refer to the ProcessLogix Knowledge Builder: Navigate in Knowledge Builder to ⇒Server and Client Configuration Guide ⇒Using ProcessLogix Data in other Applications ⇒ ProcessLogix OPC Support. External OPC Server Consult the External OPC Server documentation for correct installation and setup on the desired node.
Setup Procedures 1-3 Configure the OPC Server(s) Before ProcessLinx can work properly in runtime, each OPC Server must be installed and configured correctly. Follow the installation procedure and setup specified with the documentation for the external OPC Server. A TCP/IP connection must also exist between the NT ProcessLogix node and any remote node running an external OPC server for which you wish ProcessLinx to connect with.
1-4 Setup Procedures ps_user accounts on them. Refer to the sections in Knowledge Builder, About ProcessLogix-To-OPC Server/Client Communications, Communicating with 3rd Party Clients, and Creating a MNGR Account for a Third-Party Client. IMPORTANT The following instructions apply only to Windows 2000 and Windows XP. Windows NT is not supported. For example, if the ps_user account is not the client, you must add it by doing the following: 1. Right click on My Computer. 2.
Setup Procedures 1-5 2. Type regsvr32 opcproxy.dll in the Run dialog box. IMPORTANT Unless opcproxy.dll is in the Windows\System32 directory the above command will fail because it can't find the OPCPROXY.DLL. You need to specify the full path the the DLL (i.e. regsvr32 “C:\Program Files\Common Files\OPC Foundation\opcproxy.dll”) 3. On the server machine, go to the C:\Honeywell\Client\Opcserverconnect, folder and copy the HSCOPCCONNECT.REG & HSCOPCSERV.REG files to a floppy diskette. 4.
1-6 Setup Procedures Notes: Publication 1757-UM002B-EN-P - January 2003
Chapter 2 Getting Started This section provides the required information to setup and configure both the ProcessLinx software as well as the communications interface to the ProcessLogix OPC Server and the external OPC Server. ProcessLinx Version The version of the ProcessLinx can be found by selecting the Help menu in the main window. The version label below displays Version 2 and Build # is 68, built on January 10, 2003. Figure 2.
2-2 Getting Started To change ProcessLinx to runtime select Mode ⇒ Runtime, click Runtime Mode or press . While in runtime mode ProcessLinx acts as an OPC Client to both the ProcessLogix server and the external OPC Server. Initiating runtime mode establishes all OPC Groups and Items with the specified OPC Server(s). The opened TagMap configuration (See Figure 2.1) is activated.
Getting Started Configure ProcessLinx Options 2-3 To configure ProcessLinx Options select from the Utility menu, Utility ⇒ Configure Options or click in the tool bar. You see: Figure 2.3 Options Dialog Box Automatically startup in runtime mode when ProcessLinx is started This option starts ProcessLogix in runtime mode. This change takes effect the next time you start the program. If unchecked then you must manually place ProcessLinx in runtime mode. Default is unchecked.
2-4 Getting Started a remote server connection is lost, ProcessLinx may keep trying to connect with it, you may have to restart ProcessLinx. ATTENTION ! This restart situation depends on how you setup DCOM with the COM interface (OPC Server). Be certain to follow the DCOM steps in Chapter 7 for best performance when you configure TCP/IP and DCOM with COM I/F to OPC Server. For local OPC servers (running on the same PC as ProcessLinx) this option is not used. The default is checked.
Getting Started 2-5 Number of Retries for Redundancy / OPC Server Switchover This option specifies the number of retries attempts to connect to a redundant OPC Server. Retries are initiated after communication is lost with a server. For example, if this is set to three and communication is lost with the primary server, ProcessLinx will switchover to the secondary server (if defined). Three connection attempts are made to the secondary server before switching back to the primary.
2-6 Getting Started Notes: Publication 1757-UM002B-EN-P - January 2003
Chapter 3 ProcessLinx TagMap Configuration A ProcessLinx TagMap configuration is created to communicate OPC items (also known as tags) from one OPC server to another. This configuration maps each data point exchanged between systems using the OPC protocol. The ProcessLinx configuration is a hierarchy of user-defined objects. The top-level object is a Pipe. A Pipe defines which OPC Servers are used for data exchange.
3-2 ProcessLinx TagMap Configuration Creating a ProcessLinx Configuration IMPORTANT Opening a ProcessLinx Configuration ProcessLinx will not load or open a configuration in runtime, the interface must be placed into configure mode first. To: Select: create a ProcessLinx configuration File ⇒ New… save, copy or backup the configuration File ⇒ Save (or) Save As… and give it a meaningful name. To: Select: open an existing ProcessLinx configuration File ⇒ Open...
ProcessLinx TagMap Configuration 3-3 Name blank or set it to “localHost”. Included in ProcessLinx 2.0 is an executable that only allows you to create and/or Import up to 10 Pipes. Configure this setting by creating/editing a REG_DWORD Registry key value at: HKLM\SOFTWARE\Rockwell Software\ProcessLinx\Options\MaxPipes The default is 10 if the Key is not found. If value is set to less than 1 the default is set to 10 since there should always exist at least 1 Pipe.
3-4 ProcessLinx TagMap Configuration Figure 3.1 Pipe Properties Dialog Box Using the Pipe Properties dialog box 1. Select a meaningful name for the Pipe. 2. If needed, enter comments about the interface in the text description box. 3. Enter the host name(s) and OPC Server Name(s) for the ProcessLogix and the External OPC Server for the new Pipe. a. To browse for an OPC Server click Select… A “Select OPC Server” dialog box containing all installed OPC Servers on the local machine will be displayed. b.
ProcessLinx TagMap Configuration IMPORTANT 3-5 If the OPC Server does not show up in the list, then it has not been properly installed or registered on the machine. Remote servers do not have to be installed on the local node in order to connect with them. Their OPC Class information (GUID, refer to Preparing the Client’s User Accounts on page 1-3) needs to be registered on the local machine.
3-6 ProcessLinx TagMap Configuration Use v1.0 OPC Interfaces The Use v1.0 OPC Interfaces checkbox indicates that v1.0 OPC Interfaces are used when reading/writing data with the OPC Server. This option is for OPC Servers that do not support the v2.0 Interfaces. By default this option is left unchecked. ProcessLinx will attempt to use the v2.0 Interfaces if left unchecked, and will automatically revert to the v1.0 interfaces if the Server does not support v2.0.
ProcessLinx TagMap Configuration 3-7 Attempt Failover if all OPC Items are Bad Quality This checkbox will enable or disable failover when all OPC Items are bad Quality. This option is specifically used with ProcessLogix redundant Server scheme but can be used with any OPC Server. The redundant (backup) OPC Server of ProcessLogix will set all OPC Items to 'Out-of-Service' BAD Quality when the node becomes the backup and thus this can be used as a trigger for ProcessLinx to failover to the redundant server.
3-8 ProcessLinx TagMap Configuration • If just one of those active tags is GOOD or QUESTIONABLE quality then server is not failed on the basis of 'Bad Quality' since data can be obtained for at least one of the items. This also means that the server cannot be 'failed' on the basis of Bad Quality if the user set all groups in that server to Inactive (i.e. No active groups) since there will be no active tags to check quality with. Creating a Group To: Select: create a Group 1. Select the Pipe 2.
ProcessLinx TagMap Configuration 3-9 The number of Groups you can add is limited by memory and possible OPC Server limitations. The OPC Server may set a limit on the number of groups you can define, if the limit is exceeded then the error CONNECT_E_ADVISELIMIT is returned and ProcessLinx will display a message (“the server hit the Advise limit, please limit the # of groups defined”) that is logged in the log file.
3-10 ProcessLinx TagMap Configuration Data Flow Direction IMPORTANT Data Flow Direction is the only parameter that cannot be changed in runtime. The available data flow directions between the ProcessLogix OPC Server and the External OPC Server for all TagMaps within the Group are: Æ Specifies that OPC items are read from the ProcessLogix Server and written to their map in the External Server. ÅÆ Specifies that data flows in both directions.
ProcessLinx TagMap Configuration 3-11 Table 3.A Group Parameter Description Parameter Description Active Group This checkbox specifies the Group parameter’s active status. Data for all TagMaps in the Group can only be transmitted if the Group is active within the OPC Server in runtime. Group communication is disabled by unchecking this option. This can be modified in runtime to enable or disable particular Groups.
3-12 ProcessLinx TagMap Configuration 2. Select Edit ⇒ Add TagMap... from the main menu or right mouse clicking on the Group and then selecting “Add Single TagMap”. The TagMap Definition dialog box, (shown below) displays for the TagMap and can be edited. Figure 3.
ProcessLinx TagMap Configuration 3-13 Attributes are specified as part of defining the TagMap in the above dialog box. The TagMap parameters are defined below: Table 3.B TagMap Parameters Parameter Description Description You can enter a description for the TagMap entry. This field can be left blank if desired. IMPORTANT: Commas are not allowed in the description. Data Flow / Data Master Data Master defines where the data originates when starting runtime mode.
3-14 ProcessLinx TagMap Configuration Table 3.C TagMap Data Attributes Attribute Description Server The Server field displays the defined OPC Server for this half of the TagMap. OPC Item Use the OPC Item area to enter the specific tag in the OPC Server. For OPC v2.0 compliant servers, “Browse” opens the database for point-and-click OPC Item entry. When the Item is selected, its tag name is entered in thus field. Tip: To browse OPC Items from ProcessLogix, export the Control Builder configuration.
ProcessLinx TagMap Configuration 3-15 Table 3.C TagMap Data Attributes Attribute Description Data Type Data Type displays the default OPC tag type for the selected OPC Item. This is set to “native” initially. In runtime, the actual OPC Item’s data type is received from the OPC Server and subsequently displayed. Access The OPC Item Access displays in this field. This attribute is defined in the Parent Group and is read only. “Read Only” indicates that no value can be written to the OPC Item.
3-16 ProcessLinx TagMap Configuration By default, ProcessLinx attempts to use the item file when browsing ProcessLogix tags used to map tags. If this file does not exist then each time the “Add TagMap(s)” function is executed it parses and compiles all exported function block files and creates the function block list with no connectable items to map to. If this happens, create a ProcessLinx.itm file manually by performing the following steps: 1.
ProcessLinx TagMap Configuration 3-17 under the function blocks. Note: Some of the items are not connectable. Data Conversion/Scaling Most analog values exchanged between the ProcessLogix OPC Server and an External OPC Server are already expressed in engineering units and therefore, linear scaling of analog values is not required. To accommodate discrete values not meeting this condition, TagMap definitions allow scaling.
3-18 ProcessLinx TagMap Configuration Some of the main parameter names along with their data types for each ProcessLogix point type are given below. TIP Refer to the ProcessLogix Server and Client Configuration Guide documentation in Knowledge Builder for a complete listing of all supported data types. Refer to the ProcessLogix Parameter Reference Manual in Knowledge Builder for parameter definitions. Table 3.
ProcessLinx TagMap Configuration 3-19 Table 3.G Analog Point Parameters ModeInError VT_BOOL Read only SetPointInError VT_BOOL Read only OutputInError VT_BOOL Read only InLowAlarm VT_BOOL Read only InHighAlarm VT_BOOL Read only PointInAlarm VT_BOOL Read only Table 3.
3-20 ProcessLinx TagMap Configuration Table 3.I Table 7.D Control Point Parameters for a PID or PIDA block PVEUHI VT_R4 Read only K VT_R4 KLIN VT_R4 K VT_R4 T1 VT_R4 T2 VT_R4 CVEULO VT_R4 Read only CVEUHI VT_R4 Read only OPHILM VT_R4 OPLOLM VT_R4 SPHILM VT_R4 SPLOLM VT_R4 Table 3.
ProcessLinx TagMap Configuration Translation Table 3-21 To enable scaling for a particular TagMap, you must define and select a translation table. In runtime, the table converts values from one OPC Server to valid values for the other OPC Server. This is useful for converting the discrete mode states of a ProcessLogix DEVCTL function block an External OPC block. You can define as many translation tables as needed. The correct translation for the TagMap is selected from the available list.
3-22 ProcessLinx TagMap Configuration • To add or edit a new translation value map for the selected translation table, select Add. Figure 3.5 Translation Value Dialog Box Enter the given conversion values for either side of this translation. Repeat the Add... step for all discrete values. TIP Translations can be added and edited using CSV files. Refer to Import/Export on page 5-1 for more information. The example in Figure 3.4 shows two ProcessLogix discrete values mapped to an External OPC Server.
ProcessLinx TagMap Configuration 3-23 If you hold down the key before you drop the object(s), the objects are copied to the desired Group. Otherwise the TagMaps are moved to the new Group. Multiple TagMap Configuration Multiple tags can be mapped quickly using the “Map Tags” dialog box. Highlight the desired Group and Select Edit ⇒ Add TagMap(s)... from the main menu or press or right mouse click on the Group and select Add TagMap(s)…. Figure 3.
3-24 ProcessLinx TagMap Configuration browse capability the External Server must be registered on the local PC. Each pane contains a tree view listing of all available OPC items within the Server. You select an OPC item on one side and the corresponding item to map to on the other and click ÅMAPÆ. Alternatively, the user can select an item from one side and drag it into an OPC Item on the other to create a tag mapping. The data flow direction is decided by the direction of the Parent Group.
Chapter 4 ProcessLinx Runtime Operation Each Pipe created in ProcessLinx provides a conduit to pass information between OPC Servers. An OPC Server cannot communicate directly to another OPC Server. Each OPC Server expects responses that are normally received from an OPC Client. ProcessLinx uses OPC Client responses to receive data from one OPC Server and transmit it to another OPC Server. When runtime mode is started, the Groups defined in each ProcessLinx Pipe are created in the respective OPC Servers.
4-2 ProcessLinx Runtime Operation Writing OPC Values In runtime, values can be manually written to an OPC Item. Select and right mouse click on the desired TagMap’s OPCItem1 column. Select Write ⇒ OPCItem1 or OPCItem2 from the corresponding pop-up menu. Figure 4.1 Writing to an OPC item Enter the new value in the Current Value field. Click WRITE to force an OPC write to the specified OPC Item. To verify the value was correctly written, click READ.
ProcessLinx Runtime Operation Redundant OPC Servers / Fail over 4-3 ProcessLinx supports redundant OPC Servers using networked hosts. The Primary and Secondary hosts are configured in the Pipe dialog box. When runtime mode is started, each Pipe connection is attempted with the defined primary host. If that connection attempt fails, a new attempt is sent to the secondary host. If both attempts fail, ProcessLinx control mode is set to Configure for the user to correct the situation.
4-4 ProcessLinx Runtime Operation Server Status You can view the runtime status of each Pipe’s OPC Servers. Select Utility ⇒ Server Status…. Or right mouse click on a Pipe or Group and click Server Status. Figure 4.2 Server Status Dialog Box A switchover to the redundant OPC Server can be forced by clicking Switch Server. If a redundant Server is not defined, ProcessLinx disconnects from the primary Server and then reconnects to it.
ProcessLinx Runtime Operation Verifying OPC Tags 4-5 In runtime, you can verify the status of all active OPC Items. Select Utility ⇒ Verify OPC Tags from the main menu to check all OPC Items. If an error is found, a message is displayed in the Message pane. A successful verification displays these messages: MSG:: Verifying OPC Tags in Server A... MSG:: OPC Tags Verified! MSG:: Verifying OPC Tags in Server B... MSG:: OPC Tags Verified When you select the ‘Verify Tags...
4-6 ProcessLinx Runtime Operation Notes: Publication 1757-UM002B-EN-P - January 2003
Chapter 5 Import/Export This chapter provides ProcessLinx TagMap import/export examples. Using the Import/Export functions, you can edit configurations via text based, comma-separated-value (CSV) files such as the ProcessLinx configuration which is stored in a binary file. To: Select: export an open ProcessLinx TagMap configuration File ⇒ Export CSV… Enter an export filename and click OK. Edit the export file using Note Pad, Excel, etc.
5-2 Import/Export When you choose Yes, to overwrite the existing Pipe with the import information, ProcessLinx adds the new Groups, TagMaps, and Translation Tables to the existing Pipe. The following also occurs: • All existing Groups and Translation Tables are overwritten with the settings from the CSV file. • Existing TagMaps are not overwritten. ProcessLinx adds duplicate TagMaps. • Delete TagMaps from the existing configuration before they are imported again.
Import/Export CSV File Formats 5-3 A CSV file is an ASCII Text file that contains fields delimited by commas. Text editors, spreadsheet programs, and database packages can create, edit, and save CSV files. Because commas are used as field delimiters, commas are NOT allowed in field values. Each text line represents one ProcessLinx command or object definition. A CSV file example with one Pipe, three Groups, and two Translation tables is given in Figure 4-2. BEGIN_PIPE PIPE,Pipe1,,1,localHost,HWHsc.
5-4 Import/Export Each Pipe object in the CSV file starts with BEGIN_PIPE and ends with END_PIPE. The Pipe is declared with a PIPE statement. The fields in the PIPE statement are in Table 5.A. Pipe Declarations • A comma within the CSV file must separate each field. • No string fields can contain commas. • All string data types are NOT case sensitive. Table 5.
Import/Export 5-5 Group Declarations All Groups in a Pipe are declared between the BEGIN_PIPE and END_PIPE statements. A Group and its TagMaps are defined between the BEGIN_GROUPMAP and END_GROUPMAP statements. A Group is declared using the GROUPMAP line. Three Groups are defined in the example file shown in Figure 4-2. The fields in the GROUPMAP declaration are in Table 5.B.T Table 5.
5-6 Import/Export TagMap Declarations An unlimited number of TagMaps can be defined in each Group. Each TagMap is declared with a TAGMAP statement. The fields in a TAGMAP declaration are in Table 5.C. Table 5.C TagMap Declarations Field # FIELD NAME FIELD TYPE FIELD DESCRIPTION Examples 1 Line Type String Contains the string TAGMAP to define this line in the CSV file as a TagMap. TAGMAP 2 Description String Specifies the description of this TagMap. This field cannot contain any commas.
Import/Export 5-7 Translation Table declarations Translation tables are defined at the end of the CSV file. Each table is created with BEGIN_TABLE and END_TABLE declarations. The table name and type are declared with a TABLE line. The fields in a TABLE declaration are in Table 5.D. Table 5.D Translation Table Declarations Field # FIELD NAME FIELD TYPE FIELD DESCRIPTION Examples 1 Line Type String Contains the string TABLE to define this line in the CSV file as a Translation Table.
5-8 Import/Export 3. In the TagMap dialog box in ProcessLinx click the Read from Export Directory to load in the browseable points. Not all points will be loaded. This operation will only display points within the Control Builder configuration. Points (such as interface points) added using Quick Builder will not be displayed. These points must be manually added on a single TagMap basis or can be added using the ProcessLogix Import function.
Chapter 6 Error Diagnosis and Debugging This chapter explains how to diagnosis errors and debug ProcessLinx in the event the Runtime operations are not functioning properly. ProcessLinx logs errors along with informational messages to the message log in runtime mode only. Use the log to diagnose potential error conditions. Quick Setup Quick Setup describes how you can quickly setup ProcessLinx and diagnose common setup problems.
6-2 Error Diagnosis and Debugging Table 6.A Item Subject Description 8. Is ProcessLogix the main OPC Server? • You may need to create a user account and/or with administrator privledges on the node running ProcessLinx. • If you are running an NT Workgroup, you may need to logon to the ProcessLinx node as or in order to connect to the remote ProcessLogix OPC Server node. This is not the case when running under a domain.
Error Diagnosis and Debugging Debug Operations 6-3 You can execute simple debug operations during runtime from the main menu’s debug menu item.
6-4 Error Diagnosis and Debugging In runtime mode, ProcessLinx supports the following debug options: Table 6.B ProcessLinx Debug Options Options Description Mode (Debug Level) • Sets the debug mode of the ProcessLinx. • The higher the debug level the more messages will be printed to the screen. To turn all debug messages off set the MODE to OFF. Clear Messages • Clears all messages in the message pane window.
Chapter 7 Using DCOM OPC Servers This section details how to setup and diagnosis problems with DCOM Servers over a TCP/IP network. This is not an exhaustive guide and only discusses the common problems found with DCOM Network setup. All of the software components of the ProcessLogix OPC Server are installed during the ProcessLogix server installation. The OPC Server option MUST be included with your ProcessLogix license.
7-2 Using DCOM OPC Servers under the Identity tab. Launching User is the default option, so this task must be done manually. IMPORTANT This is not the case for the ProcessLogix OPC Server where the process is configured to run under the account. You must enable the security permissions correctly on the remote machine for the ProcessLinx node to access and launch the OPC Server remotely. Instructions for this procedure are specified in the ProcessLogix Server and Client Installation Guide. 1.
Using DCOM OPC Servers 7-3 • EnableDCOM key. Set to ‘Y’ on BOTH the remote OPC server machine and the machine running ProcessLinx regardless of the Windows version. This key is found using the registry path: HKEY_LOCAL_MACHINE\Software\Microsoft\Ole\EnableDCOM=’Y” • LegacyAuthenticationLevel key. Set to 1 on the remote OPC server machine.
7-4 Using DCOM OPC Servers Notes: Publication 1757-UM002B-EN-P - January 2003
How Are We Doing? Your comments on our technical publications will help us serve you better in the future. Thank you for taking the time to provide us feedback. You can complete this form and mail it back to us, visit us online at www.ab.com/manuals, or email us at RADocumentComments@ra.rockwell.com Pub. Title/Type ProcessLinx OPC Server to Server Software Cat. No. 1757-PROCESSLINX Pub. No. 1757-UM002B-EN-P Pub. Date January 2003 Part No. 957726-17 Please complete the sections below.
PLEASE FASTEN HERE (DO NOT STAPLE) PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO.
Publication 1757-UM002B-EN-P - January 2003 2 Supersedes Publication 1757-UM002A-EN-P - May 2001 PN 957726-17 Copyright © 2003 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
