Descripción: Presentacion de las normas actuales para la elaboracion de los HMI
kkDescripción completa
This paper concentrates on proper and effective design of the graphics used in modern SCADA systems.
Descripción completa
HmiFull description
Descripción completa
GE Energy HMI for SPEEDTRONIC™ Turbine Control Application Guide GEH-6126C Vol II GEH-6126B Vol II
i
g
These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible contingency to be met during installation, operation, and maintenance. The information is supplied for informational purposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflected herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced herein. GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not provide any license whatsoever to any of these patents. This document contains proprietary information of General Electric Company, USA and is furnished to its customer solely to assist that customer in the installation, testing, operation, and/or maintenance of the equipment described. This document shall not be reproduced in whole or in part nor shall its contents be disclosed to any third party without the written approval of GE Energy. GE provides the following document and the information included therein as is and without warranty of any kind, expressed or implied, including but not limited to any implied statutory warranty of merchantability or fitness for particular purpose. If further assistance or technical information is desired, contact the nearest GE Sales or Service Office, or an authorized GE Sales Representative.
* Trademark of General Electric Company ARCNET is a registered trademark of Datapoint Corporation. CIMPLICITY and Genius are a registered trademarks of GE Fanuc Automation North America, Inc. Ethernet is a trademark of Xerox Corporation. Excel, Microsoft, NetMeeting, Windows, and Window NT are registered trademarks of Microsoft Corporation. Modbus is a registered trademark of Schneider Automation. Pentium is a registered trademark of Intel Corporation. PI-ProcessBook is a registered trademark of OSI Software Inc. SPEEDTRONIC is a trademark of General Electric Company
g
To:
Reader Comments
GE Energy Documentation Design, Rm. 293 1501 Roanoke Blvd. Salem, VA 24153-6492 USA Fax: 1-540-387-8651 (GE Internal DC 8-278-8651)
We welcome comments and suggestions to make this publication more useful. Your Name
Today’s Date
Your Company’s Name and Address
Job Site GE Requisition No.
If needed, how can we contact you? Fax No. Phone No. E-mail
Other Comments (What you like, what could be added, how to improve, and such.) ________________________________________________
__________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?) { Superior
{ Comparable
{ Inferior
Detach and fax or mail to the address noted above.
........................................................................ Fold here and close with staple or tape .......................................................................................... Place stamp here.
GE Energy Documentation Design, Rm. 293 1501 Roanoke Blvd. Salem, VA 24153-6492 USA
.......................................................................................... Fold here first ........................................................................................................
Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not strictly observed, could result in personal injury or death.
Indicates a procedure, condition, or statement that, if not strictly observed, could result in damage to or destruction of equipment.
Indicates a procedure, condition, or statement that should be strictly followed in order to optimize these applications.
Note Indicates an essential or important procedure, condition, or statement.
This equipment contains a potential hazard of electric shock or burn. Only personnel who are adequately trained and thoroughly familiar with the equipment and the instructions should install, operate, or maintain this equipment. Isolation of test equipment from the equipment under test presents potential electrical hazards. If the test equipment cannot be grounded to the equipment under test, the test equipment’s case must be shielded to prevent contact by personnel. To minimize hazard of electrical shock or burn, approved grounding practices and procedures must be strictly followed.
To prevent personal injury or equipment damage caused by equipment malfunction, only adequately trained personnel should modify any programmable machine.
Contents Chapter 1 Overview
1-1
Introduction ...............................................................................................................................................1-1 HMI Summary...........................................................................................................................................1-1 System Configuration.....................................................................................................................1-1 Text Conventions ...........................................................................................................................1-3 Related Documentation .............................................................................................................................1-4
Chapter 2 Installation
2-1
Introduction ...............................................................................................................................................2-1 Login and Startup ......................................................................................................................................2-1 Initial Power Up .............................................................................................................................2-1 CIMPLICITY Project.....................................................................................................................2-3 Check Usernames and Passwords ..................................................................................................2-3
Chapter 3 Mark IV
3-1
Overview ...................................................................................................................................................3-1 Features, Utilities, and Tools.....................................................................................................................3-1 DDVAL - Data Dictionary Validation ...........................................................................................3-1
Chapter 4 Mark V
4-1
Mark V Controller .....................................................................................................................................4-1 HMI Unit-Specific Directory .........................................................................................................4-1 Compiling Unit-Specific Configuration Files ................................................................................4-5 Downloading Unit-Specific Configuration Files............................................................................4-6 Control Constants...........................................................................................................................4-6 Auto-Calibrate Display..............................................................................................................................4-7 Mark V Auto Calibration ...............................................................................................................4-7 Command Pushbutton ....................................................................................................................4-8 Command Line Arguments ..........................................................................................................4-10 Screen Description .......................................................................................................................4-10 Autocalibrate Display Dialog Boxes............................................................................................4-11 Control Constants Display - Mark V and Mark V LM............................................................................4-12 Changing a Control Constant .......................................................................................................4-13 Control Constants Adjust Display - Mark V and Mark V LM.....................................................4-13 CONSTCHK - Constants Check - Mark V and Mark V LM ..................................................................4-16 Operation......................................................................................................................................4-16 Diagnostic Counters Display - Mark V and Mark V LM ........................................................................4-17 File Type ......................................................................................................................................4-17 Using the Diagnostic Counters Display Program.........................................................................4-17 Logic Forcing Display - Mark V and Mark V LM..................................................................................4-21 File Structure................................................................................................................................4-22 Using the Logic Forcing Display Program...................................................................................4-23 PVOTE - Prevote Data Display - Mark V...............................................................................................4-30 Operation......................................................................................................................................4-30 Command Line Description .........................................................................................................4-31 Header Time tag...........................................................................................................................4-31
GEH-6126C Vol II HMI Application Guide
Contents • i
DABUILD - Diagnostic Alarm Build - Mark V......................................................................................4-32 DABUILD1 - Diagnostic Alarm Build - Mark V LM..................................................................4-33 DCBUILD1 - Diagnostic Counter Build - Mark V LM ...............................................................4-34 DIBUILD1 - IO_CFG Data File Build - Mark V LM..................................................................4-35 DPBUILD1 - PROM Sub-Directory Build..............................................................................................4-35 DDLOCATE - Data Dictionary Locate - Mark V and Mark V LM.............................................4-36 DDUTIL - Data Dictionary Utility...............................................................................................4-38 MK5MAKE - Mark V Make - Mark V and Mark V LM.............................................................4-39 FMVID - Fuel Metering Valve ID - Mark V LM.........................................................................4-41 LDB2RAM - Linearization Database to Memory - Mark V LM .................................................4-42 LDBCHK - Linearization Database Check - Mark V LM ..........................................................4-44 ALARM_L - Alarm List - Mark V ..............................................................................................4-45 CONSTSET - Constants Set - Mark V.........................................................................................4-46 EPA Log Configuration ...............................................................................................................4-48 SEQCOMPL - Sequencing Compiler - Mark V and Mark V LM................................................4-49 SEQDOCMT - Sequencing Documentor - Mark V and V LM....................................................4-54 SEQEDIT - Sequencing Editor - Mark V and Mark V LM ........................................................4-58 CSPPRINT - Control Sequence Program Printer - Mark V and Mark V LM ..............................4-66 TABLE_C - Table Compile - Mark V and Mark V LM ..............................................................4-68 EEPROM Downloader - Mark .....................................................................................................4-70 UDF - User Defined File - Mark V LM .......................................................................................4-72 Diagnostics ..............................................................................................................................................4-75 CARD_ID - Mark V and Mark V LM..........................................................................................4-75
Chapter 5 Mark VI
5-1
Mark VI Controller....................................................................................................................................5-1 Flash Downloader......................................................................................................................................5-1 EPA Log ....................................................................................................................................................5-1 Trend Recorder..........................................................................................................................................5-2 Auto Calibration ........................................................................................................................................5-2 Control Constants ......................................................................................................................................5-2 Forcing and Unforcing Logic Signals........................................................................................................5-2 Terminal Session Monitor .........................................................................................................................5-2
Chapter 6 HMI
6-1
Overview ...................................................................................................................................................6-1 Directory Structure and Files .........................................................................................................6-1 CIMPLICITY Directories ..............................................................................................................6-1 TCI Directories...............................................................................................................................6-2 Drive F: Files..................................................................................................................................6-2 Drive F: Sub-directories .................................................................................................................6-3 Drive G: Sub-directories ................................................................................................................6-3 Features, Utilities, and Tools.....................................................................................................................6-3 Device Communications Links ......................................................................................................6-3 Mark IV..........................................................................................................................................6-4 Mark IV Modbus............................................................................................................................6-5 Mark IV MA/MSP (Manufacturing Associates / Message Service Protocol)................................6-6 Mark IV Predefined Data Dump ....................................................................................................6-7 Mark V and Mark V LM ................................................................................................................6-7 Mark VI..........................................................................................................................................6-7 DCS Communications Links..........................................................................................................6-7 TCI Modbus Slave/Master .............................................................................................................6-8 CIMPLICITY Modbus Master.......................................................................................................6-8 GSM ...............................................................................................................................................6-9 Predefined Data Dump Transmitter................................................................................................6-9 EPA Log.........................................................................................................................................6-9 Real Time Logger Control - LOGGER ........................................................................................6-10 Using the Alarm Logger Dialog Box ...........................................................................................6-11
ii • Contents
GEH-6126C Vol II HMI Application Guide
Trip History..................................................................................................................................6-12 Trip History on the Mark V and Mark V LM (First Version).....................................................6-12 Trip History on the Mark V (New Version).................................................................................6-17 Trip History on the Mark VI ........................................................................................................6-23 DMD2SRC Demand to Source Conversion Program ..................................................................6-24 Starting the Demand Display to Source Conversion Program .....................................................6-29 Editing the Demand Display Source File .....................................................................................6-29 MODBUS List File Generators....................................................................................................6-30 MODBUS_L MODBUS List File Generator...............................................................................6-30 Cimmod_L Modbus List File Generator ......................................................................................6-31 Configuration ..........................................................................................................................................6-32 Introduction..................................................................................................................................6-32 TCI Control Panel Applet ............................................................................................................6-32 TCI Configuration........................................................................................................................6-36 TCI Configuration Files ...............................................................................................................6-37 TCI - Starting and Stopping .........................................................................................................6-39 TCI Modbus Configuration..........................................................................................................6-42 HMI Configuration Using HMI Device - Mark VI ......................................................................6-45 Configuration File (F:\AT_START.DAT And AT_STOP.DAT) ................................................6-54 Configuration File (F:\CONFIG.DAT) ........................................................................................6-56 Configuration File (F:\EGD_PUSH.DAT)...................................................................................6-59 Configuration File (F:\IO_PORTS.DAT) ....................................................................................6-60 Configuration File (F:\MODB_FWD.DAT) ................................................................................6-65 Configuration File (F:\PICONFIG.DIF) ......................................................................................6-67 Configuration File (F:\PI_PUSH.DAT) .......................................................................................6-69 Creating a Data Dictionary...........................................................................................................6-70 Configuration File (F:\TIMESYNC.DAT)...................................................................................6-77 Ethernet Alarm Protocol File (F:\ENATALM.DAT)...................................................................6-81 Exciter Configuration File (EX2000.DAT)..................................................................................6-82 EX2100 Data and Alarms - Mark VI ...........................................................................................6-82 Predefined Data Dump Configuration..........................................................................................6-83 Predefined Data Dump Transmitter (PDXMIT) Configuration ...................................................6-84 Time Synchronization Configuration...........................................................................................6-90 Time Zone Make - TZ_MAKE ....................................................................................................6-93 Time Zone Transition File (TIMEZONE.DAT) ..........................................................................6-96 Turbine Control Maintenance Icons.............................................................................................6-97 EM_ANA - Emissions Analysis ..................................................................................................6-99 Performance Monitor .................................................................................................................6-101 Using EMapView.......................................................................................................................6-102 Setup Procedure (Heavy Duty Gas Turbines, EMAP 7) ...........................................................6-103 Alarm Printing and Logging ......................................................................................................6-106 Alarm History ............................................................................................................................6-108 Disk Manager.............................................................................................................................6-109 Control Hierarchy (F:\CTRL_LOC.DAT) .................................................................................6-110 Setting the HMI Web Server Homepage....................................................................................6-116 Web Server Installation..............................................................................................................6-119 The EPA Logger ........................................................................................................................6-120 Diagnostics ............................................................................................................................................6-122 Diagnostic Tools ....................................................................................................................... 6-122 Basic Generic Questions ............................................................................................................6-122 Overview of Approach...............................................................................................................6-122 Alarm Dump 1 - ALMDUMP1 - Mark IV, Mark V, Mark V LM, and Mark VI ......................6-134 Alarm Dump 2 - ALMDUMP2..................................................................................................6-135 ARCWHO..................................................................................................................................6-135 CHECKCRC ..............................................................................................................................6-137 GBL2FILE - Global Section To File..........................................................................................6-138 MM_STAT - Modbus Master Statistics.....................................................................................6-139 M_STAT - Modbus Slave Statistics...........................................................................................6-140 PDD_STAT - Predefined Data Dump Status .............................................................................6-140 VIEWn Series ............................................................................................................................6-141 VIEWn Collection Programs .....................................................................................................6-141
GEH-6126C Vol II HMI Application Guide
Contents • iii
VIEW0 - View One Second Data...............................................................................................6-141 VIEW1 - View One Second Data...............................................................................................6-143 VIEW2 - View High-Speed Mark V Data .................................................................................6-144 VIEW2T - View High-Speed Mark V Data, Triggered .............................................................6-146 VIEWEGD - View Ethernet Global Data - Mark VI .................................................................6-149 VIEWPV - View High Speed Pre-Vote Turbine Data - Mark V................................................6-151 VIEWQ - View Multi-Processor High-Speed Turbine Data......................................................6-154 VIEWn Analysis Programs ........................................................................................................6-156 VIEW_LIM - View Data Analysis, Limits ................................................................................6-157 VIEW_SD - View Data Analysis, Standard Deviations.............................................................6-158 VIEW2ASC - Convert View Data to ASCII ..............................................................................6-159 Web-based Displays...................................................................................................................6-162 Accessing the Web displays .......................................................................................................6-163 WALMDUMP - Web Alarm Dump Display .............................................................................6-164 WANETC - Web ARCNET Counters........................................................................................6-166 WARCWHO - Web ARCWHO Display ...................................................................................6-167 WAUTHEN - Web Authentication of User ...............................................................................6-168 WCONST - Web Control Constants Display .............................................................................6-169 WDEMAND - Web Demand Display........................................................................................6-171 WGBL - Web Global Section Display .......................................................................................6-174 WHAERPT - Web Historical Alarm and Event Exception Report ............................................6-175 Historical Alarm and Event Summary Report............................................................................6-176 WHISTORY-Historical Alarm and Event Report by Day .........................................................6-178 WLFORCE - Web Logic Forcing Display.................................................................................6-180 WPBRO6 - Web Point Browser for Mark VI.............................................................................6-181 Mark VI Toolbox Browser Reports............................................................................................6-183 WPBROXD - TCI Data Dictionary Point Browser....................................................................6-187 XD Point Data Base Browser Report .........................................................................................6-188 WPROCESS - Web Process List................................................................................................6-190 WSUM_D03 - Web Summary of *.D03 Files ...........................................................................6-191
Chapter 7 Networks
7-1
Network Overview ....................................................................................................................................7-1 Mark IV System - Control System Freeway..............................................................................................7-1 CSF Characteristics ........................................................................................................................7-1 Mark V System - Stagelink .......................................................................................................................7-2 Terms of Reference ........................................................................................................................7-2 Stage Link Characteristics..............................................................................................................7-3 Cable Recommendations................................................................................................................7-4 Summary of Stage Link Topology Rules .......................................................................................7-4 Total Effective Distance Rules.......................................................................................................7-6 Redundant System Rules - Mark V................................................................................................7-7 Fiber-optics ....................................................................................................................................7-9 Review of Components ................................................................................................................7-10 System Considerations .................................................................................................................7-15 Mark VI Data Highway - Ethernet ..........................................................................................................7-16 Unit Data Highway.......................................................................................................................7-17 Plant Data Highway .....................................................................................................................7-17 Mark VI Network Rules...............................................................................................................7-18 Network Redundancy...................................................................................................................7-18 Ethernet Network Equipment.......................................................................................................7-20 Serial Link Network - Mark IV and DCS serial links ..................................................................7-20 HMI Network Configuration ...................................................................................................................7-21 Network Diagnostics ...............................................................................................................................7-22 Ping Network Diagnostic Utility..................................................................................................7-24 Firewall Settings...........................................................................................................................7-26
iv • Contents
GEH-6126C Vol II HMI Application Guide
Chapter 8 CIMPLICITY
8-1
Overview ...................................................................................................................................................8-1 Introduction....................................................................................................................................8-1 Features, Utilities, and Tools.....................................................................................................................8-2 CIMPLICITY Optional Displays ...................................................................................................8-2 Manual Synchronizing Display - Mark V, Mark V LM.................................................................8-2 Manual Synchronizing Display - Mark VI.....................................................................................8-6 Triggered Plot - Mark V and Mark V LM......................................................................................8-6 Reactive Capability Display - Mark IV, V, V LM, VI...................................................................8-8 Configuration ............................................................................................................................................8-9 Introduction....................................................................................................................................8-9 Frame Containers and Single Screens ............................................................................................8-9 Using Workbench ..........................................................................................................................8-9 Opening a Project.........................................................................................................................8-10 CIMPLICITY - Starting and Stopping a Project..........................................................................8-11 Configuring Users ........................................................................................................................8-12 Configuring Ports.........................................................................................................................8-15 Adding Devices............................................................................................................................8-17 Configuring Resources.................................................................................................................8-18 Allowing Local System Account Access .....................................................................................8-20 Alarm Filtering in HMI Servers ...................................................................................................8-20 Configuring Alarm Filters............................................................................................................8-21 Alarm Screen in a Frame Container - Mark IV, V, and V LM ....................................................8-23 Examples of Screens for Filtered Alarms.....................................................................................8-30 Currently Implemented Filters .....................................................................................................8-32 Single Screen Features - Mark VI ................................................................................................8-32 Extended Alarm Commands ........................................................................................................8-39 External Alarm Manager..............................................................................................................8-40 Signal Manager - Mark V and Mark V LM .................................................................................8-40 Alarms..........................................................................................................................................8-42 Importing Signals.........................................................................................................................8-43 Toolbox HMI Device - Mark VI ..................................................................................................8-45 System Database ..........................................................................................................................8-45 TCI - CIMPLICITY Modbus Data Interface ...............................................................................8-46 OLE for Process Controls (OPC) .................................................................................................8-46 Diagnostics ..............................................................................................................................................8-47 System Status Logs ......................................................................................................................8-47 Viewing the Status Log................................................................................................................8-47 Viewing the System Log..............................................................................................................8-48 Viewing the Project and System Status Logs...............................................................................8-48 System Log Files..........................................................................................................................8-49 Project Log Files ..........................................................................................................................8-49 Gather File Utility ........................................................................................................................8-49 How to use the Gather File Utility ...............................................................................................8-49
Glossary of Terms
Index
GEH-6126C Vol II HMI Application Guide
G-1
I-1
Contents • v
Notes
vi • Contents
GEH-6126C Vol II HMI Application Guide
CHAPTER 1
Chapter 1 Overview Introduction The Human-Machine Interface (HMI) for SPEEDTRONIC Turbine Control Application Guide Vol. II describes the maintenance features for the HMI used with ™ GE's SPEEDTRONIC Turbine Control Systems. It is written as a guide to help the engineer configure the HMI Turbine Control Interface. Volume 1 covers use of the HMI by the operator. Refer to GEH-6126, HMI for SPEEDTRONIC Turbine Control, Operators Guide, Vol. I and GFK-1180, CIMPLICITY HMI Plant Edition Base System User Manual for information not covered here.
HMI Summary The HMI is an operator interface system based on client-server technology, providing data collection, logging, and display of power island and auxiliary process data. The HMI also has the ability to issue operator commands to the control equipment. Depending on the requirements, the product can be configured for just turbine-related data, or for broader applications that include balance of plant process data.
System Configuration The HMI provides operator display and control for the Mark IV, Mark V, Mark V LM, and Mark VI controller types. The controllers and supported networks are as follows: Controller Type Supported Controller Communication Network Mark IV
Control System Freeway (CSF) ARCNET-based network, serial communication (Modbus and Serial MSP)
Mark V, Mark V LM Stagelink (ARCNET-based network) Mark VI
GEH-6126C Vol II HMI Control Application Guide
Unit Data Highway (UDH), Ethernet-based network,
Chapter 1 Overview • 1-1
Plant Data Highway (Ethernet)
Data
Data
HMI Server # 1
HMI Viewer
HMI Server # 2
Historian
TR
Mark VI Unit Data Highway (Ethernet)
Mark IV Control System Freeway (CSF) Mark V Stagelink Mark VI Turbine Control I/O
Mark IV Turbine Control I/O
Mark V Turbine Control I/O
Data Paths to the HMI Servers and Viewers from Various Controllers
In the Mark VI system, the controllers and other devices communicate with the HMI Server through the Ethernet-based Unit Data Highway and through RS-232C lines. The HMI Server uses the Plant Data Highway to communicate with the HMI Viewers.
System Capability The HMI provides an online database for collecting and storing data from multiple controllers. For TCI version 1.6, points can be collected from as many as eight turbine controls. For later versions of TCI, the number of turbine controls has been increased; consult GE for advice on your system.
Data Collection Data is collected by various methods, depending on the product. For the Mark IV, Mark V, Mark V LM, and Mark VI, the process is centered about the Control Signal Database (CSDB), which is the real-time database in the controller. The control scans the CSDB for alarm and event state changes. When a state change occurs, or a sequence of events occurs, these are sent to the HMI. These points are time tagged by the controller.
1-2 • Chapter 1 Overview
GEH-6126C Vol II HMI Application Guide
HMI Terminology Definitions of three important terms used in this manual are as follows: •
The term unit is used in the HMI configuration and refers to the turbine control being configured. Unit has also been used to refer to the physical combination of the turbine, generator, and exciter.
•
The term controller refers to the Mark IV, Mark V, Mark VI, or PLC control equipment in the control panel.
•
The term panel refers to the cabinet containing the controllers and I/O boards. In prior manuals the term panel has been used to refer to the controller.
Text Conventions Convention
Meaning A procedure follows.
Numbered list
Procedural steps to be followed in order (for example, 1, 2, 3).
Alphabetized list
Procedural substeps (of numbered steps) to be followed in order (for example, a, b, c).
Bulleted (•) list
Related items or procedures, but order does not matter. A procedure with only one step.
Bold
Provides emphasis.
Arial Bold
When describing software, indicates the actual command or option that is chosen from a menu or dialog box.
Italic
Indicates a word used as a word, or a letter used as a letter. For example, the display should now read SDB has stopped. Italic also indicates new terms, margin notes, and the titles of figures and chapters in the guide.
Monospace
Represents examples of screen text or words and characters that are typed in a text box or at the command prompt.
GEH-6126C Vol II HMI Application Guide
Chapter 1 Overview • 1-3
Related Documentation The following documents apply to the HMI and SPEEDTRONIC turbine controllers and can help in understanding HMI operation:
1-4 • Chapter 1 Overview
•
GEH-6126, HMI for SPEEDTRONIC Turbine Control, Operators Guide, Vol. I
•
GEI-100516, GSM for SPEEDTRONIC Turbine Control
•
GEI-100517, Modbus for SPEEDTRONIC Turbine Control
•
GEH-6421, System Guide for the SPEEDTRONIC Mark VI Turbine Control
•
GEH-6195, SPEEDTRONIC Mark V Turbine Control –Application Manual
•
GEH-6403, Toolbox for Configuring a Mark VI Turbine Controller
•
GEH-6422A, Turbine Historian System Guide
•
GEK-83886, MARK IV SPEEDTRONIC Gas Turbine Control Maintenance Manual
•
GEK-83885, Mark IV SPEEDTRONIC Gas Turbine Control Operator's Manual
•
GEH-5979, SPEEDTRONIC Mark V Turbine Control User's Manual
•
GEH-5980, SPEEDTRONIC Mark V Turbine Control Maintenance Manual
•
GEH-6354, SPEEDTRONIC Turbine Control Panel Manual Overview
GEH-6126C Vol II HMI Application Guide
CHAPTER 2
Chapter 2 Installation Introduction A facility receives the HMI pre-loaded with all the programs and customized software required for the customer’s application. It is then configured during installation to automatically log on and open to the main operator screen when powered-up. This chapter covers the installation, setup, and checkout of the HMI.
Login and Startup Initial Power Up To start up the HMI and open your application 1
Power up the computer if it is off. If Auto Log On is enabled the computer should start the CIMPLICITY application CimView and its associated main operation display automatically. If a Log On dialog box appears, type in Oper in the User Name field (User names are not case sensitive) and its associated password (default is no password) in the Password field.
2
If the computer is already running, press the three keys Ctrl+Alt+Delete all at once to bring up the Log On dialog box to change the User to Oper.
3
If the main operation display does not start automatically, double-click the desktop icon, typically Unit_Control.cim.
When the computer starts up, it starts all CIMPLICITY programs (refer to the following screen Typical Services Starting Display) and displays the main operation display (refer to Example of a Typical HMI Display). Note GFK-1180 describes CimView in detail for the Mark V. Note The HMI displays for the user's system are CimView displays (*.cim files), which can open before CIMPLICITY finishes loading. If at first the display is not animated or setpoints fail, wait a few minutes for the startup to complete before beginning operation. During the startup process do not click any Cancel or Close buttons. Note To login to a different account such as Administrator or maint (abbreviation for maintenance), it is necessary to hold down the Shift key while the computer is booting. This will open a login box where the user name and password can be entered.
GEH-6126C Vol II HMI Application Guide
Chapter 2 Installation • 2-1
Do not click Close button as it may cancel the complete loading of essential services before the HMI starts.
Click to manually start HMI if it does not start automatically. Typical Services Starting Display
Example of a Typical HMI Display
2-2 • Chapter 2 Installation
GEH-6126C Vol II HMI Application Guide
CIMPLICITY Project Check that the CIMPLICITY® software is loaded, its shortcuts appear on the Start menu and the CIMPLICITY projectis located in directory C:\Site\Cimproj.
Check Usernames and Passwords The user accounts and associated passwords need to be verified at initial unit checkout and later if there are problems logging into specific user accounts. ®
®
Both Windows 2000 and Windows XP are covered in this section because there are differences in the procedures for checking for the existence of proper user accounts. Password text cannot be read directly because passwords are obscured by the operating system by displaying representative asterisks in place of the actual password. Passwords can only be verified by attempting to log on to an account with the associated password. If the logon procedure fails then the password may be incorrect and can be reset from the Administrator account. Typical GE systems have three (possibly more) accounts on the pc: •
Administrator (with password)
•
Oper (typically with no password)
•
Maintenance (with password) If the ADMINISTRATOR password is changed and cannot be remembered then there is no way to retrieve it from the HMI. Store all passwords in a secure place.
Note There should be a backup of the HMI hard drive or a Restore Disk (Refer to Microsoft Windows documentation). If this is not the case, a backup of the HMI hard drive or a Password Restore Disk should be made before making any changes. Refer to the Microsoft Windows documentation on how to create a Password Restore Disk. You may need to obtain a floppy drive for your system if one is not present. Note The client can add or remove additional user accounts as needed. Refer to Microsoft Windows documentation for further information. User accounts, other than those setup by GE, may not operate the HMI properly.
Windows 2000 You must be logged in as administrator to perform procedure
To check the Windows 2000 usernames and reset password 1
From the Start menu, select Settings, Control Panel.
2
The Control Panel opens.
GEH-6126C Vol II HMI Application Guide
Chapter 2 Installation • 2-3
2-4 • Chapter 2 Installation
3
Double-click Administrative Tools. A new window opens with a list of administrative tools.
4
Double-click Computer Management. A new window opens with a list of computer management tools.
5
Expand System Tools by clicking the + next to it.
6
Expand Local Users and Groups by clicking the + next to it.
7
Select User. A list of users on the computer displays in the left pane. Right click on a User name to open a drop-down box.
8
Click Set Password. The Set Password dialog box opens. Enter the new password in the New password and the Confirm password fields. Click OK. Close all open windows. The new password takes effect immediately. Confirm, by logging on as that user.
GEH-6126C Vol II HMI Application Guide
Windows XP You must be logged in as administrator to perform procedure
To check the Windows XP usernames and reset password 1
From the Start menu, select Control Panel.
2
The Control Panel opens.
3
Double-click Administrative Tools. A new window opens with a list of administrative tools.
4
Double-click Computer Management. A new window opens with a list of computer management tools.
5
Expand System Tools by clicking the + next to it.
6
Expand Local Users and Groups by clicking the + next to it.
7
Select User. A list of users on the computer will display in the right pane. Right click on a User, which will open a drop-down menu window. Click Set Password.
GEH-6126C Vol II HMI Application Guide
Chapter 2 Installation • 2-5
8
A Warning dialog box opens.
9
Click Proceed to change the password. The Set Password dialog box opens.
10 Enter the desired Password in the New Passsword and Confirm password fields, then click OK to reset password.
11 Click OK. Close opened windows.
2-6 • Chapter 2 Installation
GEH-6126C Vol II HMI Application Guide
CHAPTER 3
Chapter 3 Mark IV Overview The Mark IV configuration is PROM-based, not downloaded from the HMI. There are no tools on the HMI to configure and download a Mark IV. All control changes are made directly either by using the Mark IV front panel display or a terminal connected to the Mark IV.
Features, Utilities, and Tools DDVAL - Data Dictionary Validation DDVAL reads the signal definitions in the HMI data dictionary and the definitions in the controller. It then compares the two definitions to check that they are the same, and thereby validates the data dictionary. DDVAL requires the user add command line parameters. Help information is available by typing DDVAL with no parameters or DDVAL /? at the command prompt. See below for help information. When DDVAL scans the Mark IV controller and compares it against the HMI Data Dictionary it can generate the following messages: ERROR - Data Dictionary point number 0x1841 with name "L25TX_ALM" was an invalid name size from the Mark IV. This message is produced if the HMI cannot retrieve the point record from the Mark IV for the desired point due to an issue in the Mark IV. ERROR - Data Dictionary point number 0x2044 with name "TNH" and type "R4" is type "F2" in the Mark IV. This message is produced if the HMI finds that the point type differs between the HMI and the Mark IV. ERROR - Data Dictionary point number 0x1838 with name "L26GHXH" translates to a bad Mark IV point name. This message is produced if the Mark IV reports that it is unable to identify the requested point and therefore cannot return its point name. This sometimes means that the point number requested is outside the Mark IV point tables. ERROR - Data Dictionary point number 0x20E1 with name "DWATT" translates to Mark IV point name "DW".
GEH-6126C Vol II HMI Application Guide
Chapter 3 Mark IV • 3-1
This message is produced if the HMI finds that the name of the point in the HMI is different than the name of the point reported by the Mark IV. In some cases this will be because the Mark IV considers it a spare (unused) point but the HMI believes that the point is used (or vice versa). Success- Data Dictionary point number 0x2A7A with name "TTXSPL" validated. This message is produced only if the /VERBOSE option is used and there are no errors validating this point. "ERROR -
Unknown error in point "L4".
This message is produced if there is an error outside of the normal errors shown above. It typically means that something has gone wrong in the process (such as the Mark IV was shut down in the middle of the scan). It is worth retrying the validation again to see if it clears the error.
The on-line help message generated is: This program does Mark IV point validation. DDVal /unit= [/file=] [/verbose] = Mark IV unit name or "ALL" to check all Mark IV units. = Optional error file name. If this file is specified, all point errors will be put in it and not on the screen. /verbose = Option to display successfully validated points.
3-2 • Chapter 3 Mark IV
GEH-6126C Vol II HMI Application Guide
CHAPTER 4
Chapter 4 Mark V Mark V Controller HMI Unit-Specific Directory Each Mark V controller communicating with an HMI has a unit-specific directory and subdirectory on the HMI hard drive. These directories have names referring to the unit. They are located on the F: drive and are defined in F:\CONFIG.DAT. The unit-specific directory for the first unit is usually named F:\UNIT1, and its subdirectory is F:\UNIT1\PROM. Subsequent unit-specific directories and their subdirectories are F:\UNIT2 and F:\UNIT2\PROM, F:\UNIT3 and F:\UNIT3\PROM, and so on. Configuration files contained in a unit-specific directory can be broken up into five groups as follows: •
Assignment files
•
Data Dictionary files
•
I/O Configuration Constant files
•
Table files
•
CSP segment files.
These five groups of files are discussed in the following sections.
Assignment Files Assignment files, while not downloaded to a Mark V controller, contain unit-specific control signal database pointnames and scale types for many of the control signals. The information in assignment files is used when creating the primary unit Data Dictionary file, UNITDATA.DAT. This file contains all of the unit-specific control signal database pointname information. For each unit, GE provides the following four assignment files in the HMI’s unitspecific directory: IO.ASG, FACTORY.ASG, ALLOCSSP.ASG, and SITE.ASG. These are ASCII (American Standard Code for Information Interchange) text files, sometimes called plain text files. They can be viewed or modified using any ASCII text editor. When I/O devices are connected to a Mark V controller, they must be assigned a control signal database pointname and a scale type. I/O devices are specified in the I/O assignment file, IO.ASG. In this file, a control signal database pointname and a scale type are assigned to the location, which is being used for a particular device.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-1
A Mark V controller has multiple spare control signal database memory locations (points) which are available for use or assignment. To make use of these spare points for new or additional control and protection functions it is necessary to define the type of point required, the control signal database pointname, and the scale code. These definitions are made in one of three assignment files. The file in which the assignment is made depends on the type of signal required as well as on who is making the assignment, that is, factory personnel or site personnel, customer or GEPS/Business Associate field personnel. The files are as follows: •
FACTORY.ASG is used for control signal database pointnames and scale types. GE or GEPS’s business associates assign these to spare memory locations in FACTORY.ASG. This file can be altered to accommodate customization of the CSP for a particular application.
•
ALLOCSSP.ASG (ALLOCation of Structured Software Points) is used for additional I/O, spare double-word variables, and spare alarm logic points. Spare double-word variables and alarm logic points, which are required, are assigned pointnames and scale types in ALLOCSSP.ASG. Both factory (GE and GEPS Business Associates) and field/site personnel make assignments for these two types of points in ALLOCSSP.ASG.
•
SITE.ASG is used for points other than I/O, double-word variables, and alarm logic points. Customer and/or GEPS/Business Associate field personnel make assignments of signal pointnames and scale types to spare control signal database memory locations in SITE.ASG.
Data Dictionary Files Data Dictionary files contain information about unit-specific control signal database pointnames, alarm text messages for both process and diagnostic alarms, and display information for signal pointnames, such as type, units, and messages. The primary unit Data Dictionary file, UNITDATA.DAT, can be created in the unit-specific directory. Assignment files and template files are used in the creation of UNITDATA.DAT. Many HMI configuration programs require information from UNITDATA.DAT when modifying or compiling unit configuration files for downloading. Some control signal database pointnames are common to applications (steam turbines or gas turbines) and must reside in memory at specific locations and must not be changed. These common, fixed pointnames are contained in template files. The fixed control-signal database pointnames, the I/O assignments, and spare memory locations being specified in the assignment files must be included in the UNITDATA.DAT file. If any new assignments are made, they must be included in a new UNITDATA.DAT file. The program DDLOCATE creates UNITDATA.DAT. This program uses the assignment files which are specified at the time DDLOCATE is run, in addition to three template files in the unit-specific PROM sub-directory: UNITDATA.TPL, UNITFREE.TPL, and UNITMAP.TPL. Information from both the assignment files and the .TPL files (TPL stands for template) in the PROM sub-directory are used to create the unit-specific UNITDATA.DAT file. The command-line format for executing DDLOCATE is as follows: DDLOCATE IO.ASG FACTORY.ASG ALLOCSSP.ASG SITE.ASG Although their order is unimportant, all assignment files for a particular unit must be specified on the command line each time DDLOCATE is run. If a modification is made to ALLOCSSP.ASG only, such as to use a spare alarm logic point, all the assignment files must be specified on the command line when DDLOCATE is run. Each time DDLOCATE is run, a new UNITDATA.DAT file is created; all the assignments must be included in this new file. DDLOCATE is run as part of MK5MAKE.BAT. For details refer to the section on MK5MAKE.BAT
4-2 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Other Data Dictionary files that must be present in the unit-specific directory for proper operation include: •
ALARM.DAT containing process and diagnostic alarm messages (maximum case).
•
ENUMDATA.DAT containing display messages for Enumerated Data types.
•
ENGLISH.DAT containing scale code information.
•
METRIC.DAT containing scale code information.
The following unit-specific Data Dictionary files are optional and not required for proper HMI operation: •
Unit-specific Data Dictionary files are not downloaded to a Mark V controller, but are loaded into the HMI’s RAM each time the HMI is turned on or reset. This information is used to scale and display control signal database pointname information on the HMI as well as for alarm and event logging. As discussed above, some HMI programs require information from UNITDATA.DAT.
I/O Configuration Constants I/O configuration constants are used to scale or condition signals to and from I/O devices connected to the Mark V controller. IO configuration files are downloaded to the controller. I/O devices include pressure transducers, temperature switches, electro-hydraulic servo-valves, position transducers or reactors, thermocouples, and RTDs. Many of the same type of I/O devices can have differing outputs or require dissimilar inputs. For example, thermocouples produce a millivoltage proportional to temperature; however, a Type K thermocouple produces a different millivoltage than a Type T for the same temperature. An I/O configuration constant is used to appropriately scale the input signals from the various types of thermocouples. As another example, milliamp transducers come in several output ranges such as 4-20 mA, 0-1 mA, and 0-10 mA. More than one type of milliamp transducer can be used on a unit or its auxiliaries, so I/O configuration constants are used to scale the input for use in the controller. I/O configuration constants are initially contained in the I/O configuration files in the unit-specific directory. The three files are as follows: •
IOCFG_Q.DAT
•
IOCFG_C.DAT
•
IOCFG_D.DAT
All three files are present in the unit-specific directory for each Mark V controller that communicates with the HMI, even if the controller does not include a backup communication processor. The information in these files is in hexadecimal format, and can be viewed using the I/O configurator program, IO_CFG, usually available from the HMI Main Menu. The screens presented in the I/O configurator depend on the configuration data files found in the unit PROM directory. PROM\IO_CFG.DAT contains the list of files required for the I/O configurator, such as TCCA_CFG.DAT. The I/O configuration files can be downloaded to a Mark V controller without any intermediate steps such as compiling.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-3
Table Files The majority of unit-specific configuration files are Table Files. These files contain tabular listings of CSDB pointnames and information about their type, use, and value. Table Files contain information in an ASCII text format which, when compiled and downloaded to the controller, is used by functions such as the Control Sequence Program and the loggers. Several of the source Table Files are dummy files containing no information, created for symmetry and possible future use. Modifications can be made to any of the ASCII text Table Files (known as source files) using any ASCII text editor. Prior to downloading the information in the source Table Files, it must be converted into binary format using the Table Compiler program, TABLE_C. The command line format for executing the Table Compiler to compile all the Table Files is as follows: TABLE_C ALL Using the Table Compiler, information in the source Table Files is converted into binary format in files with the same filename but with an .AP1 filename extension. For example, CONST_Q.SRC is compiled into CONST_Q.AP1. The Table Compiler uses information contained in UNITDATA.DAT and one of the scale code files (ENGLISH.SCA by default) when converting the source files into hex files. Since no CSDB pointnames are downloaded to the Mark V controller, the Table Compiler finds the software signal pointname in UNITDATA.DAT, and uses its memory location/address, scale code, and point type when creating the downloadable Table Files. Source Table Files
4-4 • Chapter 4 Mark V
Table Files
Description
CONST_B.SRC
Default file; blank
CONST_Q.SRC
All control constants and their (initial) values
EPA_B.SRC
A list of pointnames for emissions logging purposes
EPA_Q.SRC
Default file; blank
MAOUT_B.SRC
Default file; blank
MAOUT_Q.SRC
A list of pointnames and ranges for mA outputs
CHNG_B.SRC
A list of analog pointnames and ranges monitored for excursions and logged as events to the Historian
CHNG_Q.SRC
A list of analog pointnames and ranges monitored for excursions and logged as events to the Historian
EVENT_B.SRC
A list of logic signal pointnames logged as events
EVENT_Q.SRC
A list of logic signal pointnames logged as events
TOTT_B.SRC
A list of pointnames to configure the Hold List
TOTT_Q.SRC
A list of pointnames for which data is totalized
HIST_B.SRC
A list of pointnames included in the Trip History log, for Mark V
HIST_Q.SRC
A list of pointnames included in the Trip History log, for Mark V LM
CBLR_B.SRC
A list of digital inputs to which are associated with command pushbuttons in the CSP
CBLR_Q.SRC
A list of digital inputs to which are associated with command pushbuttons in the CSP
GEH-6126C Vol II HMI Application Guide
CSP Segment Files A Control Sequence Program (CSP) segment is an ASCII text file containing information such as control blocks, parameters, comments, and relay ladder diagram sequencing. The turbine control program is contained in the CSP. The CSP for a unit is made up of at least two segments, one for and one for . CSP segments can be run at different frequencies, such as 4, 8, 16, or 32 Hz depending on the application, and at different skews, or offsets. Segments are subsets of the CSP containing sequencing functions, which are related and must be run at a certain frequency. There can be as many as eight CSP segments for and eight CSP segments for . CSP segments can be viewed and modified using the Control Sequence Editor program, SEQEDIT.EXE, available in the HMI Turbine Control Maintenance section. In some cases, all of the unit's control and protection (other than emergency overspeed trip and servo regulator loops) can be accomplished in one CSP segment in . CSP segment files can have any valid DOS filename of eight characters maximum but must have an .SRC filename extension. Refer to the section Control Sequence Editor. Prior to downloading to a Mark V controller, the CSP must be converted to binary (AP1) format using the Control Sequence Compiler (CSP Compiler). The CSP Compiler uses information from UNITDATA.DAT, Big Block definition files in the unit-specific PROM subdirectory (PRIMITIV.DEF and BIGBLOCK.DEF), and the names of CSP segment files, which have been specified in a unit-specific control sequencing configuration file, MSTR_SEQ.CFG. The CSP Compiler creates binary format downloadable CSP files, SEQ_B.AP1 and SEQ_Q.AP1. For Mark V LM the file is SEQ.AP1. The CSP Compiler can be run from the HMI Turbine Control Maintenance section or at the command line of the unit-specific directory with the SEQCOMPL command. Text file MSTR_SEQ.CFG contains two sections defining the names of CSP segment files, which are compiled for ’s CSP and ’s CSP. In addition, it defines the rates, offsets, and skews as well as the order in which CSP segments are compiled and run. The first segment file specified is run first, the second segment file specified is run next, the third segment file specified is run next, and so on. Refer to the section MSTR_SEQ.CFG. CSP segments are initially created using Big Block Library (BBL), relay ladder diagram rungs, and comment rungs. They are customized by GE or its Business Associates to match a particular application or customer’s requirements, and can be modified in the field using the Control Sequence Editor. New CSP segments can be created using the Control Sequence Editor. If a new segment is created, the name of a new segment must be added to MSTR_SEQ.CFG to be included in the downloaded CSP files. The maximum number of segments per and that can be compiled is eight. For the Mark V LM it is 16.
Compiling Unit-Specific Configuration Files The unit-specific Table and CSP files must be converted to binary format prior to downloading to the Mark V controllers. This is done using the Table Compiler program directly or the MK5MAKE.BAT batch file, which calls the Table Compiler program. Refer to the sections on the Table Compiler and MK5MAKE for more details.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-5
Downloading Unit-Specific Configuration Files When the unit-specific ASCII text Table and CSP files are compiled to binary format, they, along with the I/O Configuration Constants, can be downloaded to the Mark V controllers using the EEPROM Downloader program (EEPROM). EEPROM is available from the HMI command line. The EEPROM Downloader program transfers unit configuration file information, sometimes known as EEPROM partitions or sections, from the HMI's hard drive to the controller. Refer to the section on the EEPROM Downloader for more details.
Control Constants Special care is needed when modifying control constants in the CONST_Q.SRC file. These constants are downloaded to non-volatile memory in the controller. They are copied to RAM memory when the control is initialized and are used during the CSP execution. The values of control constants in the processor’s RAM can be changed using the Control Constant Adjust Display program by selecting a constant on the HMI display. Control constants can be adjusted while the unit is running, although the rate of change of the control constant’s value is quite slow when the unit is running to prevent a rapid change from tripping the turbine. Refer to the section on the Control Constant Adjust Display. A feature of the Control Constants Adjust Display is to copy the control constant, whose value was changed in RAM, to the controller’s nonvolatile memory. Clicking on the target Storage Update and then clicking on the OK button in the Execute Dialog Box copy the current RAM value of every control constant to the processor’s non-volatile memory. However, there is no automatic method of updating the values of control constants in the configuration file CONST_Q.SRC. If a control constant in a Mark V controller is modified using the Control Constant Adjust Display, and the value of the control constant in CONST_Q.SRC is not subsequently changed to match the unit’s value, a re-compiling and downloading of control constants causes the controllers nonvolatile storage value of the control constant to revert to the old value in CONST_Q.SRC. Note Whenever a control constant is modified using the Control Constant Adjust Display, the control constant source Table File, CONST_Q.SRC, should be edited to reflect the new value and compiled. This assures the Control Constant Table hexadecimal file, CONST_Q.DAT, contains the new value and any subsequent downloads will be done with the correct value. It is possible to generate a list of the current values of control constants in the controller using the CONSTCHK program. Refer to the section on CONSTCHK program.
4-6 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Auto-Calibrate Display The Autocalibrate function in the controller allows a user to calibrate the feedback signals in the position control sections of the various Servo Valve Outputs (SVOs). This consists of establishing the relationship between the required position and the actual position. The servo board in the controller does the calibration process, with the required inputs downloaded to it from the HMI. The results of the calibration are then collected for display by the HMI.
Mark V Auto Calibration In addition to the calibration function, two different verify functions are available. These verify functions provide high-speed data (128 Hz) taken while ramping from one end stop to the other. Verify under position control ramps the position at a constant rate and plots the current, while verify under current control holds the current constant and plots the position. A manual control mode is provided which allows the user to specify a desired position. This is useful for positioning a valve at a desired position when the normal regulator is an integrator. The HMI has a special display used to access the autocalibrate functions in the Mark V control. The autocalibrate Display uses a data file to define the calibration parameters and the format of the screen display for each SVO.
File Type This section describes the format of the data file, ACALIB.DAT. The program AUTOCAL.EXE runs the Autocal function. ACALIB.DAT defines the calibration parameters and the format of the screen display for each SVO. ACALIB.DAT must be located in the unit configuration directory, F:\UNITn. The three main sections to this data file are Status Codes, Trace Information, and Display Definitions. •
Status Codes converts I/O board status codes to text. These are used to decipher the hexadecimal I/O board state information to text for ease of understanding.
•
Trace Information defines how many position traces are to be displayed for each regulator type when displaying a Verify Under Current Control or Verify Under Position Control plot.
•
Display Definitions section defines all the different Autocal displays for each regulator. Each definition includes items such as the processor, I/O board, I/O processor number, regulator number, positions at current saturation, logic permissive for sending commands, and the data to be displayed. When Autocal is run, it displays a list of the regulators for user selection.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-7
Menu Selections
Options
Commands
Description
File Menu FILE:SAVE AS
Saves the currently displayed text from the data window to a text file.
FILE:PRINT
Displays the standard Print dialog box. Use this menu selection to print the data window.
FILE:PRINTER SETUP
Displays the standard Printer Setup dialog box for selecting a printer and its characteristics.
FILE:EXIT
Closes the Auto Calibrate Display.
Edit Menu EDIT:COPY EDIT:SELECT UNIT
View Menu VIEW:TOOLBAR VIEW:STATUS BAR
Help Menu HELP: HELP TOPICS HELP:ABOUT
Copies Auto Calibrate Data Window to the Clipboard as a bitmap. Displays the Unit Select dialog box which lists all the unit controls defined in the turbine control interface. Doubleclicking the left mouse button on aunit name, or highlighting a unit name then selecting OK selects the unit. Toggles the toolbar on and off. Toggles the status bar on and off. Calls the Autocalibrate program help. Presents the Autocalibrate Display About dialog box.
Command Pushbutton The command pushbuttons in the button-view window have the following standard colors: •
Red - Immediate acting
•
Green - Arm/Run; this requires confirmation before sending the command
•
Gray - Setpoint: The user enters a desired setpoint
Not all command pushbuttons are available at all times. Their visibility depends on the control state and permissive logic. Personnel should keep clear of the area during an automatic calibration sequence or when one of the automatic calibration options is run. The hydraulic actuator is moving the device from mechanical stop to mechanical stop as fast as four seconds using full hydraulic pressure. If no pushbuttons are visible, then either one of the following conditions is occurring: •
The machine is not in its correct test state.
•
The test permissive, usually L3ADJ is not TRUE.
•
The Autocal function is being used by another Autocalibrate window, HMI, or .
•
Communications to the controller have failed.
The Enable Commands pushbutton must be activated to allow the user to issue further commands to the unit. Read and heed the warnings accompanying this command.
4-8 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Enable Commands. The datafile can define a logic Permissive signal that must be in a required state before calibration commands can be sent to the Mark V. If the permissive signal is found to be valid, the Enable Commands pushbutton is visible and a warning message is displayed. Read and heed the warnings accompanying this command. Start Calibrate. Start Calibrate sends the command to the Mark V to start Autocal. This runs the position calibrate function and reports the resulting information on the display. When all required permissives are met and hydraulic operation of the valve is possible, Autocal controls the servo-valve output current(s) to the servo-valve device to position the actuator or device. The Mark V then measures the feedback voltages and calculates I/O Configuration Constants. The currents determined during the Autocal procedure are stored in TCQA RAM. Verify Position. Verify Position starts the verify under position control function. This function ramps the actuator from actuator mechanical minimum travel to mechanical maximum travel then ramps back again at a constant rate (for example, constant inches per minute). While verifying under position control, Autocal causes the servo-valve output current to increase or decrease as necessary to maintain the fixed rate of travel as indicated by the LVDT/R feedback signal(s). Servo current data is collected at 128 Hz rate and placed in the Mark V's buffer. If the servo-valve, the actuator, or device is not mechanically binding or sticking, the amount of current required to maintain the fixed rate of travel should be constant. Such things as valve packing, a scored hydraulic actuator cylinder, or a damaged valve stem could cause such mechanical binding. The results of verifying under position control can be plotted on the HMI and stored or printed for further analysis. Verify Current. Verify Current starts the verify under current control function. This function causes Autocal to output a fixed servo-valve output current that causes the device to move at a constant rate of approximately 30% travel-per-second from actuator minimum mechanical to maximum mechanical travel and back. If the processor is re-booted or another valve calibrated, the current values from the most recent Autocal procedure are lost. If no values exist in TCQA RAM for moving the device, a message is displayed indicating that the device must be calibrated before the operation can occur. The current for each direction is different because of the null bias current required to overcome the fail-safe spring bias in the servo-valve. Enable Manual. Enables Manual Setpoint control from the Autocalibrate Display. Manual Setpoint. Manual Setpoint defines the position reference if manual control is enabled. Manual control is used to check the accuracy of calibration or to hold the device in some position for mechanical inspection or maintenance. The desired position is entered, Enable Manual is selected, and then the valve is driven to the setpoint position. Changing the Manual Setpoint when manual control is enabled ramps the device at a fixed 30% stroke-per-second rate to the new setpoint. Idle. Idle halts any calibration, verify, or manual control and clears any status or error condition from a previous command. View Verify. View Verify is used to collect and plot data in the capture buffer.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-9
Command Line Arguments The Autocalibrate display can be started from the command line, or the user can create screen icons using the following example: g:\exec\autocal.exe The Autocalibrate display can be launched with the following optional argument to quickly bring the display to a desired configuration: /UNIT: The following example specifies the unit name as T1: g:\exec\autocal.exe /UNIT:T1 Display actions are as follows: •
Valid Unit: The Autocalibrate display is opened with the unit already selected.
•
Invalid Unit or None: A blank screen is displayed if an invalid unit is specified on the command line.
•
Single Unit Sites: The unit parameter is ignored on single unit sites.
Screen Description The Autocalibrate screen consists of three windows as follows: •
Tree-view window
•
Autocalibrate Data window
•
Button-view window
The tree-view is on the left side of the display, the Autocalibrate data is in the center, and the Button-view is on the right. The three portions are separated by movable splitter bars. The program can display and update one set of Autocalibrate test data at a time. Tree-view. The Autocalibrate tree-view window is a graphical window that depicts the hierarchy of Unit and regulators available for calibration. The tree-view can hold and display one unit at a time; it cannot be printed. Autocalibrate Data. The Autocalibrate data window has three main regions, Header, Data Area, and Message Box. •
The Header contains the Unit Name, Site Name, Program Name, and Time tag The Header time tag displays the operator interface time and updates whenever a valid new message is received. If no valid messages are received for five seconds, the Header time tag is highlighted.
•
The Data Area is below the Header. This displays the strings for the selected Autocalibrate regulator calibration such as important data from each processor, relevant test values, and test status messages. The Data Area is updated at 1 Hz.
•
The time tag displayed in the Header reflects operator interface time when the last update message was received. If the Header time tag field is highlighted, the data being displayed may not be valid.
If the Mark V does not respond or another Autocalibrate window, HMI, or is using the Autocal function, the data fields remain blank.
4-10 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Message Box. This area at the bottom of the data window displays warnings and information about the Autocalibrate function status. Please take note of all messages and warnings.
Button-view The Button-view window contains the pushbuttons that interact with the unit control to conduct and verify Autocalibration functions. These buttons are visible only when the board permissives have been met and no other window, HMI, or is conducting an autocalibrate function. The Enable Commands pushbutton must be activated to allow the user to issue further commands to the unit. Read and heed the warnings accompanying this command. The pushbuttons and their functions are discussed in the section on Autocalibrate Command Pushbutton Description.
Autocalibrate Display Dialog Boxes Unit Select Dialog Box. Use the Unit Select dialog box to change which unit’s data is displayed. Only valid units are displayed. Highlight the unit in the list box and select OK to display data from that unit control. Cancel closes the dialog box and maintains the original unit data display. About Dialog Box. The About Dialog Box displays the program name and current revision level. Select OK to close this dialog box. Confirm Dialog Box. The confirm Dialog Box is called any time the user initiates a control action from an arm/run pushbutton within the Autocalibrate Display. The box displays an appropriate message to the user regarding the unit, regulator, control action, and OK and Cancel buttons. The default action of this dialog box is Cancel. Manual Setpoint Command Dialog Box. This dialog box is used to enter and confirm the user’s autocalibrate actuator set point command. The setpoint signal information appears in text. Enter the desired setpoint in the edit box. Select the OK button to sends the new actuator setpoint to the desired regulator. Cancel cancels the command execution. The default action for the Manual Setpoint dialog box is OK. Warning Dialog Box. The Warning Dialog Box is called any time the user selects Enable Commands. It displays a warning about the Autocalibrate procedure. The box displays OK and Cancel buttons; the default action of this dialog box is Cancel. Processor Selection Dialog Box. The Processor Selection Dialog Box is called any time the user selects View Verify and more than one processor has data. Only those processors that have verification data are displayed as choices. Highlight the processor in the list box and select OK to display data from that controller. Cancel closes the dialog box and maintains the original data display.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-11
Control Constants Display - Mark V and Mark V LM The HMI Control Constants Display displays the value of each of the control constants in the selected unit. All control constants in the selected unit’s data dictionary are displayed. From this display the user can call up the Control Constants Adjust Display to change any constants that are adjustable. Note Mark IV uses the local operator interface. Mark VI uses the toolbox. The Control Constants Display has a header above a list of control constants. The header includes the following: •
The Site name
•
The Unit name
•
The current time being sent from the unit
The list of points has three columns as follows: •
The Point name
•
The Value
•
The Units
There is an icon to the left of the Point Name to determine if the point is adjustable. The icon is a plus sign if the point is adjustable, and the icon is a question mark if the values from the three processors (R, S, and T) do not match. The question mark is also displayed if the value is outside the minimum and maximum value. Both the plus sign and the question mark can be displayed at the same time. Menu Structure
Menu
Menu Item Description
File
Print
Send what is on the display to a printer
Print Setup
Select the desired printer and its setup
Exit
Exit the Control Constants display
Select Unit
Selects the unit (controller) with which the Control Constants display communicates
Find Point
Brings up the Find Point dialog box. From this the user can locate a point in the list
Set Point
This dialog box sets the font that both the header and the data list uses
Set Default
This sets the font and column widths back to the system default
Tool Bar
Toggles the tool bar on and off
Status Bar
Toggles the status bar on and off
Edit
View Help
About Control This Dialog box displays the revision level of the Control Constants Constants Display
The Control Constants Display can be invoked from the command line with a unit name. If a valid unit name is specified, the Control Constants Display starts with data from that unit. If no unit is specified on the command line and there is more than one unit in the system, the user is prompted to select a unit. For example, use the following: G:\EXEC\CONSTDSP /UNIT:T1
4-12 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
The header time tag displays the time tag of the oldest piece of data being displayed in the data list. Before data has been received, the time tag reads No Valid Data. If the oldest piece of data on the screen is more than five seconds old, the time tag is highlighted.
Changing a Control Constant Only Control Constants with a plus next to them can be adjusted. Double click the constant to be adjusted. Or use the arrow keys to move to the constant to be adjusted and press enter.
Control Constants Display
Control Constants Adjust Display - Mark V and Mark V LM The HMI Control Constants Adjust Display allows the user to adjust the value of any control constant that is adjustable. The display is a dialog application. The dialog application must not be closed until the ramping of the control constant is finished. If it is closed, the ramping stops at the current value. More than one Control Constant Adjust Display can be active at a time. The display can be minimized at any time (including while a point is being ramped). Note Mark VI uses the toolbox. The Control Constants Adjust Display can be invoked from the command line with a Pointname. If no pointname is specified, then a dialog box displays to enter a point. The format of the command line argument is: /POINT::
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-13
The unit is required for multi unit sites, for example: G:\EXEC\CONSTADJ /POINT:T1:CSKATS The unit is optional if there is only one unit, for example: G:\EXEC\CONSTADJ /POINT:CSKATS
Header Time tag The Control Constants Adjust Display has a header that includes: Site Name, Unit Name, and Current Time being sent from the unit. The header time tag displays the time tag of the oldest piece of data being displayed. Before data has been received, the time tag reads No Valid Data. If the oldest piece of data on the screen is more than five seconds old, the time tag is highlighted.
Control Constants Adjust Display
The following information is displayed in the dialog box: Point Name, Current Point Value (if the unit is a TMR, three values are displayed), Target Point Value, Ramp Rate Value, Minimum Value (if it exists), and Maximum Value (if it exists). The Display Pushbuttons
Pushbutton
Color
Description
Enter Target
Gray with black text
This button displays the Enter Target dialog box
Start Ramp
Green with black text
The Start Ramp button displays a dialog box asking if you really want to start the ramp. The button is green with yellow text when the ramp is in action
Stop Ramp
Red with black text
This button immediately stops the ramp
Step Change
Green with black text
This button displays a dialog box asking if you really want to make the step change. A step change can only be made when the unit is off line
Storage Update
Green with black text
This button displays a dialog box asking if you really want to save all constants in non-volatile memory
4-14 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Header Time tag The Control Constants Adjust Display has a header that includes: Site Name, Unit Name, and Current Time being sent from the unit. The header time tag displays the time tag of the oldest piece of data being displayed. Before data has been received, the time tag reads No Valid Data. If the oldest piece of data on the screen is more than five seconds old, the time tag is highlighted.
Control Constants Adjust Display
The following information is displayed in the dialog box: Point Name, Current Point Value (if the unit is a TMR, three values are displayed), Target Point Value, Ramp Rate Value, Minimum Value (if it exists), and Maximum Value (if it exists). The Display Pushbuttons
Pushbutton
Color
Description
Enter Target
Gray with black text
This button displays the Enter Target dialog box
Start Ramp
Green with black text
The Start Ramp button displays a dialog box asking if you really want to start the ramp. The button is green with yellow text when the ramp is in action
Stop Ramp
Red with black text
This button immediately stops the ramp
Step Change
Green with black text
This button displays a dialog box asking if you really want to make the step change. A step change can only be made when the unit is off line
Storage Update
Green with black text
This button displays a dialog box asking if you really want to save all constants in non-volatile memory
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-15
CONSTCHK - Constants Check - Mark V and Mark V LM When a turbine control is reset or powered up, it reads the control constant values out of non-volatile memory and loads them into RAM. The controller then runs using these RAM resident values.
CONSTCHK is a command line configuration utility that displays control constants that have a different value in the controller's RAM and the controller's non-volatile storage. It is useful in determining which control constants in RAM have changed value since the controller was last reset or powered up. The Control Constant Adjust Display can dynamically change the contents of the RAM resident control constants. Use of the Control Constants Adjust Display results in the contents of the RAM and the contents of the non-volatile memory value being different. CONSTCHK outlines the differences, giving a list of the changes that were made.
Operation CONSTCHK is a command line program that is usually run from a DOS prompt. It needs one command line parameter, the name of the unit to check. If run with no parameters or the /? parameter, it displays a help screen. Normally the program reports only the values of control constants that have different values between the RAM and the non-volatile memory. If the /ALL qualifier is used on the command line, all values are displayed. The following example displays a check of a Mark V unit. Two control constants were found where the value in RAM was different than in non-volatile storage. The Mark V uses an EEPROM for its non-volatile storage. F:\UNIT1>CONSTCHK T1 ...Site: HMI Development ...Unit: T1 ...Time: 03-DEC-1997 11:58:15
... Name Units RAM (CSDB) EEPROM ...--------- -------- ------------ -----------LK90PSEL "MW" 24.0 22.6 LK90SPIN "MW" 3.0 4.0 ...There were 2 Control Constants with different values. F:\UNIT1>
The following example displays a check of a Mark V LM unit. Seven control constants were found where the value in RAM was different than that in non-volatile storage. The Mark V LM uses an AP1 file on its internal hard drive for its nonvolatile storage. F:\UNIT2>CONSTCHK T2 ...Site: HMI Development ...Unit: T2 ...Time: 03-DEC-1997 11:59:28 ... Name Units RAM (CSDB) ...--------------------------K39VTT_TD "sectd" 0.015 KOTRDITH_M "%" 3.09 KOTRR_LAG "secrt" 10.00 KOTRR_LEAD "secrt" 5.38 KPLTR_LEAD "secrt" 5.88 KPLTR_NLMT "%" 3.19 KPLT_BIAS "%" 3.19 ...There were 7 Control Constants with F:\UNIT2>
4-16 • Chapter 4 Mark V
AP1 -----------0.000 0.00 0.00 0.00 0.00 0.00 0.00 different values.
GEH-6126C Vol II HMI Application Guide
Diagnostic Counters Display - Mark V and Mark V LM The Diagnostic Counters Display (DIAGC) provides information on internal control and I/O board functions used for troubleshooting or statistical data gathering. This display permits I/O board data not defined in the unit CSDB to be viewed. Not all data is defined in the CSDB because either the data must be processed or scaled before it can be used by the Turbine Control programs, or it is data created by the operating or communication systems of the I/O boards for troubleshooting purposes. This information is intended for debugging by experienced field and factory personnel. This program is not intended for use by plant operators. No unit control functions are available on this display. The display features a split window with a tree-view of the unit on the left and the Diagnostic Counter data on the right. The tree-view can hold and display one unit at a time. Selecting a valid sub-type from the list under a unit/core/card in the tree-view causes that sub-type Diagnostic Counter data to be displayed. That data is displayed until the user selects a different sub-type or changes the unit.
File Type The program reads the F:\CONFIG.DAT file to obtain the site information. The program also reads the DIAGC.DAT file for each unit. This file can be located in the F:\UNITN directory or in the F:\UNITN\PROM directory. For the Mark V LM, the DIAGC.DAT file is a text file that is produced by the tool program G:\EXEC\DCBUILD1.EXE. Note For Mark V LM, DIAGC.DAT should always be built from the card library by the tool program. While DIAGC.DAT is a text file, it should never be edited by hand. DIAGC.DAT files should never be copied from one unit to another. For the Mark V, the DIAGC.DAT file is completed by the requisition engineer. Note For Mark V, the DIAGC.DAT file should not be edited except by qualified field personnel as part of hardware or software modifications to the unit control. DIAGC.DAT files should never be copied from one unit to another. The program can save the current DIAGC output to a text file. This text file can be opened and viewed with notepad or other text-viewing program. DIAGC cannot be used to open the text file.
Using the Diagnostic Counters Display Program This section provides information concerning the use of the following functions: •
Starting the Diagnostic Counters Display program
•
The Diagnostic Counters Display window
•
Selecting a DIAGC display screen
•
Interpreting the data
Executing Diagnostic Counters Display (DIAGC) The Diagnostic Counters Display, DIAGC, can be run from a menu pick on the Main Menu or from the DOS prompt using the command: DIAGC
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-17
DIAGC.EXE is located within the product code in the G:\EXEC subdirectory. The Diagnostic Counters Display can be launched from the command line with the following argument to quickly bring the display to a desired configuration: /UNIT:T1 The following example specifies the unit name as T1: G:\EXEC\DIAGC.EXE /UNIT:T1 The DIAGC Display can be launched from the Windows Start Menu Run dialog box by entering the command as displayed on the command line above, or by selecting the DIAGC icon from the appropriate program group.
Tree view
Diagnostic subtypes
Selected sub-type
Diagnostic data area
DIAGC - Tree View and Splitter Bar
The Diagnostic Counters Display Window The tree-view is on the left side of the display and the Diagnostic Counter data is on the right. A movable splitter bar separates the two portions. The program can display and update one set of Diagnostic Counter data at a time. The Diagnostic Counters tree view is a graphical window that depicts the hierarchy of panel/core/card/sub-type in a tree structure. The tree view can hold and display one unit at a time. The tree-view window cannot be printed.
4-18 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Navigation in the tree-view is accomplished with the keyboard or mouse. The panel/core/card levels can be expanded or collapsed to reveal the Diagnostic subtypes available to the user. Selection of a sub-type causes that sub-type Diagnostic Counter data to be displayed in the Diagnostic Counter window. That data is displayed in the data area until the user selects a different sub-type or changes the unit selection.
Unit name Site name Program name Board, core and socket name Timetag Number of replies received from the Unit. Legend with title of diagnostic sub-type
Data area with value field
Diagnostic Counter Data Window and Splitter Bar
The Diagnostic Counter data window on the right hand side has three main regions, the Header, the Legend, and the Data Area The Header is a non-scrolling region and therefore cannot be scrolled out of the window. Although this region can be turned off using the View menu, it is recommended that users leave the Header visible at all times because of the process information displayed. The Header program name, card, core and socket names all appear on the same line and serve to uniquely identify the board being examined. The legend contains the sub-type currently being viewed. The Header time tag displays the operator interface time and updates whenever a valid new message is received. If no valid messages are received for five seconds, the Header time tag is highlighted.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-19
As new data is received from the unit, the replies received counter is updated and displayed. If there is an error in the number of bytes returned in a message from the unit, the replies received field in the Header is highlighted to indicate the mismatch and possible corruption of Diagnostic Counter data on the display. The Legend displays the title of the current Diagnostic Counter sub-type. The Legend is in a non-scrolling region and cannot be scrolled out of the window. Although this region can be turned off using the View menu, it is recommended that users leave the Legend visible at all times. The Data Area is below the Header and Legend. The Data Area displays the strings for the selected Diagnostic Counters sub-type. The value field in the Data Area is updated at either 1 Hz or 4 Hz. The time tag displayed in the Header reflects operator interface time when the last update message was received. Unlike the Header and Legend, the information in the Data Area can be scrolled with the vertical scroll bar. If the Header replies received field is highlighted, the Diagnostic Counter data being displayed may not be valid.
Selecting a Diagnostic Counters Display Selecting a particular display establishes a communication link to the board in question and asks for the PROM data associated with this display. The tree view on the left gives an exploded diagram of all the cores within the panel. Each core can be expanded into its component boards and each board expanded into its diagnostics displays. Use the cursor and keyboard to expand the desired core and board, then select the appropriate diagnostic display for the board. The selection is highlighted with a check mark on the tree view portion of the screen.
Interpreting Data DIAGC is a diagnostic tool for firmware designers and field personnel only. Its purpose is to assist firmware designers in the performance evaluation of the EPROM based programming and to assist field personnel in problem diagnosis. While the program is a display only program that poses no threat to the operation of the turbine control, it does not provide Turbine Operation information and should be run by authorized personnel only.
Information for Board Designers The following data types are supported for the Diagnostic Counters Display. Board designers should refrain from using data types other than those listed here because they are not supported. Type Hn converts signed to unsigned; type Sn converts unsigned to signed.
4-20 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Data Types for Diagnostic Counter Display
Data
Code
Ctypes
Conversion-Algorithm
ASCII
A0
%s
char* =&raw_data
Binary
B1
%8s
char* =itoa((char)raw_data,str,2)
B2
%16s
char* =itoa( (int)raw_data,str,2)
C1
%f
double= (char) (raw_data) *gain +offset
C2
%f
double= (int) (raw_data) *gain +offset
C4
%lf
double= (long) (raw_data) *gain +offset
Fixed
F2
%f
double= (int) (raw_data) /32768*gain+offset
Sign/un
H1
%2X %u %c
uchar = (char) (raw_data) *gain +offset
H2
%4X %u
uint = (int) (raw_data) *gain +offset
H4
%1X 1u
ulong = (long) (raw_data) *gain +offset
Logical
L1
%d
int = (char) (raw_data)? 1 : 0
Real
R4
%f
double= (float) (raw_data) *gain +offset
Un/sign
S1
%f
double= (uchar) (raw_data) *gain +offset
S2
%f
double= (uint) (raw_data) *gain +offset
S4
%lf
DOUBLE= (ULONG) (RAW_DATA) *GAIN+OFFSET
Integer
Logic Forcing Display - Mark V and Mark V LM Forcing a point from the Logic Forcing Display program changes or maintains the logic state of the point (0 or 1) regardless of the permissives driving the point. For example, during maintenance or troubleshooting it may be necessary to make the controller believe that a certain valve is in a particular position, as indicated by a limit switch. A simple approach is to use the controller Logic Forcing capability. Only qualified personnel knowledgeable about turbine control and protection should use the Logic Forcing functions. Improper use can adversely affect the control and protective features of the control system. Note Mark IV uses the local control panel for forcing, not the HMI. Mark VI uses the toolbox. The Logic Forcing Display program always displays the currently forced points in the controller. The list of forced points appears on the display at the top of the Data Area when the program is displaying a blank Logic Forcing Display file. For existing files, the Logic Forcing Display program displays the forced points at the end of the pointname list in the Data Area. Forced Logic signals already appearing on the Logic Forcing Display screen are not duplicated. If the list of points is larger than the Logic Forcing Display window, scroll bars are enabled. Forced points reappear if deleted. Unforced points do not disappear; their updated values appear on the next scan of data. The Logic Forcing Display program allows forcing of logic data points for the currently selected controller only.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-21
A delay occurs before forced Logic signals appear on the Logic Forcing Display screen. When opening a file, wait a few moments for all of the forced signals to appear prior to taking any action.
File Structure The Logic Forcing Display program is located in the executable directory, G:\EXEC\LFORCE.EXE. Never tamper with this file. The Logic Forcing Display program stores its data in a special text format file with a .TXT extension. Never edit the Logic Forcing Display files directly, use the Logic Forcing Display program to open, modify, and save these files. Each unit has its own point list in the data file. It can be useful to set up several different logic forcing files. These files are typically located in the unit specific directory on the F:\ drive, but may reside in any directory such as F:\RUNTIME. Logic Forcing Display files use Data Dictionary files for the point list available for use in the display. Logic Forcing Displays obtain their values for these points directly from the Data Dictionary.
Header
PC time
Current value
Command target area
Engineering units
List view
Logic Forcing Display
4-22 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Using the Logic Forcing Display Program Creating and editing Logic Forcing Displays requires unique operations including loading, creating, editing, and saving a Logic Forcing Display file. Performing these operations requires using the drop-down menu options from the menu bar selections. Some of the operations are available on the toolbar. Note Only qualified personnel knowledgeable about turbine control and protection should force logic signals. Improper use can adversely affect the control and protective features of the control system. This section provides information concerning the use of the following functions: •
Forcing and Unforcing Logic Signals
•
Starting the Logic Forcing Display program and loading a Logic Forcing Display file
•
The Logic Forcing Display window
•
Navigating within a Logic Forcing Display screen
•
Modifying a pointname
•
Adding/deleting a pointname line
•
Using the Command targets
•
Printing the Logic Forcing Display screen
•
Other options available
•
Saving a Logic Forcing Display file
•
Exiting the Logic Forcing Display program
Forcing and Unforcing Logic Signals (Mark V) To force a logic signal 1
From the Logic Forcing Display program, position the cursor on the line corresponding to the desired logic signal. Click on the pointname field to select it and the pointname highlights.
2
Select one of the Forcing Command targets on the right side of the screen to arm the action, either Force To One or Force To Zero. The Logic Forcing Command dialog box displays.
3
Select OK to force the signal. The force command is sent to the controller forcing the logic signal. Signals remain forced until either an Unforce command comes from the Logic Forcing Display program or until the controller powers off.
Selecting Cancel from the Logic Forcing Command dialog box cancels the forcing command. The default is Cancel. This procedure for confirming a forcing action helps prevent a false command from executing. Signals remain forced until an unforce command comes from the Logic Forcing Display program or until the controller powers off. Forced signals can cause the controller to function improperly if forgotten. Take care to unforce all unnecessary signals prior to running the turbine.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-23
Return the logic signals to their normal state by either unforcing all of the forced logic signals at once or by individually unforcing them. To unforce a single logic signal 1
From the Logic Forcing Display, select the desired logic signal by double clicking on it. The line highlights.
2
Select the Unforce Single command target. The Execute Command dialog box displays.
3
Select OK to unforce the signal, or Cancel to leave the signal forced. The default action is Cancel. To unforce all of the forced logic signals
1
From the Logic Forcing Display, select the Unforce All command target. The Execute Command dialog box displays.
2
Select OK to unforce all forced logic signals in the controller, or Cancel to cancel the unforcing command. The default action is Cancel. Selecting UNFORCE ALL unforces all of the logic signals forced in the controller, including any signals forced from OTHER Logic Forcing Display screens.
Starting the Logic Forcing Display To start the Logic Forcing Display 1
From the desktop, select the Logic Forcing Display icon, or
2
From the Command prompt, type LFORCE, then enter, or Select Start, Run, then type LFORCE, then enter
3
The Logic Forcing Display displays.
The Logic Forcing Display program is configurable from the command prompt, however, configuration arguments are not necessary. Typing LFORCE by itself at the prompt accesses the display program. The configuration arguments are: /UNIT: /FILE: The /UNIT: argument opens the Logic Forcing Display for the unit requested. For example: F:\RUNTIME>LFORCE /UNIT:T1 where the unit number must be a valid unit. Selecting an invalid unit or no unit displays the Unit Selection dialog box. Single unit sites ignore this argument and default to the single unit. The Logic Forcing Display program allows files to be passed directly to it from the command prompt using the argument /FILE:. The /FILE: argument opens the Logic Forcing Display program and loads the requested Logic Forcing Display file. For example: F:\RUNTIME>LFORCE /FILE:LFORCE2.TXT
4-24 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
or for files located in other directories: F:\UNIT1>LFORCE /FILE:F:\RUNTIME\LFORCE2.TXT This argument requires permission to read the file or directory. Entering an invalid filename, invalid path or no filename causes an error dialog box to display. Upon acknowledgment, a blank Logic Forcing Display file displays. The Logic Forcing Display program automatically opens an untitled blank Logic Forcing Display text file unless a filename is passed to it from the command prompt. Selecting the menu bar option File and the Open command from the drop-down menu causes the Open dialog box to display. All the *.TXT files located in the directory from which the program was run display, along with the directory and drive. Selecting the file and then OK displays the requested Logic Forcing Display file. Opening *.TXT files in other directories is possible using the Open dialog box and selecting the drive, directory, and filename of the desired file and the OK button. Selecting Cancel in the Open dialog box cancels the opening of a Logic Forcing Display file.
Loading a Logic Forcing Display File There are three ways to load an existing Logic Forcing Display file. If the Logic Forcing Display program is started from the command prompt, add the name of the file after the Logic Forcing Display program execution command, LFORCE, using the /FILE: argument. The extension .TXT must be included with the filename. For example, F:\UNIT1\LFORCE /FILE:{FILENAME}.TXT where {filename}.TXT would be a Logic Forcing Display filename such as LFORCE2.TXT. To load an existing Logic Forcing Display file after starting the Logic Forcing Display program, select the menu bar option File and the Open command from the drop-down menu. The Open dialog box displays allowing for selection of the file to load. Selecting the toolbar button with the picture of the open file also displays the Open dialog box. Selecting a previously viewed file listed at the bottom of the File menu bar option opens the file directly. If the specified file does not appear to be a Logic Forcing data file, the user is prompted as to whether to continue loading the file or to abort the operation. If no existing file is specified when executing the Logic Forcing Display program, a default blank file loads. To create a new Logic Forcing Display file, select the menu bar option File and the New command from the drop-down menu, or select the toolbar button with the blank sheet of paper to display a blank Logic Forcing Display screen. The blank Logic Forcing Display screen displays with the Logic Forcing Display file title UNTITLED.TXT. This file opens blank each time, but only allows saving once per directory. Saving subsequent copies of UNTITLED.TXT overwrites the existing UNTITLED.TXT in the same directory. A new Logic Forcing Display file name should be given to this file when saving using the File menu bar option and the Save As command from the drop-down menu. Any logic point forced in the specific unit is displayed even if there is no specific file chosen. Note Saving a Logic Forcing Display file without renaming it overwrites the old Logic Forcing Display file data with the new file data. Exiting the Logic Forcing Display program without saving loses changes to the file.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-25
Logic Forcing Display Window The Logic Forcing Display operates in a Windows environment. The Logic Forcing Display program performs functions selected from drop-down menu options from the menu bar or buttons on the toolbar. The titlebar displays the filename currently in the Logic Forcing Display program. The horizontal scroll bar allows viewing of display screens that exceed the window’s boundaries. The menu bar at the top of the screen incorporates several items common to Windows applications along with special items associated with the Logic Forcing Display. A summary of these items and their corresponding functionality is displayed in the following table: Logic Forcing Display Menu Items and their Functions
Menu Items
Drop Down List Function
Description
File
New, Open, Close, Save, Save As, Selects new or existing files, recently Print, Print Preview, Print Setup, edited files, saves edited files, prints files, {Filenames}.TXT, Exit exits the Logic Forcing Display program.
Edit
Insert Blank Line, Modify Line, Inserts, deletes and modifies display lines. Delete Line, Set Font, Select Unit, Set fonts and selects units. Find
View
Toolbar, Status Bar
Help
Index, Using Help, About Demand Accesses Help screens. Display
Edits window display to show or remove toolbar and status bar.
The toolbar immediately beneath the menu bar corresponds to particular drop-down menu options. The toolbar buttons allow shortcuts to common menu commands. Placing the cursor over any of these buttons causes a pop-up explanatory text window (Tooltip) to appear. Selecting the Help Cursor (arrow with a question mark) changes the cursor to an arrow with a question mark. Selecting a subsequent item calls up Help information for that item.
Logic Forcing Display Screen Window The Logic Forcing Display permits viewing and forcing of Logic signals. Opening a window displaying a Demand Display screen allows for viewing analog signals and monitoring system reactions to forcing Logic signals. The Logic Forcing Display screen is made up of three main regions, the Header, the List View, and the Command Target area The Header contains the unit name, site name, program title, and time tag. The Header is in a non-scrolling region and cannot scroll off the window. The menu bar option View and the Header command toggles the header on or off. The Header contains valuable process information and it is recommended that it remain visible at all times. The Header time tag displays the COMPUTER time. If the Data Area is empty, contains no valid points, or the Data Area contains valid points but no data has been received from the controller, then the time tag displays No Valid Data. A highlighted Header time tag indicates the oldest piece of data in the Data Area has not been updated for five seconds.
4-26 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
The List View is composed of three columns, the Point Name, the Current Value from each processor, and the Engineering Units. The List View scrolls and each of the columns is adjustable in width. If the column becomes too narrow to display all of the data, an ellipsis (…) appears on the right side of the column. The Current Value field is updated once per second from each controller processor. The time tag displayed in the Header reflects the time tag of the oldest piece of data displayed. Only the points visible on the screen are updated. There is no limit to the number of points that can be added to the point list. Unlike the Header, the information in the Data Area scrolls with the scroll bars. The Logic Forcing Display updates only the visible points in the List View. The Pointname field holds the Control Signal pointname (or synonym) of valid unit database points. Entering the pointname causes the Logic Forcing Display program to use the currently selected unit’s data, which is the unit listed in the Header. Entering the unit number with a colon prior to the pointname, as in T2:{pointname}, displays the data from the requested controller. The Logic Forcing Display program allows entering other text into this field for commenting and separating sections of points. The Processor Value field displays the Logic signal pointname values taken from the processor. If the pointname is invalid or there is no data for the point in the Data Dictionary, this field remains blank. Forced points appear with a > character preceding the value. The Units field displays the Engineering units for valid pointnames. The text appears exactly as entered in the scale code table file. This field is blank for invalid pointnames, but indicates the units for valid points without data in the Data Dictionary. The Command Target area appears on the right side of the Logic Forcing Display window. There are four Arm/Run targets available for the Logic Forcing function. These targets are for forcing Logic signals to a state of 1 or 0, to unforce a single Logic signal, or to unforce all forced Logic signals. Arm/Run targets appear green with black text and require a confirmation prior to sending the force or unforce signal to the controller.
Navigating within a Logic Forcing Display Screen There are several ways to navigate within the Logic Forcing Display program. Viewing pointnames that are off the bottom or top of the screen is done with either the up and down arrow keys on the keyboard, the page up and page down keys on the keyboard, or the scroll up/down bar on the window.
Modifying a Pointname or Line To modify a Pointname or Line 1
From the Logic Forcing Display, highlight the desired line.
2
Select the menu bar option Edit, and from the drop-down menu, select the Modify Line command , or Select the Modify Line toolbar button.
3
Type the new pointname or line in the highlighted pointname field.
The Logic Forcing Display program allows the entry of invalid pointnames to accommodate adding textual information to the Logic Forcing Display screen. The Processor Value and Unit fields remain blank if an invalid pointname is entered. Selecting File:Save makes the changes permanent.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-27
Adding and Deleting a Pointname Line The Logic Forcing Display program allows adding lines at any point in the display screen. To add or delete a Pointname line 1
From the Logic Forcing Display, highlight the line above the desired insertion point.
2
Select the menu bar option Edit and from the drop-down menu, select the Insert Blank Line, or Select the Insert Blank Line toolbar button.
3
The Logic Forcing Display program inserts a blank line below the highlighted line.
If the display is empty, Insert Blank Line can be applied without first highlighting a location. To modify the line, refer to the Modifying a Line section. Saving the Logic Forcing Display file makes the addition permanent. The Logic Forcing Display program allows deleting lines. Highlight the pointname field in the line to be deleted. Select the menu bar option Edit and the Delete Line command from the drop-down menu, or select the Delete Line toolbar button. The line is deleted. Saving the Logic Forcing Display file makes the changes permanent. Note Deleting lines removes lines permanently. Exiting without saving the file is the only way to undo the line deletion.
Using the Command Targets The Logic Forcing Display command targets are Arm/Run targets requiring confirmation of their action prior to performing the command. This procedure for confirming a forcing action helps prevent a false command from executing. To use the Command Targets 1
Select the Command Target. The Execute Command dialog box displays.
2
Select OK. The command runs.
To cancel the command execution, select Cancel. The default action is Cancel.
Printing from the Logic Forcing Display File The Print command prints the Logic Forcing Display screen. Only the data currently displayed on the screen can be printed. To print the Logic Forcing Display screen 1
From the Logic Forcing Display screen, select the menu bar option File and either the Print or the Print Setup commands from the drop-down menu, or Select the toolbar button with the picture of the printer.
2
The Print dialog box displays.
3
Select OK. The data prints
Selecting Cancel cancels the print command. The Print Preview command previews the page and allows accessing the Print dialog box.
4-28 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Other Options There are other options available in the Logic Forcing Display program. Selecting the menu bar option Edit and the Set Font command from the drop-down menu presents the Windows Font dialog box. The Font dialog box allows for selecting the font used for the Logic Forcing Display screen. The selection applies to the entire display screen including the text defined in the Command Targets. Selecting the menu bar option Edit and the Select Unit command from the dropdown menu allows for unit selections. In multiple unit sites, any unit can be monitored from one Logic Forcing Display screen. Select Unit causes the Unit Selection dialog box to appear. The currently selected unit is highlighted. The available units are displayed in alphabetical order. Select the desired unit. This option is not available in single unit sites.
Saving a Logic Forcing Display File To save a file 1
Select the menu bar option File and from the drop-down menu, select Save, or Select the toolbar button with the picture of a disk
2
The Logic Forcing Display files are saved in the directory of the original file.
If the file is new, the Save As dialog box appears requesting a filename. If a new directory is not selected, the Logic Forcing Display program saves the file in the directory from which the program was run. Selecting the OK button after typing in a name saves the file using the filename. Saving a file overwrites the previous file and all old information is lost. To save new Logic Forcing Display files or to copy old files to new files with different names, select the menu bar option File and the Save As command from the drop-down menu. The Save As dialog box displays requesting a new filename for the file. The Save As dialog box also allows entering different directories. If a new directory is not entered, the Logic Forcing Display program saves the new filename in the directory from which the program was run. Using an already existing filename overwrites the data in the old file with the data from the new file.
Exiting the Logic Forcing Display Program Selecting the menu bar option File and the Exit command from the drop-down menu exits the Logic Forcing Display program. The Logic Forcing Display program requests whether to save changes to any Logic Forcing Display file prior to exiting.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-29
PVOTE - Prevote Data Display - Mark V The HMI Prevote Data Display allows a technician to view logic and analog I/O values before the three independent processors have selected a value through voting. This display is useful for troubleshooting voting mismatches or control I/O discrepancies. This display only displays data. It has no control actions. Note Mark VI uses TSM or the toolbox, see later in this chapter.
Operation The Prevote Data Display has a header above a list of voted points. The header includes: Site Name, Unit Name, and Current time being sent from the unit. The list of points has six columns: Point Name, Voted value, R value, S value, T value, and the Units. This list of points can be scrolled to display the desired point. All points in the data dictionary that are marked as voted are displayed in the list. The points are ordered in the list according to their assigned offsets. A dash is displayed in the column heading on each side of the processor name, for example -R, if the data from that processor is no longer valid. Menu Structure
Button
Menu Item
Description
File
Print
Send what is on the display to a printer.
Print Setup
Select and setup the desired printer.
Exit
Exit the Prevote display.
Select Unit
Selects the unit (controller) with which the Prevote display communicates.
Find Point
Brings up the Find Point dialog box. From this, the user can locate a point in the list.
Set Font
This dialog box sets the font for both the header and the data list.
Set Default
This sets the font and column widths back to the system default.
Tool Bar
Toggles the tool bar on and off.
Status Bar
Toggles the status bar on and off.
Freeze Data
This function stops the update of the data on the screen. If the list is scrolled, the new entries are not updated until the data is unfrozen.
About Prevote
Dialog box that displays the revision level of the Prevote Data display.
Edit
View
Help
4-30 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Command Line Description The Prevote Data Display can be invoked from the command line with a unit name. If a valid unit name is specified, the Prevote Display starts with data from that unit. If no unit is specified on the command line and there is more than one unit in the system, the user is prompted to select a unit. For example: G:\EXEC\PVOTE /UNIT:T1
Header Time tag The Header Time tag displays the time tag of the oldest piece of data being displayed in the data list. Before data has been received, the time tag displays No Valid Data. If the oldest piece of data on the screen is more than five seconds old, the time tag is highlighted.
Prevote Data Display
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-31
DABUILD - Diagnostic Alarm Build - Mark V DABUILD is a Mark V specific program that configures the alarm text string for the Diagnostic Alarms. It is not part of the normal configuration process, it is used only after special PROM updates. This program builds the template file, ALARMD.TPL, that is used to create the master list of alarms, ALARM.DAT. When the Mark V controller indicates a diagnostic alarm, it reports it with a diagnostic alarm number. The HMI must be able to match that number to the diagnostic alarm text to be displayed. This text information is read from the unit configuration directory ALARM.DAT file, which contains the drop number and alarm text for each alarm. In order to ensure that the drop numbers and alarm text match, the same file (DIAG.H) is used to create the drops in the unit as is used by the HMI to create the template alarm text file. DABUILD translates this file from the unit form to the HMI form. DABUILD is a command line utility program. It reads the file that defines the diagnostic alarms in the unit and creates the template diagnostic alarm text file for the HMI. The file used is typically the DIAG.H file in the unit configuration directory, but you can specify a different file as a command line parameter. If run with the parameter /? it provides a help screen. The output from this program is a new version of the ALARMD.TPL file. Note DABUILD should only be run when directed as part of a PROM upgrade. The following demonstrates the on-line help available: F:\UNIT1>dabuild /? DABUILD - Diagnostic Alarm Text Builder for Mark V This program is used to build the list of diagnostic alarm text strings for a Mark V after a major upgrade. It uses the Diagnostic Alarm header file (DIAG.H) as the source of the text strings. This file is typically not required on-site, but some major prom updates may require that DABUILD be run on-site to redefine the Diagnostic Alarm Text strings. This program will create the ALARMD.TPL template file with the results. COMMAND FORMAT: DABUILD [filename] [filename] is the name of the file containing the diagnostic alarm information, typically DIAG.H. If not supplied on the command line, the user will be prompted for the name of this file. This program should only be used when directed as part of a Mark V prom update procedure. F:\UNIT1>
4-32 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
DABUILD1 - Diagnostic Alarm Build - Mark V LM DABUILD1 is a Mark V LM specific program that is used to configure the diagnostic alarms in the Mark V LM based upon the information in the Card Library. It is run from the unit configuration directory when updates to the PROMS in the turbine controller change the diagnostic alarms that the controller produces. Many of the processor and I/O boards in the Mark V LM controller produce diagnostic alarms. The number and meaning of the diagnostic alarms can change from PROM revision to PROM revision. The Card Library defines which diagnostic alarms are generated by each PROM revision, and the PANEL.CFG file defines which boards and PROM revisions are currently installed in the controller. DABUILD1 uses the list of boards from the Panel Configuration File, PANEL.CFG, in the unit configuration directory, and the Card Library definition files to create the master list of controller diagnostic alarms. The resulting diagnostic alarm configuration information is downloaded to the controller and used by the HMI to decode the diagnostic alarm messages. This program produces three output files: •
The DALARM.AP1 file is downloaded to the controller to tell it what boards to poll for diagnostic alarms, and how many diagnostic alarms each board can produce.
•
The ALARMD.DAT file maps the diagnostic alarm numbers to the diagnostic alarm text. The TCI System Service reads this file to find the text message to use for each diagnostic alarm.
•
The HELP_QD.DAT file supports the HMI Alarm Help feature. When a user requests additional information about the diagnostic alarm, the Alarm Help program uses this file as the additional help text.
The following display displays the on-line help available: F:\UNIT1>dabuild1 /? DABUILD1 - Diagnostic Alarm Data File Build This program reads the PANEL.CFG file in the current directory to obtain a list of cards used in the panel. It then reads the card definitions out of the CARD LIBRARY and creates the files to program the panel and the operator interface. COMMAND LINE: DABUILD1 [/LIB:] [/CFG:] [/NOCORE] [/GO] /LIB: Directory for the card library. /CFG: Override default configuration file. /NOCORE Do not prefix alarm text with core identification. /GO Don't ask for permission to run. If /LIB: is not found it defaults to the current directory. INPUTS: - PANEL.CFG Defines the panel configuration. - OUTPUTS: - DALARM.AP1 The AP1 file to download to the unit. - ALARMD.DAT The diagnostic alarm text definitions. - HELP_QD.DAT The diagnostic alarm help text. F:\UNIT1>
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-33
DCBUILD1 - Diagnostic Counter Build - Mark V LM DCBUILD1 is a command line configuration program that builds the list of available Diagnostic Counter Displays for a unit. It places the results in the DIAGC.DAT file in the unit configuration directory, where the Diagnostic Counter Display (DIAGC) expects to find it. Note This program is usually used only for Mark V LM units. Mark V units usually distribute the DIAGC.DAT file as part of the distribution instead of building it on site from the Card Library. Many of the boards in the Mark V and Mark V LM panel provide advanced diagnostic information upon request. The Diagnostic Counter Display (DIAGC) program polls the boards for this diagnostic information, and then formats it for display. The DIAGC program reads the list of diagnostic displays from a file called DIAGC.DAT in the unit configuration directory. When PROMS are changed in the controller, the list of available diagnostic displays can change, as the new PROMS can change the diagnostic information available from the board. DCBUILD1 uses the information in the PANEL.CFG file to determine the set of boards that exist in the controller, including the revision level of each board. It then reads the Card Library for the list of diagnostic displays available from each board in the panel, then builds the new DIAGC.DAT file. DCBUILD1 is a command line utility that is run from the unit configuration directory. It uses command line parameters to indicate the location of the Card Library. If run with the parameter /? it provides a help screen. The following screen demonstrates the on-line help available: F:\UNIT2>dcbuild1 /? DCBUILD1 - DIAGC Data File Build This program reads the PANEL.CFG file in the current directory to obtain a list of cards used in the panel. It then reads the cards definitions out of the CARD LIBRARY and creates the file that DIAGC reads as the list of available displays. COMMAND LINE: DCBUILD1 [/LIB:] [/CFG:] [/GO] /LIB: Directory for the board library. /CFG: Override default configuration file. /GO Don't ask for permission to run. If /LIB: is not found it defaults to the current directory. INPUTS: - PANEL.CFG Defines the panel configuration. - Files that define the contents of each card. OUTPUTS: - DIAGC.DAT The data file DIAGC will read. F:\UNIT2>
4-34 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
DIBUILD1 - IO_CFG Data File Build - Mark V LM DIBUILD1 is a command line configuration program that builds the IO_CFG.DAT file which the IO_CFG file reads. It also builds the agent definition file AGENT.DAT. This program reads the PANEL.CFG file in the current directory to obtain a list of boards used in the controller, including the revision level of each board. It then reads the board definitions out of the CARD LIBRARY and creates the IO_CFG.DAT file that IO_CFG reads as the list of boards to configure. DIBUILD1 is a command line utility that is run from the unit configuration directory. If run with the parameter /? it provides a help screen. The following screen demonstrates the on-line help available: F:\>dibuild1 /? DIBUILD1 - IO_CFG Data File Build This program reads the PANEL.CFG file in the current directory to obtain a list of cards used in the panel. It then reads the card definitions out of the CARD LIBRARY and creates the file that IO_CFG reads as the list of cards to configure. COMMAND LINE: DIBUILD1 [/LIB:] [/CFG:] [/GO] /LIB: Directory for the card library. /CFG: Override default configuration file. /GO Don't ask for permission to run. If /LIB: is not found it defaults to the current directory. INPUTS: - PANEL.CFG Defines the panel configuration. - Files that define the contents of each card. OUTPUTS: - IO_CFG.DAT The data file IO_CFG will read. - AGENT.DAT The agent definition file. F:\>
DPBUILD1 - PROM Sub-Directory Build DPBUILD1 updates the Unit Configuration Directory and its PROM sub-directory using files from the Card Library matching the software revisions in the panel configuration file. DPBUILD1 is a command line utility that is run from the unit configuration directory. If run with the parameter /? it provides a help screen. The following screen demonstrates the on-line help available: F:\>dpbuild1 /? DPBUILD1 -
Update a Unit Configuration Directory (and its \PROM subdirectory) with files from the Card Library that match the software revisions found in the Panel Configuration (PANEL.CFG) file. COMMAND LINE: DPBUILD1 [/?] [/GO] [/LIB=] /? - prints this help message /GO performs all operations needed without prompting user. Useful for batch or spawned operations. /LIB= Causes DPBUILD to go to a specific directory to retrieve card library information, instead of the default card library directory. This program reads the PANEL.CFG file in the current directory to determine the type and revision level of the product being updated. It then updates the Unit Configuration directory (including \PROM) with the files contained in the compressed library file included in the card library distribution. The library file contains current versions of the *.pic, *.def, *.tpl, and *.txt files needed to support the product. F:\>
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-35
DDLOCATE - Data Dictionary Locate - Mark V and Mark V LM DDLOCATE is a command line configuration program that decides the location of signals in the Mark V or Mark V LM CSDB. This program takes a list of the signals that are needed and locates them in the proper section of the CSDB. It handles assignments for both fixed locations, used for hardwired I/O points, and for floating locations, such as software generated signals. Each turbine controller has a CSDB which is the real-time database used in the controller. All I/O signals are read and written from the CSDB, and all sequencing runs by reading and writing CSDB signals. When the controller is first created there are some fixed or permanent signals located in the CSDB. These signals always exist, and cannot be renamed or moved. In addition, blocks of signals are set aside for certain functions, such as Pushbuttons, Analog Setpoints, and Control Constants. The set of signals that are voted is also determined, and regions are set aside for spare logical and real numbers. Note The size of each region is determined by the PROMS in the controller, and cannot be changed in the field. If DDLOCATE indicates there are no more of a certain type of signal (such as Pushbuttons or Control Constants) there is no way to add more without a PROM change. DDLOCATE uses this information, which is obtained from the PROM subdirectory, to determine how to layout the rest of the signals in the CSDB. It does this by reading a set of assignment files (*.ASG) that indicates the signals to be added to the CSDB. For each signal to be added, the type of signal required determines which region of the CSDB is used to store that signal. Hardwired I/O signals use the name of the input or output to land the signal on an exact termination point on an I/O board. Software signals simply indicate the type of signal and let DDLOCATE determine the exact location in memory. When done, DDLOCATE writes out the final configuration of the CSDB, which is stored in the UNITDATA.DAT file. DDLOCATE is a command line utility, but is typically run using the MK5MAKE batch file. It accepts as its command line parameters the list of assignment files (*.ASG) that contain the signals for it to assign. Each time it runs it creates a new CSDB layout from scratch; it is not used incrementally. Note To incrementally add a signal, edit the *.ASG file to include the new signal and rerun MK5MAKE. If run with the parameter /? a help screen is provided as follows: F:\UNIT1>DDLOCATE IO.ASG FACTORY.ASG ALLOCSSP.ASG SITE.ASG ------------ Opened PROM\UNITMAP.TPL file. ------------ Closed PROM\UNITMAP.TPL file. ------------ Opened file IO.ASG ------------ Closed file IO.ASG ------------ Opened file FACTORY.ASG ------------ Closed file FACTORY.ASG ------------ Opened file ALLOCSSP.ASG ------------ Closed file ALLOCSSP.ASG ------------ Opened file SITE.ASG ------------ Closed file SITE.ASG ------------ There were 1047 hardware and 478 software assign items found. ------------ Reading PROM\UNITDATA.TPL file. ------------ Reading PROM\UNITFREE.TPL file. F:\UNIT1>
4-36 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
The typical system uses four assignment files for the list of signals used, as follows: •
IO.ASG contains the assignments for hardwired I/O points
•
FACTORY.ASG contains assignments for factory supplied options
•
ALLOCSSP.ASG contains structured software points, or points used for standard options
•
SITE.ASG contains site specific assignments, typically for customer use
The format of the assignment files is documented in the header of the SITE.ASG file, since this is where field customization is done. Refer to this for specific information. The basic format for the assignment files is as follows: ;HARDWARE ASSIGNMENTS
;SOFTWARE ASSIGNMENTS ?
There is no required order in the *.ASG files, they are processed in the order that they are read. Any line that starts with a semi-colon is treated as a comment line and ignored. Hardware assignments land specific software signal names on specific I/O signals. To do this a hardware_name is used to indicate the specific location to map the software signal. The scale_name parameter defines how the signal should be scaled for display, and must match one of the scale code names in the scale code files, either ENGLISH.DAT, METRIC.DAT, HARDWARE.DAT, or CUSTOM.DAT. Software assignments assign a spare signal in a specific region of the CSDB to the given signal name. The software_type is used to indicate the region of the CSDB where the signal should be stored. A list of the region types is included in the header of the SITE.ASG file. The software types are of the format ?TCsss, where the letters are as follows: •
The first letter is always a question mark (?) to indicate that this is a software assignment.
•
The second letter is either an L for a logic signal, or a V for a variable.
•
The third character defines the controller in which to store the signal. The Mark V uses a B for a signal that must be in the (and optional ) controller, and a Q for a signal in the (and optional and ) controller. The Mark V LM only uses Q.
•
The sss indicates a sub-class of signal. These subclasses include the following:
GEH-6126C Vol II HMI Application Guide
–
is a local, non-voted signal
–
LS is a logic state command, only valid for logic signals
–
PB is a Pushbutton command, only valid for logic signals
–
PUB is a private (local) unsigned byte, only valid for logic signals
–
AS is an analog setpoint, only valid for variable signals
–
CC is a control constant, only valid for variable signals
Chapter 4 Mark V • 4-37
In some cases an array of signals is needed. Each signal in the array has its own name, but the entire array must be in continuous memory locations. This is done using an array assignment in the form as follows: ;ARRAY ASSIGNMENT EXAMPLES ?
An asterisk as the second word on the line indicates array assignments. This asterisk can have an optional count of the number of signals to follow immediately after the asterisk. The asterisk and the count should be one word. If the count is included, a warning is issued if the required number of signals is not found. If no count is given, the number of signals found is used as the number of signals in the array. The list of signal names must be one word, with no white space between signal names. A comma is used to separate each signal name. The list of signal names can be split over multiple lines by ending the line with the comma, indicating that another signal name follows.
DDUTIL - Data Dictionary Utility DDUTIL is a command line utility program that checks a unit's CSDB layout for obvious errors. It does this by checking the UNITDATA.DAT file in the unit configuration directory for cases where multiple signals share the same memory location, or two different signals have the same name. It can also sort the UNITDATA.DAT file to put the signal names in alphabetic order, making it easy to find signals when viewing or printing the file. The UNITDATA.DAT file in the unit configuration directory defines the layout of the signals in the unit's memory. However, The HMI does not consider the order of the signals in the UNITDATA.DAT file. There are a few isolated conditions where a mistake in the configuration can cause a signal to be defined multiple times. This can cause problems since the name of a signal must uniquely define the signal's memory location in the unit. DDUTIL scans the UNITDATA.DAT file looking for cases where multiple signals share the same memory location, or separate memory locations share the same signal name. If either of these cases is found, a warning message is displayed. Also if any invalid characters are found in any of the file's numeric fields, a warning is issued. If the SORT command line option is used, the original file is copied to the file UNITDATA.BAK, and a new signal name sorted version of UNITDATA.DAT is written. The sort is not performed if any invalid entries are found, but sorting can be done if duplicates are found. DDUTIL is a command line utility run from the unit configuration directory, as part of the standard MK5MAKE procedure. If run with the /? command line parameter, a help screen is provided.
4-38 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
If no errors are found then no messages are generated during the scanning process. If the SORT option was used, a message indicating that the file was sorted is printed. In the following example, no errors were found: F:\UNIT1>DDUTIL F:\UNIT1> In the next example, no errors were found, and the file was sorted in signal name order: F:\UNIT1>DDUTIL SORT SORTING COMPLETE: UNITDATA.DAT IS NEW FILE, UNITDATA.BAK IS OLD. F:\UNIT1>
MK5MAKE - Mark V Make - Mark V and Mark V LM MK5MAKE is a batch file that contains the commands typically used when rebuilding the CSDB layout for a Mark V or Mark V LM unit. This batch file can be used to rebuild the CSDB layout, recompile the unit's configuration tables, validate the unit's alarm list, and recompile sequencing. These are the steps that are typically taken when adding or modifying signals in the unit; MK5MAKE performs these steps in one command. MK5MAKE is typically run when signals are added to the unit, or signal parameters have been changed, such as the scale code. The MK5MAKE batch file simplifies the configuration steps by running the various tools in the correct order. When run, MK5MAKE performs the following steps: •
DDLOCATE is run to lay out the CSDB with the new signal definitions. It is run using the following assignment files: –
IO.ASG, FACTORY.ASG, ALLOCSSP.ASG, SITE.ASG
•
DDUTIL is run to validate the new layout, and sorts the resulting UNITDATA.DAT file
•
The Table Compiler (TABLE_C) is run to recompile all tables downloaded to the unit
•
The Alarm List program (ALARM_L) is run to validate the process alarm tables
The user is asked whether the sequencing should be recompiled. If the user replies Yes or does not answer within 30 seconds, the sequencing is recompiled using the Sequence Compiler (SEQCOMPL). MK5MAKE is a command line utility that runs from the unit configuration directory, and can take one optional command line parameter. This parameter is passed directly to the Table Compiler (TABLE_C) and is used to change the scale code set from the default of ENGLISH to a user specified scale code set. For example, to build using the METRIC scale code set, the following would be used: MK5MAKE /SCALE:METRIC.SCA MK5MAKE creates a log file that is basically a list of the outputs from running each individual tool. This file is stored as the MK5MAKE.LOG file in the unit configuration directory. The following example demonstrates this batch file in operation:
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-39
F:\UNIT1>MK5MAKE Point assignments are now being made using IO.ASG, FACTORY.ASG, ALLOCSSP.ASG, and SITE.ASG ------------ Opened PROM\UNITMAP.TPL file. ------------ Closed PROM\UNITMAP.TPL file. ------------ Opened file IO.ASG ------------ Closed file IO.ASG ------------ Opened file FACTORY.ASG ------------ Closed file FACTORY.ASG ------------ Opened file ALLOCSSP.ASG ------------ Closed file ALLOCSSP.ASG ------------ Opened file SITE.ASG ------------ Closed file SITE.ASG ------------ There were 1047 hardware and 478 software assign items found. ------------ Reading PROM\UNITDATA.TPL file. ------------ Reading PROM\UNITFREE.TPL file. The new UNITDATA.DAT file is now being validity-checked and sorted. SORTING COMPLETE: UNITDATA.DAT is new file, UNITDATA.BAK is old. The Table Files are now being re-compiled. TABLE_C: Table compiler for Mark V AP1 files. (Version 4.9) Loading data dictionary.....5920 points loaded. TABLE_C processing complete. The Alarm Listing File (ALARM.LST) is now being created. Loading data dictionary alarm.....467 alarm points loaded. Would you like to re-compile the Control Sequence Program at this time? (You have 30 seconds to answer Yes or No; a failure to respond will cause the Control Sequence Program to be re-compiled by default.) Please enter Y[es] or N[o]: Y Mark V - Control Sequence Program Compiler Revision Date: Aug 20 1997 at 11:12:38 Compiled on: Tue Dec 02 11:35:57 1997 ---> Loading the signal data base ---> Loading the BBL and PRIM block definitions ... BBL revision Major := 7 Minor : 1 ---> segment: F:\UNIT1\SEQ_TRN1.src ... 177 rungs processed ---> segment: F:\UNIT1\SEQ_B.src ... 5 rungs processed ---> Creating the AP1 sequencing file: F:\UNIT1\SEQ_Q.AP1 ---> Creating the AP1 sequencing file: F:\UNIT1\SEQ_B.AP1 -------- CSP Compiler Finished -------The results of making point assignments, validity-checking and sorting the new UNITDATA.DAT file, re-compiling the Table Files, rebuilding the alarm listing file, and re-compiling the Control Sequence Program have been stored in MK5MAKE.LOG. F:\UNIT1>
4-40 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
FMVID - Fuel Metering Valve ID - Mark V LM This program is only used for Mark V LM units with Dry Low Emissions (DLE) systems. FMVID is a command line configuration program that configures the Fuel Metering Valve (FMV) ID table in the controller. The FMV ID table is used to prevent the unit from running if the required Fuel Metering Valve linearization table matching the valve in use has not been downloaded into the controller. Each FMV must use the linearization table that matches that particular valve. These linearization tables are valve specific, with each serial numbered valve having its own table. Attempting to run the Mark V LM with a linearization table that does not match the actual valve can cause unexpected variations in the fuel flow rate. To prevent these mismatches, each linearization table ID field has the serial number of the calibrated valve. Using FMVID, the controller matches this ID to the actual valve. FMVID displays and configures the actual FMV information that is stored in a special section of the controller non-volatile memory. This program reads and optionally writes this non-volatile memory. When the Mark V LM is restarted, it compares the part number and serial number information in the non-volatile memory with the tables downloaded in the Linearization Data Base (LDB). If the part number and serial number in the FMV ID table does not match the part number and serial number in the LDB table, the controller will not start the turbine.
Operation FMVID is a command line configuration program. It requires the name of the unit as a command line parameter. If no additional parameters are given, it displays the FMV IDs stored in the unit. If run with the /SET option, it changes the FMV ID in the unit to match the serial number information in the /SET command. The format of the /SET option is: FMVID
/SET=::
The parameters are as follows: •
is the FMV number, starting with 1 for the first valve
•
The is the field for the valve part number.
•
The field is the serial number as defined in the linearization table for that particular valve.
Multiple /SET commands can be given in the FMVID command line. These commands are processed from left to right. If a valve number is repeated, the last entry is the one used. After all /SET commands have been processed, the nonvolatile memory in the unit is read and displays the results of the changes.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-41
If FMVID is run with no parameters, or the parameter of /?, it displays a help screen, as displayed in the following example: F:\UNIT1>fmvid /? FMVID - FMV IDENTIFICATION UTILITY This program will show the user which FMVs are listed in the unit's NonVolatile RAM (NVRAM) as being installed on the unit. The FMV identification can be changed by using the /SET option. COMMAND LINE: FMVID [/SET=::] The unit name must be supplied. If no /SET commands are supplied then no changes will be made, and the current settings will be shown. If one or more /SET commands are supplied, the values will be changed in the unit's NVRAM, and the resulting configuration will be shown. /SET=:: This option will set the given FMV number to expect the given part number and serial number. The FMV number is an integer (1..n), the part number and serial number are treated as strings. More than one /SET can be given on the command line. Example: FMVID T1 /SET=1:C329465-B2:11 This registers unit T1's FMV number one (1) as expecting part number C32465B2, serial number 11. After the change is made the new configuration is shown. F:\UNIT1>
LDB2RAM - Linearization Database to Memory Mark V LM LDB2RAM is a dynamic configuration tool that downloads an individual Linearization DataBase (LDB) table to the RAM of a Mark V LM controller. This allows for adjustment of the linearization factors for the run time system without changing the permanent configuration. Only LDB tables that have the Adjustable attribute set can be dynamically downloaded into RAM. When a Mark V LM panel is reset or powered-up, it reads the LDB tables from the LDB.AP1 unit configuration file and loads these tables into RAM. The unit then uses these tables for control. Each table has an attribute indicating if the table is Adjustable or not. If a table is not adjustable, then the only way to change it is to recompile and download it to the controller. On the next restart or power-up the new table is used. If the table is adjustable, it can be downloaded directly into RAM. LDB2RAM allows a user to make changes to these RAM resident LDB tables. This is accomplished by editing the LDB table definition in the HMI and then using the LDB2RAM utility to download that table directly into RAM, where the changes take effect immediately. Since this process does not change the LDB.AP1 file in the controller, restarting the unit reloads the original table into RAM. Note If it is required to undo the changes, the HMI file changes have to be undone. This prevents the changes from being downloaded during the next compile and download.
4-42 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
In order to download an LDB table to RAM, the following conditions must be met: •
The table must be marked as Adjustable in the HMI LDB table file
•
The table must be marked as Adjustable in the unit's RAM
•
The table ID must be the same the HMI file and the unit's RAM
•
The [X] table dimension in the HMI file and the unit's RAM must be the same
•
The [Y] table dimension in the HMI file and the unit's RAM must be the same
•
The [X] data values in the HMI file and the unit's RAM must be the same
•
The [Y] data values in the HMI file and the unit's RAM must be the same
Operation To change an LDB table in the unit RAM, first make the changes to the appropriate LDB table in the HMI unit configuration directory, and then download it using the LDB2RAM utility. Note Save a backup copy of the HMI file to undo changes if required later. LDB2RAM needs to know which unit to download, and which table to download. The unit is specified using the /UNIT= qualifier. The table can be specified using either the file name or the table number, by using either the /FILE= qualifier or the /TABLE= qualifier. The associated file is compiled and downloaded directly to the controller. If LDB2RAM is run with no command line values or with a command line parameter of /? , a help screen is displayed, as in the following example: F:\UNIT1>ldb2ram /? LDB2RAM - Download an LDB TABLE to a Mark V LM's RAM This program will read an LDB table and transmit it to the RAM in the specified unit. It does not alter the value in the LDB.AP1 file, that is done using the TABLE COMPILER (TABLE_C). COMMAND LINE: LDB2RAM /UNIT= [/TABLE=] [/FILE=] is the name of the unit is the number (decimal) of the table to download is the name of the file to be downloaded F:\UNIT1>
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-43
LDBCHK - Linearization Database Check Mark V LM LDBCHK is a command line configuration utility that is used on a Mark V LM to determine if any of the Linearization DataBase (LDB) tables are different in the unit's RAM versus the unit's LDB.AP1 configuration file. This indicates if any changes were made using the LDB2RAM utility since the last controller reset or power-up. When a Mark V LM controller is reset or powered up, it reads the LDB.AP1 configuration file and loads the LDB tables it finds into RAM. The controller then runs using these RAM resident tables. LDB2RAM is a utility program that can dynamically change the contents of the RAM resident LDB tables. Use of the LDB2RAM program results in the contents of the RAM and the contents of the configuration file being different. LDBCHK outlines the differences between the contents of the RAM and the LDB.AP1 file, and gives a list of the changes that were made.
Operation LDBCHK is a command line utility program that is typically run from a command prompt. It needs one command line parameter, the name of the unit to check. If run with no parameters or the /? parameter, it displays a help screen, as displayed in the following example: F:\UNIT1>LDBCHK /? LDBCHK - LDB Table Check Utility This program will check the LDB Table definitions in the given unit and report on Tables that have different values in the RAM than in the LDB.AP1 file. This indicates which values have been changed in RAM since the unit was restarted. COMMAND LINE: LDBCHK - The name of the unit to be checked. F:\UNIT1>
4-44 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
ALARM_L - Alarm List - Mark V ALARM_L is a command line utility program that generates a printable list of all of the process alarms that a controller can generate, complete with all the signal names and alarm text. The resulting alarm list file, ALARM.LST, includes a warning section if there are any alarms that do not have any associated alarm text strings defined. ALARM_L is used with the Backup Operator Interface (BOI) because the BOI only indicates a process alarm's drop number. The ALARM.LST file listing created by ALARM_L is printed and hung on the door of the Mark V control. This provides a way to look at the process alarm number and see the alarm text, as well as the name of the signal that created that alarm. This alarm listing is also useful when connecting the HMI to a Distributed Control System (DCS), since it provides a list of all of the process alarms generated by each turbine control. The last section of the alarm list, if needed, defines all of the alarms that have been defined, but do not have any alarm text strings defined. This is useful during unit configuration to check for alarms without text strings.
Operation ALARM_L is a command line utility that is run from the unit configuration directory. It takes no command line parameters, and generates the ALARM.LST file containing the output from the program, as displayed in the following example: F:\UNIT1>alarm_l Loading data dictionary alarm.....576 alarm points loaded. F:\UNIT1> SAMPLE OUTPUT (ALARM.LST) DROP# SIGNAL NAME ALARM TEXT ------ -------------- -------------------------------------0 1 2 3 4 5 6 7 8 9 10
DIAGNOSTIC ALARM FORCED LOGIC SIGNAL DETECTED PROTECTIVE MODULE ETR RELAY TROUBLE MASTER PROTECTIVE STARTUP LOCKOUT TURBINE INCOMPLETE SEQUENCE OVERSPEED TEST MODE SELECTED - HP OVERSPEED TEST MODE SELECTED - LP PROTECTIVE MODULE HP OVERSPEED - SD PROTECTIVE MODULE LP OVERSPEED - SD MANUAL SYNCHRONIZING LOCKOUT AUTO SYNCHRONIZING LOCKOUT
Chapter 4 Mark V • 4-45
CONSTSET - Constants Set - Mark V CONSTSET is a Mark V configuration utility to make all control constants adjustable, and to set the default ramp rate for each control constant. CONSTSET is not used with the Mark V LM. In previous generations of Operator Interfaces, all control constants were adjustable through the Control Constants Display. The HMI now supports a user-controlled list of the control constants considered adjustable, and the ones that are not. In addition, the ramp rate can be defined for each control constant that is adjustable. This concept is frequently used in Mark V LM applications, but not in Mark V applications. CONSTSET creates a default control constant configuration where all control constants are defined as being adjustable, and the default ramp rate is the same rate as used in the IDP Operator Interface. It is used in Mark V HMI applications to emulate the previous generation of operator interface, without having to configure each control constant by hand. Note As of TCI Version 1.2, the CONSTSET.DAT file is still required, but an option to automatically generate the default values at Data Dictionary load time has been added. Using this new option eliminates the need for running the CONSTSET program. Refer to the application information at the end of this section for more details.
Operation CONSTSET is a command line configuration utility. It requires one command line qualifier, the name of the Mark V unit, supplied using the /UNIT= qualifier. If run with no parameters or the /? parameter, a help screen is displayed as shown in the following example. F:\UNIT1>constset This program creates a CONSTSET.DAT file for a Mark V unit. The CONSTSET.DAT file defines which control constants are adjustable, and defines the ramp rate for each adjustable constant. The file created defines all control constants as adjustable. The ramp rate is set to approximately one display unit per second, where the display unit is defined by the control constant's scale code. COMMAND FORMAT: CONSTSET
/UNIT:
F:\UNIT1>
A sample of the CONSTSET.DAT file, the output of the CONSTSET program, is displayed in the following example: ; CONSTSET.DAT -- Control Constants Adjustment Settings File ; ; ; This file contains the adjustable constants for the unit. ; ; ; Point Name Engr Units Ramp Rate Min Value Max Value AFKQG "CNT09" 0.1 AFKQPC "CNT05" 0.001 AQK0_B "#/sec" 0.01 AQK0_E "#/sec" 0.01 <…and so on…>
4-46 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Application Information With TCI Version 1.2 and above, the unit can generate the Mark V default ramp rates without using the CONSTSET program. A new option in the CONSTSET.DAT file causes the Data Dictionary loader to recalculate the default ramp rates and set each control constant to be adjustable while loading the points into the Data Dictionary. This program has the advantage that any additions to the control constants, or new control constants, are automatically picked up when TCI is restarted, with no additional configuration work. To use this new option, create a CONSTSET.DAT file that contains as its first data line a line with the option name *MARK V_DEFAULT. This special line triggers the Dictionary Loader to set every control constant as adjustable, and set the ramp rate according to the default scale code table. The results are the same as the results of running CONSTSET. If desired, additional lines can be added to the CONSTSET.DAT file to override these defaults. This allows a user to make some control constants non-adjustable or to change the default ramp rate. Note Make sure that any lines changing the defaults are after the *MARK V_DEFAULT line, otherwise the lines are overridden when the defaults are computed. The following example displays a CONSTSET.DAT file where the default values were computed when TCI started: ; ;CONSTSET.DAT - CONTROL CONSTANT ADJUSTMENT SETTINGS ; ;This will set all control constants to be adjustable ;with a ramp rate of one display digit per second. ; *MARK V_DEFAULT ; ;Add any overrides desired here ;
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-47
EPA Log Configuration To define Mark V Control Data Points for the EPA screen, the user must modify the F:\UNITN\EPA_Q.SRC source file. With the use of the notepad editor, control data points can be added or removed from the file. The following is a sample EPA_Q.SRC source file: ; ----------------------------EPA_Q.SRC------------------------; Note that the TIME column header does not have to be defined in this file. : The header is automatically created when the program is run. ; ;SIGNAL NAME ; ----------------DWATT CTIM TTXM WXJ WXC FQG FQL CMHUM ;END OF FILE
Although any valid Mark V data point can be defined for the EPA Display, it is required that both WXJ (ACTUAL FUEL/WATER-STEAM RATIO) and WXC (required FUEL/WATER-STEAM RATIO) control data points be included in all EPA displays. In addition, it is required that the points WXJ and WXC be defined for the fourth and fifth positions (from the left) of the display respectively. Therefore, they must be in the fourth and fifth positions from the top in EPA_Q.SRC. Once the correct points have been added to the EPA_B.SRC file, the file must be compiled and downloaded to the processor.
4-48 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
SEQCOMPL - Sequencing Compiler - Mark V and Mark V LM The Control Sequence Compiler is a separate command line program that compiles Control Sequence Program (CSP) segments into one CSP for use in the controller. The Sequence Compiler compiles only the sequencing source segments (*.SRC) listed in MSTR_SEQ.CFG, the compiler configuration file. The Sequence Compiler is a command line program, not a Windows program. Only qualified personnel knowledgeable about turbine control and protection should use the Sequence Compiler. Improper use can adversely affect the control and protective features of the control system. Note Mark VI uses the toolbox.
File Structure The output of the Sequence Compiler is an *.AP1 file (or files) that can be downloaded to the controller. The downloadable sequencing filename is SEQ.AP1 for Mark V LM, and for Mark V there are two, SEQ_B.AP1 and SEQ_Q.AP1. The program always writes a text log file, MSTR_SEQ.LOG in the unit configuration directory. Along with the segment source files, the Sequence Compiler uses several unit specific files that contain signal name database definitions and definitions of the available application building blocks. PRIMITIVE.DEF and BIGBLOCK.DEF files are ASCII files that detail the programming blocks available for the particular unit control. UNITDATA.DAT is a data dictionary file the Sequence Compiler uses to check the validity of pointnames used in the segment source files. MSTR_SEQ.CFG
Executing the Sequence Compiler Selecting the Sequence Compiler icon, or typing SEQCOMPL, or hitting enter while at a command prompt in the unit specific directory initiates the compiling program. The Sequence Compiler creates a listing, MSTR_SEQ.LOG, of the errors found in the segments. These errors must be resolved by using the Sequence Editor program to make appropriate changes to the sequencing source files (*.SRC). The *.AP1 output files are not produced until the Sequence Compiler runs error free. A sample Sequence Compiler execution is as follows: F:\UNIT1>SEQCOMPL Mark V – Control Sequence Program Compiler Revision Aug 20 1997 at 11 : 12 : 38 Date: Compiled on: Mon Nov 17 11:36:06 1997 ---> Loading the signal data base ---> Loading the BBL and PRIM block definitions ...BBL revision Major := 7 Minor : 1 ---> segment: F:\UNIT\SEQ_TRN1.src ... 176 rungs processed ---> segment: F:\UNIT\SEQ_TRN2.src ... 110 rungs processed ---> segment: F:\UNIT\SEQ_TRN3.src ... 95 rungs processed ---> segment: F:\UNIT\SEQ_TRN4.src ... 81 rungs processed ---> segment: F:\UNIT\SEQ_TRB1.src ... 158 rungs processed ---> segment: F:\UNIT\SEQ_TRB2.src Frequency := 2 Skew 0 ... 140 rungs processed ---> segment: F:\UNIT\SEQ_TRB3.src Frequency := 2 Skew 1 ... 151 rungs processed ---> segment: F:\UNIT\SEQ_TRN1.src ... 176 rungs processed ---> segment: F:\UNIT\SEQ_TRN2.src ... 110 rungs processed ---> segment: F:\UNIT\SEQ_TRN3.src ... 95 rungs processed ---> segment: F:\UNIT\SEQ_TRN4.src ... 81 rungs processed ---> segment: F:\UNIT\SEQ_B.src ... 5 rungs processed ---> Creating the AP1 sequencing file: F:\UNIT\SEQ_Q.AP1 ---> Creating the AP1 sequencing file: F:\UNIT\SEQ_B.AP1 --------CSP Compiler Finished ----------
4-50 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Master Sequencing Configuration File The Master Sequencing Configuration File, MSTR_SEQ.CFG, governs the sequencing source files that are compiled for each controller in the unit, and at what rate the segments are run within the controller. MSTR_SEQ.CFG is a text file that can be modified by any word processor. Only qualified personnel knowledgeable about turbine control and protection should modify the Master Sequencing Configuration File, MSTR_SEQ.CFG. Improper use can adversely affect the control and protective features of the control system. The file is located in the unit configuration directory, typically F:\UNITn. The file features are as follows: •
A # character denotes a field to be processed.
•
The #LIST directive causes the compiler to produce a listing file MSTR_SEQ.LST. This is a text file, which can be viewed with any word processor. It is a text representation of the AP1 file to be downloaded to the controller. Typically, this directive is preceded by a ‘.’ to convert it to a comment.
•
The #BBL_REVISION contains the revision of the \PROM\BIGBLOCK.DEF file. This number must match the proms in the unit control. If not, the new AP1 file is not able to run after it is downloaded. The BIGBLOCK.DEF file revision must match the prom revision in the controller.
The following is a sample MSTR_SEQ.CFG Sequence Compiler Configuration File for Mark V: ------------------------------------------------------------------MSTR_SEQ.CFG: Configuration file for sequencing compiler ------------------------------------------------------------------.#LIST ------------------------------------------------------------------Major Minor UBL Major UBL Minor rev rev rev rev #BBL_REVISION 7 1 ------------------------------------------------------------------, , and Segments ------------------------------------------------------------------#_SEGMENTS Segment Frequency Skew within Frequency name power of 2 (>0) (units of 1/16 sec) #SEGMENT SEQ_TRN1 1 0 #SEGMENT SEQ_TRN2 1 0 #SEGMENT SEQ_TRN3 1 0 #SEGMENT SEQ_TRN4 1 0 #SEGMENT SEQ_TRB1 1 0 #SEGMENT SEQ_TRB2 2 0 #SEGMENT SEQ_TRB3 2 1 ------------------------------------------------------------------ and Segments ------------------------------------------------------------------#_SEGMENTS Frequency Skew within Frequency power of 2 (>0) (units of 1/16 sec) #SEGMENT SEQ_TRN1 1 0 #SEGMENT SEQ_TRN2 1 0 #SEGMENT SEQ_TRN3 1 0 #SEGMENT SEQ_TRN4 1 0 #SEGMENT SEQ_B 1 0 ------------------------------------------------------------------#END
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-51
In the sample listing the sequencing information is grouped as follows: •
The #Q_SEGMENTS tag indicates sequencing for the , , and processors.
•
The #B_SEGMENTS tag indicates sequencing for the and processors, (Mark V only)
•
The #END tag indicates the end of the document information.
The following example demonstrates the Frequency and Skew features: Segment
Frequency n
Skew within scan rate
name
power of 2 (>0)
(units of 1/16 sec)
W
1
0
X
2
0
Y
2
1
Z
8
3
The Frame Rate of the Mark V is 16, and the frequency parameter denotes the period in frames for the segment. To calculate the execution rate use the following formula: Execution rate in Hz for a segment = Frame Rate / Frequency 16 / 2 = 8 Hz Using the above configuration yields segment execution at the following Mark V frequencies and skews, where each occurrence of a letter represents the execution time: WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Z Z Z Z Z Z Z Z | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.| 0123456789ABCDEF 0.0sec 0.5sec 1.0sec 1.5sec 2.0sec 2.5sec 3.0sec 3.5sec 4.0s
The frame rate is 16 Hz so a maximum of 16 segment executions per second are possible. The execution rates are as follows:
4-52 • Chapter 4 Mark V
•
Segment W is run every frame, for a 16 Hz execution.
•
Segment X is run every two frames, for an 8 Hz execution.
•
Segment Y is run every two frames, for an 8 Hz execution, and is skewed by one frame.
•
Segment Z is run every eight frames, for a 2 Hz execution, and is skewed by three frames.
•
At Frame #0, the segments W and X run.
•
At Frame #1, the segments W, and Y run.
•
At Frame #3, the segments W, Y, and Z run.
GEH-6126C Vol II HMI Application Guide
For Mark V LM, the Sequencing Configuration File, MSTR_SEQ.CFG, is similar to the one for Mark V, except scan rate and offset replace frequency and skew. The following sample MSTR_SEQ.CFG file is for a Mark V LM. The scan rate governs how often the segment runs and the offset controls on which frame the execution begins. ; ; MSTR_SEQ.CFG for MKV LM ; --------------------------------------------------------------------Configuration file for sequencing compiler --------------------------------------------------------------------;#LIST Major Minor rev rev #BBL_REVISION 1 1 --------------------------------------------------------------------R, S, T Segments --------------------------------------------------------------------;
Frame Rate (base)10 20 40 80 160 320 640 1280
Frame Time(period)
Hz
; Scan Rate n = 1 = = msec iteration interval 100 ; Scan Rate n = 2 = = msec iteration interval 50 ; Scan Rate n = 4 = = msec iteration interval 25 ; Scan Rate n = 8 = = msec iteration interval 12.5 ; Scan Rate n = 16 = = msec iteration interval 6.25 ; Scan Rate n = 32 = = msec iteration interval 3.125 ; Scan Rate n = 64 = = msec iteration interval 1.5625 ; Scan Rate n = 128 = = msec iteration interval 0.78125 ; ; For Mark VLM the reference rate is 100 Hz, 10 msec #_SEGMENTS ; Scan rate, n Offset within scan rate #SEGMENT SEQ_10GE 1 0 ;GENIUS COMM ;CHECK #SEGMENT #SEGMENT #SEGMENT #SEGMENT #SEGMENT
SEQDOCMT - Sequencing Documentor - Mark V and V LM The Control Sequence Documentor is a separate command line program that produces a CSP control document. The CSP document is a text file that contains a representation of the CSP control program, and is used by field service and maintenance personnel to check out and debug the controller. It is also used as a hard copy to document the CSP. The Control Sequence Documentor uses only the sequencing source segments (*.SRC) listed in MSTR_SEQ.CFG, the compiler configuration file. The Sequence Documentor is a command line program, not a Windows program. Note Mark VI uses the toolbox.
File Structure The CSP Documentor program produces two files. The first, CSP.PRN, is a complete representation of the control. The second, CSP_XREF.PRN, is a signal name cross-referencing document. Both of these files are located in the unit configuration directory.
CSP.PRN The CSP.PRN document is a text file pre-formatted with page breaks to form a complete document. The CSP.PRN is a complete representation of the unit CSP. It can be viewed with any word processor with a fixed pitch font with line drawing characters. It is best to print this document with the CSP Printer program as it adapts the format of the document to the selected printer. Each page of the document begins with a header displaying the segment name, date, and page number. Each rung starts with a rung number followed by a graphic representation of the rung and finishing with signal and cross-referencing information. More than one rung can appear on any page. The page number represents the page number within the segment. The following is a sample CSP print output: Control Sequence Document for Segment F:\UNIT_EA\SEQ20_1.SRC Tue Nov 18 13:55:02 1997
Page - 34 << Rung Number 50 >>>
4-54 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
GP2SEL -- SELECTED GP2* VALUE USED IN SEQUENCING psi SEQ20_1 39 SEQ20_1 40 SEQ20_1 42 SEQ20_1 49 SEQ20_1 50 SEQ20_1 52 SEQ20_1 59 SEQ20_1 60 SEQ20_1 62 SEQ_10GG 52 SEQ_10GG -60 SEQ_10GG 64 GP3PFF -- PILOT TRIM VALVE P3 FEED FORWARD psi SEQ20_1 -49 SEQ20_1 50 N/D GP3T2_PFFX -- PILOT TRIM VALVE P3/P2 RATIO FEED FORWARD AUX SEQ20_1 -50 SEQ20_1 51 <<< Rung Number 51 >>>
GP3T2_PFF -- PILOT TRIM VALVE P3/P2 RATIO FEED FORWARD N/D SEQ20_1 -51 SEQ20_1 52 GP3T2_PFFX -- PILOT TRIM VALVE P3/P2 RATIO FEED FORWARD AUX N/D SEQ20_1 -50 SEQ20_1 51 RZERO -- FLOATING POINT CONSTANT N/D <0.0 N/D> SEQ20_1 18 SEQ20_1 31 SEQ20_1 38 SEQ20_1 41 SEQ20_1 48 SEQ20_1 51 SEQ20_1 58 SEQ20_1 61 SEQ_80 18 SEQ_80 43 SEQ_40 32 SEQ_10GG 66
CSP_XREF.PRN The CSP_XREF.PRN document is a text file pre-formatted with page breaks to form a complete document. It is a cross-reference document containing a list of signal names with the segment and rung number where the signal is used. It can be viewed with any word processor having a fixed pitch font. To print this document it is best to use the CSP Printer program as it adapts the format of the document to the selected printer.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-55
Along with the segment source files, the Control Sequence Documentor uses several unit specific files that contain signal name database definitions and definitions of the available application building blocks. PRIMITIVE.DEF and BIGBLOCK.DEF files are ASCII files that detail the programming blocks available for the particular controller. UNITDATA.DAT is a data dictionary file that contains the pointnames and types used in the segment source files. *.PIC files are used for the primitive and BBL block graphics. *.SCA files contain the engineering units. The LONGNAME.DAT file contains the corresponding signal long names. A CSP_XREF.PRN Sequence Documentor output example is as follows: Unit Master Cross Reference CDPSUMAVGA CDPSUMAVGB CDP_CUR CDP_CUR_REF CDP_ERR CDP_ERRABS CDP_NBIAS CDP_NSC CDP_POS_DMD CHIP_AGB CHIP_BSUMP CHIP_CSUMP CHIP_DSUMP CHIP_TGB CPCVAVG CPCVMAN_PV CPCVRATEVAL CPCV_MAN CPCV_PVGOOD CPCV_PVINP CP_CV CP_CV_SEL CS3 D30T2A D30T2B D30T2DIFF
-
Page 4
Fri Jan 31 10:53:51 1997
-- CDP VALVE LVDT A SECONDARY SUM AVERAGE V RMS SEQ_CAL -3 -- CDP VALVE LVDT B SECONDARY SUM AVERAGE V RMS SEQ_CAL -3 -- CDP BLEED VALVE SERVO DRIVER FEEDBACK QTBA-033 SEQ_640 63 -- CDP BLEED VALVE SERVO DRIVER OUTPUT % SEQ_640 63 SEQ_10GG -57 -- CDP BLEED VALVE DEMAND POSITION ERROR % SEQ_640 63 SEQ_10GG -57 -- ABSOLUTE VALUE OF CDP_ERR % SEQ_640 -63 -- CDP BLEED VALVE NULL BIAS BASED ON CDPSEL % SEQ_10GG -57 -- CDP BLEED VALVE SERVO CURRENT NULL COMPENSATION % SEQ_10GG 57 -- CDP BLEED VAVLE POSITION DEMAND % SEQ20_1 -23 SEQ_10GG 57 -ohms SEQ_640 76 -ohms SEQ_640 76 -ohms SEQ_640 76 -ohms SEQ_640 76 -ohms SEQ_640 76 -- BACKUP RATIO OF SPECIFIC HEATS (CP/CV) SEQ_0 -14 SEQ_640 8 -- PREVIOUS VALUE OF MANUAL SELECT CP/CV RATIO SEQ_640 -8 -SEQ_0 -14 SEQ_640 -8 -- RATIO OF SPECIFIC HEATS (CP/CV) FOR MANUAL SELECTION SEQ_640 8 -- RATIO OF SPECIFIC HEATS (CP/CV) FAULT TIME DELAY SEQ_640 -8 -- PREVIOUS VALUE OF CP/CV RATIO INPUT SEQ_640 -8 -- GAS FUEL RATIO OF SPECIFIC HEATS SEQ_0 -14 SEQ_0 -15 SEQ_640 8 -- SELECTED VALUE OF CP_CV USED IN SEQUENCIN SEQ_0 -14 SEQ20_1 42 SEQ20_1 52 SEQ20_1 62 SEQ_640 -8 SEQ_10GG 68 -- INTERMEDIATE HEAT SOAK GAIN SEQ_20 -4 -- ALMTXT:'COMPRSR INLET TEMP(T2A) SENSOR FAILED' AL 37 SEQ_40 -2 -- ALMTXT:'COMPRSR INLET TEMP(T2B) SENSOR FAILED' AL 38 SEQ_40 -2 -- ALMTXT:'T2A & T2B SENSOR DIFFERENTIAL' AL 42 SEQ_40 -2
To initiate the compiling program, either select the Control Sequence Documentor icon, or type SEQDOCMT, or press enter while at a command prompt in the unit specific directory. The Sequence Documentor has four possible parameters. They must be listed in order after the SEQDOCMT.EXE command. For example, a valid command line with all possible parameters is as follows: F:\UNIT1>SEQDOCMT.EXE METRIC.SCA N -LOG F:\UNIT1 •
The first parameter is the scale code file name; the default is ENGLISH.SCA.
•
The second parameter is Y or N where: –
N causes the documentor to skip cross-referencing
–
Y is the default to do cross-referencing
•
The third parameter is -LOG or -N. -LOG tells the documentor to produce a log file SEQDOCMT.LOG. The default is -N for no log file.
•
The fourth parameter is the path to the unitn directory. The default is to use the current default or working directory.
The Sequence Documentor can display error messages during operation. These errors must be resolved using the Sequence Editor program to make appropriate changes to the sequencing source files, *.SRC, or other unit configuration files as needed. Note Run the Sequence Compiler any time changes are made to the files in the unit configuration directory.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-57
SEQEDIT - Sequencing Editor - Mark V and Mark V LM CSP, the Turbine Control's application software, uses a programming language known as Big Block Language (BBL). BBL is a relay ladder logic based software structure that defines data flow and function execution. A series of rungs containing combinations of comments, relay ladder diagrams, Primitives, and Big Blocks makes up the software structure. The Sequence Editor is the application tool for making control changes by modifying the CSP. The Sequence Editor does not directly modify the control code running in the controller. It is an off-line tool, so its changes are made to a source file only. After saving the changes made with the Sequence Editor, the CSP must be compiled by the Sequence Compiler and downloaded to the controller. The Sequence Compiler and download functions are described later in this document. A segment consists of a set of sequential rungs. The Control Sequence Editor allows four different types of rungs as follows: •
RLD rungs, which are relay ladder diagram rungs.
•
PRIMITIVE rungs, which combine RLD operations with a primitive function block call.
•
BBL rungs, which are rungs without RLD operations, but with a Big Block call. Big Blocks are application modules that perform standardized control functions.
•
COMMENT rungs, which are rungs containing only text, usually identifying important information about the sequencing or segment.
The Sequence Editor creates new CSP segments or edits existing ones. Once the Sequence Editor creates the segment source files, the Control Sequence Compiler compiles them into the CSP for downloading to the controller. The compiler configuration file, MSTR_SEQ.CFG, selects the segments to compile and defines a unique scan rate and execution offset for each segment. The downloaded CSP segments provide the controller with the parameters and instructions on how to control the process.
File Structure The Sequence Editor operates on segment source files within the unit configuration directory, typically F:\UNITn. These files have a *.SRC extension. The CSP segment source files have a text format. Never edit the segment source files directly, use the Sequence Editor program to open, modify, and save them. Note Other source files in the unit configuration directory have a *.SRC extension that are not CSP segment source files. While it is possible to open these files, they are not sequencing files and their contents could be overwritten if the user attempts to modify and save them from the Sequence Editor. Along with the segment source files, the Sequence Editor uses several unit specific files that contain signal name database definitions, and definitions of the available software building blocks. PRIMITIVE.DEF and BIGBLOCK.DEF are ASCII files that detail the programming blocks available for the particular unit control. UNITDATA.DAT is a data dictionary file used by the Sequence Editor to check the validity of pointnames used in the segment source files. It is usually a good idea to restrict the editing of sequencing source files to a single unit at a time. This is because different units may have different functions defined in their associated BIGBLOCK.DEF and PRIMITIV.DEF files and different signals defined in their UNITDATA.DAT files.
4-58 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Modifications of these files is not necessary, and not recommended, as their contents correlate directly to the contents of the unit control’s block library. If a block is added, modified, or removed from the unit control, the factory provides new definition files along with new files for the controller’s block library. PROM\ PRIMITIVE.DEF
UNITDATA.DAT
PROM\ BIGBLOCK.DEF
SEQEDIT.EXE Control
{Segment name}.SRC
Sequencing
Original or New source
Editor
file
Control Sequence Editor File Structure
Using the Control Sequence Editor Editing a segment requires several standard operations. These operations include loading a segment from the disk, creating a new segment, finding an existing rung, creating a new rung, and saving a modified segment to a disk. Using either the dropdown menu options from the menu bar selections or the buttons on the toolbar performs the following operations: •
Starting the Control Sequence Editor and Loading segments
•
Opening the Control Sequence Editor window
•
Navigating within segments
•
Editing rungs
•
Selecting rungs
•
Copying rungs
•
Moving rungs
•
Adding or deleting rungs
•
Creating rungs
•
Viewing multiple segments
•
Saving a segment
•
Exiting the Control Sequence Editor
The following sections provide information about using these functions.
Starting The Control Sequence Editor To start the Control Sequence Editor 1
Select the Control Sequence Editor icon, or from the Command Prompt, enter: SEQEDIT
2
The Control Sequence Editor starts.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-59
Loading An Existing Segment The Sequence Editor loads existing segments in three ways. If the Sequence Editor starts from the command prompt, type the name of the segment after the Sequence Editor execution command, SEQEDIT. Include the source extension, .SRC with the segment name. For example, enter: F:\UNIT1>SEQEDIT {Segment name}.SRC where {Segment name}.SRC is a sequencing segment filename such as SEQ_160.SRC. To load an existing segment after starting the Sequence Editor, select the menu option File:Open command from the drop-down menu. The Sequence Editor provides a list of files with .SRC extensions. Select the desired file and press enter to load the segment. Selecting the toolbar button with the picture of an open file also provides a list of existing files. To load a recently edited segment, select the menu bar option File, and then the segment name from the drop-down menu. Note Not all the .SRC files are sequencing segment source files.
Loading A New Segment If no existing file is specified when the Sequence Editor starts, a blank screen displays. To start a new segment window, select the menu bar option File:New command from the drop-down menu. Note Exiting a new segment file without saving it loses the file.
4-60 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
The Control Sequence Editor Window The Sequence Editor operates in a Windows environment. The Editor performs functions selected from drop-down menu options from the menu bar or buttons on the toolbar: •
The titlebar displays the filename currently in the Sequence Editor.
•
The Sequence Editor opens each segment in a separate segment window that displays the segment one rung at a time.
•
RLD rungs display on an 8x8 matrix.
•
Primitive rungs display using a 4x8 permissive matrix and a tile representation of the primitive.
•
Big Blocks display as a tile representation of the Big Block.
•
The horizontal and vertical scroll bars allow viewing portions of rungs and blocks that exceed the segment window boundaries.
The Sequence Editor Window Displaying an RLD Rung
The menus and toolbar at the top of the screen incorporate items common to Windows applications along with special items associated with the Editor. The toolbar immediately beneath the menu bar corresponds to particular drop-down menu options. The toolbar buttons allow short cuts to common menu commands.
Navigating Within a Segment Window Individual rungs make up the sequencing segments. The top right hand corner of the segment window displays the rung number. Navigate between the rungs using either the drop-down menu options from the menu bar, the toolbar buttons, or the page up and down keys on the keyboard. The Edit:Find menu selection locates a signal name or block name within a given segment. No tools are provided to search all sequencing segment source files.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-61
Editing an Existing Rung The Editor allows for editing existing rungs as follows: •
Double clicking on an RLD component or name within a BBL or Primitive block accesses the signal name point list dialog box for changing the associated control signal name.
•
Selecting a component from the Component menu bar option or from the toolbar and doubling clicking on the addition location adds a component or changes an existing component.
•
Selecting a new control signal name from the signal name point list dialog box.
•
Selecting Edit:Comment from the menu displays the text window with the existing comment text. The text window allows modifying text or adding text to the comment rung.
•
Changing BBL blocks and Primitive blocks deletes the components on the rung. Changing the rung type also deletes the rung components.
•
Selecting the Delete Element from the Component menu, and double clicking on the component deletes the component. Adding components to the resulting gap in the rung is necessary for proper function of the rung.
Selecting Rungs Selecting rungs allows access for copying, editing, or deleting. Navigating to the rung and selecting the menu bar option Edit and the Select command from the drop-down menu highlights the rung to indicate its selection. Repeating the selection process for other rungs selects multiple rungs. Selecting the menu option Edit:Deselect deselects the rungs.
Copying Rungs The Sequence Editor allows for copying rungs within a segment window or to another segment window. To copy rungs 1
Navigate to the rung and select it using the menu option Edit:Select. The rung highlights.
2
Select the Edit:Copy menu item. Navigate to the insertion point and select the menu bar option Edit:Paste. The Editor inserts the copied rung and re-numbers the following rungs.
3
Selecting Paste in other locations inserts the copied rung again. Copying multiple selected rungs and pasting them copies the selected rungs and inserts them to the new location. Toolbar buttons also perform copy and paste functions.
Once a rung is selected and copied, the Editor permits copying to another segment window. Exiting the existing segment window and opening the new segment window, or opening a new segment window both allow for copying the rung from one segment to another. Copying the rung to another segment follows the above procedure.
4-62 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Moving Rungs The Sequence Editor allows for moving one rung or multiple rungs. The procedure is similar to copying rungs except the menu option Edit:Cut is used to remove the rung and re-number the following rungs. Navigating to the new rung location and selecting Edit:Paste inserts the rung to the new location and renumbers the following rungs. Cutting and pasting multiple selected rungs removes all selected rungs and inserts them in the new location. Note Toolbar buttons also perform the cut and paste functions.
Adding a Rung The Editor allows adding new rungs at any point in the segment. Navigate to the insertion point for the new rung. At the location, select the menu option Rung:Add. The Editor displays a dialog box to select adding the rung before or after the current rung. The selection adds a blank RLD rung and re-numbers the following rungs.
Deleting a Rung The Editor allows deleting rungs. Navigate to the desired rung and select the menu option Rung:Delete. A dialog box requesting confirmation of the deletion displays. Deleting a rung is permanent. Only exiting the Editor without saving restores a deleted rung since there is no undelete selection. To cancel a delete, select the Cancel button in the confirmation window.
Selecting the Rung Type New rungs are one of four different types. Selecting the Rung:Type menu item displays the Modify Rung Type dialog box that allows the choice of one of the four rung types as follows: •
RLD (relay ladder logic alone) displays a blank grid for adding components
•
Primitive (a basic block made up of relay ladder logic) displays another dialog box to choose the Primitive to add. Primitives display both a tile and an RLD grid and require signal names.
•
BBL (one large block alone) displays another dialog box to choose the BBL or Primitive to add. BBLs display as tiles, and often require signal names.
•
COMMENT (text only) rung type displays a blank screen without the RLD grid.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-63
Adding RLD Rungs Selecting the RLD rung type displays a blank RLD grid on the screen. Selecting the Components menu option displays a drop-down menu of the different possible components. Selecting a component from this menu allows it to be added to the grid. The new rung must begin at the top left grid line and end at the top right grid line. Double clicking on the grid line adds the component to that location. A Signal Name dialog box displays if the component is a normally open contact, normally closed contact, or coil or inverted coil. This dialog box allows for typing the control signal name or for browsing the control signal name database to select the control signal. If the control signal name or the type of signal is invalid for the component, the Editor displays a warning. Selecting cancel at the warning removes the use of that control signal name. Selecting OK allows for the use of the control signal name. RLD rungs must follow standard relay ladder logic format. Selecting Component:Delete Component from the menu and double clicking on the component deletes a component. Note The toolbar component buttons allow for quick component addition and deletion. The menu bar option Component has six commands available for editing RLD rungs and the RLD section of Primitive rungs as follows: •
The drop-down menu command NOC represents a Normally Open Contact component selection.
•
The NCC command represents a Normally Closed Contact selection.
•
The HOR drop-down menu command represents a Horizontal connector. This selection creates both horizontal and vertical connections. Selecting HOR and double clicking on a horizontal or vertical grid line adds the connector.
•
The Coil and ICoil commands from the drop-down menu select normal coils and inverted coils respectively.
•
The Delete Element command deletes any components as described above.
Adding Primitive Rungs Selecting the PRIMITIVE rung type displays a Select Primitive Function dialog box displaying a list of the available Primitives blocks. After selecting one of the Primitive blocks from the list, the Primitive block tile appears on the right side of the segment window. The left side of the segment window displays the RLD grid for adding components. Primitive blocks automatically include their associated coil. Double clicking on locations requiring control signal names displays the Signal Name dialog box. Primitive blocks typically require signal names on the coils and any locations indicated inside the primitive tile. Double clicking on a name inside the primitive tile displays the Signal Name dialog box for selecting the associated control signal name. Typically, a primitive block requires a contact or contacts to enable it. Follow the Adding RLD rungs rules to add the enabling contacts. Normally open contacts, normally closed contacts, connectors, or combinations are allowed.
Adding BBL Rungs Selecting the BBL rung type displays a Select Block Function dialog box. This dialog box displays the list of the available Big Blocks. After selecting one of the Big Blocks from the list, the BBL tile for that Big Block displays across the entire segment window because BBL blocks do not include any RLD rung components. Double clicking on a name within the block displays the Signal Name dialog box for selecting the associated control signal name.
4-64 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Adding Comment Rungs Selecting the COMMENT rung type displays a blank segment window. Adding text involves either selecting the menu option and Edit:Comment, or double clicking anywhere in the comment rung. The Edit Comment dialog box displays for typing the text comment. Selecting the OK button on the bottom of the text window adds the text to the comment rung. Selecting the Cancel button cancels the text addition and reverts to the blank comment rung. Note Comments of 40 characters wide and 20 lines long are allowed.
Viewing Multiple Segments Windows The Editor allows displaying any number of segments at one time. Multiple selection of the menu option File:Open from the drop-down menu opens multiple segment windows. The Window menu option provides a choice for displaying the multiple segment windows. Cascade displays the windows one after the other, down the screen in an overlapping fashion. Tile displays the windows in a non-overlapping tile fashion across the screen, dependent on the number of windows open. The Window menu option offers other commands for multiple segment windows. To open another window of a segment, select the menu bar option Window and the New command from the drop-down menu. The Editor allows multiple windows of the same segment, and all windows of the same segment reflect changes to one of the segment windows. The List 1,2, ... command displays a list of currently open segment windows at the bottom of the Window drop-down menu. A check mark appears in front of the segment name of the active window. A segment window chosen from this list becomes the active window. Note The latest segment window displays on top of the others unless Tile or Cascade are selected. Minimizing a window by clicking on its top left bar button and selecting Minimize removes the segment window from the presentation window and iconizes it. Double clicking on the icon loads the segment window back onto the Editor window. Selecting Maximize enlarges the segment window to fit the size of the Editor window. Using the cursor to select and drag the side bar of a segment window adjusts the size of the window. A highlighted title bar on a segment window indicates the segment window currently selected.
Saving a Segment Selecting the menu option File:Save or clicking on the toolbar Save button saves segments. Saving a file overwrites the previous file and all old information is lost. To save new segments, select the menu option File:Save As command from the drop-down menu. A Save As dialog box prompts for a new file name and directory location. The Save As dialog box appears if the Save command or Save toolbar button are selected and the segment was not given a name previously. Saving a segment overwrites the segment losing the data in the initial (unedited) file. It is recommended that, prior to editing a segment, the segment is copied to a separate location. After verifying the saved segment’s functionality, delete the old copy of the segment.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-65
Selecting the menu option File:Close closes a segment. A Save As dialog box displays when closing with new or not-yet saved segments, and asks whether to save the segment if the segment was changed and not saved prior to closing. Selecting Yes saves an existing segment or prompts for a file name for a new segment.
Exiting the Control Sequence Editor Selecting the menu option File:Exit exits the Editor program. The Save As dialog box asks whether to save the segment if the current file has not been saved. Selecting No exits the Editor without saving the segment, losing all changes. Selecting Yes saves the segment.
CSPPRINT - Control Sequence Program Printer Mark V and Mark V LM CSPPRINT is a command line utility for printing Control Sequence Program (CSP) documents using the standard Windows printing support. CSP documents represent the control sequencing used by the Mark V and Mark V LM. Note CSPPRINT is not designed for printing document types other than CSP. There are two options for printing a CSP document: •
Print a complete document at once to a default printer, or
•
Open the CSP Printer window for more control
CSPPRINT functions with other programs, as follows: •
CSP file, which is a pre-formatted file containing all the necessary information for pagination. CSPPRINT uses this information to display and print the CSP document.
•
Sequence Editor, used to modify the CSP source code (CSPPRINT is not an editor).
•
Sequence Documentor, which produces the CSP document (refer to Sequence Documentor in this chapter).
Note During the printing process, CSPPRINT runs at a lower priority to make CPU resources available to other processes.
File Structure CSPPRINT operates on two CSP documents produced by the Sequence Documentor utility: CSP.PRN and CSP_XREF.PRN. These files are located in the unit configuration directory. The CSP output document is pre-formatted containing all the necessary information for pagination. These files can also be viewed with any word processor that has access to a fixed pitch font with the line drawing characters. However, because the CSP documents are pre-formatted, they may not print correctly from the word processor. Note CSP.PRN, is a complete representation of the control. CSP_XREF.PRN, is a signal name cross-reference.
4-66 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Operation CSPPRINT is run from a DOS window at a command prompt, as follows: G:\EXEC\CSPPRINT.EXE
F:\UNIT1\CSP.PRN/p
The file name is F:\UNIT\CSP.PRN/p; and only one file name is permitted on the command line. Without /p, the command launches the CSP Printer window. The optional parameter /p (case sensitive) when entered on the command line along with a file name causes the entire CSP document to be printed to the default windows printer. No program window displays when using the /p parameter, however a dialog box displays the status of the print job formatting and gives the user the option to cancel the print job.
Using the CSP Printer The CSP Printer is a single document interface launched by the CSPPRINT utility. Use the menu selections at the top of the CSP Printer program screen to adjust the page appearance, select a printer, and print a CSP document. It allows only one CSP document to be displayed by the program at any time. More than one copy of the CSP Printer program can be run to view and print multiple CSP documents at the same time.
CSP Printer Window
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-67
Only one page of the CSP document is displayed at time. Use the Page menu or toolbar buttons to navigate through the pages of the document. The window title bar displays the CSP document name including the full path, current page number, and total number of pages in the CSP document. In print preview mode, the main window is replaced with a print preview window in which one or two pages are displayed in their printed format. To print the CSP document 1
Select File then Open. The *.PRN document in the unit configuration directory opens.
2
Select File then Page Setup to adjust the appearance of the page: •
If desired, select a header to be printed on each page.
•
Set the page margins in either metric or English units.
•
Select OK to accept the setup changes (or Cancel to cancel them) and return to the CSP display.
3
Select File then Print. The Print Dialog Box opens.
4
Select the printer and paper options, then select OK. A dialog box displays the print progress. To cancel CSP printing in progressw Select Cancel from the dialog box.
While printing, the CSP Printer program runs at a lower priority to make the CPU resources available to other processes. Therefore, if a CPU-intensive application is running, the CSP Printer Program stops until there is enough free CPU time to resume processing. Note Refer to your Microsoft Windows documentation for instructions on selecting printer and paper options.
TABLE_C - Table Compile - Mark V and Mark V LM TABLE_C is a configuration tool that compiles the configuration tables for Mark V and Mark V LM units. It takes the configuration information out of the ASCII configuration source files (*.SRC) and converts it to the binary images that the controller needs. The results are placed in a set of *.AP1 files. Editing a set of tables containing configuration information creates some of the configuration information. These tables contain the signals to be totalized, the signals to be treated as events, and the values of the control constants. The tables are edited in ASCII source files and stored as *.SRC files in the unit configuration directory. These *.SRC files refer to signals using the signal name. TABLE_C reads the *.SRC files and converts the contents from ASCII to binary format. It stores the binary files as *.AP1 files in the unit configuration directory. These binary *.AP1 files are downloaded to the controller to provide the table driven configuration information. Mark V and Mark V LM have different tables, and the binary format used is different in some cases. TABLE_C looks for the existence of the VXFR.AP1 file in the unit configuration directory as the indication of the unit type. If VXFR.AP1 is found, the unit is assumed to be a Mark V LM, if not it is assumed to be a Mark V.
4-68 • Chapter 4 Mark V
GEH-6126C Vol II HMI Application Guide
Operation TABLE_C is a command line configuration program run from the unit configuration directory. It looks to see if it is configuring a Mark V or a Mark V LM and processes the tables accordingly. If run with no parameters or with the /? parameter, a help screen displays. This help screen includes the list of tables supported by the unit type. A few of the table files contain values, such as the control constant values. These values must be translated from ASCII to binary values, using a scale code table. By default the ENGLISH.SCA file is used. This can be overridden by using the /SCALE= qualifier in the TABLE_C command line. TABLE_C requires a list of the tables to compile, supplied as parameters to TABLE_C. There is a special parameter ALL that compiles all the table files, as displayed in the following example: F:\UNIT1>TABLE_C ALL TABLE_C: Table compiler for Mark V AP1 files. Loading data dictionary.....5920 points loaded. TABLE_C processing complete. F:\UNIT1> In the preceding example, all the table files were compiled. In this case TABLE_C determined that the unit was a Mark V. F:\UNIT1>TABLE_C CONST TABLE_C: Table compiler for Mark V AP1 files. Loading data dictionary.....5920 points loaded. CONST WARNING: constant "COMMHTHY" not found, set to zero. TABLE_C processing complete. F:\UNIT1>
In the preceding example, only the Control Constant table was compiled. TABLE_C found that the Control Constant named COMMHTHY was defined in the unit, but no value was given for it in the configuration table. It warns that this constant is being given the value of zero. Note The ALL parameter is also used by MK5MAKE to compile all tables.
GEH-6126C Vol II HMI Application Guide
Chapter 4 Mark V • 4-69
EEPROM Downloader - Mark EEPROM is a Mark V configuration utility that downloads binary configuration information from the HMI into the non-volatile memory in the Mark V controller. Mark V LM uses the UDF program to do this. Note Mark VI uses the toolbox. Various configuration tools create the *.AP1 files that define the Mark V controller configuration. These include the Sequence Compiler, the Table Compiler, and the I/O Configurator. These files are stored in the unit configuration directory for each unit, and must be downloaded from the HMI to the non-volatile memory in the controller for them to take effect. The non-volatile memory in the Mark V is EEPROM (Electronically Erasable PROM). The EEPROM program does the download, provides a directory command to view the contents of the Mark V EEPROM, and does a simple check to verify the unit's EEPROM has not been corrupted. Note The EEPROM program transfers the configuration from the HMI to the controller
Operation EEPROM is a command line utility program that is typically run from a DOS prompt. If run with no parameters or the /? parameter, help is provided, as displayed in the following example: F:\UNIT1>EEPROM /? Mark V EEPROM downloader. EEPROM
