B0400QD

REV A

I/A Series A2™ System

V7.0 Upgrade Considerations
December 2, 2002

Model P79
Workstation for Unix

Model P80
Workstation for Unix

Model P92
Workstation for Windows
Invensys, AIM*AT, AIM*Historian, Command Center, Fox, FoxAMI, FoxAPI, Foxboro, FoxCAE, FoxCom,
FoxDraw, FoxView, I/A Series, I/A Series A2, INTERSPEC, Micro-I/A, and SPECTRUM are trademarks of
Invensys plc, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.

Copyright 2002 Invensys Systems, Inc.

All rights reserved
Contents
Tables.................................................................................................................................... vii

Preface.................................................................................................................................... ix
50 Series and 70 Series Conventions ........................................................................................ ix
Naming Conventions for UNIX Workstations ..................................................................... x
Naming Conventions for Windows Workstations ................................................................ x
Revision Information ................................................................................................................ x
Reference Documents ............................................................................................................... x

1. Introduction ...................................................................................................................... 1

2. Interoperability Issues ....................................................................................................... 3

2.1 General ............................................................................................................................... 3
2.1.1 Network Fault Detection (NFD) ................................................................................ 3
2.1.2 Carrierband LAN I/F Software .................................................................................... 3
2.1.3 Compound Summary Access (CSA) ............................................................................ 4
2.1.4 EEPROM Software ..................................................................................................... 4
2.1.5 System Management Display Handler ......................................................................... 5
2.1.6 Mixed Version Configurations Require Two Commit Diskettes ................................. 5

3. Hardware Requirements (UNIX Platform)........................................................................ 7

3.1 Supported Hardware ........................................................................................................... 7
3.2 Hard Drive and RAM Size Requirements for V7.0 ............................................................. 7
3.2.1 Memory Upgrade Kits ................................................................................................. 8
3.2.2 NVRAM and Replaceable Battery Kits ........................................................................ 8
3.3 Peripheral Requirements for 50 Series Workstations ........................................................... 9

4. Hardware Requirements (Windows Platform)................................................................. 11

4.1 Hard Drive Minimum Size Requirement for V7.0 ............................................................ 11

5. Software .......................................................................................................................... 13
5.1 Standard Applications ....................................................................................................... 13
5.1.1 Compound Summary Access (CSA) .......................................................................... 13
5.1.1.1 Backing Up CSA (CSA_Save) ........................................................................... 13
5.1.1.2 Restoring CSA (CSA_Merge) on 50/70 Series Stations ...................................... 14
5.1.1.3 Moving CSA Between 50/70 Series Stations ...................................................... 15
5.1.1.4 Moving CSA from Intel to 50 Series Stations .................................................... 16
5.2 Workstation Software ........................................................................................................ 17
5.2.1 Conversions and Update Procedures ......................................................................... 17
5.2.1.1 Display Conversion ........................................................................................... 17
5.2.1.2 Caution About Display Conversion ................................................................... 18

iii
B0400QD – Rev A Contents

5.2.1.3 Common Alarm Group Configuration .............................................................. 18

5.2.1.4 Alarm Configuration File Propagation ............................................................... 18
5.2.1.5 Modifying Alarm Horn Configuration .............................................................. 18
5.2.1.6 Converting Intel Fonts and Markers to 50 Series Format .................................. 18
5.2.2 FoxView Software ..................................................................................................... 19
5.2.2.1 FoxView and FoxDraw Software ....................................................................... 19
5.2.3 Screensavers ............................................................................................................... 19
5.3 Application Packages ......................................................................................................... 19
5.3.1 Historian ................................................................................................................... 19
5.3.1.1 Configuring “Backup your Historian Archive” Message .................................... 19
5.3.2 FoxAPI Software ....................................................................................................... 19
5.3.2.1 Determining the Version of FoxAPI Software .................................................... 19

6. I/A Series Electronic Documentation .............................................................................. 21

6.1 Hardware Requirements .................................................................................................... 21
6.2 Software Requirements ...................................................................................................... 22
6.3 Uninstalling Previous Versions of I/A Series Electronic Documentation ........................... 22
6.3.1 Removing Updated Files ........................................................................................... 22
6.3.2 Stopping the I/A Series Documentation Server .......................................................... 23
6.3.3 Uninstalling the I/A Series Electronic Documentation Application ........................... 23
6.4 Installing I/A Series Electronic Documentation ................................................................. 24
6.4.1 Starting I/A Series Electronic Documentation ........................................................... 25
6.4.2 Browsing the User Documentation ........................................................................... 25
6.5 Searching I/A Series Electronic Documentation ................................................................ 25
6.5.1 Set up Preferences for Searching ................................................................................ 25
6.5.2 Add the I/A Series K0173TQ-L Search Index ........................................................... 26
6.5.3 Search ........................................................................................................................ 26
6.5.4 Advanced Search ....................................................................................................... 27

7. Preinstallation Considerations......................................................................................... 29
7.1 Backing Up Hard Disks .................................................................................................... 29
7.1.1 Pre-V7.0 50 Series Workstations ............................................................................... 29
7.1.2 Pre-V7.0 70 Series Workstations ............................................................................... 29
7.2 Saving Control Databases (SaveAlls) ................................................................................. 29
7.3 Backing Up CSA Files ....................................................................................................... 30
7.4 Backing Up Files ............................................................................................................... 30
7.4.1 Saving Invensys Foxboro Application Databases ........................................................ 30
7.4.1.1 Saving Historian Database (Model 51F/G) ........................................................ 30
7.4.1.2 Saving AIM*Historian Database ........................................................................ 30
7.4.2 User Applications and Third-Party Package Files ....................................................... 30
7.4.2.1 Uninstalling Select Packages with Single Station Licensing (AW70) .................. 31
7.4.2.2 Backing Up Display Files ................................................................................... 31
7.5 Checking the LONG_S Parameter .................................................................................... 31

8. Installation Considerations.............................................................................................. 33
8.1 Software Installation (UNIX Systems Only) ...................................................................... 33
8.1.1 Printer Message ex_fetch ........................................................................................... 33

iv
Contents B0400QD – Rev A

8.1.2 Software Install – Assign Peripheral Device Utility .................................................... 33

9. Postinstallation Considerations (UNIX Systems) ............................................................ 35

9.1 Real-Time Trends Not Displaying Recent Historical Data ............................................... 35
9.1.1 Restoring the Historian Database (AP51/AW51) ...................................................... 35
9.2 “Auto-revarp failed” Recovery at Boot Time ..................................................................... 35
9.3 Annunciator Keyboards Off-Line After Power Up ............................................................ 36
9.4 User Application Software Startup .................................................................................... 36
9.5 Converting a Customized Color Palette ............................................................................ 37
9.6 FBM Firmware Upgrade Messages .................................................................................... 38

Appendix A. Time Estimation for Migration to V7.0 Platforms.......................................... 39

A.1 Preinstallation ................................................................................................................... 39
A.2 Installation ........................................................................................................................ 40
A.3 Postinstallation ................................................................................................................. 40

Appendix B. Files to Back Up/Restore................................................................................. 41

B.1 Saving Files ....................................................................................................................... 41
B.2 Files to Back Up/Restore for Day 0 Migration .................................................................. 41
B.2.1 Application Databases ............................................................................................... 41
B.2.2 Display-Related Files ................................................................................................. 43
B.2.3 System-Related Files ................................................................................................. 44

Appendix C. EEPROM Revision Levels .............................................................................. 47

C.1 Firmware Upgrade ............................................................................................................ 52
C.2 Determining EEPROM Version ...................................................................................... 52
C.3 Performing EEPROM Update ......................................................................................... 53

v
B0400QD – Rev A Contents

vi
Tables
3-1. V7.0 Hard Drive and RAM Sizes .................................................................................. 7
3-2. Memory Upgrade Kits for 50 Series Stations ................................................................. 8
4-1. V7.0 Hard Drive and RAM Sizes ................................................................................ 11
C-1. Control Stations .......................................................................................................... 47
C-2. Communication Stations ............................................................................................ 48
C-3. Miscellaneous EEPROM Revision Levels .................................................................... 48
C-4. 100 Series FBMs (Y Form Factor) ............................................................................... 49
C-5. 200 Series FBMs (DIN Rail Mounted FBMs) and FCMs ........................................... 51

vii
B0400QD – Rev A Tables

viii
Preface
This document contains considerations for installing I/A Series software V7.0. Read all sections
before beginning the V7.0 installation process.
This document assumes that you have carefully reviewed V7.0 Read Me First (B0400QC), which
contains a release overview and considerations for migrating to a V7.0 system.

50 Series and 70 Series Conventions

Traditional I/A Series naming conventions for workstations and application servers has been to
label operator interface stations as Workstation Processors (WPs), application servers as Applica-
tion Processors (APs), and combined operator and application server stations as Application
Workstations (AWs).
Different generations of UNIX® workstations, typically referred to as 50 Series products, have
used a letter suffix to differentiate newer generations of product (for example, 51D and 51E).
Different generations of the Windows® based workstations are typically referred to as 70 Series
workstations. Manufacturing data labels on the back of the hardware have manufacturing
Style/Revision codes used to identify minor differences, such as disk size, within a workstation
generation. For both platforms, the AW or WP designation has been used interchangeably to
name the hardware, software and respective licenses associated with a particular workstation.
With this release, new workstation hardware, software, and licenses have separate designations as
follows:
1. Hardware has a Model designation, similar to AW and WP P-Codes, as follows:
♦ Model P79 Workstation for UNIX (newer product that is functionally similar to
the Model 51D)
♦ Model P80 Workstation for UNIX (newer product that is functionally similar to
the Model 51E)
♦ Model P92 Workstation for Windows (newer product that is functionally similar
to the P93, P97, P98, and P99).
2. Software licenses for workstations now use an S-code designation for a suite of soft-
ware selections. These new model coded licenses are similar to the hardware P-code
structure instead of the traditional AW, WP, or AP station licenses. The following
suites have selectable software license options and are used in combination on each
workstation:
♦ S01 Base Workstation Suite
♦ S02 Visualization Suite
♦ S03 Engineering Suite.
The new model coded licenses substitute for the old 7-character part numbers of the
former AW and WP licenses, both on Solaris® and Windows.
3. Software media has separate media part numbers and identified by platform and
version.

ix
B0400QD – Rev A Preface

This new structure provides additional flexibility in hardware software and licensing selections to
better match application requirements. Through appropriate hardware, software, and S-code
license selections, the traditional AW and WP capabilities are still available.
This document includes both newly released products and previous generations of products. Since
both products can coexist in a system, traditional references using earlier naming conventions (for
example, AW, WP, 50 Series, and 70 Series) have been used in many places as a convenient way to
describe product capabilities that transcend the new naming conventions. Note however that
where this occurs for the new workstations listed above, the new product structure is implied. The
following subsections contain specifics of the naming conventions for this document.

Naming Conventions for UNIX Workstations

Where reference is made to the 50 Series, the information applies to all styles of Model 51 sta-
tions, including the new Model 51F and Model 51G workstations.
The Model 51F workstation is also designated the “P79” workstation in user documentation asso-
ciated with this release. “Model 51F” (or “the P79”) workstation can refer to either the AW with
or without control, WP, or AP capability, unless explicitly specified as an AW51F, AW51FX,
WP51F, or AP51F (where the “FX” notation refers to the Model 51F application workstation
with control capability).
The Model 51G workstation is also designated the “P80” workstation in user documentation
associated with this release. “Model 51G” (or “the P80”) workstation refers to the AW capability
(with or without control), unless explicitly specified as an AW51G or AW51GX (where the “GX”
notation refers to the Model 51G application workstation with control capability).

Naming Conventions for Windows Workstations

Where reference is made to the 70 Series, the information applies to all styles of 70 Series stations,
including the new Model 70P workstations.
The Model 70P workstation is also designated the “P92” workstation in user documentation asso-
ciated with this release. “Model 70P” (or “the P92”) workstation can refer to either the AW with
or without control, or WP capability, unless explicitly specified as an AW70P or AW70CP (where
the “CP” notation refers to the Model 70P workstation with control capability).

Revision Information
This is the initial version of this document.

Reference Documents
For more information, refer to the following documents located on the I/A Series® Electronic
Documentation CD-ROM or on the Customer Satisfaction Center’s website:

Document Title Part Number

® ®
Application Workstation 70 with Allen-Bradley PLCs (Windows NT B0400AL
Operating System)
Color Printer Installation for V4.3.x, V6.1.x, V6.2.x, V6.3, and V6.4 B0400SF

x
Preface B0400QD – Rev A

Document Title Part Number

Command Center™ Installation Manual B0193RZ
Control Network Architecture PSS 21H-7C1-B3
Control Processor 60 (CP60) Sizing Guidelines and Excel Workbook B0400BK
Device Integration Using I/O Gates B0193VG
Display Engineering for 50 Series Workstations B0193MQ
Dual-Height Modular Mounting Structure (2xMMS) Mounting Hardware B0400PA
Installation
Field Automation Subsystem Micro-I/A® Station User’s Guide B0193VJ
Fieldbus Cluster I/O User’s Guide B0193RB
Flat Panel Monitor Software Setup for UNIX and Windows Workstations B0193PL
FoxCAE™ 5.0 Release Notes B0400PY
FoxDraw™ B0193WG
FoxView™ and FoxDraw V8.0 Release Notes B0193WL
FoxView and FoxDraw V8.0.2 Release Notes Addendum K0176AB
FoxView B0193WH
Hardware and Software Specific Instructions for Model P92*A Workstation B0400HD
(PW340)
Hardware Installation Procedures for Model P79 Workstation (Solaris 8 B0400SR
Operating System)
Hardware Installation Procedures for Model P80 Workstation (Solaris 8 B0400SS
Operating System)
HART® Communication Interface Modules (FBM214/215/216/218) B0400FF
User’s Guide
I/A Series A2™ High Performance System Network User’s Guide B0400DV
Information Suite AIM*Historian™ User’s Guide B0193YL
Installation Instructions for Control Processor 30, Style B and Control B0400SD
Processor 40, Style B
Installation Instructions for A to L Size Modules B0193TF
Integrated Control Block Descriptions B0193AX
Integrated Control Concepts B0193AW
Integrated Control Configurator B0193AV
Intelligent Field Device Configurator (IFDC) MI 020-495-C
Intelligent Field Device Configurator (IFDC) Table of Contents B0400QK
Intelligent Field Device Configurator (IFDC) Version 2.3 Release Notes B0400QL
Micro-I/A Station Hardware Installation Quick Set-Up Guide B0199AB
Model P79 Workstation for UNIX Solaris 8 Operating System PSS 21H-4R7 B4
Model P80 Workstation for UNIX Solaris 8 Operating System PSS 21H-4R8 B4
Model P92 Workstation for Windows (Windows XP Operating System) PSS 21H-4D13 B4
Modular Industrial Console Installation B0193UV
Modular Industrial Workstation Installation B0193CE

xi
B0400QD – Rev A Preface

Document Title Part Number

Nodebus/Control Network Interface (NCNI) PSS 21H-7B5 B4
Process Operations and Displays B0193MM
PROFIBUS-DP™ Communication Interface Module (FBM223) User’s Guide B0400FE
Redundant Array of Independent Disks PSS 21H-3E2 B4
Redundant Control Network Interface (RCNI) PSS 21H-7B6 B4
Site Planning B0193AB
Software Installation (Solaris® Platform) B0193JG
SPECTRUM™ Migration Integrator User’s Guide B0193RC
System Administration Guide (Solaris 8 Operating System) B0400DU
System Administration Guide (Windows NT Operating System) B0400ND
System Administration Guide (Windows XP Operating System) B0400HE
System Definition 2.4 Release Notes B0193XW
System Definition: A Step-By-Step Procedure B0193WQ
System Equipment Installation B0193AC
System Maintenance B0193AD
System Management Displays B0193JC
System Planning and Sizing B0193BF
UNIX and Windows Workstations Instructions for MIC, MIW, B0400PL
IEMFA/IEMFR (ME24/32) and IE32 Installation
V7.0 Table of Contents B0400QB
V7.0 Read Me First B0400QC
V7.0 Installation Procedures B0400QE
V7.0 Enhancements and Problems Resolved B0400QF
V7.0 Operational Recommendations B0400QG
V7.0 Release Features and Configurations B0400QH
Winchester Systems FlashDisk® RAID 1 and RAID 5 Instructions B0193RT

The following and additional documents are available on the Sun Microsystems web site at
http://www.sun.com.
♦ Sun Blade™ 150 Service Manual (part number 816-4379-10)
♦ Sun Blade 150 DIMM Installation Guide (part number 816-5370-10)
♦ Sun Blade 150 Getting Started Guide (part number 816-1161-10)
♦ Sun Blade1000 and Sun Blade 2000 Getting Started Guide (part number
816-3216-10)
♦ Sun Blade 1000 and Sun Blade 2000 Service Manual (part number 816-3217-10).
♦ 20/40 Gbyte 4 mm DDS-4 Tape Drive Installation and User’s Guide (part number
802-7791-11).

xii
1. Introduction
This document contains I/A Series V7.0 software installation and migration considerations.
The V7.0 release allows you to connect a high-bandwidth I/A Series A2 control network, includ-
ing your new Model 51F, Model 51G, and/or Model 70P workstations and associated new equip-
ment, to an existing Nodebus.
Read all sections of this document before beginning the software installation process. The follow-
ing chapters detail requirements for a migration to V7.0, including such topics as software version
interoperability, hardware and software requirements, and other subjects that you must consider
prior to, during, and after a migration to V7.0. This document assumes that you have carefully
reviewed the V7.0 Read Me First (B0400QC) and the High Performance System Network User’s
Guide (B0400DV) to understand how a migration to V7.0 impacts your current configuration.
To plan for the time required for your V7.0 Day 0 installations, refer to Appendix A “Time Esti-
mation for Migration to V7.0 Platforms”.
For interoperability requirements, review Chapter 2 “Interoperability Issues”.

1
B0400QD – Rev A 1. Introduction

2
2. Interoperability Issues
This section is a summary of the interoperability issues you might encounter as you install V7.0
software on your system. Read it to plan your migration accordingly.

2.1 General
A new V7.0 workstation can interoperate with both V6.3 and V6.4 workstations, and can coexist
with V4.3/V6.1 and V6.2 workstations. When involved with stations running V6.3 or V6.4 soft-
ware, consult the release documentation of that release to locate conversion procedures, notes
concerning migration to the Version 6.x release, and so forth.
Generally, an older workstation can host a newer CP image but a newer workstation cannot host
an older CP image. For example, a V6.3 workstation can host a V6.4 CP, but a V6.4 workstation
cannot host a V6.3 CP. However, a V7.0 workstation can host a V6.4 CP, since V6.4 is the latest
version of control, and V6.4 control images are included with V7.0 software.
When an older workstation hosts a newer CP image, the system support for the CP is at the
release level of the older workstation. For example, if a V6.3 workstation hosts a V6.4 CP, system
configuration support for the V6.4 CP is only at the V6.3 level.
Style A CPs and gateways that are boot hosted by a V7.0 workstations do not have the ability to
generate dump files.

2.1.1 Network Fault Detection (NFD)

It is highly recommended that you select a V7.0 AW or AP as the Nodebus Test Initiator on every
node that contains a mix of V6.x and V7.0 workstations. The workstation selected as Nodebus
Test Initiator defaults to a V7.0 workstation, unless overridden by an operator. Every node that
contains V7.0 workstation must have at least one V7.0 AW or V7.0 AP installed, since a WP can-
not be selected as a Nodebus Test Initiator.

2.1.2 Carrierband LAN I/F Software

The Carrierband LAN I/F (CLAN) software released with V6.4 contains enhanced diagnostics.
This fix does not increase the throughput of CLANs for V6.4 or later software. Coaxial and fiber
optic CLANs are capable of routing 300 packets/second sustained, however, the recommendation
is that the average level be less than 220 packets/second to allow for plant upsets (alarm messages)
and dynamic changes in the process which can increase traffic.
No interoperability issues exist between CLANs running V7.0 image software and any of the
following:
♦ V6.3 image, released with V6.3
♦ V6.4 image, released with V6.4.

3
B0400QD – Rev A 2. Interoperability Issues

NOTE
1. Review all peer-to-peer connections maintained through the CLAN network
prior to rebooting. Rebooting the CLAN modules causes a temporary loss of
peer-to-peer connections, which might cause a plant upset.
2. When sequence blocks perform SENDCONFIRM or related operations to a
device or object residing in another node, the blocks might go to INACTIVE
and might transition to MANUAL if booting the CLAN prevents completion of
write/read operations. There might not be an alarm to alert you when this
happens.

2.1.3 Compound Summary Access (CSA)

CSA must exist on a V6.4 or later host station before you upgrade control stations. This might
require moving CSA, if only temporarily, to support the upgrade.

! CAUTION
CSA can only reside in one station in your configuration.

You must back up the CSA files if your installation will consist of mixed-version stations (that is,
combinations of V6.3 or V6.4 and V7.0) after the upgrade is complete, and your current CSA
host station is installed with pre-V7.0 software.
You do not need to back up the CSA files if your entire system is migrating to V7.0 (that is, if
your configuration will only consist of V7.0 workstations and associated equipment and
software).
When you back up, upgrade, or move CSA, you must use the CSA_Save and CSA_Merge utilities.
For instructions on using the CSA_Save and CSA_Merge utilities, see “Compound Summary
Access (CSA)” on page 13 in Chapter 5 “Software”.

NOTE
Do not use other methods of backing up and restoring CSA database files, such as
tar’ing the data files from/to the /opt/fox/csa directory.

If you must move CSA from another station, move it and then verify proper functionality before
beginning the upgrade. See “Moving CSA Between 50/70 Series Stations” on page 15 or “Moving
CSA from Intel to 50 Series Stations” on page 16. This precaution ensures that, if you must abort
the V7.0 upgrade, restoring the old drive also restores CSA functionality.

2.1.4 EEPROM Software

Upgraded EEPROM software files exist on V7.0 hosts. See Appendix C “EEPROM Revision
Levels”.

4
2. Interoperability Issues B0400QD – Rev A

2.1.5 System Management Display Handler

Do not attempt to perform maintenance operations using versions of SMDH released before the
target equipment was introduced. For example, use only V6.4 or V7.0 SMDH for Hart and
PROFIBUS-DP operations, since Hart and Profibus equipment was introduced in V6.4.
SMDH that is running on a V7.0 workstation can access all the features of the devices that were
introduced before V7.0, and SMDH running on an pre-V7.0 workstation can view equipment
that is running at V7.0, but is unable to access the new V7.0 features and devices.

2.1.6 Mixed Version Configurations Require Two Commit

Diskettes
You must use System Definition V2.4 to create, import and/or edit your configuration, and to
create a Commit diskette.
All Commit diskettes must be produced using the Day 0 version of Media Distribution diskettes.
Media Distribution diskettes distributed for release updates cannot be used to produce Commit
diskettes.
Mixed version systems require a separate Commit diskette for use on V6.3, V6.4, and V7.0
stations. Use:
♦ The V6.2 Media Distribution Diskette (K0175TA) supplied with V6.2 media kits to
produce the V6.3 Commit diskette.
♦ The V6.4 Media Distribution Diskette (K0175XE) supplied with V6.4 media kits to
produce the V6.4 Commit diskette.
♦ The V7.0 Media Distribution Diskette (K0175YP) supplied with V7.0 media kits to
produce the V7.0 Commit diskette.

NOTE
1. The V6.3 Commit diskette is only required when you are adding new
equipment and/or making changes to your system configuration.
2. For mixed version systems, be sure to label each Commit diskette with the
I/A Series versions on which it can be used, for example, V6.3, V6.4, or V7.0.

5
B0400QD – Rev A 2. Interoperability Issues

6
3. Hardware Requirements (UNIX
Platform)
This chapter describes the hardware requirements to install V7.0.

3.1 Supported Hardware

For information on supported hardware, refer to V7.0 Release Features and Configurations
(B0400QH).

3.2 Hard Drive and RAM Size Requirements for V7.0

You can install I/A Series V7.0 software on the following workstations. The following table lists
hard disk drive and RAM requirements for the new P79 and P80 workstations.

Table 3-1. V7.0 Hard Drive and RAM Sizes

Hardware Model Operating Hard Drive Size RAM

V7.0 Station and P Designation System Control (Minimum) (Minimum)1
AP51F Model 51F (P79) Solaris 8 No 40 GB 128 MB2
WP51F Model 51F (P79) Solaris 8 No 40 GB 128 MB2
AW51F Model 51F (P79) Solaris 8 No 40 GB 128 MB2
AW51G Model 51G (P80) Solaris 8 No 73 GB3 1 GB4
AW51FX Model 51F (P79) Solaris 8 Yes 40 GB 128 MB2
AW51GX Model 51G (P80) Solaris 8 Yes 73 GB3 1 GB4
1.
The sizes listed above represent the recommendation for Solaris 8. Optional software packages, for
example FoxView or AIM*, require additional memory. Refer to the documentation accompanying
optional software for resource requirements.
2.
Optionally expandable to 2 GB RAM. Default configuration is 256 MB.
3.
Optionally expandable to include two 73 GB internal hard drives. Default configuration is one hard
disk drive.
4.
Optionally expandable to 8 GB RAM. Default configuration is 1 GB.

7
B0400QD – Rev A 3. Hardware Requirements (UNIX Platform)

3.2.1 Memory Upgrade Kits

Table 3-2. Memory Upgrade Kits for 50 Series Stations

Description Kit Part Number Installation Instructions

128 MB RAM (1 X 128 MB DIMM) P0972SK B0400SR and Sun™
Upgrade Kit for Model 51 Style F (P79)1 documentation (see below)
512 MB RAM (1 X 512 MB DIMM) P0972SL B0400SR and Sun
Upgrade Kit for Model 51 Style F (P79) documentation (see below)
1 GB RAM (4 X 256 MB DIMMs) Upgrade P0972TH B0400SS and Sun
Kit for Model 51 Style G (P80) documentation (see below)
2 GB RAM (4 X 512 MB DIMMs) Upgrade P0971TJ B0400SS and Sun
Kit for Model 51 Style G (P80) documentation (see below)
4 GB RAM (4 X 1 GB DIMMs) Upgrade P0971TK B0400SS and Sun
Kit for Model 51 Style G (P80) documentation (see below)
1.
The Model P79 Workstation must have at least one dual in-line memory module (DIMM)
installed in slot 1.

For details on memory upgrade kits and memory upgrade implementation considerations for P79
and P80 workstations, refer to the following, as applicable:
♦ Hardware Installation Procedures for Model P79 Workstation (Solaris 8 Operating
System) (B0400SR)
♦ Hardware Installation Procedures for Model P80 Workstation (Solaris 8 Operating
System) (B0400SS)
♦ Sun Blade 150 DIMM Installation Guide (part number 816-5370-10)
♦ Sun Blade 150 Service Manual (part number 816-4379-10)
♦ Sun Blade 1000 and Sun Blade 2000 Service Manual (part number 816-3217-10).

3.2.2 NVRAM and Replaceable Battery Kits

NOTE
Invensys Foxboro recommends that you replace NVRAM processors and/or
replaceable batteries after five years.

To replace the NVRAM processor in the Sun Blade 150 workstation, refer to the Sun Blade 150
Service Manual (part number 816-4379-10). To replace the battery in the Sun Blade 2000 work-
station, refer to the Sun Blade 1000 and Sun Blade 2000 Service Manual (part number
816-3217-10).

8
3. Hardware Requirements (UNIX Platform) B0400QD – Rev A

3.3 Peripheral Requirements for 50 Series

Workstations
For P79 and P80 workstations, it is recommended that you use one of the following optionally
available tape drives to back up the hard disk:
♦ External 20/40 GB DDS-4 tape drive (SCSI device)
♦ External 50/130 GB AIT-2 tape drive (SCSI device).
Since 50 Series stations use CD-ROMs for software installation and the migration process to
V7.0, a tape drive is used only for backup/restore operations and historian archiving.
The P79 workstation is shipped with a CD-ROM drive, and the P80 workstation is shipped with
a DVD-ROM drive.

9
B0400QD – Rev A 3. Hardware Requirements (UNIX Platform)

10
4. Hardware Requirements
(Windows Platform)
This chapter describes the hardware requirements to install V7.0.

4.1 Hard Drive Minimum Size Requirement for V7.0

You can install I/A Series V7.0 software on the following workstations. For more detailed infor-
mation, refer to System Administration Guide (Windows XP Operating System) (B0400HE).

Table 4-1. V7.0 Hard Drive and RAM Sizes

Hardware Model Operating Hard Drive

V7.0 Station and P Designation System Control Size RAM
WP70P Model 70P (P92) Windows XP No 36 GB 256 MB1
AW70P Model 70P (P92) Windows XP No 36 GB 256 MB1
AW70CP Model 70P (P92) Windows XP Yes 36 GB 256 MB1
1.
Optionally expandable to 2 GB ECC RAM.

11
B0400QD – Rev A 4. Hardware Requirements (Windows Platform)

12
5. Software

5.1 Standard Applications

5.1.1 Compound Summary Access (CSA)
NOTE
In the following CSA procedures, keep in mind that the term “50 Series” also
applies to the Model 51F (P79) and Model 51G (P80) workstations, and the term
“70 Series” also applies to the Model 70P (P92) workstations.

CSA must exist on a V6.4 or later host station. Refer to “Compound Summary Access (CSA)” on
page 4 to determine if you need to back up and/or restore your CSA files during the migration to
V7.0.
When you back up, upgrade, or move CSA, you must use the CSA_Save and CSA_Merge utilities,
described in the following subsections.

NOTE
Do not use other methods of backing up and restoring CSA database files, such as
tar’ing the data files from/to the /opt/fox/csa directory.

To perform the CSA operations below, you need to be in a VT100 session or Command prompt
window on the CSA host station.
On 50 Series or AP20 stations, use a WYSE terminal, or start a VT100 session from the SftMnt
pull-down menu.
On 70 Series stations, start up a Command Prompt window, and type the following to get into a
Shell mode:
D:
ncenv
sh

5.1.1.1 Backing Up CSA (CSA_Save)

On the CSA host station, perform CSA_Save to back up the CSA database files.

Intel Station (AP20/PW)

For the Intel CSA_Save procedure you need a formatted, mountable, 3.5-inch diskette (use the
VENIX™ format command).
1. Log into the AP20 from the WYSE terminal.
2. Insert the formatted diskette into drive 0 and save the CSA information. Type:
cd /usr/fox/ulan
CSA_Save

13
B0400QD – Rev A 5. Software

3. Verify the contents of the save file(s). Type the following:

mount /dev/fh0 /f0
ls -l
Verify that each control station has a text file on the diskette.
4. Unmount the diskette and label it. Type:
umount /dev/fh0
This completes the Intel CSA_Save procedure.

50/70 Series Station

NOTE
The CSA_Save operation might fail for individual stations that have compounds
without blocks. When this occurs, remove the empty compound, using the Inte-
grated Control Configurator, and retry the CSA_Save operation.

1. Back up the CSA database files. Before performing this operation, consider the
following:
♦ An empty directory must be available for the CSA_Save operation. The
(CSA_Save) operation might fail for stations for which a file already exists.
♦For drive space requirements, assume that you need 15 KB of space per control
station. Use the df command to check available drive space in the /usr partition.
2. Type the following:
cd /usr/fox/csa
mkdir save
CSA_Save ./save
This saves the CSA files in the /usr/fox/csa/save directory. There is one text file for
each control station.
3. Verify the contents of the save file(s). Type the following:
cd /usr/fox/csa/save
ls -l
Verify that each control station has a text file in this directory.
4. tar the files onto a diskette. Type the following:
cd /usr/fox/csa/save
tar cvf /dev/fd0 * (50 Series)
tar cvf a: * (70 Series)

5.1.1.2 Restoring CSA (CSA_Merge) on 50/70 Series Stations

1. Extract the CSA files from the diskette produced by the CSA backup procedure.
Insert the diskette and type the following:
mkdir /usr/fox/csa/save
cd /usr/fox/csa/save
tar xvf /dev/fd0 (50 Series)
tar xvf a: * (70 Series)

14
5. Software B0400QD – Rev A

2. Restore the CSA database. Type the following:

cd /usr/fox/csa
CSA_Merge ./save
3. You can remove the CSA text files at this time to recover drive space. Type:
rm -r /usr/fox/csa/save

5.1.1.3 Moving CSA Between 50/70 Series Stations

NOTE
The CSA_Save operation might fail for individual stations that have compounds
without blocks.

It is recommended that this procedure be performed only by qualified Invensys Foxboro

personnel.
1. Back up the CSA database files. Before performing this operation, consider the
following:
♦ An empty directory must be available for the CSA_Save operation. The
(CSA_Save) operation might fail for stations for which a file already exists.
♦ For drive space requirements, assume that you need 15 KB of space per control
station. Use the df command to check available drive space in the /usr partition.
2. Type the following:
cd /usr/fox/csa
mkdir save
CSA_Save ./save
This saves the CSA files in the /usr/fox/csa/save directory. There is one text file for
each control station.
3. Verify the contents of the save file(s). Type the following:
cd /usr/fox/csa/save
ls -l
Verify that each control station has a text file in this directory.
4. On the original host station, perform a CSA_Stop. Type the following:
cd /usr/fox/csa
CSA_Stop
This stops CSA_SERVER and removes ACSA from /usr/fox/bin/fox_apps.dat.
5. Reboot the original host. This removes all references to the CSA_SERVER
process. Verify that the CSA_SERVER is not running after the host boots up.
6. Copy the saved CSA files to an empty directory on the new host. For example,
create a save directory in /usr/fox/csa.
7. Start CSA on the new host. If there is no CSA_SERVER file in the /usr/fox/csa
directory, copy CSA_SERVER.new to CSA_SERVER. Type the following:
cd /usr/fox/csa
cp CSA_SERVER.new CSA_SERVER (if necessary)

15
B0400QD – Rev A 5. Software

Start CSA by typing:

cd /usr/fox/bin
/bin/sh go_ACSA
8. Load the database using CSA_Merge. Assuming that the CSA files were saved to the
/usr/fox/csa/save directory on the new host, type the following:
cd /usr/fox/csa
CSA_Merge /usr/fox/csa/save
9. Using an editor such as vi, edit the /usr/fox/bin/fox_apps.dat file to include ACSA.

5.1.1.4 Moving CSA from Intel to 50 Series Stations

5.1.1.4.1 Backing Up Intel CSA (CSA_Save)
This procedure describes how to save the Intel CSA database to a 3.5-inch diskette and convert it
for use by a 50 Series station. This procedure may only be used on the Intel CSA host station.

NOTE
Once the CSA_Stop utility is initiated, CSA menu access and Integrated Control
Configurator access is not possible until the CSA database is restored onto the
50 Series CSA host.

For the Intel CSA_Save procedure you need a formatted, mountable, 3.5-inch diskette (use the
VENIX format command).
1. Log into the AP20 from the WYSE terminal.
2. Insert the formatted diskette into drive 0 and save the CSA information. Type:
cd /usr/fox/ulan
CSA_Save
3. Verify the contents of the save file(s). Type the following:
mount /dev/fh0 /f0
ls -l
Verify that each control station has a text file on the diskette.
4. Unmount the diskette and label it. Type:
umount /dev/fh0
5. Turn off the CSA server. Type:
cd /usr/fox/ulan
CSA_Stop
6. Convert the CSA mountable diskette to 3.5-inch tar format for use by 50 Series sta-
tions. Perform the following on a PW or AP20 with a 3.5-inch diskette drive.
a. Enter VT100 mode.
b. Check free disk space using the df command. Each full diskette requires 2880
blocks of free space in /usr.
c. Mount the CSA diskette with read-only permissions. Type:
mount /dev/fh0 /f0 -r

16
5. Software B0400QD – Rev A

d. tar the contents of the diskette to a file named CSA. Type:

cd /f0
tar cvf /usr/tmp/CSA *
e. Unmount the diskette. Type:
cd /
umount /dev/fh0
f. Format a 3.5-inch diskette and save the tar file. Type:
format /dev/fh0
tar cvf /dev/fh0 /usr/tmp/CSA
g. Remove the tar file to free up the disk space:
rm /usr/tmp/CSA

5.1.1.4.2 Restoring CSA (CSA_Merge)

At the 50 Series CSA host station, perform CSA_Backup to restore the CSA database files.
1. Log in to the 50 Series station.
2. Transfer the saved CSA information from the 3.5-inch diskette, produced by the
procedure in “Backing Up Intel CSA (CSA_Save)” on page 16, to the 50 Series
station. The tar file loads into /usr/tmp and then expands into /opt/CSA_tmp:
tar xvf /dev/rfd0
mkdir /usr/fox/csa/save
cd /usr/fox/csa/save
tar xvf /usr/tmp/CSA
3. After tarring the CSA database files from the CSA tar file, remove the tar file. Type:
rm /usr/tmp/CSA
4. Restore the CSA database. Type the following:
cd /usr/fox/csa
CSA_Merge ./save
5. You can remove the CSA text files at this time to recover drive space. Type:
rm -r /usr/fox/csa/save

5.2 Workstation Software

5.2.1 Conversions and Update Procedures
For FoxView display conversions, see FoxView (B0193WH).

5.2.1.1 Display Conversion

When converting displays between UNIX and Windows operating systems, you may need to edit
the display picks that contain the run command on Windows workstations. If the run command
starts a script, the command must contain an sh after the run command (for example, run sh
/opt/scripts/my_script). Also note that the name of the script file must end in .ksh (for example,
my_script.ksh).

17
B0400QD – Rev A 5. Software

5.2.1.2 Caution About Display Conversion

When converting displays to 50 Series format, or when using the getremfiles file propagation util-
ity with the file conversion option or when using the d_edit or g_edit utility to edit 20 Series
(ia16) display files, be sure the display(s) being converted are not currently on display through the
Display Manager at the destination workstation. The display file may become corrupted when the
display is closed in the Display Manager. Redisplaying the corrupted file may cause the Display
Manager to hang, requiring a workstation reboot.

5.2.1.3 Common Alarm Group Configuration

If additional workstations have been added to the system configuration, including AW51s, then it
may be appropriate to invoke:
/usr/fox/alarms/CAGinit
This appends the new workstation’s letterbugs to the Common Alarm Group (CAG)
Configuration file (/usr/fox/alarms/commgrp.cfg). After running CAGinit, this ASCII file may
then be edited to configure the new workstations for inclusion within a CAG, or to configure
CAD redirection.

5.2.1.4 Alarm Configuration File Propagation

A file transfer utility which facilitates the transfer of files from one station to another is available
for 50 Series workstations. See Display Engineering for 50 Series Workstations (B0193MQ). The
alarm files /usr/fox/alarms/commgrp.cfg and /usr/fox/alarms/horn.cfg may be the same on each
50 Series workstation.
If a 50 Series workstation is available on the system, it may be desirable to make changes to these
alarm configuration files on that workstation, and then propagate these files out to other AP/AWs
and workstations from that centralized location.

5.2.1.5 Modifying Alarm Horn Configuration

When changes are made to the WPs alarm horn configuration file, /usr/fox/alarms/horn.cfg,
remove any existing binary configuration files prior to executing AAhorns. Type:
cd /usr/fox/alarms
rm -f *.BIN
AAhorns

5.2.1.6 Converting Intel Fonts and Markers to 50 Series Format

It is not necessary to do any conversions if you use the default fonts and markers delivered with
the 50 Series system. However, if you wish to copy font or marker files from a WP20/30 to a
50 Series AW or WP, you must convert them. To do so, follow the procedure described in Display
Engineering for 50 Series Workstations (B0193MQ).

18
5. Software B0400QD – Rev A

5.2.2 FoxView Software

5.2.2.1 FoxView and FoxDraw Software

If you want the FoxView package, you must separately purchase and install FoxView 8.0.2 soft-
ware. Refer to the tables titled “V7.0 Solaris Visualization Suite” and “V7.0 Windows XP Visual-
ization Suite” in V7.0 Read Me First (B0400QC) for information on the FoxView/FoxDraw kits,
which are optionally available with I/A Series Version 7.0 software.

NOTE
The FoxView and FoxDraw software packages are not included on the V7.0
Windows XP or Solaris 8 Day 0 CD-ROMs; you must install these packages from
the FoxView/FoxDraw 8.0.2 CD-ROM.

5.2.3 Screensavers
Do not run screensavers on your I/A Series stations.

5.3 Application Packages

5.3.1 Historian

5.3.1.1 Configuring “Backup your Historian Archive” Message

File /etc/wparlns defines all the WPs and AWs in the system. The message “Backup your
Historian Archive” is output when archiving control finishes its work for this file.
Use vi to edit /etc/wparlns, and delete any WPs or AWs for which you do not want the “Archive
Backup Required” message to appear.
If you prefer this message to go to the System Monitor error report printers, use vi to edit the file
/etc/histpath and set ARCPRT=yes. The default value is no.

5.3.2 FoxAPI Software

5.3.2.1 Determining the Version of FoxAPI Software

1. Use the foxtst utility to determine the installed version of FoxAPI™ software. Type:
cd /opt/fox/ais/bin
foxtst
2. Enter 1200 for the Sub Menu choice prompt.
3. Enter 29 for the function selection prompt.
4. The FoxAPI version information is returned, for example, “FoxAPI_version = 4.2.6.”

19
B0400QD – Rev A 5. Software

20
6. I/A Series Electronic
Documentation
The I/A Series Electronic Documentation CD-ROM for Windows NT 4.0, and
Windows 95/98/2000/XP contains I/A Series system user documentation for UNIX and Win-
dows platforms (.pdf files), control station sizing spreadsheets (.xls files), and on-line Help files
(.hlp files) not available from their applications.
Electronic Documentation CD-ROMs for I/A Series V6.4 and later software differ from previ-
ously released documentation CD-ROMs as follows:
♦ Documents are in PDF rather than HTML format
♦ Adobe® Acrobat Reader® 4.0 or 5.0
♦ Automatic updates of documents between releases is no longer supported.

6.1 Hardware Requirements

Before you install the I/A Series Electronic Documentation, make sure that your computer meets
the following minimum system requirements:
♦ Pentium® class processor or higher
♦ 32 MB of RAM
♦ Hard disk with at least 15.7 MB for Adobe Acrobat Reader 5.0 with Search, if not
already installed

NOTE
The I/A Series Electronic Documentation V6.5-7.0 CD ships with the Adobe
Acrobat Reader 5.0 with Search capability. If you already have Version 4.0 or later
of Acrobat Reader with Search capability installed, there is no need to install
Version 5.0.

♦ CD-ROM drive
♦ Keyboard/mouse
♦ Modem or Internet connection (for access to I/A Series hardware, software, and parts
for purchase).

21
B0400QD – Rev A 6. I/A Series Electronic Documentation

6.2 Software Requirements

In order to run, I/A Series Electronic Documentation also requires the following:
♦ Windows NT 4.0 or Windows 95/98/2000/XP operating system
♦ Internet browser, such as Microsoft® Internet Explorer 5.1, to access the I/A Series
system parts list from the iastore link on the CD-ROM
♦ Adobe Acrobat Reader 4.0 or later.

6.3 Uninstalling Previous Versions of I/A Series

Electronic Documentation
Invensys Foxboro recommends that you uninstall previously installed versions of the electronic
documentation prior to installing a newer version of I/A Series Electronic Documentation. To
uninstall, do the following in listed order:
1. Exit out of any open I/A Series Electronic Documentation window.
2. Remove downloaded documentation updates for the I/A Series Electronic Documen-
tation installation that you wish to remove.
3. Determine whether the I/A Series Electronic Documentation Server is running in the
background and close it.
4. Uninstall the previous I/A Series Electronic Documentation version.
If you would like to keep previous versions of I/A Series Electronic Documentation on your hard
drive, skip this section and go to “Installing I/A Series Electronic Documentation” on page 24.

6.3.1 Removing Updated Files

It is important that you remove updated files manually because the uninstall program for
I/A Series Electronic Documentation does not remove previously downloaded documentation
updates from your hard drive.
Below is a procedure to remove documentation updates for I/A Series 6.3 Documentation
(K0173TQ-H). Customize it to remove other installations of I/A Series Electronic
Documentation.
1. Click on Start > Programs > FoxDoc Documentation > IA Series 6.3 (K0173TQ-H)
Settings.
The I/A Series 6.3 Settings window appears.
2. Click the Remove Updated Files... button.
The FoxDoc Options dialog box appears.
3. Click Yes to remove all updates and revert to the original documents on CD-ROM.
The FoxDoc Options dialog box appears to indicate that the documentation has been
restored to its original state. You must close and reopen the I/A Series Electronic Doc-
umentation browser window to see the changes.
4. Click OK.
5. Click OK.

22
6. I/A Series Electronic Documentation B0400QD – Rev A

6.3.2 Stopping the I/A Series Documentation Server

NOTE
Perform the following steps only if you have the I/A Series Electronic Documenta-
tion for I/A Series V6.3 or earlier software installed.

To determine whether I/A Series Documentation Server is running in the background, check the
task bar for the appropriate I/A Series Documentation icon.

To stop the I/A Series Documentation Server, do the following:

1. On the task bar, right-mouse click on the IA Series Documentation icon.
2. Click Close.

NOTE
If you attempt to uninstall the I/A Series Documentation while the I/A Series
Documentation Server is running, you are prompted to restart the computer to
complete the task. This may also cause some files to remain on your hard drive. To
remove files that are left behind, delete:
driveletter:\Program Files\FoxDoc Browser\<cd-rom version>
or
driveletter:\Program Files\IA Series Browser\<cd-rom version>

6.3.3 Uninstalling the I/A Series Electronic Documentation

Application
NOTE
You should be sure to remove updated files from any existing versions and stop the
I/A Series Documentation Server prior to uninstalling, or else the previously down-
loaded files remain on your hard drive.

To uninstall a previous version of I/A Series Electronic Documentation, do the following:

1. Open the Control Panel window.
2. Double-click on the Add/Remove Programs icon.
The Add/Remove Programs Properties window opens.
3. Click on the Install/Uninstall tab. Highlight IA Series 6.4 Documentation
(K0173TQ-J) and click on Add/Remove.
4. Follow the screen prompts, and click OK to close the Install/Uninstall window when
done.

23
B0400QD – Rev A 6. I/A Series Electronic Documentation

6.4 Installing I/A Series Electronic Documentation

I/A Series Electronic Documentation requires 15.7 MB of available disk space for the Adobe
Acrobat Reader 5.0 application, if not already installed. Refer to “Hardware Requirements” on
page 21 for more details. See also “Uninstalling Previous Versions of I/A Series
Electronic Documentation” on page 22 for instructions on how to uninstall previous versions of
the I/A Series Electronic Documentation.
To install I/A Series Electronic Documentation and Adobe Acrobat Reader 5.0 with Search, pro-
ceed as follows:
1. Insert the I/A Series Electronic Documentation CD-ROM in the CD-ROM drive,
and the installation process begins automatically. If I/A Series Electronic Documenta-
tion does not automatically begin installing, perform the following steps to manually
start the process:
a. Click on Start > Run....
b. Type: x:\setup\setup.exe where x is your CD-ROM drive letter.
2. Click the Next button.
♦ If you meet the specifications for “Software Requirements” on page 22, and do
not wish to install Adobe Acrobat Reader 5.0 with Search (or if you have previ-
ously installed Adobe Acrobat Reader 5.0), leave the box next to “Adobe Acrobat
Reader 5.0” unchecked and click Next. Skip Step 3, and continue to Step 4.
♦ If you want to install Adobe Acrobat Reader 5.0, go to Step 3.
3. Follow the screen instructions and make the following selections, for installing Adobe
Acrobat Reader 5.0:
a. Check the box next to “Adobe Acrobat Reader 5.0” and click Next. If you already
have an earlier version of Acrobat Reader installed, you can simply install Adobe
Acrobat Reader 5.0 over it.
b. Continue to follow the instructions.
4. Follow the V6.5-7.0 installation instructions until the last screen indicates:
♦ I would like to view the README file
♦ Run I/A Series 6.5-7.0 K0173TQ-L.
5. Click Finish to complete the installation, being sure to select Run IA Series
6.5-7.0 K0173TQ-L, if desired.

NOTE
To minimize disk space usage, the documentation files on the CD-ROM are not
installed locally, and are instead accessed directly from the CD-ROM. You must
insert the I/A Series Electronic Dcoumentation CD-ROM in the CD-ROM drive
prior to starting I/A Series Electronic Documentation.

24
6. I/A Series Electronic Documentation B0400QD – Rev A

6.4.1 Starting I/A Series Electronic Documentation

To start I/A Series Electronic Documentation at any time:
1. Verify that the CD-ROM is inserted in the CD-ROM drive.
2. Select: Start > Programs > IA Series Documentation > IA Series 6.5-7.0
(K0173TQ-L).
A window appears which allows you to navigate or search the electronic
documentation CD-ROM.
3. To go back to the initial window from a document, click on Go Back at the top of the
Bookmark list.

6.4.2 Browsing the User Documentation

To navigate the User Documentation, follow these steps:
1. At the initial window, select an index viewing option from the Bookmark list at the
left of your screen. You have the following choices:
♦ Read Me First (explains initial installation settings and procedures)
♦ Version 6.5 (for I/A Series V6.5 users only)
♦ Version 7.0 (for I/A Series V7.0 users only)
♦ Part Number
♦ Title (alphabetical)
♦ Category
♦ iastore (online store for purchasing system software and hardware).
Click on the plus + symbol at the left of each Bookmark to expand its subsections. For
example, click the + beside Version 7.0 to access the Part Number, Title, and Category
document lists.
A new page loads with the selected choice information at the top of the page.
2. To view a document, click on the document number preceding the document revision
and title.
3. Click Go Back in the Bookmark list to return to the initial window.

6.5 Searching I/A Series Electronic Documentation

In order to search I/A Series Electronic Documentation, you must have a search version of Adobe
Acrobat (4.0 or higher). In addition, it is necessary to go into Adobe Acrobat Reader to set specific
preferences as well as add the I/A Series 7.0 K0173TQ-L search index.

6.5.1 Set up Preferences for Searching

Adobe Acrobat Reader 4.0, which is not shipped with I/A Series 6.5-7.0 (K0173TQ-L), and
Adobe Acrobat Reader 5.0 have different preference setup instructions, outlined below.
The following preferences need to be set in Adobe Acrobat Reader 4.0:
1. To have multiple windows open at the same time,
a. Select File > Preferences > General.
b. Make sure that “Open Cross-Document Links in Same Window” is unchecked.

25
B0400QD – Rev A 6. I/A Series Electronic Documentation

2. To allow the search and results windows to appear on top of the main window when
searching,
a. Select File > Preferences > Search.
b. Make sure that “Hide on Search” and “Hide on View” are unchecked.
3. To enable web links within Adobe Acrobat,
a. Select File > Preferences > Web Link.
b. Click Browse and locate the executable for the web browser. For example, the path
for Internet Explorer 5.1 is
C:\Program Files\Plus!\Microsoft Internet\IEXPLORE.EXE.
c. Click Open.
d. Click OK to close the window.
The following preferences need to be set in Adobe Acrobat Reader 5.0:
1. To have multiple windows open at the same time,
a. Select Edit > Preferences > Options.
b. Make sure that “Open Cross-Document Links in Same Window” is unchecked.
2. To allow the search and results windows to appear on top of the main window when
searching,
a. Select Edit > Preferences > Search.
b. Make sure that “Hide Query Dialog on Search” and “Hide Result Dialog on
Search” are unchecked.

6.5.2 Add the I/A Series K0173TQ-L Search Index

The Acrobat Reader, by default, searches its own index titled “Acrobat 4.0 Online Guide” or
“Acrobat 5.0 Online Guide,” depending on which version you use. In order to search the docu-
ments on the I/A Series 6.5-7.0 K0173TQ-L CD-ROM, the search index for the document set
needs to be added.
To add the I/A Series 7.0 search index using Adobe Acrobat Reader 4.0 or 5.0:
♦ Select Edit > Search > Select Indexes.
♦ Click Add. This opens a browse window.
♦ Go to the CD-ROM drive containing the CD-ROM K0173TQ-L.
♦ Double click on the file index70.pdx to add it to the searchable indexes.
♦ Click OK.

6.5.3 Search
To start a search of the I/A Series Electronic Documentation, do the following:
♦ Click on Edit > Search > Query
OR
♦ Click on Search icon (binoculars and paper) from the icon tool bar.
The search command allows you to perform full-text searches of the I/A Series PDF documenta-
tion set using the search index created for I/A Series 7.0 K0173TQ-L whereas the Find command
allows you to search only a single document. Refer to the Acrobat Guide via the Help button in

26
6. I/A Series Electronic Documentation B0400QD – Rev A

Adobe Acrobat for a complete explanation of the package and for specific search capabilities and
techniques.
To perform a full-text search:
1. Select Edit > Search > Query.
2. Type one or more keywords such as a document title, a B0 number, or phrase that
describes what you want.
3. Select Search. This command performs the search and then displays the documents
containing your keyword(s).
4. Double click on the document title that seems to contain the desired information.
The document opens on the first match within the document.
5. Click the Search Next button or the Search Previous button to go to other matches
within the document or choose another document to view.

6.5.4 Advanced Search

For a more complete explanation of the search and advanced search capabilities, refer to the
Acrobat Guide available from the Help button within Adobe Acrobat Reader.

27
B0400QD – Rev A 6. I/A Series Electronic Documentation

28
7. Preinstallation Considerations
This chapter describes items you should review before migrating to V7.0.
During the Day 0 installation of V7.0 software, the hard drive is completely overwritten by the
new version of software. You must back up all user files, and files that support applications.

7.1 Backing Up Hard Disks

Before performing V7.0 software installation, you may want to consider backing up your hard
disk drive on your existing workstation.

7.1.1 Pre-V7.0 50 Series Workstations

To back up the hard disk, see “Hard Disk Drive and Miscellaneous System Administration Proce-
dures” in System Administration Guide (Solaris 8 Operating System) (B0400DU).

7.1.2 Pre-V7.0 70 Series Workstations

To back up your hard disk and create a repair disk, refer to the subsections “Tape Backup and
Restore” and “Repair Disk Utility” in System Administration Guide (Windows NT Operating
System) (B0400ND).

! CAUTION
You cannot restore a tape made on the internal tape drive of a Windows NT work-
station to a Windows XP workstation; Windows NT and Windows XP internal
tape drives are not compatible. If you must restore these files to a Windows XP
workstation, be sure that the files are saved using an external AIT tape drive or some
other medium, for example, a recordable CD. (Model P93 Windows NT worksta-
tions have CD-RW drives that could be used to transfer files via a CD-ROM.)

7.2 Saving Control Databases (SaveAlls)

Save the databases for all control stations, gateways, and volumes before performing the Day 0
installation. If you want to upload the latest settable parameters from the control station, perform
the upload before performing the SaveAll. If the SaveAll operation requires more than one dis-
kette, label each diskette with the diskette number and quantity, for example, 1/2, 2/2.
See “SaveAll” in the “Menu Bar Functions” and/or “Upload” in the “Compounds, Blocks, and
ECBs” chapters of Integrated Control Configurator (B0193AV).

29
B0400QD – Rev A 7. Preinstallation Considerations

7.3 Backing Up CSA Files

Review “Compound Summary Access (CSA)” on page 4 to determine if you need to back up the
CSA files.
When backing up CSA files, use the CSA_Save utility described in “Backing Up CSA
(CSA_Save)” on page 13 in Chapter 5 “Software”.

7.4 Backing Up Files

You must back up the user, application, and database files of your current drive before continuing.
See Appendix B “Files to Back Up/Restore” on page 41 of this document.

7.4.1 Saving Invensys Foxboro Application Databases

Save Invensys Foxboro standard product application databases.

NOTE
Stop all processes that write to the database (Historian, AIM*Historian, or
FoxAMI™, for example).

7.4.1.1 Saving Historian Database (Model 51F/G)

If you have a legacy historian, and are going to port it to a Model 51F/G, execute the saveh50
program on the pre-V7.0 workstation. This program prompts you for the device. Enter 0 for dis-
kette (bar format), 1 for tape (tar format), 2 for cassette (tar format), or 3 for hard disk (default).

NOTE
You will lose all sample files when you use saveh50 to save the Historian database on
the old workstation, and use loadh50 to restore the Historian database to a new
Solaris 8 workstation.

To save reduction, archiving, MDE, and configuration data, type:

cd /opt/fox/hstorian/bin
saveh50
Errors can corrupt indexes and prevent saving sample data. To check for errors, type:
cat saveh50.log ¦ grep -i error

7.4.1.2 Saving AIM*Historian Database

For detailed information on saving AIM*Historian database, refer to Information Suite
AIM*Historian User’s Guide (B0193YL).

7.4.2 User Applications and Third-Party Package Files

All databases and configuration files for user applications and third-party packages must be
backed up. Include all Invensys Foxboro Industry or Application Group applications (such as,
Logs, Power Performance Package, and BOSS) found in /etc/fox/rc.foxapps and
/usr/fox/bin/user_apps.dat.

30
7. Preinstallation Considerations B0400QD – Rev A

Following I/A Series software installation, these files are restored from tape and the applications
and third-party packages are reloaded or installed from user- or vendor-supplied media.

NOTE
1. Contact your local Invensys Foxboro office to determine if there are any special
considerations for industry application packages you are using.
2. Reinstallation of third-party packages requires that the original or a newer version
of the package media is available. Consult with the vendor to determine
compatibility and rekeying requirements.

7.4.2.1 Uninstalling Select Packages with Single Station Licensing (AW70)

For software packages that have single station licensing, such as RSLinx™, uninstall the package
prior to performing the disk backup to preserve the licensing information. See Application Work-
station 70 with Allen-Bradley PLCs (Windows NT Operating System) (B0400AL).

7.4.2.2 Backing Up Display Files

Back up all customized display files. No display file conversion is necessary when upgrading to
V7.0. Customized markers, fonts, faceplates, and so forth, developed using the FoxDraw package,
are stored in the directory /opt/customer/displib.

7.5 Checking the LONG_S Parameter

The parameter Units/Range for the LONG_S parameter associated with the FIIN and FIOUT
blocks, as described in the document Device Integration Using I/O Gates (B0193VG), is incorrectly
stated as 0 = short and 1 = long. Revision C of Device Integration Using I/O Gates (B0193VG) has
been corrected to indicate that the Units/Range for LONG_S is 0 = long, 1 = short.
This correction may require database modification if any FIIN or FIOUT blocks are in use when
upgrading to V6.2.3 Micro-I/A software supplied with V7.0 I/A Series software. If you have exist-
ing FIIN or FIOUT blocks in a database, check the LONG_S parameter for correct configuration
(0 = long and 1 = short) in every block.

! CAUTION
Failure to correct this parameter may cause the blocks to operate incorrectly.

Perform the following steps:

1. Place the compound(s) containing the FIIN or FIOUT blocks off-line.
2. Modify LONG_S parameters in each FIIN and FIOUT block in the Micro-I/A
database.
3. Turn the compounds on.
4. Checkpoint the database.

31
B0400QD – Rev A 7. Preinstallation Considerations

32
8. Installation Considerations
Review this chapter for information to help you install the software.
For EEPROM considerations, review Appendix C “EEPROM Revision Levels”.

8.1 Software Installation (UNIX Systems Only)

8.1.1 Printer Message ex_fetch
During software installation, a message to the printer from the ex_fetch process indicating “No
msg found” is benign and may be ignored.

8.1.2 Software Install – Assign Peripheral Device Utility

The Assign Peripheral Devices screen under software install utilities could be misleading, that is, it
shows devices that may not exist.

33
B0400QD – Rev A 8. Installation Considerations

34
9. Postinstallation Considerations
(UNIX Systems)
This section describes some postinstallation considerations for station operation after the
station has been installed.

9.1 Real-Time Trends Not Displaying Recent

Historical Data
To avoid an issue where real-time trends do not display recent historical information after a
software upgrade or migration, perform restoration of Historian database files and display files in
the following order.
1. Always load the Historian database first.
2. Load displays and trends.
3. Reboot the AW/WP.
To recover from such an issue, perform the following procedure:
1. Save all displays and trends to tape.
2. Delete all displays and trends from the hard drive.
3. Reload all displays and trends from tape.
4. Reboot the AW/WP.

9.1.1 Restoring the Historian Database (AP51/AW51)

Execute the loadh50 program. This program prompts you for the device. Enter the load medium:
0 for diskette, 1 for tape, 2 for cassette, 3 for hard disk (default).

NOTE
You will lose all sample files when you use saveh50 to save the Historian database on
the old workstation, and use loadh50 to restore the Historian database to a new
Solaris 8 workstation.

9.2 “Auto-revarp failed” Recovery at Boot Time

In some unusual error conditions, a 50 Series station at boot time attempts to discover its letter-
bug from the network. As a result, it repeatedly displays the message “auto-revarp failed: no RARP
replies received” on the console at boot time. To allow the station to continue booting, press
CTRL+C on the console.

35
B0400QD – Rev A 9. Postinstallation Considerations (UNIX Systems)

9.3 Annunciator Keyboards Off-Line After Power Up

After a power cycle of a 50 Series station (not including the GCIO), the keyboard may remain
off-line and failed; cycling power to the GCIO box and selecting a key corrects this.

9.4 User Application Software Startup

On 50 Series stations, start user application software, including Invensys Foxboro Industry Group
and Custom application software, using the /etc/fox/user_apps.dat file.

NOTE
You must first create the /etc/fox/user_apps.dat file, because the file does not exist
on systems shipped by Invensys Foxboro.

User application software must not be started using /usr/fox/bin/fox_apps.dat. The

/etc/fox/user_apps.dat contains a list of programs to be executed during the 50 Series station star-
tup. During startup, the station checks for the existence of /etc/fox/user_apps.dat. If the
/etc/fox/user_apps.dat file exists, each line in the file is executed as a shell command. After these
commands are started, the Invensys Foxboro standard product applications, like Historian, and
Operator Message Interface (OMI) start. Each line of the /etc/fox/user_apps.dat file can contain
only one field. The single field contains the full pathname of the application or application star-
tup program that is to be executed. Each line in /etc/fox/user_apps.dat is executed in the fore-
ground and must complete execution before the next program or script in the next line is
executed.
If the program or script specified in /etc/fox/user_apps.dat needs to be executed in the back-
ground, requires command line arguments, or can be executed in parallel with other programs,
the program requires a special startup script to start the program. The following are different
examples of the ways to use /etc/fox/user_apps.dat:
Example 1: To create a few Object Manager shared variables, the program requires com-
mand line arguments:
1. Generate a script that creates OM shared variables:
#!/bin/sh
# This script is named /opt/my_applic/my_om_create and
# creates shared variables SV1, SV2 and SV3
for variable in SV1 SV2 SV3
do
/opt/fox/bin/tools/omcrt $variable
done
2. Edit /etc/fox/user_apps.dat to contain the following line:
/opt/my_applic/my_om_create

NOTE
If after you edit the file, the ps -eaf command shows that the S99FOXBORO pro-
cess is still active, a sleep command needs to be added to beginning of the
user_apps.dat file.

36
9. Postinstallation Considerations (UNIX Systems) B0400QD – Rev A

Example 2: Execute a program in background. The program is named

/opt/my_applic/4ever:
1. Generate a startup script called go_4ever in the /opt/my_applic directory, that exe-
cutes the program in the background
nohup /opt/my_applic/4ever > /opt/my_applic/4ever.log 2>&1 &
2. Edit /etc/fox/user_apps.dat to contain the following line
/opt/my_applic/go_4ever

9.5 Converting a Customized Color Palette

Skip this section if you have not customized the standard I/A Series color palette.
FoxView and FoxDraw software use the color palette definition file, /usr/fox/wp/data/color-
def.dat. This is an ASCII file that you can modify with a text editor, if desired. Using the
I/A Series Color Palette Editor, you can determine any customized RGB values in the 50 Series
color palette, sys_pal.wp50, and then enter the values into the colordef.dat file.
The colordef.dat file has the format:
<color index> RGB values
For example, color indices 16 through 31 have the following entries:
Color Index Red Green Blue
16 0 0 0
17 .760 0 0
18 0 .619 0
19 .619 .333 0
20 0 0 .60
21 .709 0 .674
22 0 .627 .619
23 .714 .714 .714
24 .447 .447 .447
25 1.0 0 0
26 0 1.0 0
27 1.0 .988 0
28 0 0 1.0
29 1.0 0 .952
30 0 1.0 .988
31 1.0 1.0 1.0

37
B0400QD – Rev A 9. Postinstallation Considerations (UNIX Systems)

9.6 FBM Firmware Upgrade Messages

When you upgrade the firmware of many FBMs of a CP, it is possible that some firmware upgrade
success messages to the printer may not be printed. After a download is completed on all FBMs, it
may be desirable to run the frev utility in the tools directory (/opt/fox/bin/tools) of the file server.
This utility shows the firmware revision levels of all FBMs.

38
Appendix A. Time Estimation for
Migration to V7.0 Platforms
This model shows the time required to migrate to the V7.0 platform. If you wish to migrate to
V7.0, you should use the following information to estimate the amount of time that may be
involved.

A.1 Preinstallation
If you are migrating files from an existing system, consider performing the following procedures
on your pre-V7.0 workstation.
1. Back up all hard disks.
This is a simple procedure if a streaming tape drive is connected to the 50 Series
station, but takes significantly more time if SCSI peripherals must be swapped.
Time Required:
1.00 hr/50 Series with streaming tape drive
2.00 hrs/50 Series without streaming tape drive
2. Save control databases.
Uploading adds significantly more time to the update. The amount of time also
includes performing the SaveAll. The CP designation also includes gateways.
Time Required:
0.25 hr/CP for Upload
0.25 hr/CP for SaveAll
3. Back up CSA files (CSA_Save).
Time Required:
0.25 hr
4. Save displays.
Time Required:
0.25 hr/100 displays
5. Save databases to diskettes.
The amount of time for this step is dependent on the number of applications and user
customized software on the station.
Time Required:
0.25 hr/AP plus 0.25 hr/application
6. Update the system definition.
Time Required:
1.00 hr

39
B0400QD – Rev A Appendix A. Time Estimation for Migration to V7.0

A.2 Installation
Perform a Day 0 install via CD-ROM and a Commit.
Time Required:
1.00 hr/50 Series station
1.00 hr/70 Series station

A.3 Postinstallation
1. Restore the CSA files (CSA_Merge).
Time Required:
0.25 hr/25 CPs
2. Load the control databases.
Time Required:
0.50 hr/CP or gateway
3. Fix, EEPROM, and download the FBMs.
Time Required:
1.00 hr/30 FBMs
4. Load the custom files and databases.
Time Required:
0.25 hr/AP plus 0.25 hr/application
5. Load the displays.
Time Required:
0.25 hr/100 displays
6. Restart the historian.
Time Required:
0.25 hr/application
7. Reoptimize/convert displays.
Time Required:
1.00 hr/100 displays
8. Back up hard drives.
Time Required:
1.00 hr/station with local tape unit
2.00 hr/station with remote tape unit

40
Appendix B. Files to Back
Up/Restore
This appendix details the standard I/A Series files and directories that you should consider
backing up from the pre-V7.0 hard drive for restoration onto the Day 0 drive.

NOTE
For 50 Series workstations, files may already be saved to tape if you backed up your
hard disk. Individual files can be restored using ufsrestore on a 50 Series station.

! CAUTION
You cannot restore a tape made on the internal tape drive of a Windows NT work-
station to a Windows XP workstation; Windows NT and Windows XP internal
tape drives are not compatible. If you must restore these files to a Windows XP
workstation, be sure that the files are saved using an external AIT tape drive or some
other medium, for example, a recordable CD. (Model P93 Windows NT worksta-
tions have CD-RW drives that could be used to transfer files via a CD-ROM.)

B.1 Saving Files

For Windows NT workstations, files must be saved to 3.5-inch diskettes, an external AIT tape
drive, or some other medium, for example, a recordable CD in order for the files to be restored
after the installation.
For Solaris workstations, files must be saved on 3.5-inch diskettes or streaming tape in order for
the files to be restored after the installation. You can use tar to save files to diskette and tape.
For more information, type man tar on 50 Series AP and AW stations.

B.2 Files to Back Up/Restore for Day 0 Migration

These files should be backed up from your pre-V7.0 system for later restoration.

B.2.1 Application Databases

NOTE
1. The columns WP51 and AW51 represent all styles of workstation (including
Model 51F and Model 51G).
2. The column WP70 represents all styles of workstation (including Model 70P).
3. The column AW70 represents both AW70 and AW70P.
4. Files noted for WP70 and AW70 exist on the D: drive.

41
B0400QD – Rev A Appendix B. Files to Back Up/Restore

Application Databases AP51 WP51 AW51 WP70 AW70 Note

Spreadsheet Database
/opt/fox/spr/environ X X X

SPECTRUM Slave Gateway Database

/usr/fox/sp/files/DB*.FSG X X

Statistical Process Control

/opt/fox/spc/db X X

INI10 and INI15 Files

/usr/fox/sp/files/*.inicnf X X
/usr/fox/sp/files/*.ini15c X X X

OMI
/usr/msgs/config X X

AIS Datasets
/opt/fox/ais/bin/aiscfg X X 1
/opt/fox/ais/bin/foxapi.cfg X X 1
/opt/fox/ais/bin/an_init.cfg X X 1
/opt/fox/ais/bin/aisstart X X 1
/opt/fox/ais/bin/*.dat X X 1
/opt/fox/ais/bin/an_server.tcp X X 1
/opt/fox/ais/bin/an_server.dec X X 1
/opt/fox/ais/bin/opensets X X 1
/opt/aim/bin/an_init.tcp X X 1
/opt/aim/bin/aimapi.cfg X X 1

Report Writer
/opt/fox/rptwrt/rpt_cfg/*.cfg X X
/opt/fox/rptwrt/rpt_cfg/REPORTS X X
/opt/fox/rptwrt/sched/mastercron X X 1

Control Libraries
/opt/fox/ciocfg/sequenlibrary X X X
/opt/fox/ciocfg/sequeninclude X X X
/opt/fox/ciocfg/plblibrary X X X

Note:
1. Files requiring changes need to be recustomized. Do not just replace Day 0 files with older files.

42
Appendix B. Files to Back Up/Restore B0400QD – Rev A

B.2.2 Display-Related Files

NOTE
1. The columns WP51 and AW51 represent all styles of workstation (including
Model 51F and Model 51G.
2. The columns WP70 and AW70 represent all styles of workstation (including
Model 70P).
3. Files noted for WP70 and AW70 exist on the D: drive.

Display-Related Files AP51 WP51 AW51 WP70 AW70 Note

/usr/fox/ia16/usr/custom/Initial_Disp X X 1
/usr/fox/ia16/usr/fox/tmplts/CAD* X 1
/usr/fox/ia16/usr/fox/tmplts/AHD?? X 1
/usr/fox/ia16/usr/displib X X 2
/usr/fox/ia16/usr/disp X X
/usr/fox/ia16/usr/dispgrp X X
/usr/fox/ia16/usr/menus X X
/usr/fox/ia16/usr/fox/sys/Change_Env X X
/usr/fox/ia16/usr/markers X X
/usr/fox/ia16/usr/fox/dd X X 1
/usr/fox/alarms/*AAtab X X X X X
/usr/fox/alarms/*AApan X X X X X
/usr/fox/alarms/commgrp.cfg X X X X X
/usr/fox/alarms/alarms.fmt X X X X X
/usr/fox/alarms/*.apccr (or *.apc) X X X X
/usr/fox/alarms/horn.cfg X X X X X
/usr/fox/hi/sys_pal.gc4 X X
/usr/fox/wp/data/sys_pal.wp50 X X 1
/usr/fox/hi/gc?_glbls.1 X X 1
/usr/fox/hi/gc?_glbls.all X X 1
/usr/fox/hi/init.cmds X X 1
/usr/diskless/<WPLBUG>/init.user X X
/usr/fox/wp/data/init.user X X 1
/usr/fox/wp/data/wp5?_cmds X X X X X 1
/usr/fox/wp/data/wp5?_glbls.1 X X X X 1
/usr/fox/wp/data/wp5?_glbls.all X X X X 1
/usr/fox/wp/data/am_cmds X X X X 1
/usr/fox/wp/data/fv_cmds X X 1
/usr/fox/hi/sys_*.* X X 1
/usr/fox/hi/conventions X X
/usr/fox/hi/Dsp_Status X X 1
/usr/fox/wp/data/conventions X X
/usr/fox/wp/data/Dsp_Status X X 1
/usr/custom/Initial_Disp X X
/usr/fox/tmplts/CAD* X X X 1
/usr/fox/tmplts/AHD?? X X X 1

43
B0400QD – Rev A Appendix B. Files to Back Up/Restore

Display-Related Files AP51 WP51 AW51 WP70 AW70 Note

/usr/fox/dd X X 1
/usr/disp X X
/usr/displib X X 2
/usr/menus X X
/usr/fox/sys/Change_Env X X 1
/usr/fox/*/.pulldown X X 1
/usr/fox/wp/data/dmpasswd_cfg X X
/usr/prog X X X
/usr/fox/wp/fonts/*usr*.bdf X X 1
/usr/fox/sp/crt_location X X
/usr/fox/customer/hi/dmcfg X X X X 1
/usr/fox/customer/alarms/cfg X X X X 1
/usr/fox/customer/config X X X X 1
/opt/ia/* X X 1
/opt/menus X X X X
/opt/disp X X X X
/opt/customer X X X X
/opt/custom/Initial_Disp.* X X X X 1
/opt/fox/env/*.* X X X X 1
Customer Display Files X X X X X

Notes:
1. Files requiring changes need to be recustomized. Do not just replace Day 0 files with older files.
2. All files in displib directory; except Invensys Foxboro supplied libraries (Buttons, Group_butn,
Group_trnd, Faceplates, Xfaceplate, MsgFile, Profiles, Trends, and XYplots).

B.2.3 System-Related Files

NOTE
1. The columns WP51 and AW51 represent all styles of workstation (including
Model 51F and Model 51G.
2. The columns WP70 and AW70 represent all styles of workstation (including
Model 70P).
3. Files noted for WP70 and AW70 exist on the D: drive.

System-Related Files AP51 WP51 AW51 WP70 AW70 Note

/etc/shadow X X X 1
/etc/printers X X X 1
/etc/system X X X 1
/etc/vfstab X X X 1
/etc/hosts X X X 1, 2
/etc/hosts.equiv X X X 1
/etc/hostname.le? X X X
/etc/hostname.hme? X X X 5
/etc/passwd X X X 1

44
Appendix B. Files to Back Up/Restore B0400QD – Rev A

System-Related Files AP51 WP51 AW51 WP70 AW70 Note

/etc/group X X X 1
/etc/netmasks X X X 1, 2
/.cshrc* X X X 1
/.profile X X X 1
/.login X X X 1
/.rhosts X X X 1
/.Xdefaults X X 1
/etc/defaultrouter X X X 1
/etc/defaultdomain X X X 1
/etc/nsswitch.conf X X X 1
/etc/dfs/dfstab X X X 1

X Terminals
/opt/ia/.profile X X X 1

Application Files
/usr/applic X X X
/etc/fox/user_apps.dat X X X 1
/etc/fox/rc.foxapps X X X 1
/etc/fox/opsys_usr.cfg X X X X X 1
/usr/spool/cron/crontabs X X X 1
/opt/foxind X X X

Historian Files
/usr/hstorian X X X 3
/opt/fox/foxhistory/inst X X X
/opt/fox/foxhistory/myfiles X X X
/opt/aim/inst X X X
/opt/aim/myfiles X X X

Open Look Menu Files

/usr/openwin/lib/openwin* X X 1

Process Summary Reporter

/usr/fox/psr/cfg X X X 4

Notes:
1. New (Day 0) versions of these files may require customization using data from your older files. Do
not just replace the Day 0 files with the older files.
2. Files have a symbolic link. Files requiring changes need to be recustomized. Do not just replace
Day 0 files with older files. Doing so can destroy the link.
3. All files excluding MSG_FMT.c, MSG_FMT.o, almhist, and almhist.bak.
4. Files $initcfg and cfg<LBUG> should be excluded, where LBUG is the letterbug.
5. hme (10,100 Mb Ethernet) drivers are used by Styles D and E station types.

45
B0400QD – Rev A Appendix B. Files to Back Up/Restore

46
Appendix C. EEPROM Revision
Levels
This appendix indicates specific modules’ EEPROM and/or V7.0 software revision levels. For
instructions on updating EEPROM firmware, see “EEPROM Update Action” of System
Management Displays (B0193JC).

NOTE
In the following tables, dashes indicate that the revision is unchanged from the previ-
ous release. N/A indicates that the station or module is not available for that I/A Series
software release.

The following table lists control stations, their EEPROM revision levels, and their V7.0 software
revision levels.

Table C-1. Control Stations

EEPROM Revision Levels V7.0 Software

Station Revision
Description Mnemonic V6.3 V6.4 V7.0 Level
®
A-B Data Highway Gateway AB-GW 2.20 — — 6.1.4
A-B Data Highway Gateway AB-R-GW 2.20 — — 6.1.4
Redundant
Allen-Bradley Station ABSTN 2.20 — — 6.2.1
Control Processor 10 CP10 2.20 — — 6.1.5
Control Processor 30 CP30 2.15 — — 6.1.4
1
Control Processor 30B CP30B 3.02 (6.3) 3.30 — 6.1.4
3.20 (6.3CS)
Control Processor 40 CP40 1.20 — — 6.1.4
Control Processor 40B CP40B 3.02 (6.3) 3.301 — 6.1.4
3.20 (6.3CS)
Control Processor 60 CP60 3.02 (6.3) 3.302 — 6.4
3.20 (6.3CS)
FoxGuard Manager 4.2.2 — — 6.2.1
Instrument Gateway 10 Inst GW 2.20 — — 6.1.4
Integrator 30 for A-B PLCs GW30AB 1.20 — — 6.1.4
Integrator 30B for A-B PLCs AB30-Style B GW 3.02 (6.3) 3.30 — 6.1.4
3.20 (6.3CS)
Integrator 30 for MG PC GW30MOD 1.20 — — 6.1.4
Integrator 30B for MG PC MG30-Style B GW 3.02 (6.3) 3.30 — 6.1.4
3.20 (6.3CS)
INTERSPEC™ Integrator 30 GW30IS 1.20 — — 6.1.4
INTERSPEC Integrator 30B IS30-Style B GW 3.02 (6.3) 3.30 — 6.1.4
3.20 (6.3CS)
Micro-I/A Type 1 Station Micro-I/A 62.3 — — 6.2.3
®
Modbus Plus ModBusPlus 1.00 — — 6.1.4

47
B0400QD – Rev A Appendix C. EEPROM Revision Levels

Table C-1. Control Stations (Continued)

EEPROM Revision Levels V7.0 Software

Station Revision
Description Mnemonic V6.3 V6.4 V7.0 Level
Modbus Plus Redundant ModBusPlus-Red 1.00 — — 6.1.4
®
Modicon Gateway MOD-GW 2.20 — — 6.1.4

1.
Control Processor Style Bs must be booted with V6.1.4 control software before the EEPROM
is updated to 3.30. See “Determining EEPROM Version” on page 52 and “Performing
EEPROM Update” on page 53.
2.
Control Processor 60s must be booted with V6.4 control software before the EEPROM is
updated to 3.30. See “Determining EEPROM Version” on page 52 and “Performing
EEPROM Update” on page 53.

The following table lists communication stations, their EEPROM revision levels, and their V7.0
software revision levels.

Table C-2. Communication Stations

EEPROM Revision Levels

V7.0 Software
Description Station Mnemonic V6.3 V6.4 V7.0 Revision Level
Communication Processor 10 COMM10 2.20 — — 6.4
Carrierband LAN I/F LI 2.12 — — 6.4

The following table lists miscellaneous stations and peripherals and their EEPROM revision
levels.

Table C-3. Miscellaneous EEPROM Revision Levels

EEPROM Revision Levels

Description Station Mnemonic V6.3 V6.4 V7.0
Workstation Processor 20 WP20 2.19m — —
Workstation Processor 30 WP30 2.9 — —
GCIO Interface GCIO Interface 1.3 — —
Keyboard KBD 5.9 — —
Annunciator Keypad AKP 5.8 — —

Table C-4 lists 100 Series FBMs and their software versions. Software versions and EEPROM
revision levels for 100 Series FBMs and associated modules are displayed in the System Manage-
ment Equipment Information display as follows:

SOFTWARE REV: <V7.0 Software Version>

EEPROM REV: 61.1

48
Appendix C. EEPROM Revision Levels B0400QD – Rev A

NOTE
EEPROM version 61.1 supports replacement (ORBIT) FBM hardware. FBMs with
an EEPROM level of 40.1 are not required to EEPROM update to Level 61.1. Note
that version 61.1 EEPROM firmware is compatible with the older style FBMs.

Table C-4. 100 Series FBMs (Y Form Factor)

Software Version
Devices Using IOM ID V6.3 V6.4 V7.0
FBM01, FBM02, FBM03, FBM03A, FBM03B, IOM 01 42.4 — —
FBM19, FBM33, FBM33A, FBM33B,
BAMM01, BASM02, BASM03, BASM33,
F1M01A, F1M01C, F1M01E, F1M01F,
F1M02, F1M03A, F1M03C, H2C02A,
H2C02B, H2C02D through H, H2C02J
through N, H2C02P through Z, H2D02A
through E, H2D02G, H2D02H, H2J02A
through H, H2M01A through D, H2M02,
H2M02A, H2M02B, H2M02E, H2M03,
H2M03A through G, H2V02B through H,
H2V02J, H2V02L through N, H2V02P through
R, H2X02A through H
FBM04, FBM05, F1M04A, F1M04B, H2M04 IOM 02 42.3 — —
H2C02A, H2C02B, H2C02F, H2C02G, IOM 03 42.2 — —
H2C02J, H2C02K, H2C02P, H2C02Q,
H2C02S, H2C02T, H2C02X, H2C02Y,
H2D02A through E, H2D02G, H2D02H,
H2J02A, H2J02B, H2J02F, H2J02G,
H2M01A, H2M02, H2M02A, H2M02B,
H2M02E, H2M03A, H2M03B, H2M03F,
H2M03G, H2V02B through H, H2V02J,
H2V02L through N, H2V02P through R,
H2X02A through H, H3M03
FBM06, F1M06, H2M06, H2M06A, H3M06 IOM 04 42.2 64.1 —
FBM07, FBM07A, FBM07B, FBM08, FBM09, IOM 05 41.1 — —
FBM09A through D, FBM10, FBM11, FBM12,
FBM12A, FBM12B, FBM13, FBM14, FBM14A
through D, FBM15, FBM16, FBM20, FBM21,
FBM24, FBM24A through C, FBM25,
FBM25A through C, FBM26, FBM26A
through C, FBM27, FBM27A through C,
FBM41, FBM41A, FBM41C, FBM42,
FBM42A, FBM42C, BDSI07, F1M07,
BDSM09, BDSM9A, BDSM9B, F1M09,
BDSO10, BDSO26, BDSO41, H2M07,
H2M07E, H2M09, H2M24, H2M26, H3M07,
H3M09
<SOE> BSME01, FBM07A, FBM07B, IOM 06 42.1 — —
FBM08, FBM12A, FBM12B, FBM13, FBM20,
FBM21, FBM24, FBM24A through C, FBM25,
FBM25A through C, F1M07, H2M24, H3M07
<PULSE> FBM07A, FBM07B, FBM08, IOM 07 41.1 — —
FBM12A, FBM12B, FBM13, FBM20, FBM21,
FBM24, FBM24A through C, FBM25,
FBM25A through C, F1M07, H2M24, H3M07

49
B0400QD – Rev A Appendix C. EEPROM Revision Levels

Table C-4. 100 Series FBMs (Y Form Factor) (Continued)

Software Version
Devices Using IOM ID V6.3 V6.4 V7.0
<LADDER> FBM07A, FBM07B, FBM08, IOM 08 61.1 — —
FBM09A through D, FBM10, FBM11,
FBM12A, FBM12B, FBM13, FBM14A through
D, FBM15, FBM16, FBM20, FBM21, FBM24,
FBM24A through C, FBM25, FBM25A
through C, FBM26, FBM26A through C,
FBM27, FBM27A through C, FBM41,
FBM41A, FBM41C, FBM42, FBM42A,
FBM42C, BDSO10, BDSO26, BDSO41,
F1M07, H2M24, H2M26, H3M07, H3M09
FBM17, FBM17A through D, FBM22, H2M17 IOM 09 42.3 — —
FBM18, FBM43 IOM 12 62.1 — —
<HTG> FBM23 IOM 13 40.2 — —
FBM38 IOM 22 40.4 — —
FBM39, FBM44 IOM 23 62.1 — —
Display IOM 28 40.2 — —
<MDACT> FBM17, FBM17A through D, IOM 34 42.2 — —
H2M17
<MDPUL> FBM17, FBM17A through D, IOM 36 42.2 — —
H2M17
<Multibaud> FBM18 IOM 37 42.3 — —
<Multibaud> FBM39 IOM 38 61.1 — —
<Gas Chromatograph> FBM45 IOM 39 40.1 — —
42.2 masked
FBP10 IOM 42 62.1 — —
FBP11 (SMI, UCM) IOM 43 42.8 — —
FBP12 (FIO) IOM 44 62.1 — —
FBP13 (UFM) IOM 45 42.8 — —
FBP14 (UIO) IOM 46 42.8 — —
FBP10R IOM 47 62.1 — —
FBP11R IOM 48 42.8 — —
FBM6 IOM 49 61.1 — —
<PID> FBM04, FBM17, FBM17A through D, IOM 52 61.2 — —
FBM22, H2M17
FBM37, BAOM37, H3M37 IOM 53 42.1 — —
H3M01 IOM 54 4.20.05.03 4.21.05.03 —
BASI03 IOM 55 5.05.05.03 5.06.05.03 —
BDSM06 IOM 55 5.05.03.03 5.06.03.03 —
BASI01, BASM01 IOM 56 4.20.05.03 4.21.05.03 —
BASO37 IOM 56 4.20.04.03 4.21.04.03 —
FRM701, FRM711, FRMMPU IOM 57 4.20.07.03 4.21.07.03 —
F2M68A IOM 58 4.20.05.03 4.21.05.03 —
F2M67A IOM 59 4.20.06.03 4.21.06.03 —
<FoxCom> FBM43 IOM 73 61.2 — —

50
Appendix C. EEPROM Revision Levels B0400QD – Rev A

Table C-5 lists 200 Series FBMs and their software versions. 200 Series FBMs and communica-
tion modules must be EEPROM updated. Software and EEPROM revision levels for 200 Series
FBMs and most associated modules (except FCMs and FBI10E) are displayed in the System
Management Equipment Information display as follows:

SOFTWARE REV: <FBM> <V7.0 Software Version> or <V7.0 Software Version> <FBM>
EEPROM REV: ROM <V7.0 Software Version>

EEPROM revision levels for Fieldbus Communication Modules (FCMs) and the FBI10E are
indicated in the SOFTWARE REV A and SOFTWARE REV B fields in the System Management Equip-
ment Information display.

Table C-5. 200 Series FBMs (DIN Rail Mounted FBMs) and FCMs

Software Version
Devices Using IOM ID V6.3 V6.4 V7.0
FBM214 (HART) IOM 214 N/A 2.10 —
FBM215 (HART) IOM 215 N/A 2.10 —
FBM216 (HART) IOM 216 N/A 2.10 —
FBM218 (HART) IOM 218 N/A 2.10 —
FBM220 (FOUNDATION™ fieldbus H1) IOM 220 2.03 (6.3) 2.07 —
2.04 (6.3CS)
FBM221 (FOUNDATION fieldbus H1) IOM 221 2.03 (6.3) 2.07 —
2.04 (6.3CS)
FBM223 (Profibus-DP) IOM 223 N/A 1.00 —
WFCM10Ef, WFCM10E, FCM10E, FCM10Ef, FBI10E, IOM 82 1.08 (6.3) 1.11 —
DCM10E, DCM10Ef (FCM)1 1.10 (6.3CS)
1.11 (6.3.2)2
FBM201, WAI01A through D, WAW01A through F, WAX01A IOM 83 1.05 — —
through C
FBM202, FBM202B, WAI02A, WAV02A, WAX02A IOM 84 1.05 — —
FBM203, FBM203B, WRF03A, WRF03B, WRT03A, IOM 85 1.05 — —
WRT03B
FBM204, WLJ04A through C IOM 86 1.05 — —
FBM205 IOM 87 1.05 — —
FBM206, WPA06A IOM 88 1.05 — —
FBM207, FBM207B, FBM207C, WCI07A, WDI01A through IOM 89 1.05 (6.3) 1.11 —
E, WID07A through P 1.09 (6.3CS)
FBM211, WAH01A through D IOM 90 1.05 — —
FBM212 IOM 91 1.05 — —
FBM213 IOM 92 1.05 — —
FBM237, WAO37A through G IOM 93 1.05 — —
FBM241, FBM241B through D IOM 94 1.06 (6.3) 1.11 —
1.09 (6.3CS)
FBM242, WBO09A, WBO09B, WRO09A through D, IOM 95 1.06 (6.3) 1.11 —
WTO09A 1.09 (6.3CS)
FBM217 IOM 96 1.05 (6.3) 1.11 —
1.09 (6.3CS)
FBM243, FBM246 (FoxCom™) IOM 97 2.06 — —

51
B0400QD – Rev A Appendix C. EEPROM Revision Levels

Table C-5. 200 Series FBMs (DIN Rail Mounted FBMs) and FCMs (Continued)

Software Version
Devices Using IOM ID V6.3 V6.4 V7.0
FBM219 IOM 98 1.06 (6.3) 1.11 —
1.09 (6.3CS)

1.
The EEPROM version for Fieldbus Communication Modules (FCMs) is indicated in the fields
SOFTWARE REV A and SOFTWARE REV B in the Equipment Information display.
2.
V6.3.2 CP60 support for Cluster I/O and SPECTRUM Migration is available through the Cus-
tomer Satisfaction Center; it is not included with V6.4 I/A Series software.

For instructions on updating EEPROM firmware, see “EEPROM Update Action” of System Man-
agement Displays (B0193JC).

C.1 Firmware Upgrade

All Fieldbus Communications Modules (FCMs), FBI10E modules, and DIN rail mounted FBMs
that are at an EEPROM revision less than is indicated in the V7.0 column of Table C-5 must be
updated via an EEPROM upgrade.

! CAUTION
1. Performing an EEPROM update forces the module off-line until completion of
the EEPROM update.
2. For non-fault-tolerant stations, the station is off-line during the update.
3. Each module of the fault-tolerant pair must be updated to the same EEPROM
version.
4. The station must be rebooted with the V7.0 image before the EEPROM is
modified.

Select a workstation that has been designated during System Monitor configuration to have access
to the secured actions of the Equipment Change display.

C.2 Determining EEPROM Version

Determine the current EEPROM version before performing EEPROM updates. Perform the
following:
1. Enter System Management.
♦ For Display Manager, select Sys from the top menu bar, then select Sys_Mgmt
from the pull-down menu.
♦ For the FoxView system, select System from the top menu bar.
2. Select the System Monitor whose domain contains the station or module to be
EEPROM updated.
3. From the System Monitor Domain display, select the letterbug of the station or mod-
ule to be EEPROM updated.

52
Appendix C. EEPROM Revision Levels B0400QD – Rev A

4. Select the CONFIG soft key. The PIO Network appears, with the graphic for the station
selected by default (shows in black).
5. Select the EQUIP INFO soft key to access the Equipment Information display.
6. Select the down-arrow paging soft key located at the bottom right of the screen to dis-
play the second page of information. The PRIM EEPROM REV (and SHAD
EEPROM REV for fault-tolerant modules) indicates the current revision levels.

C.3 Performing EEPROM Update

If the EEPROM revision is less than is indicated in the V7.0 column of the appropriate table
listed above, then the EEPROM revision must be updated. Perform the following:
1. Perform the steps of the procedure “Determining EEPROM Version,” above.
2. If the EQUIP CHG soft key is unselectable (blue text), you must choose a
workstation with equipment change access.
3. Select the EQUIP CHG soft key to access the Equipment Change display.
4. On the Equipment Change display, ENABLE DOWNLOAD must be unselectable
(blue text), indicating that this is the current state. If not, select ENABLE DOWNLOAD.
5. Proceed to the relevant section below, based on the fault-tolerant configuration.

Non-Fault-Tolerant Station

! CAUTION
Selecting EEPROM UPDATE immediately takes the control station off-line.

a. Select EEPROM UPDATE.

b. The EEPROM update may take several minutes. Standard system messages indi-
cating the results of the update are sent to the system printer.
c. The station reboots at the completion of the update. Verify that the EEPROM
revision is the same value as is indicated in the V7.0 column of the appropriate
table listed above by selecting the EQUIP INFO soft key and displaying the second
page of information.

Fault-Tolerant Station
a. Select EEPROM UPDATE.
b. A dialog box appears offering the option to update the PRIMARY, SHADOW,
BOTH, or CANCEL. Perform the EEPROM update procedure on the shadow
module first to reduce the number of role changes.

53
B0400QD – Rev A Appendix C. EEPROM Revision Levels

! CAUTION
Selecting EEPROM UPDATE of the primary module causes a role change with the
shadow module. If the fault-tolerant station is running as a single station, selecting
EEPROM UPDATE takes the control station off-line. It is not recommended that
you select BOTH as it takes the station, instead of just one module, off-line during
the update.

c. The EEPROM update may take several minutes. Standard system messages
indicating the results of the update are sent to the system printer.
d. The station reboots at the completion of the update. Verify that the EEPROM
revision is the same value as is indicated in the V7.0 column of the appropriate
table listed above by selecting the EQUIP INFO soft key and displaying the second
page of information.
e. Repeat Steps a through d for the primary module, if you have not already per-
formed them.

33 Commercial Street
Foxboro, Massachusetts 02035-2099
United States of America
www.foxboro.com
Inside U.S.: 1-866-PHON-IPS (1-866-746-6477)
Outside U.S.: 1-508-549-2424 or contact your local Foxboro representative.
Facsimile: 1-508-549-4999
Printed in U.S.A. 1202