Rockwell Automation 1788-FFCT User Manual

NI-FBUS Configurator

1788-FFCT

User Manual

Important User Information

Because of the variety of uses for the products described in this publication, those responsible for the application and use of these products must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards. In no event will Rockwell Automation be responsible or liable for indirect or consequential damage resulting from the use or application of these products.

Any illustrations, charts, sample programs, and layout examples shown in this publication are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Rockwell Automation 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 publication, notes may be used to make you aware of safety considerations. The following annotations and their accompanying statements help you to identify a potential hazard, avoid a potential hazard, and recognize the consequences of a potential hazard:

WARNING

Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal

ATTENTION

injury or death, property damage, or economic loss.

Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.

IMPORTANT

Allen-Bradley is a trademark of Rockwell Automation

Identifies information that is critical for successful application and understanding of the product.

Rockwell Automation Support

Rockwell Automation offers support services worldwide, with over 75 sales/support offices, 512 authorized distributors, and 260 authorized systems integrators located throughout the United States alone, plus Rockwell Automation representatives in every major country in the world.

Local Product Support

Contact your local Rockwell Automation representative for:

• sales and order support

• product technical training

• warranty support

• support service agreements

Technical Product Assistance

If you need to contact Rockwell Automation for technical assistance, first call your local Rockwell Automation representative, then:

• Post-sales Technical Support, 440.646.5800

• Web Links, http://www.ab.com

Your Questions or Comments on this Manual

If you find a problem with this manual, please notify us of it on the How Are We Doing? form at the back of this manual.

Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . iii

Rockwell Automation Support . . . . . . . . . . . . . . . . . . . . . . . iv

Local Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Technical Product Assistance . . . . . . . . . . . . . . . . . . . . . iv

Your Questions or Comments on this Manual . . . . . . . . . iv

Preface

Fieldbus Overview

Configuring a Fieldbus System

NI-FBUS Configurator Overview

Conventions Used in This Manual . . . . . . . . . . . . . . . . . . . . ix

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1

Introduction to Fieldbus . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Parts of a Fieldbus Network. . . . . . . . . . . . . . . . . . . . . . . . 1-1

Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Blocks and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Linkages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Loops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Chapter 2

Configuring a Typical Fieldbus System. . . . . . . . . . . . . . . . 2-1

Chapter 3

Introduction to

the NI-FBUS Configurator . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

NI-FBUS Configurator Features . . . . . . . . . . . . . . . . . . . . . 3-1

NI-FBUS Configurator Windows. . . . . . . . . . . . . . . . . . . . . 3-2

Configurator Main Window . . . . . . . . . . . . . . . . . . . . . 3-2

Project Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Help Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Status Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Chapter 4

Using the NI-FBUS Configurator

v Publication 1788-UM052B-EN-P - April 2002

Starting the NI-FBUS Configurator . . . . . . . . . . . . . . . . . . . 4-1

Configuring Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Importing Device Description Files . . . . . . . . . . . . . . . . . . 4-4

Setting Device or Block Tags . . . . . . . . . . . . . . . . . . . . . . . 4-5

Setting Device Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Resetting a Device to Factory Defaults . . . . . . . . . . . . . . . . 4-8

Formulating a Control Strategy. . . . . . . . . . . . . . . . . . . . . . 4-8

Function Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Adding Function Blocks . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Connecting Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Viewing and Editing Function Block Parameters. . . . . . . . . 4-19

Block Window Icons . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Block Window Toolbar . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Tabs of the Block Window. . . . . . . . . . . . . . . . . . . . . . 4-21

Editing Block Parameters . . . . . . . . . . . . . . . . . . . . . . . 4-23

Updating Block Parameter Values. . . . . . . . . . . . . . . . . 4-24

Using Menus and Methods . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Configuring Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Configuring Trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Viewing and Editing a Schedule. . . . . . . . . . . . . . . . . . . . . 4-27

Schedule Window Toolbar . . . . . . . . . . . . . . . . . . . . . . 4-28

Changing the Link Active Schedule. . . . . . . . . . . . . . . . 4-28

Multiple Loop Representation . . . . . . . . . . . . . . . . . . . . 4-29

Setting Network Parameters. . . . . . . . . . . . . . . . . . . . . . . . 4-30

Downloading a Configuration . . . . . . . . . . . . . . . . . . . . . . 4-31

Monitoring a Function Block Application . . . . . . . . . . . . . . 4-32

Verifying a Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

Quick Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

Comparing Two Configurations . . . . . . . . . . . . . . . . . . 4-34

Viewing and Editing a Log. . . . . . . . . . . . . . . . . . . . . . . . . 4-35

Replacing Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35

Setting Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36

Changing the Software Key . . . . . . . . . . . . . . . . . . . . . . . . 4-37

Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38

Error Messages and Warnings

Troubleshooting and Common Questions

Appendix A

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Appendix B

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Missing Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Missing Symbolic Information. . . . . . . . . . . . . . . . . . . . B-2

Device Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Mode Transition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

Reading and Writing Errors . . . . . . . . . . . . . . . . . . . . . B-5

Common Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6

How can I speed up the control? . . . . . . . . . . . . . . . . . B-6

Why is my interface missing from the

Add Links dialog box? . . . . . . . . . . . . . . . . . . . . . . . . . B-6

Glossary

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

Index

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1

Publication 1788-UM052B-EN-P - April 2002

Preface

This manual gives an overview of fieldbus, describes the NI-FBUS Configurator, and explains how to use the NI-FBUS Configurator. The NI-FBUS Configurator is intended for use with Microsoft Windows NT.

This manual assumes that you are already familiar with Windows NT.

Conventions Used in This Manual

Introduction to Fieldbus

Parts of a Fieldbus Network

The term fieldbus refers to an all-digital, two-way communication system that connects control systems to instrumentation.

The Fieldbus Foundation is an organization that developed a fieldbus network based on the work and principles of the ISA and IEC. The goal of the Fieldbus Foundation is to help create products that use a robust industrial network based on existing standards and other proven technologies and to standardize using those sources.

OUNDATION Fieldbus, the communications network created by the

Fieldbus Foundation, is a protocol designed for robust, distributed control in process control environments. Devices connected by F

OUNDATION Fieldbus control a process by exchanging data.

There are six conceptual parts to a fieldbus network:

• links

• devices

• blocks and parameters

• linkages

• loops

• schedules

Descriptions of these parts can be found on the following pages.

1 Publication 1788-UM052B-EN-P - April 2002

1-2 Fieldbus Overview

Links

A FOUNDATION Fieldbus network is made up of devices connected by a serial bus. This serial bus is called a link. Links can be separated by special devices called bridges. Figure 1.1 shows a link in a fieldbus network.

Figure 1.1 Fieldbus Network Link

43270

Publication 1788-UM052B-EN-P - April 2002

Fieldbus Overview 1-3

Devices

There are three types of devices on a fieldbus network: the link master, basic devices, and bridges.

• Link master –A link master device controls the communications traffic on a link. A link master prevents multiple devices from communicating data at the same time. A link master can be a Distributed Control System (DCS) or any other device, such as a valve or a pressure transducer. There can be more than one link master per link, but only one link master can be the Link Active Scheduler (LAS) at any given time.

• Basic device –A basic device cannot become the LAS.

• Bridge –A bridge connects two or more links.

Figure 1.2 shows these three types of devices.

Figure 1.2 Fieldbus Network Devices

43271

Identifying Devices

Devices are uniquely identified on the fieldbus network by character string name, or tag. The device tag is a configurable attribute of the device that usually describes the type of the device. Device tags are unique to each device on a fieldbus network.

Another unique identifier of a device is the device ID, which includes a serial number unique to the device. The device ID is assigned by the device manufacturer; you cannot configure it.

Publication 1788-UM052B-EN-P - April 2002

1-4 Fieldbus Overview

Blocks and Parameters

Functions that can be performed by a device are represented as function blocks. Function blocks contain algorithms and algorithm-controlling parameters. The 10 standard blocks and algorithms include the following:

• Analog Input (AI)

• Analog Output (AO)

• Bias Gain (BG)

• Control Selector (CS)

• Discrete Input (DI)

• Discrete Output (DO)

• Proportional Derivative (PD)

• Proportional Integral Derivative (PID)

• Ratio Control (RC)

• Manual Loader (ML)

You can change or set the action of a block by changing the settings of its parameters. Figure 1.3 shows an example of a function block and its input and output parameters.

Figure 1.3 Function Block Parameters

43272

Publication 1788-UM052B-EN-P - April 2002

Function block parameters are classified as follows:

• Input parameters receive data from other blocks.

• Output parameters send data to other blocks.

• Contained parameters do not receive or send data; they are

contained within the block.

Function block parameters are also classified as alarm, trend, or tuning parameters. These classifications are independent of the input, output, and contained classifications. For example, an input parameter can also be an alarm, trend, or tuning parameter.

Fieldbus Overview 1-5

Device Description Files

The vendor supplied Device Description (DD) files describe the function and transducer blocks contained in a device. A DD file includes symbolic information (such as names and help strings) and functional information (such as menus and methods that you can use with the device). DDs are used with the NI-FBUS Configurator to configure a device.

Identifying Blocks

Blocks are uniquely identified on the fieldbus network by a character string name, or tag, similar to the device tag. The block tag is an attribute of a block that usually describes the purpose and location of the block. You can change the block tag, but block tags must be unique to each block on a fieldbus network.

Linkages

The function blocks configured to control a process are linked, or connected by configuration objects inside the devices. These linkages allow you to send data from one block to the other. A linkage is different from a link, in that a link is a physical wire pair that connects devices on a fieldbus network, and a linkage is a logical connection that connects two function blocks.

A block parameter that is written to the bus is referred to as a published parameter. A block parameter that is receiving data is referred to as a subscribed parameter. Figure 1.4 shows an example of a linkage between blocks. In this example, the output parameter in block A is the published parameter and the input parameter in block B is the subscribed parameter. The blocks can be in the same device or in different devices.

Figure 1.4 Linkage Between Function Blocks

43273

Publication 1788-UM052B-EN-P - April 2002

1-6 Fieldbus Overview

Loops

A loop or control loop is a group of function blocks connected by linkages executing at a configured rate. Each block executes at the configured rate and data moves across the linkages between the blocks at the configured rate. Figure 1.5 shows an example of a control loop.

Figure 1.5 Control Loop

Loop = 1 sec

43274

Multiple Loops

It is possible to have multiple loops running at different rates on a link. Figure 1.6 shows an example of multiple loops.

Figure 1.6 Multiple Loops Running At Different Rates

Publication 1788-UM052B-EN-P - April 2002

43275

Fieldbus Overview 1-7

Even if loops are running at different rates, they can send each other data through linkages. Figure 1.7 shows an example of a linkage between two loops. All loops on a link run within one macrocycle. A macrocycle is the least common multiple of all the loop times on a given link. For example, the macrocycle in Figure 1.7 is 1 second.

Figure 1.7 Linkage Between Two Loops

43276

Publication 1788-UM052B-EN-P - April 2002

1-8 Fieldbus Overview

Schedules

A schedule of data traffic allows communication to be deterministic, meaning that data is transferred between a given set of devices at the same time during each loop.

The schedule can be divided into two parts: a function block schedule that determines when a block executes, and a publishing schedule that determines when data parameters are published over the fieldbus. The function block schedule is downloaded to the device that contains the function blocks, and the publishing schedule is usually downloaded to a device or devices that have link master capability. The link master running the publishing schedule, and therefore controlling the process, is the LAS.

Downloading the schedule to multiple devices with link master capability ensures that the process is controlled, even if the LAS fails. If the LAS fails, another device with link master capability takes over the bus and runs the schedule. Figure 1.8 shows the relationship of the two schedules to the device, link, link master, and LAS.

Link

Basic Device

(Function Block

Schedule)

Linkage

Figure 1.8 Publishing and Function Block Schedules Relationships

LAS

(Publishing

Schedule)

Basic Device

(Function Block

Schedule)

(Function Block Schedule,

Link Master

Publishing Schedule)

43277

Publication 1788-UM052B-EN-P - April 2002

Chapter

Configuring a Fieldbus System

This chapter contains brief instructions on how to configure a typical fieldbus system.

Refer to Chapter, Fieldbus Overview, or the Glossary for an explanation of fieldbus terms or concepts. Refer to Chapter 3, NI-FBUS Configurator Overview, for information about a specific control or window in the NI-FBUS Configurator.

Configuring a Typical Fieldbus System

IMPORTANT

The following is an example of a typical fieldbus system configuration, using the NI-FBUS Configurator:

1. Connect the devices in a segment. You can connect devices in

one of two ways: online or offline.

• In the online mode, connect the devices to the fieldbus segment and start the NI-FBUS Configurator.

• In the offline mode, the devices are not connected to the fieldbus.

For instructions on how to connect devices, refer to the Configuring Online section on page 4-2.

2. Import the Device Descriptions (DDs) of the connected devices

to the computer that runs the NI-FBUS Configurator.

Before you use the NI-FBUS Configurator, you must install and configure your software and any fieldbus interfaces, as instructed in your getting started manual.

For instructions on how to import DDs, refer to the Starting the NI-FBUS Configurator section on page 4-1.

1 Publication 1788-UM052B-EN-P - April 2002

2-2 Configuring a Fieldbus System

3. Set addresses and tags.

• Each device has a physical device tag and a fieldbus network address. You must assign a unique tag to each device. Each address must be unique within a fieldbus segment.

• Each device has function blocks that perform control functions, such as AI, AO, DI, DO, PID, and so on. Devices also have transducer blocks that perform I/O with sensors and actuators. You must assign a unique tag to function and transducer blocks.

For instructions on how to set addresses and tags, refer to the Setting Device or Block Tags and Setting Device Addresses sections on pages 4-5 and 4-6, respectively.

4. Formulate a control strategy.

• To define your control strategy, identify the function blocks and connect the relevant function blocks. For example, if you are configuring a cascaded PID control, you must identify the primary and secondary PIDs and their inputs and outputs.

• You must also configure loop times or cycle times. For example, you can configure the primary loop in the cascade to execute at a certain rate, and configure the secondary loop to execute at a different rate.

For instructions on how to formulate a control strategy, refer to the Formulating a Control Strategy section on page 4-8.

5. Schedule function blocks and communication.

Fieldbus schedules the execution of function blocks and the communication between the connected function blocks. The two schedules are synchronized to prevent oversampling.

For instructions on how to edit the schedule, Viewing and Editing a Schedule section on page 4-27.

Publication 1788-UM052B-EN-P - April 2002

Configuring a Fieldbus System 2-3

6. Configure alarms.

Using the NI-FBUS Configurator, you can configure fieldbus devices to generate alarms. Thus, you do not need an HMI to generate alarms. To configure alarms, identify the function blocks that generate alarms and the hosts that receive the alarms. You must also configure the alarm limits and priorities.

For instructions on how to configure alarms, refer to the Configuring Alarms section on page 4-25.

7. Configure trends.

Fieldbus devices collect trend samples (value, status, and time stamps) and broadcast them on the bus periodically. To configure trends, identify the function block (or transducer block) parameters that you want to trend, and configure the sampling rates and types for each of them. You must also identify which host or hosts receive the trend.

For instructions on how to configure trends, refer to the Configuring Trends section on page 4-26.

8. Set static parameters.

For your control strategy to work, you must configure static parameters, such as scaling parameters like XD_SCALE in AI/AO blocks and PV_SCALE in PID blocks. For PID control, you must also configure engineering units, control and I/O options, fault state values for output blocks, and tuning parameters.

For instructions on how to set parameters, refer to the Viewing and Editing Function Block Parameters section on page 4-19.

9. Configure input/output (I/O).

Sensor and actuator I/O is typically modeled as a transducer block. Refer to your sensor or actuator documentation to determine whether you can configure I/O.

For instructions on how to configure I/O, refer to the Viewing and Editing Function Block Parameters section on page 4-19.

Publication 1788-UM052B-EN-P - April 2002

2-4 Configuring a Fieldbus System

10. Set network parameters.

For communication and scheduling to function properly, you must configure the fieldbus communication-specific network parameters. An example of a network parameter is identifying the primary time master and the primary Link Active Scheduler (LAS) devices.

For instructions on how to set network parameters, refer to the Setting Network Parameters section on page 4-30.

11. Download a configuration.

Make sure that all the devices are connected to the bus, and download the configuration.

For instructions on how to download a configuration, refer to the Downloading a Configuration section on page 4-31.

Publication 1788-UM052B-EN-P - April 2002

Chapter

NI-FBUS Configurator Overview

This chapter introduces the NI-FBUS Configurator, lists some of its main features, and describes the main windows of the application.

Introduction to the NI-FBUS Configurator

NI-FBUS Configurator Features

You can use the NI-FBUS Configurator to configure a fieldbus network and keep track of your configuration changes. The NI-FBUS Configurator is an easy-to-use graphical environment for creating linkages, loops, and a schedule based on the fieldbus concepts described in Chapter, Fieldbus Overview.

Now that you are familiar with the basics of fieldbus communication, you are ready to use the NI-FBUS Configurator. To use the NI-FBUS Configurator immediately, continue to Chapter, Using the NI-FBUS Configurator.

You can use the NI-FBUS Configurator to configure a fieldbus network as follows:

• Set block and device tags

• Set device addresses

• Create and edit function block control strategies

(function block applications)

• Configure vendor-defined function and transducer blocks

• Create and edit schedules

• Read and write to function block control strategies

(function block applications)

• Invoke Device Description (DD) methods

• Display DD menus

• Download a configuration

• Verify a configuration and compare it to a saved configuration

• Monitor a downloaded configuration

• Replace devices

• Log project download changes

• Save and print a configuration

1 Publication 1788-UM052B-EN-P - April 2002

3-2 NI-FBUS Configurator Overview

NI-FBUS Configurator Windows

The NI-FBUS Configurator has three moveable, dockable windows within the Configurator Main window: the Project, Help, and Status windows.

Configurator Main Window

The Configurator Main window has menus at the top, and contains the windows described in the following sections. Figure 3.1 shows the Project, Help, and Status windows within the Configurator Main window.

Figure 3.1 Configurator Main Window

Publication 1788-UM052B-EN-P - April 2002

NI-FBUS Configurator Overview 3-3

Project Window

The Project window, which appears to the left of the Configurator Main window by default, displays the configurable objects of the link connected to the NI-FBUS Configurator. To configure each object, double-click these objects in the Project window; doing so opens the correct interface to use to configure the object. Figure 3.2 shows the Project window.

Figure 3.2 Project Window

Publication 1788-UM052B-EN-P - April 2002

3-4 NI-FBUS Configurator Overview

Each object in the Project window has its own menu that appears on the main taskbar when you select the object. You can also view the menu by right-clicking the object, as shown in Figure 3.3.

Figure 3.3 Project Window Pop-Up Menu

Conventions

The NI-FBUS Configurator uses the following standard user interface conventions:

• Double-click an object to open the configuration interface.

• Right-click an objewct to display a popup menu that lists actions

related to that object.

• Single-click an object to select it and display a popup menu in the menu bar at the top of the Main window.

• Single-click an object to select it and hover the cursor over the object to view the help information for that object. The appropriate help information appears in the Help window.

• Drag and drop icons (block or device) from one window and into another.

Publication 1788-UM052B-EN-P - April 2002

NI-FBUS Configurator Overview 3-5

Icons

Descriptions of the project icons that appear in the Project window follow:

Icon Name Description

Link This icon represents the fieldbus segment to which your PC is

connected. Double-click this icon to open the Network Parameters window.

Log/Notes Double-click this icon to see a summary of all the changes you

have made to the project link.

Network Parameters

Schedule Double-click this icon to see the schedule of function block

Function Block Application Editor

Device This icon represents a fieldbus device, followed by the device tag

Host Device This icon represents the device (PC) that hosts the NI-FBUS

Function Block

Double-click this icon to open the Network Parameters window and change the low-level configuration parameters for the link.

executions and data transmissions for the entire link.

Double-click this icon to use the Function Block Application Editor to wire function blocks together into a function block application. You can add multiple function block applications to your project.

and its unique serial identifier. Double-click this icon to open the Device window.

Configurator. Double-click this icon to open the Device window.

This icon represents a fieldbus function block, followed by the block tag and its type (in parentheses). Double-click this icon to open the Block window.

State Icons

During the initial scan of the bus, state icons sometimes overlap the project icons. Descriptions of the state icons used in the Project window follow:

Icon Name Description

Updating This icon appears when the NI-FBUS Configurator is reading or

writing to the object.

Error This icon appears when the NI-FBUS Configurator detects or

encounters an error with the object.

Invalid This icon appears when the indicated object is not responding to

the NI-FBUS Configurator scan.

Publication 1788-UM052B-EN-P - April 2002

3-6 NI-FBUS Configurator Overview

Toolbar

The toolbar at the top of the Project window helps you perform basic operations on your project. Figure 3.4 shows the Project window toolbar.

Figure 3.4 Project Toolbar

Descriptions of the buttons on the Project toolbar follow:

Button Name Description

Errors Click this button to validate the project.

New Link Click this button to add another link to the project.

New Device Click this button to add another device to the project.

New Block Click this button to add another block to the project.

New FBAP Click this button to add another Function Block Application Editor

window to the project.

Download Project

Upload Project

Verify and Diff

Show/Hide Transducers

Click this button to open the Download Configuration dialog box.

Click this button to reread the configuration.

Click this button to upload your current configuration and compare it to the saved project.

Click this button to hide the transducer blocks from the Project window.

Publication 1788-UM052B-EN-P - April 2002

+ 60 hidden pages

Rockwell Automation 1788-FFCT User Manual

Important User Information

Rockwell Automation Support

Table of Contents

Preface

Conventions Used in This Manual

Related Documentation

Introduction to Fieldbus

Parts of a Fieldbus Network

Configuring a Typical Fieldbus System

NI-FBUS Configurator Features

NI-FBUS Configurator Windows