b0400qm A

B0400QM
REV A
I/A Series A2™ System

V7.1 Release Notes and Installation for
UNIX® and Windows® XP
June 25, 2003
Model P79
Workstation for UNIX
Model P80
Workstation for UNIX
Model P92
Workstation for Windows
Invensys, AIM*AT, AIM*Historian, Command Center, Connoisseur, FIO, Fox, FoxAMI, FoxAPI, Foxboro,
FoxCAE, FoxCom, FoxDraw, FoxEDM, FoxPanels, FoxRemote, FoxView, FOXWATCH, I/A Series,
I/A Series A2, INTERSPEC, Micro-I/A, MICROSPEC, SPECTRUM, and UFM are trademarks of Invensys
plc, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.
Copyright 2003 Invensys Systems, Inc.

All rights reserved
Contents
Figures.................................................................................................................................... xi
Tables.................................................................................................................................. xiii
Preface................................................................................................................................... xv
50 Series and 70 Series Conventions ....................................................................................... xv
Naming Conventions for UNIX Workstations .................................................................. xvi
Naming Conventions for Windows Workstations ............................................................. xvi
Reference Documents ........................................................................................................... xvii
1. Read Me First.................................................................................................................... 1
1.1 Release Overview ................................................................................................................ 1
1.1.1 Installation Overview .................................................................................................. 2
1.1.2 Upgrades ..................................................................................................................... 4
1.1.3 On-Line Upgrade ........................................................................................................ 4
1.1.4 Bootless Control Station Upgrade Procedure Not Available ........................................ 5
1.1.5 FBM and Communication Modules EEPROM Updates Required ............................. 5
1.1.6 Micro-I/A Station EEPROM Update Required ........................................................... 5
1.1.7 Upgrade and Compatibility Issues ............................................................................... 6
1.1.8 System Definition 2.4.1 .............................................................................................. 6
1.1.9 FoxView V9.0 Software ............................................................................................... 6
1.1.10 I/A Series Electronic Documentation CD-ROM ....................................................... 6
1.2 User Notes for V7.1 I/A Series A2 Software ......................................................................... 7
1.2.1 Software Installation .................................................................................................... 7
1.2.1.1 V7.1 Release Update Procedures for Windows XP Workstations
with AIM*AT Installed ................................................................................................... 7
1.2.1.2 Day 1 Commit Diskette Issues ........................................................................... 7
1.2.2 Windows XP Operating System .................................................................................. 8
1.2.2.1 Windows XP System Recovery Techniques ........................................................ 8
1.2.2.2 Minimizing and Restoring Applications from the Task Bar ................................ 8
1.2.2.3 Bringing an Active Window Forward .................................................................. 8
1.2.2.4 Customizing Autologon for Stations Running I/A Series Software
and the Windows XP Operating System ......................................................................... 8
1.2.2.5 Using telnet and ftp Utilities on a Windows XP Workstation ............................. 9
1.2.2.6 Reducing Network Traffic by Stopping Windows XP Services ........................... 9
1.2.2.7 Changing the Subnet Mask to Communicate with a Network Switch ................. 9
1.2.2.8 CPU-Intensive Applications May Cause Sluggish Performance .......................... 9
1.2.3 Solaris 8 Operating System ........................................................................................ 10
1.2.3.1 Booting into OpenWindows Without Mouse and Keyboard ............................. 10
1.2.3.2 tr Command ...................................................................................................... 10
1.2.3.3 Using the “prune” Option with the “find” Command ...................................... 11
1.2.3.4 Letterbug Mapper Running on Solaris 8 ........................................................... 11
1.2.4 Workstations ............................................................................................................. 11
1.2.4.1 Sun Workstation Dot-Matrix Printer Connections ............................................ 11
iii
B0400QM – Rev A Contents
1.2.4.2 Configuring PCL3 Printers on an I/A Series UNIX Workstation ..................... 11

1.2.4.3 Annunciator Horns on WP70C (CAR #1002783) ........................................... 12
1.2.4.4 Starting a Workstation with McAfee VirusScan Enterprise 7.0 and
NutCRACKER ............................................................................................................ 12
1.2.4.5 Communication Processor 10 (COMM10) Resource Issue .............................. 12
1.2.4.6 Running Exceed Applications on a Multi-Headed Workstation ....................... 12
1.2.4.7 P92 Workstations .............................................................................................. 12
1.2.4.8 P79 and P80 Workstations ................................................................................ 14
1.2.5 I/O Gates .................................................................................................................. 15
1.2.5.1 gpgate.dll Requirement for I/O Gates ............................................................... 15
1.2.6 Video Display ............................................................................................................ 15
1.2.6.1 Flat-Screen Monitor Setup ............................................................................... 15
1.2.7 FoxGuard Manager ................................................................................................... 15
1.2.7.1 FoxGuard Manager I/O Card Alarming ........................................................... 15
1.2.8 On-Line Upgrade ...................................................................................................... 16
1.2.8.1 Transition of CP60 Blocks to Manual Mode .................................................... 16
1.2.8.2 Temporary Loss of Communication for Field Devices ...................................... 16
1.2.8.3 On-Line Upgrade Limitations for FOUNDATION fieldbus and
PROFIBUS-DP Devices ................................................................................................ 16
1.2.8.4 Checkpointing During the On-Line Upgrade Process ...................................... 16
1.2.8.5 HART Device Status Changes .......................................................................... 17
1.2.9 Integrated Control Configurator ............................................................................... 17
1.2.9.1 Checkpoint Failure After LoadAll ...................................................................... 17
1.2.9.2 ICC API Driver Task Move Function .............................................................. 17
1.2.9.3 FixAll Errors for Several FBMs .......................................................................... 17
1.2.9.4 50 Series SaveAll Issue ....................................................................................... 18
1.2.9.5 Incorrect Parameter Display in ICC .................................................................. 18
1.2.9.6 Text Editor for Use with ICC Sequence Logic Editor ........................................ 18
1.2.10 Control Blocks and Parameters ................................................................................ 18
1.2.10.1 SIMOPT Parameter ....................................................................................... 18
1.2.10.2 Packed Boolean CALC Block Functions ......................................................... 18
1.2.10.3 PID(A) Fail-Safe Behavior After CP60 Reboot ............................................... 18
1.2.10.4 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223) ........................ 19
1.2.10.5 SUPBCO Parameter of PIDA Block ............................................................... 19
1.2.10.6 Using the Setpoint Clamping Option (SPCLMP) .......................................... 19
1.2.10.7 Using the ROCV Parameter with HART FBMs ............................................. 19
1.2.10.8 Mass Flow Transmitter ECB22 Limitation ..................................................... 19
1.2.10.9 Characterizer Block, CHARC (CAR #1004203) ............................................ 19
1.2.11 Alarms and Displays ................................................................................................ 20
1.2.11.1 Scaling Button Labels in Alarm Manager Displays .......................................... 20
1.2.11.2 LOOPID Characters Preventing Alarms ......................................................... 20
1.2.11.3 Displaying Alarms on a Workstation Without a Configured Printer ............... 21
1.2.11.4 Incorrect System Monitor Status for AW51F ................................................. 21
1.2.11.5 Delay in Call-Up of New Sequence Block Default Displays ........................... 21
1.2.11.6 ECB53 Faceplate ............................................................................................. 21
1.2.11.7 PIDX and PIDXE Faceplates .......................................................................... 21
1.2.12 System Definition 2.4.1 .......................................................................................... 22
1.2.12.1 Configuring a Model 51F Workstation with GCIO or Serial Printer ............... 22
1.2.12.2 Adding a Workstation to a Nodebus Extender Segment ................................. 22
1.2.12.3 Configuring a Micro-I/A Station Letterbug Server with SysDef ...................... 23
1.2.13 Intelligent Field Device Configurator (IFDC) ......................................................... 23
1.2.13.1 Downloading Configuration Changes to a FoxCom Device ........................... 23
iv
Contents B0400QM – Rev A
1.2.13.2 Take Intelligent Field Devices Off Scan ........................................................... 24

1.2.13.3 Do Not Restore Factory Settings from IFDC .................................................. 24
1.2.13.4 Single IFDC Session Allowed .......................................................................... 24
1.2.14 PROFIBUS-DP Configurators ................................................................................ 24
1.2.14.1 Help Button Works Incorrectly for PROFIBUS-DP Master and
Slave Configurators ....................................................................................................... 24
1.2.15 FoxAPI Software ..................................................................................................... 24
1.2.15.1 Starting the Foxhosts Program (if Necessary) ................................................... 24
1.2.16 FoxCAE Software .................................................................................................... 25
1.2.16.1 Enabling Communication Between FoxCAE and FoxAPI Software ................ 25
1.2.16.2 Generating Device Template Files .................................................................. 25
1.2.16.3 FoxCAE Communication Between a Standalone and an
I/A Series Workstation ................................................................................................. 25
1.2.16.4 Configuring FoxCAE on a non I/A Series Workstation .................................. 26
1.2.16.5 Converting Databases Between Platforms ........................................................ 26
1.2.17 Object Manager ...................................................................................................... 26
1.2.17.1 OM Load Higher Than Normal ...................................................................... 26
1.2.18 Carrierband LAN Interface ...................................................................................... 26
1.2.18.1 Nodebus Test Initiator (70 Series) .................................................................. 26
1.2.18.2 Changing Nodebus Mastership from CLAN to AW with Control .................. 27
1.2.18.3 Carrierband LAN Dump Packets .................................................................... 27
1.2.18.4 Carrierband LAN Reports Benign Message .................................................... 27
1.2.19 I/A Series Tools ....................................................................................................... 27
1.2.19.1 dbvu -t with CP60 ........................................................................................... 27
1.2.20 FBMs/FCMs ........................................................................................................... 27
1.2.20.1 Displaying FoxCom Device Information After General Download ................ 27
1.2.20.2 Incorrect Status of FBMs in SMDH ................................................................ 28
1.2.20.3 Setting FBM Fail-Safe ..................................................................................... 28
1.2.20.4 Verifying EEPROM Level of 200 Series FBMs in SMDH ............................... 28
1.2.20.5 EEPROM Updating FBMs ............................................................................. 28
1.2.20.6 Misleading System Monitor Messages After EEPROM Updates
of FBM216/218 ............................................................................................................ 28
1.2.20.7 FBM216 and 218 SMDH Field Updates ........................................................ 29
1.2.20.8 Temporary Communication Failures of FBM215 and FBM218 .................... 29
1.2.20.9 Configuring Fail-Safe for Proper Operation of FBM218 ................................ 29
1.2.20.10 FBM220/221 EEPROM Updates ................................................................. 29
1.2.20.11 FBM223 Problems After CP60 Reboot ......................................................... 29
1.2.20.12 Status of FBM224 Ports at Initialization ....................................................... 29
1.2.21 Control Stations ...................................................................................................... 30
1.2.21.1 Fault-Tolerant Control Station Communication ............................................. 30
1.2.21.2 CP60 Fail-Safe Actions with PROFIBUS-DP FBM223 ................................. 30
1.2.21.3 Location of Include File mpt.h for Allen-Bradley Station ................................ 30
1.2.21.4 Incorrect Software Version Displayed for the AW70CP ................................. 30
1.2.22 Field Automation Subsystem Micro-I/A Station ...................................................... 31
1.2.22.1 Blocks, Parameters, and ECBs ......................................................................... 31
1.2.22.2 GE FANUC Direct Connect I/O Interface ..................................................... 31
1.2.22.3 Dual Ethernet Interface ................................................................................... 32
1.2.22.4 Modbus Interface ............................................................................................ 32
1.2.22.5 A-B PLC5/E Interface ..................................................................................... 32
1.2.23 Electronic Documentation ...................................................................................... 33
1.2.23.1 Incorrect Documentation for ROCV Parameter in B0193AX ......................... 33
v
1.2.23.2 Incorrect Graphical Representation of an IFDC Point Calibration

Screen ........................................................................................................................... 33
1.2.23.3 PLSOUT Holding and Tracking States .......................................................... 34
1.2.23.4 Missing Step in B0400QE .............................................................................. 35
1.2.23.5 Errors in System Setup Chapters of B0400QC ............................................... 35
1.2.23.6 Errors in Chapter 5 of B0400FA .................................................................... 35
2. UNIX System Setup ........................................................................................................ 37

2.1 Documents and Media ...................................................................................................... 37
2.1.1 V7.1 50 Series Documents ........................................................................................ 37
2.1.2 V7.1 Model P79 and Model P80 Media .................................................................... 37
2.2 Optional Packages Installation .......................................................................................... 38
2.2.1 FoxView/FoxDraw Packages ..................................................................................... 38
2.3 V7.1 Software Distribution Media Contents ..................................................................... 39
3. Windows XP System Setup ............................................................................................. 41

3.1 Documents and Media ...................................................................................................... 41
3.1.1 V7.1 70 Series Documents ........................................................................................ 41
3.1.2 V7.1 Model P92 Media ............................................................................................. 42
3.2 Optional Packages Installation .......................................................................................... 42
3.3 FoxView/FoxDraw Software ............................................................................................. 43
3.4 V7.1 Software Distribution Media Contents ..................................................................... 43
4. Upgrade Considerations .................................................................................................. 45

4.1 Interoperability Issues ........................................................................................................ 45
4.1.1 General ..................................................................................................................... 45
4.1.2 Compound Summary Access (CSA) .......................................................................... 46
4.1.3 Mixed Version Configurations Require Two Commit Diskettes ............................... 46
4.2 I/A Series A2 System Electronic Documentation ............................................................... 46
4.2.1 Hardware Requirements ............................................................................................ 47
4.2.2 Software Requirements .............................................................................................. 47
4.2.3 Uninstalling Previous Versions of Electronic Documentation .................................... 47
4.2.4 Removing Updated Files ........................................................................................... 48
4.2.5 Stopping the I/A Series Documentation Server .......................................................... 48
4.2.6 Uninstalling the I/A Series Electronic Documentation Application ........................... 49
4.2.7 I/A Series A2 System Electronic Documentation (K0173TQ-M) .............................. 49
4.2.7.1 Installing Series A2 System Electronic Documentation 6.5.1-7.1 ....................... 49
4.2.7.2 Starting I/A Series A2 System Electronic Documentation .................................. 50
4.2.7.3 Browsing the User Documentation .................................................................... 51
4.2.7.4 Searching I/A Series A2 System Electronic Documentation ............................... 51
4.2.7.5 Search ................................................................................................................ 52
4.2.7.6 Advanced Search ................................................................................................ 53
5. Installing V7.1 Release Update on 50 Series.................................................................... 55

5.1 Introduction ...................................................................................................................... 55
5.2 Preinstallation Procedures ................................................................................................. 56
5.2.1 Backing Up Hard Disk .............................................................................................. 56
vi
5.2.2 Saving Control Databases (SaveAlls) .......................................................................... 56

5.2.3 Saving Customized Files ............................................................................................ 56
5.2.4 Backing Up CSA Files ............................................................................................... 56
5.3 Software Installation .......................................................................................................... 57
5.3.1 Performing a Release Update to V7.1 ........................................................................ 57
5.3.2 Rebooting Hosted Stations ........................................................................................ 59
5.4 Postinstallation Procedures ................................................................................................ 59
5.4.1 Setting Date and Time .............................................................................................. 59
5.4.2 Restoring CSA ........................................................................................................... 60
5.4.3 Loading Control Station Databases ........................................................................... 60
5.4.3.1 Loading Databases During an On-Line Upgrade ............................................... 60
5.4.3.2 Loading Databases During an Off-Line Upgrade ............................................... 60
5.4.4 Performing EEPROM Updates ................................................................................. 60
5.4.5 Restoring Files ........................................................................................................... 60
5.4.5.1 Day 0 Installation of V7.0 Software Performed ................................................. 61
5.4.5.2 Upgrade from V7.0 Software Performed ........................................................... 61
5.4.6 Backing Up Hard Disks ............................................................................................ 61
5.4.7 Adding to Your Configuration .................................................................................. 61
6. Installing V7.1 Release Update on 70 Series.................................................................... 63

6.1 Introduction ...................................................................................................................... 63
6.2 Preinstallation Procedures ................................................................................................. 64
6.2.2 Saving Control Databases (SaveAlls) (AW) ................................................................ 64
6.2.3 Saving Customized Files ............................................................................................ 65
6.2.4 Backing Up CSA Files ............................................................................................... 65
6.3 Software Installation .......................................................................................................... 65
6.3.1 Performing a Release Update to V7.1 ........................................................................ 65
6.3.1.1 70 Series Software Installation Procedure ........................................................... 65
6.3.2 Rebooting Hosted Stations (AW70 Only) ................................................................. 68
6.4 Postinstallation Procedures ................................................................................................ 68
6.4.1 Setting Date and Time .............................................................................................. 68
6.4.2 Restoring CSA ........................................................................................................... 68
6.4.3 Loading Control Station Databases ........................................................................... 69
6.4.3.1 Loading Databases During an On-Line Upgrade ............................................... 69
6.4.3.2 Loading Databases During an Off-Line Upgrade ............................................... 69
6.4.4 Performing EEPROM Updates ................................................................................. 69
6.4.5 Restoring I/A Series Standard Application Databases and Files .................................. 69
6.4.6 Restoring User Applications and Third-Party Files and Reinstalling Software ........... 70
6.4.8 Reconciling the Configuration .................................................................................. 70
6.4.9 Adding to Your Configuration .................................................................................. 70
7. Operational Recommendations ....................................................................................... 71

7.1 Performing a Block Copy with a DCI Block ..................................................................... 71
7.2 Faceplate Changes ............................................................................................................. 71
7.3 Configuring Ramp Actions in Display Manager ................................................................ 71
7.4 Configuring AIM*Historian Instances for Inactive Tag Names ......................................... 72
vii
7.5 How to Report Problems .................................................................................................. 72

7.5.1 Customer Action Request (CAR) Form and Procedure ............................................. 72
7.5.2 CP Failure Informational Checklist ........................................................................... 73
7.5.3 Gateway (GW), Integrator 30, and Allen-Bradley
Station (ABSTA) Failure Information Checklist ................................................................. 76
7.5.4 Model 51 System Failure Information Checklist ....................................................... 79
7.5.4.1 Printscreen Failure Information Checklist ......................................................... 85
7.5.5 70 Series Failure Information Checklist ..................................................................... 86
8. Enhancements and Problems Resolved ............................................................................ 93

8.1 V7.1 Enhancements .......................................................................................................... 93
8.2 Problems Resolved for V7.1 .............................................................................................. 93
8.2.1 Workstations ............................................................................................................. 93
8.2.1.1 Booting Model 51F/G Workstations Without an Attached
Keyboard (CAR #1004337) .......................................................................................... 93
8.2.1.2 Intelligent Networking with Security Routers (CAR #1001455) ...................... 93
8.2.2 I/O Gates .................................................................................................................. 94
8.2.2.1 I/O Gate Modification (CAR #1004077) ......................................................... 94
8.2.3 Integrated Control Configurator ............................................................................... 94
8.2.3.1 Shrink Function and Workfile Corruption (CAR #992193) ............................. 94
8.2.4 Integrated Control Blocks ......................................................................................... 95
8.2.4.1 Incorrect Sequence Block Operation (CAR #2000043) .................................... 95
8.2.4.2 Non-Connectable REPTIM Parameter (CAR #1000892) ................................ 95
8.2.4.3 Calculation Errors in CALCA (CAR #1001335) .............................................. 95
8.2.4.4 Setting PRIBLK in the CHARC Block (CAR #1001430) ................................ 96
8.2.4.5 Incorrect Reports of Alarm Types (CAR #1001919) ........................................ 96
8.2.4.6 Process Alarm Printing Problems (CAR #1003102) ......................................... 96
8.2.4.7 Accessibility of ACTION in ECB15 (CAR #1001943) .................................... 97
8.2.4.8 CALC/CALCA Block Syntax Verification (CAR #1001636) ............................ 97
8.2.4.9 Accumulation Loss in ACCUM Block (CAR #1002142) ................................. 97
8.2.5 Micro-I/A Station, Dual Ethernet Monitor ............................................................... 98
8.2.5.1 Dual Ethernet Monitor Error Messages (CAR #1002188) ................................ 98
8.2.5.2 Loss of Carrier on Backup Cable (CAR #2000332) .......................................... 98
8.2.5.3 Processing of I/A Series Output Changes in Field Devices (CAR #1002864) ... 99
8.2.6 Object Manager ........................................................................................................ 99
8.2.6.1 om_scanner Memory Violations (CAR #1002790) .......................................... 99
8.2.6.2 Object Manager List Corruption (CAR #1004002) .......................................... 99
8.2.7 Process Summary Report Configurator ..................................................................... 99
8.2.7.1 Process Summary Report Configurator Block In Alarm Reports
(CAR #1002162) ......................................................................................................... 99
8.2.8 Third-Party Software ............................................................................................... 100
8.2.8.1 Bristol Wind/U Shared Library File Correction (CAR #1004123) ................. 100
8.2.9 FBMs ...................................................................................................................... 100
8.2.9.1 SMDH Indication of EEPROM Update Status (FBM221) (CAR #1002048) 100
8.2.9.2 FCM10E Cable Switching and Reporting (CAR #1004216) .......................... 100
8.2.10 Control Stations .................................................................................................... 100
8.2.10.1 End of List Null Pointer Handling (CAR #1003370) ................................... 100
8.2.10.2 Control Processor Memory Corruption (CARs #1003828 and #1003742) .. 101
8.2.10.3 Green-Death State of CP60 (CAR #2000485) ............................................. 101
8.2.11 Integrators ............................................................................................................. 101
8.2.11.1 Integrator 30 Style B Off-Line Diagnostics (CAR #1002524) ...................... 101
viii
8.2.12 Display Manager ................................................................................................... 102

8.2.12.1 Displaying the On-Line Trend Configurator from Display
Manager (CAR #1003660) ......................................................................................... 102
9. Release Features and Configurations ............................................................................. 103

9.1 Version 7.1 System Features, Benefits, and Enhancements .............................................. 103
9.1.1 Virus Checking Solution ......................................................................................... 103
9.1.2 Modbus Communication Interface ......................................................................... 104
9.1.2.1 FBM224 Configuration ................................................................................... 107
9.1.2.2 Configurators .................................................................................................. 108
9.1.3 HART Communication Interface ........................................................................... 111
9.1.3.1 HART FBM Installation ................................................................................. 112
9.1.3.2 HART FBM Configuration ............................................................................. 113
9.1.4 PROFIBUS-DP Communication Interface ............................................................. 113
9.1.4.1 PROFIBUS-DP FBM Installation ................................................................... 114
9.1.4.2 PROFIBUS-DP FBM Configuration .............................................................. 116
9.1.5 FOUNDATION Fieldbus H1 Communication Interface ............................................ 120
9.1.5.1 I/A Series Fieldbus Communication ................................................................ 120
9.1.5.2 Key Features and Benefits ................................................................................ 120
9.1.5.3 FOUNDATION Fieldbus FBM Installation ........................................................ 121
9.1.5.4 FOUNDATION Fieldbus FBM Configuration ................................................... 121
9.1.6 SPECTRUM Migration and Cluster I/O ................................................................ 122
9.1.6.1 SPECTRUM Migration Integrators ................................................................ 122
9.1.6.2 Fieldbus Cluster Input/Output Subsystem ...................................................... 123
9.1.7 Controller Setpoint Limit ........................................................................................ 123
9.2 Supported Configurations ............................................................................................... 124
9.2.1 Nodebus Control Network Example ....................................................................... 124
9.2.2 Ethernet Control Network Example ........................................................................ 126
9.2.3 Other I/A Series A2 Control Network Examples ..................................................... 127
9.2.4 Release Version 7.1 Stations and Applications ......................................................... 127
B.1 Firmware Upgrade .......................................................................................................... 139
B.2 Determining EEPROM Version ..................................................................................... 140
B.3 Performing an EEPROM Update ................................................................................... 140
ix
x
Figures
1-1. Using Installation Procedures to Upgrade to V7.1 ........................................................ 3
1-2. Corrected “Sample Point Calibration Screen” for MI 020-495 ................................... 34
1-3. Corrected Figure 5-106 in B0400FA ........................................................................... 36
5-1. 50 Series Release Update Installation Procedure .......................................................... 55
6-1. 70 Series Release Update Installation Procedure .......................................................... 63
9-1. FBM224 in Typical Modbus Network Configurations ............................................. 105
9-2. DIN Rail Mounted FBM224 .................................................................................... 106
9-3. FBM224 Termination Assembly ............................................................................... 107
9-4. I/A Series Hardware Configurations Supporting the FBM224 Configurator ............. 109
9-5. ECB/Configurator File Relationships ........................................................................ 110
9-6. Configuration Operations ......................................................................................... 111
9-7. HART FBMs used in a Typical Network Configuration ........................................... 112
9-8. FBM223 used in a Basic PROFIBUS-DP Network Configuration ........................... 115
9-9. PROFIBUS-DP Network Expansion Using Repeaters .............................................. 115
9-10. FBM223 used in a Multi-Master Network Configuration ......................................... 116
9-11. I/A Series Hardware Configurations Supporting the FBM223 Configurator ............. 117
9-12. ECB/Configurator File Relationships ........................................................................ 118
9-13. I/A Series Mixed Nodebus/Ethernet Control Network Example Diagram ................. 125
9-14. I/A Series Ethernet Control Network Example Diagram ........................................... 126
xi
B0400QM – Rev A Figures
xii
Tables
2-1. P-Code to 50 Series Station Types Correlation ........................................................... 37
2-2. V7.1 Documents for 50 Series Systems ....................................................................... 37
2-3. V7.1 Solaris Base Workstation Suite ........................................................................... 38
2-4. V7.1 Solaris Visualization Suite ................................................................................... 38
2-5. V7.1 Solaris Engineering Suite .................................................................................... 38
2-6. Version 7.1 Release Update for UNIX CD-ROM (K0195ZJ) ..................................... 39
3-1. V7.1 Documents for 70 Series Systems ....................................................................... 41
3-2. V7.0 Windows XP Base Workstation Suite ................................................................. 42
3-3. V7.1 Windows XP Visualization Suite ........................................................................ 42
3-4. V7.1 Windows XP Engineering Suite .......................................................................... 42
3-5. Version 7.1 Release Update for Windows XP CD-ROM (K0195ZH) ........................ 43
9-1. Modbus Protocol Function Codes ............................................................................ 104
9-2. ECBs and DCI Blocks Used with the FBM224 ......................................................... 107
9-3. FBM220/221 Maximum Configuration Specifications ............................................. 121
9-4. Function Blocks Corresponding to DCI Blocks ........................................................ 122
9-5. Workstations for I/A Series A2 Systems ..................................................................... 127
9-6. Controllers, Gateways, Devices for Systems with Solaris 8 Operating System ............ 128
9-7. Controllers, Gateways, Devices for Systems with Windows XP Operating System .... 129
9-8. Hardware and Software Summary ............................................................................. 130
B-1. EEPROM and Software Revision Levels of Control Stations ..................................... 135
B-2. EEPROM Revision Levels of Communication Stations ............................................ 136
B-3. Miscellaneous EEPROM Revision Levels .................................................................. 136
B-4. Software Versions of 100 Series FBMs (Y Form Factor) ............................................ 137
B-5. Software Versions of 200 Series FBMs (DIN Rail Mounted FBMs) and FCMs ........ 138
xiii
B0400QM – Rev A Tables
xiv
Preface
This document assists you in planning and executing an installation of the I/A Series V7.1 soft-
ware. The document also includes user notes and describes the media, documentation, and proce-
dures required to install your V7.1 system successfully. The enhancements included with V7.1
software are also described. Read all sections before beginning the V7.1 installation process. Infor-
mation contained in this document supersedes information in earlier documents.
This document assumes that you are upgrading from V7.0. If you are upgrading from an earlier
release, you may need to refer to documentation of earlier Version 6 releases to locate conversion
procedures, notes concerning migration to the Version 6.x release, and so forth.
Throughout these release notes, references are made to contacting the Customer Satisfaction
Center (CSC). In the U.S.A., call 1-866-746-6477, e-mail ips.csc@invensys.com or visit
http://www.ips.csc.invensys.com. Outside the U.S.A., contact your local (country) Invensys Foxboro
representative.
NOTE
Whenever you communicate with the CSC about these release notes, mention the
date on the cover and the title of the document. Knowing the date on the cover pre-
vents confusion caused by changed wording, different section numbers, or mis-
matched page numbers in your reference.
50 Series and 70 Series Conventions

Traditional I/A Series naming conventions for workstations and application servers has been to
label operator interface stations as Workstation Processors (WPs), application servers as Applica-
tion Processors (APs), and combined operator and application server stations as Application
Workstations (AWs).
Different generations of UNIX workstations, typically referred to as 50 Series products, have used
a letter suffix to differentiate newer generations of product (for example, 51D and 51E).
Different generations of the Windows based workstations are typically referred to as 70 Series
workstations. Manufacturing data labels on the back of the hardware have manufacturing
Style/Revision codes used to identify minor differences, such as disk size, within a workstation
generation. For both platforms, the AW or WP designation has been used interchangeably to
name the hardware, software and respective licenses associated with a particular workstation.
With this release, new workstation hardware, software, and licenses have separate designations as
follows:
1. Hardware has a Model designation, similar to AW and WP P-Codes, as follows:
♦ Model P79 Workstation for UNIX (newer product that is functionally similar to
the Model 51D)
♦ Model P80 Workstation for UNIX (newer product that is functionally similar to
the Model 51E)
xv
B0400QM – Rev A Preface
♦ Model P92 Workstation for Windows (newer product that is functionally similar
to the P93, P97, P98, and P99).
2. Software licenses for workstations now use an S-code designation for a suite of soft-
ware selections. These new model coded licenses are similar to the hardware P-code
structure instead of the traditional AW, WP, or AP station licenses. The following
suites have selectable software license options and are used in combination on each
workstation:
♦ S01 Base Workstation Suite
♦ S02 Visualization Suite
♦ S03 Engineering Suite.
The new model coded licenses substitute for the old 7-character part numbers of the
former AW and WP licenses, both on Solaris® and Windows.
3. Software media has separate media part numbers and identified by platform and
version.
This new structure provides additional flexibility in hardware software and licensing selections to
better match application requirements. Through appropriate hardware, software, and S-code
license selections, the traditional AW and WP capabilities are still available.
This document includes both newly released products and previous generations of products. Since
both products can coexist in a system, traditional references using earlier naming conventions (for
example, AW, WP, 50 Series, and 70 Series) have been used in many places as a convenient way to
describe product capabilities that transcend the new naming conventions. Note however that
where this occurs for the new workstations listed above, the new product structure is implied. The
following subsections contain specifics of the naming conventions for this document.
Naming Conventions for UNIX Workstations

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

Where reference is made to the 70 Series, the information applies to all styles of 70 Series stations,
including the new Model 70P workstations.
The Model 70P workstation is also designated the “P92” workstation in user documentation asso-
ciated with this release. “Model 70P” (or “the P92”) workstation can refer to either the AW with
or without control, or WP capability, unless explicitly specified as an AW70P or AW70CP (where
the “CP” notation refers to the Model 70P workstation with control capability).
xvi
Preface B0400QM – Rev A
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
(K0173TQ), but the CD-ROM may not contain the latest revision of the documents. For the lat-
est revisions of the documents, refer to the Customer Satisfaction Center’s webpage
http://ips.csc.invensys.com.
Document Title Part Number

Application Workstation 70 with Allen-Bradley® PLCs (Windows® B0400AL
Operating System)
Color Printer Installation for V4.3.x, V6.1.x, V6.2.x, V6.3, V6.4, V6.5, and B0400SF
V7.0
Command Center™ Installation Manual B0193RZ
Control Network Architecture PSS 21H-7C1-B3
Control Processor 60 (CP60) Sizing Guidelines and Excel Workbook B0400BK
DCS Fieldbus Modules for Bailey® NET90 and INIFI90 Systems User’s Guide B0193XG
DCS Fieldbus Modules for Fisher PROVOX Series 10 Systems User’s Guide B0193WV
DCS Fieldbus Modules for Fisher PROVOX Series 20 Systems User’s Guide B0193YV
DCS Fieldbus Modules for Fisher® PROVOX® Controller Series Systems B0400AR
User’s Guide
DCS Fieldbus Modules for Honeywell® TDC 3000 Systems User’s Guide B0193YW
Device Integration Using I/O Gates B0193VG
DIN Rail Mounted FBM Equipment, Agency Certifications PSS 21H-2W2 B3
DIN Rail Mounted FBM Subsystem Overview PSS 21H-2W1 B3
DIN Rail Mounted FBM Subsystem User’s Guide B0400FA
Dual-Height Modular Mounting Structure (2xMMS) Mounting Hardware B0400PA
Installation
Field Automation Subsystem Micro-I/A® Station User’s Guide B0193VJ
Fieldbus Cluster I/O User’s Guide B0193RB
Flat Panel Monitor Software Setup for UNIX and Windows Workstations B0193PL
FoxCAE™ 5.0 Release Notes B0400PY
FoxDraw™ Software B0193WG
FoxView and FoxDraw V9.0 Release Notes B0193WL
FoxView™ Software B0193WH
Hardware and Software Specific Instructions for 70 Series Processors B0400PU
(Enterprise Pentium® II)
Hardware and Software Specific Instructions for 70 Series Processors B0400SA
(GX1 Pentium II) AW70A (P99*P), WP70 (P98*M), and AW70B (P97*H)
Hardware and Software Specific Instructions for 70 Series Processors B0400RC
(GX1 Pentium III) AW70A (P99*Q), WP70 (P98*N) and AW70B (P97*J)
xvii

Hardware and Software Specific Instructions for 70 Series Processors B0400SK
(GX1 Pentium III) AW70A (P99*R), WP70 (P98*P) and AW70B (P97*K)
Hardware and Software Specific Instructions for 70 Series Processors B0400RH
(GX1 Pentium III) AW70A (P99*S), WP70 (P98*Q) and AW70B (P97*K)
Hardware and Software Specific Instructions for 70 Series Processors B0400RL
(GX1 Pentium III) AW70A (P99*T), WP70 (P98*R) and AW70B (P97*L)
Hardware and Software Specific Instructions for 70 Series Processors B0400RR
(GX200 Pentium III) AW70A (P99*U), WP70 (P98*S) and AW70B (P97*M)
Hardware and Software Specific Instructions for 70 Series Processors B0400PV
(GXA Pentium II) AW70A (P99*N), WP70 (P98*L), and AW70B (P97*G)
Hardware and Software Specific Instructions for Model P92*A Workstation B0400HD
(PW340)
Hardware and Software Specific Instructions for Model P95*B (PE2500, B0400RX
Windows NT Server 4.0 Terminal Server Edition)
Hardware and Software Specific Instructions for Server 70 Processor (PE2400) B0400SP
AW70C and WP70C (P95*A)
Hardware and Software Specific Instructions Workstation P93*A (GX240) B0400RU
Hardware Installation Procedures for Model P79 Workstation (Solaris 8 B0400SR
Operating System)
Hardware Installation Procedures for Model P80 Workstation (Solaris 8 B0400SS
Operating System)
HART® Communication Interface Modules (FBM214/215/216/218) B0400FF
User’s Guide
I/A Series A2™ Control Network User’s Guide B0400DV
Information Suite AIM*Historian™ User’s Guide B0193YL
Installation Instructions for A to L Size Modules B0193TF
Integrated Control Block Descriptions B0193AX
Integrated Control Concepts B0193AW
Integrated Control Configurator B0193AV
Micro-I/A Station Hardware Installation Quick Set-Up Guide B0199AB
Modbus Communications Interface Module (FBM224) User’s Guide B0400FK
Modbus® Communication Interface Module (FBM224) PSS 21H-2Z24 B4
Model P79 Workstation for UNIX Solaris 8 Operating System PSS 21H-4R7 B4
Model P80 Workstation for UNIX Solaris 8 Operating System PSS 21H-4R8 B4
Model P92 Workstation for Windows (Windows XP Operating System) PSS 21H-4D13 B4
Modular Industrial Console Installation B0193UV
Modular Industrial Workstation Installation B0193CE
Nodebus/Control Network Interface (NCNI) PSS 21H-7B5 B4
On-Line Upgrade B0193RE
On-Line Upgrade Read Me First B0193VN
xviii
Preface B0400QM – Rev A

Process Operations and Displays B0193MM
PROFIBUS-DP™ Communication Interface Module (FBM223) User’s Guide B0400FE
Redundant Control Network Interface (RCNI) PSS 21H-7B6 B4
Server 70 and Model P95 System Administration Guide (Windows NT B0400AS
Server 4.0, Terminal Server Edition)
Site Planning B0193AB
Software Installation (Solaris® Platform) B0193JG
Software Installation (Windows NT Operating System) B0400JG
SPECTRUM™ Migration Integrator User’s Guide B0193RC
System Administration Guide (Solaris 8 Operating System) B0400DU
System Administration Guide (Windows NT Operating System) B0400ND
System Administration Guide (Windows XP Operating System) B0400HE
System Administration Guide for 50 Series Systems (Solaris 2.X) B0193ND
System Definition 2.4.1 Release Notes B0193XW
System Definition: A Step-By-Step Procedure B0193WQ
System Equipment Installation B0193AC
System Maintenance B0193AD
System Management Displays B0193JC
System Planning and Sizing B0193BF
UNIX and Windows Workstations Instructions for MIC, MIW, IEMFA/IEMFR B0400PL
(ME24/32) and IE32 Installation
V6.4 Read Me First B0400CU
V6.4 Upgrade Considerations B0400CZ
V7.0 Enhancements and Problems Resolved B0400QF
V7.0 Installation Procedures B0400QE
V7.0 Operational Recommendations B0400QG
V7.0 Read Me First B0400QC
V7.0 Release Features and Configurations B0400QH
V7.0 Upgrade Considerations B0400QD
Redundant Array of Independent Disks (RAID1 and RAID5) Installation B0193XU
Instructions 1
Winchester Systems FlashDisk® RAID 1 and RAID 5 Instructions B0193RT
1.
This document describes the Artecon/Dot Hill RAID hardware.
xix
xx
1. Read Me First
This chapter contains an overview of the V7.1 release, including an installation overview,
upgrading information, compatibility issues, System Definition information, I/A Series
Electronic Documentation content, and V7.1 User Notes.
1.1 Release Overview

Release 7.1 provides support for the following:
♦ Windows workstations (P92)
♦ UNIX workstations (P79 and P80)
♦ High-speed networking.
For details, see V7.0 Release Features and Configurations (B0400QH) and Chapter 8 “Enhance-
ments and Problems Resolved”.
The I/A Series V7.1 software updates your V7.0 system to V7.1. V7.1 software can be installed
on the Model 51F (P79), Model 51G (P80), and Model 70P (P92) workstations, and these V7.1
workstations can interoperate with existing V6.3, V6.4, V6.5, and V7.0 workstations in your
system.
NOTE
I/A Series V7.1 supports only the V6.2.5 Micro-I/A control image.
Using the new software S-Model codes, the Model 51F (P79) workstation platform can be config-
ured for the following four software images:
♦ Application Processor 51, Style F (AP51F)
♦ Workstation Processor 51, Style F (WP51F)
♦ Application Workstation 51, Style F (AW51F)
♦ Application Workstation 51, Style F, with control capability (AW51FX).
NOTE
The Model 51F workstation with AP functionality is still supported with this
release; however, the VT100 console is not supported. An AP51F must have a
mouse, keyboard, and monitor directly connected.
Using the new software S-Model codes, the Model 51G (P80) workstation platform can be con-
figured only for the following two software images:
♦ Application Workstation 51, Style G (AW51G)
♦ Application Workstation 51, Style G, with control capability (AW51GX).
1
B0400QM – Rev A 1. Read Me First
Using the new software S-Model codes, the Model 70P (P92) workstation platform can be config-
ured for the following three software images:
♦ Workstation Processor 70, Style P (WP70P)
♦ Application Workstation 70, Style P (AW70P)
♦ Application Workstation 70, Style P, with control (AW70CP).
The I/A Series V7.1 software is a release update installation, and can only be installed on Invensys
Foxboro Model 51F (P79), Model 51G (P80), and Model 70P (P92) stations. V7.0 Upgrade
Considerations (B0400QD) addresses minimum hardware requirements for new and existing
stations.
The V7.1 release includes the same control software images released with V6.5.1.
NOTE
No support for disk mirroring, disk concatenation, or OFHA is included with the
P79, P80, or P92 workstations.
1.1.1 Installation Overview

It is mandatory that you have performed a Day 0 upgrade to V7.0 before performing the release
update to V7.1. V7.0 Installation Procedures (B0400QE) describes the installation of V7.0 soft-
ware into a new station. Detailed instructions support you in installing I/A Series V7.0 software
and preparing for operation. An overview of the steps follows.
1. Assemble the documents and media required.
2. Connect the system as applicable, using the layout shown in the applicable instruction
document(s).
3. Generate a Commit diskette using System Definition on a Windows XP station.
4. Install I/A Series software in your system’s station(s) using V7.0 Installation Procedures
(B0400QE).
5. Configure your specific control, user interface displays, and support processes.
6. Begin operation.
Refer to the flow chart, Figure 1-1, for the upgrade path.
2
1. Read Me First B0400QM – Rev A
Read Chapter 8
Start and Chapter 9
V7.0
Yes Software
Installed
?
No
Install I/A Series Refer to V7.0 Installation

V7.0 Software Procedures (B0400QE)
Review Remainder of
Chapter 1 “Read Me First”
Review V7.1 Kits in

Chapter 2 or Chapter 3
Time Estimation V7.0 Upgrade Considerations

Refer to Chapter 4 (B0400QD):
“Upgrade Considerations” Hardware Requirements Read Appendix A
Read Chapter 3 or 4
Back Up/Restore Refer to Appendix A “Files to

Install Software Using Back Up/Restore”
Chapter 5 or Chapter 6 EEPROM Update Refer to Appendix B
“EEPROM Revision Levels”
Yes Another
Station
?
No
Review Chapter 7
“Operational
Recommendations”
End
Figure 1-1. Using Installation Procedures to Upgrade to V7.1
For specific outlines of installation procedures for 50 Series or 70 Series stations, refer to
Figure 5-1 or Figure 6-1, as applicable.
3
1.1.2 Upgrades
To upgrade to V7.1, you must be at V7.0. Thoroughly review this document and V7.0 Upgrade
Considerations (B0400QD) for detailed upgrade considerations prior to beginning the upgrade.
The information can help you make major decisions, such as how to minimize the impact of soft-
ware compatibility issues, and how to perform the appropriate preinstallation, installation and
postinstallation steps. When in doubt regarding any part of the upgrade, contact the Customer
Satisfaction Center at the numbers listed on page xv.
When preparing to install V7.1on a V7.0 station, refer to “Chapter 5 “Installing V7.1 Release
Update on 50 Series” for UNIX installation and to Chapter 6 “Installing V7.1 Release Update on
70 Series” for Windows XP installation.
1.1.3 On-Line Upgrade

If you are planning an On-Line Upgrade, you must first determine if your plant is a suitable can-
didate for an On-Line Upgrade and evaluate the risks involved in performing an On-Line
Upgrade to another version of control software. Review the following documents:
♦ On-Line Upgrade Read Me First (B0193VN)
♦ On-Line Upgrade (B0193RE).
To ensure a successful upgrade, your plant must meet all requirements in each of these docu-
ments, in addition to the requirements listed in this section.
! CAUTION
Use caution when performing an On-Line Upgrade. If you have any questions or
concerns about the On-Line Upgrade procedures and the impact on your process,
contact the Customer Satisfaction Center at 1-866-746-6477.
Review the following constraints when planning the On-Line Upgrade of stations to V7.1
software.
1. You must meet all requirements described in the following documents:
♦ On-Line Upgrade (B0193RE).
2. Your host processor must be at I/A Series V7.0.
3. It is not recommended that you use the On-Line Upgrade procedures for systems with
FOUNDATION™ fieldbus devices. However, if you do decide to perform an On-Line
Upgrade, all FBM220s and FBM221s hosted by CP60 must be updated to Version
2.12 before beginning the upgrade.
4. You cannot use the On-Line Upgrade procedures for systems with PROFIBUS-DP
devices.
4
! CAUTION
It is extremely important that you contact the Customer Satisfaction Center (CSC)
before starting the On-Line Upgrade procedures if:
1. The On-Line Upgrade involves HART devices.
2. The On-Line Upgrade involves FOUNDATION™ fieldbus devices
3. The On-Line Upgrade involves PROFIBUS-DP devices.
Refer to “On-Line Upgrade” on page 16 for additional recommendations, notes, and consider-
ations relating to On-Line Upgrade process. Review each note carefully to determine its impact
on your process.
The following are supported with this version of On-Line Upgrade:
♦ Host Stations:
♦ 50 Series hosts (AP and AW)
♦ 70 Series hosts (AW70).
♦ Control Stations:
♦ CP10
♦ CP30 (Styles A and B)
♦ CP40 (Styles A and B)
♦ CP60
♦ Integrator 30 for Allen-Bradley (AB30) (Styles A and B)
♦ Integrator 30 for Modicon (MG30) (Styles A and B).
1.1.4 Bootless Control Station Upgrade Procedure Not Available

The Bootless Control Station Upgrade procedure was made available for Y2K upgrades to allow
upgrades of host software without booting the control stations. Due to differences in the structure
of control-related files between releases, the Bootless Control Station Upgrade procedures must
not be used during upgrades to I/A Series Version 7.1.
1.1.5 FBM and Communication Modules EEPROM Updates

Required
Fieldbus Communications Modules (FCMs), FBI10E modules, and DIN rail mounted FBMs
require an EEPROM update. See the Appendix B “EEPROM Revision Levels” for EEPROM ver-
sion information.
1.1.6 Micro-I/A Station EEPROM Update Required

The Micro-I/A Type 1 station requires an EEPROM update from the System Management dis-
plays after the new software has been installed. See Appendix B “EEPROM Revision Levels” for
Micro-I/A station EEPROM version information.
5
1.1.7 Upgrade and Compatibility Issues

During the Day 0 upgrade to V7.0, or the release update from V7.0 to V7.1, some compatibility
issues may exist. For information concerning Carrierband LAN I/F, Compound Summary Access
(CSA), Device Monitor, and so forth, see “Interoperability Issues” in V7.0 Upgrade
Considerations (B0400QD) and “Interoperability Issues” on page 45.
1.1.8 System Definition 2.4.1

For Version 7.1, you must use System Definition V2.4.1 to create, import, and/or edit your con-
figuration, and to create a Commit diskette.
All Commit diskettes must be produced using the Day 0 version of Media Distribution diskettes.
Media Distribution diskettes distributed for release updates cannot be used to produce Commit
diskettes.
Mixed version systems require a separate Commit diskette for use on V7.X and V6.4/V6.5.X
stations. Use:
♦ The V7.0 Media Distribution Diskette (K0175YP) supplied with V7.0 media kits to
produce a Commit diskette for use on V7.0 or V7.1 stations
♦ The V6.4 Media Distribution Diskette (K0175XE) supplied with V6.4 media kits to
produce a Commit diskette for use on V6.4, V6.5, or V6.5.1 stations.
NOTE
1. Commit diskettes for use on V7.1 stations are only required when you are adding
new equipment and/or making changes to your system configuration.
2. For mixed version systems, be sure to label each Commit diskette with the
I/A Series versions on which it can be used, for example, V7.0/V7.1.
For Day 0 installations, 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.
See System Definition 2.4.1 Release Notes (B0193XW) for instructions on installing and upgrading
to System Definition V2.4.1, features, problems resolved, and for references to supporting
documentation. For information on using System Definition 2.4.1, refer to System Definition: A
Step-By-Step Procedure (B0193WQ) and System Definition on-line Help.
1.1.9 FoxView V9.0 Software

If you want the FoxView package, you must separately purchase and install FoxView 9.0 software.
The FoxView and FoxDraw software packages are not included on the V7.0 Windows XP or
Solaris 8.0 Day 0 CD-ROM or the V7.1 Windows XP or Solaris 8.0 Release Update CD-ROMs;
you must install these packages from the FoxView/FoxDraw 9.0 CD-ROM. Refer to Table 2-4
and Table 3-3 for information on the FoxView/FoxDraw 9.0 kits.
1.1.10 I/A Series Electronic Documentation CD-ROM

The I/A Series A2 System Electronic Documentation CD-ROM for Windows NT 4.0, and
Windows 95/98/2000/XP contains I/A Series system user documentation for UNIX and
Windows platforms (.pdf files), control station sizing spreadsheets (.xls files), and on-line Help
files (.hlp files) not available from their applications.
6
I/A Series Version 7.1 documentation is available K0173TQ-M. For installation instructions, see
“I/A Series A2 System Electronic Documentation (K0173TQ-M)” on page 49.
1.2 User Notes for V7.1 I/A Series A2 Software

The following subsections are user notes for the V7.1 I/A Series software release.
1.2.1 Software Installation

1.2.1.1 V7.1 Release Update Procedures for Windows XP Workstations
with AIM*AT Installed
Before beginning the release update process from V7.0 to V7.1 on a Windows XP workstation
that has AIM * software suite components installed, you must properly shut down the AIM pro-
cesses that are running. Perform the following steps to properly shut down the AIM processes on
the workstation:
1. If you have not done so already, complete Step 1 of “70 Series Software Installation
Procedure” on page 65 of this document.
2. Close all AIM client application programs that may be open, such as Data Link,
Inform, Histspy, MDE Editor, and so forth.
3. From the Windows XP desktop click Start > Settings > Control Panel. Double-
click AIM*AT from the Control Panel. The AIM*AT dialog box appears, and may have
up to three tabbed pages for controlling AIM*AT server programs.
4. Select the AIM*SPC tab, click the StopAIM*SPC button, and uncheck the box labeled
Run AIM* SPC at system startup.
5. Select the AIM* Historian tab and click the Start AIM* Historian Manager button.
Close all AIM* Historian instances and their remote collectors using the AIM* Histo-
rian Manager window (refer to the chapter titled “AIM Historian Operation” in AIM*
Historian User’s Guide [B0193YL] for detailed instructions). Close the AIM* Histo-
rian Manager window.
6. Select the AIM*API Control tab, click the Stop AIM* API button, and uncheck the
box labeled Check to start AIM* API at boot.
7. Complete Step 2 of “70 Series Software Installation Procedure” on page 65.
8. If AIM* export to Oracle is installed on the system, shut down histexport and hist-
move by opening DOS prompt and typing the following:
d:
cd \opt\aim\bin
histexport -stop
histmove -stop
9. Proceed with Step 3 of “70 Series Software Installation Procedure” on page 65.
1.2.1.2 Day 1 Commit Diskette Issues

The Version 7.1 Windows XP and Solaris 8 Day 1 Commit diskettes exhibit the following
problems:
♦ You cannot add a parallel or direct-connected serial printer; they do not appear in
SMDH or the Control Panel.
7
♦ You cannot move a station from one boot host or System Monitor to another.
1.2.2 Windows XP Operating System

Model P92 workstations provide the hardware platform running the Microsoft® Windows XP
operating system on which the I/A Series Software Releases 7.0 and 7.1 can be installed. Shipped
with each Model P92 Workstation are two documents that contain important and useful infor-
mation. You should familiarize yourself with these documents:
♦ Hardware and Software Specific Instructions for Model P92*A Workstation (PW340)
(B0400HD)
♦ System Administration Guide (Windows XP Operating System) (B0400HE).
In addition to these documents, the following subsections provide recommendations, notes, and
considerations relating to the Windows XP operating system that you may find useful.
1.2.2.1 Windows XP System Recovery Techniques

There are several recovery techniques that you can use in the event that you encounter system
problems on a workstation running the Windows XP operating system. The Windows XP resto-
ration features allow you to roll back device drivers, boot up into one of several safe modes, or per-
form other system recovery techniques if your system requires some restoration.
System Restore, in particular, is a very powerful tool that uses “restore points” to return your com-
puter to an earlier time, consequently restoring your system’s settings and performance. For exam-
ple, if you suspect that a file is corrupted (such as might happen if the workstation is not on a
UPS when a power glitch occurs), you can use the Windows XP System Restore utility to recover
from that type of a failure.
For complete details on the different methods of system recovery, refer to the chapter titled
“System Recovery Techniques” in System Administration Guide (Windows XP Operating System)
(B0400HE).
1.2.2.2 Minimizing and Restoring Applications from the Task Bar

Using the Windows XP task bar to minimize and restore applications such as Operator Action
Journal may cause an error message to appear in a command tool window.
If you leave the error message window open and ignore it, the application functions normally, but
if you close the window by clicking the Close (X) button in the top right-hand corner of the win-
dow, the application exits.
1.2.2.3 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.
1.2.2.4 Customizing Autologon for Stations Running I/A Series Software

and the Windows XP Operating System
If you want the I/A Series workstation to automatically boot up into an account other than the
default I/A Series system Fox account, you can create a registry entry to specify a different user
account and password. Refer to System Administration Guide (Windows XP Operating System)
(B0400HE) for instructions.
8
1.2.2.5 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).
1.2.2.6 Reducing Network Traffic by Stopping Windows XP Services

To reduce the amount of unnecessary IP traffic on the I/A Series network, several services that are
normally running on the Windows XP workstation are turned off on P92 workstations. For
example, the “Computer Browser” and “Messenger” services are two such services that are dis-
abled. For more information, refer to System Administration Guide (Windows XP Operating System)
(B0400HE).
1.2.2.7 Changing the Subnet Mask to Communicate with a Network

Switch
For Model P92 Workstations, the subnet mask for the network interface card that is selected dur-
ing the I/A Series Software Installation is set to 255.255.224.0. This mask allows communica-
tions between I/A Series stations but does not allow communication with the network switches
themselves.
In order to communicate directly with the switches (for example, to ping them), the subnet mask
should be changed to 255.255.0.0. Change the subnet mask by right clicking on the My Network
Places icon on the desktop and selecting Properties. When the “Network Connections” win-
dows comes up, right click on the Local Area Connection that is connected to the I/A Series net-
work and select Properties. From the “General” tab, select Internet Protocol (TCP/IP) and
click on the Properties button, and the “Internet Protocol (TCP/IP) Properties” window opens.
Change the subnet mask in this window.
1.2.2.8 CPU-Intensive Applications May Cause Sluggish Performance

It is possible that certain CPU-intensive applications which are not optimally-written for the
Windows XP platform (for example, some legacy applications) may cause the CPU load to go to,
or approach 100% for an extended period of time. This can delay the execution of other software
applications, display updates, and so forth.
To prevent this from happening, such CPU-intensive applications can be run at a lower priority.
You can lower the priority of these applications by using the start /belownormal feature in a
command prompt window.
For example:
start /belownormal cmd.exe /c “compress myfile”
or
start /belownormal cmd.exe /c myscript.cmd
or
start /belownormal cmd.exe /c “sh <scriptfile>”
where <scriptfile> is the name of a script file that contains UNIX like shell commands.
9
1.2.3 Solaris 8 Operating System

P79 and P80 workstations provide the hardware platform running the Solaris 8 operating system
on which the I/A Series Software Releases 7.0 and V7.1 can be installed. Shipped with each
Model P79/80 Workstation are documents that contain important and useful information. You
should familiarize yourself with these documents:
♦ Hardware Installation Procedures for Model P79 Workstation (Solaris 8 Operating
System) (B0400SS)
♦ Hardware Installation Procedures for Model P80 Workstation (Solaris 8 Operating
System) (B0400SR)
♦ System Administration Guide (Solaris 8 Operating System) (B0400DU).
In addition to these documents, the following subsections provide recommendations, notes, and
considerations relating to the Solaris 8 operating system that you may find useful.
1.2.3.1 Booting into OpenWindows Without Mouse and Keyboard

Booting into OpenWindows without the mouse or keyboard attached to the system requires con-
figuration of the “OWconfig” file. The “null_kbd” script in the “/usr/openwin/server/etc” direc-
tory is provided to enable or disable the mouse and keyboard facilities on the workstation.
Running the “null_kbd” script informs you of the current configured state and asks if you desire a
change. The following examples show a disabling and then enabling of the mouse and keyboard
via the “null_kbd” script.
X2AW5D# cd /usr/openwin/server/etc
X2AW5D# null_kbd
Solaris 8 keyboard/mouse enable/disable script.
Keyboard currently enabled, Disable y/n ?
y
Keyboard has been disabled.
Setting input-device and output-device to ttyb.
Mouse currently enabled, Disable y/n ?
y
Mouse has been disabled.
X2AW5D# null_kbd
Solaris 8 keyboard/mouse enable/disable script.
Keyboard currently disabled, Enable y/n ?
y
Keyboard has been enabled.
Setting input-device to keyboard and output-device to screen.
Mouse currently disabled, Enable y/n ?
y
Mouse has been enabled.
1.2.3.2 tr Command
The tr command functions differently on the Solaris 8 operating system. Scripts that use this
command must be reviewed and modified if necessary to be compatible with pre Solaris 8. This is
10
an upgrade issue to application scripts that use tr to strip out brackets on OM get calls of string
variables. Another alternative is to use /usr/ucb/tr.
1.2.3.3 Using the “prune” Option with the “find” Command

The “find” command can produce errors when traversing the /proc filesystem. If a local process
has opened a remote file over an rmount, “find” can prematurely abort and/or produce error mes-
sages such as “Transport endpoint is not connected” and/or “Operation not supported”
when it examines the file descriptor.
To avoid this problem, you must use the “prune” option within the “find” command so that the
file descriptors in /proc/*/fd are not examined. For example, instead of using the following simple
“find” command to look for core files:
find / -name core
You could use the following “find” command which utilizes the “prune” option:
find / -type d -name fd -prune -o name core
(Note that this “find” does not descend into any directory named “fd”.)
1.2.3.4 Letterbug Mapper Running on Solaris 8

The “Show number of OMC’s requesting a letterbug” field on the Letterbug Mapper display
does not update. This field remains 0 when a rebooting Micro-I/A station (green/red led blinking)
is requesting its Letterbug. To determine that a Micro-I/A station is requesting its letterbug, per-
form one of the following steps:
1. Observe the Micro-I/A station that is rebooting. If both red/green LEDs remain
blinking once per second, the Micro-I/A station is trying to request its letterbug from
the Letterbug Server.
2. Observe the Letterbug Display. If the booting Micro-I/A station letterbug is not
present in this display, then the Micro-I/A station remains in the request Letterbug
state (flashing red/green). The letterbug must be assigned to allow the boot to
complete.
3. To assign a letterbug to the Micro-I/A station, follow the instructions in the Field
Automation Subsystem Micro-I/A Station User’s Guide (B0193VJ).
1.2.4 Workstations
1.2.4.1 Sun Workstation Dot-Matrix Printer Connections
Do not connect a dot-matrix printer to a parallel port on a Sun® workstation; this configuration
is not allowed. However, you can connect a dot-matrix printer to a serial port on a Sun
workstation.
1.2.4.2 Configuring PCL3 Printers on an I/A Series UNIX Workstation

When using the K0173UW diskette on an I/A Series UNIX workstation to run scripts and make
manual changes to your printer configuration files, you are prompted to enter an I/A Series soft-
ware version number. If you are at V7.1 or V6.5.1, enter the previous I/A Series version release
number. Enter “7.0” if you are at I/A Series V7.1, and enter “6.4” or “6.5” if you are at I/A Series
V6.5.1.
11
1.2.4.3 Annunciator Horns on WP70C (CAR #1002783)

When a process alarm is sent to a Server 70 configured as a WP (WP70C), you need to acknowl-
edge the alarm horn on both annunciator keyboards; that is, you must ACK twice. However, after
using the ACK buttons one at a time, the horn is no longer activated if a new alarm occurs.
To avoid this, reconfigure the WP70C to an AW70C. AW70Cs do not exhibit this problem.
1.2.4.4 Starting a Workstation with McAfee VirusScan Enterprise 7.0 and

NutCRACKER
Depending on the workstation configuration and the I/A Series platform model, there may be a
startup contention between McAfee VirusScan Enterprise 7.0 and NutCRACKER, causing a
Dr. Watson error to appear. If this problem occurs, restart the system by powering it off then on.
1.2.4.5 Communication Processor 10 (COMM10) Resource Issue

Due to the higher loads allowed with the new V7.0 network, you may encounter a resource issue
if you are using a COMM10 for printers. The COMM10 processor displays red in System Man-
agement and a “No Short Term Reports for that station” message is reported by System Monitor.
To avoid this issue, rehost the printer that is currently using the COMM10 to a workstation pro-
cessor (WP). Rehosting the printer involves reconfiguring the system using System Definition and
recommiting all workstations
1.2.4.6 Running Exceed Applications on a Multi-Headed Workstation

On multi-headed Windows XP I/A Series workstations, applications that are displayed in an
Exceed window (such windows have an “X” at the left edge of the title bar) can only be run on the
primary head where their initial windows are displayed. These applications (for example, SMDH,
Integrated Control Configurator, Operator Action Journal, and Process Summary Report) cannot
be moved and run on any other than the primary head.
1.2.4.7 P92 Workstations

1.2.4.7.1 Performing Day 1 Procedures Using Revision B of V7.0 Day 0 CD-ROM
If you want to change your system configuration, for example if you want to add, remove, or
rehost control stations, you must use Revision B of V7.0 P92 Workstation Redundant Network
Windows XP Day 0 CD-ROM (K0175YS-B) or V7.0 P92 Workstation Non-Redundant Net-
work Windows XP Day 0 CD-ROM (K0175YW-B).
NOTE
You do not need to perform a Day 0 installation on your workstation using this
CD-ROM; you simply need to insert Revision B of the CD-ROM when prompted
during Day 1 procedures.
If you use Revision A of either of these V7.0 Windows XP Day 0 CD-ROMs for Day 1 proce-
dures, Day 1 installations will fail, the workstation will not recover and will then require a Day 0
installation.
12
1.2.4.7.2 Configuring a Windows XP Workstation as Stand-Alone

When you configure a Model P92 workstation as a stand-alone station (such as an AW70CP not
connected to a network), the I/A Series software installation process still prompts you to select a
network adapter to use with I/A Series software. When the Network Installation dialog box
appears and you are prompted to select a network adapter, select the Microsoft Loopback
Adapter if this station is to be a stand-alone station.
1.2.4.7.3 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 a
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
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 the 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.
1.2.4.7.4 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.
13
1.2.4.8 P79 and P80 Workstations

1.2.4.8.1 Remotely Logging into an ia Account on a WP51G or AW51G Workstation
Model 51F and 51G workstations do not support remote login under the “ia” account. To work
around this problem, modify the mode attributes of the blink_task executable as follows. From a
command tool, type:
cd /usr/fox/wp/bin
chmod +s blink_task
This modification is not required when remotely logging in under the “root” account.
1.2.4.8.2 System Utilities Reporting Incorrect Station Type

The Model 51F (P79) workstation is a Sun Blade 150, but system utilities like “uname” report
that the workstation is a Sun Blade 100. This issue has no functional bearing.
A similar problem exists for the Model 51G (P80) workstation, which is a Sun Blade™ 2000.
System utilities report “Sun Blade 1000”. Again, this issue has no functional bearing.
1.2.4.8.3 Installing V7.0 on P79 and P80 Workstations with an External

Hard Drive
You cannot perform a Day 0 installation on a Model 51F/G workstation with an internal drive
when an external drive is connected. If any external drives are to be concatenated to an internal
system drive, they must be disconnected during the Day 0 installation. The only external System
drive that is supported is RAID.
1.2.4.8.4 Ejecting a CD-ROM

The eject command does not work as it has in the past; the alias “cdrom” is not recognized. The
command “eject cdrom” does not work on the AW51F.
You must either eject the CD-ROM manually or type the following to eject the CD-ROM:
# eject /dev/rdsk/c0t1d0s0
or
# eject /dev/sr0
1.2.4.8.5 Plugging in a USB Mouse and/or Keyboard

After unplugging a USB mouse or keyboard from a workstation with GCIO, make sure to plug
the mouse or keyboard back into the same port. Hotplugging into a new port can cause a loss of
mouse and/or keyboard functionality until the station is rebooted.
If the GCIO station’s keyboard or mouse is connected through a USB hub, do not unplug the
keyboard, mouse, or hub. Even when the devices are hotplugged back into their original ports,
there will still be a loss of mouse and/or keyboard functionality until the station is rebooted.
1.2.4.8.6 Swapping Pointing Devices

If you want to swap pointing devices (for example, replace a mouse with a trackball) on a P79
workstation with GCIO, you must shut your workstation down first, switch the devices, and then
power your workstation back up. The pointing device works correctly after reboot.
14
1.2.4.8.7 Turning Off Serial Printers Directly Connected to the P79 Workstation
If a serial printer directly connected to an AP51F or AW51F is turned off, it takes up to one
minute for SMDH, lpstat, Device Monitor, and System Monitor to indicate that the printer has
been turned off. If the printer is turned back on, these subsystems do not detect that the printer
has been turned back on; they report that the printer is failed.
To correct this problem, you must reboot the workstation.
1.2.4.8.8 Printer Issue with P80 Workstations Using Parallel Extender Cables
Printers connected to P80 workstations with parallel extender cables do not print correctly.
To work around this issue, you must change the “fast-centronics” parameter value in the /ker-
nel/drv/ecpp.conf file to “true”. To change this parameter on a P80 workstation that is using the
parallel extender cable for a printer connection, perform the following:
1. Open the “/kernel/drv/ecpp.conf ” file using the vi editor.
2. Change the line that reads:
fast-centronics=”false”;
to:
fast-centronics=”true”;
1.2.5 I/O Gates

1.2.5.1 gpgate.dll Requirement for I/O Gates
In order for any I/O Gate products to operate properly with V6.5.1 or V7.1 I/A Series software,
Version 1.8 of the file “gpgate.dll” is required. This file ships with the various I/O Gate driver
packages or is available via QuickFix #1004077B.
To determine the version of gpgate.dll on the system, browse to d:\opt\diw\iogates\[driver
package]\bin. Select the gpgate.dll file (or GPGateD.dll if it is an OPC IOGate product), right-
click Properties, and pick the Version tab.
If “File Version” is not 1.8.0.0, install QuickFix #1004077B which is available on the Customer
Satisfaction Center’s website.
1.2.6 Video Display

1.2.6.1 Flat-Screen Monitor Setup
Refer to Revision D of Flat Panel Monitor Software Setup for UNIX and Window Workstations
(B0193PL) for proper setup of flat-screen monitors.
1.2.7 FoxGuard Manager

1.2.7.1 FoxGuard Manager I/O Card Alarming
FoxGuard Manager I/O cards are sending alarm messages to the system printer, even when alarm-
ing is inhibited for these cards in the ECB.
15
1.2.8 On-Line Upgrade

This section assumes that in preparation for an On-Line Upgrade, you have read On-Line Upgrade
Read Me First (B0193VN), On-Line Upgrade (B0193RE), and “On-Line Upgrade” on page 4.
The following subsections provide additional recommendations, notes, and considerations relat-
ing to On-Line Upgrade process. Review each note carefully to determine its impact on your
process.
1.2.8.1 Transition of CP60 Blocks to Manual Mode

During the On-Line Upgrade procedure, CP60 blocks with the MBADOP (Manual if Bad
option) set transition to Manual during an On-Line Upgrade.
1.2.8.2 Temporary Loss of Communication for Field Devices

During transition to the new version of the control software during an On-Line Upgrade proce-
dure, there will be a loss of communications between the CP and field devices (Allen-Bradley
devices, Modicon devices, and FBMs, including the Modbus FBM224) for approximately 5 to 8
seconds. FBMs (excluding the Modbus FBM224) hold their outputs at the last value for this time
period, but there is no similar action for Allen-Bradley or Modicon devices connected by
I/A Series Gateways or Integrators, or Modbus FBM224 connected devices. The process under
control must be able to ride through this 5 to 8 second output hold duration.
Contact the Customer Satisfaction Center (CSC) before starting the On-Line Upgrade proce-
dures if you are upgrading Allen-Bradley or Modicon devices connected by I/A Series Gateways or
Integrators, or if devices connected to the Modbus FBM224 are involved. Call 1-866-746-6477,
or visit http://www.ips.csc.invensys.com.
1.2.8.3 On-Line Upgrade Limitations for FOUNDATION fieldbus and

PROFIBUS-DP Devices
On-Line Upgrade (B0193RE) indicates that you can use on-line upgrade procedures for control
stations connected to FOUNDATION fieldbus, HART, and PROFIBUS-DP devices. However, the
following limitations have been revealed:
♦ On-Line Upgrade procedures involving FOUNDATION fieldbus devices do not func-
tion correctly when upgrading from V6.3 to V6.4, and do not function as well as
Foxboro proprietary devices going from V6.4 to V6.5.
♦ On-Line Upgrade procedures involving PROFIBUS-DP devices do not function cor-
rectly when upgrading from V6.4 to newer releases because of the fail-safe assertion
on the CP reboot.
It is not recommended that you use the On-Line Upgrade procedures for FOUNDATION fieldbus
and PROFIBUS-DP devices.
Contact the Customer Satisfaction Center (CSC) before starting the On-Line Upgrade proce-
dures if FOUNDATION fieldbus or PROFIBUS-DP devices are involved. Call 1-866-746-6477, or
visit http://www.ips.csc.invensys.com.
1.2.8.4 Checkpointing During the On-Line Upgrade Process

During the On-Line Upgrade procedure, you are offered two options:
♦ Incrementing fail-safe timers automatically for hold action, and
♦ Performing a checkpoint.
16
It is highly recommended that you do not choose both options together (that is, do not respond
with Y to both prompts). Incrementing the fail-safe timers, and checkpointing will result in the
checkpoint containing undesired status information if status changes occur during the fail-safe
timer reconfiguration process. See “HART Device Status Changes” below.
You may choose one of the two options.
1.2.8.5 HART Device Status Changes

During an On-Line Upgrade, you are given the option of automatically incrementing fail-safe
timers for hold action. If you choose to increment the fail-safe timer values during an on-line
upgrade of HART devices, the following status changes occur for some of the HART devices:
1. HART 4 to 20 mA devices appear with a Device State of FAILED on the Equipment
Information display.
2. RIN blocks appear cyan with the error indication W62 - UNRESOLVED CONNECTION.
After the transition to the newer version of software, the device returns to its original state of
health that was preserved in the checkpoint file, although the faults persist for a few minutes.
1.2.9 Integrated Control Configurator

1.2.9.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.
1.2.9.2 ICC API Driver Task Move Function

The MOVE function of the ICC API driver task does not work correctly within ECB com-
pounds. If you try to move an ECB to any processing order position other than the last position
in the ECB zone using the -END_ECB_ZONE syntax, the error message “cannot move the block
ahead of the compound” appears.
If you are working with an ECB compound, and you want to move an ECB to position within
the ECB zone other than the last position, use the Integrated Control Configurator. Refer to
Integrated Control Configurator (B0193AV) for instructions.
1.2.9.3 FixAll Errors for Several FBMs

Performing a FixAll from the ICC does not work (generates errors) for the following FBMs:
♦ FOUNDATION fieldbus FBMs: FBM220 and 221
♦ FoxCom FBMs: FBM243 and 246
♦ HART FBMs: FBM214, 215, 216, and 218
♦ PROFIBUS-DP FBM: FBM223.
You must create the child devices manually in the ICC.
17
1.2.9.4 50 Series SaveAll Issue

The SaveAll function of the Integrated Control Configurator does not function properly when
saving databases to remote 50 Series diskette drives. The SaveAll diskette contains all of the com-
pounds, but the compound list file (file .Compound_Dir) is truncated. LoadAll operations using
these diskettes load only one compound, even though the complete database is stored on the
SaveAll diskette. This problem only occurs when the LoadAll is performed using the ICCAPI
driver with these diskettes.
During all SaveAll operations, you must specify the diskette drive attached to the control
processor’s host. This is only required if the ICCAPI is used to perform the LoadAll.
1.2.9.5 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.
1.2.9.6 Text Editor for Use with ICC Sequence Logic Editor
The ICC Sequence Logic Editor now uses the more user-friendly “TextEdit” program, instead of
the “vi” editor. For additional information, type man textedit.
1.2.10 Control Blocks and Parameters

1.2.10.1 SIMOPT Parameter
For DCI blocks, the Simulation Option, SIMOPT, is a configurable option parameter that speci-
fies whether the DCI block output value is to be simulated by storing the block output value into
the read-back value to simulate confirmation by the field device.
SIMOPT=1 does not work in the BOUT, BOUTR, ROUT, ROUTR, and IOUT blocks for the
CP60.
1.2.10.2 Packed Boolean CALC Block Functions

The following packed boolean logic functions for the CALC block are not working correctly in
the CP60:
♦ NANX
♦ NORX
♦ NXOX.
The ORX and XORX functions work correctly.
1.2.10.3 PID(A) Fail-Safe Behavior After CP60 Reboot

After a CP60 reboot, the PID and PIDA blocks that are connected to a PROFIBUS-DP ROUT
block may return in the fail-safe mode when fail-safe due to communication loss is configured
(PIDA.MANFS = 1, ROUT.PRIBLK = 1, ROUT.FSOPTN is between 4 and 7, and
ECB200.FSENAB = 1). Under normal conditions, the blocks should stay in the auto mode and
18
resume control from the ROUT block’s FSOUT value. If you want the PIDA block to hold con-
trol at the fail-safe value (ROUT.FSOUT), set PIDA.INITMA to 0.
1.2.10.4 Changing FSENAB for ECB200 (PROFIBUS-DP FBM223)

Changing the FSENAB (fail-safe enable) parameter from 0 to 1 on an ECB200 which is config-
ured 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.
1.2.10.5 SUPBCO Parameter of PIDA Block

If you utilize the SUPBCO parameter within a Supervisory program, you should be aware that in
certain setpoint limiting situations where SPCLMP is equal to either 1 or 2, SUPBCO may not
represent the actual setpoint value used by the controller. This situation arises because, for the
PIDA algorithm, the SUPBCO value is calculated prior to the setpoint limiting logic. For this
reason, it is advisable to utilize the SPT value in place of the SUPBCO value if actual controller
setpoints are required within some calculations as part of an overall supervisory control scheme.
1.2.10.6 Using the Setpoint Clamping Option (SPCLMP)

When using the Setpoint Clamping option, it is possible for the setpoint to jump to the clamping
values (SPHLIM/SPLLIM) under the following conditions:
♦ SPCLMP is set to 0
♦ PIDA is in remote setpoint
♦ Remote setpoint is outside the SPHLIM/SPLLIM limits
♦ PIDA is transferred to local setpoint where the setpoint limits are temporarily
stretched to prevent a bump
♦ After transferring to local setpoint, SPHLIM/SPLLIM values are then adjusted.
This is part of the design and should be understood by all engineers using this feature. Integrated
Control Block Descriptions (B0193AX) will be updated to describe this aspect of the design.
1.2.10.7 Using the ROCV Parameter with HART FBMs

The Rate of Change feature is not currently supported for 4 to 20 mA input signals to HART
input FBMs (FBM214 and FBM216). As such, the ROCV parameter for RIN and RINR blocks
has no effect when used with these FBMs.
1.2.10.8 Mass Flow Transmitter ECB22 Limitation

If you enable fail-safe in the ECB22 (Mass Flow Transmitter equipment control block), the Cori-
olis Mass Flow Transmitter CFT10 does not stay on-line. Setting the FSENAB parameter to 1 in
the ECB22 causes the CFT10 mass flow meter to cycle from good to bad to good.
To avoid this condition, make sure that the ECB22 FSENAB parameter is set to 0.
1.2.10.9 Characterizer Block, CHARC (CAR #1004203)

An option of the CHARC block is the Extender Block Option (EXTOPT), which allows the
CHARC block to function as an extension to an AIN or MAIN block for performing signal con-
ditioning and thermocouple compensation.
19
When EXTOPT is set, the PHASE parameter of the CHARC block is set to -1, indicating that
the block is running as an extension to an AIN or MAIN block. The CONFIG overlay for the
Characterizer (CHARC) block detail display will show a -1 for the PHASE parameter when this
configuration condition exists.
In the chapter titled “CHARC – Characterizer Block” of Integrated Control Block Descriptions
(B0193AX), the EXTOPT parameter description should explain that the PHASE parameter dis-
plays as -1 when the extender block option (EXTOPT) is set.
1.2.11 Alarms and Displays

1.2.11.1 Scaling Button Labels in Alarm Manager Displays
In V6.3 I/A Series software, the Alarm Manager was modified so that if eight or more alarm but-
tons were defined on its displays (for example, the Current Alarm Display [CAD], Most Recent
Alarm History [MRH]), a smaller font size would be used to label those buttons. In some cases,
the smaller font made it difficult for operators to see the button labels.
In the V6.5.1 and V7.1 versions of Alarm Manager, you are given the option to enable the font
scaling of those alarm buttons. By default, scaling is disabled. To enable scaling, you must define
the variable “AM_SCALE_FONT” in the globals file “/usr/fox/wp/data/wp51_glbls.all” as
follows:
AM_SCALE_FONT=Y # Note, not case sensitive.
By default, when scaling is enabled, button labels are scaled if a display contains two or more but-
ton rows or 13 or more columns of buttons. You can also redefine the number of rows, columns,
or both before the scaling takes effect.
To redefine the number of rows, define “AM_SCALE_FONT” as follows:
AM_SCALE_FONT=Y,R=3
Scaling now takes effect when three or more rows or 13 (default) or more columns of buttons are
defined.
To redefine the number of columns, define “AM_SCALE_FONT” as follows:
AM_SCALE_FONT=Y,C=8
Scaling now takes effect when two (default) or more rows or eight or more columns of buttons are
defined.
To redefine both rows and columns, define “AM_SCALE_FONT” as follows:
AM_SCALE_FONT=Y,R=3,C=8
Scaling now takes effect when three or more rows or eight or more columns of buttons are
defined.
NOTE
The order in which you define “R” and “C” does not matter.
The workstation must be rebooted for any of these options to take effect.
1.2.11.2 LOOPID Characters Preventing Alarms

Alarms are not issued with compound LOOPID if the LOOPID value starts with the character
zero (0). Use another character.
20
1.2.11.3 Displaying Alarms on a Workstation Without a Configured

Printer
If you reboot a standalone AW70CP that does not have a connected printer configured in System
Definition, alarm messages may not be displayed in the Current Alarms Display (CAD). This
problem occurs because the Device Monitor marks the station as “failed”, and as a result, alarm
messages are not sent to the workstation.
This problem does not occur if a printer is configured in System Definition prior to V7.0 software
installation on the AW70CP or if another workstation is attached to the same node as the work-
station without a printer. Under these conditions, the Device Monitor marks the station correctly
and alarm messages appear on the CAD correctly. Alternatively, if there are no other stations or
devices on the node (for example, another workstation or a printer), alarm messages are not dis-
played on the CAD.
To work around this issue, you can add commands to any script that runs during boot-up, (such
as d:/usr/fox/bin/go_ACSA.ksh) as follows:
sleep 5
/usr/fox/cs/dm_recon
1.2.11.4 Incorrect System Monitor Status for AW51F

If a workstation has failed or unavailable devices connected to it, normally the station appears yel-
low and failed devices appear red on the System Management displays. When this occurs, you can
inhibit (disable) the failed devices alarms so that the workstation appears white in SMDH. This
does not happen for an AW51F with attached devices that are failed or unavailable, even if you
inhibit the devices’ alarms.
1.2.11.5 Delay in Call-Up of New Sequence Block Default Displays

The enhanced FoxView Sequence block detail displays include the Sequence block Code on the
initial page. If the Sequence block is hosted by an AW70, calling in the enhanced Sequence block
detail display in FoxView running on an AW/WP51 causes FoxView to lock up for 1 to 2 min-
utes. This same phenomenon occurs when accessing the Code page of original style Sequence
block detail displays from either Display Manager or FoxView. As noted, this lock up only occurs
if the CP is hosted by an AW70.
1.2.11.6 ECB53 Faceplate

There is no ECB53 faceplate available for Display Manager or FoxView user displays. The ECB53
Block Detail display is available.
1.2.11.7 PIDX and PIDXE Faceplates

Display Manager and FoxView user displays with PIDX and PIDXE old-style faceplates and
PIDX and PIDXE Detail displays may show a D in the faceplate indicating that supervisory con-
trol is selected, even if supervisory control is not configured for the block displayed. Enhanced
Detail displays are optionally available with FoxView software for the Windows operating system,
and work correctly. For information on using the enhanced detail displays, refer to FoxView Soft-
ware (B0193WH).
21
1.2.12 System Definition 2.4.1

1.2.12.1 Configuring a Model 51F Workstation with GCIO or Serial
Printer
The Model 51F (Sun Blade 150) workstation has only one serial port, and would normally need a
multiport serial card installed and configured using System Definition in order to connect annun-
ciator keypanels, a touchscreen, or a directly connected serial printer.
However, System Definition does not allow the configuration of a multiport serial card on a
Model 51F (Sun Blade 150) workstation. Due to remnant configuration parameters in System
Definition and software install, and the fact that the multiport serial card drivers are built in the
Model 51F at boot time, you can perform the following workaround that negates the System Def-
inition problem.
NOTE
This problem also exists for the Model 51G workstation. However, Model 51G
workstations are equipped with two serial ports, and do not need multiport serial
cards to connect annunciator keypanels, a touchscreen, or a directly connected serial
printer.
The software installation process does not allow both a serial printer and a GCIO configured
through System Definition on the same machine.
To work around this issue, perform the following steps:
1. Do not configure a multiport expander card for the Model 51F workstation in System
Definition. Simply create the “GCDEV” or directly connected serial printer in System
Definition, and physically connect the GCIO or printer to “Serial Port 1” on the
workstation, as is done for a Model 51B, C, D, or E workstation.
2. Install the multiport serial card in the Model 51F station per the instructions in the
workstation-specific document shipped with your processor. When software install
executes, it builds the serial port configuration parameters as it did previously on the
Model 51B, C, D, or E workstations, which have two serial ports.
3. Connect the GCIO or printer to the multiport serial card, using the first connector
(0) for GCIO, or the second connector (1) for a serial printer.
4. The multiport serial card drivers are created on bootup. When the devices are con-
nected properly, SMDH, Device Monitor, lpstat, and System Monitor messages show
the devices as operational.
1.2.12.2 Adding a Workstation to a Nodebus Extender Segment

When moving an existing workstation to a Nodebus extender segment, its IP address may be
recalculated to the next consecutive IP address. If the workstation IP addresses are not consecu-
tive, and the workstation that is added to the Nodebus extender segment is directly after the gap
in the address list, then its address will be recalculated. Please refer to the following figure:
22
There is a gap in the IP address list; 151.128.008.66 is missing because a workstation has been
deleted. If the workstation with IP address 151.128.008.67 is moved to a Nodebus extender seg-
ment, its IP address would then change to the next consecutive address, 151.128.008.66. It is
important that you are aware of this issue when adding Nodebus extenders to an existing system
configuration.
1.2.12.3 Configuring a Micro-I/A Station Letterbug Server with SysDef

If you are configuring a Micro-I/A station using System Definition 2.4 or 2.4.1, assign only one
instance of the Micro-I/A Letterbug Server (AMCSRV) in your system. The Check Configuration
utility does not provide an error message when more than one Letterbug Server is configured.
1.2.13 Intelligent Field Device Configurator (IFDC)

1.2.13.1 Downloading Configuration Changes to a FoxCom Device
After downloading configuration changes from a Model 51F (P79) workstation to a FoxCom™
device (for example, RTT20) the following error message may be displayed:
Parameter Read Error
Sizes do not match ....
After you download the configuration changes, IFDC reads back a “configuration change
counter”. This counter helps track such activity as changing the device configuration with the
push buttons directly on the device.
23
The error message displays because the target device does not respond to the request to deliver the
counter for a long time, and the message queue gets mixed up during the IFDC’s recovery
strategy. The result of the mix-up is a bad response with the wrong length and the error message.
To work around this problem, select the Upload from Device button after the error message
appears. This function uploads the latest change counters.
1.2.13.2 Take Intelligent Field Devices Off Scan

Before performing any complex operations such as device calibration in Intelligent Field Device
Configurator (IFDC), the intelligent field device needs to be taken off scan. Taking the device off
scan helps prevent a process upset and reduces conflicts between I/A Series software scanning and
the device transient state.
1.2.13.3 Do Not Restore Factory Settings from IFDC

Do not perform a “Restore Factory Settings” operation via IFDC, the results could cause all chan-
nels on the connected FBM to go in and out of service. Disconnect the device and use the PC20
to restore and reset factory settings.
1.2.13.4 Single IFDC Session Allowed

To avoid IFDC communication failures, only a single IFDC session is allowed when CP30s and
CP40s are used with FoxCom devices.
1.2.14 PROFIBUS-DP Configurators

1.2.14.1 Help Button Works Incorrectly for PROFIBUS-DP Master and
Slave Configurators
On Solaris systems, the help pages do not load when either the Help button or the F1 key is
pressed on dialog boxes in the Profibus Master Configurator and the Profibus Slave Configurator.
The help pages do load when HELP is selected through the application’s menu. If the help page is
loaded from the menu and left active, pressing the HELP button in a dialog box automatically
displays the help page for that dialog box.
1.2.15 FoxAPI Software

1.2.15.1 Starting the Foxhosts Program (if Necessary)
Foxhosts (UNIX) and foxhosts.exe (Windows) have been added to FoxAPI™. These programs
provide the server identification of this UNIX or Windows server to any client that requests it.
These programs 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 /opt/fox/ais/bin/an_init.tcp file on a UNIX server or the
D:\opt\fox\ais\bin\an_init.tcp on a Windows server.
24
♦ Edit the HOST line in the [AISnet] section of the appropriate file with the letter-
bug of this server:
[AISnet]
HOST=<Local server letterbug>
2. Start the foxhosts program by performing one of the following steps:
a. On a UNIX workstation, edit the /opt/fox/ais/bin/servers file as follows:
♦ Remove the # from the four lines that follow #Kill foxhosts
♦ Remove the # from the one line that follows #Start foxhosts
b. On a Windows workstation, edit the 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 performing one of the following steps:
a. On a UNIX server, run the aisstart script in /opt/fox/ais/bin, or
b. On a Windows server, run the apistart script in D:\opt\fox\ais\bin.
1.2.16 FoxCAE Software

1.2.16.1 Enabling Communication Between FoxCAE and FoxAPI Software
To enable FoxCAE 5.0 to communicate with the FoxAPI application on a Server 70
(Windows NT) or a Windows XP workstation, you must perform the following steps:
1. Configure the an_init.cfg found in the FoxCAE installation directory.
2. Copy the an_init.cfg file that you configured to the following directory, as applicable:
a. For Server 70 workstations, copy the file to the c:\wtsrv directory
b. For Windows XP workstations, copy the file to the c:\windows directory.
3. Remove the an_init.cfg file from the following directory, as applicable:
a. For Server 70 workstations, remove the an_init.cfg file from the
c:\wtsrv\Profile\fox\windows directory
b. For Windows XP workstations, remove the an_init.cfg file from the
c:\windows\Profile directory.
1.2.16.2 Generating Device Template Files

FoxCAE 5.0 software does not support the generation of device template files on the
Windows XP platform. You must generate the device template files using a Windows NT work-
station and import them to the Windows XP workstation on which FoxCAE 5.0 is installed.
1.2.16.3 FoxCAE Communication Between a Standalone and an

I/A Series Workstation
FoxCAE software installed on a standalone (non I/A Series) Windows XP workstation may have
problems communicating with an I/A Series workstation hosting a CP. Before attempting to con-
nect to an I/A Series workstation, verify the following:
1. The workstation’s name is at least 6 characters in length. FoxCAE cannot communi-
cate with devices if the workstation’s name contains fewer than 6 characters.
25
2. The an_init.cfg file is configured for all workstations to which you want to connect.
3. A “Network Bridge” does not exist on the standalone Windows XP workstation on
which FoxCAE is installed. To verify that a network bridge does not exist, right-click
My Network Places and select Properties. If a network bridge exists, delete it.
1.2.16.4 Configuring FoxCAE on a non I/A Series Workstation

When FoxCAE is installed on a standalone (non I/A Series) Windows NT or standalone
Windows XP workstation, the workstation’s name must be at least 6 characters in length.
FoxCAE cannot communicate with devices if the workstation’s name contains fewer than
6 characters.
1.2.16.5 Converting Databases Between Platforms

The FoxCAE transfer utilities are no longer supported. To transfer SaveAlls from a Solaris
(UNIX) system to a Windows XP system and vice-versa, refer to “Converting Control Databases”
in System Administration Guide (Windows XP Operating System) (B0400HE).
1.2.17 Object Manager

1.2.17.1 OM Load Higher Than Normal
While running the V6.4, V6.5, or V7.x CP60 image, the OM Load on the Station display may
report a higher than normal load percentage. This problem has been seen with stations under high
FBM loads and peer-to-peer connections. If this condition presents itself after loading or while
running I/A Series V6.4, V6.5, or V7.x software, contact the Customer Satisfaction Center for
assistance (refer to the preface for contact information).
1.2.18 Carrierband LAN Interface

1.2.18.1 Nodebus Test Initiator (70 Series)
The following issues exist on application workstations (AW70):
♦ If an application workstation without control is the Nodebus test initiator, and you
select Carrierband LAN I/F (CLI), followed by CHANGE NODEBUS TEST INITIATOR,
the application workstation remains the test initiator and the system message
“invalid alias name Add alias” reports at the system printer. This is not an issue
for application workstations with control.
♦ Selecting DEFAULT NODEBUS TEST INITIATOR does not consistently force the CLI to
become the Nodebus test initiator.
♦ If a CLI is the Nodebus test initiator, and you select an application workstation with-
out control, followed by CHANGE NODEBUS TEST INITIATOR, the CLI remains the test
initiator and the system message “Invalid Station Type for Requested Opera-
tion” reports on the SMDH display. This is not an issue for application workstations
with control.
26
1.2.18.2 Changing Nodebus Mastership from CLAN to AW with Control

The Carrierband LAN Interface module does not allow the selection of an AW51 with control
(AW51X, styles B through G) as the Nodebus test initiator; an Illegal Station Type for
Operation message displays.
You can manually force the AW51X to become the Nodebus Master by performing one of the fol-
lowing steps in the On-Line Diagnostics display:
♦ Switch the test initiator from the LAN Interface to an AW or AP without control, and
then switch the test initiator to the workstation with control.
or
♦ (For V7.1 AWs only) If there is not an AW or AP without control, select Default Test
Initiator. This resets the user override bit to allow a workstation with control to take
over as the Nodebus master. If necessary, switch the test initiator to the desired work-
station with control.
NOTE
On a node with only a V6.x LAN and a V6.x AW51X, you cannot force the
AW51X to become the Nodebus Master.
1.2.18.3 Carrierband LAN Dump Packets

V7.x hosts cannot receive dumps from Carrierband LAN modules; the packets are too large to be
forwarded by Ethernet switches.
1.2.18.4 Carrierband LAN Reports Benign Message

V7.x APs and AWs attempt to assume Nodebus mastership from Carrierband LANs. During any
period that the CLAN is the current initiator, you may experience a repeating IPC invalid alias
name, Add alias message. This message ceases when the CLAN relinquishes mastership to an AP
or AW station.
1.2.19 I/A Series Tools

1.2.19.1 dbvu -t with CP60
The dbvu utility does not function properly with the CP60. When you use the dbvu -t option,
the utility fails to read the FCM ECB.
1.2.20 FBMs/FCMs
1.2.20.1 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
27
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.
1.2.20.2 Incorrect Status of FBMs in SMDH

When control processors boot up as fault-tolerant pairs and the I/O fieldbus is disconnected,
FBMs that are configured may appear white and on-line in SMDH. When the I/O fieldbus is
connected and communication between the CP and the FBMs occurs, the correct FBM status is
reported.
1.2.20.3 Setting FBM Fail-Safe

Do not set fail-safe above 100%. If fail-safe is set above 100%, a type 1 fail-safe condition (FBM
is taken off-line) results in incorrect operation upon return from fail-safe if the FBM is in MAN-
UAL. The FBM outputs drop to -2% rather than the MANUAL value. This function works cor-
rectly for type 2 (COMM failure, FBM to CP) conditions.
1.2.20.4 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.
1.2.20.5 EEPROM Updating FBMs

Specifically for FOUNDATION fieldbus H1 and PROFIBUS-DP FBMs where large size iom files
are used, when in a position to EEPROM update any FBMs hosted by a specific CP60, it is rec-
ommended that you ensure that at least one FBM (legacy or 200 series) is on-line and communi-
cating to the CP60 prior to starting the EEPROM update. This technique reduces the amount of
EEPROM update time for all the additional FBMs on the bus.
1.2.20.6 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. After the EEPROM update has finished, verify that the
FBM is using the new EEPROM revision level by looking at the EEPROM REV field on the
FBM’s Equipment Information display.
28
1.2.20.7 FBM216 and 218 SMDH Field Updates

Following an EEPROM update of the FBM216 and of the FBM218, the SMDH Equipment
Information display field labeled MAIN VER NO. does not always update automatically.
This field updates if the FBMs are put off-line then back on-line. However, the information con-
tained in this field is the same information that is contained in the MAIN SOFTWARE REV
field, which updates automatically following the EEPROM update.
1.2.20.8 Temporary Communication Failures of FBM215 and FBM218

An output block (ROUT, IOUT) driving the current output of a HART® device connected to an
FBM215 or FBM218 can cause HART communication failures on the channel to which the
device is connected. These communication failures result in the FBM generating “device failure”
messages followed immediately by “device online” messages. Occasionally, an FBM218 will
switch from the Master to the Tracker as a result of these temporary communication failures.
The conditions under which the output block is most likely to cause these failures is the continu-
ous changing of the output level over a period of several seconds (such as while ramping the out-
put steadily). A single output change is unlikely to cause trouble if it is separated in time from
other output changes by at least two seconds.
It is important to note that these events (temporary loss of HART communications, and occa-
sional switching from Master to Tracker) do not affect or interrupt the current output to the
device, but care must be taken if your control scheme monitors and takes actions based upon the
status.
1.2.20.9 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.
1.2.20.10 FBM220/221 EEPROM Updates

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 (fail-safe) value.
1.2.20.11 FBM223 Problems After CP60 Reboot

On rare occasions, rebooting a CP60 can result in the ports of one or more PROFIBUS-DP I/O
FBMs not working properly when the control blocks restart execution. The status of the devices
in System Management displays and status in block displays do not indicate any failure, but the
data values do not change.
This problem can be corrected by restarting the FBM223 using the DOWNLOAD function on
the Equipment Change display.
1.2.20.12 Status of FBM224 Ports at Initialization

Because of a known issue with the CP60, when the CP60 initializes the FBM224, the CP60 does
not use the correct information from the checkpoint file regarding which FBM224 ports should
be enabled and which should be disabled. A consequence of this problem is that following recov-
29
ery from a power outage, for example, both the CP60 and the FBM224 initialize, and the
FBM224 ports initialize to their default state of Disabled. Hence, there are no communications
from the FBM224 to the configured devices; recovery to a fully operational state is not automatic.
To work around this problem, the default state of the FBM224 ports has been changed to
Enabled. With this modification, any ports that were enabled and operating prior to the initializa-
tion recover to full operation.
There is, however, a side effect of this work-around of which you need to be aware: if you disabled
FBM224 ports using SMDH, the ports automatically become enabled following initialization. If
this poses a potential danger, it is recommended that you use the Modbus Port Configurator to
disable the ports in the port configuration file itself, rather than disabling the ports in the
ECB200 (using the SMDH Equipment Change Action). If you use this method (modification of
the port configuration file), you must download the modified port configuration file to the
FBM224 (using the DB Download Equipment Change Action of SMDH), and then checkpoint
the CP60 database.
1.2.21 Control Stations

1.2.21.1 Fault-Tolerant Control Station Communication
When initially installing the control stations into the I/A Series rack for a fault-tolerant pair,
ensure that both elevators are in the fully engaged position. Fault-tolerant I/O communication
cannot start until both modules have a valid connection.
1.2.21.2 CP60 Fail-Safe Actions with PROFIBUS-DP FBM223

Use caution when turning a compound OFF that contains a PROFIBUS-DP output block with
configured fail-safe options (FSOPTN). When the compound is turned back ON, the CP60
intermittently writes the previously set output value to the FBM223, and not the configured fail-
safe value. (This problem occurs only when the compound is turned back on. There has been no
observed problem to date when the compound is turned off.)
1.2.21.3 Location of Include File mpt.h for Allen-Bradley Station

The include file, mpt.h, provides structures for the format of messages that are sent to the
Allen-Bradley (A-B) Station and passed through the A-B Station to communicate with A-B PLCs.
The include file, mpt.h, is used by ipc_rtns.c. The location of the include file is:
/opt/fox/OS1AB4/reloc/Solaris/usr/include/fox/mpt.h
1.2.21.4 Incorrect Software Version Displayed for the AW70CP

A Software Version of “V7.1” should display on the Station Block display for a Windows XP
workstation with control capability (AW70CP). However, the Station Block display incorrectly
shows “V7.0” for the Control Software Version of this workstation.
30
1.2.22 Field Automation Subsystem Micro-I/A Station

1.2.22.1 Blocks, Parameters, and ECBs
1.2.22.1.1 Placing ECB102 Off-Line or On-Line May Cause Micro-I/A Station to Crash
When an ECB102 is taken off-line or placed on-line, the Micro-I/A station may crash with a
memory violation.
To avoid this problem, take the child ECB103s off-line first, then the ECB102 can be turned off-
line and on-line without crashing the Micro-I/A station. After putting the ECB102 back on-line,
the ECB103s can be placed on-line and on-scan via a General Download.
1.2.22.1.2 Ensure ECB is Off-Line Before Editing

Attempting to make changes to an ECB while it is on-line can cause the Micro-I/A station to
crash. In addition, trying to delete/undelete an ECB that is not in the ECB compound and is on-
line causes a message box to appear that implies you must take the compound off-line before per-
forming a delete/undelete. However, the compound is deleted regardless of its on-line/off-line
state.
To avoid these problems, place each ECB in the ECB compound. If the ECB does not reside in
the ECB compound, make sure that you take each ECB off-line before making changes to it or
performing a delete/undelete.
1.2.22.1.3 Avoid Switching Quickly Between SMDH and the ICC

If a Micro-I/A station parent ECB is off-line and you perform an ONLINE or GENERAL
DOWNLOAD function in SMDH and then immediately switch to the ICC to perform a
DELETE/UNDELETE of the block, a problem may occur. The block may delete but never
undelete, and the block is lost, even though SMDH shows it ONLINE. Please allow 15 to 20 sec-
onds for the ECB to complete going on-line before attempting any ECB edits.
1.2.22.1.4 Changing the Modbus VAL_ID and CONV Parameters

If you change the Modbus FIIN block VAL_ID and CONV parameters then select Done, the
Micro-I/A station can become inoperable. To change the Modbus FIIN block’s VAL_ID and
CONV parameters from the Integrated Control Configurator, first delete the FIIN block, then
recreate it with the new VAL_ID and CONV values.
1.2.22.1.5 CONV Parameter for FMCOUT and FMCIN Blocks

For the FMCOUT and FMCIN blocks, use only 16 bits or less when using CONV values 1, 2, 3,
and 4. For a CONV value of 0, 32 bits can be used.
1.2.22.2 GE FANUC Direct Connect I/O Interface

1.2.22.2.1 Updating GE I/O Displays in SMDH
If the 6.5 V power cable is disconnected when the Micro-I/A station reboots and then you recon-
nect the 6.5 V power cable, the parent ECB displays yellow and the child ECBs display red in
SMDH. However, the Equipment Information Display shows the correct status: a run mode of
on-line and a device state of on scan. To update the SMDH display, select Download. Further-
more, you should make sure the 6.5 V power cable is connected to the Micro-I/A station during a
reboot.
31
1.2.22.2.2 GE I/O Modules Do Not Go On-Line

After you initially install the V6.2.3 station software and reboot the Micro-I/A stations, GE® I/O
modules may not go back on-line. If this happens, perform a SaveAll, Initialize, Reboot, then a
LoadAll, and the I/O modules go on-line.
1.2.22.3 Dual Ethernet Interface

1.2.22.3.1 Dual Ethernet Crash Dump Files
Crash dump files are not supported on dual Ethernet systems.
1.2.22.4 Modbus Interface

1.2.22.4.1 Updating ECB109 Displays in SMDH
After a power failure or a pushbutton reset of the Micro-I/A station with a configured ECB108,
ECB109 comes on-line showing cyan in SMDH, and with a run status of ONLINE and a fail sta-
tus of NOT READY in the Equipment Information Display. To update the status display, toggle
the parent ECB108 off-line then on-line via SMDH.
1.2.22.4.2 Incorrect ECB109 Displays in SMDH

Modicon PLC shows as white and on scan in SMDH even though no PLC is connected. Once in
this state, it always shows white.
To recover from this problem, delete the ECB109 and rebuild it.
NOTE
Delete/undelete does not correct the SMDH displays. You must rebuild the
ECB109.
1.2.22.4.3 Incorrect ECB108 Displays in SMDH

If you delete/undelete or delete and rebuild an ECB108 hosting ECB109s, read/write problems
occur with the Modbus PLC and/or SMDH. Values can be written to the PLC incorrectly.
To recover from this problem, perform the following steps:
1. Delete the ECB109 and rebuild it. (Delete/undelete does not correct the SMDH dis-
plays. You must rebuild the ECB109.)
2. Toggle the compounds off then on.
1.2.22.5 A-B PLC5/E Interface

1.2.22.5.1 PLCIO Block is Not Supported
The Allen-Bradley Ethernet PLCIO block is not supported.
Functionally, the PLCIO block is a composite merge of:
♦ 2 Binary Output (BOUT) blocks
♦ 2 Real Output (ROUT) blocks
♦ 1 Packed Input (PAKIN) block
♦ 1 Packed Output (PAKOUT) block
32
♦ 1 Multiple Real Input (MRIN) block

♦ 1 Multiple Real Output (MROUT) block.
Each of these individual blocks is supported and can be utilized independently.
1.2.22.5.2 Ensure ECB107 is Off-Line Before Editing Attached Blocks

The Allen-Bradley Ethernet block set consists of the following blocks:
♦ Binary Input (BIN) block
♦ Binary Output (BOUT) block
♦ Real Input (RIN) block
♦ Real Output (ROUT) block
♦ Multiple Real Input (MRIN) block
♦ Multiple Real Output (MROUT) block
♦ Packed Input (PAKIN) block
♦ Packed Output (PAKOUT) block
♦ Pulse Output (PLSOUT) block.
Attempting to make changes to any of these Allen-Bradley Ethernet blocks that are attached to an
on-line ECB107 can cause the Micro-I/A station to crash.
To avoid this problem, make sure to take the ECB107 off-line before making changes to the
attached blocks.
1.2.22.5.3 Support for A-B PLC5/E Modules

The Micro-I/A Station Hardware Installation Quick Set-Up Guide (B0199AB) incorrectly states
that the maximum number of Allen-Bradley PLC-5/E modules per Micro-I/A station is 16. Only
one Allen-Bradley PLC-5/E PCMCIA card per Micro-I/A station is currently supported.
1.2.23 Electronic Documentation

1.2.23.1 Incorrect Documentation for ROCV Parameter in B0193AX
The chapter titled “RIN – Real Input Block” in Integrated Control Block Descriptions (B0193AX)
contains incorrect information for the ROCV parameter description. The second paragraph of
the parameter description incorrectly states that ROCV is currently supported only by the HART
FBM216/218. In fact, ROCV is currently not supported by any HART FBMs.
1.2.23.2 Incorrect Graphical Representation of an IFDC Point Calibration

Screen
Figure A-3 “Sample Point Calibration Screen” in Appendix A of Intelligent Field Device Configura-
tor (IFDC) (MI 020-495) shows an incorrect configuration graphic.
Under “Point Calibration” in Appendix A, the Sample Calibration Screen shown in Figure A-3
should reflect the following calibration graphic rather than the configuration graphic shown in
the document.
33
Figure 1-2. Corrected “Sample Point Calibration Screen” for MI 020-495
1.2.23.3 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).
34
♦ 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.
1.2.23.4 Missing Step in B0400QE

The instructions in Chapter 3, “50 Series Day 0 Installation Procedures” of V7.0 Installation Pro-
cedures (B0400QE) do not indicate that you need to specify a workstation type when running the
ia_install script. This missing step should be performed between Steps 5 and 6 in the section titled
“Day 0 CD-ROM Procedure for Stations without RAID Devices”.
After typing ia_install, as specified in Step 5, the installation process prompts you to enter a
workstation type. Type AW51, WP51 (P79 only), or AP51 (P79 only) or press Enter to accept the
default workstation type (AW51).
1.2.23.5 Errors in System Setup Chapters of B0400QC

The following errors were found in V7.0 Read Me First (B0400QC):
♦ Table 2-2 and Table 3-1 do not list the revision of Intelligent Field Device Configurator
(MI 020-495). The correct revision date is October 2002.
♦ The V7.0 I/A Series Documentation CD-ROM is listed as K0173TQ-J in Table 2-3
and Table 3-2; the correct revision is Revision L (K0173TQ-L).
♦ The OMC (Micro-I/A Type 1 station) diskette is noted as V6.2.3 in Table 2-2 and
Table 3-1, but the diskette is labeled V6.4.
1.2.23.6 Errors in Chapter 5 of B0400FA

Chapter 5, “Field Signal Connections” of DIN Rail Mounted FBM Subsystem User’s Guide
(B0400FA) shows higher electrical ratings for certain Termination Assemblies than the agency
permits. The following errors in B0400FA will be corrected in a future revision of the document:
♦ Table 5-53, “Termination Assembly Relays Contact Data”, reflects the incorrect maxi-
mum operating voltage. The correct voltage should read “380 V ac, 125 V dc.”
♦ Figure 5-106, “Maximum Switching Capacity for Relays Used in Termination Assem-
blies” should look as follows:
35
Figure 1-3. Corrected Figure 5-106 in B0400FA
36
2. UNIX System Setup
Use this chapter, as applicable to your system, to verify that the identified parts have been
provided. If you find or suspect any discrepancies, contact the Customer Satisfaction Center for
assistance. Once you verify the equipment, cabling, documentation, and media, proceed with
the system installation.
2.1 Documents and Media

Use the table below to determine the types of stations available at your site, then use the checklists
to verify that you have all the necessary documentation and media to install I/A Series V7.1 soft-
ware on your Model 51F (P79) or Model 51G (P80) station.
Table 2-1. P-Code to 50 Series Station Types Correlation
P-Code Station Type

P79 Model 51F
P80 Model 51G
2.1.1 V7.1 50 Series Documents

The V7.1 UNIX media kits contain the following documents. For additional V7.1 documenta-
tion, refer to “Reference Documents” on page xvii.
Table 2-2. V7.1 Documents for 50 Series Systems
Part Number Description

K0200XC-A – V7.1 P79/80 Workstation Solaris Media Kit
B0400QM-A I/A Series A2 System V7.1 Release Notes and Installation for
UNIX and Windows XP
P0922QL-A – FoxView/FoxDraw Kit
B0193WH-G FoxView Software
B0193WG-G FoxDraw Software
B0193WL-J FoxView and FoxDraw V9.0 Release Notes
K0200RL-E – System Definition 2.4.1 (SysDef 2.4.1) Windows Media Kit
B0193WQ-F System Definition: A Step-By-Step Procedure
B0193XW-E System Definition 2.4.1 Release Notes
2.1.2 V7.1 Model P79 and Model P80 Media

Table 2-3 lists the contents of the required V7.1 Solaris Base Workstation Suite, including the
V7.1 P79/80 Workstation Solaris media kit (K0200XC).
37
B0400QM – Rev A 2. UNIX System Setup
Table 2-3. V7.1 Solaris Base Workstation Suite

K0200XC-A – V7.1 P79/80 Workstation Solaris Media Kit
K0175ZJ-A V7.1 P79/80 Workstation Solaris Release Update CD-ROM
K0175ZF-A Media Distribution Diskette (10091)
K0175ZG-A Revision Level Diskette (11001-3)
K0173TQ-M V7.1 I/A Series Documentation CD-ROM
Table 2-4 lists the contents of the optionally available V7.1 Solaris Visualization Suite.
Table 2-4. V7.1 Solaris Visualization Suite

FoxView/FoxDraw 9.0 for I/A Series Systems
K0200GK-A FoxView/FoxDraw 9.0 for I/A Series CD-ROM
K0175TW-A Clip-Art CD-ROM for the Windows operating system
K0175TX-A Clip-Art CD-ROM for the UNIX operating system
Table 2-5 lists the contents of the optionally available V7.1 Solaris Engineering Suite.
Table 2-5. V7.1 Solaris Engineering Suite

System Definition 2.4.1
K0200RL-E – System Definition V2.4.1 (SysDef V2.4.1) Windows Media Kit
K0200MG-L SysDef 2.4.1 Software CD-ROM
2.2 Optional Packages Installation

The I/A Series V7.0 P79/80 Workstation Redundant Network and Non-Redundant Network
Solaris Day 0 CD-ROMs provide workstations with Display Manager (DM) and the Intelligent
Transmitter Maintenance Workbench (IT_Maint). You can elect to install FoxView/FoxDraw
and/or Intelligent Field Device Configurator (IFDC) as optional packages on Model 51F (P79)
and Model 51G (P80) stations.
2.2.1 FoxView/FoxDraw Packages

The FoxView/FoxDraw 9.0 CD-ROM includes software that can be installed on any I/A Series
workstation that is running I/A Series Version 6.1 through Version 6.5.x and I/A Series
Version 7.x.
38
2. UNIX System Setup B0400QM – Rev A
NOTE
After you have installed I/A Series software on a new workstation, the workstation
restarts, and I/A Series software starts without FoxView or FoxDraw.
The FoxView and FoxDraw software packages are not included on the V7.0 Day 0
CD-ROMs or the V7.1 Release Update CD-ROMs; you must install these packages
from the FoxView/FoxDraw 9.0 CD-ROM. Refer to Table 2-4 for information on
the FoxView/FoxDraw 9.0 kits, which are optionally available with I/A Series
Version 7.1 software and are licensed as part of the V7.1 Solaris Visualization Suite.
To install FoxView/FoxDraw 9.0, refer to FoxView and FoxDraw V9.0 Release Notes (B0193WL).
2.3 V7.1 Software Distribution Media Contents

Table 2-6 lists the packages contained on the V7.1 P79/80 Workstation Solaris Release
Update CD-ROM (K0195ZJ). On-line stations with software version differing from the ver-
sions listed in this table must be rebooted after a release update to V7.1.
Table 2-6. Version 7.1 Release Update for UNIX CD-ROM (K0195ZJ)
Mnemonic Description Package Number Version

COMM10 Communication Processor 10 K0175WZ-B V6.5.1
LAN I/F Carrierband LAN Interface K0175XA-B V6.5.1
CP101 Control Processor 10 K0175US-B V6.1.5
CP40B Control Processor 40 Style B K0175VE-B V6.1.5
CP60 Control Processor 60 K0175YA-C V6.5.2
AB30B AB30 Gateway Style B K0175VG-B V6.1.5
MG30B MG30 Gateway Style B K0175VH-B V6.1.5
IS30B1 Interspec 30 Style B K0175VJ-B V6.1.4
OMC Micro-I/A Type 1 Station K0175XQ-B V6.2.5
ABSTN1 Allen-Bradley Station K0175XG-A V6.2.1
1. The station image contained in this package has not changed for this release, but is rein-
stalled during the release update to V7.1 software. If you have a currently loaded station
image containing a quick fix, contact the Customer Satisfaction Center to obtain the quick
fix software and reinstall it after the installation.
39
B0400QM – Rev A 2. UNIX System Setup
40
3. Windows XP System Setup
Use this chapter, as applicable to your system, to verify that the identified parts have been
provided. If you find or suspect any discrepancies, contact the Customer Satisfaction Center for
assistance. Once you verify the equipment, cabling, documentation, and media, proceed with
the system installation.
3.1 Documents and Media

Use the checklists below to verify that you have all the necessary documentation and media to
install I/A Series V7.1 software on your Model P92 station.
3.1.1 V7.1 70 Series Documents

The V7.1 Windows XP media kits contain the following documents. For additional V7.1 docu-
mentation, refer to “Reference Documents” on page xvii.
Table 3-1. V7.1 Documents for 70 Series Systems

K0200XD-A – V7.1 P92 Workstation Windows XP Media Kit
B0400QM-A I/A Series A2 System V7.1 Release Notes and Installation for
UNIX and Windows XP
B0193WH-G FoxView Software
B0193WG-G FoxDraw Software
B0193WL-J FoxView and FoxDraw V9.0 Release Notes
K0200RL-E – System Definition 2.4.1 (SysDef 2.4.1) Windows Media Kit
B0193WQ-F System Definition: A Step-By-Step Procedure
B0193XW-E System Definition 2.4.1 Release Notes
41
B0400QM – Rev A 3. Windows XP System Setup
3.1.2 V7.1 Model P92 Media

Table 3-2 lists the contents of the required V7.1 Windows XP Base Workstation Suite, including
the V7.1 P92 Workstation Windows XP media kit (K0200XD).
Table 3-2. V7.0 Windows XP Base Workstation Suite

K0200XD-A – V7.1 P92 Workstation Windows XP Media Kit
K0175ZH-A V7.1 P92 Workstation Windows XP Release Update CD-ROM
K0175ZF-A Media Distribution Diskette (10091)
K0175ZG-A Revision Level Diskette (11001-3)
K0173TQ-M V7.1 I/A Series Documentation CD-ROM
Table 3-3 lists the contents of the optionally available V7.1 Windows XP Visualization Suite.
Table 3-3. V7.1 Windows XP Visualization Suite

FoxView/FoxDraw 9.0 for I/A Series Systems
K0200GK-A FoxView/FoxDraw 9.0 for I/A Series CD-ROM
K0175TX-A Clip-Art CD-ROM for the UNIX operating system
Table 3-4 lists the contents of the optionally available V7.1 Windows XP Engineering Suite.
Table 3-4. V7.1 Windows XP Engineering Suite

FoxDraw 9.0 for Windows
P0922QN-A – FoxDraw 9.0 Stand-Alone Kit
K0175ZB-A FoxDraw 9.0 Stand-Alone CD-ROM
System Definition 2.4.1
K0200RL-E – System Definition V2.4.1 (SysDef V2.4.1) Windows Media Kit
K0200MG-L SysDef 2.4.1 Software CD-ROM
3.2 Optional Packages Installation

The I/A Series V7.0 P92 Workstation Windows XP Day 0 CD-ROM provides the system with
Intelligent Transmitter Maintenance Workbench (IT_Maint). You can elect to install Intelligent
Field Device Configurator (IFDC) as an optional package on the P92 station.
42
3. Windows XP System Setup B0400QM – Rev A
3.3 FoxView/FoxDraw Software

The FoxView/FoxDraw 9.0 CD-ROM includes software that can be installed on any I/A Series
workstation that is running I/A Series Version 6.1 through Version 6.5.x and I/A Series
Version 7.x.
NOTE
After you have installed I/A Series software on an AW70P workstation, the worksta-
tion restarts, and I/A Series software starts without FoxView or FoxDraw.
The FoxView and FoxDraw software packages are not included on the V7.0 Day 0
CD-ROM or the V7.1 Release Update CD-ROM; you must install these packages
from the FoxView/FoxDraw 9.0 CD-ROM. Refer to Table 3-3 for information on
the FoxView/FoxDraw 9.0 kit, which is optionally available with I/A Series
Version 7.1 software and is licensed as part of the V7.1 Windows XP Visualization
Suite.
To install FoxView/FoxDraw 9.0, refer to FoxView and FoxDraw V9.0 Release Notes (B0193WL).
3.4 V7.1 Software Distribution Media Contents

Table 3-5 lists the packages contained on the V7.1 P92 Workstation Windows XP Release
Update CD-ROM (K0175ZH). On-line stations with software version differing from the ver-
sions listed in this table must be rebooted after a release update to V7.1.
Table 3-5. Version 7.1 Release Update for Windows XP CD-ROM (K0195ZH)
Mnemonic Description Package Number Version

COMM10 Communication Processor 10 K0175WZ-B V6.5.1
LAN I/F Carrierband LAN Interface K0175XA-B V6.5.1
CP101 Control Processor 10 K0175US-B V6.1.5
CP40B Control Processor 40 Style B K0175VE-B V6.1.5
CP60 Control Processor 60 K0175YA-C V6.5.2
AB30B AB30 Gateway Style B K0175VG-B V6.1.5
MG30B MG30 Gateway Style B K0175VH-B V6.1.5
IS30B1 Interspec 30 Style B K0175VJ-B V6.1.4
OMC Micro-I/A Type 1 Station K0175XQ-B V6.2.5
ABSTN1 Allen-Bradley Station K0175XG-A V6.2.1
1.
The station image contained in this package has not changed for this release, but is rein-
stalled during the release update to V7.1 software. If you have a currently loaded station
image containing a quick fix, contact the Customer Satisfaction Center to obtain the quick
fix software and reinstall it after the installation.
43
B0400QM – Rev A 3. Windows XP System Setup
44
4. Upgrade Considerations
This chapter contains considerations for installing I/A Series software V7.1; including a
summary of the interoperability issues you might encounter as you install V7.1 software on your
system, hardware and software requirements, preinstallation, installation, and post-installation
considerations. Refer to V7.0 Upgrade Considerations (B0400QD) for additional information.
All stations must have one of the following I/A Series software versions installed:
♦ V6.4
♦ V6.5
♦ V7.0
♦ V7.1.
These software versions can co-exist on the same Nodebus and Carrierband network.
To upgrade to V7.1, you must be at V7.0. If you have stations currently at the V7.0 release, thor-
oughly review this document and V7.0 Upgrade Considerations (B0400QD) for detailed upgrade
considerations prior to beginning the upgrade. The information can help you make major deci-
sions, such as how to minimize the impact of software compatibility issues, and how to perform
the appropriate preinstallation, installation and postinstallation steps. When in doubt regarding
any part of the upgrade, contact the Customer Satisfaction Center at the numbers listed on
page xv.
When preparing to install V7.1 on a V7.0 station, refer to Chapter 5 “Installing V7.1 Release
Update on 50 Series” for UNIX installation and to Chapter 6 “Installing V7.1 Release Update on
70 Series” for Windows XP installation.
If you are considering using the on-line upgrade procedures, review the following:
♦ On-Line Upgrade (B0193RE)
♦ “On-Line Upgrade” on page 4
♦ “On-Line Upgrade” on page 16.
To plan for the time required for a V7.0 Day 0 installation, refer to the appendix titled “Time
Estimation for Migration to V7.0 Platforms” in V7.0 Upgrade Considerations (B0400QD).
4.1 Interoperability Issues

4.1.1 General
V6.4, V6.5, V7.0, and V7.1 are allowed to interoperate within the configuration. When involved
with stations running V6.4, V6.5, or V7.0 software, consult the release notes released with these
software versions.
45
B0400QM – Rev A 4. Upgrade Considerations
4.1.2 Compound Summary Access (CSA)

CSA must exist on a boot host station with the highest release of control software (that is, V7.1 or
V6.5.1) before you upgrade control stations. This might require moving CSA, if only temporarily,
to support the upgrade.
! CAUTION
CSA can only reside in one station in your configuration.
When you back up, upgrade, or move CSA, you must use the CSA_Save and CSA_Merge utilities.
For instructions on using the CSA_Save and CSA_Merge utilities, see “Compound Summary Access
(CSA)” in V7.0 Upgrade Considerations (B0400QD).
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. See “Moving CSA Between 50/70 Series Stations” or
“Moving CSA from Intel to 50 Series Stations” in V7.0 Upgrade Considerations (B0400QD). This
precaution ensures that, if you must abort the V7.1 upgrade, restoring the old drive also restores
CSA functionality.
If you move CSA to another workstation to support the upgrade, restore CSA to the appropriate
boot host station with the highest release of control software (V7.1 or V6.5.1).
4.1.3 Mixed Version Configurations Require Two Commit

Diskettes
For Version 7.1, you must use System Definition V2.4.1 to create, import, and/or edit your con-
figuration, and to create a Commit diskette. For information on using System Definition V2.4.1
and creating a Commit diskette, refer to “System Definition 2.4.1” on page 6.
4.2 I/A Series A2 System Electronic Documentation

The I/A Series System Electronic Documentation CD-ROM (K0173TQ) for Windows NT 4.0,
and Windows 95/98/2000/XP contains I/A Series system user documentation for UNIX and
Windows platforms (.pdf files), control station sizing spreadsheets (.xls files), and on-line Help
files (.hlp files) not available from their applications.
46
4. Upgrade Considerations B0400QM – Rev A
Electronic Documentation CD-ROMs for I/A Series V6.4 and later software differ from previ-
ously released documentation CD-ROMs as follows:
♦ Documents are in PDF rather than HTML format
♦ Adobe® Acrobat Reader® 4.0 with Search (available on the V6.4 CD only) and
Adobe Acrobat Reader 5.0 with Search (available on the V6.5 CD and later) allows
access to the new documents and document revisions as well as search capability.
♦ Automatic updates of documents between releases is no longer supported.
Documentation for I/A Series Version 7.1 is available on the I/A Series A2 System Electronic Docu-
mentation CD-ROM (K0173TQ-M).
4.2.1 Hardware Requirements

Before you install the I/A Series A2 System Electronic Documentation, make sure that your com-
puter meets the following minimum system requirements:
♦ Pentium class processor or higher
♦ 32 MB of RAM
♦ Hard disk with at least 15.7 MB for Adobe Acrobat Reader 5.0 with Search, if not
already installed
NOTE
K0173TQ-M ships with the Adobe Acrobat Reader 5.0 with Search capability. If
you already have Version 4.0 or later of Acrobat Reader with Search capability
installed, there is no need to install Version 5.0.
♦ CD-ROM drive
♦ Keyboard/mouse
♦ Modem or Internet connection (for access to I/A Series hardware, software, and parts
for purchase).
4.2.2 Software Requirements

Running I/A Series A2 System 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, to access the I/A Series
system parts list from the iastore link on the CD-ROM
♦ Adobe Acrobat Reader 4.0 or later.
4.2.3 Uninstalling Previous Versions of Electronic

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

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

NOTE
Perform the following steps only if you have the I/A Series Electronic Documenta-
tion for I/A Series V6.3 or earlier software installed.
To determine whether I/A Series Documentation Server is running in the background, check the
task bar for the appropriate I/A Series Documentation icon.
To stop the I/A Series Documentation Server, do the following:

1. On the task bar, right-mouse click on the IA Series Documentation icon.
2. Click Close.
48
NOTE
If you attempt to uninstall the I/A Series Documentation while the I/A Series
Documentation Server is running, you are prompted to restart the computer to
complete the task. This may also cause some files to remain on your hard drive.
To remove files that are left behind, delete:
[drive]:\Program Files\FoxDoc Browser\<cd-rom version>
or
[drive]:\Program Files\IA Series Browser\<cd-rom version>
4.2.6 Uninstalling the I/A Series Electronic Documentation

Application
NOTE
You should be sure to remove updated files from any existing versions and stop the
I/A Series Documentation Server prior to uninstalling, or else the previously down-
loaded files remain on your hard drive.
To uninstall a previous version of I/A Series Electronic Documentation, do the following:

1. Click on Start > Settings > Control Panel.
The Control Panel window opens.
2. Double-click on the Add/Remove Programs icon.
The Add/Remove Programs Properties window opens.
3. Click on the Install/Uninstall tab. Highlight IA Series 6.4 Documentation
(K0173TQ-J) and click on Add/Remove.
4. Follow the screen prompts, and click OK to close the Install/Uninstall window when
done.
See the following section for installation instructions and information on navigation and setting
preferences.
4.2.7 I/A Series A2 System Electronic Documentation

(K0173TQ-M)
The I/A Series A2 System Electronic Documentation CD-ROM (K0173TQ-M), contains
Version 6.5.1 and Version 7.1 documents. The following sections contain instructions for install-
ing, accessing, and navigating the V7.1 documents, as well as setting document preferences.
I/A Series A2 System Electronic Documentation requires 15.7 MB of available disk space for the
Adobe Acrobat Reader 5.0 application, if not already installed. Refer to “Hardware Require-
ments” on page 47 for more details. See also “Uninstalling Previous Versions of Electronic Docu-
mentation” on page 47 for instructions on how to uninstall previous versions of the I/A Series
System Electronic Documentation.
4.2.7.1 Installing Series A2 System Electronic Documentation 6.5.1-7.1

To install I/A Series A2 System Electronic Documentation and Adobe Acrobat Reader 5.0 with
Search, proceed as follows:
49
1. Insert the I/A Series A2 System Electronic Documentation CD-ROM in the CD-
ROM drive, and the installation process begins automatically. If I/A Series A2 System
Electronic Documentation does not automatically begin installing, perform the fol-
lowing steps to manually start the process:
a. Click on Start > Run....
b. Type: x:\setup\setup.exe where x is your CD-ROM drive letter.
2. Click the Next button.
♦ If you meet the specifications for “Software Requirements” on page 47, and do
not wish to install Adobe Acrobat Reader 5.0 with Search (or if you have previ-
ously installed Adobe Acrobat Reader 5.0), leave the box next to “Adobe Acrobat
Reader 5.0” unchecked and click Next. Skip Step 3, and continue to Step 4.
♦ If you want to install Adobe Acrobat Reader 5.0, go to Step 3.
3. Follow the screen instructions and make the following selections, for installing Adobe
Acrobat Reader 5.0:
a. Check the box next to “Adobe Acrobat Reader 5.0” and click Next. If you already
have an earlier version of Acrobat Reader installed, you can simply install Adobe
Acrobat Reader 5.0 over it.
b. Continue to follow the instructions.
4. Follow the installation instructions until the last screen indicates:
♦ I would like to view the README file.
♦ Run I/A Series 6.5.1-7.1 K0173TQ-M.
5. Click Finish to complete the installation, being sure to select Run IA Series
6.5.1-7.1 K0173TQ-M, if desired.
NOTE
To minimize disk space usage, the documentation files on the CD-ROM are not
installed locally, and are instead accessed directly from the CD-ROM. You must
insert the I/A Series A2 System Electronic Documentation CD-ROM in the CD-
ROM drive prior to starting I/A Series A2 System Electronic Documentation.
4.2.7.2 Starting I/A Series A2 System Electronic Documentation

To start I/A Series A2 System Electronic Documentation at any time:
1. Verify that the CD-ROM is inserted in the CD-ROM drive.
2. Select: Start > Programs > IA Series Documentation > IA Series 6.5.1-7.1
(K0173TQ-M).
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.
50
4.2.7.3 Browsing the User Documentation

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

In order to search I/A Series A2 System Electronic Documentation, you must have a search version of
Adobe Acrobat (4.0 or higher). In addition, it is necessary to go into Adobe Acrobat Reader to set
specific preferences as well as add the I/A Series 7.1 (K0173TQ-M) search index.
4.2.7.4.1 Set up Preferences for Searching

Adobe Acrobat Reader 4.0, which is not shipped with I/A Series 6.5.1-7.1 (K0173TQ-M), and
Adobe Acrobat Reader 5.0 have different preference setup instructions, outlined below.
The following preferences need to be set in Adobe Acrobat Reader 4.0:
1. To have multiple windows open at the same time,
a. Select File > Preferences > General.
b. Make sure that “Open Cross-Document Links in Same Window” is unchecked.
2. To allow the search and results windows to appear on top of the main window when
searching,
a. Select File > Preferences > Search.
b. Make sure that “Hide on Search” and “Hide on View” are unchecked.
3. To enable web links within Adobe Acrobat,
a. Select File > Preferences > Web Link.
b. Click Browse and locate the executable for the web browser. For example, the path
for Internet Explorer 5.1is
C:\Program Files\Plus!\Microsoft Internet\IEXPLORE.EXE.
c. Click Open.
51
d. Click OK to close the window.

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

The Acrobat Reader, by default, searches its own index titled “Acrobat 4.0 Online Guide” or
“Acrobat 5.0 Online Guide,” depending on which version you use. In order to search the docu-
ments on the I/A Series 6.5.1-7.1 (K0173TQ-M) CD-ROM, the search index for the document
set needs to be added.
To add the I/A Series 7.1 search index using Adobe Acrobat Reader 4.0 or 5.0:
♦ Select Edit > Search > Select Indexes.
♦ Click Add. This opens a browse window.
♦ Go to the CD-ROM drive containing the CD-ROM K0173TQ-M.
♦ Double click on the file index71.pdx to add it to the searchable indexes.
♦ Click OK.
4.2.7.5 Search
To start a search of the I/A Series A2 System Electronic Documentation, do the following:
♦ Click on Edit > Search > Query
OR
♦ Click on Search icon (binoculars and paper) from the icon tool bar.
The search command allows you to perform full-text searches of the I/A Series PDF documenta-
tion set using the search index created for I/A Series 7.1 (K0173TQ-M) whereas the Find com-
mand allows you to search only a single document. Refer to the Acrobat Guide via the Help
button in Adobe Acrobat for a complete explanation of the package and for specific search capa-
bilities and techniques.
To perform a full-text search:
1. Select Edit > Search > Query.
2. Type one or more keywords such as a document title, a B0 number, or phrase that
describes what you want.
3. Select Search. This command performs the search and then displays the documents
containing your keyword(s).
4. Double click on the document title that seems to contain the desired information.
The document opens on the first match within the document.
52
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.
4.2.7.6 Advanced Search

For a more complete explanation of the search and advanced search capabilities, refer to the
Acrobat Guide available from the Help button within Adobe Acrobat Reader.
53
54
5. Installing V7.1 Release Update
on 50 Series
This chapter describes the procedure for the installation of the V7.1 release update software on
Model 51F (P79) and Model 51G (P80) workstations.
V7.1 Preinstallation V7.1 Software Installation V7.1 Postinstallation

(for existing V7.0
stations only*)
Back Up Perform Release Restore CSA

Hard Disk Update to V7.1 Files, if Required
Save Control Perform Load Control

Databases (SaveAlls) Installation of Databases
Optional Packages
from Diskette
Save Customized Perform EEPROM
Files Update
Reboot Stations,
Perform Initialization,
Back Up CSA and LoadAll if required Restore Customized
Files (if moving) Files
Back Up
Hard Disk
Add to Your
Configuration
* For V7.0 preinstallation and Day 0 software installation procedures, refer

to V7.0 Installation Procedures (B0400QE).
Figure 5-1. 50 Series Release Update Installation Procedure
5.1 Introduction
This chapter addresses installation procedures that allow you to upgrade an existing Model 51F
(P79) or Model 51G (P80) workstation to V7.1. This is a release update installation and not a
Day 0; the steps shown in the following paragraphs are listed in the order that they should be per-
formed.
If you are considering using the on-line upgrade procedures, you should contact the Customer
Satisfaction Center for additional software installation requirements.
55
B0400QM – Rev A 5. Installing V7.1 Release Update on 50 Series
If your Model 51F (P79) or Model 51G (P80) workstation is not at I/A Series A2 software
Version 7.0, you must perform a Day 0 installation of V7.0 software prior to performing the
release update procedure to V7.1.
5.2 Preinstallation Procedures

Verify in Chapter 2 “UNIX System Setup” that you have all the required media and
documentation.
If you have just completed the steps in the chapter titled “50 Series Day 0 Installation Procedures”
in V7.0 Installation Procedures (B0400QE), proceed directly to “Software Installation” on page 57.
If you are currently upgrading a V7.0 workstation to V7.1 software, review the following subsec-
tions. It is recommended that you back up your hard disk, perform a SaveAll, save customized
files, and back up CSA files for safety purposes. It is mandatory that you move CSA software if
you cannot upgrade the CSA host workstation to V7.1 at this time. Moving CSA between hosts
requires that you back up and restore the CSA files where indicated in the following procedures.
Refer to “Compound Summary Access (CSA)” on page 46 for additional information on backing
up, restoring, or moving CSA.
5.2.1 Backing Up Hard Disk

Before performing a release update to V7.1 software, it is recommended that you back up your
hard disk. To back up the hard disk, see “Hard Disk Drive and Miscellaneous System Administra-
tion Procedures” in System Administration Guide (Solaris 8 Operating System) (B0400DU).
5.2.2 Saving Control Databases (SaveAlls)

Before performing a release update to V7.1 software, it is recommended that you save control
databases. Save the databases for all control stations, gateways, and volumes. If you want to
upload the latest settable parameters from the control station, perform the upload before
performing the SaveAll. If the SaveAll operation requires more than one diskette, label each dis-
kette with the diskette number and quantity, for example, 1/2, 2/2.
See “SaveAll” in the “Menu Bar Functions” chapter and/or “Upload” in the “Compounds, Blocks,
and ECBs” chapter of Integrated Control Configurator (B0193AV).
5.2.3 Saving Customized Files

During release updates, some files are rewritten or replaced. Before performing a release update to
V7.1 software, it is recommended that you save any customized files. If you customized any files
listed in Appendix A “Files to Back Up/Restore”, save them before continuing with the
installation.
5.2.4 Backing Up CSA Files

Back up the CSA files using the CSA_Save utility described in “Compound Summary Access
(CSA)” of V7.0 Upgrade Considerations (B0400QD).
56
5. Installing V7.1 Release Update on 50 Series B0400QM – Rev A
5.3 Software Installation

Perform procedures in the following subsections to upgrade to V7.1 software.
5.3.1 Performing a Release Update to V7.1

Prior to installing software on a P79 or P80 workstation, make sure that the workstation is con-
nected to a functioning Redundant Control Network Interface (RCNI) with the correct letterbug
installed. Refer to Control Network User’s Guide (B0400DV) and the machine-specific document
shipped with your processor for installation details.
1. Close all windows, such as System Management Display Handler (SMDH),
Integrated Control Configurator, and so forth.
2. Stop all applications, such as FoxAMI™, Historian, AIM*Historian, and so forth, if
configured.
For FoxAMI software, type the following in a VT100 window:
cd /opt/fox/ami/bin
ami_cmd stopami <ami instance name>
To determine <ami instance name>, check /opt/fox/ami/local_instance.
To stop AIM*Historian, refer to Information Suite AIM*Historian User’s Guide
(B0193YL).
3. Enter the software installation environment. Choose one of the following methods:
NOTE
If you are installing an AP51F, make sure the monitor, keyboard, and mouse are
connected to the station. If they are not, connect them now.
AP51F (with monitor, keyboard, and mouse directly connected)

a. Enter root and gnomes for the login and Password prompts.
b. Enter the software installation environment by typing:
cd /usr/fox/swi
installap
NOTE
In the command tool window, access and select options as
follows: in the menu bar, use the initial letter of the function
to select; in pull-down menus, use the up and down arrows to
highlight the function and the Enter key to select the
function.
or
57
WP51F, AW51F, and AW51G

a. Select Sys > Change_Env > Proc_Eng_Env.
or
Select File > Change Environment > Process_Eng and click OK (from
the FoxView display manager).
b. Select Config > Install_WP or Install_AW.
4. Select Install Software > Release Updates.

5. Select INSTALL from the dialog box to start; at the Insert media #10091 prompt,
insert the V7.1 Media Distribution Diskette (K0175ZF) and select LOAD.
NOTE
You may see a dialog box Check for Files to be Archived. Select NO.
6. Insert the V7.1 P79/80 Workstation Solaris Release Update CD-ROM (K0175ZJ)
when prompted, and select LOAD.
7. Insert the V7.1 Revision Level Diskette(s) (#11001) (K0175ZG) when prompted,
and select LOAD.
8. After the release media have been installed, Running Post-Process Script displays
and the station returns to the software installation screen.
9. View the software install logs to verify that the release update installation was
successful.
a. Select Log Review > Display Installation Log.
b. Select the log that corresponds to this installation, that is, the most recent log.
c. Select Show selected log. Click Nxt to page down to view the log.
Notes:
♦ You may see warnings if certain parameters are not configured (such as com-
munication processor ports). These warnings are normal. Do not confuse
them with failures.
♦ The message Reinstall Operating System reports for each hosted station,
but only the station types listed in Table 2-6 on page 39 are installed.
♦ The FoxGuard Manager package lists as having been installed; however, the
FoxGuard Manager package is not included in this release.
♦ If you have any software packages that failed to install, call the Customer
Satisfaction Center for assistance.
♦ If an indication similar to OS6FS1 Core file found in “/” is listed, deter-
mine which process generated the core file by typing the following in a VT100
session:
file /core*
If the core file is from omclbsvr, it is benign and can be removed.
10. If no errors are listed in the log, select Return and Quit to exit the software installation
environment.
11. Remove the media from the CD-ROM and diskette drives.
58
12. Reboot the station after completing the installation.

13. If desired, install FoxView/FoxDraw 9.0 from the FoxView/FoxDraw 9.0 CD-ROM.
NOTE
The FoxView and FoxDraw software packages are not included on the V7.1 Solaris
CD-ROM; you must install these packages from the FoxView/FoxDraw 9.0 CD-
ROM. Refer to Table 2-4 for information on the FoxView/FoxDraw 9.0 kits, which
are optionally available with I/A Series Version 7.1 software.
5.3.2 Rebooting Hosted Stations

If you are performing an On-Line Upgrade, do not reboot control stations at this time. You must
follow the procedures of On-Line Upgrade (B0193RE).
If you are not performing an On-Line Upgrade, perform the following:
1. Reboot hosted stations as necessary. See Table 2-6 on page 39 to verify which station
images have changed for V7.1.
! CAUTION
1. Use extreme caution when rebooting control stations.
2. Use extreme caution when rebooting Carrierband LAN stations. Consider the
reactions to the temporary loss of peer-to-peer connections and secure operations
such as the SENDCONFIRM command used by sequence blocks.
2. You must perform an EEPROM update on all stations that are not at the revision level
specified for V7.1 (for example, the Micro-I/A station). Refer to Appendix B
“EEPROM Revision Levels” for V7.1 EEPROM revision levels, and instructions to
determine the EEPROM version and perform an EEPROM update.
5.4 Postinstallation Procedures

5.4.1 Setting Date and Time
NOTE
Perform the following procedure only once on a new workstation.
1. From the I/A Series initial display, access System Management displays from the
System button (FoxView), or by picking Sys > Sys_Mgmt (Display Manager).
2. From the System Monitor display, select the Time button to access the Set Date and
Time screen. Set the current date and time.
59
5.4.2 Restoring CSA

Restore the CSA files that you backed up in “Backing Up CSA Files” on page 56 if:
♦ Upgrading to V7.1 included a Day 0 installation of V7.0 software, or
♦ You moved your CSA host to support the upgrade.
When restoring CSA files, use the CSA_Merge utility described in “Restoring CSA (CSA_Merge)
on 50/70 Series Stations” in V7.0 Upgrade Considerations (B0400QD).
Refer to “Compound Summary Access (CSA)” on page 46 for additional information on restor-
ing CSA.
5.4.3 Loading Control Station Databases

A LoadAll is not required if you are upgrading a V7.0 workstation to V7.1. However, if you had
to perform a Day 0 installation of Version 7.0 I/A Series software on this workstation, you must
perform a LoadAll to reinstall the control databases.
5.4.3.1 Loading Databases During an On-Line Upgrade

If you are performing an on-line upgrade from V7.0, when the On-Line Upgrade (B0193RE) doc-
ument directs you to Chapter 3 or 4, follow the procedures in Chapter 3 “FTCP Takeover – No
LoadAll Required” in On-Line Upgrade (B0193RE).
If you are performing an on-line upgrade from pre-V7.0 software, do not perform a LoadAll at
this time. Instead, be sure you are following the procedures in On-Line Upgrade (B0193RE),
which uses the Virtual Checkpoint Function to perform a LoadAll. When the On-Line Upgrade
(B0193RE) document directs you to Chapter 3 or 4, follow the procedures in Chapter 4 “FTCP
Takeover – LoadAll Required” in On-Line Upgrade (B0193RE).
5.4.3.2 Loading Databases During an Off-Line Upgrade

A LoadAll is not required if you are upgrading a V7.0 workstation to V7.1 off-line. However, if
you are performing an off-line upgrade from a pre-V7.0 release of I/A Series software, you must
perform an Initialize, Reboot (if not already done), and LoadAll of the databases of control sta-
tions, gateways and volumes. See Integrated Control Configurator (B0193AV) for Initialize and
LoadAll instructions.
5.4.4 Performing EEPROM Updates

You must perform an EEPROM update on all FBMs and control stations that are not at the revi-
sion level specified for V7.1. Refer to Appendix B “EEPROM Revision Levels” for V7.1
EEPROM revision levels and instructions to determine the EEPROM version and perform an
EEPROM update.
5.4.5 Restoring Files

If you had to perform a V7.0 Day 0 installation on this workstation, refer to “Day 0 Installation
of V7.0 Software Performed”, below. If you are currently upgrading a V7.0 workstation to V7.1,
refer to “Upgrade from V7.0 Software Performed” on page 61.
60
5.4.5.1 Day 0 Installation of V7.0 Software Performed

For additional information on restoring and reinstalling, see V7.0 Upgrade Considerations
(B0400QD).
If you had to execute a V7.0 Day 0 installation on this workstation, perform the following:
♦ Restore application databases, display-related files, and system-related files (that is,
standard I/A Series files) saved in “Saving Invensys Foxboro Application Databases” in
the “Preinstallation Considerations” chapter of V7.0 Upgrade Considerations
(B0400QD).
♦ Recustomize the specially noted files in the appendix titled “Files to Back
Up/Restore,” of V7.0 Upgrade Considerations (B0400QD), rather than overwriting the
new file with the contents of the old file.
♦ Restore any applications, third-party packages, and database files saved in “User
Applications and Third-Party Package Files” in the “Preinstallation Considerations”
chapter of V7.0 Upgrade Considerations (B0400QD).
♦ Restore the customized files that you saved in the appendix titled “Files to Back
Up/Restore” in V7.0 Upgrade Considerations (B0400QD).
5.4.5.2 Upgrade from V7.0 Software Performed

If you are currently upgrading a V7.0 station to V7.1, restore the customized files that you saved
in “Saving Customized Files” on page 56 and refer to Appendix A “Files to Back Up/Restore”.
5.4.6 Backing Up Hard Disks

After performing a release update to V7.1 software, it is recommended that you back up your
hard disk. To back up the hard disk, see “Hard Disk Drive and Miscellaneous System Administra-
tion Procedures” in System Administration Guide (Solaris 8 Operating System) (B0400DU).
5.4.7 Adding to Your Configuration

If you want to add new stations or features of V7.1 to your current configuration, refer to “System
Definition 2.4.1” on page 6 for information to help you properly prepare for the installation.
! CAUTION
Do not re-install the V7.1 Revision Level Diskettes, if prompted.
61
62
6. Installing V7.1 Release Update
on 70 Series
This chapter describes the V7.1 release update software installation procedure for the
Model 70P (P92) workstations.
V7.1 Preinstallation V7.1 Software Installation V7.1 Postinstallation

for existing V7.0
installations only
Back Up Perform Release Restore CSA

Hard Disk Update to V7.1 Files, if Required
Save Control Reboot Stations, Load Control

Databases (SaveAlls) Perform Initialization, Databases
and LoadAll if required
Save Customized Perform EEPROM

Files Update
Back Up CSA
Files (if moving) Restore Files
Install
Service Pack 5 Back Up
if required Hard Disk
Add to Your
Configuration
* For V7.0 preinstallation and Day 0 software installation procedures,

refer to V7.0 Installation Procedures (B0400QE).
Figure 6-1. 70 Series Release Update Installation Procedure
6.1 Introduction
This chapter addresses installation procedures that allow you to upgrade an existing Model 70P
(P92) workstation to V7.1. This is a release update installation and not a Day 0; the steps shown
in the following paragraphs are listed in the order that they should be performed.
If you are considering using the on-line upgrade procedures, you should contact the Customer
Satisfaction Center for additional software installation requirements.
If your P92 workstation is not at I/A Series A2 software Version 7.0, you must perform a Day 0
installation of V7.0 software prior to performing the release update procedure to V7.1.
63
6.2 Preinstallation Procedures

Verify in Chapter 3 “Windows XP System Setup” that you have all the required media and
documentation.
If you have just completed the steps in the chapter titled “70 Series Day 0 Installation Procedures”
in V7.0 Installation Procedures (B0400QE), proceed directly to “Software Installation” on page 65.
NOTE
Before performing the release update to V7.1, make sure that you obtain Revision B
of the V7.0 P92 Workstation Redundant Network Windows XP Day 0 CD-ROM
(K0175YS-B) or Revision B of the V7.0 P92 Workstation Non-Redundant Net-
work Windows XP Day 0 CD-ROM (K0175YW-B). To obtain a new V7.0 Day 0
CD-ROM, contact the Customer Satisfaction Center at the contact numbers listed
on page xv.
! CAUTION
Your workstation will crash and will not recover without a Day 0 installation if you
use Revision A of the V7.0 Day 0 CD-ROM to perform Day 1 procedures. Refer to
“Performing Day 1 Procedures Using Revision B of V7.0 Day 0 CD-ROM” on
page 12 for additional information.
If you are currently upgrading a V7.0 workstation to V7.1 software, review the following subsec-
tions. It is recommended that you back up your hard disk, perform a SaveAll, save customized
files, and back up CSA files for safety purposes. It is mandatory that you move CSA software if
you cannot upgrade the CSA host workstation to V7.1 at this time. Moving CSA between hosts
requires that you back up and restore the CSA files where indicated in the following procedures.
Refer to “Compound Summary Access (CSA)” on page 46 for additional information on backing
up, restoring, or moving CSA.

Before performing a release update to V7.1 software, it is recommended that you back up the
hard disk and create a Windows XP Professional “restore point”. 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 machine-specific document supplied
with your processor.
6.2.2 Saving Control Databases (SaveAlls) (AW)

Before performing a release update to V7.1 software, it is recommended that you save control
databases. Save the databases for all control stations, gateways, and volumes. If you want to
upload the latest settable parameters from the control station, perform the upload before perform-
ing the SaveAll. If the SaveAll operation requires more than one diskette, label each diskette with
the diskette number and quantity, for example, 1/2, 2/2.
64
See “SaveAll” in the “Menu Bar Functions” chapter and/or “Upload” in the “Compounds, Blocks,
and ECBs” chapter of Integrated Control Configurator (B0193AV).
6.2.3 Saving Customized Files

During release updates, some files are rewritten or replaced. Before performing a release update to
V7.1 software, it is recommended that you save any customized files. If you customized any files
listed in Appendix A “Files to Back Up/Restore”, save them before continuing with the
installation.
6.2.4 Backing Up CSA Files

Back up the CSA files using the CSA_Save utility described in “Compound Summary Access
(CSA)” of V7.0 Upgrade Considerations (B0400QD).
6.3 Software Installation

Perform procedures in the following subsections to upgrade to V7.1 software.
6.3.1 Performing a Release Update to V7.1

Prior to installing software on a P92 workstation, make sure that the workstation is connected to
a functioning Redundant Control Network Interface (RCNI) with the correct letterbug installed.
Refer to Control Network User’s Guide (B0400DV) and the machine-specific document shipped
with your processor for installation details.
6.3.1.1 70 Series Software Installation Procedure

To perform a release update to I/A Series V7.1 software:
1. Disable the I/A Series software from starting on boot:
a. Ensure that all files are closed, all applications, such as a historian, are exited (not
closed), and the process is in a stable state.
Exit all third-party packages that you are running.
b. From the Windows XP desktop, click start > Settings > Control Panel.
c. From the Control Panel, double-click Foxboro I/A.
The Startup Options for Reboot dialog box appears.
d. In the I/A Series Off group box, click Autologon.
e. Click OK.
NOTE
Before performing the following steps on a Windows XP workstation that has
AIM*AT software installed, be sure that you have properly shut down all AIM *
processes. For instructions, refer to “V7.1 Release Update Procedures for
Windows XP Workstations with AIM*AT Installed” on page 7.
2. Perform the following steps from the FoxView program to reboot the station:
a. Click Change Env. The Change Environment dialog box appears.
b. Select Process_Eng or Softw_Eng from the Environment list, and click OK.
65
c. Click SftMnt > Shutdown/Reboot...> > Shutdown and Reboot.

d. Wait for the computer to shut down and restart.
3. Enter the software installation environment. Perform the following steps:
a. Insert the V7.1 P92 Workstation Windows XP Release Update CD-ROM
(K0175ZH) in the CD-ROM drive.
b. Double-click My Computer, then the E: drive, then the Setup.exe icon.
c. After the Foxboro I/A Series Installation dialog box appears, click Next>.
d. The Foxboro I/A Series Install dialog box appears. Select Install Release
Update and click Next>.
e. Select the network card which I/A Series software is using, for example, [1] 3Com
EtherlinkXL 10/100 PCI For Complete PC Management NIC (3C905C) and
click OK.
NOTE
A Hardware Installation dialog box may appear indicating that the software you
are installing for this hardware has not passed the Windows Logo testing to verify its
compatibility. When offered the Continue Anyway pick, select it to continue.
NOTE
Configuring a Windows XP Workstation as Stand-Alone
When you configure a Model P92 workstation as a stand-alone station (such as an
AW70CP not connected to a network), the I/A Series software installation process
still prompts you to select a network adapter to use with I/A Series software. When
the Network Installation dialog box appears and you are prompted to select a net-
work adapter, select the Microsoft Loopback Adapter if this station is to be a stand-
alone station.
4. The Setup Needs The Next Disk dialog box appears. Insert the Media Distribution
Diskette (#10091) (K0175ZF) and click Load>.
5. The Multiple Media Selection dialog box appears.
a. Check the box labeled Load all remaining packages from CD-ROM, if
available.
b. Click Load From Selected Media>.
66
NOTE
A ReadOnly File Detected dialog box may appear during installation informing
you that one of the following read-only files have been detected:
D:\opt\fox\OS1UC\pkginfo
D:\usr\fox\sp\files\OS1UC
D:\usr\fox\sp\files\OS1UC.mp2
D:\usr\fox\sp\files\ucromb.bin
D:\usr\fox\sp\files\ucromb2.bin
D:\usr\fox\sp\files\addresses\addr.UC
D:\usr\fox\sp\files\param\CP.BIN
D:\usr\fox\sp\files\param\CPFT.BIN
If this dialog box appears for any of the files listed above, click Yes to overwrite the
read-only file.
6. The Setup Needs The Next Disk dialog box appears. Insert the Revision Level dis-
kette(s) (#11001) (K0175ZG) and click Load>.
7. The Setup Complete dialog box appears after several minutes. View the software
install logs to verify that the release update installation was successful.
a. Click View Logs.
b. Review the Setup Log, Pkg Log, and Init Log.
Notes:
♦ You may see warnings if certain parameters are not configured (such as com-
munication processor ports). These warnings are normal. Do not confuse
them with failures.
♦ The message Reinstall Operating System reports for each hosted station,
but only the station types listed in Table 3-5 on page 43 are installed.
♦ The FoxGuard Manager package lists as having been installed; however, the
FoxGuard Manager package is not included in this release.
♦ If you have any software packages that failed to install, call the Customer
Satisfaction Center for assistance.
c. Click File then Exit to return to the software installation program.
8. Perform the following steps to reboot the workstation after completing the
installation:
a. Select Yes, I want to restart my computer now.
b. Remove media from CD-ROM and diskette drives.
c. Click Finish. The station reboots with I/A Series software running.
9. If desired, install FoxView/FoxDraw 9.0 from the FoxView/FoxDraw 9.0 CD-ROM.
67
NOTE
The FoxView and FoxDraw software packages are not included on the V7.1
Windows XP CD-ROM; you must install these packages from the
FoxView/FoxDraw 9.0 CD-ROM. Refer to Table 3-3 for information on the
FoxView/FoxDraw 9.0 kits, which are optionally available with I/A Series Version 7.1
software.
6.3.2 Rebooting Hosted Stations (AW70 Only)

If you are performing an On-Line Upgrade, do not reboot stations at this time. You must follow
the procedures of On-Line Upgrade (B0193RE).
If you are not performing an On-Line Upgrade, perform the following:
1. Reboot hosted stations as necessary. See Table 3-5 on page 43 to verify which station
images have changed for V7.1
! CAUTION
1. Use extreme caution when rebooting control stations.
2. Use extreme caution when rebooting Carrierband LAN stations. Consider the
reactions to the temporary loss of peer-to-peer connections and secure operations
such as the SENDCONFIRM command used by sequence blocks.
2. You must perform an EEPROM update on all stations that are not at the revision level
specified for V7.1. Refer to Appendix B “EEPROM Revision Levels” for V7.1
EEPROM revision levels, and instructions to determine the EEPROM version and
perform an EEPROM update.
6.4 Postinstallation Procedures

6.4.1 Setting Date and Time
NOTE
Perform the following procedure only once on a new workstation.
1. From the I/A Series initial display, access System Management displays from the
System button.
2. From the System Monitor display, select the Time button to access the Set Date and
Time screen. Set the current date and time.
6.4.2 Restoring CSA

Restore the CSA files that you backed up in “Backing Up CSA Files” on page 65 if:
♦ Upgrading to V7.1 included a Day 0 installation of V7.0 software, or
♦ You moved your CSA host to support the upgrade.
68
When restoring CSA files, use the CSA_Merge utility described in “Restoring CSA (CSA_Merge)
on 50/70 Series Stations” in V7.0 Upgrade Considerations (B0400QD).
Refer to “Compound Summary Access (CSA)” on page 46 for additional information on
restoring CSA.
6.4.3 Loading Control Station Databases

A LoadAll is not required if you are upgrading a V7.0 workstation to V7.1. However, if you had
to perform a Day 0 installation of Version 7.0 I/A Series software on this workstation, you must
perform a LoadAll to reinstall the control databases.
6.4.3.1 Loading Databases During an On-Line Upgrade

If you are performing an on-line upgrade from V7.0, when the On-Line Upgrade (B0193RE) doc-
ument directs you to Chapter 3 or 4, follow the procedures in Chapter 3 “FTCP Takeover – No
LoadAll Required” in On-Line Upgrade (B0193RE).
If you are performing an on-line upgrade from pre-V7.0 software, do not perform a LoadAll at
this time. Instead, be sure you are following the procedures in On-Line Upgrade (B0193RE),
which uses the Virtual Checkpoint Function to perform a LoadAll. When the On-Line Upgrade
(B0193RE) document directs you to Chapter 3 or 4, follow the procedures in Chapter 4 “FTCP
Takeover – LoadAll Required” in On-Line Upgrade (B0193RE).
6.4.3.2 Loading Databases During an Off-Line Upgrade

A LoadAll is not required if you are upgrading a V7.0 workstation to V7.1 off-line. However, if
you are performing an off-line upgrade from a pre-V7.0 release of I/A Series software, you must
perform an Initialize, Reboot (if not already done), and LoadAll of the databases of control sta-
tions, gateways and volumes. See Integrated Control Configurator (B0193AV) for Initialize and
LoadAll instructions.
6.4.4 Performing EEPROM Updates

You must perform an EEPROM update on all FBMs and stations that are not at the revision level
specified for V7.1. Refer to Appendix B “EEPROM Revision Levels” for V7.1 EEPROM revision
levels and instructions to determine the EEPROM version and perform an EEPROM update.
6.4.5 Restoring I/A Series Standard Application Databases and

Files
For additional information on restoring and reinstalling, see V7.0 Upgrade Considerations
(B0400QD).
After performing a release update to V7.1 software, it is recommended that you perform a selec-
tive restore from the disk backup tape created in “Backing Up Hard Disks” on page 64.
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 V7.1
files should not be automatically restored to their original locations. Rather restore the files to a
temporary prior release directory, such as /priorrel.
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.
! CAUTION
Keep in mind that you cannot restore a tape made on the internal tape drive of a
Windows NT workstation to a Windows XP workstation; Windows NT and Win-
dows XP internal tape drives are not compatible. If you must restore these files to a
Windows XP workstation, be sure that the files are saved using an external AIT tape
drive or some other medium, for example, a recordable CD. (Model P93
Windows NT workstations have CD-RW drives that could be used to transfer files
via a CD-ROM.)
6.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.

Back up the hard disk and create a Windows XP Professional “restore point”. 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 machine-specific document supplied
with your processor.
6.4.8 Reconciling the Configuration

Reconcile your configuration by following the procedures in “Documenting Your System” of
Hardware and Software Specific Instructions for Model P92*A Workstation (PW340) (B0400HD).
6.4.9 Adding to Your Configuration

If you want to add new stations or features of V7.1 to your current configuration, refer to “System
Definition 2.4.1” on page 6 for information to help you properly prepare for the installation.
! CAUTION
Do not re-install the V7.1 Revision Level Diskettes, if prompted.
70
7. Operational Recommendations
This chapter provides references to assist you in the daily operation of your plant and supplies
procedures for contacting Invensys Foxboro if you have any problems.
For additional information and recommendations on the daily operation of your plant, including
system hardware and installation, system operations and administration, I/A Series workstations,
control, gateways, and Windows XP operating system, refer to V7.0 Operational Recommendations
(B0400QG).
7.1 Performing a Block Copy with a DCI Block

You cannot perform a block copy on a DCI block (a RIN block, for example) using the Integrated
Control Configurator. An attempt to do a block copy with a DCI block results in the error mes-
sage E70 – CANNOT MODIFY PARAMETER.
7.2 Faceplate Changes

The ROUT, IOUT, and PAKOUT faceplates changed with Version 6.4 I/A Series software to
include an “F” to indicate the fail-safe condition. The IOUT block’s faceplate has also been
changed to include the OUTFBK (output feedback option) parameter.
Since these faceplates are embedded in Display Manager customized group displays, you may
need to rebuild any group displays containing the ROUT, IOUT, or PAKOUT blocks for these
changes to take effect.
7.3 Configuring Ramp Actions in Display Manager

Starting with V6.4, you are given the option of disabling the continuous ramp function in Dis-
play Manager. Continuous ramping is defined as pressing and holding down the mouse button on
a graphic object that is configured for ramp function. Pressing and holding the mouse button on
a ramp object results in the configured variable being modified until the mouse button is released.
Starting with V6.4, you are given the option of disabling the continuous ramp function of Dis-
play Manager. When you define the variable “DM_CRAMP” in the file
“/usr/fox/wp/data/wp51_glbls.all” as either “N” or “n”, the continuous ramp function is disabled.
When the variable is defined, a press and hold acts the same as a mouse button click, that is, the
configured variable is modified once. In order to change the value again, you must release the but-
ton and press or click it again.
When the “DM_CRAMP” variable is not defined, Display Manager ramping operates as in previ-
ous releases.
71
B0400QM – Rev A 7. Operational Recommendations
To define the variable:

1. Edit file /usr/fox/wp/data/wp51_glbls.all.
2. In the DM features section, add:
DM_CRAMP=N
3. Save the file.
In order for change to take effect, the workstation must be rebooted.
7.4 Configuring AIM*Historian Instances for Inactive

Tag Names
The AIM*Historian Configurator cannot configure a historian instance with I/A Series tag names
that are defined in CSA but are not active (that is, blocks in the work volume [volwrk] or in miss-
ing CPs). To configure the historian instance for these tags, create an ASCII historian input file
(for example, hist01.inp) as described in the AIM*Historian User’s Guide (B0193YL).
7.5 How to Report Problems

For questions about release notes, contact the Customer Satisfaction Center (CSC). In the
U.S.A., call 1-866-746-6477, e-mail ips.csc@invensys.com or visit http://www.ips.csc.invensys.com.
Outside the U.S.A., contact your local (country) Invensys Foxboro representative company. Please
check the documentation first.
7.5.1 Customer Action Request (CAR) Form and Procedure

The following Customer Action Request (CAR) Form (attached to this document) is to be used
to document a system problem which appears to be a product defect or to formally request an
additional product feature or enhancement. Please include all required information (as specified
by an asterisk *), describing the issue as thoroughly as possible. Also include any appropriate addi-
tional information requested when reporting station failures (see checklists in the following sub-
sections) and any requested files.
In the U.S.A. and Canada, submit this to the Customer Satisfaction Center at the following
address:
Invensys Process Systems
Customer Satisfaction Center, D921, B52-AA
33 Commercial Street
Foxboro, MA 02035
CARs with no file attachments may be faxed to 508-549-4492. This CAR form and the check
lists are also available at http://ips.csc.invensys.com and may be submitted through the website.
Resolved CARs are available at the website for perusal. To request access to the website,
contact your regional service office.
Outside the U.S.A. and Canada, submit the CAR and attachments to your local Invensys Foxboro
representative company.
Upon receipt of the CAR, an acknowledgment is sent to the originator to confirm receipt and
report the assigned CAR number. In addition, an Invensys Foxboro product engineer attempts to
duplicate the reported problem. If additional information is required to duplicate the problem,
72
7. Operational Recommendations B0400QM – Rev A
the originator is contacted. Once duplicated, the CAR is entered into our Engineering Problem
Log. An engineer is assigned to review the problem and determine the solution. If a software edit
is required, a decision is made as to when this change can be incorporated into the system soft-
ware. This information is then sent to the originator. Problems which are not immediately sched-
uled to a specific release remain active in the Engineering Problem Log and are resolved when the
applicable software is next released.
The following subsections provide procedures for contacting Invensys Foxboro if you have any
problems. They also include failure information check lists to help you report the necessary infor-
mation to the CSC.
7.5.2 CP Failure Informational Checklist
Station Information
CP Letterbug:
CP Type (CP10, CP30, CP40, CP60, FT or single, Style A or B):
Host Station Type (AW51F, AW51G, and so forth):
If Fault-Tolerant, Hardware Revision Level of Z-Bus:
Hardware Revision Level of CP Module(s):
Firmware (EEPROM) Revision Level:
Date and Time of the Failure:
Serial Number(s) of Module(s):
Type of Fieldbus (Remote, Local):
Note: All information must correspond to the same date and time period.
Station Block Information for the CP in Normal Operation

If the CP is back on-line, submit the contents of the station block display (must be activated). Sub-
mit a printscreen of this data if possible. If not, note the respective values from the display and
enter them in the following table:
Average CP Load: Average Block Load:
Average I/O Load: Available Memory:
# of Peer-to-Peer: Cumulative Overruns
(for 10 minutes):
73
CP Failure Information
How did the CP fail (one or both sides)? At the time of the failure, what were the colors of each
module’s front LEDs: red/green, red, or green? Did the CP reboot by itself or was a reboot or restart
from Off-Line Diagnostics required?
What type of activity was occurring when the CP(s) failed (for example, ICC manipulation,
SMDH activity, calling a display, and so forth)?
How long did the CP(s) run before the failure?
Have any events occurred on the system in the recent past that could be related to the problem (for
example, software upgrades, addition or deletion of blocks or compounds, or an addition or change
in status of I/O device)?
Does the System Monitor show the CP as failed? Y N

Do displays connect with any data from the CP? Y N
Is there any activity indicated by the LEDs on the Fieldbus Isolators for the CP? Y N
Are the CPs in a nest, rack, enclosure, and so forth that uses battery backup power? Y N
If the CP requires a reboot, can it be rebooted from SMDH or the reboot command? Y N
Are there any peer-to-peer connections between CPs involving the failed CP(s)? Y N
Are there any peer-to-peer connections between CPs across a LAN? Y N
Does the Select screen on any WP show compounds and blocks from the CP? Y N
74
Attach or Copy the Following Information to This Checklist

System messages prior to the time of the failure and/or reboot, and after the station recovered
or was rebooted.
Current SaveAll diskette.
Current and previous CP checkpoint files from /usr/fox/sp/files (include the DB and
BB files):
♦ /usr/fox/sp/files/DB<CPLBUG>.UC
♦ /usr/fox/sp/files/BB<CPLBUG>.UC.
Detailed topology, including nest layouts, FBM types, cabling, node extensions, and so forth.
Station image upload /usr/fox/sysmgm/softmgr/dump/<CPLBUG>.dmp
(or <CPLBUG>.1, .2, .3, .4…) if the files exist at the time of the failure.
File sizes should be similar to the following:
CP10: <CPLBUG>.1 1050684
CP30: <CPLBUG>.1 1050684
<CPLBUG>.2 1050684
<CPLBUG>.3 522044
CP40: <CPLBUG>.1 1050684
<CPLBUG>.2 1050684
<CPLBUG>.3 1050684
<CPLBUG>.4 1045308
CP60: <CPLBUG>.1 1049522

<CPLBUG>.2 1049522
<CPLBUG>.3 1049522
<CPLBUG>.4 1049522
<CPLBUG>.5 1049522
<CPLBUG>.6 1049522
<CPLBUG>.7 1049522
<CPLBUG>.8 1046822
The checksum of each <CPLBUG>.* should be recorded and included in the CAR attach-
ment. (Type sum <CPLBUG>.*.)
75

CP Image information.
♦ For CP10s, type what /usr/fox/sp/files/OS1UC
♦ For CP30s, type what /usr/fox/sp/files/OS1C30
♦ For CP30s, Style B, type what /usr/fox/sp/files/OS1C3B
♦ For CP40s, type what /usr/fox/sp/files/OS1C40
♦ For CP40s, Style B, type what /usr/fox/sp/files/OS1C4B
♦ For CP60s, type what /usr/fox/sp/files/OS1C60.
OS1UC OS1C30 OS1C3B OS1C40 OS1C4B OS1C60
CP10 (_-_-_) CP30 (_-_-_) CP_B (_-_-_) CP40 (_-_-_) CP_B (_-_-_) CP60 (_-_-_)
FTX FTX FTX FTX FTX FTX
SEQ_Proc SEQ_Proc SEQ_Proc SEQ_Proc SEQ_Proc SEQ_Proc
SEQ_Erh SEQ_Erh SEQ_Erh SEQ_Erh SEQ_Erh SEQ_Erh
CIOSOFT CIOSOFT CIOSOFT CIOSOFT CIOSOFT CIOSOFT
BLKCODE BLKCODE BLKCODE BLKCODE BLKCODE BLKCODE
NFD VRTX NFD VRTX NFD VRTX NFD VRTX NFD VRTX NFD VRTX
OM OM OM OM OM OM
IPC IPC IPC IPC IPC IPC
NETWORK TIME NETWORK TIME NETWORK TIME NETWORK TIME NETWORK TIME NETWORK TIME
SMAS - CP10 SMAS - CP30 SMAS - CP30 SMAS - CP40 SMAS - CP40 SMAS - CP40
RDSS RDSS RDSS RDSS RDSS RDSS
EH EH EH EH EH EH
BLKPARMS BLKPARMS BLKPARMS BLKPARMS BLKPARMS BLKPARMS
DBMNT DBMNT DBMNT DBMNT DBMNT DBMNT
APR APR APR APR APR APR
CMX CMX CMX CMX CMX CMX
sum OS1UC sum OS1C30 sum OS1C3B sum OS1C40 sum OS1C4B sum OS1C60
7.5.3 Gateway (GW), Integrator 30, and Allen-Bradley

Station (ABSTA) Failure Information Checklist
Station Information
GW Letterbug:
GW Type:
(MDGW, MDGW30, MBPGW, ABGW, ABGW30, ABSTA,
ISGW30, FT or single):
Module Hardware Revision Level:
Firmware (EEPROM) Revision Level:
Date and Time of the Failure:
76
Station Block Information for the GW in Normal Operation

Average GW Load: Average Block Load:
Average I/O Load: Available Memory:
# of Peer-to-Peer: Cumulative Overruns
(for 10 minutes):
BPC:
GW Failure Information
Does the System Monitor show the GW as failed? Y N
Does the System Monitor show the PLC as failed? Y N
Do displays connect with any data from the GW? Y N
Does the Select screen on any WP show compounds and blocks? Y N
If the GW requires a reboot, can it be rebooted from SMDH or the reboot command? Y N
From SMDH, go to the station peripheral counters and get the counters for the station
and configured PLCs.
time-outs:
inval cmd:
inval resp:
What are the communication parameters?
Baud:
Parity:
Stop Bits:
Data Bits:
For GW Integrator 30, what are the P0970VB switch box settings?
Which cables are used?

GW15 to PLC:
GW30 to P0970VB switchbox:
P0970VB to PLC
Is the PLC directly connected (no modems or proprietary network)? Y N
Number of PLCs configured:
Type of PLC(s):
If Allen-Bradley, type of CAM:

Is there more than one master communicating to the PLC? Y N
77
GW Failure Information
How did the GW fail (one or both sides)? At the time of the failure, what were the colors of each
module’s front LEDs: red/green? Did the GW reboot by itself or was a reboot or restart from Off-
Line Diagnostics required? List or attach any corresponding System Monitor messages that
appeared on the printer, including the date and time of the messages.
example, hardware changes, ICC changes, and so forth)?

System messages at the time of the failure and/or reboot.
Current SaveAll diskette.
Station image upload /usr/fox/sysmgm/softmgr/dump/<GWLBUG>.* if the files exist at the
time of the failure. Verify that the date and time of the file correspond to the GW failure.
For a GW15 there is one file, <GWLBUG>.1. For a GW30, there are three files, <GWL-
BUG>.1, <GWLBUG>.2, and <GWLBUG>.hi. For AB_STATION no dump file is
generated.
Approximate file sizes should be as follows
GW15: <GWLBUG>.1 1050684

GW30: <GWLBUG>.1 1050684
<GWLBUG>.2 1050684
<GWLBUG>.hi 522044
AB_STATION: No Dump File
The checksum of each <GWLBUG>.* should be recorded and included in the CAR attach-
ment. (Type sum <GWLBUG>.* for checksums.)
78

GW Image information:
Enter VT100 mode, type what /usr/fox/sp/files/<GW_TYPE>.
GW_TYPE:
♦ OS1ADH – Allen-Bradley Gateway 15
♦ OS1AB3 – Allen-Bradley Integrator 30
♦ OS1A3 – Allen-Bradley Integrator 30, Style B
♦ MODGW – Modicon Gateway 15
♦ MDGW30 – Modicon Integrator 30
♦ MDGW3B – Modicon Integrator 30, Style B
♦ ISGW30 – INTERSPEC Integrator 30
♦ OS1AB4 – Allen-Bradley Station.
Block diagram of physical setup?
7.5.4 Model 51 System Failure Information Checklist
Station Information
Station Letterbug:
Station Hardware Type:
(Sun Blade 150 = F, Sun Blade 2000 = G)
Station Application Type (AP / AW / WP):
Sun Station Serial Number:
Invensys Foxboro Station P-Code:
I/A Series Software Revision Level:
Station Configuration Information

Amount of Memory (shown at boot time):
Number of Display Heads:
Number of Local Display Managers:
Number of Remote Display Managers:
Annunciator Keyboard(s)? Y N
Touchscreen? Y N
Qwerty Keyboard? Y N
Mouse/Trackball? Y N
USB Extender? Y N
79
Station Configuration Information

Directly Connected Printers? Y N
Serial or Parallel?
Printer Manufacturer:
Printer Model:
Used for:
(for example, alarms or reports)
If the second network is implemented, list the type, description, and protocols.
Standard System Software and Applications

ICC? Y N
System Monitor? Y N
SMDH? Y N
Historian? Y N
number of collection points:
sample rates:
number of reduction groups:
size:
period:
archive information:
Batch? Y N
Batch Version:
SPC? Y N
Report Writer? Y N
OAJ? Y N
Alarm Manager? Y N
OMI? Y N
Other:
Additional Applications
IRIS? Y N
PEC? Y N
Field Scan? Y N
Setpoint? Y N
80
Additional Applications
PI? Y N
MDT? Y N
DMC? Y N
Other:
OM Shared Variable Usage:

Accessed locally? Y N
Accessed remotely? Y N
Via get/set or omlist? Y N
Miscellaneous Questions
Brand of diskettes used:
DOS copies done? Y N
Automount used? Y N
Name Service Used (NIS+, NIS, DNS):
Security used (for example, Kerberos):
Bulk Storage/SCSI Configuration

Number of Hard Drives, Size, External/Internal:
Tape Drive: Y N
Type, Size:
SCSI ID and Position:
Diskette Drive(s): Y N
CD-ROM Drive: Y N
RAID: Y N
RAID Level:
Other: Y N
Installed Cards
Indicate in the table below the slot number that contains the interface card:
Card Type and Abbreviation Model 51F Model 51G
81
Installed Cards
PGX64 Graphics Card (for second monitor)
Serial Controller PCI Card with eight (8) ports
TP 10/100 Mbps Ethernet and MII interface PCI
card
card for Allen-Bradley interface (SLC/05)
card plus MII to AUI adapter for Allen-Bradley inter-
face (PLC5)
TP 10/100 Mbps Ethernet and Ultra-Wide SCSI PCI
card*
System Failure Information (Submit Per Incident)

Date and time of the failure:
How did the system fail? Did the system reboot/crash by itself or was manual reboot with forced
crash required to recover from the failure?
Indicate what was occurring on the user interface at the time of the failure.
Have any events occurred on the system in the recent past that could be related to the problem
(such as, hardware changes/additions, software changes/additions, configuration changes, and
so on)?
List or attach any corresponding System Monitor messages that appeared on the printer, including
the date and time of the messages.
Did the System Monitor show the Model 51 station as failed? Y N

Did the system successfully reboot after the failure? Y N
There are two different reasons why the system may reboot:
1. System crash (Panic).
82
In this case the string “Panic” will be present in the /var/adm/messages file prior to the
normal booting information and, if there is enough free disk space in the
/opt/crash/{letterbug} directory, the files unix.{n} and vmcore.{n} will be generated
after the reboot. (The space should be equal to or greater than 2/3 of the total mem-
ory size of the processor.)
2. Orderly system reboot due to failure of a critical process.
In the event of the failure of a task such as mles, mac_daemon, om_server, om_client,
om_scanner, or others, there will be NO string “Panic” in the messages file prior to
the corresponding reboot information and NO files in /opt/crash/{letterbug}.
Instead, appropriate information relevant to the failure will be contained in the file
/usr/fox/exten/fox_monitor_save. This file should be examined immediately after the
system reboot to see exactly which process has failed. When a system is rebooted, the
existing /usr/fox/exten/fox_monitor_log file is renamed fox_monitor_save and a new
fox_monitor_log file is started, thus, if another failure occurs, the information for the
previous failure is lost.
In addition, a “core” file should be produced in the directory from which the process
was run. Using the Unix “file” command on any “core” file should confirm that it was
created by the process that failed. Also, the date and time of the process failure as
recorded in fox_monitor_save should be the same as the creation date of the core file
as determined by “ls -l core”.

System messages prior to the time of the hang-up and/or reboot (the /var/adm/messages file).
If a diskette was involved in the crash, attach the diskette as is.
Relevant Printscreens.
83

Please provide the following files:
♦ /var/adm/messages
♦ /usr/fox/exten/fox_monitor_save
♦ /usr/fox/sp/lastinst/SYSLVL
♦ /usr/fox/sp/lastinst/QFINFO
♦ System crash dump files unix.n, vmcore.n in the directory /var/crash/<letterbug> or
/opt/crash/<letterbug>, where n=1, 2,...
Remarks:
1. The date and time of the fox_monitor_save file in the directory /usr/fox/exten must
match the date and time of the crash event; the next crash and/or reboot overwrites
this file.
2. The date and time of the unix.n and vmcore.n files must match the date and time of
the crash event.
Please provide the results of entering the following commands:
♦ who -b
♦ vmstat 10 10
♦ ps -eaf
♦ show_params
♦ prtconf
♦ df -kF ufs
♦ /usr/fox/wp/bin/tools/show_win
(C shell version):
♦ setenv INFORMIXDIR /opt/informix
♦ setenv PATH ${PATH}:/opt/informix/bin
♦ tbstat -d
♦ eeprom
84
7.5.4.1 Printscreen Failure Information Checklist

Operation Description Complete
Port Name (LPxx) xx is the number assigned during configuration.
Printer Model Give manufacturer and model.
Self-Test Page Refer to owner’s manual for instructions.
Record LP Printer From vt100.local enter lpstat -pLPxx - l where LPxx is the
Status printer port name from above.
Contents of Insert formatted diskette in diskette drive and enter:
/etc/printers File tar cvf /dev/rfd0 /etc/printers
Printer Connection Direct: AW/WP51 Parallel port
Type Remote: Hosted via CMP10.
Output Sample & ♦ From vt100.local enter:
Copy of Spool files disable LPxx
where LPxx is the port in question.
♦ From the Config menu, select LPxx as the default printer,
then select Palette Display. Ensure that the palette dis-
play is in front and press <CTRL>Print.
♦ tar the files found in the directory /var/spool/<LB> to a
diskette. (LB is the letterbug of the station from which the
printscreen is initiated.)
tar rvf /dev/rfd0 /var/spool/<LB>/*
♦ Eject the diskette and re-enable the printer.
enable LPxx
This should allow the job to print. Save the printer output.
Printscreen Source Please indicate the letterbug and type of station that requested
the printscreen.
In the following graphic, please indicate the location of the printer. Please label it as PTR. If it is
connected to the AW or WP51, please indicate if it is the serial (S) or parallel (P) port. Within
each box please indicate the letterbug and type of processor.
If the printer is connected via a CMP10, please indicate which port number is used and fill in the
switch positions for the P0970VB Configuration Selector. Also please write the letterbug inside
the CMP10 box. If your configuration does not use the P0970VB Configuration Selector, please
include the part numbers of the cables used to connect the printer to the CMP10.
85
S P S P
AW51 WP51
NB NB
CMP10
1 2 3 4
P0970VB
D Cable Socket
1 8 1 8
C C
O O
1 8 1 8
C C
O O
26-Pin Socket
26-Pin Socket
7.5.5 70 Series Failure Information Checklist
Station Information
Station Letterbug:
Station Hardware Type:
Processor Speed (MHz) and Type (for example, Pentium IV):
Installed Memory in MB:
86
Station Information
Are any Service Packs Installed? What level:
Station Application Type (AW or WP):
Manufacturer’s Serial Number:
Invensys Foxboro P-Code and Part Number:
I/A Series Software Level:
Information in /usr/fox/sp/lastinst/trailer.info:
Drive Configuration (SCSI)

Hard Drives Installed (Number, Size, and Type):
Tape Drive Type and Size:
SCSI Controller Type:
Optical Drive Type:
Speed:
Installed Cards
Card Type Model Number Installed? Quantity Installed
Indicate the type and quantity of cards installed in the workstation.
3Com® PCI Ethernet:
PKTX f or A-B communication only (PCI):
Serial expansion card (PCI):
Sound Card:
Dual Monitor Card:
Other:
System Configuration
Does the system have a GCIO?
Is the system connected to the standard I/A Series Nodebus? or Ethernet only?
Are hardware annunciators used? How many?
87
System Configuration
Is a serial alarm printer used? What type? Is it connected to a COM port or serial port expansion
card?
Is a parallel printer used? What type?
Is a PLC connected? What type? How is it connected? Provide the complete topology as an
attachment to this checklist.
Is the system connected to a second (corporate, Allen-Bradley, etc.) network?
What type of network cabling is used?
Is the station connected to the internet?
Describe how your station connects to the network.
88

Date and time of the failure:
How did the system fail? Did the system reboot/crash by itself or was manual reboot with forced
crash required to recover from the failure?
List or attach any corresponding System Monitor messages that appeared on the printer, including
the date and time of the messages.
example, hardware or software changes or additions)?
Did the System Monitor show the 70 Series station as failed? Y N

Did the system successfully reboot after the failure? Y N
89

What application software is installed on the station (for example, AIM*, RSLinx®)? Include
Version number and Revision Level where available. If FoxAPI is being used, indicate the number
and size of the data sets if data sets are being used.
What additional software has been loaded on the station (for example, Microsoft Office)? Include
Version number and Revision Level where available.

System messages prior to the time of the failure and/or reboot.
System crash dump files (*.dmp) in the %SystemRoot% directory. These files are usually
large; save them to tape using Windows XP Backup utility.
Note: The date and time of the crash file must correspond to the date and time of the failure
being reported.
Event Viewer Logs.
The files fox_monitor save and fox_monitor_log in the \usr\fox\exten directory.
Notes:
1. The files must be copied immediately after reboot; the next crash and/or reboot
overwrites these files.
2. The date and time of the files must correspond to the date and time of the failure
being reported.
If a diskette was involved in the crash, attach the diskette as is.
90
Invensys Process Systems B0400QM

Attn: Car Administrator
FAX# 508-549-4492 Customer Action Request
* CUSTOMER : Customer name
ADDRESS : Customer address
SITE # : FieldWatch site number

CUST CONTACT : Customer person to contact
TELEPHONE : Telephone number of customer contact
REFERENCE : Customer reference number
DATE OCCURRED : When did problem occur?
* PRODUCT : Product from list
[I/A Series, INSTRUMENTS]
* VERSION : Software version
* PLATFORM : If I/A Series software, which base product?
(50 Series, 70 Series)
* SUBMITTER : Who is writing up this form?
* SBMTR FAX # : FAX # or E-Mail Address of submitter
FOX CONTACT : Who to contact at Invensys Foxboro
* SOURCE : Where was the problem found? [AREA CO, CUST
SITE, MANUFACTURING, STAGING]
* REPORT TYPE : Type of problem
[PROBLEM, ENHANCEMENT, QUESTION]
* IMPACT : What impact does problem have?
[HEAVY, MODERATE, MINOR, NONE]
* REPRODUCIBLE : Can problem be reproduced?
[ALWAYS, NO, SOMETIMES, DIDN'T TRY]
ATTACHMENTS : Listings, Diskettes, etc.
CONFIGURATION : Number of APs, WPs, CPs, COMMs, etc.
* DESCRIPTION :
* Indicates “Must Enter” field

PRODUCT CATEGORY (For CSC Use Only) B0400QM
PRODUCT TYPE (For CSC Use Only)
91
92
8. Enhancements and Problems
Resolved
This chapter describes the enhancements provided and the problems resolved with the I/A Series
V7.1 software release. The list of resolved problems provides a description of the problem and
the associated Customer Action Request (CAR) number.
8.1 V7.1 Enhancements

Refer to “Release Features and Configurations” on page 103.
8.2 Problems Resolved for V7.1

8.2.1 Workstations
8.2.1.1 Booting Model 51F/G Workstations Without an Attached
Keyboard (CAR #1004337)
Problem Model 51F and Model 51G workstations running V7.0 software did not
boot without a keyboard attached. With V7.0 software, you needed to
remove two lines from the null_kbd script in /usr/openwin/server/etc to
allow the Model 51F and 51G stations to boot without a keyboard.
Resolution This issue is corrected with V7.1 I/A Series A2 software. You do not need to
modify the null_kbd script; the Model 51F and Model 51G workstations
successfully boot into OpenWindows without a keyboard attached.
8.2.1.2 Intelligent Networking with Security Routers (CAR #1001455)
Problem Model 51B workstations stop communicating over the Nodebus, although
they are still accessible on the second Ethernet network. This problem
occurs because COMEX does not handle Novell packets, type IPX 99 or
type IPX 8137. This cause of Model 51 communication loss over the Node-
bus can be avoided with the use of Security Routers.
Resolution This problem is corrected with V7.1 I/A Series A2 software.
93
B0400QM – Rev A 8. Enhancements and Problems Resolved
8.2.2 I/O Gates

8.2.2.1 I/O Gate Modification (CAR #1004077)
Problem A problem occurs when you turn off compounds with a large number of
rapidly updating I/O Gate input points, for example, 200 or more input
points updating every 0.5 second. Turning off such a compound may cause
the compound processor to report an access violation and crash.
Resolution This problem is corrected with QuickFix #1004077B.

In order for any I/O Gate products to operate properly with V6.5.1 or V7.1
I/A Series software, Version 1.8 of the file “gpgate.dll” is required. This file
ships with the various I/O Gate driver packages or is available via
QuickFix #1004077B. Refer to “gpgate.dll Requirement for I/O Gates” on
page 15 for details.
8.2.3 Integrated Control Configurator

8.2.3.1 Shrink Function and Workfile Corruption (CAR #992193)
Problem The Integrated Control Configurator’s “Shrink” function compresses the

current ICC database to save disk space. If there is not enough disk space
available to perform this operation, the Shrink function fails with no error
message, and the workfile is corrupted.
Resolution The Integrated Control Configurator’s Shrink function has been corrected
with V7.1 I/A Series A2 software to check the available free disk space
before starting the Shrink function. If the size of the free disk space is less
than the size of the workfile, the error message “No free disk space,
Shrink function failed” pops up, and the workfile is unharmed.
! CAUTION
Sometimes the free disk space may only be slightly larger than the workfile size.
Since the operating system also uses a portion of the free disk space to perform its
operations, this free disk space is very dynamic. This could cause a further reduction
in free disk space, and could ultimately cause a corruption in the workfile.
94
8. Enhancements and Problems Resolved B0400QM – Rev A
8.2.4 Integrated Control Blocks

8.2.4.1 Incorrect Sequence Block Operation (CAR #2000043)
Problem Every sequence block should execute its sequence code (HLBL statements)
only when the block’s ACTIVE parameter is TRUE (that is, when the block
is in the ACTIVE state). But when the ACTIVE parameter of a IND,
MON, or DEP block is connected by a Boolean invert operator “~”, the
operation is incorrectly reversed: the sequence code executes when the block
state is INACTIVE and is not executed when the block state is ACTIVE.
The Detail Display shows the block state (ACTIVE or INACTIVE)
correctly.

When the ACTIVE parameter of an IND, MON, or DEP block is con-
nected by a Boolean invert operator, the sequence code executes when the
block is ACTIVE, and does not execute when the block is INACTIVE.
8.2.4.2 Non-Connectable REPTIM Parameter (CAR #1000892)
Problem In the PTC and MATH blocks, the REPTIM parameter is improperly
secured. If the compound containing these blocks is turned ON, the REP-
TIM parameter is not connectable. The error message “Error E41 Unlinked
Input Secured Check OM Lists - Failed” appears. REPTIM can be con-
nected if the compound is OFF.

In the PTC and MATH blocks, the REPTIM parameter is connectable
when the compound containing these blocks is turned ON. No error mes-
sage appears.
8.2.4.3 Calculation Errors in CALCA (CAR #1001335)
Problem With pre-V7.1 and pre-V6.5.1 software, the CALCA block performs an
incorrect calculation when subtracting a constant number greater than 63
when RI01 is 99. For example, the following code would execute correctly,
giving a result of 36:
♦ SUB RI01 63 OUT RO01
Whereas the following code would execute incorrectly, giving a result of
163:
♦ SUB RI01 66 OUT RO01
Resolution This calculation in the CALCA block is corrected with V7.1 I/A Series A2
software.
95
8.2.4.4 Setting PRIBLK in the CHARC Block (CAR #1001430)
Problem Integrated Control Block Descriptions (B0193AX) should be modified to state

that you need to have unique Y values in order to successfully configure
PRIBLK=1 in the CHARC block.
Resolution The following paragraph appears in the chapter titled “CHARC –

Characterizer Block” in Revision J and later of Integrated Control Block
Descriptions (B0193AX):
“A unique result of the inverse interpolation is needed for the back calcula-
tion, and this will only be possible if the “Y” coordinates of the breakpoints
are all either actually increasing or actually decreasing (not monotonically).
If PRIBLK is set true in the block, this is verified at validation time. Failure
of this validation produces an appropriate message in ERCODE, and the
CHARC block is set Undefined.”
8.2.4.5 Incorrect Reports of Alarm Types (CAR #1001919)
Problem When you inhibit alarms of a BLNALM block residing in a Modicon Gate-
way, and you generate a Process Summary report, alarm types appear on the
report as LLABS and should report as STATE.
Resolution Alarm types are correctly reported with V7.1 I/A Series A2 software.
8.2.4.6 Process Alarm Printing Problems (CAR #1003102)
Problem If the INHPRT parameter is set to 1 in the STATION block, a problem

occurs where process alarm messages are not sent to the alarm printer
attached to a communication server. Consecutive alarm messages that are
destined to the communication server are packaged into one IPC message.
If one of the alarm types in this IPC message is an ALARM_ENABLE or
ALARM_DISABLE type, and INHPRT = 1, the communication server
discards all the messages, and both the process alarms and the alarm
inhibit/uninhibit messages are not printed.
Resolution This problem is corrected with V7.1 I/A Series A2 software. When
INHPRT is set to 1 in the STATION block, process alarms are printed to
the alarm printer, but ALARM_ENABLE or ALARM_DISABLE messages
are not.
96
8.2.4.7 Accessibility of ACTION in ECB15 (CAR #1001943)
Problem The Equipment Change Action parameter (ACTION) is a packed boolean

data store that is a request from the Station Manager to perform an action
related to a particular FBM. The ACTION parameter should be settable.
However, trying to set the ACTION parameter of an ECB15 (software
interface for Allen-Bradley Programmable Logic Controllers) results in OM
error 15, which means the parameter is not settable.
Resolution The ACTION parameter is settable with V7.1 I/A Series A2 software.
8.2.4.8 CALC/CALCA Block Syntax Verification (CAR #1001636)
Problem The CALC and CALCA blocks are not checking the syntax of steps and are
accepting invalid operands without generating an error message. For exam-
ple, typing IN I001 (instead of the correct IN IO01 or IN II01) does not
generate any error message.
Resolution With V7.1 I/A Series A2 software, CALC/CALCA blocks check for invalid
syntax and generate configuration error messages.
8.2.4.9 Accumulation Loss in ACCUM Block (CAR #1002142)
Problem The ACCUM block loses one scan accumulation when going out of
HOLD. The ACCUM block should start the accumulation from the scan
at which the HOLD is removed.

The ACCUM block does not drop one scan accumulation when going out
of HOLD.
97
8.2.5 Micro-I/A Station, Dual Ethernet Monitor

8.2.5.1 Dual Ethernet Monitor Error Messages (CAR #1002188)
Problem In dual Ethernet systems with Micro-I/A stations using Cable A in the
“Auto” mode, disconnecting the CA Nodebus interface (NBI) cable should
cause the dual Ethernet monitor application to report CA AW COMM LOSS in
the “Station State” message box and Switching to Cable B in the “Events”
message box.
Occasionally, the dual Ethernet monitor reports that a Micro-I/A station is
Switching to Cable A in the “Events” message box, when the Micro-I/A
station is actually switching to Cable B, and vice-versa.

When the dual Ethernet Micro-I/A stations are on-line and using the pri-
mary Cable A, disconnecting the CA NBI from the Nodebus results in the
following messages in the dual Ethernet monitor:
♦ CA AW COMM LOSS in the “Station State” message box.
♦ Switching to Cable B in the “Events” message box.
Disconnecting the CB NBI from the Nodebus and restoring the CA NBI
results in the following messages in the dual Ethernet monitor:
♦ CB AW COMM LOSS in the “Station State” message box.
♦ Switching to Cable A in the “Events” message box.
8.2.5.2 Loss of Carrier on Backup Cable (CAR #2000332)
Problem The dual Ethernet monitor successfully reports the loss of communication
of the primary (active) cable, but does not report the loss of communica-
tion of the backup cable.
After a failure of the active cable on a dual Ethernet system where the
backup cable is also failed, communications to and from the Micro-I/A sta-
tions attached to these cables are lost.

The loss of carrier on the backup cable is detected, and the dual Ethernet
monitor displays the following:
CABLE: A
STATE: NORMAL
ERRORS: CABLE B Carrier Loss
No cable switching is necessary; the selected primary cable remains “A” for
this station. When the carrier loss condition is cleared, the error message is
cleared from the dual Ethernet monitor.
98
8.2.5.3 Processing of I/A Series Output Changes in Field Devices

(CAR #1002864)
Problem There is a problem resetting I/A Series output changes that occur faster
than they can be processed in the field device. This can result in cases where
not every output in a system is written to the field device.
8.2.6 Object Manager

8.2.6.1 om_scanner Memory Violations (CAR #1002790)
Problem A memory violation occurs when om_scanner is processing an open_var

(variable in a list) with an invalid name.
8.2.6.2 Object Manager List Corruption (CAR #1004002)
Problem When removing, adding, or activating objects in an Object Manager list, it

is possible that you can run out of omlists on the hosting AW, or that the
existing lists can become corrupted.
8.2.7 Process Summary Report Configurator

8.2.7.1 Process Summary Report Configurator Block In Alarm Reports
(CAR #1002162)
Problem The Process Summary Report Configurator (PSR) does not generate a list
of blocks in alarm when selecting the CP60 as the control station.
Resolution This problem is corrected with V7.1 I/A Series A2 software. PSR correctly
generates “Block In Alarm” type reports.
99
8.2.8 Third-Party Software

8.2.8.1 Bristol Wind/U Shared Library File Correction (CAR #1004123)
Problem A problem occurs in V7.0 Solaris 8 workstations running applications using

Bristol Windu/U. When the File -> Open dialog box is invoked, the appli-
cation crashes. This problem occurs because an older version of the
Wind/U shared library file was included with V7.0 media.
Resolution A corrected version of the Wind/U shared library file is included with V7.1
I/A Series A2 software, and the problem no longer occurs.
8.2.9 FBMs
8.2.9.1 SMDH Indication of EEPROM Update Status (FBM221)
(CAR #1002048)
Problem During an EEPROM update to an FBM221, SMDH does not give any
indication that the EEPROM update operation is in progress.
Resolution This problem is corrected with V7.1 I/A Series A2 software. The DEVICE
STATE field in the FBM221 Equipment Information display shows
EE Updating while the EEPROM update operation is taking place.
8.2.9.2 FCM10E Cable Switching and Reporting (CAR #1004216)
Problem Under certain conditions, the information presented on SMDH displays

and at the system printer regarding PIO bus state is incorrect. Specifically, it
can happen that when PIO Bus B has failed, SMDH indicates that it is Bus
A that has failed.
Resolution This problem is corrected with V6.5.1 I/A Series software with
Version 1.13 of iom82.
8.2.10 Control Stations

8.2.10.1 End of List Null Pointer Handling (CAR #1003370)
Problem Block list handling does not identify and handle the end of list null pointer.
This may cause a CP station to crash with a memory violation.
Resolution Handling of end of list null pointer errors are corrected with V7.1
I/A Series A2 software.
100
8.2.10.2 Control Processor Memory Corruption (CARs #1003828 and

#1003742)
Problem Memory corruption in a CP60, CP40B, AB30 Gateway Style B, MG30

Gateway Style B, Device Integrator 30 Style B, or Micro I/A station can
occur if the processor is subject to a rapid succession of requests to perform
Object Manager deletions and additions without sufficient delay between
these deletions and additions.
8.2.10.3 Green-Death State of CP60 (CAR #2000485)
Problem Using om_setval, if a value with a status of 0 is written to the compound’s

station block parameter GR4, the CP60 stops communicating to the Node-
bus (green-death state), but still executes the control blocks and handles the
I/O.
Resolution This problem is corrected with V7.1 I/A Series A2 software. om_setval
checks the validity of input ‘status’.
8.2.11 Integrators
8.2.11.1 Integrator 30 Style B Off-Line Diagnostics (CAR #1002524)
Problem Performing an off-line diagnostic test to a single module in a fault-tolerant

pair of Integrator 30 Style B modules can upset communication from the
modules to the field devices, requiring a reboot of the modules to recover.
Resolution This problem is corrected with V7.1 I/A Series A2 software. During off-line
diagnostics, the shadow module now takes over without losing communica-
tion to the PLC.
101
8.2.12 Display Manager

8.2.12.1 Displaying the On-Line Trend Configurator from Display
Manager (CAR #1003660)
Problem If you click on a trend in Display Manager when CSA is unavailable (for
example, if the CSA server node is down), there is a significant delay before
the On-Line Trend Configurator displays.
Resolution This problem is corrected with V7.1 I/A Series A2 software. There is no
delay accessing the On-Line Trend Configurator from Display Manager.
102
9. Release Features and
Configurations
This chapter presents information to familiarize you with the scope, functions, and capabilities
of the products associated with the V7.1 I/A Series release.
9.1 Version 7.1 System Features, Benefits, and

Enhancements
V7.1 introduces new features to the I/A Series A2 platform. The following subsections provide an
overview of the major enhancements, features, and benefits of the I/A Series Release 7.1 products
including:
♦ A new Virus Checking Solution
♦ Modbus Communication Interface Module (FBM224)
♦ HART Communication Input/Output Interface Modules (FBM214, FBM215,
FBM216, and FBM218)
♦ PROFIBUS-DP Communication Interface Module (FBM223)
♦ FOUNDATION Fieldbus H1 Communication Interface Modules (FBM220/FBM221)
♦ SPECTRUM Migration and Cluster I/O
♦ Controller Setpoint Limit.
9.1.1 Virus Checking Solution

V7.1 software supports a new virus checking solution for I/A Series workstations running the
Windows XP operating system, ensuring the protection of your Invensys Foxboro workstations
and data from harmful viruses. Virus checking can be performed via the VirusScan 7.0 from
McAfee®. For information on purchasing, installing, configuring, and operating the McAfee
virus scanning software on your I/A Series system, refer to Custom McAfee VirusScan Enterprise 7.0
Install Documentation For I/A Series Software, available on the CSC website.
The virus checking software that is supported by V7.1 I/A Series software:
1. Detects and prevents known viruses and virus-like behaviors.
2. Removes a virus upon finding one, or warns you and suggests a recovery method.
3. Provides regular automatic or on-demand updates of virus definitions and software.
4. Scans all incoming and outgoing files, including I/A Series files.
5. Scans entire drive(s) on demand.
6. Provides you with control over reboots (for example, during an upgrade or a virus
scan).
7. Does not disrupt I/A Series system control over your process.
103
B0400QM – Rev A 9. Release Features and Configurations
9.1.2 Modbus Communication Interface

The FBM224 Modbus Communication Interface Module was introduced with I/A Series
Version 6.5 software and is now supported by V7.1 I/A Series A2 software. FBM224 integrates
third-party devices that support a Modbus interface, such as PLCs and field I/O devices, into an
I/A Series system. The FBM224 provides digital communications to/from Modbus slave devices
(input/output devices) on Modbus networks.
Modbus protocol is a vendor independent communication standard which supports digital
communication between a host controller interface (such as the FBM224) and a broad range of
Modbus compliant devices.
Key features of the FBM224 are:
♦ Conforms to Modbus protocol.
♦ Offers a choice of RS-232, RS-422, or RS-485 communication interface standard.
♦ Integrates Modbus slave device data into an I/A Series control database.
♦ With its associated termination assembly (TA), is suitable for installation in Class 1,
Division 2, and Zone 2 locations.
♦ Baseplate Module Mounting
♦ Easy Removal/Replacement.
Devices with which the FBM224 can successfully communicate are those that support some sub-
set of the Modbus function codes listed in Table 9-1, and operate in the Modbus RTU mode.
These devices must respond as slave devices to some or all of the subset of commands of the
Modbus function codes as listed in Table 9-1.
Table 9-1. Modbus Protocol Function Codes
Function
Code Description
01 Read Coil Status
02 Read Input Status
03 Read Holding Registers
04 Read Input Registers
05 Force Single Coil
06 Preset Single Register
08 Loopback Diagnostic Test
15 Force Multiple Coils
16 Preset Multiple Registers
Figure 9-1 shows the relationship between the various equipment elements in an I/A Series system
Modbus interface. The FBM224, together with Fieldbus Communications Modules (FCMs),
provides a communication interface between the I/A Series control processor and the slave devices
on the Modbus bus.
The FBM224 services all Modbus slave devices and communicates with the devices on a mas-
ter/slave basis. As a master, the FBM224 initiates each data communication exchange; the slave
devices can only send messages to the master when requested to do so.
104
9. Release Features and Configurations B0400QM – Rev A
To/From I/A Series To Additional, Similar

Control Station Equipment Groupings
(if applicable)
Fieldbus F F
C C 2 Mbps
Communications
M M Module Fieldbus
Modules
To Additional FBMs (if applicable)
Up to 64 Modbus Slave
FBM224
1 2 3 4
Devices per FBM224
Four FBM224 Ports

Termination TA
1 2 3 4
Assembly
See below for typical connections.
TA TA
1 2 3 4 1 2 3 4
Slave
Devices
Slave
Devices Slave Slave
Devices Devices
Slave Slave
Devices Devices
RS-422 or RS-485 multidrop
without modems or converters. RS-422 or RS-485 multidrop
Ports 1 and 2 Redundant. without modems or converters.
Ports 3 and 4 Redundant. Ports 1, 2, 3 and 4 Non-redundant.
TA TA TA
1 2 3 4 1 2 3 4 1 2 3 4
Modem/ Modem/ Modem/ Modem/

Converter/ Converter/ Modem/
Converter/ Converter/ Slave
Device Device Converter/
Device Device Devices
Device
Modem/ Modem/ Slave
Converter/ Converter/ Devices
Device Device
RS-232 Direct Connection. RS-232 Direct Connection. RS-232 Direct Connection

Ports 1, 2, 3, and 4 Ports 1 and 2 Redundant. on Ports 1 and 2 Redundant.
Non-redundant. Ports 3 and 4 Redundant. RS-422 or RS-485 multidrop on
Ports 3 and 4 Non-redundant.
NOTES:
Each FBM224 port can be configured for RS-232, RS-422, or RS-485 communication standards.
Ports 1 and 2, and/or 3 and 4 can be configured for dual ported devices.
Figure 9-1. FBM224 in Typical Modbus Network Configurations
105
The FBM224 has four ports – each port can be individually configured for RS-232, RS-422 or
RS-485. Ports 1 and 2, and/or Ports 3 and 4 can be configured to function as a single logical port
for dual ported devices. The FBM224 can support a total of 64 devices distributed over its four
ports.
The FBM224 and its associated termination assembly (TA) accommodate several types of connec-
tions to devices: dual ported and/or single ported connections (Figure 9-1), direct connection to
devices, connection to modems when used with RS-232, RS-232 converters to RS-422 or
RS-485, and intrinsic safety protective devices between the TA and the device.
Physically, the FBM224 mounts on a baseplate along with other DIN rail mounted FBMs (see
Figure 9-2). The FCMs, which are also baseplate mounted, provide conversion of the 10 Mbps
Ethernet trunk Fieldbus signals to the 2 Mbps signals required by the FBMs. [For detailed infor-
mation on the functional aspects of the FCMs and other I/A Series DIN rail mounted equipment,
refer to DIN Rail Mounted FBM Subsystem User’s Guide (B0400FA)].
Baseplate
FBM224
Figure 9-2. DIN Rail Mounted FBM224
A TA provides physical connection of the Modbus devices to the FBM224 ports (see Figure 9-3).
The TA provides for the connection of up to four RS-422 and/or RS-485 cable connections
and/or up to four serial RS-232 DB-25 cable connections. Switches on the TA, used with
RS-232, provide for selection of the clear-to-send, request-to-send, and other RS-232 signals. In
an RS-422 or RS-485 configuration, the FBM224 can be located anywhere on the Modbus bus.
If the FBM224 is located at the end of a bus segment, terminators (terminating resistors) for the
prevention of signal reflection on the TA are switch selectable. Where devices are positioned at the
ends of the bus segments, line terminators are typically included as part of the devices.
106
Termination Switches Switches for RS-232 Switches for RS-232

Cable for RS-422 and RS-485 Communication Signals Communication Signals
Type 5 (under cover) (under cover) (under cover)
Compression Screw DB-25

Connection for Connectors
RS-422 and RS-485 for RS-232
Figure 9-3. FBM224 Termination Assembly
The FBM224 interfaces with the control processor and other hardware and software elements of
the I/A Series system to provide control, alarming, trending, and display capabilities. Software
residing in the control processor and I/A Series workstations provides full support of the
FBM224.
9.1.2.1 FBM224 Configuration

The FBM224 input/output (reading/writing data to/from the devices) uses equipment control
blocks (ECBs) and Distributed Control Interface (DCI) blocks. Table 9-2 lists the ECBs and DCI
blocks used with the FBM224. For descriptions of the ECBs and DCI blocks used with the
FBM224, refer to Integrated Control Block Descriptions (B0193AX).
Table 9-2. ECBs and DCI Blocks Used with the FBM224
ECB/DCI Block Description

ECB110 Fieldbus Communications Module
(FCM) for DIN rail subsystem
ECB200 Parent ECB, representing the FBM224
ECB201 Child ECB, representing a device
RIN Real Input DCI block
107
Table 9-2. ECBs and DCI Blocks Used with the FBM224 (Continued)
ECB/DCI Block Description

RINR Redundant Real Input DCI block
ROUT Real Output DCI block
BIN Binary Input DCI block
BINR Redundant Binary Input DCI block
BOUT Binary Output DCI block
PLSOUT Pulsed Output DCI block
PAKIN Packed Input DCI block
PAKOUT Packed Output DCI block
IIN Integer Input DCI block
IOUT Integer Output DCI block
One ECB200 must be configured for the FBM224 and, for each device associated with the
FBM224, a child ECB201 must be configured and connected to the (parent) ECB200. In addi-
tion, DCI blocks must be configured to access device data via the FBM224. The DCI blocks may
be configured anywhere in the Continuous List hierarchy (List 1 or 2), in any compound in a
control processor (except the ECB compound).
The Integrated Control Configurator (ICC) or FoxCAE software configures the ECBs, DCI, and
I/A Series control blocks for the FBM224.
The DCI blocks contain the identification of the data to be transferred to/from the device.
The port configuration file defines the communication parameters for the FBM224 port (for
example, port baud rate, number of stop bits and dual/single port). There is one ECB200 for an
FBM224 and one port configuration file that defines all four FBM224 ports.
The device transaction configuration file defines the communication parameters for the devices
(for example, start address to read/write registers and coils, heartbeat and read rate). There is one
ECB201 per Modbus device and up to 64 device transaction specifications (in the device transac-
tion configuration file) for each device.
For additional information, refer to the following documents:
♦ Modbus Communication Interface Module (FBM224) (PSS 21H-2Z24 B4)
♦ Modbus Communication Interface Module (FBM224) User’s Guide (B0400FK).
9.1.2.2 Configurators
Two configurators are provided, Windows or Solaris versions, for the setup of FBM224 port and
slave configuration files. The FBM224 Port Configurator allows for easy setup of the communica-
tion parameters for each port (such as, communication interface standard, baud rate, parity). The
Device Transaction Configurator allows for easy setup of the transaction specifications for slave
device files (such as, scan rate, function code, start address of the data to be transferred, and the
amount of data to be transferred in one transaction). During configuration, the selected values
and supported options are automatically checked for range validity. This information is used by
the FBM224 to initialize itself as a master on the network and to maintain communication with
the devices.
108
NOTE
You may configure the ECB200 and all device ECBs (ECB201s) before, or after,
creating the FBM224 port configuration and/or device transaction configuration
files.
9.1.2.2.1 Hardware Configurations

The FBM224 port and device transaction configurators run on an I/A Series AW70 or AW51 sta-
tion, in either of two hardware configurations (see Figure 9-4).
FBM224 FBM224
Configurators Configurators
AW70
AW51
(Host to CP) (Host to CP)
CP CP
FBM224 FBM224
Figure 9-4. I/A Series Hardware Configurations Supporting the FBM224 Configurator
The configuration files are platform independent: files created on an AW70 can be used by an
AW51 host; and files created on an AW51 can be used on an AW70 host.
NOTE
Configuration filenames on an AW51 host must be all uppercase because the ICC
converts the name entered for the FILEID to all uppercase characters and because
UNIX is case-sensitive.
Principles of Operation
The FBM224 configurator consists of two separate configuration utilities. These utilities (or con-
figurators) produce corresponding configuration files, in accordance with user-entered data:
♦ Device Transaction Configurator – This utility produces device transaction configura-
tion files associated with the devices assigned to the FBM224 ports. These files
contain device transaction specifications relating to the transfer of data with the
devices.
♦ Port Configurator – This utility produces a port configuration file containing the
communication parameters for each port of the FBM224.
Linkage to the files is provided through the ECBs for the FBM224 and the devices on the net-
work. The filename of the port configuration file is specified in the FILEID parameter of the
ECB200 block (representing the FBM224).
109
The filename of the device transaction configuration file is specified in the FILEID parameter of
the ECB201 block (representing the device). These ECB/file relationships are illustrated in
Figure 9-5. Note that, as indicated in Figure 9-5, a single device transaction configuration file
(detailing the device communication parameters) may be used by more than one ECB201.
ECB200
Port
FILEID Configuration
File
ECB201
ECBs FILEID
Representing Device
Identical Transaction
Devices Configurator
Configuration
ECB201 File
FILEID
ECB201 Device
Transaction
File
Figure 9-5. ECB/Configurator File Relationships
NOTE
The ECBs cannot be created or edited using the FBM224 configurator. Setting of
the FILEID parameter in the ECBs is done through a control configurator: ICC or
FoxCAE software.
Once the port configuration file and the device transaction configuration files are created using
their respective configurators, they are stored in the host workstation. As a final step in the config-
uration process, the files are downloaded to the FBM for use in initializing and maintaining com-
munications with the devices.
Configurator Operations
Figure 9-6 shows the major steps in operating the FBM224 configurator.
The FBM224 port and device transaction configurators configure the FBM224 ports and data
transactions for the devices. The ICC editor creates the blocks for the ECB200s and ECB201s.
All the configurators (port, device transaction, and ICC) can be used independently. There is no
certain order needed.
110
Start
Start Device Transaction Configurator

and Create All Device Transaction
Configuration Files.
Save the Device Transaction

Start Port Configurator and

Create Port Configuration File.
Save the Port

Configuration File.
Back Up the
Figure 9-6. Configuration Operations
For detailed operating procedures for the FBM224 Port Configurator and the FBM224 Device
Transaction Configurator, refer to Modbus Communication Interface Module (FBM224) User’s
Guide (B0400FK).
9.1.3 HART Communication Interface

The HART Communication Input/Output Interface Modules (FBM214, FBM215, FBM216,
and FBM218) were introduced with I/A Series Version 6.4 software and are now supported by
V7.1 I/A Series A2 software. The HART Communication Interface Modules provide analog and
digital communications to and from HART compliant field devices. They also support standard 4
to 20 mA signals from analog devices. Each of these FBMs contains eight channels that are group
isolated for the FBM214/216 and individually isolated for the FBM216/218.
♦ FBM214 – Each channel provides bidirectional digital communications with a field
device, and performs analog to digital conversion on the 4 to 20 mA input control sig-
nal from that device.
♦ FBM215 – Each channel provides bidirectional digital communications with a field
device, and performs digital to analog conversion to generate the 4 to 20 mA output
control signal to that device.
♦ FBM216 – This module, used in pairs, provides a redundant version of the FBM214.
♦ FBM218 – This module, used in pairs, provides a redundant version of the FBM215.
HART FBMs communicate with the Fieldbus I/O devices on a master/slave basis. HART is a
communications standard which supports digital communication between a master (such as the
FBM214/215/216/218) and a broad range of slave devices which include transmitters and actua-
111
tors. Each HART FBM can service up to eight slave devices in a point-to-point network configu-
ration; multidrop network configurations are not supported. During normal operation, each
communication is initiated by the HART FBM, which serves as the primary master. The slave
devices can only acknowledge received messages, or send messages to the master when requested
to do so.
The HART communication protocol is based on the Bell 202 telephone communication standard
and operates according to the frequency shift keying (FSK) principle. This is in addition to the 4
to 20 mA normal analog input or analog output signal (depending on the FBM model). The dig-
ital signal is made up of two frequencies, 1,200 Hz and 2,200 Hz, representing respectively the
bits 1 and 0. The sine waves of these two frequencies are superimposed on the direct current (ana-
log) signal to provide simultaneous analog and digital communications. The FSK signal allows
communication at 1200 baud.
The FBMs operate in a point-to-point configuration. In this mode, the traditional 4-20 mA
signal is used to communicate one main process variable. The HART communication digital
signal provides access to secondary process variables, configuration parameters, and other device
data that can be used for operations, commissioning, maintenance, and diagnostic purposes.
9.1.3.1 HART FBM Installation

Figure 9-7 shows the relationship between the various equipment elements in a HART subsystem.
FBM214/215/216/218 together with Fieldbus Communications Modules (FCMs) provide a
communication interface between the I/A Series control station, such as the Control Processor 60
(CP60), and the I/O field devices. Termination assemblies (TAs) provide for physical connection
of the field devices to the FBMs.
10Base2 (10 Mbps)

Ethernet Trunk Fieldbus
To/From I/A Series (redundant) To Additional, Similar
(if applicable)
Fieldbus F F To Additional FBMs (if applicable)
C C 2 Mbps
Communications
M M Module Fieldbus (Up to 120 FBMs per I/A Series Control Station)
Modules
FBM 214 FBM 215 FBM 216 FBM 216 FBM 218 FBM 218
REDUNDANT ADAPTER REDUNDANT ADAPTER

Termination
Assemblies TA TA
TA TA
... ...
... ...
Up to 8 Slave Devices per HART FBM
Note: Each HART FBM can service up to eight slave devices in a point-to-point network configuration.
Figure 9-7. HART FBMs used in a Typical Network Configuration
112
Physically, the FBMs mount on a baseplate that is DIN rail mounted. The FCMs, which are also
baseplate mounted, provide conversion of the 10 Mbps Ethernet trunk Fieldbus signals to the
2 Mbps signals required by the FBMs. For detailed information on the functional aspects of the
FCMs and other I/A Series DIN rail mounted equipment, refer to DIN Rail Mounted FBM Sub-
system User’s Guide (B0400FA).
The redundant adapter, used with the redundant FBM pairs (FBM216 and FBM218), provides a
“Y” connection between the FBM pairs and the associated TA. This allows either module in the
pair to communicate with the field devices.
Field devices are generally configured using either of the following:
♦ The Foxboro Intelligent Field Device Configurator (IFDC) which is an optional com-
ponent of an I/A Series control system.
♦ A hand held configurator connected to the active (operational) link between the TA
and the devices.
For general instructions on installing the FBMs and their termination assemblies (TAs), refer to
DIN Rail Mounted FBM Subsystem User’s Guide (B0400FA). The non-redundant FBMs (FBM214
or FBM215) can be located in any slot on the baseplate, with the associated TAs mounted in adja-
cent cable connectors. The redundant FBMs (FBM216 or FBM218) must be located in adjacent
positions on the baseplate (positions 1 and 2, 3 and 4, 5 and 6, or 7 and 8). The first (odd) mem-
ber of the pair is referred to as the main and the second is referred to as the backup. The module
that is the primary source of data is considered active and the other module (if it is working nor-
mally) would be in the track state. The connected device equipment control blocks (ECBs) nor-
mally get their input data from the active member of the pair. They use input data from the
module in track mode, if this was the only good source of data.
Refer to HART Communication Interface Modules (FBM214/215/216/218) User’s Guide
(B0400FF) for additional HART FBM installation instructions.
9.1.3.2 HART FBM Configuration

An ECB200 must be configured for each FBM214 or FBM215, and an ECB202 must be config-
ured for each FBM216 or FBM218 redundant pair. For each device associated with the FBMs, a
child ECB201 must be configured and connected to the (parent) ECB200 or ECB202. In addi-
tion, a DCI block must be configured for each HART FBM parameter that is connectable. The
DCI blocks can be configured anywhere in the Continuous List hierarchy (List 1 or 2), in any
compound in a control station. Refer to HART Communication Interface Modules
(FBM214/215/216/218) User’s Guide (B0400FF) for general ECB200/201/202 configuration
information, and refer to I/A Series Integrated Control Configurator (B0193AV) and I/A Series Inte-
grated Control Block Descriptions (B0193AX) for detailed instructions on creating and editing
ECBs.
9.1.4 PROFIBUS-DP Communication Interface

The PROFIBUS-DP Communication Interface Module (FBM223) was introduced with
I/A Series Version 6.4 software and is now supported by V7.1 I/A Series A2 software. The
FBM223 provides digital communications to/from PROFIBUS slave stations (input/output
devices) on PROFIBUS-DP networks. PROFIBUS slave stations interfaced to the I/A Series sys-
tem by the FBM223 typically include programmable logic controllers (PLCs) and field I/O
devices.
113
PROFIBUS is a vendor independent communication standard which supports digital communi-

cation between a host controller interface (such as the FBM223) and a broad range of
PROFIBUS compliant devices. PROFIBUS-DP represents the communication profile that is
most often used with PROFIBUS. It is optimized for speed, efficiency, and low connection cost,
making it well suited for communication between a host system (such as the I/A Series system)
and distributed field devices. The physical PROFIBUS-DP bus wiring consists of twisted-pair
shielded cable, in accordance with Electronic Industrial Association (EIA) standard RS-485.
Figure 9-8 shows the relationship between the various equipment elements in a basic
PROFIBUS-DP subsystem (no repeaters used). FBM223, together with Fieldbus Communica-
tions Modules (FCMs), provides a communication interface between the I/A Series control pro-
cessor (typically, a Control Processor 60) and the I/O slave devices on the PROFIBUS-DP bus.
Termination assemblies (TAs) provide for physical connection of the PROFIBUS-DP bus seg-
ments to the FBM223 ports (up to 2). FBM223 can be located anywhere on the PROFIBUS-DP
bus.
Active (powered) terminators are required at the ends of the bus segments, to prevent signal reflec-
tion. If the FBM223 is located at the end of a bus segment, termination is provided by means of
terminating resistors on the TA(s). Where slave devices are positioned at the ends of the bus seg-
ments, line terminators, typically included as part of the slave devices, can be activated (switched
on) as required.
Repeaters1 can be used in the PROFIBUS-DP network configuration (see Figure 9-9) to extend
the length of the bus, and to provide support for a greater number of slave devices. As shown in
Figure 9-9, with the use of repeaters, multiple bus segments are formed for each FBM223 port,
each segment supporting up to 32 active devices2. With repeaters, up to 91 slave devices are sup-
ported per FBM223 port. (Without repeaters, up to 31 slave devices are supported per FBM223
port.)
The FBM223 operates in a multi-master network. Every master, other FBM223s or foreign mas-
ters, communicates only to the slave devices addressed by the master. Multiple masters cannot
address the same slave device. Figure 9-10 shows both ports of an FBM223 connected in a multi-
master network.
9.1.4.1 PROFIBUS-DP FBM Installation

Physically, the FBM223 mounts on a baseplate along with other DIN rail mounted FBMs. The
FCMs, which are also baseplate mounted, provide conversion of the 10 Mbps Ethernet trunk
Fieldbus signals to the 2 Mbps signals required by the FBMs. [For detailed information on the
functional aspects of the FCMs and other I/A Series DIN rail mounted equipment, refer to the
DIN Rail Mounted FBM Subsystem User’s Guide (B0400FA)].
1. For detailed information on the use of repeaters, refer to related documentation offered by the
PROFIBUS organization.
2.
Active devices include master stations, slave stations, and repeaters.
114

(if applicable)
Fieldbus F F 10Base2 (10 Mbps)
C C 2 Mbps Ethernet Trunk Fieldbus
Communications
M M Module Fieldbus (redundant)
Modules
FBM223
Up to 31 PROFIBUS Slave Devices per Non-
Expanded Bus, or up to 91 per Expanded Bus
Termination (See Note)
Assembly TA
Terminator
Terminator
Two Independent PROFIBUS-DP Buses

(RS-485 Communications, Typical Configuration)
NOTE:
Each bus (one per port) can be segmented (expanded) through the use of repeaters, to
accommodate additional slave devices (see Figure 2-3).
Figure 9-8. FBM223 used in a Basic PROFIBUS-DP Network Configuration
Bus Master
(FBM223)
Segment 1
Termination
Assembly Repeater Slave
Station
Segment 2
Repeater Slave
Segment 3 Station
Slave Slave Slave

Station Station Station
Legend: = Bus Terminator

Figure 9-9. PROFIBUS-DP Network Expansion Using Repeaters
115

(if applicable)
Fieldbus F F 10Base2 (10 Mbps)
C C 2 Mbps Ethernet Trunk Fieldbus
Communications
M M Module Fieldbus (redundant)
Modules
FBM223
Up to 31 PROFIBUS Slave Devices per Non-
Expanded Bus, or up to 91 per Expanded Bus
Termination (See Note)
Assembly TA
Terminator
Both FBM223 Ports Connected
to one PROFIBUS-DP Bus One PROFIBUS-DP Bus
(RS-485 communications, multi-master configuration)
NOTE:
The bus can be segmented (expanded) through the use of repeaters, to
accommodate additional slave devices (see Figure 2-3).
Figure 9-10. FBM223 used in a Multi-Master Network Configuration
The FBM223 services all PROFIBUS slave devices (devices conforming to PROFIBUS standard
EN 50 170) and communicates with the PROFIBUS I/O devices on a master/slave basis. As a
master, the FBM223 initializes each data communication exchange; the slave devices can only
acknowledge received messages, or send messages to the master when requested to do so.
FBM223 interfaces with the control processor and other hardware and software elements of the
I/A Series system to provide proven control, alarming, trending, and display capabilities. Soft-
ware residing in the FBM223, control processor, and I/A Series workstations provides full support
of the PROFIBUS-DP communication profile.
DIN Rail Mounted FBM Subsystem User’s Guide (B0400FA). Refer to PROFIBUS-DP™ Commu-
nication Interface Module (FBM223) User’s Guide (B0400FE) for additional HART FBM installa-
tion instructions.
9.1.4.2 PROFIBUS-DP FBM Configuration

One ECB200 must be configured for the FBM223 (see Figure 5-1) and, for each slave device
associated with the FBM223, a child ECB201 must be configured and connected to the (parent)
ECB200. In addition, a DCI block must be configured for each slave parameter that is connect-
able. (See Table 5-1 for a listing of the DCI block types used in PROFIBUS data transfer opera-
tions.) The DCI blocks can be configured anywhere in the Continuous List hierarchy (List 1 or
2), in any compound in a control processor. Refer to PROFIBUS-DP™ Communication Interface
Module (FBM223) User’s Guide (B0400FE) for general ECB200/201 configuration information,
and refer to Integrated Control Configurator (B0193AV) and Integrated Control Block Descriptions
(B0193AX) for detailed instructions on creating and editing ECBs.
116
9.1.4.2.1 PROFIBUS-DP Bus Configurator

The FBM223 configurator produces files containing user-specified information defining the spe-
cific elements of FBM223 port and PROFIBUS slave device communication. This information is
used by FBM223 to initialize itself as a master on the PROFIBUS network and to maintain com-
munication with the PROFIBUS slave devices.
NOTE
Before FBM223 and slave device communication files can be created using this con-
figurator, ECB200 and all device ECBs (ECB201s) must be configured. Also, ven-
dor-supplied device definition files (typically called GSD files) must be stored
locally, for access by the FBM223 configurator. Without a GSD file, you cannot
configure a device using this configurator.
Hardware Configurations
The FBM223 configurator runs on an I/A Series AW70 or AW51 station, in either of two hard-
ware configurations (see Figure 9-4).
FBM223 FBM223
Configurator Configurator
AW70
AW51
(Host to CP60) (Host to CP60)
CP60 CP60
FBM223 FBM223
Figure 9-11. I/A Series Hardware Configurations Supporting the FBM223 Configurator
The configuration files are platform independent: files created on an AW70 can be used by an
AW51 host; and files created on and AW51 can be used on an AW70 host.
Principles of Operation
The FBM223 configurator consists of two separate configuration utilities. These utilities (or con-
figurators) produce corresponding configuration file types, in accordance with user-entered (or
user-specified) data:
♦ Slave Device Configurator – This utility produces multiple slave device configuration
files associated with the slave devices assigned to the FBM223 ports. These files con-
tain device definition parameters relating to PROFIBUS communications.
♦ Port Configurator – This utility produces a port configuration file containing the
FBM223 PROFIBUS communication parameters for both ports.
Linkage to the files is provided through the ECBs for the FBM223 and the devices on the
PROFIBUS network. The filename of the port configuration file is specified in the FILEID
parameter of the ECB200 block (representing the FBM223); likewise, the filename of the slave
117
device configuration file is specified in the FILEID parameter of the ECB201 block (representing
the slave device). These ECB/file relationships are illustrated in Figure 9-5. Note that, as indicated
in Figure 9-5, a single slave device configuration file (detailing the device communication param-
eters) can be used by more than one ECB201.
ECB200
Port
File
ECB201
ECBs FILEID
Representing Device
Identical Transaction
Devices Configurator
Configuration
ECB201 File
FILEID
ECB201 Device
Transaction
File
Figure 9-12. ECB/Configurator File Relationships
NOTE
The ECBs cannot be created or edited using the FBM223 configurator. Setting of
the FILEID parameter in the ECBs is done through a control configurator: ICC or
FoxCAE™ software.
Once the port configuration file and the slave device configuration files are created using their
respective configurators, they are stored in the host workstation. As a final step in the configura-
tion process, the files are downloaded to the FBM for use in initializing and maintaining
PROFIBUS communications with the devices.
Slave Device Communication Configuration
For each slave device, there are various parameters that must be configured. These parameters are
not unique to each device but rather to each type of device. For example, all Foxboro model
SRD991 devices from Invensys Foxboro may be configured with the same parameter values.
Because a slave device configuration file does not contain any device-unique information, the
same file can be used by multiple device instances. (The device-unique information is specified
through ECB201 parameters.)
Thus, the slave device configurator allows you to create files whose parameters define multiple
devices of a particular type (for example, multiple model SRD991s). The slave device editor
118
allows you to select a device type, create an instance, and configure the parameters. If devices of a
particular type have different parameter values, then multiple slave device configuration files can
be generated, as required.
Files defining the definitions of various devices are available from various device manufacturers
(on CD-ROM or via the Internet). Device vendors supply these files (termed GSD files) to define
the characteristics of their devices. The slave device configurator allows you to use these files as a
basis for slave device configuration, thus providing a quick and convenient means for configuring
the device parameters.
Before starting, the GSD file for all slave devices must be copied onto the AW hosting the con-
trol processor. Make a directory to store all your GSDs; for example, /opt/GSDs.
The slave device configurator generates default filenames for the files, based on device identifiers
supplied as part of the device definition files. The device configuration files must be configured
on the I/A Series station that hosts the FBMs assigned to the control processor (CP60).
NOTE
Before generating slave device configuration files, the configurator requires that the
slave devices be assigned to the FBM223 ports. This assignment is assumed to have
been made previously, by user configuration of the ECB201 PARENT and
PORTNO parameters. PARENT specifies the ECB200 representing the FBM223,
and PORTNO specifies the port (1 or 2) to which the device is assigned.
For slave device communication parameters, slave device file storage and additional detailed
instructions on using the PROFIBUS-DP Bus Configurator, refer to PROFIBUS-DP Communi-
cation Interface Module (FBM223) User’s Guide (B0400FE).
FBM223 Port Communication Configuration
The FBM223 port configurator is used to create the port configuration file, which specifies the
communication settings for both ports of the FBM223. Use of the port configurator requires that
you first produce the communication configuration files for all associated slave devices (as
described above) and that you assign the slave devices to the FBM223 port(s). (You assign slave
devices to the FBM ports by setting the ECB201 PARENT and PORTNO parameter in the
ECB201.)
You set the communication parameters for the FBM223 using the port configurator’s dialog
boxes. The configurator uses the information entered for the slave devices (during slave device
configuration) to validate the settings for the FBM223 port parameters.
For FBM223 communication parameters and port configuration file storage, and for additional
detailed instructions on using the PROFIBUS-DP Bus Configurator, refer to PROFIBUS-DP
Communication Interface Module (FBM223) User’s Guide (B0400FE).
Multi-Master Configuration
Multiple masters can reside on the same bus. Some of these masters can be FBM223 ports (some
can be other vendors’ products). In fact, both ports on a single FBM223 can act as masters on the
same bus or multiple FBMs can have ports connected to the single bus.
Refer to PROFIBUS-DP Communication Interface Module (FBM223) User’s Guide (B0400FE) for
additional information on configuring the FBM223 in a multi-master configuration.
119
9.1.5 FOUNDATION Fieldbus H1 Communication Interface

The FOUNDATION Fieldbus H1 Communication Interface Modules (FBM220/FBM221) were
introduced with I/A Series Version 6.3 software and are now supported by V7.1 I/A Series A2
software. FBM220 and FBM221 provide an interface between FOUNDATION fieldbus field
devices and the I/A Series system. FBM220 supports one H1channel isolated fieldbus segment,
and FBM221 provides integration of four H1 channel isolated fieldbus segments. The H1 seg-
ments are isolated from the Fieldbus and from each other. Power is supplied to the field devices
via the FBM termination assembly (TA). Refer to the FOUNDATION Fieldbus H1 Communication
Interface Modules (FBM220/FBM221) User’s Guide (B0400FD).
The FOUNDATION fieldbus is an all digital, serial, bi-directional communication bus for integrat-
ing process measurement and control devices. The H1 bus is the digital alternative to the
4 to 20 mA standard. The primary H1 physical media is twisted pair wire at 31.25 kbit/s that
provides both power and communications to the devices.
The physical media can be made intrinsically safe when used with intrinsically safe FOUNDATION
fieldbus devices. Intrinsic safety can be achieved through the use of barriers as described in
FOUNDATION fieldbus documents.
FBM220/221, acting as an intelligent field device link master that supports device scheduling on
each of the H1 segments, receives digital messages from the field devices in engineering units.
Analog inputs and outputs of connectable variables are collected and made available to the
I/A Series system in IEEE 32-bit floating-point format. Security information (status of the AI and
AO variables) is supplied, as is diagnostic information and message checking.
9.1.5.1 I/A Series Fieldbus Communication

FBM220/221 communicates with its associated FCM via the I/A Series 2 Mbps Module Field-
bus. Communication between the FCM and the control station is via the optionally redundant
I/A Series 10 Mbps Ethernet trunk Fieldbus. FBM220/221 accepts communication from either
path (A or B) of the redundant Ethernet trunk Fieldbus.
9.1.5.2 Key Features and Benefits

Key features and benefits of the FBM220/221 modules include:
♦ Reduced engineering, downtime, maintenance
♦ Higher performance, accuracy, speed, security with faster startup
♦ Improved safety with multi-drop networks
♦ Module mix and match capabilities
♦ Open communications with intrinsically safe performance
♦ Conformance to the FOUNDATION fieldbus specifications allowing devices from vari-
ous manufacturers to be used.
♦ Ability to be combined with other protocols and analog devices
♦ Ability for fail-safe operation to be implemented at the device level on a per device
basis
♦ Use of FoxCAD™ and FoxCAE™ integrated engineering environment
♦ Integration of H1 device data into an I/A Series program format for consistent opera-
tor display of alarms, trends, and operator displays, independent of the
protocol/communication bus used to bring them into the system
120
♦ A Link Active Scheduler (LAS) that is provided for each H1 segment and associated
FBM220/221
♦ FBMs that automatically detect and schedule all devices on the H1 segment, provid-
ing faster startup and commissioning
♦ FBMs and termination assemblies that are suitable for installation in Class 1, Division
2 and Zone 2 locations
♦ The FBM module, which can be removed/replaced without removing field device
termination cabling, power, or communications cabling, mounts on a standard
baseplate which accommodates up to eight FBMs.
♦ The I/A Series FBM220/221 implementation of FOUNDATION fieldbus segments
conform to ANSI/ISA S-50, IEC 61158, and CENELEC EN 50170.
9.1.5.3 FOUNDATION Fieldbus FBM Installation

The FBM220/221 mounts on a baseplate along with other DIN rail mounted FBMs, and con-
nects to its associated termination assembly (TA) by means of a cable. FBM220/221 receives and
processes signals to/from the FOUNDATION fieldbus via the TA, and communicates with the
I/A Series CP60 via the FCM(s).
DIN Rail Mounted FBM Subsystem User’s Guide (B0400FA). For more specific FOUNDATION
Fieldbus FBM installation instructions, refer to FOUNDATION™ fieldbus H1 Communication
Interface Modules (FBM220/FBM221) User’s Guide (B0400FD).
9.1.5.4 FOUNDATION Fieldbus FBM Configuration

One ECB200 must be configured for the FBM220/221, and for each H1 field device associated
with the FBM220/221; a child ECB201 must be configured and connected to the (parent)
ECB200. (The ECB200 and ECB201 parameters are defined in Integrated Control Block Descrip-
tions (B0193AX)).
Table 9-3 shows the maximum number of H1 devices and point connects allowed per
FBM220/221. These numbers may vary depending on factors such as the power consumption of
each device, type of cable used, use of repeaters, duration of macrocycle, and so forth. You must
configure the H1 device itself as well as configuring the I/A Series system.
Table 9-3. FBM220/221 Maximum Configuration Specifications
FBM Maximum Number Maximum Number of

Type of H1 Devices Allowed Point Connects Allowed
FBM220 16 24 *
FBM221 32 (8 per port) 64 total per FBM (16 per port) *
* Note: Each analog or discrete output requires two point connects, one for the output and one
for the readback.
FBM220 and FBM221 support the standard FOUNDATION Fieldbus I/O function blocks (AI,
AO, DI, and DO), passing all block parameters to the I/A Series control station over the
I/A Series high speed redundant Ethernet Fieldbus. DCI control blocks are configured and con-
nected, in a one-to-one functional relationship, to the appropriate ECB201 as follows:
121
Table 9-4. Function Blocks Corresponding to DCI Blocks
I\O Function Blocks DCI Control Blocks

AI (Analog Input) RIN (Real Input)
AO (Analog Output) ROUT (Real Output)
DI (Digital Input) BIN (Binary Input)
DO (Digital Output) BOUT (Binary Output)
A field device may contain multiple function blocks, which can be accessed via multiple associ-
ated DCI control blocks.
For additional information on FBMs 220 and 221, refer to refer to FOUNDATION™ fieldbus H1
Communication Interface Modules (FBM220/FBM221) User’s Guide (B0400FD).
9.1.6 SPECTRUM Migration and Cluster I/O

SPECTRUM Migration Integrators (SMI) and Cluster I/O (FBC) are fully supported by the
CP60, as well as the CP30, CP30B, CP40, and CP40B in the V7.1 Release.
Support for SPECTRUM and Cluster I/O on the CP60:
♦ Allows you to mix the latest 200 series FBMs on the same CP
♦ Allows you to combine SPECTRUM, Cluster I/O, HART, and PROFIBUS-DP
devices
♦ Provides the benefits of a faster Ethernet fieldbus.
The following FBPs are supported:
♦ FBP10: FBC / Cluster IO
♦ FBP11: UCM1, UCM2, UCM3, and UCM4
♦ FBP12: FIO™, including the satellites
♦ FBP13: UFM™
♦ FBP14: UIO
NOTE
For the Control Processor 60, I/A Series software versions 6.3.2 and 6.5 and higher
are required for SPECTRUM Migration Integrator and Cluster migration support.
Software Version 6.4 does not include this support for the CP60. However, V6.4
supports all other competitive migration products.
9.1.6.1 SPECTRUM Migration Integrators

The I/A Series SPECTRUM Migration Integrator subsystem provides a means of migrating con-
trol of SPECTRUM loops from MICROSPEC™ (UCM), Field Input/Output (FIO), Universal
Field Multiplexer (UFM), and Universal Input/Output (UIO) racks to the I/A Series system.
UCM uses an FBP11 module, FIO uses an FBP12 module, UFM uses an FBP13 module, and
UIO uses an FBP14 module for integration.
As part of the equipment upgrade, Fieldbus Processor (FBP) Integrators plug directly into existing
SPECTRUM racks in place of logic nest cards to pass process measurement and output signals
122
between the SPECTRUM input/output (I/O) cards and I/A Series control processors. Operating
under control of the I/A Series control and management software, the SPECTRUM Migration
Integrator subsystem provides advanced control, display, and system management capabilities
while retaining the original SPECTRUM I/O field interface and wiring.
9.1.6.2 Fieldbus Cluster Input/Output Subsystem

The I/A Series Fieldbus Cluster Input/Output Subsystem provides full support for analog mea-
surement, digital sensing, and analog or discrete control capabilities. The subsystem integrates
with the I/A Series Control Processor or Personal Workstation via the I/A Series Fieldbus, and
includes a multi-slot chassis configuration made up of a Fieldbus Processor (FBP10), Analog/Dig-
ital Fieldbus Cards (FBC), subsystem main power supply, and power monitor card.
The Fieldbus Cluster I/O Subsystem is configurable, gathering analog measurements with up to
12-bit accuracy, while simultaneously handling analog and digital input and output channels.
The I/A Series Fieldbus Cluster I/O Subsystem is offered in both non-redundant and redundant
configurations. Each FBP10 in a redundant pair is individually addressable on the Fieldbus with a
unique logical address. In a redundant configuration, the FBP10s provide switchover from the
primary FBP10 to the redundant FBP10 and back again automatically.
The FBCs are suitable in applications where a high number of channels per card are required.
They are ideal for non-isolated and isolated input signal gathering and data acquisition systems
where high quantities of “points per cluster” areas are desired. The Subsystem is suitable for G1
(mild) corrosive environments. The FBCs may be optionally connected as redundant pairs.
Various input cards are available with one of the following three levels of isolation:
♦ Non-isolated - Each channel is referenced to ground and the card itself is referenced to
ground.
♦ Group-isolated - Electrically separate card-to-card but not channel-to-channel on the
same card.
♦ Isolated - Each channel is electrically separated from any other channel, card, group,
building, site, and so forth.
9.1.7 Controller Setpoint Limit

Controller Setpoint Limit is fully supported on the CP60 in the V7.1 Release; the Set Point
Clamping (SPCLMP) parameter has been modified to support the new set point limiting option.
Set Point Clamp Option specifies one of the following:
♦ Whether or not the SPT, RSP, and SUP_IN parameters in a PIDA or DPIDA block
are to be limited by the set point limits, SPHLIM and SPLLIM.
♦ Whether or not the CVSPT and SUP_IN parameters in an MVL block are to be lim-
ited by the set point limits, CVHCON and CVLCON.
Valid settings for the SPCLMP parameter for a PID or PIDA block are:
♦ 0 = Clamp RSP and SUP_IN values outside the HSCI1 and LSCI1 range, and clamp
SPT values outside the SPHLIM and SPLLIM range when in local setpoint mode
♦ 1 = Clamp values outside the SPHLIM, SPLLIM limits
♦ 2 = Reject values outside the SPHLIM, SPLLIM limits.
The default setting is 0.
123
Valid settings for the SPCLMP parameter for a MVL block are:
♦ 0 = Clamp SUP_IN values outside the CVHVAL and CVLVAL range, and clamp
CVSPT values outside the CVHCON and CVLCON limits
♦ 1 = Clamp values outside the CVHCON and CVLCON limits
♦ 2 = Reject values outside the CVHCON and CVLCON limits.
The default setting is 0.
9.2 Supported Configurations

Use the information in this section to determine valid equipment combinations and
configurations.
9.2.1 Nodebus Control Network Example

Figure 9-13 shows an example of an I/A Series mixed Nodebus/Ethernet control network com-
prising the following stations, I/O subsystems, and interface modules:
♦ I/O subsystems for distributed process I/O and PLC control
♦ Micro-I/A Stations for distributed, field-based control functions interfacing to I/O
subsystems
♦ Control stations for performing regulatory, logic, timing, and sequential control
♦ Ethernet switches for interconnecting I/A Series stations using CAT5 cable and fiber
optic cable supporting 10/100Base-T and 100Base-FX Ethernet communications
♦ Dual Nodebus 10Base-T Interface modules for interfacing to the Nodebus using
CAT5 cable
♦ Host workstation connected to switched Ethernet network for viewing real-time pro-
cess data, system management, executing applications, and providing boot host
services to Micro-I/A stations and control processors
♦ Application workstation for viewing real-time process data, monitoring the health of
the control system, and executing applications
♦ Windows workstation for executing applications and interfacing with PLCs
♦ COTS Server as a Web Portal plus Internet/Intranet connected browser computer.
124
ETHERNET
INFORMATION NETWORK (ETHERNET) SWITCH COMPUTER
TO CORPORATE WITH BROWSER
INFORMATION
SYSTEMS INTERNET/
INTRANET
WINDOWS
WORKSTATION
• WINWRK
HOST APPLICATION
WORKSTATION WORKSTATION
• WINHST • WINAPP
• AW70 • WP70
• AW51 • WP51
DUAL COTS SERVER

NODEBUS PLC OR
WEB PORTAL
10BASE-T OTHER DEVICE
INTERFACE
DNBT DNBT
(MAU) (MAU)
NODEBUS (REDUNDANT)
DNBT DNBT CONTROL NCNI NCNI

(MAU) (MAU) STATION
• CP60
• CP60S
• AB30B
• M30B
ETHERNET
SWITCHES
ETHERNET
SWITCH
RCNI RCNI RCNI
REDUNDANT
COMMUNICATIONS
MICRO-I/A
STATIONS
MICRO-I/A
STATION APPLICATION UNIX AND/OR UNIX AND/OR
WORKSTATION WINDOWS WINDOWS
• WINAPP WORKSTATION WORKSTATION
ETHERNET
I/O I/O I/O SWITCH
SUBSYSTEMS SUBSYSTEMS SUBSYSTEMS
Figure 9-13. I/A Series Mixed Nodebus/Ethernet Control Network Example Diagram
125
9.2.2 Ethernet Control Network Example

The example in Figure 9-14 uses Ethernet switches for interconnection of up to 24 I/A Series
station and workstations per switch with CAT5 cable supporting 10/100Base-T Ethernet
communications.
COMPUTER
WITH BROWSER
INFORMATION NETWORK (ETHERNET) INTERNET/
INTRANET
TO CORPORATE ETHERNET SWITCH
INFORMATION
SYSTEMS
WINDOWS COTS SERVER

WORKSTATION WEB PORTAL
• WINWRK
HOST APPLICATION
WORKSTATION WORKSTATION
• WINHST • WINAPP
• AW70 • WP70
• AW51 • WP51
ETHERNET SWITCH
10/100BASE-T
CONTROL NETWORK
MICRO-I/A MICRO-I/A
STATION STATION
I/O I/O
SUBSYSTEMS SUBSYSTEMS
Figure 9-14. I/A Series Ethernet Control Network Example Diagram
The following components are depicted in the example:

♦ I/O subsystems for distributed process I/O and PLC control
♦ Micro-I/A Stations for distributed, field-based control functions interfacing to I/O
subsystems
♦ Ethernet switches for interconnecting I/A Series stations and workstations using
CAT5 cable supporting 10/100Base-T Ethernet communications
♦ Host workstation for viewing real-time process data, managing the system, executing
applications, and providing boot host services to Micro-I/A stations and control
processors
126
♦ Application workstation for viewing real-time process data, monitoring the health of
the control system, and executing applications
♦ Windows workstation for executing applications
♦ COTS Server for providing Internet/Intranet web portal services and executing
applications
♦ Computer for accessing information over the Internet or company Intranet via a web
browser.
9.2.3 Other I/A Series A2 Control Network Examples

Refer to Control Network User’s Guide (B0400DV) for additional control network examples.
9.2.4 Release Version 7.1 Stations and Applications

The following tables summarize the available equipment for systems with Solaris 8 or
Windows XP operating systems. The equipment lists include workstations, gateways, integrators,
and so forth. For stations that cannot be used with specific equipment, refer to the previous fig-
ures and Table 9-8.
Table 9-5. Workstations for I/A Series A2 Systems
Hardware Model and Operating

V7.0 Station P Designation System Control
WP51F Model 51F (P79) Solaris 8 No
AW51F Model 51F (P79) Solaris 8 No
AW51G Model 51G (P80) Solaris 8 No
AW51FX Model 51F (P79) Solaris 8 Yes
AW51GX Model 51G (P80) Solaris 8 Yes
WP70P Model 70P (P92) Windows XP No
AW70P Model 70P (P92) Windows XP No
AW70CP Model 70P (P92) Windows XP Yes
The following are consoles and peripherals for workstations running the Solaris 8 operating sys-
tem used in the I/A Series A2 System:
♦ Modular Industrial Console (MIC)
♦ Modular Industrial Workstation (MIW)
♦ Command Center
♦ Annunciator Keyboard
♦ Annunciator/Numeric Keyboard
♦ Color PostScript® Printer
♦ Color PCL5 Printer
♦ Color Dot Matrix Printer
♦ B/W Dot Matrix Printer
♦ HP DeskJet™ Printer
127
♦ Line Printer
♦ 20.1-Inch Flat LCD
♦ 21-Inch Display (with/without touchscreen)
♦ GCIO Interface Module (with/without touchscreen)
♦ Random Array of Independent Disks (RAID).
The following are consoles and peripherals for workstations running the Windows XP operating
system used in the I/A Series A2 System:
♦ Modular Industrial Console (MIC)
♦ Modular Industrial Workstation (MIW)
♦ Command Center
♦ Annunciator Keyboard
♦ Annunciator/Numeric Keyboard
♦ Color PostScript Printer
♦ Color PCL5 Printer
♦ Color Dot Matrix Printer
♦ B/W Dot Matrix Printer
♦ HP DeskJet Printer
♦ Line Printer
♦ 20.1-Inch Flat LCD Display
♦ 21-Inch Display (with/without touchscreen)
♦ GCIO Interface Module (with/without touchscreen)
♦ Random Array of Independent Disks (RAID).
The following table lists controllers, gateways, and devices for systems with Solaris 8 operating
system and lists which device configurations are supported.
Table 9-6. Controllers, Gateways, Devices for Systems with Solaris 8 Operating System
Nodebus Control Ethernet Control

Component Network Network
Allen-Bradley Data Highway™ Gateway Yes No
Integrator 30 for Allen-Bradley PLCs Yes No
Allen-Bradley PLCs Yes Yes
(for direct connection to AW51 via Ethernet)
Allen-Bradley Station Yes No
Device Integrator 15/30/30B Yes No
Foreign Device Gateway (FDG) Yes No
GE FANUC™ Programmable Controllers No No
Hydrostatic Interface Unit (HIU) Yes No
Information Network Interface 15 (INI15) Yes No
Instrument Gateway Yes No
128
Table 9-6. Controllers, Gateways, Devices for Systems with Solaris 8 Operating System (Continued)
Nodebus Control Ethernet Control

Component Network Network
Intelligent Field Devices Yes Yes
INTERSPEC™ Integrator 30 Yes No
Integrator 30 for Modbus Devices Yes No
Integrator for ModbusPlus Devices Yes No
Gateway For Modbus Devices Yes No
Modicon® Programmable Controllers Yes Yes
(for direct connection to stand-alone AW51 via RS-232)
The following table lists controllers, gateways, and devices for systems with Windows XP operat-
ing system and lists which device configurations are supported.
Table 9-7. Controllers, Gateways, Devices for Systems with Windows XP Operating System
Nodebus Ethernet
Component Control Network Control Network
Allen-Bradley Data Highway Gateway Yes No
Integrator 30 for Allen-Bradley PLCs Yes No
Allen-Bradley PLCs Yes Yes
(for direct connection to AW70 via Ethernet or
PKTX card)
Allen-Bradley Station Yes No
I/O Gate Yes Yes
Device Integrator 15/30/30B Yes No
Foreign Device Gateway (FDG) Yes No
GE FANUC Programmable Controllers No No
Hydrostatic Interface Unit (HIU) No No
Information Network Interface 15 (INI15) No No
Instrument Gateway No No
Intelligent Field Devices Yes Yes
INTERSPEC Integrator 30 Yes No
Integrator 30 for Modbus Devices Yes No
Integrator for Modbus Plus Devices Yes No
Gateway For Modbus Devices Yes No
Modicon Programmable Controllers Yes Yes
(for direct connection to stand-alone AW70 via RS-232)
129
The following table summarizes the stations, network usage and applications:
Table 9-8. Hardware and Software Summary
Ethernet Ethernet Nodebus Nodebus

Hardware and Control Network Control Network Control Network Control Network
Software Products AW51F/G AW70P AW51F/G AW70P
Software
Operating System Solaris 8 Windows XP Solaris 8 Windows XP
FoxDraw/FoxView Yes Yes Yes Yes
Display Manager Yes1 No Yes1 No
FoxAlert Yes Yes Yes Yes
Intelligent Field Device Yes Yes Yes Yes
Configurator (IFDC)
PROFIBUS-DP Bus Yes Yes Yes Yes
Configurator
FoxAnalyst No Yes No Yes
I/A Series Batch Yes No Yes No
FoxPanels™ No Yes No Yes
Operator Action Journal Yes Yes Yes Yes
Process Summary Reporter Yes Yes Yes Yes
AIM*AT™ Suite Yes Yes Yes Yes
FoxAMI™ No No No No
Report Writer Yes No Yes No
FoxSPC Yes No Yes No
FoxDPM Yes No Yes No
I/A Series Electronic Doc Yes Yes Yes Yes
FoxPage Yes No Yes No
FoxEDM™ Yes Yes Yes Yes
FoxDMM Yes Yes Yes Yes
FoxBIS Yes No Yes No
FOXWATCH™ No No Yes Yes
Remote Plus Yes Yes Yes Yes
FoxSFC Yes Yes Yes Yes
FoxGuard No No Yes Yes
Hardware
Comm Processor No No Yes Yes
Touchscreen Yes Yes Yes Yes
Dual Head CRTs Yes Yes Yes Yes
Quad Head CRTs No No No No
Annunciator/Annunciator Yes Yes Yes Yes
Numeric Keyboard
Control Processor 60 DIN No No Yes Yes
Rail Mounted FBMs
RAID Storage Subsystem Yes Yes Yes Yes
Advanced Intelligent Tape Yes Yes Yes Yes
Mobile Workstation Yes No Yes No
Control
Integrated Control Software in Yes Yes Yes Yes
AW; 15,000 value points
130
Table 9-8. Hardware and Software Summary (Continued)
Ethernet Ethernet Nodebus Nodebus

Hardware and Control Network Control Network Control Network Control Network
Software Products AW51F/G AW70P AW51F/G AW70P
Ladder Logic in FBM Yes Yes Yes Yes
Micro-I/A Station Yes Yes Yes Yes
Connoisseur™ (MVC) Yes Yes Yes Yes
DMC Bridge Yes No Yes No
Intelligent Insights Yes No Yes No
Device Integration
Device Integrator No No Yes Yes
I/O Gate (with DDE) No Yes No Yes
A-B Data HighwayPlus™ into No Yes No Yes
AW
A-B Ethernet into AW Yes Yes Yes Yes
A-B Station No No Yes Yes
A-B Configurator Yes Yes Yes Yes
Modbus into AW Yes Yes Yes Yes
GE Ethernet into AW No Yes No Yes
760/761/762 into AW No No No No
A-B Integrator 15/30 No No Yes Yes
Modbus Integrator 15/30 No No Yes Yes
ModbusPlus Integrator 30 No No No No
INTERSPEC Integrator 30 No No Yes Yes
Device Integrator 15/30/30B No No Yes Yes
Information Network No No Yes No
Integrator 15 (INI15)
C50 FoxSCADA RTU No No No No
Networking
FoxRemote™ Yes No Yes No
Remote FoxView Yes No Yes No
Remote X-Window System™ Yes No Yes No
Data for Windows V1.0 Yes Yes Yes Yes
Data for Windows V2.3 Yes Yes Yes Yes
FoxAPI Yes Yes Yes Yes
Net-FoxAPI Yes Yes Yes Yes
1. FoxView is required for an increased capacity AW configuration.
Also note that WP70Ps do not support remote configurators, and that distributed printers are
available only on systems with the Solaris 8 operating system.
131
132
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 current hard drive for protection during restoration after release upgrades.
The following files might be rewritten during the release update process.
Release Update Changes AP WP AW

Customized Initial Displays
/usr/custom/Initial_Disp X X
/usr/fox/ia16/usr/custom/Initial_Disp X X
For a list of standard I/A Series files and directories that should be backed up from your pre-V7.0
hard drive prior to performing a Day 0 upgrade to V7.0 software, refer to the appendix titled
“Files to Back Up/Restore” in V7.0 Upgrade Considerations (B0400QD).
133
B0400QM – Rev A Appendix A. Files to Back Up/Restore
134
Appendix B. EEPROM Revision
Levels
This appendix indicates specific modules’ EEPROM and/or V7.1 software revision levels. For
instructions on updating EEPROM firmware, see “EEPROM Update Action” of System
Management Displays (B0193JC).
NOTE
In the following tables, dashes indicate that the revision is unchanged from the previ-
ous release. N/A indicates that the station or module is not available for that I/A Series
software release.
The following table lists control stations, their EEPROM revision levels, and their software revi-
sion levels for V7.0 and V7.1.
Table B-1. EEPROM and Software Revision Levels of Control Stations
Software EEPROM
Revision Level Revision Level
Station
Description Mnemonic V7.0 V7.1 V7.0 V7.1
A-B Data Highway Gateway AB-GW 6.1.4 – 2.20 –
A-B Data Highway Gateway Redundant AB-R-GW 6.1.4 – 2.20 –
Allen-Bradley Station ABSTN 6.2.1 – 2.20 –
Control Processor 10 CP10 6.1.5 – 2.20 –
1
Control Processor 30B CP30B 6.1.4 – 3.30 –
Control Processor 40B CP40B 6.1.4 6.1.5 3.301 –
Control Processor 60 CP60 6.4 6.5.2 3.302 –
FoxGuard Manager FOXG 6.2.1 – 4.2.2 –
Instrument Gateway 10 Inst GW 6.1.4 – 2.20 –
Integrator 30 for A-B PLCs GW30AB 6.1.4 – 1.20 –
Integrator 30B for A-B PLCs AB30-Style B GW 6.1.4 6.1.5 3.30 3.31
Integrator 30 for MG PC GW30MOD 6.1.4 – 1.20 –
Integrator 30B for MG PC MG30-Style B GW 6.1.4 6.1.5 3.30 3.31
INTERSPEC Integrator 30 GW30IS 6.1.4 – 1.20 –
INTERSPEC Integrator 30B IS30-Style B GW 6.1.4 – 3.30 3.31
Device Integrator 30 DI30 6.1.4 – 2.20 –
Device Integrator 30B DI30B 6.1.4 6.1.5 3.30 3.31
Micro-I/A Type 1 Station Micro-I/A 6.2.3 6.2.5 62.3 62.4
®
Modbus Plus ModBusPlus 6.1.4 – 1.00 –
Modbus Plus Redundant ModBusPlus-Red 6.1.4 – 1.00 –
Modicon® Gateway MOD-GW 6.1.4 – 2.20 –
135
B0400QM – Rev A Appendix B. EEPROM Revision Levels
1.
Control Processor Style Bs must be booted with V6.1.4 control software before the EEPROM is
updated to 3.30. See “Determining EEPROM Version” on page 140 and “Performing an
EEPROM Update” on page 140.
2. Control Processor 60s must be booted with V6.4 control software before the EEPROM is
updated to 3.30. See “Determining EEPROM Version” on page 140 and “Performing an
EEPROM Update” on page 140.
The following table lists communication stations, and their software version and EEPROM
revision levels.
Table B-2. EEPROM Revision Levels of Communication Stations
Software Version EEPROM Revision Level

Description Station Mnemonic V7.0 V7.1 V7.0 V7.1
Communication Processor 10 COMM10 6.4 6.5.1 2.20 –
Carrierband LAN I/F LI 6.4 6.5.1 2.12 –
The following table lists miscellaneous stations and peripherals and their EEPROM revision
levels.
Table B-3. Miscellaneous EEPROM Revision Levels
EEPROM Revision Level

Description Station Mnemonic V7.0 V7.1
Workstation Processor 20 WP20 2.19m –
Workstation Processor 30 WP30 2.9 –
GCIO Primary GCIO Primary 5.6 –
GCIO Interface GCIO Interface 1.3 –
Keyboard KBD 5.9 –
Annunciator Keypad AKP 5.8 –
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: <V7.1 Software Version>

EEPROM REV: 61.1
NOTE
EEPROM version 61.1 supports replacement (ORBIT) FBM hardware. FBMs with
an EEPROM level of 40.1 are not required to EEPROM update to Level 61.1. Note
that version 61.1 EEPROM firmware is compatible with the older style FBMs.
136
Appendix B. EEPROM Revision Levels B0400QM – Rev A
Table B-4. Software Versions of 100 Series FBMs (Y Form Factor)
Software Version
Devices Using IOM ID V7.0 V7.1
FBM01, FBM02, FBM03, FBM03A, FBM03B, FBM19, IOM 01 42.4 –
FBM33, FBM33A, FBM33B, BAMM01, BASM02, BASM03,
BASM33, F1M01A, F1M01C, F1M01E, F1M01F, F1M02,
F1M03A, F1M03C, H2C02A, H2C02B, H2C02D through H,
H2C02J through N, H2C02P through Z, H2D02A through E,
H2D02G, H2D02H, H2J02A through H, H2M01A through D,
H2M02, H2M02A, H2M02B, H2M02E, H2M03, H2M03A
through G, H2V02B through H, H2V02J, H2V02L through N,
H2V02P through R, H2X02A through H
FBM04, FBM05, F1M04A, F1M04B, H2M04 IOM 02 42.3 –
H2C02A, H2C02B, H2C02F, H2C02G, H2C02J, H2C02K, IOM 03 42.2 –
H2C02P, H2C02Q, H2C02S, H2C02T, H2C02X, H2C02Y,
H2D02A through E, H2D02G, H2D02H, H2J02A, H2J02B,
H2J02F, H2J02G, H2M01A, H2M02, H2M02A, H2M02B,
H2M02E, H2M03A, H2M03B, H2M03F, H2M03G, H2V02B
through H, H2V02J, H2V02L through N, H2V02P through R,
H2X02A through H, H3M03
FBM06, F1M06, H2M06, H2M06A, H3M06 IOM 04 64.1 –
FBM07, FBM07A, FBM07B, FBM08, FBM09, FBM09A IOM 05 41.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, IOM 06 42.1 –
FBM12B, FBM13, FBM20, FBM21, FBM24, FBM24A
through C, FBM25, FBM25A through C, F1M07, H2M24,
H3M07
<PULSE> FBM07A, FBM07B, FBM08, FBM12A, FBM12B, IOM 07 41.1 –
FBM13, FBM20, FBM21, FBM24, FBM24A through C,
FBM25, FBM25A through C, F1M07, H2M24, H3M07
<LADDER> FBM07A, FBM07B, FBM08, FBM09A through D, IOM 08 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 IOM 09 42.3 –
FBM18, FBM43 IOM 12 62.1 –
<HTG> FBM23 IOM 13 40.2 –
FBM38 IOM 22 40.4 –
FBM39, FBM44 IOM 23 62.1 –
Display IOM 28 40.2 –
<MDACT> FBM17, FBM17A through D, H2M17 IOM 34 42.2 –
<MDPUL> FBM17, FBM17A through D, H2M17 IOM 36 42.2 –
<Multibaud> FBM18 IOM 37 42.3 –
137
Table B-4. Software Versions of 100 Series FBMs (Y Form Factor) (Continued)
Software Version
Devices Using IOM ID V7.0 V7.1
<Multibaud> FBM39 IOM 38 61.1 –
<Gas Chromatograph> FBM45 IOM 39 40.1 –
42.2 masked
FBP10 IOM 42 62.1 6.3.2
FBP11 (SMI, UCM) IOM 43 42.8 6.3.2
FBP12 (FIO) IOM 44 62.1 6.3.2
FBP13 (UFM) IOM 45 42.8 6.3.2
FBP14 (UIO) IOM 46 42.8 6.3.2
FBP10R IOM 47 62.1 6.3.2
FBP11R IOM 48 42.8 6.3.2
FBM46 IOM 49 61.1 –
<PID> FBM04, FBM17, FBM17A through D, FBM22, H2M17 IOM 52 61.2 –
FBM37, BAOM37, H3M37 IOM 53 42.1 –
H3M01 IOM 54 4.21.05.03 –
BASI03 IOM 55 5.06.05.03 –
BDSM06 IOM 55 5.06.03.03 –
BASI01, BASM01 IOM 56 4.21.05.03 –
BASO37 IOM 56 4.21.04.03 –
FRM701, FRM711, FRMMPU IOM 57 4.21.07.03 –
F2M68A IOM 58 4.21.05.03 –
F2M67A IOM 59 4.21.06.03 –
<FoxCom> FBM43 IOM 73 61.2 –
Table B-5 lists 200 Series FBMs and their software versions. 200 Series FBMs and communica-
tion modules must be EEPROM updated. Software and EEPROM revision levels for 200 Series
FBMs and most associated modules (except FCMs and FBI10E) are displayed in the System
Management Equipment Information display as follows:
SOFTWARE REV: <FBM> <V7.1 Software Version> or <V7.1 Software Version> <FBM>
EEPROM REV: ROM <V7.1 EEPROM Revision Level>
EEPROM revision levels for Fieldbus Communication Modules (FCMs) and the FBI10E are
indicated in the SOFTWARE REV A and SOFTWARE REV B fields in the System Management Equip-
ment Information display.
Table B-5. Software Versions of 200 Series FBMs (DIN Rail Mounted FBMs) and FCMs

Devices Using IOM ID V7.0 V7.1 V7.0 V7.1
WFCM10Ef, WFCM10E, FCM10E, IOM 82 1.11 1.13 1.11 1.13
FCM10Ef, FBI10E, DCM10E,
DCM10Ef (FCM)1
FBM201, WAI01A through D, IOM 83 1.05 – 1.05 –
WAW01A through F, WAX01A
through C
138
Table B-5. Software Versions of 200 Series FBMs (DIN Rail Mounted FBMs) and FCMs (Continued)

Devices Using IOM ID V7.0 V7.1 V7.0 V7.1
FBM202, FBM202B, WAI02A, IOM 84 1.05 – 1.05 –
WAV02A, WAX02A
FBM203, FBM203B, WRF03A, IOM 85 1.05 – 1.05 –
WRF03B, WRT03A, WRT03B
FBM204, WLJ04A through C IOM 86 1.05 – 1.05 –
FBM205 IOM 87 1.05 – 1.05 –
FBM206, WPA06A IOM 88 1.05 – 1.05 –
FBM207, FBM207B, FBM207C, IOM 89 1.11 – 1.11 –
WCI07A, WDI01A through E,
WID07A through P
FBM211, WAH01A through D IOM 90 1.05 – 1.05 –
FBM212 IOM 91 1.05 – 1.05 –
FBM213 IOM 92 1.05 – 1.05 –
FBM237, WAO37A through G IOM 93 1.05 – 1.05 –
FBM241, FBM241B through D IOM 94 1.11 – 1.11 –
FBM242, WBO09A, WBO09B, IOM 95 1.11 – 1.11 –
WRO09A through D, WTO09A
FBM217 IOM 96 1.11 – 1.11 –
FBM243, FBM246 (FoxCom™) IOM 97 2.06 – 2.06 –
FBM219 IOM 98 1.11 – 1.11 –
FBM214 (HART) IOM 214 2.10 2.12 2.10 2.12
FBM215 (HART) IOM 215 2.10 2.12 2.10 2.12
FBM216 (HART) IOM 216 2.10 2.12 2.10 2.12
FBM218 (HART) IOM 218 2.10 2.12 2.10 2.12
FBM220 (FOUNDATION fieldbus H1) IOM 220 2.07 2.15 2.07 2.13
FBM221 (FOUNDATION fieldbus H1) IOM 221 2.07 2.15 2.07 2.13
FBM223 (Profibus-DP) IOM 223 1.00 1.01 1.00 1.01
FBM224 (Modbus) IOM 224 N/A 1.00 N/A 1.00
1.
The EEPROM version for Fieldbus Communication Modules (FCMs) is indicated in the fields
SOFTWARE REV A and SOFTWARE REV B in the Equipment Information display.
For instructions on updating EEPROM firmware, see “EEPROM Update Action” of System
Management Displays (B0193JC).
B.1 Firmware Upgrade

All control stations, Fieldbus Communications Modules (FCMs), FBI10E modules, and DIN rail
mounted FBMs that are at an EEPROM revision less than is indicated in the V7.1 column of
Table B-5 must be updated via an EEPROM upgrade.
139
! CAUTION
1. Performing an EEPROM update forces the module off-line until completion of
the EEPROM update.
2. For non-fault-tolerant stations and fault-tolerant stations, the station is off-line
during the update.
3. Each module of the fault-tolerant pair must be updated to the same EEPROM
version.
4. The station must be rebooted with the V7.1 image before the EEPROM is
modified.
Select a workstation (WP, AW, or PW) that has been designated during System Monitor configu-
ration to have access to the secured actions of the Equipment Change display.
B.2 Determining EEPROM Version

Determine the current EEPROM version before performing EEPROM updates. Perform the
following:
1. Enter System Management.
♦ From Display Manager, select Sys from the top menu bar, then select Sys_Mgmt
from the pull-down menu, or
♦ From the FoxView system, select System from the top menu bar.
2. Select the System Monitor whose domain contains the station or module to be
EEPROM updated.
3. From the System Monitor Domain display, select the letterbug of the station or
module to be EEPROM updated.
4. Select the CONFIG soft key. The PIO Network appears, with the graphic for the station
selected by default (shows in black).
5. Select the EQUIP INFO soft key to access the Equipment Information display.
6. Select the down-arrow paging soft key located at the bottom right of the screen to dis-
play the second page of information. The PRIM EEPROM REV (and SHAD EEPROM REV
for fault-tolerant modules) indicates the current revision levels.
B.3 Performing an EEPROM Update

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

b. The EEPROM update may take several minutes. Standard system messages indi-
cating the results of the update are sent to the system printer.
c. The station reboots at the completion of the update. Verify that the EEPROM
revision is the same value as is indicated in the V7.1 column of the appropriate
table listed above by selecting the EQUIP INFO soft key and displaying the second
page of information.
Fault-Tolerant Station
a. Select EEPROM UPDATE.
b. A dialog box appears offering the option to update the PRIMARY, SHADOW,
BOTH, or CANCEL. Perform the EEPROM update procedure on the shadow
module first to reduce the number of role changes.
! CAUTION
Selecting EEPROM UPDATE of the primary module causes a role change with the
shadow module. If the fault-tolerant station is running as a single station, selecting
EEPROM UPDATE takes the control station off-line. It is not recommended that
you select BOTH as it takes the station, instead of just one module, off-line during
the update.
c. The EEPROM update may take several minutes. Standard system messages
indicating the results of the update are sent to the system printer.
d. The station reboots at the completion of the update. Verify that the EEPROM
revision is the same value as is indicated in the V7.1 column of the appropriate
table listed above by selecting the EQUIP INFO soft key and displaying the second
page of information.
e. Repeat Steps a through d for the primary module, if you have not already per-
formed them.
141
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. 0603

b0400qm A

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

b0400qm A

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

b0400qm A

Uploaded by

Copyright:

Available Formats

B0400QM

I/A Series A2™ System

Copyright 2003 Invensys Systems, Inc.

1.2.4.2 Configuring PCL3 Printers on an I/A Series UNIX Workstation ..................... 11

1.2.13.2 Take Intelligent Field Devices Off Scan ........................................................... 24

1.2.23.2 Incorrect Graphical Representation of an IFDC Point Calibration

2. UNIX System Setup ........................................................................................................ 37

3. Windows XP System Setup ............................................................................................. 41

4. Upgrade Considerations .................................................................................................. 45

5. Installing V7.1 Release Update on 50 Series.................................................................... 55

5.2.2 Saving Control Databases (SaveAlls) .......................................................................... 56

6. Installing V7.1 Release Update on 70 Series.................................................................... 63

7. Operational Recommendations ....................................................................................... 71

7.5 How to Report Problems .................................................................................................. 72

8. Enhancements and Problems Resolved ............................................................................ 93

8.2.12 Display Manager ................................................................................................... 102

9. Release Features and Configurations ............................................................................. 103

50 Series and 70 Series Conventions

Naming Conventions for UNIX Workstations

Naming Conventions for Windows Workstations

Document Title Part Number

Document Title Part Number

Document Title Part Number

1.1 Release Overview

1.1.1 Installation Overview

Install I/A Series Refer to V7.0 Installation

Review V7.1 Kits in

Time Estimation V7.0 Upgrade Considerations

Back Up/Restore Refer to Appendix A “Files to

1.1.3 On-Line Upgrade

1.1.4 Bootless Control Station Upgrade Procedure Not Available

1.1.5 FBM and Communication Modules EEPROM Updates

1.1.6 Micro-I/A Station EEPROM Update Required

1.1.7 Upgrade and Compatibility Issues

1.1.8 System Definition 2.4.1

1.1.9 FoxView V9.0 Software

1.1.10 I/A Series Electronic Documentation CD-ROM

1.2 User Notes for V7.1 I/A Series A2 Software

1.2.1 Software Installation

1.2.1.2 Day 1 Commit Diskette Issues

1.2.2 Windows XP Operating System

1.2.2.1 Windows XP System Recovery Techniques

1.2.2.2 Minimizing and Restoring Applications from the Task Bar

1.2.2.3 Bringing an Active Window Forward

1.2.2.4 Customizing Autologon for Stations Running I/A Series Software

1.2.2.5 Using telnet and ftp Utilities on a Windows XP Workstation

1.2.2.6 Reducing Network Traffic by Stopping Windows XP Services

1.2.2.7 Changing the Subnet Mask to Communicate with a Network

1.2.2.8 CPU-Intensive Applications May Cause Sluggish Performance

1.2.3 Solaris 8 Operating System

1.2.3.1 Booting into OpenWindows Without Mouse and Keyboard

1.2.3.3 Using the “prune” Option with the “find” Command

1.2.3.4 Letterbug Mapper Running on Solaris 8

1.2.4.2 Configuring PCL3 Printers on an I/A Series UNIX Workstation

1.2.4.3 Annunciator Horns on WP70C (CAR #1002783)

1.2.4.4 Starting a Workstation with McAfee VirusScan Enterprise 7.0 and

1.2.4.5 Communication Processor 10 (COMM10) Resource Issue

1.2.4.6 Running Exceed Applications on a Multi-Headed Workstation