Schneider Electric Monitor Pro User Guide

FactoryLink 7
Conversion Guide
FactoryLink / Conversion Guide
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Version 7.0
•
•
•
•
© Copyright 2000 United States Data Corporation. All rights reserved.
NOTICE:
The information contained in this document (and other media provided herewith) constitutes
confidential information of United States Data Corporation ("USDATA") and is protected by
copyright laws and international copyright treaties, as well as other intellectual property laws
and treaties. Such information is not to be disclosed, used or copied by, or transferred to, any
individual, corporation, company or other entity, in any form, by any means or for any
purpose, without the express written permission of USDATA.
The information contained in this document and related media constitutes documentation
relating to a software product and is being provided solely for use with such software product.
The software product was provided pursuant to a separate license or other agreement and such
information is subject to the restrictions and other terms and conditions of such license or other
agreement.
The information contained in this document and related media is subject to change without
notice and does not represent a commitment on the part of USDATA. Except for warranties, if
any, set forth in the separate license or other agreement relating to the applicable software
product, USDATA makes no warranty, express or implied, with respect to such information or
such software product.
USDATA and FactoryLink are registered trademarks of United States Data Corporation in the
United States and/or other countries. Open Software Bus is a registered trademark licensed to
United States Data Corporation. All other brand or product names are trademarks or registered
trademarks of their respective holders.
Table of Contents
Table of Contents...................................................................................... 3
Audience ...............................................................................................................................
Structure of the FactoryLink Conversion Guide ..................................................................
How to Use This Guide ........................................................................................................
Getting Help .........................................................................................................................
Chapter 1
7
7
7
7
Conversion Overview................................................................................ 9
FactoryLink 7.0 Overview ................................................................................................... 9
Client/Server Environment ....................................................................................... 9
Configuration Explorer vs. Configuration Manager ............................................... 10
New Development Tools ......................................................................................... 10
Client Builder vs. Application Editor ...................................................................... 10
Conversion Overview ......................................................................................................... 12
USER vs. SHARED Domain ............................................................................................. 13
Existing Applications ............................................................................................. 13
Conversion Considerations .................................................................................... 13
Conversion Procedure ........................................................................................................ 15
FLCONVERT in the Command Prompt Window ..................................................... 15
FLCONVERT in Configuration Explorer ................................................................ 15
Chapter 2
Converting Alarm................................................................................... 17
Alarm Task Overview .........................................................................................................
Architecture Comparison ...................................................................................................
Distributed Alarm Logging Task in FactoryLink Pre-7.0 ........................................
Distributed Alarm Logging Task in FactoryLink 7.0 ...............................................
Conversion Procedure ........................................................................................................
Step 1: Convert the FactoryLink Application ..........................................................
Step 2: Review Alarm Definitions and Alarm Logger Information ..........................
Step 3: Configure the Alarm Server ........................................................................
Step 4: Configure the Interval Timer Information Table ..........................................
17
18
19
21
23
24
25
26
29
FactoryLink / Conversion Guide / 3
Step 5: Configure the System Configuration Table ..................................................
Step 6: Create a New Client Builder Project ...........................................................
Step 7: Set Up the Alarm Parameters in Client Builder ..........................................
Step 8: Set Up the Alarm View Display ...................................................................
Step 9: Set up the Alarm Viewer Properties ............................................................
Chapter 3
30
32
34
42
45
Converting Trend ................................................................................... 51
Trend in FactoryLink Pre-7.0 Versions .............................................................................. 51
Overview ................................................................................................................ 51
Trend Configuration ............................................................................................... 52
Trend in FactoryLink 7.0 .................................................................................................... 53
Conversion Procedure ........................................................................................................ 54
Converting Historical Trend ................................................................................... 54
Converting Real-Time Trend ................................................................................ 101
Chapter 4
Converting Database Browser.............................................................. 115
Database Browser Task ....................................................................................................
Database Browser Control ................................................................................................
Browser Task vs. Browser Control ...................................................................................
Conversion Considerations ...............................................................................................
Conversion Procedure ......................................................................................................
Examples: Database Browser vs. Database Browser Control ...............................
Chapter 5
115
115
116
117
119
129
Converting Graphics ............................................................................ 143
FactoryLink 7.0 Graphic Tools .........................................................................................
Conversion Considerations ...............................................................................................
Converting USER-Domain Tags to SHARED .......................................................
File Directories ....................................................................................................
ECSConvert.exe ...................................................................................................
Bitmap Files .........................................................................................................
Converted Object Types .......................................................................................
Converted Animation Types ..................................................................................
Conversion Procedure ......................................................................................................
Step 1: Create a New Project in Client Builder .....................................................
Step 2: Configure the OPC Server ........................................................................
4 / FactoryLink / Conversion Guide
143
144
144
145
145
147
148
149
151
152
154
Step 3: Convert an Application ............................................................................. 155
Evaluation ......................................................................................................................... 157
Summary .......................................................................................................................... 158
Chapter 6
Miscellaneous Conversion Issues......................................................... 159
Converting an Application with Existing Data ................................................................
NetDTL ............................................................................................................................
ODBC Historian ...............................................................................................................
............................................................................................................................
Converting Third-Party Driver or PAK Task (6.0.4 or Earlier) ........................................
Converting from Alarm Logger to Distributed Alarm Logger .........................................
Banner and Output Lines .....................................................................................
Multiple Invocations ............................................................................................
Limitations ...........................................................................................................
Converting Your Applications ...............................................................................
Possible Changes to Improve Performance ..........................................................
Distributed Alarm Logger Supersedes Alarm Supervisor ................................................
PowerSPC Supersedes Statistical Process Control (SPC) ................................................
PowerVB ..........................................................................................................................
160
160
160
160
161
162
162
162
163
165
168
169
170
171
Configuration of the OPC Server......................................................... 173
Index .................................................................................................... 181
FactoryLink / Conversion Guide / 5
6 / FactoryLink / Conversion Guide
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Preface
The FactoryLink Conversion Guide presents basic concepts necessary to understand how
FactoryLink conversion works. It also provides the technical information to users of
FactoryLink systems who need to convert their applications from earlier versions of
FactoryLink to 7.0.
A UDIENCE
The major audience of this guide is users of early versions of FactoryLink who need to upgrade
their systems to the 7.0 version.
S TRUCTURE
OF THE
F ACTORY L INK C ONVERSION G UIDE
The FactoryLink Conversion Guide contains six chapters:
• Chapter 1, “Conversion Overview”
• Chapter 2, “Converting Alarm”
• Chapter 3, “Converting Trend”
• Chapter 4, “Converting Database Browser”
• Chapter 5, “Converting Graphics”
• Chapter 6, “Miscellaneous Conversion Issues”
H OW
TO
U SE T HIS G UIDE
The material in this guide is presented in a learning order. We recommend you read the entire
guide to familiarize yourself with all the information before you proceed to convert your
application.
G ETTING H ELP
For help, contact your USDATA Tier One Partner (TOP) or visit the USDATA Web site
(www.USDATA.com) to locate a TOP in your region.
FactoryLink / Conversion Guide / 7
•
PREFACE
•
Getting Help
•
•
8 / FactoryLink / Conversion Guide
•
•
•
•
Chapter 1
Conversion Overview
This chapter describes the new features and tools of FactoryLink 7.0 and provides an overview
on converting from earlier versions to 7.0. It also discusses the domain issue and the
conversion procedure.
F ACTORY L INK 7.0 O VERVIEW
FactoryLink 7.0 is a multitier software for a SCADA (Supervisory Control and Data
Acquisition) application built exclusively for the Microsoft Windows NT platform. It provides
a powerful and intuitive configuration environment that gives access to a proven high
performance architecture. FactoryLink 7.0 also provides new tools to support the creation of a
highly functional graphical user interface.
The following subsections discuss the new features in the 7.0 release.
Client/Server Environment
FactoryLink 7.0 consists of distinctive client and server functions. The server supports the
collection, processing, and logging of data, while the client provides all user interface
functionality for engineering and operational activities. The automated process can run entirely
under the control of a server and without any human intervention. One or more client stations
are used to interact with the system in operation and to develop and maintain the custom
application.
The FactoryLink 7.0 installation procedure reflects the distinctive server and client functions
by prompting for both server and client options. While both types of options can be installed
on the same computer, they can also be installed on different computers on an enterprise
network. The server installation installs the run-time components, such as executable files and
supporting utilities to run applications. The client installation installs the configuration and
visualization tools, including Configuration Explorer, Client Builder, and WebClient.
FactoryLink 7.0 provides an open architecture through its support for both OPC client and
server functions. Both of these are provided as standard with the server. FactoryLink 7.0 is also
highly extensible through the use of the PAK and CFKPAK APIs.
FactoryLink 7.0 runs as an NT Service. This means that the application is started when the
node on which the application is running is turned on. This allows the application to begin
acquiring, logging, and processing data, irrespective of whether a user logs into the system. A
FactoryLink / Conversion Guide / 9
•
CONVERSION OVERVIEW
•
FactoryLink 7.0 Overview
•
•
user can either log on to the system or connect remotely through any of the supported clients to
access and visualize and control the system.
Configuration Explorer vs. Configuration Manager
In FactoryLink 7.0, Configuration Explorer takes the place of the Configuration Manager in
earlier versions of FactoryLink. It utilizes Microsoft DNA component architecture, has the
look and feel of a standard Microsoft product, and functions as a client so that it can be used to
configure and run applications on any FactoryLink server on the enterprise network. It also
supports simultaneous application development by multiple developers.
For information on Configuration Explorer, refer to the Configuration Explorer User Guide.
New Development Tools
FactoryLink 7.0 has two new development tools, Generate Records and Application Objects,
to increase development productivity and provide a more real-world object approach to
application development.
• Generate Records provides the ability to instantiate large numbers of records into a
configuration table by defining record-generation rules in a user-friendly editor.
• Application Objects allows developers to assemble multiple types of configuration
information (such as PLC read, scaling, alarming, and logging) in a single hierarchical
object, such as a pump object or a switch object, that represents a real-world object. These
objects can then be used to instantiate one or many pumps or switches in an application,
with all the associated information automatically configured.
Both these tools support multiple data sources, such as spreadsheets or text files, to provide
specific data for the instantiated configuration objects.
For information on these two tools, refer to the Configuration Explorer User Guide.
Client Builder vs. Application Editor
FactoryLink 7.0 introduces a new graphics product, Client Builder, to take the place of
Application Editor in earlier versions. However, users of FactoryLink 7.0 can continue to use
Application Editor if they choose.
Client Builder has a standard Microsoft look and feel, utilizes ActiveX technology, and is a
client implementation. It interfaces to the FactoryLink server as an OPC client of the
FactoryLink OPC Server. It is a tool for both design time and run time. A single instance of
Client Builder can be connected to multiple FactoryLink servers, or multiple Client Builder
instances can be connected to one FactoryLink server.
10 / FactoryLink / Conversion Guide
CONVERSION OVERVIEW
FactoryLink 7.0 Overview
In addition to the same basic graphics-animation capabilities as supported by the legacy
graphics product, Client Builder includes ActiveX controls for viewing alarm and trend data
and for browsing database information. Client Builder can host third-party ActiveX controls,
including the WebClient control.
For information on Client Builder, refer to its online help.
FactoryLink / Conversion Guide / 11
•
CONVERSION OVERVIEW
•
Conversion Overview
•
•
C ONVERSION O VERVIEW
FactoryLink 7.0 includes all the legacy components of the 6.6.0 release. All existing
applications can be upgraded to 7.0 by the FLCONVERT utility. They can run without any
modification after being converted to 7.0. Application conversion, while always a requirement
of previous upgrades, is more significant for this upgrade in order to support the new features
in the 7.0 release, such as Configuration Explorer and Application Objects.
Use the FLCONVERT utility to convert existing applications before any attempt to access them
with FactoryLink 7.0. Protection has been added to prevent the use of FactoryLink 7.0
development and run-time modes with previous application versions. Once converted to
FactoryLink 7.0 compatibility, applications will NOT be accessible using FactoryLink 6.x
versions.
Note: FactoryLink only supports conversion of applications currently
running in version 4.3.0 or higher. If you need help to convert an
application with a version prior to 4.3.0, please contact USDATA
Customer Support.
The application composition in FactoryLink 7.0 is different from previous versions:
• In pre-7.0 versions, graphics files were a fundamental part of the application and could be
restored with the application. Now that Client Builder provides a client architecture for
visualization, graphics are separate from the server configuration.
• In 7.0, different client configurations can access the same server application. A new utility,
FVARCHIVE, is included to save Client Builder projects. It can then be used to restore the
saved Client Builder projects to any client node.
• In 7.0, the old FactoryLink 6.x MULTIPLATFORM SAVE (MPS) is now known as SINGLE
FILE SAVE. FactoryLink 7.0 can recognize and restore pre-7.0 multiplatform saves, but
7.0’s SINGLE FILE SAVE cannot be accessed by pre-7.0. versions.
• The FactoryLink 7.0 server configuration can be saved and restored using the traditional
FLSAVE and FLRESTORE commands. Make sure to use FLSAVE to save the server
configuration and use FVARCHIVE to save Client Builder projects.
12 / FactoryLink / Conversion Guide
CONVERSION OVERVIEW
USER vs. SHARED Domain
USER
VS .
SHARED D OMAIN
In previous versions of FactoryLink, USER-domain tags were used for many purposes, such as
the following:
• Graphics navigation
• Logic dependent upon graphic being displayed
• Database browsing
• Various kinds of usage created by individual users for various purposes
With FactoryLink 7.0, USDATA’s recommended architecture is a central SCADA Server with
Rich Clients. The SCADA Server will process only SHARED data, and all USER logic will be
handled in the Client Builder applications.
Client Builder provides functionality capable of fully replacing the USER domain. It is
strongly recommended that all new FactoryLink 7.0 applications be built without using the
USER domain.
Existing Applications
As we know, virtually every existing FactoryLink application makes use of the USER domain.
In most cases, it would be an enormous undertaking to completely convert all USER domain
logic to Client Builder before running the application with FactoryLink 7.0. For this reason,
USDATA decides to retain the USER domain in the 7.x versions so that users have sufficient
time and flexibility to gradually convert applications from the USER domain logic to Client
Builder. The time between 7.0 and 8.0 versions should be considered as a transition period, and
users should take advantage of the 7.x versions to migrate their applications away from the
USER domain. Timely migration is very important since USDATA plans to remove the USER
domain in FactoryLink 8.0.
Conversion Considerations
Before you convert from earlier versions of FactoryLink to 7.0, read the following information
to help you decide how to migrate to FactoryLink 7.0.
Scenario 1: Use WebClient Instead of Client Builder
If you continue to use WebClient and do not use Client Builder in 7.0, perform the following
steps:
1 Run FLCONV to convert your application to 7.0.
2 Use Configuration Explorer and Application Objects for ongoing application development.
FactoryLink / Conversion Guide / 13
•
CONVERSION OVERVIEW
•
USER vs. SHARED Domain
•
•
Scenario 2: Use Client Builder (One User/Client Only)
If you use Client Builder and there is only one user/client, perform the following steps:
1 Run FLCONV to convert your application to 7.0.
2 Move all USER-domain tags to the SHARED domain by performing the following steps:
(1) Open a DOS/Command Prompt window and change directory to application directory.
For example, D> C:, then C> CD %FLAPP%.
(2) Start BH_SQL.
For example, C> BH_SQL.
(3) Enter the command to change all tags to SHARED.
For example, SQL> update object set tagdomain=’SHARED’ where tagdomain=’USER’
(4) Quit BH_SQL.
For example, SQL> quit
(5) Run the application to test it.
3 Run ECSConvert to convert your existing graphics to Client Builder mimic displays. The
application can be incrementally migrated from the previous USER-domain logic to Client
Builder logic one graphic at a time.
For information on converting graphics, refer to Chapter 5, “Converting Graphics.”
Scenario 3: Use Client Builder (More Than One Client/User)
Unfortunately, there is no easy migration solution for FactoryLink 7.0 when more than one
user/client is needed. USDATA suggests that you work toward learning Client Builder by
temporarily using a single user/client as described in Scenario 2.
A patch release will be available within a few weeks of the 7.0 release that will allow the
USER-domain tags to be accessed from Client Builder. This will facilitate a quick conversion
of a multiuser 6.x application to FactoryLink 7.0 using USER-domain tags. The application
can then be incrementally migrated away from the USER domain one graphic at a time.
14 / FactoryLink / Conversion Guide
CONVERSION OVERVIEW
Conversion Procedure
C ONVERSION P ROCEDURE
After restoring a FactoryLink application on a new platform or a new FactoryLink version, you
must convert it using the FLCONVERT utility. Once you convert the application, it is no longer
compatible with the previous version of FactoryLink.
Caution: Do not abort the conversion during processing as this
corrupts the application.
FLCONVERT in the Command Prompt Window
There are no command line switches or options for this utility. Use the following syntax:
FLCONV <application directory>
Perform the following steps:
1 Back up the application using a platform-specific FLSAVE.
Note: For information on FLSAVE, FLREST, FLCONV, or any other
utilities, refer to the Utilities chapter in the FactoryLink Task
Configuration Reference Guide.
2 Start the FLCONV utility. A dialog is displayed containing the drive and path of the application
to convert.
3 Verify that the drive and the path are correct.
4 Choose one of the two answers:
Y
Converts the application.
N
Cancels the conversion.
The application files are now converted.
FLCONVERT in Configuration Explorer
Perform the following steps:
1 Add the application for conversion into Configuration Explorer (refer to the Configuration
Explorer User Guide).
2 Back up the application by right-clicking the application and selecting SAVE from the pop-up
menu (refer to the Utilities chapter in the FactoryLink Task Configuration Reference Guide).
FactoryLink / Conversion Guide / 15
•
CONVERSION OVERVIEW
•
Conversion Procedure
•
•
3 Right-click the application and select Convert in the pop-up menu (see Figure 1-1).
Figure 1-1 Select Convert
4 The conversion process completes when the Output box reads: FLCONV successfully
completed (see Figure 1-2).
Figure 1-2 FLCONV Successfully Completed
16 / FactoryLink / Conversion Guide
•
•
•
•
Chapter 2
Converting Alarm
This chapter provides an overview of the Alarm task in FactoryLink 7.0. It compares the
functionality of both the Alarm task in earlier versions of FactoryLink and the Alarm ActiveX
Control in FactoryLink 7.0. It also provides a step-by-step description on migrating the alarm
information from pre-7.0 versions to 7.0.
A LARM TASK O VERVIEW
Data collected by FactoryLink is stored as a data element (tag) in a real-time database. Each
time data is collected, the value stored in the real-time database for an element is overwritten
by the new data.
Using Distributed Alarm Logger, you can establish criteria for getting an alarm for any defined
data element in the real-time database. If the value for the element meets the established alarm
criteria, an alarm message is displayed on the Alarm Viewer screen for the FactoryLink
operator. The element is then monitored throughout the alarm cycle in the Alarm Viewer until
the element value no longer meets the alarm criteria.
The Alarm task interacts with the Historian task to write alarm records to a database. The
alarm data is logged to the relational database in the same way the FactoryLink Database
Logger performs logging in table format as the alarm occurs, when the alarm is acknowledged,
or after an alarm has returned to the normal status.
At run time, operators can view alarms that have met established criteria for any defined data
element in the real-time database, acknowledge them, and delete them.
For detailed information on the Alarm task, refer to the “Alarm Control” chapter in the
FactoryLink Task Configuration Reference Guide.
FactoryLink / Conversion Guide / 17
•
CONVERTING ALARM
•
Architecture Comparison
•
•
A RCHITECTURE C OMPARISON
The most important change in FactoryLink 7.0 architecture is that there is no USER domain
any more; everything is in a single SHARED domain. It is a client/server environment where
the Alarm ActiveX Control viewer is used to look at the alarms. The Alarm ActiveX Control is
configured using Client Builder, the new graphical user interface for FactoryLink 7.0, which
takes the place of Application Editor in previous versions. This new method gives you more
flexibility in displaying alarms in the system within the client/server paradigm.
For information on Client Builder, refer to Chapter 1, “Conversion Overview” of this guide
and the Client Builder online help.
Table 2-1 compares the alarm functionality between FactoryLink pre-7.0 and 7.0 versions:
Table 2-1 Functionality Comparison
Functionality
FactoryLink Pre-7.0
FactoryLink 7.0
Alarm Definitions
Yes
Yes
Alarm Logging
Yes
Yes
Alarm Server
No
Yes
Alarm Viewer
Yes in USER Domain
Yes, task replaced by the
server-side Alarm Server and
Alarm ActiveX Control in
Client Builder
18 / FactoryLink / Conversion Guide
CONVERTING ALARM
Architecture Comparison
Distributed Alarm Logging Task in FactoryLink Pre-7.0
The Distributed Alarm Logging task in pre-7.0 versions consists of two tasks: the Distributed
Alarm Logger task (AL_LOG) in the SHARED domain and Alarm Viewer task (AL_VIEW)
in the USER domain. If an application has multiple users (through WebClient), then there will
be multiple instances of AL_VIEW running on the FactoryLink application.
The AL_LOG task is configured by filling in the information in the Alarm Definition
Information panel (see Figure 2-1).
Figure 2-1 Alarm Definition Information Panel
FactoryLink / Conversion Guide / 19
•
CONVERTING ALARM
•
Architecture Comparison
•
•
The AL_VIEW task presents alarms and alarm statuses through tags defined in the Alarm
View Output Information pane (see Figure 2-2).
Figure 2-2 Alarm View Output Information Panel
As part of a new FactoryLink application, an alarm summary graphic utilizes these tags to
display the alarm information to the user.
20 / FactoryLink / Conversion Guide
CONVERTING ALARM
Architecture Comparison
Distributed Alarm Logging Task in FactoryLink 7.0
In FactoryLink 7.0, the Distributed Alarm Logging task consists of two tasks: the Distributed
Alarm Logger task (AL_LOG) and the Alarm Server task (ALARM_SRV). The Distributed
Alarm Logger task remains the same; that is, the alarms are still defined in the Alarm
Definition Information panel (see Figure 2-3). However, the Alarm Server task is new and
replaces the Alarm Viewer task in pre-7.0 versions. It is configured in the Distributed Alarm
Server panel (see Figure 2-4).
Figure 2-3 Alarm Definition Information Panel
FactoryLink / Conversion Guide / 21
•
CONVERTING ALARM
•
Architecture Comparison
•
•
Figure 2-4 Distributed Alarm Server Panel
The two mailbox tags are used for the Alarm Server to communicate with the Alarm Logger.
The poll trigger determines the time interval for communications between the Alarm Server
and the Alarm Logger. This trigger needs to be set up in the Interval Timer Information panel
(see Figure 2-5).
Figure 2-5 Interval Timer Information Panel
According to this Interval Timer Information panel, the Alarm Server will poll the alarm
logger every three seconds to check for alarms.
In FactoryLink 7.0, viewing alarms is done through the Alarm ActiveX Control that is
configured in Client Builder. It gives you much more flexibility in displaying alarms in the
system in the client/server paradigm. Refer to the following section for details on how to view
alarms in the Alarm ActiveX Control.
22 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
C ONVERSION P ROCEDURE
This section provides step-by-step instructions on how to convert the Alarm task from a
FactoryLink application of an earlier version to 7.0.
Perform the following steps:
1 Convert your FactoryLink application of an earlier version to 7.0.
2 Review the alarm definition settings in Configuration Explorer.
3 Define the Alarm Server parameters in Configuration Explorer.
4 Define the timer entry for the Alarm Server poll interval in Configuration Explorer.
5 Configure the Alarm Server in the System Configuration table in Configuration Explorer.
6 Create a new project and new file in Client Builder.
7 Configure the Alarm Server/Cluster parameters in Client Builder.
8 Create a new alarm view display in Client Builder.
9 Add an Alarm ActiveX Control in Client Builder.
10 Set up the properties for the Alarm ActiveX Control in Client Builder.
FactoryLink / Conversion Guide / 23
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Step 1: Convert the FactoryLink Application
You can convert your FactoryLink application of an earlier version from the Command Prompt
or in Configuration Explorer. For information on FLRestore, FLConvert, and how to convert
the application from the Command Prompt or in Configuration Explorer, refer to the
“Utilities” chapter in the FactoryLink Task Configuration Reference Guide.
To convert your application in Configuration Explorer, right-click the application name in the
Enterprise View and select Convert from the pop-up menu (see Figure 2-6).
Figure 2-6 Configuration Explorer
Your FactoryLink application is converted when the output box displays “FLCONV
successfully completed.”
24 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
Step 2: Review Alarm Definitions and Alarm Logger Information
Perform the following steps:
1 Double-click the Configuration Explorer icon on your desktop. The default Enterprise View
appears as shown in Figure 2-7.
Figure 2-7 Configuration Explorer
2 Review the information in the Distributed Alarm Definitions and the Distributed Alarm
Logger Setup tables. FLConvert automatically converts the information from the original
tables in Configuration Manager to the tables in Configuration Explorer. Therefore, you do not
need to change any information manually.
Note: If you use a different Historian, for example, SQL Server, you
should review your logging options.
FactoryLink / Conversion Guide / 25
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Step 3: Configure the Alarm Server
Perform the following steps to configure the Alarm Server:
1 In the Distributed Alarm Server 7.0-SHARED table, fill in the tag names for Send Mailbox,
Receive Mailbox, and Poll Trigger (see Figure 2-8).
Figure 2-8 Distributed Alarm Server 7.0-SHARED
2 In the Distributed Alarm Server 7.0-SHARED table, right-click tag name
ALARMSRV_SNDMBX and define its properties in the FactoryLink TagEditor dialog box (see
Figure 2-9). Click OK.
Figure 2-9 FactoryLink TagEditor for ALARMSRV_SNDMBX
26 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
Note: For information on defining the properties, refer to the
FactoryLink Task Configuration Reference Guide.
3 Define the properties of ALARMSRV_RCVMBX (see Figure 2-10). Click Apply. Then click OK.
Figure 2-10 FactoryLink TagEditor for ALARMSRV_RCVMBX
FactoryLink / Conversion Guide / 27
•
CONVERTING ALARM
•
Conversion Procedure
•
•
4 Define the properties of ALARMSRV_POLL (see Figure 2-11). Click Apply. Then click OK.
Figure 2-11 FactoryLink TagEditor for ALARMSVR_POLL
5 In the expanded Timers folder, open the Interval Timer Information table. Add
ALARMSRV_POLL to the Tag Name list and set the poll interval time (see Figure 2-12).
Figure 2-12 Interval Timer Information - SHARED
28 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
Step 4: Configure the Interval Timer Information Table
Enter the poll interval time for the poll tag in the Interval Timer Information table (see Figure
2-13).
Figure 2-13 Interval Timer Information
FactoryLink / Conversion Guide / 29
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Step 5: Configure the System Configuration Table
The conversion program makes all the database structure changes that are necessary for
compatibility, but it does not automatically create any entries in the System Configuration
table.
Perform the following steps to enter the Alarm Server information in the System Configuration
table:
1 Open the System Configuration Information table from Configuration Explorer (see Figure
2-14).
Note: For information on the System Configuration table, refer to the
FactoryLink Task Configuration Reference Guide.
Figure 2-14 System Configuration Information - SHARED
2 Click the >> button at the bottom of the dialog box and scroll to the end of the task list.
3 Click the * button to insert a new task.
30 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
4 Use the following information in the System Configuration Information dialog box. Click
Apply.
Task Name
ALARMSVR
Task Description
Alarm Server
Task Group
Run At Startup
Task Option
Sort Order—1
Start Priority—201 (default)
Task Executable
Executable File—bin/alarmsrv
5 Click Yes in the Insert new record dialog box (see Figure 2-15).
Figure 2-15 Insert New Record
6 Close the System Configuration Information dialog box.
FactoryLink / Conversion Guide / 31
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Step 6: Create a New Client Builder Project
Perform the following steps:
1 Double-click the Client Builder icon on your desktop.
2 In the Open Project dialog box, click the New... button (see Figure 2-16).
Figure 2-16 Open Project
3 In the New Project dialog box, fill in the Project Name and Location (see Figure 2-17). Click
OK. A new Client Builder project is created.
Figure 2-17 New Project
32 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
4 From the File menu in the Client Builder window, click New (see Figure 2-18).
Figure 2-18 Client Builder Window
5 In the New Mimic dialog box, click OK (see Figure 2-19). A new Client Builder mimic file is
created.
Figure 2-19 New Mimic
FactoryLink / Conversion Guide / 33
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Step 7: Set Up the Alarm Parameters in Client Builder
In Client Builder, you need to set up Server Types, Alarm Servers for the Server Types, Alarm
Clusters, and Alarm Servers for the Alarm Clusters.
A Setup Shortcut
If you have installed the Starter Application, you can use the following shortcut: copy the
Servers.dat file in the USDATA\Client Builder\Project\Starter\Config Files directory to the
Config Files folder in the directory of your application (see Figure 2-20). Once the
Servers.dat file is in place, you do not need to manually configure the Alarm parameters in
Client Builder; therefore, you can skip Step 7.
Figure 2-20 Copying Servers.dat File
If you did not install the Starter Application, you have no shortcut to take. Therefore, follow
the instructions in the subsections to set up the Alarm parameters.
34 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
I. Set up the Server Types
1 In the Client Builder mimic file you created in Step 6, select Servers from the Tools menu.
The Servers Editor appears as shown in Figure 2-21.
Figure 2-21 Servers Editor
2 Right-click SERVERTYPES. The Communication Manager pane appears on the right side of
the screen as shown in Figure 2-22.
Figure 2-22 Alarm Server Type Configuration
FactoryLink / Conversion Guide / 35
•
CONVERTING ALARM
•
Conversion Procedure
•
•
3 Fill in the following information:
Name
Type
Computer
AlarmServer or any name you want to use.
AlarmFW10
MyComputer
Class ID
Filled in automatically: {CCDE3FE1-56DB-11D3-BF8D-00C04F7E967F}
Prog ID
Filled in automatically: ClientBuilder.AlarmFWMgr
Note: Keep in mind that FactoryLink 7.0, a Client/Server environment,
can have multiple servers as well as multiple clients.
4 Click Set. Then click OK.
36 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
II. Set up the Alarm Server for the Server Types
1 Right-click the newly created server type AlarmServers and select Add Server from the
pop-up menu. The configuration pane appears on the right side of the screen as shown in
Figure 2-23.
Figure 2-23 Alarm Server Configuration.
2 Provide the following information:
Name
AlarmServer1 or any name you wan to use.
Run Time
Computer
Prog ID
Use the drop-down button to choose My
Computer>FLAlarmServer.AlarmServer.1.
Filled in automatically: FLAlarmServer.AlarmServer.1
In the Run Time pane, click the Advanced button to obtain the default
Advanced Server Settings for the Run Time Server (see Figure 2-24).
FactoryLink / Conversion Guide / 37
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Figure 2-24 Run Time Server
Accept the default settings:
- Prog ID: FLAlarmServer.AlarmServer.1
- Class ID: {5AEC3E98-CFB3-11D2-A597-00C04F7D7A54}
- Scan Rate: 1000
- Time Out: 10000
- Reconnection Delay: On Failure—60000; On Shutdown—60000
Click OK.
Design Time
Computer
Prog ID
Use the drop-down button to choose My
Computer>FLAlarmServer.AlarmServer.1.
Filled in automatically: FLAlarmServer.AlarmServer.1
In the Design Time pane, click the Advanced button to obtain the default
Advanced Server Settings for the Design Time Server (see Figure 2-25).
38 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
Figure 2-25 Design Time Server
Accept the default settings:
- Prog ID: FLAlarmServer.AlarmServer.1
- Class ID: {5AEC3E98-CFB3-11D2-A597-00C04F7D7A54}
- Scan Rate: 1000
- Time Out: 10000
Click OK.
Storage Name
Leave it blank. Not implemented for FactoryLink 7.0.
Your Alarm Server is now set up.
FactoryLink / Conversion Guide / 39
•
CONVERTING ALARM
•
Conversion Procedure
•
•
III. Set up the Alarm Clusters
1 In the Servers Editor, right-click CLUSTERS and select New. The configuration pane appears
on the right side of the screen as shown in Figure 2-26.
Figure 2-26 Alarm Cluster Configuration
2 Provide the following information:
Name
Server Type Name
Use any name for the cluster.
Select the Alarm Server Type you just created.
3 Click Set. Then click OK.
The Alarm Cluster is now set up.
40 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
IV. Set up the Alarm Server for the Alarm Cluster
1 In the Servers Editor, right-click AlarmCluster that you just created and select Add Member
from the pop-up menu. The configuration pane appears on the right side of the screen as shown
in Figure 2-27.
Figure 2-27 Alarm Cluster Server Configuration
2 Provide the following information:
Name
Server Name
Rank
Use any name for the cluster member
Select an alarm server from the drop-down list. Notice that the content of
the drop-down list matches the servers you defined earlier.
This field shows the rank of the server within a particular cluster of servers
and is related to the failure mode. When the highest-ranked server is not
available, the next highest-ranked server is used.
Note: This feature is not implemented for FactoryLink 7.0.
3 Click Set. Then click OK.
The Alarm Server for the Alarm Cluster is now set up.
FactoryLink / Conversion Guide / 41
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Step 8: Set Up the Alarm View Display
In earlier versions of FactoryLink, alarms and their statuses are displayed by tags animated at
an Alarm View display in the USER domain. In FactoryLink 7.0, this is accomplished by the
Alarm ActiveX Control in Client Builder.
Perform the following steps to set up the Alarm View display:
1 Create a new mimic file in a Client Builder project (refer to Step 6).
2 From the Mode menu, click Design (see Figure 2-28). Now you are in design mode.
Figure 2-28 Set up Mode in Client Builder
3 From the Tools menu, select Preferences>ActiveX Controls. The ActiveX Controls
Configuration dialog box appears as shown in see Figure 2-29.
4 Select the AlarmViewer Control from the Installed ActiveX Controls list on the left side of the
box and click the >> button to move it to the Approved ActiveX Controls list on the right.
The AlarmViewer Control is then listed on the right side of the dialog box. The checked box
means that the control will be listed in Favorites ActiveX Controls in the Insert menu.
42 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
Figure 2-29 ActiveX Controls Configuration
5 From the Insert menu, select Favorites ActiveX Controls>AlarmViewer. The Alarm ActiveX
Control appears as shown in Figure 2-30.
Figure 2-30 Alarm ActiveX Control
You can resize the control by using the size handles.
FactoryLink / Conversion Guide / 43
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Generally, the Alarm ActiveX Control provides the following information:
• Connected to Design Server (Yes/No). This indicates whether or not you are connected to
the Alarm Server that you set up as described in the previous section.
• Alarm Band (Yes/No). This indicates whether this is an alarm band or not. An alarm band
shows up to three alarms at a time and is used to focus on a particular type of alarms.
• Number of Items Displayable at Run Time. this indicates how many lines can be shown
in the Alarm Control box. The number is dependent on the size of the box and the font used
to display the alarm records.
• Colors Available/No Colors available. Color definitions depend on the connection of the
Alarm Control to the server. The range of available colors is determined by the server.
As an example, Figure 2-30 on the previous page presents the following design time Alarm
Control information:
• Connected to Design Server. The value defaults to No for first time access.
• Alarm Band. The defaults to No for first time access.
• Number of Items Displayable at Run Time. The value 4 indicates that four alarm records
can be displayed in the alarm control box.
• No Colors Available. Color definitions are available after the Alarm Control is connected
to the Alarm Server. The range of available colors is determined by the server.
44 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
Step 9: Set up the Alarm Viewer Properties
Perform the following steps to set up the Alarm Viewer properties:
1 Right-click anywhere on the Alarm ActiveX Control and select Properties from the pop-up
menu (see Figure 2-31).
Figure 2-31 Select Properties
2 The AlarmViewer Control Properties dialog box appears, which shows four tabs with the
following information for the configuration setup (see Figure 2-32).
• General. Connect to a server cluster, specify connection cycles, the sort defaults, and
display attributes.
• Colors and Fonts. Choose the font type, field blinking, and colors for all alarms by Alarm
Groups.
• Group Browser. Select the group fields, field attributes and field sequence to display.
Enable group field resizing at run time and select the relative size of the group display.
• Present Alarm List . Select the fields, field size, and the field sequence to display. Also
determine to display the vertical scroll bar, format the date fields, sort keys, and filtering
options.
FactoryLink / Conversion Guide / 45
•
CONVERTING ALARM
•
Conversion Procedure
•
•
Figure 2-32 AlarmViewer Control Properties - General
3 Select the alarm cluster defined earlier. To activate connection to the cluster, click the
Connection button to the right. The red x on the button disappears when the connection is
successful. Connection to the server is essential for design.
46 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
4 Select the groups to appear in the group browser (see Figure 2-33). All predefined alarm
groups are listed.
Figure 2-33 Select Groups
5 Define the other parameters in the General tab as you wish.
Note: For detailed description of the AlarmViewer Control Properties,
refer to the FactoryLink Task Configuration Reference Guide.
FactoryLink / Conversion Guide / 47
•
CONVERTING ALARM
•
Conversion Procedure
•
•
6 Define the parameters in the Color/Font tab (see Figure 2-34). Click OK.
Figure 2-34 AlarmViewer Control Properties - Color/Font
48 / FactoryLink / Conversion Guide
CONVERTING ALARM
Conversion Procedure
7 Define the properties in the Group Browser tab (see Figure 2-35). Click OK.
Figure 2-35 AlarmViewer Control Properties - Group Browser
FactoryLink / Conversion Guide / 49
•
CONVERTING ALARM
•
Conversion Procedure
•
•
8 Define the properties in the Present tab. Click Apply (see Figure 2-36). Click OK.
Figure 2-36 AlarmViewer Control Properties - Present
After you have performed the nine steps, your alarm conversion is completed.
50 / FactoryLink / Conversion Guide
•
•
•
•
Chapter 3
Converting Trend
This chapter provides an overview of the Trend task in both FactoryLink pre-7.0 and 7.0
versions and gives step-by-step instructions on converting from earlier versions to 7.0.
TREND
IN
F ACTORY L INK P RE -7.0 VERSIONS
This section gives an overview and configuration of Trend in pre-7.0 versions of FactoryLink.
Overview
As data is collected or computed by FactoryLink, it is stored as a data element in a real-time
database. Each time data is collected, or computed, the new data overwrites the value stored in
the real-time database for an element. To keep a listing of the data, you store the data in a
relational database.
Trending in previous versions of FactoryLink had two categories: real-time and historical.
Real-time Trending
Real-time only trending allows you to chart data directly from the real-time database. The
real-time database receives and stores data from various sources, such as a remote device, user
input, or computation results from a FactoryLink task. When data is collected and stored in this
database, other tasks can access and manipulate it. As a new value is written to the database,
the old value is overwritten. The new value is displayed on the real-time trend chart. Data
displayed on a real-time trend chart is not saved.
Real-time only trending is a function of the run-time graphics application. Real-time only trend
charts are configured using the real-time database and the Application Editor. For more
information, refer to the FactoryLink Application Editor Guide.
Historical Trending
Historical trending allows you to chart data from the relational database historically or in real
time. The data to include on a historical trend chart is retrieved from a relational database
through Historian. The source of the data to be trended from the database is defined in the
Trend Database Tables panels.
FactoryLink / Conversion Guide / 51
•
CONVERTING TREND
•
Trend in FactoryLink Pre-7.0 Versions
•
•
For more information on historical trending, refer to the FactoryLink ECS Configuration
Guide.
Trend Configuration
In previous versions of FactoryLink, the Trend task worked together with the Historian and
Graphic tasks.
Trend configuration consisted of configuring a Historian to log the data, configuring trending
task to communicate with the Historian and graphics, and graphics editor to create the trend
charts and link it to database tables (via Trend task). Additionally, Trend and Graphics tasks
ran in the USER domain, one per each user.
For more information, refer to the FactoryLink ECS Configuration Guide.
52 / FactoryLink / Conversion Guide
CONVERTING TREND
Trend in FactoryLink 7.0
TREND
IN
F ACTORY L INK 7.0
In FactoryLink 7.0 the Trending task is composed of three components:
• Trend Control is a client of the client/server software architecture. It is an ActiveX control
and contained in Client Builder. The Control’s properties are available for custom
programming. The Trend Control requests data from the Trend Server, which sends the
requested data back to the Trend Control, which then accepts the data.
• Relational Database is a database where all Trend data is stored. This data is historical.
Data in the relational database can come from sources other than FactoryLink’s Real-Time
Data Base (RTDB).
• Trend Server provides services to the Trend Control. It can query any relational database or
many databases simultaneously.
To show the data after the time or event has occurred, you create a Trend chart that fetches data
from a relational database to graphically show the numeric data. To show data in near real
time, you create a Trend chart that fetches data from a relational database as frequently as data
is logged to it.
The FactoryLink 7.0 environment is not composed of SHARED and USER domains as in
previous versions. Everything is in a single SHARED domain. The Trend ActiveX Control is
used to configure and display trends. The Trend Control is configured using the Client Builder,
a new graphical user interface for FactoryLink 7.0.
For more information, refer to the FactoryLink Task Configuration Reference Guide.
FactoryLink / Conversion Guide / 53
•
CONVERTING TREND
•
Conversion Procedure
•
•
C ONVERSION P ROCEDURE
In this document, we will use FLTest.mps to illustrate the conversion process. FLTest.mps is
installed in the USDATA\FactoryLink\FactoryLink\Mps\En directory. You can use it for
practice purposes if you choose to do so.
Because we use FLTest.mps, before we begin the conversion process, we are going to restore
it, using the FLRestore utility, and rename it as TrendConv. For information on FLRestore,
refer to the “Utilities” chapter in the FactoryLink Task Configuration Reference Guide.
If you have an existing application, you may not need to restore the application. You just need
to add it to Configuration Explorer. For information, refer to the Configuration Explorer User
Guide.
Converting Historical Trend
The conversion process for Historical Trend takes nine steps summarized as follows:
1 Convert the previous application to FactoryLink 7.0 format.
2 Review logging information in Configuration Explorer.
3 Document existing Trend configuration in Application Editor.
4 Configure the database Historian.
5 Set up the System DSN.
6 Create a new project and new file in Client Builder.
7 Configure Trend Cluster/Server parameters in Client Builder.
8 Add a Trend ActiveX Control in Client Builder.
9 Set up the properties for the Trend ActiveX Control.
54 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 1: Convert the Previous FactoryLink Application to 7.0
You can convert your FactoryLink application of an earlier version from the Command Prompt
or in Configuration Explorer.
Using the Command Prompt
Use the following command for the Command Prompt:
flconv <directorypathname>
The <directorypathname> is the path of your old application, for example, c:\TrendConv.
Using Configuration Explorer
To convert your application in Configuration Explorer, right-click the application name in the
Enterprise View and select Convert from the pop-up menu (see Figure 3-1).
Figure 3-1 Converting an Application in Configuration Explorer
FactoryLink / Conversion Guide / 55
•
CONVERTING TREND
•
Conversion Procedure
•
•
Your FactoryLink application is converted when the output box displays “FLCONV
successfully completed.”
Showing USER Domain Graphics
In order to show the USER domain graphics, after you add your application to Configuration
Explorer, you need to perform the following steps, in the same way we are illustrating here
with TrendConv:
1 In Configuration Explorer, right-click TrendConv and select Properties from the pop-up
menu (see Figure 3-2).
Figure 3-2 Open Properties
56 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
2 In the TrendConv Properties dialog box, delete “-nShared” for FLRunArgs (see Figure 3-3).
Click OK.
Figure 3-3 TrendConv Properties
FactoryLink / Conversion Guide / 57
•
CONVERTING TREND
•
Conversion Procedure
•
•
Trend Chart Before Conversion
In this document, we will be using trend.g in Application Editor to illustrate the conversion
process (see Figure 3-4):
Figure 3-4 Trend Chart - Before Conversion
58 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 2: Review Logging Information in Configuration Explorer
It is important to review, in advance, the logging information in existing tables that will be
used for the Trend Control configuration.
Perform the following steps to review the logging information:
1 Expand TrendConv in Configuration Explorer.
2 Expand the folders of Data Logging, Database Logging, and Database Logging Control.
3 Right-click the Database Logging Control table and select Open in Form (see Figure 3-5).
Note: You also have the option of opening the table in grid.
Figure 3-5 Open Database Logging Control Table
FactoryLink / Conversion Guide / 59
•
CONVERTING TREND
•
Conversion Procedure
•
•
4 In the Database Logging Control table, note the following information (see Figure 3-6):
Log Name
TREND
Log Trigger
Logtrig
Historian Mailbox
Histmbx
Database Alias
Name
TREND
Database Table
Name
TRENDTBL
Schema Name
TRENDSCH
Figure 3-6 Database Logging Control
60 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
5 Expand the folders of Historians, Historian for dBASE IV (R), and Historian Information for
dBASE IV (R).
6 Open the Trend table and note the following information (see Figure 3-7):
Database Alias
Name
Database Directory
TREND
’{FLAPP}/{FLNAME}
Figure 3-7 Historian Information for dBASE IV (R)
7 Expand the folders of Data Logging, Database Schema Creation, Schema Control, and
TRENDSCH.
FactoryLink / Conversion Guide / 61
•
CONVERTING TREND
•
Conversion Procedure
•
•
8 Open the Index Information table and note the following information (see Figure 3-8):
Index Number
1
Unique Index
Y
Column List
TRENDKEY
Figure 3-8 Index information
Note: For the Trend we are demonstrating in this document, we use
TRENDKEY as Index and FLSEC as the trended data item.
9 Expand the Schema Information folder. Open the TRENDKEY table and note the following
information (see Figure 3-9):
Column Name
FLSEC
Column Type
Smallint
Figure 3-9 Schema Information
62 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
10 Expand the folders of Data Logging, Database Logging, and Database Logging Control.
Open the Database Logging Information table and note the following information (see Figure
3-10):
Tag Name
Column Name
SECTIME
TRENDKEY
Figure 3-10 Database Logging Information
FactoryLink / Conversion Guide / 63
•
CONVERTING TREND
•
Conversion Procedure
•
•
Step 3: Document Existing Trending Configuration in Application Editor
FactoryLink 7.0 uses a new graphics product, Client Builder, in the place of the Application
Editor as used in previous versions. After the conversion process, you have the option of using
either the Application Editor or Client Builder to display the graphics. If you choose to use
Client Builder, you need to go through and document each trend chart that you wish to convert,
because the trend charts are not converted automatically for Client Builder to use.
Perform the following steps to gather the information for Trend charts in Application Editor:
1 In Configuration Explorer, open Application Editor in the Graphics folder.
2 Form the File menu, select trend.g and click OK (see Figure 3-11).
Figure 3-11 Open a File
64 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
3 Click on the Historical Trending chart object.
4 From the Animation menu, click Chart (see Figure 3-12).
Figure 3-12 Animation Menu
5 In the Chart Animation dialog box, note the following information (see Figure 3-13):
Data Source or
Scroll Trigger Tag
TRENDMBX_U
Initial Chart
Duration
360 (Secs)
Chart Scroll
Frequency
2 (Secs)
FactoryLink / Conversion Guide / 65
•
CONVERTING TREND
•
Conversion Procedure
•
•
Figure 3-13 Chart Animation
6 In the Chart Animation dialog box, click Edit Pens.
7 In the Select Pen dialog box, select TRNPEN1 (see Figure 3-14). Click OK.
Figure 3-14 Select Pen
66 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
8 In the Pen properties dialog box, note the pen attributes, such as scale, color changes, line and
marker styles, especially the Data Source for Pen (see Figure 3-15):
Tag
Database
Table
Column/Tag
trn_pen_column
TREND
TRENDTBL
FLSEC
Figure 3-15 Pen Properties
FactoryLink / Conversion Guide / 67
•
CONVERTING TREND
•
Conversion Procedure
•
•
Step 4: Configure the Database Historian
You may need to convert your existing database files so they can be read by the new Trend
Control. The Trend Control needs a System Data Source Name (DSN) in order to access the
data to be trended. For information, refer to “Step 5: Setting up System DSN.”
The DSN requires the use of Visual Fox Pro driver. To configure the System DSN,
FactoryLink 7.0 requires a Database Type of “Free Table Directory.” The Visual Fox Pro driver
expects to see database tables with a “.dbf” extension.
If your DB4_HIST task is currently configured with program arguments of “-m -dbase”, your
log files will have the “.dbf” extension. In this case, you do not need any file conversions to
visualize your historical data or to use the FactoryLink 7.0 Trend Control.
If your DB4_HIST task is NOT currently configured with program arguments of “-m -dbase”,
your log files will have the “.cdb” extension. In this case, you MUST perform file conversions
to visualize your historical data. Setting these program arguments results in FactoryLink 7.0
writing log files with the “.dbf” extension. If you do not need to view your existing data, then
you can delete the log files from the log directory; FactoryLink 7.0 will create the new log files
the next time the application runs.
68 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Perform the following steps to set up the DB4_HIST task:
1 In Configuration Explorer, expand the folders of System and System Configuration.
2 Open the System Configuration Information table in System Grid (see Figure 3-16).
Figure 3-16 Open System Configuration Information Table
FactoryLink / Conversion Guide / 69
•
CONVERTING TREND
•
Conversion Procedure
•
•
3 In the dialog box, click the > button at the bottom to scroll forward to Program Arguments,
and put in -m -dbase in the space provided (see Figure 3-17).
Figure 3-17 System Configuration Information
70 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
4 Select an action on what you should do with your log files by evaluating your situation
illustrated by Table 3-1.
Table 3-1 Evaluate Your Database Files
If you have
.cdb files...
and if you want
to visualize the
history...
then you should...
No
No
Do nothing. The .dbf files you have will be
appended by the Historian. Skip the
remainder of Step 4.
No
Yes
Do nothing; the .dbf files you have will be
appended by the historian. The trend
control can read from your existing files.
Skip the remainder of Step 4.
Yes
No
Delete the log files associated with your
Trend schema. If you do not need any of
the log files, then delete them all. The files
will be generated the next time you start
your application. You can now skip the
remainder of Step 4.
Yes
Yes
Convert your existing log files.
For example, perform the following steps:
1. Backup your log files in case the
conversion fails.
2. Create the batch file described below.
3. Run the batch file in your log file
directory.
4. Delete the batch file.
Batch File Example
Note the following issues before running the batch file:
1. Make sure to back up you data in case a typographic or other error corrupts the file(s).
2. Use a text editor, such as Edit or Notepad, to create an MS-DOS batch file containing the
following commands.
FactoryLink / Conversion Guide / 71
•
CONVERTING TREND
•
Conversion Procedure
•
•
If you choose to execute these commands from the command prompt, remember to enter
the variable prefix as “%”, instead of “%%.”
3. Run this batch file in the directory containing your log file(s).
This batch file will rename all .cdb files. Make sure that only FactoryLink 7.0 Historian
database files are in the directory when you run this batch file.
Note: Make sure to use the semi-colon in lines 2 through 5.
LIH[LVWOLVWW[WGHOOLVWW[W
)25L,1FGE'2#HFKRXSGDWHV\VWHPBWDEOHVHWWILOH
aQLGEI
ZKHUHWILOH
)25L,1VHULDOFGE'2#HFKRXSGDWHV\VWHPBWDEOHVHWWILOH
L
!!OLVWW[W
aQLFGE
ZKHUHWILOH
)25L,1V\VBILOHFGE'2#HFKRXSGDWHV\VWHPBWDEOHVHWWILOH
L
!!OLVWW[W
aQLFGE
ZKHUHWILOH
L
!!OLVWW[W
HFKRTXLW!!OLVWW[W
EKBVTOIOLVWW[W
UHQFGEGEI
LIH[LVWVHULDOGEIUHQVHULDOGEIVHULDOFGE
LIH[LVWV\VBILOHGEIUHQV\VBILOHGEIV\VBILOHFGE
GHOOLVWW[W
In order to avoid confusion and “rem” lines in the batch file listing, we provide remarks for
each line as follows:
Line 1 ensures there is no list.txt file as a starting point.
Line 2 creates list.txt containing an BH_SQL update statement for each .cdb file in the
directory
Line 3 adds another line to list.txt to correct the serial.cdb file used by PowerSPC, if it exists.
Line 4 adds another line to list.txt to correct the sys_file.cdb file, which is always a .cdb file.
Line 5 adds another line to list.txt to quit the BH_SQL session.
Line 6 runs the BH_SQL utility with input from the file list.txt.
Line 7 renames all the .cdb files to .dbf files.
Line 8 renames the serial.dbf file to serial.cdb as required by PowerSPC and other tasks, if it
exists.
Line 9 renames the sys_file.dbf file to sys_file.cdb as required by FactoryLink.
Line 10 deletes the list.txt file to clean up the directory.
72 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 5: Setting up the System DSN
The Trend Control requires that the data sources exist prior to the configuration of a Trend pen.
Perform the following steps to set up the System DSN:
1 From the Start menu, select Settings>Control Panel.
2 In the Control Panel, select ODBC Data Sources (see Figure 3-18).
Figure 3-18 Control Panel
FactoryLink / Conversion Guide / 73
•
CONVERTING TREND
•
Conversion Procedure
•
•
3 In the ODBC Data Source Administrator dialog box, select the System DSN tab (see Figure
3-19). Click Add.
Figure 3-19 ODBC Data Source Administrator
4 In the Create New Data Source dialog box, select Microsoft Visual FoxPro Driver (see
Figure 3-20). Click Finish.
Figure 3-20 Create New Data Source
74 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
5 In the ODBC Visual FoxPro Setup dialog box, provide the following information (see Figure
3-21):
Data Source Name
Description
Database type
Path
TrendConv
Trend conversion Data Source
Free Table directory
Provide a path or click the Browse button to select one (see Figure 3-22)
Figure 3-21 ODBC Visual FoxPro Setup
6 In the Select Directory Containing Free Tables dialog box, select d:\trendconv\flapp1 for
the Folders and TRENDTBL.dbf for the Directory contents (see Figure 3-22). Click OK.
Figure 3-22 Select Directory Containing Free Tables
FactoryLink / Conversion Guide / 75
•
CONVERTING TREND
•
Conversion Procedure
•
•
7 The System DSN is now set up for TrendConv as shown in Figure 3-23. Click OK.
Figure 3-23 ODBC Data Source Administrator
76 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 6: Create a New Project and New File in Client Builder
Perform the following steps to create a new Client Builder project:
1 Double-click the Client Builder icon on your desktop.
2 In the Open Project dialog box, click New (see Figure 3-24).
Figure 3-24 Open Project
3 In the New Project dialog box, fill in the Project Name and Location (see Figure 3-25). Click
OK.
Figure 3-25 New Project
A new Client Builder project is created.
FactoryLink / Conversion Guide / 77
•
CONVERTING TREND
•
Conversion Procedure
•
•
4 From the File menu in the Client Builder window, click New (see Figure 3-26).
Figure 3-26 Client Builder Window
5 In the New Mimic dialog box, click OK (see Figure 3-27).
Figure 3-27 New Mimic
A new Client Builder mimic file is created.
78 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 7: Configure the Trend Cluster/Server Parameters in Client Builder
In Client Builder, you need to set up Server Types, Trend Servers for the Server Types, Trend
Clusters, and Trend Servers for the Trend Clusters.
A Setup Shortcut
If you have installed the Starter Application, you can use the following shortcut to set up the
Trend parameters: copy the Servers.dat file in the USDATA\Client
Builder\Project\Starter\Config Files directory to the Config Files folder in the directory of
your application (see Figure 3-28). Once the Servers.dat file is in place, you do not need to
manually configure the Trend parameters in Client Builder; therefore, you can skip Step 7.
Note: Make sure to close the Client Builder file so that next time you
open it, it can read from the copied Servers.dat file.
Figure 3-28 Copying Servers.dat File
If you did not install the Starter Application, you have no shortcut to take, and therefore, you
have to perform the following steps to set up the Trend parameters in Client Builder.
FactoryLink / Conversion Guide / 79
•
CONVERTING TREND
•
Conversion Procedure
•
•
I. Set up the Trend Server Type
1 In the Client Builder mimic file you created in Step 6, select Servers from the Tools menu
(seeFigure 3-29).
Figure 3-29 Tools Menu
2 The Servers Editor appears as shown in Figure 3-30.
Figure 3-30 Servers Editor
80 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
3 Right-click SERVERTYPES. The Communication Manager pane appears on the right side of
the screen (see Figure 3-31).
Figure 3-31 Trend Server Type Configuration
4 Fill in the following information:
Name
Type
Computer
TrendServer or any name you want to use.
TrendFW10
MyComputer
Class ID
Filled in automatically: {C495D4F3-5480-11D3-BF8D-00C04F7E967F}
Prog ID
Filled in automatically: ClientBuilder.TrendFWMgr
Note: If you have installed the Starter Application, the SERVERTYPES
are preconfigured for you.
Also keep in mind that FactoryLink 7.0, a Client/Server environment, can
have multiple servers as well as multiple clients.
5 Click Set. Then click OK.
Your Trend Server Type is now set up.
FactoryLink / Conversion Guide / 81
•
CONVERTING TREND
•
Conversion Procedure
•
•
II. Set up the Trend Server for the Trend Server Type
1 Right-click the newly created TrendServerType and select Add Server from the pop-up menu.
The configuration pane appears on the right side of the screen as shown in Figure 3-32.
Figure 3-32 Trend Server Configuration.
2 Provide the following information:
Name
TrendServer1 or any name you want to use.
Run Time
Computer
Use the drop-down button and choose
My Computer>TrendDSServer.TrendServer.1 (double-click)
Prog ID
Filled in automatically: TrendDSServer.TrendServer.1
In the Run Time pane, click the Advanced button to obtain the default
Advanced Server Settings for Run Time Server (see Figure 3-33).
82 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Figure 3-33 Run Time Server
Accept the default settings:
- Computer: My Computer
- Prog ID: TrendDSServer.TrendServer.1
- Class ID: {B3C554D0-B6FA-11D3-8FFC-00105A8B4212}
- Scan Rate: 1000
- Time Out: 10000
- Reconnection Delay: On Failure—60000; On Shutdown—60000
Click OK.
Design Time
Computer
Use the drop-down button to choose
My Computer>TrendDSServer.TrendServer.1 (double-click).
Prog ID
Filled in automatically: TrendDSServer.TrendServer.1
In the Design Time pane, click the Advanced button to obtain the default
Advanced Server Settings for Design Time Server (see Figure 3-34).
FactoryLink / Conversion Guide / 83
•
CONVERTING TREND
•
Conversion Procedure
•
•
Figure 3-34 Design Time Server
Accept the default settings:
- Prog ID: TrendDSServer.TrendServer.1
- Class ID: {5AEC3E98-CFB3-11D2-A597-00C04F7D7A54}
- Scan Rate: 1000
- Time Out: 10000
Click OK.
Storage Name
Leave it blank. Not implemented for FactoryLink 7.0.
Your Trend Server is now set up.
84 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
III. Set up the Trend Cluster
1 In the Servers Editor, right-click CLUSTERS and select New. The configuration pane appears
on the right side of the screen (see Figure 3-35).
Figure 3-35 Trend Cluster Configuration
2 Provide the following information:
Name
Server Type Name
Use any name for the cluster.
Select the Trend Server Type you just created.
3 Click Set. Then click OK.
The Trend Cluster is now set up.
FactoryLink / Conversion Guide / 85
•
CONVERTING TREND
•
Conversion Procedure
•
•
IV. Set up the Trend Server for the Trend Cluster
1 In the Servers Editor, right-click TrendCluster that you just created and select Add Member
from the pop-up menu. The configuration pane appears on the right side of the screen as shown
in Figure 3-36.
Figure 3-36 Trend Cluster Server Configuration
2 Provide the following information:
Name
Use any name for the cluster member.
Server Name
Select a Trend Server from the drop-down list. Notice that the content of the
drop-down list matches the servers you defined earlier.
Rank
This field shows the rank of the server within a particular cluster of servers
and is related to the failure mode. When the highest-ranked server is not
available, the next highest-ranked server is used.
Note: This feature is not implemented for FactoryLink 7.0.
3 Click Set. Then click OK.
The Trend Server for the Trend Cluster is now set up.
86 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 8: Add a Trend ActiveX Control in Client Builder
Perform he following steps to create a Trend display:
1 Create a mimic file in Client Builder (refer to Step 6).
1 From the Mode menu, select Design (see Figure 3-37). A design mode is required for this
configuration.
Figure 3-37 Design Mode
2 From the Insert menu, select USDATA Trend Control (see Figure 3-38).
Figure 3-38 The Insert Menu
FactoryLink / Conversion Guide / 87
•
CONVERTING TREND
•
Conversion Procedure
•
•
3 The Trend Control window appears as shown in Figure 3-39. You can resize it by using its size
handles.
Figure 3-39 Trend Control
The information at the bottom of the control provides the following information:
• Connected (Yes/No) indicates whether you are connected to the Trend Server that you set
up as described in the previous section.
• Time Zone indicates the time zone of the computer.
• Online (Yes/No) indicates whether the Trend Control has a connection to the specified
database.
88 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 9: Set up the Properties for the Trend ActiveX Control
For detailed information on configuring the Trend Control, refer to the Task Configuration
Reference Guide.
Configure the Trend Control in the following tabs:
• Graph
• Pen
• Font
The Graph Tab
Perform the following steps to set up the Graph parameters:
1 Right-click anywhere in the Trend Control window and select Properties from the drop-down
menu (see Figure 3-40).
Figure 3-40 Select Properties
FactoryLink / Conversion Guide / 89
•
CONVERTING TREND
•
Conversion Procedure
•
•
2 In the TREND Control Properties dialog box, check Use Single Axis and uncheck Auto
X-Scale and Auto Y-Scale (see Figure 3-41).
Figure 3-41 Trend Control Properties
3 Set up the other parameters as follows:
Duration Length
Duration Type
360
Seconds
Plot Min
0
Plot Max
60
4 Click Axis Properties.
90 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
5 In the Axis Properties dialog box, set up the axis properties as shown in Figure 3-42. Click
OK.
Figure 3-42 Axis Properties
6 In the TREND Control Properties dialog box, click Trend Server.
7 In the Trend Cluster Selection dialog box, select TrendCluster from the drop-down list for
Cluster Name (see Figure 3-43). Click OK.
Figure 3-43 Trend Cluster Selection
FactoryLink / Conversion Guide / 91
•
CONVERTING TREND
•
Conversion Procedure
•
•
The Pens Tab
Perform the following steps to set up Trend pens:
1 In the TREND Control Properties dialog box, click the Pens tab to bring up the configuration
panel for pens (see Figure 3-44). Click New.
Figure 3-44 Pens
92 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
2 In the properties dialog box, configure the properties for the new pen as shown in Figure 3-45.
Click Color Ranges.
Figure 3-45 New Pen
FactoryLink / Conversion Guide / 93
•
CONVERTING TREND
•
Conversion Procedure
•
•
3 Click Add to set up the color ranges as follows (see Figure 3-46). Click Close when finished.
0 - 14
Skyblue
15 - 29
Red
30 - 44
Yellow
45 - 60
Violet
Figure 3-46 Color Ranges
4 In the TREND Control Properties dialog box, click the browse button for Pen Data Source
(see Figure 3-45).
5 In the Pen Configuration dialog box, right-click Historical Data Sources and select Add
Database (see Figure 3-47).
Figure 3-47 Pen Configuration
94 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
6 In the Database Setup dialog box, use the Driver browse button and select ODBC (see Figure
3-48).
Figure 3-48 Database Setup
7 Provide the following information for Connection:
Display Name
Description
DSN
TrendConv
Trend Control Conversion Example Database
TrendConv
8 Click Test to bring up the Testing Connection dialog box (see inside Figure 3-48). Click OK.
9 Click Finish to close the Database Setup dialog box.
FactoryLink / Conversion Guide / 95
•
CONVERTING TREND
•
Conversion Procedure
•
•
10 In the Pen Configuration dialog box, right-click TrendConv that you just added and select
Add Table from the pop-up menu (see Figure 3-49).
Figure 3-49 Add Table
11 In the Table Setup dialog box, in the Unconfigured Tables, click trendbl (see Figure 3-50).
Click Add.
Figure 3-50 Table Setup
96 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
12 After trendbl is filled in the Trending Table(s) automatically, change Single Point Table to
Multi Point Table (see Figure 3-50). The Trend Type for trendbl then becomes MPT.
13 In the Configuration Data table, click on the Value line for each Parameter and select the
following information from the drop-down list (see Figure 3-50). Click Finish.
Key Column
trendkey
Time Column
trendkey
Time Format
Sec Time
Time Is GMT
False
14 In the Pen Configuration dialog box, right-click trendtbl that you just added and select Add
Pen from the pop-up menu (see Figure 3-51).
Figure 3-51 Pen Configuration
FactoryLink / Conversion Guide / 97
•
CONVERTING TREND
•
Conversion Procedure
•
•
15 In the Pen Setup dialog box, in the Unconfigured Pen Filed(s) table, click flsec and then
Add (see Figure 3-52). Click Finish.
Figure 3-52 Pen Setup
98 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
The Font Tab
Perform the following steps to set up the font attributes:
1 In the TREND Properties Control dialog box, click the Fonts tab to bring up the configuration
panel for fonts.
2 Define the attributes for Fonts (see Figure 3-53). Click OK.
Figure 3-53 Fonts
FactoryLink / Conversion Guide / 99
•
CONVERTING TREND
•
Conversion Procedure
•
•
After you have finished configuring the Trend Control, you can test it by going to the Run
Mode (assuming that your FactoryLink is running). The converted Historical Trend chart is
shown in Figure 3-54:
Figure 3-54 Converted Historical Trend Chart
100 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Converting Real-Time Trend
The conversion process for Real-time Trend takes six steps summarized as follows:
1 Convert the original application to FactoryLink 7.0 format.
2 Document existing Trend configuration using Application Editor.
3 Create a new project and new file in Client Builder.
4 Configure Trend Cluster/Server parameters in Client Builder.
5 Create a new real-time Trend display in Client Builder.
6 Set up the properties for the Trend display.
FactoryLink / Conversion Guide / 101
•
CONVERTING TREND
•
Conversion Procedure
•
•
Step 1: Convert the Previous FactoryLink Application to 7.0
Refer to “Step 1: Convert the Previous FactoryLink Application to 7.0” on page 55 in
“Converting Historical Trend.”
Step 2: Document the Existing Trend Chart in Application Editor
Perform the following steps:
1 In Configuration Explorer, open Application Editor in the Graphics folder.
2 Form the File menu, select trend.g and click OK (see Figure 3-55).
Figure 3-55 Open a File
3 Click on the Real-Time Trend chart object.
102 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
4 From the Animation menu, click Chart (see Figure 3-56).
Figure 3-56 Animation Menu
5 In the Chart Animation dialog box, note the following information (see Figure 3-57). Click
Edit Pens.
Data Source or
Scroll Trigger Tag
logtrig
Initial Chart
Duration
350 (Secs)
Chart Scroll
Frequency
2 (Secs)
FactoryLink / Conversion Guide / 103
•
CONVERTING TREND
•
Conversion Procedure
•
•
Figure 3-57 Chart Animation
6 In the Select Pen dialog box, select count (see Figure 3-58). Click OK.
Figure 3-58 Select Pen
104 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
7 In the Pen Count for Object Box dialog box, note the attributes for count as shown in Figure
3-59. Click OK.
Figure 3-59 Pen Count for Object Box
FactoryLink / Conversion Guide / 105
•
CONVERTING TREND
•
Conversion Procedure
•
•
8 Note the pen attributes for seconds as shown in Figure 3-60. Click OK.
Figure 3-60 Pen Seconds for Object Box
106 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
Step 3: Create a New Project and New File in Client Builder
Refer to “Step 6: Create a New Project and New File in Client Builder” on page 77 in
“Converting Historical Trend.”
Step 4: Configure the Trend Cluster/Server Parameters in Client Builder
Refer to “Step 7: Configure the Trend Cluster/Server Parameters in Client Builder” on page 79
in “Converting Historical Trend.”
Step 5: Create a New Real-Time Trend Display
Perform the following steps to create a new Trend display:
1 In the mimic file you created at Step 3, select Trend from the Insert menu (see Figure 3-61).
Figure 3-61 Select Trend
FactoryLink / Conversion Guide / 107
•
CONVERTING TREND
•
Conversion Procedure
•
•
2 In the Trend Display dialog box, click the browse button under Variable (see Figure 3-62).
Note: Before start browsing for tags for Client Builder, start your FLAPP
in Configuration Explorer.
Figure 3-62 Trend Display
108 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
3 In the Variable Browser dialog box, select tag, ctr_value1, for the pen named count (see
Figure 3-63). Click Apply.
Figure 3-63 Variable Browse
FactoryLink / Conversion Guide / 109
•
CONVERTING TREND
•
Conversion Procedure
•
•
4 In the Variable Browser dialog box, select tag, A-SEC, for the pen named seconds (see
Figure 3-64). Click Apply.
Figure 3-64 Variable Browser
5 In the Trend Display dialog box, click the Display tab and define the attributes as shown in
Figure 3-65. Click OK.
Figure 3-65 Display
110 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
6 Click the Aspect tab and define the attributes as shown in Figure 3-66. Click OK.
Figure 3-66 Aspect
7 Click the Execution tab and take the default (see Figure 3-67). Click OK.
Figure 3-67 Execution
FactoryLink / Conversion Guide / 111
•
CONVERTING TREND
•
Conversion Procedure
•
•
8 Click the Curves tab and define the attributes as shown in Figure 3-68. Click OK.
Figure 3-68 Curves
9 Click the Invalid Curves tab, take the default (see Figure 3-69). Click OK.
Figure 3-69 Invalid Curves
112 / FactoryLink / Conversion Guide
CONVERTING TREND
Conversion Procedure
After you have finished configuring the properties of the Trend display, you can go to the run
mode and view the converted Real-Time Trends chart as shown in Figure 3-70.
Note: In our example, we changed the background color to black to
match the legacy file.
Figure 3-70 Real-Time Trends- After Conversion
Please note that real-time Trend at this stage does not support the location of scale, direction of
the trends, or color ranges.
FactoryLink / Conversion Guide / 113
•
CONVERTING TREND
•
Conversion Procedure
•
•
After you have taken the procedures to convert both the Historical and Real-time Trend as
illustrated in this chapter, you should be able to view the converted trending charts as shown in
Figure 3-71.
Figure 3-71 Converted Historical and Real-Time Trending Charts
114 / FactoryLink / Conversion Guide
•
•
•
•
Chapter 4
Converting Database
Browser
This chapter provides a review of the Database Browser task in previous FactoryLink versions
and an introduction to the new Database Browser Control in FactoryLink 7.0. It gives
step-by-step instructions on how to convert an existing Database Browser task configuration to
a Database Browser Control configuration. It also presents three example cases to illustrate the
differences between using the Database Browser task and the Database Browser Control.
D ATABASE B ROWSER TASK
The FactoryLink Database Browser in pre-7.0 versions is a Historian-client task that
communicates with the Historian through mailbox elements to transfer data between
FactoryLink real-time database elements, also called tags, and external database tables.
The Browser offers the following features:
• Manipulation of relational database information from within FactoryLink
• Ability to send and retrieve data to and from all external database tables, including those
created outside of FactoryLink
• Definition of elements referenced by Browser both in arrays and individually
For more information on the Database Browser task, refer to the FactoryLink ECS
Configuration Guide.
D ATABASE B ROWSER C ONTROL
The new FactoryLink 7.0 Database Browser Control does not work in conjunction with the
Historian task. It is an ActiveX Control that allows the user to view, add, modify, and delete
database records from any database with an ODBC Data Source Name (DSN). It is a
two-tiered control that can generically attach to any database. Configuration is intuitive and
geared toward a more user-friendly environment. In addition, it offers comprehensive scripting
abilities for a dynamic run-time environment.
For more information on the Database Browser Control, refer to the FactoryLink Task
Configuration Reference Guide.
FactoryLink / Conversion Guide / 115
•
CONVERTING DATABASE BROWSER
•
Browser Task vs. Browser Control
•
•
B ROWSER TASK
VS .
B ROWSER C ONTROL
The Database Browser Control in FactoryLink 7.0 is for SHARED domain only. It has very
similar client-side functions as the FactoryLink Database Browser task in the previous
versions. Table 4-1 compares the functionality of the Browser task and the Browser Control.
Table 4-1 Comparison of Functionality
Functionality
Browser Task
Browser Control
SELECT record(s)
Yes
Yes
Positional update
Yes
Yes
Positional delete
Yes
Yes
Logical update
Yes
Yes
Logical delete
Yes
Yes
Insert record
Yes, indirect.
Yes, direct through scripting
Result set displayed on display
Yes, through tags
and links to tags on
the display.
Yes, through the ActiveX
Control display grid.
Absolute move in display to
highlight record
Yes
Not available
Relative move in display to
highlight record
Yes
Yes, replaced by scroll bar
Select/Update/Delete can be
activated via scripting.
Yes
Yes
Result set can be written to tags.
Yes
Yes, through scripting
You can use the Database Browser task for other server-side functions, such as the following:
• Trigger select from the server
• Trigger update from the server
• Trigger delete from the server
• Support stored procedures
116 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Considerations
C ONVERSION C ONSIDERATIONS
The properties of the Database Browser Control in FactoryLink 7.0 differ from those of the
Database Browser in earlier versions. Table 4-2 lists the properties of both. Make sure to refer
to the values in this table when converting from an existing Database Browser task
configuration to a Database Browser Control configuration.
Table 4-2 Comparison of Properties
Database Browser
Properties
Database Browser Control Properties
Browse Name
Not applicable
Select Trigger
Executed at startup and refresh at run time
Update Trigger (Positional
and Logical Update)
At run time, positional update is done by
overwriting a selected record field and tabbing to
another field.
Logical update is done by executing an update
query in the SQL text window.
Delete Trigger (Positional and
Logical Delete)
At run time, positional delete is done by selecting
the record and pressing the “Delete” button on your
keyboard.
Logical delete is done by executing a delete query
in the SQL text window at run time.
Move Trigger (Relative
Move)
Use scroll bars
Position Trigger
Use scroll bars
Historian Mailbox
Not applicable
Database.Table Name
In Data Source Properties
Current Row Tag
Active Row Property (run time only)
Auto Create Record (Yes/No)
At run time, may insert record interactively in the
last line of the grid, or execute an insert query in the
SQL text window.
Browse Table Size
Not applicable
FactoryLink / Conversion Guide / 117
•
CONVERTING DATABASE BROWSER
•
Conversion Considerations
•
•
Table 4-2 Comparison of Properties
Database Browser
Properties
Database Browser Control Properties
Internal Table Size
Not applicable
External Table Size
Not applicable
Completion Trigger
Not applicable
Completion Status
Not applicable
Tag Name
Not applicable
Logical Operator/Column
Name/Logical Expression
Select Statement Property
Column Name in Display
(Graphics)
Column Properties
118 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
C ONVERSION P ROCEDURE
The following procedure illustrates how to convert from the Database Browser to the Database
Browser Control in order to view the browsed data on screen.
Perform the following steps:
1 Start the Configuration Manager and review the information in the existing Database Browser
Control table (see Figure 4-1).
Figure 4-1 Database Browser Control Panel in Configuration Manager
This table shows that there are a Select Trigger STARTUP and a Move Trigger UNITMOVE.
It also shows which table is connected and that the Browse Table Size has ten rows.
FactoryLink / Conversion Guide / 119
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
2 Review the information in the existing Database Browser Information table (see Figure 4-2).
Figure 4-2 Database Browser Information Table
The Database Browser Information table contains the logical statement for the WHERE clause
of the database select statement and the tags and columns associated with the data. Because the
Browse Table Size has ten rows (refer to Figure 4-1), you need to define a minimum of
ten-element array tag.
To see the data in the original application, animate all the tags in a graphics screen and set up
animation to use the Move Trigger or Position trigger in order to scroll up and down.
3 Double-click the Client Builder icon on your desktop.
120 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
4 In the Open Project dialog box, click New to open a new project (see Figure 4-3).
Figure 4-3 Open Project Dialog Box
5 In the New Project dialog box, fill in a new project name and location (see Figure 4-4). Click
OK.
Figure 4-4 New Project Dialog Box
FactoryLink / Conversion Guide / 121
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
6 From the File menu in the Client Builder window, click New (see Figure 4-5).
Figure 4-5 File Menu
7 In the New Mimic dialog box, click OK (see Figure 4-6).
Figure 4-6 New Mimic Dialog Box
122 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
8 From the Tools menu in the new mimic file, select Preferences>ActiveX Controls (see
Figure 4-7).
Figure 4-7 Tools Menu
9 In the ActiveX Controls Configuration panel, double-click USDATA.DbBrowserCtl from the
Installed ActiveX Controls list. Click the >> button and move it to the Approved ActiveX
Controls list (see Figure 4-8). Click OK.
Figure 4-8 ActiveX Controls Configuration
FactoryLink / Conversion Guide / 123
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
10 From the Insert menu in the Client Builder mimic file, select Favorites ActiveX
Controls>USDATA.DbBrowserCtl (see Figure 4-9).
Figure 4-9 Insert Menu
11 The Database Browser Control appears inside the grid window display (see Figure 4-10).
Resize the grid window, by using its size handles, to the number of data rows and columns you
wish to see.
Figure 4-10 Database Browser Control
124 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
12 From the Edit menu or right-click anywhere in the Database Browser Control object area
inside the display window, select Properties in the pop-up menu (see Figure 4-11).
Figure 4-11 Select Properties
13 The USDATA.DbBrowserCtl Properties screen appears, which presents three categories of
properties as tabs across the top of the screen (see Figure 4-12).
Each tab presents configurable fields that determine what data you retrieve and the format of
the data presentation.
Note: Permanent changes to property values must be made in the design
mode.
• General controls data access abilities, grid appearance, and run-time security options.
• Data Source Properties allows access to and configuration of the database and table you
will browse through the entry of a DSN.
• Column Properties allows you to customize the appearance, availability, and caption of
database table columns.
FactoryLink / Conversion Guide / 125
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
Figure 4-12 USDATA.DbBrowserCtl Properties Dialog Box - General
14 Refer to the following information to define General (see Figure 4-12):
Data Access
• Allow database updates allows or disallows users to update database records.
• Confirm database updates, if checked, enables a pop-up confirmation window for
database updates during run time.
• Automatic refresh allows or disallows the grid to be updated (automatically or
periodically) from the data in the database. When you select this option you may specify
how often the grid refreshes in the Interval field (seconds).
Grid Properties
• Foreground Color defines the foreground color to be used within the grid.
• Background Color defines the background color to be used within the grid.
126 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
• Font defines the text font to be used within the grid.
15 Refer to the following information to define the Connection Values of the Data Source
Properties (see Figure 4-13).
• DSN defines the name of the data source pointing to a database.
• UID specifies the user identification if required by the database server.
• Password specifies the user password if required by the database server.
• Database identifies the name of the database.
• Tables identify the names of the tables which are available in this database.
• SQL Statement executes actions performed by the Database Browser Control. For
example, to select all records from a table, type in select* from table_name; for sort order,
type in select* from table_name order by column_name desc.
Figure 4-13 USDATA.DbBrowserCtl Properties Dialog Box - Data Source Properties
FactoryLink / Conversion Guide / 127
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
16 Accept the defaults for Column Properties or define them as options (see Figure 4-14). Click
OK.
Figure 4-14 USDATA.DbBrowserCtl Properties Dialog Box - Column Properties
17 Click OK, then Apply, after you finish defining each property. The values will show up in the
Database Browser Control object grid view.
In the Database Browser Control, you do not need to set any trigger for the initial browse as in
the Database Browser task.
For more information, refer to the FactoryLink Task Configuration Reference Guide.
128 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
Examples: Database Browser vs. Database Browser Control
Both the Database Browser and the Database Browser Control can access data in different
ways. Look at the three example cases and see how different it is to use the Database Browser
Control from the Database Browser in these situations.
Case 1: The user looks only at data on the screen and scrolls through a data set
(data does not need to be returned in FactoryLink tags).
If you use the Database Browser, perform the following steps:
1 Open the Configuration Manager.
2 Create Database Browser Control and Database Browser Information tables.
3 Associate tags to specific columns.
4 Show the tags on a display.
5 Configure a Move Trigger and a Position Trigger to scroll a specific row using a relative move
or absolute move.
6 Associate the Move Trigger and the Position Trigger to animation objects (for example, up and
down arrows) to enable users to do precise relative or absolute moves.
Depending on the complexity of the data and number of tags to animate, setting up a display
like this could take hours.
For detailed information on how to configure Database Browser, refer to the FactoryLink ECS
Configuration Guide.
FactoryLink / Conversion Guide / 129
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
If you use the Database Browser Control, perform the following steps:
1 Double-click the Client Builder icon on your desktop. In the Open Project dialog box, click
New to open a new project (see Figure 4-15).
Figure 4-15 Open Project Dialog Box
2 In the New Project dialog box, provide the new project name and location (see Figure 4-16).
Click OK.
Figure 4-16 New Project Dialog Box
130 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
3 From the File menu in the Client Builder window, click New (see Figure 4-17).
Figure 4-17 File Menu
4 From the Tools menu in the new mimic file, select Preferences>ActiveX Controls (see
Figure 4-18).
Figure 4-18 Tools Menu
FactoryLink / Conversion Guide / 131
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
5 From the Installed ActiveX Controls list in the ActiveX Controls Configuration panel,
double-click USDATA.DbBrowserCtl (see Figure 4-19). Click the >> button and move it to the
Approved ActiveX Controls list. Then click OK.
Figure 4-19 ActiveX Controls Configuration
132 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
6 From the Insert menu in the Client Builder mimic file, select Favorites ActiveX
Controls>USDATA.DbBrowserCtl (see Figure 4-20).
Figure 4-20 Insert Menu
7 The Database Browser Control appears inside the grid window display (see Figure 4-21).
Resize the grid window, by using its size handles, to the number of data rows and columns you
wish to see.
Figure 4-21 Database Browser Control
FactoryLink / Conversion Guide / 133
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
8 From the Edit menu or right-click anywhere in the Database Browser Control object area
inside the display window, select Properties in the pop-up menu (see Figure 4-22).
Figure 4-22 Select Properties
9 The USDATA.DbBrowserCtl Properties screen appears, with three categories of properties as
tabs across the top of the screen (see Figure 4-23).
Each tab presents configurable fields that determine what data you retrieve and the format of
the data presentation.
Note: Permanent changes to property values must be made in the design
mode.
• General controls data access abilities, grid appearance, and run-time security options.
• Data Source Properties allows access to and configuration of the database and table you
will browse through the entry of a DSN.
• Column Properties allows you to customize the appearance, availability, and caption of
database table columns.
134 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
Figure 4-23 USDATA.DbBrowserCtl Properties - General
10 Refer to the following information to define General (see Figure 4-23):
Data Access
• Allow database updates allows or disallows users to update database records.
• Confirm database updates, if checked, enables a pop-up confirmation window for
database updates during run time.
• Automatic refresh allows or disallows the grid to be updated (automatically or
periodically) from the data in the database. When you select this option you may specify
how often the grid refreshes in the Interval field (seconds).
Grid Properties
• Foreground Color defines the foreground color to be used within the grid.
• Background Color defines the background color to be used within the grid.
FactoryLink / Conversion Guide / 135
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
• Font defines the text font to be used within the grid.
11 Refer to the following information to define Data Source Properties (see Figure 4-24).
• DSN defines the name of the data source pointing to a database.
• UID specifies the user identification if required by the database server.
• Password specifies the user password if required by the database server.
• Database identifies the name of the database.
• Tables identify the names of the tables which are available in this database.
• SQL Statement executes actions performed by the Database Browser Control. For
example, to select all records from a table, type in select* from table_name; for sort order,
type in select* from table_name order by column_name desc.
Figure 4-24 USDATA.DbBrowserCtl Properties -Data Source Properties
136 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
12 Accept the defaults for Column Properties or define them as options (see Figure 4-25).
Figure 4-25 USDATA.DbBrowserCtl Properties - Column Properties
13 Click OK, then Apply, after you finish defining each property. The values will show up in the
Database Browser Control object grid view.
There is no functionality to do precise selection of a row by either Absolute or Relative Move.
However, you may scroll up or down in the table.
The whole conversion process takes only a few minutes. One caveat is that the Data Source has
to be accessible in order to set up the Database Browser Control. For more information on Data
Source Properties, refer to the FactoryLink Task Configuration Reference Guide.
FactoryLink / Conversion Guide / 137
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
Case 2: The user enters some parameters. A Select is processed, and data is
returned to the user in a format suitable for further processing (not for screen
display alone).
If you use the Database Browser, perform the following steps:
1 Open the Configuration Manager.
2 Create Database Browser Control and Database Browser Information tables.
3 Associate tags to specific columns.
4 Associate the data entry fields to columns being used for Select.
5 Associate a Select Trigger to an animation object (for example, the OK button).
For more information on how to configure Database Browser, refer to the FactoryLink ECS
Configuration Guide.
Depending on the complexity of the data and number of tags to animate, setting up a display
like this could take hours.
If you use the Database Browser Control, perform the following steps:
1 Repeat the steps in Case 1.
2 Create and label data entry fields. Date and UnitName are text boxes through which users enter
parameters (see Figure 4-26).
3 Create an OK button.
4 Associate the button to a script to tell the Browser Control where to get the data.
The whole process takes only a few minutes. Refer to the screen and code on the following
page to help you with the process.
138 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
The following example has the hourly emissions data for a specific day for an emissions source
(see Figure 4-26).
Figure 4-26 Example Screen for Case 2
Use the following code for the data:
Private Sub OK_Click()
Dim temp2 As String
temp2 = "select UNITNAME,idate,noxcorr,noxrate,soxcorr,soxrate from hourly WHERE
UNITNAME = ‘” + UnitName.Text + “‘ AND IDATE >= ‘” + IDate.Text + “000000' AND IDATE
< ‘” + IDate.Text +”235959’”
DbBrowserCtl1.SetQuery temp2
End Sub
FactoryLink / Conversion Guide / 139
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
Case 3: The user scrolls through a data set, selects a row, and writes the current
row to a set of tags.
A real-life example is to select a set of recipes associated with a process. The user enters the
work center identification, selects a recipe, moves it to a set of text fields, fine-tunes the
parameters, and then writes it out to a PLC.
If you use the Database Browser, perform the following steps:
1 Open the Configuration Manager.
2 Create Database Browser Control and Database Browser Information tables.
3 Associate specific tags to columns to receive the data.
4 Use tag input fields to define select parameters.
5 Define another set of data input tags to get the selected row.
6 Implement some logic to move the tags to a set of PLC write tags, and force a write to the PLC.
(Where possible, you could use the same Database Browser tags as PLC write tags.)
For more information on how to configure Database Browser, refer to the FactoryLink ECS
Configuration Guide.
Depending on the complexity of the data and number of tags to animate, setting up a display
like this could take hours.
If you use the Database Browser Control, perform the following steps:
1 Repeat the steps in Case 2.
2 Associate the text fields to PLC write tags.
3 Move the selected row into a set of editable text fields.
140 / FactoryLink / Conversion Guide
CONVERTING DATABASE BROWSER
Conversion Procedure
The following example browses a recipe database for a particular product and then moves the
chosen row of data to text fields (see Figure 4-27).
Figure 4-27 Example Screen for Case 3
The “Select’ and the “Get Row” buttons have codes associated with them:
• Select—Uses the product text field to build an SQL query and get all the records associated
with that product.
Use the following script:
Private Sub Select_Click()
Dim temp2 As String
temp2 = “select * from recipe where product = ‘ ” + Product.Text+” ’ ”
DbBrowserCtl1.SetQuery temp2
End Sub
• Get Row—Gets the data from a row chosen by the user. Clicking anywhere on a row, the
marker on the left of the grid indicates the active row.
Use the following script:
Private Sub GetRow_Click()
Dim ActiveRow As Variant
ActiveRow = DbBrowserCtl1.ActiveRow
CoTemp.Text = DbBrowserCtl1.GetCellText ( ActiveRow,CoTemp )
CoPsi.Text = DbBrowserCtl1.GetCellText ( ActiveRow,CoPsi )
O2Temp.Text = DbBrowserCtl1.GetCellText ( ActiveRow,O2Temp )
O2Psi.Text = DbBrowserCtl1.GetCellText ( ActiveRow,O2Psi )
BurnTime.Text = DbBrowserCtl1.GetCellText ( ActiveRow,BurnTime )
BurnTime2.Text = DbBrowserCtl1.GetCellText ( ActiveRow,BurnTime2 )
End Sub
FactoryLink / Conversion Guide / 141
•
CONVERTING DATABASE BROWSER
•
Conversion Procedure
•
•
In summary, using the Database Browser Control is more efficient and less time-consuming
than using the Database Browser. To view the browsed data on screen, only minimal amount of
effort is required to set up the Database Browser Control, manipulate its properties during run
time to post queries, and access subsets of data within Client Builder.
142 / FactoryLink / Conversion Guide
•
•
•
•
Chapter 5
Converting Graphics
This chapter presents general information on graphics within the Client Builder environment.
It provides instructions on how to convert the drawing files for the FactoryLink legacy
graphics product to drawing files for the newly-introduced Client Builder product. It also
discusses a few other issues that you should consider during the conversion process.
F ACTORY L INK 7.0 G RAPHIC TOOLS
Operators access data in the real-time database through graphical user interface screens. To
illustrate these screens, the previous versions of FactoryLink used Application Editor
(APPEDIT) drawing tools. For more information on Application Editor, refer to the
FactoryLink ECS Application Editor Guide.
FactoryLink 7.0 introduces a new graphics product, Client Builder, for the configuration of the
graphical user interface. However, the 7.0 version still supports the FactoryLink ECS graphics
tools, namely Application Editor, WebClient, and Graph. In addition, both of these graphical
environments can be installed on the same FactoryLink client machine.
Client Builder has a standard Microsoft look and feel. It provides an integrated design and
run-time environment so graphic screens can be developed and viewed in run-time mode
concurrently. In addition to all the graphic-animation capabilities supported by the ECS
graphics tools, Client Builder includes ActiveX controls for viewing alarm and trend data and
for browsing database information. It can host third-party ActiveX controls, including the
WebClient control.
For more information on Client Builder, refer to the Client Builder online help.
FactoryLink / Conversion Guide / 143
•
CONVERTING GRAPHICS
•
Conversion Considerations
•
•
C ONVERSION C ONSIDERATIONS
This section provides information for your consideration before you convert the graphics:
• USER vs. SHARED-domain tags
• File directories
• ECSConvert.exe
- Syntax
- PowerVB
- Switches
• Bitmap files
• Converted object types
• Converted animation types
Converting USER-Domain Tags to SHARED
Because Client Builder applications do not use the USER domain, USER-domain tags cannot
be used for Client Builder animation. By default, ECSConvert does not convert animation that
references tags in the ECS USER domain, but does report errors, for example, tag names,
objects, and drawings that are still in the USER domain, in the conversion log. We recommend
that you change all the required USER tags into SHARED before converting the graphics.
Perform the following steps to change the USER-domain tags to SHARED:
1 Open a DOS/Command Prompt window and change directory to application directory.
For example, D> C:, then C> CD %FLAPP%.
2 Start BH_SQL.
For example, C> BH_SQL.
3 Enter the command to change all tags to SHARED.
For example, SQL> update object set tagdomain=’SHARED’ where tagdomain=’USER’
4 Quit BH_SQL.
For example, SQL> quit
5 Run the application to test it.
Use the -U switch to make ECSConvert convert the USER-domain animation, but you must
change it later by using the animation in Client Builder or a SHARED tag. Be especially
careful when you use the -U switch. If you find animation not working after the conversion,
check and see whether it is still associated with USER-domain tags.
144 / FactoryLink / Conversion Guide
CONVERTING GRAPHICS
Conversion Considerations
For more information on the domain issue, refer to Chapter 1, “Conversion Overview.”
File Directories
The conversion practice requires that you keep all the conversion-related files as subdirectories
under the Client Builder project directory you create. For the purposes of this document, we
use C:\Program Files\USDATA\Client Builder\Project\ECS as the project directory.
Table 5-1 provides a list of file directories in conversion.
Table 5-1 File Directories
File
Directory
New Client Builder
Project
C:\Program Files\USDATA\Client Builder\Project\ECS
Converted ECS
Drawings
C:\Program Files\USDATA\Client Builder\Project\ECS\Mimic Files
Converted ECS
Symbols
C:\Program Files\USDATA\Client Builder\Project\ECS\Symbols
Optional PowerVB
Documentation
C:\Program Files\USDATA\Client Builder\Project\ECS\PowerVB
ECSConvert.log
C:\Program Files\USDATA\Client Builder\Project\ECS
The only required parameter is the destination directory, which is the Client Builder project
directory. It must also have “Mimic Files” and “Symbol Files” subdirectories. Files in these
directories with the same name as ECS drawings or symbol objects will be deleted. Therefore,
it is recommended that you back up files in these directories before you run ECSConvert.
ECSConvert.exe
ECSConvert.exe is a command-line utility that converts ECS graphics to Client Builder
graphics. It is designed to be used one time only on an application to provide an initial base
client configuration. After the initial conversion, any new change must be made within Client
Builder. Modifying the base application and reconverting will cause the client configuration to
lose all changes, and therefore it should be avoided.
Although ECSConvert.exe can handle most conversion issues, some features of ECS graphics
cannot convert completely. As a result, you may need to use features in Client Builder to
modify the converted graphics.
FactoryLink / Conversion Guide / 145
•
CONVERTING GRAPHICS
•
Conversion Considerations
•
•
If no drawing files are specified, ECSConvert converts all application graphics (.g) files. If
some drawing files are specified and some are not, ECSConvert converts only the specified
ones.
Make sure to include symbols.g file in the list of drawing files to be converted.
PowerVB
ECSConvert does not convert PowerVB scripts. The -D switch documents the PowerVB code
into the PowerVB subdirectory of the destination directory. The documented PowerVB code
can be used to form the basis of script animation in the Client Builder graphics.
Switches
Four switches take the form of command-line parameters. Table 5-2 lists all the conversion
switches.
Table 5-2 List of Switches
Switch
What it means
-Adirectory
ECS application directory (which uses %FLAPP% if -A is
not specified)
-Cclustername
FactoryLink cluster (which defaults to FactoryLinkCluster)
-D
Documents PowerVB code
-U
Converts USER-domain animation
Note: Switches are case-insensitive.
For example, the following syntax will convert the SHARED Run Manager, plant and symbols
drawings, including USER-domain animation, from the application D:\OldFLAPP.
ECSConvert -U -AD:\OldFLAPP dest_dir runmgrs.g plant.g symbols.g
Note: If you use more than one option, make sure to leave a space
between options.
146 / FactoryLink / Conversion Guide
CONVERTING GRAPHICS
Conversion Considerations
Syntax
Simple syntax
ECSConvert directory
For example, ECSConvert “C:\Program Files\USDATA\Client
Builder\Project\ECS” converts the application specified by the FLAPP
environment variable, but does not document the PowerVB code or convert
USER-domain animation.
Note: If the directory name includes a space (spaces), you must
use double quotes. If not, double quotes are not necessary.
Complete syntax
ECSConvert [switches] directory [filename1.g [filename2.g...]]
where
[]
indicates optional parameters.
For example, ECSConvert -D “C:\Program Files\USDATA\Client
Builder\Project\ECS” draw1.g draw2.g... converts the draw1.g and draw2.g
graphics in the C:\Program Files\USDATA\Client Builder\Project\ECS
directory, while documenting the PowerVB code.
Note: If the directory name includes a space (spaces), you must
use double quotes. If not, double quotes are not necessary.
Important: For the conversion to work properly, make sure to put options before the directory
and file name(s) in the syntax.
Conversion Log
All conversion errors or problems are kept in a conversion log in C:\Program
Files\USDATA\Client Builder\Project\ECS\ECSConvert.log.
Bitmap Files
Bitmap files within FactoryLink are not converted. Therefore, you need to copy them manually
from %FLAPP%\USER\DRW to the Program Files\USDATA\Client
Builder\Projects\ECS\Bitmap Files folder.
FactoryLink / Conversion Guide / 147
•
CONVERTING GRAPHICS
•
Conversion Considerations
•
•
Converted Object Types
Table 5-3 lists the converted object types.
Table 5-3 Converted Object Types
Object Types
Connected objects
Conversion Results
Converted, but with the following limitation:
Connected objects become combined objects and
may appear closed or solid, instead of transparent as
they did before the conversion.
Composite objects
Converted
Ellipses
Converted
Floats
Converted, but with the following limitation:
Fields without decimal points converted as integers.
Layered objects
Converted, but with the following limitation:
Users may need to rearrange the layers in Client
Builder after conversion.
Legends
Not converted. They are provided by other controls,
for example, the Trend Control.
Lines
Converted
Parabolas
Not converted
Polygons (both closed
and open)
Converted
Rectangles
Converted
Splines
Not converted
Text
Converted
148 / FactoryLink / Conversion Guide
CONVERTING GRAPHICS
Conversion Considerations
Converted Animation Types
Most animation types can be converted without any problem. Each FactoryLink ECS
animation type is converted into multiple Client Builder animation types, because Client
Builder treats animation differently for digital tags (which use bit animation), analog/long
analog/float tags (which use register animation), and message tags (which use text animation).
As a result, some animation types or unusual combination of tag types may not convert as
expected.
Table 5-4 lists all the converted animated types.
Table 5-4 Converted Animated Types
Animation Types
Conversion Result
Bar charts
Converted
Button animation
Converted, but with the following limitations:
Only certain button actions are converted, for
example, set, toggle, add, subtract, on and off.
Unlike ECS, Client Builder buttons function only
when they are not obscured by another object.
Therefore, stacking buttons does not work. If a
button fails to operate, check to see if any objects
are layered over it.
Button momentary
actions
Not converted
Button set animation
Converted, but with the following limitations:
Only for settings for fixed values, not to a source
tag. Setting a register value to another requires
scripting in the converted application.
Color fill and symbol
animation
Converted, but with the following limitations:
If more than eight limit values are specified in the
FactoryLink ECS animation, only the first eight will
be used in the Client Builder animation. This also
applies to colors used in text animation.
FactoryLink / Conversion Guide / 149
•
CONVERTING GRAPHICS
•
Conversion Considerations
•
•
Table 5-4 Converted Animated Types
Animation Types
Text input
Conversion Result
Converted, but with the following limitations:
Converted correctly for only message and numeric
(analog/long analog/float) tags, but not for digital
tags, because Client Builder does not have “sent
bit” text animation.
Text output
Converted, but with the following limitations:
Text output fields with no decimal points tied to
floating point tags behave differently under Client
Builder. They display as fixed (no decimal points).
X-Y positioning on
buttons and symbols
150 / FactoryLink / Conversion Guide
Converted
CONVERTING GRAPHICS
Conversion Procedure
C ONVERSION P ROCEDURE
Before you convert the graphics (using ECSConvert), you need to convert your FactoryLink
application from earlier versions to 7.0 by using FLNew, FLRestore, and FLConvert. You can
run these utilities from the Command Prompt or in Configuration Explorer. For instructions on
how to use these utilities, refer to the “Utilities” chapter in the FactoryLink Task Configuration
Reference Guide.
Perform the following steps to complete the graphics conversion process:
1 Create a new project in Client Builder.
2 Configure the FactoryLink OPC server in Client Builder.
3 Convert the application.
FactoryLink / Conversion Guide / 151
•
CONVERTING GRAPHICS
•
Conversion Procedure
•
•
Step 1: Create a New Project in Client Builder
USDATA recommends that you create a new project for imported ECS graphics. If you import
the graphics into an existing Client Builder project, the existing window and symbol
definitions will be overridden by the ECS drawings and symbols with the same names.
1 Double-click the Client Builder icon on your desktop.
2 Click New in the Open Project dialog box (see Figure 5-1).
Figure 5-1 Open Project
152 / FactoryLink / Conversion Guide
CONVERTING GRAPHICS
Conversion Procedure
3 In the New Project dialog box, fill in the Project Name and Location (see Figure 5-2). Click
OK.
Figure 5-2 New Project
Your new Client Builder ECS project is now created.
FactoryLink / Conversion Guide / 153
•
CONVERTING GRAPHICS
•
Conversion Procedure
•
•
Step 2: Configure the OPC Server
If you have selected the Starter Application as an install option, the install program creates a
default cluster, called FactoryLinkCluster, which could be used by graphics converted by
ECSConvert. In this case, you could simply copy the Servers.dat file in USDATA\Client
Builder\Project\Starter\Config Files to the Config Files folder in the directory you created
for the converted application (the ECS directory). Once the Servers.dat file is in place, you do
not need to configure the OPC server manually.
If you do not want to use FactoryLinkCluster as your cluster name, or if you did not install the
Starter Application, you need to configure the OPC Server manually. For configuration
instructions, refer to Appendix A, “Configuration of the OPC Server.”
Important: The FactoryLink server must be running in order for Client Builder
animation to attach to it. If you set up your servers and clusters and develop graphics
without the FactoryLink server running, you are not able to browse the list of tags to
apply to animation.
154 / FactoryLink / Conversion Guide
CONVERTING GRAPHICS
Conversion Procedure
Step 3: Convert an Application
The following is an example way to convert a FactoryLink application:
1 From the Start menu, select Command Prompt.
2 Set your FLAPP to E:\ECS (see Figure 5-3).
Figure 5-3 Set FLAPP
3 Type in the syntax for conversion as shown in Figure 5-4. Click Enter.
Figure 5-4 ECSConvert Syntax (Example One)
FactoryLink / Conversion Guide / 155
•
CONVERTING GRAPHICS
•
Conversion Procedure
•
•
Use the options -D and -U to document PowerVB code and convert USER-domain animation
as shown in Figure 5-5.
Figure 5-5 ECSConvert Syntax (Example Two)
The conversion process is now completed.
156 / FactoryLink / Conversion Guide
CONVERTING GRAPHICS
Evaluation
E VALUATION
After you have completed the graphics conversion process, you can take the following steps to
check the converted drawings in Client Builder for both appearance and animation behavior.
1 Add the newly converted application to Configuration Explorer (refer to the FactoryLink
Configuration Explorer User Guide).
2 Start the FactoryLink application in Configuration Explorer and keep it running (refer to the
FactoryLink Configuration Explorer User Guide).
3 Double-click the Client Builder icon on your desktop.
4 In the Open Project dialog box, open the ECS project.
5 From the File menu, click Open.
6 From the Choose Mimic dialog box, select a mimic file.
Check to see if the animation appears to behave correctly. You can double-click the animated
object and view its animation tab, compare the animation with the ECS animation (in AppEdit)
on the same object, and then make modifications to the object within Client Builder.
FactoryLink / Conversion Guide / 157
•
CONVERTING GRAPHICS
•
Summary
•
•
S UMMARY
Converting the FactoryLink graphics is a one-time operation. After you have converted the
ECS application, we recommend that you not convert again, because a second conversion will
overwrite all the changes and fixes that you make to the first one. However, if you discover
immediately after conversion that you can make some changes to improve the conversion, for
example, converting tags from USER to SHARED domain, then you should make the changes
in AppEdit and convert again, before editing the drawings with Client Builder.
Once the graphics are converted, treat them as Client Builder projects and maintain them
within Client Builder. If you are satisfied with the conversion results, make all subsequent
changes with Client Builder and do not use ECSConvert again on those graphics.
Although this chapter covers some of the conversion issues, depending on the complexity of
your conversion task, you may encounter other issues. We recommend that you thoroughly test
the converted graphics to ensure that no features are lost or changed.
158 / FactoryLink / Conversion Guide
•
•
•
•
Chapter 6
Miscellaneous Conversion
Issues
This chapter contains additional conversion-related information that was in the Release Notes
of previous versions of FactoryLink. Please exercise caution when using the information in
this chapter, since it may only apply to certain releases.
This chapter discusses these topics:
• Converting an application with existing data
• NetDTL
• ODBC Historian
• Converting third-party driver or PAK task
• Converting from Alarm Logger to Distributed Alarm Logger
• Distributed Alarm Logger supersedes Alarm Supervisor
• PowerSPC supersedes Statistical Process Control (SPC)
• PowerVB
For help with conversion, contact your USDATA Tier One Partner (TOP) or visit USDATA’s
Web site at www.usdata.com to locate a TOP in your region.
FactoryLink / Conversion Guide / 159
•
MISCELLANEOUS CONVERSION ISSUES
•
Converting an Application with Existing Data
•
•
C ONVERTING
AN
A PPLICATION
WITH
E XISTING D ATA
If you convert an application from a version of FactoryLink ECS prior to 6.0.0 that contains
existing data, you must run a BH_SQL repair to correct index problems.
Perform the following steps to do the repair:
1 Run BH_SQL.
2 Connect to the database.
3 Enter REPAIR.
If your databases include PowerSPC data or multicolumn indexed data, the repair may report
success when it is not actually successful. Then when you are running the application, errors
may occur. For additional help with this problem, contact USDATA Customer Support.
N ET DTL
Starting in FactoryLink ECS 6.0.3, the NeTDTL task was enhanced to support more than 40
PLCs. This required the addition of a new configuration panel for the Logical Station
configuration. The 6.5.0 release provided a conversion utility, although 6.0.3 and 6.0.4 could
not. If your application has not already been converted to this new configuration, then run
FLCONV directly against the pre-6.3.0 NeTDTL configuration, or a restore of a
platform-specific save. Do not perform a multiplatform restore of the application before
running FLCONV.
ODBC H ISTORIAN
If you are converting an application that has the ODBC Historian configured, the conversion to
the multi-instance ODBC Historian requires that you run FLCONV directly against the
pre-6.6.0 ODBC Historian configuration or a restore of a platform-specific save. Do not
perform a multiplatform restore of the application before running FLCONV.
160 / FactoryLink / Conversion Guide
MISCELLANEOUS CONVERSION ISSUES
Converting Third-Party Driver or PAK Task (6.0.4 or Earlier)
C ONVERTING T HIRD -P ARTY D RIVER
OR
PAK TASK (6.0.4
OR
E ARLIER )
For conversion from FactoryLink 6.0.4 or earlier, it is possible that the installation will fail if
the previous FLINK directory structure is expected. This directory would be in the form
{FLINK}\msg\<language> as in {FLINK}\msg\English. If the installation fails, create this
directory manually and reinstall.
Run the FactoryLink mv_pak utility. The mv_pak utility copies your driver and/or PAK files in
the correct directory structure and renames the initial *.txt files to *.bkt, *.hlp files to *.bkh,
and *.key files to *.bkk. If you created an English subdirectory, delete it now.
FactoryLink / Conversion Guide / 161
•
MISCELLANEOUS CONVERSION ISSUES
•
Converting from Alarm Logger to Distributed Alarm Logger
•
•
C ONVERTING
FROM
A LARM L OGGER
TO
D ISTRIBUTED A LARM L OGGER
FactoryLink versions 4.4 and later feature a new Distributed Alarm Logger. Earlier versions of
FactoryLink used a different Alarm Logger function. Read this section to see which changes
and limitations apply before you start the conversion. If your application was developed using
a version of FactoryLink before version 4.3, please call the USDATA Customer Support, and
they will assist you in the conversion of your Alarm Logging application.
Converting to the new Distributed Alarm Logger is an irreversible process, so you should
perform a platform-specific save of your old application before you convert as a precautionary
measure. It is not possible to reverse the conversion process.
To save your old application, run the FLSAVE utility. For more information, please refer to the
“Utilities” chapter in the FactoryLink Task Configuration Reference Guide.
Most of the conversion is done automatically, although the user must make some changes
manually to avoid breaking running applications.
Banner and Output Lines
The new Multiuser Alarm Viewer does not differentiate between banner lines and output lines.
The Alarm Viewer supports views with different filter and sort criteria. Although the banner
lines no longer exist, users can obtain the same result by defining a second (or third) view with
filtering conditions and sorting criteria that match the banner interpretation. The filtering
conditions and the sorting criteria can change online.
During conversion, a separate view is defined for the banner lines and the output lines. If
multiple invocations are defined, multiple corresponding views will be defined. The name for
the view of invocation 0 is BANNER_0 and VIEW_0. Other invocations will have equal
views.
Multiple Invocations
The new Distributed Alarm Logger does not support Multiple Invocations. All alarms defined
in all invocations are converted to a single Alarm System. To do this, all defined groups and
alarms are combined into a single system.
During conversion, set the area code to match the table name in which the alarm was defined.
The group name will be used as the new table selector. If you have defined alarms to have
nonexisting groups, make sure that the groups exist prior to conversion. This only happens if
you are currently developing an application. The old ALOG will not start up in this case.
162 / FactoryLink / Conversion Guide
MISCELLANEOUS CONVERSION ISSUES
Converting from Alarm Logger to Distributed Alarm Logger
The table name is converted to the area code, using the area filter, so that the user can
distinguish between the invocations. The default area code for the alarms is set to the table
name in the old ALOG.
Limitations
The following limitations apply when converting your application. If your application has one
of the following limitations, the conversion may work differently, although not necessarily
incorrectly. Check to see if any of these limitations are affecting your application.
Multiple Group Definitions
Where the same group name is used in different invocations, only the first group definition will
be converted. Other definitions will be ignored. If you defined the groups as having different
colors or acknowledgments, you will lose the information.
Multiple Logging Destinations
The Alarm Logger provides every ALOG task with its own directory to store the historical
alarms. The new Distributed Alarm Logger puts all historical alarms into a single database.
Since the area code is converted to the table name, it is possible to differentiate the old
invocations using an historical analysis tool like DBBROWSE. You can use a WHERE clause,
as shown in the following example:
where area = “warning”
The user must complete the link to a historian before logging is active.
Maximum Number of Alarms
In the old ALOG, each invocation has its own number of active alarms. In the new Distributed
Alarm Logger there is only one active task. The maximum number of active alarm is converted
from invocation number 0.
If you have defined multiple invocations, you might want to use more memory for concurrent
active alarms. You can increase it up to 721. A safe number would be the total of all
invocations (if less than 721).
Alarm Input Controls
The old ALOG uses a table with multiple actions to control the output lines. Some of these
functions have become obsolete, while others have changed. If the tags could be reused for the
FactoryLink / Conversion Guide / 163
•
MISCELLANEOUS CONVERSION ISSUES
•
Converting from Alarm Logger to Distributed Alarm Logger
•
•
same function, they will convert to the proper View. Table 6-1 lists all the implemented
changes:
Table 6-1 Alarm Input Controls
Ack
Converted to Single Ack on the Banner View
Banner
Converted to Sort tag in the Banner View
Group
Converted to the Group Filter tag in the Output View. You
can reuse this tag for input on a group list.
Grpack
Converted to the View Acknowledgment in the Output View
Scroll
Converted to the Selection Offset in the Output View
Selack
Converted to the Single Acknowledgment in the Output
View
Sort
Converted to the Sort tag in the Output View. You can reuse
this tag for input on a sort method.
Pgdn, Pup, Sdn, Sup
The Alarm Logger uses these four DIGITAL tags to control
the scroll offset of the Alarm Output Lines. This has changed
to a single ANALOG tag giving you the same functionality
with more control. You should change a few animations on
the ALOG screen and all other screens you use to present
alarms. All these tags have become obsolete, so you need to
supply a new tag and change the graphics.
The following functions are obsolete:
• Archive
• Exec
• Print
• Return
ALOG in USER Domain
If the user has defined the ALOG in the SHARED domain, the conversion should not be done
automatically.
164 / FactoryLink / Conversion Guide
MISCELLANEOUS CONVERSION ISSUES
Converting from Alarm Logger to Distributed Alarm Logger
Limit Tags
In the New Distributed Alarm Logger, the fields limit default and limit tags are grouped
together as a single tag-constant field. If a tag is defined, the conversion program will use the
tag in the tag-constant field, and also use the limit default value as the tag default value. If you
want to change this default limit, you can change the default for the tag.
If you are using a tag array element for limit tags, please note there is only one default value
for the entire array. This value is updated with the latest limit default value found in the
conversion process.
Converting Your Applications
Running the CV_ALOG Utility
Perform the following steps to start the automatic conversion of your application:
1 Run FLSAVE to safeguard your application. Be aware that the conversion is irreversible.
2 Make sure the FLAPP environment variable is set to the correct application directory.
3 Run CV_ALOG and answer all the questions.
4 If you run an FLCONV to convert the Alarm Logger and choose yes, FLCONV automatically
makes the changes for you. Do not do so if you need to make manual changes.
5 Choose File >Run from the Program Manager, then enter the command:
fldbdoor -x%FLINK%\ac\cvalog.cvt -rasc\ -easc\
A log file flconvrt.log is created in the FLAPP directory. This file lists which configuration
database files have been converted. View this file for any errors that may have occurred.
6 Start FactoryLink Configuration Manager and verify the Distributed Alarm Definitions panel
is completed correctly.
7 Make final changes to complete the conversion. Follow the instructions in the manual.
Historian Link
If your application needs to log historical alarms, perform the following steps to create a link to
the Historian:
1 Open the Distributed Alarm Logger Setup panel, and click Next for the Database Logging
control table.
FactoryLink / Conversion Guide / 165
•
MISCELLANEOUS CONVERSION ISSUES
•
Converting from Alarm Logger to Distributed Alarm Logger
•
•
2 Complete the panel by providing a Database Alias Name and an Historian Mailbox tag.
3 Click Enter and exit to close the tables.
4 Open the Database Historian of your choice.
5 Fill out the Historian Mailbox tag defined in Step 2 with appropriate priority.
6 Fill out the Database Alias Name as in Step 2 and complete the line with the database
directory.
7 Press Enter and exit to close the tables.
Graphics Changes
Note: Use the information in this section only if you are upgrading from
an earlier version to FactoryLink 7.0 and will continue to use FactoryLink
ECS. If you are upgrading to FactoryLink 7.0 from an earlier version and
will use Client Builder as your graphics tool, you do not need to read this
section.
You must change the ALOG screen to restore the alarm scroll pages. The example shows how
to change the default ALOG screen provided in the blank application from version 4.3.x. If
you are using a different screen, you can adjust your screen based on the information provided.
Open the Distributed Alarm Viewer control panel in the Distributed Alarm Setup table.
Perform the following steps to make a change in a single invocation. If you have defined
multiple invocations and are using multiple ALOG screens, this routine should be followed for
each individual screen. Make sure that all tags which need to be defined are unique for each
invocation.
1 Enter a valid new analog tag called ALC_DISPLAY for the Scroll Tag field for the VIEW_0
table.
2 Press Enter and exit to save and close the tables.
3 Start the Graphics editor.
4 Open your ALOG drawing.
5 Select the scroll-up object, and edit the Button animation on the field.
6 Change the action to subtract, change the value to 1, and replace the ALC_SUP tag with
ALC_DISPLAY.
7 Select the pageup object, and edit the Button animation on the field.
166 / FactoryLink / Conversion Guide
MISCELLANEOUS CONVERSION ISSUES
Converting from Alarm Logger to Distributed Alarm Logger
8 Change the action to sub, change the value to 14, and replace the ALC_PGUP tag with
ALC_DISPLAY.
9 Repeat Steps 4 to 8 for the scrolldown and pagedown objects, but use add instead of subtract.
The tags that need to be replaced are called ALC_SDN and ALC_PGDN.
10 Select the object called group. Delete the output text animation and make an input text
animation based on the same tag called ALD_GROUP.
11 Select the object called sort. Delete the output text animation and make an input text animation
based on the same tag called ALD_SORT.
12 Choose Save and exit to finish the graphics changes.
System Configuration
To make sure the two tasks start up automatically, you must change and add to the lines in the
System Configuration. Perform the following steps to the do the system configuration:
1 Open the System Configuration from the Configuration Manager Main Menu.
2 Find the line that has ALOG as the task name. Change ALOG to AL_LOG at the task name.
3 Press tab until you see the name of the executable file. Change bin/alog to bin/al_log. Remove
all program arguments on the line.
4 Press Enter to save changes.
5 Add a new task called AL_VIEW to the SHARED domain. The easiest way to do so is to copy
and paste the last line in the SHARED domain by selecting the last line, choosing. Copy twice,
and select Paste once. Then, select the new line.
6 Change the flags to fr.
7 Change task name to AL_VIEW.
8 Increase the index number on all task tags by 1.
9 Change the executable file name to bin/al_view. All multiple invocations are grouped together
to become AL_LOG. Delete the multiple invocations since you no longer need them. For
example, now that you have ALOG, you no longer need the old multiple invocations of
ALOG1 and ALOG2 and therefore can delete them.
10 Press Enter and exit.
FactoryLink / Conversion Guide / 167
•
MISCELLANEOUS CONVERSION ISSUES
•
Converting from Alarm Logger to Distributed Alarm Logger
•
•
Test the Converted Application
When the above-listed steps are completed, test the converted application to make sure that
everything is running without error. Perform the following steps to test the converted
application:
1 Check AL_LOG and AL_VIEW to be sure they are running.
2 Test the scroll-up/down and page-up/down buttons.
3 Run through the rest of the program, and should errors occur, see the documentation on the
Distributed Alarm Logger or contact Customer Support.
Possible Changes to Improve Performance
Multiuser AL_VIEW
If you are using the output lines or any of the controls in other tasks in the SHARED domain,
such as Math and Logic, ensure these references are gone. If this method is not possible, define
a second viewer in the USER domain.
Changing the Area Filter to Match Invocations
The area filter default is set to ALL. Change it to a list containing all tables for a specific
invocation, such as warn_1 and alarms_1. The area codes are all set to the table name.
Incorporate the New ALOG Screen
Instead of changing the ALOG screen, you can also use the new ALOG screen in your
applications. Export the ALOG screen from a blank application and import it back into your
application. Check your viewer setup to match the blank setup.
New Functions
New functions you might want to incorporate in your application include parent-child relations
and distribution. Refer to the documentation on the Distributed Alarm Logger for more
information.
168 / FactoryLink / Conversion Guide
MISCELLANEOUS CONVERSION ISSUES
Distributed Alarm Logger Supersedes Alarm Supervisor
D ISTRIBUTED A LARM L OGGER S UPERSEDES A LARM S UPERVISOR
The Distributed Alarm task in FactoryLink ECS versions 6.6.0 or later is not compatible with
pre-6.5.0 applications regardless of the platform. This only applies to the distribution of alarms
between 6.6.0 and/or 6.5.0 nodes and pre-6.5.0 nodes regardless of platform.
Distribution of alarms between 6.6.0 and 6.5.0 systems is supported. If distribution of alarms is
required between 6.6.0 and/or 6.5.0 systems and pre-6.5.0 systems, regardless of the platform,
the pre-6.5.0 systems need to be upgraded to the appropriate Year 2000 Compliant version for
the affected systems. Refer to the USDATA Web site Year 2000 page for information on Year
2000 Compliant version information for the various platforms.
Because of various defect correction and enhancements to the Distributed Alarm option in the
6.5.0 release, the Max Active Alarm limit has been lowered from 750 to 721 alarms. This is
automatically enforced, and no application changes need to be made for applications with Max
Active limits set to greater than 721. While the limit change is recognized as a somewhat
negative consequence, it was unavoidable when compared to the enhanced features added and
the software defects that have been corrected. One specific enhancement that acts as a
counter-balance to this decrease in the active alarm limit is a change to the purge algorithm
used when the active alarm limit is reached. In previous versions, the oldest alarms were
always the first to be discarded. The purging algorithm has been updated in all Year 2000
Compliant versions so that it is based first on the alarm priority (lowest priority first) and then
oldest alarms within equal priorities.
FactoryLink / Conversion Guide / 169
•
MISCELLANEOUS CONVERSION ISSUES
•
PowerSPC Supersedes Statistical Process Control (SPC)
•
•
P OWER SPC S UPERSEDES S TATISTICAL P ROCESS C ONTROL (SPC)
We recommend upgrading your existing Statistical Process Control (SPC) to PowerSPC
supported in FactoryLink ECS. Contact Customer Support for instructions on converting SPC
tasks to PowerSPC.
PowerSPC references Chart Objects by Object Name. FactoryLink versions 4.4.0 allowed you
to specify an Object Name other than the system generated number. FactoryLink ECS Objects
now have both Object Names and Local Names. The Application Editor allows you to change
only the Local Name, but PowerSPC still references Chart Objects by Object Name.
Use the system generated (and currently unchangeable) Object Name rather than changing the
Object Local Name and using this name in the PowerSPC Charts Definition panel to describe a
PowerSPC chart.
170 / FactoryLink / Conversion Guide
MISCELLANEOUS CONVERSION ISSUES
PowerVB
P OWER VB
The Summit 2.2 libraries used for PowerVB in 6.5.0 and 6.6.0 no longer accept a redundant
syntax for variable declaration as shown in the following example:
Dim xyz $ as string
Instances such as this example in PowerVB scripts will be converted when restored to
FactoryLink ECS 6.6.0 from a pre-6.5.0 version or when the FLCONV utility is run. This has
been implemented only for the data type identifiers $, %, &, and #. All other identifiers and
declarations that span more than one line will result in a validation error for PowerVB and will
need to be manually corrected by removing either the identifier or the “as string” type
declaration.
FactoryLink / Conversion Guide / 171
•
MISCELLANEOUS CONVERSION ISSUES
•
PowerVB
•
•
172 / FactoryLink / Conversion Guide
•
•
•
•
Appendix A:
Configuration of the OPC
Server
Perform the following steps to configure the OPC Server in Client Builder:
1 From the Tools menu in a Client Builder mimic file, select Servers in the pop-up menu. The
Servers Editor dialog box appears as show in Figure 6-1.
Figure 6-1 Servers Editor for Server Types
FactoryLink / Conversion Guide / 173
•
CONFIGURATION OF THE OPC SERVER
•
•
•
2 Right-click SERVERTYPES and select New in the pop-up menu. The Communications
Manager pane appears on the right as shown in Figure 6-2.
Figure 6-2 Communications Manager.
3 Fill in the following information in the Communications Manager pane:
Name
Type
Computer
Class ID
Prog ID
Use any name for the server.
Select OPCDA20 in the drop-down list.
Use My Computer.
Filled in automatically: {BD 28D 911-F-11d2-88CB-00105AABB585}
Filled in automatically: FrontVue.OPCCM.
4 Click Set. Then click OK.
The OPC Server Type is now set up.
174 / FactoryLink / Conversion Guide
CONFIGURATION OF THE OPC SERVER
5 Right-click the OPC Server Type you just created, and select Add Server in the pop-up menu
(see Figure 6-3).
Figure 6-3 Add Server for Server Types
6 Fill in the following information in the configuration pane on the right (see Figure 6-4):
Figure 6-4 Server Configuration Pane
FactoryLink / Conversion Guide / 175
•
CONFIGURATION OF THE OPC SERVER
•
•
•
Name
Use any name for the server.
Run Time
Computer
Program ID
Class ID
Select My Computer and double-click USDATA.SERVER.1 in the
drop-down list.
Filled in automatically: USDATA.SERVER.1.
Click the Advanced button to get the Advanced Server Settings for the
Real Time Server dialog box (see Figure 6-5).
The Class ID is filled in automatically:
{A9BA2928-195E-11D1-8D41-000000000000}.
Click OK to accept all default settings.
Figure 6-5 Advanced Server Settings for Run Time Server
Design Time
Computer
Program ID
Class ID
Select My Computer and double-click USDATA.SERVER.1 in the
drop-down list.
Filled in automatically: USDATA.SERVER.1.
Click the Advanced button to get the Advanced Server Settings for the
Design Time Server dialog box (see Figure 6-6).
The Class ID is filled in automatically:
{A9BA2928-195E-11D1-8D41-000000000000}.
Click OK to accept all the default settings.
176 / FactoryLink / Conversion Guide
CONFIGURATION OF THE OPC SERVER
Figure 6-6 Advanced Server Settings for Design Time Server
Storage Name
Leave it blank. This feature is not applicable to FactoryLink 7.0.
7 Click Set. Then click OK. Your OPC Server is now set up.
8 In the Servers Editor dialog box, right-click CLUSTERS and select New (see Figure 6-7).
Figure 6-7 Add New Clusters
FactoryLink / Conversion Guide / 177
•
CONFIGURATION OF THE OPC SERVER
•
•
•
9 Fill in the following information in the right-hand pane (see Figure 6-8):
Figure 6-8 Configuration for Clusters
Name
Server Type Name
Use any name for the cluster.
In the drop-down list, select the OPC Server Type you created earlier.
10 Click Set. Then click OK. Your OPC Cluster is now set up.
11 Right-click the cluster you just created and select Add Member (see Figure 6-9).
Figure 6-9 Cluster Server Configuration
178 / FactoryLink / Conversion Guide
CONFIGURATION OF THE OPC SERVER
12 Fill in the following information in the configuration pane:
Name
Use any name for the cluster server.
Server
Use Server1 in the drop-down list.
*Rank
Is used when you have multiple servers in the same cluster. All the servers
must be of the same type (OPCDA20) and contain the same data.
When a FactoryLink tag is referenced in Client Builder animation, Client
Builder will check the cluster for the highest ranked server. If that server is
unavailable, Client Builder will look for the next highest ranked server until
it finds an available server.
* The Rank option is not available in this release.
13 Click Set. Then click OK. Your cluster server is now set up.
Important: The FactoryLink server must be running in order for Client Builder animation to
attach to it. You can set up your servers and clusters and develop graphics without the
FactoryLink server running, but you are not able to browse the list of tags to apply to
animation.
FactoryLink / Conversion Guide / 179
•
CONFIGURATION OF THE OPC SERVER
•
•
•
180 / FactoryLink / Conversion Guide
Index
Converting Real-time Trend 101
Converting Trend 51
Converting USER-domain tags to SHARED 144
D
A
Alarm ActiveX Control 44
Alarm Definition Information panel 21
Alarm definition information panel 19
Alarm task overview 17
Alarm view output information panel 20
AlarmViewer Control properties 45
B
Bitmap files 147
Browser conversion considerations 117
Browser conversion examples 129
Browser task vs. Browser Control 116
Database Browser Control 115
Database Browser Control properties 125
Database Browser Information table 120
Database Browser task 115
Distributed 21
Distributed Alarm Logger 17
Distributed Alarm Server panel 22
E
ECSConvert.exe 145
F
FactoryLink 7.0 graphic tools 143
FactoryLink 7.0 Overview 9
File directories iin Graphics conversion 145
C
Client Builder 143
Client Builder vs. Application Editor 10
Client/Server Environment 9
Configuration Explorer vs. Configuration Manager
10
Configure the Alarm Server 26
Configure the System Configuration table 30
Conversion considerations 117
Conversion Overview 12
Conversion procedure 15, 23
Convert the FactoryLink application 24
Converted animation types 149
Converted object types 148
Converting Historical Trend 54
G
Graphics conversion considerations 144
Graphics conversion evaluation 157
Graphics conversion procedure 151
Graphics conversion summary 157
I
Interval Timer Information panel 22
M
Miscellaneous conversion issues 159
FactoryLink / Conversion Guide / 181
N
New development tools 10
S
Set up the Alarm parameters 34
Set up the Alarm View display 42
Set up the Alarm Viewer properties 45
T
Trend Conversion Procedure 54
U
USER vs. SHARED domain 13
182 / FactoryLink / Conversion Guide