I/A Series System V8.2 Release Notes and Installation Procedures

B0700RN
REV C
I/A Series® System

V8.2 Release Notes and Installation Procedures
June 4, 2007
Invensys, Foxboro, AIM*API, AIM*AT, AIM*Historian, Fox, FoxAPI, FoxCAE, FoxDraw, FoxView, and
I/A Series are trademarks of Invensys plc, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.
Copyright 2006-2007 Invensys Systems, Inc.

All rights reserved
SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures................................................................................................................................. xiii
Tables.................................................................................................................................... xv
Preface................................................................................................................................. xvii
Revision Information ............................................................................................................ xvii
Reference Documents .......................................................................................................... xviii
1. Release Overview............................................................................................................... 1
1.1 Installation Overview .......................................................................................................... 1
2. Features of the V8.2 Release .............................................................................................. 5

2.1 Security ............................................................................................................................... 5
2.2 New and Upgraded Software Packages ................................................................................ 6
2.2.1 V2.8 System Definition Software ................................................................................ 6
2.2.2 V2.1 I/A Series Configuration Component (IACC) .................................................... 6
2.2.3 System Management Displays ..................................................................................... 6
2.2.4 V10.1 FoxView®/FoxDraw® Software ........................................................................ 6
2.2.5 V4.3.1 FoxAPI® Software ........................................................................................... 6
2.2.6 V3.2.4 AIM*API® Software ........................................................................................ 6
3. Upgrade Considerations .................................................................................................... 7

3.1 Supported Topologies and System Rules ............................................................................. 7
3.1.1 ATS Modes of Operation ............................................................................................ 8
3.1.1.1 LI Mode .............................................................................................................. 8
3.1.1.2 Extender Mode .................................................................................................... 8
3.1.2 System Sizing and Limitations ..................................................................................... 8
3.1.3 Station Hosting ........................................................................................................... 9
3.1.4 Overview of Control Station Rehosting ..................................................................... 10
3.2 Transition Scenarios .......................................................................................................... 11
3.2.1 Adding Mesh Stations to a Single Node .................................................................... 13
3.2.2 Connecting Multiple Nodes to The Mesh ................................................................. 14
3.2.3 Removing the Carrierband LAN from a Nodebus/Mesh Network ............................ 15
3.2.4 Removing the Carrierband LAN from a Nodebus Network ...................................... 16
3.2.5 Resetting Station Address Assignments and Updating System Topology ................... 18
3.2.6 Adding V8.2 Components to a V8.0x or V8.1 System .............................................. 18
3.2.7 Equipment Upgrade .................................................................................................. 18
3.3 System Configuration and Installation .............................................................................. 19
3.3.1 System Configuration ................................................................................................ 19
3.3.2 Software Installation .................................................................................................. 20
3.3.3 Controller Quick Fixes .............................................................................................. 21
3.3.4 Control Configuration .............................................................................................. 21
iii
B0700RN – Rev C Contents
3.4 Interoperability ................................................................................................................. 22

3.4.1 Control Database Interoperability ............................................................................. 22
3.4.2 Image Levels for Nodebus Control Stations ............................................................... 23
3.4.3 Display Interoperability ............................................................................................. 23
3.4.4 Network Fault Detection (NFD) .............................................................................. 24
3.4.5 Compound Summary Access (CSA) .......................................................................... 24
3.4.6 System Management and System Monitor ................................................................ 24
3.4.7 Device Monitor ......................................................................................................... 24
3.4.8 Timekeeping ............................................................................................................. 25
3.4.9 Alarm Processing ....................................................................................................... 25
3.4.10 Historian ................................................................................................................. 25
3.4.11 IP Communications ................................................................................................ 25
3.4.12 FoxAPI and AIM*API Software Compatibility ........................................................ 26
3.4.13 Intelligent Field Device Configuration .................................................................... 26
3.4.14 FoxSFC Software ..................................................................................................... 26
3.4.15 McAfee Virus Scan .................................................................................................. 26
3.5 Supported Software and Operations .................................................................................. 26
3.5.1 Supported API Functions in All Directions ............................................................... 28
3.5.2 Supported Operations from Any Source to Any Destination ..................................... 28
3.5.3 Additional Supported Operations from Mesh to Nodebus ........................................ 28
3.5.4 Additional Supported Operations from Nodebus to Nodebus ................................... 29
3.6 System Startup and Operation .......................................................................................... 29
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
5. Windows System Setup ................................................................................................... 37

5.1 V8.2 Documentation ........................................................................................................ 37
5.2 V8.2 Media ....................................................................................................................... 37
5.3 Additional Software Packages ............................................................................................ 38
iv
Contents B0700RN – Rev C
5.3.1 FoxAPI Software ....................................................................................................... 39
6. Defining Your System ..................................................................................................... 41

6.1 Notes on Configuring an ATS in System Definition ......................................................... 41
6.2 Upgrading V2.7 and Earlier System Definition Configurations ........................................ 41
6.3 Support for Workstation Processor (WP) Configurations .................................................. 42
7. V8.2 Installation Procedures............................................................................................ 43

7.1 Before You Begin .............................................................................................................. 43
7.1.1 Migrating Files .......................................................................................................... 43
7.1.2 Platform-Specific Hardware Upgrade Kits and Required Media ................................ 43
7.1.2.1 Microsoft Security Patch Media ......................................................................... 43
7.1.2.2 P92 Style A or B Workstation (Dell® PW340) .................................................. 44
7.1.2.3 P92 Style C Workstation (Dell® PW360) ......................................................... 44
7.1.2.4 P92 Style D Workstation (Dell® PW370) ......................................................... 45
7.1.2.5 P92 Style E Workstation (Dell® PW370) .......................................................... 46
7.1.2.6 P92 Style F Workstation (Dell® PW380) .......................................................... 46
7.1.2.7 P91 Server (Dell® PowerEdge 2800 and PowerEdge 2900) ............................... 47
7.2 Installation Classes ............................................................................................................ 47
7.2.1 Class A Installation .................................................................................................... 48
7.2.2 Class B Installation .................................................................................................... 49
7.2.3 Class C Installation ................................................................................................... 50
7.2.4 Class D Installation ................................................................................................... 52
7.3 Pre-Installation Procedures ................................................................................................ 54
7.3.1 System Definition Configuration and Creating a Commit Diskette .......................... 54
7.3.2 Creating Microsoft Security Patch CD or USB Memory Stick .................................. 56
7.3.3 Ensuring Correct Time Settings for Merged Mesh and Nodebus Systems ................. 56
7.3.4 Prepare Your System ................................................................................................. 56
7.3.4.1 Backing Up CSA Files ....................................................................................... 56
7.3.4.2 Consideration for PW380 RAID Users ............................................................. 57
7.4 Installation Procedures ...................................................................................................... 57
7.4.1 Installing V8.2 I/A Series Software ............................................................................ 57
7.4.1.1 Reinstalling Master Timekeeper ........................................................................ 57
7.4.1.2 Day 0 Installation Procedure for P92 Workstations ........................................... 58
7.4.1.3 Day 0 Installation Procedure for P91 Servers ..................................................... 63
7.4.1.4 Installing the Version 8.2 Trailer CD-ROMs (K0174AY and K0174BC) ......... 66
7.4.1.5 Setting Date and Time ...................................................................................... 67
7.4.1.6 Resetting Station Address Assignments .............................................................. 67
7.4.1.7 Updating CP270 Images ................................................................................... 68
7.4.1.8 Installing Additional Software ........................................................................... 69
7.4.2 Restoring CSA ........................................................................................................... 69
7.4.3 Loading Control Station Databases ........................................................................... 69
7.4.4 Performing EEPROM Updates ................................................................................. 69
7.4.5 Restoring I/A Series Standard Application Databases and Files .................................. 69
7.4.6 Restoring User Applications and Third-Party Files and Reinstalling Software ........... 70
7.4.7 Committing Nodebus Workstations ......................................................................... 70
7.4.8 Post-Commit for Pre-8.0 ........................................................................................... 70
7.4.9 Setting the Letterbug and Performing an Image Update of ATS Modules ................. 71
v
7.5 Postinstallation Procedures ................................................................................................ 72

7.5.1 Backing Up Hard Disks ............................................................................................ 72
7.5.2 Reconciling the Configuration .................................................................................. 72
8. V8.2 Operational Recommendations............................................................................... 73

8.1 System Configuration ....................................................................................................... 73
8.1.1 Blue Screen Resulting from COMM10 Ports Configured with Printers ................... 73
8.2 Software Installation .......................................................................................................... 73
8.2.1 Communication Loss After Incorrect Day 1 Software
Installation of Replacement ATS ........................................................................................ 73
8.2.2 Proper Method to Disable I/A Series Software During a Day 1 ................................. 74
8.2.3 Microsoft Security Patches ........................................................................................ 74
8.3 Workstations ..................................................................................................................... 75
8.3.1 IP Netmask Settings of Windows Workstations on the Nodebus .............................. 75
8.3.2 Java Support ............................................................................................................. 76
8.3.3 CPU Usage When Removing a Flash Drive .............................................................. 76
8.3.4 Resolution and Color Settings of Multi-Headed Workstation Displays ..................... 76
8.3.5 Installing Drivers for Parallel Printers Attached to Model P92 Workstations ............. 76
8.3.6 Screensavers ............................................................................................................... 77
8.4 Windows XP Service Pack 2 .............................................................................................. 77
8.4.1 Disabling Firewalls for Mesh Network Connections .................................................. 77
8.5 MKS Toolkit Commands ................................................................................................. 78
8.5.1 The compress and mkszip Command-Line Utilities .................................................. 78
8.6 Time Considerations ......................................................................................................... 80
8.6.1 Windows Time Service and Network Time Protocol Conflicts ................................ 80
8.6.2 Setting the Time on Nodebus Systems ...................................................................... 80
8.6.3 Time Inconsistencies and FoxView Lock-Ups on Nodebus Workstations .................. 80
8.6.4 Daylight Saving Time (DST) Control ....................................................................... 81
8.7 System Monitor ................................................................................................................ 83
8.7.1 System Monitor Messages Reporting Unavailable Workstations ................................ 83
8.8 Displays ............................................................................................................................ 83
8.8.1 Detail Display Differences on Nodebus and Mesh Workstations ............................... 83
8.9 Alarm Management Subsystem ......................................................................................... 84
8.9.1 FoxPanels Configurator Requirements ...................................................................... 84
8.9.2 Clearing Alarms from Alarm Displays ...................................................................... 84
8.9.3 Alarm Counts and Page Counts on the Title and Status Bars ................................... 84
8.9.3.1 Configuring Alarm Management Options for V8.x Systems Using ADMC ...... 85
8.9.4 Previously Deleted Alarm Manager Configuration Files ........................................... 86
8.9.5 Canceling “Accessing Historian” Dialog Box ............................................................ 86
8.9.6 Alarm History Display and AIM*AT Software Restrictions ...................................... 86
8.9.7 Device Monitor Causing Process Alarms to Stop Updating (CAR #1006913) ........... 86
8.9.8 FoxAPI ...................................................................................................................... 87
8.9.8.1 Starting the Foxhosts Program if Necessary ....................................................... 87
8.10 Historian Software .......................................................................................................... 87
8.10.1 Assumptions ............................................................................................................ 87
8.10.2 Historian Configuration .......................................................................................... 88
8.10.3 Data Collection Across ATS Boundaries ................................................................. 89
8.10.4 Historian Naming ................................................................................................... 89
vi
8.10.5 Historians Running on the Same Station ................................................................. 89

8.10.6 Porting the Configuration and Data from Legacy Historian to AIM*AT Software .. 89
8.10.7 Changing Points on a FoxView Trend Display to a New Historian Name .............. 90
8.10.8 Starting and Stopping AIM* Trend Servers ............................................................. 90
8.11 Integrated Control Configurator (ICC) ........................................................................... 91
8.11.1 FixAll Errors for Several FBMs ................................................................................ 91
8.12 ICCAPI ........................................................................................................................... 91
8.12.1 Error Message When Deleting a Block or Compound in ICCAPI .......................... 91
8.13 Control Software ............................................................................................................. 91
8.13.1 Time-Stamping and Reprioritizing Alarms .............................................................. 91
8.13.2 Re-Alarming Change in FCP270 and ZCP270 Versions 2.5 and Later ................... 92
8.13.3 Re-Alarming for Multiple Alarm Priority Types ...................................................... 92
8.13.4 Time Stamping of Re-Alarmed Messages ................................................................. 93
8.13.5 Migrating a Control Database to an FCP270 or ZCP270 ...................................... 93
8.13.6 Changing Block Modes on DO or AO Blocks ......................................................... 93
8.13.7 VAL_ID Character Limit ........................................................................................ 94
8.14 CP270 ............................................................................................................................. 94
8.14.1 Repeatedly Removing and Installing CP270 Fiber Cables ....................................... 94
8.14.2 Installing or Replacing CP270 and FCM100Et Modules in a Running I/A Series V8.x
System ................................................................................................................................ 94
8.15 Address Translation Station (ATS) .................................................................................. 95
8.15.1 Communicating Directly to an ATS ........................................................................ 95
8.16 Fieldbus Modules (FBMs) and Field Communication Modules (FCMs) ......................... 95
8.16.1 Performing General Downloads ............................................................................. 95
8.16.2 Verifying EEPROM Level of 200 Series FBMs in SMDH ...................................... 95
8.16.3 EEPROM Updating FBM201, 207, and 217 ......................................................... 96
8.16.4 Misleading System Monitor Messages After EEPROM Updates of FBM216/218 ... 96
8.16.5 EEPROM Updating FDSI FBMs (FBM230 to FBM233) ..................................... 96
8.16.6 Ethernet Switches Causing FCM Failure and Recovery Messages ............................ 96
8.16.7 Network Spanning Causing Failure and OOS Indications in SMDH ..................... 96
8.16.8 Letterbug Naming Restriction for FCMs ................................................................ 97
8.17 Tools and Utilities ........................................................................................................... 97
8.17.1 Live List Tool Posts Error on Launch ..................................................................... 97
8.17.2 FDA Driver Task .................................................................................................... 97
9. V8.2 User Notes .............................................................................................................. 99

9.1 Workstations ..................................................................................................................... 99
9.1.1 Bringing an Active Window Forward ........................................................................ 99
9.1.2 Using telnet and ftp Utilities on a Windows XP Workstation .................................. 99
9.1.3 Serial Expansion Card Cable-to-Port Mapping ......................................................... 99
9.2 Software Installation .......................................................................................................... 99
9.2.1 Selecting NICs During V8.2 I/A Series Software Installation .................................... 99
9.2.2 Relocating CSA ....................................................................................................... 100
9.2.3 Reinstalling Canceled/Failed Packages ..................................................................... 101
9.2.4 Canceling Software Installation Processes ................................................................ 101
9.2.5 Adding a Serial Printer During a Day 1 Install ........................................................ 101
9.2.6 System Monitor Tries to Start ................................................................................. 101
9.2.7 Successfully Creating and Appending to a Reconcile Diskette ................................. 102
vii
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
9.15.5 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223) .............................. 111

9.15.6 TIMSTP Parameter of the EVENT Block ............................................................. 111
9.15.7 Changing Engineering Range Limits in AOUT, AOUTR,
ROUT, and ROUTR Blocks ........................................................................................... 111
9.16 Electronic Documentation ............................................................................................ 112
9.16.1 DCI Block and Fail-Safe ....................................................................................... 112
9.16.2 PLSOUT Holding and Tracking States ................................................................ 112
9.16.3 Time Strobe Converter Installation Documented in B0700AQ ............................. 113
10. Problems Resolved in V8.2.......................................................................................... 115

10.1 FBM211 Values Freeze (CAR #1005709) .................................................................... 115
10.2 FBM224 Phasing Enhancements (CAR #1006285) ..................................................... 115
10.3 Release Level Information in SYSLVL ........................................................................... 115
10.4 Blue Screen During Day 1 Installation (CAR #1006761) ............................................. 116
10.5 Display Manager Redirect Command (CAR# 1006892) ............................................... 116
10.6 Counting and Retrieving Alarms for Alarm History Displays (CAR# 1006902) ........... 116
10.7 Off-Line Indication of GCIO and Annunciator Keyboards in SMDH (CAR# 1006911) 117
10.8 ACCUM and PID Default Displays (CAR# 1006964) ................................................ 117
10.9 Timeouts Causing Device Failure on FDSI FBMs (CAR# 1006848) ........................... 117
10.10 FCM100Ets Freezing After Power Failure (CAR# 1006999) ..................................... 118
10.11 Status of Switches and ZCP270 in System Management (CAR# 1007002, 1007285) 118
10.12 ROUT Default Display (CAR# 1007036) ................................................................. 118
10.13 Changing Block Order Using ICCAPI (CAR# 1007052) .......................................... 119
10.14 FIELD BUS A and FIELD BUS B Text Fields on ZCP270 Equipment Information
Display (CAR# 1007119) ..................................................................................................... 119
10.15 Error Messages on Windows XP Based Workstations (CAR# 1007128) ..................... 120
10.16 FCM100Et Letterbug Restriction (CAR# 1007185) ................................................... 120
10.17 CP Shadow Failure after Switch Failure (CAR# 1007241) .......................................... 120
10.18 Backup Alarm System Causing Lost Alarms (CAR# 1007247) .................................... 121
10.19 FCM100Et and Time Strobe (CAR# 1007374) .......................................................... 121
10.20 CP270 Alarm Messaging (CAR# 1007348, 1007102) ................................................ 121
10.21 Removing Control Bus Cables from Fault-Tolerant CP270s(CAR# 1007391) .......... 122
10.22 Role Reversals After Removing Cable from FCM Master (CAR# 1007392) .............. 122
10.23 Configuring Alarm Panels for USER DISPLAY and TOP PRIORITY Functions
(CAR# 1007509) .................................................................................................................. 122
10.24 Multiple FCM100Et Status Indications (CAR# 1007520) .......................................... 123
10.25 Equipment Failure Acknowledged and FCM
Failure and Recovery Messages (CAR# 1007531) ................................................................. 123
10.26 Foundation fieldbus Network Issues (CAR# 1007553) ............................................... 124
10.27 Alarm Manager Locking Up (CAR# 1007575) ........................................................... 124
10.28 Cyan Points from FBM233 (CAR# 1007587) ............................................................ 124
ix
10.29 ZCPs Going Single (CAR# 1007589) ......................................................................... 125

10.30 ECB110 HWTYPE and SWTYPE Parameters (CAR# 1007630) ............................... 125
10.31 Nodebus Cable Tests Causing ATS and
Workstation Failure and Recovery (CAR# 1007736) ............................................................ 125
10.32 Inconsistent PDUS30 Counts (CAR# 1007738) ......................................................... 125
10.33 Master Timekeeper Takeover Logic Improvements (CAR# 1007771) ......................... 126
10.34 FCM100Et Status Error (CAR# 1007799) ................................................................. 126
10.35 System Monitor Exiting (CAR# 1008008) .................................................................. 126
10.36 CPU Usage While Running Vulnerability Scanner (CAR# 1008039) ......................... 127
10.37 FBM228 Tracker Takeover Problems (CAR# 1008048) ............................................. 127
10.38 Incorrect FF H1 Selector Value Used by FBM228 (CAR# 1008090) ......................... 127
10.39 ZCP270 Reboot Causing FBM/FCM SMDH Status Changes (CAR# 1008171) ....... 128
10.40 Letterbug Restrictions Causing FBM Download Failure (CAR# 1008209) ................. 128
10.41 PIO Subsystem Alarm Correction (CAR #2001786) ................................................... 128
10.42 System Alarming When ZCP270 Loses PIO Connection (CAR# 2001900) ............... 129
11. I/A Series Electronic Documentation .......................................................................... 131

11.1 Hardware Requirements ................................................................................................ 131
11.2 Software Requirements .................................................................................................. 132
11.3 Installing I/A Series Electronic Documentation ............................................................. 132
11.4 Starting I/A Series Electronic Documentation ............................................................... 133
11.5 Browsing the User Documentation ............................................................................... 133
11.6 Searching I/A Series Electronic Documentation ............................................................ 134
11.6.1 Set up Preferences for Searching ............................................................................ 134
11.6.2 Add the I/A Series Electronic Documentation Search Index .................................. 134
11.6.3 Search .................................................................................................................... 135
11.6.4 Advanced Search ................................................................................................... 136
Appendix A. Files to Back Up/Restore............................................................................... 137

A.1 Saving Files ..................................................................................................................... 137
A.2 Files to Back Up/Restore for Day 0 Migration ................................................................ 137
A.2.1 Application Databases ............................................................................................. 137
A.2.1.1 FoxAPI/AIM*API ........................................................................................... 137
A.2.1.2 Control Libraries ............................................................................................. 138
A.2.2 Display-Related Files .............................................................................................. 138
A.2.3 System-Related Files ............................................................................................... 139
A.2.3.1 Application Files ............................................................................................. 139
A.2.3.2 Historian Files ................................................................................................. 139
A.2.3.3 User Applications and Third-Party Package Files ............................................ 139
A.3 Backing Up and Restoring Compound Summary Access (CSA) ..................................... 139
A.3.1 Backing Up CSA (CSA_Save) ................................................................................. 140
A.3.2 Restoring CSA (CSA_Merge) on 50/70 Series Stations ........................................... 141
A.3.3 Moving CSA Between 50/70 Series Stations ........................................................... 142
x
A.3.4 Moving CSA from Intel to 50 Series Stations .......................................................... 143

A.3.4.1 Backing Up Intel CSA (CSA_Save) ................................................................. 143
A.3.4.2 Restoring CSA (CSA_Merge) .......................................................................... 144
A.4 Saving and Loading Control Databases ........................................................................... 144
A.4.1 Saving Control Databases (SaveAlls) ....................................................................... 144
A.4.2 Downloading Control Databases ............................................................................ 144
Appendix B. EEPROM Revision Levels............................................................................. 145

B.1 Image Revision Levels for V6.x/V7.x Control Stations .................................................... 145
B.2 Image Revision Levels for V8.2 Components .................................................................. 145
B.3 100 Series FBM Software Versions ................................................................................. 146
B.4 200 Series FBM Software Versions ................................................................................. 148
Appendix C. Installing/Updating NIC Drivers.................................................................. 151

C.1 Checking Current NIC Driver Versions ......................................................................... 151
C.1.1 Allied Telesyn NIC Driver ..................................................................................... 151
C.1.2 Intel NIC Driver .................................................................................................... 151
C.2 Installing the Allied Telesyn NIC Driver (Fiber) ............................................................ 152
C.3 Installing the Intel NIC Driver (Copper) ....................................................................... 153
Appendix D. Installing Optional Workstation Components ............................................. 155

D.1 KSI Time Card Driver and Control Utility .................................................................... 155
D.1.1 Installing the Time Card Driver ............................................................................. 155
D.1.2 Installing the KSI TPRO/TSAT-PCI Control Utility ............................................ 155
Appendix E. Installing Microsoft Security Patches ............................................................ 157

E.1 List of Recommended Security Patches ........................................................................... 157
E.2 Download Instructions ................................................................................................... 160
E.3 Creating the Equivalent of the K0173XY-A CD-ROM .................................................. 161
E.4 Example Batch File ......................................................................................................... 162
xi
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.1 Installation Overview

Installing I/A Series V8.2 software requires a Day 0 installation. Controllers hosted by V8.2
workstations require an image update after installation of the workstation software, so careful
planning will be required. The On-Line Image Update (or On-Line Upgrade) procedure is not
available for Day 0 installations because the control database files (workfiles) are lost during the
Day 0 software installation. To restore the control database after a Day 0 installation, you must
perform an Initialize and LoadAll. The on-line image update procedure is available for future
upgrades that do not involve a Day 0 installation on the host workstation. Refer to Control Proces-
sor 270 (CP270) On-Line Image Update (B0700BY).
These release notes provide detailed instructions to support you in installing I/A Series V8.2 soft-
ware on a V8.x workstation and preparing for process operation. Thoroughly review this docu-
ment, as well as The MESH Control Network Architecture Guide (B0700AZ) prior to beginning
installation of your V8.2 I/A Series system.
Before performing any system configuration or software installation, read Chapter 3 “Upgrade
Considerations”. Chapter 3 presents information you should consider when upgrading to V8.2
software or transitioning to a mixed Nodebus and Mesh network configuration. Chapter 3 also
outlines several different scenarios for transitioning to a mixed Nodebus and Mesh system config-
uration and describes the procedures required for each scenario. Software interoperability issues
and supported operations between Mesh and Nodebus stations are also discussed in Chapter 3.
Prior to installation, you should also read Chapter 4 “Hardware Requirements”. This chapter lists
the hardware requirements for new and existing stations, and discusses supported Ethernet net-
working equipment. When in doubt regarding any part of the installation, contact the Global
CSC at the numbers listed in “Preface” on page xvii.
The Address Translation Station (ATS) allows communication between stations on The Mesh
control network and stations on the Nodebus, provided that the host of the ATS is at I/A Series
software V8.1 or later. ATS modules allow connection to Nodebus systems running I/A Series
software releases at V6.1 or newer.
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
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
Yes Is this a new

V8.2 system
?
No
Class A Class B Class C Class D

Installation Installation Installation Installation
Figure 1-1. Using Installation Procedures
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
2.2 New and Upgraded Software Packages

2.2.1 V2.8 System Definition Software
For an overview of System Definition software and detailed instructions on how to create a con-
figuration and produce a Commit diskette for I/A Series software installation, refer to System
Definition: A Step-by-Step Procedure (B0193WQ). For installation procedures and other consider-
ations relating to SysDef software, refer to System Definition Release Notes (B0193XW).
2.2.2 V2.1 I/A Series Configuration Component (IACC)

For an overview of IACC software and detailed instructions on how to create a control configura-
tion, refer to I/A Series Configuration Component (IACC) User’s Guide (B0400BP). For installation
procedures and other considerations relating to IACC software, refer to I/A Series Configuration
Component Release Notes (B0400BR). Do not use IACC for system configuration.
2.2.3 System Management Displays

For an overview of System Management Displays and how to use them, refer to System Manage-
ment Displays (B0193JC).
2.2.4 V10.1 FoxView®/FoxDraw® Software

FoxView® V10.1 software adds an important new feature for customers who will be utilizing
ATS modules to extend their existing Nodebus based system with Mesh network based worksta-
tions. FoxDraw displays can be configured on a V8.2 workstation and used on Nodebus-based
workstations running V9.0.2 or later versions of FoxView/FoxDraw software. This new feature
allows a single V8.2 engineering workstation to be used for all FoxDraw configuration and main-
tenance activities. Further, it allows customers using IACC V2.1 or later to gain the benefits of
coordinating databases and displays in a single engineering environment, even when the system
includes a combination of Nodebus and Mesh-based workstations and controllers.
For information about FoxView software, refer to FoxView Software (B0700BD). For information
about FoxDraw® software, refer to FoxDraw Software (B0700BE). FoxView and FoxDraw Soft-
ware Release Notes (B0700RJ) provides installation instructions and other considerations relating
to the FoxView and FoxDraw software packages.
2.2.5 V4.3.1 FoxAPI® Software

For information about FoxAPI® software, refer to FoxAPI User’s Guide (B0193UD). FoxAPI
Installation Guide (B0193UC) provides installation instructions and other considerations relating
to FoxAPI software.
2.2.6 V3.2.4 AIM*API® Software

For information about AIM*API® software, refer to AIM*AT Service Pack Release Notes
(B0400EL).
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.
3.1 Supported Topologies and System Rules

I/A Series V8.1 and later software provides control data connectivity between The Mesh control
network and an existing Nodebus network. Connectivity is accomplished with the Address Trans-
lation Station (ATS).
V8.1 and later software also provides a migration path from Nodebus/Carrierband LAN (token
bus) topologies to Mesh network topologies. The Address Translation Station (ATS) allows Node-
bus-based control stations to communicate with stations on The Mesh control network and vice-
versa, provided that the host of the ATS is at I/A Series software V8.1 or later. ATS modules allow
the connection of The Mesh control network systems to all I/A Series software releases at 6.1 or
newer. Refer to Address Translation Station User’s Guide (B0700BP) for detailed information about
the ATS.
The ATS allows for:
♦ Connection of The Mesh network to an existing I/A Series system Nodebus via 100
Mbps Fast Ethernet fiber optic or copper cable, up to a combined total of 1920 Node-
bus and Mesh stations.
♦ Communication between Mesh stations with existing I/A Series system Nodebus
stations.
♦ Using an ATS in Extender mode to extend an existing Nodebus-based I/A Series sys-
tem with V8.x workstations and FCP270/ZCP270 control stations. Refer to
Figure 3-1 for an example of a system using an ATS in Extender mode.
♦ Using ATSs in LI mode to replace LAN Interfaces (LIs) on a Carrierband LAN net-
work with the high speed Mesh network as the communication backbone between
nodes. Refer to Figure 3-1 for an example of a system using an ATS in LI mode.
Because the host of an ATS must be a Mesh workstation, The Mesh requires at least one worksta-
tion at V8.1 or later. A Nodebus-based system can only have one Mesh connection. Likewise, all
LAN Interfaces must connect to the same Carrierband LAN. Only one Carrierband LAN is
allowed.
For each node that will be directly connected to The Mesh, you must add an ATS. For multi-node
systems, only one node needs to be directly connected to The Mesh network using an ATS in
Extender mode in order for all nodes on the Carrierband LAN to communicate with Mesh sta-
tions. Additional nodes, however, can be directly connected to The Mesh using an ATS in LI
mode, resulting in less network load on the Carrierband LAN. If there is a large amount of com-
munication between the two networks via an ATS in Extender mode, the LI on this node may
become the bottleneck for traffic throughput. Refer to the latest revision of The Mesh Control Net-
work System Planning and Sizing (B0700AX) for additional information.
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 ATS Modes of Operation

When the ATS starts up, it determines if there is an LI on its node by querying the ATS
STA<letterbug>.bin configuration file on its boot host. If it finds an LI on the same node, the ATS
starts up in Extender mode; otherwise it starts in LI mode.
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.
3.1.1.2 Extender Mode

An ATS operates in Extender mode when there is an LI on the same node. In this configuration,
The Mesh appears as an extension of the node. Only one ATS can operate in Extender mode on
any given system.
3.1.2 System Sizing and Limitations

There is a limit of 1920 stations maximum on a combined Nodebus and Mesh I/A Series system.
A maximum of 30 nodes are available in an I/A Series system, that is, the number of LIs and ATS
in LI mode cannot exceed 30. The system needs to be sized for the expected network traffic.
Before configuring the system, you should analyze the network traffic in and out of the nodes that
are being migrated. The Mesh Control Network System Planning and Sizing (B0700AX) gives infor-
mation on network sizing and examples on calculating and comparing traffic rates between the
networks and between nodes.
One node on the network can contain both an LI and an ATS in Extender mode. This node,
shown in Figure 3-1, is referred to as a “bridging node”. All traffic between nodes using the Carri-
erband LAN and The Mesh passes through this bridging node. As stated above, in order to
achieve the highest possible performance in multi-node system with an ATS running in Extender
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
Nodebus 100 Mbps/1 Gbps
The Mesh and Nodebus 10 Mbps
The Mesh 5 Mbps
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.
3.1.3 Station Hosting

I/A Series V8.2 Mesh workstations support configuration and boot host support for the following
Nodebus stations:
♦ AB30B and AB30BFT – single and fault-tolerant Allen-Bradley Integrator 30 Style B
♦ CP30B and CP30BFT – single and fault-tolerant CP30 Style B
♦ CP40B and CP40BFT – single and fault-tolerant CP40 Style B
♦ CP60 and CP60FT – single and fault-tolerant CP60
♦ DI30B and DI30BFT – single and fault-tolerant Device Integrator 30 Style B
♦ MG30B and MG30BFT – single and fault-tolerant Modbus Integrator 30 Style B
9
♦ COMM 10 – Communication Processor 10 for FoxWatch support.
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.
3.1.4 Overview of Control Station Rehosting

Rehosting a control station from a Nodebus workstation to a Mesh workstation can be performed
before or after the V8.2 Day 0 installation. Following is an overview of steps required to rehost a
station:
♦ Reconfigure hosting.
♦ Perform a Day 1 installation on The Mesh.
♦ Perform a Day 1 installation on the Nodebus.
♦ Reconcile The Mesh and Nodebus.
Contact Global CSC for detailed procedures.
10
3.2 Transition Scenarios

Migration scenarios and topology examples for adding a Mesh network to a Nodebus system are
provided in the following subsections. You can:
♦ Add Mesh stations to an existing I/A Series Nodebus system with only a single node
♦ Add Mesh stations to an existing I/A Series Nodebus system with multiple nodes
♦ Replace the LAN Interfaces (LIs), using The Mesh as the backbone between nodes
instead of the Carrierband LAN
♦ Combine multiple I/A Series systems into one I/A Series system, for example, com-
bine an I/A Series V8.0B or later system and a V6.5.2 system.
See Figure 3-1 for a sample ATS network topology. Ideally, the bridging node would have only an
ATS and an LI on it, in order to minimize the traffic on the Nodebus. Optionally, the node can
also contain a workstation (see page 8). Refer to The Mesh Control Network System Planning and
Sizing (B0700AX) for information on analyzing network sizing and for additional examples of
determining the best scenario for migrating multiple nodes to The Mesh network.
Refer to Figure 3-2 for an example of an initial system configuration and the final configuration
after migration.
11
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
ATS ATS ATS

LI Mode LI Mode LI Mode
The Mesh
AW FCP FCP
Keys
Nodebus 5 Mbps
The Mesh 100 Mbps/1 Gbps
Figure 3-2. Comparison of Pre-Migration and Post-Migration Topologies
12
3.2.1 Adding Mesh Stations to a Single Node

You can add an ATS to a node provided that there are less than 64 other stations on the node.
There is a limit of 1920 stations maximum on a combined Nodebus and Mesh I/A Series system.
A maximum of 30 nodes are available in an I/A Series system, that is, the number of LIs and ATSs
in LI mode cannot exceed 30. However, you must follow the sizing guidelines in B0700AX. Mesh
stations (other than the ATS) do not count against the 64-station limit on a Nodebus.
A single-node system does not need an LI or Carrierband LAN to add Mesh stations. You only
need to add an ATS as described above. In this case, the ATS would operate in LI mode rather
than Extender mode, as there is no LI on the node.
Figure 3-3 shows the addition of Mesh stations to a single V6.x node and Figure 3-4 shows the
addition of Mesh stations to a single V7.x node.
AW
Nodebus
CP
ATS
LI Mode
The Mesh
AW FCP FCP
Nodebus 100 Mbps/

1 Gbps
The Mesh
Mesh stations added to single V6.x node
Figure 3-3. Adding Mesh Stations to a Single V6.x Node
13
V7.x Ethernet A
RCNI AW
NCNI NCNI V7.x Ethernet B
AW
Nodebus
CP
ATS
LI Mode
The Mesh
AW FCP FCP
Nodebus 100 Mbps/

1 Gbps
The Mesh
Mesh stations added to single V7.x node
Figure 3-4. Adding Mesh Stations to a Single V7.x Node
3.2.2 Connecting Multiple Nodes to The Mesh

You may wish to connect more than one node to The Mesh via an ATS while leaving the Carrier-
band LAN in place. You can add nodes to The Mesh one at a time or add nodes in groups.
Figure 3-5 shows the connection of multiple nodes to The Mesh network.
Only one node connected to The Mesh can have an LI. This is enforced by System Definition.
Connecting additional Nodebus nodes to The Mesh stations requires that you:
♦ Recommit workstations to update them with the latest configuration information
♦ Remove the LAN Interfaces from the Nodebus cell-buses before connecting the ATSs
that will replace them.
♦ Reboot other ATS modules to update them with the new STA<letterbug>.bin file
information.
♦ Reboot LIs so they can be updated with the new system information.
14
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
The Mesh 5 Mbps
Nodes added to The Mesh
Bridging node
Figure 3-5. Connecting Multiple Nodes to The Mesh Network
3.2.3 Removing the Carrierband LAN from a Nodebus/Mesh

Network
Before you can remove the Carrierband LAN infrastructure (Carrierband LAN and LAN Inter-
faces), configure your system in System Definition so that every node is connected to The Mesh
through an ATS. Figure 3-6 illustrates the removal of a Carrierband LAN from a combined Node-
bus/Mesh network. Removing the Carrierband LAN requires that you:
♦ Recommit workstations to update them with the latest configuration information
♦ Remove the LIs
♦ Reboot the ATS that was on the bridging node after Recommitting its host (this step
serves to change the ATS from Extender mode to LI mode).
It is possible to host Nodebus controllers from a Nodebus workstation across The Mesh.
15
Carrierband LAN
LI LI*
Nodebus
Nodebus
Nodebus
AW AW AW
CP CP CP
ATS ATS ATS

LI Mode LI Mode LI Mode*
The Mesh
AW FCP FCP
The Mesh 5 Mbps
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.
Figure 3-6. Removing the Carrierband LAN from a Nodebus/Mesh Network
3.2.4 Removing the Carrierband LAN from a Nodebus Network

It is possible to migrate from a Nodebus network with a Carrierband LAN to a Nodebus network
using The Mesh as a backbone. Removing the Carrierband LAN from the system requires that
you perform the following steps for each node:
♦ Configure, Commit, and boot the workstations
♦ Remove the LAN Interfaces from the Nodebus cell-buses
♦ Insert the ATS into the Nodebus cell-bus and connect the ATS to The Mesh.
16
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
ATS ATS ATS

LI Mode LI Mode LI Mode
The Mesh
AW FCP FCP Added items
The Mesh 5 Mbps
Added/Removed Items
Figure 3-7. Removing the Carrierband LAN from a Nodebus Network
17
3.2.5 Resetting Station Address Assignments and Updating

System Topology
During any change where the system topology is updated, for example, when connecting multiple
nodes to The Mesh, you must make sure that the controllers and ATS modules have the correct
address assignments.
During the Commital process, a unique STA<letterbug>.bin file is created for each ATS and con-
troller in the system. The file contains information such as IP addresses (Nodebus and Mesh IP
addresses for an ATS), NSAP address, primary and secondary MAC addresses, and information
about the topology of the system (how many ATSs, how many LIs, and on which nodes these sta-
tions reside). The file is located on the station’s boot host. Whenever the topology changes, new
information in each station’s STA<letterbug>.bin file must be downloaded from the host worksta-
tion to the associated stations. This includes all ATSs and Mesh controllers in the system. In addi-
tion, if LIs are added or removed, all other LIS must be rebooted to update their configuration
data.
Once the STA<letterbug>.bin file information is downloaded into the station’s resident flash
memory, it will boot with this information from this point forward.
The procedure to download the appropriate information differs depending on the current image
version of the station. 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. For a fault-tolerant CP270 pair at image version 3.1 or later, you must reboot both
modules (REBOOT STATION > BOTH) to properly download configuration data. For an ATS
at image version 1.0 or later, you only need to reboot the primary ATS (REBOOT STATION >
PRIMARY) to download its current configuration data.
For image versions prior to 3.1 for CP270s or 1.0 for ATSs, you must manually clear the old
information still residing in the station’s flash memory and force the station to download the cor-
rect information from its host. This is described on “Resetting Station Address Assignments” on
page 67.
3.2.6 Adding V8.2 Components to a V8.0x or V8.1 System

This is a standard expansion of an I/A Series system. The V8.0x or V8.1 workstations must be
Recommitted.
3.2.7 Equipment Upgrade

The following subsections describe upgrading equipment.
Nodebus Conversion to Mesh—Total Replacement

♦ 200 Series FBMs can be moved to FCP270s or ZCP270s
♦ 100 Series FBMs can be moved to FCP270s
♦ Fiber cables can be reused for FCP270s, ZCP270s, FCM100s, and ATSs.
Nodebus Connected to Mesh via ATS

♦ 200 Series FBMs can be moved to FCP270s or ZCP270s
♦ 100 Series FBMs can be moved to FCP270s.
18
ATS Replaces Carrierband LAN

♦ Nodebus Control Network Interface (NCNI) modules, Redundant Control Network
Interface (RCNI) modules, fiber-optic Nodebus extenders (FONBE), and Nodebus
extenders (NBE) can still exist on Nodebus
♦ P92 Style A or newer are the only workstations supported on The Mesh side
♦ Only some switches sold with Nodebus work on Mesh. It may be necessary to
upgrade firmware on some early switches; V05.07.12 for P0972MJ and P0972MK,
and 2.5.2.5 for P0972WP and P0972YC are the minimum versions for Mesh
support.
Refer to “Ethernet Networking Hardware” on page 32 for information on supported NICs and
Ethernet switches.
3.3 System Configuration and Installation

3.3.1 System Configuration
To configure a system with both Mesh components and Nodebus components, you must use Sys-
tem Definition V2.8 to create appropriate Commit diskettes. Refer to Chapter 6 “Defining Your
System”.
When combining multiple I/A Series systems, the basic requirements are the same whether the
network is a Mesh or a Carrierband LAN. Only one of the systems will have its station addresses
unchanged. All stations on all other systems will have changed addresses. If the address of a station
changes, then it must be rebooted. This constraint is not specific to the V8.2 release; it is a con-
straint that applies to all versions of I/A Series systems.
You can, however, ensure that the addresses of either the Nodebus components or The Mesh com-
ponents remain unchanged by using specific techniques to create the system definition.
To prevent addresses of the Nodebus components from changing, add Mesh system components
to an existing Nodebus configuration. Doing so allows the upgrade of a system without the need
to reboot the Nodebus CPs. All existing Mesh stations will require a reboot.
Alternatively, if you want the addresses of The Mesh components to remain unchanged, add the
Nodebus components to a Mesh configuration. This allows the upgrade of a system without the
need to reboot The Mesh controllers that are already at V8.2. All the Nodebus stations will
require a reboot.
The ATS operates in one of two modes, LI mode or Extender mode. When configured to operate
in LI mode, the ATS is assigned the same address as an LI. This address is the same for all LIs and
ATSs in LI mode, and it is a universal address that is understood by all I/A Series stations. When
configured to operate in Extender mode, the ATS does not take on the characteristics of a LI; it is
given an address that is different from the LI address.
Replacing the backbone of the Nodebus system requires replacing LAN Interface modules with
ATS modules. Node traffic that previously passed through the 5 Mbps Carrierband LAN now
passes through the 100 Mbps/1 Gbps Mesh network.
Using System Definition Software

When replacing the Carrierband LAN with The Mesh, you need to create The Mesh network
(and its switches) in System Definition. For each node, create an ATS module and connect it to a
19
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.
Commit Procedures and Reboot Information

All workstations in the system must be Committed (Day 0 or Day 1) with the same final System
Definition configuration. The final System Definition configuration is the configuration that
defines the combined systems. This allows the pre-V8.2 workstations to recognize the V8.2 com-
ponents. Because the V8.2 workstations and printers are then recognized by Nodebus stations,
alarm messages can be sent in either direction across the ATS. Refer to Address Translation Station
User’s Guide (B0700BP).
Commit diskettes must be produced using the Day 0 version of Media Distribution (10091) dis-
kettes. Media Distribution diskettes distributed for release updates cannot be used to produce
Commit diskettes. Mixed version systems require separate Commit diskettes for Committing
workstations at different release levels. For example, use the V8.0B Media Distribution Diskette
supplied with V8.0B media kits to produce the V8.0B/V8.1 Commit diskette, use the V8.2
Media Distribution Diskette supplied with the V8.2 media kit to produce the V8.2 Commit dis-
kette, and use the V6.4 Media Distribution Diskette supplied with V6.4 media kits to produce
the V6.4/V6.5 Commit diskette.
When adding Mesh stations to an existing system, you do not need to reboot the existing Node-
bus CPs. However, when the Nodebus workstations are Day 1 Committed, you must reboot the
workstations. There is no difference between adding Mesh components to a single-node system or
to a multi-node, Carrierband LAN based system. Ideally in a Carrierband LAN based system, you
would create a bridging node containing only an ATS, an LI, and optionally, one workstation to
minimize the traffic on the Nodebus. This configuration is shown in Figure 3-5.
3.3.2 Software Installation

The V8.2 release involves a Day 0 software installation on Mesh workstations. Workstations on
the Nodebus have no new software updates, however, you must reboot the workstations on the
Nodebus as stated above. Support for Day 1 installation is included in release V8.0 and later.
20
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.
3.3.3 Controller Quick Fixes

The FCP270 and ZCP270 image versions released with I/A Series V8.2 software is 3.8. The fol-
lowing quick fixes have been incorporated into Version 3.8:
♦ QF2001786 – ZCP270 V2.3
♦ QF1007102 – FCP270 V2.4
♦ QF1007348 – ZCP270 V2.4
♦ QF1007242 – FCP270 V2.5
♦ QF1007241 – ZCP270 V2.5.
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.
3.3.4 Control Configuration

You can use IACC to configure the control database for both Mesh control stations and Nodebus
control stations. When communicating to Nodebus stations, use a separate network to eliminate
excessive traffic on the I/A Series network. In order to use IACC for control configurations, all
Nodebus stations must be at release level V6.4 or later, because IACC does not support release
levels prior to V6.4. Using ICC is supported from Mesh workstations to Nodebus control stations
21
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.
3.4.1 Control Database Interoperability

Control databases are interchangeable between Nodebus and Mesh controllers. Nodebus SaveAlls
can be loaded into Mesh control stations. Mesh SaveAlls can be loaded into Nodebus control sta-
tions. None of the blocks that are new for Mesh will load into a Nodebus control station. Refer to
V8.0 Revision B Read Me First (B0700RC) for a list of new blocks. In addition, new block param-
eters are ignored by Nodebus controllers. Control stations must be at the release level listed below
or higher:
♦ CP60 must be at image 6.5.3
♦ CP30B must be at image 6.1.6
♦ CP40B must be at image 6.1.6
♦ DI30B must be at image 6.5.2
♦ AB30B must be at image 6.1.6
♦ MG30B must be at image 6.1.6.
Control stations that are not listed above or that are not at the revision levels listed above will not
load any Mesh station control blocks that have new parameters. The load will be aborted.
These images were released with I/A Series Release V7.1.1/6.5.2 software.
22
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.
3.4.2 Image Levels for Nodebus Control Stations

When an ATS is applied to a node that has control stations with image levels below Release
V7.1.1/6.5.2, there is a possibility of station “islanding” occurring. The stations become isolated
on a single cable, and the data points from stations appear cyan. To avoid islanding when applying
ATS modules to a node, it is recommended that all the following Style A and Style B control sta-
tions are upgraded to the following minimum I/A Series levels in order to obtain a Comex fix:
♦ Style A control stations should be upgraded to Release V7.1.1/6.5.2 and Style B
should be updated to at least Release V7.1/6.5.1.
♦ The following Style A stations received the Comex fix at Release V7.1.1/6.5.2: CP10,
CP30A, CP40A, AB-GW, AB-R-GW, GW30AB, GW30MOD, DI30A, and ACM.
♦ The following Style B stations received the Comex fix at Release V7.1/6.5.1: CP30B,
CP40B, AB30B, MG30B, DI30B, CP60, and LAN.
There is no image upgrade for stations not listed above. It is recommended that you upgrade to
one of the stations listed above.
3.4.3 Display Interoperability

FoxView V10.1 displays can be configured on a V8.2 workstation and used on Nodebus-based
workstations running V9.0.2 or later versions of FoxView/FoxDraw software. This new feature
allows a single V8.2 engineering workstation to be used for all FoxDraw configuration and main-
tenance activities. Further, it allows customers using IACC V2.1 or later to gain the benefits of
coordinating database and displays in a single engineering environment, even when the system
includes a combination of Nodebus and Mesh based workstations and controllers.
Display conversions are required if platforms are different, for example, a conversion is required
when transferring displays from the Windows to the UNIX operating system and vice versa. If the
platform is the same, a display conversion is not required, but is recommended so the display will
connect the first time. If no conversion is performed, the display will not connect until the second
call-up. Refer to FoxView/FoxDraw V10.1 Software Release Notes (B0700RJ) for specific details
regarding display compatibility and conversion.
The I/A Series V8.2 release, coupled with FoxView V10.1, FoxView V9.0.2, and AIM* V3.2.4,
now supports viewing historical trends on a Mesh workstation from a historian residing on a
Nodebus workstation (and vice versa).
23
NOTE
V10.1 FoxView software runs on Mesh workstations, and V9.0.2 FoxView software
runs on Nodebus workstations.
3.4.4 Network Fault Detection (NFD)

The NFD Nodebus Master software is present on all Nodebus workstations and LIs, but only one
Nodebus Master is active per node. The active master is selected by nomination and contention
algorithms. A Nodebus Master maintains network status information for a node and all stations
on the node. The active master coordinates Nodebus cable tests, and in the event of a detected
fault, sends a message to each workstation on the node to avoid the fault.
Like an LI on the Carrierband LAN, the ATS runs the Nodebus Master software. Because the
ATS receives Cable Test (off-node) packets from stations on The Mesh, it is convenient to have
the active master on the ATS itself. Doing this avoids the network latency of sending cable test
requests onto the Nodebus. As such, the NFD master on the ATS uses the revised contention
algorithm introduced in I/A Series V7.0 software to ensure the master is on the ATS, rather than
the LI or a workstation. You can override this selection using the Change Nodebus Test Initiator
pick from the Network view of SMDH. You must be on a Mesh station to change NFD master-
ship from an ATS to another station. Mastership will revert to the ATS when the ATS is
rebooted.
3.4.5 Compound Summary Access (CSA)

CSA can be assigned to run on either a Mesh workstation or a Nodebus workstation. If you have
CP270s on The Mesh network, CSA must reside on The Mesh network. If you need to move
CSA, refer to “Backing Up CSA (CSA_Save)” on page 140 and refer to user note “Relocating
CSA” on page 100.
3.4.6 System Management and System Monitor

System Monitor (SMON) and SMDH on the Mesh workstations will monitor and display all sta-
tions in the network, including switches. SMON and SMDH on the Nodebus workstations will
not recognize station types introduced in V8.x, including switches.
Mesh stations must be assigned to a SMON on a Mesh workstation. System Monitoring cannot
be done from Nodebus workstations to Mesh stations, but can be done from Mesh workstations
to Nodebus stations. Older System Monitors cannot monitor newer station types.
You must view Mesh stations and switches from SMDH on a Mesh workstation. A Nodebus
SMDH does not know about the new station types associated with the Mesh stations and
switches. SMDH should be confined to manipulating stations at the same or older software
releases.
3.4.7 Device Monitor

The Device Monitor operates across an ATS. The Device Monitor master will automatically run
on a V8.x workstation and will automatically disable any potential Nodebus device master.
If you have a Nodebus system that contains pre-V6.3 nodes, you must install Quick Fix 991068B
and Quick Fix 990273B on the pre-V6.3 nodes.
24
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.9 Alarm Processing

Alarms can be sent to any workstation (Nodebus or Mesh), and back-up printers can be utilized
across the ATS in either direction.
However, there are alarm processing restrictions between the Nodebus and The Mesh:
♦ Back-up Current Alarm Displays (CADs) cannot be utilized across the ATS in either
direction. A V8.x system cannot serve as an alarm backup for a pre-V8.x system and
vice versa.
♦ A Common Alarm Group (CAG) cannot contain both Mesh and Nodebus
workstations.
♦ A Mesh workstation’s Alarm History Display (AHD) has the ability to view alarm
messages stored in an AIM*Historian® database that resides on either the local work-
station or on any other Mesh workstation. Alarm history viewing is not compatible
between Nodebus and Mesh workstations. Alarm messages that are stored in a Node-
bus workstation’s historian cannot be viewed by a Mesh workstation’s AHD, and
alarm messages that are stored in a Mesh workstation’s AIM*Historian cannot be
viewed by a Nodebus workstation’s AHD.
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
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.
3.4.12 FoxAPI and AIM*API Software Compatibility

FoxAPI software versions 4.3.1 and later are only compatible with Versions 3.2.3 and later of
AIM*API software and vice versa.
These versions of FoxAPI and AIM*API software can share their OM connection lists (collections
of connected I/A Series objects). This feature of shared connections saves time and resources on
the station where both the FoxAPI and AIM*API software packages are installed.
If you want to take advantage of sharing object lists between FoxAPI and AIM*API software, you
must install compatible versions of FoxAPI software and AIM*API software. The latest compati-
ble versions of software are V4.3.1 FoxAPI software and V3.2.4 AIM*API software. AIM*API can
be installed from the AIM*AT® Service Pack 3.2.4 CD-ROM.
For additional information regarding AIM*AT and FoxAPI software, refer to:
♦ FoxAPI™ V4.3 Release Notes (B0193UH)
♦ AIM*AT Service Pack 3.2.4 Release Notes (B0400EL).
3.4.13 Intelligent Field Device Configuration

IFDC is not currently qualified for the V8.2 release. Users requiring IFDC should not upgrade to
V8.2 at this time.
3.4.14 FoxSFC Software

FoxSFC software is not currently qualified for the V8.2 release. Users requiring FoxSFC software
should not upgrade to V8.2 at this time.
3.4.15 McAfee Virus Scan

The version of McAfee Virus Scanning software supported on V8.2 workstations is Virus Scan
Version 8.0i. This version of virus scan software is not compatible with any other I/A Series soft-
ware version, and should only be installed on V8.2 workstations. Additionally, V8.2 is not com-
patible with any other version of Virus Scan software. Previous versions of virus scanning software
should not be installed on V8.2 workstations.
For information on obtaining the software, refer to Custom McAfee VirusScan Enterprise 8.0i
Installation (B0700CC).
3.5 Supported Software and Operations

Because the ATS provides a communication path between Mesh stations and Nodebus stations,
certain operations can be performed from Nodebus to Mesh and vice versa, or Nodebus to Node-
bus via a Mesh backbone. The following table lists these types of supported operations.
26
Table 3-1. Supported Software and Operations
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
Table 3-1. Supported Software and Operations (Continued)
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
3.5.1 Supported API Functions in All Directions

You can perform the following API functions in all directions:
♦ OM API
♦ FoxAPI
♦ AIM*API
♦ IPC API
3.5.2 Supported Operations from Any Source to Any Destination

The following operations are supported from any source to any destination:
1. Ability to get and set process variable data
2. Ability to view process and system alarms
3. Ability to acknowledge alarms
4. Ability to access historized data
5. Ability to print
6. Real-time trending
7. Operations (C:B:P “gets” and “sets”)
8. Peer-to-peer
9. Control application interoperability, for example, I/A Series Batch (COMEX).
3.5.3 Additional Supported Operations from Mesh to Nodebus

The following operations are supported from a Mesh station to a Nodebus station:
1. Read maintenance actions (SMDH)
2. Write maintenance actions (SMDH).
28
3.5.4 Additional Supported Operations from Nodebus to

Nodebus
The following operations are supported from a Nodebus station to a Nodebus station over the
Mesh:
1. Configure control stations and applications
2. Engineering actions (ICC configuration)
3. Read maintenance actions (SMDH)
4. Write maintenance actions (SMDH)
5. Operator Action Journal (OAJ)
6. Historical trending.
3.6 System Startup and Operation

Refer to the documents listed on page xviii for information about start-up and operation of the
installed Mesh and Nodebus combined system; these topics are not covered in this document.
29
30
4. Hardware Requirements
This chapter provides hardware and software requirements and lists supported and
unsupported hardware and software.
4.1 Minimum Workstation Hardware Requirements

for V8.2
V8.2 I/A Series software can be installed on the P91 and P92 workstation platforms. P92 Style A
or later workstations and P91 Style A or later servers are supported in the V8.2 system, as long as
they meet all specifications described in this section and are configured correctly.
Previously released versions of workstations currently being used in V7.x or V8.x systems may
require hardware and software changes including upgrading the memory, installing new network
interface cards (NICs), updating NIC drivers, replacing or recabling Ethernet switches, removing
RCNIs, and so forth. Refer to the hardware and software specific instruction document shipped
with the workstation and Appendix C “Installing/Updating NIC Drivers” for configuration and
installation information, and The MESH Control Network Architecture Guide (B0700AZ) for
instructions on connecting the workstation to The Mesh control network.
4.1.1 Memory Requirements for V8.2

The minimum memory requirement for a workstation to run in a V8.2 system is 512 MB. In
order to be ArchestrA® enabled, 1 GB of memory is required.
If your workstation does not meet the memory specification, upgrade the workstation’s memory
according to your needs. For information on base memory configurations of each workstation
type, refer to the appropriate subsection under “Platform-Specific Hardware Upgrade Kits and
Required Media” on page 43. To install the memory, refer to the hardware and software specific
instruction document shipped with the workstation.
4.1.2 Workstation Network Interface Card Support

This subsection describes the available and supported NIC options for V8.2. In order to connect
to The Mesh control network, your workstation must have two of the same NICs installed from
the list below. If your workstation does not have these NICs installed, replace them with two sup-
ported NICs of the same type before upgrading to V8.2 software.
♦ Allied Telesyn 100Base-FX fiber-optic Ethernet PCI card, Invensys Part Number
P0972WD. This is the latest fiber-optic Ethernet card offering shipped from the
factory.
♦ Intel Pro/1000 GT Single-Port 100Base-TX copper Ethernet PCI card, Invensys Part
Number P0923DV. This is the latest copper Ethernet card offering shipped from the
factory.
♦ Intel Pro/1000 MT 10/100/1000 Base-TX copper Ethernet PCI card, Invensys Part
Number P0923AA. This card is supported for V8.2, but is superseded by P0923DV.
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”.
4.2 Platform-Dependent Interface Card Limitations

The time synchronization card is not supported in the P91 server. Additionally, in order for the
P92 Style F to support the time synchronization card, the workstation must have two copper
NICs installed, and if necessary, the appropriate media converter.
4.3 Ethernet Networking Hardware

The following sections list support information for Ethernet switches and media converters. For
additional information on installing, configuring, and using Ethernet networking hardware, refer
to The MESH Control Network Architecture Guide (B0700AZ).
4.3.1 Supported Ethernet Switches

Following are the Ethernet switches supported anywhere in The Mesh control network running
V8.2 software:
♦ 24-port Enterasys fiber optic switch (P0972YC) – This switch requires a firmware
update; see “Ethernet Switches Requiring Firmware Updates” below.
♦ 24-port Enterasys copper switch (P0972WP) – This switch requires a firmware
update; see “Ethernet Switches Requiring Firmware Updates” below.
♦ N7 Chassis managed switch (P0972YE) – This switch requires a firmware update; see
“Ethernet Switches Requiring Firmware Updates” below.
♦ 16-Port 100Base-FX switch (P0972MJ) – This switch has been superseded by
P0972YC. Both P0972MJ and P0972YC require firmware updates; refer to “Ethernet
Switches Requiring Firmware Updates” below.
32
4. Hardware Requirements B0700RN – Rev C
♦ E7 Chassis managed switch (P0972MK) – This switch has been superseded by

P0972YE. P0972MK requires a firmware update; refer to “Ethernet Switches Requir-
ing Firmware Updates” below.
4.3.2 Supported Fieldbus-Only Ethernet Switch

The 8-port copper and 8-port fiber managed switch (P0972WG) was available for use with previ-
ous I/A Series releases. V8.1 and V8.2 I/A Series software versions support this switch when it is
used in a fieldbus-only configuration connecting a ZCP270 and an FCM100. It is not supported
if The Mesh has combined control and fieldbus networks or when participating in the Spanning
Tree Protocol on The Mesh control network.
4.3.3 Unsupported Ethernet Switches

The following Ethernet switches available for use with previous I/A Series releases are not avail-
able for use with V8.2 I/A Series software:
♦ 8-Port unmanaged 10/100 Mbps switch (no fiber optic port) (P0972MZ)
♦ 8-Port Copper managed switch (P0972MF) with built-in 100 Mbps multimode fiber
(MMF) uplink (supported in earlier I/A Series software releases)
♦ 8-Port Copper managed switch (P0972MG) with built-in 100 Mbps single mode
fiber (SMF) uplink (supported in earlier I/A Series software releases)
♦ 24-Port 10/100Base-T switch (P0972MH).
4.3.4 Ethernet Switches Requiring Firmware Updates

Following are Ethernet switches that are supported in I/A Series V8.2 software, but require firm-
ware updates:
♦ 24-port Enterasys fiber optic switch (P0972YC)
♦ 24-port Enterasys copper switch (P0972WP)
♦ 16-Port 100Base-FX switch (P0972MJ), superseded by P0972YC
♦ Blades for the N7 Chassis managed switch (P0972YE)
♦ Blades for the E7 Chassis managed switch (P0972MK), superseded by P0972YE.
4.3.4.1 P0972YC and P0972WP

P0972YC and P0972WP do not report the correct status of the Link Up and Link Down signals
to the SMDH display for the V8.x release. Note that these switches are qualified for V7.x systems,
but the switches require firmware updates before their link signals will be displayed correctly in
V8.x software.
The required minimum firmware level necessary for the P0972WP and P0972YC switches to
operate correctly with The Mesh control network is 2.5.2.5. The firmware update is available in
the AG100YT firmware upgrade kit, which contains a label and a CD-ROM. The CD-ROM
contains the firmware upgrade, instructions, and a tftp server to download the firmware. If you
have received one of these switches without a firmware upgrade kit, the kit can be obtained
through Global CSC.
33
4.3.4.2 P0972MJ and P0972MK Blades

The required minimum firmware level for the P0972MJ (16-port fiber) and the blades that go
into the P0972MK chassis for operation with The Mesh control network is 05.07.12. There is a
purchasable upgrade kit, P0972YZ, which contains a label and a CD. The CD contains the firm-
ware upgrade, instructions and a tftp server to download the firmware.
4.3.4.3 Firmware Updates for N-series Chassis Switches

When upgrading N-series (P0972YE, P0973AR, or P0973AS) switches in your network to firm-
ware revision 5.25.16, all V-series (P0972WP/YC) switches in the network need to be upgraded
to firmware revision 2.6.0.4. The N-series firmware upgrade is supported with the AG100ZL
upgrade kit, and the V-series firmware upgrade is supported with the AG100ZK upgrade kit.
V-series firmware upgrade 2.6.0.4 has been incorporated with new configuration features, as
defined in the release notes. Review the “Switch Configuration” section of the V-Series
(P0972WP/P0972YC) Switches, Hardware and Software Configuration Instructions (B0700CL) to
determine if the switches must be re-configured to take advantage of these added features.
4.3.5 Connecting Ethernet Switches

It is recommended that you use the gigabit uplink ports for inter-switch connections. It is
strongly recommended that you do NOT use 100 Mbit copper-to-fiber converters for inter-
switch connections.
4.3.6 User Notes for Ethernet Networking Hardware

4.3.6.1 Link Speed Settings of Allied Telesyn Fiber-Optic NICs
For 70 Series workstations with Allied Telesyn™ fiber-optic Ethernet NICs, the card’s driver
reports the link speed as 10 Mbps. The NIC actually is running at 100 Mbps. The fiber switches
and the Allied Telesyn NIC adapters are configured to run at 100 Mbps.
This speed is reported from the Networking tab of the Windows Task Manager, or the Local Area
Network Connection Status display, under the “Local Connection” screen associated with the
Foxboro Intermediate Driver (“FoxInt NDIS Intermediate Miniport Driver”).
4.3.6.2 Configuring Broadcast Suppression on V2 24-Port Switches

Broadcast suppression on the 100 Mb ports should be configured differently from the 1 Gb ports
on an Ethernet switch. However, the Enterasys V2 24-port switches (P0972YC and P0972WP)
with firmware versions earlier than 2.5.2.12 do not allow you to configure Broadcast suppression
differently for the 100 Mb and 1 Gb ports. Configure the broadcast suppression rate to 5,000
packets/second for all 100 Mb and 1 Gb ports or upgrade the firmware to version 2.5.2.12.
4.3.6.3 Interoperability of Mature and Preferred Chassis Switches
! 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
4.3.6.4 Configuring P0972MK/P0972MJ Ethernet Switches
! 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).
4.3.6.5 Metrobility Copper-to-Fiber Media Converter P0972XH

If you are migrating from a V7.x system to V8.x system, do not use the Metrobility copper-to-
fiber media converter, part number P0972MD. The Link Loss Carry Forward (LLCF) does not
work properly in these converters. The LLCF function is not required for V7.x systems (LLCF is
disabled for the V7.x converters), but is required (enabled) for V8.x systems.
The LLCF problem has been corrected with a newer version of the media converter, P0972XH,
and this is the converter that should be used with V8.x systems.
The only media converter that is acceptable for use with V8.x systems is P0972XH, and it must
have an Invensys revision level of “OC” or greater. Note that the Invensys revision level of “OC”
corresponds to the switch vendor’s revision level of “D”, and “Revision D” will appear on the
converter.
35
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.
5.1 V8.2 Documentation

Verify that you have all the necessary documentation required for your installation. Refer to “Ref-
erence Documents” on page xviii for a list of all documentation related to the V8.2 software
release. Most documents are located on the V8.2 I/A Series Electronic Documentation CD-ROM
(K0173WT), and you can find the latest revisions of the documents on the Global CSC webpage
http://support.ips.invensys.com.
5.2 V8.2 Media

Use the checklists below to verify that you have all the necessary media to install I/A Series V8.2
software. If your workstation does not conform to the specifications listed in Chapter 4 “Hard-
ware Requirements”, you may also need the upgrade kits and media listed in that chapter. You will
also need platform-specific media before installing V8.2. Refer to “Platform-Specific Hardware
Upgrade Kits and Required Media” on page 43 for a detailed list of media required depending on
the workstation type.
Table 5-1. I/A Series V8.2 Software Media
Part Number Description

I/A Series Software V8.x Media Kit (K0200YT-C)
I/A Series V8.2 CD-ROM for Windows XP/Server 2003 operating systems (K0174AU-A)
K0174AA-A AW70 OS
K0174AB-A WP70 OS
K0174AC-A System Management Display Handler (SMDH – Windows XP)
K0174AD-A Compound Summary Access (CSA – Windows XP)
K0174AE-A Integrated Control Configurator (ICC – Windows XP)
K0174AF-A Alarm Management System (AMS – Windows XP)
K0174AG-A System Monitor (Windows XP)
K0174AH-A Device Monitor (Windows XP)
K0174AJ-A Field Communication Module (FCM100Et) Image
K0174AK-A Field Device System Integrator
K0174AL-A FoxPanels (Windows XP)
K0174AM-A Message Management System (Windows XP)
K0174AN-A FDA Driver for Windows
K0174AP-A Field Control Processor 270 (FCP270 – OS1C70)
K0174AQ-A Z-Format Control Processor 270 (ZCP270 – OS1Z70)
37
B0700RN – Rev C 5. Windows System Setup
Table 5-1. I/A Series V8.2 Software Media (Continued)

K0174AR-A Address Translation Station (ATS) Package (OS1A70)
K0174AT-A Revision Level diskette (11001)
K0174AS-A Media Distribution diskette (10091)
K0174AY-A I/A Series V8.2 Trailer CDROM
K0174BC-A I/A Series V8.2 Trailer CDROM #2
K0173XN-B Pre-V8.1 Compatibility Diskette
B0700RN-C V8.2 Release Notes and Installation Procedures
K0173WT-G User Documentation V8.x
K0200YC-D FoxAPI V4.3.1 Media Kit
K0200YU-A Service Pack 2 for Windows XP Operating System, Menu Driven CD-ROM
K0173XA-D Ethernet NIC Driver CD
K0200RL-J System Definition 2.8 (SysDef 2.8) Windows Media Kit
NOTE
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.
5.3 Additional Software Packages

Additional software packages are usually installed from their respective CD-ROMs via standard
installation procedures. They are not included on the I/A Series system software media. Refer to
the associated documentation that accompanies the software for exact installation procedures.
Following is a list of the additional software packages for V8.2:
Table 5-2. I/A Series V8.2 Software Media

P0922RV FoxView/FoxDraw V10.x for Windows Media Kit
P0922RW FoxDraw Stand-Alone Software Media Kit
Q0301FZ AIM*AT® I/A Series Information Suite V3.2.4 (AIM*AT suite
including AIM*Historian software)
Q0301FX AIM*Historian® V3.2.4 (AIM*Historian software only)
K0200YC FoxAPI V4.3.1
K0173XG Windows XP Driver For KSI TSAT-PCI GPS System” CD-ROM ()
38
5. Windows System Setup B0700RN – Rev C
5.3.1 FoxAPI Software

The FoxAPI™ software is not included on the I/A Series software CD-ROM as in previous
releases; you must install FoxAPI from a separate FoxAPI Software CD-ROM. For information
on installing FoxAPI software, refer to FoxAPI Installation Guide (B0193UC). When you are
building a V8.2 Commit diskette in System Definition, make sure the FoxAPI software package
is not selected in System Definition when you are selecting software packages for an AW70P
(P92 or P91) workstation. Otherwise, the software installation log will contain an error message.
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.
6.1 Notes on Configuring an ATS in System Definition

The System Definition Release Notes (B0193XW) provides procedures for implementing an ATS in
a system configuration. For other System Definition procedures, including creating a pre-V8.x
node under a V8.x system, moving a pre-V8.x node back to a pre-V8.x network, refer to System
Definition Release Notes (B0193XW).
6.2 Upgrading V2.7 and Earlier System Definition

Configurations
If you have an existing System Definition V2.7, V2.6, V2.5, or V2.4 configuration (Mesh or
Nodebus), you must upgrade it to V2.8 before creating the Commit diskette. Perform the follow-
ing steps to upgrade a configuration created by an earlier release of System Definition to V2.8:
1. Export the configuration by selecting File > Export > Standard Export Diskette.
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.
6.3 Support for Workstation Processor (WP)

Configurations
The capability to configure an I/A Series workstation as a “WP” is not available with V8.x
software.
However, if you are upgrading a configuration containing WP70P stations that are connected to a
switch, these workstations are still allowed to connect to the switch in the upgraded configuration.
Those WPs that were previously connected to a Nodebus or were unconnected, as well as newly
created WPs, cannot be connected to an Ethernet switch in the upgraded configuration, and con-
sequently will not be implemented for a V8.x system.
To determine the connectability of each WP in your configuration, open the Hardware Editor for
the WP70P. A new read-only field called “Mesh Connection” is set to Allowed or Not Allowed.
If you want to migrate a WP to The Mesh, but the “Mesh Connection” field in the Hardware
Editor is “Not Allowed”, you must reconfigure the WP as an AW. In this case, delete the WP from
the configuration and add a new AW instead.
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.
7.1 Before You Begin

P92 Style A or later workstations and P91 servers are supported in the V8.2 system, as long as
they meet all specifications described in this section and are configured correctly.
Previously released versions of workstations currently being used in V7.x or V8.x systems may
require hardware and software upgrades. Refer to Chapter 4 “Hardware Requirements”.
NOTE
V8.2 does not support the migration of workstation integrators.
7.1.1 Migrating Files

If you are migrating files and/or control databases from an existing system, consider performing
the procedures in Appendix A “Files to Back Up/Restore”, which includes recommended steps
that you can take on your pre-V8.2 workstation to ensure a successful migration.
7.1.2 Platform-Specific Hardware Upgrade Kits and Required

Media
Verify that you have all the required media and documentation for I/A Series V8.2 installation.
You will need the V8.2 media kit in addition to the platform-specific items described in the fol-
lowing subsections.
7.1.2.1 Microsoft Security Patch Media

V8.2 I/A Series software has been tested and qualified with the security patches that were previ-
ously included on the K0173XY CD-ROM. Because Microsoft does not allow the redistribution
of security patches, this CD-ROM is not included with any I/A Series software media kit. How-
ever, you can create the equivalent of the K0173XY CD-ROM and install the recommended
patches during I/A Series V8.2 software installation. Refer to Appendix E “Installing Microsoft
Security Patches” for information on creating and installing the K0173XY equivalent.
43
B0700RN – Rev C 7. V8.2 Installation Procedures
7.1.2.2 P92 Style A or B Workstation (Dell® PW340)

The following media is required when installing V8.2 software on a P92 Style A or B workstation.
Table 7-1. Media Required for P92 Style A or B Workstation
Description Part Number

I/A Series® System Hardware and Software Specific Instructions for B0400HD
Model P92*A Workstation (PW340)
Dell Plus Restore CD K0175YC
Foxboro Ethernet NIC Driver CD K0173XA-D
Windows XP Service Pack 2 CD K0200YU
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.
Table 7-2. Upgrade Kits for P92 Style A or B Workstation

256 MB ECC RDRAM PC800 memory P0922MN
512 MB ECC RDRAM PC800 memory P0922KX
1 GB ECC RDRAM PC800 memory P0922MW
Allied Telesyn 100Base-FX Fiber Optic Ethernet (PCI) P0972WD
Intel Pro/1000GT Single-Port 100Base-TX Copper Ethernet (PCI) P0923DV
7.1.2.3 P92 Style C Workstation (Dell® PW360)

The following media is required when installing V8.2 software on a P92 Style C workstation.
Table 7-3. Media Required for P92 Style C Workstation

I/A Series®System Hardware and Software Specific Instructions for B0700BL
Model P92*C Workstation (PW360)
Dell Plus Restore CD K0173WS
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
Table 7-4. Upgrade Kits for P92 Style C Workstation

256 MB ECC DDR SDRAM memory P0922UV
512 MB ECC DDR SDRAM memory P0922UW
1 GB ECC DDR SDRAM memory P0922UX
Intel Pro/1000GT Single-Port 100Base-TX Copper Ethernet (PCI) P0923DV
7.1.2.4 P92 Style D Workstation (Dell® PW370)

The following media is required when installing V8.2 software on a P92 Style D workstation.
Table 7-5. Media Required for P92 Style D Workstation

I/A Series® System Hardware and Software Specific Instructions for B0700BR
Model P92*D Workstation (PW370)
Dell Plus Restore CD K0173XB
listed in Table 7-6. The P92 Style D was shipped with a minimum memory configuration of 512
(P0922KY), Allied Telesyn™ fiber-optic Ethernet card (P0972WD), or Intel single-port Ethernet
card (P0923AA).
Table 7-6. Upgrade Kits for P92 Style D Workstation

512 MB ECC DDR SDRAM memory P0922ZB
1 GB ECC DDR SDRAM memory P0922ZC
2 GB ECC DDR SDRAM memory P0922ZD
Intel Pro/1000GT Single-Port 100Base-TX Copper Ethernet P0923DV
(PCI)
45
7.1.2.5 P92 Style E Workstation (Dell® PW370)

The following media is required when installing V8.2 software on a P92 Style E workstation.
Table 7-7. Media Required for P92 Style E Workstation

I/A Series® System Hardware and Software Specific Instructions for B0700BR
Model P92*D Workstation (PW370)
Dell Plus Restore CD K0173XP
listed in Table 7-8. The P92 Style E was shipped with a minimum memory configuration of 512
card (P0923AA).
Table 7-8. Upgrade Kits for P92 Style E Workstation

512 MB ECC DDR SDRAM memory P0922ZB
1 GB ECC DDR SDRAM memory P0922ZC
2 GB ECC DDR SDRAM memory P0922ZD
(PCI)
7.1.2.6 P92 Style F Workstation (Dell® PW380)

The following media is required when installing V8.2 software on a P92 Style F workstation.
Table 7-9. Media Required for P92 Style F Workstation

I/A Series® System Hardware and Software Specific Instructions for B0700CB
Model P92*F Workstation (PW380)
Dell Plus Restore CD K0173XU
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
card (P0923DV).
Table 7-10. Upgrade Kits for P92 Style F Workstation

512 MB (2x256MB) ECC DDR SDRAM memory P0923GL
1 GB (2x512MB) ECC DDR SDRAM memory P0923GM
2 GB (2x1GB) ECC DDR SDRAM memory P0922GN
(PCI)
7.1.2.7 P91 Server (Dell® PowerEdge 2800 and PowerEdge 2900)

The following media is required when installing V8.2 software on a P91 server.
Table 7-11. Media Required for P91 Server

I/A Series® System Hardware and Software Specific Instructions B0700BW
for Model P91*A
I/A Series® System Hardware and Software Specific Instructions for B0700CQ
Model P91*B
Dell Plus Restore CD (P91*A) K0173XJ
Dell Plus Restore CD (P91*B) K0173YY
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”.
7.2 Installation Classes

Each of the following sections presents a flow chart of the steps required to install a V8.2 system
successfully based on the current system configuration. As depicted in the flow charts, not all pro-
cedures presented in this chapter are required for every installation class. Additionally, the order in
which you need to perform certain procedures may vary slightly for a particular installation class
from the order in which the procedures are laid out in this chapter.
47
7.2.1 Class A Installation

Class A installation involves a brand new installation of a V8.2 system.
Start for Class A

installations
Using SysDef V2.8, create a V8.2 Day 0

configuration with new V8.2 stations and
peripherals (Section 7.3.1).
Generate a V8.2 Day 0 Commit diskette

using V8.2 Media Distribution Diskette
(10091) (Section 7.3.1).
Perform the V8.2 Day 0 installation

(Section 7.4.1.2 or Section 7.4.1.3).
Install both of the V8.2 trailer CD-

ROMs (Section 7.4.1.4).
Set the date and time* (Section 7.4.1.5).
Perform CP270 Image

Updates (Section 7.4.1.7).
Install additional software on

V8.2 stations (Section 7.4.1.8).
Perform EEPROM Updates

(Section 7.4.4).
Perform a system backup.

(Section 7.5.1).
Reconcile your configuration.

(Section 7.5.2).
End for Class A

installations
* 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.
Figure 7-1. Class A Installation Flow Chart
48
7.2.2 Class B Installation

Class B installation involves installing V8.2 on an existing V8.0 Revision B or V8.1 system.
Start for Class B
installations
Make sure SysDef configuration is

reconciled (Section 7.3.1).
Import reconciled SysDef configuration

into SysDef V2.8 (Section 7.3.1).
For existing V8.0B/V8.1 stations going to

V8.2, set to Day 0 by marking all packages
to NOTYET (Section 7.3.1).
Configure new V8.2 stations and

peripherals (Section 7.3.1).
Generate V8.2 Day 0 Commit diskette

using V8.2 Media Distribution Diskette
(10091) (Section 7.3.1).
Any Generate V8.0B/V8.1 Day 1 Commit Install V8.1 Master

Yes
V8.0B/V8.1 diskette using V8.0B Media Distribution Timekeeper on any V8.0B
stations Diskette (10091) (Section 7.3.1). stations. (Section 7.4.1.1)
?
No

Install both of the V8.2 trailer CD-

ROMs (Section 7.4.1.4).
Reset station addresses.

(Section 7.4.1.6).
Perform V8.0B/V8.1 Day 1 Commit if new

stations or peripherals have been added to
Perform CP270 Image
the system.
Install additional software on Perform a system backup.

V8.2 stations. (Section 7.4.1.8). (Section 7.5.1).
Perform EEPROM Updates Reconcile your configuration.

(Section 7.4.4). (Section 7.5.2).
Restore files and applications End for Class B

(Section 7.4.5 and 7.4.6). installations
Figure 7-2. Class B Installation Flow Chart
49
7.2.3 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. The Nodebus configuration
is the baseline configuration and Nodebus stations will maintain their addresses.
Start for Class C
installations
Import reconciled Nodebus SysDef Import existing Mesh configuration into

configuration into SysDef V2.8 SysDef V2.8. Perform V8.2 configuration
(Section 7.3.1). and set to Day 0 by marking all packages
as NOTYET (Section 7.3.1).
Merge Mesh configuration into

Nodebus configuration (Section 7.3.1).
CAUTION!
It is required that you merge the
new Mesh configuration into the
Add ATSs to SysDef configuration per existing Nodebus configuration.
site upgrade plan (Section 7.3.1). Doing so is REQUIRED TO KEEP
NODEBUS SYSTEM ON-LINE.
Check configuration in SysDef. Make

corrections as required until config.
passes all checks (Section 7.3.1).
Generate Day 1 Commits for Nodebus Generate Day 0 Commits for

versions V7.0, V6.4, V6.2, V6.1 using The Mesh.
correct Media Distribution Diskette.
Any Generate V8.0B/V8.1 Day 1 Commit

V8.0B/V8.1 Yes diskette using the V8.0B Media
stations Distribution Diskette (10091).
?
No
Prepare system (Section 7.3.4):

Do CSA_Save on both sides.
Update switch configurations per
new SysDef parameters.
Any Install V8.1 Master

V8.0B Yes
Timekeeper on any V8.0B
stations stations (Section 7.4.1.1).
?
No
Proceed to Class C Flow Chart Page 2
Figure 7-3. Class C Installation Flow Chart, Page 1
50
Page 2 for Class C

installations

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
Set the date and time on The Mesh

(Section 7.4.1.5).
Reset station address assignments.

(Section 7.4.1.6).
Perform CP270 Image

Install additional software on Execute Post-Commit procedure for

V8.2 stations (Section 7.4.1.8). Pre-8.0 stations (Section 7.4.8).
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).
Bring nodes on-line and perform

Restore files and applications
system operational checks per site
(Section 7.4.5 and 7.4.6).
upgrade plan.
Perform Day 1 install on Nodebus Perform a system backup

Run rm_station on hosts of LIs
being replaced by ATSs and hosts
of CPs being rehosted.
Perform cable tests and clear all Reconcile your configuration
node faults. (Section 7.5.2).
End for Class C

installations
* 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.
** 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.
Figure 7-4. Class C Installation Flow Chart, Page 2
51
7.2.4 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. The Mesh configuration is
the baseline configuration and Mesh stations will maintain their addresses.
Start for Class D

Installations
If not already in SysDef V2.8, import Import RECONCILED Nodebus config.

RECONCILED Mesh SysDef into SysDef V2.8 and set to Day 0 by
configuration into SysDef V2.8 marking all packages as NOTYET
Merge Nodebus configuration into

Mesh configuration.
CAUTION!
It is required that you merge the
Nodebus configuration into the
Add ATSs to SysDef configuration per existing Mesh configuration.
site upgrade plan (Section 7.3.1). Doing so is REQUIRED TO KEEP
THE MESH SYSTEM ON-LINE.
Check configuration in SysDef. Make

corrections as required until config.
passes all checks (Section 7.3.1).
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).
Any Generate V8.0B/V8.1 Day 1 Commit

V8.0B/V8.1 Yes diskette using the V8.0B Media
stations Distribution Diskette (10091).
?
No
Prepare system (Section 7.3.4):

Do CSA_Save on both sides.
Any Install V8.1 Master

V8.0B Yes
Timekeeper on any V8.0B
stations stations (Section 7.4.1.1).
?
No
Proceed to Class D Flow Chart Page 2
Figure 7-5. Class D Installation Flow Chart, Page 1
52
Page 2 for Class D

installations

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
Set the date and time on The Mesh

(Section 7.4.1.5).
Reset station address assignments.

(Section 7.4.1.6).
Perform CP270 Image

Install additional software on Execute Post-Commit procedure for

V8.2 stations (Section 7.4.1.8). Pre-8.0 stations (Section 7.4.8).
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).
Bring nodes on-line and perform

Restore files and applications
system operational checks per site
(Section 7.4.5 and 7.4.6).
upgrade plan.
Perform Day 0 installation of Nodebus

Perform a system backup
stations and check network status
(Section 7.5.1).
(Section 7.4.7).
Perform cable tests and Reconcile your configuration

clear all node faults. (Section 7.5.2).
End for Class D

installations
Figure 7-6. Class D Installation Flow Chart, Page 2
53
7.3 Pre-Installation Procedures

Perform the steps in the following subsections to prepare your system for V8.2 installation.
7.3.1 System Definition Configuration and Creating a Commit

Diskette
If your Mesh or Nodebus System Definition configuration is not in System Definition V2.8, you
must import the configuration into V2.8. Separate Commit diskettes are required for each version
of I/A Series software in the system. To create the necessary Commit diskettes, follow all proce-
dures applicable to your installation class as indicated in the flow charts and in the sections below.
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
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
! 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.
7. Add ATSs to combined SysDef configuration per site upgrade plan.

8. Check the configuration and make corrections as required until the configuration
passes all checks.
9. Create Day 1 Commit diskettes for Nodebus Versions 7.0, 6.4, 6.2, and 6.1 using the
appropriate Day 0 release’s Media Distribution Diskette (10091).
10. Create a V8.2 Day 0 Commit diskette using the V8.2 Media Distribution Diskette
(10091).
create a Day 1 V8.0B/V8.1 Commit diskette using V8.0B Media Distribution Dis-
kette (10091).
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.
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.
7. Add ATSs to combined SysDef configuration per site upgrade plan.

8. Check the configuration and make corrections as required until the configuration
passes all checks.
9. Create Day 0 Commit diskettes for Nodebus Versions 7.0, 6.4, 6.2, and 6.1 using the
appropriate Day 0 release’s Media Distribution Diskette (10091).
10. Create a V8.2 Day 0 Commit diskette for The Mesh using V8.2 Media Distribution
Diskette (10091).
create a Day 1 V8.0B/V8.1 Commit diskette using V8.0B Media Distribution Dis-
kette (10091).
55
7.3.2 Creating Microsoft Security Patch CD or USB Memory

Stick
If you plan to install the recommended security patches, create the equivalent of the K0173XY
CD-ROM. Refer to Appendix E “Installing Microsoft Security Patches” for information on creat-
ing the K0173XY equivalent.
7.3.3 Ensuring Correct Time Settings for Merged Mesh and

Nodebus Systems
On an I/A Series System (V8.1 or later) that has a Mesh network connected to a Nodebus net-
work (Class C and D installations), you must be careful that time is set correctly before connect-
ing the networks via an ATS. The Master Timekeeper (MTK) on a Mesh workstation will
automatically assume mastership and disable any MTK running on a Nodebus workstation.
There is no difference in MTK priority for V8.x workstations. A system can have a V8.1 worksta-
tion as the primary MTK and a V8.2 workstation as the backup MTK. The roles of primary and
backup MTK are determined by system configuration. All workstations not configured as either
the primary or backup MTK have equal priority and will try to assume mastership should both
the primary and backup fail.
Before connecting the Mesh network to the Nodebus network via an ATS, you must ensure that
the Mesh has an MTK with the correct time. This is accomplished by performing the following:
1. For each Mesh workstation, set the Timezone and Daylight Savings Adjustment using
the Windows Date & Time applet.
2. On a Mesh workstation, set the correct time and date using SMDH. If using GPS, the
time and date will be set automatically and setting time via SMDH will be disabled.
3. Update V8.0B workstations with the V8.1 Master Timekeeper software (refer to
Section 7.4.1.1).
4. Set the Daylight Saving Time (DST) Control that determines how the Mesh MTK
sends DST time adjustments to the Nodebus stations (refer to Section 8.6.4)
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.
7.3.4 Prepare Your System

For Class C and D installations prepare your system for the upgrade by backing up CSA.
7.3.4.1 Backing Up CSA Files

When upgrading to V8.2 software, you may want to move CSA to a new host. If you have
CP270s on The Mesh network, CSA must reside on The Mesh network. Moving CSA is required
for Class D installations and for Class C installations when the system contains CP270s. Moving
CSA between hosts requires that you back up and restore the CSA files using the CSA_Save and
CSA_Merge utilities. If you want to move CSA between hosts, move it and verify proper func-
56
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.
7.3.4.2 Consideration for PW380 RAID Users

If you are using a P92 Style F (PW380) with RAID1, you must address “degraded drive” issues
prior to beginning the restore and I/A Series software installation process. If you restore the sta-
tion using the Restore CD and then correct the RAID issue, installation is unsuccessful and you
must repeat the restore process before continuing with I/A Series software installation.
Refer to Hardware and Software Specific Instructions for Model P92*F Workstation (PW380)
(B0700CB) for instructions on establishing a RAID set.
7.4 Installation Procedures

Note that steps in the following subsections may not be applicable to all classes of installations.
Perform the steps indicated in the flow charts in the previous sections.
7.4.1 Installing V8.2 I/A Series Software
! 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.
7.4.1.1 Reinstalling Master Timekeeper

The V8.0B Master Timekeeper functionality is not compatible with the V8.1 and V8.2 Master
Timekeepers. For this reason, it is required that you install the V8.1 Master Timekeeper on V8.0B
workstations if you plan to have V8.0B workstations running either temporarily or permanently
on the I/A Series V8.2 system. The V8.1 Master Timekeeper is used instead of the V8.2 Master
Timekeeper because it uses the same version of Nutcracker installed on the V8.0B workstation,
whereas a V8.2 workstation has an upgraded Nutcracker.
57
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
A check mark should appear to the left of this package.

5. Click Load Selected Packages.
6. Under Multiple Media Selection, select Unstamped Floppy and click Load Selected
Media.
A dialog box prompts you when setup needs the next disk.
7. Insert the K0173XN diskette and select Load in the dialog box.
8. Click Skip the next time the dialog box appears.
The dialog box Installing I/A Series Files appears. When the installation is done, a dia-
log box prompts you to restart the workstation.
9. Select No, I will restart my computer later, click Finish, and remove the 3.5-inch
diskette.
10. Reboot the system. (The workstation must be rebooted before it is connected to The
Mesh network that has an ATS connected to a Nodebus network.)
11. Verify that the Master Timekeeper has been re-installed correctly by confirming the
sums of the following files:
/usr/fox/exten/hpstk.exe 26923 240
/usr/fox/sp/dst.cfg 501 1
/usr/fox/system32/foxfdr.dll 8668 879
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.
7.4.1.2 Day 0 Installation Procedure for P92 Workstations

On each workstation on which you want to install I/A Series V8.2 software, perform the follow-
ing steps:
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
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.
59
♦
For 3 GB, use 4606 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.
b. A Welcome screen appears. Click Continue.

c. Click Install now to install, and the installation process extracts the SP2 files.
This takes a few minutes.
d. The Windows XP Service Pack 2 Setup Wizard starts. Click Next.
e. At the License Agreement, click I Agree, and then click Next.
f. Click Next to accept the default directory.
g. Wait for the installation process to complete. When the wizard is complete, click
Finish to restart the PC. Wait a short time, and the platform will reboot on its
own.
60
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
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
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.
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.
10. Proceed to “Installing the Version 8.2 Trailer CD-ROMs (K0174AY and K0174BC)”
on page 66.
7.4.1.3 Day 0 Installation Procedure for P91 Servers

On each P91 server on which you want to install I/A Series V8.2 software, perform the following
steps:
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
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.
c. Set the time and date. Perform the following:

♦ 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.
d. Update the NIC drivers from K0173XA-D. Refer to Appendix C “Install-
ing/Updating NIC Drivers” on page 151.
2. By default, the firewall feature is turned off for the P91. To enable the firewall for the
network interface that is NOT being used for the I/A Series control network, proceed
as follows:
b. Note the “Local Area Connection” number for the corporate non I/A Series net-
work interface. The connection number associated with the NIC appears under
c. Right-click the network connection and select Properties.
opens.
e. Click the Advanced tab, and select the box for the network interface that corre-
sponds to the NIC number noted in Step b above.
f. Click OK, and then OK again.
g. Click Yes when a dialog box appears asking if you want to enable ICS.
h. Close the “Network Connections” window.
3. Disable Virus Scan software before proceeding with installation.
4. 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 document shipped
with your server. Be sure you use only V8.2 media. (The same media is used on the
Windows XP and Windows Server 2003 operating systems.)
64
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.
b. Note the “Local Area Connection” number for the FoxInt NDIS Intermediate
Miniport Driver. The connection number associated with the NIC appears under
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.
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.
6. Proceed to “Installing the Version 8.2 Trailer CD-ROMs (K0174AY and K0174BC)”
below.
65
7.4.1.4 Installing the Version 8.2 Trailer CD-ROMs (K0174AY and

K0174BC)
NOTE
To complete the installation of I/A Series V8.2 software on an AW, you must install
two trailer CD-ROMs. The two trailer CD-ROMs are labeled as follows:
– “Version 8.2 Trailer CD-ROM for Windows (K0174AY)” and
– “Version 8.2 Trailer CD-ROM #2 for Windows (K0174BC)”.
On a WP, install the first trailer CD-ROM only.
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.
7.4.1.4.1 Installing Version 8.2 Trailer CD-ROM (K0174AY)

1. Insert the Version 8.2 Trailer CD-ROM for Windows XP (K0174AY).
2. A command prompt automatically pops up, and Installing IA Series System
Version 8.2 Trailer appears.
3. Press Enter to begin the installation, and Starting Installation appears on the
screen.
4. When the installation is complete, the following message appears:
Installation complete. View <DIR> for installation details
where <DIR> is D:\usr\fox\sp\SetupLog.<time stamp>.
5. If this is an AW, proceed to Section 7.4.1.4.2 below to install Version 8.2 Trailer CD-
ROM #2 (K0174BC). If this is a WP, trailer software installation is complete. Reboot
the workstation.
7.4.1.4.2 Installing Version 8.2 Trailer CD-ROM #2 (K0174BC)

1. Insert the Version 8.2 Trailer CD-ROM #2 for Windows XP (K0174BC).
2. A command prompt automatically pops up, and Installing IA Series System
Version 8.2 Trailer #2 appears.
3. Press Enter to begin the installation, and Starting Installation appears on the
screen.
4. When the installation is complete, the following message appears:
Installation complete. View <DIR> for installation details
where <DIR> is D:\usr\fox\sp\SetupLog.<time stamp>.
5. Reboot the computer to complete installation.
7.4.1.4.3 Installing Fixes for cs_alarm and REDL Applications

Refer to the hardware and software specific instructions document shipped with your processor,
and install the fixes for the cs_alarm program and the REDL program.
66
7.4.1.5 Setting Date and Time

For an internally sourced Master TimeKeeper (MTK), set the local date and time using the
SMDH Set Date and Time display:
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.
7.4.1.6 Resetting Station Address Assignments

You must make sure that the controllers and ATS modules have the correct address assignments,
especially if system topology has changed. (See “Resetting Station Address Assignments and
Updating System Topology” on page 18.) The procedure to reset station address assignments dif-
fers depending on the current image version of the station.
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
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.
7.4.1.7 Updating CP270 Images
! 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.
Perform the following:

1. If your CP270s currently have databases installed, initialize the CP270s and reboot.
2. Verify the following checksums on the FCP270 and ZCP270 boot host workstations
prior to performing IMAGE UPDATE.
CP File Checksum
FCP270 /usr/fox/sp/files/OS1C70 51742 3069
ZCP270 /usr/fox/sp/files/OS1Z70 58471 4123
68
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.
7.4.1.8 Installing Additional Software

After restarting the station following I/A Series software installation, you may need to perform
one or more of the following tasks:
1. If not already installed, install FoxView™ and FoxDraw™ V10.1 software from the
FoxView/FoxDraw V10.1 CD-ROM. Refer to FoxView™ and FoxDraw™ Software
Release Notes (B0700RJ) for installation instructions.
2. Install AIM*Historian® software according to the instructions provided with the
AIM*Historian media.
3. If you want FoxAPI™ software, install this software package from the FoxAPI CD-
ROM. Refer to FoxAPI Installation Guide (B0193UC) for installation instructions.
4. Install any other software media for selected optional packages.
7.4.2 Restoring CSA

If you backed up CSA, restore the CSA files using the CSA_Merge utility described in “Restoring
CSA (CSA_Merge) on 50/70 Series Stations” on page 141.
7.4.3 Loading Control Station Databases

Perform a LoadAll of the control station databases. Depending on the configurator you are using,
refer to I/A Series Configuration Component (IACC) User’s Guide (B0400BP) or Integrated Control
Configurator (B0193AV) for procedures to download the control station databases. This step is
not required if you are not migrating control databases.
7.4.4 Performing EEPROM Updates

Perform an EEPROM update of all FCMs and FBMs that are not at the revision level specified
for V8.2. Refer to Appendix B “EEPROM Revision Levels”. It is recommended that you bring
your FBMs up to the latest revision levels at the earliest convenient time.
7.4.5 Restoring I/A Series Standard Application Databases and

Files
For additional information on restoring and reinstalling, see Appendix A “Files to Back
Up/Restore”. This step is not required if you are not migrating application databases and files.
Refer to System Administration Guide (Windows XP Operating System) (B0400HE) and Windows
Help for restore procedures. Those files that need to be used as reference in recustomizing V8.2
files should not be automatically restored to their original locations. Rather restore the files to a
temporary prior release directory, such as \priorrel so that file content can be viewed.
69
! 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.
7.4.6 Restoring User Applications and Third-Party Files and

Reinstalling Software
Restore any databases and files related to user or third-party packages that were backed up. Rein-
stall the user applications and third-party packages using vendor media. This step is not required
if you are not migrating applications or third-party software.
7.4.7 Committing Nodebus Workstations

This step is applicable to Class C and D installations. After updating workstations on The Mesh
network to V8.2 software, you must Commit (Day 0 or Day 1) the workstations on the Nodebus
side of the network using Commit disks created from the same System Definition configuration
(the final configuration that defines the combined systems; see page 20). Failing to Commit the
stations on the Nodebus that are SMON hosts with the final System Definition configuration
causes the ATS to enter a state where you cannot perform an IMAGE UPDATE on the ATS, and
the ATS does not report messages to the System Monitor or communicate with the I/A Series Let-
terbug Configurator.
Additionally, after performing the Commit on Nodebus workstations for Class C and D installa-
tions, run “rm_station” on hosts of LIs being replaced by ATSs and on hosts of CPs being moved
to a new host. Perform necessary cable tests, and clear all node faults.
7.4.8 Post-Commit for Pre-8.0

NOTE
Do not install this software on Mesh workstations. Perform this step on all Nodebus
workstations after every Commit installation or any installation where the worksta-
tion operating system is selected for installation.
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.
Instructions for Windows Workstations

To execute the procedure on Nodebus (V6.x/V7.x, etc.) I/A Series workstations running the Win-
dows NT Workstation 4.0, Windows NT Server 4.0, or Windows XP operating system (AW and
WP):
1. Insert the K0173XN diskette.
2. Open a Command Prompt window, and type the following:
70
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.
Instructions for Solaris Workstations

To execute the procedure on Nodebus (V6.x/V7.x, etc.) I/A Series workstations running the
Solaris 2.5.1 or Solaris 2.8 (also referred to as “Solaris 8”) operating system (AP, AW, and WP):
1. Insert the K0173XN diskette.
2. Open a VT100 session, and type the following:
cd /
tar xvf /dev/fd0 ./usr/fox/bin/mkhosts.sh
cd /usr/fox/bin
mkhosts.sh
3. A reboot of the workstation is not required.
7.4.9 Setting the Letterbug and Performing an Image Update of

ATS Modules
This step is applicable to Class C and D installations. For Class C installations, it is recommended
that you set the letterbug and perform an IMAGE UPDATE while the ATS modules are not con-
nected to the Nodebus network. This can be accomplished using a spare 1x8 mounting structure.
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.
Perform the following steps:

1. Plug in a single ATS into the system without connecting to The Mesh network.
2. Set the ATS letterbug using the I/A Series Letterbug Configurator.
3. Confirm that the ATS letterbug was set correctly and connect the cables to The Mesh.
4. If this is a redundant pair of ATS modules, plug in the shadow ATS when the primary
is running and checked out.
5. If an ATS is not installed with the latest image, verify the following checksum on the
ATS boot host workstation.
Station File Checksum
ATS /usr/fox/sp/files/OS1A70 59690 1575
6. After you verify the checksum, perform an IMAGE UPDATE as directed in Address
Translation Station User’s Guide (B0700BP).
71
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.
7.5 Postinstallation Procedures

Note that some of the paragraphs in this section apply to every installation, while others only
apply in the case where files are being brought over (migrated) from an existing station.
7.5.1 Backing Up Hard Disks

For P92 workstations, back up the hard disk and create a “restore point” on workstations running
the Windows XP operating system. Creating a restore point allows you to restore your I/A Series
software if it is deleted or accidentally corrupted.
♦ For the hard disk backup procedure, see “Tape Backup and Restore” in System Admin-
istration Guide (Windows XP Operating System) (B0400HE).
♦ For instructions on creating a restore point, refer to the subsection titled “Creating a
Windows XP Professional Restore Point” in the hardware and software specific
instructions shipped with your workstation.
For P91 servers, back up the hard disk. For the hard disk backup procedure, see “Tape Backup
and Restore” in Model P91 System Administration Guide (B0700BX).
7.5.2 Reconciling the Configuration

If not already done, reconcile all workstations in your configuration by following the procedures
in “Documenting Your System” in the chapter titled “Installing I/A Series Software” of the hard-
ware and software specific instructions shipped with your workstation.
Refer to “Reconciling the System Configuration” in System Definition: A Step-by-Step Procedure
(B0193WQ) for a complete description of reconciliation.
72
8. V8.2 Operational
Recommendations
This chapter provides recommendations that you may want to consider relating to V8.2
I/A Series software.
8.1 System Configuration

8.1.1 Blue Screen Resulting from COMM10 Ports Configured
with Printers
The Communication Processor 10 (COMM10) hosted by a Mesh workstation can only be used
as a FoxWatch® terminal on nodebus on which it resides. Configure port 4 of the COMM10 as a
VT100 terminal (TERM); do not configure printers on COMM10 ports 1 through 3.
If you are rehosting a COMM10 from a legacy host, you must perform the following steps:
1. Remove all printers configured on COMM10 ports.
2. Configure the fourth COMM10 port as a VT100 terminal.
3. Add any printers you just removed to another legacy-hosted COMM10, or a legacy
workstation.
4. Day 1 Commit the system to update printer and Device Monitor configurations.
5. Make any adjustments to Group-Devices of databases targeting printers that are elim-
inated or renamed.
Failure to remove the printers configured on the ports of COMM10 stations may result in blue
screens of the Mesh workstations. The workstation recovery requires:
♦ Removing the printers configured on the COMM10 ports using SysDef software
(essentially steps 1 through 5 above).
♦ Performing a Day 0 software installation on the Mesh workstation with the corrected
Commit diskette.
8.2 Software Installation

8.2.1 Communication Loss After Incorrect Day 1 Software
Installation of Replacement ATS
If software is not installed correctly on an ATS running in Extender mode during a Day 1 Com-
mited software installation, a loss of communication can occur after replacing one of the LIs in
the system with an ATS in LI mode. When a Day 1 Commit diskette is created that does not
specify that the workstation and ATS software images must be reinstalled, the Commit diskette
contains incorrect configuration data used by the ATS in Extender mode.
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.
8.2.2 Proper Method to Disable I/A Series Software During a

Day 1
When initiating a Day 1 install at V8.x, do not disable the I/A Series system using the I/A applet
in the Windows Control Panel. Disabling I/A Series software using the applet in the Control
Panel can result in a “blue screen” and constant rebooting of the workstation after performing a
Day 1.
The proper method to disable I/A Series software during a Day 1 install at V8.x is as follows.
While I/A Series software is still running:
1. Insert the V8.x CD-ROM, run the setup.exe.
2. Select Next at Welcome screen.
3. Select the Committed Configuration Files bullet.
4. Select Next.
5. Click Yes when the window appears asking, “Would you like to disable the I/A
Series drivers and services now?”.
6. Click Yes in response to “Do you want to restart now?”.
In the past, recovery from manually disabling I/A Series software during a Day 1 software installa-
tion involved performing a Day 0 software installation on the workstation. It is now possible to
recover from this without performing an I/A Series Day 0 software installation on the station.
If a Day 1 software install is done incorrectly, recover by performing the following steps:
1. Reboot the station, and press F8 while booting to enter Safe Mode.
2. Access the Control Panel.
3. Select the Fox I/A icon (the Foxboro red fox).
4. In the Startup Options for Reboot dialog box, toggle I/A Series Off, then toggle
I/A Series On, then click OK.
5. Reboot the station, and I/A Series software will boot without incident.
8.2.3 Microsoft Security Patches

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. However, it is still recommended that
you install the security patches that were contained on this CD on V8.2 I/A Series worksta-
tions; 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.
This can be accomplished by creating the equivalent of the K0173XY CD-ROM directly at your
site before installing software, and then installing the patches from the newly created CD or USB
memory stick when instructed during I/A Series software installation.
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.
Changing the Netmask on a Nodebus Windows NT Workstation

Perform the following steps to change the netmask on a Nodebus workstation running the
Windows NT operating system:
1. From the Start menu, select Settings > Control Panel.
2. Open the Network control panel.
3. Select the Protocols tab.
4. With TCP/IP Protocol selected, click Properties.
5. From the Adapter pulldown, select the I/A Series network card.
(If you are not sure which card is correct, try them one by one until you find one with
an IP address of the form 151.128.xxx.xxx.)
6. Change the Subnet Mask from 255.255.254.0 to 255.255.0.0.
7. Click OK to exit the Microsoft TCP/IP Properties dialog box.
8. Click Close to exit the Network control panel.
9. When asked if you want to restart your computer now, click No.
10. Reboot the workstation from the Display Manager or FoxView. From the FoxView
main menu bar, select SftMnt > Shutdown/Reboot > Shutdown and Reboot.
Changing the Netmask on a Nodebus Windows XP Workstation

Perform the following steps to change the netmask on a Nodebus workstation running the
Windows XP operating system:
1. From the Start menu, select Settings > Control Panel.
2. Open the Network Connections control panel.
3. Right-click the I/A Series Local Area Connection and select Properties.
(If you are not sure which connection is correct, try them one by one until you find
one with the Foxboro Protocol checked.)
4. Double-click Internet Protocol (TCP/IP) from the list of items.
5. Change the Subnet mask from 255.255.224.0 to 255.255.0.0.
6. Click OK to exit the Internet Protocol (TCP/IP) Properties dialog box.
7. Click OK to exit the Local Area Connection Properties dialog box.
8. Exit the Network Connections control panel.
75
8.3.2 Java Support

The Windows XP Professional operating system, which runs on P92 I/A Series workstations, has
no built-in embedded support for Java™. This is due to a legal settlement between Microsoft and
Sun Microsystems®, which precludes Microsoft from shipping Java.
Applications requiring Java support will not run on Windows XP workstations as shipped from
the Invensys factory. If you require Java support, install a Java run-time environment.
8.3.3 CPU Usage When Removing a Flash Drive

After using a USB flash drive to transfer or back up files, do not right-click on the system tray
icon and click Safely Remove Hardware. Doing so causes the CPU usage to continuously operate
between 50 and 100%, which causes an extreme slowdown of the I/A Series workstation and
causes freezing of data points for up to 12 seconds.
If you are using a USB flash drive, left-click the system tray icon and left-click Safely Remove
Hardware from the pop-up box. Removing the hardware in this matter causes the CPU usage to
remain in the normal range.
8.3.4 Resolution and Color Settings of Multi-Headed

Workstation Displays
When configuring a multi-headed workstation, always configure the primary screen’s resolution
and color quality settings equal to or greater than the secondary screen’s resolution and color qual-
ity settings. These settings are configurable in the Settings tab of the Display Properties window.
Configuring the primary screen with a lower resolution or a lower color quality setting than the
secondary screen causes the following error message to appear on bootup of the workstation:
Your Xconfig Screen Definition settings are incompatible with your current
Display settings.
For example, the message will appear if:
♦ The primary screen is set to “Medium (16 bit)” and the secondary screen is set to
“Highest (32 bit)”.
♦ The primary screen is set to “1024 by 768 pixels” and the secondary screen is set to
“1280 by 1024 pixels”.
8.3.5 Installing Drivers for Parallel Printers Attached to

Model P92 Workstations
You can configure your Model P92 workstations to have parallel printers attached to them using
the System Definition (SysDef ) utility. In this utility, names are also assigned to the printers, such
as LP01, LP02, and so forth. This information is placed on the Commit disk. When you perform
an I/A Series Software Install, the software installation process reads the Commit disk and installs
a printer driver for each printer that has an associated assigned name.
The printer driver installed during software installation is a generic driver, and may not be the
optimum driver for the specific parallel printer that is attached to your workstation. To determine
which printer driver is installed, invoke the “Printers” information window (click Start >
Settings > Printer and Faxes).
This window lists each printer that is configured. If the description in the “Model” column does
not match the printer that is actually attached to the Model P92 workstation, you must delete the
76
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.
8.4 Windows XP Service Pack 2

8.4.1 Disabling Firewalls for Mesh Network Connections
Windows XP Service Pack 2 turns on the Network Interface Card (NIC) firewalls by default. If
you are adding NICs to an imaged I/A Series workstation, or if you are applying Windows XP
Service Pack 2, you must turn off the firewalling on The Mesh network connections.
After adding NICs or applying Windows XP SP2, turn off firewalling by performing the follow-
ing steps:
1. Click Start > Settings > Network Connections.
2. Note the “Local Area Connection” numbers for each I/A Series NIC and for the Fox-
Int NDIS Intermediate Miniport Driver. The connection number associated with the
NIC or intermediate driver 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 Con-
nection 2” and the intermediate driver listed as “Local Area Connection 4”. Note
these associations.
3. Right-click the first NIC for I/A Series and select Properties in the dialog box.
4. Click the Advanced tab, and click Settings in the Windows Firewall section of the
NIC’s Properties dialog box. The “Windows Firewall” window opens.
5. Click the Advanced tab, and deselect the boxes for each I/A Series NIC based on the
NIC numbers noted in Step 2 above.
77
6. Click OK, OK, and close the “Network Connections” window.

This disables the firewall for I/A Series NICs, but leaves the Windows firewall enabled for the sec-
ondary network for security.
8.5 MKS Toolkit Commands

8.5.1 The compress and mkszip Command-Line Utilities
The “compress” command is no longer supported by the new MKS Toolkit. MKS recommends
using the replacement command “mkszip”.
For the purposes of backward compatibility with existing end-user scripts, the compress com-
mand from the older MKS Toolkit is being shipped on the I/A Series Day 0 CD. This old version
may become non-functional with future MKS releases, so it is recommended that existing scripts
using the old compress command be converted to use the new mkszip command instead. All new
scripts that need compression functionality should use the new mkszip command.
Note that the “uncompress” command will expand compressed data written by either the old
compress command or the new mkszip command.
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.
The following subsections describe the mkszip command.
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
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
♦
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.
8.6 Time Considerations

8.6.1 Windows Time Service and Network Time Protocol
Conflicts
The Windows Date/Time applet contains three tabs. The Date & Time tab allows you to change
the current time and date. The Time Zone tab allows you to establish local time by setting a time
zone. The Internet Time tab triggers time synchronization.
If you select the Internet Time tab and exit via the OK button (as opposed to the Cancel button),
the Windows Time service resets to Automatic Start (from Disabled), which means that the
Windows Time service will automatically start when you reboot the workstation. The Windows
Time service should always be set to Disabled; otherwise, the workstation’s time settings may fluc-
tuate unpredictably. This problem occurs because there are conflicts between the Windows Time
Service and the Network Time Protocol Daemon used by V8.x time synchronization software.
To avoid this problem, exit the Internet Time tab by clicking the Cancel button or simply closing
the applet.
8.6.2 Setting the Time on Nodebus Systems

Do not set the time from SMDH running on a workstation on the Nodebus; The Mesh ignores
the changes and overrides them on the Nodebus side. Refer to the section below for additional
information. For procedures on setting the time on a V8.2 workstation, refer to “Setting Date and
Time” on page 67.
8.6.3 Time Inconsistencies and FoxView Lock-Ups on Nodebus

Workstations
When upgrading a system to V8.1 or later software that will have the Mesh network connected
via an ATS to a Nodebus network, you must be careful that the Nodebus stations are not
adversely affected by the Master Timekeeper (MTK) on a Mesh workstation. The MTK will auto-
matically run on a V8.x workstation and disable any potential Nodebus MTK.
V8.0B MTK software will incorrectly send UTC time to Nodebus stations instead of the desired
local time as is sent by V8.1 or later MTK software. All V8.0B workstations must be upgraded
with the V8.1 Master Timekeeper software (refer to Section 7.4.1.1) before connecting the V8.0B
workstation to a Mesh network that is connected to the Nodebus network via an ATS. Sending
UTC time results in system time moving forward/backward should the MTK move from V8.0B
to V8.1 or later and vice versa. On a Solaris-based system, these incorrect time changes will cause
FoxView software to lock up and the I/A Series Batch Reporter to fail.
80
8.6.4 Daylight Saving Time (DST) Control

I/A Series product releases (V8.1 and later) support the use of Address Translation Stations (ATSs)
that connect The Mesh control network to Nodebus networks. The Master Timekeeper (MTK)
resides on The Mesh and provides time updates to all stations on the Mesh and Nodebus net-
works. DST time adjustments (Standard Time to Daylight Savings Time and vice versa) are auto-
matically sent to all stations on The Mesh.
Options are provided that allow an operator to determine when DST time adjustments are sent to
Nodebus stations. The operator can choose to have DST time adjustments sent automatically or
manually based on operator SMDH selections. These options ensure backwards compatibility for
I/A Series product releases with Nodebus networks where the operator decided when to manually
change time via SMDH for DST adjustments. This feature provided protection for applications
(for example, Batch) where changing time backwards (from Daylight Savings Time to Standard
Time) could cause problems.
The following two attributes control sending DST time adjustments to Nodebus stations:
♦ DST Mode (MANUAL/AUTO)
♦ Nodebus Time Mode (STANDARD/DAYLIGHT)
MANUAL: Manual is a DST mode that requires manual operator intervention for Node-
bus stations to change from Standard Time to Daylight Savings Time and vice versa. Time
changes from Standard Time to Daylight Savings Time in the spring and reverts back to
Standard Time in the fall.
AUTO: Auto is a DST mode that will cause Nodebus stations to automatically track time
of Mesh stations when they change from Standard Time to Daylight Savings Time and
vice versa.
STANDARD: Standard Time is the time in any of 24 time zones, usually the mean solar
time at the central meridian of each zone.
DAYLIGHT: Daylight Savings Time is the time during which clocks are set one hour or
more ahead of Standard Time to provide more daylight at the end of the working day dur-
ing spring, summer, and early fall.
If DST mode is MANUAL (default value), time sent to the Nodebus stations is based on Node-
bus Time Mode (default value is STANDARD) regardless if The Mesh is in STANDARD or
DAYLIGHT time mode. The only way to change the Nodebus station times from Standard Time
to Daylight Savings Time or vice versa is for the operator to manually change the Nodebus Time
Mode via SMDH. If DST mode is AUTO, time sent to the Nodebus stations is the same as the
Mesh time mode (STANDARD or DAYLIGHT). The Mesh time mode is controlled by the
Windows operating system and the Windows Time Applet settings.
System Management (SMDH) provides the following DST support:
♦ SMDH allows you to change the DST Mode (MANUAL or AUTO) via the DST
button. Confirmation of the selection appears on the SMDH message line.
♦ SMDH allows you to change the Nodebus Time Mode (STANDARD or DAY-
LIGHT) via the DST button. Confirmation of the selection appears on the SMDH
message line.
♦ You can make changes before or after actual DST changes occur on The Mesh.
♦ The DST button is always selectable unless there is no ATS configured.
81
♦ 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
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.7 System Monitor

8.7.1 System Monitor Messages Reporting Unavailable
Workstations
On a heavily loaded system, System Monitor messages are issued indicating that UNIX worksta-
tions on the Nodebus alternate between being available and unavailable. This issue is a result of
performance limitations of older UNIX workstations.
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
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 Alarm Management Subsystem

8.9.1 FoxPanels Configurator Requirements
FoxPanels Configurator requires that either FoxAPI or AIM*API software be installed and cor-
rectly configured on at least one workstation in the I/A Series system. It does not require FoxAPI
or AIM*API software to be installed on the workstation from where FoxPanels Configurator is
launched.
If FoxAPI or AIM*API software is not installed somewhere in the I/A Series system, launching the
FoxPanels Configurator returns the following warning message:
“A CSA interface error has occurred.”: Error # 1944774008 from the API could
not be translated.
8.9.2 Clearing Alarms from Alarm Displays

A maximum of 1,000 alarms can be cleared from an AM display at a time. If more than 1,000
alarms are selected, a warning dialog will popup indicating that only the first 1,000 selected
alarms will be cleared.
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
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.
8.9.3.1 Configuring Alarm Management Options for V8.x Systems Using

ADMC
Alarm management options such as RTN_DROP, which removes alarms that have returned-to-
normal from the alarm database, are now configurable in ADMC. For details on configuring these
options in ADMC refer to Alarm and Display Manager Configurator (ADMC) (B0700AM).
\usr\fox\customer\alarms\cfg contains two files, wp_am.cfg and am_def.cfg, that define the
default settings for these and other alarm management options.
If you have an existing (pre-V8.0) configuration that you would like to use on V8.0 or later sys-
tems, you will need to copy your am_def.cfg file and any customer AM specific configuration files
(for example, AM0001.cfg) to \usr\fox\customer\alarms\cfg and rename the wp_am.cfg file (to
wp_am.cfg-80, for example). In addition, you will need to copy your init.user file to
\usr\fox\wp\data. (To use init.user, you must delete the wp_am.cfg file.) The alarm management
software then reads your custom configuration files and fills in defaults for new options. Any
options previously set in init.user are again read from that file.
Note, this applies to the following alarm options:
ALMCLR ACKCLR RTNCLR RTN_DROP
SORT_CFG CLR_OPT MAX_ACTIONS MAX_CAD
HORN_OPT ACK_HORN RESOUND ALMPRI
ALMRTNS CONF_RTN LIA_OLDEST
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
8.9.4 Previously Deleted Alarm Manager Configuration Files

Previously deleted Alarm Manager configuration files are still shown in the Install Files Distribu-
tion dialog box. Create Install Files does not remove the old .cfg files, and Install Files Distribu-
tion distributes all .cfg files existing for a configuration in the file system. Old .cfg files should be
removed manually after the corresponding AMs have been deleted in the database.
8.9.5 Canceling “Accessing Historian” Dialog Box

Currently there is a lag time after you select Cancel on the “Accessing Historian” dialog box and
when the operation canceled dialog box displays. You must wait for the second dialog box to dis-
play before proceeding.
8.9.6 Alarm History Display and AIM*AT Software Restrictions

1. Reading the alarm messages from the AIM*Historian database can take several min-
utes. Please be patient. The message This Display is busy... will appear when you
recall or refresh the Alarm History Display (AHD) while it is updating.
2. If the number of alarm messages in the AIM*Historian database gets too large, you are
not able to view them on the AHD. The following message appears:
Too many historian alarms in database <histname> on <wsname>.
Please archive your database
The AIM*API calls may timeout if there are too many alarms and return an error with
no data to the AM. The AM displays the above message instructing you to archive.
It is difficult to determine how many alarms are “too many” since it is timing based.
The call may timeout on different numbers of alarms depending on what else is hap-
pening on the system. A couple of things that will allow you to have more alarms are:
♦ When you configure the AIM*Historian for alarm messages, only configure it
for “alarmmesg”. Do not include the specific types, such as “hiabsmesg”.
Including both means each alarm message is actually stored twice in the data-
base. The AMS only reads the “alarmmesg” type.
♦ Dedicate a historian to collecting alarm messages, if possible. AIM*Historian
stores all messages in the same files so the API call may timeout sooner if it
must skip over messages that are not alarm messages. At the very least, do not
store multiple types of messages (that is, alarm, system monitor, and so forth)
in the same historian.
Refer to AIM*Historian User’s Guide (B0193YL) for more information on how to archive your
database.
8.9.7 Device Monitor Causing Process Alarms to Stop Updating

(CAR #1006913)
On some workstations, process alarms will occasionally stop updating. This issue is not tied to
system boot and does not occur on every workstation; however, when it does occur on a worksta-
tion, it usually happens every time the workstation is rebooted. This problem occurs because the
Device Monitor marks the station as “failed”, and as a result, alarm messages are not sent to the
workstation.
86
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 Historian Software

This section presents observations and recommendations for Historian software users, and
describes the idiosyncrasies of AIM*Historian software, FoxHist software, and Historian software
relative to the use of the ATS module.
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
8.10.2 Historian Configuration

There are 3 historian configuration attributes that are important for proper collection and
retrieval of timestamps: IATIME (I/A Series time), TZ (time zone), and DST (daylight savings time).
IATIME IATIME is a historian instance attribute. It determines the format in

which the timestamps will be stored in the historian. Setting IATIME to
yes (or 1) causes the timestamp to be stored in IATIME in the historian.
Setting IATIME to no (or 0) causes the timestamp to be stored in UTC
format in the historian.
It is recommended that you configure this parameter to match the system
time domain on the station on which the historian resides.
♦ For AIM*Historian software on the V6.x/V7.x side, configure this
attribute as IATIME=yes.
♦ For AIM*Historian software on The Mesh, or for off-platform his-
torians, configure IATIME=no.
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.
Historian Time Configuration Notes

♦ The TZ and DST attributes are only used by the Historian collector and only when a
time conversion is necessary for the timestamps. A time conversion is necessary when
the timekeeping format on the local station is different from the timekeeping format
configured in the Historian instance by the parameter IATIME. For example, if the
station is keeping time in IATIME, but the IATIME parameter in the Historian
instance is set to ‘no’ (or 0), then the collector must convert the station time from
IATIME to UTC time. In order to make the proper conversion, the TZ and DST
time offsets must be included in the calculation. This time conversion for the times-
tamps is done automatically by the Historian when data values are being written to
88
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.
8.10.3 Data Collection Across ATS Boundaries

An AIM*Historian or even a legacy historian should not encounter any problems collecting data
that originated in control stations on the other side of the ATS. In both cases, the data is collected
with the correct timestamp.
8.10.4 Historian Naming

While there is a statement in the AIM* documentation that it is permissible to have two
AIM*Historian instances with the same name on the same I/A Series node. This is not recom-
mended for a production system, in particular, for a production system with a mixture of legacy
and AIM*Historian instances.
Two historians with the same name can never coexist on the same station. Two historians with
the same name can coexist on two different stations on the same node and collect data without
problem, but only one set of trend servers can be active at any particular point of time. Switching
from one set of trend servers to the other requires an operator intervention consisting of multiple
steps1 to be executed on both historian host stations. It has been observed that the switch-over
may not be reliable when legacy historians are involved. In addition, it is not trivial for the opera-
tor to find out which set of trend servers is currently active, so it would be difficult for him to
know from where the trend data is coming. For these reasons, it is strongly discouraged to have
multiple historian instances with the same name.
8.10.5 Historians Running on the Same Station

Multiple AIM*Historian instances can run with full functionality on the same station. The AIM*
trend servers are designed to service all instances on the same station.
However, running a legacy historian and an AIM*Historian instance together on the same station
causes similar problems as having two historians with the same name (see “Historian Naming”
above).
8.10.6 Porting the Configuration and Data from Legacy

Historian to AIM*AT Software
There is an AIM*AT tool called “leg2fh” that allows you to clone the configuration of a legacy
historian and import it to AIM*AT software. You can run the leg2fh utility while the legacy histo-
rian is still active, and the utility copies the contents of the configuration into an “.inp” file for use
by histbatch. You can edit the .inp file by hand, for example, if you need to change the AIM*His-
torian instance name.
1.
Refer to “Starting and Stopping AIM* Trend Servers” on page 90.
89
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.
8.10.7 Changing Points on a FoxView Trend Display to a New

Historian Name
Refer to FoxView Software (B0700BD) to find out what you need to do if the source of trend dis-
play data must be changed from one historian to another.
8.10.8 Starting and Stopping AIM* Trend Servers

To start and stop the AIM* trend servers, perform the following:
♦ To start the AIM* trend servers, open a DOS window in /opt/aim/bin and run
start_server FH.
♦ To stop the AIM* trend servers, run start_server STOP.
To stop and start the legacy historian and its trend servers, perform the following:
♦ To stop the legacy historian and its trend servers, open a DOS window in
/opt/fox/hstorian/bin and run histonoff OFF.
♦ To start the legacy historian and its trend servers, run histonoff ON.
If you want to keep the legacy historian running but stop only the legacy trend servers, first, copy
the AIM*AT “start_server” script to the legacy system. (Make sure you copy the correct version of
the start_server script for the platform!)
In this case, to stop the legacy trend servers:
♦ Run start_server STOP.
To restart the legacy trend servers:
♦ Run start_server IA.
When the servers are shut down gracefully with the above procedures, it should not be necessary
to use omdel to remove the servers’ process aliases. (During testing, “kill” was used to stop the
servers, which prevented the automatic deletion of the OM aliases, and omdel had to be used to
remove them.)
To find out if an active set of trend servers is running anywhere, run:
glof -p <processname>
The trend servers register with the Object Manager (OM) under several process names, consisting
of the historian name plus a suffix. With a historian name of “hist01”, the OM process names are
as follows:
♦ hsfetch: hist01sf
♦ hrfetch: hist01rk and hist01rf
♦ histsrv: hist01he
♦ ipchisti: hist01mv and hist01 (no suffix)
For example, to find out if there is an “hsfetch” process running that serves the historian
“ben007”, run:
cd /opt/fox/bin/tools
90
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.11 Integrated Control Configurator (ICC)

8.11.1 FixAll Errors for Several FBMs
Performing a FixAll from the ICC does not work (generates errors) for the following FBMs:
♦ FOUNDATION fieldbus FBMs: FBM220, 221, and 228
♦ FoxCom FBMs: FBM243 and 246
♦ HART FBMs: FBM214, 215, 216, and 218
♦ PROFIBUS-DP™ FBM: FBM223
♦ Field Device System Integrator (FDSI) FBMs: FBM230, 231, 232, and 233.
♦ All FBMs attached to an FCM.
You must create these devices manually in the ICC.
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.
8.13 Control Software

8.13.1 Time-Stamping and Reprioritizing Alarms
Changes have been made to the re-alarming behavior of CP270 controllers running V2.5 and
later image versions. This section describes changes relating to alarm time-stamping and how re-
alarming functions when a block has two or more alarm priority types enabled, and an alarm pri-
ority is lowered.
For more information on I/A Series control blocks and alarming, refer to:
♦ Integrated Control Block Descriptions (B0193AX)
91
♦ Control Processor 270 (CP270) Integrated Control Software Concepts (B0700AG).
8.13.2 Re-Alarming Change in FCP270 and ZCP270 Versions 2.5

and Later
With the earlier FCP270 and ZCP270 Version 2.2 control images released with V8.0 Revision B
software, any change in alarm priority (higher to lower or lower to higher, where 1 is the highest
priority) caused the controller to send a re-alarm message and set the alarm acknowledgement sta-
tus to the Unacknowledged state. That is, the block parameter UNACK was set to 1 when the pri-
ority of an alarm was lowered.
By contrast, the later FCP270 and ZCP270 Version 2.5 control images, originally released with
Quick Fix 1007242 and Quick Fix 1007241 respectively, preserve the alarm acknowledgement
status for alarms that are changed from a higher to a lower priority. Controller software does not
automatically re-alarm to the Unacknowledged state (UNACK=1) when you lower the priority of
an alarm.
For example, if an alarm has been generated and acknowledged, lowering its priority does not set
the block alarm state to Unacknowledged. Alternately, if the same block alarm was generated and
acknowledged, raising its priority will set the block alarm state to Unacknowledged.
8.13.3 Re-Alarming for Multiple Alarm Priority Types

If more than one alarm priority type is enabled for a single block, there are cases where an
acknowledged alarm can require an additional operator acknowledgement if an alarm priority is
lowered. This behavior occurs because a block has only one boolean acknowledgement status
parameter but can have multiple alarms with different priorities.
AIN Block Example

For example, take a situation where an AIN block has multiple active acknowledged alarms
(UNACK=0). Raising one alarm’s priority causes the block to go to the Unacknowledged state
(UNACK=1) as expected. Then, if you lower the priority of another alarm from the same block,
the Unacknowledged state of the block that existed before alarm reprioritization is preserved,
UNACK=1. Therefore changing the priority of the second alarm in this case has no effect on the
block alarm state; the block remains in the Unacknowledged state and an operator acknowledge-
ment is required. The event history follows:
1. The AIN block has the following alarms tripped:
♦ High Absolute Alarm Indicator (HAI)
♦ High-High Absolute Alarm Indicator (HHAIND)
♦ High Out-of-Range Alarm (HOR)
♦ Bad input (BAD).
2. Alarms are acknowledged.
3. Out-of-Range alarm priority (ORAP) is raised from 3 to 2. This action causes the
block alarm state to be set to Unacknowledged.
4. High/Low alarm priority (HLPR) is lowered from 2 to 3. This action has no effect on
the block alarm state, which remains Unacknowledged.
When ORAP was raised, the Unacknowledged state was set. Lowering HLPR does not change the
Unacknowledged state of the block, which will be preserved.
92
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.
8.13.4 Time Stamping of Re-Alarmed Messages

The original timestamp of the alarm occurrence is used in all re-alarmed messages sent in reply to
a Current State Update (CSU) request. In addition, there is a new option defined in the Station
block (CFGOPT Bit 6 (0x40)). If set, this option specifies that re-alarmed messages contain the
original timestamp when:
♦ An alarm priority is changed. In this case, re-alarming is done only if the Station
Block CFGOPT bit 3 (0x08) is also set.
♦ A re-alarm timer (AMRTIN) expires.
In all other cases, re-alarmed messages contain new timestamps.
8.13.5 Migrating a Control Database to an FCP270 or ZCP270

You can migrate a SaveAll database from a CP60 to an FCP270 or ZCP270 provided that the
database is configured correctly. Database validation logic in the FCP/ZCP270 has been
improved since the CP60, and databases containing configuration errors that are undetected by a
CP60 will not load correctly into an FCP270/ZCP270. Before performing the SaveAll and load-
ing the database for use with an FCP/ZCP270, you must correct these configuration errors to
guarantee proper system performance.
First, check the periods and phases of all ECB200/ECB202 blocks and their associated DCI
blocks to make sure there are no phasing discrepancies. DCI block execution frequency cannot be
faster than its associated parent ECB200/ECB202 execution frequency. The period/phase of the
associated child ECB201 is irrelevant to the DCI block execution. DCI blocks must be config-
ured to run on a multiple of both the ECB200/ECB202 phase and the phase of the compound
containing the DCI block. For example, an invalid configuration can include a DCI block config-
ured for 0.5 second execution, but the block’s parent ECB200/ECB202 is configured for 1 second
execution. This invalid configuration error goes undetected in the CP60, but will prevent the
database from being loaded on an FCP/ZCP270. Prior to Version 8.0 the complete set of DCI
blocks is as follows: BIN, BINR, BOUT, IIN, IOUT, PAKIN, PAKOUT, PLSOUT, RIN, RINR,
ROUT, STRIN, and STROUT.
Second, if you are migrating a control database from a Nodebus CP to an FCP270 or ZCP270,
please note that databases containing the MVC (Multivariable Controller Block) and MVL (Mul-
tivariable Loop Block) blocks will not load into an FCP270 or ZCP270 controller.
8.13.6 Changing Block Modes on DO or AO Blocks

When changing block modes on a DO (digital output) or AO (analog output) block and while
the output value is simultaneously changing, the detail display may display a CFG error indication,
including the text message “W73-FF Function Block Configuration Error”. This occurs
because there is a “race” condition between the mode change and the output data change. The
message clears when the mode is changed again. The block operates normally.
To avoid this situation, when changing modes, wait for the transition to the new mode before
changing the output value.
93
8.13.7 VAL_ID Character Limit

The VAL_ID field is limited to 22 characters, which might be too short for some interfaces.
The VAL_ID field of the DI blocks holds the label of the data item being retrieved. For some
interfaces, such as Data for Windows through the DDE Gate, the item label can be quite long.
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.
8.14.2 Installing or Replacing CP270 and FCM100Et Modules in

a Running I/A Series V8.x System
To install a “new” or “replacement” module in a running system, care should be taken to avoid the
use of duplicate letterbugs, IP addresses, and/or MAC addresses. To ensure that there are no
duplicates, you should clear the newly added station’s NVRAM before adding the module. Per-
form the following steps:
1. Power up the station without any cables.
2. Set the letterbug to “NOSUCH” with the PDA. Refer to Letterbug Configurator
(B0700AY) for procedures on setting letterbugs.
3. After the station’s NVRAM is cleared, read the station’s status with the PDA. If prop-
erly flushed, the PDA will read the “NOSUCH” letterbug and an IP address of
255.255.255.255.
Once the station is flushed, you can then add the station to the system.
To add a module to a fault-tolerant pair:
1. Connect the cables to the station.
2. Insert the module with its partner. The shadow station boots up and copies the perti-
nent information it needs from the primary module.
3. The two modules will then marry and begin running as a pair.
To add a single CP:
1. Power up the module without any cables and set the system letterbug.
2. Remove the module from the system, attach the cables, and replace the module in the
system. The module will reboot two times to collect the NVRAM information from
the host, and will then become an active station.
94
8.15 Address Translation Station (ATS)

8.15.1 Communicating Directly to an ATS
If you want to communicate directly with an ATS in LI mode, don’t use a workstation on a node
with an LI. Communicate to the ATS from a workstation on The Mesh or from a node with
another ATS in LI mode.
Direct communication to ATSs include:
♦ Reading ATS OM variables, as described in the Address Translation Station User’s
Guide (B0700BP).
♦ Performing Nodebus Test Initiator actions, such as running a cable test. These actions
are sent to the Current Test Initiator, which by default is the ATS.
♦ Getting SGL cable indications. SMDH gets these indications from the Current Test
Initiator of each node, which by default is its ATS.
The restriction is a result of the address translation functions that the ATS performs. As packets
are forwarded through the ATS in Extender mode, it translates the source Node ID so the packet
looks as if it originated on the bridging node. ATSs in LI mode use the LI MAC address 00-00-
6c-c0-01-ff, so the translated packets appear to have originated from the LI of the bridging node.
Consequently, stations on nodes with LIs end up directing communications for ATSs in LI mode
to the LI on the bridging node instead.
Stations on The Mesh and stations on nodes with ATSs in LI mode do not exhibit these symp-
toms because these stations see the actual Node IDs, as opposed to the translated IDs.
8.16 Fieldbus Modules (FBMs) and Field

Communication Modules (FCMs)
8.16.1 Performing General Downloads
When performing a general download after a LoadAll, you must pick the GENERAL DOWN-
LOAD key twice. The first pick downloads all the FCMs and the second downloads all the FBMs.
8.16.2 Verifying EEPROM Level of 200 Series FBMs in SMDH

When doing an EEPROM update of an I/A Series 200 Series FBM, using the Equipment Change
action through SMDH, the “EEPROM UPDATE SUCCESS” and “EEPROM UPDATE FAIL-
URE” messages that appear after the action are sometimes incorrect, hence misleading. The event
that results in the display of the message does not originate within the FBMs, which is the only
place success or failure is known; that is, what is being reported is not based on information from
the FBM.
Given that the reporting of the success or failure of the update is not consistently correct, you
should look at the Equipment Information display for the FBM (EEPROM REV) after the
update process has completed to confirm that the new version is in use.
95
8.16.3 EEPROM Updating FBM201, 207, and 217

When you EEPROM update your FBM201, FBM207, or FBM217 from version 1.12 through
1.15F to the newest version, the FBM red and green LEDs may go out and stay out, and the FBM
appears to be dead even though the EEPROM update has completed successfully.
To recover from this situation, cycle the power to the FBM by removing it and reinstalling it in
the baseplate. After that, further EEPROM updates work correctly as long as the firmware version
doing the burn is 1.15G and later, or 1.11 and earlier.
For the latest EEPROM revision levels, refer to Appendix B “EEPROM Revision Levels”.
8.16.4 Misleading System Monitor Messages After EEPROM

Updates of FBM216/218
System Monitor reports misleading error messages during the EEPROM update process on a
redundant FBM216 or FBM218. These messages report that the FBM being updated has failed,
PIO Bus Access errors and Recovery are occurring, and once the FBM EEPROM update has fin-
ished, the FBM is no longer failed. These messages are erroneous and do not affect the operational
health of either FBM and can be ignored.
8.16.5 EEPROM Updating FDSI FBMs (FBM230 to FBM233)

After performing a Day 0 I/A Series software installation, you must EEPROM update the FDSI
FBMs (FBM230 to FBM233). After performing the EEPROM update, restart the FBM and con-
firm that the FBM has the correct EEPROM revision level for V8.2. For the latest EEPROM revi-
sion levels, refer to Appendix B “EEPROM Revision Levels”.
When EEPROM updating these FBMs, you may encounter problems getting the FBMs to go on-
line. In extreme cases of difficulties making the FBM operational after the update, it may be nec-
essary to do a delete/undelete of the ECB for the FBM, or even to reboot the controller that is
hosting the FBM.
8.16.6 Ethernet Switches Causing FCM Failure and Recovery

Messages
During power cycling of Ethernet switches in the I/A Series Mesh network, FCM100 bus failures
may be reported followed almost immediately by an FCM bus recovery message. These FCM bus
failure messages are caused by a transient condition in the FCM module that can occur, depend-
ing on network topology, when the network spans due to a switch failure or network failure. Dur-
ing network spanning, the FCMs in the system may experience an intermittent loss of
communications. In this scenario, the loss of communications is brief, typically less than one
BPC, and it does not interrupt control. Observing a control trend during the time of the FCM
bus failure messages will confirm that there is no loss of control.
8.16.7 Network Spanning Causing Failure and OOS Indications

in SMDH
If the network spans, I/O communication could be lost for enough time such that FBMs and
FCMs temporarily appear failed and I/O devices may appear out-of-service (OOS) in SMDH.
96
8.16.8 Letterbug Naming Restriction for FCMs

When selecting the letterbug of an FCM, make sure the first four characters of the FCM’s letter-
bug do not match the first four characters of the letterbug of any existing control processor.
8.17 Tools and Utilities

8.17.1 Live List Tool Posts Error on Launch
The Live List Tool (LLT) “remembers” the CP and FBM letterbug from any previous invocation
of itself. If the CP or FBM is not available (off-line, failed, or deleted), then the LLT will post an
error upon startup as it times out trying to locate the now non-existent CP or FBM. In such a
case, simply enter a correct CP and FBM letterbug after the timeout period, and the LLT will
then work properly. This condition would typically only occur during some sort of checkout situ-
ation prior to normal plant operations.
8.17.2 FDA Driver Task

Both FoxCAE software and the Live List Tool (LLT) use a low-level utility task called the FDA
Driver Task (FDA DT) to communicate from the workstation through the control processor (CP)
to DC™ fieldbus H1 field devices. The FDA DT is a relatively low priority task for the control
processor and the FBM228. Therefore, when the CP and FBM228 are heavily loaded (for exam-
ple executing configuration changes) or when concurrent FDA DTs are being executed by Fox-
CAE or by the LLT, timeouts and retries may take place. Occasionally this may result in a dialog
box appearing on the workstation stating that a timeout has occurred. In those cases, retry the
same operation. The operation is likely to run to completion when re-tried.
This is considered to be normal behavior and is dependent upon CP load, FBM load, and the
number of concurrent FDA Driver Task users (via FoxCAE or the LLT).
97
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.
9.1.2 Using telnet and ftp Utilities on a Windows XP

Workstation
If you want to use the telnet or ftp utilities, be aware that there are two versions of each utility
available on the P92 workstation. One version is better when used between Windows XP stations,
while the other version is better when a non-Windows XP workstation is involved. For details on
using the different versions of these utilities, refer to System Administration Guide (Windows XP
Operating System) (B0400HE).
9.1.3 Serial Expansion Card Cable-to-Port Mapping

The Model P92 Workstation has two built-in serial ports (that is, COM1 and COM2). The serial
expansion card adds four additional serial ports to the workstation (that is, COM3, COM4,
COM5, and COM6) without affecting COM1 and COM2. The splitter cable that attaches to
the serial expansion card has four connectors labeled P1, P2, P3 and P4, which correspond to
COM3, COM4, COM5, and COM6, respectively.
9.2 Software Installation

9.2.1 Selecting NICs During V8.2 I/A Series Software
Installation
During I/A Series software installation, you are prompted to select the two Network Interface
Cards you will be using for the I/A Series control network. After selecting the two cards and click-
ing Next, an I/A Series Network Installation dialog box appears indicating that the system is
reconfiguring network components. When this dialog box appears, wait about 10 seconds before
clicking OK. Otherwise, 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.
99
B0700RN – Rev C 9. V8.2 User Notes
Figure 9-1. I/A Series Network Installation Dialog Box
9.2.2 Relocating CSA

When the System Definition is modified such that CSA is moved to a different host, you must
perform the procedures below. There are two separate procedures: one for Windows platforms
and one for UNIX platforms.
CSA_Stop fails with errors on a Windows NT or a Windows XP platform that resides on the
Nodebus. In order to stop CSA on a Windows platform, perform the following steps:
1. Perform the CSA_Save operation (refer to “Backing Up and Restoring Compound
Summary Access (CSA)” on page 139).
2. Type the following in a command tool window from the workstation that previously
hosted CSA:
a. Type d: and press Enter.
b. Type ncenv and press Enter.
c. Type sh and press Enter.
3. Change directories by typing:
cd D:/usr/fox/bin
4. Use an editor such as vi or Wordpad to open the file fox_apps.dat.
5. Delete the record “ACSA”.
6. Save the file and exit the editor.
7. Reboot the workstation.
When the System Definition is modified such that CSA is moved to a different host, proceed as
follows on a UNIX workstation:
1. Perform the CSA_Save operation (refer to “Backing Up and Restoring Compound
Summary Access (CSA)” on page 139).
2. On the workstation that previously hosted CSA, open a VT100 window.
3. Change directories by typing:
cd /usr/fox/bin
4. Use an editor such as vi to open the file fox_apps.dat.
5. Delete the record “ACSA”.
6. Save the file and exit the editor.
7. Reboot the workstation.
100
9. V8.2 User Notes B0700RN – Rev C
9.2.3 Reinstalling Canceled/Failed Packages
! 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.
9.2.4 Canceling Software Installation Processes

Do not cancel out of any software installation routine such as “Install Selected Packages/Load
Release Level Diskettes” or “Reinstall Canceled/Failed Packages”. Doing so can result in a blue
screen crash of the workstation. When this issue occurs, you must re-ghost the machine and rein-
stall the Day 0 I/A Series software.
9.2.5 Adding a Serial Printer During a Day 1 Install

If you are adding a serial printer to a V8.2 system that did not have a serial printer configured ini-
tially, performing a Day 1 Commited installation does not add the serial printer's driver to the
system. To manually add the printer driver, perform the following steps:
1. Create the directory “D:\usr\fox\system32\fox_drivers\WinXP\free\ntswi”.
2. Copy “D:\usr\fox\sp\IIF.prm” to
“D:\usr\fox\system32\fox_drivers\WinXP\free\ntswi”.
3. Copy “D:\usr\fox\system32\foxser.inf ” to
“D:\usr\fox\system32\fox_drivers\WinXP\free\”.
4. Run “D:\usr\fox\system32\fox_drivers\WinXP\free\foxins.exe”.
9.2.6 System Monitor Tries to Start

After a Day 1 installation on Nodebus workstations, the System Monitor tries to start after the
workstation is rebooted if the System Monitor has been removed from the workstation. When
this occurs, the System Monitor log reports System Monitor () Premature Exit --- Reason
(12). This message can be ignored.
101
9.2.7 Successfully Creating and Appending to a Reconcile

Diskette
A problem occurs if you create a Reconcile diskette on a workstation running a UNIX-based
operating system. After creating the Reconcile diskette on the UNIX-based workstation, you can
successfully append the remaining UNIX platforms and only the first Windows-based platform to
the diskette. Appending subsequent Windows platforms to the Reconcile diskette will fail, citing
an incorrect media type.
If you want to create a Reconcile diskette for a Day 1 installation, first, create the diskette on a
workstation running the Windows operating system. Second, append the remaining Windows-
based platforms, and finally, append the UNIX platforms. Following this procedure will allow you
to successfully create a Reconcile diskette.
9.2.8 White Process Alarm Page after Software Installation

After performing a software installation on a workstation running the Solaris operating system,
the process alarm page is all white.
To workaround this problem, open the /usr/fox/exten/foxboro.local script and find the line that
begins with “am” in the lower portion of the script. Remove the word “-icon” from this line and
reboot the workstation. The process alarm page will appear correctly.
9.2.9 Restoring from Tape Backup

When restoring an I/A Series 8.2 AW from tape while following System Administration Guide
(Windows XP Operating System) (B0400HE), additional steps are required.
Follow the procedure though to the subsection titled “Booting the System With a New Hard
Drive”. Once the Windows XP operating system is restored, install Service Pack 2 software by fol-
lowing Step 2 of section Section 7.4.1.2 in this document. You can then install the recommended
Service Pack 2 Security patches by following Step 4 of Section 7.4.1.2 and Appendix E “Installing
Microsoft Security Patches”. If you plan on restoring the hosts file from the backup tape with the
restore process, you must first rename the empty hosts file that was installed during the Windows
XP operating system restore process to hosts.old. You can find this file in C:\win-
dows\system32\drivers\etc\hosts. Otherwise the empty hosts file will remain and the backed up
host file will not be restored.
9.2.10 Reinstalling the HP 3000 Printer Driver

If maintenance functions such as Day 1 or AIM* software installations that require I/A Series soft-
ware to be “turned off ” via the control panel are performed on a workstation, upon reboot the
workstation will often request the printer driver for the HP 3000 DeskJet® printer to be re-
installed. When this occurs re-install the printer driver.
9.3 System Configuration

9.3.1 Changing Host of Nodebus CP
If the system configuration is modified such that the host of a Nodebus CP is changed from one
workstation to another, the control processor may fail to boot.
102
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.4 Combined Mesh and Nodebus Systems

9.4.1 Data Transfers Between the Nodebus and The Mesh
Networks
V8.2 supports inter-network traffic between The Mesh and Nodebus networks using ATSs. How-
ever, you need to ensure that stations that migrate to The Mesh and continue to communicate
with stations on the Nodebus adhere to their original Nodebus communication limits. When the
Nodebus is involved in the transfer of large amounts of data, the Nodebus rules still apply. Nor-
mally, if the data transfer starts to exceed 1.2 MB, control stations could island and hot remarry.
Copying large streams of data from a Nodebus through an ATS to the Mesh is not recommended.
Avoid using the Nodebus for large data transfers; use a separate network instead.
9.5 System Monitor

9.5.1 System Monitor Behavior after a Power Failure
After a power failure, some of the System Monitors on Nodebus workstations may not restart.
The message System Monitor (LBUG) Premature Exit --- Reason (17) appears on the system
alarm printer. If the System Monitor does not start, reboot the 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.
9.6.2 Availability of Reboot Station and EEPROM Update

Selections from SMDH
Occasionally, the Reboot Station and EEPROM Update selections will not be available from a
Nodebus SMDH even when appropriate privileges are assigned to the host workstation. This
occurs when Equip Chg is selected for a Mesh station, and subsequently Equip Chg is selected for
a Nodebus station. Reboot Station and EEPROM Update will not be immediately accessible for
the Nodebus station. After a few minutes, the picks will return and operate.
9.6.3 Performing Nodebus Cable Tests

If you manually run a cable test on one node, results for cable tests generated on other nodes may
be displayed on the SMDH message line. This may happen when Layer Initiated cable tests are
occurring on other nodes and those results are displayed in the SMDH message line.
103
9.6.4 Excess Collisions Counter in the MAC Sublayer Counters

Display
For I/A Series V8.1.1 and later releases, the EXCESS COLLISIONS counter for the CP270 in
the MAC Sublayer Counters display in SMDH has functionality that did not exist in previous
I/A Series software releases running on The Mesh network. Because collisions cannot occur in
The Mesh network full-duplex domain, this counter is now used to detect the number of times
the low-level Mesh network connectivity test cannot send from the primary to the backup port on
a station. This counter can be used as an indication of intermittent communication through The
Mesh. A number that is constantly increasing (there are 3 tests per second) would indicate a
breakdown between the two ports of a station in The Mesh. A number that is intermittently
increasing could be indicative of excessive spanning by The Mesh network switches or an inter-
mittent (possibly dirty) fiber connection. Prior to V8.1.1, this counter had no function.
9.6.5 Eurotherm Device Status Not Correct in SMDH

Failed Eurotherm devices interfaced through an FBM223 may not show failed status in SMDH
or the System Monitor log after a reboot of a FCP/ZCP. The only indication that the device is
failed is the associated user detail displays are cyan. Disabling/Enabling communication to the
devices causes the correct status to be displayed in SMDH.
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.
9.8 Alarm Management Subsystem

9.8.1 Time/Date Formats in Alarm Messages
Changes have been made to how the Alarm Manager (AM) displays the time and date within
alarm messages on the CAD, NEWALM, UNACK, ACKED, and AHD displays. V8.x releases
prior to Revision B display the time/date as:
mm-dd HH:MM:SS
For example:
11-23 11:42:13
Even if you changed the format via ADMC to another format, the time and date were always dis-
played as shown above.
With V8.0 Revision B and later software, the format is now read from the configuration files, pro-
viding alternate time and date formats for alarm messages. For example the same time/date can
now be displayed as:
23-11 11:42:13
The executables and data files to support this are on the Day 0 CD-ROM. Included are updated
versions of the following data files:
104
♦ 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
9.8.2 Moveable Alarm Manager Displays

The Alarm and Display Manager Configurator (ADMC) contains configurable settings for each
AM window. In ADMC, the Alarm Manger Display Type dialog box contains an option to allow
or disallow a user to resize displays. This selection is enabled by default. Another checkbox needs
to be added to allow or disallow a user to move displays. Currently, this option is not available.
9.9 Integrated Control Configurator (ICC)

9.9.1 Incorrect Parameter Display in ICC
Performing a certain sequence of operations while creating an ECB block in the Integrated Con-
trol Configurator, such as selecting Insert New Block/ECB, utilizing the block copy feature, then
canceling in the middle of the operation and re-entering an ECB Type, will cause the incorrect
block parameter list to be displayed. The compound parameter list will be displayed instead of the
block parameter list.
If this problem occurs, exit the ICC then reinvoke it. The new ICC session will allow you to
interact with the correct block parameter lists unless the above sequence is repeated.
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.
9.11 Object Manager

9.11.1 OM API register_name Function
When created, Application:Object.Atrributes (AOAs) are registered with the Object Manager via
the “register_name” function. This function and its return codes are not documented in Object
Manager Calls (B0193BC).
The OM API “register_name” function can return with a error code of 104. This error code is
non-fatal; try the operation again.
106
9.12 Fieldbus Modules (FBMs) and Field

Communication Modules (FCMs)
9.12.1 Addition of the “NOFAIL” DVOPTS Option for HART
FBMs
In addition to the “4-20” and “HART” options that can be used in the DVOPTS parameter for
the ECB201 corresponding to a HART device, there is now a “NOFAIL” option. When
DVOPTS is set to “NOFAIL”, HART communications are enabled, as with the “HART” option,
but when HART communication failures occur, the device will not be failed and the analog value
will remain in service.
Indications that there has been a HART communications failure include:
1. The device’s icon in SMDH becomes yellow
2. A system alarm is indicated on the second page of the SMDH Equipment Informa-
tion display for the device
3. The last page of the SMDH Equipment Information display indicates a HART com-
munications failure under DEV DIAG STATUS
4. A failure message is sent to the system print device, if there is one. An example of this
message is:
2006-01-01 01:16:22 51CP11 Equip = 511106/1106C3 SYSMON -00133 Warning
Error Condition Exists
When the condition no longer exists, that is, when the HART communications recover, the sys-
tem alarm indication and the HART communication failure indication in the SMDH Equipment
Information Display for the device disappear, and a recovery message is sent to the system print
device, if there is one. An example of this message is:
2006-01-01 01:16:22 51CP11 Equip = 511106/1106C3 SYSMON -00133 Warning Error
Condition No Longer Exists
2004-01-29 11:54:47 CP60BK Process = FCM101 017F -39 1 HART Port 1 OK
9.12.2 Switching FBM214/215 Channel Assignments in

Associated Child ECBs
When trying to exchange channel assignments for ECB201s associated with an FBM214 or 215,
you must perform the control block configuration in such a way to avoid “invalid device connec-
tion” and “duplicate connection” errors which are reported in the ECBs’ Detail displays.
Consider a configuration that has two ECB201s corresponding to Channel 1 (DVNAME=CH1)
and Channel 2 (DVNAME=CH2) of an FBM214 or 215. If you use IACC to change the first
ECB's DVNAME parameter from CH1 to CH2, change the second ECB's DVNAME parameter
from CH2 to CH1, and then download the changes, a “W66 - INVALID DEVICE CONNEC-
TION” error appears followed by a “W66 - DUPLICATE CONNECTION” error. There is no
straightforward way to recover under these circumstances without rebooting the controller or
deleting/undeleting the ECB200 for the FBM.
To switch channel assignments successfully, perform the following:
1. Delete one of the ECB201s corresponding to one channel of the FBM.
107
2. Change the DVNAME of the remaining ECB201.

3. Confirm that the change is operational. (This may require that you delete/undelete
the ECB201 for the change to take effect.)
4. Add the second ECB201 corresponding to the other channel.
9.12.3 Configuring Fail-Safe for Proper Operation of FBM218

Proper operation of the redundant FBM218 requires that the fail-safe parameters in the ECBs
associated with both FBMs (main and backup) be correctly configured. In general, the FBM out-
puts must be configured to fail to zero in order to allow the opposite (non-failed) FBM to assume
(or continue) control without interference from the failed module.
9.12.4 EEPROM Updating FBM220 and 221

Before you perform an EEPROM update on an FBM connected to a FOUNDATION™ fieldbus
positioner, be sure that the ROUT block corresponding to the positioner has recovered from any
previous operation, such as an FBM reboot. If you do not allow the ROUT block to complete its
operation, the positioner may not retain its configured faultstate value.
9.12.5 EEPROM Updating an FCM100Et

The ZCP does not clear FCM errors properly. To clear the ZCP of FCM errors, you must take
both FCM partners off-line at the same time, which can interrupt plant control.
This problem manifests itself when an FCM100Et is EEPROM updated. The ZCP parent and
the FCM have a seven-step handshake process that ultimately loads the new image into the FCM.
If noise garbles the communication while this process is in progress, or if the FCM fails to com-
plete one of the steps successfully, flags in the ZCP are left in such a state where the FCM is
treated as EEPROM updating forever, even though the FCM properly clears itself. In this state,
the ZCP refuses to use that FCM partner for anything, even control.
There are two ways to recover from this problem:
1. Clear the ZCP’s state bits for the FCM100Et by taking both FCM partners off-line
and then putting them back on-line, even the partner that was not being EEPROM
updated. Taking both FCMs of a pair off-line means an interruption of control for all
devices under that FCM pair.
2. Instead of taking both FCM partners off-line, you can also run simplex if this prob-
lem occurs.
If running single or interrupting control cannot be tolerated, do not perform an EEPROM
update until you have the opportunity to recover from the problem should it occur.
9.12.6 Field Device System Integrator (FDSI) Subsystem

9.12.6.1 Common Issue for FDSI Modules
Review the following notes relating to the FDSI drivers.
♦ When reinstalling an FDSI driver, Field Device System Integrators
(FBM230/231/232/233) User’s Guide (B0700AH) instructs you to remove the previ-
ously installed driver by using the Add/Remove programs under the Windows Control
Panel. In some cases, the FDSI driver does not appear in the list of software packages
that can be removed. You can work around this issue by uninstalling the driver from
108
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.
9.12.6.2 OPC Client Driver for FDSI Modules, and Diagnostics

Application for OPC Clients
Review the following notes relating to the FDSI OPC Client driver.
♦ Fail-safe on CP disconnect is now supported PAKOUT blocks.
♦ Mixed or lower case OPC Item tags used to configure heartbeat points are now
supported.
♦ Corrected problem where DCI blocks are sometimes marked as “Invalid” when the
FBM or OPC Server disconnects or reboots.
♦ Corrected problem of OPC driver freezing when Ethernet cable is unplugged.
♦ Changing the Fixed (No Dhcp) IP Address of an FBM232 or 233 may require reboo-
ting the FBM for the change to take effect.
♦ Non-existing or misconfigured OPC Item tags cause a memory leak.
♦ When an FBM is put Offline via SMDH and 10 or more ECB201s are configured,
the FBM may reboot.
Review the following notes relating to the diagnostics utility for OPC clients.
♦ Corrected problem of points and groups not all being displayed on the Diagnostic
view. All points and groups are now shown.
♦ Corrected problem of missing data messages during initial connection and update.
♦ Corrected problem with the Active Item Count. It now displays the correct value.
♦ Improved value status operation and OPC Quality value display on Diagnostic view.
♦ Improved Browser error messaging and Item Properties display.
♦ The number of reads versus the number of writes is not enabled and set to 0.
♦ Improved Browsing operations when connected to an OPC server machine.
9.12.7 Displaying FoxCom Device Information After General

Download
At the startup or initial General Download or Download function used to bring FoxCom FBMs
that support child devices on-line, the SMDH and Detail displays for these devices may omit
some transmitter information. To correct this problem, toggle the FoxCom device off-line then
on-line in the SMDH Equipment Change display, and the transmitter information displays
correctly. Once the FoxCom devices have been toggled off-line and on-line, the problem no
longer exists.
109
9.13 FOUNDATION fieldbus

9.13.1 DD Explorer – Adding Device Descriptor Files
After you have obtained appropriate device descriptor files, you can load them into DD Explorer.
The SYM, FFO, and CFF files must all be located in the same directory.
When you select File > Add Device Description, the resulting Open dialog box contains only a
“*.CFF” selection in the Files of Type field. To verify that the required SYM, FFO, and CFF files
are in the same directory, enter “*.*” in the File name field. All files in the directory are listed, and
you can make sure that all the required files are present and make corrections as necessary before
you receive an error message.
9.14 Control Stations

9.14.1 Shadow ZCP270 Failure after Image Update
If a fault-tolerant ZCP270 has remote I/O configured but not physically connected during an
image update, the shadow ZCP270 module fails red/green after the update. To clear the condi-
tion, manually reboot the ZCP.
9.15 Control Blocks and Parameters

9.15.1 Changing the ECPOPT Parameter in ROUTR, BOUTR,
IOUTR, RINR, or BINR Blocks
When setting the ECBOPT parameter from 0 to 1 or 1 to 0 in the ROUTR, BOUTR, IOUTR,
RINR, or BINR blocks, verify that IOMID1 is set to a valid entry and that IOMID2 and 3 are
blank. Failure to do this could result in a condition where the CP will lose communication with
ICC with a -4 error. This loss of communication will require ICC to be exited without a proper
checkpoint and then require a CP reboot before ICC can access the CP again.
9.15.2 PIDA with MODOPT Set at 7 or 8

The PIDA block with the Mode Option parameter (MODOPT) set to 7 or 8 (dead-time control-
lers) does not work properly if both of the following conditions exist:
♦ The output span is NOT between 0 and 100
♦ FILTER ≠ 0.
The block will work properly if either or both the output span is between 0 and 100 or FILTER =
0.
9.15.3 Using the OSP 0 Instruction in the LOGIC Block

Using the instruction “OSP 0” (one-shot pulse timing function) in the LOGIC block of the
CP60 or the CP270 does not work properly. The block logic incorrectly uses the value specified
in RI01 instead of using a time constant of 0.5 second. If RI01 is unused by the LOGIC block
program, then the timer duration will default to a value of 0, and the expected pulse will not be
generated.
110
9.15.4 PRIBLK and PRITIM Functionality in the IOUT Block

In the IOUT block, the Primary Block (PRIBLK) parameter indicates whether the IOUT block
has a connection from an upstream block (PRIBLK=1) or not (PRIBLK=0). Its value, together
with that of the Primary Cascade Timer (PRITIM), determines whether the IOUT block remains
in Holding until the upstream block returns an Acknowledge, remains in Holding for a fixed time
delay, or ends the Hold after one cycle.
If you set the PRIBLK parameter in the IOUT block to 1, the block should use the PRITIME (set
to 0 to x seconds) to determine whether to wait for the upstream block to return an Acknowledge
(PRITIM=0) or hold the current output for x seconds (PRITIM=x) during a manual to automatic
mode change.
However, the warning “W48 – INVALID BLOCK OPTION” appears when you configure PRITIM to
0.0 and PRIBLK to 1 (that is, forcing the block to Hold until the upstream block returns an
Acknowledge). Set PRITIM to a value greater than 0 seconds.
9.15.5 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223)

Changing the FSENAB (fail-safe enable) parameter from 0 to 1 on an ECB200 that is configured
for PROFIBUS-DP FBM223 may cause the associated DCI blocks to go fail-safe. This is only
true if the DCI blocks are configured for fail-safe due to loss of communications.
9.15.6 TIMSTP Parameter of the EVENT Block

The Time Stamp parameter (TIMSTP) in the EVENT block should give the time, in millisec-
onds past midnight, when the FBM generates an event record. Occasionally, the TIMSTP param-
eter of the EVENT block resets to 0 when the FBM is downloaded or placed on-line. After the
TIMSTP parameter resets, it starts counting the milliseconds since the reset, instead of resuming
counting at milliseconds since midnight. After about 50 seconds, the parameter is synchronized
correctly with the CP time. This situation has been observed using an FBM207b attached to a
ZCP270 via a pair of Fieldbus Communication Modules.
9.15.7 Changing Engineering Range Limits in AOUT, AOUTR,

ROUT, and ROUTR Blocks
Changing engineering range limits in the AOUT, AOUTR, ROUT, or ROUTR blocks may limit
output in ways you would not expect. For example, after changing the engineering units in the
ROUTR block from 4-20 to 0-100, the block output may still be limited in the 4-20 range. This
output limiting behavior is a phenomenon that has existed in the AOUT, AOUTR, ROUT, and
ROUTR blocks.
The absolute engineering range limits of the output in these blocks is specified by the LSCO1,
HSCO1, and OSV parameters. However, these blocks also contain output limit values (LOLIM
and HOLIM), which are normally used to constrain the output to operating limits that are nar-
rower than the engineering range limits.
When these blocks run, the LOLIM and HOLIM limit values are not allowed to exceed the engi-
neering range. In the example noted above, the block logic sets LOLIM=4 and HOLIM=20 when
the block initializes, since LSCO1=4 and HSCO1=20.
When the block initializes with the modified engineering range (LSCO1=0 and HSCO1=100),
the LOLIM, HOLIM values are NOT modified since they are already within the new engineering
range. As a result, the output will remain limited between 4-20.
111
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.
9.16 Electronic Documentation

9.16.1 DCI Block and Fail-Safe
Field Device System Integrators (FBM230/231/232/233) User’s Guide (B0700AH) indicates that
deleting a DCI block that is configured with a non-zero FSOPTN parameter causes the DCI
block to write its configured fail-safe value to the FBM. This feature does not work in the current
product.
9.16.2 PLSOUT Holding and Tracking States

According to PLC Interface Block Descriptions (B0193YQ), the PLSOUT block goes to the Hold
state when the ECB is bad or out of service, when in fact, the block goes to the Tracking state
under these conditions. The “PLSOUT” chapter should be revised to clarify the tracking and
holding states, as follows:
Block Tracking Conditions

The PLSOUT block remains in “Tracking” to indicate that, even though the PLSOUT block is
able to communicate with the field device, the PLSOUT block has no control on the actual out-
put to the process. This can happen when:
♦ There is an initialization request from the field indicated by INI_PT
♦ The field device (through the FBM) indicates both a Limited Low and a Limited
High condition
♦ The field device indicates that it is under Local Override control.
While in Tracking, the PLSOUT block keeps its output (COUT_1 and COUT_2) unchanged.
Block Holding Conditions

The PLSOUT block remains in “Holding” to indicate that the PLSOUT block is unable to send
the output value to the field. This can happen when:
♦ There is loss of communication to the FBM (the ECB is bad and/or out of service).
♦ Any one of COUT_1, COUT_2, RBK, or INI_PT has status indicating bad and/or
out of service.
♦ IN is “Bad” as determined by parameter EROPT [see “Parameter Definitions” in PLC
Interface Block Descriptions (B0193YQ)].
While in Holding, the PLSOUT block keeps its output (COUT_1 and COUT_2) unchanged.
112
9.16.3 Time Strobe Converter Installation Documented in

B0700AQ
Figure 5-7, “Time Strobe Converter (P0972KA and P0973BW)” in Time Synchronization User’s
Guide (B0700AQ) shows the P0972KA and P0973BW time strobe converters with power input
and power output polarities reversed. Connecting power according to the incorrect diagram spec-
ifications can cause the converter to fail.
The polarity of the power input and power output connectors is positive, negative, positive, nega-
tive starting at the left side of the converter. The following diagram, which shows the correct
polarities, will be included in a future revision of B0700AQ.
Power Input Power Output

(-) (+)
Power Input Power Output

Time Strobe
(+) (-)
Outputs (8)
Strobe Output Strobe Input (Rx)

(Tx) - MMF Cable MMF for P0972KA
SMF for P0973BW
Rear View Front View

Figure 9-2. Time Strobe Converter (P0972KA and P0973BW)
113
114
10. Problems Resolved in V8.2
This chapter describes the problems resolved in I/A Series V8.2 software.
10.1 FBM211 Values Freeze (CAR #1005709)
Problem Occasionally, values from an FBM211 used in combination with ISTA

boards would not update. There is no operator indication when this occurs,
and replacing the FBM did not correct the problem.
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.
10.2 FBM224 Phasing Enhancements

(CAR #1006285)
Problem An enhancement to support phasing of transactions from the FBM224 to

the field devices was needed.
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.
10.3 Release Level Information in SYSLVL
Problem The file /usr/fox/sys/lastinst/SYSLVL contained incorrect release

information.
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
10.4 Blue Screen During Day 1 Installation

(CAR #1006761)
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.
10.5 Display Manager Redirect Command

(CAR# 1006892)
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.
10.6 Counting and Retrieving Alarms for Alarm

History Displays (CAR# 1006902)
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
10.7 Off-Line Indication of GCIO and Annunciator

Keyboards in SMDH (CAR# 1006911)
Problem GCIO, annunciator keyboards, and annunciator/numeric keyboards would

intermittently go offline (appear red) in SMDH and send messages to the
log. When this occurred, the operation of these devices was not affected.
Rebooting the workstation would clear the off-line indication in SMDH.
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.
10.8 ACCUM and PID Default Displays

(CAR# 1006964)
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.
10.9 Timeouts Causing Device Failure on FDSI FBMs

(CAR# 1006848)
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
10.10 FCM100Ets Freezing After Power Failure

(CAR# 1006999)
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.
10.11 Status of Switches and ZCP270 in System

Management (CAR# 1007002, 1007285)
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.
10.12 ROUT Default Display (CAR# 1007036)
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.13 Changing Block Order Using ICCAPI

(CAR# 1007052)
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.
10.14 FIELD BUS A and FIELD BUS B Text Fields on

ZCP270 Equipment Information
Display (CAR# 1007119)
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
10.15 Error Messages on Windows XP Based

Workstations (CAR# 1007128)
Problem Windows XP based workstations were encountering error messages on

bootup.
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.
10.16 FCM100Et Letterbug Restriction

(CAR# 1007185)
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.
10.17 CP Shadow Failure after Switch Failure

(CAR# 1007241)
Problem After a switch port failure, a CP shadow failure occurred.
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.18 Backup Alarm System Causing Lost Alarms

(CAR# 1007247)
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.
10.19 FCM100Et and Time Strobe (CAR# 1007374)
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.
10.20 CP270 Alarm Messaging (CAR# 1007348,

1007102)
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
10.21 Removing Control Bus Cables from Fault-

Tolerant CP270s(CAR# 1007391)
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.
10.22 Role Reversals After Removing Cable from

FCM Master (CAR# 1007392)
Problem Occasionally, when an A or B cable is removed from an FCM Master, the

Master/Tracker roles do not reverse. In some cases, removing an A cable
causes the A cable to fail on both Master and Tracker. If the baseplate is
powered down and then back up, the problem is non-repeatable.
Resolution This problem has been corrected with V8.2 software. Master/Tracker roles
reverse correctly after removing cables from an FCM100Et Master.
10.23 Configuring Alarm Panels for USER DISPLAY

and TOP PRIORITY Functions (CAR# 1007509)
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.24 Multiple FCM100Et Status Indications

(CAR# 1007520)
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.
10.25 Equipment Failure Acknowledged and FCM

Failure and Recovery Messages (CAR# 1007531)
Problem System Management was reporting inaccurate indications:

♦ An “Equipment failure acknowledged” message appeared when no
acknowledgement was performed
♦ “FCM A bus failed”, and “FCM B bus failed” messages appeared
when only the A bus from the Ethernet switch, ZCP, or workstation
was failed.
Resolution The incorrect “Equipment failure acknowledged” message no longer

appears with V8.2 software.
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
10.26 Foundation fieldbus Network Issues

(CAR# 1007553)
Problem The following problems occurred while testing a FOUNDATION fieldbus

network:
♦ After a power cycle of the FF bus, not all blocks were coming back on-
line. An FBM download would solve the problem periodically.
♦ Turning an actuator off and then back on again was causing blocks to
randomly go from yellow to red in System Management. Some blocks
did not return to their normal yellow or white status.
♦ The system exhibits incorrect redundancy behavior if the redundancy
adapter is removed.
♦ If synchronization between Master and Tracker fails, the Tracker may
remove configured points, and the points end up BAD and OOS.
Resolution These problems have been corrected in V8.2 I/A Series software.
10.27 Alarm Manager Locking Up (CAR# 1007575)
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.
10.28 Cyan Points from FBM233 (CAR# 1007587)
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.29 ZCPs Going Single (CAR# 1007589)
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.
10.30 ECB110 HWTYPE and SWTYPE Parameters

(CAR# 1007630)
Problem Revision S of Integrated Control Block Descriptions (B0193AX) incorrectly

lists the ECB110 HWTYPE and SWTYPE parameters as “110”. The cor-
rect values are HWTYPE=200 and SWTYPE=200.
Resolution This problem has been corrected in Revision T of B0193AX.
10.31 Nodebus Cable Tests Causing ATS and

Workstation Failure and Recovery (CAR# 1007736)
Problem After performing a series of “RUN NODEBUS CABLE TEST” actions

between an ATS and a workstation from the Online Diagnostics display in
SMDH, the System Monitor log and SMDH indicated the failure of the
ATS and workstation. Eventually, the ATS and workstation would recover
without the need to reboot.
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.
10.32 Inconsistent PDUS30 Counts (CAR# 1007738)
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
10.33 Master Timekeeper Takeover Logic

Improvements (CAR# 1007771)
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.
10.34 FCM100Et Status Error (CAR# 1007799)
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.
10.35 System Monitor Exiting (CAR# 1008008)
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.36 CPU Usage While Running Vulnerability

Scanner (CAR# 1008039)
Problem Startup of FlexLM, an unused license manager, caused the Windows XP

workstations CPU usage to rise to 100% while an open-source vulnerability
scanner was running. The only way to restore the workstation to its normal
CPU utilization after the scan was to stop the FOXBOROD.exe process.
Resolution This problem has been corrected in V8.2 I/A Series software. V8.2 software
prevents the startup of the FlexLM license manager.
10.37 FBM228 Tracker Takeover Problems

(CAR# 1008048)
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.
10.38 Incorrect FF H1 Selector Value Used by

FBM228 (CAR# 1008090)
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
10.39 ZCP270 Reboot Causing FBM/FCM SMDH

Status Changes (CAR# 1008171)
Problem When a ZCP270 shadow module is rebooted, all FCM100Efs go off-line

and then back on-line after 2 to 3 seconds. Under each FCM, the FBMs
may also go off-line and then back on-line after 2 to 3 seconds. The same
results are obtained when rebooting the primary ZCP270.
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.
10.40 Letterbug Restrictions Causing FBM Download

Failure (CAR# 1008209)
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.
10.41 PIO Subsystem Alarm Correction

(CAR #2001786)
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.42 System Alarming When ZCP270 Loses PIO

Connection (CAR# 2001900)
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
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.
11.1 Hardware Requirements

Before you install the I/A Series Electronic Documentation, make sure that your computer meets
the following minimum system requirements:
♦ Pentium® class processor or higher
♦ 32 MB of RAM
♦ Hard disk with at least 43.5 MB for Adobe Reader 6.0, if not already installed
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
11.2 Software Requirements

Adobe Reader software allows you to view documents on the I/A Series Electronic Documenta-
tion CD-ROM. The only versions of Adobe Reader that support the Search capability of the elec-
tronic documentation are V7.0 and V6.0. These versions are provided on the documentation
CD-ROM.
Adobe Reader V7.0 is supported on:
♦ Windows NT with Service Pack 6 or 6a, Windows 2000 with Service Pack 2,
Windows XP, or Windows Server 2003 operating system.
Adobe Reader V6.0 is supported on:
♦ Windows 98 Second Edition, Windows NT with Service Pack 6, Windows 2000
with Service Pack 2, or Windows XP operating system.
These are the minimum requirements for correctly viewing and searching I/A Series documenta-
tion. If you want to view or search documents using Windows 98, you must manually install
Adobe Reader V6.0 from the Electronic Documentation CD-ROM.
In order to run, I/A Series Electronic Documentation also requires the following:
♦ Windows NT 4.0, Windows XP, or Windows 95/98/2000 operating system
♦ Internet browser, such as Microsoft® Internet Explorer 5.1 or later, to access the
I/A Series system parts list from the iastore link on the CD-ROM
♦ Adobe Acrobat Reader 5.0 or later.
11.3 Installing I/A Series Electronic Documentation

I/A Series Electronic Documentation requires 43.5 MB of available disk space for the Adobe
Reader 7.0 application, if not already installed. Refer to “Hardware Requirements” on page 131
for more details.
To install I/A Series Electronic Documentation and Adobe Reader 7.0, proceed as follows:
1. Uninstall any previous versions of I/A Series Electronic Documentation using the Add
or Remove Programs icon from the Control Panel.
2. Insert the I/A Series Electronic Documentation CD-ROM in the CD-ROM drive,
and the installation process begins automatically. If I/A Series Electronic Documenta-
tion does not automatically begin installing, perform the following steps to manually
start the process:
a. Click on Start > Run....
b. Type: <driveletter>:\setup\setup.exe where <driveletter> is your
CD-ROM drive letter.
3. Click the Next button.
♦ If you meet the specifications for “Software Requirements” on page 132, and do
not wish to install Adobe Reader 7.0 (or if you have previously installed Adobe
Reader 7.0), leave the box next to “Adobe Reader 7.0” unchecked and click Next.
Skip Step 3, and continue to Step 4.
♦ If you want to install Adobe Reader 7.0, go to Step 3.
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.
11.4 Starting I/A Series Electronic Documentation

To start I/A Series Electronic Documentation at any time:
1. Verify that the CD-ROM is inserted in the CD-ROM drive.
2. Select: Start > Programs > IA Series Documentation > IA Series 8.x
(K0173WT-G).
NOTE
The I/A Series software version and documentation CD revision letter in the Start
menu may vary.
A window appears which allows you to navigate or search the electronic

documentation CD-ROM.
3. To go back to the initial window from a document, click on Go Back at the top of the
Bookmark list.
11.5 Browsing the User Documentation

To navigate the User Documentation, follow these steps:
1. At the initial window, select an index viewing option from the Bookmark list at the
left of your screen. You have the following choices:
♦ Read Me First (explains initial installation settings and procedures)
♦ Part Number
♦ Title (alphabetical)
♦ Category
♦ iastore (online store for purchasing system software and hardware).
133
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.
11.6 Searching I/A Series Electronic Documentation

In order to search I/A Series Electronic Documentation, you must have a search version of Adobe
Acrobat (5.0 or higher). In addition, it is necessary to go into Adobe Reader to set specific prefer-
ences as well as add the I/A Series Electronic Documentation search index.
11.6.1 Set up Preferences for Searching

Adobe Acrobat Reader 5.0, which is not shipped on the I/A Series Electronic Documentation
V8.0 CD, and Adobe Reader 6.0 have different preference setup instructions, outlined below.
Adobe Acrobat Reader 5.0 Instructions

The following preferences need to be set in Adobe Acrobat Reader 5.0:
1. To have multiple windows open at the same time,
a. Select Edit > Preferences > Options.
b. Make sure that “Open Cross-Document Links in Same Window” is unchecked.
2. To allow the search and results windows to appear on top of the main window when
searching,
a. Select Edit > Preferences > Search.
b. Make sure that “Hide Query Dialog on Search” and “Hide Result Dialog on
Search” are unchecked.
Adobe Reader 6.0 Instructions

The following preferences need to be set in Adobe Reader 6.0:
1. To have multiple windows open at the same time,
a. Select Edit > Preferences > General.
b. Make sure that “Open Cross-Document Links in Same Window” is unchecked.
2. Access the Adobe Online Guide from the Help menu on the CD-ROM to obtain
additional information on navigation, searching, zooming in and out, and setting up
preferences.
11.6.2 Add the I/A Series Electronic Documentation Search

Index
The Adobe Reader, by default, searches its own index (the Adobe Online Guide). In order to
search the documents on the I/A Series Electronic Documentation CD-ROM, the search indexes
for the document sets need to be added.
134
11. I/A Series Electronic Documentation B0700RN – Rev C
Adobe Acrobat Reader 5.0 Instructions

To add the search index using Adobe Acrobat Reader 5.0:
♦ Select Edit > Search > Select Indexes.
♦ Click Add. This opens a browse window.
♦ Go to the CD-ROM drive containing the I/A Series Electronic Documentation
CD-ROM.
♦ Double-click on the file index80.pdx to add it to the searchable indexes.
♦ Click OK.
Adobe Reader 6.0 Instructions

To add the search index using Adobe Reader 6.0:
♦ Select Edit > Search. This opens a Search pane in the right-hand side of the
window.
♦ In the Search pane, click Use Advanced Search Options.
♦ From the Look In pull-down menu, choose Select Index. The Index Selection
window appears.
♦ Click Add to open the browse window.
♦ From the browse window, navigate to the CD-ROM drive containing the I/A
Series Electronic Documentation CD-ROM.
♦ Double-click on the file index80.pdx to add it to the searchable indexes.
♦ Click OK.
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
11.6.4 Advanced Search

For a more complete explanation of the search and advanced search capabilities, refer to the
Adobe Reader Help available from the Help button within Adobe Acrobat Reader V5.0 or Adobe
Reader V6.0.
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.1 Saving Files

For workstations running the Windows operating system, files must be saved to 3.5-inch dis-
kettes, a tape drive, or some other medium, for example, a recordable CD in order for the files to
be restored after the installation.
A.2 Files to Back Up/Restore for Day 0 Migration

Files listed in the following subsections may be backed up from your pre-V8.2 Windows system
for later restoration.
A.2.1 Application Databases

Consider backing up the following application database files. These files reside on the D: drive of
a Windows workstation.
Files requiring changes need to be recustomized. Do not just replace Day 0 files with older files.
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).
Consider backing up the following application database files.

♦ \opt\fox\ais\bin\aiscfg
♦ \opt\fox\ais\bin\foxapi.cfg
♦ \opt\fox\ais\bin\an_init.cfg
♦ \opt\fox\ais\bin\aisstart
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
A.2.1.2 Control Libraries

♦ \opt\fox\ciocfg\sequenlibrary
♦ \opt\fox\ciocfg\sequeninclude
♦ \opt\fox\ciocfg\plblibrary
A.2.2 Display-Related Files

Back up all customized display files. No display file conversion is necessary when migrating dis-
play files from a pre-V8.x Windows workstation. Display file conversion may be required if you
have displays from a UNIX-based workstation that you would like to port to a V8.x Windows sys-
tem. Refer to the appendix titled, “Display Convert Utility” in FoxDraw™ Software (B0700BE)
for instructions on using the conversion utility.
Customized markers, fonts, faceplates, and so forth, developed using the FoxDraw package, are
stored in the directory /opt/customer/displib.
Consider backing up the following display-related files. These files reside on the D: drive of a
Windows workstation.
♦ \usr\fox\alarms\<logical_name>AAtab1
♦ \usr\fox\alarms\<logical_name>AApan1
♦ \usr\fox\alarms\commgrp.cfg
♦ \usr\fox\alarms\alarms.fmt
♦ \usr\fox\alarms\<logical_name>.apc (or <logical_name>.apccr)1
♦ \usr\fox\alarms\horn.cfg
♦ \usr\fox\wp\data\wp5?_cmds2
♦ \usr\fox\wp\data\wp5?_glbls.12
♦ \usr\fox\wp\data\wp5?_glbls.all2
♦ \usr\fox\wp\data\am_cmds2
♦ \usr\fox\customer\hi\dmcfg2
♦ \usr\fox\customer\alarms\cfg2
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.
A.2.3 System-Related Files

Consider backing up the following system-related files. These files reside on the D: drive of a
Windows workstation.
A.2.3.1 Application Files

♦ \etc\fox\opsys_usr.cfg3
A.2.3.2 Historian Files

♦ \opt\aim\inst
♦ \opt\aim\myfiles.
A.2.3.3 User Applications and Third-Party Package Files

All databases and configuration files for user applications and third-party packages must be
backed up. Include Invensys Foxboro Industry or Application Group applications found in
/etc/fox/rc.foxapps and /usr/fox/bin/user_apps.dat.
Following I/A Series software installation, these files can be restored from tape and the applica-
tions and third-party packages can be reloaded or installed from user- or vendor-supplied media.
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.
A.3 Backing Up and Restoring Compound Summary

Access (CSA)
When upgrading to V8.2 software, you may want to move CSA to a new host. Moving CSA
between hosts requires that you back up and restore the CSA files using the CSA_Save and
CSA_Merge utilities, described in the following subsections.
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
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
A.3.1 Backing Up CSA (CSA_Save)

On the CSA host station, perform CSA_Save to back up the CSA database files.
Intel Station (AP20/PW)

For the Intel CSA_Save procedure you need a formatted, mountable, 3.5-inch diskette (use the
VENIX™ format command).
1. Log into the AP20 from the WYSE terminal.
2. Insert the formatted diskette into drive 0 and save the CSA information. Type:
cd /usr/fox/ulan
CSA_Save
3. Verify the contents of the save file(s). Type the following:
mount /dev/fh0 /f0
ls -l
Verify that each control station has a text file on the diskette.
4. Unmount the diskette and label it. Type:
umount /dev/fh0
This completes the Intel CSA_Save procedure.
140
50/70 Series Station
NOTE
The CSA_Save operation might fail for individual stations that have compounds
without blocks. When this occurs, remove the empty compound, using the Inte-
grated Control Configurator, and retry the CSA_Save operation.
1. Back up the CSA database files. Before performing this operation, consider the
following:
♦ An empty directory must be available for the CSA_Save operation. The
(CSA_Save) operation might fail for stations for which a file already exists.
♦ For drive space requirements, assume that you need 15 KB of space per control
station. Use the df command to check available drive space in the /usr partition.
2. Type the following:
cd /usr/fox/csa
mkdir save
CSA_Save ./save
This saves the CSA files in the /usr/fox/csa/save directory. There is one text file for
each control station.
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:
tar cvf /dev/fd0 * (50 Series)
tar cvf a: * (70 Series)
A.3.2 Restoring CSA (CSA_Merge) on 50/70 Series Stations

1. Extract the CSA files from the diskette produced by the CSA backup procedure.
Insert the diskette and type the following:
mkdir /usr/fox/csa/save
tar xvf /dev/fd0 (50 Series)
tar xvf a: * (70 Series)
2. Restore the CSA database. Type the following:
cd /usr/fox/csa
CSA_Merge ./save
3. You can remove the CSA text files at this time to recover drive space. Type:
rm -r /usr/fox/csa/save
141
A.3.3 Moving CSA Between 50/70 Series Stations

NOTE
The CSA_Save operation might fail for individual stations that have compounds
without blocks.
It is recommended that this procedure be performed only by qualified Invensys Foxboro

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

A.3.4.1 Backing Up Intel CSA (CSA_Save)
This procedure describes how to save the Intel CSA database to a 3.5-inch diskette and convert it
for use by a 50 Series station. This procedure may only be used on the Intel CSA host station.
NOTE
Once the CSA_Stop utility is initiated, CSA menu access and Integrated Control
Configurator access is not possible until the CSA database is restored onto the
50 Series CSA host.
For the Intel CSA_Save procedure you need a formatted, mountable, 3.5-inch diskette (use the
VENIX format command).
1. Log into the AP20 from the WYSE terminal.
2. Insert the formatted diskette into drive 0 and save the CSA information. Type:
cd /usr/fox/ulan
CSA_Save
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
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
A.3.4.2 Restoring CSA (CSA_Merge)

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

A.4.1 Saving Control Databases (SaveAlls)
Save the databases for all control stations before performing the Day 0 installation. If you want to
upload the latest settable parameters from the control station, perform the upload before perform-
ing the SaveAll. Label each diskette with the diskette number and quantity if the SaveAll opera-
tion requires more than one diskette, for example, 1/2, 2/2.
Refer to the appropriate document below for information on performing the SaveAll:
♦ I/A Series Configuration Component (IACC) User’s Guide (B0400BP)
♦ Integrated Control Configurator (B0193AV).
A.4.2 Downloading Control Databases

Depending on the configurator you are using, refer to I/A Series Configuration Component (IACC)
User’s Guide (B0400BP) or Integrated Control Configurator (B0193AV) for procedures to down-
load the control station databases.
144
Appendix B. EEPROM Revision
Levels
This section indicates specific modules’ image revision levels.
B.1 Image Revision Levels for V6.x/V7.x Control

Stations
Station images released with V6.5.3/V7.1.2 software are also included on the V8.2 trailer CD-
ROM. If you are rehosting Nodebus control stations on Mesh workstations, the station must be
updated with a minimum of the images listed in “Control Database Interoperability” on page 22
and “Image Levels for Nodebus Control Stations” on page 23.
The appendixes titled, “EEPROM Revision Levels” in the following documents list control sta-
tion images for I/A Series software V7.1.2 and V6.5.3 and describe updating control station
images:
♦ V7.1.2 Release Notes and Installation for UNIX® and Windows® XP (B0400QP)
♦ V6.5.3 Release Notes and Installation UNIX® and Windows NT® (B0400EM).
B.2 Image Revision Levels for V8.2 Components

Station images for V8.2 components are listed below.
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.
Table B-1. V8.2 Control Stations
Description Station Mnemonic V8.2 Image Revision Level

Field Control Processor 270 FCP270 3.8
Z-Module Control Processor 270 ZCP270 3.8
The following table lists the EEPROM revision level of the ATS.
Table B-2. V8.2 Address Translation Station
V8.2 EEPROM Revision

Description Station Mnemonic Level
Address Translation Station ATS 3.8
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.
Table B-3. Miscellaneous EEPROM Revision Levels
V8.2 EEPROM Revision

Description Station Mnemonic Levels
GCIO Interface GCIO Interface 1.3
Keyboard KBD 5.9
Annunciator Keypad AKP 5.8
B.3 100 Series FBM Software Versions

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

EEPROM REV: <EEPROM Version>
NOTE
In the following table, N/A indicates that the station or module is not available for
that I/A Series software release.
Table B-4. Software Versions of 100 Series FBMs (Y Form Factor)
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
V8.0B/
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,
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
Table B-4. Software Versions of 100 Series FBMs (Y Form Factor) (Continued)
EEPROM
V8.0B/
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
B.4 200 Series FBM Software Versions

Table B-5 lists 200 Series FBMs and their software versions. 200 Series FBMs and communica-
tion modules must be EEPROM updated if they are not at the current revision level. Software
and EEPROM revision levels for 200 Series FBMs and most associated modules (except FCMs)
are displayed in the System Management Equipment Information display as follows:
SOFTWARE REV: <FBM> <Software Version> or <Software Version> <FBM>

EEPROM REV: ROM <Software Version>
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)
Software Version EEPROM Revision Level

V8.0B/ V8.0B/
Devices Using IOM ID V7.1.1 V8.1 V8.1.1 V8.2 V7.1.1 V8.1 V8.1.1 V8.2
FBM208 IOM80 N/A 1.15F 1.16 – N/A 1.15F 1.16 –
FBM240 IOM81 N/A 1.15A 1.16 – N/A 1.15A 1.16 –
FBI10E, FCM10E, IOM82 ? ? ? 1.16 ? ? ? 1.16
FBI10E, FCM10E,
FCM10Ef,
WFCM10E,
WFCM10Ef,
DCM10E
148
Appendix B. EEPROM Revision Levels B0700RN – Rev C
Table B-5. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) (Continued)

V8.0B/ V8.0B/
FBM201, WAI01A IOM83 1.05 1.15G 1.16 – 1.05 1.15G 1.16 –
through D, WAW01A
through F, WAX01A
through C
FBM202, FBM202B, IOM84 1.05 1.15F 1.16 – 1.05 1.15F 1.16 –
WAI02A, WAV02A,
WAX02A
FBM203, FBM203B, IOM85 1.05 1.15E 1.17 – 1.05 1.15E 1.17 –
FBM203C, WRF03A,
WRF03B, WRT03A,
WRT03B
FBM204, WLJ04A IOM86 1.05 1.15C 1.16 – 1.05 1.15C 1.16 –
through C
FBM205 IOM87 1.05 1.15C 1.16 – 1.05 1.15C 1.16 –
FBM206, WPA06A IOM88 1.05 1.15A 1.16 – 1.05 1.15A 1.16 –
FBM207, FBM207B, IOM89 1.11 1.15G 1.16 – 1.11 1.15G 1.16 –
FBM207C, WCI07A,
WDI01A through E,
WID07A through P
FBM211, WAH01A IOM90 1.05 1.15A 1.19 – 1.05 1.15A 1.19 –
through D
FBM212 IOM91 1.05 1.15A 1.18 – 1.05 1.15A 1.18 –
FBM2132 IOM92 1.05 1.15A 1.16 – 1.05 1.15A 1.16 –
FBM237, WAO37A IOM93 1.05 1.15A 1.16 – 1.05 1.15A 1.16 –
through G
FBM241, FBM241B IOM94 1.11 1.15A 1.16 – 1.11 1.15A 1.16 –
through D
FBM242, WBO09A, IOM95 1.11 1.15G 1.16 – 1.11 1.15G 1.16 –
WBO09B, WRO09A
through D, WTO09A
FBM217 IOM96 1.11 1.15G 1.16 – 1.11 1.15G 1.16 –
FBM243, FBM246 IOM97 2.06 2.07 – – 2.06 2.07 – –
(FoxCom™)
FBM219 IOM98 1.11 1.15A 1.16 – 1.11 1.15A 1.16 –
FCM100Et IOM210 N/A 1.30 – 1.38 N/A 1.30 – 1.38
FBM214 (HART) IOM214 2.23LA 2.24 2.29 – 2.23LA 2.24 2.29 –
FBM215 (HART) IOM215 2.23LA 2.24 2.28B 2.30 2.23LA 2.24 2.28B 2.30
FBM216 (HART) IOM216 2.23LA 2.24 2.29 – 2.23LA 2.24 2.29 –
FBM218 (HART) IOM218 2.23LA 2.24 2.28B 2.30 2.23LA 2.24 2.28B 2.30
FBM220 (FOUNDA- IOM220 2.15 2.17 2.18 2.19 2.13 – – –
TION™ fieldbus H1)
FBM221 (FOUNDA- IOM221 2.15 2.17 2.18 2.19 2.13 – – –
TION fieldbus H1)
FBM223 (Profibus- IOM223 1.02 1.03 1.05 – 1.02 – – 1.05
DP)
FBM224 (Modbus) IOM224 1.02c 1.03 1.07 – 1.02c 1.03 1.07 –
FBM228 (Redun- IOM228 N/A 1.05 2.02 2.05 N/A 1.0 – –
dant FOUNDATION
fieldbus H1)
149
Table B-5. Software Versions for 200 Series FBMs (DIN Rail Mounted Form Factor) (Continued)

V8.0B/ V8.0B/
FBM230 (Simplex IOM230 N/A 1.01 1.03 – N/A 0097/03 04.01.0052 –
Serial FDSI) 05
FBM231 (Redun- IOM231 N/A 1.01 1.03 – N/A 0097/03 04.01.0052 –
dant Serial FDSI) 05
FBM232 (Simplex IOM232 N/A 1.01 1.03 – N/A 0097/03 04.01.0052 –
Ethernet FDSI) 05
FBM233 (Redun- IOM233 N/A 1.01 1.03 – N/A 0097/03 04.01.0052 –
dant Ethernet FDSI) 05
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.
C.1 Checking Current NIC Driver Versions

Check the date and version of the current NIC drivers installed in the workstation, and upgrade
drivers as appropriate.
C.1.1 Allied Telesyn NIC Driver

Perform the following steps to check the date and version number of the Allied Telesyn NIC
driver:
1. Right-click My Computer and select Manage.
2. Click Device Manager.
3. Under Network adapters, the Device Manager should indicate two adapters of type
Allied Telesyn AT-2701FX PCI 100Mb Fiber Ethernet Adapter.
4. Right-click on the first Allied Telesyn AT-2701FX PCI 100Mb Fiber Ethernet
Adapter, select Properties, and click on the Driver tab.
5. Check the driver’s date and version number. The supported driver has a date of
7/21/2005 and a version number of 4.52.0.0. If any other dates or version numbers
are displayed, 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.
C.1.2 Intel NIC Driver

Perform the following steps to check the date and version number of the Intel NIC driver:
3. Under Network adapters, the Device Manager should indicate two adapters of type
Intel(R) Pro/1000 MT Desktop Adapter or Intel(R) Pro/1000 GT Desktop
Adapter.
4. Right-click on the first Intel(R) Pro/1000 MT (or GT) Desktop Adapter in Device
Manager, select Properties, and click on the Driver tab.
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.
C.2 Installing the Allied Telesyn NIC Driver (Fiber)

To install the correct driver for your P0972WD Allied Telesyn NICs, perform the following steps:
1. Insert the K0173XA-D CD in the CD-ROM drive.
4. Double-click Network adapters.
5. Right-click the first Allied Telesyn AT-2701FX PCI 100Mb Fiber Ethernet
Adapter or AMD PCNet Family PCI Ethernet Adapter and select Update Driver.
6. The “Hardware Update Wizard” opens. Select Install from a list or specific
location (Advanced). Click Next.
7. The wizard asks you to choose search and installation options. Click Don’t Search.
I will choose the driver to install. Click Next.
8. The wizard asks you to select the network adapter you want to install for this hard-
ware. Click Have Disk.
9. The “Install from Disk” window opens. Browse to E:\Allied Telesyn and click Open
twice.
10. When the “Install from Disk” window returns, click OK.
11. The wizard returns to the “Select Network Adapter” window. Click Next.
12. The “Completing the Hardware Update Wizard” window opens. Click Finish.
13. The Device Manager should indicate an Allied Telesyn AT-2701FX PCI 100Mb
Fiber Ethernet Adapter.
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
C.3 Installing the Intel NIC Driver (Copper)

To install the correct driver for your P0923AA or P0923DV Intel NICs, perform the following
steps. On system startup, the “Found New Hardware Wizard” may start. If it does, skip to step 5.
1. Insert the K0173XA-D CD in the CD-ROM drive.
4. Double-click Network adapters.
5. Right-click the first Intel(R) Pro/1000 MT or GT Adapter and select Update Driver.
6. The “Hardware Update Wizard” opens. Select Install from a list or specific
location (Advanced). Click Next.
7. The wizard asks you to choose search and installation options. Click Don’t Search.
I will choose the driver to install. Click Next.
8. If the wizard asks to “select the hardware type”, select Network Adapters and click
Next.
9. The wizard asks you to select the network adapter. Click Have Disk.
10. The “Install from Disk” window opens. Type E:\IntelPro and click OK.
11. The wizard returns to the “Select Network Adapter” window. Click Next.
12. The “Completing the Hardware Update Wizard” window opens. Click Finish.
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.
D.1 KSI Time Card Driver and Control Utility

After you restore your system, the workstation allows you to install the driver for the KSI time
card. After restoring the system, you need to install the KSI TPRO/TSAT-PCI Control Utility.
These procedures are described below.
D.1.1 Installing the Time Card Driver

When a Windows XP station is initially booted with a time card installed, the Plug-and-Play wiz-
ard recognizes the new hardware. At this point, you can install the KSI time card driver by per-
forming the following steps:
1. Install the “Windows XP Driver For KSI TSAT-PCI GPS System” CD-ROM
(K0173XG) when the initial Welcome screen appears and indicates “Other PCI
Bridge Device”.
2. Select Install the Software Automatically (Recommended).
3. The wizard asks you to select the Hardware Type you want to install for this hardware.
Select KSI TSAT PCI-FXA Timing board.
4. Click Next.
5. In the “Completing Found New Hardware” window select Finish.
You have completed installation of the KSI time card driver.
D.1.2 Installing the KSI TPRO/TSAT-PCI Control Utility

Follow the steps below to install the KSI TPRO/TSAT-PCI Control Utility:
1. Install the KSI CD-ROM in the CD-ROM drive and select Start > Run.
2. Type <drive letter>:\setup (where <drive letter> is the CD-ROM drive).
3. Continue to select OK, Yes, Next, or Finish when prompted.
4. Confirm the GPS hardware is working before I/A Series software is installed. To verify
the GPS system is receiving data from the satellites, proceed as follows:
a. Select Start > Programs > KSI > TPRO/TSAT Control Utility.
b. Select the product TPRO/TSAT-PCI and the selected device name, tpropci0,
appears.
c. When the TPRO/TSAT Control Utility appears, select Satellite > Retrieve
Satellite Info.
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.
E.1 List of Recommended Security Patches

If you want to install the recommended security patches, download and install the following 37
security patches from a workstation with Internet access.
1. WindowsXP-KB885836-x86-ENU.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=703DE7D8-68D9-4A92-
8C59-87221F89EF14&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=27115D5C-3E4A-4F41-
B81E-376AA1CD204F&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=96BBD220-5E2A-43AD-
B8B7-54EC608BD8BE&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=CBCCADF6-449A-4D74-
937D-4087A6E6C1C2&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=FB8A7622-94AB-44E7-
85C3-163BAC4602E2&displaylang=en
6. Windowsxp-kb888302-x86-enu.exe
http://www.microsoft.com/downloads/details.aspx?FamilyId=B8C867C2-B7CD-4E2F-
90E0-169B2C7125DC&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=6DF9B2D9-B86E-4924-
B677-978EC6B81B54&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=A0E59D77-8AC1-4AC0-
9572-A7E1C2E4A66A&displaylang=en
157
B0700RN – Rev C Appendix E. Installing Microsoft Security Patches
http://www.microsoft.com/downloads/details.aspx?FamilyId=9490e7d2-03c2-463a-
b3d0-b949f5295208&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=6005C5A3-AFF2-4765-
B26F-BE47ED408E0B&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=F0683E2B-8E8F-474F-
B8D8-46C4C33FCE99&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=17833b94-af70-47bd-
872c-033a3f0e982a&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=9CC719AD-5E57-4AEF-
9FB3-9F7AB7BB5D32&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=F2247275-25F9-4937-
97CD-9334135D6D79&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=b8ba775e-e9a7-47e9-
81a9-a68a71b9faac&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=c5bcf2db-adce-42bd-
abee-1380f258158b&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=b049004b-af28-41d7-
8ae6-7a3db15211f1&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=a229f193-da3f-4014-
925d-1eacf5ba296c&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=DD24F6FA-F6BB-4358-
8C2F-7F6AB405981A&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=EF402946-1C3B-47E9-
9D51-77D890DF8725&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=351C63A3-AB62-418D-
8678-3AF791D73A29&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=19569E67-6D99-41FC-
9457-44EC524F6106&displaylang=en
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
http://www.microsoft.com/downloads/details.aspx?FamilyId=1559E44A-DDEE-4C86-
BF02-A6C3B9BEEE0C&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=e0daf2d1-656c-4580-
94c1-8ab009b4ad4f&displaylang=en
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
http://www.microsoft.com/downloads/details.aspx?FamilyId=4C1C2C16-99E7-4701-
A3F8-65B803B8B881&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=20F79CE7-D4DB-42D7-
8E57-58656A3FB2F7&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=F7241DEB-9E2D-401A-
9D71-10ACAB4450AF&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=E38372B2-3BF6-4393-
B9A4-F34248C8073E&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=E4B5BA57-D4F2-4798-
9154-2869E371C9D1&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=0C1B4C96-57AE-499E-
B89B-215B7BB4D8E9&displaylang=en
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
http://www.microsoft.com/downloads/details.aspx?FamilyId=7BB21D74-C37B-472B-
BB10-71D4680680A7&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=62535040-5204-4469-
B0BF-EAE14567C2D5&displaylang=en
159
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
E.2 Download Instructions

Perform the following steps to download each patch on the list above:
1. On the hard disk drive of a workstation with Internet access, create a directory such as
“C:\K0173XY Patch CD” into which you will download the patches.
2. Click on a link above to download the corresponding patch. After clicking the link, a
screen similar to the following appears:
Figure 11-1. Security Update Download Window
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
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.
E.3 Creating the Equivalent of the K0173XY-A

CD-ROM
Perform the following steps to create an equivalent of the Microsoft Windows XP Security Patch
CD for Service Pack 2 (K0173XY-A) CD-ROM. Following the steps in this procedure allows you
to create a batch file that will load all the patches at one time, without having to reboot the work-
station after each patch is installed.
1. Copy and paste the contents of “Example Batch File” on page 162 to a standard
ASCII text file with a “.bat” file extension.
2. Click Start > Accessories > Notepad to open the Notepad text editor.
3. Copy the text below, starting with the Rem K0173XY-A batch file for end users
and ending with PAUSE.
4. Paste the text into the Notepad text editor.
5. Save the file as K0173XY_A.bat to the same folder containing the Microsoft patches
that were previously downloaded.
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
E.4 Example Batch File

Following is an example batch file you can cut and paste to K0173XY_A.bat.
Rem K0173XY-A batch file for end users
echo off
echo .
echo You are about to install All Windows XP Professional
echo Security Patches that were on the
echo K0173XY Rev A CD for XP Service Pack 2
echo that used to ship with the
echo I/A Series 8.2 Media Kit
echo .
echo Press CTRL-C to abort, or
PAUSE
echo .
echo on
WindowsXP-KB885836-x86-ENU.exe /quiet /norestart


Windowsxp-kb888302-x86-enu.exe /quiet /norestart





162



WindowsXP-KB886185-x86-enu.exe /quiet /norestart


WindowsMedia9-KB911565-x86-ENU.exe /quiet /norestart

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
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

I/A Series System V8.2 Release Notes and Installation Procedures

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

I/A Series System V8.2 Release Notes and Installation Procedures

Uploaded by

Copyright:

Available Formats

B0700RN

I/A Series® System

Copyright 2006-2007 Invensys Systems, Inc.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

2. Features of the V8.2 Release .............................................................................................. 5

3. Upgrade Considerations .................................................................................................... 7

3.4 Interoperability ................................................................................................................. 22

5. Windows System Setup ................................................................................................... 37

5.3.1 FoxAPI Software ....................................................................................................... 39

6. Defining Your System ..................................................................................................... 41

7. V8.2 Installation Procedures............................................................................................ 43

7.5 Postinstallation Procedures ................................................................................................ 72

8. V8.2 Operational Recommendations............................................................................... 73

8.10.5 Historians Running on the Same Station ................................................................. 89

9. V8.2 User Notes .............................................................................................................. 99

9.15.5 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223) .............................. 111

10. Problems Resolved in V8.2.......................................................................................... 115

10.29 ZCPs Going Single (CAR# 1007589) ......................................................................... 125

11. I/A Series Electronic Documentation .......................................................................... 131

Appendix A. Files to Back Up/Restore............................................................................... 137

A.3.4 Moving CSA from Intel to 50 Series Stations .......................................................... 143

Appendix B. EEPROM Revision Levels............................................................................. 145

Appendix C. Installing/Updating NIC Drivers.................................................................. 151

Appendix D. Installing Optional Workstation Components ............................................. 155

Appendix E. Installing Microsoft Security Patches ............................................................ 157

1.1 Installation Overview

Yes Is this a new

Class A Class B Class C Class D

2.2 New and Upgraded Software Packages

2.2.2 V2.1 I/A Series Configuration Component (IACC)

2.2.3 System Management Displays

2.2.4 V10.1 FoxView®/FoxDraw® Software

2.2.5 V4.3.1 FoxAPI® Software

2.2.6 V3.2.4 AIM*API® Software

3.1 Supported Topologies and System Rules

3.1.1 ATS Modes of Operation

3.1.1.2 Extender Mode

3.1.2 System Sizing and Limitations

Nodebus 100 Mbps/1 Gbps

The Mesh and Nodebus 10 Mbps

The Mesh 5 Mbps

3.1.3 Station Hosting

♦ COMM 10 – Communication Processor 10 for FoxWatch support.

3.1.4 Overview of Control Station Rehosting

3.2 Transition Scenarios

ATS ATS ATS

The Mesh and Nodebus 10 Mbps

The Mesh 100 Mbps/1 Gbps

Figure 3-2. Comparison of Pre-Migration and Post-Migration Topologies

3.2.1 Adding Mesh Stations to a Single Node

Nodebus 100 Mbps/

Mesh stations added to single V6.x node

Figure 3-3. Adding Mesh Stations to a Single V6.x Node

NCNI NCNI V7.x Ethernet B

Nodebus 100 Mbps/

Mesh stations added to single V7.x node

Figure 3-4. Adding Mesh Stations to a Single V7.x Node

3.2.2 Connecting Multiple Nodes to The Mesh

Nodebus 100 Mbps/1 Gbps

The Mesh and Nodebus 10 Mbps

The Mesh 5 Mbps

Nodes added to The Mesh

Figure 3-5. Connecting Multiple Nodes to The Mesh Network