ControlNet-to-Foundation Fieldbus, H1 Linking Device
Contents
1. lt Pond DD Info Ea lt a Purl BP Door The base directory for your Device Descriptions FH Porno e nitous data Cancel This field can be blank if you do not have manufacturer specific DD info The changes made in FBCONF only Import DD Your standard text dictionary e nifbus detainifh ct Cnterthe ffo Mile Name Browse Cancel Impor DD Dialog will create subdirectories under the base directory of Device Description based on your manufacturer ID and Device Type and then copy ffo and sym file there The DD Info dialog box appears If this is the first time you have installed a device description the base directory edit box will be empty We recommend that you enter the same directory as the location of your standard text dictionary in this example e nifbus data 3 Click on Import DD The Import DD dialog box appears The path to the DD typically uses a hierarchy of directories indicating vendor ID product code and product revision Select the DD ffo file path from the support disk of the Fieldbus device NI FBUS installs the DD in the base directory that you specified 1788 6 5 1 January 1999 3 6 Software Installation and Configuration 1788 6 5 1 January 1999 Configuring Fieldbus Communication Parameters Each Fieldbus device must have a unique address within one Fieldbus network It must also have a unique physical device tag Each Fieldbus port2. gt ANEBEEE Allen Bradley ControlNet to H1 Linking Device FOUNDATION Fieldbus User Manual Cat No 1788 CN2FF Important User Information Because of the variety of uses for the products described in this publication those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements including any applicable laws regulations codes and standards The illustrations charts sample programs and layout examples shown in this guide are intended solely for purposes of example Since there are many variables and requirements associated with any particular installation Allen Bradley does not assume responsibility or liability to include intellectual property liability for actual use based upon the examples shown in this publication Allen Bradley publication SGI 1 1 Safety Guidelines for the Application Installation and Maintenance of Solid State Control available from your local Allen Bradley office describes some important differences between solid state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication Reproduction of the contents of this copyrighted publication in whole or part without written permission of Rockwell Automation is prohibited Throughout this manua
3. 7 Timeout ns fono In the Interface Type field choose the ControlNet radio button The utility displays the ControlNet network address and path to the selected linking device In the Driver field type the driver name that RSLinx uses to communicate with your ControlNet PC interface The default driver AB_KTC 1 uses an Allen Bradley 1784 KTC15 interface card In the Network Address field enter the ControlNet node number of the linking device you are configuring In the of Ports field select the number of Fieldbus ports that matches the linking device 1788 6 5 1 January 1999 3 4 Software Installation and Configuration 1788 6 5 1 January 1999 In the Path field enter 02 the default path indicating NI FBUS uses the ControlNet port on an Allen Bradley PC ControlNet interface card The path is compromised of ASCII encoded hexadecimal bytes separated by spaces required to reach the destination linking device In the Timeout field specify a timeout in milliseconds for communication with the linking device The default value is most likely adequate However if you encounter communication errors increasing the timeout may solve the problem If you want to accept these settings to communicate with the listed linking device choose Add if you want to abort these settings choose Cancel Repeat steps 1 through 8 for each linking device in your system Configuring the Interface
4. install a new device description click on Import DD and follow the instructions Testing the Installation Software Installation and Configuration 3 7 Make sure that you have installed and configured the RSLinx software and an Allen Bradley PC ControlNet interface The NI FBUS Configurator requires these components to interact with the linking device To make sure that your NI FBUS software is correctly installed and is working properly follow these steps 1 Restart Windows NT 2 Start the NI FBUS Communications Manager by selecting the NIFB icon in the NI FBUS menu On successful startup NI FBUS displays a message saying that NIFB started up successfully and the title bar of the window changes to NIFB running 1788 6 5 1 January 1999 3 8 Software Installation and Configuration Notes 1788 6 5 1 January 1999 Blocks in the Linking Device Chapter 4 Using the 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 perform either analog input analog output
5. of the linking device is considered a Fieldbus device Therefore each Fieldbus port must have its own address and tag The linking device is shipped with all the Fieldbus ports set to the default address and without any physical device tag You must assign a tag and address to a port before using it to communicate with other Fieldbus devices connected to the Fieldbus network Use the NI FBUS Configurator to do this See the sections on setting tags and addresses in the NI FBUS Configurator User Manual publication 1788 6 5 2 Using the NI FBUS Interface Configuration Utility After Installation You should use the NI FBUS interface configuration utility after installation to e add or remove a linking device e change the software settings to match the linking device settings e view or change the software settings The NI FBUS interface configuration utility prompts you to provide the following information e Hardware information number of linking devices ControlNet network address of each linking device path to each linking device e Logical name for each Fieldbus port you can use this information to access the port using the logical name e Device Description DD information base directory to store your DD information location of the standard text dictionary If you change the base directory or location of the standard text dictionary you must copy all the DDs from the old base directory to the new one To
6. 2 They indicate the state of the ControlNet connected to the BNC connectors These LEDs do not reflect anything about the status of the network if the linking device is connected to the network through the network access port NAP If more than one state is present the LEDs always reflect the highest priority status present on the network Table 2 B describes the LED states and the priority of each status Table 2 B Description of ControlNet Network Status LED States LED State Priority How to View Cause Both steady off 1 Reset or no power highest Both steady red 2 Failed to link interface to ControlNet View together Alternating red amp green 3 Self testing Alternating red 4 Bad node configuration such as duplicate ControlNet network address Steady off 5 Channel disabled or not supported Flashing red amp green 6 Invalid link configuration Flashing red 7 View Link fault or no frames received independently Flashing green 8 Temporary channel error or listen only Steady green 9 Normal operation lowest Fieldbus Network Status LEDs Each Fieldbus port on the linking device has an LED to indicate the functional states of the port Table 2 C describes each state Table 2 C Description of Fieldbus Network Status LED States LED State Meaning Off Fieldbus port not receiving packets Steady green Fieldbus port is alive as Link Active Scheduler Flashin
7. 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 bit position once it is read as a 1 1788 6 5 1 January 1999 4 12 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device Discrete Outputs 1788 6 5 1 January 1999 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 a number of MDO block instances 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 CNetMacldxx_DO_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 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 t
8. Configuration 4 7 Sample Multiple Macrocycle MAI Configuration 4 3 Sample NI FBUS Configurator View of ControlNet Object Information 4 17 Sample Non Cascade AO Configuration 4 6 Sample Single Macrocycle MAI Configuration 4 2 Sample Single Macrocycle MDI Configuration 4 9 service pack 3 1 3 Setting the ControlNet Network Address 2 5 Setting Up an Alarm 4 14 Specifications A 1 System Requirements 1 3 T Testing the Installation 3 7 Trends and Alarms 4 18 Typical Linking Device Connections to a ControlNet Network 2 3 U Using the ControlNet to FOUNDATION Fieldbus Linking Device 4 1 Using the NI FBUS Interface Configuration Utility After Installation 3 6 V Viewing Object Information in the NI FBUS Configurator 4 16 wW Windows NT 4 0 1 3 AB Allen Bradley vr Publication Problem Report If you find a problem with our documentation please complete and return this form Pub Name ControlNet to Foundation Fieldbus H1 Linking Device User Manual Cat No 1788 CN2FF Pub No 1788 6 5 1 Pub Date January 1999 PartNo 955133 78 Check Problem s Type Describe Problem s Internal Use Only L Technical Accuracy C text _ illustration L Completeness _ procedure step C illustration _ definition C info in manual What information is missing _ example C guideline _ feature accessibility C explanation C other C info not in L Clarity What is uncle
9. January 1999 Alarm Handling by the HMI 4 14 Assembly ODjectss 4 654 vos an 4 14 MAI Bloks 23a HH ee 4 15 MAO BIOCKS LEE sit ape re 4 15 MIITBIOCKS ne Me ted A er ER a EL Fr 4 16 MDO Blocken na ee 4 16 Viewing Object Information in the NI FBUS Configurator 4 16 Changing the Linking Device Configuration 4 17 Trends and Alarms aus rn 4 18 Specifications 1788 6 5 1 January 1999 Chapter 1 Product Overview Introduction The ControlNet to FOUNDATION Fieldbus linking device connects a ControlNet network with one or more FOUNDATION Fieldbus Hl 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 Figure 1 1 shows these functions within a simple ControlNet system Figure 1 1 Linking Device Function within a Simple ControlNet System Engineering Fieldbus PLC Operator Configuration and Configurator HMI Interface Monitoring ControlNet Closed Loop Control Linking Link
10. alarm related bits as shown in Figure 4 3 Analog Outputs Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 5 Figure 4 3 Alarm Attribute Definition Bit Position RARE BE 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 bit position once it is read as a 1 This section describes co
11. ControlNet e RSLinx 2 0 or RSLinx OEM 2 0 or later this is the driver for the Allen Bradley PC interfaces RSLinx Lite is not sufficient e RSNetWorx for ControlNet version 1 8 or later this is the ControlNet configuration tool 1788 6 5 1 January 1999 1 4 Introduction Linking Device Hardware Description 1788 6 5 1 January 1999 Compatibility Information The linking device is compatible with ControlNet specification version 1 03 or later and Fieldbus specification version 1 3 Figure 1 2 shows the components of the linking device Figure 1 2 ControlNet to FOUNDATION Fieldbus Linking Device Case Enclosure 5 DIN Rail Clip Network Address 6 Fieldbus Status LEDs Switches under cover 7 ControlNet BNC Connectors ControlNet Module 8 ControlINet Network Access STATUS LED Port NAP ControlNet Network Status 9 Fieldbus Connectors LEDs 0 Power Supply Connector on The linking device is designed to be mounted on a 35 mm DIN rail It has one ControlNet port with support for redundant media and a network access port The ControlNet status LEDs on the front of the linking device display the current status of each of the redundant media channels The rotary switches are used to set the ControlNet network address You can write the network address in the space provided on front ofthe device The linking device has two separate Fieldbus ports Next to each port is an LED to display the curr
12. I object has the attributes and access rules shown in Table 4 C Table 4 C ControlNet Discrete Input Object Attributes Attribute Number Name Type Access Initial Value Remarks 3 Value Boolean Get 0 4 CNStatus Boolean Get Bad ControlNet status 0 Good 1 Bad 150 Ffstatus uint8 Get Bad Out of Service Fieldbus status of the value obtained 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 0 See Alarm Handling for Discrete Inputs All attributes in Table 4 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 corr
13. L_OUT_D parameter of the DO block to BKCAL_INn 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 DO is associated with CN OUT D0 CN_BKCAL_IN DI with CN OUT _DI 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 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 4 D Table 4 D ControlNet Discrete Output Object Attributes Attribute Number Name Type Access Initial Value Remarks 3 Value Boolean Set 0 This is written from the ControlNet side 4 CNStatus Boolean Set Bad ControlNet status 0 Good 1 Bad 6 FailStateValue uint8 Set 0 The linking device writes the value to the DO block when this attribute is changed by the controller 151 TagDesc String Get As configured Tag of the Fieldbus function block that this object instance represents 152 FailstateTime Float Set 0 The linking device writes the value to the DO block when this attribute is changed by the controller 153 ReadBack uint8 Get 0 This represents the BKCAL_ OUT _D valu
14. Name To configure the interface name follow these steps 1 To change the interface name of a Fieldbus in a linking device click on the port icon and click on the Edit button The interface configuration utility displays the current port configuration Interface Name MENECER Device Tag Cancel type Fixed Device Address Default Visitor Usage ce NI FBUS Bus Monitor 2 Enter the logical interface name for the port in this dialog The logical interface name must be unique within a PC but the same linking device may be referenced by different interface names in different PCs Software Installation and Configuration 3 5 Installing Device Descriptions Device descriptions describe functionality of Fieldbus devices using the Fieldbus Device Description Language Device Descriptions must be provided to NI FBUS for all attached Fieldbus devices NI FBUS includes many standard DDs Most devices contain custom functionality therefore you should install the DD for all attached Fieldbus devices The linking device is shipped with the Linking Device Setup disk containing its device description To install device descriptions follow these steps 1 Insert the disk in an unused drive 2 Click on the DD Info button in the NI FBUS Interface Configuration Utility screen NI FBUS Interface Configuration Utility 2 3 Za N FBUS OK SSP Boardo DU Into
15. TION Fieldbus H1 Linking Device 1788 6 5 1 January 1999 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 output 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 Config
16. The right two V terminals are connected in the linking device These connections are indicated on the power connector by the lines over the V and C terminals There are two types of ControlNet connectors on the linking device The BNC connectors are for direct connection to a ControlNet network through a tap The BNC connectors must be used to connect the linking device to the ControlNet network The RJ 45 connector is a network access port NAP This port is only for temporary connections to a ControlNet network Figure 2 2 shows an example of a typical network connection Important Do not connect the linking device to more than one ControlNet network at a time Attempting to connect to a second network will cause the linking device to operate erratically Figure 2 2 Typical Linking Device Connections to a ControlNet Network Linking Device ControlNet Device BER O gt p m ons ons TE ME h MEY aap E a _ AN jf ME REZ O ee ill ControlNet Device 1788 6 5 1 January 1999 2 4 Hardware Installation and Configuration Connecting to The location of the Fieldbus connectors is shown in Figure 2 3 the Fieldbus Network Figure 2 3 Fieldbus Connectors on the Linking Device Fieldbus Connectors If you want to make your own Fieldbus cable make sure that it uses pins 6 an
17. ar _ Sequence What is not in the right order _ Other Comments Use back for more comments Your Name Location Phone Return to Marketing Communications Allen Bradley 1 Allen Bradley Drive Mayfield Hts OH 44124 6118Phone 440 646 3176 FAX 440 646 4320 Publication ICCG 5 21 August 1995 PN 955107 82 PLEASE FASTEN HERE DO NOT STAPLE Other Comments PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE 62 Rockwell Automation Allen Bradley 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE www rockwellautomation com Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1788 6 5 1 January 1999 PN 955133 78 1999 Rockwell International Corporation Printed in the U S A
18. atus uint8 Get Bad Out of Fieldbus status of the value obtained from the Service Fieldbus device 151 TagDesc String Get As configured Tag of the Fieldbus function block that is represented by this object instance All attributes in Table 4 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 and Confirmed after the condition causing the alarm is corrected When the function block detects the alarm condition is no longer present the alarm is said to be CLEARED The CLEARED state must be Confirmed when it is detected Users of the LD use the alarm attributes to process Fieldbus alarms Each attribute corresponding to a process alarm has the three
19. d 7 for the Fieldbus signals as specified in the Fieldbus Standard for Use in Industrial Control Systems Part 2 ISA S50 02 1992 Refer to Figure 2 4 for the connector pinout of the linking device Figure 2 4 Fieldbus Connector Pinout for the Linking Device 2 22 2 Z OQ QO Oy Q ejeq ejeq ON ON NC No Connection 1788 6 5 1 January 1999 Setting the ControlNet Network Address Hardware Installation and Configuration 2 5 Valid ControlNet network addresses are 1 99 Network address zero is reserved Switch 1 controls the most significant decimal digit the tens Switch 2 controls the least significant decimal digit the ones Figure 2 5 shows the location of the network address switches and an example of switch settings for a network address of 15 Figure 2 5 ControlNet Network Address Switches Set to 15 mee ITH Switch Cover Removed tens ones KZ 3 z KZ 3 z on Oeil on 1788 6 5 1 January 1999 2 6 Hardware Installation and Configuration Interpreting the LEDs 1788 6 5 1 January 1999 Follow these steps to set the ControlNet network address for the linking device For optimum throughput assign network addresses to your ControlNet nodes in a sequential order starting
20. 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 MAI 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 1788 6 5 1 January 1999 4 2 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device Analog Inputs 1788 6 5 1 January 1999 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 a number of MAI block instances Each instance of the MAI block is the software equivalent of an analog input module in an I O subsystem Each MAI block has eight chan
21. e from the DO block 154 BkCalStatus uint8 Get Bad Not This represents the status of the Readback Connected attribute 155 casinstatus uint8 Set Bad Not This represents the status of the CAS_IN_D to connected the DO block Note that 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 aBKCAL_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 1788 6 5 1 January 1999 4 14 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device Alarm Handling by the HMI Assembly Objects 1788 6 5 1 January 1999 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 4 10 Figure 4 10 Setting Up an Alarm Functi
22. e Input Objects 4 10 Index ControlNet Discrete Output Object Attributes 4 13 ControlNet Discrete Output Objects 4 13 ControlNet Network Address Switches Set to 15 2 5 ControlNet Network Status LEDs 2 7 custom function blocks 1 2 D Description of ControlNet Network Status LED States 2 7 Description of Fieldbus Network Status LED States 2 7 Discrete Inputs 4 8 Discrete Outputs 4 12 F Fieldbus Connector Pinout for the Linking Device 2 4 Fieldbus Connectors on the Linking Device 2 4 Fieldbus Network Status LEDs 2 7 G Glossary G 1 H Handling the Linking Device 2 1 Hardware 1 3 Hardware Installation and Configuration 2 1 Installing Device Descriptions 3 5 Installing the Linking Device 2 1 Installing the NI FBUS Configurator Software 3 1 Interface Configuration Utility 3 2 Interpretation of ControlNet Module STATUS LED 2 6 Interpreting the LEDs 2 6 Introduction 1 1 L Linking A 1 1788 6 5 1 January 1999 1 2 Index 1788 6 5 1 January 1999 M MAI Blocks 4 15 MAO Blocks 4 15 MDI Blocks 4 16 MDO Blocks 4 16 Module STATUS LED 2 6 N network access port NAP 2 3 NI FBUS Configurator version 2 3 1 3 P Power Connector Pinout 2 2 Product Overview 1 1 R Removing the Linking Device 2 2 RJ 45 connector 2 3 RSLinx Lite 1 3 RSLinx OEM 2 0 1 3 RSLinx 2 0 1 3 RSNetWorx 1 3 RSNetWorx for ControlNet 1 3 S Sample Cascaded AO Configuration 4 7 Sample Multiple Macrocycle AO
23. e Limit 1 S x 2 9 Ir Ar 2 ai Loop Time 1 sec Stale Limit 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_AS and not use any of the others As shown in the lower loop of Figure 4 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 MAI block is not limited to interfacing with AI function blocks 1788 6 5 1 January 1999 4 4 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 1788 6 5 1 January 1999 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 4 A Table 4 A ControlNet Analog Input Object Attributes Attribute Number Name Type Access Initial Value Remarks 3 Value Float Get 0 4 CNStatus Boolean Get Bad ControlNet status 0 Good 1 Bad 107 LoFlag uint8 Get Set 0 See Alarm Handling for Analog Inputs 108 HiFlag uint8 Get Set 0 See Alarm Handling for Analog Inputs 109 LoLoFlag uint8 Get Set 0 See Alarm Handling for Analog Inputs 110 HiHiFlag uint8 Get Set 0 See Alarm Handling for Analog Inputs 150 FFst
24. e STATUS LED s csi v5 6 wu aaa 2 6 ControlNet Network Status LEDs 2 7 Fieldbus Network Status LEDs 2 7 Installing the NI FBUS Configurator Software 3 1 Configuring the NI FBUS Configurator Software 3 3 Configuring the Interface Address 3 3 Configuring the Interface Name 3 4 Installing Device Descriptions 3 5 Configuring Fieldbus Communication Parameters 3 6 Using the NI FBUS Interface Configuration Utility After Installation nass ads a 3 6 Testing the Installation u 2 ea ea ea el 3 7 Blocks in the Linking Device 4 1 Analog INPUIS lt 2 4505 08 ates eek ar 4 2 Configuration of Analog Inputs 4 2 ControlNet Analog Input Objects 4 4 Alarm Handling for Analog Inputs 4 4 Analog ORDNEN ant NT ce de E aa 4 5 Configuration of Analog Outputs 4 5 ControlNet Analog Output Objects 4 8 Discrete Inpuls Le es bee te dei tes 4 8 Configuration of Discrete Inputs 4 9 ControlNet Discrete Input Objects 4 10 Alarm Handling for Discrete Inputs 4 10 Discrete Outputs on Dr ae it 4 12 Configuration of Discrete Outputs 4 12 ControlNet Discrete Output Objects 4 13 1788 6 5 1
25. ected When the function block detects the alarm condition is no longer present the alarm is said to be CLEARED The CLEARED state must be Confirmed when it is detected Users of the LD use the alarm attributes to process Fieldbus alarms Each attribute corresponding to a process alarm has the three alarm related bits as shown in Figure 4 8 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 11 Figure 4 8 Alarm Attribute Definition Bit Position 7 6 5 ala 2 1 0 gt Value 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
26. ement de Classe 1 Division 2 Le code de temp rature est indiqu sur l tiquette produit Code de temp rature CLI DIV 2 GP A B C D TEMP Le code de temp rature est indiqu ici D B Les avertissements suivants s appliquent aux produits certifi s pour une utilisation en environnements dangereux DANGER Risque d explosion e La substitution de composants peut rendre cet quipement inadapt une utilisation en environnement de Classe 1 Division 2 e Couper le courant ou s assurer que l environnement est class non dangereux avant de remplacer des composants e Couper le courant ou s assurer que l environnement est class non dangereux avant de d brancher l quipement e Couper le courant ou s assurer que l environnement est class non dangereux avant de d brancher les connecteurs Fixer tous les connecteurs fournis par l utilisateur pour se brancher aux circuits externes de cet quipement l aide de vis loquets coulissants connecteurs filet s ou autres de sorte que les connexions r sistent une force de s paration de 15 newtons 1 5 kg 3 4 Ib appliqu e pendant au moins une minute 1788 6 5 1 January 1999 Glossary We use these abbreviations acronmys and initialisms throughout the document AI Analog Input AO Analog Output CH Channel DD Device Description DI Discrete Input DO Discrete Output Fieldbus FOUNDATION Fieldbus Hl H1 31 25 Kb
27. ent status ofthe port The status LED indicates ifthe device is powered on and operating properly The power connections are used to supply power to the linking device For more information on connecting and configuring the linking device see chapter 2 Hardware Installation Introduction 1 5 NI FBUS Configurator Software Use the NI FBUS Fieldbus Configurator to configure a Fieldbus network and keep track of your configurations The Configurator is an easy to use graphical environment for creating Fieldbus linkages loops and schedules Description Figure 1 3 shows the Configurator Main window For more information refer to the NI FBUS Configurator User Manual publication 1788 6 5 2 Figure 1 3 NI FBUS Configurator Main Window dilavet Log Notes 3 Network Parameters EE Schedule 3 Function Block Application D amp ALL BLOCKS ID NIC ALL BLOCKS amp Analog nput Al E EI BiasGain BG EI EontrolSelector CS E ML MI El Discretelnput DI DiscreteDutput DO Pdfnntral PD PidCantral PID RatinCantral R ResourceBlock RB a AOPID ID NIC AOPID AOIAQ PID PID BI AOPID resource block RB gt a Devi ID NIC ATFBUS001 3 8 Test Al ID NIC Al E ALA E ai resource block RB BLOCK RatioControl open block success read block attributes success free attributes success BLOCK AnalogOutput open block success read block attributes success Analog Outp
28. erent rates of publishing on Fieldbus you must choose different MAO blocks as shown in Figure 4 6 Figure 4 6 Sample Multiple Macrocycle AO Configuration Function Block Applicat Loop Time 1s Stale Limit K Kiel Sal la 2 amp Loop lime 1 sec Stale Laut 1 PCH BECAL IN 41 NAO PCN BKCAL IN 45 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 1788 6 5 1 January 1999 4 8 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device That is you may use channels CN_OUT_A3 and CN OUT AS and not use any of the others As shown in the lower loop of Figure 4 6 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 ControlNet AO object has the attributes and access rules shown in Table 4 B Table 4 B ControlNet Analog Output Object Attributes Attribute Number Name Type Access Initial Value Remarks 3 Value Float Set 0 This is written from the ControlNet side 4 CNStatus Boolean Set Bad ControlNet status 0 Good 1 Bad 11 Fa
29. g red and green Fieldbus port is seeing traffic but is at a default or visitor address Flashing red Fieldbus port encountered transient non fatal network error Steady red Fieldbus port encountered fatal network error 1788 6 5 1 January 1999 2 8 Hardware Installation and Configuration Notes 1788 6 5 1 January 1999 Installing the NI FBUS Configurator Software Chapter 3 Software Installation and Configuration After you have configured and installed the linking device you are ready to install the NI FBUS Configurator software Complete the following steps to install the NI FBUS Configurator software 1 Determine the ControlNet network address of the linking device or devices from rotary address switches Refer to Figure 2 5 2 Using Windows NT log in as Administrator or as a user that has administrator privileges 3 Insert installation diskette 1 into an unused drive 4 Run Add Remove Programs from the control panel or select Start gt Run and type x setup where x is the letter of the drive containing the installation diskette usually a or b The interactive setup program takes you through the necessary steps to install the software By default the installation program installs the software in the nifbus directory You can change the directory if you want to install the NI FBUS software into a different directory The installation program copies nifb d11 and drvint dl1 into your W
30. he MDO function blocks in the linking device You must connect the Fieldbus DO function blocks that will be controlled by the ControlNet controllers or devices to the MDO channels The MDO function block has two valid configurations In the first configuration the BKCAL OUT D parameter of the DO is not connected back to the controller In this case there is no mode handshake provided by the upstream controller for cascade initialization of the DO You connect only the CN_OUT_Dx parameter from the MDO to the CAS_IN_D of the DO block In this case you must not connect the BKCAL OUT D parameter of the DO to the BKCAL_INn parameter of the MDO block Figure 4 9 Sample Cascade DO Configuration Function Dlock Applicati Loop Time 1s Stale Limit N E al Sal Al 32 CNetMacld03_DO_ModuleO_1 CHDO CN EKCAL IN DO 34 DiscreteOutput DO gt CN BKCAL IN Di CN OUT DI CAS IN D Ben D CN BKCAL IN D2 CN OUT DR DO Aharas BP CH BECAL IN Da A CH OUT D4 E Trends Be CN BKCAL IN D CN OUT D5 J gt CN OUT DO Be CN RKCAT IN NA CN ONT DA D PCN BECAL IN D7 CN OUT De Alarms gt Trends gt Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 13 In the second configuration shown in Figure 4 9 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 BKCA
31. he software equivalent 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 j where xx is the ControlNet network address i is the Fieldbus channel number and j 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 4 7 The remaining configuration is similar to that for the analog inputs Figure 4 7 Sample Single Macrocycle MDI Configuration Function Block Application Loop Time 1 9 sec Stale Limit 1 1 DI DD E CNethfacld03_DI_Module0_0 CNDI OUT D CN DO Alans DI Aum ENDI Trends pe Trends De Be CR D2 CEE ECN D Bands ECN D6 E CN D7 CNDI 1788 6 5 1 January 1999 4 10 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 1788 6 5 1 January 1999 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 D
32. idity 5 to 90 non condensing Vibration Operating 2Gs each axis Tested 2Gs 10 500 Hz per IEC 68 2 6 Communication ControlNet redundant media and network access port FOUNDATION Fieldbus H1 2 independent channels LAS on both channels Time Master on both channels Power Requirements 11 30V dc 270 mA 24V de typical Indicators Module Status Fieldbus Status 1 each channel ControlNet Status 1 each connection Connectors ControlNet BNC connectors Network Access Port RJ45 Fieldbus 9 pin sub D connectors Conductors Wire Size Category Category 2 Mounting 35 mm DIN rail ControlNet Channel Selection two 10 position rotary switches Agency Certification when product is marked U e Information Technology Equipment e Industrial Control Equipment e Class Div 2 Groups A B C D Hazardous Location ce e EN 50082 1 2 e EN 55022 Radiated Emission Class B e EN 61131 2 FCC Part 15 SubPart B 1 Refer to the Industrial Automation Wiring and Grounding Guidelines for Noise Immunity publication 1770 4 1 1788 6 5 1 January 1999 A 2 Specifications Compliance to European Union Directives 1788 6 5 1 January 1999 If this product has the ce marking it is approved for installation within the European Union and EEA regions It has been designed and tested to meet the following directives EMC Directive This product is tested to mee
33. ilStateValue Float Set 0 The linking device writes the value to the AO block when this attribute is changed by the controller 151 TagDesc String Get As configured Tag of the Fieldbus function block that this object instance represents 152 FailstateTime Float Set 0 The linking device writes the value to the AO block when this attribute is changed by the controller 153 ReadBack Float Get 0 This represents the BKCAL_OUT value from the AO block 154 BkCalStatus uint8 Get Bad Not This represents the status of the Readback Connected attribute 155 casinstatus uint8 Set Bad Not This represents the status of the CAS_IN to the connected AO block Discrete Inputs 1788 6 5 1 January 1999 Note that 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 aBKCAL_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 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 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 9 The linking device contains a number of MDI block instances Each instance of the MDI block is t
34. indows directory and adds information to the Windows NT registry 1788 6 5 1 January 1999 3 2 Software Installation and Configuration After installing the software components to the appropriate directories the installer starts the NI FBUS Interface Configuration Utility as shown in Figure 3 1 To reach this program after initial installation click on the Windows Start icon point to Programs point to National Instruments FBUS and select Interface Config Figure 3 1 Interface Configuration Utility NI FBUS Interface Configuration Utility 2 3 x NI FBUS Sa Board0 DD Info lt Port Add Interface Device lt Port Board Porto The changes made in FBCOMF only takes effect after you start NI FBUS process the nexttime 1788 6 5 1 January 1999 Configuring the NI FBUS Configurator Software Software Installation and Configuration 3 3 Configuring the Interface Address To add view or change the interface address of the linking device complete the following steps 1 In the NI FBUS Interface Configuration Utility window select the icon for the linking device you want to change and click on the Edit button If you are adding a linking device click on the Add Interface Device button The Interface dialog box appears Interface x InterfaceType CISA Add C PCMCIA ge Cl 3 Driver AB KTCH 4 Network Address 5 of Ports fi 6 Path fe
35. ing Device Device H1 H1 H1 H1 AI Le Ae Le AO PID PID AO PID Closed loop Control The linking device basically permits closed loop control between the Fieldbus devices and ControlNet controllers ControlNet PLC processors can access data and control Fieldbus devices such as pressure transmitters and valves As an example a PID executing on a ControlNet PLC processor can get process values from a Fieldbus pressure transmitter and control the position of a Fieldbus valve 1788 6 5 1 January 1999 1 2 Introduction 1788 6 5 1 January 1999 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 perform one of these functions analog input AJ analog output AO discrete input DI discrete output DO The linking device models the I O modules in software The linking device has four types of custom function blocks multiple AI block multiple AO block multiple DI block multiple DO block Each of these function blocks has multiple channels These function blocks are similar to the I O modules in the I O subsystem Each channel of these custom blocks is associated with an analog discrete input or output value in a Fieldbus device You establish the association when you configure the system The linking device creates a ControlNet object analog input analog output discrete input or discrete output f
36. l we use notes to make you aware of safety considerations ATTENTION Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attention statements help you to e identify a hazard e avoid a hazard e recognize the consequences Important Identifies information that is critical for successful application and understanding of the product Allen Bradley is a trademark of Rockwell Automation Introduction Hardware Installation and Configuration Software Installation and Configuration Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device Table of Contents PrOdUCE Overview ode tak alee aa 1 1 Closed loop Control ess ae 1 1 Configuration and Monitoring 1 2 System Requirements es Less er late ne nas 1 3 Hardware usa ea Beni 1 3 DS OLIW ALG see 1 3 Compatibility Information 1 4 Linking Device Hardware Description 1 4 NI FBUS Configurator Software Description 1 5 Handling the Linking DEVICE ana ca nated al 2 1 Installing the Linking Device ce a 2 1 Removing the Linking Devices at ar a a 2 2 Connecting POWeL a la ea er 2 2 Connecting to the ControlNet Network 2 3 Connecting to the Fieldbus Network 2 4 Setting the ControlNet Network Address 2 5 Interpreting the LEDER 2 6 Modul
37. lowing information becomes a part of the product literature for this certified industrial control product e This equipment is suitable for use in Class Division 2 Groups A B C D or non hazardous locations only e The products having the appropriate markings that is Class I Division 2 Groups A B C D are certified for use in other equipment where the suitability of combination that is application or use is determined by the local authority having jurisdiction Important Due to the modular nature of a programmable control system the product with the highest temperature rating determines the overall temperature code rating of a programmable control system in a Class Division 2 location The temperature code rating is marked on the product label as shown Temperature code rating CLI DIV2 GP A B C D TEMP Look for temperature code rating here The following warnings apply to products having certification for use in hazardous locations ATTENTION Explosion hazard e Substitution of components may impair suitability for Class Division 2 e Do not replace components unless power has been switched off or the area is known to be non hazardous e Do not disconnect equipment unless power has been switched off or the area is known to be non hazardous e Do not disconnect connectors unless power has been switched off or the area is known to be non hazardous Secure any user supplied connectors that mate t
38. nels with each channel containing a float and a status pair The linking device assigns a tag to each MAI block in the form CNetMacldxx AI 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 4 1 Figure 4 1 Sample Single Macrocycle MAI Configuration Function Block Application Loop Time 1 sec Stale Limit 1 K f A E AI 101 3 AD Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 3 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 ControlNet you must choose different MAI blocks as shown in the Figure 4 2 Figure 4 2 Sample Multiple Macrocycle MAI Configuration Function Block Application Time 600 ms Stal
39. nfiguration 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 a number of MAO block instances 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 blocks The linking device assigns a tag to each MAO block in the form CNetMacldxx AO Modulei j where xx is the ControlNet network address i is the Fieldbus channel number and j is the module or instance number Configuration of Analog Outputs The NI FBUS Configurator lists all the devices and the function blocks in each device in its browse window 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 1788 6 5 1 January 1999 4 6 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 1788 6 5 1 January 1999 2 BETA NI FBUS Fieldbus Configuration System ver 2 3 Node 8 Function Block Application DD File Edt View Configure Zoom Wind
40. o external circuits on this equipment by using screws sliding latches threaded connectors or other means such that any connection can withstand a 15 Newton 3 4 Ib separating force applied for a minimum of one minute 1788 6 5 1 January 1999 A 4 Specifications Approbation d utilisation en environnements dangereux Ce produit est certifi pour une utilisation g n rale aussi bien que pour une utilisation en environnements dangereux La certification en vigueur est indiqu e par l tiquette produit et non par des indications dans la documentation utilisateur Exemple d tiquette de certification d un produit Pour satisfaire la certification en environnements dangereux les informations suivantes font partie int grante de la documentation des produits de commande industrielle certifi s e Cet quipement ne convient qu une utilisation en environnements de Classe 1 Division 2 Groupes A B C D ou non dangereux e Les produits portant le marquage appropri c est dire Classe 1 Division 2 Groupes A B C D sont certifi s pour une utilisation avec d autres quipements les combinaisons d applications et d utilisation tant d termin es par le bureau local d inspection qualifi Important De par la nature modulaire des syst mes de commande programmables le produit ayant le code de temp rature le plus lev d termine le code de temp rature global du syst me dans un environn
41. on Block Applicati Loop Time 1s Stale Limit R J ke 24 PidC ontrol PID Pin ex cas IN DKCAL OUTP CN FF Linking Device DEERCAL IN Alas De Alums TRK IN D Trends gt Be Trends PTRK VAL PFF 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 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 ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 15 Table 4 E describe
42. or every channel that is associated with a Fieldbus device In summary the linking device makes the function blocks in Fieldbus devices visible as ControlNet objects on the ControlNet ControlNet devices and controllers can access the Fieldbus devices as though they are ControlNet devices The function blocks in Fieldbus devices have contained parameters and I O parameters Contained parameters are mainly used to configure the function blocks I O parameters are used in distributed control of the process These parameters are made visible as attributes of the ControlNet objects The linking device publishes and subscribes to the I O parameters on the Fieldbus network and consumes and produces the corresponding ControlNet object attributes on the ControlNet as assembly objects The linking device can be Link Active Scheduler LAS on all of the connected Fieldbus networks Configuration and Monitoring The linking device permits the NI FBUS Fieldbus Configurator on a PC connected to ControlNet to configure Fieldbus devices as if the configurator were directly connected to the Fieldbus network Fieldbus devices have a physical address a physical device tag and function block tags They also have schedules for function block execution information on connections between function blocks and so on All of these are configurable System Requirements Introduction 1 3 The Fieldbus devices have View objects that are a collection of dynamic proces
43. ow Help l x The MAO function block has two valid configurations In the first configuration the BKCAL OUT parameter of the AO is not connected back to the controller In this case there is no mode handshake provided by the upstream controller for cascade initialization of the AO You connect only the CN OUT_Ax parameter from the MAO to the CAS IN of the AO block as shown in Figure 4 4 In this case you must not connect the BKCAL OUT parameter of the AO to the BKCAL_INn parameter of the MAO block Figure 4 4 Sample Non Cascade AO Configuration om p SE TE rm tr fume ol 2 0 Su aeae a aD Node 8 g Function Block Application 44 FNetMacldNN_DN_Madulen_N CNDN BON NKCAT IN AI CN ONT Al ISKCAL OUT Ra Honeywell RECN DKCAL IN A2 CN OUT A2 ee 4 34 AI DFFN2DG AI RECN UKCAL IN A3 CH OUT AI oe Trende SMAN FIN Log Notes Network Paaneters OM Schedule CN FF Linking Device E Device lr o 3d CNctMacld08 Al ModulcO 0 CNAI 34 CNetMachi8_A1_Modube1_N CNAI Tj CNetMacld0S AO Modued 0 CNAD 34 CNetMachin8_AN_Mudule 1_1 CNAN 4 CNetMacid08 DI ModuleO 0 CNDI 34 CNetMacld08_AO_Module0_0 CNAO Sy AO 1 Ad PCN RKCAL IN Af CN OUT AN 3 PID DEFB206 PID ICN BKCAL IN Aa CN OUT AS PCN EKCAL IN EX CN OUT AS gt PCN BKCAL IN A6 CN 4 CN EKCAL IN AT CN OUT 47 gt Alarme gt Trends fe 2j AO Hi AO 34 SMAN AO 2 AO J SMAR AO 13 A0 34 SMAN PIC PID 24 Ari
44. pe Valve 54 AO Module0_0 0 1 CHYALUE D 4 CHFLOAT CHSTATUS 4 1 CHBOOL FFCASINSTATUS 5 1 CHUSINT Valve 7 AQ Modulef_0O 1 2 oa CHVALUE 6 4 CHFLOAT CHSTATUS 10 1 CHBOOL FFCASINSTATUS 11 1 CHUSINT Drive 11 AQ Modulef_0O 2 3 CHVALUE 12 4 CHFLOAT TATUS 16 1 CHROOL FFCASINSTATUS 1 1 CHUSINT SEE Donna EME q F Ready 1 14 PM 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 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 existing instances of ControlNet objects and assembly offsets are unchanged 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 1788 6 5 1 Januar
45. ps Fieldbus HMI Human Machine Interface MAI Multiple Analog Input MAO Multiple Analog Output MDI Multiple Discrete Input MDO Multiple Discrete Output PID Proportional Integral Derivative PLC Programmable Logic Controller 1788 6 5 1 January 1999 G 2 Notes 1788 6 5 1 January 1999 Numerics 11 30V dc power supply 2 2 1784 KTCX15 1 3 1784 PCC 1 3 A Alarm Handling by the HMI 4 14 Alarm Handling for Analog Inputs 4 4 Alarm Handling for Discrete Inputs 4 10 Analog Inputs 4 2 Analog Outputs 4 5 Assembly Objects 4 14 Attributes in Input and Output Assemblies 4 15 B Blocks in the Linking Device 4 1 C Changing the Linking Device Configuration 4 17 Closed loop Control 1 1 Compatibility Information 1 4 Configuration and Monitoring 1 2 Configuration of Analog Inputs 4 2 Configuration of Analog Outputs 4 5 Configuration of Discrete Input 4 9 Configuration of Discrete Outputs 4 12 Configuring Fieldbus Communication Parameters 3 6 Configuring the Interface Address 3 3 Configuring the Interface Name 3 4 Configuring the NI FBUS Configurator Software 3 3 Connecting Power 2 2 Connecting to the ControlNet Network 2 3 Connecting to the Fieldbus Network 2 4 ControlNet 2 5 ControlNet Analog Input Object Attributes 4 4 ControlNet Analog Input Objects 4 4 ControlNet Analog Output Object Attributes 4 8 ControlNet Analog Output Objects 4 8 ControlNet Discrete Input Object Attributes 4 10 ControlNet Discret
46. r it is in position push the rail snap into the locked position to lock it in place on the DIN rail Linking Device DIN Rail Rail Clip Unlocked Rail Clip Locked Position Device Along DIN Rail Removing the Linking Device To remove a linking device unlock it from the DIN rail by placing a screwdriver in the slot on the rail snap and opening the rail snap to the unlocked position as shown in step 1 on page 2 1 Then lift the device off of the rail Connecting Power An 11 30V dc power supply is required by each linking device The linking device filters and regulates this supplied power The power connector is a 6 pin screw terminal connector The pinout for the power connector is shown in Figure 2 1 Figure 2 1 Power Connector Pinout 11 30 VDC Backup Power V Supply To adjacent device optional optional connection 11 30 VDC Primary Power Supply T 1788 6 5 1 January 1999 Connecting to the ControlNet Network Hardware Installation and Configuration 2 3 Connect the primary power supply to the center V and C pair An optional backup power supply may be connected to the left V and C pair The right V and C pair may be used to chain the primary power supply to other devices All three terminals labeled C are connected in the linking device
47. s data Fieldbus devices broadcast alarms collect trend data and broadcast trend data An HMI typically accesses the view objects collects trends from different Fieldbus devices processes alarms and acknowledges alarms The linking device permits a Fieldbus HMI on a PC connected to ControlNet to access and monitor Fieldbus devices as if the HMI were directly connected to the Fieldbus network The NI FBUS Fieldbus Configurator generates the information about the layout or structure of the ControlNet assembly objects produced and consumed by the linking devices It provides the offset within the assembly objects for every Fieldbus function block parameter being published or subscribed by the linking device You can use this information to program your PLC processors Therefore you configure your Fieldbus network before you obtain linking device assembly object information to program your PLC processor This section describes the required hardware and software components you need before you can use the linking device You should also review the README TXT file on the linking device setup disk for the latest information Hardware e ControlNet to Fieldbus linking device e PC ControlNet interface 1784 KTC15 or 1784 PCC e ControlNet and Fieldbus cabling Software e Windows NT 4 0 with service pack 3 or higher e NI FBUS Configurator version 2 3 or higher These are necessary to configure the Fieldbus devices and the linking device using
48. s the attributes placed into the input and output assembly for each object type Table 4 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 3 4 and 150 placed into the required input assembly object Each 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 Each 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 1788 6 5 1 January 1999 4 16 Using the ControlNet to FOUNDA
49. t Council Directive 89 336 EEC Electromagnetic Compatibility EMC and the following standards in whole or in part documented in a technical construction file e EN 50081 2 EMC Generic Emission Standard Part 2 Industrial Environment e EN 50082 2 EMC Generic Immunity Standard Part 2 Industrial Environment This product is intended for use in an industrial environment Low Voltage Directive This product is tested to meet Council Directive 73 23 EEC Low Voltage by applying the safety requirements of EN 61131 2 Programmable Controllers Part 2 Equipment Requirements and Tests For specific information required by EN 61131 2 see the appropriate sections in this publication as well as the following Allen Bradley publications e Industrial Automation Wiring and Grounding Guidelines for Noise Immunity publication 1770 4 1 e Automation Systems Catalog publication B111 This equipment is classified as open equipment and must be installed mounted in an enclosure as a means of providing safety protection Specifications A 3 Hazardous Location Approval This product may be certified for general use as well as for use in hazardous locations Actual agency certification is indicated by the product label as shown below and not by statements in any user documentation Example of the certification product label CLI DIV2 GP A B C D TEMP To comply with certification for use in hazardous locations the fol
50. thmetic A 34 Sohtter 5 24 Signal Characterizer SC 34 Integrator I 24 Analog Alarm AA wil 11 15AM In the second configuration the controller 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 ofthe AO block and BKCAL OUT ofthe AO block to BKCAL IN Ax of the MAO block as shown in Figure 4 5 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 Al and so on Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 7 Figure 4 5 Sample Cascaded AO Configuration JloopTime Isec Faeim iy zo Sal Salon Salm 34 CNetMaclal3_AO ModuleO 0 CNAO 24 Valve 54 AO PCN BKCAL IN AD CN OUT A0 CN EKCAL IN A1 CN OUT Al PCN BKCAL IN A2 CN OUT 2 CN BKCAL IN A3 CN OUT A3 CN BKCAL IN A4 CN OUT Ad DCN EKCAL IN ASO CN OUT AS CN EKCAL IN A6 CN OUT A6 Pe PCN DKCAL IN A7 CN OUT 47 Alans D Trends otal 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 diff
51. urator from the browse window A sample Device Info display is shown in Figure 4 11 To print the Device Info put the cursor on the display of the Device Info that is shown in Figure 4 11 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 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device 4 17 Figure 4 11 Sample NI FBUS Configurator View of ControlNet Object Information 23 BETA NI FBUS Fieldbus Configuration System ver 2 3 CN FF Linking Device Device Info E Ele Edit View Device Info Configure window Help 8 x CN FF Linking Device ID NIC_CN FF 2_00ACDSFA_O INPUT Assembly I FieldbusTag Hodule Channel Instance Handshake Attribute Offset Length DataType Pot 3 TEMP AI_Modulef_0 0 2 VAL 6 4 CHFLOAT CHSTATUS 10 1 CHBOOL FFSTATUS 11 CHUSINT Pot 3 Press AI Moduled_O 7 1 VALUE 0 4 CHFLOAT CHSTATUS 4 CHBOOL FFSTATUS 5 1 CHUSINT Valve 54 A0_Modulel_0 0 1 TRUE FFREADBACK 12 4 CHFLOAT FFBKCALSTATUS 16 CHUSINT Valve 7 AO Module0_0 1 2 TRUE FFREADBACK 18 4 CHFLOAT FFBKCALSTATUS 22 CHUSINT Drive 11 AQ Modulel_0 2 3 TRUE FFREADBACK 24 4 CHFLOAT FFBKCALSTATUS 28 CHUSIH OUTPUT Assembly FieldbusTag Module Channel Instance Handshake Attribute Offset length DataTy
52. ut Diock lelp The Analng Output AN black converts the value in setpoint SP to something useful for the hardware found at the channel CHANNEL selection Block help Double click or right click on this item to edit block parameters This interface can be uscd to tag the block and to alter parameters in the hinek 1788 6 5 1 January 1999 1 6 Introduction Notes 1788 6 5 1 January 1999 Chapter 2 Hardware Installation and Configuration Handling the Linking Device We recommend that you adhere to this precautionary information ATTENTION This module contains ESD Electrostatic Discharge sensitive parts and assemblies Static control precautions are required when installing or testing this assembly Component damage may result if these procedures are not followed Installing the Linking Device The linking device has a rugged simple clip for mounting reliably on a standard 35 mm DIN rail Follow these steps to mount the linking device onto a DIN rail 1 Use a flat bladed screwdriver to open the DIN rail clip to the unlocked position Rail Clip Locked Rail Clip Unlocked ge 2 Hook the lip on the rear of the linking device onto the top of a 35 mm DIN rail and press the linking device down onto the DIN rail DIN Rail Press 1788 6 5 1 January 1999 2 2 Hardware Installation and Configuration 3 Slide the linking device to the desired position on the DIN rail Afte
53. with 01 for the PC running the configuration software 1 Choose and set a network address 2 Write the network address setting in the space provided on the linking device label 3 Apply or cycle power to the linking device to enable the new network address 4 Make the same address changes in your NI FBUS configuration software Module STATUS LED The STATUS LED is located on the front of the linking device between the two Fieldbus connectors as shown in Figure 1 2 It indicates whether the linking device is powered configured and operating properly Table 2 A shows how to interpret the STATUS LED states Table 2 A Interpretation of ControlNet Module STATUS LED LED State Meaning Off No power to linking device Flashing red and green Linking device self testing Flashing green Standby state Solid green Operational state Flashing red Major recoverable fault Solid red Major unrecoverable fault Standby state indicates the linking device has passed all self tests and is ready to operate Yet it is not functioning because of a lack of configuration Operational state indicates the linking device has left standby state because the necessary network configuration if any has occurred Hardware Installation and Configuration 2 7 ControlNet Network Status LEDs The ControlNet network status LEDs are located on the front of the linking device beside the ControlNet BNC connectors as shown in Figure 1
54. y 1999 4 18 Using the ControlNet to FOUNDATION Fieldbus H1 Linking Device Trends and Alarms 1788 6 5 1 January 1999 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 resources continue to be in use In order to remove existing objects from a configuration you must remove the existing configuration To accomplish this select Download Configuration in the NI FBUS Configurator enable the Clear Devices checkbox in the dialog box that appears and download a new configuration 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 Specifications Appendix A Table A A Linking Device Specifications Type Environmental Specifications Operating Temperature 0 to 60 C 32 to 140 F Storage Temperature 40 to 85 C 40 to 185 F Relative Hum
Download Pdf Manuals
Related Search