Specifications

ManualsBrandsSeagate ManualsInternal Hard DrivesMedalist 2120

RS3t

Software

Release Notes

Performance Series 1, Release 4.2

February 2002

U.S. Manual PN: 12P23600102

Summary of content (202 pages)

PAGE 1
RS3t Software Release Notes Performance Series 1, Release 4.2 February 2002 U.S.
PAGE 2
E 1987--2002 Fisher-Rosemount Systems, Inc. All rights reserved. Printed in the U.S.A. Components of the RS3 distributed process control system may be protected by U.S. patent Nos. 4,243,931; 4,370,257; 4,581,734. Other Patents Pending. RS3 is a mark of one of the Emerson process Management group of companies. All other marks are property of their respective owners.
PAGE 3
License Agreement Definitions: The term “You” includes, but is not limited to, users of the Fisher-Rosemount Systems, Inc. (FRSI) product embodied in the computer program herein, the user’s employer, the employer’s wholly owned subsidiaries, parent company, agents, employees, contractors, and subcontractors.
PAGE 4
LIMITED WARRANTY: FRSI warrants the media on which the program is furnished to be free from defects in materials and workmanship under normal use for a period of ninety (90) days from the date of delivery to you as evidenced by a copy of your invoice. However, FRSI does not warrant that the functions contained in the program will meet your requirements or that the operation of the program will be uninterrupted or error free.
PAGE 5
Comment Form RS3t Manuals Software Release Notes Please give us your feedback to help improve this manual. Never Rarely Sometimes Usually Always D configuring making changes or enhancements ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ D operating the system ______ ______ ______ ______ ______ D troubleshooting D other __________________________ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ ______ 1.
PAGE 6
Name Place stamp here Company Address Fisher-Rosemount Systems, Inc. Technical Documentation 8627 Mopac Expressway North Austin, Texas 78759 U.S.A. Seal with tape.
PAGE 7
RN: vii RS3t Software Release Notes About This Manual This document provides information about Performance Seriest Version 1, Release 4.2 (P1 R4.2) software. Section 1: Lists Version P1 enhancements to RS3t. Section 2: Lists software and hardware requirements for Version P1, Release 4.x. Section 3: Lists system improvements, including corrected software discrepancies. Section 4: P1 R4.x changes to RS3 manuals. Section 5: Version P1 R3.4 changes to RS3 manuals.
PAGE 8
RN: viii Changes for These Release Notes These Release Notes supercede previous P1 R4 Release Notes, and cover all current releases of P1 R4 (R4.0, R4.1, and R4.2). References or requirements that pertain to all three releases are shown as P1 R4.x. References to a particular release are identified specifically, for example, P1 R4.2. Major changes for these revised Release Notes include: D D D RS3: Software Release Notes for P1 R4.
PAGE 9
RN: ix Revision Level for This Manual Refer to This Document: For This Software Version: Title Date Part Number P1 R4.2 Software Release Notes February 2002 12P23600102 P1 R4.0 Software Release Notes May 2000 12P23600101 P1 R3.4 Software Release Notes September 1999 12P21360101 P1 R3.2.2 Software Release Notes August 1999 10P56870109 P1 R3.3 Software Release Notes July 1999 10P56870108 P1 R3.2 Software Release Notes September 1998 10P56870107 P1 R3.
PAGE 10
RN: x References to Other Manuals References to other RS3 user manuals list the manual, chapter, and sometimes the section as shown below. Sample Entries: For ..., see CC: 3. Manual Title Chapter For ..., see CC: 1-1.
PAGE 11
RN: xi Reference Documents Prerequisite Documents You should be familiar with the information in the following documents before using this manual: System Overview Manual and Glossary Software Loading and Upgrade Procedure, Including Batch, Performance Series 1 1984-2640-21x0 12P23600201 Related Documents You may find the following documents helpful when using this manual: ABC Batch Quick Reference Guide 1984-2818-1104 ABC Batch Software Manual 1984-2654-21x1 Alarm Messages Manual 1984-2657-19x1 Con
PAGE 12
RN: xii RS3: Software Release Notes for P1 R4.
PAGE 13
RN: xiii Contents Section 1: Section 2: P1 Enhancements to RS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 New P1 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Recent Hardware Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary of Recent Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 14
RN: xiv Section 3: Section 4: Section 5: System Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Corrected Discrepancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 P1 R4.x Changes to RS3 manuals . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 SV — Pixel Board Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68020 OI Processor EPROM Upgrade . . . . . .
PAGE 15
RN: xv DT: Chapter 3 (Theory of Operations) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DT: Chapter 4 (Hints) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O Block Configuration Manual Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO: Chapter 3 (Pulse Blocks) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO: Chapter 5 (Configuring Redundant Input/Output Blocks) . . . . . .
PAGE 16
RN: xvi List of Figures Figure 4.1. 68020 IO Processor Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Figure 4.2. EPROM Pin Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Figure 4.3. 68040 IO Processor Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Figure 4.4. EPROM Pin Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Figure 4.5.
PAGE 17
RN: xvii List of Tables Table 1.1. Summary of New Software Features in P1 . . . . . . . . . . . . . . . . . . . . . 1-2 Table 1.2. Summary of Recent P1-Compatible Hardware . . . . . . . . . . . . . . . . . . 1-5 Table 1.3. RS3 Base System Software Compatibility Matrix (English) . . . . . . . . 1-7 Table 1.4. ROS Software Compatibility Matrix (English) . . . . . . . . . . . . . . . . . . . . 1-8 Table 2.1. Supported PeerWay Node Hardware Combinations for P1 PeerWay Image Designation . . . . . . . .
PAGE 18
RN: xviii Table 2.25. CPIV or CPIV+ Batch CP ControlFiles with MPCII Controllers . . . . 2-24 Table 2.26. CPIV or CPIV+ Standard CP ControlFiles with MPCII Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 Table 2.27. CPIV+ ControlFile with MPCII and Standard Controllers . . . . . . . . . 2-25 Table 2.28. CPII ControlFile with MPCII and Standard Controllers . . . . . . . . . . . 2-26 Table 2.29.
PAGE 19
RN: 1-1 Section 1: P1 Enhancements to RS3 The software version numbers of the subsystems for P1, Release 4.2 are as follows: D Console (MTCC) P1.30 D System Manager Station (SMS) P1.30 D Coordinator Processor (CP) P1.15 D Controller Processor P1.19 D Supervisory Computer Interface P1.02 D RS3 Operator Station (ROS) 4.x (separate media) D RS3 Network Interface (RNI) 4.x (separate media) Table 1.1 describes new features of the P1 releases. NOTE: In Table 1.
PAGE 20
RN: 1-2 New P1 Software Features The following table lists new features and enhancements to P1. Table 1.1. Summary of New Software Features in P1 Description Feature CP5 Coordinator Processor P1 R4.0 with CP5 Coordinator Processor supports mixing MPCII and MPC5 controllers within the same ControlFile. For More Information When Added ---- P1 R4.0 BA:2 and 4 BQ:6 RB:10 P1 R3.4 and ROS 3.2 RN:4 P1 R3.4 Improved Batch performance ABC Batch Messaging supported RS3 supports ABC Batch Messaging.
PAGE 21
RN: 1-3 Table 1.1. Summary of New Software Features in P1 (continued) Feature Description For More Information When Added Automatic backups Capability has been added for automatic backups of plant and console configurations. RN:4 P1 R1.2 Batch on SMS Batch commands now available on System Manager Station (SMS). RN:4 P1 R1.2 Master License Agreement User must now confirm Master License Agreement to continue the restore operation of a program file or folder. RN:4 P1 R1.
PAGE 22
RN: 1-4 Table 1.1. Summary of New Software Features in P1 (continued) Description For More Information When Added HART Command The “Stop HART Comm” command must be executed anytime a third party HART valve product is being used IO:8 P1 R1.0 Modbus The new Modbus broadcast message will allow PLCBs to be configured with PLC=0 to designate a “broadcast” message. This will only apply to write messages and for this reason the user will not be allowed to configure the read option in this case.
PAGE 23
RN: 1-5 Summary of Recent Hardware Releases Table 1.2 lists recently released hardware that operates in the P1 environment. This is not a complete list, but is provided as a guide to make you aware of newer hardware. Table 1.2. Summary of Recent P1-Compatible Hardware When Added Description Part Number 10P5736X022 CP5 Coordinator Processor P1 R4.0 12P23040001 Seagate MEDALIST Pro (4.5 Gigabyte, narrow SCSI) disk drive P1 R4.
PAGE 24
RN: 1-6 Table 1.2. Summary of Recent P1-Compatible Hardware (continued) Part Number 12P0238X012 12P0236X012 12P0239X012 Description Power Supply Unit: Single 1200 watt Power Module Housing (supports two (2) Power Modules) When Added P1 R3.0 Fan Replacement Kit 10P58300005 MAI32, 32 Point Analog Input FIM P1 R3.4 10P58080005 MAO16, 16 Point Analog Output FIM P1 R3.4 10P58900001 Pixel Graphics Card P1 R3.
PAGE 25
RN: 1-7 Summary of Recent Releases Table 1.3 and Table 1.4 show recently released software and hardware. Use these as a guide to understanding valid, compatible combinations, and to plan for the future DeltaV Operate for RS3 Operator Stations. DeltaV Operate for RS3 lets you operate your RS3 from DeltaV consoles. DeltaV is Emerson Process Management’s latest control system. This is not a complete list, but is provided as a guide. Consult Section 2 for more specifics on any requirements. Table 1.3.
PAGE 26
RN: 1-8 Table 1.4. ROS Software Compatibility Matrix (English) Features of this Release Base System Software Version Available for Shipment ROS SystemWide Tag License ROS 4.0.1 with SP 1 Yes Yes Yes ROS 4.0 No Yes ROS 3.2 Yes ROS 3.1.2 Yes (1) (2) ROS ABC Compatible Batch with CF Messaging V18 Images Use With Base System Software Version Compatible with Future DeltaV Operate for RS3 No P1 R3.4 and above(1) Yes(2) Yes No P1 R3.4 and above(1) Yes(2) No Yes No P1 R2.
PAGE 27
RN: 2-1 Section 2: P1 Software and Hardware Requirements This section specifies the software and hardware requirements for RS3 P1 R4.x and provides information about the coexistence of RS3 software images to facilitate plant upgrades. Definition of RS3 Software Terms The following are definitions of RS3 software terms used in this document. Software Image A software image is an individual file that is loaded into one component of RS3 hardware.
PAGE 28
RN: 2-2 PeerWay Image Designation A PeerWay Image Designation defines the collection of images running together on a PeerWay. This is a subset of the images contained within a software release. A P1 PeerWay Image Designation is when all the images running together on a PeerWay are P1 images only, from the same Software Release. There can be no V18 images on the PeerWay with a P1 PeerWay Image Designation. Typically P1 images support the latest technology.
PAGE 29
RN: 2-3 Table 2.1. Supported PeerWay Node Hardware Combinations for P1 PeerWay Image Designation ControlFiles(1) Consoles Future DeltaV Operate for RS3 ROS MTCC or SMS Coordinator Processors Memory Controllers Consult Tables for Boot ROM and Images Yes ROS 4.0.1 with SP 1 68040 CP5 4 MB NV RAM MPC5 Table 2.14 or Table 2.15, and Table 2.22 CP5 4 MB NV RAM MPC5 MPCII Table 2.16 or Table 2.17, and Table 2.22 CPIV+ or CPIV 4 MB NV RAM MPC5 Table 2.18 or Table 2.19, and Table 2.
PAGE 30
RN: 2-4 DeltaV Operate for RS3 lets you operate your RS3 from DeltaV consoles. On the DeltaV screen, you can see and manipulate data and information from RS3. DeltaV Operate for RS3 will allow current MTCC or ROS users to migrate to newer technology. When combined with DeltaV controllers, data from both RS3 and DeltaV equipment can be combined on the same process graphic on the DeltaV Operate for RS3 consoles.
PAGE 31
RN: 2-5 Table 2.2. Supported Peerway Node Hardware Combinations for P1/V18 Combined PeerWay Image Designation ControlFiles(1) Consoles Future DeltaV Operate for RS3 ROS MTCC or SMS Coordinator Processors Memory Controllers Consult Tables for Boot ROM and Images No ROS 3.1.2 68040 CPIV+ or CPIV 4 MB NV RAM MPC5 Table 2.23 or Table 2.24, and Table 2.29 CPIV+ or CPIV 4 MB NV RAM or 2 MB NV RAM MPCII Table 2.25 or Table 2.26, and Table 2.
PAGE 32
RN: 2-6 Unsupported Software P1 R4.
PAGE 33
RN: 2-7 D A screen print of the Disk Directory PeerWay (DDP) screen (or screens if the system is large). This screen lists all consoles that have their own hard drives on the system (master nodes). Any consoles that are listed on the PS screen but not listed on the Disk Directory PeerWay screen are slave nodes. Slave nodes (consoles that share hard drives and tape drives with a master node) have to be upgraded.
PAGE 34
RN: 2-8 Table 2.3. Nonvolatile Memory Card Identification D Memory Part Number Comments 4 MB 1984--2347--0041 RAM; Required with CP5 Coordinator Processor and/or MPC5 controllers 2 MB 1984--2347--0021 RAM; Used with ABC Batch and CPIV; (Minimum Required for P1 PeerWay Image Designation) 1 MB 1984--2347--0011 RAM; Used only with CPII 1 MB 1984--1598--0001 Bubble Memory; Used only with CPII 0.5 MB 1984--1483--0001 1984--1224--000x Bubble Memory; Used only with CPII Use Table 2.
PAGE 35
RN: 2-9 See the VAX section to determine if your current VAX interface software will work with P1 R4.x software. Determining Upgrade Requirements The following pages include compatibility charts that list detailed hardware and software requirements for P1 R4.x. If you are a current user who is upgrading to P1 R4.x, you need to make sure your system meets these requirements. If it does not, contact your Emerson Process Management sales or service representative.
PAGE 36
RN: 2-10 Table 2.4. P1 R4.
PAGE 37
RN: 2-11 Table 2.6. P1 R4.x/68040 System Manager Station (SMS) with Hard Drive and Tape Drive Tape Drives Supported Hard Drive Minimum Processor Boot ROM Seagate ST34520N 4.5 Gigabyte Tandberg 150 Meg Viper 2150S 11 10 11.10 Quantum Thunderbolt, Thunderbolt 540 Meg Tandberg 150 Meg Viper 2150S 11 10 11.10 IBM DeskStar 540, 540 540 Meg Tandberg 150 Meg Viper 2150S 11 10 11.
PAGE 38
RN: 2-12 Table 2.9. P1 R4.x/SMS Console Boot ROM and Graphics Card Requirements Boot ROM OI Processor Board w/Graphics Card 10P55270011 (all revs) 1984--3204--1112 (Ver 11.12) 1984--2503--0001 or 10P58900001 10P55270011 (all revs) 1984--3204--1110 (Ver 11.10) 1984--2503--0001 NOTE: The Boot ROM level X.YY is the minimum required; a higher .YY number will also work. Table 2.10.
PAGE 39
RN: 2-13 Table 2.11. P1 R4.x/Console Accessory Requirements Keyboard Revisions Device Boot ROM Option Description Part Number 4.02 Enhanced Operator/ Engineering Keyboard 10P5084x004 * 1984--3222--x004 1984--2889--x004 3.7 Enhanced Operator/ Engineering Keyboard 1984--1978--0003 1.4 Configure Keyboard 1984--1978--0001 Trackball Card Assembly (TB) 1.1 Trackball 10P5285000x 1984--2662--000x 1984--1975--000x Display Panel (DISPPNL) 1.
PAGE 40
RN: 2-14 Table 2.12. Definition of Terms Definition Console Type MTCC Multitube Command Console SMS System Manager Station ECC Enhanced Command Console BCC Basic Command Console MC MiniConsole 68040 A console using the 68040 processor board (10P5527001x or 1984--3202--001x). 68040 consoles are either MTCCs or SMS consoles. 68020 A console using the 68020 processor board (1984--1540--0009 or 1984--1161--0009). All 68020 consoles are MTCCs.
PAGE 41
RN: 2-15 Table 2.13. Typical Upgrade Scenarios (continued) Console 68020 SCSI Master MTCC and One Slave Node Upgrade Scenario The slave console must be split from the master and made into a master node. This requires a hard drive to make a disk-only console, or a hard drive and tape drive. Kits are available to make this change. See Console Upgrades in Section 4. Both 68020 processor boards must be replaced with 68040 processor boards using a 68040 upgrade kit.
PAGE 42
RN: 2-16 Table 2.13. Typical Upgrade Scenarios (continued) Console Upgrade Scenario 68000 SCSI Master MTCC and Two Slave Nodes with Character Graphics Both slave consoles must be split from the master console and made into master nodes. This requires at least a hard drive to make a disk-only console, or a hard drive and tape drive. Kits are available to make this change. See Console Upgrades in Section 4. All three 68000 processor boards must be replaced with 68040 processor boards.
PAGE 43
RN: 2-17 ControlFile Node Combinations Supported in P1 PeerWay Image Designation Table 2.14 through Table 2.22 show ControlFile node combinations supported in P1 R4.x for P1 PeerWay Image Designation requirements. Table 2.30 lists the part numbers for the CPs and controller processors. Table 2.14. CP5 Batch Control Files with MPC5 Controllers NV Memory CP Image $ $CP5BA_P1 _ Batch CP Hardware CP5 Boot ROM 7 01 7.01 Size/Type 4MB NV Memory (Requires 1.
PAGE 44
RN: 2-18 Table 2.16. CP5 Batch Control Files with MPCII and MPC5 Controllers NV Memory CP Image Hardware Boot ROM Size/Type Controller Image and Hardware to Support Image Controller Image File Name Controller Image Hardware Boot ROM MPC5+ $MPC5_P1 _ $CP5BA P1 $CP5BA_P1 Batch CP CP5 7.01 4MB NV Memoryy (Requires 1.17 NV Boot) PLC+ MUX+ $RBLC5_P1 MPC5 7 03 7.03 MPCII 6 05 6.05 RBLC+ MPC2+ $MPC2+_P1 PLC+ MUX+ $RBLC2_P1 RBLC+ NOTES: D These ControlFiles run P1 software on all cards.
PAGE 45
RN: 2-19 Table 2.18. CPIV or CPIV+ Batch CP ControlFiles with MPC5 Controllers NV Memory CP Image Hardware $CP4BA_P1 $ _ CPIV or Batch CP CPIV+ Boot ROM 4 02 4.02 Size/Type 4 MB NV Memory (Requires 1.17 NV Boot) Controller Image and Hardware to Support Image Controller Image File Name Controller Image Hardware Boot ROM MPC5+ $MPC5_P1 _ PLC+ MUX+ $RBLC5_P1 MPC5 7 03 7.03 RBLC+ NOTES: D These ControlFiles run P1 software on all cards.
PAGE 46
RN: 2-20 Table 2.20. CPIV or CPIV+ Batch CP ControlFiles with MPCII Controllers NV Memory CP Image Hardware $CP4BA_P1 CPIV or Batch CP CPIV+ Boot ROM 4.02 Size/Type 4 MB NV Memory (Requires 1.17 NV Boot)) or 2 MB NV Memory (Requires 1.15 NV Boot) Controller Image and Hardware to Support Image Controller Image File Name Controller Image Hardware Boot ROM MPC2+ $MPC2+_P1 PLC+ MPCII 6 05 6.05 MUX+ $RBLC2_P1 RBLC+ NOTES: D These ControlFiles run P1 software on all cards.
PAGE 47
RN: 2-21 CPI and CPII ControlFile Requirements for P1 PeerWay Image Designation CPI and CPII ControlFiles are not supported in P1 R4.x software release for P1 PeerWay Image Designation. CPI or CPII ControlFiles must be upgraded to a minimum CPIV ControlFiles or CPIV+ ControlFiles with MPCII controllers installed (see Table 2.20 and Table 2.21). Typically, the CPI’s and CPII’s are replaced with CPIV+’s and the bubble board is replaced with at least a 2 MB NV memory board to upgrade these ControlFiles.
PAGE 48
RN: 2-22 Table 2.22. I/O Requirements for P1 PeerWay Image Designation (continued) Minimum Required Type CIO MAI MAI-HD MAO MDIO Description Contact I/O MAIO Input FIM MAI High-Density (32 points) MAIO Output FIM MDIO Low Side Switch MDIO High Side Switch Part Number F-Rev S-Rev 1984 1460 0003 1984--1460--0003 31 3.1 N/A 1984--4414--0001 1984--4414--1001 10P54040004 (EMC Approved) 10P57700005 (Replaces 10P54040004) (EMC Approved) 10P53190004 (EMC Approved) 1.1 3.3 4.1 3.3 5.0 3.3 4.
PAGE 49
RN: 2-23 ControlFile Node Combinations Supported in P1/V18 Combined Peerway Image Designation Table 2.23 through Table 2.29 show ControlFile node combinations supported in P1 R4.x for P1/V18 Combined PeerWay Image Designation requirements. Table 2.30 lists the part numbers for the CPs and controller processors. Table 2.23. CPIV or CPIV+ Batch CP ControlFiles with MPC5 Controllers CP Image $CP4BA_P1 Hardware CPIV+ or CPIV NV Memory Boot ROM 4.02 Batch CP Size/Type 4 MB NV Memory (Requires 1 17 NV 1.
PAGE 50
RN: 2-24 Table 2.25. CPIV or CPIV+ Batch CP ControlFiles with MPCII Controllers CP Image $CP4BA_P1 B t h CP Batch Hardware CPIV+ or CPIV NV Memory Boot ROM 4.02 Size/Type 4 MB NV RAM (R (Requires i 1.17 NV Boot) or 2 MB NV Memory (Requires 1.15 NV Boot) Controller Image and Hardware to Support Image Controller Image File Name Controller Image Hardware Boot ROM MPC2+ $MPC2+_P1 PLC+ MPCII 6 05 6.05 MUX+ $RBLC2_P1 RBLC+ NOTES: D These ControlFiles run P1 software on all cards.
PAGE 51
RN: 2-25 Table 2.27. CPIV+ ControlFile with MPCII and Standard Controllers CP Image $CP4_18 Standard CP Hardware CPIV+ NV Memory Boot ROM 4.02 Size/Type 2 MB NV Memory (Requires 1 15 NV 1.15 Boot) Controller Image and Hardware to Support Image Controller Image File Name Controller Image Hardware Boot ROM MPC2+ $MPC2+_18 PLC+ MPCII 6 05 6.05 CC 5.15 MPC(I)(1) 5.15 MPCII(2) 6.05 MLC MLC 5.15 SSC SSC 5.15 MUX/PLC 5.15 MPC(I)(3) 5.15 MPCII(4) 6 06 6.
PAGE 52
RN: 2-26 Table 2.28. CPII ControlFile with MPCII and Standard Controllers CP Image Max Config $$CPMAX18 Hardware CPII NV Memory Boot ROM 2.70 Size/Type Controller Image and Hardware to Support Image Controller Image File Name 2 MB NV RAM (Requires 1 15 NV 1.15 Boot) or 1 MB NV RAM (Requires 1 15 NV 1.15 Boot) or Controller Image CC $$CPMAX18(1) MLC MUX 1 MB Bubble or 0.5 MB Bubble SSC $$MPCA18 MPC $$MPCAS18 MPCAS Hardware Boot ROM CC 5.15 MPC(I)(2) 5.15 MPCII(3) 6.05 MLC 5.
PAGE 53
RN: 2-27 Table 2.28. CPII ControlFile with MPCII and Standard Controllers (continued) Image Hardware Boot ROM Size/Type Controller Image File Name Controller Image $$MPCAP18 MPCAP $$MPCAT18 MPCAT $$MPTUN18 MPTUN $$SMART18 MPC $$PLCM18 PLC Hardware Boot ROM MPC(I) 5.21 MPCII(6) 6.05 MPC(I) 5.21 MPCII(6) 6.05 MPC(I) 5.21 MPCII(6) 6.05 MPC(I) 5.21 MPCII(6) 6.05 MUX/PLC 5.21 MPC(I) 5.21 MPCII(6) 6.05 (1) These controller images are part of the $$CPMAX18 image.
PAGE 54
RN: 2-28 CPI ControlFile Requirements for P1/V18 Combined PeerWay Image Designation CPI ControlFiles are not supported in P1 R4.x software. CPI ControlFiles must be upgraded to a minimum CPIV ControlFiles or CPIV+ ControlFiles with MPCII controllers installed (see Table 2.25, Table 2.26 and Table 2.27). Typically, the CPI’s are replaced with CPIV+’s and the bubble board is replaced with at least a 2 MB NV memory board to upgrade these ControlFiles. Check Table 2.25, Table 2.26 or Table 2.
PAGE 55
RN: 2-29 I/O Requirements for P1/V18 Combined PeerWay Image Designation Table 2.29 identifies the I/O requirements for P1/V18 Combined PeerWay Image Designation. Table 2.29. I/O Requirements for P1/V18 Combined PeerWay Image Designation Type Description Part Number Minimum Required F-Rev AI MLC Input FIC AIO-R Analog FIC S-Rev Use the following FIC/FIM software image 1984--1463--000x 1984--1394--000x 1984--1325--000x 1984--2412--000x N/A N/A ------ 1984--2518--0001 1.X 1.6 $$AFIC1_6 2.
PAGE 56
RN: 2-30 Table 2.29. I/O Requirements for P1/V18 Combined PeerWay Image Designation (continued) Type Description Part Number Minimum Required F-Rev 1984--1460--0003 CIO MAI MAI--HD 3.1 S-Rev N/A Contact I/O MAIO Input FIM MAI High-Density (32 points) Use the following FIC/FIM software image ------ 1984--1304--0001 1.X N/A 1984--4414--0001 1984--4414--1001 1.1 3.3 10P54040004 (EMC Approved) 4.1 3.3 10P57700005 (Replaces 10P54040004) (EMC Approved) 5.0 3.
PAGE 57
RN: 2-31 Table 2.29. I/O Requirements for P1/V18 Combined PeerWay Image Designation (continued) Type MAO MDIO Description MAIO Output FIM MDIO Low Side Switch MDIO High Side Switch Part Number Minimum Required F-Rev S-Rev 1984--4418--0001 1984--4418--0004 1.1 3.3 10P54080004 (EMC Approved) 4.1 3.3 10P58080005 (Replaces 10P54080004) (EMC Approved) 5.1 3.3 1984 4080 0001 1984--4080--0001 11 1.1 34 3.4 10P53520006 (EMC Approved) 6.6 4.0 10P53550006 (EMC Approved) 6.7 4.0 1 15 1.
PAGE 58
RN: 2-32 Table 2.30.
PAGE 59
RN: 2-33 Supervisor Computer Interface (SCI) Requirements Table 2.32. P1 R4.x/SCI Requirements Software Image $$SCIPROG Processor Board 68000 (Requires a 1 MB OI processor board) 10P57140008 1984--2759--0008 1984--2137--0008 OI NV Memory Boot ROM OI Bubble 1984--1147--000x 1984--1167--000x 8.XX OI NV RAM 1984--1547--000x 8.72 NOTE: Boot ROM level X.YY is the minimum required; a higher .YY number will also work. RS3 Network Interface (RNI) Requirements RNI software version 4.1 requires P1 R4.
PAGE 60
RN: 2-34 Memory Allocations and Plant Program Space Be sure to calculate available space for plant program images to be loaded before upgrading software. You may need to increase the size of the NV memory in the ControlFile before upgrading. Use Table 2.33 through Table 2.35, along with the worksheet (Table 2.36), to verify that enough space is available in the NV memory card. Table 2.33.
PAGE 61
RN: 2-35 Table 2.35. Controller Image Size Image Memory Size Image Memory Size $RBLC2_P1 139K $$MPCAS18 88K $MPC2+_P1 300K $$MPCAP18 87K $MPC5_P1 301K $$MPCAT18 83K $MPC2+_18 283K $$MPTUN18 89K $RBLC2_18 138K $$PLCM18 88K $RBLC5_P1 139K $$SMART18 89K $$MPCA18 88K $$STDC_18 97K Table 2.36. Free Space Worksheet Line Description 1 Free space for CP and Controller Images (from Table 2.33) 2 Size of CP Image (from Table 2.34) 3 Size of first Controller Image (from Table 2.
PAGE 62
RN: 2-36 P1 R4.0 Software Image Versions Table 2.37. P1 R4.0 Software Image Versions Image Version Image Version ECCBOOT (English) P1.30 $$MPCAS18 18.11 ECCBOOT (French) P1.31 $$MPCAP18 18.11 ECCBOOT (German) P1.32 $$MPCAT18 18.11 ECCBOOT (Russian) P1.29 $$MPTUN18 18.11 SMSBOOT (English) P1.30 $$PLCM18 18.10 SMSBOOT (French) P1.31 $$SMART18 18.10 SMSBOOT (German) P1.32 $$STDC_18 18.11 SMSBOOT (Russian) P1.29 $MPC2+_18 18.11 $CP4_P1 P1.15 $RBLC2_18 18.
PAGE 63
RN: 2-37 P1 R4.1 Software Image Versions Table 2.38. P1 R4.1 Software Image Versions Image Version $MPC2+_P1 (see Note 1) P1.18 $MPC5_P1 (see Note 1) P1.18 Image Version Note 1 This RS3 Base Software release is identical to P1 R4.0 except that Track issue #0469 has now been corrected. Only two images on the tape have changed, $MPC2+_P1 and $MPC5_P1. Emerson Process Management has issued a safety notice dated April 24, 2001, for this Release. (See KBA #AUS1--247--010419112733).
PAGE 64
RN: 2-38 RS3: Software Release Notes for P1 R4.
PAGE 65
RN: 3-1 Section 3: System Improvements This section describes improvements to the RS3 system, including corrected discrepancies. Corrected Discrepancies Table 3.1 lists discrepancies corrected for Release P1 R4.2. Table 3.2 lists discrepancies corrected for Release P1 R4.1. Table 3.3 lists discrepancies corrected for Release P1 R4.0. Table 3.4 lists discrepancies corrected for Release P1 R3.4. Table 3.5 lists discrepancies corrected for Release P1 R3.3. Table 3.
PAGE 66
RN: 3-2 Table 3.2. RS3 Corrected Software Discrepancies in P1, Release 4.1 Description Rating During a controller start or redundancy switchover, Multipoint Input values may momentarily be read at the value of zero or the low cutoff value, generating process or hardware low value alarms. This condition will only exist for several seconds and the Hold Forward flag will be set to on. This HF flag can be used to detect the system error vs. the actual alarm condition. Fixed A1 ID Controller 0469 Table 3.3.
PAGE 67
RN: 3-3 Table 3.3. RS3 Corrected Software Discrepancies in P1, Release 4.0 (continued) ID Description Rating Console 805569/148 Disk Folder search criteria is now saved for use on the next search. Fixed Controller 805466/165 Intermittent Controller crash. Fixed D4 Controller 805144/169 Intermittent Controller crash. Fixed D4 Controller 805543/170 Intermittent Controller crash. Fixed D4 CP 800293 The batch print statement “print(4,“SCF^t%511.0d”,SCxF,1) no longer causes a CP crash.
PAGE 68
RN: 3-4 Table 3.6. RS3 Corrected Software Discrepancies in P1, Release 3.2 Description ID Rating Batch 801577 Infrequently, align--on statements can fall through without aligning correctly with the appropriate comm--op icon. D2 Batch 805071 A nuisance alarm is generated when a recipe is started and an old file is automatically deleted. Batch 152627 Using redundant virtual arrays as parameters in some instructions halts the script and floods the Batch log with error messages.
PAGE 69
RN: 3-5 Table 3.6. RS3 Corrected Software Discrepancies in P1, Release 3.2 (continued) ID Description Rating Batch 805157 Some V17 ABC recipes do not upgrade, had to manually change header to get recipe to upgrade to P1 R3.2. D4 Batch 805513 Recipes won’t update in some cases unless there is at least one parameter in the Batch Operations Table Batch 805556 Console allows manually assigning same BAPU to two different recipes.
PAGE 70
RN: 3-6 Table 3.6. RS3 Corrected Software Discrepancies in P1, Release 3.2 (continued) ID Description Rating Console 801219 On the I/O block, you can change the device type even if your console does not own the plant unit for the I/O block. D4 Console On the report Read/Scan screen, entering a new file locks the console. 801281 Fixed Console 801385 Consoles might reboot if a Controller Processor is disabled while and FIC Detail screen is displayed on the console.
PAGE 71
RN: 3-7 Table 3.6. RS3 Corrected Software Discrepancies in P1, Release 3.2 (continued) ID Documentation 800442 Description Rating Trend file 0 is not adequately described in the user manuals. D3 Fixed Documentation The Associated_Text_40 fields on the bottom banner line and the list banner get clipped at 21 characters on batch and RBL generated alarms & events.
PAGE 72
RN: 3-8 Table 3.6. RS3 Corrected Software Discrepancies in P1, Release 3.2 (continued) ID Description Rating Documentation ABC Batch manual does not clearly indicate that the Batch Config screen “Recipe Support Data” disk entry controls the VDIMs, tables and scripts. D4 802478 Fixed Documentation Data may be lost if a disk shutdown (DS) is not done before powering down a console. 802819 Fixed Documentation MDIO online replacement documentation contains inconsistencies. Clarification is needed.
PAGE 73
RN: 3-9 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases Fixed in Release Number Description ID Batch 800498 Working recipe icon is wrong color after executing. Fixed. 1.0 Batch 800671 Duplicate child task started after power failure. Fixed. 1.0 Batch 800699 When you restart a Batch Working Recipe suspended in Static mode, the Recipe View menu receives a “Config” warning. 1.0 Fixed. (continued on next page) RS3: Software Release Notes for P1 R4.
PAGE 74
RN: 3-10 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Description ID Batch 801057 Fixed in Release Number When writing a character string to a string variable, the string length might be prematurely terminated. 3.
PAGE 75
RN: 3-11 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number Description ID Batch 801106 The Master Recipe validation may hang with more than 10 warnings or errors. 1.0 Batch 801183 When two batch operations are run in parallel, “Left CP Data Integrity” errors may be generated, up to a rate of 10 alarms per second.
PAGE 76
RN: 3-12 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Description ID Batch 804551 Fixed in Release Number Checksum is incorrectly calculated after a script is saved (ctrl--w). NOTE: The following information is applicable only to ABC Batch users who use the Validation “HALT” or “WARN” in any of the Batch Unit, Material or Operation Tables: 3.1 In software versions V18 through P1 R2.
PAGE 77
RN: 3-13 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number Description ID Console 152786 When viewing the Disk Directory Peerway screen, all drives are listed under the drive 1 position for several seconds. 1.0 Console 152821 When configuring a console with a blank disk, the default size of the Console Program Folder is too small to boot the console software.
PAGE 78
RN: 3-14 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number Description ID Console 801323 Console crashed during printing of a report. No alarms appeared. Fixed. 1.0 Console 801362 If more than 32 consoles and SRUs are on linked PeerWays, a console might not be able to access a process graphic on a different node. 1.0 Console 801375 One task undoes what another task had done so changes are not made. Fixed 1.
PAGE 79
RN: 3-15 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number Description ID Console 803914 On 68040 consoles, the bars and symbols on group displays and tuning displays start to disappear pixel by pixel. 1.2 Console 804165 If you enter a date later than 2000 into an SIB or HOB Date field, “0000” is actually sent to the device and is displayed incorrectly in AMS. AMS displays 01/01/2000 as 00/00/00 Fixed. 2.
PAGE 80
RN: 3-16 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number ID Description Controller 801426 RS3 V18R2.3 cannot support some PLCs because RS3 asks for more coils than are configured in the PLC. Controller 801471 On HOB, when the HOB is switching back from digital to analog, the valve display does not automatically show the right control mode. Controller 801849 An upload of the information in a smart output device cannot be completed. Fixed.
PAGE 81
RN: 3-17 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number ID Description Controller 803394 Logic prolog ramp() malfunction with multiple ramp function on a single step. Fixed. 1.2 Controller 803401 When using a PLC write Mask other than FFFF, the PLC controller is turning on bits other than those turned on in the source link. 1.
PAGE 82
RN: 3-18 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number ID Description Controller 804479 If SIB, AIB, HOB, AOB blocks are configured on addresses above 116 for a FIM, the controller will crash on an AMS I/O traversal. Controller 804250 HOB and DOB blocks do not evaluate immediately after their source comp block. They evaluate after “ALL” comp blocks have completed. Evaluation order was incorrect. Fixed. 3.
PAGE 83
RN: 3-19 Table 3.7. RS3 Corrected Software Discrepancies in Previous P1 Releases (continued) Fixed in Release Number Description ID I/O 801262 When a 4080 FIM is installed as a discrete I/O cold spare, sometimes it does not take over and start communicating with the controller. 1.0 SMS 803261 When the SMS is configured to use an enhanced keyboard, the keyboard still behaves as if it is a configuror’s keyboard. Fixed. 1.1 Fixed. RS3: Software Release Notes for P1 R4.
PAGE 84
RN: 3-20 RS3: Software Release Notes for P1 R4.
PAGE 85
RN: 4-1 Section 4: P1 R4.x Changes to RS3 manuals This section describes changes to the following Version P1 manuals. These changes occurred after the last printing of these manuals, so they supplement or correct the Version P1 set. RN Page Number Manual Service Manual 4-1 Site Preparation and Installation 4-13 I/O Block Configuration 4-13 SV — Pixel Board Upgrade To upgrade the 68020 board (1984--1540--0009) use the instructions in the paragraph titled 68020 OI PROCESSOR EPROM UPGRADE.
PAGE 86
RN: 4-2 Table 4.2. P1 R4.x/68040 Console Boot ROM and Graphics Card Requirements OI Processor Board Boot ROM w/Graphics Card 10P55270010 (all revs) 1984--3204--1010 (Ver. 10.10*) 1984--2503--0001 10P55270010 (all revs) 1984--3204--1012 (Ver 10.12*) 1984--2503--0001 or 10P58900001 * The Boot ROM level X.YY is the minimum required; a higher .YY number will also work. Table 4.3. P1 R4.
PAGE 87
RN: 4-3 PWA Number The leftmost of these 2 EPROMS is U80, the rightmost U81 Figure 4.1. 68020 IO Processor Board 3. Verify that the revision level of the board is new enough to upgrade the EPROMs. The revision of the board must be revision B/C or newer. NOTE: In order to classify as a newer revision board, both the letter before and after the ’/‘ must be greater than the letters specified.
PAGE 88
RN: 4-4 Side view of EPROM chips Unformed Pins Formed Pins Figure 4.2. EPROM Pin Alignment 7. Once formed, position the chip directly over the socket WITH THE NOTCHED EDGE OF THE SOCKET LINING UP WITH THE NOTCHED EDGE OF THE CHIP. 8. Slowly lower the chip into the socket. If the pins are not lining up with the socket holes, reform the pins as needed. Lower the chip onto the socket. When all of the pins are started into the socket holes, press the chip down firmly onto the socket. 9.
PAGE 89
RN: 4-5 PWA Number The chip on the top is in position U20, and the bottom U9 Figure 4.3. 68040 IO Processor Board 3. Verify that the revision level of the board is new enough to upgrade the EPROMS. If the board is the 1984-3202-0010, then the revision of the board must be revision F/H or newer. If the board is the 10P55270010, then all revisions of the boards are ready to be upgraded.
PAGE 90
RN: 4-6 Side view of EPROM chips Unformed Pins Formed Pins Figure 4.4. EPROM Pin Alignment 7. Once formed, position the chip directly over the socket WITH THE NOTCHED EDGE OF THE SOCKET LINING UP WITH THE NOTCHED EDGE OF THE CHIP. 8. Slowly lower the chip into the socket. If the pins are not lining up with the socket holes, reform the pins as needed. Lower the chip onto the socket. When all of the pins are started into the socket holes, press the chip down firmly onto the socket. 9.
PAGE 91
RN: 4-7 Description: The upgrade kit ( 1984-3045-0017 or 1984-3045-0018 ) includes the necessary hardware, Table 4.5, to add a tape drive and hard disk to an existing console. With one of these kits a dual tube can be split into two singles or with two of these kits a triple tube can be split into three singles. Table 4.5. Parts List F/N --0017 Qty. --0018 Qty. 4 1 1 4 5 1 1 5 --0019 Qty. --0020 Qty. Part Number Description 10P56909902 Cable Assy. Multitude Mem. Pwr.
PAGE 92
RN: 4-8 Minimum firmware requirements: Boot ROM 68040=V10.10 (MTCC) OR V11.10 (SMS) is the minimum software requirements: P1 R3.2 CAUTION Prior to working inside an electronics cabinet, be sure you are wearing a static grounding strap (1984--2718--0001). Insure that the strap is properly grounded to the chassis. Upgrade Use the following instructions to upgrade the --0017 and --0018 control consoles: 1 Power down the cabinet.
PAGE 93
RN: 4-9 Upgrade Instructions for Disk Only Consoles —0019, —0020 Description: The upgrade kit (1984--3045--0019 or 1984--3045--0020) includes the necessary hardware, Table 4.5, to add a hard disk to an existing console. With one of these kits a dual tube can be split into two singles or with two of these kits a triple tube can be split into three singles. Minimum firmware requirements: BOOT ROM 68040=V10.10 (MTCC) OR V11.10 (SMS). Minimum software requirements: P1 R3.
PAGE 94
RN: 4-10 0I SCSI host adaptor (1984--1140--000x) 1 Install 4 SCSI terminator resistors (F/N 19) in the 4 socket locations as shown. A mark (DOT, BAR) at one end of the resistor network indicates Pin1. See Figure 4.7 for details. 2 This board is now 1984--1140--0003. Change the part number label to 1984--1140--0003. Table 4.6. Connector Table 1 SCSI Signal (10P57159902)(Hard Disk and Tape Drive) Connector Ref. Destination Ref. Term Ref.
PAGE 95
RN: 4-11 GND P980 18 Front P982 6 7 8 4 PLCS Top P134 Back Figure 4.5. Tape Drive Mounting in Can 18 2 PLCS Front P138 AND P983 Top 6 14 8 8 PLCS Figure 4.6. Hard Disk Mounting in Can RS3: Software Release Notes for P1 R4.2 P1 R4.
PAGE 96
RN: 4-12 RN5 RN6 1 R12 74F240 R11 75452 1 ID 74F240 13 1 HD1 HD2 HD3 HD4 HD5 HD6 HD7 HD8 74F240 11 1 75452 10 RN3 RN4 75452 9 SCSI TERMINATION RESISTORS (DISK ONLY) C1 A C PIN 1 Figure 4.7. SCSI Termination Resistors 68020 to 68040 Console Upgrade Kit (1984--2380--0005) Description: OI Processor 68040 (10P55270010) performs 68020 or 68000 OI processor functions but has more memory and is enhanced for increased performance.
PAGE 97
RN: 4-13 Monitor Upgrades The following monitor changes have been implemented. SV — MTCC/SMS CRTs The color CRT monitor that can be used with the Multitube Command Console or System Manager is the 21-inch ViewSonic P220F. The unit operates on either 115 or 220 VAC nominal, 50 or 60 Hz. It is compatible with both consoles, and has common cable connections. Setup and controls are described in the manual which accompanies the unit.
PAGE 98
RN: 4-14 I/O BLOCK CONFIGURATION Address =2AA401 Device Type AIB Block Tag⇒ Block Type Redundancy Scheme Cage Line Backup Health A2 A3 ⇒ YES GOOD A4 A5 A6 A7 A8 FREE FREE FREE FREE ⇒ NO GOOD Xfer Health Backup Status Mode → AUTO Auto Lock ⇒ no ⇒RIOB >3/1 A1 ⇒ YES 18-Jan-92 11:58:59 GOOD READY READY FREE R-4 Reset Backup of Line 2 (press enter) Force Backup on Number Alarm Priority ⇒0 >0 (none) Plant Unit ⇒0 FIC Type AIO Rev 2.1 HW Alarm Code 0 CONFIG 1 Figure 4.8.
PAGE 99
RN: 5-1 Section 5: Version P1 R3.4 Changes to RS3 Manuals This section describes changes to the following Version P1 manuals. These changes occurred after the last printing of these manuals, so they supplement or correct the Version P1 set.
PAGE 100
RN: 5-2 Alarm Messages Manual Changes Changes to the Alarm Messages Manual (AL) are a result of: D Additional information on alarm generation D New disk-only console released with P1 R1.1 The following information describes the changes to this manual. AL: Section 1 (Reading Alarm and Event Messages) Description: The following subsection was added after “Alarm Banner” on page 1-2.
PAGE 101
RN: 5-3 CB DISCRETE DIAGRAM 08-Oct-98 12:14:31 Tag Agitator 155 Descriptor Block_Descriptor Addr -1A-01 Function DISC Discrete Block Plnt>0 Free Space: Stat = 91 % Dyn = 88 % Priority>0 +------------------CONDITIONS---------------------+Step>a >Level 1 |@c * | Off OFF | * a= > |Mode>Auto | * |MsgPr >Level 2/c |@e * Set >@c & @e |>*14 Off OFF | * |Off | *Clear>@b | >Tank 4 |@b * |> FORWARD on off |---*------------------ACTIONS--------------------| | * |Event >Tank 25 |B * Rise> |Type>244 .
PAGE 102
RN: 5-4 Description: Table 2.5 on page 2-5 was changed to read as follows. Table 2.5. Output Device Status Message Descriptions Code Field Device Malfunction Description 1000 0000 Field device malfunction; Cleared by field device self-test. Configuration has been changed by the user. Cleared by user command and RESET.
PAGE 103
RN: 5-5 Alarm 419 will occur normally on all disk-only consoles. 419 No Tape or Floppy Disk Drive Found Occurs when the RS3 cannot detect the presence of a tape or floppy drive. You should check your cable connections. This error may also occur when a disk-only (040) console is the only storage media present. In this case, the error is merely a verification of that hardware. S Disk 775 Start Memory Dump cont: A manually initiated memory dump of Controller Processor has been started.
PAGE 104
RN: 5-6 CC-2: Section 1, Figures 2.1.5, 2.1.6, and 2.1.7 Description: Replace Console Configuration screen examples. The Console Configuration screens have added fields for the automatic backup function, and other fields have shifted as a result. The screens in their current form are shown following. NOTE: Not all occurrences of the Console Configuration screen displays are shown in these Release Notes; however, the same changes apply to all instances of these displays.
PAGE 105
RN: 5-7 - To call up: D Type CCC [ENTER] at the command line. D [PAGE AHEAD] from Command Console Menu. - To access other screens: D [PAGE AHEAD] to see Page 2 of the Console Configuration screen. D [PAGE BACK] to see Menu Command Console Screen. CONSOLE CONFIGURATION 03-Nov-97 12:07:37 This is Node 32 MTCC Date ⇒03-Nov-97 Time ⇒12:08:36 Prgm Revision P1.09 PX ENG 68040 MTCC Boot Revision 10.
PAGE 106
RN: 5-8 - To access other screens: D [PAGE AHEAD] to see Page 3 of the Console Configuration Screen. D [PAGE BACK] to see Page 1 of the Console Configuration Screen. CONSOLE CONFIGURATION Keyboard Nodes>0 >0 >0 Keyboard Revisions KBI 1.4 TB 1.
PAGE 107
RN: 5-9 Controls automatic console configuration backup. D Console Config: field toggles between Enable and Disable. D Destination File field must be configured by the user before the automatic console configuration operation can be enabled. D Event Type field requires selection of an event number from 0 to 240, to trigger the automatic console configuration backup. Console Config See page 2--1--28 for more information on automatic console configuration backup.
PAGE 108
RN: 5-10 CC-2: Section 1, starting on page 2--1--28 Description: Add text supporting the automatic backup functions, as shown below. Automatic Backup Functions You can elect to have RS3 automatically backup your console configuration and/or your plant configuration through the Console Configuration screen display or command line options.
PAGE 109
RN: 5-11 You can backup groups of nodes within various PeerWays in the system into destination files with a specific destination filename, all within one save operation. You can also maintain multiple revisions of a particular plant configuration. Automatic plant configuration backup triggers the Disk Cont Save or Backup operation (Disk Activity screen).
PAGE 110
RN: 5-12 Customizing the Plant Configuration Backup You can customize the backup of plant configurations using the BackUp Plant Config (BUP) command line option, which displays the Backup Plant Config screen. Within the Backup Plant Config screen, you can: D Select/deselect particular nodes to be backed up (from 1 to 992) D Specify the first five characters for the destination file(s) D Enter a maximum revision letter (from A to Z) D Write the backup plant configuration file to disk.
PAGE 111
RN: 5-13 D Graphic files in the Process Graphics folder D Report configuration files in the Report Configuration folder D Group Display configurations in Console Configuration files D Trend configurations in Console Configuration files D Trend Display configurations in Console Configuration files NOTE: D D D When blocks are copied using the Plant Configuration “Disk Load Transfer”, remember to change any duplicate tags.
PAGE 112
RN: 5-14 Modified using ”Batch Load Transfer” function on the Disk Activity screen. D RBL Files Modified using the search and replace function within each individual RBL script. (Set the “Tags or Addresses” field on the Configure Command Console screen to “Addresses”.) RBL files may also be modified using the PC-based Batch Studio application. Calling Up the Link Editor Screen - To call up the Link Editor screen (Figure 2.7.1), type: L E or L E (node) [:] (drive) RS3: Software Release Notes for P1 R4.
PAGE 113
RN: 5-15 Address Range. Current address range of links to be edited or listed. You can specify a range by PeerWay node and controller processor card numbers. New Address. New address range of links after editing. You can specify a range by PeerWay node and controller processor card numbers. At Node. You cannot change to a different node using this screen. File Name. Name of the file used to modify block link references.
PAGE 114
RN: 5-16 Procedure: Editing Link Addresses - To edit link addresses: Step Operation 1 Action: Call up the Link Editor screen. Type: L E 2 Action: Select the operation in the “Operation” field. Scroll through the available operations with the [NEXT OPTION] key.
PAGE 115
RN: 5-17 - To edit link addresses: Step Operation 8 Action: Description Cursor to the “Press ” field and press [ENTER] to execute the mode specified in the “Edit Mode” field. Comments: The operation is complete when the following message appears: File is updated with new Address If you have performed a Modify operation, the “Unmodified Addresses” box shows only the addresses that were not modified. The modified addresss will appear on the list again after you do a List operation.
PAGE 116
RN: 5-18 Select trend log as the object type. REPORT CONFIGURATION 28-Aug-98 14:18:04 ****************** START OF REPORT ****************** Type :⇒trend log File Name:⇒trf1 Color :⇒1n white Node :⇒28 Row :⇒38 Scaled :⇒100 Tag ⇒TREND 2/PV Accum :⇒none Time :⇒10:50:00 Duration :⇒10 mins Col :⇒15 CREATE DELETE Inter :⇒5 secs Detail :⇒y Time : Data : Mean :⇒y Total :⇒y Minimum:⇒y Maximum ⇒y MM Time:⇒y ⇒y ⇒y ⇒y ⇒y ⇒y ⇒y CONFIG 1 CREATE must be used to create or to modify a trend log object.
PAGE 117
RN: 5-19 Description: The following sentence was added at the end of the first paragraph under the heading “How to Generate a Report Based on Time and Date” and Figure 4.4.27 was modified to include an additional step on setting the “Active ?” field on page 4-4-38. Reports configured to print based on time must have the “Active ?” field in the Report Configuration screen set to “yes.
PAGE 118
RN: 5-20 CC: Chapter 6 (Alarm Management) Section 3 (Separating and sorting Alarms at a Console) Description: The field “Flush Block Cache” was added to Figure 6.3.2 and to Table 6.3.3 (pages 6-3-9 and 6-3-10). - - To call up: D A L C [ENTER] at the command line To access other screens: D [PAGE AHEAD] to see Event List Configuration D - [PAGE BACK] to see Automatic Alarm Deletion To change an entry: 1. Cursor to the field, type in the new entry, and press [ENTER].
PAGE 119
RN: 5-21 Table 6.3.3. Alarm List Configuration Screen Fields Description Field Clears the block cache, to ensure information stored in console’s cache is up to date. Useful on larger systems after configuration changes. Flush Block Cache CC: Chapter 8 (Commands) CC-8: Section 2 Description: Update this chapter to include the new command line entries for the automatic backup functions, as shown below. Table 8.2.
PAGE 120
RN: 5-22 Operation Performed Entry Command Line Text Disable plant config backup DPB [ENTER] Disable Plant Cfg Backup Enable plant config backup EPB [ENTER] Enable Plant Cfg Backup CC-8: Section 3 Table 8.3.1 (MTCC Commands that Call Up Screens) Entry Screen Called Up Command Line Text Plant Configuration Backup Backup Plant Config BUP [ENTER] BackUp Plant Config Table 8.3.
PAGE 121
RN: 5-23 Configuration Quick Reference Guide Changes Changes to the Configuration Quick Reference Guide (CQ) reflect the changes documented in the Console Configuration manual that are a result of: D Addition of automatic backup capability released with P1 R1.2 D Release of the MPC5 Controller Processor released with P1 R3.0 The following information describes the changes to this manual.
PAGE 122
RN: 5-24 This section contains tables listing commands that can be entered from the command line at the top of the System Manager Station (SMS) screen. You can access these commands by typing the indicated letters, or by repeatedly pressing [NEXT OPTION] and [PREV OPTION]. The first two tables list SMS commands that call up screens; the commands are organized by primary function in the first table, and alphabetically by command in the second table.
PAGE 123
RN: 5-25 ControlBlock Configuration Manual Changes Changes to the ControlBlock Configuration Manual (CB) are a result of: D Introduction of the MPC5 Controller Processor with the P1 R3.0 release D Allowable entries for the Prop Band field D The values for the TOT function input and output registers The following information describes the changes to this manual. CB: Chapter 1 (Introduction to ControlBlocks) CB-1: Section 1 (what is a ControlBlock?) Description: The first bulleted item and Figure 1.1.
PAGE 124
RN: 5-26 Table 2.2.5. P, I, and D Configuration Fields on Continuous Faceplate Screen Field Prop Band (or Cont Gain) Access Level Description Allowable Entries Supr Proportional Band or Controller Gain. The field that appears depends on the “PID Proportional” field on the Console Configuration screen. (See CC: 1.) (Prop Band of 100) = (Controller Gain of 1) Appears when you configure proportional control or a combination that includes proportional control. PV, LS, RS, FF, E to O, .
PAGE 125
RN: 5-27 Description: The first paragraph on page 3-4-3 was modified to include the MPC5 Controller Processor. Forty links are available for each MPC Controller Processor. Eighty links are available into and out of each MPCII or MPC5 Controller Processor. The ControlFile Status screen displays the number of remaining links for Controller Processors. For information about the ControlFile Status screen, see “Viewing the Number of ControlFile Links Available” later in this section. Description: Table 3.4.
PAGE 126
RN: 5-28 CB: Chapter 9 (Data Compression) CB-9: Section 3 (Configuring Compressors in a Data Compression Block) Description: The following note was added after the paragraph on page 9-3-1. NOTE: Do not perform engineering units (EU) conversion for Data Compression block (DCB) inputs on the Continuous Links screen. Instead, set EU conversion on the register that the DCB input is linked to. The DCB will then operate with a scaled value, and that value in the source block will also be scaled.
PAGE 127
RN: 5-29 Table 1.1.1. Media Capacity Media Type Unformatted Initialized Total Files Hard Disk 2.1 GB 970 MB N/A Description: One sentence was added to the paragraph under “Tapes” on page 1-1-4. The following two sections describe precautions for handling and storing tape media. The third section describes how to locate tape drives. Description: The following subject was added before “How Are Media Organized?” on page 1-1-5. Tape Drive Locations Figure 1.1.0 through Figure 1.1.
PAGE 128
RN: 5-30 SYSTEM CABINET SIDE VIEW FRONT VIEW DOOR HANDLE Figure 1.1.0. Tape Drive Location Label on the System Cabinet Figure 1.1.0A shows the label on the operator console and System Manager Station (SMS) enclosure. The door on which the tape symbol is located indicates which door provides access to the tape drive. RS3: Software Release Notes for P1 R4.
PAGE 129
RN: 5-31 OPERATOR CONSOLE WITH 7U HANGING ENCLOSURE (SERIES II FURNITURE) SMS ENCLOSURE Figure 1.1.0A. Tape Drive Location Labels on the Operator Console and SMS Enclosure Figure 1.1.0B shows the label on the Electronic Console (EC) and tower. The door on which the tape symbol is located indicates which door provides access to the tape drive. ELECTRONIC CONSOLE (EC) (SERIES I FURNITURE) TOWER Figure 1.1.0B.
PAGE 130
RN: 5-32 DT-1: Section 1, Table 1.1.2 (Console Hard Drive Compatibility Matrix) Description: The Tandberg Tape Drive was added to Table 1.1.6. Also, the capacity of the tape drives and the notes were changed. Table 1.1.6. Tape Drives and Recommended Cartridges FRSI Part Number for Cartridge MTCC or SMS CCC Screen Displays 1984--1954--0001 RS3*T1 45S Scorpion 1984--1954--0001 RS3*T2 60S 1984--1954--0002 Tape Drive Cartridge Type Format Capacity DC300XLP qic-24 33.
PAGE 131
RN: 5-33 DT-1: Section 2 (Directory Screens) Description: Information on the MPC5 was added to the last two paragraphs under the heading “Operating Program Files” on page 1-2-18. The Plant Program folder also contains operating programs for the different functions that can be performed by the Controller Processors. (MPCI, MPCII, and MPC5). Table 1.2.2 lists the basic operating program files for use with the CP-II and CP-IV Coordinator Processors. Table 1.2.
PAGE 132
RN: 5-34 The memory in the Controller is volatile, so if the Controller is disabled, the configuration is gone from the Controller, but not from the NV Memory. The NV Memory utilizes non-volatile battery backup memory. All plant configurations from the Controllers are retained even if the board is removed from the ControlFile. Loss of setpoint data can only occur under a specific set of circumstances.
PAGE 133
RN: 5-35 DT: Chapter 2 (Procedures) DT-2: Section 4 (Saving) Description: The Console Configuration screen in Figure 2.1.5 was changed to include the ‘Host’ field for ABC Batch Messaging (page 2-1-12). CONSOLE CONFIGURATION This is Node 32 MTCC Prgm Revision P1.02 PX ENG 68040 MTCC Boot Revision 11.
PAGE 134
RN: 5-36 ControlFile $$AFIC Disk Load Program or Script Plant Program FIC FIC Figure 2.3.2A. Loading the $$AFIC Plant Program File To load a FIC/FIM program image to an FIC/FIM, the console you are at must own the ControlFile node on which the FICs or FIMs are located. - To call up the Plant Status screen to check node ownership, type: PS [ENTER] Owned nodes are backlighted. For information about changing the node ownership, see CC: 2. For more information on FIC/FIM addressing, see OV: 4.
PAGE 135
RN: 5-37 Procedure 2.3.4. Disk Load Program or Script to FIC/FIM Step 1 Operation Description CAUTION The Disk Load Program operation may affect the plant control Action: scheme. Call up the Disk Directory PeerWay screen by typing: Response: 2 Action: DDP [ENTER] The Disk Directory PeerWay screen appears. Cursor to the disk volume name or location containing the FIC/FIM program, and press [SELECT ]. Response: The Disk Directory screen appears.
PAGE 136
RN: 5-38 Procedure 2.3.4.
PAGE 137
RN: 5-39 DT-2: Page 2-4-7, Figure 2.4.2 (Disk Activity Screen: Disk Controller Save or Backup) Description: The name of this screen has been changed to “Disk Controller Save or Backup.” In addition, the following lines on this screen have been modified: D Address Range D Operation D Will SAVE … Replace the existing figure with the modified figure as shown following.
PAGE 138
RN: 5-40 Step Operation 5 Description CAUTION The Disk Controller Save or Backup operation may overwrite existing blocks in the file. Action: Cursor to the Operation field on the Disk Activity screen. Press the [NEXT OPTION] key repeatedly until the following message appears above the Operation field: Disk Cont Save or Backup Response: 7 Press [ENTER].
PAGE 139
RN: 5-41 Saving a Plant Configuration Automatically You can enable an automatic save/backup of the plant configuration from the Console Configuration screen (see CC: Chapter 2, Section 1 for more information) or from the command line option EPB (Enable Plant Backup). Automatic plant configuration backup can be customized using the BackUp Plant Config screen, shown in Figure 2.4.3. This screen is called up by the BUP (Backup Plant Config) command line option.
PAGE 140
RN: 5-42 BackUp Plant Config ⇒Write 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 > 11 > 12 > 13 > 14 > 15 > 16 > Backup Name: DISKNAME, $$BACKUP Backup File to Disk 17 > 33 > 49 > 65 > 81 > 97 18 > 34 > 50 > 66 > 82 > 98 19 > 35 > 51 > 67 > 83 > 99 20 > 36 > 52 > 68 > 84 > 100 21 > 37 > 53 > 69 > 85 > 101 22 > 38 > 54 > 70 > 86 > 102 23 > 39 > 55 > 71 > 87 > 103 24 > 40 > 56 > 72 > 88 > 104 25 > 41 > 57 > 73 > 89 > 105 26 > 42 > 58 > 74 > 90 > 106 27 > 43 > 59 > 75 > 91 > 107 28 > 44 > 60 > 76 > 92 > 108 29 > 45
PAGE 141
RN: 5-43 Backup Plant Configuration Procedure Step 1 Operation Action: Action: Response: 3 Action: Response: 4 Call up the Backup Plant Config screen by typing: BUP [ENTER] Response: 2 Description Action: The Backup Plant Config screen appears. Cursor to the Destination File field; enter the first 5 characters for the destination file(s) and press [ENTER]. Note that this will overwrite an existing file that has the same name. The initial destination filename will be displayed.
PAGE 142
RN: 5-44 DT-2: Section 7 (Restoring) Description: Add the following new screen, Master License Agreement, after Figure 2.7.1: DISK ACTIVITY Source Disk v19beta At Node 134 On Drive 2 15-APR-97 10:59:49 Destination Disk DEMO-1 At Node 134 On Drive 1 License Information: In order to use the RS3 software, you must first confirm the existence of a license agreement.
PAGE 143
RN: 5-45 Description: Add statement about the Master License Agreement to step 7, as follows: 7 Action: Response: Comments: Cursor to the “Press to Begin” field, and press [ENTER]. The Master License Agreement is displayed. Select to continue the restore operation. While the operation is in progress this field reads: Tape Operation in Progress The operation is complete when the “Press to Begin” field reappears. The operation takes several minutes to complete.
PAGE 144
RN: 5-46 DT-2: Procedure 2.7.2, Disk File Restore from Tape Description: Add statement about the Master License Agreement to Step 8, as follows: 8 Action: Response: Comments: Cursor to the “Press to Begin” field, and press [ENTER]. The Master License Agreement is displayed. Select to continue the restore operation. While the operation is in progress, this field reads: Disk Operation in Progress The operation is complete when the “Press to Begin” field reappears.
PAGE 145
RN: 5-47 Tables 4.1.1. Device Error Messages for the Hard Disk Message Meaning Action Check the SCSI board and cable; replace the hard drive unit if necessary. Hardware Error A non-recoverable hardware failure in the hard drive has been detected. Medium Error The hard disk probably has bad magnetic medium. Replace the hard drive unit. Drive Not Ready The hard drive cannot be accessed at the present time; the hard drive may be doing a recalibration. Try the disk activity later. Table 4.1.2.
PAGE 146
RN: 5-48 I/O Block Configuration Manual Changes Changes to the I/O Block Configuration Manual (IO) are a result of additional information concerning: D D Additional information on configuring a Pulse Input/Output Block (PIOB) Additional information on configuring redundant input/output blocks D HART errors returned in the Stat field D Stat field errors with SIB and HOB blocks D PLC scaling D MPC5 Controller Processor released with P1 R3.
PAGE 147
RN: 5-49 Point Type ⇒Pulse Input Type ⇒Contact or Voltage Function Type ⇒Counter Field signals Pulses ControlBlock Target Count Continuous Q Discrete PIOB Count xxxx01 or xxxx02 Target Output— No. of pulses Actual count= ControlBlock Continuous Q Discrete Target count m Reset Target n Reset Counter With a ControlBlock linked to the PIOB, the ControlBlock provides the target value. Anytime that logic step m rises (turns on), the ControlBlock output value becomes the PIOB target value.
PAGE 148
RN: 5-50 Description: The Source HF field was added to Table 3.2.13 on page 3-2-35. Table 3.2.13. PIOB Fields for a Loader Application with a Binary Output Description Field Allowable Entries Selects the hold forward flag option for the source. “Yes” = The hold forward flag from the source is taken into account. Source HF “No” = The hold forward flag from the source is ignored.
PAGE 149
RN: 5-51 I/O BLOCK CONFIGURATION Address =2AA401 Device Type AIB Block Tag⇒ Block Type Redundancy Scheme Cage Line Backup Health A2 A3 ⇒ YES GOOD A4 A5 A6 A7 A8 FREE FREE FREE FREE ⇒ NO GOOD Xfer Health Backup Status Mode → AUTO Auto Lock ⇒ no ⇒RIOB >3/1 A1 ⇒ YES 18-Jan-92 11:58:59 GOOD READY READY FREE R-4 Reset Backup of Line 2 (press enter) Force Backup on Number Alarm Priority ⇒0 >0 (none) Plant Unit ⇒0 FIC Type AIO Rev 2.1 HW Alarm Code 0 CONFIG 1 Figure 5.1.3.
PAGE 150
RN: 5-52 Table 8.1.1. Example of Digital PV Update Rates Activity Digital PV Update Rate from Each Device No AMS activity Every 15 seconds AMS PV scan (periodic) Every 20 seconds AMS reading device configuration parameters Every 30 seconds Digital PV is not recommended for process control because sampling is slow and sampling time is variable. Description: Add the following note to the description of the “Stat” field in Tables 8.1.3 (page 8-1-26) and 8.1.11 (page 8-1-48).
PAGE 151
RN: 5-53 MPC II/MPC5 SIB A SP B PID Q PROCESS Smart Field Interface Card (FIC) Control Block PV XMTR HOB Digital Valve Controller MTCC Console Graphics VIB VIB MPC II/MPC5 SIB Control Block PV A SP B MTCC Console Graphics PID Q MAI/ MAI32 FIM XMTR PROCESS HOB MAO FIM Digital Valve Controller VIB VIB Figure 8.2.2. How an HOB Functions with a Smart FIC or Multipoint Hardware in a Control Loop Description: The following subject was added to the bottom of page 8-2-20.
PAGE 152
RN: 5-54 IO: Chapter 9 (Configuring PLC Blocks) IO-9: Section 1 (What is a PLC Interface?) Description: Changes to the second sentence to include the part number for the MPC5 MultiPurpose Controller card under this topic (page 9--1--2). PLC Interface Hardware The Controller Processor can be a PLC Processor card (1984-1494-000x) or a MultiPurpose Controller card (10P57520007, 1984-2500-000x or 1984-4068-0006).
PAGE 153
RN: 5-55 =16 A 45 PeerWay Node Number (Must begin with = sign) (Leading zeros can be omitted) 1--992 PLC Block # MPC I: 1--200 MPC II: 1--256 MPC5: 1--512 Controller Processor Card Slot (ControlFile) A -- H Figure 9.2.1 PLC Addressing Scheme Description: The fifth bulleted item under “Module Switch Requirements” was modified to include the baud rate for the MPC5 (page 9-2-8). D Recommended baud rate of 9600 (19200 for the MPC5) Description: Corrected decimal value in third row of Table 9.2.
PAGE 154
RN: 5-56 IO-9: Section 3 (Configuring a PLC) Description: Add the following paragraph under this topic (page 9-3-1). PLC Block Applications In addition, you can configure scaling on a PLCB on the four PLCBs that allow scaling. The four PLCBs that allow scaling are S INT Scale, U INT Scale, BCD3 Scale, and BCD4 Scale. You can also configure alarms based on individual coil values in a Flags data type.
PAGE 155
RN: 5-57 Figure 9.3.3B is an example of a controlled PLC flag read and write. The 16 PLC coils starting at address 33 will be written to and read from the PLC during controller scans when the =1G--01/C register is at 100% of scale. The data written to the PLC will be the user flags of register =1G--01/C.u.a to =1G--01/C.u.p. The data read will be available to any block link to this PLCB block.
PAGE 156
RN: 5-58 I/O BLOCK CONFIGURATION Device Type PLCB Address =1G004 Block Tag ⇒ Block Type ⇒PLCB Source ⇒ PLCMux/D Addr 1G-01/D Data Type ⇒S int Value From Source 0. Write ⇒no Sample Time ⇒1 S Sim Tag⇒ Addr Value From PLC 0. ponmlkjihgfedcba 0000x Hardware Alarm Code 0 Read →filter Plant Unit ⇒0 06-Aug-98 09:40:30 Mode → AUTO Auto Lock ⇒no PLC write Mask ⇒FFFFx Value to PLC 0000x Port⇒ A PLC number ⇒1 PLC Word Address ⇒040004 Alarm Priority ⇒0 Figure 9.3.3C.
PAGE 157
RN: 5-59 I/O BLOCK CONFIGURATION Device Type PLCB Address =1G006 Block Tag ⇒ Block Type ⇒PLCB Source ⇒ PLCMux/F Addr 1G-01/F Data Type ⇒S int Value From Source 0. Write ⇒filter Sample Time ⇒1 S Sim Tag⇒ Addr Value From PLC 0. ponmlkjihgfedcba 0000x Hardware Alarm Code 0 Read →filter Plant Unit ⇒0 06-Aug-98 09:40:30 Mode → AUTO Auto Lock ⇒no PLC write Mask ⇒FFFFx Value to PLC 0000x Port⇒ A PLC number ⇒1 PLC Word Address ⇒040006 Alarm Priority ⇒0 Figure 9.3.3D.
PAGE 158
RN: 5-60 Table 9.3.9. PLCB I/O Block Configuration Fields (continued) Field Data Type Access Level CONF Description Type of word that is being read from or written to the PLC. Allowable Entries(1) Flags, BCD3, BCD4, S Int, U Int, S Int Scale, U Int Scale, BCD3 Scale, BCD4 Scale, Float(2) For more information, see Table 9.3.12 Block Out The value displayed is the block output scaled according to the engineering scaling values.
PAGE 159
RN: 5-61 NOTE: Make sure to verify the scaling of the values in the PLC registers, and match them to your scaling in the PLCB. Otherwise, erroneous values will result. Address =2B008 I/O BLOCK CONFIGURATION Device Type PLCB Block Tag ⇒ Block Type ⇒PLCB Source ⇒DMC-6 Addr =2B-010 4-Aug-98 Mode Auto Lock 10:57:34 ⇒AUTO ⇒No Data Type ⇒ S Int Scale Value From Source Write ⇒filter Block Out .00 Value From PLC 0200x .
PAGE 160
RN: 5-62 Standard engineering scaling is also available. The default values are 0 and 100. Alarms are configured with this scaling just as in the AIB block. The default alarm value is “none” and the default dead band is 1.00. If the scaling is changed, the alarm and dead band numbers automatically change to match the new scaling. Engineering Units and the Descriptor also work as with the AIB block. Description: Additional information was added after Figure 9.3.11 under this topic (page 9-3-23).
PAGE 161
RN: 5-63 I/O BLOCK CONFIGURATION Device Type PLCB Address =1G005 Block Tag ⇒ Block Type ⇒PLCB Source ⇒ PLCMux/E Addr 1G-01/E Data Type ⇒S int Value From Source 0. Write ⇒filter Sample Time ⇒1 S Sim Tag⇒ Addr Read →no Hardware Alarm Code 0 Plant Unit ⇒ 0 06-Aug-98 09:40:30 Mode →AUTO Auto Lock ⇒no PLC write Mask ⇒FFFFx Value to PLC 0000x Port ⇒ A PLC number ⇒1 PLC Word Address ⇒040005 Alarm Priority ⇒ 0 Figure 9.3.11B. Controlled PLC Register Write Description: Changes to Table 9.3.
PAGE 162
RN: 5-64 Address =02B008 I/O BLOCK CONFIGURATION Device Type PLCB 7-Jul-92 13:15:30 Block Tag ⇒ Block Type ⇒PLCB Source ⇒ DMC-6 Addr =2B-010 Mode → AUTO Auto Lock ⇒no Data Type ⇒ BCD4 PLC Write Mask ⇒ FFFFx Sample Time ⇒1 S Value To PLC Tag ⇒ Addr Port⇒ A Value From Source Write ⇒ no 0200x Read → no Hardware Alarm Code 0 Plant Unit ⇒233 0200x PLC number ⇒ 7 PLC Word Address ⇒ 1000 Alarm Priority ⇒ 0 Figure 9.3.
PAGE 163
RN: 5-65 Description: Changes were made to Figure 9.3.13 under this topic (page 9-3-27).
PAGE 164
RN: 5-66 Description: The following note was added under the first bullet under this topic (page 9-5-9). Jumpers on Controller Board NOTE: MPC5’s do not have jumpers HD21 through HD24. Description: A change was made to the second paragraph with a bullet under this topic (page 9-5-9) and the reference to the Service Manual was corrected.
PAGE 165
RN: 5-67 Operator’s Guide Changes OP: Chapter 6 (Alarms) Description: The instruction “To enable or disable alarm areas:” in the illustration on page 6-16 was changed from “Press [Select]” to “Press [OPTION] [ENTER}.” - To call up Active System Status screen, type: ANC [ENTER] - To enable or disable alarm areas: D Press [OPTION] [ENTER]. The area name annunciates alarm conditions. Number of alarms in area. Plant unit in area with highest priority alarm.
PAGE 166
RN: 5-68 OP: Appendix A (Responding to System Faults) Description: The following note was added after step 1 on page A-2. NOTE: The Disk shutdown (DS) command should always be performed before powering down the console. This will purge the cache and prevent possible loss of data. PeerWay Interfaces Changes Changes to the PeerWay Interfaces (PW) are a result of additional information concerning: D D Introduction of the MPC5 Controller Processor with the P1 R3.
PAGE 167
RN: 5-69 Figure 1.3.61. ControlFile Status Reply Message----Message Type 73 Field Format 2 d Definition Card Type “Card Type” field value. 99=None 06=SMART 01=MLC 07=RBLC 02=CC 08=MPC 03=SSC 09=ATMLC 04=MUX 10=MPTUN 05=PLC 11=MPCAS 12=MPCAP 13=MPCAT 14=MPC2 15=MPC5 PW-1: Section 4 (Field Codes) Description: Changes to Table 1.4.5 on page 1-4-10 show a change in the field used with code 0200. Table 1.4.5.
PAGE 168
RN: 5-70 M C Peerway Interface (1984--1045--000x) Power Regulator (1984--1137--000x) Bubble Memory (1984--1167--000x ) Nonvolatile Memory (1984--1547--000x) Operator Interface Processor (1984--2759--0008) Card Cage (10P52820001) Power Switch Cooling Fan Assembly (1984--3282--0001) Shelf Assembly Figure 3.1.2. Single HIA (Front View) The internal/external clock jumpers on the Nonvolatile Memory Card (1984--1167--000x or 1984--1547--000x) determine the source of the HIA clock synchronization.
PAGE 169
RN: 5-71 NOTE: If the primary FIM fails and the secondary FIM takes over but then fails, the redundant FIM should be replaced first. If this is not done but redundant controllers are configured, it may take 5--30 seconds to regain normal operation via a redundant controller switch. If redundant controllers are not available, replacing both FIMs or moving one FIM to the redundant slot will restore normal operation. If necessary, rebooting the controller will also restore normal operation.
PAGE 170
RN: 5-72 Description: The definitions of “kill” on page G-16 were modified to read as follows. 1) To delete the controller configuration. kill 2) To stop and end a batch task or recipe. Service Manual, Volume 1 Changes Changes to the Service Manual (SV), Volume 1 are a result of additional information concerning: D The SCSI card boot ROM D Using the Coordinator Processor enable/disable switch D The MPC5 I/O communication baud rate The following information describes the changes to this manual.
PAGE 171
RN: 5-73 The Pixel Graphics Video Generator (10P58900001 or 1984--2503--0001) generates color video signals for the command console CRT. SV: Chapter 4 (ControlFiles) SV-4: Section 2 (ControlFile Support Section) Description: The following note was added to the bottom of page 4-2-29 under the heading “CP LEDs, Test Points, and Enable/Disable Switch”. NOTE: If the CP switch is disabled and then quickly enabled, the CP may refuse to boot up. Wait for the red LED to come on before throwing the switch again.
PAGE 172
RN: 5-74 Service Manual, Volume 2 Changes Changes to the Service Manual (SV), Volume 2 are a result of additional information concerning: D FIC redundancy D FIM redundancy D Loop power D MAIO16 Termination Panel D Introduction of a new MAI32 FIM with the P1 R3.4 release D D Changing a detail screen name from “FIC Detail” to “Field I/O Detail” Analog FIM bits The following information describes the changes to this manual.
PAGE 173
RN: 5-75 SV: Chapter 6 (Multipoint I/O) SV-6: Section 1 (Multipoint I/O Installation and System Wiring) Description: The following note was added after the second paragraph on page 6-1-1 to clarify information on FIM replacement. NOTE: If the primary FIM fails and the secondary FIM takes over but then fails, the redundant FIM should be replaced first. If this is not done but redundant controllers are configured, it may take 5--30 seconds to regain normal operation via a redundant controller switch.
PAGE 174
9 8 RS3: Software Release Notes for P1 R4.
PAGE 175
RN: 5-77 Description: Table 6.4.7 on page 6-4-35 was modified for the new MAI32 FIM . Table 6.4.7.
PAGE 176
RN: 5-78 There are two types of 16-point output FIMs: D D MAIO16 Field Interface Module (FIM) CE Approved: 4--20 mA Output 16 Point 10P54080004 or 10P58080005 MAIO Field Interface Module (FIM): 4--20 mA Output 1984--4418--0001 There is one 32-point input FIM: D MAI32 Field Interface Module (FIM) CE Approved: 4--20 mA Input 32 Points 10P53190004 or 10P58300005 Table 6.4.10.
PAGE 177
RN: 5-79 One MAIO Termination Panel (1984--4383--0002) and an MAIO FIM can support up to16 points on 8 dual-channel barriers. Use an MAIO Input FIM (10P54040004 or 10P57700005) for inputs or an MAIO Output FIM (10P54080004 or 10P58080005) for outputs. Use Marshaling Panel Cable 1984--4298--xxxx. Description: The part number for the new MAO Output FIM was added to page 6-6-25.
PAGE 178
RN: 5-80 SV: Chapter 10 (Troubleshooting) SV-10: Section 3 (Troubleshooting Consoles) Description: The following note was added on page 10-3-15 NOTE: Once a memory snap has started, do not attempt any other action until it is complete. Otherwise, the node may crash. Description: Figure 10.3.3. on page 10-3-17 was updated to show the current fields being displayed in the Memory View screen.
PAGE 179
RN: 5-81 Description: Additional information was added to the Node field description and a Refresh Rate field was added to Table 10.3.3. on page 10-3-18 to reflect changes made to the Memory View screen. Table 10.3.3. Memory View Screen Field Description Description Field Specifies the node number of the source of the memory data for the primary CP or the Controller Processors in slots A--H. For example: Node When Node 136 is entered, the memory of the primary CP for Node 136 is read.
PAGE 180
RN: 5-82 Description: Information on Analog FIM Bits for bits 0, 1, and 2 was changed on page 10-5-15. Table 10.5.8. FIC/FIM Status Bits Status for: Analog FIM Bits: Status Bits Bit Description xxxx x1xx 2 MAI16 and MAO16: Loop Power Module status bits: 0 for Loop Power Module A. 1 for Loop Power Module B. MAI32: Not used. xxxx xx1x 1 Set to 0 when the Loop Power is good. Set to 1 when the Loop Power is bad. 0 MAI16 and MAO16: Set to 0 when the Loop Power Module is present.
PAGE 181
RN: 5-83 FIELD I/O DETAIL 16:01:49 Controller FIC Type DIO Tag/Address =33CA101 =33CA102 =33CA103 =33CA104 =33CA105 =33CA106 A1 =33C 23-Mar-99 F-Rev 1.0 S-Rev 2.0 Status ssssssss aaaaaaaa bbbbbbbb cccccccc dddddddd Type SIB SIB AOB DOB DOB DOB . . . Value 00 00 00 Mode MANUAL MANUAL AUTO AUTO AUTO AUTO Figure 10.5.2. Field I/O Detail Screen Table 10.5.9.
PAGE 182
RN: 5-84 Service Quick Reference Guide Changes Changes to the Service Quick Reference Guide (SQ) are a result of additional information concerning: D D Changing of the status and detail screen names from “FIC Status” to “Field I/O Status” and “FIC Detail” to “Field I/O Detail” Introduction of a new MAI32 FIM with the P1 R3.4 release The following information describes the changes to this manual.
PAGE 183
RN: 5-85 Field I/O Detail Screen Fields Field Description of Displayed Information Controller Address of the Controller Processor associated with the particular FICs. None is displayed if no Controller Processor has been assigned. Type Configured type of FIC: analog I/O (AIO), contact I/O (CIO), redundant analog I/O (AIO-R), redundant AIO with Smart daughter board (AIO-RS), discrete I/O (DIO). FIC Slot number of the FIC within the Controller Processor. F-Rev Revision level and firmware of the FIC.
PAGE 184
RN: 5-86 With the MPC5, the I/O communication baud rate is set by software instead of by a hardware jumper (as done by the MPC II and MPC). The baud rate is set automatically when either the PLC+ or MUX+ image is selected. SQ: Chapter 7 (Input/Output) Description: The part number for the new MAO16 was added to page 7-61. MAIO Output FIM MAO16 (EMC Approved) . . . . . . . . . . . . . . . . . . . . . . . 10P54080004 or 10P58080005 MAO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 185
RN: 5-87 Site Preparation and Installation Manual Changes Changes to the Site Preparation and Installation Manual (SP) are a result of additional information concerning: D Introduction of a new MAI32 FIM with the P1 R3.4 release D FIM replacement and redundancy D MAI32 termination panel jumpers D Power supply redundancy The following information describes the changes to this manual.
PAGE 186
RN: 5-88 Description: Information under the heading “Finding the Number of Power supplies Required” on page 1-2-12 was changed to read as follows. AC/DC Power Supplies To determine the number of AC/DC Power Supplies needed to power the DC bus: 1. Add the DC current requirements of all equipment that will be fed from the DC bus. 2. Add an allowance for equipment expansion. 3. Divide the total current by 18 amps to determine the number of power supplies required to supply the load.
PAGE 187
RN: 5-89 5. Divide the number of power supply modules, including any redundant modules, by two. Number of Power Number of Housings Needed = Supply Modules 2 6. Round up the resulting number to the next higher whole number to find the number of power supplies needed. The limit is four power supply modules on one bus; one additional module may be added for redundancy.
PAGE 188
RN: 5-90 A System Power Supply Unit has about four times the power density of AC/DC Power Supply assemblies. For example, if you needed a total of 2400 watts, two 1200-watt power supply modules would use about one-fourth the mounting space required by four 600-watt AC/DC Power Supplies. NOTE: Because of differing output voltages, AC/DC Power Supplies cannot be mixed on a DC Distribution Bus with System Power Supply Units.
PAGE 189
RN: 5-91 A DC Distribution Bus should have not less than two and no more than five power supply modules wired to it. This requires the use of 1--3 System Power Supply Units. There must always be one power supply module more than required to supply the load. The additional module is redundant and serves as a backup in case one of the other modules fails. This is referred to as N+1 redundancy.
PAGE 190
RN: 5-92 modules (with two or more located in the same or a separate housing) are connected to Bus A to supply the load. There must be power supplies connected to Bus B that are capable of supplying the same load and at the same voltage. When only one power supply is needed on each bus, the system must be wired for a single non-redundant bus. See “Non-redundant Bus Configuration” for more information.
PAGE 191
RN: 5-93 Case 1: Two power supply modules on Bus A require the same source capacity used on Bus B; therefore, Bus B must be protected for the same loading (86 amperes) as Bus A. It does not matter how many over-current devices (for multiple sources) are used as long as the input to Bus B is protected for a maximum load of 86 amperes. Simply stated, the concept is: make the Bus B loading and over-current protection equivalent to Bus A.
PAGE 192
RN: 5-94 Bus A/B Power Supply Modules (up to 4) System Power Supply Unit 2 PS2 -- + System Power Supply Unit 1 PS1 -- PS2 + -- + DC Bus to DC Bus Jumper PS1 -- + Bus A Bus A Return Bus Return Bus Bus B Bus B Figure 1.2.8A. Redundant Bus/Redundant Power Supply Configuration for System Power Supply Units The DC bus configuration ratings in Table 1.2.3 are as close to a DC bus-rated load as can be achieved.
PAGE 193
RN: 5-95 Separate system cabinet groups in a common area can be daisy chained together using a 35mm2 (2 AWG) intercabinet grounding conductor, and connected to the grounding electrode system through a single grounding electrode conductor (Figure 1.3.2). Alternatively, each cabinet group can have its own grounding electrode conductor to the grounding electrode system. Multiple grounding electrode conductors can attach at the same point on the grounding electrode system, or to different points.
PAGE 194
RN: 5-96 NOTE: The label for a discrete FIM is marked “Comm Active”. Current labels for analog FIMs are marked “Comm A” and “Comm B”. Older labels for analog FIMs were marked “Port A” and “Port B”. NOTE: The new FIM may be left in service in that socket; the failed FIM should be removed immediately. The empty socket will provide for another online replacement. Do not leave two FIMs plugged into an online replacement style panel.
PAGE 195
RN: 5-97 Description: The new part number for the MAIO16 FIM was added on page 7-3-2. D MAIO16 Field Interface Module (FIM): 4--20 mA Output 16 Point 10P54080004 or 10P58080005 Description: The new part number for the MAI32 FIM was added on page 7-3-27. D MAI32 Field Interface Module (FIM) 10P53190004 or 10P58300005 Description: Information on the new MAI32 FIM was added to Table 7.3.11 on page 7-3-38. Table 7.3.11.
PAGE 196
RN: 5-98 SP-7: Section 5 (Intrinsic Safety (IS)) Description: The new part number for the MAO16 FIM was added on page 7-5-18. Two FIMs are available: D MAI16 4--20 mA Input 10P54040004 or 10P57700005 D MAO16 4--20 mA Output 10P54080004 or 10P58080005 RS3: Software Release Notes for P1 R4.
PAGE 197
RN: Index-1 RS3t Software Release Notes Index Numbers 10P 5040000x, 2-32 5084x004, 1-5, 2-13 50870004, 2-32, 2-34 52800002, 2-12 5285000x, 2-13 53190004, 1-2, 2-22, 2-30, 5-78, 5-86, 5-96 53520006, 2-22, 2-31 53550006, 2-22, 2-31 54040004, 2-22, 2-30, 5-75, 5-77– 5-79, 5-98 54080004, 1-2, 2-22, 2-31, 5-75– 5-78, 5-79, 5-86, 5-96, 5-97 54440002, 2-21, 2-29, 5-79 54470002, 2-22, 2-31 5450000x, 5-79 55270010, 2-11, 2-14, 4-1, 4-2, 4-4, 4-5, 4-12 55270011, 2-12, 4-2 5527001x, 2-14 56450001, 1-5 56450002, 1-5
PAGE 198
RN: Index-2 1594--000x, 2-34 1598--0001, 2-8 1632--x000, 2-13 1634--x00x, 2-13 1895--9909, 4-7, 4-10 1927--000x, 2-12 1928--000x, 2-12 1954--000x, 5-32 1975--000x, 2-13 1978--0001, 2-13 1978--0003, 2-13 1989--000x, 2-12 2107--0005, 2-14 2120--0008, 2-14 2122--0007, 2-14 2137--0008, 2-14, 2-32, 2-33 2172--0927, 4-1 2307--000x, 2-12 2347--0011, 2-8 2347--0021, 2-8 2347--0041, 1-5, 2-8 2372--x0xx, 2-13 2380--0005, 4-12 2412--000x, 2-29 2480--000x, 5-79 2500--0005, 2-32 2500--000x, 5-54 2503--0001, 2-11, 2-12,
PAGE 199
RN: Index-3 Corrected Defects, 3-1 CP5, 1-2, 1-5, 1-7, 2-3, 2-5 CPI ControlFile Requirements, 2-3, 2-6, 2-21, 2-28 CPII ControlFile Requirements, 2-3, 2-5, 2-6, 2-21, 2-26 Crash dump format, 1-3 D DeltaV, 1-7 DeltaV Operate for RS3, 1-7, 2-3, 2-4, 2-5 Disk Load Program or Script, theory, 5-35– 5-38 Disk--only console, 1-3, 2-10, 2-14– 2-16, 5-2, 5-5 drive locations, tape, 5-29 E Enhancements 4 Meg NV Memory, 1-2, 2-8 ABC Batch Messaging, 1-2, 2-33, 5-5, 5-9, 5-28, 5-35 Alarm Banner, 1-3 Asset Management S
PAGE 200
RN: Index-4 Kill memory dump alarm, 5-5 L Link Editor capabilities, 1-3 Link Editor changes, 1-3, 5-5, 5-12– 5-17 links available, 5-26– 5-28 block, 5-26– 5-50 ControlFile links available, 5-26 within Controller Processor, 5-26– 5-27 loading, FIC/FIM program image, 5-35– 5-38 M magnetic media, storage and handling, 5-29– 5-31 MAI32 FIM, 1-2, 1-6, 5-74, 5-77– 5-79, 5-82, 5-84, 5-86, 5-87, 5-96– 5-98 MAO16 Output FIM, 1-2, 1-6, 5-79, 5-82, 5-86, 5-98 Master License Agreement, 1-3, 5-28, 5-44– 5-46 Memory Al
PAGE 201
RN: Index-5 V Video Generator, Pixel Graphics, 5-85 Version P1 Corrected Defects, 3-1 Version P1 R4.0 Software Image Versions, 2-36 Version P1 R4.1 Software Image Versions, 2-37 Version P1 R4.2 Software Image Versions, 2-37 W RS3: Software Release Notes for P1 R4.2 write filter.
PAGE 202
RN: Index-6 RS3: Software Release Notes for P1 R4.