3BUR002065R3501 A en AdvaBuild Version 3.5 Migration Guide

AdvaBuild®
Migration
Version 3.5
User’s Guide
AdvaBuild®
Migration
Version 3.5
User’s Guide
NOTICE
This document contains information about one or more ABB products and may include a
description of or a reference to one or more standards that may be generally relevant to
the ABB products. The presence of any such description of a standard or reference to a
standard is not a representation that all of the ABB products referenced in this document
support all of the features of the described or referenced standard. In order to determine
the specific features supported by a particular ABB product, the reader should consult the
product specifications for the particular ABB product.
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB. ABB assumes no responsibility for any errors that
may appear in this document.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respec-
tive owners.
Copyright © 2009 by ABB

All rights reserved.
Release: December 2009

Document number: 3BUR002065R3501
TABLE OF CONTENTS
About This Book

General ..............................................................................................................................9
Use of Warning, Caution, Information, and Tip ................................................................9
Document Conventions ...................................................................................................10
Terminology.....................................................................................................................11
Related Documentation ...................................................................................................12
Section 1 - Introduction
Prerequisites and Requirements ......................................................................................15
Section 2 - Migration
General ............................................................................................................................17
Migration from HP-UX to Windows...............................................................................18
Preparation Before Migration from HP-UX to Windows ....................................18
Database Migration from HP-UX to Windows....................................................19
Overview of Database Migration ........................................................19
Procedure for Migration of a Database ...............................................20
TCL File Migration from HP-UX to Windows....................................................28
Overview of TCL File Migration ........................................................28
Procedure for Migration of TCL Source Files in FMS Format ..........29
FMS User Data File Migration from HP-UX to Windows ..................................35
Overview of FMS User Data Files Migration.....................................35
Procedure for Migration of FMS User Data Files...............................35
Using File Migration Utility for Multibus to Windows...................................................43
Multibus Preparations ..........................................................................................43
DCN File Transfer Utility ....................................................................................43
3BUR002065R3501 5
Table of Contents
Migrating Files.................................................................................... 44
Create Ladder Logic File List ............................................................. 47
Transfer TLL Files .............................................................................. 48
Transfer Page Builder Graphics or Console Environments ................ 49
Check Log File and Exit ..................................................................... 50
Appendix A - Additional HP-UX to Windows Migration

Procedures
General Information ........................................................................................................ 51
Migrating Object Comments........................................................................................... 51
Migrating Annotation Text.............................................................................................. 55
Appendix B - Data Transfer From Windows to HP-UX Platform

Overview of Data Transfer from Windows to HP-UX Platform .................................... 61
Data Transfer of a Database ............................................................................................ 62
Appendix C - Revision Control Tools

Get Revision ........................................................................................................ 69
Running GetRevision.......................................................................... 69
Viewing GetRevision Output File....................................................... 70
Appendix D - Serial Data Transfers

Migration from Multibus to Windows ............................................................................ 71
Preparation Before Migration from Multibus to Windows.................................. 71
Database Migration from Multibus to Windows ................................................. 72
Overview of Database Migration........................................................ 72
Procedure for Migration of a Database............................................... 72
TCL File Migration from Multibus to Windows ................................................. 81
Overview of TCL File Migration........................................................ 81
Procedure for Migration of TCL Source Files.................................... 82
FMS User Data File Migration from Multibus to Windows................................ 94
Overview of FMS User Data Files Migration .................................... 94
Procedure for Migration of FMS User Data Files .............................. 95
6 3BUR002065R3501
Table of Contents
Environment and Graphic File Migration from Multibus to Windows..............102

Console/Page Builder File Transfer Utility.......................................102
INDEX
3BUR002065R3501 7
Table of Contents
8 3BUR002065R3501
About This Book
General
This book describes how to migrate a full or partial database, TCL files (sequence
and recipe source), and FMS user data files (Page Builder files, Console
Configurator files, TLL files, PLC configuration files, and memory pool
configuration files) from either the HP-UX or Multibus platform to the Windows
platform.
Use this section as a guide to the conventions and terminology used throughout this
book. For a list of documentation related to the product described in this book, see
Related Documentation on page 12.
Use of Warning, Caution, Information, and Tip

This publication includes Warning, Caution, and Information where appropriate
to point out safety related or other important information. It also includes Tip to
point out useful hints to the reader. The corresponding symbols should be
interpreted as follows:
Electrical warning indicates the presence of a hazard which could result in
electrical shock.
Warning indicates the presence of a hazard which could result in personal injury.
Caution indicates important information or warning related to the concept

discussed in the text. It might indicate the presence of a hazard which could result
in corruption of software or damage to equipment/property.
3BUR002065R3501 9
Document Conventions
Information alerts the reader to pertinent facts and conditions.
Tip indicates advice on, for example, how to design your project or how to use a
certain function.
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
Document Conventions
The following conventions are used for the presentation of material:
• The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
• Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
• Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
• Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
• The names of push and toggle buttons are boldfaced. For example, click OK.
• The names of menus and menu items are boldfaced. For example, the File
menu.
– The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: choose File > New >
Type.
– The Start menu name always refers to the Start menu on the Windows
Task Bar.
• System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
10 3BUR002065R3501
Terminology
value out of range, the following message is displayed:

Entered value is not valid. The value must be 0 to30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using lowercase letters.
sequence name
Terminology
The following is a list of terms associated with AdvaBuild software that you should
be familiar with. The list contains terms and abbreviations that are unique to ABB
or have a usage or definition that is different from standard industry usage.
Term Description
ATF ASCII Transition File
BTF Binary Transition File
CI Computer Interface
DCN Distributed Communication Network. E-DCN is an
Ethernet DCN.
FMS File Management Services
FTP File Transfer Protocol
MCB MOD Control Builder
RCS Revision Control System
TCB TCL Builder
TCL Taylor Control Language
TLB TLL Builder
TLL Taylor Ladder Logic
Windows Microsoft Windows operating system
3BUR002065R3501 11
Related Documentation
Table 1 identifies the documentation to consult for detailed information on a given
subject related to the AdvaBuild software.
Table 1. Related Documentation
Category Title Description

System Microsoft Windows Administrator’s Install, uninstall, administration, and
Administration Guide registry of Windows operating system.
AdvaBuild Administrator’s Guide Installation and project administration
for AdvaBuild suite of software products.
AdvaBuild Migration Guide Information regarding migration of
database configuration files from HP-UX
Engineering Station or Multibus CDP to
Windows-based Engineering Station.
AdvaBuild Release Notes Information regarding upgrades and
changes that are not described in this
book.
Installation Instructions for Real-time Details regarding installation of the RTA
Accelerator Board board.
Software AdvaBuild Control Builder User’s Guide Consult this book for instructions on how
to:
• operate the various builders
(Control and Template Builders) to
configure the MOD 300 database
• compile, install, download, and
decompile the database
• transfer data between the various
database configuration platforms
12 3BUR002065R3501
Table 1. Related Documentation (Continued)
Category Title Description

Options AdvaBuild TCL Builder User’s Guide This book describes how to generate
and manage TCL programs via the TCL
Builder.
Taylor Control Language (TCL) User’s This book provides format and syntax
Guide rules, and other reference information
for TCL. This book also provides
instructions for using the TCL Catalog
display to compile and link TCL
sequences.
AdvaBuild TLL Builder User’s Guide This book describes how to generate
and manage TLL segment files via the
TLL Builder.
Taylor Ladder Logic (TLL) User’s Guide This book provides structure
requirements and instruction information
for TLL segment files.
After you install the AdvaBuild documentation, you can access it from the
Windows task bar by choosing Start > Programs > ABB Industrial IT > Control
IT > AdvaBuild > Documentation > Document.
3BUR002065R3501 13
14 3BUR002065R3501
Section 1 Introduction
Prerequisites and Requirements

Migration of files from the Multibus or HP-UX platforms to an AdvaBuild for
Windows platform requires that the system software versions be at certain levels.
With the addition of the DCN generic file download utility, all migration can be
done over the DCN. For the general hardware and memory requirements of the
AdvaBuild software, see the AdvaBuild Administrator’s Guide. System
requirements for migrating files to the Windows platform are:
• HP-UX platform with AdvaBuild version 2.7/0 or higher software
• Multibus platform with MOD 300 version 14.4/0 or higher software if using
serial data transfers
• DCN file transfer utility on floppy disk for the Multibus platform
System Software Patch ABB-PSSU_146041 adds the ability to transfer any file
from another node on the DCN from an Operator/Engineering Station (OS/ES). The
System Software 14.6/4 release supports AdvaCommand 1.9/0 / AdvaBuild 2.9/1.
Previously, the DCN file transfer utility could only transfer graphics or
environments and not other file types. Now, the generic file download option allows
any file to be transferred.
The Control Builder does not directly support serial data transfer functions for
migrating MOD 300 database configuration files generated on an IBM PC with
PC Template Generator software to the Windows platform. You must first
download the database generated with the PC Template Generator to either the
HP-UX or Multibus platform, and then migrate the database to the Windows
platform.
3BUR002065R3501 15
Prerequisites and Requirements Section 1 Introduction
16 3BUR002065R3501
Section 2 Migration
General
The MOD 300 system supports four platforms for database configuration:
• the PC running the Windows operating system with AdvaBuild software,
• the Advant Station with AdvaBuild for HP-UX software,
• the Multibus-based configurator/data processor (CDP).
• IBM PC with PC Template Generator software,
TCL development is supported on three platforms:
• the PC running the Windows operating system with AdvaBuild TCL Builder
software,
• the Advant Station with AdvaBuild TCL Builder for HP-UX software,
• the Multibus-based CDP.
Migration of database configuration, TCL and TLL files from the Multibus platform
or the HP-UX platform to the Windows platform is accomplished using a file
transfer utility (Multibus) or FTP (HP-UX) over the DCN.
Also available, but no longer necessary, is a serial data transfer function provided by
the AdvaBuild Control Builder for migrating MOD 300 database configuration,
TCL and TLL files generated on the Multibus platform to the Windows platform via
a serial interface. See Appendix D, Serial Data Transfers.
The remainder of this chapter provides instructions that describe how to migrate a
database, TCL sequences and recipes, and FMS user data files (Page Builder files,
Console Configurator files, TLL files, PLC configuration files, and memory pool
configuration files) generated on the HP-UX or Multibus platform to the Windows
platform. A database generated with the PC Template Generator must be download
3BUR002065R3501 17
Migration from HP-UX to Windows Section 2 Migration
to either the HP-UX or Multibus platform before migrating the database to the
Windows platform.
Migration from HP-UX to Windows

This section provides procedures for:
• Preparation Before Migration from HP-UX to Windows
• Database Migration from HP-UX to Windows
• TCL File Migration from HP-UX to Windows
• FMS User Data File Migration from HP-UX to Windows
Preparation Before Migration from HP-UX to Windows

To prepare your PC for migration of a database, TCL sequences and recipes, and
FMS user data files generated on the HP-UX platform, transfer the fmsConvert
script from the client/server PC to the HP-UX platform. To do so,
1. Open a Command Prompt window from the Windows task bar by choosing
Start > Programs > Accessories > Command Prompt.
2. Change to the drive letter where AdvaBuild is installed to see the path if it is
something other than c:\ (enter d: for example).
3. At the command prompt, change directories using the command below:
cd %AdvaBuild_DataModel_HOME%\Project\migrate
4. Make the ftp connection to the Advant Station with AdvaBuild for HP-UX
software using the following command:
ftp <device name>
For example, to connect to the device named roc239, you would enter
ftp roc239
Messages are then displayed indicating whether the connection was made to
the source device and if it is ready. You are also prompted to enter a user name.
5. Log in to the device by entering the root user name and password in response
to the prompts.
18 3BUR002065R3501
Section 2 Migration Database Migration from HP-UX to Windows
6. At the ftp> prompt, change to the following directory by entering:

cd /opt/advant/MODBase/bin
7. Overwrite the fmsConvert script and put the hptont and ctunf1 scripts in the
directory using the following commands:
put fmsConvert
binary
put hptont
put ctunf1
Once transfer of the scripts is complete, a message indicating transfer is
complete is displayed.
8. After transfer of the script files is complete, at the ftp> prompt, enter:
quit
This exits you from the ftp function and returns you to the command prompt.
Database Migration from HP-UX to Windows

This section contains an overview of the database migration process and the detailed
procedures for migrating a database from HP-UX to Windows.
Overview of Database Migration

The following is a brief overview of the database migration procedure:
1. On the HP-UX platform, save the full or partial database you want to migrate
as a binary transition file.
2. On the Advant Station with AdvaBuild for HP-UX software, use fmsConvert
to convert the HP binary transition file to a Windows binary transition file.
3. Transfer the binary transition file to the Windows platform.
4. On the PC running the Windows operating system, convert the binary transition
file to an ASCII transition file using the BTFtoATF utility.
5. Create a project on the PC where the database migrated from the HP will be
stored.
6. Log in to AdvaBuild Control Builder and open the project.
3BUR002065R3501 19
Database Migration from HP-UX to Windows Section 2 Migration
7. Load the transition file.

8. Check the contents of the log file for any errors.
Procedure for Migration of a Database

To migrate a database from the HP-UX platform to the Windows platform:
1. On the Advant Station with AdvaBuild for HP-UX software, save the database
you want to migrate as a transition file. (Refer to the AdvaBuild Basic
Functions User’s Guide for details on how to start the Structure Builder, log in
to the project, and save the transition file.) To do so,
a. Start the Structure Builder and log in to the project that you want to
migrate.
b. Select the MOD_DB level object.
c. Choose Special Commands from the Object menu.
d. Select SAVE_TRANS.
This displays the Save Transition File dialog that lists the name of the
selected database object, its templet type, Transition File field, and toggle
buttons to indicate whether or not the data in an existing transition file
with the same name as the one being created is to be replaced by the data
being saved.
e. With the Transition File field selected, type the transition file’s name, up
to eight alphanumeric characters, including underscores. No other
characters (for example, period, dash, and so on) may be used in the
transition file’s name.
f. Click on the toggle button to indicate whether the transition file being
created will overwrite an existing transition file with the same name.
The choices are YES and NO. If selected (depressed), the YES button
overwrites the data in the existing transition file with the same name, and
the NO button does not overwrite the data in the existing transition file.
g. Click on Start Save.
When the save is complete, a save complete message is displayed, or if the
file could not be saved, an error message is displayed.
20 3BUR002065R3501
Click on OK to acknowledge. If necessary, take steps to correct the error.

All errors detected during the save process are recorded in a log file.
2. On the Advant Station with AdvaBuild for HP-UX software, use fmsConvert
to convert the HP binary transition file to a Windows binary transition file. To
do so,
a. Open an HP-Term window.
b. Verify that the permissions and owners for fmsConvert, hptont, and ctunf1
in /opt/advant/MODBase/bin are set as follows:
Permissions: r-xr-xr-x
Owner: ocsmgr:ocs
If necessary, use chown and chmod to set as above.
c. At the command prompt, enter:
fmsConvert $FMSPATH/WC00/50/DBASE
This converts all transition files located in the $FMSPATH/WC00/50/DBASE
directory. The converted files will be located in
/tmp/fmsconvert/WC00/50/DBASE.
The following is an example of the messages displayed in the HP-Term
window during the fmsConvert process.
3BUR002065R3501 21
<eng55:ocsmgr> fmsConvert $FMSPATH/WC00/50/DBASE

devString = WC00/50/DBASE
workDir = /tmp/fmsconvert/WC00/50/DBASE
Copying files from /home/opt/advant/FMS/WC00/50/DBASE to /tmp/fmsconvert/WC00/50/DBASE...
Running hptont on files in /tmp/fmsconvert/WC00/50/DBASE...
Copying back original ctree index files...

cp: cannot access /home/opt/advant/FMS/WC00/50/DBASE/*.idx: No such file or directory
cp: cannot access /home/opt/advant/FMS/WC00/50/DBASE/*.con: No such file or directory
Running ctree conversion on files in /tmp/fmsconvert/WC00/50/DBASE...
Conversion of files from /home/opt/advant/FMS/WC00/50/DBASE completed.
Converted files will be found in /tmp/fmsconvert/WC00/50/DBASE.
During the conversion process, you may receive the following messages that you
can ignore:
cp: cannot access /home/opt/advant/FMS/WC00/50/DBASE/*.idx
No such file or directory.
cp: cannot access /home/opt/advant/FMS/WC00/50/DBASE/*.con
No such file or directory.
Similar messages may appear for all the different conversion processes involved
in migrating data from the HP-UX platform to the Windows-based Engineering
Station.
22 3BUR002065R3501
3. On the PC running the Windows operating system, get the resulting binary
transition file via ftp. To do so,
a. Open a Command Prompt window from the Windows task bar by
choosing Start > Programs > Accessories > Command Prompt.
b. Change to the drive letter where System Services is installed to see the
path if it is something other than c:\ (enter d: for example).
c. At the command prompt, change directories using the command below:
cd %FMSPATH%\WC00\50\
d. If the DBASE directory is not present, create it using the command below:
mkdir DBASE
e. Change to the DBASE directory using the command below:
cd DBASE
f. Make the ftp connection to the source device where the transition file
resides using the following command:
ftp <device name>
ftp roc239
Messages are then displayed indicating whether the connection was made
to the source device and if it is ready. You are also prompted to enter a
user name.
g. Log in to the device by entering the operator user name and password in
response to the prompts.
h. At the ftp> prompt, enter:
prompt
i. At the ftp> prompt, enter:
binary
The ftp transfer mode must be set to binary as indicated above. Failure to do so
will result in corrupt FMS files on the target Windows-based Engineering Station
after transfer.
3BUR002065R3501 23
j. Change to the directory where the converted transition file resides using
the command below:
cd /tmp/fmsconvert/WC00/50/DBASE
k. Use the mget command to retrieve the transition file(s) from the HP in the
following format:
mget <transition file name>.DT.*
l. After transfer of the desired .dat and .nky files is complete, at the ftp>
prompt, enter:
quit
This exits you from the ftp function and returns you to the command
prompt.
4. Convert the binary transition file (BTF) to an ASCII transition file (ATF) using
the BTFtoATF utility. To do so,
a. At the command prompt, change directories using the command below:
cd %AdvaBuild_Bin%
b. Initiate the BTF to ATF conversion by entering:
btftoatf WC00:[50.DBASE]<transtion file name>.DT
..\<transition file name>.txt
Enter the transition file name in all uppercase characters.

The ATF file is saved in Program Files\ABB Industrial IT\AdvaBuild.
The binary transition file is converted to an ASCII transition file that
resides on the PC client. You can edit the resulting ASCII transition file
before you load it into a project database on the Windows-based
Engineering Station.
The following is an example of the messages displayed in the Command
Prompt window during the BTF to ATF conversion process.
C:\>btftoatf WC00:[50.DBASE]TURBO.DT.1 TURBO.txt

Converting WC00:[50.DBASE]TURBO.DT...
INTISAM: error 5 creating mutex.
12 Templets Converted
24 3BUR002065R3501
The following error may be displayed during the conversion and can be ignored:
c. Close the Command Prompt window by entering exit at the command

prompt and proceed to Step 5.
5. Create a project on the Windows-based Engineering Station where the database
migrated from the HP will be stored.
a. Start the AdvaBuild Administration component and login as the Admin
user. Refer to the AdvaBuild Administrator’s Guide for details.
b. Choose Projects > Insert Project… from the menu bar or click on the
Insert Project icon (file folder) in the tool bar. This opens the Insert Project
dialog, Figure 1.
Figure 1. Insert Project Dialog
c. Enter the project name, project number, and project size as it was defined
on the HP platform.
d. Click Insert Project to create the project.
This opens the Insert Project Status dialog indicating the insertion process
is running and you should wait. When the insertion process is finished, the
Insert Project Status dialog closes and the Insert Project Completion
dialog opens. The Insert Project Completion dialog indicates whether the
insertion process was successful.
3BUR002065R3501 25
e. Click OK to close the Insert Project Completion dialog.

6. Log in to the Control Builder and open the project under which you want to add
the transferred data. Refer to the AdvaBuild Control Builder User’s Guide for
details.
7. Load the ASCII transition file using the Load ATF functionality of the
AdvaBuild Control Builder. See the AdvaBuild Control Builder User’s Guide
for more detailed information about the Load ATF functions.
To load the ASCII transition file,
a. Choose Tools > Load ATF from the menu bar. This opens the Load
ASCII Transition File dialog, Figure 2.
Figure 2. Load ASCII Transition File Dialog
b. Click on the Browse button to the right of the field to open the Open
Transition File dialog, Figure 3. Then, open the ASCII transition file you
want to load by either double-clicking on its name or selecting its name
and clicking on the Open button in the Open Transition File dialog. The
file is actually located in:
c:\Program Files\ ABB Industrial IT\AdvaBuild
26 3BUR002065R3501
Figure 3. Open Transition File Dialog
The selected ASCII transition file’s name now appears in the Transition
File field of the Load ASCII Transition File dialog. The name for the load
transition report file (log) generated by the load process also appears in the
Log File field. Note the log file name.
c. Click on the Load button to start loading the transition file.
Once you click on the Load button, the load process is started and the
Load ATF progress dialog is opened. Upon completion of the load, the
load status will change to “Completed” if no errors were detected or
“Completed with Errors” if errors are detected.
8. Once loading of the transition file is complete, check the contents of the log file
for any errors.
Each database object that exists within a project can have comments and annotation
text associated with it. When migrating project data from an Advant Station with
AdvaBuild for HP-UX software to a PC running the Windows operating system
with AdvaBuild software via transition files as described above, the comment and
annotation information is not included in the process. See Appendix A, Additional
HP-UX to Windows Migration Procedures for information about migrating database
comments and annotation text associated with a project.
3BUR002065R3501 27
TCL File Migration from HP-UX to Windows Section 2 Migration
TCL File Migration from HP-UX to Windows

TCL file migration refers to the transfer of TCL sequence and recipe source files
from the HP-UX platform to the Windows platform. This section contains an
overview of the TCL file migration process and the detailed procedures for
migrating TCL files from HP-UX to Windows.
Overview of TCL File Migration

The following is a brief overview of TCL sequence and recipe source file migration
in FMS format:
1. On the HP-UX system where the TCL sequences and recipes reside, download
all TCL sequences (.tcl) and recipes (.rcp) to FMS.
2. On the HP-UX system where the TCL recipes reside, decompile direct recipes
to source.
3. On the HP-UX system where the TCL sequences and recipes reside, use the
fmsConvert utility to convert the TCL sequence and recipe files in HP-UX
FMS format to the Windows FMS format.
4. Use ftp to transfer the converted TCL sequence and recipe files in the Windows
FMS format to the Windows TCL Builder Server.
5. On the PC running the Windows operating system, use the SetNotCompiled
executable to set the status for transferred FMS sequence and recipe files to
“Not Compiled.”
6. On the Windows TCL Builder Server, use the TCL Migration utility to extract
the transferred TCL sequence and recipe files in Windows FMS format as text
files. TCL sequence files will have the .tcl extension, and TCL recipe files will
have the .rcp extension.
7. From the Command Prompt on the Windows system, execute AddRCSInfo to
add $Header$ type information to the source files so when they are
downloaded to FMS via a check-in and Set Active Revision, there will be
keywords in the files that can be used to verify the Revision Control System
(RCS) version number. The executable, GetRevision reads the FMS files
8. Use the TCL Builder to check in the extracted sequence (.tcl) and recipe (.rcp)
text files to the RCS of the Windows TCL Builder Server. The text files placed
28 3BUR002065R3501
Section 2 Migration TCL File Migration from HP-UX to Windows
under revision control may be moved to on-line storage using the TCL Builder
Set Active Revision, Compile, and Link commands.
Procedure for Migration of TCL Source Files in FMS Format

To migrate TCL source files in FMS format from the HP-UX platform to the
Windows platform:
1. On the HP-UX system where the TCL sequences and recipes reside, download
all TCL sequences (.tcl) and recipes (.rcp) to FMS. See the AdvaBuild TCL
Builder User’s Guide for instructions on how to download files to FMS.
2. On the HP-UX system where the TCL sequences and recipes reside, decompile
direct recipes to source. See the Taylor Control Language (TCL) User’s Guide
for instructions on how to decompile a recipe to source.
If the recipes are not decompiled back into source, errors similar to the following
are reported during migration:
Server: ITEM10
Error file not found:
WC00:[210.RECIPESR]ITEM10.SR
The above error indicates that the direct recipe for ITEM10 exists, but was not
decompiled back into source.
3. On the HP-UX system where the TCL sequences and recipes reside, use
fmsConvert to convert the TCL sequence and recipe files in HP-UX FMS
format to the Windows FMS format. To do so,
a. Open an HP-Term window.
b. Convert all TCL sequences by entering the following at the command
prompt:
fmsConvert $FMSPATH/WC00/210/TCL
The converted files will be located in /tmp/fmsconvert/WC00/210/TCL.
c. Convert all TCL recipes by entering the following at the command
prompt:
fmsConvert $FMSPATH/WC00/210/RECIPE
fmsConvert $FMSPATH/WC00/210/RECIPESR
3BUR002065R3501 29
The converted files will be located in

/tmp/fmsconvert/WC00/210/RECIPE and
/tmp/fmsconvert/WC00/210/RECIPESR.
4. On the Windows TCL Builder Server, when you transfer the FMS files to the
Windows TCL Builder Server via ftp, they are placed in the following
directories (assuming System Services is installed on the C drive):
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\210\RECIPE
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\210\RECIPESR
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\210\TCL
If these directories do not exist use the mkdir command in the Command
Prompt window or use File > New > Folder from the Windows Explorer menu
bar.
5. On the Windows TCL Builder Server, get the resulting converted files via ftp.
To do so,
a. If necessary, open a Command Prompt window from the Windows task
bar by choosing Start > Programs > Accessories > Command Prompt.
b. Change to the drive letter where System Services is installed to see the
path if it is something other than c:\ (enter d: for example).
cd %FMSPATH%\WC00
d. Make the ftp connection to the HP-UX source device where the converted
files reside using the following command:
ftp <device name>
ftp roc239
to the source device and if it is ready. You are also prompted to enter your
user name.
e. Log in to the device by entering the operator user name and password in
30 3BUR002065R3501
f. At the ftp> prompt, enter:

prompt
g. At the ftp> prompt, enter:
binary
h. Change to the directory where the converted transition file resides using
the command below:
cd /tmp/fmsconvert/WC00
i. Use the lcd command to change to the Windows subdirectory where you
want to place the converted TCL sequence files and use the mget
command to retrieve the corresponding converted files from the HP-UX
platform by entering the following at the command prompt:
lcd 210\TCL
mget 210/TCL/*.SR.*
mget 210/TCL/*.D*.*
Once transfer of the TCL sequence file(s) is complete, a message
indicating transfer is complete is displayed.
j. Use the lcd command to change to the Windows subdirectory where you
want to place the converted TCL recipe files and use the mget command
to retrieve the corresponding converted files from the HP-UX platform by
entering the following at the command prompt:
lcd ..\RECIPE
mget 210/RECIPE/*.RR.*
mget 210/RECIPE/*.D*.*
Once transfer of the recipe file(s) is complete, a message indicating
transfer is complete is displayed.
k. Use the lcd command to change to the Windows subdirectory where you
want to place the converted TCL recipe files and use the mget command
lcd ..\RECIPESR
mget 210/RECIPESR/*.SR.*
3BUR002065R3501 31
Once transfer of the recipe file(s) is complete, a message indicating

transfer is complete is displayed.
l. At the ftp> prompt, enter:
quit
prompt.
m. At the command prompt, enter:
exit
This closes Command Prompt window.
6. On the PC running the Windows operating system, use the SetNotCompiled
executable to set the status for transferred FMS sequence and recipe files to
“Not Compiled.” To do so,
a. Open Windows Explorer and go to the folder
C:\Program Files\ABB Industrial IT\AdvaBuild\bin
b. Start the SetNotCompiled executable by double clicking on the
SetNotCompiled icon.
A Command Prompt window opens and runs for a few seconds before closing.
7. On the PC running the Windows operating system, use the TCL Migration
Utility to extract the transferred FMS files to the text file format and move the
text files into the appropriate directories. To do so,
b. Start the TCL Migration Utility by double clicking on the TCLMigration
icon.
This opens the TCL Migration dialog, Figure 4.
c. In the Server Name field, enter the name of the Windows server to which
the FMS files were transferred in Step 5.
d. Enter your CONFIG user name and password in the corresponding User
Id and Password fields.
32 3BUR002065R3501
Figure 4. TCL Migration Dialog
e. Select the desired drive and folder where you want to store the .tcl and .rcp
text files. By default, the drive and folder for the TCL Builder is located at
c:\Documents and Settings\<username>\My Documents\My TCL.
f. Click on the Migrate Data button.
This moves the migrated .tcl and .rcp text files to the specified drive and
folder on the server you are currently logged into.
(RCS) version number.
3BUR002065R3501 33
Enter the following at the command prompt to convert all .tcl sequence and
.rcp recipe files. ADDRCSInfo is located in the path represented by the
variable AdvaBuild_Bin.
cd %AdvaBuild_Bin%
AddRCSInfo seq <input file path> <<output file path>>
AddRCSInfo rec <input file path> <<output file path>>
where
<input file path> = All input files at this location will be converted.
Default path is: c:\Documents and Settings\<username>\My
Documents\My TCL.
<<output file path>> = Location of output files and .log files (seq.log and
rec.log). Not required. If not specified, files are located in: c:\Documents
and Settings\<username>\My Documents\My TCL\AddRCSInfo.
text files to the Revision Control System (RCS) of the Windows TCL Builder
Server. The text files placed under revision control may be moved to on-line
storage using the TCL Builder Set Active Revision, Compile, and Link
commands. See the AdvaBuild TCL Builder User’s Guide for information
about checking in files to the RCS, compiling, linking, and so on. A
GetRevision executable is used to get RCS information from FMS files and
output the results to a file where you can verify what versions of files are
actually executing at runtime. See Appendix C, Revision Control Tools.
34 3BUR002065R3501
Section 2 Migration FMS User Data File Migration from HP-UX to Windows
FMS User Data File Migration from HP-UX to Windows

FMS user data file migration refers to the transfer of Page Builder files, Console
Configurator files, TLL files, PLC configuration files, and memory pool
configuration files from the HP-UX platform to the Windows platform. This section
contains an overview of the FMS user data file migration process and the detailed
procedures for migrating FMS user data files from HP-UX to Windows.
Overview of FMS User Data Files Migration

The following is a brief overview of the FMS user data file migration procedure,
1. Convert the Page Builder, Console Configurator, TLL files, PLC
configuration, and memory pool configuration files from HP-UX FMS format
to Windows FMS format.
2. Transfer the converted FMS files to the Windows platform.
Procedure for Migration of FMS User Data Files

To migrate FMS user data files from the HP-UX platform to the Windows platform:
1. On the HP-UX platform where the FMS files reside, open an HP Term window
and log in as either operator.
2. Convert all Page Builder files by entering the following at the command
prompt:
fmsConvert $FMSPATH/WC00/170/PAGEDATA
fmsConvert $FMSPATH/WC00/170/UDPSDATA
fmsConvert $FMSPATH/WC00/170/LIBDATA
The converted files will be located in
/tmp/fmsconvert/WC00/170/PAGEDATA,
/tmp/fmsconvert/WC00/170/UDPSDATA, and
/tmp/fmsconvert/WC00/170/LIBDATA directories.
3. Determine all the ENV# directories that exist in the FMSPATH/WC00/170
directory. To do so,
a. At the command prompt, enter:
ls $FMSPATH/WC00/170
3BUR002065R3501 35
FMS User Data File Migration from HP-UX to Windows Section 2 Migration
b. Note the names of all ENV# directories displayed (for example, ENV1
and ENV3).
4. Convert all files of the ENV# directories noted in Step b of Step 3 by entering
the following for each directory at the command prompt:
fmsConvert $FMSPATH/WC00/170/ENV#
where # is the number of the ENV directory. For example, for the directories
listed in the example in Step b of Step 3, you would enter:
fmsConvert $FMSPATH/WC00/170/ENV1
fmsConvert $FMSPATH/WC00/170/ENV3
The converted files will be located in the corresponding
/tmp/fmsconvert/WC00/170/ENV# directory.
5. Convert all the Console Configurator files by entering the following at the
command prompt:
fmsConvert $FMSPATH/WC00/170/CONFIG
The converted files will be located in the
/tmp/fmsconvert/WC00/170/CONFIG directory.
6. Determine all the Ladder Logic directories that exist in the
$FMSPATH/WC00/20556 directory. To do so,
a. At the command prompt, enter:
ls $FMSPATH/WC00/20556
b. Note the names of all Ladder Logic directories displayed (for example,
AC1_LL and AC3_1_LL).
7. Convert all files of the Ladder Logic directories noted in Step b of Step 6 by
entering the following for each directory at the command prompt:
fmsConvert $FMSPATH/WC00/20556/<ladder logic
directory>
where <ladder logic directory> is the Ladder Logic directories determined in
Step b of Step 6.
For example, for the directories listed in the example in Step b of Step 6, you
would enter:
36 3BUR002065R3501
fmsConvert $FMSPATH/WC00/20556/AC1_LL
fmsConvert $FMSPATH/WC00/20556/AC3_1_LL
The converted files will be located in the corresponding
/tmp/fmsconvert/WC00/20556/<ladder logic directory> directory.
8. Convert the Ladder Logic library files by entering the following at the
command prompt:
fmsConvert $FMSPATH/WC00/1/PLC
The converted files will be located in the /tmp/fmsconvert/WC00/1/PLC
directory.
9. Convert all PLC Configuration files by entering the following at the command
prompt:
fmsConvert $FMSPATH/WC00/260/CONFIG
The converted files will be located in the
/tmp/fmsconvert/WC00/260/CONFIG directory.
10. Convert all memory pool configuration files by entering the following at the
command prompt:
fmsConvert $FMSPATH/WC00/50/DPOOLS
fmsConvert $FMSPATH/WC00/50/GPOOLS
fmsConvert $FMSPATH/WC00/50/TPOOLS
The converted files will be located in /tmp/fmsconvert/WC00/50/DPOOLS,
/tmp/fmsconvert/WC00/50/GPOOLS, and
/tmp/fmsconvert/WC00/50/TPOOLS directories.
11. In an HP Term window, remove default files by entering the following:
rm /tmp/fmsconvert/WC00/50/DPOOLS/POOLS.PL.*
rm /tmp/fmsconvert/WC00/50/GPOOLS/POOLS.PL.*
rm /tmp/fmsconvert/WC00/50/TPOOLS/POOLS.PL.*
12. On the PC running the Windows operating system, create target directories for
the FMS user data files you want to migrate. To do so,
3BUR002065R3501 37
b. At the command prompt, change directories using the command below:

cd %FMSPATH%\WC00
c. Create Page Builder and ENV# directories for each such directory by
mkdir 170\CONFIG
mkdir 170\PAGEDATA
mkdir 170\UDPSDATA
mkdir 170\LIBDATA
mkdir 170\ENV#
where # is the number of the catalog. For example, for the directories
listed in the example in Step b of Step 3, you would enter:
mkdir 170\ENV1
mkdir 170\ENV3
d. Create Ladder Logic directories for each such directory whose files were
converted in Step 7 by entering the following at the command prompt:
mkdir 20556\<ladder logic directory>
where <ladder logic directory> is the Ladder Logic directories determined
in Step b of Step 6.
For example, for the directories listed in the example in Step b of Step 6,
you would enter:
mkdir 20556\AC1_LL
mkdir 20556\AC3_1_LL
e. Create the Console Configurator directory for the directory whose files
were converted in Step 5 by entering the following at the command
prompt:
mkdir 260\CONFIG
13. Make the ftp connection to the HP-UX source device where the converted files
reside using the following command:
ftp <device name>
38 3BUR002065R3501
ftp roc239
Messages are then displayed indicating whether the connection was made to
the source device and if it is ready. You are also prompted to enter your user
name.
14. Log in to the device by entering the operator user name and password in
15. At the ftp> prompt, enter:
prompt
16. At the ftp> prompt, enter:
binary
17. Change to the directory where the converted files reside using the command
below:
cd /tmp/fmsconvert/WC00
18. Use the lcd command to change to the Windows subdirectory where you want
to place the converted Page Builder files and use the mget command to retrieve
the corresponding converted files from the HP-UX platform by entering the
following at the command prompt:
lcd 170\PAGEDATA
mget 170/PAGEDATA/*
lcd ..\UDPSDATA
mget 170/UDPSDATA/*
lcd ..\LIBDATA
mget 170/LIBDATA/*
to place the converted Console Configurator files and use the mget command
lcd ..\CONFIG
mget 170/CONFIG/*
3BUR002065R3501 39
to place the converted ENV# files and use the mget command to retrieve the
converted files from each of the corresponding directories on the HP-UX
lcd ..\ENV#
mget 170/ENV#/*
where # is the number of the catalog. For example, for the directories listed in
the example in Step b of Step 3, you would enter:
lcd ..\ENV1
mget 170/ENV1/*
lcd ..\ENV3
mget 170/ENV3/*
to place the converted Ladder Logic files and use the mget command to
retrieve the corresponding converted files from the HP-UX platform by
lcd ..\..\20556\<ladder logic directory>
mget 20556/<ladder logic directory>/*
where <ladder logic directory> is the Ladder Logic directories determined in
Step b of Step 6.
For example, for the directories listed in the example in Step b of Step 6, you
would enter:
lcd ..\..\20556\AC1_LL
mget 20556/AC1_LL/*
lcd ..\AC3_1_LL
mget 20556/AC3_1_LL/*
to place the converted Ladder Logic library files and use the mget command to
lcd ..\..\1\PLC
mget 1/PLC/*
40 3BUR002065R3501
to place the converted PLC configuration files and use the mget command to
lcd ..\..\260\CONFIG
mget 260/CONFIG/*
to place the converted memory pool configuration files and use the mget
command to retrieve the corresponding converted files from the HP-UX
lcd ..\..\50\DPOOLS
mget 50/DPOOLS/*
lcd ..\GPOOLS
mget 50/GPOOLS/*
lcd ..\TPOOLS
mget 50/TPOOLS/*
25. After transfer of the all the FMS user data files converted in Step 2 through
Step 10 is complete, at the ftp> prompt, enter:
quit
This exits you from the ftp function and returns you to the command prompt.
26. For each Controller or Generic DPSS device from which ladder logic program
files were transferred, convert the transferred files from FMS to text file format
by entering the following commands at the command prompt:
cd %AdvaBuild_Bin%
and then
TLLTranslateFMS.exe <tlldevice name>
where:
<tlldevice name> is the templet name of the TLL device in the Controller or
Generic DPSS device where TLL is configured to run.
3BUR002065R3501 41
All .SR files transferred from that device are converted to text files with the .tll
extension and are placed in that device’s default directory:
C:\Documents and Settings\advabuild\My Documents\My TLL\<device
name>
These files may be placed under revision control using the TLL Builder.
Enter the following at the command prompt to convert all .tll segment files.
ADDRCSInfo is located in the path represented by the variable
AdvaBuild_Bin.
cd %AdvaBuild_Bin%
AddRCSInfo seg <device name> <input file path> <<output
file path>>
where
<device name> is the templet name of the Controller or Generic DPSS
device where TLL is configured to run.
<<output file path>> = Location of output files and
seg_<device name>.log file. Not required. If not specified, files are
located in: c:\Documents and Settings\<username>\Local
Settings\Temp\AddRCSInfo.
28. Use the TLL Builder to check in the text files (.tll) to the Revision Control
System (RCS) of the Windows TLL Builder Server. The text files placed under
revision control may be moved to on-line storage using the TLL Builder Set
Active Revision and Compile commands. See the AdvaBuild TLL Builder
User’s Guide for information about checking in files to the RCS, compiling,
and so on. A GetRevision executable is used to get RCS information from FMS
files and output the results to a file where you can verify what versions of files
are actually executing at runtime. See Appendix C, Revision Control Tools.
42 3BUR002065R3501
Section 2 Migration Using File Migration Utility for Multibus to Windows
29. Migration of the FMS user data files is complete and you can close the
Command Prompt window. To do so, at the command prompt, enter:
exit
30. Reboot your Windows-based Engineering Station.
Using File Migration Utility for Multibus to Windows

All Multibus file migration to the Windows platform can be done using the latest
DCN file migration utility (see Prerequisites and Requirements on page 15).
Multibus Preparations
Prepare the Multibus CDP as follows to make it available as a non CDP node on the
DCN,
1. Connect the Multibus Turbo Node and Windows-based Engineering Station via
a DCN connection.
2. Remove or rename the file [0.BOOT]BOOT.PK on the Multibus Turbo Node
and reboot the Turbo Node with an address that is not 0100 and is also not the
normal Multibus address. This is done so the Multibus Turbo Node will boot
off the Windows-based Engineering Station.
3. Insert the floppy disk with the DCN file migration utility.
4. From a BUGs terminal on the Multibus Turbo Node, entering the following at
the What’s up Doc?> prompt:
ID L751 FD00:[170.CONVERT]FTDLD.DP
the response is:
L751 T65535 FD00:TEST[170.CONVERT]FTDLD.DP
DCN File Transfer Utility

This utility allows you to copy files from a given Multibus CDP to a Windows-based
Engineering Station on the same DCN. Note that the Windows-based Engineering
Station must have a DCN address which is not used elsewhere in the system (for
example, 0x1100, 0x2100, … 0xF100).
3BUR002065R3501 43
DCN File Transfer Utility Section 2 Migration
This utility is intended for the one time transfer of existing data. When you
download files, the data on the Multibus CDP will be stored on the Windows-based
Engineering Station. If you have existing Multibus files on your Windows-based
Engineering Station, they will be deleted when you download these files from the
Multibus CDP. The transfer of files from multiple Multibus CDPs requires that the
files be transferred out of the destination catalog before each transfer. Alternately, if
multiple CDPs are involved, you could consolidate data on one CDP before doing
the download.
It is recommended that you do not use this utility while using the system for
production.
Migrating Files
Run the file transfer utility from the AdvaBuild for Windows pc as follows to
migrate all but the TCL files from the Multibus node. See the generic example in
step 7 for the types of files transferred.
1. Select Start > Programs > ABB Industrial IT > System Service > Bugs to
open up a bugs window on the Windows-based Engineering Station.
2. Press <ESC> to get the bugs prompt.
3. To start the utility, do the following:
What's up Doc?> DP L749
What's up Doc?> EX
Once the utility is started, a menu is shown.
MOD300 TO ADVANT STATION FILE DOWNLOADER
P: DOWNLOAD PAGEBUILDER GRAPHICS
C: DOWNLOAD CONSOLE ENVIRONMENTS
F: GENERIC FILE DOWNLOAD
Q: QUIT
ENTER SELECTION: F
4. Press F to download generic files.
ENTER NODE NUMBER FOR SOURCE FILES IE: 0X0100? 0X0400
44 3BUR002065R3501
Section 2 Migration DCN File Transfer Utility
5. Enter the hexadecimal number for the source CDP where the files are located
(for example, 0X0400), and then press <Return>.
DOWLOADED FILE(S) WILL REPLACE EXISTING FILE(S),
OK? (Y OR N)Y
6. Enter Y and confirm.
ARE YOU SURE?? (Y OR N)Y
7. Enter the file path and the transfer completes as shown in the following generic
example.
Enter file path: ? @WC00:[50.MIGRATE]MIGRATE.CM
Started File Transfer: 10:48:43.733
TRANSFERRING RECORD x OF 43 FOR WC00:[50.DBASE]T1-AVG1.DT

TRANSFERRING RECORD x OF 43 FOR WC00:[50.DBASE]D1.DTand
TRANSFERRING RECORD x OF 67 FOR WC00:[260.CONFIG]INDEX.DT
TRANSFERRING RECORD x OF 60 FOR WC00:[260.CONFIG]LCNODE00.LI
TRANSFERRING RECORD x OF 33 FOR WC00:[210.RECIPE]RECIPE.DR
TRANSFERRING RECORD x OF 33 FOR WC00:[210.RECIPE]RECIPE.D2
TRANSFERRING RECORD x OF 12 FOR WC00:[210.RECIPE]REC1M.RR
TRANSFERRING RECORD x OF 90 FOR WC00:[210.RECIPESR]REC1M.LS
TRANSFERRING RECORD x OF 90 FOR WC00:[210.RECIPESR]REC1M.SR
TRANSFERRING RECORD x OF 90 FOR WC00:[210.RECIPESR]REC2M.LS
TRANSFERRING RECORD x OF 90 FOR WC00:[210.RECIPESR]REC2M.SR
TRANSFERRING RECORD x OF 883 FOR WC00:[210.TCL]SEQ_DIR.DR
TRANSFERRING RECORD x OF 883 FOR WC00:[210.TCL]SEQ_DIR.D2
TRANSFERRING RECORD x OF 40 FOR WC00:[210.TCL]SEQ1.LS
TRANSFERRING RECORD x OF 40 FOR WC00:[210.TCL]SEQ1.SR
TRANSFERRING RECORD x OF 50 FOR WC00:[50.TPOOLS]POOLS.PL
TRANSFERRING RECORD x OF 50 FOR WC00:[50.DPOOLS]POOLS.PL
TRANSFERRING RECORD x OF 50 FOR WC00:[50.GPOOLS]POOLS.PL
TRANSFERRING RECORD x OF 20 FOR WC00:[1.PLC]LIB_DIR.DR
TRANSFERRING RECORD x OF 20 FOR WC00:[1.PLC]LIB_DIR.D2
Records Transferred (Approx): 2812
DOWNLOAD COMPLETED WITH NO ERRORS

TERMINATED WITH STATUS = 0
3BUR002065R3501 45
PRESS ANY KEY TO CONTINUE
There could be errors in the transfer. The program will make reference to the log
file if errors are detected.
46 3BUR002065R3501
Create Ladder Logic File List

Run the make TLL list utility from the AdvaBuild for Windows pc as follows to
create a list of TLL files.
8. At the bugs prompt on the Windows-based Engineering Station, enter the
following sequence of commands:
What's up Doc?> ID L700 WC00:[50.MIGRATE]MKTLLLST.DP
L700 T65535 WC00:TEST[00050.MIGRATE ]MKTLLLST.DP
What's up Doc?> EX
Creating WC00:[50.MIGRATE]TLL_LIST.CM
Insert Record: WC00:[20556.AC1-LL ]*.*
Insert Record: WC00:[20556.AC3_1-LL]*.*
Insert Record: WC00:[20556.AC5_1_LL]*.*
Insert Record: WC00:[20556.AC6_2_LL]*.*
Insert Record: WC00:[20556.AC9_1_TL]*.*
Insert Record: WC00:[20556.PB1_1_LL]*.*
Insert Record: WC00:[20556.SC16_1_L]*.*
Insert Record: WC00:[20556.SC5_1-LL]*.*
Insert Record: WC00:[20556.SC7_1_LL]*.*
Insert Record: WC00:[20556.TURBO1-L]*.*
Creation of [50.MIGRATE]TLL_LIST.CM completed
successfully
3BUR002065R3501 47
Transfer TLL Files

Run the TLL record transfer utility from the AdvaBuild for Windows pc as follows.
9. At the bugs prompt on the Windows-based Engineering Station, enter the
following sequence of commands:
What's up Doc?> EX
Once the utility is started, a menu is shown.
Q: QUIT
ENTER SELECTION: F
10. Press F to download generic files.
DOWLOADED FILE(S) WILL REPLACE EXISTING FILE(S), OK? (Y
OR N)Y
12. Enter Y and confirm.
ARE YOU SURE?? (Y OR N)Y
13. Enter the file path and the transfer completes as shown in the following generic
example:
Enter file path: ? @WC00:[50.MIGRATE]TLL_LIST.CM
Started File Transfer: 10:48:43.733
TRANSFERRING RECORD x OF 43 FOR WC00:[20556.AC1-LL ]1.ID

TRANSFERRING RECORD x OF 23 FOR WC00:[20556.AC1-LL ]1.PC
TRANSFERRING RECORD x OF 45 FOR WC00:[20556.AC1-LL ]1.SR
TRANSFERRING RECORD x OF 22 FOR WC00:[20556.AC1-LL ]1.UP
TRANSFERRING RECORD x OF 40 FOR WC00:[20556.AC1-LL ]2.ID
TRANSFERRING RECORD x OF 36 FOR WC00:[20556.AC1-LL ]2.PC
48 3BUR002065R3501
TRANSFERRING RECORD x OF 39 FOR WC00:[20556.AC1-LL ]2.SR

TRANSFERRING RECORD x OF 20 FOR WC00:[20556.AC1-LL ]2.UP
...
Records Transferred (Approx): 286
DOWNLOAD COMPLETED WITH NO ERRORS

TERMINATED WITH STATUS = 0
PRESS ANY KEY TO CONTINUE
14. Press any key to get the utility menu.

Q: QUIT
ENTER SELECTION:
Transfer Page Builder Graphics or Console Environments

Run the TLL record transfer utility from the AdvaBuild for Windows pc as follows.
15. Press either P to download Page Builder graphic files or C to download
console environment files.
If you are downloading Page Builder graphics, you are prompted as follows:
ALL EXISTING GRAPHICS WILL BE DELETED, OK? (Y OR N)
ENTER Y OR N
If you are downloading Console environment files, you are prompted as
follows:
ALL EXISTING CONSOLE ENVIRONMENTS WILL BE DELETED, OK?
(Y OR N)
3BUR002065R3501 49
ENTER Y OR N
17. Press Y to delete all existing files.
To confirm deletion of all existing files, you are prompted to enter Y or N
again.
18. Press Y to confirm deletion of all existing files.
The utility then proceeds to delete all existing files of the selected type before
starting the file transfer.
Once the transfer is started, a message indicating the progress of the transfer is
displayed.
Once the transfer is complete, a message indicating if any errors were
encountered is displayed and you are prompted to press any key to continue.
19. Press any key to continue.
This returns you to the main menu. At this point, you can either perform
another transfer or quit.
Check Log File and Exit

If errors were encountered during the transfer, you should look at the log file to
find out what the errors were. To look at the log file, enter:
VI [170.CONVERT]PBCODNLD.LG ;”
and press <Return>.
To return to the bugs prompt from the log file, press the period (.) key.
To exit bugs, enter EX
and press <Return>.
50 3BUR002065R3501
Appendix A Additional HP-UX to Windows
Migration Procedures
General Information
Each database object that exists within a project can have comments and annotation
text associated with it. When migrating project data from an Advant Station with
AdvaBuild for HP-UX software to a PC running the Windows operating system
with AdvaBuild software via transition files as described in Database Migration
from HP-UX to Windows on page 19, the comment and annotation information is
not included in the process. See the procedures that follow for information about
migrating database comments and annotation text associated with a project.
Migrating Object Comments

You must perform the following to migrate the comments from the HP-UX platform
to the Windows platform:
1. Transfer the script file (get_comments_on_hp.sql) that retrieves the comment
data to the Advant Station with AdvaBuild for HP-UX software. To do so from
the PC running the Windows operating system where the migrated database
resides,
b. Change to the drive letter where AdvaBuild is installed to see the path if it
is something other than c:\ (enter d: for example).
3BUR002065R3501 51
Migrating Object Comments Appendix A Additional HP-UX to Windows Migration Procedures
d. Make the ftp connection to the Advant Station with AdvaBuild for HP-UX
ftp <device name>
ftp roc239
to the source device and if it is ready. You are also prompted to enter a user
name.
f. At the ftp> prompt, change to the /tmp directory by entering:
cd /tmp
g. Put the script file that retrieves the comments in the \tmp directory using
the following command:
put get_comments_on_hp.sql
Once transfer of the script file is complete, a message indicating transfer is
h. After transfer of the script file is complete, at the ftp> prompt, enter:
quit
prompt.
Once the script file to retrieve comment data is transferred to the Advant
Station with AdvaBuild for HP-UX software where the database was migrated
from, it can be run against the project containing the comments to be migrated.
2. Run the script file to retrieve the comment data. To do so from the PC running
the Windows operating System where the migrated database resides,
a. At the command prompt, open a Telnet window to the Advant Station with
AdvaBuild for HP-UX software where the script file resides using the
following command:
telnet <device name>
52 3BUR002065R3501
Appendix A Additional HP-UX to Windows Migration Procedures Migrating Object Comments
telnet roc239
b. Using Telnet, log in to the device by entering the operator user name
and password in response to the prompts.
c. At the command prompt, change to the /tmp directory by entering:
cd /tmp
d. For each project whose comment data you want to migrate to the Windows
platform, run the script file by entering the following command:
sqlplus <user>/<password> @get_comments_on_hp.sql
<project>
where <user> is the user name, <password> is the user’s password, and
<project> is the project name.
The user name and password must be associated with the project whose comment
data is being retrieved.
For example, for project Q2 with user Q2_CFG whose password is

Q2_CFG, you would enter:
sqlplus Q2_CFG/Q2_CFG @get_comments_on_hp.sql Q2
The script retrieves the comment data and places in a file named
update_nt_comments_<project>.sql where <project> is the project name.
For the project in the example above, the file name is
update_nt_comments_Q2.sql.
e. Enter exit to logout of and close the connection to the Advant Station
with AdvaBuild for HP-UX software.
This opens a Telnet message box indicating: “Connection to host lost”.
f. Click OK.
3. Transfer the update_nt_comments_<project>.sql file to the PC running the
Windows operating system with the AdvaBuild software where the migrated
project resides. To do so from the PC running the Windows operating system
with the AdvaBuild software,
3BUR002065R3501 53
Migrating Object Comments Appendix A Additional HP-UX to Windows Migration Procedures
a. At the command prompt, make the ftp connection to the Advant Station
with AdvaBuild for HP-UX software where the update comments file
resides using the following command:
ftp <device name>
ftp roc239
name.
b. Log in to the device by entering the operator user name and password in
c. At the ftp> prompt, change to the /tmp directory by entering:
cd /tmp
d. Retrieve the update_nt_comments_<project>.sql file using the following
command:
get update_nt_comments_<project>.sql
where <project> is the project name.
Once transfer of the update_nt_comments_<project>.sql file is complete,
a message indicating transfer is complete is displayed.
e. After transfer of the update_nt_comments_<project>.sql file is complete,
at the ftp> prompt, enter:
quit
prompt.
4. Update the project on the Windows platform with their comment data by
running the corresponding update_nt_comments_<project>.sql script file.
The project whose comments are to be updated must exist on the Windows
platform before the script can be run. In addition, all objects that existed for the
project on the HP-UX platform must also exist on the Windows platform.
To run the script file, enter the following at the command prompt:
54 3BUR002065R3501
Appendix A Additional HP-UX to Windows Migration Procedures Migrating Annotation Text
sqlplus <user>/<password>
@update_nt_comments_<project>.sql
The user name and password must be associated with the project being updated.

sqlplus Q2_CFG/Q2_CFG @update_nt_comments_Q2.sql
The script generates a log file named update_nt_comments_<project>.log
where <project> is the project name. The .log file contains the result of the
update, and must be checked for any errors.
5. Check the .log file(s) created by running the script file for updating the
comments.
6. Close the Command Prompt window by entering exit at the command
prompt.
7. Verify that the comments were updated in the migrated project.
a. Log in to the Control Builder and open the project under which you
updated the comments. Refer to the AdvaBuild Control Builder User’s
Guide for details.
b. Examine the contents of the Comment field in the List view of the
Navigator window. The comment data that existed for objects on the
HP-UX platform should be shown in the Comment field for those same
objects on the Windows platform.
Migrating Annotation Text

You must perform the following to migrate the annotation text from the HP platform
to the Windows platform:
1. Transfer the script file (export_hp_annotate.sh) that retrieves the annotation
text to the Advant Station with AdvaBuild for HP-UX software. To do so from
3BUR002065R3501 55
Migrating Annotation Text Appendix A Additional HP-UX to Windows Migration Procedures
the PC running the Windows operating System where the migrated database
resides,
b. Change to the drive letter where AdvaBuild is installed to see the path if it
is something other than c:\ (enter d: for example).
d. Make the ftp connection to the Advant Station with AdvaBuild for HP-UX
ftp <device name>
ftp roc239
name.
f. At the ftp> prompt, change to the /tmp directory by entering:
cd /tmp
g. Put the script file that retrieves the annotation text in the \tmp directory
using the following command:
put export_hp_annotate.sh
Once transfer of the script file is complete, a message indicating transfer is
h. After transfer of the script file is complete, at the ftp> prompt, enter:
quit
prompt.
56 3BUR002065R3501
Once the script file to retrieve annotation text is transferred to the Advant
Station with AdvaBuild for HP-UX software where the database was migrated
from, it can be run against the project containing the annotation text to be
migrated.
2. Run the script file to retrieve the annotation text. To do so from the PC running
the Windows operating System where the migrated database resides,
a. At the command prompt, open a Telnet window to the Advant Station with
AdvaBuild for HP-UX software where the script file resides using the
following command:
telnet <device name>
telnet roc239
b. Using Telnet, log in to the device by entering the operator user name
and password in response to the prompts.
c. At the command prompt, change to the /tmp directory by entering:
cd /tmp
d. Set up execute permissions for the script file:
chmod u+x export_hp_annotate.sh
e. For each project whose annotation text you want to retrieve and migrate to
the Windows platform, run the script file by entering the following
command:
export_hp_annotate.sh <user> <password> <project>
where <user> is the project user name, <password> is the project user’s
password, and <project> is the project name.
The user name and password must be associated with the project whose
annotation text is being retrieved.

export_hp_annotate.sh Q2_CFG Q2_CFG Q2
3BUR002065R3501 57
The script retrieves the annotation data and places it in two files named
annotate_<project>.dmp and annotate_<project>.log where <project> is
the project name. For the project in the example above, the file names are
annotate_Q2.dmp and annotate_Q2.log. The .log file contains the result of
the export, and must be checked for any export errors. The .dmp file
contains the ORACLE export data for the LOOP_ANNOTATE table and
must be transferred to the Windows platform.
f. Enter exit to logout of and close the connection to the Advant Station
with AdvaBuild for HP-UX software.
This opens a Telnet message box indicating: “Connection to host lost”.
g. Click OK.
3. Transfer the annotate_<project>.dmp file to the PC running the Windows
operating system with the AdvaBuild software where the migrated project
resides. To do so from the PC running the Windows operating system with the
AdvaBuild software,
a. At the command prompt, make the ftp connection to the Advant Station
with AdvaBuild for HP-UX software where the annotate_<project>.dmp
file reside using the following command:
ftp <device name>
ftp roc239
name.
b. Log in to the device by entering the operator user name and password in
c. At the ftp> prompt, enter:
binary
d. At the ftp> prompt, change to the /tmp directory by entering:
cd /tmp
58 3BUR002065R3501
e. Get the corresponding annotate_<project>.dmp file using the following

command:
get annotate_<project>.dmp
where <project> is the project name.
Once transfer of the annotate_<project>.dmp file is complete, a message
indicating transfer is complete is displayed.
f. After transfer of the annotate_<project>.dmp file is complete, at the ftp>
prompt, enter:
quit
prompt.
4. Update the project on the Windows platform by importing the transferred .dmp
file into the migrated project.
The project whose annotation text is being updated must exist on the Windows
platform before the script can be run. In addition, all objects that existed for the
project on the HP-UX platform must also exist on the Windows platform.
To do so from the PC where the migrated project resides,
a. Run the import_nt_annotate.bat batch file by entering the following at the
command prompt:
import_nt_annotate.bat <user> <password>
annotate_<project>.dmp
The user name and password must be associated with the project whose
annotation text is being updated.

import_nt_annotate.bat Q2_CFG Q2_CFG annotate_Q2.dmp
3BUR002065R3501 59
When the batch file is run, the LOOP_ANNOTATE table is populated with the
annotation text values that existed for the project on the HP-UX platform.
Running the batch file, also generates a set of log files whose names are
displayed on the screen by the batch file. Each .log file created has a name
unique to the project being updated. The .log file contains the result of the
update, and must be checked for any errors.
5. Check the .log file created by running the batch file for updating the annotation
text.
prompt.
7. Verify that the annotation text was updated in the migrated project.
a. Log in to the Control Builder and open the project under which you
updated the annotation text. Refer to the AdvaBuild Control Builder
User’s Guide for details.
b. Select the CTRL_BLOCK, LOOP_DEF or DEV_LOOP object in the tree
view that had annotation text on the HP-UX platform.
c. Choose Object > Annotation from the menu bar or Annotation from the
context menu (right mouse button).
d. Examine the contents of the lower portion of the Loop Annotation dialog.
The annotation text that existed for objects on the HP-UX platform should
be shown in the lower portion of the Loop Annotation dialog for those
same objects on the Windows platform.
60 3BUR002065R3501
Appendix B Data Transfer From Windows to
HP-UX Platform
Overview of Data Transfer from Windows to HP-UX

Platform
1. On the Windows platform (that is, Windows-based Engineering Station), save
the full or partial database you want to migrate using the advanced functions of
the Save ATF utility.
2. On the Windows-based Engineering Station, use fmsHPConvert to convert the
Windows FMS file to a FMS file that can be read by HP-UX FMS utilities (that
is, a HP binary transition file).
3. Transfer the binary transition file to the HP-UX platform.
4. Create a project on the Advant Station with AdvaBuild for HP-UX software
where the database migrated from the Windows platform will be stored.
5. Load the binary transition file.
3BUR002065R3501 61
Data Transfer of a Database Appendix B Data Transfer From Windows to HP-UX Platform
Data Transfer of a Database

To migrate a database from the Windows platform to the HP-UX platform:
1. On the Windows-based Engineering Station, save the database you want to
migrate as an ASCII transition file and then convert the ASCII transition file to
a binary transition file by using the built in conversion utility of the Save ATF
function. To do so,
a. Log in to the Control Builder and open the project you want to migrate to
the HP-UX platform. Refer to the AdvaBuild Control Builder User’s
Guide for details.
b. You determine what portion of the current database is included in the
transition file by selecting an object. The selected object and all of its
descendants will be included in the transition file. If you want to include
the entire data base you must select the MOD_DB object. Select the
desired object (MOD_DB or lower) in the tree view.
c. Choose Object > Special Commands > Save_ATF from the menu bar.
This opens the Save ASCII Transition File dialog, Figure 5.
Figure 5. Save ASCII Transition File Dialog
62 3BUR002065R3501
Appendix B Data Transfer From Windows to HP-UX Platform Data Transfer of a Database
If you hold the cursor over the Transition File or Log File fields, the
default directory path where the file will reside is displayed as help text.
d. To convert the ASCII transition file to a binary transition file using the
built in conversion utility of the Save ATF function, click on the
Advanced button.
This opens the Advanced… dialog, Figure 6.
Figure 6. Advanced… Dialog
e. Make sure the Save as Binary option is checked.

f. By default, the Binary Filename field contains a default binary transition
file name. If desired, enter a different transition file name of up to eight
alphanumeric characters by typing it in the field.
g. Binary transition files are version dependent; therefore, the version of the
binary file generated by the Save_ATF function must match the version of
3BUR002065R3501 63
AdvaBuild for HP-UX software installed on the Advant Station where you
want to migrate the database. Select the appropriate version from the pick
list for the Version field.
Select Version ES2.9/0(14.5/0) to support ES2.9/1.

The (14.6/0) version should not be used.
h. Click on the Ok button to close the Advanced… dialog.
i. On the Save ASCII Transition File dialog, click on the Save button or
press <ALT+V> to start the save.
Profibus I/O is not supported on the HP-UX platform. If the built in utility of the
Save ATF function that converts the ASCII transition file to a binary transition
file encounters a PROFIBUS_IO, PROFIBUS_LAN, PROFIBUS_DEV,
PROFIBUS_MOD, or PROFIBUS_DIR object below the object selected in
Step b, the Profibus object is skipped and an entry is made in the log file that
states the object was not included in the binary transition file. The following is an
example of the log message for a PROFIBUS_IO object:
TEMPLET: “AC460-1_PROFIBUS_IO” WAS NOT INCLUDED IN BINARY
TRANSITION FILE BECAUSE IT IS A PROFIBUS TEMPLET TYPE.
When the Save ATF process is complete, the Save ATF utility converts the
newly created ASCII transition file to a binary transition file. The binary
transition file is created on the Windows-based Engineering Station in the
Binary Transition File directory located in:
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\50\DBASE
2. On the Windows-based Engineering Station, use fmsHPConvert to convert the
Windows FMS file to a FMS file that can be read by HP-UX FMS utilities. To
do so, at the command prompt, enter:
cd %AdvaBuild_Bin%
fmsHPConvert “c:\Program Files\ABB Industrial
IT\Data\SystemServices\FMS\WC00\50\DBASE\*”
Assuming System Services is loaded on drive c, this converts all transition files
and places the converted files in either: c:\Temp\fmsconvert\wc00\50\dbaseor
64 3BUR002065R3501
in c:\Documents and Settings\<username>\Local

Settings\Temp\fmsconvert\wc00\50\dbase.
The following is an example of the messages displayed in the Command
Prompt window during the fmsHPConvert process.
C:\> fmsHPConvert "c:\Program Files\ABB Industrial IT\Data\SystemServices\FMS

\WC00\50\DBASE\*"
Starting the conversion of:
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\50\DBASE\*
The converted files will be in:

c:\Documents and Settings\<username>\Local Settings\Temp\fmsConvert\wc00\50
\dbase\*
See the log file for details: (c:\Documents and Settings\<username>\Local

Settings\Temp\fmsConvert\ConvertLog.txt)
The following is an example of the information included in the log file for the
fmsHPConvert process.
******** Start of FMS File Convert Log File ********

Start time: Thu Jun 15 15:13:53 2000
Running nttohp conversion on: C:\Documents and Settings\<username>\Local

Settings\Temp\fmsConvert\wc00\50\dbase\AC_AREA.DT.dat
Running nttohp conversion on: C:\Documents and Settings\<username>\Local
Settings\Temp\fmsConvert\wc00\50\dbase\CCF_X.DT.dat
Running CTUNF1 conversion on: C:\Documents and Settings\<username>\Local
Settings\Temp\fmsConvert\wc00\50\dbase\AC_AREA.DT.dat
Running CTUNF1 conversion on: C:\Documents and Settings\<username>\Local
Settings\Temp\fmsConvert\wc00\50\dbase\AC_AREA.DT.nky
End time: Thu Jun 15 15:13:56 2000

******** End of FMS File Convert Log File ********
3BUR002065R3501 65
3. On the Windows-based Engineering Station, put the resulting binary transition

file on the target Advant Station with AdvaBuild for HP-UX software via ftp.
To do so,
a. At the command prompt, change to the directory where the converted
transition file resides using the command below:
cd Documents and Settings\<username>\Local
Settings\Temp\fmsconvert\wc00\50\dbase
b. Make the ftp connection to the target device to which you want to transfer
the transition file using the following command:
ftp <device name>
For example, to connect to the device named roc239, you would enter ftp
roc239.
to the source device and if it is ready. You are also prompted to enter a
user name.
c. Log in to the device by entering the ocsmgr user name and password in
d. At the ftp> prompt, enter:
prompt
e. At the ftp> prompt, enter:
binary
The ftp transfer mode must be set to binary as indicated above. Failure to do so
will result in corrupt FMS files on the target Advant Station with AdvaBuild for
HP-UX software after transfer.
f. Change to the directory to which you want to transfer the converted
transition file using the command below:
cd /home/opt/advant/FMS/WC00/50/DBASE
g. Use the mput command to transfer the transition file from the Windows-
based Engineering Station in the following format:
mput <transition file name>.DT.*
66 3BUR002065R3501
h. After transfer of the desired .dat and .nky files is complete, at the ftp>
prompt, enter:
quit
prompt.
i. Close the Command Prompt window by entering exit at the command
prompt.
4. On the Advant Station with AdvaBuild for HP-UX software, load the binary
transition file transferred from the Windows-based Engineering Station. To do
so,
a. Open an HP-Term window and change directories using the command
below:
cd $FMSPATH/WC00/50/DBASE
b. Verify that the permissions for the transition file are set as follows:
Permissions: rw-rw-rw
If necessary, use chmod to set as above.
c. If the project does to which you want to migrate the database from the
Windows platform does not already exist, insert the project using the
Structure Builder Administration functionality. (Refer to the AdvaBuild
Basic Functions User’s Guide for details on how to start the Structure
Builder, insert a project, load the transition file, and check the log file.)
d. Log into the project using the project name and password, and select the
PROJECT level object in the tree structure.
e. Choose Special Commands from the Object menu.
f. Select LOAD_TRANS.
This displays the Load Transition File dialog.
g. With the Transition File field selected, type the transition file’s name, up
to eight alphanumeric characters, including underscores. No other
characters (for example, period, dash, and so on) may be used in the
transition file’s name.
3BUR002065R3501 67
h. Click on Start Load to start the load transition file process.

A message box is displayed when the load is finished.
i. Click on OK to acknowledge the message and return to the Load
Transition File dialog.
When you compile a database that contains a PROFIBUS I/O templet on an

Advant Station with AdvaBuild for HP-UX software, the compiler skips the
PROFIBUS I/O templet and produces the following message:
Warning: PROFIB_IO is not supported by ADVANT Stations.Templets
Skipped.
68 3BUR002065R3501
Appendix C Revision Control Tools
Get Revision
The GetRevision executable is used to get RCS information from FMS files and
output the results to a file where you can verify what versions of files are actually
executing at runtime.
Running GetRevision
To run this program, open a Command Prompt window from the Windows task bar
by choosing Start > Programs > Accessories > Command Prompt (as
appropriate) and change to the drive letter and path where AdvaBuild is installed
(AdvaBuild_Bin is the install path variable) as follows:
cd %AdvaBuild_Bin%
For TCL Sequence(s), use either of the following commands (use * to do all files or
specify a file name to do one file):
GetRevision seq *
GetRevision seq <seq name>
For TCL Recipe(s), use either of the following commands (use * to do all files or
GetRevision rec *
GetRevision rec <rec name>
For TLL Segment(s), use either of the following commands (use * to do all files or
GetRevision seg <device name> *
GetRevision seg <device name> <seg name>
3BUR002065R3501 69
Get Revision Appendix C Revision Control Tools
Viewing GetRevision Output File

All output files will be located in the Temp directory. The output file name uses
"List" when * is used;, otherwise, the file name name is used as follows:
SeqList_<date>.log (for example SeqList_30May02.log)
<seq name>_<date>.log
RecList_<date>.log
<rec name>_<date>.log
<device name>List_<date>.log
<device name><seq name>_<date>.log
The output format is as follows:
Filename, Status, FMS Date, incString, RCS ver, RCS Date
12 chars., 17chars., 19 chars., 12 chars., 6 chars., %19chars.
PL_1000, Linked, 2002/07/09 11:09:36, , 1.1, 2002-05-10 16:11:13
PL_1001C, Linked, 2002/07/09 11:09:45, , 1.1, 2002-05-10 15:13:55
70 3BUR002065R3501
Appendix D Serial Data Transfers
Migration from Multibus to Windows

This section provides procedures for serial data transfer which is also available, but
no longer necessary. Use the procedure in Using File Migration Utility for Multibus
to Windows on page 43 if possible.
• Preparation Before Migration from Multibus to Windows
• Database Migration from Multibus to Windows
• TCL File Migration from Multibus to Windows
• FMS User Data File Migration from Multibus to Windows
• Environment and Graphic File Migration from Multibus to Windows
Preparation Before Migration from Multibus to Windows

To prepare your PC for migration of a database, TCL sequences and recipes, and
FMS user data files generated on the Multibus platform, verify the Computer
Interface configuration.
In order to use the AdvaBuild Control Builder serial data transfer functions to
migrate MOD 300 database configuration files generated on the Multibus platform
to the Windows platform, there must be a serial interface between the PC running
the Windows operating system and the Multibus Console. Hardware requirements
for the serial interface of a Multibus Console are described in the Taylor IBM PC
Interface User’s Guide.
To verify the serial interface configuration, you will need the following two nodes
connected via a serial cable and configured as per the user’s guide mentioned above:
• a PC running the Windows operating system with the Windows Computer
Interface application and FMS functions installed
3BUR002065R3501 71
Database Migration from Multibus to Windows Appendix D Serial Data Transfers
• a Multibus Turbo Node configured to run the CI Interface (does not need to be
a CDP node)
The parameters (baud rate, parity, data bits, and stop bits) for the serial port on the
PC running the Windows operating system must be configured to match the
parameters of the corresponding serial port on the remote platform (Multibus
Console). For the Multibus node, the serial interface parameters are defined on the
Serial Port Setup Template as described in the System Configurator User’s Guide.
From the PC, run CiConfigure to verify the Computer Interface configuration.
Database Migration from Multibus to Windows

This section contains an overview of the database migration process and the detailed
procedures for migrating a database from the Multibus to the Windows platform.
Overview of Database Migration

1. On the Multibus platform, save the full or partial database you want to migrate
as a binary transition file.
2. Transfer the binary transition file to the Windows platform.
3. On the PC running the Windows operating system, convert the binary transition
file to an ASCII transition file.
4. Load the ASCII transition file.
Procedure for Migration of a Database

To migrate a database from the Multibus platform to the Windows platform:
1. From the Multibus Console, save the database you want to migrate as a
transition file. To do so,
a. Start the System Configurator.
b. Select the MOD 300 Data Base Templet or Directory.
c. From the third set of softkeys on the templet or directory, select the SAVE
TRANS softkey.
72 3BUR002065R3501
Appendix D Serial Data Transfers Database Migration from Multibus to Windows
This calls up two fields above the softkeys: TRANSITION FILE NAME
and OVERWRITE EXISTING FILE. The TRANSITION FILE NAME
field is where you name the transition file being created for the database.
The OVERWRITE EXISITING FILE field is where you indicate whether
or not the data in an existing transition file with the same name as the one
being created is to be replaced by the data being saved. Initially the
TRANSITION FILE NAME field is selected (highlighted) and waiting for
you to enter the transition file’s name; however, you can select either of
these fields by pressing the NEXT FIELD key.
d. With the TRANSITION FILE NAME field selected, type the transition
file’s name, up to eight alphanumeric characters, including underscores.
No other characters (for example, period, dash, and so on) may be used in
the transition file’s name.
e. Press the ENTER key.
f. With the OVERWRITE EXISTING FILE field selected, press the NEXT
CHOICE key until the desired response is displayed in the field.
The choices are YES and NO. The YES option overwrites the data in the
existing transition file with the same name, and the NO option does not
overwrite the data in the existing transition file.
g. After you enter a valid transition file name and indicate whether a
duplicate transition file it to be overwritten, select the SAVE TRANS
softkey again to create the transition file.
2. Test the serial connection between the Multibus node and the Windows
platform and save the configuration settings. To do so,
cd %AdvaBuild_Bin%
c. At the command prompt, enter: CiConfigure
This opens the Computer Interface Configuration dialog, Figure 7, that
reads the CiConfig.dat file and displays the contents of that file in the
3BUR002065R3501 73
dialog. If no CiConfig.dat file exists or there is an error getting the data,

the default data is displayed.
Figure 7. Computer Interface Configuration Dialog
d. If necessary, change the entries in the fields of the Computer Interface

Configuration dialog to match the settings of the Multibus node and select
Save.
e. Click on the Test Serial Connection button and verify that the connection
to the Multibus system is working properly.
During the test of the serial connection, a status dialog indicating whether
the serial port was successfully initialized and opened is displayed,
Figure 8.
74 3BUR002065R3501
Figure 8. CiCheckConnection Status Dialog— Serial Port Initialized
f. Click on the OK button to acknowledge the message, close the status

dialog, and begin testing the serial connection.
This opens another Command Prompt window showing the progress of
the serial connection test, Figure 9.
Figure 9. Command Prompt Window for Serial Connection Test
When the serial connection test is complete, a completion dialog

indicating whether the test of the serial port was successful is displayed,
Figure 10.
3BUR002065R3501 75
Figure 10. CiCheckConnection Completion Dialog— Test Serial Port Completion
g. Click on the OK button to acknowledge the message and close the

completion dialog.
h. If testing of the serial connection was successful, proceed to the next step;
otherwise, repeat steps Step c through Step g until the test is successful.
i. Click on the Save button to save the serial port configuration settings and
close the Computer Interface Connection dialog.
CIFileUpld will not run until the serial connection configuration displayed in the
CiConfigure dialog has been tested and saved.
3. Transfer the transition file to the Windows system using the CIFileUpld
functionality which creates a binary transition file on the Windows system. To
do so, enter the following command at the command prompt:
CIFileUpld WC00:[50.DBASE]<transtion file name>.DT <node name>::WC00:[50.DBASE]<transition file name>.DT 1
where:
<transition file name> is the name of the transition file, <node name> is the
name of the Multibus node that the transition file is coming from, and the 1 at
the end indicates that Window mode is ON.
For example, to upload the transition file named REFINERY.DT from the
Multibus node named DPSS-CONFIG-REF97, you would enter:
CIFileUpld WC00:[50.DBASE]REFINERY.DT DPSS-CONFIG-
REF97::WC00:[50.DBASE]
REFINERY.DT 1
Once the CIFileUpld process is initiated, the CIFileUpld Abort dialog,
Figure 11, is opened.
76 3BUR002065R3501
Figure 11. CIFileUpld Abort Dialog
To abort the CIFileUpld process at any time, click on the OK button which will
close the dialog and abort the process. Otherwise, when the process is
complete, the CIFileUpld complete dialog is displayed and the resulting binary
transition file is located in the following directory:
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\50\DBASE
An application error for the CIFileUpld process is seen following the transfer and
can be ignored.
The following error is displayed during the conversion and can be ignored:
If a binary transition file with the same name already exists in C:\Program
Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\50\DBASE on the
Windows platform, the upload fails and the following error is displayed:
File WC00:[50.DBASE]<transition file name>.DT already
exists.
4. Convert the binary transition file (BTF) to an ASCII transition file (ATF).
a. At the command prompt, change directories using the command below:
cd %AdvaBuild_Bin%
b. Initiate the BTF to ATF conversion by entering:
btftoatf WC00:[50.DBASE]<transtion file name>.DT
..\<transition file name>.txt
3BUR002065R3501 77
The binary transition file is converted to an ASCII transition file, creating

a ATF on the PC client. The ATF file is saved in Program Files\ABB
Industrial IT\AdvaBuild.
The following error is displayed during the conversion and can be ignored:
c. Close the Command Prompt window by entering exit at the command

prompt.
5. Create a project on the PC where the database migrated from the Multibus
platform will be stored.
a. Start the AdvaBuild Administration component and login as the Admin
user. Refer to Section 3, System Administration of the AdvaBuild
Administrator’s Guide for details.
b. Choose Projects > Insert Project… from the menu bar or click on the
Insert Project icon (file folder) in the tool bar. This opens the Insert Project
dialog, Figure 12.
Figure 12. Insert Project Dialog
c. Enter a project name, project number, and project size.
The project name cannot be the same as the Multibus database name.
d. Click Insert Project to create the project.
78 3BUR002065R3501
This opens the Insert Project Status dialog indicating the insertion process
is running and you should wait. When the insertion process is finished, the
Insert Project Status dialog closes and the Insert Project Completion
dialog opens. The Insert Project Completion dialog indicates whether the
insertion process was successful.
e. Click OK to close the Insert Project Completion dialog.
6. Insert a MOD_DB templet into the newly inserted project, using the Multibus
database name. See the AdvaBuild Control Builder User’s Guide for more
detailed information about inserting objects.
To insert the MOD_DB templet:
a. Log in to the Control Builder and open the project under which you want
to add the transferred data. Refer to the AdvaBuild Control Builder User’s
Guide for details.
b. Select the PROJECT object.
c. Choose Templet > Insert… from the menu bar or Insert… from the
context menu.
This displays the Insert Object dialog box, Figure 13.
Figure 13. Insert Object Dialog
d. Select MOD_DB from the pick list for the Object Type field.
3BUR002065R3501 79
e. Enter the Multibus database name in the Object ID field.

f. Optionally, you can enter a comment for the new MOD_DB object in the
Comment field; otherwise proceed to the next step. The comment is
displayed in list view.
g. Click on the Insert button to insert the new MOD_DB object and close
the Insert Object dialog.
7. Load the ASCII transition file using the Load ATF functionality of the
AdvaBuild Control Builder. See the AdvaBuild Control Builder User’s Guide
for more detailed information about Load ATF.
To load the ASCII transition file,
a. If the Control Builder view of the project is not currently displayed, log in
to the Control Builder and open the project under which you want to add
the transferred data. Refer to the AdvaBuild Control Builder User’s Guide
for details.
b. Choose Load ATF from the Tools menu. This calls up the Load ATF
dialog.
c. Browse the location where the ASCII transition file resides (C:\temp) and
select the desired ASCII transition file name.
This automatically enters the name for the load transition report file (log)
generated by the load process for the transition file in the Log File field.
Note the log file name.
d. Click on the Load button to start the load process.
The load process is started and a progress dialog is displayed. Upon
completion of the load, the load status will change to Completed if no
errors were detected or Completed with Errors if errors are detected. If
you cancel the load operation, the load status changes to Cancelled.
During the load process, an error is generated stating that the MOD_DB templet
(inserted in Step 6) already exists and was not overwritten. As a result, one less
templet is reported to have been loaded. For example, if the transition file for the
database being migrated had 1,000 templets, the status indicates 999 templets
were loaded.
80 3BUR002065R3501
Appendix D Serial Data Transfers TCL File Migration from Multibus to Windows
8. Once loading of the ASCII transition file is complete, check the contents of the
log file for any errors.
TCL File Migration from Multibus to Windows

TCL file migration refers to the transfer of TCL sequence and recipe source files
from the Multibus platform to the Windows platform. This section contains an
overview of the TCL file migration process and the detailed procedures for
migrating TCL files from the Multibus to the Windows platform.
Overview of TCL File Migration

There is only one method for migrating TCL sequence and recipe data from the
Multibus platform to the Windows platform as outlined below. A detailed
description of this method is provided in Procedure for Migration of TCL Source
Files on page 82.
1. On the Multibus system where the TCL Builder software resides, decompile
direct recipes to source.
2. Change the CI_DEF timeout using BUGs.
3. If TCL sequence and recipe directory files exist on the Windows-based
Engineering Station, you must delete them using BUGs.
4. Connect the Multibus TCL development system to the Windows TCL Builder
Server via a RS-232 serial cable.
5. Test the serial connection between the Multibus TCL development system and
the Windows TCL Builder Server.
6. Upload the TCL sequence and recipe files in FMS format from the Multibus
TCL development system to the Windows TCL Builder Server using the
TCLMultibusMigration.bat batch program.
7. On the Windows TCL Builder Server, use the TCL Migration utility to extract
the transferred TCL sequence and recipe data as text files.
3BUR002065R3501 81
TCL File Migration from Multibus to Windows Appendix D Serial Data Transfers
commands.
Procedure for Migration of TCL Source Files

To migrate TCL source files from the Multibus platform to the Windows platform:
1. If necessary, decompile any direct recipes back into source on the Multibus
platform. See the Taylor Control Language (TCL) User’s Guide for
instructions on how to decompile a recipe to source.
If the recipes are not decompiled back into source, errors similar to the following
are reported during migration:
Server: ITEM10
Error file not found:
WC00:[210.RECIPESR]ITEM10.SR
The above error indicates that the direct recipe for ITEM10 exists, but was not
decompiled back into source.
2. Modifications can be made to the CIGATE.PK file on the Multibus Turbo
Node from which you are migrating data to increase the timeout value. To do
so,
a. From a BUGs terminal on the Multibus Turbo Node, check the date
CIGATE.PK file was last updated by entering the following at the What’s
up Doc?> prompts:
FMS [50.MOD300S]
DIR CIGATE.PK ;LD
82 3BUR002065R3501
The following is an example of the messages displayed on the BUGs

terminal for the above commands.
Directory WC00:TEST[50.MOD300S]
CIGATE.PK File Type: Contiguous
Write Access Code: $0 Date Created: 1-JAN-1981

Read Access Code: $0 Last Updated: 3-DEC-1999
Starting Sector: $12632 Number of Sectors: &666
Copy size: &671 Checksum: $cbc9
Total of 1 File
b. Determine the address for which the timeout value must be changed from
Table 2 by using the Last Updated date. In the example above, the Last
Updated date is 3-DEC-1999; therefore, the address for which the timeout
value must be changed is 0028041C.
Table 2. Addresses for which the Timeout Value Must be Changed
Source
Version Date Last Updated Address
Level
E14R4 1-FEB-1999 0028041C
E14R4 21-DEC-1998 00280414
E14R4 15-DEC-1998 00280FD6
E14R4 15-MAY-1997 00280FFE
E14R4 2-APR-1997 00280FFE
E14R5 3-DEC-1999 0028041C
E14R6 3-DEC-1999 0028041C
3BUR002065R3501 83
If the Last Updated date for your CIGATE.PK file does not match any of those
listed in Table 2 or the value at the corresponding address is not 00000002, do not
continue and notify Technical Support.
c. Increase the internal timeout value by entering the following at the What’s
up Doc> prompt:
MM 28041C ;L
0028041C 00000002 ?10.
This increases the internal timeout value at that address. You may proceed with
the migration.
This change only affects the version of CIGATE.PK that is loaded into memory.
If for some reason the Multibus Turbo Node is rebooted and you wish to transfer
the files again, you must repeat the above procedures again.
3. If TCL sequence and recipe directory files exist on the Windows-based
Engineering Station, you can delete them using BUGs. To do so on the
Windows-based Engineering Station,
The method described in this step is optional and can be done from Windows
Explorer as described in Step 5.
a. Enter the following at the What’s up Doc?> prompts:

FMS [210.TCL]
DEL SEQ_DIR.*
FMS [210.RECIPE]
DEL RECIPE.*
84 3BUR002065R3501
The following is an example of the messages displayed on the BUGs terminal

for the above commands.
What’s up Doc?> FMS [210.TCL]
FMS Path Defaults-

Device Name: WC00
Volume Label: TEST
<NEW> User Number: 210
<NEW> Catalog Name: TCL
WC00:TEST[210.TCL]
What’s up Doc?> DEL SEQ_DIR.*

<dbgdelete> Deleting: WC00:TEST[210.TCL]SEQ_DIR.D2
<dbgdelete> Deleting: WC00:TEST[210.TCL]SEQ_DIR.DR
What’s up Doc?> FMS [210.RECIPE]
FMS Path Defaults-

Device Name: WC00
Volume Label: TEST
<NEW> User Number: 210
<NEW> Catalog Name: RECIPE
WC00:TEST[210.RECIPE]
What’s up Doc?> DEL RECIPE.*

<dbgdelete> Deleting: WC00:TEST[210.RECIPE]RECIPE.D2
<dbgdelete> Deleting: WC00:TEST[210.RECIPE]RECIPE.DR
b. Exit BUGs by entering the following at the What’s up Doc?> prompt:
EX
4. Connect the Multibus node to the Windows TCL Builder Server via a RS-232
serial cable. That is, connect the 25-pin connector to the serial output board on
the back of the Multibus node, and connect the 9-pin connector to the COM1 or
COM2 port on the back of the Windows TCL Builder Server.
5. The TCLMultibusMigration.bat utility will not overwrite any existing TCL
sequence and recipe files in FMS format that are located in the following
3BUR002065R3501 85
directories (assuming System Services is installed on the C drive). An empty

TCL directory is automatically created as part of creating a project.
If files exist in these directories (from a previously migration or failed
migration), use Windows Explorer to delete them. Existing files are not
overwritten. Remember, an empty TCL directory file is auto created when the
project is created.
6. Test the serial connection between the Multibus node and the Windows TCL
Builder Server and save the configuration settings. To do so,
cd %AdvaBuild_Bin%
CiConfigure
dialog. If no CiConfig.dat file exists or there is an error getting the data,
the default data is displayed.

Save.
Figure 15.
86 3BUR002065R3501

3BUR002065R3501 87

Figure 17.
Figure 17. CiCheckConnection Completion Dialog — Test Serial Port

completion dialog.
otherwise, repeat steps Step c through Step g until the test is successful.
88 3BUR002065R3501
TCLMultibusMigration.bat will not run until the serial connection configuration

displayed in the Computer Interface Configuration dialog has been tested and
saved.
7. Start the TCLMultibusMigration.bat batch program (which uploads the TCL
sequence and recipe files in FMS format from the Multibus node to the
Windows TCL Builder Server) by entering the following command at the
command prompt:
TCLMultibusMigration.bat <node name>
where <node name> is the name of the Multibus node from which the TCL
sequence and recipe files are being transferred.
For example, to upload the TCL sequence and recipe files in FMS format from
the Multibus node named DPSS100, you would enter:
TCLMultibusMigration.bat DPSS100
Once the upload process is initiated, progress messages are displayed in the
Command Prompt window. Figure 18 and Figure 19 show examples of the
upload progress messages.
An abort dialog is also opened, Figure 20. To abort the migration at any time,
click on the OK button. This will close the dialog and abort the upload process;
otherwise, when the process is complete the abort dialog is closed.
8. Upload completion dialogs, Figure 21, are opened during the upload process.
Click on the OK button to acknowledge these messages and close the dialogs.
3BUR002065R3501 89
Figure 18. TCLMultibusMigration Progress Messages
90 3BUR002065R3501
Figure 19. TCLMultibusMigration Progress Messages (Continued)
Figure 20. CIFileUpld Abort Dialog
3BUR002065R3501 91
Figure 21. CIFileUpld Completion Dialog
The upload completion dialogs open on top of the abort dialog. It is

recommended that you move the abort dialog to another location in the screen to
avoid inadvertently aborting the upload instead of acknowledging a completion
message.
When the upload is complete the resulting TCL sequence and recipe files in
FMS format are placed in the following directories on the Windows TCL
Builder Server:
prompt.
10. On the Windows TCL Builder Server, use the SetNotCompiled executable to
set the status for uploaded sequence and recipe text files to “Not Compiled.” To
do so,
b. Start the SetNotCompiled executable by double clicking on the
SetNotCompiled.exe icon.
11. On the Windows TCL Builder Server, use the TCL Migration Utility to extract
the uploaded sequence and recipe text files in FMS format as text files and
move them into the appropriate directories. To do so,
92 3BUR002065R3501

b. Start the TCL Migration Utility by double clicking on the TCLMigration
icon.
This opens the TCL Migration dialog, Figure 4.
c. In the Server Name field, enter the name of the Windows server to which
the FMS files were transferred in Step 7.
d. Enter your CONFIG user name and password in the corresponding User
Id and Password fields.
e. Select the desired drive and folder where you want to store the .tcl and .rcp
text files. By default, the drive and folder for the TCL Builder is located at
c:\Documents and Settings\<username>\My Documents\My TCL.
f. Click on the Migrate Data button.
This closes the TCL Migration dialog and moves the migrated .tcl and .rcp
text files to the specified drive and folder on the server you are currently
logged into.
Enter the following at the command prompt to convert all .tcl sequence and
.rcp recipe files. ADDRCSInfo is located in the path represented by the
variable AdvaBuild_Bin.
cd %AdvaBuild_Bin%
AddRCSInfo seq <input file path> <<output file path>>
AddRCSInfo rec <input file path> <<output file path>>
where
3BUR002065R3501 93
FMS User Data File Migration from Multibus to Windows Appendix D Serial Data Transfers
<<output file path>> = Location of output files and .log files (seq.log and
rec.log). Not required. If not specified, files are located in: c:\Documents
and Settings\<username>\Local Settings\Temp\AddRCSInfo.
commands. See the AdvaBuild TCL Builder User’s Guide for information
about checking in files to the RCS, compiling, linking, and so on. A
GetRevision executable is used to get RCS information from FMS files and
output the results to a file where you can verify what versions of files are
actually executing at runtime. See Appendix C, Revision Control Tools.
FMS User Data File Migration from Multibus to Windows

FMS user data file migration refers to the transfer of TLL files and memory pool
configuration files from the Multibus platform to the Windows platform. This
section contains an overview of the FMS user data file migration process and the
detailed procedures for migrating FMS user data files from the Multibus to the
Windows platform.
Serial transfer of nested TLL and PLC configuration files does not work. Use the
procedures in Using File Migration Utility for Multibus to Windows on page 43.
Overview of FMS User Data Files Migration

The following is a brief overview of the FMS user data file migration procedure,
1. Connect the Multibus Console to the PC running the Windows operating
system with AdvaBuild Control Builder software via a RS-232 serial cable.
2. Test the serial connection between the Multibus Console and the PC running
the Windows operating system with AdvaBuild Control Builder software.
3. Upload the FMS user data files from the Multibus Console to the PC running
the Windows operating system with AdvaBuild Control Builder software using
the CiFileUpld utility.
94 3BUR002065R3501
Appendix D Serial Data Transfers FMS User Data File Migration from Multibus to Windows
Procedure for Migration of FMS User Data Files

To migrate FMS user data files from the Multibus platform to the Windows
platform:
1. Connect the Multibus node to the PC running the Windows operating system
with AdvaBuild Control Builder software via a RS-232 serial cable. Place the
25-pin connector into the serial output board on the back of the Multibus node,
and the 9-pin connector into the COM1 or COM2 port on the back of the PC
running the Windows operating system with AdvaBuild Control Builder
software.
2. If the BUGS terminal connected to the Multibus node is in debug mode, type
EX at the command prompt and press <Return>.
If the BUGS terminal is in the debug mode, the serial connection will not operate
properly.
3. Test the serial connection between the Multibus node and the PC running the
Windows operating system with AdvaBuild Control Builder software and save
the configuration settings. To do so,
cd %AdvaBuild_Bin%
CiConfigure
dialog. If no CiConfig.dat file exists or there is an error getting the data, a
dialog indicating so is opened and the default data is displayed. Click on
the OK button to acknowledged the message and close the dialog.

Save.
3BUR002065R3501 95
Figure 23.
96 3BUR002065R3501


Figure 25.
Figure 25. CiCheckConnection Completion Dialog — Test Serial Port
3BUR002065R3501 97

completion dialog.
otherwise, check the serial connection between the Multibus and
Windows platforms, make sure the BUGS terminal is in the debug mode,
and repeat steps Step c through Step g until the test is successful.
CIFileUpld will not run until the serial connection configuration displayed in the
CiConfigure dialog has been tested and saved.
4. Transfer the TLL files that reside on the Multibus platform to the Windows
platform using the CIFileUpld functionality and then convert the transferred
files from FMS to text file format. To do so,
a. Upload the LIB_DIR.DR/D2 directory files in FMS format from the
[1.PLC] catalog of the Multibus node to the Windows-based Engineering
Station by entering the following command at the command prompt:
%AdvaBuild_Bin%\UPLOADTLLDEVLIB <MOD300 Node Name>
b. For each Controller or Generic DPSS device where Ladder Logic is
configured, upload LIB_DIR.DR/D2 directory files in FMS format from
that device’s catalog [20556.<device name>] to the Windows-based
Engineering Station by entering the following command at the command
prompt:
%AdvaBuild_Bin%\UPLOADTLLSEGLIB <device name> <MOD300
Node Name>
where:
<MOD300 Node Name> is the name of the Multibus Configurator Data
Processor (CDP) node name where TLL is configured.
c. For each Controller or Generic DPSS device where Ladder Logic is
configured, transfer the ladder logic programs in FMS format to the
98 3BUR002065R3501
Windows-based Engineering Station by entering the following command

at the command prompt:
CIFileUpld WC00:[20556.<device>]*.SR
<node>::WC00:[20556.<device>]*.SR 1
where:
<device> is the templet name (unique 8 character beginning not the full
template name) of the Controller or Generic DPSS device where TLL is
configured to run.
<node> is the name of the Multibus node that the ladder logic program
file(s) is (are) coming from, and the 1 at the end indicates that Window
mode is ON so messages are displayed in a Command Prompt window
during the transfer process.
Click OK to acknowledge the transfer.
When the upload of the TLL FMS user data files is complete the resulting
TLL FMS user data files in FMS format are placed in the following
directories on the PC running the Windows operating system with
AdvaBuild Control Builder software:
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\1\PLC
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\20556\<device name>
d. For each Controller or Generic DPSS device from which ladder logic
program files were transferred, convert the transferred files from FMS to
text file format by entering the following command at the command
prompt:
“%AdvaBuild_Bin%\TLLTranslateFMS.exe” <tlldevice name>
where:
<tlldevice name> is the templet name of the TLL device in the Controller or
Generic DPSS device where TLL is configured to run.
All .SR files transferred from that device are converted to text files with
the .tll extension and are placed in that device’s default directory:
C:\Documents and Settings\advabuild\My Documents\My TLL\<device
name>
3BUR002065R3501 99
These files may be placed under revision control using the TLL Builder.
Enter the following at the command prompt to convert all .tll segment files.
ADDRCSInfo is located in the path represented by the variable
AdvaBuild_Bin.
cd %AdvaBuild_Bin%
AddRCSInfo seg <device name> <input file path> <<output
file path>>
where
<<output file path>> = Location of output files and
seg_<device name>.log file. Not required. If not specified, files are
located in: c:\Documents and Settings\<username>\Local
Settings\Temp\AddRCSInfo.
6. Use the TLL Builder to check in the text files (.tll) to the Revision Control
System (RCS) of the Windows TLL Builder Server. The text files placed under
revision control may be moved to on-line storage using the TLL Builder Set
Active Revision and Compile commands. See the AdvaBuild TLL Builder
User’s Guide for information about checking in files to the RCS, compiling,
and so on. A GetRevision executable is used to get RCS information from FMS
files and output the results to a file where you can verify what versions of files
are actually executing at runtime. See Appendix C, Revision Control Tools.
7. Transfer the PLC configuration files that reside on the Multibus platform to the
Windows platform using the CIFileUpld functionality. To do so, enter the
following command at the command prompt:
100 3BUR002065R3501
CIFileUpld WC00:[260.CONFIG]*.* <node

name>::WC00:[260.CONFIG]*.* 1
where:
<node name> is the name of the Multibus node that the transition file(s) is
(are) coming from, and the 1 at the end indicates that Window mode is ON so
messages are displayed in a Command Prompt window during the transfer
process.
If contiguous files are present, you may have to run this program multiple times
in order to pick up the indexed files. After the files are transferred, you can delete
the files created for any contiguous files.
PC Def and PC Port files are transferred. PC Command files are not and must be
manually re-entered. Use the DCN file transfer program (see Using File
Migration Utility for Multibus to Windows on page 43) for transfers.
For example, to upload the PLC configuration files from the Multibus node
named DPSS100, you would enter:
CIFileUpld WC00:[260.CONFIG]*.*
DPSS100::WC00:[260.CONFIG]*.* 1
Click OK to acknowledge the transfer.
When the upload of the PLC Configuration FMS user data files is complete the
migration of the PLC Configuration is complete. The resulting PLC
Configuration FMS user data files in FMS format are placed in the following
directory on the PC running the Windows operating system with AdvaBuild
Control Builder software:
C:\Program Files\ABB Industrial IT\Data\SystemServices\FMS\WC00\260\CONFIG
8. To transfer the memory pool configuration files that reside on the Multibus
platform, with the exception of the POOLS.PL files, to the Windows platform,
you must use the DCN transfer program (see Using File Migration Utility for
Multibus to Windows on page 43).
3BUR002065R3501 101
Environment and Graphic File Migration from Multibus to Windows Appendix D Serial Data
Environment and Graphic File Migration from Multibus to Windows

Environment and Graphic file migration refers to the transfer of Console
Configurator files and Page Builder files from the Multibus platform to the
Windows platform.
Up until this point, data has been transferred from the Multibus platform via the
serial interface. Due to limitations within the interface, Environment and Page
Builder files must be transferred across the DCN. In preparation to do so,
1. Connect the Multibus Turbo Node and Windows-based Engineering Station
via a DCN connection.
2. Remove or rename the file [0.BOOT]BOOT.PK on the Multibus Turbo Node
and reboot the Turbo Node with an address that is not 0100 and is also not the
normal Multibus address. This is done so the Multibus Turbo Node will boot
off the Windows-based Engineering Station.
If the Multibus Turbo Node is not at Version 14/5, then you will see an ILLEGAL
INSTRUCTION in Task 89 - RSDISPATCH. This task is not required for the
migration process and you may proceed.
Console/Page Builder File Transfer Utility

This utility allows you to copy either Page Builder graphics or Console environment
files from a given Multibus CDP to an Windows-based Engineering Station on the
same DCN. Note that the Windows-based Engineering Station must have a DCN
address which is not used elsewhere in the system (for example, 0x1100, 0x2100,
… 0xF100).
This utility is intended for the one time transfer of existing data. When you
download Page Builder graphics or Console environment files, the data on the
Multibus CDP will be stored on the Windows-based Engineering Station. If you
have existing Multibus graphics or environments on your Windows-based
Engineering Station, they will be deleted when you download these files from the
Multibus CDP. The transfer of Page Builder graphics and/or Console environment
files from multiple Multibus CDPs is not supported; therefore, if multiple CDPs are
involved, you should consolidate data on one CDP before doing the download.
102 3BUR002065R3501
Appendix D Serial Data Transfers Environment and Graphic File Migration from Multibus to
It is recommended that you do not use this utility while using the system for
production.
To run the file transfer utility:

1. Open up a bugs window on the Windows-based Engineering Station.
2. Press <ESC> to get the bugs prompt.
3. To start the utility, enter:
DP L749
and press <Return>.
Once the utility is started, the menu shown is displayed.
Q: QUIT
ENTER SELECTION:
4. To exit bugs, enter
EX
and press <Return>.
5. Press either P to download Page Builder graphic files, C to download console
environment files, or Q to quit the utility.
If you are downloading Page Builder graphics, you are prompted as follows:
ALL EXISTING GRAPHICS WILL BE DELETED, OK? (Y OR N)
ENTER Y OR N
If you are downloading Console environment files, you are prompted as
follows:
3BUR002065R3501 103
Environment and Graphic File Migration from Multibus to Windows Appendix D Serial Data
ALL EXISTING CONSOLE ENVIRONMENTS WILL BE DELETED, OK?

(Y OR N)
ENTER Y OR N
7. Press Y to delete all existing files.
To confirm deletion of all existing files, you are prompted to enter Y or N
again.
8. Press Y to confirm deletion of all existing files.
The utility then proceeds to delete all existing files of the selected type before
starting the file transfer.
Once the transfer is started, a message indicating the progress of the transfer is
displayed.
Once the transfer is complete, a message indicating if any errors were
encountered is displayed and you are prompted to press any key to continue.
9. Press any key to continue.
This returns you to the main menu. At this point, you can either perform
another transfer or quit.
If errors were encountered during the transfer, you should look at the log file to
find out what the errors were. To look at the log file, enter:
VI [170.CONVERT]PBCODNLD.LG ;”
and press <Return>.
To return to the bugs prompt from the log file, press the period (.) key.
To exit bugs, enter
EX
and press <Return>.
104 3BUR002065R3501
INDEX
A all files of Ladder Logic directories in HP-UX
AddRCSInfo 28, 33, 42, 81, 93, 100 FMS format to Windows FMS format via
addresses for which timeout value must be fmsConvert 36
changed 83 all memory pool configuration files in HP-UX
annotate_.dmp file 58 FMS format to Windows FMS format via
annotation text migration from HP-UX to fmsConvert 37
Windows 27, 51, 55 all PLC Config files in HP-UX FMS format to
ASCII transition file to binary transition file Windows FMS format via fmsConvert 37
conversion via Save ATF 63 ASCII transition file to binary transition file
using conversion utility of Save ATF 63
B binary transition file to ASCII transition file
binary transition file to ASCII transition file using BTFtoATF utility 24, 77
conversion via BTFtoATF utility 24, 77 Console Configurator files in HP-UX FMS
BTFtoATF utility 24, 77 format to Windows FMS format via
fmsConvert 36
HP binary transition file to Windows binary
C
transition file via fmsConvert 21
checking in extracted sequence and recipe text files
Ladder Logic library files in HP-UX FMS
to RCS of 2000 TCL Builder Server 42
format to Windows FMS format via
checking in extracted sequence and recipe text files
fmsConvert 37
to RCS of Windows TCL Builder Server 34, 94,
Page Builder files in HP-UX FMS format to
100
Windows FMS format via fmsConvert 35
checking log file for errors 27, 55, 60, 68, 81
TCL sequence and recipe files in HP-UX FMS
CIFileUpld, transferring Multibus files
PLC 100
fmsConvert 29
TLL 98
Windows binary transition file to HP-UX
transition file 76
binary transition file via fmsHPConvert 64
comment migration 51
creating
Console Configurator file migration
project on Windows-based Engineering
from HP-UX to Windows 35
Station 25, 78
from Multibus to Windows 102
target directories for FMS user data files
Console/Page Builder File Transfer utility 102
migrated 37
converting
target Ladder Logic directories for FMS user
all files of ENV# directories in HP-UX FMS
data files migrated 38
target Page Builder and ENV# directories for
fmsConvert 36
3BUR002065R3501 105
Index
FMS user data files migrated 38 format 37

converting all PLC Config files in HP-UX FMS
D format to Windows FMS format 37
database comment migration from HP-UX to converting Console Configurator files in HP-
Windows 27, 51 UX FMS format to Windows FMS
database migration format 36
from HP-UX to Windows 18, 20 converting HP binary transition file to
from Multibus to Windows 71 to 72 Windows binary transition file 21
from Windows to HP-UX 62 converting Ladder Logic library files in HP-
DCN 11 UX FMS format to Windows FMS
DCN File Transfer Utility 43 format 37
decompiling direct recipes to source 29, 82 converting Page Builder files in HP-UX FMS
deleting FMS sequence and recipe files from format to Windows FMS format 35
RECIPE, RECIPESR, and TCL directories 86 converting TCL sequence and recipe files in
downloading TCL sequences and recipes to HP-UX FMS format to Windows FMS
FMS 29 format 29
fmsHPConvert 64
E ftp
environment and graphic file migration from mgetting converted Console Configurator
Multibus to Windows 102 files 39
export_hp_annotate.sh script file 55 mgetting converted ENV# files 40
extracting mgetting converted Ladder Logic files 40
transferred FMS files to text file format via mgetting converted Ladder Logic library
TCL Migration utility 32 files 40
uploaded FMS files to text file format via TCL mgetting converted memory pool configuration
Migration utility 92 files 41
mgetting converted Page Builder files 39
mgetting converted PLC configuration files 41
F
mgetting converted TCL recipe files 31
FMS user data file migration
mgetting converted TCL sequence files 31
using to get binary transition file 23
from Multibus to Windows 94 to 95
using to put binary transition file 66
fmsConvert
converting all files of ENV# directories in HP-
UX FMS format to Windows FMS G
format 36 get_comments_on_hp.sql script file 51
converting all files of Ladder Logic directories getting
in HP-UX FMS format to Windows FMS binary transition file via ftp 23
format 36 converted files via ftp 30
converting all memory pool configuration files
in HP-UX FMS format to Windows FMS
106 3BUR002065R3501
Index
H Windows 102
HP binary transition file to Windows binary database comments from HP-UX to
transition file conversion 21 Windows 27, 51
database from HP-UX to Windows 18, 20
I database from Multibus to Windows 71 to 72
import_nt_annotate.bat batch file 59 database from Windows to HP-UX 62
importing annotate_.dmp file via environment and graphic files from Multibus to
import_nt_annotate.bat batch file 59 Windows 102
inserting MOD_DB templet into new project 79 FMS user data files from HP-UX to
Windows 35
FMS user data files from Multibus to
L
Windows 94 to 95
loading
memory pool configuration files from HP-UX
ASCII transition file 26, 80
to Windows 35
binary transition file 67
Page Builder files from HP-UX to
transition file via Load ATF 26, 80
Windows 35
logging in to Control Builder and opening
Page Builder files from Multibus to
project 26
Windows 102
PLC configuration files from HP-UX to
M Windows 35
memory pool configuration file migration TCL sequence and recipe source files from HP-
from HP-UX to Windows 35 UX to Windows 28
mgetting TCL sequence and recipe source files from
converted Console Configurator files via Multibus to Windows 81
ftp 39 TCL source files from HP-UX to Windows 29
converted ENV# files via ftp 40 TCL source files from Multibus to
converted Ladder Logic files via ftp 40 Windows 81
converted Ladder Logic library files via ftp 40 TLL files from HP-UX to Windows 35
converted memory pool configuration files via modifying CIGATE.PK file 82
ftp 41
converted Page Builder files via ftp 39
P
converted PLC configuration files via ftp 41
Page Builder file migration
converted TCL recipe files via ftp 31
converted TCL sequence files via ftp 31
migrating
PLC configuration file migration from HP-UX to
annotation text from HP-UX to Windows 27,
Windows 35
51, 55
putting binary transition file on HP-UX via ftp 66
comments from HP-UX to Windows 51
Console Configurator files from HP-UX to
Windows 35 R
Console Configurator files from Multibus to RCS, see revision control system
3BUR002065R3501 107
Index
retrieving U
annotation text from HP-UX to Windows via update_nt_comments_.sql script file 53
export_hp_annotate.sh script 57 updating
comment data from HP-UX to Windows via project on Windows by importing
get_comments_on_hp.sql script 52 annotate_.dmp file 59
revision control system 34, 42, 94, 100 project on Windows with comment data via
update_nt_comments_.sql script file 54
S uploading TCL sequence and recipe files in FMS
saving database as transition file 20, 62, 72 format from Multibus to Windows TCL Builder
SetNotCompiled executable 32, 92 Server 89
setting status for transferred FMS sequence and using
recipe files to “Not Compiled.” via ftp to get binary transition file 23
SetNotCompiled executable 32, 92 ftp to put binary transition file 66
T V
TCL Migration utility 32, 92 verifying
TCL sequence and recipe source file migration annotation text was updated in migrated
from HP-UX to Windows 28 project 60
from Multibus to Windows 81 comments were updated in migrated
TCL source file migration project 55
TCLMultibusMigration.bat batch program 89
Telnet message box 53, 58
testing serial connection between Multibus and
Windows 73, 86, 95
TLL file migration from HP-UX to Windows 35
transferring
memory pool configuration files on Multibus to
Windows 101
PLC configuration files on Multibus to
Windows via CIFileUpld 100
TLL files on Multibus to Windows via
CIFileUpld 98
transition file to Windows via CIFileUpld 76
transition file
loading via Load ATF 26, 80
saving database 20, 62, 72
transferring to Windows via CIFileUpld 76
108 3BUR002065R3501
3BUR002065R3501 Litho in U.S.A. December 2009
Copyright © 2009 by ABB. All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.
http://www.abb.com
Automation Technology Products Automation Technology Products Automation Technology Products

Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
www.abb.com/controlsystems www.abb.com/controlsystems www.abb.de/controlsystems

3BUR002065R3501 A en AdvaBuild Version 3.5 Migration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3BUR002065R3501 A en AdvaBuild Version 3.5 Migration Guide

Uploaded by

Copyright:

Available Formats

AdvaBuild®

Copyright © 2009 by ABB

Release: December 2009

About This Book

Appendix A - Additional HP-UX to Windows Migration

Appendix B - Data Transfer From Windows to HP-UX Platform

Appendix C - Revision Control Tools

Appendix D - Serial Data Transfers

Environment and Graphic File Migration from Multibus to Windows..............102

Use of Warning, Caution, Information, and Tip

Caution indicates important information or warning related to the concept

Information alerts the reader to pertinent facts and conditions.

value out of range, the following message is displayed:

Table 1. Related Documentation

Category Title Description

Table 1. Related Documentation (Continued)

Category Title Description

Prerequisites and Requirements

Migration from HP-UX to Windows

Preparation Before Migration from HP-UX to Windows

6. At the ftp> prompt, change to the following directory by entering:

Database Migration from HP-UX to Windows

Overview of Database Migration

7. Load the transition file.

Procedure for Migration of a Database

Click on OK to acknowledge. If necessary, take steps to correct the error.

<eng55:ocsmgr> fmsConvert $FMSPATH/WC00/50/DBASE

Running hptont on files in /tmp/fmsconvert/WC00/50/DBASE...

Copying back original ctree index files...

Running ctree conversion on files in /tmp/fmsconvert/WC00/50/DBASE...

Conversion of files from /home/opt/advant/FMS/WC00/50/DBASE completed.

Converted files will be found in /tmp/fmsconvert/WC00/50/DBASE.

Enter the transition file name in all uppercase characters.

C:\>btftoatf WC00:[50.DBASE]TURBO.DT.1 TURBO.txt

c. Close the Command Prompt window by entering exit at the command

Figure 1. Insert Project Dialog

e. Click OK to close the Insert Project Completion dialog.

Figure 2. Load ASCII Transition File Dialog

Figure 3. Open Transition File Dialog

TCL File Migration from HP-UX to Windows

Overview of TCL File Migration

Procedure for Migration of TCL Source Files in FMS Format

The converted files will be located in

f. At the ftp> prompt, enter:

Once transfer of the recipe file(s) is complete, a message indicating

Figure 4. TCL Migration Dialog

FMS User Data File Migration from HP-UX to Windows

Overview of FMS User Data Files Migration

Procedure for Migration of FMS User Data Files

b. At the command prompt, change directories using the command below:

Using File Migration Utility for Multibus to Windows

DCN File Transfer Utility

TRANSFERRING RECORD x OF 43 FOR WC00:[50.DBASE]T1-AVG1.DT

Records Transferred (Approx): 2812

DOWNLOAD COMPLETED WITH NO ERRORS

PRESS ANY KEY TO CONTINUE

Create Ladder Logic File List

Transfer TLL Files

TRANSFERRING RECORD x OF 43 FOR WC00:[20556.AC1-LL ]1.ID

TRANSFERRING RECORD x OF 39 FOR WC00:[20556.AC1-LL ]2.SR

Records Transferred (Approx): 286

DOWNLOAD COMPLETED WITH NO ERRORS

PRESS ANY KEY TO CONTINUE

Start of FMS File Convert Log File