Chapter 1
Introduction
1-8
©
National Instruments Corporation
What Is the BridgeVIEW System Architecture?
The BridgeVIEW system contains three sets of processes: the user HMI
Application, the BridgeVIEW Engine, and industrial automation device
servers, as shown in Figure 1-1. These processes interact through a
client-server relationship.
Figure 1-1.
BridgeVIEW Architecture
The BridgeVIEW Engine, with any device servers, runs as a separate
process independent of your HMI application. Your HMI application is
built as a collection of VIs developed using the G programming language.
BridgeVIEW maintains a high performance Real-Time Database in
the BridgeVIEW Engine that provides information to client applications.
The BridgeVIEW Engine also performs other functions including
the following:
•
Data acquisition, engineering unit (EU) scaling, and alarm processing
•
Alarm and event logging
•
Historical data collection and trending
EU scaling converts the Raw Range value from the device server to the
engineering value used in the user application and vice versa.
User HMI Application
The end user of the BridgeVIEW system sees and interacts with an
HMI. The HMI application is a collection of VIs that you build with the
G programming language in BridgeVIEW. You build VIs that interact
Tags
• EU Scaling
• Alarming
• Event/Alarm Logging
• Trending
PLC
DAQ
OPC
Other (including DDE)
HMIs
Real-Time Database
Servers
VIs
BridgeVIEW
Engine