The media on which you receive National Instruments software are warranted not to fail to execute programming
instructions, due to defects in materials and work man ship, for a peri od of 90 d ays from da te o f sh ipm ent, as evi denced
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 noti ce of su ch defect s d uring th e warranty perio d.
National Instruments does not warrant that the op eration of t he soft ware shall b e uni nterrup ted or erro r free.
A Return Material Authorization (RMA) number must b e ob tain ed fro m th e facto ry an d clearl y mark ed on t he outsi de
of the package before any equipment will be a ccepted for warranty work. National Instruments will pay the shipping c osts
of returning to the owner parts which are covered by warran ty.
National Instruments believes that the information in this manual is accurate. The document has been c arefully 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 th is do cume nt with ou t p rio r no ti ce to hold ers o f thi s ed itio n. The read er sh ou ld
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 docume nt o r th e in form ati on con tai ned in i t.
XCEPT AS SPECIFIED HEREIN
E
SPECIFICALLY DISCLAIMS ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
RIGHT TO RECOVER DAMAGES CAUSED BY FAULT OR NEGLIGENCE ON THE PART OF NATIONAL INSTRUMENTS SHALL BE
LIMITED TO THE AMOUNT THERETOFORE PAID BY THE CUSTOMER
DAMAGES RESULTING FROM LOSS OF DATA, PROFITS, USE OF PRODUCTS, OR INCIDENTAL OR CONSEQUENTIAL DAMAGES
EVEN IF ADVISED OF THE POSSIBILITY THEREOF
regardless of the form of action, whether in contract or tort , incl udin g n egli gen ce. An y 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 reason able control . T he wa rranty pro vided herein does n ot cove r
damages, defects, malfunctions, or service failures caused by own er’s fai lure to fol low the Nati onal In st rume nts
installation, operation, or maintenan ce in structi on s; ow ner’s modi ficat io n o f th e pro du ct; ow ner’s ab use, m isus e , o r
negligent acts; and power failure or surges, fire, flood, accident, actions of third pa rties, or other events outside reasonable
control.
ATIONAL INSTRUMENTS MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AND
, N
. This limitation of the liability of Nati onal In st rum ent s will appl y
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.
USTOMER’S
. C
ATIONAL INSTRUMENTS WILL NOT BE LIABLE FOR
. N
,
Trademarks
BridgeVIEW™, LabVIEW™, National Instruments™, natinst.com™, and NI-DAQ™ are trademarks of National
Instruments Corporation.
Product and company names listed are trademarks or trade names of their respective companies.
WARNING REGARDING MEDICAL AND CLINICAL USE OF NATIONAL INSTRUMENTS PRODUCTS
National Instruments products are not designed with com ponent s and tes ting inten ded to ensure a l evel of reliab ilit y
suitable for use in treatment and diagnosis of humans. Applications of National Instruments products invol ving m edical
or clinical treatment can create a potential for accidental injury caused by product failure, or by errors on the part of the
user or application designer. Any use or application of National Instruments products for or involving medical or clinical
treatment must be performed by properly trained and qualified medical personnel, and all traditional medical safeguards,
equipment, and procedures that are appropriate in the particular situation to prevent serious injury or death should always
continue to be used when National Instruments products are being used . National Instrum ents product s are NOT intended
to be a substitute for any form of established process, procedure, or equipment used to monitor or safeguard human health
and safety in medical or clinical treatment.
Contents
About This Manual
Organization of This Manual...............................................................................................xix
The BridgeVIEW User Manual contains the information you need to get
started with the BridgeVIEW software package. This manual explains the
BridgeVIEW environment, tag configuration, human machine interfaces,
alarms and events, and historical data logging and extraction. This manual
also reviews the concepts of G programming.
Throughout both sections of this manual, there are activities that teach
you what you need to know to build your own virtual instruments, and
ultimately, your own SCADA system. This manual assumes that you
know how to operate your computer and that you are familiar with its
operating system.
Organization of This Manual
This manual is divided into two parts. Part I, BridgeVIEW Concepts,
introduces you to the basic BridgeVIEW concepts, and includes Chapters 1
through 8. Part II, G Tutorial, describes the G programming language, and
how it works within BridgeVIEW, and includes Chapters 9 through 15.
We encourage you to work through all the activities in this manual before
you begin building your applications. You should save all of the VIs you
create with the BridgeVIEW activities in the
directory. To view the VI(s) for an activity that you have not completed
yourself, see the
solutions to the activities from the BridgeVIEW Concepts section of this
manual, and the
solutions to the activities in the G Tutorial section of this manual.
BridgeVIEW\Activity\Solutions
BridgeVIEW\Activity\Solution
BridgeVIEW\Activity
directory for the
directory for the
BridgeVIEW Concepts
Part I, BridgeVIEW Concepts, contains the following chapters.
•Chapter 1, Introduction, describes the unique BridgeVIEW approach
to Human Machine Interface (HMI) and Supervisory Control and
Data Acquisition (SCADA). It also contains system configuration,
installation instructions and basic information that explains how
to start using BridgeVIEW to develop industrial automation
applications.
•Chapter 2, BridgeVIEW Environment, describes the BridgeVIEW
environment. It explains the basic concepts behind G, the
programming language upon which BridgeVIEW is built, the
BridgeVIEW Engine Manager, system errors and events, the Tag
Monitor utility, and the Tag Browser utility. This chapter also explains
how to access online help for BridgeVIEW and provides an activity
that illustrates how to examine the front panel and block diagram of a
virtual instrument (VI).
•Chapter 3, Tag Configuration, explains tags, the Tag Configuration
Editor, and how you edit tags within the BridgeVIEW system.
•Chapter 4, Human Machine Interface, explains what a Human
Machine Interface (HMI) is and how you can monitor and control tags
from your HMI.
•Chapter 5, Alarms and Events, introduces the basic concepts of alarms
and events, and explains how to view, acknowledge, and configure
them within the BridgeVIEW system.
•Chapter 6, Historical Data Logging and Extraction, explains the
concept of a trend, how to log and extract historical data, and how to
use the Historical Trend V iewer (HTV), a utility that displays historical
data that has been logged to disk with BridgeVIEW.
•Chapter 7, Advanced Application Topics, explains the advanced topics
you need to understand to make optimum use of BridgeVIEW for
developing applications. The advanced topics covered in this chapter
are the Panel G Wizard, BridgeVIEW System Control, Tag Attributes
VIs, and BridgeVIEW Security.
•Chapter 8, Servers, explains how to use servers with BridgeVIEW.
BridgeVIEW supports several types of servers including OPC Serv ers,
DDE Servers, and IA Device Servers.
G Tutorial
Part II, G Tutorial, contains the following chapters.
•Chapter 9, Creating VIs, introduces the basic concepts of virtual
instruments and provides activities that explain how to create the icon
and connector, how to use a VI as a subVI, ho w to use the VI Setup…
option, and how to use the SubVI Node Setup… option.
•Chapter 10, Customizing VIs , introduces the basic concepts used for
customizing VIs.
•Chapter 11, Loops and Charts, introduces structures and explains
the basic concepts of charts, the While Loop, and the For Loop.
•Chapter 12, Case and Sequence Structures and the Formula Node,
introduces the basic concepts of Case and Sequence structures, and
provides activities that explain how to use the Case structure, how
to use the Sequence structure, and what sequence locals are and
how to use them.
•Chapter 13, Front Panel Object Attributes, describes objects called
attribute nodes, which are special block diagram nodes that control the
appearance and functional characteristics of controls and indicators.
•Chapter 14, Arrays, Clusters, and Graphs, introduces the basic
concepts of polymorphism, arrays, clusters, and graphs and provides
activities that explain auto-indexing and the Graph and Analysis VIs.
•Chapter 15, Application Control, introduces the VI Server and
provides an activity that explains how to use it within BridgeVIEW.
The VI Server allows you to control when a VI is loaded into memory,
run, and unloaded from memory.
•Chapter 16, Program Design, suggests some techniques to use when
creating programs and offers programming style recommendations.
Appendices, Glossary, and Index
•Appendix A, HMI Function Reference, describes error handling
for BridgeVIEW VIs and contains an explanation of the VIs in the
BridgeVIEW VI library. In this appendix, the VIs are arranged
alphabetically, first by VI Library name (Alarms and Events,
Historical Data, System, Tags, and Tag Attributes), then by VI name.
•Appendix B, Citadel and Open Datab ase Connectivity, describes the
Citadel database and the Open Database Connectivity (ODBC) driver ,
and includes several examples of how to use it.
•Appendix C, Customer Communication, contains forms to help
you gather the information necessary to help us solve your
technical problems, and a form you can use to comment on
the product documentation.
•The Glossary contains an alphabetical list of terms used in this
manual, including abbreviations, acronyms, metric prefixes,
mnemonics, and symbols.
•The Index contains an alphabetical list of key terms and topics in
this manual, including the page where you can find each one.
The following conventions are used in this manual:
boldBold text denotes a parameter, menu name, palette name, menu item,
return value, function panel item, or dialog box button or option.
italicItalic text denotes mathematical variables, emphasis, a cross reference,
or an introduction to a key concept.
bold italicBold italic text denotes an activity objective, note, caution, or warning.
monospace
monospace bold
monospace italic
<>Angle brackets enclose the name of a key on the keyboard—for example,
-A hyphen between two or more key names enclosed in angle brackets
<Control>Key names are capitalized.
»The » symbol leads you through nested menu items and dialog box options
Text in this font denotes text or characters that you should literally enter
from the keyboard. Sections of code, programming examples, and syntax
examples also appear in this font. This font also is used for the proper
names of disk drives, paths, directories, programs, subprograms,
subroutines, device names, variables, filenames, and extensions, and
for statements and comments taken from program code.
Bold 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.
Italic text in this font denotes that you must enter the appropriate words or
values in the place of these items.
<PageDown>.
denotes that you should simultaneously press the named keys—for
example, <Control-Alt-Delete>.
to a final action. The sequence File»Page Setup»Options»Substitute Fonts directs you to pull down the File menu, select the Page Setup item,
select Options, and finally select the Substi tute Fonts option from the last
dialog box.
pathsPaths in this manual are denoted with backslashes (\) to separate drive
This icon to the left of bold text denotes the beginning of an activity, which
contains step-by-step instructions you can follow to learn more about
BridgeVIEW.
This icon to the left of bold text denotes the end of an activity, which
contains step-by-step instructions you can follow to learn more about
BridgeVIEW.
This icon to the left of bold italicized text denotes a note, which alerts you
to important information.
Abbreviations, acron yms, metric pref ixes, mnemonics , symbols, and terms
are listed in the Glossary.
Related Documentation
The following documents contains information that you might find helpful
as you read this manual:
•G Programming Reference Manual
•BridgeVIEW Online Reference, available online by selecting
Help»Online Reference
About This Manual
Customer Communication
National Instruments wants to receive your comments on our products
and manuals. We are interested in the applications you develop with our
products, and we want to help if you have problems with them. To make it
easy for you to contact us, this manual contains comment and configuration
forms for you to complete. These forms are in Appendix C, Customer
This section contains information about the BridgeVIEW environment, tag
configuration, Human Machine Interface, alarms and events, historical data
logging and extraction, servers, and advanced application topics such as
system control and security.
Part I, BridgeVIEW Concepts, contains the following chapters.
•Chapter 1, Introduction, describes the unique BridgeVIEW approach
to Human Machine Interface (HMI) and Supervisory Control and
Data Acquisition (SCADA). It also contains system configuration,
installation instructions and basic information that explains how
to usestart using BridgeVIEW to develop industrial automation
applications.
•Chapter 2, BridgeVIEW Environment, describes the BridgeVIEW
environment. It explains the basic concepts behind G, the
programming language upon which BridgeVIEW is built, the
BridgeVIEW Engine Manager, system errors and even ts, th e Tag
Monitor utility, and the Tag Browser utility. This chapter also explains
how to access online help for BridgeVIEW and provides an activity
that illustrates how to examine the front panel and block diagram of a
virtual instrument (VI).
•Chapter 3, Tag Configuration, explains tags, the Tag Configuration
Editor, and how you edit tags within the BridgeVIEW system. Before
you can run a BridgeVIEW application, you must specify a tag
configuration.
•Chapter 4, Human Machine Interface, explains what a Human
Machine Interface (HMI) is and how you can monitor and control tags
from your HMI.
•Chapter 5, Alarms and Events, introduces the basic concepts of alarms
and events, and explains how to view, acknowledge, and configure
them within the BridgeVIEW system.
Part I
Part I BridgeVIEW Concepts
•Chapter 6, Historical Data Logging and Extraction, explains the
concept of a trend, how to log and extract historical data, and how to
use the Historical Trend V iewer (HTV), a utility that displays historical
data that has been logged to disk with BridgeVIEW.
•Chapter 7, Advanced Application Topics, explains BridgeVIEW
Environment Securitythe advanced topics you need to understand to
make optimum use of BridgeVIEW for developing applications. The
advanced topics covered in this chapter are the Panel G Wizard,
BridgeVIEW System Control, Tag Attributes VIs, and BridgeVIEW
Security.
•Chapter 8, Servers, explains how to use servers with BridgeVIEW.
BridgeVIEW supports several types of servers including OPC Serv ers,
DDE Servers, and IA Device Servers.
This chapter describes the unique BridgeVIEW approach to
Human Machine Interface (HMI) and Supervisory Control and Data
Acquisition (SCADA). It also contains system configuration, installation
instructions, and basic information that explains how to start using
BridgeVIEW to develop industrial automation applications. This chapter
refers you to other chapters or manuals for more information.
Welcome to BridgeVIEW
BridgeVIEW adds real-time process monitoring, historical trending, alarm
and event reporting, online configuration tools and PLC connectivity to a
premiere graphical development environment, G.
BridgeVIEW makes use of an intuitive graphical user interface combined
with a powerful graphical programming language, G, that enables you to
perform data acquisition and analysis, create an operator interface or
Human Machine Interface (HMI), and develop adv anced supervisory
control applications.
1
BridgeVIEW provides the following features for the development of your
Industrial Automation applications.
•Graphical human-machine interface (HMI)
•Easy-to-use, fill in the blank configuration utilities
•Graphical programming tools
•Real-Time Database (RTDB)
•Historical data collection and trending (Citadel)
•Alarm and event reporting and logging
•Security
•Connectivity to PLC and industrial device networks
BridgeVIEW is distributed on a CD-ROM that includes the complete
BridgeVIEW 2.0 release.
The Windows 95/NT version of BridgeVIEW runs on any system that
supports Windows 95 or W indows NT 4.0. A minimum of 24 MB of RAM
is required for this version to run effectively. We recommend 32 MB of
RAM and at least 30 MB of swap space available on your system.
Note
Installation
The standard BridgeVIEW installation requires approximately 110 MB of disk
space. A full installation requires approximately 150 MB. If you plan to install the
NI-DAQ Server as well, an additional 30 MB of disk space is required.
Complete the following steps to install BridgeVIEW.
1.Insert the CD in your CD-ROM drive.
2.Run the BridgeVIEW installer.
a.If you have Windows 95 or Windows NT 4.0 and your system
uses the AutoPlay feature, the Welcome to BridgeVIEW screen
appears a short time after you insert the CD.
b.If you have a system not using AutoPlay, run the following
program:
X
:\bvsetup.exe
X
where
is the letter of your CD-ROM drive.
3.Choose an installation. The installer offers several installation types:
Standard, Full, Minimum, and Custom. The Standard installation
requires approximately 110 MB. The Full installation, which also
includes Data Acquisition, GPIB, and VISA libraries and examples,
requires approximately 150 MB of disk space. The Standard
installation is recommended.
4.After selecting an installation, follow the instructions that appear on
your screen.
Note
If you plan to use National Instruments Data Acquisition (DAQ) devices, VISA, or
GPIB instrumentation, you can perform either the Full installation, which installs
all necessary drivers and example programs, or the Custom installation, in which
you select the items to install.
After you have installed BridgeVIEW completely, it is ready to run.
You migh t need to re-boo t your machine after installation so that updated
system, DAQ, VISA, or GPIB drivers can be loaded properly.
BridgeVIEW is a software package specifically targeted at industrial
automation applications. BridgeVIEW provides configurable solutions for
common HMI and SCADA functions while leveraging the flexibility of
graphical programming. BridgeVIEW is built around the Gprogramming
language, created by National Instruments Corporation.
With BridgeVIEW, you can acquire data and control one or more
distributed devices in an overall facility. BridgeVIEW can change set points
or send control instructions to the individual devices while monitoring the
entire system. It also can gather information like alarms and measurement
points from these devices.
Common devices used for data acquisition include Programmable Logic
Controllers (PLCs), plug-in Data Acquisition boards, and other distributed
Input/Output (I/O) modules. BridgeVIEW device servers communicate
with these non-plug-in devices through RS-232, RS-485, TCP/IP, DDE,
netDDE, direct I/O, or other proprietary interfaces. BridgeVIEW device
servers provide the necessary protocol software to communicate with
thesedevices. BridgeVIEW also operates directly with OPC servers.
Chapter 1 Introduction
How Does BridgeVIEW Work?
BridgeVIEW uses a combination of tags, events, and data. A tag is a
connection to a real-world I/O point, while an event is anything that
happens to a tag or to the BridgeVIEW Engine in general. The
BridgeVIEW Engine communicates with device servers on one end,
andwith your HMI application at the other end. The BridgeVIEW
Enginemaintains a Real-Time Database (RTDB) of tag information and
logs historical data and events. You can build your HMI to interface with
the BridgeVIEW Engine using virtual instruments (VIs) to read and write
tag values, view alarm information and trend data. A virtual instrument is
a BridgeVIEW function, written in the graphical programming language G.
For more information about G, see any of the chapters in the G Tutorial
section of this manual.
Start by configuring all the tags in your system with the Tag Configuration
Editor. Then, you can launch the BridgeVIEW Engine, which reads your
configuration file and starts monitoring tags, logging data and events. You
can create your HMI application to display tag values, trends, and alarms.
You also can acknowledge alarms and control output tags. You can build
the HMI using BridgeVIEW VIs to read and write tag values, view alarm
information, acknowledge alarms, view real-time trends and retrieve
historical data. For more information about how to get started with
BridgeVIEW, see the Where Should I Start? section at the end of this
chapter.
G is the easy-to-use graphical data flow programming language
BridgeVIEW is based upon. G simplifies scientific computation,
processmonitoring and control, test and measurement, and a wide
varietyof other applications.
G was first introduced by National Instruments as the programming
language behind LabVIEW, the program development application used
commonly for test and measurement purposes. BridgeVIEW has taken all
the functionality of G and enhanced it for your industrial automation needs.
The G Tutorial section of this manual covers the functionality of G that you
need to get started with most BridgeVIEW applications. For a more
extensive explanation of BridgeVIEW functionality, see the
GProgramming Reference Manual.
The basic concepts of G that are covered in this manual are as follows:
• VIs—Virtual instruments (VIs) have three main parts: the front panel,
the block diagram, and the icon/connector. The front panel specifies
the user interface of the VI. The block diagram consists of the
executable code that you create using nodes, terminals, and wires.
With the icon/connector, you can use a VI as a subVI in the block
diagram of another VI. For more information about VIs, refer to
Chapter9, CreatingVIs, and Chapter10, Customizing VIs.
• Loops and Charts—G has two structures to repeat execution of a
sub-diagram—the While Loop and the For Loop. Both structures are
resizable boxes. You place the subdiagram to be repeated inside the
border of the loop structure. The While Loop executes as long as the
value at the conditional terminal is TRUE. The For Loop executes a set
number of times. Charts are used to display real-time trend information
to the operator. For more information about loops and charts, refer to
Chapter11, Loops and Charts.
• Case and Sequence Structures—The Case structure is a conditional
branching control structure, which executes a subdiagram based on
certain input. sequence structure is a program control structure that
executes its subdiagrams in numeric order. For more information about
Case or Sequence structures, refer to Chapter12, Case and Sequence
• Attribute Nodes—Attribute nodes are special block diagram nodes that
you can use to control the appearance and functional characteristics of
controls and indicators. For more information about attribute nodes,
refer to Chapter13, Front Panel Object Attributes.
• Arrays, Clusters and Graphs—An array is a resizable collection of
data elements of the same type. A cluster is a statically sized collection
of data elements of the same or different types. Graphs commonly are
used to display data. For more information about arrays, clusters, and
graphs, refer to Chapter14, Arrays, Clusters, and Graphs.
• VI Server—The VI Server allows you to control when a VI is loaded
into memory, run, and unloaded from memory. For more information
about VI Control VIs, refer to Chapter15, Application Control.
A tag value is acquired and/or controlled by a device server that
communicates with the BridgeVIEW Engine and can be read or set by
aVIin your HMI application. Tags can be of the following types: input,
output, Input/Output, or memory. You can configure tags through the
TagConfiguration Editor. A tag configuration consists of its data type,
connection, scaling, operations, and alarms settings. For more information
about this topic, refer to Chapter3, Tag Configuration.
Data Type
A tag datatype can be analog, discrete, bit array, or string. Analog tags
have continuous values with a specified range (such as 0.0 to 100.0).
Discrete tags have values that are either ON (1) or OFF (0). Bit array tags
are comprised of up to 32 bits, each of which can have an ON (1) or OFF(0)
state. String tags consist of ASCII characters or binary data and can be of
any length.
• Access rights (input only, output only, Input/Output, or memory)
•Server name
• I/O group name
• Item name
• Access path (for OPC servers)
Scaling
Scaling controls the type of scaling to perform on a tag when
communicating with a device server, and the expected engineering
rangeand units for the tag.
Operations
You can specify how the BridgeVIEW Engine updates the Real-Time
Database (RTDB), when it logs the tag data to disk, if it logs events
associated with the tag, and what value exists in the database at startup.
Theoperations that can be performed on a tag are as follows:
• Updating the Real-Time Database
• Historical logging
• Event logging
• Event printing
Alarms
An alarm is an abnormal process condition. For example, an analog
tagcanbe configured to be in a HI alarm state when its value is greater
than25.You can set alarm limits for a tag in the Tag Configuration Editor.
Each alarm limit has a priority associated with it to determine the severity
of the alarm.
An event is something that happens within the BridgeVIEW system.
Events can be divided into two groups: those that pertain to individual
tagsand those that pertain to the overall BridgeVIEW system. Events
pertaining to tags include the following:
• A tag going in or out of alarm
• An operator changing the value of a tag
• An operator acknowledging an alarm
Events pertaining to the system include the following:
• The launching or shutting down of the Engine
• A new operator logging on
• An error from a server
The Engine also maintains alarm summary and event history information
pertaining to tags. This information can be viewed by the user’s HMI and/or
be logged to disk.
Historical Data Logging and Extraction
You can extract data from the historical database to view the trend of tag
data over time. The BridgeVIEW Engine manages logging data to the
Citadel Historical Database. A trend is a view of data over time. Trends can
be real-time (current data) or historical (logged data). You can view logged
data with a user interface (HMI) or with the Historical Trend Viewer
(HTV). For more information about historical data logging and extraction
or the Citadel Historical Database, see Chapter6, Historical Data Logging
andExtraction, or AppendixB, Citadel and Open Database Connectivity.
Chapter 1 Introduction
Security
Environment security is built into BridgeVIEW and determines access to
certain parts of the BridgeVIEW environment. BridgeVIEW security is
broken into two general categories: