I/A Series System V8.2 Release Notes and Installation Procedures
I/A Series System V8.2 Release Notes and Installation Procedures
I/A Series System V8.2 Release Notes and Installation Procedures
REV C
Tables.................................................................................................................................... xv
Preface................................................................................................................................. xvii
Revision Information ............................................................................................................ xvii
Reference Documents .......................................................................................................... xviii
1. Release Overview............................................................................................................... 1
1.1 Installation Overview .......................................................................................................... 1
iii
B0700RN – Rev C Contents
4. Hardware Requirements.................................................................................................. 31
4.1 Minimum Workstation Hardware Requirements for V8.2 ................................................ 31
4.1.1 Memory Requirements for V8.2 ................................................................................ 31
4.1.2 Workstation Network Interface Card Support .......................................................... 31
4.2 Platform-Dependent Interface Card Limitations ............................................................... 32
4.3 Ethernet Networking Hardware ........................................................................................ 32
4.3.1 Supported Ethernet Switches ..................................................................................... 32
4.3.2 Supported Fieldbus-Only Ethernet Switch ................................................................ 33
4.3.3 Unsupported Ethernet Switches ................................................................................ 33
4.3.4 Ethernet Switches Requiring Firmware Updates ........................................................ 33
4.3.4.1 P0972YC and P0972WP ................................................................................... 33
4.3.4.2 P0972MJ and P0972MK Blades ....................................................................... 34
4.3.4.3 Firmware Updates for N-series Chassis Switches ............................................... 34
4.3.5 Connecting Ethernet Switches ................................................................................... 34
4.3.6 User Notes for Ethernet Networking Hardware ........................................................ 34
4.3.6.1 Link Speed Settings of Allied Telesyn Fiber-Optic NICs ................................... 34
4.3.6.2 Configuring Broadcast Suppression on V2 24-Port Switches ............................. 34
4.3.6.3 Interoperability of Mature and Preferred Chassis Switches ................................. 34
4.3.6.4 Configuring P0972MK/P0972MJ Ethernet Switches ........................................ 35
4.3.6.5 Metrobility Copper-to-Fiber Media Converter P0972XH ................................. 35
iv
Contents B0700RN – Rev C
v
B0700RN – Rev C Contents
vi
Contents B0700RN – Rev C
vii
B0700RN – Rev C Contents
9.2.8 White Process Alarm Page after Software Installation .............................................. 102
9.2.9 Restoring from Tape Backup ................................................................................... 102
9.2.10 Reinstalling the HP 3000 Printer Driver ............................................................... 102
9.3 System Configuration ..................................................................................................... 102
9.3.1 Changing Host of Nodebus CP ............................................................................... 102
9.4 Combined Mesh and Nodebus Systems .......................................................................... 103
9.4.1 Data Transfers Between the Nodebus and The Mesh Networks .............................. 103
9.5 System Monitor .............................................................................................................. 103
9.5.1 System Monitor Behavior after a Power Failure ....................................................... 103
9.6 Displays .......................................................................................................................... 103
9.6.1 Selecting DISABLE ALL REPORTS Twice from SMDH ...................................... 103
9.6.2 Availability of Reboot Station and EEPROM Update Selections from SMDH ....... 103
9.6.3 Performing Nodebus Cable Tests ............................................................................ 103
9.6.4 Excess Collisions Counter in the MAC Sublayer Counters Display ......................... 104
9.6.5 Eurotherm Device Status Not Correct in SMDH ................................................... 104
9.7 Applications .................................................................................................................... 104
9.7.1 Compound/Block Listbox Population ..................................................................... 104
9.8 Alarm Management Subsystem ....................................................................................... 104
9.8.1 Time/Date Formats in Alarm Messages ................................................................... 104
9.8.2 Moveable Alarm Manager Displays ........................................................................ 106
9.9 Integrated Control Configurator (ICC) ........................................................................... 106
9.9.1 Incorrect Parameter Display in ICC ........................................................................ 106
9.10 ICCAPI ......................................................................................................................... 106
9.10.1 Checkpoint Failure After LoadAll .......................................................................... 106
9.11 Object Manager ............................................................................................................ 106
9.11.1 OM API register_name Function .......................................................................... 106
9.12 Fieldbus Modules (FBMs) and Field Communication Modules (FCMs) ....................... 107
9.12.1 Addition of the “NOFAIL” DVOPTS Option for HART FBMs ......................... 107
9.12.2 Switching FBM214/215 Channel Assignments in Associated Child ECBs ............ 107
9.12.3 Configuring Fail-Safe for Proper Operation of FBM218 ...................................... 108
9.12.4 EEPROM Updating FBM220 and 221 ................................................................ 108
9.12.5 EEPROM Updating an FCM100Et ...................................................................... 108
9.12.6 Field Device System Integrator (FDSI) Subsystem ................................................ 108
9.12.6.1 Common Issue for FDSI Modules ................................................................. 108
9.12.6.2 OPC Client Driver for FDSI Modules, and Diagnostics
Application for OPC Clients ....................................................................................... 109
9.12.7 Displaying FoxCom Device Information After General Download ...................... 109
9.13 FOUNDATION fieldbus .................................................................................................. 110
9.13.1 DD Explorer – Adding Device Descriptor Files .................................................... 110
9.14 Control Stations ............................................................................................................ 110
9.14.1 Shadow ZCP270 Failure after Image Update ........................................................ 110
9.15 Control Blocks and Parameters ..................................................................................... 110
9.15.1 Changing the ECPOPT Parameter in ROUTR, BOUTR,
IOUTR, RINR, or BINR Blocks ..................................................................................... 110
9.15.2 PIDA with MODOPT Set at 7 or 8 ...................................................................... 110
9.15.3 Using the OSP 0 Instruction in the LOGIC Block ................................................ 110
9.15.4 PRIBLK and PRITIM Functionality in the IOUT Block ...................................... 111
viii
Contents B0700RN – Rev C
ix
B0700RN – Rev C Contents
x
Contents B0700RN – Rev C
xi
B0700RN – Rev C Contents
xii
Figures
1-1. Using Installation Procedures ........................................................................................ 4
3-1. Sample Network Topology Bridging a Nodebus and a Mesh Network Using an ATS .. 9
3-2. Comparison of Pre-Migration and Post-Migration Topologies .................................... 12
3-3. Adding Mesh Stations to a Single V6.x Node .............................................................. 13
3-4. Adding Mesh Stations to a Single V7.x Node .............................................................. 14
3-5. Connecting Multiple Nodes to The Mesh Network .................................................... 15
3-6. Removing the Carrierband LAN from a Nodebus/Mesh Network .............................. 16
3-7. Removing the Carrierband LAN from a Nodebus Network ........................................ 17
7-1. Class A Installation Flow Chart ................................................................................... 48
7-2. Class B Installation Flow Chart ................................................................................... 49
7-3. Class C Installation Flow Chart, Page 1 ...................................................................... 50
7-4. Class C Installation Flow Chart, Page 2 ...................................................................... 51
7-5. Class D Installation Flow Chart, Page 1 ...................................................................... 52
7-6. Class D Installation Flow Chart, Page 2 ...................................................................... 53
9-1. I/A Series Network Installation Dialog Box ............................................................... 100
9-2. Time Strobe Converter (P0972KA and P0973BW) .................................................. 113
11-1. Security Update Download Window ......................................................................... 160
xiii
B0700RN – Rev C Figures
xiv
Tables
3-1. Supported Software and Operations ............................................................................ 27
5-1. I/A Series V8.2 Software Media .................................................................................. 37
5-2. I/A Series V8.2 Software Media .................................................................................. 38
7-1. Media Required for P92 Style A or B Workstation ...................................................... 44
7-2. Upgrade Kits for P92 Style A or B Workstation .......................................................... 44
7-3. Media Required for P92 Style C Workstation ............................................................. 44
7-4. Upgrade Kits for P92 Style C Workstation ................................................................. 45
7-5. Media Required for P92 Style D Workstation ............................................................. 45
7-6. Upgrade Kits for P92 Style D Workstation ................................................................. 45
7-7. Media Required for P92 Style E Workstation ............................................................. 46
7-8. Upgrade Kits for P92 Style E Workstation .................................................................. 46
7-9. Media Required for P92 Style F Workstation .............................................................. 46
7-10. Upgrade Kits for P92 Style F Workstation .................................................................. 47
7-11. Media Required for P91 Server ................................................................................... 47
B-1. V8.2 Control Stations ............................................................................................... 145
B-2. V8.2 Address Translation Station .............................................................................. 145
B-3. Miscellaneous EEPROM Revision Levels .................................................................. 146
B-4. Software Versions of 100 Series FBMs (Y Form Factor) ............................................ 146
B-5. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) ............... 148
xv
B0700RN – Rev C Tables
xvi
Preface
This document assists you in planning and executing an installation of the I/A Series® V8.2
software. The document also includes user notes and describes the media and documentation
required to install your V8.2 system successfully.
Throughout these release notes, references are made to contacting the Global Customer Support
Center (CSC). In the U.S.A., call 1-866-746-6477, e-mail support@ips.invensys.com or visit
http://support.ips.invensys.com. Outside the U.S.A., contact your local (country) Invensys®
Foxboro® representative.
NOTE
Whenever you communicate with the Global CSC about these release notes, men-
tion the date on the cover and the title of the document. Knowing the date on the
cover prevents confusion caused by changed wording, different section numbers, or
mismatched page numbers in your reference.
Revision Information
For Revision C of this document, the following changes have been made:
♦ Changed contact e-mail and website address throughout the document.
♦ Added B0700AJ and B0700RU to “Reference Documents” below.
♦ Revised media in Chapter 5 “Windows System Setup”. Deleted K0173XS-B and
K0173XY-A, which are no longer shipped with the I/A Series software media. Added
K0174AM-A, which is shipped on the I/A Series V8.2 software Day 0 CD-ROM.
♦ Added installation procedures to Chapter 7 “V8.2 Installation Procedures”.
♦ Added Appendix E “Installing Microsoft Security Patches”.
NOTE
Microsoft does not allow the redistribution of security patches. Therefore, the
K0173XY-A Microsoft Windows XP Security Patch CD for Service Pack 2 is no
longer shipped as part of I/A Series software media distribution kits. However,
because these are the patches that were qualified for and tested with I/A Series V8.2
software, it is still recommended that you install the security patches that were con-
tained on this CD on V8.2 I/A Series workstations. You can download the patches
directly from the Microsoft web site to a CD or USB memory stick and use the
example batch file provided in Appendix E “Installing Microsoft Security Patches” to
install the patches during I/A Series software installation.
xvii
B0700RN – Rev C Preface
Reference Documents
The following documents provide detailed explanations on the topics described in this document.
Most of these documents are available on the I/A Series® Electronic Documentation CD-ROM.
The latest revisions are available through the Global CSC webpage http://support.ips.invensys.com.
Document Title Part Number
Address Translation Station User’s Guide B0700BP
AIM*AT Installation Guide B0193YM
AIM*Historian User's Guide B0193YL
Custom McAfee VirusScan Enterprise 8.0i Installation B0700CC
DIN Rail Mounted FBM Subsystem User’s Guide B0400FA
E7 Chassis and 16-Port Fiber (P0972MK/P0972MJ) Switches, Hardware and B0700CM
Software Configuration Instructions
Field Control Processor 270 (FCP270) User’s Guide B0700AR
FoxAPI Installation Guide B0193UC
FoxAPI™ User’s Guide B0193UD
FoxView™ and FoxDraw™ Release Notes B0700RJ
FoxView™ Software B0700BD
Hardware and Software Specific Instructions for Model P92*A Workstation (PW340) B0400HD
Hardware and Software Specific Instructions for Model P92*C Workstation (PW360) B0700BL
Hardware and Software Specific Instructions for Model P92*D Workstation (PW370) B0700BR
Hardware and Software Specific Instructions for Model P92*F Workstation (PW380) B0700CB
Hardware and Software Specific Instructions for Model P92*G Workstation (PW390) B0700CR
Hardware and Software Specific Instructions for Model P91*A B0700BW
Hardware and Software Specific Instructions for Model P91*B B0700CQ
I/A Series Configuration Component (IACC) User’s Guide B0400BP
Integrated Control Block Descriptions B0193AX
Message Manager User’s Guide B0700AJ
Message Manager Release Notes B0700RU
System Administration Guide (Windows XP Operating System) B0400HE
System Definition 2.8 Release Notes B0193XW
System Definition: A Step-By-Step Procedure B0193WQ
System Management Displays B0193JC
The MESH Control Network Architecture Guide B0700AZ
The MESH Control Network System Planning and Sizing B0700AX
The MESH Network Configuration Tool B0700CA
Time Synchronization User’s Guide B0700AQ
Z-Module Control Processor 270 (ZCP270) User’s Guide B0700AN
xviii
1. Release Overview
This chapter contains an introduction to the V8.2 release and an overview of V8.2 software
installation.
I/A Series Release 8.2 software provides enhancements to the I/A Series core software and pro-
vides additional functionality and security to I/A Series control systems. Features of this release
are described in Chapter 2 “Features of the V8.2 Release”.
V8.2 software is compatible with all P92 workstations, including Styles A through F, and P91
servers. These workstation styles include the Dell® Precision Workstation 340 (Styles A and B),
360 (Style C), 370 (Styles D and E), and 380 (Style F), and the Dell PowerEdge® 2800 and 2900
servers, as well as later styles of the Precision Workstation and PowerEdge stations. Note that
upgrading a V7.x workstation to V8.2 will require different network interface cards and possibly
additional memory. The minimum memory requirement for a workstation to run in a V8.2 sys-
tem is 512 MB.
1
B0700RN – Rev C 1. Release Overview
NOTE
References to Version 8.1 also apply to Version 8.1.1.
An overview of the steps required to install I/A Series V8.2 software is given in Figure 1-1.
I/A Series V8.2 software is provided on CD-ROMs and 3.5-inch diskettes.
NOTE
Microsoft does not allow the redistribution of security patches. Therefore, the
K0173XY-A Microsoft Windows XP Security Patch CD for Service Pack 2 is no
longer shipped as part of I/A Series software media distribution kits. However, it is
still recommended that you install the security patches that were contained on this
CD on V8.2 I/A Series workstations; these were the patches that were qualified for
and tested on I/A Series V8.2 software. Refer to Appendix E “Installing Microsoft
Security Patches” for information.
To migrate databases and preserve customized files for use on a new V8.2 system, you can copy
them from your existing system. After the new software is loaded, the databases and customized
files can be restored to the new workstation. For information about migrating specific hardware
and/or control databases to a new V8.2 system, refer to Appendix A “Files to Back Up/Restore”.
In addition to the hardware and software instruction document shipped with your workstation,
the following documents provide additional information regarding the installation procedures:
♦ System Administration Guide (Windows XP Operating System) (B0400HE)
♦ System Definition: A Step-by-Step Procedure (B0193WQ)
♦ I/A Series Configuration Component (IACC) User’s Guide (B0400BP).
Prior to the installation of I/A Series software, you must install all hardware components into
your workstation and upgrade drivers as required. Refer to the hardware and software specific
instruction document shipped with your workstation and Appendix C “Installing/Updating NIC
Drivers” for procedures.
There are four scenarios for installing V8.2 software categorized into “installation classes” for the
purposes of this document. They are summarized in the following sections and illustrated in
Figure 1-1. Detailed flow charts and installation instructions for each of the classes are given in
Chapter 7 “V8.2 Installation Procedures”. After determining which class of installation proce-
dures your system requires, refer to Chapter 7 “V8.2 Installation Procedures” for details of the
installation procedures.
Class A Installation
Class A installation involves a brand new installation of a V8.2 system. This installation does not
require the addition of ATS modules, and includes a Day 0 installation of V8.2 software. See
“Class A Installation” on page 48.
Class B Installation
Class B installation involves installing V8.2 on an existing V8.0 Revision B or V8.1 system. In
this class of system installation, the addition of ATS modules is not required and there is no
merge with an existing Nodebus system. This installation includes a Day 0 installation of V8.2
software. See “Class B Installation” on page 49.
2
1. Release Overview B0700RN – Rev C
Class C Installation
Class C installation involves merging two existing separate Mesh network and Nodebus systems
with the requirement that the Nodebus control stations stay on-line. This scenario requires the
addition of The Mesh network stations to the system configuration of the Nodebus system. A
V8.2 Day 0 installation is required on The Mesh network stations, and a Day 1 Commit is
required on the Nodebus stations.
Because the merge of the two systems in SysDef causes The Mesh station addresses to change, all
Mesh stations must be rebooted. The Nodebus control stations will stay on-line.
See “Class C Installation” on page 50.
Class D Installation
Class D installation involves merging two existing separate Mesh network and Nodebus systems
with the requirement that Mesh network control stations stay on-line. This scenario requires the
addition of Nodebus network stations to the system configuration of The Mesh system. The
existing Nodebus stations will require reinstallation of the appropriate Day 0 (and release update)
software. Existing Mesh workstations will require a Day 0 V8.2 software installation. If already
updated with the V8.2 image revision level, existing Mesh control stations will remain on-line.
Because the merge of the two systems in SysDef causes the Nodebus station addresses to change,
all Nodebus stations must be rebooted. The Mesh control stations that have been updated with
the V8.2 image revision level will stay on-line.
See “Class D Installation” on page 52.
3
B0700RN – Rev C 1. Release Overview
Start
Read Chapter 1,
"Release Overview"
Review Chapter 3,
"Upgrade Considerations"
Review Chapter 4,
"Hardware Requirements"
Review Chapter 5,
"Windows System Setup"
Review Chapter 6,
"Defining Your System"
Have you
generated an Yes
upgrade plan
?
No
Generate a detailed
site-specific upgrade plan.
Merging Keeping
Nodebus and Yes Nodebus No
Mesh Networks On-Line
? ?
No Yes
No
4
2. Features of the V8.2 Release
This chapter describes the major features and enhancements included with the I/A Series V8.2
software release.
I/A Series V8.2 software release continues to extend the functionality and security of I/A Series
workstations. New functionality for the V8.2 Windows-based workstations includes:
1. The ability of Windows XP and Server 2003 workstations to host and configure
Nodebus based controllers whose nodes are connected to the Mesh network via
Address Translation Station modules
2. Upgrade of the Windows XP operating system to Service Pack 2
3. Numerous maintenance fixes for the FCP270, ZCP270, and ATS images
4. FoxView/FoxDraw Version 10.1, which includes important new functionality for
customers who will connect their V8.2 system to a Nodebus-based system via an ATS
5. P92 and P91 Windows-based workstations shipped with the latest release of McAfee®
Virus Scan V8.0i software, which is compatible with I/A Series V8.2 software
6. The ability to host FCP270 controllers with 100 Series FBMs was included in the
V8.1.1 release for Windows XP based systems. That capability is also applicable to
Server 2003 workstations as part of the V8.2 release.
2.1 Security
The new Windows XP Service Pack 2 software and the new platform running Workstation Server
2003 operating system with Service Pack 1 provide improved security in terms of resistance to
unauthorized access or external attack. For customers connecting their workstations to plant
intranets, the embedded Windows Firewall can be configured to provide an additional level of
security.
Further, the new release of McAfee Virus Scan V8.0i software provides the latest release of anti-
virus functionality to provide the best protection against unauthorized access or external attack.
I/A Series workstations are equipped with embedded virus protection, assuring continuous pro-
tection from the factory to the staging floor to the customer’s plant.
New P92 workstations and P91 servers are shipped with McAfee V8.0i embedded on the system
Restore CD. Customers who are upgrading existing P92 workstations that have McAfee Version
7.1 will need to purchase the McAfee V8.0i software directly from McAfee.
During V8.2 I/A Series software installation, it is recommended that you also install the tested
and qualified security patches from Microsoft. Refer to Appendix E “Installing Microsoft Security
Patches” for information on how to install the security patches.
5
B0700RN – Rev C 2. Features of the V8.2 Release
6
3. Upgrade Considerations
This chapter presents upgrade considerations for customers who are either upgrading a pre-V8.2
Mesh system to V8.2 or are performing a transition/migration of an I/A Series Nodebus system
to a system that is a mix of V8.2 Mesh components and V7.x /6.x Nodebus components.
7
B0700RN – Rev C 3. Upgrade Considerations
In order to achieve the highest possible performance using a multi-node system with an ATS run-
ning in Extender mode, it is strongly recommended that you create a new node on the existing
Carrierband LAN as a bridging node. The new bridging node would consist of exactly one LI and
one ATS, and would carry all traffic between the two networks.
If a new node is created as a bridging node without a boot host, verify that the LAN for the
remote boot host is not too heavily loaded. If the remote boot host is on a node with a LAN that
is too heavily loaded, there may be problems booting the remote LI on the bridging node.
The bridging node is the only node in the system that can reach all other nodes using IP commu-
nications. If you have a utility based on IP communications that you want to run from a single
place, then a workstation should be added to the bridging node for this purpose. The workstation
on the bridging node will be able to access all nodes connected by LAN as well as The Mesh and
all nodes connected to The Mesh with ATS stations. This approach should only be used for utili-
ties that do not generate high Nodebus traffic; if they are IP based applications, they should com-
municate among nodes via a non I/A Series Ethernet port.
Also note that only one node in the network can contain both an LI and an ATS, and each node
cannot contain more than one ATS. A node that has an ATS but does not have an LI has the same
configuration restrictions as a node with an LI. For example, there is a maximum limit of 64 sta-
tions on the node, including the ATS.
See Figure 3-1 for a sample network topology.
3.1.1.1 LI Mode
An ATS operates in LI mode when there is not an LI on the same node. In this mode, the ATS
acts as an LI. Up to 30 ATSs can operate in LI mode on any given system.
8
3. Upgrade Considerations B0700RN – Rev C
mode and to minimize the traffic on the Nodebus, it is strongly recommended that the bridging
node comprises only an ATS and an LI.
Carrierband LAN
LI
Nodebus
Nodebus
AW LI AW
AW
Nodebus
CP ATS CP
Extender Mode CP
ATS ATS
LI Mode LI Mode
The Mesh
AW FCP FCP
Bridging node
Figure 3-1. Sample Network Topology Bridging a Nodebus and a Mesh Network Using an ATS
The amount of traffic through the LI, even in the configuration shown above, may be too high if
you have not analyzed the traffic rate in and out of the nodes being moved.
Once all LIs are removed the bridging node can be removed. See Figure 3-7 for an example of this
migration strategy.
9
B0700RN – Rev C 3. Upgrade Considerations
Control Configuration
Control stations must be at a certain revision level to support block configuration from a Mesh
workstation. Revision levels are:
♦ CP60 @ 6.5.3 Firmware 3.30
♦ CP30B @ 6.1.6 Firmware 3.30
♦ CP40B @ 6.1.6 Firmware 3.30
♦ DI30B @ 6.5.2 Firmware 3.31
♦ AB30B @ 6.1.6 Firmware 3.31
♦ MG30B @ 6.1.6 Firmware 3.31
System Management Displays (B0193JC) provides detailed procedures for updating the images of
single and fault-tolerant stations and for verifying that the station is at the correct image level
using the Equipment Change and Equipment Information displays.
Boot Hosting
♦ Remote boot hosting through an ATS is a low priority activity for the ATS as it is for
the LI on Nodebus. The LI is limited to two stations booting simultaneously.
♦ Remote booting through an LI is supported. This applies to Nodebus stations.
♦ Remote booting through both an ATS and an LI is not supported.
♦ On-Line Upgrade (OLUG) of pre-8.0 stations will not be supported when boot host-
ing across the ATS. Customers requiring OLUG capability are encouraged to upgrade
to CP270 control stations.
♦ While SysDef and the IACC System Editor allow the configuration support needed
for boot hosting of Nodebus stations from Mesh workstations, they do not prevent
the configuration of unsupported station types. Additionally, the Check Configura-
tion utility does not indicate that the configuration is illegal.
Dump Packets
♦ Firmware 3.30 or later is needed to support CP dump packets through The Mesh.
10
3. Upgrade Considerations B0700RN – Rev C
11
B0700RN – Rev C 3. Upgrade Considerations
Pre-Migration Topology
Carrierband LAN
LI LI LI
Node ID 1 Node ID 2 Node ID 3
AW
Nodebus
Nodebus
AW AW
Nodebus
CP CP CP
Post-Migration Topology
Nodebus
Nodebus
Nodebus
AW AW AW
CP CP CP
The Mesh
AW FCP FCP
Keys
Nodebus 5 Mbps
12
3. Upgrade Considerations B0700RN – Rev C
AW
Nodebus
CP
ATS
LI Mode
The Mesh
AW FCP FCP
The Mesh
13
B0700RN – Rev C 3. Upgrade Considerations
V7.x Ethernet A
RCNI AW
AW
Nodebus
CP
ATS
LI Mode
The Mesh
AW FCP FCP
The Mesh
14
3. Upgrade Considerations B0700RN – Rev C
There is a period between the removal of the LAN Interfaces and connection of the Address
Translation Stations when the node is not connected to a backbone. During this period, inter-
node communication to and from the node is lost.
Carrierband LAN
Nodebus LI
Nodebus
AW AW
LI
AW
Nodebus
CP CP
ATS
Extender Mode CP
ATS ATS
LI Mode LI Mode
The Mesh
AW FCP FCP
Bridging node
15
B0700RN – Rev C 3. Upgrade Considerations
Carrierband LAN
LI LI*
Nodebus
Nodebus
Nodebus
AW AW AW
CP CP CP
The Mesh
AW FCP FCP
Nodes added to The Mesh * This LI and ATS were originally on the bridging node on
the combined Mesh/Nodebus system. The ATS has
been changed from Extender mode to LI mode with
Bridging node an Image Update.
16
3. Upgrade Considerations B0700RN – Rev C
NOTE
A node containing a control station but not its workstation host can be migrated to
the Mesh without also migrating the node that contains the host. However, if a
Nodebus workstation is a boot host of a station that is on another node, then the
stations must be connected through a LAN or an ATS, but not both. The stations
cannot be connected over a bridging node.
There is a period between the removal of the Carrierband LAN and LIs and connection of the
ATSs when the node is not connected to a backbone. During this short period, inter-node com-
munication to and from the node is lost. Connections are lost and recovered on reconnection.
Figure 3-7 shows the Carrierband LAN and all LIs being simultaneously removed and replaced
with ATSs.
Carrierband LAN
LI LI LI
Removed items
Nodebus
Nodebus
Nodebus
CP AW AW
CP CP CP
The Mesh
Added/Removed Items
17
B0700RN – Rev C 3. Upgrade Considerations
18
3. Upgrade Considerations B0700RN – Rev C
19
B0700RN – Rev C 3. Upgrade Considerations
switch on The Mesh network. In System Definition, first drag the nodes to the ATS, then delete
the LI. Once you perform these steps for all nodes, you can delete the Carrierband LAN. Refer to
System Definition V2.8 Release Notes (B0193XW) for information on configuring an ATS.
You can configure a node to act as a bridging node so that you do not need to migrate all nodes to
The Mesh at the same time. To create the bridging node in System Definition, create an ATS and
attach the ATS to a node that is still attached to the Carrierband LAN. Then manually configure
the ATS to attach to two switches using the Hardware Editor in System Definition. Only one
bridging node can exist in a system.
After connecting the ATS and nodes together, ensure that all nodes have a unique Node ID. If
not, the Check Configuration routine will detect it. The Node ID is the last two digits of the
node’s NSAP address, which is viewable by double-clicking on the node to open the Hardware
Editor. If there are any nodes that share the same Node ID, then assign a new NSAP to one of the
nodes using the Hardware Editor. For a node that is attached to only an ATS (and not a Carrier-
band LAN) the suggested NSAP values are 000001 or 0001xx (where xx is a value from 01 to 31).
All nodes attached to a Carrierband LAN must have a NSAP in the form of 0001xx. Please be
aware that modifying the NSAP address of a node will also change the IP addresses assigned to the
workstations residing on that node.
20
3. Upgrade Considerations B0700RN – Rev C
To prepare for a successful upgrade, there are several procedures you need to follow prior to
installing a V8.2 system:
♦ All V8.x stations that were installed using Commit diskettes created with a pre-V2.8
System Definition must be Recommitted using Commit diskettes created with a V2.8
System Definition configuration if an ATS will be added to the system. You will need
to upgrade your configuration to SysDef 2.8.
♦ If you plan to have V8.0B workstations running either temporarily or permanently on
the I/A Series V8.2 system, you must update the Master Timekeeper on the V8.0B
workstations. To accomplish this, you need to install the Pre-V8.1 Compatibility Dis-
kette (K0173XN) after the Commit process on V8.0B workstations.
♦ If you have merged (or are merging) Mesh and Nodebus systems, you must perform a
Post-Commit for Pre-8.0 using the Pre-V8.1 Compatibility Diskette (K0173XN) on
Nodebus workstations. This step adds addressing information to the host files on
Nodebus workstations, and must be done on all Nodebus workstations after every
Commit installation or any installation where the workstation operating system is
selected for installation.
Nodebus controllers will not need to be rebooted provided that system configuration is performed
as described above, i.e., by adding the V8.2 Mesh stations to the Nodebus configuration in Sys-
tem Definition, as opposed to adding V6.x/V7.x Nodebus stations to a Mesh configuration.
The V8.2 System Monitor can monitor Nodebus and Mesh stations. The Nodebus System Mon-
itor can monitor the Nodebus stations only.
NOTE
The FCP270 V3.1 image that was released with I/A Series V8.1.1 software is also
superseded by V3.8.
If you are running a quick fix that is not listed above, do not install it. Contact Global CSC for
information on the latest available quick fixes supported by V8.2 software.
21
B0700RN – Rev C 3. Upgrade Considerations
that have been rehosted by a Mesh workstation. Using ICC is not supported from Nodebus work-
stations to Mesh control stations.
You can configure the control database without needing to reboot the control station. Keep in
mind that a Windows workstation can only configure those control stations that it hosts.
3.4 Interoperability
The following sections define the interoperability and compatibility of base software and applica-
tion software between the I/A Series V8.x release (The Mesh network) and previously released
standard I/A Series products (Nodebus-based networks).
In general, Nodebus workstations will not have full access to functionality that is part of The
Mesh network released with V8.0x. For example, in a configuration consisting of a mix of Node-
bus and Mesh stations:
♦ Nodebus workstations cannot bring up Detail displays for new block types introduced
in V8.x (such as COUTR)
♦ If a Default display references any new V8.x block parameters, the new block parame-
ters appear cyan if the display connects to a block on a pre-V8.x system
♦ Nodebus workstations cannot perform all system operations (such as Image Updates)
on the new FCP270 and ZCP270 station types.
New features, for example, new blocks, block parameters, station types, introduced in a release are
generally unknown to workstation software subsystems and applications from previous releases.
The following sections describe the interoperability of various databases, displays, software appli-
cations, and so forth between workstations/controllers on the Nodebus and workstations/control-
lers on The Mesh.
22
3. Upgrade Considerations B0700RN – Rev C
System Management Displays (B0193JC) provides detailed procedures for updating the images of
single and fault-tolerant stations and for verifying that the station is at the correct image level
using the Equipment Change and Equipment Information displays.
The configuration of control stations via the Integrated Control Configurator (ICC) between a
Mesh workstation and a Nodebus controller is supported for specified Nodebus controllers (refer
to “Station Hosting” on page 9). Configuration between a Nodebus workstation and a Mesh con-
troller is not supported. You can load IACC client software on any workstation running the Win-
dows XP operating system. IACC client software can configure any controller (Nodebus or Mesh)
as long as its workstation host is at I/A Series software release V6.4 or greater.
Configuration from both IACC and FoxCAE® should be done through a separate network.
For FoxCAE, downloads can be done using SaveAll diskettes or using a FoxAPI network connec-
tion. This means that FoxCAE can download to any other workstation once the initial setup is
complete.
23
B0700RN – Rev C 3. Upgrade Considerations
NOTE
V10.1 FoxView software runs on Mesh workstations, and V9.0.2 FoxView software
runs on Nodebus workstations.
24
3. Upgrade Considerations B0700RN – Rev C
3.4.8 Timekeeping
The Master Timekeeper (MTK) resides on The Mesh and provides time updates to all stations on
the Mesh and Nodebus networks. The Master Timekeeper will automatically run on a V8.x work-
station and will automatically disable any potential Nodebus Master Timekeeper. Refer to “Day-
light Saving Time (DST) Control” on page 81 for additional information on timekeeping.
3.4.10 Historian
Collection of historical data from the Mesh and Nodebus is fully supported by the INFORMIX-
based Historian software, FoxHistory software, and AIM*Historian software. You can install the
INFORMIX-based Historian software, FoxHistory software, or AIM*Historian software on
Nodebus workstations. On Mesh workstations, you should only install AIM*Historian 3.2.4 or
later.
In previous versions of I/A Series system software releases for The Mesh, in order to properly view
historical trends on a Mesh workstation from a historian residing on a Nodebus workstation (and
vice versa), both the Mesh and Nodebus workstations be configured to use IATIME. This is no
longer required; The Mesh can now be configured to use UTC time.
3.4.11 IP Communications
IP communications cannot be accomplished directly from one station to another if the stations
are separated by both an LI and an ATS, that is, across both the Carrierband LAN and The Mesh.
IP communications can be accomplished directly from one station to another if the stations are
separated by the Carrierband LAN only or The Mesh only.
If you use the preferred method of migrating all nodes on the Nodebus by replacing LIs with
ATSs, IP communication is not affected, and there is no special action that you need to take.
Applications or scripts that are based on IP communications can then be run from anywhere in
the system.
When a LAN exists, only stations on the bridging node, which has both an LI and an ATS, can
reach all other stations without needing to pass through both an LI and an ATS. Consequently, if
25
B0700RN – Rev C 3. Upgrade Considerations
your system uses a bridging node, applications or scripts that are based on IP communications
must be run from the bridging node in order to be able to communicate with stations on all nodes
within the system.
26
3. Upgrade Considerations B0700RN – Rev C
Nodebus to
Nodebus Mesh to Nodebus (through Additional
Description to Mesh Nodebus The Mesh network) Information
Alarm Management Subsystem
Aprint process alarm messages Yes Yes Yes page 20,
page 25
Alarm History No No Yes (Solaris only) page 25
Alarm backup No No Yes page 25
Common Alarm Groups No No Yes page 25
Station Hosting
Station hosting No Yes Yes page 9,
page 16
Rehosting without reboot of control station No No No page 9
Station Dump Packets No Yes Yes, same as 7.1. page 10
Control Configuration
Control configuration using ICC No Yes Yes page 21,
page 22
Control configuration using FoxCAE 5.1 Yes Yes Yes page 21,
page 22
Control configuration using IACC V2.x Yes Yes Yes page 21,
page 22
Display Functionality/FoxView and FoxDraw Software
Process graphics Yes Yes Yes page 23
Default displays Yes Yes Yes page 23
FoxSelect Yes Yes Yes page 23
Real-time trends Yes Yes Yes page 23
Historical trends Yes Yes Yes page 25
Application Packages
Operator Action Journal Yes Yes Yes –
Services and APIs
AIM*API Yes Yes Yes page 26,
page 28
Aprint API Yes Yes Yes page 20,
page 25
CSA API Yes Yes Yes page 24,
page 100,
page 140
FoxAPI Yes Yes Yes page 26,
page 28,
page 39
I/A Series Batch API Yes Yes Yes –
ICCAPI No Yes Yes (for Solaris only) –
IPC API Yes Yes Yes page 28
OM API Yes Yes Yes page 28
OM data as source Yes Yes Yes page 28
OM data as sink Yes Yes Yes page 28
27
B0700RN – Rev C 3. Upgrade Considerations
Nodebus to
Nodebus Mesh to Nodebus (through Additional
Description to Mesh Nodebus The Mesh network) Information
Printer services Yes Yes Yes page 20,
page 25
Timekeeper services N/A Yes N/A page 81
System Configuration/System Definition
System configuration using System N/A N/A N/A page 19,
Definition page 41
System Management and System Monitor
SMDH actions No Yes Yes page 24
System Monitoring No Yes Yes page 24
Device Monitor No Yes Yes page 24
Network Fault Detection (NFD)
Network Fault Detection (NFD) N/A N/A Yes page 24
28
3. Upgrade Considerations B0700RN – Rev C
29
B0700RN – Rev C 3. Upgrade Considerations
30
4. Hardware Requirements
This chapter provides hardware and software requirements and lists supported and
unsupported hardware and software.
31
B0700RN – Rev C 4. Hardware Requirements
The following NICs available for use with previous I/A Series releases are not available for use
with V8.2 I/A Series software:
♦ The Intel Pro/1000 MT dual-port NIC (P0972UU)
♦ Intel 21143-Based PCI Fast Ethernet Adapter/NIC
♦ 3C905CX-TX 10/100 Base-TX copper Ethernet PCI card (P0922KY)
♦ 100Base-FX fiber optic Ethernet PCI card w/MTRJ (P0972UT)
♦ 10/100 Base-TX copper Ethernet PCI card (P0972UZ).
For information on which Ethernet network cards shipped with each workstation type, refer to
the appropriate subsection under “Platform-Specific Hardware Upgrade Kits and Required
Media” on page 43. For installation instructions, refer to the hardware and software installation
document shipped with your workstation.
If you are migrating the workstation from a V7.x system, you may only have one network inter-
face card installed. In this case, you must be sure that the workstation has a free PCI slot for the
second Mesh connection.
You must also make sure that the correct drivers are installed for these NICs. The correct drivers
are located in the driver CD-ROM (K0173XA Revision D) supplied with I/A Series V8.2
software. Refer to Appendix C “Installing/Updating NIC Drivers”.
32
4. Hardware Requirements B0700RN – Rev C
33
B0700RN – Rev C 4. Hardware Requirements
! CAUTION
When using chassis switches in the various topology configurations, the N-7 series
chassis switches (P0972YE) are not compatible with E-7 series chassis switches
(P0972MK) at the root switch level. Do not use an E-7 and an N-7 switch together
as a root and backup root switch.
34
4. Hardware Requirements B0700RN – Rev C
! CAUTION
WebView should not be used for network switch configuration changes. It has been
observed that performing configuration changes via WebView can and will cause
configuration issues resulting in system-wide failures. This tool is only for network
switch observation only. All configuration changes should be perform via the CLI
port of the switch.
To ensure proper re-spanning, be sure to configure the switches as described in E7 Chassis and 16-
Port Fiber (P0972MK/P0972MJ) Switches, Hardware and Software Configuration Instructions
(B0700CM).
35
B0700RN – Rev C 4. Hardware Requirements
36
5. Windows System Setup
Use this chapter to verify that the identified parts have been provided. If you find or suspect any
discrepancies, contact Global CSC for assistance. Once you verify the equipment, cabling,
documentation, and media, proceed with the system installation.
37
B0700RN – Rev C 5. Windows System Setup
NOTE
Microsoft does not allow the redistribution of security patches. Therefore, the
K0173XY-A Microsoft Windows XP Security Patch CD for Service Pack 2 is no
longer shipped as part of I/A Series software media distribution kits. However,
because these are the patches that were qualified for and tested with I/A Series V8.2
software, it is still recommended that you install the security patches that were con-
tained on this CD on V8.2 I/A Series workstations. Refer to Appendix E “Installing
Microsoft Security Patches” for information on installing the security patches dur-
ing I/A Series V8.2 software installation.
38
5. Windows System Setup B0700RN – Rev C
39
B0700RN – Rev C 5. Windows System Setup
40
6. Defining Your System
This chapter describes the requirements for creating a Commit diskette.
You must use System Definition V2.8 software to create, import, and/or edit your configuration,
and to create a Commit diskette.
For instructions on installing the software, refer to System Definition Release Notes (B0193XW).
To create a Commit diskette, follow the procedures in System Definition: A Step-By-Step Procedure
(B0193WQ).
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.) Use the V8.2 Media Distribution Diskette (K0174AS) supplied with the V8.2 media
kit to produce the V8.2 Commit diskette.
NOTE
Be sure to label the Commit diskette with the I/A Series versions on which it can be
used, for example, V8.2.
For Day 0 installations such as V8.2, the Commit diskette must be a Day 0 type or if the Commit
diskette is reconciled, all packages hosted by the station you are installing must have the Software
Install status NOTYET.
NOTE
If installation procedures specify importing a reconciled system configuration, make
sure the configuration is reconciled before exporting it.
41
B0700RN – Rev C 6. Defining Your System
2. Uninstall the old System Definition software, and install System Definition V2.8 soft-
ware. Refer to System Definition Release Notes (B013XW) for instructions to uninstall
the previous version of System Definition software and install V2.8.
3. Import the configuration to be upgraded by selecting File > Import > Standard Sys-
Def Export Diskette, and then selecting Yes in the Upgrade Configuration dialog
box.
Modify and check this configuration as necessary, and then create the Commit diskette.
42
7. V8.2 Installation Procedures
This chapter describes the procedure for the installation of V8.2 software on an I/A Series
system. Note that actions identified in each step below are dependent on which installation
scenario is selected.
NOTE
Any references to V8.1 also apply to V8.1.1.
NOTE
V8.2 does not support the migration of workstation integrators.
43
B0700RN – Rev C 7. V8.2 Installation Procedures
In addition to the media listed above, if the workstation does not conform to the specifications
listed in Chapter 4 “Hardware Requirements”, you may need one or more of the upgrade kits
listed in Table 7-2. The P92 Styles A and B were shipped with a minimum memory configuration
of 256 MB and the 3Com 3C905C Ethernet PCI card. A workstation with this base configura-
tion needs to be upgraded with additional memory and the supported NICs.
In addition to the media listed above, if the workstation does not conform to the specifications
listed in Chapter 4 “Hardware Requirements”, you may need one or more of the upgrade kits
listed in Table 7-4. The P92 Style C was shipped with a minimum memory configuration of 256
MB and one or more of the following Ethernet cards: 3Com® 3C905C Ethernet card
(P0922KY), Allied Telesyn™ fiber-optic Ethernet card (P0972WD), or Intel dual-ported Ether-
net card (P0972UU).
44
7. V8.2 Installation Procedures B0700RN – Rev C
In addition to the media listed above, if the workstation does not conform to the specifications
listed in Chapter 4 “Hardware Requirements”, you may need one or more of the upgrade kits
listed in Table 7-6. The P92 Style D was shipped with a minimum memory configuration of 512
MB and one or more of the following Ethernet cards: 3Com® 3C905C Ethernet card
(P0922KY), Allied Telesyn™ fiber-optic Ethernet card (P0972WD), or Intel single-port Ethernet
card (P0923AA).
45
B0700RN – Rev C 7. V8.2 Installation Procedures
In addition to the media listed above, if the workstation does not conform to the specifications
listed in Chapter 4 “Hardware Requirements”, you may need one or more of the upgrade kits
listed in Table 7-8. The P92 Style E was shipped with a minimum memory configuration of 512
MB and one or more of the following Ethernet cards: 3Com® 3C905C Ethernet card
(P0922KY), Allied Telesyn™ fiber-optic Ethernet card (P0972WD), or Intel single-port Ethernet
card (P0923AA).
In addition to the media listed above, if the workstation does not conform to the specifications
listed in Chapter 4 “Hardware Requirements”, you may need one or more of the upgrade kits
listed in Table 7-10. The P92 Style F was shipped with a minimum memory configuration of
512 MB and one or more of the following Ethernet cards: 3Com® 3C905C Ethernet card
46
7. V8.2 Installation Procedures B0700RN – Rev C
(P0922KY), Allied Telesyn™ fiber-optic Ethernet card (P0972WD), or Intel single-port Ethernet
card (P0923DV).
Because the P91 server was shipped with a minimum memory configuration of 1 GB and sup-
ported NICs (P0923DV or P0972WD), you should not need to upgrade these machines with
new hardware to run with I/A Series V8.2 software. However, check the NIC driver dates and ver-
sions to make sure that the correct NIC drivers are installed. Refer to Appendix C “Install-
ing/Updating NIC Drivers”.
47
B0700RN – Rev C 7. V8.2 Installation Procedures
* Set the date and time only on systems on The Mesh control network
that do not have the external GPS time capability. Set the time zone
on all workstations.
48
7. V8.2 Installation Procedures B0700RN – Rev C
No
49
B0700RN – Rev C 7. V8.2 Installation Procedures
50
7. V8.2 Installation Procedures B0700RN – Rev C
Any Yes
Install both of the V8.2 trailer CD- V8.0B/V8.1 Perform Day 1 Commit of V8.0B/V8.1
ROMs (Section 7.4.1.4). stations stations.
?
No
Merge CSA and load control data- Set the letterbug and perform an
bases (Section 7.4.2 and 7.4.3). IMAGE UPDATE of ATSs off the
Nodebus network** via their
configured hosts (Section 7.4.9).
Verify ATS image versions in
Perform EEPROM Updates SMDH.
(Section 7.4.4).
** It is recommended that you set the letterbug and perform the IMAGE UPDATE while the
ATS modules are not connected to the Nodebus network. This can be accomplished using
a spare 1.8 mounting structure. See Section 7.4.9 for details.
51
B0700RN – Rev C 7. V8.2 Installation Procedures
Generate Day 0 Commits for Nodebus Generate Day 0 Commit diskette for
versions 7.0, 6.4, 6.2, 6.1 using correct The Mesh using the V8.2 Media
Media Distribution Diskette. Distribution Diskette (10091).
52
7. V8.2 Installation Procedures B0700RN – Rev C
Any Yes
Install both of the V8.2 trailer CD- V8.0B/V8.1 Perform Day 1 Commit of V8.0B/V8.1
ROMs (Section 7.4.1.4). stations stations.
?
No
Merge CSA and load control data- Set the letterbug and perform an
bases (Section 7.4.2 and 7.4.3). IMAGE UPDATE of ATSs off the
Nodebus network via their
configured hosts (Section 7.4.9).
Verify ATS image versions in
Perform EEPROM Updates
SMDH.
(Section 7.4.4).
53
B0700RN – Rev C 7. V8.2 Installation Procedures
Class A Installations
1. Create a new configuration in SysDef V2.8 and check the configuration until it passes
all checks.
2. Create a V8.2 Day 0 Commit diskette using the V8.2 Media Distribution Diskette.
Class B Installations
1. If not already done, reconcile the current Mesh configuration.
2. Import the configuration into SysDef V2.8.
3. For existing V8.0B/V8.1 stations going to V8.2, set the configuration to Day 0 by
marking the installation status of all software packages as “NOTYET”. Refer to Sys-
tem Definition on-line help for procedures.
4. Configure any new V8.2 stations and peripherals.
5. Create a V8.2 Day 0 Commit diskette using V8.2 Media Distribution Diskette
(10091).
6. If there are any V8.0B or V8.1 stations that will not be upgraded to V8.2 at this time,
create a Day 1 V8.0B/V8.1 Commit diskette using the V8.0B Media Distribution
Diskette (10091).
Class C Installations
1. If not already done, reconcile the current Mesh configuration.
2. Import The Mesh configuration into SysDef V2.8, and perform V8.2 configuration
changes.
3. Set The Mesh configuration to Day 0 by marking the installation status of all software
packages as “NOTYET”. (Refer to System Definition on-line help for procedures.)
Save the configuration.
4. If not already done, reconcile the current Nodebus configuration.
5. Import the Nodebus configuration into SysDef V2.8. Save the configuration
6. Merge The Mesh configuration into the Nodebus configuration.
54
7. V8.2 Installation Procedures B0700RN – Rev C
! CAUTION
If you want to keep the Nodebus system on-line, it is very important that you merge
The Mesh configuration into the existing Nodebus configuration and not the other
way around.
Class D Installations
1. If not already done, reconcile the current Nodebus configuration.
2. Import the Nodebus configuration into SysDef V2.8. Save the configuration.
3. Set the Nodebus configuration to Day 0 by marking the installation status of all soft-
ware packages as “NOTYET”. (Refer to System Definition on-line help for proce-
dures.) Save the configuration.
4. If not already done, reconcile the current Mesh configuration.
5. Import The Mesh configuration into SysDef V2.8, and perform V8.2 configuration
changes.
6. Merge the Nodebus configuration into The Mesh configuration.
! CAUTION
If you want to keep The Mesh system on-line, it is very important that you merge
Nodebus configuration into the existing Mesh configuration and not the other way
around.
55
B0700RN – Rev C 7. V8.2 Installation Procedures
NOTE
Once the Mesh network has an established MTK that is sending time updates to the
Nodebus stations, you can upgrade other Mesh workstations while the Mesh is con-
nected to the Nodebus via an ATS. For example, V8.2 stations can be added to an
existing system that has V8.1 workstations.
56
7. V8.2 Installation Procedures B0700RN – Rev C
tionality before beginning the upgrade. This precaution ensures that if you must abort the
upgrade, you can restore CSA functionality.
To back up CSA, perform the procedures in “Backing Up CSA (CSA_Save)” on page 140 and
refer to user note “Relocating CSA” on page 100.
! CAUTION
Make sure that time is never set backward on the Nodebus. Motif applications like
I/A Series Batch and FoxView software running on Solaris stations do not handle
setting time backward correctly. Additionally, users running historical data collec-
tion applications like AIM*Historian or the I/A Series INFORMIX-based Historian
on either the Solaris or Windows platforms will experience issues. For additional
information, refer to the Customer Advisory on I/A Series and Daylight Savings
Time at the Global CSC webpage http://support.ips.invensys.com.
NOTE
1. Refer to Appendix B “EEPROM Revision Levels” for the latest EEPROM/
IMAGE and software revision levels for control stations and FBMs.
2. The media listed in this document supercedes any media specified in the
hardware and software specific instructions shipped with your workstation. This
applies to references such as “I/A Series CD-ROM”, “Release Level Diskette(s)”,
“Revision Level Diskette(s)”, and so forth.
57
B0700RN – Rev C 7. V8.2 Installation Procedures
To update the V8.0B Master Timekeeper, use the “Install Selected Packages/Load Release Level
diskettes” process described below. You will need the V8.0 Revision B Windows XP Day 0 CD-
ROM (K0200XG-B) and the Pre-V8.1 Compatibility Diskette (K0173XN).
1. Insert the V8.0 Revision B Windows XP Day 0 CD-ROM (K0200XG-B) into the
CD-ROM drive and start the I/A Series startup application through Windows
Explorer.
2. After the first prompt, select Next.
3. Select Install Selected Package(s) > Load Release Level Diskette(s), and click Next.
4. Click Clear All in the Selected Packages Installation dialog box, and then the appro-
priate package from the Package menu:
OS7AW1 Opsys for AW70
OS7GC1 Opsys for WP70
12. If this is a P92 workstation, proceed to the next section. If this is a P91 server, proceed
to “Day 0 Installation Procedure for P91 Servers” on page 63.
NOTE
If this is a new machine shipped from the Invensys factory, skip to Step 1e. If you
are migrating files and databases, refer to Appendix A “Files to Back Up/Restore”.
58
7. V8.2 Installation Procedures B0700RN – Rev C
1. Install hardware, restore the Windows XP operating system, and update drivers for
your workstation by performing the following steps:
a. Refer to “Platform-Specific Hardware Upgrade Kits and Required Media” on
page 43.
If you need to install memory upgrades, PCI cards, and so forth, refer to the
“Installing Hardware Upgrades” chapter of the hardware and software specific
instructions manual for your workstation.
b. Restore the Windows XP operating system on your workstation. Perform all pro-
cedures of the “Quick Restore, Windows XP Professional Operating System”
chapter of the hardware and software specific instructions document shipped with
your workstation.
c. The Windows operating system installs drivers for optional workstation compo-
nents at this point.
♦ If you are installing the quad-head video card driver, and you are given two
choices of drivers, choose V2.00.02 – Stretched and independent modes.
♦ If you are installing a RAID system and have an internal SCSI controller card,
follow the prompts to allow Windows XP to install the correct driver for your
hardware.
♦ If your workstation contains a KSI time synchronization card, the operating
system finds new hardware of type “Other PCI Bridge Device”.
- Insert the “Windows XP Driver For KSI TSAT-PCI GPS System”
CD-ROM (K0173XG, supplied with the time synchronization hardware)
when the initial Welcome screen appears and indicates “Other PCI Bridge
Device”.
- Select Install the Software Automatically (Recommended)
- The wizard asks you to select the hardware type you want to install for this
hardware. When prompted, select the FXA Timing Board.
- Click Next, and then click Finish.
- After I/A Series installation, you must install the KSI Control Utility. See
“Installing the KSI TPRO/TSAT-PCI Control Utility” on page 155.
! WARNING
Some hardware and software specific instructions manuals instruct you to proceed
to the “Installing I/A Series Software on a New Processor” section. Do not install
I/A Series software at this time.
d. Increase the workstation’s page file size using the instructions in the hardware and
software specific instructions manual shipped with your workstation. Use the fol-
lowing page file sizes, which have changed since the publication of the hardware
and software specific instructions:
♦ For 512 MB, use 1536 MB for the initial and maximum page sizes.
♦ For 1 GB, use 3000 MB for the initial and maximum page sizes.
♦ For 1.5 GB, use 4095 MB for the initial and maximum page sizes.
♦ For 2 GB, use 4095 MB for the initial and maximum page sizes.
59
B0700RN – Rev C 7. V8.2 Installation Procedures
♦
For 3 GB, use 4606 MB for the initial and maximum page sizes.
♦ For 4 GB, use 6142 MB for the initial and maximum page sizes.
e. Set the time and date:
♦ Open the Windows date and time applet by double-clicking the Date and
Time icon in the Control Panel.
♦ Click the Time Zone tab.
♦
Select the correct time zone from the drop-down list and select the checkbox
(if not already selected) to automatically adjust the clock for daylight savings
changes, if desired.
♦ Click the Date & Time tab.
♦ Adjust the Date and Time.
♦ Click Apply then OK.
f. With the exception of NIC drivers, install and update drivers as required. (NIC
drivers are updated in step 1g below.)
Refer to the “Installing and Updating Drivers” chapter of the Hardware and Soft-
ware Specific Instructions manual, or the “Dual-Head Video Card Driver Installa-
tion” and “Installing Tape Drive Drivers” chapters if you are installing a P92 Style
A or B Workstation (PW340).
g. Check the versions of the NIC drivers, and update the NIC drivers from
K0173XA-D if required. Refer to Appendix C “Installing/Updating NIC Drivers”
on page 151 of this document.
h. If you have a KSI time card installed and have installed a functioning driver dur-
ing the system Restore process, install the KSI time card control utility. See
“Installing the KSI TPRO/TSAT-PCI Control Utility” on page 155.
2. Install Windows XP Service Pack 2:
a. Insert the Windows XP Service Pack 2 CD-ROM (K0200YU), and the installa-
tion process should start automatically.
NOTE
If Autorun is disabled, navigate to the CD-ROM drive in Explorer and double-click
Autorun.exe.
60
7. V8.2 Installation Procedures B0700RN – Rev C
h. Upon booting, the security screen “Help protect your PC” opens. Select Not
right now and click Next. The workstation continues booting into the
Windows XP operating system.
i. The Security Center opens. Click Change the way Security Center alerts me
in the Resources pane in the left-hand portion of the Windows Security Center
window.
j. Deselect the boxes for Firewall, Automatic Updates, and Virus protection. Click
OK.
k. Close the Security Center.
3. Disable the firewall for I/A Series NICs:
a. Click Start > Settings > Network Connections.
b. Note the “Local Area Connection” numbers for each I/A Series NIC. The connec-
tion number associated with the NIC appears under the “Name” column in the
“LAN or High-Speed Internet” section of the window. For example, you may have
two Intel Pro/1000 GT copper NICs listed as “Local Area Connection” and
“Local Area Connection 2”. Note these associations.
c. Right-click the first NIC for I/A Series and select Properties in the dialog box.
d. Click the Advanced tab, and click Settings in the Windows Firewall section of
the NIC’s Properties dialog box. The “Windows Firewall” window opens.
e. Click the Advanced tab, and deselect the boxes for each I/A Series NIC based on
the NIC numbers noted in Step b above. This disables the firewall for both
I/A Series NICs, but leaves the Windows firewall enabled for the secondary net-
work for security.
f. Click OK, OK, and close the “Network Connections” window.
4. Install the recommended Service Pack 2 security patches from the media created in
Section 7.3.2:
a. From the CD or USB memory stick you created in Section 7.3.2, execute
K0173XY_A.bat. If the E:\ drive opens when the CD is inserted into the worksta-
tion, double-click K0173XY_A.bat to start the patch update process. Alternately,
you can open a Command Prompt window and start the batch file by executing
<drive>:\K0173XY_A.bat from the CD or USB memory stick containing the
patches.
b. A prompt appears informing you that you are about to install the security patches
previously contained on the K0173XY-A CD-ROM. The command prompt win-
dow provides a list of security patches as they are installed.
c. After all the patches are successfully installed, you will be prompted to shut down
and restart the workstation.
5. Upgrade to McAfee Virus Scan software V8.0i. Refer to Custom McAfee VirusScan
Enterprise 8.0i Installation (B0700CC).
61
B0700RN – Rev C 7. V8.2 Installation Procedures
NOTE
♦ McAfee 7.0 or 7.1 Enterprise Editions of Virus Scan are not supported for use
with I/A Series V8.2 software. The only supported version is Version 8.0i.
♦ Do not use Virus Scan Version 8.0i on any P92 workstations running previous
versions of I/A Series software. Virus Scan Version 8.0i software is only
supported on I/A Series V8.1 P91 Server and I/A Series V8.2 platforms.
♦ Installation files for McAfee 8.0i software are provided on the Dell Restore
CD-ROMs shipped with P92 Style F and later workstations. All earlier styles of
P92 I/A Series workstations must upgrade to McAfee 8.0i by purchasing the
upgrade from McAfee. Visit the following website for information:
https://secure.nai.com/us/forms/downloads/upgrades/login.asp.
a. For P92 workstation styles A through E, upgrade to McAfee 8.0i and update the
McAfee Virus Scan DAT files. Custom McAfee VirusScan Enterprise 8.0i Installa-
tion (B0700CC) gives instructions on how to obtain the virus scanning software
from McAfee, download the files, install the software, and update the DAT files.
b. For P92 Style F and later workstations, the Dell Restore CD-ROM contains the
installation files for McAfee Virus Scan V8.0i. You do not need to obtain and
download the files from McAfee. When the Restore CD is loaded on a P92 Style F
or later workstation, a zip file (VSE80iLEN.zip) is placed in C:\Drivers\McAfee.
Upgrade to Version 8.0i McAfee Virus Scan Software and update DAT files using
the provided zip file and the procedures in Custom McAfee VirusScan Enterprise
8.0i Installation (B0700CC).
6. Restart the workstation.
7. Disable Virus Scan software before proceeding with installation. Double-click the
Virus Scan icon on the task bar, click Disable, and then click Close.
8. Install I/A Series V8.2 software. Perform the steps of the “Installing I/A Series Soft-
ware” chapter of the hardware and software specific instructions shipped with your
workstation. Be sure you use only V8.2 media. (The same media is used on the Win-
dows XP and Windows Server 2003 operating systems.)
Notes on following the instructions in the hardware and software specific documents
are below:
a. The hardware and software instructions tell you to change the workstation’s
name and reboot the machine, which automatically re-enables the Virus Scan
software. After you reboot, you must disable Virus Scan software again.
b. During I/A Series software installation, you are prompted to select the two Net-
work Interface Cards you will be using for the I/A Series control network. After
selecting the two cards and clicking Next, an I/A Series Network Installation dia-
log box appears indicating that the system is reconfiguring network components.
When this dialog box appears, wait about 10 seconds before clicking OK. Other-
62
7. V8.2 Installation Procedures B0700RN – Rev C
wise, a blue screen appears and installation fails. To recover from this problem, re-
ghost the workstation and reinstall the Day 0 I/A Series software.
c. The hardware and software specific instructions tell you to reboot the workstation
after software installation. Because you must install the V8.2 trailer software, it is
not required that you reboot at this time. A reboot is required after installing the
V8.2 trailer software.
9. Disable the firewall for the I/A Series FoxInt NDIS Intermediate Miniport driver.
a. Click Start > Settings > Network Connections.
b. Note the “Local Area Connection” number for the FoxInt NDIS Intermediate
Miniport Driver. The connection number associated with the NIC appears under
the “Name” column in the “LAN or High-Speed Internet” section of the window.
For example, the FoxInt NDIS Intermediate Miniport Driver may be listed as
“Local Area Connection 4”. Note this association.
c. Right-click the FoxInt NDIS Intermediate Miniport Driver and select
Properties.
d. Click the Advanced tab, and click Settings. The “Windows Firewall” window
opens.
e. Click the Advanced tab, and deselect the box for the FoxInt NDIS Intermediate
Miniport Driver based on the NIC number noted in Step b above.
f. Click OK, OK, and close the “Network Connections” window.
10. Proceed to “Installing the Version 8.2 Trailer CD-ROMs (K0174AY and K0174BC)”
on page 66.
NOTE
If this is a new machine shipped from the Invensys factory, skip to Step 1d. If you
are migrating files and databases, refer to Appendix A “Files to Back Up/Restore”.
1. Install hardware, restore the Windows Server 2003 operating system, and update driv-
ers for your server. Perform the following:
a. If you need to install memory upgrades, PCI cards, and so forth, refer to the
“Installing Hardware Upgrades” chapter of the hardware and software specific
instruction document shipped with the server.
63
B0700RN – Rev C 7. V8.2 Installation Procedures
b. Restore the Windows Server 2003 operating system on your workstation and
install required drivers. Perform all procedures of the “Quick Restore, Windows
Server 2003 Operating System” chapter of the hardware and software specific
instructions document shipped with your server. Use the procedures in this sec-
tion of the hardware and software specific instruction manual to update drivers as
required by your server configuration.
! WARNING
The Hardware and Software Specific Instructions manual instructs you to proceed
to the “Installing I/A Series Software on a New P91 Server” section. Do not install
I/A Series software at this time.
64
7. V8.2 Installation Procedures B0700RN – Rev C
Notes on following the instructions in the hardware and software specific documents
are below:
a. The hardware and software instructions tell you to change the workstation’s
name and reboot the machine, which automatically re-enables the Virus Scan
software. After you reboot, you must disable Virus Scan software again.
b. During I/A Series software installation, you are prompted to select the two Net-
work Interface Cards you will be using for the I/A Series control network. After
selecting the two cards and clicking Next, an I/A Series Network Installation dia-
log box appears indicating that the system is reconfiguring network components.
When this dialog box appears, wait about 10 seconds before clicking OK. Other-
wise, a blue screen appears and installation fails. To recover from this problem, re-
ghost the workstation and reinstall the Day 0 I/A Series software.
c. The hardware and software specific instructions tell you to reboot the workstation
after software installation. Because you must install the V8.2 trailer software, it is
not required that you reboot at this time. A reboot is required after installing the
V8.2 trailer software.
5. Disable the firewall for the I/A Series FoxInt NDIS Intermediate Miniport driver.
a. Click Start > Settings > Network Connections.
b. Note the “Local Area Connection” number for the FoxInt NDIS Intermediate
Miniport Driver. The connection number associated with the NIC appears under
the “Name” column in the “LAN or High-Speed Internet” section of the window.
For example, the FoxInt NDIS Intermediate Miniport Driver may be listed as
“Local Area Connection 4”. Note this association.
c. Right-click the FoxInt NDIS Intermediate Miniport Driver and select
Properties.
d. Click the Advanced tab, and click Settings. The “Windows Firewall” window
opens.
e. Click the Advanced tab, and deselect the box for the FoxInt NDIS Intermediate
Miniport Driver based on the NIC number noted in Step b above.
f. Click OK, OK, and close the “Network Connections” window.
6. Proceed to “Installing the Version 8.2 Trailer CD-ROMs (K0174AY and K0174BC)”
below.
65
B0700RN – Rev C 7. V8.2 Installation Procedures
On an AW, you must install both CD-ROMs in the correct order. A workstation reboot is
required after the installation of CD-ROM #2.
For a WP, you only need to install the first trailer CD-ROM. “Copy failed” error messages appear
if the second trailer CD-ROM is mistakenly installed on a WP. These messages do not affect sys-
tem installation and can safely be ignored.
66
7. V8.2 Installation Procedures B0700RN – Rev C
NOTE
Although you can set the time of day on the PC more than once, you should do so
only rarely. The PC clock may drift over long periods of time.
Time changes made via SMDH can take up to 15 minutes before the workstations
and controllers are synchronized due to NTP time algorithms and Master Time-
keeper operations.
FoxView software must already be installed as indicated in the hardware and software
instructions provided with the workstation.
1. From the I/A Series initial display, access System Management displays from the
System button on the FoxView main window.
2. From the System Monitor display, select the Time button to access the Set Date and
Time screen. Set the current date and time by clicking the appropriate arrows on the
screen. Click RETURN - SET.
For an active externally sourced MTK, the Set Date and Time display is unavailable. The date and
time are automatically established and synchronized by an external GPS satellite.
Refer to Time Synchronization User’s Guide (B0700AQ) for a complete description of the time
synchronization subsystem.
NOTE
As of CP270 image version 3.1 and ATS image version 1.0, the correct addresses are
automatically downloaded from the STA<letterbug>.bin file when the station is
rebooted.
CP270s with Image Versions 3.1 and Later and ATS Modules with Image Versions 1.0 and
Later
For FCP270s and ZCP270s installed with image version 3.1 or later, perform a REBOOT STA-
TION > BOTH from SMDH to ensure that the address in the station matches the address in the
station’s STA<letterbug>.bin file.
For ATS modules installed with image version 1.0 or later, perform a REBOOT STATION >
PRIMARY from SMDH to ensure that the address in the station matches the address in the sta-
tion’s STA<letterbug>.bin file.
67
B0700RN – Rev C 7. V8.2 Installation Procedures
Refer to the station’s user documentation for instructions (see “Reference Documents” on
page xviii).
CP270s with Image Versions Prior to 3.1 and ATSs with Image Versions Prior to 1.0
For FCP270s and ZCP270s installed with image versions prior to 3.1 and ATS modules installed
with image versions prior to 1.0, you must flush the letterbugs to ensure that the address in the
station matches the address in the station’s STA<letterbug>.bin file. Perform the following:
1. If this is a fault-tolerant station, remove one module.
2. Remove the Mesh connections from the station module.
3. Set the station letterbug to a non-configured value, such as NOSUCH, using the
I/A Series Letterbug Configurator.
4. Allow the module to reboot to accept the new letterbug.
5. Read the module status with the I/A Series Letterbug Configurator. The letterbug
should be the non-configured value, and the IP address should be 255.255.255.255.
6. Set the letterbug back to the configured value.
7. Reconnect the Mesh cables to the module.
8. The module reboots a second time as it reads the STA<letterbug>.bin information.
Successful flushing is indicated by a system message indicating “Config data
verified”.
9. If this is a fault-tolerant station, insert or plug in the other module.
! CAUTION
Use extreme caution when rebooting or updating the image of control stations.
NOTE
1. On-line Image Update is not supported during V8.2 Day 0 software installation.
See page 1 for additional information.
2. If an image update fails, make sure that the firewall is disabled. See
“Disabling Firewalls for Mesh Network Connections” on page 77.
68
7. V8.2 Installation Procedures B0700RN – Rev C
3. Perform an IMAGE UPDATE for FCP270s and ZCP270s, and verify that these con-
trol stations are at the correct revision level for V8.2. Refer to Appendix B “EEPROM
Revision Levels” for the latest EEPROM revision levels for V8.2.
The “System Management” chapters in Field Control Processor 270 (FCP270) User’s Guide
(B0700AR) and Z-Module Control Processor 270 (ZCP270) User’s Guide (B0700AN) provide
detailed procedures for updating the images of single and fault-tolerant CP270 modules and for
verifying that the station is at the correct image level using the Equipment Change and Equip-
ment Information displays.
69
B0700RN – Rev C 7. V8.2 Installation Procedures
! CAUTION
When performing a selective restore using the Restore Wizard, do not check the box
next to System State. Checking this box overwrites the Windows XP Registry file.
This step is applicable to Class C and D installations. The following procedure must be per-
formed on all Nodebus workstations (AP, AW, and WP) to add I/A Series addressing information
to the host files on Nodebus components. To perform the Post-Commit for Pre-8.0, install the
Pre-V8.1 Compatibility Diskette (K0173XN) on each Nodebus workstation.
The following sections detail the steps for installing the disk on the two platforms. For Windows-
based workstations, use the process described below. For Solaris-based workstations, use the pro-
cess described on page 71.
70
7. V8.2 Installation Procedures B0700RN – Rev C
d:
ncenv
sh
tar xvf A: ./usr/fox/bin/mkhosts.sh
cd /usr/fox/bin
sh mkhosts.sh
3. A reboot of the workstation is not required.
NOTE
If you have not rebooted the ATS module, reboot before continuing to ensure that
the ATS is configured with the correct addresses from its STA<letterbug>.bin file.
Refer to “Resetting Station Address Assignments” on page 67.
6. After you verify the checksum, perform an IMAGE UPDATE as directed in Address
Translation Station User’s Guide (B0700BP).
71
B0700RN – Rev C 7. V8.2 Installation Procedures
7. Using System Management Displays, confirm that the ATS has the latest image ver-
sion installed. Refer to Appendix B “EEPROM Revision Levels” for the latest image
levels.
72
8. V8.2 Operational
Recommendations
This chapter provides recommendations that you may want to consider relating to V8.2
I/A Series software.
73
B0700RN – Rev C 8. V8.2 Operational Recommendations
After the incorrect software configuration is installed in the ATS, the station information for the
ATS in Extender mode incorrectly indicates that the updated node contains both an ATS and an
LI, and the node with the replacement ATS cannot communicate to other nodes on the Nodebus.
To prevent this occurrence, when creating the Day 1 Commit diskette in SysDef, specify
“REINST” for the OS7AW1 (Opsys for AW70P) and OS1A70 (Opsys for ATS) software pack-
ages on the host of the ATS in Extender mode.
74
8. V8.2 Operational Recommendations B0700RN – Rev C
8.3 Workstations
8.3.1 IP Netmask Settings of Windows Workstations on the
Nodebus
Nodebus workstations have their IP netmask set to 255.255.254.0 for Windows NT workstations
and 255.255.224.0 for Windows XP workstations. The IP netmasks of these workstations need to
be changed to 255.255.0.0 for IP forwarding through the ATS to work.
Without changing the netmask, a Windows workstation will behave as if the Mesh workstations
are on a different subnet, and will not be able to reach them via IP. This affects IP communica-
tion, e.g., pings, ftp, rlogin, rsh, and telnet. Solaris workstations have the correct netmask.
75
B0700RN – Rev C 8. V8.2 Operational Recommendations
76
8. V8.2 Operational Recommendations B0700RN – Rev C
current driver and install the correct one (which is typically available on the CD-ROM that was
shipped with the printer).
! CAUTION
If you do not install the correct printer driver, the CPU load may go to 100%,
which reduces communication data to and from the Windows XP workstation.
Perform the following steps after performing I/A Series software installation:
1. Invoke the “Printers” information window.
2. Make a note of the SysDef LPxx name currently assigned to the printer (for example,
LP01).
3. Delete the current printer (for example, HP 1200).
4. Insert the driver CD-ROM shipped with the printer.
5. Make the selections to add the new printer to the parallel port (LPT1).
6. When the installation is complete, invoke the “Printers” information window again.
7. Select the printer that you just installed and rename it to match the SysDef name that
you noted above.
8.3.6 Screensavers
Do not run screensavers on your I/A Series stations.
77
B0700RN – Rev C 8. V8.2 Operational Recommendations
NOTE
The appendices titled “Commonly Used Commands” in the System Administration
Guides for the Windows Server 2003 and the Windows XP operating systems
(B0700BX and B0400HE respectively) include tables that list the MKS Toolkit
commands, but do not list the mkszip command. These tables will be corrected in
future revisions of the documents.
Synopsis
mkszip [-cDdfVv] [-b hash_bits] [-l comp_level] [file ...]
Description
mkszip compresses each specified input file. If you do not specify any input files, mkszip reads
data from the standard input and writes the compressed result to the standard output.
Output files have the same names as the input files but with a .gz suffix. For example, abc is com-
pressed into abc.gz. The .gz suffix is appended regardless of existing suffixes; for example, abc.txt
would be compressed into abc.txt.gz. If the .gz file already exists and you did not specify the -f
option, mkszip prints an error and asks you whether or not it should overwrite the existing file.
Options
-b hash_bits
sets the size of the hash table to hash_bits. The value hash_bits may be an integer from
13 to 15. The default is 15.
-l comp_level
78
8. V8.2 Operational Recommendations B0700RN – Rev C
sets the level of compression to comp_level. Higher values lead to greater compression
but result in more time taken during the compression process. The value comp_level may
be an integer from 0 to 9. The default is 9.
-c
writes the output to the standard output. When you use this option, you can specify only
one file on the command line.
-D
allows an extra degree of compression for files such as sorted dictionaries where subse-
quent lines normally have many characters in common with the preceding line. This
option is for text files only and should not be used with binary files. When decompressing
a file compressed with this option, you must specify this option along with -d.
-d
decompresses argument files instead of compressing them. This works by overlaying the
mkszip program with the uncompress program. For this to work, uncompress must be
available somewhere in your search path (given by the PATH environment variable).
Decompressing files this way is slower than calling uncompress directly.
-f
forces compression even if the resulting file is larger or the output file already exists. When
you do not specify this option, files that are larger after compression are not compressed.
mkszip does not print an error message if this happens.
-V
prints the version number of mkszip.
-v
prints statistics giving the amount of compression achieved. Statistics give the name of
each file compressed and the compression ratio, expressed as a percentage. If the file
resulting from compression is larger than the original, the compression ratio is negative.
Environment Variables
PATH
contains a list of directories for mkszip to search when looking for the uncompress utility.
DIAGNOSTICS
Possible exit status values are:
♦ 0 = Successful completion.
♦ 1 = Failure because of one of the following errors:
♦ missing number of bits after -b option
♦ invalid number of bits specified
♦ failed to execute uncompress
♦ unknown option
♦ dictionary option -- same count of string exceeded
♦ output path or file name too long
♦ cannot stat file
79
B0700RN – Rev C 8. V8.2 Operational Recommendations
♦
argument file not a regular file: unchanged
♦ argument file has other links: unchanged
♦ no space for compression tables
♦ 2 = One or more files were not compressed because the compressed version was larger
than the original.
80
8. V8.2 Operational Recommendations B0700RN – Rev C
81
B0700RN – Rev C 8. V8.2 Operational Recommendations
♦ If DST Mode is AUTO, SMDH presents a pop-up box that allows you to change the
selection to MANUAL.
♦ If DST Mode is MANUAL, SMDH presents a pop-up box that displays current
Nodebus Time Mode and current Mesh Time Mode. The pop-up box allows you to
change DST Mode to AUTO or change Nodebus Time Mode to STANDARD or
DAYLIGHT.
Refer to System Management Displays (B0193JC) for more information on these displays.
After the operator makes a selection, the message Do not reboot any workstation for 1
minute appears on the SMDH message line to confirm that the selection has been processed. The
operator is warned not to reboot workstations intentionally for one minute to allow all worksta-
tions to record the SMDH time selection, thus making the time selection persistent should a
workstation later fail and a new Master Timekeeper take over.
The worst-case scenario would be if the Primary Master Timekeeper workstation fails immedi-
ately after a DST selection is made and other workstations do not get a chance to record the new
DST selection. This could result in Nodebus stations going to the selected SMDH DST state and
immediately reverting back to the previous DST state when a new Master Timekeeper takes over.
In this case, the operator would need to make his desired DST selection again.
! WARNING
Operators should only make DST changes via SMDH if all workstations that are up
and running are able to communicate on the network. Isolated workstations can
cause problems due to multiple Master Timekeepers.
The Master Timekeeper will generate system messages indicating if The Mesh and Nodebus net-
works are operating in the same time mode (STANDARD vs. DAYLIGHT). Examples:
1. An operator wants initial time setting different from the DST default values on an ini-
tial V8.2 installation. The default values are MANUAL and STANDARD, and there
are two possible changes: 1) AUTO or 2) MANUAL, DAYLIGHT. In order to make
one of these changes, the operator would:
a. Disconnect the ATS from Nodebus stations.
b. Get The Mesh system up and running.
c. Via SMDH, change DST Mode to AUTO, or leave DST Mode in MANUAL
and change Nodebus Time Mode to DAYLIGHT.
d. Connect the ATS to the Nodebus stations.
2. An operator wants to change Nodebus Time Mode from Daylight Savings Time to
Standard Time on an up-and-running system because The Mesh has just automati-
cally changed from Daylight Savings Time to Standard Time in the fall. To accom-
plish this, the operator would:
a. Via SMDH, select the DST button.
b. Verify that the Current Nodebus Time Mode is DAYLIGHT and Current Mesh
Time Mode is STANDARD.
c. The time on the Nodebus stations should be 1 hour or more ahead of The Mesh
stations.
d. Via SMDH, set the Nodebus Time Mode to STANDARD.
82
8. V8.2 Operational Recommendations B0700RN – Rev C
e. Time on the Nodebus stations and The Mesh stations should now be the same.
3. An operator wants to change Nodebus Time Mode from Standard Time to Daylight
Savings Time on an up-and-running system because The Mesh has just automatically
changed from Standard Time to Daylight Savings Time in the spring. To accomplish
this, the operator would:
a. Via SMDH, select the DST button.
b. Verify that the Current Nodebus Time Mode is STANDARD and Current Mesh
Time Mode is DAYLIGHT.
c. Time on the Nodebus stations should be 1 hour or more behind The Mesh
stations.
d. Via SMDH, set the Nodebus Time Mode to DAYLIGHT.
e. Time on the Nodebus stations and The Mesh stations should now be the same.
4. An operator wants to change DST Mode to AUTO on an up-and-running system so
Mesh and Nodebus station times are always the same. To do this, the operator would:
a. Via SMDH, select DST button.
b. Via SMDH, select AUTO.
c. Via SMDH, select the DST button and verify The Mesh and Nodebus Time
Modes are the same.
d. Time on the Nodebus stations and The Mesh stations should be the same.
NOTE
It is no longer required that you use IATIME for historical trend support across the
ATS from Nodebus to Mesh or vice versa.
8.8 Displays
8.8.1 Detail Display Differences on Nodebus and Mesh
Workstations
Operation of Detail displays is different for workstations on the Nodebus side versus workstations
on The Mesh side of two networks connected by an ATS. First, the default Detail displays for the
new V8.x control blocks (for example, AI, AO, DI, DO) are not present on workstations on the
Nodebus side; the new control blocks are only installed on V8.x workstations when I/A Series
V8.x software is installed.
83
B0700RN – Rev C 8. V8.2 Operational Recommendations
Additionally, the same Detail display may look different on workstations on The Mesh side and
workstations on the Nodebus side. The discrepancy is apparent if you are running Display Man-
ager, if you have not installed the enhanced Detail display, or if the display was enhanced only for
I/A Series V8.x.
Also refer to “Display Interoperability” on page 23 for additional information on display interop-
erability and conversion requirements.
8.9.3 Alarm Counts and Page Counts on the Title and Status Bars
Alarm counts (for example, Alarm x of y) or page counts (for example, Page x of y), or both, can
be displayed in either the title bar or status bar.
When the alarm count is displayed, the ‘x’ value refers to the first alarm at the top of the current
display being viewed, and the ‘y’ value refers to the total number of alarms on the display. The ‘x’
and ‘y’ values are always accurate because the total alarm count is incremented for each new alarm
available.
This works somewhat differently for page counts. When the page count is displayed, the ‘x’ value
refers to the page on which the first alarm viewed is located, and the ‘y’ value refers to the total
number of pages on the display.
The alarm count feature is designed to work with scrolling, and the page count feature is designed
to work with paging commands.
Using the scroll bar to scroll to the end of a display never shows empty cells. Unless the last page
of alarms is filled, the page count will appear inaccurate on the title and status bars, but will actu-
ally be correct. For example, if you can view 10 alarms per page on your CAD and you have 97
alarms scrolling to the end of the display, the following indicators are produced for alarm counts
and page counts respectively:
Alarm 88 of 97
Page 9 of 10
84
8. V8.2 Operational Recommendations B0700RN – Rev C
Scrolling to the very end of the display causes alarm 97 to be the last alarm on the screen. Since 10
alarms are viewed on the display at one time, the first alarm on the screen is alarm 88. However,
alarm 88 is technically on page 9 of the display, so Page 9 of 10 appears as the page count.
If you are looking at page counts as reference points when navigating through a display, use the
paging commands. These commands are designed to work with the page count feature.
With paging commands, you can “go to the last page”. This will display your alarm and page
counts as:
Alarm 91 of 97
Page 10 of 10
where alarms 91 though 97 are displayed in the top seven cells, and the remaining three cells will
be empty. Scrolling to the end of the same display will never show empty cells.
ALMLNS and ALMTIM are configurable only through ADMC. This has been the case since
ADMC was available. All other options that are configurable through \usr\fox\wp\bin\init.user
remain unchanged.
One major advantage to configuring these options with ADMC is that a reboot is usually not
required. The exceptions are for MAX_ACTIONS and MAX_CAD, because configuring these
options result in a change in size to the shared memory segment.
ADMC also provides a menu pick to distribute the configuration files to the workstations. You
can also select the type of action required on each of the workstations. Actions include rebooting
the workstation or restarting selected alarm management components (for example, Alarm Alert,
Alarm Manager).
85
B0700RN – Rev C 8. V8.2 Operational Recommendations
86
8. V8.2 Operational Recommendations B0700RN – Rev C
If you notice that alarms are updating on one workstation but not on another, or alarms are not
being synchronized between workstations, work around this issue by manually starting
“dm_recon”. The dm_recon program forces the Device Monitor to reconcile all its configured
alarm destinations with the current availability status. Modify the “go_ADM” script with the fol-
lowing lines:
# Start Device Monitor
#
nohup /usr/fox/cs/cs_devmon >/dev/null </dev/null 2>&1 &
sleep 10
/usr/fox/cs/dm_recon
sleep 5
/usr/fox/cs/dm_recon
If go_ADM does not exist, you can add these commands to any script that runs during boot-up.
8.9.8 FoxAPI
8.9.8.1 Starting the Foxhosts Program if Necessary
Foxhosts.exe (Windows operating system) has been added to FoxAPI. This program provides the
server identification of this Windows server to any client that requests it. This program can be run
only if there is no AIM*AT™ apihosts program running on this host.
Follow the directions below only when the AIM*Historian is not installed on the workstation.
AIM*AT has its own version of the foxhosts program, and if both programs are activated, you
could be denied access to AIM*Historian. When both AIM*Historian and FoxAPI software are
running on the same workstation, AIM*AT provides all the functionality of FoxAPI, but not vice-
versa.
1. Before starting the foxhosts program on the workstation running a FoxAPI server,
modify the D:\opt\fox\ais\bin\an_init.tcp on a Windows server. Edit the HOST line in
the [AISnet] section of the appropriate file with the letterbug of this server:
[AISnet]
HOST=<Local server letterbug>
2. Start the foxhosts program by editing D:\opt\fox\ais\bin\aisstart.ksh file as follows:
♦ Remove the # from the five lines that follow #Stop foxhosts
♦ Remove the # from the one line that follows #Start foxhosts
3. Restart FoxAPI by running the apistart script in D:\opt\fox\ais\bin.
8.10.1 Assumptions
It is assumed that timekeeping (system time domain) located on The Mesh side of the I/A Series
node is in UTC, and the timekeeping on the Nodebus is in IATIME.
87
B0700RN – Rev C 8. V8.2 Operational Recommendations
TZ and DST TZ and DST are collector attributes. They determine the amount of
adjustments made to the timestamps by the collectors and by the data
retrieval software when necessary. These attributes are configured the same
on Nodebus and Mesh historians.
♦ Configure TZ to the time zone where the historian is actually
located. For example, in the Eastern U.S., configure TZ=
GMT_MINUS_5; in most of Western Europe, configure TZ=
GMT_PLUS_1.
(Note that on Mesh stations, the TZ attribute should match the
system time setting. On Nodebus stations, however, the system
time zone is set to GMT and the TZ attribute will not typically
match that setting).
♦ Configure DST to the actual status of the Daylight Savings Time;
in the summer months, configure DST=yes; in the winter months,
set DST=no.
It is recommended that you configure the TZ and DST attributes the
same for all collector stations of each instance, including the shadow sta-
tions REALTIME_SERVER and MESSAGE_SERVER.
88
8. V8.2 Operational Recommendations B0700RN – Rev C
the Historian and also when values are being read from the Historian for a FoxView
trend, for example.
♦ It is required that you configure the TZ and DST offsets in the collector because the
TZ and DST offset values are both set to zero on the standard I/A Series stations.
♦ No time conversion is necessary if the IATIME parameter matches the timekeeping
type of the local station.
Refer to AIM*Historian User’s Guide (B0193YL) for additional information on configuring the
TZ and DST attributes.
1.
Refer to “Starting and Stopping AIM* Trend Servers” on page 90.
89
B0700RN – Rev C 8. V8.2 Operational Recommendations
Another AIM*AT utility, “mig_data”, allows you to migrate recent sample data from a legacy his-
torian to AIM*AT software.
Refer to the AIM*AT Installation Guide (B0193YM) for additional information.
90
8. V8.2 Operational Recommendations B0700RN – Rev C
glof -p ben007sf
If the process variable is registered somewhere, glof shows its PSAP address. Otherwise glof times
out after about 5 seconds.
To find the PSAP address of a particular station for comparison, run:
glof <letterbug>
8.12 ICCAPI
8.12.1 Error Message When Deleting a Block or Compound in
ICCAPI
Occasionally, when deleting a block using the ICCAPI, the following error message appears:
rm: cannot unlink entry “/opt/fox/ciocfg/<COMPOUND>/<BLOCK>.*”: The system
cannot find the file specified.
<COMPOUND> and <BLOCK> are the names of the block being deleted and its associated compound.
This message may also appear when a compound is deleted.
This message appears because the program is trying to delete a file that does not exist. This condi-
tion does not in any way affect the block delete operation, and this error message may be ignored.
91
B0700RN – Rev C 8. V8.2 Operational Recommendations
92
8. V8.2 Operational Recommendations B0700RN – Rev C
The chapter titled “Block/Process Alarming” in CP270 Integrated Control Software Concepts
(B0700AG) describes the details of alarm reprioritization, specifically, the preservation of alarm
acknowledgement status following re-alarming.
93
B0700RN – Rev C 8. V8.2 Operational Recommendations
8.14 CP270
8.14.1 Repeatedly Removing and Installing CP270 Fiber Cables
If fiber cables are repeatedly removed and replaced in a running fault-tolerant pair of controllers
(either FCP or ZCP), a single-sided reboot of the Shadow module may occur. Typically this does
not occur until the third cycle of removing and installing the cables. Within 15 seconds the mod-
ules will remarry and continue fault-tolerant operation. All process control is unaffected.
94
8. V8.2 Operational Recommendations B0700RN – Rev C
95
B0700RN – Rev C 8. V8.2 Operational Recommendations
96
8. V8.2 Operational Recommendations B0700RN – Rev C
97
B0700RN – Rev C 8. V8.2 Operational Recommendations
98
9. V8.2 User Notes
This chapter contains user notes for the V8.2 I/A Series software release. For additional
recommendations for installing and using V8.2 software, refer to Chapter 8 “V8.2 Operational
Recommendations”.
9.1 Workstations
9.1.1 Bringing an Active Window Forward
On the Windows XP operating system, sometimes a window does not come to the front when it
becomes active; however, its icon in the taskbar flashes. Clicking on the flashing icon brings the
active window to the front.
99
B0700RN – Rev C 9. V8.2 User Notes
100
9. V8.2 User Notes B0700RN – Rev C
! CAUTION
Do not reinstall “Canceled/Failed Packages” if there are no canceled or failed
packages.
Reinstalling canceled or failed packages on an I/A Series workstation hangs up the workstation if
there are no packages that were canceled or that failed to install correctly. A warning box with the
following message appears:
The current station, <letterbug> is not found in the configuration. Please
load a different configuration.
When you click OK, another warning box appears. Rebooting the workstation causes the following
blue screen message to appear:
STOP: C0000021a {fatal system errors} The windows logon process system
process terminated unexpectedly with a status of 0xc00000034 (0x00000000
0x00000000) The system has been shutdown
When this issue occurs, you must re-ghost the machine and reinstall the Day 0 I/A Series
software.
101
B0700RN – Rev C 9. V8.2 User Notes
102
9. V8.2 User Notes B0700RN – Rev C
This occurs because the /usr/fox/sp/files/CMX<letterbug>.bin is not removed from the former
host. Remove this file from the former host workstation.
9.6 Displays
9.6.1 Selecting DISABLE ALL REPORTS Twice from SMDH
In the SMDH Equipment Action display, if you select DISABLE ALL REPORTS twice in a row, the
PIO Network Display for the CP no longer displays any attached devices until you select ENABLE
ALL REPORTS to properly display attached devices.
103
B0700RN – Rev C 9. V8.2 User Notes
9.7 Applications
9.7.1 Compound/Block Listbox Population
Large system users may experience a delay during Compound/Block listbox population within the
AIM*Historian Configurator, FoxPanels Configurator, and FoxDraw software.
104
9. V8.2 User Notes B0700RN – Rev C
♦ am_def.cfg
♦ foxboro.am.
These files can be used directly as the default or can be used to create custom configuration files.
By default, these files configure the time/date using US format (mm-dd HH:MM:SS).
A problem arises when custom configuration files exist that were created prior to the changes to
these data files. Previous versions of these data files were configured to display the time/date as:
mm/dd/yy HH:MM:SS (for example, 11/23/04 11:42:13)
This configuration is no longer ignored with V8.0 Revision B and later software. If these custom
configuration files are used as-is, the time/date in the alarm messages will actually be displayed as:
mm/dd/yy HH:MM (for example, 11/23/04 11:42)
The last colon and the seconds field are truncated because the field width on the displays is only
14 characters wide.
The solution is to convert your existing configuration files using ADMC as follows:
1. In FoxView, change your working environment to either the Process_Eng or
Softw_Eng environment.
2. Select Config > DispAlarmCfg to start ADMC.
3. Select File > Open and select your custom .am file to edit your configuration.
NOTE
There is no reason to edit foxboro.am. An updated configuration file was installed
via the Day 0 CD-ROM.
From the Select box, select Alarm Formats and edit EACH Alarm Format Scheme as follows:
a. If the Time/Date Format is set to 11/23/04 11:42:13 Local Time & Date:
♦ Change it to 11-23 11:42:13 24 hr. mm-dd HH:MM:SS for US format, or
♦ Change it to 23-11 11:42:13 24 hr. dd-mm HH:MM:SS for European
format.
Repeat for EACH Alarm Format Scheme.
4. Select File > Save to save your changes.
5. Select File > Validate Records… to validate your changes.
6. Select File > Create Install Files… to create the new configuration files.
7. Select File > Distribute Install Files… to distribute the new configuration files to
the workstations.
8. Select File > Exit to exit ADMC.
9. On each workstation close all AMs. If needed use pref from a Command window to
close the AMs, as follows:
pref -<amname> amcmd “quitam on; exit”
10. Restart the AMs. The new configuration files will be used by the AMs on restart.
105
B0700RN – Rev C 9. V8.2 User Notes
9.10 ICCAPI
9.10.1 Checkpoint Failure After LoadAll
If you use the ICCAPI load_all utility, the ICCAPI does not warn you when a checkpoint fails
after performing a load_all.
After performing a load_all, use the STATION block to verify that the checkpoint took place.
Also, verify the time and date that the last checkpoint was initiated. If the checkpoint did not take
place, perform a checkpoint using System Management displays.
106
9. V8.2 User Notes B0700RN – Rev C
107
B0700RN – Rev C 9. V8.2 User Notes
108
9. V8.2 User Notes B0700RN – Rev C
the driver’s installation CD-ROM. After inserting the CD-ROM, run the setup.exe
program. A dialog box appears offering three choices: Modify, Repair, and Remove.
Select Remove to uninstall the driver.
♦ After CP270s have been updated to a newer control image, using the COLD START
option of ON-LINE IMAGE UPDATE to update the image for a CP270 with FDSI
modules (FBM230, 231, 232, and 233) may result in a temporary loss of I/O
connections.
109
B0700RN – Rev C 9. V8.2 User Notes
110
9. V8.2 User Notes B0700RN – Rev C
111
B0700RN – Rev C 9. V8.2 User Notes
If you want to expand the engineering range, also adjust the LOLIM and HOLIM values accord-
ingly by setting them to their desired values. Once this is done, the new limit values will be used
correctly to constrain the output value.
112
9. V8.2 User Notes B0700RN – Rev C
113
B0700RN – Rev C 9. V8.2 User Notes
114
10. Problems Resolved in V8.2
This chapter describes the problems resolved in I/A Series V8.2 software.
Resolution This problem has been corrected. Values from an FBM211 used with an
ISTA board do not freeze when the FBM is using Version 1.19 or later
software.
Resolution Phasing has been implemented with a scheme equivalent to the phasing
used in control blocks in the I/A Series control processors.The phasing fea-
ture is included in the new Modbus Device Configurator and the FBM224
image delivered with V8.2.
Resolution This problem has been corrected with V8.2 I/A Series software. The SYS-
LVL file shows the correct release information.
115
B0700RN – Rev C 10. Problems Resolved in V8.2
Problem Day 1 installation procedures were crashing workstations if I/A Series soft-
ware was not disabled in the manner described in the release notes.
Resolution This has been corrected. Refer to “Proper Method to Disable I/A Series
Software During a Day 1” on page 74.
Problem The display manager “redirect” command was not functioning after
I/A Series software installation. The wp51_glbls.all file contains variables
that are initialized and created when a workstation is booted. The redirect
command would no longer function because a reserved variable, GCRED,
was not created and initialized in the wp51_glbls.all file for I/A Series V8.x
software.
Resolution Version 8.2 I/A Series software restores the functionality for the Display
Manager “redirect” command. This command is needed for graphics redi-
rection on projects with multiscreen displays.
Problem When an Alarm History display was initially connecting to a server, the
CPU usage would get very high and the message “Too many historian
alarms in database <histname> on <wsname>. Please archive your
database” would appear. Other running programs may have been affected
during this time. This problem occurred because an AIM* timeout occurs
when getting the count of alarm messages in a large database.
Resolution This problem is corrected in Version 8.2 I/A Series software. An enhanced
filtering mechanism implemented in the software avoids the timeout by
providing faster alarm message counting and retrieval.
116
10. Problems Resolved in V8.2 B0700RN – Rev C
Resolution This problem is corrected in Version 8.2 I/A Series software. GCIO, annun-
ciator keyboards, and annunciator/numeric keyboards report their correct
status to SMDH.
Problem The ACCUM Block Detail display had an extra set of buttons at the bot-
tom of the display, and the PID Block Detail display had the text field for
.OUTADB configured to .DEVADB.
Resolution The ACCUM and PID Block Detail displays supplied with Version 8.2
I/A Series software have been corrected.
Problem Devices were being set failed as a result of 3 consecutive timeouts. Role-
switching was seen in redundant modules if device failure occurred on the
Master module, along with a Role switch Master/Tracker due to driver
request message in the System Monitor log.
If a device failure occurred on Tracker module, the System Monitor log
would show Warning Error Condition Exists.
Resolution This problem has been corrected in FDSI Modbus Master 1.03 and greater.
The sequence to retry when a device response to a query is not received was
modified to include toggling of the socket connection before third and final
retry.
117
B0700RN – Rev C 10. Problems Resolved in V8.2
Problem After a power failure, fault-tolerant FCM100Ets would freeze and would
not reboot from System Management displays. Removing power from the
baseplate allowed the modules to reboot.
Resolution The FCM image released with I/A Series V8.2 software corrects this prob-
lem with the addition of a mechanism to handle situations where two
FCM100Ets of a fault-tolerant pair are both in the tracker state.
Problem During power cycling of an Ethernet switch in the system, System Manage-
ment did not display the correct status for the switch. Acknowledged state
and color were incorrect in System Management. Switch status was also
inconsistent between the workstations in the system.
Following a communication failure to a ZCP and a subsequent acknowl-
edgement of the failure, the fault automatically went back into the unac-
knowledged state 15 to 20 seconds later.
Resolution The System Management display subsystem was modified to correct display
status and color issues and to provide consistency between workstations that
were reporting the status. The System Management monitoring subsystem
was modified to correct incorrect handling of uplink ports and incorrect
setting of the unacknowledged status of communication faults.
Problem The ROUT Block Detail display did not contain the REVOPT parameter.
Resolution The ROUT Block Detail display supplied with Version 8.2 I/A Series soft-
ware was corrected to include the REVOPT parameter.
118
10. Problems Resolved in V8.2 B0700RN – Rev C
Problem After moving the last block in the continuous zone to somewhere in the
middle of a compound using the IACC Execution Editor, the iccdrvr.tsk
input file creates the correct MOVE action, which will move the desired
block to the correct location. However, after closing and reopening FoxSe-
lect and refreshing the CP, the block is still at its original location. Addition-
ally, after moving a group of blocks from the end of the continuous zone to
somewhere in the middle of the compound, iccdrvr.tsk input file creates the
correct MOVE action. FoxSelect then shows the moved blocks are still at
the end of the continuous zone, but are now in reverse order.
Resolution This problem is corrected in Version 8.2 I/A Series software. Blocks can be
moved correctly within a compound using ICCAPI.
Problem With ZCP270 controller versions prior to V2.5, the FIELD BUS A and
FIELD BUS B fields on the ZCP270 FBM0 Equipment Information dis-
play would always display Ok regardless of the state of the PIO Ethernet
connections.
Resolution This problem has been corrected. With V8.2 software and ZCP270 con-
troller version 2.5 and higher, the FIELD BUS A and FIELD BUS B fields
on the ZCP270 FBM0 Equipment Information display will contain the sta-
tus of the ZCP270 PIO Ethernet connections. The states will be Ok if the
PIO Ethernet connection is functional and Failed if the PIO Ethernet con-
nection is not functional.
119
B0700RN – Rev C 10. Problems Resolved in V8.2
Resolution This problem has been corrected in I/A Series V8.2 software. This problem
resulted from the presence of dump files on the workstations. After remov-
ing the dump files, the message did not reappear.
Problem Any FCM with a letterbug that had a “D” character in the third position of
its letterbug would not communicate with the ZCP.
Resolution This problem has been corrected with Version 1.35 and later FCM images,
including the image released with V8.2. Using a “D” in the FCM100Et’s
letterbug no longer restricts communication to the ZCP.
Resolution This problem has been fixed in V8.2 I/A Series software. The controller
code was modified to reboot the offline module as soon as at least one link
is up. This avoids the case where the controller software does not have either
link for a period of time following a switch failure, and the shadow module
is left in the offline state.
120
10. Problems Resolved in V8.2 B0700RN – Rev C
Problem There is an issue with the backup alarm subsystem that can cause the system
to miss alarms.
Resolution This problem has been corrected in V8.2 I/A Series software. The operation
of the backup alarm subsystem does not cause the system to miss alarms.
Problem The FCM100Et does not recognize the time synchronization pulse when
using a single Timestrobe sync connection to an FCM100Et (A only). The
Equipment Information Status always shows:
SYNC STATE: Network Time
STROBE STATE A: Not Applicable
STROBE STATE B: Not Applicable
Resolution This problem has been corrected in FCM100Et image versions 1.35 and
later.
Problem If an FCP270 or ZCP270 was hosted by a workstation that did not have
System Monitor installed, alarm messages were not sent by the controller.
Resolution This problem has been corrected in the FCP270 and ZCP270 images
released with I/A Series V8.2 software. The controller alarm messaging soft-
ware is no longer dependent on the presence of a System Monitor.
121
B0700RN – Rev C 10. Problems Resolved in V8.2
Problem When a control bus cable is removed from a fault-tolerant CP270, one of
the modules may go red/green.
Resolution This problem has been corrected with V8.2 software. See also “Repeatedly
Removing and Installing CP270 Fiber Cables” on page 94.
Resolution This problem has been corrected with V8.2 software. Master/Tracker roles
reverse correctly after removing cables from an FCM100Et Master.
Problem Operators could not use annunciator alarm panels numbered 7 through 12
when configuring alarm panel keys to support the “USER DISPLAY” or
“TOP PRIORITY” features. Only 6 annunciator alarm panels could be
configured with respect to these functions.
Resolution This problem has been corrected with V8.2 software. The correct number
of alarm panels (12) can be configured to support the “USER DISPLAY” or
“TOP PRIORITY” features.
122
10. Problems Resolved in V8.2 B0700RN – Rev C
Problem FCM100Et status was being generated and sent multiple times.
Resolution This problem has been corrected with V8.2 software. The correct
FCM100Et status is generated and sent only once.
Changes to the V8.2 ZCP image have lessened the frequency that the sec-
ond message appears, although the cause of the message still exists. The
observed behavior is a result of the limitations of current Ethernet switching
technology and Rapid Spanning Tree (RSTP) protocol technology after an
Ethernet switch or network failure. Refer to “Ethernet Switches Causing
FCM Failure and Recovery Messages” on page 96 for additional details.
123
B0700RN – Rev C 10. Problems Resolved in V8.2
Resolution These problems have been corrected in V8.2 I/A Series software.
Problem Alarm Manger was locking up after selecting and acknowledging a number
of alarms. A reboot was required to restore functionality. This problem
occurs when “om updates” is enabled.
Resolution This problem has been corrected in V8.2 I/A Series software. Alarms can be
selected quickly, cleared quickly, and the values update correctly.
Problem Points from the redundant FDSI FBM233 running the OPC driver were
becoming cyan. This problem was unrecoverable.
Resolution This problem has been corrected in Version 1.2.0 and later of the FBM233
software.
124
10. Problems Resolved in V8.2 B0700RN – Rev C
Problem ZCP270s were going single and sending Error Escalation Threshold
exceeded messages.
Resolution This problem has been corrected in V2.5 and later ZCP270 images.
Resolution This problem has been corrected in V8.2 I/A Series software. The cable
selection algorithm has been improved to prevent this problem from
occurring.
Problem The PDUS30 counter does not represent the total throughput of packets
through the ATS. This problem occurs because the PDUS30 counter does
not include IP packets in its count.
Resolution This problem has been corrected in V8.2 I/A Series software. The PDUS30
counter has been modified to include IP packets in its count.
125
B0700RN – Rev C 10. Problems Resolved in V8.2
Problem The Master Timekeeper takeover logic was not providing safeguards for
unforeseen error conditions on large systems, for example, to prevent unex-
pected changes in time settings because of misconfigured timekeeper
settings.
Resolution The additional safeguards have been added, and this problem has been cor-
rected in V8.2 I/A Series software.
Problem After 8.3 months of continuous operation, an FCM100Et pair can go into a
state where the Tracker module appears “failed” in SMDH, although it
actually has not failed. There is a 32-bit counter in the FCM100Et that
rolls over, causing the Master to send an incorrect status to System Manage-
ment, resulting in the failed status displayed in SMDH.
Resolution This problem has been corrected in Version 1.37 and later of the
FCM100Et image. The timers were expanded to 64 bits.
Problem After opening a station display from System Monitor and then returning to
the System Monitor domain, System Monitor exits.
Resolution This problem has been corrected in V8.2 I/A Series software. System Moni-
tor does not close under these circumstances.
126
10. Problems Resolved in V8.2 B0700RN – Rev C
Resolution This problem has been corrected in V8.2 I/A Series software. V8.2 software
prevents the startup of the FlexLM license manager.
Problem Due to a self test performed in the Tracker module, the Tracker was not
always taking over the Master role properly if the Master module was failed
or unplugged. To work around this problem (in a replacement scenario) the
Master module needed to be switched to operate as Tracker (using SMDH)
before the FBM228 module was replaced.
Resolution This problem has been corrected in V8.2 I/A Series software.
Problem The FBM228 fails to execute the FMS Initiate to the Yamatake device. The
FMS Initiate that the FBM228 sends does not get any response from the
device. The reason for this is that the FBM uses a FF H1 selector value
0x15, which is an incorrect selector value. The lowest value selector allowed
per the FF specification is 0x20.
Resolution This problem has been corrected in V8.2 I/A Series software.
127
B0700RN – Rev C 10. Problems Resolved in V8.2
Resolution This problem has been corrected in V8.2 I/A Series software. The software
has been improved so that FCMs and FBMs can ride through the ZCP270
reboot with no SMDH status changes.
Problem An FBM could not be downloaded if its letterbug was configured with a
“D” character in the third position.
Resolution This problem has been corrected in V8.2 I/A Series software. Letterbug
restrictions were removed, and a “D” is allowed as the third character of the
letterbug.
Problem The PIO subsystem was allowed to queue one more message than the chan-
nel’s queue control data structure supports. This resulted in an CP270 fail-
ures without the creation of dump files.
Resolution This problem has been corrected in V3.1 and later (?is this the latest?)
FCP270 and ZCP270 images, including the images released with V8.2 soft-
ware. The PIO subsystem was corrected to allow the correct number of
messages.
128
10. Problems Resolved in V8.2 B0700RN – Rev C
Problem Breaking a connection between the splitter and the switch on the PIO side
of a ZCP270 did not generate an alarm that was specific to the CP in Sys-
tem Management or System Monitor. The alarm provided in System Man-
agement for this condition was an off-line message associated with the
switch due to loss of link. A similar message was generated by breaking the
input from the station to the splitter. However, the ZCP270 continued to
appear white in System Management and there was no message stating the
ZCP270 had a fault.
Resolution This problem has been corrected in V8.2 I/A Series software. A System
Management alarm has been provided for this condition.
129
B0700RN – Rev C 10. Problems Resolved in V8.2
130
11. I/A Series Electronic
Documentation
This chapter provides information on installing and using 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 Windows platforms
(.pdf files), control station sizing spreadsheets (.xls files), and on-line Help files (.hlp files) not
available from their applications.
The Electronic Documentation CD-ROM for I/A Series software uses Adobe Reader® 6.0 or 7.0.
NOTE
K0173WT-F, which was shipped with the original I/A Series V8.2 media kit, has
been superseded by K0173WT-G. In addition to containing all information
included on Revision F, Revision G of the K0173WT CD also includes updates and
corrections to many documents.
NOTE
The I/A Series Electronic Documentation CD ships with the Adobe Reader 7.0. If
you already have Version 6.0 or later of Acrobat Reader with Search capability
installed, you can install Version 7.0, but it is not required.
♦ CD-ROM drive
♦ Keyboard/mouse
♦ Modem or Internet connection (for access to I/A Series hardware, software, and parts
for purchase).
131
B0700RN – Rev C 11. I/A Series Electronic Documentation
132
11. I/A Series Electronic Documentation B0700RN – Rev C
4. Follow the screen instructions and make the following selections, for installing Adobe
Reader 7.0:
a. Check the box next to “Adobe Reader 7.0” and click Next. If you already have an
earlier version of Acrobat Reader installed, you can simply install Adobe Reader
7.0 over it.
b. Continue to follow the instructions.
5. Follow the installation instructions until the last screen gives you options for viewing
the README file and running the I/A Series V8.x documentation CD K0173WT.
6. Select the desired option, and click Finish to complete the installation.
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 Documentation CD-ROM in the CD-ROM drive
prior to starting I/A Series Electronic Documentation.
NOTE
The I/A Series software version and documentation CD revision letter in the Start
menu may vary.
133
B0700RN – Rev C 11. I/A Series Electronic Documentation
Click on the plus + symbol at the left of each Bookmark to expand its subsections. For
example, click the + beside Part Number to access a list of documents sorted by part
number.
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 revi-
sion and title.
3. Click Go Back in the Bookmark list to return to the initial window.
134
11. I/A Series Electronic Documentation B0700RN – Rev C
11.6.3 Search
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 the I/A Series Electronic Documentation V8.0 CD.
Refer to the Adobe Reader help via the Help button for a complete explanation of the package
and for specific search capabilities and techniques.
To perform a full-text search:
1. If you are using V6.0, select Edit > Search or click the Search button (binoculars and
paper).
or
If you are using V5.0, select Edit > Search > Query or click the Search button (binoc-
ulars and paper).
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.
135
B0700RN – Rev C 11. I/A Series Electronic Documentation
136
Appendix A. 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-V8.2 hard drive of a Windows workstation for restoration onto the
Day 0 drive.
This chapter describes items you should review before migrating to V8.2. You can back up all user
files, and files that support applications.
A.2.1.1 FoxAPI/AIM*API
For detailed information on saving the AIM*Historian database, refer to AIM*Historian User's
Guide (B0193YL) and AIM*AT Installation Guide (B0193YM).
For detailed information on saving FoxAPI files and databases, refer to FoxAPI Installation Guide
(B0193UC).
NOTE
Stop all processes that write to the database (Historian, AIM*Historian, or
FoxAMI™, for example).
137
B0700RN – Rev C Appendix A. Files to Back Up/Restore
♦ \opt\fox\ais\bin\*.dat
♦ \opt\fox\ais\bin\an_server.tcp
♦ \opt\fox\ais\bin\an_server.dec
♦ \opt\fox\ais\bin\opensets
♦ \opt\aim\bin\an_init.tcp (server file)
♦ Program Files\aim\Common\an_init.cfg (client file for AIM*API 3.1 and later) or
\winnt\an_init.cfg or \windows\an_init.cfg (client file for pre-V3.1AIM*API and
FoxAPI)
♦ \opt\aim\bin\aimapi.cfg
♦ \opt\aim\bin\alias.cfg
1. Before restoration, make sure file names contain the correct workstation’s logical name.
2.
Files requiring changes need to be recustomized. Do not just replace Day 0 files with older files.
138
Appendix A. Files to Back Up/Restore B0700RN – Rev C
♦ \usr\fox\customer\config2
♦ \opt\menus
♦ \opt\disp
♦ \usr\disp
♦ \opt\customer
♦ \opt\custom\Initial_Disp.*2
♦ \opt\fox\env\*.*2
♦ Customer Display Files.
NOTE
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.
3. 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.
139
B0700RN – Rev C Appendix A. Files to Back Up/Restore
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 to support the upgrade, move it and verify proper
functionality before beginning the upgrade. This precaution ensures that, if you must abort the
upgrade, restoring the old drive also restores CSA functionality.
NOTE
In the following CSA procedures, keep in mind that the term “50 Series” applies to
workstations running the UNIX operating system, and the term “70 Series” applies
to workstations running the Windows operating system.
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 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
140
Appendix A. Files to Back Up/Restore B0700RN – Rev C
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)
141
B0700RN – Rev C Appendix A. Files to Back Up/Restore
142
Appendix A. Files to Back Up/Restore B0700RN – Rev C
9. Using an editor such as vi, edit the /usr/fox/bin/fox_apps.dat file to include ACSA.
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
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:
143
B0700RN – Rev C Appendix A. Files to Back Up/Restore
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
144
Appendix B. EEPROM Revision
Levels
This section indicates specific modules’ image revision levels.
NOTE
In the following tables, N/A indicates that the station or module is not available for
that I/A Series software release.
The following table lists control stations and their V8.2 image revision levels.
The following table lists the EEPROM revision level of the ATS.
145
B0700RN – Rev C Appendix B. EEPROM Revision Levels
The following table lists miscellaneous peripherals and their EEPROM revision levels. These are
unchanged from previous releases.
NOTE
In the following table, N/A indicates that the station or module is not available for
that I/A Series software release.
EEPROM
Software Version Version
V8.0B/
Devices Using IOM ID V7.1.1 V8.1 V8.1.1 V8.2 V8.2
FBM01, FBM02, FBM03, FBM03A, FBM03B, FBM19, IOM01 42.4 N/A 42.4 – 61.1
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 IOM02 42.3 N/A 80.1 – 61.1
H2C02A, H2C02B, H2C02F, H2C02G, H2C02J, H2C02K, IOM03 42.2 N/A 42.2 – 61.1
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 IOM04 64.1 N/A 80.1 – 61.1
146
Appendix B. EEPROM Revision Levels B0700RN – Rev C
Table B-4. Software Versions of 100 Series FBMs (Y Form Factor) (Continued)
EEPROM
Software Version Version
V8.0B/
Devices Using IOM ID V7.1.1 V8.1 V8.1.1 V8.2 V8.2
FBM07, FBM07A, FBM07B, FBM08, FBM09, FBM09A IOM05 41.1 N/A 80.1 – 61.1
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, FBM08, FBM12A, IOM06 42.1 N/A 42.1 – 61.1
FBM12B, FBM13, FBM20, FBM21, FBM24, FBM24A
through C, FBM25, FBM25A through C, F1M07, H2M24,
H3M07
<PULSE> FBM07A, FBM07B, FBM08, FBM12A, FBM12B, IOM07 41.1 N/A 41.1 – 61.1
FBM13, FBM20, FBM21, FBM24, FBM24A through C,
FBM25, FBM25A through C, F1M07, H2M24, H3M07
<LADDER> FBM07A, FBM07B, FBM08, FBM09A through D, IOM08 61.1 N/A 80.1 80.2 61.1
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 IOM09 42.3 N/A 80.1 – 61.1
FBM18, FBM43 IOM12 62.1 N/A 62.1 – 61.1
<HTG> FBM23 IOM13 40.2 N/A 40.2 – 61.1
Panel Display Station IOM14 80.1 N/A 80.1 – 61.1
FBM38 IOM22 40.4 N/A 40.4 – 61.1
FBM39, FBM44 IOM23 62.1 N/A 80.1 – 61.1
Display IOM28 40.2 N/A 40.2 – 61.1
<MDACT> FBM17, FBM17A through D, H2M17 IOM34 42.2 N/A 80.1 – 61.1
<MDPUL> FBM17, FBM17A through D, H2M17 IOM36 42.2 N/A 80.1 – 61.1
FBM43 IOM37 42.3 N/A 42.3 – 61.1
<Multibaud> FBM39, FBM44 IOM38 65.2 N/A 80.2 – 61.1
<Gas Chromatograph> FBM45 IOM39 40.1 N/A 40.1 – 61.1
42.2
masked
FBP10 IOM42 6.3.2 N/A 6.3.2 – 61.1
FBP11 (SMI, UCM) IOM43 6.3.2 N/A 6.3.2 – 61.1
FBP12 (FIO) IOM44 6.3.2 N/A 6.3.2 – 61.1
FBP13 (UFM) IOM45 6.3.2 N/A 6.3.2 – 61.1
FBP14 (UIO) IOM46 6.3.2 N/A 6.3.2 – 61.1
FBP10R IOM47 6.3.2 N/A 6.3.2 – 61.1
FBP11R IOM48 6.3.2 N/A 6.3.2 – 61.1
FBM46 IOM49 65.2 N/A 80.1 – 61.1
<PID> FBM04, FBM17, FBM17A through D, FBM22, H2M17 IOM52 61.2 N/A 80.1 – 61.1
147
B0700RN – Rev C Appendix B. EEPROM Revision Levels
Table B-4. Software Versions of 100 Series FBMs (Y Form Factor) (Continued)
EEPROM
Software Version Version
V8.0B/
Devices Using IOM ID V7.1.1 V8.1 V8.1.1 V8.2 V8.2
FBM37, BAOM37, H3M37 IOM53 42.1 N/A 80.1 – 61.1
H3M01 IOM54 4.21.05.03 N/A 4.21.05.03 – 61.1
BASI03, BDSM06 IOM55 5.06.05.03 N/A 5.06.05.03 – 61.1
BASI01, BASM01, BASO37 IOM56 4.21.05.03 N/A 4.21.05.03 – 61.1
FRM701, FRM711, FRMMPU IOM57 4.21.07.03 N/A 4.21.07.03 – 61.1
F2M68A IOM58 4.21.05.03 N/A 4.21.05.03 – 61.1
F2M67A IOM59 4.21.06.03 N/A 4.21.06.03 – 61.1
<FoxCom> FBM43 IOM73 65.2 N/A 80.2 – 61.1
EEPROM revision levels for Fieldbus Communication Modules (FCMs) are indicated in the
SOFTWARE REV A and SOFTWARE REV B fields in the System Management Equipment Information
display.
NOTE
In the following table, 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.
Table B-5. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor)
148
Appendix B. EEPROM Revision Levels B0700RN – Rev C
Table B-5. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) (Continued)
149
B0700RN – Rev C Appendix B. EEPROM Revision Levels
Table B-5. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) (Continued)
150
Appendix C. Installing/Updating
NIC Drivers
This section describes procedures for installing or upgrading the Network Interface Card
drivers for use with V8.2 I/A Series software.
Before starting to install I/A Series V8.2 software, the network interface card drivers must be
installed or updated from the K0173XA-D CD-ROM. Perform the procedures in this section
after loading (restoring) the operating system, and before installing SP2.
151
B0700RN – Rev C Appendix C. Installing/Updating NIC Drivers
5. Check the driver’s date and version number. The supported driver has a date of
3/8/2005, and a version of 8.5.14.0. If any other dates or version numbers are dis-
played, you must update the NIC driver as described below.
6. Click OK to close the window and return to the Device Manager.
7. Perform steps 4 through 6 for the second NIC.
NOTE
Every time the “System Settings Change” window appears offering you a chance to
restart the workstation, click No.
14. Right-click on Allied Telesyn AT-2701FX PCI 100Mb Fiber Ethernet Adapter,
select Properties, and click the Driver tab. The driver should have a date of
7/21/2005 and a version of 4.52.0.0. Click OK to close window.
15. Repeat steps 5-14 for the second Allied Telesyn (AMD PCNet) NIC.
16. Shutdown and restart the workstation for the driver to take full effect.
152
Appendix C. Installing/Updating NIC Drivers B0700RN – Rev C
NOTE
Every time the “System Settings Change” window appears offering you a chance to
restart the workstation, click No.
13. The Device Manager should indicate an Intel(R) Pro/1000 MT Desktop Adapter or
Intel(R) Pro/1000 GT Desktop Adapter.
14. Right-click the first Intel(R) Pro/1000 MT (or GT) Desktop Adapter in Device Man-
ager, select Properties, and click the Driver tab. The driver should have a date of
3/8/2005, and a version of 8.5.14.0. Click OK to close window.
15. Click the Advanced tab. Under the Advanced tab you will find a “Property” list box
and a “Value” drop-down list.
16. In the Property list box, select the Link Speed & Duplex property.
17. In the Value drop-down list, select 100Mbps/Full Duplex.
18. In the Property list box, select the Flow Control property.
19. In the Value list box, select Off.
20. Click OK.
21. Repeat steps 5-20 for the second Intel NIC.
22. Shutdown and restart the workstation for the driver to take full effect.
153
B0700RN – Rev C Appendix C. Installing/Updating NIC Drivers
154
Appendix D. Installing Optional
Workstation Components
This section describes procedures for installing or optional components on a V8.2 I/A Series
workstation.
155
B0700RN – Rev C Appendix D. Installing Optional Workstation Components
The number of satellites tracked should be between 4 and 8 satellites. The mes-
sage No satellites tracked indicates the system is not working. Refer to Time
Synchronization User’s Guide (B0700AQ) for information on time synchroniza-
tion hardware and setup.
Select Sync > Status > Check. The synchronized box should become checked to
indicate success.
d. Select Cancel and exit.
You have completed installation of the KSI TPRO/TSAT-PCI Control Utility.
156
Appendix E. Installing Microsoft
Security Patches
This section describes procedures for creating the equivalent of the K0173XY CD-ROM
containing the Microsoft Security patches that you can install on workstations running the
Windows XP Service Pack 2 operating system.
Microsoft does not allow the redistribution of security patches, and consequently, the
K0173XY-A Microsoft Windows XP Security Patch CD for Service Pack 2 is no longer shipped as
part of any I/A Series software media distribution kit. Installation of these security patches is not
mandatory. However, because I/A Series P92 workstations running the Microsoft Windows XP
Service Pack 2 operating system were tested with the patches installed, all Microsoft Security
patches that comprised the K0173XY-A CD-ROM should be installed prior to installing
I/A Series software.
157
B0700RN – Rev C Appendix E. Installing Microsoft Security Patches
9. WindowsXP-KB891781-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=9490e7d2-03c2-463a-
b3d0-b949f5295208&displaylang=en
10. Windowsxp-kb888113-x86-enu.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=6005C5A3-AFF2-4765-
B26F-BE47ED408E0B&displaylang=en
11. WindowsXP-KB890859-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=F0683E2B-8E8F-474F-
B8D8-46C4C33FCE99&displaylang=en
12. WindowsXP-KB896358-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=17833b94-af70-47bd-
872c-033a3f0e982a&displaylang=en
13. WindowsXP-KB896422-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=9CC719AD-5E57-4AEF-
9FB3-9F7AB7BB5D32&displaylang=en
14. WindowsXP-KB890046-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=F2247275-25F9-4937-
97CD-9334135D6D79&displaylang=en
15. WindowsXP-KB896428-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=b8ba775e-e9a7-47e9-
81a9-a68a71b9faac&displaylang=en
16. WindowsXP-KB901214-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=c5bcf2db-adce-42bd-
abee-1380f258158b&displaylang=en
17. WindowsXP-KB893756-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=b049004b-af28-41d7-
8ae6-7a3db15211f1&displaylang=en
18. WindowsXP-KB899591-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=a229f193-da3f-4014-
925d-1eacf5ba296c&displaylang=en
19. WindowsXP-KB899587-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=DD24F6FA-F6BB-4358-
8C2F-7F6AB405981A&displaylang=en
20. WindowsXP-KB896423-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?familyid=EF402946-1C3B-47E9-
9D51-77D890DF8725&displaylang=en
21. WindowsXP-KB905495-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=351C63A3-AB62-418D-
8678-3AF791D73A29&displaylang=en
22. WindowsXP-KB905414-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=19569E67-6D99-41FC-
9457-44EC524F6106&displaylang=en
23. WindowsXP-KB904706-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyID=2636cfce-49ea-4d06-
80ba-21a84f3658a5&DisplayLang=en
158
Appendix E. Installing Microsoft Security Patches B0700RN – Rev C
24. WindowsXP-KB905749-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=1559E44A-DDEE-4C86-
BF02-A6C3B9BEEE0C&displaylang=en
25. WindowsXP-KB901017-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=e0daf2d1-656c-4580-
94c1-8ab009b4ad4f&displaylang=en
26. WindowsXP-KB887742-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?familyid=d96edb1c-79f0-443b-
ac96-8b5dca23f395&displaylang=en
27. WindowsXP-KB886185-x86-enu.exe
http://www.microsoft.com/downloads/details.aspx?FamilyID=da66a0ac-55ca-4591-
b3e6-d78695899141&displaylang=en
28. WindowsXP-KB899589-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=4C1C2C16-99E7-4701-
A3F8-65B803B8B881&displaylang=en
29. WindowsXP-KB902400-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=20F79CE7-D4DB-42D7-
8E57-58656A3FB2F7&displaylang=en
30. WindowsXP-KB900725-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=F7241DEB-9E2D-401A-
9D71-10ACAB4450AF&displaylang=en
31. WindowsXP-KB896424-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=E38372B2-3BF6-4393-
B9A4-F34248C8073E&displaylang=en
32. WindowsXP-KB905915-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=E4B5BA57-D4F2-4798-
9154-2869E371C9D1&displaylang=en
33. WindowsXP-KB912919-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=0C1B4C96-57AE-499E-
B89B-215B7BB4D8E9&displaylang=en
34. WindowsXP-KB908519-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=6DAEA2AF-3723-4CDF-
B5BD-B21AC75B5243&displaylang=en
35. WindowsMedia9-KB911565-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F9EEF16-04F7-4DA8-
A0EF-1797B52D0B4B&displaylang=en
36. WindowsXP-KB913446-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=7BB21D74-C37B-472B-
BB10-71D4680680A7&displaylang=en
37. WindowsXP-KB911927-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=62535040-5204-4469-
B0BF-EAE14567C2D5&displaylang=en
159
B0700RN – Rev C Appendix E. Installing Microsoft Security Patches
These patches are available from the Microsoft Support Web site. As an example, the first patch
on the list is KB885836 and is available at the following link:
http://www.microsoft.com/downloads/details.aspx?familyid=703DE7D8-68D9-4A92-8C59-
87221F89EF14&displaylang=en
3. Click Download.
4. When a dialog box appears asking Do you want to run or save this file, click
Save.
5. When the Save As dialog box opens, save the file (for example,
WindowsXP-KB885836-x86-ENU.exe) to the directory created in Step 1.
160
Appendix E. Installing Microsoft Security Patches B0700RN – Rev C
6. Perform Steps 2 through 5 for all patches listed in “List of Recommended Security
Patches” on page 157. Be sure to save all the patches in the same hard drive folder.
After downloading the patches, you are ready to create an equivalent to K0173XY-A Microsoft
Windows XP Security Patch CD for Service Pack 2.
NOTE
You must use the .bat file extension for the file to be used as a batch file; using the
default “.txt” file extension will not work.
6. Save the patches and K0173XY_A.bat onto removable media, either a CD-ROM or a
USB memory stick.
During I/A Series software installation (using instructions in Chapter 7 “V8.2 Installation Proce-
dures”), you will be instructed to load the patches on to the P92 I/A Series workstations by invok-
ing the batch file that is on the removable media. If Windows Explorer opens up the E:\ drive
when a CD is inserted into the workstation, you can click K0173XY_A.bat to start the patch
updating process.
Alternately, you can open a Command Prompt window and start the batch file by executing
<drive>:\K0173XY_A.bat from the CD or USB memory stick containing the patches.
After all the patches are successfully installed, you must reboot the workstation, and then you can
continue installing I/A Series V8.2 software.
161
B0700RN – Rev C Appendix E. Installing Microsoft Security Patches
echo .
echo Press CTRL-C to abort, or
PAUSE
echo .
echo on
162
Appendix E. Installing Microsoft Security Patches B0700RN – Rev C
echo off
c:
date /T >> C:\Patchlog.txt
time /T >> C:\patchlog.txt
echo XPpro-all-post-sp2-rev-A-patches-installed >> C:\Patchlog.txt
echo .
echo .
Echo Security patches added for Windows XP Pro SP2
echo From Security patch CD
echo .
Echo ALL DONE please shut down and restart
echo .
PAUSE
163
B0700RN – Rev C Appendix E. Installing Microsoft Security Patches
33 Commercial Street
Foxboro, Massachusetts 02035-2099
United States of America
www.foxboro.com
Inside U.S.: 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. 0607