For further support information, refer to the Technical Support and Professional Services appendix. To comment
on the documentation, send email to techpubs@ni.com.
The media on which you receive National Instruments software are warranted not to fail to execute programming instructions, due to defects
in materials and workmanship, for a period of 90 days from date of shipment, as evidenced by receipts or other documentation. National
Instruments will, at its option, repair or replace software media that do not execute programming instructions if National Instruments receives
notice of such defects during the warranty period. National Instruments does not warrant that the operation of the software shall be
uninterrupted or error free.
A Return Material Authorization (RMA) number must be obtained from the factory and clearly marked on the outside of the package before
any equipment will be accepted for warranty work. National Instruments will pay the shipping costs of returning to the owner parts which are
covered by warranty.
National Instruments believes that the information in this document is accurate. The document has been carefully reviewed for technical
accuracy. In the event that technical or typographical errors exist, National Instruments reserves the right to make changes to subsequent
editions of this document without prior notice to holders of this edition. The reader should consult National Instruments if errors are suspected.
In no event shall National Instruments be liable for any damages arising out of or related to this document or the information contained in it.
E
XCEPTASSPECIFIEDHEREIN, NATIONAL INSTRUMENTSMAKESNOWARRANTIES, EXPRESSORIMPLIED, ANDSPECIFICALLYDISCLAIMSANYWAR RANTYOF
MERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE . CUSTOMER’SRIGHTTORECOVERDAMAGESCAUSEDBYFAULTORNEGLIGENCEONTHEPART OF
N
ATIONAL INSTRUMENTSSHALLBELIMITEDTOTHEAMOUNTTHERETOFOREPAIDBYTHECUSTOMER. NATIONAL INSTRUMENTSWILLNOTBELIABLEFOR
DAMAGESRESULTINGFROMLOSSOFDATA, PROFITS, USEOFPRODUCTS, ORINCIDENTALORCONSEQUENTIALDAMAGES, EVENIFADVISEDOFTHEPOSS IBILITY
THEREOF. This limitation of the liability of National Instruments will apply regardless of the form of action, whether in contract or tort, including
negligence. Any action against National Instruments must be brought within one year after the cause of action accrues. National Instruments
shall not be liable for any delay in performance due to causes beyond its reasonable control. The warranty provided herein does not cover
damages, defects, malfunctions, or service failures caused by owner’s failure to follow the National Instruments installation, operation, or
maintenance instructions; owner’s modification of the product; owner’s abuse, misuse, or negligent acts; and power failure or surges, fire,
flood, accident, actions of third parties, or other events outside reasonable control.
Copyright
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying,
recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National
Instruments Corporation.
Trademarks
FieldPoint™, Lookout™, National Instruments™, National Instruments Alliance Program™, NI™, NI-FBUS™, and ni.com™ are trademarks of
National Instruments Corporation.
Product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
For patents covering National Instruments products, refer to the appropriate location: Help»Patents in your software, the patents.txt file
on your CD, or
ni.com/patents.
WARNING REGARDING USE OF NATIONAL INSTRUMENTS PRODUCTS
(1) NATIONAL INSTRUMENTS PRODUCTS ARE NOT DESIGNED WITH COMPONENTS AND TESTING FOR A LEVEL OF
RELIABILITY SUITABLE FOR USE IN OR IN CONNECTION WITH SURGICAL IMPLANTS OR AS CRITICAL COMPONENTS IN
ANY LIFE SUPPORT SYSTEMS WHOSE FAILURE TO PERFORM CAN REASONABLY BE EXPECTED TO CAUSE SIGNIFICANT
INJURY TO A HUMAN.
(2) IN ANY APPLICATION, INCLUDING THE ABOVE, RELIABILITY OF OPERATION OF THE SOFTWARE PRODUCTS CAN BE
IMPAIRED BY ADVERSE FACTORS, INCLUDING BUT NOT LIMITED TO FLUCTUATIONS IN ELECTRICAL POWER SUPPLY,
COMPUTER HARDWARE MALFUNCTIONS, COMPUTER OPERATING SYSTEM SOFTWARE FITNESS, FITNESS OF COMPILERS
AND DEVELOPMENT SOFTWARE USED TO DEVELOP AN APPLICATION, INSTALLATION ERRORS, SOFTWARE AND
HARDWARE COMPATIBILITY PROBLEMS, MALFUNCTIONS OR FAILURES OF ELECTRONIC MONITORING OR CONTROL
DEVICES, TRANSIENT FAILURES OF ELECTRONIC SYSTEMS (HARDWARE AND/OR SOFTWARE), UNANTICIPATED USES OR
MISUSES, OR ERRORS ON THE PART OF THE USER OR APPLICATIONS DESIGNER (ADVERSE FACTORS SUCH AS THESE ARE
HEREAFTER COLLECTIVELY TERMED “SYSTEM FAILURES”). ANY APPLICATION WHERE A SYSTEM FAILURE WOULD
CREATE A RISK OF HARM TO PROPERTY OR PERSONS (INCLUDING THE RISK OF BODILY INJURY AND DEATH) SHOULD
NOT BE RELIANT SOLELY UPON ONE FORM OF ELECTRONIC SYSTEM DUE TO THE RISK OF SYSTEM FAILURE. TO AVOID
DAMAGE, INJURY, OR DEATH, THE USER OR APPLICATION DESIGNER MUST TAKE REASONABLY PRUDENT STEPS TO
PROTECT AGAINST SYSTEM FAILURES, INCLUDING BUT NOT LIMITED TO BACK-UP OR SHUT DOWN MECHANISMS.
BECAUSE EACH END-USER SYSTEM IS CUSTOMIZED AND DIFFERS FROM NATIONAL INSTRUMENTS' TESTING
PLATFORMS AND BECAUSE A USER OR APPLICATION DESIGNER MAY USE NATIONAL INSTRUMENTS PRODUCTS IN
COMBINATION WITH OTHER PRODUCTS IN A MANNER NOT EVALUATED OR CONTEMPLATED BY NATIONAL
INSTRUMENTS, THE USER OR APPLICATION DESIGNER IS ULTIMATELY RESPONSIBLE FOR VERIFYING AND VALIDATING
THE SUITABILITY OF NATIONAL INSTRUMENTS PRODUCTS WHENEVER NATIONAL INSTRUMENTS PRODUCTS ARE
INCORPORATED IN A SYSTEM OR APPLICATION, INCLUDING, WITHOUT LIMITATION, THE APPROPRIATE DESIGN,
PROCESS AND SAFETY LEVEL OF SUCH SYSTEM OR APPLICATION.
Compliance
FCC/Canada Radio Frequency Interference Compliance
Determining FCC Class
The Federal Communications Commission (FCC) has rules to protect wireless communications from interference. The FCC
places digital electronics into two classes. These classes are known as Class A (for use in industrial-commercial locations only)
or Class B (for use in residential or commercial locations). All National Instruments (NI) products are FCC Class A products.
Depending on where it is operated, this Class A product could be subject to restrictions in the FCC rules. (In Canada, the
Department of Communications (DOC), of Industry Canada, regulates wireless interference in much the same way.) Digital
electronics emit weak signals during normal operation that can affect radio, television, or other wireless products.
All Class A products display a simple warning statement of one paragraph in length regarding interference and undesired
operation. The FCC rules have restrictions regarding the locations where FCC Class A products can be operated.
Consult the FCC Web site at
FCC/DOC Warnings
This equipment generates and uses radio frequency energy and, if not installed and used in strict accordance with the instructions
in this manual and the CE marking Declaration of Conformity*, may cause interference to radio and television reception.
Classification requirements are the same for the Federal Communications Commission (FCC) and the Canadian Department of
Communications (DOC).
Changes or modifications not expressly approved by NI could void the user’s authority to operate the equipment under the FCC
Rules.
Class A
Federal Communications Commission
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC
Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated
in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference in which case the user is required to correct the interference
at their own expense.
www.fcc.gov for more information.
Canadian Department of Communications
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations.
Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada.
Compliance to EU Directives
Readers in the European Union (EU) must refer to the manufacturer’s Declaration of Conformity (DoC) for information*
pertaining to the CE marking compliance scheme. The manufacturer includes a DoC for most hardware products except for those
bought from OEMs. In addition, DoCs are usually not provided if compliance is not required, for example electrically benign
apparatus or cables.
To obtain the DoC for this product, click Declaration of Conformity at
by product family. Select the appropriate product family, followed by your product, and a link to the DoC appears in Adobe
Acrobat format. Click the Acrobat icon to download or read the DoC.
* The CE marking Declaration of Conformity contains important supplementary information and instructions for the user or
installer.
ni.com/hardref.nsf/. This Web site lists the DoCs
Conventions
The following conventions are used in this manual:
»The » symbol leads you through nested menu items and dialog box options
to a final action. The sequence File»Page Setup»Options directs you to
pull down the File menu, select the Page Setup item, and select Options
from the last dialog box.
This icon denotes a tip, which alerts you to advisory information.
This icon denotes a note, which alerts you to important information.
This icon denotes a caution, which advises you of precautions to take to
avoid injury, data loss, or a system crash.
boldBold text denotes items that you must select or click in the software, such
as menu items and dialog box options. Bold text also denotes parameter
names.
FieldbusThe generic term fieldbus refers to any bus that connects to field devices.
This includes Foundation Fieldbus, CAN, DNET, and Profibus. In this
manual, the term Fieldbus refers specifically to the Foundation Fieldbus.
italicItalic text denotes variables, emphasis, a cross reference, or an introduction
to a key concept. This font also denotes text that is a placeholder for a word
or value that you must supply.
monospaceText in this font denotes text or characters that you should enter from the
keyboard, sections of code, programming examples, and syntax examples.
This font is also used for the proper names of disk drives, paths, directories,
programs, subprograms, subroutines, device names, functions, operations,
variables, filenames and extensions, and code excerpts.
monospace boldBold text in this font denotes the messages and responses that the computer
automatically prints to the screen. This font also emphasizes lines of code
that are different from the other examples.
monospace italic
Italic text in this font denotes text that is a placeholder for a word or value
that you must supply.
Contents
Chapter 1
NI-FBUS Configurator Overview
Introduction to the NI-FBUS Configurator ...................................................................1-1
NI-FBUS Configurator Windows ..................................................................................1-1
Configuration Tree ..........................................................................................1-2
Help Window...................................................................................................1-3
Status Window.................................................................................................1-3
Status Tab..........................................................................................1-3
This chapter introduces the NI-FBUS Configurator, lists some of its
main features, and describes the main windows of the application.
This manual assumes that you are already familiar with
Windows 2000/NT/XP and have read the Foundation Fieldbus Overview
document or are otherwise familiar with using Foundation Fieldbus.
Introduction to the NI-FBUS Configurator
You can use the NI-FBUS Configurator to configure a Foundation Fieldbus
network and keep track of your configuration changes. The NI-FBUS
Configurator is a graphical environment for creating linkages, loops,
and a schedule based on the concepts described in the Foundation Fieldbus Overview document.
NI-FBUS Configurator Windows
1
The NI-FBUS Configurator has three resizable windows within the main
window: the configuration tree, help window, and status window.
Additional specialty windows can be opened in the middle frame to
configure your function block applications, change parameters, and update
the schedule. You also can open separate windows for block parameter
adjustment on top of the main window. The elements of the NI-FBUS
Configurator main window are shown in the following figure.
At the upper-right corner of the screen, you may see two sets of resize
buttons. The outer set of buttons controls the NI-FBUS Configurator,
and the inner set controls whatever window is currently active in the middle
frame. To see other windows in the middle frame, you may need to
minimize the active window in the middle frame.
Configuration Tree
The configuration tree, which appears to the left of the middle frame,
displays the configurable objects of the link(s) connected to the
NI-FBUS Configurator. When you select an object in the configuration
tree, its own menu appears as the main menu bar Object menu item. You
also can view the items on this menu by right-clicking the object.
NI-FBUS Configurator User Manual1-2ni.com
Note It is normal for objects to go invalid briefly during the initial bus scan or when
changing the device address. This is because the device suspends communication while
setting the address.
Help Window
Chapter 1NI-FBUS Configurator Overview
To configure or view an object settings, double-click its icon in the
configuration tree.
You can click the Show/Hide Transducers and Device IDs button to
toggle between showing or hiding the transducer blocks and device IDs in
the configuration tree.
During the initial bus scan, the following state icons sometimes overlap the
configuration tree icons:
•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.
The help window, which appears to the right of the middle frame, displays
help information. To view help information for a particular topic, move the
mouse cursor over the relevant object or parameter. Some objects require
you to click the object to view the help. To toggle between showing or
hiding the help window, select Window»Help Window.
Status Window
The status window, which appears below the middle frame, displays the
current status of the NI-FBUS Configurator. The status window contains
three tabs. To toggle between showing or hiding the status window, select
Window»Status Window.
Status Tab
The Status tab shows live updates of what the NI-FBUS Configurator does
on the Fieldbus. The Status tab automatically appears on top when you
start the NI-FBUS Configurator. The Status tab displays the steps that the
NI-FBUS Configurator takes to accomplish a task when you read, write,
scan, or download data to the bus.
The Download tab shows all the status information for the last
configuration download to the bus. The NI-FBUS Configurator retains this
information until the next download. The Download tab automatically
appears on top when you begin to download your configuration. The status
information on the Download tab can also be read in the log/notes window.
The Download tab is updated only when a configuration is downloaded to
the bus.
Errors Tab
The Errors tab displays all recent I/O errors, project configuration errors,
and warnings in the current project. To fix an error, double-click the error
to open the window showing the cause of the error. For a list of possible
errors, refer to Appendix A, Error Messages and Warnings.
Use the drop-down list attached to the upper-left corner of the Errors tab
to filter the types of errors shown. The All Errors selection shows all I/O
and project errors, and the Project Errors selection shows only project
errors.
When you download your configuration, the NI-FBUS Configurator
checks for errors in your project. If you have a project error, the
NI-FBUS Configurator warns you and allows you to cancel the download.
The NI-FBUS Configurator automatically regenerates error information
each time you change the project. However, you can force the
NI-FBUS Configurator to revalidate the project by clicking the Check Project for Errors toolbar button.
Middle Frame
The contents of the middle frame are determined by what you choose to
open there. Double-clicking certain items in the configuration tree causes a
corresponding window to open in the middle frame. The items in the
configuration tree that open a window in the middle frame are Function
Block Application, Schedule, Log/Notes, or any device.
Double-clicking a second item in the configuration tree opens another
window on top of the first window in the middle frame. To retrieve the first
window, you should minimize, restore, or close the second window using
the resize buttons shown in the following figure.
The Function Block Application Editor is the graphical interface you use to
create your Foundation Fieldbus control strategy (also known as the block
diagram) in the NI-FBUS Configurator.
You can open the Function Block Application Editor by double-clicking the
Function Block Application icon in the configuration tree. The Function
Block Application Editor appears in the middle frame of the NI-FBUS
Configurator. You can minimize and maximize this window using the
resize buttons in the upper-right corner. When this window is maximized,
the resize buttons appear under the main window resize buttons, above the
help window.
To connect blocks, use the Wiring tool. For help using this tool, refer to the
Wiring Blocks Manually section of Chapter 2, Using the NI-FBUS
Configurator.
To switch between the pointer, wiring, and loop tools in the Function Block
Application Editor window, press the <Tab> key. To switch between the
pointer and the wiring tool, press the spacebar.
You can drag and drop block or device icons from one window into another.
This is especially helpful when dragging function blocks from the
configuration tree into the Function Block Application Editor window.
Schedule Window
The NI-FBUS Configurator combines the link active schedule and function
block schedules into one diagram, as shown in the following figure.
NI-FBUS Configurator User Manual1-6ni.com
Chapter 1NI-FBUS Configurator Overview
To view or edit the link active schedule, double-click the Schedule icon in
the configuration tree. The schedule window appears in the middle frame.
In the schedule window, a key to the scheduled objects appears on the left.
The timing diagram on the right displays the execution times of the function
blocks, and when data is transmitted on the bus. The blue bars on the screen
correspond to the function block execution times and the red bars
correspond to the data transmission times, which consist of LAS
notification time and transmission time.
Tip With only one device, you will not see data transmission since there are no parameters
that need to be transmitted to other devices. Also, for some fast devices (such as the
FP-3000), the blue block execution bars are so short that they are entirely hidden behind
the block icons themselves.
Note An optimized schedule can show that the transmission time overlaps the end of
function block execution. This is because the transmission time includes the time that the
LAS uses to tell the device to publish the data.
To change the execution time for a loop, click the execution time next to the
loop icon and type in the new time.
Device Window
The device window shows the device ID and address of the host device
or field device you select. From this window, you can view and change
advanced parameters. You can view the values in hex or decimal
representation.
You can open the device window in the following ways:
•Double-click the Host icon to open the device window for a host
device, which is the device that hosts the NI-FBUS Configurator
(the PC).
•Double-click the Device icon to open the device window for a field
device. The icon is followed by the device tag and its unique serial
identifier.
•Double-click the HSE/H1 Linking Device icon to open the device
window for a linking device. The icon is followed by the device tag and
its unique serial identifier.
Tip The Host device only occurs in the H1 segment, and the HSE/H1 Linking Device
only occurs in the HSE segment.
•This icon represents the H1 segment.
•This icon represents the HSE segment.
Network Parameters Window
The network parameters window lets you change the low-level (advanced)
configuration parameters for the link. To open the network parameters
window, double-click the Network Parameters icon in the configuration
tree. The network parameters window appears floating over the main
window.
Caution This feature is disabled in the HSE segment. Do not modify these parameters
without good reason. If you must modify parameters for certain devices, the device
manufacturer will recommend settings. Modifying these parameters can have an adverse
affect on data throughput rates. If settings are incorrectly modified, some devices may
disappear off the bus.
NI-FBUS Configurator User Manual1-8ni.com
Block Configuration Window
Each function block in your application has a block configuration window
that you can use to change block parameters and other settings. When you
read or write data in the block configuration window, the Status tab in the
status window shows the status of the transactions.
To open the block configuration window for a block, do one of the
following:
•Double-click the name of the function block under the appropriate
device in the configuration tree.
•Double-click a function block in the Function Block Application
Editor window.
The block configuration window appears floating over the main window.
A block configuration window is shown in following figure.
You can change parameter settings either by clicking the desired field and
typing the new value or by selecting the new value from a pull-down menu,
if provided. For more information, refer to the Editing Block Parameters
section of Chapter 2, Using the NI-FBUS Configurator.
Yellow highlighting in the block configuration window indicates that a
parameter setting has been changed and does not match the parameter value
stored in the device.
Block Configuration Window Icons
As shown in the previous figure, an icon to the left of each parameter name
color-codes and symbolically represents the class of the parameter.
Table 1-1 describes the classes of the parameters.
Table 1-1. Block Configuration Window Icons
ShapeColorDescription
CircleGreen—AlarmsRepresents contained
Light blue—Tuning
Black—Others
parameters. Contained
parameters cannot be linked
to other parameters; they are
contained in the block.
Right arrowRedRepresents output that can be
sent to another block.
Left arrowBlueRepresents input that can be
obtained from another block.
Block Configuration Window Tabs
The block configuration window groups the parameters by functional
category. For example, parameters related to alarms appear on the
Alarms tab, and parameters related to tuning appear on the Tuning tab.
Uncategorized parameters appear on the Others tab. Some parameters
appear on multiple tabs. The tabs and their contents that you see will vary,
depending on the type of block you select.
You also can customize the tabs of the block configuration window. You
can add or delete tabs, change the order in which they appear in the window,
and add or remove any block parameters from an individual tab. For more
NI-FBUS Configurator User Manual1-10ni.com
information, refer to the Categorizing Block Parameters section of
Chapter 2, Using the NI-FBUS Configurator.
Note When you customize a tab of the block configuration window, that customization
applies to all blocks of the same type, even in other projects.
Block Configuration Window Units
Some information in the block configuration window is presented in time,
however units are not explicitly shown. The units are 1/32 of a millisecond.
For example, if
736 by 32 to get the execution time of 23.8 milliseconds.
Execution Time is listed as 736, you should divide
1.Install and configure your software and any Foundation Fieldbus
interfaces, as instructed in your getting started manual.
2.Install device descriptions, as instructed in your getting started manual.
3.Install and wire your Foundation Fieldbus device(s), as instructed in
the documentation that came with your device(s).
4.Select Start»Programs»National Instruments»NI-FBUS»NI-FBUS Configurator to start the NI-FBUS Configurator and when
prompted, click Yes to start NIFB.EXE.
or
Select Start»Programs»National Instruments»NI-FBUS»
NI-FBUS Communication Manager to start the NIFB process, then select Start»Programs»National Instruments»NI-FBUS»
NI-FBUS Configurator. Refer to your getting started manual for
more information about the NIFB process.
2
Create a New Project
1.When you start the NI-FBUS Configurator, the Start Up dialog box
appears automatically. If you want to create a new project at any other
time, select File»New.
Tip Close any open projects before opening or creating another. The multiple window
structure of the NI-FBUS Configurator quickly becomes confusing with multiple open
projects.
To hi d e the Start-up dialog box the next time you launch the NI-FBUS Configurator,
check Don't display this dialog again. To reveal the Start-up dialog box, select
Show New-Open Dialog at Start-up in the General page of the preferences dialog under
View»Preferences.
2.In the Start Up dialog box, each configured interface will appear.
Select the link(s) (ports on your Foundation Fieldbus interface) you
want to include in your project in the Added Link(s) checklist.
3.Select the type of project to create. Usually, this will be online.
4.Click OK.
The NI-FBUS Configurator scans the Foundation Fieldbus network and
checks addresses and object tags. If a device is missing either an address or
a tag, the NI-FBUS Configurator assigns one. If the NI-FBUS Configurator
detects duplicate tags, it renames the device or block, appending a numeric
identifier to the original device or block tag.
After you complete the preceding steps, the configuration tree appears,
displaying all the Fieldbus objects on the link or links you chose in step 3.
During the initial bus scan, the following state icons sometimes overlap the
configuration tree icons:
•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.
Note It is normal for objects to go invalid briefly during the initial bus scan or when
changing the device address. This is because the device suspends communication while
setting its address.
Open an Existing Project
To open an existing project, complete the following steps.
1.When you start the NI-FBUS Configurator, the Start Up dialog box
appears automatically. If you want to open an existing project at any
other time, select File»Open, browse to the file you want to edit, and
click Open.
2.In the Start-up dialog box, the recently accessed files appear in the
bottom listbox.
3.Select the Open an Existing Project option.
4.Choose the file item in the listbox, click the OK button, or double-click
the file item to open it directly.
NI-FBUS Configurator User Manual2-2ni.com
5.To open other files, double-click More Files... in the listbox.
Upload Project Configuration
Using the Upload Project button (or selecting Configure»Upload
Configuration), you can cause the NI-FBUS Configurator to read a
configuration from a device that has already been configured and overwrite
the currently open project with that information. To prevent overwriting an
existing project, close all projects, then select File»New before uploading
a configuration. The function block parameters, schedules, linkages for
publisher/subscriber, alarms, and trends will be uploaded and placed in the
project. Note that the LAS schedule is not uploaded. The LAS schedule will
be created from the list of linkages and function block schedules by the
NI-FBUS Configurator’s usual scheduling algorithm. When the upload is
complete, the project can be modified, saved, or downloaded just as if you
had created it manually.
Set Device Addresses
The NI-FBUS Configurator automatically attempts to set addresses for the
devices it detects. Information on manually setting device addresses is
provided in case you want to change the addresses assigned by the
NI-FBUS Configurator when the device is initially brought on the bus.
Chapter 2Using the NI-FBUS Configurator
Note The HSE device disables this operation for its IP address, and the host device
disables this operation for its constant address. In addition, be aware that devices may
disappear off the bus while their addresses are being set.
Complete the following steps to set the device address.
1.In the configuration tree, right-click the device whose address you
want to set and select Set Address. The Set Address dialog box
appears.
2.In the New Address field, select the desired address from the
3.Check the Set to OOS Mode checkbox. Doing so sets the block to out
of service (
current control system.
Caution When you set the device address, the device loses all linkage and
communication configuration information and loses control of the process. You should
not change a device address after you have configured and are running your process.
4.Click the Set button.
The NI-FBUS Configurator sets the device resource block to
mode before setting the new address. If the device does not go to
mode, the NI-FBUS Configurator notifies you and you must determine
whether to continue to set the address.
5.After you successfully set the address, you can set the resource block
to the desired mode.
If you need to expand the range of available addresses shown in the New Address field, use the network parameters window to modify the number
of polled addresses.
OOS) mode, which prevents the device from operating in its
OOS
OOS
Function Block Instantiation and Deletion
The NI-FBUS Configurator detects whether a given device supports
function block instantiation (creation) and deletion. If a device supports
instantiation and deletion, Instantiate new block appears in the device
object menu. This menu can be accessed by right-clicking the device, or
from the menu bar when that device is selected. When you select
Instantiate new block, a dialog box appears that shows the available block
types for this device, as read from the device description. You may choose
the block type and the number of blocks of that type to instantiate. To delete
a block from a device which supports deletion, click in the block and press
the <Delete> key.
Note Most devices do not support instantiation and deletion of function blocks. For these
devices, all the available function blocks are pre-programmed and appear automatically in
the configuration tree under the device.
NI-FBUS Configurator User Manual2-4ni.com
Set Device or Block Tags
Note If you have multiple host machines, setting a device or block tag may affect how
other host machines on an operating network access a device.
1.There are three ways to change a tag.
•In the configuration tree, right-click the device or block whose tag
you want to change and select Set Tag.
•Select the object menu item from the main menu bar and select
Set Tag.
•Double-click the device or block in the configuration tree to
launch the block configuration window. Then, click the Device
Tag field in the block configuration window.
2.In the New Tag field, type the tag you want to assign.
3.Make sure the Set to OOS Mode checkbox is selected.
Caution The host device does not permit this operation because it keeps in constant
communication. The HSE/H1 linking device also does not permit this operation because
it contains the H1 host device. Be aware that when you set the device tag, the device loses
all linkage and communication configuration information and loses control of the process.
You should not change device tags after you have configured your process.
Chapter 2Using the NI-FBUS Configurator
4.Click the Set button. The NI-FBUS Configurator sets the block or
device to
does not go to
OOS mode before setting the new tag. If the device or block
OOS mode, the NI-FBUS Configurator notifies you and
you must determine whether to continue to set the tag. You should not
try to set the tag without putting the device in
Note It may take a few minutes for the tag to set.
OOS mode.
5.After you successfully set the tag, double-click the block icon to
launch the block configuration window.
6.On the Process tab, change the block from
mode (usually
MODE_BLK parameter. For a description of modes, refer to the Function
Auto) by selecting the desired Target mode from the
The most common operational modes for function blocks on devices are
Automatic (
(
OOS).
•In Automatic mode, the block is running under its normal automatic
control, using a local setpoint value in the normal block algorithm to
determine the output value.
•In Cascade mode, the block is receiving its setpoint value from another
function block for use in the normal block algorithm to determine the
output value. A linkage object makes the connection between the two
blocks. The linkage object is created implicitly when you wire the
output of one function block to the input of another as described in the
Create and Edit Function Block Applications section. For example,
a PID function block receives its setpoints from an upstream block.
•In Out Of Service mode, the block is not running at all. Normally, this
mode is used during block configuration. Some devices require that the
function block be in Out Of Service mode when changing certain
parameters.
•In Manual mode, the block output is not being calculated by the normal
block algorithm. The operator writes the output of the block directly.
Auto), Cascade (Cas), Manual (Man), and Out Of Service
The MODE_BLK Parameter
The MODE_BLK parameter for a function block is the parameter that
contains information on the modes of the block. It has four fields:
ACTUAL, PERMITTED, and NORMAL. PERMITTED and NORMAL are defined
by the device manufacturer.
•
PERMITTED contains a list of all allowable modes for that block.
•
NORMAL is the mode the device manufacturer expects the block to be
in during normal operation.
•
ACTUAL is the current operating mode of the function block on the
device.
•
TARGET is a field that is writable by the user. Writing this field tells the
device to change to the specified mode. The device will attempt to
change the mode. If it is successful, the
reflect the
NI-FBUS Configurator User Manual2-6ni.com
TARGET mode.
ACTUAL mode changes to
TARGET,
Note If the block is not currently scheduled, it will always remain in OOS mode, regardless
of any writes to the
Application Editor window and downloading the project to the device. Refer to the Add
Blocks to the Function Block Application section and the Download a Project
Configuration section for more information.
TARGET field. A block is scheduled by placing it in a Function Block
For more information on all the allowable modes, refer to the MODE_BLK
(Diagnostic, Process) parameter description of Chapter 4, Parameters.
Configure Block Parameters
Categorizing Block Parameters
The NI-FBUS Configurator lets you customize the parameter
categorization. You can add or delete custom tabs on the block
configuration window.
All custom changes that you make will be saved on this computer, and
associated with this block type, so all blocks of this type in all projects will
use your custom setup.
Chapter 2Using the NI-FBUS Configurator
If you do not want to change the default categorization, skip to the Editing
Block Parameters section.
Adding Tabs
1.Click the Add or Delete Custom Tab button in the block
configuration window toolbar. The Add & Delete Custom Tabs
dialog box appears.
2.Click the section where you want to add the tab.