User Manual FOUNDATION Fieldbus System Catalog Numbers 9308-RSFB64ENE, 9308-RSFB256ENE, 9308-RSFB1024ENE, 1757-FFLD2, 1757-FFLD4, 1757-FFLDC2, 1757-FFLDC4
Important User Information Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid-state equipment and hard-wired electromechanical devices.
Table of Contents Preface Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Chapter 1 FOUNDATION Fieldbus System Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fieldbus Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EtherNet/IP and 1757-FFLD Linking Device Example . . . . . . . . . . . . .
Table of Contents Delete and Restore Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit Line Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use Tools for Function Block Characterization . . . . . . . . . . . . . . . . . . . . . Offline Characterization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Characterization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Chapter 6 Logix Block Operation in a ControlLogix System Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ownership and Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use RSLogix 5000 and RSNetWorx Software . . . . . . . . . . . . . . . . . . . . . Direct Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logix Block Module Operation.
Table of Contents Chapter 9 Diagnostic Web Pages Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H1 Live List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VCR Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VCR Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Appendix B Data Types and Data Structures Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DS-65 - Value & Status (floating point structure) . . . . . . . . . . . . . .
Table of Contents Notes: 8 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Preface This manual explains how to use fieldbus devices in applications with the FOUNDATION Fieldbus network. It provides technical, network setup, and configuration information, as well as guidelines on function block use. In addition, this manual offers configuration guidelines for the FOUNDATION Fieldbus network (H1) and the Rockwell Automation linking devices, catalog numbers 1757-FFLD and 1757-FFLDC.
Preface Notes: 10 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Chapter 1 FOUNDATION Fieldbus System Introduction This section explains the components of a typical FOUNDATION Fieldbus system and the integral roles that RSFieldbus configuration software and the Rockwell Automation linking devices (catalog numbers 1757-FFLD and 1757FFLDC) contribute to process control. Through the FOUNDATION Fieldbus protocol, the 1757-FFLD and 1757-FFLDC linking devices provide connectivity for fieldbus devices to Logix controllers, such as ControlLogix and CompactLogix.
Chapter 1 FOUNDATION Fieldbus System EtherNet/IP and 1757-FFLD Linking Device Example To set up communication between a controller and a linking device, you need a bridge module and Logix5000 Logix Blocks. Logix Blocks, which transfer signals between a ControlLogix environment and a fieldbus environment, have to be configured by using RSFieldbus software and RSLogix 5000 software. RSLogix 5000 software sees the linking device as a remote chassis with a virtual backplane with up to 16 available slots.
FOUNDATION Fieldbus System ControlNet and 1757-FFLDC Linking Device Example Chapter 1 The ControlNet network combines the functionality of an I/O network and a peer-to-peer network, providing high-speed performance for both functions. Devices can be scheduled for deterministic transfers of important data in addition to unscheduled time intervals for non-critical information.
Chapter 1 FOUNDATION Fieldbus System RSFieldbus Software Features RSFieldbus software, which is installed on the host workstation, is a configuration tool for creating links, loops, and schedules. The list of RSFieldbus software features includes the following: • Configure a fieldbus network with devices. • Create and edit function block control strategies. • Integrate fieldbus data into ControlLogix software via the Logix Block. • Download a configuration.
Chapter 2 RSFieldbus Software Basics Introduction This section describes the windows in RSFieldbus software and some of the tool features found in these windows. If you want to start using RSFieldbus software immediately, go to Chapter 3. The table lists the software topics described in this section.
Chapter 2 RSFieldbus Software Basics To open the Main window, you must start RSFieldbus software. See page 28 for procedures. Licensed Blocks From the Help menu, choose About to determine how many blocks you have licensed. The licensed block information appears below the Rockwell Software copyright. TIP When choosing an RSFieldbus license, keep in mind that a typical device requires a minimum of three blocks (Resource, Transducer, and process control) with an average of five blocks used.
RSFieldbus Software Basics Chapter 2 Main Window Toolbar IMPORTANT Toolbar Icon Toolbars can be moved anywhere on the screen by dragging and dropping them to the desired location. Description Opens a new project or template. You must close all open projects or templates before you can open another. Opens an existing project or template. You must close all open projects or templates before you can open another.
Chapter 2 RSFieldbus Software Basics Project Window Toolbar Toolbar Icon Description Opens a new template. You must close any open templates before you can open another. Opens an existing template. Saves the currently selected window. Saves all open windows except template windows. Prints the selected window. Displays the print preview of the project. Toggles the operation mode between online and offline. Opens the Communication window (Error Log).
RSFieldbus Software Basics Chapter 2 Fieldbus Window Toolbar The Fieldbus window toolbar contains the same buttons as the Project toolbar. For descriptions of these buttons, see page 18. Process Cell Window The Process Cell window shows an individual process cell and all attached control modules and blocks. Right-clicking each item in this window opens a corresponding menu. To open a Process Cell window, you must add a process cell to the area and expand it. See page 43 for procedures.
Chapter 2 RSFieldbus Software Basics Strategy Window The Strategy window shows a graphic representation of the blocks, parameters, and links in a control strategy. To open the Strategy window, you must first create a control module. See page 48 for more information. Function Blocks and Parameters Functions that can be performed by a device are represented as function blocks. The set of function blocks available is dependent on the types of devices on your fieldbus network.
RSFieldbus Software Basics Chapter 2 Strategy Toolbar IMPORTANT Toolbar Icon To view or hide any of the toolbars while the Strategy window is selected, choose Tool Boxes on the Tools menu and select the toolbar you want to view or hide. Description Selects items. To select more than one item, press Shift. Used to modify block tags, links, link drawings and link connections. Used to add blocks. Creates links between blocks. Imports templates into the strategy.
Chapter 2 RSFieldbus Software Basics Drawing Toolbar Toolbar Icon Description Used to selects items. To select more than one item, press Shift. Used to modify drawn objects. Used to draw rectangles. To draw a square, press Shift. Used to draw rounded rectangles. To draw a rounded square, press Shift. Used to draw ellipses. To draw a circle, press Shift. Used to draw arcs. To draw an arc whose height is equal to its width, press Shift. Used to draw sections of a pie.
RSFieldbus Software Basics Chapter 2 Alignment Toolbar Do these steps to use the alignment buttons to align objects. 1. Select the object or objects you want to align. 2. Click one of the alignment buttons. 3. Click the anchor object (object to which you want to align the other objects). Toolbar Icon Description Aligns the left side of the objects to the left side of the anchor. Vertically aligns the center of the objects to the center of the anchor.
Chapter 2 RSFieldbus Software Basics Ordering Toolbar Toolbar Icon Description Moves the selected object to the front. Moves the selected object to the back. Moves the selected object up one layer. Moves the selected object down one layer. Switches two objects in the order. Select the two objects that you want to switch, then click the icon. Moves the selected object in front of another.
RSFieldbus Software Basics Communication Window (error log) Chapter 2 The Communication window shows all errors in the current project. Do these steps. 1. Click the Error Log icon to open the Communication window. 2. To delete individual entries, right-click the date and time of the desired entry and choose Delete. 3. To delete all entries, right-click anywhere in the log and choose Clear Log.
Chapter 2 RSFieldbus Software Basics Notes: 26 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Chapter 3 Create an RSFieldbus Software Project Introduction This section describes procedures for creating a fieldbus project by using the RSFieldbus configuration software. Projects contain both a physical and logical component. The physical component contains the project hardware and the logical component contains the function blocks and algorithms that are used to control the project. Projects can be started from either component.
Chapter 3 Create an RSFieldbus Software Project Initiate a Fieldbus Project Figure 5 shows an example of a typical fieldbus system. The HSE protocol is established during the initial download of the RSFieldbus software. Data is transferred and stored to the workstation through the Ethernet or ControlNet networks depending on your application requirements and the selected linking device.
Create an RSFieldbus Software Project Chapter 3 Do these steps to initiate an RSFieldbus project. 1. To start the RSFieldbus software program, choose Start>Programs>Rockwell Software>RSFieldbus>RSFieldbus. The RSFieldbus Main window appears. There is a choice for a demo license that lets you create a limited number of function blocks. In the non-demo mode, you must activate a license. To check how many blocks are licensed on your system, choose About on the Help menu.
Chapter 3 Create an RSFieldbus Software Project Define the Server When a new project is created, your computer is defined as the HSE host and the bridge from the RSFieldbus software to your HSE fieldbus devices. The HSE host also has been designated as the Link Master. Do these optional steps to make sure the server path is correct to store the field device data. Otherwise, proceed to Create a New Bridge (linking device) on page 31. 1.
Create an RSFieldbus Software Project Chapter 3 2. In the Project window, right-click Fieldbus Networks and choose Communication Settings. The Communication Settings dialog box appears. 3. Verify the settings are the same as the dialog box shows, and click OK. Create the Physical Component Do these steps to add bridges and devices to your project. Create a New Bridge (linking device) This section defines the linking device as the bridge from HSE to your H1 field devices.
Chapter 3 Create an RSFieldbus Software Project The Project window appears. 3. Right-click HSE Network 1 and choose New>Bridge. The New Bridge dialog box appears. 4. Select the settings for the linking device you are using in the application. IMPORTANT Be sure that the Device Rev and DD Rev match the revision of linking device and revision of firmware that you are using. 5. Type a tag name for the bridge in the Device Tag box. If you do not enter a tag the default tag is Bridge_#.
Create an RSFieldbus Software Project Chapter 3 6. Click OK. The linking device is added to the HSE Host. 7. Click the Advanced Options tab. Use the default of ‘Creation based on Default Template.’ Clear the box to make your own selections. 8. Click OK. The linking device is added to the HSE Host. Create a New Fieldbus (H1) Link Do these steps to associate the fieldbus with the H1 segment. 1. In the Project window, right-click the linking device and choose New Fieldbus.
Chapter 3 Create an RSFieldbus Software Project The New Fieldbus dialog box appears. 2. Enter a tag name for the H1. If you do not enter a tag, the default tag is Fieldbus #. The 1757-FFLD linking device has two or four H1 ports depending on your system requirements. We recommend that you name each tag according to its port number. For example, H1-1 indicates that this is Upstream Port 1. 3. Select the Upstream Port (H1 port) on the linking device to which the H1 segment is connected. 4. Click OK.
Create an RSFieldbus Software Project Chapter 3 To facilitate commissioning activities, the macrocycle can be set to 1000… 2000 ms. After all the devices are commissioned and operating and the strategy is downloaded, the macrocycle can be reduced. If more unscheduled time is needed, increase the macrocycle. The unused scheduled time will be used for the unscheduled activities. 1. In the Project window, double-click H1-1 (or whatever you named the tag for the H1 link). The Fieldbus window appears. 2.
Chapter 3 Create an RSFieldbus Software Project Create a New Device Do these steps to add devices to the H1 network. 1. In the Fieldbus (H1) window, right-click the H1 icon and choose New>Device. The New Device dialog box appears.
Create an RSFieldbus Software Project Chapter 3 2. Configure the device by entering information in the New Device dialog box. Field Description Manufacturer Choose a manufacturer from the pull-down menu. Device Type Choose a device type from the pull-down menu. Device Rev Choose the device revision. IMPORTANT: The DD and CF values default to the latest revisions in the device support files if the ‘Follow the Latest DD and CF Revisions’ box is checked.
Chapter 3 Create an RSFieldbus Software Project Devices are added to the H1 and a set of function blocks are added as well. This set includes a Transducer and Resource block, and may include others depending on the device. Change Device Class to Link Master This procedure enables you to configure the device class of all the devices in the project at the same time. You must be online for this task.
Create an RSFieldbus Software Project Chapter 3 1. Right-click the H1 icon and choose Configure Device Class. The Device Class dialog box appears. 2. Select the device that you want to change to a Backup LAS and click the right arrow . 3. Repeat for any other devices that you want to change to a Backup LAS. 4. Click Apply. Change Device Class to Basic ATTENTION: During this procedure, control of the associated devices and anything linked to them will be lost.
Chapter 3 Create an RSFieldbus Software Project 2. Select the device that you want to change to a Basic and click the left arrow . 3. Repeat for any other devices that you want to change to a Basic. 4. Click Apply. Edit Attributes To change or delete an ID or tag for an H1, device, or bridge, do these steps. 1. To edit a tag, double-click the corresponding icon in the H1 window. An Attributes dialog box appears. 2. Make the necessary changes, and then click OK. 3.
Create an RSFieldbus Software Project Chapter 3 3. From the Block Type pull-down menu, choose a block type tag. ATTENTION: Be sure the tags used in your RSFieldbus projects on the same HSE Server are unique or your project may not function properly. Tags cannot include a ’.’ (period). If a separator is needed, use an ’_’ (underscore). Spaces are allowed, but not recommended.
Chapter 3 Create an RSFieldbus Software Project 2. Choose the desired block and click OK. The block is added to the physical component. Detach a Block from a Device Do these steps to remove a function block from a device. 1. In the Fieldbus (H1) window, right-click the desired block and choose Detach Block. 2. Click Yes at the warning message. The function block is removed from the device.
Create an RSFieldbus Software Project Chapter 3 2. Enter the tag in the Tag to Find box. You also can click the tag in the Tags list. The location of the tag appears in the Fieldbus Networks Location section. 3. Click OK. The tag is highlighted in your configuration. Create the Logical Component This section describes how to create a logical component to your fieldbus application. Create a New Process Cell Do these steps to create a process cell to administer function block logic. 1.
Chapter 3 Create an RSFieldbus Software Project The Process Cell dialog box appears. 2. Type a tag name. Our example is Process Cell 1. 3. Click OK. The Process Cell is added to the project.
Create an RSFieldbus Software Project Chapter 3 Create a New Control Module Do these steps to add a control module to your project. 1. Right-click the Process Cell icon and choose Expand. The Process Cell window appears. 2. Right-click the Process Cell icon and choose New Control Module. The Control Module dialog box appears. 3. Type a tag name. Our example is Control Module 1. 4. Click OK. The new (Pressure) Control Module is added to the Project.
Chapter 3 Create an RSFieldbus Software Project Set the Stale Count Stale count is the number of macrocycles that elapse before a signal is sent to indicate there has been no update of the link data. Table 1 - Stale Count Examples Macrocyle Stale Count Delay Before a Link Failure is Indicated via the Input Fault Bit or Quality/Status Data 200 ms 10 2s 1000 ms 10(1) 10 s (1) A more appropriate stale count for this example may be 3 or 4 seconds depending on the application requirements.
Create an RSFieldbus Software Project Chapter 3 Create a Function Block in Logical Component Follow the same procedures as documented on page 40, except make sure you add the blocks in the Process Cell window. An attached function block in the Process Cell will have a question mark until the block is attached to a device. Do these steps to attach a function block to a control module. 1.
Chapter 3 Create an RSFieldbus Software Project Create a New Strategy This section explains how to create and maintain a control strategy. Each control module has its own Strategy window. You can make change to a strategy in the H1 and Process Cell windows. Do these steps to initiate a control strategy. 1. In the Process Cell window, right-click the control module icon and choose Strategy. The Strategy window appears.
Create an RSFieldbus Software Project Chapter 3 Drag Blocks to a Strategy Window You can drag blocks to the Strategy window after they have been added to the control module or the Fieldbus (H1) window. Do these steps to drag-and-drop blocks into a Strategy window. 1. In the Process Cell window, click a block and drag the icon into the Strategy window. TIP If you drop the block too close to another block, the selected block will not be drawn. 2.
Chapter 3 Create an RSFieldbus Software Project The New Block dialog box appears. IMPORTANT The Device Rev, DD Rev and CF Rev values in this dialog box default to the latest version in the device support files. If the values do not match your firmware, change them or otherwise you will receive a warning on download. 3. Enter a tag name for the block and click OK. The new block appears in the Strategy window. 4. To remove an incorrect block, right-click the block and choose Delete.
Create an RSFieldbus Software Project Chapter 3 Link Blocks You can link function blocks only in the Strategy window. Do these steps. 1. In the Strategy window, click the Link icon . 2. Click the first block. The Output Parameter Selection dialog box appears. You can mouse over the pins to read their descriptions at the bottom of the dialog box. 3. Select a parameter, such as the OUT pin (as shown in the example). The pin fills to show that it is selected. 4. Click OK.
Chapter 3 Create an RSFieldbus Software Project A link is drawn from the first block to the second block. Fast Link Do these steps to create links without opening the Parameter Selection window. 1. Click the Link icon . 2. Right-click the first block and choose the desired parameter. 3. Right-click the second block and choose the desired parameter. The link is drawn.
Create an RSFieldbus Software Project Chapter 3 Edit Link Attributes This section describes how to change the attributes of links. 1. To change a link attribute, right-click selected links . 2. Use the block pop-up menu to make modifications as described in Table 2.
Chapter 3 Create an RSFieldbus Software Project 3. Do one of the following: – To remove the link from the entire project, click Yes. This action will also remove the block from the Process Cell window. – To remove the link from the strategy only, click No. This action hides the link. You can restore it, if necessary. – To halt the deletion, click Cancel. 4. To restore links that have been deleted, right-click the block to which the link was attached and choose Show Hidden Links.
Create an RSFieldbus Software Project Use Tools for Function Block Characterization Chapter 3 You have tools that provide access to the value and status of a block parameter as well as let you make configurations both offline and online. You must save the configuration upon closing, especially when online. If you ignore the prompt warning to save, and do not save the changes, the configuration file will not have the same values as the changes made in the device.
Chapter 3 Create an RSFieldbus Software Project Offline Characterization This section explains how to configure function block parameters offline. Do these steps. 1. In the Fieldbus (H1) window, right-click the desired block and choose Off Line Characterization. The Off Line Characterization dialog box appears. 2. Click to view all parameters. 3. Select a desired parameter and click Edit at the bottom of the dialog box. 4. Enter a value and click End Edit.
Create an RSFieldbus Software Project Chapter 3 5. Repeat step 3and step 4 for all desired parameters. 6. Click Close. The edited parameters are added to the block. Online Characterization Once your project is online, you can edit the device parameters. Changes are saved to the device, but you must save the project upon closing for the configuration file to contain the same modifications. 1. In the Fieldbus (H1) window, right-click the desired block and choose On Line Characterization.
Chapter 3 Create an RSFieldbus Software Project The Customization dialog box appears. 2. Do one of the following to move available parameters to selected parameters and vice versa: TIP Procedures are the same for the three tabs—Default, Type, Tag. – Select an ‘Available’ parameter and click the right arrow move the parameter to the ‘Selected’ parameter box. – Select a ‘Selected’ parameter and click the left arrow the parameter to the ‘Available’ parameter box. 3. Click Apply. 4. Click OK.
Create an RSFieldbus Software Project Design Templates Chapter 3 Templates save time and provide consistency to your projects. This section describes how to create a base template and how to import and export the template into projects. Create a Device or Bridge Template Do these steps to create a device or bridge template. This base template can be used for the same block type for other projects. 1. From the RSFieldbus main menu, click New Bridge Template.
Chapter 3 Create an RSFieldbus Software Project 4. Click the Advanced Options tab. 5. Make desired selections and click OK. 6. From the RSFieldbus main menu, choose Save As on the ProjectFile menu. The Save As dialog box appears. 7. Choose a folder in which to save the template. IMPORTANT We recommend that you save all templates in the RSFieldbus software templates folder. Choose Program Files> Rockwell Software> RSFieldbus> Fieldbus Manager>Templates. 8. Enter a name for the template and click OK. 9.
Create an RSFieldbus Software Project Chapter 3 Import a Template into a Project Do these steps to use a template to create a bridge or device for a project. 1. Right-click the HSE Network icon and choose New>Bridge from Template. The Open dialog box appears. 2. Browse to the location of your templates. 3. Select the desired template and click Open. A message dialog box appears to confirm the importing of the template. 4. Click OK.
Chapter 3 Create an RSFieldbus Software Project The Tag Table appears. 5. Right-click a tag in the New Tag column to rename the tag name. IMPORTANT Make sure your tag names are different in your RSFieldbus projects on the same HSE server or your project may not function properly. 6. Click OK. The bridge or device is added to your project. Create and Import a Strategy Template Do these steps to create a template that you can use to import and export a strategy into projects. 1.
Create an RSFieldbus Software Project Chapter 3 3. Open a Strategy window and from the Tools menu, choose Strategy, Import Strategy Template. The Open dialog box appears. 4. Browse to the location of your templates. 5. Select the desired template and click Open. The template and the Importing Template window appear. 6. Click OK. The template is added to the strategy. 7. Attach the added blocks to their respective devices. 8. Save your work.
Chapter 3 Create an RSFieldbus Software Project The Open dialog box appears to the default installation folder. If RSFieldbus software was not installed to the default folder, you must browse to the folder where it was installed. 3. Double-click the IDShell HSE.ini file. The FFLDC ControlNet Setup Tool appears. 4. Browse the network and select the 1757-FFLDC linking device that you plan to use in your RSFieldbus projects. 5. Click the Add Item icon 64 .
Create an RSFieldbus Software Project Chapter 3 The FFLDC path is added to the lower window. 6. Complete step 4 and step 5 with all other 1757-FFLDC linking devices you plan to use in RSFieldbus projects. 7. Click the Save to INI file icon . The CIP path is saved to the IDShell HSE.ini file. 8. Close the FFLDC ControlNet Setup tool.
Chapter 3 Create an RSFieldbus Software Project Notes: 66 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Chapter 4 RSFieldbus Communication Introduction This section describes how to set up an RSFieldbus project to communicate with field devices. A project must be created and a bridge module (linking device) must be in the configuration. The linking device, such as the 1757-FFLD shown in Figure 6, provides connectivity for fieldbus devices to Logix controllers via H1 networks. Figure 6 - Linking Device Connectivity Example Power Supply Ethernet network to Logix controller and RSFieldbus workstation.
Chapter 4 RSFieldbus Communication Initialize Communication Do these steps to start the communication process with field devices. 1. From the Window menu, choose Tile to make all windows visible at the same time. 2. Click the RSFieldbus online icon . The Initialize Communication animation begins. During this time, all devices are located on the network. TIP This window may appear for up to 20 seconds while RSFieldbus software is waiting for the HSE Server to respond.
RSFieldbus Communication Chapter 4 There is an order of precedence in associating devices. The bridges on the HSE network need to be associated prior to the devices on the H1 network, because the linking device is the link between the H1 and the host computer. 3. Right-click the linking device and choose Attributes. The Bridge dialog box appears. 4. From the Device Id pull-down menu, choose the corresponding device ID. 5. Click OK.
Chapter 4 RSFieldbus Communication The table describes the symbols used in the Live List. Symbol Description Basic device Bridge Link master Link active scheduler Devices that are ghosted (dimmed) in the H1-1 Live List have not yet established a connection to RSFieldbus through the HSE Server and linking device. Prior to continuation, the device must not be in a ghosted state in the live list.
RSFieldbus Communication Assign Tags Chapter 4 This section describes how to assign unique tags to each device to differentiate between similar devices on the network. ATTENTION: During this procedure, control of the associated devices and anything linked to them will be lost. IMPORTANT If this procedure is not done, the device tag in the project and the online device tag will not match and the project cannot be downloaded. 1. In the H1 window, right-click the linking device and choose Attributes.
Chapter 4 RSFieldbus Communication Export Tags A file with all the device and function block tags must be created to enable online OPC communication with RSFieldbus software and third-party OPC clients. Each time that you edit or add a device or block, the Export Tags procedure must be repeated. Otherwise, supervision of the modified tag is not allowed. 1. In the Project window, right-click a project icon and choose Export Tags. The Export Tag message window appears. 2. Click OK.
RSFieldbus Communication Chapter 4 The Consolidate OPC Database dialog box appears. This dialog box lets you do the following: • Add a project, see page 73. • Remove a project, see page 74. • Clear the project list, see page 74. Add a Consolidated Project Do these steps to add a project to the consolidated list. IMPORTANT Only the project that is currently open can be added to the consolidate list. 1. To add the project that is currently open, click Add This on the Consolidate OPC Database dialog box.
Chapter 4 RSFieldbus Communication Remove a Consolidated Project Do these steps to remove a project from the consolidated list. 1. In the Consolidate OPC Database dialog box, select a project in the Configurations section. 2. Click Remove. A message dialog box appears to confirm you want to remove the project. 3. Click Yes. A message dialog box appears to confirm the project has been removed. The tags are removed from the HseTagInfo_CONSOLIDATION.ini file. 4. Click OK.
RSFieldbus Communication Chapter 4 The Download dialog box appears. IMPORTANT The Propagate downstream is checked and dimmed by default. This means that after the HSE is downloaded, all H1 segments in the project are then downloaded. 4. Click Start. The Download dialog box shows the progress while the configuration downloads. After a download, it may take up to two minutes for OPC data to be available from the OPC server.
Chapter 4 RSFieldbus Communication Notes: 76 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Chapter 5 Create an RSLogix 5000 Software Project Introduction This section describes how to set up a linking device with a Logix5000 controller by using the RSLogix 5000 software. Examples show the 1757-FFLD linking device but procedures are similar for the 1757-FFLDC linking device, which bridges H1 field devices to Logix controllers via the ControlNet network.
Chapter 5 Create an RSLogix 5000 Software Project Create a Project for the Controller This section shows how to use the RSLogix 5000 programming software to start a project and configure a Logix5000 controller. Do these steps to create a project. 1. Start the RSLogix 5000 software, and click the New icon . The New Controller dialog box appears. The example shows information for instructional purposes. 2. Configure the controller by entering information in the New Controller dialog box.
Create an RSLogix 5000 Software Project Chapter 5 The RSLogix 5000 window redisplays with the controller project name in the Controller Organizer. Conventions for Names Throughout a Logix5000 project, you define names for the different elements of the project such as the controller, data addresses (tags), routines, I/O modules, and so forth.
Chapter 5 Create an RSLogix 5000 Software Project Add the Communication Module, Linking Device, and Logix Blocks To communicate with the controller, you add a local communication module, the linking device, and then the Logix Blocks. Within the I/O Configuration folder, organize the modules into a hierarchy (tree/branch, parent/child).
Create an RSLogix 5000 Software Project Chapter 5 The Select Major Revision pop-up dialog box appears. TIP The Major Revision number represents the functional capabilities and data exchange formats of the module. Typically, although not always, a later, that is higher, Major Revision supports at least all of the data formats supported by an earlier, that is lower, Major Revision of the same catalog number and, possibly, additional ones. 5. Choose the module revision and then click OK.
Chapter 5 Create an RSLogix 5000 Software Project 7. In the Module Definition box, click Change. The Module Definition dialog box appears. 8. Complete the module definition dialog box. Field Description Revision Defaults both the Major Revision (first field) and Minor Revision numbers. Choose the appropriate revisions from the pull-down menus, if necessary. Electronic Keying Use the default of Compatible Module or choose Exact Match or Disable Keying from the pull-down menu. See page 94 for details.
Create an RSLogix 5000 Software Project Chapter 5 Add the Linking Device Do these steps to add a linking device to communicate to field devices. 1. In the Controller Organizer, right-click Ethernet and choose New Module. The Select Module window dialog box appears. 2. Click the ‘+’ sign in front of Communications on the Select Module dialog box. 3. Select the 1757-FFLD Linking Device. 4. Click OK. 5. Choose a module revision and click OK.
Chapter 5 Create an RSLogix 5000 Software Project The New Module dialog box appears to let you enter the Name and EtherNet/IP address for your linking device. 6. Configure the linking device by entering information in the New Module dialog box. Field Description Type Defaults the type of module that you are initiating. Vendor Defaults to Allen-Bradley. Parent Defaults to the selected communication module. Name Type a name for the linking device module.
Create an RSLogix 5000 Software Project Chapter 5 The Module Properties dialog box has tabs if you checked Open Module Properties on the New Module dialog box. The Connection tab defaults as shown in the example. 8. Click OK. Add the Logix Blocks The Logix Block facilitates cascading control between a ControlLogix environment and a fieldbus environment. The Logic Block takes signals generated in either environment and sends them to the other.
Chapter 5 Create an RSLogix 5000 Software Project The Select Module dialog box appears. 2. Click the ‘+’ sign in front of Analog on the Select Module dialog box. 3. Select the Logix Block module, and then click OK. The New Module dialog box appears to let you name the Logix Block and corresponding slot number. 4. Click OK. Your I/O Configuration tree should look similar to this example.
Create an RSLogix 5000 Software Project Chapter 5 Configure the Linking Device and Logix Block Properties Use the following information to configure the linking device and Logix Block module properties. Configure Linking Device Properties 1. In the Controller Organizer, right-click the linking device and choose Properties. The Module Properties dialog box appears.
Chapter 5 Create an RSLogix 5000 Software Project 2. On the Module Properties dialog box, click the Connection tab. In this tab, you can inhibit the module and enable a major fault on the controller if the connection fails in Run mode. See page 92 for more information. 3. On the Module Properties dialog box, click the Fieldbus tab. 4. Click the icon to launch RSFieldbus software. You can create a linking device in RSLogix 5000 software or RSFieldbus software.
Create an RSLogix 5000 Software Project Chapter 5 5. Return to the Module Properties dialog box and click the Module Info tab. In this tab, you can view the module’s identification information and module’s status. You must be online for module details to appear. 6. On the Module Properties dialog box, click the Port Configuration tab. In this tab, you can view or set the module’s port configuration. You must be online for these details to appear.
Chapter 5 Create an RSLogix 5000 Software Project 7. On the Module Properties dialog box, click the Port Diagnostics tab. In this tab, you can view, refresh, and reset the module’s interface counters and media counters. You must be online for these details to appear. Maintain Logix Block Data Do these steps to rename your Logix Block and choose the type of electronic keying for an existing module. 1. On the Controller Organizer, right-click the Logix Block module and choose Properties.
Create an RSLogix 5000 Software Project Chapter 5 The Module Properties dialog box appears. In the General tab, you can rename the Logix Block module, change the slot number, add a description and choose the type of electronic keying you need. 2. On the Module Properties dialog box, click the Connection tab.
Chapter 5 Create an RSLogix 5000 Software Project 3. Review the checkboxes on this dialog box. Field Description Requested Packet Interval (RPI) Choose the RPI to determine the rate at which a communication module, such as a 1756-ENBT module, queries the block. Inhibit Module Check the box to prevent communication between the owner-controller and the module. This option allows for maintenance of the module without faults being reported to the controller.
Create an RSLogix 5000 Software Project Schedule the ControlNet Network Chapter 5 This section is only for the 1757-FFLDC linking device that can be set up for scheduling data transmissions on the ControlNet network. To select a scheduled connection for communication to the Logix Block you must run RSNetWorx for ControlNet software to schedule the network for the connection to begin running.
Chapter 5 Create an RSLogix 5000 Software Project Electronic Keying The electronic keying feature automatically compares the expected module, as shown in the RSLogix 5000 I/O Configuration tree, to the physical module before I/O communication begins. You can use electronic keying to help prevent communication to a module that does not match the type and revision expected.
Create an RSLogix 5000 Software Project Chapter 5 Figure 7 - General Tab IMPORTANT Changing electronic keying selections online may cause the I/O communication connection to the module to be disrupted and may result in a loss of data. Exact Match Exact Match keying requires all keying attributes, that is, Vendor, Product Type, Product Code (catalog number), Major Revision, and Minor Revision, of the physical module and the module created in the software to match precisely to establish communication.
Chapter 5 Create an RSLogix 5000 Software Project EXAMPLE In the following scenario, Exact Match keying prevents I/O communication. The module configuration is for a 1756-IB16D module with module revision 3.1. The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is prevented because the Minor Revision of the module does not match precisely.
Create an RSLogix 5000 Software Project Chapter 5 Release notes for individual modules indicate the specific compatibility details. When a module is created, the module developers consider the module’s development history to implement capabilities that emulate those of the previous module. However, the developers cannot know future developments.
Chapter 5 Create an RSLogix 5000 Software Project EXAMPLE In the following scenario, Compatible keying allows I/O communication: The module configuration is for a 1756-IB16D module with module revision 2.1. The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is allowed because the major revision of the physical module is higher than expected and the module determines that it is compatible with the prior major revision.
Create an RSLogix 5000 Software Project EXAMPLE Chapter 5 In the following scenario, Disable keying prevents I/O communication: The module configuration is for a 1756-IA16 digital input module. The physical module is a 1756-IF16 analog input module. In this case, communication is prevented because the analog module rejects the data formats that the digital module configuration requests.
Chapter 5 Create an RSLogix 5000 Software Project Notes: 100 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Chapter 6 Logix Block Operation in a ControlLogix System Introduction RSLogix 5000 programming software sees the linking device as a remote chassis with a virtual backplane, with up to 16 available slots. When a Logix Block is added it is seen by RSLogix 5000 programming software as an analog module. Each configured Logix Block module takes one slot and is assigned a unique slot number. This chapter explains how the Logix Block works within the ControlLogix system.
Chapter 6 Logix Block Operation in a ControlLogix System Use RSLogix 5000 and RSNetWorx Software The I/O configuration portion of the RSLogix 5000 software generates the configuration data for each I/O module in the control system, whether the module is located in a local or remote chassis. A remote chassis, also known as networked, contains the I/O module but not the module’s owner-controller. A remote chassis can be connected to the controller by an EtherNet/IP network (1757-FFLD linking device).
Logix Block Operation in a ControlLogix System Chapter 6 • If the configuration data is not appropriate, the data is rejected and an error message is displayed in the software. In this case, the configuration data can be inappropriate for any of a number of reasons. For example, a module’s configuration data may be appropriate except for a mismatch in electronic keying that prevents normal operation. The controller maintains and monitors its connection with a module.
Chapter 6 Logix Block Operation in a ControlLogix System Scheduled Logix Block Modules Connected through ControlNet Network (1757-FFLDC linking device) When Logix Block modules are connected to the owner-controller through a scheduled ControlNet network, the value of the RPI determines how often the owner-controller will receive the data over the network.
Chapter 7 Linking Device Function Blocks Introduction The linking device supports two function blocks: resource and Logix. The resource block controls the linking device itself. The Logix Block is used to move data between FOUNDATION Fieldbus devices on H1 segments and a Logix controller. The table shows the main topics in this section.
Chapter 7 Linking Device Function Blocks RES - Resource Block The resource block contains data specific to the linking device’s hardware. All data is modeled as contained, so there are no links to this block. The data is not processed in the way that a function block processes data, so there is no function schematic. One resource block must be included in each linking device. Block Use The actual mode of the resource block is used to control major states of the linking device.
Linking Device Function Blocks Chapter 7 Nonvolatile Parameters The linking device has a mechanism to save nonvolatile parameters into nonvolatile memory during the power down sequence. Parameters are recovered during the power-up sequence. Alert Notification The MAX_NOTIFY parameter value is the maximum number of alert reports that this resource block can send without getting a confirmation, corresponding to the amount of buffer space available for alert messages.
Chapter 7 Linking Device Function Blocks Supported Modes Out of Service (OOS) and AUTO are supported modes for the linking device. BLOCK_ERR The BLOCK_ERR of the resource block indicates the following causes for the error: • Device Fault State Set – When FAULT_STATE is active. • Out of Service – When the block is in OOS mode. Block Configuration Out of Service - Incorrect parameter value or uninitialized value for a parameter that requires a value or selection for the block to operate.
Linking Device Function Blocks Chapter 7 Table 5 - RES Block Parameters Index Parameter Data Type (length) Valid Range/ Options 10 MANUFAC_ID Unsigned32 11 DEV_TYPE 12 Default Value Edit Mode Description Enumeration; 0x00014D None controlled by FF RO Manufacturer identification number - used by an interface device to locate the DD file for the resource block.
Chapter 7 Linking Device Function Blocks Table 5 - RES Block Parameters Index Parameter Data Type (length) Valid Range/ Options Default Value Units Edit Mode Description 29 SET_FSTATE Unsigned8 1: Off 2: Set 1 E AUTO Allows the fault state condition to be manually initiated by selecting Set. 30 CLR_FSTATE Unsigned8 1: Off 2: Clear 1 E AUTO Writing a Clear to this parameter will clear the device fault state if the field condition, if any, has cleared.
Linking Device Function Blocks Chapter 7 Table 6 - Block Options Bit Meaning 8–15 Reserved CYCLE_SEL Bits 0 Scheduled 1 Block Execution 2 Manufacturer Specific 3–15 Reserved CYCLE_TYPE Bits 0 Scheduled (LSB) 1 Completion of block execution 2 Manufacturer specific 3–15 Reserved FEATURES Bits 0 Reserved 1 Not used 2 Fault State supported If this feature is selected in FEATURE_SEL, setting the SET_FSTATE parameter will force all output function blocks (AO and DO) in the resource to g
Chapter 7 Linking Device Function Blocks LGX -Logix Block The Logix Block facilitates linking control between a ControlLogix environment and a fieldbus environment. The Logix Block takes signals generated in either environment and sends them to the other. Figure 8 - Logix Block Schematic IN_0 ControlLogix Controller OUT_1 IN_1 IN_2 IN_3 IN_4 IN_5 IN_6 OUT_0 In[x] In[x].Value In[x].Quality In[x].SubStatus In[x].WindupL In[x].WindupH In[x].InitPrimary In[x].Initializing In[x].
Linking Device Function Blocks Chapter 7 Block Use One Logix Block lets a Logix controller to send 8 analog outputs and 8 discrete outputs to H1 devices and to receive 8 analog inputs and 8 discrete inputs from H1 devices. Each linking device can use up to 16 Logix Blocks. Within the RSLogix 5000 software, the linking device is configured and each Logix Block is assigned a slot number, similar to assigning slot numbers to physical modules.
Chapter 7 Linking Device Function Blocks Table 7 - VCR Examples Example Linking Device VCR Count Basic input device 1 input (PV) = 1 VCR (subscriber) Diagram Pressure or Temperature Transmitter Linking Device Total VCRs = 1 subscriber VCR 1 Logix Block Input Complex input device x inputs (PV) = x VCRs (subscribers) Flowmeter Input 1 Total VCRs = x subscribers VCR 1 VCR 2 Input 2 Input x Output device 1 output (PV) = 1 VCR (publisher) + 1 VCR (subscriber) from BKCAL 2 inputs (PV) from Limi
Linking Device Function Blocks Chapter 7 Figure 9 - Logix Blocks Add Extra Status in the ControlLogix Tag FF Connection 1 Value Value Qualit FF to CLX Status Fields in CLX Input Tag Substatus Value WindupH InitPrimary WindupH InitPrimary Initializing InitiateFault State 1 FF Connection WindupL WindupL Initializin Value CLX to FF InitiateFault State Status Fields in CLX Output Tag Fault 43656 The status fields listed take the fieldbus signal and break it down to pass on data that can be
Chapter 7 Linking Device Function Blocks Parameters Table 8 describes parameters for the Logix Block. See page 155 for data type and structure definitions. Table 8 - LGX Block Parameters Index Parameter Data Type (length) 1 ST_REV Unsigned16 2 TAG_DESC 3 Units Edit Mode Description 0 None RO 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.
Chapter 8 Device Web Pages Introduction Typical Applications This section describes the linking device web pages and some of the basic functions as shown in the table. Topic Page Typical Applications 117 Web Page Requirements 118 Access the Web Pages 119 Manage the Administrator Account 121 The linking device's web pages provide remote access to module data through the Ethernet port. The Ethernet port has a default static IP address of 192.168.1.
Chapter 8 Device Web Pages Web Page Requirements The table describes web page requirements. General Requirements Number of concurrent users, max 1 Supported display size, min 1024 by 768 pixels Supported internet browser Internet Explorer 6.
Device Web Pages Access the Web Pages Chapter 8 Follow these steps to access the Home page of the linking device. 1. In your Web browser, type the IP address of the linking device. The IP address shown is an example. 2. Press Enter. The Home page appears.
Chapter 8 Device Web Pages Navigate the Web Pages You navigate the web pages by using the navigation panel on the left of the window. Some pages also include tabs that can be used to access pages in each folder. Hidden pages do not contain this navigation. 1 2 3 4 TIP Examples in this section show the 1757-FFLD linking device, but the procedures are the same for the 1757-FFLDC linking device.
Device Web Pages Chapter 8 2. Click Minimize to close all folders. Manage the Administrator Account The administrator account gives you access to the linking device’s Reset, Date and Time Zone pages. These pages require the entry of a user name and password. The default user name and password are listed below. Default user name = default Default password = password Change the User Name and Password In order to secure these web pages, change the default user name and password to ones of your choosing.
Chapter 8 Device Web Pages The Password Warning appears. 2. Click Continue if the Web service can be safely restarted. The Username/Password page appears. 3. Enter the following information. a. Old UserName (default) b. New UserName c. Old Password (password) d. New Password (4 to 8 alphanumeric characters) e. Confirm the New Password 4. Click Submit.
Device Web Pages Chapter 8 Reset the User Name and Password If you forget your user name or password, you can reset the default values by resetting the linking device to its factory defaults. See page 141 for details on performing a reset. Logout IMPORTANT Once confirmed, you do not have to re-enter a user name or password when accessing subsequent pages. You must close your browser to logout.
Chapter 8 Device Web Pages Notes: 124 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Chapter 9 Diagnostic Web Pages Introduction H1 Live List This chapter describes the diagnostic web pages of the linking device. Topic Page H1 Live List 125 VCR Pages 127 Ethernet Pages 129 Diagnostic Log Files 132 The H1 Live List page is a list of devices on the linking device’s H1 ports. Each port on the linking device is listed as a separate network and the linking device appears as a device on each network list.
Chapter 9 Diagnostic Web Pages Table 9 - H1 Live List Page Field Description Port The linking device port to which the device is connected. Device Tag The name you have given to the device. ID The fieldbus device ID. Address The device’s fieldbus address. Function The fieldbus function to which the device is set: • Bridge - The 1757-FFLD linking device • Link Master - A device that can become the LAS when the linking device is not available.
Diagnostic Web Pages VCR Pages Chapter 9 The Virtual Communication Relationship (VCR) Pages consist of the VCR Overview and the H1 diagnostic pages. VCR Overview For each H1 channel there is a maximum of 64 publisher and 64 subscriber VCRs. The VCR Overview page indicates this maximum number and also indicates how many of each are currently in use on the H1 channels. IMPORTANT If you exceed the maximum number of VCRs, this page will continue to show a total of 64 VCRs used.
Chapter 9 Diagnostic Web Pages HSE and H1 VCR Diagnostics For information on specific VCR entries, refer to FOUNDATION Fieldbus Specification, document FF-007. The HSE VCR Entry tab has a pull-down menu that displays the HSE VCRs that are in use. The Static and Dynamic Entry tabs have a pull-down menu that lets you select any of the possible 166 VCRs. The list of 166 VCRs includes the 64 publisher VCRs and the 64 subscriber VCRs. An asterisk (*) next to the entry indicates that the VCR is in use.
Diagnostic Web Pages Ethernet Pages Chapter 9 This section describes the information that can be gathered about the linking device’s performance on the Ethernet network. Ethernet Network Settings The Ethernet Network Settings page provides a summary of the current Ethernet configuration of the linking device.
Chapter 9 Diagnostic Web Pages Ethernet Statistics The Ethernet Statistics page provides a summary of the status of communication activity on the Ethernet network. This summary includes the following: • Ethernet network configuration • Packets sent and received over the Ethernet network • Frames sent and received over the Ethernet network You can set the refresh rate for the Ethernet Statistics at the bottom of the page.
Diagnostic Web Pages Chapter 9 Table 11 - Ethernet Statistics Page Field Description Ethernet Link Speed Indicates if the Ethernet port is operating at 10 Mbps or 100 Mbps Interface Counters In Octets Octets received on the Ethernet interface In Ucast Packets Unicast packets received on the Ethernet interface In NUcast Packets Non-unicast packets received on the Ethernet interface In Discards Inbound packets received on the Ethernet interface but discarded In Errors Inbound packets that conta
Chapter 9 Diagnostic Web Pages Diagnostic Log Files The Diagnostic Log Files consist of the Web Server Log and the Linking Device Log. Web Server Log The Web Server Log provides a report of recent requests to the web pages. It lists when the request was made, from which IP address the request came, and a description of what was requested.
Diagnostic Web Pages Chapter 9 Linking Device Log The Linking Device Log provides a report of recent activities in the linking device. This information may be useful to Technical Support to diagnose anomalies in your linking device. It lists when the activity occurred and a description of the activity. To download the Linking Device Log, right-click the Linking Device Log document on the navigation panel and choose Save Target As.
Chapter 9 Diagnostic Web Pages Notes: 134 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Chapter 10 Advanced Diagnostics and Hidden Web Pages Introduction This chapter describes the Advanced Diagnostics and Hidden web pages of the linking device. The table describes the topics in this section. Topic Advanced Diagnostics Page Advanced Diagnostics 135 Hidden Pages 140 Advanced diagnostics appear on the Configure H1 Capture page.
Chapter 10 Advanced Diagnostics and Hidden Web Pages Follow these steps to access the Capture page. 1. On the 1757-FFLD Diagnostics Display page, click Advanced Diagnostics in the left-side pane. A sub-menu appears. 2. Click Configure H1 Capture. The Capture page appears. Ver. 1.6.0 The fields on the Capture page are described in the following pages.
Advanced Diagnostics and Hidden Web Pages Chapter 10 H1 Captures An H1 capture is in 256 KB blocks and the file size increases by 256 KB. The H1 capture saves the data of all four ports. Follow these steps to capture information about fieldbus communication on a linking device H1 port. 1. On the Capture page, verify that H1 is selected (default) as the Capture Type. 2. Click Browse. The H1 Capture File Location dialog box appears. 3. Browse to an existing folder or create a new folder. 4.
Chapter 10 Advanced Diagnostics and Hidden Web Pages 5. Specify the time and size of the capture by using the following information. a. To capture for a specific amount of time, type a Capture Time and Size. If the file size is reached before the time elapses, the capture will stop. b. To capture a specific sized file, type the Capture Size and type a Capture Time of 0. c.
Advanced Diagnostics and Hidden Web Pages Chapter 10 HSE Captures To capture information about the communication between the computer and the linking device, an additional driver must be installed. Refer to Knowledgebase Tech Note ID G128737547 at http://www.rockwellautomation.com/ knowledgebase/ for more information. HSE captures are in 5 KB blocks and the file size increases by 5 KB. Only one computer connection to the linking device at a time, is allowed for captures.
Chapter 10 Advanced Diagnostics and Hidden Web Pages Hidden Pages Access to the hidden pages is limited to the administrator account. If you have not logged into the account before accessing these pages you will be asked to enter a user name and password. To set or reset the user name or password, see page 121. Date and Time Zone Follow these steps to log date and time on web pages. 1.
Advanced Diagnostics and Hidden Web Pages Chapter 10 Reset the Linking Device The linking device can be reset in the following ways. Shaded cells indicate the reset types described in this chapter. IMPORTANT When you reset the linking device, it no longer communicates with other fieldbus devices. Make sure your process is shut down or under manual control before you reset the linking device.
Chapter 10 Advanced Diagnostics and Hidden Web Pages Reset Device Follow these steps to reset the linking device. 1. To access the Reset page, type the following address (where the IP address is the IP address of your linking device). The Linking Device Reset Page appears. 2. On the Linking Device Reset Page, click Reset Device. 3. Click Submit. A warning message appears. 4. Click Continue to reset the configuration. If you click Cancel you will return to the Home page.
Advanced Diagnostics and Hidden Web Pages Chapter 10 A dialog box appears with a reset message when you click Continue. The linking device restarts and the browser closes. Reset Configuration Follow these steps to reset fieldbus configurations and restart the linking device. 1. On the Linking Device Reset Page, click Reset Configuration. 2. Click Submit. A warning message appears. 3. Click Continue to reset configuration. The linking device restarts and the browser closes.
Chapter 10 Advanced Diagnostics and Hidden Web Pages Reset to Factory Defaults Follow these steps to reset configuration to defaults, clear log files and restart the linking device. 1. On the Linking Device Reset Page, click Reset to Factory Defaults. 2. Click Submit. A warning message appears. IMPORTANT After performing this reset the IP address is set back to DHCP. 3. Click Continue to reset configuration to factory defaults. The linking device restarts and the browser closes.
Appendix A Troubleshoot the Linking Device Introduction This appendix describes options for troubleshooting the 1757-FFLDx and the 1757-FFLDCx linking devices. The table describes the topics in this section.
Appendix A Troubleshoot the Linking Device Table 12 - 1757-FFLD Status Indicators Indicator Status Description NS (network status) Off Not powered. Flashing green No connections. Verify that the linking device is connected to the fieldbus network. Solid green CIP connections. Flashing red Connection timeout. Verify the linking device is connected to the Ethernet network. Flashing red and green Self-test. Solid green Linking device is operational.
Troubleshoot the Linking Device Appendix A Table 13 - 1757-FFLDC Status Indicators Indicator Status Description NS (network status) Off Not powered. Flashing green No connections to the Logix Blocks in the controller or to the Logix Blocks in the linking device. • Verify physical connection by using the ControlNet status indicators. • Verify the following: – The Logix Block is downloaded to the controller (via RSLogix 5000 software) and the linking device (via RSFieldbus software).
Appendix A Troubleshoot the Linking Device Table 14 - ControlNet Network Troubleshooting (A AND B) AND Cause Action Alternating red/ green Self-test None. Incorrect channel configuration Verify that the ControlNet network is connected to the correct channel of the linking device (for example), if the ControlNet network is configured for channel A only, then the linking device must be connected to the network via channel A).
Troubleshoot the Linking Device Reset the Linking Device Appendix A To manually use the reset jumper or reset button, use the Reset Configuration illustration and procedures in this section. To use the Web page to perform a remote reset, see page 141. You can reset the linking device by using one of these three ways: • Reset jumper (locally) • Reset button (locally) • Reset Web page (remotely) IMPORTANT When you reset the linking device, it no longer communicates with the fieldbus devices.
Appendix A Troubleshoot the Linking Device 2. Move the jumper from its original position (two right pins) to the two left pins. Reset Configuration Jumper Factory-default Reset Button (inside top cover) 43481-C 3. Wait 5 seconds. 4. Move jumper back to its original position. 5. Return power to the linking device.
Troubleshoot the Linking Device Appendix A 2. Press the reset button. Reset Configuration Jumper Factory-default Reset Button (inside top cover) 43481-C Reset through RSFieldbus Software By using RSFieldbus software, you can reset the linking device through the Restart parameter in the Resource block.
Appendix A Troubleshoot the Linking Device 4. Click End Edit. The reset begins. 5. Once Run appears in the value field, click Close. 6. At the Save modified parameters dialog box, click No. Reset through RSLogix 5000 Software You can reset the linking device through RSLogix 5000 software without having an RSFieldbus project configured or a Resource block downloaded. This reset restarts the linking device and deletes all downloaded fieldb us configuration.
Troubleshoot the Linking Device Appendix A 4. At the Warning dialog box, click OK. The reset starts and may take a few minutes to complete. 5. At the Module Not Found warning, click OK. This warning appears from RSLogix 5000 software not providing enough time for the reset. Once you clear the warning, you can verify that the linking device still is under the I/O Configuration folder and that it is reset.
Appendix A Troubleshoot the Linking Device Notes: 154 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Appendix B Data Types and Data Structures Introduction Data Types This appendix defines data types and data structures used in the linking device function blocks. Topic Page Data Types 155 Data Structures 156 The linking device function blocks contain the following data types.
Appendix B Data Types and Data Structures Data Structures The linking device function blocks contain the following data structures. DS-65 - Value & Status (floating point structure) This data structure consists of the value and status of floating point parameters that are Inputs or Outputs.
Data Types and Data Structures Appendix B DS-70 - Access Permissions This data structure consists of access control flags for access to block parameters. Table 19 - Access Permissions - DS-70 E Element Name Data Type Size (bytes) 1 Grant Bit String 1 2 Deny Bit String 1 DS-72 - Discrete Alarm Structure This data structure consists of data that describes discrete alarms.
Appendix B Data Types and Data Structures DS-74 - Alarm Summary Structure This data structure consists of data that summarizes 16 alerts. Table 22 - Alarm Summary Structure - DS-74 E Element Name Data Type Size (bytes) 1 Current Bit String 2 2 Unacknowledged Bit String 2 3 Unreported Bit String 2 4 Disabled Bit String 2 DS-85 - Test Structure This data structure consists of function block test read/write data.
Appendix C Fieldbus Status Codes for RSLogix 5000 Projects Introduction The status codes in this appendix are in the controller tags of projects created in the RSLogix 5000 programming software. Topic Page Input Parameters 159 Output Parameters 164 Input Parameters Table 24 - FFLD1:0:I.In[0].xxxxxx Fieldbus Status Logix Status - FFLD1:0:I.In[0].
Appendix C Fieldbus Status Codes for RSLogix 5000 Projects Table 24 - FFLD1:0:I.In[0].xxxxxx Fieldbus Status Logix Status - FFLD1:0:I.In[0].xxxxxx Quality Sub-status Limits Quality Substatus WindupL WindupH Init Primary Initializing Initiate Fault State Bad (cont.
Fieldbus Status Codes for RSLogix 5000 Projects Appendix C Table 24 - FFLD1:0:I.In[0].xxxxxx Fieldbus Status Logix Status - FFLD1:0:I.In[0].xxxxxx Quality Sub-status Limits Quality Substatus WindupL WindupH Init Primary Initializing Initiate Fault State Uncertain (cont.
Appendix C Fieldbus Status Codes for RSLogix 5000 Projects Table 24 - FFLD1:0:I.In[0].xxxxxx Fieldbus Status Logix Status - FFLD1:0:I.In[0].xxxxxx Quality Sub-status Limits Quality Substatus WindupL WindupH Init Primary Initializing Initiate Fault State Good NonCascade (cont.
Fieldbus Status Codes for RSLogix 5000 Projects Appendix C Table 24 - FFLD1:0:I.In[0].xxxxxx Fieldbus Status Logix Status - FFLD1:0:I.In[0].
Appendix C Fieldbus Status Codes for RSLogix 5000 Projects Output Parameters Table 25 - FFLD1:0:O.Out[0].xxxxxx Fieldbus Status Logix Status - FFLD1:0:O.Out[0].
Appendix D Connections Introduction This appendix describes how to count the connections on an EtherNet/IP network (used by a 1757-FFLD linking device) or on the ControlNet network (used by the 1757-FFLDC linking device). Counting Connections The 1757-FFLD and 1757-FFLDC linking device each uses one Class 1 connection for each Logix Block instantiated through RSFieldbus software and configured in the Logix controllers via an RSLogix 5000 project.
Appendix D Connections Table 26 shows an example of counting your ControlNet network connections. To determine the number of connections and packets per second for an Ethernet network, use the EtherNet/IP Capacity tool at http://www.ab.com/go/iatools.
Appendix E Device Support This appendix describes how to add device support files both automatically, by using the Import Device Support function, and manually. Introduction The device description (DD) for a particular device is provided by the manufacturer and distributed by Fieldbus Foundation. There is a DD for each device type, and it consists of the files whose extensions are .ffo and .sym. There is also a capabilities file for each device type, and it consists of the files whose extensions are .
Appendix E Device Support Import Device Support Files Before importing device support files, you must obtain these files from the device manufacturer. WARNING: For anomalies concerning importing device support files, please contact Rockwell Automation Technical Support at http://www.rockwellautomation.com/support/. Do these steps to import the device support files. 1. In the RSFieldbus software, from the ProjectFile menu, choose Import Device Support. The Browse for Folder dialog box appears. 2.
Appendix F HSE Network Setup Tool The HSE Network Setup Tool lets you view the 1757-FFLD linking devices (and their IP address) that are active on the HSE network. The tool also lets you do the following: • Select the network card that is used to connect to the HSE network. • Select which 1757-FFLD linking devices are shown in the RSFieldbus Live Lists and can be used in RSFieldbus software projects.
Appendix F HSE Network Setup Tool 3. Click the Save icon . The HSE OPC Server uses the selected network card to connect to the HSE Network. This configuration selection affects only the HSE OPC Server. No Windows system configuration is affected. Activate 1757-FFLD Linking Devices An active 1757-FFLD linking device can be used by any client connected to the HSE OPC Server; while an inactive linking device cannot be used.
Glossary The following terms and abbreviations are used throughout this manual. For definitions of terms not listed here, refer to the Allen-Bradley Industrial Automation Glossary, publication AG-7.1. 1757-FFLD An HSE node that connects either two or four H1 segments to an HSE network and to the EtherNet/IP network. The linking device supports all H1 and HSE functionality and basic, link master, and bridge modes of operation, as well as Class 1 CIP produce or consume Class 3 CIP server.
Glossary contained parameter An internal parameter that can not be linked to other function blocks or devices. ControlNet network An open control network that uses the producer/consumer model to combine the functionality of an I/O network and peer-to-peer network, while providing high-speed performance for both functions. cycle Scanning of inputs, execution of algorithms and transmission of output values to devices.
Glossary fieldbus A digital, two-way, multi-drop communication link among intelligent measurement and control devices. It serves as a Local Area Network (LAN) for advanced process control, remote input/output and high-speed factory automation applications. Fieldbus Foundation The organization that developed a fieldbus network specifically based upon the work and principles of the ISA/IEC standards committee. FOUNDATION Fieldbus The communication network that the Fieldbus Foundation created.
Glossary HSE device Any device connected directly to High-speed Ethernet (HSE) media that contains a conformant FOUNDATION fieldbus. HSE communication stack, including a configurable network management agent. For example, linking devices, I/O gateways, and HSE field devices. HSE host Non-HSE device capable of communicating with HSE devices. For example, configurators and operator workstations.
Glossary linking device As a bridge, enables peer-to-peer communication between H1 devices without the need for host system intervention. As a gateway, connects the HSE network to other plant control and information networks. link active scheduler Abbreviated as LAS, this scheduler is responsible for coordinating all communication on the fieldbus; maintaining a list of transmission times for all data buffers in all devices that need to be cyclically transmitted.
Glossary online Perform tasks, such as configuration, while the Host system is communicating with the field devices. output parameter A block parameter that sends data to another block. physical component The hardware of the fieldbus project. physical layer Physical layer receives messages from the communication stack and converts the messages into physical signals on the fieldbus transmission medium, and vice-versa. PID Acronym for Proportional Integral Derivative.
Glossary tag ID Unique alphanumeric code assigned to inputs, outputs, equipment items, and control blocks. terminator Impedance-matching module used at or near each end of a transmission line that has the same characteristic impedance of the line. Terminators are used to minimize signal distortion, which can cause data errors. H1 terminators convert the current signal transmitted by one device to a voltage signal that can be received by all devices on the network.
Glossary Notes: 178 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Index Numerics 1756-ENBT 80 1757-FFLD activation 170 administrator account 121 connections 165 function blocks 105 status indicators 145 web pages 117 1757-FFLDC administrator account 121 function blocks 105 status indicators 145 web pages 117 A access permissions 157 ActiveX page 118, 135 add devices to the Logix 5000 project 80 Logix Blocks 85 logix blocks 85 additional resources 9 administrator account 121 advanced diagnostics pages configure H1 capture page 135 alarm summary structure 158 ALARM_SUM and
Index FEATURE_SEL resource block 111 FEATURES resource block 110 fieldbus functions within device basic 126 bridge 126 link master 126 status codes for RSLogix 5000 projects 159 window 18 floating point structure 156 FOUNDATION documentation 9 URL 9 G guidelines engineering 9 licenses 16 linking device bridge 31 factory defaults 144 log 133 reset page 141 Status indicators 145 web pages 117 listen-only connections 104 live list link active scheduler 125 Logix Block adapted behavior 115 add to RSLogix 500
Index requirements web page 118 reset button 150 configuration using jumper 149 using web pages 143 device using web pages 142 factory-default 150 jumper 150 linking device manually 149 linking device with web pages 141 password 123 to factory default using web pages 144 user name 123 resource block alert notification 107 block use 106 BLOCK_ERR 108 FEATURES / FEATURE_SEL parameters 107 function block options 110 nonvolatile parameters 107 parameters 108 RESTART parameter 106 supported modes 108 RSFieldbus
Index Notes: 182 Rockwell Automation Publication 1757-UM012A-EN-P - July 2011
Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
