P1 Console Configuration Manual · CC: vi RS3: Console Configuration Manual About This Manual Changes for This Release D Automatic backup capability has been added. D Support for

RS3t

ConsoleConfiguration

Manual

Performance Series 1, Release 4.0

Aug 1999U.S. Manual PN: 1984-2643-2100

A-4 Size Manual PN: 1984-2643-2110

1984-2643-50071984-2643-5017

EFisher-Rosemount Systems, Inc., 1987--1999.

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. OtherPatents Pending.

RS3 is a mark of one or more of the Fisher-Rosemount group of companies. All other marks are property of their respective owners. Thecontents of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy,they are not to be construed as warranties or guarantees, express or implied, regarding the products or services described herein or theiruse or applicability. We reserve the right to modify or improve the designs or specifications of such products without notice.

Fisher-Rosemount Systems, Inc.12000 Portland Avenue SouthBurnsville, Minnesota 55337 U.S.A.

Telephone: (612) 895-2000TWX/Telex: 192177FAX: (612) 895-2044

Comment FormRS3t Manuals

Console Configuration Manual 1984-2643-21x0

Please give us your feedback to help improve this manual.

Never Rarely Sometimes Usually Always1. Do you actually use this manual when

you are:D configuringD making changes or enhancements

D operating the system

D troubleshootingD other __________________________

____________

______

____________

____________

______

____________

____________

______

____________

____________

______

____________

____________

______

____________

2. Does this manual answer your questions? ______ ______ ______ ______ ______

3. What could be changed in this manual to make it more useful?

Errors and Problems: Please note errors or problems in this manual, including chapter and page number,if applicable; or send a marked-up copy of the affected page(s).

May we contact you about your comments? j Yes j No

Name ______________________________________________

Company ______________________________________________

Phone ______________________________________________

Date ______________________________________________

Fisher-Rosemount FAX #: (612) 895-2044 Thank you!

Placestamphere

Name

Company

Address

Fisher-Rosemount Systems, Inc.RS3 User DocumentationMail Station G3012000 Portland Avenue SouthBurnsville, MN 55337U.S.A.

Seal with tape.

CC: v

RS3: Console Configuration Manual About This Manual

RS3tConsole Configuration Manual

About This Manual

This manual describes the operations performed on RS3 consoles. Themanual is divided into eight chapters:

D Chapter 1 Describes the two types of RS3 consoles: theSystem Manager Station and the single CRTMultitube Command Console.

D Chapter 2 Provides information on configuring consoleoperating characteristics, color, operatingdisplays, callup and display buttons, messagepairs, and the block print function. Also givesinformation on the Russian Console.

D Chapter 3 Describes the operating characteristics of theprocess graphics system, including configuringcolor, creating shapes, and combining and editingobjects.

D Chapter 4 Explains operation and configuration of reports,which feed back vital process variable informationto the screen or to a printout.

D Chapter 5 Provides information about trending data from aprocess, including storing, organizing, andaccessing that data.

D Chapter 6 Describes management of alarms generated bythe RS3, including alarm types, alarm display,alarm acknowledgment, separation and storing ofalarms, alarm history, and alarm animation.

D Chapter 7 Explains password security for the RS3. Includeslogging functions, as well as password systemconfiguration and troubleshooting.

D Chapter 8 Provides lists of commands used on the SystemManager Station and single CRT MultitubeCommand Console.

CC: vi


Changes for This Release

D Automatic backup capability has been added.D Support for ABC Batch Messages (ABM) has been added.D Batch support on SMS has been added.D Changes to the Link Editor function have been made and a new

section (Section 2-7) was created for this subject.D The Tandberg TDC 3660 tape drive is now supported.

Revision Level for This Manual

For ThisSoftware

Refer to This Document:SoftwareVersion: Title Date Part Number

P1R4.0 Console Configuration Manual ??? 1999 1984--2643--????

P1R1.0 Console Configuration Manual May 1996 1984-2643-21x0

18R2 Console Configuration Manual August 1994 1984-2643-18x1

18R1 Console Configuration Manual October 1993 1984-2643-18x1

17 Console Configuration Manual August 1992 1984-2643-17x1

16 Console Configuration Manual January 1992 1984-2643-16x1

15 Console Configuration Manual January 1991 1984-2643-15x1

CC: vii


References to Other Manuals

References to other RS3 user manuals list the manual, chapter, andsometimes the section as shown below.

Sample Entries:For ..., see CC: 3. For ..., see CC: 1-1.

Manual Title Manual TitleChapter Chapter-Section

Abbreviations of Manual TitlesAL= Alarm MessagesBA= ABC BatchCB= ControlBlock ConfigurationCC= Console ConfigurationDT= Disk and Tape FunctionsIO = I/O Block ConfigurationOP= Operator’s GuideOV= System Overview and GlossaryPW= PeerWay InterfacesRB= Rosemount Basic LanguageRI = RNI Release Notes and Installation GuideRP= RNI Programmer’s Reference ManualSP= Site Preparation and InstallationSV= Service

CC: viii


Reference Documents

Prerequisite Documents

You should be familiar with the information in the following documentsbefore using this manual:

System Overview Manual and Glossary 1984-2640-21x0

Software Release Notes, Performance Series 1 1984-2818-0110

Related Documents

You may find the following documents helpful when using this manual:

ABC Batch Software Manual 1984-2654-21x0

Alarm Messages Manual 1984-2657-19x1

ABC Batch Quick Reference Guide 1984-2818-1103

Configuration Quick Reference Guide 1984-2812-0808

Console Configuration Manual 1984-2643-21x0

ControlBlock Configuration Manual 1984-2646-21x0

I/O Block Configuration Manual 1984-2645-21x0

Operator’s Guide 1984-2647-19x1

PeerWay Interfaces Manual 1984-2650-21x0

Rosemount Basic Language Manual 1984-2653-21x0

RNI Programmer’s Reference Manual 1984-3356-02x1

RNI Release Notes and Installation Guide 1984-3357-02x1

Service Manual, Volume 1 1984-2648-21x0

Service Manual, Volume 2 1984-2648-31x0

Service Quick Reference Guide 1984-2816-0904

Site Preparation and Installation Manual 1984-2642-21x0

Software Discrepancies for Performance Series 1 1984-2818-0311

User Manual Master Index 1984-2641-21x0

RS3: Console Configuration Manual Contents

Chapter 1: RS3 Consoles

Section 1: System Manager Station 1-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: Single CRT Multitube Command Console 1-2-1. . . . . . . . . . . . . . . . . .

Chapter 2: Configuring Operating Characteristics

Section 1: Configuring Console Operations 2-1-1. . . . . . . . . . . . . . . . . . . . . . . . . .

User Privileges 2-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Access Levels 2-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Access Indicators 2-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Menu Command Console Screen 2-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring the Console 2-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Console Configuration Screen Fields 2-1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Access to an Alternate Console Disk over the PeerWay 2-1-17. . . . . . .Configuring Consoles to Switch Keyboard Control 2-1-19. . . . . . . . . . . . . . . . . . . . . .

Configuring 16-Character Block Tags 2-1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Tags Affected 2-1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Splitting and Masking Tags 2-1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Taking Advantage of Masking and Splitting Options 2-1-21. . . . . . . . . . . . . . . . . . . . .Split Tags 2-1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Where Tags Are Automatically Split 2-1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Specifying Where to Split Tags-Tag Row Break 2-1-23. . . . . . . . . . . . . . . . . . . . . .

Masking Tags 2-1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Where Masking Does Not Apply 2-1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Specifying a Mask 2-1-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Turning Masking On and Off 2-1-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How Tag Splitting and Masking Interact 2-1-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automatic Backup Functions 2-1-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automatic Console Configuration Backup 2-1-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automatic Plant Configuration Backup 2-1-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Customizing the Plant Configuration Backup 2-1-30. . . . . . . . . . . . . . . . . . . . . . . .Node Ownership and Plant Unit Ownership 2-1-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Node Ownership 2-1-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Plant Unit Ownership 2-1-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operator Change Log 2-1-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Configuring Console Operations 2-1-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 2-1-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tips 2-1-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Refresh and Advance Request Rates 2-1-38. . . . . . . . . . . . . . . . . . . . . . .

Screen Refresh Rate 2-1-39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Field Refresh Rate 2-1-40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: x


Section 2: Configuring Color 2-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Master Color Selection Screen 2-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Color Configuration Screens 2-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Configuring Colors 2-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 2-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Configuring Operating Displays 2-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Group Displays 2-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Group Directory Screen 2-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Group Display Screen 2-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Unit Displays 2-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Unit Directory Screen 2-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Unit Display Screen 2-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Overview Displays 2-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Overview Directory Screen 2-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Overview Display Screen 2-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Configuring Callup and Display Buttons 2-4-1. . . . . . . . . . . . . . . . . . .

Configuring Callup Buttons 2-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring a Command 2-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring a Callup Button Number 2-4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Alarm Annunciation 2-4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Callup Buttons Screen 2-4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Display Buttons Screen 2-4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Callup Buttons and Display Buttons 2-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 2-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tips 2-4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 5: Configuring Message Pairs 2-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standard and User Message Pairs 2-5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Message Pairs Screens 2-5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Using Message Pairs 2-5-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Tips 2-5-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 6: Configuring the Block Print Function 2-6-1. . . . . . . . . . . . . . . . . . . . . .

Section 7: Link Editor 2-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Modifying a Configuration File 2-7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Modifying Other RS3 File Types 2-7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Calling Up the Link Editor Screen 2-7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Procedure: Editing Link Addresses 2-7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 8: Multinational Characters and Russian Console 2-8-1. . . . . . . . . . . . .Multinational Characters 2-8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Russian Console 2-8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Entering Text and Commands 2-8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Compatibility with Previous Releases 2-8-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Printing 2-8-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: xi


Chapter 3: Process Graphics

Section 1: Introduction to Process Graphics 3-1-1. . . . . . . . . . . . . . . . . . . . . . . . . .

How are Process Graphics Stored? 3-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How are Process Graphics Created and Accessed? 3-1-3. . . . . . . . . . . . . . . . . . . . . . .

Creating a Process Graphic 3-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Calling Up the Viewing Mode of a Process Graphic 3-1-4. . . . . . . . . . . . . . . . . . . . .Calling Up the Configuration Mode of a Process Graphic 3-1-6. . . . . . . . . . . . . . . . .

Section 2: Creating and Configuring Process Graphics 3-2-1. . . . . . . . . . . . . . . .

Creating Process Graphics Objects 3-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object Types 3-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How Objects Appear in Viewing and Configuration Modes 3-2-7. . . . . . . . . . . . . . . . . .Creating Shapes: Circles 3-2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Boxes 3-2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Triangles 3-2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Arcs 3-2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Lines 3-2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Lines with Different Characteristics 3-2-14. . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Shape Characteristics 3-2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Library Symbols 3-2-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: New Symbols 3-2-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Shapes that Fill Up in Response to a Block Variable 3-2-21. . . . . .Creating Shapes: Multicolor Shapes 3-2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Block Information: Tag, Blkdes, Mode Objects 3-2-25Creating Objects That Display Block Variable Information in Character Form:Links, Units, Disc Objects 3-2-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Block Variable Information in Graphic Form:Hdev, Vdev, Ticbar Objects 3-2-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How the Hdev and Vdev Objects Are Displayed 3-2-33. . . . . . . . . . . . . . . . . . . . . . . .How the Ticbar Object is Displayed 3-2-35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Objects That Display Faceplates: Group, Unit, Overview Objects 3-2-37. . . .Displaying a Faceplate from a Process Graphic Object 3-2-40. . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Trend Information: Trend Object 3-2-41. . . . . . . . . . . . . .

How the Trend Object is Displayed 3-2-44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Displayed Text: Text Object 3-2-46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Displaying Alarms: Alarm Object 3-2-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Data Entry Fields: Disc Object 3-2-53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring The Appearance of Objects to Change, Depending on the State of aDiscrete Block Variable 3-2-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Moving and Copying Objects 3-2-56. . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Deleting Objects 3-2-57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Stacking Objects—Top and Bottom Operations 3-2-58. . . . . . . . .Configuration Tools: Example of Stacking Objects 3-2-59. . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Grouping Objects 3-2-60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Grouping Objects—Area Operation 3-2-61. . . . . . . . . . . . . . . . . . .

CC: xii


Configuration Tools: Grouping Objects—Group and Join Operations 3-2-63. . . . . . . . .Joining Single Objects 3-2-63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Joining Groups of Objects 3-2-64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Tools: Grouping Objects—Merge Operation 3-2-66. . . . . . . . . . . . . . . . . .Configuration Tools: Using the Link Editor Field 3-2-67. . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Splitting an Object from a Group 3-2-69. . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Undoing the Previous Operation 3-2-70. . . . . . . . . . . . . . . . . . . . . .Configuring Display Characteristics: Process Graphics Fabric Coordinates 3-2-71. . . .Configuring Display Characteristics: Changing the Panning Limits andOrigin Point 3-2-72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation 3-2-73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation: Objects that Call up Other Displays 3-2-74.Creating Assists for Display Manipulation: Objects that Call up Another Part of theSame Display 3-2-75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation: Display Targets 3-2-77. . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation: Hiding Parts of the Display Usingan Icon Object 3-2-79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Copying a Process Graphic 3-2-82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Batch Task Data: Bface Object 3-2-83. . . . . . . . . . . . . . .Alarm Annunciation on Graphics 3-2-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Object 3-2-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Icon Object 3-2-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Optimizing Graphics Performance 3-3-1. . . . . . . . . . . . . . . . . . . . . . . . .

Process Graphic Limits 3-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Link Count Field 3-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using Funnel Blocks 3-3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Merging Objects 3-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Other Methods of Optimizing Graphics 3-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preconfigured Process Graphics 3-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Screen Refresh and Field Refresh 3-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4: Reports

Section 1: Introduction to Reports 4-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: The Report File Structure 4-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Report Read Directory Screen 4-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report File Contents Screen 4-2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report Read/Scan Screen 4-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report Config Directory Screen 4-2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report Status Screen 4-2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Designing a Report 4-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assembling Information for a Report 4-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Dimensions of a Report 4-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Formatting the Report for Printing 4-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: xiii


Section 4: Configuring a Report 4-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report Configuration Screen 4-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Report Objects 4-4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using Report Objects to Configure Reports 4-4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Editing the Body of a Report 4-4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring How a Report is Printed 4-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Determine Report Print Characteristics 4-4-9. . . . . . . . . . . . . . . . . . . . . . . . .How to Begin a New Report Page 4-4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Text in a Report 4-4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Print Regular--sized Text 4-4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Print Oversized Text 4-4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Operator Comments in a Report 4-4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Block Information in a Report 4-4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Configure a Block Tag 4-4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Address 4-4-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Descriptor 4-4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Function 4-4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Mode 4-4-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure Block Units 4-4-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure Block Values 4-4-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Perform Calculations 4-4-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Configure Trend File Information in a Report 4-4-25. . . . . . . . . . . . . . . . . . . . . . .How to Use an Accumulator with a Trend Log Object 4-4-30. . . . . . . . . . . . . . . . . . . .

Configuring Time and Date Information in a Report 4-4-31. . . . . . . . . . . . . . . . . . . . . . . .How to Configure the Current Time 4-4-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure the Current Date 4-4-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Console Lists in a Report 4-4-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring the List Object 4-4-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Formatting a List 4-4-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Configure Another Report in a Report 4-4-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Generating Reports 4-4-38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Generate a Report Based on Time and Date 4-4-38. . . . . . . . . . . . . . . . . . . .How to Generate a Report Based on Alarms or Events 4-4-40. . . . . . . . . . . . . . . . . .How to Generate a Report from the Report Configuration Screen 4-4-41. . . . . . . . .How to Print a Report When it is Generated 4-4-42. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 5: Saving a Report to Disk 4-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 6: Hints for Configuring and Using Reports 4-6-1. . . . . . . . . . . . . . . . . . .Configuration Problems 4-6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Tips 4-6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Marking Lines in Reports 4-6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5: Trending

Section 1: Trending Operations 5-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Console Trending Capabilities 5-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: xiv


How Trend File Information is Stored 5-1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .What Block Variables Can be Trended 5-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using Trending Screens 5-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Enabling and Disabling Trending 5-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Trending Condition upon Console Restart 5-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: Configuring Trend Files 5-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Trend File Setup Screen 5-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring a Trend File 5-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining When and How Often Data is Stored(Frequency and Duration Fields) 5-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Configuring Trend Groups 5-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Trend Group Configuration 5-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Trend Group Displays 5-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the Slidewire 5-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Trend Group Scaling 5-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Viewing Trend Data 5-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How Often Trend Group Displays Update 5-3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Archive Trend Data 5-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How a Backup Trend File is Saved 5-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Restoring and Reading Trend Archive Data 5-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Restoring and Reading Trend Archive Data from Tape 5-4-3. . . . . . . . . . . . . . . . . . .

Section 5: Hints for Configuring Trending 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Copying Trend Files 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Determining Trend Group Update Time 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6: Alarm Management

Section 1: Managing the Number of Alarm Messages on the PeerWay 6-1-1. .

Configuring Which Nodes Are Sent Alarms from a ControlFile or Console 6-1-2. . . . .Using CAB to Reduce Message Load 6-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inhibiting Alarms from Generating on the PeerWay 6-1-7. . . . . . . . . . . . . . . . . . . . . . . .Using ControlBlock Logic 6-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using the ControlFile Status Screen 6-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Effects of Inhibiting Alarms 6-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: How Alarms Get Stored in Console RAM 6-2-1. . . . . . . . . . . . . . . . . . .

Section 3: Separating and Sorting Alarms at a Console 6-3-1. . . . . . . . . . . . . . . .

Alarm Types 6-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Areas 6-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Disabling and Enabling an Alarm Area 6-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: xv


Disabling an Alarm Area 6-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Enabling an Alarm Area 6-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Suppression 6-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Suppressing an Alarm 6-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Unsuppressing an Alarm 6-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Alarm List and Event List Properties 6-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . .The Alarm List Configuration Screen 6-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RS3 Events 6-3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .User-defined Events 6-3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring the Event List 6-3-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Alarm History 6-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Log Display Configurations 6-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Displaying Information from the Alarm Log 6-4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Disabling and Enabling the Alarm Log 6-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 5: Configuration and Display Topics 6-5-1. . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Configuration Screen 6-5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Configuration Screen—Automatic Alarm Deletion 6-5-8. . . . . . . . . . . . . . . . .

Alarm Regeneration 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .When Do Alarms Regenerate 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How Consoles Regenerate Alarms 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Restrictions 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Priority 6-5-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Type Priority 6-5-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Priority Numbers 6-5-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Display Mode 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Banner Mode 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Summary Mode 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Determining the Alarm Display Mode 6-5-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 6: Alarm Animation 6-6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Tags 6-6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Tags on Trend Group Displays 6-6-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Block Variable Values 6-6-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Plant Units and Area Names 6-6-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Graphic Alarm Objects and Icon Objects 6-6-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Message Source Descriptions 6-6-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 7: Hints for Alarm Management 6-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 6-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tips 6-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: xvi


Chapter 7: Password Security

Section 1: Configuring Password Security 7-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .Initial Password System Configuration 7-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Factory-shipped Password System 7-1-2. . . . . . . . . . . . . . . . . . . . . . . . .Logging in and Configuring Primary and Backup Nodes 7-1-3. . . . . . . . . . . . . . .Changing User and Login Names and Completing Configuration 7-1-4. . . . . . .

Defining Password Security with a Configuror’s Key 7-1-5. . . . . . . . . . . . . . . . . . . . .Configuring Primary and Backup Nodes 7-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .Adding a System Manager 7-1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Logging In 7-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System-wide Password Parameters 7-1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Defining System-wide Parameters 7-1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Saving the Console Configuration 7-1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .User Profile Directory 7-1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Plant Unit Access 7-1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Plant Unit Access and Plant Unit Configuration 7-1-15. . . . . . . . . . . . . . . . . . . . . . . . .Defining Plant Unit Access 7-1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing Plant Unit Access Definitions 7-1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User Name Detail Screen 7-1-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Adding Users to the Password System 7-1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing User Name Profiles 7-1-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing a Configuror to a System Manager 7-1-24. . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: Accessing a Password Secure System 7-2-1. . . . . . . . . . . . . . . . . . . . .Logging on to the System 7-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing a Password 7-2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Logging Off the Console 7-2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Password Security Hints and Troubleshooting 7-3-1. . . . . . . . . . . . .Scenario 1: Handling Primary and Backup Nodes 7-3-2. . . . . . . . . . . . . . . . . . . . . . . . . .Scenario 2: Using Passwords with Keylock and Secure Interfaces 7-3-3. . . . . . . . . . .Scenario 3: Using Passwords with a Standard KBI 7-3-4. . . . . . . . . . . . . . . . . . . . . . . . .Scenario 4: Using Key and Password Access 7-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Scenario 5: Loss of $$PASSWD File 7-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Scenario 6: Console Configuration File Not Found 7-3-7. . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 8: Commands

Section 1: Introduction to Commands 8-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Symbols Used 8-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: SMS Commands 8-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: MTCC Commands 8-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Hints for Using Commands 8-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1984-2643-72001984-2643-7210

ContentsRS3: RS3 Consoles


Chapter 1:RS3 Consoles

Section 1: System Manager Station 1-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: Single CRT Multitube Command Console 1-2-1. . . . . . . . . . . . . . . . . .

CC: ii

RS3: RS3 Consoles Contents

CC: 1-1-1

RS3: RS3 Consoles System Manager Station

Section 1:System Manager Station

The System Manager Station (SMS) provides maintenance andtroubleshooting functions on an RS3 system.

On the SMS, you can enter commands that

D Configure console operating characteristics

D Do plant configuration

D Manage alarms and events, alarm and event lists, and alarmareas

D Manage RBL

D Perform disk and tape operations

D Perform operations on ControlFiles

D Perform diagnostics

D Manage password security functions

Chapter 8 of this manual includes a summary of the SMS commands.Table 8.2.1 lists the commands that call up screens and Table 8.2.2.lists the commands that perform operations.

CC: 1-1-2

RS3: RS3 Consoles System Manager Station

CC: 1-2-1

RS3: RS3 Consoles Single CRT Multitube Command Console

Section 2:Single CRT Multitube Command Console

The single CRT Multitube Command Console (MTCC) includes all of thecapabilities provided on the SMS, plus the functions required for anoperations environment and batch processing. Note that wherever“MTCC” is used in this manual, the actual meaning is a single CRTMTCC.

On the MTCC, you can enter commands that

D Configure console operating characteristics

D Do plant configuration

D Manage alarms and events, alarm and event lists, and alarmareas

D Manage Batch and RBL

D Perform disk and tape operations

D Perform operations on ControlFiles

D Perform diagnostics

D Manage password security functions

D Create and configure process graphics

D Design, configure, and generate reports

D Create trend files

Chapter 8 includes a summary of the MTCC commands. Table 8.3.1lists the commands that call up screens, and Table 8.3.2 lists thecommands that perform operations. The commands and operationsallowed by users are determined by console access levels. SeeChapter 2: Section 1 for more information about console access levels.

CC: 1-2-2

RS3: RS3 Consoles Single CRT Multitube Command Console

ContentsRS3: Configuring Operating Characteristics


Chapter 2:Configuring Operating Characteristics

Section 1: Configuring Console Operations 2-1-1. . . . . . . . . . . . . . . . . . . . . . . . . .User Privileges 2-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Access Levels 2-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Access Indicators 2-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Menu Command Console Screen 2-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring the Console 2-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Console Configuration Screen Fields 2-1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Access to an Alternate Console Disk over the PeerWay 2-1-17. . . . . . .Configuring Consoles to Switch Keyboard Control 2-1-19. . . . . . . . . . . . . . . . . . . . . .

Configuring 16-Character Block Tags 2-1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Tags Affected 2-1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Splitting and Masking Tags 2-1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Taking Advantage of Masking and Splitting Options 2-1-21. . . . . . . . . . . . . . . . . . . . .Split Tags 2-1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Where Tags Are Automatically Split 2-1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Specifying Where to Split Tags-Tag Row Break 2-1-23. . . . . . . . . . . . . . . . . . . . . .

Masking Tags 2-1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Where Masking Does Not Apply 2-1-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Specifying a Mask 2-1-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Turning Masking On and Off 2-1-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How Tag Splitting and Masking Interact 2-1-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automatic Backup Functions 2-1-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automatic Console Configuration Backup 2-1-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automatic Plant Configuration Backup 2-1-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Customizing the Plant Configuration Backup 2-1-30. . . . . . . . . . . . . . . . . . . . . . . .Node Ownership and Plant Unit Ownership 2-1-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Node Ownership 2-1-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Plant Unit Ownership 2-1-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operator Change Log 2-1-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Configuring Console Operations 2-1-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 2-1-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tips 2-1-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Refresh and Advance Request Rates 2-1-38. . . . . . . . . . . . . . . . . . . . . . .

Screen Refresh Rate 2-1-39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Field Refresh Rate 2-1-40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: Configuring Color 2-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Master Color Selection Screen 2-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: ii

RS3: Configuring Operating Characteristics Contents

Color Configuration Screens 2-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Configuring Colors 2-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 2-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Configuring Operating Displays 2-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Group Displays 2-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Group Directory Screen 2-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Group Display Screen 2-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Unit Displays 2-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Unit Directory Screen 2-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Unit Display Screen 2-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Overview Displays 2-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Overview Directory Screen 2-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Overview Display Screen 2-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Configuring Callup and Display Buttons 2-4-1. . . . . . . . . . . . . . . . . . .

Configuring Callup Buttons 2-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring a Command 2-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring a Callup Button Number 2-4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Alarm Annunciation 2-4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Callup Buttons Screen 2-4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Display Buttons Screen 2-4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Callup Buttons and Display Buttons 2-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 2-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tips 2-4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 5: Configuring Message Pairs 2-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Standard and User Message Pairs 2-5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Message Pairs Screens 2-5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Hints for Using Message Pairs 2-5-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Tips 2-5-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 6: Configuring the Block Print Function 2-6-1. . . . . . . . . . . . . . . . . . . . . .

Section 7: Link Editor 2-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Modifying a Configuration File 2-7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Modifying Other RS3 File Types 2-7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Calling Up the Link Editor Screen 2-7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Procedure: Editing Link Addresses 2-7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 8: Multinational Characters and Russian Console 2-8-1. . . . . . . . . . . . .

Multinational Characters 2-8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Russian Console 2-8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Entering Text and Commands 2-8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Compatibility with Previous Releases 2-8-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Printing 2-8-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iii

ContentsRS3: Configuring Operating Characteristics

List of Figures

Figure Page

2.1.1 Relationship Between Console Access Levels 2-1-2. . . . . . . . . . . . . . . . . . . .

2.1.2 Menu Command Console Screen for the SMS 2-1-5. . . . . . . . . . . . . . . . . . . .

2.1.3 Menu Command Console Screen for the MTCC 2-1-6. . . . . . . . . . . . . . . . . .

2.1.5 Console Configuration Screen for the SMS—Page 1 2-1-7. . . . . . . . . . . . . .

2.1.6 Console Configuration Screen for the MTCC—Page 1 2-1-8. . . . . . . . . . . . .

2.1.7 Console Configuration Screen—Page 2 2-1-9. . . . . . . . . . . . . . . . . . . . . . . . . .


2.1.9 Access to Alternate Console Disk over the PeerWay 2-1-18. . . . . . . . . . . . . .

2.1.10 Console Configuration Screen Switch Keyboard Examples 2-1-19. . . . . . . . .

2.1.11 Examples of Split Tags 2-1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.12 Splitting Character Tags 2-1-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.13 Masking Character Tags 2-1-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.14 Interaction of Tag Splitting and Masking 2-1-27. . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.15 Plant Status Screen 2-1-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.16 Plant Unit Configuration Field 2-1-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.17 Operator Change Log Screen Entries 2-1-35. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.18 Advance Request Concept 2-1-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.1 Master Color Selection Screen 2-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.2 Color Configuration Screen 2-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Group Directory Screen 2-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.2 Group Display Screen 2-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.3 Unit Directory Screen 2-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.4 Unit Display Screen 2-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.5 Overview Directory Screen 2-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.6 Overview Display Screen 2-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 Callup and Display Buttons 2-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.2 Alarm Annunciation Screen 2-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.3 Option Keyboard Callup Button Example 2-4-4. . . . . . . . . . . . . . . . . . . . . . . . .

2.4.4 Alarm Annunciation Screen Example 2-4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.5 Callup Buttons Screen 2-4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.6 Display Buttons Screen 2-4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.1 Faceplates and Message Pairs 2-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iv

RS3: Configuring Operating Characteristics Contents

2.5.2 Standard Message Pairs Screen 2-5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.3 User Message Pairs Screen 2-5-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6.1 Block Print Setup Screen 2-6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7.1 Link Editor Screen 2-7-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Tables

Table Page

2.1.1 Console Access Level Indicators 2-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 Console Configuration Screen Fields 2-1-10. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.3 How Node Ownership and Plant Unit Ownership Work Together 2-1-31. . . .

2.1.4 Printer Interface Instructions 2-1-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.1 Color Configuration Screen Fields 2-2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 Group Display Entries for Faceplates 2-3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.1 Command Examples 2-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.2 Special Commands 2-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.4.3 How to Configure Alarm Annunciation 2-4-5. . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.1 Message Pair Characteristics 2-5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.2 Preconfigured Standard Message Pairs 2-5-6. . . . . . . . . . . . . . . . . . . . . . . . .

2.5.3 Preconfigured User Message Pairs 2-5-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6.1 Block Print Setup Screen Fields 2-6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: 2-1-1

RS3: Configuring Operating Characteristics Configuring Console Operations

Section 1:Configuring Console Operations

This section describes the following:

D Console access levels

D The Menu Command Console screen

D The Console Configuration screens

D Configuring 16--character block tags

D Automatic backup functions

D Node ownership and plant unit ownership

D The Operator Change Log

D Hints for configuring console operations

CC: 2-1-2


User Privileges

User privileges ensure that authorized system users have appropriateaccess to the RS3. The system grants users privileges based on jobcategory, or access level.

For systems without password security, a key inserted into the consoleidentifies the user’s access level. For systems with password security,login names and passwords give users access to the RS3 and identifythe user’s access level.

Access Levels

These are access levels for RS3 console users:

D System manager

D Configuror

D Supervisor

D Operator

D Recipe manager

The diagram in Figure 2.1.1 shows the relationship between the levels.

System Manager Privileges (password systems only)

Configuror Privileges

OperatorPrivileges

Recipe ManagerPrivileges

SupervisorPrivileges

RecipeManager

Supervisor

Figure 2.1.1. Relationship Between Console Access Levels

CC: 2-1-3


An operator has only operator-specific privileges. A recipe manager anda supervisor both contain all of the privileges of an operator, but theprivileges specific to each of them do not intersect. The configuror hasaccess to all the privileges of recipe manager, supervisor, and operator.

The system manager level is available on the SMS and on an MTCCwith password security. For more information about password security,see Chapter 7.

On an SMS, the system manager has all the privileges of the foursubordinate levels, but cannot perform all of the functions of thoselevels. See Chapter 8 for a list of the commands available on the SMS.

A user with system manager privileges can configure password securityand perform certain disk and tape functions, such as:

D Perform disk operations on the $$PASSWD file in the ConsoleConfiguration folder

D Delete a Console Configuration folder

D Configure the hard disk

D Initialize the disk

If any user other than a system manager attempts to perform theseactivities on an MTCC, no enterable fields appear on the screen.

CC: 2-1-4


Access Indicators

Fields on the configuration screens are usually preceded by an indicatorthat shows what type of user has access privileges for that field.Table 2.1.1 lists each access level, its definition, the access indicatorused, and the key used.

Table 2.1.1. Console Access Level Indicators

AccessLevel

AccessIndica-tor

Definition Key

System manager *

A user who has access to allconfiguror privileges, and is alsoallowed to set up password securityand to perform certain disk and tapefunctions.

None

Configuror �A user who is responsible forconfiguring the system. 3 or 4

Recipe manager #

In ABC Batch, a user who isresponsible for constructing theMaster Recipes. The recipemanager is typically a chemist whomust have complete access to allrecipe interface features.

8 or 9

Supervisor !A user who oversees the RS3control system operation. 5, 6, or 7

Operator > A user who has privileges relatedto operations. 10 to 31

CC: 2-1-5


The Menu Command Console Screen

The Menu Command Console Screen is the main menu from which youcan select other directories and configure your console.

Figure 2.1.2 shows the Menu Command Console Screen for the SystemManager Station (SMS). Figure 2.1.3 shows the Menu CommandConsole Screen for the Multitube Command Console (MTCC).

MENU COMMAND CONSOLE 09-Jul-96 15:22:10

Overview Directory Disk Directory PeerWay

Unit Directory Disk Directory

Group Directory Configure Command Console

Process Active Alarms Plant Status

Alarm List Configuration Tuning Display Directory

Operator Log

Copyright E 1981-1996 Fisher-Rosemount Systems, Inc

FULL CONFIG 1

- To call up:D Type MCC [ENTER] at the command line.

D [PAGE AHEAD] from Page 3 of the ConsoleConfiguration Screen

D [PAGE BACK] from Page 1 of the ConsoleConfiguration Screen

- To access other screens:D [PAGE AHEAD] to see Page 1 of the

Console Configuration Screen.

D [PAGE BACK] to see Page 3 of theConsole Configuration Screen.

- To select a Directory on the MCC screen:D Place the cursor over the desired

directory and press [SELECT].

Figure 2.1.2. Menu Command Console Screen for the SMS

CC: 2-1-6


MENU COMMAND CONSOLE 09-Jul-96 15:22:10

Process Graphics Directory Disk Directory PeerWay

Overview Directory Disk Directory

Unit Directory Configure Command Console

Group Directory Plant Status

Trend Group Directory Process Active Alarms

Tuning Display Directory Alarm List Configuration

Report Read Directory Operator Log

Copyright E 1981-1996 Fisher-Rosemount Systems, Inc

FULL CONFIG 1

- To call up:D Type MCC [ENTER] at the command line.

D [PAGE AHEAD] from Page 3 of the ConsoleConfiguration Screen

D [PAGE BACK] from Page 1 of the ConsoleConfiguration Screen



D [PAGE BACK] to see Page 3 of theConsole Configuration Screen.

- To select a Directory on the MCC screen:D Place the cursor over the desired

directory and press [SELECT].

Figure 2.1.3. Menu Command Console Screen for the MTCC

CC: 2-1-7


Configuring the Console

The Console Configuration screen is used to configure consoleoperating characteristics. The Console Configuration screen consists oftwo screen pages of fields. To move between pages, you press either[PAGE AHEAD] or [PAGE BACK].

Figure 2.1.5 shows an example of page 1 of the Console Configurationscreen on the SMS. Figure 2.1.6 shows an example of page 1 of theConsole Configuration screen on the MTCC.

Figure 2.1.4 shows an example of Page 2 of the Console Configurationscreen for both the SMS and the MTCC. Figure 2.1.8 shows anexample of Page 3 of the Console Configuration screen for both theSMS and the MTCC. Table 2.1.2 gives the parameters and descriptionsof the fields on the screens.

CONSOLE CONFIGURATION 05-Nov-97 11:31:28

This is Node 28 SMS Date 05-Nov-97 Time 11:31:28Prgm Revision 7.42 PX ENG 68040 SMSBoot Revision 11.10 Peerway # >2 Slot width 30Last Restarted 04-Nov-97 15:32:57Logs: Batch >Enable Maint >Enable Time Correction >.00 Sec/dayAlarm >Disable Op Chg >Enable Host >Disable

Key Click >yes Keyclass for Ignore Interlock >SUPERMark Key >no

Keyclass for Loop Tuning >SUPERSpeaker Volume >MedAlarm Speaker >yes Keyclass for Reports >OPERGrp Blk ID for Oper >Descriptors Printer/Modem ConfigTags or Addresses >TagsPID Proportional >Band Printer >Fujitsu L/Pg >66Tape Auto Load >no

Configuration File Baud >4800 Print Node >28Name Update >yes Autodial >no FF >yes >ResetVolume Name : 540megFile Name : $TR-CNFG

CONFIG 1

- To call up:D Type CCC [ENTER] at the command line.

D [PAGE AHEAD] from Command ConsoleMenu.


Console Configuration screen.

D [PAGE BACK] to see Menu CommandConsole Screen.

Figure 2.1.5. Console Configuration Screen for the SMS—Page 1

CC: 2-1-8


CONSOLE CONFIGURATION 03-Nov-97 12:07:37

This is Node 32 MTCC Date �03-Nov-97 Time �12:08:36Prgm Revision 7.41 PX ENG 68040 MTCCBoot Revision 10.10 Peerway # >2 Slot width>30Last Restarted 31-Oct-97 09:02:47Logs: Batch >Disable Maint > Disable Time Correction >.00 Sec/dayAlarm >Disable Op Chg >Disable Host >DisableASCII Keyboard >Configuror Reboot Menu >13Key Click >yes Keyclass for Ignore Interlock >SUPERMark Key >noGraphics Menu Key >no Keyclass for Loop Tuning >SUPERSpeaker Volume >MedAlarm Speaker >yes Keyclass for Reports >OPERGrp Blk ID for Oper >Descriptors Printer/Modem ConfigTags or Addresses >TagsPID Proportional >Gain Printer >Fujitsu L/Pg >66Tape Auto Load >no

Configuration File Baud >4800 Print Node >28Name Update >yes Autodial >no FF >yes >ResetVolume Name : TMPFile Name : GRP-WDAY1

CONFIG 1

- To call up:D Type CCC [ENTER] at the command line.

D [PAGE AHEAD] from Command ConsoleMenu.


Console Configuration screen.

D [PAGE BACK] to see Menu CommandConsole Screen.

Figure 2.1.6. Console Configuration Screen for the MTCC—Page 1

CC: 2-1-9


CONSOLE CONFIGURATION 22-Oct-97 09:45:27

Keyboard Nodes>0 >0 >0 Tag Mask XXXXXXXXXXXXXXXXUse Tag Mask >no Tag Row Break >0

Keyboard Revisions >INITIALIZE TAG MASKKBI 1.4 Change Tag Size >yes Old >8 New >16TB 1.4 TAG OBJECTS CONFIGURED IN PROCESS GRAPHICSDISPPNL AND IN REPORTS FILES MAY BE CHANGED IN SIZEOPTPNL1 Tape Drive Type: RS3*T1 45S (qic-24)OPTPNL2OPTPNL3

Backup DisksOverlay Backup Node >None Volume > In Use>no

General Backup Node >None Volume > In Use>no

Automatic Backup ManagementPlant Config:>Disable Backup File $$BACKUP Event Type>0

Console Config:>Disable Destination File> Event Type>0

Field Refresh>0.5 secs Screen Refresh>1.0 secs Advance Requests >309:31:00 :=91H-05/FF 30:0000 PDHPIDLS CL U



D [PAGE BACK] to see Page 1 of the ConsoleConfiguration Screen.

Figure 2.1.7. Console Configuration Screen—Page 2

CONSOLE CONFIGURATION 09-Apr-96 12:08:00

System-wide Password Management

Title For Login Screen *Fisher-Rosemount Systems, Inc.

Primary Volume For $$PASSWD *Node_88

Backup Volume For $$PASSWD *Node_88

Current Volume For $$PASSWD >Node_88

- To access other screens:D [PAGE AHEAD] to view the Menu

Command Console Screen.D [PAGE BACK] to view Page 2 of the



CC: 2-1-10


Console Configuration Screen Fields

Table 2.1.2 describes the fields on Pages 1, 2, and 3 of the ConsoleConfiguration screen.

Table 2.1.2. Console Configuration Screen Fields

Field Description

Advance Requests

Specifies the maximum number of outstanding data request messagesto a controller that a console will allow at one time. The data requestedis used to update block links and data points in process graphics andgroup displays. Allowable values are from 1 to 5 requests. The defaultvalue is 3 requests.

NOTE: Advance Request can affect the performance of the PeerWayand controller. For more information on Configuring Refresh andAdvance Request Rates, see 2-1-38.

Alarm Speaker

Specifies if the console alarm speaker is functioning. Press [ENTER]to change the entry. Alarm speaker volume is determined by the“Speaker Volume” field.

D Yes specifies that the alarm speaker produces sound.D No specifies that the alarm speaker does not produce sound.

ASCII Keyboard

Specifies whether the configuror keyboard operates as an enhancedkeyboard or as a normal configuror keyboard. Press [ENTER] tochange the entry.

D Enhanced specifies that the keyboard operates as anenhanced keyboard. For more information about enhancedkeyboard displays, see OP.

D Configuror specifies that the keyboard operates as a normalconfiguror keyboard.

AutodialSpecifies whether or not a modem is used to generate a print requestto a remote printer. This field only applies if the printer is connected tothis node. Entries are yes and no. Press [ENTER] to change the entry.

Automatic Backup Management Displays the options for automatic backup of the plant configurationand console configuration.

Backup Volume for $$PASSWD

Backup drive where the $$PASSWD file resides.Enter up to 10 alphanumeric characters that match a valid disk drivename.

NOTE: A primary name that is blinking in yellow indicates that thisnode has been out of service at some time since configuration.

Baud

Specifies the communication speed (bits per second) between theconsole and the printer. This field only applies if the printer isconnected to this node.

Entries are 300, 600, 1200, 2400, 4800, and 9600.

(continued on next page)

CC: 2-1-11


Table 2.1.2. Console Configuration Screen Fields (continued)

Field Description

Boot Revision Displays the revision level of the Boot ROM on the console processorboard.

Change Tag SizeOld and New

Determines whether tag objects should change size in processgraphics and reports. This feature is useful when upgrading from anearlier version console software. For more information on changing tagsize, see the Software Upgrade Procedure.Note that the “Old” and “New” fields appear only if the value of“Change Tag Size” is “yes.” Also, the two lines immediately below thisfield stating that “TAG OBJECTS CONFIGURED IN PROCESSGRAPHICS AND IN REPORTS FILES MAY BE CHANGED IN SIZE”only appear if Change Tag Size is set to yes.

Console Config

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 theautomatic console configuration operation can be enabled.

D Event Type field requires selection of an event number from 0to 240, to trigger the automatic plant configuration backup.

See page 2--1--28 for more information on automatic consoleconfiguration backup.

Current Volume For $$PASSWDDrive where the $$PASSWD file is currently being stored.Enter up to 10 alphanumeric characters that match a valid disk drivename.

Date

Specifies the current date on all PeerWay nodes. Changes to oneconsole will change all nodes.

NOTE: Under a password security system, this field is designated withan asterisk (*), and may only be changed by a system manager(sysmgr).

FFSpecifies whether or not a form feed is generated on the printer after aprint has finished. This field only applies if the printer is connected tothis node. Entries are yes and no.

Field RefreshSpecifies the maximum rate at which the console can refresh a graphicobject field. Allowable refresh rates are from 0.5 to 4 seconds. Thedefault refresh rate is 0.5 seconds.

File Name Displays the file name of the console configuration file that is loadedfrom console battery backup memory if the console is rebooted.

General Backup Node Specifies a backup node for process graphic files.


CC: 2-1-12



Field Description

Graphics Menu Key(MTCC only)

Specifies whether or not the [HOME/MENU] key calls up theuser--configured $$MENU graphic file. Press [ENTER] to change theentry.

D Yes specifies that the $$MENU graphic file is called up if the[HOME/MENU] key is pressed at the command line (or pressedtwice from anywhere on a screen).

D No specifies that the [HOME/MENU] key does not call up agraphic file.

Grp Blk ID for Oper

Specifies if tags/addresses or descriptors are displayed when groupdisplays are called up and an operator key is inserted in this console.Press [ENTER] to change the entry.

D Tags/Addrs specifies that tags or addresses are displayed.(The “Display Tags” field determines whether the tag or theaddress is displayed.)

D Descriptors specifies that a descriptor is displayed.

Initialize Tag Mask Resets the tag mask back to its default state in which no charactersare masked.

Keyboard Nodes Specifies the console node to which the keyboard is connected.

Keyboard Revisions

Displays keyboard revision numbers for the following keyboardhardware:

KBI (Keyboard Interface software) foruse with the console.

TB (Trackball keyboard) for cursor andCRT Control.

DISPPNL(Display Panel keyboard) of operator functions. Alsoreferred to as the Operator’s keyboard.

OPTPNL (Options keyboard) with panels1, 2, and 3 for calling up user--definedsets of commands and graphic displays.

Key class for Loop Tuning

Specifies the access level for configuration of the following PIDControlBlock fields on the Tuning Display screen:

— Integral Time— Derivative Time— Cont Gain/Prop Band— FF Gain

Key class for Ignore Interlock

Specify the access level for configuration of the following discretemotor and valve function ControlBlock field on the ContinuousFaceplate screen:

— Ignore Interlock


CC: 2-1-13



Field Description

Key class for Reports(MTCC only)

Specifies the key class required to read and print reports.D Oper specifies that operators, supervisors, and configurors can

read and print reports.

D Super specifies that supervisors and configurors can read andprint reports.

D Config specifies that configurors can read and print reports.

Key Click

Specifies whether or not an audible sound is produced when akeyboard button is pressed. The key click volume is determined by the“Speaker Volume” field. Press [ENTER] to change the entry.

D Yes specifies that there is a key click.D No specifies that there is no key click.

L/Pg Specifies the number of lines printed on each page. This field onlyapplies if the printer is connected to this node. Entries are 0 to 127.

Last Restarted Displays the time when the console was last restarted.

Logs:

Batch

AlarmMaint

Op Chg

Host

Specifies whether or not the particular log is enabled or disabled.Press [ENTER] to change the entry.

Batch = Batch log

Alarm = Alarm logMaint = Smart transmitter maintenance log

Op Chg = Operator change log

Host = ABC Batch MessagesNote: Do not change the Host field to “Enable” mode unless you areusing the ABC Batch Messaging function to send Batch messages tothe RS3 Operator Station Journal. See the ROS Getting StartedManual for more information.

Mark Key

Specifies whether or not the [RECALL] button marks screens forrecall. Press [ENTER] to change the entry.

D Yes specifies that screens can be marked for recall.

D No specifies that screens cannot be marked for recall. The[RECALL] key only calls up the previous screen.

A screen is marked for recall by pressing [ENTER] from the commandline when that screen is displayed. A screen is recalled by pressing the[RECALL] key and specifying the number of the screen (1--5) to berecalled. After a screen has been recalled, the mark function for thatscreen is removed.


CC: 2-1-14



Field Description

Name Update

Specifies whether or not the Configuration Volume Name and FileName are updated. The Configuration Volume Name and File Namedetermine which file is used to boot up the console.

D Yes specifies that the “Volume Name” and “File Name” fieldschange to show the last console configuration file that is loadedor saved at this console.

D No specifies that the “Volume Name” and “File Name” fields donot change.

Overlay Backup Node Specifies a backup node on which screen overlays are stored.

PeerWay #

Specifies the number of the PeerWay that is connected to the console(1 -- 31). It is recommended that no PeerWay be designated asPeerWay 31.

If you change the PeerWay number, you should press [ENTER] twiceto verify the change.

Do not change this field if your process is running.

PID ProportionalSpecifies whether controller gain (Gain) or proportional band (Band) isused at this console for PID blocks. Press [ENTER] to change theentry.

Plant Config

Controls automatic plant configuration backup.D Plant Config: field toggles between Enable and Disable.

D Backup File field always specifies $$BACKUP as the backupfile. The $$BACKUP file must exist before the automatic plantconfiguration operation can be enabled.

D Event Type field requires selection of an event type numberfrom 0 to 240, to trigger automatic plant configuration backup.

See page 2--1--29 for more information.

Prgm Revision

Displays information about the console software.

Revision level — xx.xxGraphics — PX (Pixel) or CHAR (Character)Language — ENG (English), FREN (French), or

GERM (German)Processor — 68040Console type — MTCC or SMS

Primary Volume For $$PASSWD

Primary drive where the $$PASSWD file resides.Enter up to 10 alphanumeric characters that match a valid disk drivename.

NOTE: A primary name that is blinking in yellow indicates that thisnode has been out of service at some time since configuration.

Print NodeSpecifies the node number to which print requests are sent. Thisshould be the node number of the console to which the printer isconnected. Entries are 0 to 992.


CC: 2-1-15



Field Description

Printer

Specifies the type of printer. This field only applies if the printer isconnected to this node.

D TI810 should be used for the Texas Instruments model 810printer.

D Fujitsu should be used for a Fujitsu printer.

D Other should be used for any other printer.

Reboot Menu(MTCC only)

Specifies the number of the enhanced keyboard software menu thatappears when the console reboots. The menu numbers are from theMENUS menu. This field only applies if “ASCII Keyboard�Enhanced”is configured. For more information about enhanced keyboardsoftware, see OP.

ResetResets the printer subsystem. In addition, you may have to turn theprinter off and on to reset successfully.

To reset the printer, cursor to the field and press [ENTER].

Screen Refresh

Specifies the maximum rate at which the console can request datafrom a controller. Allowable refresh rates are from 0.25 to 20.0seconds. The default refresh rate is 0.25 seconds. Screens refresh isused by the following screens:

D Process Graphics

D Group Display

D Unit DisplayD Overview Display

NOTE: The screen refresh rate can affect the performance of thePeerWay and controller. For more information on Configuring Refreshand Advance Requests Rates, see 2-1-38.

Slot width

Specifies a time width used to tune PeerWay performance.NOTE: Under a password security system, this field is designated withan asterisk (*), and may only be changed by a system manager(sysmgr).

This field must not be changed without thesupervision of Fisher--Rosemount personnel.

Speaker VolumeSpecifies the speaker volume, which is used for audible alarmannunciation, key click, and entry errors at the console. Entries areNone, Low, Med, and High. Press [ENTER] to change the entry.

Tags or Addresses

Specifies whether blocks are identified by tag or by address on screendisplays at this console. Press [ENTER] to change the entry.

D Tags specifies that blocks are identified by tag.

D Addresses specifies that blocks are identified by address.

Tag MaskSpecifies portions of 16--character tags that do not appear on screens.Hiding redundant or extraneous parts of the tag can make it easier forthe operator to identify blocks while viewing screens.


CC: 2-1-16



Field Description

Tag Position The “Tag Position” field appears only when the cursor is resting in the“Tag Mask” field. It specifies the position of that character in the tag.

Tag Row Break Specifies where a tag should be split if the default split is notacceptable.

Tape Auto Load

Specifies whether or not tapes are automatically loaded when inserted.D Yes specifies that tapes are automatically loaded when inserted.

D No specifies that a manual tape load procedure must beperformed to load a tape.

Tape Drive Type

Displays the tape drive on a console acting as a Master Node.Possible displays are:

D RS3*T1 45S (Scorpion qic--24 format)

D RS3*T2 60S (Viper 2060S qic--24 format)D RS3*T3 150S (Viper 2150S qic--150 format)

D RS3*T4 TDC 3660 (Tandberg 3660 qic--150 format)

For more information about tape drive types and specifications, seeDT:1.

This is Node Displays the node number and console type.

Time

Displays the current time on all PeerWay nodes. Changes to oneconsole will change all nodes.

NOTE: Under a password security system, this field is designated withan asterisk (*), and may only be changed by a system manager(sysmgr).

Time Correction

For HIA use only. Used with the highest--addressed operator interfaceon the local Peerway to synchronize the HIA (Highway InterfaceAdapter) tic master. Only a time correction on the tic master affects thesystem.

Title for Login screenTitle for the system login screen.Enter up to 40 alphabetic characters including spaces.

Use Tag Mask Turns masking on or off. If masking is off, link displays show allcharacters in the block tag.

Volume NameDisplays the volume name of the console configuration file that isloaded from the console battery backup memory if the console isrebooted.

CC: 2-1-17


Configuring Access to an Alternate Console Disk over thePeerWay

Purpose

In rare circumstances, a console hard disk may fail. If that happens, youcan still access group displays, but you cannot access displays thatrequire the hard disk, such as process graphics.

However, you may still need to maintain operator control from thatconsole for a short period of time. You can configure a console so that itaccesses an alternate console disk over the PeerWay if its own harddisk fails. You should correct the disk problem as soon as possible.

Configuration

The alternate console disk feature is configured on the ConsoleConfiguration screen (see Figure 2.1.9).

Overlay alternate disk

The overlay alternate disk provides access to overlays. Overlays are thebase structure of most system displays, and are stored on the hard disk.Any console on the PeerWay that is the same console type and isrunning the same console software as the console you are configuringcan be used as the overlay alternate disk.

General (graphic) alternate disk

The general alternate disk provides access to process graphic files. Thegeneral alternate disk can be any disk drive on the PeerWay. Sincegraphic displays use overlays, you must also configure an overlayalternate disk if you want to configure a general alternate disk.

Events that cause a switch to the alternate disk

D When the local console cannot read its hard disk.

D When the user changes the “In Use” field on the ConsoleConfiguration screen to “yes”. This action should only be done ifyou want to test the alternate node.

Events that cause a switch back to the local disk

The local console does not automatically switch back to the local harddisk when the disk becomes available. The console switches back tothe local hard disk when one of the following events occurs.

D When the user changes the “In Use” field on the ConsoleConfiguration screen to “no”.

CC: 2-1-18


D The next disk access after the alternate disk fails.

D When a console configuration is loaded into the local console.

D When the local console restarts.

CONSOLE CONFIGURATION 27-Jul-96 09:44:23

Keyboard Nodes>0 >0 >0 Tag Mask XXXXXXXXXXXXXXXX Tag Position: 16

Keyboard Revisions Use Tag Mask >N >INITIALIZE TAG MASKKBI 4.1TB 4.1 Tag Row Break >0DISPPNLOPTPNL1 1.4 Change Tag Size >NOPTPNL2OPTPNL3

Tape Drive Type RS3*T1 45SBackup Disks

Overlay Backup Node >26 Volume >CS13 In Use>no

General Backup Node >28 Volume >CS17 In Use>no

Keyclass for Loop Tuning >SUPER

Keyclass for Ignore Interlock >SUPER

Field Refresh >0.5 secs Screen Refresh > 1.0 Advance Requests >3

FULL CONFIG 1

Specifies an alternate disk foroverlays. Enter either the nodenumber or the volume name.

The alternate disk node must berunning the same console softwareas the local node.

- To call up:D [PAGE AHEAD] from Console Configuration

screen, Page 1.

D [PAGE BACK] from Menu CommandConsole.

- To access other screens:D [PAGE AHEAD] to see Menu Command

Console.

D [PAGE BACK] to see page 1 of theConsole Configuration screen.

Specifies an alternate disk forprocess graphics files. Entereither the node number or thevolume name.

Indicates whether or not the alternatedisk is in use (yes, no). You can alsochange the entry manually.

Figure 2.1.9. Access to Alternate Console Disk over the PeerWay

CC: 2-1-19


Configuring Consoles to Switch Keyboard Control

Consoles can be configured so that keyboard control can be switchedamong other consoles on a PeerWay. The keyboard switching isconfigured from the Console Configuration screen.

Figure 2.1.10 shows two sample switching configurations. The [CRT]button is used to switch keyboard control.

- To call up the Console Configuration screen:

1. Call up the Command Console Configuration screen, type

CCC [ENTER] at the command line.

2. Press [PAGE AHEAD] to call up page 2 of the ConsoleConfiguration screen.


Keyboard Nodes � 26 � 28 � 0


Keyboard Nodes � 28 � 30 � 26

In this example, the keyboards can be switched between nodes 28, 30, and 26.If [CRT] is pressed at a keyboard controlling node 30, control is switched to node 26.When [CRT] is pressed again, control is switched to node 28. If [CRT] is pressedagain, control is switched back to node 30.

In this example, the keyboards can be switched between nodes 26 and 28. An entryof 0 is configured in the unused field.

If [CRT] is pressed at a keyboard controlling node 26, control is switched to node28. When [CRT] is pressed again, control is switched back to node 26.

Figure 2.1.10. Console Configuration Screen Switch Keyboard Examples

CC: 2-1-20


Configuring 16-Character Block Tags

RS3 software can accept ControlBlock tags and I/O block tags up to 16characters, as well as only 8 character tags or fewer. The longer tagsallow you to use more descriptive tags to name blocks. The longer tagscan improve the operator interface.

As you work with the tags over eight characters, keep in mind:

D Tags are never truncated by the system. (However, a configurorcan specify a mask that causes a tag to appear truncated.)

D All printed output (other than screen prints) shows complete,unmasked tags. This feature ensures that printed recordsindicate the exact block to which a tag refers.

Tags Affected

ControlBlock tags and I/O block tags are the only tags that can use 16characters. The Batch subsystem and the PLC and SMART controllersuse the term tag; however, these tags will remain 8 characters long.

Splitting and Masking Tags

The longer tags give you as configuror more flexibility in designing tags.Two options on the Console Configuration screen, splitting tags andmasking tags, provide additional flexibility.

Splitting tags

On a few screens, tags are automatically split to fit on the screen. Youcan override the default split and specify a split that makes your tagseasier to read and understand.

Masking tags

You might decide that not all information in a longer tag needs to bedisplayed at all times. You can specify that part of the tag be masked ondisplays to improve readability.

CC: 2-1-21


Taking Advantage of Masking and Splitting Options

As you design 16-character tags, you can use the new configurationoptions most effectively if you keep these hints in mind:

D Devise tags that will split to separate general plant information onone line, and specific device information on the other. To controlthe split, use spaces, hyphens, or periods within the first 8characters of a tag; or combine spaces with masking. (See “SplitTags” on page 2-1-22 and “Masking Tags” on 2-1-24)

D Put repeated information in the same location in every tag. Thatway you can mask the redundant information, and highlightspecific devices. (See “Masking Tags” on 2-1-24)

D Put information that might confuse operators or prevent themfrom taking quick action in the same location in every tag. Theconfusing information can be masked. (See “Masking Tags” on2-1-24)

D Structure tag names so they are concise and useful for everydayplant operation.

D Avoid trailing spaces.

CC: 2-1-22


Split Tags

On a few displays, 16-character tags are split to make them fit on thescreen. Tags are split into two rows of up to 8 characters each, onebelow the other.

Where Tags Are Automatically Split

The software applies the following default rules when it splits tags:

D Tags of 8 or fewer characters are centered and displayed on oneline.

D Tags of more than 8 characters are split at the first space, period,or hyphen that is found by scanning backwards from the eighthcharacter.

D If no space, period, or hyphen is found, or if a split using themwould result in a second line of more than 8 characters, then thefirst line is filled with 8 characters and the remaining charactersare centered on the second line.

D Each row of a split tag is centered.

D A tag row break configured on the Console Configuration screentakes precedence over a split defined by these rules.

Figure 2.1.11 shows examples of tags split using these rules.

12345678blower--228

blower-228

Tag Text:

Split TagAppearance:

plant 7 fan 3 STK1--A11Sensor 2 valve.flowfan 24

12345678plant 7fan 3

12345678STK1--A11Sensor 2

12345678fan 24

12345678valve.flow

Figure 2.1.11. Examples of Split Tags

CC: 2-1-23


Specifying Where to Split Tags-Tag Row Break

You can choose to override the default tag splitting rules and specify acharacter position where tags should be split. Figure 2.1.12 shows anexample of splitting character tags.

NOTE:1. If the position you specify would make the second line of the tag

longer than 8 characters, the default tag--splitting rules are usedinstead.

2. The character position used by the system is based on theunmasked tag. (See “How Masking and Splitting Interact” onpage 2-1-27 .)




Tape Drive Type: RS3*t3 150S (qic-150)Backup Disks





Graphic Refresh >0.5 secs Screen Refresh > 1.0 Advance Requests >3

FULL CONFIG 1

- To save the configuration:D When you finish configuring tag splitting and

tag masking, be sure to save yourconfigurations on disk (in the CC file).For specific steps, see DT: 2--4.

- To call up, type:1. CCC [ENTER] at the command line.

2. [PAGE AHEAD] from Console Configurationscreen to display page 2.

- To specify where to split the tag:1. Cursor to the “Tag Row Break” field.

2. Type a number from 1 to 8 and press[ENTER].The number represents a characterposition from 1 to 8 starting from the left.The number 0 is the default, and can betyped in this field, but causes tags to splitusing the default tag--splitting rules.

Tags will now split following the positionyou typed.

Figure 2.1.12. Splitting Character Tags

CC: 2-1-24


Masking Tags

At each console, you can specify that portions of 16--character tags donot appear on screens. By temporarily hiding redundant or extraneousparts of the tag, this feature can make it easier for the operator toidentify blocks while viewing screens. (Note that the operator can togglebetween viewing the masks or not by using the TTM command. See“Turning Masking On and Off” on page 2-1-26.)

Where Masking Does Not Apply

Masking affects only displays, and applies in almost all cases. It doesnot apply in the following instances:

D The full 16--character tag must be typed in all enterable fields.(That is, you cannot type just the unmasked portion of the tag ina field that requires you to enter a tag.)

D The tag of the block being configured is not masked onconfiguration screens. Examples include continuous and discreteControlBlock:— Faceplate displays— Diagram displays— Link displays

D Tags are not masked on printed output (other than screen prints).This includes:— Alarm lists— Reports— Batch reports— RBL script listings

CC: 2-1-25


Specifying a Mask

You can specify or modify a mask on the Console Configuration screen.Figure 2.1.13 shows an example of masking character tags.

If you are not satisfied with the mask for some reason, you can initializethe mask to return it to the default setting and start over.




Tape Drive Type RS3*T1 45SBackup Disks





Graphic Refresh >0.5 secs Screen Refresh > 1.0 Advance Requests >3

FULL CONFIG 1

- To save the configuration:D When you finish configuring tag splitting and

tag masking, be sure to save yourconfigurations on disk (in the CC file).For specific steps, see DT: 2--4.

- To call up, type:1. CCC [ENTER] at the command line.

2. [PAGE AHEAD] from Console Configurationscreen to display page 2.

- To Mask the tag:1. Cursor to the “Tag Mask” field.

2. Place the cursor on a character positionthat you want hidden and press [ENTER].(The character position is indicated in the“Tag Position” field.)

The character position appears in normalvideo, indicating that the position willappear blank on displays.

To unmask a masked (normal video)character position, cursor to that positionand press [ENTER].

3. Repeat step 4 until you are satisfied withthe mask.

- To initialize the mask:D Cursor to the “Initialize Tag Mask” field and

press [ENTER]. The “Tag Mask” field is reset toits default state in which no characters aremasked.

Figure 2.1.13. Masking Character Tags

CC: 2-1-26


Turning Masking On and Off

Both configurors and operators can turn masking on and off. Use eitherof two methods to toggle between masking and no masking.

- To toggle between masking and no masking:

D From page 2 of the Console Configuration screen, cursor to the“Use Tag Mask” field and press [ENTER]. (The value in this fieldis saved as the new default setting when you save yourconfiguration.)

or

D From the command line, type TTM (for Toggle Tag Mask) andpress [ENTER].

CC: 2-1-27


How Tag Splitting and Masking Interact

Tag splitting and masking interact to produce the tag display. When thesoftware splits and masks tags, it applies the following rules in thefollowing order:

1. If you specified a character position in the “Tag Row Break” field,tags are split accordingly.

2. If you specified a mask, the tags are masked.3. If you did not specify a character position in the “Tag Row Break”

field, the default tag splitting rules are applied.Figure 2.1.14 shows examples of splitting and masking.

1234567890123456XXXXXXXXXXXXXXXX




12345678STK1-A1Sensor 2

Example 1: Example 2:

Example 3: Example 4:

Tag

Tag Mask

Tag splitwith mask off

Tag splitwith mask on

Tag

Tag Row Break: none specified

Tag Mask



Tag

Tag Mask



Tag

Tag Mask



1234567890123456STK1-A1Sensor 2

1234567890123456STK1-A1Sensor 2

1234567890123456STK1 Sensor A

1234567890123456STK1-Valve AB2

Tag Row Break: position 7

12345678STK1-A1Sensor 2

12345678A1Sensor 2

12345678Sensor 2

12345678STK1

Sensor A

12345678Sensor A

12345678STK1-Valve AB2

12345678ValveAB2

Tag Row Break: position 7

Tag Row Break: none specified

Figure 2.1.14. Interaction of Tag Splitting and Masking

CC: 2-1-28


Automatic Backup Functions

You can elect to have RS3 automatically backup your consoleconfiguration and/or your plant configuration through the ConsoleConfiguration screen display or command line options.

Automatic Console Configuration Backup

Automatic console configuration backup assures you that the consoleconfiguration will be backed up automatically in accordance with auser-established event trigger; and frees you from having to perform theoperation manually.

Automatic console configuration backup triggers the Disk Console Saveoperation (Disk Activity screen), on an event basis. You can enable anddisable automatic console configuration backup by toggling betweenEnable/Disable on the Console Config field on the ConsoleConfiguration display (see Figure 2.1.6), or by using the ECB (EnableConsole Config Backup) and DCB (Disable Console Config Backup)command line options, respectively.

Before enabling this function, you need to configure a destinationfilename in the Destination File field and select an event type in theEvent Type field. Event type field numbers are from 0 to 240, and theevent selected triggers the automatic backup. Messages are displayedif the destination filename is not configured or the event type entered isnot valid.

When the specified event occurs, a 15-second countdown warningmessage is displayed on the Disk Activity screen. After 15 seconds, theDisk Console Save operation is executed internally, saving consoleconfigurations of all types. During the save operation, an in-progressmessage is displayed on the Disk Activity screen. You cannot executeanother operation until this operation completes.

If another operation is currently in progress, the console configurationbackup operation is not executed immediately, but is stored in a queueand executed upon the completion of the current operation.

Note that this capability is automatically turned off upon power up orreset.

CC: 2-1-29


Automatic Plant Configuration Backup

Automatic plant configuration backup assures you that the plantconfiguration will be backed up automatically, in accordance with thebackup plant config file and a user-established event trigger; and freesyou from performing the backup manually.

You can backup groups of nodes within various PeerWays in the systeminto destination files with a specific destination filename, all within onesave operation. You can also maintain multiple revisions of a particularplant configuration.

Automatic plant configuration backup triggers the Disk Cont Save orBackup operation (Disk Activity screen). You can enable or disableAutomatic Plant Configuration Backup by toggling betweenEnable/Disable on the Plant Config field on the Console Configurationdisplay (see Figure 2.1.6), or by using the EPB (Enable Plant ConfigBackup) and DPB (Disable Plant Config Backup) command line options,respectively.

The Backup File field always specifies $$BACKUP as the backup file.Before you enable the automatic plant config backup operation, youmust create a backup plant config file, using the BackUp Plant Config(BUP) command line option. See DT: Chapter 2, Section 4 for moreinformation.

If you have not created a backup plant config file before enablingautomatic plant configuration backup, a banner message will bedisplayed. Note that you cannot modify the backup plant config file whilethe backup plant configuration capability is enabled.

You will also need to select an event type in the Event Type field. Eventtype numbers are from 0 to 240, and the event selected triggers theautomatic backup. If the event type entered is not valid, a bannermessage will be displayed.

When the specified event occurs, a 15-second countdown warningmessage is displayed on the Disk Activity screen. After 15 seconds, theDisk Cont Save or Backup operation is executed internally, inconjunction with the backup plant config file. During the backupoperation, an in-progress message is displayed on the Disk Activityscreen; you cannot execute another operation until this operationcompletes.

If another operation is currently in progress, the plant configurationbackup operation is not executed immediately, but is stored in a queueand executed upon the completion of the current operation.

You can abort the plant configuration backup while it is in progress,using an APB (Abort Plant Config Backup) command line option. Theoperation will terminate when the current node being backed up hascompleted.

CC: 2-1-30


You can also manually execute the Disk Cont Save or Backup operationfrom the Disk Activity screen display using a backup plant config file.

Note that the automatic plant configuration backup capability isautomatically turned off upon power up or reset.

Customizing the Plant Configuration Backup

You can customize the backup of plant configurations using the BackUpPlant Config (BUP) command line option, which displays the BackupPlant 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.

For more information, refer to the Disk and Tape Manual, DT: 2--4--10.

CC: 2-1-31


Node Ownership and Plant Unit Ownership

Node ownership and plant unit ownership are defined at each console.These two features work together to determine:

D Which blocks, batch tasks, and nodes the console can configureand control, and

D Which alarms the console stores.

Table 2.1.3 shows how node ownership and plant unit ownership worktogether.

Table 2.1.3. How Node Ownership and Plant Unit Ownership Work Together

If... then... only if the console...

a block or batch task has anon--zero plant unit number,

the console stores alarms fromthe block or task, and canconfigure and control the block ortask,

owns the plant unit number.

a block or batch task has a plantunit number of zero,

the console stores alarms fromthe block or task, and canconfigure and control the block ortask,

owns the source node.

the source is not a block or batchtask,

the console stores alarms fromthe source, and can configureand control the source,

owns the source node.

CC: 2-1-32


Configuring Node Ownership

Node ownership is configured on the Plant Status screen(See Figure 2.1.15)

PLANT STATUS 24-Jul-96 07:30:45

First Node Listed> 1 Peerway Number> ALLNode Type Displayed > OWNED AND EXISTING NODES

Node Node Node Node1 CTL Norm 20 MTCC

2 MTCC 22 MTCC

4 ?CC 26 MTCC

6 MTCC 28 MTCC

8 SMS 30 ?SRU

10 CTL Norm

12 MTCC

16 MTCC

Displays the node type:CC Pedestal Command ConsoleCTL ControlFileDI Diogenes InterfaceHIA Highway Interface AdapterMC MiniConsoleMTCC Multitube or Hardened

Command ConsoleRFI Rosemount Factory InterfaceRNI RS3 Network InterfaceSCI Supervisory Computer InterfaceSMS System Manager StationSRU System Resource UnitVAX MicroVAX to Peerway Interface

PeerWay number ofdisplayed nodes.

Specifies the types of nodes displayed. Use the[NEXT OPTION] button to step through thechoices.

- To own a node:An owned node is backlighted. Cursor tothe field and press [ENTER] to togglebetween the owned and not-owned state.

- To call up, type:D PS [ENTER] at the command line

D [PEERWAY STATUS]

D [EXCH] from PeerWay Overview

- To access other screens:D [EXCH] to see PeerWay Overview

Note: A node type preceded by a “?” meansthat the node type is no longer supported.

Figure 2.1.15. Plant Status Screen

CC: 2-1-33


Configuring Plant Unit Ownership

Plant unit ownership is configured on the Plant Unit Configurationscreen (see Figure 2.1.16).

PLANT UNIT CONFIGURATION 23-Jul-96 11:47:12

1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 2412 18 34 50 66 82 98 114 130 146 162 178 194 210 226 2423* 19 35* 51 67 83 99 115 131 147 163 179 195 211 227 2434* 20 36 52 68 84 100 116 132 148 164 180 196 212 228 2445* 21 37 53 69 85 101 117 133 149 165 181 197 213 229 2456* 22 38 54 70 86 102 118 134 150 166 182 198 214 230 2467 23 39 55 71 87 103 119 135 151 167 183 199 215 231 2478 24 40 56 72 88 104 120 136 152 168 184 200 216 232 2489 25 41 57 73 89 105 121 137 153 169 185 201 217 233 24910 26 42 58 74 90 106 122 138 154 170 186 202 218 234 25011 27 43 59 75 91 107 123 139 155 171 187 203 219 235 25112 28 44 60 76 92 108 124 140 156 172 188 204 220 236 25213 29 45 61 77 93 109 125 141 157 173 189 205 221 237 25314 30 46 62 78 94 110 126 142 158 174 190 206* 222 238 25415 31 47 63 79 95 111 127 143 159 175 191 207 223 239 25516 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256

Set range �3,6 Clear range �

CONFIG 4

Owned plant units are followed by *.

- To call up:D PUC [ENTER] at the command line.

D [SELECT] from “Unit Ranges” field onArea Name Configuration.

- Access other screens:D None

- To own a single plant unit:D Cursor to the plant unit number and

press [ENTER] to toggle betweenthe owned and not-owned state. Anowned plant unit number is followedby *.

- To own a range of plant units:D Cursor to the “Set range” field, type a

range of numbers separated by a comma(for example “3,6”), then press [ENTER].

- To no longer own a range of plant units:D Cursor to the “Clear range” field, type a

range of numbers separated by a comma(for example “3,6”), then press [ENTER].

Figure 2.1.16. Plant Unit Configuration Field

CC: 2-1-34


Operator Change Log

The Operator Change Log is a record of operator activities at the localconsole and at any nodes owned by this console. Activities includechanges made to the block mode, setpoint, inputs, outputs, andadjustable parameters, as well as key insertion and withdrawal. Inpassword systems, login name or user number replace the source andkey fields. The Operator Change Log screen cannot be altered.

To log an activity, the console initiating the activity must have a keyinserted, and the “Op Chg” field of the Console Configuration screenmust be configured as “Enable”.

The Operator Change Log is stored in console RAM. The size andprinting properties of the Operator Change Log are configured on theAlarm List Configuration screen (see 6-3-8).

Figure 2.1.17 shows an example of this screen with field descriptions. Itshows the screen as seen in keylock systems, password systems, andfor SCI and QBI. Note the following:

D The Source, which states the type of console, the node number,and the key value, are not listed when the login names areidentified.

D The Login Name field shows all 16 characters of the login nameif all 16 are used. Other screens show only the first eightcharacters.

D For password systems, the Login Name field appears in place ofthe Key field. If the value in the Key field is 2, then the precedingnumber is a user number and not a node number.

D The batch log now shows the name of the user instead of the keyvalue.

CC: 2-1-35


MakeConsoleKeylock System* OPERATOR CHANGE LOG 12-Mar-96 11:01:41

--Occur---PU------Location-----Parameter----Old------New-----Login Name-------------------------- 12-Mar-9611:00:45 175 :=49A-15/PV Input A .00 .60 kenta11:00:13 175 :=49A-17 Block Mode AUTO MANUAL kenta11:01:28 0 Login Change kenta No User11:01:28 0 Login Change ******* *******10:59:40 175 :=49AA502 Block Mode AUTO MANUAL joew10:59:33 175 :=49AA502 Block Out .00 .50 joew

Occur PU Location Parameter Old New User No.-------- ---- ---------------- ------------ -------- -------- ------- --------

11:00:45 175 >=49A-15/PV Input A .00 .60 2

OPERATOR CHANGE LOG 25-Jul-96 12:07:37

Occur PU Location Parameter Old New Source Key

14:46:34 1 :PIC-112/LS Input B .0 35.0 CC=4 OPER 614:46:26 104 :PIC-112 Block Mode LOCAL AUTO CC=4 OPER 614:45:45 0 :FIC-104/LS Input B .0 55.0 CC=4 OPER 614:44:59 0 :PIC-104/LS Input B .0 55.0 CC=4 OPER 614:44:27 0 Oper Chged Key No Key OPER 6 CC=414:44:20 0 Oper Chged Key CONFIG 3 35.0 CC=420:42:29 0 :FQ-32708 Block Mode AUTO MANUAL CC=4 CONFIG 3

* End *

Occur = Time that the activity occurredPU = Plant unit

Location = ControlBlock tag

Parameter = Block parameter that was changed

- To call up, type:D OL [ENTER] from the command line.

D [PAGE AHEAD] from Event List 10.

- To access other screens:D [PAGE BACK] to see Event List 10.

Old = Initial value of the block parameterNew = New value of the block parameter

Source = Console type and node of theconsole initiating the activity

Key = Key type (operator, configuror,supervisor) and number

Screen Layout with Keylock System

Screen Layout with a Password System

Login Name = User name asconfigured on theUser Name DetailScreen

User No. = User Number asconfigured onUser NameDetail Screen

Screen Layout with an SCI or QBI Interface

Figure 2.1.17. Operator Change Log Screen Entries

CC: 2-1-36


Hints for Configuring Console Operations

This section discusses some problems that you may encounter whenconfiguring console operations, along with some helpful configurationtips.

Configuration Problems

Listed below are possible problems that might occur when configuringconsole operations along with possible solutions.- There is no console speaker sound even though I have a

“Speaker Volume” configured.“Alarm Speaker�yes” must be configured on the ConsoleConfiguration screen to get any sound.

- After I mark a screen for recall and then recall the screen once,I can’t recall the screen again.The mark function only lets you recall a screen once.

- The printer does not reset after I perform the reset function.To reset a printer fully, you may have to turn the printer off and on.To reset a printer from a console node that is not connected to theprinter, the console you are at must own the console node that isconnected to the printer.

- My alarm lists don’t print at the right print node.Alarm lists print at the print nodes specified on the Alarm ListConfiguration screen.

- The printer is functioning properly, but I can’t get a consolescreen print.The cause of this problem could be one of many sources:

— Call up the Console Configuration screen and see if you havethe correct “Print Node” field entry.

— If the “Print Node” field is backlighted, you need to restore theprinter. Call up the Alarm List Configuration screen, cursor tothe “Restore Primary Printer Nodes” field, and press[ENTER].

— You may need to reset the printer.- The “Print Node” field on the Console Configuration screen is

backlighted.You need to restore the printer. Call up the Alarm List Configurationscreen, cursor to the “Restore Primary Printer Nodes” field, andpress [ENTER].

CC: 2-1-37


Configuration Tips

- How to configure the printer for specific tasks

Table 2.1.4 lists configuration parameters for some useful printerinstructions.

Table 2.1.4. Printer Interface Instructions

Task Performing the Task

To print alarm and event lists.

1. Set “FF” to yes.2. Set “L/Pg” to 66 (for 8 1/2 by 11

paper) or 69 (for A4 or 210 by 297mm paper).

To print blocks or full screens (two screens per page).

1. Set “FF” to no.2. Set “L/Pg”to 33 (for 8 1/2 by 11

paper) or 34 (for A4 or 210 by 297mm paper).

To generate a print request to a remote printer. (This featurerequires that a modem be connected to the printer port.)

Set “Autodial” to yes. When “Autodial” isset to yes, the “Dial�” field comes up toindicate that a phone number (xxx--xxxx)should be entered.

To designate the type of printer being used. Enter an option in the “Printer” field.

To set the console communication rate between the consoleand the printer.

Enter an option in the “Baud” field. Theentry must match the communicationrate set at the printer. The recommendedrate for TI--810 and Fujitsu printers is4800.

CC: 2-1-38


Configuring Refresh and Advance Request Rates

The following fields control the rate at which console graphics and blockdisplays can request data from controller processors:

D Screen Refresh Rate

D Field Refresh Rate

D Advance Request

Refresh rate differs from advance request in that refresh rate specifieshow often request messages are generated, whereas advance requestspecifies how many request messages can be generatedsimultaneously. However, when used improperly, both refresh rate andadvance request can have a similar disruptive effects on systemperformance. By generating too many messages too fast, high advancerequest and refresh rates have the potential to flood the PeerWay andoverwhelm the Coordinator Processor (CP) and controller processors.

Optimum communications between consoles, CPs, and controllerprocessors require a balance between refresh rate and advancerequest. The appropriate balance varies depending on the configurationand demands of the system. For every system condition, there is themaximum rate at which the console and controller processor cancommunicate without causing disruption or drain on PeerWayresources. As a general rule, you should use the lowest refresh rate andadvance request number that your system can efficiently accommodate.Some experimentation may be required to find the optimum values.

CC: 2-1-39


Screen Refresh Rate

Screen refresh refers to the maximum rate at which a console canrequest data from a controller for refreshing the following screens:

D Process Graphics

D Group Display

D Unit Display

D Overview Display

A console requests data by generating request messages. The refreshrate enables you to slow the generation of request messages to bettermatch processing speed of the controller or prevent multiple consolesfrom overloading a single controller with data requests.

If the screen refresh rate is too high, these screens will request inputdata faster than the scan time of the controller processor; that is, therate at which the controller can process and update data. At best, thissituation is an inefficient use of memory; at worst, it is a potentiallydisruptive situation in which excessive messages can flood thePeerWay and overwhelm the CP and controller processor.

Allowable screen refresh rates are from 0.25 to 20.0 seconds. However,if the Controller cannot respond to data requests at the specified refreshrate, the actual refresh rates will be slower. A screen cannot refreshuntil it has received data for all data points requested. A generalrecommendation is to use the slowest refresh rate your process canaccommodate (1 to 2 seconds or slower for infrequently used consoles).

The optimum refresh rate depends on the configuration and peakdemand of your system.

CC: 2-1-40


Field Refresh Rate

The field refresh is used as a supplement to screen refresh forrefreshing individual objects on process graphic displays. The object orfield is refreshed by positioning the cursor on it.

The field refresh rate gives you a means for controlling the refresh rateof individual objects on the graphic. You typically want to use a fasterspeed for the field refresh rate than for the screen refresh rate. A fastfield refresh rate for a single object is less likely to upset processperformance than a fast screen refresh rate for an entire graphic.

Allowable field refresh rates are from .5 to 4 seconds. However, fieldrefresh rate should meet two criteria:

D The field refresh rate should be at least a half of a second fasterthan the screen refresh rate. For example, a field refresh of 0.5will offer little advantage over a screen refresh rate of 0.75.

D The field refresh rate should not exceed the scan time of thecontroller processor. Otherwise, the console will generaterequest messages faster than the controller processor canrespond.

The advance request number specifies the maximum number ofoutstanding data request messages that a console can send to acontroller at one time. Each time the console receives a reply to anoutstanding message, it can generate another message to bring thenumber of outstanding messages back up to the number specified bythe advance request.

A single request message can contain data requests for multiple linksfor the same controller processor. For example:

=1A--2=1A--3

=1A--53=1A--45

However, a request message cannot contain multiple data requests fordifferent controller processors. For example:

=1A--2=1B--54=31C--5

CC: 2-1-41


From a practical point of view, advance request specifies the number ofController Processors with which a graphic or group display cancommunicate simultaneously. Allowable advance request numbers arefrom 1 to 5 (the default is 3). This means that a console cancommunicate with up to 5 controllers at a time. A high advance requestnumber may be advantageous on a small system where only oneconsole communicates with several Controller Processors. However, ona large system where multiple consoles access the same controller, ahigh advance request number can overwhelm the CP and ControllerProcessor with excess messages.

NOTE: An advance request number of 1 or 2 will enable a console toadapt to system slowdowns caused by communications acrossPeerWays and loading of CP and Controller processor images.

Figure 2.1.18 shows how the advance request number determinesoutstanding data requests.

CC: 2-1-42


=1B--54PeerWay

PeerWay

=1B--45

=31C--1

=31C--2

=1A--45

Refresh AdvanceRate Request

1 second 2

Process Graphic

Queue(outstandingmessages)

Message #1

Message #2

Queue(outstandingmessages)

Message #2

Message #3

NOTE:D The specified advance request allows 2 outstanding messages.

D As each outstanding message is answered, the queue frees up space for a newmessage.

D The screen refresh rate is 1 second. The process graphic must receive data for alllinks before it can begin a new refresh cycle.

=1A--2

=1A--53

=1A--3

=31C--5

=31C--10

=1B--45

=31C--1

=31C--2

=1A--45

Process Graphic

=1A--2

=1A--53

=1A--3

=1B--54

=31C--5

=31C--10

CONTROLLER

CONTROLLER

Figure 2.1.18. Advance Request Concept

CC: 2-2-1

RS3: Configuring Operating Characteristics Configuring Color

Section 2:Configuring Color

Console screen colors are configurable. The Master Color Selectionscreen is used to configure the foreground and background colorcombinations used in the system. The Color Configuration screens areused to assign the color combinations to system display componentssuch as alarms, variables, and screen titles.

This section describes how to configure the Master Color Selectionscreen and Color Configuration screens.

CC: 2-2-2


Master Color Selection Screen

The background/foreground color combinations are configured on theMaster Color Selection screen. Figure 2.2.1 shows an example of aMaster Color Selection screen with default colors.

MASTER COLOR SELECTION 14-Jul-96 10:11:05

Foreground Background Foreground Background

1 �white �high �black �low 9 �brown �high �black low

2 �green �high �black low 10�lt green �high �black low

3 �blue �high �black low 11�yellow �high �black low

4 �cyan �high �black low 12�aqua �high �black low

5 �magenta �high �black low 13�gray �high �black low

6 �orange �high �black low 14�tan �high �black low

7 �salmon �high �black low 15�red �high �black low

8 �purple �high �black low 16�black �low black low

CONFIG 3

A color combination is configured as foreground color (thetext color) and background color (the screen color). Sixteencolor combinations can be configured. Background colorsmust be chosen from the configured foreground colors. As anexample, blue cannot be used as a background color unlessblue is configured as one of the sixteen foreground colors.

In addition to the colors listed on the screen, these colors arealso available:

blue--2 cyan--2 salmon--2 aqua--2 orange--2

Color intensity is adjusted for a high,med, or low level. Each foregroundcolor has an individual intensityadjustment. The backgroundintensity of a color matches theforeground intensity of that color.

- To call up, type:D CCP [ENTER] at the command line.

D [PAGE AHEAD] from the last ColorConfiguration.

D [PAGE BACK] from the first ColorConfiguration.

- To access other screens, type:D [PAGE AHEAD] to see the first Color

Configuration.

D [PAGE BACK] to see the last ColorConfiguration.

Figure 2.2.1. Master Color Selection Screen

CC: 2-2-3


Color Configuration Screens

Color Configuration screens are used to assign color combinations tosystem display components, such as alarm messages and consolescreen titles. Figure 2.2.2 shows an example of a Color Configurationscreen. Table 2.2.1 describes the system display components on theColor Configuration screens.

COLOR CONFIGURATION 14-Jul-96 10:30:45

Color Usage ColorNormal Reverse

1n white 1r black Date �2n2n green 2r black3n blue 3r black Default Values �2n4n cyan 4r black5n magenta 5r black Cursor/Prompt/Entry �10n6n orange 6r black7n salmon 7r black Events �2n8n purple 8r black9n brown 9r black System Alarms �1n10n lt green 10r black11n yellow 11r black Advisory Alarms �11n12n aqua 12r black13n gray 13r black Critical Alarms �15n14n tan 14r black15n red 15r black Hardware Alarms �5n16n black 16r black

Batch Alarms �6n

CONFIG 3

Colors are assigned or changed in the“Color” field. In this example, alladvisory alarms are assigned colorcombination 11n, yellow text on a blackbackground.

The color palette is shown on every ColorConfiguration screen as a reference.

The Color Usage list changes foreach Color Configuration screen.

- To call up:D CCU [ENTER] at the command line.

D [PAGE AHEAD] from Master Color Selection.

- To access other screens:D [PAGE AHEAD] to see other Color

Configuration screens.

D [PAGE BACK] to see Master ColorSelection.

Figure 2.2.2. Color Configuration Screen

CC: 2-2-4


Table 2.2.1. Color Configuration Screen Fields

Color Usage Field Name Description Default Color

1st screen

Date Date displayed in the upper right corner of screen. 2n

Default Values Enterable fields on the console screens. 2n

Cursor/Prompt/Entry Cursor. 10n

Events Operator logs, event lists. 2n

System Alarms System alarm messages. 1n

Advisory Alarms Advisory process alarm messages. 11n

Critical Alarms Critical process alarm messages. 15n

Hardware Alarms Hardware alarm messages. 5n

Batch Alarms Batch alarm messages. 6n

2nd screen

Process Variables The A input of a ControlBlock. 2n

Setpoints The B input of a ControlBlock. 4n

Remote Setpoints The C input of a ControlBlock. 8n

Feed Forward The D input of a ControlBlock. 14n

Output Value The Q output of a ControlBlock. 6n

Input E The E input of a ControlBlock. 2n

Input F The F input of a ControlBlock 2n

Input G The G input of a ControlBlock. 2n

Input H The H input of a ControlBlock. 2n

3rd screen

Auto Mode Auto mode on blocks. 2n

Manual Mode Manual mode on blocks. 2n

Remote Mode Remote mode on blocks. 2n

Local Mode Local mode on blocks. 2n

Computer Mode DDC or Comp SP mode on blocks. 2n

Trend Color 1* Color 1 on all trend group displays. 5n

* Does not appear on an SMS.


CC: 2-2-5


Table 2.2.1. Color Configuration Screen Fields (continued)

Color Usage Field Name Default ColorDescription




4th screen

Continuous Function Not used. 9n

Discrete Function Not used. 13n

Sub-Title Color Group titles on unit and overview operating displays. 6n

Message-pair Color 1 C1 on a STD or a User Message Pairs screen. 2n






5th screen

Arbitrary Color Outline color for a selected key on the keypad of theDisplay Buttons screen. 2n

I/O Block Mode 1 Not used. 1n



Screen Titles The name of the console screen. 8r

Report Color 1* Report configuration fields on a Report Configurationscreen. 4n

Report Color 2* Report body on a Report Configuration screen. 12n

Report Color 3* Window on a Report Configuration screen. 11n

Report Color 4* Not used. 7n

6th screen

Graphics View Background* Background on a Process Graphic screen. 4n

Graphics View Select Outline* Outline of the selected Process Graphic screen. 6n



CC: 2-2-6


Table 2.2.1. Color Configuration Screen Fields (continued)

Color Usage Field Name Default ColorDescription

Graphics Config Background* Grid on the Process Graphic Generation screen. 10n

Graphics Config MenuWindow* Menu window on the Process Graphic Generation screen. 11n

Graphics Config AreaBackground*

Background color on the Process Graphic Generationscreen. 11r

7th screen

Batch Program Batch program line after it has been entered. 1n

Batch Error An incorrect line entry. 15r

Batch Modified Batch line currently being typed. 11r

Batch End End of the batch script. 3r

Batch Current Line Currently executing batch line. 4r

Batch Comments

Comments of batch script. This entry only takes effectwhen the Batch Program color is 1r. If the Batch Programcolor is anything else, then the batch comments are thesame color as the Batch Program color.

6n

8th screen

ABC Icon Complete* Execution of recipe icon complete. 2n

ABC Icon Active* Currently executing recipe icon. 11n

ABC Icon Not Started* Recipe icon has not been executed. 4n

ABC Icon Error* A recipe icon runtime error. 15n

ABC Icon Skipped* Recipe icon skipped without executing. 12n

ABC Icon Highlight* Recipe icon highlighted with [SELECT] key. 1n

ABC Static Node Mark* Recipe execution complete up to mark. 15n

ABC Block Step Mark* Recipe execution blocked at mark. 6n

9th screen

Inhibit Alarms Block tags that are inhibited at the block level. 7n

Disable Alarms Block tags in alarm areas that are disabled. 13n

Suppressed Alarms Block tags and alarms that are suppressed. 12n

Plant Unit Plant unit numbers on Plant Unit Configuration screen. 2n


CC: 2-2-7


Hints for Configuring Colors

This section discusses problems you may have when configuringcolors.


- Why can’t I get black as a background color?

On the Master Selection screen, black must be configured as aforeground color in order to use it as a background color.

CC: 2-2-8


CC: 2-3-1

RS3: Configuring Operating Characteristics Configuring Operating Displays

Section 3:Configuring Operating Displays

This section shows how to configure operating displays. Operatingdisplays contain ControlBlock faceplates, which facilitate operatorcontrol and monitoring of processes. A faceplate often represents acontrol loop.

D Group displays contain up to 8 faceplates. Plant processes canbe controlled and monitored from group displays.

D Unit displays contain up to 4 groups (up to 32 faceplates). Plantprocesses can only be monitored from unit displays.

D Overview displays contain up to 2 units (up to 64 faceplates).Plant processes can only be monitored from unit displays.

CC: 2-3-2


Configuring Group Displays

D Group display titles are configured on the Group Directoryscreen.

D Groups are configured on the Group Display screens.

Group Directory Screen

The Group Directory screen shows the list of group displays. Groupdisplay titles must be configured on the Group Directory screen.Figure 2.3.1 gives an example of a Group Directory screen.

GROUP DIRECTORY 25-Jul-96 12:20:11

Group Title Group Title Page 1

1 �PLANT MASTER 11 �

2 �1 BOILER CONTROL 12 �

3 �2 BOILER CONTROL 13 �

4 �8 STOKER CONTROL 14 �

5 �2 FUEL CONTROL 15 �

6 � 16 �

7 � 17 �

8 � 18 �

9 � 19 �

10 � 20 �CONFIG 1

D Groups 1--80 for MiniConsoles;groups 1--200 for command consoles.

D Group titles 71--80 on MiniConsolesand 181--200 on command consolescan be configured with an operatorkey.

D A title can contain up to 20 characters,including spaces.

D If no title is listed, “Group #” isdisplayed at the top of the GroupDisplay screen.

D To delete a title, press [ENTER].

- To call up, type:D GD: [ENTER] at the command line.

- To access other screens:D [PAGE AHEAD] and [PAGE BACK] to see

other directory pages

D [SELECT] on group title to see GroupDisplay

Figure 2.3.1. Group Directory Screen

CC: 2-3-3


Group Display Screen

A group display contains up to eight ControlBlock faceplates. Plantprocesses can be monitored and controlled from a Group Displayscreen. Figure 2.3.2 shows an example of a Group Display screen.

You can label each faceplate on a group display with a 16--charactertag. Tags that are longer than 8 characters appear on two lines on thisscreen.


other Group Displays

D [SELECT] on faceplate to see blockfaceplate screen

2: MIX 25-Jul-96 12:17:38

Tag � �boiler � � � � �� control � �KCB-MC � � �KCB-MC

Units TEMP OPERATOR .00PV-A *405. start .00LSP-B *410. stop .00RSP-C --AUTO-- .00FF-D start

stop100

--------75

on cfrm50 off cfrm

tripped25

-OUTPUT-0 run .00

13.8 STOPfailed

AUTO OPERATOR OPERATOR

CONFIG 1

Group faceplates are addedand deleted in the Tag field.

- To call up, type:D G: (group #) [ENTER] at the command line

D G [ENTER] at the command line from ablock configuration screen

D [SELECT] from group on Group Directory,Unit Display, or Overview Display

Figure 2.3.2. Group Display Screen

CC: 2-3-4


- To add a faceplate on a Group Display screen:

1. Cursor to the Tag field.

2. Type the tag or address of the faceplate according to Table 2.3.1.

3. Press [ENTER].

Table 2.3.1. Group Display Entries for Faceplates

To get this faceplate... Enter this in the“Tag” Field

Standard faceplate----Continuous faceplate for continuous

function ControlBlocks----Discrete faceplate for discrete function

ControlBlocks

tag or address

Nonstandard faceplate----Discrete faceplate for continuous

function ControlBlocks----Continuous faceplate for discrete

function ControlBlocks

#tag or #address

Continuous faceplate +tag or +address

Discrete faceplate --tag or --address

- To delete a faceplate on a Group Display screen:

1. Cursor to the faceplate so that it is highlighted.

2. Press [NEXT OPTION] or type “none”.

3. Press [ENTER].

CC: 2-3-5


Configuring Unit Displays

D Unit display titles are configured on the Unit Directory screen.D Unit displays are configured on the Unit Display screen.

Unit Directory Screen

The Unit Directory screen lists Unit Displays. Unit display titles must beconfigured on the Unit Directory. Figure 2.3.3 gives an example of aUnit Directory screen.

Units 1--80 forcommand consoles

- To call up, type:D UD: [ENTER] at the command line.


other directory pages.

D [SELECT] on unit title to see Unit Display.

D A title can contain up to 20 characters,including spaces.

D If no title is listed, “Unit #” is displayedat the top of the Unit Display screen.


UNIT DIRECTORY 14-Jul-96 02:33:11

Unit Title Unit Title Page 1

1 �Heat & Preheat Zones 11�

2 �Soak Zone & Misc Controls 12�

3 �Desalination Control 13�

4 �Desalination Startup 14�

5 �Demethanizer Control 15�

6 �INDUSTRIAL POWER DEMO 16�

7 � 17�

8 � 18�

9 � 19�

10� 20�CONFIG 3

Figure 2.3.3. Unit Directory Screen

CC: 2-3-6


Unit Display Screen

A unit display contains up to four group displays on one screen. Tagsthat are longer than 8 characters appear on two lines on this screen.Figure 2.3.4 shows an example of a Unit Display screen.

.

- To call up, type:D U: (unit #) [ENTER] at the command line.

- To access other screens, type:D [PAGE AHEAD] and [PAGE BACK] to see

other Unit Displays.

D [SELECT] on faceplate to see GroupDisplay.

D Type the group number in the “Group”field.

D To delete a group, press [NEXT OPTION]or type “none”.

Unit #1 27-Jul-96 10:10:42

Group >1 Line 1 Tank 5

STACK 2 STACK 2 STACK 2 STACK 2 STACK 2VALVE E1 MCC-E1 Sensor E VCC-E2 VALVE E2

| run | | open | || STOP | | close | || failed | | failed | |


STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2VALVE F1 MCC-F1 Sensor F VCC-F2 VALVE F2 VALVE F3 VALVE F4 VALVE F5

| run | | open | | | || STOP | | close | | | || failed | | failed | | | |


STACK 2 STACK 2VALVE G1 MCC-G1

| run || STOP || failed |


STACK 2 STACK 2 STACK 2 STACK 2 STACK 2VALVE H1 MCC-H1 Sensor H VCC-H2 VALVE H2

| run | | open | || STOP | | close | || failed | | failed | |

FULL CONFIG 1

Figure 2.3.4. Unit Display Screen

CC: 2-3-7


Configuring Overview Displays

D Overview display titles are configured on the Overview Directoryscreen.

D Overview displays are configured on the Overview Displayscreen.

Overview Directory Screen

The Overview Directory allows you to configure titles for OverviewDisplays. Figure 2.3.5 shows an example of an Overview Directoryscreen.

OVERVIEW DIRECTORY 18-Jul-96 07:33:31

Overview Title Overview Title Page 1

1 �Reheat Furnace Overview 11�

2 �Desalination Overview 12�

3 �Demethanizer Overview 13�

4 � 14�

5 � 15�

6 � 16�

7 � 17�

8 � 18�

9 � 19�

10� 20�CONFIG 2

Overviews 1--80 forcommand consoles.

- To call up:D OD: [ENTER] at the command line.


other directory pages.

D [SELECT] on overview title to see OverviewDisplay.

D A title can contain up to 20 characters, includingspaces.

D If no title is listed, “Overview #” is displayed atthe top of an Overview Display screen.


Figure 2.3.5. Overview Directory Screen

CC: 2-3-8


Overview Display Screen

An overview display monitors group displays by configuring unitdisplays. Tags that are longer than 8 characters appear on two lines onthis screen. Figure 2.3.6 shows an example of an Overview Displayscreen.

Overview #1 27-Jul-96 10:11:16Unit >1 Unit #1

STACK 2 STACK 2 STACK 2 STACK 2 STACK 2VALVE E1 MCC-E1 Sensor E VCC-E2 VALVE E2

| failed | | L| | | |STACK 2 STACK 2 STACK 2 STACK 2 STACK 2 STACK 2VALVE F1 MCC-F1 Sensor F VCC-F2 VALVE F2 Valve F3

| | | | | | | |STACK 2 STACK 2 STACK 2 STACK 2 STACK 2VALVE G1 MCC-G1 Sensor G VCC-G2 VALVE G2

| | | | | |STACK 2 STACK 2 STACK 2 STACK 2 STACK 2VALVE H2 MCC-H1 Sensor H VCC-H2 VALVE H2

L| failed | L| failed | L|

Unit >2 Unit #2STACK 4 STACK 4 STACK 4 STACK 4 STACK 4VALVE P1 MCC-P1 Timer P VCC-P2 VALVE P2

| failed | | | failed | |STACK 4 STACK 4 STACK 4 STACK 4 STACK 4VALVE Q1 MCC-R1 Timer Q VCC-Q2 VALVE Q2

L| | | | |STACK 4 STACK 4VALVE R1 MCC-R1

| |STACK 4 STACK 4 STACK 4 STACK 4 STACK 4VALVE S1 MCC-R1 Timer S VCC-S2 VALVE S2

| | | | |

FULL CONFIG 1

D Type the unit number in the “Unit” field.D To delete a group, press [NEXT

OPTION] or type “none”.

- To call up, type:D O: (overview #) [ENTER] at the command

line.


other Overview Displays.

D [SELECT] on faceplate to see GroupDisplay.

Figure 2.3.6. Overview Display Screen

CC: 2-4-1

RS3: Configuring Operating Characteristics Configuring Callup and Display Buttons

Section 4:Configuring Callup and Display Buttons

This section shows how to configure callup and display buttons to callup group displays, graphic displays, reports, alarm lists, and otherinformation. Figure 2.4.1 shows the location of the callup and displaybuttons on the console keyboard.

Callup buttons

Display buttons

Figure 2.4.1. Callup and Display Buttons

CC: 2-4-2


Configuring Callup Buttons

Callup buttons are configured on the Alarm Annunciation screen.Figure 2.4.2 shows an example of an Alarm Annunciation screen.

You configure commands, assign them to callup buttons, and configurealarm annunciation characteristics for them.

The Callup Buttons screen is useful for testing and troubleshootingcallup buttons. See the “Callup Buttons Screen” on page 2-4-7 formore information.

ALARM ANNUNCIATION 02-Aug-96 12:45:32

No. COMMAND

�1 �

PushButton

�

LAMP�

Associated Unit/Area/Block Ad-dresses

� �

� �

� �

� �

� �

� �

� �

� �

� ��

NoneLAMPYES

2

- To call up, type:D AAC [ENTER] at the command line.

D [EXCH] from Callup Buttons.

- To access other screens, type:D [PAGE AHEAD] to see other commands.

D [EXCH] to see Callup Buttons.

To access a command number, enter thenumber in the “No.” field.

Figure 2.4.2. Alarm Annunciation Screen

CC: 2-4-3


Configuring a Command

A command is a set of keystrokes that is executed from the commandline when the associated callup button is pressed. You configure thecommand in the “Command” field on the Alarm Annunciation screen.Some command examples are listed in Table 2.4.1.

You can configure special commands to perform specific functions.These special commands are listed in Table 2.4.2.

Table 2.4.1. Command Examples

Command Result

G:1* Calls up group #1.

PG:,Boiler * (MTCC only) Calls up the process graphic Boiler.

RR:,Daily * (MTCC only) Calls up the report Daily.

Table 2.4.2. Special Commands

Special Characters Description

* Represents the [ENTER] button.

#(block input) Changes the status of an input.For example, the command ”#FIC--101/@a” changes the input FIC--101/@a toits opposite state. This command might be used as a fast way to stopequipment in case of an alarm.

~

Used at the beginning of a command to prevent the keystrokes from beingexecuted on the command line.

Can be used to configure callup buttons as individual keyboard keys. Forexample, ~K would cause a callup button to insert the letter K wherever thecursor happened to be on the screen when the button was pressed.

#�C Performs a console restart.

#�H Moves the cursor to the left.

#�J Moves the cursor down.

#�K Moves the cursor up.

#�L Moves the cursor to the right.

CC: 2-4-4


Configuring a Callup Button Number

You can assign a callup button to a configured command. When thecallup button is pressed, the command is executed.

D You use the “Push Button” field on the Alarm Annunciationscreen to assign a callup button to a command.

D The callup button number consists of two numbers separated bya period. The first number specifies the bank of callup buttons.The second number specifies the number of the button on thebank.

D The callup button bank numbering is also shown on the CallupButtons screen.

Figure 2.4.3 shows examples of callup button numbers.

If “None” is entered in the “Push Button” field, the command is executedonly when a block listed in the Associated Block Addresses field is inalarm, “Lamp�Yes” is configured, and the [ACTIVE ALARM] button ispressed.

RS3FISHER--ROSEMOUNT

Button 1.17 Button 2.6

Figure 2.4.3. Option Keyboard Callup Button Example

CC: 2-4-5


Configuring Alarm Annunciation

D Blocks, plant units, and alarm areas can be configured in the“Associated Unit/Area/Block Addresses” field on the AlarmAnnunciation screen. Examples are shown in Table 2.4.3.

D If a configured address is in alarm and “Lamp�Yes” isconfigured, then the callup button LED lights. If the alarm isunacknowledged, the LED also blinks.

D If a configured block is in alarm, “Lamp�Yes” is configured, andyou press [ACTIVE ALARM], the configured command isexecuted. (Remember that the [ACTIVE ALARM] key calls upscreens according to time of alarm.)

Figure 2.4.4 shows an example of a callup button configuration.

Table 2.4.3. How to Configure Alarm Annunciation

To configure.. Enter...For example:

Type... And it appears as...

a blockthe block tag

oraddress

LI--101or

=2C--22

LI--101or

=2C--22

a plant unit the plant unit number 4 #4

an alarm area the alarm area name Boiler $Boiler

CC: 2-4-6


ALARM ANNUNCIATION 02-Aug-96 12:45:32

No. COMMAND

�1 �G:5*

PushButton

�1.1

LAMP�

Associated Unit/Area/Block Addresses

�=2C-3 �=2C-5

�=2C-6 �=2C-7

�=2C-10 �=2C-12

� ��

� �

� �

� �

NoneLAMPYES

2

If you press callup button 1.1,Group Display #5 is called up.

If one of the configured blocks is in alarm,the LED on callup button 1.1 lights.

Figure 2.4.4. Alarm Annunciation Screen Example

CC: 2-4-7


Callup Buttons Screen

The Callup Buttons screen shows the commands that are configured forthe buttons. The callup button commands are assigned using the AlarmAnnunciation screen. Figure 2.4.5 shows an example of a Callup Buttonscreen with field descriptions.

PushButton COMMAND

1 G:1*2 G:2*3 G:7*456 TAFC-101*BD*7891011121314 CFS*1516

(MORE)

CONFIG 3

1 9 17 25

2 10 18 26

3 11 19 27

4 12 20 28

5 13 21 29

6 14 22 30

7 15 23 31

8 16 24 32

CALLUP BUTTONS 02-Aug-96 16:43:22

D The “Command” field shows thecommands that are configured for thecallup buttons. Press [PAGE AHEAD] todisplay more buttons and to see othercallup buttons keyboards.

D If you cursor to a number and press[SELECT], the number appears at the topof the column.

OPTIONS Set No. 1

- To access other screens, type:D [PAGE AHEAD] to see other commands for

callup buttons keyboard 1 and to seecommands for other callup buttonskeyboards.

D [EXCH] to see Alarm Annunciation.

D Cursor to button number on left or right,[SELECT], then [EXCH] to call up AlarmAnnunciation for that button.

D The box on the left shows the callupbuttons numbering scheme. The callupbutton number corresponds to the “PushButton” field on the right.

D If you cursor to a number and press[ENTER], the configured command isexecuted.

D If you cursor to a number and press[SELECT], the number appears at the topof the right column.

- To call up, type:D CCB [ENTER] at the command line.

D [EXCH] from Alarm Annunciation.

Figure 2.4.5. Callup Buttons Screen

CC: 2-4-8


Display Buttons Screen

The Display Buttons screen is used to configure commands for thedisplay buttons. The display buttons are located at the left side of theOperator keyboard (see Figure 2.4.1). The display buttons function thesame as the callup buttons, except that they have no lights for alarmannunciation. Figure 2.4.6 shows an example of a Display Buttonsscreen.

Button COMMAND�7 �

12 o:3 td:4 el:*5 del*6 sp*78 u:9 tg:10 ol*11. ddp*12 da*1314 g:151617 ~%

DISPLAY BUTTONS 02-Aug-96 16:43:22

1 7 13

2 8 14

3 9 15

4 10 16

5 11 17

6 12

STATUS

P Way C F C B

DISPLAYS

- To call up, type:D CDB [ENTER] at the command line

- To access other screens:D None

D The box on the left shows the displaybuttons numbering scheme. The callupbutton number corresponds to the“Button” field on the right.

D If you cursor to a number and press[ENTER], the configured command isexecuted.

D If you cursor to a number and press[SELECT], the button number appears atthe top of the column on the right.

- To configure a command for a displaybutton:

1. Cursor to the “Button” field, type the buttonnumber, and press [ENTER].

or

Cursor to the display number on the left sideof the display and press [SELECT].

2. Enter the desired command. For informationabout commands, see the “Configuring aCommand” heading on page 2-4-3.

Figure 2.4.6. Display Buttons Screen

CC: 2-4-9


Hints for Callup Buttons and Display Buttons

This section discusses some problems you might have whenconfiguring callup buttons and display buttons, along with someconfiguration tips.


- After I programmed a callup button, I tried to use it. When Ipush the callup button, nothing happens and the Button NotProgrammed message appears.

Remember that the “Push Button” field on the Alarm Annunciationscreen determines which callup button is assigned to a command.The “Command” field does not perform this function.

An easy way to see what command is configured for a button is togo to the Callup Buttons screen, cursor to the picture on the left ofthe button you want, press [SELECT] and then press [EXCH]. TheAlarm Annunciation appears with the command that contains thatcallup button at the top of the display.

- I have configured a command to callup a group display, butsome of the blocks in the group display are not listed in the“Associated Addresses” field on the Alarm Annunciationscreen.

If you have added or deleted blocks from a group display, thechanges are not reflected in the “Associated Addresses” field. Youcan update the field by deleting the command and reentering it.

CC: 2-4-10


Configuration Tips

- Tips for keeping track of callup button numbers and commandnumbers

It is a good idea to keep the command number and the callup buttonnumber consistent. For example, assign callup button 1.1 tocommand 1, callup button 1.2 to command 2, and so on.

- How to configure a command without assigning a callup buttonto it

If you want to configure a command without a callup button,configure a command number larger than the largest callup buttonnumber on your console. Each console has a few more commandsthat can be configured than callup buttons. The command is thenexecuted only when a block listed in the “Associated Addresses”field is in alarm, “Lamp�Yes” is configured, and the [ACTIVEALARM] key is pressed. (Remember that the [ACTIVE ALARM] keycalls up screens according to time of alarm.)

- If you configure commands to call up group displays

When you configure a command to call up a group display, theblocks that are currently in that group display are automatically put inthe “Associated Addresses” field.

- If you change blocks in a group display after configuring acommand to call up that group display

If you have added or deleted blocks from a group display, thechanges are not reflected in the “Associated Addresses” field. Youcan update the field by deleting the command and reentering it.

- If you change the “Associated Addresses” field entries for acommand that calls up a group display

If you alter the “Associated Addresses” field entries for a commandthat calls up a group display, you must be careful. The blocks mustappear in the same order in the “Associated Addresses” field as theydo on the group display.

You can delete blocks from the “Associated Addresses” field, but theones that remain must be in the same order as they appear on thegroup display.

CC: 2-5-1

RS3: Configuring Operating Characteristics Configuring Message Pairs

Section 5:Configuring Message Pairs

This section shows how to configure message pairs. Each consolestores text items called message pairs. Message pairs are usedthroughout the system to represent discrete states. A message pairconsists of one message for the on (1) state and one message for theoff (0) state of a discrete variable. Figure 2.5.1 shows an example of amessage pair.

STD MESSAGE PAIRS

Pair True Atr False Atr Pair

*21 �CONFIRM �C4 �confirm �C1 *31

*22 �ON CFRM �C4 �on cfrm �C1 *32

*23 �LO CFRM �C4 �lo cfrm �C1 *33

*24 �HI CFRM �C4 �hi cfrm �C1 *34

*25 �FWD CFRM �C4 �fwd cfrm �C1 *35

*26 �REV CFRM �C4 �rev cfrm �C1 *36

*27 �OFF CFRM �C4 �off cfrm �C1 *37

*28 �OPN CFRM �C4 �opn cfrm �C1 *38

*29 �CLS CFRM �C4 �cls cfrm �C1 *39

*30 �RUN CFRM �C4 �run cfrm �C1 *40

When the discretevariable has a 0 state,the false message isdisplayed.

OPERATOR> start> stop

---AUTO--

STARTstop

---------

ON CFRMoff cfrmtripped

-OUTPUT-RUNstopfailed

OPERATOR> start> stop

---AUTO--

startSTOP

---------

on cfrmOFF CFRMtripped

-OUTPUT-runSTOPfailed

When the discrete variablehas a 1 state, the truemessage is displayed.

Figure 2.5.1. Faceplates and Message Pairs

CC: 2-5-2


Standard and User Message Pairs

The system includes standard message pairs and user message pairs.Table 2.5.1 lists message pair characteristics.

Table 2.5.1. Message Pair Characteristics

Item Standard Message Pairs User Message Pairs

Quantity 100 155

Configurable? Yes Yes

Preconfigured?* All Some

Max # of characters 8 8

* Preconfigured message pairs are used in the system to represent discrete states. You should take carewhen changing preconfigured message pairs so that unwanted system changes do not occur.

CC: 2-5-3


The Message Pairs Screens

Standard message pairs are configured on the Std Message Pairsscreens (see Figure 2.5.2). User message pairs are configured on theUser Message Pairs screens (see Figure 2.5.3).

The preconfigured standard message pairs are listed in Table 2.5.2.The preconfigured user message pairs are listed in Table 2.5.3.

User message 101, called “Tag”, can be assigned on a Discrete Linksscreen as a message on input or output blocks. For an example ofusing this message, see “Hints for Using Message Pairs” on page2-5-9.

- To configure non--English characters in a message pair:

D Scroll through the foreign character options by typing a character,then pressing the [CTRL] and [A] keys simultaneously.

CC: 2-5-4


STD MESSAGE PAIRS 18-Jul-96 11:35:11

Pair True Atr False Atr Pair True Atr False Atr

*1 �ON �C4 �OFF �C1 *11 �AUTO �C1 �OPERATOR �C5

*2 �START �C4 �start �C1 *12 �ENABLE �C4 �enable �C1

*3 �LOW �C4 �low �C1 *13 �PUMP �C4 �pump �C1

*4 �HIGH �C4 �high �C1 *14 �AGITATE �C4 �agitate �C1

*5 �FORWARD �C4 �forward �C1 *15 �TRANSFER�C4 �transfer �C1

*6 �REVERSE �C4 �reverse �C1 *16 �DRAIN �C4 �drain �C1

*7 �STOP �C5 �stop �C2 *17 �WASH �C4 �wash �C1

*8 �OPEN �C4 �open �C1 *18 �PROCEED �C4 �proceed �C1

*9 �CLOSE �C5 �close �C2 *19 �DISABLE �C5 �disable �C2

*10 �RUN �C4 �run �C1 *20 �DISABLED�C5 �disabled �C2CONFIG 1

Attributes C1 through C6 determine the color(text and background) of the message.Attributes are assigned on the ColorConfiguration screen.

Standard message pairs are numbered1 -- 100 and are identified with an asterisk (*).

True and False correspond tothe on/off states of a discreteaction.

- To call up, type:D MPS [ENTER] at the command line.


other standard message pairs and usermessage pairs.

Figure 2.5.2. Standard Message Pairs Screen

CC: 2-5-5


USER MESSAGE PAIRS 18-Jul-96 11:35:11

Pair True Atr False Atr Pair True Atr False Atr

1 � �C1 � �C1 11 � �C1 � �C1

2 � �C1 � �C1 12 � �C1 � �C1

3 � �C1 � �C1 13 � �C1 � �C1

4 � �C1 � �C1 14 � �C1 � �C1

5 � �C1 � �C1 15 � �C1 � �C1

6 � �C1 � �C1 16 � �C1 � �C1

7 � �C1 � �C1 17 � �C1 � �C1

8 � �C1 � �C1 18 � �C1 � �C1

9 � �C1 � �C1 19 � �C1 � �C1

10 � �C1 � �C1 20 � �C1 � �C1CONFIG 1

Attributes C1 through C6 determine the color(text and background) of the message.Attributes are assigned on the ColorConfiguration screen.

User message pairs are numbered 1--155.

True and False correspond tothe on/off states of a discreteaction.

- To call up, type:D MPU [ENTER] at the command line.

- To access other screens, type:D [PAGE AHEAD] and [PAGE BACK] to

see other user message pairs andstandard message pairs.

Figure 2.5.3. User Message Pairs Screen

CC: 2-5-6


Table 2.5.2. Preconfigured Standard Message Pairs

StandardMessagePair

Number

True(on)

False(off)

StandardMessagePair

Number

True(on)

False(off)

*1 ON OFF *26 REV CFRM rev cfrm

*2 START start *27 OFF CFRM off cfrm

*3 LOW low *28 OPN CFRM opn cfrm

*4 HIGH high *29 CLS CFRM cls cfrm

*5 FORWARD forward *30 RUN CFRM run cfrm

*6 REVERSE reverse *31 SHUTDOWN shutdown

*7 STOP stop *32 INTERLOK interlok

*8 OPEN open *33 RESET reset

*9 CLOSE close *34 POSN ’A’ posn ’A’

*10 RUN run *35 POSN ’B’ posn ’B’

*11 AUTO OPERATOR *36 ’A’ CFRM ‘A’ cfrm

*12 ENABLE enable *37 ’B’CFRM ’B’ cfrm

*13 PUMP pump *38 OPERATOR operator

*14 AGITATE agitate *39 ----AUTO---- ----auto----

*15 TRANSFER transfer *40 STATUS status

*16 DRAIN drain *41 FAILED

*17 WASH wash *42 ON FAIL on fail

*18 PROCEED proceed *43 LO FAIL lo fail

*19 DISABLE disable *44 HI FAIL hi fail

*20 DISABLED disabled *45 FWD FAIL fwd fail

*21 CONFIRM confirm *46 REV FAIL rev fail

*22 ON CFRM on cfrm *47 OFF FAIL off fail

*23 LO CFRM lo cfrm *48 OPN FAIL opn fail

*24 HI CFRM hi cfrm *49 CLS FAIL cls fail

*25 FWD CFRM fwd cfrm *50 RUN FAIL run fail


CC: 2-5-7


Table 2.5.2. Preconfigured Standard Message Pairs (continued)

StandardMessagePair

Number

False(off)

True(on)

StandardMessagePair

Number

False(off)

True(on)

*51 IGNORE ignore *76 PMP CFRM pmp cfrm

*52 FAILED failed *77 DRN CFRM drn cfrm

*53 SW FAIL sw fail *78 WSH CFRM wsh cfrm

*54 TRIPPED tripped *79 SETPOINT setpoint

*55 LOCKOUT lockout *80 NEXT next

*56 MCC OFF mcc off *81 ON off

*57 TRAVEL travel *82 ON off

*58 ABORT abort *83 STOP stop

*59 ABORTED *84 START stop

*60 NOT USED not used *85 RUN stop

*61 CLS TRP cls trp *86 RUN stop

*62 RUN TRP run trp *87 OPEN close

*63 RETRY LM retry lm *88 --OUTPUT-- --output--

*64 MCC ALRM mcc alrm *89 ALARM ok

*65 V TRAVEL v travel *90 ALARM ok

*66 FORWARD forward *91 ON OFF

*67 REVERSE reverse *92 ON OFF

*68 HOLD hold *93 START STOP

*69 HOLD *94 START STOP

*70 STATUS status *95 RUN STOP

*71 PROCEED *96 RUN STOP

*72 RUN *97 OPEN CLOSE

*73 ACTIVE active *98 OPEN CLOSE

*74 INACTIVE inactive *99 ALARM OK

*75 STP CFRM stp cfrm *100 ALARM

CC: 2-5-8


Table 2.5.3. Preconfigured User Message Pairs

UserMessage Pair

Number

True(on)

False(off)

151 AUTOTUNE AutoTune

152 AUTOENTR AutoEntr

153 ADJ.GAIN adj.gain

154 ADJ. TI adj. Ti

155 ADJ. TD adj. Td

CC: 2-5-9


Hints for Using Message Pairs

This section discusses message pair configuration tips.

Configuration Tips

- How to configure non-English characters in a message pair

Scroll through foreign character options by typing a character, thenpressing the [CTRL] and [A] keys simultaneously.

- How to configure a tag as a message pair

You can configure a block tag as a message pair by using usermessage 101. You must configure the block as a discrete input oroutput with a message pair of 101. The message pair for that inputor output then consists of the block tag. The tag is backlighted for anon (1) condition and is not backlighted for an off (0) condition.

CC: 2-5-10


CC: 2-6-1

RS3: Configuring Operating Characteristics Configuring the Block Print Function

Section 6:Configuring the Block Print Function

The block print function allows you to produce system documentation byprinting block configuration screens. The block print function isconfigured on the Block Print Setup screen (see Figure 2.6.1).Table 2.6.1 shows the Block Print Screen Setup screen fields.

- To perform a block print:

1. Call up the Block Print Setup screen.

2. Configure the fields as desired.

3. Cursor to the “Start Print” field and press [ENTER].

As the block print is performed, the block configuration screensthat are being printed appear on the CRT. Also, the message “BPBusy” is displayed in the lower left of the display.

You cannot perform other tasks while the block print function isactive. However, the block print function can be stopped andrestarted at any time.

It may take several hours to print all block screens for a plant.

- To stop the block print:

D Press any console key.

- To restart the block print function:

1. Return to the Block Print Setup screen.

2. Cursor to the “Resume Print“ field and press [ENTER].

CC: 2-6-2


BLOCK PRINT SETUP 21-Jul-96 08:00:58Block

First Block, Last Block Faceplates Links Logic Alarms Ref:

1� =1A-1, =1A-5 �both �both �yes �yes �no

2� =2A1, =2D-99 �both �both �yes �no �no

3� =4A-1, =7H-99 �both �both �yes �no �no

4�

5�

6�

7�

8�

9�Start Print

CONFIG 4

3. To select field options, cursor toeach field and press [NEXTOPTION]. Then, press [ENTER].

4. Begin the block print function bycursoring to the “Start Print” field. Press[ENTER].

- To do a block print:1. Cursor to the “First Block” field and type in the

block address or range of block addressesseparated by a comma.

2. Press [ENTER]. The tags align themselves inthe appropriate columns.

- To call up, type:D BP [ENTER] at the command line.

- To access other screens, type:D None.

Figure 2.6.1. Block Print Setup Screen

CC: 2-6-3


Table 2.6.1. Block Print Setup Screen Fields

Field Description Entries

Block Range

Specifies the blocks to be printed. Blocks can be referenced bytag or address. Blocks can be listed singly (e.g., =1A--1) or in arange (e.g., =1A--1,=1A--5). Control blocks or input/outputblocks can be printed.

Tag or address;single or range

Faceplates Specifies the block faceplates to be printed. Analog, Discrete,Both, Neither.

Links Specifies the block links that are printed. Analog, Discrete,Both, and Neither

Logic Specifies whether or not defined block logic steps are printed. Yes, No

Alarms Specifies whether or not block variable alarm configurationscreens are printed if the variables are in alarm. Yes, No

Block Ref: Specifies whether or not block references are printed. Yes, No

CC: 2-6-4


CC: 2-7-1

RS3: Configuring Operating Characteristics Link Editor

Section 7:Link Editor

The Link Editor allows you to change the addresses of links withinvarious files to allow them to transfer configurations from one addressrange to another.

There are two cases where this is often required:

D If the node number is re-addressed to another node number forsome reason (including being moved to a different PeerwayNumber).

D If a configuration or range of blocks for a section of the plant iscopied to another area. For example, if two boiler configurationsare similar, once the first configuration is completed, the secondconfiguation may be copied from the first.

The Link Edit function allows the following operations for fileconfigurations:

D Moving or copying from one ControlFile to another ControlFileExample: move =3 to =31 or move =3 to =294

D Moving or copying from one controller to another controllerExample: move =3A to =3B or move =3A to =31A

D Moving an address range within a controllerExample: move range of =3AA101,=3AA832 to starting address=3BA101 or move =3A--1,5 to starting at address =31A--10 to=31A--14

You can change the following configurations on the Link Editor screen:

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 When blocks are copied using the Plant Configuration “Disk LoadTransfer”, remember to change any duplicate tags.

D The Link Editor changes only references to block links in theconfiguration. It has no effect on actual block links in thespecified controllers.

D You cannot change the range of an I/O card cage.

CC: 2-7-2


Modifying a Configuration File

The Link Editor allows you to update the addresses within aconfiguration file. The file is modified to reflect the new addresses forthe address range that is modified for all functions.

NOTE: Always make a copy of your original file, and work from thecopy.

You must be careful when loading the Console Configuration modifiedfile. The suggested procedure is to load in this order:

1. Load the full Console Configuration for the desired file on theDisk Activity screen.

2. Save the Console Configuration using the “All” function on theDisk Activity screen.

3. Verify that the “Configuration File” on the lower left corner of the“Configure Command Console” screen is updated so that theconsole will load the correct file the next time the console isrebooted.

Modifying Other RS3 File Types

Other RS3 file types within the system cannot be changed using theLink Editor, however each can be modified in another manner:

D Plant ConfigurationModified using ”Disk Load Transfer” function on the Disk Activityscreen, or using the PC-based Control Studio application.

D Batch TasksModified using ”Batch Load Transfer” function on the Disk Activityscreen.

D RBL FilesModified using the search and replace function within eachindividual RBL script. (Set the “Tags or Addresses” field on theConfigure Command Console screen to “Addresses”.)RBL files may also be modified using the PC-based Batch Studioapplication.

CC: 2-7-3


Calling Up the Link Editor Screen

Figure 2.7.1 shows the Link Editor screen.

- To call up the Link Editor screen, type:

L E

or

L E (node) [:] (drive)

CC: 2-7-4


LINK EDITOR 07-Nov-97 14:35:19Console Node 68

Disk Name WINIAt Node 60 On Drive 1

File Name � ABC14 Console Config

Address Range �=7E-60,=7E-80

New Address �=91A-60

Operation �Edit GROUP Display

Edit Mode � List

Group Range � All

� Press <ENTER> to Execute

Unmodified AddressesTRIANGLE:=7E-60/cBOX:,=7E-61TAG:,=7E-60TAG:,=7E-61TAG:,=7E-62TAG:,=7E-63TAG:,=7E-64TAG:,=7E-65LINK:,=7E-60LINK:,=7E-61LINK:,=7E-62LINK:,=7E-63LINK:,=7E-64LINK:,=7E-65DISC:,=7E-60DISC:,=7E-61Page 1 *More*

File Name. Name of the file used tomodify block link references.

Address Range. Current address range oflinks to be edited or listed. You can specify arange by PeerWay node and controllerprocessor card numbers.New Address. New address range of linksafter editing. You can specify a range byPeerWay node and controller processor cardnumbers.

Operation. Press [SELECT] to choose the operation:Edit TREND DisplayEdit Graphic DisplayEdit Report ProgramEdit GROUP DisplayEdit TREND File

Modified addresses reappear in thiswindow when you do a “List” after a“Modify”.

Edit Mode. The Link Editor has two modes:Modify Changes the address of the “Address

Range” field as specified in the “NewAddress” field.

List Display the block links used in theconfiguration in the “UnmodifiedAddresses” window on the right.

Group Range or Trend File: This fieldis displayed if you have selected “EditGROUP Display”, “Edit TRENDDisplay”, or “Edit TREND File” as theoperation. The field defaults to “All”; youcan can change it to a range.

At Node. You cannot change to adifferent node using this screen. Use“L E node :” to access a different node.

Figure 2.7.1. Link Editor Screen

CC: 2-7-5


Procedure: Editing Link Addresses

- To edit link addresses:

Step Operation Description

1 Action: Call up the Link Editor screen. Type:L E (node) [:] (drive)

2 Action: Select the operation in the “Operation” field. Scroll through the availableoperations with the [NEXT OPTION] key. The operations are

Edit TREND FileEdit TREND DisplayEdit Graphic DisplayEdit Report ProgramEdit GROUP Display

Comments: The operation selected determines which folder appears in the “Source File” field(either the Process Graphics, Console Config, or Report Config folder). It alsodetermines whether a “Group Range” or “Trend File” field appears on the screen.

3 Action: Enter the name of a file in the “File Name” field or press [NEXT OPTION] tochoose a file from the available filenames in the folder.

Comments: To call up the file, press [SELECT] on the “File Name” field.

4 Action:Comments:

Enter the current link address range for the file in the “Address Range” field.The address range consists of the PeerWay node and controller processor cardnumbers. Use the format:

=1A (where 1 is the PeerWay node and A is the controller processor card.)The address range must match the actual address range used by the file.

5 Action:Comments:

Enter the new link address range for the file in the “New Address” field.The address range consists of the PeerWay node and controller processor cardnumbers. Use the format:

=1B (where 1 is the PeerWay node and B is the controller processor card.)Note: All addresses that fall inside the source Address Range will be modified bythe addition of an offset that corresponds to the difference between the NewAddress base address and the source Address Range base address.

6 Action: In the “Edit Mode” field select either “List or Modify”. Press the [NEXT OPTION]key to toggle between the two modes.

Modify Changes the address of the “Address Range” field as specified in the“New Address” field.

List List the block links used in the configuration in the “UnmodifiedAddresses” window on the right.

7 Action: If you selected “Edit GROUP Display” or “Edit TREND Display” as the operation,enter a range the “Group Range” field. If you selected “Edit TREND File” as theoperation, enter a range in the “Trend File” field. “All” is the default range.

CC: 2-7-6


- To edit link addresses:

Step DescriptionOperation

8 Action: Cursor to the “Press <ENTER>” field and press [ENTER] to execute the modespecified 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” boxshows only the addresses that were not modified. The modified addresss willappear on the list again after you do a List operation.Note: When modifying the file, the Edit operation will not do anything if the filedoes not contain any addresses that fall in the specified Address Range. Thefollowing message is displayed:

No update: Address is out of range

CC: 2-8-1

RS3: Configuring Operating Characteristics Multinational Characters and Russian Console

Section 8:Multinational Characters and Russian Console

The RS3 offers multinational characters and a Russian (Cyrillic) consoleoption for console software.

Multinational Characters

You can include multinational characters (such as à, é, ö, ñ, and ç) inmost user-entered text, such as in descriptors.- To enter a multinational character:

1. Type the base character (the letter in ASCII closest to themultinational character). For example, to get ñ, type n.

2. Use CTRL A to scroll through the options available formultinational characters associated with the base character untilthe one you want appears.

NOTE: You cannot include multinational characters in tag names, blockaddresses, and in reserved words such as in logic prologue.Multinational characters can be used in logic prologue comments (textbetween quotation marks), batch tags, batch comments, blockdescriptors, block input units, message pairs, file descriptors, report textand banners, and text in process graphics.

Russian Console

On the Russian console, the field names, messages, and othercharacters displayed are in Russian (Cyrillic).

Entering Text and Commands

You can enter text in fields in either Cyrillic, Roman characters, or a mixof Cyrillic and Roman. You can also issue commands on the commandline in either Cyrillic or Roman.

You can toggle back and forth between Cyrillic and Roman. You can bein Roman for text entry and Cyrillic for command line options, or viceversa, or in Roman for both, or in Cyrillic for both.- To toggle between Roman and Cyrillic text entry:

D [CTRL] [A] on a text-entry field.

CC: 2-8-2

RS3: Configuring Operating Characteristics Multinational Characters and Russian Console

- To toggle between Roman and Cyrillic for commands:

D [CTRL] [A] in the HOME position (first row, first column).

Compatibility with Previous Releases

The ability to mix Cyrillic and Roman characters in block descriptor andblock units fields is new with Performance Series Release 1 (P1).Configurations made in systems running version V18 or earlier are stillread. However, if you use a mix of Cyrillic and Roman characters forany new or existing block configuration, the block becomesunrecognizable for versions prior to P1. This means that if you use P1to do a configuration, you must use P1 for normal operation.

In order to display descriptors and units properly in P1, you need to setthe Config Language field on the Command Console Configurationscreen to the language used for the original configuration:

1. Type CCC to call up the Command Console Configurationscreen.

2. [PAGE AHEAD] to see Page 2.

3. Go to the Config Language field.

4. [SCROLL] to select either English or Russian.

An incorrect setting will affect the display of characters, but not thenormal operation of the unit.

CAUTION

Any change to a block descriptor or block units field fromconfigurations prior to P1 may use more memory. Youshould view memory usage as you make changes.

You can view block memory usage by looking at a DiscreteDiagram screen. You can view controller memory on theControlFile Status screen.

Printing

To print Cyrillic in plain text mode you need a Fujitsu model DL2600 orlater. A Cyrillic font will be downloaded automatically from the console atpower up.

If the Cyrillic printer font is lost for any reason (for example, if the printerwas turned off), the Cyrillic font can be manually downloaded againusing the reset field in the printer box on the CCC screen. On the first[ENTER], the print output in the console will clear and the systemdisplays a message asking for an optional second [ENTER] to start theactual font downloading to the printer.

ContentsRS3: Process Graphics


Chapter 3:Process Graphics

Section 1: Introduction to Process Graphics 3-1-1. . . . . . . . . . . . . . . . . . . . . . . . . .

How are Process Graphics Stored? 3-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How are Process Graphics Created and Accessed? 3-1-3. . . . . . . . . . . . . . . . . . . . . . .

Creating a Process Graphic 3-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Calling Up the Viewing Mode of a Process Graphic 3-1-4. . . . . . . . . . . . . . . . . . . . .Calling Up the Configuration Mode of a Process Graphic 3-1-6. . . . . . . . . . . . . . . . .

Section 2: Creating and Configuring Process Graphics 3-2-1. . . . . . . . . . . . . . . .

Creating Process Graphics Objects 3-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Object Types 3-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How Objects Appear in Viewing and Configuration Modes 3-2-7. . . . . . . . . . . . . . . . . .Creating Shapes: Circles 3-2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Boxes 3-2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Triangles 3-2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Arcs 3-2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Lines 3-2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Lines with Different Characteristics 3-2-14. . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Shape Characteristics 3-2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Library Symbols 3-2-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: New Symbols 3-2-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Shapes: Shapes that Fill Up in Response to a Block Variable 3-2-21. . . . . . . .Creating Shapes: Multicolor Shapes 3-2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Block Information: Tag, Blkdes, Mode Objects 3-2-25. .Creating Objects That Display Block Variable Information in Character Form:Links, Units, Disc Objects 3-2-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Block Variable Information in Graphic Form:Hdev, Vdev, Ticbar Objects 3-2-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How the Hdev and Vdev Objects Are Displayed 3-2-33. . . . . . . . . . . . . . . . . . . . . . . .How the Ticbar Object is Displayed 3-2-35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating Objects That Display Faceplates: Group, Unit, Overview Objects 3-2-37. . . .Displaying a Faceplate from a Process Graphic Object 3-2-40. . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Trend Information: Trend Object 3-2-41. . . . . . . . . . . . . .

How the Trend Object is Displayed 3-2-44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Displayed Text: Text Object 3-2-46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Displaying Alarms: Alarm Object 3-2-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Data Entry Fields: Disc Object 3-2-53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: ii

RS3: Process Graphics Contents

Configuring The Appearance of Objects to Change, Depending on the Stateof a Discrete Block Variable 3-2-54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Moving and Copying Objects 3-2-56. . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Deleting Objects 3-2-57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Stacking Objects—Top and Bottom Operations 3-2-58. . . . . . . . . .Configuration Tools: Example of Stacking Objects 3-2-59. . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Grouping Objects 3-2-60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Grouping Objects—Area Operation 3-2-61. . . . . . . . . . . . . . . . . . . .Configuration Tools: Grouping Objects—Group and Join Operations 3-2-63. . . . . . . . .

Joining Single Objects 3-2-63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Joining Groups of Objects 3-2-64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Tools: Grouping Objects--Merge Operation 3-2-66. . . . . . . . . . . . . . . . . . .Configuration Tools: Using the Link Editor Field 3-2-67. . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Splitting an Object from a Group 3-2-69. . . . . . . . . . . . . . . . . . . . . .Configuration Tools: Undoing the Previous Operation 3-2-70. . . . . . . . . . . . . . . . . . . . . .Configuring Display Characteristics: Process Graphics Fabric Coordinates 3-2-71. . . .Configuring Display Characteristics:Changing the Panning Limits and Origin Point 3-2-72. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation 3-2-73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation: Objects that Call up Other Displays 3-2-74.Creating Assists for Display Manipulation: Objects that Call up Another Part ofthe Same Display 3-2-75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation: Display Targets 3-2-77. . . . . . . . . . . . . . . . . .Creating Assists for Display Manipulation: Hiding Parts of the Display Usingan Icon Object 3-2-79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Copying a Process Graphic 3-2-82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Creating Objects That Display Batch Task Data: Bface Object 3-2-83. . . . . . . . . . . . . . .Alarm Annunciation on Graphics 3-2-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Object 3-2-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Icon Object 3-2-85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Optimizing Graphics Performance 3-3-1. . . . . . . . . . . . . . . . . . . . . . . . .

Process Graphic Limits 3-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Link Count Field 3-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using Funnel Blocks 3-3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Merging Objects 3-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Other Methods of Optimizing Graphics 3-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Preconfigured Process Graphics 3-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Screen Refresh and Field Refresh 3-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Graphics Link Editor 3-3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Calling Up the Link Editor Screen 3-3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Procedure: Editing Link Addresses 3-3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iii


List of Figures

Figure Page

3.1.1 Example of a Process Graphic Display Fabric 3-1-1. . . . . . . . . . . . . . . . . . . .

3.1.2 Process Graphics Folder 3-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.3 Using [EXCH] to Move Between Viewing and Configuration Modes 3-1-3. .

3.2.1 Creating a Process Graphics Object—Top Menu 3-2-2. . . . . . . . . . . . . . . . . .

3.2.2 Creating a Process Graphics Object—Object Menu 3-2-3. . . . . . . . . . . . . . .

3.2.3 Creating a Process Graphics Object—Edit Object Menu 3-2-4. . . . . . . . . . .

3.2.4 Viewing Mode 3-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.5 Configuration Mode 3-2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.6 Creating a Circle 3-2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.7 Creating a Box 3-2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.8 Creating a Triangle 3-2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.9 Creating an Arc 3-2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.10 Creating a Line 3-2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.11 Edit Object Menu for the Line Object 3-2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.12 Edit Object Menu for Shapes 3-2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.13 Adding a Library Symbol to a Process Graphic 3-2-18. . . . . . . . . . . . . . . . . . .

3.2.14 Creating a New Symbol 3-2-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.15 Edit Object Menu for Creating a Shape that Fills Up in Responseto a Block Variable 3-2-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.16 Examples of the Ways that Shapes Can Be Used 3-2-22. . . . . . . . . . . . . . . . .

3.2.17 Multicolor Shape and Edit Object Menu 3-2-23. . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.18 Example of a Multicolor Shape with Edit Links Menu 3-2-24. . . . . . . . . . . . . . .

3.2.19 How the Tag, Blkdes, and Mode Objects Appear in ConfigurationMode 3-2-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.20 Edit Object Menu for the Tag, Blkdes, and Mode Objects 3-2-27. . . . . . . . . . .

3.2.21 How the Link, Units, and Disc Objects Appear In Configuration Mode 3-2-29

3.2.22 Edit Object Menu for the Link, Units, and Disc Objects 3-2-30. . . . . . . . . . . . .

3.2.23 How the Hdev, Vdev, and Ticbar Objects Appear in ConfigurationMode 3-2-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.24 How the Hdev and Vdev Objects Appear in Viewing Mode 3-2-33. . . . . . . . . .

3.2.25 Edit Object Menu for the Hdev, Vdev, and Ticbar Objects 3-2-34. . . . . . . . . .

3.2.26 How the Ticbar Object Appears in Viewing Mode 3-2-35. . . . . . . . . . . . . . . . . .

3.2.27 Edit Object Menu for the Hdev, Vdev, and Ticbar Objects 3-2-36. . . . . . . . . .

CC: iv


3.2.28 How the Group, Unit, and Overview Objects Appear inConfiguration Mode 3-2-38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.29 Edit Object Menu for the Group, Unit, and Overview Objects 3-2-39. . . . . . .

3.2.30 Displaying a ControlBlock Faceplate from a Process Graphic Object 3-2-40.

3.2.31 How the Trend Object Appears in Configuration Mode 3-2-41. . . . . . . . . . . . .

3.2.32 Edit Object Menu for the Trend Object 3-2-42. . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.33 How the Trend Object is Displayed 3-2-44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.34 Slidewire Feature of the Trend Object 3-2-45. . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.35 Edit Object Menu for the Text Object 3-2-46. . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.36 How the Alarm Object is Displayed 3-2-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.37 Example of Alarm Object 3-2-49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.38 Examples of Criteria Configurations 3-2-52. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.39 Example Data Entry Fields 3-2-53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.40 Configuring the Edit Object Menu for Conditional Display of Objects 3-2-54.

3.2.41 Moving and Copying an Object 3-2-56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.42 Deleting an Object 3-2-57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.43 Stacking Objects Using the Top and Bottom Operations 3-2-58. . . . . . . . . . . .

3.2.44 Creating an Object Superimposed on Another Object 3-2-59. . . . . . . . . . . . . .

3.2.45 Joining Objects into Groups with the Area Operation 3-2-62. . . . . . . . . . . . . .

3.2.46 Joining Single Objects into Groups 3-2-63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.47 Joining Groups of Objects 3-2-64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.48 Joining Groups of Objects 3-2-65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.49 Merging a Group into a Permanent Thing Object 3-2-66. . . . . . . . . . . . . . . . . .

3.2.50 Using the LinkEd Option to Link an Area 3-2-67. . . . . . . . . . . . . . . . . . . . . . . . .

3.2.51 Splitting an Object from a Group 3-2-69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.52 Undoing an Operation 3-2-70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.53 Fabric Coordinates 3-2-71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.54 Changing a Panning Limit or the Origin Point 3-2-72. . . . . . . . . . . . . . . . . . . . .

3.2.55 Edit Object Menu for Pagefrwd and Pageback Objects forDisplay Manipulation 3-2-74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.56 Use of Anchor Object 3-2-75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.57 Edit Object Menu for Anchor Object 3-2-76. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.58 Example Use of Anchor Object 3-2-76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.59 Example Use of Target Objects 3-2-77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.60 Edit Object Menu for Target Object 3-2-78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.61 How the Icon Object is Displayed 3-2-80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.62 Edit Object Menu for Icon Object 3-2-80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.63 Copying a Process Graphic 3-2-82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: v


3.2.64 How the Bface Object Appears in Configuration Mode 3-2-83. . . . . . . . . . . . .

3.2.65 Edit Object Menu for the Bface Object 3-2-84. . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.1 Using the Link Count Field 3-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.2 Funnel Block Concept 3-3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.3 Link Editor Screen 3-3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

List of Tables

Table Page

3.2.1 Process Graphic Object Types 3-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.2 Screen Fields on the Edit Object Menu for Shape Characteristics 3-2-16. . .

3.2.3 Objects that Display Block Information 3-2-25. . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.4 Screen Fields on the Edit Object Menu for the Tag, Blkdes, andMode Objects 3-2-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.5 Objects that Display Block Variable Information in Character Form 3-2-28. .

3.2.6 Screen Fields on the Edit Object Menu for Link, Units, and DiscObjects 3-2-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.7 Objects that Display Block Variable Information in Graphic Form 3-2-31. . . .

3.2.8 Screen Fields on the Object Edit Menu for the Hdev, Vdev, andTicbar Objects 3-2-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.9 Screen Fields on the Edit Object Menu for the Hdev, Vdev, andTicbar Objects 3-2-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.10 Objects that Display Faceplates 3-2-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.11 Screen Fields on the Edit Object Menu for the Trend Object 3-2-43. . . . . . . .

3.2.12 Screen Fields on the Edit Object Menu for the Text Object 3-2-47. . . . . . . . .

3.2.13 Screen Fields on the Edit Object Menu for the Alarm Object 3-2-50. . . . . . .

3.2.14 Grouping Operations 3-2-60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.15 LinkEd Functions 3-2-68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.16 Display Manipulation Objects 3-2-73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2.17 Screen Fields on the Edit Object Menu for Target Object 3-2-78. . . . . . . . . . .

3.2.18 Screen Fields on the Edit Object Menu for Icon Object 3-2-81. . . . . . . . . . . . .

3.2.19 Screen Fields on the Edit Object Menu for the Bface Object 3-2-84. . . . . . . .

3.3.1 Parameter Limits 3-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: vi


CC: 3-1-1

RS3: Process Graphics Introduction to Process Graphics

Section 1:Introduction to Process Graphics

A process graphic display on an MTCC is a pictorial representation ofplant conditions. It can show pictures of tanks, valves, pipes, and otherequipment, along with numerical and bar--graph representations ofcurrent process data. A process graphic display can also allowoperators to enter data, change controller modes, and perform otherfunctions directly on the display.

You construct a process graphic display with objects, piecing themtogether to build the desired features of the process graphic display.Objects can be physical shapes, displays of current values, operatorentry fields, trend information, faceplates, and other items.

Each process graphic display is constructed on a fabric. The consoledisplay can only show a portion of the process graphic fabric at a time,as shown in Figure 3.1.1. You can move the trackball to see other areasof the process graphic fabric.

The actual size of a process graphic display is limited by factors such asthe number and type of configured objects, the complexity of eachobject, and the number of defined links.

Portion of fabric visible on screen

Figure 3.1.1. Example of a Process Graphic Display Fabric

CC: 3-1-2


How are Process Graphics Stored?

Process graphics are stored as files on the MTCC hard disk. Eachprocess graphic display has a unique file name and is stored in theProcess Graphics folder on the hard disk. Figure 3.1.2 shows the DiskDirectory screen with the Process Graphics folder boxed in.

When an MTCC is initially used, the Process Graphics folder does notexist. The folder is created the first time that a process graphic displayis created.

Plant Config

Plant Prog

1

R

CONFIG 1

Folders on Disk

Console Config

2

DISK DIRECTORY 22-Feb-96 16:42:25Console Node 32

Disk Name CC32 At Node 32 On Drive 1Created 21-Oct-87 Capacity (bytes) 33554176

Remarks�

Reports

12

Trend Data

Console Prog

R

10

Process Graphics

12

Process Symbols

58

Report Config

4

Figure 3.1.2. Process Graphics Folder

CC: 3-1-3


How are Process Graphics Created and Accessed?

A process graphic can be displayed in two modes: viewing mode andconfiguration mode. The [EXCH] key can be used to transfer from onemode to the other, as shown in Figure 3.1.3.

D Viewing mode is used to display the process graphic for plantoperation.

D Configuration mode is used to create and modify the processgraphic.

This section contains procedures for creating and calling up processgraphic displays. For more information about calling up and usinggraphic displays, see OP: 3.

Graphics Viewing

EXCH

Viewing (Operating) Mode

Configuration Mode

Process Graphic Generation

Figure 3.1.3. Using [EXCH] to Move Between Viewing and Configuration Modes

CC: 3-1-4


Creating a Process Graphic

- To create a process graphic, type:

PGG (volume,filename) [ENTER]

If the volume that the Process Graphic resides on is the default volume(usually the console disk drive), the volume entry can be omitted. Forinformation about default volumes, see the DT Manual.

If the process graphic does not exist on the volume, the followingmessage appears at the top of the screen, and a blank Process GraphicGeneration screen appears:

Requested Filename Not Found

The process graphic has now been created and may be configured.Leaving the configuration display writes the process graphicconfiguration to disk.

Calling Up the Viewing Mode of a Process Graphic

- To call up the viewing mode display of a process graphic:

D From the volume containing the graphic:

1. Type:

DD: [ENTER]

The Disk Directory screen for the console hard disk appears.

2. Cursor to the Process Graphics folder and press [SELECT]. TheProcess Graphics Directory screen for the Process Graphicsfolder appears.

3. Cursor to the desired process graphic file name and press[SELECT]. The process graphic viewing mode display appears.

or

D From the command line:

PG: (volume,filename) [ENTER]

If the volume that the Process Graphic resides on is the defaultvolume (usually the console disk drive), the volume entry can beomitted. For information about default volumes, see the DTManual.

CC: 3-1-5


If the process graphic does not exist on the volume, the followingmessage appears at the top of the screen, and a blank GraphicsViewing screen appears:


or

D From the process graphic configuration mode display:Press [EXCH].

CC: 3-1-6


Calling Up the Configuration Mode of a Process Graphic

- To call up the configuration mode display of a process graphic:

D Type:

PGG (volume,filename) [ENTER]If the volume that the process graphic resides on is the defaultvolume (usually the console’s own disk drive), the volume entrycan be omitted. For information about default volumes, see theDT Manual.If the process graphic does not exist on the volume, the followingmessage appears at the top of the screen, and a blank ProcessGraphic Generation screen appears:


The process graphic has now been created and may beconfigured.

or

D Press [EXCH] from the process graphic viewing mode display.

CC: 3-2-1

RS3: Process Graphics Creating and Configuring Process Graphics

Section 2:Creating and Configuring Process Graphics

This section explains how to create and configure process graphics.

CC: 3-2-2


Creating Process Graphics Objects

A process graphic is constructed by configuring objects on the processgraphic fabric. Process Graphics uses menus to accomplishconfiguration tasks. A process graphic display can contain no more than24 Kbytes of memory.

- To create an object:

1. Move the cursor to the location on the fabric where you want theobject to appear.

2. Press [SELECT]. The Top Menu appears on the screen, asshown in Figure 3.2.1. The “Type�None” field indicates that noobject has been configured for this location on the fabric.

PROCESS GRAPHIC GENERATION 02-Feb-96 09:49:12

Top Menu

Type�None

Limits

AreaClose Files

+

X

Figure 3.2.1. Creating a Process Graphics Object—Top Menu

CC: 3-2-3


3. Move the cursor to the “Type” field on the Top Menu so that thefield is highlighted. Press [SELECT]. The Object Menu appearssuperimposed over the Top Menu, as shown in Figure 3.2.2. TheObject Menu lists the object types that can be configured.

NOTE: To move any menu, cursor to the menu name and press[SELECT]. Use the trackball to move the menu to the desired location.Press [SELECT] again.

Top Menu

Type�None

Limits

FilesClose


Object Menu

TEXT TAG GROUP PAGEFRWDLINE LINK UNIT PAGEBACKBOX DISC OVERVIEW ANCHORCIRCLE MODE TREND TARGETARC UNITS BFACE HDEVTRIANGLE BLKDES TICBAR VDEV

Close Symbol

+

X

Figure 3.2.2. Creating a Process Graphics Object—Object Menu

CC: 3-2-4


4. Move the cursor to the desired object type on the Object Menuso that the object type is highlighted. Press [SELECT]. The EditObject Menu appears and the Top Menu and Object Type Menusdisappear, as shown in Figure 3.2.3.

5. Each type of object has its own Edit Object Menu. An item on theEdit Object Menu can be configured by moving the cursor to thedesired field and pressing [SELECT]. Another menu appears thatallows the field characteristics to be configured.


Edit Object Menu

Type TEXT Option�NormalCond�Color�White 1n Blink�NOCommandFont�Normal Edit Text

Close Top Menu

+

X

Figure 3.2.3. Creating a Process Graphics Object—Edit Object Menu

CC: 3-2-5


Object Types

Table 3.2.1 provides brief descriptions of objects that can be used toconfigure a process graphic display. They are explained in more detaillater in this chapter.

Table 3.2.1. Process Graphic Object Types

Object Type Description

Shapes

Circle Displays a circle.

Line Displays one or more lines.

Arc Displays an arc.

Triangle Displays a triangle.

Box Displays a box.

Block information

Tag Displays a block tag.

Blkdes Displays a block descriptor.

Mode Displays the mode of a block.

Block variable information

Link Displays the value of a block variable.

Units Displays the units of a block variable.

Disc Displays one line of a discrete faceplate.

Ticbar Displays a horizontal line that travels along a vertical axis. The line showsthe value of a block variable.

Hdev Displays a bar with horizontal travel that shows the difference between twoblock variables.

Vdev Displays a bar with vertical travel that shows the difference between twoblock variables.

Permanent Faceplates

Group Displays a continuous or discrete faceplate.

Unit Displays a continuous or discrete faceplate from a unit display.

Overview Displays a continuous or discrete faceplate from an overview display.


CC: 3-2-6


Table 3.2.1. Process Graphic Object Types (continued)

Text—Text Displays user--configured text. Can also be used to execute a command.

Object Type Description

Alarm Information—Alarm Provides access to alarms from a process graphic.

Trend Information—Trend Displays graphic trend information for a block variable from a configuredtrend file.

Batch InputWindow—Bainputw

Displays batch messages and input prompts. For more information, see BA:4--1.

Batch Recipe ViewingWindow—Barcpw

Displays a window version of the Batch Working Recipe screen formonitoring the Working Recipe. For more information, see BA: 4--1.

Batch faceplate—Bface Displays a batch faceplate for use on the graphic display.

Display Manipulation

Pagefrwd Executes command when [PAGE AHEAD] is pressed.

Pageback Executes command when [PAGE BACK] is pressed.

Anchor Provides pointer for Pagefrwd, Pageback, and Text objects.

Target Provides target for quick cursor positioning on a large fabric.

Icon Provides the ability to display or hide another object or a group of objects.

CC: 3-2-7


How Objects Appear in Viewing and ConfigurationModes

Most object types appear differently in viewing mode and configurationmode. Figure 3.2.4 shows a portion of a graphic display in viewingmode. The graphic display includes a block tag and a block variablevalue.

Figure 3.2.5 shows the same portion of the graphic display, this time inconfiguration mode. The block tag is represented by the shaded boxlabeled Tag, and the block variable is represented by the shaded boxlabeled Link.

GRAPHICS VIEWING 02-Feb-96 09:49:12

FCC-101

35.7

Figure 3.2.4. Viewing Mode

CC: 3-2-8


LINK

TAG


Figure 3.2.5. Configuration Mode

CC: 3-2-9


Creating Shapes:Circles

- To create a circle:

1. Move the cursor to the desired location of the center of the circle.Press [SELECT]. The Top Menu appears.

2. Move the cursor to the “Type�None” field and press [SELECT].The Object Type Menu appears.

3. Move the cursor to the “Circle” field and press [SELECT]. TheEdit Object Menu appears.

4. Move the cursor to change the size of the circle, as shown inFigure 3.2.6. When the circle is the desired size, press[SELECT]. The circle is now entered on the fabric.

5. If you want, modify the characteristics of the circle using the EditObject Menu. For more information on shape characteristics, see“Creating Shapes: Shape Characteristics” on page 3-2-15.


Edit Object Menu

Type CIRCLE Option�OutlineCond�Color�White 1n Blink�NO

ResizeClose Undo Top Menu

Figure 3.2.6. Creating a Circle

CC: 3-2-10


Creating Shapes:Boxes

- To create a box:

1. Move the cursor to the desired location of one corner of the box.Press [SELECT]. The Top Menu appears.


3. Move the cursor to the “Box” field and press [SELECT]. The EditObject Menu appears.

4. Move the cursor to change the size of the box, as shown inFigure 3.2.7. When the box is the desired size and shape, press[SELECT]. The box is now entered on the fabric.

5. If you want, modify the characteristics of the box using the EditObject Menu. For more information on shape characteristics, see“Creating Shapes: Shape Characteristics” on page 3-2-15.


Edit Object Menu

Type BOX Option�OutlineCond�Color�White 1n Blink�NO

Resize RotateClose Undo Top Menu

Figure 3.2.7. Creating a Box

CC: 3-2-11


Creating Shapes:Triangles

- To create a triangle:

1. Move the cursor to the desired location of one corner of thetriangle. Press [SELECT]. The Top Menu appears.


3. Move the cursor to the “Triangle” field and press [SELECT]. TheEdit Object Menu appears.

4. Move the cursor to the desired location of the second corner ofthe triangle. Press [SELECT].

5. Move the cursor to change the size of the triangle, as shown inFigure 3.2.8. When the triangle is the desired size and shape,press [SELECT]. The triangle is now entered on the fabric.

6. If you want, modify the characteristics of the triangle using theEdit Object Menu. For more information on shape characteristics,see “Creating Shapes: Shape Characteristics” on page 3-2-15.


Edit Object Menu

Type TRIANGLE Option�OutlineCond�Color�White 1n Blink�NO


Figure 3.2.8. Creating a Triangle

CC: 3-2-12


Creating Shapes:Arcs

- To create an arc:

1. Move the cursor to the desired location of one end of the arc.Press [SELECT]. The Top Menu appears.


3. Move the cursor to the “Arc” field and press [SELECT]. The EditObject Menu appears.

4. Move the cursor to the desired location of the other end of thearc. Press [SELECT].

5. Move the cursor to change the size of the arc, as shown inFigure 3.2.9. When the arc is the desired size, press [SELECT].The arc is now entered on the fabric.

6. If you want, modify the characteristics of the arc using the EditObject Menu. For more information on shape characteristics, see“Creating Shapes: Shape Characteristics” on page 3-2-15.


Edit Object Menu

Type ARC Option�OutlineCond�Color�White 1n Blink�NO


Figure 3.2.9. Creating an Arc

CC: 3-2-13


Creating Shapes:Lines

- To create a line:

1. Move the cursor to the desired location of one end of the line.Press [SELECT]. The Top Menu appears.


3. Move the cursor to the “Line” field and press [SELECT]. The EditObject Menu appears.

4. Move the cursor to the desired location of the other end of theline. Press [SELECT]. The line is now entered on the fabric.

Multiple lines can be drawn with the same LINE object. Eachsubsequent line begins where the previous line ended.

5. To finish drawing lines, move the cursor to the “End Line” fieldand press [SELECT], as shown in Figure 3.2.10.


Edit Object

Type LINE Option�LineCond�Color�White 1n Blink�NOLink� Edit Links

Resize RotateClose End Line Top Menu

- To end a line or a seriesof lines:

D Cursor to the ”End Line”field and press[SELECT].

The last line is notentered on the fabric.

Figure 3.2.10. Creating a Line

CC: 3-2-14


Creating Shapes:Lines with Different Characteristics

The characteristics of the line, such as the color in which it is to appearor its ability to blink, can be modified using the Edit Object Menu andthe Edit Links Menu. These characteristics are described in more detailin Table 3.2.2. Figure 3.2.11 shows the Edit Object Menu with optionsfor configuring a line.

- To select a display option for a line:

1. Cursor to the desired field and press [SELECT]. Another menuappears that allows the field to be edited.

2. Move the cursor to the desired field on the new menu and press[NEXT OPTION]. Then press [ENTER].

Edit Object

Type LINE Option�LineCond�Color�White 1n Blink�NOLink� Edit Links

Resize RotateClose End Line Top Menu

The “Option” field determinesthe display option:

D Line

D DashedD Sm Dash

D Dotted

A line can be configured to fill or flow inresponse to a block variable.

The “Link” field determines the tag oraddress of the block variable that theedit links come from.

The “Edit Links” field determines thecolor and action in the segments of theline. See “Creating Shapes: MulticolorShapes” on page 3-2-23 forinformation on the Edit Links Menu.

Figure 3.2.11. Edit Object Menu for the Line Object

CC: 3-2-15


Creating Shapes:Shape Characteristics

The characteristics of a shape are determined by the fields on the EditObject Menu, as shown in Figure 3.2.12 and Table 3.2.2.

- To configure shape characteristics:

1. The Edit Object Menu for the object must be displayed. Move thecursor to the desired field and press [SELECT]. Another menuappears that allows the field to be edited.

2. Move the cursor to the desired field on the new menu. The fieldentry can be changed by using the [NEXT OPTION] key, ifpossible, or by typing the desired entry. Press [ENTER].

Edit Object

Type BOX Option�LineCond�Color�white 1n Blink�NO


- To increase the size:D Enter a number >1. For example, an entry

of 3 triples the size.- To decrease the size:

D Enter a fractional number between zero andone, or a negative number. For example, anentry of .25 or an entry of --4 reduces the sizeto 1/4.

Figure 3.2.12. Edit Object Menu for Shapes

CC: 3-2-16


Table 3.2.2. Screen Fields on the Edit Object Menu for Shape Characteristics

Field Description

Blink Determines whether or not the object blinks.

Color Determines the color. The color choices are configured on the Master Color Selectionscreen ( [C] [C] [P] command).

Cond Determines a condition that affects how the object is displayed. See “Configuring theAppearance of Objects to Change” on page 3-2-54

Option

Determines the display option:D Line, Dashed, Displayed as an outline with the

Sm Dash, Dotted indicated border style.

D Solid Displayed as a solid shape.D FillN, FillS, FillE, FillW Displayed as a solid object the size of which is

determined by the value of a linked variable. See“Creating a Shape That Fills Up” on page 3-2-21.

D MultiN, MultiS Displayed as a solid multicolored object. See“Creating Shapes: Multicolor Shapes” on page3-2-23.

Resize

Resizes the object:D H Size Changes the horizontal size.

D V Size Changes the vertical size.

D H+V Size Changes the horizontal and vertical sizes equally.

Rotate Rotates the object in one of five ways.

CC: 3-2-17


Creating Shapes:Library Symbols

A symbol is a combination of one or more objects that represents acommonly used graphic feature. Symbols reside in the ProcessSymbols folder on the console disk. A standard library of symbolsresides in the Process Symbols folder. You can also create symbols andadd them to your own library.

Figure 3.2.13 shows how to add an existing symbol to a processgraphic. A symbol is added to a process graphic by reading it from adisk. A symbol is read from the same volume as the currently displayedprocess graphic.

- To access the list of available symbols:

D Call up the Disk Directory screen, cursor to the Process Symbolsfolder, and press [SELECT]. The contents of the folder are theavailable symbol files. Press [EXCH] to view the descriptions ofthe symbol files.

D In step 5 of Figure 3.2.13, use the [NEXT OPTION] key to scrollthrough the available symbols.

CC: 3-2-18


Top Menu

Type�None

Limits

FilesClose

Object Menu

TEXT TAG GROUP PAGEFRWDLINE LINK UNIT PAGEBACKBOX DISC OVERVIEW ANCHORCIRCLE MODE TREND TARGETARC UNITS BFACE HDEVTRIANGLE BLKDES TICBAR VDEV

Close Symbol



Process Graphics Symbols

Symbol File�PUMP-1

Close Object Type

- To add a library symbol to aprocess graphic:

1. Cursor to the desired fabriclocation and press [SELECT].

2. Cursor to the “Type” field andpress [SELECT]. The ObjectType Menu appears.

3. Cursor to the “Symbol” fieldand press [SELECT]. TheProcess Graphics SymbolsMenu appears.

4. Cursor to the “Symbol File” field.5. Use the [NEXT OPTION] button to

scroll through the availablesymbols, or type the name of thedesired symbol. Press [ENTER].

NOTE: Less memory is used if a symbolis added to a graphic only once and thencopied as often as desired, than if thesymbol is added to the graphicrepeatedly.

Figure 3.2.13. Adding a Library Symbol to a Process Graphic

CC: 3-2-19


Creating Shapes:New Symbols

A symbol is a combination of one or more objects that represents acommonly used graphic feature. Symbols reside in the ProcessSymbols folder on the console disk. A standard library of symbolsresides in the Process Symbols folder. You can also create symbols.

A combination of objects is made into a symbol so that it can be easilyretrieved without having to be recreated. Objects must be grouped withan Area command, Group and Join commands, or Merge commandbefore being made into a symbol. (For more information about groupingobjects, see “Configuration Tools: Grouping Objects” on page 3-2-60.)The objects are then written to a Process Symbols folder as a symbol.A symbol can be written to any MTCC on the PeerWay. Figure 3.2.14shows how to create a symbol.

NOTE: The Process Graphics folder contains five files of commonlyused graphic icons, such as valves, motors, boilers, and other processsymbols. You can select preconfigured icons from the following files tocreate process symbols:

D $Readme

D $Stdsym

D $SymbolS1

D $SymbolS2

D $SymbolS3

CC: 3-2-20




- To create a new symbol:1. Select one object in a

group.

2. Cursor to the “Files” fieldand press [SELECT].

3. Cursor to the “Symbol” field.4. Type in a comma (,) and the

desired symbol name.

A symbol can be copied toanother disk by entering:volume,symbolname

The “Link Count” field displays thenumber of blocks/addresses thatare configured on the graphic.

Top Menu

Type�THINGMove GroupCopyLimits LinkEdDelete TopUndo Bottom

AreaClose Files

File Operations

Read�volume,filename.pg

Write�volume,filename.pg

Symbol�Close Link Count

Figure 3.2.14. Creating a New Symbol

CC: 3-2-21


Creating Shapes:Shapes that Fill Up in Response to a Block Variable

The Box, Circle, Arc, and Triangle shapes can be configured as solidshapes that fill up in response to a block variable. Other objects can beplaced on top of a shape, and shapes can be combined to fill up acomplex shape, as shown in Figure 3.2.16.

- To create a shape that fills up in response to a block variable:

1. Call up the Edit Object Menu for the shape. Cursor to the“Option” field and press [SELECT]. The Option Menu appears, asshown in Figure 3.2.15.

2. Use the [NEXT OPTION] key to access the “Option” fieldchoices. Enter the desired option. Close the menu.— FillN indicates that the object fills from bottom to top.— FillS indicates that the object fills from top to bottom.— FillE (Box only) indicates that the object fills from left to right.— FillW (Box only) indicates that the object fills from right to left.When one of the fill options is configured, the “Link”, “Empty”,and “Full” fields appear on the Edit Object Menu.

3. Cursor to the “Link” field and press [SELECT]. The Link Menuappears. Enter the desired block variable. Close the menu.

4. The default scaling values are “Empty�.00%” and“Full�100.00%”. If other “Empty” or “Full” values are desired,cursor to one of those fields and press [SELECT]. The ScalingMenu appears.

The “Empty” field indicates the percent value of the blockvariable that is shown as an empty shape. For example, if“Empty�25.00%” is configured, the shape appears empty (noshape is shown) until the block variable value is 25.00% of theblock variable range.

The “Full” field indicates the percent value of the block variablethat is shown as a full shape. For example, if “Full�75.00%” isconfigured, the shape appears full (the entire shape is shown)when the block variable value is 75.00% of the block variablerange.

CC: 3-2-22


Edit Object

Type BOX Option�FillNCond�Color�white 1n Blink�NOLink�Empty�.00% Full�100.00%Resize RotateClose Undo Top Menu

Determines the tag oraddress of the blockvariable that is linkedto the fill function.

Determine the scaling ofthe fill function.

Determines the fill option.

Figure 3.2.15. Edit Object Menu for Creating a Shape that Fills Up in Response to a Block Variable

PRODUCT

Other objects can beconfigured on top of the fillshape.

Multiple fill shapes can beput together to form anintricate fill function.

Box object with“Option�FillN”“Full�75.00%”“Empty�25.00%”

Arc object with“Option�FillN”“Full�100.00%”“Empty�75.00%”

Arc object with“Option�FillN”“Full�25.00%”“Empty�.00%”

Figure 3.2.16. Examples of the Ways that Shapes Can Be Used

CC: 3-2-23


Creating Shapes:Multicolor Shapes

The Box, Circle, Arc, and Triangle shapes can be configured to fill inmore than one color. One multicolor object is configured from oneControlBlock variable.

Figure 3.2.17 and Figure 3.2.18 show an example of configuring amulticolor shape with the Edit Object Menu and the Edit Links Menu.

Edit Object

Type BOX Option�Multi NCond�

Block� Edit LinksEmpty�.00% Full�100.00%Resize

RotateClose Undo Top Menu

Determines the multicolor options:� Multi N to indicate that the object fills from bottom to top.� Multi S to indicate that the object fills from top to bottom.

Determines the tag oraddress of the blockvariable that the edit linkscome from.

Determines the scaling ofthe fill function.

Determines the order andcolor of the layers in theobject.

Box object with“Multi N” option.

Figure 3.2.17. Multicolor Shape and Edit Object Menu

CC: 3-2-24


Edit Object

Type BOX Option�Multi NCond�

Block�9A-99 Edit LinksEmpty�.00% Full�100.00%Resize Rotate

Close Undo Top Menu

Highlight “Edit Links“ and press[SELECT] to call up the EditLinks Menu.

The “Color Input“ can be anormal color combinationfrom the Master ColorSelection screen or thecolor of a continuous blockinput (A through O).

The “Scaling Input“ must be a continuousblock input (A through O). Links areconfigured on the Continuous Linksscreen of the ControlBlock. ScalingInputs are layered in the order in whichthey are configured on the Edit LinksMenu.

Up to 15 continuous links from oneblock variable can be selected on theEdit Links Menu.

As an example, if the tank is configured as 0--200gallons:

Link A (with a value of 150 gallons) is listed first.

Link E (with a value of 50 gallons) is listed second.

Link F (with a value of 30 gallons) is listed third.

Edit Links

Color Input�2n Scaling Input�A

Color Input�5n Scaling Input�E

Color Input�G Scaling Input�F

Color Input� Scaling Input�

Color Input� Scaling Input�

Close Next

Figure 3.2.18. Example of a Multicolor Shape with Edit Links Menu

CC: 3-2-25


Creating Objects That Display Block Information:Tag, Blkdes, Mode Objects

Block information such as tag, descriptor, and operating mode can bedisplayed on a process graphic. Table 3.2.3 describes the objects thatdisplay block information.

Table 3.2.3. Objects that Display Block Information

Object Description

Blkdes Displays the descriptor of a block, for example “INLET FLOW VALVE”, “Producttemperature”.

Mode Displays the mode of a block, for example “>AUTO”, “>MANUAL”.

CC: 3-2-26


- To create the Tag, Blkdes, or Mode object:

1. Move the cursor to the desired location of the object. Press[SELECT]. The Top Menu appears.


3. Move the cursor to the appropriate field and press [SELECT].

The Edit Object Menu appears. Figure 3.2.19 shows how theTag, Blkdes, and Mode objects appear in configuration mode.

4. If you want, modify the characteristics of the object using the EditObject Menu.

MODE

BLKDES


TAG

Figure 3.2.19. How the Tag, Blkdes, and Mode Objects Appear in Configuration Mode

CC: 3-2-27


- To configure the Tag, Blkdes, and Mode object characteristics:

1. The characteristics of an object are determined by the fields onthe Edit Object Menu, as shown in Figure 3.2.20 and Table 3.2.4.Move the cursor to the desired field and press [SELECT].Another menu appears.

2. Move the cursor to the desired field. The field entry may bechanged by using the [NEXT OPTION] key, if possible, or bytyping the desired entry. Press [ENTER].

Edit Object Menu

Type Tag Num Col� 8Cond�Color� White 1n Blink� NoBlock� Split� NoFont�

Close Top Menu

Figure 3.2.20. Edit Object Menu for the Tag, Blkdes, and Mode Objects

Table 3.2.4. Screen Fields on the Edit Object Menu for the Tag, Blkdes, and Mode Objects

Field Description


Block Determines the tag or address of the block that provides the information for theobject.


Cond Determines a condition that affects how the object is displayed. See “Configuring theAppearance of Objects to Change” on page 3-2-54.

Font

Determines the font size of the displayed charactersD “Normal” indicates normal size.

D “Small” indicates half-size -- half the width and half the height.

Num Col Determines the width of the object, in columns. A column is the width of a standardcharacter.

SplitLets you determine whether a tag should be split. If you choose not to split the tag,the window displays the “Num Col” field, and you must then specify the number of tagcharacters to display.

CC: 3-2-28


Creating Objects That Display Block VariableInformation in Character Form:Links, Units, Disc Objects

Block variable information can be displayed on a process graphic incharacter form as text. Table 3.2.5 describes the objects that displayblock variable information in character form.

Table 3.2.5. Objects that Display Block Variable Information in Character Form

Object Description

Link Displays the value of a block variable.

Units Displays the units of a block variable, for example “GPM”, “DEG C”.

DiscDisplays one line of a discrete faceplate. If the line is operator--enterable on thefaceplate, it is also operator--enterable on the graphic display. For an example on theuse of the Disc object, see “Creating Data Entry Fields” on page 3-2-53.

CC: 3-2-29


- To create the Link, Units, or Disc object:




The Edit Object Menu appears. Figure 3.2.21 shows how theLink, Unit, and Disc objects appear in configuration mode.



LINK

UNITS

DISC

Figure 3.2.21. How the Link, Units, and Disc Objects Appear In Configuration Mode

CC: 3-2-30


- To configure the Link, Units, and Disc object characteristics:

1. The characteristics of an object are determined by the fields onthe Edit Object Menu, as shown in Figure 3.2.22 and Table 3.2.6.Move the cursor to the desired field and press [SELECT].Another menu appears.


Edit Object Menu

Type Disc Num Col�8Cond�

Block� Index�Font�Normal

Close Top Menu

Figure 3.2.22. Edit Object Menu for the Link, Units, and Disc Objects

Table 3.2.6. Screen Fields on the Edit Object Menu for Link, Units, and Disc Objects

Field Description

Block Determines the tag or address of the block or link that provides the information for theobject.


Font

Determines the font size of the displayed characters.D “Normal” indicates normal size.


Index

(Disc only) Determines which of the 17 lines in the discrete faceplate is displayed. If aline on the discrete faceplate is operator enterable, the same line displayed on theProcess Graphic is also operator enterable. See “Creating Data Entry Fields” on page3-2-53.

Num Col Determines the maximum number of characters to be displayed.

CC: 3-2-31


Creating Objects That Display Block VariableInformation in Graphic Form:Hdev, Vdev, Ticbar Objects

Block variable information can be displayed on a process graphic ingraphic form. Table 3.2.7 describes the objects that display blockvariable information in graphic form.

Table 3.2.7. Objects that Display Block Variable Information in Graphic Form

Object Description

Hdev Displays a bar that travels horizontally from a center vertical axis. The bar representsthe difference between two ControlBlock variables.

Vdev Displays a bar that travels vertically from a center horizontal axis. The bar representsthe difference between two ControlBlock variables.

Ticbar Displays a horizontal line with travel along a vertical axis. The line shows the value ofa block variable.

CC: 3-2-32


- To create the Hdev, Vdev, or Ticbar object:



3. Move the cursor to the appropriate field and press [SELECT].The Edit Object Menu appears. Figure 3.2.23 shows how theHdev, Vdev, and Ticbar objects appear in configuration mode.


HDEV

HDEV


VDEV

VDEVTIC-BAR

Figure 3.2.23. How the Hdev, Vdev, and Ticbar Objects Appear in Configuration Mode

CC: 3-2-33


How the Hdev and Vdev Objects Are Displayed

Figure 3.2.24 shows how the Hdev and Vdev objects are displayed on aprocess graphic.

The outline represents thesize of the object. The outlineis not visible in the viewingmode.

A bar to the right of the center linerepresents a positive deviationvalue. (Plus Input > Minus Input)

A bar that extends to theedge of the object representsa value of 50% of the“Range” field.

A bar to the left of the center linerepresents a negative deviationvalue. (Plus Input < Minus Input)

Graphics ViewingThe Hdev object displaysa bar. The bar representsthe difference betweentwo block variables. The Vdev object

displays a bar. The barrepresents thedifference between twoblock variables.

A bar below the center line representsa negative deviation value.(Plus Input < Minus Input)

A bar above the center linerepresents a positive deviationvalue. (Plus Input > Minus Input)

Hdev

Vdev

Figure 3.2.24. How the Hdev and Vdev Objects Appear in Viewing Mode

CC: 3-2-34


The characteristics of an object are determined by the fields on the EditObject Menu, as shown in Figure 3.2.25 and Table 3.2.8.

- To configure the Hdev and Vdev object characteristics:

1. Move the cursor to the desired field and press [SELECT].Another menu appears.


Edit Object Menu

Type HDEV Size� �Cond�Color�white 1n Blink�NOBlock�Offset�.00% Range�100.00%Plus Input�B Minus Input�AClose Undo Top Menu

Figure 3.2.25. Edit Object Menu for the Hdev, Vdev, and Ticbar Objects

Table 3.2.8. Screen Fields on the Object Edit Menu for the Hdev, Vdev, and Ticbar Objects

Field Description


Block Determines the tag or address of the block that provides the variable values.



RangeDetermines the range of the deviation. The range is specified as a per cent value ofthe Plus Input block variable range. A range of 100% displays a deviation of 50% ofthe Plus Input block variable range in each direction.

Minus InputDetermines the minus input.The object displays: (Plus Input) - (Minus Input)

Offset Determines the percent value that the deviation is offset from 0.

Plus Input Determines the plus input. The object displays:(Plus Input) - (Minus Input)

Size

Determines the size of the object.D “Num Col” indicates the width of the object in number of columns. A column is

the width of a standard character.

D “Num Row” indicates the height of the object in number of rows. A row is theheight of a standard character.

CC: 3-2-35


How the Ticbar Object is Displayed

Figure 3.2.26 shows how the Ticbar object is displayed on a processgraphic.

The outline represents thesize of the Ticbar object.The outline is not visible inthe viewing mode.

A horizontal line at the bottom ofthe Ticbar object represents the“Empty” field value configured onthe Ticbar Edit Object Menu.

A horizontal line at the top ofthe Ticbar object representsthe “Full” field valueconfigured on the Ticbar EditObject Menu.

Graphics Viewing

The Ticbar object displaysa horizontal line. The linerepresents the value of ablock variable.

Figure 3.2.26. How the Ticbar Object Appears in Viewing Mode

CC: 3-2-36



- To configure the Ticbar object characteristics:



Edit Object Menu

Type TICBAR Size� �Cond�Color�white 1n Blink�NOLink�Empty�.00% Full�100.00%

Close Undo Top Menu

Figure 3.2.27. Edit Object Menu for the Hdev, Vdev, and Ticbar Objects

Table 3.2.9. Screen Fields on the Edit Object Menu for the Hdev, Vdev, and Ticbar Objects

Field Description




Size

Determines the size of the object.D “Num Col” indicates the width of the object in number of columns.

D “Num Row” indicates the height of the object in number of rows.

Full Determines the percent value of the block variable range that represents the top ofthe Ticbar object.

Empty Determines the percent value of the block variable range that represents the bottomof the Ticbar object.

Link Determines the tag or address of the link that provides the variable values.

CC: 3-2-37


Creating Objects That Display Faceplates:Group, Unit, Overview Objects

Faceplates can be configured as permanent parts of a process graphicdisplay. Table 3.2.10 describes the objects that display faceplates.

Table 3.2.10. Objects that Display Faceplates

Object Description

Group Displays a full--sized ControlBlock faceplate, as shown on a group display.

Unit Displays a ControlBlock faceplate from a unit display.

Overview Displays a ControlBlock faceplate from an overview display.

CC: 3-2-38


- To create the Group, Unit, or Overview object:




The Edit Object Menu appear. Figure 3.2.28 shows how theGroup, Unit, and Overview objects appear in configuration mode.



UNITUNITUNITUNIT

GROUPGROUPGROUPGROUPGROUPGROUPGROUPGROUPGROUPGROUP

OVERVIEWOVERVIEW

Figure 3.2.28. How the Group, Unit, and Overview Objects Appear in Configuration Mode

CC: 3-2-39


The characteristics of an object are determined by the fields on the EditObject Menu, as shown in Figure 3.2.29.

- To configure the Group, Unit and Overview objectcharacteristics:



Edit Object Menu

Type Group Option�AnalogCond�

Block�

Close Top Menu

Determines the tag oraddress of the blockthat provides thefaceplate.

Determines a condition that determineswhether the object is displayed. See“Configuring the Appearance of Objectsto Change” on page 3-2-54.

Determines the type of faceplate:D “Analog” indicates the block continuous

faceplate.

D “Discrete” indicates the block discretefaceplate.

Figure 3.2.29. Edit Object Menu for the Group, Unit, and Overview Objects

CC: 3-2-40


Displaying a Faceplate from a Process Graphic Object

A process graphic object that is interactive with a ControlBlock can beused to display the ControlBlock faceplate temporarily, as shown inFigure 3.2.30. If a ControlBlock is interactive with a process graphicobject, the faceplate for that block can be displayed by cursoring to theobject and pressing [SELECT]. The Continuous Faceplate screen forthe ControlBlock can be called up by pressing [SELECT] again.

A ControlBlock faceplate can be displayed from the following graphicobjects: Tag, Blkdes, Mode, Link, Disc, Ticbar, Hdev, Vdev, Group, Unit,Overview, Trend, and Target. A faceplate can also be displayed fromBox, Circle, Triangle, and Arc objects that have a fill option configured.

FLV-2A

Flow Temperature #1

>AUTO

FLV-2A

GPM76.0073.000.000.00

99.0

GallonsAUTO

PRO1PU004

GRAPHICS VIEWING

- To display the faceplate for the block:D Cursor to the object and press [SELECT].

The faceplate appears on the side of the graphics screen.The [EXCH] key can be used to view the other blockfaceplate.

- To call up the Continuous Faceplate screen for theblock:

D Cursor to the faceplate and press [SELECT].

Figure 3.2.30. Displaying a ControlBlock Faceplate from a Process Graphic Object

CC: 3-2-41


Creating Objects That Display Trend Information:Trend Object

Block variable information from a trend file can be displayed on aprocess graphic using the Trend object.

- To create the Trend object:

1. Move the cursor to the location on the fabric where the objectshould be. Press [SELECT]. The Top Menu appears.



The Edit Object Menu appears. Figure 3.2.31 shows how theTrend object appears in configuration mode.

4. If you want, edit the characteristics of the object using the EditObject Menu.


TREND TRENDTREND TRENDTREND TRENDTREND TREND

Figure 3.2.31. How the Trend Object Appears in Configuration Mode

CC: 3-2-42



- To configure the Trend object characteristics:



Edit Object Menu

Type Trend Size� �Cond�Color�white 1n Blink�NOLink� File�Low� High�Freq.� Slidewire�Close Top Menu

Figure 3.2.32. Edit Object Menu for the Trend Object

CC: 3-2-43


Table 3.2.11. Screen Fields on the Edit Object Menu for the Trend Object

Field Description




File Determines the trend file that contains the desired information. Expressed as:node # / trend file # (for example, =28/1).

FreqDetermines how often data is added to the Trend object. This value can be greaterthan or equal to the ”Frequency” field on the Trend File Configuration screen for theblock variable.

High Determines the percent value of the block variable range that represents the top ofthe Trend object.

Link Determines the link that provides the trend values.

Low Determines the percent value of the block variable range that represents the bottomof the Trend object.

Size

Determines the size of the object.D “Num Col” indicates the width of the object in number of columns. A column is

the width of a standard character.

D “Num Row” indicates the height of the object in number of rows. A row is theheight of a standard character.

SlidewireDetermines the slidewire group. All trend objects with the same slidewire number arelinked together. If a slidewire is used on one object, a slidewire shows on all objects inthe group.

CC: 3-2-44


How the Trend Object is Displayed

Figure 3.2.33 shows how the Trend object is displayed on a processgraphic. Figure 3.2.34 shows how the Trend object slidewire featureoperates.

The outline represents thesize of the Trend object. Theoutline is not visible in theviewing mode.

The Trend object displays a line. The linerepresents block variable values from atrend configuration file.

The “Freq” field on the Edit ObjectMenu determines how frequentlydata values are entered on theTrend object.

The “Low” field on the Edit ObjectMenu determines the value of thebottom of the Trend object. The“Low” field entry is expressed as apercentage of the block variablerange, which is specified on theControlBlock Links screen.

The “High” field on the Edit Object Menu determinesthe value of the top of the Trend object. The “High”field entry is expressed as a percentage of the blockvariable range, which is specified on the ControlBlockLinks screen.

The amount of time displayed bya Trend object is equal to the“Freq” field times number ofcolumns wide.

Graphics Viewing

Figure 3.2.33. How the Trend Object is Displayed

CC: 3-2-45


SLIDEWIRE: a feature thatallows the user to view numerictrend data for a Trend object.

233.5

08:32:33

233.5

08:32:33

51.3

08:32:33

1225

08:32:33

When the cursor is movedinto the Trend object, theslidewire appears.

Along with theslidewire, a time andnumeric value are alsodisplayed.

When a slidewire is used on one ofthese objects, slidewires appear on allobjects in the group.

All Trend objects with thesame “Slidewire” field entryon the Edit Object Menu aregrouped together.

Graphics Viewing

Figure 3.2.34. Slidewire Feature of the Trend Object

CC: 3-2-46


Creating Displayed Text:Text Object

Text can be displayed on a process graphic with the Text object. TheText object consists of one line containing up to 72 characters.

- To create the Text object:

1. Move the cursor to the desired location where the text shouldbegin. Press [SELECT]. The Top Menu appears.


3. Move the cursor to the “Text” field and press [SELECT]. The EditObject Menu appears. Even though the Text object is nowcreated, nothing appears on the screen until characters areentered in the “Edit Text” field of the Edit Object Menu.

4. Type the characters to go into the text next to the “Edit Text” field.


- To configure the Text object characteristics:

The characteristics of an object are determined by the fields on theEdit Object Menu, as shown in Figure 3.2.35 and Table 3.2.12.



Edit Object Menu

Type Text Option�NormalCond�Color�white 1n Blink�NOCommand�Font�Normal Edit Text

Close Top Menu

Figure 3.2.35. Edit Object Menu for the Text Object

CC: 3-2-47


Table 3.2.12. Screen Fields on the Edit Object Menu for the Text Object

Field Description




Command

Determines a command that is executed if [SELECT] is pressed when the cursor ison the object. The command can be any combination of keystrokes that can beentered at the command line, or the number of an Anchor object. See the “CreatingObjects That Call Up Other Displays” heading in this section.

Edit Text Allows text to be entered.

Font



Option

Determines how the text is displayed:D “Normal” indicates that the text covers any object below it.

D “Clear” indicates that objects below the text show through.

CC: 3-2-48


Displaying Alarms:Alarm Object

The Alarm object provides access to alarms from a process graphic.The operator can view and acknowledge alarms from the graphic. Youcan configure the Alarm object to read console RAM lists, including theEvent Lists.

- To create the Alarm object:




The Edit Object Menu appears. Figure 3.2.36 shows how theAlarm object appears in configuration mode.


Figure 3.2.37 shows how the Alarm object is used in a process graphic.Table 3.2.13 describes the fields on the Alarm object Edit Object Menu.For more information about configuring alarms, see CC: 6.


ALARM

Figure 3.2.36. How the Alarm Object is Displayed

CC: 3-2-49


ALARMS 2

ALARM ACK UP DN TOP# 1Occur Tag18:46:11 =19A Controller Not Backed Up18:45:40 =19A Controller Not Backed Up18:45:18 =18 Alarm logging Enabled18:45:16 =18 Trend Recording Disabled18:45:04 =18 Node Restarted18:44:42 LIC-20/PV Drum Level High Critical 12.64Ft.18:43:30 =19A Controller Not Backed Up

***MORE***

- To call up the faceplatefor a block:

D Press [SELECT]on the process alarm.

- To see more alarms:D Cursor to DN and

press [SELECT]to see the previousalarms.

D Cursor to UP andpress [SELECT]to see the next alarms.

When the cursor is inside the alarmwindow on the [ALARM ACK] key, the[ALARM ACK] key acts only on the

alarms in the window.

- To suppress an alarm:D Cursor to the alarm and

press [s].

- To acknowledge alldisplayed alarm:

D Cursor to[ALARM ACK]and press [a].

The Alarm object titleshows the alarm conditionof the highest priorityalarm in the object.

- To see a specific alarm:D Cursor to TOP# and

enter the row no. (from 1to the scan limit) of thedesired alarm.

- To see the last alarm:

D Cursor to TOP# andenter a row no. that islarger than the currentno. of alarms, but lessthan the scan limit.

- To acknowledge onedisplayed alarm:

D Cursor to the alarm andpress [a].

- To unsuppress (or enable)an alarm when viewingsuppressed alarms:

D Cursor to the alarm andpress [e].

GRAPHICS VIEWING

Figure 3.2.37. Example of Alarm Object

CC: 3-2-50


Table 3.2.13. Screen Fields on the Edit Object Menu for the Alarm Object

Field Description

Blink Specifies whether or not the object blinks.

Color Specifies the normal color of the object. The color choices are configured on theMaster Color Selection screen ([C] [C] [P] command).

Cond Specifies a condition that affects how the object is displayed.

Display Format

Specifies display parameters.Ack Time Specifies whether the acknowledge time appears in alarm entries.

Clear Time Specifies whether the clear time appears in alarm entries.

Date Specifies whether the date appears in alarm entries.Desc Specifies whether the block descriptor appears in alarm entries.

List Specifies when the alarm list appears.

Active =When there are active alarms in the alarm list.Any =When there are any alarms in the alarm list.

Always =Always.

NOTE: Never is no longer an option. If the alarm List option waspreviously configured as Never, Never will appear until youreconfigure the alarm List option.

Occur Time Specifies whether the occur time appears in alarm entries.Tag Specifies whether the tag appears in alarm entries.

Title Specifies when the title appears.Never =neverActive =only when there are active alarms in the alarm list

Any =only when there are any alarms in the alarm list

Always =always

FILT Criteria

Specifies the filter parameters of alarms to be excluded from the Alarm object display.If no parameters are configured, all alarms are included. The alarm area containingthe Alarm object must be enabled for the alarm to be displayed.

Filter parameters:unit = plant unit (1--255)

area = area name

blk = block tagpri = priority (ControlBlock: 0--15; I/O block: 0--3)

type = alarm type (hard, proc, crit, adv, batch, sys, disk, el1--el10)

state = alarm state (active, clear, unack, ack)node = node number

Figure 3.2.38 shows some examples of criteria configurations.


CC: 3-2-51


Table 3.2.13. Screen Fields on the Edit Object Menu for the Alarm Object (continued)

Field Description

FIND Criteria

Specifies which information is included in the Alarm object display. If no parametersare configured, all nonsuppressed alarms are included. The alarm area containing theAlarm object must be enabled for the alarm to be displayed.

Find parameters:unit = plant unit (1--255)

area = area name

blk = block tagpri = priority (ControlBlock: 0--15; I/O block: 0--3)

type = alarm type (hard, proc, crit, adv, batch, sys, disk, el1--el10)*

state = alarm state (active, clear, unack, ack, suppr)*node = node

ctime = cutoff time (format=dd--mm--yy/hh:mm:ss)


Scan LimitSpecifies the maximum number of matched entries of alarm information for which thealarm list is scanned. The highest allowable entry is 5000. The alarm list is scanneduntil either the scan limit or the end of the alarm list is reached.

Title The title that appears at the top of the alarm list. The title can be up to 26 characterslong.

Window Size

Specifies how big the alarm object is when the alarm list is displayed. The maximumsize is 82 columns wide and 20 rows high. The Alarm object that appears on theProcess Graphic Generation screen shows the upper left location of the Alarmobject—it does not represent the actual size of the object.NOTE: In order to enter a number in the TOP# field, or to use [a] to acknowledgealarms, [s] to suppress an alarm, or [e] to unsuppress an alarm, the Alarm objectmust be at least 40 columns.

CC: 3-2-52


FIND:Find Crit>unit=1-6;

| >

| >

FILTER:Filt Crit>state=unack

| >

| >

This configuration specifies that the Alarmobject displays all alarms from plant units 1through 7.

Find Crit>unit=1-7;

Find Crit>area=boiler1,boiler2This configuration specifies that theAlarm object displays all alarms fromalarm areas “boiler1” and “boiler2”.

Find Crit>area=boiler1

| >blk=TEMP1

| >

Find Crit>area=boiler1& type=critThis configuration specifies that the Alarmobject displays all critical alarms from alarmarea boiler1.The & represents a logical and operation.

Find Crit>area=boiler1 | blk=TEMP1

Both of these configurations specify thesame criteria—that the Alarm objectdisplays all alarms from alarm area boiler1and from block TEMP1.The | represents a logical or operation.

This configuration specifies that the Alarmobject displays all alarms from plant units 1through 6, but excludes unacknowledgedalarms.

Figure 3.2.38. Examples of Criteria Configurations

CC: 3-2-53


Creating Data Entry Fields: Disc Object

The configuror can use the Disc object to create fields on the processgraphic display that allow the operator to enter data and to turn deviceson and off. The Disc object displays a line from a ControlBlock discretefaceplate. If the line is operator--enterable on the faceplate, it is alsooperator--enterable on the process graphic.

Figure 3.2.39 shows two examples of Disc objects used as data entryfields. The top DISC object allows the operator to start a motorcontrolled by a DMC ControlBlock. The lower Disc object allows theoperator to change a bias setting.

1 OPERATOR2 > start3 > stop45 --AUTO--6 start7 stop89 -------10 on cfrm11 offcfrm12 tripped1314 -OUTPUT-15 run16 STOP17 failed

Edit Object Menu

Type DISC Num Col�8Cond�

Block�DMC-4 Index�2Font�Normal

Close Undo Top Menu

12 112.553 GPM456 > 12.007 GPM BIAS891011121314151617

Edit Object Menu

Type DISC Num Col�8Cond�

Block�BIAS-1 Index�6Font�Normal

Close Undo Top Menu

GRAPHICS VIEWING

>start

>12.00

BIAS--1

DMC--4

Figure 3.2.39. Example Data Entry Fields

CC: 3-2-54


Configuring The Appearance of Objects to Change,Depending on the State of a Discrete Block Variable

Most process graphics objects can be configured to appear in twoforms, depending on the true/false condition of a discrete block variable.

Figure 3.2.40 shows how to configure the appearance of an object tochange.

Edit Object

Type BOX Option�OutlineCond�Color�white 1n Blink�NO

Close Top Menu

- To configure an object to change:1. Call up the Edit Object Menu for the

object. Move the cursor to the “Cond”field and press [SELECT].

2. The Condition Menu appears. Enter atrue/false block variable condition inthe “Cond” field.

For example, =1A--3/b indicates thatthe condition is met when logic step bof ControlBlock =1A--3 is true.

The entry =1A--3/b indicates that thecondition is met when logic step b ofControlBlock =1A--3 is false. The blockvariable can be entered by address ortag.

3. Close the Condition Menu.

Condition

Cond�FIC-101/aClose

Figure 3.2.40. Configuring the Edit Object Menu for Conditional Display of Objects(continued on next page)

CC: 3-2-55


Edit Object

Type BOX Option�OutlineCond� Chg�--erase--Color�white 1n Blink�NO

Close Top Menu

These fields determine the displaycharacteristics of the object when thecondition is not met.

The default condition is “----erase----”, whichmeans that the object is not displayed at allwhen the condition is not met.

The Group, Unit, Overview, Pagefrwd, andPageback objects do not have a ”Chg” field.If the condition is not met, the object is notdisplayed.

These fields determine thedisplay characteristics of theobject when the condition ismet.

4. When the “Cond” field is configured, the “Chg” fieldappears on the Edit Object Menu.

To change any of these display characteristics:D Cursor to the “Color”, “Blink”, or “Chg” field and press

[SELECT]. The Select Color Menu appears.Configure the true and false conditions as you wantthem to appear.

Select Color

Color�white 1n Blink�NO

Chg -�-erase-- Blink�NOClose

Figure 3.2.40. Configuring the Edit Object Menu for Conditional Display of Objects

CC: 3-2-56


Configuration Tools:Moving and Copying Objects

Figure 3.2.41 shows how to move and copy graphic objects.

NOTE: If you copy an Area that includes overlapped objects, thetop/bottom arrangement of the objects may change.


TAG

- To move or copy an object:1. Call up the Top Menu for the object.

2. Move the cursor to the desiredoperation (Move or Copy). Press[SELECT].

3. Move the cursor to the desiredlocation of the new object. The outlineof the object follows the cursor. Press[SELECT].

4. To undo the last operation, move thecursor to the “Undo” field on the TopMenu and press [SELECT].

Top Menu

Type�TAGMove GroupCopyLimits LinkEdDelete TopUndo Bottom

AreaClose Files

Figure 3.2.41. Moving and Copying an Object

CC: 3-2-57


Configuration Tools:Deleting Objects

Figure 3.2.42 shows how to delete graphic objects.

PROCESS GRAPHIC GENERATION 02-Feb-96 09:49:12- To delete an object:

1. Call up the Top Menu for the object.

2. Move the cursor to the “Delete” field.Press [SELECT]. The object is nowdeleted and the Top Menu with“Type�None” is displayed.

- To undo the last operation:D Move the cursor to the ”Undo” field on the

Top Menu and press [SELECT].

Top Menu


AreaClose Files

TAG

Figure 3.2.42. Deleting an Object

CC: 3-2-58


Configuration Tools:Stacking Objects—Top and Bottom Operations

You can place an object at the top or bottom of a stack using the topand bottom operations. Figure 3.2.43 shows how the top and bottomoperations are used. Figure 3.2.44 shows an example of two Boxobjects in a stack to form a tank.

Top Menu


AreaClose Files

Top Menu


AreaClose Files


TAGTAG


TAGTAG

Figure 3.2.43. Stacking Objects Using the Top and Bottom Operations

CC: 3-2-59


Configuration Tools:Example of Stacking Objects


Edit Object Menu

Type BOX Option�OutlineCond�Color�cyan Blink�NO

Close Undo Top Menu


Edit Object Menu

Type BOX Option�FillNCond�Color�White 1n Blink�NOLink�FIC-101/A

Close Undo Top Menu

- Example: Configuring a tank by stacking oneobject on another :

1. Select a point on the fabric.

2. Create a Box object with “Option�Outline”.3. Close the Edit Object Menu.

4. Move the cursor back to the Box object.5. Press [SELECT] so that the Box object is

selected.

6. Press [SELECT] again so that the Top Menudisplays “Type�NONE”.

7. Create a Box object with “Option�FillN”. Entera block variable in the “Link“ field.Two objects have been created in the samelocation to create a tank that fills up in responseto an input. One object forms the outline, theother forms the solid shape.

Figure 3.2.44. Creating an Object Superimposed on Another Object

CC: 3-2-60


Configuration Tools:Grouping Objects

Process graphics contains tools for grouping objects together.Table 3.2.14 lists the operations that can be used to group graphicobjects and the typical uses for each operation.

Table 3.2.14. Grouping Operations

Operation Description

Area

The Area operation draws a box around the objects that are to be groupedtogether. The objects are grouped together for one operation only.

The Area operation is typically used when only one operation is to be performedon the set of objects, or when the set of objects is so large that using the Groupand Join operations are cumbersome.

Group and Join

The Group operation identifies an object as the first object in a group. The Joinoperation joins other objects to the group. Once joined in a group, objectsremain in the group until the Split operation is used to split them from the group.Multiple operations can be performed on the group.The Group and Join operations are typically used when multiple operations areto be performed on a set of objects, or when other operations may beperformed on the set of objects in the future.

MergeThe Merge operation is used to join a set of shape objects into a single objectcalled a Thing.

The Merge operation is typically used to create symbols.

CC: 3-2-61


Configuration Tools:Grouping Objects—Area Operation

A set of objects can be put into a temporary group with the Areaoperation to perform display operations more efficiently, as shown inFigure 3.2.45. Objects that are grouped with an Area operation aretreated as a group only for the next operation. If a Move, Copy, orDelete operation is performed on one object in a group, the operation isperformed on all objects in the group. After the operation is performed,the objects are no longer in a group (unless the next operation is anUndo, in which case the Undo operation applies to the group). If anArea operation is attempted on a Thing object, all components of theThing must be included in the Area.

CC: 3-2-62


Top Menu

Type�NONE

Limits

AreaClose Files



X

+

X

LINK

TAG

- To join objects into a temporary group:1. Cursor to a location that will be one

corner of the area and press[SELECT].

2. Cursor to the “Area” field on the TopMenu and press [SELECT].

Top Menu

Type�NONE

Limits

AreaClose Files

LINK

TAG

3. Move the cursor to the oppositecorner of the desired area, drawinga box around the desired objects.Press [SELECT].

NOTE: If an object is part of a permanentgroup, all objects in that group must beincluded in the box. Otherwise, no part ofthat group will be included in the area.

Figure 3.2.45. Joining Objects into Groups with the Area Operation

CC: 3-2-63


Configuration Tools:Grouping Objects—Group and Join Operations

Objects can be joined into permanent groups with the Group and Joinoperations to perform display operations more efficiently. If a Move,Copy, or Delete operation is performed on one object in a group, theoperation is performed on all objects in the group. There are differentmenu paths for joining single objects or joining groups of objects.

Joining Single Objects

Once the Group command has been invoked, a single graphic objectwill always display the Top Menu with the Join command, while groupedobjects will display the Split command in the same field. Join singleobjects to a group as shown in Figure 3.2.46.

Top Menu

Type�TAGMove GroupCopy JoinLimits LinkEdDelete Top

BottomArea

Close Files

Top Menu

Type�LINKMove GroupCopyLimits LinkEdDelete Top

BottomArea

Close Files


TAG

LINK


- To join single objects into a group:1. Cursor to the first object that is to

be part of the group and press[SELECT].

2. Cursor to the “Group” field on theTop Menu and press [SELECT].

3. Cursor to the next object that is to bepart of the group. Press [SELECT].

4. Cursor to the “Join” field on the TopMenu and press [SELECT]. The objectis now joined to the group of objects.

5. Repeat steps 3 and 4 for all objects thatare to be part of the group.

NOTE: Single objects can be added to thegroup at a later time by doing steps 1 and 2for any existing object in the group, and thendoing steps 3 and 4 for the new object.TAG

LINK

Figure 3.2.46. Joining Single Objects into Groups

CC: 3-2-64


Joining Groups of Objects

To join two or more groups of graphic objects, you must join them asindividual elements, as shown in Figure 3.2.47 and Figure 3.2.48.


TAG

LINK


- To join groups of objects together:1. For each object in one group,

cursor to each object and press[SELECT].

2. Cursor to the “Split” Field on theTop Menu and press [SELECT].

NOTE: To minimize the number ofcommands, you should split the smallergroup.

LINK

TAG

3. Cursor to one element of the largergroup and press [SELECT].

4. Cursor to the “Group” field on theTop Menu and press [SELECT].

NOTE: Always use the Group commandat the destination, and not at the elementyou wish to group.

TAG

TEXT

TAG

TEXT Top Menu

Type�LINKMove GroupCopy SplitLimits LinkEdDelete Top

BottomMerge AreaClose Files

Top Menu

Type�TAGMove GroupCopy SplitLimits LinkEdDelete Top

BottomMerge AreaClose Files

Group

Group

Group

Group

Figure 3.2.47. Joining Groups of Objects

CC: 3-2-65


Top Menu

Type�TAGMove GroupCopy JoinLimits LinkEdDelete Top

BottomArea

Close Files


TEXT

TAG5. Return to the group you split. For

each element you wish to connectto the larger group, cursor to the“Join” field and press [SELECT].

LINK

TAG

Group

Figure 3.2.48. Joining Groups of Objects

CC: 3-2-66


Configuration Tools:Grouping Objects—Merge Operation

A group of shape objects can be merged into a Thing object. To bemerged, a set of shape objects must have been joined into a permanentgroup using the Group and Join operations. The objects must havesimilar configuration characteristics, such as “Color” and “Cond” fields.

Thing objects are typically used to create symbols (see “CreatingSymbols” on page 3-2-19 for more information). A set of objects that aremerged into a Thing object takes up less memory than the same set ofobjects that are joined into a group.

When the Merge operation has been performed on a group of shapeobjects, a Thing object has been created. The individual shape objectsthat were used to create the Thing object no longer exist and cannot besplit apart. The Thing object has one Top Menu and one Edit ObjectMenu.

Figure 3.2.49 shows how to merge a group of shape objects into aThing object.


Top Menu

Type�BoxMove GroupCopyLimits SplitDelete TopUndo BottomMerge AreaClose Files

- To merge objects into a permanent group (a Thing object):1. Cursor to an object in the group and press [SELECT].

2. Move the cursor to the “Merge” field of the Top Menu andpress [SELECT].

Figure 3.2.49. Merging a Group into a Permanent Thing Object

CC: 3-2-67


Configuration Tools:Using the Link Editor Field

The LinkEd field allows portions of process graphics to be linked todifferent ControlBlock addresses. You can use the LinkEd option toassign part of a process graphic to a different controller. The LinkEdoption makes it easy to duplicate a new unit, such as a reactor, or anArea containing several units. Select the original, copy it, and use aLinkEd to change the controller(s) that are used in the copy. SeeFigure 3.2.50 for an example of the LinkEd field. Table 3.2.15 describesthe LinkEd functions.

The LinkEd option is different from other options in the following way:

D The Move field moves objects on the same fabric.

D The Link Editor screen (seeNO TAG) allows whole graphicsfabrics (rather than just pieces) to be linked elsewhere.

D The LinkEd field on the Top Menu allows objects or areas to belinked to different ControlBlock addresses. It otherwise performsthe same functions as the Link Editor screen.

PROCESS GRAPHIC GENERATION 20-DEC 96 08:22:13

- To link a selected object or areawith LinkEd:

1. Cursor to the object and press[SELECT], or bound the area thatis to be linked.

2. Cursor to the “LinkEd” field on theTop Menu and press [SELECT].

+

X

Top Menu

Type�NONEMoveCopyLimits LinkEdDelete

AreaClose Files

Figure 3.2.50. Using the LinkEd Option to Link an Area(continued on next page)

CC: 3-2-68


PROCESS GRAPHIC GENERATION 20-DEC 96 08:22:13

3. Cursor to the Source fieldand enter the source rangeof address and press[ENTER].

4. Cursor to the Destinationfield and key in the start tagor address, then press[ENTER].

5. Cursor to Proceed and press[SELECT], or Close toCancel the operation.

6. Verify that the new links arecorrect.

Top Menu

Type�NONEMoveCopyLimits LinkEdDelete

AreaClose Files

LinkEd

Source�1A--3, =1A--5

Destination�=12B--6

Close Proceed

- The operation above performs the followingoperations:

Changes the matching links in the bounded area:

D 1A--3 becomes 12B--6D 1A--4 becomes 12B--7

D 1A--5 becomes 12B--8

Figure 3.2.50. Using the LinkEd Option to Link an Area (continued)

Table 3.2.15. LinkEd Functions

Field Description

Source Specifies the range of addresses to be changed. Separate ranges with a comma.

Destination Specifies the start of the changed (new) block addresses.

Close Closes the LinkEd menu without saving.

Proceed Changes the references to the Block(s) you specified.

NOTE: The LinkEd field changes only references to block links in theprocess graphic file. It has no effect on actual block links in the specifiedcontrollers.

CC: 3-2-69


Configuration Tools:Splitting an Object from a Group

Objects can be split from a group using the Split operation, as shown inFigure 3.2.51. The Split operation removes only the selected objectfrom the group. To break up a group completely into its individualobjects, each object must be separately split from the group using theprocedure in Figure 3.2.51.

Top Menu

Type�TAGMove GroupCopy SplitLimits LinkEdDelete TopUndo Bottom

FilesClose


- To split an object from a group:1. Cursor to the object that is to be

split from the group and press[SELECT].

2. Cursor to the “Split” field on theTop Menu and press [SELECT].

TAG

LINK

TAG

LINK

Figure 3.2.51. Splitting an Object from a Group

CC: 3-2-70


Configuration Tools:Undoing the Previous Operation

The Undo operation on the Top Menu undoes Move, Copy, Delete,Group, Join, Split, Top, Bottom, or Merge operations. The Undooperation also undoes operations made in the Edit Object Menu. Youmust perform the Undo operation immediately after the operation that isto be undone. Figure 3.2.52 shows an example of undoing a Deleteoperation.

Top Menu

Type�TAGMove GroupCopyLimitsDelete TopUndo Bottom

AreaClose Files

Top Menu

Type�TAGMove GroupCopyLimitsDelete TopUndo Bottom

AreaClose Files


LINK


LINK

By selecting the Undo operation, theDelete operation has been undone.

NOTE: The Undo operation mustimmediately follow the operation that is tobe undone.

In this example, anobject has been deleted.

TAG

Figure 3.2.52. Undoing an Operation

CC: 3-2-71


Configuring Display Characteristics:Process Graphics Fabric Coordinates

The fabric of a process graphics display is 16000 pixels high x 16000pixels wide, as shown in Figure 3.2.53. A console screen display is 640pixels wide x 448 pixels high.

0/0 0/16000

16000/1600016000/0

Graphics Viewing

Coordinates of theProcess Graphicfabric

Dimensions ofone consoledisplay

640 pixels wide

448 pixels high

Figure 3.2.53. Fabric Coordinates

CC: 3-2-72


Configuring Display Characteristics:Changing the Panning Limits and Origin Point

A process graphic has display characteristics that can be configured forthe viewing mode. When the viewing mode of a process graphic iscalled up, the origin point is the fabric location in the upper left corner ofthe display. The default origin point is 0/0. That is, when the processgraphic is initially called up, fabric location 0/0 is in the upper left cornerof the display.

The panning limits are the top, bottom, left, and right edges of theprocess graphic that the user is allowed to access when in viewingmode. The default panning limits are Top�0, Left�0, Right�640, andBottom�448. They are the same size as a console display.

Figure 3.2.54 shows how to change the panning limits and the originpoint.

TAGLINK

Top Menu

Type�NONE

Limits

FilesClose

25/532


The first coordinate is the current verticallocation of the cursor, and it is associated withthe “Top” and “Bottom” fields.

The second coordinate is the currenthorizontal location of the cursor, and it isassociated with the “Left” and “Right” fields.

In the example, the user places thecursor on the “Top” field and presses[SELECT]. The current verticalcoordinate, 25, appears in the “Top” field.

- To change a panning limit or the originpoint:

1. Move the cursor to the desired point onthe fabric (for example, the new topedge). Press [SELECT]. The Top Menuappears.

2. Move the cursor to the “Limits” field.Press [SELECT]. The Set Limits Menuappears.

3. Move the cursor to the desired field andpress [SELECT]. The current cursorposition appears in the field as the newlimit.Numbers cannot be entered into the SetLimits Menu fields. When the cursor ismoved to a field and [SELECT] ispressed, the new cursor locationcoordinate is automatically entered intothe field.

Set Limits

Origin �0/0Top �25Bottom �448Left �0Right �640Close

Figure 3.2.54. Changing a Panning Limit or the Origin Point

CC: 3-2-73


Creating Assists for Display Manipulation

The Pagefrwd, Pageback, and Text objects can be used to call up otherdisplays or, when used with the Anchor object, to move to another partof the same process graphic. Table 3.2.16 describes the Pagefrwd,Pageback, and Text objects.

In viewing mode the Pagefrwd and Pageback objects are not displayed,but they still exist.

D When the [PAGE AHEAD] key is pressed, the command of thePagefrwd object nearest the upper left corner of the currentdisplay is executed.

D When the [PAGE BACK] key is pressed, the command of thePageback object nearest the upper left corner of the currentdisplay is executed.

Table 3.2.16. Display Manipulation Objects

Object Description

Pagefrwd Can be configured to call up a display or move to another part of the same display ifthe [PAGE AHEAD] key is pressed.

Pageback Can be configured to call up a display or move to another part of the same display ifthe [PAGE BACK] key is pressed.

TextCan be configured to call up a display or move to another part of the same display bymoving the cursor to the Text object, and pressing [SELECT]. The creation of theText object is described in the “Creating Text” heading in this section.

CC: 3-2-74


Creating Assists for Display Manipulation:Objects that Call up Other Displays

- To create an object that calls up other displays:

1. Move the cursor to the desired location on the fabric. Press[SELECT]. The Top Menu appears.

2. Move the cursor to the “Type” field and press [SELECT]. TheObject Type Menu appears.

3. Move the cursor to the desired field (Pagefrwd, Pageback, orText) and press [SELECT]. The Edit Object Menu appears.

Figure 3.2.55 shows the Edit Object Menu for the Pagefrwd andPageback objects. The Text object Edit Object Menu is describedin the “Create Text” section on page 3-2-46.

Edit Object Menu

Type PAGEBACK

Command�

Close Top Menu

Determines a command that is executedwhen the associated key ( [PAGE AHEAD]or [PAGE BACK] ) is pressed.

The command can be any combination ofkeystrokes that can be entered at thecommand line. The command may also bethe number of an Anchor object.

For example, the command “G:1*”executes the keystrokes [G] [:] [1][ENTER] and calls up group display 1.(The asterisk executes the [ENTER] key.)

For a list of command line options, seeChapter 8 of this manual.

Figure 3.2.55. Edit Object Menu for Pagefrwd and Pageback Objects for Display Manipulation

CC: 3-2-75


Creating Assists for Display Manipulation:Objects that Call up Another Part of the Same Display

The Anchor object allows part of a process graphic to be called up fromanother part of the same graphic. The Anchor object is assigned anumber. If a Pagefrwd, Pageback, or Text object is configured with the“Command” field entry the same as the Anchor object number, thePagefrwd, Pageback, or Text object calls up the part of the processgraphic with the Anchor object at its center, as shown in Figure 3.2.56.

In addition, the anchor number can be used in the command line to callup a process graphic. For example, the command “PG:,PLANT.3” callsup the part of the process graphic Plant with anchor number 3 at itscenter.

PAGEFRWD 1

ANCHOR 1

The Pagefrwd and Anchor objectsexist on the Process Graphic but arenot displayed.

1. When [PAGE AHEAD] ispressed and the nearestPagefrwd object is linkedto Anchor number 1, 2. A new viewing area is

displayed that has Anchorobject number 1 at its center.

Figure 3.2.56. Use of Anchor Object

CC: 3-2-76


- To create objects that call up another part of the same display:

1. Create one or more Pagefrwd, Pageback, or Text objects that willbe used to call up the desired part of the process graphic. (See“Creating Objects That Call Up Other Displays” on page 3-2-74.)

2. Move the cursor to the center of the viewing area that will becalled up. Press [SELECT]. The Top Menu appears.

3. Move the cursor to the “Type” field and press [SELECT]. TheObject Type Menu appears.

4. Move the cursor to the ANCHOR field and press [SELECT]. TheEdit Object Menu appears.

Figure 3.2.57 shows the Edit Object Menu for the Anchor object.Figure 3.2.58 shows an example of using a Pageback object andan Anchor object to call up another part of a display.

Edit Object Menu

Type ANCHOR

Number�

Close Top Menu

Determines the number of the Anchorobject. A Process Graphic should notcontain multiple Anchor objects with thesame number.To have the part of the Process Graphicwith this Anchor object in the centercalled up, a Pagefrwd, Pageback, or Textobject must have this Anchor numberspecified in its “Command” field.

Figure 3.2.57. Edit Object Menu for Anchor Object

As an example, a graphic display is configured with onePageback object that has “Command�3”.

The graphic display also has an Anchor object with“Number�3”.When the [PAGE BACK] key is pressed, the console displaysthe portion of the process graphic fabric that includes theAnchor object. The Anchor object is at the center of thescreen.

Edit Object Menu

Type ANCHOR

Number�3

Close Top Menu

Edit Object Menu

Type PAGEBACK

Command�3

Close Top Menu

Figure 3.2.58. Example Use of Anchor Object

CC: 3-2-77


Creating Assists for Display Manipulation:Display Targets

The Target object enables quick cursor positioning on a processgraphic. The Target object consists of one alphanumeric character thatis displayed on the graphic. Whenever the key for that character ispressed while viewing the process graphic, the cursor moves to theTarget object. The Target object operates regardless of what portion ofthe process graphic is displayed.

Figure 3.2.59 shows an example of a process graphic display that usesTarget objects to easily move around the display.

6

5

3

12

4

Target objects are used in this example to provide quick access toobjects on the Process Graphic.

When a number is pressed, the cursor moves to that number anddisplays that part of the fabric.

Figure 3.2.59. Example Use of Target Objects

CC: 3-2-78


- To create a display target:

1. Move the cursor to the desired location of the Target object.Press [SELECT]. The Top Menu appears.

2. Move the cursor to the ”Type” field and press [SELECT]. TheObject Type Menu appears.

3. Move the cursor to the Target field and press [SELECT]. The EditObject Menu appears.

Figure 3.2.60 shows the Edit Object Menu for the Target objectand Table 3.2.17 explains the fields on the screen.

Edit Object Menu

Type TARGET Char�Cond�Color�white 1n Blink�NOBlock�

Close Top Menu

Figure 3.2.60. Edit Object Menu for Target Object

Table 3.2.17. Screen Fields on the Edit Object Menu for Target Object

Field Description


Block Determines the tag or address of the block that is displayed if the object is selected.

Char Determines the single alphanumeric character that forms the target.



CC: 3-2-79


Creating Assists for Display Manipulation:Hiding Parts of the Display Using an Icon Object

The Icon object allows you to hide a group of objects from view until theoperator chooses to display the group. The Icon object appears as aline of text. It can be grouped or joined with any number of otherobjects. When you cursor to the Icon object and press [SELECT], thegroup of objects appears. Pressing [SELECT] again causes the objectsto disappear.

NOTE: If you move an object that is grouped with an Icon object, all ofthe objects in the group also move.

- To create an icon:

1. Move the cursor to the desired location of the Icon object. Press[SELECT]. The Top Menu appears.

2. Move the cursor to the “Type�NONE” field and press [SELECT].The Object Type Menu appears.


The Edit Object Menu appears. Figure 3.2.61 shows how theIcon object appears in configuration mode.


5. If you want, use the Group and Join operations on the Top Menuto create the desired group of objects. Include the Icon object inthe group. See “Grouping Objects—Group and Join Operations”on page 3-2-60.

CC: 3-2-80



ICON

Figure 3.2.61. How the Icon Object is Displayed

Figure 3.2.62 shows the Edit Object Menu for the Icon object andTable 3.2.18 explains the fields on the screen.

Edit Object Menu

Type ICONCond�Color�white 1n Blink�NOInitial View Mode�OFFFont�Normal Edit Text�Al Obj TanklevClose Top Menu

Title of the Alarmobject to which theIcon object is linked—Tanklev

Figure 3.2.62. Edit Object Menu for Icon Object

CC: 3-2-81


Table 3.2.18. Screen Fields on the Edit Object Menu for Icon Object

Field Description

Blink Determines whether or not the group of objects blinks.

Color

Determines the color. The color choices are configured on the Master Color Selectionscreen ( [C] [C] [P] command).

If the Icon object is linked to an alarm, the Icon object has the color configured for thealarm, not to be confused with the color configured for the Alarm object.

Initial View Mode Determines whether the objects grouped with the Icon object are displayed in the onstate or off state when initially called up. The default is Off.

Cond

Determines a condition that affects how the object is displayed. This refers to thedisplay of the Icon object only, not the display of the objects that might be groupedwith the Icon object. See “Configuring the Appearance of Objects to Change” on page3-2-54.When the condition is false, the Icon object is not displayed.

Edit Text Allows text to be entered.

Font


D “Small” indicates half--size—half the width and half the height.

Al ObjTitle of the Alarm object to which the Icon object is linked, if any. This field is fordisplay only; it is not enterable. This field is displayed only when an Alarm object isjoined with an Icon object.

CC: 3-2-82


Copying a Process Graphic

A process graphic can be copied to the same volume or to anothervolume. Figure 3.2.63 shows the procedure.



File Operations



Close

- To copy a graphic:1. Cursor to any location on the

fabric and press [SELECT].

2. Cursor to the “Files” field andpress [SELECT]. The FileOperations Menu appears.

3. Cursor to the “Write” field.4. Type in the volume and filename

of the new Process Graphic.Press [ENTER]. The newgraphic has been created.

5. Reenter the volume andfilename of the current ProcessGraphic. Press [ENTER].

CAUTION

If the volume and filename are notchanged back to the currentgraphic, any changes made fromthis point until the user leaves thegraphics generation screen arewritten to the new file and not to thecurrent graphic file.

Top Menu

Type�None

Limits

AreaClose Files

Figure 3.2.63. Copying a Process Graphic

CC: 3-2-83


Creating Objects That Display Batch Task Data:Bface Object

Batch task information can be configured as part of a process graphicwith the Bface object. The Bface object allows the user to performBatch Run screen functions from a process graphic. For informationabout the Bface object characteristics, see BA: 1.

- To create the Bface object:



3. Move the cursor to the “Bface” field and press [SELECT]. TheEdit Object Menu appears. Figure 3.2.64 shows how the Bfaceobject appears in configuration mode.



BFACEBFACEBFACEBFACEBFACEBFACE

Figure 3.2.64. How the Bface Object Appears in Configuration Mode

CC: 3-2-84


- To configure the Bface object characteristics:

1. The characteristics of an object are determined by the fields onthe Edit Object Menu, as shown in Figure 3.2.65 andTable 3.2.19. Move the cursor to the desired field and press[SELECT]. Another menu appears.


Edit Object Menu

Type BFACE Size�4 �1Cond�Color�white 1n Blink�NOTask�30:1 Edit Items

Close Undo Top Menu

Figure 3.2.65. Edit Object Menu for the Bface Object

Table 3.2.19. Screen Fields on the Edit Object Menu for the Bface Object

Field Description


Color Determines the color of the data in the Bface object. The color choices are configuredon the Master Color Selection screen ( [C] [C] [P] command).

Cond Determines a condition that determines the object is displayed. See “Configuring theAppearance of Objects to Change” on page 3-2-54.

Edit Items

Determines the items that are included in the Bface object. When this item is selectedthe Batch Edit Items Menu appears. Moving the cursor to an arrow on the menu andpressing [NEXT OPTION] shows the possible entries for the Bface object.

The entries are parameters for the specified task. For more information about Bfaceobjects and the parameters, see BA: 1.

Size

Determines the size of the Bface object and how the data lay out.D Num Col determines the number of columns of information (1--3).

D Num row determines the number of rows of information (1--10). The actual sizeof the Bface object is two rows more than the Num row field.

Task Determines the batch task in the form “node:task”.

CC: 3-2-85


Alarm Annunciation on Graphics

The way that alarms are announced on graphics varies for differenttypes of graphic objects.

Alarm Object

The Alarm object title shows the alarm condition of the highest priorityalarm in the Alarm object.

Icon Object

The alarm annunciation for an Icon object depends on whether the Iconobject is linked to an Alarm object.

D If a group containing an Icon object also contains one Alarmobject, the Icon object shows the alarm condition of the Alarmobject.

D If a group containing an Icon object also contains more than oneAlarm object, the Icon object shows the alarm condition of theAlarm object that is configured in the “Al Obj” field of the Icon EditObject Menu.

CC: 3-2-86


CC: 3-3-1

RS3: Process Graphics Optimizing Graphics Performance

Section 3:Optimizing Graphics Performance

The size of the graphic file and refresh rates can affect the performanceof the process graphic. Anything you can do to make the processgraphic smaller or more consistent with the response time of the CPand Controller Processors will improve its performance.

CC: 3-3-2


Process Graphic Limits

Table 3.3.1 list process graphic parameters and their correspondinglimits. You should be aware that running a process graphic near theparameter limits reduces console memory available for graphicperformance.

Table 3.3.1. Parameter Limits

Parameter Limit

Graphic Fabric 16000 pixels high by 16000 pixels wide

Graphic File 25 Kilobytes (24 Kilobyte maximum practical size)

Block Links 64 block links

Object Overhead 32 bytes

Field Refresh Rate 0.25 to 2 seconds

Screen Refresh Rate 0.25 to 20.0 seconds

CC: 3-3-3


Link Count Field

To determine how many ControlBlock links exist in a process graphic,use the Link Count field.

File Operations



Symbol�Close LinkCount x

Top Menu

Type�THINGMove GroupCopyLimits LinkEdDelete TopUndo Bottom

AreaClose Files



- To use Link Count field:1. Press “select” anywhere

on the graphic.

2. Cursor to the “Files” fieldand press [SELECT].

3. Cursor to the “Link Count”field.

4. Select.

The number of block linksused by the graphic willappear at x.

Figure 3.3.1. Using the Link Count Field

You may have up to 64 block links per graphic. For graphics with manylinks to the same ControlFile, consider optimizing by usingfunnel blocks.

CC: 3-3-4


Using Funnel Blocks

You can use a ControlBlock called a funnel block to reduce the numberof ControlBlock links per process graphic. A funnel block brings linksfrom several different blocks in to the process graphic. The processgraphic counts all registers from the funnel block as one link, so thatonly one out of 64 links are consumed. Figure 3.3.2 shows howfunneling works.

NOTE: Funnel blocks are most useful if the links being funneled are forblocks in the same ControlFile as the funnel block. When ControlBlocksare in other ControlFiles on the PeerWay, the advantage of funneling isoffset by the use of valuable PeerWay links.

File Operations

Read > DOC,LINK_GRWrite> DOC,LINK_GR

Close Link Count 1

Process GraphicControlBlockContinuous Links

Tag> FunnelA > =99A-01B > =99A-05C > =99A-20D >E >F >G >

Funnel/A

Funnel/B

Funnel/C

The Process Graphic counts all registers ofthe funnel block as one link.

Figure 3.3.2. Funnel Block Concept

CC: 3-3-5


Merging Objects

You can merge a group of objects together to create a complex objectcalled a Thing object. A set of objects that are merged into a Thingobject take up less memory than the same objects would take upindividually. Using fewer objects also reduces the screen refresh time.

Individual objects are assigned 32 bytes of overhead and additionalspace for the object description. The Thing object reduces overhead by32 bytes for each object merged. Objects copied from the Thing objectuse even less memory, because the copied objects share the samedescription with the original Thing object.

Individual objects do not need to be visually connected on the screen tobe merged together into a Thing object. You can merge objects scatteredaround the screen. See page 3-2-66 for more merge information.

NOTE: Since you cannot separate merged objects, you might want tosave a copy of the unmerged objects in a separate file for editing.

CC: 3-3-6


Other Methods of Optimizing Graphics

The following are recommendations for constructing and maintaininggraphics to use console memory efficiently:

Wide lines There are two ways to construct lines that are morethan one pixel wide:

D Draw multiple lines parallel to each other.

D Configure a narrow box as a solid shape.

A box line uses less memory than multiple lines. Ifyou use multiple lines, merge them into a Thingobject.

Invisible Use invisible objects sparingly. Invisible objects areobjects often useful for hiding pieces of other objects, but

increase the byte size of the graphic. Whereverpossible, construct objects differently to reduce thenumber of objects required.

Unused Remove unused objects from the process graphics.graphics It is easy to overlook text and link objects that do

not have any size, since these objects are indicatedon the screen by only a single pixel. To find theseobjects, press the [NEXT OPTION] key to movefrom one object to another.

CC: 3-3-7


Preconfigured Process Graphics

The Process Graphics folder contains five files of commonly usedgraphic icons, such as valves, motors, boilers, and other processsymbols. These icons have been designed to provide you withpreconfigured process graphics with a minimum waste of space andgraphics capabilities.

You can select preconfigured icons from the following files to creategraphic symbols:

D $Readme

D $Stdsym

D $SymbolS1

D $SymbolS2

D $SymbolS3

For information on creating symbols, see “Creating Shapes: NewSymbols” on page 3-2-19.

CC: 3-3-8


Screen Refresh and Field Refresh

Refresh rates specify the maximum rate at which the console canrequest data from the controller. Screen Refresh refers to length of timerequired to refresh all data points on the graphic. Field refresh refers tothe length of time required to refresh data for a particular data point orfield on the process graphic.

The screen refresh and field refresh rates are set on the ConsoleConfiguration screen. The screen refresh rate is intended to slow datarequests to prevent excess data request messages from overwhelmingthe controller and flooding the PeerWay. You can set the field refreshrate to a higher speed than the screen refresh rate to maintain fasterresponse times for select data items.

- To refresh individual fields:

D Move the cursor to that field. The field thus selected will refreshat the field refresh rate instead of the screen refresh rate.

For more information on refresh rates, see “Configuring Refresh andAdvance Request Rates” on page 2-1-38.

ContentsRS3: Reports


Chapter 4:Reports

Section 1: Introduction to Reports 4-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: The Report File Structure 4-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Report Read Directory Screen 4-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report File Contents Screen 4-2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report Read/Scan Screen 4-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report Config Directory Screen 4-2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The Report Status Screen 4-2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Designing a Report 4-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assembling Information for a Report 4-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Dimensions of a Report 4-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Formatting the Report for Printing 4-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Configuring a Report 4-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Report Configuration Screen 4-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Report Objects 4-4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using Report Objects to Configure Reports 4-4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Editing the Body of a Report 4-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring How a Report is Printed 4-4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Determine Report Print Characteristics 4-4-10. . . . . . . . . . . . . . . . . . . . . . . . .How to Begin a New Report Page 4-4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Text in a Report 4-4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Print Regular--sized Text 4-4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Print Oversized Text 4-4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Operator Comments in a Report 4-4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Block Information in a Report 4-4-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Configure a Block Tag 4-4-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Address 4-4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Descriptor 4-4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Function 4-4-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure a Block Mode 4-4-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure Block Units 4-4-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure Block Values 4-4-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Perform Calculations 4-4-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Configure Trend File Information in a Report 4-4-26. . . . . . . . . . . . . . . . . . . . . . .

CC: ii

RS3: Reports Contents

How to Use an Accumulator with a Trend Log Object 4-4-31. . . . . . . . . . . . . . . . . . . .Configuring Time and Date Information in a Report 4-4-32. . . . . . . . . . . . . . . . . . . . . . . .

How to Configure the Current Time 4-4-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How to Configure the Current Date 4-4-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Console Lists in a Report 4-4-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring the List Object 4-4-35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Formatting a List 4-4-35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Configure Another Report in a Report 4-4-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Generating Reports 4-4-39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How to Generate a Report Based on Time and Date 4-4-39. . . . . . . . . . . . . . . . . . . .How to Generate a Report Based on Alarms or Events 4-4-41. . . . . . . . . . . . . . . . . .How to Generate a Report from the Report Configuration Screen 4-4-42. . . . . . . . .How to Print a Report When it is Generated 4-4-43. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 5: Saving a Report to Disk 4-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 6: Hints for Configuring and Using Reports 4-6-1. . . . . . . . . . . . . . . . . . .

Configuration Problems 4-6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tips 4-6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Marking Lines in Reports 4-6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iii


List of Figures

Figure Page

4.2.1 Report Folders and Report Screens 4-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 Report Read Directory Screen 4-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.3 Report File Contents Screen 4-2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.4 Report Read/Scan Screen 4-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.5 Report Configuration Directory Screen 4-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.6 Report Status Screen 4-2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.1 Report Sample Layout 4-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.2 Visible Report Screen Dimensions 4-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.3 Sizing a Report Page 4-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.1 Report Configuration Screen 4-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.2 Report Configuration Screen with Report Configuration Window 4-4-5. . . . .

4.4.3 Report Configuration Window with Fields 4-4-8. . . . . . . . . . . . . . . . . . . . . . . .

4.4.4 Report Configuration Screen with Print Object 4-4-10. . . . . . . . . . . . . . . . . . . .

4.4.5 Report Configuration Screen with Newpage Object 4-4-11. . . . . . . . . . . . . . . .

4.4.6 Report Configuration Screen with Text Object 4-4-12. . . . . . . . . . . . . . . . . . . .

4.4.7 Report Configuration Screen with Banner Object 4-4-13. . . . . . . . . . . . . . . . . .

4.4.8 Report Configuration Screen with Comment Object 4-4-14. . . . . . . . . . . . . . . .

4.4.9 Report Configuration Screen with Tag Object 4-4-15. . . . . . . . . . . . . . . . . . . . .

4.4.10 Report Configuration Screen with Address Object 4-4-16. . . . . . . . . . . . . . . . .

4.4.11 Report Configuration Screen with Descriptor Object 4-4-17. . . . . . . . . . . . . . .

4.4.12 Report Configuration Screen with Function Object 4-4-18. . . . . . . . . . . . . . . . .

4.4.13 Report Configuration Screen with Mode Object 4-4-19. . . . . . . . . . . . . . . . . . .

4.4.14 Report Configuration Screen with Unit Object 4-4-20. . . . . . . . . . . . . . . . . . . . .

4.4.15 Report Configuration Screen with Value Object 4-4-21. . . . . . . . . . . . . . . . . . .

4.4.16 Report Configuration Screen with Value and Accumulator Objects 4-4-23. . .

4.4.17 Report Configuration Screen with Value Objects 4-4-24. . . . . . . . . . . . . . . . . .

4.4.18 Report Configuration Screen with Accumulator Object 4-4-25. . . . . . . . . . . . .

4.4.19 Report Configuration Screen with Trend Log Object 4-4-26. . . . . . . . . . . . . . .

4.4.20 Sample Trend Log Object Configuration Window and Resulting Report 4-4-27

4.4.21 Sample Trend Log Object Configuration Window and Resulting Report 4-4-28

4.4.22 Report Configuration Window with Trend Log Object and Accumulator 4-4-31

4.4.23 Report Configuration Screen with Time Object 4-4-32. . . . . . . . . . . . . . . . . . . .

CC: iv


4.4.24 Report Configuration Screen with Date Object 4-4-33. . . . . . . . . . . . . . . . . . . .

4.4.25 Report Configuration Screen with List Object 4-4-35. . . . . . . . . . . . . . . . . . . . .

4.4.26 Report Configuration Screen with Generate Object 4-4-37. . . . . . . . . . . . . . . .

4.4.27 Generating a Report Based on Time 4-4-39. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.28 Generating a Report Based on Date 4-4-40. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.29 Generating a Report Based on Alarms and Events 4-4-41. . . . . . . . . . . . . . .

4.4.30 Report Configuration Screen with Generate this Report Command 4-4-42. .

4.4.31 Report Configuration Screen with Auto Print Field 4-4-43. . . . . . . . . . . . . . . . .

CC: v


List of Tables

Table Page

4.4.1 Report Configuration Screen Fields 4-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.2 Report Object Types 4-4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.3 Editing Instructions 4-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.4 Trend Log Field Description 4-4-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.5 List Object Configuration Screens 4-4-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.6 Generate Field Descriptions 4-4-38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: vi


CC: 4-1-1

RS3: Reports Introduction to Reports

Section 1:Introduction to Reports

Reports are user--configured displays of information on an MTCC thatprovide pertinent information about system process variables. A reportconsists of report configuration and report generation. Up to 200 reportscan be configured on an MTCC. Each configured report can have up to100 report generations. The maximum number of reports on an MTCCvaries depending on the amount of available memory. Reports may begenerated on the basis of time, alarms, events, or operator commands.

Reports are usually configured to be printed, but they may be simplydisplayed on the console screen. A report may be printed automaticallywhen it is generated, or several copies of a report may be accumulatedon the disk and printed when requested by an operator.

CC: 4-1-2

RS3: Reports Introduction to Reports

CC: 4-2-1

RS3: Reports The Report File Structure

Section 2:The Report File Structure

Two disk folders are used by the report subsystem:

D The Report Config folder stores the configuration entries for allreports to be generated by the console.

D The Reports folder stores the report generations.

When a configured report is generated, a corresponding report fileappears in the Reports folder. The Report Config folder is created thefirst time a report configuration is saved to the disk. A Reports folder iscreated the first time that a report is generated. Figure 4.2.1 shows therelationship between the Report Config and the Reports folders and thecorresponding report screens.

Configured report activity and generated report activity is contained onthe Report Status screen.

CC: 4-2-2


REPORT CONFIGDIRECTORYSCREEN

REPORTREAD

DIRECTORYSCREEN

REPORT FILECONTENTSSCREEN

REPORTREAD/SCANSCREEN

REPORTCONFIGSCREEN

Reports

The Reports Config folder onthe Disk Directory PeerWayscreen contains configurationfiles for each report.

The Report ConfigDirectory screencontains a list of thereport configuration files.

Report Config

The Report Configscreen contains aconfigured report.

The Reports folder on the DiskDirectory PeerWay screencontains report generation files.

The Report ReadDirectory contains a listof report generation files.

The Report FileContents screencontains a singlereport’s generationhistory.

The ReportRead/Scanscreen containsa generatedreport.

- To access the next level:1. Highlight the folder or report file selection and press [SELECT].

Figure 4.2.1. Report Folders and Report Screens

CC: 4-2-3


The Report Read Directory Screen

The Report Read Directory screen provides a list of all reports that havebeen generated. Figure 4.2.2 shows an example of a Report ReadDirectory screen with field descriptions.- To call up the Report Read Directory screen:

D Highlight the Report folder on the Disk Directory screen andpress [SELECT].

orD Type:

RRD: [ENTER]

Report Read Directory 04-Aug-96 18:06:09

Disk Name WINI-C55 At Node 18 On Drive 1Free Bytes 1958656

Sort Criterion� Filename Sort Order �Ascending Start�1Filename Size Modification Time Max# Node Autoprint# Rpts Unprint

------------------------------------------------------------------------------

#1B-LOG1 48384 04-Feb-96 17:31:50 32 6 Y 1 0Blr-MnRun 33280 01-Feb-96 09:40:29 10 0 N 10 10SNY 3584 03-Jan-96 09:41:46 63 2 N 1 1

* END *CONFIG 3

Autoprint = If “Y“, a report is printed andsaved to disk when generated; if“N“ the report is written to disk.

#Rpts = Number of report generationsUnprint = Reports that are generated but

not printed

Disk Name= Disk where volume is currently locatedAt Node = Node number where volume is currently located

On Drive = Drive number where volume is currently located

Free Bytes= Space available in folder

Filename = User--assigned filenameSize = Size in bytes of the file

Modification Time Last time and date file was modified,if ever

Max = Maximum number of report generations

Node = Print node

Sort Criterion = Sorts the directory to oneof the directory columns

Sort Order = Ascending or descendingfiles

Start = Searches for filename—enter a numberor /xxx/, where xxx is oneor more characters

Figure 4.2.2. Report Read Directory Screen

CC: 4-2-4


The Report File Contents Screen

The Report File Contents screen lists all generations of an individualreport. Figure 4.2.3 shows an example of a Report File Contents screenwith field descriptions.- To call up the Report File Contents screen:

D Highlight a report file on the Report Read Directory screen andpress [SELECT].

orD Type:

RFC ( , report_name) [ENTER]

Report File Contents 04-Aug-96 18:06:09

Disk Name WINI-C55 At Node 18 On Drive 1

Report Name> Size15360Created on 01-Feb-96 17:24:22 Last Modified 02-Feb-96 11:09:45Last Backup Time 02-Feb-96 12:12:36#Ent Prted? Node Size Pages Lines Generated Completed-----ENTER-to-print--------------SELECT-to-read----------CTRL-d-to-delete-------1 Yes 6 46768 5 308 02-Feb-96 03:12:15 02-Feb-96 06:15:242 No 6 45555 5 300 01-Feb-96 05:12:15 01-Feb-96 06:15:243 No 6 46000 5 302 01-Feb-96 03:12:15 01-Feb-96 04:15:244 Yes 6 46768 5 308 01-Feb-96 02:12:15 01-Feb-96 02:15:24

**END**CONFIG 3

Disk Name = Disk where the volume is currently locatedAt Node = Node number where volume is currently locatedOn Drive = Drive number where volume is currently locatedReport Name = User--configured report nameCreated on = Date and time file was first written to diskLast Modified = Last date and time file was changedLast Backup time =Last time and date file was backed up, if ever#Ent = Latest report generation (1) to earliest report generationPrted? = Specifies if the report was printedNode = Print nodeSize = Size in bytes of the report configuration filePages = Number of pages of a reportLines = Number of lines in a reportGenerated = Date and time the report started generationCompleted = Date and time the report completed generation

Figure 4.2.3. Report File Contents Screen

CC: 4-2-5


The Report Read/Scan Screen

The Report Read/Scan screen contains a copy of a generated report.Figure 4.2.4 shows an example of a Report Read/Scan screen with fielddescriptions. If a report is very long, the Report Read/Scan screen maynot be able to display all the lines of the report.

- To call up the Report Read/Scan screen:

D Highlight a report file on the Report File Contents screen andpress [SELECT].

or

D Type:

RR: ( , report name) [ENTER]

Report Read/Scan 02-Aug-96 14:23:47

Filename : �node 44-1 Print entry #�1 (1 = newest, 99 = oldest entry)Generated on 02-Feb-96 from 14:22:21 to 14:22:22 Lines : 8

********* END-OF-FILE *********

Filename = User--configured report namePrint entry = Entry number on the Report File

Contents screenGenerated on = Date and time the report was generatedLines = Number of lines in the report

Figure 4.2.4. Report Read/Scan Screen

CC: 4-2-6


The Report Config Directory Screen

The Report Config Directory screen provides a list of all reports thathave been configured. A report listed on this screen can be selectedand copied to be used as a format for multiple reports. Figure 4.2.5shows an example of a Report Config Directory screen with fielddescriptions.

Individual report configuration screens are called up from the ReportConfig Directory screen. For more information about the ReportConfiguration screen, see page 4-4-2

- To call up the Report Config Directory screen:

D Highlight the Report Config folder on the Disk Directory screenand press [SELECT].

or

D Type:

RCD [ENTER]

- To call up a Report Configuration screen:

D Cursor to a selected report file on the Report Config Directoryscreen and press [SELECT].

CC: 4-2-7


Report Config Directory 04-Aug-96 15:32:16

Disk Name WINI-C55 At Node 18 On Drive 1Free Bytes 1968128

Sort Criterion � Filename Sort Order �Ascending Start�1Filename Size Modification Time Max# Node Autoprint Active

-------------------------------------------------------------------------------#1B-LOG1 4352 04-Feb-96 14:25:12 32 6 Y Y#1B-LOG2 3072 03-Feb-96 09:40:29 32 6 Y Y#1B-LOG3 3072 03-Feb-96 09:41:46 32 6 Y Y#2B-LOG1 2816 03-Feb-96 09:42:37 32 6 Y Y#2B-LOG2 2816 03-Feb-96 09:43:52 32 6 Y Y#2B-LOG3 3072 03-Feb-96 09:44:43 32 6 Y Y#3B-LOG1 2816 03-Feb-96 09:45:23 32 6 Y Y#3B-LOG2 3072 03-Feb-96 09:46:12 32 6 Y Y#3B-LOG3 3072 03-Feb-96 09:47:34 32 6 Y Y#4B-LOG1 2816 03-Feb-96 09:52:17 32 6 Y Y#4B-LOG2 3072 03-Feb-96 09:53:29 32 6 Y Y#4B-LOG3 3072 03-Feb-96 09:54:35 32 6 Y Y#5B-LOG1 2816 03-Feb-96 09:55:26 32 6 Y Y#5B-LOG2 3072 03-Feb-96 09:56:28 32 6 Y Y#5B-LOG3 3072 03-Feb-96 09:57:24 32 6 Y Y

* MORE *CONFIG 1

Sort Criterion = Sorts the directory to oneof the directory columns

Sort Order = Ascending or descendingfiles

Start = Searches for file name----enter a number or /xxx/where xxx is one or morecharacters

Disk Name = Disk where volume is currently locatedAt Node = Node number where volume is currently

mountedOn Drive = Drive number where volume is currently

mountedFree Bytes = Space available in folder

Autoprint = If “Y”, a report is printed andwritten to disk when generated;if “N”, a report is written to disk

Active = If “Y”, a report is generated atspecified times or alarms/events; if“N”, a report is generated only onoperator command

Filename = User--configured report nameSize = Size in bytes of the fileModification Time =Last time and date file was

modified, if everMax = Maximum number of report

generationsNode = Print node

Figure 4.2.5. Report Configuration Directory Screen

CC: 4-2-8


The Report Status Screen

The Report Status screen shows the activity of configured andgenerated reports. The Report Status screen shows up to 18 entries.Each new entry appears at the bottom of the screen and the oldestentry is scrolled off the top of the screen. Figure 4.2.6 shows anexample of a Report Status screen with field descriptions.

- To call up the Report Status screen, type:

RS [ENTER]

Report Status 04-Aug-96 15:32:16

Current state ;�Enabled Disk Owner: yes RunningFilename Action Time#1B-LOG2 Report generation completed 09:47:02 04-Feb-96#1B-LOG2 AUTO-PRINT kicked off to node 16 09:47:02 04-Feb-96#1B-LOG2 Report has been scheduled (alarm) 09:48:24 04-Feb-96#1B-LOG2 Starting report generation 09:48:24 04-Feb-96#1B-LOG2 Deleting existing report entry #3 09:48:25 04-Feb-96#1B-LOG2 Report generation completed 09:48:26 04-Feb-96#1B-LOG2 AUTO-PRINT kicked off to node 16 09:48:26 04-Feb-96#1B-LOG2 Report has been scheduled (alarm) 09:49:45 04-Feb-96#1B-LOG2 Starting report generation 09:49:45 04-Feb-96#1B-LOG2 Deleting existing report entry #3 09:49:47 04-Feb-96#1B-LOG2 Report generation completed 09:49:47 04-Feb-96#1B-LOG2 AUTO-PRINT kicked off to node 16 09:50:58 04-Feb-96#1B-LOG2 was modified, is active awaiting alarm 09:51:12 04-Feb-96#1B-LOG2 Report has been scheduled (alarm) 09:51:12 04-Feb-96#1B-LOG2 Starting report generation 09:51:12 04-Feb-96#1B-LOG Deleting existing report entry #3 09:51:14 04-Feb-96#1B-LOG2 Report generation completed 09:51:14 04-Feb-96

CONFIG 3

Current state = If “Enabled”, the report system is running; if “Disabled”, thereport system is not running

Disk Owner = Specifies which Multitube Command Console generates thereport

Filename = User--configured report nameAction = Report status messagesTime = Date and time the action took place

Figure 4.2.6. Report Status Screen

CC: 4-3-1

RS3: Reports Designing a Report

Section 3:Designing a Report

Reports can be designed for viewing on a CRT screen and for printing.This section gives guidelines for designing and formatting reports.

Assembling Information for a Report

Reports can be assembled with information from ControlBlocks, I/Oblocks, or trend files. The appearances of a report will vary dependingon the type of information that is included. Before starting theconfiguration process on a console screen, it may be helpful toapproximate the appearance and size of report by doing a layout on agrid worksheet. Figure 4.3.1 shows a sample layout of a report.

Report Configuration 28-Jul-96 09:32:16

****************** START OF REPORT ******************

BANNERDate Time

Process Narrative

Variables Process Descriptions Process Descriptions Process Descriptions

Total (accumulator)

CONFIG 1

Figure 4.3.1. Report Sample Layout

CC: 4-3-2


Dimensions of a Report

Report dimensions include the visible size of a report on a screen andthe maximum size of a report. Information can be configured in onereport that spans several pages, or configured in several reports thatare one page each.

D The visible size of one report on the screen is 80 columns wideby 30 rows long.

D The maximum size of one report is 160 rows wide by 30,000rows long.

Figure 4.3.2 shows the visible report body with dimensions.


****************** START OF REPORT ******************

30 rows long visible on the screen

80 columns wide visible on the screen

CONFIG 1

The body of the report begins here.

Figure 4.3.2. Visible Report Screen Dimensions

CC: 4-3-3


Formatting the Report for Printing

Figure 4.3.3 shows how to lay out a single-page report so that it fitsproperly on an 8½I� 11I sheet of paper. A page of a printed reportshould be 60 lines with a 3-line margin at the top of the page and a3-line margin at the bottom of the page.

If a report requires more than one page, a newpage object must beconfigured in a report. For information about the newpage object, seepage 4-4-10.

Contents of reportshould occupy nomore than 60 lines or74 columns per page

Allow at least6-column left marginfor hole-punching

Console inserts 3-line margin at topof first page when report is generated

Allow at least 3-line bottom margin

Edge of paper Edge of display

66 linestotalin an11-inchsheet

Figure 4.3.3. Sizing a Report Page

CC: 4-3-4


CC: 4-4-1

RS3: Reports Configuring a Report

Section 4:Configuring a Report

Each report is configured on a Report Configuration screen. Thissection describes the Report Configuration screen and describesconfiguring report objects.

CC: 4-4-2


The Report Configuration Screen

Figure 4.4.1 shows an example of a Report Configuration screen withfield descriptions. Table 4.4.1 gives brief descriptions of the fields thatare configured at the top of the Report Configuration screen.

- To call up a Report Configuration screen, type:

RG ( , filename) [ENTER]

NOTE: If the filename already exists, the Report Configuration screenfor that file appears. If the filename is new, a blank Report Configurationscreen appears.

REPORT CONFIGURATION 21-Aug-96 14:18:04Description :�

Created : neverFilename : � Size :0 Last saved : neverSTATUS : new file Free Space :100 Backed up : never

Auto Print ?�yes Max number of reports :�3 Print node :�16 Active ? �no

Generate on alarm/event from : �RPTTEST � ��

Month : anyDay/month: anyDay/week : anyHour : anyMinute : never

�TIME ENTRY :�

Command : �

****************** START OF REPORT ******************

CONFIG 1

Use the fields in the shaded areaof the screen to configure how,where, and when to generate andprint the report.

Configure the format andcontent of the report in thearea below the START OFREPORT.

Figure 4.4.1. Report Configuration Screen

CC: 4-4-3


Table 4.4.1. Report Configuration Screen Fields

Field Description Allowable Entries

Active ?Determines whether or not the “Generate on alarm/eventfrom” field is active. It also determines whether or not areport is configured to print based on time.

yes,no

Auto Print ? Determines whether or not a report is printed when it isgenerated.

yes,no

Backed Up Date and time when configuration file was last copied toanother disk or tape. Display only

Command

Used to execute one of the following commands:1) Save this configuration to disk

2) Generate a copy of this report

3) Clear the configuration of the body of this report4) Load from disk the report configuration screen for the

file currently entered in “Filename”

1) Save to disk2) Generate this report3) Clear Configuration4) Load from disk

Created Date and time when report was first configured. Display only

Day/month

Days of the month in which a report is to be generated.(any = every day) An entry is made after the arrow next tothe “Time Entry” field. For more information, see “How toGenerate a Report based on Time and Date” on page4-4-31.

any, or 1--31

Day/week

Days of the week in which a report is to be generated.(any = every day) An entry is made after the arrow next tothe “Time Entry” field. For more information, see “How toGenerate a Report based on Time and Date” on page4-4-31.

any, 1--7, or Sun to Sat(1=Sun)

Description Description of the report. Up to 59 alphanumericcharacters

Filename Name of the report configuration file. Up to to 9 alphanumericcharacters

Free Space Percent of report’s configuration file space not yet used. Display only

Generate onalarm/eventfrom

Determines block variable alarms and events that triggerreport generations. Refer to “Generating Reports” on page4-4-38 for more information.

Any existing variable’stag or address.

Hour

Hours at which a report is to be generated.(any = every hour) An entry is made after the arrow next tothe “Time Entry” field. For more information, see “How toGenerate a Report based on Time and Date” on page4-4-31.

any, or 0--23

Last Saved Date and time when report was last saved to disk, either byexiting the screen or entering a “Save to disk” command. Display only

Max Number ofReports

Number of report generations to be saved on the disk. Themost current generations are saved. 1 to 99


CC: 4-4-4


Table 4.4.1. Report Configuration Screen Fields (continued)

Field Allowable EntriesDescription

Minute

Minutes on the clock at which report is to be generated. Anentry is made after the arrow next to the “Time Entry” field.For more information, see the “How to Generate a Reportbased on Time and Date” on page 4-4-31.

never or0--55 in 5 min. intervals

Month

Months in which a report is to be generated.(any = every month) An entry is made after the arrow next tothe “Time Entry” field. For more information, see “How toGenerate a Report based on Time and Date” on page4-4-31.

any, 1--12, or Jan to Dec(1=Jan)

Print NodeNode where the report is to be printed. This must be thesame entry as the “Print Node” field entry on the ConsoleConfiguration screen.

Any node number wherea printer is connected.

Size Size in bytes of the configuration file. Display only

Status

new file = file being configured for the first timemodified = configuration modified since last saved to

disk

unchanged = configuration unchanged since last saved todisk

exists = name of an existing file has been entered in“Filename”.

Display only

Time Entry

Used to select any one of the time parameters for entry.Select the desired time parameter. Cursor to the arrowimmediately to the right and enter the desired value. Repeatfor each time parameter.

Month, Day/month,Day/week, Hour and

Minute

CC: 4-4-5


Report Objects

A report is configured with various objects. You configure each objectand place it in the body of a report. Each object is configured in aReport Configuration Window. Figure 4.4.2 shows an example of aReport Configuration Window with the procedure for selecting a reportobject. Table 4.4.2 gives descriptions of report objects that can beselected.


****************** START OF REPORT ******************

Type :�value Color :�1n white Row :�26 Col :�13

Tag :�none CREATE DELETE

Accum :�none

CONFIG 1

- To select a report object:1. Position the cursor in the body

of the report where the objectshould be.

2. Press [SELECT]. AReport ConfigurationWindow appears.

3. To select an object, cursorto the “Type” field andpress [NEXT OPTION].Then press [ENTER].

4. Configure the remainingfields in the ReportConfiguration Window.

Figure 4.4.2. Report Configuration Screen with Report Configuration Window

CC: 4-4-6


Table 4.4.2. Report Object Types

Report Object Function

accumulateDisplays a result calculated from several value objects, such as a column total. Theform of the calculation depends on the operation (+, --, �, or �) selected for eachvalue object.

addr Displays the address of the specified block.

ban1 Displays a large-type banner or heading. Each character will be 10 lines high and 8columns wide. Maximum of 10 characters across an 80-column page.

ban2 Displays a large--type banner or heading. Each character will be 10 lines high and 16columns wide. Maximum of 5 characters across an 80-column page.

comment Allows the operator to enter up to 70 characters in a report before the report isgenerated.

date Inserts the current date whenever the report is generated.

descriptor Displays the descriptor of the specified block.

func Displays the block function configured for the specified block.

generate Allows another generated report to be incorporated into the report being configured.

list Inserts the current contents of an alarm or event list into the report.

mode Displays the current mode of the specified block.

newpage Directs the printer to execute a form feed

print Permits entry of a hexadecimal code to control the operation of the printer, permittinguse of special features such as type font and color selection. (See printer manual).

tag Displays the tag of the specified block.

text Displays up to 40 characters of text.

time Inserts the current clock time whenever the report is generated.

trend log Creates a table of periodic readings of one or more variables overa specified time span.

units Displays the engineering units legend associated with the specified variable.

value Displays the value of the specified continuous or discrete variable.

CC: 4-4-7


Using Report Objects to Configure Reports

Some fields appear in Report Configuration Windows for all reportobjects. Figure 4.4.3 shows a Report Configuration Window withdescriptions of those fields that appear in all Report ConfigurationWindows.

Type :�value Color :�1n white Row :�26 Col :�13value

CREATE DELETE

CONFIG 1

Report objects can be displayed(but not printed) in various colors.Select different colors for objectsby pressing [NEXT OPTION] in the”Color” Field.

A report object is selected in the“Type” field.

A location on the body of the report isidentified as the intersection of a row and acolumn, as indicated by the ”Row” and ”Col”fields.

CREATE is used to create text or values for thegenerate object and the trend log object. CREATE isalso used with other report objects to copy text orvalues. To copy text or values, select the object andlocation, then cursor to CREATE and press [ENTER].

DELETE is used to delete a single object. To delete anobject, select the object and location, cursor toDELETE and press [ENTER]. Or, press [SELECT] onthe left end of the object, then cursor to DELETE andpress [ENTER].

Figure 4.4.3. Report Configuration Window with Fields

CC: 4-4-8


Editing the Body of a Report

Table 4.4.3 gives editing instructions to use when configuring the bodyof the report.

Table 4.4.3. Editing Instructions

Editing Tasks Action

To delete a line or row of objects Cursor to the line to be deleted and press the [CNTL] and [D]keys at the same time.

To delete a space (to the left of anobject)

Cursor to the line containing the object and press the [CNTL]and [F] keys at the same time.

To delete an object Cursor to the left end or upper left corner of the object and press[ENTER].

To insert a line (above an object) Cursor to the line containing the object and press the [CNTL]and [I] keys at the same time.

To insert a space (to the left of anobject)

Cursor to the line containing the object and press the [CNTL]and [E] keys at the same time.

To page through the report To scroll up one line, press the [CNTL] and [J] keys at the sametime.

To scroll down one line, press the [CNTL] and [K] keys at thesame time.

To jump to the last position jumpedfrom Press the [CNTL] and [G] keys at the same time.

To print the report Press the [CNTL] and [P] keys at the same time.

To read the report from a disk Press the [CNTL] and [R] keys at the same time.

To write the report to disk Press the [CNTL] and [W] keys at the same time.

CC: 4-4-9


Configuring How a Report is Printed

The print object determines the font style, size and color of the text inwhich the report is printed. The newpage object causes a page break inthe report.

How to Determine Report Print Characteristics

The print uses a hex code to determine the report print characteristics.The hex code remains in effect until the next print object is inserted in areport. See the printer manual for printer hex codes. Figure 4.4.4 showsthe procedure for configuring a print object in a report.

NOTE: The print object in the Report Configuration window does notdetermine when and if the report is printed.

Report Configuration 02-Aug-96 15:31:16

ENERGY PRODUCTION REPORTGenerated at 14:27:42 on 02-Feb-96

TOTAL TOTAL TOTAL TOTAL AVERAGESTEAM FLOW FW FLOW GAS FLOW OIL FLOW EFFICIENCY

(KLB) (KLB) (KSCF) (GALLON) (%)

BOILER #1 .089 .903 .442 .96 .54BOILER #2 .087 .877 .368 .65 .69BOILER #3 .077 .857 .314 .21 .34- - - - - - - - - - - - - - - - - - - - - - - - - - -SUBTOTAL ACCUM #1 ACCUM #2 ACCUM #3 ACCUM #4 ACCUM #5

printType :�print Color :�1n white Row :�30 Col :�45

CREATE DELETEHex code : �

CONFIG 1

- To configure a print object in a report:1. Select print as the object type.

2. Enter a hex code asindicated in the printerspecifications.

3. Press [ENTER]. Text followingthe print command has thedesignated print style.

Figure 4.4.4. Report Configuration Screen with Print Object

CC: 4-4-10


How to Begin a New Report Page

The newpage object causes a new report page to begin four lines afterthe newpage object has been inserted. Figure 4.4.5 shows theprocedure for configuring the newpage object in a report.





BOILER #1 .089 .903 .442 .96 .54BOILER #2 .087 .877 .368 .65 .69BOILER #3 .077 .857 .314 .21 .34

- - - - - - - - - - - - - - - - - - - - - - - - - - -SUBTOTAL ACCUM #1 ACCUM #2 ACCUM #3 ACCUM #4 ACCUM #5

>

newpageType :�newpage Color :�1n white Row :�30 Col :�88

CREATE DELETE

CONFIG 1

- To configure a new page:1. Select newpage as the object type.

2. Press [ENTER]. Aprompt > appears.

The new report page appears onthe fourth line (with a top margin ofthree lines).

Figure 4.4.5. Report Configuration Screen with Newpage Object

CC: 4-4-11


Configuring Text in a Report

This section explains how to configure text to appear in a report.

How to Print Regular-sized Text

Regular-sized text can be used in a report body for titles, labels, columnheadings, and comments. A text object may be created in either of twoways. Figure 4.4.6 shows the procedures for configuring text in the bodyof a report.


****************** START OF REPORT ******************

Production Report for 02:Feb:96

Production Report for

textType :�text Color :�1n white Row :�13 Col: : �5

CREATE DELETEText :�Production Report for

CONFIG 1

- To configure text in the body of a report:1. Select text as the object type.

2. Type in text in the “Text”field.

or 1. Cursor to the desiredlocation in the report body, type intext, and press [ENTER].

3. Press [ENTER]. The textappears in the body of thereport.

Figure 4.4.6. Report Configuration Screen with Text Object

CC: 4-4-12


How to Print Oversized Text

Oversized characters are called banners. You can use banners in areport as titles or headers. Banner styles include ban1 and ban2objects. Ban1 uses letters 8 columns wide and 10 rows high. Ban2 usesletters 16 columns wide and 10 rows high.

To center the banner on the report page, you need to calculate thecolumn location of the left edge. For example, if ban1 is selected, andthe banner uses six characters, use this formula:

6 letters � 8 columns per letter = 48 columns total width80 columns× 48 columns = 32 columns unused32 columns � 2 = 16 columns on either side of bannerBegin banner in column 17.

Figure 4.4.7 shows the procedure for configuring a banner object.


****************** START OF REPORT ******************

REPORT

ban1Type :�ban1 Color :�1n white Row :�13 Col: : �6

CREATE DELETEText :�REPORT

CONFIG 1

- To configure a banner object:1. Select ban1 or ban2 as the object type.

2. Type in the text to beused as a banner.

3. Press [ENTER]. Thebanner appears in thebody of the report.

Figure 4.4.7. Report Configuration Screen with Banner Object

CC: 4-4-13


Configuring Operator Comments in a Report

The comment object allows an operator to configure comments in areport without a configuror’s key. Comments must be added to a reportconfiguration screen in order to be included in a generated report.Figure 4.4.8 shows the procedure for configuring comments in a report.


****************** START OF REPORT ******************

comment Row :�13 Col: : �6Type :�comments CREATE DELETELength:�70Text :�

CONFIG 1

- To configure comments in areport:

1. Select comment as the objecttype.

2. Determine the length of thecomment in the “Length”field.

3. Type in the text (up to70 characters).

4. Press [ENTER]. Thecomment appears in thereport.

Figure 4.4.8. Report Configuration Screen with Comment Object

CC: 4-4-14


Configuring Block Information in a Report

Information from Controlblocks or I/O blocks can be configured in areport.

How to Configure a Block Tag

You can use block tags as labels in a report to identify the tag of aspecified block. Figure 4.4.9 shows the procedure for configuring ablock tag in a report.


****************** START OF REPORT ******************

MCIN-1U

CON-1U

tagType :�tag Color :�1n white Row :�26 Col :�13

Tag :�CON-1U CREATE DELETE

CONFIG 1

- To configure a block tag in a report:1. Select tag as the object type.

2. Type the tag or theaddress of the tag in the“Tag” field.

3. Press [ENTER]. The tagappears in the body of thereport.

Figure 4.4.9. Report Configuration Screen with Tag Object

CC: 4-4-15


How to Configure a Block Address

You can use block addresses as labels in a report to identify theaddress of a specified block. Figure 4.4.10 shows the procedure forconfiguring a block address in a report.


****************** START OF REPORT ******************

=1AA101

=1AA201

addrType :�addr Color :�1n white Row :�26 Col :�13

Tag :�=1AA201 CREATE DELETE

CONFIG 1

- To configure a block address in a report:1. Select addr as the object type.

2. Type the address or thetag in the “Tag” field.

3. Press [ENTER]. Theaddress appears in thebody of the report.

Figure 4.4.10. Report Configuration Screen with Address Object

CC: 4-4-16


How to Configure a Block Descriptor

You can use block descriptors to provide additional information about ablock in a report. Block descriptors can contain up to 24 characters.Figure 4.4.11 shows the procedure for configuring a descriptor in areport.


****************** START OF REPORT ******************

Tank 3 Level 726.26 liters

Tank 4 Level 425.48 liters

descriptorType :�descriptor Color :�1n white Row :�26 Col :�13


CONFIG 1

- To configure a descriptor in a report:1. Select descriptor as the object type.

2. In the “Tag” field, type thetag or address of the blockwhose descriptor is to bedisplayed.

3. Press [ENTER]. Thedescriptor appears in thebody of the report.

Figure 4.4.11. Report Configuration Screen with Descriptor Object

CC: 4-4-17


How to Configure a Block Function

You can use block functions as descriptions in a report to identify thefunction of a specified block. Figure 4.4.12 shows the procedure forconfiguring a block function in a report.


****************** START OF REPORT ******************

=1AA101 I/O BLOCK

=1AA201 PI Controller

funcType :�func Color :�1n white Row :>26 Col :>18


CONFIG 1

- To configure a block function in a report:1. Select func as the object type.

2. In the “Tag” field, type thetag or address of the blockwhose function is to bedisplayed.

3. Press [ENTER]. Thefunction appears in thebody of the report.

Figure 4.4.12. Report Configuration Screen with Function Object

CC: 4-4-18


How to Configure a Block Mode

You can use block modes in a report to describe the mode of operationof a specific block. Figure 4.4.13 shows the procedure for configuring ablock mode in a report.


****************** START OF REPORT ******************

=1AA101 MANUAL

=1AA201

modeType :�mode Color :�1n white Row :>26 Col :>18


CONFIG 1

- To configure a block mode in a report:1. Select mode as the object type.

2. In the “Tag” field, type the tagor address of the blockwhose mode is to bedisplayed.

3. Press [ENTER]. The modeappears in the body of thereport.

Figure 4.4.13. Report Configuration Screen with Mode Object

CC: 4-4-19


How to Configure Block Units

You can use block units as labels for specified blocks. Figure 4.4.14shows the procedure for configuring block units in a report.


****************** START OF REPORT ******************

MCIN-1U

GALLONS

5679

unitType :�unit Color :�1n white Row :�30 Col :�22

Tag :�MCIN-1U CREATE DELETE

CONFIG 1

- To configure block units in a report:1. Select unit as the object type.

2. In the “Tag” field, type thetag or address of the tagwhose units will bedisplayed.

3. Press [ENTER]. The unitsappear in the body of thereport.

Figure 4.4.14. Report Configuration Screen with Unit Object

CC: 4-4-20


How to Configure Block Values

You can configure block values in the body of a report. Values can alsobe added, subtracted, multiplied and divided in a report. Figure 4.4.15shows the procedure for configuring block values in a report.


****************** START OF REPORT ******************

GALLONSMCIN-1U 5679MCIN-2U 1234

valueType :�value Color :�1n white Row :�30 Col :�68

Tag :�MCIN-2U CREATE DELETE

Accum :� +1

CONFIG 1

- To configure block values in a report:1. Select value as the object type.

2. In the “Tag” field, type the tagor address of the tag whosevalue will be displayed.

3. If the value is to be combined in acalculation, type in the accumulatornumber with a mathematical operator(+, --, *, / ) in the “Accum” field.

4. Press [ENTER]. Thevalue appears in thebody of the report.

Figure 4.4.15. Report Configuration Screen with Value Object

CC: 4-4-21


How to Perform Calculations

In a report, any number of value objects can be added, subtracted,multiplied, and divided together. The results of these calculations areplaced in accumulators, or storage areas. A report can use up to 20accumulators. Accumulate objects are used to configure accumulators.

The “Accum” field in the value object Report Configuration Windowdesignates if the value is to be part of a calculation and in whataccumulator the result of the calculation will be stored.

NOTE: Value objects in accumulators are processed on the basis oflocation: top to bottom, left to right.

- To configure an accumlulator:

1. Enter an accumulator number (1--20) with a mathematicaloperator (--, +, *, / ) in the “Accum” field of the value object ReportConfiguration Window.

NOTE: Depending on how the accumulator is specified,subtraction (--) and division (/) operators are placed before orafter the accumulator number. For example, 5/ means thataccumulator #5 is divided by the value; /5 means that the value isdivided by accumulator #5. Addition (+) and multiplication (*)operators can be entered before or after the accumulatornumber. For example, *5 or 5* will give the same result.

2. Configure the accumulate object.

As an example, Figure 4.4.16 and Figure 4.4.17 show how toobtain a steam flow total and a mean average of the total.Figure 4.4.18 shows the procedure for configuring an accumulateobject for an accumulator.

CC: 4-4-22


Type :�accumulate Color :�1n whiteAccum:� 1 Clear ? �yesDecimal Point : �3

valueType :�value Color :�1n whiteTag :�MCIN-3UAccum :� +1, +2







BOILER #1 .089 .903 .442 .96 .54BOILER #2 .087 .877 .368 .65 .69BOILER #3 .077 .857 .314 .21 .34-----------------------------------------------------------------

SUBTOTAL ACCUM #1 ACCUM #4 ACCUM #5 ACCUM #6 ACCUM #7

Individual values can beconfigured to be part ofa calculation. In thisexample, the threevalues in the TotalSteam Flow column areconfigured to be addedtogether. The result ofthis addition is placed inaccumulator #1 andaccumulator #2.

Accumulator #1 isconfigured.

Figure 4.4.16. Report Configuration Screen with Value and Accumulator Objects

CC: 4-4-23






BOILER #1 .089 .903 .442 .96 .54BOILER #2 .087 .877 .368 .65 .69BOILER #3 .077 .857 .314 .21 .34-----------------------------------------------------------------_______________________________________SUBTOTAL ACCUM #1 ACCUM #4 ACCUM #5 ACCUM #6 ACCUM #7 3

AVERAGE ACCUM #2

Type :�accumulate Color :�1n whiteAccum:� 2 Clear ? �yesDecimal Point : �3

valueType :�value Color :�1n whiteTag :�NUM-3UAccum :�2/

A mean average of the value in accumulator #2 canbe obtained by dividing the contents of accumulator#2 by 3. The value “3” must be first be configured ina block.

Accumulator #2 isconfigured.

Figure 4.4.17. Report Configuration Screen with Value Objects

CC: 4-4-24






BOILER #1 .089 .903 .442 .96 .54BOILER #2 .087 .877 .368 .65 .69BOILER #3 .077 .857 .314 .21 .34- - - - - - - - - - - - - - - - - - - - - - - - - -SUBTOTAL ACCUM #1 ACCUM #2 ACCUM #3 ACCUM #4 ACCUM #5

Type :�accumulate Color :�1n white Row :�30 Col: �66

Accum:� 1 Clear ? �no

Decimal Point :�

CONFIG 1

3. Designate the numberof decimal places (up to6) in the “Decimal Point”field.

4. If “yes” is entered in the“Clear” field, theaccumulator resets to zeroafter the result is displayed.

5. Press [ENTER]. Theaccumulator appears in thebody of the report.

- To configure an accumulate object:1. Select accumulate as the object type.

2. Type an accumulatornumber (1--20) in the“Accum” field.

Figure 4.4.18. Report Configuration Screen with Accumulator Object

CC: 4-4-25


How to Configure Trend File Information in a Report

The trend log object allows trend data to be included in a report.Figure 4.4.19 shows the trend log Report Configuration Window withdefault values. Table 4.4.4 describes the trend log configuration fields.Figure 4.4.20 and Figure 4.4.21 show examples of trend log objects andthe resulting reports.

REPORT CONFIGURATION 28-Aug-98 14:18:04

****************** START OF REPORT ******************

Detail :�yType :�trend log Color :�1n white Row :�38 Col :�15 Time : �y

Data : �yFile Name:�trf1 Node :�28 Scaled :�100 CREATE DELETE Mean :�y �y

Total :�y �yTag �TREND 2/PV Accum :�none Inter :�5 secs Minimum:�y �y

Maximum �y �yTime :�10:50:00 Duration :�10 mins MM Time:�y

CONFIG 1

Select trend log as the object type.

CREATE must be used to createor to modify a trend log object.

Figure 4.4.19. Report Configuration Screen with Trend Log Object

CC: 4-4-26



Data : �yFile Name:�trf1 Trend Node :�28 CREATE DELETE Mean :�y �y

Total :�y �nScaled :�1 Accumulator :�none Tag �tab/A Minimum:�y �n

Maximum:�y �nTime :�00:00:00 Duration :�10 hr Interval :�1 hr MM Time:�n

REPORT

01:00:00 85.06 84.9802:00:00 86.05 84.9603:00:00 83.45 84.7604:00:00 85.67 84.8905:00:00 84.35 84.9406:00:00 85.90 84.7607:00:00 86.23 84.5008:00:00 84.78 84.8809:00:00 87.23 84.8210:00:00 88.01 84.81Mean 84.95 84.31Total 941.68 932.61Minimum 83.45 82.11Maximum 88.01 86.34

The left column determines whether or not the informationis included in each column.

In this example, each column includes interval values(detail), mean, total, maximum, and minimum.

Datacolumn

Meancolumn

Timecolumn

Detail----Determines whether or notinterval values are included

The right column determines which columns areincluded in the report.

In this example, the report includes the time,data, and mean columns.

Figure 4.4.20. Sample Trend Log Object Configuration Window and Resulting Report

CC: 4-4-27



Data : �nFile Name:�trf1 Trend Node :�28 CREATE DELETE Mean :�n �n

Total :�y �nScaled :�1 Accumulator :�none Tag �tag/A Minimum:�n �y

Maximum:�n �nTime :�00:00:00 Duration :�10 hr Interval :�1 hr MM Time:�n

REPORT

01:07:34 1699.6002:07:34 1699.2003:07:34 1666.6004:07:34 1697.5005:07:34 1699.4006:07:34 1698.7007:07:34 1695.7008:07:34 1690.0009:07:34 1697.6010:07:34 1685.80Total 101755.20

MinimumIn this example, the report includesthe time and minimum columns.

In this example, the report includesthe detail and total rows.

Figure 4.4.21. Sample Trend Log Object Configuration Window and Resulting Report

CC: 4-4-28


Table 4.4.4. Trend Log Field Description

Field Description

Accum Represents a mathematical expression of the trend data applied to a reportaccumulator. Accumulators in trend log objects can accumulate one column of trenddata.

The mathematical operators available are: + (addition)-- (subtraction)/ (division)* (multiplication)

When using an accumulator, only one column of data (“Mean”, “Total”, “Minimum”, or“Maximum”) can be included in the trend object type.

NOTE: For information on configuring an accumulate object, see “How to PerformCalculations (Accumulate Object)” on page 4-4-21.

Data Represents the instantaneous value of the “Tag” being trended. The yes/no fieldspecifies whether or not a column of instantaneous data is included in the report.

Detail Represent interval values. The yes/no field specifies whether or not rows of intervalvalues are included in the report.

Duration The length of time of the trend log data that is included in the report.

File Name Trend file names trf1 through trf9.

Inter The time interval of trend log entries in the report. For example, an “Interval” entry of1 hr provides trend data for every hour of the “Duration” time period. Figure 4.4.20shows an example of a duration and an interval.

Maximum Represents the maximum value. The first yes/no field specifies whether or not a rowof maximum values is included in the report. The second yes/no value specifieswhether or not a column of maximum values is included in the report.

Mean Represents the mean average. The first yes/no field specifies whether or not a row ofmean values is included in the report. The second yes/no value specifies whether ornot a column of mean values is included in the report.

Minimum Represents the minimum value. The first yes/no field specifies whether or not a rowof minimum values is included in the report. The second yes/no value specifieswhether or not a column of minimum values is included in the report.

MM Time The yes/no field indicates whether or not a minimum time and maximum time iscalculated over the “Duration” for the trend data.

If more than one minimum or maximum occurred, the first minimum or maximum isdisplayed.

Scaled Scaling factor for the trend values. All trend values shown on the report for the objecttype are multiplied by the “Scaled” factor.

Tag Tag of the trended variable. This field must have a value other than “none” entered.


CC: 4-4-29


Table 4.4.4. Trend Log Field Description (continued)

Field Description

Time The beginning time of the trend log data that is included in the report. The time canbe entered in the following ways:

NOTE: You can enter a maximum of eight characters. When you specify a relativevalue for day or time, you will not be able to specify seconds and you may be limitedas to the number of characters available to specify minutes.

--DD/HH:MM:SS specifies a start time relative to the day or the generation of thereport; for example, --2/10:15 specifies that the report includestrend log data starting 2 days, 10 hours, and 15 minutes beforethe generation of the report.

HH:MM:SS specifies at time; for example, 16:00:00 specifies that the reportincludes trend log data starting at 4 P.M.

--HH:MM:SS specifies an amount of time prior to generation of the report; forexample, --8:00:00 specifies that the report includes trend log datastarting 8 hours before the report generation time.

block variable specifies a number of seconds previous to the report generationtime; for example, a block variable with a value of 120 specifiesthat the report includes trend log data starting 120 seconds beforethe report generation time.

Time Represents the time values of instantaneous data and the labels of the other valuefields (Mean, Total, Maximum, Minimum, MM Time). The yes/no field specifieswhether or not the Time column is included in the report.

Total Represents the total value. The first yes/no field specifies whether or not a row oftotal values is included in the report. The second yes/no value specifies whether ornot a column of total values is included in the report.

Node Node on which the trend file resides.

CC: 4-4-30


How to Use an Accumulator with a Trend Log Object

The accumulate object is used to accumulate one column of data from atrend file. Figure 4.4.22 shows examples of using an accumulator witha trend log object. In both examples, the trend log object is used to getdata from trend file trf1.

Detail :�nType :�trend log Color :�1n white Row :�38 Col :�15 Time : �n

Data : �yFile Name:�trf1 Trend Node :�28 CREATE DELETE Mean :�n �n

Total :�n �nScaled :�1 Accumulator :�3- Tag �tag/A Minimum:�n �n


In this example, the trend data value is subtracted from the value in accumulator 3 and theresult is put into accumulator 3.

For example, if the trend data is 173.50 and the value in accumulator 3 is 92.75, thecalculation becomes: 92.75 -- 173.50 = --80.75. The value --80.75 is put into accumulator 3.

In this example, the value in accumulator 3 is subtracted fromthe trend data value and the result is put into accumulator 3.

For example, if the trend data is 173.50 and the value inaccumulator 3 is 92.75, the calculation becomes: 173.50 --92.75 = 80.75. The value 80.75 is put into accumulator 3.

NOTE: In both examples, thetrend log object must containonly one column of data.

Detail :�nType :�trend log Color :�1n white Row :�38 Col :�15 Time : �n

Data : �yFile Name:�trf1 Trend Node :�28 CREATE DELETE Mean :�n �n

Total :�n �nScaled :�1 Accumulator :�3- Tag �tag/A Minimum:�n �n


Figure 4.4.22. Report Configuration Window with Trend Log Object and Accumulator

CC: 4-4-31


Configuring Time and Date Information in a Report

This section explains how to configure a report so that the time and dateit was generated automatically appear in the report.

How to Configure the Current Time

The time object shows the current hour, minutes, and seconds(hh:mm:ss) in a report. The time displayed in a report is the same asthe time displayed in the top corner of the CRT screen. Figure 4.4.23shows the procedure for configuring a time object in a report.

NOTE: The time object does not determine what time a report isgenerated.

Report Configuration 02:Aug:96 09:31:16

****************** START OF REPORT ******************

Report generated at 09:30:05

timeType :�time Color :�1n white Row :>26 Col :>25

CREATE DELETE

CONFIG 1

- To configure a time object in a report:1. Select time as the object type.

2. Press [ENTER]. A time object that displays the currenthour, minutes, and seconds appears in the body of thereport.

Figure 4.4.23. Report Configuration Screen with Time Object

CC: 4-4-32


How to Configure the Current Date

A date object shows the day, month, and year (dd:mm:yy) in a report.The date displayed in a report is the same as the date displayed in thetop corner of the CRT screen. Figure 4.4.24 shows the procedure forconfiguring a date object in a report.

NOTE: The date object does not determine when a report is generated.

Report Configuration 02:Aug:96 09:31:16

****************** START OF REPORT ******************

Report generated on 02:Feb:96

Type :�date Color :�1n white Row :>26 Col :>25

CREATE DELETE

CONFIG 1

- To configure a date object in a report:1. Select date as the object type.

2. Press [ENTER]. A date with the current day,month, and year is displayed on the report.

Figure 4.4.24. Report Configuration Screen with Date Object

CC: 4-4-33


Configuring Console Lists in a Report

Console lists can be inserted into a report generated by that console.Console lists include alarm lists, event lists, status lists, and theoperator change log. The advantages of including console lists in areport is that reports can be configured to include narrative text as wellas being configured to generate on a regular basis.

You can configure a console lists to generate a printout at a certaintrigger point. A trigger point is configured on the Alarm ListConfiguration and the Event List Configuration screens. Once a list hasbeen printed out the information is no longer available to be included ina report.

When inserted into a report, the contents of a list may be “filtered” toinclude only a specified range of block addresses, or entries after aspecified time. The report list object does not receive data until thereport is generated.

NOTE: The report can includes entries from a console list forapproximately 7 days (or 9999 minutes).

CC: 4-4-34


Configuring the List Object

Figure 4.4.25 shows the Report Configuration Window with list objectentries. Table 4.4.5 gives the Configuration Window field descriptions.

Formatting a List

A console list occupies 80 columns.


****************** START OF REPORT ******************

LIST: lst=System Status, tm=0, hdr=no, #1n=0, bk1=any, bk2=any

listType :�list Color :�1n white Row :�26 Col :�2

List :�System Status Hdrs :� no CREATE DELETE

Time Period :�none # lines ;� none Blk1 :� any

Alarm Format :� 80C Blk2 :� anyCONFIG 1

Select list as the object type.

Figure 4.4.25. Report Configuration Screen with List Object

CC: 4-4-35


Table 4.4.5. List Object Configuration Screens


Alarm FormatThe column width of the report. The maximum columnwidth is 132 characters. Use the [NEXT OPTION] or[LAST OPTION] key to step through options.

80O, 80C, 132

Blk1*

The lowest-numbered block for which data is to beincluded.

NOTE: If information other than the default value isentered in this field, it must agree with the block range inthe specified list.

Any block address lowerthan Blk2 entry.

Blk2*

The highest-numbered block for which data is to beincluded.

NOTE: If information other than the default value isentered in this field, it must agree with the block range inthe specified list.

Any block address higherthan Blk1 entry.

Hdrs Determines if a full header will be printed with the list. yes, no

lines*

The number of lines from the list to be included in thereport, beginning with the most recent entry. If “none”, alllines that otherwise qualify will be included.

NOTE: If information other than the default value isentered in this field, it must agree with the number oflines in the specified list.

1--2000

List*

Identifies the specific list to be inserted into the report.Use the [NEXT OPTION] or [LAST OPTION] key to stepthrough options.

If you select the Alarm Area List entry, the “Area Name”field appears for you to enter the desired area name.

none,Batch Alarm List

Process Alarm List,

Critical Alarm List,Advisory Alarm ListHardware Alarm List,System Status List,Disk Event List,

Operator Change Log,Event Lists #1--10,Alarm Area List,

Suppressed Alarm List

Plant Area

Time Period*

Counts back in minutes from the time the report isgenerated. If “none”, the report will go back to the lastavailable alarm information.

NOTE: To use this field, the time must agree with thealarm time period in the specified list. For example, if 45minutes is entered in the “Time Period” field, and thealarm period of the list is 60 minutes, 15 minutes of thealarm list will not be included.

1--9999 min

* List entries that meet the conditions specified in all of these fields are included in the list object.

CC: 4-4-36


How to Configure Another Report in a Report

The generate object allows a generated report to be included in anotherreport. Figure 4.4.26 shows the generate object default entries and howto configure the generate object. Table 4.4.6 lists the generate objectReport Configuration Window fields.

REPORT CONFIGURATION 21-Jul-96 14:18:04

****************** START OF REPORT ******************

Type :�generate Color :�1n white Row :�38 Col :�15

Include:� , CREATE DELETE

After this time : 25-Jul-96 �08:30:04 Mark :�no Only Unprinted�no

Last number of files :�0 Header :�no File Number :�0

CONFIG 1

- To configure the generate object:1. Select generate as the object type.

Press [ENTER].

Cursor to the “CREATE” fieldand press [ENTER].

Figure 4.4.26. Report Configuration Screen with Generate Object

CC: 4-4-37


Table 4.4.6. Generate Field Descriptions

Field Description

Include The volume and filename of the generated report that is included in this object. Onlygenerated reports can be included in another report.

After this time* The beginning date and time of reports that can be included in this object. Reportsgenerated after this date and time can be included in this object.

Mark* Indicates whether or not the included reports have already been included in reports.If “Yes” is entered, the system checks to see if the report is marked. If the report ismarked, it will not be included. If the report is not marked, the report will be markedand included.If “No” is entered, the report is included.

Only Unprinted* Indicates whether or not to include only unprinted reports in this object.

Last number offiles*

Indicates a specific number of the most recently generated reports to include in thisobject. For example, an entry of 3 in this field indicates that the last three generatedreports (1, 2, and 3) are included in this object.

An entry of 0 (default entry) disables this field.

Header Indicates whether or not the header information from the included report file isincluded in this object.

File Number* Indicates a specific report file number to be included in this object. The report filenumbers are listed on the Report File Contents screen for each filename.

An entry of 0 (default entry) disables this field.

* Any report generation that meets the values specified in these fields is included in the generate object.

CC: 4-4-38


Generating Reports

Reports can be configured to generate and print automatically usingfields on the Report Configuration screen.

How to Generate a Report Based on Time and Date

Reports can be configured to generate automatically on a time and datebasis. Figure 4.4.27 shows the procedure for entering time parameterson the Report Configuration screen to control generation of a report. Inthis example, the report will be generated at 12:05 AM, 8:05 AM, and4:05 PM every day. Entries made in the “Time Entry” field are displayedon the appropriate line above the entry area. Reports configured to printbased on time must have the “Active ?” field in the Report ConfigurationScreen set to “yes.”

Figure 4.4.28 shows the same report modified to print only on weekdays(Monday -- Friday). The same procedure can be used for the “Month”and “Day/month” fields. For additional information on entering timeparameters, see Table 4.4.1.

Generate on alarm/event from:�


�Time Entry :�

Command : �

- To enter timeparameters:

1. Use [NEXT OPTION]to select desired timeparameter. Thenpress [ENTER].

2. Enter hours whenreport should begenerated.(Example:midnight, 8AM,4PM). Thenpress [ENTER].

Generate on alarm/event from :�

Month : anyDay/month: anyDay/week : anyHour : 0,8,16Minute : never

�Hour :�0,8,16

Command : �

3. Repeat procedurefor ”Minutes“ entry.(Report generatesat 12:05AM,8:05AM, & 4:05PM)


Month : anyDay/month: anyDay/week : anyHour : 0,8,16Minute : 5

�Minute :�5

Command : �

4. Set the“Active ?”field to “yes.”

Active ? �yes

Figure 4.4.27. Generating a Report Based on Time

CC: 4-4-39


Entries are displayed as a series ofvalues regardless of the entryformat. Day/week can be enteredas any of the following:

D 2--6

D Mon--Fri

D Mon,Tue,Wed,Thu,Fri


Month : anyDay/month: anyDay/week : Mon,Tue,Wed,Thu,FriHour : 0,8,16Minute : 5

�Day/week:�Mon,Tue,Wed,Thu,Fri

Command : �

Figure 4.4.28. Generating a Report Based on Date

CC: 4-4-40


How to Generate a Report Based on Alarms or Events

Alarms or events from ControlBlocks or input blocks can be configuredto generate a report automatically. Figure 4.4.29 shows the procedurefor configuring alarms and events on the Report Configuration screen.Figure 4.4.29 also shows examples of alarm and event entries.

NOTE: To generate a report, the alarm or event must be received bythe console. In other words, the block that generates the alarm or eventmust be in a plant unit that has been assigned to the console or, if plantunits are not used in your system, the node containing the block mustbe owned by the console. For information about plant units and nodeownership, see Chapter 1 of this manual.

NOTE: If a report is configured to generate on a ControlBlock logic stepevent, the logic step must have “Log�None” configured for the report togenerate from the event.

NOTE: If a report is configured to generate on an event, the associatedevent number must be configured in a console event list. Forinformation about event lists, see Chapter 6 of this manual.

REPORT CONFIGURATIONDescription :�

Created : neverFilename : �Size :0 Last saved : neverSTATUS : new file Free Space :100 Backed up : never

Auto Print ?�yes Max number of reports :�3 Print node :�16 Active ? �yes

Generate on alarm/event from : �2C12 �=3A-9/PV �=2A-20/a �=5A-10

Any hardwarealarm, processalarm or event froman input block

Any process alarmfrom a ControlBlockcontinuous input

Any process alarm,hardware alarm, or eventfrom a ControlBlockdiscrete step

Any process alarmfrom a ControlBlockcontinuous output

- To configure alarms and events on the Report Configuration screen:1. Cursor to the “Generate on alarm/event” field and enter the tag or

address of the variable in any of the four entry fields.

2. Press [ENTER].

Figure 4.4.29. Generating a Report Based on Alarms and Events

CC: 4-4-41


How to Generate a Report from the Report Configuration Screen

A report can be generated from the Report Configuration screen. Ifchanges have been made to the configuration of the body of the report,the report must first be saved to disk so that the changes are included inthe generated report. Figure 4.4.30 shows the procedure for generatinga report from the Report Configuration screen.

REPORT CONFIGURATION 21-Jul-96 14:18:04Description :�

Created : neverFilename : �Size :0 Last saved : neverSTATUS : new file Free Space :100 Backed up : never


Generate on alarm/event from :�RPTTEST � � �


�TIME ENTRY :�

Command : � Generate this Report

- To generate a report from the Report Generation screen:1. Cursor to the “Command” Field and press [NEXT OPTION] to

get the “Generate this Report” command.

2. Press [ENTER]. Areport is generated.

Figure 4.4.30. Report Configuration Screen with Generate this Report Command

CC: 4-4-42


How to Print a Report When it is Generated

A report can be configured to print automatically when it is generated.Figure 4.4.31 shows the procedure for configuring the Auto Printfunction.

REPORT CONFIGURATION 21-Jul-96 14:18:04Description :�

Created : neverFilename : � Size :0 Last saved : neverSTATUS : new file Free Space :100 Backed up : never


- To configure the Auto Print function:1. Cursor to the “Auto Print” field and type in “yes”

to receive a printout of the report when thereport is generated.

Figure 4.4.31. Report Configuration Screen with Auto Print Field

CC: 4-5-1

RS3: Reports Saving a Report to Disk

Section 5:Saving a Report to Disk

Initially, entries made on the Report Configuration screen are stored inRAM memory. The configuration entries made in the body of a reportwill not take effect until the report configuration has been written to thedisk. A report configuration is written to disk in two ways:

D Whenever the configuror exits the Report Configuration screen,the configuration is automatically written to disk, if changes havebeen made.

D A “Save to Disk” operation can be executed using the“Command” entry field in the top portion of the ReportConfiguration screen. Select the operation using [NEXTOPTION], then press [ENTER].

CC: 4-5-2

RS3: Reports Saving a Report to Disk

CC: 4-6-1

RS3: Reports Hints for Configuring and Using Reports

Section 6:Hints for Configuring and Using Reports

This section discusses some problems you might have whenconfiguring reports, along with some configuration tips.

CC: 4-6-2



- I’m having trouble selecting objects.

To select an object, you must put the cursor at the upper left cornerof the object.

- The screen doesn’t display all lines of a report.

A console can only display 92,000 characters or 2174 lines of areport. The limit only affects the display of a report; it does not affectthe printing of a report.

CC: 4-6-3


Configuration Tips

- How to move an object

When you delete or create an object, the object is kept in a buffer.You can then recreate the object.

Therefore, to move an object:

1. Delete the object.

2. Cursor to the new location, and press [SELECT].

3. Cursor to the Create field and press [ENTER]. The object is nowin the new location.

- How to copy an object

When you delete or create an object, the object is kept in a buffer.

Therefore, to copy an existing object:

1. Delete the object.

2. Create the object again by moving the cursor to Create andpressing [ENTER].

3. Cursor to the location where you want the copy, and press[SELECT].

4. Cursor to the Create field and press [ENTER]. The object hasbeen copied in the new location.

5. Repeat steps 3 and 4 as many times as you need.

To create a new object and make copies of it:

1. Create the object.

2. Follow steps 3 through 5 in the previous procedure.

Marking Lines in Reports

You can use the [CTRL] [G] function to mark two places in a long reportto move quickly from one line in the report to another. To mark a line,you move the cursor to that line and press [CTRL] and [G]. Then youmove the cursor to another line in the report and press [CTRL] and [G]to mark that line. Each time you press [CTRL] [G], the cursor will movebetween these two lines until you physically move the cursor to anotherline and mark it with the [CTRL] [G] function.

CC: 4-6-4


ContentsRS3: Trending


Chapter 5:Trending

Section 1: Trending Operations 5-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Console Trending Capabilities 5-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How Trend File Information is Stored 5-1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .What Block Variables Can be Trended 5-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using Trending Screens 5-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Enabling and Disabling Trending 5-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Trending Condition upon Console Restart 5-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: Configuring Trend Files 5-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Trend File Setup Screen 5-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring a Trend File 5-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining When and How Often Data is Stored(Frequency and Duration Fields) 5-2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Configuring Trend Groups 5-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The Trend Group Configuration 5-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Trend Group Displays 5-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the Slidewire 5-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Trend Group Scaling 5-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Viewing Trend Data 5-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .How Often Trend Group Displays Update 5-3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Archive Trend Data 5-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

How a Backup Trend File is Saved 5-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Restoring and Reading Trend Archive Data 5-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Restoring and Reading Trend Archive Data from Tape 5-4-3. . . . . . . . . . . . . . . . . . .

Section 5: Hints for Configuring Trending 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Copying Trend Files 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Determining Trend Group Update Time 5-5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: ii

RS3: Trending Contents

List of Figures

Figure Page

5.1.1 Trend Group Screen Example 5-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1.2 The Trending Process 5-1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.1 Trend File Setup Screen 5-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.2 Trend File Configuration Screen 5-2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.3 Trend File Configuration Screen with Frequency and Duration Fields 5-2-7

5.3.1 Trend Group Configuration Screen 5-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3.2 Trend Group Screen with Slidewire 5-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3.3 Trend Group Screen with Scaling Fields 5-3-7. . . . . . . . . . . . . . . . . . . . . . . . .

5.3.4 Trend Group Screen with Fields that Determine Data Points and Time 5-3-8

5.3.5 Update Time Algorithm 5-3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3.6 Update Time in Even Seconds 5-3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3.7 Update Time in Fractions of Seconds 5-3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4.1 The Process of Saving a Trend File 5-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4.2 Restoring and Reading a Trend File 5-4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iii

ContentsRS3: Trending

List of Tables

Table Page

5.2.1 Trend File Setup Screen Fields 5-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.2 Trend File Configuration Screens 5-2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3.1 Trend Group Configuration Screen Fields 5-3-3. . . . . . . . . . . . . . . . . . . . . . .

CC: iv

RS3: Trending Contents

CC: 5-1-1

RS3: Trending Trending Operations

Section 1:Trending Operations

Trending is a process used to store data so that it can be accessed andanalyzed. The trend data may reside on any MTCC on the Peerway.

Trending information is organized in trend files that reside on the MTCChard disk. Trend files determine the frequency, duration, data type, andother information about the trend data. Block variables from trend filescan be configured in trend group displays.

Figure 5.1.1 shows an example of a Trend Group screen.

4: No. 3 Boiler Drum 28-Jul-96 16:13:50

16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current

>STACK 1 FCC-A

Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-Jan-89Data Pts >240 Value at

Tag Descriptor 28-Jan-86 16:08:00 Units Eng. Min Eng. MaxStack 1 SENSOR A Drum Level 0.00 Inches -25.00 25.00STACK 1 FCC-A Flow 160.00 KLb/Hr 0.00 200.00STACK 1 DPR-A Drum Press 200.0 PSIG 0.0 600.0STACK 1 FCC-B Steam Flow 150.00 KLb/Hr 0.00 200.00

CONFIG 1

>200.00

100.00

KLb/Hr

>0.00

>100.

50.

%

>0.

Figure 5.1.1. Trend Group Screen Example

CC: 5-1-2


Console Trending Capabilities

Trend data is stored in trend files.

D Up to 10 trend files can be configured for each MTCC.

D Up to 200 block variables can be configured per console.

D Up to 80 block variables can be configured in one trend file.

Trend data consists of block variable values.

D Trend data is stored on the console hard disk.

Each ControlBlock variable that is configured for trending takes upavailable trend space on the associated Controller Processor.

D Each MPCI allows 40 links

D Each MPCII allows 80 links (see CB: 3-4 for more information)

D Each MPCI has 1856 bytes available for trending.

D Each MPCII has 4600 bytes available for trending.

D Each continuous block variable configured with a trendingfrequency of a 5-second multiple (5 seconds, 10 seconds, 15seconds, etc.) uses 14 bytes. Any other block variable uses 46bytes.

Trend variables can be configured in trend groups so that trend datacan be displayed.

D Each trend group can contain up to 4 trend variables.

D Each console can contain up to 400 trend groups.

CC: 5-1-3


How Trend File Information is Stored

Trend files are stored in the Trend Data Folder on a console disk. Youshould configure the disk to provide enough storage space for theconfigured trend data. (For information about configuring the disk, seeDT:3.)

One of the trend files (1--9) may be used to generate a system alarmnotifying the user to back up the Trend Data Folder. If a trend file is notbacked up, the file is deleted when the disk becomes full. Section 3describes how to configure a Trend Overflow Warning, and Section 4describes how trend files can be backed up to tape or disk.

Figure 5.1.2 shows how trend files are processed and how trend fileinformation is stored.

A trend file is configured.

Once the file is configured, trendingbegins. The 60 most current data pointsare stored in the console buffermemory.

ConsoleBufferMemory

trf#b file

When trending is enabled for the firsttime after a trend file is configured, thetrend file is created on the disk. Thetrend file name is trf# where # is thenumber of the trend file, (e.g., trf1 totrf9).

trf# file

When the trf# file is full, the file isrenamed trf#b and a new trf# file iscreated. An alarm message to back upthe trf#b file is displayed when thisprocess occurs. The trf#b file can bebacked up to tape or to another disk.

Trend FileConfiguration

screen

Figure 5.1.2. The Trending Process

CC: 5-1-4


What Block Variables Can be Trended

Trend files can include the following types of block variables:

D I/O block values

D ControlBlock continuous input values

D ControlBlock continuous output value

D ControlBlock discrete output values

Using Trending Screens

You can configure and display console trend files using the followingscreens:

D Trend File Setup Displays information about a trend file.

D Trend FileConfiguration

Allows configuration of a trend file.

D Trend GroupConfiguration

Allows configuration of a trend group.

D Trend Group Displays graphic trend information about theblock variables in a trend group.

D Trend GroupMenu

Displays titles of all configured console trendgroups and the variables within each, with amaximum of 400 groups allowed.

CC: 5-1-5


Enabling and Disabling Trending

You must enable trending for trend data to be stored on the consolehard disk. You must disable trending to perform operations such asconfiguring trend files. When you disable trending, data is stored in theconsole buffer memory but not on the console disk.

- To enable or disable trending from the Trend File Setup screen:

1. Cursor to the “Trend Status” field.

2. Select Enable or Disable.

3. Press [NEXT OPTION], then [ENTER].

- To enable trending from the command line, type:

ET [ENTER]

- To disable trending from the command line, type:

DT [ENTER]

Trending Condition upon Console Restart

If the console restarts, then the initial trending enabled/disabledcondition after restart depends on the trending condition when theconsole configuration was saved.

If the console configuration was saved with trending enabled, and if theconsole restarts, then trending is initially enabled after restart. If theconsole configuration was saved with trending disabled, and if theconsole restarts, then trending is initially disabled after restart.

CC: 5-1-6


CC: 5-2-1

RS3: Trending Configuring Trend Files

Section 2:Configuring Trend Files

This section describes how to set up and configure trend files. Becausetrend files share a finite amount of console disk space, someconsiderations should be made when configuring trend files. For moreinformation about trending restrictions, see Section 1 of this chapter.

CC: 5-2-2


The Trend File Setup Screen

The Trend File Setup screen displays information about the trend filesat a console. Figure 5.2.1 shows the Trend File Setup screen.Table 5.2.1 describes the fields on the screen.

- To call up the Trend File Setup screen, type:

TFS [ENTER]

TREND FILE SETUP 28-Jul-96 16:13:50

Trend Volume:>CC26 Trend Status:�Enabled History Volume:>CC26

--> Trend Overflow Warning uses file no. �5 at �4 hr before full.

Variables DiskWarning File No. Freq. Data Type Duration Max Used Used Status

0 1 sec sample 1 min 10 6 0%1 1 sec average 5 hrs 10 8 3% Good2 10 sec average 1 day 25 23 3% Good3 30 sec average 1 day 35 20 2% Good4 1 min average 1 day 30 25 1% Good

--> 5 1 min average 7 days 50 38 7% Good6 1 sec sample 1 min 0 0 0% Good7 1 sec sample 1 min 0 0 0% Good8 1 sec sample 1 min 0 0 0% Good9 1 sec sample 1 min 0 0 0% Good

�Reset Trending (press ENTER) Total :150 20%Operator Configurable File �0 Maximum : 200 100%

CONFIG 1

The trending function can be enabled and disabled inthe “Trend Status” field.

To call up a Trend File Configuration screen, cursorto the file number and press [SELECT].

File Number Zero (0) is notwritten to disk; it is used forvisual display only.

Figure 5.2.1. Trend File Setup Screen

CC: 5-2-3


Table 5.2.1. Trend File Setup Screen Fields


Data Type

Type of data to be trended:“average”= average of values is used for

trending.

“sample” = actual value is used for trending.

Display only

Disk Used

Percentage of disk space (1--100%) used by thetrend file. The percentage is based on the diskconfiguration, the frequency, the duration, andthe maximum number of variables.

Display only

DurationLength of time the data is stored on the disk ifthe “Variables Max” field matches the “VariablesUsed” file.

Display only

File No.

Number of the trend file.NOTE: Trend File 0 is not written to disk. Itstores real-time data only, and no history data isavailable.NOTE: Trend file 0 is a trend file in RAM only. Itis not saved on disk. With trend file 0,there is nocontrol over time duration; frequency (60 databits) controls duration. For example, if thefrequency is every minute, the duration is onehour. Your sample rate is 60.

Display only

Freq. Time between trend data values. Display only

History Volume:Volume name of the disk from which trend datamay be recalled for display. Under normaloperation, this is the same as the Trend Volume.

Up to 10 alphanumericcharacters

Maximum: Maximum number of variables allowed and thetotal percentage of available disk space. Display only

Operator ConfigurableFile

One trend file that can have tags configured bythe operator. A value of 0 indicates that no trendfiles can be configured by the operator.

0 to 9

Reset TrendingAllows initialization of configured trend data.Trending must be reset when the console isreloaded.

[ENTER]

Status

Status of the trend file:“Error”= indicates that the file structure

(“Duration”, “Frequency”, and“Variables Max” fields) does not matchthe structure of the file currently on thedisk.

“Good”= indicates that the file is present on thedisk.

Display only


CC: 5-2-4


Table 5.2.1. Trend File Setup Screen Fields (continued)

Field EntriesDescription

Total:

Sum of variables in the “Variables Max” field forall four files, and the total percentage of diskspace used by all files based on “Variables Max”field.

Display only

Trend OverflowWarning

Two fields used to provide a warning that disktrend space is low. The “Trend OverflowWarning” message is generated when the trendfile specified in the “file no.” field is within thetime period specified in the “at” field of being full.

If the file is not backed up and the disk becomesfull, data will be overwritten. For moreinformation, see Section 4 of this chapter.

file no. � 1 to 9

at � 1--999 m (mins)1--999 h (hrs)1--999 d (days)

Trend Status: Status of the trending function on that console. Disabled,Enabled

Trend Volume: Volume name of the disk on which trend data isbeing recorded.

Up to 10 alphanumericcharacters

Variables Max Maximum number of variables that can beconfigured for the file. Display only

Variables Used Number of variables currently configured for thefile. Display only

CC: 5-2-5


Configuring a Trend File

Trend files are configured on the Trend File Configuration screen. Up to80 block variables can be configured for a trend file. Up to 10 trend filescan be configured on a console.

Figure 5.2.2 shows a Trend File Configuration screen. Table 5.2.2describes the fields on the Trend File Configuration screen.- To call up a Trend File Configuration screen, type:

TFC [file number] [ENTER]- To page through the Trend File Configuration screens:

D Press [PAGE AHEAD] and [PAGE BACK].

TREND FILE CONFIGURATION 27-Jul-96 10:16:47

Variables DiskFile No. Frequency Data Type Duration Max Used Used

>1 >5 secs >sample >5 days >10 4 7 %

Tag Descriptor

1 >STACK 1 SENSOR A Level

2 >STACK 1 VALVE A Valve

3 >STACK 1 VCC-A Valve controller

4 >STACK 1 FCC-A Flow

5 >

6 >

7 >* MORE *

FULL CONFIG 1

A non-zero value must be entered in thisfield in order to configure trend variables.

- To call up a ControlBlock Faceplate screen or an I/O Block Configuration screen:D Cursor to the variable and press [SELECT].

Figure 5.2.2. Trend File Configuration Screen

CC: 5-2-6


Table 5.2.2. Trend File Configuration Screens


Data Type

Displays the average or sample data type to betrended.

“Average” indicates a rolling average taken everysecond. The result is sent to the console at the timespecified in the “Frequency” field. For example, if thefrequency is 5 seconds, an average of trending data istaken once a second for 5 seconds. The compositeresult is sent to the console from the ControllerProcessor.

“Sample” indicates one sample of data. For example,if the frequency is 43 seconds, one sample of trendingis taken every 43 seconds. The result is sent to theconsole from the Controller Processor.

average, sample

Descriptor The descriptor for the block from which the variable isobtained. Display only

Disk Used Percentage of disk space used by the file based onthe maximum number of variables. Display only

Duration*

Length of time data is stored on the disk. Thespecified duration is accurate only if the “VariablesMax” field matches the “Variables Used” field. Forexample, if the “Duration” is 1 hour, the “VariablesMax” field is 10, and the “Variables Used” field is 1,then the duration will actually be10 hours.

1--999 m,h,d(minutes, hours, days)

File No. Number of the trend file. 0--9

Frequency* Sampling time between data.1--999 s (seconds)1--59 m (minutes)

1 h (hour)

Tag Tag or address of the block variable to be trended. Any existing tag oraddress

Variables Max*Maximum number of variables to be stored in the file.NOTE: You must enter a non-zero number in this fieldin order to enter information in the “Tag” field.

0--80

Variables Used Number of variables currently configured for the file. Display only

* This entry is dependent on the disk space available at the time of entry.

CC: 5-2-7


Determining When and How Often Data is Stored(Frequency and Duration Fields)

You configure the sampling frequency and the length of time that data isto be saved individually for each trend file on a Trend File Configurationscreen. Sampling frequency is designated in the “Frequency” field. Thelength of time data is to be saved is designated in the “Duration” field.

The combination of “Frequency” and “Duration” field values for the trendfiles determine the total number of trend values that are configured tobe stored on the console. You must must ensure that enough diskspace has been configured for these trend values. For more informationon configuring disk space, see DT:3.

Figure 5.2.3 shows the Trend File Configuration screen with the“Frequency” and “Duration” fields.

TREND FILE CONFIGURATION 27-Jul-96 10:16:47

Variables DiskFile No. Frequency Data Type Duration Max Used Used

>1 >5 secs >sample >5 days >10 4 7 %

Tag Descriptor

1 >STACK 1 SENSOR A Level

2 >STACK 1 VALVE A Valve

3 >STACK 1 VCC-A Valve controller

4 >STACK 1 FCC-A Flow

5 >

6 >

7 >* MORE *

FULL CONFIG 1

“Frequency” determines how often a data sample is taken.“Duration” determines how often data is saved. In thisexample, data will be averaged every 30 seconds for 1 day.

Figure 5.2.3. Trend File Configuration Screen with Frequency and Duration Fields

CC: 5-2-8


CC: 5-3-1

RS3: Trending Configuring Trend Groups

Section 3:Configuring Trend Groups

A trend group contains up to four block variables that have beenconfigured in trend files. This section describes how to configure a trendgroup and a trend group display in order to view trending data.

The Trend Group Configuration

Each trend group is configured on a Trend Group Configuration screen.Up to 400 trend groups can be configured for one MTCC.

Figure 5.3.1 shows the Trend Group Configuration screen. Table 5.3.1describes the fields on the Trend Group Configuration screen.

- To call up the Trend Group Configuration screen:

D Type TGC [group number] [ENTER]

or

D Press [EXCH] while viewing a Trend Group screen.

CC: 5-3-2


TREND GROUP CONFIGURATION 28-Jul-96 16:13:50

Trend Group Number >4

Group Description >No. 3 Boiler Drum

Tag Descriptor Node File Freq. Type State

> LC-204/PV Drum Level >32 >3 30 secs average Good

> FC-205/PV FW Flow >4 >3 1 sec average Good

> PI-204/PV Drum Press >* >3 5 secs average Good

> FI-210/PV Steam Flow >2 >3 1 sec average Good

Data Pts>240 Time Scale>1 >MinutesVertical Graph Scaling (default)

Trend number >1 Min >0. % Max >100. %

CONFIG 1

- To call up a Trend Group Configuration screenfor another group:

D Change the number in this field and press[ENTER] or press [PAGE AHEAD] or [PAGEBACK].

- To add a variable to a tag group:1. Cursor to the “Tag” field.

2. Type in the tag or address of the variable,and press [ENTER].

- To access a ControlBlock Faceplatescreen:

D Cursor to a selected tag and press[SELECT].

Fields that determine theengineering units scaling of thegraph on the Trend Group screen.

“Data Pts” field is displayed on consoleswith pixel graphics.

Figure 5.3.1. Trend Group Configuration Screen

CC: 5-3-3


Table 5.3.1. Trend Group Configuration Screen Fields


The current status of the variable or file. The status conditionsinclude:

Bad Kind= Input block variable has been changed sinceoriginally listed in the file. This conditionsometimes can be cleared by re-entering the tagor address.

Block Cfg= Block not found.

Good= Data is available for display

Currently Initial = This message may appear prior to “Good” toindicate that the first piece of data is beingreceived.

Display Only

New Trend = Variable was just added to the file and no datahas been received yet.

No Data = Communication error just occurred affecting thetransfer of trend data.

No Room= Limit of 1856 bytes for the Controller Processorhas been reached.

File Cfg= The variable is not configured in the specified file.

No Node= Node not found.

Node Cfg= The variable is not configured on the specifiednode.

Data Pts Data points being displayed. Trend Group screen defaults to thisentry. 60, 120, 240, 480

Descriptor Descriptor for the block from which the variable is obtained. Display only

File Trend file number where the variable trend data is stored. 0--9

Freq. Sampling frequency from the “Frequency” field on the Trend FileConfiguration screen Display only

GroupDescription User-assigned display title. Maximum of 20

characters

Node

Node where the trend file containing variable trend data exists. Aconsole can display trend data stored at any console on thePeerWay. An asterisk in this field indicates that the default diskdrive is searched for the trend data.

2--992(even numbers

only)

Tag Tag or address of a block variable that is configured in a trend file.Up to 16

alphanumericcharacters


CC: 5-3-4


Table 5.3.1. Trend Group Configuration Screen Fields (continued)

Field EntriesDescription

Time Scale Desired time scale of the graph. Trend Group screen defaults tothis entry.

1--99, Minutes,Hours, or 366 Days

Trend GroupNumber Number of the trend group being configured. 1--400

Type Trend data type from the “Data Type” field on the Trend FileConfiguration screen Display only

Default engineering units scale of the graph on a Trend Groupscreen. The default engineering units are displayed each time youcall up the Trend Group screen. Vertical Graph Scaling fieldsconsist of the “Trend Number”, “Min”, and “Max” fields:

Trend number: 1 4

VerticalGraphScaling

TrendNumber=

Number of the block variable that has itsengineering units displayed on the left side of thegraph.

Trend number: 1--4Minimum:0--999999

Maximum:Scaling

Min= Minimum percent engineering units valuedisplayed on the right side of the graph.

Maximum:0--999999

Max= Maximum percent engineering units valuedisplayed on the right side of the graph.

CC: 5-3-5


Trend Group Displays

The Trend Group screen displays graphic trend information about theblock variables in a trend group. The Trend Group screen displays 60samples of data on a console with character graphics and 60 to 480samples of data on a console with pixel graphics. The most recentinformation is on the right side of the graph and the oldest information ison the left side of the graph. Figure 5.3.2 shows an example of a TrendGroup screen.

- To call up the Trend Group Screen

D Type TG [group number] [ENTER]

or

D Press [EXCH] while viewing a Trend Group Configuration screen.

CC: 5-3-6


Using the Slidewire

The cursor can be moved into the graph on the Trend Group screenand used as a slidewire. Figure 5.3.2 shows the use of the slidewire.The variable values at the slidewire location are shown at the bottom ofthe screen. To get the most recent values to appear again, move theslidewire to the far right of the graph.

NOTE: The accuracy of these values is approximately 0.5% from --12%to 112% of the range.

NOTE: On consoles with pixel graphics, move the cursor vertically tomake fine adjustments. When the cursor is at the top half of the screen,the reading will be to the right of the cursor. When the cursor is at thebottom half of the screen, the reading will be to the left of the cursor.

16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current>STACK 1 FCC-A

Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-Jan-89Data Pts >240 Value at


CONFIG 1


>200.00

100.00

KLb/Hr

>0.00

>100.

50.

%

>0.

Slidewire

Variable values“Data Pts” field is displayed on consoleswith pixel graphics.

Figure 5.3.2. Trend Group Screen with Slidewire

CC: 5-3-7


Trend Group Scaling

The graph on the Trend Group screen has two adjustable scaling areas.The scaling area to the right of the graph shows scaling as a percent ofthe engineering units. For example, a value of 100 represents the “EngMax” value of a variable. A value of 0 represents the “Eng Min” value.

The left side of the graph shows the engineering units of one of thetrend group variables. The engineering units are associated with thevalues on the right side of the graph.

The default scaling values on the right side of the graph are determinedby the “Min” and “Max” fields on the Trend Group Configuration screen.The default variable engineering units displayed on the left side of thegraph are the units of the variable defined in the “Trend Number” fieldon the Trend Group Configuration screen.

Figure 5.3.3 shows the Trend Group screen with fields used for scaling.

>100.

50.

%

>0.

>25.00

00.00

Inches

>-25.00


16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current>STACK 1 DPR-A

Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-June-96Data Pts >240 Value at


CONFIG 1

- To change the variable that has its units displayed onthe left side of the graph:

D Press [NEXT OPTION] to scroll through tags until theappropriate tag appears., then [ENTER].

Variable tag/addressof current scaling

Engineering units scalingof the trend variable

Percent scaling of thetrend variable

Figure 5.3.3. Trend Group Screen with Scaling Fields

CC: 5-3-8


Viewing Trend Data

The graph on the Trend Group screen displays trend data. The TrendGroup Display screen defaults to the current trend group display.

Figure 5.3.4 shows the fields of the Trend Group screen that are usedto configure the graph on a Trend Group screen.

16:04:54 16:06:34 16:08:14 16:09:54 16:11:34 Current>STACK 1 DPR-A

Time Scale >10 >Minutes >Start Time > 16:13:14 > 28-June-96Data Pts >240 Value at

Tag Descriptor 28-Jan-86 16:08:00 Units Eng. Min Eng. MaxStack 1 SENSOR A Drum Level 0.00 Inches -25.00 25.00STACK 1 FCC-A Flow 160.00 KLb/Hr 0.00 200.00STACK 1 DPR-A Drum Press 200.0 PSIG 0.0 600.0STACK 1 FCC-B Steam Flow *OFF* KLb/Hr 0.00 200.00

CONFIG 1


>22.00

00.00

Inches

>-25.00

>100.

50.

%

>0.

Data Pts= Number of data points being displayed (Format: 60, 120, 240, 480).Time Scale= Desired time scale of the graph ( Format: 1--366, Minutes, Hours, or Days).

Start /End = Time and date of the newest or oldest data on the graph. If a time is entered in thisfield, the field displays a “History” status and the graph does not update. (Format: Timeis HH:MM:SS; Date is DD--MM--YY)

“Start” Time is shown on the right side of the graph and all data viewed is older than the start time.“End” Time is shown on the left side of the graph and all data viewed is newer than the end time.

Current/History statusCurrent indicates that the graph isshowing the most current data andthat the graph is continually updating.History indicates that the graph isshowing data from a past time andthat the graph is not updating.

- To turn a trend display line on or off:D Cursor to the tag of the trended link

and press [ENTER]. While the trendis turned off, “*OFF*” appears in the“Value at” field.

Figure 5.3.4. Trend Group Screen with Fields that Determine Data Points and Time

CC: 5-3-9


How Often Trend Group Displays Update

In order to reduce request message load on controllers, trend groupsuse an update algorithm to determine how often to refresh the display.Trend groups determine update time as a function of the time scale andthe number of trend data points.

Figure 5.3.5 shows the update algorithm that trending uses to calculatethe update time. You can use this algorithm to assess the impact of“Time Scale” and data points on update time. For additional informationabout the Trend Group Display, see page 5-3-5.

NOTE: The formula that is shown in Figure 5.3.5 is used by the displayonly and does not affect how the data is stored on the disk.

If: Time Scale % Data Points = 0

or

If: Time Scale % Data Points = Fraction of a Second

Where Data Points and n are:Data Points n

480 8

240 4120 2

60 1

NOTE:

D The update time is in the units of time specified in the “Time Scale” field: hours or minutes.D The operator % stands for the mathematical function modulus.

Update Time= Time Scale

Data Points

Update Time= Time Scale

Data Points ∙ n

Figure 5.3.5. Update Time Algorithm

CC: 5-3-10


The trend group displays can update only in even seconds. If theupdate time, as computed by the above formula (Time Scale % DataPoints), contains a fraction of a second, the trend group will multiply theresult by the “n” (see formula) to round off the update time to an evensecond.

D In Figure 5.3.6, 480 data points and a time scale of 40 minutesresult in an update time of 5 seconds.

NOTE: The trend data requires 5 seconds to update. In this case,

Update Time= Time ScaleData Points

40 minutes480

= 5 seconds

Figure 5.3.6. Update Time in Even Seconds

D In Figure 5.3.7, 480 data points and a time scale of 41 minutesresult in an update time of 5.125 seconds. Because the updatetime contains a fraction of a second (0.125), the display mustwait 41 seconds (that is a multiple of eight 5.125 update times)before it can update.

NOTE: The trend data requires 41 seconds (5.125 * 8) to update. In this case,

Update Time= Time ScaleData Points ∙ n

41 minutes480

= 5.125 seconds

Figure 5.3.7. Update Time in Fractions of Seconds

CC: 5-4-1

RS3: Trending Archive Trend Data

Section 4:Archive Trend Data

This section describes how to save trend files, how to view historicaltrend data, and how to reload previously configured trend files fromtape.

The Disk and Tape Functions Manual gives instructions for saving atrend file to tape or disk, reloading the file from tape or disk, andrestoring a tape.

NOTE: When you save a trend file, you should also save theconsole trend file configuration and trend group configurations.When you restore the trend data, these configurations should alsobe restored. Otherwise, you will not be able to view the restoredtrend data.

CC: 5-4-2


How a Backup Trend File is Saved

When a trf# file becomes backup trend file trf#b, an alarm message isdisplayed notifying the user to save the file. The backup trend file canbe saved to tape or disk within the time that is shown in the “Duration”field on the Trend File Configuration screen. If the file is not saved, thecontents are deleted and the data is lost.

Figure 5.4.1 shows the process for saving a trend file to tape or disk.

Disk Activity Screen

trf#b file

trf# file

When the trf# file is full, the file isrenamed trf#b, a backup file. Thebackup trend file can be saved to tape,floppy disk, or another hard disk.

A backup trend file is saved to disk ortape on a Disk Activity screen. To avoidduplicate file names, rename a filewhen it is saved to tape or disk. Thefirst four characters of the trend file,trf#, must remain the same. Rename byadding one or more characters to thistrend file name.

Figure 5.4.1. The Process of Saving a Trend File

CC: 5-4-3


Restoring and Reading Trend Archive Data

Restoring and reading trend archive data can be performed by readingbackup trend file tapes, or by directly reading the file over the PeerWay.

Restoring and Reading Trend Archive Data from Tape

Figure 5.4.2 shows the process of restoring a trend file tape andreading the trend data on a Trend Group screen.

Time Scale >10 >Minutes Start Time>22:48:14 >05-Jan-89

- To restore a trend file tape:1. Load the archive tape to the

console disk.

TAPE DIRECTORYSCREEN

The Tape Directory screen lists allfiles that are on the tape.

2. Restore the files using the DiskActivity screen.

DISK ACTIVITYSCREEN

3. Call up the Trend Groupscreen. Specify the timeof the trending data inthe “Start Time/EndTime” field. The archivetrend data is displayedon the trend graph.

Figure 5.4.2. Restoring and Reading a Trend File

CC: 5-4-4


CC: 5-5-1

RS3: Trending Hints for Configuring Trending

Section 5:Hints for Configuring Trending

This section discusses some problems you might have whenconfiguring trending.


- Why doesn’t the block tag on a Trend Group display show thealarm condition of the block?

The block tag only shows the alarm condition of the trendedvariable.

- On the Trend Group Configuration screen, the “Currently” fielddisplays Bad Kind for a variable.

You may be able to clear the condition by reentering the variable inthe “Tag” field.

Copying Trend Files

If you copy a trend file (using the Disk Activity screen), the copy file isnot functional until you enable and disable it. The processor willcontinue to write to the original file until you enable and disable the newfile.

Determining Trend Group Update Time

In order to reduce excess data request messages to controllers, trendgroups use update time to determine how often to update trend data.The trend group computes update time as a function of time scale andthe number of trend data points. For more information on how updatetime works, see “How Often Trend Group Displays Update” onpage 5-3-9.

CC: 5-5-2

RS3: Trending Hints for Configuring Trending

ContentsRS3: Alarm Management


Chapter 6:Alarm Management

Section 1: Managing the Number of Alarm Messages on the PeerWay 6-1-1. .

Configuring Which Nodes Are Sent Alarms from a ControlFile or Console 6-1-2. . . . .Using CAB to Reduce Message Load 6-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inhibiting Alarms from Generating on the PeerWay 6-1-7. . . . . . . . . . . . . . . . . . . . . . . .Using ControlBlock Logic 6-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Using the ControlFile Status Screen 6-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Effects of Inhibiting Alarms 6-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: How Alarms Get Stored in Console RAM 6-2-1. . . . . . . . . . . . . . . . . . .

Section 3: Separating and Sorting Alarms at a Console 6-3-1. . . . . . . . . . . . . . . .

Alarm Types 6-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Areas 6-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Disabling and Enabling an Alarm Area 6-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Disabling an Alarm Area 6-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Enabling an Alarm Area 6-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Suppression 6-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Suppressing an Alarm 6-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Unsuppressing an Alarm 6-3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Alarm List and Event List Properties 6-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . .The Alarm List Configuration Screen 6-3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RS3 Events 6-3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .User-defined Events 6-3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring the Event List 6-3-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Alarm History 6-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Log Display Configurations 6-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Displaying Information from the Alarm Log 6-4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Disabling and Enabling the Alarm Log 6-4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 5: Configuration and Display Topics 6-5-1. . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Configuration Screen 6-5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Configuration Screen—Automatic Alarm Deletion 6-5-8. . . . . . . . . . . . . . . . .

Alarm Regeneration 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Purpose 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .When Do Alarms Regenerate 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: ii

RS3: Alarm Management Contents

How Consoles Regenerate Alarms 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Restrictions 6-5-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Priority 6-5-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Type Priority 6-5-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Priority Numbers 6-5-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Display Mode 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Banner Mode 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Summary Mode 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Determining the Alarm Display Mode 6-5-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 6: Alarm Animation 6-6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Tags 6-6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Tags on Trend Group Displays 6-6-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Block Variable Values 6-6-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Plant Units and Area Names 6-6-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Graphic Alarm Objects and Icon Objects 6-6-37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Alarm Message Source Descriptions 6-6-48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 7: Hints for Alarm Management 6-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Problems 6-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuration Tips 6-7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iii


List of Figures

Figure Page

6.1.1 Configure Alarm Broadcast Screen 6-1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.2 Comparison of Message Traffic 6-1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.3 Effect of Partitioning into Logical Sections 6-1-5. . . . . . . . . . . . . . . . . . . . . . . .

6.3.1 Area Name Configuration Screen 6-3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.2 Alarm List Configuration Screen 6-3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.3 Event List Configuration Screen 6-3-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4.1 Log Display Configuration Screen 6-4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4.2 Examples of Criteria Configurations 6-4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4.3 Using the Alarm Log Display Screen 6-4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5.1 Alarm Configuration Screen for the SMS 6-5-2. . . . . . . . . . . . . . . . . . . . . . . . .

6.5.2 Alarm Configuration Screen for the MTCC 6-5-3. . . . . . . . . . . . . . . . . . . . . . .

6.5.3 Automatic Alarm Deletion Screen 6-5-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5.4 Example of an Alarm Banner 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5.5 Example of an Alarm Summary 6-5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.1 Example Portion of an Animation Table 6-6-2. . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iv


List of Tables

Table Page

6.1.1 Comparison of Alarm Inhibiting Logic Step Functions 6-1-7. . . . . . . . . . . . . .

6.2.1 How Node Ownership and Plant Unit Ownership Work Togetherto Determine Alarm Storage 6-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.1 Alarm Type Lists 6-3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.2 Area Name Configuration Screen Fields 6-3-4. . . . . . . . . . . . . . . . . . . . . . . . .

6.3.3 Alarm List Configuration Screen Fields 6-3-10. . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.4 Reserved Event Numbers 6-3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.5 Event List Configuration Screen Fields 6-3-15. . . . . . . . . . . . . . . . . . . . . . . . . .

6.4.1 Log Display Configuration Screen Fields 6-4-3. . . . . . . . . . . . . . . . . . . . . . . .

6.4.2 Alarm Log Display Screen Fields 6-4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5.1 Alarm Configuration Screen Fields 6-5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5.2 Alarm Configuration Screen----Automatic Alarm Deletion Fields 6-5-9. . . . .

6.6.1 Tag Animation Hardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%ISA 6-6-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.2 Tag Animation Hardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%ISA 6-6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.3 Tag Animation Hardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%ISA 6-6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.4 Tag Animation Hardware Alarms Have More Prioritythan%SystemUnacked, Cleared Alarm%ISA 6-6-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.5 Tag Animation Hardware Alarms Have More Priority than%Diskor NoneUnacked, Cleared Alarm%ISA 6-6-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.6 Tag Animation Hardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%RMT or Color 6-6-9. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.7 Tag Animation Hardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%RMT or Color 6-6-10. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.8 Tag Animation Hardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%RMT or Color 6-6-11. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.9 Tag Animation Hardware Alarms Have More Prioritythan%SystemUnacked, Cleared Alarm%RMT or Color 6-6-12. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.10 Tag Animation Hardware Alarms Have More Priority than%Diskor NoneUnacked, Cleared Alarm%RMT or Color 6-6-13. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.11 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%ISA 6-6-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: v


6.6.12 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%ISA 6-6-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.13 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%ISA 6-6-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.14 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%SystemUnacked, Cleared Alarm%ISA 6-6-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.15 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%Disk or NoneUnacked, Cleared Alarm%ISA 6-6-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.16 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%RMT or Color 6-6-21. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.17 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%RMT or Color 6-6-22. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.18 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%RMT or Color 6-6-23. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.19 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%SystemUnacked, Cleared Alarm%RMT or Color 6-6-24. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.20 Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than%Disk or NoneUnacked, Cleared Alarm%RMT or Color 6-6-25. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.21 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%ISA 6-6-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.22 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%ISA 6-6-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.23 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%ISA 6-6-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.24 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%SystemUnacked, Cleared Alarm%ISA 6-6-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.25 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%Disk or NoneUnacked, Cleared Alarm%ISA 6-6-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.26 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%RMT or Color 6-6-32. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.27 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%RMT or Color 6-6-33. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.28 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%RMT or Color 6-6-34. . . . . . . . . . . . . . . . . . . . . . . . .

CC: vi


6.6.29 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%SystemUnacked, Cleared Alarm%RMT or Color 6-6-35. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.30 Plant Unit and Area Name AnimationHardware Alarms Have More Priority than%Disk or NoneUnacked, Cleared Alarm%RMT or Color 6-6-36. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.31 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%ISA 6-6-38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.32 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%ISA 6-6-39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.33 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%ISA 6-6-40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.34 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%SystemUnacked, Cleared Alarm%ISA 6-6-41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.35 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%Disk or NoneUnacked, Cleared Alarm%ISA 6-6-42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6.36 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%CritUnacked, Cleared Alarm%RMT or Color 6-6-43. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.37 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%AdvUnacked, Cleared Alarm%RMT or Color 6-6-44. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.38 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%BatchUnacked, Cleared Alarm%RMT or Color 6-6-45. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.39 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%SystemUnacked, Cleared Alarm%RMT or Color 6-6-46. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.40 Alarm and Icon Object AnimationHardware Alarms Have More Priority than%Disk or NoneUnacked, Cleared Alarm%RMT or Color 6-6-47. . . . . . . . . . . . . . . . . . . . . . . . .

6.6.41 Alarm Message Source Description Animation 6-6-48. . . . . . . . . . . . . . . . . . . .

CC: 6-1-1

RS3: Alarm Management Managing the Number of Alarm Messages on the PeerWay

Section 1:Managing the Number of Alarm Messages on thePeerWay

Normally, an alarm condition generates an alarm message on thePeerWay for each node in the system. You can reduce the number ofalarm messages on the PeerWay in the following ways:

D If you have multiple PeerWays connected, or if the performanceof the PeerWay has declined, you may want to reduce thenumber of nodes that get ControlFile and console alarmmessages. You can do this with the Configure Alarm Broadcastscreens.

D If you do not want alarms from a ControlBlock to generate undercertain conditions, you can inhibit alarms from generating withControlBlock logic.

D If you do not want alarms from a Controller Processor togenerate under certain conditions, you can automatically inhibitalarms from generating with ControlBlock logic or manually inhibitalarms from generating with the ControlFile Status screen.

CC: 6-1-2


Configuring Which Nodes Are Sent Alarms from aControlFile or Console

If you have multiple PeerWays connected together, or if PeerWayperformance has declined, you may want to limit the amount ofPeerWay traffic by using the Configure Alarm Broadcast feature.Configure Alarm Broadcast (CAB) is used to reduce unnecessary alarmmessages and alarm acknowledge traffic on the PeerWay.

Normally, if an alarm occurs or is acknowledged in a ControlFile orConsole, an alarm message is sent to every existing node on allconnected PeerWays. However, you can use the Configure AlarmBroadcast screens to specify which nodes are sent alarms from aspecific ControlFile or console (see Figure 6.1.1). Each ControlFile andconsole has its own alarm broadcast configuration.

Configure Alarm Broadcast screens are used to filter the sending ofalarms, while the Plant Status and Plant Unit screens are used forreceiving them. The CAB for consoles is saved in the Alarm/Eventconfiguration portion of the Console Configuration file. The CAB for oneor more ControlFiles can be saved to a Plant Config file (type CAB). Tosave and restore the Alarm Broadcast Configurations, see the Disk andTape Functions Manual.

NOTE: When you configure which nodes are sent alarms with CAB,make sure that you select the node that you are configuring. Otherwise,you will not receive alarm messages generated by that node.

CC: 6-1-3


Node� 116 Configure Alarm Broadcast 23-Jul-96 11:47:12

1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 2412 18 34 50 66 82 98 114 130 146 162 178 194 210 226 2423 19 35 51 67 83 99 115 131 147 163 179 195 211 227 2434 20 36 52 68 84 100 116 132 148 164 180 196 212 228 2445 21 37 53 69 85 101 117 133 149 165 181 197 213 229 2456 22 38 54 70 86 102 118 134 150 166 182 198 214 230 2467 23 39 55 71 87 103 119 135 151 167 183 199 215 231 2478 24 40 56 72 88 104 120 136 152 168 184 200 216 232 2489 25 41 57 73 89 105 121 137 153 169 185 201 217 233 24910 26 42 58 74 90 106 122 138 154 170 186 202 218 234 25011 27 43 59 75 91 107 123 139 155 171 187 203 219 235 25112 28 44 60 76 92 108 124 140 156 172 188 204 220 236 25213 29 45 61 77 93 109 125 141 157 173 189 205 221 237 25314 30 46 62 78 94 110 126 142 158 174 190 206 222 238 25415 31 47 63 79 95 111 127 143 159 175 191 207 223 239 25516 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256

Set range �3,6 Clear range � Local Pway Initialize

CONFIG 4

Nodes that are sentalarms are backlighted.

- To call up:D C A B (node #) [ENTER]

at the command line

- To access other screens:D [PAGE AHEAD] and [PAGE BACK]

to see other ControlFile nodenumbers.

- To select or deselect a single node:D Cursor to the node number and press

[ENTER].

- To select all the nodes on the localPeerWay

D Cursor to the “Local Pway” field and press[ENTER].

Uninitialize indicates that alarmsare sent to all active nodes.

Initialize indicates that alarms areonly sent to the selected nodes.This field is not used on the CABscreen for consoles.

- To deselect a range of nodes:D Cursor to the “Clear range” field, type a

range of numbers separated by acomma (for example “3,6”), then press[ENTER].

- To select a range of nodes:D Cursor to the ”Set range” field, type a range

of numbers separated by a comma (forexample “3,6”), then press [ENTER].

Each ControlFile and consolemust have its own CABscreen configured.

Figure 6.1.1. Configure Alarm Broadcast Screen

CC: 6-1-4


Using CAB to Reduce Message Load

Continuous alarms or bursts of alarms (which often peak at start-up orshutdown) can be caused by too many unnecessary, redundant alarmsand alarm acknowledge messages traveling between too many nodes.Redundant alarms and alarm acknowledge messages can substantiallyslow down responses and obscure more significant events, especially inlarge systems.

Figure 6.1.2 shows an example of the decrease in message traffic if onedestination is removed from the coordinator processor using the CABscreen, and only one console is allowed to acknowledge the alarms.

CoordinatorProcessor

Console 1

Console 2

Console 3


Console 1(Acking)

Console 2

Console 3(Non-acking)

3 consoles acknowledge alarm12 message sets created


1 console acknowledges alarm5 message sets created


Figure 6.1.2. Comparison of Message Traffic

As a configuror, you must reduce the number of unnecessary messagesin order to optimize the performance of your system. To minimize waste,you are strongly encouraged to use these techniques:

D Reduce the amount of alarm message traffic that travels to otherPeerways across the HIA.

D In large systems, use one console to receive alarms from otherPeerways, but not to receive alarm message traffic from its ownPeerway. Use other consoles on the Peerway to handle thisconsole’s Peerway alarm message traffic.

CC: 6-1-5


D As your plant grows, divide it into logical sections correspondingto one to three ControlFiles. Have one section report to one tothree consoles, only one of which acknowledges alarms, to avoidduplicate acknowledge messages for the same alarm. Examplesof logical sections could be the power area of a plant, a storagearea, or an area where a portion of a process takes place.

Use the CAB screen to ensure that alarm message traffic is limited onlyto nodes in that logical section. The ideal scheme would have minimalmessage traffic across section boundaries. Figure 6.1.3 shows anexample of message traffic before and after partitioning using the CABscreen.

Each alarm at a CP creates message sets = 4 to 7 � number of alarmsEach alarm ack at a console creates message sets = 3 � number of console acks

NorthSection

CP CP CP CP

Console Console Console Console

CP CP CP CP

Console Console Console Console

SouthSection

Each alarm at a CP creates message sets = 2 to 3 � number of alarmsEach alarm ack at a console creates message sets = 1 � number of console acks

blocklinks

Figure 6.1.3. Effect of Partitioning into Logical Sections

CC: 6-1-6


The CAB screen allows you to reduce the number of redundantmessages by allowing you to limit the number of nodes that receivealarms and alarm acknowledge messages from your console. The CABscreen affects alarms, events, and alarm acknowledge messagesbefore messages are sent on the Peerway, substantially reducingPeerway, node, and HIA load.

The Plant Status and Plant Unit Configuration screens are not aseffective as using the CAB screen to limit message traffic, because theyonly filter out unwanted messages after they have already been sent.This means that the unwanted messages are sent and received, usingup Peerway resources, and then are discarded after the resources havealready been used.

You should not configure HIAs or coordinator processors asdestinations from the CAB screen, because these just discard receivedalarms and alarm acknowledge messages. (However, selectedcoordinator processors running Batch should be sent alarms for ontraps.) You should only configure a few consoles or logging nodes in thesame Peerway as console CAB destinations.

CC: 6-1-7


Inhibiting Alarms from Generating on the PeerWay

You can inhibit alarms from a ControlBlock and from a ControllerProcessor.

Using ControlBlock Logic

You can use ControlBlock logic to inhibit ControlBlock alarms andController Processor alarms from generating and being sent on thePeerWay. Table 6.1.1 compares the inhibit logic step functions. Formore information about these logic steps, see CB: 6.

Table 6.1.1. Comparison of Alarm Inhibiting Logic Step Functions

This logic stepfunction: Affects: And it lasts:

inhibit* ControlBlock alarms

Only as long as the function is executed.That is, alarms are inhibited only forthose evaluation cycles in which theinhibit function is executed.

inha and enba Alarms that originate in a ControllerProcessor

Until the opposite function is executed.That is, once a function is executed, thatcondition remains in effect until theopposite condition is executed.

* Does not work on MPCI controllers.

Using the ControlFile Status Screen

In addition, you can use the “Alarm Inhib” field on the ControlFile Statusscreen to inhibit Controller Processor alarms from generating and beingsent on the PeerWay.

Effects of Inhibiting Alarms

When a ControlBlock or Controller Processor is inhibited, the followingtasks occur:

D The ControlBlock or Controller Processor sends a clear messageon the PeerWay for each uncleared alarm.

D All alarms from the ControlBlock or Controller Processor areinhibited from generating and are not sent on the PeerWay.

CC: 6-1-8


CC: 6-2-1

RS3: Alarm Management How Alarms Get Stored in Console RAM

Section 2:How Alarms Get Stored in Console RAM

A console receives alarm messages from the PeerWay. The consolestores some of these alarms in RAM on the console OI Processor cardand discards the rest. The console determines whether or not to storean alarm based on the configured node ownership and plant unitownership at the console.

Table 6.2.1 describes how node ownership and plant unit ownershipwork together to determine alarm storage. For more information onnode ownership and plant unit ownership, see 2-1-31.

The “Total Entries” field on the Alarm List Configuration screen displaysthe number of alarm and event messages that can be stored in consoleRAM. For more information on the Alarm List Configuration screen, seeSection 3.

Table 6.2.1. How Node Ownership and Plant Unit Ownership Work Together toDetermine Alarm Storage

If: Then: Only if the console:

a block or batch task has anon-zero plant unit number,

the console stores alarms fromthe block or task, owns the plant unit number.

a block or batch task has a plantunit number of zero,

the console stores alarms fromthe block or task, owns the source node.

the source is not a block or batchtask,

the console stores alarms fromthe source, owns the source node.

CC: 6-2-2

RS3: Alarm Management How Alarms Get Stored in Console RAM

CC: 6-3-1

RS3: Alarm Management Separating and Sorting Alarms at a Console

Section 3:Separating and Sorting Alarms at a Console

Alarms that are stored in console RAM are separated and sorted in thefollowing ways. The following sorting methods are described in thissection:

D Alarms are automatically sorted by alarm type into alarm typelists.

D Alarms are also sorted by configurable alarm area into alarmarea lists. Alarm areas can be disabled.

D Alarms can be separated from the alarm type lists and alarmarea lists (suppressed).

In addition, this section describes how to configure alarm list and eventlist properties.

CC: 6-3-2


Alarm Types

Each alarm belongs to one and only one alarm type. All alarms storedat the console are automatically separated by alarm type into alarm typelists. The alarm types and alarm type lists are listed in Table 6.3.1.

The alarm type lists include all alarms stored at the console, except:

D Suppressed alarms

D Alarms from disabled alarm areas

Table 6.3.1. Alarm Type Lists

Alarm Type Alarm Lists

Advisory Process Alarms

Active Advisory Process Alarm ListCleared Advisory Process Alarm List

Active Process Alarm List*

Cleared Process Alarm List*

Batch AlarmsActive Batch Alarm ListCleared Batch Alarm List

Critical Process Alarms

Active Critical Process Alarm ListCleared Critical Process Alarm List

Active Process Alarm List*

Cleared Process Alarm List*

Disk Event Messages Disk Event List

Hardware AlarmsActive Hardware Alarm ListCleared Hardware Alarm List

System Status MessagesActive System Status Alarm ListCleared System Status Alarm List

* The Process Alarm lists are a combination of the Advisory Process and CriticalProcess alarm lists.

CC: 6-3-3


Alarm Areas

You can configure alarm areas. Alarm areas are helpful in groupingalarms from certain areas of the plant. Each alarm area is associatedwith one or more plant units. Alarms from the specified plant units aresorted into alarm area lists.

Plant units can belong to more than one alarm area. As a result, alarmscan reside in more than one alarm area list.

Alarm areas are configured on the Area Name Configuration screen(see Figure 6.3.1). Table 6.3.2 describes the fields on the screen.

AREA NAME CONFIGURATION 25-Jul-96 12:07:37

Area Name: Status: Graphic: +------------Unit Ranges-----------+>1�Boiler >Enable �Boiler1 �1-4,6,9-12 |

2�Area 2 >Enable � �1-10 |

3� > � � |

4� > � � |

5� > � � |

6� > � � |

7� > � � |

8� > � � |

9� > � � |

FULL CONFIG 3

- To call up:D A N C [ENTER] at the

command line

- To access other screens:D [PAGE AHEAD] and [PAGE BACK] and scroll

with trackball to call up other alarm areas

D [EXCH] on Unit Ranges field to showDescriptor field and number of alarms

D [SELECT] on Area Name entry to see areaalarm list

D [SELECT] on Graphic entry to see processgraphic

D [SELECT] on Unit Ranges field heading tosee Plant Unit Configuration

Figure 6.3.1. Area Name Configuration Screen

CC: 6-3-4


Table 6.3.2. Area Name Configuration Screen Fields

Field Description

> Enter the number of the next area name that you want displayed.

|

Indicates whether there are more units to be displayed. | indicates all theunits have been displayed. > indicates there are more units to the right. <indicates there are more units to the left. <> indicates there are more units inboth directions.

Area Name

Specifies the alarm area name. The area name can contain up to 12characters. Each console can contain up to 99 area names.

Area names are used throughout the PeerWays. When you enter an areaname, the console searches the PeerWays to see if the area name has beendefined on another console. If it has, the console brings the already-defined“Graphic” and “Unit Ranges” field entries to your console.

CAUTION: The information on the Area Name Configuration screen is part ofthe configuration of this console only. As a result, if you make changes to the“Graphic” or “Unit Ranges” fields of an area name, the changes are onlymade to the local console configuration. The changes are not propagated toother consoles. To make those changes at other consoles, you must go toeach console that contains that area name in node number order, deletethe area name, and reenter it.

Descriptor

Specifies a descriptor for the alarm area. The descriptor can contain up to 35characters. The far right of the display shows the number of alarms for thearea.

Pressing [EXCH] switches between displaying the “Unit Ranges” and“Descriptor” fields for the configuror.

Graphic

Specifies a process graphic on the local hard disk that is associated with anarea. The operator can cursor to the graphic name and press [SELECT] tocall up the graphic.

You can also call up the graphic with the commandA N G (area name) [ENTER].

Status

Specifies the status of the area (Enabled or Disabled).When you enter the area name, the area is enabled. The area must beenabled for the console to display area alarms. For information aboutdisabling and enabling alarm areas, see “Disabling and Enabling an AlarmArea” on page 6-3-5.

Unit Ranges

Specifies the plant units for the alarm area. You can enter single plant unitsand ranges of plant units.

If the console does not own the plant unit, the plant unit appears backlightedin the advisory alarm color.If the displayed list of plant units is longer than the available space, you canpress [NEXT OPTION] on this field to see the rest of the plant units.

Pressing [EXCH] switches between displaying the “Unit Ranges” and“Descriptor” fields for the configuror.

CC: 6-3-5


Disabling and Enabling an Alarm Area

If you do not want to see alarms from certain areas of the plant, you candisable a console alarm area. While the area is disabled, the followingconditions exist:

D The alarms from that area are not shown in the alarm type lists.

(If a plant unit is listed in more than one area on a console, thenall areas with that plant unit must be disabled for alarms from thatplant unit not to be shown in the alarm type lists.)

D You cannot use [PAGE AHEAD] and [PAGE BACK] to access thealarm lists for that area.

D If you call up the alarm area lists, a message states “DisabledArea List”.

The “Key Classes for area status” field on the Alarm Configurationscreen determines the key access level required to disable or enablealarm areas. For more information on the Alarm Configuration screen,see page 6-5-2.

Disabling an Alarm Area

NOTE: If you want to disable an area, the same area must be enabledin at least one other console.- To disable an alarm area from the Area Name Configuration

screen:1. Call up the Area Name Configuration screen

(press A N C [ENTER] from the command line).2. Cursor to the “Status” field for the desired area. Press

[NEXT OPTION] until “Disabled” appears. Press [ENTER].

- To disable an alarm area from the command line:D Press A D : (area name) [ENTER]

Enabling an Alarm Area

- To enable an alarm area from the Area Name Configurationscreen:1. Call up the Area Name Configuration screen

(press A N C [ENTER] from the command line).2. Cursor to the “Status” field for the desired area. Press

[NEXT OPTION] until “Enabled” appears. Press [ENTER].- To enable an alarm area from the command line:

D Press A E : (area name) [ENTER].

CC: 6-3-6


Alarm Suppression

You can suppress active block alarms at a console. You suppressalarms when there are a lot of alarms coming in. Suppression isdifferent from disabling. One reason you might disable alarms is if youdon’t want to know about them because they are in a part of the plantthat is not your concern.

Suppressed alarms characteristics

D When you suppress an active alarm from a block, all activealarms from that block that are of the specified alarm types aresuppressed.

D Suppressed alarms do not appear on alarm type lists or alarmarea lists.

D Suppressed alarms appear in active and cleared suppressedalarm lists.

D Suppressed alarms appear in a configured color.

D If an active suppressed alarm clears, the alarm goes into thecleared suppressed alarm list.

D If the console regenerates alarms, the suppressed alarm lists arenot rebuilt. Instead, regenerated alarms that were in thesuppressed alarm lists appear in the alarm type lists.

Unsuppressed alarm characteristics

D When you unsuppress an alarm, all active suppressed alarmsfrom that block are moved back to the alarm type lists. All clearedalarms from that block are deleted.

Which alarm types can be suppressedYou configure which alarm types can be suppressed with the“Suppressed Type” field on the Alarm Configuration screen. When yousuppress an active alarm from a block, all active alarms from that blockthat are of the specified alarm types are suppressed.

For example, if you configure “Suppressed Type�Hard,Adv,System”and suppress an alarm, then all active hardware, advisory, and systemstatus alarms from that block are suppressed. For more information onthe Alarm Configuration screen, see page 6-5-2.

Which key access level can suppress alarmsYou determine the key access level required to suppress alarms withthe “Key Class for suppress alarms” field on the Alarm Configurationscreen.

For more information on the Alarm Configuration screen, seepage 6-5-2.

CC: 6-3-7


Suppressing an Alarm

- To suppress an active alarm:

1. Call up an alarm list that contains the alarm that you want tosuppress.

2. Cursor to the alarm. Press S.

Unsuppressing an Alarm

- To unsuppress an alarm:

1. Call up an alarm list that contains the alarm that you want tounsuppress.

2. Cursor to the alarm. Press E.

CC: 6-3-8


Configuring Alarm List and Event List Properties

You can configure the printing properties and size of some alarm listsand event lists.

Size of alarm lists and event lists

Each console has a maximum number of alarms and events that can bestored. The maximum number is displayed in the “Total Entries” field onthe Alarm List Configuration screen (see Figure 6.3.2).

You configure the size of some alarm lists and event lists. The sum ofthe sizes of all lists must not exceed the “Total Entries” value. You mustkeep track of the sum of the sizes yourself.

Batch-generated alarms and events

Each batch-generated alarm uses 2 entries. For example, if the Processlist type has a size of 200, it can hold 100 batch-generated processalarm messages.

Console restart

All alarm and event lists are cleared if the console is restarted.

The Alarm List Configuration Screen

The Alarm List Configuration screen is used to configure size andprinting properties of alarm type lists. Figure 6.3.2 shows an example ofan Alarm List Configuration screen. Table 6.3.3 describes the fields onthe Alarm List Configuration screen.

CC: 6-3-9


ALARM LIST CONFIGURATION 01-Aug-96 11:44:24+---Print---+

List Type Size Trigger Node�

Hardware �200 �50 �32 Flush Block Cache

Process �200 �100 �20 External Alarm �NC

Batch �200 �50 �20 Backup Printer Node�20

System Status �100 �50 �32 Restore Primary Printer Nodes

Disk Events �50 �25 �32 Alarm Print�Normal

Operator Log �100 �50 �32 Last Initialize Time28-Oct-95 07:11:38

Suppressed 2860 ** **

Total Entries (All Lists, including Events) 3850

�Initialize Lists (press ENTER)WARNING: This will Clear ALL Alarm and Event Lists

FULL CONFIG 1

- To call up:D A L C [ENTER] at the

command line

The difference between the “Total Entries” sizeand the sum of the configured alarm type listand event list sizes is automatically reserved forthe suppressed alarm lists.

Shows the maximum number ofalarms and events that can bestored in console RAM.

- To change an entry:1. Cursor to the field, type in the new entry, and press [ENTER].

New entries are displayed in a contrasting color.

2. The changes do not take effect until you initialize all the lists.When you have made all the changes to the screen that youwant, initialize the list by cursoring to the “Initialize Lists” fieldand pressing [ENTER].

NOTE: This will clear all alarm and event lists.

- To access other screens:D [PAGE AHEAD] to see Event List

Configuration

D [PAGE BACK] to see Automatic AlarmDeletion

Figure 6.3.2. Alarm List Configuration Screen

CC: 6-3-10


Table 6.3.3. Alarm List Configuration Screen Fields

Field Description

Alarm Print

Determines how the alarm list is printed.Normal = Prints an alarm list with a heading on a new page (form feed).

Single Line = Prints an alarm list without a heading and without a form feed.

Backup Printer Node

Specifies a backup printer node for printing lists. This field must specify the nodeof a printer.

This field is used as a backup for printer nodes specified on the Alarm ListConfiguration, Event List Configuration, and Console Configuration screens.

External Alarm

Specifies the type of console contacts used if the console is connected to anexternal annunciator. Contacts are actuated when a process or hardware alarmoccurs and are deactuated by pressing the [ALARM ACK] button.

NC = normally closed (open on alarm)NO = normally open (closed on alarm)

Off = non-functioning

Flush Block Cache Clears the block cache, to ensure information stored in console’s cache is up todate. Useful on larger systems after configuration changes.

Initialize ListsInitializes (clears) all alarm and event lists. To initialize lists, cursor to the“Initialize Lists” field and press [ENTER]. New entries to the Alarm ListConfiguration screen are not implemented until the list is initialized.

List Type Displays the list types.

Node Specifies the console node where the list is printed.

Restore PrimaryPrinter Nodes

Restores the primary printer if it is available. This field is used as a backup forprinter nodes specified on the Alarm List Configuration, Event List Configuration,and Console Configuration screens. If a printer node entry on one of these fieldsis backlighted, there has been a printer problem. You can attempt to restore theprimary printer by cursoring to the “Restore Primary Printer Node” field andpressing [ENTER].

SizeSpecifies the number of entries that are saved in a list. Once the “Size” value isreached, each new entry added to the list causes the oldest entry to be taken offthe list.

Trigger

Specifies the number of entries of a list that trigger the printing of the list. Forexample, if “Trigger�24” is configured, the list is printed after 24 entries haveoccurred. To print all alarms, the “Trigger” value must be less than or equal to the“Size” value.If a list type has active and cleared lists, both are printed when the trigger isreached.

CC: 6-3-11


RS3 Events

RS3 offers 255 event types that perform one of the following tasks:

D Send a message to one of ten user-defined event lists.

D Initiate the printing of a user-defined or system-defined event list.

Event types are identified by a number between 1 and 255:

D Event types 1 to 240 are user-definable.

D Event types 241 to 255 are reserved to initiate the printing of alist as explained in Table 6.3.4.

Table 6.3.4. Reserved Event Numbers

EventNumber Initiates printing of... Event

Number Initiates printing of...

241 Hardware Alarm Lists 249 Event List 5

242 Process Alarm Lists 250 Event List 6

243 System Status List 251 Event List 7

244 Disk Event List 252 Event List 8

245 Event List 1 253 Event List 9

246 Event List 2 254 Event List 10

247 Event List 3 255 Operator Change Log

248 Event List 4

CC: 6-3-12


User-defined Events

User-defined events can be generated from a ControlBlock logic step,from a batch script, or from a host application.

D When you generate an event from a ControlBlock logic step, youuse the Discrete Diagram screen to specify the following:— The event type (a number between 1 and 240)— The message type (Evt)— The ControlBlock variable that contains the value that you

wanted printed in the event list entry (continuous inputs Athrough O, discrete inputs a through p, or discrete outputs @athrough @o)

— The logic step action that you want to generate the event(rise, one, fall, off, or change)

For more information about configuring events, see CB: 6.

D When you generate an event from a batch script, you use aRosemount Basic Language instruction to specify the following:— The event type (a number between 1 and 240)— The priority of the message (a number between 0 and 15 with

0 indicating a high priority and 15 a low priority)— The message text (up to 21 characters)For more information about configuring events, see RB.

D When you generate an event from a host application, you use theALM_generateEvent function. For more information aboutconfiguring events, see Rosemount Network Interface (RNI)Programmer’s Manual (RP: 4).

CC: 6-3-13


Configuring the Event List

The Event List Configuration screen allows you to perform the followingtasks from an RS3 console:

D Assign event types 1 to 240 to one, and only one, of the 10 eventlists. One approach is to configure List 1 with events 1 to 24, List2 with events 25 to 48, etc.

D For each of the 10 event lists, you also define the following:— The number of entries to save; after the list reaches that size,

the oldest entry is always deleted when a new entry comes in.— The number of entries to trigger a printout of the list; each

subsequent printing lists only entries that occurred since thelast print-out.

— The console node where the list is to be printed.

The Event List Configuration screen is shown in Figure 6.3.3. Thescreen fields are described in Table 6.3.5.

CC: 6-3-14


EVENT LIST CONFIGURATION 21-Jul-96 08:00:58+---Print---+

Event List Size Trigger Node +------------Event Ranges------------+

1 �20 �18 �10 �1,7 �9 �11,21 � �

2 �100 �90 �28 �101,195 �8 �37 �200,202 �0

3 �0 �0 �0 �0 �0 �0 �0 �0

4 �0 �0 �0 �0 �0 �0 �0 �0

5 �20 �18 �2 �45,50 �61 �84 �89,100 �38

6 �0 �0 �0 �0 �0 �0 �0 �0

7 �0 �0 �0 �0 �0 �0 �0 �0

8 �0 �0 �0 �0 �0 �0 �0 �0

9 �0 �0 �0 �0 �0 �0 �0 �0

10 �0 �0 �0 �0 �0 �0 �0 �0

- To call up:D E L C [ENTER] at the

command line

- To access other screens:D [PAGE AHEAD] to see Alarm Configuration

D [PAGE BACK] to see Alarm List Configuration

- To change an entry:1. Cursor to the field, type in the new entry, and press [ENTER].

New entries are displayed in a contrasting color.

2. The changes do not take effect until you initialize all the lists.When you have made all the changes to the screen that youwant, initialize the list by cursoring to the “Initialize Lists” fieldand pressing [ENTER].

NOTE: This will clear all alarm and event lists.

Figure 6.3.3. Event List Configuration Screen

CC: 6-3-15


Table 6.3.5. Event List Configuration Screen Fields

Field Description

Event Lists Displays event list numbers 1 to 10.

Event Ranges

Specifies the event types that are included in the event list. The event typescan be listed individually or as a group. Figure 6.3.3 shows some exampleentries. Up to five ranges of event types can be specified for each event list.Events 1 to 240 can be specified in only one list.

Node Specifies the console node where the list is printed.

SizeSpecifies the number of entries that are saved in a list. Once the “Size” value isreached, each new entry added to the list causes the oldest entry to be takenoff the list.

Trigger

Specifies the number of entries of a list that trigger the printing of the list. Forexample, if “Trigger�24” is configured, the list is printed after 24 entries haveoccurred. To print all events, the “Trigger” value must be less than or equal tothe “Size” value.

CC: 6-3-16


CC: 6-4-1

RS3: Alarm Management Alarm History

Section 4:Alarm History

Alarm history is provided with the alarm log. The alarm log stores alarmmessages in a file on the console disk. You configure how the alarm loginformation is sorted and displayed at the console.

This section describes:

D Configuring log display configurations

D Displaying information from the alarm log

D Disabling and enabling the alarm log

CC: 6-4-2


Configuring Log Display Configurations

You configure log display configurations that specify how the alarm loginformation is sorted and displayed on the Alarm Log Display screen.

Log display configurations are part of the console configuration file.

Up to 30 log display configurations can be configured at a console.

You configure the log display configurations on the Log DisplayConfiguration screen (see Figure 6.4.1). The fields on the screen aredescribed in Table 6.4.1.

LOG DISPLAY CONFIGURATION 25-Jul-96 12:07:37

LOG Logging Criteria >log1 Configuration File :console18

HELP: unit area blk pri type state node ctime

SORT:Sort Crit>pri

Direction>Ascending SORT Status >ON

FIND:Find Crit>unit=1-4

| >

| >

FILTERFilt Crit>

| >

| >

FULL CONFIG 1

- To call up:D L D C [ENTER]

at the command line

D [SELECT] on CNFG from AlarmLog Display


to see other configurations

D [SELECT] on LOG to see AlarmLog Display

Figure 6.4.1. Log Display Configuration Screen

CC: 6-4-3


Table 6.4.1. Log Display Configuration Screen Fields

Screen Location Description

Top of screen

LOG = Cursor to this word and press [SELECT] to see the Alarm LogDisplay.

Logging Criteria = Specifies the name of this log display configuration. You can[PAGE AHEAD] and [PAGE BACK] to other log displayconfigurations. To delete a configuration, press [ENTER].

Configuration File = Displays the current console configuration file.

HELP

The parameters in this location are used in the Sort, Find, and Filter locations tospecify the logging criteria. They are listed on the screen as a helpful reminder. Youcan cursor to each of these words and press [ENTER] for a short description of theparameter.The available parameters are:

unit = plant unit (1--255)

area = area nameblk = block tag or address (sort by address only)

pri = priority (ControlBlock�0--15; I/O block�0--3)

type = alarm type (hard, proc, crit, adv, batch, sys, disk, el1--el10)state = alarm state for Find and Filter (active, clear, unack, ack, suppr)

state = alarm order for “Sort Crit” field (yes, no)yes specifies alarms in the order:

—active unacknowledged—cleared unacknowledged—active acknowledged—cleared acknowledged

no specifies alarms in the order:—cleared unacknowledged—active unacknowledged—cleared acknowledged—active acknowledged

node = node number

ctime = cutoff time (format=dd-mm-yy/hh:mm:ss)

SORT

The fields in this location are used to specify the sort criteria.Sort Crit = Specifies how to sort the alarm log display. As an example, the

configuration in Figure 6.4.1 will sort the log by alarm priority andwill sort each priority by block address. You cannot sort by area orctime.

Direction = Specifies ascending or descending sort order.

SORT Status = Specifies the state of the sorter. OFF specifies that the alarmscannot be sorted. ON specifies that the alarms can be sorted.With ON specified, new alarms are not added while the Alarm LogDisplay screen is displayed. To change the entry, cursor to thefield and press [ENTER].


CC: 6-4-4


Table 6.4.1. Log Display Configuration Screen Fields (continued)

Screen Location Description

FINDSpecifies which information is included in the alarm log display. If no parameters areconfigured, all alarms are included.


FILTERSpecifies which information is excluded from the alarm log display. If no parametersare configured, no alarms are excluded.


CC: 6-4-5


FIND:Find Crit>unit=1-4

| >

| >

FILTER:Filt Crit>state=clear

| >

| >

This configuration specifies that the alarm logdisplays all alarms from plant units 1 through 4.Find Crit>unit=1-4

Find Crit>blk=boiler1,boiler2This configuration specifies that the alarm logdisplays all alarms from blocks “boiler1” and“boiler2”.

Find Crit>blk=boiler1

| >unit=1-5

| >

Find Crit>blk=boiler1&type=critThis configuration specifies that the log displaysall critical alarms from block boiler1.The “&” represents a logical and operation.

Find Crit>blk=boiler1|unit=1-5

Both of these configurations specify the samecriteria—that the log displays all alarms fromblock boiler1 and all alarms from plant units 1--5.

The “|” represents a logical or operation.

This configuration specifies that the log displaysall alarms from plant units 1 through 4, butexcludes cleared alarms.

Figure 6.4.2. Examples of Criteria Configurations

CC: 6-4-6


Displaying Information from the Alarm Log

The Alarm Log Display shows information from the alarm log fileaccording to the criteria defined in the log display configuration. You cantemporarily modify the log display configuration from the Alarm LogDisplay screen.

The alarm log file resides in the Logs folder on the console and containsup to 65,535 alarm messages. When the alarm log file is full, the newestmessage overwrites the oldest message. The initial name of the alarmlog file is $$ALARM.

You configure which alarm types are stored in the alarm log with the“Alarm Log Types” field on the Alarm Configuration screen. For moreinformation about the Alarm Configuration screen, see Section 5 in thismanual.

Figure 6.4.3 shows an example of an Alarm Log Display. Table 6.4.2describes the fields on the screen.

CC: 6-4-7


ALARM LOG DISPLAY 25-Jul-96 12:07:37

File Name :vol12,console18 CNFG FIND FILT SORT LPRT PPRTCnfg’d Log: OCCUR Entry Count:7Logging Criteria >log1 Top Entry #>1 Last Entry :7

Find Crit: node=16-20Filt Crit:

Occur S Source Description Sum05-Dec-91

18:46.11:685 >=19A 0-1 Controller Not Backed Up ?-OK18:45.40:185 >=19A 0-175 Controller Not Backed Up ?-OK18:45.18:190 >=18 0-1 Alarm logging Enabled ?-OK18:45.16:135 >=18 0-1 Trend Recording Disabled ?-OK18:45.04:245 >=18 0-175 Node Restarted ?-OK18:45.00:686 >=16 0-1 Node Restarted ?-OK18:43.30:195 >=19A 0-175 Controller Not Backed Up ?-OK

FULL CONFIG 5

- To call up:D A L D (node) (log file name)

[ENTER] at the command line

D A L S (log display config) [ENTER]at the command line

D [SELECT] on the LOG button from LogDisplay Configuration


to see more alarms

D [SELECT] on CNFG to see Log DisplayConfiguration

D [EXCH] to toggle between alarmformats of occur and current.[EXCH] above the top alarm to toggleall alarms on the screen.

[EXCH] on one alarm to toggle that onealarm.

Specifies a log displayconfiguration. The Alarm LogDisplay shows alarms accordingto the log display configuration.

If the log display configuration specifiesthat the sort state is on, then thedisplay is not sorted until you cursor tothe “Sort” field and press [ENTER].This is true each time that you call upthe Alarm Log Display screen.

Alarm format that is currentlydisplayed—either occur or current.

Figure 6.4.3. Using the Alarm Log Display Screen

CC: 6-4-8


Table 6.4.2. Alarm Log Display Screen Fields

Field Meaning

Cnfg’d Log

Specifies the state of the alarm log. Appending alarms to the list is the normal state.Inserting means a regeneration is happening and the alarms have to be inserted inthe correct time order if they are not already on that console. NA (not applicable) isshown if the log is not enabled.

Description The text of the alarm messages which varies by alarm type and the method used togenerate the alarm. For more information, see AL: 1.

Entry Count Specifies the number of displayed entries. The highest value shown is 1600, even ifmore than 1600 entries are displayed.

File Name Displays the name of the current console configuration file.

Filt Crit Displays the current filter criteria for the display.

FIND, FILT, SORT

Can be used to modify the log display configuration temporarily. The modificationsare only in effect as long as the Alarm Log Display appears. Press [SELECT] to callup the corresponding configuration window. For information about displayconfiguration, see “Log Display Configuration” on page 6-4-2.

Find Crit Displays the current find criteria for the display.

Last Entry Displays the number of the last entry in the sublog.

Logging Criteria Specifies the name of the log display configuration that determines which alarm loginformation is displayed and how it is displayed.

LPRT Prints the alarm log according to the current display criteria. Press [SELECT] on thisfield to print. The alarms are printed in 132 column format.

PPRT Prints a page of the currently displayed screen. Press [SELECT] on this field to print.

S(Occur mode)

The state of the block at occurrence time: D means the alarm belonged to a disabledarea when it occurred. S means the alarm is from a suppressed block and does notbelong to a disabled area. * means the alarm is late and is not from a suppressedblock or a disabled area. “ ” means the alarm is not from a suppressed block or adisabled area or late.

S(Current mode)

The state of the block at clear time: D means the alarm belonged to a disabled areawhen it occurred. S means the alarm is from a suppressed block and does not belongto a disabled area. * means the alarm is late and is not from a suppressed block or adisabled area. “ ” means the alarm is not from a suppressed block or a disabled areaor late.

Source Tag of the block that the alarm came from.

SummA--The alarm is acknowledged but not cleared. ?--OK Alarm is cleared but notacknowledged. A--OK Alarm is acknowledged and cleared. ?--The alarm isunacknowledged and is not cleared.

Top Entry Specifies the number of the log entry that is shown at the top of the display.

CC: 6-4-9


Disabling and Enabling the Alarm Log

You can disable the alarm log. When the alarm log is disabled, newalarms are not added to the log. When the alarm log is enabled again,alarms that occurred while the log was disabled are put into the log (ifthe alarms are stored at the console).

- To enable or disable the alarm log from the Alarm Configurationscreen:

D Cursor to the “Alarm Log” field and press [NEXT OPTION] tomake the desired entry. Press [ENTER].

- To enable the alarm log from the command line:

D Type E L A [ENTER].

- To disable the alarm log from the command line:

D Type D L A [ENTER].

CC: 6-4-10


CC: 6-5-1

RS3: Alarm Management Configuration and Display Topics

Section 5:Configuration and Display Topics

This section describes other alarm management issues such as theAlarm Configuration screen, alarm regeneration, alarm priority, andalarm display mode.

CC: 6-5-2


Alarm Configuration Screen

The Alarm Configuration screen is used to configure parameters foralarm management. Figure 6.5.1 shows the Alarm Configuration screenfor the System Manager Station (SMS). Figure 6.5.2 shows the AlarmConfiguration screen for the Multitube Command Console (MTCC).

Table 6.5.1 describes the fields on the screen.

ALARM CONFIGURATION 09-Apr-96 12:07:37

Alarm Log �Enabled Alarm log file�filename Alarm log size �3850 entriesActual Log Size 142K

Alarm Log Types �System, Disk, Hard, Crit, Batch, Adv, EL1-EL10, Proc

Alarm Summary >Enabled Hardware alarms have more priority than �Crit

Alarm Regeneration : NOW Read Console Lists �16,18

Suppressed Types �System, Hard, Batch, Proc, Crit, AdvKey classes:suppress alarms �OPER screen ack�OPER area status �OPER alarmview�OPER

Remote can Silence �no Local Silence Time !0 secs Alarm Speaker !yes

Ack/Horn �Silence, then Ack Ack=Screen Ack? �no External Alarm �OFF

Unacked, Cleared alarm �ISA

Replace yellow on printout �5n brown Default priority for CB: �5 IOB: �2

Alarm View Toggle:>FULL

FULL CONFIG 11

- To call up:D A C at the command line

D [PAGE AHEAD] from Event List Configuration

D [PAGE BACK] from Automatic Alarm Deletion

- To access other screens:D [PAGE AHEAD] to see Automatic Alarm

Deletion

D [PAGE BACK] to see Event ListConfiguration

Figure 6.5.1. Alarm Configuration Screen for the SMS

CC: 6-5-3


ALARM CONFIGURATION 09-Apr-96 12:07:37

Alarm Log �Enabled Alarm log file�filename Alarm log size �3850 entriesActual Log Size 142K

Alarm Log Types �System, Disk, Hard, Crit, Batch, Adv, EL1-EL10, Proc

Alarm Summary >Enabled Hardware alarms have more priority than �Crit

Alarm Regeneration : NOW Read Console Lists �16,18

Suppressed Types �System, Hard, Batch, Proc, Crit, AdvKey classes:suppress alarms �CONFIG screen ack�CONFIG area status �CONFIG alarmview�CONFIG

Remote can Silence �no Local Silence Time !0 secs Alarm Speaker !yes

Ack/Horn �Silence, then Ack Ack=Screen Ack? �no External Alarm �OFF

Unacked, Cleared alarm �ISA

Replace yellow on printout �5n brown Default priority for CB: �5 IOB: �2

Trend: Backup and File full alarms �Enabled Alarm View Toggle:>FULL

FULL CONFIG 11

- To call up:D A C at the command line

D [PAGE AHEAD] from Event List Configuration

D [PAGE BACK] from Automatic Alarm Deletion

- To access other screens:D [PAGE AHEAD] to see Automatic Alarm

Deletion

D [PAGE BACK] to see Event ListConfiguration

Figure 6.5.2. Alarm Configuration Screen for the MTCC

CC: 6-5-4


Table 6.5.1. Alarm Configuration Screen Fields

Field Description Field Entries

Ack/Horn

Specifies the effect on the console alarm horn (and any externalalarm contacts) of pressing the [ALARM ACK] key.

Silence then Specifies that, if the console horn is on, theAck first push silences the horn (and deactivates

any external alarm contacts) and the secondpush acknowledges the alarm.

Silence and Ack Specifies that one push both silences the horn(and deactivates any external alarm contacts)and acknowledges the alarm.

No Silence Specifies that pushing the key has no effect onthe console alarm horn (or any external alarmcontacts).

Silence, then AckSilence and Ack

No Silence

Ack=ScreenAck?

Specifies whether or not the [ALARM ACK] key performs a screenacknowledge function on the following screens when the alarmsummary is enabled. The screen acknowledge function issummarized below.

D Group and Unit—only acknowledges process alarms onpoints that are visible on the display. For example, if agroup faceplate does not show tag/A, then process alarmson tag/A will not be acknowledged.

D Alarm lists—acknowledges all alarms visible on thescreen and those unacknowledged alarms that are an exactmatch.

NOTE: This acknowledges alarms not visible on the screen.

Yes, No

Actual LogSize

Displays the maximum size of the alarm log, in bytes. This value isdetermined by the entry configured in the “Alarm Log Size” field. Display only

Alarm Log

Specifies whether the alarm log is Enabled or Disabled. When thealarm log is disabled, new alarms are not added to the log. Whenthe alarm log is enabled again, any new alarms are put into the log(if they are stored in console RAM).If you disable the alarm log from the Alarm Configuration screenand the field displays Shutdown, it indicates that the console isinserting alarms in the alarm log.While the field displays Shutdown, you cannot perform any actionson the alarm log so that the console can finish its present task.When the console is finished, the field displays Disable.

Enabled, Disabled

Alarm LogSize

Specifies the maximum number of entries in the alarm log. If youchange the log size, the alarm log is cleared.

An alarm generated in a batch script uses 2 entries in the alarmlog.

3850--65535

NOTE: Bold text indicates default selections.


CC: 6-5-5


Table 6.5.1. Alarm Configuration Screen Fields (continued)

Field Field EntriesDescription

Alarm LogTypes

Specifies which alarm types are included in the alarm log.To specify alarm types, type the first letter of the alarm types thatyou want to include. For example, “phb” indicates that process,hardware, and batch alarms are included in the alarm log.For event lists, specify the number of the event list. For example,“1--5” specifies event lists 1 through 5. “0” specifies event list 10.“1--0” specifies all event lists.To specify all alarm types, enter “*”.

a=Advisoryb=Batch

c=Critical

d=Diskh=Hardware

p=Process

s=System status1--0=all event lists

*=all types listed

AlarmRegeneration

Causes a regeneration of console alarms. To regenerate alarms,press [ENTER]. For more information about alarm regeneration,see “Alarm Regeneration” on page 6-5-11.

Now

Alarm Speaker

Specifies whether or not the console alarm horn is activated.Alarm speaker volume is configured in the “Speaker Volume” fieldon the Console Configuration screen.

The “Alarm Speaker” field also appears on the ConsoleConfiguration screen.

yes, no

AlarmSummary

Specifies whether the alarm summary mode is Enabled orDisabled. When the alarm summary mode is disabled, the alarmbanner mode is enabled. For more information about alarmdisplay modes, see “Alarm Display Mode” on page 6-5-13.

Enabled, Disabled

Alarm ViewToggle

Specifies whether the alarm animation is set to full or focusedmode. Full mode allows all the animation to be displayed includingsuppressed, disabled, and inhibited. Focused mode masks out theanimation of suppressed, disabled, and inhibited alarms.

Full, Focused

Default priorityfor CB: IOB:

Specifies default alarm priorities for ControlBlocks (CB) and I/Oblocks (IOB). The default priorities are used when blocks arecreated at this console. For more information about priorities, see“Alarm Priority” on page 6-5-12.

CB�0--15IOB�0--3(0=high)

External Alarm

Specifies the type of console contacts used if the console isconnected to an external annunciator. Contacts are actuated whena process or hardware alarm occurs and are deactivated when theconsole horn is silenced.

D NC = normally closed (open on alarm)

D NO = normally open (closed on alarm)

D Off = non-functioningThe “External Speaker” field also appears on the Alarm ListConfiguration screen.

NC, NO, Off



CC: 6-5-6




Hardwarealarms havemore prioritythan

Specifies the relative priority of hardware alarms. The entryspecifies which alarm type follows hardware alarms in the systempriority scheme. For more information about alarm priorities, see“Alarm Priority” on page 6-5-12.

CRIT, ADV, BATCH,SYSTEM, DISK,

NONE

Key class:alarm view

Specifies the key access level required to toggle between full andfocused alarm views.

CONFIG,SUPER, OPER

Key class:area status Specifies the key access level required to enable/disable areas.

CONFIG,SUPER, OPER

Key Class:screen ack

Specifies the key access level required to perform a screenacknowledge function.

CONFIG,SUPER, OPER

Key Class:suppressalarms

Specifies the key access level required to suppress alarms. CONFIG,SUPER, OPER

Local SilenceTime

Guarantees from one second to five minutes of peace and quietwhen the [SIL] key is pressed, or the Silence Horn (S H)command is entered. New alarms will not reactivate the horn untilthe time period has expired.

0 to 300

Read ConsoleLists

Specifies which consoles are searched for alarm messages uponalarm regeneration. For more information about alarmregeneration, see “Alarm Regeneration” on page 6-5-11.

Console nodenumbers

Remote CanSilence

Specifies whether or not an alarm acknowledge at anotherconsole silences the local console alarm horn. yes, no

Replaceyellow onprintout with

Specifies a color that replaces yellow when a screen is printed.Yellow is often difficult to see when printed. Use [NEXT OPTION]to see the color choices.

a console color(a number 1--16

and n or r)

SuppressedTypes

Specifies which alarm types can be suppressed.To specify alarm types, type the first letter of the alarm types thatyou want to include. For example, “sha” indicates that systemstatus, hardware, and advisory alarms can be suppressed.To specify all possible alarm types, enter “*”.

a=Advisoryb=Batch

c=Critical

h=Hardwarep=Process

s=System status

*=all types listed



CC: 6-5-7




Trend: Backupand File fullalarms

Specifies whether or not Trend File Overflow, Trend File OverflowWarning, and Trend File trfx Ready for Backup alarm messagesare included in the alarm log.

NOTE: If you disable Trend Backup and File Full alarms, you willnot receive any trend overflow warnings in the Alarm Log.

Enabled specifies that the messages are included.

Disabled specifies that the messages are not included.

Enabled, Disabled

Unacked,Cleared alarm

Specifies how alarms animate. Each entry specifies a different setof alarm animation characteristics. For more information aboutalarm animation, see Section 6, “Alarm Animation”.

ISA, RMT, color


CC: 6-5-8


Alarm Configuration Screen—Automatic Alarm Deletion

Figure 6.5.3 shows the Automatic Alarm Deletion screen. Table 6.5.2describes the fields on this screen.

The Automatic Alarm Deletion screen deletes alarms from console RAMwhen the conditions you specify are met.

AUTOMATIC ALARM DELETION 25-Jul-96 02:05:12

Delete Alarms/Events �Disabled Time (DD/HH:MM) �00/00:02

Types �CRIT, ADV, BATCH, HARD, EL1-EL10

Deletion Criteria-------------------------------------------------

Types Acknowledged Logged Printed Priorities

CRITICAL �yes �yes �yes �0-15

ADVISORY �yes �yes �yes �0-15

BATCH �yes �yes �yes �0-15

HARDWARE �yes �yes �yes �0-15

SYSTEM �yes �yes �yes �0-15

DISK �yes �yes �yes �0-15

EVENT �yes �yes �0-15

Initialize Deletion Criteria for all types (Press ENTER)

- To call up:D A C [ENTER] at the command line,

then [PAGE AHEAD]

D [PAGE BACK] from Alarm List Configuration

- To access other screens:D [PAGE AHEAD] to see Alarm List

Configuration

D [PAGE BACK] to see Alarm Configuration

The types appear when they areconfigured in the Types field.

Figure 6.5.3. Automatic Alarm Deletion Screen

CC: 6-5-9


Table 6.5.2. Alarm Configuration Screen----Automatic Alarm Deletion Fields

Field Description Field Entries

Acknowledged Specifies whether or not alarms of this type must beacknowledged before they can be deleted. yes, no

DeleteAlarms/Events

Specifies whether the alarm delete process is enabled ordisabled.

The alarm delete process automatically deletes entries fromthe alarm lists and event lists if the entries:

D are cleared

D are of the types configured in the “Types” field

D are older than the time configured in the “Time” fieldD meet the “Acknowledged”, “Logged”, “Printed”, and

“Priorities” fields configured requirements

Enabled,Disabled

Initialize DeletionCriteria for all types

Pressing [ENTER] on this field clears the Deletion Criteriatable. [ENTER]

Logged

Specifies whether or not alarms of this type must be loggedbefore they can be deleted.

To be logged, all information known about an alarm at theconsole must also be in the alarm log. For example, if analarm that is in the alarm log is cleared, the clearedinformation must be entered in the alarm log before the alarmcan be deleted.If the heading Logged is blinking, then an alarm type isconfigured with a Logged value of Yes, even though the alarmtype is not configured in the Alarm Log Types field on theAlarm Configuration screen (page 1). This means that thealarms of that type will not be logged and, therefore, will notbe deleted.

yes, no

Printed

Specifies whether or not alarms of this type must be printedbefore they can be deleted.

If the heading Printed is blinking, then there is a printerproblem that is preventing alarms from being printed.

yes, no

PrioritiesSpecifies the alarm priorities that can be deleted.An entry can be a single number (for example, 7) or a rangeof numbers separated by a dash (for example, 5--15).

0--15



CC: 6-5-10


Table 6.5.2. Alarm Configuration Screen----Automatic Alarm Deletion Fields (continued)


Time (DD/HH:MM)

Specifies a time interval for the alarm delete process. Allalarms older than the specified time can be deleted.

For example, an entry of 00/12:00 specifies that all alarmsmore than 12 hours old can be deleted in the alarm deleteprocess.

For a description of the alarm delete process, see the “DeleteAlarms” field.

a time in the formdd/hh:mm

00/00:00

Types

Specifies the types of alarms that can be deleted in the alarmdelete process.

To specify alarm types, type the first letter of the alarm typesthat you want to include. For example, “sha” indicates thatsystem status, hardware, and advisory alarms can be deleted.

To specify all possible alarm types, enter “*”.

For event lists, specify the number of the event list. Forexample, “1--5” specifies event lists 1 through 5. “0” specifiesevent list 10. “1--0” specifies all event lists.

a=Advisoryb=Batch

c=Critical

d=Diskh=Hardware

p=Process

s=System status1--0=all event lists

*=all types listed


CC: 6-5-11


Alarm Regeneration

If a console quits functioning or is rebooted, alarms stored in consoleRAM are lost. When the console becomes functional again, the alarmlists can be regenerated from other consoles.

When Do Alarms Regenerate

Alarms are automatically regenerated when the console restarts. Youcan also manually regenerate alarms.

How Consoles Regenerate Alarms

You specify which consoles are searched during alarm regeneration.When alarm regeneration occurs, the regenerating console searchesthe specified consoles for alarms.If the source of an alarm in another console is owned by theregenerating console, the regenerating console retrieves the alarm. Formore information about ownership criteria, see “How Alarms Get Storedin Console RAM” on page 6-2-1.

Configuration

The “Read Console Lists” field on the Alarm Configuration screen isused to specify which consoles are to be searched during alarmregeneration. The “Alarm Regeneration” field is used to regeneratealarms manually. For more information about the Alarm Configurationscreen, see “Alarm Configuration Screen” on page 6-5-2.

Restrictions

D The console can only regenerate alarms if they are present at thespecified consoles. If the other consoles have rebooted,initialized their alarm lists, or otherwise lost their alarms, theconsole cannot recover the desired alarms.

CC: 6-5-12


Alarm Priority

Alarms are prioritized by alarm type, and by alarm priority number withineach alarm type. Alarm priorities determine which unacknowledgedalarm message is displayed in alarm banner mode when more than oneunacknowledged alarm exists. The unacknowledged alarm messagesare displayed according to the following criteria:

1. Alarm type priority

2. Alarm priority number

3. Time of alarm (newest first)

Alarm Type Priority

The alarm types are prioritized in the following order:

D Hardware[

D Critical Process

D Advisory Process

D Batch

D System Status

D Disk Event

[ This is the default priority. You can configure the relative priority ofhardware alarms with the “Hardware Alarms Have More Priority Than”field on the Alarm Configuration screen. For more information about theAlarm Configuration screen, see “Alarm Configuration Screen” onpage 6-5-2.

Alarm Priority Numbers

Each alarm message is assigned a priority number. The prioritynumbers are used to determine priority within an alarm type.

D When you configure a block, you assign the priority number foralarms from that block.

D All other alarms have a priority number of 0 (highest priority).

You can configure the default priority levels for blocks with the “Defaultpriority for CB” and “Default priority for IOB” fields on the AlarmConfiguration screen. For more information about the AlarmConfiguration screen, see “Alarm Configuration Screen” onpage 6-5-2.

CC: 6-5-13


Alarm Display Mode

The bottom of the console screen displays alarm information. Youdetermine whether the alarm information is presented in alarm bannermode or alarm summary mode. For information on setting the alarmmode, see 6-5-14. For information about using the alarm displaymodes, see OP:6 and the Alarm Messages Manual.

Alarm Banner Mode

Alarm banner mode displays the alarm banner of the unacknowledgedalarm with the highest priority. The alarm banner provides informationabout the alarm. Figure 6.5.4 shows an example of an alarm banner.

18:46:11.685 >=19A LIC-200/PV Drum Level High Critical LEVEL ?-OK

Figure 6.5.4. Example of an Alarm Banner

Alarm Summary Mode

Alarm summary mode displays a summary of alarm type information,including the number of active and unacknowledged alarms. The alarmtypes are also annunciated. Figure 6.5.5 shows an example of an alarmsummary.

FULL Crit 0/0 Adv 0/0 Batch 0/0 Hard 2/3 Sys 0/5 CONFIG 1

Number ofunacknowledged

alarms

Number ofactive alarms

Figure 6.5.5. Example of an Alarm Summary

CC: 6-5-14


Determining the Alarm Display Mode

- To change the alarm display mode from the AlarmConfiguration screen:

D Cursor to the “Alarm Summary” field. Press [NEXT OPTION] untilthe desired entry appears. Press [ENTER].

- To enable the alarm summary mode (disable the alarm bannermode) from the command line:

D Press A S E [ENTER].

- To disable the alarm summary mode (enable the alarm bannermode) from the command line:

D Press A S D [ENTER].

CC: 6-6-1

RS3: Alarm Management Alarm Animation

Section 6:Alarm Animation

What is alarm animation?

Alarm animation consists of visual cues on RS3 displays that indicatealarm information. Animation can involve color, blinking, andbacklighting.

There are two types of alarm animation:

D Focused Mode

D Full Mode

Focused mode means that certain objects are not highlighted when theyhave been disabled, suppressed, or inhibited, or when the object plantunit is unowned.

Full mode means that tags that are disabled, suppressed, or inhibitedwill highlight in the disabled, suppressed, or inhibited color. In addition,values from continuous block variables from unowned nodes or plantunits will continue to animate.

The animation modes only affect the animation of tags and values. Theydo not affect any other type of object, and they do not affect animationon alarm lists or the alarm log display.

You can set the animation mode on the Alarm Configuration screen orfrom the command line with Alarm View Toggle. For more informationon how to set the animation mode, see page 6-5-1.

What parts of RS3 displays animate?

Many displays include items that animate alarm conditions. This sectiongroups together items that animate alarms in the same way:

D Tags

D Tags on Trend Group Displays

D Block values

D Plant Units and Alarm Areas

D Graphic Alarm objects and Icon objects

D Alarm message source descriptions

CC: 6-6-2


Animation tables

Most of this section consists of animation tables like the one shown inFigure 6.6.1. The tables are designed for you to copy and use in yourplant. The tables show how the alarms work with the Full AnimationMode. For information on the Focused Animation Mode, seepage 6-6-1.

For example, Table 6.6.1 through Table 6.6.10 are the animation tablesfor tags. Each of these tables describes alarm animation for one set ofconfiguration parameters. You can select the table that matches yourconfiguration, write in the colors you have configured for your plant, andmake copies for the users of your system.

Item animated Configuration parametersvalid for this table

Lists the field on the ColorConfiguration screen that

determines the animation color

Blank area where you canwrite in the color you haveconfigured for your plant

Alarm information thatcan be determined if this

color is displayed

D If unblinking-- active hardware alarm and no

unacked alarms

D If blinking-- active hardware alarm and an

unacked alarm, or

-- unacked hardware alarmD Plant unit is not disabled.

D Block is not inhibited.

D If unblinking-- active critical alarm, and no active

hardware alarms, and no unackedalarms

D f blinking, no active or unacked hardwarealarms, and

-- active critical alarm and an unackedalarm or

-- unacked critical alarm

D Plant unit is not disabled.D Block is not inhibited.

Hardware Alarms

Critical Alarms

Color Configuration Plant Color Meaning

Table 6.6.1. Tag AnimationHardware Alarms Have More Priority than �Crit

Unacked, Cleared Alarm �ISA

Figure 6.6.1. Example Portion of an Animation Table

CC: 6-6-3


Tags

Screens that animate tags

D ControlBlock Directory screen

D ControlBlock Faceplate screens

D ControlBlock Status screen

D Group Display

D Loop Tuning Display

D Overview Display

D Process Graphics— Overview object— Pop-up faceplates— Tag object— Unit object

D Unit Display

Animation tables

Table 6.6.1 Hardware Alarms Have More Priority than�CritUnacked, Cleared Alarm�ISA

Table 6.6.2 Hardware Alarms Have More Priority than�AdvUnacked, Cleared Alarm�ISA

Table 6.6.3 Hardware Alarms Have More Priority than�BatchUnacked, Cleared Alarm�ISA

Table 6.6.4 Hardware Alarms Have More Priority than�SystemUnacked, Cleared Alarm�ISA

Table 6.6.5 Hardware Alarms Have More Priority than�Disk or NoneUnacked, Cleared Alarm�ISA

Table 6.6.6 Hardware Alarms Have More Priority than�CritUnacked, Cleared Alarm�RMT or Color

Table 6.6.7 Hardware Alarms Have More Priority than�AdvUnacked, Cleared Alarm�RMT or Color

Table 6.6.8 Hardware Alarms Have More Priority than�BatchUnacked, Cleared Alarm�RMT or Color

Table 6.6.9 Hardware Alarms Have More Priority than�SystemUnacked, Cleared Alarm�RMT or Color

Table 6.6.10 Hardware Alarms Have More Priority than�Disk or NoneUnacked, Cleared Alarm�RMT or Color

CC: 6-6-4


Table 6.6.1. Tag Animation Hardware Alarms Have More Priority than�CritUnacked, Cleared Alarm�ISA

Color Configuration Meaning Plant Color

Inhibit Alarms* D Block is inhibited.

Disable Alarms*D All areas with this plant unit are disabled.D Block is not inhibited.

Suppressed Alarms*D Block alarms are suppressed and no active or unacked

alarms exist for suppressed type exceptions.D Plant unit is not disabled. Block is not inhibited.

Hardware Alarms

D If not blinking-- active hardware alarm and no unacked alarms

D If blinking-- active hardware alarm and an unacked alarm, or-- unacked hardware alarm.

D Plant unit is not disabled. Block is not inhibited.

Critical Alarms

D If not blinking-- active critical alarm, and no active hardware alarms,

and no unacked alarmsD If blinking, no active or unacked hardware alarms, and

-- active critical alarm and an unacked alarm or-- unacked critical alarm.


Advisory Alarms

D If not blinking-- active advisory alarm, and no active hardware or

critical alarms, and no unacked alarmsD If blinking, no active or unacked hardware or critical

alarms, and-- active advisory alarm and an unacked alarm, or-- unacked advisory alarm


Batch Alarms

D If not blinking-- active batch alarm, and no active hardware, critical,

or advisory alarms, and no unacked alarmsD If blinking, no active or unacked hardware, critical, or

advisory alarms, and-- active batch alarm and an unacked alarm, or-- unacked batch alarm


System Alarms

D If not blinking-- active system alarm, and no active hardware,

critical, advisory, or batch alarms, and no unackedalarms

D If blinking, no active or unacked hardware, critical,advisory, or batch alarms, and-- active system alarm and an unacked alarm, or-- unacked system alarm


* In Focused Mode, the tags for alarms that are inhibited, disabled, or suppressed will not animate.

CC: 6-6-5


Table 6.6.2. Tag Animation Hardware Alarms Have More Priority than�AdvUnacked, Cleared Alarm�ISA






Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms






CC: 6-6-6


Table 6.6.3. Tag Animation Hardware Alarms Have More Priority than�BatchUnacked, Cleared Alarm�ISA






Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms






CC: 6-6-7


Table 6.6.4. Tag Animation Hardware Alarms Have More Priority than�SystemUnacked, Cleared Alarm�ISA






Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms






CC: 6-6-8


Table 6.6.5. Tag Animation Hardware Alarms Have More Priority than�Disk or NoneUnacked, Cleared Alarm�ISA






Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms






CC: 6-6-9


Table 6.6.6. Tag Animation Hardware Alarms Have More Priority than�CritUnacked, Cleared Alarm�RMT or Color

ColorConfiguration Meaning Plant Color


Disable Alarms* D All areas with this plant unit are disabled.D Block is not inhibited.

Suppressed Alarms*

D Block alarms are suppressed and no active orunacked alarms exist for suppressed type exceptions.


Hardware Alarms

D Active hardware alarmD If blinking, unacked alarmD If not blinking, no unacked alarmsD Plant unit is not disabled.D Block is not inhibited.

Critical Alarms

D Active critical alarmD No active hardware alarmsD If blinking, unacked alarmD If not blinking, no unacked alarmsD Plant unit is not disabled.D Block is not inhibited.

Advisory Alarms

D Active advisory alarmD No active hardware or critical alarmsD If blinking, unacked alarmD If not blinking, no unacked alarmsD Plant unit is not disabled.D Block is not inhibited.

Batch Alarms

D Active batch alarmD No active hardware, critical, or advisory alarmsD If blinking, unacked alarmD If not blinking, no unacked alarmsD Plant unit is not disabled.D Block is not inhibited.

System Alarms

D Active system alarmD No active hardware, critical, advisory, or batch alarmsD If blinking, unacked alarmD If not blinking, no unacked alarmsD Plant unit is not disabledD Block is not inhibited

A) Blinking in someother color

B) Color onUnacked, ClearedAlarm field onAlarmConfigurationscreen

A) Unacked, Cleared Alarm�RMT onlyB) Unacked, Cleared Alarm�Color only

D Unacked, cleared alarmD No active alarmsD Plant unit is not disabledD Block is not inhibited


CC: 6-6-10


Table 6.6.7. Tag Animation Hardware Alarms Have More Priority than�AdvUnacked, Cleared Alarm�RMT or Color




Suppressed Alarms*

D Block alarms are suppressed and no active orunacked alarms exist for suppressed typeexceptions.


Hardware Alarms


Critical Alarms


Advisory Alarms


Batch Alarms


System Alarms

D Active system alarmD No active hardware, critical, advisory, or batch

alarmsD If blinking, unacked alarmD If not blinking, no unacked alarmsD Plant unit is not disabledD Block is not inhibited


B) Color on Unacked,Cleared Alarm fieldon AlarmConfiguration screen




CC: 6-6-11


Table 6.6.8. Tag Animation Hardware Alarms Have More Priority than�BatchUnacked, Cleared Alarm�RMT or Color




Suppressed Alarms*



Hardware Alarms


Critical Alarms


Advisory Alarms


Batch Alarms


System Alarms








CC: 6-6-12


Table 6.6.9. Tag Animation Hardware Alarms Have More Priority than�SystemUnacked, Cleared Alarm�RMT or Color




Suppressed Alarms*



Hardware Alarms


Critical Alarms


Advisory Alarms


Batch Alarms


System Alarms








CC: 6-6-13


Table 6.6.10. Tag Animation Hardware Alarms Have More Priority than�Disk or NoneUnacked, Cleared Alarm�RMT or Color




Suppressed Alarms*



Hardware Alarms


Critical Alarms


Advisory Alarms


Batch Alarms


System Alarms








CC: 6-6-14


Tags on Trend Group Displays

The Tag field on the Trend Group Display animates the same as blockvariable values.

Animation tablesSee Table 6.6.11 through Table 6.6.20.

CC: 6-6-15


Block Variable Values

Screens that animate block variable values

D ControlBlock Faceplate screens

D Group Displays

D Loop Tuning Displays—discrete faceplates only

D Process Graphics— Disc object— Group object— Link object— Pop-up faceplate— Unit object— Overview object

D Unit Displays

D Overview Display

Animation tables











CC: 6-6-16


Table 6.6.11. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Crit

Unacked, Cleared Alarm�ISA


Hardware Alarms


D If blinking

-- active hardware alarm and an unacked alarm,or

-- unacked hardware alarm.

Critical Alarms

D If not blinking-- active critical alarm, and no active hardware

alarms, and no unacked alarms

D If blinking, no active or unacked hardware alarms,and

-- active critical alarm and an unacked alarmor

-- unacked critical alarm.

Advisory Alarms


critical alarms, and no unacked alarms

D If blinking, no active or unacked hardware or criticalalarms, and

-- active advisory alarm and an unacked alarm,or

-- unacked advisory alarm

Batch Alarms

D If not blinking-- active batch alarm, and no active hardware,

critical, or advisory alarms, and no unackedalarms

D If blinking, no active or unacked hardware, critical, oradvisory alarms, and

-- active batch alarm and an unacked alarm,or

-- unacked batch alarm

System Alarms



D If blinking, no active or unacked hardware, critical,advisory, or batch alarms, and

-- active system alarm and an unacked alarm,or

-- unacked system alarm

NOTE: In Focused Mode, block variable values will not animate unless the plant units are owned and theblock is not disabled or suppressed.

CC: 6-6-17


Table 6.6.12. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Adv



Hardware Alarms


D If blinking



Critical Alarms






Advisory Alarms






Batch Alarms






System Alarms







CC: 6-6-18


Table 6.6.13. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Batch



Hardware Alarms


D If blinking



Critical Alarms






Advisory Alarms






Batch Alarms






System Alarms







CC: 6-6-19


Table 6.6.14. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�System



Hardware Alarms


D If blinking



Critical Alarms






Advisory Alarms






Batch Alarms






System Alarms







CC: 6-6-20


Table 6.6.15. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Disk or None



Hardware Alarms


D If blinking



Critical Alarms






Advisory Alarms






Batch Alarms






System Alarms







CC: 6-6-21


Table 6.6.16. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Crit

Unacked, Cleared Alarm�RMT or Color


Hardware Alarms

D Active hardware alarmD If blinking, unacked alarm

D If unblinking, no unacked alarms

Critical Alarms

D Active critical alarmD No active hardware alarms

D If blinking, unacked alarm


Advisory Alarms

D Active advisory alarmD No active hardware or critical alarms



Batch Alarms

D Active batch alarmD No active hardware, critical, or advisory alarms



System Alarms


alarms

D If blinking, unacked alarmD If unblinking, no unacked alarms




D Unacked, cleared alarm

D No active alarms


CC: 6-6-22


Table 6.6.17. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Adv



Hardware Alarms



Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms






D No active alarms


CC: 6-6-23


Table 6.6.18. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Batch



Hardware Alarms



Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms






D No active alarms


CC: 6-6-24


Table 6.6.19. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�System



Hardware Alarms



Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms






D No active alarms


CC: 6-6-25


Table 6.6.20. Block Variable Value and Trend Group Display Tag AnimationHardware Alarms Have More Priority than�Disk or None



Hardware Alarms



Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms






D No active alarms


CC: 6-6-26


Plant Units and Area Names

Screens that animate plant units

D Plant Configuration screen

D Area Name Configuration(only plant units immediately to the right of the area name)

Screens that animate area names

D Area Name Configuration screen

Animation tables











CC: 6-6-27


Table 6.6.21. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Crit



Disable Alarms

D Plant Unit:-- all areas with this plant unit are disabled

D Area Name:-- area is disabled-- all plant units in this area are disabled. Plant units

can exist in more than one area. The plant unitmust be disabled in all areas to be truly disabled.

Hardware Alarms


D If blinking-- active hardware alarm and an unacked alarm, or-- unacked hardware alarm

D Plant unit or area name is not disabled

Critical Alarms


alarms, and no unacked alarmsD If blinking, no active or unacked hardware alarms, and

-- active critical alarm and an unacked alarm or-- unacked critical alarm


Advisory Alarms





Batch Alarms





System Alarms





CC: 6-6-28


Table 6.6.22. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Adv



Disable Alarms




Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms





CC: 6-6-29


Table 6.6.23. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Batch



Disable Alarms




Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms





CC: 6-6-30


Table 6.6.24. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�System



Disable Alarms




Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms





CC: 6-6-31


Table 6.6.25. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Disk or None



Disable Alarms




Hardware Alarms




Critical Alarms





Advisory Alarms





Batch Alarms





System Alarms





CC: 6-6-32


Table 6.6.26. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Crit



Disable Alarms

Plant Unit:-- all areas with this plant unit are disabled

Area Name:

-- area is disabled-- all plant units in this area are disabled. Plant

units can exist in more than one area. Theplant unit must be disabled in all areas to betruly disabled.

Hardware Alarms


D If not blinking, no unacked alarms


Critical Alarms



D If not blinking, no unacked alarmsD Plant unit or area name is not disabled

Advisory Alarms




Batch Alarms




System Alarms


alarms

D If blinking, unacked alarmD If not blinking, no unacked alarms






D No active alarmsD Plant unit or area name is not disabled

CC: 6-6-33


Table 6.6.27. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Adv



Disable Alarms


Area Name:



Hardware Alarms




Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms








CC: 6-6-34


Table 6.6.28. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Batch



Disable Alarms


Area Name:



Hardware Alarms




Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms








CC: 6-6-35


Table 6.6.29. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�System



Disable Alarms


Area Name:



Hardware Alarms




Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms








CC: 6-6-36


Table 6.6.30. Plant Unit and Area Name AnimationHardware Alarms Have More Priority than�Disk or None



Disable Alarms


Area Name:



Hardware Alarms




Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms


alarms








CC: 6-6-37


Graphic Alarm Objects and Icon Objects

Items that animate

D Alarm object window title

D Icon object that is grouped with one or more Alarm objects(has same animation as the Alarm object configured in theAl Obj field)

Animation tables











CC: 6-6-38


Table 6.6.31. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Crit



Hardware AlarmsDisk Alarms*

D If not blinking-- active hardware alarm or active disk alarm and no

unacked alarmsD If blinking

-- active hardware alarm and an unacked alarm, or-- unacked hardware alarm or unacked disk alarm

Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms




* Disk Alarms use the configured Hardware alarm color.

CC: 6-6-39


Table 6.6.32. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Adv





unacked alarms

D If blinking-- active hardware alarm and an unacked alarm, or

-- unacked hardware alarm or unacked disk alarm

Critical Alarms



D If blinking, no active or unacked hardware alarms, and-- active critical alarm and an unacked alarm or


Advisory Alarms




-- active advisory alarm and an unacked alarm, or


Batch Alarms


or advisory alarms, and no unacked alarms


-- active batch alarm and an unacked alarm, or


System Alarms




-- active system alarm and an unacked alarm, or-- unacked system alarm


CC: 6-6-40


Table 6.6.33. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Batch







Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms





CC: 6-6-41


Table 6.6.34. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�System







Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms





CC: 6-6-42


Table 6.6.35. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Disk or None







Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms





CC: 6-6-43


Table 6.6.36. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Crit




D Active hardware alarm or active disk alarmD If blinking, unacked alarm


Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms

D Active system alarmD No active hardware, critical, advisory, or batch alarms




B) Color on Unacked,Cleared Alarm fieldon AlarmConfigurationscreen



D No active alarms

* Disk alarms use the configured Hardware alarm color.

CC: 6-6-44


Table 6.6.37. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Adv






Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms








D No active alarms


CC: 6-6-45


Table 6.6.38. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Batch






Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms








D No active alarms


CC: 6-6-46


Table 6.6.39. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�System






Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms








D No active alarms


CC: 6-6-47


Table 6.6.40. Alarm and Icon Object AnimationHardware Alarms Have More Priority than�Disk or None






Critical Alarms




Advisory Alarms




Batch Alarms




System Alarms








D No active alarms


CC: 6-6-48


Alarm Message Source Descriptions

What is an alarm message source description?

An alarm message usually contains a tag or address that indicates thesource of the alarm.

Screens that animate alarm message source descriptions

D Alarm lists

D Graphics Alarm object

Table 6.6.41. Alarm Message Source Description Animation


Any colorD If blinking, alarm is unackedD If backlighted and not blinking, alarm is active

CC: 6-7-1

RS3: Alarm Management Hints for Alarm Management

Section 7:Hints for Alarm Management

This section discusses some problems you might have whenconfiguring event lists, along with some configuration tips.


- Some entries on event lists do not include all of the eventinformation.

Because of the limited size of event entries, some information maybe truncated or left off.

- Some entries on event list printouts do not include dates.

Dates do not appear on event list printouts when the event lists areautomatically generated.

Configuration Tips

- Using alarm broadcast configurations with batch systems

If you have batch scripts that use alarm traps, be sure to include theassociated Batch ControlFile nodes in the alarm broadcastconfigurations. Otherwise, the alarm messages that you want to trapon will never reach the Batch CPs.

- How to configure alarm lists so that alarms are printed one at atime without a form feed command or a header.

Configure “Alarm Print�Single Line” and “Trigger�1” on the AlarmList Configuration screen for the desired alarm lists.

- How to configure Alarm Logs for good system performance.

Alarm Logs are designed to provide flexibility and versatility.However, using this flexibility to its fullest can reduce systemperformance. For example, alarm logs can contain over 65,000entries. However, alarm logs over 15,000 entries can decreaseconsole performance.

In general, keep in mind that alarm log activities (logging, displaying,filtering, and so on) are disk processes. The console must performthese functions in addition to trending, reports, graphics, and otherdisk activities. If the console disk is heavily loaded, consoleperformance may suffer.

CC: 6-7-2

RS3: Alarm Management Hints for Alarm Management

ContentsRS3: Password Security


Chapter 7:Password Security

Section 1: Configuring Password Security 7-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Initial Password System Configuration 7-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configuring Factory-shipped Password System 7-1-2. . . . . . . . . . . . . . . . . . . . . . . . .

Logging in and Configuring Primary and Backup Nodes 7-1-3. . . . . . . . . . . . . . .Changing User and Login Names and Completing Configuration 7-1-4. . . . . . .

Defining Password Security with a Configuror’s Key 7-1-5. . . . . . . . . . . . . . . . . . . . .Configuring Primary and Backup Nodes 7-1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .Adding a System Manager 7-1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Logging In 7-1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System-wide Password Parameters 7-1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Defining System-wide Parameters 7-1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Saving the Console Configuration 7-1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .User Profile Directory 7-1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Plant Unit Access 7-1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Plant Unit Access and Plant Unit Configuration 7-1-15. . . . . . . . . . . . . . . . . . . . . . . . .Defining Plant Unit Access 7-1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing Plant Unit Access Definitions 7-1-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

User Name Detail Screen 7-1-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Adding Users to the Password System 7-1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing User Name Profiles 7-1-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing a Configuror to a System Manager 7-1-24. . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: Accessing a Password Secure System 7-2-1. . . . . . . . . . . . . . . . . . . . .

Logging on to the System 7-2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Changing a Password 7-2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Logging Off the Console 7-2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: Password Security Hints and Troubleshooting 7-3-1. . . . . . . . . . . . .

Scenario 1: Handling Primary and Backup Nodes 7-3-2. . . . . . . . . . . . . . . . . . . . . . . . . .Scenario 2: Using Passwords with Keylock and Secure Interfaces 7-3-3. . . . . . . . . . .Scenario 3: Using Passwords with a Standard KBI 7-3-4. . . . . . . . . . . . . . . . . . . . . . . . .Scenario 4: Using Key and Password Access 7-3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . .Scenario 5: Loss of $$PASSWD File 7-3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Scenario 6: Console Configuration File Not Found 7-3-7. . . . . . . . . . . . . . . . . . . . . . . . .

CC: ii

RS3: Password Security Contents

List of Figures

Figure Page


7.1.2 User Profile Directory 7-1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1.3 Plant Unit Access Screen 7-1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1.4 User Name Detail Screen 7-1-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1.5 Changing Configuror to System Manager 7-1-24. . . . . . . . . . . . . . . . . . . . . . . .

7.2.1 Login Screen 7-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.2 Changing a Password 7-2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iii

ContentsRS3: Password Security

List of Tables

Table Page

7.1.1 Console Configuration Screen Fields—Page 3 7-1-9. . . . . . . . . . . . . . . . . . . .

7.1.2 User Profile Directory Fields 7-1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1.3 Plant Unit Access Screen Fields 7-1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1.4 User Name Detail Screen Fields 7-1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.1 Login Screen Fields 7-2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: iv

RS3: Password Security Contents

CC: 7-1-1

RS3: Password Security Configuring Password Security

Section 1:Configuring Password Security

Console Access Levels

User privileges ensure that authorized users have appropriate access tothe RS3. The system grants users privileges based on job category, oraccess level.

For systems without password security, a key inserted in the base of theconsole identifies the user’s access level. For systems with passwordsecurity, login names and passwords give users access to the RS3 andidentify the user’s access level.

Figure 7.1.1 shows the different levels and the relationships betweenthem.

System Manager Privileges (password systems only)

Configuror Privileges

OperatorPrivileges

Recipe ManagerPrivileges

SupervisorPrivileges

RecipeManager Supervisor

Figure 7.1.1. Relationship Between Console Access Levels

An operator has only operator-specific privileges. A recipe manager anda supervisor both contain all of the privileges of an operator, but theprivileges specific to each of them do not intersect. The configuror hasaccess to all the privileges of recipe manager, supervisor, and operator.

The system manager level is available on systems with passwordsecurity. The system manager has access to all configuror privileges,and also is allowed to set up password security and to perform certaindisk and tape functions.

CC: 7-1-2


Password Security

Password security is a feature that gives the RS3 control system moreadaptability where tighter security is required.

One password system can handle up to 991 users. Each user is givenunique plant unit access. This password system provides an “electronicsignature” for each user and, in general, meets the requirements of asignature on paper.

The best way to use password security is to have a keyboard interfacewith no physical key for accessing the system. However, a keyboardinterface that allows use of the physical key can be configured forpassword security by following special instructions that are given onpage 7-1-6.

NOTE: See the RBL Manual for details on handling securityrequirements for batch applications.

This section explains the initial configuration process and the followingtasks that a system manager performs to maintain password security:

D Defining primary and backup disks for the $$PASSWD file that isstored in the Console Configuration folder.

D Defining user names, login names, and login and passwordupdate times.

D Defining plant unit access for each user.

Only a system manager can view and edit the following screens relatedto password security:

D User Profile Directory screen

D Plant Unit Access screen

D User Name Detail screen (This screen can also be viewed by aconfiguror.)

CC: 7-1-3


Initial Password System Configuration

You can receive an RS3 password-secure system in either of two ways:

If your system is being � then follow the directions in �

Shipped from the factory with a newkeyboard interface,

“Configuring Factory-shippedPassword System”, on page 7-1-3.

Upgraded from an existing system with aprevious version of the RS3 keyboardinterface,

“Defining Password Security with aConfiguror’s Key”, on page 7-1-6.

Configuring Factory-shipped Password System

New password systems from the factory include the following:

D A default $$PASSWD file on the hard disk

D A default configuration for the $$PASSWD file, which has theprimary and backup nodes set to “mynode”.

D A known login name and password.

CAUTION

In order to minimize the risk of losing the $$PASSWD file,be sure that you make a backup copy of the file that wasshipped with your system before you do any passwordsystem configuration.

Using the login name and password that is shipped with this system, adesignated system manager can log in and redefine the necessarydefaults. The following procedures allow you to complete this task:

D Log in.

D Configure primary and backup nodes.

D Change user and login names.

D Change password and complete initial configuration.

CC: 7-1-4


Logging in and Configuring Primary and Backup Nodes

- To log in:

1. From the command line, type

LI [ENTER]

2. Enter the login name and password that were shipped with yoursystem (login name = rs 3 and password = systest).

NOTE: You must type the login name and password exactly asthey are shown above; all login names and passwords arecase-sensitive.

- To configure primary and backup nodes:

CAUTION

The systems that you want to define as primary and backupshould be running during this initial set-up so that theconfiguration files can be saved to the appropriate disks.

1. To call up page 3 of the Console Configuration screen, type

CCC [ENTER] [PAGE AHEAD] [PAGE AHEAD]

2. Enter the name of a valid console node in the “Primary Volumefor $$PASSWD” field.

3. Enter the name of another valid console node in the “BackupVolume for $$PASSWD” field.

4. Save the console configuration, and copy it to all affectedconsoles.

For additional details about primary and backup nodes, see“Defining System-wide Parameters” on page 7-1-11.

CC: 7-1-5


Changing User and Login Names and Completing Configuration

- To change your user and login names:

1. On the command line, type

UND rs 3

The User Name Detail screen appears with the access leveldefined as SYSMGR. See “User Name Detail Screen” onpage 7-1-20.

2. Cursor to the “User Name” field; type your name (up to 32characters), and press [ENTER].

3. Cursor to the “Login” field; change “rs 3” to your login name (4 to16 characters); ensure that the access level is SYSMGR; andpress [ENTER].

The password is automatically reset to “Cleared”.

4. Type the following to save the $$PASSWD file:

[Ctrl] W

5. Cursor to the command line and log out by typing

LO [ENTER]

- To complete the initial configuration:


LI [ENTER]

2. Enter your new login name.

Because your password is currently “Cleared”, you areautomatically prompted to change it.

3. Cursor to the “OLD PASSWORD” field; and enter “Cleared”.

NOTE: You must type the password exactly as it is shown above;all passwords are case-sensitive.

4. Enter a new password with 6 to 16 characters.

5. Enter your new password again.

6. Delete the default $$PASSWD files from the nodes that are notprimary or backup.

You are now the system manager and can create plant unit access files(see page 7-1-15) and add new users (see page 7-1-20).

CC: 7-1-6


Defining Password Security with a Configuror’s Key

If you have an existing RS3, you can still set up and maintain passwordmanagement.

Using a configuror’s key in your existing keyboard interface, adesignated system manager can redefine your current system forpassword security. The following procedures included on this page andthe next allow you to complete this task:

D Configure primary and backup nodes.

D Add a system manager on the User Name Detail screen.

D Log in to the console.

Configuring Primary and Backup Nodes

- To configure primary and backup nodes:

CAUTION

The systems that you want to define as primary and backupshould be running during this initial set-up so that theconfiguration files can be saved to the appropriate disks.

1. To call up page 3 of the Console Configuration screen, type


2. Enter the name of a valid console node in the “Primary Volumefor $$PASSWD” field.

3. Enter the name of another valid console node in the “BackupVolume for $$PASSWD” field.

4. Save the console configuration, and copy it to all affectedconsoles.

For additional details about primary and backup nodes, see“Defining System-wide Parameters” on page 7-1-11.

CC: 7-1-7


Adding a System Manager

- To add a system manager:

1. As a configuror, call up the User Name Detail screen by typing

UND [ENTER]

The User Name Detail screen appears with the access leveldefined as SYSMGR. See “User Name Detail Screen” onpage 7-1-20.

2. Cursor to the “User Name” field; type your name (up to 32characters), and press [ENTER].

3. Cursor to the “Login” field; type your login name (4 to 16characters); ensure that the access level is SYSMGR; and press[ENTER].

The password is automatically reset to “Cleared”.

4. Type the following to save the $$PASSWD file.

[Ctrl] W

5. Reboot the console.

Following this reboot, the console operates as apassword-secure system and the physical keys no longerfunction.

CC: 7-1-8


Logging In

- To log in:


LI [ENTER]

2. Enter your new login name.

Because your password is currently “Cleared”, you areautomatically prompted to change it.

3. Cursor to the “OLD PASSWORD” field; and enter “Cleared”.

NOTE: You must type the password exactly as it is shown above;all passwords are case-sensitive.

4. Enter a new password with 6 to 16 characters.

5. Enter your new password again.

You are now the system manager and can create plant unit access files(see page 7-1-15) and add new users (see page 7-1-20).

CC: 7-1-9


System-wide Password Parameters

The Console Configuration screen, page 3, allows you to definesystem-wide password parameters that determine the following:

D Primary node for storing the $$PASSWD file.

D Backup node for storing the $$PASSWD file.

CAUTION

To minimize the risk of losing access to the $$PASSWD file,you must configure both primary and backup disks. It isrecommended that you also copy the consoleconfiguration containing the system-wide parameters to athird console and then configure additional primary andbackup volumes for storing the $$PASSWD file.

Figure 7.1.2 shows Page 3 of the Console Configuration screen, andTable 7.1.1 describes the fields. This screen can be viewed when noone is logged on to the console. Only a system manager can edit thefields on this screen; however, a configuror can edit the screen duringthe initial conversion from a keylock to a password system.

When a primary node goes down, the system automatically goes to thebackup node for the $$PASSWD file. After the primary node has beenrestored to operation, you must manually reset the console to look atthe primary node.

- To reset the console to its primary node:

1. Call up Page 3 of the Console Configuration screen as explainedin Figure 7.1.2.

2. Cursor to the field that shows the name of the “Current VolumeFor $$PASSWD”, and press [ENTER].

NOTE: If a primary or backup volume goes down, the name blinks inyellow on the Console Configuration screen. If you made any changesto the $$PASSWD file while either the primary or backup was notrunning, you must ensure that you are using the most recent file andthat the files on both nodes match. This requires that a system managermust delete the old file and copy the latest one to the appropriatenode(s).

CC: 7-1-10


CONSOLE CONFIGURATION 12-Mar-96 10:56:05

System-wide Password Management

Title For Login Screen *Fisher-Rosemount Systems, Inc.

Primary Volume For $$PASSWD *Node_88

Backup Volume For $$PASSWD *Node_88

Current Volume For $$PASSWD >Node_88

- To access the Console Configuration screen:D On the command line, type



Table 7.1.1. Console Configuration Screen Fields—Page 3


Title for Loginscreen Title for the system login screen.

Up to 40 alphabeticcharacters including

spaces

Primary VolumeFor $$PASSWD Primary drive where the $$PASSWD file resides.

Up to 10 alphanumericcharacters that match avalid disk drive name.

Backup VolumeFor $$PASSWD Backup drive where the $$PASSWD file also is used.


Current VolumeFor $$PASSWD Drive where the $$PASSWD file is currently being stored.


NOTE: A primary or backup name that is blinking in yellow indicates that this node has been out of serviceat some time since configuration.

CC: 7-1-11


Defining System-wide Parameters

The first step in setting up system-wide password management is todefine parameters on page 3 of the Console Configuration screen.

CAUTION

You must define the “Primary Volume for $$PASSWD” and“Backup Volume for $$PASSWD”. The other fields on thisscreen have default values that you do not have to change.

- To define the system-wide password parameters for eachconsole:

1. Log in as a system manager.

2. To call up page 3 of the console configuration screen, type


3. Cursor to the “Primary Volume for $$PASSWD” field, and enterthe name of a valid console node that you want to use for storingthe $$PASSWD file.

4. Cursor to the “Backup Volume for $$PASSWD” field, and enterthe name of a valid console node that you want to serve as abackup for storing the $$PASSWD file.

CC: 7-1-12


Saving the Console Configuration

- To save the Console Configuration:

1. To call up the Disk Activity screen, type

DD: [ENTER]

2. Cursor to the Console Configuration folder, and press [SELECT].

3. Cursor to the file containing the console configuration you wantto save, and press [ENTER].

The Disk Activity screen appears with Disk Console Save in the“Operation” field.

4. Cursor to the “Config Types” field; press [NEXT OPTION] until“All” appears, and then press [ENTER].

5. Cursor to the “Press Enter to Begin” field, and press [ENTER].

CC: 7-1-13


User Profile Directory

The User Profile Directory screen shown in Figure 7.1.3 allows asystem manager to view all users that have been defined in the systemand to move to the User Name Detail or Plant Unit Access screens for aselected user. This screen can be viewed only by a system managerwho is logged in.

The fields on this screen are a subset of those on the User Name Detailscreen and include the following, which are described in Table 7.1.2.

The User Profile Directory screen has two selectable areas for eachuser:

D User number through the access level fields

D PUA field

- To access the User Profile Directory:


UPD [ENTER]

2. To view additional users in the User Profile Directory, press[PAGE FORWARD] or [PAGE BACKWARD].

- To move to the Plant Unit Access screen from the User ProfileDirectory:

1. Locate the user whose plant unit access screen you want to view,and position the cursor anywhere on the PUA field.

2. Press [SELECT].

- To move to the User Name Detail screen from the User ProfileDirectory:

1. Locate the user whose User Name Detail screen you want toview, and position the cursor anywhere between the user numberand the access level fields.

2. Press [SELECT].

CC: 7-1-14


User Profile Directory 12-Mar-96 11:03:52

Login User Name Access PUA Filename26 oper 26 OPER27 oper 27 OPER OperPUA28 oper 28 OPER29 johnp John Powers CONFIG Configu PUA29 oper 29 OPER30 oper 30 temp OPER31 dave Dave Owen CONFIG ConfigPUA32 kents Kent Smith OPER33 annl Ann London OPER34 kenta Kent Anders SYSMGR SysMgrPUA35 donm Don Miller OPER36 joew Joe Wilson OPER373839

- To move to another part of theUser Profile Directory:

D Position cursor here, and type

user number [ENTER]

- To move to the User Detail screen for ahighlighted user:

D Place the cursor anywhere between the usernumber and the access level, and press[SELECT].

- To move to the Plant Unit Accessscreen for a highlighted user:

D Place the cursor anywhere on thePUA field, and press [SELECT].

- To access the User Profile Directory screen:D On the command line, type

UPD [ENTER]

- To move through the list of users in the UserProfile Directory:D Press [PAGE FORWARD] or [PAGE BACKWARD]

Figure 7.1.3. User Profile Directory

Table 7.1.2. User Profile Directory Fields

Field Description

(Column 1) User number

Login Name that user enters when logging in

User Name User’s full name

Access Defines level of system access (OPER, SUPER, CONFIG, SYSMGR, RCPM, NONE)

PUA filename Name of file that lists the plant units that this user can access.See “Defining Plant Unit Access” on page 7-1-15.

CC: 7-1-15


Plant Unit Access

The Plant Unit Access screen allows a system manager to create thefiles that define which plant units a user can operate.

Each console has its own plant unit configuration, which is combinedwith the plant unit access configuration to allow different operators tohave control of different parts of a plant.

The plant-unit access (PUA) information is stored in the $$PASSWD file.The same filename can be assigned to multiple users; however, nomore than 991 files (one for each user) can be defined.

NOTE: A PUA filename must have been configured on the Plant UnitAccess screen before you can enter it on the User Name Detail screen.The suggested procedure, therefore, is to create the necessary PUAfilenames before you add users to the password system.

CC: 7-1-16


Plant Unit Access and Plant Unit Configuration

The Plant Unit Access file provides the same basic functionality as thePlant Unit Configuration:

D Each console has a Plant Unit Configuration (PUC) that specifieswhich plant units send alarms to that console.

D Each operator has a Plant Unit Access (PUA) filename thatspecifies which plant units send alarms to that operator.

The Plant Unit Configuration and Plant Unit Access information mustboth show ownership of a particular plant unit before an operator canmodify blocks or acknowledge alarms for that plant unit:

If the operatorPUA specifies �

and the consolePUC specifies �

then this operator at this console cansee and ack alarms for �

1 -- 10 1 -- 30 1 -- 10

15 -- 30 1 -- 30 15 -- 30

10 -- 40 15 -- 30 15 -- 30

CAUTION

The Plant Unit Configuration and Plant Unit Accessinformation work together to define which alarms can beacknowledged by a particular operator at a particularconsole. If an alarm from plant unit 15 (based on the firstexample above) is on the banner line when the operatorlogs in, that operator cannot acknowledge the alarm on thebanner line. That acknowledgement must be done by anoperator at a console where both the PUC and operatorPUA include plant unit 15.

CC: 7-1-17


Defining Plant Unit Access

Figure 7.1.4 and Table 7.1.3 explain the fields on this screen that can beviewed and changed only by a system manager. An asterisk to the rightof a plant unit number indicates that this plant unit has been enabled fora user or users who have been associated with this file.

- To define a new plant-unit access file:

1. With system manager access, call up the Plant Unit Accessscreen, by typing

PUA [ENTER]

The screen appears a shown in Figure 7.1.4.

2. Cursor to the “PUA filename” field; enter a valid filename, andpress [ENTER].

3. Configure the plant units that users with this PUA filename canaccess by doing one of the following:— Cursor to each plant unit that this user should be able to

access, and press [ENTER].— Cursor to the “Set range” field, enter two numbers separated

by a comma, and then press ENTER].— Clear an enabled field by pressing [ENTER] again on a plant

unit number or by entering values in the “Clear range” field.

4. To save the $$PASSWD file after you enter appropriate values inall necessary fields, type

[Ctrl] W

CC: 7-1-18


Plant Unit Access 15-Mar-96 13:20:25

PUA Filename > OperPUA

1 17 33 49 65 81 97 113 129 145 161 177 193 209 225 2412 18 34 50 66 82 98 114 130 146 162 178 194 210 226 2423 19 35 51 67 83 99 115 131 147 163 179 195 211 227 2434 20 36 52 68 84 100 116 132 148 164 180 196 212 228 2445 21 37 53 69 85 101 117 133 149 165 181 197 213 229 2456 22 38 54 70 86 102 118 134 150 166 182 198 214 230 2467 23 39 55 71 87 103 119 135 151 167 183 199 215 231 2478* 24 40 56 72 88 104 120 136 152 168 184 200 216 232 2489 25 41 57 73 89* 105 121 137 153 169 185 201 217 233 24910 26 42 58 74 90 106 122 138 154 170 186 202 218 234 25011 27 43 59 75 91 107 123 139 155 171 187 203 219 235 25112 28 44 60 76 92 108 124 140 156 172 188 204 220 236 25213 29 45 61 77 93 109 125 141 157 173 189 205 221 237 25314 30 46 62 78 94 110* 126 142 158 174 190 206 222 238 25415 31 47 63 79 95 111 127 143 159 175 191 207 223 239 25516 32 48 64 80 96 112 128 144 160 176 192 208 224 240

Set Range > Clear Range >

- To access the Plant Unit Access screen:D On the command line, type

PUA [filename] [ENTER]

Indicates that the user who is assigned thisPUA filename can access Units 8, 89, and 110.

- To move through plant unit access files in theorder in which they were created:

D Press [PAGE FORWARD] or [PAGE BACKWARD]

Figure 7.1.4. Plant Unit Access Screen

Table 7.1.3. Plant Unit Access Screen Fields


PUA filenameFile name associated with a particular user to definewhich plant units that user can access.

A maximum of 991 filenames can be defined.

Up to 9 alphabeticcharacters

Plant units Asterisks indicate which units this user can access. Press [ENTER] to toggleasterisk on and off.

Set range Allows you to specify a range of plant units to enable forthis user. 1 to 255*

Clear range Allows you to specify a range of plant units to disablefor this user. 1 to 255*

* To specify a range of values, enter two numbers separated by a comma and press [ENTER]: “3,55”[ENTER].

CC: 7-1-19


Changing Plant Unit Access Definitions

Plant unit access definitions cannot be deleted, but the filename andplant unit assignments can be changed.

- To change information in an existing Plant Unit Access file:

1. With system manager access, call up the Plant Unit Accessscreen and do one of the following:— On the command line, type

PUA filename [ENTER]— In the User Profile Directory, cursor to the name of the file you

want to change, and press [SELECT].

2. To clear any previously enabled plant units, do one of thefollowing:— Cursor to a plant unit marked with an asterisk that you do not

want this user to access, and press [ENTER].— Cursor to the “Clear range” field; enter a single number or two

numbers separated by a comma, and then press ENTER].

3. To enable the appropriate fields, do one of the following:— Cursor to each plant unit that this user should be able to

access, and press [ENTER].— Cursor to the “Set range” field; enter a single number or two

numbers separated by a comma, and then press ENTER].

4. To cancel changes and recall the original plant unit accessconfiguration, type

[Ctrl] R


[Ctrl] W

CC: 7-1-20


User Name Detail Screen

The User Name Detail screen shown in Figure 7.1.5 allows a systemmanager to add users to the password management system. Thisscreen can be edited only when a system manager is logged in, but itcan be viewed by a configuror.

- To access the User Name Detail screen:D On the command line, type

UND [login_name] [ENTER]

- To move through user name detail screens innumerical order:

D Press [PAGE FORWARD] or [PAGE BACKWARD]

User Name Detail 12-Mar-96 10:41:34

Number *1 Fisher-Rosemount Systems, Inc.

User Name *Joe Brown

Login Name *Joeb

Access *SYSMGR GLOBAL SYSTEM PARAMETERS

PUA Filename *SYSMGRPUA Password

Login/Logout Times Change Required Every *10 Days

Days *any Change not allowed for *0 Days

Start/End Time *00:00 *00:00 hh:mm Inactive User Logout *00:00 hh:mm

Inactive User Logout *00:00 hh:mm NEW SYSMGR:

Password *Cleared Raise to SYSMGR: (press ENTER)

Last Change 02-Jul-96 11:04:10

Next Change 12-Jul-96 11:04:10

Figure 7.1.5. User Name Detail Screen

CC: 7-1-21


Table 7.1.4. User Name Detail Screen Fields

Field Description Allowable Entries *

Number User number that is automatically assigned when a useris added; a value can be entered in this field to call upthe User Name Detail screen for the user who wasassigned that particular number.

1 to 991

User Name User’s full name Up to 32 alphanumericcharacters

(spaces are allowed)

Login Name Name that user enters when logging into the console. 4 to 16 alphanumericcharacters

(spaces allowed)

Access Defines level of system access NONE, OPER, SUPER,RCPM, CONF, SYSMGR

PUA Filename Name of file that lists the plant units that this user canaccess.

See “Defining Plant Unit Access” on page 7-1-15.

Up to nine alphanumericcharacters that represent

an existing file.

Login/Logout Times

Days Indicates the days of the week that this user is allowed tolog in. You can indicate the days in a list separated bycommas (Mon, Wed, Fri) or as a range (Mon--Thu); oryou can press [ENTER] to indicate “any”.

Mon, Tue, Wed, Thu, Fri,Sat, Sun, any

Start/End Time Indicates the hours during which the user is allowed tolog in; this assumes that the user works the same hourseach day.

00:00 to 23:59

Inactive UserLogout

Indicates how long the console can remain untouchedbefore the user is automatically logged out.

00:00 means that a user is never logged out. The defaultis based on the GLOBAL SYSTEM PARAMETER,Inactive User Logout on the right-hand side of thisscreen.

00:01 to 23:59

Password Indicates the status of this user’s password; one of thefollowing appears in the field:

D “Valid Password” indicates that this user hasdefined a password.

D “Cleared” indicates that this is a new user who hasnever defined a password or one who hasforgotten a password and needs to define a newone.

D “Canceled” indicates that this user is no longerallowed to log in.

Canceled, Cleared

Last Change Indicates last time this user changed his/her password. Display only

* Bold indicates the default value.


CC: 7-1-22


Table 7.1.4. User Name Detail Screen (continued)Fields

Field Allowable Entries *Description

Next Change Indicates when this user must change his/her password;this field appears only if value in “Change RequiredEvery” field is greater than 0.

Display only

GLOBAL SYSTEM PARAMETERS

Password

ChangeRequired Every

Indicates how often passwords must be changed. Thedefault, 0, indicates that passwords never have to bechanged.

0 to 365 days

Change notallowed for

Indicates how long any password must be in effectbefore it can be changed; that is, another passwordchange is not allowed for this period of time. This valuecannot be greater than the “Change Required Every”field.

0 to 365 days

Inactive UserLogout

Indicates how long the console can remain untouchedbefore the user is automatically logged out.

Default value, 00:00, means that a user is never loggedout. The value entered in this field determines the defaultfor all users.

0:01 to 23:59

NEW SYSMGR The following fields are used only when a configuror mustbe redefined as a system manager.

D Raise to SYSMGR: (press ENTER)

D Additional userD Password

See “Changing Configurorto System Manager” on

page 7-1-25 for additionalinformation.

* Bold indicates the default value.

CC: 7-1-23


Adding Users to the Password System

Only a system manager can add users to the system from the UserName Detail screen. The information on this screen is stored in the$$PASSWD file in the Console Configuration folder.

You define the following fields for each user:

D User Name

D Login

D Access level: OPERATOR, SUPER, RCPM, CONFIG, orSYSMGR

D Optional name of file containing plant unit access

All other fields on the User Name Detail screen have default values and,therefore, do not require additional entries.

- To add a new user to the system:

1. With system manager access, call up the User Name Detailscreen, by typing

UND [ENTER]

The User Name Detail screen, and the next available usernumber is automatically assigned.

2. Cursor to the “User Name” field, and enter up to 32 characters.

3. Cursor to the “Login Name” field, and enter between 4 and 16characters that this user can use to log in.

4. Cursor to the “Access” field; press [NEXT OPTION] until theappropriate access level appears; and then press [ENTER].

5. Cursor to the “PUA Filename” field, and enter up to 9 charactersthat define the name of a file containing this user’s plant-unitaccess privileges.

6. Cursor to other fields that you want to define, and enterappropriate values as listed in Table 7.1.4.


[Ctrl] W

CC: 7-1-24


Changing User Name Profiles

Once assigned a user number, a user can never be specifically deletedfrom the system. You can deny someone future access to the system,by setting the password to “Canceled”, or you can change a user nameto reassign a particular user number to someone else.

- To change information on the User Detail screen:

1. With system manager access, call up the User Name Detailscreen and do one of the following:— On the command line, type

UND login_name [ENTER]— In the User Profile Directory, cursor to the name of the user

whose profile you want to change, and press [SELECT].

2. Cursor to the fields as explained on page 7-1-23, and enter theappropriate values for fields that you want to modify.

3. To remove changes and recall the original user profile, type

[Ctrl] R


[Ctrl] W

CC: 7-1-25


Changing a Configuror to a System Manager

If an existing system manager is unavailable, it may be necessary toassign system manager privileges to another user. The access level ofan existing configuror can be raised to a system manager under thefollowing conditions:

D The configuror is currently logged in.

D Another configuror or supervisor is available to approve thechange.

Such a change is only temporary unless as a system manager, theconfiguror changes the access level on his or her user name detailscreen and saves that configuration to the $$PASSWD file. If thechange is not permanently made to the $$PASSWD file, the systemmanager status is valid only as long as the configuror is logged in.

NEW SYSMGR:

Raise to SYSMGR: (press ENTER)

Additional User >

Password

Cursor to “Raise toSYSMGR” field, andpress [ENTER].

User Name Detail 12-Mar-96 10:41:34

Number *1 Fisher-Rosemount Systems, Inc.

User Name *Joe Brown

Login Name *Joeb

Access *SYSMGR GLOBAL SYSTEM PARAMETERS

PUA Filename *SYSMGRPUA Password

Login/Logout Times Change Required Every *0 Days

Days *any Change not allowed for *0 Days

Start/End Time *00:00 *00:00 hh:mm Inactive User Logout *00:00 hh:mm

Inactive User Logout *00:00 hh:mm NEW SYSMGR:

Password *Valid Password Raise to SYSMGR: (press ENTER)

Last Change 02-Jul-96 11:04:10

Figure 7.1.6. Changing Configuror to System Manager

CC: 7-1-26


- To change a configuror to a system manager:

1. As a configuror, log in to the system and call up the User NameDetail screen, by typing

UND (your_login_ name) [ENTER]

NOTE: You can raise yourself to a system manager from anyUser Name Detail screen.

2. With another configuror or supervisor immediately available,cursor to the “Raise to SYSMGR: (press ENTER)” field; andpress [ENTER].

3. Cursor to the “Additional User” field, and allow the otherconfiguror or supervisor to enter his or her name.

4. Cursor to the “Password” field, and allow the other configuror orsupervisor to enter his or her password.

The configuror who was originally logged in now has the accesslevel and privileges of a system manager until he or she logs off.

- To make the system manager access level permanent:

1. Cursor to the “Access Level” field on the User Name Detailscreen for the new system manager.

2. Press [NEXT OPTION] until SYSMGR appears, and then press[ENTER].

3. Cursor to any other fields that need updating, and make thenecessary changes.

4. To save the $$PASSWD file after updating the appropriate fields,type

[Ctrl] W

The configuror who was originally logged in now has permanentsystem manager status.

NOTE: If you move to the User Name Detail screen for the configurorwho has been raised to a SYSMGR, the access level is highlighted inyellow. The access level for such a configuror is also highlighted inyellow on the User Profile Directory.

CC: 7-2-1

RS3: Password Security Accessing a Password Secure System

Section 2:Accessing a Password Secure System

This section explains how all users can gain access to a passwordsecure RS3 distributed control system.

The login process differs slightly depending on the console state:

D A cold login occurs if the console is initializing with an existing$$PASSWD file after a reboot or power-up situation. Followingthe entry of a valid login name and password, the consoledisplays the Menu Command Console screen.

D A warm login occurs after a user has logged off a console that isstill in a normal operating condition. Following the entry of a validlogin name and password, the last screen that the previous userwas viewing appears; however, if a system manager was the lastone logged in, the Menu Command Console screen is displayed.

CAUTION

If you press the [CRT] button to move to another console,your privileges become those of the person logged in tothat console.

CC: 7-2-2


Logging on to the System

The Login screen shown in Figure 7.2.1 allows you to log into thesystem based on additional criteria:

D If “Automatic Update” for the system is set to “Yes” and thatupdate time has expired, you are prompted to define a newpassword before gaining access to the console.

D If you have a login that is restricted by days and hours, thesystem verifies the current time before allowing you to access theconsole.

D If your password has been set to “Canceled” and you attempt tolog in, you receive a “Login Incorrect” message and cannotaccess the console.

Table 7.2.1 explains the fields on the Login screen.

- To log in to the console:


LI [ENTER]

NOTE: The name of the last person logged in automatically appears inthe “Login” field; however, if this person has a time-restricted login, the“Login” field becomes blank.

2. Cursor to the “Login” field; type your login name as defined bythe system manager, and press [ENTER].

3. Type your password, and press [ENTER].

CC: 7-2-3


Change Password 12-Mar-96 10:47:51

Fisher-Rosemount Systems, Inc.

Login

Password :

Silence Horn: (press ENTER)

Copyright E 1981-1994 Fisher-Rosemount Systems, Inc.

- To access the Login screen:D On the command line, type

LI [ENTER]

Figure 7.2.1. Login Screen

Table 7.2.1. Login Screen Fields


LoginValid login name for this user.NOTE: If the user was the last one logged into this console, noentry in the “Login” field is required.

4 to 16alphanumericcharacters

Password

Valid password for the user whose name was entered in the“Login” field.

NOTE: The password is case sensitive. If you are logging infor the first time, you must type “Cleared” in upper and lowercases as shown here.

6 to 16alphanumericcharacters

Silence Horn:(press Enter)

Allows user to silence the horn generated by alarms that haveoccurred while no one is logged onto the console.

NOTE: Pressing [ENTER] on this field has the same effect aspressing [ACK] the first time to silence an alarm; pressing[ACK] after you log in actually acknowledges the alarm.

[ENTER]

Next PasswordUpdate Indicates next time that you must change your password. Display only

CC: 7-2-4


Changing a Password

Changing a password involves three basic steps:

D Confirming your old password

D Entering a new password

D Verifying the new password by entering it a second time.

The following situations allow (or require) you to change your password:

D You are logged onto the system and know that you must updateyour password before you log on again.

D Your password is defined as “Cleared”.

D You are logged off and the password update time has passed.

In the first situation, you can begin changing your password from thecommand line. In the other two situations, you are prompted to changeyour password when you attempt to log in.

Change Password 12-Mar-96 10:47:51

Login SYSMGR

Old Password :

Login SYSMGR

New Password :

Login SYSMGR

Repeat Password :

Figure 7.2.2. Changing a Password

CC: 7-2-5


- To change a password while logged onto the console:


CUP [ENTER]

The Login screen appears as shown in Figure 7.2.2.

2. Cursor to the “OLD PASSWORD” field; type the currentpassword, and press [ENTER].

The field changes to “NEW PASSWORD”.

3. Type a new password with 6 to 16 characters, and press[ENTER].

The field changes to “REPEAT PASSWORD”.

4. Type the new password again, and press [ENTER].

If both entries (Steps 2 and 3) match, the console recalls thedisplay that was on the screen before you issued the “CUP”command.

- To change a password without first logging onto the console:


LI [ENTER]

The Login screen appears with a message that indicates thepassword must be updated.

2. Cursor to the “OLD PASSWORD” field; type the currentpassword, and press [ENTER].

The field changes to “NEW PASSWORD”.

3. Type a new password with 6 to 16 characters, and press[ENTER].

The field changes to “REPEAT PASSWORD”.

4. Type the new password again, and press [ENTER].

If both entries (Steps 2 and 3) match, the console recalls thedisplay that was on the screen.

CAUTION

If the backup node for the $$PASSWD file is down whenyou change your password, you should contact the systemmanager to copy the file from the primary to the backupnode.

CC: 7-2-6


Logging Off the Console

Logging off a console can occur in one of two ways:

D If you are assigned an automatic log off, the system logs you offif the console remains untouched for the period of time specifiedon your User Name Detail screen.

D You can log yourself off the console from the command line.

- To log off the console:

D From the command line, type

LO [ENTER]

The Login screen appears and the user name on the bottom lineof the screen is “NO USER”.

CC: 7-3-1

RS3: Password Security Password Security Hints and Troubleshooting

Section 3:Password Security Hints and Troubleshooting

This section describes some security situations and explains how tohandle them using the password management system. Five scenariosare described with suggested solutions and preventive measures.

The following general guidelines are suggested to maintain the integrityof your password management system.

D Configure more than one set of primary and backup nodes forstoring the $$PASSWD file.

D Make regular backups of files in your console configurationfolder, especially the $$PASSWD file.

D Store a spare configuror’s key and standard keyboard interface(KBI) in a restricted area; this keyboard can then be used if noother means of access is available.

CC: 7-3-2


Scenario 1: Handling Primary and Backup Nodes

Situation:

On a system using only secure keyboard interfaces, the primary andbackup nodes disappear.

Result:

The password file can no longer be accessed and no one can log onto the system. If no one is currently logged in and only one set ofprimary and backup nodes were defined, nothing can be done.

Preventive Measures:

To minimize the risk of this situation ever occurring, do one of thefollowing:

- Maintain a tape backup of the latest $$PASSWD file.

- Define a second set of primary and backup nodes.

CAUTION

If you define a second set of primary and backup nodes,you must ensure that all $$PASSWD files are alwaysidentical.

- Maintain a spare standard KBI with a configuror’s key.

1. See Scenario 2, 7-3-3 for the initial steps in correcting theproblem.

2. When everything is backed up and running, remove the standardKBI and replace it with the secure keyboard interface.

Correction:

If and only if a configuror or system manager is logged in, he or shecan replace the file from tape.

- To reload tape:

1. If a configuror is logged in, raise the configuror to a systemmanager. (See Section 1, 7-1-25).

2. Replace the $$PASSWD file from tape, and then reconfigure theprimary and backup nodes.

NOTE: If a console using the standard KBI has power cycled and theprimary and backup volumes cannot be found, then this console willcome up as a keylock system. Using a secure KBI will not generate thisproblem although you will not be able to log in.

CC: 7-3-3


Scenario 2: Using Passwords with Keylock and SecureInterfaces

Situation:

A system has both a keylock and secure keyboard interface. Howcan this system be made as secure as possible?

Solution:

You can configure standard KBI keyboards to operate with passwordsecurity.

- To configure a system with both keylock and secure keyboardinterfaces.

1. On page 3 of the Console Configuration screen, specify consoleswith the secure keyboard interface as primary and backup nodes.

Note: You may need to perform this configuration using aconfiguror’s key on a system with the standard KBI.

2. Ensure that all consoles (including those with a standard KBI)specify primary and backup nodes that use the secure keyboard.

3. On the “User Name Detail” screen, define a system manager byentering at least one login name (the first name entered is alwaysdefined with system manager access).

4. Reboot all consoles.

All consoles are now set up for login access only.

CC: 7-3-4


Scenario 3: Using Passwords with a Standard KBI

Situation:

A system has only keyboards with the standard KBI. How can youuse this system as a secure password system?

Solution:

You can configure the standard KBI to use passwords instead ofkeys.

- To configure a standard KBI for password security:

1. Using the configuror’s key, modify page 3 of the ConsoleConfiguration screen to specify primary and backup nodes for the$$PASSWD file.

2. On the “User Name Detail” screen, define a system manager byentering at least one login name (the first name entered is alwaysdefined with system manager access).

3. To save the $$PASSWD on the primary and backup nodes, type

[Ctrl] w

4. Configure all consoles with these same primary and backupnodes, and then reboot each console.

The system returns with a login screen, and the access levelis set to ‘NO USER’. You can now log in with SYSMGRaccess, change your password, add additional users, etc.

CC: 7-3-5


Scenario 4: Using Key and Password Access

Situation:

A system uses key access on some consoles and password accesson others. How can this system be made as secure as possible?

Result:

Very little can be done to provide limited access when keys are stillavailable.

Solution:

You have two possible means of providing better security.

- To configure all keyboards to serve as a password system:

D See Scenario 2, 7-3-3.

- To restrict use of the consoles with standard KBIs:

1. Use the consoles with a standard KBI in restricted areas wherefewer people have access to them.

2. Use the password consoles in more generally accessible areas.

CC: 7-3-6


Scenario 5: Loss of $$PASSWD File

Situation:

The $$PASSWD file is lost.

Solution:

Recovery of the $$PASSWD file depends on the overall systemconfiguration:

- To retrieve the $$PASSWD file in a system in which only securekeyboard interfaces are used and a system manager waslogged in:

D Restore the file from tape as explained in Scenario 1, 7-3-2.

- To retrieve the $$PASSWD file in a system in which onlystandard KBIs are used:

1. Reboot the console.

2. Insert the configuror’s key.

3. Restore the file from tape as explained in Scenario 1, 7-3-2.

CC: 7-3-7


Scenario 6: Console Configuration File Not Found

Situation:

A console has power cycled and cannot find its consoleconfiguration file.

D If this console is using a standard KBI, it will come up as akeylock system.

D If this console is using a secure KBI and was not configured as aprimary or backup volume for the $$PASSWD file, no one can login.

NOTE: To determine if the console configuration file cannot befound, check page one of the Console Configuration screen to see ifthe name of the console configuration file appears in yellow.

Solution:

- To retrieve the $$PASSWD file:

1. Log in as system manager to another console and copy the$$PASSWD file to the console that could not find its consoleconfiguration file.

2. If using a secure keyboard interface, log in to the console whichwill then use this new copy of the $$PASSWD file;

or

If using a standard KBI, reboot the console and then log in.

3. Load the console with the correct console configuration file.

CC: 7-3-8


ContentsRS3: Commands


Chapter 8:Commands

Section 1: Introduction to Commands 8-1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Symbols Used 8-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 2: SMS Commands 8-2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 3: MTCC Commands 8-3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section 4: Hints for Using Commands 8-4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CC: ii

RS3: Commands Contents

List of Tables

Table Page

8.1.1 Symbols Used in Command Lines 8-1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2.1 SMS Commands that Call Up Screens 8-2-2. . . . . . . . . . . . . . . . . . . . . . . . . .

8.2.2 SMS Commands that Perform Operations 8-2-7. . . . . . . . . . . . . . . . . . . . . . .

8.3.1 MTCC Commands that Call Up Screens 8-3-2. . . . . . . . . . . . . . . . . . . . . . . . .

8.3.2 MTCC Commands that Perform Operations 8-3-10. . . . . . . . . . . . . . . . . . . . .

CC: 8-1-1

RS3: Commands Introduction to Commands

Section 1:Introduction to Commands

Commands on the MTCC and SMS are used to call up screens andperform operations. Commands are entered on the command line,which is the top line of the CRT screen.

The commands that can be entered on the SMS are shown inTable 8.2.1 and Table 8.2.2. The commands that can be entered on theMTCC are shown in Table 8.3.1 and Table 8.3.2.

The Entry column in the command tables lists the keyboard entries thatmust be made on the command line to call up the desired screen or toperform the desired operation.

Table 8.1.1 explains the symbols and text used in the command tables.

CC: 8-1-2

RS3: Commands Introduction to Commands

Symbols Used

Special symbols and text are used to describe what keyboard entriesyou need to make. Table 8.1.1 provides explanations of the symbolsand text.

Table 8.1.1. Symbols Used in Command Lines

Symbols or Text Explanation

DD:Uppercase and/orbold letters

Indicates that the entry is mandatory.For example, you must type DD: to call up the DiskDirectory.

( ) ParenthesesIndicates that the entry is optional.For example, (node# : drive #) means that you canoptionally type the node number and drive number.

[ ] BracketsIndicates that the text represents a single key.For example, [ENTER] means press the ENTER key;[R] means press the R key.

tag Italic

Indicates that the text represents one or more characters.For example, (area name) means type in an area name;(volume or node #) means enter the volume name or thenode number.An entry that is both in bold and italics indicates the entryis mandatory and variable in characters.

spIndicates the space bar.This is a special notation that represents the space bar.For example, [sp].

CC: 8-2-1

RS3: Commands SMS Commands

Section 2:SMS Commands

This section provides the list of commands that can be entered on theSMS.

Table 8.2.1 lists the commands that call up screens. Table 8.2.2 lists thecommands that perform operations.

CC: 8-2-2


Table 8.2.1. SMS Commands that Call Up Screens

Screen Called Up Entry Command Line Text

Alarm and Event Lists

Active Batch Alarms BAAA [ENTER] BATCH Active Alarms

Alarm Annunciation AAC [ENTER] Alarm Annunciation Cnf:

Active Hardware Alarms HA [ENTER] Hardware Active Alarms

Active Process Alarms AAL [ENTER] Alarm Active List

Active Process Alarms PA [ENTER] Process Active Alarms

Active Suppressed Alarms ASA [ENTER] Alarm Suppressed Actv

Active System Status SSA [ENTER] System Status Active

Advisory Active Alarms ADAA [ENTER] ADV Actv Alrms

Advisory Cleared Alarms ADCA [ENTER] ADV Clrd Alrms

Cleared Batch Alarms BACA [ENTER] BATCH Cleared Alarms

Cleared Hardware Alarms HC [ENTER] Hardware Cleared Alarms

Cleared Process Alarms PC [ENTER] Process Cleared Alarms

Cleared Suppressed Alarms ASC [ENTER] Alarm Suppressed Clrd

Cleared System Status SSC [ENTER] System Status Cleared

Critical Active Alarms CRAA [ENTER] CRIT Actv Alarms

Critical Cleared Alarms CRCA [ENTER] CRIT Clrd Alarms

Disk Event List DEL [ENTER] Disk Event List

Event List EL: (event list#) [ENTER] Event List:

Plant Area (ACTV) AN: [area name] [ENTER] Area Name:

Plant Area (ACTV) AAA (area name) [ENTER] Actv Area Alms:

Plant Area (CLRD) CAA [area name] [ENTER] Clrd Area Alms:

Alarms and Events

Alarm Configuration AC [ENTER] Alarm Configuration

Alarm List Configuration ALC [ENTER] Alarm List Configuration

Alarm Log Display ALD (alarm log filename) [ENTER] Alm Log Disp:

Alarm Log Display ALS (log display configuration name)[ENTER] Alm Log Search:

Configure Alarm Broadcast CAB [ControlFile node#] [ENTER] Cnfg Alarm Broadcast

CC: 8-2-3


Table 8.2.1. SMS Commands that Call Up Screens (continued)

Screen Called Up Command Line TextEntry

Alarms and Events (continued)

Event List Configuration ELC [ENTER] Event List Configuration

Log Display Configuration LDC [ENTER] Log Display Config:

Alarm Areas

Area Name Configuration ANC [ENTER] Area Name Config:

RBLC

RBL Directory (RBL) RBLD (node# or volume name)[ENTER] RBL Directory:

RBL File Transfer FT [ENTER] File Transfer

RBL File Contents (RBL)RBLF (volume , filename) [ENTER]or

RBLF (node#, filename) [ENTER]RBL File Contents:

RBLC Monitor RBLM (block tag or address)[ENTER] RBLC Monitor

RBLC ScriptRBLS (volume , filename) [ENTER]or

RBLS (node#, filename) [ENTER]RBLC Script:

Block

Block Directory CBD: (Controller Processor address)[ENTER] Cont Block Directory:

Block Print Setup BP [ENTER] Block Print

Block References BR (tag or address) [ENTER] Block References:

Block Status CBS (Controller Processor address)[ENTER] Cont Block Status:

Continuous Diagram BD (tag or address) [ENTER] Block Diagram:

Continuous Faceplate BF (tag or address) [ENTER] Block Faceplate:

Continuous Links BL (tag or address) [ENTER] Block Links:

Group Display screen or CBContinuous Faceplate TA (tag or address) [ENTER] Tag/Address:

Callup Buttons

Alarm Annunciation AAC (command#) [ENTER] Alm Annunciation Cnf:

Callup Buttons CCB (option keyboard#) [ENTER] Config Callup Buttons

CC: 8-2-4




Callup Buttons (continued)

Calls up the screen orperforms the operation thatis assigned to a callupbutton.

CUB: [button#] [ENTER] Call Up Button:

Display Buttons CDB (button#) [ENTER] Config Display Buttons:

Color

Color Configuration CCU [ENTER] Config Color Usage

Master Color Selection CCP [ENTER] Config Color Palette

Console Configuration

Console Configuration CCC [ENTER] Config Command Console

Console Menu

Menu Command Console MCC [ENTER] Menu Command Console

ControlFile and I/O

ControlFile Dump CFD node# or ControllerProcessor# [ENTER] Cont File Dump:

ControlFile Dump or NodeDump ND node# [ENTER] Node Dump:

ControlFile Links CFL (ControlFile#) [ENTER] Cont File Links:

ControlFile Status CFS (ControlFile#) [ENTER] Cont File Status:

Field I/O Status FS (Controller Processor address)[ENTER] Field I/O Status:

Transmitter Maint LogTL (volume , filename) [ENTER] orTL (node#, filename) [ENTER]

Trans Log:

Diagnostics

Background Diagnostics MCT [ENTER] Menu Confidence Tests

Memory Dump MD node#, (filename) [ENTER] Memory Dump

Memory View MV [ENTER] Memory View

Diogenes Interface

Diogenes I/F Configuration CDI (node#) [ENTER] Configure Diogenes I/F:

CC: 8-2-5




Disk and File

Calls up specified file DDF [ENTER] Disk Dir File:

Configure Download ScriptCDS (volume , filename) [ENTER]or

CDS (node#, filename) [ENTER]Cfg Dnld Script:

Disk Activity (last screen) DA [ENTER] Disk Activity

Disk Directory DD: (node#: drive#) [ENTER] Disk Dir:

Disk Directory PeerWay DDP [ENTER] Disk Dir PeerWay

Disk Folder Configuration DC: (node#) [ENTER] Disk Configure:

HIA

Configure HIA CH (node #) [ENTER] Config HIA:

Login

User Name Detail UND (login_name) [ENTER] User Name Detail

Plant Unit Access PUA (filename) [ENTER] Plant Unit Access

User Profile Directory UPD [ENTER] User Profile Directory

Login CUP [ENTER] Change User Password

Login LI [ENTER] Log In :

Log out LO [ENTER] Log Out :

Message Pairs

STD Message Pairs MPS [ENTER] Message Pairs Std

User Message Pairs MPU [ENTER] Message Pairs User

Operating Displays

Group G: (group number) [ENTER] Group:

Group Directory GD: [ENTER] Group Directory:

Overview O: (overview number) [ENTER] Overview:

Overview Directory OD: [ENTER] Overview Directory:

Unit U: (unit number) [ENTER] Unit:

Unit Directory UD: [ENTER] Unit Directory:

CC: 8-2-6




Operator Log

Operator Change Log OL [ENTER] Operator Log

PeerWay and Plant

PeerWay Node PN (node#) [ENTER] PeerWay Node:

PeerWay Overview PO (PeerWay#) [ENTER] PeerWay Overview:

PeerWay Performance PP [ENTER] PeerWay Performance

Plant Status PS (node#) [ENTER] Plant Status:

Plant Unit Configuration PUC [ENTER] Plant Unit Configuration

Plant Configuration Backup

Backup Plant Config BUP [ENTER] BackUp Plant Config

PLC

Configure PLC CP [ENTER] Configure PLC:

RFI

Configure RFI CR: (node#) [ENTER] Configure RFI:

RNI

Configure RNI CRN (node#) [ENTER] Configure RNI:

RNI Status CRN (node#) [ENTER][EXCHANGE] Configure RNI:

SCI

Configure SCI CS (node#) [ENTER] Configure SCI:

Tuning Displays

Tuning Display TD: (tuning display#) [ENTER] Tuning Display

Tuning Display Directory TDD [ENTER] Tuning Display Directory

VAX

Host Mode HM (node#) [ENTER] Hostmode:

VAX RPQNA Status Display VS (node#) [ENTER] VAX Status:

CC: 8-2-7


Table 8.2.2. SMS Commands that Perform Operations

Operation Performed Entry Command Line Text

Alarm and Event Lists*

Active Process AlarmsList—PrintCleared Process AlarmsList—Print

P [sp] PA [ENTER] Pr Process Alarm List

Active Process AlarmsList— PrintCleared Process AlarmsList—Print

P [sp] AA [ENTER] Pr Alarm Active List

Active System StatusAlarmsList—PrintCleared System StatusAlarms List—Print

P [sp] SSA [ENTER] Pr System Status Active

Active Hardware AlarmList—PrintCleared Hardware AlarmList—Print

P [sp] HA [ENTER] Pr Hardware Alarm List

Active Batch AlarmsList—PrintCleared Batch AlarmsList—Print

P [sp] BA [ENTER] Pr BATCH Alarm List

Disk Event List—Print P [sp] DEL [ENTER] Pr Disk Event List

Event List—Print P [sp] EL [:] event list# [ENTER] Pr Event List:

Alarms and Events

All alarms on ascreen—acknowledge(cannot be used on allscreens)

SA [ENTER] Screen Acknowledge

Alarm area—Disable AD: area name [ENTER] Area Disable:

Alarm area—Enable AE: area name [ENTER] Area Enable:

Alarm banner mode(bottom line of display) ASD [ENTER] Alarm Summary Disable

Alarm summary mode(bottom line of display) ASE [ENTER] Alarm Summary Enable:

Alarm view toggle (togglesbetween focused and full) AVT [ENTER] Alarm View Toggle

Alarm logging—Disable DLA (node#) [ENTER] Disable Logging Alarms:

Alarm logging—Enable ELA (node#) [ENTER] Enable Logging Alarms:


CC: 8-2-8


Table 8.2.2. SMS Commands that Perform Operations (continued)

Operation Performed Command Line TextEntry

Alarm regeneration—Initiate AR [ENTER] Alarm Regen:

Silence console horn SH [ENTER] Silence Horn

Console

Abort backup AB [ENTER] Abort Backup:

Abort tape restore ATR [ENTER] Abort Tape Restore:

Disable console configbackup DCB [ENTER] Disable Console Cfg Backup

Enable console configbackup ECB [ENTER] Enable Console Cfg Backup

Eject a floppy disk EF (node#) [ENTER] Eject Floppy:

Reboot the console RBC [ENTER] Re--Boot Console

Shut down operation of disk DS: (node#) [ENTER] Disk Shutdown

Console Screens

Mark—remove RM mark# [ENTER] Remove Mark:

Next page—call up PF [ENTER] Page Forward

Previous page—call up PB [ENTER] Page Backward

Recall the previous screen R: (node#) [ENTER] Recall:

ControlFile

Kill operation of ControllerProcessor

KC Controller Processor address[ENTER] Kill Controller:

Nonvolatile memory—Eliminate areas ofnonvolatile memory that arereserved fornon-existent blocks

FB (node#) [ENTER] Free Bubble

Nonvolatilememory—Initializeconfiguration information

IC (ControlFile address) [ENTER] Init CF Nvmem Config:

Wipe bubble memory WB (ControlFile address) [ENTER] Wipe Bubble:

Diagnostics (See SV:9)

Stop memory dump before itfinishes KMD Kill Memory Dump


CC: 8-2-9


Table 8.2.2. SMS Commands that Perform Operations (continued)


Captures RAM memory of anode in a file MD (node#), (filename) [ENTER] Memory Dump:

Mask

Toggle Tag Mask TTM: [ENTER] Toggle Tag Mask:

Operator Log

Operator Log—print P [sp] OL [ENTER] Pr Operator Log

Plant Configuration

Abort plant config backup APB [ENTER] Abort Plant Cfg Backup

Disable plant config backup DPB [ENTER] Disable Plant Cfg Backup

Enable plant config backup EPB [ENTER] Enable Plant Cfg Backup

Screen print

Character print of screen SC (node#) [ENTER] Screen Char Print:

Graphic print of screen SG (node#) [ENTER] Screen Graph Print:

Screen print (continued)

Configured mode print ofscreen SP (node#) [ENTER] Screen Print:

Transmitter Log

Trans MaintenanceLog—Disable DML (node#) [ENTER] Disable Maint Log:

Trans MaintenanceLog—Enable EML (node#) [ENTER] Enable Maint Log:

* If you perform one of these print operations from the command line, the informationis printed at the node configured in the “Backup Printer Node” field on the Alarm ListConfiguration screen. In addition, the alarm list unprinted count does not change.

CC: 8-2-10


CC: 8-3-1

RS3: Commands MTCC Commands

Section 3:MTCC Commands

The commands that can be entered on an MTCC include all SMScommands, plus commands related to Batch, Reports, Trending, andGraphics.

Table 8.3.1 lists the commands that call up screens. Table 8.3.2 lists thecommands that perform operations.

CC: 8-3-2


Table 8.3.1. MTCC Commands that Call Up Screens

Screen Called Up Entry Command Line Text

Alarm and Event Lists

Active Batch Alarms BAAA [ENTER] BATCH Active Alarms

Alarm Annunciation AAC [ENTER] Alarm Annunciation Cnf:

Active Hardware Alarms HA [ENTER] Hardware Active Alarms

Active Process Alarms AAL [ENTER] Alarm Active List

Active Process Alarms PA [ENTER] Process Active Alarms

Active SuppressedAlarms ASA [ENTER] Alarm Suppressed Actv

Active System Status SSA [ENTER] System Status Active

Advisory Active Alarms ADAA [ENTER] ADV Actv Alrms

Advisory Cleared Alarms ADCA [ENTER] ADV Clrd Alrms

Cleared Batch Alarms BACA [ENTER] BATCH Cleared Alarms

Cleared HardwareAlarms HC [ENTER] Hardware Cleared Alarms

Cleared Process Alarms PC [ENTER] Process Cleared Alarms

Cleared SuppressedAlarms ASC [ENTER] Alarm Suppressed Clrd

Cleared System Status SSC [ENTER] System Status Cleared

Critical Active Alarms CRAA [ENTER] CRIT Actv Alarms

Critical Cleared Alarms CRCA [ENTER] CRIT Clrd Alarms

Disk Event List DEL [ENTER] Disk Event List

Event List EL: (event list#) [ENTER] Event List:

Plant Area (ACTV) AN: [area name] [ENTER] Area Name:

Plant Area (ACTV) AAA (area name) [ENTER] Actv Area Alms:

Plant Area (CLRD) CAA [area name] [ENTER] Clrd Area Alms:

Alarms and Events

Alarm Configuration AC [ENTER] Alarm Configuration

Alarm List Configuration ALC [ENTER] Alarm List Configuration

Alarm Log Display ALD (alarm log filename) [ENTER] Alm Log Disp:

Alarm Log Display ALS (log display configuration name)[ENTER] Alm Log Search:

Configure AlarmBroadcast CAB [ControlFile node#] [ENTER] Cnfg Alarm Broadcast

Event List Configuration ELC [ENTER] Event List Configuration

CC: 8-3-3


Table 8.3.1. MTCC Commands that Call Up Screens (continued)


Alarms and Events(continued)

Log DisplayConfiguration LDC [ENTER] Log Display Config:

Alarm Areas

Area NameConfiguration ANC [ENTER] Area Name Config:

Graphic for specifiedarea ANG [area name] [ENTER] Area Name Graphic:

Batch & RBLC

Batch Acquire QueuesBAQ (task tag) [ENTER] orBAQ (node#: task#) [ENTER]

BATCH Queues:

Batch Configuration BAC: [ENTER BATCH Config:

Batch Control RecipeConfig

BACR (filename) [ENTER] orBACR (batch id) [ENTER]

BATCH Control Rec:

Batch Formula Table BAFT: [ENTER] BATCH Formula Tbl:

Batch InputBAI (task tag) [ENTER] orBAI (node#: task#) [ENTER]

BATCH Input:

Batch LogBAL: (volume , filename) [ENTER] orBAL: (node#, filename) [ENTER]

BATCH Log:

Batch Master RecipeConfig BAMR (filename) [ENTER BATCH Master Rec:

Batch MaterialProperties BAMP [ENTER BATCH Mat Prop

Batch Materials Table BAMT (filename) [ENTER BATCH Material Tbl:

Batch MonitorBAM: (task tag) [ENTER] orBAM: (node#: task#) [ENTER]

BATCH Monitor:

Batch Operations Table BAOT (filename) [ENTER BATCH Oper Tbl:

Batch OverviewBAO: (task tag) [ENTER] orBAO: (node#: task#) [ENTER]

BATCH Overview:

Batch Plant Unit Status BAP [ENTER] BATCH Plant Unit

Batch RunBAR: (task tag) [ENTER] orBAR: (node#: task#) [ENTER]

BATCH Run:

Batch ScriptBAS: (volume , filename) [ENTER] orBAS: (node#, filename) [ENTER]

BATCH Script:

Batch Unit Set BAUS: (filename) [ENTER] BATCH Unit Set:

CC: 8-3-4




Batch & RBLC (continued)

Batch Units Table BAUT (filename) [ENTER] BATCH Unit Tbl:

Batch Working Recipe BAWR (tag) [ENTER] BATCH Working Rec:

RBL Directory (Batch) BAD (node# or volume name)[ENTER] BATCH Directory:

RBL Directory (RBL) RBLD (node# or volume name)[ENTER] RBL Directory:

RBL File Contents(Batch)

BAF (volume , filename) [ENTER] orBAF (node#, filename) [ENTER]

BATCH File Cont:

RBL File Transfer FT [ENTER] File Transfer

RBL File Contents (RBL)RBLF (volume , filename) [ENTER] orRBLF (node#, filename) [ENTER]

RBL File Contents:

RBLC Monitor RBLM (block tag or address) [ENTER] RBLC Monitor

RBLC ScriptRBLS (volume , filename) [ENTER] orRBLS (node#, filename) [ENTER]

RBLC Script:

Block

Block Directory CBD: (Controller Processor address)[ENTER] Cont Block Directory:

Block Print Setup BP [ENTER] Block Print

Block References BR (tag or address) [ENTER] Block References:

Block Status CBS (Controller Processor address)[ENTER] Cont Block Status:

Continuous Diagram BD (tag or address) [ENTER] Block Diagram:

Continuous Faceplate BF (tag or address) [ENTER] Block Faceplate:

Continuous Links BL (tag or address) [ENTER] Block Links:

Group Display screen orCB ContinuousFaceplate

TA (tag or address) [ENTER] Tag/Address:

Callup Buttons

Alarm Annunciation AAC (command#) [ENTER] Alm Annunciation Cnf:

Callup Buttons CCB (option keyboard#) [ENTER] Config Callup Buttons

Calls up the screen orperforms the operationthat is assigned to acallup button.

CUB: [button#] [ENTER] Call Up Button:

Display Buttons CDB (button#) [ENTER] Config Display Buttons:

CC: 8-3-5




Color

Color Configuration CCU [ENTER] Config Color Usage

Master Color Selection CCP [ENTER] Config Color Palette

Console Configuration

Console Configuration CCC [ENTER] Config Command Console

Console Menu

Menu CommandConsole MCC [ENTER] Menu Command Console

ControlFile and I/O

ControlFile Dump CFD node# or Controller Processor#[ENTER] Cont File Dump:

ControlFile Dump orNode Dump ND node# [ENTER] Node Dump:

ControlFile Links CFL (ControlFile#) [ENTER] Cont File Links:

ControlFile Status CFS (ControlFile#) [ENTER] Cont File Status:

Field I/O Status FS (Controller Processor address)[ENTER] Field I/O Status:

Transmitter Maint LogTL (volume , filename) [ENTER] orTL (node#, filename) [ENTER]

Trans Log:

Diagnostics

Background Diagnostics MCT [ENTER] Menu Confidence Tests

Memory Dump MD node#, (filename) [ENTER] Memory Dump

Memory View MV [ENTER] Memory View

Diogenes Interface

Diogenes I/FConfiguration CDI (node#) [ENTER] Configure Diogenes I/F:

Disk and File

Calls up specified file DDF [ENTER] Disk Dir File:

Configure DownloadScript

CDS (volume , filename) [ENTER] orCDS (node#, filename) [ENTER]

Cfg Dnld Script:

Disk Activity (last screen) DA [ENTER] Disk Activity

Disk Directory DD: (node#: drive#) [ENTER] Disk Dir:

Disk Directory PeerWay DDP [ENTER] Disk Dir PeerWay

CC: 8-3-6




Disk and File (continued)

Disk FolderConfiguration DC: (node#) [ENTER] Disk Configure:

Graphics

Graphic ViewingPG: [volume , filename] [ENTER] orPG: [node#, filename] [ENTER]

Pr Graph:

Link Editor LE (node) : (drive) Link Edit:

Process GraphicsGeneration

PGG (volume , filename) [ENTER] orPGG (node#, filename) [ENTER]

Pr Graph Gen:

Process GraphicsSymbol generationscreen

PGS (volume , filename) [ENTER] orPGS (node#, filename) [ENTER]

Pr Graph Sym:

HIA

Configure HIA CH (node #) [ENTER] Config HIA:

Login

User Name Detail UND (login_name) [ENTER] User Name Detail

Plant Unit Access PUA (filename) [ENTER] Plant Unit Access

User Profile Directory UPD [ENTER] User Profile Directory

Login (continued)

Login CUP [ENTER] Change User Password

Login LI [ENTER] Log In :

Log out LO [ENTER] Log Out :

Message Pairs

STD Message Pairs MPS [ENTER] Message Pairs Std

User Message Pairs MPU [ENTER] Message Pairs User

Operating Displays

Group G: (group number) [ENTER] Group:

Group Directory GD: [ENTER] Group Directory:

Overview O: (overview number) [ENTER] Overview:

Overview Directory OD: [ENTER] Overview Directory:

Unit U: (unit number) [ENTER] Unit:

Unit Directory UD: [ENTER] Unit Directory:

CC: 8-3-7




Operator Log

Operator Change Log OL [ENTER] Operator Log

PeerWay and Plant

PeerWay Node PN (node#) [ENTER] PeerWay Node:

PeerWay Overview PO (PeerWay#) [ENTER] PeerWay Overview:

PeerWay Performance PP [ENTER] PeerWay Performance

Plant Status PS (node#) [ENTER] Plant Status:

Plant Unit Configuration PUC [ENTER] Plant Unit Configuration

Plant Configuration Backup

Backup Plant Config BUP [ENTER] BackUp Plant Config

PLC

Configure PLC CP [ENTER] Configure PLC:

Reports

Report ConfigurationRG (volume , filename) [ENTER] orRG (node#, filename) [ENTER]

Reprt Gen:

Report ConfigurationDirectory RCD (node#) [ENTER] Reprt Config Directory:

Report File ContentsRFC (volume , filename) [ENTER] orRFC (node#, filename) [ENTER]

Reprt File Contents:

Report Read DirectoryRRD: (volume , filename) [ENTER] orRRD: (node#, filename) [ENTER]

Reprt Read Directory:

Report Read/ScanRR: (volume , filename) [ENTER] orRR: (node#, filename) [ENTER]

Reprt Read:

Report Status RS (node#) [ENTER] Reprt Status:

RFI

Configure RFI CR: (node#) [ENTER] Configure RFI:

RNI

Configure RNI CRN (node#) [ENTER] Configure RNI:

RNI Status CRN (node#) [ENTER] [EXCHANGE] Configure RNI:

SCI

Configure SCI CS (node#) [ENTER] Configure SCI:

CC: 8-3-8




Trend

Trend File Configuration TFC (trend file#) [ENTER] Trend File Config:

Trend File Setup TFS (trend group#) [ENTER] Trend File Setup

Trend Group TG: (trend group#) [ENTER] Trend Group:

Trend GroupConfiguration TGC [ENTER] Trend Group Config:

Trend Group Menu TGD: (menu page#) [ENTER] Trend Group Directory

Trend Group Menu TGM (menu page#) [ENTER] Trend Group Menu

Tuning Displays

Tuning Display TD: (tuning display#) [ENTER] Tuning Display

Tuning Display Directory TDD [ENTER] Tuning Display Directory

VAX

Host Mode HM (node#) [ENTER] Hostmode:

VAX RPQNA StatusDisplay VS (node#) [ENTER] VAX Status:

CC: 8-3-9


Table 8.3.2. MTCC Commands that Perform Operations

Operation Performed Entry Command Line Text

Alarm and Event Lists*


P [sp] PA [ENTER] Pr Process Alarm List


P [sp] AA [ENTER] Pr Alarm Active List

Active System StatusAlarms List—PrintCleared System StatusAlarms List—Print

P [sp] SSA [ENTER] Pr System Status Active

Active Hardware AlarmList—PrintCleared Hardware AlarmList—Print

P [sp] HA [ENTER] Pr Hardware Alarm List

Active Batch AlarmsList—PrintCleared Batch AlarmsList—Print

P [sp] BA [ENTER] Pr BATCH Alarm List

Disk Event List—Print P [sp] DEL [ENTER] Pr Disk Event List

Event List—Print P [sp] EL [:] event list# [ENTER] Pr Event List:

Alarms and Events

All alarms on ascreen—acknowledge(cannot be used on allscreens)

SA [ENTER] Screen Acknowledge

Alarm area—Disable AD: area name [ENTER] Area Disable:

Alarm area—Enable AE: area name [ENTER] Area Enable:

Alarm banner mode (bottomline of display) ASD [ENTER] Alarm Summary Disable

Alarm summary mode(bottom line of display) ASE [ENTER] Alarm Summary Enable:

Alarm view toggle (togglesbetween focused and full) AVT [ENTER] Alarm View Toggle

Alarm logging—Disable DLA (node#) [ENTER] Disable Logging Alarms:

Alarm logging—Enable ELA (node#) [ENTER] Enable Logging Alarms:

Alarm regeneration—Initiate AR [ENTER] Alarm Regen:

Silence horn SH [ENTER] Silence Horn

Batch


CC: 8-3-10


Table 8.3.2. MTCC Commands that Perform Operations (continued)


Batch—Disable DBAS (node#) [ENTER] Disable Batch System:

Batch (continued)

Batch—Enable EBAS (node#) [ENTER] Enable Batch System:

Batch Bubblememory—Initialize BAW (node#) [ENTER] BATCH Wipe:

Batch Log—Disable DBAL (node#) [ENTER] Disable Batch Log:

Batch Log—Enable EBAL (node#) [ENTER] Enable Batch Log:

Console

Abort backup AB [ENTER] Abort Backup:

Abort tape restore ATR [ENTER] Abort Tape Restore:

Disable console configbackup DCB [ENTER] Disable Console Cfg Backup

Enable console configbackup ECB [ENTER] Enable Console Cfg Backup

Eject a floppy disk EF (node#) [ENTER] Eject Floppy:

Reboot the console RBC [ENTER] Re--Boot Console

Shut down operation of disk DS: (node#) [ENTER] Disk Shutdown

Console Screens

Mark—remove RM mark# [ENTER] Remove Mark:

Next page—call up PF [ENTER] Page Forward

Previous page—call up PB [ENTER] Page Backward

Recall the previous screen R: (node#) [ENTER] Recall:

ControlFile

Kill operation of ControllerProcessor

KC Controller Processor address[ENTER] Kill Controller:

Nonvolatile memory—Eliminate areas ofnonvolatile memory that arereserved for non-existentblocks

FB (node#) [ENTER] Free Bubble

Nonvolatilememory—Initializeconfiguration information

IC (ControlFile address) [ENTER] Init CF Nvmem Config:

Wipe bubble memory WB (ControlFile address) [ENTER] Wipe Bubble:

Diagnostics (See SV:9)

Stop memory dump before itfinishes KMD Kill Memory Dump


CC: 8-3-11


Table 8.3.2. MTCC Commands that Perform Operations (continued)


Captures RAM memory of anode in a file MD (node#), (filename) [ENTER] Memory Dump:

Mask

Toggle Tag Mask TTM: [ENTER] Toggle Tag Mask:

Operator Log

Operator Log—print P [sp] OL [ENTER] Pr Operator Log

Plant Configuration

Abort plant config backup APB [ENTER] Abort Plant Cfg Backup

Disable plant config backup DPB [ENTER] Disable Plant Cfg Backup

Enable plant config backup EPB [ENTER] Enable Plant Cfg Backup

Reports

Print a reportRP (volume , filename) [ENTER]or

RP (node#, filename) [ENTER]Reprt Prt:

Print a reportP [sp] R [volume , filename][ENTER] or

P [sp] R [node#, filename] [ENTER]Pr Report:

Reports—Disable DR [ENTER] Disable Reports

Reports—Enable ER [ENTER] Enable Reports

Screen print

Character print of screen SC (node#) [ENTER] Screen Char Print:

Graphic print of screen SG (node#) [ENTER] Screen Graph Print:

Configured mode print ofscreen SP (node#) [ENTER] Screen Print:

Transmitter Log

Trans MaintenanceLog—Disable DML (node#) [ENTER] Disable Maint Log:

Trans MaintenanceLog—Enable EML (node#) [ENTER] Enable Maint Log:

Trending

Trending—Disable DT (node#) [ENTER] Disable Trending

Trending—Enable ET (node#) [ENTER] Enable Trending

* If you perform one of these print operations from the command line, the information is printed at the nodeconfigured in the “Backup Printer Node” field on the Alarm List Configuration screen. In addition, thealarm list unprinted count does not change.

CC: 8-3-12


CC: 8-4-1

RS3: Commands Hints for Using Commands

Section 4:Hints for Using Commands

This section discusses some tips for using commands.

- You can use the [NEXT OPTION] and [LAST OPTION] keys toscroll through the commands in (mostly) alphabetical order.

- You can type a letter and then use the [NEXT OPTION] and[LAST OPTION] keys to scroll through commands.

For example, if you know that a command starts with the letter C,but you aren’t sure of the exact combination of letters, you can type[C] and [NEXT OPTION] to scroll through the commands from Conward.

CC: 8-4-2

RS3: Commands Hints for Using Commands

CC: Index-1

RS3: Console Configuration Manual Index


Index

Symbols

$$PASSWD filedefault, 7-1-2hints, 7-3-1lost, 7-3-6, 7-3-7storing, 7-1-8

A

access indicators, 2-1-4access levels, 2-1-2accumulate object, reports, 4-4-21, 4-4-24, 4-4-30accumulators, reports, 4-4-19, 4-4-30adding users to password system, 7-1-22address object, reports, 4-4-15Advance request rate, configuring, 2-1-38advisory process alarms, 6-3-2alarm

priority, 6-5-12separating and sorting at a console, 6-3-1–6-3-7, 6-3-8– 6-3-12

suppression, 6-3-6type priority, 6-5-12types, 6-3-2

alarm annunciation on graphics, 3-2-85Alarm Annunciation screen, 2-4-3

calling up screen, 2-4-2– 2-4-6configuring alarm annunciation, 2-4-3configuring callup button, 2-4-2

alarm area, 6-3-3– 6-3-6configuring, 6-1-1– 6-1-2, 6-3-3disabling, 6-3-5enabling, 6-3-5

alarm banner mode, 6-5-12alarm broadcast configuration, 6-1-2– 6-1-4

restoring, 6-1-5saving, 6-1-5

Alarm Configuration screen, 6-5-2– 6-5-3alarm display mode, 6-5-13– 6-5-14alarm list

properties configuration, 6-3-8size, 6-3-8

Alarm List Configuration screen, 6-3-8– 6-3-10

alarm log, 6-4-1– 6-4-9disabling, 6-4-9display, 6-4-6– 6-4-8display configurations, 6-4-2– 6-4-5enabling, 6-4-9

Alarm Log Display screen, 6-4-6– 6-4-8alarm management

hints, 6-7-1troubleshooting, 6-7-1

alarm messagesmanaging message load, 6-1-1reducing message load, 6-1-1, 6-1-4– 6-1-5,6-1-7

alarm object, process graphics, 3-2-48– 3-2-52,3-2-85

alarm summary mode, 6-5-13alarm, storage in console RAM, 6-2-1alternate disk access, 2-1-17– 2-1-18arc object

characteristics, 3-2-16fill option, 3-2-21– 3-2-22process graphics, 3-2-12

archive trend data, 5-4-1– 5-4-3attributes, message pairs, 2-5-4– 2-5-5automatic backup, 2-1-28– 2-1-30

console configuration, 2-1-28plant configuration, 2-1-29– 2-1-30

customizing, 2-1-30

B

backup nodes, $$PASSWD file, 7-1-3, 7-1-5,7-1-8, 7-3-2

backup trend file, 5-4-2ban1 object, reports, 4-4-12ban2 object, reports, 4-4-12banners, reports, 4-4-12batch alarms, 6-3-2batch information, process graphics, 3-2-83– 3-2-84batch task data, process graphics, 3-2-83– 3-2-84bface object, process graphics, 3-2-83– 3-2-84blkdes object, process graphics, 3-2-25– 3-2-27block information objects

blkdes object, 3-2-25– 3-2-27disc object, 3-2-28– 3-2-30, 3-2-53hdev object, 3-2-31– 3-2-34

CC: Index-2


link object, 3-2-28– 3-2-30mode object, 3-2-25– 3-2-27tag object, 3-2-25– 3-2-27ticbar object, 3-2-31– 3-2-32units object, 3-2-28– 3-2-30

block information reportsaddress, 4-4-15descriptor, 4-4-16function, 4-4-17mode, 4-4-18tag, 4-4-14units, 4-4-19values, 4-4-20

block links, limits, 3-3-2Block Print function, 2-6-1– 2-6-3Block Print Setup screen, 2-6-2block tags (16 character), configuring, 2-1-20–2-1-27

block variable informationdisplayed in character form, 3-2-28displayed in graphic form, 3-2-32process graphics, 3-2-28– 3-2-31

block variables, trending, 5-1-2, 5-1-4bottom operation, 3-2-58box object

characteristics, 3-2-16fill option, 3-2-21– 3-2-22process graphics, 3-2-10, 3-2-16, 3-2-21–3-2-24

C

CAB--type Plant Configuration file, 6-1-5calculations, performed in reports, 4-4-21, 4-4-24calling up, process graphic, 3-1-4– 3-1-5callup buttons, 2-4-1Callup Buttons screen, 2-4-7changing configuror to system manager, 7-1-24–7-1-25

changing password, 7-2-4– 7-2-5circle object

characteristics, 3-2-16fill option, 3-2-21– 3-2-22process graphics, 3-2-9, 3-2-16, 3-2-21–3-2-24

color, 2-2-1– 2-2-8Color Configuration screen, 2-2-3– 2-2-7combining objects, 3-2-60– 3-2-64commands

configuring, 2-4-2description, 8-1-1MTCC, 8-3-1– 8-3-12SMS, 8-2-1– 8-2-11

comment object, reports, 4-4-13conditional display, process graphics, 3-2-54–3-2-55

configuration file links, changing, 2-7-1configuration file links, changing, 2-7-1configuration mode

calling up, 3-1-6display, 3-1-3objects, 3-2-8

Configure Alarm Broadcast screen, 6-1-2– 6-1-3configuring

block print function, 2-6-1– 2-6-3callup and display buttons, 2-4-1– 2-4-10color, 2-2-1– 2-2-3console operations, 2-1-1– 2-1-12, 2-1-20–2-1-36

console operations hints, 2-1-36– 2-1-39message pairs, 2-5-1– 2-5-9operating displays, 2-3-1– 2-3-8password security, 7-1-1– 7-1-7

configurorchanging to system manager, 7-1-24– 7-1-25description, 2-1-4

configuror arrow, 2-1-4console access levels, 2-1-2Console Configuration screen, 2-1-7– 2-1-9, 7-1-8–7-1-10

console lists, reports, 4-4-33, 4-4-34console operations

configuring, 2-1-1– 2-1-12, 2-1-20– 2-1-36configuring hints, 2-1-36– 2-1-39

console screen display coordinates, 3-2-71console trending capabilities, 5-1-2– 5-1-3ControlBlock, configuration screens, access arrows,2-1-4

coordinatesconsole screen display, 3-2-71process graphics fabric, 3-2-71

copying a process graphic, 3-2-82copying objects

process graphics, 3-2-56reports, 4-6-3

creating a process graphic, 3-1-4creating objects, 3-1-1– 3-1-3criteria configurations, 6-4-5critical process alarms, 6-3-2

Ddata entry fields, process graphics, 3-2-53date object, reports, 4-4-32delete operation, process graphics, 3-2-57descriptor objects, reports, 4-4-16designing a report, 4-1-1, 4-3-1, 4-3-3dimensions of a report, 4-3-2disable trending command, 5-1-5disabling an alarm area, 6-3-5disc object, process graphics, 3-2-28– 3-2-30,3-2-53

disk and tape activities, password security, 2-1-3disk event messages, 6-3-2display

alarms, 3-2-48hiding parts of object, 3-2-79– 3-2-80trend group, 5-3-5– 5-3-8

display buttons, 2-4-1, 2-4-8

CC: Index-3


Display Buttons screen, 2-4-8display of objects, appearance dependent ondiscrete block var., 3-2-54

display targets, 3-2-77– 3-2-78

E

edit object menu, 3-2-4editing the body of a report, 4-4-8enable trending command, 5-1-5enabling and disabling alarm areas, 6-3-5event list, size, 6-3-8events, disk switch, 2-1-17

F

fabric, 3-1-1process graphic coordinates, 3-2-71process graphic description, 3-1-1viewing, 3-2-72

faceplatesdisc object, 3-2-53Group Display screens, 2-3-2– 2-3-3group object, 3-2-37– 3-2-39overview object, 3-2-37– 3-2-39process graphics, 3-2-37– 3-2-39unit object, 3-2-37– 3-2-39with message pairs, 2-5-1

field refresh rateconfiguring, 2-1-40limits, 2-1-40, 3-3-2process graphics, 3-3-8

file structure, reports, 4-2-1– 4-2-8fill object, process graphics, 3-2-21formatting, 4-3-3function object, reports, 4-4-17funnel block, 3-3-4

G

general (graphic) alternate disk, 2-1-17generate object, reports, 4-4-36generating a report

from the Report Configuration screen, 4-4-41manually, 4-4-41using alarms and events, 4-4-40using time and date, 4-4-38

graphic fabric, limits, 3-3-2graphic file, limits, 3-3-2Graphics Link Editor, 2-7-1– 2-7-3, 3-2-67graphics performance, optimizing, 3-3-1– 3-3-4Group Directory screen, 2-3-2Group Display screen, 2-3-2– 2-3-3group object, process graphics, 3-2-37– 3-2-39grouping objects

area operation, 3-2-61– 3-2-62description, 3-2-60– 3-2-64group operation, 3-2-63join operation, 3-2-63merge operation, 3-2-66split operation, 3-2-69undo operation, 3-2-70

H

hardware alarms, 6-3-2hdev object, process graphics, 3-2-31– 3-2-34hiding parts of the display, 3-2-79hints

alarm management, 6-7-1configuring trending, 5-5-1reports, 4-6-1, 4-6-3using commands, 8-4-1

I

icon object, process graphicsalarm annunciation, 3-2-85hiding display, 3-2-79– 3-2-80

inhibit alarms, 6-1-7

J

joining objects, 3-2-63

K

keyboard, configuring callup and display buttons,2-4-1

keyboard control switching, 2-1-19keyboard interface for password systems, 7-1-1,7-3-1

keylock interface, with passwords, 7-3-3, 7-3-5

L

layout, report sample, 4-3-1library symbols, 3-2-17– 3-2-18line object, process graphics, 3-2-13– 3-2-14link addresses, editing, 2-7-5Link Count field, 3-3-3Link Editor, 2-7-1

modifying a configuration file, 2-7-2modifying other RS3 file types, 2-7-2

Link Editor screen, 2-7-3link object, process graphics, 3-2-28– 3-2-30LinkEd field, 3-2-67

CC: Index-4


linksediting, 2-7-1linking areas of a graphic, 3-2-67

list object, reports, 4-4-34log display configuration, 6-4-2– 6-4-5Log Display Configuration screen, 6-4-2– 6-4-3logging off console, 7-2-6logging on to console, 7-2-2Login screen, 7-2-2loss of $$PASSWD file, 7-3-6, 7-3-7

M

masking tags, 2-1-20– 2-1-21, 2-1-24– 2-1-27Master Color Selection screen, 2-2-2Menu Command Console screen, 2-1-5merging objects, 3-2-66, 3-3-5message pair, 2-5-1– 2-5-9mode object

process graphics, 3-2-25– 3-2-27reports, 4-4-18

modem interface to printer, 2-1-37moving objects


MTCCand console access levels, 2-1-2CCC screen -- Page 1, 2-1-8commands, 8-3-1– 8-3-12description, 1-2-1MCC screen, 2-1-6trend file capability, 5-1-2

multinational characters, 2-8-1

N

newpage object, reports, 4-3-3, 4-4-10node ownership

configuration, 2-1-31– 2-1-32determining alarm storage, 6-2-1

non--English characters, 2-5-3

O

object menu, process graphics, 3-2-3object overhead, limits, 3-3-2object types


objectsappearance dependent on discrete block var.,3-2-54– 3-2-55

calling up another part of same display, 3-2-75–3-2-77

calling up other displays, 3-2-74

copying, 3-2-56deleting, 3-2-57displaying batch task data, 3-2-83– 3-2-84grouping, 3-2-60– 3-2-64joining objects, 3-2-63merging, 3-2-66moving, 3-2-56removing from group, 3-2-69splitting from a group, 3-2-69stacking, 3-2-58– 3-2-59which display faceplates, 3-2-37– 3-2-39

operating displays, 2-3-1– 2-3-8operator, description, 2-1-4operator arrow, 2-1-4operator change log, 2-1-34optimizing graphics performance, 3-3-1– 3-3-4origin point, process graphics, 3-2-72overlay alternate disk, 2-1-17Overview Directory screen, 2-3-7Overview Display screen, 2-3-8overview object, process graphics, 3-2-37– 3-2-39

Ppageback object, process graphic, 3-2-73– 3-2-79pagefrwd object, process graphic, 3-2-73– 3-2-79panning limits, process graphics, 3-2-72password

adding users to system, 7-1-22changing, 7-2-4– 7-2-5

password file,. See $$PASSWD file.password security

configuring, 7-1-1– 7-1-7hints, 7-3-1keyboard interface, 7-1-1using with standard keyboard interface, 7-3-4

password system, accessing, 7-2-1pictorial representation of plant conditions, 3-1-1Plant Configuration file (type CAB), 6-1-5Plant Status screen, 2-1-32Plant Unit Access screen, 7-1-14– 7-1-18plant unit configuration, with plant unit access,7-1-15

Plant Unit Configuration screen, 2-1-33plant units

configuration, 2-1-33– 2-1-34console alarm storage, 6-2-1ownership, 2-1-33

preconfigured process graphics, 3-3-7primary and backup nodes, 7-3-2

$$PASSWD file, 7-3-2configuring, 7-1-3, 7-1-5resetting, 7-1-8

print object, reports, 4-4-9printer configuration tips, 2-1-37printing

report configuration, 4-4-10report when generated, 4-4-42

process graphicaccessing, 3-1-3

CC: Index-5


area, 3-2-61– 3-2-62block variable information

character form, 3-2-28graphic form, 3-2-31text form, 3-2-28– 3-2-29

bottom, 3-2-58calling up, 3-1-6configuration mode, 3-1-6configuration tools, 3-2-56– 3-2-66copying graphic file, 3-2-82copying objects, 3-2-56creating graphic file, 3-1-4creating object, 3-2-2– 3-2-4creating shapes, 3-2-21– 3-2-22deleting objects, 3-2-57description, 3-1-1fabric coordinates, 3-2-71files, 3-1-2grouping objects, 3-2-63introduction, 3-1-1– 3-1-5joining objects, 3-2-63library symbols, 3-2-17– 3-2-18limits, 3-3-2merging objects, 3-2-66moving objects, 3-2-56new symbols, 3-2-19– 3-2-20object types, 3-2-5– 3-2-6origin point, 3-2-72panning limits, 3-2-72preconfigured, 3-3-7shape characteristics, 3-2-15– 3-2-16splitting objects from group, 3-2-69storage, 3-1-2Top Menu, 3-2-58undoing operation, 3-2-70viewing mode, 3-1-4

process graphic (pixel graphics), calling up, 3-1-4Process Graphic Generation screen, 3-1-4process graphics, 3-2-1– 3-2-81Process Graphics folder, 3-1-2

R

recipe manager, description, 2-1-4recipe manager access indicator, 2-1-4reducing message requests, 5-3-10refresh rate, configuring, 2-1-38report, 4-1-1Report Config Directory screen, 4-2-6– 4-2-7Report Configuration screen, 4-4-2, 4-4-3Report Configuration window, 4-4-5, 4-4-7report dimensions, 4-3-2Report File Contents screen, 4-2-4report objects

types, 4-4-6using, 4-4-5

Report Read Directory screen, 4-2-3Report Read/Scan screen, 4-2-5Report Status screen, 4-2-8

reports, 4-2-1, 4-3-3, 4-4-1, 4-5-1, 4-6-1assembling information for, 4-3-1configuring, 4-4-1, 4-4-42configuring a report in a report, 4-4-36configuring block information, 4-4-14, 4-4-24configuring console lists, 4-4-33configuring oversized text, 4-4-12configuring print appearance, 4-4-9configuring text, 4-4-11configuring time and date, 4-4-31, 4-4-32configuring trend information, 4-4-25, 4-4-30designing, 4-3-1, 4-3-3dimensions, 4-3-2editing, 4-4-8file structure, 4-2-1– 4-2-8formatting for printing, 4-3-3generating, 4-4-38, 4-4-42hints, 4-6-1, 4-6-3introduction, 4-1-1operator comments, 4-4-13print appearance, 4-4-9saving to disk, 4-5-1troubleshooting, 4-6-1, 4-6-3

Russian Console, 2-8-1

Sscaling, Trend Group screen, 5-3-7screen refresh rate

configuring, 2-1-38limits, 2-1-39, 3-3-2process graphics, 3-3-8

secure keyboard interface, with passwords, 7-3-3selecting a report object, 4-6-2shapes

creating arcs, 3-2-12creating boxes, 3-2-10creating circles, 3-2-9creating lines, 3-2-13creating lines with different characteristics,3-2-13, 3-2-14

creating shape characteristics, 3-2-15– 3-2-16creating triangles, 3-2-11library symbols, 3-2-17– 3-2-18new symbols, 3-2-19– 3-2-20which fill up, 3-2-21– 3-2-22

slidewireTrend Group screen, 5-3-6trend object, 3-2-43– 3-2-46

splitting an object from a group, 3-2-69splitting tags, 2-1-20– 2-1-21, 2-1-22– 2-1-23stacking objects, 3-2-58standard KBI, with passwords, 7-3-4standard message pairs, 2-5-2– 2-5-4supervisor, description, 2-1-4supervisor arrow, 2-1-4Suppressed alarms, 6-3-6suppressing and unsuppressing alarms, 6-3-6symbols, 8-1-2

process graphics, 3-2-17– 3-2-20

CC: Index-6


system managerchanging from configuror, 7-1-24– 7-1-25description, 2-1-4

system manager access symbol, 2-1-4System Manager Station

and console access levels, 2-1-3CCC screen -- Page 1, 2-1-7commands, 8-2-1– 8-2-11description, 1-1-1MCC screen, 2-1-5

system privileges, 2-1-2configuror, 2-1-2operator, 2-1-2supervisor, 2-1-2system manager, 2-1-2

system status messages, 6-3-2

T

tag objectprocess graphics, 3-2-25– 3-2-27reports, 4-4-14

tagsmasking, 2-1-20– 2-1-21, 2-1-24– 2-1-27splitting, 2-1-20– 2-1-21, 2-1-22

target object, process graphic, 3-2-77– 3-2-78text object

calling up other displays, 3-2-74– 3-2-77process graphics, 3-2-46– 3-2-47reports, 4-4-11, 4-4-12

thing object, process graphicsgrouping objects, 3-2-66merging objects, 3-3-5

ticbar objectconfiguring characteristics, 3-2-32process graphics, 3-2-31– 3-2-32

alarm annunciation, 3-2-85time object, reports, 4-4-31tips

configuring callup and display buttons, 2-4-10configuring console operations, 2-1-37message pairs, 2-5-9

Top menu, process graphics, 3-2-2, 3-2-56– 3-2-66top operation, 3-2-58– 3-2-59trend data

archiving, 5-4-1– 5-4-3viewing, 5-3-8

Trend Data folder, 5-1-3trend file

backup, 5-4-2configuring, 5-2-1– 5-2-7storage, 5-1-3

Trend File Configuration screen, 5-1-4, 5-2-5–5-2-7

Trend File Setup screen, 5-2-2– 5-2-3trend group

capabilities, 5-1-2

configuring, 5-3-1– 5-3-9example, 5-1-1updating, 5-3-10

Trend Group screen, 5-3-5– 5-3-8trend information, process graphics, 3-2-41– 3-2-42trend log object, reports, 4-4-25trend object, process graphic, 3-2-44trending

enabling and disabling, 5-1-5hints, 5-5-1operations, 5-1-1– 5-1-6process graphics, 3-2-41– 3-2-44screens, 5-1-4troubleshooting, 5-5-1

trf#, 5-1-3, 5-4-2trf#b, 5-1-3, 5-4-2triangle object

configuring characteristics, 3-2-16fill option, 3-2-21– 3-2-22process graphics, 3-2-11

troubleshootingalarm management, 6-7-1callup and display buttons, 2-4-9configuring colors, 2-2-7configuring console operations, 2-1-36configuring trending, 5-5-1reports, 4-6-1

U

undoing the previous operation, process graphics,3-2-70

Unit Directory screen, 2-3-5Unit Display screen, 2-3-6units object

process graphics, 3-2-28– 3-2-30, 3-2-37–3-2-39

reports, 4-4-19Unsuppressed alarm, 6-3-6update time, configuring, 5-3-10user message pairs, 2-5-1– 2-5-3, 2-5-5, 2-5-8User Message Pairs screen, 2-5-5User Name Detail screen, 7-1-19– 7-1-21user name profile, changing, 7-1-23user privileges, 2-1-2User Profile Directory screen, 7-1-12– 7-1-13

V

value object, reports, 4-4-20vdev object, process graphics, 3-2-31– 3-2-34viewing mode

calling up, 3-1-4display of objects, 3-2-7displaying, 3-1-3