Version 2.

FANUC Spares
Proprietary Notice

The manual and software contain confidential information which represents trade secrets of Intellution,
Inc. and/or its suppliers, and may not be copied or disclosed except as provided in the license with
Intellution, Inc. The information in this manual is subject to change without notice and should not be
construed as a commitment by Intellution, Inc. Intellution, Inc. assumes no responsibility for any errors
that may be in this document.

©2003 GE Fanuc International, Inc. All rights reserved. All other brands or names are property of their respective holders.

Trademarks

Microsoft® Visual Basic® Technology. ©1996, Microsoft Corporation. ALL RIGHTS RESERVED.
 Contents
1. Introduction .........................................................................................................................1

Who Should Read this Manual.....................................................................................1

What You Need to Know to Complete this Migration ...................................................1

2. Before Migrating to iFIX......................................................................................................3

Recommended System Configuration..........................................................................3

Compatibility of FIX Nodes on the Network..................................................................4
New Command Scripts.................................................................................................5
Converting FIX Versions 6.x and 7.x Functionality.......................................................7
Converting Alarm Functionality .......................................................................8
Converting Database Functionality .................................................................9
Converting DDE Functionality (Dynamic Data Exchange) ............................10
Converting Historical Functionality ................................................................12
Converting I/O Drivers ..................................................................................13
Converting the Message Handler Package (MHP) Functionality ..................14
Converting ODBC (Open Database Connectivity) Functionality ...................14
Converting OPC Server Functionality ...........................................................15
Converting Picture Functionality ...................................................................16
Converting Key Macro Files .........................................................................20
Converting Recipe Files ................................................................................20

Contents i

FANUC Spares
 Converting Security Files ..............................................................................20
Converting the System Configuration Utility .................................................20

3. Migrating to iFIX ................................................................................................................21

Backing up Files .........................................................................................................21

Networking Computers...............................................................................................22
Obtaining Updates......................................................................................................22
Completing Tasks on the Current FIX Installation......................................................23
Manually Exporting Files ...............................................................................23
Completing Tasks on the iFIX Target Machine ..........................................................25
Installing iFIX Software...............................................................................................26
Setting Up the System Configuration Utility ...............................................................27
Verifying the I/O Driver and Database Migration .......................................................28
Completing the Migration ..........................................................................................29

4. Converting Pictures ..........................................................................................................33

Using the Picture Conversion Utility ...........................................................................33

5. Migrating to iFIX with DDA Drivers..................................................................................35

Finding and Replacing a Tag in iFIX .............................................................35

Index .......................................................................................................................................37

ii Migration Guide
1. Introduction
The iFIX Migration Guide contains information to help you transition from
FIX v6.x or v7.x to iFIX. The guide contains these five chapters:

Introduction – describes the guide, who should read it, and what you need to
know to complete the migration.

Before Migrating to iFIX – provides new information and describes required

pre-migration tasks.

Migrating to iFIX – details the migration process.

Converting Pictures – explains how to convert pictures created in previous

versions of FIX.

Migrating to iFIX with DDA Drivers – discusses several issues when you
migrate to iFIX while using the BR3, LIN, ROC, or MBR driver.

Who Should Read this Manual

The iFIX Migration Guide v2.5 manual is intended for people in your
organization who are responsible for migrating your system from FIX v6.x
or 7.x to iFIX.

What You Need to Know to Complete this

Migration
This manual assumes you have knowledge of the Windows environment,
including Windows NT v4.0 or Windows 2000, and a basic understanding of
iFIX operations and concepts.

Chapter 1. Introduction 1

FANUC Spares
 Individuals performing this migration should also have some understanding
of Visual Basic or Visual Basic for Applications (VBA). This foundation
will help you develop your iFIX system.

2 Migration Guide
2. Before Migrating to iFIX
This chapter provides information you need before installing iFIX including:

• Recommended system configuration

• Compatibility of FIX nodes on the network

• New command scripts

• Functionality conversion from FIX v6.x or v7.x to iFIX

Recommended System Configuration

iFIX runs on Windows NT and Windows 2000. Windows 95 and Windows
98 are not supported by iFIX. Intellution recommends that you use the
system configuration listed in the following table to run iFIX. The physical
memory and the CPU clock speed recommendations in the table are only
minimum requirements. System performance improves when minimum
requirements are exceeded.

NOTE: iFIX supports Symmetrical Multiprocessor (SMP) computers.

Table 2-1: Recommended System Configuration

Operating System Microsoft Windows NT 4.0 SP5 (with IE 5.0 or

greater) or Windows 2000.

Minimum CPU 266 MHz Intel Pentium II. Intel Celeron is

Clock Speed supported but not recommended.

Minimum Physical 96 MB (iClients), 128 MB or greater (SCADA)

Memory

Chapter 2. Before Migrating to iFIX 3

FANUC Spares
 Table 2-1: Recommended System Configuration (continued)

Available Hard A minimum of 120 MB of free hard drive space

Drive Space required to install typical iFIX system, including
pictures, databses, alarm files, and other data files.
More space is needed for local installation of
electronic documentation.

Video Specifications 64K+ Colors, 600 x 800 (1024 x 768 recommended

for iClients)

Compatibility of FIX Nodes on the Network

This section describes the compatibility of FIX nodes on the network. Use
the table below to determine from which FIX SCADA nodes you can
retrieve data and alarms when running an iClient node.

Table 2-2: Compatibility of FIX Nodes on the Network

If you are running a View You can get data and alarms from these
Client… SCADA Servers

FIX for Windows NT/95 v6.x • FIX for Windows v5.5 /10
• FIX for Windows v5.5 /30
• FIX for Windows v5.65
• FIX for Windows NT/95 v 6.x or v7.x
• iFIX

4 Migration Guide
 Table 2-2: Compatibility of FIX Nodes on the Network (continued)

If you are running a View You can get data and alarms from these
Client… SCADA Servers

FIX for Windows NT v7.0 • FIX for Windows v5.5 /10

• FIX for Windows v5.5 /30
• FIX for Windows v5.65
• FIX for Windows NT/95 V6.x or v7.x
• iFIX

iFIX • FIX for Windows v5.5 /30

• FIX for Windows v5.65
• FIX for Windows NT/95 v6.x or v7.x
• FIX for Windows NT v7.0
• iFIX

New Command Scripts

iFIX uses new global subroutines instead of the FIX32 Command Language
scripts. The following table lists the FIX32 command scripts (versions 6.x
and 7.x) and their equivalent iFIX global subroutines.

Table 2-3: iFIX Global Subroutines

This FIX32 Command Is replaced by this iFIX Global Subroutine...

Script...

ALARMACKALL AcknowledgeAllAlarms([Picture As String])

ALARMACK AcknowledgeAnAlarm([DataPoint As String])

CLOSEDIG CloseDigitalPoint([DigitalPoint As String])

CLOSEPIC ClosePicture([Picture As String])

Chapter 2. Before Migrating to iFIX 5

FANUC Spares
 Table 2-3: iFIX Global Subroutines (continued)

This FIX32 Command Is replaced by this iFIX Global Subroutine...

Script...

DISABLEALARM DisableAlarm([DataPoint As String])

ENABLEALARM EnableAlarm([DataPoint As String])

LOGIN and LOGOUT LogIn()

FINDLINK LocateObject(ObjectName As String, [bRelative

As Boolean])

OFFSCAN OffScan([DataPoint As String])

ONSCAN OnScan([DataPoint As String])

OPENDIG OpenDigitalPoint([DigitalPoint As String])

OPENPIC OpenPicture([Picture As String], [PictureAlias As

String], [TopPosition], [LeftPosition])

OPENPIC OpenTGDPicture([sPicture As String],

[sPictureAlias As String], [fTop], [fLeft],
[sTagGroup As String])

SETNICKNAME PictureAlias(PictureAlias As String)

RAMP RampValue(RampValue As Double, ByPercent As

Boolean, [DataPoint As String])

GETVAL ReadValue([DataPoint As String])

REPLACEPIC ReplacePicture(NewPicture As String, [OldPicture

As String], [TagGroupFileName As String])

REPLACEPIC ReplaceTGDPicture(sNewPicture As String,

sTagGroup As String, [sOldPicture As String =
""])

SETAUTO SetAuto([DataPoint As String])

SETMANL SetManual([DataPoint As String])

6 Migration Guide
 Table 2-3: iFIX Global Subroutines (continued)

This FIX32 Command Is replaced by this iFIX Global Subroutine...

Script...

TOGGLEDIG ToggleDigitalPoint([DigitalPoint As String])

TOGGLEMANL ToggleManual([DataPoint As String])

TOGGLESCAN ToggleScan([DataPoint As String])

SETVAL WriteValue(Value As String, [DataPoint As

String])

MESSAGE System.SendOperatorMessage(Text As
String,[Nodename As String])

FILEOPEN Open
FILECLOSE Close
FILEREAD Input #
FILEWRITE Write #

NOTE: These four entries are standard Visual

Basic statements, not iFIX global subroutines.
See the Visual Basic Reference Help for additional
information.

Converting FIX Versions 6.x and 7.x

Functionality
This section describes the functionality in FIX versions 6.x and 7.x that
converts to iFIX. Although a small percentage of v6.x and v7.x functionality
does not convert to iFIX, iFIX offers more overall system capability and
extensibility.

Each of the following sections begins with a table that provides a quick
description of how specific functionality is converted. The subsequent
subsections provide more detailed conversion information.

Chapter 2. Before Migrating to iFIX 7

FANUC Spares
 Converting Alarm Functionality

This section describes how the FIX v6.x and v7.x Alarm functionality
converts to iFIX.

Table 2-4: Alarm Functionality Conversion Quick Reference

FIX v6.x and v7.x How does it convert to iFIX?

Function

Alarm Areas Converts directly.

Alarm Horn You can access this functionality:

• Through the Alarm Horn Task
Wizard in configuration mode.
• By writing scripts with the
following methods in run mode:
• system.silencealarmhorn
• system.enablealarmhorn
• system.disablealarmhorn

Alarm Counter Converts directly.

Alarm Areas

The FIX v6.x and v7.x A-P alarm areas are compatible with iFIX. No
special conversion is needed.

Alarm Horn
iFIX has an alarm horn that causes the computer’s speaker to beep
whenever unacknowledged alarms are present. No special conver-
sion is needed.

8 Migration Guide
 Alarm Counter

FIX v6.x and v7.X alarm counters convert directly to iFIX. No special
conversion is needed.

Converting Database Functionality

This section describes how the FIX v6.x and v7.x Database functionality
converts to iFIX.

Table 2-5: Database Functionality Conversion Quick Reference

FIX v6.x and v7.x Function How does it convert to iFIX?

Process Database (PDB) Converts directly.

Easy Database Access Converts directly.

(EDA) Programs

Historical Data Access Converts directly.

(HDA) Programs

Database Dynamos Converts directly.

Database (Process Database)

FIX v6.x and v7.x Process Database files automatically convert to the iFIX
format. Ensure that the FIX v6.x or v7.x .PDB database file is located in the
\Dynamics\PDB directory, and than start iFIX. The conversion occurs when
iFIX starts up. You can also copy the file into the PDB folder, start iFIX, and
then run DBCVT.exe, before starting the Database Manager. DBCVT.exe is
a database conversion utility located in the \Dynamics directory.

Chapter 2. Before Migrating to iFIX 9

FANUC Spares
 Easy Database Access (EDA) and Historical Data Access (HDA)
Programs

Existing applications that use EDA and HDA work with iFIX. However,
EDA programs built under the v6.x or v7.x FIX Integration Toolkit are not
able to send or receive alarms. You must recompile and link the program
using the iFIX Integration Toolkit to access this functionality.

Database Dynamos

To use your Database Dynamos, you must recompile them with the iFIX
Database Dynamo Toolkit. Follow the steps outlined in the iFIX Database
Dynamo Toolkit and the Database Converter will update your Database
Dynamos. The Database Converter runs whenever iFIX is started.

NOTE: The Database Dynamo conversion process is detailed in the new

iFIX Database Dynamo Toolkit.

Converting DDE Functionality (Dynamic Data

Exchange)

This section describes how the FIX v6.x and v7.x Dynamic Data Exchange
functionality converts to iFIX. For more information on any of the DDE
functionality discussed in this section, refer to the Using DDE manual.

Table 2-6: DDE Functionality Conversion Quick Reference

FIX v6.x and v7.x How does it convert to iFIX?

Function

Process Database as a DDE Converts directly.

Server

Process Database as a DDE Converts directly.

Client

10 Migration Guide
 Table 2-6: DDE Functionality Conversion Quick Reference (continued)

FIX v6.x and v7.x How does it convert to iFIX?

Function

Pictures as a DDE Client Use OPC or ODBC in place of

DDE to bring external data
into an iFIX picture.

Report Generator Use Crystal Reports or some

other reporting option.

Process Database as a Server

iFIX can act as a server to other DDE-aware applications. Use the same
DDE syntax that you use to access the FIX v6.x or v7.x process database.

Process Database as a Client

You can bring data into the iFIX Process Database through the DDE Driver
in the same way you bring it into the FIX v6.x or v7.x Process Database.

The Intellution WorkSpace (Pictures) as a Client

DDE is not supported within the Intellution WorkSpace. Use OPC or ODBC
(with VisiconX) to bring data into an iFIX picture.

Report Generator

The FIX v6.x and v7.x Report Generator is not supported by iFIX because it
uses DDE. However, iFIX works with Crystal Reports and many other third
party reporting tools. For example, you can:

• Access Crystal Reports through a wizard in the Scheduler.

• Use VBA Automation to create reports in Word or Excel.

• Use the iFIX ODBC drivers to generate reports in Access.

Chapter 2. Before Migrating to iFIX 11

FANUC Spares
 The Crystal Report run-time DLLs are now included with iFIX to provide
the capability of running developed Crystal Reports on all your iFIX
iClients. Note that this is not the complete Crystal Reports tool.

Converting Historical Functionality

This section describes how the FIX v6.x and v7.x Historical functionality
converts to iFIX.

Table 2-7: Historical Functionality Conversion Quick Reference

FIX v6.x and v7.x How does it convert to iFIX?

Functions

Historical Assign (HTA) No conversion needed.

files

Chart Groups, Pen Groups, iFIX does not use these existing
Time Groups groups to view historical data.

Existing Historical Data No conversion needed.

Lab Data This functionality can be

accessed through iFIX scripting.

Existing SQL Queries This functionality can be

accessed through iFIX scripting.

Remote Historical iFIX does not support Remote

Historical functionality.

Historical Assign (HTA) Files

Historical Assign (HTA) has not changed. Simply open your FIX v6.x or
v7.x .HTA files using the iFIX Historical Assign program.

12 Migration Guide
 Chart Groups, Pen Groups, Time Groups

The Historical Display program does not exist in iFIX. Existing Chart
Groups, Pen Groups, and Time Groups are also not used in iFIX. Instead, in
iFIX you view historical data in the Chart Object of a picture. You can
create and configure new Chart Objects within a picture in the Intellution
WorkSpace or use the Chart Group Wizard.

Existing Historical Data

You can view historical data from FIX v6.x or v7.x nodes using the Chart
Object in an iFIX picture.

Lab Data

You cannot view lab data directly in a Chart Object. To view the data, you
need to convert the lab data into a relational database and use scripting to
view the data.

Existing SQL Queries

You cannot view SQL data directly in a Chart Object. You can use scripting
to view the data.

Converting I/O Drivers

FIX v6.x and v7.x I/O Drivers work with iFIX, but you must first export
them. For more information, see the Manually Exporting Files section in the
Migrating to iFIX chapter.

Chapter 2. Before Migrating to iFIX 13

FANUC Spares
 Converting the Message Handler Package (MHP)
Functionality

The Message Handler Package is not a part of iFIX, but you can duplicate
this functionality within the iFIX environment. As an example, add a simple
text object to a picture and animate the caption of that text object. Use the
Table Conversion option and map an integer value into a text string. When
the value of the datasource changes, the text on the screen also changes.

Converting ODBC (Open Database Connectivity)

Functionality

This section describes how the FIX v6.x and v7.x ODBC functionality
converts to iFIX.

Table 2-8: ODBC Functionality Conversion Quick Reference

FIX v6.x and v7.x How does it convert to

Function iFIX?

From the Process Database Converts directly.

(SQT & SQD Blocks)

The ODBC Data Source No conversion needed.

From Pictures (with the This functionality can be

Command Language) accessed through iFIX
scripting or using
VisiconX.

ODBC Configuration in the The SCU ODBC

System Configuration Configuration must be
Utility (SCU) reconfigured.

14 Migration Guide
 SQT & SQD Blocks

FIX v6.x and v7.x Process Database files will automatically convert to the
iFIX format. Locate the FIX v6.x or v7.x *.PDB file in the Dynamics\Pdb
directory and start iFIX v2.5. The conversion occurs when iFIX starts up.
You can also copy the file into the PDB folder, start iFIX and run
DBCVT.exe, before starting the Database Manager. DBCVT.exe is a
database conversion utility located in the \Dynamics directory.

ODBC Data Source

The ODBC Data Source is configured in the Windows NT Control Panel and
is not affected by Intellution software.

From Pictures (with the Command Language)

The easiest way to view data from an OBDC data source in a picture is to use
VisiconX. This powerful tool requires no scripting and is easy to use.

Converting OPC Server Functionality

All Intellution OPC servers developed with the v7.1 toolkit operate under
iFIX.

NOTE: The OPCNIO.DLL option that converts v6.x drivers into OPC
Servers is no longer provided by Intellution, nor will it work with iFIX. All
new Intellution OPC Servers are built using the v7.1 OSDK toolkit. All v6.x
I/O drivers work with iFIX.

Chapter 2. Before Migrating to iFIX 15

FANUC Spares
 Converting Picture Functionality

This section describes each FIX v6.x and v7.x Picture functionality that
converts to iFIX.

Table 2-9: Picture Conversion Functionality Quick Reference

FIX v6.x and v7.x Function How does it convert to

iFIX?

Subpicture Functionality You can achieve this

functionality through
scripting.

Shapes and Bitmaps Converts directly.

Graphic Dynamos By making the Dynamo Set a

picture, you can the convert
directly, although scripts do
not convert.

BDF files You can achieve this

functionality through
scripting.

Command Language Scripts You can achieve this

functionality through
scripting.

Layout Files A default layout is available

by using the WorkSpace User
Preferences.

Tag Groups Converts directly.

Picture Templates You can achieve this

functionality by creating read-
only picture files.

Zoom To Functionality You can achieve this

functionality through
scripting.

16 Migration Guide
 Subpictures

Subpicture functionality is not available in iFIX. However, you can create

an Always on Top picture through scripting. For more information, refer to
the OpenPicture Subroutine or the Open Method in the iFIX Automation
Reference Help.

To create an Always on Top Picture:

[1] Select the picture you want to create as an Always on Top Picture.

[2] Click the right mouse button anywhere in the Intellution WorkSpace.
A popup menu appears.

[3] Select Picture from the popup menu. The Edit Picture dialog box
appears.

[4] Select the Always on Top check box in the Edit Picture dialog box,
to create a picture that will display on top of other pictures.

The difference between the Subpictures functionality in FIX v6.x and v7.x
and the Always on Top picture described above is that the picture does not
close automatically when the picture that opened it closes.

Shapes and Bitmaps

The Picture Conversion Utility converts shapes, bitmaps, and dynamic

properties in FIX v6.x and v7.x pictures to their closest iFIX equivalent.

Graphic Dynamos

Graphic Dynamos are converted to objects in iFIX. Scripts do not convert.

Details for this process are included in the Using the Picture Converter
Utility section of the Creating Pictures manual.

Chapter 2. Before Migrating to iFIX 17

FANUC Spares
 BDF Files (Block Definition Files)

BDF files are not available in iFIX. However, you can view the information
contained in BDF files by creating a picture or by creating a user form in
VBA.

Command Language Scripts

iFIX does not support the FIX Command Language. iFIX translates all
Command Language scripts to comments in the VBA script attached to the
converted picture. All Command Language functionality exists in VBA.

Script Converter Tool

The Script Converter Tool converts Intellution’s FIX32 Command Language

scripts, which appear as comments in iFIX VBA, to equivalent VBA code.
This tool is used in conjunction with the iFIX Picture Converter. Use the
Script Converter after converting the FIX Object Definition Files (.ODF
files) to iFIX Graphic Files (.GRF files).

The Script Converter scans through the VBA code searching for
unconverted FIX32 Command Language scripts which are contained as
comments in iFIX pictures. When a script is found, it is converted to its
equivalent VBA code. The original FIX32 script remains as a comment.

This tool is available to all iGlobalCare Complete customers on the

Intellution Knowledge Base CD.

NOTE: The Script Converter Tool is not an Intellution-supported tool. It is

important to read the Script Converter documentation included on the
Knowledge Base CD before using it.

18 Migration Guide
 Layout Files

While iFIX does not contain layout files, you can configure a default layout
through User Preferences in the WorkSpace:

[1] Select User Preferences from the WorkSpace menu. The User
Preferences dialog box appears.

[2] Click the Startup Pictures tab. The pictures listed in this dialog box
open when you start the WorkSpace in run mode.

[3] To configure the position of the pictures on the screen:

[a] In WorkSpace configuration mode (using full screen mode if

applicable), position the picture where you want it to appear.

[b] Click the right mouse button anywhere in the WorkSpace. A

popup menu appears.

[c] Select Update Window Location from the popup menu.

[d] Click Save.

Tag Groups

You can convert FIX v6.x and v7.x Tag Group files by using the iFIX Tag
Group Editor.

To convert FIX v6.x or v7.x Tag Group files:

[1] Open the file in the FIX v6.x or v7.x Tag Group Editor.

[2] Save the file as a .CSV file.

[3] Select Convert .CSV files to .TGD Files from the File menu. The
Tag Group Editor converts the files.

For more information about Tag Groups, refer to the Creating Pictures and
Creating Recipes manuals.

Chapter 2. Before Migrating to iFIX 19

FANUC Spares
 Picture Templates

While iFIX does not support the use of picture templates, you can duplicate
this functionality by creating read-only pictures. You can open and edit
these pictures, but you must save them by using a new name, thereby
preserving the original read-only file as a template.

Zoom To Functionality

You can duplicate the Zoom To functionality through scripting.

Converting Key Macro Files

Existing Key Macro Files do not convert to iFIX. However, iFIX v2.5 has a
Key Macro Editor with a wizard that lets you create new key macros quickly
and easily.

Converting Recipe Files

FIX v6.x and v7.x recipe files will work with iFIX, but you must export
them. For more information, see the Manually Exporting Files section in the
Migrating to iFIX chapter.

Converting Security Files

FIX v6.x and v7.x security files will work with iFIX, but you must export
them. For more information, see the Manually Exporting Files section in the
Migrating to iFIX chapter of this manual.

Converting the System Configuration Utility

The System Configuration Utility converts to iFIX. You must export the
settings to an .RPT file and then re-enter them in the iFIX SCU. For more
information on exporting SCU settings, see the Manually Exporting Files
section in the Migrating to iFIX chapter of this manual.

20 Migration Guide
3. Migrating to iFIX
This section describes iFIX migration tasks, including:

• Backing up your files.

• Networking machines.

• Getting updates.

• Tasks to complete on the computers involved in the upgrade.

Backing up Files
Intellution recommends that you back up your current FIX installation
before proceeding with the migration to iFIX. If a complete backup is not
possible, ensure that, minimally, the following files are backed up:

• FIX/Local Files – .INI, .SCU.

• Picture (PIC) path files – .ODF, .LYT, .SBL, .TGE, .KMX.

• Database (PDB) path files – all files.

• Historical path files – all files.

• Historical Data path files – all files.

• Security Files – export current configuration from the SCU. Consult

the FIX documentation for more information on this feature.

• The STARTUP.XLA file located in the Microsoft Excel path.

• Master and Control Recipes – .RCC, .RCM.

Chapter 3. Migrating to iFIX 21

FANUC Spares
 Networking Computers
If you are installing iFIX on a computer other than the one currently running
the application, connect the two machines using a network. If there is no
network connection, then you must copy files that you manually export to
the target machine using removable media.

Obtaining Updates
Intellution recommends that you obtain the following updates before
migrating to iFIX:

• Download the latest SIMs and the latest drivers from the Intellution
web site, http://support.intellution.com:500/downloads/sims/.

• Check with Intellution Technical Support for any new updates.

• Download iFIX add-ons, such as the Dynamo Wizard. Copy and

expand these files on the iFIX computer.

• Check for new utilities available for download, located on the iFIX
Developers’ Corner page on Intellution’s web site, http://
support.intellution.com.

22 Migration Guide
 Completing Tasks on the Current FIX
Installation
Complete the following tasks on the computer containing your current FIX
installation. Note, document, and correct errors when applicable.

[1] Verify the FIX Process Database by selecting Verify from the
Database menu, located in the Database Builder.

[2] Export the FIX HTA file by selecting Export from the File menu,
located in Historical Assign. Import the HTA configuration back into
the Historical Assign file by selecting Import from the File menu.

[3] Click the I/O Control tab from Mission Control, and note the Time
Outs, the Retries, and the DRVST* error codes.

[4] Click the HTC tab from Mission Control and check for overruns.

[5] Click the SQL tab from Mission Control and check for errors.

Manually Exporting Files

To manually export FIX files, complete the following procedure on the

computer containing your current FIX installation. You must first create a
new directory for the exported files before you begin.

To manually export files:

[1] Start the current installation of FIX (if it is not already running).

[2] If security is enabled, log in using a user account with Administrator

rights.

[3] Start the System Configuration Utility (SCU). If Security is not

enabled, advance to step 7.

[4] Enter the Security Configuration by selecting Security from the

Configure menu.

Chapter 3. Migrating to iFIX 23

FANUC Spares
 [5] Select Export from the File menu. Note the location of the exported
files and select Save. Passwords are not exported and you must
recreate them later.

[6] Select Exit from the File menu in the Security Configuration program
to return to the SCU.

[7] Select Report from the File menu of the SCU main screen. Note the
file name (NodeName.RPT) and location. Intellution recommends
that you use Notepad to print this report for future reference.

[8] Select SCADA from the Configure menu. The SCADA

Configuration dialog box appears. Select an installed driver (other
than SIM or DDE), and then click the Configure button.

[9] Once the Configurator has started, select Save As from the File menu
and specify CSV file type. Repeat this step for each Channel of each
Driver currently installed. Note the file names and locations for later
use.

[10] Exit the SCU.

[11] If the current project uses recipes (RCP.EXE), start Recipe Manager.
Otherwise, advance to Step 13.

[12] From the File menu in the Recipe Manager, select Save As .RCX
(Master text) or .RCY (Control text) for each Master and Control
Recipe. Note the file names and locations.

[13] If the current project contains Tag Groups, start the Tag Group Editor
(TGE.exe). Otherwise, advance to Step 15.

[14] Open a .TGE file, select Save As from the File menu, and specify file
type .CSV. Repeat this step for each tag group file. Note the file
names and locations for later use. When finished, exit the Tag Group
Editor.

[15] If iFIX is to be installed on a different machine, and the current FIX

and target machines are on the network, share the FIX directory to
allow network access. Otherwise, make a copy of all the files you
created in the previous steps.

24 Migration Guide
 NOTE: FileWedge, available at http://www.taltech.com, is a utility that you
can use to automatically export files. Using FileWedge, you can open, edit,
and save hundreds of files without user intervention. FileWedge uses an
ASCII file as a template for an integral SendKeys program, which can send
an automated series of Keystrokes into any currently active window.

For example, to create a .TXT file containing a list of all the TGE files in the
FIX32\PIC directory, you enter the following at the command line:

DIR C:\FIX32\PIC\*.TGE /B > TGELIST.TXT

Using FileWedge, you can now operate on the entire file list.

Completing Tasks on the iFIX Target Machine

Complete the following tasks on the computer where you are installing iFIX.
To complete these tasks, you must log in to Windows NT or Windows 2000
with a user account that has administrative rights on the local machine.

[1] If applicable, convert to Windows NT or Windows 2000. The

computer on which iFIX is to be installed must be running the
Windows NT 4.0 or Windows 2000 operating system. Windows 95
and Windows 98 are not supported.

[2] Check the computer and its installed software. From the Start menu,
select Programs, then select Administrative Tools, and then select
Event Viewer. Inspect the System and Application entries. Note,
document, and correct any errors. Contact the System Administrator
if you need assistance.

[3] Check the size of the current Swap file. Follow Intellution’s
recommendations for correctly sizing the Swap file. Contact the
System Administrator if you need assistance sizing the Swap file.

[4] Verify the virtual memory setting. Your virtual memory should be set
to 2.5 times the physical memory (RAM). If you are unsure of how
to change the Virtual Memory settings on your operating system,
contact your System Administrator for assistance.

Chapter 3. Migrating to iFIX 25

FANUC Spares
 [5] If networked, verify that the network is functioning properly. If using
TCP/IP as a network protocol, verify that all Hosts files are correct
and current on all FIX nodes on the network.

[6] If applicable, turn off anti-virus software. Disable the software and
reboot your computer before you install iFIX. Once your upgrade is
complete, you may restart your anti-virus software.

Installing iFIX Software

If you plan to install iFIX on the computer currently running FIX, complete
the following steps:

[1] Ensure your FIX software is not running, and close any other
programs that are running.

[2] Log in to Windows NT or Windows 2000 with Administrator

privileges.

[3] Insert the iFIX CD into the CD-ROM drive. If Setup does not start
automatically, select Run from the Start menu. Enter your CD drive
letter, followed by a colon and a backslash and the command
Setup.exe, (for example, D:\Setup.exe), and then click OK.

[4] From the iFIX Welcome screen, select Install.

[5] Select NO, do not use the current SCU information when you see the
prompt “SCU found do you want to use its information?”

[6] When prompted for the Destination Folder, select a unique folder.
Do not install over the current FIX installation. When finished,
select Next.

[7] Intellution recommends that you select Typical install.

[8] Enter your Nodename. Refer to the NodeName.RPT report described

in the Manually Exporting Files section if you do not have this
information.

26 Migration Guide
 [9] Enter the Node Type and Network Type, if applicable, and then click
OK.

[10] Enter Remote SCADA nodes, if applicable. Verify that IP and

Names are in the Hosts file.

[11] Install applicable Drivers. (Check Intellution’s web site, http://

support.intellution.com:500/downloads/sims/, for the latest releases.)
You must install the drivers before the migration of the Process
Database (PDB).

[12] View the Release Notes and restart the computer.

[13] Log in to NT or 2000 with Administrator privileges. While this is not

necessary at this time, it can prove helpful if you encounter problems.

[14] Install applicable iFIX SIMs and add-ons from the Intellution web
site.

Setting Up the System Configuration Utility

Once iFIX is installed, complete the following steps to set up the System
Configuration Utility on the iFIX node:

[1] Start the iFIX SCU.

[2] Verify that the Node name is correct. Refer to the NodeName.RPT
report described in the Manually Exporting Files section for this
information.

[3] Enter the Database Name you want to use. Ensure it is the same
name as the previous project. When prompted, select Use Anyway.

[4] Select SCADA from the Configure menu to verify that drivers are
present. If required, add the SIM and DDE driver to the Configured
I/O Drivers list.

[5] Select your current Driver from the list of Drivers and then click the
Configure button.

Chapter 3. Migrating to iFIX 27

FANUC Spares
 [6] From the Driver Configurator, select Open from the File menu.
Change List Files of Type to .CSV in the combo box. From the
Folders List, browse to the file you created in step 9 of the Manually
Exporting Files section.

[7] Select Save As from the File menu and save the changes to the
\Dynamics\Pdb directory. Repeat this process for each Driver and
Channel in use on the project.

[8] Save and Exit the Driver Configurator when you complete these tasks
for all drivers.

[9] Save and Exit the SCU.

Verifying the I/O Driver and Database

Migration
After configuring the SCU, complete the following procedure to verify the I/
O driver migration and to convert the Process Database:

[1] Start iFIX.

[2] Start Mission Control.

[3] Select the I/O Control tab and examine the information. Ensure that
data is being polled. If data is present, advance to Step 6.

[4] If there is no data present, ensure that the Driver is loaded and is
running. Exit Mission Control and select System Configuration to
start the SCU.

[5] Select SCADA from the Configure menu, select the I/O driver and
verify that the Poll Records are present. If they are not present,
repeat steps 6 and 7 in the Setting Up the System Configuration
Utility section.

NOTE: It is very important that the Drivers are loaded before

proceeding with conversion of the Process Database.

28 Migration Guide
 [6] Minimize the WorkSpace.

[7] Using Windows Explorer, copy the PDB you want to convert to the
iFIX PDB Directory.

[8] Select Run from the Start menu, and enter:

<DriveLetter>:\Dynamics\dbcvt.exe.

The Command Window closes automatically when the conversion

completes.

[9] Maximize the iFIX WorkSpace and then:.

[a] Start Database Manager from the WorkSpace System Tree.

[b] Select Reload from the Database menu, located in the Database
Manager.

[c] Select the converted PDB file to open the Process Database
from the file lists.

[10] Save and exit Database Manager.

[11] Errors that occur during the database conversion are written to the
error log file (dbcvt.err). You can open this file in any text editor.
Use this log file to identify the individual tags causing the problems.
Consult your manual or contact Intellution for more details on how to
troubleshoot database conversion errors.

Completing the Migration

After converting and successfully running the I/O Drivers and Process
Database, complete the following steps to finish migrating the FIX files:

[1] Use Windows Explorer to copy the old HTA files to the location
specified in the Path Configuration in the SCU.

[2] Copy the HTRDATA files to the location specified in the Path
Configuration in the SCU.

Chapter 3. Migrating to iFIX 29

FANUC Spares
 [3] Start Historical Assignment:

[a] Select Open from the File menu.

[b] Navigate and locate the file you created in the Manually
Exporting Files procedure.

[c] Open the file and save it to the \Dynamics\Htr directory.

[4] If you have Recipes you want to import, do so now.

[a] Select New Recipe from the FIX Recipes directory, located in
the system tree in the WorkSpace.

[b] Open the .RCX and .RCY files created during the Manually
Exporting Files procedure.

[c] Save each file to the new \Dynamics\Rcm or \Dynamics\Rcc

directory.

[d] When you are finished, exit the Recipe Builder.

[5] If you have Tag Group Editor files, start the Tag Group Editor.

[a] Select Open from the File menu.

[b] Change File of Type to .CSV.

[c] Browse to the files you created in the Manually Exporting Files
procedure from the Folders List.

[d] Open and save them to the \Dynamics\Pdb directory.

[6] If you want to import your old security configuration, you can do so
now:

[a] Select Setup from the Security directory from the WorkSpace
System Tree.

[b] Select Import from the file menu from the Security
Configuration main menu.

30 Migration Guide
 [c] Browse to the file you created in the Manually Exporting Files
procedure from the Folders List.

[d] Select Open, and follow the prompts. Passwords may need to
be re-entered for the User configuration.

[e] You can optionally enable security at this time. When done,
exit and save changes.

[7] Convert the FIX .ODF file to iFIX .GRF files. Use the notes in the
Converting Pictures chapter for more information.

Chapter 3. Migrating to iFIX 31

FANUC Spares
32 Migration Guide
4. Converting Pictures
This chapter describes how to use the Picture Conversion Utility to convert
pictures created in previous versions of FIX. The following information
describes how to use the utility and how to download upgrades as they
become available.

Additional information about the utility is available in the Using the Picture
Converter Utility section of the Creating Pictures manual.

NOTE: The Picture Conversion Utility converts pictures to iFIX from FIX
versions 5.65, 6.0, 6.12, 6.15, and 7.0.

Using the Picture Conversion Utility

You can use the Picture Conversion utility to simultaneously convert
multiple pictures.

To use the Picture Conversion utility:

[1] Copy your FIX v5, v6.x or v7.x database to the Dynamics\Pdb
directory.

[2] Ensure that the iFIX WorkSpace is running.

[3] Ensure that the database your pictures reference is the currently-
loaded database. If it is not, open the Database Manager and reload
the database.

If any of the pictures reference tags on remote nodes, then the remote
nodes must be running and a connection to them must be established.

[4] Double click the picture conversion utility (PictureConverter.exe) to

open it. This file is located in your Dynamics directory.

Chapter 4. Converting Pictures 33

FANUC Spares
 [5] When the utility opens, select Set Destination Directory from the File
menu and select the destination directory for the converted pictures.

[6] Select Open ODF File to Convert from the File menu. The Select
Picture Files for Conversion dialog box appears.

[7] Browse to the directory where the FIX pictures you want to convert
are located.

[8] Select the pictures to be converted, and click the Open button. The
utility converts the pictures selected, sending any conversion
warnings or errors to the utility window.

NOTE: Error and warning information is also written to the

PictureName.log file.

For additional information on using the Picture Converter utility, refer to the
Using the Picture Converter section of the Creating Pictures manual.

You can download upgrades for the Picture Converter utility from the
Developers’ Corner page on the Intellution Web site, located at http://
support.intellution.com:500/downloads.

34 Migration Guide
5. Migrating to iFIX with DDA Drivers
This chapter discusses finding and replacing a tag when you migrate to iFIX
while using the BR3, LIN, ROC, or MBR driver.

Finding and Replacing a Tag in iFIX

When using the Find and Replace operation in iFIX, you must add another
pair of backslashes around the first backslash, as shown in the following
example. These additional backslashes are needed because the first
backslash is considered part of the tag’s address.

FIX32.Fix.\\’Device1:Record1\\’.F_40001

Chapter 5. Migrating to iFIX with DDA Drivers 35

FANUC Spares
36 Migration Guide
 Index
database Dynamos 10
A DDE 10

alarm areas 8
alarm counter 9 E
alarm horn 8
Easy Database Access (EDA) programs 10
exporting
B FIX files not automatically exported 23

backing up files 21
BDF 18 F
block definition files
see BDF files
backing up before migrating 21
manually exporting 23
C FileWedge utility 25
finding and replacing a tag 35
Chart Group Wizard 13 FIX Nodes
chart groups 13 compatibility on the network 4
Command Language Scripts 18 FIX32 command scripts 5
Command scripts functionality conversion
corresponding iFIX global subroutines 5 alarm areas 8
completing the migration 29 alarm counter 9
converting pictures 33 alarm horn 8
converting to iFIX database dynamos 10
functionality conversion 7 database files 9
tasks to complete on the iFIX target DDE 10
machine 25 historical 12
CPU I/O Drivers 13
recommended clock speed 3 Key Macro Files 20
MHP 14
ODBC 14
D OPC servers 15
Pictures 16
database 9 recipes 20
database Dynamo conversion process 10 report generator 11

Index 37

FANUC Spares
 security 20 MHP 14
System Configuration Utility 20 migrating to iFIX
information needed to complete 1
tasks to complete on your current FIX
G installation 23
Visual Basic knowledge needed 2
global subroutines 5 with DDA Drivers 35
graphic Dynamos 17

O
H
ODBC 14
historical 12 ODBC Data Source 15
Historical Assign (HTA) 12 OPC Servers 15
historical data operating system
existing 13 recommended 3
Historical Data Access (HDA) programs 10

P
I
pen groups 13
I/O Driver and Database Migration 28 Picture Conversion Utility 33
I/O Drivers 13 using to convert pictures 33
iFIX picture functionality
installation procedure 26, 27, 28, 29 converting 16
migration process 21 picture templates 20
installing iFIX 26 pictures
converting 33
process database as a client 11
K process database as a server 11

key macro files 20

R
L recipes 20
replacing a tag in iFIX 35
lab data 13 Report Generator 11
layout files 19

S
M
security 20
memory setting up the System Configuration Utility 27
recommended minimum 3 shapes and bitmaps 17
Message Handler Package SQL queries, existing 13
see MHP subpictures 17

38 Migration Guide
Symmetrical Multiprocessor (SMP) computers
3
system configuration
minimum CPU clock speed 3
minimum physical memory 3
operating system 3
video specifications 4
System Configuration Utility 20
system performance 3

T
tag groups 19
tags
finding and replacing 35
time groups 13

U
updates
obtaining before migrating 22

V
video specifications
recommended 4
Visual Basic 2
Visual Basic for Applications 2

W
Windows 2000 3
Windows 95 3
Windows 98 3
Windows NT 3
Workspace (pictures) as a client 11

Z
Zoom To functionality 20

Index 39

FANUC Spares
40 Migration Guide