Home

1757-UM006 - Literature Library

1. Setpoint Bypass Feed Forward __ Output CAS_IN sp_RATE_DN BYPASS FF SCALE OUT_HI_LIM 7 OUT SP_RATE_UP M FF_GAIN OUT _LO LIM a j Control t SP_LO_LIM LW eee RESET _ SP _ BAL_TIME Status r RATE BKCAL_HYS IN SM Filter PV PV_FTIME _ Alarm cer Output Track Mode TRK_SCALE SHED_OPT TRK_IN_D TRK_VAL Table 1 L Proportional Integral Derivative Block Specifications Description The Proportional Integral Derivative function block provides classic three mode control function for closed loop control applications When the Process Variable deviates from the Set point the PID function acts upon the error to move the output in a direction to correct the deviation PID blocks support cascade applications to compensate for the difference in process time constants of a primary and secondary process measurement A functional schematic of the block is shown in Figure 1 12 for reference Function Notes e Supports Out of Service OOS Initialization Manual I Man Local Override LO Manual Man Automatic Auto Cascade Cas Remote Cascade RCas and Remote Out ROut modes e The input IN passes through a filter with a time constant PV_FIIME The filtered value becomes the Process Variable PV to be used with the Set point SP in the block s algorithm A PID algorithm will not integrate if the limit status of the input IN is con
2. 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 Control the Process Use ControlBuilder or RSLogix 5000 to control the process using the data from the existing Fieldbus Devices connected via the CN2FF Linking Device Figure F 1 Example Linking Device Configuration ProcessLogix System Server ProcessLogix and ControlLogix E of Fm i I p a r m i Data Highway EA 1788 CN2FF nnam ne 3 ControlNet SLC Controller 1771 Remote 1 0 Flex Ex FOUNDATION Controller T r Fieldbus Pressure PLC5 C Controller Transmitter Publication 1757 UMO06A EN P May 2002 1788 CN2FF Installation Example F 5 Connecting the Hardware 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 po 1794 PS1 C Ta 1788 CN2FF amp Allen Bradley j Hex I O wy Allen Bradley LINKING DEVICE 1788 CN2FF POWER bre ControlNet m S iP ia A
3. Fieldbus Wiring Considerations D 5 Cable Guidelines 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 35 500 1900 100 1200 0 35 0 35 is less than 1 0 therefore segment resistance is good Cable Attenuation Signals attenuate or get smaller as they travel though cables Attenuation is measured in decibels dB based on the following formula dB 20 log V1 V2 Where V1 Amplitude of Signal Transmitted in Volts V2 Amplitude of Signal by device in Volts e Cables have different attenuation ratings for a given frequency The frequency of interest for fieldbus is 39 kHz e The preferred type 1 cable for fieldbus has an attenuation of 3 dB km e A fieldbus device can transmit a signal as low as 0 75 volts peak to peak and detect a signal as small as 0 15 volts peak to peak This means that the cable can attenuate the signal by 14 dB 20 log 0 75 0 15 14 dB Based on using the preferred type 1 cable a fieldbus cable run could be up to 4 6 km 15091 ft long as determined from this formula 14 d
4. Publication 1757 UMO06A EN P May 2002 1 28 The Fieldbus Communication Model Level 2 Function Block Parameters Level 3 Transducer Block Parameters Level 4 Manufacturer Specific Parameters 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 Level 1 Universal Parameters Defined by Fieldbus Foundation Specification Al 0 0 PID TEMP FLOW Defined by Resource Transducer Function Publication 1757 UMO06A EN P May 2002 Block Block Block Levels 1 2 and 3 are the Device Descriptions that the Fieldbus Foundation provides on CD ROM Level 1 consists of Universal Parameters that define common attributes such as Tag Revision and Mode All blocks must include Universal Parameters Level 2 consists of Function Block Parameters that define parameters for all standard Function Blocks including the standard Resource Block Level 3 consists of Transducer Block Parameters that define parameters for the standard Transducer block In some cases the Transducer Block specification may add parameters to the standard Resource Block Level 4 is the Manufacture
5. 0005 E 2 Appendix F OVERA NO a ae Rat ated dent aa Wl sos SE a Oe OSE ee F 1 Required Hardware for Installation Example F 2 Required SOMWATEs garias es dd dh ae oe oer ee Go F 3 Example DESeripion amp a 0u6 cs sose Bove foe ue eee Oe F 3 Connecting the Hardwate 2 c 46 2aevetae hae eee bee ks F 5 Install the 1788 FFCT Softwares 4 4644944545484 444284 F 6 Adding an Interface Device ok a sucraiy a Oo Cer ee we F 7 Finding the Interface Driver Name 2 0050 4 F 9 Assigning a Path to the 1788 CN2FF F 10 POR COMMeUIaHON 4 recria 43 vi doa cebu debt ads F 12 Installing Device Descriptions DDs F 14 UAT MO eI EN saiae te Soca tt ese Ak PD he Ghd te neta ated eee 4 F 17 Troubleshooting the Port Configuration F 18 INTER SSOImeware Masta igi 1 tour s aust oo wa dee oth dd F 18 Did PC nan oe ou E ES Oe ee ee F 19 Modifying Device and Function Block Names F 24 Changing a Tag Name 00 0000 0c eee F 26 Configuring the Fieldbus Device F 29 Download the Device Configuration F 31 Sending Data To the PLC 5 CLX PLX or SLC F 36 Schedule Data Transmission to Controllers WIth RONCUW OIG o 2 sud ra owe Oe Hac A ae eee F 37 PLC 5 Data Manipulation 4 4 444 294 4402 e keke board F 37 List of Figures Table of Contents xi PLC 5 and ControlLogix Applications F 40 ControlLogix Application o oo a
6. 4 Current Time 0 CPU Free Average 0 CPU Free Minimum 0 NWS usage 0 l Enable stack diagnostics i Task x stack usage oji Data is only present in these fields when the FIM LINK is loaded and communicating with the system 13 Click the Server Parameters Tab Main Statistics Server Parameters Server Parameters Point Detail Page Associated Display FO Group Detail Page FP Control Level 200 Control Area Pn EU HI Parameter PT EU LO Parameter PO 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 Publication 1757 UMO06A EN P May 2002 4 12 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 ae example_cascade H a example_motor ge example_pid Et example scr fmm F150 HER LINKS HER LINKS 2 Lil Library 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 b
7. ATTENTION Inactivating a fieldbus Link essentially shuts downs the Link and the FIM if both Links are inactivated and interrupts the transfer of data to the ProcessLogix system Be sure you system can tolerate the lost of live data while the link is inactive Operating the 1757 IM_ 5 3 You can initiate this same function through the gt corresponding Detail display in Station 1 In the Monitoring tab click the LINK icon Pod ie 2 Click Toggle State 4 in the toolbar The Change State window opens Change State aie Bess Set Selected objectis Inactive selected objects LINK 5101 es 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 lt S101 A 3 Ux 4101 a ST 4245008 Ear ST_102 bee R LINK_5102 Publication 1757 UM006A EN P May 2002 5 4 Operating the 1757 FIM Publication 1757 UMO06A EN P May 2002 4 With LINK icon selected click the Toggle State button E in the toolbar The Change State window opens ee Selected object s LINK S101 Change State Set Selected objects Active 5 Click Yes This initiates the state change The icon changes from blue to ereen Monitoring 7 5 i k Ca Monitoring Interacting with given component block Once you download a FIM and its contents you can use the Monitoring tab to
8. J e J e Use the PV_FIIME to set the time that the input must be in one state before it gets passed to the PV_D J J e The SIMULATE_D parameter is for testing purposes only and always initializes in the disabled state ACK_OPTION ALARM_SUM ALERT_KEY BLOCK_ALM BLOCK_ERR CHANNEL DISC_ALM DISC_LIM DISC_PRI FIELD_VAL_D GRANT_DENY IO_OPTS MODE_BLK OUT_D OUT_STATE PV_D PV_FIIME SIMULATE_D ST_REV STATUS_OPTS STRATEGY TAG_DESC UPDATE_EVT XD_STATE Publication 1757 UMO06A EN P May 2002 1 18 The Fieldbus Communication Model Discrete Output Block Figure 1 9 Functional Schematic for Discrete Output Function Block BKCAL OUT D gt P OUTD P RCAS OUT D P Transducer CAS_IN_D RCAS_IN D gt DO __BKCAL_OUT_D RCAS_OUT_D CAS IN D Setpoin Optional Output a Invert OUT_D RCAS_IN D Simulate i SPD PVD SIMULATE_D poe Mode Optional Failsafe SHED_OPT Invert FSAFE_TIME FSAFE_ VALD READBACK D Table 1 1 Discrete Output Block Specifications Description The Discrete Output function block converts the value in SP_D to something useful for the hardware linked to the CHANNEL selection A functional schematic of the block is shown in Figure 1 9 for reference Function Notes e Supports Out
9. 5 Select Next and set the RPI rate to 40 ms Publication 1757 UMO06A EN P May 2002 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 Now that the project is downloaded in the controller you need to use RSNetWorx software to schedule the connection between the controller and the Linking device Publication 1757 UMO06A EN P May 2002 F 44 1788 CN2FF Installation Example Publication 1757 UMO06A EN P May 2002 Schedule the Connection Between the Controller and the Linking Device 1 pA 3 Open RSNetWorx Select File from the main menu Select New Select ControlNet Configuration and click OK Go online to the ControlNet network Select the Edits Enabled checkbox in the upper left of the screen Browse the network click the Browse icon Save the network RSNetWorx will schedule all the connections during the save operation View the Controller Tags Open RSLogix 5000 and view the controller tags Expand the input tags for the linking device so that you can see the data values Your screen should appear as shown in Figure F 6
10. D p OMT hite a 7 Black 4 D Yi Yi FOUNDATION FIELDBUS O2 D 4 Z OO OO OO0OO0OO0OO D Uy D o oo amp Orr IO O grarus PORT2 YQ QI Blac AC Power l Black Connection White 24 Power White Connection If indicator lights do not light reverse polarity of 24 V leads O Olo Fieldbus Power QO o Conditioner with Terminators ae j RELCOM INC terminators usedin this example S s O0 Wire to Fieldbus device Hae 7i To open the connector push down hard on the small white lever Auxiliary Terminal Block Auxillary Terminal Block 43187 2 Connect the CN2FF and the other Fieldbus Devices to the Relcom terminal block Publication 1757 UMO06A EN P May 2002 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 Open the small door on the top of the 1788 CN2FF and set the rotary switches to an unused ControlNet Mac ID In the examples that follow Mac ID 9 has been used The units digit is on the right wh
11. kh ee ee es es i So 7 by i BS Allen Bradley Fieldbus Solutions for Rockwell Automation s Integrated Architecture ProcessLogix ControlLogix and PLC5 User Manual _ gt cats A 7 7 f F B 4 d f ae o Ge ee ae o Vee a ey Shy gt Wee ee Ta ate L ion mm L m m 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 In no event will Allen Bradley be responsible or liable for indirect or consequential damage resulting from the use or application of these products Any illustrations charts sample programs and layout examples shown in this publication are intended solely for purposes of example Since there are many variables and requirements associated with any particular installation Allen Bradley does not assume responsibility or liability to include intellectual property liability for actual use based upon the examples shown in this publication Allen Bradley publication SGI 1 1 Safety Guidelines for the Application Installation and Maintenance of Solid State Control available from your local Allen Bradley office describes some important differences betwee
12. 2 29 Foundation Fieldbus Performance 005 2 30 INO UIICAR OMe CMC IMes ca eminin eoice hip bee Gs aici ee ee i 2 32 Fieldbus versus ProcessLogix Alarm Priorities 2 32 Fieldbus Alarm Conditions 00005 2 33 Alert Object Formal Model aaau aaua oe ba ae we 2 35 1757 FIM Planning Considerations Configurating the 1757 FIM Table of Contents vil Chapter 3 Relerence PUDNCANONS 6404 44 bo awe hems Ged x eb a 3 1 Installation declaration nnan aaaea 3 2 FIM and I O module allowance 3 3 Fieldbus network references n nanana aaa 3 3 Fieldbus wiring selection and calculation 3 4 Installing 1757 FIM Fieldbus Interface Module 3 4 Installing 1757 RTP Remote Terminator 3 4 Chapter 4 Belote OUS rey renee te arana E S R be 4 1 Configuring Fieldbus Components In a Control Strategy 4 3 About ProcessLogix control strategy configuration 4 3 Example Application and Control Strategy for Proced r il REICIENCS crestere oid bof eho ain 4 4 System Management Timers oeieo ra a EE EN 4 6 ACSYNCINIR g ss sero pitate toed edo E E 4 8 Adding Fieldbus Interface Module to Project 4 9 Checking link configuration a tii oi hehe aaa 4 12 Making a Fieldbus Device Template from a vendors WO Oi 4 dere dota dt ak ae de a 4 17 Making a fieldbus device template from existing definition DEF files 4 22 Adding a Fieldbus Device
13. Network Management description Network Management provides the following capabilities for managing the communication system of a fieldbus device e Loading a Virtual Communication Relationship VCR list or single entries in this list A VCR represents a communication channel through the complete communication stack e Configuring the communication stack e Loading the Link Active Schedule LAS e Monitoring performance and e Monitoring fault detection The collection of managed variables is called the Network Management Information Base NMIB System Management Description System Management provides the following functions to coordinate the operation of various devices in a distributed fieldbus system e Assigning node addresses for devices e Synchronizing the application clock e Distributing application scheduling across the link and e Providing support for locating application tags It provides the needed facilities for bringing new devices on the link to an operational state and for controlling the overall system operation Information which is used to control system management operation is organized as objects stored in the System Management Information Base SMIB Integrating Fieldbus into Rockwell Automation Logix System 2 1 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 Syst
14. Publication 1757 UMO06A EN P May 2002 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 m r DD Member Id 2 2 m Key Index ON AV 3 Gm Data Type 3 1 m Meta Type RECORD 3 2 m r Type Name Alert 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 4 m r Mfr Type Unsigned8s 4 5 m 1 Message Type Unsigned8 4 6 m r Priority Unsigned8 4 7 m r Time Stamp Time Value m r Data Length m r Units m r Usage CONTAINED m r Storage DYNAMIC 9 m r List of Valid Values Standard type enumerations 0 12 are defined Message type enumeration s 0 3 are defined see attribute definitions 10 11 m r Initial Value m r DD Item Id Services 1 2 m FB_Alert_Notify m FB_ Alert Ack Publication 1757 UMO06A EN P May 2002 2 36 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 Table 2 L Attribute Definitions Attribute DD Member Id Index Meta Type Type Name sub index Data Length Units Definition A unique number which identifies the alert This number will be assigned as
15. Represents the mode record of the block Contains the Actual Target Permit ted and Normal modes DS 69 C Mode 4 Standard Function Block Parameters A 29 Nxxx Blocks Oxxx Blocks Valid Views Storage Remarks VIEW_1 VIEW_3 mix 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 Permit ted Non Volatile for Target mode and Dynamic for Actual mode The data type consists of bit strings for Actual Target Permitted and Normal modes It uses the following four elements e arget e Actual e Permitted e Normal Table A 79 NV_CYCLE_T Classification Simple Variable Description Defines interval between writing copies of Non Volatile NV parameters to NV memory Zero means never FF Data Type Unsigned 32 Range Positive Usage C Contained Length 4 Valid Views VIEW_2 Storage Static Remarks Ready Only Table A 80 OUT Classification Record Description Represents the primary analog value calculated as a result of executing the function FF Data Type DS 65 Range OUT_SCALE 10 percent Usage 0 Primary Output Length 5 Publication 1757 UMO06A EN P May 2002 A 30 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Valid Views Storage Remarks Classification Description
16. gt TRK_VAL FF_VAL gt ___BKCAL_OUT RCAS_OUT PD FF_VAL BKCAL_OUT P OUT p gt RCAS OUT ROUT OUT ROUT _OUT Setpoint Bypass Feed Forward Output CASLIN SP RATE_DN BYPASS FF SCALE OUT_HI_LIM OUT SP_RATE_UP FF_GAIN OUT_LO_LIM per ee Control SP_LO_LIM CRIN BIAS SP __ BAL_TIME Status T RATE BKCAL_HYS IN _ _ Filter PV PV_FTIME im Alarm faces Output Track Mode TRK_SCALE SHED_OPT TRK_IN_D TRK_VAL Table 1 K Proportional Derivative Block The Proportional Derivative function block provides classic two mode control function for processes that handle their own integration When the Process Variable deviates from the Set point the PD function acts upon the error to move the output in a direction to correct the deviation PD blocks support cascade applications to compensate for the difference in process time constants of a primary and secondary process measurement A functional schematic of the block is shown in Figure 1 11 for reference Function Notes e Supports Out of Service OOS Initialization Manual I Man Local Override LO Manual Man Automatic Auto Cascade Cas Remote Cascade RCas and Remote Qut ROut modes e The inpu
17. 150 FFstatus uint8 Bad an of Service Fieldbus status of the value obtained from the Fieldbus device 151 TagDesc string As configured Tag of the Fieldbus function block that is represented by this object instance Publication 1757 UMO06A EN P May 2002 All attributes in Table 7 A are created if a standard Fieldbus AI function block is connected to a channel of an MAI block Otherwise only Value CNStatus TagDesc and FFstatus are created Alarm Handling for Analog Inputs You can configure Fieldbus AI function blocks to detect and report alarms Four process alarms HI_HI_ALM HI_ALM LO_LO_ALM and LO_ALM are exposed through the ControlNet AI object When you connect an AI function block to an MAI block the NI FBUS Configurator configures the field device to send the four alarms to the linking device In Fieldbus terminology confirming an alarm means that the alarm has been received by an operator and acknowledging an alarm means that the operator has taken the necessary action When an alarm condition is detected by a Fieldbus function block the alarm is said to be ACTIVE An active alarm should be Acknowledged Analog Outputs 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
18. 192 153 194 155 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 side FailStateValue uint8 Set The linking device writes the value to the DO block when this attribute is changed by the controller TagDesc String Get As configured Tag of the Fieldbus function block that this object instance represents Failstatelime Float Set The linking device writes the value to the DO block when this attribute is changed by the controller ReadBack uint8 Get This represents the BKCAL_OUT _D value from the DO block BkCalStatus uint8 Get Bad Not This represents the status of the Connected Readback attribute casInstatus uint8 Set Bad Not This represents the status of the connected CAS_IN_D to the DO block The BkCalStatus is created only when the controller is capable of participating in the CAScade initialization handshake that is when the BKCAL_OUT_D of the DO block is wired to a BKCAL_INx parameter of the MDO block Only Value CNStatus casInstatus ReadBack and TagDesc are created when an MDO channel is connected to something other than a DO function block CAS_IN_D parameter Publication
19. If you find a problem or have a comment about this manual please notify us of it on the enclosed How Are We Doing form at the back of this manual If you have any suggestions about how we can make this manual more useful to you please contact us at the following address Rockwell Automation Allen Bradley Company Inc Control and Information Group Technical Communication 1 Allen Bradley Drive Mayfield Heights OH 44124 6118 Publication 1757 UM006A EN P May 2002 About this document P 4 Notes Publication 1757 UMO06A EN P May 2002 About this Document The Fieldbus Communication Model Table of Contents Important User Information nnsa aaa hae a il Preface COMMIS PUICS oe eee e eee eG a P 1 CONV COUOINS eisin en E Rin E Ue ee iw EAR E EN P 2 Rockwell Automation Technical Support P 3 Local Product Support osaa aaa P 3 Obtain Technical Product Support P 3 Your Questions or Comments about This Manual P 3 Chapter 1 Fieldbus Organizatie ee nebus artea i deat aan ee ed 1 1 About the Fieldbus Foundation 1 1 Want more information naaa aa 1 1 Wpat TS Pedi asea a aa 1 1 Open Communications Architecture 1 3 Communication Layer Description 1 4 Standard Function Blocks n n a uaaa aaa 1 6 About Modes of Operation 0 aaa 1 8 Analog Input BIOCK 22 2 leuuceoiy eee uii as xe 1 9 ANJOS Oulpur BIOCK anere ainra P
20. Valid Views Storage simple Variable Identifies state of discrete input that will generate an alarm Unsigned 8 PV state C Contained 1 VIEW_4 Static Table A 32 DISC_PRI Classification Description FF Data Type Range Usage Length Valid Views Storage simple Variable Identifies the priority of the discrete alarm Unsigned 8 0 to 63 C Alert Priority 1 VIEW_4 Static Table A 33 DV_HI_ALM Classification Description FF Data Type Usage Length Storage Remarks Record Identifies the status and time stamp associated with the high deviation alarm DS 71 C Alarm 16 Dynamic Read Only The Data type consists of data that describes floating point alarms It uses the following five elements e Unacknowledged e Alarm State e Time Stamp e Subcode e Value Standard Function Block Parameters A 13 Table A 34 DV_HI_LIM Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the high deviation alarm limit setting in engineering units Float 0 to PV Span infinity C Contained 4 VIEW_4 Static Initial value Is infinity Table A 35 DV_HI_ PRI Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines priority of the high deviation alarm Unsigned 8 0 to 63 C Alert Priority 1 VIEW_4 Static Initial value is 0 Table A 36 DV_LO
21. a single CN2FF you must 1 Check both ports now 2 Configure both Fieldbus networks 3 Perform two downloads The reason you must do both Fieldbus networks at the same time is that when you restart this Add Links function you delete the data from the first download 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 Wait until the software is finished gathering data It will be finished when the working icon disappears Although you see nothing going on there is a lot of Fieldbus communication going on If you see yellow circles with an exclamation mark in them that indicates that the FFCT configuration software doesn t understand that device This is a caution and needs to be addressed UNK to the right of a the name of a Function Block that means again that the FFCT doesn t recognize that Function Block These indicate that the DD s for those devices were not loaded or did not match the data that the FFCT read from the device ATTENTION You can t use a Function Block with a UNK note The UNK is a show stopper You need to get a more current DD from the device manufacturer Publication 1757 UMO06A EN P May 2002 F 22 1788 CN2FF Ins
22. 5 Publication 1757 UMO06A EN P May 2002 A 4 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Valid Views Storage Remarks Classification Description FF Data Type Usage Length Valid Views Storage Remarks Classification Description FF Data Type Usage Length Valid Views Storage Remarks VIEW_3 Non Volatile The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Table A 9 BKCAL_OUT Record 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 DS 65 O Back Calculation Output 5 VIEW_3 Dynamic The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Table A 10 BKCAL_OUT_D Record The output value and status provided to an upstream discrete block that Is used to provide bumpless transfer for closed loop control DS 66 O Back Calculation Output 2 VIEW_3 Dynamic The data type consists of the value and status of discrete value parameters It uses the following two elements e Status e Value Standard Function Block Parameters A 5 Table A 11 BKCAL_SEL_1 Classification Description FF Data Type Usage Length Valid Views St
23. Ee EEEE eae ee Redundant Controllers Data Highway 1771 Remote 1 0 Eat OAOA DODE LE DA DA A PLC5 C Controller SLC Controller ControlNet Flex Ex Publication 1757 UMO06A EN P May 2002 1757 FIMRTP 9 9 FIM va va G ControlNet 1 0 ControlNet ProcessLogix and ControlLogix m J m 1 A L i n i 1788 CN2FF J 1757 FIMRTP m J Y FIM Data Highway o FOUNDATION Fieldbus A OOOO ControlNet a B EB E B Pressure SLC Controller Transmitter PLC5 1771 Remote 1 0 l Controller ControlNet oo m 1788 CNZFF aa Flex Ex are Th petri Pressure PLC5 C Controller Transmitter 43190 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 Foun
24. For this reason once a configuration has been stored into the linking device if the user wires more Fieldbus devices with NI FBUS additional object instances are created and additional offsets are appended to the assembly objects the existin The individual instances increment from the last one used in the category The offsets within the assembly objects are assigned in the same order as described previously but are placed after existing offsets For example assume you have two MAI channels and one MDO channel with cascade initialization The instances and offsets are created Sometime later you need to add an additional MAI channel and two MAO channels to your configuration These additions are placed after the final MDO from the previous configuration Because existing programs may be using a configuration the deletion of a linkage from a Fieldbus network does not result in a renumbering of ControlNet objects or a reordering of the assembly object offsets If the Fieldbus device is no longer present Fieldbus and ControlNet status indicates an error condition and the object and assembly offset Publication 1757 UMO06A EN P May 2002 7 18 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Trends and Alarms Publication 1757 UMO06A EN P May 2002 resources continue to be in use In order to remove existing objects from a configuration you must remove the existing configuration To accomplish this se
25. Function Notes e Supports Out of Service OOS Initialization Manual IMan Local Override LO Manual Man Automatic Auto Cascade Cas and Remote Cascade RCas modes e The input 1 IN_1 value to be ratioed passes through a filter with a time constant of RA_FTIME The filtered value is multiplied by the Set point SP and GAIN to become the target output The GAIN controls the number of zeros in the SP display e The input IN value is the actual value of the ratioed variable and it passes through a filter with a time constant of PV_FTIME The filtered IN value is divided by the filtered IN_1 value and the GAIN to become the PV The units of IN are not PV but OUT The units of IN_1 are OUT units divided by PV units Publication 1757 UMO06A EN P May 2002 1 26 The Fieldbus Communication Model Table 1 M Ratio Block Specifications Function Notes e The full cascade SP sub function is used with rate and absolute limits Additional control options are available to cont 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 If this option is OFF or to pass a status of Not Invited NI or Initialization Request IR at BKCAL_IN will be passed to BKCAL_OUT The BKCAL_OUT value will be calculated from the value of BKCALC_IN divide
26. Length 1 Valid Views VIEW_4 Storage Static Remarks Initial value is 0 Table A 59 HI_LIM Classification Simple Variable Description Defines the high alarm limit setting in engineering units FF Data Type Float Range PV_SCALE infinity Publication 1757 UMO06A EN P May 2002 A 22 Standard Function Block Parameters Ixxx Blocks Publication 1757 UMO06A EN P May 2002 Usage C Contained Length 4 Valid Views VIEW_4 Storage Static Remarks Initial value is infinity Table A 60 HI_PRI 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 61 10_OPTS Classification Simple Variable Description Identifies user selectable options for altering the Input and Output block pro cessing FF Data Type Bit String Usage C Contained Length 2 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 62 10 OPTS Bit Selections oe eee Os ae E E C i i ESOS Re 2 Cr a es ee E E ee Standard Function Block Parameters A 23 ff Wiener Pd eT E e a A A e S a A e S S x e onnie ff o X_ fs perenn TTX ofw a e C fe fees fe fewes e e fe fewes rs ewes Table A 63 IN Classification Record Description Represents the primary input va
27. Publication 1757 UM006A EN P May 2002 F 34 1788 CN2FF Installation Example 6 Select the Show Hide Transducer block icon from the toolbar to display the hidden transducer block Ha sal Ei 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 eee E H Pressure Transmitter ID 452B4 fa E H Pressure Transmitter TRANSDUCER TBPR Miel Fa Apply Values TRANSDUCER TEPA aasal ajsa Haka M Periodic Updates 2 sec 005 Auto Manual Process Diagnostics Trends Others Parameter Value 74G_DESC EuH PRESSUREMETER B MODE BLE TARGET 005 ACTUAL m 005 PERMITTED Auto Man 005 NORMAL Auto Write Changes Read All Publication 1757 UMO06A EN P May 2002 8 10 11 12 13 14 15 16 17 18 1788 CN2FF Installation Example F 35 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 p gt 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 It should also be in Auto Mode If it is not attempt to manually set
28. The Publisher Subscriber type handles the publishing of User Application function block data on the network Defines how fieldbus devices exchange User Application messages across the fieldbus using a set of standard message formats It uses object descriptions that are stored in an object dictionary OD to facilitate data communication The OD also includes descriptions for standard data types such as floating point integer Boolean and bitstring A Virtual Field Device VFD mirrors local device data described in the OD A physical device may have more than one VFD Provides these communication services to standardize the way the User Applications such as function blocks communicate over the fieldbus Context Management Object Dictionary Variable Access Event Upload Download and Program Invocation Uses a formal syntax description language called Abstract Syntax Notation 1 ASN 1 to format FMS messages and applies special behavioral rules for certain types of objects Publication 1757 UMO06A EN P May 2002 Associated Terms H1 31 25 kbit s signal rate H1 Link H1 Segment HSE High Speed Ethernet Compel Data CD message Pass Token PT message Time Distribution TD message Live List Link Active Scheduler LAS Virtual Communication Relationship VCR Object Dictionary OD Virtual Field Device VFD Network Management Information Base NMIB system Management Information Base SMIB The Fieldbus Commun
29. This completes the firmware upgrade 12 Click OK The LINK Parameters window closes FIM LED indications As shown in Figure 6 1 the FIM has one four character display and three two color LEDs on its front panel From left to right the LEDs provide Link 1 status Link 2 status and module health status respectively The following table summarizes some typical indications for reference Figure 6 1 FIM front panel indicators Table 1 FIM LED Interpretations 4 Character Display gt Link 1 Status LED gt amp lt WY Module Health LED liane 2 Status LED Publication 1757 UMO06A EN P May 2002 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 Oft 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 DY In its READY state and ready for its Boot image load JJ Solid or Flashing Green Alternating link states as noted inthe Operating normally If solid green there are ProcessLogix Control following rows Data Access CDA connections to the FIM lf Link 1 or Link 2 LED is And 4 Character Display shows Then LINK is Off or Flashing Red Flashing Green X FW Loading firmware Down offline Flashin
30. although it may be limited The operator directly sets it through an interface device The algorithm must initialize to avoid a bump when the mode switches The Set Point may be maintained initialized to the Process Variable parameter value or initialized to the Set Point value associated with the previous retained target mode Automatic Auto The block s normal algorithm uses a local Set Point value to determine the primary output An operator may set the value of the Set Point through an interface device Cascade Cas The block s normal algorithm uses a Set Point value fed through the Cascade input parameter from another block to determine the primary output value Remote RCas The block s Set Point is being set by a Control Application running on an interface device through Cascade the remote cascade in parameter The block s normal algorithm uses this Set Point to determine the primary output value The block maintains a remote cascade out parameter to support initialization of the control application when the block mode is not remote cascade Remote Out ROut The block s output is being set by a Control Application running on an interface device through the remote output in parameter The algorithm must initialize to avoid a bump when the mode switches The block maintains a remote output out parameter to support initialization of the Control Application when the block mode is not remote output The Set Point may be maintained or initialize
31. e Worst Case Alarm Indication e Upstream Block Class Identification Publication 1757 UMO06A EN P May 2002 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 B Breakdoun of bit assignments Substatus if Quality field is Limits BAD UNCERTAIN GOOD GOOD Cascade Non Cascade 0 1 D O1 O gt co N BAD Data Quality Non Specific Non Specific Non Specific Non Specific No Limits UNCERTAIN Data Configuration Error Last Usable Value Active Block Alarm Initialization Low Limit Quality Acknow ledge IA GOOD Not Connected Substitute Active Advisory Initialization Request High Limit Non Cascade Alarm IR Data Quality GOOD Cascade Device Failure Initial Value Active Critical Not Invited NI Constant Data Quality Alarm Sensor Failure Sensor Conversion Unacknow ledged Not Selected NS Not Accurate Block Alarm No Communication with Engineering Unit Unacknow ledged Do Not Select DNS Last Usable Value Range Violation Advisory Alarm No Communication with Sub Normal Unacknow leged Local Override LO no Last Usable Value Critical Ala
32. would help the synchronization 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 You can configure a FIM block in the Control Builder Project tab without the FIM hardware installed However it is good idea to have the communications D gt driver and hardware that is going to be used for the system installed and configured The FIM needs the name of the communications driver specified on its configuration form to complete its configuration data Like the CPM the FIM represents a hardware module and the block configuration specifies the communication path to the hardware 3 With Control Builder running click New gt Interface Modules gt FIM Fieldbus Interface Module Controllers REAN A ET esi Module aat TEESE ae eee Sale a Modules Sr ETERA ee we Rn i Expo ee Import AEN E Name FIMS50 Address Information Network Type Driver Name Supervisory Chassis MAC Supervisory Chassis Slot Number 17 I Remote Chassis Remote MAC Address Remote Chassis Slot Number State of Module s Redundancy NONREDUN 7 FIM Command NONE FIM State OK M Show Parameter Names Cancel Help Publication 1757 UM006A EN P May 20
33. 1757 UMO06A EN P May 2002 7 14 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Alarm Handling by the HMI Assembly Objects Publication 1757 UMO06A EN P May 2002 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 In general all alarms except the AI and DI process alarms must be handled by a Fieldbus HMI You must configure the linking device to receive such alarms and forward them to a PC based HMI on ControlNet You set up the linking device as shown in Figure 7 9 Figure 7 9 Setting Up an Alarm Function Block Applicati Loop Time 1 5 Stale Lirnit b z T 24 PidControl PIC In OUT P Poa N EKCAL OUT fF CN FF Linking Device PPEKCAL IN Alans BY Alums TRE IN D Trends J Trends TRE VAL RFF VAL If you connect the AI and DI alarms to the linking device the linking device forwards all alarms from these to the HMI The process alarms are also visible to your PLC processor through the ControlNet objects You must ensure through your application design that either the HMI or the PLC processor acknowledges the process alarms For each channel that you connect on the MAI
34. 19 Pass Token 20 Probe Node 21 lt answer from our new Node 21 gt Pass Token 17 Pass Token 18 Pass Token 19 Pass Token 20 Pass Token 21 this one is in the Live List now Probe Node 22 etc You can see that the token is passed around the ring perhaps 200 times between Probes of inactive addresses to see if there is someone new Software Example Forever End Forever For each address not in the Live List For each node in the Live List Pass Token lt node transmits if it has something to say gt lt node returns token gt end For Probe Address to see if a Node is there now if Node answers add to Live List Publication 1757 UMO06A EN P May 2002 4 8 Configurating the 1757 FIM ACSYNCINTR Publication 1757 UMO06A EN P May 2002 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 This is important so that the Function Block will be Done Executing at the time it is Scheduled to Publish the answers outputs of the Function Block to other nodes on the Fieldbus On H1 the LAS will tell the node through a Compel Data message when to Publish but it is up to the node to schedule block execution at the right time If the crystals of the clocks of all the Fieldbus Nod
35. 3 4 and 150 placed into the required input assembly object Fach MAI channel requires 6 bytes in the input assembly object MAO Blocks For each MAO 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 155 placed into the required output assembly object Additionally if your controller participates in cascade initialization for a specific channel wiring BKCAL_OUT from AO attribute 154 is placed into the required input assembly Fach MAO channel requires 6 bytes in the output assembly object and 6 bytes in the input assembly if cascade initialization is performed 4 bytes in the input assembly if cascade initialization is not performed Publication 1757 UM006A EN P May 2002 7 16 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Publication 1757 UMO06A EN P May 2002 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 MDO Blocks For each MDO 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 155 placed into the required ou
36. 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 The link data transfer schedule is derived from the portion of the link schedule that deals with publication of parameters The Control Builder CB provides a default link schedule of publications and function block execution phasing based on the function block connections in the user configured control strategy The basis for the link schedule is this link s content from all currently loaded Control Modules CM Execution phasing is based solely on function block existence in the CM Order of execution is based on the order in CM ORDERINCM parameter for each block Publications are based on inter device function block connections and device to ProcessLogix or ProcessLogix to device function block connections The following publication rules apply e Function block publications appear in the link data transfer schedule in the order specified by their ORDERINCM parameters Duplicate values of ORDERINCM may produce indeterminate ordering of those blocks involved If the user changes the sequence of execution order for function blocks in a schedule the ORDERINCM parameters of
37. BLOCK_ERR OUT_SCALE STATUS_OPTS BKCAL_IN GRANT_DENY SEL_1 STRATEGY BKCAL_SEL_1 MODE_BLK SEL_2 TAG_DESC BKCAL_SEL_2 OUT SEL_3 UPDATE_EVT BKCAL_SEL_3 OUT_HI_LIM SEL_TYPE BLOCK_ALM OUT_LO_LIM ST_REV Publication 1757 UMO06A EN P May 2002 Discrete Input Block Transducer i DI CHANNEL Simulate SIMULATE_D Mode SHED OPT The Fieldbus Communication Model 1 17 Figure 1 8 Functional Schematic for Discrete Input Function Block OUT Optional Filter Invert PV_FTIME FIELD VAL D OUT_D Alarms DISC Table 1 H Discrete Input Block Specifications Description Function Notes Parameters see Appendix A for definitions of each parameter 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 A functional schematic of the block is shown in Figure 1 8 for reference Supports Out of Service OOS Manual Man and Automatic Auto modes The FIELD_VAL_D represents the true ON OFF state of the value from the Transducer using XD_STATE Use the IO_OPTS Invert selection to do a Boolean NOT function between the field value and the output The PV_D is always the value that the block places in QUT_D when the mode is Automatic In Manual mode if allowed an operator can write a value to OUT_D
38. CN2FF Hew Clone Delete Apply Help 3 Create a New Topic refer to page F 7 4 Start with a TCP 1 interface navigate to and highlight the CN2FF 5 Click Apply Publication 1757 UMO06A EN P May 2002 F 50 1 88 CN2FF Installation Example 6 Select Advanced Communications DDE O PC Topic Configuration mytftopic Fath_from_mp_PC_to_mp_CH2FF TCP to on 130 aG This is the path a from your PC via TCP 1 to Mac ID 7 OP IM627 7 Read the Path and copy it to the Path window of the Interface window refer to page F 12 Interface That s it Congratulations You have told the Fieldbus Configuration software the path to communicate with the remote CN2FF Publication 1757 UMO06A EN P May 2002 Troubleshooting an Application 1788 CN2FF Installation Example 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 NI FBUS Fieldbus Configuration System a Fle Edt View Configure oom Window Help e Ha zsa zi oA Function Block Application Demo Sys LD 11 a Device Info To see the Transducer Block you must uncheck the T in the top toolbar that initially had a red X through it The Fieldbus A
39. EN P May 2002 Device Descriptions and Block Parameters The Fieldbus Communication Model 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 The Fieldbus Foundation provides Device Descriptions for all standard Function Blocks and Transducer Blocks on a CD ROM Manufacturer s provide an Incremental DD that references the standard DDs and describes manufacturer specific features such as calibration and diagnostic procedures added to their devices Device Description Language The Device Description Language DDL is a structured text language used to write a DDL source file A DDL source file describes each device function parameter and special feature as well as how a field device can interact with a host application and other field devices A completed DDL source file is converted into a binary formatted DD output file The DD output file information can be provided in object form in the device itself or on a removable storage media delivered with the device A field device s Object Dictionary OD can be transferred from a device to a host using standard Fieldbus Message Specification services
40. FF devices should be supplied by the manufacturers of all Registered Fieldbus devices The 1788 FFCT must have the DDs for each FF devices to configure that FF device Imagine that you find yourself in a mill that has been controlled by an old DCS systems that has been updated using Fieldbus You have been asked if there is any way for one of your systems ProcessLogix ControlLogix or CompactLogix to interface to the existing Fieldbus devices Yes Rockwell Automation offers ControlNet to Fieldbus linking device called a 1788 CN2FF which interfaces a ControlNet network with a Fieldbus network Connect Fieldbus Devices and Configure Linking Device to Gather Data In this lab example you will connect to Fieldbus devices on the Fieldbus network and then configure the 1788 CN2FF Linking device to gather data from the devices Use 1788 FFCT Software Rockwell Automation uses the 1788 FFCT software to configure the Fieldbus part of the system The software is manufactured by National Instruments Publication 1757 UMO06A EN P May 2002
41. Foundation provides the standard Function Blocks listed below for basic control functionality They also support additional blocks for more complex applications Please refer to the applicable Fieldbus Foundation specification for more information about these additional blocks Table 1 B Function Block Specifications Function Block Class Analog Input Input Analog Output Output Bias Gain Control Control Selector Control Discrete Input Dl Input Discrete Output DO Output Manual Loader Control Proportional Derivative ce Control Proportional Integral Deriva ie Control tive Ratio Control 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 3 Using Function Blocks in Fieldbus Devices to Form a Control Loop Fieldbus Device 1 an Device 2 Publication 1757 UMO06A EN P May 2002 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 nor
42. Good Cascade Interface Connections Summary Since the downstream action with the upstream feedback is the same for all fieldbus blocks there are essentially the following six types of interface connections through the FIM e Analog process value into the FIM e Discrete process value into the FIM e Analog process output from the FIM e Discrete process output from the FIM e Analog process output from the FIM with backcalculation feedback Integrating Fieldbus into Rockwell Automation Logix System 2 17 e 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 The FIM can also monitor subscribe to the data published between the functions blocks of these fieldbus devices Fieldbus status data details According to Foundation Fieldbus specifications every fieldbus function block input and output connection must support a status byte that provides the following status indications e Data Quality usability e Bad Data Cause e Degraded Data Cause e Limit Conditions e Cascade Control Initialization Rejection e Fault State Initiation Indication e Local Override Indication
43. LD 11 Tramning Unit P FE Device Info DO NOT change the gt Pe mesource iu names or Properties of esa CMetMachd11_4I_ModuleQ_0 CHAI these tags ad CNetMacld11_Al_Modulel_0O CNAI ad CNetMacld11_A0_Module0_0 CHAO ad CNetMacld11_A0_ Modulel_0 CHAO ad CNetMacld11_DI_ModuleO_0 CHDI ad CNetMacld11_DO0_Module0_0 CNDO F SHAR FF tol 2 a FR 3051 E FR RE AB e FA Fres Al aoa FA Temp Al P ad FR PID PID OK to change Ed FR ISEL ISB the names or gd FR CHAR SCB Properties of gd FR ARITH AB these tags ad FR INTEG IB Ey T Hw Press B HW PRES RB AB f Hw PRES Al Al Hwlemp PID PID 5 Hw TEMP Hw TEMP RB RE ao HV TEMP Al Al HwlempPiD PID Publication 1757 UMO06A EN P May 2002 F 26 1788 CN2FF Installation Example Publication 1757 UMO06A EN P May 2002 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 Set Tag FR 3051 3 1D 0011513 New Taq AEGEE W Setto O05 mode Set Cancel Short names are easier to read in Device Info which you ll use later 4 Check the Device addresses The devices on
44. Linkmaster DL Operational Functional Class LINE MASTER 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 gt 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 The Change Online Value prompt opens Change OnLine Value OLBASCHAR OPRFUNCCLAS BASIC Ves Moa 6 Click Yes to acknowledge the change 7 Click OK to close the window Checking live list and interacting with uncommissioned devices Use the following procedure to check the link for devices that are added to the Live List as uncommissioned LINK 51071 The asterisk signals that an uncommissioned device has been added to the link Publication 1757 UMO06A EN P May 2002 Operating the 1757 FIM 5 7 2 Click the I to expand the Link Monitoring on FIM_B1 Eli LINK_S101 i ST DEFOIED i a Eaa Tt LINE S102 3 Double click the uncommissioned device icon oh The LINK Parameters window opens SYSTEM LINK Block LINK_S101 Parameters Monitoring Ea xi Main System Management Network Management Application Uncommissioned Devices Server Parameters a Tag Addes Range Device ID Vendor Modei Name ta 0x15 Perman 4
45. MAO MDI and MDO blocks the linking device creates an instance of a ControlNet object corresponding to the type of channel These individual instances are useful for unscheduled querying and setting object information For scheduled communications on ControlNet the linking device takes specific attributes from the corresponding object instances and combines them into input and output assembly objects The linking device uses input assembly objects to produce data on ControlNet and output assembly objects to consume data from ControlNet The definition of assembly objects is determined after you configure the MAI MAO MDI and MDO blocks on the linking device Assembly offsets are 0 based and increment by the size of data placed into them 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 E Attributes in Input and Output Assemblies Attributes in Input Attributes in Output Object Type Assembly Assembly Al 3 4 150 AO 153 154 3 4 155 CAScade initialization AO 153 3 4 155 NO CAScade initialization DI 3 4 150 DO 153 154 3 4 155 CAScade initialization DO 153 3 4 155 NO CAScade initialization MAI Blocks For each MAI block configured in the linking device beginning with the lowest numbered module each channel that is connected to a Fieldbus function block has attributes
46. Management set address wait timer in 1 32 millisecond increments 8 10 11 Configurating the 1757 FIM 4 15 In the Local Clock Time Offset CLOCTIMDIFF 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 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 System management sets it during node address assignment Set it 5 because this is a good compromise for more information see page 4 6 In the Addr of Lnk Primary Time Pub PTIMEPUB field either leave the default value of 20 or enter a new value This value is the node address of the primary time publisher for the local link System Management sets it during node address assignment It is a configuration error if the SM Support SM_SUPPORT parameter of the device specified by this node address does not have the Application Clock Synchronization feature bit set To enable the SMK Operational Power Up state OPERPWRUP click the check box next to the field e If the device is in the SM_OPERATIONAL state or fully commissioned and operating when power is lost this parameter controls which state the SMK will enter after powerup e If OPE
47. OOS mode If it shows OOS change it All the Function Blocks including RB should be in the Auto mode Be sure the RB Function Block is in Auto Mode as Rosemount 1151 ID 0011513051280000002 0 a 28 Pres RB AB vee al TRANSDUCER TB Rosemount Temp ID 0011513244 FR TEMP 0 vee Re RESOURCE RB gt vn T Temp Transducer TB ia FTA 1004 Al Publication 1757 UMO06A EN P May 2002 1788 CN2FF Installation Example F 53 The Transducer FB window opens EJ Honeywell Attached XD DEFB2D Apply Values 4D DEFB2D6 ST SO00T EB ras a4 E sec O05 Auto Process Diagnostics Trends Others Parameter TAG DESC El MODE BLE TARGET ACTUAL DCCOMITTOM Write Changes If the OOS is active Table F3 If Then the OOS is active e Click on the Auto button to put the Transducer Block in Auto mode the Transducer goes into Auto mode and if e The bad data indication will go that was your only problem away the Transducer FB doesn t go into Auto e Check the mode of the Resource Block and the Al Block e All should be in Auto Mode e f the Transducer will not go into Auto Mode refer to the FF device manufacturer for help e You also need to have the RB Resource Block in Auto Mode Publication 1757 UMO06A EN P May 2002 F 54 1788 CN2FF Installation Example Publication 1757 UMO06A EN P May 2002 List of Figures OSI versus Fieldbus communicatio
48. Status Byte haa el att tatus Fie UNCERTAIN Uncertain UNCERTAIN Uncertain L UNCERTAIN Uncertain H UNCERTAIN Uncertain C UNCERTAIN Unc LastOK UNCERTAIN Unc LastOK L UNCERTAIN Unc LastOK H UNCERTAIN Unc LastOK C UNCERTAIN Unc Subst L UNCERTAIN Une Subst H UNCERTAIN Une Subst C UNCERTAIN Unc Initial UNCERTAIN Unc NotAcc UNCERTAIN Unc NotAcc L UNCERTAIN Unc NotAcc H UNCERTAIN Une NotAcc C UNCERTAIN Unc SubNorm UNCERTAIN Unc SubNrm L UNCERTAIN Unc SubNrm H UNCERTAIN Unc SubNrm C GOOD Non Cascade Non Specific No Limits none GOOD Non Cascade Non Specific Low Limit GOOD Non Cascade Non Specific High Limit High Limit Publication 1757 UMO06A EN P May 2002 Fieldbus Status Display Indications B 3 Table B 1 Fieldbus Status Byte inal Independent Status Field GOOD Non Cascade Constant GOOD Non Cascade Alarm Block GOOD Non Cascade Alarm Blck L GOOD Non Cascade Alarm Blck H GOOD Non Cascade Alarm Blck C GOOD Non Cascade Alarm Advis GOOD Non Cascade Alarm Advis L GOOD Non Cascade Alarm Advis H GOOD Non Cascade Alarm Advis C GOOD Non Cascade Alarm Crit GOOD Non Cascade Alarm Crit L GOOD Non Cascade Alarm Crit H GOOD Non Cascade Alarm Crit C GOOD Non Cascade Alm U Block GOOD Non Cascade Alm U Blck L GOOD Non Cascade Alm U Blck H GOOD Non Cascade Alm U Blck C GOOD Non Cascade Alm U Advis GOOD Non Cascade Alm U Advs L GOOD Non Cascade Alm U Advs H GOOD Non Cascade Alm U Advs C G
49. Track in Manual selection must be true for this to occur in Manual mode If the actual mode is OOS or IMan the track request is ignored If the TRK_VAL replaces the OUT its status becomes Locked Out with Limits set to Constant The actual mode goes to LO The status of BKCAL_OUT RCAS_OUT and ROUT_OUT goes to Not Invited NI if not already there If the status of TRK_IN_D is Bad its last usable value will be maintained and acted upon If the device restarts losing the last usable value it will be set to false If the status of TRK_VAL is Bad the last usable value will be used If there is no last usable value the present value of the OUT will be used Use the Obey SP limits if Cas or RCas CONTROL_OPTS to use SP value after limiting in Cas or RCas mode Use the Use PV for BKCAL_OUT CONTROL_OPTS to the PV value for the BKCAL_OUT value Parameters ACK_OPTION DV_LO_LIM LO_LO_LIM SHED_OPT see Appendix A ALARM_HYS DV_LO_PRI LO_LO_PRI SF for definitions of ALARM_SUM FF_GAIN LO_PRI SP_HI_LIM each parameter ALERT_KEY FF_SCALE MODE_BLK SP_LO_LIM BAL_TIME FF_VAL OUT SP_RATE_DN BKCAL_HYS GAIN OUT_HI_LIM SP_RATE_UP BKCAL_IN GRANT_DENY OUT_LO_LIM ST_REV BKCAL_OUT H _ ALM QUT_SCALE STATUS_OPTS BLOCK_ALM HI_HI_ALM PV STRATEGY BLOCK_ERR HI_HI_LIM PV_FIIME TAG_DESC BYPASS HI_HI_PRI PV_SCALE TRK_IN_D CAS_IN HI_LIM RATE TRK_SCALE CONTROL_OPTS HI_PRI RCAS_IN TRK_VAL DV_HI_ALM IN RCAS_OUT UPDATE_EVT DV_HI_LIM LO_ALM RESET DV_HI_PRI LO_LIM ROUT_I
50. UMO06A EN P May 2002 Configuring Fieldbus Components In a Control Strategy Configurating the 1757 FIM 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 ProcessLogix R400 0 Control Builder includes a separate utility called the Fieldbus Library Manager application The Fieldbus Library Manager provides the capability to create templates for fieldbus devices based on the vendor supplied Device Description DD This means each fieldbus device has an associated template for viewing and defining the configurable attributes of its fieldbus function blocks These attributes include naming and identifying the component s location within the network as well as setting device and channel specific parameters as applicable ATENA The following information is only intended as a supplement to the Control Building Guide and does not repeat the basic functionality details for calling up navigating and interacting with the application Publication 1757 UM006A EN P May 2002 4 4 Configurating the 1757 FIM Example Application and Control Strategy for Procedural
51. Your values may be different 1788 CN2FF Installation Example F 45 Figure 6 Data Values TagName Vale Force Mask Style ews ooo o o m S E E O eC E E S T P CN2FF Datal2 BNF nl ee rr oaoa eso P o E io 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 Then you think that could end up being a lot of instructions if there were a lot of values A HA You think this is a great opportunity to take advantage of the User Defined Data Type feature of the ControlLogix processor We can take this cryptic information coming from the Linking device and with a single copy instruction have it formatted into tags which we can easily read and use Let s create a data type for the linking device 3 Go offline with RSLogix 5000 4 In the controller organizer right mouse on User Defined under the Data Types folder and select New Data Type from the popup menu 5 Set the name of the data type to FF_Linking_ Device 6 In the first line of the Name column for the members below type Pad 7 Tab over to the data type column and set th
52. a change in NAME results in an automatic change in PD_TAG to keep them the same However a change in PD_TAG does not result in an automatic change in the assigned NAME So the name and physical device tag can be different Since it is possible to change a physical device tag configuration using a handheld communicator you must be sure the device name specified on this configuration form matches the device name configured in the device Configurating the 1757 FIM 4 29 1 Double click the device icon in the Project tab example cascade ge example rmator 2 example pid r example scr 3 FIMO hid E i J5 1 ee 00 Po The Block Parameters window opens FLOWSER E LX1400FF_0502 Block LX1400FF_050240 Parameters Project ees Main System Management Network Management Server Name X1400FF_ 050240 Description Device Network Node Address 20 Device Identification Physical Device Tag Lxi 400FF_050240 Device State OFFLINE M Show Parameter Names Cancel Help 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
53. a series of System Management messages until it concludes that the System Manager has failed This is used for SET_ADDRESS sequence as shown in the following diagram As you can see to set a node s address requires several messages to be sent from the System Manager the CN2FF in our case to a node If the System Manager fails before completing all the steps the Remote Node must give up and resume operation at its previous settings The time for the remote node to wait after each step is called T2 I3 Specifies how long after a node is changed to a new address it might take for it to begin communication at the new address This time includes stuff like writing the new information to flash memory and re initializing some stuff but is primarily the time it takes for the Link Active Scheduler LAS the CN2FF in this case to Probe the Node at its new address 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 lt no answer gt Pass Token 17 Pass Token 18 Pass Token 19 Pass Token 20 Probe Node 33 lt no answer gt etc up to Probe Node 255 lt no answer gt Pass Token 17 Pass Token 18 Pass Token
54. acknowledge the build complete message Publication 1757 UMO06A EN P May 2002 4 24 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 These procedures assumes that Control Builder is running and you have made templates for the fieldbus devices that will be used in your application using the Fieldbus Library Manager utility TIP If a FIM and its associated Links exist in the Project tab you can drag and drop a fieldbus device from a gt directory in the Library tab directly to a Link The following procedure adds a fieldbus device to the offline Project tab and then shows how to assign it to a Link through the Assignment dialog box in the next procedure Once a device is assigned to a Link it represents a matching physical device that is to reside on the given Link Method 1 Drag and Drop 1 Click the in front of the applicable vendor template directory in the Library tab The directory tree expands to show stored device templates 2 Drag the device icon to a open area in the project tab The cursor appears with a when positioned in a vali
55. block is the software equivalent of an analog input module in an I O subsystem Each MAI block has eight channels with each channel containing a float and a status pair The linking device assigns a tag to each MAI block in the form CNetMacIdxx_Al_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 Inputs When the NI FBUS Configurator is started and continuously thereafter it lists all the devices and the function blocks in each device in its browse window This includes the AI function blocks in the Fieldbus devices and the MAI function blocks in the linking device You must connect the Fieldbus AI function blocks that will be accessed by ControlNet controllers or devices to the MAI channels as shown in Figure 7 1 Figure 7 1 Sample Single Macrocycle MAI Configuration Function Block Application Loop Time 1 sec Stale Limit 1 C R cali Sn TO od Oe hd ahd AI 101 3 AD The NI FBUS Configurator sets up the analog input devices to publish their data on Fieldbus The linking device MAI block subscribes to these values and produces them on ControlNet Each MAI block has its own schedule of subscribing on Fieldbus and producing on ControlNet For different rates macrocycle of production on Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device 7 3 ControlNet you must choose different M
56. box with the assign state icon Assigned Devices ST SOQ0FF_ Ost 1 6 Click Close Publication 1757 UMO06A EN P May 2002 4 28 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 7 Repeat the procedure to assign other devices TIP gt 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 TIP 4 While the device has been assigned to a link this is still offline configuration of a matching physical device that is to be connected to this Link Each device on the link must have a unique physical device tag PD_TAG that the fieldbus system relates to a node address The physical device tag node address and the manufacturer device identifier DEV_ID are used to match a configured device to a physical device In ProcessLogix each independent component in the control strategy must have a unique tag name NAME This is automatically enforced through the Control Builder application For this reason the unique name that was assigned to the device when it was created in project is also assigned as the device s physical device tag This is done to assure that the names are unique within the system This means
57. can be used to connect fieldbus devices to one another and a host Figure D 1 Overview of fieldbus wiring topologies Spurs Unterminated Terminator HOST Terminator Home Run Cable Trunk Junction Box Is Barrier Optional Terminator HOST f Ya V Terminator Junction Box I S Barrier Optional Terminator Junction Box HOST PS Terminator Home Run Cable Trunk Barrier Optional Maximum or acceptable cable distances may be significantly reduced by using Non FF spec wire gt Publication 1757 UMO06A EN P May 2002 D 2 Fieldbus Wiring Considerations Power Conditioning Publication 1757 UMO06A EN P May 2002 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 If an ordinary power supply is connected directly to the Fieldbus the power supply would absorb signals on the cable because it would try to maintain a constant voltage level The power conditioner puts an inductor between the power supply and the Fieldbus wiring The inductor connects the DC power to the Fieldbus wiring but prevents signals from going into the power supply In practice a real inductor is not used in the power
58. conditioner but an electronic equivalent The electronic inductor circuit has the added advantage of limiting the current provided to the network segment if the cable is shorted The voltage supplied to the Fieldbus cable can be as high as 32 V The voltage at any device can be as low as 9 V for the device to operate correctly A typical Fieldbus device takes about 20 mA of current from the cable The Fieldbus is configured so that one of the wires has a voltage the other wire has a voltage and the shield is grounded ORANGE BLUE GROUND A cable with the orange wire as plus and the blue wire as minus is shown above This type of cable is available from Fieldbus cable manufacturers Other cables or existing plant wiring conventions may be different Regardless of the color convention keep the sense of Fieldbus polarity consistent throughout the plant a IMPORTANT We suggest that you not use White Black or White Red pairs since they may be mistaken for 115 volt power wiring 1 RELCOM inc Fieldbus Wiring Design and Installation Guide 2221 Yew Street Forest Grove OR 97116 p 5 Reprinted by permission Power Distribution Signal Degradation Limitations Fieldbus Wiring Considerations 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 The number of devices on a fieldbus seg
59. describes floating point values for display purposes It uses the following four elements e Engineering Units at 100 percent e Engineering Units at 0 percent e Units Index e Decimal Point Table A 44 FF_VAL Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents the feed forward value DS 65 Input 5 VIEW_3 Non Volatile 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 e Status e Value Table A 45 FIELD_VAL Classification Description FF Data Type Usage Length Record Represents the raw value from the field device in percent of transducer span with a status reflecting the transducer condition before signal characteriza tion L_TYPE or filtering PV_FTIME DS 65 C Contained 5 Valid Views Storage Remarks Standard Function Block Parameters A 17 VIEW_1 VIEW_3 Dynamic 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 e Status e Value Table A 46 FIELD_VAL_D Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents the raw value of a field device discrete input with a status reflect ing the transducer condition DS 66 C Contained 2 VIEW_1 VIEW_3 Dynamic Read O
60. devices into Detail Group Trend Maintenance and Alarm displays through the Station application in ProcessLogix as well as the Monitoring tab of the Control Builder application Publication 1757 UMO06A EN P May 2002 2 2 Integrating Fieldbus into Rockwell Automation Logix System ME A PLC 5 Controller Station o Supervisory ControlNet Ethernet ProcessLogix and ControlLogix 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 It works with a Remote Termination Panel RTP for connecting and powering up to two fieldbus H1 links For applications that require a more highly distributed connection and or communications directly with a PLC5 or ControlLogix 5500 processor you can us the 1788 CN2FF ControlNet to Foundation Fieldbus Gateway device Figure 2 1 Logix system architecture for Fieldbus integration Ethernet TCP IP Redundant ProcessLogix L TE iiini i iY NMI Servers mo a Te HAH N al
61. directory tree pane and view pane as shown in Figure E 2 Figure E 2 Fieldbus Library Manager features common Windows type interface Dropdown Si FieldbusLibraryManager s x i s 5 Menus gt W Rockwell Automation Pressure Transmitter Toolbar gt ca fel A fai amp Ga wa Ama IE a HOMEY WELL Pressure Transmitter 15 x sT Rev A j er Pi tac_pesc gt N 7 Pl stratecy 5 P l meN a TRANSDUCER ALERT ken D n View Pane EMODE 5 59 E MODE TARGET 5 ia BE MovE ACTUAL 5 14 E Move penmitTeD 5 14 E Mone NoRmaL 5 14 MELo ERR 6 ia 7 65 i 5 5 5 65 I 5 5 5 B E 65 9 5 Status Ba P gt For Help press FI PID 177 Parameters f cahot Ug 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 If you are familiar with working in a Windows type environment you should be able to intuitively interact with all the functions provided through FLM menu and toolbar selections Table E 2 Menu and toolbar selection summary Click Or follow this menu selection To perform this function File gt Open Device Ctrl 0 Opens Select Device dialog box so you can navigate to the Release directory containing the DD file File gt Save Ctrl S save the data to the default DEF file directory Rockwell Automation t ps50 system er ffdevices File gt Save As Opens Se
62. fieldbus device residing on an H1 link to the input of a Device Control DEVCTL function block or other block with a digital input contained in a Control Module in the ProcessLogix Control Builder application The Fieldbus Library Manager FLM in ProcessLogix R400 0 Control Builder makes this possible The FLM reads the manufacturer s DD for the fieldbus device and creates a device template that is included in the Project tab of Control Builder The device template includes the device s fieldbus function blocks so it can be configured and integrated with control strategies through Control Builder Figure 2 6 shows a simplified functional diagram of how the output from an Discrete Input function block in a fieldbus compliant transmitter is integrated with a Device Control DEVCTL function block in a Control Module that is assigned and loaded to the CEE in the Control Processor Module CPM Publication 1757 UMO06A EN P May 2002 2 14 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 Figure 2 6 Integration of fieldbus device digital input signal with ProcessLogix control strategy CM oOo gt DI 1 Device Control CPM CEE a SO DOC FIM FIM Fieldbus Device Digital Input OUT CEE Control Execution Environment CM Control Module CPM Control Processor Module Transducer FIM Fieldbus Interface Modu
63. function blocks attached set it for 10 seconds The Monitor Data is acquired with messages to the FF devices and it adds a significant load to the FF network if you ask for many of readings Publication 1757 UMO06A EN P May 2002 1788 CN2FF Installation Example F 33 34 Honeywell AI AD aid CHethfacldd Al Modul O O020S022 Good NonCascade TT ia TARGET Auto H AO Alarms i ACTUAL auto CN Al Trends J CN A2 l l TARGET Auto ad Diff Press Hi AD ACTUAL Auto OIT Tas TARGET Auto ACTUAL Auto 0 551653 Good NonCastadel et LA ea ad Diff Press Low AD Monitor at 4 rate of fi sec STINE M Monitor Block Modes tT Ms TARGET Auto M Monitor Block Outputs ACTUAL Auto Monitor Block Inputs M Monitor only wired parameters ee T Show Substatus 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 aw re el aN Application on page F 51 Frequently the Hidden Transducer Block being set to OOS out of service causes this If this happens try the following ad EH Press AN OIT B TARGET Auto ACTUAL Auto
64. if known The ID will be detected when the device is commissioned 6 In the Physical Device Tag PD_TAG field leave the assigned tag name or enter the name that matches the one configured in the device up to 16 characters Publication 1757 UM006A EN P May 2002 4 30 Configurating the 1757 FIM Ts 8 9 10 11 Publication 1757 UMO06A EN P May 2002 The Device State C DEVSTATE parameter is only active in the Monitoring tab after the FIM LINK DEVICE is loaded and communicating with the system Click the System Management tab FLOWSERVE LX1400FF_0502 Block LX1400FF_050240 Parameters Project A aA x Main System Management Network Management Server SM Support Step Timer Preset Preset Set Addr Seq Timer fis20000 Preset Set Addr Wait Timer fas0000 Current App Clock Time Local Clock Time offset 00 App Clk Syne Interval BO Last Revd Ap Clack Time a Sanne Node Addr Of Active Dey pooo SM Macrocycle Duration fico t C SN V SMK Operational Power Up State FB Schedule Version fo Show Parameter Names Cancel Help 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 The grayed out parameters are only accessible in the Monitoring tab
65. interact with the components including the function blocks in the fieldbus devices 1 Double click the desired component block icon in the Link Device tree menus under the FIM icon to call up the associated Configuration form 2 Click the given tab to view the current status of the related fieldbus data Both the FIM and LINK function blocks must be active to view on line data The data can be viewed either by name or parameter reference by not checking or checking the Show Parameter Names checkbox at the bottom of each tab See the On Line Monitoring Using Control Builder section in Knowledge Builder 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 HONEY WELL ST3000FF_0801 Block 514245008 Parameters Monitoring 7 4245008 48574C0002 HWL S T 3000 424501 ST 4245008 ONLINE v 2 Click the Network Management tab HONEY WELL ST3000FF_0801 Block ST4245008 Parameters Monitoring 000001 0000001000011 000000000 00000000000000001 0 ERER 3 Scroll to find the DL Operational Functional Class field Publication 1757 UM006A EN P May 2002 5 6 Operating the 1757 FIM 4 Verify that the functional class is appropriate for the device Basic or
66. mode calculation of actual mode considers the input parameter status attributes input values and resource state as represented graphically in Figure 2 8 Figure 2 8 Block mode calculation summary Target Mode gt Determine B Host Timeout lt 4 4 Actual Mode o and Target A Remote Cascade C Remote Out Shed Option _ gt Actual and Target Cascade gt Primary Input gt Back Calculation Input gt Resource State Block Specific Inputs _ gt Mode Calculation See Appendix C for list of conditions which will change the mode in order of priority with Good Non Cascade status on input parameter as the lowest priority Publication 1757 UMO06A EN P May 2002 2 24 Integrating Fieldbus into Rockwell Automation Logix System Link and Block Schedules Publication 1757 UMO06A EN P May 2002 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 e Recognizes and adds new devices to the link e Removes non responsive devices from the link e Distributes Data Link and Link Scheduling time on the link The data link layer synchronizes the network wide Data Link Time Link scheduling time is a link specific
67. 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 When you are finished you should be able to use the Monitor Function in the Fieldbus Configuration software to monitor the data coming from a Fieldbus device and using a second window on the PC monitor see the same value in the Floating Point Data Table in the controller If you happen to have Fieldbus sensors that show the value that they are transmitting all three readings should be the same If you are using a PLX system The Offset Values must be set on the IN function blocks which you drag to your Control Module from the Library If you are receiving data from a Discrete IN DI function block you will drag and set the offset in an IN_D function block If you are using a CLX processor Tech Support at 440 646 5800 can provide a CLX program that includes a structure that spreads the FF data so it is understandable You can obtain the ControlLogix Example Code by doing the following 1 Visit us at www ab com 2 Click on Product Support 3 Click on Knowbase 4 Search on Knowbase document number A5754787 5 Double click the file and download to you PC With the CLX there are two pad bytes before the real data from the CN2FF starts to appear Therefore the CLX program from Tech 1788 CN2FF Installation Example F 39 Support adds 2 to the listed Offset Uf you are
68. of Service OOS Local Override LO Manual Man Automatic Auto Cascade Cas and Remote Cascade RCas modes The Set point SP_D supports the full cascade sub function Use the Cascade mode to transfer the output of another block to the Set point SP_D of the DO block Use the IO_OPTS Invert selection to do a Boolean NOT function between the field value and the output Use the IO_OPTS Invert selection to do a Boolean NOT function between the SP_D and the output If the hardware supports a readback value it is used for READBACK_D and after accounting for the O_OPTS Invert selection acts as the PV_D for this block If this is not supported READBACK is generated from OUT_D In the Man mode an operator can force the output in a programmable logic controller sense If Man mode is not permitted it must be supported as a transition mode for exiting the OOS mode e The SIMULATE_D parameter is for testing purposes only and always initializes in the disabled state Parameters ALERT_KEY IO_OPTS ST_REV see Appendix A BKCAL_OUT_D MODE_BLK STATUS_OPTS for definitions of BLOCK _ALM OUT_D STRATEGY each parameter BLOCK_ERR PV_D TAG_DESC CAS_IN_D PV_STATE UPDATE_EVT CHANNEL RCAS_IN_D XD_STATE FSAFE_TIME RCAS_OUT_D SIMULATE_D FSAFE_VAL_D READBACK_D SP_D GRANT_DENY SHED_OPT Publication 1757 UM006A EN P May 2002 The Fieldbus Communication Model 1 19 Manual Loader Block Figure 1 10 Functional Schematic for Manual Loader Functio
69. of the Precess Variables that are scheduled The protocol also says that you must allow significant time for a Fieldbus device to respond to a request for data or information The result of the slow data rate and the protocol dictate that Fieldbus configuration tools allow 40 to 50 milliseconds for the transmission of data from each Function Block Also many pressure transmitters measures both the pressure and the temperature If the application dictates that both values must be used then 80 to 100 milliseconds will be allocated to communicating with those two function blocks in that one pressure transmitter Both the Pressure and the Temperature interface with other Fieldbus devices through independent function blocks so each require their own 40 to 50 milliseconds The CN2FF operates on the Fieldbus side at the max speed of the Fieldbus and at the ControlNet rate on the ControlNet side Therefore the CN2FF is not a limiting factor in a Fieldbus systems performance When a CN2FF operates the Fieldbus side and the CN side run asynchronously When the CN2FF receives data it is stored in the CN2FF and is Produced on CN at the NUT rate Therefore in a typical CN2FF Fieldbus system the controller will be receiving a lot of redundant data In a PLX system with a FIM fieldbus interface the Fieldbus side operates at the Fieldbus data rate and the controller side operates at the backplane rate so again it is not a restriction on the perf
70. 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 e A minimum Fieldbus message uses 99 bits e A minimum response uses 150 bits Just to put those messages on the wire takes 8 ms The protocol says that you must allow time for each device to send nonscheduled messages in addition to the Publishing of the Precess Variables that are scheduled The protocol also says that you must allow significant time for a Fieldbus device to respond to a request for data or information The result of the slow data rate and the protocol dictate that Fieldbus configuration tools allow 40 to 50 milliseconds for the transmission of data from each Function Block Also many pressure transmitters measures both the pressure and the temperature If the application dictates that both values must be used then 80 to 100 milliseconds will be allocated to communicating with those two function blocks in that one pressure transmitter Both the Pressure and the Temperature interface with other Fieldbus devices Publication 1757 UMO06A EN P May 2002 1 30 The Fieldbus Communication Model Publication 1757 UMO06A EN P May 2002 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 an
71. perform either analog input analog output discrete input or discrete output functions The linking device models the I O modules in software The linking device has four types of function blocks Multiple Analog Input MAT Multiple Analog Output MAO Multiple Discrete Input MDI Multiple Discrete Output MDO Each of these function blocks has eight channels Each channel is a combination of a value and Fieldbus status You can connect an analog input function block on the Fieldbus network to a channel on the MAI block just as you would wire a 4 20ma analog input to an analog channel in your I O subsystem The main difference is that the Fieldbus function blocks do considerable processing The channel value represents a scaled value in engineering units Each value has an associated status The status is more than a boolean of good or bad It has four major status values of Good or Bad with 16 sub status values for each major status and four limits Publication 1757 UMO06A EN P May 2002 7 2 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Analog Inputs Publication 1757 UMO06A EN P May 2002 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
72. 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 Discrete Outputs 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 716 5 4i 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 Bit 2 Acknowledge is undefined when read and should be ignored when performing a GET When a user wants to Acknowledge an alarm this bit should be written as a 1 when performing a SET Each time the LD detects a 1 in the Acknowledge position a Fieldbus Acknowledge will be generated Therefore users must be careful not to set the Acknowledge bit more than once per alarm Bits 1 and 0 CLEARED and ACTIVE respectively are read write bits When an alarm condition is ACTIVE or CLEARED these bits are read as a 1 when performing a GET The user must Confirm each of these states by writing them to a 0 by a SET Once an alarm has occurred become ACTIVE alarm processing is NOT complete until the user intervenes to remove the alarm condition Acknowledges the alarm writing a 1 in the Ackn
73. process environments such as automotive manufacturing building automation or discrete parts manufacturing and later adapted to process control Generally they are well suited to the applications for which they were originally developed Some of these technologies are open some are proprietary Every communication technology provides a method for transmitting data between various devices and a host and some provide communications directly between devices The various schemes differ in how well they are optimized for moving data quickly their suitability for real time control the cost of hardware implementations their networking capability for branches spurs and long distances and for how power is distributed Sections of this publication has been provided by FOUNDATION Fieldbus Publication 1757 UMO06A EN P May 2002 1 2 The Fieldbus Communication Model Publication 1757 UMO06A EN P May 2002 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 Using a strategy exactly opposite of FOUNDATION fieldbus these various communications technologies minimize dependence on local intelligenc
74. rte wh Re ose HE eta Ho a Beds Gide Ae A 46 USBC k arenan ell ee Se Re ER Ge DA A 48 VIXX DOCKS 2 6 05 Lote dee tee h ethos Siw tad ae ers A 49 WS BIOCKS uere etna n etic eased ees ee oleae si a ened A 49 POCO DIOCKS 5 anise oo esata oe wear ee ake Ee A 50 WoO IDIOCK S42 keene Mee Behe ee ok wa aed A 50 LK BIOCKS 5 x 6 ah be ah be DAE HLS wee BD A 50 Appendix B CE E ee E hte Se pct ees ey eh al tee sate Se Uh pct yo ee aa es B 1 Appendix C PREG i CCS ie rae Sots ds Bee en et ee EE noe Bde A eet aes C 1 Publication 1757 UMO06A EN P May 2002 X Table of Contents Fieldbus Wiring Considerations Fieldbus Library Manager 1788 CN2FF Installation Example Publication 1757 UM006A EN P May 2002 Appendix D E eae EEE EN E EE E EEE oS D 1 Pieklb s TOpOlocics 4 5 34 43 095 a aa a a A D 1 Power Condonin O ainaka aa a ads ety eS ee hs aed Shae B D 2 Power Dist DUtlOM s ai we eon eke beatae oe ed baer es D 3 Signal Degradation Limitations 0 00045 D 3 Cale GIGS Six iy a Ss esate ek edt eh ee An doe we Des D 5 CADE Amendo e Said eo ee et Sh eld oe D 5 Signal Distortion vs Capacitance 0 0 000 eee D 6 CalculatinS Attenda HON si jpactoned dst ee nde eee ees D 7 Te Ci CA DIG att ok end ee we Sais ee od ead ee A Pl D 7 RCs ie tank dt haath eR A Be eR PR RE eR ake D 7 Appendix E About Fieldbus Library Manager 00005 E 1 Desc iplOt seun ans e Veeck eee mee a eee eee E 2 Menu and toolbar selections
75. s concept that Cascade is a higher mode of operation than Automatic Automatic is a higher mode of operation than Manual and so on The Dominance Order interpretation is based on Foundation Fieldbus special rules for modes dominating one another For example Out of Service dominates over Manual Manual dominates over Remote Out and Remote Out dominates over Remote Cascade This is relevant if multiple mode bits are set in the target or normal mode bitstrings A block uses the concept of priority to compute an actual mode that is different than the target mode and to determine if the particular actual mode allows write access Table 2 E 2 character and 4 character mode indications Mode Mode Abbreviation Priority Interpretation 4 Character Priority Order Control Order Dominance Order 8 highest 8 highest 6 Highest OOS Manual Publication 1757 UMO06A EN P May 2002 M TIP The ProcessLogix software installation wizard for Server includes a dialog box for choosing the desired mode acronyms Select the Fieldbus acronyms radio button to use the mode abbreviations listed above in the Station displays 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 F Mode Bit Assignments Bit p Mode 0 LSB p Remote Outp
76. states are found Cancel Help Component mismatches are flagged Publication 1757 UMO06A EN P May 2002 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 Be sure ALIV does not appear in the LED display on the front of the FIM If it does you must first load the FIM s personality firmware using the NIOOLS utility supplied with ProcessLogix Engineering Tools A CM that contains only fieldbus We recommend that CMs containing only fieldbus function blocks be assigned and loaded only function blocks to the appropriate FIM LINK They will only take up unnecessary memory and execution time in the CPM CEE A CM that contains both ProcessLogix Be sure CMs that contain any ProcessLogix function blocks are assigned and loaded to a CEE and fieldbus function blocks Control Builder enforces this and will also load the Foundation Fieldbus A fieldbus device through a FIM Be sure the device configuration in Project tab has the proper PD_TAG specified While you can load a device to the link from Project you can not load and commission a device until it Is connected to the link and its PD_TAG and address agree with those specified in Project Please see the next two sections Fie d
77. that the FF suggests They are shown in the window oe NI FBUS Fieldbus Configuration System Linkinking Device_11 Network Parameters Parameter CONFIGURED LINE SETTING SLOT_TIME PER _OLPOL PHL OVERHEAD Max AESPONSE DELAY FIRST UNPOLLED NODE_ID THIS LINE MIB INTER POU DELAY NUM CONSEC_UNPOLLED NOD 186 PAEAMBLE EXTENSION foe PUST TRANS GS amp PLEXTENSION 1 Max INTER CHAN SIGNAL SKE 1 TIME SYNC CLASS _ 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 16 or 10 hex is the first usable address on a Fieldbus network and it will be assigned to the CN2FF 2 Close the Network Parameters window 3 When the hourglasses have disappeared you are ready to proceed The Library of Function Blocks in this example shows two pressure transmitters You will give a tag name to each transmitter check the FF Publication 1757 UMO06A EN P May 2002 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 A Linkinking Device_11 Log Notes Network Parameters Baad Schedule a Function Block Application oe
78. the involved function blocks are appropriately adjusted Publication of each output is scheduled immediately after execution of the function block that produces the value considering inter publication delays and potential conflicts Blocks publish if their output is connected to an input in another device or the FIM e No unneeded time delay is allowed in the default link data transfer schedule e The macrocycle is the least common multiple of the execution periods of all the CMs involved in the link data transfer schedule Publication 1757 UMO06A EN P May 2002 2 26 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 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 They may run asynchronously The block execution time can be broken into these three phases 1 Preprocessing Snap shot of parameter values 2 Execution Function block outputs are determined 3 Postprocessing Block output values alarm and associated trend parameters are updated Since input parameter values
79. the system Publication 1757 UM006A EN P May 2002 4 14 Configurating the 1757 FIM 4 Click the System Management tab SYSTEM LINK Block LINK51 Parameters Project Bee x Main System Management Network Management Application Server Parameters SM Support Step Timer Preset Preset Set Addr Seq Timer fis20000 Preset Set Addr Wait Timer jas0000 Current App Clock Time Eee Local Clock Time offset Poo App Cik Syne Interval BO Last Revd Ap Clock Time E I Adkor Lk Pinay Tna Paa 0 Node Addr Of Active Dev eo SM Macrocycle Duration eao M SMK Operational Power Up State Show Parameter Names Cancel Help 5 Publication 1757 UMO06A EN P May 2002 ee 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 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 In the Preset Set Addr Seq Timer T2 field either leave the default value of 1920000 or enter a new value This is the preset value for the System Management set address sequence timer in 1 32 millisecond increments In the Preset Set Addr Seq Timer T3 field either leave the default value of 480000 or enter a new value This is the preset value for the System
80. the window Using the Tools Menu Functions Many of the Tools menu functions designed for use with the Controller and CEE components also apply for the FIM and LINKs components These include Upload Update and Snapshot functions These functions are useful for correcting mismatches that may occur between the components and the database Please refer to the Control Building Guide in Knowledge Builder for details about a given menu function Adding Removing and Replacing Components Chapter 6 1757 FIM General Maintenance Checkout and Calibration About Removal and Insertion Under Power 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 IMPORTANT This is a general document on how to use ProcessLogix tools and that full maintenance should use live analysts This document is not intended to replace Foundation Fieldbus or the device Manufacturers installation and training documents Repeated electrical arcing causes excessive wear to contacts on both the module and its mating connector Worn contacts may create electrical resistance that can affect module operation You can remove and insert the FIM without removing power The removal of the FIM results in the loss of communications with both H1 fieldbus links The removal
81. time represented as an offset from Data Link Time It is used to indicate when the LAS on each link begins and repeats its schedule System Management uses it to synchronize function block execution with the data transfers scheduled by the LAS e Polls devices for buffered data at scheduled transmission times e Distributes a priority driven token to devices between scheduled transmissions Any device on the link may become the LAS as long as it is capable The devices that are capable of becoming the LAS are called Link Master devices All other devices are referred to as Basic devices The FIM is Link Master capable and supports both a primary and a backup link schedules It is designated as the primary Link Master Upon startup or failure of the existing LAS the Link Master devices on the link bid to become the LAS The Link Master that wins the bid begins operating as the LAS immediately upon completion of the bidding process Link Masters that do not become the LAS act as basic devices when viewed by the LAS They also act as LAS backups by monitoring the link for failure of the LAS and by bidding to become the LAS when a LAS failure is detected ATTENTION ATTENTION If a LAS is too large to fit in the active Link Master capable device the user must reconfigure the device to become a Basic one through Control Builder and restart the device to initiate the change Integrating Fieldbus into Rockwell
82. under limited conditions or mode change DS 65 C Remote Output Out 5 VIEW_3 Dynamic 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 e Status e Value Table A 103 RS_STATE simple Variable Defines the state of the function block application state machine Unsigned 8 1 Start Restart 2 Initialization 3 On Line Linking 4 On Line 5 Standby 6 Failure C Resource State 1 VIEW_1 VIEW_3 Dynamic Read Only Sxxx Blocks Standard Function Block Parameters A 39 Table A 104 SEL_1 Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents first input value to the selector DS 65 Cascade Input 5 VIEW_1 VIEW_3 Non Volatile 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 e Status e Value Table A 105 SEL 2 Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents second input value to the selector DS 65 Cascade Input 5 VIEW_1 VIEW_3 Non Volatile 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 e Status e Value Table A 106 SEL 3 Classification Description FF Dat
83. 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 HI FBUS Interface Configuration Utility OF DOD Info PoartO The changes made in FECONF only takes effect after you start NI FBUS process the nest time 8 Go to Port Configuration on page F 12 Finding the Interface Driver Name If you don t know the name of your device driver do the following 1 In RSLinx select Communication Drivers File Edit View Communications Station DDE VORPC Security Window Help g amp g liz x Publication 1757 UM006A EN P May 2002 F 10 1788 CN2FF Installation Example You see ply ie Drivers As stated on Available Driver Tones page F 8 driver names must match Configured Drivers i Sa 4B PCC 1 ControlNet MAC ID 24 AUNNING 12 Running 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 Use RSLinx to check the communication path for the 1788 CN2FF 1 Start RSLinx Vy RSLinx Gateway File Edit View Communications Station D
84. used by a function block must not change during execution a copy of the input parameter values is captured or snapped at the beginning of execution Also since block outputs to other blocks must be time coincident the output values are only updated at the completion of the function block execution The block algorithm execution phase is always executed in the following ordered sequence as shown in Figure 2 9 1 Determine the actual mode attribute of the mode parameter This calculation is based on the target mode and the status attributes of input parameters 2 Calculate the set point if the Set Point parameter is defined for the function block The calculation of working set point is based on the actual mode set point input parameters such as cascade and remote cascade and any backward path input status Also the value of the controlled parameter process variable may be used for set point tracking The resulting set point is shown in the set point parameter 3 Execute the control or calculation algorithm to determine the value and status of output parameters in the forward path The conditions that determine the status attribute of output parameters The value attributes of the block s input parameters and contained parameters the actual mode and the working set point are used in this algorithm Also where defined by the block profile some blocks may use the status of selected inputs Integrating Fieldbus into Rockwe
85. 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 Publication 1757 UMO06A EN P May 2002 F 40 1788 CN2FF Installation Example PLC 5 and ControlLogix Applications AI FBUS Fieldbus Configuration System ver 2 4 Beta Demo System LD 11 Function Block Application File Edt View Configure oom Window Help co aw 55 za el Loop Time 1sec Stale Limit 1 l lk Aa HA Function Block Application E H AT Ary a a Demo Sys LD 11 E Device Info RB Resource RB a CNetMacld11_Al_ModuleQ_0 CHAI 34 CNetMacld11_Al_Modulel_0 C E ee CMetklacldii_A0_Modulel_0 CHAC CH A0 Adans M 34 CNetMacld11_A0_Module1_O a CHethfacld 1_Al Modit 0 CH 3 ad CNetMacld11_DI_ModuleQ_0 0 CH 43 D 34 CNetMacld11_DO_Modulef_0 CH a ie 5 E H Cerabar H RESOURCE_44Y0610 UNK oot 2 E H AI AI e enin 3051 Pressure i RESOURCE RB i 2 RosePresAl Al o RoseTemp Al2 Al ad PIDI PID ad ISEL ISB ad CHAR SCB a ARITH AB 3 INTEG IB 5 SMAR FF to g SMAR RE RB oo 2 SMAR 1 AQ CH BECAL IN ACH OUT AD eer CAS IN Ef SMAR 12 A0 E p E SMAR 3 AO Ie CH BECAL
86. was 4 it would retrieve the ControlNet status It would retrieve the FF status if the attribute was 150 Publication 1757 UMO06A EN P May 2002 1788 CN2FF Installation Example F 49 Remote Configuration of a Fieldbus Network via the 1788 CN2FF 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 The procedure for Ethernet is similar 1 Set up an Ethernet Gateway Driver to connect to the 1756 ENET module in the remote rack where you will connect to ControlNet 2 Open the DDE OPC window DBEFOPC Topic Configuration E x Project Default Topic List Data Source Data Collection Advanced Communication myfftopic M Autobrowse Path_from_my_PC_to_mp_CH2FF E Workstation W477ES TCP 1 x i E r Lins Gateways Ethernet H AB_ETH 1 Ethernet Glas AB_PCC 1 ControlMet Ela TCP 1 Ethernet lef 130 151 133 76 1756 ENB TVA 1756 ENBT JA G Backplane 1756 4744 00 1756 ENET A D2 17 56 L14 LOGI 5550 FF_sample_CL _program_Ocl 03 1756 module 1757 FlM Fieldbus I F 2 Chan 0E 1756 CNBA D 1756 CNBR D Eas A ControlNet 01 1756 CNBR D 1756 CNBR D 04 1789 CN2FF Linking Device 1789
87. 02 1 12 The Fieldbus Communication Model Table 1 E Analog Output Specifications Description Function Notes Equation Options Parameters see Appendix A for definitions of each parameter 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 Can use either the Set point SP value after limiting or the Process Variable PV value for the BKCAL_OUT value e Supports Out of Service OOS Local Override LO Manual Man Automatic Auto Cascade Cas and Remote Cascade RCas modes The conversion of Set point SP to percent of span is based on the PV_SCALE range The conversion of the percent of span to a compatible value for the hardware is based on the XD_SCALE range Use the Increase to Close Option in IO_OPTS to invert the span Use the Cascade mode to transfer the output of another block to the Set point of the AO block If the hardware such as a valve positioner supports a readback value run this value backwards through the XD scaling to act as the PV for this block If this is not supported READBACK is generated from OUT In the Man mode an operator can write a value to OUT A manufacturer must put operational limits in the Transducer where an operator cannot access them to permit the Man mode If Man mode is not permitted it must be supporte
88. 02 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 If the FIM is located in a remote chassis go to step 9 In the Supervisory Chassis MAC field select the MAC address assigned to the ControlNet Network module connected to the Supervisory network also known as the uplink 8 In the Supervisory Chassis Slot Number field select the slot number where the FIM is installed Go to step 12 9 If the FIM is located in a remote chassis select the check box next to the Remote Chassis Field M Remote Chassis 10 In the Remote MAC Address field select the address of the ControlNet Network module in the Remote I O Chassis 11 In the Remote Chassis Slot Number field select the slot number where the FIM is installed Publication 1757 UMO06A EN P May 2002 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 Main Statistics Server Parameters
89. 07987 Tel 65 351 6723 Fax 65 355 1733 Publication 1757 UMO06A EN P May 2002 PN 957603 37 Copyright 2002 Rockwell Automation All rights reserved Printed in the U S A AB Allen Bradl ey Fieldbus Solutions for Rockwell Automation s Integrated Architecture User Manual
90. 2FF Linking Device 1757 CN2FF 04 1 7868 CN2FF Linking Device 1757 CM2FF 05 1 7868 CN2FF Linking Device 1757 CM2FF 06 1788 CN2FF Linking Device 1757 CN2FF 1788 CN2FF Linking Device 1757 CN2FF 1788 CH2FF Linking Device 1757 CH2FF 17868 CWAFF Linking Devine 17R7 CNAFF 7 Click Apply 8 Click Advanced Communications Publication 1757 UMO06A EN P May 2002 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 LO Y board port Pance a a ee pim E Piven Sa I aneen oan Ee eran eter Li E O pase WETE 1 Type in a name that is meaningful to your project Publication 1757 UM006A EN P May 2002 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 PortO and Portl 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 You see NI FBUS Interf
91. 43 VIEW_1 VIEW_3 Non Volatile 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 e Status e Value Table A 115 SP_D Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks Record Defines the setpoint of any discrete block DS 66 PV_STATE C Setpoint 2 VIEW_1 VIEW_3 Non Volatile 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 discrete value parameters It uses the following two elements e Status e Value Table A 116 SP_HI_LIM Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the high limit for setpoint entry Float PV_SCALE 10 percent C Contained 4 VIEW_2 Static Initial value is 100 percent Publication 1757 UMO06A EN P May 2002 A 44 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Table A 117 SP_LO_LIM Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable
92. 6A EN P May 2002 A 8 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Usage Length Valid Views Storage Remarks C Channel 2 VIEW_4 Static The initial value is 0 Table A 20 CLR_FSAFE Classification Description FF Data Type Range Usage Length Storage Remarks simple Variable Serves as a switch to reset clear the device failsafe state after the fault con dition is cleared Unsigned 8 1 Off 2 Clear C Contained 1 Dynamic The operator can control PROGRAM or LOCAL access to these values Table A 21 CONFIRM_TIME Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the time between retries of alert reports Unsigned 32 Positive C Contained 4 VIEW_2 Static The initial value is 32000 milliseconds Table A 22 CONTROL_OPTS Classification Description FF Data Type Usage Length simple Variable Represents bit string for control options to alter the calculations done in an applicable function block Bit String C Contained 2 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 23 CONTROL OPTS Bit Selections Function Block t Meaning ae e e a ofsa y S a perene y e Pe o feren ff xt o ferreo ff e a x X 2 3 4 D D
93. 8574C0002 Hw Honeywell ST3000FF Template Not Installed Uncommissioned Devices 4 Review the device details The device manufacturer assigns tag and device IDs gt It is a good idea to record the device s Tag name and Device ID for future reference Publication 1757 UM006A EN P May 2002 5 8 Operating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 It is possible that the uncommissioned device may have an earlier version of the vendor s software Device Rev In this case the device would appear gt to have no matching template even if one exists for the same device but it is for a different software version If the vendor supports flash upgrade of its device s firmware you can upgrade the device s firmware through this tab Please see the next Section Maintenance Checkout and Calibration for more information A new Link Active Schedule LAS must be loaded to the FIM and other LinkMaster devices anytime there is a change that invalidates the active LAS such as adding a device removing a device or making a configuration change 6 Click OK to close
94. AI blocks as shown in the Figure 7 2 Figure 7 2 Sample Multiple Macrocycle MAI Configuration Loop Time 1 sec Stale Lint 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_AO and CN_A5 and not use any of the others As shown in the lower loop of Figure 7 2 you can connect any parameter that is a float value and status combination to the MAI block In other words you can bring values from any function block to the PLC processor The MAT block is not limited to interfacing with AI function blocks Publication 1757 UMO06A EN P May 2002 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 A ControlNet Analog Input Object Attributes Attribute Number Type Initial Value Remarks oo foe f e oo 4 CNStatus Boolean Get f Bad o0 ControlNet status 0 Good 1 Bad 107 Loflag f uint8 Gev Set JO see Alarm Handling for Analog Inputs 108 fHiFlag uint8 Gev Set JO see Alarm Handling for Analog Inputs 109 lolog vin Geyset oO see Alarm Handling for Analog Inputs 110 0 See Alarm Handling for Analog Inputs
95. AS ROUT attribute of BAD permitted mode Target mode is RCAS and N A N A N A N A Actual mode N AF remote cascade in does not from last have status of Good execution or Initialization Acknowledge and AUTO actual mode attribute last execution was not RCAS Target mode is ROUT and N A N A N A N A N A Actual mode remote out in status is not Good Initialization Acknowledge and actual mode attribute last execution was not ROUT from last exe cution or MAN Publication 1757 UMO06A EN P May 2002 C 2 Mode Change Conditions Input Parameters Status Mode Parameter Target Attribute Value Attributes Inputs Values and Automatic Cascade Remote Remote Auto CAS Cascade Output RCAS ROUT Resource States Actual mode N A N A Out of Service 00S Target mode is CAS and N A cascade input status is not from last Good Initialization execution or Acknowledge and actual mode AUTO attribute last execution was not CAS Status attribute of primary input OOS MAN MAN MAN MAN ROUT parameter is BAD or Uncertain with option to treat Uncertain as BAD and bypass not set Status attribute of back OOS IMAN IMAN IMAN IMAN IMAN calculation input parameter is BAD Status attribute of back OOS IMAN IMAN IMAN IMAN IMAN calculation input parameter Good failsafe active local override not invited or initialization request Tracking is enabled track input OOS LO active and track override manual is Enable
96. B 3 dB km 4 6 km A shorter cable will have proportionately less attenuation For example a preferred type 1 cable that is 500 m 1640 ft long would have an attenuation of 1 5 dB Publication 1757 UMO06A EN P May 2002 D 6 Fieldbus Wiring Considerations Signal Distortion vs Capacitance Publication 1757 UMO06A EN P May 2002 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 In addition to cable attenuation calculations for determining the maximum fieldbus cable length must also use the following guidelines to calculate signal distortion due to spurs e Each spur is converted to an equivalent capacitance e All spurs are assumed to be at the extreme end of the trunk e Signal attenuation is calculated as 0 035 dB nf For example if the fieldbus topology includes five devices each on a 20 m 66 ft spur the total cable length is 100 m 328 ft equivalent capacitance is 3 nf 100 m x 0 03 nf m and spur distortion is 0 105 dB 3 nf x 0 035 dB nf 0 105 dB Another source of distortion is the fieldbus device s equivalent capacitance Use the following guidelines to calculate the distortion due to device capacitance e D
97. CN_OUT_AO cal e CN_OUT_Al CNetMacId05 DI Moduled 0 CNDI CNetMacId05 AI ModuleO O CNAT 3 CNetMacId05 AI Modulel 0 CNATL a a al ll Be M0B 200 300 400 500 600 700 800 300 ms Part of the reason that Fieldbus is slow is that Fieldbus devices operate on very small amounts of current e 10 to 20 ma per device is typical e Translates into slow computations in the transmitters e Typically takes 100 ms for a fieldbus transmitter to make a new measurement of an input with all the associated calculations completed e Therefore when attempting to determine the performance of a fieldbus system please recognize these facts Performance calculation considerations Publication 1757 UMO06A EN P May 2002 Integrating Fieldbus into Rockwell Automation Logix System 2 31 e Some pressure transmitters will read their transducers and create a new floating point digital readings of the PV every 100 ms e That value can only be read every 40 to 50 milliseconds because of the Fieldbus data rate and of the Fieldbus protocol e The data rate is 31 25 Kbps or 31 bits per millisecond Very very slow by comparison with ControlNet or Ethernet e A minimum Fieldbus message uses 99 bits A minimum response uses 150 bits Just to put those messages on the wire takes 8 ms The protocol says that you must allow time for each device to send nonscheduled messages in addition to the Publishing
98. Cascade In 5 VIEW_3 Non Volatile The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Standard Function Block Parameters A 35 Table A 94 RCAS_IN_D Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents target setpoint and status provided by a supervisory host to the analog control or output block DS 66 C Remote Cascade In 2 VIEW_3 Non Volatile The data type consists of the value and status of discrete value parameters It uses the following two elements e Status e Value Table A 95 RCAS_OUT Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents block setpoint and status after ramping It serves as input to a supervisory host for back calculation that allows action to be taken under lim iting conditions or mode change DS 65 C Remote Cascade Out 5 VIEW_3 Dynamic 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 e Status e Value Table A 96 RCAS_OUT_D Classification Description FF Data Type Usage Length Record Represents block setpoint and status It serves as input to a Supervisory host for back calculation that allows action to be taken under limiting condition
99. DE OPC Security Window Help 2 S19 lle x 2 Click on DDE OPC 3 Select Topic Configuration Publication 1757 UM006A EN P May 2002 1788 CN2FF Installation Example F 11 4 Click on New and type in a name DDESOPC Topic Configuration x Project Default Topic List Data Source Data Collection Advanced Communication Path_from_my_PC_to_my_CN2FF WM Autobrowse Workstation M4765 Fae Link Gateways Ethernet Els AB_PCC 1 ControlNet H A 01 1756 CNBR D 1756 CNBR D 02 1756 CNBR D 1756 CNBR D O39 1756 CNBR D 1756 CNBR D O04 1756 CNBR D 1756 CNBR D 05 1756 CNBR D 1756 CNBR D FY 06 1756 CNBR D 1756 CNBR D eee Fackplane 1756 41074 A OO 1756 CNBR AD 01 1757 PLX52 CONTROL PROCESSOR 1757 PL 0a 17 56 OF 614 1756 0 FBT AA ood 04 17 56 1F 614 17 56 1F BLA Aga al 06 1756 CNBA D 1756 CNBR D OF 1756 ENET 44 17 56 ENET 4 08 1756 041674 1756 0416448 ACOUT 09 1756 02814 1756 0884 RELAY n o amp ee H Bl nar Fer eann AFE N Elane Delete Apply Done Help 5 Navigate to the 1788 CN2FF you want to configure 6 Select the 1788 CN2FF You see Data Collection Advanced Communication O Backplane 1756 41044 00 1756 CNBR O 01 1757 PL 52 CONTROL PROCESSOR 1757 PLX5 03 1756 OF 6144 1756 OF BVI Ja OOOO 04 1756 164 1 756 1F 67a AAA 0G 17 56 CNBR D 17 56 CNBR D Fae A Control et Al 01 1756 CNBR D 1756 CNBR D se U2 1 788 CN
100. Defines the low limit for setpoint entry Float PV_SCALE 10 percent C Contained 4 VIEW_2 Static Initial value is zero 0 Table A 118 SP_RATE_DN Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the downward ramp rate in PV units per second for setpoint changes to Invoke action in the Auto mode Float Positive C Contained 4 VIEW_4 Static If the ramp rate is set to zero or the block is not in Auto mode the setpoint change is invoked immediately Table A 119 SP_RATE UP Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the upward ramp rate in PV units per second for setpoint changes to invoke action in the Auto mode Float Positive C Contained 4 VIEW_4 Static If the ramp rate is set to zero or the block is not in Auto mode the setpoint change is invoked immediately 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 121 STATUS_OPTS Classification Simple Variabl
101. F Linking Device Device Info Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device i File Edit View Devicelnfo Configure Window Help x CN FF Linking Device ID HNIC_CN FF 2_00ACD5FA_0 a IHFUT Assembly FieldbusTag Module Channel Instance Handshake Attribute Offset Length DataType Pot 3 TEMP AIT ModuleO_O O VALUE 6 4 CHFLOAT CHSTATUS 10 1 CNHBOOL FFSTATUS 11 1 CHUSINT Pot 3 Press AI ModuleO_O 7 1 VALUE 0 4 CHFLOAT CNSTATUS 4 1 CHBOOL FFSTATUS 5 1 CHUSINT Valve 54 AQ ModuleO_O O 1 TRUE FFREADBACE 12 4 CHFLOAT FFBECALSTATUS 16 1 CHUSINT Valve 7 AO Moduled_oO 1 2 TRUE FFREADBACE 18 4 CHFLOAT FFBECALSTATUS 22 1 CHUSINT Drive 11 AQ ModuleO_O 2 3 TRUE FFREADHACE 24 4 CHFLOAT FFBECALSTATUS 28 1 CHUSINT OUTPUT Assembly FieldbusTag Module Channel Instance Handshake Attribute Offset Length DataType Valve 54 AQ ModuleOd_oO O0 CHYALUE 0 4 CHFLOAT CNSTATUS 4 1 CNHBOOL FFCASINSTATUS 5 1 CHUSINT Valve 7 AQ Moduleod_oO 1 2 CHYALUE 6 4 CHFLOAT CNSTATUS 10 1 CHBOOL FFCASINSTATUS 11 1 CHUSINT Drive 11 AQ ModuleOd_O 2 3 CHYALUE 12 4 CHFLOAT CNHSTATUS 16 1 CHBOOL FFCASINSTATUS 17 1 CHUSINT pL EMSC SETS A S Ready 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
102. FF Data Type Range Usage Length Valid Views Storage Remarks Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks VIEW_1 VIEW_3 Non Volatile 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 e Status e Value Table A 81 OUT D Record Represents the primary discrete value calculated as a result of executing the function DS 66 OUT_STATE O Primary Output 2 VIEW_1 VIEW_3 Non Volatile 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 discrete value parameters It uses the following two elements e Status e Value Table A 82 OUT_HI_LIM simple Variable Defines the maximum output value limit in all modes unless the CONTROL_OPTS selection No Out limits in Manual is chosen Float QUT_SCALE 10 percent C Contained 4 VIEW_2 Static Initial value is 100 Standard Function Block Parameters A 31 Table A 83 OUT_LO_LIM Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple V
103. GOOD Cascade jFault State Active FSA High Limit F FaultState H GOOD Cascade ae ee a FaultState C GOOD Cascade InitFaultSt GOOD Cascade LoLim nitFS GOOD Cascade Initiate Fault State IFS High Limit a HiLim nitFS GOOD Cascade Initiate Fault State IFS Constat fC Const InitFS Publication 1757 UMO06A EN P May 2002 Appendix C Mode Change Conditions Reference Input Parameters Status Mode Parameter Target Attribute Value Attributes Inputs Values and Resource States Automatic Cascade Remote Remote Auto CAS Cascade Output RCAS ROUT All input parameters have Good OOS MAN AUTO CAS RCAS ROUT Status or Uncertain status with option set to treat Uncertain as Good Remote cascade in has BAD OOS MAN AUTO CAS Status or time out is detected and the shed option parameter value is Normal Remote cascade in time out is OOS MAN AUTO CAS Set target and ROUT detected and the shed option actual mode as parameter value is not set to specified Normal AS Out of Service 00S Shed to next ROUT permitted or target model Remote out in has BAD status 00S MAN AUTO RCAS Shed to next or time out is detected and the permitted or shed option parameter value Is target mode normal Remote out in time out is OOS MAN AUTO C RCAS Set target and detected and the shed option actual mode parameter value is not set to as specified Normal Cascade input has a status OOS MAN AUTO Shed to next RC
104. HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL amp amp Allen BE PAID BY THE ADDRESSEE Bradley DODGE RELIANCE ELECTRICE ROCKWELL EJ SOFTWARE Bis Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE www rockwellautomation com Corporate Headquarters Rockwell Automation 777 East Wisconsin Avenue Suite 1400 Milwaukee WI 53202 5302 USA Tel 1 414 212 5200 Fax 1 414 212 5201 Headquarters for Allen Bradley Products Rockwell Software Products and Global Manufacturing Solutions Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Rockwell Automation SA NV Vorstlaan Boulevard du Souverain 36 BP 3A B 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation 27 F Citicorp Centre 18 Whitfield Road Causeway Bay Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Headquarters for Dodge and Reliance Electric Products Americas Rockwell Automation 6040 Ponders Court Greenville SC 29615 4617 USA Tel 1 864 297 4800 Fax 1 864 281 2433 Europe Rockwell Automation Br hlstra e 22 D 74834 Elztal Dallau Germany Tel 49 6261 9410 Fax 49 6261 17741 Asia Pacific Rockwell Automation 55 Newton Road 11 01 02 Revenue House Singapore 3
105. ID DESC CM102 CONTRO EUDESC CM102 DEVCTL_102 DEVCTL f HIALM PR Chain CTOICS CTO WIALhA Cle Point Name CM101 DATSACQ_101 Parameter Selected Item cw 01 DATAACO_101 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 Chii DATAACO 101 PLLALW F L Publication 1757 UM006A EN P May 2002 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 Ld 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 ele CM102 Project OEY L Oe DEWCTL_102 CMIO1OSTeASCO 107 PVLLSL FL FF HORMMODESTTR MORAAL HUM STAT Es z C M i0i DATA 101 P LOL L Fi FF c FF LOG FF ree gur FTRIGS ore Publication 1757 UMO06A EN P May 2002 Configurating the 1757 FIM 4 51 Loading Components Online PLX About load operations The ProcessLogix system provides the ability to build Foundation Fieldbus control strategies offline online or without being connected to the field compone
106. INE TS i a a Foundation Fieldbus Configuration Tool To configure the 1788 CN2FF you use 1788 FFCT Configuration Software tool This Fieldbus configuration software uses RSLinx to connect via ControlNet supports redundant ControlNet to any CN2FF devices on the Network Using the FFCT software you can configure any Foundation Fieldbus device as well as view display and monitor all Foundation Fieldbus parameters You can also use this tool to setup the data exchange to PLCs ControlLogix and ProcessLogix processors Centralized Operator Interface The ProcessLogix R400 0 Station application includes Detail Displays dedicated to the configured FIM associated H1 Links fieldbus device and associated fieldbus function blocks They provide access to the same parameters that are accessible through the control charts and configuration forms in the Monitoring tab of Control Builder This includes manufacturer specific parameters where applicable The reporting of alarm conditions and retrieval of process data for inclusion in group trend history and schematic displays is closely integrated with ProcessLogix s existing notification management system The existing access authorization levels apply and will take precedence over fieldbus restrictions specified in Device Descriptions Publication 1757 UMO06A EN P May 2002 2 6 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002
107. It includes a fieldbus Analog Output AO function block to integrate the Logics 1400 Valve Positioner with the PI controller output from the control strategy The CM102 includes a ProcessLogix Device Control DEVCTL function block to control the recycle pump through corresponding Discrete Input and Discrete Output Input Output Module function blocks It also includes links to the LO and LOLO alarm flags for the DATAACQ block in CM101 for device safety override and output override interlocks respectively The recycle pump is to be restarted at 35 percent Publication 1757 UMO06A EN P May 2002 4 6 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 Depending on the Function Block execution and Publishing schedule this might take as little as 100 mS but 3 seconds is recommended by the FF and it doesn t hurt to allow extra time for slow nodes or slow commands 2 T2 specifies how long a Remote Node such as a Pressure Transmitter waits for the next System Management message in
108. Management Description 2 6 ADOUL the Deyice ODICCK ogak ood eds eee ee ees 2 7 ADOUL tne VED ODC Eada ka ace dott pa amp Mei bt ae te a 2 7 Fieldbus Device Analog Input Integration 2 7 Fieldbus Analog Input data manipulation 2 8 Fieldbus device Analog Output or PID integration 2 9 Fieldbus Analog Output or PID data manipulation 2 11 Fieldbus device Discrete Input integration 2 13 Fieldbus Discrete Input data manipulation 2 14 Fieldbus device Discrete Output data integration 2 15 Fieldbus Discrete Output data manipulation 2 16 Interface Connections SUMMATLY 4 244 600444 0444444 2 16 Fieldbus status data details 000 2 17 Fieldbus Status Indications 6 0 4654000505 2 18 Control Mode Interaction ot 4d a8 KARAS SES oar 2 19 Fieldbus Block Modes Versus Processlogix Modes 2 19 Control Mode Priorities and Indications 2 20 Rotary Switch Model versus Toggle Switch Model 2 21 Display indications and mode calculation 2 23 Link and Block Scheqdules 24 6442sr54042 04 a R02 2 24 Link Active Scheduler LAS 0 000005 2 24 Dnk SCC UN eese ae eek goons at Pages Ake Re a ede ae 2 25 Function block execution schedule 2 26 Tags Addresses and Live List 242443 4202040444 44004 2 28 Tag and address assignments 0008 2 28 Live List and Uncommissioned Devices
109. N DV_LO_ALM LO_LO_ALM ROUT_OUT Publication 1757 UMO06A EN P May 2002 The Fieldbus Communication Model 1 25 Ratio Block Figure 1 13 Functional schematic for Ratio function block iN gt IN 1 gt BKCAL_IN gt CAS IN gt RCAS IN gt TRK_IN_D gt TRK_VAL gt ___ BKCAL_OUT RA BKCAL_OUT OUT RCAS_OUT RCAS_OUT BKCAL_IN _ Setpoint Ratio Output CAS_IN SP RATE DN SP GAIN OUT_HI_LIM OUT SP_RATE_UP OUT LO LIM RCAS_IN SP_HI_LIM BAL TIME SP_LO_LIM Calc PV IN 141 Filter GAIN PV RA_FTIME Filter IN PV_FTIME Alarm l Bly Output Track Mode TRK_SCALE SHED_OPT TRK_IN_D TRK VAL Table 1 M Ratio Block Specifications Description The Ratio function block set point is the ratio of its output to its input A ratio set point of 0 5 produces an output that is one half of its input The input IN_1 is either a wild flow or the output of a blend pacing controller The output can be used as the set point for a secondary flow controller An input IN from the secondary measurement is used to calculate the actual ratio which is displayed as the PV A functional schematic of the block is shown in Figure 1 13 for reference
110. N AICH OUT a3 3d SMAR PID PID CN BECAL IN AICH OUT At ie ad SMAR A A Ie CH BECAL IH ACH OUT As E ad SMAR 5 5 CN BECAL IN ACH OUT as Be ad SMAR SC SC Ie CH BECAL IN ACH OUT A7 i ad SMAR I 1 3d SMAR AA AA ee S T HW TEMP a HW TEMP RB RB i Hw TEMP Al Al F HwlempPID PID T CHethacldl 1 AQ Modit 0 CHA S SMAR 1 40 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 The AI function block FB in the E H pressure transmitter the AI FB in the Honeywell temperature transmitter and both the Pressure AI and the Temperature AI in the Rosemount Pressure Transmitter are all connected to the CN2FF Multiple Analog Input MAI function block The AO FB in the Multiple Analog Output MAO of the CN2FF is connected to the CAS_IN pin of the SMAR 1 AO function block The Publication 1757 UMO06A EN P May 2002 ControlLogix Application 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 cre
111. NSDUCER v Err 7005 00S NORMAL 1101 RESOURCE V Err 7005 00S NORMAL ONLINE Err 7005 Err 7005 Err 7005 V Restore all blocks to Post Load State after load IN Note Mismatched states are found Cancel Help If you want to load just a Fieldbus device click the With Contents so you can load more than one device at a time device icon and click Tools gt Load Use LINK Load 3 Verify that checkmarks appear in the LINK and Device checkboxes listed in the Load column Ll LINK 5101 w Ls14_101 Le 14_101 TRANSDUCER Le 14_ 101 RESOURCE ww ST_101 gt T_101 TRANSDUCER 1_101 RESOURCE 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 LINK S101 ee f L14 101 L 14_101 TRANSDUCER L 14_101 RESOURCE V ST_4101 Ls ST_101 TRANSDUCER ST_101 RESOURCE 5 To change the Post Load State for selected components click the appropriate Post Load State row The dropdown menu opens Post Load Sta 6 Select the appropriate state Publication 1757 UMO06A EN P May 2002 4 60 Configurating the 1757 FIM 7 Click OK The load is initiated shown by the Load window If errors are detected they will be listed and you will prompted to select whether or not you want to con
112. O Side The AO FB in the output device must be in the Cascade Mode to accept inputs from the MAO FB If the data from the MAO module is listed as BAD you are probably not providing the required FF status byte with your output PV To show good data the FF Status Byte needs to have a numeric value between 112 and 128 The best approach is to copy the FF status from the inputs that are supplying the PVs that were manipulated to produce the AO Publication 1757 UMO06A EN P May 2002 F 52 1788 CN2FF Installation Example 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 IMPORTANT Faja HI FEUS Fieldbus Configuration System File Edit View Configure Zoom Window Help Hja sa El oe Log Notes Table F 2 Troubleshooting If you see Bad Status Bad Data Value a function block in OOS mode a Transducer function block in OOS mode Bad Data in the Monitor window Transducers Function Blocks Rs Do this Make sure to see that all the Function Blocks and Transducers are in the proper operating mode OOS Out Of Service Mode In the FFCT window click on the T with the red X through it That will Unhide the Transducer Function Blocks Check to see that the Transducer FB is not in the
113. O 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 8 Sample Cascade DO Configuration Function Block Applicat Loop Time 1s a Stale Limit i Ege Ral al AT 34 CNetMacld03_DO ModuleO_1 CNDO CN BEKCAL IN DO CN OUT DO ad DiscreteQutput DO CN EBKCAL IN DI CN OUT DI CAS IN D TT PCN BKCAL IN D2 CN OUT D2 BKCAL OUT D CN BKCAL IN D3 CN OUT D3 e DO Alarms CN BKCAL IN D4 CN OUT D4 Trends P CN BKCAL IN D5 CN OUT D5 CN BKCAL IN D CN OUT D j PCN BKCAL IN D7 CN OUT D7 gt Alarms Pe The configuration shown in Figure 7 8 the controller provides the necessary mode handshake for cascade initialization of the DO block In this case you connect CN_OUT_Dx of the MDO block to the CAS_IN_D parameters of the DO block and the BKCAL_OUT_D parameter of the DO block to BKCAL_INv of the MDO block Note that there is a strict ordering relationship between the CN_OUT_Dx and CN_BKCAL_IN_Dx parameters of the MDO block that is CN_BKCAL_IN_D0O is associated with CN_OUT_D0O CN_BKCAL_IN_D1 with CN_OUT_D1 and so on You can connect the MDO block to any parameter that is a byte value and status combination In other words you can bring values from a PLC processor to any function block The MDO block is not limited to interfacing with DO function blocks Attribute Number 3 151
114. OOD Non Cascade Alm U Crit GOOD Non Cascade Alm U Crit L GOOD Non Cascade Alm U Crit H GOOD Non Cascade Alm U Crit C GOOD Cascade Low Limit GOOD Cascade High Limit GOOD Cascade Constant GOOD Cascade Acknowledge Initialization IA NoLimit J o InitAck GOOD Cascade Acknowledge Initialization IA fLowLimit J InitAck L GOOD Cascade Acknowledge Initialization IA High Limit InitAck H GOOD Cascade Acknowledge Initialization IA Constant 00 InitAck C Publication 1757 UMO06A EN P May 2002 B 4 Fieldbus Status Display Indications Table B 1 Fieldbus Status Byte Independent Status Field GOOD Cascade Request Initialization IR f LowLimit J R Reqlnit L GOOD Cascade Request Initialization IR High Limit R Reqlnit H GOOD Cascade Request Initialization IR Constant R Reqlnit C GOOD Cascade Notlnvited GOOD Cascade ae E Notlnvited L GOOD Cascade Notlnvited H 6000 Cascade Nativited GOOD Cascade NotSelected GOOD Cascade N NotSelectd L GOOD Cascade NotSelectd H GOOD Cascade NotSelectd C GOOD Cascade Local Override LO No Limits J 0 OverrideLocl GOOD Cascade Local Overide LO flowlimt 0 OverrideloL GOOD Cascade Local Overide L0 Hohtimt 0 Overridelo GOOD Cascade Local Override LO f Constant 0 OverrideLc C GOOD Cascade Fault State Active FSA Nomis F FaullStat GOOD Cascade Fault State Actve FSA lowlimt F FautStatel
115. Open This initiates the firmware upgrade gt Device Firmware Upgrade Bes x Cancel Physical Device Identification DEW ID 485 4C0002 HW L ST S000 DEFO1EO000 PO_T4G ST DEFOIEO i Application Identification strings Application Identification hex VENDOR 00485974C DEY_TYPE O002 Vendor Honeywell Model 5 T2000FF Revision Rev 3 00 Address 15 DEY_REY 05 DDOLREY 4 Sending data chunk 1726 of 2315 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 Jclose the window 8 Verify that there is an existing template listed in the Templates column that matches the upgraded version of the device Interpreting Component LED Indications 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 Uncommissioned Device Ma E ST DEF12E4 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 Include the fieldbus device in the control strategy and the Link Active Schedule
116. PV parame ter and parameters that have the same scaling as PV DS 68 C Scaling 11 VIEW_2 Static The Data type consists of data that describes floating point values for display purposes It uses the following four elements e Engineering Units at 100 percent e Engineering Units at 0 percent e Units Index e Decimal Point Table A 90 PV_STATE Classification Description FF Data Type Usage Length Valid Views Storage simple Variable Defines the index to the text describing the states of a discrete PV Unsigned 16 C Contained 2 VIEW_2 Static No Q parameters Publication 1757 UMO06A EN P May 2002 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 FF Data Type Float Range Positive Usage C Contained Length 4 Valid Views VIEW_4 Storage Static Table A 93 RCAS_IN Classification Description FF Data Type Usage Length Valid Views Storage Remarks Publication 1757 UMO06A EN P May 2002 Record Represents target setpoint and status provided by a supervisory host to the analog control or output block DS 65 C Remote
117. PV value regardless of the Use PV for BRCAL_OUT CONTROL_OPTS status Use the Direct Acting CONTROL_OPTS to define how a change in PV relative to the SP affects the output When Direct Acting is ON the output increases when the PV exceeds the SP When Direct Acting is OFF the output decreases when the PV exceeds the SP Be sure this option is set correctly and never changed while in the Automatic mode since it makes the difference between positive and negative feedback This option setting also affects the calculation of the limit states for BKCAL_OUT This block includes a Feed Forward algorithm It accepts a value that Is proportional to some disturbance in the control loop as its FF_VAL input The FF_SCALE values convert the FF_VAL to a percent of output span value The converted value is multiplied by the FF_GAIN and added to the target output of the block s algorithm If the status of FF_VAL is Bad the last usable value will be used to prevent a bump in the output When the status returns to Good the block adjusts its Integral RESET term to maintain the previous output The TRK_VAL input brings in an external value or uses a constant The TRK_SCALE values convert the TRK_VAL to a percent of output span value If the CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true the converted TRK_VAL replaces the output OUT when the block is in Automatic Auto Cascade Cas Remote Cascade RCas or Remote Out ROut mode The CONTROL_OPTS
118. RMAL is written to Target mode the MODE TARGET the FIM OOS MAN AUTO CAS RCAS ROUT replaces it with the value from MODE NORMAL MODE ACTUAL Enumeration Read Only Actual Mode OOS IMAN LO MAN AUTO CAS RCAS ROUT MODE PERMITTED Bitstring Read Write If anew MODE NORMAL value is Permitted mode entered it is validated against MAN AUTO CAS RCAS ROUT the MODE PERMITTED values OOS is always permitted MODE NORMAL Enumeration Read Write If anew MODE NORMAL value is Normal mode entered it is validated against MAN AUTO CAS RCAS ROUT the MODE PERMITTED values OOS is not Normal Table 2 D shows how ProcessLogix modes are mapped to fieldbus ones Table 2 D Mapping ProcessLogix Modes to Fieldbus ProcessLogix Mode Comment NORMAL When setting as target mode read MODE NORMAL value and write to MODE TARGET BCAS Not used in fieldbus blocks Attempt to set to target is illegal NONE Not used in fieldbus blocks Attempt to set to target is illegal Publication 1757 UMO06A EN P May 2002 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 The Control Order interpretation is based on the traditional control engineer
119. RPWRUP is enabled the SMK will enter the SM_OPERATIONAL state on powerup e If OPERPWRUP is disabled the SMK will enter the INITIALIZED state Publication 1757 UMO06A EN P May 2002 4 16 Configurating the 1757 FIM 12 Click the Application tab SYSTEM LINK Block LINK51 Parameters Project ae xi Main System Management Network Management Application Server Parameters Device Class Device Name FIMLINK Communications Group Number Bo Communications Class 0000100000000000 Communications Sub Class ooooo00000000000 Max Num Client YCA Supportec a Max Num Server YCR Supporte 3 Max Num Source YCA Supporte a Max Num Sink YCR Supported a Max Num Subscriber YCA Supp a Max Num Publisher YCA Suppo a Max Services calling for Client 00 Max Services called for Client 00 Max Services calling for Server 00 Show Parameter Names Cancel Help 13 In the Device Name DEVNAME field either leave the default name or enter a new name of up to 33 characters 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 The parameters on the Network Management tab are only accessible in the Monitoring tab with the FIM LINK communicating with the system Click the
120. 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 2 Sample Application and Control Strategy Integrating Fieldbus Devices with a ProcessLogix System as the Supervisory Control CM101 FF gt cpm AI PID CEE 4 FF DACA 1O O FIM cay Smart Pressure Transmitter Surge Tank T 106 CPM CEE CM102 A A DI O DEVCTL LL FTRIG Interlocks DO 2000 Gallons SP 50 HI 70 HIHI 85 LO 25 LOLO 15 Nominal Recycle Feed 100 gal min AO Logix 1400 Valve Positioner yar Ta a pra yt F I r Recycle Pump Shut Off at LOLO Restart at 35 IOM IOM DI DO A Feedback Command Publication 1757 UMO06A EN P May 2002 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 min
121. SLC from the Linking Device over ControlNet 1 Double click on the Device Info icon as b ssa E EaD LD 4 Log Notes Network Parameters Mi Schedule s Function Block Application LD 9 ID 4E 49434002 _CH FF 2 gt Device Info o E Resource RB A new screen displays all the data produced by the attached Fieldbus Devices by Function Block Tag name Publication 1757 UMO06A EN P May 2002 1788 CN2FF Installation Example F 37 Figure F 4 Device Information Screen dbus Configuration System ver 2 3 6 Device 4E 49434002_CH FF 2_802200 Device Info indaw Help Device dE4 INPUT Assembly 6434002 CH FF 2 602200 ID 4F49434002 CH FF 2 80220014 CN7FF interface name FieldbustTag Hodule Channel Instance Handshake Attribute Offset Length DataType FR 3 Pres AT Moduled_oO O0 1 VALUE 0 4 CNFLOAT CHSTATUS 4 1 CHBOOL FFSTATUS 5 1 CHUSIHT FE 3 Temp AT Moduled oO 1 2 VALUE is 4 CHFLOAT CHSTATUS 12 1 CHBOOL FFSTATUS 13 1 CHUSINT E H 5 Pres AT Moduled_O z 3 VALUE 16 4 CHF LOAT CHSTATUS 20 1 CHBOOL FFSTATUS 21 1 CHUSIHT E H 5 Temp AT Moduled 0 3 4 VALUE 4 4 CHFLOAT CHSTATUS 25 1 CHBOOL FFSTATUS 29 1 CHUSIHT Connection Port Number Offset in bytes from th Length of Used with ControlNet start of the ControlNe valein Message Instructions produced data bytes 2 Expand the window so you can read all the columns This screen is the reason we recomme
122. Server Parameters tab SYSTEM LINK Block LINK51 Parameters Project ae x Main System Management Network Management Application Server Parameters m Server Parameters Point Detail Page Associated Display Group Detail Page Control Level 200 Control Area EU HI Parameter EU LO Parameter M Show Parameter Names Cancel Help Publication 1757 UM006A EN P May 2002 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 TIP You must have the DD files for the fieldbus device either on a floppy diskette or the Foundation Fieldbus Compact Disc supplied by the gt manufacturer This means you can make a device template while the system is offline You can skip this procedure if a template for the given device type already exists in the Control Builder Library database Rockwell Automation has tested and included some devices as part of the base product for you convenience See Appendix E for general information about using the Fieldbus Library Manager utility and lists of a
123. The 1788 FFCT software is not compatible with Windows 95 98 _I High Resolution Monitor 1200 x 1024 recommended Use at least 1024 x 800 The Fieldbus Configurator is much easier to use with a high resolution monitor If you use a 640 X 480 screen you will be unable to find some of the items on the toolbars L 1784 PCIC 1784 KTCX15 or 1784 PCC card for direct connection to ControlNet J PLC 5 or CLX or PLX or SLC with a ControlNet Interface _I One Operating ControlNet Network supporting the Controller the PLC 5 CLX or PLX or SLC plus a PC with KTCX15 1784 PCC or a 1784 PCIC and one or more 1788 CN2FF s LJ One or more Registered Fieldbus devices 1788 FFCT software requires that the Fieldbus devices be on line Off line configuration will be supported later Required Software Example Description 1788 CN2FF Installation Example F 3 LJ RSLinx version 2 10 166 or later OEM version or better IMPORTANT RSLinx Lite is not compatible Ld RSNetworks for ControlNet version 2 25 or later to schedule data to the controller I 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 J 1788 FFCT the Foundation Fieldbus Configuration Tool Version 2 3 6 or later _I Device Descriptions DD s for the Linking Device and for each of the Fieldbus Devices you plan to connect to the Fieldbus DD s that match the
124. UMO06A EN P May 2002 2 16 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 Fieldbus Discrete Output data manipulation When the DOI 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 DOI n with status parameter to the fieldbus data structure DS 66 of the CAS_IN_D parameter It interprets the value portion in ProcessLogix terms and converts it to fieldbus representation The CEE output agent also accepts a single BKCAL_OUT_D parameter with the fieldbus data structure DS 66 and maps it to the BACKCALIN parameter of the DEVCTL block in ProcessLogix terms It sends the outgoing control signal either to a subscribed parameter or a client server written parameter through the CAS_IN_D or RCAS_OUT_D connection It can optionally receive the backcalculation signal from either the corresponding published parameter or client server read parameter The ProcessLogix data quality is converted to fieldbus data quality The ProcessLogix Good indication is represented as fieldbus Good Cascade The ProcessLogix control initialization indicators map only to the limited number of substatus conditions that have corresponding indications in fieldbus
125. UP UPDATE_EVT Publication 1757 UM006A EN P May 2002 The Fieldbus Communication Model 1 15 Control Selector Block Figure 1 7 Functional Schematic for Control Selector Function Block SEL1 gt gt OUT SEL 3 gt CS amp gt BKCAL SEL 2 BKCAL_IN gt p BKCAL SEL 3 BKCAL_IN __ Selection agg E E SELI SEL TYPE OUT_HI_LIM OUT SEL 2 OUT LO LIM SELI Back Calc BKCAL_SEL_1 TTE BKCAL_SEL_2 i BKCAL SEL 3 Publication 1757 UM006A EN P May 2002 1 16 The Fieldbus Communication Model Table 1 G Control Selector Block Specifications Description Function Notes Parameters see Appendix A for definitions of each parameter 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 All inputs must have the same scaling as OUT since any one can be selected for OUT Supports Out of Service OOS Initialization Manual Man Local Override LO Manual Man and Automatic Auto modes If an input has a sub status of Do Not Select it will not be selected e Three separate back calculation outputs BKCAL_SEL_1 2 3 are available one for each input SEL_1 2 3 The status will identify those inputs t
126. US data nif det DO NOT CLICK THIS BROWSE BUTTON The program will automatically install the Device Descriptions in the default directory C NIFBUS DATA If you accidently click Browse go back and enter the IMPORTANT 7 1 8 IMPORTANT name of the default directory C nifbus data 2 Click on Import DD Publication 1757 UMO06A EN P May 2002 1788 CN2FF Installation Example F 15 You see Import DD Enter the ffo File Hame Browse lt HER Import OD Dialog will create subdirectories under the base directory of Device Description based on your manufacturer ID and Device Type and then copy tto and sym file there 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 If you are not given the DD for a device you can download most of them from the Fieldbus Foundation Web Site www Fieldbus org You can also go to the suppliers web site and download the DD files After you click Browse you will need to navigate to the location of the DD s you are trying to install You see Look ire Sy CN2FF DD amp fm F 0101 ffo Filename 01101 ffo Files of type oD Files ffo Canc
127. YALM SY HIALM PR HIALM SY HIALM TYPE INALM LASTGOODPY LOCUTOFF P1 P1CLAMPOPT PIEU PIFILTINIT PIFILT TIME PISTS PY PYAUTO PYAUTOSTS PYCHAR PYEUHI PYEULO PYEXHIFL PYEHILM PYEXLOFL PVEXLOLM PYFORMAT Visible Pins Input Top sad View Options IV Show Value IV Show Label Pin Position Input Left input Left Right Top Bottom Output Bottom Array Indic ES a lt Remove Output Right Move Up Move Down Insert Blank Show Parameter Names Cancel Help Configurating the 1757 FIM 4 43 9 Select PVLLALM FL in the Parameters list Parameters PYHISIGCHG TP View Options PYLLALM DB PYvLLALM DBU If Show Value W Show Label Pin Position Output f input PVLOALM PR 10 Verify that the Pin Position is Output and Top Bottom 11 Click Add PVLLALM FL is added to the Output Bottom list Output Bottan Pi PY LLALM FL 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 Output Bottom 17 Select PV in the Parameters list 18 Select Left Right in the Pin Position box Publication 1757 UM006A EN P May 2002 4 44 Configurating the 1757 FIM 19 Click Add PV is adde
128. _ALM Classification Description FF Data Type Usage Length Storage Remarks Record Identifies the status and time stamp associated with the low deviation alarm DS 71 C Alarm 16 Dynamic Read Only The Data type consists of data that describes floating point alarms It uses the following five elements e Unacknowledged e Alarm State e Time Stamp e Subcode e Value Publication 1757 UMO06A EN P May 2002 A 14 Standard Function Block Parameters Exxx Blocks Fxxx Blocks Publication 1757 UMO06A EN P May 2002 Table A 37 DV_LO_LIM Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the low deviation alarm limit setting in engineering units Float infinity PV Span to 0 C Contained 4 VIEW_4 Static Initial value is infinity Table A 38 DV_LO_PRI Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines priority of the low deviation alarm Unsigned 8 0 to 63 C Alert Priority 1 VIEW_4 Static Initial value is 0 No E parameters Table A 39 FAIL_SAFE Classification Description FF Data Type Range Usage Length simple Variable Condition set by lost of communication to an output block failure promoted to an output block or a physical contact When the failsafe action is active the output function blocks will perform th
129. a Type Usage Length Record Represents third input value to the selector DS 65 Cascade Input 5 Publication 1757 UMO06A EN P May 2002 A 40 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Valid Views Storage Remarks VIEW_1 VIEW_3 Non Volatile 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 e Status e Value Table A 107 SEL_TYPE Classification Description FF Data Type Range Usage Length Valid Views Storage simple Variable Defines the type of selector action as High Medium or Low Unsigned 8 1 High 2 Low 3 Medium C Contained 1 VIEW_4 Static Table A 108 SET_FSAFE Classification Description FF Data Type Range Usage Length Storage Remarks simple Variable Allows the failsafe condition to be manually initiated by selecting Set Unsigned 8 1 Off 2 Set C Contained 1 Dynamic The operator can control PROGRAM or LOCAL access to this value Table A 109 SHED_OPT Classification Description FF Data Type simple Variable Defines action to be taken on remote control device timeout Unsigned 8 Range Usage Length Valid Views Storage Remarks Standard Function Block Parameters A 41 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
130. aa F 41 Schedule the Connection Between the Controller and the Linking Device F 44 View the Controller Tags o naana 04644480640 F 44 Testing the Installation Example F 46 Messages to PLC 5s and CLX to Get Data from CN2FF F 47 Remote Configuration of a Fieldbus Network via Pie Wes N ZR Mr Bad dats oa A ele aes de ed F 49 Troubleshooting an Application 00 F 51 Publication 1757 UMO06A EN P May 2002 xii Table of Contents Publication 1757 UM006A EN P May 2002 Fieldbus Organization Chapter 1 The Fieldbus Communication Model 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 Want more information Visit the Fieldbus Foundation web site at www fieldbus org or the following address for more information 9390 Research Blvd Suite II 250 Austin TX 78759 9780 What ts Fieldbus There are many digital communication technologies being promoted as the future replacement for the venerable 4 20 mA analog standard and most are self described as fieldbus With the exception of FOUNDATION fieldbus virtually all of these technologies were developed for non
131. ace Configuration Utility 2 3 6 DD Info Add Interface Device Edit The changes made in FECONF only takes effect after you start NI FBUS process the next time Now that you have defined the communication path to the Fieldbus network the Device Descriptions DD s need to be loaded for the devices you are going to configure Publication 1757 UMO06A EN P May 2002 F 14 1788 CN2FF Installation Example A DD is a file which describes the FF device to the configuration Installing Device file which describes the FF d he config gs software DD s are like the EDS files we use on DeviceNet and Descriptions DDs 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 MI FBUS Interface Configuration Utility 2 3 6 p DD Info Add Interface Device Fort Edit Fort The changes made in FECONF only takes effect after you start HI FEUS process the next time You see DD Info EJ The base directory for your Device Descriptions The software program will install the C nifbus data Cancel Device Descriptions in the default directory CANIFBUS DATA directory E a a coo impot DD If you change this directory the software have manufacturer specific DD into di may not be able to find the DD s Your standard text dictionary C ANIFB
132. akes this possible The FLM reads the manufacturer s DD for the fieldbus device and creates a device template that is included in the Project tab of Control Builder The device template includes the device s fieldbus function blocks so it can be configured and integrated with control strategies through Control Builder Figure 2 7 shows a simplified functional diagram of how the output from a Device Control DEVCTL function block in a Control Module that is assigned and loaded to the CEE in the Control Processor Module CPM is integrated with a Discrete Output function block in a fieldbus compliant device Figure 2 7 Integration of fieldbus device digital output signal with ProcessLogix control strategy CM DIC PVFL Device BACKCALIN gt Control CPM CEE DI 1 DO 1 RCAS_IN CAS_INA FIM FIM y i a Fieldbus Device gt _ BKCAL_OUT_D CAS IND Digital 1 6 ed gt Output RCAS_OUT_D RCAS_IN_D OUT_D Transducer BACKCALIN Back Calculation Input DIC Digital Input Channel BKCAL_OUT_D Back Calculation Output Discrete FIM Fieldbus Interface Module CAS_IN_D Cascade Input Discrete OP Output CEE Control Execution Environment PVFL Process Variable Flag CM Control Module RCAS_IN_D Remote Cascade Input Discrete CPM Control Processor Module RCAS_OUT_D Remote Cascade Output Discrete Publication 1757
133. alent of a discrete input module in a I O subsystem Each MDI block has eight channels with each channel containing a byte and a status pair The linking device assigns a tag to each MDI block in the form CNetMacldxx_DI_Modulei j7 where xx is the ControlNet network address 7 is the Fieldbus channel number and is the module or instance number Configuration of Discrete Inputs The NI FBUS Configurator lists all the devices and the function blocks in each device in its browse window This includes the DI function blocks in the Fieldbus devices and the MDI function blocks in the linking device You must connect the Fieldbus DI function blocks that will be accessed by the ControlNet controllers or devices to the MDI channels as shown in Figure 7 6 The remaining configuration is similar to that for the analog inputs Figure 7 6 Sample Single Macrocycle MDI Configuration Function Block Application Loop Time 1 9 sec Stale Lirit 1 F E DI OI CHethMfacld03 DI Modat 0 CHED OUT D CH Dd Alanns DI Alms CDI Trends fe Tenk E CH DD CHD cH Dt CHD cH be CHD CHDI A Publication 1757 UM006A EN P May 2002 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 attribut
134. alizes in the disabled state Equation Options FIELD VAL 100 x channel value EU 0 EU 100 EU 0 XD_SCALE Direct PV channel value Indirect PV FIELD_ VAL 100 x EU 100 EU 0 EU 0 OUT _ SCALE Ind Sar Root PV sqrt FIELD_ VAL 100 x EU 100 EU 0 EU 0 OUT_SCALE Parameters ACK_OPTION HI_ALM LO_LIM PV see Appendix A ALARM_HYS HI_HI_ALM LO_LO_ALM PV_FTIME for definitions of ALARM_SUM HI_HI_LIM LO_LO_LIM SIMULATE each parameter ALERT_KEY HI_HI_PRI LO_LO_PRI ST_REV BLOCK_ALM HI_LIM LO_PRI STATUS_OPTS BLOCK_ERR HI_PRI LOW_CUT STRATEGY CHANNEL IO_OPTS MODE_BLK TAG_DESC FIELD_VAL LLY PE OUT UPDATE_EVT GRANT_DENY LO_ALM OUT_SCALE XD_SCALE Publication 1757 UMO06A EN P May 2002 The Fieldbus Communication Model 1 11 Analog Output Block Figure 1 5 Functional Schematic for Analog Output Function Block P BKCAL OUT lt P nmo P OUT RCAS_IN gt RCAS OUT P Transducer ___ BKCAL_OUT RCAS OUT Setpoint Out Convert Output CAS_IN sp RATE DN PV_SCALE OUT SP_RATE_UP XD_SCALE RCAS_IN SP_HI_LIM SP_LO_LIM Simulate sp py SIMULATE CHANNEL Mode PV Convert Failsafe SHED_OPT XD_SCALE FSAFE_TIME PV_SCALE FSAFE_VAL _ READBACK Publication 1757 UMO06A EN P May 20
135. also have to create a new template for the device and or upgrade the device s firmware Use the following procedure to upgrade the firmware in an uncommissioned device through Control Builder This procedure assumes that you have the vendor supplied upgrade file for the device It also assumes that you are monitoring the FIM LINK through the Monitoring tab in Control Builder 1 Double click the uncommissioned device icon a The LINK Parameters window opens SYSTEM LINK Block LINK_S101 Parameters Monitoring Sa x N 7 Main System Management Network Management Application Uncommissioned Devices Server Parameters Uncommissioned Devices ET tag tes Rooel Davee Verve Perman 48574C0002 H W Honeywell ST3000FF Template Not Installed Publication 1757 UMO06A EN P May 2002 6 4 1757 FIM General Maintenance Checkout and Calibration Publication 1757 UMO06A EN P May 2002 2 Click Load Firmware The Device Firmware Upgrade window opens Physical Device Identification Cancel DEVYID 4685 4C0002 H 4 L 5 T S000 DEFOTE OOOO PO_TAG ST DEFOIED if Application Identification strings Application Identification hex Vendor Honeywell Model ST S000FF VENDOR 00486574C DEY_TYPE 000Z Revision Aew 3 00 Address 15 DEW REW 05 DODLREY 04 3 Click Upgrade The Open window opens 4 Locate and select the vendor s upgrade file 5 Click
136. alue is the node address of the primary time publisher for the local link System Management sets it during node address assignment It is a configuration error if the SM Support SM_SUPPORT parameter of the device specified by this node address does not have the Application Clock Synchronization feature bit set To enable the SMK System Management Kernal Operational Power Up state OPERPWRUP click the check box next to the field If the device is in the SM_OPERATIONAL state or fully commissioned and operating when power is lost this parameter controls which state the SMK will enter after powerup If OPERPWRUP is enabled the SMK will enter the SM_OPERATIONAL state on powerup If OPERPWRUP is disabled the SMK will enter the INITIALIZED state Publication 1757 UMO06A EN P May 2002 4 32 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 HONEY WELL ST3000FF_0701 Block ST3000FF_070153 Parameters Project Bis xj Main System Management Network Management Server Server Parameters Point Detail Page Associated Display FO Group Detail Page FO Control Level 200 Control Area PO EU HI Parameter FO EU LO Parameter FO Show Parameter Names Cancel Help IMPORTANT If you have a Distributed Ser
137. ariable Defines the minimum output value limit in all modes unless the CONTROL_OPTS selection No Out limits in Manual is chosen Float OQUT_SCALE 10 percent C Contained 4 VIEW_2 Static Initial value is 0 Table A 84 OUT_SCALE Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record 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 OUT param eter and parameters that have the same scaling as OUT DS 68 C Scaling 11 VIEW_2 Static The Data type consists of data that describes floating point values for display purposes It uses the following four elements e Engineering Units at 100 percent e Engineering Units at 0 percent e Units Index e Decimal Point Table A 85 OUT_STATE Classification Description FF Data Type Usage Length Valid Views Storage simple Variable Represents the index to the text describing the states of a discrete output Unsigned 16 C Contained 2 VIEW_2 Static Publication 1757 UMO06A EN P May 2002 A 32 Standard Function Block Parameters Pxxx Blocks Publication 1757 UMO06A EN P May 2002 Table A 86 PV Classification Description FF Data Type Usage Length Valid Views Storage Remarks Classification Description FF Data Type Usage Length Valid Views Storage Remarks Classification Desc
138. aring the physical device tag and identifying the device are available Operational State In the operational state a fieldbus device has both a physical device tag and an assigned node address Its application layer protocols are started to allow applications to communicate across the network Additional network management configuration and application configuration may be needed for the device to become fully operational Fieldbus device matching rules The FIM initiates the following matching rules depending upon whether or not the device identification C DEV_ID is specified when a device is loaded from Control Builder Table 4 D Ifthe Device ID is And the Device State Is The matching rule is Specified un initialized The device ID DEV_ID must match If the desired physical device tag PD_TAG and node address ADDR are available FIM will assign them to the device Initialized The device ID DEV_ID and physical device tag PD_ TAG must match If the desired address is not in use FIM will assign it to the device Operational The device ID DEV_ID physical device tag PD_TAG and node address ADDR must match those specified through configuration in Control Builder Any mismatch results in an error Not specified Initialized The physical device tag PD_ TAG must match If the desired node address ADDR is not in use FIM will assign it to the device Operational The physical device tag PD_TAG and
139. ars in the lower right corner of the toolbar Shortcut to fbcon exe indicating that the NIFB software is running Use this section if NIFB does not start NIFB Software Install If this window does not disappear but says that NIFB can t find Interface X on Board Y You have a problem Do the following 1 First look at RSLinx to verify that you can see all the ControlNet devices on the network including the CN2FF If you see the Mac ID you re trying to configure but you got the message check to see that you entered the correct Driver on the Interface screen refer to Adding an Interface Device on page F 7 The path was not entered correctly refer to Assigning a Path to the 1788 CN2FF page F 10 The path will always start with 2 and end with 2 if your PC is on ControlNet Don t put a space before the first 2 or after the last 2 Use only one space between each number in the path statement e The MAC ID of the CN2FF and the MAC ID entered do no agree refer to step 9 on page F 12 After you edit any configuration attributes you must close the NIFB software for the changes to take effect The NIFB exe program does not go back and check for changes TIP Sometimes you may think the NIFB software is closed but it could still be running To double check look at Microsoft Task Manager and gt review the status of NIFB exe If it is still open it will be listed on the Task Manager highligh
140. as 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 Function Notes e Supports Out of Service OOS Initialization Manual I Man Local Override LO Manual Man Automatic Auto Equation Options Cascade Cas and Remote Cascade RCas modes The output supports the track algorithm The Balance Ramp option is supported The CONTROL_OPTS selection Act on IR determines whether initialization requests are to be passed on or acted on locally by changing the BIAS value If the Act on IR option is false a status of Not Invited NI or Initialization Request IR at BRKCAL_IN will be passed to BKCAL_OUT The BKCAL_OUT value will be calculated from the value of BKCAL_IN adjusted for SP and GAIN as determined by the control or process status of IN_1 When the upstream block sends an Initialization Acknowledge IA status this block will send IA status since its output will now be nearly equal to the value of BKCAL_IN If the Act on IR option is true a status of NI or IR at BKCAL_IN results in an adjustment to SP to balance OUT to the value of BKCAL_IN The IA status can be sent as soon as IR is detected BKCAL_OUT will not request initialization The TRK_VAL input brings in an external value
141. as or Ratio to return to the operator set value In PID block specifies the time constant to be used to move the integral term to obtain balance when the output is limited and the mode is Auto Cas or RCas Float Positive C Contained 4 Valid Views Storage Remarks Table A 6 BIAS Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks Standard Function Block Parameters A 3 VIEW_4 Static Initial value is 0 simple Variable specifies the Bias value in engineering units to be used in computing the function block output Float QUT_SCALE 10 percent C Contained 4 VIEW_1 VIEW_3 Non Volatile Normally the operator has permission to write these values but PROGRAM or LOCAL remove the permission and grant it to a supervisory computer or a local control panel Table A 7 BKCAL_HYS Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the amount of change an output value must attain from the limit before the limit status is turned OFF Float 0 to 50 percent of output span C Contained 4 VIEW_4 Static Initial value is 0 5 percent Table A 8 BKCAL_IN Classification Description FF Data Type Usage Length Record The value and status from a lower block s BKCAL_OUT that is used to prevent reset windup and to Initialize the control loop DS 65 Back Calculation Input
142. ate a ControlNet Object in the CN2FF that can be sent to controllers using RSNetworks or ControlBuilder depending on which controller you are using IMPORTANT If a Fieldbus Device becomes disconnected from the Fieldbus or suddenly stops transmitting data or if the transducer stopped functioning in a transmitter and the device could not produce data the CN2FF will still retain the last valid value that it received To handle this the Fieldbus Status Byte and or the byte listed as the ControlNet Status Byte will change It is absolutely necessary that the control application program monitor the Status of the PV and take whatever action is appropriate if a PV so no longer valid We are now ready to use RSLogix 5000 and RSNetWorx software to set up and schedule a connection between the ControlLogix system and the Linking Device Normally all data exchanged between the ControlLogix controller and the CN2FF Linking Device is scheduled 1 Open RSLogix 5000 software and create a project called CN2FF 2 Add a 1756 CNBIRI B to your project in the I O configuration folder The next step is to add the 1788 CN2FF module to the I O configuration below the 1756 CNBIRI B However the RSLogix 5000 software does not currently support the 1788 CN2FF so we have to select the generic module connection 3 Add a CONTROLNET MODULE connection below the 1756 CNBIRI B This connection will be used for the1788 CN2FF module 4 Fill in t
143. ation 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 The device alarms are associated with actual device conditions or processes within the block as indicated by BLOCK_ERR and XD_ERROR bitstring alarms These alarms are reported as device or system alarms into the ProcessLogix notification system Table 2 K summarizes the possible fieldbus alarm enumerations and lists the alarm event type identification to be used in the alarm summary and event summary displays in Station change ROC alarms ROC alarms can only be generated in applications that use ProcessLogix data acquisition blocks for input signal conditioning Fieldbus alarm functions do not support rate of Table 2 K Fieldbus alarm enumerations and alarm event type identification Enumeration Deserion Avon Twe Publication 1757 UMO06A EN P May 2002 2 34 Integrating Fieldbus into Rockwell Automation Logix System Table 2 K Fieldbus alarm enumerations and alarm event type identification BLOCK BLOCK_ERR 5 Dev Fault State Set FFFLSAFE ATTENTION When using the 1788 CN2FF no alarms come from Fieldbus devices when used with ProcessLogix Data with status will be produced
144. ave all other parameters at their default values as they do not apply to this example Click OK to close the window and save the values Publication 1757 UMO06A EN P May 2002 4 36 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 FMB EFL LINK_s101 oa m B amp ST101 E RESOURCE E TRANSDUCER ER UNK S5102 33 Project 45 Monitoring M Library 2 Click and drag the AI block i to CM101 chart An FF AI block is added to the CM101 chart HOM EVWELLSTA000F F_N A Al DEVICE S710 OUT WaLUE 3 In the Library tab expand the DATAACQdirectory by clicking the Se AURILIARY Sa DEYCTL 2 DATAACO Ooh DATAACO Configurating the 1757 FIM 4 37 Click and drag the DATAACQ block F Saale to the CM101 chart A DATAACO block is added to the CM101 chart DT SD OA ac DAT AAC HA PysRCO PT ON LYSUTO PAFILTTIME O PYEULO PYEWHI 10 c 2 In the Library tab expand the REGCTL directory by click the Ey E AUTOMAN EJ FANOUT OVADSEL z PID PIDFF POSPROP PULSECOUNT Ey PULSELENGTH Publication 1757 UMO06A EN P May 2002 4 38 Configurating the 1757 FIM i to the CM101chart The PID block is added t
145. ayer FAS Fieldbus Message specification FMS Functional Description Defines the transmission medium for fieldbus signals and the message conversion tasks to from the Communication Stack Based on the Manchester Biphase L Encoding technique so a FOUNDATION Fieldbus FF device interprets a positive transition in the middle of a bit time as logical 0 and a negative transition as logical 1 Complies with existing International Electrotechnical Commission IEC 1158 2 and the Instrumentation Systems and Automation Society ISA 50 02 physical layer standards And it can be used with existing 4 to 20mA wiring Defines how messages are transmitted on a multi drop network It uses a deterministic centralized bus scheduler called a Link Active Scheduler LAS to manage access to the fieldbus It controls scheduled and unscheduled communications on the fieldbus in a publish subscribe environment Identifies device types as Basic Device Link Master or Bridge A Link Master device type can become a Link Active Scheduler LAS for the network Defines the types of services used to pass information to the Fieldbus Message specification layer The types of services are defined as Virtual Communication Relationships VCR The VCR types are Client Server Report Distribution and Publisher Subscriber The Client Server type handles all operator messages The Report Distribution type handles event notification and trend reports
146. be terminators on each side of the repeaters A Fieldbus with one repeater will use four terminators you terminate each Fieldbus segment Publication 1757 UMO06A EN P May 2002 D 8 Fieldbus Wiring Considerations Notes Publication 1757 UMO06A EN P May 2002 About Fieldbus Library Manager Appendix E 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 It reads the DD binary files from a user supplied floppy diskette or a Foundation Fieldbus Compact Disc in an offline mode It does not read data directly from an online fieldbus device DD s can also be downloaded from www fieldbus org Figure E 1 Fieldbus Library Manager uses vendor DD file to create device template for Control Builder Control Builder Library Vendor l S Fieldbus AVe def Fy Library Manager bid nal Template Open Server Publication 1757 UMO06A EN P May 2002 E 2 Fieldbus Library Manager Description The FLM features a Windows type interface with drop down menus toolbar
147. bit position once it is read as a 1 This section describes configuration of the linking device to control any analog value and status in a Fieldbus device such as in a Analog Output AO function block It also describes the attributes of the created ControlNet analog output object The linking device contains two of MAO block instances on each Fieldbus channels Each instance of the MAO block is the software equivalent of an analog output module in an I O subsystem Each MAO block also has eight channels or outputs with each channel containing a float and a status pair Each MAO block has eight inputs to provide for the BKCAL or readback from the analog output function Publication 1757 UMO06A EN P May 2002 7 6 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Publication 1757 UMO06A EN P May 2002 blocks The linking device assigns a tag to each MAO block in the form CNetMacldxx_AO_Modulei 7 where xx is the ControlNet network address 7 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 This includes the AO function blocks in the Fieldbus devices and the MAO function blocks in the linking device You must connect the Fieldbus AO function blocks that will be controlled by the ControlNet controllers or devices to the MAO channels The cont
148. bus device states and Fieldbus device matching rules tor more information Fieldbus Device States A fieldbus device is unaware of the steps being executed to configure a network Its System Management Kernel SMK does sense the completeness of its configuration to determine what services it can provide The following table shows the three major states a SMK in a field device must go through and the associated services for each state before a device can fully function on the network Table 4 C SMK State System Management Services Un initialized SM_IDENTIFY SET_PD_TAG Clear False Initialized SM_IDENTIFY SET ADDRESS SET_PD_TAG Clear True Operational SM_IDENTIFY CLEAR_ADDRES FIND_ TAG QUERY FIND_TAG_REPLY FB_START SMIB_Acess Publication 1757 UMO06A EN P May 2002 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 The device is ready to be attached to the network at a default system management node address Only system management services for assigning a node address cle
149. ck includes a Feed Forward algorithm It accepts a value that is proportional to some disturbance in the control loop as its FF_VAL input The FF_SCALE values convert the FF_VAL to a percent of output span value The converted value is multiplied by the FF_GAIN and added to the target output of the block s algorithm If the status of FF_VAL is Bad the last usable value will be used to prevent a bump in the output When the status returns to Good the block adjusts its BIAS term to maintain the previous output The TRK_VAL input brings in an external value or uses a constant The TRK_SCALE values convert the TRK_VAL to a percent of output span value If the CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true the converted TRK_VAL replaces the output OUT when the block is in Automatic Auto Cascade Cas Remote Cascade RCas or Remote Out ROut mode The CONTROL_OPTS Track in Manual selection must be true for this to occur in Manual mode If the actual mode is OOS or IMan the track request is ignored If the TRK_VAL replaces the OUT its status becomes Locked Out with Limits set to Constant The actual mode goes to LO The status of BKCAL_OUT RCAS_OUT and ROUT_OUT goes to Not Invited NI if not already there If the status of TRK_IN_D is Bad its last usable value will be maintained and acted upon If the device restarts losing the last usable value it will be set to false If the status of TRK_VAL is Bad the last usable value wi
150. 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 Err7005 appears in the Current State column if no CPM CEE blocks have been downloaded yet This gt means that the parameter does not exist in the database The State to Load and Post Load States are not applicable since the FIM contains no data at this time The Load Progress window opens Finalizing Load gt CPM30 Publication 1757 UMO06A EN P May 2002 Configurating the 1757 FIM 4 57 6 After the load completes click the Monitoring tab The Monitoring tab opens ra EA CPM30 FE 7 Verify that the FIM icon appears in Monitoring tab 8 Click the H to expand the FIM LINE _ S101 a im LINK_S102 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 In Project tab click the desired LINK icon Publication 1757 UMO06A EN P May 2002 4 58 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 2 Click Tools gt Load With Contents The Load window opens LINK S101 V LX14_101 LX14_101 TRANSDUCER LX14_101 RESOURCE V ST101 Err 7005 Nia 1101 TRA
151. ction Block Parameters Publication 1757 UMO06A EN P May 2002 Table A 14 BLOCK_ALM Classification Description FF Data Type Usage Length Storage Remarks Record 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 As soon as the Unreported status is cleared by the alarm reporting task another block alarm may be reported without clearing the Active status if the sub code has changed DS 72 C Alarm 13 Dynamic The data type describes discrete alarms using the following five elements e1 Unacknowledged e2 Alarm State e3 Time Stamp e4 Subcode e5 Value Table A 15 BLOCK_ERR Classification Simple Variable Description Reflects the error status associated with the hardware or software compo nents associated with a block It is a bit string that can show multiple errors FF Data Type Bit String Usage C Block Error Length 2 Valid Views VIEW_1 VIEW_3 Storage Dynamic Table A 16 BYPASS Classification Simple Variable Description Provides the means to bypass the normal control algorithm When BYPASS is On the setpoint value is directly transferred to the output To prevent a bump upon BYPASS switching the setpoint automatically initializes to the output value or process variable and sets the path broken flag for
152. ctory Creating templates on localhost Creating template 8742 03071 If your ProcessLogix system architecture includes multiple clients the newly created device template 14 15 resides only in the database of the Server designated gt during FLM login You must be logged onto the given Server to access device templates stored in its ERDB through Control Builder Click OK to acknowledge the build complete message Repeat Steps 6 to 14 to make other device templates Publication 1757 UM006A EN P May 2002 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 ips50 system bin er ffdevices ATTENTION Exit the Control Builder application before launching the Fieldbus Library Manager utility 1 Click Start gt Programs gt ProcessLogix Engineering Tools gt Fieldbus Library Manager The Fieldbus Library Manager FLM login window opens Server Name o Cancel 2 In the Server Name field select the Server where you want the device template stored The device template is stored in
153. d Tracking is enabled initiated OOS and track override manual is Disabled Failsafe is active in an output OOS function block LO lt gt i D LO rm m m E E m 7 EEE m If target mode has changed MAN MAN MAN MAN MAN from OOS to another mode since the block was last executed Resource state as reflected in OOS OOS OOS OOS OOS OOS the resource block parameter resource state is Standby Shed to the next lowest priority non remote mode which 1s permitted or optionally which is retained by the target mode attribute and for which the required inputs are available Publication 1757 UMO06A EN P May 2002 Appendix D Fieldbus Topologies Spur Topology Requires layout design Requires T connection Allows changing a device without disturbing other devices Daisy Chain Topology Requires layout design Requires terminators Difficult to replace one device without stopping entire Fieldbus Difficult to maintain Branch Topology Requires design evaluation Requires terminators Wiring savings are realized only in home run cable Conforms to present practices Fieldbus Wiring Considerations The following wiring information is for general purposes only Refer to each device s cooresponding wiring and installation instructions Figure D 1 illustrates the Spur Daisy Chain and Tree type wiring topologies that
154. d as a transition mode for exiting the OOS mode The SIMULATE parameter is for testing purposes only and always initializes in the disabled state Temp SP EU 0 EU 100 EU 0 PV_SCALE OUT Temp x EU 100 EU 0 EU 0 XD_SCALE Temp READBACK EU 0 EU 100 EU 0 XD_SCALE PV Temp x EU 100 EU 0 EU 0 PV_SCALE ALERT_KEY GRANT_DENY READBACK ST_REV BKCAL_OUT IO_OPTS SHED_OPT STATUS_OPTS BLOCK_ALM MODE_BLK SIMULATE STRATEGY BLOCK_ERR OUT SP TAG_DESC CAS_IN PV SP_HI_LIM UPDATE_EVT CHANNEL PV_SCALE SP_LO_LIM XD_SCALE FSAFE_TIME RCAS_IN SP_RATE_DN FSAFE_VAL RCAS_OUT SP_RATE_UP Publication 1757 UMO06A EN P May 2002 CAS_IN RCAS_IN IN 1 Bias Gain Block Figure 1 6 Functional Schematic for Bias Gain Function Block INi gt BKCAL_IN gt CAS IN gt RCAS IN gt TRK_IN_C gt TRK_VAL Setpoint SP_RATE_DN SP_RATE UP SP_HI_LIM SP_LO LIM ____ BKCAL_ OUT RCAS_OUT BG The Fieldbus Communication Model 1 13 P BKCAL_OUT gt OUT P RCAS OUT BKCAL_IN Mode SHED_OPT Bias amp Gain Output GAIN OUT _HI_LIM OUT LO LIM BAL TIME Output Track TRK_SCALE TRKIND TRK_VAL OUT Publication 1757 UMO06A EN P May 2002 1 14 The Fieldbus Communication Model Table 1 F Bi
155. d 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 When the CN2FF receives data it is stored in the CN2FF and is Produced on CN at the NUT rate Therefore in a typical CN2FF Fieldbus system the controller will be receiving a lot of redundant data In a PLX system with a FIM fieldbus interface the Fieldbus side operates at the Fieldbus data rate and the controller side operates at the backplane rate so again it is not a restriction on the performance of a fieldbus system Overview Chapter 2 Integrating Fieldbus into Rockwell Automation Logix System 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 Function Connection of Foundation Fieldbus devices to a Logix system Configuration of Foundation Fieldbus devices through Tools system Integration of Foundation Fieldbus Devices process maintenance and alarm data with notification and display functions in control systems Goal Integrate fieldbus devices on an H1 link with Supervisory level ControlNet or Ethernet network and or the 1 0 ControlNet network Integrate configuration of fieldbus devices through the NetLinx strategy Integrate data from fieldbus
156. d by GAIN and IN_1 When the upstream block sends Initialization Acknowledge IA status the block sends the IA status since its output will now be nearly identical to the value BKCAL_IN If this option is ON or to act a status of NI or IR at BKCAL_IN adjusts the SP to balance the output to the value of BKCAL_IN The IA status is sent as soon as IR is detected The BKCAL_OUT will not request initialization Use the Balance Ramp CONTROL_OPTS to maintain the ratio SP value when the block is in Manual Man mode An internal value follows the actual value required to maintain balance When block mode changes to Automatic Auto the internal value ramps to zero contribution in BAL_TIME seconds If Balance Ramp option is OFF or not used the ratio SP value immediately changes to follow the changes to the input or output when the block is in Man mode The TRK_VAL input brings in an external value or uses a constant The TRK_SCALE values convert the TRK_VAL to a percent of output span value If the CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true the converted TRK_VAL replaces the output OUT when the block is in Automatic Auto Cascade Cas or Remote Cascade RCas mode The CONTROL_OPTS Track in Manual selection must be true for this to occur in Manual mode If the actual mode is OOS or IMan the track request is ignored If the TRK_VAL replaces the OUT its status becomes Locked Out with Limits set to Constant The actual mode goes t
157. d location Configurating the 1757 FIM 4 25 The Name New Function Block s dialog box opens Name New Function Block s Source o Destination ST3000FF_080171 ST3000FF_080171 Change the name in the column on the right to the new Find Replace desired name or accept the default lt Back Cancel Help 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 example cascade example rmator example pid example scr FIM S10 lig LINK52 Sa pidloop gf ST3000FF_080171 r 3 3 Project ti Library 5 Repeat this method to add other devices Publication 1757 UMO06A EN P May 2002 4 26 _ Configurating the 1757 FIM Method 2 File Menu 1 Click File New gt FFDevices gt Rockwell Automation desired device name Fieldbus Device eis Control Builder Project File Edit view Insert Tools Operate Options Window Help 00 z aje Blap tjej Controllers Open Redundancy Module es eel IO Modules gt Interface Modules gt Login to Server m ST3000FF_0801 FieldBus Device Page Setup Control Module Print gt Sequential Control Module Export Wizard Import Exit The Block Parameters window opens 2 Leave the default Name or enter a desired name of
158. d to the Output Right box Output Aight Fay 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 REGCTL PID Block PIDA Parameters Project N SHA as x Configuration Parameters Monitoring Parameters Block Preferences Main Algorithm SetPoint Output Alams SCM Block Pins Name Execution Order in CM 20 Description Mode Engineering Units Normal Mode NONE Normal Mode amp ttribute N ONE X Process Variable PVEU Range Hi 100 Mode MAN BE R an 0 Mode Attribute OPERATOR z Manual PV Option SHEDHOLD z MV Permit Operator Mode Changes E Permit External Mode Switching Engr Access allows enabling J Enable Secondary Initialization Option Enable External Mode Switching Oper Access If Permit checked Safety Interlock Option SHEDHOLD Bad Control Option NO_SHED M Show Parameter Names Cancel Help 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 In the Normal Mode Attribute field select NORMAL Publication 1757 UM006A EN P May 2002 Configurating the 1757 FIM 4 45 7 Click the Algorithm tab REGCTL PID Block PIDA Parameters Project aa
159. d to the Process Variable parameter value Publication 1757 UMO06A EN P May 2002 Analog Input Block The Fieldbus Communication Model 1 9 Figure 1 4 Functional Schematic for Analog Input Function Block Transducer Al OUT 3 i i PV CHANNEL Simulate Convert Filter SIMULATE L TYPE PV_FTIME LOW CUT XD_SCALE OUT SCALE Output FIELD_ VAL Mode Alarms SHED OPT HI LO OUT Publication 1757 UM006A EN P May 2002 1 10 The Fieldbus Communication Model Table 1 D Analog Input Block Specifications Description The Al 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 e Supports Out of Service OOS Manual Man and Automatic Auto modes The XD_SCALE units code must match the channel units code or the block will remain in QOS mode after being configured The OUT_SCALE is normally the same as the transducer unless the L_TYPE is set to Indirect or Ind Sqr Root then the OUT_SCALE determines the conversion from FIELD_ VAL to the output If the mode is Auto the PV is the value the block puts in QUT If the mode is Man an operator can write a value to OUT The SIMULATE parameter is for testing purposes only and always initi
160. dation 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 It supports both the publish subscribe and the client server communication methods to communicate with fieldbus function blocks The control connections must be downstream only The FIM is a doublewide module that plugs into a non redundant Controller or remote I O chassis It connects up to two Fieldbus H1 links through a companion Remote Termination Panel RTP These independent links each have their own link schedule link master and time master functions The RTP is designed for DIN rail mounting within an enclosure It optionally accepts a 24 Vdc input from an external power supply to provide low level power to fieldbus devices on the H1 links The Fieldbus Interface Module functions as a dual network bridge using a dynamic data cache to facilitate the exchange of data between the ControlNet Ethernet network and the Fieldbus H1 links It supports both publish subscribe and client server communications methods to implement control connections between ProcessLogix function blocks and fieldbus function blocks FIM capability includes converting ProcessLogix value status structure to fieldbus value status by mapping similar fields to one another and defaulting others This means ProcessLogix can monitor fieldbus control f
161. dbus Status Display Indications Mode Change Conditions Table of Contents iX MDO BIOCKS ck gm aS ade wh ea he ae eer 7 16 Viewing Object Information in the NI FBUS CONO UO fala e e bbe A ae nee ee 7 16 Changing the Linking Device Configuration 7 17 Trends and Alarms 0 000000 eee ee eae 7 18 Tips for Connecting to a 1756 ENET Controller 7 19 Appendix A AXXX BIOCK Six te bok vo chk we See on ded ie Re eh Ae a ak A 1 Bxxx BIOCKS 4 6 04444 oad ba bo e ob BS ed be hee he A 2 CISC DIOS eaa oni rev wh So ees Hoe ws eek eA A 7 DEBIO se sscr we 8 te se oh de odes De ae gv eee gah Pe eee Beg A 10 Peon DIGG KS s 4 ack oan bed ce bok ee oe ee A 14 PIOSEBIGEKS co n esera ash Sadreceesk e Sa Baers ah Sede 6 bees A 14 GS DIOC ro an AS ae PO Oe ee eS A 19 Px BIOCKSS 4 t4 840044646408 6446584600444 0 882648 A 20 bce DIOC KS nu 3s baile DAS Ube E EER R RE RSA A 22 JRX BIO CK Gen hei neen EEEE Kone DS OHH wt ee es aves A 24 KOCK BIOCKS rouet Easy ed e e 8 dtd eh eee aa 2 A 24 ee BIOCKS 235 Ae 5 68 Goh ah So a oh eo ee eee A 24 ieaoo Gr i che ey eee abe o here aes ad Les A 27 Nemec BIOCKS are bain wows shee ood bas Coe E A 29 Oxxx BIOCKS 4 2444 64444654 65440400 04464445 466 54 A 29 Pee BIOCKS ia 4 2 ee td Bk Oe ea A 32 OBI OCS sg oh Poa ids ot tah Gt aed ah ae ae gt a A 33 ROCCHI OCIS ge saree ted aoe 6 os rh ee eee ed aoe Base ee A 34 SOO DIGG a k Bind bo ke ee ed oe a ee ee ee A 39 T BIOR e Sesto amp inte 4x
162. dition clears Float 0 to 50 percent of PV span C Contained 4 VIEW_4 Static Initial value is 0 5 percent Triste terenceuntonnaionts provided by FOUNDATION Fieldbus Want more Foundation Fieldbus information Visit the Fieldbus Foundation web site at www fieldbus org or the following address for more information 9390 Research Blvd Suite II 250 Austin TX 78759 9780 Publication 1757 UMO06A EN P May 2002 A 2 Standard Function Block Parameters Bxxx Blocks Publication 1757 UMO06A EN P May 2002 Table A 3 ALARM_SUM Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Detects the current alert status unacknowledged states and disable states of the alarms associated with the block DS 74 C Alarm Summary 8 VIEW_1 VIEW_3 Dynamic The data type summarizes 16 alerts using the following 4 elements e1 Current e Unacknowledged e3 Unreported e4 Disabled Table A 4 ALERT_KEY Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable The identification number of the plant unit This data may be used in the host for sorting alarms Unsigned 8 1 to 255 C Alert Key 1 VIEW_4 Static Initial value is 0 Table A 5 BAL_TIME Classification Description FF Data Type Range Usage Length simple Variable specifies the time in seconds for the internal working value of Bi
163. dules divided by three including local and remote chassis 0 and rail 0 Maximum number of 3 000 fieldbus devices Each H1 link is capable of supporting a practical limit at least 16 fieldbus devices This number may vary depending on the dynamics of the link Maximum number of H1 links independent LAS Fieldbus network references Please refer to the following publications for guidance in designing and implementing the fieldbus network to be interfaced to the ProcessLogix system through the FIM and its companion Remote Termination Panel RTP Table 3 C AG 140 Wiring and Overview of what you need Fieldbus Foundation Installation 31 25 kbit s to know to wire power and 9390 Research Blvd Voltage Mode Wire layout network components Suite Il 250 Medium Application Guide Austin Texas 78759 9780 www fieldbus org AG 165 Fieldbus Outlines things to consider Fieldbus Foundation Installation and Planning before installing a fieldbus 9390 Research Blvd Guide network Suite Il 250 Austin Texas 78759 9780 www fieldbus org Relcom Inc Provides fieldbus wiring Visit the Relcom Inc products wiring design and website installation data www relcominc com Offer a free Fieldbus Wiring Design and Installation Guide you can download Publication 1757 UMO06A EN P May 2002 3 4 1757 FIM Planning Considerations Installing 1757 FIM Fieldbus Interface Module Installing 1757 RTP Remote Termi
164. e Description Defines user selectable options for the block processing of status FF Data Type Bit String Usage C Contained Length 2 Valid Views VIEW_4 Storage Static Remarks see the following Table 3 for a list of the control options by bit and applicable function block Table A 122 STATUS OPTS Bit Selections Function Block Fonction Block at m ao 00 wt 6 es Po Pm ra oen Xe Pfs Peep xe pe z ferns Tf x x x x x x a reren e fT rwr xtxt x x ewen TT e x fe termine xT ff worms p TT EO o oorsee TXT TT E o orrae Tf x mfe TT TT T referee TT TP 1 TL Publication 1757 UMO06A EN P May 2002 A 46 Standard Function Block Parameters elem ee a a a ee ES i ee a Table A 123 STRATEGY 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 Txxx Blocks Table A 124 TAG_DESC Classification Simple Variable Description Serves as user defined description of the block FF Data Type Octet String Usage C Tag Description Length 32 Storage Static Remarks Initial value is 32 space characters Table A 125 TEST_RW Classification Record Description Defines read write test parameter FF Data Type DS 85 Usage C Test Publication 1757 UM006A EN P May 2002 Length Storage Remark
165. e A 74 MANUFAC_ID Classification Simple Variable Description Defines the manufacturer s identification number This number is used by an interface device to locate the DD file for the resource FF Data Type Unsigned 32 Range Set by manufacturer Usage C Contained Length 4 Valid Views VIEW_4 Storage Static Remarks Read Only Table A 75 MAX_NOTIFY Classification Description FF Data Type Range Usage Length simple Variable Defines the maximum number of unconfirmed notify messages possible Unsigned 8 set by manufacturer C Contained 1 Publication 1757 UMOQ06A EN P May 2002 A 28 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Valid Views Storage Remarks VIEW_4 Static Read Only Table A 76 MEMORY_SIZE Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Represents the available configuration memory in the empty resource Unsigned 16 set by manufacturer C Contained 2 VIEW_4 Static Read Only Table A 77 MIN_CYCLE_T Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the time duration of the shortest cycle interval that the resource can Support Unsigned 32 set by manufacturer C Contained 4 VIEW _4 Static Read Only Table A 78 MODE_BLK Classification Description FF Data Type Usage Length Record
166. e Guide 1757 INO40B EN P ProcessLogix R400 0 Selection Guide 1757 SG001B EN P 1757 FIM Installation Instructions 1757 IN913A EN P 1757 RPT Installation Instructions 1757 IN915A EN P 1788 CN2FF Installation Instructions 1757 IN051B EN P NI FBUS Configurator User Manual 1788 6 5 2 1757 PLX52 ProcessLogix Controller Module 1757 IN901C EN P Installation Instructions Other Manuals Available ProcessLogix Theory Manual 1757 RM805A EN P ProcessLogix Function Block Reference 1757 RM810A EN P ProcessLogix Error Codes and Troubleshooting 1757 TGO01A EN P ProcessLogix Function Block Parameters 1757 RM811A EN P If this is a new ProcessLogix system installation we recommend that you familiarize yourself with the contents of these publications before you install any ProcessLogix system equipment Visit us at http www theautomationbookstore com or contact your local sales office to obtain these manuals Publication 1757 UMO06A EN P May 2002 3 2 1757 FIM Planning Considerations ATTENTION Installation declaration 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 Without appropriate precautions there may be potential difficulties ensuring el
167. e HMI Server Foundation Fieldbus Devices You can configure display monitor modify Foundation Fieldbus device parameters remotely Use RSLinx to create a TCP xx path from the computer that is running the 1788 FFCT The path lists the Ethernet IP address of the remote 17560 ENET ethernet interface Be sure that you have the correct IP address Use an Internet Browser and rather than typing htpp www address type the IP address ex 130 151 133 48 of the 1756 ENET If you have the correct address you can look at the devices in the remote ControlLogix backplane Refer to Remote Configuration of a Fieldbus Network via the 1788 CN2FF on page F 49 for more information Publication 1757 UMO06A EN P May 2002 7 20 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Notes Publication 1757 UMO06A EN P May 2002 Appendix A Standard Function Block Parameters 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 2 ALARM_HYS Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the amount of change a PV value must attain within the alarm limits before the alarm con
168. e data type to DINT We are using DINT for the first member since we know that the linking device sends 2 INT words of pad which equals 1 DINT We could have set the data type to INT and then set the size to A 8 On the second line type a name of Pressure 9 Set the data type to REAL REAL floating point Publication 1757 UM006A EN P May 2002 F 46 1788 CN2FF Installation Example Testing the Installation Example Publication 1757 UMO06A EN P May 2002 10 11 12 13 14 15 16 Iz 18 Click Apply At this point we have the first two parts of the structure defined Enter the remaining members as shown below 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 Open the controller tags database and select the Edit tab on the bottom of the window Enter a tag name of LD_Node_9 Tab over to the Data Type field Click the button with the 3 dots to bring up the choices for data type The FF_Linking_Device is one of the data types listed Set the data type to FF_Linking_Device and click OK Press Enter to accept the new tag Open MainRoutine and enter the following rung This rung will copy the contents of the input data in the linking device tags to the tag LD_Node_9 The length is set to 1 since we are only copying to one element of LD_Node_9 The copy instructio
169. e in deference to minimum device cost and maximize reliance on a centralized control architecture Measurement instruments in such structures communicate to a central computing system at the request of that central system A proprietary control application running on the central system processes the field data and distributes control signals to other devices back in the field Regardless of how open the communication scheme may be the control application is always proprietary The key distinctions between these technologies and FOUNDATION fieldbus are FOUNDATION fieldbus provides an open specification for both communications and the control application FOUNDATION fieldbus distributes control functionality across the bus making maximum use of local intelligence to improve performance and reduce total system cost Devices are required to be interoperable providing the user with tools to implement a control system with products from multiple manufacturers without custom programming With FOUNDATION fieldbus the network is the control system 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 Ope
170. e the window and save the configuration Publication 1757 UM006A EN P May 2002 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 DATAACO 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 Be sure to add vertices where required by clicking in the desired path to the final pin See Figure 4 3 for the completed CM101 with all blocks wired Figure 4 3 Completed CM101 for sample loop fiz CM101 Project HON EvWELL 3ST 000F F_O501 4 Al LEVEL DEVICE 5T1 1 REGCTL FID OUT AALUE PID_ 101 7 SP HORMMODE AUTO HORMMODEATTR NORMAL CTLEOQN EUA DATAACG DATAACO DATAACQ 101 PYSROCOPT OHLYAUTO PIFILT TIME CAS IN WLU F LONSER w E Lx 1400F F_N PYEULO T D 40 FLOVY PWEUHI 100 T DEVICE L lt 14_104 PYLLALIN FL OUTMALUE OFF o PWLOALM FL OFF ip Publication 1757 UM006A EN P May 2002 4 48 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 wil
171. e through appropriate Link block and device block configuration forms in Control Builder TIP The FIM must be configured and loaded through D Control Builder before you can view the module You can view the module s links and devices through the Monitoring tab of Control Builder Publication 1757 UMO06A EN P May 2002 2 30 Integrating Fieldbus into Rockwell Automation Logix System Foundation Fieldbus Foundation Fieldbus FF is a very powerful network providing both communication and distributed control capability However fast Performance 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 Therefore in the application reflected in this schedule you should plan on a loop closure time of on the order of 1 second if you want new data from all devices each time you run the loop calculation 45 Function Block Application Jus C Loop Time 1 sec optimized 8ge a a05 200 300 400 500 600 700 800 300 349 Left T AI 1 AT OUT 3d Left T AI 2 AI P OUT a Left T AI 3 AT af Left T AI 4 AT Temp Al AI Temp A2 AI Temp A3 ATL Temp A4 AT 3g Left T DI 1 DT aq Left T DI 2 DI gt OUT _D 3g Left T DI 3 DI gt OUT _D ad Left PID PID gt OUT gt BKCAL OUT 34d Left T PID 1 PID gt OUT P BKCAL OUT gq CNetMacId05_AO_Moduleo_o cna P
172. e writes the value to the AO block when this attribute is changed by the controller 151 TagDesc String Get As Tag of the Fieldbus function block that configured this object instance represents 152 Failstatelime Float Set The linking device writes the value to the AO block when this attribute is changed by the controller 153 ReadBack Float Get This represents the BKCAL_OUT value from the AO block 154 BkCalStatus uint8 Get Bad Not This represents the status of the Connected Readback attribute 155 casInstatus uint8 Set Bad Not This represents the status of the connected CAS_IN to the AO block Publication 1757 UM006A EN P May 2002 The BkCalStatus is created only when the controller is capable of participating in the CAScade initialization handshake and when the BKCAL_OUT of the AO block is wired to a BKCAL_INx parameter of the MAO block Only Value CNStatus casInstatus ReadBack and TagDesc are created when an MAO is connected to something other than an AO function block CAS_IN parameter Discrete Inputs Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device 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 equiv
173. ectromagnetic compatibility in other environments due to conducted as well as radiated disturbance This equipment is supplied as open type equipment It must be mounted within an enclosure that is suitably designed for those specific environmental conditions that will be present and appropriately designed to prevent personal injury resulting from accessibility to live parts The interior of the enclosure must be accessible only by the use of a tool Subsequent sections of this publication may contain additional information regarding specific enclosure type ratings that are required to comply with certain product safety certifications See NEMA Standards publication 250 and IEC publication 60529 as applicable for explanations of the degrees of protection provided by different types of enclosure Also see the appropriate sections in this publication as well as the Allen Bradley publication 1770 4 1 Industrial Automation Wiring and Grounding Guidelines for additional installation requirements pertaining to this equipment Publication 1757 UMO06A EN P May 2002 1757 FIM Planning Considerations 3 3 FIM and 1 0 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 Total Per Controller Total Per Server Maximum number of FIMs 100 plus I O mo
174. eir FSAFE action Unsigned 8 1 Clear 2 Active C Contained 1 Standard Function Block Parameters A 15 Valid Views VIEW_1 VIEW_3 Storage Non Volatile Remarks Read Only 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 41 FEATURE_SEL Classification Description FF Data Type Usage Length Valid Views Storage simple Variable Bit string that identifies the selected resource block options Bit String C Contained 2 VIEW_2 Static Table A 42 FF_GAIN Classification Description FF Data Type Usage Length Valid Views Storage simple Variable Defines the gain value used to multiply the feed forward signal before it is added to the calculated control output Float C Contained 4 VIEW_4 Static Publication 1757 UMO06A EN P May 2002 A 16 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Table A 43 FF_SCALE Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks Record Defines the feed forward input high and low scale values engineering units code and number of digits to the right of the decimal DS 68 0 100 percent C Scaling 11 VIEW_4 Static The Data type consists of data that
175. el Open az read only A DD file consists of two or three files with the extensions ffo and sym The main DD file has an extension ffo When you select the ffo file the software automatically installs the other files Publication 1757 UMO06A EN P May 2002 F 16 1788 CN2FF Installation Example 5 Select the file with the extension ffo and click Open You see Import DD Enter the fto File Marne C ALinking Device SupportkD i a Cancel Import D Dialog will create subdirectories under the base directory of Device Description based on your manufacturer ID and Device Type and then copy fo and sym file there 6 Click OK to import the DD You will receive a message telling you the copy succeeded 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 D gt 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 IMPORTANT You must have a DD for every device or you will not be able to configure that device 8 When you have copied all the DDs click OK again to close the DD Info window 9 Click OK to close the Interface Config utility If you have just installed the 1788 FFCT software you will be asked if you want to restart your gt computer now Publication 1757 UM006A EN P May 2002 1788 CN2FF Installation Exam
176. em 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 Once the MIB VCR is configured and opened FIM retrieves MIB information SMdirectory and NM directory Knowledge of these directories allows FIM to transform writes into domain object variables into proper sequence of domain download operations The SM directory is also used to determine the number of application VFDs The NM directory is key in attempting to configure VCRs to access Function Block Application Process VFDs in the device About the VFD Object The Virtual Field Device object represents an application VFD and provides parameter access to that VFD Each physical device may have one or more application VFDs The FIM attempts to build a client server VCR to every VFD in the device when it is added to the network If the VCR configuration is successful the FIM obtains VFD and resource identification from the device s VFD During device download you can overwrite VCR configuration used to access VFD parameters through the Control Builder application Fieldbus Device Analog Input Integration A user can functionally wire the output from an Analog Input AD function block in a fieldbus device residing on an H1 link to the input of a regulatory control type function block contained in a C
177. en you are facing the CN2FF Cycle power on the CN2FF after you set the Mac ID Install the 1788 FFCT 1 Install the 1788 FFCT Foundation Fieldbus Configuration Tool Software software TIP We suggest that you copy the FFCT files to your hard drive and install from there Install the software in p the default directory This example is based on these default locations IMPORTANT If you have other National Instruments Fieldbus Monitor Software installed on your PC the system may try to install this 1788 FFCT software in a directory called Monitor Don t allow the software to install in that directory make sure it installs in the NIFBUS directory 2 Open Disk 1 3 Click on the Setup with the monitor icon 4 Accept the defaults during the installation Publication 1757 UMO06A EN P May 2002 1788 CN2FF Installation Example F 7 When installation is complete you see HI FBEUS Interface Configuration Utility La NI FBUS DD Into Add Interlace Device Edit The changes made in FECONF only takes effect after you start NI FBUS process the next time 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 Publication 1757 UMO06A EN P May 2002 F 8 1788 CN2FF Installation Example You see IntertaceT ype
178. ents 0 4 Bytes Object ID 1 Destination ValueFromCN 2FF Object Attribute 3 Hes Create Tag 2 Enable lt 2 Enable Waiting 2 Stark 2 Done Done Length 2 w Error Code 16 0001 T Timed Out Bonet Failure Extended Error Code 16 0204 Cancel Spp Help For a PLC 5 to retrieve data setup the message as shown in Figure F 7 Publication 1757 UMO06A EN P May 2002 F 48 1788 CN2FF Installation Example Figure F 7 PLC 5 Message Setup z R Logix 5 Fimessag_rsp CIO CT10 0 File Edt View Search Comme Tools Window Help ey ea es one He OR NoEdits Forces Disabled 4 i Driver AB ETL 1 Node 2 A e EAE eae ja H TE 3E IE lt gt a gt a gt os h alh User Bt A TimerfCounter A InputfOutput A Compare Command Control Bits Communication Command Paste lgnore if timed out TO la Awaiting Execution EM a Continuous Run CO la Error ER la Serice Code Hex Class Humber Hex Instance Number Hex Attribute Humber Hes Done DN Transmitting 5T a Enabled EM This PLC 5 le la i PLC 5 Data Table Address Size in Elements Fort Number Error Error Code Hes p Target Device Local Control et Node 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
179. er 6 Use the two pull down menu s to select the Linking Device for both Check only the Linking Device to receive the LAS schedule In this example you would remove the check by the Honeywell Publication 1757 UMO06A EN P May 2002 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 All the devices that have an LM overlaid on the icon to the left of the name of the FF Devices have the ability to be the LAS on that network 8 Click Link Settings Advanced The information on this screen relates to the timing of the network You should be aware that if these parameters are set too low they could cause communications problems on the network The default settings are those currently suggested by the Fieldbus Foundation To see if some of the attached devices are requesting more time a Click Press To See Suggested Values b Click Apply Suggested Values c Click Write Changes if there are any Publication 1757 UMO06A EN P May 2002 F 24 1788 CN2FF Installation Example The best thing to do is use the values
180. er When setting as the target mode set the Auto bit and reset all the other bits Reject the request if the current mode is OOS and the access level is not ENGR or higher When setting as the target mode set both Cas and Auto bits and reset all the other bits Reject the request if the current target mode is OOS and the access level is not ENGR or higher When setting as the target mode set both RCas and Auto bits and reset all the other bits Reject the request if the current target mode is OOS and the access level is not ENGR or higher When setting as the target mode set both ROut and Auto bits and reset all the other bits Reject the request if the current target mode is OOS and the access level is not ENGR or higher When setting as the target mode read the MODE NORMAL value and write to the MODE TARGET Reject the request if the current target mode is OOS and the access level is not ENGR or higher 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 Descipion Joam Satisfied in mode a actual same OOS MAN AUTO CAS RCAS as target ROUT a t In mode a not satisfied in higher MAN A CAS RC IM A LO target mode t CAS AUTO M CAS M The block
181. ert Objects and View Objects They provide linking between internal Function block inputs and outputs trending of Function block parameters reporting of alarms and events viewing of predefined block parameter sets through one of four defined views The four defined views are View 1 Operation Dynamic View 2 Operation Static View 3 All Dynamic and View 4 Other Static Figure 1 2 Function Block Application Process based on blocks i i User Application Fieldbus Foundation Defined Blocks ee Resource Block Transducer Function Block Block Communication Stack Physical Layer Fieldbus Publication 1757 UMO06A EN P May 2002 1 6 The Fieldbus Communication Model Standard Function Blocks Publication 1757 UMO06A EN P May 2002 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 Foundation Function Blocks are similar in nature to the Function Blocks used to build control strategies in the Control Builder application in the ProcessLogix system The Fieldbus
182. es and access rules shown in Table 7 C Table 7 C ControlNet Discrete Input Object Attributes Attribute Number Type Initial Value Remarks 7 one en oe 0 150 Ffstatus uint8 Get Bad Out of Fieldbus status of the value obtained Service from the Fieldbus device 151 TagDesc String Get As configured Tag of the Fieldbus function block that is represented by this object instance 156 DiscAlmFlag uint8 Get Set O 000 see Alarm Handling for Discrete Inputs Publication 1757 UMO06A EN P May 2002 All attributes in Table 7 C are created if a standard Fieldbus DI function block is connected to a channel on an MDI block Otherwise DiscAlmFlag is not created Alarm Handling for Discrete Inputs You can configure Fieldbus DI function blocks to detect and report alarms The process alarm DISC_ALM are exposed through the ControlNet DI object When you connect a DI function block to an MDI block the NI FBUS Configurator configures the field device to send the alarm to the linking device In Fieldbus terminology confirming an alarm means that the alarm has been received by an operator and acknowledging an alarm means that the operator has taken the necessary action When an alarm condition is detected by a Fieldbus function block the alarm is said to be ACTIVE An active alarm should be Acknowledged and Confirmed after the condition causing the alarm is corrected When the function block detects the alarm condition is no longer
183. es as shown e Clear Devices e 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 Click OK and click on Close in the Download window HI FBUS Fieldbus Configuration System Ci Configuration of link LO 9board 0portl has completed successfully If the download does not complete try it again Some FF devices need to be told many times what they should do If the Publication 1757 UMO06A EN P May 2002 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 Loop Time 1 sec Stale Limit 1 I ty C Syl Al as Sal When you run the monitor you get a display of the values being read from the attached transmitters gt Honitor Function Blo ii MW Monitor Block Outputs Monitor Block Inputs IY Monitor only wired parameters Show Substatus Start Monitoring The Monitor window will appear as shown here If you have only 3 or 4 function blocks attached to the CN2FF set the monitor rate to 5 seconds If you have 20 or so
184. es were exactly the same this message would not be necessary but since a man with 2 watches never knows what time it is the time must be re synchronized The clock synchronization method facilitates synchronization of clocks which run at different speeds very well It does not do so well for clocks that speed up and slow down i e consistently slow clocks work ok but sporadically slow clocks are difficult So the question is how long does it take until the clocks drift far enough apart for anyone to care If it is set to 1 ms then you waste all your fieldbus messages updating the clock and never get anything done If it is set to say 5 hours then a clock can drift a long way from the LAS s clock causing Stale Data because the function block did not execute prior to the node being Compelled to Publish its data there are other causes of Stale Data also 5 seconds is a comprimise reigning in deviant clocks before they get too far out of hand yet not wasting much network bandwidth You might increase it if you are in a real pinch for network speed but there won t be a measurable improvement by removing 1 ms of traffic out of 5 seconds or 1 5000 You can decrease it if you think that the clocks are drifting apart prior to 5 seconds but most of the cause of clock drift is because of the jitter in delivery of time sync messages theory don t repeat it so if anything spreading the transmission error out over a longer time
185. escriptions of some standard fieldbus function blocks and describes the role of Device Descriptions and block parameters for general reference Chapter 2 Integrating Fieldbus into gain some insight on what functional relationships result from the integration of fieldbus ProcessLogix R400 0 devices with a ProcessLogix system The information in this section will be helpful background for planning and configuring your control strategy Chapter 3 Planning Considerations be responsible for setting up the hardware infrastructure to support fieldbus devices This section identifies the things you should consider before installing any equipment and provides detailed procedures for how to install the Fieldbus Interface Module FIM and its companion Remote Termination Panel RTP Chapter 4 Configuration be the one configuring the control strategy through Control Builder This section provides detailed procedures for including fieldbus functional components in your overall control Strategy It includes creating hardware blocks making templates associating blocks assigning modules assigning devices and loading components Chapter 5 Operation be monitoring system operation This section provides an overview of functions you can monitor through Station displays and the Monitoring tab in Control Builder Chapter 6 General Maintenance be responsible for maintaining and trouble shooting system operation This section provides Checkout and Calibration in
186. etermine each device s input capacitance e Assume all devices are at the extreme end of the trunk e Use 0 035 dB nf as signal attenuation calculation EXAMPLE For example if the fieldbus topology includes five devices each with a 3000 pF input capacitance the equivalent capacitance is 15 nf 5 x 300 pF and the resulting attenuation is 0 525 dB 15 nF x 0 035 dB nF Fieldbus Wiring Considerations D 7 Calculating Attenuation Testing the Cable Repeaters Take the sum of the following calculations to determine if the attenuation will exceed the allowed level of 14 dB e Calculate the cable attenuation e Calculate the attenuation due to spurs e 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 525 device capacitance attenuation 2 13 dB Use a fieldbus tester and signal generator to determine if existing cable is suitable for fieldbus use or not The tester and signal generator work together to determine the resistance of the wires and measure the signal quality of the transmission This testing also determines if the wiring polarity is consistent Repeaters can be used in a Fielbus cable system There can be a maximum of four repeaters between any two nodes on a Fieldbus If repeaters are used there must
187. fF SA C PCMCIA Check CONTROLNET C CONTROLNET Base Address OD 0000 IRG of Ports Polled Mode 2 For Interface Type check CONTROLNET When you select ControlNet the dialog box changes to reflect the default ControlNet parameters Intert ATENON The driver name must be entered EXACTLY case punctuation underscores as it is listed IntertaceT ype C 5A Add in RSLinx refer to Finding the Interface Driver Name on page F 9 for an example C PCMCIA Cancel f CONTROLNET Enter the ControlNet driver name peasy AB KT C Enter the ControlNet MAC ID of the CN2FF Network Address fs Enter 1 or 2 depending on the number of Foundation Fieldbus channels attached to the 1788 CN2FF H of Ports This is the default path from the PC to the 1788 CNZ2FF Use this path Fath with the PC on the same ControlNet as the 1788 CN2FF Timeout ma eooo 3 Enter the Driver name for you ControlNet interface AB_PCIC 1 AB_KTC 1 or AB_PCC If you do not know the name of your driver follow the procedure in Finding the Interface Driver Name on page F 9 Publication 1757 UM006A EN P May 2002 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
188. fication Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Used to disallow writes from anywhere except to unlock clear this parameter when it is locked set Inputs will continue to read Unsigned 8 1 Unlocked 2 Locked C Contained 1 VIEW_2 Static The operator can control PROGRAM and LOCAL access to this value Table A 132 WRITE_PRI Classification Description FF Data Type Range Usage simple Variable Defines the priority of the alarm generated by clearing the WRITE_LOCK Unsigned 8 0 to 63 C Alert Priority Publication 1757 UMO06A EN P May 2002 A 50 Standard Function Block Parameters Length 1 Valid Views VIEW_4 Storage Static Xxxx Blocks 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 FF Data Type DS 68 Usage C Scaling Length 11 Valid Views VIEW_2 Storage Static Remarks The Data type consists of data that describes floating point values for display purposes It uses the following four elements e1 Engineering Units at 100 percent e Engineering Units at 0 percent e3 Units Index e4 Decimal Point Table A 134 XD_STATE Classification Simple Variable Description Represents index to the text describing the states of a discrete for the
189. figured 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 Once you establish communications with a fieldbus H1 link you can begin monitoring the status of any component that has been loaded as part of a Control Strategy to a FIM with points registered in the ProcessLogix Server The Detail displays let you quickly view the component s current state fault status and pertinent configuration data Figure 5 1 shows a sample FIM Detail display The fieldbus Detail displays feature links to related fieldbus component displays Figure 5 1 Typical FIM Detail display in Station Provides view to Provides convenient links configuration data and to related fieldbus displays real time data updates Fieldbus Interface Module Detail Main 16 Feb 01 11 58 35 Statistics Server Parameters Current Time 97933461 10100 Reset statistics CPU Free average EZ CPU Free Minimum 36 0346 WYS usage 1 47606 k Enable stack diacnostics LINKO501 LINKO502 aft localhost Stn Oper ml See the Operator s Guide in Knowledge Builder for detailed information about calling up navigating and viewing Station displays Publication 1757 UMO06A EN P May 2002 5 2 Operating the 1757 FIM gt Station default s
190. formation about replacing components upgrading firmware in uncommissioned devices and checking device calibration Chapter 7 Using the use the 1788 CN2FF H1 Linking Device Contro Net to FOUNDATION Fieldbus H1 Linking Device Appendix F follow a hands on example explaining how to configure and monitor a field bus device using the 1788 CN2FF Publication 1757 UMO06A EN P May 2002 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 Click Click left mouse button once Assumes cursor is positioned on Click the Browse button object or selection Double click Click left mouse button twice in quick succession Assumes Double click the Station icon cursor is positioned on object or selection Drag Press and hold left mouse button while dragging cursor to new Drag the PID function block onto the screen location and then release the button Assumes cursor is Control Drawing positioned on object or selection to be moved Right click Click right mouse button once Assumes cursor is positioned on Right click the AND function block object or selection lt F1 gt Keys to be pressed are shown in angle brackets Press lt F1 gt to view the online Help File gt New shows menu selection as menu name followed by menu Click File gt New to start new drawing selection gt D setup exe l
191. g 11 UPDATE Link associated with function block 12 UPDATE Trend associated with block Message type will be enumerated in the following manner 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 The alert object will be invoked by the alert notification task If multiple alarms or event parameters are unreported then the one with the highest priority or is the oldest of equal priority will be selected by the alert notification task The selected alert object is sent in a message at the first opportunity less than the alert confirm time If a confirmation from an interface device is not received by the alarm notification routine in the field device within a time determined by the resource block confirm time parameter then the alert will be considered unreported so it may be considered for selection Publication 1757 UMO06A EN P May 2002 2 38 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 Reference Publications Chapter 3 1757 FIM Planning Considerations 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 Upgrad
192. g Red X FE Having a firmware load error X CE Having a communications Initialization error X DE Having a database initialization error Flashing Green or Off X CI Initializing communications with fieldbus devices X Dl Initializing database X YY Communicating with fieldbus devices Display alternates between Link 1 and Link 2 in two second intervals The X is either 1 or 2 for the respective Link and YY equals the number of fieldbus devices present on a given Link Checking Fieldbus Device Please refer to the manufacturer s documentation for the fieldbus Calibration device to determine the recommended calibration schedules and procedures The Other tab on the Parameters form for a device s transducer block provides pertinent calibration information when accessed through the Monitoring tab in Control Builder Publication 1757 UMO06A EN P May 2002 Blocks in the Linking Device Chapter Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device This chapter describes e the blocks in the linking device e configuring the linking device to access the AI AO DI DO function blocks on the Fieldbus network from ControlNet e attributes of the created ControlNet objects assembly objects alarm handling e ControlNet connection details The linking device is similar to an I O subsystem An I O subsystem typically contains several I O modules Each module has a number of channels The channels
193. gt PY Limits Hi 102 9 PY Limits Lo 29 PY Character NONE F Low Signal Cut Off NaN Clamping Filtering PY Format D1 v Clamping Option DISABLE C ENABLE Lag Time 0 minutes Show Parameter Names Cancel Help 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 Leave the Execution Order in CM field at the default of 20 Publication 1757 UMO06A EN P May 2002 4 42 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 6 Click the Alarms tab Main Alarms Block Pins Configuration Parameters Monitoring Parameters Block Preferences Deadband Value 1 m Alarm Limits Trip Point Priority Severity P High High NaN i P High NaN PY Low NaN PY Low Low NaN Positive Rate of Change NaN Negative Rate of Change NaN Bad PY High Significant Change NaN Low Significant Change NaN Deadband Filter Time fo Deadband Units PERCENT JEU 7 Enter or select the following values for these Alarm Limits Alarm Limit Leave all other Alarm Limits at their default values 8 Click the Block Pins tab DATAACQ DATAACQ Block DATAACQA Parameters Project Main Alarms Block Pins Configuration Parameters Monitoring Parameters Block Preferences Parameters BADPYALM FL BADPYALM PR BADP
194. hat are not selected Control signals that are not selected are limited in one direction only as determined by the SEL_TYPE selection The value of each BKCAL_SEL_1 2 3 output is the same as OUT The limits of back calculation outputs corresponding to not selected inputs will be high for a low selection low for a high selection or one of each for a middle selection If the status of an input is Bad it is not eligible for selection If the status of an input is Uncertain it is treated as Bad unless the STATUS_OPTS selection is Use Uncertain as Good When all inputs are Bad the actual mode goes to Manual This condition will set Initiate Failsafe IFS in the output status if the STATUS_OPTS setting is IFS if BAD IN If SEL_TYPE selection is Middle and only two inputs are good the higher input will be selected If the status of BKCAL_IN is Not Invited NI or Initialization Request IR it is passed back on all three back calculation outputs This causes all initializable inputs to initialize to the BKCAL_IN value Otherwise if the status of BKCAL_IN is not normal it is passed back on the BKCAL_SEL_N where N is the number of the selected input The back calculation outputs for not selected inputs just have the Not Selected status with the appropriate high or low limit set When the mode is Manual no input is selected All three back calculation outputs will have a Not Invited status and Constant limits with a value equal to OUT ALERT_KEY
195. hat describes floating point alarms It uses the following five elements e Unacknowledged e Alarm State e Time Stamp e Subcode e Value Table A 70 LO_LO_LIM Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the setting for the low low alarm in engineering units Float Infinity PV_SCALE C Contained 4 VIEW_4 Static Initial value is Infinity Table A 71 LO_LO_PRI Classification Description FF Data Type Range Usage Length Valid Views Storage simple Variable Represents the priority of the low low alarm Unsigned 8 0 to 63 C Alert Priority 1 VIEW_4 Static Table A 72 LO_PRI Classification Description FF Data Type Range Usage simple Variable Represents the priority of the low alarm Unsigned 8 0 to 63 C Alert Priority Standard Function Block Parameters A 27 Length Valid Views Storage 1 VIEW _4 Static Table A 73 LOW_CUT 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 I10_OPTS If the calcu lated PV falls below this limit the PV value is set to zero 0 FF Data Type Float Range Positive Usage C Contained Length 4 Valid Views VIEW _4 Storage Static Remarks This function may be used to eliminate noise near zero from a flow sensor Mxxx Blocks Tabl
196. he parameters in the module properties window as shown in Figure F 5 Publication 1757 UMO06A EN P May 2002 F 42 1788 CN2FF Installation Example Figure F5 ControlNet Module Properties Module Properties cnet CONTROLNET MODULE 1 1 Type LONTAOLNET MODULE Generic Controldet Module Vendor Allen Bradley Connection Parameters Assembly l Instance aize 302 B2bi Name CN AFF Descriptions Comm Format Data DINT Node fs Input Output 32 bit Configuration 3 0 28 bit Aala Status Input A Status Output Cancel Back Hest gt Finish gt gt Help 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 Therefore you want an input area x times 8 where x is something greater than the number of Analog inputs that you expect may be connected to the CN2FF When you look at the data transmission that the CLX receives from the CN2FF you ll see that there is nothing in the first 4 bytes That is because there is four bytes of pad in front of the first data Output Size The output size is set to 1 since a generic connection requires at least one word of output We are not using any outputs in this lab
197. ication Model 1 5 Table 1 A Communication Layer Descriptions Layer Functional Description Associated Terms User Defines blocks to represent different types of application functions The three types of Resource block Application or blocks are the Resource block the Function block and the Transducer block See Function block Function Block Figure 1 2 Transducer block Application The Resource block is used to describe characteristics of the fieldbus device such as the Link Objects Process FBAP device name manufacturer and serial number Each fieldbus device requires one Trend Objects Resource block Alert Objects The Function block is used to define the specific characteristics of the process control View Objects function The Fieldbus Foundation provides a set of pre defined function blocks A single View 1 Operation Dynamic fieldbus device can include many Function blocks to achieve the desired control View 2 Operation Static functionality See the following section Standard Function Blocks for more information View 3 All Dynamic The Transducer block is used to Interface Function blocks with local input output View 4 Other Static devices They read sensors and command outputs and contain information such as calibration date and sensor type One Transducer block is usually included for each input or output Function block These associated objects are also defined in the User Application Link Objects Trend Objects Al
198. ice digital input signal with ProcessLogix CONMOISIFAICOY wea we Rie bo eed Ae oS 2 14 Integration of fieldbus device digital output signal with PLrOCeSsLOGix COMPO SHALES e ee oh ea eee a ers 2 15 Block mode calculation summary 00005 2 23 Algorithm execution phase sequence 00 2 27 Summary of address allocations for fieldbus devices 2 28 Example Rockwell Fieldbus Configuration 4 2 Sample Application and Control Strategy Integrating Fieldbus Devices with a ProcessLogix System as the Supervisory Control 5 25 a 8 cds Yah od Ss 4 4 Completed CM101 for sample loop 4 47 Sample CM with Device Control block for pump control if sample lOO Dhue 25 5 8 eis endow Bon oe Ae Aas Be ed 4 48 Completed CM102 with parameter connections for sample OOP interlocks esetere ceed Taaa ou bE nea a GS 4 50 Overview of load operations used to initiate COMmMpPOnents ONIN 4 4 400 s ae ee owe Ge eae eho a 4 5 Descriptions of the FIM Dialog Box Features 4 52 Typical FIM Detail display in Station 5 1 Publication 1757 UMO06A EN P May 2002 List of Figures ii Publication 1757 UM006A EN P May 2002 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 Att
199. ieldbus org Table F 1 Topics Covered in the Installation Example Topics Page Required Hardware for Installation Example F 2 Required Software F 3 Example Description F 3 Connecting the Hardware F 5 Install the 1788 FFCT Software F 6 Assigning a Path to the 1788 CN2FF F 10 Installing Device Descriptions DDs F 14 Starting NIFB F 17 Troubleshooting the Port Configuration F 18 Moditying Device and Function Block Names F 24 Configuring the Fieldbus Device F 29 sending Data To the PLC 5 CLX PLX or SLC F 36 PLC 5 and ControlLogix Applications F 40 ControlLogix Application F 41 Testing the Installation Example F 46 Remote Configuration of a Fieldbus Network via the 1788 CN2FF F 49 Troubleshooting an Application F 51 Publication 1757 UM006A EN P May 2002 F 2 1788 CN2FF Installation Example Required Hardware for Installation Example Publication 1757 UMO06A EN P May 2002 LJ One 1788 CN2FF ControlNet to Fieldbus Linking Device L 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 _J FF convenience Relcom Connector Blocks Connector block should include built in power conditioner and two Fieldbus terminators LI One Personal Computer 233 MHz or faster 128 Meg Memory _J With Windows NT Service Pack 3 or later You must use Windows NT 2000
200. ignal quality This is based on published Fieldbus Foundation wiring guidelines Publication 1757 UMO06A EN P May 2002 D 4 Fieldbus Wiring Considerations Publication 1757 UMO06A EN P May 2002 The following table lists limits for some possible fieldbus cable types listed in the order of usage preference with 1 being preferred Table D 2 Fieldbus Cable Limits Preference Description Distance Resistance Attenuation Type Meters Feet Ohms per km dB per km 1 18 AWG shielded 1900 6233 22 3 twisted pair 2 22 AWG 1200 3937 56 D multiple twisted pairs with overall shield 3 26 AWG 400 1312 132 8 multiple twisted pairs without shield 4 16 AWG multiple 200 656 20 8 conductor no twisted pairs with overall shield Another rule of thumb based on Fieldbus Foundation published guidelines is for the length of spurs and how many devices can be on various lengths of cable as listed in the following table Table D 3 Number of devices on the fieldbus and maximum spur length Number of Devices Maximum Spur Length Meter Feet 1 to 12 120 394 one device per Spur 13 to 14 90 295 one device per Spur 15 to 18 60 197 one device per Spur 19 to 24 30 98 one device per Spur 25 to 32 No spurs allowed ATTENTION ATTENTION The spur length limitations are for spurs with one device each Please refer to the Fieldbus Foundation AG 140 Wiring and Installation Guide for rules on multiple devices per spur
201. ignal with ProcessLogix control strategy CM AIC PV PV BACKCALIN P1 l PID CPM CEE DAC 9 OP PV RCAS_IN CAS_INA FIM FIM SE B Fieldbus Device N BKCAL OUT CAS_IN Analog RCAS OUT Bs ee ae ee i ReAs In Output Fs Transducer AIC Analog Input Channel BACKCALIN Back Calculation Input BKCAL_OUT Back Calculation Output CAS_IN Cascade Input CEE Control Execution Environment CM Control Module CPM Control Processor Module DACQ Data Acquistion FIM Fieldbus Interface Module OP Output PID Proportional Integral Derivative PV Process Variable RCAS_IN Remote Cascade Input RCAS_OUT Remote Cascade Output CPM CEE Fieldbus Device 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 5 Integration of fieldbus device PID control with ProcessLogix control strategy gt Analog Transducer Input OUT AIC Analog Input Channel BACKCALIN Back Calculatio
202. into Rockwell Automation Logix System Tags Addresses and Live Tag and address assignments List 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 The SMK for devices without tags are set to the Uncommissioned state and connected to the bus at one of four default device addresses The Data Link Layer specifies these default addresses as non visitor node addresses The following figure shows the general allocation of data link layer addresses to field devices Figure 2 10 Summary of address allocations for fieldbus devices Non Visitor addresses Number of used as default First Unused Unused Node addresses for devices Visitor addresses Node Address Addresses requiring address used for temporary V FUN SN V NUN assignments handheld devices Node Addresses 0 E E T 10 E E a es ee x eG amp woos a ay ee Y ee ak ae Ge F8 roi FB FC Ta FF Standard Global Usable Usable Addresses and Flat Node Addresses Addresses ORINI E Temporary devices such as handheld interfaces are not assigned tags or addresses They join the netw
203. irect Acting Balance Ramp Track Enable Track in Manual Use PV for BKCAL_OUT opem mer a e sme x ff x e Ronin Xe referee TTT rs freee PT e Table A 24 CYCLE_SEL Classification Simple Variable Description A bit string to identify the block execution method selected for this resource FF Data Type Bit String Usage C Contained Length 2 Valid Views VIEW_2 Storage Static Remarks Changing this parameter may be fatal to communication Publication 1757 UMO06A EN P May 2002 A 10 Standard Function Block Parameters Dxxx Blocks Publication 1757 UMO06A EN P May 2002 Table A 25 CYCLE_TYPE Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable A bit string to identity the block execution methods available for this resource Bit String set by Manufacturer C Contained 2 VIEW_4 Static Read Only Table A 26 DEV_REV Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Identifies the manufacturer revision number associated with the resource An interface device uses it to locate the DD file for the resource Unsigned 8 set by manufacturer C Contained 1 VIEW_4 Static Read Only Table A 27 DEV_TYPE Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Identifies the manufacturer s
204. irectly DIRECT or if the value is in different units must be converted linearly indirectly or with square root Ind Sqr Root using the input range defined by the transducer and associated output range Unsigned 8 1 Direct 2 Indirect 3 Ind Sqr Root C Contained Length Valid Views Storage Standard Function Block Parameters A 25 1 VIEW _4 Static Table A 67 LO_ALM Classification Description FF Data Type Usage Length Storage Remarks Record Represents the status of the low alarm and Its associated time stamp DS 71 C Alarm 16 Dynamic Read Only The Data type consists of data that describes floating point alarms It uses the following five elements e Unacknowledged e Alarm State e Time Stamp e Subcode e Value Table A 68 LO LIM Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Defines the setting for the low alarm in engineering units Float Infinity PV_SCALE C Contained 4 VIEW_4 Static Initial value is Infinity Table A 69 LO_LO_ALM Classification Description FF Data Type Usage Record Represents the status of the low low alarm and its associated time stamp DS 71 C Alarm Publication 1757 UMO06A EN P May 2002 A 26 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Length Storage Remarks 16 Dynamic Read Only The Data type consists of data t
205. 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 3 Alarm Attribute Definition Bit Position 7 615 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 Bit 2 Acknowledge is undefined when read and should be ignored when performing a GET When a user wants to Acknowledge an alarm this bit should be written as a 1 when performing a SET Each time the LD detects a 1 in the Acknowledge position a Fieldbus Acknowledge will be generated Therefore users must be careful not to set the Acknowledge bit more than once per alarm Bits 1 and 0 CLEARED and ACTIVE respectively are read write bits When an alarm condition is ACTIVE or CLEARED these bits are read as a 1 when performing a GET The user must Confirm each of these states by writing them to a 0 by a SET Once an alarm has occurred become ACTIVE alarm processing is NOT complete until the user intervenes to remove the alarm condition Acknowledges the alarm writing a 1 in the Acknowledge bit position Confirms the alarm writing a 0 to the ACTIVE bit position once it is read as a 1 and Confirms the alarm condition being CLEARED writing a 0 to the CLEARED
206. it to Auto If the AI output does not go to AUTO and the Status to Good you will probably need help from the transmitter manufacturer Close the Transducer block window The monitor window should now be displaying values with a status of Good NonCascade If the AI has not changed to Auto mode check to see that the Channel and L_type have been initialized Double click on the offending AI block Under the Process Tab look for Channel This indicates which of the channels through the Foundation Fieldbus device is supported by this AI If the Channel is uninitalized click on it and select one of the available choices Click Write Go to the Scaling Tab Look at L_type or Lineariztion Type If it is uninitialized set it to Direct and write the value If you still have problems with the device call device manufacturer Squeeze the pressure ball on the transmitter or wait for a pressure cycle and verify you can see the pressure change on the monitor Now that the Fieldbus side is set up and working you are ready to configure the ControlNet side Publication 1757 UMO06A EN P May 2002 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 The following steps illustrate the sequence in which data will be sent CLX PLX or
207. king Device 7 7 Figure 7 5 Sample Multiple Macrocycle AO Configuration Function Block Applicati Loop Time 1s Stale Limit N 2 O Sul a6 AT 0 K Loon Time 1 sec Stale Limit 1 BEKCAL IN BKCAL IN BKCAL IN BKCAL IN BEKCAL IN BKCAL IN BKCAL IN BEKCAL IN Loop Time 500 ms Stale Limit 1 BEKCAL IN BECAL IN BEKCAL IN BEKCAL IN BECAL IN BEKCAL IN BEKCAL IN BEKCAL IN 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 In other words you can bring values from a PLC processor to any function block The MAO block is not limited to interfacing with AO function blocks ControlNet Analog Output Objects The linking device creates an instance of a ControlNet AO object for every wired channel in the MAO block instances Each instance of the Publication 1757 UMO06A EN P May 2002 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 Initial Number Type Value Remarks side 11 FailStateValue Float Set The linking devic
208. ks to incorporate fieldbus devices in a unified ProcessLogix Control Strategy This means ProcessLogix function blocks and fieldbus function blocks can be easily interconnected so control can reside on the fieldbus link in the Control Processor Control Execution Environment CEE or cascaded from CEE to the fieldbus device An integrated Fieldbus Library Manager lets users read the manufacturer s Device Descriptions for fieldbus devices to be tied to an H1 Link and create individual templates for each fieldbus device including their function blocks The fieldbus device templates will reside in the Engineering Repository Database for ProcessLogix Once a fieldbus device template is created the fieldbus device is easily associated with the appropriate FIM H1 Link through the Project tab in Control Builder The following figure shows how icons are used to readily identify FIM H1 Links and fieldbus devices in the Control Builder Project tab Icon for function block representing FIM hardware Icon for function block representing fieldbus device to be tied to one of the H1 Links Integrating Fieldbus into Rockwell Automation Logix System 2 5 Figure 2 2 Project tab in Control Builder has new icons for Fieldbus components Project a Foot 7 CPM19 Icons for H1 Links _ associated with FIM11 Et amp 1757 FIM 4 Al Ea SB Icons for fieldbus function blocks associated with fieldbus device a i L
209. l 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 fle CM102 Project GALL OEY DEWCTL_102 HORMMOCESTTR NORMAL HUMSTATES z FF ol IFF LL EF TEG our FTRIGS ore 4 HZ 1 With CM102 chart open click the parameter connector button in the toolbar The cursor changes to cross hairs T 2 Click SI pin on DEVCTL block Double click area adjacent to pin Configurating the 1757 FIM 4 49 3 Parameter connection box appears Ld 4 Click Browse E The Point Selector window opens Point Selection Eile x Point Names Block Names Types CM101 CONTRO CM101 ALLEVEL TT1000FF pl CM101 AO FLOW AOCHAN CM101 DATAACO_ DATAACO CM101 PID_101 PID CM102 CONTRO CM102 DEVCTL_102 DEVCTL CPM19 CPM200 j Cikdid CIKA Point Name Parameter Selected Item 5 In the Point Names list scroll to find CM101 DATAACQ_101 and select it The Parameters list is populated with applicable parameters _Point Names Block Names Types Parameters of CM101 DATAAC CEE20 CEEFB CM101 CONTRO CM101 AlLEVEL TT1000FF BADPVALM FL CM101 40 _FLOW AOCHAN BADPVALM PR DATAACG DATAACO BADPYALM SY CM101 PID_101 P
210. le DOC Digital Output Channel Fieldbus Discrete Input data manipulation When the OUT from the fieldbus Discrete Input function block is wired to the DI n input for a DEVCTL function block the Control Builder creates a CFE discrete input agent to handle the digital input from the fieldbus block The block like discrete input agent maps the data structure DS 66 of the OUT parameter to the ProcessLogix DI n with status parameter It interprets the value portion in fieldbus terms as a Boolean for Discrete Input DD block and as the appropriate multi state representation for special fieldbus Device Control DC block The value is converted and represented in ProcessLogix at the output The discrete input agent accepts inputs from either a published parameter or a client server read parameter depending upon the communication method used The fieldbus data quality of good cascade good non cascade bad and uncertain is mapped to the appropriate ProcessLogix parameter for good bad and uncertain 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 m
211. lect Directory dialog box so you can select another directory location where the DEF file is to be saved File gt Build Device Template gt From Current Device Makes template from current open device file Publication 1757 UMO06A EN P May 2002 Fieldbus Library Manager E 3 Table E 2 Menu and toolbar selection summary Click Or follow this menu selection To perform this function File gt Build Device Template gt From Existing DEF Opens dialog box so you can navigate to the directory containing the Files desired device DEF files Default directory is Rockwell Automation tps50 system er ffdevices File gt Login to server Opens Login Information dialog box so you can login to another ProcessLogix Server in your system Edit gt Undo Ctrl Z Undo the last action Edit gt Cut Ctrl X Cut selected data from current location a Edit gt Copy Ctrl C Copy selected data and store it on the clipboard Edit gt Paste Ctrl V Paste previous cut or copied data to selected location View gt select View gt ProcessLogix Display Select ProcessLogix parameter data for viewing in the view pane View gt select View gt FF Device Display Select Fieldbus Foundation parameter data for viewing in the view pane View gt Select View gt Custom select user customized view as named by user View gt Organize Views gt Add View Opens Add New View dialog box so you can enter name for a customized view you want to create Cu
212. lect Download Configuration in the NI FBUS Configurator enable the Clear Devices checkbox in the dialog box that appears and download a new configuration The linking device can receive trends and alarms from connected Fieldbus devices Use NI FBUS configurator to connect trends and alarms to the linking device Within the function block application drag the linking device icon from the browse window Connect trends and alarms as necessary from Fieldbus devices to the trends or alarms inputs Refer to the NI FBUS Configurator User Manual publication 1788 6 5 2 for additional information Tips for Connecting to a 1756 ENET Controller Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device 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 You can bridge to ControlNet through a ControlLogix Gateway and then to Foundation Fieldbus through a 1788 CN2FF Figure 7 11 Remote Configuration Example Hot Backup Configuration ControlLogix ControlLogix Local HMI PC Processor 1 Processor 2 Ethernet Redundant 1756 CNB Remote ControlNet CLX 1 0 and Comms Connection Chassis 1756 ENET Ethernet Interface 1788 CN2FF Foundation Ethernet Fieldbus Remot
213. ll 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 TIP A fieldbus device whose period of function block execution is an integer factor of the macrocycle of gt the link will have a function block execution schedule prepared that has the optimal shorter cycle For example if the control strategy includes a CM with a 10 second period for a temperature loop a second CM with a 1 second period for a pressure loop and a third CM with a 250 millisecond period for a flow loop a 1 second macrocycle can be downloaded to the device that contains functions blocks used in the 1 second and 250 ms CMs Figure 2 9 Algorithm execution phase sequence Cascade uull 2 Remote Cascade Set Point Calculation Target Actual Mode Mode 1 Mode Calculation set aa A py Remote Out 3 Back Calculation oo Primary Input F pa Block Specific Parameters i Out 1 Primary Output i ed Calculation SP amp OUT Output 4 gt Remote Cascade Out Parameters In Back Calculation Out Backward Path gt Remote Out Out Publication 1757 UMO06A EN P May 2002 2 28 Integrating Fieldbus
214. ll be used If there is no last usable value the present value of the OUT will be used Use the Obey SP limits if Cas or RCas CONTROL_OPTS to use SP value after limiting in Cas or RCas mode Use the Use PV for BKCAL_OUT CONTROL_OPTS to the PV value for the BKCAL_OUT value ACK_OPTION ALARM_HYS ALARM_SUM ALERT_KEY BAL_TIME BIAS BKCAL_HYS BKCAL_IN BKCAL_OUT BLOCK_ALM BLOCK_ERR BYPASS CAS_IN CONTROL_OPTS DV_HI_ALM DV_HI_LIM DV_HI_PRI DV_LO_ALM DV_LO_LIM DV_LO_PRI FF_GAIN FF_SCALE FF_VAL GAIN GRANT_DENY HI_ALM HI_HI_ALM HI_HI_LIM HI_HI_PRI HI_LIM HI_PRI IN LO_ALM LO_LIM LO_LO_ALM LO_LO_LIM LO_LO_PRI LO_PRI MODE_BLK OUT OUT_HI_LIM OUT_LO_LIM OUT_SCALE PV PV_HIME PV_SCALE RATE RCAS_IN RCAS_OUT ROUT_IN ROUT_OUT SHED_OPT SP SP_HI_LIM SP_LO_LIM SP_RATE_DN SP_RATE_UP ST_REV STATUS_OPTS STRATEGY TAG_DESC TRK_IN_D TRK_SCALE TRK_VAL UPDATE_EVT The Fieldbus Communication Model 1 23 Proportional Integral Derivative Block Figure 1 12 Functional Schematic for Porportional Integral Derivative Function Block IN gt BKCAL_IN gt gt CAS IN gt gt BKCAL OUT RCAS_IN gt PID P OUT ROUT_IN gt P RCAS_OUT TRK_IN_D gt m gt ROUT_OUT TRK_VAL FF_VAL gt lt BKCAL_OUT 5 E eso RCAS_OUT FF VAL z ROUT IN
215. lock in the Project tab of Control Builder TIP You can configure a Link through the Project tab of Control Builder without having the link installed However some parameters on the Link configuration gt form can only be viewed through the Monitoring tab with the FIM and Link installed and communicating with the system Be sure to click the plus sign in front of the FIM icon to open its directory tree and expose the link icons Configurating the 1757 FIM 4 13 1 Double click the link icon Eg The Link Block Parameters window opens SYSTEM LINK Block LINK51 Parameters Project i xi Main System Management Network Management Application Server Parameters Name F DESCRIPTION C SEG State SEG Command NONE Enable MAU loopback Last communication error a Cy Oana 0 J75 usage Average Sent lime 0 Average Acknowledge Time F Average Confirmation Time ea a May Sent Time a E M Show Parameter Names Cancel Help 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 The other parameters can not be configured because they are only active in the Monitoring tab after the FIM LINK is loaded and communicating with
216. lue of the block Blocks that filter the input to get the PV require this parameter FF Data Type DS 65 Usage Primary Input Length 5 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 e Status e Value Table A 64 IN_1 Classification Record Description Represents the auxiliary input value to the block It is used for values other than the PV FF Data Type DS 65 Usage I Input Length 5 Publication 1757 UMO06A EN P May 2002 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 e Status e 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 FF Data Type Unsigned 8 Range 0 to MAX_NOTIFY Usage C Contained Length 1 Valid Views VIEW_2 Storage Static Remarks Initial value is MAX_NOTIFY Table A 66 L_TYPE Classification Description FF Data Type Range Usage Publication 1757 UMO06A EN P May 2002 simple Variable Determines whether the values passed by the Transducer block to the Analog Input block may be used d
217. mal 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 following table provides a summary of the available modes of operation and their effect on operation Table 1 C Modes of Operation Mode Abbreviation Operation Effect Out of Service OOS The block is not being evaluated The output is maintained at the last value an assigned failsafe value last value or configured failsafe value Set Point is maintained at last value Initialization IMan The block output is being set in response to the back calculation input parameter status When Manual status Is no path to the final output element control blocks must initialize to provide for bumpless transfer when the condition clears The Set Point may be maintained or initialized to the Process Variable parameter value Local Override L Applies to control and output blocks that support a track input parameter Also manufacturers may provide a local lockout switch on the device to enable the Local Override mode The block output is being set to track the value of the track input parameter The algorithm must initialize to avoid a bump when the mode switches back to the target mode The Set Point may be maintained or initialized to the Process Variable parameter value o Manual Man The block is not being calculated
218. 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 PLCS Pub No 1757 UMOO6A EN P Pub Date May 2002 Part No 957603 37 Please complete the sections below Where applicabte rank the feature 1 needs improvement 2 satisfactory and 3 0utstanding Overall Usefulness 1 2 3 How can we make this publication more useful for you 2 3 Can we add more information to help you Completeness all necessary information procedure step illustration _ feature ided gel ee _ example guideline _ other _ explanation definition Technical Accuracy 1 E Can we be more accurate all provided information Clarity 1 2 3 How can we make things clearer all provided information is easy to understand Other Comments You can add additional comments on the back of this form Your Name Location Phone Your Title Function Would you like us to contact you regarding your comments ___No there is no need to contact me ___Yes please call me ___Yes please email me at ____Yes please contact me via Return this form to Allen Bradley Marketing Communications 1 Allen Bradley Dr Mayfield Hts OH 44124 9705 Phone 440 646 3176 Fax 440 646 3525 Email RADocumentComments ra rockwell com Publication ICCG 5 21 January 2001 PN 955107 82 Other Comments PLEASE FASTEN HERE DO NOT STAPLE PLEASE FOLD
219. ment is limited by Ohm s law E IxR Where E The voltage of the dc power supply I The amount of current in amperes drawn by each device typically 20mA R The resistance of the cable in ohms EXAMPLE Assume that the characteristics of the segment are a power supply output of 20Vdc 18 AWG cable with a resistance of 22 ohms per kilometer 3281 feet and a home run trunk cable that is 1 km 8 281 ft long This results in a combined resistance of 44 ohms for both wires If each device at the branch draws 20mA and needs a minimum of 9Vdc the cable can use up to 11Vdc 20 9 11 and the total current that can be supplied at the chickenfoot is 250mA 11Vdc 44 ohms 250mA This means the maximum number of bus powered devices that can be used at this example chickenfoot is 12 250mA 20mA 12 devices Be sure to check the fieldbus device specifications to determine the power requirements since they can vary by device type and manufacturer A physical test can should be performed on each H1 segment prior to power up to check for shorts and verify resistance Test the power carrying capability of the fieldbus cable by connecting the wires together at one end of the cable and measuring the resistance across the wires at the other end with an ohmmeter One approach to minimizing signal distortion is to apply rules of thumb that suggest how long a fieldbus cable can be and still get adequate s
220. mode switches to Cascade the upstream block is requested to initialize to the value of QUT Upon transition to bypass OFF the upstream block is requested to initialize to the PV value regardless of the Use PV for BRCAL_OUT CONTROL_OPTS status Use the Balance Ramp CONTROL_OPTS to maintain the BIAS value when the block is in Manual Man mode An internal value follows the actual value required to maintain balance When block mode changes to Automatic Auto the internal value ramps to zero contribution in BAL_TIME seconds If Balance Ramp option is OFF or not used the BIAS value immediately changes to follow the changes to the input or output when the block is in Man mode Use the Act on IR CONTROL_OPTS to select whether to ignore initialization requests or act on them by changing the BIAS If this option is ON a status of Not Invited NI or Initialization Request IR at BKCAL_IN causes the BIAS term to be adjusted to balance OUT to the value of BKCAL_IN Use the Direct Acting CONTROL_OPTS to define how a change in PV relative to the SP affects the output When Direct Acting is ON the output increases when the PV exceeds the SP When Direct Acting is OFF the output decreases when the PV exceeds the SP Be sure this option is set correctly and never changed while in the Automatic mode since it makes the difference between positive and negative feedback This option setting also affects the calculation of the limit states for BKCAL_OUT This blo
221. model number associated with the resource An interface device uses it to locate the DD file for the resource Unsigned 16 set by manufacturer C Contained 2 VIEW_4 Static Read Only Standard Function Block Parameters A 11 Table A 28 DD_RESOURCE Classification Description FF Data Type Usage Length Storage Remarks simple Variable Identifies the tag of the resource that contains the Device Description for this resource Visible String C DD Resource 32 Static Read Only Table A 29 DD_REV Classification Description FF Data Type Usage Length Valid Views Storage Remarks Simple Variable Identifies the revision of the Device Description associated with the resource so an interface device can locate the DD file for the resource Unsigned 8 C Contained 1 VIEW _4 Static Read Only Table A 30 DISC_ALM Classification Description FF Data Type Usage Length Storage Remarks Record Identifies the status and time stamp associated with the discrete alarm DS 72 C Alarm 13 Dynamic Read Only The data type consists of data that describes discrete alarms It uses the fol lowing five elements e Unacknowledged e Alarm State e Time Stamp e Subcode e Value Publication 1757 UMO06A EN P May 2002 A 12 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Table A 31 DISC_LIM Classification Description FF Data Type Range Usage Length
222. n Block IN gt BKCAL_IN gt ROUT IN gt ML P OUT TRK IND gt ROUT OUT TRK_VAL BKCAL_IN aerar ROUT_IN ROUT_OUT aa a Filter Output IN py_FTIME OUT_HI_LIM oot B APY OUT LO LIM Alarm HI LO Mode Output Track SHED_OPT TRK_SCALE a TRKIND TRK_VAL Publication 1757 UMO06A EN P May 2002 1 20 The Fieldbus Communication Model Table 1 J Manual Loader Block Specifications Description Function Notes Parameters see Appendix A for definitions of each parameter 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 Supports Out of Service OOS Initialization Manual I Man Local Override LO Manual Man and Remote Out ROut modes Accepts output from an Al block as its input IN to get a PV filtered by PV_FTIME The block s algorithm uses value and status for alarming only If selected the STATUS_OPTS of IFS if BAD IN will work The BKCAL_IN value and status can force balancing of the output The TRK_VAL input brings in an external value or uses a constant The TRK_SCALE values convert the TRK_VAL to a percent of output span value If the CONTROL_OPTS Track Enable selection is tr
223. n Input BKCAL_IN Back Calculation Input BKCAL_OUT Back Calculation Output CAS_IN Cascade Input CM AIC PV PV BACKCALIN P1 l J PID DACQ OP PV RCAS_IN CAS_INA FIM ca Y Ay gt IN BKCAL_OUT a KKK CAS_IN RCAS_OUT zo a c RCAS_IN OUT ROUT_IN O O gt BKCAL_ OUT ROUT OUT ga PD cASIN Analog E gt our BKCAL_IN gt js gt RCAS IN Output pene TRK_IN_D y gt Transducer TRK_VAL gt FF_VAL CEE Control Execution Environment OP Output CM Control Module PID Proportional Integral Derivative CPM Control Processor Module PV Process Variable DACQ Data Acquistion RCAS_IN Remote Cascade Input FIM Fieldbus Interface Module RCAS_OUT Remote Cascade Output ROUT _OUT Remote Out Output Fieldbus Analog Output or PID data manipulation When the OP from the PID function block is wired to the CAS_IN input for a fieldbus Analog Output or Proportional Integral Derivative function block the Control Builder automatically creates a CEE output agent to handle the analog output to the fieldbus block Publication 1757 UMO06A EN P May 2002 2 12 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 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 convert
224. n System Interconnection OSI model for layered communications As shown in Figure 1 1 OSI layer 1 is the Physical Layer OSI layer 2 is the Data Link Layer and OSI layer 7 is the application layer or the Fieldbus Message Specification A Fieldbus Access Sublayer maps the Fieldbus Message Specification onto the Data Link Layer Fieldbus does not use OSI layers 3 to 6 and layers 2 and 7 form the Communication Stack Also the OSI model does not define a User Application but the Fieldbus Foundation does Figure 1 1 OSI versus Fieldbus communication model Fieldbus Model OSI Model User Application User Application Fieldbus Message Specification Application Layer Fieldbus Access Sublayer Presentation Layer Communication Session Layer Stack Transport Layer Network Layer Data Link Layer Data Link Layer Physical Layer Physical Layer Physical Layer Publication 1757 UMO06A EN P May 2002 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 4 Communication Layer Descriptions Layer Physical Data Link DLL Fieldbus Access Subl
225. n model 1 3 Function Block Application Process based on blocks 1 5 Using Function Blocks in Fieldbus Devices to Fori a COnUOM OOD s 2 2 44 646k ee haa gees ee ees 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 1 13 Functional Schematic for Control Selector Function Block 1 15 Functional Schematic for Discrete Input Function Block 1 17 Functional Schematic for Discrete Output Function Block 1 18 Functional Schematic for Manual Loader Function Block 1 19 Functional Schematic for Proportional Derivative Function Block1 21 Functional Schematic for Porportional Integral Derivative FUNCHON BIOCK 22 424 4452e nt ge nea ehe santas gas 1 23 Functional schematic for Ratio function block 1 25 Device Descriptions infrastructure 0 0005 1 28 Logix system architecture for Fieldbus integration 2 2 Project tab in Control Builder has new icons for Fieldbus components anaana dh a oy ah aed 2 5 Integration of fieldbus device analog input signal with ProcessLogix control strategy 2b naaa aaa 2 8 Integration of a Fieldbus device analog output signal with ProcessLogix control strategy oo ie dod Sa a ee 2 10 Integration of fieldbus device PID control with ProcessLogix control strategy n nnaou aaa 2 11 Integration of fieldbus dev
226. n solid state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication Reproduction of the contents of this copyrighted publication in whole or part without written permission of Rockwell Automation is prohibited Throughout this publication notes may be used to make you aware of safety considerations The following annotations and their accompanying statements help you to identify a potential hazard avoid a potential hazard and recognize the consequences of a potential hazard WARNING Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss Identifies information racti r ATTENTION de tifies information about practices o E circumstances that can lead to personal injury or death property damage or economic loss IMPORTANT Identifies information that is critical for successful application and understanding of the product 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 become familiar with the Fieldbus Foundation is or what constitutes the FOUNDATION Model or network layer Fieldbus technology This section also includes d
227. n 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 Leave the Tag Description field at the default of CM101 AI LEVEL CM name plus block name 6 In the Grant and Deny fields click the desired checkboxes to select the functions you want to Grant Deny an operator Grant Deny Progam Program Denied W Tune W Tune Denied I Alarm I Alarm Denied Iw Local lw Local 7 Scroll down to the Mode section MODE Target Actual Permitted ROUT Iv REAS gt CAS IY AUTO M MAN r Lo M IMAM lf O05 MHormal 8 Click the desired checkboxes to select the modes you want to permit 9 Click OK to clock the window and save the configuration Publication 1757 UM006A EN P May 2002 Configurating the 1757 FIM 4 41 Configuring DATAAC 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 DATAACOQ Block Parameters window opens DATAACQ DATAACQ Block DATAACQA Parameters Project fo CX I Name Execution Order in CM 170 Description Engr Units r Process Variable P Source Option ONLYAUTO ALL PVEU Range Hi 100 7 PYEU Range Lo 0 Py Source auto
228. n will actually copy 12 bytes since the copy instruction always bases the length on the size of the destination tag Since the destination tag is actually a structure of 12 bytes 1 element is 12 bytes 19 20 1 Accept the rung and save your project Download the project to the controller We are now ready to test the project Put the processor in RUN mode and view the individual elements under the tag structure LD_Node_9 You should be able to read all the values directly now 1788 CN2FF Installation Example F 47 The actual pressure of about 04 psi Gin 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 You can use a ControlNet message instruction to get any of the data CLX to Get Data from CN2FF that is stored in the different tables that list the various ControlNet objects The best way to get data from a CN2FF into a controller is to have it produced by the CN2FF This requires that you use RSNetworx to gt schedule the data It is much more efficient than using message commands For a CLX to retrieve data setup the message as shown below Message Configuration mp 5G ES Configuration Communication Message Type CIP Genetic Service Code le Hex Source O Object Type la Hes Hum OfElem
229. nator Publication 1757 UMO06A EN P May 2002 Fieldbus wiring selection and calculation The preferred cable for connecting fieldbus devices is 18 AWG 0 8mm 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 TIP We can t emphasize enough the use of high quality network wire installation The higher quality of installation materials the better B gt performance you will achieve in your network application Universal manufacturers sell Fieldbus cable which meets all the specifications required for Fieldbus cable Windows based Fieldbus Segment Calculator tools are available in the market place that can assist you in calculating the performance characteristics of a planned fieldbus segment See Appendix D for a condensed overview of fieldbus wiring considerations provided for convenient reference This information does overlap some information that is found in other data references as well Refer to the 1757 FIM Installation Instructions publication 1757 IN0913A EN P Refer to the 1757 RTP Installation Instructions publication 1757 IN915A EN P Before You Start Question What do you kn
230. nd using a high resolution monitor and short Function Block names The Device Info screen describes the format of the data that is produced by the 1788 CN2FF on ControlNet The Offset column indicates the offset in bytes from the beginning of the transmission to each piece of data from a Fieldbus devise Schedule Data Transmission to Controllers with RSNetworx You must use RSNetworx to schedule the transmission of data to the controller RSLogix 5000 or Control Builder Place the data in an integer data table like N13 starting at location N13 0 You may need to add some devices to the configuration so we recommend that you leave some empty words in the data table Store the data from each of the linking devices at an easy to calculate location like N13 0 then store the data from the next CN2FF at N13 50 the data from the next CN2FF at N13 100 etc PLC 5 Data Manipulation Figure F 4 on page F 37 shows that the Floating Point value of each Analog Input from the Fieldbus devices is a four byte ControlNet Float when it goes on the wire When this four byte value arrives at the PLC 5 it is stored in an integer file in a PLC 5 word format That Publication 1757 UM006A EN P May 2002 F 38 1788 CN2FF Installation Example Publication 1757 UMO06A EN P May 2002 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
231. nge 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 e Run e Restart Resource e Restart with Defaults e Restart Processor FF Data Type Unsigned 8 Range 1 Run 2 Restart Resource 3 Restart with Defaults 4 Restart Processor Usage C Contained Length 1 Storage Dynamic Remarks Changing this parameter may be fatal to communication Table A 101 ROUT_IN Classification Description FF Data Type Usage Length Record Represents target output and status provided by a host to a control block for use as the block s output in ROUT mode DS 65 C Remote Output In 5 Publication 1757 UMO06A EN P May 2002 A 38 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Valid Views Storage Remarks Classification Description FF Data Type Usage Length Valid Views Storage Remarks Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks VIEW_3 Dynamic The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Table A 102 ROUT OUT Record Represents block output and status It serves as input to a host for back calcu lation in ROut mode that allows action to be taken
232. nly The data type consists of the value and status of discrete value parameters It uses the following two elements e Status e Value Table A 47 FREE_SPACE Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Identifies the percent of memory available for further configuration Zero in a preconfigured resource Float 0 100 percent C Contained 4 VIEW_2 Dynamic Read Only Publication 1757 UMO06A EN P May 2002 A 18 Standard Function Block Parameters Table A 48 FREE_TIME Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Identifies the percent of block processing time that is free to process addi tional blocks Float 0 100 percent C Contained 4 VIEW_1 VIEW_3 Dynamic Read Only Table A 49 FSAFE_TIME Classification Description FF Data Type Range Usage Length Valid Views Storage simple Variable Represents the reaction time in seconds from the detection of a failure at the output block remote setpoint to the output block action if the condition still exists Float Positive C Contained 4 VIEW_4 Static Table A 50 FSAFE_VAL Classification Description FF Data Type Range Usage Length Valid Views Storage Publication 1757 UMO06A EN P May 2002 simple Variable Defines the preset analog setpoint to use when a failure occur
233. node address ADDR must match those specified through Control Builder Any mismatch results in an error Publication 1757 UMO06A EN P May 2002 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 This confirms that the designated FIM is operating and that the RTP and the H1 segment is OK TIP If ALIV appears in the FIM s front panel display you must load the FIM s personality firmware before proceeding 2 Click the FIM block icon in the Project tab Project ee CM102 CM55 CPM30 example cascade example motor example pid example scr Publication 1757 UMO06A EN P May 2002 4 56 Configurating the 1757 FIM 3 Click Tools Load The Load Dialog window opens Load Dialog MSS ee xj Loa Current State StateToLoad Post Load State V FIMS0 Err 7005 N A N A V Restore all blocks to Post Load State after load Cancel Help 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
234. ns Chapter 6 Adding Removing and Replacing Components About Removal and Insertion Under Power Genera PIOCeQUiet 4 0024 Bae eee eee ees Upgrading firmware in an uncommissioned device Interpreting Component LED Indications FIM LED inCicanlOns oi graean eR eS a Checking Fieldbus Device Calibration Chapter 7 Blocks in the Linking Device 00 00 0008 PANG SVMS a audit ty cote ng eke aes Bee ee sete Ge ees fe a Configuration of Analog Inputs ControlNet Analog Input Objects Alarm Handling for Analog Inputs ANAOOOUPUSs 2 42a ba tae ee S426 SEG ea eS AS Configuration of Analog Outputs ControlNet Analog Output Objects SOUS OG acca amp Sony vy e e a a Oe Dh ee ek Gee Gs Configuration of Discrete Inputs 04 ControlNet Discrete Input Objects Alarm Handling for Discrete Inputs Discrete OUIPUIS 2am e ea eee Cede eae Shadaweed as Configuration of Discrete Outputs 04 ControlNet Discrete Output Objects Alarm Handling by the HMI 0 0 4 SSE MIDI ODC dala reas eh dead Guia Raat eed MALBO 2 eg ctune 2 eG Aik tae oe Meee Cae ee MAG BIOCKS sa io Ge bene oe he 34s Oe wae oa rat IML EL BIOCKS s 24 a Bde odo 3 Ue oes Bae wd aoe hx Standard Function Block Parameters Fiel
235. nt values for display purposes It uses the following four elements e1 Engineering Units at 100 percent e Engineering Units at 0 percent e3 Units Index e4 Decimal Point Table A 128 TRK_VAL Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents the input value for external tracking DS 65 Input 5 VIEW_1 VIEW_3 Non Volatile 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 e Status e Value Table A 129 UPDATE_EVT Classification Description FF Data Type Usage Length Storage Remarks Record Represents an alert generated by any change to the static data DS 73 C Event Update 1 4 Dynamic Read Only The data type consists of data that describes a static revision alarm It uses the following five elements e Unacknowledged e Update State e ime Stamp e Static Revision e Relative Index Standard Function Block Parameters A 49 VXXX Blocks No V parameters Wxxx Blocks Table A 130 WRITE_ALM Classification Record Description Represents alert that is generated if the write lock is cleared FF Data Type DS 72 Usage C Alarm Length 13 Storage Dynamic Remarks Read Only The data type describes discrete alarms using the following five elements e Unacknowledged e Alarm State e Time Stamp e Subcode e Value Table A 131 WRITE_LOCK Classi
236. nts 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 The load operation functionally copies configuration data from the control strategy that is stored in the Engineering Repository Database ERDB to the assigned field component in the system architecture In ProcessLogix R400 0 the load operation has been expanded to include fieldbus components The load operation assures that the planned Foundation Fieldbus system matches the actual one The communication addresses and physical location assignments specified for components through Control Builder configuration must match the actual addresses and locations of components in the system Figure 4 6 is a simplified graphical representation of what happens during a load operation Figure 4 6 Overview of load operations used to initiate components online ERDB PLX a Slot 05 io PLX na bi LX Allen Bradley e s J car IM IOMs i H1 Link 1 J R Remote B Termination Panel FOUNDATION Fieldbus Compliant Devices Notes CM Control Module CN ControlNet Module FB Function Block FIM Fieldbus Interface Module Publication 1757 UM006A EN P May 2002 4 52 Configurating the 1757 FIM Lists com
237. o LO The status of BKCAL_OUT and RCAS_OUT goes to Not Invited NI if not already there If the status of TRK_IN_D is Bad its last usable value will be maintained and acted upon If the device restarts losing the last usable value it will be set to false If the status of TRK_VAL is Bad the last usable value will be used If there is no last usable value the present value of the OUT will be used Use the Obey SP limits if Cas or RCas CONTROL_OPTS to use SP value after limiting in Cas or RCas mode e Use the Use PV for BKCAL_OUT CONTROL_OPTS to the PV value for the BKCAL_OUT value Equation Options If Auto mode OUT IN_1 filtered x SP x GAIN PV IN filtered IN_1 filtered GAIN If IN_1 has non cascade status BRCAL_OUT BKCAL_IN GAIN IN_1 filtered If IN_1 has cascade status BKCAL_OUT BKCAL_IN GAIN SP Parameters ACK_OPTION DV_LO_LIM LO_LO_LIM SP see Appendix A ALARM_HYS DV_LO_PRI LO_LO_PRI SP_HI_LIM for definitions of ALARM_SUM GAIN LO_PRI SP_LO_LIM each parameter ALERT_KEY GRANT_DENY MODE_BLK SP_RATE_DN BAL_TIME HI_ALM OUT SP_RATE_UP BKCAL_IN HI_HI_ALM OUT_HI_LIM ST_REV BKCAL_OUT HI_HI_LIM OUT_LO_LIM STATUS_OPTS BLOCK_ALM HI_HI_PRI OUT_SCALE STRATEGY BLOCK_ERR HI_LIM PV TAG_DESC CAS_IN HI_PRI PV_FIIME TRK_IN_D CONTROL_OPTS IN PV_ SCALE TRK_SCALE DV_HI_ALM IN_1 RA_FIIME TRK_VAL DV_HI_LIM LO_ALM RCAS_IN UPDATE_EVT DV_HI_PRI LO_ LIM RCAS_OUT DV_LO_ALM LO_LO ALM SHED_OPT Publication 1757 UMO06A
238. o the CM101 chart a 2 HOR MAC O E HORMMODESTTR CTLEQH Fme B Unk sin l Et L14101 oio o AO PID Fe RESOURCE a TRANSDUCER amp stio til Library Publication 1757 UMO06A EN P May 2002 Configurating the 1757 FIM 4 39 8 Click and drag the AO block AD to the CM101 chart The AO block is added to the CM101 chart COS IN WALU FONS ER YE L1H0F F _ a0 AQ DEVICE L 14 104 OUT WALUE o Configuring Al block for sample loop 1 In the CM101 chart double click the AI block The AI Block Parameters opens HONEY WELL ST3000FF_0801 AI Block Al_LE VEL Parameters Project Na ANAR xj Name m E Description Associated Device 5T101 Execution Order in CM hooo Pre execution delay Doo Post execution delay OO Tag Description MINA Grant Deny I Program Program Denied I Tune I Tune Denied I Alarm J Alarm Denied I Local Local Process Variable 0 Bad Raw Field Value 0 Bad Output 0 Bad I Show Parameter Names Cancel Help 2 In the Name field type AI_ LEVEL 3 In the Description field type Input for Tank 106 Level Publication 1757 UM006A EN P May 2002 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 i
239. ode hee oe hoe 1 11 Bias GaN DIOCKs 241 464 enant ELE ee wee eed toa es 1 13 Control Selector Bloke renra piine ee eee ad hed 1 15 Discrete In pul DIOCK vssans taco rre ds hee eee 1 17 Discrete Output BlOCK 1404444644204 6440446204 1 18 Manual Loader Block 0 000 000 0000 cee 1 19 Proportional Derivative Block 00 1 21 Proportional Integral Derivative Block 1 23 RAW c DIO Cle ich he che ees hla See tee 1 25 Device Descriptions and Block Parameters 1 27 About Device Descriptions 0 00008 1 27 Device Description Langgate 6 a 25h4Ge hae hae ards 127 Device Description infrastructure 1 28 Foundation Fieldbus Performance 0 66 00 5 0044 1 29 Performance Calculation Considerations 1 29 Publication 1757 UMO06A EN P May 2002 vi Table of Contents Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 Chapter 2 OTe in amp ete sae a eee ae ay dh hole aah eee th ee a ee S 2 1 Background the goals of integration 2 1 Fieldbus Integrated Architectures i 1va04 6 ic own wae 2 2 Fieldbus Interface Modules The Key to an Integrated System 240ae 44054eh44e4 2 3 Configuration Tools naaa 24a ee he ORS A RD RS 2 4 Foundation Fieldbus Configuration Tool 2 5 Centralized Operator Interface 0 0005 2 5 Network Management description 2 6 system
240. of an individual fieldbus device only breaks communications with that device Publication 1757 UMO06A EN P May 2002 6 2 1757 FIM General Maintenance Checkout and Calibration General Procedure ATTENTION 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 Publication 1757 UMO06A EN P May 2002 1757 FIM General Maintenance Checkout and Calibration 6 3 Upgrading firmware in an uncommissioned device 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 If you are adding a fieldbus device follow the installation instructions for the component and then configure it through Control Builder to integrate it with your control strategy If you are removing and or replacing a fieldbus device proceed with extreme caution You must delete restore and or create all hardware connections and the control strategy database configuration through the Control Builder You may
241. on Record Description Allows the transducer analog input or output to the block to be manually sup FF Data Type Usage Length Storage Remarks plied when SIMULATE is enabled When SIMULATE is disabled the simulate value and status track the actual value and status DS 82 C Simulate 11 Dynamic The data type consists of simulate and transducer floating point value and sta tus and a simulate enable disable discrete It uses the following five ele ments 1 Simulate Status 2 Simulate Value 3 Transducer Status 4 Transducer Value 5 Simulate Enable Disable Table A 113 SIMULATE_D Classification Description FF Data Type Usage Length Storage Remarks Table A 114 SP Classification Description FF Data Type Range Usage Length Record Allows the transducer discrete input or output to the block to be manually sup plied when SIMULATE is enabled When SIMULATE is disabled the simulate value and status track the actual value and status DS 83 C Simulate 5 Dynamic The data type consists of a simulate and transducer discrete value and status and a simulate enable disable discrete It uses the following five elements 1 Simulate Status 2 Simulate Value 3 Transducer Status 4 Transducer Value 5 Simulate Enable Disable Record Defines the setpoint of any analog block DS 65 PV_SCALE 10 percent C Setpoint 5 Valid Views Storage Remarks Standard Function Block Parameters A
242. one execution FF Data Type Unsigned 8 Range 1 Off 2 On Usage C Contained Length 1 Cxxx Blocks Valid Views Storage Remarks Standard Function Block Parameters A 7 VIEW_2 Static Initial value is 0 Table A 17 CAS_IN Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents the remote setpoint value that must come from another fieldbus block or a distributed control system DCS block through a defined link DS 65 Cascade Input 5 VIEW_1 VIEW_3 Dynamic The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Table A 18 CAS_IN_D Classification Record Description Represents the remote setpoint value for a discrete block that must come from another fieldbus block or a distributed control system DCS block through a defined link FF Data Type DS 66 Usage Cascade Input Length 2 Valid Views VIEW_1 VIEW_3 Storage Dynamic Remarks The data type consists of the value and status of discrete value parameters It uses the following two elements e Status e Value Table A 19 CHANNEL Classification Simple Variable Description The number of the logical hardware channel that is connected to this 1 0 block It defines the transducer used to connect to the physical world FF Data Type Unsigned 16 Range 1 to Manufacturer Limit Publication 1757 UMO0
243. ontrol Module in the ProcessLogix Control Builder application The Proportional Integral Derivative PID function block is a typical regulatory control type function block The Fieldbus Library Manager FLM in ProcessLogix R400 0 Control Builder makes this possible The FLM reads the manufacturer s DD for the fieldbus device and creates a device template that is included in the Project tab of Control Builder The device template includes the device s fieldbus function blocks so it can be configured and integrated with control strategies through Control Builder Publication 1757 UMO06A EN P May 2002 2 8 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 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 3 Integration of fieldbus device analog input signal with ProcessLogix control strategy CM PV gt PID CPM CEE OP OP AOC FIM FIM Fieldbus AOC Analog Output Channel Device Analog CEE Control Execution Environment Input OUT CM Control Module CPM Control Processor Module FIM Fieldbus Interface Module Transducer OP Output PID Proportional Integral De
244. or uses a constant The TRK_SCALE values convert the TRK_VAL to a percent of output span value If the CONTROL_OPTS Track Enable selection is true and TRK_IN_D is true the converted TRK_VAL replaces the output OUT when the block is in Automatic Cascade or Remote Cascade mode The CONTROL_OPTS Track in Manual selection must be true for this to occur in Manual mode If the actual mode is OOS or IMan the track request is ignored If the TRK_VAL replaces the OUT its status becomes Locked Out with Limits set to Constant The actual mode goes to LO The status of RCAS_OUT goes to Not Invited NI if not already there If the status of TRK_IN_D is Bad its last usable value will be maintained and acted upon If the device restarts losing the last usable value it will be set to false If the status of TRK_VAL is Bad the last usable value will be used If there is no last usable value the present value of the OUT will be used In Automatic mode OUT IN_1 SP x GAIN If IN_1 has Non Cascade status BKCAL_OUT BKCAL_IN GAIN IN_1 lf IN_1 has Cascade status BKCAL_OUT BKCAL_IN GAIN SP Parameters ALERT_KEY GAIN RCAS_IN ST_REV see Appendix A for BAL_TIME GRANT_DENY RCAS_ OUT STATUS _OPTS definitions of each BKCAL_IN IN_1 SHED_OPT STRATEGY parameter BKCAL_OUT MODE_BLK SP TAG_DESC BLOCK_ALM OUT SP_HI_LIM TRK_IN_D BLOCK_ERR OUT_HI_LIM SP_LO_LIM TRK_SCALE CAS_IN OUT_LO_LIM SsP_RATE_DN TRK_VAL CONTROL_OPTS OUT_ SCALE SP_RATE_
245. orage Remarks Record The selector output value and status associated with SEL_1 input that is pro vided to BKCAL_IN of the block connected to SEL_1 to prevent reset windup DS 65 O Back Calculation Output 5 VIEW_3 Dynamic The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Table A 12 BKCAL_SEL_2 Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record The selector output value and status associated with SEL_2 input that is pro vided to BKCAL_IN of the block connected to SEL_2 to prevent reset windup DS 65 O Back Calculation Output 5 VIEW_3 Dynamic The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Table A 13 BKCAL_SEL_3 Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record The selector output value and status associated with SEL_3 input that is pro vided to BKCAL_IN of the block connected to SEL_3 to prevent reset windup DS 65 O Back Calculation Output 5 VIEW_3 Dynamic The data type consists of the value and status of floating point parameters that are Inputs or Outputs It uses the following two elements e Status e Value Publication 1757 UMO06A EN P May 2002 A 6 Standard Fun
246. ork through one of four data link visitor addresses reserved for them in the data link layer protocol Publication 1757 UMO06A EN P May 2002 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 When the LAS for the link recognizes a new device at a default address it adds it to its live list according to the data link layer procedures The FIM detects the change in the live list and makes a connection to the new uncommissioned device It gathers the following information from the device to be passed to Control Builder Table 2 1 Gathered information from device passed to Control Builder Description Data Type Pdlag Physical Device Tag 32 byte string Read Write Device Address Unsigned8 DevID Globally unique Device 32 byte string Read Only Identifier Control Builder uses the device information to create an item in its Monitoring tree to represent the new uncommissioned device on the given link Users can now view and configure pertinent information for the uncommissioned devic
247. ormance of a fieldbus system Publication 1757 UMO06A EN P May 2002 2 32 Integrating Fieldbus into Rockwell Automation Logix System Notification Scheme Publication 1757 UMO06A EN P May 2002 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 ProcessLogix alarms use Journal Low High and Urgent as priorities with a sub priority of 0 to 255 Table 2 J shows how fieldbus priorities are mapped to ProcessLogix priorities and severities Table 2 J Mapping Fieldbus Priorities to ProcessLogix Fieldbus Alarm Priority ProcessLogix Alarm ProcessLogix Alarm Priority Severity Can never be seen by FIM Can never be seen by FIM or above or above 1 Can never be seen by FIM Can never be seen by FIM or above or above 2 Journal BLOCK_ERR bit 14 Event System Only power up BLOCK_ERR bit 15 Out of Service 3 System Level Diagnostic All other bitstring High indications BLOCK_ERR bits 0 13 XD_ERROR bits 16 25 2 User selected Journal 15 gt al BI wt N No No al BI cw Mm gt I co Integrating Fieldbus into Rockwell Autom
248. ow about Control Builder Do you know how to configure a Control Processor Module Can you configure a Control Module Are you familiar with your system architecture Are you ready Chapter 4 Configurating the 1757 FIM Table 4 A Where do you begin If your answer is If your answer Is Nothing Yes you can skip this section 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 No Yes you can skip this section Read the Creating a Control Processor Module section in the Control Building Guide or find the topic in Knowledge Builder This section shows you how to create a Control Processor Module CPM and its associated Control Execution Environment CEE No Yes you can skip this section Read at least the Creating and Saving a Control Module section in Knowledge Builder This section shows you how to create a Control Module CM and insert and connect function blocks To complete the configuration data for certain components you must know the planned or current location of the associated hardware components in your ProcessLogix system architecture This includes the chassis slot location for any given CPM and FIM We suggest that you create a simple diagram that outlines the location of components in your system showing slot locations and communication addresses for
249. owledge bit position Confirms the alarm writing a 0 to the ACTIVE bit position once it is read as a 1 and Confirms the alarm condition being CLEARED writing a 0 to the CLEARED bit position once it is read as a 1 This section describes configuration of the linking device to control any discrete value and status in a Fieldbus device such as in a Discrete Output DO function block It also describes the attributes of the created ControlNet discrete output object The linking device contains one MDI block instances on each Fieldbus channels Each instance of the MDO block is the software equivalent of a discrete output module in a I O subsystem Each MDO block also has eight channels or outputs with each channel containing a byte and a status pair Each MDO block has eight inputs to provide for the BKCAL or readback from the discrete output function blocks The linking device assigns a tag to each MDO block in the form CNetMacIdxx_DO_Modulei j7 where xx is the ControlNet network address i is the Fieldbus channel number and 7 is the module or instance number Publication 1757 UMO06A EN P May 2002 7 12 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Publication 1757 UMO06A EN P May 2002 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 MD
250. p Aah Limit Wap Low Limit Wap lain Factor Linear lain Factor oi Non Linearity Korm Non Linear lain Factor Linear lain Factor Linear lain Factor External Gain Factor 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 REGCTL PID Block PIDA Parameters Project Advisory sr alue E E Normal Ramp Fate Mas Ramp Deviation Publication 1757 UM006A EN P May 2002 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 This is a function block that was loaded using the gt 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 FLOWSERVE LX1400FF_0502 A0 Block AO Parameters Project exh Name AO Description Associated Device Lx14_101 Execution Order in CM 000 Pre execution delay 00 Post execution delay 00 Tag Description EMA Grant Deny I Program Program Denied T Tune Tune Denied Alarm Alarm Denied Local Local Setpoint 0 Bad Cascade Input 0 Bad Back Calculation Output 1 Bae ii M Show Parameter Names Cancel Help 2 In the Name field enter AO_FLOW 3 In the Description field enter Flow Control Output 4 Click OK to clos
251. 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 The location of the alert in the OD Identifies the alert as a record multiple values of different types Identifies the data format as a data structure associated with the Meta type Attributes of an object which may be individually accessed through the FB_Read and FB_ Write service by using the sub index number with the object index number Sub index numbers are assigned based on Meta type The number of bytes required to represent the data type The engineering units in which the value is represented Usage Indication of whether the alert may be linked to a block parameter Storage Specification that alert must be stored in dynamic D memory List of Valid Values Standard type will have the following enumerated values Table 2 M Standard type valid values Valid Values 0 j CO N My o A wy N Meaning Undefined LO Low limit HI High limit LO LO Critical low limit HI HI Critical high limit DV LO Deviation low DV HI Deviation high DISC Discrete BLOCK Block Alarm UPDATE Static data update WRITE Write protect changed Integrating Fieldbus into Rockwell Automation Logix System 2 37 Table 2 M Standard type valid values Valid Values Meanin
252. ple F 17 10 Double click the NIFB icon on the desktop Starting NIFB ation Irkst U Windows NT Wi gt EKIA Foomicaemacce If the Icon is not on your Desktop you can get it at Start Programs National Ed Instruments NIFB exe Shortcut to fbcont exe Lee tio SYSTEM M1 SIntensnice Le p CA ITS Utilities La Monitor d Programs i La National Instruments FBUS i Configurator Readme La Netscape Communicator Interface Config Documents Le Network gl NIFE Settings LE NI FBUS ES NI FBUS Configurator mn Le Norton Antivirus a NI FBUS Dialog p Le Offices NI FBUS Readme Help Lea Oracles2 t Bun Shut Down You are now ready for the next step toward configuring a Fieldbus 1 Go to Start gt Programs National Instruments FBUS and click You see NI FBUS ver 2 3 6 on NIFB dl Configurator Readme pa Interlace Config al NIFE ee NI FBUS Configurator a NI FBUS Dialog NI FBUS Readme Starting Publication 1757 UMO06A EN P May 2002 F 18 1788 CN2FF Installation Example Troubleshooting the Port Configuration Publication 1757 UMO06A EN P May 2002 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 z appe
253. ponents to be loaded Load Dialog Individual checkboxes let you edit list of components to be loaded Shaded area flags component with possible invalid data 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 7 Descriptions of the FIM Dialog Box Features Specifies state component must be in during a load Specifies state component will assume after load is completed Chance to select Shows current partial load if state of applicable component Load Partial Load Current Stat State To Load Post Load Sta Z FIM B1 L EERUN gP o a e e o 7 410 LX14_101 TRANSDUCE ee LX14_101 RESOURCE Err 7005 OOS NORMAL Can select another STID pr 7005 State from dropdown STOLTRANSDUCER O p erzo oos Normal menu for this field ST101 RESOURCE Err 7005 OOS NORMAL Z LINK 102 ONLINE Y amp 42 030156 Err 7005 MA hed 8742 030156 TRANSDU Err 7005 DOS NORMAL 8742030156 RESOURC Err 7005 00S NORMAL Y Butfalo_1 Bre 7005 INACTIWE ACTIWE Buffalo1 PIDHON1 Err 7005 OOS NORMAL Buffalo tALHON ferros oos norme J3 Am m mas a _ Select whether or not Flestore all blocks to Post Load State alter load component is to be returned to the post load state AN Mote Mismatched
254. r Specific Parameters that define the parameters a manufacturer has added to the standard Function Block and Transducer Block parameters These added parameters will be included on the manufacturer s Incremental DD Foundation Fieldbus Performance The Fieldbus Communication Model 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 Therefore in the application reflected in this schedule you should plan on a loop closure time of on the order of 1 second if you want new data from all devices each time you run the loop calculation Part of the reason that fieldbus is slow is that Fieldbus devices operate on very small amounts of current 10 to 20 ma per device is typical This translates into slow computations in the transmitters It typically takes 100 ms for a fieldbus transmitter to make a new measurement of an input with all the associated calculations completed Therefore when attempting to determine the performance of a fieldbus system please recognize these facts Performance Calculation Considerations Some pressure transmitters will read their transducers and create a new floating point digital readings of the PV every 100 ms That value can
255. r to build ProcessLogix control strategies you will find adding fieldbus function blocks is intuitive since it is the same as adding ProcessLogix function blocks Also the procedures are abbreviated in some cases in the interest of brevity Once you get the feel of using Control Builder it is more efficient to interact directly with the application and use the online help to find an answer to a question about a function or an entry Creating Control Module in Project 1 In the Library tab expand the System directory by clicking the Ba FLOWSERVE So HONEYWELL Sa ROSEMOUNT HE SYSTEM 3a CONTROLMODULE Publication 1757 UMO06A EN P May 2002 4 34 Configurating the 1757 FIM 2 Double click the CONTROLMODULE icon a A new control module opens fiz CM63 Project 3 Click Tools gt Configure Module Parameters The Control Module Block Parameters window opens SYSTEM CONTROLMODULE Block CM63 Parameters Project Main Server Name Execution Period DEFAULT Description Execution Phase j Engr Units Unit Text Keyword Version Enable Alarming Option IV SCM Option NONE gt Execution Order in CEE fio SCi Hawa Fieldbus Specific Execution Order in Link ft 0 FF Execution Period DEFAULT Stale Count 2 J Show Parameter Names Cancel Help 4 In the Name field enter CM101 5 In the Desc
256. reference during configuration Once you have addressed all the questions in this section you are ready to move on to the next section Configuring Fieldbus Components At this point you should have at least a working knowledge of the Control Builder application Publication 1757 UMO06A EN P May 2002 4 2 Configurating the 1757 FIM Figure 4 1 Example Rockwell Fieldbus Configuration ProcessLogix System Server ControlNet Network PLX amp CLX E TA m ey a a a eee ae z z ae i DeviceNet oor ANA Data Highway pLu DEUNORO Ci DEMN HI E SLC Controller PLC 5 1771 Remote 1 0 Flex Ex Controller Am PLC5 C Controller Pressure Transmitter Publication 1757
257. 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 C Shed Option 1 VIEW_4 Static Note 1 Actual mode changes to the next lowest priority non remote mode permitted but returns to the target remote mode when the remote computer completes the initialization handshake Note 2 Target mode changes to the next lowest priority non remote mode per mitted The target remote mode is lost so there is no return to It Note 3 Target mode changes to Auto on detection of a shed condition Note 4 Target mode changes to Man on detection of a shed condition Table A 110 SHED_RCAS Classification Description FF Data Type Range Usage Length Valid Views Storage simple Variable Defines timeout in milliseconds for computer writes to function block RCas locations Unsigned 32 Positive C Contained 4 VIEW_2 Static Table A 111 SHED_ROUT Classification Description FF Data Type Range Usage Length Valid Views Storage simple Variable Defines timeout in milliseconds for computer writes to function block ROut locations Unsigned 32 Positive C Contained 4 VIEW_2 Static Publication 1757 UMO06A EN P May 2002 A 42 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Table A 112 SIMULATE Classificati
258. ribute Definition naaa aaa TED Sample Cascaded AO Configuration naaa aaaea 7 6 Sample Multiple Macrocycle AO Configuration IF Sample Single Macrocycle MDI Configuration 7 9 Alarm Attribute Definition tk 42h 43 bo ade y awd eee 7 10 Sample Cascade DO Configuration 04 7 12 Semne Wp am Alass aac hod on aks Be wR ara Be oe ee 7 14 Sample NI FBUS Configurator View of ControlNet Object MORMANON 4 4 daa e ot ao Wes ean ae Be 7 17 Remote Configuration Example y s t o0ise outa Same te 7 19 Overview of fieldbus wiring topologies D 1 Fieldbus Library Manager uses vendor DD file to create device template for Control Builder E 1 Fieldbus Library Manager features common Windows type interface naana ey Ge oa ay ad E 2 Example Linking Device Configuration F 4 Wano he 17 OSsOCNZEE amp gsig dette ee Poe Bike eo ee F 5 5 Analog Input Function Blocks 04 F 30 Device Information Screen 2 ssae ac ba eae obtains de F 37 Control Net Module PIO peices ws v adhe amp od eed Se F 42 Data VAN CS 3 cian oe Guten 6 oe ee Gr ee ee S F 45 PLC Mosd oe SCUD 4 644 404 o4 4 deg beds ena Ed F 48 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 Wy You can complete this form and mail it back to us visit us online at www ab com
259. ription FF Data Type Range Usage Record 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 DS 65 C Process Variable 5 VIEW_1 VIEW_3 Dynamic 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 e Status e Value Table A 87 PV_D Record Represents either the primary discrete value for use In executing the function Or a process value associated with it It may also be calculated from the READBACK_D value of a Discrete Output block DS 66 C Process Variable 2 VIEW_1 VIEW_3 Dynamic Read Only The data type consists of the value and status of discrete value parameters It uses the following two elements e Status e Value Table A 88 PV_FTIME simple Variable Defines the time constant of a single expotential filter for the Process Variable in seconds Float Positive C Contained Standard Function Block Parameters A 33 Oxxx Blocks Length Valid Views Storage 4 VIEW _4 Static Table A 89 PV_SCALE Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record 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
260. ription field type Surge Tank Control Loop 6 In the Eng Units field type Percent 7 In the Keyword field type Recycle Publication 1757 UM006A EN P May 2002 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 MRE RE 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 Leave the Execution Period field at DEFAULT This equals1000ms for a 50ms CEE or 200ms for a 5ms CEE 11 Leave the Execution Order in Link field at the default of 10 the smaller the number the sooner the device is polled on the link GURIDI E The Execution Order in Link parameter only applies to contained fieldbus blocks It combines with the combines with the block s Execution Order in CM parameter to determine how the fieldbus block participates in the Link Active Schedule 12 Leave the FF Execution Period field at DEFAULT ATTENTION The FF Execution Period parameter only applies to contained fieldbus blocks It determines how the fieldbus blocks participate in the Link Active Schedule 13 Leave the Stale Count field at the default of 2 14 Le
261. rivative PV Process Variable Fieldbus Analog Input data manipulation When the OUT from the fieldbus analog input function block is wired to the PV input for a PID function block the Control Builder creates a CEE input agent to handle the analog input from the fieldbus block The block like input agent maps the data structure DS 65 of the OUT parameter to the ProcessLogix PV with status parameter It interprets the value portion in fieldbus terms and converts it to ProcessLogix representation The floating point representation is identical in most cases but the fieldbus infinity value must be converted to a ProcessLogix representation If the fieldbus status byte indicates BAD the value must be converted to Not a Number NaN for ProcessLogix representation 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 The handshaking provided by the substatus associated with Good cascade status is not supported from an upstream Fieldbus device This means
262. rm Out Of Service a Fault State Active FSA sl Initiate Fault State IFS The Good non cascade substatus is used by output connections for fieldbus blocks such as Analog Input and Discrete Input The Good cascade substatus is used by output connections for fieldbus blocks such as PID Both of these substatuses are converted to the single ProcessLogix data quality of Good Fieldbus Status Indications See Appendix B for list of possible display indications associated with a given fieldbus status Publication 1757 UMO06A EN P May 2002 Integrating Fieldbus into Rockwell Automation Logix System 2 19 Control Mode Interaction 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 For use within ProcessLogix the structure of the MODE_BLK parameter is expanded to add MODE to the existing Actual Target Permitted and Normal modes as outlined in Table 2 C Table 2 C Mode Descriptions ProcessLogix Mode Data Type Description FIM Action Structure MODE Enumeration Write Only The FIM captures all writes to ProcessLogix style mode enumeration MODE and maps valid changes to MAN AUTO CAS NORMAL BCAS NONE MODE TARGET MODE TARGET Enumeration Read Write If the value NO
263. roller provides the necessary mode handshake for cascade initialization of the AO block In this case you must connect CN_OUT_Ax of the MAO block to CAS_IN of the AO block and BKCAL_OUT of the AO block to BKCAL_IN_Ax of the MAO block as shown in Figure 7 4 Note that there is a strict ordering relationship between CN_OUT_Ax and CN_BKCAL_IN_Ax parameters of the MAO block That is CN_ BKCAL_IN_AO is associated with CN_OUT_AO CN_BKCAL_IN_A1 with CN_OUT_A1 and so on Figure 7 4 Sample Cascaded AO Configuration loop Time 1sec 4fStale Limit 1 B ty S Sal ATO Salam ad CNetMacld03_AO0 Module _0 CNAO ad Valve 54 AO CN BKCAL IN AO CN OUT AD CAS IN OUT gt PCN BKCAL IN Al CN OUT Al Pe BKCAL OUT fo CN BKCAL IN A2 CN OUT A gt RT rms Me PCN BKCAL IN A3 CN OUT A3 Trends e PCN BKCAL IN A4 CN OUT Ad ee PCN DECAL IN A30 CN OUT AS BCN BKCAL IN Ao CN OUT Ach CN BKCAL IN A CN OUT AT Alarms De Trends j The linking device consumes analog values produced by the controller on ControlNet and publishes these values on Fieldbus The NI FBUS Configurator sets up the analog output devices to subscribe to their data on Fieldbus Each MAO block has its own schedule to consume data on ControlNet and publish it on Fieldbus For different rates of publishing on Fieldbus you must choose different MAO blocks as shown in Figure 7 5 Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Lin
264. s Standard Function Block Parameters A 47 112 Dynamic The data type consists of function block test read write data It uses the fol lowing 15 elements e Value 1 Boolean e Value 2 Integer 8 e Value 3 Integer 16 e Value 4 Integer 32 e Value 5 Unsigned 8 e Value 6 Unsigned 16 e Value 7 Unsigned 32 e Value 8 Floating Point e Value 9 Visible String e Value 10 Octet String e Value 11 Date e Value 12 Time of Day e Value 13 Time Difference e Value 14 Bit String e Value 15 Time Value Table A 126 TRK_IN_D Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Represents the discrete input for initiation of the external tracking function DS 66 Input 2 VIEW_1 VIEW_3 Non Volatile Read Only The data type consists of the value and status of discrete value parameters It uses the following two elements e Status e Value Table A 127 TRK_SCALE Classification Description FF Data Type Usage Length Record Defines the high and low scale values engineering units code and number of digits to the right of the decmial point associated with TRK_VAL DS 68 C Scaling 11 Publication 1757 UMO06A EN P May 2002 A 48 Standard Function Block Parameters Uxxx Blocks Publication 1757 UMO06A EN P May 2002 Valid Views Storage Remarks VIEW_4 Static The Data type consists of data that describes floating poi
265. s Value Is ignored if the O_OPTS Failsafe to value option is false Float PV_SCALE 10 percent C Contained 4 VIEW_4 Static Standard Function Block Parameters A 19 Table A 51 FSAFE_VAL_D Classification Simple Variable Description Defines the preset discrete setpoint to use when a failure occurs Value is ignored if the O_OPTS Failsafe to value option is false FF Data Type Unsigned 8 Usage C Contained Length 1 Valid Views VIEW_4 Storage Static Gxxx Blocks Table A 52 GAIN Classification Simple Variable Description Represents dimensonless gain used by several different algorithms FF Data Type Float Usage C Contained Length 4 Valid Views VIEW_4 Storage Static Table A 53 GRANT_DENY Classification Description FF Data Type Usage Length Valid Views Storage Remarks Record Defines options for controlling access of host computer or local control panels to the block s operating tuning and alarm parameters DS 70 C Access Permission 2 VIEW_2 Non Volatile The data type consists of access control flags for access to block parameters It uses the following two elements e Grant e Deny Publication 1757 UMO06A EN P May 2002 A 20 Standard Function Block Parameters Hxxx Blocks Publication 1757 UMO06A EN P May 2002 Table A 54 HARD_TYPES Classification Description FF Data Type Range Usage Length Valid Views Storage Remarks simple Variable Identifies type
266. s 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 If the status of OP is BAD its value must be converted from NaN to zero 0 0 for fieldbus representation or it may retain its previous good value as long as the fieldbus status byte indicates BAD The CEE output agent also accepts a single BKCAL_OUT parameter with the fieldbus data structure DS 65 and maps it to the BACKCALIN parameter of the PID block in ProcessLogix terms ATTENTION The ProcessLogix Control Builder application automatically makes the appropriate back calculation connections during configuration and the connections are hidden in Control Chart views Like the FIM the output agent supports both publish subscribe and client server communication methods The publish subscribe method allows the FIM to appear as a fieldbus device on the H1 link The FIM publishes the output OP for subscribing fieldbus device resident blocks such as Analog Output and Proportional Integral Derivative PID through their CAS_IN parameter input connection This connection is generally used when the downstream control block is in the Cas cascade mode This means that the fieldbus block s BKCAL_OUT parameter is published by the downstream block and subscribed to by the FIM The client server method allows the FIM to appear as a computing de
267. s of hardware that are available as channel numbers on this resource Bit String Set by manufacturer C Contained 2 VIEW _4 Static Read Only Table A 55 HI_ALM Classification Description FF Data Type Usage Length Storage Remarks Record Identifies the status and time stamp associated with the high alarm DS 71 C Alarm 16 Dynamic Read Only The Data type consists of data that describes floating point alarms It uses the following five elements e Unacknowledged e Alarm State e Time Stamp e Subcode e Value Table A 56 HI_HI_ALM Classification Description FF Data Type Usage Record Identifies the status and time stamp associated with the high high alarm DS 71 C 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 e1 Unacknowledged e Alarm State e3 Time Stamp e4 Subcode e5 Value Table A 57 HI_HI_LIM Classification Simple Variable Description Defines the high high alarm limit setting in engineering units FF Data Type Float Range PV_SCALE infinity Usage C Contained Length 4 Valid Views VIEW_4 Storage Static Remarks Initial value is infinity Table A 58 HI_HI_PRI Classification Simple Variable Description Defines priority of the high high alarm FF Data Type Unsigned 8 Range 0 to 63 Usage C Alert Priority
268. s or mode change DS 66 C Remote Cascade Out 2 Publication 1757 UMO06A EN P May 2002 A 36 Standard Function Block Parameters Publication 1757 UMO06A EN P May 2002 Classification Description FF Data Type Usage Length Valid Views Storage Remarks 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 e Status e Value Table A 97 READBACK Classification Record Description Represents the readback of the actual continuous valve or other actuator position in transducer units FF Data Type DS 65 Usage C Contained Length 5 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 e Status e Value Table A 98 READBACK_D Record Represents the readback of the actual discrete valve or other actuator posi tion in the transducer state DS 66 C Contained 2 VIEW_1 VIEW_3 Dynamic Read Only The data type consists of the value and status of discrete value parameters It uses the following two elements e Status e Value 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 Ra
269. s used in multiple locations in your application You can make adjustments to selected device parameters through Control Builder configuration access You can find definitions for many of the standard fieldbus function blocks in Appendix A in this document Vendors also supply a text file that includes definitions for each function block used in their device Configurating the 1757 FIM 4 21 10 11 12 13 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 STATUS_OPTS 0 000000 0 000000 0 OxE 400 SP_RATE_UP 0 000000 0 000000 0 20 SP_RATE_DN 0 000000 0 000000 0 10 SP_LO_LIM 0 000000 0 000000 0 SP_HI_LIM 0 000000 0 000000 0 700 SP 0 000000 0 000000 0 O Enter the desired value and press Enter Repeat Steps 9 10 and 11 to edit parameters for your application as required Click File gt Build Device Template gt From Current Device Edit View Help Open Device Cie fe 23 Faye PS EF Save Chrl 5 Save As Build Device Templates From Current Device From Existing DEF Files 1 Honeywell Pressure Transmitter FlowServe Valve Controller Exil The ProcessLogix device template is built from current data in the ERDB and a device directory name pre defined by the vendor is added to the Library tab in Control Builder If the device directory already exists the device is added to the dire
270. stant e 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 Publication 1757 UMO06A EN P May 2002 1 24 The Fieldbus Communication Model Table 1 L Proportional Integral Derivative Block Specifications Function Notes e The tuning constant used for the Proportional term is GAIN RESET is used for the Integral term and RATE is used cont 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 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 While BYPASS is ON the SP value in percent of range is passed directly to the target output and the value of OUT is used for BKCAL_OUT When block mode switches to Cascade the upstream block is requested to initialize to the value of QUT Upon transition to bypass OFF the upstream block is requested to initialize to the
271. stomize the new view by selecting desired attributes through the Select View Attributes dialog box The new custom view name is added to the Select View menu selections View gt Organize Views gt Delete View Opens Select View to Delete dialog box so you can delete the selected customized view View gt Organize Views gt Modity View Opens Select View to Modify dialog box so you can modify selected view through the Select View Attributes dialog box a View gt Toolbar Toggle Toolbar view On Off View gt Optimize View Columns Automatically adjusts columns for optimum viewing cd Help gt Help Topics Calls up online Help topics Publication 1757 UMO06A EN P May 2002 E 4 Fieldbus Library Manager Table E 2 Menu and toolbar selection summary Click Or follow this menu selection To perform this function Help gt About Fieldbus Library Manager Opens About Fieldbus Library Manager dialog box for general information about the utility Publication 1757 UM006A EN P May 2002 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 F
272. t Data to be keyed in at prompt or in an entry field Key in this path location gt D setup exe lt lt Ctrl gt lt C gt Keys to be pressed together are shown with a plus sign Press lt Ctrl gt lt C gt to close the window Publication 1757 UMO06A EN P May 2002 Rockwell Automation Technical Support About this document 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 Local Product Support Contact your local Rockwell Automation representative for e sales and order support e product technical training e warranty support support service agreements Obtain Technical Product Support If you need to contact Rockwell Automation for technical assistance first call your local Rockwell Automation representative then If you need to contact Rockwell Automation for technical assistance try one of the following methods Type of technical support Access at Personalized Service Call your local Rockwell Automation representative Pre sales Technical Support 1 440 646 3638 3NET Post sales Technical Support 1 440 646 5800 Email your questions racleasktheexpert ra rockwell com Internet www ab com Publications www theautomationbookstore com Your Questions or Comments about This Manual
273. t IN passes through a filter with a time constant PV_FIIME The filtered value becomes the Process Variable PV to be used with the Set point SP in the block s algorithm e 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 e The tuning constant used for the Proportional term is GAIN and RATE is used for the Derivative term 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 Description Publication 1757 UMO06A EN P May 2002 1 22 The Fieldbus Communication Model Table 1 K Proportional Derivative Block Function Notes cont Parameters see Appendix A for definitions of each parameter Publication 1757 UMO06A EN P May 2002 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 While BYPASS is ON the SP value in percent of range is passed directly to the target output and the value of OUT is used for BKCAL_OUT When block
274. t NIFB and click End 1788 CN2FF Installation Example F 19 Once the NIFB software is running we are ready to start the configurator tool IMPORTANT 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 Therefore it is good practice to verify your connection by manually starting the NIFB exe before starting the config tool Start FCS 1 Double click on the NI FBUS configuration icon on the desktop This software will again check to see that it can see all the Fieldbus interfaces that we listed in the Interface Config Window and it will ask which of the Fieldbus networks that you want to configure The following window appears Add Links What kind of project would you like to create f Online connected to a certain buslink E afne aot conpected to any bus Added link s WILD 9 Board 0 Port 0 2 Select the Linking Device and associated Fieldbus you want to configure and click OK Publication 1757 UMO06A EN P May 2002 F 20 1788 CN2FF Installation Example Add Links What kind of project would you like to create f Online connected to a certain bus link E aine ot connected ta any busi Added link z WILD 9 Board 0 Port 0 3 Uncheck one box so we onl
275. tallation Example 4 When the working icon disappears click Network Parameters eal NI FBUS Freldbus Configuration System File Edit View Rosemount Temp Configure Window Help s HH ssa fiz Ene LO 9 Log Motes These are the devices on the FF network Network Parameters Your list of devices and Function Blocks H i Schedule will be different This is called the ma Function Block Application Function Block Library 5 i a Si M evice Into RE Resource RB ad CNetMacld09_Al_Module0_0 CHAI ad CNetMacld09_Al_Module1_0 CHAI ad CNetMacld09_A0_Module0_0 CNAO ad CNetMacld09_A0_Module1_0 CHAD ad CNetMacld09_DI_ModuleO_0 CNDI iai CNetMacld09_D0_Module0_0 CNDO cm BS Honeywell Attached H E Rosemount 1151 You see Primary LAS LD 9 Network Parameters LAS Link Active Scheduler Ej at LAS stands for Link Active Scheduler and ra Eal E identifies the device which will hold the Primary Settings Link Settings Advanced network schedule and tell each node when to aR l LD 9 D 4E 49434002 CN FF 2 OO4SCD620 0 Publish its FF information Primary LAS i Primary Timemaster LO 9 ID 4E 49454002 CH FF 2 00ACDEZ0 0 Uncheck the download to Link Masters Devices that will receive the LAS schedule Honeywell Attached This will LO 9 ID 4E 49434002 CH FF 2 0QACDEZO 0 reduce the download time Bdonevwell Attached D 485 4C0002 H W L 5 TS000 400465361 2 5 Select the Primary LAS and the Primary Timemast
276. th Man cleared Likewise If neither Auto nor Man or both are set and neither ROut RCas nor Cas mode is set Man mode will be assumed with Auto cleared For the OOS mode the Man bit should be set unless it is not permitted If Man is not permitted the Auto bit should be set unless it is not permitted If neither Auto nor Man is permitted the OOS bit should be set IMPORTANT An operator needs an access level of ENGR or higher to invoke the OOS mode or to return a block to an in service mode ProcessLogix adheres to the following additional rules for setting fieldbus target mode bits in Table 2 G for its MODE supported subset of combinations Table 2 G Additional rules for setting fieldbus target mode bits Fieldbus Mode OOS Man ii lt a 5 Auto Cas RCas ROut Normal Publication 1757 UM006A EN P May 2002 Rule When setting as the target mode obtain the target mode preserve the Auto and Man bits set the OOS bit and optionally reset all the other bits Reject the request if the access level is not ENGR or higher This is a Read Only parameter and can not be set as the target mode Never set the IMan as the target mode This is a Read Only parameter and can not be set as the target mode Never set the LO as the target mode When setting as the target mode set the Man bit and reset all the other bits Reject the request if the current mode is OOS and the access level is not ENGR or high
277. that control may not originate in the field and cascade into the ProcessLogix Controller Fieldbus device Analog Output or PID integration A user can functionally wire the output from a regulatory control type function block contained in a Control Module in the ProcessLogix Control Builder application to the input of an Analog Output AO or Proportional Integral Derivative PID function block in a fieldbus device residing on an H1 link The Proportional Integral Derivative PID function block is a typical ProcessLogix regulatory control type function block The Fieldbus Library Manager FLM included in the R400 Control Builder makes this possible The FLM reads the manufacturer s DD for the fieldbus device and creates a device template that is included in the Project tab of Control Builder The device template includes the device s fieldbus function blocks so it can be configured and integrated with control strategies through Control Builder Publication 1757 UMO06A EN P May 2002 2 10 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 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 4 Integration of a Fieldbus device analog output s
278. 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 See your system administrator to get your assigned Publication 1757 UM006A EN P May 2002 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 gt Build Device Template gt From Existing DEF Files The Select Device Template Definition Files dialog box opens Select Device Template Definition Files ie x Device Template Definition File Director Template Definition File List in 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 Click OK to confirm The device directory name pre defined by the vendor is added to the Library tab in Control Builder If the device directory already exists the device is added to the directory TIP If your ProcessLogix system architecture includes multiple clients the newly created device template gt resides only in the database of the Server designated during FLM login You must be logged onto the given Server to access device templates stored in its ERDB through Control Builder 10 Click OK to
279. the column on the left and drag them into the Function Block Application window i NI FBUS Fieldbus Configuration System FCP1 LD 9 Function Block Application TS BE EER Sl gt File Edit View Configure Zoom Window Help 53 zje El Loop Time 1 sec Stale Limit 1 34 K 2 O Sul EAIA Ca 12 6 LD 9 Log Notes 34 Honeywell AI AD Network Parameters ed Schedule OUT Je 45 Function Block Application Alarms A LD 9 Trends Device Info 38 Resource RB aH 1151 Temp A 24 CNetMacld09_Al_Module1_0 CNAI ad emp AD ad CNetMacld09_AO_Module0_0 CNAO 3d CNetMacld09_Al_Modulel_0 m 2 a o a 2 gt a E T _ o 3 gt 24 CNetMacld09_DI_ModuleO_0 CNDI me CN AO Alarms E 34 CNetMacld09_DO_Module0_0 CNDO CN AL Trends 3 6 Honeywell Attached 3a RS DEFB2D6 RB ad H PID Attach PID Rosemount 1151 Pres RB RB 34 PID1 PID 3 Rosemount Temp z RESOURCE RB 2 Drag one of the CN2FF Multiple Analog Input Function Blocks to the right side of the FB Application Window All AT Blocks have AI in to the right of their Tag Name 3 Consider the Loop Time which can be set in the window just above the Function Block Application You will need 40 to 50 ms for the transmission of each data value you put on the Fieldbus Therefore if you connect 10 Function BLocks to the MAI you need a loop
280. time of 500ms or more Publication 1757 UMO06A EN P May 2002 F 30 1788 CN2FF Installation Example 4 Click on the spool of wire in the top tool bar and use the wire Linkinking Device_11 Function Block Application ow Help Stale Limit 1 w 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 ad Honeywell Al AT OUT Alarms Trends p gt 24 CNetMacld09 Al Moadulel_ 0 CN a 1151 Temp AD CH A0 Alarms jie 31151 Pressure OUT OUT D P Alarms J Trends jE ES ad FT A 1004 An ad Dels Temp AD OUT OUT OUT D P OUT D P Alarms Alarms j Trends j Trends gt E C After creating this Function Block configuration drag and drop the 1788 FFCT software knows where you want connections but the Fieldbus Devices do not You must now download the configuration to the devices Publication 1757 UM006A EN P May 2002 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 Download Configuration Choose object to download Entire Configuration pe 5 T write Contained Block Parameters W Clear Devices Ready for download Download Help 2 Check the box
281. tinue 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 Errors Detected Continue to Load Server Points Continue Errors Chose 574245008 RESOURCE FEATURE_SEL FMS Od Other Error PS_E_FMSOdDther 2L 101 316 574245008 RESOURCE WRITE_LOCK FMS Od Other Error PS_E_FMSOdOther 2L 101 3182 74245008 RESOURCE ERROR_DETAIL 1 FMS Access Object Attribute Inconsistent PS_E_F S74245008 RESOURCE ERROR DETAILI21 FMS Access Obiect Attribute Inconsistent PS a 4 gt 8 After the load is complete click the Monitoring tab Monitoring OR Gime Hg FIM_E1 i LINK S101 i LINK_S102 9 Verify that the Link is activated 10 Repeat Steps 1 to 9 to load another Link or device Summary The Control Builder for the R400 ProcessLogix system lets you add and configure fieldbus components as a natural and intuitive extension to the existing ProcessLogix components This promotes a seamless integration of the fieldbus functions with existing ProcessLogix capabilities Publication 1757 UM006A EN P May 2002 Chapter 5 Monitoring Fieldbus Functions Through Station Displays Provides live view of front panel display Station del ault stn PlantScape PID Point Detail sysDtlFim dsp Operating the 1757 FIM Using Station Detail displays The ProcessLogix Server Station application includes pre con
282. tn Event Summary 140 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 2 Event Summary display includes fieldbus related details Station Edit Schematic View Control Action Configure Help aaa YY AE EOE W a aw vy xX VQ Shows all fieldbus network related events Monitoring Fieldbus Functions Through Monitoring Tab Publication 1757 UMO06A EN P May 2002 Date Time Point ID 16 Feb0O1 07 56 30 CM55 15 Feb0O1 07 58 30 LINK S101 16 Feb01 07 47 46 LINK 101 16 FebO1 07 47 46 LINK 101 16 FebO1 07 47 41 No Tag 16 FebO1 07 47 18 No Tag 16 Feb01 07 47 13 CPM30 16 Feb0O1 07 47 11 FIM_B1 16 Feb0O1 07 47 11 CNIOO01 16 Feb01 07 47 08 FIM_B1 Level Description mngr FAILURE mngr SUCCESS Event recovery begin Event recovery begin Connection ESTABLISHED Connection ESTABLISHED C200 Controller Connection ESTABLISHED AB KTC 1 Card Added Connection ESTABLISHED Inactivating Activating a Link Use the following procedure to inactivate activate a fieldbus Link through the Monitoring tab in Control Builder
283. to Project 4 24 Assigning a Device to a Link in Project 4 27 Checking Device Configuration 04 4 28 Creating Control Module for Sample PID Loop 4 33 Loading Components Online ossaa aaa aaa 4 51 About load operations o an aaaea 4 51 About the new load dialog box 4 52 General load considerations 42 4 14 4 e Sa bh ao ee 3 4 53 PiclG DUS DEVICE SIES aisir dete tad tg woe E ees 4 53 Fieldbus device matching rules 4 64 vets ee ee ke 4 54 Loading a FIM and its Links 0 0 4 55 Loading Link contents or fieldbus device 4 57 UIA te ie Ge rae a aa wae ee Ee ee tee E eek oe os 4 60 Publication 1757 UMO06A EN P May 2002 vill Table of Contents Operating the 1757 FIM 1757 FIM General Maintenance Checkout and Calibration Using the 1788 CN2FF ControlNet to FOUNDATION Fieldbus H1 Linking Device Publication 1757 UMO06A EN P May 2002 Chapter 5 Monitoring Fieldbus Functions Through Station Displays Using Station Detail displays 00 Using Station Event Summary display Monitoring Fieldbus Functions Through Monitoring Tab Inactivating Activating a Link 0 Monitoring Interacting with given component block Checking fieldbus device functional class Checking live list and interacting with uncommissioned devices anaa dd wee eke aes Using the Tools Menu Functio
284. tput assembly object Additionally if your controller participates in cascade initialization for a specific channel wiring BKCAL_OUT_D from DO attribute 154 is placed into the required input assembly Each MDO channel requires 2 bytes in the input assembly object and 4 bytes in the output assembly object if cascade initialization is performed 2 bytes if cascade initialization is not performed Viewing Object Information in the NI FBUS Configurator The NI FBUS Configurator can display information about the ControlNet objects created inside the linking device This information contains the layouts and instance numbers of the input and output assembly objects as well as instance numbers of the base ControlNet objects created To display this information view the Device Info for the linking device in question You can view the Device information in the NI FBUS Configurator from the browse window A sample Device Info display is shown in Figure 7 10 To print the Device Info put the cursor on the display of the Device Info that is shown in Figure 7 10 and click on Print under the File menu Note if the cursor is not on the Device Info display when you click on Print you will be given an extensive menu of other items that you may print but no listing for the Device Info Figure 7 10 Sample NI FBUS Configurator View of ControlNet Object Information T ie BETA NI FBUS Fieldbus Configuration System ver 2 3 CN F
285. ue and TRK_IN_D is true the converted TRK_VAL replaces the output OUT when the block is in Remote Out ROut mode The CONTROL_OPTS Track in Manual selection must be true for this to occur in Manual mode If the actual mode is OOS or IMan the track request Is ignored If the TRK_VAL replaces the OUT its status becomes Locked Out with Limits set to Constant The actual mode goes to LO The status of ROUT_OUT goes to Not Invited NI if not already there If the status of TRK_IN_D is Bad its last usable value will be maintained and acted upon If the device restarts losing the last usable value it will be set to false If the status of TRK_VAL is Bad the last usable value will be used If there is no last usable value the present value of the QUT will be used ACK_OPTION IN PV_SCALE ALARM_HYS LO_ALM ROUT_IN ALARM_SUM LO_LIM ROUT_OUT ALERT_KEY LO_LO_ALM SHED_OPT BKCAL_IN LO_LO_LIM ST_REV BLOCK_ALM LO_PRI STATUS_OPTS BLOCK_ERR LO LO_PRI STRATEGY CONTROL_OPTS MODE_BLK TAG_DESC GRANT_DENY OUT TRK_IN_D HI_ALM OUT_HI_LIM TRK_SCALE HI_HI_ALM OUT_LO_LIM TRK_VAL HI_HI_LIM OUT_SCALE UPDATE_EVT HI_HI_PRIHI_LIM PV HI_PRI PV_FIIME Publication 1757 UMO06A EN P May 2002 The Fieldbus Communication Model 1 21 f Proportional Derivative Block Figure 1 11 Functional Schematic for Proportional Derivative Function Block IN gt BKCAL_IN gt CAS_IN gt RCAS_IN ROUT_IN gt TRK_IN D
286. unctions fully integrate with control functions or provide a combination that includes using fieldbus based control as backup for selected ProcessLogix control functions The FIM uses low and high priority send queues to make sure that publish subscribe data normally used for control is processed before less important display access data Publish subscribe requests are placed in the high priority send queue and client server requests are placed in the low one Publication 1757 UMO06A EN P May 2002 2 4 Integrating Fieldbus into Rockwell Automation Logix System Publication 1757 UMO06A EN P May 2002 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 The ControlNet network consists of controllers such as PLC processors HMIs drives I O devices and so on The linking device has two broad functions supporting the following e closed loop control e configuration and monitoring Contro Builder The ProcessLogix R400 0 Control Builder application supports integral configuration of fieldbus function blocks with ProcessLogix function bloc
287. up to 16 characters 3 Click OK A device icon with the given name is created in the Project tab e example pid f at evample scm PS Fso i NKS fig LINK52 pidloop fe ST3000FF_080171 fe ge ST3000FF_080181 fe ge ST3000FF_080188 34 Project til Library 4 Repeat this method to add other devices Publication 1757 UMO06A EN P May 2002 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 gt Assign Or click the assign button in the toolbar The Controller Assignments window opens Controller Assignments Fie x Available Modules Selected CEE Link Information lOMs CMs SCMs Devices Select a CEE Link Assigned Modules example_cascade example_motor LINKS1 example_pid LINK52 pidloop CM86 example_scem lt Unassign CEES Statistics Show All ee Show CMs C Show Unassigned Performance I Show lOMe Memory Capacity Help fie Communication Loadd Delete 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 Click Assign to assign the selected device to the selected Link The device is added to the Assigned Devices
288. ut ROut 1 p Remote Cascade RCas 2 p Cascade Cas 3 P Automatic Auto 4 p Manual Man 5 Local Override LO 6 p Initialization Manual IMan 7 MSB Out of Service 00S Rotary Switch Model versus Toggle Switch Model The Fieldbus Foundation supports both the Rotary Switch and the Toggle Switch models of mode operation The Rotary Switch model supports only one mode request at a time For example an operator can request OOS Man Auto Cas RCas or ROut It has no memory of previous target modes The Toggle Switch model supports more than one mode request at a time For example an operator can request Manual override of Cascade Manual override of Remote Cascade and so on ProcessLogix supports the Rotary Switch model as well as the following two instances of the Toggle Switch model e An operator may request the Cas mode at the same time the RCas mode is requested e An Operator may request the Cas mode at the same time the ROut mode is requested Publication 1757 UMO06A EN P May 2002 2 22 Integrating Fieldbus into Rockwell Automation Logix System ProcessLogix also ignores the following illegal mode combinations as defined by the Fieldbus Foundation e If ROut is set RCas may not be set If it is set it will be ignored e 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 wi
289. ute 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 The following are some pertinent characteristics about this application and the corresponding ProcessLogix control strategy for reference The goal is to recycle the process fluid back to the process with a minimum swing in the recycle feed rate The tank level set point SP is 50 percent The tank level low LO alarm is 25 percent and the low low LOLO alarm is 15 percent The tank level high CHD alarm is 70 percent and the high high HIHD alarm is 85 percent The ProcessLogix control strategy includes a tank level Control Module CM named CM101 and a pump control CM named CM102 The CM101 includes a ProcessLogix Proportional Integral Derivative PID function block configured to operate as a Proportional and Integral PI two mode controller The tuning for the PI controller is loose to allow some swing in the level of fluid in the tank The CM101 includes a ProcessLogix Data Acquisition DATAACQ function block to provide the alarm flags for the LO LOLO HI and HIHI tank level alarms The CM101 includes a fieldbus Analog Input AD function block to integrate the tank level indicating signal from the ST3000FF smart pressure transmitter with the control strategy
290. vailable templates ATTENTION Exit the Control Builder application before launching the Fieldbus Library Manager utility Publication 1757 UM006A EN P May 2002 4 18 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 1 Click Start gt Programs gt ProcessLogix Engineering Tools gt Fieldbus Library Manager The Fieldbus Library Manager FLM login window opens 5 FieldbusLibraryManager Untitled File Edit wiew Help SHAR Lee AnA Bele e a ll xi Login Information BS xi User Name anr E Password o Server Name O Cancel 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 Enter your login password in the Password field You need an access level of at least Engineer to make a template See your system administrator to get your assigned password if required The password is tied to the operator security for Station Click OK Insert the DD floppy diskette into your computer s floppy drive Configurating the 1757 FIM 4 19 6 In the FLM window click File gt Open Device FieldbusLibraryManager Untitled File Edit View Help Open Device Chrl o Save Gh 5 Save Osi The Select Driver window opens Select Device E Device Release Directory release Device List 7 In the De
291. value obtained from the Transducer FF Data Type Unsigned 16 Usage C Contained Length 2 Valid Views VIEW_2 Storage Static YXXX Blocks No Y parameters LXXX Blocks No Z parameters Publication 1757 UM006A EN P May 2002 Appendix B Fieldbus Status Display Indications Table B 1 Fieldbus Status Byte Independent Status Field BAD Non Specific Bad Bad LowLimit Bad HiLimit Bad Constant Bad Contig Bad Config L Bad Config H Bad Config C Bad NotCon Bad NotCon L Bad NotCon H Bad NotCon C Bad DevFail Bad DevFail L Bad DevFail H Bad DevFail C Bad SensFail Bad SnFail L Bad snFail H Bad snFail C Bad LUValue Bad LUV L Bad LUV H Bad LUV C Bad NoComm Bad NoComm L Bad NoComm H Bad NoComm C Bad OutSvc BAD Non Specific BAD Non Specific BAD Non Specific BAD Configuration Error BAD Configuration Error BAD Configuration Error BAD Configuration Error BAD Not Connected BAD Not Connected BAD Not Connected BAD Not Connected BAD Device Failure BAD Device Failure BAD Device Failure BAD Device Failure BAD sensor Failure BAD Sensor Failure BAD sensor Failure BAD sensor Failure BAD No Comm Last Usable BAD No Comm Last Usable BAD No Comm Last Usable BAD No Comm Last Usable BAD No Comm No Last Usable BAD No Comm No Last Usable BAD No Comm No Last Usable BAD No Comm No Last Usable BAD Out Of Service No Limit Publication 1757 UMO06A EN P May 2002 B 2 Fieldbus Status Display Indications Table B 1 Fieldbus
292. ver 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 Leave all other fields with their default displays unless you have created a custom graphic and click OK 18 Repeat this procedure for each device as required to support your control strategy 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 This procedure assumes that Control Builder is running and that you have added the Control Processor CPM Control Execution Environment CEE block to the Project tab Also the following fieldbus components have been created in the Project tab using the previous procedures in this section e FIM named FIM _ Bl e Associated Links named LINK_S101 and LINK S102 e E amp H Endress Hoisers pressure transmitter named ST101 and assigned to LINK_S101 e Flowserve valve controller named LX14_101 and assigned to LINK_S101 TIP The following procedure is really intended for users who have never used Control Builder before If you gt have used Control Builde
293. vice 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 Loading Parameters for Device Pressure Transmitter Processing Block analog_input_block Processing Parameter LO LO_ALM 4B waa Publication 1757 UMO06A EN P May 2002 4 20 Configurating the 1757 FIM Publication 1757 UMO06A EN P May 2002 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 FieldbusLibraryManager HO Bile Edit view Help hd e m SU0UFF_OS01 RESOURCE Block parameters are displayed in table format on the right side of the FLM window Mm w N MN aAa eT SF ONY Yn HH He oa oof eS _ t m 22220220 02 22 ZZZzzz z FACEPLATONLY FACEPLATONLY FACEPLATONLY FACEPLATONLY FACEPLATONLY FACEPLATONLY FACEPLATONLY FACEPLATONLY OUTPUT FACEPLATONLY FACEPLATONLY FACEPLATONLY FACEPLATONLY FACEPLATONLY INPUT FACEPLATONLY FACEPLATONLY INPUT FACEPLATONLY FACEPLATONLY CACC OL ATOM Typeld Size Enm Use Dim Store 7 al b a se 09 N w m lw la l ila l lM i llui iMa of By keeping default values you may use the same template for like vendor device
294. vice on the H1 link The FIM writes the output OP to be read by fieldbus device resident blocks such as Analog Output and Proportional Integral Derivative PID through their RCAS_IN parameter input connection This connection is generally used when the downstream control block is in the RCas Remote Cascade mode This means that the fieldbus block s BKCAL_OUT parameter is written by the downstream block and read by the FIM The client server method also allows the FIM to function in a Direct Digital Control DDC mode or the Remote Out mode in fieldbus terms In this case the FIM writes the output to be read by the fieldbus PID block though its ROUT_IN parameter input connection In turn the PID block publishes the ROUT_OUT or back calculation output value for the subscribing FIM 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 The ProcessLogix control initialization indicators map only to the limited number of substatus conditions that have corresponding indications in fieldbus Good Cascade Fieldbus device Discrete Input integration A user can functionally wire the output from a Discrete Input DD function block in a
295. with the FIM LINK communicating with the system 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 In the Preset Set Addr Seq Timer T2 field either leave the default value of 1920000 or enter a new value This is the preset value for the System Management set address sequence timer in 1 32 millisecond increments In the Preset Set Addr Wait Timer T3 field either leave the default value of 480000 or enter a new value 12 13 14 15 Configurating the 1757 FIM 4 31 This is the preset value for the System Management set address wait timer in 1 32 millisecond increments In the Local Clock Time Offset CLOCTIMDIFF 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 In the App Clk Sync Interval ACSYNCINTR field either leave the default value of 5 or enter a new value See page 4 8 for more information This value is the interval in seconds between time messages on the link System management sets it during node address assignment In the Addr of Lnk Primary Time Pub PTIMEPUB field either leave the default value of 20 or enter a new value This v
296. xample 12 Double click on the device and you ll get a window like this CN2FF 10 Port 0 FR 3051 3 1D 0011513051073199080646 01 0000669 l FR 3051 3 alaa Faaa ey 2 PD_TAG DEVICE_ID NODE_ADDRESS Publication 1757 UMO06A EN P May 2002 Hel FA 3051 3 GO PO TAG help Device s physical name 00115130510731993050646 060 DEVICE_ID help Unique device identifier Fea NODE_ADDRESS help Unique device address on this link 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 You may also need to resolve Node Number conflicts if a new FF device was previously assigned a node number that another device is now using If necessary you can change the FF address of a device by right clicking on the device and selecting Set Address Then enter the desired address in the window and click Set 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
297. y use one port on the CN2FF Click OK to accept the selection we are only using one link 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 If you must connect to more than 4 Fieldbus devices at one time an additional license to support that can be arranged through Tech Support We suggest that each CN2FF be configured and saved by itself You see a similar window 2a NI FBUS Fieldbus Configuration System File Edit View Rosemount Temp Configure Window Help Ed OF Oh DEVICE Rosemount Temp Else P b omsi 3044 FR TEMP 081 O4E01D 2m LD 9 Log 7 Notes Device help Optional Double click on this enak Parameters item to open a device window Certain items like device tag and address can be H BEY Schedule edited with this window Function blacks oon Function Block Application can algo be edited with this interface 5 Li LD 9 H Device Info E Resource RB ad CHetMacld09_Al_Module0_0 CNAI 34 CHetMacld09_Al_Module1_0 CNAI ad CNetMacild09_A0_Module0_0 CNAO ad CNetMacld09_A0_Module1_0 CHAO 34 CNetMacld09_DI_ModuleO_0 CNDI ad CNetMacild09_D0_Module0_0 CNDO E JE Honeywell Attached H E Rosemount 1151 Eg 3 Rosemount Temp Publication 1757 UMO06A EN P May 2002 IMPORTANT If you are using both ports on
298. your fieldbus should automatically be assigned a network address in the range of 16 36 This MAX address is based on the setting of the First_Unpolled_Node_ID Check the address that was assigned to each device Devices which have LM Link Master capability should have addresses of 23 or higher 5 Right click on LM devices 6 Click Set Address If the address is less than 23 pick a new available address The CN2FF should be at FF address 16 If not change the address to 16 7 Select Set Tag 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 Assign a name to the block that is appropriate for your application 11 Continue this process for all the Fieldbus Devices Each time you SET a TAG and after a short delay the Set Tag window will close and you should get the following status messages on the bottom of the screen DEVICE E H Pressure Transmitter D 4527H4s61007 44Y0608 set tag succes set address success 4 Publication 1757 UMO06A EN P May 2002 F 28 1788 CN2FF Installation E

1757-UM006 - Literature Library

Contents

Download Pdf Manuals

Related Search

Related Contents