Fieldbus Solutions for Rockwell Automation’s Integrated Architecture ProcessLogix, ControlLogix, and PLC5 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 these products 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 About this Document Contents guide The following table summarizes each chapter in this document. Table P.A Content Summary Read this chapter: If you need to: Chapter 1, The Fieldbus Communication Model or network layer? become familiar with the Fieldbus Foundation is or what constitutes the FOUNDATION Fieldbus® technology. This section also includes descriptions of some standard fieldbus function blocks and describes the role of Device Descriptions and block parameters for general reference.
About this document P-2 Conventions The following table summarizes the terms and type representation conventions used in this Guide. Table P.B Convention Definitions Term/Type Representation Meaning Example Click Click left mouse button once. (Assumes cursor is positioned on object or selection.) Click the Browse button. Double-click Click left mouse button twice in quick succession. (Assumes cursor is positioned on object or selection.) Double click the Station icon.
About this document Rockwell Automation Technical Support P-3 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.
About this document P-4 Notes: Publication 1757-UM006A-EN-P - May 2002
Table of Contents Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . . ii Preface About this Document Contents guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rockwell Automation Technical Support . . . . . . . . . Local Product Support . . . . . . . . . . . . . . . . . . . . Obtain Technical Product Support . . . . . . . . . . . Your Questions or Comments about This Manual . . . . . . . . . .
vi Table of Contents Chapter 2 Integrating Fieldbus into Rockwell Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Background - the goals of integration . . . . . . . . . . . . . . 2-1 Automation Logix System Fieldbus Integrated Architecture . . . . . . . . . . . . . . Fieldbus Interface Modules - The Key to an Integrated System . . . . . . . . . . . . . . . . . Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . Foundation Fieldbus Configuration Tool .
Table of Contents vii Chapter 3 1757-FIM Planning Considerations Reference Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Installation declaration . . . . . . . . . . . . . . . FIM and I/O module allowance . . . . . . . . Fieldbus network references. . . . . . . . . . . Fieldbus wiring selection and calculation . Installing 1757-FIM Fieldbus Interface Module Installing 1757-RTP Remote Terminator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii Table of Contents Chapter 5 Operating the 1757-FIM Monitoring Fieldbus Functions Through Station Displays Using Station Detail displays. . . . . . . . . . . . . . . . . . . Using Station Event Summary display . . . . . . . . . . . . Monitoring Fieldbus Functions Through Monitoring Tab . Inactivating/Activating a Link . . . . . . . . . . . . . . . . . . Monitoring/Interacting with given component/block . Checking fieldbus device functional class . . . . . . . . .
Table of Contents MDO Blocks . . . . . . . . . . . . . . . . . . . . . . . Viewing Object Information in the NI-FBUS Configurator. . . . . . . . . . . . . . . . . . . . . Changing the Linking Device Configuration Trends and Alarms . . . . . . . . . . . . . . . . . . . . . Tips for Connecting to a 1756-ENET Controller. ix . . . . . . . . . 7-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16 7-17 7-18 7-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x Table of Contents Appendix D Fieldbus Wiring Considerations ........................ Fieldbus Topologies . . . . . . . . . Power Conditioning . . . . . . . . . Power Distribution . . . . . . . . . . Signal Degradation Limitations. . Cable Guidelines. . . . . . . . . . . . Cable Attenuation . . . . . . . . . . . Signal Distortion vs Capacitance Calculating Attenuation . . . . . . . Testing the Cable . . . . . . . . . . . Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents PLC-5 and ControlLogix Applications . . . . . . . . . . . . . ControlLogix Application. . . . . . . . . . . . . . . . . . . . . . Schedule the Connection Between the Controller and the Linking Device. . . . . . . . . . View the Controller Tags . . . . . . . . . . . . . . . . . . . Testing the Installation Example . . . . . . . . . . . . . . . . Messages to PLC-5s and CLX to Get Data from CN2FF Remote Configuration of a Fieldbus Network via the 1788-CN2FF . . . . . . . . . . . . . . . . .
xii Table of Contents Publication 1757-UM006A-EN-P - May 2002
Chapter 1 The Fieldbus Communication Model Fieldbus Organization About the Fieldbus Foundation The Fieldbus Foundation is a not-for-profit corporation made up of nearly 120 leading suppliers and customers of process control and manufacturing automation products. Since its inception in 1994, it is totally dedicated to developing one standard, “open,” interoperable field communication model known as FOUNDATION™ Fieldbus(1). Want more information? Visit the Fieldbus Foundation web site at www.fieldbus.
1-2 The Fieldbus Communication Model Comparisons among “fieldbus technologies” typically reduces to comparisons of data rates, message length, number of devices on a segment, etc. These are all important communications issues and each technology represents a particular set of trade-offs which adapt it to its original application, and each is rooted in the technology that was available or in vogue at the time of its development.
The Fieldbus Communication Model 1-3 Open Communications Architecture FOUNDATION Fieldbus is an enabling technology for dynamically integrating dedicated field devices with digitally based control systems. It defines how all “smart” final control devices are to communicate with other devices in the control network. The technology is based upon the International Standards Organization's Open System Interconnection (OSI) model for layered communications. As shown in Figure 1.
1-4 The Fieldbus Communication Model Communication Layer Description The following table provides a summarized description of the communication layers that make up the FOUNDATION Fieldbus. The Fieldbus Foundation maintains a complete library of detailed reference specifications including a Technical Overview, and Wiring and Installation Guides. Table 1.
The Fieldbus Communication Model 1-5 Table 1.A Communication Layer Descriptions Layer Functional Description Associated Terms User Application or Function Block Application Process (FBAP) Defines blocks to represent different types of application functions. The three types of blocks are the Resource block, the Function block, and the Transducer block. See Figure 1.2. The Resource block is used to describe characteristics of the fieldbus device such as the device name, manufacturer, and serial number.
1-6 The Fieldbus Communication Model Standard Function Blocks The key to fieldbus interoperability is the User Application or Function Block Application Process (FBAP) that defines standard function blocks that can reside in field devices and be interconnected as a distributed process control system. A function block is a named entity that has inputs, outputs, and parameters. It performs certain functions that operate on its inputs and produce outputs in accordance with its assigned parameters.
The Fieldbus Communication Model 1-7 Function blocks make it possible to build a control loop using fieldbus devices that include the appropriate Function block types. For example, a pressure transmitter that contains an Analog Input and Proportional/Integral/Derivative blocks can be used with a valve containing an Analog Output block to form a control loop, as shown in Figure 1.3. Figure 1.
1-8 The Fieldbus Communication Model About Modes of Operation Every Function block includes a mode parameter with configured permitted modes. This structured parameter is composed of the actual mode, the target mode, the permitted mode, and the normal mode. The normal mode is the desired operating mode. The actual mode reflects the mode used during block execution. The target mode may be set and monitored through the mode parameter. The permitted mode defines the allowable target mode settings.
The Fieldbus Communication Model 1-9 Analog Input Block Figure 1.
1-10 The Fieldbus Communication Model Table 1.D Analog Input Block Specifications Description The AI function block takes the input data from a Transducer block and calculates an output to be fed to other fieldbus function blocks. A functional schematic of the block is shown in Figure 1.4 for reference. Function Notes • Supports Out of Service (OOS), Manual (Man), and Automatic (Auto) modes.
The Fieldbus Communication Model 1-11 Analog Output Block Figure 1.
1-12 The Fieldbus Communication Model Table 1.E Analog Output Specifications Description The Analog Output function block converts the set point (SP) value to a number that can be used by the hardware associated with the CHANNEL selection. A functional schematic of the block is shown in Figure 1.5 for reference. Function Notes • Can use either the Set point (SP) value after limiting or the Process Variable (PV) value for the BKCAL_OUT value.
The Fieldbus Communication Model 1-13 Bias/Gain Block Figure 1.
1-14 The Fieldbus Communication Model Table 1.F Bias/Gain Block Specifications Description The Bias/Gain function block can be used for biased external feedforward control or to set several unit controllers, such as boiler masters, from one controller output, such as a plant master. A functional schematic of the block is shown in Figure 1.6 for reference.
The Fieldbus Communication Model 1-15 Control Selector Block Figure 1.
1-16 The Fieldbus Communication Model Table 1.G Control Selector Block Specifications Description The Control Selector function block accepts input from up to three control signals and selects one for output based on the SEL_TYPE setting of High, Middle, or Low. A functional schematic of the block is shown in Figure 1.7 for reference. Function Notes • All inputs must have the same scaling as OUT, since any one can be selected for OUT.
The Fieldbus Communication Model 1-17 Discrete Input Block Figure 1.8 Functional Schematic for Discrete Input Function Block Transducer Simulate SIMULATE_D CHANNEL OUT DI Optional Invert Filter PV_FTIME PV_D Output OUT_D FIELD_VAL_D Mode SHED_OPT Alarms DISC Table 1.H Discrete Input Block Specifications Description The Discrete Input function block takes the discrete input data from a selected Transducer block channel and provides it as an output for other fieldbus function blocks.
1-18 The Fieldbus Communication Model Discrete Output Block Figure 1.9 Functional Schematic for Discrete Output Function Block BKCAL_OUT_D CAS_IN_D OUT_D RCAS_OUT_D DO RCAS_IN_D Transducer BKCAL_OUT_D RCAS_OUT_D CAS_IN_D Setpoint Output Optional Invert OUT_D RCAS_IN_D SP_D Mode SHED_OPT PV_D Optional Invert Failsafe FSAFE_TIME FSAFE_VAL_D Simulate SIMULATE_D CHANNEL READBACK_D Table 1.
The Fieldbus Communication Model 1-19 Manual Loader Block Figure 1.
1-20 The Fieldbus Communication Model Table 1.J Manual Loader Block Specifications Description The Manual Loader function block output is not set by the block's algorithm. Its output can be set by an operator in the Manual mode or a program in the Remote-Out mode. A functional schematic of the block is shown in Figure 1.10 for reference. Function Notes • Supports Out of Service (OOS), Initialization Manual (IMan), Local Override (LO), Manual (Man), and Remote-Out (ROut) modes.
The Fieldbus Communication Model 1-21 Proportional/Derivative Block Figure 1.
1-22 The Fieldbus Communication Model Table 1.K Proportional/Derivative Block Function Notes (cont.) • A BYPASS switch function is available for operators to use, when secondary cascade controllers have a bad PV and the Bypass Enable (LSB) CONTROL_OPTS is ON. The Bypass Enable option is required, since some control schemes may become unstable when BYPASS is ON. An operator can only set the BYPASS switch, when the block is in the Man or OOS mode.
The Fieldbus Communication Model 1-23 Proportional/Integral/Derivative Block Figure 1.
1-24 The Fieldbus Communication Model Table 1.L Proportional/Integral/Derivative Block Specifications Function Notes (cont.) • The tuning constant used for the Proportional term is GAIN, RESET is used for the Integral term, and RATE is used for the Derivative term. Both RESET and RATE are time constants expressed in seconds. Some controllers use the inverse values of Proportional Band and repeats per minutes for their tuning constants. Users can choose which tuning constants they want to display.
The Fieldbus Communication Model 1-25 Ratio Block Figure 1.13 Functional schematic for Ratio function block. IN IN_1 BKCAL_IN BKCAL_OUT RA CAS_IN RCAS_IN OUT RCAS_OUT TRK_IN_D TRK_VAL BKCAL_OUT RCAS_OUT CAS_IN RCAS_IN Setpoint SP_RATE_DN SP_RATE_UP SP_HI_LIM SP_LO_LIM IN_1 Filter RA_FTIME IN Filter PV_FTIME Mode SHED_OPT SP BKCAL_IN Ratio GAIN Calc PV GAIN Output OUT_HI_LIM OUT_LO_LIM BAL_TIME OUT PV Alarm HI/LO DEV Output Track TRK_SCALE TRK_IN_D TRK_VAL Table 1.
1-26 The Fieldbus Communication Model Table 1.M Ratio Block Specifications Function Notes (cont.) • The full cascade SP sub-function is used, with rate and absolute limits. Additional control options are available to have the SP value track the PV value, when the block's actual mode is IMan, LO, Man, or ROut. Limits do not cause SP-PV tracking. • Use the Act on IR CONTROL_OPTS to select whether to pass initialization requests or act on them locally by changing the SP value.
The Fieldbus Communication Model Device Descriptions and Block Parameters 1-27 About Device Descriptions Device Descriptions (DD) are absolutely critical to the interoperability of fieldbus devices. They define the data needed to establish communications among different fieldbus devices from multiple vendors and with control system hosts. The DD provides an extended description of each object in the User Application Virtual Field Device (VFD).
1-28 The Fieldbus Communication Model Device Description infrastructure The Fieldbus Foundation defines a four-level infrastructure for Device Descriptions for the sake of consistency. See Figure 1.14 for a graphical representation of the DD infrastructure. Figure 1.14 Device Descriptions infrastructure.
The Fieldbus Communication Model Foundation Fieldbus Performance 1-29 Foundation Fieldbus is a powerful network providing both communication and distributed control capability. However, fast response is not one of its great capabilities. The screen capture below reflects the time allocated for 18 function blocks to publish their outputs on Fieldbus. The average time is about 40 ms. per published value.
1-30 The Fieldbus Communication Model through independent function blocks, so each require their own 40 to 50 milliseconds. The 1788-CN2FF operates on the Fieldbus side at the max. speed of the Fieldbus, and at the ControlNet rate on the ControlNet side. Therefore, the 1788-CN2FF is not a limiting factor in a Fieldbus systems performance. When a 1788-CN2FF operates, the Fieldbus side and the CN side run asynchronously.
Chapter 2 Integrating Fieldbus into Rockwell Automation Logix System Overview Background - the goals of integration The following table summarizes the major areas of consideration that were key to defining the goals for bringing Fieldbus into ProcessLogix. Table 2.A 1 Function Goal Connection of Foundation Fieldbus devices to a Logix system. Integrate fieldbus devices on an H1 link with Supervisory level ControlNet or Ethernet network, and/or the I/O ControlNet network.
2-2 Integrating Fieldbus into Rockwell Automation Logix System Fieldbus Integrated Architecture As shown in Figure 2.1, Foundation Fieldbus devices can be connected or integrated into a Rockwell Logix system. ProcessLogix, Release 400.0 and later can be configured with a Fieldbus Interface Module (FIM). The FIM serves as the communication gateway between the Supervisory ControlNet/Ethernet and/or I/O ControlNet network and the Foundation Fieldbus H1 communications medium.
Integrating Fieldbus into Rockwell Automation Logix System 2-3 Fieldbus Interface Modules - The Key to an Integrated System The 1757-FIM, Fieldbus Interface Module is the key to bringing the Foundation Fieldbus system into a ProcessLogix system. The FIM has been designed to operate as a stand-alone Foundation Fieldbus interface or as a bridge between the ProcessLogix control environment and the fieldbus devices.
2-4 Integrating Fieldbus into Rockwell Automation Logix System Configuration Tools 1788-CN2FF Linking Device The ControlNet-to-Foundation Fieldbus H1 linking device (1788-CN2FF) connects a ControlNet™ network with one or two FOUNDATION Fieldbus H1 (Fieldbus) networks. Each H1 network consists of multiple Fieldbus devices. Each field device has one or more function blocks. Each function block performs an elementary control function such as analog input, analog output, discrete input, or discrete output.
Integrating Fieldbus into Rockwell Automation Logix System 2-5 Figure 2.2 Project tab in Control Builder has new icons for Fieldbus components.
2-6 Integrating Fieldbus into Rockwell Automation Logix System Network Management description Network Management provides the following capabilities for managing the communication system of a fieldbus device. • Loading a Virtual Communication Relationship (VCR) list or single entries in this list; (A VCR represents a communication channel through the complete communication stack.
Integrating Fieldbus into Rockwell Automation Logix System 2-7 About the Device Object The device object represents a physical device entity connected to the fieldbus link. It provides access to the device's Network Management (NM) and System Management (SM) parameters. The client/server VCR is configured in the FIM to access the Management Interface Base (MIB) of the device as soon as it joins the network. The Control Builder does not configure the MIB VCR explicitly.
2-8 Integrating Fieldbus into Rockwell Automation Logix System Figure 2.3 shows a simplified functional diagram of how the output from an Analog Input function block in a fieldbus compliant transmitter is integrated with a PID function block in a Control Module that is assigned and loaded to the CEE in the Control Processor Module (CPM). Figure 2.
Integrating Fieldbus into Rockwell Automation Logix System 2-9 The fieldbus data quality of good, bad, and uncertain is mapped to the appropriate ProcessLogix parameter of PVSTS, PVSTSFL.NORM, PRSTSFL.BAD, or PVSTSFL.UNCER. The fieldbus limit indications of no-limit, limited-low, limited-high, and constant are mapped to the same four indications for ProcessLogix. The fieldbus data substatus indicator maps only the limited number of substatus conditions that have corresponding ProcessLogix indications.
2-10 Integrating Fieldbus into Rockwell Automation Logix System Figure 2.4 shows a simplified functional diagram of how the output from a PID function block in a Control Module that is assigned and loaded to the CEE in the Control Processor Module (CPM) is integrated with an Analog Output function block in a fieldbus compliant device. Figure 2.
Integrating Fieldbus into Rockwell Automation Logix System 2-11 Figure 2.5 shows a simplified functional diagram of how the output from a PID function block in a Control Module that is assigned and loaded to the CEE in the Control Processor Module (CPM) is integrated with a cascaded Proportional, Integral, Derivative function block in a fieldbus compliant device. Figure 2.
2-12 Integrating Fieldbus into Rockwell Automation Logix System The block-like output agent maps the ProcessLogix OP with status parameter to the fieldbus data structure (DS-65) of the CAS_IN parameter. It interprets the value portion in ProcessLogix terms and converts it to fieldbus representation. The floating-point representation is identical, in most cases, but the ProcessLogix +/-infinity value must be converted to a fieldbus representation.
Integrating Fieldbus into Rockwell Automation Logix System 2-13 The ProcessLogix data quality is converted to fieldbus data quality. The ProcessLogix Good indication is represented as fieldbus Good(Cascade). The ProcessLogix limit indications of no-limit, limited-low, limited-high, and constant are mapped to the same four indications for fieldbus.
2-14 Integrating Fieldbus into Rockwell Automation Logix System Figure 2.
Integrating Fieldbus into Rockwell Automation Logix System 2-15 Fieldbus device Discrete Output data integration A user can functionally “wire” the output from a discrete process or control value producing ProcessLogix function block like Device Control to the input of a Discrete Output block in a fieldbus device residing on an H1 link. The Fieldbus Library Manager (FLM) included in the R400 Control Builder makes this possible.
2-16 Integrating Fieldbus into Rockwell Automation Logix System Fieldbus Discrete Output data manipulation When the DO[n] from the Device Control (DEVCTL) function block is wired to the CAS_IN_D input for a fieldbus Discrete Output function block, the Control Builder automatically creates a CEE output agent to handle the discrete output to the fieldbus block. The block-like output agent maps the ProcessLogix DO[n] with status parameter to the fieldbus data structure (DS-66) of the CAS_IN_D parameter.
Integrating Fieldbus into Rockwell Automation Logix System 2-17 • Discrete process output from the FIM with backcalculation feedback. Bit types 5 and 6 described in Table 2.B support publish/subscribe communications in Cascade mode or client/server communications in Remote Cascade mode. And, the analog values can also be used in the Remote Out mode. Fieldbus also supports direct device-to-device (peer-to-peer) publish/subscribe connections independent of the FIM.
2-18 Integrating Fieldbus into Rockwell Automation Logix System The status byte structure consists of a 2-bit quality, most significant bit, field; a 4-bit substatus field; and a 2-bit limits, least significant bit, field. The following table provides a breakdown of bit assignments for general reference. The value of the quality field determines the applicable substatus field indication. Table 2.
Integrating Fieldbus into Rockwell Automation Logix System Control Mode Interaction 2-19 Fieldbus Block Modes Versus Processlogix Modes Every fieldbus function block including Resource and Transducer blocks contain the MODE_BLK parameter. This structured parameter consists of the Actual, Target, Permitted, and Normal modes. Refer to About Modes of Operation on page 1-8 for descriptions of the eight modes.
2-20 Integrating Fieldbus into Rockwell Automation Logix System Control Mode Priorities and Indications Table 2.E shows the 2-character and 4-character mode indications to be used in operating displays and lists the mode priorities based on several interpretations. The Priority Order interpretation is based on the Out-of-Service mode being serviced over all others.
Integrating Fieldbus into Rockwell Automation Logix System 2-21 While every block type or block instance does not need to support all eight modes, all eight indicator bits are present in the database. The mode bit assignments are listed in Table 2.F. Table 2.
2-22 Integrating Fieldbus into Rockwell Automation Logix System ProcessLogix also ignores the following illegal mode combinations as defined by the Fieldbus Foundation. • If ROut is set, RCas may not be set. If it is set, it will be ignored. • The Auto and Man bits must always be of opposite states. If neither Auto nor Man or both are set, and the ROut, RCas, or Cas mode is set, Auto mode will be assumed with Man cleared.
Integrating Fieldbus into Rockwell Automation Logix System 2-23 Display indications and mode calculation The fieldbus mode indications for actual mode and composite actual/target modes will appear in the following formats on Station displays as shown in Table 2.H. Table 2.H Fieldbus mode indications Format Description Examples a Satisfied in mode a; actual same as target. OOS, MAN, AUTO, CAS, RCAS, ROUT a (t) In mode a; not satisfied in higher target mode t.
2-24 Integrating Fieldbus into Rockwell Automation Logix System Link and Block Schedules Link Active Scheduler (LAS) All links must have a Link Active Scheduler (LAS). The LAS operates at the data link layer as the bus arbiter for the link. It dynamically provides the following functions. • Recognizes and adds new devices to the link. • Removes non-responsive devices from the link. • Distributes Data Link and Link Scheduling time on the link.
Integrating Fieldbus into Rockwell Automation Logix System 2-25 Link Schedule The Link Schedule is the overall schedule for the link. It includes both the link data transfer and the device function block execution schedules. An independent Link Schedule is provided for the FIM interface port for each link. A backup Link Schedule is provided for all Link Master capable devices on the link.
2-26 Integrating Fieldbus into Rockwell Automation Logix System Function block execution schedule The function block execution schedule is derived from the portion of the link schedule that deals with starting the execution of each function block or FB_START indications. The link schedule provides only those entries that pertain to the blocks residing in a given fieldbus device. While device function blocks may be synchronized to the link schedule, it is not a Foundation Fieldbus mandated feature.
Integrating Fieldbus into Rockwell Automation Logix System 2-27 In general, the calculation of actual mode and the use of actual mode in the algorithm accounts for the status of critical inputs. 4. Calculate output parameters in the backward path. This phase applies only to output blocks and calculation blocks designed for use in a cascade path.
2-28 Integrating Fieldbus into Rockwell Automation Logix System Tags, Addresses, and Live List Tag and address assignments Before a fieldbus device can actively join a network it must be assigned a name and data link address. Device names are system specific identifiers called physical device tags (PD_TAG). The PD_TAGs may be assigned by the vendor or through the System Management Kernel (SMK), normally in an off-line configuration environment so devices without tags are kept off the operational network.
Integrating Fieldbus into Rockwell Automation Logix System 2-29 Live List and Uncommissioned Devices FOUNDATION Fieldbus defines a live list as a 32-byte bitstring (256 bits) where each bit represents an address of the fieldbus network. A set bit at a particular bit number means that a device is present at that address. The LAS of the network owns the live list and maintains it as part of its operation. The FIM constantly monitors the live list for each fieldbus link or device connected to it.
2-30 Integrating Fieldbus into Rockwell Automation Logix System Foundation Fieldbus Performance Foundation Fieldbus, FF, is a very powerful network providing both communication and distributed control capability. However, fast response is not one of its great capabilities. The screen capture below reflects the time allocated for 18 function blocks to publish their outputs on Fieldbus. The average time is about 40 ms. per published value.
Integrating Fieldbus into Rockwell Automation Logix System 2-31 • Some pressure transmitters will read their transducers and create a new floating point digital readings of the PV every 100 ms. • That value can only be read every 40 to 50 milliseconds because of the Fieldbus data rate, and of the Fieldbus protocol. • The data rate is 31.25 Kbps, or 31 bits per millisecond. Very very slow by comparison with ControlNet or Ethernet. • A minimum Fieldbus message uses 99 bits. A minimum response uses 150 bits.
2-32 Integrating Fieldbus into Rockwell Automation Logix System Notification Scheme Fieldbus versus ProcessLogix Alarm Priorities The Fieldbus alarms are closely integrated with the existing ProcessLogix notification system. The ProcessLogix Server handles FIM alarms in the same way it handles Control Processor ones. But, the fieldbus devices themselves own their alarm data and generate the alarms, clears, and events. Fieldbus devices use 0 to 15 as numeric priorities for alarm reporting.
Integrating Fieldbus into Rockwell Automation Logix System 2-33 Fieldbus Alarm Conditions Fieldbus devices provide both process and device related alarms. The fieldbus devices themselves own their alarm data; generates and clears the alarms and events. The process alarms are associated with process variable conditions and they are reported as process alarms into ProcessLogix.
2-34 Integrating Fieldbus into Rockwell Automation Logix System Table 2.
Integrating Fieldbus into Rockwell Automation Logix System 2-35 Alert Object Formal Model The alert object allows block alarms and events to be reported to a device responsible for alarm management. Class: Alert Subclass of: Root Attributes: 1. (m) (r) DD Member Id 2. 2. (m) (Key) Index 3. 3. (m) (r) Data Type 3.1 (m) (r) Meta Type = RECORD 3.2 (m) (r) Type Name = Alert 4. (m) (r) Sub-index 4.1 (m) (r) Block Index - Unsigned16 4.2 (m) (r) Alert Key - Unsigned8 4.3 (m) (r) Standard Type - Unsigned8 4.
2-36 Integrating Fieldbus into Rockwell Automation Logix System Table 2.L Attribute Definitions Attribute Definition DD Member Id A unique number which identifies the alert. This number will be assigned as part of the development of the Device Description (DD). A DD member Id is assigned if an object is defined as part of a structure. A value of zero (0000) will be used for the DD member Id if the object is not part of a structure. Index The location of the alert in the OD.
Integrating Fieldbus into Rockwell Automation Logix System 2-37 Table 2.M Standard type valid values Valid Values Meaning 11 UPDATE - Link associated with function block 12 UPDATE - Trend associated with block Message type will be enumerated in the following manner: 0= 1 = Event Notification 2 = Alarm Clear 3 = Alarm Occur The alert object contains information from an alarm or update event object, which is to be sent in the notification message.
2-38 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757-UM006A-EN-P - May 2002
Chapter 3 1757-FIM Planning Considerations Reference Publications Please refer to the following Rockwell Automation publications for general planning details and installation considerations for the ProcessLogix system in general. Table 3.A Publication References Publication Name Publication Number ProcessLogix R400.0 Installation and Upgrade Guide 1757-IN040B-EN-P ProcessLogix R400.
3-2 1757-FIM Planning Considerations Installation declaration ATTENTION ! Environment and Enclosure This equipment is intended for use in a Pollution Degree 2 industrial environment, in overvoltage Category II applications (as defined in IEC publication 60664-1), at altitudes up to 2000 meters without derating. This equipment is considered Group 1, Class A industrial equipment according to IEC/CISPR Publication 11.
1757-FIM Planning Considerations 3-3 FIM and I/O module allowance Be sure your ProcessLogix System Fieldbus and I/O requirements do not exceed the capacities listed in the following table. In terms of processing allocations, the FIM is the equivalent of three I/O modules. Table 3.B Component Total Per Controller Total Per Server Maximum number of FIMs plus I/O modules divided by three (including local and remote chassis I/O and rail I/O).
3-4 1757-FIM Planning Considerations Fieldbus wiring selection and calculation The preferred cable for connecting fieldbus devices is #18 AWG (0.8mm2) shielded, twisted pair wire. It is important to calculate how the planned topology for your fieldbus segment, selected wiring, supplied power and intended mix of fieldbus devices may impact the overall performance of a fieldbus network. The original Fieldbus specification allows using twisted pair wiring, which is commonly used for 4-20 ma transmitters.
Chapter 4 Configurating the 1757-FIM Before You Start Table 4.A Where do you begin? 1 Question: If your answer is: If your answer is What do you know about Control Builder? Nothing. Read the Functional Overview section in the Control Building Guide or locate the topic in Knowledge Builder. This section shows you how to launch the application and complete the Server login. Yes, you can skip this section. Do you know how to configure a Control Processor Module? No.
4-2 Configurating the 1757-FIM Figure 4.
Configurating the 1757-FIM Configuring Fieldbus Components In a Control Strategy 4-3 About ProcessLogix control strategy configuration You use ProcessLogix's Control Builder application to configure a process Control Strategy using predefined function blocks. Since Fieldbus Foundation had been functionally integrated with the ProcessLogix system, the Control Builder enables the inclusion of fieldbus related Function Blocks for easy integration of fieldbus functions within the overall Control Strategy.
4-4 Configurating the 1757-FIM Example Application and Control Strategy for Procedural Reference Figure 4.2 shows a process feed and recycle line application being controlled through a ProcessLogix control strategy loaded in a Control Process Module (CPM) and associated Control Execution Environment (CEE). This sample application and control strategy will be used for reference to illustrate the applicability of functions in the following procedures Figure 4.
Configurating the 1757-FIM 4-5 The application involves controlling the level of a 2000 gallon surge tank with a steady-state 100 gallon per minute (gal/min) process feed and recycle line. A fieldbus approved smart pressure transmitter is being used to monitor the level in the surge tank. A fieldbus approved valve positioner is being used to regulate the control valve in the process feed line.
4-6 Configurating the 1757-FIM System Management Timers T1, T2, and T3 are the System Management Timers. The units are 1/32000 of a second, so 96000 gets 3 seconds. T1 T1 specifies how long the 1788-CN2FF waits for an answer to a System Management message, such as Set PD Tag. The time needs to include the time to acquire the Token for Unscheduled Transmission, transmit the message, remote node to process the message, remote node to acquire Token, transmit reply.
Configurating the 1757-FIM 4-7 Since the CN2FF only occasionally polls the addresses that have shown no previous activity (called the Slow Poll List), it takes relatively longer to detect a node at a new address than to pass the Token to a known node at an active address. The sequence is sort of like: Pass Token 17 Pass Token 18 Pass Token 19 Pass Token 20 Probe Node 32 Pass Token 17 Pass Token 18 Pass Token 19 Pass Token 20 Probe Node 33 etc.
4-8 Configurating the 1757-FIM ACSYNCINTR This is the period of time between Application Clock synchronization messages. Application Clock synch messages are used to coordinate the 'application clock' among the various nodes. The Application Clock is used by each Node to begin execution of its Function Blocks at the Scheduled Time.
Configurating the 1757-FIM 4-9 Adding Fieldbus Interface Module to Project Use the following procedure to add a Fieldbus Interface Module block to the Project tab in Control Builder. This also adds two Link blocks for the two H1 fieldbus links that can be associated with this FIM. TIP You can configure a FIM block in the Control Builder Project tab without the FIM hardware installed.
4-10 Configurating the 1757-FIM 4. Leave the CB assigned Name FIMxx, where xx equals the next unique sequential number. Or, enter a unique name of up to 16 characters. 5. In the Network field, select the communications medium your ProcessLogix system uses. Ethernet or ControlNet, ControlNet is the default selection. 6. In the Driver Name field, select the correct communications driver. TIP The communications driver must be installed and configured for it to be included in the dropdown list. 7.
Configurating the 1757-FIM 4-11 12. Leave all other fields on the Main tab at their defaults, as these are the only valid values at this point. Click the Statistics tab. Data is only present in these fields when the FIM/LINK is loaded and communicating with the system. 13. Click the Server Parameters Tab. 14. Leave the Point Detail Page and Control Level fields at their default. The Associated Display and Group Detail Page are not required to complete the configuration, but can be entered if known.
4-12 Configurating the 1757-FIM 15. Click OK. The FIM icon is added to the Project tab. The FIM also includes icons for the two H1 fieldbus links that it supports. TIP Refer to the 1757-FIM as a controller because the module can function independently, without a 1757-PLX52. Checking link configuration Use the following steps to check the link configuration of the links associated with a given FIM block. This procedure assumes that you have configured a FIM block in the Project tab of Control Builder.
Configurating the 1757-FIM 1. Double-click the link icon 4-13 . The Link Block Parameters window opens. 2. Leave the CB assigned name LINKxx, where xx equals the next unique sequential number assignment. Or, enter a unique number of up to 16 characters. 3. In the Description field, enter a description of up to 24 characters. This text appears in applicable detail and group displays associated with this block.
4-14 Configurating the 1757-FIM 4. Click the System Management tab. ATTENTION ! Do not change the default value settings for the active parameters in this window unless you are familiar with tuning the performance of fieldbus links. 5. In the Step Time Preset (T1) field, either leave the default value of 96000, or enter a new value. This is the preset value for the System Management step timer in 1/32 millisecond increments. 6.
Configurating the 1757-FIM 4-15 8. In the Local Clock Time Offset (LOCTIMDIFF) field, either leave the default value of 0, or enter a new value. This value is used to calculate the local time from the Curr App Clock Time (CURTIME) in the number of +/- 1/32 millisecond increments to add to the clock to obtain local time. 9. In the App Clk Sync Interval (ACSYNCINTR) field, either leave the default value of 5, or enter a new value. This value is the interval in seconds between time messages on the link.
4-16 Configurating the 1757-FIM 12. Click the Application tab. 13. In the Device Name (DEVNAME) field, either leave the default name, or enter a new name of up to 33 characters. TIP The remaining parameters on this tab define the Application Relationships that determine how Application Processes communicate with each other. Leave the default values for these parameters, then revisit them in the Monitoring tab when the FIM/LINK is communicating with the system. 14.
Configurating the 1757-FIM 4-17 15. Leave all other fields with their default displays and click OK. 16. Repeat these steps for another Link, as required. Making a Fieldbus Device Template from a Vendor's DD Use the following steps to add a template to the Control Builder Library using the Fieldbus Library Manager utility included with ProcessLogix R400.0 Engineering Tools and vendor supplied Device Description (DD) files, version 4.01 or later.
4-18 Configurating the 1757-FIM 1. Click Start ⇒Programs ⇒ProcessLogix Engineering Tools ⇒Fieldbus Library Manager. The Fieldbus Library Manager (FLM) login window opens. 2. In the Server Name field, select the Server where you want the device template stored. The device template is stored in the Engineering Repository Database (ERDB) on the Server. 3. Enter your login password in the Password field. You need an access level of at least Engineer to make a template.
Configurating the 1757-FIM 4-19 6. In the FLM window, click File ⇒Open Device. The Select Driver window opens. 7. In the Device Release Directory field, select the device you want to make a template for in the Device List box. You can use either the drop-down menu or Browse to select the device. 8. Click OK. The device data begins to load to the FLM.
4-20 Configurating the 1757-FIM 9. After loading is complete, double-click the function block you want to view or edit under the device directory on the left side of the FLM window. Block parameters are displayed in table format on the right side of the FLM window. TIP By keeping default values, you may use the same template for like vendor devices used in multiple locations in your application. You can make adjustments to selected device parameters through Control Builder configuration access.
Configurating the 1757-FIM 4-21 10. To edit a given parameter value, double-click in the desired cell, or right-click the field and select edit. The edit field is activated. 11. Enter the desired value and press Enter. 12. Repeat Steps 9, 10, and 11 to edit parameters for your application, as required. 13. Click File ⇒Build Device Template ⇒From Current Device.
4-22 Configurating the 1757-FIM 16. (Optional) Launch Control Builder to confirm that the device template is listed in the Rockwell Automation directory in the Library tab. Making a fieldbus device template from existing definition (.DEF) files Use the following procedure to make a device template from definition files that have been previously saved to a folder on the Server's hard drive. The default folder location is: C:\Honeywell\tps50\system\bin\er\ffdevices.
Configurating the 1757-FIM 4-23 password, if required. The password is tied to the operator security for Station. 4. Click OK. 5. Click File ⇒Build Device Template ⇒From Existing .DEF Files. The Select Device Template Definition Files dialog box opens. 6. Click Browse to navigate to the directory containing the saved definition (.DEF) files. The default directory is: C:\Honeywell\tps50\system\bin\er\ffdevices. 7. Click OK. 8. Click OK to initiate the template build from selected .DEF files. 9.
4-24 Configurating the 1757-FIM 11. Repeat Steps 5 to 10 to make other device templates. 12. (Optional) Launch Control Builder to confirm that the device template is listed in the Rockwell Automation directory in the Library tab. Adding a Fieldbus Device to Project Use either method that follows to add a fieldbus device from a Library tab directory to the Project tab.
Configurating the 1757-FIM 4-25 The Name New Function Block(s) dialog box opens. 3. Leave the default name that appears in the Destination column or enter a new name of up to 16 characters. 4. Click Finish. A device icon with the given name is created in the Project tab. 5. Repeat this method to add other devices.
4-26 Configurating the 1757-FIM Method 2: File Menu 1. Click File ⇒New ⇒FFDevices ⇒Rockwell Automation ⇒(desired device name)-Fieldbus Device. The Block Parameters window opens. 2. Leave the default Name or enter a desired name of up to 16 characters. 3. Click OK. A device icon with the given name is created in the Project tab. 4. Repeat this method to add other devices.
Configurating the 1757-FIM 4-27 Assigning a Device to a Link in Project Use the following procedure to assign a device to a Link associated with the applicable FIM in the Project tab. 1. Click Tools ⇒Assign. Or, click the assign button toolbar. in the The Controller Assignments window opens. 2. Click the Devices tab. 3. Click the device you want to assign to a Link to highlight it. 4. Confirm that the desired Link is selected in the Select Link list box. 5.
4-28 Configurating the 1757-FIM 7. Repeat the procedure to assign other devices. TIP An alternate method to the following procedure is to drag and drop the device to the applicable Link in Project. Checking Device Configuration Use the following procedure to check the configuration of a selected fieldbus device in the Project tab. This procedure assumes that the device has been assigned to a Link.
Configurating the 1757-FIM 4-29 1. Double-click the device icon in the Project tab. The Block Parameters window opens. 2. In the Name field, leave the default name or enter a unique name of up to 16 characters. 3. In the Description (DESC) field, enter the desired description of up to 59 characters, or leave it blank. 4. In the Device Network Node Address (ADDR) field, leave the default address. 5. In the Device Identification (DEV_ID) field, enter the manufacturer’s ID for the device, if known.
4-30 Configurating the 1757-FIM 7. The Device State (DEVSTATE) parameter is only active in the Monitoring tab after the FIM/LINK/DEVICE is loaded and communicating with the system. 8. Click the System Management tab. ATTENTION ! Do not change the default value settings for the active parameters in this window unless you are familiar with tuning the performance of fieldbus links. In most cases, the parameter values will mirror those configured for the Link.
Configurating the 1757-FIM 4-31 This is the preset value for the System Management set address wait timer in 1/32 millisecond increments. 12. In the Local Clock Time Offset (LOCTIMDIFF) field, either leave the default value of 0, or enter a new value. This value is used to calculate the local time from the Curr App Clock Time (CURTIME) in the number of +/- 1/32 millisecond increments to add to the clock to obtain local time. 13.
4-32 Configurating the 1757-FIM 16. The parameters on the Network Management tab are only accessible in the Monitoring tab with the FIM/LINK communicating with the system. Click the Server tab. IMPORTANT If you have a Distributed Server Architecture (DSA), you must enter the Control Area assignment for this Server (area code assignments are made through Station). If you do not have a DSA, you can skip this field, if Areas is not enabled through Station. 17.
Configurating the 1757-FIM 4-33 Creating Control Module for Sample PID Loop The following procedures are optional tutorials on creating a CM to provide the PID control loop function for the example application shown in Figure 4.2. They provide a general reference for including fieldbus function blocks with ProcessLogix function blocks in a control strategy.
4-34 Configurating the 1757-FIM 2. Double-click the CONTROLMODULE icon . A new control module opens. 3. Click Tools ⇒Configure Module Parameters. The Control Module Block Parameters window opens. 4. In the Name field, enter CM101. 5. In the Description field, type Surge Tank Control Loop. 6. In the Eng. Units field, type Percent. 7. In the Keyword field, type Recycle.
Configurating the 1757-FIM 4-35 8. Click the Enable Alarming Option check box, if it is not already selected. 9. In the Execution Order in CEE field, enter 30 (the smaller the number, the earlier the module executes in the cycle). ATTENTION ! The Execution Order in CEE parameter only applies to contained ProcessLogix function blocks in CM’s that are assigned to a CEE. It has no affect on contained fieldbus blocks and it is disabled, if the CM is assigned to a Link. 10.
4-36 Configurating the 1757-FIM Adding blocks to CM for sample loop 1. In the Project tab, expand the FIM down to the device block level by clicking the left of FIM, then LINK_S101, then ST101. 2. Click and drag the AI block to CM101 chart. An FF AI block is added to the CM101 chart. 3. In the Library tab, expand the DATAACQdirectory by clicking the Publication 1757-UM006A-EN-P - May 2002 .
Configurating the 1757-FIM 4. Click and drag the DATAACQ block chart. 4-37 to the CM101 A DATAACQ block is added to the CM101 chart. 5. In the Library tab, expand the REGCTL directory by click the .
4-38 Configurating the 1757-FIM 6. Click and drag the PID block to the CM101chart. The PID block is added to the CM101 chart. 7. In the Project tab, expand the LX14_101 by clicking the Publication 1757-UM006A-EN-P - May 2002 .
Configurating the 1757-FIM 8. Click and drag the AO block 4-39 to the CM101 chart. The AO block is added to the CM101 chart. Configuring AI block for sample loop 1. In the CM101 chart, double-click the AI block. The AI Block Parameters opens. 2. In the Name field, type AI_LEVEL. 3. In the Description field, type Input for Tank 106 Level.
4-40 Configurating the 1757-FIM 4. Leave the Execution Order in CM at the default of 10 (the smaller the number the sooner the block executes within the CM cycle). ATTENTION ! The Execution Order in CM parameter defines the order of execution and publication for all blocks contained in the CM. For contained fieldbus blocks, this parameter combines with the CM’s Execution Order in Link parameter to determine how the fieldbus block participates in the Link Active Schedule. 5.
Configurating the 1757-FIM 4-41 Configuring DATAACQ block for sample loop 1. In the CM101 chart, double-click the DATAACQ block. TIP The DATAACQ is a 1757-PLX52 function as well as a Foundation Fieldbus function, with ControlBuilder you can mix both in a control strategy. The DATAACQ Block Parameters window opens. 2. In the Name field, type DATAACQ_101. 3. In the Description field, type Level Input Conditioning. 4. In the Eng. Units field, type Percent. 5.
4-42 Configurating the 1757-FIM 6. Click the Alarms tab. 7. Enter or select the following values for these Alarm Limits: Alarm Limit Trip Point Priority Severity PV High High 85 URGENT 15 PV High 70 HIGH 8 PV Low 25 HIGH 8 PV Low Low 15 URGENT 15 Leave all other Alarm Limits at their default values. 8. Click the Block Pins tab.
Configurating the 1757-FIM 4-43 9. Select PVLLALM.FL in the Parameters list. 10. Verify that the Pin Position is Output and Top/Bottom. 11. Click Add. PVLLALM.FL is added to the Output-Bottom list. 12. Select PVLOALM.FL in the Parameters list. 13. Verify that the Pin Position is Output and Top/Bottom. 14. Click Add. PVLOALM.FL is added to the Output -Bottom list. 15. Select PV in the Output-Bottom list. 16. Click Remove. PV is removed from the Output-Bottom box. 17. Select PV in the Parameters list.
4-44 Configurating the 1757-FIM 19. Click Add. PV is added to the Output-Right box. 20. Click OK to close the window and save the configuration. Configuring PID block for sample loop 1. In the CM101 chart, double-click the PIDA block. The PID Block Parameters window opens. 2. In the Name field, enter PID_101. 3. In the Description field, enter Recycle Loop Controller. 4. In the Engineering Units field, enter Percent. 5. In the Normal Mode field, select AUTO. 6.
Configurating the 1757-FIM 4-45 7. Click the Algorithm tab. 8. Leave the Control Equation Type field at the default of EQA. 9. In the Control Action field, select DIRECT. 10. Click the Set Point tab.
4-46 Configurating the 1757-FIM 11. In the SP field, enter 50. 12. Click OK to close the window and save the configuration. Configuring AO block for sample loop TIP This is a function block that was loaded using the Fieldbus Library Manager and the DD from the Flowserve Actuator. 1. In the CM101 chart, double-click the AO function block. The AO Block Parameters window opens. 2. In the Name field, enter AO_FLOW. 3. In the Description field, enter Flow Control Output. 4.
Configurating the 1757-FIM 4-47 Wiring blocks in CM101 for sample loop 1. In CM101 chart, double-click the OUT_VALUE pin on the AI_LEVEL block. The Pin is highlighted and cursor changes to cross-hairs . 2. Move cursor over the P1 pin for the DATAACQ block and click. A wire is drawn between the pins, the P1 pin is highlighted, and the cursor reverts to its normal shape. 3. Repeat Steps 1 and 2 to wire the DATAACQ_101 PV pin to the PID_101 PV and the PID_101 OP to the AO_FLOW CAS_IN.VALUE.
4-48 Configurating the 1757-FIM 4. Close the CM101 chart and click Yes to save changes. Adding parameter connectors for sample loop interlocks This procedure assumes that a CM named CM102 will be created for the pump control loop in the example application. The CM102 will include a standard Device Control block and Discrete I/O Channel blocks to start and stop the pump as shown in Figure 4.4. Figure 4.4 Sample CM with Device Control block for pump control in sample loop. 1.
Configurating the 1757-FIM 4-49 3. Parameter connection box appears. 4. Click Browse . The Point Selector window opens. 5. In the Point Names list, scroll to find CM101 DATAACQ_101 and select it. The Parameters list is populated with applicable parameters. 6. In the Parameters list, scroll to find PVLLALM.FL and select it. PBLLALM.FL is inserted into both the Parameters field and the Selected Item field. 7. Click Select. The parameter name is inserted into the parameter connection box.
4-50 Configurating the 1757-FIM 8. Click the IN pin on the FTRIGA block. Double-click the area adjacent to the pin. The parameters connection box appears. 9. Repeat the previous steps to select DATAACQ_101.PVLOALM.FL as the parameter name. 10. Close the Point Selector dialog box. See Figure 4.5 for the completed CM102 with parameter connections. Figure 4.5 Completed CM102 with parameter connections for sample loop interlocks.
Configurating the 1757-FIM Loading Components Online 4-51 About load operations The ProcessLogix system provides the ability to build Foundation Fieldbus control strategies offline, online or without being connected to the field components that will translate the strategy into the actual control operations. The process of transferring the Control Strategy to the “live” working components in the field is called the load operation.
4-52 Configurating the 1757-FIM About the new load dialog box Figure 4.7 shows a sample Load Dialog box invoked for a load with contents operation for a FIM. It provides a brief description of the dialog box features for quick reference. Figure 4.
Configurating the 1757-FIM 4-53 General load considerations The following are some general load considerations to keep in mind, when you are loading fieldbus components. In most cases, the load dialog box will quickly guide you through the load operations and will alert you to potential system problems. Table 4.B If you are loading... Consider this... A FIM. Be sure ALIV does not appear in the LED display on the front of the FIM.
4-54 Configurating the 1757-FIM Un-initialized State In the un-initialized state, a fieldbus device has neither a physical device tag nor a node address assigned by a master configuration device. The only access to the device is through system management, which permits identifying the device and configuring the device with a physical device tag. Initialized State In the initialized state, a fieldbus device has a valid physical device tag, but no node address has been assigned.
Configurating the 1757-FIM 4-55 Loading a FIM and its Links The following procedure outlines the typical steps used to “load” a FIM through the Project tab in Control Builder. It assumes that the FIM and its associated RTP are installed and capable of communicating with the system. 1. Verify that the OK LED on the front of the FIM is flashing and the numbers 1 and 2 are sequencing in the left-hand LED on the front panel display.
4-56 Configurating the 1757-FIM 3. Click Tools ⇒Load. The Load Dialog window opens. TIP The associated FIM Links are included with a FIM load even if the selected action is Load instead of Load with Contents. We suggest just loading the FIM without all of its contents first to be sure communications paths are working. 4. Verify that a check appears to the left of the FIM listed in the Load? column. 5. Click OK.
Configurating the 1757-FIM 4-57 6. After the load completes, click the Monitoring tab. The Monitoring tab opens. 7. Verify that the FIM icon appears in Monitoring tab. 8. Click the to expand the FIM. 9. Verify that the LINK icons appear under the FIM. Loading Link contents or fieldbus device Use the following procedure to load the Fieldbus link contents or fieldbus devices. It assumes that the FIM has been loaded and the fieldbus devices are installed and powered on the Links. 1.
4-58 Configurating the 1757-FIM 2. Click Tools ⇒Load With Contents. The Load window opens. TIP If you want to load just a Fieldbus device, click the device icon and click Tools->Load. Use LINK/Load With Contents so you can load more than one device at a time. 3. Verify that checkmarks appear in the LINK and Device checkboxes listed in the Load? column. If you do not want to load a given device, just click it to remove the checkmark from its checkbox.
Configurating the 1757-FIM 4-59 4. To load all, leave the Partial Load checkboxes selected for all blocks. 5. To change the Post Load State for selected components, click the appropriate Post Load State row. The dropdown menu opens. 6. Select the appropriate state.
4-60 Configurating the 1757-FIM 7. Click OK. The load is initiated, shown by the Load window. TIP If errors are detected, they will be listed and you will prompted to select whether or not you want to continue the load with errors. It is a good idea to note the errors and abort the load (close), so you can go back and correct the errors before completing the load. 8. After the load is complete, click the Monitoring tab. 9. Verify that the Link is activated. 10.
Chapter 5 Operating the 1757-FIM Monitoring Fieldbus Functions Through Station Displays Using Station Detail displays The ProcessLogix Server Station application includes pre-configured Detail displays for the FIM, Link, device and fieldbus function blocks. These displays are the default entries for the Point Detail Page parameter on the Server Parameters tab of the configuration form.
5-2 Operating the 1757-FIM Using Station Event Summary display Like the Detail displays, the Alarm and Event Summary displays support the integration of fieldbus generated notifications and events. It is integrated with ProcessLogix component data and is for the most part self-explanatory. Figure 5.2 shows a typical Event Summary display that includes FIM, Link, and Device indications. Use this display to get a quick review of recent actions that have been initiated within the system. Figure 5.
Operating the 1757-FIM 5-3 TIP You can initiate this same function through the corresponding Detail display in Station. 1. In the Monitoring tab, click the LINK icon. 2. Click Toggle State in the toolbar. The Change State window opens. 3. Click Yes. This initiates the state change. The icon changes from green to blue. The FIM is only inactivated when both Links are inactivated (shown below).
5-4 Operating the 1757-FIM 4. With LINK icon selected, click the Toggle State button toolbar. in the The Change State window opens. 5. Click Yes. This initiates the state change. The icon changes from blue to green. Monitoring/Interacting with given component/block Once you download a FIM and its contents, you can use the Monitoring tab to interact with the components including the function blocks in the fieldbus devices. 1.
Operating the 1757-FIM 5-5 Checking fieldbus device functional class Use the following procedure to check and change, if necessary, the functional class of the fieldbus device. 1. Double-click the device icon. The Device Configuration Parameters window opens. 2. Click the Network Management tab. 3. Scroll to find the DL Operational Functional Class field.
5-6 Operating the 1757-FIM 4. Verify that the functional class is appropriate for the device, Basic or Linkmaster. TIP The FIM is the primary Linkmaster for both Links. If you designate a device as a “backup” Linkmaster, be sure it has the capacity to handle the Link Active Schedule. Otherwise, you may have to reset the device and restart it to restore operation if the LAS is too large for it to handle. 5. If the functional class is not correct, select the appropriate functional class.
Operating the 1757-FIM 2. Click the 5-7 to expand the Link. 3. Double-click the uncommissioned device icon . The LINK Parameters window opens. 4. Review the device details. TIP The device manufacturer assigns tag and device IDs. It is a good idea to record the device’s Tag name and Device ID for future reference.
5-8 Operating the 1757-FIM 5. If a template exists, go to the procedures in Chapter 4 to create, assign, configure, and load the device. If a template does not exist, create one using the vendor’s DD files and the Fieldbus Library Manager, as described in the Chapter 4. A template must exist before a device can be integrated into the system. TIP It is possible that the uncommissioned device may have an earlier version of the vendor’s software (Device Rev).
Chapter 6 1757-FIM General Maintenance, Checkout, and Calibration Adding, Removing and Replacing Components About Removal and Insertion Under Power WARNING ! IMPORTANT When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.
6-2 1757-FIM General Maintenance, Checkout, and Calibration General Procedure ATTENTION ! Publication 1757-UM006A-EN-P - May 2002 We recommend that you proceed with extreme caution whenever replacing any component in a control system. Be sure the system is offline or in a safe operating mode. Component replacements may also require corresponding changes in the control strategy configuration through Control Builder, as well as downloading appropriate data to the replaced component.
1757-FIM General Maintenance, Checkout, and Calibration 6-3 The direct replacement of a FIM of the same kind is just a matter of disconnecting the RTP cable, removing the existing component, installing a new one in its place, and connecting the RTP cable. You may also have to load its “personality” image firmware before it can become fully operational.
6-4 1757-FIM General Maintenance, Checkout, and Calibration 2. Click Load Firmware. The Device Firmware Upgrade window opens. 3. Click Upgrade. The Open window opens. 4. Locate and select the vendor’s upgrade file. 5. Click Open. This initiates the firmware upgrade. 6. After the firmware upgrade is complete, wait for the device to rejoin the network. This may take up to 3 minutes. 7. When the device has rejoined the network, click the the window. close 8.
1757-FIM General Maintenance, Checkout, and Calibration 6-5 9. To automatically match the template, click in the Tag field to expose the Match button. Click it to initiate enhanced matching functions. 10. If a template exists, use The procedures in Chapter 4 to include the device in the Control Strategy. If a template does not exist, get the DD file for the device and use the Fieldbus Library Manager to create one. Refer to Making a Fieldbus Device Template from a Vendor's DD on page 4-17. 11.
6-6 1757-FIM General Maintenance, Checkout, and Calibration Table 6.A LED Definitions If Module Health LED is: And, 4-Character Display shows: The FIM is: Flashing Red/Green TEST Running its self-test. Flashing Green/Off BOOT Initiating its startup or boot sequence. ALIV in its ALIVE state and ready for its Personality Image load. LOAD In the midst of a firmware load sequence. RDY In its READY state and ready for its Boot image load.
Chapter 7 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device This chapter describes: • the blocks in the linking device • configuring the linking device to access the AI, AO, DI, DO function blocks on the Fieldbus network from ControlNet • attributes of the created ControlNet objects, assembly objects, alarm handling • ControlNet connection details Blocks in the Linking Device The linking device is similar to an I/O subsystem.
7-2 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device Analog Inputs This section describes configuration of the linking device to access any analog value (and status) in a Fieldbus device. It also describes the attributes of the created ControlNet analog input object. The linking device contains two of MAI block instances on each Fieldbus channels. Each instance of the MAI block is the software equivalent of an analog input module in an I/O subsystem.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device 7-3 ControlNet, you must choose different MAI blocks as shown in the Figure 7.2. Figure 7.2 Sample Multiple Macrocycle MAI Configuration You do not have to connect to all the channels in an MAI block instance before using another instance. You do not have to use the channels in order. That is, you may use channels CN_A0 and CN_A5 and not use any of the others. As shown in the lower loop of Figure 7.
7-4 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device ControlNet Analog Input Objects The linking device creates an instance of a ControlNet AI object for every wired channel in the MAI block instances. Each instance of the ControlNet AI object has the attributes and access rules shown in Table 7.A. Table 7.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device 7-5 and Confirmed after the condition causing the alarm is corrected. When the function block detects the alarm condition is no longer present, the alarm is said to be CLEARED. The CLEARED state must be Confirmed when it is detected. Users of the LD use the alarm attributes to process Fieldbus alarms. Each attribute corresponding to a process alarm has the three alarm-related bits as shown in Figure 7.3. Figure 7.
7-6 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device blocks. The linking device assigns a tag to each MAO block in the form CNetMacIdxx_AO_Modulei-j, where xx is the ControlNet network address, i is the Fieldbus channel number, and j is the module or instance number. Configuration of Analog Outputs The NI-FBUS Configurator lists all the devices and the function blocks in each device in its browse window.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device 7-7 Figure 7.5 Sample Multiple Macrocycle AO Configuration You do not have to connect to all the channels in an MAO block instance before using another instance. You do not have to use the channels in order. That is, you may use channels CN_OUT_A3 and CN_OUT_A5 and not use any of the others. As shown in the lower loop of Figure 7.5, you can connect the MAO block to any parameter that is a float value and status combination.
7-8 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device ControlNet AO object has the attributes and access rules shown in Table 7.B. Table 7.B ControlNet Analog Output Object Attributes Attribute Number Name Type Initial Value Access Remarks 3 Value Float Set 0 This is written from the ControlNet side. 4 CNStatus Boolean Set Bad ControlNet status. 0-Good; 1-Bad.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device Discrete Inputs 7-9 This section describes configuration of the linking device to access any discrete value (and status) in a Fieldbus device. It also describes the attributes of the created ControlNet discrete input object. The linking device contains one MDI block instances on each of the two channels. Each instance of the MDI block is the software equivalent of a discrete input module in a I/O subsystem.
7-10 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device ControlNet Discrete Input Objects The linking device creates an instance of a ControlNet DI object for every wired channel in the MDI block instances. Each instance of the ControlNet DI object has the attributes and access rules shown in Table 7.C. Table 7.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device 7-11 Each attribute corresponding to a process alarm has the three alarm-related bits as shown in Figure 7.7. Figure 7.7 Alarm Attribute Definition Bit Position 7 6 5 4 3 2 1 0 Value X X X X X Acknowledge CLEARED ACTIVE Bits 7-3, DON’T CARE, are undefined when read and should be ignored when performing a GET. The DON’T CARE bits should be written as 0 when performing a SET.
7-12 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device Configuration of Discrete Outputs The NI-FBUS Configurator lists all the devices and the function blocks in each device in its browse window. This includes the DO function blocks in the Fieldbus devices and the MDO function blocks in the linking device. You must connect the Fieldbus DO function blocks that will be controlled by the ControlNet controllers (or devices) to the MDO channels. Figure 7.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device 7-13 ControlNet Discrete Output Objects The linking device creates an instance of a ControlNet DO object for every wired channel in the MDO block instances. Each instance of the ControlNet DO object has the attributes shown in Table 7.D. Table 7.D ControlNet Discrete Output Object Attributes Attribute Number Name Type Access Initial Value Remarks 3 Value Boolean Set 0 This is written from the ControlNet side.
7-14 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device Alarm Handling by the HMI The linking device makes the process alarms from AI and DI function blocks visible as attributes of the created ControlNet objects, as discussed in the previous sections. Fieldbus devices generate other types of alarms; for example, they send out an alarm whenever their static configuration changes. Other function block types also generate alarms.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device 7-15 Table 7.E describes the attributes placed into the input and output assembly for each object type. Table 7.
7-16 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device MDI Blocks For each MDI block configured in the linking device beginning with the lowest numbered module, each channel that is connected to a Fieldbus function block has attributes 3, 4, and 150 placed into the required input assembly object. Each MDI requires 4 bytes in the input assembly object.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device 7-17 Figure 7.10 Sample NI-FBUS Configurator View of ControlNet Object Information Changing the Linking Device Configuration Once a configuration is created in the linking device and a PLC processor or PC is using the offsets previously defined, an addition to the configuration should not require you to change functioning code in your application.
7-18 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device resources continue to be in use. In order to remove existing objects from a configuration, you must remove the existing configuration. To accomplish this, select Download Configuration in the NI-FBUS Configurator, enable the Clear Devices checkbox in the dialog box that appears, and download a new configuration. Trends and Alarms The linking device can receive trends and alarms from connected Fieldbus devices.
Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device Tips for Connecting to a 1756-ENET Controller 7-19 Here are some general tips that might help you if you are connecting to a Fieldbus network via a 1756-ENET controller. Rockwell has demonstrated the bridging capability of Ethernet to ControlNet for years. Accessing a 1756-CN2FF that sits on ControlNet is not a problem. In RSLinx, use the Ethernet driver, TCP.
7-20 Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device Notes: Publication 1757-UM006A-EN-P - May 2002
Appendix A Standard Function Block Parameters(1) Axxx Blocks Table A.1 ACK_OPTION Classification Simple Variable Description Selects whether alarms associated with the block will be automatically acknowledged. FF Data Type Bit String Range 1: Unacknowledge Usage C/Contained Length 2 Valid Views VIEW_4 Storage Static Remarks Initial value is 0 Table A.
A-2 Standard Function Block Parameters Table A.3 ALARM_SUM Classification Record Description Detects the current alert status, unacknowledged states, and disable states of the alarms associated with the block FF Data Type DS-74 Usage C/Alarm Summary Length 8 Valid Views VIEW_1, VIEW_3 Storage Dynamic Remarks The data type summarizes 16 alerts using the following 4 elements. •1 Current •2 Unacknowledged •3 Unreported •4 Disabled Table A.
Standard Function Block Parameters Valid Views VIEW_4 Storage Static Remarks Initial value is 0 A-3 Table A.
A-4 Standard Function Block Parameters Valid Views VIEW_3 Storage Non-Volatile Remarks The data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Table A.9 BKCAL_OUT Classification Record Description The value and status required by an upper block's BKCAL_IN so the upper block may prevent reset windup and provide bumpless transfer to closed loop control.
Standard Function Block Parameters A-5 Table A.11 BKCAL_SEL_1 Classification Record Description The selector output value and status associated with SEL_1 input that is provided to BKCAL_IN of the block connected to SEL_1 to prevent reset windup. FF Data Type DS-65 Usage O/Back Calculation Output Length 5 Valid Views VIEW_3 Storage Dynamic Remarks The data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements.
A-6 Standard Function Block Parameters Table A.14 BLOCK_ALM Classification Record Description The block alarm is used for all configuration, hardware, connection failure, or system problems in the block. The cause of the alarm is entered in the sub-code field. The first alarm to become active will set the Active status in the Status attribute.
Standard Function Block Parameters Cxxx Blocks Valid Views VIEW_2 Storage Static Remarks Initial value is 0. A-7 Table A.17 CAS_IN Classification Record Description Represents the remote setpoint value that must come from another fieldbus block or a distributed control system (DCS) block through a defined link.
A-8 Standard Function Block Parameters Usage C/Channel Length 2 Valid Views VIEW_4 Storage Static Remarks The initial value is 0. Table A.20 CLR_FSAFE Classification Simple Variable Description Serves as a switch to reset/clear the device failsafe state after the fault condition is cleared. FF Data Type Unsigned 8 Range 1: Off 2: Clear Usage C/Contained Length 1 Storage Dynamic Remarks The operator can control PROGRAM or LOCAL access to these values. Table A.
Standard Function Block Parameters A-9 Valid Views VIEW_4 Storage Static Remarks See the following for a list of the control options by bit and applicable function block. Table A.
A-10 Standard Function Block Parameters Table A.25 CYCLE_TYPE Dxxx Blocks Classification Simple Variable Description A bit string to identify the block execution methods available for this resource. FF Data Type Bit String Range Set by Manufacturer Usage C/Contained Length 2 Valid Views VIEW_4 Storage Static Remarks Read Only Table A.26 DEV_REV Classification Simple Variable Description Identifies the manufacturer revision number associated with the resource.
Standard Function Block Parameters A-11 Table A.28 DD_RESOURCE Classification Simple Variable Description Identifies the tag of the resource that contains the Device Description for this resource. FF Data Type Visible String Usage C/DD Resource Length 32 Storage Static Remarks Read Only Table A.29 DD_REV Classification Simple Variable Description Identifies the revision of the Device Description associated with the resource so an interface device can locate the DD file for the resource.
A-12 Standard Function Block Parameters Table A.31 DISC_LIM Classification Simple Variable Description Identifies state of discrete input that will generate an alarm. FF Data Type Unsigned 8 Range PV state Usage C/Contained Length 1 Valid Views VIEW_4 Storage Static Table A.32 DISC_PRI Classification Simple Variable Description Identifies the priority of the discrete alarm.
Standard Function Block Parameters A-13 Table A.34 DV_HI_LIM Classification Simple Variable Description Defines the high deviation alarm limit setting in engineering units. FF Data Type Float Range 0 to PV Span, + infinity Usage C/Contained Length 4 Valid Views VIEW_4 Storage Static Remarks Initial value is + infinity Table A.35 DV_HI_PRI Classification Simple Variable Description Defines priority of the high deviation alarm.
A-14 Standard Function Block Parameters Table A.37 DV_LO_LIM Classification Simple Variable Description Defines the low deviation alarm limit setting in engineering units. FF Data Type Float Range – infinity, - PV Span to 0, Usage C/Contained Length 4 Valid Views VIEW_4 Storage Static Remarks Initial value is – infinity Table A.38 DV_LO_PRI Classification Simple Variable Description Defines priority of the low deviation alarm.
Standard Function Block Parameters Valid Views VIEW_1, VIEW_3 Storage Non-Volatile Remarks Read Only A-15 Table A.40 FEATURES Classification Simple Variable Description Bit string that identifies the supported resource block options. FF Data Type Bit String Range Set by manufacturer Usage C/Contained Length 2 Valid Views VIEW_4 Storage Static Remarks Read Only Table A.
A-16 Standard Function Block Parameters Table A.43 FF_SCALE Classification Record Description Defines the feed-forward input high and low scale values, engineering units code, and number of digits to the right of the decimal. FF Data Type DS-68 Range 0-100 percent Usage C/Scaling Length 11 Valid Views VIEW_4 Storage Static Remarks The Data type consists of data that describes floating point values for display purposes. It uses the following four elements.
Standard Function Block Parameters A-17 Valid Views VIEW_1, VIEW_3 Storage Dynamic Remarks Read Only The Data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Table A.46 FIELD_VAL_D Classification Record Description Represents the raw value of a field device discrete input with a status reflecting the transducer condition.
A-18 Standard Function Block Parameters Table A.48 FREE_TIME Classification Simple Variable Description Identifies the percent of block processing time that is free to process additional blocks. FF Data Type Float Range 0 - 100 percent Usage C/Contained Length 4 Valid Views VIEW_1, VIEW_3 Storage Dynamic Remarks Read Only Table A.
Standard Function Block Parameters A-19 Table A.51 FSAFE_VAL_D Gxxx Blocks Classification Simple Variable Description Defines the preset discrete setpoint to use when a failure occurs. Value is ignored, if the IO_OPTS Failsafe to value option is false. FF Data Type Unsigned 8 Usage C/Contained Length 1 Valid Views VIEW_4 Storage Static Table A.52 GAIN Classification Simple Variable Description Represents dimensonless gain used by several different algorithms.
A-20 Standard Function Block Parameters Hxxx Blocks Table A.54 HARD_TYPES Classification Simple Variable Description Identifies types of hardware that are available as channel numbers on this resource. FF Data Type Bit String Range Set by manufacturer Usage C/Contained Length 2 Valid Views VIEW_4 Storage Static Remarks Read Only Table A.55 HI_ALM Classification Record Description Identifies the status and time stamp associated with the high alarm.
Standard Function Block Parameters A-21 Length 16 Storage Dynamic Remarks Read Only The Data type consists of data that describes floating point alarms. It uses the following five elements. •1 Unacknowledged •2 Alarm State •3 Time Stamp •4 Subcode •5 Value Table A.57 HI_HI_LIM Classification Simple Variable Description Defines the high high alarm limit setting in engineering units.
A-22 Standard Function Block Parameters Usage C/Contained Length 4 Valid Views VIEW_4 Storage Static Remarks Initial value is + infinity Table A.60 HI_PRI Ixxx Blocks Classification Simple Variable Description Defines priority of the high alarm. FF Data Type Unsigned 8 Range 0 to 63 Usage C/Alert Priority Length 1 Valid Views VIEW_4 Storage Static Remarks Initial value is 0 Table A.
Standard Function Block Parameters A-23 4 SP Track retained target X X 5 Increase to close X 6 Failsafe to value X X 7 Use Failsafe value to restart X X 8 Target to Man if failsafe activated X X 9 Use PV for BKCAL_OUT X X 10 Low Cutoff 11 Reserved 12 Reserved 13 Reserved 14 Reserved 15 Reserved X Table A.63 IN Classification Record Description Represents the primary input value of the block. Blocks that filter the input to get the PV require this parameter.
A-24 Standard Function Block Parameters Valid Views VIEW_3 Storage Non-Volatile Remarks Read Only The Data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Jxxx Blocks No J parameters Kxxx Blocks No K parameters Lxxx Blocks Table A.65 LIM_Notify Classification Simple Variable Description Defines the maximum number of unconfirmed alert notify messages allowed.
Standard Function Block Parameters Length 1 Valid Views VIEW_4 Storage Static A-25 Table A.67 LO_ALM Classification Record Description Represents the status of the low alarm and its associated time stamp. FF Data Type DS-71 Usage C/Alarm Length 16 Storage Dynamic Remarks Read Only The Data type consists of data that describes floating point alarms. It uses the following five elements. • Unacknowledged • Alarm State • Time Stamp • Subcode • Value Table A.
A-26 Standard Function Block Parameters Length 16 Storage Dynamic Remarks Read Only The Data type consists of data that describes floating point alarms. It uses the following five elements. • Unacknowledged • Alarm State • Time Stamp • Subcode • Value Table A.70 LO_LO_LIM Classification Simple Variable Description Defines the setting for the low low alarm in engineering units.
Standard Function Block Parameters Length 1 Valid Views VIEW_4 Storage Static A-27 Table A.73 LOW_CUT Mxxx Blocks Classification Simple Variable Description Represents the limit used for the flow sensor input processing by the Analog Input block, if the Low Cutoff selection is choosen in IO_OPTS. If the calculated PV falls below this limit, the PV value is set to zero (0).
A-28 Standard Function Block Parameters Valid Views VIEW_4 Storage Static Remarks Read Only Table A.76 MEMORY_SIZE Classification Simple Variable Description Represents the available configuration memory in the empty resource. FF Data Type Unsigned 16 Range Set by manufacturer Usage C/Contained Length 2 Valid Views VIEW_4 Storage Static Remarks Read Only Table A.
Standard Function Block Parameters Nxxx Blocks Oxxx Blocks A-29 Valid Views VIEW_1, VIEW_3 Storage mix Remarks Normally, the operator has permission to write these values, but PROGRAM or LOCAL remove that permission and grant it to a supervisory computer or a local control panel. This block has a mixture of storage types. Static for modes Normal and Permitted, Non-Volatile for Target mode, and Dynamic for Actual mode.
A-30 Standard Function Block Parameters Valid Views VIEW_1, VIEW_3 Storage Non-Volatile Remarks Normally, the operator has permission to write this value, but PROGRAM or LOCAL remove that permission and grant it to a supervisory computer or a local control panel. The Data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Table A.
Standard Function Block Parameters A-31 Table A.83 OUT_LO_LIM Classification Simple Variable Description Defines the minimum output value limit in all modes, unless the CONTROL_OPTS selection No Out limits in Manual is chosen. FF Data Type Float Range OUT_SCALE +/- 10 percent Usage C/Contained Length 4 Valid Views VIEW_2 Storage Static Remarks Initial value is 0. Table A.
A-32 Standard Function Block Parameters Pxxx Blocks Table A.86 PV Classification Record Description Represents either the primary analog value for use in executing the function, or a process value associated with it. It may also be calculated from the READBACK value of an Analog Output block.
Standard Function Block Parameters Length 4 Valid Views VIEW_4 Storage Static A-33 Table A.89 PV_SCALE Classification Record Description Defines the high and low scale values, engineering units code, and number of digits to the right of the decimal point to be used in displaying the PV parameter and parameters that have the same scaling as PV.
A-34 Standard Function Block Parameters Rxxx Blocks Table A.91 RA_FTIME Classification Simple Variable Description Defines the time constant of a single expotential filter for the value to be ratioed in seconds. FF Data Type Float Range Positive Usage C/Contained Length 4 Valid Views VIEW_4 Storage Static Table A.92 RATE Classification Simple Variable Description Defines the derivative time constant in seconds.
Standard Function Block Parameters A-35 Table A.94 RCAS_IN_D Classification Record Description Represents target setpoint and status provided by a supervisory host to the analog control or output block. FF Data Type DS-66 Usage C/Remote-Cascade In Length 2 Valid Views VIEW_3 Storage Non-Volatile Remarks The data type consists of the value and status of discrete value parameters. It uses the following two elements. • Status • Value Table A.
A-36 Standard Function Block Parameters Valid Views VIEW_3 Storage Dynamic Remarks Read Only The data type consists of the value and status of discrete value parameters. It uses the following two elements. • Status • Value Table A.97 READBACK Classification Record Description Represents the “readback” of the actual continuous valve or other actuator position in transducer units.
Standard Function Block Parameters A-37 Table A.99 RESET Classification Simple Variable Description Represents the Integral time constant in seconds. It is the inverse of repeats per minute. FF Data Type Float Range Positive Usage C/Contained Length 4 Valid Views VIEW_4 Storage Static Table A.100 RESTART Classification Simple Variable Description Allows a manual restart to be initiated. The following degrees of restart are possible.
A-38 Standard Function Block Parameters Valid Views VIEW_3 Storage Dynamic Remarks The data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Table A.102 ROUT_OUT Classification Record Description Represents block output and status.
Standard Function Block Parameters Sxxx Blocks A-39 Table A.104 SEL_1 Classification Record Description Represents first input value to the selector. FF Data Type DS-65 Usage I/Cascade Input Length 5 Valid Views VIEW_1, VIEW_3 Storage Non-Volatile Remarks Read Only The data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Table A.
A-40 Standard Function Block Parameters Valid Views VIEW_1, VIEW_3 Storage Non-Volatile Remarks Read Only The data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Table A.107 SEL_TYPE Classification Simple Variable Description Defines the type of selector action as High, Medium, or Low.
Standard Function Block Parameters A-41 Range 1: Normal Shed, normal return -See Note 1 in Remarks 2: Normal Shed, no return - See Note 2 in Remarks 3: Shed to Auto, normal return 4: Shed to Auto, no return - See Note 3 in Remarks 5: Shed to Manual, normal return 6: Shed to Manual, no return - See Note 4 in Remarks 7: Shed to Retained target, normal return 8: Shed to Retained target, no return Usage C/Shed Option Length 1 Valid Views VIEW_4 Storage Static Remarks Note 1: Actual mode changes to
A-42 Standard Function Block Parameters Table A.112 SIMULATE Classification Record Description Allows the transducer analog input or output to the block to be manually supplied, when SIMULATE is enabled. When SIMULATE is disabled, the simulate value and status track the actual value and status. FF Data Type DS-82 Usage C/Simulate Length 11 Storage Dynamic Remarks The data type consists of simulate and transducer floating point value and status and a simulate enable/disable discrete.
Standard Function Block Parameters A-43 Valid Views VIEW_1, VIEW_3 Storage Non-Volatile Remarks Normally, the operator has permission to write this value, but PROGRAM or LOCAL remove the permission and grant it to a supervisory computer or a local control panel. The data type consists of the value and status of floating point parameters that are Inputs or Outputs. It uses the following two elements. • Status • Value Table A.
A-44 Standard Function Block Parameters Table A.117 SP_LO_LIM Classification Simple Variable Description Defines the low limit for setpoint entry. FF Data Type Float Range PV_SCALE +/- 10 percent Usage C/Contained Length 4 Valid Views VIEW_2 Storage Static Remarks Initial value is zero (0) Table A.118 SP_RATE_DN Classification Simple Variable Description Defines the downward ramp rate in PV units per second for setpoint changes to invoke action in the Auto mode.
Standard Function Block Parameters A-45 Table A.120 ST_REV Classification Simple Variable Description Defines the revision level of the static data associated with the function block. The revision value is incremented each time a static parameter value in the block is changed. FF Data Type Unsigned 16 Usage C/Static Revision Length 2 Valid Views VIEW_1, VIEW_2, VIEW_3, VIEW_4 Storage Static Remarks Read Only Table A.
A-46 Standard Function Block Parameters 13 Reserved 14 Reserved 15 Reserved Table A.123 STRATEGY Txxx Blocks Classification Simple Variable Description Assists in grouping blocks. This data is not checked or processed by the block. FF Data Type Unsigned 16 Usage C/Strategy Length 2 Valid Views VIEW_4 Storage Static Table A.124 TAG_DESC Classification Simple Variable Description Serves as user defined description of the block.
Standard Function Block Parameters A-47 Length 112 Storage Dynamic Remarks The data type consists of function block test read/write data. It uses the following 15 elements.
A-48 Standard Function Block Parameters Valid Views VIEW_4 Storage Static Remarks The Data type consists of data that describes floating point values for display purposes. It uses the following four elements. •1 Engineering Units at 100 percent •2 Engineering Units at 0 percent •3 Units Index •4 Decimal Point Table A.128 TRK_VAL Uxxx Blocks Publication 1757-UM006A-EN-P - May 2002 Classification Record Description Represents the input value for external tracking.
Standard Function Block Parameters Vxxx Blocks No V parameters Wxxx Blocks Table A.130 WRITE_ALM A-49 Classification Record Description Represents alert that is generated if the write lock is cleared. FF Data Type DS-72 Usage C/Alarm Length 1, 3 Storage Dynamic Remarks Read Only The data type describes discrete alarms using the following five elements: • Unacknowledged • Alarm State • Time Stamp • Subcode • Value Table A.
A-50 Standard Function Block Parameters Xxxx Blocks Length 1 Valid Views VIEW_4 Storage Static Table A.133 XD_SCALE Classification Record Description Defines the high and low scale values, engineering units code, and number of digits to the right of the decimal point used with a specified channel value obtained from the Transducer.
Appendix B Fieldbus Status Display Indications Table B.
B-2 Fieldbus Status Display Indications Table B.
Fieldbus Status Display Indications B-3 Table B.
B-4 Fieldbus Status Display Indications Table B.
Appendix C Mode Change Conditions Reference Input Parameters Status Mode Parameter - Target Attribute Value Attributes, Inputs Values and Resource States Out of Service (OOS) Manual (MAN) Automatic (Auto) Cascade (CAS) Remote Cascade (RCAS) Remote Output (ROUT) All input parameters have Good Status or Uncertain status with option set to treat Uncertain as Good. OOS MAN AUTO CAS RCAS ROUT Remote cascade in has BAD status or time-out is detected and the shed option parameter value is Normal.
C-2 Mode Change Conditions Input Parameters Status Mode Parameter - Target Attribute Value Attributes, Inputs Values and Resource States Out of Service (OOS) Manual (MAN) Automatic (Auto) Cascade (CAS) Remote Cascade (RCAS) Remote Output (ROUT) N/A N/A N/A Actual mode from last execution or AUTO N/A N/A Status attribute of primary input OOS parameter is BAD or Uncertain with option to treat Uncertain as BAD and bypass not set MAN MAN MAN MAN ROUT Status attribute of back calculation inpu
Appendix D Fieldbus Wiring Considerations The following wiring information is for general purposes only. Refer to each device’s cooresponding wiring and installation instructions. Fieldbus Topologies Figure D.1 illustrates the Spur, Daisy Chain, and Tree type wiring topologies that can be used to connect fieldbus devices to one another and a host. Figure D.
D-2 Fieldbus Wiring Considerations Power Conditioning You must use a power conditioner between your Fieldbus power supply and the Fieldbus netwrok. You can use a power supply designed for Foundation Fieldbus operation which has the proper power conditioning elements. If you are using an ordinary power supply, a separate power conditioner must also be used.
Fieldbus Wiring Considerations Power Distribution D-3 The design of a fieldbus network requires understanding of the electrical requirements of the devices (current/voltage) and the properties of the cable use (resistance).
D-4 Fieldbus Wiring Considerations The following table lists limits for some possible fieldbus cable types listed in the order of usage preference with 1 being preferred. Table D.
Fieldbus Wiring Considerations Cable Guidelines D-5 A quick method to determine if the segment is within limits is to calculate a segment ratio. Total cable length is the sum of trunk and spur lengths. If different cable preference types are used, apportion each type against its limit and be sure the total is less than one (1). EXAMPLE For example, if the 500m (1640ft) trunk cable is preferred type 1 cable and the spurs are 100m (328ft) preferred type 2 cable, the total cable resistance equals 0.
D-6 Fieldbus Wiring Considerations Signal Distortion vs Capacitance Other factors such as varying characteristic impedance, spur connection reflections, and capacitive unbalance between the wires and shield can distort signals as they travel though the cable. This means an ideal signal transmission that is within fieldbus specifications can arrive at the other end of the cable as a distorted signal.
Fieldbus Wiring Considerations Calculating Attenuation D-7 Take the sum of the following calculations to determine if the attenuation will exceed the allowed level of 14 dB. • Calculate the cable attenuation. • Calculate the attenuation due to spurs. • Calculate the attenuation due to device capacitance. EXAMPLE For example, the total attenuation for the fieldbus topology used in the previous examples in this section would be 2.13 dB (1.5 dB (cable attenuation) + 0.105 (spur attenuation) + 0.
D-8 Fieldbus Wiring Considerations Notes: Publication 1757-UM006A-EN-P - May 2002
Appendix E Fieldbus Library Manager About Fieldbus Library Manager The Fieldbus Library Manager (FLM) is an Engineering Tools utility for reading the vendor supplied Device Description (DD) files for fieldbus devices and creating device templates to be stored in the Engineering RepositoryDatabase(ERDB).Thestoredtemplatesareaccessiblethroughthe Library tab in Control Builder, where they are cataloged in vendor named directories. Figure E.1 shows a simplified graphical representation of the process.
E-2 Fieldbus Library Manager Description The FLM features a Windows type interface with drop-down menus, toolbar, directory tree pane, and view pane as shown in Figure E.2. Figure E.2 Fieldbus Library Manager features common Windows type interface. Rockwell Automation - Pressure Transmitter Menu and toolbar selections Table E.1 The following table summarizes the functions you can initiate through a given menu selection or toolbar button for reference.
Fieldbus Library Manager E-3 Table E.2 Menu and toolbar selection summary Click: Or, follow this menu selection: To perform this function: File->Build Device Template->From Existing .DEF Files Opens dialog box so you can navigate to the directory containing the desired device .DEF files. Default directory is: Rockwell Automation\tps50\system\er\ffdevices File->Login to server Opens Login Information dialog box so you can login to another ProcessLogix Server in your system.
E-4 Fieldbus Library Manager Table E.2 Menu and toolbar selection summary Click: Or, follow this menu selection: To perform this function: Help->About Fieldbus Library Manager Opens About Fieldbus Library Manager dialog box for general information about the utility.
Appendix F 1788-CN2FF Installation Example Overview This installation example provides a step by step approach to the installation of the 1788-CN2FF. For more information on the operation the 1788-CN2FF, and its companion software, the 1788-FFCT, Foundation Fieldbus Configuration Tool refer to Chapter 7, Using the 1788-CN2FF, ControlNet-to-FOUNDATION Fieldbus H1 Linking Device. For more information on Foundation Fieldbus visit www.Fieldbus.org. Table F.
F-2 1788-CN2FF Installation Example Required Hardware for Installation Example ❏ One 1788-CN2FF, ControlNet to Fieldbus Linking Device ❏ One 24 Power Supply for the CN2FF, such as 1794-PS1 1794-PS1 is a good power supply for use with the CN2FF, and is OK to use for a small demo with one or two Fieldbus devices, but it is too noisy for a real control application. ❏ FF convenience Relcom Connector Blocks. Connector block should include built in power conditioner and two Fieldbus terminators.
1788-CN2FF Installation Example Required Software F-3 ❏ RSLinx version 2.10.166 or later, OEM version or better. IMPORTANT RSLinx Lite is not compatible. ❏ RSNetworks for ControlNet version 2.25 or later - - to schedule data to the controller. ❏ RSLogix 5, RSLogix 500, RSLogix 5000, or ProcessLogix ControlBuilder, to program the controller and to see the FF data in the file in the controller ❏ 1788-FFCT, the Foundation Fieldbus Configuration Tool, Version 2.3.6 or later.
F-4 1788-CN2FF Installation Example Schedule Connections The platform Rockwell uses to schedule the ControlNet connections to the controller is Windows NT with RSNetWorx. Utilize RSLinx RSLinx OEM is needed for the 1788-FFCT software. The version of RSLinx that is bundled with many products is not RSLinx OEM. You must have RSLinx OEM or a more complete version of RSLinx for the 1788-FFCT to function.
1788-CN2FF Installation Example Connecting the Hardware F-5 1. Wire the 1784-PS1, the 1788-CN2FF, and the Terminal Block as shown in Figure F.2. Figure F.2 Wiring the 1788-CN2FF 1794-PS1 1788-CN2FF LINKING DEVICE 1788-CN2FF ControlNet A B Green A B White V V V FOUNDATION™ FIELDBUS 1 Black 2 C PORT 1 STATUS PORT 2 Black AC Power Connection White Black White 24 V Power Connection If indicator lights do not light, reverse polarity of 24 V leads.
F-6 1788-CN2FF Installation Example The base terminal block supports either two or four device connections (depends on the type of block), plus the power connection. An auxiliary block supports four additional device connections. IMPORTANT To provide power to a fieldbus device, use our ordinary 24V instrumentation power supply. You must also use a Fieldbus Power Conditioner (power isolator), 3. Select a Mac ID for the CN2FF. 4.
1788-CN2FF Installation Example F-7 When installation is complete, you see: 5. Click OK. 6. Follow instructions to restart the computer. Adding an Interface Device Whenever you want to add a new device, you will need to go through this procedure. You will do this procedure frequently. 1. Click on Add Interface Device.
F-8 1788-CN2FF Installation Example You see: Check CONTROLNET 2. For Interface Type check CONTROLNET. When you select ControlNet, the dialog box changes to reflect the default ControlNet parameters. ATTENTION: The driver name must be entered EXACTLY (case, punctuation, underscores) as it is listed in RSLinx. refer to Finding the Interface Driver Name on page F-9 for an example. Enter the ControlNet driver name Enter the ControlNet MAC-ID of the CN2FF.
1788-CN2FF Installation Example F-9 4. In Network Address, type in the MAC ID of the 1788-CN2FF. 5. Select the number of ports you are using. For this example we are only using 1. 6. If your computer is on the same ControlNet and the 1788-CN2FF, set the Path to 02. If your computer is on another ControlNet, use the path suggested by RSLinx. A typical PLX path might be 2 6 1 6 2. 2(1 space)6(1 space)1(1 space)6(1 space)2 7. Leave the Timeout as defaulted. Click Add.You see: 8.
F-10 1788-CN2FF Installation Example You see: As stated on page F-8, driver names must match exactly. 2. Make a note of the ControlNet Driver name and go back to Step 3 on page F-8 and type the name in the Driver Field at the Interface dialog box. The name here is AB_PCIC-1. Assigning a Path to the 1788-CN2FF Assigning a Path through which the 1788-FFCT software will communicate with the 1788-CN2FF. If you are familiar with the Path and you know it is correct, you can skip this section.
1788-CN2FF Installation Example F-11 4. Click on New and type in a name. 5. Navigate to the 1788-CN2FF you want to configure. 6. Select the 1788-CN2FF. You see: 7. Click Apply. 8. Click Advanced Communications.
F-12 1788-CN2FF Installation Example You see: The path here is 2.6.1.6.2 The 10 at the end of this string is the MAC ID. 9. Copy the path from here to Step 6 on page F-9 in the Path field of the Interface dialog box. The path here is 2.6.1.6.2 The 10 at the end of this string is the MAC ID. Port Configuration When you have finished with the Interface dialog box and click Add, you see: 1. Type in a name that is meaningful to your project.
1788-CN2FF Installation Example F-13 This is the name for the Fieldbus connection on port 0 of the linking device. IMPORTANT The ports on the front of the 1788-CN2FF are labeled Port 1 and Port 2. However, the software labels them Port0 and Port1. We are using the first port on the linking device, which will appear as port 0 in the software, but is physically marked as port 1 on the linking device. 2. Click OK.
F-14 1788-CN2FF Installation Example Installing Device Descriptions (DDs) A DD is a file, which describes the FF device to the configuration software. DD's are like the EDS files we use on DeviceNet and ControlNet but DDs are typically 10 times larger. The Device Descriptions need to be installed for all the devices that you will connect to the Fieldbus, including the DD for the 1788-CN2FF. 1. Click DD Info.
1788-CN2FF Installation Example F-15 You see: When you start, all the DD’s will be located in another directory. Use Browse to find the location. 3. Insert the disk for the 1788-CN2FF in the A: drive. 4. Click Browse. You are looking for the DD Files. The DD for the CN2FF is on the disk that was shipped with the 1788-CN2FF. The DD’s for the Fieldbus Devices should be on disks that ship with the device.
F-16 1788-CN2FF Installation Example 5. Select the file with the extension .ffo and click Open. You see: 6. Click OK to import the DD. You will receive a message telling you the copy succeeded. TIP If you get a message that says: Can Not Import that DD, there is a good chance that the DD has already been installed on your system. Go on, and don't worry for now. 7. Repeat the process to import the DDs for all the other Foundation Fieldbus devices attached to the 1788-CN2FF.
1788-CN2FF Installation Example F-17 10. Double-click the NIFB icon on the desktop. TIP If the Icon is not on your Desktop, you can get it at Start\Programs\National Instruments\NIFB.exe. Starting NIFB You are now ready for the next step toward configuring a Fieldbus. 1. Go to Start⇒Programs⇒National Instruments FBUS, and click on NIFB. You see: ver 2.3.
F-18 1788-CN2FF Installation Example If you don’t see this screen, your interface is not configured properly, refer to Adding an Interface Device on page F-7 for more information. This window appears for a few seconds, then displays a quick message saying that all the interfaces are there, and then disappear. This icon appears in the lower right corner of the toolbar indicating that the NIFB software is running. Troubleshooting the Port Configuration Use this section if NIFB does not start.
1788-CN2FF Installation Example F-19 Once the NIFB software is running we are ready to start the configurator tool. IMPORTANT Start FCS You could go directly to the configuration tool without manually starting the NIFB software. The config tool, the FCS.exe, automatically starts the NIFB software. However, if there is a problem with the connection, the config tool may hang without providing an indication of the problem.
F-20 1788-CN2FF Installation Example 3. Uncheck one box so we only use one port on the CN2FF. Click OK to accept the selection.(we are only using one link). TIP The standard version of the FFCT only supports the configuration of 4 Fieldbus networks at one time. You can configure two Fieldbus networks connected to each of two CN2FFs or you can configure one fieldbus connected to each of 4 CN2FF.
1788-CN2FF Installation Example F-21 It will take several minutes for all the data to be gathered to complete this window. This is primarily a list of the Function Blocks that are in the attached Fieldbus devices. Until all the data is complete, you will see the “working” hour glass. IMPORTANT If you are using both ports on a single CN2FF, you must: 1. Check both ports, now. 2. Configure both Fieldbus networks. 3. Perform two downloads.
F-22 1788-CN2FF Installation Example 4. When the working icon disappears, click Network Parameters. These are the devices on the FF network. Your list of devices and Function Blocks will be different. This is called the Function Block Library, You see: Primary LAS LAS, Link Active Scheduler LAS stands for Link Active Scheduler and identifies the device which will hold the network schedule and tell each node when to Publish its FF information. Uncheck the download to Honeywell Attached.
1788-CN2FF Installation Example F-23 Attached.” Doing this saves a little time since you will not load the LAS into the Honeywell device. IMPORTANT Some devices that are capable of being LAS can cause some conflict. For your first test, check only the 1788-CN2FF. 7. Use the Primary LAS and Primary Timemaster pull down lists to Select the 1788-CN2FF to be both the primary LAS and the Primary Timemaster. (the CN2FF is the second one listed above).
F-24 1788-CN2FF Installation Example The best thing to do is use the values that the FF suggests: They are shown in the window. 8 4 10 37 0 16 186 2 1 1 4 Modifying Device and Function Block Names 1. Click Write Changes to save the changes. FIRST_UNPOLLED_NODE_ID = 37 This setting defines 36 to be the last available address to be polled on this network. When addresses are assigned for this network, they will be assigned in the range of 16-36.
1788-CN2FF Installation Example F-25 network address of each transmitter, and then give names to each of the function blocks. 4. Move your mouse over the device name of your first device and click the right mouse button.
F-26 1788-CN2FF Installation Example Changing a Tag Name You can change the names of the Fieldbus Devices, and most of the function blocks so they have meaning in your application. IMPORTANT Do not attempt to change the names of the Function Blocks in the 1788-CN2FF. If you change these names the 1788-CN2FF will not work properly. 1. Right click on a Function Block. 2. Select Set Tag. 3. Type any name that fits your application. Short names are easier to read in Device Info which you’ll use later. 4.
1788-CN2FF Installation Example F-27 If you ever plan to change the name of a Function Block, do it now. After you do your download, you do not want to change any connections, or Tag names. When you look at the Device Info window after you download, you will see the value of using very short names for the Device and the Function Blocks. 8. Highlight the RB function block in the Library of Function Blocks, and click the right mouse button. 9. Select Set Tag. 10.
F-28 1788-CN2FF Installation Example 12. Double click on the device and you'll get a window like this. This screen shows the name and the node address assigned to the device, and lists a Device ID assigned by the manufacturer. It is a unique identification. You or the FF protocol may have assigned the Node Address. Because the Link Master device with the lowest node number becomes the Link Active Scheduler, you may want to adjust Node Numbers after they have been automatically assigned.
1788-CN2FF Installation Example F-29 Configuring the Fieldbus Device Once you have finished assigning device names you need to program the Fieldbus devices to move data where we want it. 1. In the screen below, select all the Analog Input Function Blocks in the Fieldbus Transmitters in the column on the left, and drag them into the Function Block Application window. 2. Drag one of the CN2FF Multiple Analog Input Function Blocks to the right side of the FB Application Window.
F-30 1788-CN2FF Installation Example 4. Click on the spool of wire in the top tool bar, and use the wire to connect, or program the Function Blocks as your application requires. Figure F.3 illustrates 5 Analog Input Function Blocks connected to one Multiple Analog Input Function Block, MAI FB. Figure F.3 5 Analog Input Function Blocks After creating this Function Block configuration (drag and drop), the 1788-FFCT software knows where you want connections, but the Fieldbus Devices do not.
1788-CN2FF Installation Example F-31 Download the Device Configuration 1. On the left side of the toolbar, Click on the Download Button on the top toolbar. You see: 2. Check the boxes as shown: • Clear Devices • Automatic Mode Handling. 3. Click Download. This may take a few minutes. While waiting you can monitor the activity in the Download window at the bottom of the screen. When the download is complete, you will get a small new window to advise you.
F-32 1788-CN2FF Installation Example download fails again, remove the FF device and configure again. Look at the download log and status for ideas. If you continue to have download problems, refer to Troubleshooting an Application on page F-51. In the toolbar at the top of the screen, click on the blue eye to start the Monitor. When you run the monitor, you get a display of the values being read from the attached transmitters. 3 The Monitor window will appear as shown here.
1788-CN2FF Installation Example F-33 4. Set the monitor to update the display every 5 seconds. The output values from the analog Function Blocks will be displayed along with the status of the Function Blocks. If you change the temperature or the pressure being measured by the Transmitter, you should see the new value on the screen 5. You may have an output that is displaying bad with a red border as shown below. If you see this, to refer to Troubleshooting an Application on page F-51.
F-34 1788-CN2FF Installation Example 6. Select the Show/Hide Transducer block icon from the toolbar to display the hidden transducer block. The hidden transducer blocks will now appear in the list of function blocks for the transmitters The image below shows an E+H Transducer block. 7. Double-click on the transducer block.
1788-CN2FF Installation Example F-35 8. To Change the block from OOS mode to Auto mode click on the AUTO buttons at the top of the window. TIP There is typically no reason for a Transducer Block to be in the OOS mode, other than the Configurator may not have been able to set it to AUTO. Therefore, manually set it to AUTO. If that is the only problem, the AI value will go to AUTO, the status will change to GOOD, and you will start to see data values from the transducer. Also check the Resource Block.
F-36 1788-CN2FF Installation Example When the transmitter has been configured and the Monitor window is displaying process variables properly, you have completed the configuration. Congratulations! Sending Data To the PLC-5, CLX, PLX or SLC The following steps illustrate the sequence in which data will be sent from the Linking Device over ControlNet. 1. Double click on the “Device Info” icon. A new screen displays all the data produced by the attached Fieldbus Devices by Function Block Tag name.
1788-CN2FF Installation Example F-37 Figure F.4 Device Information Screen CN2FF interface name Connection Port Number Used with ControlNet Message Instructions Offset in bytes from the start of the ControlNet produced data Length of value in bytes 2. Expand the window so you can read all the columns. This screen is the reason we recommend using a high resolution monitor and short Function Block names.
F-38 1788-CN2FF Installation Example process swaps the sequence of the data floating point which is the process variable. To get the analog value into floating point format so you can use the data, you need to swap the sequence of the words, and then copy the 32 bit value to a Floating Point data table. When you do the copy, specify a length of 1.
1788-CN2FF Installation Example F-39 Support adds 2 to the listed Offset. (If you are using a PLC-5, the Offset values are correct.) The 1788-FFCT and 1788-CN2FF are capable of producing data that can be used by all RA controllers that interface directly to ControlNet. This includes the PLX, CLX, PLC-5s and SLC. If you have problems, call Rockwell Automation Technical Support at 440.646.5800. Also refer to Rockwell Automation Technical Support on page P-3.
F-40 1788-CN2FF Installation Example PLC-5 and ControlLogix Applications After the initial, setup the task is to get data to and from a controller. You can move Fieldbus data to and from SLCs, PLC-5’s, ControlLogix 5550, and ProcessLogix. The first stage is to set up a working Fieldbus network that has connections to the linking device. Here is an example configuration.
1788-CN2FF Installation Example F-41 OUT pin of the SMAR AO block is connected to the fifth input of the MAI module, on the MAI FB. There is also the BackCalibration, or BKCAL connections shown from the SMAR. At present the FFCT software demands that there be a BKCAL connection to the MAO FB. This combination of connections will create a ControlNet Object in the CN2FF that can be sent to controllers using RSNetworks or ControlBuilder, depending on which controller you are using.
F-42 1788-CN2FF Installation Example Figure F.5 ControlNet Module Properties There are several parameters to note on this window: Comm The Comm Format is Data-DINT. Assembly Instance The Assembly Instance values must be set as shown in Figure F.5. Input Size Look back at the Device Info in the Configuration software. Notice that an Analog input repeats every 8 bytes.
1788-CN2FF Installation Example F-43 Given that the Fieldbus network operates much slower than the ControlNet network, and does not carry time critical information, it is a good idea to bump up the RPI for the Linking Device to preserve ControlNet bandwidth. 6. Select Finish. The linking device is now configured for ControlNet communications. 7. Save your project and download it to the controller.
F-44 1788-CN2FF Installation Example Schedule the Connection Between the Controller and the Linking Device 1. Open RSNetWorx. 2. Select File from the main menu. 3. Select New. 4. Select ControlNet Configuration and click OK. 5. Go online to the ControlNet network. 6. Select the Edits Enabled checkbox in the upper left of the screen. 7. Browse the network, click the Browse icon. 8. Save the network. RSNetWorx will schedule all the connections during the save operation. View the Controller Tags 1.
1788-CN2FF Installation Example F-45 Figure F.6 Data Values The first double word is the pad. The pressure is contained in word 1. Remember, the pressure is returned as a floating-point value. You are currently viewing it in a DINT. Word 2 contains the 2 status bytes. As you look at the values you realize that in their current representation the values are not of much use. Your first thought is to create a bunch of copy instructions to copy the values into their proper data type.
F-46 1788-CN2FF Installation Example 10. Click Apply. At this point we have the first two parts of the structure defined. Enter the remaining members as shown below. 11. Click OK. We now have a structure with which we can create tags just the same as Timers, Counters, etc. Let's create a tag which will hold the data coming from the Linking device. 12. Open the controller tags database and select the Edit tab on the bottom of the window. 13. Enter a tag name of: LD_Node_9 14.
1788-CN2FF Installation Example F-47 The actual pressure of about .04 psi (in this case) can now be read directly. 3. Squeeze the bulb (or place your thumb over the connector) on the transmitter. 4. Verify the pressure reading increases and follows the pressure displayed on the transmitter itself. Messages to PLC-5s and CLX to Get Data from CN2FF You can use a ControlNet message instruction to get any of the data that is stored in the different tables that list the various ControlNet objects.
F-48 1788-CN2FF Installation Example Figure F.7 PLC-5 Message Setup This example message will retrieve the Analog Process Variable at Instance, as shown in the Device Info Figure F.4 on page F-37, because the attribute is 3. If the attribute was 4, it would retrieve the ControlNet status. It would retrieve the FF status if the attribute was 150.
1788-CN2FF Installation Example Remote Configuration of a Fieldbus Network via the 1788-CN2FF F-49 The 1788-FFCT, the Foundation Fieldbus Configuration Tool, works through RSLinx, so the things that you expect to be able to do through RSLinx, you can in fact do with the FFCT, including configuration from a remote location. In the section Assigning a Path to the 1788-CN2FF starting on page F-10, we determined the path to a CN2FF where multiple ControlNet networks were involved.
F-50 1788-CN2FF Installation Example 6. Select Advanced Communications. This is the path from your PC, via TCP-1 to Mac ID 7. 7. Read the Path and copy it to the Path window of the Interface window, refer to page F-12. That’s it. Congratulations. You have told the Fieldbus Configuration software the path to communicate with the remote CN2FF.
1788-CN2FF Installation Example Troubleshooting an Application F-51 The Fieldbus AI Side: After you have created the FF configuration, click on the blue eyeball to see that you are getting data from all the AI FBs. If you are getting “BAD Data” from a device, check first to see that the Resource Block and the Transducer Blocks in that device are in the “Auto” mode. To see the Transducer Block, you must uncheck the “T” in the top toolbar that initially had a red X through it.
F-52 1788-CN2FF Installation Example IMPORTANT At present, Rockwell Automation is not promoting the use of the distributed control capability of Fieldbus. That means that all the control is done in the controller. We are using the Fail-safe processing capability of the individual Fieldbus devices. Table F.2 Troubleshooting If you see: Do this: Bad Status, Bad Data Value Make sure to see that all the Function Blocks and Transducers are in the proper operating mode.
1788-CN2FF Installation Example F-53 The Transducer FB window opens. If the OOS is active: Table F.3 If: Then: the OOS is active • Click on the “Auto” button, to put the Transducer Block in “Auto” mode. the Transducer goes into Auto mode, and if that was your only problem • The bad data indication will go away. the Transducer FB doesn’t go into Auto • Check the mode of the Resource Block and the AI Block. • All should be in Auto Mode.
F-54 1788-CN2FF Installation Example Publication 1757-UM006A-EN-P May 2002
List of Figures OSI versus Fieldbus communication model . . . . . . . . . . . . 1-3 Function Block Application Process based on blocks . . . . . . 1-5 Using Function Blocks in Fieldbus Devices to Form a Control Loop . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Functional Schematic for Analog Input Function Block . . . . . 1-9 Functional Schematic for Analog Output Function Block. . . 1-11 Functional Schematic for Bias/Gain Function Block . . . . . .
List of Figures ii Event Summary display includes fieldbus related details . . . . 5-2 FIM front panel indicators. Table 1 FIM LED Interpretations. 6-5 Sample Single Macrocycle MAI Configuration . . . . . . . . . . . . 7-2 Sample Multiple Macrocycle MAI Configuration . . . . . . . . . . 7-3 Alarm Attribute Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Sample Cascaded AO Configuration. . . . . . . . . . . . . . . . . . . 7-6 Sample Multiple Macrocycle AO Configuration . . . . . . . . .
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 Fieldbus Solutions for Rockwell Automation’s Integrated Architecture Cat. No. ProcessLogix, ControlLogix, and PLC5 Pub. No. 1757-UM006A-EN-P Pub. Date May 2002 Part No.
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-UM006A-EN-P - May 2002 2 PN 957603-37 Copyright © 2002 Rockwell Automation. All rights reserved. Printed in the U.S.A.
Fieldbus Solutions for Rockwell Automation’s Integrated Architecture User Manual
