GEH-6126
HMI for SPEEDTRONIC™ Turbine Controls
Application Manual
HMI for SPEEDTRONIC™ Turbine Controls Application Manual GEH-6126 Issue Date: 1999-01-25
1999 General Electric Company, U.S.A. All rights reserved. Printed in the United States of America.
ARCNET is a registered trademark of Datapoint Corporation. CIMPLICITY is a trademark of GE Fanuc Automation North America, Inc. Ethernet is a trademark of Xerox Corporation. GE and are registered trademarks of General Electric Company, USA. IBM is a registered trademark of International Business Machines Corporation. PC is a registered trademark of International Business Machines Corporation. Microsoft, Windows, Windows NT are registered trademarks of Microsoft Corporation. Modbus is a trademark of Modicon. Series 90 is a trademark of GE Fanuc Automation North America, Inc. SPEEDTRONIC is a trademark of General Electric Company, USA.
Safety Symbol Legend
Indicates a procedure or condition that, if not strictly observed, could result in personal injury or death.
Indicates a procedure or condition that, if not strictly observed, could result in damage to or destruction of equipment.
Note Indicates an essential or important procedure, condition, or statement.
GEH-6126
a
! Warning
! Caution
b
To prevent personal injury or equipment damage caused by equipment malfunction, only adequately trained personnel should modify any programmable machine.
The example and setup screens in this manual do not reflect the actual application configurations. Be sure to follow the correct setup procedures for your application.
GEH-6126
Contents Chapter 1 Overview.....................................................................................................................................1 Introduction............................................................................................................................................................... 1 Related Documents ................................................................................................................................................... 4 SPEEDTRONIC Mark V Turbine Control – GEH-5979 ...................................................................................... 4 SPEEDTRONIC Mark V Turbine Control – GEH-5980 ...................................................................................... 4 SPEEDTRONIC Mark V Turbine Control Application Manual Overview – GEH-6195 .................................... 5 SPEEDTRONIC Turbine Control Panel Manual Overview – GEH-6354............................................................ 5 CIMPLICITY Base System User's Manual – GFK-1180 ..................................................................................... 5 Getting Assistance................................................................................................................................................. 5
Chapter 2 Start Up.......................................................................................................................................7 Logging On ............................................................................................................................................................... 7 Main Cimview........................................................................................................................................................... 7 Alarm Displays ......................................................................................................................................................... 8 Commands ................................................................................................................................................................ 8 Style Recommendations........................................................................................................................................ 8 Advanced Topics ...................................................................................................................................................... 9 Trending................................................................................................................................................................ 9 Point Control Panel ............................................................................................................................................... 9 Demand Display.................................................................................................................................................. 10 Chapter 3 Theory of Applications ...............................................................................................................11 Advanced Data Flow............................................................................................................................................... 11 Directory Structure.................................................................................................................................................. 12 TCI Directories: .................................................................................................................................................. 12 Drive F: Files ...................................................................................................................................................... 13 Drive F: Sub-directories...................................................................................................................................... 14 Drive G: Sub-directories ..................................................................................................................................... 14 Program Categories................................................................................................................................................. 15 Displays............................................................................................................................................................... 16 Control ................................................................................................................................................................ 16 Configuration ...................................................................................................................................................... 16 Remote Data and Control.................................................................................................................................... 16 Chapter 4 Display Applications ..................................................................................................................17 Introduction............................................................................................................................................................. 17 ARCWHO............................................................................................................................................................... 17 Purpose................................................................................................................................................................ 17 Background ......................................................................................................................................................... 17 Operation............................................................................................................................................................. 17 CARD_ID ............................................................................................................................................................... 18 Purpose................................................................................................................................................................ 18 Background ......................................................................................................................................................... 18
GEH-6126
i
Operation............................................................................................................................................................. 19 Examples............................................................................................................................................................. 20 Mark V Example ............................................................................................................................................. 20 Mark V LM Example ...................................................................................................................................... 21 CHECKCRC ........................................................................................................................................................... 22 Purpose................................................................................................................................................................ 22 Background ......................................................................................................................................................... 22 Operation............................................................................................................................................................. 23 Example .............................................................................................................................................................. 23 Diagnostic Counters Display................................................................................................................................... 24 Purpose................................................................................................................................................................ 24 File Type ............................................................................................................................................................. 24 Mark V LM ..................................................................................................................................................... 24 Mark V ............................................................................................................................................................ 24 Using the Diagnostic Counters Display Program.................................................................................................... 25 Executing Diagnostic Counters Display (DIAGC) ............................................................................................. 25 The Diagnostic Counters Display Window............................................................................................................. 26 Tree View............................................................................................................................................................ 26 Diagnostic Counter Data Window ...................................................................................................................... 27 Header ............................................................................................................................................................. 28 Legend............................................................................................................................................................. 28 Data Area ........................................................................................................................................................ 28 Selecting a Diagnostic Counters Display ............................................................................................................ 29 Interpreting Data ................................................................................................................................................. 29 Information for Card Designers ...................................................................................................................... 29 Dynamic Rung Display ........................................................................................................................................... 30 Purpose................................................................................................................................................................ 30 File Structure....................................................................................................................................................... 30 Dynamic Rung Display Screen Description........................................................................................................ 31 Rung Windows........................................................................................................................................................ 32 Rung Window Header......................................................................................................................................... 33 Header Timetag................................................................................................................................................... 33 Big Blocks and Comment Rungs .................................................................................................................... 33 RLD and Primitive Rungs ............................................................................................................................... 33 Data Display........................................................................................................................................................ 33 RLD Rungs ......................................................................................................................................................... 33 Contacts........................................................................................................................................................... 33 Coils ................................................................................................................................................................ 34 Primitive Rungs................................................................................................................................................... 34 Big Blocks........................................................................................................................................................... 34 Comment Rungs.................................................................................................................................................. 35 Picture File Windows .............................................................................................................................................. 36 Picture File Window Header ............................................................................................................................... 36 Header Timetag................................................................................................................................................... 37 Static Display .................................................................................................................................................. 37 Values Display ................................................................................................................................................ 37 Main Frame Window .............................................................................................................................................. 37 Using The Dynamic Rung Display ......................................................................................................................... 38 Starting the Dynamic Rung Display.................................................................................................................... 38 Selecting a Sequencing Display screen ............................................................................................................... 38 Using the Find All function................................................................................................................................. 38 Viewing Tabular Data ......................................................................................................................................... 39 Prevote Data Display............................................................................................................................................... 40 Purpose................................................................................................................................................................ 40 Menu Structure.................................................................................................................................................... 40 File .................................................................................................................................................................. 40
ii
GEH-6126
Edit........................................................................................................................... ....................................... 40 View........................................................................................................................... ..................................... 40 Help........................................................................................................................... ...................................... 40 Command Line Description ....................................................................................................... ......................... 41 Header Timetag................................................................................................................. .................................. 41 Trip History Log ............................................................................................................... ...................................... 41 Purpose........................................................................................................................ ........................................ 41 File Type ...................................................................................................................... ....................................... 42 Viewing........................................................................................................................ ................................... 42 Configuration .................................................................................................................. ................................ 42 Trip History Dialog Box Description............................................................................................ ...................... 44 Trip History................................................................................................................... .................................. 44 Saved Data ..................................................................................................................... ................................. 44 New Data ....................................................................................................................... ................................. 44 Data Retrieval ................................................................................................................. ................................ 45 Viewing Results ................................................................................................................ .............................. 45 Executing the Trip History Program ............................................................................................. ...................... 46 Trip History Log List Viewer ................................................................................................... .............................. 47 Purpose........................................................................................................................ ........................................ 47 File Type ...................................................................................................................... ....................................... 47 Mark V Trip Log List Viewer Dialog Box......................................................................................... ................. 48 Data Retrieval ................................................................................................................. ................................ 48 Viewing Results ................................................................................................................ .............................. 48 Executing the Mark V Trip Log List Viewer ...................................................................................... ............ 48 VIEW2 .......................................................................................................................... .......................................... 49 Purpose........................................................................................................................ ........................................ 49 Background ..................................................................................................................... .................................... 49 Operation...................................................................................................................... ....................................... 49 Examples....................................................................................................................... ...................................... 50
Chapter 5 Control .......................................................................................................................................53 Introduction............................................................................................................................................................. 53 Logic Forcing Display............................................................................................................................................. 53 Purpose................................................................................................................................................................ 53 File Structure....................................................................................................................................................... 55 Using the Logic Forcing Display Program.......................................................................................................... 56 Forcing and Unforcing Logic Signals ................................................................................................................. 56 Starting the Logic Forcing Display ..................................................................................................................... 57 Loading a Logic Forcing Display File ................................................................................................................ 58 Logic Forcing Display Window...................................................................................................................... 59 Logic Forcing Display Screen Window .......................................................................................................... 59 Navigating Within a Logic Forcing Display Screen ....................................................................................... 61 Modifying a Pointname or Line ...................................................................................................................... 61 Adding and Deleting a Pointname Line .......................................................................................................... 61 Using the Command Targets........................................................................................................................... 61 Printing From the Logic Forcing Display File ................................................................................................ 62 Other Options.................................................................................................................................................. 62 Saving a Logic Forcing Display File............................................................................................................... 62 Exiting the Logic Forcing Display Program ................................................................................................... 62 Control Constants Display ...................................................................................................................................... 63 Purpose................................................................................................................................................................ 63 Menu Structure.................................................................................................................................................... 63 Command Line Description ................................................................................................................................ 64 Header Timetag................................................................................................................................................... 64 Changing a Control Constant .............................................................................................................................. 64
GEH-6126
iii
Control Constants Adjust Display........................................................................................................................... 65 Purpose................................................................................................................................................................ 65 Demand Display...................................................................................................................................................... 65 Purpose................................................................................................................................................................ 65 Demand Display Menu Screen............................................................................................................................ 66 Demand Display Data Screen.............................................................................................................................. 66 File Structure....................................................................................................................................................... 66 Using the Demand Display Program................................................................................................................... 67 Starting the Demand Display Program................................................................................................................ 67 Loading Demand Display Files and Screens....................................................................................................... 69 The Demand Display Window............................................................................................................................ 70 Demand Display Screens Window.................................................................................................................. 72 Header ............................................................................................................................................................. 73 Legend............................................................................................................................................................. 74 Data Area ........................................................................................................................................................ 74 Immediate Action............................................................................................................................................ 75 Arm/Execute ................................................................................................................................................... 75 Analog Setpoint............................................................................................................................................... 75 Selecting a Demand Display Screen ................................................................................................................... 75 Creating a New Demand Display Screen ........................................................................................................ 76 Modifying a Demand Display Screen Definition/Type................................................................................... 76 Changing a Display Title................................................................................................................................. 77 Navigating ....................................................................................................................................................... 78 Adding/Deleting a Pointname or Line............................................................................................................. 78 Modifying a Pointname or Line ...................................................................................................................... 78 Adding a Command Target ............................................................................................................................. 78 Deleting a Command Target ........................................................................................................................... 80 Modifying a Command Target ........................................................................................................................ 80 Using a Command Target ............................................................................................................................... 80 Printing............................................................................................................................................................ 81 Other Options .................................................................................................................................................. 81 Saving Demand Display Screens and Demand Display Files ......................................................................... 81 Copying Demand Display Screen Definitions................................................................................................ 82 Exiting the Demand Display Program............................................................................................................. 82 Alarm Logger Control............................................................................................................................................. 82 Purpose................................................................................................................................................................ 82 Using the Alarm Logger Dialog Box .................................................................................................................. 83 Select Information to be Printed.......................................................................................................................... 83 Select Unit........................................................................................................................................................... 84 Executing the Alarm Logger Control.................................................................................................................. 84 Command Line Description ................................................................................................................................ 85 Header Timetag ............................................................................................................................................... 85 Hold List ................................................................................................................................................................. 85 Hold List Points................................................................................................................................................... 86 Hold List Programs ............................................................................................................................................. 86 Hold List Rules ................................................................................................................................................... 86 Manual Sync Object................................................................................................................................................ 87 Scope Tab............................................................................................................................................................ 88 Breaker Tab......................................................................................................................................................... 89 Permissives Tab .................................................................................................................................................. 90 Buttons Tab ......................................................................................................................................................... 91 Values Tab .......................................................................................................................................................... 92 Colors Tab........................................................................................................................................................... 93
Chapter 6 Configuration.............................................................................................................................. 93 Introduction ............................................................................................................................................................. 93
iv
GEH-6126
HMI Configuration ................................................................................................................................................. 94 HMI Configuration Overview............................................................................................................................. 94 TCI Configuration............................................................................................................................................... 96 TCI Registry Information - Control Panel Applet............................................................................................... 97 TCI Configuration Files ...................................................................................................................................... 98 F:\CONFIG.DAT ............................................................................................................................................ 98 F:\TIMEZONE.DAT....................................................................................................................................... 98 Optional Configuration Files............................................................................................................................... 98 TCI Font Loading................................................................................................................................................ 99 TCI Print Queues ................................................................................................................................................ 99 EPA Log................................................................................................................................................................ 100 EPA Logger ...................................................................................................................................................... 100 EPA Data Display ............................................................................................................................................. 102 Defining EPA Data Points ............................................................................................................................ 102 Turbine Control Maintenance Icons.................................................................................................................. 104 Stagelink ............................................................................................................................................................... 105 Terms of Reference........................................................................................................................................... 106 Stage Link Characteristics................................................................................................................................. 106 The Primary Operator Interface, HMI........................................................................................................... 107 Cable Recommendations............................................................................................................................... 107 Total Effective Distance Rules...................................................................................................................... 109 Redundant System Rules (Mark V Only)...................................................................................................... 110 Examples....................................................................................................................................................... 111 Fiber Optics....................................................................................................................................................... 113 Advantages.................................................................................................................................................... 113 Disadvantages ............................................................................................................................................... 114 Review of Components ..................................................................................................................................... 114 Basics ............................................................................................................................................................ 114 Cable ............................................................................................................................................................. 115 Hubs .............................................................................................................................................................. 115 Connectors .................................................................................................................................................... 116 System Considerations ...................................................................................................................................... 116 Installation......................................................................................................................................................... 117 Specifications .................................................................................................................................................... 118 Four Fiber Cable without Armor................................................................................................................... 118 Four Fiber Cable with Armor........................................................................................................................ 119 Fiber Optic Hub ............................................................................................................................................ 121 Fiber Optic Connectors ................................................................................................................................. 121 Typical Stage Link Addresses....................................................................................................................... 121 Control Hierarchy ................................................................................................................................................. 123 Overview........................................................................................................................................................... 123 Defining a Control Hierarchy........................................................................................................................ 123 Time Zone Make Utility Program – TZ_MAKE .......................................................................................... 129 TCI Control Panel Applet .................................................................................................................................... 132 Auto Login ........................................................................................................................................................ 132 ARCNET .......................................................................................................................................................... 132 Site .................................................................................................................................................................... 133 Time Sync ......................................................................................................................................................... 133 TCI Alarm and Event Logger ........................................................................................................................... 133 CIMPLICITY Project ....................................................................................................................................... 134 Introduction................................................................................................................................................... 134 Setup ............................................................................................................................................................. 134 Signals........................................................................................................................................................... 135 Alarms........................................................................................................................................................... 136 Importing Signals.......................................................................................................................................... 136 Configuring Exciter Alarms .......................................................................................................................... 138
GEH-6126
v
Unit Configuration ................................................................................................................................................ 139 Unit Configuration Overview............................................................................................................................ 139 HMI F: \ Drive Configuration Files .................................................................................................................. 140 HMI Unit-Specific Directory ............................................................................................................................ 142 Unit-Specific Assignment Files..................................................................................................................... 142 Unit-Specific Data Dictionary Files .............................................................................................................. 143 Unit-Specific I/O Configuration Constants ................................................................................................... 144 Unit-Specific Table Files .............................................................................................................................. 145 Unit-Specific CSP Segment Files.................................................................................................................. 146 Compiling Unit-Specific Configuration Files ................................................................................................... 146 Downloading Unit-Specific Configuration Files............................................................................................... 147 Control Constants.............................................................................................................................................. 147 DABUILD......................................................................................................................................................... 148 DCBUILD1 ....................................................................................................................................................... 149 DDLOCATE ..................................................................................................................................................... 151 DDUTIL............................................................................................................................................................ 154 MK5MAKE....................................................................................................................................................... 155 FMVID.............................................................................................................................................................. 157 Overview....................................................................................................................................................... 157 Operation....................................................................................................................................................... 157 LDB2RAM........................................................................................................................................................ 158 Overview....................................................................................................................................................... 158 Operation....................................................................................................................................................... 159 LDBCHK .......................................................................................................................................................... 160 Overview....................................................................................................................................................... 160 Operation....................................................................................................................................................... 160 ALARM_L........................................................................................................................................................ 160 Overview....................................................................................................................................................... 160 Operation....................................................................................................................................................... 161 DMD2SRC........................................................................................................................................................ 161 Overview....................................................................................................................................................... 161 Starting The Demand Display to Source Conversion Program ..................................................................... 167 Editing the Demand Display Source File ...................................................................................................... 168 CONSTSET ...................................................................................................................................................... 168 Overview....................................................................................................................................................... 168 Operation....................................................................................................................................................... 168 Application Information ................................................................................................................................ 169 CONSTCHK ..................................................................................................................................................... 170 Overview....................................................................................................................................................... 170 Operation....................................................................................................................................................... 170 Example......................................................................................................................................................... 171 SEQCOMPL (Sequencing) ............................................................................................................................... 171 Overview....................................................................................................................................................... 171 File Structure................................................................................................................................................. 172 Executing the Sequence Compiler ................................................................................................................ 172 Master Sequencing Configuration File.......................................................................................................... 173 SEQDOCMT (Sequencing)............................................................................................................................... 177 Overview....................................................................................................................................................... 177 File Structure................................................................................................................................................. 177 SEQEDIT (Sequencing).................................................................................................................................... 181 Overview....................................................................................................................................................... 181 File Structure................................................................................................................................................. 182 Using The Control Sequence Editor.............................................................................................................. 183 Starting The Control Sequence Editor........................................................................................................... 184 Loading An Existing Segment ...................................................................................................................... 184 Loading A New Segment .............................................................................................................................. 185
vi
GEH-6126
The Control Sequence Editor Window ......................................................................................................... 185 Navigating Within a Segment Window......................................................................................................... 186 Editing an Existing Rung .............................................................................................................................. 186 Selecting Rungs............................................................................................................................................. 186 Copying Rungs.............................................................................................................................................. 186 Moving Rungs................................................................................................................................................... 187 Adding A Rung ............................................................................................................................................. 187 Deleting A Rung ........................................................................................................................................... 187 Selecting The Rung Type.............................................................................................................................. 187 Adding Rld Rungs......................................................................................................................................... 187 Adding Primitive Rungs................................................................................................................................ 188 Adding BBL Rungs....................................................................................................................................... 188 Adding Comment Rungs............................................................................................................................... 188 Viewing Multiple Segments Windows.......................................................................................................... 189 Saving a Segment.......................................................................................................................................... 189 Exiting the Control Sequence Editor............................................................................................................. 190 CSPPRINT........................................................................................................................................................ 190 Overview....................................................................................................................................................... 190 File Structure................................................................................................................................................. 190 Using the CSP Printer Program..................................................................................................................... 191 Command Line Arguments ........................................................................................................................... 191 Screen Description ........................................................................................................................................ 191 Page Setup..................................................................................................................................................... 192 Printer Selection............................................................................................................................................ 193 How to Print the CSP .................................................................................................................................... 193 TABLE_C (Table Compile).............................................................................................................................. 193 Overview....................................................................................................................................................... 193 Operation....................................................................................................................................................... 194 IO Configuration ................................................................................................................................................... 195 EEPROM .......................................................................................................................................................... 195 Overview....................................................................................................................................................... 195 Operation....................................................................................................................................................... 196 Application Information................................................................................................................................ 197 UDF ................................................................................................................................................................. 198 Overview....................................................................................................................................................... 198 Operation....................................................................................................................................................... 199
Chapter 7 Remote Access and Control....................................................................................................201 Remote Access...................................................................................................................................................... 201 Web Interface.................................................................................................................................................... 201 FTP Interface .................................................................................................................................................... 202 Remote Mount Disks ........................................................................................................................................ 202 GEIS Standard Message Formats.......................................................................................................................... 202 Introduction....................................................................................................................................................... 202 Notation............................................................................................................................................................. 202 Timetag Considerations .................................................................................................................................... 204 GSM Message Type Summary ......................................................................................................................... 205 Administrative Message Formats...................................................................................................................... 206 Supported Controller Request: ...................................................................................................................... 206 Supported Controller Response......................................................................................................................... 207 Heartbeat Message ............................................................................................................................................ 208 Event-Driven Data Messages............................................................................................................................ 209 Alarm Record Establish Request................................................................................................................... 209 Alarm Record Establish ACK/NAK Response ............................................................................................. 209 Alarm Data Messages ................................................................................................................................... 210
GEH-6126
vii
Digital Input Record Establish Request ........................................................................................................ 213 Digital Input Record Establish ACK/NAK Response ................................................................................... 214 Digital Input Data Messages ......................................................................................................................... 215 Software Event Record Establish Request .................................................................................................... 217 Software Event Record Establish ACK/NAK Response............................................................................... 218 Software Event Data Messages ..................................................................................................................... 219 Periodic Data Messages .................................................................................................................................... 221 Periodic Data Request ................................................................................................................................... 221 Periodic Data ACK/NAK Response.............................................................................................................. 223 Periodic Data Message .................................................................................................................................. 223 Command Messages.......................................................................................................................................... 224 Alarm Command Request ............................................................................................................................. 224 Alarm Command ACK/NAK Response........................................................................................................ 225 Alarm Dump Messages ................................................................................................................................. 226 Process Control Command Requests: ........................................................................................................... 230 Process Control Command ACK/NAK Response......................................................................................... 231 Application Notes.............................................................................................................................................. 233 Networking.................................................................................................................................................... 233 TCP communications .................................................................................................................................... 234 Telnet Interface ............................................................................................................................................. 234 Command Summary:..................................................................................................................................... 235 Point ID Hint Parameter ................................................................................................................................ 235 EGD .............................................................................................................................................................. 235 TCI Modbus .......................................................................................................................................................... 236 Introduction ....................................................................................................................................................... 236 Modbus Slave................................................................................................................................................ 236 Modbus Master.............................................................................................................................................. 236 MODBUS_L ..................................................................................................................................................... 237 Overview....................................................................................................................................................... 237 Operation....................................................................................................................................................... 237 Specifications ................................................................................................................................................ 238 External Communication Links- Modbus Slave mode.................................................................................. 238 External Communication Links- Modbus Master Mode ............................................................................... 239 RS232 and Modbus ........................................................................................................................................... 239 Physical Link Layer/Format, RS232 Communications..................................................................................... 240 Link Layer..................................................................................................................................................... 240 Physical Layer ............................................................................................................................................... 240 TCI Modbus Configuration............................................................................................................................... 243 F:\IO_PORTS.DAT: Modbus Link Definition.............................................................................................. 243 Modbus Master Setup.................................................................................................................................... 244 Modbus Slave configuration: Holding Coils, Input Coils, Holding Registers, Input Registers .................... 245 Modbus Slave: @SPARE: Unused Coils and Registers................................................................................ 246 Modbus Slave: F:\UNITn\MODBUS.DAT: MODBUS Mapping File Format............................................. 246 Modbus Master Configuration ...................................................................................................................... 248 Description Of Modbus_Data_File ................................................................................................................... 250 Table_Type Table_point CSDB_Pointname ............................................................................................... 250 MODBUS_L.EXE: MODBUS Listing Program........................................................................................... 251 F:\UNITn\MODBUS.LST: MODBUS Listing File ...................................................................................... 252 Modbus Data Format And Scaling.................................................................................................................... 254 Modbus Data Conversions: Logics ............................................................................................................... 254 Modbus Data Conversions: Analogs ............................................................................................................. 254 RS16.............................................................................................................................................................. 254 RU16 ............................................................................................................................................................. 255 UN12............................................................................................................................................................. 255 HW12 ............................................................................................................................................................ 256 NATIVE........................................................................................................................................................ 257
viii
GEH-6126
Modbus Command And Response Definition......................................................................................... .......... 257 Introduction................................................................................................................................................... 257 RTU Transmission Mode.................................................................................................................................. 258 Message Errors.............................................................................................................................................. 258 Exception Code Response Format .................................................................................................................... 259 Function Code Details................................................................................................................................... 260 Function Code 01: Read Holding Coils ........................................................................................................ 260 Function Code 02: Read Input Coils ............................................................................................................. 261 Function Code 03: Read Holding Registers .................................................................................................. 262 Function Code 04: Read Input Registers....................................................................................................... 263 Function Code 05: Force Single Holding Coil .............................................................................................. 264 Function Code 06: Preset Single Holding Register....................................................................................... 264 Function Code 07: Read Exception Status ................................................................................................... .265 Function Code 08: Diagnostic....................................................................................................................... 266 Function Code 0F: Force Multiple Holding Coils......................................................................................... 268 Function Code 10: Preset Multiple Holding Registers.................................................................................. 268 Modbus Master Diagnostics.............................................................................................................................. 269 Statistics ........................................................................................................................................................ 270
Chapter 8 Time Sync................................................................................................................................271 Time Synchronization ........................................................................................................................................... 271 Time Synchronization Features......................................................................................................................... 271 Supported GTSs that use periodic pulses:..................................................................................................... 272 General Architecture ......................................................................................................................................... 273 Backup Synchronization ................................................................................................................................... 274 Documentation Organization ........................................................................................................................... 274 Overview....................................................................................................................................................... 274 Basic Theory of Turbine Control Time Synchronization.............................................................................. 274 Hardware Setup............................................................................................................................................. 274 Software Setup and Configuration ................................................................................................................ 274 General Timesync Operations....................................................................................................................... 274 Diagnostics and Troubleshooting.................................................................................................................. 274 Sample Timesync Configurations ................................................................................................................. 274 Appendix A - IRIG Nomenclature ................................................................................................................ 275 Glossary ........................................................................................................................................................ 275 Related Documents ....................................................................................................................................... 275 Time Synchronization Theory....................................................................................................................... 275 Timesync Protocol ........................................................................................................................................ 275 GPS Interface ................................................................................................................................................ 277 Hardware Setup..................................................................................................................................................... 278 Testing the Time and Frequency Board ............................................................................................................ 278 Board Installation .......................................................................................................................................... 278 Setting Base I/O Address .............................................................................................................................. 279 Setting the IRQ.............................................................................................................................................. 279 Connecting the GTS to bc627AT.................................................................................................................. 280 Time Processing Board TPRO_PC ................................................................................................................... 280 Board Installation .......................................................................................................................................... 281 Setting Base I/O Address .............................................................................................................................. 281 Event Input.................................................................................................................................................... 281 Setting the IRQ.............................................................................................................................................. 281 Connecting the GTS to the Board ................................................................................................................. 282 Connecting the Operator Interface ................................................................................................................ 282 Software Setup ...................................................................................................................................................... 283 Timesync Data File ........................................................................................................................................... 283 File Configuration ......................................................................................................................................... 283
GEH-6126
ix
TCI Control Panel Applet ............................................................................................................................. 287 Timesync Operation ...................................................................................................................................... 287 General Operations........................................................................................................................................ 287 Using the TIMEUTIL Program..................................................................................................................... 288 Turning Off the TIMESYNC Function ......................................................................................................... 288 Restoring the TIMESYNC Function ............................................................................................................. 288 Loading MAJOR TIME into the Time Processing Board ............................................................................. 289 Diagnostics and Troubleshooting.......................................................................................................................... 289 Obtaining General Information About the Turbine Control Timesync Function .............................................. 289 Other Timesync Diagnostic Capabilities........................................................................................................... 291 Sample Timesync Configurations ..................................................................................................................... 294 Examples ....................................................................................................................................................... 294 Testing the bc620AT/bc627AT Time and Frequency Board ............................................................................ 299 Test #1........................................................................................................................................................... 300 Test #2........................................................................................................................................................... 301 Test #3........................................................................................................................................................... 303 Test #4 and Test #5 ....................................................................................................................................... 304 Glossary of Terms ..................................................................................................................................................... 307 Appendix A ............................................................................................................................................................... 311
x
GEH-6126
Conventions
The following conventional terms, text formats, and symbols are used throughout this documentation for he described applications. Convention
Meaning
Bold
Indicates that the word is being defined.
Arial Bold Indicates the actual command or operation that is chosen from a menu or dialog box. The command can also be a key to press. 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. Italics also emphasis new terms, margin notes, and the titles of figures, chapters, and other books in the toolbox package. UPPERCASE Indicates a directory, filename, or block name. Lowercase letters can be used when typing names in a dialog box or at the command prompt, unless otherwise indicated for a specific application or utility. Monospace Represents examples of screen text or words and characters that are typed in a text box or at the command prompt.
! Warning
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 persons should modify any programmable machine.
GEH-6126
xi
xii
GEH-6126
Chapter 1 Overview
Introduction This manual provides information on the use and maintenance of the Human Machine Interface, referred to here as HMI, for application to Mark V and Mark V LM SPEEDTRONIC™ Turbine Controls: •
Software tools
•
Data gathering tools
•
Software structure
•
Storage
•
Installation
The HMI can be used to monitor a single turbine or several turbines. The operator can thereby select the units he wishes to monitor or issue commands to. All HMIs are capable of issuing commands to a unit at any time while communicating with Mark V control panels. For the purposes of this manual, it is assumed the HMI is controlling a single turbine and driven device. Commands - may be issued to the turbine and driven device. Examples consist of START, STOP, COOLDOWN ON, AUTO, and RAISE SPEED/LOAD). Displays - may be accessed to view the status of the turbine and driven device. Examples are ALARMS, WHEELSPACE TEMPERATURES, and VIBRATION FEEDBACK (see figure on next page).
GEH-6126
Chapter 1 Overview • 1
Sample Display
The associated printer(s) enables the operator to manually select and copy any display, to automatically log selected parameters, and to log alarms.
2 • Chapter 1 Overview
GEH-6126
CIMPLICITY SERVER
HMI SCREEN(s) HMI VIEWER Windows NT
HMI VIEWER Windows NT
#2
Point Data Base
#1
Ethernet
Turbine Control Interface Mark V Device Communication
Data Dictionary
Stage Link
I/O
MARK V PANEL
TURBINE
Pictorial Overview of Components
A standard HMI consists of the following: IBM®-compatible PC with color monitor (rack mounted or freestanding "desk top" model), a keyboard, and a central processing unit (CPU). The CPU contains: • • • • • •
ARCNET® interface card ETHERNET ™Card 2 RS-232 serial ports 1 parallel port (LPT1) Cursor Positioning Device (CPD) such as a trackball or a mouse Dot Matrix Printer
Options may include: • • • • •
GEH-6126
serial port expander card additional dot matrix printer(s), laser printer(s) and/or color printer(s) long distance data set(s) (LDDs) modem(s) computer "operator station" such as a PC® desk
Chapter 1 Overview • 3
The Mark V Stage Link (see GEH-6195 for Mark V, GEH-6353 for Mark V LM) is the communication link between a turbine control panel and the HMI. The configuration section of this manual includes a section on Stage Link. Communication with a DCS can also be accomplished using MODBUS protocol over a serial communication link through LDDSs or modems. Alarm and event logging is accomplished using a dot matrix printer. Optionally, additional dot matrix printer(s), laser printer(s), and/or color printer(s) may be supplied. Alarm Logging, though with a lower time resolution, to disk storage is available through CIMPLICITY™ Logging. Note The auxiliary components of an HMI such as the printer(s) and LDDS(s) may not be the same for all HMIs on a particular site.
Related Documents SPEEDTRONIC Mark V Turbine Control User’s Manual – GEH-5979 The user’s manual provides information needed by a turbine operator to understand both the primary and back-up Mark V operator interfaces. Topics in the manual include: • Main Menu and Display
• Trip Log Display
• PASSWORD Administration
• EPA Display
• Synonyms
• Back-up Operator Interface Operation
• Alarm Management
• Printer Functions
• User-Defined Displays
• Multi-Unit Operator Interfaces
SPEEDTRONIC Mark V Turbine Control Maintenance Manual – GEH-5980 The maintenance manual provides information needed by control system maintenance personnel for installation, calibration, and troubleshooting the Mark V control system. Topics in the manual include: • Control System Installation
• LCC Operation
• Control Constant Adjustment
• Terminal Interface Monitor Operation
• Dynamic Rung Display
• DIAGC Display Operation
• Logic Forcing
• VIEW Tools
• Pre-voted Data Display
4 • Chapter 1 Overview
GEH-6126
SPEEDTRONIC Mark V Turbine Control Application Manual Overview – GEH-6195. The application manual is an engineer’s reference for the Mark V control system. Topics in the manual include: • Introduction To Mark V controls
• Stage Link Application Rules
• Specifications & I/O Capacities
• MODBUS Configuration Instructions
• The Screen Builder
• The I/O Configurator
• The Control Sequence Editor
• Signal Flow Diagrams
• I/O Application Examples
• Hardware Jumper Application Notes
• Regulator Descriptions & Diagrams
• Big Block Reference
SPEEDTRONIC Turbine Control Panel Manual Overview – GEH-6354. The application manual is an engineer’s reference for the Mark V LM control system. It provides information needed by control system maintenance personnel for installation, calibration, and troubleshooting the Mark V LM control system. Topics in the manual include: • • • • •
Unit Configuration Specifications & I/O Capacities The I/O Configurator I/O Application Examples Stage Link Configuration
CIMPLICITY Base System User's Manual – GFK-1180 The application manual is an engineer’s reference for the CIMPLICITY Base System.
Getting Assistance If assistance is needed, please contact: GE Industrial Systems Product Service Engineering, Rm. 191 1501 Roanoke Blvd. Salem, VA 24153-6492 USA Phone + 1 540 387 7595 Fax + 1 540 387 8606
GEH-6126
Chapter 1 Overview • 5
Notes
6 • Chapter 1 Overview
GEH-6126
Chapter 2 Start Up
Logging On After powering on the HMI and waiting until a “window” box appears for logon instruction log on to the Windows NT® operating system, press Ctrl-Alt-Delete. A log on window will then appear where you can enter your User ID and password. If you do not have a User ID and password, contact your system administrator to obtain a User ID and password. Along the bottom of the log on window are four buttons. Click on the OK button after entering your User ID and password to complete the log on. Click on the Cancel button to abort the log on. Click on the Help button for information on how to log on. Click on the Shut Down button to halt the system prior to powering down the computer.
Main Cimview A typical HMI system will have a Desktop shortcut to the main CimView display screen. Double click on the Desktop shortcut to activate the display screen. Some systems may have a shortcut on the Start menu instead of or in addition to the Desktop shortcut. You can also create shortcuts to other frequently used display screens. To create a new shortcut, right click on the Desktop and choose New/Shortcut from the pop-up menu. For more information about CimView, consult the CIMPLICITY Base System User’s Manual, GFK-1180
GEH-6126
Chapter 2 Start Up • 7
Alarm Displays A typical HMI system will have one or more alarm displays configured. Some systems may have a Desktop or Start menu shortcut for each alarm display. Most of the CimView display screens will have a transfer button that will call up an alarm display. The alarm display contains a scrollable viewing area and one or more rows of buttons along the bottom of the display. The buttons allow you to take action on the alarms displayed in the viewing area. To take an action on an alarm, select the desired alarm in the viewing area and click on the button that corresponds to the desired action (e.g. Acknowledge, Lock). You may notice that other displays contain an abbreviated alarm display in the lower portion of the screen. Typically the last few alarms are displayed and there are no action buttons. You will need to transfer to the alarm display to take action on alarms. The alarm display has two modes of operation: •
Dynamic mode - all alarms might NOT be displayed. If there are more alarms than will fit in the viewing area then only the most recent alarms will be displayed until the viewing area is filled. The display updates in real time as the alarm information changes.
•
Static mode - the display will NOT continually update. To update the display, click on the Refresh button. All alarms are displayed. If there are more alarms than will fit in the viewing area, a scroll bar will appear on the right edge on the window. This mode is used if the alarm incoming rate makes it difficult to select an individual alarm.
Commands Each CimView display screen contains one or more action objects that will invoke commands. When the mouse pointer is over an action object, a rectangle will appear highlighting the action object. By clicking the left mouse button or pressing the enter key, you can invoke the configured command(s).
Style Recommendations GE recommends that push buttons on CimView displays follow a consistent style of appearance and interaction with the user. Any push button that sends a command or analog setpoint to the turbine control should adhere to this style. Consistent color coding of pushbuttons to indicate their function will help prevent operator errors. A suggested scheme for operator pushbuttons is: • • •
8 • Chapter 2 Start Up
Green - command pushbutton with confirmation Red - command pushbutton without confirmation Gray - analog setpoint
GEH-6126
Advanced Topics Trending You can use CIMPLICITY HMI Trending to embed trend charts in CimView and CimEdit screens. The charts can display line trends from CIMPLICITY HMI Database Logger group tables, current data, CSV files and reference files. Trending gives you the ability to:
•
Display trends with multiple Y-axes so that different parameter types can be displayed in the same chart.
•
Display trends with data from different time periods so those different production periods can be compared in the same chart.
•
Display trends with different time duration so those production periods of differing length can be compared in the same chart.
•
Display trends with auto update enabled so that the most recently logged data is automatically retrieved from disk while the trend is displayed.
•
Display lines containing run-time data as reported by CIMPLICITY HMI Point Management.
•
Display a line containing both logged and real-time data.
•
Zoom and pan through logged data to locate data of particular interest.
•
Compare relative values with a movable cursor that updates a legend with actual values.
•
Display long time periods in compressed format where the plotted data is the average, minimum, maximum, first, or last element from a sample.
•
Create a reference trend from a trend display that can be recalled and displayed. The reference trend can be displayed and compared with other comparable data.
For more information about trending (CIMPLICITY Trending Operation Manual, GFK-1260).
Point Control Panel This feature lets you: •
View the current point values for points in any project in your enterprise.
•
Perform setpoints on points you are displaying.
•
Enable/disable alarms for points you are displaying.
•
Change the alarm limits for points you are displaying.
•
Save a Point Control Panel document and redisplay it at a later time.
When you select Add from the Edit menu or press Ctrl+A, the Select a Point browser opens.
GEH-6126
Chapter 2 Start Up • 9
Select the project from which you want to display points. To request a list of all points, just select Browse. To refine the list, you can enter search strings for Point ID, Device ID, Resource, Point Type or Description, then select Browse. When the list of points displays in the list box, select the ones you want to display, then select OK. The Select a Point browser closes and the Point Control Panel redisplays with the points you selected. All the points you requested are automatically selected in the Point Control Panel so that you can just look at them, then delete them from the view if you wish. The current value, units and timestamp for each point are displayed in the Point Control Panel. If a point is in an alarm condition, its text is displayed in the appropriate color. You can display point properties for each point in the list. You can also perform a setpoint, enable/disable alarming and set new alarm limits for each point in the list. For more information about Point Control Panel (CIMPLICITY Base System User’s Manual, GFK-1180).
Demand Display Many applications require monitoring several turbine data points at a time. Some of these applications may also require the issuing of simple commands. This tool is designed for these applications. Demand Displays offer flexible monitoring and control of a variety of points and of multiple units. Features include:
•
Allowing for monitoring point data and issuing commands to the unit(s).
•
Having alterable displays that conform to the users needs.
•
Conforming easily to the displays required for testing and other special procedures.
•
Controlling special unit functions while monitoring.
The Demand Display program contains two types of Display windows: •
Demand Display menu screen - includes a list of all of the screens available in the selected Demand Display file. Selecting one of the Demand Display screens
on the list accesses the screen. Note New Demand Display screens must be added to the menu for access. The Demand Display menu screen must be saved to make the addition permanent.
•
Demand Display screen - displays the Demand Displays.
For more detailed information, refer to the Demand Display description in the Control section of this manual.
10 • Chapter 2 Start Up
GEH-6126
Chapter 3 Theory of Applications
Advanced Data Flow This section describes the HMI components and highlights some of their features. The HMI consists of these components: CIMPLICITY Viewer: •
Allows a machine to view any running project on a network.
CIMPLICITY Server: •
Collects data from different devices.
•
Maintains a database.
•
Capable of logging.
CIMPLICITY-to-Turbine Bridge (CIMB):
GEH-6126
•
Forwards points and alarms to CIMPLICITY.
•
Turbine Control Interface (TCI):
•
Provides real-time device communications to the turbine control.
•
Provides turbine control configuration capabilities.
•
Collects data, alarms and forwards commands to the turbine control.
•
Maintains a data dictionary.
Chapter 3 Theory of Applications • 11
CIMPLICITY SERVER E-net
E-net
Alarms
CIMB
Alarm Mgr
Alrm API
Point Mgr
EXTERNAL Alarm Mgr Interface
Point Data Base
Point Data SRTP EGD DEVCOM
Point Data
MARKV RP
X Library
TCI ALARM SYSTEM
Data Collection and other functions
Data Dictionary
ARCNET Devices GE Fanuc GE Motors & Industrial Systems
Overview of CIMPLICITY Server
Directory Structure
The HMI software is stored in three groups on the hard disk drive; the first is CIMPLICITY, and the other two are TCI specific. CIMPLICITY directories: C:
CIMPLICITY HMI BSM_DATA DATA EXE LOG
For a description of CIMPLICITY directories, refer to CIMPLICITY User’s Manual GFK-1180.
TCI Directories: The TCI groups are product-specific software and site-specific software, and are divided on pseudo or substitute drives. The F: drive contains the site-specific software in various subdirectories. Drive G: contains the software common to all turbine control panels in various subdirectories.
12 • Chapter 3 Theory of Applications
GEH-6126
The hard drive for a typical factory-configured TCI computer is partitioned to be one logical drive, C:. The following shows a directory tree for C: of a typical TCI computer. C: CIMPLICITY TCI DATA EXEC LOG SITE RUNTIME UNIT1 PROM USER
UTILITY
The following shows a directory tree for the pseudo drive F:. F: RUNTIME UNIT1 PROM USER
The following shows a directory tree for the pseudo drive G:. G: DATA EXEC LOG
As shown in the directory trees, drive F: and G: are actually root directories of the C: drive. The pseudo drives are established by TCI when it starts up. Programs running under TCI require the above pseudo drive and directory structure for proper operation of the TCI and the transmission of data to and from the unit control panel(s).
Drive F: Files The top level of the pseudo drive F: contains the following site-specific configuration files: CONFIG.DAT is the master site configuration file. It specifies items such as how many units exist on the site and the unit names and subdirectory names containing all the unit specific information. It also contains network information about what communication links exist out of the TCI and which units can be reached on those links.
GEH-6126
Chapter 3 Theory of Applications • 13
SYSTEM.DD is the master data dictionary file. It contains pointers to all the unit.dd files that will be used by the demand displays. It will be locked while TCI is running
Drive F: Sub-directories \RUNTIME contains the user defined Display Menu definitions, which are stored in the DEMANDNN.DM2 files. It also contains the last ten trip history files from Mark V units in text format. \USER is the default directory specified during start-up of the TCI. Some programs, such as screen copy programs, create data files in the current default directory. If the current default directory has not changed, the data files output by these programs could be found here. \UNITN is created for each unit being controlled by a TCI, where n is equal to the unit designator number (up to a maximum of eight units/subdirectories). Files, which make up the Data Dictionary for a unit are stored in its unit-specific directory and should always be kept there. This directory contains the files, which configure and program the unit control (Such as UNITDATA.DAT, IOSCALE.DAT, ALARM.DAT, AND CONSTSET.DAT.).
\UNITN\PROM contains control panel processor PROM-related files. Programs such as the I/O Configurator, the CSP Documenter, the Control Sequence Editor, the Control Sequence Compiler, and others use them. The files in this sub-directory must match the BBL and memory location information stored in the processor PROMs for proper configuration and operation of the control panel.
Drive G: Sub-directories Sub-directories on drive G: contain the following information/files: \EXEC contains all the executable files/programs that form the basic TCI and any batch files used during start-up or execution. \DATA contains any data files, which programs require that are not site-specific. It also contains any generic data files, which might be used before any site-specific data files are created. Programs using data files look for and use any files found in site-specific directories on drive F: first. They only use the generic data files if no site-specific files can be found. \LOG contains the output from various programs, which might be important for debugging or troubleshooting purposes. Error log files and normal start-up files are stored here.
14 • Chapter 3 Theory of Applications
GEH-6126
Program Categories
The HMI has three software components: •
CIMPLICITY
•
TCI
•
CIMB
CIMPLICITY is used primarily for displaying various screens that show the state of the turbine, so the operator can monitor the unit(s). Screens typically have a refresh rate of 1 second. CIMPLICITY cannot configure the turbine control. For description of CIMPLICITY’s capabilities refer to CIMPLICITY User’s Manual GFK-1180. TCI is used to display higher speed data (faster than 1-second updates), to configure a turbine unit and to affect the control of a turbine unit. TCI provides three categories of functionality: Displays, Control, and Configuration. TCI also provides two kinds of remote access to turbine data and control. CIMB (CIMPLICITY Bridge) enables CIMPLICITY to collect data and alarms from a turbine unit. CIMB is made of: •
MARKVRP - Collects data from a Turbine using TCI and forwards the
information to the CIMPLICITY Point Manager. •
EXTMGR - Collects alarms and forwards them to the CIMPLICITY Alarm
Manager. •
LOCKOUT - Sends a lockout command to a unit using TCI. It is configured as a button in the CIMPLICITY Alarm Viewer. The syntax is: LOCKOUT:
[(NODENAME)] LOCK: LOCKOUT.EXE 1 %RES %ID %REFID [(NODENAME)]. UNLOCK: LOCKOUT.EXE 0 %RES %ID %REFID [(NODENAME)].
•
SILENCE - Sends a silence command to a unit using TCI. The syntax is: SILENCE %RES [(NODE)].
GEH-6126
Chapter 3 Theory of Applications • 15
Displays TCI provides various programs to look at turbine data. Their primary purpose is to allow real-time monitoring of a turbine unit. Some programs show data that updates every second, and some can display data that is collected as fast as the frame rate. The display program cannot modify points in the unit. Values such as power output, temperatures and speeds may be monitored but not changed.
Control TCI provides several programs that display parameters, which are involved in the control of a turbine. They also allow some modification of these control parameters. For example, constants may be viewed and some logical points, which affect the sequencing of the control system, may be forced.
Configuration TCI provides several important programs that facilitate the setup and configuration of the HMI and unit control. These programs can be used to change configuration and download configuration to the unit control.
Remote Data and Control TCI provides two programs for remote data monitoring and unit control. They can provide a DCS and other remote devices access to turbine control and data.
16 • Chapter 3 Theory of Applications
GEH-6126
Chapter 4 Display Applications Introduction This chapter contains information about programs that display data and configuration information about the unit control, Stagelink, and HMI. These programs are useful in analyzing problems with the control system. None of the programs in this section have the capability to issue control commands. .
ARCWHO Purpose ®
ARCWHO is a Command Line utility program that provides a list of the ARCNET
nodes that are present on the HMI’s ARCNET link. It is useful when trying to track down ARCNET communication problems, and during the initial installation to verify that the unit configuration information is correct.
Background The Mark V family of Turbine Controls communicates with the HMI using an industry standard ARCNET connection. Each device on the ARCNET is given an address that must be unique. This address is used in the F:\CONFIG.DAT file to match units with ARCNET addresses. The ARCWHO utility program uses the ARCNET driver in the HMI to poll for nodes on the ARCNET. All nodes that are present on the ARCNET will be listed, it does not matter what type of node (turbine control, HMI, etc.) it is.
Operation ARCWHO is normally run from a DOS window. There are no command line parameters. The ARCNET addresses shown are always presented in HEX, which is how they are specified in the F:\CONFIG.DAT file (see example on next page).
GEH-6126
Chapter 4 Display Applications • 17
G:\EXEC>ARCWHO Your Arcnet address is: 1E LUNS FOUND: FE FC 1F G:\EXEC>
This example shows the results of running ARCWHO on an HMI. In this example, the HMI was assigned the ARCNET address 1E, which is typical for the second HMI. There are three ARCNET nodes visible, at addresses FE, FC, and 1F. This would be typical of a site with two Mark V controllers (addresses FE and FC) and one other HMI (1F).
CARD_ID Purpose CARD_ID is a Command Line utility program that will scan a Mark V or Mark V LM turbine control panel and report on the versions of the PROMS that are found. It is useful in cases where you need to know the version of the panel’s PROMs, such as during upgrades, field replacements, or advanced troubleshooting. Note The term firmware is software changed by manipulated hardware. In this case, the firmware is different by changing the PROM on the card.
Background The Mark V and Mark V LM turbine control panels consist of many individual processor cards. Each processor card has a PROM associated with it that contains the firmware that drives the card. Revising the firmware on the card (the PROM revision level) is often required. This determines the available options on the card. This information is often needed during card replacement and during panel upgrades. This information can be read from the sticker on the PROM, but it is sometimes easier to use the CARD_ID utility. There are some differences in the information that is available for the Mark V and the Mark V LM turbine control panels. The Mark V turbine control is polled for each possible PROM, and it responds with the version of the PROM. The version consists of two fields, the card name (such as TCDA) and the version number (such as 1.2). Note Because the Mark V poll is for any possible card, a panel that does not have every possible card will generate a diagnostic alarm when a non-existent card is polled during this process. These diagnostic alarms can be safely ignored.
18 • Chapter 4 Display Applications
GEH-6126
The alarms generated are: • •
DCC DPM: Invalid destination address DCC No queue server for destination
The Mark V front panel messages that correspond to these alarms are: •
QST DPM NO DEST
•
NO QST AVAILABLE
The Mark V LM turbine control uses a slightly different approach due to the flexibility in the card sets that can be configured for the panel. The Mark V LM uses the PANEL.CFG file in the unit configuration directory as a list of cards to poll in the panel. For each card it finds in the PANEL.CFG file, it polls the panel for that card. The card responds with the hardware version, firmware version, and current card state. Comparing what the card returned with what is configured in the PANEL.CFG file will flag any differences. The flag field uses letters to indicate what differences were found using the following letters: H - The hardware version needs to be checked F - The firmware version needs to be checked S - The card state indicates that the card is not ready for operation After the Mark V LM revision report, will print out a list of physical locations for cards of interest. A card is included in this list if there are any flags indicated. A command line parameter (/ALL) can be used to include all cards in this list instead of only the flagged cards.
Operation CARD_ID is normally run from a DOS window. If it is run with no parameters or with a "/?" parameter, it will present a summary of the command line options. CARD_ID requires the name of the unit to check as a command line parameter.
If CARD_ID is being run on a Mark V LM, the following command line options can be used: /ALL - This option will include every card in the summary instead of only the cards that had been flagged. /FULLID - Normally the information returned by the card is a string that is terminated with a null character. Some early cards included information after the null terminator that may be of use during advanced debugging. If this option is used the full field (including the information after the null terminator) is shown.
GEH-6126
Chapter 4 Display Applications • 19
Examples Mark V Example In the next example, a Mark V Simplex panel was queried and the PROM revisions of the cards that were present were reported. F:\UNIT1> CARD_ID T1 Card identification for SALEM PLANT unit T1:
System is type ’B’
C-TCCA:(TCCA
4.2
)
C-TCCB:(TCCB
4.1
)
C-320B:(TCCB
C-SLCC:(LCCB
4.4
)
C-SDCC:(DCCB
6.6
)
C-TCDA:(
C-IOMA:(IOMA
4.5
)
R-TCXX:(TCQA
2.5
)
R-TCXX:(TCQB
1.4
)
R-SLCC:(LCCQ
4.4
)
R-SDCC:(DCCQ
6.6
)
R-IOMA:(IOMA
4.5
)
R-TCPA:(
)
R-TCD1:(TCD1
3.5
)
R-TCD2:(
)
R-TCE1:(TCE1
5.2
)
R-TCE2:(TCE2
5.2
)
R-320B:(TCQB
4.1
)
1.1
R-320P:(
R-TCE3:(TCE3
)
)
)
5.2
)
No response from No response from Enter any key to exit program: F:\UNIT1>
20 • Chapter 4 Display Applications
GEH-6126
Mark V LM Example In the next example, a Mark V LM was queried and the PROM revisions of the cards that were present were reported. Notice that a card that does not support the CARD_ID message type (R:25 processor 1) will not show up in the list of Items of Interest. Cards that respond but are unable to determine their own revisions (R:25 processor 0) do appear in the Items of Interest.
F:\UNIT2> CARD_ID T2
SYSTEM IS MARK V LM BMS ----R:13 R:25 R:25 R1:01 R1:02 R1:02 R1:04 R1:12 R1:13 R1:13 R1:15 R1:16 R1:17 R2:01 R2:12 R2:13 R2:13 R3:01 R3:12 R3:13 R3:13 R5:01 R5:02 R5:02 R5:04 R5:12 R5:13 R5:13
|----------EXPECTED-----------|------------ACTUAL------------|PR HARDWARE FIRMWARE |PR HARDWARE FIRMWARE ST |-- ------------ ------------ |-- ------------ ------------ -| 0 UCIAG2AC* UCIAP1AAC | | 0 UCPBG7AF* DS206TMCAED | 0 DS206TMCAED A7 | 1 UCPBG7AF* DS206TMQAEF | | 0 TCQAG1BF* TCQAP1BBB | 0 TCQAG**** TCQAP1BBB A7 | 0 TCQEG1AE* TCQEP1ABB | 0 TCQEG**** TCQEP1ABB A7 | 1 TCQEG1AE* TCQEP2AAB | 1 TCQEG**** TCQEP2AAB A7 | 0 TCDAG1BF* TCDAP1BCG | 0 TCDAG1BG* TCDAP1BCG-1 A7 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7 | 0 TCEAG1BA* TCEAP1BBC | 0 TCEAG**** TCEAP1BBC A7 | 0 TCEAG1BA* TCEAP1BBC | 0 TCEAG**** TCEAP1BBC A7 | 0 TCEAG1BA* TCEAP1BBC | 0 TCEAG**** TCEAP1BBB-1 A7 | 0 TCQAG1BF* TCQAP1BBB | 0 TCQAG**** TCQAP1BBC A7 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7 | 0 TCQAG1BF* TCQAP1BBB | 0 TCQAG**** TCQAP1BBB A7 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7 | 0 TCCAG1BA* TCCAP1BAD | 0 TCCAG**** TCCAP1BAD A7 | 0 TCCBG1BE* TCCBP1BAC | 0 TCCBG**** TCCBP1BAC A7 | 1 TCCBG1BE* TCCBP2BAB | 1 TCCBG**** TCCBP2BAB A7 | 0 TCDAG1BF* TCDAP1BCG | 0 TCDAG1BG* TCDAP1BCG A7 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7
--HFS --H
HF
F F
H
----- |-- ------------ ------------| --- -------- ---- ---------- LIST OF ITEMS OF INTEREST ----BMS ----R:25 R1:04 R1:17 R2:01 R5:04
GEH-6126
|PR |-| 0 | 0 | 0 | 0 | 0
HARDWARE -----------UCPBG7AF* TCDAG1BA* TCEAG1BA* TCQAG1BF* TCDAG1BF*
FIRMWARE | ------------| DS206TMCAED | TCDAP1BCG | TCEAP1BAD | TCQAP1BBB | TCDAP1BCG |
HFS --H HF F F H
PHYSICAL SLOT (DHTR) -------- ---- -----R 1 ( 1H1) Q11 1 ( ) P1 3 ( ) R2 2 ( ) R51 1 ( )
Chapter 4 Display Applications • 21
CHECKCRC Purpose CHECKCRC is a Command Line utility program that checks the files distributed by
the TCI Product Code to make sure that all the files exist on the PC, and that they have not been corrupted or infected with any computer viruses. It is useful when debugging software problems to verify that all required Product Code files are in place and intact.
Background The TCI Product Code consists of many computer files spread out over multiple directories. When debugging software problems it is helpful to know that all the required files exist and have not been corrupted in any way. When the TCI Product Code distribution is made, one of the last steps is to create a TCI.CRC file that contains the Cyclic Redundancy Code (CRC) of all files distributed by that product. This file is used by CHECKCRC as the list of files that must exist and the CRC of each file. There is one TCI.CRC file in each directory that TCI populates. This scheme allows multiple Product Code distributions to populate the same directory - each one will have a separate *.CRC file associated with its distribution. CHECKCRC is currently implemented as a batch file that checks ALL of the *.CRC
files that it finds in the product distribution directories. This means that running CHECKCRC will check all products that support this type of CRC file checking.
22 • Chapter 4 Display Applications
GEH-6126
Operation CHECKCRC is normally run from a DOS window. There are no command line parameters. CHECKCRC does use the pseudo drive G: so this needs to be defined.
This is typically done by starting the TCI System Service. If the TCI System Service is running, then the G: drive will be defined and will be able to find the Product Code files that need to be checked. CHECKCRC will report problems by reporting files as:
MISSING - This means the file was listed in the *.CRC file, but was not found in the directory. MISMATCH - This means the file listed in the *.CRC file was found on the disk, but the CRC of the file on the disk did not match the CRC in the *.CRC file. This means that the file on the disk is not the same file that was distributed as part of the Product Code.
Example The next example shows that CHECKCRC found two problems. The first is that the ALMRCV.EXE file in the G:\EXEC directory is not the version that was distributed with the TCI Product Code. (The fact that it is checking the TCI.CRC file means that the file is distributed as part of the TCI Product Code.) The second problem was a missing file; the TABLE_C.EXE file appears to have been removed from the G:\EXEC directory. G:\EXEC>CHECKCRC CHECKING "G:\EXEC\TCI.CRC" FILES IN "G:\EXEC\". G:\EXEC\ALMRCV.EXE, MISMATCH G:\EXEC\TABLE_C.EXE, MISSING CHECKING "G:\DATA\TCI.CRC" FILES IN "G:\DATA\". ...ALL FILES MATCHED. CHECKING "C:\WINNT\SYSTEM32\TCI.CRC" FILES IN "C:\WINNT\SYSTEM32\". ...ALL FILES MATCHED. CHECKING "C:\INETPUB\SCRIPTS\GEDS\TCI.CRC" FILES IN "C:\INETPUB\SCRIPTS\GEDS\". ...ALL FILES MATCHED. CHECKING "C:\INETPUB\WWWROOT\GEDS\TCI.CRC" FILES IN "C:\INETPUB\WWWROOT\GEDS\". ...ALL FILES MATCHED.
G:\EXEC>
GEH-6126
Chapter 4 Display Applications • 23
Diagnostic Counters Display Purpose The Diagnostic Counters Display (DIAGC) provides information on internal control and I/O card functions used for troubleshooting and/or statistical data gathering purposes. This display permits I/O card data not defined in the unit Control Signal Database (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 cards for troubleshooting purposes. This information is intended for debugging by experienced field and factory personnel. No unit control functions are available on this display. Note This program is NOT intended for use by plant operators! 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 treeview causes that sub-type Diagnostic Counter data to be displayed. That data will be 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 may be located in the F:\UNITN directory or in the F:\UNITN\PROM directory.
Mark V LM The DIAGC.DAT file is a text file that is produced by the tool program G:\EXEC\DCBUILD1.EXE. 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.
Mark V The DIAGC.DAT file is completed by the Requisition Engineer. This file should NOT be edited except by qualified field personnel as part of hardware and/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 may then be opened and viewed with notepad or other text-viewing program. DIAGC cannot be used to open the text file.
24 • Chapter 4 Display Applications
GEH-6126
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 Data
Executing Diagnostic Counters Display (DIAGC) The Diagnostic Counters Display, DIAGC, may be executed from a menu pick on the Main Menu or from the DOS prompt using the command: DIAGC. DIAGC.EXE is located within the product code in the G:\EXEC subdirectory. The Diagnostic Counters Display may be launched from the command line with the following argument to quickly bring the display to a desired configuration: /UNIT:
The following example specifies the unit name as T1: G:\EXEC\DIAGC.EXE /UNIT: T1
The DIAGC Display may be launched from the Windows Start Menu Run dialog box by entering the command as shown on the command line above, or by selecting the DIAGC icon from the appropriate program group.
DIAGC - Tree View and Splitter Bar
GEH-6126
Chapter 4 Display Applications • 25
The Diagnostic Counters Display Window The Diagnostic Counters Display features two portions: • •
Tree View Diagnostic Counter data
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.
Tree View The Diagnostic Counters tree view window is a graphical window that attempts to depict 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. Navigation in the tree-view is accomplished with the keyboard or mouse. The panel/core/card levels may 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 will be displayed in the data area until the user selects a different sub-type or changes the unit selection.
26 • Chapter 4 Display Applications
GEH-6126
Diagnostic Counter Data Window and Splitter Bar
Diagnostic Counter Data Window The Diagnostic Counter Data Window has three main regions: • • •
GEH-6126
Header Legend Data Area
Chapter 4 Display Applications • 27
Header contains: • • • • • • • •
Unit Name Site Name Program Name Card Core Socket Name Timetag Number of replies received from the unit
The Header is a non-scrolling region and therefore cannot be scrolled out of the window. Although this region may 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 card being examined. The legend contains the subtype currently being viewed. Timetag The Header timetag 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 timetag will be highlighted. Replies Received 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.
Legend 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 may be turned off using the View menu, it is recommended that users leave the Legend visible at all times.
Data Area 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 timetag 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 may 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.
28 • Chapter 4 Display Applications
GEH-6126
Selecting a Diagnostic Counters Display Selecting a particular display establishes a communication link to the card 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 may be expanded into its component cards and each card expanded into its diagnostics displays. Use the cursor and keyboard to expand the desired core and card, then select the appropriate diagnostic display for the card. 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 Card Designers The following data types are supported for the Diagnostic Counters Display. Card designers should refrain from using data types other than those listed here because they are NOT supported. 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
Data Types for Diagnostics Counter Display Type Hn converts signed to unsigned. Type Sn converts unsigned to signed.
GEH-6126
Chapter 4 Display Applications • 29
Dynamic Rung Display Purpose The Dynamic Rung Display is a tool for stepping through the control programming of a Mark V. It shows the control rungs and blocks in a control sequence segment for a given unit. The rungs are "animated" to show the current state of the control. Rung Ladder Display (RLD) rungs are shown with green representing continuity in contacts and the energized state in a coil. The Primitive and Big Block rungs may have their associated picture files displayed with either signal names or actual point values. A Demand Display with all of the signal names and values from a rung may be displayed. A Find utility is included to show the locations and usage of all occurrences of a signal in the unit’s Control Sequence Program (CSP). The Dynamic Rung Display may have more than one control segment from a given unit open at a time. Only segments from a single unit may be displayed at any time. The unit's Control Sequence Program cannot be altered using this program. The Turbine Control Interface must be running in order to use the Dynamic Rung Display.
File Structure Files Used by the Dynamic Rung Display: MSTR_SEQ.CFG
Lists the sequencing source files (*.SRC) used in the control
*.SRC
The source files for the individual control sequence segments
\PROM\BIGBLOCK.DEF
The big block definition file for the unit
\PROM\PRIMITIVE.DEF
The primitive definition file for the unit
\PROM\*.PIC
The picture files for the big blocks and primitives
\PROM\*.SPC
Sequencing BBL source files
The files are used by the Dynamic Rung Display to coordinate and accurately display the unit control data. These files are also used for unit control configuration and cannot be altered by the Dynamic Rung Display. It is imperative that the configuration and sequencing files in the unit control and in the operator interface match. The Dynamic Rung display program does NOT independently verify that the operator interface files match the unit control files. If these files do not match, the Dynamic Rung Display may display data that does not reflect the state of the unit control.
30 • Chapter 4 Display Applications
GEH-6126
The Dynamic Rung Display has the capability to save picture file displays in a text format for future reference. These text files may be opened by any editor or word processing application. It also creates temporary Demand Display (*.DM2) files in the system temporary directory when the Demand Display is used to show the points and values from a given rung. These files are automatically deleted when the Demand Display closes.
Dynamic Rung Display Screen Description The Dynamic Rung Display is a multiple document interface, which allows the user to open windows with different segments or the same segment. The user may also have picture file view windows and sub rung view windows open. The windows are sized to display a full view of a rung; however, the window may be resized and repositioned. There are three major types of windows: • • •
GEH-6126
Rung Windows Picture File Window Main Frame Window
Chapter 4 Display Applications • 31
Rung Windows Rung Windows are used to display the animation of the control sequencing and to navigate through the control sequencing segments. Rung Windows may display data from main sequencing rungs or sub rungs that are predefined into Big Blocks.
The Dynamic Rung Display Window
The title bar of the segment window will display: • •
Unit Name Segment Name
Each Rung Window will display Header information in its upper left corner.
32 • Chapter 4 Display Applications
GEH-6126
Rung Window Header Header contains: • • • • • •
Unit Name Site Name Program Name Segment Name Rung Number Timetag
Although this region may be scrolled off the screen or hidden by other windows, it is recommended that users leave the Header visible at all times because the Header contains valuable process information.
Header Timetag Big Blocks and Comment Rungs The Header timetag displays the operator interface time of when the rung was displayed.
RLD and Primitive Rungs The Header timetag displays the timetag of the oldest piece of data being displayed in the RLD portions of the rung. If no data has been received from the unit, then the timetag text will be No Valid Data. If the oldest piece of data in the rung has not been updated for at least five seconds, the Header timetag will be highlighted.
Data Display • • • •
Relay-ladder Logic Diagrams (RLDs) Primitives Big Blocks Comment Rungs
RLD Rungs In an RLD Rung display, the Header information is displayed in the upper left corner. The Header timetag displays the timetag of the oldest piece of data on this rung. The animation of the rungs occurs once per second. The rules for animating contacts and coils are as follows:
Contacts Normally Open Contacts
GEH-6126
1.
Indicate continuity with a green rectangle between the contacts.
2.
Indicate an open circuit with no rectangle between the contacts.
3.
Forced signals shall have a ">" symbol between the contacts.
4.
Contacts that are forced to the open condition will have a rectangle outline around the ">" symbol to highlight the condition.
Chapter 4 Display Applications • 33
Normally Closed Contacts 1.
Normally closed contacts are indicated by a slash drawn through the contact.
2.
Indicate continuity with a green rectangle between the contacts.
3.
Indicate an open circuit with no rectangle between the contacts.
4.
Contacts that are forced to the open condition will have a rectangle outline around the ">" symbol to highlight the condition. The slash through the contacts is broken in the middle to highlight the ">" symbol.
Coils Normal Coils 1.
Indicate that having the coil circle filled in green energizes them.
2.
Indicate that they are de-energized by having the coil circle filled in with the window background color.
3.
Forced signals shall have a ">" symbol in the coil circle.
Inverted Coils 1.
Inverted coils are shown with a slash through the coil.
2.
Indicate that having the coil circle filled in green energizes them.
3.
Indicate that they are de-energized by having the coil circle filled in with the window background color.
4.
Forced signals shall have a ">" symbol in the coil circle. The slash through the contacts is broken in the middle to highlight the ">" symbol.
Primitive Rungs In a Primitive Rung display, the Header information is displayed in the upper left corner. The Header timetag displays the timetag of the oldest piece of data from the RLD portions of the rung. The animation of the contacts and coils in the rung occurs once per second. The rules for animating contacts and coils are the same as for RLD rungs. The Primitive Block Rung passed parameter information is not animated in the Rung Window. The user may select the View:Picture File menu selection or View:Demand Display to watch live updates of the Primitive passed parameters.
Big Blocks In a Big Block Rung display, the Header information is displayed in the upper left corner. The Header timetag displays the operator interface time when the rung was displayed and does not update. The Big Block Rung passed parameter information is not animated in the Rung Window. The user may select the View:Picture File menu selection or View:Demand Display to watch live updates of the Big Block passed parameters. Big Block automatic parameters can only be viewed using the View:Demand Display menu selection.
34 • Chapter 4 Display Applications
GEH-6126
Comment Rungs In a Comment Rung display, the Header information is displayed in the upper left corner. The Header timetag displays the operator interface time when the rung was displayed and does not update. There is no animation of a Comment display.
GEH-6126
Chapter 4 Display Applications • 35
Picture File Windows Picture File Windows are used to display the picture file and animation of the passed parameters for Primitive and Big Blocks.
The Dynamic Rung Display Picture File Window
The title bar or the Picture File Window displays: • • • •
Unit Name Segment Name Rung Number Picture File Name
Header information is displayed in the upper left corner.
Picture File Window Header The Header contains: • • • • • •
Unit Name Site Name Segment Name Rung Number Picture File Name Timetag
Although this region may be scrolled off the screen or hidden by other window, it is recommended that users leave the Header visible at all times because the Header contains valuable process information.
36 • Chapter 4 Display Applications
GEH-6126
Header Timetag Static Display The Header timetag displays the operator interface time of when the rung was displayed.
Values Display The Header timetag displays the timetag of the oldest piece of data being displayed as a passed parameter. This includes the coil output for Primitive Blocks. If no data has been received from the unit, then the timetag text will be No Valid Data. If the oldest piece of data in the view has not been updated for at least five seconds, the Header timetag will be highlighted. Picture Files cannot be opened directly by the File:Open menu selection. Only a regular sequencing segment from the files listed in the MSTR_SEQ.CFG file can be opened with the File:Open menu selection. The user should open a segment, then navigate to the rung that contains the Primitive or Big block of interest. He may then select View:Picture File to open a new window displaying the Picture File. Picture Files are initially displayed as static with the passed parameter point names shown as inputs and outputs to the block. Selecting the View:Values menu selection will cause the parameter point names to be replaced by their current values from the real time database. The data is updated once per second. Selecting View:Values a second time will cause the Picture File display to revert to the static display with the passed parameter point names shown. Big Block automatic parameters are not animated in the Picture File Window. Their values can only be viewed using the View:Demand Display menu selection. Users cannot navigate to other rungs or Picture File Windows from a Picture File Window. A Picture File Window will remain open until it is closed from the File:Close menu command or the unit selection is changed.
Main Frame Window This window is the outer window that contains the rung and picture file windows. If no control sequencing files or picture files are open, this window is empty.
GEH-6126
Chapter 4 Display Applications • 37
Using The Dynamic Rung Display This section provides information concerning the use of the following functions: • • • •
Starting the Dynamic Rung Display Program Selecting A Sequencing Display Screen Using The Find All Function Viewing Tabular Data
Starting the Dynamic Rung Display The Dynamic Rung Display may be launched from the command line with the following arguments to quickly bring the display to a desired configuration: /UNIT: /FILE: /RUNG:
The user may use these command line parameters to customize the startup of the Dynamic Rung Display or enter dynrung.exe in the Run dialog box in the Start Menu, or simply double click on the program icon. The following example specifies the unit name as T1: G:\EXEC\DYNRUNG.EXE /UNIT:T1:
The following example specifies the desired file name: G:\EXEC\DYNRUNG.EXE /UNIT:T1 /FILE:SEQ_40.SRC:
The following example specifies the rung number: G:\EXEC\DYNRUNG.EXE /UNIT:T1 /FILE:SEQ_40.SRC/RUNG:23
Selecting a Sequencing Display screen Only a regular sequencing segment from the files listed in the MSTR_SEQ.CFG file can be opened with the File:Open menu selection. A unit must be selected before any sequencing files can be opened. These files contain the Control Sequence for each control segment. The user may open more than segment at a time, or have multiple views of the same segment. Use the Window menu selection to change between views. To navigate within a segment, use the Rung menu selections and toolbar buttons.
Using the Find All function The Dynamic Rung Display allows users to find the occurrence of a particular signal anywhere within the control sequencing. The Find All Function will locate signal names in RLD rungs, signal names as passed parameters, signal names as automatic parameters, and Primitive and Big Block names. It will not locate signals and block names used in sub rungs. It does not search Comment Rungs. The Find All Function is available only after a valid unit has been selected. From the drop-down menu list, select Edit:Find All. In the Find All Dialog box, enter the desired signal or block name. Press Find. The Find All Results dialog box will show the results of the search in a tabular format.
38 • Chapter 4 Display Applications
GEH-6126
The first column displays the rung number where the rung was found. Double-click the left mouse button on the rung number, or highlight the rung number and click the Goto button to open a segment with the desired rung displayed The second column shows the segment name. The third column shows the rung type. The fourth column shows how the signal is used in the rung. The Find All Results dialog box will remain open until the user selects the Close button or changes units.
Viewing Tabular Data Selecting Demand Display under the View menu starts a Demand Display showing all of the points from the current rung. It includes RLD elements, Big Block and Primitive passed parameters, and Big Block automatic parameters. Many users find this to be useful when studying the behavior of a BBL with automatic parameters. The Demand Display is a separate program outside of the Dynamic Rung Display.
GEH-6126
Chapter 4 Display Applications • 39
Prevote Data Display Purpose 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. 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 will be displayed in the list. The points are ordered in the list according to their assigned offsets. A dash will be displayed in the column heading on each side of the processor name (example: -R-) if the data from that processor is no longer valid.
Menu Structure File Print - Send what is on the display to a printer. Print Setup - Select and setup the desired printer. Exit - Exit the Prevote display.
Edit Select Unit - Selects the unit the Prevote Display will communicate with. 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.
View 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 will not be updated until the data is unfrozen.
Help About Prevote … - Dialog box that shows the revision level of the Prevote Data Display.
40 • Chapter 4 Display Applications
GEH-6126
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 will be started 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 will be prompted to select a unit. Example: G:\EXEC\PVOTE /UNIT:T1
Header Timetag The Header Timetag displays the timetag of the oldest piece of data being displayed in the data list. Before data has been received, the timetag will be No Valid Data. If the oldest piece of data on the screen is more than five seconds old, the timetag will be highlighted.
Prevote Data Display
Trip History Log Purpose The function of the Trip History Program is to assist in the evaluation of turbine trip events. This is accomplished by providing a chronological record of relevant data gathered by the unit control. The data is organized according to post-trip, pretrip, and alarm categories.
GEH-6126
Chapter 4 Display Applications • 41
The Trip History Program allows the user to retrieve data from the unit control and view it on the operator interface. To view the data, the user must select a valid unit and choose the type of historical data to be collected. When the data retrieval completes successfully, the results are displayed in a separate viewer window. Control Signal Database Points (CSDBs) can be defined for collection. These definitions (64 max.) are made in a single file (HIST_B.SRC). All data in the display is chronologically indexed according to Mark V Control Panel time and a separate panel counter (HIS_AGE).
File Type Viewing The Trip History Program stores the results of the data retrieval in a read-only temporary text file. This file will be displayed using Notepad and then may be saved to another permanent file by using the File:Save As menu option in Notepad.
Configuration The Trip History file for the unit resides in the unit configuration directory and is named HIST_B.SRC. It contains the points for collection and retrieval by the Trip History Program. Information logged in the alarm section of the display is not userdefinable. Any text editor may modify the file. For pre-trip and post-trip screens, timetag (TIME) definitions are listed for the displayed Control Data Point information. These designations provide a chronological index that ties the exhibited signal information to the unit control time. This register can provide valuable information in terms of determining the sequence of events that lead to a turbine trip. If the panel time is reset during an event, however, this index will be lost. To prevent such an occurrence, the Trip Log Display is equipped with a second counter that, though internal to the unit control, runs independently of the panel clock. Updated once-per-second, this counter (HIS_AGE), advances until a maximum value is reached. At that point, the counter returns to zero and restarts. Please note in the sample HIST_B.SRC file (shown below) that this counter increments only when the turbine is in a run condition. HIS_AGE should always be the first point in the HIST_B.SRC file.
42 • Chapter 4 Display Applications
GEH-6126
;-----------------------------------------;
HIST_B.SRC
; HIS_AGE MUST BE THE FIRST POINT! ; ; Signal Name ; ----------HIS_AGE DWATT TNH FSR L52GX L14HR L14HM L14HA L14HS L94X L4 L3 L2TV L28FDX TTXD_1 TTXD_2 TTXD_3 TTXD_4 TTXD_5 TTXD_6 TTXD_7 TTXD_8 TTXD_9 TTXD_10 TTXD_11 TTXD_12 TTXD_13 TTXD_14 TTXD_15 TTXD_17 TTXD_18 FQG FQL1 FSG CTIM CSGV CPD TTXSPL TTXSP1 TTXSP2 TTXSP3 L4CT
After any modifications, this file should be processed and downloaded as described in the Configuration section of this manual.
GEH-6126
Chapter 4 Display Applications • 43
Trip History Dialog Box Description
Trip History Dialog Box
The Trip History dialog box controls the collection of Trip History data and Historical log data from the unit control. The user must select a valid unit in the Select Unit list box and choose the type of historical data to be collected from the radio buttons in the Select Log section. Only one type of data may be collected at a time. There are three categories of information that may be collected: •
Trip History
•
Saved Data
•
New Data
Trip History Trip History is saved when the turbine trips. For Mark V LM unit controls, the data is saved in the control even after the control is reset. Note Trip History data will be lost in Mark V units if the unit control is reset.
Saved Data Saved Data is saved into the control memory when the user collects New Data. It remains in memory until it is overwritten by New Data or until the control is reset.
New Data New Data is saved to the control memory when the user collects New Data. The data reflects the most recent control data. The data remains in the control memory as Saved Data until it is overwritten or until the control is reset.
44 • Chapter 4 Display Applications
GEH-6126
Note Collecting New Data will overwrite the Saved Data in the control! On Mark V units, New Data will overwrite the Trip History Data in the control!
Data Retrieval Begin data retrieval by selecting the Collect button in the Trip History dialog box. Selecting the Stop button may halt data retrieval. A message box will display if the data retrieval fails or is stopped by a user command. When the data retrieval completes successfully, the results are displayed in a separate viewer window. Selecting the Close button exits the Trip History dialog box. Any results currently being viewed will remain in their respective windows.
Viewing Results When the data retrieval completes successfully, the results are displayed using Notepad in a separate viewer window. The data is designed to be viewed using a fixed pitch font (All characters have the same width). Any word wrapping features should be disabled. The results shown are stored in a read-only temporary file. To save the information being displayed, the file must be copied to a permanent file location using the File:Save As menu option. The results saved will be in the following format: • • • • • • •
Post Trip List: three 1 second post trip records. These three records are filled with data only when there has been an actual trip. Otherwise, these records will be blank. 10 Second List: ten 1 second records. 1-Minute List: five 10 second records. 10-Minute List: nine 1-minute records. 1-Hour List: five 10-minute records. 4-Hour List: four 1-hour records. Last 60 Process Alarms.
Each record consists of the following fields: • •
Timetag Value of from 1 to 64 points from the Control Signal Database.
Up to 64 points may be viewed. HIS_AGE is always reserved as the first point. Enumerated state variable data are displayed as numbers, not as text strings.
GEH-6126
Chapter 4 Display Applications • 45
The Trip History Data Viewer
Executing the Trip History Program The Trip History Program may be launched from the command line with the following optional argument to quickly bring the display to a desired configuration: The user may use this command line parameter to customize the startup of the program, or enter TRIPDLOG.EXE in the Run dialog box in the Start Menu, or simply double click on the program icon. The following example specifies the unit name (/UNIT:) as T1: G:\EXEC\TRIPDLOG.EXE /UNIT:T1
46 • Chapter 4 Display Applications
GEH-6126
Trip History Log List Viewer Purpose For Mark V control systems, the trip history data stored in the unit control is lost if the unit control is reset or rebooted making the data unavailable for later review and analysis. (The trip history data is preserved in the controller memory over a unit control reset or reboot in Mark V LM units.) In order to preserve this data for Mark V controlled units, a special program is included as part of the TCI system so that the trip history data is automatically collected and stored on the HMI if it is running when the trip occurs. The last ten trips are stored on the HMI. The Mark V Trip Log Viewer program is provided to access this data. To view the data, the user must run the Mark V Trip Log Viewer, then select a valid unit and choose the file from the list presented. The trips are shown by their date and time stamps. The latest trips are listed at the top of the list. After selecting the trip to be viewed, the results are displayed in a separate viewer window.
File Type The Mark V Trip Log List Viewer Program reads the previously saved trip text files stored on the disk to display the valid trip times for selection. This file will be displayed using Notepad and then may be saved to another permanent file by using the File:Save As menu option in Notepad. The files are stored in the F:\RUNTIME directory. The automatic collection program manages the file names where the file name format is TRIP01T1.TXT: • • • •
Where TRIP denotes an automatically collected trip history file. This is followed by a two digit number 00 through 09. The unit name is next. The file has a *.TXT extension.
The last ten trips are stored. After that, the oldest trip log will be overwritten by any new trip data.
GEH-6126
Chapter 4 Display Applications • 47
Mark V Trip Log List Viewer Dialog Box
Mark V Trip Log List Viewer
The Mark V Trip Log List Viewer dialog box controls the selection of Trip History data stored on the disk. The user must select a valid Mark V unit in the Select Unit list box . The list of past trips for that unit will be listed below for selection. The files are shown in the Trip Log Viewer Dialog Box by the trip date and time. Highlighting a selection and using the Go To button will cause that file to be displayed. Selecting the Close button exits the Mark V Trip Log List Viewer dialog box.
Data Retrieval Trip History data retrieval for Mark V controlled units is automatically collected and stored on the HMI disk if the HMI is running and communicating with the control. The last ten trips are stored. After that, the oldest trip log will be overwritten by any new trip data.
Viewing Results Please refer to the Viewing Results section on the Trip History Program for a detailed description of the data format and viewer program.
Executing the Mark V Trip Log List Viewer The Mark V Trip Log List Viewer may be launched from the command line with the following optional argument to quickly bring the display to a desired configuration: The user may use this command line parameter to customize the startup of the program, or enter tripvwr.exe in the Run dialog box in the Start Menu, or simply double click on the program icon. The following example specifies the unit name (/UNIT:) as T1: G:\EXEC\TRIPVWR.EXE /UNIT:T1
48 • Chapter 4 Display Applications
GEH-6126
VIEW2 Purpose VIEW2 is a command line utility that collects high-speed turbine data from a Mark V or Mark V LM controller into a memory buffer. When the buffer fills or the collection is stopped by the user, the data is formatted into ASCII and saved in a disk file. The data contains a unit-defined timetag, and the values for each of the points requested. It is commonly used for conducting high-speed data collection during a specific test, where the duration of the test (or its conclusion) is known.
All points collected must be from the same turbine control. Up to 50 points can be collected. A Mark V controller can support data at up to 32 Hz, a Mark V LM controller can support data at up to 100 Hz.
Background When performing advanced diagnostics, it is often handy to be able to collect data at or even above the frame rate of the controller. It allows for the collection of data as fast as the controller supports it, and saves that data into a disk file for later analysis. All data is time tagged by the unit when the data was sent. Because many of these tests are repetitive in nature, the list of points to be collected can be stored in a Point List file. The name of the Point List file is then passed to the program, preventing having to type in each point name every time the test is run. The point list file is an ASCII file containing a list of point names, one point name per line.
Operation VIEW2 is a command line utility program that is run from a DOS window. If run with no parameters or the "/?" parameter, a help screen is provided.
Note At the current time, the Mark V LM accepts its scan parameter in units of 5mSec intervals, although its internal task schedule rate is at 10mSec. For that reason, non-zero even values for the /SCAN are recommended for Mark V LM units.
GEH-6126
Chapter 4 Display Applications • 49
Examples The following example shows a sample help screen:
F:\UNIT1>VIEW2 /?
VIEW2 - VIEW HIGH SPEED TURBINE DATA THIS PROGRAM WILL COLLECT HIGH SPEED DATA FROM THE TURBINE AND SAVE IT IN A MEMORY DATA BUFFER. WHEN THE BUFFER FILLS (OR A USER SPECIFIED NUMBER OF SAMPLES IS REACHED) THE DATA IS WRITTEN INTO A FILE FOR ANALYSIS. IT CAN COLLECT DATA AS FAST AS THE PROCESSOR CAN SUPPLY IT. UP TO 50 POINTS CAN BE COLLECTED, BUT DO NOT ASK FOR MORE THAN 29 IF YOUR ANALYSIS ROUTINES CAN NOT HANDLE LINES LONGER THAN 256 CHARACTERS.
COMMAND FORMAT:
VIEW2
[OPTIONS] [@POINTLIST_FILE]
OUTPUT_FILE
OPTIONS ARE: /UNIT=
WHERE IS THE UNIT NAME
/PROC=
WHERE IS THE NAME OF THE PROCESSOR (OR CORE)
/SCAN=
WHERE N IS MULTIPLIER OF PROCESSOR SCAN RATE (1=EVERY)
/SAMPLES= WHERE N IS MAXIMUM NUMBER OF SAMPLES DEFAULTS: /UNIT IS REQUIRED AND DOES NOT HAVE A DEFAULT VALUE /PROC DEFAULTS TO "C" FOR A MARK V, AND "R" FOR A MARK V LM /SCAN (1=EVERY SCAN, 2 = EVERY OTHER SCAN...) - MARK V: BASIC SCAN RATE = 1/32 SECOND, DEFAULT IS 1 FOR 32 HZ - MARK V LM: BASIC SCAN RATE = 5 MSEC, DEFAULT IS 8 FOR 25 HZ - .........: SCAN SHOULD BE A NON-ZERO EVEN NUMBER FOR THE MARK V LM /SAMPLES DEFAULTS TO AS MANY AS WILL FIT IN A 1 MB MEMORY BUFFER
F:\UNIT1>
50 • Chapter 4 Display Applications
GEH-6126
In the following example, two points were collected from a Mark V at the default rate. The user hitting a key when the test completed, and 2210 samples had been collected stopped the test. F:\UNIT1>VIEW2 /UNIT=T1 /PROC=R VIEW2.OUT OUTPUT WILL BE WRITTEN TO THE FILE VIEW2.OUT TO READ A POINT LIST FROM A FILE, ENTER @FILENAME AS A PROGRAM PARAMETER. CURRENT UNIT IS: T1 ENTER POINTNAME[1]: FSR ENTER POINTNAME[2]: CPD ENTER POINTNAME[3]: ## UNIT POINTNAME SCALE -- ---- ------------ ----1 T1 FSR % 2 T1 CPD PSI MEMORY FOR DATA SAMPLES: 1048570 BYTES SIZE OF EACH DATA SAMPLE: 10 BYTES MAXIMUM NUMBER OF SAMPLES: 104857 SAMPLES NUMBER OF SAMPLES PER SECOND: 32 SAMPLES/SEC DURATION OF SAMPLES: 3276 SECONDS 2 % - PERCENT OF SAMPLE BUFFER FILLED. << HIT ANY KEY TO STOP. >> 2210 SAMPLES TO BE WRITTEN TO THE OUTPUT FILE. 0 SAMPLES LEFT TO WRITE. THE MAXIMUM PENDING MESSAGE QUEUE DEPTH WAS 2. OUTPUT HAS BEEN WRITTEN TO FILE VIEW2.OUT. F:\UNIT1>
The results can be found in the VIEW2.OUT file. A sample of the output file is also shown below. F:\UNIT1>TYPE VIEW2.OUT ## UNIT POINTNAME SCALE -- ---- ------------ ----1 T1 FSR % 2 T1 CPD PSI 08-DEC 11:23:10.937 16.02 08-DEC 11:23:10.968 16.02 08-DEC 11:23:11.000 16.02 08-DEC 11:23:11.031 16.02 08-DEC 11:23:11.062 16.02 08-DEC 11:23:11.093 16.02 08-DEC 11:23:11.125 16.02 08-DEC 11:23:11.156 16.02 08-DEC 11:23:11.187 16.02 08-DEC 11:23:11.218 16.02 08-DEC 11:23:11.250 16.02 08-DEC 11:23:11.281 16.02 <<< AND SO ON >>>
GEH-6126
101.6 101.6 101.6 101.6 101.6 101.6 101.6 101.6 101.6 101.6 101.6 101.6
Chapter 4 Display Applications • 51
Notes
52 • Chapter 4 Display Applications
GEH-6126
Chapter 5 Control Introduction This chapter contains information about programs that can issue control commands to the unit, or in some way alter the unit control functions. These programs are used to modify the turbine control behavior by issuing basic control commands including setpoints, forcing logic points, and modifying control constants. These operator actions can have a profound affect on turbine control.
!
Only qualified personnel knowledgeable about turbine control and protection should use the program in this chapter..
Caution : .
Logic Forcing Display Purpose The Logic Forcing Display program allows authorized personnel to force any logic data point in the database. Forcing a point changes and/or maintains the logic state, such as “0” or “1”, of a logic data point regardless of the permissives driving the logic data point. During maintenance or troubleshooting it may be necessary to have the Control Panel "believe" that a certain valve is in a particular position (as indicated by a position limit switch on the valve). A simple approach is to use the Logic Forcing capability of the Control Panel.
! Warning
GEH-6126
Only qualified personnel knowledgeable about turbine control and protection should use the Logic Forcing functions. Improper use may adversely affect the control and protective features of the control system.
Chapter 5 Control • 53
The Logic Forcing Display program always shows the currently forced points in the unit. 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 appear to show the existence of more information. 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 unit only.
54 • Chapter 5 Control
GEH-6126
! Caution
A delay occurs prior to forced Logic signals appearing on the Logic Forcing Display screen. When opening a file, wait a few moments prior to taking any action for all of the forced signals to appear.
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 will have its own point list in the data file. It may 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.
The Logic Forcing Display Window
GEH-6126
Chapter 5 Control • 55
Using the Logic Forcing Display Program Creating and editing Logic Forcing Displays require both standard Windows and unique operations. These operations include: •
Loading a Logic Forcing Display file
•
Creating a new Logic Forcing Display file
•
Editing a Logic Forcing Display file
•
Saving Logic Forcing Display files
Performing these operations requires using the drop-down menu options from the menu bar selections. Some of the operations are available on the toolbar. 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
! Caution
Only qualified personnel knowledgeable about turbine control and protection should force logic signals. Improper use may adversely affect the control and protective features of the control system.
To force a logic signal in 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. The pointname highlights. Select one of the forcing Command Targets on the right side of the screen. To arm the action, select the desired command target on the right side of the Logic Forcing Display, either Force To One or Force To Zero. The Execute Command dialog box appears. Selecting OK forces the signal. The force command is sent to the unit causing the forcing of the logic signal at the Control Panel. Signals remain forced until either an Unforce command issues from the Logic Forcing Display program or until the Control Panel powers off. Selecting Cancel from the Execute Command dialog box cancels the forcing command. The default is Cancel.
56 • Chapter 5 Control
GEH-6126
Note This procedure for confirming a forcing action prevents executing false commands.
! Caution
Signals remain forced until an unforce command issues from the Logic Forcing Display program or until the Control Panel powers off. Forced signals may cause the unit to function improperly if forgotten. Take care to unforce all unnecessary signals prior to running the unit.
Returning the logic signals to their normal state is done either by unforcing all of the forced logic signals at once or by individually unforcing the logic signals. To unforce a single logic signal, select the desired logic signal by double clicking on it. After the line is highlighted, select the Unforce Single Command Target. The Execute Command dialog box appears. Select OK to unforce the signal, Cancel to leave the signal forced. The default action is Cancel. To unforce all of the forced logic signals, select the Unforce All Command Target. The Execute Command dialog box appears. Selecting OK unforces ALL forced logic signals in the Control Panel. Selecting the Cancel button cancels the unforcing command. The default action is Cancel.
!
Selecting UNFORCE ALL unforces ALL of the logic signals forced at the Control Panel, including any signals forced from other Logic Forcing Display screens.
Caution Starting the Logic Forcing Display Selecting the Logic Forcing Display icon or typing LFORCE and hitting enter while at the command prompt starts the Logic Forcing Display program. Accessing the Start Menu and Run then entering LFORCE will also start the Logic Forcing Display. The Logic Forcing Display program is configurable from the command prompt. However, configuration arguments are not necessary. Typing LFORCE by itself at the prompt will access the display program. The configuration arguments are: /UNIT: /FILE:
The /UNIT: argument opens the Demand 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:.
GEH-6126
Chapter 5 Control • 57
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
or for files located in other directories: F:\UNIT1>LFORCE /FILE:F:\RUNTIME\LFORCE2.TXT
This argument requires permission to read the file and/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 appears. 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 the OK button 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 menu bar option File opens the file directly. If the specified file does not appear to be a Logic Forcing data file, the user will be prompted as to whether to continue loading the file or aborting 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 appears 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 menu bar option File and the Save As command from the drop-down menu. Any logic point forced in the specific unit will be 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 Logic Forcing Display file data. Exiting the Logic Forcing Display program without saving loses changes to the file. 58 • Chapter 5 Control
GEH-6126
Logic Forcing Display Window The Logic Forcing Display operates in a Windows environment. Using the Logic Forcing Display program is similar to using other Windows applications. 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 shown below : Logic Forcing Display Menu Items and their Functions Menu Items
Drop Down List Function
Description
File
New, Open, Close, Save, Save As, Print, Print Preview, Print Setup, {Filenames}.TXT, Exit
Selects new or existing files, recently edited files, saves edited files, prints files, exits the Logic Forcing Display program.
Edit
Insert Blank Line, Modify Line, Delete Line, Set Font, Select Unit, Find
Inserts, deletes and modifies display lines. Set fonts and selects units.
Toolbar, Status Bar
Edits window display to show or remove toolbar and status bar.
Index, Using Help, About Demand Display
Accesses Help screens.
View Help
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 showing 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:
GEH-6126
•
Header
•
List View
•
Command Target Area
Chapter 5 Control • 59
Header The Header contains the unit name, site name, program title and timetag. 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 is recommended to remain visible at all times. The Header timetag displays the PC 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 unit, then the timetag is No Valid Data. A highlighted Header timetag indicates the oldest piece of data in the Data Area has not been updated for five seconds. List View The List View is composed of the following columns: •
Point Name
•
Current Value from each Processor
•
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 the each processor. The timetag displayed in the Header reflects the timetag 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 may 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 unit. 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. Command Target Area The Command Target area appears on the right side of the Logic Forcing Display window. There are four Arm/Execute 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/Execute targets appear green with black text and require a confirmation prior to sending the force or unforce signal to the unit.
60 • Chapter 5 Control
GEH-6126
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 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 Highlight the desired line. Select the menu bar option Edit and the Modify Line command from the drop-down menu or choose the Modify Line toolbar button. The highlighted pointname field becomes an entry field for the user to type in. The Logic Forcing Display program allows entering 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.
Adding and Deleting a Pointname Line The Logic Forcing Display program allows adding lines at any point in the display screen. Highlight the line above the desired insertion point. Select the menu bar option Edit and the Insert Blank Line command from the drop-down menu or select the Insert Blank Line toolbar button. The Logic Forcing Display program inserts a blank line below the highlighted line. If the display is empty, Insert Blank Line may be applied without first hightlighting a location. To modify the line, see 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 deletes. 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/Execute targets. Arm/Execute command targets require confirmation of their action prior to performing the command. After selecting the Command Target, the Execute Command dialog box appears. Selecting the OK button executes the command. Cancel cancels the command execution. The default action for the Execute Command dialog box is Cancel. Note This procedure for confirming a forcing action prevents executing false commands.
GEH-6126
Chapter 5 Control • 61
Printing From the Logic Forcing Display File The Print command prints the Logic Forcing Display screen. Only the data currently displayed on the screen prints. 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. All three of these commands present the Print dialog box. The Print dialog box allows for the selection of the printer and its properties, the number of copies, and what to print. Selecting OK prints the data, selecting Cancel cancels the print command. The Print Preview command previews the page and allows accessing the Print dialog box.
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 may 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 Selecting the menu bar option File and the Save command from the drop-down menu or selecting the toolbar button with the picture of a disk, saves Logic Forcing Display files already having filenames. The file saves 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 executed. Selecting the OK button after typing in a name saves the file using the filename. Saving a file overwrites the previous file and loses all old information. Note Saving a file overwrites the file, losing data in the initial (unedited) file. 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 appears 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 executed. Using an already exiting 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 will request whether to save changes to any Logic Forcing Display file prior to exiting.
62 • Chapter 5 Control
GEH-6126
Control Constants Display Purpose 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 will be displayed. From this display the user can call up the Control Constants Adjust Display to change any constants that are adjustable. The Control Constants Display has a header above a list of control constants. The header includes: •
Site Name
•
Unit Name
•
Current time being sent from the unit
The list of points has have three columns: •
Point Name
•
Value
•
Units
There will be an icon to the left of the Point Name to determine if the point is adjustable. The icon will be a plus sign if the point is adjustable. The icon will be 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 File Print … - Send what is on the display to a printer. Print Setup … - Select the printer to use and its setup. Exit - Exit the Control Constants display. Edit Select Unit … - Selects the unit the Control Constants display will communicate
with. 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 both the header and the data list will use. Set Default - This sets the font and column widths back to the system default. View Tool Bar - Toggles the tool bar on and off. Status Bar - Toggles the status bar on and off. Help About Control Constants … - Dialog box that shows the revision level of the
Control Constants Display.
GEH-6126
Chapter 5 Control • 63
Command Line Description 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 will be started 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 will be prompted to select a unit. Example: G:\EXEC\CONSTDSP /UNIT:T1
Header Timetag The header timetag displays the timetag of the oldest piece of data being displayed in the data list. Before data has been received, the timetag will read “No Valid Data”. If the oldest piece of data on the screen is more than five seconds old, the timetag will be highlighted.
Changing a Control Constant The Control Constants Adjust can be invoked in two ways: from the mouse or the keyboard. Only Control Constants with a plus next to them can be adjusted. From the mouse, double click the constant to be adjusted. From the keyboard, use the cursor keys to move to the constant to be adjusted and then press the enter key.
Control Constants Display
64 • Chapter 5 Control
GEH-6126
Control Constants Adjust Display Purpose 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 will stop at the current value. More than one Control Constant Adjust Display can be active at a time. The Control Constant Adjust Display can be minimized at any time (including while a point is being ramped). The Control Constants Adjust Display has a header which will include: Site Name, Unit Name, and Current Time being sent from the unit. The following information will be displayed in the dialog box: Point Name, Current Point Value (if the unit is a TMR, three values will be displayed), Target Point Value, Ramp Rate Value, Minimum Value (if it exists), and Maximum Value (if it exists).
Pushbuttons include: • • • • •
Enter Target - Button is gray with black text and will pop up the enter target dialog box when it is pushed. Start Ramp - Button is green with black text. The Start Ramp button will pop up a dialog box asking if you really want to start the ramp. The button will be green with yellow text when the ramp is in action. Stop Ramp - Button is red with black text. This button will immediately stop the ramp. Step Change - Button is green with black text. It will pop up 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 - Button is green with black text. It will pop up a dialog box asking if you really want to save all constants into non-volatile memory.
Demand Display Purpose Many applications require monitoring several data points at a time. Some of these applications may also require the issuing of simple commands. The Demand Display program is a tool designed for these applications. • • • • •
GEH-6126
Demand Displays offer flexible monitoring and control of a variety of points and of multiple units. There are several Demand Display features: Demand Displays allow for monitoring point data and issuing commands to the unit(s). Demand Displays are alterable displays that conform to the users needs. Demand Displays easily conform to the displays required for testing and other special procedures. Demand Displays can control special unit functions while monitoring associated data.
Chapter 5 Control • 65
! Caution
Only qualified personnel knowledgeable about turbine control and protection should create and execute commands. The commands can affect the control state and action of the unit control.
The Demand Display program contains two types of Display windows: • •
Demand Display Menu Demand Display Data
Demand Display Menu Screen The first window is the Demand Display Menu screen. This screen includes a list of all of the Demand Display screens available in the selected Demand Display file. Selecting one of the Demand Display screens on the list accesses the screen. New Demand Display screens must be added to the menu for access and the Demand Display Menu screen must be saved to make the addition permanent.
Demand Display Data Screen The second window is the Demand Display Data screen. The Demand Display Data screen displays the Demand Displays. See the descriptions in the Demand Display Window section. The definitions of each screen are associated with a particular unit. That way, unit 1 may differ from unit 2 in the names and definitions of the displays. Many different types of units may be accommodated in one Demand Display file. The Demand Display may access data from and issue commands to Mark V and Mark V LM units.
File Structure The executable directory, G:\EXEC, contains the Demand Display program, demand.exe. Never tamper with this file. The Demand Display program attempts to open files with .DM2 extensions. For example, DEMAND01.DM2 is a Demand Display filename. The file format for these files is binary. Never edit the Demand Display files directly. Use the Demand Display program to open, modify, and save these files. The *.DM2 files contain definitions for all of the Demand Display screens listed on the Demand Display Menu list for that file. One binary Demand Display file generally saves several Demand Display screens and one unit may use several Demand Display files. The RUNTIME directory in the F:\ drive is the typical location for these files, however, the Demand Display program saves new Demand Display files in the directory in which the program was executed unless a different directory is selected. Demand Displays use data dictionary files for the point list available for use in the Demand Display screens. Demand Displays obtain the values for these points directly from the Data Dictionary. Refer to the Demand Display to Source Conversion Program later in this document for information on how to create a text representation of the binary file.
66 • Chapter 5 Control
GEH-6126
Using the Demand Display Program Creating and editing Demand Displays require both standard and unique operations, which are performed by using the drop-down menu options from the menu selections. Some of the operations are available on the toolbar. This section provides information concerning the following functions: •
Starting the Demand Display Program and Loading a Demand Display file
•
The Demand Display Window
•
Selecting a Demand Display screen
•
Creating a new Demand Display screen
•
Modifying a Demand Display screen Definition
•
Creating a new Demand Display file
•
Selecting a Demand Display type
•
Navigating within a Demand Display screen
•
Adding/Deleting a point name
•
Modifying a point name
•
Adding/Deleting a Command Target
•
Modifying a Command Target
•
Using Command Targets
•
Viewing multiple Demand Displays
•
Saving Demand Displays
•
Copying Demand Display definitions
•
Exiting the Demand Display program
Starting the Demand Display Program Selecting the Demand Display icon or typing DEMAND and hitting enter while at the command prompt accesses the Demand Display program. The Demand Display may also be started by selecting the Windows Start button then selecting Run. Entering DEMAND.EXE in the Run dialog box will start the Demand Display. The Demand Display program is configurable from the command prompt. Note Typing DEMAND by itself will access the Demand Display program. The configuration arguments are: /UNIT: /FILE: /DISPLAY: /TYPE:
The /UNIT: argument executes the Demand Display program for the unit specified. For example: F:\RUNTIME>DEMAND /UNIT:T1
GEH-6126
Chapter 5 Control • 67
where the unit name 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 /FILE: argument executes the Demand Display program and loads a requested Demand Display file. For example: F:\RUNTIME>DEMAND /FILE:OPERATOR.DM2
or F:\RUNTIME>DEMAND /FILE:F:\RUNTIME\OPERATOR.DM2
This argument requires permission to read the file and/or directory. Entering an invalid path or filename displays an error message box and defaults to a blank, untitled Demand Display file. When entering no filename, the Demand Display program attempts to open the default file F:\RUNTIME\DEMAND01.DM2. An error message displays if the program cannot open this file, and the blank Demand Display file appears. The /DISPLAY: argument displays the Demand Display screen in a particular Demand Display file. For example: F:\RUNTIME>DEMAND /FILE:OPERATOR.DM2 /DISPLAY:”LUBE OIL”
The Demand Display program ignores the Demand Display screen name if it is invalid and displays the menu for the Demand Display file requested. If the Demand Display file is invalid, the blank Demand Display file appears. The /TYPE: argument displays the data screen with points specified at the command line. For example: F:\RUNTIME>DEMAND /TYPE:(L1,F4)
The Demand Display program displays the blank Demand Display file if the point types are invalid. If a filename is entered, the point types are ignored.
68 • Chapter 5 Control
GEH-6126
Using multiple arguments configures the Demand Display program more specifically. Combination rules are: •
The File and Display arguments ignore the Type argument.
•
The File argument ignores an invalid Display argument.
•
The Type argument can only be used with the Unit argument or alone.
•
The Unit argument can be used with any other argument, unless it is a single unit system, then the unit argument is ignored.
•
The Unit argument ignores any following invalid argument.
•
The Display argument requires a File argument preceding it.
Examples of valid combinations: F:\RUNTIME>DEMAND /UNIT:T2 /FILE:OPERATOR.DM2/DISPLAY:”LUBE OIL”
or F:\RUNTIME> DEMAND/UNIT:T2 /TYPE:(F4)
The Demand Display program automatically opens the default Demand Display file DEMAND01.DM2, located in the F:\RUNTIME directory. This generic Demand Display file can use data from multiple units. Selecting the menu option File:Open from the drop-down menu displays the Open dialog box. The Open dialog box lists the *.DM2 files located in the directory from which the program was executed. Selecting the file and the OK button displays the requested Demand Display file. Opening *.DM2 files in other directories is possible using the Open dialog box and selecting the drive, directory, file name and the OK button. Selecting Cancel in the Open dialog box cancels the opening of a Demand Display file.
Loading Demand Display Files and Screens There are three ways to load an existing Demand Display file. If the Demand Display program is started at the command line, the name of the file can be added after the Demand Display execution command, Demand, using the /FILE: argument. The extension .DM2 must be included with the filename. For example, F:\RUNTIME>DEMAND /FILE:{FILENAME}.DM2
where {filename}.DM2 would be a Demand Display filename such as OPERATOR.DM2. The Demand Display program is executable from any directory. To load an existing Demand Display file after starting the Demand Display program, select the menu option File:Open command from the drop-down menu. The Open dialog box appears 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 menu option File opens the file directly. If no existing file is specified when executing the Demand Display program, the default file DEMAND01.DM2 located in the F:\RUNTIME directory loads. To create a new Demand Display file, select the menu option File:New from the drop-down menu. A blank Demand Display Menu screen displays with the single menu item Demand Display. This is the blank Demand Display screen template and requires renaming after modification. A new Demand Display file name is required, or the current Demand Display file is rewritten with the new file. Selecting the toolbar button with the picture of a blank sheet of paper also displays the blank Demand Display list screen.
GEH-6126
Chapter 5 Control • 69
Note Saving the Demand Display template screen without a new Demand Display screen name causes the Demand Display template to no longer be a blank template. Saving a Demand Display file without renaming it overwrites the Demand Display file data with the new Demand Display file data. Exiting either the Demand Display screen and/or the Demand Display file without saving loses changes to the file.
The Demand Display Window The Demand Display program operates in a Windows environment. Using the Demand Display program is similar to using other Windows applications. The Demand Display program performs functions selected from drop-down menu options from the menu or buttons on the toolbar. The titlebar displays the filename currently in the Demand Display. The horizontal or vertical scroll bars allow viewing of display screens that exceed the window’s boundaries. The menu at the top of the screen incorporates several items common to Windows applications along with special items associated with the Demand Display. A summary of these items and their corresponding functionality are shown.
70 • Chapter 5 Control
GEH-6126
Menu Items
Drop Down List Function
Description
File
New, Open, Close, Save, Save As, Print, Print Preview, Print Setup, {Filename}.DM2, Exit
Selects new or existing files, recently edited files, saves edited files, prints files, exits the Demand Display program.
Edit
Insert Blank Line, Modify Line, Delete Line, Set Font, Select Unit, Find
Inserts, deletes and modifies display lines. Set fonts and selects units. All others are disabled.
View
Toolbar, Status Bar, Header, Legend, Menu
Edits window display to show or remove toolbar and status bar. Edits Display screen to show or remove Header and Legend. Toggles between Demand Display Menu screen and last Demand Display screen viewed.
Display
Definition, Save, Save As
Changes Demand Display screen to Point List Demand Display type or Data Dictionary Demand Display type. Changes Demand Display Title. Saves Demand Display screen.
Help
Accesses Help screens. Index, Using Help, About Demand Display Demand Display Menu Items and their Functions
The toolbar immediately beneath the menu 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.
GEH-6126
Chapter 5 Control • 71
Demand Display Menu Screen Example
Demand Display Screens Window There are two types of Demand Displays. The Menu screen shows the list of available demand displays for the selected unit. From this screen, the user selects the actual Demand Display Data Display Screen. There are two types of Data Displays, Point List based and Data Dictionary Based.
Demand Display Points Base Display, User Defined, Example
The Point List type Demand Display is a user-defined display created and edited to meet the users needs. These displays are built from points and commands entered by the user and are the most common type of display. The Demand Display program allows modifying and saving Point List type Demand Displays for reuse.
72 • Chapter 5 Control
GEH-6126
Demand Display Dictionary Based Using Logics Example
The Data Dictionary type Demand Display is built automatically from point information stored in the Data Dictionary. This information is useful when investigating specific point types and command options. Data Dictionary type Demand Displays use Dictionary Display Options to configure the Demand Display screens. These options select what points and commands are shown on the Demand Display screen. The names and definitions of the Demand Display Screens are defined on a per-unit basis. Both Demand Display windows are made up of three main regions: •
Header
•
Legend
•
Data Area
Header The Header contains the unit name, site name, program name, display screen name, and timetag for the oldest piece of data in the Data Area. The Header is in a nonscrolling region and cannot scroll off the window. The menu option View:Header toggles the Header on or off. The Header contains valuable process information and is recommended to remain visible at all times. The Header timetag displays the oldest of the displayed pointname timetags in the Mark V LM Control Panel. 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 unit, then the timetag is No Valid Data. A highlighted Header timetag indicates that the oldest piece of data in the Data Area has not been updated for five seconds. The Header timetag in the Demand Display Menu screen displays the PC time.
GEH-6126
Chapter 5 Control • 73
Legend The Legend displays the column headers for the data shown in the Data Area. The Legend is in a non-scrolling region and can not scroll off the window. The menu option View and the Legend command toggles the Legend on or off. The Legend is recommended to remain visible at all times.
Data Area The Data Area is below the Header and Legend. In the Demand Display Menu screen, the Data Area consists of a list of the Demand Display screens available for viewing. In a Demand Display screen, the Data Area consists of an unlimited list of pointnames, their values and units. This information is in a tabular format. Any Command Targets defined appear on the right side of the window. The user may define additional pointnames and Command Targets or remove existing ones from the Point List Displays only. Adding and deleting Pointnames and Command Pushbuttons from a Data Dictionary Display is temporary and cannot be saved. The Value field for the Data Area updates once each second from the Data Dictionary. Unlike the Header and Legend, the pointnames and Command Targets in the Data Area scroll with the scroll bars. The Demand Display program updates only the visible points in the Data Area. The Pointname field holds the control signal pointname (or synonym) of valid unit database points. Entering the pointname causes the Demand 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 data from the requested unit. The Pointname field is 15 characters in length. The Demand Display program allows entering other text into this field for commenting and separating sections of points. Invalid pointnames are treated as text to allow for entering textual separations of the data. The Value field contains point value information. This field updates once each second, is right justified, and may contain up to ten characters. If the value is larger than ten characters, ten asterisks appear. Enumerated state values display across both the Value field and the Units field. The Demand Display program centers the Enumerated state values across these fields and truncates them if they are over seventeen characters long. A blank Value field indicates that the point information is invalid or that there is no data for the point in the Data Dictionary. The Units field displays the engineering units for valid pointnames. The text appears exactly as entered in the data dictionary file. This field is blank for invalid pointnames, but indicates the units for valid points without data in the Data Dictionary. The Units field combines with the Value field to display the text for enumerated points. The Command Target field is the region to the right of the Units field. Unit Command Targets for sending control commands to the unit typically reside here. There are three Command Target types:
74 • Chapter 5 Control
•
Immediate Action
•
Arm/Execute
•
Analog Setpoint
GEH-6126
Immediate Action Immediate Action Command Targets send a command to the control immediately without requiring further action. These targets typically perform an incremental change to the control such as Raise or Lower. They are red targets whose text turns yellow if the feedback logic is supplied and met. Not every Immediate Action Command Target uses feedback logic, as it is optional.
Arm/Execute Arm/Execute Command Targets require an Execute Command to confirm execution. The Execute Command dialog box requests confirmation when the Arm/Execute Command Target is selected. If confirmation or cancellation is not received, the Demand Display defaults to canceling the execution of the command. Selecting OK in the Execute Command dialog box sends the command to the unit. Selecting Cancel cancels the command. The Arm/Execute Command Target typically perform changes to the control state, such as Start and Stop. They are green targets whose text turns yellow if the feedback logic is supplied and met. Not every Arm/Execute Command Target uses feedback logic, as it is optional.
Analog Setpoint Analog Setpoint Command Targets change the setpoint value of the specified control signal, such as a speed or temperature reference. Selecting an Analog Setpoint Command Target displays the Setpoint dialog box. The Setpoint dialog box requests the new value for the control signal and must have a confirmation to perform the change. After entering the new value, selecting OK confirms the change and the new value is sent to the unit. Selecting Cancel cancels the change. The Demand Display cancels the change if neither confirmation nor cancellation is received. The setpoint values use the current display engineering units. Analog Setpoints do not use feedback logics. Note This procedure for confirming commands prior to sending to the unit prevents executing false commands.
Demand Display Setpoint Command Dialog Box Example
Selecting a Demand Display Screen After selecting the Demand Display file, the Demand Display Menu screen is shown in the window. The top of this screen contains the Header with the unit name, site name, file name and PC timetag. Below the Header is the Legend, and then the Demand Display Menu. The Demand Display Menu lists all of the Demand Display screens available in the selected Demand Display file. Clicking on the desired Demand Display screen menu pick or using the arrow keys on the keyboard and hitting enter when the cursor is next to the desired screen menu pick, displays the Demand Display screen. Using the /DISPLAY: argument at the command line also selects a particular Demand Display screen as stated earlier. The names and
GEH-6126
Chapter 5 Control • 75
definitions of the Demand Display Screens are defined on a per-unit basis. The menu screen for each unit may vary and definitions for a given name may vary from unit to unit.
Creating a New Demand Display Screen Adding new Demand Display screens takes place at the Demand Display Menu screen. Position the cursor on the line for the desired insertion point for the new menu item. Select the menu item Edit:Insert Line command from the drop-down menu. The Demand Display program adds a new, blank Demand Display screen titled Untitled:#, where the # is the number of the new screen. After modifying the new screen, save the screen with a new name.
Modifying a Demand Display Screen Definition/Type Modifying a Demand Display screen definition takes place at the Demand Display Menu screen. Position the cursor on the line associated with the desired screen. Select the menu option Edit: Modify Line from the drop-down menu. The Display Definition dialog box appears. The Display Definition dialog box contains three sections. The first section indicates the title of the Demand Display screen. The second section allows for changing the Demand Display screen type. The third section selects what point types to display in a Data Dictionary Display. Use the second section to change between a Point List type or a Data Dictionary type. Saving the change makes it permanent.
76 • Chapter 5 Control
GEH-6126
Display Definition Dialog Box
Selecting the menu option Display:Definition from the drop-down menu from the Demand Display screen also allows modifying the Display Definition. The Display Definition dialog box appears to allow changes of the Demand Display screen definition type. Saving the change makes it permanent.
Changing a Display Title Selecting the menu option Display:Definition on the drop-down menu presents the Display Definition dialog box. Use the first section, the Display Title box, to change the Demand Display screen title. Placing the cursor in this box and typing in a new name changes the name of the Demand Display screen. The Display Title can be up to 25 characters long. Duplicate title names are possible, but not recommended. Display Titles should never be empty or all blanks. The use of ellipsis (.....) placed before the title of a Data Dictionary type Demand Display is recommended to differentiate it from a Point List type Demand Display. Selecting the Save or Save As command from the drop-down menu of the Display menu is required to make the Display Title change permanent. Save As by itself does not change the old Display Title to the new Display title, as it inserts the Demand Display screen to the bottom of the Demand Display Menu list with the new Display Title. If no new Display Title is entered, it inserts a copy of the Demand Display screen with the same Display Title as the old Demand Display screen at the bottom of the Demand Display Menu list. The Demand Display program requests whether the Display Title should be saved if the Demand Display Menu screen is accessed or the program exited without saving.
Navigating There are several ways to navigate within the Demand Display program. To view menu items or pointnames that are off the bottom or top of the screen, use 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. To view areas out of the display window on the sides use the scroll left/right bar on the window.
Adding/Deleting a Pointname or Line Adding lines is possible in either Demand Display screen type, but saving is only allowed in a Point List type Demand Display screen. Position the cursor on the line below the desired addition location. Selecting the menu option Edit:Insert Blank Line from the drop-down menu inserts a blank line above the selected line. To modify the line, see the Modifying a Point Name or Line section below. Saving both the Demand Display screen and Demand Display file makes the changes permanent. Deleting lines is possible in either Demand Display screen type, but saving is only allowed in a Point List type Demand Display screen. Position the cursor on the desired line. Selecting the menu option Edit:Delete Line from the drop-down menu deletes the line. If the line corresponds to the first line of a Command Target, the target deletes. Saving the Demand Display screen and the Demand Display file makes the changes permanent.
Modifying a Pointname or Line Modifying lines is possible in either Demand Display screen type, but saving is only allowed in the Point List type Demand Display screen. Position the cursor on the desired line. Selecting the menu option Edit:Modify Line from the drop down menu displays the Point Name dialog box. Entering the desired point name and selecting OK changes the information on the line or adds information to a blank line. The Cancel button cancels any changes. The Define Command button appears when it is GEH-6126
Chapter 5 Control • 77
possible to add or modify a Command Target associated with that line. Saving the Demand Display screen and Demand Display file makes the changes permanent.
Modify Line Dialog Box
Adding a Command Target Adding Command Targets is possible in either Demand Display screen type, but saving is only allowed in the Point List type Demand Display screen. Position the cursor on the line that corresponds to the Command Target. One blank line between targets in the Target field is required. Select the menu option Edit:Modify Line from the drop-down menu. The Point Name dialog box appears. Enter the desired point name if adding to a blank line. Typically, the point name on the line corresponding to the first line of the Command Target has direct relevance to the button and its action. Select the Define Command button. The Command Definition dialog box appears. If this button is not visible, then a Command Target is not allowed on this line.
Command Definition Dialog Box
The Command Definition dialog box contains fields for information to define a Command Target and its feedback (optional). Command Targets require definition of several parameters: Button text, unit command pointname, button type, unit command value of the point and value type, and feedback signal pointname and sense. The button text should indicate the Command Target’s action. Enter the button text in the two fields of the button text section. The Command Targets permit two lines
78 • Chapter 5 Control
GEH-6126
of text of up to eight characters on a line. The Demand Display program centers the Command Target text with the button. Button text appears black and turns yellow if the associated feedback logic is supplied and sense met. The unit command pointname is the control signal pointname that receives the targets value. Enter the pointname of the unit command in the field for the pointname. Only command pointnames may be entered and may be Pushbutton, Logics or Analog Setpoints. Other point types are not allowed. The button type defines which of the three Command Targets to use. Select the button type. Refer to the earlier Demand Display screen section for a description of the Command Target types. The value field holds the value the Command target sends to the unit. There are three guidelines correlating to the type of pointnames used. A Pushbutton’s value is the number of scans to hold the pushbutton true. The minimum value is four scans. Logic States require a value of 1 or 0, other values are not allowed. Analog Setpoints require a value in the engineering units specified for the command signal point.
GEH-6126
Chapter 5 Control • 79
The value type governs how the Command Target sends the value to the unit. There are three possible choices. A set (=) sends the value from the value type to the unit. Set is required for Pushbuttons and Logic States and is optional for Analog Setpoints. An increment (+) adds the value in the value field to the current value of an Analog Setpoint and sends it to the unit. Decrement (-) subtracts the value in the value field from the current value of an Analog Setpoint and sends it to the unit. The feedback signal fields contain the feedback signal’s definition. Immediate Action and Arm/Execute button types can use feedback signals. Analog Setpoint button types cannot. The pointname field is for the control signal pointname of the feedback signal. These can only be logic point types. The Sense field can invert the sense of the feedback signal. After completing all of the fields in the Command Definition dialog box, the entries must be confirmed. There are five buttons in the Command Definition dialog box referring to confirmation. The Check Form button checks the command definition entries for consistency and errors. The OK saves any changes and creates the target. Help initiates the help data for this dialog box. Cancel cancels any changes to the command definition. Delete resets the Command Definition and destroys the Command Target.
Deleting a Command Target There are two ways to delete Command Targets: deleting the target itself or deleting the entire line, pointname and target. To delete the Command target only, position the cursor on the pointname in the line corresponding to the top button line of the target. Select the menu option Edit:Modify Line from the drop-down menu. The Point Name dialog box appears. Select the Define Command button. The Command Definition dialog box appears. Selecting Delete resets the Command Definition and deletes the Command Target. To delete the associated pointname and the Command Target, position the cursor on the pointname in the line corresponding to the top button line of the target. Select the menu option Edit:Delete Line from the drop-down menu deletes the point name and the Command Target.
Modifying a Command Target It is possible to modify Command Targets. Position the cursor on the line corresponding to the top button line of the desired Command Target. Selecting the menu option Edit:Modify Line from the drop-down menu displays the Point Name dialog box. Selecting the Define Command button from the Point Name dialog box displays the Command Definition dialog box. Modify the definition as stated in the Adding a Command Target section above.
Using a Command Target Positioning the cursor on the Command Target and selecting it activates the Command Targets. Immediate Action Command Targets are red and activating them immediately sends the command to the unit. Arm/Execute Command Targets are green. Activating them displays the Execute Command dialog box to confirm execution. The default action of this dialog box is Cancel. OK confirms the execution and the command is then sent to the unit. Cancel cancels the command.
80 • Chapter 5 Control
GEH-6126
Analog Setpoint Command Targets are gray, and when activated, the Setpoint dialog box appears. The Setpoint dialog box requests a value for the Analog Setpoint and also to confirm execution. Selecting OK confirms the command and the value is sent to the unit. Cancel cancels the command. The default action is Cancel.
Printing The Print command prints the Demand Display screens. Only the data currently displayed in the Demand Display screen window prints. Select the menu option File:Print or the Print Setup from the drop-down menu or select the toolbar button with the printer. All three of these commands present the Print dialog box. The Print dialog box allows for the selection of the printer and its properties, the number of copies to print, and what to print. Selecting OK prints the data, selecting Cancel cancels the print command. The Print Preview command previews the page and allows access to the Print dialog box.
Other Options There are several other options available in the Demand Display program. Selecting the menu option Edit:Set Font from the drop-down menu presents the Windows Font dialog box. The Font dialog box allows for selecting the font and color of the Demand Display screen. The selection applies to the entire Demand Display screen except for the Command Targets whose colors are predefined. Selecting the menu option Edit:Select Unit from the drop-down menu allows for unit selections. In multiple unit sites, any unit may be monitored from one Demand Display screen. Select Unit displays the Unit Selection dialog box. The currently selected unit is highlighted. The available units display in alphabetical order. Select the desired unit. This option is not available in single unit sites. Selecting the menu option View:Menu from the drop-down menu toggles between the menu and the most recently viewed Demand Display screen. Toggling to the Demand Display Menu screen from a Demand Display screen loses any changes if the Demand Display screen is not saved. The Demand Display program asks whether or not to save the Demand Display screen. Selecting Yes saves the Demand Display screen, No toggles to the Demand Display Menu screen without saving. Selecting Menu from the Demand Display Menu screen displays the most recently viewed Demand Display screen.
Saving Demand Display Screens and Demand Display Files Demand Display screens and Demand Display files are saved separately. To save a Demand Display screen, select the menu option Display:Save or Save As from the drop-down menu. The Save command saves the Demand Display screen changes to the same Demand Display screen title. The Save As command saves the Demand Display screen changes to a new Demand Display screen title on the Demand Display Menu. Selecting Save As presents the Display Definition dialog box. If a new Demand Display screen title is not typed in here, another Demand Display screen with the same name is added to the bottom of the Demand Display Menu. It is recommended to re-title edited Demand Display screens if the original is kept. If the Demand Display program is exited prior to saving changes to Demand Display screens, the program asks whether the Demand Display screen should be saved prior to exiting. Selecting Yes saves the Demand Display screen, No exits the Demand Display screen without saving.
GEH-6126
Chapter 5 Control • 81
Save Demand Display files anytime a Demand Display screen is saved or added. From the Demand Display Menu screen, select the menu option File:Save from the drop-down menu to save the changes to the current Demand Display file. Selecting the Save As command displays the Save As dialog box allowing for the directory and new file name to be selected. Exiting the Demand Display program prior to saving changes causes the program to ask whether or not to save the Demand Display file. Selecting Yes saves the file, No exits the Demand Display program without saving.
Copying Demand Display Screen Definitions The names and definitions of the Demand Display Screens are defined on a per-unit basis. On locations where there are duplicate units or units that share similar functions, it may be useful to Copy a Demand Display Screen from one unit to another. To do this, open the desired Demand Display Screen. Now, select the Edit menu item. Select Unit and select the new unit. Select the DISPLAY menu item Save and the Screen is now saved to the new unit. To make this change permanent, select File and Save or Save As. Otherwise, the change will be lost when the Demand Display program closes.
Exiting the Demand Display Program Selecting the menu option File:Exit from the drop-down menu exits the Demand Display program. If changes were made to the Demand Display file without saving, the Demand Display program asks whether to save the changes. Selecting Yes saves the changes to the current Display screens and Demand Display file, No exits the program without saving.
Alarm Logger Control Purpose Several classes of turbine control actions may be automatically logged to a hard copy printer. The Alarm Logger Program allows the user to select the types of alarms and events to output to the printer. The user must select from four categories of information to be printed and select the unit from which the information is gathered. There are four categories of information that may be printed: • • • •
Process Alarms Diagnostic Alarms Events SOEs - Sequence of Events
The definition and configuration of these point categories and the setup of the Alarm Printer are covered later in this manual.
82 • Chapter 5 Control
GEH-6126
The Alarm Logger Control Dialog Box
Using the Alarm Logger Dialog Box The Alarm Logger Control dialog box controls the output of the Alarm Logger. The user must make the following decisions when completing the Alarm Logger dialog box: • • • • •
Select Information to be Printed Select Unit from which Information is Gathered All Units Selection Flush Button Selection Save Changed Settings
Select Information to be Printed There are four categories of information that may be printed: • • • •
Process Alarms Diagnostic Alarms Events SOEs
An ’X’ in the checkbox for an information type indicates to the Alarm Logger Program to enable printing for that information type for that unit. Please note that the configuration of the individual points is not a function of the Alarm Logger Control.
GEH-6126
Chapter 5 Control • 83
Select Unit Each of the categories of information may be selected on a unit basis. The unit may be changed by clicking in the Select Unit combo box and selecting a unit name. Unit names are listed in alphabetical order. •
All Units The All Units button selection applies the settings for the current unit to all units.
•
Flush Button The Flush button deletes all pending alarm print jobs for ALL units from the Alarm Printer. The Flush button takes immediate action and does not require the OK button to be activated.
•
Save Settings Any changes made to the Alarm Logger settings are saved ONLY if the user selects OK when leaving the Alarm Logger Control dialog box. Leaving the dialog box by any other method, such as selecting Close or Cancel, causes the changes NOT to be saved.
•
File Type The Alarm Logger Control does not access any files when making its
changes. Instead, it writes its output to a special section of global memory that is then read by the Alarm Log program which writes the alarms and events to the alarm printer.
Executing the Alarm Logger Control The Alarm Logger Control may be launched from the command line with the following optional argument to quickly bring the display to a desired configuration: The user may use this command line parameter to customize the startup of the program, or enter logger.exe in the Run dialog box in the Start Menu or simply double click on the program icon. The following example specifies the unit name (/UNIT:) as T1: G:\EXEC\LOGGER.EXE /UNIT:T1
84 • Chapter 5 Control
GEH-6126
Command Line Description The Control Constants Adjust Display can be invoked from the command line with a Pointname. If no pointname is specified, then a dialog box will appear to enter a point. The format of the command line argument will be: /POINT::
The unit is optional if there is only one unit. Example:
G:\EXEC\CONSTADJ /POINT:T1:CSKATS
G:\EXEC\CONSTADJ /POINT:CSKATS (for single unit sites)
Header Timetag The header timetag displays the timetag of the oldest piece of data being displayed. Before data has been received, the timetag will read No Valid Data. If the oldest piece of data on the screen is more than five seconds old, the timetag will be highlighted.
Control Constants Adjust Display
Hold List The Hold List is required for the HMI to support Mark V Large and Medium Steam Turbine Controls on systems that have ATS, Automatic Turbine Startup. The ATS code resides in ROM in the processor only. ATS is active only when the Automatic mode has been selected. Its purpose is to set speed control targets and valve positions based on various inputs - steam temperatures and pressures, calculated valve stresses, turbine rotor stresses, and turbine shell stresses, metal temperatures, speed and operating mode. Turbine operating conditions may cause a hold which prevents ATS from setting the speed or load target to a higher value. In the HMI processor, the Hold List Display provides the operator a way to view the current points on the Hold List and to override any or all hold points if he desired.
GEH-6126
Chapter 5 Control • 85
Overriding a hold allows the ATS to advance its targets as operating conditions permit.
Hold List Points The points for the Hold list should be listed in the HMI unit configuration directory F:\UNITN\TOTT_B.SRC file. The list can hold 64 points, maximum. The points should be either Alarms or Events so that they will appear on the Alarm and Event Logger. This file must be compiled by the table compiler, G:\EXEC\TABLE_C.EXE. The point list is then downloaded to and processors with the EEPROM downloader, G:\EXEC\EEPROM.EXE. Select TOTT for the section to download. The processors should be rebooted to make any list changes active.
Hold List Programs The Hold List is maintained in the and processors by programs in PROM. The Hold List receiver in the HMI is automatically started by the TCI system service. The Hold List is displayed on the HMI by the Cimplicity Alarm Viewer. Users should configure a separate Cimplicity Alarm Viewer for the Hold List to allow only the holds from a given unit on the display and to exclude holds from the regular alarm list. (Of course, the user can change this at any time.)
Hold List Rules The HMI Hold List is maintained according to the following rules : •
A point that is picked up is entered in the Hold List as (0 -> 1).
•
Unacknowledged entries will have an “N” character in the ACK field.
•
Acknowledged entries will have a “Y” character in the ACK field.
•
A hold point whose state is a picked up (1) will display the text ALARM in the state field.
•
A hold point whose state is a dropped out (0) will display the text NORMAL in the state field.
•
A point that picks up and drops out and has been acknowledged is removed from the Hold List display.
•
A picked up hold point may be overridden by an operator using the Lock command button.
86 • Chapter 5 Control
•
Overridden points will display Locked as the first part of their long name text.
•
An overridden point loses its override when it drops out (1 -> 0).
•
The Hold List displays the time of the last pickup or override, unit, acknowledge state, current state, override status, and the short and long name of each hold point in the list.
•
The text Hold will appear in the drop number field and the CSDB offset will be in the reference field. The reference field is typically not displayed.
•
The Hold List program in , not , will output a logic signal indicating that there are one or more active holds that have not been overridden. This point is named L68DW_ATS_HL. ATS and the turbine control use this signal to set speed, load, and valve position targets.
GEH-6126
Manual Sync Object The Manual Sync Object is an OLE object to be used in CIMPLICITY to make a screen similar to the Synchronizing Display in the MKV . The object contains all the fields that need to be updated at a fast rate. All data in the object is updated at 16 Hz. TCI must be running in the computer that is displaying the object. The object uses BMS and other TCI resources to get its data and send the commands. The object consists of five parts:
GEH-6126
•
The middle of the object contains the synchroscope. It will be configured using the Scope tab on the Properties page.
•
The top left of the object displays the breaker close times. It will be configured using the Breaker tab on the Properties page.
•
The right of the object displays the permissives needed to close the breaker. It will be configured using the Permissives tab on the Properties page.
•
The center left of the object contains the Breaker Trip and Breaker Close buttons. They will be configured using the Buttons tab on the properties page.
•
The bottom left of the object displays some values that need to be updated quickly. These will be configured using the Values tab on the Properties page.
Chapter 5 Control • 87
Scope Tab
The Scope tab is used to configure the Synchroscope part of the object. It has 7 fields to fill in: •
Unit - This field must be filled with the unit name. You can only pick Mark V
and Mark V LM units. These are the only units that will appear in the pick list. •
Angle Pointname - This is the signal that will drive the synchroscope pointer.
The pointer will be positioned at this angle as long as the slip frequency is less than the Maximum slip frequency. •
Slip Freq. Pointname - This is the signal that will be used to determine the current slip frequency. If this frequency is greater than the maximum slip frequency, the pointer will be positioned at the bottom of the scope.
•
Max. slip freq. to show - This is the maximum slip frequency. It is used above.
•
Scale Marks - This entry is used to enter the location of where marks should
appear on the scope. They are entered in degrees separated by spaces.
88 • Chapter 5 Control
•
Sync Check Pointname (optional) - This signal will be used to change the color of the pointer. If this signal is not defined, the pointer will always be displayed in white. If the signal is TRUE, the pointer will be displayed in green. If the signal is FALSE, the pointer will be displayed in red.
•
Sync Relay Pointname (optional) - This signal is the state of the sync relay. It will be used to draw a green dot at the end of the pointer when it is TRUE. These dots will drawn each time the pointer is updated and this signal is TRUE. The “R” button to the top right of the scope is used to reset the dots.
GEH-6126
Breaker Tab
The Breaker tab is used to configure the breaker close times part of the object. It has 6 fields to fill in: •
TCEA Socket - This entry defines the BMS socket that should be used for obtaining the TCEA diagnostic message. This message is how the object gets the breaker close times. This value is usually 15.
•
TCEA IO Processor - This entry defines the I/O Processor that is used for
obtaining the TCEA diagnostic message. This value is usually 2F HEX. •
TCEA Diagnostic Message type - This entry defines the type for a diagnostic
message. This value is usually 5. •
Nominal Close Time message offset - This entry defines the offset into the
diagnostic message to the nominal close time value. This value is usually 40. •
Learned Close Time message offset - This entry defines the offset into the
diagnostic message to the learned close time value. This value is usually 42. •
GEH-6126
Actual Close Time message offset - This entry defines the offset into the diagnostic message to the actual close time value. This value is usually 48.
Chapter 5 Control • 89
Permissives Tab
The Permissives tab is used to configure the Permissives part of the object. The list box has 3 columns. The Sense column determines when a green or red box is displayed by the variable. If the value equals the sense value, a green box is displayed. A red box is displayed otherwise. When a red box is displayed, a dash is displayed next to it. The Pointname column is the logic signal that will be used. The ID String column is the string that will be displayed next to the box. The permissives will appear in the object in the same order they are displayed in the list box.
The Add button is used the add entries to the list. Entries are always added to the end of the list. The Delete button will delete the currently selected entry. The Edit button will edit the currently selected entry. The Up button will move the currently selected entry up one row in the list box. The Down button will move the currently selected entry down one row in the list box.
90 • Chapter 5 Control
GEH-6126
Buttons Tab
The Buttons tab is used to configure the buttons on the center left of the object. There are two buttons that can be configured: •
Breaker Close Pointname (optional) - This is the signal to send the Breaker
Close pushbutton command to. If this field is not filled in, the button will not appear. The duration of the pushbutton command will be set in the duration box. •
Breaker Trip Pointname (optional) - This is the signal to send the Breaker Trip
pushbutton command to. If this field is not filled in, the button will not appear. The duration of the pushbutton command will be set in the duration box.
When either of the above buttons are pushed, they will bring up another dialog box. This dialog box will contain a command button and a done button. The breaker close or trip command will be sent on the release of the command button. The done button is used to exit the dialog box.
GEH-6126
Chapter 5 Control • 91
Values Tab
The Values tab is used to configure the Values part of the object. The list box has 3 columns. The ValueSize column sets the number of digits to use to display the value. The number of decimal places and the units string specified in the scale code will be used. The PointName column is the signal that will be used for the value. The Label is the string that will be displayed to the left of the value. The values will appear in the object in the same order as they appear in the list box. The Add button is used the add entries to the end of the list. The Delete, Edit, Up, and Down button apply to the currently selected entry. The Up button will move the currently selected entry up one row in the list box, and the Down button moves it down one row.
Colors Tab
The Colors tab is used to change some of the colors in the object. Background Color will set the background color of the object. Foreground Color will set the color of the text in the object.
92 • Chapter 5 Control
GEH-6126
Chapter 6 Configuration
Introduction This chapter describes the files, tools, and processes available to personnel for modifying the Unit Control and HMI configuration. The configuration of the HMI is divided into three major areas: •
Unit Control Configuration
•
Turbine Control Interface (TCI) Configuration
•
CIMPLICITY Configuration
When the HMI, Unit Control and CIMPLICITY systems are properly configured, they work together to provide safe, reliable, and efficient unit operation with friendly, easy to use operator screens providing accurate data display and unit control.
! Caution
Only trained, experienced personnel should be involved in modifying any aspect of configuration on the HMI. Improper alterations to any configuration on the HMI can affect unit function, unit control, accuracy of data displayed, and unit and external communications reliability.
Unit Control Configuration deals with the files and tools available for modifying the Unit Control Configuration. These changes may include:
GEH-6126
•
Adding and deleting CSDB points
•
Changing display scale codes
•
Modifying Control Constants
•
Changing control sequencing
•
Changing Big Block and Primitive Block passed parameters
•
Modifying alarm and long name text
Chapter 6 Configuration • 93
This manual is intended as a reference to the specific HMI features available to the user. This manual is not intended to cover the philosophy of unit configuration.
HMI Configuration deals with how to configure the TCI. TCI is the product that builds the files and runs the processes that allow communication with the unit control panel. It contains: •
The tools building and downloading the unit configuration.
•
A set of unit control, data display, and diagnostic screens.
•
The TCI Service that uses the unit configuration on the HMI to communicate with the unit.
•
Programs for Remote Control, MODBUS and GSM.
CIMPLICITY Configuration in this manual is limited to creation and modification of the CIMPLICITY point database including points for display, as well as alarms, events, and hold points. The details of creating and modifying CIMPLICITY Projects and View screens and other configuration of CIMPLICITY features are not described in this manual. Please refer to the CIMPLICITY documentation in GFK 1180 for more information on CIMPLICITY.
HMI Configuration HMI Configuration Overview
The HMI consists of many software products, each requiring its own configuration. The HMI is composed of these software products: •
Windows NT
•
Turbine Control Interface (TCI)
•
Cimplicity Bridge (CIMB)
•
CIMPLICITY
The HMI has been designed to use the features of each system so to display unit control data and send commands to control the unit. These systems must work together. The HMI is delivered pre-configured from the factory with the proper versions of software. Upgrades to any portion of the HMI software must coordinated with the factory in order to insure proper HMI function. The upgrade of any single component could render the system inoperable. Always check with the factory first.
94 • Chapter 6 Configuration
GEH-6126
! Caution
! Caution
Software upgrades to the HMI must be coordinated with the factory. Only qualified personnel should make these changes. Installing the wrong version of software could render the HMI inoperable.
Only trained, experienced personnel should be involved in modifying any aspect of configuration on the HMI. Improper alterations to any configuration on the HMI can affect unit function, unit control, accuracy of data displayed, and unit and external communications reliability.
When the Windows NT, HMI, Unit Control and CIMPLICITY systems are properly configured, they work together to provide safe, reliable, and efficient unit operation with friendly, easy to use operator screens providing accurate data display and unit control.
This section describes the HMI configuration files, tools, and processes available for modifying its configuration. The configuration of the HMI is divided into these areas: •
Windows NT
•
Turbine Control Interface (TCI) Configuration
•
Windows NT Control Panel Applet
•
TCI Print Queues
•
Turbine Maintenance Icons
•
Control Hierarchy
•
EPA Display
•
Stagelink
•
Time Zone Creation
•
Time Synchronization
•
CIMPLICITY Bridge
•
CIMPLICITY Configuration
This manual does not cover the Windows NT configuration except for the section on user accounts. Windows NT is highly flexible, very powerful operating system with a graphical user interface (GUI). It can run word processing, spreadsheet, database, and other programs from other vendors. Note Operation of third party software on the HMI can affect the use of computer
resources, which may affect HMI performance. The intended purpose of the HMI is to display unit control data and send user commands to the control.
GEH-6126
Chapter 6 Configuration • 95
TCI is the product that builds the files and runs the processes that allow communication with the unit control panel. It contains: •
The tools building and downloading the unit configuration.
•
A set of unit control, data display, and diagnostic screens.
•
The TCI Service that uses the unit configuration on the HMI to communicate with the unit.
•
Programs for Remote Control, MODBUS and GSM.
•
TCI forms the core of the HMI system and its configuration is critical to proper HMI function. The sections in this manual describe how to configure TCI.
CIMPLICITY Bridge is the communication path within the HMI between the TCI and CIMPLICITY. It puts unit control data in the CIMPLICITY database, sends operator commands from the HMI to the unit control, and manages the alarm and event messages between the unit control and CIMPLICITY. There is no configuration for the CIMPLICITY Bridge other than to configure the CIMPLICITY point database and alarms. These topics are covered under CIMPLICITY configuration.
CIMPLICITY Configuration in this manual is limited to creation and modification of the CIMPLICITY point database including points for display, as well as alarms, events, and hold points. The details of creating and modifying CIMPLICITY Projects and View screens and other configuration of CIMPLICITY features are not described in this manual. Please refer to the CIMPLICITY documentation in GFK 1180 for more information on CIMPLICITY.
TCI Configuration TCI is the software package that provides the Turbine Control Interface. This software is used to: •
Configure and download the Turbine Control Panel
•
Communicate with the Turbine Control Panel to collect real time data
•
Provide advanced debugging programs
TCI is installed as a Windows NT System Service. The TCI System Service is typically set to start automatically when the computer is restarted, no user needs to be logged in for the TCI service to be running.
96 • Chapter 6 Configuration
GEH-6126
TCI Registry Information - Control Panel Applet As a System Service, TCI uses the Windows NT Registry to save configuration information. TCI provides a Control Panel Applet (Start - Settings - Control Panel - TCI) for changing its configuration values in the Registry. Available options include: Auto Login: This section informs the Windows NT Operating System that when the system is booted it should automatically log in the specified user. This prevents a user from having to log in when the computer is started. Note If the computer is set for Automatic Login, you can disable this feature by holding down the Shift key on the keyboard when the desktop background appears during the Windows NT startup process. TCI Site: This section informs TCI about the options it requires to find and use the site configuration files. TCI defines the pseudo drive "F:" to point to the TCI site configuration files, and this section informs TCI where those files exist. Other site options, such as whether to run in English, Metric, or Custom engineering units, are also set here. Time Sync: This section informs TCI what type of hardware exists for acquiring the current time. (This function is typically used when the HMI is requested to become a time master on the StageLink.) This setting must match the hardware in the PC that is being configured. The options for "Time Acquisition Hardware" include: None: The TCI service will be told that the current time is not available for dissemination. Low Resolution: The TCI service will be allowed to fetch the normal PC clock as a low-resolution time source. High Resolution: The TCI service will expect a high resolution time board installed in this PC. If this option is selected the High Resolution Time Card section must be filled out defining which time card is installed and its configuration parameters. ARCNET: This section informs TCI how to communicate with an installed ARCNET card. The ARCNET card is the interface to the StageLink. The settings in this section must match the settings on the actual ARCNET card.
GEH-6126
Chapter 6 Configuration • 97
TCI Configuration Files The configuration files for TCI are stored on the pseudo drive "F:". The top level of the F: drive contains the files that configure the TCI System Service for a particular site. Included here is information on where to find the directories that contain the unit configuration files. Two files are always required for TCI to run, F:\CONFIG.DAT and F:\TIMEZONE.DAT. A number of optional configuration files are only required if the option they control is in use at this site.
F:\CONFIG.DAT F:\CONFIG.DAT is the primary configuration file for the TCI System Service. This file informs the TCI System Service:
•
The list of turbines, and for each turbine:
•
The internal unit number for the turbine (1..n)
•
The name associated with this unit
•
The unit configuration directory for the unit
•
The type of turbine control (Mark V, Mark V LM)
•
The addresses of each node on the StageLink
•
The TCI options that are in use at this site
F:\TIMEZONE.DAT F:\TIMEZONE.DAT is used to convert times from UTC to local time. The Windows NT operating system keeps track of the current conversion, but this file is used by TCI to be able to convert times from historical data correctly.
Optional Configuration Files Other TCI configuration files are only required if the option that they control is in use at this site. These potential files include:
F:\IO_PORTS.DAT: This optional data file is used if the TCI System Service is to take over any of the RS-232 ports on the computer. This file indicates which communication ports should be used, what the port settings are supposed to be (baud rate, parity…) and what function the port is used for. Functions include MODBUS Master and MODBUS Slave.
F:\TIMESYNC.DAT: This optional data file is used if the HMI is to be a time master on the StageLink. It is also used if you wish this HMI to synchronize its clock to an external time source, be it a High Resolution Time Card or a time master on the StageLink.
F:\MODB_FWD.DAT: This optional data file is only used if the MODBUS Slave over Ethernet function is being used and the MODBUS master does not support sending a slave address as part of the Ethernet message. This file remaps the individual slave register sets into one large register set, allowing information from multiple slaves to be treated as information from one large slave. (This function is only supported for the MODBUS over Ethernet link, not for RS-232 links.)
98 • Chapter 6 Configuration
GEH-6126
F:\AT_START.DAT: This file defines a set of commands that are run after TCI is started. It is used to start any site-specific programs that need to be started after TCI is started. F:\AT_STOP.DAT: This file defines a set of commands that are run before TCI is shut down. It is normally used to stop any site-specific programs that need to be stopped before TCI is stopped.
TCI Font Loading There are two fonts that are distributed with the TCI Product Code. These are regular TrueType fonts that can be installed in Windows NT’s list of available fonts. The fonts are installed by using the Fonts item in the Control Panel. (Start Settings - Control Panel - Fonts) The font files are distributed in the G:\DATA directory, and include:
LINEDRAW.TTF: This TrueType font includes the special symbols used for drawing line and box graphics in a non-proportional spaced font. This is used for printing out CSP documents, and is used by the Dynamic Rung Display for presenting information. GELOF___.TTF: This TrueType font includes GE logos that are used on various displays.
TCI Print Queues TCI has two optional programs that provide a real time printout of information to a printer. To activate these real time printers, special print queues are created. (If the print queues are not created, TCI simply assumes that the function is not desired at this site.) Real time print queues are typically directed to local printers that are dot matrix printers. These dot matrix printers print each entry immediately, they do not buffer a page of text at a time like laser printers or other page printers do. The print queues that TCI support include:
Alarm Printer: If the Windows NT Print Queue called "Alarm Printer" is defined, TCI will format and send to that printer a real time report of the digital exception messages from the Turbine Control Panel. These exception messages include: Process Alarms, Diagnostic Alarms, Events, and SOE’s. The LOGGER program can be used to fine tune which type of messages are sent to the printer on a per-unit basis.
EPA Printer: If the Windows NT Print Queue called "EPA Printer" is defined, TCI will format and send to that printer a real time report of any EPA logs generated by the Turbine Control Panel.
GEH-6126
Chapter 6 Configuration • 99
EPA Log EPA Logger The EPA Logger will provide access to the EPA data that has been configured in the Mark V controller. To enable the EPA Logger on the HMI, configure a printer in Window NT and name it "EPA Printer" and add the following entry to F:\CONFIG.DAT in the Options section: Options EPA_LOG=Yes
The EPA logger will periodically poll any units that have EPA logging enabled and reports will be printed as determined by the unit. As this capability is not present in Mark VI or Mark V LM controllers, the EPA Logger will only poll Mark V controllers. The EPA Logger provides access to current EPA data from the controller for use on CIMPLICITY displays. The printer that you configure as "EPA Printer" should be different from the printer configured for alarm logging. A properly configured demand display should provide enough information to verify the operation of the EPA logger. A description of the inputs, outputs and operation of the EPA function in the controller can be found in the EPALOG.PIC file in your unit directory on the F: drive. This feature is also shown in the following two illustrations.
100 • Chapter 6 Configuration
GEH-6126
EPALOG -- Wet Low NOx EPA Logger L3WQIN
clear
DCC
SS
List of inputs from EPA_B.SRC
Calculate average of each input every minute based on once per second sampling
L83WQL3N enable
time clear
Minute Averages: Stored in 60 point circular file
Four Minute Alarm: If WXC>WXJ for four consecutive minute avg. then set LWLX4MIN=1
LWLX4MIN
clear data enable
time clear
Hourly Average: Calculated after each 60 points have been stored. clear data
Hourly Alarm: If WXC>WXJ for hourly average then set LWLXHR=1
LWLXHR
enable
EPALOG, DCC Portion
GEH-6126
Chapter 6 Configuration • 101
EPALOG -- Wet Low NOx EPA Logger Processor Output to display: hourly and minute averages
CONFIG.DAT If EPA_LOG=YES collect data from and enable outputs
Output to printer:
minute average
All minute averages from hourly average calculation
hourly average enable
enable LWLXHR AND
IO_PORTS.DAT Enable output to printer assigned to EPA$PRINT variable
Output to printer once an hour: hourly average enable
enable
EPALOG, Processor Portion
EPA Data Display Defining EPA Data Points To define Mark V Control Data Points for the EPA screen, the user must modify the F:\UNITN\EPA_Q.SRC source file. This can be done by using the notepad editor. With the use of the editor, control data points can be added or removed from the file.
102 • Chapter 6 Configuration
GEH-6126
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 may 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.
GEH-6126
Chapter 6 Configuration • 103
Turbine Control Maintenance Icons The User Icon Program, UICON.EXE, automatically creates the Desktop and Start Menu Icons needed for the major tasks required for both HMI and unit configuration and control. This allows maintenance personnel quick access from the Desktop and Start Menu. Users may customize the menu selections by adding or deleting items through use of the Windows NT user interface features.
TheTurbine Control Maintenance Start Menu Selections This program may be run from the command line: G:\EXEC\UICON.EXE
or from the Start Menu:Turbine Control Maintenance section as shown above. The program can rebuild the entire Turbine Control Maintenance section, and build desktop Icons.
104 • Chapter 6 Configuration
GEH-6126
Rebuild Start Menu Dialog Box The Rebuild Start Menu dialog box appears when the program is started. There is an option to remove the existing definitions then rebuild. This option will delete all icons and folders in the Turbine Control Maintenance section, including any user created custom selections, then replace them with the TCI standard set. Do not use this option to retain user customization. The default option is not to remove the existing definitions. The second option adds the unit configuration icons to the desktop. The default is not to create desktop icons. Removal of desktop unit configuration icons can be done items through use of the Windows NT user interface features.
Stagelink Communication between the operator interface(s) (HMI) and the Mark V panel(s) is carried out by means of the control system’s Stage Link. In its simplest configuration, the Stage Link connects one Mark V turbine control panel to a single HMI (or node) across a single segment (see segment definition below). This communication topology may however be expanded to accommodate multiple HMIs and/or multiple panels. For example, a single operator interface can be configured to issue commands to and receive turbine data from up to eight Mark V gas/steam turbine controls. In addition, multiple HMIs may be attached to the Stage Link — each HMI communicating with multiple control panels. In this way, the Stage Link provides enhanced flexibility for establishing effective communications, which can be tailored to individual site needs. The Stage Link was designed specifically to address turbine control needs such as downloading or uploading software between the Mark V and the HMI, issuing commands, alarm management, and monitoring. Distributed control systems (DCS) interface to the Mark V via separate communication link(s) routed to the HMI, typically using a ModBus protocol. This chapter provides guidance and rules for successfully mapping Stage Links. Examples are used to help explain how certain topologies maximize communication link availability and/or enhance network distances.
GEH-6126
Chapter 6 Configuration • 105
Terms of Reference NODE: Any device connected to the Stage Link system that has a valid address; a TCP core, which for a Mark V is a core (communications processor), or a core (backup communications processor), and for a Mark V LM is a core (communications processor); or an HMI. Where a specific core (communications processor) is meant, like , it would be explicitly written instead of TCP. REPEATER: Electronic device that receives, amplifies and re-transmits Stage Link signals. The TCP cores and a hub are considered repeaters, HMI’s are not. HUB: For the Stage Link, the hub is a 4-port repeater (two coax ports and two fiber optic ports) for converting electrical signals to or from light pulses for fiber optic transmission or reception. It can also be used as a repeater to amplify coax signals. It is not considered a node because it does not have an address. SEGMENT: Any Stage Link section that joins two repeaters or connects one repeater to one or more high impedance devices and ends with a terminating resistor. A segment may have multiple taps for high impedance connections to HMI’s.
Stage Link Characteristics The Stage Link consists of a 2.5 MHz/2.5 Megabit-per-second ARCNET system that uses either fiber optic or standard RG-62 A/U copper cabling. Either type can be purchased with a variety of insulation systems such as flame retardant Teflon or high density polyethylene. In applications that must meet IEC codes, GE INDUSTRIAL SYSTEMS recommends using armored co-axial cable. These cable types have a metal sheath outer layer that functions as both a mechanical shield and as an electrical conductor that can alleviate lightning induced disturbances on short outdoor runs. This outer layer must be grounded at each building’s entrances and exits. Fiber optic cabling prevents electromagnetic interference and is often a better alternative for long outdoor segments (See the section on Fiber Optics).
General Specifications Local Area Network (LAN) ARCNET Type Communication Type Baseband Frequency/Speed 2.5 MHz/ 2.5Mbps Propagation Delay (Maximum) 31 micro seconds Maximum Network Length, 6,000 meters or based on Propagation Delay 19,680 feet Repeater Nodes TCP Other Repeaters Fiber optic Hubs High Impedance Nodes HMI The Mark V Panel
106 • Chapter 6 Configuration
GEH-6126
Within the Mark V panels, the ARCNET cable should be connected to, for Mark V the CTBA card, for Mark V LM AAHA board, which is located within the TCP communication processor(s). The CTBA or AAHA card communicates directly with the TCP communication processor(s). This data exchange is carried out through the one internal port of a three port repeater; the remaining two ports are for external customer use. Signals entering any one of these three legs are amplified and sent out through the other two. Therefore, a signal entering the first external port will be sent to TCP and re-transmitted on the second external port. Signals entering the internal port will be sent out on both external ports. Should the CTBA or AAHA card lose control power, a relay de-energizes and connects the two external ports. In this manner, all the other nodes on the Stage Link can continue to function as long as the topology is designed in accordance with the distance rules provided later in this Chapter.
The Primary Operator Interface, HMI The operator interface (or HMI) utilizes a single high impedance port that distributes signals in both directions on the Stage Link via a "T" type connector. The ARCNET card within the HMI receives data by tapping off a portion of signal transmitted on the Stage Link.
Cable Recommendations If the turbine control application requires a segment too long for a co-axial cable, a fiber optic cable should be used. For more on fiber optic installation, see the section on Fiber Optics.
Copper Cable Recommendations Indoor Cable RG-62 A/U Co-axial Cable Outdoor Cable Armored Co-axial or Tri-axial Cable Connector Type BNC Male (both ends) Fiber Optic Cabling Recommendations Cable Multi-mode with 62.5 micron core/120 micron cladding Connector Type ST bayonet Hub Power 120 VAC/60 HZ or 240 VAC/50 HZ (Customer supplied) Hub Configuration 2 Co-axial ports and 2 Fiber-optic ports (4 ST type connectors) Stage Link Rules
GEH-6126
Chapter 6 Configuration • 107
Summary of Topology Rules No Loops Maximum Number of Nodes Allowed 100 Maximum Number of HMIs in one 16 network Maximum Time Delay between any two 31 microseconds Nodes Both Ends Of The Stage Link Must Have A 93 ohm Terminating Impedance Every Node must have a unique network address Maximum Segment Lengths Co-ax Repeater To Repeater 609.6 meters Co-ax Repeater To Single HMI 609.6 meters Co-ax Repeater to More Than One HMI 304.8 meters HMI Between Two Repeaters 304.8 meters Maximum HMIs Per Segment 8 Fiber Optic Cable Hub To Hub (62.5/120 1825 meters micron fiber) Minimum cable length between HMIs 1.5 meters Segment Rules The cable and nodes between two repeaters is called a segment. The segment distance cannot exceed 609.6 meters for a coax connection. Fiber optic segments can go farther as described below. If a TCP loses power, total length becomes the sum of the two adjacent segments (see rule 8 below). TCP is either a Mark V LM core or a Mark V or core. < 609.6 meters, coax >
TCP
TCP
The segment between fiber optic repeaters can be as much as 1825 meters. The typical fiber optic hub is a 4 port repeater that contains two coax and two fiber optic ports. coax coax
active hub
< 1825 meters fiber optic cable >
active hub
coax coax
A two-node segment with one repeater and one high impedance node forming the end of the link may be 609.6 meters long. The HMI must have a cableterminating resistor (shown as R).
TCP
< 609.6 meters, coax >
R 93 ohms
HMI
108 • Chapter 6 Configuration
GEH-6126
No more than 8 HMI’s can be used in one segment. Each node must use a proper "T" connector in the cable to minimize reflection. The "T" is located on the card, and does not have a length of cable between the "T" and the card.
8 High Impedance Nodes Maximum
TCP HMI
HMI
HMI
HMI
R
HMI
HMI
High impedance nodes must be separated by a minimum of 1.5 meters of cable between the T’s. On a segment that has one TCP and two or more high impedance nodes, the maximum segment cable distance must be limited to 304.8 meters or less.
Less than 304.8 meters
TCP HMI
HMI
HMI
HMI
R HMI
HMI
The length of a segment with two TCP’s, and one to eight HMI’s, must be limited to 304.8 meters or less.
Less than 304.8 meters
TCP HMI
HMI
HMI
HMI
TCP HMI
Each TCP repeater has a relay that drops out when the power is off, connecting the two ports in order to maintain communication among the remaining nodes. This complicates the distances allowed between nodes because the segment formed by any sing le failure still must not exceed 609.6 meters. For segments containing HMIs, this distance drops to 304.8 meters.
Less than 304.8 meters and no more than eight HMIs TCP
TCP HMI
HMI
HMI
R HMI
HMI
HMI
Total Effective Distance Rules Always calculate the total "effective cable distance" between the two network nodes that have the longest effective distance. This is not always the nodes that are farthest apart physically. Each repeater has a delay equal to the delay in 25 meters of cable. Effective distance is calculated as follows: Copper (coax) cable length + (Fiber optic cable length * 1.25) + (number of repeaters * 25 meters) with all lengths in meters Total "effective cable distance" may not exceed 6000 meters.
GEH-6126
Chapter 6 Configuration • 109
The maximum 31 micro second propagation delay is approximately equal to the delay in 6000 meters of cable. As it is easier to calculate "effective cable distance" than it is to measure propagation delay, this approximation is used. The deciding factor is propagation delay, not total length. If questions arise about a particular application, it may be necessary to measure the propagation delay.
Redundant System Rules (Mark V Only) The two Stage Link systems, and , are not interconnected. Interconnections are not allowed as they will lower the communication interface reliability; that is, both networks could be brought down by a common failure such as a shorted coax or one node continuously transmitting. The and cables can be routed independently to minimize opportunities for a common failure. Typically unit control nodes are connected in a "daisy-chain" configuration. A cable from the Stage Link is routed from one physical end of the daisy chain to the central control room. The cable to the central control room is attached to the opposite side of the unit control string. In this way, a break in the cable or loss of power to a and/or leaves all other nodes accessible from some HMI in the central control room. On a system with a fiber optic link, the fiber optic repeater pair does not have bridging relays. Some customers may therefore prefer to use two links to the central control room, one from each end of the chain of unit controls as shown on the Figure of Example 2. In this example, one set of HMIs in the central control room is operational if any one of the four fiber optic active hubs fails.
110 • Chapter 6 Configuration
GEH-6126
Example 1: A Simple Plant Application
S1
R
3m HMI 1
HMI 2
267m
TCP
R HMI 4
S2
S3
30m
25m TCP
HMI 3
SEGMENTS
Cable length, meters Effective cable length Maximum Segment with 1 Node Failure Calculations
S1 S2 S3 270 30 55 3 s at 25 = 75, plus 625 Failure of Node:
30m
S4
270m TCP
TOTALS and COMMENTS S4 270
625 700, well below 6000 meter limit * All combined segments have HMIs, thus the maximum is 304.8 meters. 2 to HMI 4 the 1 to 2 segment. HMI 1 to 2 is close to the limit but should work if 1 fails, depending upon conditions.
1 2 3 Results in combined segment of: HMI1 to 1 2 2 to to 3 HMI 4 300 85 325* Total number of Nodes
GEH-6126
7, well below 100 maximum
Chapter 6 Configuration • 111
Example 2: Redundant Link Stage Application (MARK V ONLY) FOH
R HMI
FOH
R
HMI
HMI
HMI
FOH
FOH HMI
R
R
HMI - Communications Processor - Backup Communications Processor FOH - Fiber Optic Hub HMI - Operator Interface R - Terminating Resistor (93 ohms)
Example 3: Complex Plant Application S1
FOH1 HMI
R
S11
R
HMI
HMI
S2 600m Fiber Optic
FOH3 HMI S10 760m Fiber Optic
FOH2
FOH4
S3 3m
S9 3m
S4 TCP
S5 TCP
S6 TCP
HMI
S7 TCP
S8 TCP
TCP
TCP - Communications Processor FOH - Fiber Optic Hub HMI - Operator Interface R - Terminating Resistor (93 ohms)
112 • Chapter 6 Configuration
GEH-6126
SEGMENTS TOTAL S1 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11 Fiber cable length 600 760 1360 Co-ax cable length 6 3 30 30 180 30 150 3 6 438 Max. Effective cable (6 s at 25) + (4 FOH at 25) + {1.25 * (600 + 760)} + 438 2388, well within 6000 length meter maximum All are less than Maximum Segment Failure of Node: 609 or 304 with 1 Node Failure maximums. Calculations 1 2 3 4 5 6 Results in combined segment of: FOH 2 to 1 to 2 to 3 to 4 to 5 to 2 3 4 5 6 FOH 4 33 60 210 210 180 153 Total number of Nodes 15, much less than 100 maximum
Fiber Optics Fiber optics can be an effective substitute for copper coax cabling, especially in cases where longer distances are required, or electrical disturbances are a serious problem.
Advantages Larger diameter fiber extends this to 9000 feet (2,740 m) because the light transmitter gets more light into the fiber. If the plant is in a high lightning area, fiber optic segments can reduce the control outages caused by lightning. Grounding problems are avoided with optical cable. The ground potential can rise when there is a ground fault on transmission lines, caused by currents coming back to the generator neutral grounding point. Optical cable can be routed through switchyards and other electrically noisy areas with no interference. This can shorten the required runs and simplify the installation. With proper cable jacket materials it can be run direct buried, in trays, or in conduit, being careful not to drop below the bend radius. High quality optical fiber cable is light, tough, and easily pulled. The total cost of installation and maintenance of a fiber optic segment may be less than a coax segment.
GEH-6126
Chapter 6 Configuration • 113
Disadvantages Fiber optic links require powered hubs, with a reliable source of AC power. Failure of power to either hub causes a link failure. The effective distance of a fiber segment is 1.25 times the actual cable routing distance. The rule for Stage Link is that the total effective distance between the farthest apart devices must not exceed 20,000 feet. The extra equipment required for fiber links can increase maintenance. Cost, particularly for short runs, may be more for a fiber optic Stage Link segment. Inexpensive fiber optic cable is easily broken during installation and more prone to mechanical and performance degradation over time. The highest quality cable is recommended.
Review of Components This section will review all of the basic components of a fiber optic system, including cable, hubs, and connectors.
Basics The recommended fiber optic hub accepts two copper coax connections and two fiber optic links. A message coming in on any one of the four ports is repeated out the other three ports. Each fiber port consists of an outgoing fiber and an incoming fiber. The incoming signal is picked up with a phototransistor and converted to an electrical signal. The outgoing signal is converted from a train of electrical pulses to infrared light using a light emitting diode. On the fiber segment the optical output of one hub is connected through the fiber cable to the optical input of the other hub. Two fibers are needed for each segment. Multimode fiber, with a graded index of refraction core and an outer cladding, is recommended for the Stage Link (See Section X-4.). The amount of light that gets into the fiber depends on the brightness of the light source and the area of the lightcarrying portion of the fiber. The amount of light that comes out the other end depends on the clarity of the glass, the distribution of the index of refraction, the condition of the fiber, and the attenuation of connectors. The amount of electrical signal generated depends on the light coming out of the fiber and the area and sensitivity of the phototransistor. Tracking all this is done by using a power budget (Section X-10.4.). ## The fiber is protected with "buffering" which is the equivalent of insulation on metallic wires and protects the cable from excessive bends. Mechanical stress can damage fibers. One way to protect the fiber is to spiral it on the inside of a tube filled with gel. A more reliable system uses tight buffering with precision tensioned Kevlar fibers which carry the stress of pulling and vertical runs.
! Warning
114 • Chapter 6 Configuration
Never look directly into a fiber. Although most fiber links use light emitting diodes, which cannot damage the eyes, some longer fiber links use lasers, which can cause permanent damage to the eyes.
GEH-6126
Cable High quality fiber is recommended, especially for long distance links. It should be 62.5/125 optical cable as well. Cable attenuation should be between 3.0 and 3.3 dB/km at 850 nm, and around 1 to 1.2 dB/km at 1300 nm. The acrylate protective layer of the fiber should be specified with a 100 kpsi proof test and a 500-micrometer coating, rather than the 50 kpsi and 250-micrometer coating. Gel filled (or "loose tube") cables should not be used because of the special care required during installation, the difficulty of making terminations and problems of maintaining the gel seal, particularly in vertical runs where hydrostatic pressure can cause gel leakage. Use a high quality "break out" cable, which will make each fiber in itself sturdy cable that helps prevent too sharp bends. Combine the sub-cables with more strength and filler members to build up the cable for resisting mechanical stress and outside environment attack. In Section X-10.6, there are two sample specifications for fiber cable; one without armor and one with armor. Rodent damage is one of the major causes of failure of optical cable. If there is a possibility of wire insulation damage from rodents, the armored cable should be chosen. Otherwise, the armor is not recommended because it is heavier, has a larger bend radius, is more expensive, attracts lightning currents, and has lower impact and crush resistance. Particularly for underground runs, a direct lightning strike through the earth to the cable shield can cause explosive formation of steam in damp earth that can mechanically damage the cable. Test the optical characteristics of the cable with either an optical time domain reflectometer (OTDR) which can be provided by the manufacturer or with a simpler device that compares light levels at both ends of the cable. Four-fiber cables can be used to bring redundant communications to a central control room, or the extra fibers can be retained as spares. A less expensive option is to get the same cable with only two fibers.
Hubs The type of hub described throughout this chapter is built particularly for ARCNET communications and has the proper impedance to match the ARCNET line (93 ohms). For this reason, a fiber hub intended for ETHERNET, for example, will not function properly on the Stage Link. It consists of a power supply that runs from 120 or 220 volts AC 50 or 60 Hz. The two models can be converted by moving an internal jumper to accept the other voltage in case an error was made in ordering. The rack contains a power supply with sufficient power for 4 "expansion" cards. Each card has two copper coax ports and two fiber optic ports. A signal coming in on any port will be amplified and transmitted on the other three ports. Ordinarily only one card is used. If the system uses two fiber segments, a second hub is recommended to improve the communications availability. On the card, normally only one copper port and one fiber port are used for the same reason. The fiber optic ports in the hub’s card have ST connectors, which are the bayonet type. The light gray is the transmit port, the dark gray the receive port. In service a light gray connector always attaches to a dark gray one.
GEH-6126
Chapter 6 Configuration • 115
Connectors Connectors come in two forms, SMA and ST. The ST connectors give less problems in the field because they are bayonet type and not subject to over tightening. Over tightening the SMA connector can chip the glass fiber surface causing problems with reflections and loss of transmission. The bayonet type effectively uses a spring to push the two connecting fibers together with the proper force. Ceramic, glass filled plastic, or stainless steel are used to make the connectors. They come in three standard sizes to fit the different diameter fibers. Connectors for the 62.5/125-micron fiber are relatively easy to procure. The ceramic connectors can be precisely made and match the coefficient of expansion of glass.
System Considerations Having two HMIs in the central control room allows one to be down for maintenance while continuing control of the turbines from the control room from the remaining HMI. Similarly, having two fiber segments also allows for failure of one of the hubs, or the power to it. A failure of any one of the copper segments also retains control of all machines. Often only HMIs and possibly an (Historian) will be near the central control room. It will have reliable AC, and if that AC is gone, control from that location stops. Therefore, reliable AC in the control room is satisfactory for the hubs as well. Another system consideration is the optical power budget for the Stage Link. The total budget refers to the brightness of the light source divided by the sensitivity of the light receiver. These ratios of power are usually measured in dB to make calculations easier. The difference between the dB power of the source and the dB power of the receiver represents the total power budget. This must be compared to the link loss budget, which is made up of the loss in the connectors and optical cable. Installation of the fiber can decrease its performance over the new cable condition. The LED light source can get dimmer over time, the connections can get dirty, and the cable loss increase with aging, and the receiver can become less sensitive. For all these reasons there must be a margin between the available power budget and the link loss budget of a minimum of 3 dB. A good installation, including using correct parts and cabling, preparing connectors properly, and laying the cable so as to avoid sharp bends and hot locations will help keep availability. The hub manufacturer specifies one fiber segment to operate as far as 6000 feet with 62.5/125 microns fiber, and 9000 feet for the 100/140 microns fiber. These distance limitation have been incorporated into the Stage Link layout rules. It is recommended that fiber optic sections used in the Stage Link must not be longer than the specified 6,000 and 9,000 feet for the two fiber diameters. If the application significantly exceeds these distances another hub must be added to amplify the optical signals.
116 • Chapter 6 Configuration
GEH-6126
Installation Install the fiber optic cable in accordance with all local safety codes. Polyurethane and PVC are two possible options for cable materials that might meet local safety codes. See Section X-10.6. for some examples of specific cables. Proper planning is extremely important. Layout for the level of redundancy needed, cable routing distances, proper application of the distance rules, and procurement of excellent quality hubs, UPS systems, fiber cable, and connectors should all be included in planning the Stage Link. Install the system so that it will be strong enough for indoor and outdoor applications, including direct burial. Strictly adhere to the manufacturer’s recommendations on the minimum bend radius and maximum pulling force. Test the installed fiber to measure the losses caused by the cable and the connectors. A substantial measured power margin is the best proof of a high quality installation. The process of attaching the fiber connectors involves stripping the buffering from the fiber, inserting the end through the connector, and casting it into an epoxy or other plastic. This typically involves using a kit designed for the particular connector system. After the epoxy has hardened, the end of the fiber must be cut off, ground, and polished. The fiber hubs need reliable power, and should be placed in a location that will minimize the amount of movement they must endure, yet keep them accessible for maintenance.
GEH-6126
Chapter 6 Configuration • 117
Specifications The following sections provide specification information for Four-Fiber Cable with/without Armor, the Fiber Optic Hub, and Fiber Optic connectors.
Four Fiber Cable without Armor Optical Cable Corporation Part (or its equivalent):
RK920929-A
Fiber and buffering: Fiber Type: Core diameter: Cladding Diameter: Fiber proof test: Coating Diameter: Tight buffer diameter: Tight buffer material:
Multimode 62.5 microns 125 microns 100 kpsi 500 microns 900 microns Hard elastomeric; plastic not acceptable. 0.275 Attenuation
Numerical aperture: Attenuation & Bandwidth Bandwidth 850 nm 3.5 dB/km 160 MhzKm 1300 nm 1.3 dB/km 500 MhzKm Stripping ability: All layers can be easily removed with commercially available tools. Sub Cables: Four sub cables each with one fiber Fiber strength member: Aramid yarn Sub-cable diameter: 2.5 + - 0.125 mm Sub-cable jacket: Elastomeric Color-coded: Standard -- blue, orange, green, and brown Cable construction: Sub-cables with filler/strength member Jacket: Tight bound pressure extruded Flame retardant polyurethane Color: Black Cable weight: 65 kg/km Cable diameter: 8.0 mm Strength members: Aramid yarn with individual precise tensioning Conductivity: No electrical conductors may be used. Installation: Min bend radius: Max tensile load: Location: Pulling:
118 • Chapter 6 Configuration
16 cm (when pulling) 2200 N Aerial, direct burial, or duct Ordinary cable grips
GEH-6126
Operating: Min bend radius: Max tensile load: Temperature: Immersion: Storage: Test specification: Impact resistance: Crush resistance: Cyclic flexing:
8 cm 550 N -40°C to +85°C No damage -55°C to +85°C EIA-STD-RS-455 (or equivalent): 1500 impacts 2200 N/cm 2000 cycles
Four Fiber Cable with Armor Optical Cable Corporation Part (or equivalent): RK920929-A-CST Comprised of the same cable as described above, but surrounded with steel tape and polyethylene over jacket. Recommended vendor: Optical Cable Corporation, 5290 Concourse Drive, Roanoke VA 24019 (shipping); PO Box 11967, Roanoke VA 24022-1967 (mailing); 1 (800) 622-7711 or 1 (540) 265-0690. Fiber and buffering: Fiber Type: Multimode Core diameter: 62.5 microns Cladding Diameter: 125 microns Fiber proof test: 100 kpsi Coating Diameter: 500 microns Tight buffer diameter: 900 microns Tight buffer material: Hard elastomeric; plastic not acceptable. Numerical aperture: 0.275 Attenuation & Bandwidth Attenuation Bandwidth 850 nm 3.5 dB/km 160 MhzKm 1300 nm 1.3 dB/km 500 MhzKm Stripping ability: All layers easily removed with commercially available tools. Sub Cables: Four sub cables each with one fiber Fiber strength member: Aramid yarn Sub-cable diameter: 2.5 +- 0.125 mm Sub-cable jacket: Elastomeric Color-coded: Standard -- blue, orange, green, and brown
GEH-6126
Chapter 6 Configuration • 119
Cable construction: Jacket: Color: Armor: Armor overlap: Over jacket: Cable weight: Cable diameter: Strength members: Installation: Min bend radius: Max tensile load: Location: Pulling: Operating: Min bend radius: Max tensile load: Temperature: Immersion: Storage: Test specification: Impact resistance: Crush resistance:
120 • Chapter 6 Configuration
Sub-cables with filler/strength member Tight bound pressure extruded and flame retardant polyurethane Black Steel tape nominal 0.155 mm 2 mm, Bonded, corrugations in register. Polyethylene 1 to 1.5 mm thick 174 kg/km 13.0 mm Aramid yarn with individual precise tensioning 26 cm (when pulling) 2660 N Aerial, direct burial, or duct Ordinary cable grips 13 cm 532 N -40°C to +65°C No damage -55°C to +70°C EIA-STD-RS-455: (or equivalent) 50 impacts 440 N/cm
GEH-6126
Fiber Optic Hub The Hub Assembly is typically a metal box with a power supply and card slots. The Stage Link application typically calls for two hub assemblies each with one card. They can be ordered for table or flange mounting, and for 120 or 240 volt application. Moving an internal jumper can reconfigure for the other voltage if a mistake has been made. TABLE MOUNTED 120 vac 50/60 Hz 240 vac 50/60 Hz
MODHUB-16 EXP-CXS/FOG-ST MODHUB-16E EXP-CXS/FOG-ST
FLANGE MOUNTED MODHUB-16F EXP-CXS/FOG-ST MODHUB-16EF EXP-CXS/FOG-ST
MODHUB-16 can hold four cards, each with 4 ports for a total of 16 ports. This expansion module has two optical ports and two copper coax ports.
Fiber Optic Connectors 3M Connector model 6100 (or equivalent). This ST bayonet type zirconia connector is already filled with a thermoplastic material that is melted for the insertion of the fiber. The installation kit is model 6150A (or its equivalent). The filler is melted, fiber inserted, end cleaved and polished with only one paper. This connector makes fast and reliable connections and is gaining popularity. Thomas & Betts Connector model 91810-125-2P (or equivalent). ST connector of composite polymer, glass capillary, crimp and polish termination. Filler is a fast drying epoxy. Assembly Polishing Kit model 91000AKP (or equivalent) includes all parts needed and instructions. Amphenol Connector model 953-101-5010 (or equivalent). ST connector made of glass reinforced polymeric, ceramic ferrule, copper crimp ferrule, and PVC bend relief boot. Termination kit, model 927-100-5000 (or equivalent), includes stripper, curing oven, microscope, crimp tool, snips, polish board, training video. Add on termination kit has a cleave tool, polishing tool, cable preparation template and instructions. Filler is heat-cured epoxy.
Typical Stage Link Addresses The following table shows typical Stage Link addresses as assigned by the factory. Mark V LM: Any valid two digit hexadecimal number may be used for any Stage Link address. How to assign a new communication processor, Mark V LM Trainer, or operator interface processor node to an existing Stage Link is described in Chapter 3 of the Mark V LM Panel Manual (GEH-6353). Mark V: Any valid two digit hexadecimal number may be used for any Stage Link address except for processor addresses. For information about using a processor for Ethernet Communications with a DCS system, see GEH-6195C Chapter 11. How to assign a new communication processor, Mark V Trainer, or HMI processor node to an existing Stage Link is described in Chapter 5 of the Maintenance Manual, GEH-5980.
GEH-6126
Chapter 6 Configuration • 121
Address 01 02 . . . 0F 10
Description Addresses between 01 and the start of the processor addresses are not reserved.
8th processor
Reserved for communication with customer’s DCS via Ethernet
11 7th processor 12 6th processor 13 5th processor 14 4th processor 15 3rd processor 16 2nd processor 17 1st processor 18 8th HMI processor Reserved for HMI processor addresses. 19 7th HMI processor 1A 6th HMI processor 1B 5th HMI processor 1C 4th HMI processor 1D 3rd HMI processor 1E 2nd HMI processor 1F 1st HMI processor Addresses between 20 and the start of the Communication Core addresses are not reserved. . . Reserved for the Mark V Communication Core(s), TCP. . . EE . EF . FA 5th Mark V FB 4th Mark V FC 3rd Mark V FD 2nd Mark V FE 1st Mark V Stage Link Addresses
*Address 00 is reserved *Address FF is not reserved but typically not used
122 • Chapter 6 Configuration
GEH-6126
Control Hierarchy Overview Control Hierarchy is an optional scheme to define different control locations and pass control between these locations. Control locations are defined, and then different elements in the system are configured to only send commands if the current control location allows them to send commands. The HMI implements what commands are forwarded to the Mark V control panel through Control Hierarchy. This is a cooperative function of the HMI processor and the Mark V panel. The Mark V maintains a CONTROL LEVEL variable, and each HMI processor looks at the panel’s current control level to decide if that HMI is allowed to send command to the unit. Any element of the system that can initiate a command is called a CONTROL PORT. The database of an HMI server is an example of a control port, as is the MODBUS link and the ETHERNET link. Control Hierarchy is implemented by specifying which control ports are allowed to send commands to a unit based upon the unit’s current control location. Each unit has its own current control location, which is stored in the unit control.
Defining a Control Hierarchy The following steps are used to define a Control Hierarchy:
1) Decide how many control locations should exist.
2) Decide which control ports can send commands to the unit while it is in each control location.
3) Decide which ports are allowed to change the control location, based upon the current control location.
4) Create the HMI file F:\CTRL_LOC.DAT according to the decisions made in steps 1 - 3.
5) (Optional) Modify the HMI configuration to define an enumerated state table which defines the control locations.
6) Create the HMI displays for changing the control locations.
GEH-6126
Chapter 6 Configuration • 123
STEP 1: Decide how many control locations should exist.
The Control Location is held by the Mark V control panel, and will always be set to zero (0) when the control panel is reset. For that reason, Control Location zero (0) is usually defined as being "UNASSIGNED".
Control Location one (1) is often used to indicate control is isolated to the Backup Operator Interface (BOI). No control ports are given permission to send commands to the unit when the control location is in "BOI". This provides a form of panel-only control that is often used by maintenance.
The higher numbered control locations are typically used for control locations such as: "HMI", "MODBUS", and "ETHERNET". At the very extreme is the case where a different control location is defined for each HMI Server, and only that HMI Server is allowed to send commands.
There is a limit of 16 control locations, numbered from 0 to 15, allowed at any site.
STEP 2 - Decide which control ports can send commands to the unit while it is in each control location.
These decisions should be easy once you have defined the number of control levels needed. Some sites will opt for the ability for all control ports to send commands to units that are "UNASSIGNED", while other sites may decide that no commands may be sent to "UNASSIGNED" units, the control location must be changed to assign the unit to a control location first. If you define a control location of "BOI", do not let any control ports send commands to the unit while it is in "BOI" control.
An additional (optional) feature of the Control Hierarchy is the ability to block commands based upon a logic signal in the unit. If a LOCKOUT signal is defined for the unit, when the lockout signal is true only one specified command will be sent to the unit. That one command must have the ability to set the LOCKOUT signal to false. This LOCKOUT signal is sometimes used to block commands when the unit has been selected for CABLE REMOTE operation. If the logic is true in the unit that indicates that the unit is in CABLE REMOTE operation (usually L43CA) it will block all commands except the SC43 command, which is used to change from CABLE REMOTE back to AUTO.
124 • Chapter 6 Configuration
GEH-6126
Note It is usually not necessary to block HMI commands while operating the unit in CABLE REMOTE selection, but this can be done if desired. If commands are not disabled, the HMI will simply be a peer with the cable remote commands. Normal control hierarchy can take care of multiple HMI processors.
STEP 3 - Decide which ports are allowed to change the control location, based upon the current control location.
The next major decision is what control ports are allowed to change the control location from one value to another. This is done dependent upon the current control location.
A useful philosophy is that any control port that is "closer" to the turbine can take control if desired. This means that an HMI can take control away from a MODBUS link, or an Ethernet, and the BOI can take control away from any location.
Another useful philosophy is that control should be taken, not given away. This prevents the case of control being turned over to another location, but that location was not aware that it was expected to control the unit.
STEP 4 - Create the HMI file F:\CTRL_LOC.DAT according to the decisions made in steps 1 - 3.
Once the decisions are made on how the Control Hierarchy is to be implemented, the actual implementation is done by creating a file on each HMI processor. The file is the F:\CTRL_LOC.DAT file, and it is an ASCII text file that is edited using the standard text editor.
This data file defines a COMMAND table that indicates what control ports are allowed to forward commands and alarm commands to the unit based upon the unit’s current control location. This table will be different for HMI processors at different levels. (For example: The local HMI will have the table filled in differently than the remote HMI.)
The data file also defines a TRANSFER table that indicates what control ports are allowed to change the current control location based upon the unit’s current control location. This table will also be different for HMI processors at different levels.
If desired, the LOCKOUT signal and the one command that can be passed when the lockout signal is TRUE can be defined.
GEH-6126
Chapter 6 Configuration • 125
STEP 5 - (Optional) Modify the HMI configuration to define an enumerated state table, which defines the control locations.
The HMI processor uses a special signal in the Mark V control panel to hold the control location. The point used has the pointname of I_C_CTRL_1. This signal defaults to an "analog" signal scaled with a scale type of CNT15. When displayed, it will be shown as an integer.
Many sites prefer to change this point from an integer to an enumerated state point. This allows the displays to show the control locations as: "UNASSIGNED" - "BOI" - "HMI" - "MODBUS" - “ETHERNET"
instead of simply 0 - 1 - 2 - 3 - 4.
This can be done by editing the ENUMDATA.DAT file for the unit to define a new enumerated type that contains the strings for the control locations. Once this table has been defined the I_C_CTRL_1 signal can have its scale type changed from CNT15 to ENMnn, where "nn" is the number of the newly created control locations enumerated table. Once this is done, the displays will now show the control location using the enumerated string, not the integer value.
If your site is using synonyms, you might also wish to edit the SYNONYM.DAT file to include a synonym for the I_C_CTRL_1 point. STEP 6 - Create the HMI displays for changing the control locations. Any display that can send a command to the unit can have a command added to change the control locations. Add control targets to send the I_C_CTRL_1 point the value of the desired control location. The HMI will check the command against the TRANSFER table before sending the command to the unit.
126 • Chapter 6 Configuration
GEH-6126
; ; CTRL_LOC.DAT ; ; This file defines the parameters required to implement Control Hierarchy ; for the Mark V at Your Site ; ;-------------------------------------------------------------------------; ; The UNIT section defines which units the tables are being defined for. ; At some sites all units will share the same tables, and at other sites ; there may be different tables for each unit. ; ; The unit section is the keyword UNIT followed by the unit NAMES of the ; units that the following tables are valid for. UNIT T1 ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
; List of units that use the following tables.
The (optional) LOCKOUT section is used to block commands if the given logic signal is TRUE, passing only the given command. Needless to say, the one command that is passed needs to be able to change the state of the lockout logic. This does not block alarm management commands. The The the can
header line is simply the word "LOCKOUT". data line is the name of the logic signal, followed by the name of one command allowed when that logic signal is TRUE. No unit names be specified in the point name fields.
LOCKOUT L43CA
SC43
; If logic is true, only this one command is allowed ; Allow only SC43 (mode select) if on cable remote
The command table indicates which control ports are allowed to forward commands to the unit based upon the unit’s current control location. There can be at most 16 control locations, numbered 0 to 15. The panel will boot up in control location zero (0), which is usually "unassigned". The lines must be three "words", where the first is the current control location, the second is the list of which control ports can send commands, and the third is the list of which control ports can send alarm commands. A period "." can be used as a placeholder to give a column oriented table. The control ports are: I - The HMI keyboard/crt M - The MODBUS port E - The ETHERNET port COMMAND
; CTRL ; LOC ; --0 1 2
; This defines the command table.
CTRL CMDS ---I.. I.. ..E
ALRM CMDS ---I.. I.. ..E
; Control Location Description -----------------------------; Unassigned ; Local HMI ; Ethernet
;----------------------------------------------------------------------;The command locations for Black Point are: ; 0. Unassigned. Everyone has control and everyone can grab control. ; 1. Local HMI. The HMI in the control cab ; 2. DCS. The Ethernet port from both local HMI and MCR HMI ; When in unassigned, the HMIs have control capability and the DCS cannot ; send commands. When in local and MCR HMI, the DCS cannot send commands. ; Local and MCR HMIs are set up as peers and either location is equivalent. ; When in DCS mode, the local and MCR HMIs cannot send commands. ;-----------------------------------------------------------------------
; ; ; ;
The transfer table indicates which control ports are allowed to set a new control location based upon the unit’s current control location. The control port descriptions follow the same format (one word per location) as the command table above. TRANSFER
;
GEH-6126
CUR
; This table shows what transfers of control loc are allowed
---- DESIRED LOC -----
Chapter 6 Configuration • 127
; ;
LOC --0 1 2 3
0 --... I.. I.. ..E
1 --I.. ... I.. I.E
2 --I.E I.. I.. ...
;----------------------------------------------------------------------;The transfers of control location for Black Point are: ; ; When in unassigned, either HMI can take control or can pass it to the DCS. ; The DCS can also take control itself. ; ; When in either HMI location, each HMI can ask for the control location to ; be itself or it can give it to the DCS or it can relinquish it to ; unassigned. Having two separate HMIs like this means that, although ; operators can always have immediate control, they also have the ; opportunity to find out cooperatively who has control and kindly defer to ; the other location. A gentlemen’s agreement. ; ; When in DCS location, the DCS can transfer back to any of the other ; locations. The HMIs can take control to each other but they cannot make ; it unassigned directly (They can of course after first taking it to ; themselves) ;----------------------------------------------------------------------
CTRL_LOC.DAT Example
128 • Chapter 6 Configuration
GEH-6126
Time Zone Make Utility Program – TZ_MAKE This section describes F:\TIMEZONE.DAT, and the use of the TZ_MAKE.EXE utility program. TIMEZONE.DAT is used to define the UTC based times of transition to/from Standard Time from/to Daylight Time. Each transition definition also contains an entry containing the number of minutes to add to a UTC based timetag to arrive at LOCAL.
Note This is the opposite of many time correction schemes, most notably the TIME_ZONE_INFORMATION data structure defined by Windows NT. TIMEZONE.DAT can contain up to 100 entries. A minimum of 3 entries are required. This allows a span of 50 years to be used for UTC/LOCAL time conversion lookup.
The XT routines use the UTC based transition records to create internal LOCAL based lookup records. These LOCAL based lookup records allow XtLocalTimeToUtcTime () to determine whether a input local time is: 1.) Normal, 2.) Non-existent (Springtime) or 3.) Ambiguous (Fall). The UTC based transition records are used as straight lookup entries. UTC --> Local Time translation is always exact. No UTC time later than or equal to the last transition record can be used. TZ_MAKE.EXE is a utility program that can make TIMEZONE.DAT (or a file by any other name). It is a rule-based program that calculates past and future date/times for transition to/from Standard Time from/to Daylight Time. It generates entries starting 5 years in front of the year in which it is run, and generates 100 entries. For example, if TZ_MAKE is run in 1996, it will generate entries spanning from 1991 through 2040 inclusive. By default, TZ_MAKE uses the Windows NT GetTimeZoneInformation() routine to obtain the PC site local timezone information. Optionally, the user can define a "TZ" variable to define the rules used to calculate Standard/Daylight transition date. The form of this TZ definition is based on QNX/UNIX timezone rules. (Julian date formats are not supported however.) Note The resulting TIMEZONE.DAT file may require editing if local laws change the actual transition times normally used by a given locale. The format for entries in TIMEZONE.DAT was selected to allow grafting to F:\TIMESYNC.DAT used for Mark timesync TZ_MAKE Usage: D:>\TZ_MAKE outputdatafile-name ["TZ="] Where: output-datafile-name is the name of the time correction file to generate. TZ= is used to define the rules on daylight to standard time transitions. If TZ= is specified, it must be enclosed in quotes (") If TZ= argument is omitted, local Windows NT timezone rules are used. takes the following form (Spaces are for clarity only): offset dst offset, rule
std
std, dst are strings containing 3 or more characters and spaces. These are the names corresponding to Standard Time and Daylight Time respectively. offset takes the form HH[:MM[:SS]], optionally preceded by "+" or "-"
GEH-6126
Chapter 6 Configuration • 129
NOTE ------> DIRECTION-->
These indicate the values to add to LOCAL time to arrive at Universal Time Coordinated (UTC).
"-" indicates the local area is East of the Prime Meridian. "+" indicates the local area is West of the Prime Meridian. rule
takes the form of: date/time,date/time
Where the first date/time defines the transition from Standard Time to Daylight Time, and the second date/time defines the transition from Daylight Time to Standard Time. date
is specified in the following form:
Mm.n.d The d’th day (0 <= d <= 6) of week n in the month of m. (1 <= n <= 5) and (1 <= m <= 12). d=0 means Sunday. n=5 means the last d-day of the month. time takes the form HH[:MM[:SS] as above, but may not have "+" or "-" specified in front of HH. Example definition for Eastern Timezone of the U.S.A. TZ_MAKE filename.dat "TZ=EST5EDT4,M4.1.0/02:00:00,M10.5.0/02:00:00"
This example shows that Eastern Standard Time is 5 hours earlier than UTC, and that Eastern Daylight Time is 4 hours earlier than UTC. Daylight Time begins on the first Sunday in April at 02:00:00. Standard Time begins on the last Sunday in April at 02:00:00. Below is an abbreviated sample output. This example used the "TZ=" construct to define the transitions for Central Time USA.
130 • Chapter 6 Configuration
GEH-6126
; ; TZ_MAKE Generated File. ; ; This file was created on: 20-NOV-1996 20:06:32 (UTC) ; ; NOTE: This file was created using a day-of-week and week-of-month ; algorithm. This file may require editing if local laws ; caused changes in actual standard/daylight transition dates. ; ; The TZ argument used to create this text file was: ; ; "TZ=Central Standard Time6Central Daylight Time5,M4.1.0/2,M10.5.0/2" ; ; Standard Time Name: Central Standard Time ; Standard Time is entered on the last Sunday in October ; at 02:00:00 (Local Time) ; ; ; Daylight Time Name: Central Daylight Time ; Daylight Time is entered on the first Sunday in April ; at 02:00:00 (Local Time) ; ;---------------------------------------------------------------------; ; Time Offset Definition Table. Each entry defines number of minutes ; correction to use when Universal Time Coordinated (UTC) crosses: ; ; -----------UTC---------Minutes Correction to LOCAL Time TIME_OFFSET 07-APR-1991 08:00:00.000 -300 TIME_OFFSET 27-OCT-1991 07:00:00.000 -360 TIME_OFFSET 05-APR-1992 08:00:00.000 -300 TIME_OFFSET 25-OCT-1992 07:00:00.000 -360 TIME_OFFSET 04-APR-1993 08:00:00.000 -300 TIME_OFFSET 31-OCT-1993 07:00:00.000 -360 TIME_OFFSET 03-APR-1994 08:00:00.000 -300 TIME_OFFSET 30-OCT-1994 07:00:00.000 -360 TIME_OFFSET 02-APR-1995 08:00:00.000 -300 TIME_OFFSET 29-OCT-1995 07:00:00.000 -360 TIME_OFFSET 07-APR-1996 08:00:00.000 -300 TIME_OFFSET 27-OCT-1996 07:00:00.000 -360 TIME_OFFSET 06-APR-1997 08:00:00.000 -300 TIME_OFFSET 26-OCT-1997 07:00:00.000 -360 TIME_OFFSET 05-APR-1998 08:00:00.000 -300 TIME_OFFSET 25-OCT-1998 07:00:00.000 -360 TIME_OFFSET 04-APR-1999 08:00:00.000 -300 TIME_OFFSET 31-OCT-1999 07:00:00.000 -360 TIME_OFFSET 02-APR-2000 08:00:00.000 -300 TIME_OFFSET 29-OCT-2000 07:00:00.000 -360 TIME_OFFSET 08-APR-2001 08:00:00.000 -300 TIME_OFFSET 28-OCT-2001 07:00:00.000 -360
GEH-6126
Chapter 6 Configuration • 131
TCI Control Panel Applet The Turbine Controls Interface (TCI) Control Panel Applet allows you to adjust parameters used by the Turbine Applications. Incorrect values in some of these entries can cause the Turbine Applications to not work correctly. They will need to be corrected before the system will function correctly. Most of the changes will not take affect until the system is rebooted or the correct services are stopped and restarted.
Auto Login Auto Login causes the computer to login as the defined user when it is rebooted or when the current user logs off. To override the auto login when it is enabled, upon reboot hold the shift key down after the desktop background appears. Disabled/Enabled - If disabled is selected, the computer will not try to auto login the user. If enabled is selected, the computer will try to automatically login the user defined below. Username - This is the user name used to login if auto login is enabled. Domain - This is the domain used by the login if auto login is enabled. This is usually the computer name assigned to this computer. Password - This is the password used by the login if auto login is enabled. Password Verify - This entry must match the entry in Password. If they do not match, you will get a warning and be asked to enter them again.
ARCNET This tab allows you to set the parameters the ARCNET driver will use to talk to the ARCNET card. The jumpers on the card must be set to match these parameters for the ARCNET driver to work. Base IO Address - This is the IO Address the ARCNET card is set to. Base Memory Address - This is the Memory Address the ARCNET card is set to. Interrupt Number - This is the Interrupt number the ARCNET card is set to. ARCNET Link Address - This is the address of the ARCNET card on the ARCNET network. All cards on the network must have a unique address.
132 • Chapter 6 Configuration
GEH-6126
Site This tab allows you to set the default Site parameters for the Turbine Control Interface (TCI), On Site Monitor (OSM), Cimplicity Bridge for Mark V (CBV), or Historian (HST). Site Directory - This is the directory that all the site information will be located in. Default Scale - This is the default scale that will be used to display information. This can be set to any scale that is defined in the data dictionary.
Time Sync This tab allows you to set the type of time synchronization hardware on this Turbine Control Interface. Each individual application will have its own configuration information. Time Acquisition Hardware - This allows you to select the type of time synchronization hardware to use. None - This computer will not be a time master. Low Resolution - This computer will be a time master using the internal PC clock. High Resolution - This computer will be a time master using a high-resolution time board. This option will only be available if a high-resolution time board was installed when the Turbine Product was setup. High Resolution Time Card - This allows you to set the parameters for the highresolution time board. This section will only be available if a high-resolution time board was installed when the Turbine Product was setup and High Resolution is selected in section 1 above. Base IO Address - This is the base IO address set on the time card. Card Type - This is the type of high-resolution card installed.
TCI Alarm and Event Logger The Alarm and Event Logger program logs incoming alarm and event messages from units on a predefined printer attached to the computer running the TCI software. The Alarm Logger program runs automatically and requires very little system setup. Once the Alarm Logger is running, the logger control dialog box (logger.exe) can be used to control the logging of specific items from the various units attached to the system. The Alarm and Event Logger program requires that the following items be set up as part of the TCI software configuration: A Windows NT print queue must be named "Alarm Printer" using the Print Manager. This queue will receive all of the alarm and event log messages. The queue should generally be associated with a line-printing device such as a dot matrix printer rather than a page-printing device such as a laser printer. This allows the alarm and event records to be examined as they are received and printed.
GEH-6126
Chapter 6 Configuration • 133
The printer must be configured with a small font to allow printing alarm and event messages on a single line. Alarm messages can be up to 90 characters wide, event messages up to 140 characters wide. A font pitch of 15 characters per inch on 8.5inch wide paper will allow all alarm messages to be printed on a single line, and all but the widest event messages to be printer on a single line. This should be configured as the default font size on the alarm and event-logging printer. Once these two items are taken care of, the Alarm and Event Logger will log alarm and event messages to the queue named Alarm Printer as they are received, as filtered by the Logger Control dialog box.
CIMPLICITY Project Introduction The Signal Manager is a utility program for configuring CIMPLICITY points and alarms for Mark V Turbine controllers. It can also be used to view the attributes of signals in the Control Signal Database (CSDB). The program can be found on the HMI in G:\EXEC\CSDBUtil.EXE. The TCI service must be running before using this program since it accesses data from each unit’s Data Dictionary, which is built and maintained by the TCI service.
Setup To enable Mark V alarms in CIMPLICITY, the External Alarm Manager project option must be selected and to enable Mark V signal data the Mark V+ Communications protocol must be selected. After creating a new CIMPLICITY project, a CIMPLICITY Port for the Mark V+ Communications protocol must be configured before Mark V signals can be imported into the project. See figure below.
See also the CIMPLICITY Base System User’s Manual GFK-1180 for more information on creating projects and configuring ports.
134 • Chapter 6 Configuration
GEH-6126
When the Signal Manager imports Mark V signals into CIMPLICITY any needed CIMPLICITY devices and resources are also configured if they are not already present. For example when importing signals for unit T1, the program will configure a CIMPLICITY device called T1 and a CIMPLICITY resource called T1. For each device configured by the program, three virtual points needed by the MARK V_RP program are also configured. If the device were called T1 then these would be the virtual points created: T1_TIME – contains the unit’s current time T1_DATE – contains the unit’s current date T1_VALID – Boolean indicating if the HMI is currently communicating with the unit
Signals The program displays data from the Data Dictionary, which describes the unit’s CSDB. Each row of the display shows information about a signal, divided into columns. Each column shows a signal attribute, e.g. Name, Engineering Units etc. The display is a standard Windows List Control and as such will support the expected user interface commands for selecting items, sorting rows and sizing columns. The columns that are displayed can be configured by the user, the following attributes are available for display: Name – the signal’s name Access – read /write Cim Type – the CIMPLICITY point type that corresponds to this signal Description – a description of the signal Eng. Units – Engineering Units Flags – signal attributes (e.g. alarm, command, permanent) High Limit – the high limit for the signal’s value Low Limit – the low limit for the signals value Offset – the offset into the CSDB where this signal is located Precision – numeric precision for display of the signal’s value Scale Code – scale code for engineering unit conversion Synonym – optionally specified synonym for this signal Type – data type for this signal Value – the signal’s current value
GEH-6126
Chapter 6 Configuration • 135
Alarms The Signal Manager can be used to configure CIMPLICITY alarms for Mark V, Mark V LM and Mark VI turbine controllers. It can also be used to configure alarms for an EX2000 exciter. The CIMPLICITY alarms for turbine controllers are only placeholders and will be given the appropriate parameters at run time when they occur. Process alarms are configured with an alarm id of “P” where n is the drop number reported by the controller, likewise diagnostic alarms are configured as “D”. CIMPLICITY alarms are also used for not only for turbine alarms but for hold list entries, sequence of events and digital events as well. An alarm ID of “HOLD” is configured for hold list points. An alarm ID of “SOE” is configured for sequence of events. An alarm ID of “EVENT” is configured for digital events. These CIMPLICITY alarms are only placeholders and will be generated multiple times at runtime with different parameters for each instance. When the Signal Manager configures alarms it will also configure alarm classes if needed. If a needed alarm class is not configured, it will be added to the CIMPLICITY configuration. If the alarm class is already configured, the existing alarm class definition will be used. These are the alarm classes used: PRC – process alarms DIAG – diagnostic alarms HOLD – hold list entries SOE – sequence of events EVENT – digital events EX2K – exciter alarms Exciter alarms are configured from information contained in the file F:\EX2000.DAT. This information is specific to the EX2000 exciter and represents interpretations of the fault codes generated by the EX2000 exciter. The exciter alarms are not place holders and are configured with all parameters fully defined.
Importing Signals When the Signal Manager is started, an empty list is displayed. To populate the list with signals select New from the File menu. A dialog is displayed allowing the user to specify which signals to fetch from the Data Dictionary. The desired unit should be chosen from the displayed list of units. The user can optionally provide a signal name with wild cards to filter the signals retrieved from the Data Dictionary. The wild card characters supported are the asterisk (*) which matches zero or more occurrences of any character, and the question mark (?) which matches zero or one occurrence of any character. The displayed check boxes can be used to filter the signals by type. Putting a check mark in a box will allow signals of the corresponding type to pass through the filter.
136 • Chapter 6 Configuration
GEH-6126
To import signals into CIMPLICITY, select the desired signals from the displayed list (to select all the signals in the display choose Select All from the Edit menu) and choose Import from the Action menu. A dialog is then displayed allowing the user to select the .GEF file for the desired CIMPLICITY project.
It is sometimes desirable to populate the CIMPLICITY point database with points from a set of screens. The Signal Manager’s displayed list of signals can be populated with the signals referenced in a set of screens. To invoke this function select Match from the Action menu. After the program has scanned all the screens, any points not found in the Data Dictionary are displayed. Some or all of the signals found can then be selected and imported into the CIMPLICITY point database.
GEH-6126
Chapter 6 Configuration • 137
Configuring Exciter Alarms To configure alarms for Mark V controllers, select Alarms from the Action menu. The Signal Manager program will then configure process and diagnostic alarms as well as alarms for Hold List, Sequence of Events and Digital Events. To configure alarms for EX2000 exciters select EX2000 Alarms from the Action menu. The program will then configure exciter alarms as defined in F:\EX2000.DAT. A dialog is then displayed asking the user to specify one or more CIMPLICITY points that contain the exciter fault codes. The exciter core that generates the fault code must also be specified. After providing the point name and exciter core, select Configure. The program will then run some command line utilities and display their output in a scrolling text box. These command line utilities configure events and actions in CIMPLICITY that will generate alarms when the value of the fault code CIMLICITY point changes value. After these events and actions are configured the user can then specify another exciter fault code point or select Done.
138 • Chapter 6 Configuration
GEH-6126
Unit Configuration Unit Configuration Overview The TCI service uses the information contained in the F: Drive to determine which units to communicate with, how those units are controlled, what data is to be collected and how it is displayed. The configuration files require modification to configure and control the units.
! Caution
Only qualified personnel should make changes to the configuration files. Any changes can have an impact on the unit control!
Modifications include modifying the files at the top level of F: to configure the site parameters and turbine control units the HMI will be communicating with. Next the files of each unit configuration must be set up, modified, and tuned to give the turbine control its desired control function and performance through the configuration parameters. This accomplished by both directly editing the files and employing the various HMI turbine tools (programs) to build the unit Control System Database (CSDB). The unit CSDB must be downloaded to the turbine control and the controller must be reinitialized with the new CSDB. Lastly, the unit configuration directories on each HMI must be kept in synchronization with those on the other HMIs. This is best accomplished by designating one HMI as the configuration master. The unit configuration files from this HMI can be copied from the configuration master to the other HMIs via network or diskette.
! Caution
GEH-6126
Failure to have the unit configuration files match those, which have been downloaded to the unit, could result in erroneous data being displayed on the HMI.
Chapter 6 Configuration • 139
HMI F: \ Drive Configuration Files When the TCI service starts up, it will use a pseudo F: drive if one has been defined. Otherwise, it creates a pseudo F: drive at the location specified by the TCI Control Panel Applet in the TCI Site tab. This is usually the C:\SITE directory. Users must configure three files in this directory: CONFIG.DAT
– This file is shown and described below.
TIMEZONE.DAT
– This file is shown and described in the TZ_MAKE section.
TIMESYNC.DAT
– This file is shown and described in the Time Synchronization
section. These files govern which units the HMI is able to communicate with and how time synchronization is handled. The F:\CONFIG.DAT file, shown below, is a text file that contains information about the units with which the HMI can communicate. The lines in this file that begin with a semi-colon ( ; ) are comments which do not affect operation and are ignored by HMI programs that use the file.
140 • Chapter 6 Configuration
GEH-6126
; F:\CONFIG.DAT - HMI CONFIGURATION FILE ; SITENAME Power Station ; ; ;-----------------------------------------------------------------; ; Section 2 - UNIT DATA DEFINITION ; ; This section defines the unit numbers, unit names, the path to the ; directory that contains the unit information for each Mark V control ; panel this is to communicate with, and the unit type (when ; the Plant Load Control Option is enabled). Each line contains the ; unit number (decimal), the unit name (2 char max), the path to the ; unit configuration data (64 char max), and the unit type (decimal). ; Valid unit types are: (0 = Mark V), (1 = This ), (2 = Mark V LM). ; Theunit numbers must be in order starting with one (1), if a unit ; number is repeated, the last entry wins. ; ; ; UNIT UNIT PATH TO UNIT UNIT ; NUMBER NAME CONFIGURATION DATA TYPE ; ----------------------------UNIT_DATA 1 T1 F:\UNIT1 0 2 T2 F:\UNIT2 2 ; ; ; ;--------------------------------------------------------------------; ; Section 3 - NETWORK (STAGE LINK) CONFIGURATION DEFINITION ; ; This section defines the network configuration for each node this is ; to communicate with. Each line contains the unit number (decimal), ; processor ("C" or "D"), the network number (decimal value), and the ; Stage Link ID (hexadecimal value). ; ; STAGE ; NETWORK LINK ; UNIT# PROC NUMBER ID ; -------- ------- ----NETWORK_DATA 1 C 1 FF 2 R 1 FC ; ; ; ;-----------------------------------------------------------------; ; Section 4 - OPTION DEFINITION ; ;This section defines which options will be enabled each time the is ; re-booted or started up. The enabling of options during boot-up/re-boot ; is reported in G:\LOG\STARTUP.LOG. ; OPTIONS ; EPA_LOG =YES ; ;---------------------------------------------------------------------; End of file. Please do not remove this line.
GEH-6126
Chapter 6 Configuration • 141
The section of the file shown in the example defines the unit information for the HMI. Information in the UNIT_DATA section denotes the unit(s) with which an HMI can communicate. Each line in the section represents a particular unit; that is, the unit number, the unit name, and the path to the unit’s configuration information (its unit-specific directory). This information is necessary to determine where the unitspecific files for a particular unit reside. The cautions specified in the comment should be observed when making modifications to this section, and the TCI service must be restarted in order for the changes to take effect.
HMI Unit-Specific Directory Each Mark V control panel assigned to communicate with an HMI has a unit-specific directory and subdirectory on the hard disk of the HMI. These directories have names, which refer 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 the HMI communicates with is usually named F:\UNIT1; its subdirectory is F:\UNIT1\PROM. Subsequent unit-specific directories and their subdirectories would be 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 the following groups: • Assignment files • Data Dictionary files • I/O Configuration Constant files • Table Files • CSP segment files. These five groups of files are detailed below.
Unit-Specific Assignment Files Assignment files, while not downloaded to a Mark V control panel’s processors, 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 unitspecific 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 American Standard Code for Information Interchange (ASCII) 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 control panel, they must be assigned a control signal database pointname and a scale type. I/O devices connected to a Mark V control panel 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. A Mark V control panel’s processors have 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 for the point, and the scale code for the point. These definitions are made in one of the following assignment files:
142 • Chapter 6 Configuration
GEH-6126
FACTORY.ASG, ALLOCSSP.ASG, or SITE.ASG. 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). GE or GEPS’s business associates assign control signal database pointnames and scale types to spare memory locations in FACTORY.ASG. This file may be altered to accommodate customization of the Control Sequence Program for a particular application. The only types of assignments not made in FACTORY.ASG are for additional I/O, spare double-word variables, and spare alarm logic points. Spare double-word variables and alarm logic points which are required for a particular application are assigned pointnames and scale types in ALLOCSSP.ASG (which stands for ALLOCation of Structured Software Points). Both factory (GE and GEPS Business Associates) and field/site personnel can make assignments for these two types of points in ALLOCSSP.ASG. Customer and/or GEPS/Business Associate field personnel are to make assignments of signal pointnames and scale types to spare control signal database memory locations in SITE.ASG for points other than I/O, double-word variables, and alarm logic points.
Unit-Specific 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 (type/units, messages, etc.). The primary unit Data Dictionary file, UNITDATA.DAT, can be created on an HMI in the unitspecific directory. Assignment files and template files (see below and section 3-1.1.) are used in the creation of UNITDATA.DAT. Many configuration programs on an HMI 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 executed 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: 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 executed. 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 executed. Each time DDLOCATE is executed, 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 more details see the section on MK5MAKE.BAT.
GEH-6126
Chapter 6 Configuration • 143
Other Data Dictionary files that must be present in the unit-specific directory for proper operation include: • ALARM.DAT Process and Diagnostic Alarm messages (Max-case) • ENUMDATA.DAT Display messages for Enumerated Data types • ENGLISH.DAT Scale code information • METRIC.DAT Scale code information
The following unit-specific Data Dictionary files are optional and not required for proper operation of an HMI:
• LONGNAME.DAT CSDB Pointname Descriptions • SYNONYM.DAT Site-specific CSDB Pointname Synonyms
Unit-specific Data Dictionary files are not downloaded to a Mark V control panel’s processors, 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 programs on the HMI require information from UNITDATA.DAT.
Unit-Specific 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 control panel. I/O devices include pressure transducers, temperature switches, electro-hydraulic servo-valves, position transducers or reactors, thermocouples, RTDs, etc.. Many of these I/O devices, being of the same type, 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 can be used to appropriately scale the input signals from various types of thermocouples. Milliamp transducers come in several output ranges: 4-20 mA, 0-1 mA, 0-10 mA, etc.. More than one type of milliamp transducer may be used on a unit or its auxiliaries. I/O Configuration Constants are used to scale the input for use in controlling, protecting, or monitoring the unit. I/O Configuration Constants are initially contained in the I/O configuration files in the unit-specific directory. The files are:IOCFG_Q.DAT, IOCFG_C.DAT, and IOCFG_D.DAT. All three files will be present in the unit-specific directory for each Mark V control panel that is to communicate with the HMI, even if the control panel 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 PROM directory for the unit. 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 may be downloaded to a Mark V control panel’s processor(s) without any intermediate steps (such as compiling).
144 • Chapter 6 Configuration
GEH-6126
Unit-Specific Table Files The majority of unit-specific configuration files are Table Files. These files contain tabular listings of control signal database pointnames and information about their type, use, value, etc. Table Files contain information in an ASCII text format which, when compiled and downloaded, is used by functions such as the Control Sequence Program and the loggers of the Mark V control panel’s processors. Figure 3-3 shows a list of Table Files and a brief description of their contents. Several of the source Table Files are dummy files and contain no information. They have been 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: TABLE_C ALL
Using the Table Compiler, information in the source Table Files will be converted into binary format in files with the same filename but with a .AP1 filename extension. (For example, CONST_Q.SRC would be 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 control signal database pointnames are downloaded to the Mark V control panel processors, the Table Compiler finds the software signal pointname in UNITDATA.DAT, and uses its memory location/address and scale code and point type when creating the downloadable Table Files from the information in the source Table Files (see example below).
GEH-6126
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 (Mark V)
HIST_Q.SRC
A list of pointnames included in the Trip History log (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
Chapter 6 Configuration • 145
Unit-Specific CSP Segment Files A CSP segment is an ASCII text file, which contains information such as Control Blocks, parameters, comments, and/or relay ladder diagram sequencing. The Control Sequence Program for a unit is made up of at least two segments — one for and one for . CSP segments can be executed 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/or must be executed 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 Turbine Control Maintenance section on the HMI). Refer to the section for the Control Sequence Editor. 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 (eight characters max) but must have an .SRC filename extension. Prior to downloading to a Mark V control panel, the CSP must be converted to binary (AP1) format using the Control Sequence Compiler, or CSP Compiler. The CSP Compiler uses information from UNITDATA.DAT, BBL 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 (SEQ.AP1 for Mark V LM). The CSP Compiler can be executed from the Turbine Control Maintenance section of an HMI or at the command line of the unit-specific directory with the COMP_SEQ command. MSTR_SEQ.CFG (a text file) contains two sections, which define the names of CSP segment files, which are compiled for ’s CSP and ’s CSP. In addition, it defines the rates and the offsets/skews as well as the order in which CSP segments are compiled and executed. (The first segment file specified will be executed first, the second segment file specified will be executed next, the third segment file specified will be executed next, and so on.) See the section on MSTR_SEQ.CFG for more information.
CSP segments are initially created using BBLs , 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 of segments per and that can be compiled is eight (16 for Mark V LM).
Compiling Unit-Specific Configuration Files The unit-specific Table and CSP files must be converted to binary format prior to downloading to the processors in a Mark V control panel. This is accomplished by using the Table Compiler program directly or the MK5MAKE.BAT batch file which calls the Table Compiler program. Please refer to the sections on the Table Compiler and MK5MAKE for more details.
146 • Chapter 6 Configuration
GEH-6126
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 processors in the Mark V control panel using the EEPROM Downloader program. The EEPROM Downloader program, EEPROM, is available from the command line of an HMI. The EEPROM Downloader program will transfer unit configuration file information (sometimes known as EEPROM partitions or sections) from the HMI computer’s hard disk to controller. Please refer to the section on the EEPROM Downloader for more details.
Control Constants Special care must be exercised when modifying control constants in the CONST_Q.SRC file. These constants are downloaded to nonvolatile memory on the unit control. They are copied to RAM memory when the control is initialized and used during the execution of the CSP. 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 Control Constants display on an HMI. 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. For more information on the Control Constant Adjust Display, refer to its section in this manual. A feature of the Control Constants Adjust Display is the copy the Control Constant whose value was changed in RAM to the controller’s nonvolatile memory. By clicking on the target Storage Update and then clicking on the OK button in Execute Dialog Box, the current RAM value of every Control Constant will be copied to the processor’s nonvolatile 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 control panel 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 will cause 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 will assure the Control Constant Table File hexadecimal file, CONST_Q.DAT, will contain 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 unit control using the CONSTCHK program. Refer to its section for more details.
GEH-6126
Chapter 6 Configuration • 147
DABUILD DABUILD is a Mark V specific program that is used to configure 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). This program should only be run when directed as part of a PROM upgrade.
When an element in the Mark V control panel indicates a diagnostic alarm, it reports it through the use of a diagnostic alarm number. The HMI must be able to match that number to the diagnostic alarm text to be shown. This text information is read from the unit configuration directory ALARM.DAT file. This file 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. This file needs to be translated from the unit form to the HMI form, and that is what DABUILD does. 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 will provide a help screen. The output from this program will be a new version of the ALARMD.TPL file. The following screen 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>
148 • Chapter 6 Configuration
GEH-6126
DCBUILD1 DCBUILD1 is a command line configuration program that builds the list of available Diagnostic Counter Displays for a unit. It places the results into the DIAGC.DAT file in the unit configuration directory, where the Diagnostic Counter Display (DIAGC) expects to find it. Note This program is traditionally 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 cards in the Mark V or Mark V LM panel provide advanced diagnostic information upon request. The Diagnostic Counter Display (DIAGC) is the program that can poll the cards for this diagnostic information, and then format 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 unit, the list of available diagnostic displays may change, as the new PROMS may change the diagnostic information available from the card. DCBUILD1 uses the information in the PANEL.CFG file to determine the set of cards that exist in the panel, including the revision level of each card. It then reads the Card Library for the list of diagnostic displays that are available from each card 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 will provide a help screen.
GEH-6126
Chapter 6 Configuration • 149
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 card
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 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: - DIAGC.DAT
The data file DIAGC will read.
F:\UNIT2>
150 • Chapter 6 Configuration
GEH-6126
DDLOCATE DDLOCATE is a command line configuration program that is used to define (locate) signals in the Mark V or Mark V LM Control Signal DataBase (CSDB). This
program takes a list of the signals that are needed and will locate 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 control has a Control Signal DataBase (CSDB) which is the real time database used in the unit for controlling the turbine. All I/O signals are read and written from the CSDB, and all sequencing runs by reading and writing CSDB signals. When the panel is first created there are some "fixed" or "permanent" signals located in the CSDB. These signals will always exist, and can not 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 will be 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 turbine control, and can not be changed in the field. If DDLOCATE indicates that you have run out 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 (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) which indicate the signals that should be added to the CSDB. For each signal to be added, the type of signal that is required is used to determine which region of the CSDB will be 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 card. 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.
GEH-6126
Chapter 6 Configuration • 151
DDLOCATE is a command line utility, but is typically run through the use of 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 is run it creates a new CSDB layout from scratch; it is not used incrementally. (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 will be provided: 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>
Assign Files
152 • Chapter 6 Configuration
GEH-6126
The typical job uses four assignment files for the list of signals used. These include: 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 will be done. Refer to this for specific information. The basic formats 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 that the software signal must be mapped to. 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 (ENGLISH.DAT, METRIC.DAT, HARDWARE.DAT, and CUSTOM.DAT) files. 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 which region of the CSDB the signal should be stored in. (A list of the region types is included in the header of the SITE.ASG file.) The software types will be of the format "?TCsss". 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 which controller the signal should be defined in. The Mark V uses a "B" for a signal that must be in the (and optional ) controller, and a for a signal in the (and optional and ) controller. The Mark V LM only uses . The "sss" indicates a sub-class of signal, and these subclasses include:
- A local, non-voted signal
LS - A Logic State command (only valid for logic signals) PB - A Push Button command (only valid for logic signals) PUB - A private (local) unsigned byte (only valid for logic signals) AS - An Analog Setpoint (only valid for variable signals) CC - A Control Constant (only valid for variable signals)
GEH-6126
Chapter 6 Configuration • 153
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 shown in the example below: ;ARRAY ASSIGNMENT EXAMPLES ? * Name1,Name2,Name3,Name4 ? *4 Name1,Name2,Name3,Name4 ;Multi-line example ? * Name1,Name2,Name3,Name4,Name5,Name6, Name7,Name8,Name9
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, as long as the asterisk and the count are one "word". If the count is included, a warning will be 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, which indicates that another signal name will follow.
DDUTIL DDUTIL is a command line utility program that will check 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 were given the same name. It also has the ability to sort the UNITDATA.DAT file to put the signal names in alphabetic order.
Note The HMI does not care about the order of the signals in the UNITDATA.DAT file, the sorting is only to make it handy 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. 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 will scan 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. If any invalid characters are found in any of the numeric fields of the file, a warning will also be issued. If the SORT command line option is used, the original file will be copied to the file UNITDATA.BAK, and a new signal name sorted version of UNITDATA.DAT will be written. The sort will not be performed if there were any invalid entries found, but sorting can be done if there were duplicates found. DDUTIL is a command line utility run from the unit configuration directory. (It is run
as part of the standard MK5MAKE procedure.) If run with the "/?" command line parameter, a help screen will be provided. If no errors are found then no messages will be generated during the scanning process. If the SORT option was used, a message indicating that the file was sorted will be printed.
154 • Chapter 6 Configuration
GEH-6126
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 MK5MAKE is a batch file that contains the commands typically used when rebuilding the Control Signal DataBase (CSDB) layout for a Mark V or Mark V LM panel. 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 simply performs these steps in one command.
There are many steps in configuring a panel, and the MK5MAKE batch file helps simplify that task by running the various tools used to configure the unit in the correct order. MK5MAKE is typically run when signals are added to the unit, or parameters on the signals have been changed, such as its scale code. When run, MK5MAKE performs the following steps: 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
DDLOCATE
DDUTIL is run to validate the new layout, and is run such that it 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 run from the unit configuration directory.
Note MK5MAKE can take one optional command line parameter. This parameter is passed directly to the Table Compiler (TABLE_C). In the IDP Product, this was used to change the scale codes set from the default of ENGLISH to a user specified scale code set. In the HMI this is no longer required if the desired set is ENGLISH, METRIC, HARDWARE, or CUSTOM. The HMI version of the Table Compiler will scan those four scale code sets looking for the matching engineering units specified in the Table Compiler input file. MK5MAKE creates a log file that is basically the concatenation of the output from running each individual tool. This file is stored as the MK5MAKE.LOG file in the
unit configuration directory.
GEH-6126
Chapter 6 Configuration • 155
The following example demonstrates this batch file in operation: 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>
156 • Chapter 6 Configuration
GEH-6126
FMVID Overview This program is used only 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 a Mark V LM controller. The FMV ID table is used to prevent the unit from trying to run if the required Fuel Metering Valve linearazation table matching the valve in use has not been downloaded into the panel. Each Fuel Metering Valve (FMV) used in a Mark V LM must use the linearazation table that matches that particular valve. These linearazation tables are valve specific, with each serial numbered valve having its own table. Attempting to run the Mark V LM with a linearazation table that does not match the actual valve in use will cause unexpected variations in the fuel flow rate. To try and prevent these mismatches, each linearazation table has in its ID field the serial number of the valve that it is calibrated for. The Mark V LM control needs to match this ID to the actual valve in use, which is where FMVID comes in. FMVID is how you configure a panel to tell it what valve is actually being used. FMVID is used to display and configure the actual FMVs used in the panel. This information is stored in a special section of the panel’s non-volatile memory. This program reads and optionally writes this non-volatile memory in the Mark V LM control panel. 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 Linearazation 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 Mark V LM will not allow the unit to be started.
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 will display the FMV IDs stored in the unit.
If run with the /SET option, it will change 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=::
where is the FMV number, starting with the number one (1) for the first valve. The is the part number field, which is the part number for the valve. The field is the serial number as defined in the linearazation table for that particular valve.
GEH-6126
Chapter 6 Configuration • 157
Multiple /SET commands can be given in the FMVID command line. They will be processed from left to right. If a valve number is repeated, the last entry will be the one used. After all /SET commands have been processed, the non-volatile memory in the unit will be read and displayed, showing the results of the changes. If run with no parameters, or the parameter of "/?" it will display a help screen, as show in the example below: 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 C32465-B2, serial number 11. After the change is made the new configuration is shown. F:\UNIT1>
LDB2RAM Overview LDB2RAM is a dynamic configuration tool that allows an individual Linearazation
DataBase (LDB) table to be downloaded to the RAM of a Mark V LM. This allows for adjustment of the linearazation 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 will read the LDB tables from the LDB.AP1 unit configuration file and load those tables into RAM. The unit then uses these RAM based 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 the table is to recompile it and download the unit. On the next restart or power-up the new table will be used. If the table is ADJUSTABLE then 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 the RAM of the unit, where the
changes will take effect immediately. Since the LDB.AP1 file in the unit has not been changed by this process, restarting the unit will reload the original table into RAM. (The file on the HMI, however, will have to have the changes undone in order to prevent the changes from being downloaded during the next panel compile and download.) In order to be able to download an LDB table to RAM, the following conditions must be met:
158 • Chapter 6 Configuration
GEH-6126
•
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 between 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 unit configuration directory on the HMI. (You may wish to save a backup copy of this file to undo your changes in the future should that need arise.) Once the LDB table has been modified, it is downloaded using the LDB2RAM utility. LDB2RAM needs to know which unit to download, and it needs to know which table to download. The unit is specified using the "/UNIT=" qualifier. The table can be specified by using either the file name or the table number, through the use of either the "/FILE=" qualifier or the "/TABLE=" qualifier. The associated file is compiled and downloaded directly to the unit. If run with no command line values or with a command line parameter of "/?" a help screen will be provided, as seen in the example below. 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-6126
Chapter 6 Configuration • 159
LDBCHK Overview LDBCHK is a command line configuration utility that is used on a Mark V LM to determine if any of the Linearazation DataBase (LDB) tables are different in the unit’s RAM versus the unit’s LDB.AP1 configuration file. This will indicate if any changes were made using the LDB2RAM utility since the last panel reset or powerup. When a Mark V LM control is reset or powered up, it reads the LDB.AP1 configuration file and loads the LDB tables found into RAM. The panel then runs using these RAM resident tables. A utility program exists (LDB2RAM) that can dynamically change the contents of the RAM resident LDB tables. Use of the LDB2RAM program will result in the contents of the RAM and the contents of the configuration file being different. LDBCHK is a utility program that will outline the differences between the contents of the RAM and the LDB.AP1 file, giving a list of the changes that were made.
Operation LDBCHK is a command line utility program that is typically 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 will provide a help screen, as shown in the example below: 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>
ALARM_L Overview ALARM_L is a command line utility program that will generate a printable list of all
of the process alarms that a unit can generate, complete with the signal name and alarm text for each one. The resulting alarm list file (ALARM.LST) includes a warning section if there are any alarms defined that do not have any associated alarm text strings defined. ALARM_L was originally created in conjunction with the Backup Operator Interface
(BOI) because the BOI only indicated a process alarm’s drop number. The listing that ALARM_L created (the ALARM.LST file) was typically printed and hung on the door of the Mark V control. This provided 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 has also been 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.
160 • Chapter 6 Configuration
GEH-6126
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 handy during the unit configuration to catch any alarms that don’t have text strings defined for them yet.
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 shown in the example below: F:\UNIT1>alarm_l Loading data dictionary alarm.....576 alarm points loaded. F:\UNIT1> SAMPLE OUTPUT (ALARM.LST) DROP# | SIGNAL NAME | ALARM TEXT ------|--------------|---------------------------------------0 | L30DIAG | DIAGNOSTIC ALARM 1 | L30FORCED | FORCED LOGIC SIGNAL DETECTED 2 | L4ETR_FLT | PROTECTIVE MODULE ETR RELAY TROUBLE 3 | L86MP | MASTER PROTECTIVE STARTUP LOCKOUT 4 | L48 | TURBINE INCOMPLETE SEQUENCE 5 | L83HOST | OVERSPEED TEST MODE SELECTED - HP 6 | L83LOST | OVERSPEED TEST MODE SELECTED - LP 7 | L12H_P_ALM | PROTECTIVE MODULE HP OVERSPEED - SD 8 | L12L_P_ALM | PROTECTIVE MODULE LP OVERSPEED - SD 9 | L86MAN_SYNC | MANUAL SYNCHRONIZING LOCKOUT 10 | L86S | AUTO SYNCHRONIZING LOCKOUT
DMD2SRC Overview The Demand to Source Conversion Program, DM22SRC.EXE, converts the Demand Display binary storage file to a text format for easy editing by hand. The program has a reverse option, which converts the text source file back to a binary storage file. It is a command line program, not a Windows program. Refer to a description of the Demand Display program later in this document. Refer to the section on the Demand Display for a description of the Demand Display binary file, *.DM2. The conversion program converts the binary file to a text file. The text file will have the same name as the binary file, but with a *.SRC extension. An explanation of the file contents is included in this sample file and all *.SRC files produced by this program.
GEH-6126
Chapter 6 Configuration • 161
; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ; ;
The name of Demand Display file being read is DEMO.DM2. The Demand Display file is being read on Thu Nov 20 11:31:00 1997
+-----------------------------------------------------------------+ |UNIT_NUMBER TITLE "" TYPE "<display type>" | +-----------------------------------------------------------------+ DISPLAY RECORD: One of the displays defined. start in the first column. <num> is the decimal unit number. in the F:\CONFIG.DAT file.<br />
<br />
These must<br />
<br />
This must match the description<br />
<br />
<title> is the title of the display.<br />
<br />
(Limited to 25 characters.)<br />
<br />
<display type > is the type of the display. Only two types are allowed: Dictionary and Point +------------------------------------------------------------------+ | P "unit" "pointname" +------------------------------------------------------------------+<br />
<br />
|<br />
<br />
POINT RECORD: One of the points shown on the display. These lines must be indented under the DISPLAY RECORD. Point records are valid only for Point type displays. (see DISPLAY RECORD) <unit> is the NAME of the unit. If an empty string is supplied, the currently selected unit is used. The name must match the list in the F:\CONFIG.DAT file. <pointname> is the control signal name, as described in the F:\UNITDATA.DAT file. The synonym can NOT be used, but will be displayed if synonyms are enabled. +-------------------------------------------------------------------+ |T "Text line1" "Text line2" btype "bunit" "command" "funit" "fname"| | fsense vtype value | +-------------------------------------------------------------------+ TARGET RECORD: One of the targets shown on the display. These lines must be indented under the DISPLAY RECORD. (It must also be one line, it was broken into two lines here for explanation only. A target record is associated with the point record immediately preceding it. The top line of the button text will line up with the point name text on the display. A target record is permitted every three point records so they will not overlap when displayed. Target records are valid only for Point type displays. (see DISPLAY RECORD)<br />
<br />
162 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
; ; <Text line1> and <Text line2> are the text strings in the target. ; If both are blank, the rest of the line is ignored. ; ; <btype> is a single character button type: ; - - <not used> ; ? - ARM/EXECUTE ; ! - IMMEDIATE ACTION ; # - ANALOG SETPOINT ; ; <bunit> is the name of the unit to send the command to. If an empty ; string is supplied, the command will be sent to the currently ; selected unit. ; ; <command> is the name of the command signal. ; ; <funit> is the name of the unit to get the feedback signal from. If ; an empty string is supplied, the currently selected unit is used. ; ; <fname> is the name of the feedback signal. If an empty string is ; supplied, no feedback signal is used. ; ; <fsense> is a feedback signal state that highlights the target: ; 0 - Highlight when the feedback signal is FALSE (0). ; 1 - Highlight when the feedback signal is TRUE (1). ; ; <vtype> is a single character value type: ; + - The value is added to the current value and sent. ; - - The value is subtracted from the current value and sent. ; = - The value is sent to the unit. ; ; <value> is the HEX value for the command. ; ; ; +------------------------------------------------------------------+ ; | S "search class" | ; +------------------------------------------------------------------+ ; ; SEARCH RECORD: One of the point classes to be shown on the display. ; These lines must be indented under the DISPLAY RECORD. The entries ; in the search record are used to search the data dictionary and ; points matching at least one of the criteria are displayed. ; Search records are valid only for Dictionary type displays.(see ; DISPLAY RECORD) ; ; <search class> is the data dictionary search criteria. All ; valid XDTYPEs are allowed (for logics, XDTYPEL1, use L1 and so on. ; Also allowed are special classes - Command Pushbuttons, Logic State, ; Analog Setpoints, Control Constants, and All. ; ; ; +-----------------------------------------------------------------+ ;------------------------------------------------------------------UNIT_NUMBER 1 TITLE "Demand Display" TYPE "Point" ; ; This is a point list based display. ; ; ; There are 0 lines in this display. ; ; ;P unit-pointname ;- ---- -------------;-------------------------------------------------------------------UNIT_NUMBER 1 TITLE "Logics" TYPE "Dictionary" ; ; This is a dictionary-based display. ; ; ;S Point Type ;- ---------S "L1" ;--------------------------------------------------------------------UNIT_NUMBER 1 TITLE "Demonstration" TYPE "Point" ; ; This is a point list based display. ; ; ; There are 11 lines in this display. ; ;<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 163<br />
<br />
;P ;P ; ;T ;T ; ;P ;P P P P P P ; ;T ;T ; ;P ;P P P P ;<br />
<br />
unit-pointname ---- -------------"" "L4" Text line1 Text line2 BT unit-command-name unit-feedback-name F T value ---------- ---------- -- ---- -------------- ---- -------------- - - -----"LOAD" "SETPOINT" # "" "L90PSEL_CMD" "" "" 0 = 0x00 unit-pointname ---- -------------"" "L52GX" "" "L90PSEL_CMD" "" "DWATT" "" "TTXM" "" "" "" "L1X" Text line1 Text line2 BT unit-command-name unit-feedback-name F T value ---------- ---------- -- ---- -------------- ---- -------------- - - -----"START" "" ? "" "L1START_CPB" "" "L1X" 1 = 0x04 unit-pointname ---- -------------"" "L2TV" "" "L14HM" "" "L14HS" "" "L3"<br />
<br />
DM22SRC.EXE Source File Output Example The following examples show the Demand Display screens from DEMO.DM2 corresponding to the DEMO.SRC source file.<br />
<br />
164 • Chapter 6 Configuration<br />
<br />
•<br />
<br />
Demand Display Menu File<br />
<br />
•<br />
<br />
Demand Display screen (empty)<br />
<br />
•<br />
<br />
Demand Display Screen “Logics”, a Dictionary based Display. Can show given types of points and classes of points.<br />
<br />
•<br />
<br />
Demand Display Screen “Demonstration”, a Point based Display. Populated by user-selected points and user defined commands.<br />
<br />
GEH-6126<br />
<br />
Demand Display Menu Screen Example<br />
<br />
Demand Display Screen (empty) Example<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 165<br />
<br />
Demand Display Dictionary Based Using Logics Example<br />
<br />
Demand Display Points Base Display, User Defined, Example<br />
<br />
166 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Starting The Demand Display to Source Conversion Program The Demand to Source Conversion Program, DM22SRC.EXE, is a command line program, not a Windows program. The program has a reverse option, which converts the text source file back to a binary storage file. To convert a Demand Display binary file (*.DM2) to a text source file (*.SRC), change directories to the location of the *.DM2 file, typically F:\RUNTIME. Then enter: DM22SRC.EXE filename<br />
<br />
It is not necessary to enter the file extension as the program will append the appropriate extension. The output file will have the same name with a *.SRC extension. Note This procedure will overwrite an existing source text file with the same name. To convert a text source file (*.SRC) to a Demand Display binary file (*.DM2), change directories to the location of the *.SRC file. Then enter: DM22SRC.EXE FILENAME /R<br />
<br />
It is not necessary to enter the file extension as the program will append the appropriate extension. The output file will have the same name with a *.DM2 extension. Note This procedure will overwrite an existing binary format file with the same name. The program will display an error message and halt execution if it encounters an error in the *.SRC file.<br />
<br />
Editing the Demand Display Source File The Demand Display Source File may be edited by any word processor that can use a fixed pitch font and save to a text format. The rules for formatting the text file are described in the source file example earlier in this document.<br />
<br />
Each display must have a Title, which:<br />
<br />
GEH-6126<br />
<br />
•<br />
<br />
Defines which unit number the screen is applied to.<br />
<br />
•<br />
<br />
Defines the screen title<br />
<br />
•<br />
<br />
Defines the display type<br />
<br />
•<br />
<br />
There are two types of displays:<br />
<br />
•<br />
<br />
Dictionary Based<br />
<br />
•<br />
<br />
May contain only specific point types, and/or point classes.<br />
<br />
•<br />
<br />
They do not contain commands.<br />
<br />
•<br />
<br />
Point Based<br />
<br />
•<br />
<br />
Contain user-defined points.<br />
<br />
•<br />
<br />
May have user defined commands (command spacing is no closer than every fourth line to prevent overlap.)<br />
<br />
Chapter 6 Configuration • 167<br />
<br />
CONSTSET Overview CONSTSET is a configuration utility used for Mark V turbine controls to make all control constants that are defined adjustable, and to set the default ramp rate for each control constant. (It is not used for the Mark V LM.)<br />
<br />
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 which control constants are to be considered adjustable, and which ones are not. In addition, for each control constant that is adjustable, the ramp rate for that constant can be defined. This concept is heavily used in Mark V LM applications, but is not as typical in Mark V applications. CONSTSET is a configuration utility that 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 applications to have the HMI emulate what the previous generation of operator interface did, without having to configure each control constant by hand.<br />
<br />
Note As of TCI Version 1.2, the CONSTSET.DAT file is still required, but a new 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 at all. (See the application information at the end of this section for more details.)<br />
<br />
Operation CONSTSET is a command line configuration utility. It requires one command line<br />
<br />
qualifier, the name of the Mark V unit to configure. This is supplied using the "/UNIT=<unit_name>" qualifier. If run with no parameters or the "/?" parameter, a help screen is presented, as shown in the example below: 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:<br />
<br />
CONSTSET<br />
<br />
/UNIT:<unitname><br />
<br />
F:\UNIT1><br />
<br />
The next example shows a sample of the CONSTSET.DAT file, the output of the CONSTSET program: ; CONSTSET.DAT -- Control Constants Adjustment Settings File ; ; ; This file contains the adjustable constants for the unit. ; ; ; Point Engr Ramp Min Max ; Name Units Rate Value Value AFKQG "CNT09" 0.1 AFKQPC "CNT05" 0.001 AQK0_B "#/sec" 0.01 AQK0_E "#/sec" 0.01<br />
<br />
168 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
<…and so on…><br />
<br />
Application Information Starting with TCI Version 1.2, there is an easier way to have the unit generate the Mark V default ramp rates than through the use of the CONSTSET program. A new option was added to the CONSTSET.DAT file that will cause 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 scheme has the advantage that any additions to the control constants (or new control constants) will automatically be picked up when TCI is restarted with no additional configuration work required. 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 will trigger the Dictionary Loader to set every control constant as adjustable, and set the ramp rate according to the default scale code table. The results of this 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. Make sure that any lines changing the defaults are after the "*MARK V_DEFAULT" line, or else the lines will be overridden when the defaults are computed.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 169<br />
<br />
The next example shows a CONSTSET.DAT where the default values are computed when TCI is 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 ;<br />
<br />
CONSTCHK Overview CONSTCHK is a command line configuration utility that displays control constants<br />
<br />
that have a different value between the unit’s RAM and the unit’s non-volatile storage. It is useful in determining which control constants have had their RAM values changed since the unit was last reset or powered up. When a turbine control is reset or powered up, it reads the control constant values out of non-volatile memory and loads the values into RAM. The panel then runs using these RAM resident values. The Control Constant Adjust Display can dynamically change the contents of the RAM resident control constants. Use of the Control Constants Adjust Display will result in the contents of the RAM and the contents of the non-volatile memory value being different. CONSTCHK is a utility program that will outline the differences between the contents of the RAM and non-volatile storage, giving a list of the changes that were made.<br />
<br />
Operation CONSTCHK is a command line utility program that is typically 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 will provide a help screen.<br />
<br />
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 will be displayed.<br />
<br />
170 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Example The following example shows 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 ...--------LK90PSEL LK90SPIN<br />
<br />
Units -------"MW" "MW"<br />
<br />
RAM (CSDB) -----------24.0 3.0<br />
<br />
EEPROM -----------22.6 4.0<br />
<br />
...There were 2 Control Constants with different values. F:\UNIT1><br />
<br />
The following example shows 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 ...--------K39VTT_TD KOTRDITH_M KOTRR_LAG KOTRR_LEAD KPLTR_LEAD KPLTR_NLMT KPLT_BIAS<br />
<br />
Units -------"sectd" "%" "secrt" "secrt" "secrt" "%" "%"<br />
<br />
RAM (CSDB) -----------0.015 3.09 10.00 5.38 5.88 3.19 3.19<br />
<br />
AP1 -----------0.000 0.00 0.00 0.00 0.00 0.00 0.00<br />
<br />
...There were 7 Control Constants with different values. F:\UNIT2><br />
<br />
SEQCOMPL (Sequencing) Overview The Control Sequence Compiler is a separate command line program that compiles CSP segments into one Control Sequence Program (CSP) for use in the unit control. The Control Sequence Compiler compiles only the sequencing source segments (*.SRC) listed in MSTR_SEQ.CFG, the compiler configuration file. Refer to other sections of this document for more information on the MSTR_SEQ.CFG file. The Sequence Compiler is a command line program, not a Windows program.<br />
<br />
! Caution<br />
<br />
GEH-6126<br />
<br />
Only qualified personnel knowledgeable about turbine control and protection should use the Sequence Compiler. Improper use may adversely affect the control and protective features of the control system.<br />
<br />
Chapter 6 Configuration • 171<br />
<br />
File Structure The output of the Sequence Compiler is an *.AP1 file (or files) that can be downloaded to the unit control. The downloadable sequencing filename is SEQ.AP1 for Mark V LM. The downloadable sequencing filenames are SEQ_B.AP1 and SEQ_Q.AP1 for Mark V. Please refer to the section on the Downloader for more information on how to download the files to the unit control. The program always writes a text log file - MSTR_SEQ.LOG in the unit configuration directory. Along with the segment source files, the Control Sequence Compiler uses several unit specific files that contain signal name database definitions and definitions of the available software building blocks. The following Figure is a summary of these files. 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 Control Sequence Compiler uses to check the validity of pointnames used in the segment source files. MSTR_SEQ.CFG SEQ.AP1 (Mark VLM) UNITDATA.DAT<br />
<br />
PROM\PRIMITIVE.DEF<br />
<br />
SEQCOMPL.EXE Control Sequence Compiler<br />
<br />
SEQ_B.AP1 (Mark V)<br />
<br />
PROM\BIGBLOCK.DEF<br />
<br />
{Segment1 {Segment2<br />
<br />
SEQ_Q.AP1 (Mark V)<br />
<br />
{Segment name}.SRC<br />
<br />
Sequence Compiler Block Diagram<br />
<br />
Executing the Sequence Compiler Selecting the Control Sequence Compiler icon or typing SEQCOMPL or hitting enter while at a command prompt in the unit specific directory initiates the compiling program. The Control Sequence Compiler creates a listing, MSTR_SEQ.LOG, of the errors (if any) found in the segments. These errors must be resolved by using the Sequence Editor program to make appropriate changes to the sequencing source file (or files) (*.SRC). The *.AP1 output files will not be produced until the Sequence Compiler executes error free. A sample Sequence Compiler execution follows:<br />
<br />
172 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
F:\UNIT1>SEQCOMPL Mark V - Control Sequence Program Compiler Revision Date: Aug 20 1997 at 11:12:38 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 ---> <Q> segment: F:\UNIT1\SEQ_TRN1.src ... 176 rungs processed ---> <Q> segment: F:\UNIT1\SEQ_TRN2.src ... 110 rungs processed ---> <Q> segment: F:\UNIT1\SEQ_TRN3.src ... 95 rungs processed ---> <Q> segment: F:\UNIT1\SEQ_TRN4.src ... 81 rungs processed ---> <Q> segment: F:\UNIT1\SEQ_TRB1.src ... 158 rungs processed ---> <Q> segment: F:\UNIT1\SEQ_TRB2.src Frequency := 2 Skew 0 ... 140 rungs processed ---> <Q> segment: F:\UNIT1\SEQ_TRB3.src Frequency := 2 Skew 1 ... 151 rungs processed ---> <B> segment: F:\UNIT1\SEQ_TRN1.src ... 176 rungs processed ---> <B> segment: F:\UNIT1\SEQ_TRN2.src ... 110 rungs processed ---> <B> segment: F:\UNIT1\SEQ_TRN3.src ... 95 rungs processed ---> <B> segment: F:\UNIT1\SEQ_TRN4.src ... 81 rungs processed ---> <B> segment: F:\UNIT1\SEQ_B.src ... 5 rungs processed ---> Creating the <Q> AP1 sequencing file: F:\UNIT1\SEQ_Q.AP1 ---> Creating the <B> AP1 sequencing file: F:\UNIT1\SEQ_B.AP1 -------- CSP Compiler Finished --------<br />
<br />
Master Sequencing Configuration File The Master Sequencing Configuration File, MSTR_SEQ.CFG, governs which sequencing source files are compiled for which controller in the unit, and at what rate the segments are executed within the control. It is a text file, which may be modified by any word processor. The file is located in the unit configuration directory, typically F:\UNITn.<br />
<br />
! Caution<br />
<br />
Only qualified personnel knowledgeable about turbine control and protection should modify the Master Sequencing Configuration File, MSTR_SEQ.CFG. Improper use may adversely affect the control and protective features of the control system.<br />
<br />
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 may be viewed with any word processor. It is a text representation of the AP1 file to be downloaded to the unit. Typically, this directive is preceded by a ‘.’ to convert it to a comment.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 173<br />
<br />
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 will not be able to execute after it is downloaded. The BIGBLOCK.DEF file revision must match the prom revision in the unit control. The following listing 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 ---------------------------------------------------------------------- <R>, <S>, and <T> Segments --------------------------------------------------------------------#<Q>_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 ---------------------------------------------------------------------- <C> and <D> Segments --------------------------------------------------------------------#<B>_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 The “#Q_SEGMENTS” tag indicates sequencing for the <R>, <S>, & <T> processors.<br />
<br />
The “#B_SEGMENTS” tag indicates sequencing for the <C> & <D> processors. (Mark V only) The “#END” tag indicates the end of the document information.<br />
<br />
174 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
The following example demonstrates the Frequency and Skew features: Segment<br />
<br />
Frequency n<br />
<br />
Skew within scan rate<br />
<br />
name<br />
<br />
power of 2 (>0)<br />
<br />
(units of 1/16 sec)<br />
<br />
W<br />
<br />
1<br />
<br />
0<br />
<br />
X<br />
<br />
2<br />
<br />
0<br />
<br />
Y<br />
<br />
2<br />
<br />
1<br />
<br />
Z<br />
<br />
8<br />
<br />
3<br />
<br />
Equation (Frame Rate of Mark V is 16): Execution Rate in Hz = Frame Rate / Frequency 8 Hz = 16 / 2 Note that the frequency parameter denotes the period in frames for the segment. Using the above configuration would yield segment execution at the following Mark V Frequencies and Skews (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<br />
<br />
Z<br />
<br />
Z<br />
<br />
|<br />
<br />
Z<br />
<br />
|<br />
<br />
| |<br />
<br />
Z<br />
<br />
| |<br />
<br />
|<br />
<br />
|<br />
<br />
Z<br />
<br />
|<br />
<br />
| |<br />
<br />
Z<br />
<br />
| |<br />
<br />
|<br />
<br />
|<br />
<br />
| |<br />
<br />
|<br />
<br />
Z<br />
<br />
| |<br />
<br />
|<br />
<br />
|<br />
<br />
| |<br />
<br />
|<br />
<br />
| |<br />
<br />
|<br />
<br />
| |<br />
<br />
|<br />
<br />
|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.| 0123456789ABCDEF 0.0sec 0.5sec<br />
<br />
1.0sec 1.5sec 2.0sec<br />
<br />
2.5sec 3.0sec<br />
<br />
3.5sec 4.0sec<br />
<br />
The frame rate is 16 Hz. 16 executions per second are possible. Segment W is executed every one frame, for a 16 Hz execution. Segment X is executed every two frames, for an 8 Hz execution. Segment Y is executed every two frames, for an 8 Hz execution, and is skewed by one frame. Segment Z is executed every eight frames, for a 2 Hz execution, and is skewed by three frames. At Frame #0 above, the segments W, and X will execute. At Frame #1 above, the segments W, and Y will execute. At Frame #3 above, the segments W, Y, and Z will execute. --------------------------------------------------------------------For Mark V LM, the Master Sequencing Configuration File, MSTR_SEQ.CFG, is similar to the one for Mark V, except scan rate and offset replace frequency and skew.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 175<br />
<br />
The following example (MSTR_SEQ.CFG Sequence Compiler Configuration File Example for Mark V LM) shows the file for a Mark V LM. The scan rate governs how often the segment executes and the offset controls on which frame 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 Frame Time(period) Hz ; Scan Rate n = 1 = (base)10 = msec iteration interval 100 ; Scan Rate n = 2 = 20 = msec iteration interval 50 ; Scan Rate n = 4 = 40 = msec iteration interval 25 ; Scan Rate n = 8 = 80 = msec iteration interval 12.5 ; Scan Rate n = 16 = 160 = msec iteration interval 6.25 ; Scan Rate n = 32 = 320 = msec iteration interval 3.125 ; Scan Rate n = 64 = 640 = msec iteration interval 1.5625 ; Scan Rate n = 128 = 1280 = msec iteration interval 0.78125 ; ; For Mark VLM the reference rate is 100 Hz, 10 msec #<Q>_SEGMENTS ; Scan rate, n Offset within scan rate #SEGMENT SEQ_10GE 1 0 ;GENIUS COMM ;CHECK #SEGMENT SQ_BLK 1 0 ; #SEGMENT SQ40_2 4 2 ;PD #SEGMENT SQ40_1 4 1 ;PD #SEGMENT SQ640 64 11 ;13 #SEGMENT SQ160_5T 16 5 ; DRAIN / PURGE ;VALVE DEMAND AND FEEDBACK #SEGMENT SQ160_3T 16 3 ; DRAIN / PURGE #END<br />
<br />
176 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
SEQDOCMT (Sequencing) Overview 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. This document is used by field service and maintenance personnel to check out and debug the unit control. 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. Refer to other sections of this document for more information on the MSTR_SEQ.CFG file. The Sequence Documentor is a command line program, not a Windows program.<br />
<br />
File Structure Two files are produced by the CSP Documentor program. 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 will be 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 (Control Sequence Program). It may 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 will adapt the format of the document to the selected printer. Each page of the document begins with a header showing the segment name, date, and page number. Please note that the page number represents the page number within the segment. 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 may appear on any page.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 177<br />
<br />
Control Sequence Document for Segment F:\UNIT_EA\SEQ20_1.SRC Tue Nov 18 13:55:02 1997 Page - 34 <<< Rung Number 50 >>> ±µµµµµµµµµµµµµ£ ¢ DIVIDE ¢ LZZ LTRUE Enable ¢ ¢ ¬¬¬ «¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¿¬ ¬ ¬ ¬ ¬ ¬ ¬¿¬¬¬¬¬¬¬¬¬¬( ) ¢ ¢ GP3PFF 1¢Dvdnd¬§ ¢0 GP3T2_PFFX ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¿¬¬¬¬¬ «¬¬¬¬¬¿¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ ¢ Þ ¢ GP2SEL 2¢Dvsr ¢ ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¿¬¬¬¬Á¨¬Á ¢ ¢ ¢ ¢ ¢ °µµµµµµµµµµµµµ¤ 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 GP3T2_PFFX -- PILOT TRIM VALVE P3/P2 RATIO FEED FORWARD AUX N/D SEQ20_1 -50 SEQ20_1 51 <<< Rung Number 51 >>> ±µµµµµµµµµµµµµµµµ£ ¢ MAX ¢ LZZ LTRUE Enable ¢ Maximum Select ¢ ¬¬¬ «¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¿¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬¬¿¬¬¬¬¬¬¬¬¬¬( ) ¢ ¢ GP3T2_PFFX 1¢ ¬¬¬¬¬¬¬¬§ ¢ ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¿¬¬¬ ¢ ¢ ¢ RZERO 2¢ Max ¢0 GP3T2_PFF ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¿¬¬¬ «¬¬¬¿¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬ ¢ Select ¢ RZERO 3¢ ¢ ¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¬¿¬¬¬ ¢ ¢ ¨¬¬¬¬¬¬¬¬Á ¢ °µµµµµµµµµµµµµµµµ¤ 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<br />
<br />
CSP.PRN Sequence Documentor Output Example<br />
<br />
178 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
CSP_XREF.PRN The CSP_XREF.PRN document is a text file pre-formatted with page breaks to form a complete document. The CSP_XREF.PRN is a cross-reference document which contains a list of signal names with the segment and rung number where the signal is used. It may be viewed with any word processor with a fixed pitch font. It is best to print this document with the CSP Printer program as it will adapt the format of the document to the selected printer. A CSP_XREF.PRN Sequence Documentor Output example is shown below.<br />
<br />
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 software 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 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.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 179<br />
<br />
Unit Master Cross Reference - Page 4 Fri Jan 31 10:53:51 1997 CDPSUMAVGA -- CDP VALVE LVDT A SECONDARY SUM AVERAGE V RMS SEQ_CAL -3 CDPSUMAVGB -- CDP VALVE LVDT B SECONDARY SUM AVERAGE V RMS SEQ_CAL -3 CDP_CUR -- CDP BLEED VALVE SERVO DRIVER FEEDBACK <R2> QTBA-033 SEQ_640 63 CDP_CUR_REF -- CDP BLEED VALVE SERVO DRIVER OUTPUT % SEQ_640 63 SEQ_10GG -57 CDP_ERR -- CDP BLEED VALVE DEMAND POSITION ERROR % SEQ_640 63 SEQ_10GG -57 CDP_ERRABS -- ABSOLUTE VALUE OF CDP_ERR % SEQ_640 -63 CDP_NBIAS -- CDP BLEED VALVE NULL BIAS BASED ON CDPSEL % SEQ_10GG -57 CDP_NSC -- CDP BLEED VALVE SERVO CURRENT NULL COMPENSATION % SEQ_10GG 57 CDP_POS_DMD -- CDP BLEED VAVLE POSITION DEMAND % SEQ20_1 -23 SEQ_10GG 57 CHIP_AGB -ohms SEQ_640 76 CHIP_BSUMP -ohms SEQ_640 76 CHIP_CSUMP -ohms SEQ_640 76 CHIP_DSUMP -ohms SEQ_640 76 CHIP_TGB -ohms SEQ_640 76 CPCVAVG -- BACKUP RATIO OF SPECIFIC HEATS (CP/CV) N/D SEQ_0 -14 SEQ_640 8 CPCVMAN_PV -- PREVIOUS VALUE OF MANUAL SELECT CP/CV RATIO SEQ_640 -8 CPCVRATEVAL -N/D SEQ_0 -14 SEQ_640 -8 CPCV_MAN -- RATIO OF SPECIFIC HEATS (CP/CV) FOR MANUAL SELECTION SEQ_640 8 CPCV_PVGOOD -- RATIO OF SPECIFIC HEATS (CP/CV) FAULT TIME DELAY SEQ_640 -8 CPCV_PVINP -- PREVIOUS VALUE OF CP/CV RATIO INPUT N/D SEQ_640 -8 CP_CV -- GAS FUEL RATIO OF SPECIFIC HEATS N/D SEQ_0 -14 SEQ_0 -15 SEQ_640 8 CP_CV_SEL -- SELECTED VALUE OF CP_CV USED IN SEQUENCIN SEQ_0 -14 SEQ20_1 42 SEQ20_1 52 1 62 SEQ_640 -8 SEQ_10GG 68 CS3 -- INTERMEDIATE HEAT SOAK GAIN N/D SEQ_20 -4 D30T2A -- ALMTXT:'COMPRSR INLET TEMP(T2A) SENSOR FAILED' AL 37 SEQ_40 -2 D30T2B -- ALMTXT:'COMPRSR INLET TEMP(T2B) SENSOR FAILED' AL 38 SEQ_40 -2 D30T2DIFF -- ALMTXT:'T2A & T2B SENSOR DIFFERENTIAL' AL 42 SEQ_40 -2<br />
<br />
%<br />
<br />
LOGIC<br />
<br />
N/D N/D<br />
<br />
N/D SEQ20_<br />
<br />
LOGIC LOGIC LOGIC<br />
<br />
Executing the Sequence Documentor<br />
<br />
180 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Selecting the Control Sequence Documentor icon or typing SEQDOCMT or hitting enter while at a command prompt in the unit specific directory initiates the compiling program. The Sequence Documentor has four possible parameters. They must be listed in order after the SEQDOCMT.EXE command. For example, a valid command line is shown with all possible parameters: F:\UNIT1>SEQDOCMT.EXE METRIC.SCA N -LOG F:\UNIT1<br />
<br />
The first parameter is the scale code file name. The default is ENGLISH.SCA. The second parameter is Y or N. N tells 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, 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 may display error messages during execution. These errors must be resolved by using the Sequence Editor program to make appropriate changes to the sequencing source file (or files) (*.SRC) or other unit configuration files as needed. The Sequence Compiler should be run any time changes are made to the files in the unit configuration directory.<br />
<br />
SEQEDIT (Sequencing) Overview The Control Sequence Program (CSP), the Turbine Control Panel’s application software, uses a programming language known as Big Block Language, or BBL. BBL is a relay ladder logic based software structure that defines data flow and function execution. A series of rungs that can contain combinations of comments, relay ladder diagrams, Primitives and Big Blocks makes up the software structure. The Sequence Editor is the software tool for modifying the CSP to make control changes. It is an off-line tool; that is, its changes are made to a source file only. The Sequence Editor does not directly modify the control code running in the panel. After saving the changes made with the Sequence Editor, the CSP must be compiled by the Sequence Compiler and downloaded to the unit control. The Sequence Compiler and download functions are described later in this document. The Control Sequence Editor operates on a basic unit of software known as a segment. A segment consists of a series of sequentially executed rungs. The Control Sequence Editor operates on these rungs. The Control Sequence Editor allows four different types of rungs. Mixing the four rung types within a rung is NOT possible. The four rung types are:<br />
<br />
GEH-6126<br />
<br />
•<br />
<br />
RLD rungs. Pure relay ladder diagram rungs.<br />
<br />
•<br />
<br />
PRIMITIVE rungs. Rungs combining RLD operations with a primitive functional block call.<br />
<br />
•<br />
<br />
BBL rungs. Rungs without RLD operations, but with a Big Block call. Big Blocks are software modules that perform standardized control functions.<br />
<br />
•<br />
<br />
COMMENT rungs. Rungs containing only text, usually identifying important information about the sequencing or segment.<br />
<br />
Chapter 6 Configuration • 181<br />
<br />
The Control Sequence Editor creates new CSP segments or edits existing ones. Once the Control Sequence Editor creates the segment source files, the Control Sequence Compiler compiles them into the CSP for downloading to the Control Panel. The compiler configuration file, MSTR_SEQ.CFG, selects which segments to compile and defines a unique scan rate and execution offset for each segment. The downloaded CSP segments provide the Control Panel with the parameters and instructions on how to control the process.<br />
<br />
File Structure The Sequence Editor operates on segment source files within the unit configuration directory, typically F:\UNITn. The files have a *.SRC extension. The CSP segment source files have a text format. Never edit the segment source files directly. Use the Control Sequence Editor program to open, modify, and save these files. 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.<br />
<br />
182 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Along with the segment source files, the Control Sequence Editor uses several unit specific files that contain signal name database definitions and definitions of the available software building blocks. The Figure below is a summary of these files. 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 Control Sequence Editor uses 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 as different units may have different functions defined in their associated BIGBLOCK.DEF and PRIMITIV.DEF and different signals defined in their UNITDATA.DAT files. 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.<br />
<br />
! Caution<br />
<br />
UNITDATA.DAT<br />
<br />
PROM\ PRIMITIVE.DEF<br />
<br />
SEQEDIT.EXE Control Sequencing Editor<br />
<br />
PROM\ BIGBLOCK.DEF<br />
<br />
{Segment name}.SRC Original or New source file<br />
<br />
The Control Sequence Editor File Structure<br />
<br />
Using The Control Sequence Editor Editing a segment requires performing 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 drop-down menu options from the menu bar selections or the buttons on the toolbar performs these operations.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 183<br />
<br />
This section provides information concerning the use of the following functions: •<br />
<br />
Starting the Control Sequence Editor and Loading a segment(s)<br />
<br />
•<br />
<br />
The Control Sequence Editor Window<br />
<br />
•<br />
<br />
Navigating within a segment(s)<br />
<br />
•<br />
<br />
Editing a rung(s)<br />
<br />
•<br />
<br />
Selecting a rung(s)<br />
<br />
•<br />
<br />
Copying a rung(s)<br />
<br />
•<br />
<br />
Moving a rung(s)<br />
<br />
•<br />
<br />
Adding/Deleting a rung(s)<br />
<br />
•<br />
<br />
Creating a rung(s)<br />
<br />
•<br />
<br />
Viewing multiple segments<br />
<br />
•<br />
<br />
Saving a segment<br />
<br />
•<br />
<br />
Exiting the Control Sequence Editor<br />
<br />
Starting The Control Sequence Editor Selecting the Control Sequence Editor icon or typing SEQEDIT and hitting enter at the command prompt or in the Start Menu Run Dialog Box starts the Control Sequence Editor. Typing SEQEDIT {Segment name}.SRC and hitting enter passes the name of the desired segment to the Control Sequence Editor, where Segment name is the name of a segment file. Insert a space between SEQEDIT and the segment name and include the file extension .SRC. When accessing the Control Sequence Editor from the icon or starting without supplying a segment name at the command prompt, select the menu bar option File and the Open command from the drop down menu to open a segment file for editing. The Control Sequence Editor allows opening multiple segments, each in a separate segment window within the Control Sequence Editor.<br />
<br />
Loading An Existing Segment The Control Sequence Editor loads existing segments in three ways. If the Control Sequence Editor starts from the command prompt, type the name of the segment after the Control Sequence Editor execution command, SEQEDIT. Include the source extension, .SRC with the segment name. For example: F:\UNIT1>SEQEDIT<br />
<br />
{Segment name}.SRC<br />
<br />
Where {Segment name}.SRC is a sequencing segment filename such as SEQ_160.SRC. To load an existing segment after starting the Control Sequence Editor, select the menu option File:Open command from the drop-down menu. The Control Sequence Editor provides a list of files with .SRC extensions. Not all of these files are sequencing segment source files. Select the desired file and hit 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 the segment name from the drop-down menu.<br />
<br />
184 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Loading A New Segment If no existing file is specified when the Control 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.<br />
<br />
The Control Sequence Editor Window The Control Sequence Editor operates in a Windows environment. Using the Control Sequence Editor is similar to using other Windows applications. The Control Sequence 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 Control Sequence Editor. The Control Sequence Editor opens each segment in a separate segment window. The segment window displays the segment one rung at a time. RLD rungs display on a 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 rung/blocks that exceed the segment window boundaries.<br />
<br />
The Sequence Editor Window Showing an RLD Rung The menus and toolbar at the top of the screen incorporates items common to Windows applications along with special items associated with the Control Sequence 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.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 185<br />
<br />
Navigating Within a Segment Window Individual rungs make up the sequencing segments. Navigating within the segment involves moving about the rungs. The top right hand corner of the segment window displays the rung number. Navigate between the rungs using drop-down menu options from the menu bar, 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.<br />
<br />
Editing an Existing Rung The Control Sequence Editor allows for editing existing rungs. 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. The signal name point list dialog box selects the new control signal name. Selecting Edit:Comment from the menu displays the text window with the existing comment text. The text window allows modifying text or adding additional 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 selection 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.<br />
<br />
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 dropdown 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.<br />
<br />
Copying Rungs The Control Sequence Editor allows for copying of rungs within a segment window or to another segment window. Navigate to the rung and select it using the menu option Edit: Select. The rung highlights. Select the Edit:Copy menu item. Navigate to the insertion point and select the menu bar option Edit:Paste. The Control Sequence Editor inserts the copied rung and re-numbers the following rungs. 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 Control Sequence 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.<br />
<br />
186 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Moving Rungs The Control Sequence Editor allows for moving one rung or multiple rungs. The procedure is identical to that of copying rungs except the menu option Edit: Cut is used to remove the rung and re-number the following rungs. Navigating to the new location for the rung and selecting Edit:Paste inserts the rung to the new location and re-numbers the following rungs. Cutting and pasting multiple selected rungs removes all selected rungs and inserts them in the new location. Toolbar buttons also perform the cut and paste functions.<br />
<br />
Adding A Rung The Control Sequence 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 Control Sequence 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.<br />
<br />
Deleting A Rung The Control Sequence Editor allows deleting rungs. Navigate to the desired rung. At the rung, select the menu option Rung:Delete. The Control Sequence Editor displays a dialog box requesting confirmation of the deletion. Deleting a rung is permanent. Only exiting the Control Sequence Editor without saving restores a deleted rung. There is no undelete selection. To cancel a delete, select the Cancel button in the confirmation window.<br />
<br />
Selecting The Rung Type New rungs are one of four different rung types: •<br />
<br />
RLD (relay ladder logic alone)<br />
<br />
•<br />
<br />
Primitive (a basic block with relay ladder logic)<br />
<br />
•<br />
<br />
BBL (one large block alone)<br />
<br />
•<br />
<br />
COMMENT (text only)<br />
<br />
Selecting the Rung:Type menu item displays the Modify Rung Type dialog box that allows the choice of one of the four rungs. Choosing the RLD rung type displays a blank grid for adding components. Selecting the BBL or PRIMITIVE rung types displays another dialog box to choose which BBL or Primitive to add. BBLs display as tiles, and often require signal names. Primitives display both a tile and an RLD grid and require signal names. The COMMENT rung type displays a blank screen without the RLD grid.<br />
<br />
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 for its addition on 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, 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 for that component. If the control signal name is invalid or the type of signal is<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 187<br />
<br />
invalid for the component, the Control Sequence 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. Using the toolbar buttons representing components allows for quick component additions and deletions. The menu bar option Component has six commands available for editing RLD rungs and the RLD section of Primitive rungs. The drop-down menu command NOC represents a Normally Open Contact component selection, while 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.<br />
<br />
Adding Primitive Rungs Selecting the PRIMITIVE rung type displays a Select Primitive Function dialog box. The Select Primitive Function dialog box displays a list of the available Primitives blocks. After selecting one of the Primitive blocks from the list, the Primitive block tile for that Primitive 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 for selecting the control signal name. Primitive blocks typically require signal names on the coils and any locations indicated inside the primitive tile itself. Double clicking on the names inside the primitive tile displays the Signal Name dialog box for selecting the associated control signal name. Typically, a primitive block requires a contact(s) to enable it. Follow the Adding RLD rungs rules to add the enabling contact(s). Normally open contacts, normally closed contacts, connectors, or combinations are allowed.<br />
<br />
Adding BBL Rungs Selecting the BBL rung type displays a Select Block Function dialog box. The Select Block Function 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 appears across the entire segment window as BBL blocks do not include any RLD rung components. Double clicking on the names within the block displays the Signal Name dialog box for selecting the associated control signal name.<br />
<br />
Adding Comment Rungs Selecting the COMMENT rung type displays a blank segment window. Adding text involves selecting the menu option and Edit:Comment or double clicking anywhere in the comment rung. The Edit Comment dialog box appears for typing in text. 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. The Control Sequence Editor allows comments of 40 characters wide and 20 lines long.<br />
<br />
188 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Viewing Multiple Segments Windows The Control Sequence Editor allows displaying any number of segments at one time. Selecting the menu option File:Open command from the drop-down menu multiple times 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 tile fashion across the screen, dependent on the number of windows open. Tile uses a non-overlapping display. 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 Control Sequence Editor allows multiple windows of the same segment, and all windows of the same segment reflect changes to one of the segment windows. The latest segment window displays on top of the other unless the Tile or Cascade commands are selected. 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. Minimizing a window by clicking on the top left bar button of the window and selecting Minimize removes the segment window from the presentation window by iconizing it. Double clicking on the icon loads the segment window back onto the Control Sequence Editor window. Selecting Maximize enlarges the segment window to fit the size of the Control Sequence Editor window. Using the cursor to select the side bar of a segment window allows for adjusting of the size of the window, similar to other Window applications. A highlighted title bar on a segment window indicates the segment window currently selected.<br />
<br />
Saving a Segment Selecting the menu option File:Save or clicking on the toolbar button of a disk saves segments. Saving a file overwrites the previous file and loses all old information. 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 segment was not given a name previously and the Save command or Save toolbar button are selected.<br />
<br />
! Caution<br />
<br />
Saving a segment overwrites the segment losing the data in the initial (unedited) file. It is recommended that prior to editing a segment, copy the segment to a separate location. After verifying the saved segment’s functionality, delete the old copy of the segment.<br />
<br />
Selecting the menu option File:Close closes a segment. A Save As dialog box appears when closing with new or not yet saved segments and requests 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.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 189<br />
<br />
Exiting the Control Sequence Editor Selecting the menu option File:Exit exits the Control Sequence Editor program. The Save As dialog box requests whether to save the segment if the current file has not been saved. Selecting No exits the Control Sequence Editor without saving the segment, losing all changes. Selecting Yes saves the segment.<br />
<br />
CSPPRINT Overview The Control Sequence Program Printer, is a utility program for printing CSP documents using the standard Windows printing support. The CSP documents are important as they represent the sequencing used by the Mark V and Mark V LM for control. The CSP file is a pre-formatted file containing all the necessary information for pagination. The CSP Printer program uses this information to display and print the CSP document. The CSP Printer program is intended for use only with CSP documents. It is not designed to display or print other document types. The CSP Printer program cannot edit or modify the CSP Document. Use the Sequence Editor to modify the CSP source code. The CSP document is produced by the Sequence Documentor command line program. After successfully running the Documentor, the CSP document is ready for printing by the CSP Printer program. Please refer to the section of this manual on the Sequence Documentor for specifics about its operation. The CSP Printer program can print all or part of the CSP document. It can also be run from the command line without a window to print the entire CSP document to the default printer. During the printing process, the CSP Printer program runs at a lower priority to make the CPU resources available to other processes.<br />
<br />
File Structure The CSP Printer program operates on CSP.PRN and CSP_XREF.PRN files in the unit configuration directory. The CSP documents are produced by the Sequence Documentor command line program. The CSP output document is pre-formatted containing all the necessary information for pagination. The CSP Printer program is intended for use with CSP documents. It is not designed to display or print other document types such as text or other word processing documents. These files may 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.<br />
<br />
190 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Using the CSP Printer Program This section provides information concerning the use of the following functions: •<br />
<br />
Starting the CSP Printer Program<br />
<br />
•<br />
<br />
The Display Window<br />
<br />
•<br />
<br />
Page Setup<br />
<br />
•<br />
<br />
Printer Selection<br />
<br />
•<br />
<br />
How to Print the CSP<br />
<br />
Command Line Arguments The CSP Printer may be launched from the command line with the file name as an Argument to quickly bring the display to a desired configuration: G:\EXEC\CSPPRINT.EXE F:\UNIT1\CSP.PRN<br />
<br />
Only one file name is permitted on the command line. The parameter "/p" (case sensitive) when entered on the command line along with a file name will cause the entire CSP document to be printed to the default windows printer. G:\EXEC\CSPPRINT.EXE F:\UNIT1\CSP.PRN /P<br />
<br />
No program window will appear when using the "/p" parameter, however a dialog box will appear showing the status of the formatting of the print job and giving the user the option to cancel the print job.<br />
<br />
Screen Description The CSP Printer is a single document interface, which allows only one CSP document to be displayed by the program at any time. More than one copy of the CSP Printer program may be run to view and print multiple CSP documents at the same time.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 191<br />
<br />
The CSP Printer Window<br />
<br />
Only one page of the CSP document is displayed at time. Users can use the Page menu or toolbar buttons to navigate through the pages of the CSP document. The window title bar shows the CSP document name including the full path, current page number, and total number of pages in the CSP document. The print preview window displays the active document as it will appear when printed. In print preview mode, the main window is replaced with a print preview window in which one or two pages will be displayed in their printed format.<br />
<br />
Page Setup The user may adjust the appearance of the page by accessing the Page Setup Dialog Box through the File:Page Setup menu selection. This dialog box allows the user as to adjust the appearance of the printed page. The user can select a header to be printed on each page. He can set the page margins in either metric or English units. The OK button modifies the page setup as requested. The Cancel button returns to the current CSP display without changing the page setup.<br />
<br />
192 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Printer Selection The printer and its available options are accessed through the File:Print menu selection. This brings up the standard Windows Print Dialog Box. Please refer to your Windows documentation for how to select the printer and its options using the dialog box.<br />
<br />
How to Print the CSP To print the CSP document, start the CSP printer program. Use the File:Open menu selection to open the *.PRN document in the unit configuration directory. After opening the document, use the File:Page Setup menu selection to adjust the appearance of the page. Then, use the File:Print menu selection to bring up the Print Dialog Box. Select the appropriate printer and paper options, then select the OK button. A dialog box will appear showing the print progress. The user may cancel the print at any time from this dialog box. During the printing process, the CSP Printer program runs at a lower priority to make the CPU resources available to other processes. If a CPU intensive application is running, the CSP Printer Program may appear to be stalled. It is not. It is merely waiting for some free CPU time to resume processing.<br />
<br />
TABLE_C (Table Compile) Overview TABLE_C is a configuration tool that compiles the configuration tables for Mark V<br />
<br />
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 panel needs. The results are placed into a set of *.AP1 files. Some of the configuration information for a Mark V or Mark V LM turbine control is created by editing a set of tables that contain configuration information. These tables contain information such as: which signals are to be totalized, which signals are to be treated as events, and the values of the control constants. These tables are edited in ASCII source files, stored as *.SRC files in the unit configuration directory. These *.SRC files refer to signals using the signal name. TABLE_C is a configuration program that reads the *.SRC files and converts the<br />
<br />
contents of the files from ASCII to the BINARY format that the turbine panel needs. It stores the binary files as *.AP1 files in the unit configuration directory. These binary *.AP1 files are downloaded to the unit to provide the table driven configuration information. There are different tables used in the Mark V from in the Mark V LM, and the binary format used between the two are 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 VXFR.AP1 is not found, the unit is assumed to be a Mark V.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 193<br />
<br />
Operation TABLE_C is a command line configuration program that is run from the unit<br />
<br />
configuration directory. It will look to see whether it is configuring a Mark V or a Mark V LM and process the tables accordingly. If run with no parameters or with the "/?" parameter, a help screen will be provided. This help screen will include 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 values to binary values. To do this, a scale code table is required. By default the ENGLISH.SCA file is used. This can be overridden by using the "/SCALE=<filename>" qualifier in the TABLE_C command line. TABLE_C requires a list of the tables to compile. This list is supplied as parameters to TABLE_C. There is a special parameter "ALL" that will compile all of the table<br />
<br />
files, as shown in the example below: 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><br />
<br />
(The "ALL" parameter is also used by MK5MAKE to compile all tables.) 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 will be given the value of zero.<br />
<br />
194 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
I/O Configuration EEPROM Overview EEPROM is a Mark V configuration utility that downloads the binary configuration information from the HMI into the non-volatile memory (EEPROM) in the Mark V control panel. (EEPROM is not used for the Mark V LM - it uses the UDF program instead.)<br />
<br />
Various configuration tools create the *.AP1 files that define the configuration of the Mark V turbine control. 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. These files must be downloaded from the HMI to the non-volatile memory in the control panel for them to take effect. EEPROM is used to copy these files to the Mark V non-volatile memory. The Mark V uses an EEPROM (Electronically Erasable PROM) as its non-volatile memory to hold these files. EEPROM is the program that transfers the information between the EEPROM in the<br />
<br />
Mark V and the *.AP1 files on the HMI. It also provides a directory command to view the contents of the Mark V EEPROM, and will do a simple sanity check to verify the unit’s EEPROM has not been corrupted.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 195<br />
<br />
Operation EEPROM is a command line utility program that is typically run from a DOS<br />
<br />
prompt. If run with no parameters or the "/?" parameter, help will be provided, as shown in the example below: F:\UNIT1>EEPROM /? Mark V EEPROM downloader. EEPROM <option> <unit_name> <proc> <sections> Where: <option> is one of { UP | DOWN | DIR | CHECK | NOCHECK | HELP | EXIT } <unit_name> is the name of the desired unit. <proc> is the processor to talk to, one of { R | S | T | C | D } <sections> is ALL, USER, or a list of EEPROM partition names, including: FORMAT - Formats (reinitializes) the EEPROM. [Not in USER category] SEQ - Contains the Control Sequence Program. CONST - Contains control constants. IOCFG - Contains IO configuration. UBBL - Contains User BBL library. HIST - Contains point list for history log. EPA - Contains point list for EPA log. MAOUT - Contains point list for 4-20 mA outputs. EVENT - Contains point list for events. CHNG - Contains point list for change detection. BOI - Contains point list for backup operator interface. TOTT - Contains point list for totalized data. TOTD - Contains totalized data. [Not in USER category] CBLR - Contains point list for cable remote. F:\UNIT1><br />
<br />
The available options are: UP - This option uploads the binary from the Mark V to the HMI. It is used when<br />
<br />
you wish to preserve the contents in the unit as disk files on the HMI. This option requires one or more section names. DOWN - This option will download a binary file from the HMI to the Mark V. It is<br />
<br />
used when configuring the Mark V. This option requires one or more section name. DIR - This option will provide a directory of the current contents of the Mark V.<br />
<br />
This option does not required a section name, all sections are shown. CHECK - This option will check the non-volatile memory for possible corruption. This is accomplished by looking at the checksum field in the EEPROM header and<br />
<br />
comparing the expected checksum with the actual checksum. Some sections (such as the totalizer data) do not use a checksum, these sections are skipped in this check. This option does not require a section name. NOCHECK - This option marks a particular section as NOT using a checksum.<br />
<br />
Currently the totalizer data (TOTD) section is the only section that is marked to not use a checksum - due to it constantly changing values. This option requires a section name, which is typically only the TOTD section. HELP - A help screen is provided. EXIT - The EEPROM program will exit. This is typically used as the command in<br />
<br />
the last line in a batch file driven download.<br />
<br />
In addition to the individual sections (or partitions) in the EEPROM, two special pseudo section names are provided which act as a collection of the other sections. These include:<br />
<br />
196 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
ALL - This pseudo section means all of the sections, including the Format section. This is a dangerous section when used with the Down option, it reformats the entire EEPROM and downloads all the sections. This erases all information (including totalizer data) already in the EEPROM. This option is seldom used with a download, and a confirmation will be requested by the program if this pseudo section name is used in a download. This pseudo section is most commonly used with the Up option to upload all sections prior to a unit upgrade. USER - This pseudo section means all of the sections except the FORMAT and TOTD<br />
<br />
sections. This is commonly used to download all of the user-configured sections after rebuilding the panel configuration. Consider the example below: F:\UNIT1>EEPROM DIR T1 R DIRECTORY OF UNIT T1 PROCESSOR R: Partition offset size --------date-------SEQ 5000 243A 03-MAY-1997 12:36:48 CONST 2000 1000 03-MAY-1997 12:36:26 IOCFG 4000 00CB 24-MAY-1995 13:10:56 UBBL 4800 0117 24-NOV-1993 13:54:34 HIST 0000 0000 03-MAY-1997 12:36:26 EPA 0000 0000 03-MAY-1997 12:36:26 MAOUT 0DD0 003C 03-MAY-1997 12:36:26 EVENT 0E60 007A 03-MAY-1997 12:36:26 CHNG 0F60 0100 03-MAY-1997 12:36:28 BOI 12E0 02B6 03-MAY-1997 12:36:28 TOTT 0C00 00A9 03-MAY-1997 12:36:28 TOTD 0200 0910 11-MAR-1992 16:40:48 CBLR 1160 0006 03-MAY-1997 12:36:28 F:\UNIT1><br />
<br />
03-DEC-1997 10:28:53 cksum -id4E28 SEQ 0936 CNST 2C8F IO 6B5A UBL 0000 HIST 0000 EPA 0FCD 4-20 2570 EVNT 38BD CHNG 847A BOI 1EAF TOTT 0000 TOTD CAFE CBLR<br />
<br />
Application Information The date and time in the EEPROM header is a copy of the date and time from the file used to download the panel. This means that the date represents the information in the panel, not the date that the information was downloaded to the panel. Doing this helps to correlate the information in the unit to the HMI disk files that were used to configure the panel. If a file is uploaded from the unit, the date and time on the HMI will be set to the date and time from the EEPROM header. There is a default layout for the EEPROM built into the EEPROM program. The default layout defines what EEPROM partitions exist, where each one starts in the EEPROM, and how large each partition is. Most sites use this default layout with no problems. Some sites and some product lines redefine the layout to resize the partitions or to allow for a larger EEPROM supplied on some jobs. This is done using the EEPROM.DAT file in the unit configuration directory. If no EEPROM.DAT file exists, the program assumes the default layout. If EEPROM.DAT exists, it uses the partition layout defined in that file. If the partition layout is changed, the EEPROM will need to be completely reformatted and downloaded for the change to take effect. If a different EEPROM layout is required in the <B> controllers than the <Q> controllers, separate EEPROM_B.DAT and EEPROM_Q.DAT files can be used.<br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 197<br />
<br />
The header of the EEPROM contains some unit specific information including this unit’s ARCNET address, whether the unit is a Simplex or a TMR, and the base frame rate. This information, along with the EEPROM directory and partition layout, is stored in a special partition known as FORMAT. Downloading the FORMAT partition to the unit will re-format the EEPROM, loosing all the contents. (The FORMAT partition is not included in the USER pseudo section.) Because of the unit specific information in the FORMAT section, extra care needs to be taken if the FORMAT section is copied from one unit configuration to another.<br />
<br />
UDF Overview UDF (User Defined File) is a Mark V LM configuration utility that downloads the<br />
<br />
binary configuration information from the HMI into the non-volatile memory (a disk drive) in the Mark V LM control panel. (UDF is not used for the Mark V - it uses the EEPROM program instead.) Various configuration tools create the *.AP1 files that define the configuration of the Mark V LM turbine control. 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. These files must be downloaded from the HMI to the nonvolatile memory in the control panel for them to take effect. UDF is used to copy these files to the Mark V LM non-volatile memory. The Mark V LM uses a disk drive as its non-volatile memory to hold these files. UDF is the program that transfers the files between the disk drive in the Mark V LM and the unit configuration directory on the HMI. It also provides a directory command to view the contents of the Mark V LM disk drive, and will do a simple sanity check to verify the unit’s files have not been corrupted.<br />
<br />
198 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Operation UDF is a command line utility program that is typically run from a DOS prompt.<br />
<br />
When the program is run it prompts the user for the desired unit. This must be a Mark V LM unit. (Entering a question mark when prompted for the unit name will provide a list of valid Mark V LM unit names.) The user is then prompted for which controller to talk to, with the default being the <R> controller. UDF then drops into a loop prompting the user with its "UDF>" prompt. The Help command providing the list of commands is shown below. A special condition exists when a Mark V LM panel is first loaded. The sequence for loading a panel (somewhat simplified) is as follows: Use the serial download via RS-232 cable to load the operating system with ARCNET communications support into the panel Use the ARCNET to download the rest of the configuration files to the panel The serial download to the panel gives the panel enough software to be able to talk on the ARCNET, but not enough software to perform as a turbine control unit. In this condition, the panel is not able to function as a unit, so it will not understand if its address is specified as a unit name. For UDF to contact the unit, the ARCNET address of the panel must be used instead of the unit name. To do this, when asked for the unit name enter instead "0x" followed by the ARCNET address. This allows the UDF program to talk to a particular address, even before the unit software has been downloaded to it. When the ARCNET address is used, one additional question has to be asked, that of which core the address maps to. This is typically the <R> core, which is the default answer. The UDF program has the ability to run from a remote node by using the "/NODE=<nodename>" option on the command line. This is intended for cases where the unit must be contacted from a remote location through the HMI. The nodename is the name of the HMI that is going to act as a passthrough node for the UDF messages. When run from a remote location, the unit name can not be used to specify the unit, the ARCNET address must be used instead. Review the examples below: F:\UNIT1>UDF Enter the Unit Name: T1 Enter the target core (R, S, T) [R]: Attached to <88:R> via <R>. UDF> F:\UNIT1>UDF Enter the Unit Name: 0x88 Enter the Control Engine the LUN is for (R,S,T) [R]: Enter the target core (R, S, T) [R]: Attached to <88:R> via <R>. UDF><br />
<br />
GEH-6126<br />
<br />
Chapter 6 Configuration • 199<br />
<br />
UDF> HELP COMMAND FORMAT: UDF [/NODE=\\nodename] AVAILABLE COMMANDS: AP1 [filespec...] - Remote AP1 file check CD [dir] - Remote change directory CRC [filespec...] - Remote CRC command DELETE [filespec*...] - Remote delete command DIR [filespec*...] - Remote directory command EXEC [filespec*...] - Mark file(s) as executable FLASH [filespec*...] - Send files to remote FLASH FREE [dir] - Get free space in directory GET [filespec...] - Get files from remote LCD [dir] - Local change directory LCRC [filespec*...] - Local CRC command LDIR [filespec*...] - Local directory command MD [dir] - Remote make directory RD [dir] - Remote remove directory SEND [filespec*...] - Send files to remote STAT*US - Show status of settings AVAILABLE OPTIONS: AUTOEXEC { ON | OFF } - Marks no-extension files as Execs CASE { NONE | UPPER | LOWER } - Forces case of remote names SEP*ARATOR { "/" | "\" } - Defines remote directory specifier TRACE { ON | OFF } - Enable/Disable trace buffer RESTART - Restart with new connection EXIT, BYE, QUIT - Leave the program [parameter] parameters are optional "filespec*" parameters can include the wildcards "*" and "?" "filespec..." parameters can be a list, separated by spaces Attached to <88:R> via <R>. UDF><br />
<br />
The date and time on the unit’s disk drive is a copy of the date and time from the file used to download the panel. This means that the date represents the information in the panel, not the date that the information was downloaded to the panel. Doing this helps to correlate the information in the unit to the HMI disk files that were used to configure the panel. If a file is uploaded from the unit, the date and time on the HMI will be set to the date and time from the unit’s disk drive.<br />
<br />
200 • Chapter 6 Configuration<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control<br />
<br />
Remote Access All remote access will be through a Remote Access Service (RAS) connection. The computer phoning the site will have to have Dial Up Networking capability. A connection will have to be made to the HMI computer with RAS. To do this, you will need a user account and password on the HMI. The protocols to communicate over the RAS connection will be TCP/IP and NetBEUI. Most of the communications will use TCP/IP. NetBEUI resolves names when mounting remote disks.<br />
<br />
Web Interface Demand Display – This display allows the display of the values of a selected list of<br />
<br />
points. Any point in the data dictionary can be displayed by typing in the point name. You can add new Point Lists or modify the points contained in a Point List by editing the F:\WDEMAND.DAT file. Process Alarms – This display shows a list of the current process alarms. Diagnostic Alarms – This display shows a list of the current diagnostic alarms. Logic Forcing – This display shows a list of all the forced points in the unit. It does not allow the forcing or unforcing of points. Control Constants – This display shows each of the control constants and its current<br />
<br />
value. HMI Startup log – This display shows the last startup log file for this HMI.<br />
<br />
(Browse) – This allows you to pick the log file you would like to see. You can then display the log file. Point Browser – This display shows all the points in the data dictionary for the<br />
<br />
selected unit. ARCWHO – This display shows all the nodes that are alive on the ARCNet.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 201<br />
<br />
FTP Interface The FTP Interface will allow the transfer of files to and from the HMI. The only directories that will be accessible will be the ones below the ftp-root directory. Virtual directories can be used to make any directory appear in the ftp-root directory.<br />
<br />
Remote Mount Disks You can mount disks from the HMI to your computer. This allows you to copy files to and from the HMI.<br />
<br />
GE Industrial Systems Standard Message Formats Introduction This document defines message formats available to DCS vendors for data collection and process control. It does not define the message transport mechanism although that is presumed to be a TCP over IP system. GE INDUSTRIAL SYSTEMS (GEIS) Standard Messages are application level messages. These application level messages will be collectively referred to as GSM in this document. GSM messages are processed by software in an intervening box or gateway to the process controllers. These gateways, in turn, can communicate directly with potentially several process controllers. The general function of the intervening box is to act as a protocol translator yielding a consistent external interface regardless of internal protocols and data representations used. No data will be emitted from the gateway unless previously requested by the DCS equipment. Note The intervening box may or may not be only a gateway in function. However, the remainder of this document will continue to refer to the intervening box as a gateway.<br />
<br />
Notation Unless otherwise noted all data is specified in Little Endian format. This is the byte order for Intel processors. For multi-byte data, the least significant byte is transmitted first while the most significant byte is transmitted last. For notational convenience, multi-byte data is shown below such that the most significant byte is to the left; least significant byte is on the right; but the transmission sequence of bytes will be right to left. For example, a 32-bit integer value is shown as follows: <------------------TRANSMISSION SEQUENCE Bit # 31 0 ±µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ£ ¢ M.S.B. L.S.B. ¢ °µµµµµµµµµ·µµµµµµµµµ·µµµµµµµµµ·µµµµµµµµµ¤<br />
<br />
202 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Many messages have Name fields within them. The format of a Name field will in all cases, except parameter list entries (see below), will be a counted-ASCII string, where the first byte transmitted is treated an unsigned number n followed by the name itself. The first byte following n is the leftmost character in the name. Note that n may be zero. For notational illustration, Name fields will shown generically as follows: ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ£ ¢ (ASCIIC) <n> ¢ °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ·µµµµµµµµµ¤ Similar to Name fields, many messages have records defined. In these instances, each record will be identified by a Record Identifier or Record Type, followed by record size, followed by record specific information. Note that n (record size) may be zero. For notational illustration, records will be shown generically as follows: ±µµµµµµµ¹µµµµµµµµµ£ ¢ <Record Type> ¢ ´µµµµµµµ¹µµµµµµµµµ¡ ¢ <Size> ¢ ±µµµµµµµµµ¹µµµµµµµµ/../°µµµµµµµµµµµµµµµµµ¡ ¢ <Record specific illustration> ¢ °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ·µµµµµµµµµ¤ Most records within GSM messages are made up of groups of sub-records, which are implemented as parameter lists. Each item in a parameter list consists of at least two 16-bit words. The first word identifies the parameter. The second word identifies the number of bytes to follow which qualify the parameter. These two words are then followed by zero or more bytes (as defined by the second word). Software may use the parameter size to skip unknown parameters.<br />
<br />
Generic records containing parameter lists can be illustrated as follows: ±µµµµµµµ¹µµµµµµµµµ£ ¢ <Record Type> ¢ ´µµµµµµµ¹µµµµµµµµµ¡ ¢ <Total Size> ¢ ´µµµµµµµ¹µµµµµµµµµ¡ ¢ Item Code #1 ¢ ´µµµµµµµ¹µµµµµµµµµ¡ ¢ Qual. #1 Size ¢ °µµµµµµµµµµµµµµµµµ¡ Param #1 Qualifier ¢ .../ /... µµµµµµµµµµ¤ . . ±µµµµµµµ¹µµµµµµµµµ£ ¢ Item Code #n ¢ ´µµµµµµµ¹µµµµµµµµµ¡ ¢ Qual. #n Size ¢ °µµµµµµµµµµµµµµµµµ¡ Param #n Qualifier ¢ .../ /... µµµµµµµµµµ¤<br />
<br />
A special item code with a value of 0x0000 is the End-of-list item code. Even if the total record size indicates space for more item list entries, no interpretation of data beyond End-of-list should be attempted. Software that scans item lists must simply bypass unknown or previously undefined item code entries. Item Codes and Record Types have unique values. No item code will have the same value as a defined record type.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 203<br />
<br />
Most data messages have time tagged data points within them. All time tags are represented using GE INDUSTRIAL SYSTEMS Standard Time. The GE INDUSTRIAL SYSTEMS standard time representation is a structure consisting of 2 unsigned longwords (32 bits each). The first longword is the number of seconds since 1-JAN-1970 00:00:00.000000 GMT. The second longword is the number of microseconds within the second, having a decimal range of 0-999,999. The latest date and time that can be stored using this representation is 07-FEB-2106 06:28:15.999999 GMT. The layout of a time tag is illustrated below: Byte Bit # 31 0 Offset ±µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ£ ¢ Seconds since 1-JAN-1970 00:00 GMT. ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Microseconds ¢ 4 °µµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµµ¤ Within a message format specification, the time tag will be merely illustrated as: ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ£ ¢ 8 Byte Timetag ¢ °µµµµµµµµµµµµµµµµµµ/../µµµµµµµµµµµµµµµµµµ¤ Many of the message formats have fields within them defined as RESERVED or MBZ. These fields are intended for use in future versions of the GSM specification. To preserve backward/forward compatibility, software, which generates GSM messages, must fill in RESERVED and MBZ fields with zeros; and software that receives GSM messages must ignore these fields.<br />
<br />
GSM allows data acquisition/control of multiple process controllers. Part of the generic GSM messages is a small message header. This message header consists of three parts: a 16-bit message code; a 16-bit sequence number; and an ASCIIC process controller name. The message code identifies the requested function (data acquisition, command etc.). The sequence number is an arbitrary number generated by the data/command requester to uniquely identify a given request; all responses to a given request message will have this sequence number echoed back allowing stale data to be thrown away. The ASCIIC controller name defines which controller within a multi-controller site the request is directed. A GSM message has the following generic form: Message Offset ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ Message Code ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ³µµµµµµµµµ¡ . Message . . Specific.<br />
<br />
Timetag Considerations As shown above the resolution of the GE INDUSTRIAL SYSTEMS Standard Time tag is 1 Microsecond. All time tagged data is stamped at the source of the data, using the resolution available in the local process controller. The resolution of time stamps in the local process controller is usually less than 1 microsecond (i.e. it’s more coarse).<br />
<br />
204 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Other considerations on time tagging include I/O scan rates used. For example, certain control functions may only scan inputs at an 8 Hz. rate. This means that consecutive data samples collected will be time tagged in multiples of 125 milliseconds. Other controllers, such as the SOE (Sequence Of Events) scanner in Mark V controller run at a much higher rate like every 122 microseconds. Time tag accuracy or coherency across different process controllers is the subject of time setting and time synching. GSM does not define the capability of time setting via messages over a network nor does it allow the concept of time synching process controllers over a network. Where required, time setting/time synching of process controllers can be handled by external equipment utilizing a common time reference. Time tag coherency in these cases will be achieved to an accuracy as demanded by system requirements. High-resolution time tagged data does not necessarily imply speedy reporting of data. Some process controllers for example, may buffer multiple pieces of time tagged data into envelopes which are delivered at a later time. Due to the asynchronous nature of delivering buffered time tagged data, it is both possible and likely that different pieces of data will not be delivered in chronological order.<br />
<br />
GSM Message Type Summary GSM supports the following types of request messages: •<br />
<br />
Administrative requests<br />
<br />
•<br />
<br />
Requests for event-driven data.<br />
<br />
•<br />
<br />
Requests for periodic data.<br />
<br />
•<br />
<br />
Command requests.<br />
<br />
Administrative requests are not associated with a single process controller. These requests are DCS to gateway messages, mainly to interrogate the capability of the gateway. Event-driven data messages are spontaneously sent messages sent as a result of a change in state. There are several classes of event driven data. These include:<br />
<br />
GEH-6126<br />
<br />
•<br />
<br />
Changes in process alarm state.<br />
<br />
•<br />
<br />
Changes in digital input.<br />
<br />
•<br />
<br />
Software detected changes in pre-defined Boolean variables.<br />
<br />
•<br />
<br />
Deadband crossings detected in pre-defined analog variables.<br />
<br />
•<br />
<br />
Changes in controller alarm (diagnostic) state.<br />
<br />
Chapter 7 Remote Access and Control • 205<br />
<br />
Periodic data consists of sets of data requested to be transmitted back to the requester either once, or periodically at rates up to once per second. This data typically is used for updating status displays. Command requests fall into two generic classes: •<br />
<br />
Process alarm command requests.<br />
<br />
•<br />
<br />
Process command requests either in the form of momentary contact push buttons or in the form of analog setpoints.<br />
<br />
It should be noted that command requests may be rejected by the local controller or may be blocked by the gateway as dictated by system requirements.<br />
<br />
Administrative Message Formats Supported Controller Request: This request from the DCS to the gateway is used by the DCS to determine what process controllers the gateway can communicate with, along with current communication status. Note that this is a DCS-to-gateway message, and as such the Controller Name field is inappropriate. The gateway will ignore this field, but the DCS should still fill it in as a zero length name. The format of the Supported Controller Request message is shown below: Message Offset<br />
<br />
±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0100 ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµµµµµµµµµµµ¤<br />
<br />
206 • Chapter 7 Remote Access and Control<br />
<br />
NOTES<br />
<br />
Message Code Field Ignored<br />
<br />
GEH-6126<br />
<br />
Supported Controller Response The gateway will respond to the previously described request with a list of supported controllers, controller type, and current communication status. The response is a list of parameter lists where each parameter list defines information about a single controller. The format of the response is shown below. Message Offset<br />
<br />
NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0101 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 From request °µµµµµµµµµ³µµµµµµµµµ¡ ¢ 0 ¢ 4 ASCIIZ Controller Name ±µµµµµµµµµ²µµµµµµµµµ¡ ¢ Reserved ¢ 5 *1 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ 7 Record Type *2 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ 9 Size of Response ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8100 ¢11 First Controller Info *3 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ 13 Size of Controller Info °µµµµµµµµµµµµµµµµµµµ¡ First Controller Information ¢ 15 Parameter List *4 ...// µµµµµµµµµµµµµµµµµµµµ¤ ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8100 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Controller Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ . . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8100 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Controller Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
15+Size2 *3 Parameter List<br />
<br />
*3 Parameter List<br />
<br />
This response contains a list of parameter lists (denoted by *2), and is identified by a record type value of 0x8000. Each parameter list corresponds to a supported controller. Possible parameters are shown below: ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1000 ¢ Param ID = Controller Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of controller name. °µµµµµµµµµµµµµµµµµµ¡ Controller Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 207<br />
<br />
This parameter defines the name of the controller. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1010 ¢ Param ID = Active Comm Links ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Number of active links. °µµµµµµµµµµµµµµµµµµ¤ This parameter defines the number of communication links that are currently active between the gateway and the controller. A value of zero indicates that the gateway supports the controller, but cannot currently communicate with it. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1020 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Controller type Parameter size. Controller type..<br />
<br />
This parameter defines the controller type. Currently defined Controller Types are: •<br />
<br />
0001 – Turbine Controller<br />
<br />
•<br />
<br />
0002 – CIMPLICITY<br />
<br />
Other values will be defined in the future.<br />
<br />
Heartbeat Message The DCS requests to be placed on various distribution lists as defined later in this document. The Heartbeat message is merely a keep-alive message in a DCS-toGateway administrative message. This message should be transmitted by the DCS approximately every 20 seconds. If the gateway does not receive a heartbeat message from the DCS for a period of 60 seconds, any data lists currently defined on behalf of the DCS will be automatically canceled and the connection to the DCS will be terminated. The gateway does not respond to heartbeat messages. The format of the Heartbeat message is shown below:<br />
<br />
±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0200 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµµµµµµµµµµµ¤<br />
<br />
208 • Chapter 7 Remote Access and Control<br />
<br />
Message Offset NOTES 0<br />
<br />
Message Code<br />
<br />
2<br />
<br />
Field Ignored<br />
<br />
4<br />
<br />
Field Ignored<br />
<br />
GEH-6126<br />
<br />
Event-Driven Data Messages Alarm Record Establish Request This message requests the gateway to place/remove the DCS on/from the distribution list for process alarm messages. Process alarm messages defined below are container messages that are issued spontaneously any time a process alarm changes state. State changes include transitions in alarm value; alarm lock/unlock transitions; and removal of an alarm from the process controller’s alarm queue (if supported in the controller). For CIMPLICITY alarms, a resource ID may be substituted for the Controller name and only alarms for that resource will be forwarded to the DCS. The gateway always responds to this request with an establish ACK/NAK message. The format of the alarm establish request is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0300 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Alarm Function ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Alarm Function has 2 defined values. 0x0000 requests that the DCS be added to the alarm distribution list for the specified controller. 0xFFFF requests that the DCS be removed from the alarm distribution list. All other values are reserved. Options request other information be included in spontaneously sent alarm messages. Bit 0 = 1 requests that alarm text be included in alarm messages; otherwise alarm text will be omitted. Bits 1-15 are reserved and must be zero.<br />
<br />
Alarm Record Establish ACK/NAK Response The gateway responds to an alarm establish request with an establish ACK/NAK response. The format of the establish ACK/NAK response is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0301 ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0300 ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Alarm Function ¢ 7+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Status ¢ 9+n °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
GEH-6126<br />
<br />
Message Code (Echoed) Controller Name Establish Code (Echoed) ACK/NAK Code<br />
<br />
Chapter 7 Remote Access and Control • 209<br />
<br />
The Sequence Number, Controller Name and Alarm Function are echoed from the alarm establish request. The establish code = 0x0300 for an alarm ACK/NAK response. Possible ACK/NAK codes are: •<br />
<br />
0 – Success.<br />
<br />
•<br />
<br />
+1 – DCS on Gateway's distribution list. Communication with process controller is not currently possible.<br />
<br />
•<br />
<br />
-1 – Unknown Controller Name.<br />
<br />
•<br />
<br />
-2 – Function not supported by process controller.<br />
<br />
•<br />
<br />
-3 – Gateway distribution list table is full.<br />
<br />
•<br />
<br />
-4 – Malformed request.<br />
<br />
Alarm Data Messages Alarm data messages are sent spontaneously to any DCS, which has been placed on the gateway's distribution list for alarm messages. Alarm data messages are container messages containing 1 or more alarms, which have changed state. These messages do not provide current status of all alarms. This message contains a list of parameter lists where each parameter list defines information about a single alarm. Not all process controllers support all possible parameters. Information not relevant to a given process controller will be missing.<br />
<br />
210 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0302 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8300 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ °µµµµµµµµµµµµµµµµµµµ¡ First Alarm Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Alarm Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Alarm Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message Offset<br />
<br />
NOTES<br />
<br />
0<br />
<br />
Message Code<br />
<br />
2<br />
<br />
From Estab. Request<br />
<br />
4<br />
<br />
Controller Name<br />
<br />
5<br />
<br />
*1<br />
<br />
7<br />
<br />
Record Type *2<br />
<br />
9<br />
<br />
Size of Response<br />
<br />
11<br />
<br />
First Alarm Info *3<br />
<br />
13<br />
<br />
Size of Alarm Info<br />
<br />
15<br />
<br />
Parameter List *4<br />
<br />
15+Size2 *3 Parameter List<br />
<br />
*3 Parameter List<br />
<br />
These messages contain a list of parameter lists (denoted by *2), and is identified by a record type value of 0x8000. Each parameter list corresponds to a single alarm, which has changed state. Possible parameters are shown below: ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Point Name Size of point name.<br />
<br />
This parameter defines the short name of the alarm. This parameter is not included if the gateway is incapable of translating the alarm drop into its short name form. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Timetag Parameter size. Alarm Queue Time<br />
<br />
This parameter is the time tag associated with the alarm record.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 211<br />
<br />
±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1050 ¢ Param ID = Alarm Drop Number ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Drop Number °µµµµµµµµµµµµµµµµµµ¤ This parameter identifies the alarm drop number. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ Param ID = Alarm State ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Alarm State °µµµµµµµµµ¤ Bit 0 defines the current state of the alarm. Bit 0 = 0 if out of alarm. Bit 0 = 1 if in alarm. All other bits are reserved. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1070 ¢ Param ID = Alarm Lock State ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Alarm Lock State °µµµµµµµµµ¤ Bit 0 defines the current state of the alarm. Bit 0 = 0 if alarm is not locked. Bit 0 = 1 if alarm is locked. All other bits are reserved. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1080 ¢ Param ID = Reason Code ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Reason Code °µµµµµµµµµ¤ This parameter is used for remote alarm queue management. It defines why the alarm record is being sent. The following list defines reason codes:<br />
<br />
0x00 = Not used 0x01 = Alarm state just transitioned. 0x02 = Alarm just locked. 0x03 = Alarm just unlocked. 0x04 = Reserved. 0x05 = Alarm just re-triggered. Reset time tag in alarm queue. 0x06 = Reserved. 0x07 = Alarm just acknowledged. 0x08 = Alarm reset. Remove alarm from alarm queue. 0x09 = Alarm Dump Record. 0xFE = End of Alarm Dump. 0xFF = Clear Alarm Queue to prepare for alarm dump. All other values are reserved.<br />
<br />
212 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ Param ID = Long Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of long name. °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ This parameter defines the long name (text) associated with the alarm. This information is not sent if it is not requested in the alarm establish message. Text size will be zero if the gateway cannot provide the associated text. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10A0 ¢ Param ID = Alarm Seq. Number ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Alarm Sequence Number °µµµµµµµµµµµµµµµµµµ¤ This parameter identifies the alarm record sequence number. Each alarm queue has a sequence number, which is incremented for every alarm record. The alarm sequence number is provided for remote alarm queue management. If the remote alarm queue sequence number (plus 1) does not equal this sequence number, then the remote alarm queue is out-of-sync with the process controller’s alarm queue. In this event, the DCS should request an alarm dump (See alarm commands defined later in this document) to re-synchronize. Note that this value is a two byte-unsigned integer and will rollover after 0xFFFF. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10C0 ¢ Param ID = Alarm ACK State ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Alarm ACK State Value °µµµµµµµµµ¤ Bit 0 defines the Acknowledged state of the alarm. Bit 0 = 0 if the alarm has not been acknowledged. Bit 0 = 1 if the alarm has been acknowledged. All other bits are reserved. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10D0 ¢ Param ID = Point ID Hint ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Point ID Hint Value °µµµµµµµµµµµµµµµµµµ¤ The gateway will send this parameter if it cannot translate the alarm drop number into its short name form. Reception of this parameter indicates incomplete translation tables in the gateway. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ °µµµµµµµµµµµµµµµµµµ¤ No more information about this alarm follows.<br />
<br />
Param ID = END-OF-LIST Parameter size.<br />
<br />
Digital Input Record Establish Request This message requests the gateway to place/remove the DCS on/from the distribution list for digital input messages. Digital input messages defined below are container messages that are issued spontaneously any time a digital input in the process controller changes state (if supported in the controller). The gateway always responds to this request with an establish ACK/NAK message.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 213<br />
<br />
The format of the digital input establish request is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0400 ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message Code Controller Name<br />
<br />
Establish Function has 2 defined values. 0x0000 requests that the DCS be added to the digital input distribution list for the specified controller. 0xFFFF requests that the DCS be removed from the distribution list. All other values are reserved. Options request other information be included in spontaneously sent digital input messages. Bit 0 = 1 requests that longname descriptive text be included in any generated digital input messages; otherwise longname text will be omitted. Bits 1-15 are reserved and must be zero.<br />
<br />
Digital Input Record Establish ACK/NAK Response The gateway responds to a digital input establish request with an establish ACK/NAK response. The format of the establish ACK/NAK response is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0301 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 (Echoed) ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0400 ¢ 5+n Establish Code ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 7+n (Echoed) ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Status ¢ 9+n ACK/NAK Code °µµµµµµµµµµµµµµµµµµ¤ The Sequence Number, Controller Name and Establish Function are echoed from the digital input establish request. The establish code = 0x0400 for a digital input ACK/NAK response.<br />
<br />
Possible ACK/NAK codes are: 0 – Success. +1 – DCS on Gateway's distribution list. Communication with process controller is not currently possible. -1 – Unknown Controller Name. -2 – Function not supported by process controller. -3 – Gateway distribution list table is full. -4 – Malformed request.<br />
<br />
214 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Digital Input Data Messages Digital input data messages are sent spontaneously to any DCS, which has been placed on the gateway’s distribution list for digital input messages. Digital input data messages are container messages containing 1 or more inputs which have changed state. This message contains a list of parameter lists where each parameter list defines information about a single digital input. Not all process controllers support all possible parameters. Information not relevant to a given process controller will be missing.<br />
<br />
±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0402 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8400 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ °µµµµµµµµµµµµµµµµµµµ¡ First Digital Input Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8400 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Digital Input Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8400 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Digital Input Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message Offset<br />
<br />
NOTES<br />
<br />
0<br />
<br />
Message Code<br />
<br />
2<br />
<br />
From Estab. Request<br />
<br />
4<br />
<br />
Controller Name<br />
<br />
5+n<br />
<br />
*1<br />
<br />
7+n<br />
<br />
Record Type *2<br />
<br />
9+n<br />
<br />
Size of Response<br />
<br />
11+n<br />
<br />
First Digin Info *3<br />
<br />
13+n<br />
<br />
Size of Digin Info<br />
<br />
15+n<br />
<br />
Parameter List *4<br />
<br />
15+Size2 *3 Parameter List<br />
<br />
*3 Parameter List<br />
<br />
These messages contain a list of parameter lists (denoted by *2), and is identified by a record type value of 0x8000. Each parameter list corresponds to a single digital input, which has changed state. Possible parameters are shown below: ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Point Name Size of point name.<br />
<br />
This parameter defines the short name of the digital input. This parameter is not included if the gateway is incapable of translating the digital input number into its short name form.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 215<br />
<br />
±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Timetag Parameter size. Alarm Queue Time<br />
<br />
This parameter is the time digital input changed state. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµ¤<br />
<br />
Param ID = Digin State Parameter size. Digital Input State<br />
<br />
Bit 0 defines the current state of the digital input. All other bits are reserved. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Long Name Size of long name.<br />
<br />
This parameter defines the long name (text) associated with the digital input. This information is not sent if it was not requested in the digital input establish message. Text size will be zero if the gateway cannot provide the associated text. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10D0 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Point ID Hint Parameter size. Point ID Hint Value<br />
<br />
The gateway will send this parameter if it cannot translate the digital input number into its short name form. Reception of this parameter indicates incomplete translation tables in the gateway. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ Param ID = END-OF-LIST ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ Parameter size. °µµµµµµµµµµµµµµµµµµ¤ No more information about this digital input follows.<br />
<br />
216 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Software Event Record Establish Request This message requests the gateway to place/remove the DCS on/from the distribution list for software event messages. Event messages defined below are container messages that are issued spontaneously any time a logic variable in the process controller changes state (if supported in the controller). Which logic variables defined to be software change detected is predefined in the process controller. The gateway always responds to this request with an establish ACK/NAK message. The format of the software generated event establish request is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0500 ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message Code Controller Name<br />
<br />
Establish Function has two defined values. 0x0000 requests that the DCS be added to the event message distribution list for the specified controller. 0xFFFF requests that the DCS be removed from the distribution list. All other values are reserved. Options request other information be included in spontaneously sent event messages. Bit 0 = 1 requests that longname descriptive text be included in any generated digital input messages; otherwise longname text will be omitted. Bits 1-15 are reserved and must be zero.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 217<br />
<br />
Software Event Record Establish ACK/NAK Response The gateway responds to a event establish request with an establish ACK/NAK response. The format of the establish ACK/NAK response is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0301 ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0500 ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 7+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Status ¢ 9+n °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message Code (Echoed) Controller Name Establish Code (Echoed) ACK/NAK Code<br />
<br />
The Sequence Number, Controller Name and Establish Function are echoed from the event establish request. The establish code = 0x0500 for an event ACK/NAK response. Possible ACK/NAK codes are: 0 – Success. +1 – DCS on Gateway's distribution list. Communication with process controller is not currently possible. -1 – Unknown Controller Name. -2 – Function not supported by process controller. -3 – Gateway distribution list table is full. -4 – Malformed request.<br />
<br />
218 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Software Event Data Messages Software event data messages are sent spontaneously to any DCS, which has been placed on the gateway’s distribution list for event messages. Event data messages are container messages containing 1 or more logic points, which have changed state. This message contains a list of parameter lists where each parameter list defines information about a single logic variable. Not all process controllers support all possible parameters. Information not relevant to a given process controller will be missing.<br />
<br />
±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0502 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8500 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ °µµµµµµµµµµµµµµµµµµµ¡ First Event Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message Offset<br />
<br />
±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8500 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Event Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8500 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Event Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
NOTES<br />
<br />
0<br />
<br />
Message Code<br />
<br />
2<br />
<br />
From Estab. Request<br />
<br />
4<br />
<br />
Controller Name<br />
<br />
5<br />
<br />
*1<br />
<br />
7<br />
<br />
Record Type *2<br />
<br />
9<br />
<br />
Size of Response<br />
<br />
11<br />
<br />
First Event Info *3<br />
<br />
13<br />
<br />
Size of Event Info<br />
<br />
15<br />
<br />
Parameter List *4<br />
<br />
15+Size2 *3 Parameter List<br />
<br />
*3 Parameter List<br />
<br />
These messages contain a list of parameter lists (denoted by *2), and is identified by a record type value of 0x8000. Each parameter list corresponds to a single logic value, which has changed state. Possible parameters are shown below: ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Point Name Size of point name.<br />
<br />
This parameter defines the short name of the event. This parameter is not included if the gateway is incapable of translating the event number into its short name form.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 219<br />
<br />
±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ Param ID = Timetag ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ Parameter size. ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ Alarm Queue Time °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤ This parameter is the time logic variable changed state. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµ¤ Bit 0 defines the current state of the logic variable. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Event State Parameter size. Event State<br />
<br />
All other bits are reserved. Param ID = Long Name Size of long name.<br />
<br />
This parameter defines the long name (text) associated with the event. This information is not sent if it was not requested in the software event establish message. Text size will be zero if the gateway cannot provide the associated text. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10D0 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Point ID Hint Parameter size. Point ID Hint Value<br />
<br />
The gateway will send this parameter if it cannot translate the event number into its short name form. Reception of this parameter indicates incomplete translation tables in the gateway. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ °µµµµµµµµµµµµµµµµµµ¤ No more information about this event follows.<br />
<br />
220 • Chapter 7 Remote Access and Control<br />
<br />
Param ID = END-OF-LIST Parameter size.<br />
<br />
GEH-6126<br />
<br />
Periodic Data Messages Periodic Data Request The DCS can define lists of data to be returned on a periodic basis. This is typically used to maintain real time databases for display purposes. Using this method, any data point defined in the process controller (and also defined in the gateway’s database) can be returned to the DCS. Multiple data lists may be defined by the DCS. Limitations are placed on list definitions based on the controller as shown below. Controller<br />
<br />
Max Points<br />
<br />
Max Lists<br />
<br />
Mark V<br />
<br />
96<br />
<br />
32<br />
<br />
Mark V LM<br />
<br />
50<br />
<br />
64<br />
<br />
CIMPLICITY<br />
<br />
300<br />
<br />
no maximum<br />
<br />
The gateway will respond to a periodic data definition with a periodic data ACK/NAK message.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 221<br />
<br />
The format of a periodic data list definition is shown below: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0600 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ List Name ¢ 7+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Period Code ¢ 9+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x1030 ¢11+n Pointname Param ´µµµµµµµµ¹µµµµµµµµµ¡ List ¢ <Size m> ¢ °µµµµµµµµ¹µµµµµµµµµ¡ First Point Name ¢ ..//..µµµ³µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x1030 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size x> ¢ °µµµµµµµµ¹µµµµµµµµµ¡ Second Point Name ¢ ..//..µµµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ ´µµµµµµµ¹µµµµµµµµµ¡ ¢ <Size z> ¢ °µµµµµµµ¹µµµµµµµµµ¡ Last Point Name ¢ ..//..µµµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
List Name combined with Controller Name defines a unique set of data points to be returned. If the request contains a List Name/Controller Name that is identical to a previously defined set, the new request will supersede the previous definition. List Name may be any value. Establish Function has 2 defined values. 0x0000 requests that the data points specified in the request be returned to the DCS according to Period Code. 0xFFFFrequest cancellation of any previously defined list corresponding to List Name/Controller Name. Period Code defines the number of seconds between data transmissions. It is ignored on list cancellation requests. A period code with a value of zero requests the data to be transmitted only once. The Point Name parameter list is ignored on list cancellations. The Point Name parameter is an ASCII string and must match the point name defined in the controller configuration.<br />
<br />
222 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Periodic Data ACK/NAK Response The gateway responds to a periodic data request with a periodic data ACK/NAK response. The format of the periodic data ACK/NAK response is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0601 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 (Echoed) ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0600 ¢5+n Establish Code ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ List Name ¢ 7+n (Echoed) ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 9+n (Echoed) ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Status ¢ 11+n ACK/NAK Code °µµµµµµµµµµµµµµµµµµ¤ The Sequence Number, Controller Name, List Name and Establish Function are echoed from the event establish request. The establish code = 0x0600 for a periodic data ACK/NAK response.<br />
<br />
Possible ACK/NAK codes are: 0 – Success. +1 – DCS on Gateway's distribution list. Communication with process controller is not currently possible. -1 – Unknown Controller Name. -2 – Function not supported by process controller. -3 – Gateway periodic list definition table is full. -4 – Malformed request. -5 – Internal Gateway error. -6 – All points requested are undefined. -7 – Too many data points defined in request.<br />
<br />
Periodic Data Message Periodic data messages are sent periodically to the DCS following the transmission of the periodic data ACK/NAK message at the rate defined in the period code. These messages consist of a small header identifying which data list is contained in the message, followed by a parameter list containing a time tag and point values. For CIMPLICITY data the time tag for the list represents the time tag of the first point in the list. The point value list is transmitted in the same order as defined in the periodic data request. If a requested point is undefined, the returned list entry will show a size of zero. The format of the periodic data message is:<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 223<br />
<br />
Message Offset NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0602 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 From Estab. Request ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ List Name ¢ 5 *1 ´µµµµµµµµµµµµµµµµµµµ¡ ¢ 0x1040 ¢ 7 PARAM = TIMETAG ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ 9 Size of TIMETAG ±µµµµµµµµµµµµµµ/../µµ²µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ 11 °µµµµµµµµµµµµµµ/../µµ³µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x1060 ¢ 19 PARAM = Point Value ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Data Size> ¢ 21 Size of Point Value °µµµµµµµµµµµµµµµµµµµ¡ First Data Value ¢ 23 First Data Value ...// µµµµµµµµµµµµµµµµµµµµ¤ ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ PARAM = Point Value ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Data Size> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Data Value ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ PARAM = Point Value ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Data Size> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Data Value ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
*1 – The List Name is used by the DCS to determine which set of data values are being returned if the DCS has defined multiple lists. Note If the gateway loses communications with the process controller, periodic transmission of these messages will cease. Message transmission will resume automatically when the gateway regains communication with the process controller.<br />
<br />
Command Messages Alarm Command Request This message is used for remote control of the process controller's alarm queue. The alarm command request can be used to acknowledge, reset, lock or unlock alarms or request an alarm dump. Note that not all process controllers will accept all alarm commands. For CIMPLICITY alarms the drop number is generated by the gateway and will not be the same between connections. The gateway always responds to this request with an alarm command ACK/NAK message.<br />
<br />
224 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
The format of the alarm command request is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0700 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Alarm Command ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n °µµµµµµµµµµµµµµµµµµ¤ Options are specified to qualify the alarm command. Available alarm command values, and the meaning of options is shown below:<br />
<br />
Command Value<br />
<br />
Command Function<br />
<br />
Options Meaning<br />
<br />
2<br />
<br />
Lock Single Alarm<br />
<br />
Alarm Drop Number<br />
<br />
3<br />
<br />
Unlock Single Alarm<br />
<br />
Alarm Drop Number<br />
<br />
4<br />
<br />
Acknowledge Alarms<br />
<br />
Number of alarms<br />
<br />
6<br />
<br />
Reset All Alarms<br />
<br />
<Ignored><br />
<br />
7<br />
<br />
Acknowledge 1 Alarm<br />
<br />
Alarm Drop Number<br />
<br />
8<br />
<br />
Reset 1 Alarm<br />
<br />
Alarm Drop Number<br />
<br />
10<br />
<br />
Alarm Silence<br />
<br />
<Ignored><br />
<br />
255<br />
<br />
Request Alarm Dump<br />
<br />
Include Alarm Text Flag *2<br />
<br />
*1<br />
<br />
All other values for alarm command are reserved. *1 – A value of 0xFFFF for options will acknowledge all alarms. Maximum of 12. *2 – Options bit 0 = 1 requests alarm dump include alarm text, otherwise is omitted. Bits 1-15 are reserved.<br />
<br />
Alarm Command ACK/NAK Response The gateway responds to an alarm command request with an ACK/NAK response. The format of the alarm command ACK/NAK response is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0701 ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Alarm Command ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Command Status ¢ 9+n °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
GEH-6126<br />
<br />
Message Code (Echoed) Controller Name (Echoed) (Echoed) ACK/NAK Code<br />
<br />
Chapter 7 Remote Access and Control • 225<br />
<br />
The Sequence Number, Controller Name, Alarm Command and Options are echoed from the alarm command request. Possible ACK/NAK codes are: 0 – Success. Alarm command sent to process controller. +1 – Request received by gateway, but communication with process controller is not currently possible. -1 – Unknown Controller Name. -2 – Function not supported by process controller. -3 – Invalid command. -4 – Malformed request. -5 – Internal Gateway error. -6 – Permission violation due to control hierarchy.<br />
<br />
Alarm Dump Messages Alarm dump messages are nearly identical to alarm data messages described above. Alarm dump messages are sent following the alarm command ACK/NAK message if an alarm dump was requested, and the function is supported by the process controller. Alarm dump messages provide current status of all alarms. Due to the potential size of the entire alarm queue information, this message may be broken up into several GSM messages. The DCS can use the alarm sequence number to synchronize it's own alarm queue. The alarm sequence number in an alarm dump is the latest alarm sequence number used in the process controller. This same number will appear for multi-GSM messages. This message contains a list of parameter lists where each parameter list defines information about a single alarm. Not all process controllers support all possible parameters. Information not relevant to a given process controller will be missing.<br />
<br />
226 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0702 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8300 ¢ ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ °µµµµµµµµµµµµµµµµµµµ¡ First Alarm Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Alarm Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Alarm Information ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message NOTES Offset 0 Message Code 2<br />
<br />
From Estab. Request<br />
<br />
4<br />
<br />
Controller Name<br />
<br />
5<br />
<br />
*1<br />
<br />
7<br />
<br />
Record Type *2<br />
<br />
9<br />
<br />
Size of Response<br />
<br />
11<br />
<br />
First Alarm Info *3<br />
<br />
13<br />
<br />
Size of Alarm Info<br />
<br />
15<br />
<br />
Parameter List *4<br />
<br />
15+Size2 *3 Parameter List<br />
<br />
*3 Parameter List<br />
<br />
These messages contain a list of parameter lists (denoted by *2), and is identified by a record type value of 0x8000. Each parameter list corresponds to a single alarm, which is in the alarm queue. If the alarm queue is empty, there will be one parameter list containing only the End-Of-List parameter. Possible parameters are shown below: ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Point Name Size of point name.<br />
<br />
This parameter defines the short name of the alarm. This parameter is not included if the gateway is incapable of translating the alarm drop into its short name form. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Timetag Parameter size. Alarm Queue Time<br />
<br />
This parameter is the time tag associated with the alarm record.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 227<br />
<br />
±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1050 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Alarm Drop Number Parameter size. Drop Number<br />
<br />
This parameter identifies the alarm drop number. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµ¤<br />
<br />
Param ID = Alarm State Parameter size. Alarm State<br />
<br />
Bit 0 defines the current state of the alarm. Bit 0 = 0 if out of alarm. Bit 0 = 1 if in alarm. All other bits are reserved. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1070 ¢ Param ID = Alarm Lock State ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Alarm Lock State °µµµµµµµµµ¤ Bit 0 defines the current state of the alarm. Bit 0 = 0 if alarm is not locked. Bit 0 = 1 if alarm is locked. All other bits are reserved. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1080 ¢ Param ID = Reason Code ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Reason Code °µµµµµµµµµ¤ This parameter is used for remote alarm queue management. It defines why the alarm record is being sent. The following lists defined reason codes:<br />
<br />
0x00 = Not used 0x01 = Alarm state just transitioned. 0x02 = Alarm just locked. 0x03 = Alarm just unlocked. 0x04 = Reserved. 0x05 = Alarm just re-triggered. Reset time tag in alarm queue. 0x06 = Reserved. 0x07 = Alarm just acknowledged. 0x08 = Alarm reset. Remove alarm from alarm queue. 0x09 = Alarm Dump Record. 0xFE = End of Alarm Dump. 0xFF = Clear Alarm Queue to prepare for alarm dump. All other values reserved.<br />
<br />
228 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Long Name Size of long name.<br />
<br />
This parameter defines the long name (text) associated with the alarm. This information is not sent if it is not requested in the alarm establish message. Text size will be zero if the gateway cannot provide the associated text. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10A0 ¢ Param ID = Alarm Seq. Number ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Alarm Sequence Number °µµµµµµµµµµµµµµµµµµ¤ This parameter identifies the alarm record sequence number. Each alarm queue has a sequence number, which is incremented for every alarm record. The alarm sequence number is provided for remote alarm queue management. If the remote alarm queue sequence number (plus 1) does not equal this sequence number, then the remote alarm queue is out-of-sync with the process controller’s alarm queue. In this event, the DCS should request an alarm dump (See alarm commands defined later in this document) to re-synchronize. Note that this value is a two byte-unsigned integer and will rollover after 0xFFFF. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10C0 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµ¤<br />
<br />
Param ID = Alarm ACK State Parameter size. Alarm ACK State Value<br />
<br />
Bit 0 defines the Acknowledged State of the alarm. Bit 0 = 0 if the alarm has not been acknowledged. Bit 0 = 1 if the alarm has been acknowledged. All other bits are reserved. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10D0 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = Point ID Hint Parameter size. Point ID Hint Value<br />
<br />
The gateway will send this parameter if it cannot translate the alarm drop number into its short name form. Reception of this parameter indicates incomplete translation tables in the gateway. ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Param ID = END-OF-LIST Parameter size.<br />
<br />
No more information about this alarm follows.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 229<br />
<br />
Process Control Command Requests: There are two types of process control command messages: 1.) Push Button commands (i.e. Start/Stop/Raise/Lower etc.) 2.) Setpoint Target commands (i.e. Speed target/Load Target etc.) Both control command requests may be blocked either by the gateway or the process controller. The DCS should monitor feedback signals to determine if the command request has been acted upon by the process controller. To specify the number of scans for a push button use the Setpoint command. Mark V defaults to 4 and Mark V LM defaults to 25. The gateway will respond to a process control command request by a control request ACK/NAK response message. The format of the process control command request is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0800 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name ´µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Process Command Name (ASCIIC) <m> ¢ 5+n Command Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢Command Parameter ¢ 6+n+m ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size Parameter> ¢ 8+n+m °µµµµµµµµµµµµµµµµµµ¡ Parameter Value ¢10+n+m /../µµµµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
The format of a push button command parameter is: ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ 6+n+m ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ 8+n+m °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
PARAM = End List Value not required<br />
<br />
The format of a setpoint target command parameter is: ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10B0 ¢ 6+n+m PARAM = Setpoint ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Value Size> ¢ 8+n+m °µµµµµµµµµµµµµµµµµµ¡ Setpoint Target Value ¢10+n+m /../µµµµµµµµµµµµµµµµµµµµµµ¤<br />
<br />
230 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Process Control Command ACK/NAK Response The gateway responds to a process control command request with a command request ACK/NAK response. The format of the process control command request ACK/NAK response is: ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0801 ¢ 0 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 ´µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Process Command Name (ASCIIC) <m> ¢ 5+n °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Command Status ¢ 6+n+m °µµµµµµµµµµµµµµµµµµ¤<br />
<br />
Message Code (Echoed) Controller Name (Echoed)<br />
<br />
The Sequence Number, Controller Name and Process Command Name are echoed from the process control command request. Possible ACK/NAK codes are: •<br />
<br />
0 – Success. Requested command sent to process controller.<br />
<br />
•<br />
<br />
+1 – Request received by gateway, but communication with process controller is not currently possible.<br />
<br />
•<br />
<br />
-1 – Unknown controller Name.<br />
<br />
•<br />
<br />
-2 – Function not supported by process controller.<br />
<br />
•<br />
<br />
-3 – Invalid process command name.<br />
<br />
•<br />
<br />
-4 – Invalid parameter (i.e. Value for Push Button or no value for a setpoint target.)<br />
<br />
•<br />
<br />
-5 – Internal Gateway error.<br />
<br />
•<br />
<br />
-6- Permission violation due to control hierarchy<br />
<br />
Note: No more than 10 process control command requests per second should be sent to any one controller.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 231<br />
<br />
MESSAGE CODE SUMMARY Message Code<br />
<br />
Message Type<br />
<br />
Sent By<br />
<br />
0x0100<br />
<br />
Supported Controller Request<br />
<br />
DCS<br />
<br />
0x0101<br />
<br />
Supported Controller Response<br />
<br />
Gateway<br />
<br />
0x0200<br />
<br />
Heartbeat Message<br />
<br />
DCS<br />
<br />
0x0300<br />
<br />
Alarm Establish Request<br />
<br />
DCS<br />
<br />
0x0301<br />
<br />
List Establish ACK/NAK<br />
<br />
Gateway<br />
<br />
0x0302<br />
<br />
Alarm Data Message<br />
<br />
Gateway<br />
<br />
0x0400<br />
<br />
Digital Input Est. Request<br />
<br />
DCS<br />
<br />
0x0402<br />
<br />
Digital Input Data Message<br />
<br />
Gateway<br />
<br />
0x0500<br />
<br />
Software Event Est. Request<br />
<br />
DCS<br />
<br />
0x0502<br />
<br />
Software Event Data Message<br />
<br />
Gateway<br />
<br />
0x600<br />
<br />
Periodic Data Definition<br />
<br />
DCS<br />
<br />
0x601<br />
<br />
Periodic Data ACK/NAK<br />
<br />
Gateway<br />
<br />
0x602<br />
<br />
Periodic Data Message<br />
<br />
Gateway<br />
<br />
0x700<br />
<br />
Alarm Command Request<br />
<br />
DCS<br />
<br />
0x701<br />
<br />
Alarm Command ACK/NAK<br />
<br />
Gateway<br />
<br />
0x702<br />
<br />
Alarm Dump Data Message<br />
<br />
Gateway<br />
<br />
0x800<br />
<br />
Process Control Command Request<br />
<br />
DCS<br />
<br />
0x801<br />
<br />
Process Control ACK/NAK Response<br />
<br />
Gateway<br />
<br />
232 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
RECORD/PARAMETER IDENTIFICATION SUMMARY RECORD ID RECORD TYPE 0x8000 List of sub-records. 0x8100 Controller Information parameter list. 0x8300 Alarm Information parameter list. 0x8400 Digital Input Information parameter list. 0x8500 Software Event Information parameter list.<br />
<br />
PARAM ID PARAMETER TYPE 0x0000 End of parameter list. 0x1000 Process controller name 0x1010 Number of communication links to process controller. 0x1020 Process controller type. 0x1030 Point name (short name). 0x1040 Time tag. 0x1050 Alarm drop number. 0x1060 Point value. 0x1070 Alarm locked state. 0x1080 Alarm reason code. 0x1090 Point text (long name). 0x10A0 Alarm sequence number. 0x10B0 Process control setpoint value. 0x10C0 Alarm ACK state. 0x10D0 Point Identifier Hint.<br />
<br />
Application Notes Networking The GSM server will use TCP port 768 on all configured network interfaces on the gateway. A different TCP port number can be specified by editing the NT registry. Add a DWORD value named ‘port’ to the key: [HKEY_LOCAL_MACHINE\SOFTWARE\GEDS\GSM]<br />
<br />
and give it the desired value. The key may need to be created if it does not already exist. Each GSM message must be preceded by a two-byte integer indicating the size of the message. The recipient can use this size as an indication of how many bytes to read from the network. The maximum GSM message size that the gateway will send or receive is 4096 bytes.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 233<br />
<br />
TCP communications Conceptually, a TCP socket represents the endpoint of a virtual circuit. Each client socket has a corresponding socket on the server and each client-server socket pair are the endpoints of a distinct virtual circuit. Thus each client will have a separate communication path to the HMI. Responses to requests from Client-A will be sent only to Client-A. That the server is using only one port can be confusing. The fundamental abstraction of the TCP protocol is the virtual circuit and each virtual circuit is uniquely identified by a pair of endpoints. An endpoint is identified by a pair of integers (host, port) where host is the IP address of the host and port is a TCP port number. Thus the same endpoint on the server can be used by multiple virtual circuits because each virtual circuit is identified by a PAIR of endpoints.<br />
<br />
Telnet Interface The GSM server provides a simple telnet interface that can be used to examine data in the server and trace messages passed to and from a client. To use the telnet interface, run a telnet client and connect to the gateway on the GSM port (768 by default). When the connection is made, the server needs to be informed that the connection is from a telnet client and not a GSM client. To do this press the ‘z’ key twice and the server will respond with a command prompt. If the first two characters typed are not ‘zz’, the server will assume that a GSM client has connected and you will have to disconnect and try again.<br />
<br />
234 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Command Summary: show client – displays a list of all connected clients, including which controllers they have signed up for alarms, events or periodic data. show log – display the contents of the file G:\LOG\GSM.LOG show list <client number> <controller name> <list number> – display the given periodic data list, including point name, point type, last reported value as well as the time the list was last sent to the client. trace <client number> – toggle tracing of GSM messages sent to and received from the given client. trace next – enable tracing of GSM messages sent to and received from the next client to connect to the server. trace all – enable tracing of GSM messages sent to and received from all clients that connect to the server. Acts as a toggle. exit – disconnect from the GSM server. The server will respond to any input that it can not understand by displaying a command summary. There is no command line editing capability, except as may be provided by the telnet client.<br />
<br />
Point ID Hint Parameter The Point ID Hint parameter can be used as a point name in a periodic data request. The Point ID Hint parameter represents the Control Signal Database offset for a data point in a Mark V or Mark V LM controller and when converted to ASCII in base ten, can be used as a point name. This means that any integer offset (converted to ASCII) from 0 to 65535 can be used as a point name for Mark V and Mark V LM controllers. If there is a point configured for that offset then the GSM server will return the appropriate number of bytes, however if no point is configured for that offset then two bytes are returned to the client(i.e. the point is assumed to be a 16 bit integer).<br />
<br />
EGD The GSM server provides access to any EGD data that is being collected on the HMI. A special controller name of EGD should be used in requests. Only periodic data requests are valid for the EGD controller. Point names for EGD data are colonseparated fields that specify Exchange ID, Offset and Length. For example the 4 bytes at offset 45 in exchange 5 would be named 5:45:4.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 235<br />
<br />
TCI Modbus Introduction The Modbus™ interface for the Turbine Control Interface (TCI) can act as either a slave to the Distributed Control System (DCS) master or as a master to the DCS slave. When the TCI acts as a slave, the control is said to be in Modbus Slave mode; when the TCI acts as a master, the control is said to be in Modbus Master mode. Either or both modes may be enabled. Modbus slave mode supports RS-232 serial communications and Ethernet. Modbus master mode supports RS-232 serial communication only. In Modbus slave mode the DCS can thereby request information from each Mark V(LM) controller or Cimplicity project by sending a Modbus data request message via the Modbus link to a specific slave address. The DCS master can also issue Modbus command messages to initiate operator commands to each Mark V(LM) or Cimplicity. These command messages support both push button commands (such as START, STOP) and analog setpoint commands (such as preselected load setpoint). A Modbus data file specifies the correspondence between Modbus coil and register numbers and the Unit’s data. In Modbus master mode the TCI can gather data from attached Modbus slaves. The data gathered is requested and stored in the TCI database based on points and update rates specified in a Modbus data file.<br />
<br />
Modbus Slave The rate at which the data can be collected from a serial Modbus slave is limited by the transmission rate on the RS232 link, and by the turn-around times of the computers on each end of the link. The rate at which the data can be collected from an Ethernet Modbus slave is limited by the Ethernet traffic, and by the turn-around times of the computers on each end of the connection. The DCS may issue no more than ten operator command messages per second. A maximum of 8 serial links may be configured for a single TCI. The number of Ethernet connections an Ethernet Modbus slave will accept is configurable. Ethernet and serial links may both be used at the same time. All data to and from a controller will be serialized and operated on one at a time. The TCI Modbus slave, configured with the appropriate address, will reply with the requested data. A single TCI can respond to multiple slave addresses. Up to a maximum of 16 slave addresses may be configured for a single TCI. Normally each separate slave address would be assigned to gather data from a separate unit control.<br />
<br />
Modbus Master The rate at which the data can be collected is limited by the transmission rate on the RS232 link, by the turn-around times of the computers on each end of the link, and by the periodic rate specified in the configuration data file. The TCI Modbus master, configured with the appropriate address, will request data from a DCS slave at a specified rate. A single TCI can communicate with multiple slave addresses over various communication ports. Up to a maximum of 8 communication ports may be used to communicate with up to 48 separate slave addresses.<br />
<br />
236 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
MODBUS_L Overview If the HMI is configured to provide a Modbus link, MODBUS_L is used to provide a list of the signals that are available over the Modbus link, along with the information on how to interpret (scale) the values. Modbus is an industry standard communication link used by the HMI to provide the current value of plant variables from the HMI to any system that requests it via the Modbus link. The HMI acts as a Modbus slave, which means it waits for requests from another computer (a Modbus master) and answers them by returning the current value of the variables requested. The Modbus protocol is implemented as a set of registers. The HMI supports up to 2000 registers of each type from each turbine control. The mapping of the Modbus register number to the turbine signal name is done via the MODBUS.DAT file in the unit configuration directory. (See the Modbus configuration chapter for more information on configuring the MODBUS interface.) Once the Modbus configuration has been done, MODBUS_L is used to generate a formatted list of the Modbus register numbers, turbine signal names, and scaling information for each signal defined. This information is stored in the MODBUS.LST file. The MODBUS.LST file is then used to configure the Master side of the Modbus link.<br />
<br />
Operation MODBUS_L is a command line utility program run from the unit configuration directory. It does not require any command line parameters, but a few are available to change the default format or scale codes generated. If run with the /? parameter, it will produce a help screen, as shown in the example below: F:\UNIT1>MODBUS_L /? MODBUS_L: MODBUS LISTING PROGRAM Command format: MODBUS_L [options] options: ENGLISH, METRIC, CUSTOM, HARDWARE These options control the scale code set used to supply the gain, offset, and engineering units for each point. RS16, RU16 These options control the formatting of the raw data, with the appropriate changes to the gain and offset for each point. QUIET This option disables the printout to the terminal of messages indicating that a point name was not found in the dictionary. The messages, however, will be indicated in the MODBUS.LST file. NOLONG This option produces a MODBUS.LST file without longnames. LONG This option makes a MODBUS.LST with a nonlogic longname field of 66 characters. The nonlogic longname field default is 40 char. /LOG Redirect output sent to the screen into MODBUS_L.LOG. F:\UNIT1><br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 237<br />
<br />
Specifications The Modbus interface uses Gould Modicon’s Modbus Protocol. The following text provides application information only. It does not specify Modbus Protocol. Detailed information on the Modbus protocol is available from Gould Inc.’s Reference Guide PI-MBUS-300 Rev B, January 1985. This is not the Modbus Plus specification. It is recommended that both this document and the Gould reference guide be used together. The TCI system allows easy addition, deletion, or modification of the data lists by the DCS vendor or customer after equipment installation. The data point capability of the Mark V turbine control system generally far exceeds the actual needs of the DCS. A TCI can be located local, remote, or anywhere within the distance limitations of the Stage Link system (for details on the Stage Link, see GEH-6195B, Chapter 9). The DCS or remote control system can be located anywhere within the restrictions of the RS232 serial communication link or anywhere on the Ethernet link.<br />
<br />
External Communication Links- Modbus Slave mode An external communication link allows an operator at a remote location to initiate any operator command by sending a logical command or an analog setpoint to a TCI. Logical commands are used to initiate automated sequences which reside in the Mark V control system, and analog setpoints are used to set a variable, such as the turbine load, to a predefined level. It is occasionally more efficient to set targets with an analog number, such as megawatts, rather than manually entering raise/lower commands. The operator can send a target setpoint that the Mark V enters into its data base and ramps to the target at a predetermined ramp rate. Any operator command that can be initiated from the TCI can be initiated from the remote control system through a communication link. This does not preclude the use of hard-wired remote control interface. However, a traditional hard-wired interface can be I/O intensive and needs to be evaluated on a case-by-case basis. Maintenance commands (editing application software, changing tuning constants, etc.) are generally restricted to being issued from a TCI.<br />
<br />
238 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
All application data in the Mark V can be monitored by the remote control system via the remote serial communication link. The Mark V data base contains several thousand points, but usually less than 500 points are of interest to the remote control system. These consist of logical data for alarm and event messages and analog or numeric data for such variables as speed, load, vibration, temperature, and so forth. One TCI can interface with up to 16 Mark Vs. Therefore, the external communication link to the remote control system has the capability to communicate through the TCI to up to 16 Mark Vs.<br />
<br />
External Communication Links- Modbus Master Mode External communication links allow the TCI control to communicate with a DCS or other Modbus slaves over up to eight serial communication ports. Communication is possible over these links with up to 48 different Modbus slaves. For each Modbus slave, the data communicated will be specified by the contents of a data file found in the unit directory. This file will specify what data is read from the slave and stored in the data dictionary and also what data is sent (written) to the slave.<br />
<br />
RS232 and Modbus GE INDUSTRIAL SYSTEMS offers Modbus protocol with an RS232 link as a level #1 communication link because it is compatible with most control systems. The DCS is the master, and it issues a command to the Mark V that is the slave. Logical and analog setpoint commands can be issued from the DCS to preassigned points in TCI to initiate control action. Requests for data can be sent to preassigned points in the TCI and these points can be modified to include any point in the database. Modbus, with an RS232 link, is adequate for most applications, but its limitations must be recognized. The limitations are a 19,200-baud (bit/sec) transmission rate and the lack of individual time tags for alarms and events. The RS232 link transmission rate makes it satisfactory for one or two units on a single communication link depending on the amount of data that is requested for transmission. A major factor in determining the suitability of the Modbus and RS232 is whether the historical data base for the Mark V is local such as a Mark V Historian <H> or remote in the DCS. If a Mark V Historian <H> is used, the communication link to the DCS is used to retrieve data from the Mark V. This data is used to support the displays which currently appear on the monitors in the control room. This retrieval requires minimal data transmission from the Mark V. The communication link load is a function of the amount of data that the DCS is requesting and how often it is to be transmitted. Data in the Mark V requires one word per analog point and one word for each 16 logic points (such as the state of alarms and events). An evaluation of the link load for a specific application requires reviewing the amount and frequency of the data transmission(s) and the specified baud rate and verifying that all is within the desired sampling rate. In order to minimize the sampling rate for alarms, a contact output is provided from the Mark V to the plant alarm horn system that informs the DCS that a new alarm has occurred. The DCS can then request a transmission of the alarm states data. This eliminates the need to continuously sample the alarm queue at a fast rate. Some sites provide a remote printer to get high-resolution local alarm (62ms), event (62ms), and sequence of event logs in the control room without investing in more sophisticated equipment.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 239<br />
<br />
Physical Link Layer/Format, RS232 Communications These sections detail the physical link layer/format of the Modbus serial link.<br />
<br />
Link Layer Each TCI processor can provide up to 8 point-to-point Modbus RS232 serial links and a defined number of Ethernet connections to a customer’s DCS. Since the master may communicate with multiple slaves, the TCI will send data upon request only. No periodic transmission of data from the TCI is possible, except as a reply to a periodically transmitted request sent from the DCS.<br />
<br />
Physical Layer The TCI processor is used as the communications port for Modbus, typically using the TCI’s COM2 serial communications port. If the COM2 port is not available, a serial expander card is required to supply eight more serial ports. The port used is configured with a DB9P (Male) connector as Data Terminal Equipment (DTE). Diagrams showing this connection are provided below. The system is asynchronous RS232 compatible, 300 to 19,200 baud, programmable parity. It is compatible with full duplex data sets (i.e. modems). Modem generated signals such as CTS (Clear to Send), CD (Carrier Detect) and RI (Ring Indicator) are not required to enable the transmitter. The RTS (Ready to Send) and the DTR (Data Terminal Ready) on the TCI are always equal to 1 when the TCI is powered up. This prohibits any multi-drop DCS configurations, as these signals cannot enable or disable communications. Hardware handshaking (flow control via RTS/CTS signals) is not supported. It is up to the master to only request data that it can reasonably expect to handle in a single burst. (See the section below on TCI Modbus Configuration for timeout configuration.) GE INDUSTRIAL SYSTEMS does not recommend remote control of turbine products over a telephone modem due to the inherent unreliability in this type of communication. If it is necessary to collect data or operate over telephone modems, the maximum number of bits that can be communicated is ten. Therefore the standard eight bits of Modbus data and the two bits for start/stop is all that can be accommodated. This means that PARITY is not supported over telephone modems. RS232 systems require two metallic shielded twisted pair wires to connect the shorthaul modems. RS232 transmission distances are defined below:<br />
<br />
TRANSMISSION DISTANCE Baud Rate<br />
<br />
26 Gauge Miles km<br />
<br />
24 Gauge Miles km<br />
<br />
22 Gauge Miles km<br />
<br />
19 Gauge Miles km<br />
<br />
300 1200 2400 4800 9600 19200<br />
<br />
10.0 6.0 4.5 3.5 2.2 1.0<br />
<br />
12.0 7.5 5.5 4.5 3.2 1.2<br />
<br />
15.0 9.0 7.5 5.5 4.0 1.5<br />
<br />
25.0 15.0 11.0 7.0 5.0 2.0<br />
<br />
16.1 9.7 7.2 5.6 3.5 1.6<br />
<br />
19.3 12.1 8.9 7.2 5.1 1.9<br />
<br />
24.1 14.5 12.1 8.9 6.4 2.4<br />
<br />
40.2 24.1 17.7 11.3 8.0 3.2<br />
<br />
RS232 Transmission Distances with modems RS232 Connections are limited to 50 feet (13 meters) without the use of modems. While modems are supplied by GE INDUSTRIAL SYSTEMS, the customer must supply the cabling and terminations. The standard modems supplied by GE INDUSTRIAL SYSTEMS require power on pin four. The modem connected to the TCI obtains its power from the TCI serial port. The other modem must receive power<br />
<br />
240 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
on pin four from the DCS. If the DCS cannot supply power, the optional modem set is required and must be specified when ordering from GE INDUSTRIAL SYSTEMS. This set is powered by an external source.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 241<br />
<br />
Typical <I> DB9P (DTE) RXD TXD RTS CTS SCOM CD DTR DSR RI<br />
<br />
DB25P (DTE) DCS Cable<br />
<br />
(2) (3) (7) (8) (5) (1) (4) (6) (9)<br />
<br />
TXD RXD RTS CTS SCOM<br />
<br />
NC NC Common (not shielded) NC NC NC NC<br />
<br />
(2) (3) (4) (5) (7)<br />
<br />
RS232 connection to DB9 serial ports with no modems<br />
<br />
<I> Data Set DB9P (DTE) (Modem) RXD TXD DTR SCOM<br />
<br />
(2) (3) (4) (5)<br />
<br />
(2) (3) (4) (5)<br />
<br />
Data Set (Modem)<br />
<br />
S1-2 S2-1 S1-4 R2-3<br />
<br />
R1-4 R2-3 S1-2 S2-1<br />
<br />
Shielded Twisted Pair wire<br />
<br />
DCS<br />
<br />
(2) (3) (4) (5)<br />
<br />
RXD TXD V+ SCOM<br />
<br />
Cable<br />
<br />
RS232 connection to DB9 Serial port with modems<br />
<br />
V+, the DCS power, is 3-5 mA @ 10 Vdc. It is a nominal 12 Vdc, minimum 6 Vdc, maximum 25 Vdc.<br />
<br />
Typical <I> DB9P (DTE) RXD TXD RTS CTS SCOM CD DTR DSR RI<br />
<br />
(2) (3) (7) (8) (5) (1) (4) (6) (9)<br />
<br />
Data Set LDDS (3) (2) NC NC<br />
<br />
S1 S2 R1 R2<br />
<br />
Data Set LDDS R1 R2 S1 S2<br />
<br />
(7) NC NC NC NC<br />
<br />
Power 120Vac<br />
<br />
(3) (3) (4) (5) (7) (8)<br />
<br />
DB25P (DTE) DCS RXD TXD RTS CTS SCOM CD<br />
<br />
(3) (2) (4) (5) (7) (8)<br />
<br />
Power 120Vac<br />
<br />
Optional RS232 connection with LDDS<br />
<br />
The DCS and the cabling are supplied by the customer.<br />
<br />
242 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
NC means No Connection. LDDS means Limited Distance Data Set (short haul modem). If a DB9 pin connector is used instead of a DB25 pin connector, change: •<br />
<br />
pin 3 to pin 2 for RXD<br />
<br />
•<br />
<br />
pin 2 to pin 3 for TXD<br />
<br />
•<br />
<br />
pin 4 to pin 7 for RTS<br />
<br />
•<br />
<br />
pin 5 to pin 8 for CTS<br />
<br />
•<br />
<br />
pin 7 to pin 5 for SCOM<br />
<br />
•<br />
<br />
pin 8 to pin 1 for CD<br />
<br />
TCI Modbus Configuration This section defines the required additions and/or modifications to configuration files on a TCI to accomplish the following: •<br />
<br />
enable and configure the Modbus task on the TCI<br />
<br />
•<br />
<br />
enable and configure a serial port for Modbus communication<br />
<br />
•<br />
<br />
set up the Modbus mapping tables<br />
<br />
•<br />
<br />
generate the related document for the DCS vendor<br />
<br />
F:\IO_PORTS.DAT: Modbus Link Definition The Modbus Master program (MModbus.exe) and the Modbus Slave program (Modbus.exe) share a common configuration file entitled F:\IO_PORTS.DAT to specify important site variable data such as port, baud rate, Modbus slave id, etc. The configuration file is an ASCII based text file that may be modified with any standard text editor. Lines are not case sensitive. The configuration file is divided into sections and each section begins with a title enclosed in brackets [ ]. The Modbus Slave program uses three sections: [MODBUS_SLAVE_PORT] [MODBUS_SLAVE_TIMEOUT] [MODBUS_ASSIGNMENT]<br />
<br />
The Modbus Master program uses one section: [MODBUS_MASTER_PORT]<br />
<br />
The [MODBUS_SLAVE_PORT] and [MODBUS_MASTER_PORT] sections may appear multiple times to define multiple ports. In the [MODBUS_SLAVE_PORT] section, the TCI uses information in the TCI port definition/configuration file, F:\IO_PORTS.DAT, to assign functions to its available I/O ports. These ports include the serial port (example: COM2), plus, the serial ports<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 243<br />
<br />
on an expander card (if supplied). A serial port is configured here as a Modbus link. The TCI responds to commands sent from the DCS based on the slave address(es) set up in this file, and decides what Mark V unit is to supply data for that address. The format of the transmitted data (the mode) is also set here. This file is also used to define serial port as Modbus Master ports. To customize F:\IO_PORTS.DAT, use the standard text file editor. F:\IO_PORTS.DAT contains textual information to help define a MODBUS link. The following sections are in the file: •<br />
<br />
[MODBUS_SLAVE_PORT] – defines a Modbus slave port and its characteristics. There will be as many of these sections as there are slave ports. One of these sections will define the Ethernet port if the Modbus slave is to respond to Ethernet messages.<br />
<br />
•<br />
<br />
[MODBUS_ASSIGNMENT] – defines slave addressed and modes. These slaves can be either Mark V(LM) units or Cimplicity projects.<br />
<br />
•<br />
<br />
[MODBUS_SLAVE_TIMEOUT] – define slave timeout value and NAK code.<br />
<br />
•<br />
<br />
[MODBUS_MASTER_PORT] – define a serial port as a Modbus Master port. There will be as many of these as there are Modbus Master ports.<br />
<br />
These sections are defined in more detail in the sample configuration file in G:\DATA\IO_PORTS.DAT.<br />
<br />
Modbus Master Setup The Modbus Master program first reads the section file called MODBUS_SETUP_FILE file (filename F:\IO_PORTS.DAT) for information specifying Modbus port and hardware characteristics. This section, [MODBUS_MASTER_PORT], provides details such as: •<br />
<br />
Port, baud rate, parity, etc.<br />
<br />
•<br />
<br />
Modbus address and software characteristics. Provides details such as slave address and unit number. Up to 48 master entries may be specified.<br />
<br />
•<br />
<br />
Modbus timeout and loop characteristics.<br />
<br />
This program ignores Modbus slave assignment. The program then reads A MODBUS_DATA_FILE in the unit directory for information specifying a correspondence between Modbus data structures (holding registers, holding coils, input registers, input coils, etc.) and the corresponding Mark V (LM) data points and scaling information. The MODBUS_DATA_FILE resides in the unit directory (F:\UNITn) and has a filename in the form MMBUSnnn.DAT where nnn is the slave address being referenced. Multiple MMBUSnnn.DAT files may exist in the same directory. For example, if the F:\IO_PORTS.DAT file specified that we communicate with slave address 3 with lines such as: Master 3 Unit Mm Mode RS16 Then the Modbus Master program would read file MMBUS3.DAT from the unit directory to determine the register and coil correspondence. Leading zeros for nnn are not used.<br />
<br />
244 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Next, the program opens the port specified in (1) above and monitors the port for messages from a Modbus master to one of its 48 slave addresses. Upon receiving a message reply, the program stores the data in the unit data dictionary as appropriate.<br />
<br />
Modbus Slave configuration: Holding Coils, Input Coils, Holding Registers, Input Registers Each TCI that supplies Modbus data must have a Modbus Mapping file (Modbus.dat) for each Mark V(LM) panel. This file contains mapping tables to associate the registers and coils with Mark V(LM) control signal database (CSDB) pointnames. Each TCI that supplies Modbus data must have a Modbus Mapping file (CimMod.dat) for each CIMPLICITY project. This file contains mapping tables to associate the registers and coils with the CIMPLICITY points. There are two categories of point mapping tables. They are, holding and input. The Modbus protocol supports reading and writing of holding table points, and reading but not writing of input table points. The TCI does not make any restrictions on what Mark V CSDB pointnames can be in input and holding tables. The TCI knows on a point by point basis which points are Mark V commands and which points are not. A Mark V command is one of the following: LOGICS:<br />
<br />
pushbuttons<br />
<br />
logic state variables.<br />
<br />
ANALOGS:<br />
<br />
analog setpoints<br />
<br />
enumerated state variables<br />
<br />
As such, the holding tables may be used exclusively, and the input tables may be omitted completely. Sending a Modbus write command to a point on a holding table that is not mapped to a Mark V command will have no effect and will be ignored. There are two classes of signals found on the two tables: coils and registers. A coil is one bit, and maps to a logic Mark V CSDB pointname, with a value of zero or one. A register is 16 bits, and maps to an analog Mark V CSDB pointname, or to a set of (up to) 16 packed logicals. Multiple holding coils or registers may be mapped to any one Mark V CSDB pointname. If the pointname is a Mark V command, a write command from the DCS to any of the mapped holding coils or registers will cause the TCI to execute the Mark V command. HC – holding coils – one bit logic signals that are both readable and writable. Logic Mark V commands must be in this table for the TCI to issue the command to the Mark V; however, not all points in this table must be logic Mark V commands. Logic Mark V commands are not writable from the holding register table. IC – input coils – one-bit logic signals that are readable but not writable. Any Mark V logic control database signal can be in this table, but logic Mark V commands will not be writable from this table. HR – holding registers – 16 bit analog signals that are both readable and writable. Analog Mark V commands must be in this table for the TCI to send the command to the Mark V, but not all points in this table must be analog Mark V commands. They can be any analog control database signal, or a set of (up to) 16 bit packed logic control database signals. Mark V logic commands can be packed into a holding register, however, they will not be writable in that format. For the TCI to issue a signal to a logic Mark V command, it must be in the holding coil table. Simply put: packed holding registers are not writable.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 245<br />
<br />
IR – input registers – 16 bit analog values that are readable but not writable. Any analog control database signal, or a set of (up to) sixteen (16) bit packed logic control database signals, may be in this table. Analog or logic Mark V commands will not be writable from this table.<br />
<br />
Modbus Slave: @SPARE: Unused Coils and Registers If a request for any read or write command from the DCS using a coil or register not mapped to a Mark V CSDB pointname, the TCI will respond with a NAK code of 02, which is listed as INVALID ADDRESS (see the section on Message Errors, below). This prevents the DCS from interpreting the reply from the TCI as data from the Mark V. To define coils or registers without mapping them to Mark V CSDB pointnames, map them to @SPARE in the mapping table. This tells the TCI that the Coil or register is not used, but is legally defined. The TCI will respond to any DCS request with a data value of zero (0) for all coils and registers defined as @SPARE. It is not necessary to map all the points in the mapping table. The @SPARE is used only to fill in the gaps or to format the table as required by the DCS. Bit packed registers (logic control database signals packed into a 16 bit register) should not have unused bits defined as @SPARE. When any one bit of a register is defined as a packed bit, the entire register is defined as a packed register. Therefore, omit defining the unused bits. Bits in a packed register not mapped to a logic Mark V CSDB pointnames will always send a value of 0 to the DCS. @SPARE can only be used on an unpacked register when the entire register is unused.<br />
<br />
Modbus Slave: F:\UNITn\MODBUS.DAT: MODBUS Mapping File Format The hidden text needs to be added when NATIVE mode is added to the Modbus Slave in the next revision of TCI. If the Modbus Slave mode is NATIVE, F:\UNITN\MODBUS_N.DAT is used for the point configuration. If the Modbus Slave is in any mode except NATIVE, F:\UNITN|MODBUS.DAT is used for the point configuration. The following section contains a simple template as an example for filling out the Modbus mapping file. More details are in the sample file in g:\data\modbus.dat and g:\data\modbus_n.dat.<br />
<br />
246 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
If the Slave is defined to be a CIMPLICITY project, the configuration file is CIMMOD.DAT. They are located in the data directory of the Cimplicity project. For the Cimplicity data to work, the TCI Modbus option must be installed. When this option is installed, templates of these files will be installed. There is information in the header of these files on how to fill them out. They are almost the same as the unit configuration files. A sample MODBUS.DAT file is listed below: ; HOLDING_COIL TABLE HC0001 logic_signal_name HC0002 logic_signal_name HC0003 @SPARE ; INPUT_COIL TABLE [Optional] IC0101 logic_signal_name IC0102 logic_signal_name IC0103 @SPARE ; HOLDING_REGISTER TABLE HR0001 analog_signal_name HR0002 @SPARE HR0004.0 logic_signal_name HR0004.1 logic_signal_name HR0003 analog_signal_name ; INPUT_REGISTER TABLE [Optional] IR0101 analog_signal_name IR0102 @SPARE IR0004.4 logic_signal_name IR0004.5 logic_signal_name<br />
<br />
When adding or modifying entries in this file, the following rules and guidelines apply:<br />
<br />
GEH-6126<br />
<br />
•<br />
<br />
It is not necessary to define all the table points in this file, only the ones that are desired.<br />
<br />
•<br />
<br />
Never define a bit of a packed holding register (such as HR0001.1) as @SPARE. Defining just one of the bits as packed defines the entire register as a packed register. A 0 is returned for bits not mapped.<br />
<br />
•<br />
<br />
When a semi-colon is found in a line, the rest of the line is considered a comment.<br />
<br />
•<br />
<br />
Do not add scaling information or definitions in this file, only the required three fields.<br />
<br />
•<br />
<br />
Never add page breaks (form feeds) in this file.<br />
<br />
•<br />
<br />
The Table entries may be in any order.<br />
<br />
•<br />
<br />
Do not map any one register to both packed Mark V CSDB logic pointnames and to an analog Mark V CSDB pointname.<br />
<br />
•<br />
<br />
Do not have any one coil or register mapped more that once.<br />
<br />
•<br />
<br />
Group similar Mark V CSDB points together, such as temperatures, speed signals, or Mark V command feedback signals.<br />
<br />
Chapter 7 Remote Access and Control • 247<br />
<br />
From the example below, it can be seen that not all table points are defined or in order, comments are added using a semi-colon ( ; ), there are no duplicate table point definitions, etc. However, the rules outlined above have been followed and the file can therefore be considered correct. The TCI must be restarted for changes to take effect. After the TCI has restarted, inspect the file G:\LOG\MODBUS.LOG for any errors or warnings.<br />
<br />
Modbus Master Configuration This section describes the Modbus Master sections in the TCI port definition/configuration file, F:\IO_PORTS.DAT, and in the data configuration files, F:\UNITn\MMBUSn.DAT. In the TCI port definition/configuration file, F:\IO_PORTS.DAT: Comments are specified by a semicolon. Any semicolon makes the remainder of the line a comment and will be ignored. There is only one section used by the Modbus Master entitled: [MODBUS_MASTER_PORT]<br />
<br />
but this section may appear up to 8 times. Each appearance should correspond to a separate communications port for the Modbus Master. For example, the first [MODBUS_MASTER_PORT] section may be for com2 while the next section might be for com3. These sections should appear as above, including brackets. They may appear in any order. Sections other than [MODBUS_MASTER_PORT] are ignored by this program. Data lines following each section specify configuration information. For the section [MODBUS_MASTER_PORT], example data lines are:<br />
<br />
[MODBUS_MASTER_PORT] port com2 baud 9600 parity 0 ;0-4 (none, odd, even, mark, space) databits 8 ;5-8 stopbits 0 ;0-2 (1, 1.5, 2 stop bits) xonxoff 0 ;0-1 port_it 4 ;Timeout interval between characters, msec. Default=40 ;Normally, port_it should specify 3.5 character times as ;defined by the Modbus Gould specification. At 9600 baud, ;and 8 data bits, 1 start, and 1 stop bit, this yields ;a character time of 1.04 msec. 3.5 character times would ;therefore be 3.125 msec. port_tt 200 ;Timeout for total message, msec. Default=200 ;This is time to receive message only, not process it. modbus_timeout 2000 ;Time (milliseconds) before we give up ;waiting for a response from a slave. ;Default timeout is 2000 milliseconds. ;Minimum timeout is 100 milliseconds. ;Maximum timeout is 60000 milliseconds. modbus_loop 5000 ;Time (milliseconds) before we restart ;the request loop. This is the period of ;between asking the slave(s) for all the ;data specified and the time we start ;over and reask. ;Default loop is 5000 milliseconds. ;Minimum loop is 100 milliseconds. ;Maximum loop is 86400000 milliseconds. MASTER 1 UNIT 62 MODE RS16 MASTER 2 UNIT T3 MODE RS16 [MODBUS_MASTER_PORT] port com3 baud 9600 MASTER 7 UNIT 63 MODE RU16<br />
<br />
248 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Comments: The above example defines two ports for use with Modbus Master. Both com2 and com3 will be used. Modbus slave ids 1 and 2 will be reached using com2 and Modbus slave id 7 will be reached using com3. For port, specify com1, com2, com3, ... To disable, specify none For baud, specify baud rates supported by the operating system. For parity, specify 0 for none, 1 for odd, 2 for even, 3 for mark, or 4 for space. For databits, always specify 8 For stop bits, specify 0 for 1 stop bit, 1 for 1.5 stop bits, or 2 for 2 stop bits. For xonxoff, specify 0 to disable. For port_id, specify intercharacter timeout as desired based on DCS transmission. The Modbus specification specifies 3.5 character times. For 9600 baud in the example above, show that 4 msec is appropriate for strict Gould specification adherence. For port_tt, specify the total time permitted for the I+ to RECEIVE a message from the DCS, starting from receipt of the first character. Normally it will be most convenient to make this number high and use only the intercharacter timeout, port_it.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 249<br />
<br />
The only required entries are port and MASTER-UNIT-MODE. Baud defaults to 9600. Parity, databits, stopbits, and xonxoff default as shown above. Port_it defaults to 40. Port_tt defaults to 200. For the MASTER-UNIT-MODE line: format: MASTER mmm UNIT uu MODE keyword where: mmm is the SLAVE address (in decimal) to use when communicating with unit uu. uu is the two-character unit name (defined in F:\CONFIG.DAT) keyword is either RS16 or RU16 for Signed & Unsigned data respectively. MASTER, UNIT, and MODE are required entries. A new line should appear for each unit or slave address. Normally this is one or two lines for typical data patterns. A maximum of 48 MASTER-UNIT-MODE lines may appear. Each line requires: MASTER followed a slave entry specifying a Modbus Slave id number, UNIT followed by a two-character unit id. These IDs correspond to the units already defined in F:\CONFIG.DAT. MODE followed by RS16 or RU16. For analog data, use RS16 for signed mode, RU16 for unsigned. RS16 specifies a signed result, ranging from a minimum of -32768 (hex 8000) to a maximum of 32767 (hex 7FFF). RU16 specifies an unsigned result, ranging from a minimum of zero to a maximum of 65535 (hex FFFF). Raw data in the Mark V (LM) will be rescaled based on the minimum and maximum numbers provided in the F:\UNITn\MMBUSnnn.DAT data file to a result specified<br />
<br />
Description Of Modbus_Data_File Comments are specified by a semicolon. Any semicolon makes the remainder of the line a comment and will be ignored. Each line has three required entries:<br />
<br />
Table_Type Table_point CSDB_Pointname Where Table_Type is one of six kinds: HC IC HR IR WC WR Where Table_Point is 1 through 2000 Where CSDB_Pointname is a valid control signal database pointname. Following the CSDB_Pointname are optional fields to specify the minimum and maximum CSDB values. These fields should always be specified except in the case of logic points. Refer to section 10-5.5 of SPEEDTRONIC™ Mark V Turbine Control Application Manual GEH-6195B for details. Table_Types WR and WC have been added for write register and write coil capability from the I+ or OSM to the Modbus slave.<br />
<br />
250 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
MODBUS_L.EXE: MODBUS Listing Program After F:\UNITn\MODBUS.DAT is completed, the document F:\UNITn\MODBUS.LST is created for use by the DCS vendor for setting up the DCS. This file documents the Modbus tables. The Modbus Listing Program, G:\EXEC\MODBUS_L.EXE, reads the necessary configuration files on the TCI and creates F:\UNITn\MODBUS.LST. This file contains a list of the coil and register maps, complete with scaling information. A new listing file must be created each time F:\UNITn\MODBUS.DAT is changed, or when the mode defined for the Modbus link is changed in F:\IO_PORTS.DAT. This Modbus listing file is the key to programming the DCS end of the Modbus link. The Modbus listing file defines the format and scaling of each mapped coil and register. Included in this list is an indication of which signals are Mark V commands. To create a new listing file F:\UNITn\MODBUS.LST, type MODBUS_L from the DOS line in the unit specific directory F:\UNITn. There is a corresponding Modbus listing program for Cimplicity. It is CimMod_L.exe. To run this program, create a DOS prompt for the Cimplicity Configuration Cabinet. Change directory to the data directory. Then type CimMod_L.<br />
<br />
The format is shown by typing MODBUS_L /? which returns printout resembling the illustration below:<br />
<br />
MODBUS_L:<br />
<br />
MODBUS LISTING PROGRAM<br />
<br />
Command format: MODBUS_L [options] options: ENGLISH, METRIC, CUSTOM, HARDWARE These options control the scale code set used to supply the gain, offset, and engineering units for each point. RS16, RU16, UN12, HW12 These options control the formatting of the raw data, with the appropriate changes to the gain and offset for each point. QUIET This option disables printout to the terminal of messages indicating that point name was not found in the dictionary. The messages, however, will be indicated in the MODBUS.LST file. NOLONG This option produces a MODBUS.LST file without “ longnames” . LONG This option makes a MODBUS.LST with nonlogic longname field of 66 characters. The nonlogic longname field default is 40 char.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 251<br />
<br />
MODBUS_L Command Format The options described below are used to modify the format of F:\UNITn\MODBUS.LST as follows: scaling (ENGLISH, METRIC, CUSTOM, HARDWARE) determines which F:\UNITn\*.SCA file is used (ENGLISH.SCA is the default file).<br />
<br />
mode (RS16, RU16, UN12, HW12, NATIVE) used must match the mode defined in F:\IO_PORTS.DAT. MODBUS_L does not read this file, it must be added manually. quiet if used, F:\UNITn\MODBUS.LST should be checked for error messages, as the errors will not be displayed on the screen. nolong omits longnames (Mark V control signal database pointname definitions) defined in the file F:\UNITn\LONGNAME.DAT. long is used to widen F:\UNITn\MODBUS.LST to avoid trimming longnames of nonlogic (analog) signals. MODBUS_L will flag duplicate coil or register assignments, undefined Mark V CSDB pointnames, invalid formats, invalid coil or register numbers, conversion errors, etc. Resolve all errors before communicating with the DCS.<br />
<br />
F:\UNITn\MODBUS.LST: MODBUS Listing File An example F:\UNITn\MODBUS.LST file is shown below: +HR0001 +HR0002 +HR0003 HR0004 HR0005 +HR0006<br />
<br />
| | | | | |<br />
<br />
+HR0009<br />
<br />
| SC43<br />
<br />
HR00010 | SELECTION HR0200.00| HR0200.01| HR0200.02| HR0200.03| +HC0001 | +HC0002 | +HC0003 | +HC0004 |<br />
<br />
SWREF_CMD DRVAR_CMD SC43LOAD @SPARE @SPARE L90PSEL_CMD<br />
<br />
| SIGN16 | | SIGN16 | | UNS16 | | spare | | spare | | SIGN16 | |<br />
<br />
UNS16 |<br />
<br />
SS43<br />
<br />
|<br />
<br />
UNS16 |<br />
<br />
L52GX L94X L30D_SD L30D_SU L1FAST_CPB L1START_CPB L70R4R_CPB L70R4L_CPB<br />
<br />
| | | | | | | |<br />
<br />
PACKED PACKED PACKED PACKED LOGIC LOGIC LOGIC LOGIC<br />
<br />
| | | | | | | |<br />
<br />
512 | 0 | MW | 512 | 0 | MVAR | 65536 | 0 | STATE | 512 | 0 | MW | PRESELECTED LOAD ANALOG SETPOINT 65536 | 0 | STATE | TURBINE CONTROL SELECTION 65536 | 0 | STATE | TURBINE COMMAND STATE GENERATOR BREAKER CLOSURE NORMAL SHUTDOWN NORMAL DISPLAY MESSAGE “ SHUTDOWN STATUS” NORMAL DISPLAY MESSAGE “ STARTUP STATUS” FAST LOAD START SIGNAL START SIGNAL SPEED SETPOINT RAISE COMMAND PUSHBUTTON SPEED SETPOINT LOWER COMMAND PUSHBUTTON<br />
<br />
F:\UNITn\MODBUS.LST<br />
<br />
252 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Each line in F:\UNITn\MODBUS.LST contains the following information in this order: •<br />
<br />
(Write Status)<br />
<br />
•<br />
<br />
Table Point<br />
<br />
•<br />
<br />
CSDB Pointname<br />
<br />
•<br />
<br />
Mode<br />
<br />
•<br />
<br />
Gain<br />
<br />
•<br />
<br />
Offset<br />
<br />
•<br />
<br />
Units<br />
<br />
•<br />
<br />
Longname<br />
<br />
(Write Status) – A preceding plus sign (+) indicates that this is mapped to a Mark V command. In this case it is legal for the DCS to request a write to the point, and thus the TCI issues the command to the Mark V. The sample listing shows holding register 1 as an analog command, holding coil 1 as a logic command, and holding register 9 as a enumerated state variable that can be written to the Mark V. Logic Mark V commands can not be written if packed into holding registers (see above section on holding coils and holding registers). In this example, a 0 may select OFF, 1 may select CRANK, 2 may select AUTO, etc. Enumerated state variables are discussed in Chapter 5. Table Point – indicates which one of the four Mapping Tables and what point on the table is used for this point. CSDB Pointname – Mark V control signal database pointname that the coil or register maps. Mode – transmission mode that the data is sent in over the Modbus link. Gain – required to convert the Modbus value of registers to engineering units. Offset – required to convert the Modbus value of registers to engineering units. Engineering Units – displayed units associated with the above Modbus Gain and Offset for registers. A entry of HEX indicates that this point is not normally converted into engineering units, but displayed in hexadecimal. Special points, such as bit masks, are defined this way. Longname – description of the signal found in F:\UNITn\LONGNAME.DAT. Once F:\UNITn\MODBUS.LST is generated, do not edit it as running MODBUS_L overwrites any changes.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 253<br />
<br />
Modbus Data Format And Scaling Modbus Data Conversions: Logics Logic control database signal values can be transmitted to the DCS using either coils or registers. Coil data conversion corresponds to a single logic control database signal with the LSB indicating its state. When registers are used to transmit logic control database signal values, each bit corresponds to the state of a logic control database signal. A register having 16 bits corresponds to a group of (up to) 16 logicals with the least significant bit being the first logic CSDB signal in the group, and the MSbit as the last logic CSDB signal in the group. The two bytes are packed into the Modbus message using the normal rules for MSB and LSB order. The values of undefined bits in a packed register are transmitted as 0. Read carefully for details on the modes used in transmission of data, as some modes may not be suitable for bit packed registers.<br />
<br />
Modbus Data Conversions: Analogs Analog control database signal values can be transmitted using registers only. Since DCS vendors handle analog signals in different ways, such as 12 bit positive numbers, the TCI may be configured to transmit analog data in one of several modes. The following modes are currently supported to meet customer needs. This section defines how to convert each data type to engineering units. The Modbus listing file (see above) defines the data type for each signal. The conversion algorithms presented here define the conversion process at the most understandable level. The implementation of these algorithms do not always follow these algorithms directly as there are many different schemes used to prevent mathematical overflows in computations. The choice of the final implementation is left to the DCS vendor.<br />
<br />
RS16 If a point is of data type SIGN16, it is a signed 16-bit number. In this mode, the most significant bit of the 16 bit analog signal is treated as a sign bit, where a one is used to for negative values. C2 type signals are transmitted modulo 32768 to prevent the sign bit from being set. H2 and X2 types are transmitted directly with an assumed value of (-32768 to +32767). The convention of assuming the raw value is a fraction from -1.0 to +1.0 was used in defining the Modbus Gain and Offset. This allows the Gain to indicate the maximum (and minimum) value when the Offset is zero. The Modbus listing file defines the Modbus Gain and Offset required to calculate the value into engineering units, with the conversion being: Engineering units = (Raw_value) / 32768 * GAIN + OFFSET For example, Thermocouples are scaled with a gain of 2048 and an offset of 0 for conversion to DEG F. If the register value is 1120, the conversion to engineering units is: Engineering units = (1120) / 32768 * 2048 + 0 Engineering units = 70 DEG F<br />
<br />
254 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
RU16 If a point is of data type UNS16, it is an unsigned 16-bit number. This mode transmits F2 analog signals as unsigned 16 bit numbers by adding 32768. The most significant bit therefore turns from a sign bit into a bit with a weight of 32768. This transforms the range of F2 signals to [0,+65535]. The Modbus listing file defines the Modbus Gain and Offset required to calculate the value into engineering units, with the conversion being: Engineering units = (Raw_value) / 65536 * GAIN + OFFSET Example 1: If an UNS16 is used for a normal counter, the raw value is the value of the counter. If a counter has the value of 418, it is converted as: Engineering units = (418) / 65536 * 65536 + 0 Engineering units = 418 Example 2: A number that is normally a signed number in the Mark V is requested as an unsigned number. If the register value of a thermocouple was requested, it shows that in UNS16 mode the Modbus Gain is 4096, and the Offset is -2048 for DEG F. The conversion of the raw data value of 33888 to engineering units is: Engineering units = (33888) / 65536 * 4096 – 2048 Engineering units = 70 DEG F Converting a SIGN16 to an UNS16 causes no loss of resolution.<br />
<br />
UN12 If a point is of data type UNS12, it is an unsigned 12-bit number. The function of this mode is to restrict signals to a range of [0,+4095]. The Modbus listing file’s Modbus Gain and Offset define the conversion into engineering units, where the conversion is: Engineering units = (Raw_value) / 4096 * GAIN + OFFSET For example, if the register value of a thermocouple is requested, the listing file shows that the Modbus Gain is 4096 and the Offset is -2048 to get to DEG F. The conversion of the register value of 2118 to engineering units is: Engineering units = (2118) / 4096 * 4096 – 2048 Engineering units = 70 DEG F The conversion from SIGN16 to UNS12 causes a loss in resolution of 16:1 and should be avoided. Certain internal signal types (e.g. H2, X2) become meaningless if restricted to the UNS12 range and would therefore be transmitted directly without conversion (if requested by the DCS). Logics packed into registers also become meaningless if the register’s value is converted. The Modbus listing file will list these points with a mode of UNS16. Fortunately most analog signals that are of interest to the DCS are in an F2 representation. A gain of 1/16th is applied to F2 signals and 2048 is added to convert the range from [-32767,+32767] to [0,+4095]. The unsigned 16 bit signal type C2 is transmitted Modulo 4096 to also restrict the range to [0,+4095].<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 255<br />
<br />
HW12 A special version of the UNS12 mode is available for use with some models of DCS systems. These systems collect data using the normal UNS12 mode described above, but are unable to send analog setpoints to the Mark V using the same GAIN and OFFSET conversion. In these DCS systems, no OFFSET is allowed in the conversion of analog setpoint commands to Modbus register values, only a GAIN. To accommodate these systems, the HW12 mode reports data to the DCS using UNS12 mode, but uses a different formula for analog setpoint commands sent from the DCS to the Mark V. This scheme allows the DCS the full positive range of the Mark V command, but does prevent sending negative values. Analog setpoint commands in these systems are usually scaled in percentages. Make sure that the programming in the DCS reflects the fact that the scaling of the analog setpoint command to the Mark V is different than the scaling of the feedback signal from the Mark V. (The HW12 mode analog setpoint command is the only place where this is true.) For data from the Mark V to the DCS, the conversion is the same as the UNS12 mode: Engineering units = (Raw_value) / 4096 * GAIN + OFFSET For setpoint commands from the Mark V to the DCS and the DCS to the Mark V, the conversion is: Engineering units = (Raw_value) / 8192 * GAIN Raw_command_value = (Engineering units / GAIN) * 8192 Example: If a value position is requested, the listing file shows that the Modbus Gain is 256 and the Offset is 0 to get percent. The conversion of the register value of 1216 to engineering units is : Engineering units = (1216) / 8192 * 256 Engineering units = 38% To send the analog setpoint command to set the valve to this same position of 38%, the analog setpoint command value that must be sent is: Raw_command_value = (38) / 256 * 8192 Raw_command_value = 1216<br />
<br />
256 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
NATIVE If a point is of data type NATIVE, all analog signals are transmitted in their internal Mark V representation. This is the recommended mode because the signals can be transmitted directly without any manipulation, which could result in decreased resolution. Any 32-bit signal requires 2 registers to be assigned to it. These data points are defined in F:\UNITn\MODBUS_N.DAT, not the standard definition file. The most common signal types used in the Mark V are as follows: •<br />
<br />
L1<br />
<br />
logic signal, least significant bit indicating state zero or one.<br />
<br />
•<br />
<br />
F2<br />
<br />
16 bit signed two’s complement representation, range: [-32767,+32767].<br />
<br />
•<br />
<br />
C2<br />
<br />
16 bit unsigned representation, range: [0,+65535].<br />
<br />
•<br />
<br />
S2<br />
<br />
16 bit signed representation, range: [-32767,+32767].<br />
<br />
•<br />
<br />
H2<br />
<br />
16 bit unsigned representation used for bit masks.<br />
<br />
•<br />
<br />
X2<br />
<br />
16 bit unsigned representation used to form the lower 16 bits of long, 32 bit values.<br />
<br />
•<br />
<br />
F4<br />
<br />
32 bit signed two’s complement representation.<br />
<br />
•<br />
<br />
C4<br />
<br />
32 bit unsigned representation.<br />
<br />
•<br />
<br />
H4<br />
<br />
32 bit unsigned representation used for bit masks.<br />
<br />
•<br />
<br />
R4<br />
<br />
32 real floating point number.<br />
<br />
Modbus Command And Response Definition Introduction This section describes the commands and responses supported by the TCI to implement the Modbus communications and control functions needed. The TCI will be a slave station on an RS232 data link and will respond to commands from the master. Messages are transmitted and received using the RTU transmission mode, which is one of two Modbus transmission modes, where RTU transmits data in eight bit bytes. The other mode, where characters are transmitted in ASCII, is not supported. The RTU transmission mode uses the format below (where slave address, function code, CRC-16 MSB, CRC-16 LSB are all bytes): 6/$9( )81&7,21 &5& &5& $''5(66 &2'( '$7$ 06% /6% <br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 257<br />
<br />
RTU Transmission Mode slave address – number from 0 to 255 and specifies the unit with which to communicate (a slave address of zero is considered a broadcast message to all slaves). function code – specifies the purpose and format of the remaining message portion. CRC-16 – bytes are two bytes that complete each and every Modbus message. The abbreviation CRC stands for Cycle Redundancy Check, MSB stands for Most Significant Byte, and LSB stands for Least Significant Byte. These bytes are used for error checking and are calculated for each transmitted and received message to insure that no transmission error has occurred while the message was in transit. The method for calculating the CRC-16 is a public protocol and is described in numerous textbooks and the Gould Modicon Modbus Protocol Reference Guide. Please refer to these other documents for information on calculation of a correct CRC. Modbus over Ethernet adds the header below to the message formats. All the same functions are supported over Ethernet that are supported over the serial ports. ,19 ,19 35272 35272 6WDQGDUGVHULDO ,' ,' ,' ,' /(1 /(1 IXQFWLRQPHVVDJH 06% /6% 06% /6% 06% /6% <br />
<br />
invocation id – not used by the TCI Modbus. proto id – not used by the TCI Modbus. length – is the byte count of the remaining part of the message. This is used by the TCI Modbus to receive the rest of the message. The rest of the message is exactly what is sent and received over the serial connections.<br />
<br />
Message Errors When a message is received that cannot be acted upon, the message is either ignored and the TCI waits for the next message or it is responded to with an exception message. Any messages that are misunderstood, incomplete, or altered in some manner as indicated by framing error, parity error, or CRC-16 error are always ignored due to the fact that it is not possible to reliably determine for whom the message was intended. It is the master’s responsibility to detect this timeout condition and resend the message as necessary (see the section TCI Modbus Configuration above). Any time a message receipt is in progress and an interval of time corresponding to 3.5 character times (based on the baud rate) occurs without receipt of a character, the message receipt in progress is aborted and ignored. Message failures due to other causes are responded to with an exception response if no reception error has occurred and if the message was not a broadcast (slave address was zero).<br />
<br />
258 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
The exception code responses that are supported when a normal response is impossible is shown in the chart below. (see the section above on TCI Modbus Configuration concerning exception codes 04 and 06). Exception<br />
<br />
Code Name<br />
<br />
Meaning<br />
<br />
01<br />
<br />
Illegal Function<br />
<br />
The message function received is not supported<br />
<br />
02<br />
<br />
Illegal Data Address<br />
<br />
The address referenced in the data field is not in a permissible range.<br />
<br />
03<br />
<br />
Illegal Data Value<br />
<br />
The value transmitted in the data field is illegal.<br />
<br />
04<br />
<br />
Failure in Associated Device<br />
<br />
Information requested cannot be provided due to a communication failure with associated unit as specified by the slave address.<br />
<br />
06<br />
<br />
Device Busy<br />
<br />
Information requested cannot be provided due to a communication time out with the associated unit as specified by the slave address.<br />
<br />
Exception Code Responses<br />
<br />
Format of exception message reply from the slave is shown below: 6/$9( )81&7,21 (;&(37,21 &5& &5& $''5(66 &2'( &2'( 06% /6% <br />
<br />
Exception Code Response Format slave address – must be in the range [1-255]. Zero is not allowed as a reply, as it is only used in broadcast messages from the master. function code – is always equal to the master’s function code with the most significant bit set. Therefore, an exception response sent back to a master that has sent a message with function code 02 hex would have a function code of 82 hex (or 130 decimal) in the exception reply. exception code – as shown in chart below, only codes 01 through 04 and 06 are supported.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 259<br />
<br />
Function Code Details<br />
<br />
Function Code, Hex<br />
<br />
Description<br />
<br />
01<br />
<br />
Read Holding Coils<br />
<br />
02<br />
<br />
Read Input Coils<br />
<br />
03<br />
<br />
Read Holding Registers<br />
<br />
04<br />
<br />
Read Input Registers<br />
<br />
05<br />
<br />
Force (Write) Single Holding Coil<br />
<br />
06<br />
<br />
Preset (Write) Single Holding Register<br />
<br />
07<br />
<br />
Read Exception Status<br />
<br />
08<br />
<br />
Diagnostic<br />
<br />
0F<br />
<br />
Force (Write) Multiple Holding Coils<br />
<br />
10<br />
<br />
Force (Write) Multiple Holding Registers<br />
<br />
DCS Function Codes<br />
<br />
This chart lists the function codes supported by the TCI included in the messages sent from the DCS. Six of the eight function codes implemented in the TCI are used to read from and/or write to the four table types. See the above sections regarding mapping tables. Each function code and the TCI’s replies are described below.<br />
<br />
Function Code 01: Read Holding Coils Function code 01 is used to read the holding coil table. The format of a message from the master is shown below: 6/$9( )81&7,21 67$57 67$57 180% 180% &5& &5& $''5(66 &2'( &2,/ &2,/ &2,/6 &2,/6 06% /6% 06% /6% 06% /6% <br />
<br />
slave address – must be in the range [1-255], zero is not allowed. starting holding coil number – two bytes in length and may be any value less than the highest holding coil number available in the holding coil table. The starting holding coil number is equal to one less than the number of the first holding coil returned in the normal response to this request, i.e. to get the first holding coil, holding coil number 1, enter 0 for the starting holding coil number. The high order byte of the starting holding coil number field is sent as the first byte. The low order byte is sent next. number of holding coils value – two bytes in length and must be in the range from 1 to 2000 inclusive. It specifies the number of holding coils returned in the normal response. The sum of the starting holding coil value and the number of holding coils value must be less than or equal to the highest holding coil number available in the holding coil table. The high order byte of the number of holding coils field is sent as the first byte. The low order byte is sent next.<br />
<br />
260 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Format of normal message reply from the slave is shown below: 6/$9( )81&7,21 %<7( '$7$ '$7$ '$7$ &5& &5& $''5(66 &2'( &2817 %<7( %<7( %<7(Q 06% /6% byte count – is a binary number from 1 to 250; the specified number of data bytes follow.<br />
<br />
data field – is packed holding coil status data. Each byte contains eight holding coil values. The LSbit of the first byte contains the value of the holding coil whose number is equal to the starting holding coil number plus one. The value of the holding coils are ordered by number starting with the LSbit of the first byte of the data field and ending with the MSbit of the last byte of the data field. If the number of the holding coils is not a multiple of eight, then the last data byte contains zeros in one to seven of its highest order bits.<br />
<br />
Function Code 02: Read Input Coils Function code 02 is used to read the input coil table. The format of a message from the master is shown below: 6/$9( )81&7,21 67$57 67$57 180% 180% &5& &5& $''5(66 &2'( &2,/ &2,/ &2,/6 &2,/6 06% /6% 06% /6% 06% /6% <br />
<br />
slave address – must be in the range [1-255], zero is not allowed. starting input coil number – two bytes in length and may be any value less than the highest input coil available in the input coil table. The starting input coil number is equal to one less than the number of the first input coil returned in the normal response to this request, i.e. to get the first input coil, input coil number one, enter zero for the starting input coil number. The high order byte of the starting input coil field is sent as the first byte. The low order byte is sent next. number of input coils value – two bytes in length and must be in the range from 1 to 2000 inclusive. It specifies the number of input coils returned in the normal response. The sum of the starting input coil value and the number of input coils value must be less than or equal to the highest input coil available in the input coil table. The high order byte of the number of input coils field is sent as the first byte. The low order byte is sent next.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 261<br />
<br />
Format of normal message reply from the slave is shown below: 6/$9( )81&7,21 %<7( '$7$ '$7$ '$7$ &5& &5& $''5(66 &2'( &2817 %<7( %<7( %<7(Q 06% /6% byte count – binary number from 1 to 250; the specified number of data bytes follow.<br />
<br />
data field – is packed input coil status data. Each byte contains eight input coil values. The LSbit of the first byte contains the value of the input coil whose number is equal to the starting input coil plus one. The value of the inputs are ordered by number starting with the LSbit of the first byte of the data field and ending with the MSbit of the last byte of the data field. If the number of the input coils is not a multiple of eight, then the last data byte contains zeros in one to seven of its highest order bits.<br />
<br />
Function Code 03: Read Holding Registers Function code 03 is used to read holding registers. The format of a message from the master is shown below: 6/$9( )81&7,21 67$57 67$57 180% 180% &5& &5& $''5(66 &2'( 5(* 5(* 5(*6 5(*6 06% /6% 06% /6% 06% /6% <br />
<br />
slave address – must be in the range [1-255], zero is not allowed. starting holding register number – is two bytes in length and may be any value less than the highest holding register number available in the holding register table. The starting holding register number is equal to one less than the number of the first holding register returned in the normal response to this request, i.e. to get the first holding register number, holding register number one, enter zero for the starting holding register number. The high order byte of the starting holding register number field is sent as the first byte. The low order byte is sent next. number of holding registers – value is two bytes in length and must be in the range from 1 to 128 inclusive. It specifies the number of holding registers returned in the normal response. The sum of the starting holding register value and the number of holding registers value must be less than or equal to the highest holding register number available in the holding register table. The high order byte of the number of holding registers field is sent as the first byte. The low order byte is sent next.<br />
<br />
262 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Format of normal message reply from the slave is shown below: 6/$9( )81&7,21 %<7( ),567 ),567 /$67 &5& &5& $''5(66 &2'( &2817 5(*675 5(*675 5(*675 06% /6% 06% /6% /6% byte count – even binary number from 2 to 254, or zero. If the byte count is zero (0), then the master is to assume 256 data bytes follow. Otherwise, the specified number of data bytes follow. The byte count specifies the total number of bytes in the message following the byte count, not including the two CRC-16 bytes.<br />
<br />
holding registers – are returned in the data field in order of number with the lowest number holding register in the first two bytes, and the highest number holding register in the last two bytes of the data field. The number of the first holding register in the data field is equal to the starting holding register number plus one. The high order byte is sent before the low order byte of each holding register.<br />
<br />
Function Code 04: Read Input Registers Function code 04 is used to read input registers. The format of a message from the master is shown below: 6/$9( )81&7,21 67$57 67$57 180% 180% &5& &5& $''5(66 &2'( 5(* 5(* 5(*6 5(*6 06% /6% 06% /6% 06% /6% <br />
<br />
slave address – must be in the range [1-255], zero is not allowed. starting input register number – is two bytes in length and may be any value less than the highest input register number available in the input register table. The starting input register number is equal to one less than the number of the first input register returned in the normal response to this request, i.e. to get the first input register, input register number one, enter zero for the starting input register number. The high order byte of the starting input register number field is sent as the first byte. The low order byte is sent next. number of input registers – value is two bytes in length and must be in the range from 1 to 128 inclusive. It specifies the number of input registers returned in the normal response. The sum of the starting input register value and the number of input registers value must be less than or equal to the highest input register number available in the input register table. The high order byte of the number of input registers field is sent as the first byte. The low order byte is sent next. Format of normal message reply from the slave is shown below: 6/$9( )81&7,21 %<7( ),567 ),567 /$67 &5& &5& $''5(66 &2'( &2817 5(*675 5(*675 5(*675 06% /6% 06% /6% /6% byte count – even binary number from 2 to 254, or zero. If the byte count is zero (0), then the master is to assume 256 data bytes follow. Otherwise, the specified number of data bytes follow. The byte count specifies the total number of bytes in the message following the byte count, not including the two CRC-16 bytes.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 263<br />
<br />
input registers – are returned in the data field in order of number with the lowest number input register in the first two bytes, and the highest number input register in the last two bytes of the data field. The number of the first input register in the data field is equal to the starting input register number plus one. The high order byte is sent before the low order byte of each input register.<br />
<br />
Function Code 05: Force Single Holding Coil Function code 05 is used to force (or write) a single holding coil in the holding coil table. The format of a message from the master is shown below: 6/$9( )81&7,21 +2/',1* +2/',1* 67$7( &5& &5& $''5(66 &2'( &2,/ &2,/ +25 + 06% /6% 06% /6% ))+ <br />
<br />
slave address – must be in the range [1-255], zero is not allowed. holding coil number – is two bytes in length and may be any value less than the highest holding coil number available in the holding coil table. The holding coil number is equal to one less than the number of the holding coil forced, i.e. to change the first holding coil, holding coil number one, enter zero for the holding coil number. The high order byte of the starting holding coil number field is sent as the first byte. The low order byte is sent next. state byte – sent by the master with only two possible values. A zero is sent (00h) to turn the specified holding coil off (set false). A value of 255 is sent (FFh) to turn the specified holding coil on (set true). The state byte is always followed by a single byte with value zero. Format of normal message reply from the slave is identical to the received message.<br />
<br />
Function Code 06: Preset Single Holding Register Function code 06 is used to preset (or write) to a single holding register. The format of a message from the master is shown below: 6/$9( )81&7,21 +2/',1* +2/',1* 5(* 5(* &5& &5& $''5(66 &2'( 5(* 5(* '$7$ '$7$ 06% /6% 06% /6% 06% /6% <br />
<br />
slave address – must be in the range [1-255], zero is not allowed. holding register number – is two bytes in length and may be any value less than the highest holding register number available in the holding register table. The holding register number is equal to one less than the number of the holding register changed by this request, i.e. to change the first holding register, holding register number one (1), enter zero (0) for the holding register number. The high order byte of the starting holding register number field is sent as the first byte. The low order byte is sent next. holding register data field – is two bytes in length and contains the value to which the holding register specified by the holding register number field is preset. The first byte in the data field contains the high order byte of the preset value. The second byte in the data field contains the low order byte.<br />
<br />
264 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Format of normal message reply from the slave is identical to the received message.<br />
<br />
Function Code 07: Read Exception Status. Function code 07 is used to read the exception status data, defined as the first eight holding coils. These can be used to indicate slave controller status or condition of any other state. Function code 07 thus provides a short form of request for the purpose of reading these first eight holding coils, holding coils one through eight. The format of a message from the master is shown below: 6/$9( )81&7,21 &5& &5& $''5(66 &2'( 06% /6% <br />
<br />
slave address – must be in the range [1-255], zero is not allowed. Format of normal message reply from the slave is shown below: 6/$9( )81&7,21 '$7$ &5& &5& $''5(66 &2'( %<7( 06% /6% <br />
<br />
data byte field – the normal response is packed holding coil status data. The data byte contains eight holding coil values. The LSbit of the byte contains the value of the holding coil number one (1). The MSbit contains the value of holding coil number eight.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 265<br />
<br />
Function Code 08: Diagnostic Function code 08 is used to get diagnostic data. The purpose of the diagnostic message to test the communications system (the TCI); it does not affect the controller (the Mark V). The format of a message from the master is shown below 6/$9( )81&7,21 ',$* ',$* &5& &5& $''5(66 &2'( &2'( &2'( '$7$ '$7$ 06% /6% 06% /6% 06% /6% <br />
<br />
slave address – zero indicates that the message received is a broadcast. Nonbroadcast messages use a slave address in the range [1-255]. The TCI will respond to requests to its designated slave addresses, or to a broadcast. If the message is not a broadcast, the data returned will be from the unit as defined by the slave address and the TCI system configuration file. In the event that the message is a broadcast, no data will be returned. Only commands to reset counters and change Listen Only mode will be accepted as broadcast messages. diagnostic codes – shown below: data fields – zero unless specified otherwise. Format of normal reply message from the slave is shown below: 6/$9( )81&7,21 ',$* ',$* &5& &5& $''5(66 &2'( &2'( &2'( '$7$ '$7$ 06% /6% 06% /6% 06% /6% <br />
<br />
When a response is sent at all, the normal response to a diagnostic message by the slave is shown above, with each of the fields listed above identical to the corresponding field sent in the message received from the master except for diagnostic codes 0Ah through 0Eh, where the required data is returned.<br />
<br />
266 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Diagnostic Code (Hex)<br />
<br />
Name<br />
<br />
Meaning<br />
<br />
00<br />
<br />
Return Query Data<br />
<br />
The data passed in the data field will be returned to the DCS without modification.<br />
<br />
01<br />
<br />
Restart Comm Option<br />
<br />
This code causes the TCI to reset the RS232 port if necessary. It will also cause a reset of all error counters associated with the Modbus link if the high order byte of the data field is 255 (0FFh). If the TCI is in Listen Only caused by a previously issued command, the condition is reset to normal. A normal response is returned to the master before the restart is executed if and only if the TCI was not in Listen Only Mode (LOM).<br />
<br />
04<br />
<br />
Force slave to Listen Only Mode<br />
<br />
When this command is received, the TCI will not respond to any commands other than the Restart Comm Option command listed above.<br />
<br />
0A<br />
<br />
Clear Counters<br />
<br />
All error counters and the diagnostic register will be reset. A normal response will be sent. All counters are cleared upon each power up, reboot, Clear Counters command or Restart Comm Option command.<br />
<br />
0B<br />
<br />
Return Bus Message Count<br />
<br />
The total number of messages addressed to this TCI (broadcast and non-broadcast messages modulo 65536 will be returned to the master. This counter is cleared upon each power up, reboot, Clear Counters command or Restart Comm Option command.<br />
<br />
0C<br />
<br />
Return Bus CRC Error Count<br />
<br />
The total number of messages detected by the TCI that had a bad CRC modulo 65536 will be returned to the master. This counter is cleared upon each power up, reboot, Clear Counters command or Restart Comm Option command.<br />
<br />
0D<br />
<br />
Return Bus Exception Error Count<br />
<br />
The total number of exception response messages sent by the TCI modulo 65536 will be returned to the master. This counter is cleared upon each power up, reboot, Clear Counters command or Restart Comm Option command.<br />
<br />
0E<br />
<br />
Return Bus Slave Message Count<br />
<br />
The total number of messages addressed to this TCI (broadcast and non-broadcast) modulo 65536 will be returned to the master. This counter is cleared upon each power up, reboot, Clear Counters command or Restart Comm Option command.<br />
<br />
12<br />
<br />
Return Bus Overrun Message Count<br />
<br />
The total number of error in receiving a message from the serial port modulo 65536. This counter is cleared upon each power up, reboot, Clear Counters command or Restart Comm Option command.<br />
<br />
Function Code 08 Diagnostic Codes<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 267<br />
<br />
Function Code 0F: Force Multiple Holding Coils Function code 0F is used to force (or write) multiple holding coils in the holding coil table. The format of a message from the master is shown below: 6/$9( )81&7,21 67$57 67$57 180% 180% %<7( '$7$ '$7$ $''5(66 &2'( &2,/ &2,/ &2,/6 &2,/6 &2817 %<7( %<7(« ) 06% /6% 06% /6% DATA &5& &5& BYTE n 06% /6% <br />
<br />
<br />
<br />
Function Code 0F Message Format<br />
<br />
slave address – must be in the range [1-255], zero is not allowed. start coil number – is two bytes in length and may be any value less than the highest holding coil number available in the holding coil table. The holding coil number is equal to one less than the number of the holding coil forced, i.e. to change the first holding coil, holding coil number one, enter zero for the holding coil number. The high order byte of the starting holding coil number field is sent as the first byte. The low order byte is sent next. number of holding coils value – two bytes in length. It specifies the number of holding coils to set. The sum of the starting holding coil value and the number of holding coils value must be less than or equal to the highest holding coil number in the holding coil table. The high order byte of the number of holding coils field is sent as the first byte. The low order byte is sent next. byte count – is the number of data bytes to follow. data field – is packed holding coil data. Each byte contains eight holding coil values. The LS bit of the first byte contains the value of the holding coil whose number is equal to the starting holding coil number plus one. The value of the holding coils are ordered by number starting with the LSbit of the first byte of the data field and ending with the MSbit of the last byte of the data field. If the number of the holding coils is not a multiple of eight, then the last data byte contains unused data in its highest order bits. Format of normal message reply from the slave is identical to the received message without the byte count or the data.<br />
<br />
Function Code 10: Preset Multiple Holding Registers Function code 10 is used to preset (or write) to a multiple holding registers. The format of a message from the master is shown below: 6/$9( )81&7,21 67$57 67$57 180% 180% %<7( 5(* 5(* $''5(66 &2'( 5(* 5(* 5(*6 5(*6 &2817 '$7$ '$7$ « 06% /6% 06% /6% 06% /6% REG &5& &5& DATA n 06% /6% (LSB) <br />
<br />
268 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
slave address – must be in the range [1-255], zero is not allowed. start register number – is two bytes in length and may be any value less than the highest holding register number available in the holding register table. The holding register number is equal to one less than the number of the holding register changed by this request, i.e. to change the first holding register, holding register number one (1), enter zero (0) for the holding register number. The high order byte of the starting holding register number field is sent as the first byte. The low order byte is sent next. number of holding registers value – two bytes in length. It specifies the number of holding registers to set. The sum of the starting holding register value and the number of holding registers value must be less than or equal to the highest holding register number in the holding register table. The high order byte of the number of holding registers field is sent as the first byte. The low order byte is sent next. byte count – is the number of data bytes to follow. Register data field – is two bytes for each holding register to set. The first byte in the data field contains the high order byte of each preset value. The next byte contains the low order byte. Format of normal message reply from the slave is identical to the received message without the byte count or the data.<br />
<br />
Modbus Master Diagnostics When debug is on (on by default), global section trace buffer may be viewed with the command: gbl2file MModbus_trace# <some_file_name><br />
<br />
where # is 1,2,3...8 depending on which [MODBUS_MASTER_PORT] section corresponds to the information we want. If only one [MODBUS_MASTER_PORT] section exists, then the global section trace command could be viewed with: gbl2file MModbus_trace1 modbus1.dat<br />
<br />
This will display some debugging and program status information. The trace option may be turned off by adding /NOTRACE to the command line:<br />
<br />
MModbus /NOTRACE<br />
<br />
If the program encounters a serious error or warning, the result is placed into a log file as well as the global section trace buffer. The user should check file G:\LOG\MModbus#.log where # is defined as above.<br />
<br />
GEH-6126<br />
<br />
Chapter 7 Remote Access and Control • 269<br />
<br />
Statistics The Modbus Master program gathers statistics and makes counters available for diagnostic purposes. The program MM_stat.exe has been especially designed as a console program to communicate with the Modbus Master program and retrieve/control these diagnostic counters. Running MM_stat displays these counters as shown: F:\USER>mm_stat<br />
<br />
Modbus Master statistical summary: Modbus Master 1. 4815 = Count of messages sent by Modbus Master. 0 = Count of bad messages sent by Modbus Master. 4815 = Count of successful replies. 0 = Count of exception replies. 0 = Count of message timeouts. 0 = Count of buffer full, read error, etc.. 0 = Count of CRC errors. 0 = Count of bad received messages. Modbus Master 2. 4815 = Count of messages sent by Modbus Master. 0 = Count of bad messages sent by Modbus Master. 4745 = Count of successful replies. 0 = Count of exception replies. 45 = Count of message timeouts. 0 = Count of buffer full, read error, etc.. 0 = Count of CRC errors. 25 = Count of bad received messages. When multiple Modbus Masters appear, each group corresponds to a separate port as specified in the F:\IO_PORTS.DAT file. The counters can be reset by passing reset as a parameter to the MM_stat program. Reset is case insensitive and does not include the quotation marks.<br />
<br />
270 • Chapter 7 Remote Access and Control<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync<br />
<br />
Time Synchronization Time Synchronization within the Turbine Control is offered with one of the following: •<br />
<br />
Lower Accuracy option with software implementation only.<br />
<br />
•<br />
<br />
Time Synchronization option for SPEEDTRONIC™ Turbine Control systems synchronizes all Turbine Control panels on the stagelink to a Global Time Source (GTS) with a limited loss of accuracy. In addition, this option sets all operator interface computer timeclocks to the GTS. It is recommended that the remaining plant equipment, including Distributed Control Systems (DCSs), synchronize to this common GTS.<br />
<br />
Time Synchronization Features •<br />
<br />
Time Signal Sources<br />
<br />
•<br />
<br />
Turbine Control Time Synchronization supports several GTSs.<br />
<br />
Timecode signals supported:<br />
<br />
GEH-6126<br />
<br />
•<br />
<br />
IRIG-A<br />
<br />
•<br />
<br />
IRIG-B<br />
<br />
•<br />
<br />
NASA-36<br />
<br />
•<br />
<br />
2137<br />
<br />
Chapter 8 Time Sync • 271<br />
<br />
Supported GTSs that use periodic pulses: •<br />
<br />
1 PPS<br />
<br />
•<br />
<br />
1 PPM<br />
<br />
•<br />
<br />
1 PPH<br />
<br />
Typical GTSs are GPS (Global Positioning System) receivers such as the StarTime GPS Clock or other time processing hardware. The preferred time sources are UTC(Universal Time Coordinated) or GPS. However, the Time Synchronization option also supports a GTS using local time as its base time reference.<br />
<br />
272 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
Software Setup” on page 283 discusses the setup for specifying local or global.<br />
<br />
General Architecture The GTS supplies a time link network to one or more operator interface computers. Special time/frequency processor boards such as the bc620AT and the TPRO_PC are placed in these computers. These boards acquire time from the GTS with a high degree of accuracy. When the computers receive the time signal, it is sent to the Turbine Control panels using a special purpose Stagelink Timesync protocol. This protocol minimizes time losses. Figure ## show a general plant-wide time synchronization setup.<br />
<br />
T u r b in e C o n tro l<br />
<br />
T u r b in e C o n tro l<br />
<br />
T u r b in e C o n tro l<br />
<br />
T u r b in e C o n tro l<br />
<br />
T E R M IN A T IO N R E S IS T O R<br />
<br />
S T A G E L IN K<br />
<br />
T E R M IN A T IO N R E S IS T O R O p e r a to r In te r fa c e<br />
<br />
O p e ra to r In te rfa c e<br />
<br />
O p e ra to r In te rfa c e<br />
<br />
*<br />
<br />
O p e ra to r In te rfa c e<br />
<br />
*<br />
<br />
*<br />
<br />
C O M M O N T IM E R E F E R E N C E B U S T IM E L IN K TO D C S E Q U IP M E N T<br />
<br />
G LO BAL T IM E S O U R C E<br />
<br />
* O p t io n a l Typical Time Synchronization Architecture<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 273<br />
<br />
Backup Synchronization Redundancy provides backup time synchronization. Supplying time/frequency processor boards to two or more operator interfaces is redundant. Not all operator interfaces require these boards. Those that do not contain time/frequency processor boards do not attempt to send time to the Turbine Control. Instead, they become time slaves to the selected Stagelink Time Master in the same way that all Turbine Control panels are time slaves. The Stagelink Time Master is the common operator interface selected by all other equipment on the stagelink as the official time source. Failure of this source results in all time slaves selecting another, but common, operator interface as the new Stagelink Time Master.<br />
<br />
Documentation Organization This documentation is organized as follows:<br />
<br />
Overview This section describes Turbine Control Time Synchronization and its function. An overview of this documentation, as well as related publications, are also presented in this section.<br />
<br />
Basic Theory of Turbine Control Time Synchronization This section describes how Turbine Control time Synchronization works and the logic that runs the system. An overview of supported GTSs is given in this section.<br />
<br />
Hardware Setup This section describes how to set up the Turbine Control Time Synchronization hardware.<br />
<br />
Software Setup and Configuration This section describes how to configure the software to run Turbine Control Time Synchronization.<br />
<br />
General Timesync Operations This section explains some general operations of Turbine Control Time synchronization. Use of the TIMEUTIL program is described here.<br />
<br />
Diagnostics and Troubleshooting This section discusses how to get general information from Turbine Control Time synchronization. Other ways to diagnose problems with the Turbine Control Time Synchronization are explained here.<br />
<br />
Sample Timesync Configurations Three examples of possible Turbine Control Time Synchronization setups are discussed in this section.<br />
<br />
274 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
Appendix A - IRIG Nomenclature Defines the nomenclature for standard IRIG Time Codes.<br />
<br />
Glossary Defines acronyms and terms used in this documentation.<br />
<br />
Related Documents GE Industrial Systems provides the applicable documents to customers as needed to support equipment it supplies. For documentation that covers equipment from other companies, contact the applicable manufacturer. GE Publications: GEH-5979 - SPEEDTRONIC™ Mark V Turbine Control User’s Manual GEH-5980 - SPEEDTRONIC™ Mark V Turbine Control Maintenance Manual GEH-6195 - SPEEDTRONIC™ Mark V Turbine Control Applications Manual GEH-6123 - SPEEDTRONIC™ Mark V Turbine Control Historian Maintenance Guide and User’s Manual Other: Handbook of Time Code Formats, 1987, Datum Inc. bc620AT Time and Frequency Module, Operation and Technical Manual, 1994, Datum Inc. Bancomm Div. bc627AT GPS Satellite Receiver Addendum User’s Guide, 1993, Datum, Inc. Bancomm Div. TPRO_PC, Operation and Maintenance Manual, 1994, KSI A division of Odetics<br />
<br />
Time Synchronization Theory This section refers to the High Accuracy synchronization option and explains the basic theory of synchronizing Turbine Control time to the GTS. Selection of the Stagelink Time Master is discussed in this section as well as supported GTSs.<br />
<br />
Timesync Protocol The Time Processing Board is used to get time for one or more operator interface computers with a high degree of accuracy. Time is then sent to each Turbine Control and operator interface time slave using an internal Stagelink Timesync protocol. This protocol is specifically designed to minimize the loss of accuracy in the time slaves. Each operator interface with a Time Processing Board is an available Stagelink Time Master. Each available Stagelink Time Master periodically broadcasts an identification message to all time slaves. Each time slave collects the list of available Stagelink Time Masters and selects the same node for its time reference. Periodically, each time slave asks for the current global time, noting at the same instant, what local time it has. The Stagelink Time Master notes the global time at the instant the request for time is received. Next, the Stagelink Time Master returns the recorded global time. The time slave computes the difference between the returned time and the recorded time of request and adjusts its internal time accordingly.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 275<br />
<br />
Local time is used for display of real-time data. This is done by adding a local time correction to UTC. A node’s internal time clock is normally Global rather than Local. This is done because global time steadily increases at a constant rate while corrections are allowed to local time. Historical data is stored with global time to minimize discontinuities. Backup is provided if either the GTS or Stagelink Time Master becomes inoperative. If the GTS becomes inoperative, the Time Processing Board goes to flywheel mode with a maximum drift of ±2 ms per hour. In most cases, this allows sufficient time to repair the GTS without severe disruption of the plant’s system time. If the primary Stagelink Time Master becomes inoperative, then each of the time slaves picks another, but common, secondary Stagelink Time Master. This means that each node on the Stagelink locks onto the identical reference for its own time, even if the primary and secondary Stagelink Time Masters had different time bases for their references. The Turbine Control selects the best Stagelink Time Master if multiple Stagelinks exist and Stagelink Time Masters exist on each network. This means that if two operator interfaces on the same stagelink are available Stagelink Time Masters and one of them has lost contact with the GTS time signals, each time slave selects the other available Stagelink Time Master as its time reference of choice. If multiple available Stagelink Time Masters exist, each time slave selects the current Time Master based on the following: •<br />
<br />
Is the Time Master tracking the GTS<br />
<br />
•<br />
<br />
Which Time Master has the lowest Stagelink (ARCNET®) address.<br />
<br />
•<br />
<br />
Supported GTSs<br />
<br />
The Time Processing Boards support the use of several different time sources. However, the Time Synchronization software does not support all source supported by the Time Processing Board.<br />
<br />
276 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
The following is a list of time source, and their characteristics that are supported by both the Time Processing Board and the Time Synchronization software: •<br />
<br />
Modulated IRIG-A, IRIG-B, 2137, or NASA-36 timecode signals.<br />
<br />
Note IRIG-A and 2137 are not supported on TPRO_PC. Modulation ratio 3:1 to 6:1 Amplitude 0.5 to 5 volts peak to peak •<br />
<br />
DC Level shifted IRIG-A, IRIG-B, or NASA-36 timecode signals. Note DC Level Shift is not supported on TPRO_PC. TTL/CMOS compatible voltage levels<br />
<br />
•<br />
<br />
1 PPS (one pulse per second) using the External 1 PPS input signal of the Time Processing Board TTL/CMOS compatible voltage levels, positive edge on time<br />
<br />
•<br />
<br />
1 PPM (one pulse per minute) using the Event Capture input signal of the Time Processing Board TTL/CMOS compatible voltage levels, positive edge on time 20 nanosecond minimum pulse width, 250 nanosecond minimum period<br />
<br />
•<br />
<br />
1 PPH (one pulse per hour) using the Event Capture input signal of the Time Processing Board TTL/CMOS compatible voltage levels, positive edge on time 20 nanosecond minimum pulse width, 250 nanosecond minimum period<br />
<br />
No Signal using the low-drift clock on the Time Processing Board in flywheel mode as the sole time source for the plant<br />
<br />
GPS Interface This applies only to bc627AT Time Processing Board There are two-time source supported by the Time Processing Board but not supported by the Time Synchronization software. These signals are XR3 tomcods and Negative Edge on time inputs. Please refer to Appendix A for IRIG timecode nomenclature.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 277<br />
<br />
Hardware Setup Testing the Time and Frequency Board This section discusses the proper testing procedures for the bc620AT/bc627AT Time and Frequency Board. To set up the Time Synchronization hardware, the Time Processing Board must be correctly installed in the operator interface and then configured for this application. The setup of the Time Processing Board for the Turbine Control Time Synchronization option, involves setting hardware jumpers to select the base I/O address of the board (see “Setting Base I/O Address” on page 279 for bc620AT or “Setting Base I/O Address” on page 281 for TPRO_PC), and disabling the IRQ (Interrupt Request) since the software makes no use of interrupts for the board (see “Setting the IRQ” on page 279 for bc620AT or “Setting the IRQ” on page 281 for TPRO_PC). Then the GTS and the operator interfaces must be connected (see “Connecting the GTS to ” on page 279 for bc620AT or “Connecting the GTS to the Board” on page 282 for TPRO_PC and “Connecting the Operator Interface” on page 282).<br />
<br />
BANCOMM bc620AT<br />
<br />
J1<br />
<br />
I/O ADDRESS<br />
<br />
SW1 IRQ JUMPERS<br />
<br />
J2<br />
<br />
JP1<br />
<br />
Typical bc620AT/bc627AT Time and Frequency Module<br />
<br />
Board Installation The bc620AT or bc627AT board can be placed in any spare ISA(Industry Standard Architecture) slot of an operator interface. See the PC vendor user manual that comes with the operator interface for proper installation procedures. See Manufacturing documentation for details of soft switch settings.<br />
<br />
278 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
Setting Base I/O Address The bc620AT or bc627AT board is shipped from the Bancomm factory with a base I/O address of 0x0300. This address conflicts with the base I/O address used in operator interfaces with Ethernet® boards and those with the Historian option (see GEH-6123C, The Mark V Historian Maintenance Guide and User’s Manual). Therefore, always set the base I/O address to 0x0280 as shown in Figure 3-2. Address Bit<br />
<br />
1<br />
<br />
2<br />
<br />
A9<br />
<br />
A8<br />
<br />
A7<br />
<br />
A6<br />
<br />
3<br />
<br />
4<br />
<br />
5<br />
<br />
6<br />
<br />
A5<br />
<br />
A4<br />
<br />
ON<br />
<br />
OFF OPEN<br />
<br />
SW1<br />
<br />
INDICATES DIRECTION OF TOGGLE ON = 0 OFF = 1 A9 A8 1<br />
<br />
A7 A6 A5 A4<br />
<br />
0<br />
<br />
1<br />
<br />
0<br />
<br />
0<br />
<br />
0<br />
<br />
A3 A2 A1 A0 0<br />
<br />
0<br />
<br />
0<br />
<br />
0<br />
<br />
= 0x0280<br />
<br />
SW1 Base I/O Address switch selections<br />
<br />
Setting the IRQ Adjust the board’s IRQ setting to No IRQ as shown in the figure below:<br />
<br />
IR 15<br />
<br />
IRQ<br />
<br />
IR 14<br />
<br />
IR 12<br />
<br />
IR 11<br />
<br />
IR 10<br />
<br />
IR 9<br />
<br />
IR 7<br />
<br />
IR 6<br />
<br />
IR 5<br />
<br />
IR 4<br />
<br />
IR 3<br />
<br />
JP 1<br />
<br />
Pin<br />
<br />
1<br />
<br />
3<br />
<br />
5<br />
<br />
7<br />
<br />
9<br />
<br />
11<br />
<br />
13<br />
<br />
15<br />
<br />
17<br />
<br />
19<br />
<br />
21<br />
<br />
23<br />
<br />
IRQ selection on bc620AT and bc627AT<br />
<br />
Connecting the GTS to bc627AT The bc627AT has two connectors, J1 and J2 (see Figure 3-1). J1 is not used for this application. J2 is a 12-pin receptacle and is used to connect to a GPS receiver core module. Please refer to bc627AT GPS Satellite Receiver Addendum User’s Guide for information regarding placement of the GPS antenna.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 279<br />
<br />
N O I R Q<br />
<br />
Connecting the GTS to bc620AT The bc620AT has two connectors, J1 and J2 (see Figure 3-1). J2 is not used for this application. J1 is a 15-pin receptacle D-connector and is used to connect the GTS. The type of GTS determines how J1 is interfaced. For most GTSs, a 15-pin to BNC adapter is used. This connector consists of a 15-pin plug D-connector, and five BNC receptacle connectors. Figure 3-4 shows a diagram of this adapter.<br />
<br />
Adapter<br />
<br />
Receptacle BNC’s<br />
<br />
To bc620AT J1<br />
<br />
(GTS Source) Timecode Input (Modulated)<br />
<br />
(IRIG-A, IRIG-B, NASA36, or 2137)<br />
<br />
Event Input<br />
<br />
(1 PPM or 1 PPH)<br />
<br />
1 PPS Output<br />
<br />
(Optional External Use)<br />
<br />
1 PPS Input<br />
<br />
(1 PPS)<br />
<br />
Timecode Output<br />
<br />
(Flywheel Mode Out)<br />
<br />
15-pin D Plug 15-Pin D to BNC Adapter.<br />
<br />
Time Processing Board TPRO_PC The illustration below shows the general layout of the TPRO_PC board.<br />
<br />
P4<br />
<br />
I/O ADDRESS<br />
<br />
J1<br />
<br />
P3<br />
<br />
J2<br />
<br />
IRQ JUMPERS<br />
<br />
J3 P2<br />
<br />
TPRO_PC Time Processing Board<br />
<br />
280 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
Board Installation The TPRO_PC board can be placed in any spare ISA (Industry Standard Architecture) slot of an operator interface. See the PC vendor user manual that comes with the operator interface for proper installation procedures.<br />
<br />
Setting Base I/O Address The TPRO_PC board is shipped from KSI Odectics with a base I/O address of 0x0300. This address conflicts with the base I/O address used in operator interfaces with Ethernet® boards and those with the Historian option (see GEH6123C, The Mark V Historian Maintenance Guide and User’s Manual). Therefore, always set the base I/O address to 0x0280 as shown in the figure below: Connected Pins = 0<br />
<br />
I/O ADDR JP=0<br />
<br />
Open Pins = 1<br />
<br />
P3 1110 9 8<br />
<br />
7654<br />
<br />
0000 0010 1000 0000<br />
<br />
Pin<br />
<br />
11<br />
<br />
8<br />
<br />
9<br />
<br />
10<br />
<br />
7<br />
<br />
6<br />
<br />
5<br />
<br />
0<br />
<br />
4<br />
<br />
2<br />
<br />
8<br />
<br />
0<br />
<br />
Base I/O Address pin selections<br />
<br />
Event Input The TPRO_PC board is shipped from KSI Odectics with Event Input disabled. Event Input is used for 1 PPM and 1 PPH references. To enable Event Input, adjust the board’s settings as shown in the figure below:<br />
<br />
P4 E<br />
<br />
X<br />
<br />
D<br />
<br />
Event Input enabled on TPRO_PC<br />
<br />
Setting the IRQ Adjust the board's IRQ setting to No IRQ as shown in the figure below:<br />
<br />
7<br />
<br />
6<br />
<br />
5<br />
<br />
4<br />
<br />
3<br />
<br />
2<br />
<br />
14<br />
<br />
15<br />
<br />
12<br />
<br />
11<br />
<br />
10<br />
<br />
NO IRQ<br />
<br />
IRQ P2 IRQ selection on TPRO_PC<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 281<br />
<br />
Connecting the GTS to the Board The TPROC_PC has one panel connector, J1 and two BNC connectors, J2 and J3. J1 is a 15-pin receptacle D-connector and is used to connect the GTS. The type of GTS determines how J1 is interfaced. For most GTSs, a 15-pin to BNC adapter is used. This connector consists of a 15-pin plug D-connector, and five BNC receptacle connectors. The figure below shows a diagram of this adapter. J2 can be connected to a timecode input and J3 may be used as a timecode output.<br />
<br />
Receptacle BNC’s<br />
<br />
Adapter<br />
<br />
To TPRO_P J1<br />
<br />
(GTS Source) Timecode Input (Modulated)<br />
<br />
(IRIG-B or NASA36)<br />
<br />
Event Input<br />
<br />
(1 PPM or 1 PPH)<br />
<br />
1 PPS Output<br />
<br />
(Optional External Use)<br />
<br />
1 PPS Input<br />
<br />
(1 PPS)<br />
<br />
Timecode Output<br />
<br />
(Flywheel Mode Out)<br />
<br />
15-pin D Plug<br />
<br />
15-Pin D to BNC Adapter.<br />
<br />
Connecting the Operator Interface All available Stagelink Time Masters are wired as a bus configuration using RG-58 coaxial cable and T-connectors. Since the timecode signals are low frequency signals (1 kHz for IRIG-B), special terminating resistors are not required. This is in contrast to the 50 ohm resistors required for Ethernet (10 MHz) or the 93 ohm resistors required for Stagelink (2.5 MHz).<br />
<br />
! Caution<br />
<br />
! Caution<br />
<br />
282 • Chapter 8 Time Sync<br />
<br />
Use the same lightning protection techniques for the timelink as for Stagelink or Ethernet. See the documentation for these networks for protection techniques to be used.<br />
<br />
The timelink cabling (RG-58) is identical to that used for Ethernet and very similar to that used for Stagelink (RG-62). Label all cables used for timelink differently than the other network cables. Damage to equipment is possible if these cables are interconnected.<br />
<br />
GEH-6126<br />
<br />
Software Setup The Timesync software must be configured correctly in order to communicate over the Stagelink. Data files must be modified to define the Stagelink Time Master and specify the time base.<br />
<br />
Timesync Data File The Stagelink driver program in the operator interface sends time to the Turbine Control panels. This program uses the file F:\TIMESYNC.DAT to get information regarding timesync/timeset information. The key lines in F:\TIMESYNC.DAT are shown below: ---------------------------------------------------------TIMESYNC [<controller> MODE <mode> [LEVEL_SHIFT] | LOWRES | SLAVE] LOCAL_TIMESET [ENABLED | DISABLED] I_TIME [LOCAL | UTC] MARKV_TIME [LOCAL | UTC] TIME_SOURCE [LOCAL | UTC] TIME_LOAD [MANUAL | LOCAL |NETWORK] ----------------------------------------------------------<br />
<br />
File Configuration A template file for timesync is in G:\DATA\TIMESYNC.DAT. Copy this template file to F:\TIMESYNC.DAT and edit as required. An example of the template file TIMESYNC.DAT is shown below: ;-----------------------------------------------------------; ; TIMESYNC Parameters. 11-JUL-1995 ; Last Update: 14-MAR-1997 ; ; The line beginning with "TIMESYNC" indicates time acquisition hardware ; exists in the system. The syntax of this line is: ; ; TIMESYNC <controller> MODE <mode> [LEVEL_SHIFT] ; ; where <controller> is one of the following: ; BC620AT (from Bancomm, Division of Datum Inc.) ; PC-SG2 (from TrueTime Inc.) ; ISA-SYNCCLOCK16 (from JXI2 Inc.) ; TPRO-PC (from KSI, Division of Odetics Inc.) ; ; ; <mode> defines the external time reference and ; is one of the following: ; IRIG-A IRIG-A Timecode. ; IRIG-B IRIG-B Timecode. ; NASA-36 Nasa 36 bit timecode. ; 2137 2137 Timecode. ; 1PPS 1 pulse per second. ; 1PPM 1 pulse per minute. ; 1PPH 1 pulse per hour. ; FLYWHEEL Free Running Clock. ; "LEVEL_SHIFT" is specified if the timecode is DC Level Shifted ; rather than modulated. ; ; Different timeboards do not support all <mode> selections. The ; following table defines available combinations of timeboards and ; mode combinations: ; ; TimeBoard External Time References Supported ; ------------------------------------------<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 283<br />
<br />
; BC620AT IRIG-A (Modulated and DC Level Shifted) ; IRIG-B (Modulated and DC Level Shifted) ; NASA-36 (Modulated and DC Level Shifted) ; 2137 (Modulated only) ; 1PPS, 1PPM, and 1PPH ; FLYWHEEL ; ; TPRO-PC IRIG-B (Modulated only) ; NASA-36 (Modulated only) ; 1PPS (Requires -m option on board) ; 1PPM and 1PPH ; FLYWHEEL ; ; PC-SG2 IRIG-A (Modulated and DC Level Shifted) ; IRIG-B (Modulated and DC Level Shifted) ; 1PPM and 1PPH ; FLYWHEEL ; ; ISA-SYNCCLOCK16 IRIG-A (Modulated only) ; IRIG-B (Modulated only) ; NASA-36 (Modulated only) ; 1PPS, 1PPM, and 1PPH ; FLYWHEEL ; TIMESYNC BC620AT MODE IRIG-B ; ; "LOCAL_TIMESET [ENABLED | DISABLED]" is used to allow the operator interface ;time to be set to the same time as the Stagelink Time Master. Note the operat or ;interface does not require a time/frequency board in order to be a time sla ve. ; LOCAL_TIMESET ENABLED ; ; "I_TIME", "MARKV_TIME" and "TIME_SOURCE" identify what timebase is used ; in the operator interface, the Turbine Control, and the Global Time Source. ; Choices are UTC and LOCAL. ; ; NOTE: MARK V Plus panels always have UTC as their timebase. This is not ; changeable. ; I_TIME LOCAL MARKV_TIME LOCAL TIME_SOURCE UTC ; ; "TIME_LOAD [MANUAL | LOCAL | NETWORK]" defines whether major time elements ; (year, day-of-year etc.) are derived from the PC automatically (i.e. LOCAL); ; or obtained from other Stagelink Time Masters (i.e. NETWORK), ; or whether TIMESYNC functions are disabled until major time is entered ; manually via TIMEUTIL (i.e. MANUAL). ; TIME_LOAD LOCAL ; ; "TIMESET <node-address>" is used when Mark V panels with older versions ; of firmware exist on the stagelink that do not support the timesync ; protocol. In this case, this computer can act as a "repeating timeset" ; computer, transmitting time every hour. <node-address> is the Arcnet ; address in HEX and must be in the range 01-FF. There may be up to ; 32 "TIMESET <node-address>" lines specified in this datafile. ; ;-------------------------------------------------------------------<br />
<br />
284 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
The file’s key words and their significance are listed below: •<br />
<br />
TIMESYNC<br />
<br />
If the "TIMESYNC" line is missing, the operator interface will not have Stagelink Time Master functions. However, the other lines may be specified such that the operator interface is a time slave. The TIMESYNC line may be setup using one of the following: TIMESYNC <controller> MODE <mode> [LEVEL_SHIFT] •<br />
<br />
controller [BC620AT | BC627AT | TPRO_PC] BC620AT / BC627AT / TPRO_PC is the name of the Time/Frequency Processor board.<br />
<br />
•<br />
<br />
MODE <mode><br />
<br />
<mode> defines the type of global time source, and is one of the following: IRIG-B<br />
<br />
Modulated IRIG-B Time Code Signal<br />
<br />
IRIG-A<br />
<br />
Modulated IRIG-A Time Code Signal (N/A for TPRO_PC)<br />
<br />
NASA-36<br />
<br />
Modulated NASA-36 Time Code Signal<br />
<br />
2137<br />
<br />
Modulated 2137 Time Code Signal (N/A for TPRO_PC)<br />
<br />
1PPS<br />
<br />
One pulse per second time input<br />
<br />
1PPM<br />
<br />
One pulse per minute time input<br />
<br />
1PPH<br />
<br />
One pulse per hour time input<br />
<br />
FLYWHEEL Use the Time Processing Board itself as the GTS GPS<br />
<br />
GPS Reference Signal (bc627AT only)<br />
<br />
LEVEL_SHIFT is used if IRIG-x, NASA-36, or 2137 timecodes are dc Level Shifted instead of modulated signals. This applies to bc620AT only. TIMESYNC LOWRES This statement implies that the Lower Accuracy Time Synchronization option with software implementation only has been selected. TIMESYNC SLAVE This statement implies that the Lower Accuracy Time Synchronization option with software implementation only has been selected and that this interface can only be a Slave, never a Master. LOCAL_TIMESET [ENABLED | DISABLED] This line defines whether the operator interface time is set to the time defined by the stagelink time master (ENABLED), or follows the CMOS clock (DISABLED). I_TIME [LOCAL | UTC] I_TIME is only applicable if the line LOCAL_TIMESET ENABLED (above) exists in the data file. This customer-specified parameter defines whether the internal time of the IDP or <I> is set to UTC or Local Time.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 285<br />
<br />
MARKV_TIME [LOCAL | UTC] This customer-specified parameter defines whether the Mark V panel time is UTC based or Local Time based. TIME_SOURCE [LOCAL | UTC] This line specifies whether the GTS is UTC based or Local Time based. This parameter applies only to timecode GTSs; it does not apply to pulse input time sources. TIME_LOAD [MANUAL | LOCAL | NETWORK] This line enables or disables the automatic loading of initial major time fields. No Stagelink Timemaster will send time until all major time elements are loaded, and time is locked to the GTS. MANUAL disables the operator interface as a Stagelink time master until major time elements are manually entered. See “Using the TIMEUTIL Program” on page 288 describing the TIMEUTIL program for more details. LOCAL specifies that major time is loaded automatically from the operator interface’s CMOS clock. NETWORK specifies that major time is loaded from another Stagelink Timemaster, assuming multiple operator interfaces on the Stagelink have Time/Frequency processor boards installed. For IRIG-A, IRIG-B and NASA-36 timecodes, major time elements consist only of the year (since these are time-of-year timecodes). For 2137 timecode, major time consists of current year, month and day, as this is a time-of-day timecode. For pulse input styles of GTS, major time consists of current year, month, day, hour, minute, and seconds. Note TIME_LOAD LOCAL is not recommended for 1 PPS Global Time Sources, since the CMOS clock may have errors in time on the order of several seconds.<br />
<br />
Note All operator interfaces in a system must be setup in F:\TIMESYNC.DAT in an identical fashion, with the exception of those computers not having a Time Processing card installed. Failure to have identical system setup can cause shifts in the Stagelink Time Reference upon power down of the primary Stagelink Time Master. Note Operator interfaces not containing a Time Processing card should have the identical lines in F:\TIMESYNC.DAT, but with the "TIMESYNC..." line commented out.<br />
<br />
286 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
TCI Control Panel Applet When the TCI system is installed, a Windows NT applet, TCI, is created. With this application, a TCI dialog box containing a tab labeled Time Sync appears. Under this tab, the user is able to make selections concerning the Time Acquisition Hardware and High Resolution Time Card. If TCI setup is told that a Time Processing Board exists, the fields containing the Base IO Address and Card Type are loaded and are available for entry. Otherwise, these fields are grayed out and are not available for entry. An example of this applet is shown below:<br />
<br />
Timesync Operation This chapter covers normal timesync/timeset operations, as well as use of the TIMEUTIL program.<br />
<br />
General Operations<br />
<br />
GEH-6126<br />
<br />
•<br />
<br />
Upon bootup, no operator interface acts as an available Stagelink Timemaster until the following conditions are met:<br />
<br />
•<br />
<br />
Major Time elements (year, month, day etc.) have been acquired from CMOS memory, another Stagelink Time Master, or manually through the TIMETUTIL program.<br />
<br />
•<br />
<br />
The GTS has established its presence and the Time Processing Board has asserted its tracking status bit. (This is ignored if mode is set to FLYWHEEL.) For pulse input GTS, at least one reference pulse must have been recorded after Major Time was loaded.<br />
<br />
•<br />
<br />
For GPS operation (bc627AT), timesync functions will not commence until the bc627AT has established contact with 4 satellites and determined its position. Depending on installation conditions, this may take anywhere from 3 to 20 minutes.<br />
<br />
Chapter 8 Time Sync • 287<br />
<br />
Note The first item number above does not occur automatically upon bootup if the line TIMELOAD MANUAL is specified in F:\TIMESYNC.DAT. Use of the TIMEUTIL program is required to load major time elements in this case. •<br />
<br />
Every 20 seconds, each available Stagelink Time Master broadcasts an identification message announcing its availability.<br />
<br />
•<br />
<br />
Every 20-32 seconds, each Turbine Control panel asks the selected Stagelink Time Master for the current date and time. It jumps or slews its internal time based on the time error calculated. The rate of slew allows for sub-millisecond errors, assuming the GTS is stable.<br />
<br />
•<br />
<br />
Every 60 seconds, all nodes select the Stagelink Time Master of choice, if more than one is available. This selection is based on Stagelink address, timesync accuracy, and tracking status (as stated in “Time Synchronization Theory” on page 275).<br />
<br />
•<br />
<br />
Every 20 minutes, each operator interface with the LOCAL_TIMESET ENABLED line in F:\TIMESYNC.DAT performs a TIMESET function by asking the selected Stagelink Time Master for the current date and time. Unlike the timesync function in the Turbine Control, the timeset function in the operator interface does not slew its internal time. Instead, it jumps. The time error in this timeset function is typically ±10 ms, assuming the GTS is stable.<br />
<br />
•<br />
<br />
Each available Stagelink Time Master does a limited amount of stability checking on the Global Time Source (timecode GTSs only). If the time-of-year ever changes by more than ±30 seconds (except changing from December 31, 23:59:59 to January 1, 00:00:00), the timesync function is disabled for a minimum of three minutes. If the time-of-year continuously increases at a normal rate for more than three consecutive minutes, the timesync function automatically resumes.<br />
<br />
Using the TIMEUTIL Program The TIMEUTIL program controls time synchronization in the operator interface functioning as the Stagelink Time Master. This program is used to do the following: •<br />
<br />
Obtain status about the Stagelink Time Master, and other available time masters on the Stagelink<br />
<br />
•<br />
<br />
Enable or Disable the timesync functions<br />
<br />
•<br />
<br />
Set the Major Time in the Stagelink Time Master<br />
<br />
TIMEUTIL is a maintenance program and is only accessible from the Command Console Window. If run without parameters, TIMEUTIL gives limited help on its usage. Listed below are a few operations in TIMEUTIL.<br />
<br />
Turning Off the TIMESYNC Function To turn off the timesync function in an available Stagelink Time Master, enter: C:\> TIMEUTIL TIMESYNC DISABLE<br />
<br />
Restoring the TIMESYNC Function To restore the timesync function in an available Stagelink Time Master, enter: C:\> TIMEUTIL TIMESYNC ENABLE<br />
<br />
288 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
Loading MAJOR TIME into the Time Processing Board Depending on the type of GTS and TIME_LOAD option specified in F:\TIMESYNC.DAT, the operator interface may not act as an available Stagelink Time Master until Major Time is loaded and the Time Processing Board is locked on to the GTS. This means it is "tracking" the GTS. To load Major Time into the Time Processing Board, enter: C:\> TIMEUTIL TIMELOAD DD-MMM-YYYY HH:MM:SS.CCCC<br />
<br />
and press <RETURN> as close as possible to the entered time (down to the second). Note The major time entered should match the base time of the GTS. That is, if the GTS is UTC based, then a UTC major time should be loaded. Conversely, if the GTS is Local based, then the major time entered should be local. If the overall timesync function is not turned off, the operator interface automatically assumes Stagelink Time Master duties as follows: •<br />
<br />
After the next pulse input if the GTS is a pulse<br />
<br />
•<br />
<br />
After the next timecode frame if the GTS is a timecode<br />
<br />
•<br />
<br />
Immediately if the timesync mode is set to FLYWHEEL.<br />
<br />
•<br />
<br />
If "dd-mmm-yyyy hh:mm:ss.cccc" is omitted from the command line, TIMEUTIL prompts for this.<br />
<br />
Diagnostics and Troubleshooting This chapter covers some of the Turbine Control Time Synchronization’s built-in diagnostics and troubleshooting features. TIMEUTIL and the trace buffers are discussed here.<br />
<br />
Obtaining General Information About the Turbine Control Timesync Function The information available about Turbine Control Timesync is formatted such that it may exceed 25 lines of output. For this reason, set the screen to 50 line mode by entering: C:\> V50<br />
<br />
or redirect the output to a file. To obtain timesync status information, enter one of the following: C:\> TIMEUTIL STATUS C:\> TIMEUTIL STATUS >FILENAME.OUT<br />
<br />
The information returned by TIMEUTIL STATUS varies slightly depending on whether the GTS is a timecode signal, or pulse input.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 289<br />
<br />
Below is a sample output from TIMEUTIL STATUS for an IRIG-B GTS. This example was done on May 23, 1997, the 143rd day of the year. -------------------------------------------------------------------<I+> TIMESYNC STATUS Overall TIMESYNC Function: ENABLED TIMESYNC Controller: bc620AT TIMESYNC Mode: IRIG-B (Modulated) Status: TRACKING Global Time Acquired: YES Year: 1997 Days: 143 Pulse Correction in Use: N/A Major Time Load Flag: LOCAL CMOS Global Time Source: UTC Mark V Panel Time: LOCAL Mark V LM Panel Time: UTC <I> / <G> CPU Time: LOCAL Network Address Status Selected 1 0x1F 0x1903 x 2 0x20 0x1903 3 0x22 0x1903<br />
<br />
Local Windows NT Timeset: ENABLED<br />
<br />
Network #1, Local ARCNET address: 0x1F ----------------------------------------------------------------------------------------------------Items to Note in the Information Shown Above:<br />
<br />
290 • Chapter 8 Time Sync<br />
<br />
•<br />
<br />
The GTS is IRIG-B, and current status is TRACKING (the GTS is present). Otherwise, current status would be FLYWHEELING rather than TRACKING.<br />
<br />
•<br />
<br />
If Global Time Acquired was NO, then this operator interface is not going to attempt to pass time to other nodes on the Stagelink. NO, implies that the IRIGB timecode signal has never been detected by the Time Processing Board; or if the GTS is a pulse input, that no pulses have been received.<br />
<br />
•<br />
<br />
If Year is 0, then Major Time elements have not been loaded; this operator interface is not going to attempt to send time to other nodes on the Stagelink. The same is true if Days (the current day-of-year) is 0.<br />
<br />
•<br />
<br />
If the GTS is a pulse input (1 PPM or 1 PPH), the current pulse correction in use is displayed. This is less than or equal to ±30 seconds for 1 PPM, or ±30 minutes for 1 PPH. It shows N/A for timecode GTSs, 1 PPS, or FLYWHEEL modes. The Time Processing Board tracks 1 PPS inputs directly.<br />
<br />
•<br />
<br />
The next five lines of the output reflect information in F:\TIMESYNC.DAT.<br />
<br />
•<br />
<br />
At the bottom of the display is a list of all available Stagelink Time Masters (on this operator interface Stagelink), their addresses, their status, and which is the selected Stagelink Timemaster used by all nodes on this Stagelink.<br />
<br />
GEH-6126<br />
<br />
Note In a normal, functioning system, all status digits displayed for each available Stagelink Timemaster should be identical. If not, then verify that F:\TIMESYNC.DAT in each operator interface has the same information for the following parameters: TIME_SOURCE [LOCAL | UTC] MARKV_TIME<br />
<br />
[LOCAL | UTC]<br />
<br />
I_TIME<br />
<br />
[LOCAL | UTC]<br />
<br />
The status is displayed in hexadecimal. Bit 0 is considered the least significant (rightmost) bit. The current definition for each bit is shown below: Bit 0:<br />
<br />
1 ==> Stagelink Timemaster is tracking the GTS.<br />
<br />
Bit 0:<br />
<br />
0 ==> Stagelink Timemaster is flywheeling.<br />
<br />
Bit 1:<br />
<br />
Reserved. Normally has a value of 1.<br />
<br />
Bits 2-7: Reserved. Normally has a value of 0.<br />
<br />
Bit 8:<br />
<br />
1 ==> GTS is UTC based<br />
<br />
Bit 8:<br />
<br />
0 ==> GTS is LOCAL.<br />
<br />
Bit 9:<br />
<br />
1 ==> <I> ( IDP ) / <G> ( GDP ) time is UTC based.<br />
<br />
Bit 9:<br />
<br />
0 ==> <I> ( IDP ) / <G> ( GDP ) time is LOCAL.<br />
<br />
Bit 10: 1 ==> Mark V’s time is UTC based. Bit 10: 0 ==> Mark V’s time is LOCAL.<br />
<br />
Bits 11-12:<br />
<br />
Reserved. Normally has a value of 1.<br />
<br />
Bits 13-15:<br />
<br />
Reserved. Normally has a value of 0.<br />
<br />
Reserved bit definitions are subject to change.<br />
<br />
Other Timesync Diagnostic Capabilities Each operator interface with a Time Processing Board installed, maintains a trace buffer in memory. This trace buffer contains recordings of timesync protocol messages transmitted or received from the Stagelink. The information in these trace buffers can show the current time error in each time slave.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 291<br />
<br />
Decoding the trace buffer requires the following: Get a copy of the trace buffer into a binary file by entering at the Command prompt: C:\> GBL2FILE timesync_trace TIMESYNC.OUT<br />
<br />
The timesync_trace parameter must be in lowercase letters. Now this information is in the file TIMESYNC.OUT. The timesync protocol traces for Message Type: 4 (Time Diagnostic) contain error corrections between the Stagelink Time Master and the time slave. Other message type dumps are used for development purposes only, and are not discussed here. A portion of a sample output from the timesync_trace buffer is shown below:<br />
<br />
000131CC, E1 --> 00 (OUT) Msg.Type: 1(Timesync Master ID)Sequence #32DD Highest Time Format: 4, Timesync Master Status: 1903 Packet recorded at: 22-MAY-1997 18:59:02.214 (NT Time) 000131CD, 59 --> E1 (IN) Msg. Type: 2 (Request For Time Sequence #B560 Raw Time: 01 42 18 59 12 52 39 69 Time Format: 3, Timeboard Time: 142 18:59:12.523969 Packet recorded at: 22-MAY-1997 18:59:12.379 (NT Time) 000131CE, E1 --> 59 (OUT) Msg. Type: 3 (Time Response) Sequence #B560 Time Format: 3, Local Correction: -0240, Response Status: 0000 Raw Time: 80 97 84 33 C1 FE 07 00 Time Returned: 22-MAY-1997 18:59:12.523969 Packet recorded at: 22-MAY-1997 18:59:12.389 (NT Time) 000131CF, 59 --> E1 (IN) Msg. Type: 4 (Time Diagnostic) Sequence #B560 Raw Time: 00 00 00 00 85 09 00 00 Time Format: 3, Delta-Time: -0000 00:00:00.000437 Packet recorded at: 22-MAY-1997 18:59:12.389 (NT Time) 000131D0, E1 --> 00 (OUT) Msg.Type:1 (Timesync Master ID)Sequence #32DE Highest Time Format: 4, Timesync Master Status: 1903 Packet recorded at: 22-MAY-1997 18:59:22.223 (NT Time) 000131D1,<br />
<br />
Doing LOCAL TIMESET Function. Old Time: 22-MAY-1997 18:59:22.223 New Time: 22-MAY-1997 18:59:22.360<br />
<br />
292 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
000131D2, 59 --> E1 (IN) Msg. Type: 2 (Request For Time)Sequence #B561 Raw Time: 01 42 18 59 32 52 15 32 Time Format: 3, Timeboard Time: 142 18:59:32.521532 Packet recorded at: 22-MAY-1997 18:59:32.514 (NT Time) 000131D3, E1 --> 59 (OUT) Msg. Type: 3 (Time Response) Sequence #B561 Time Format: 3, Local Correction: -0240, Response Status: 0000 Raw Time: 94 97 84 33 3C F5 07 00 Time Returned: 22-MAY-1997 18:59:32.521532 Packet recorded at: 22-MAY-1997 18:59:32.514 (NT Time) 000131D4, 59 --> E1 (IN) Msg. Type: 4 (Time Diagnostic)Sequence #B561 Raw Time: 00 00 00 00 80 09 00 00 Time Format: 3, Delta-Time: -0000 00:00:00.000432 Packet recorded at: 22-MAY-1997 18:59:32.514 (NT Time) 000131D5, E1 --> 00 (OUT) Msg.Type:1 (Timesync Master ID)Sequence #32DF Highest Time Format: 4, Timesync Master Status: 1903 Packet recorded at: 22-MAY-1997 18:59:42.368 (NT Time) 000131D6, 59 --> E1 (IN) Msg. Type: 2 (Request For Time)Sequence #B562 Raw Time: 01 42 18 59 52 51 90 87 Time Format: 3, Timeboard Time: 142 18:59:52.519087 Packet recorded at: 22-MAY-1997 18:59:52.513 (NT Time) 000131D7, E1 --> 59 (OUT) Msg. Type: 3 (Time Response) Sequence #B562 Time Format: 3, Local Correction: -0240, Response Status: 0000 Raw Time: A8 97 84 33 AF EB 07 00 Time Returned: 22-MAY-1997 18:59:52.519087 Packet recorded at: 22-MAY-1997 18:59:52.513 (NT Time) 000131D8, 59 --> E1 (IN) Msg. Type: 4 (Time Diagnostic) Sequence #B562 Raw Time: 00 00 00 00 85 09 00 00 Time Format: 3, Delta-Time: -0000 00:00:00.000437 Packet recorded at: 22-MAY-1997 18:59:52.513 (NT Time)<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 293<br />
<br />
Sample Timesync Configurations This chapter shows three examples of possible Turbine Control Time Synchronization setups.<br />
<br />
Example 1 Using a Single Operator Interface as the Global Time Source This example uses a single operator interface as the GTS for the entire plant, using the low-drift capabilities of the Time Processing Board. The figure below shows a typical layout. Follow the steps below for setup: If multiple operator interfaces exist, install the Time Processing Board into the operator interface containing the lowest Stagelink address. This interface is referred to as the Primary Operator Interface in this example. If redundant Time Processing Boards exist, install the board(s) in the operator interface(s) with a higher Stagelink address(es) than the Primary Operator Interface described in step 1. These operator interfaces are referred to as Secondary Operator Interfaces in this example. Connect RG-58 cable from the TIMECODE OUTPUT BNC connector of the Primary Operator Interface to the TIMECODE INPUT BNC connectors on each Secondary Operator Interface. Use T-connectors to parallel the signal from computer to computer. In addition, parallel this cable to any DCS equipment which are to act as time slaves to the Primary Operator Interface. Optionally, the 1 PPS output can be connected to DCS equipment that are to act as time slaves to the Primary Operator Interface. The Primary Operator Interface may have F:\TIMESYNC.DAT configured with the following: TIMESYNC BC620AT MODE FLYWHEEL TIME_SOURCE LOCAL MARKV_TIME LOCAL I_TIME<br />
<br />
LOCAL<br />
<br />
TIME_LOAD<br />
<br />
LOCAL<br />
<br />
LOCAL_TIMESET ENABLED<br />
<br />
The F:\TIMESYNC.DAT files in each of the Secondary Operator Interfaces may be configured with the following: TIMESYNC BC620AT MODE IRIG-B TIME_SOURCE LOCAL MARKV_TIME LOCAL I_TIME<br />
<br />
LOCAL<br />
<br />
TIME_LOAD LOCAL LOCAL_TIMESET ENABLED<br />
<br />
294 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
If TIMESET capability is wanted in any operator interface without a Time Processing Board installed, configure F:\TIMESYNC.DAT in those computers with LOCAL_TIMESET ENABLED. (Other parameters are not required.) STAGELINK (ARCNET) (RG-62 COAX CABLE) TIMECODE OUT BNC PRIMARY OP INTERFACE<br />
<br />
TURBINE CON #1<br />
<br />
1PPS OUT BNC<br />
<br />
*<br />
<br />
RG-58 COAX CABLE<br />
<br />
TURBINE CON #2<br />
<br />
1 PPS TO DCS EQUIPMENT<br />
<br />
*<br />
<br />
TIMECODE IN BNC<br />
<br />
*<br />
<br />
SECONDARY OP INTERFACE TURBINE CON #3<br />
<br />
TIMECODE IN BNC<br />
<br />
*<br />
<br />
SECONDARY OP INTERFACE<br />
<br />
* Optional TERMINATION RESISTOR<br />
<br />
IRIG-B TIMECODE TO DCS EQUIPMENT<br />
<br />
TERMINATION RESISTOR<br />
<br />
Typical Layout for FLYWHEELING Timesync Mode<br />
<br />
Example 2 Using IRIG-B Timecode as the GTS with Multiple Operator Interface Stagelink Timemasters and Multiple Stagelinks This example uses a single box as the GTS for the entire plant, possibly a satellite receiver that generates an IRIG-B timecode signal. The figure below shows a typical layout. Note For redundancy requirements, no more than two-operator interface computers per Stagelink need to have Time Processing Boards installed.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 295<br />
<br />
Follow the steps below for setup: Install a Time Processing Board in each operator interface to be used as an available Stagelink Time Master. Connect RG-58 cable from the source of the IRIG-B timecode signal to each Time Processing Board, using the TIMECODE INPUT BNC connector. Use T-connectors to parallel the signal to each board. Continue the RG-58 cabling to any other piece of equipment in the plant that is to act as a time slave. The following is a typical F:\TIMESYNC.DAT configuration for each of the operator interfaces that have Time Processing Boards installed: TIMESYNC BC620AT MODE IRIG-B TIME_SOURCE LOCAL MARKV_TIME LOCAL I_TIME<br />
<br />
LOCAL<br />
<br />
TIME_LOAD LOCAL LOCAL_TIMESET ENABLED<br />
<br />
Note If the timebase of the IRIG-B timecode signal is UTC, change the TIME_SOURCE LOCAL line above to TIME_SOURCE UTC. If TIMESET capability is wanted in any operator interface without a Time Processing Board installed, configure F:\TIMESYNC.DAT in those computers with LOCAL_TIMESET ENABLED. (Other parameters are not required.)<br />
<br />
296 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
IRIG-B TIMECODE GNAL FROM SATELLITE RECEIVER OR OTHER DEVICE<br />
<br />
STAGELINK (ARCNET) TIMECODE IN BNC<br />
<br />
TERMINATION RESISTOR<br />
<br />
(RG-62 COAX CABLE) OP INTERFACE #1<br />
<br />
TURBINE CON #1<br />
<br />
TIMECODE IN BNC<br />
<br />
OP INTERFACE #2<br />
<br />
TERMINATION RESISTOR<br />
<br />
TURBINE CON #2<br />
<br />
RG-58 COAX CABLE TIMECODE IN BNC<br />
<br />
OP INTERFACE #3<br />
<br />
TERMINATION RESISTOR TURBINE CON #3<br />
<br />
TIMECODE IN BNC<br />
<br />
OP INTERFACE #4<br />
<br />
IRIG-B TIMECODE TO OTHER PLANT EQUIPMENT<br />
<br />
TERMINATION RESISTOR<br />
<br />
STAGELINK (ARCNET) (RG-62 COAX CABLE)<br />
<br />
Typical Layout for External IRIG-B GTS, using redundancy and multiple Stagelink Networks<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 297<br />
<br />
Example 3 Using Pulse Inputs as the GTS with Multiple Operator Interface Stagelink Timemasters and Multiple Stagelinks This example uses a single box as the GTS for the entire plant, possibly a satellite receiver that generates one pulse per minute (or hour) as a time reference. The figure below shows a typical layout. Note For redundancy requirements, no more than two-operator interface computers per Stagelink need to have Time Processing Boards installed. Follow the steps below for setup: Install a Time Processing Board in each operator interface to be used as an available Stagelink Time Master. Connect RG-58 cable from the source of the pulse input signals to each Time Processing Board, using the EVENT INPUT BNC connector. Use T-connectors to parallel the signal to each board. Continue the RG-58 cabling to any other piece of equipment in the plant that is to act as a time slave. The following is a typical F:\TIMESYNC.DAT configuration for each of the operator interfaces that have Time Processing Boards installed: TIMESYNC BC620AT MODE 1PPM TIME_SOURCE LOCAL MARKV_TIME LOCAL I_TIME<br />
<br />
LOCAL<br />
<br />
TIME_LOAD LOCAL LOCAL_TIMESET ENABLED<br />
<br />
Note If the pulse rate is 1 pulse per hour, change 1 PPM to 1 PPH. If TIMESET capability is wanted in any operator interface without a Time Processing Board installed, configure F:\TIMESYNC.DAT in those computers with LOCALTIMESET ENABLED. (Other parameters are not required.) Notes for interfacing pulse input references: The bc620AT has internal 4.7 kΩ pullup resistors between a +5 V power source and both the 1 PPS Input and Event Input signals. Therefore any interface to these inputs must be able to draw at least 1 mA of current per bc620AT board. Pulse inputs are positive edge on time. The interface must be at logic 0 except when the reference pulse is active. Pulse input references must be stable, therefore only use stable pulse references. For example, 1 PPM references pulses should be as close to 60.00000 seconds apart as possible. Otherwise, Turbine Control timesync loses accuracy. The use of electro-mechanical relays for pulse inputs is not recommended. The use of open collector circuits or solid state relays is acceptable. GE does not recommend using software operating systems in the DCS to generate the reference pulses.<br />
<br />
298 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
Pulse input references are at logic 0 most of the time. Therefore, the Time Processing Board’s BNC connector records a false pulse input when the reference cable is disconnected from the Time Processing Board. The board senses a positive edge caused by the internal 4.7 kΩ pull-up resistor. The card then sends invalid time to the Turbine Control panels until the next true reference pulse is signaled. GE recommends restarting the operator interface software after the reference cables are reconnected. 1 PULSE PER MINUTE OR 1 PULSE PER HOUR SATELLITE RECEIVER OR OTHER DEVICE<br />
<br />
TERMINATION RESISTOR<br />
<br />
STAGELINK (RG-62 COAX CABLE) EVENT IN BNC<br />
<br />
TURBINE CON<br />
<br />
OP INTERFACE #1<br />
<br />
#1<br />
<br />
EVENT IN BNC<br />
<br />
OP INTERFACE #2<br />
<br />
TERMINATION RESISTOR RG-58 COAX CABLE<br />
<br />
TURBINE CON #2<br />
<br />
TERMINATION RESISTOR<br />
<br />
EVENT IN BNC<br />
<br />
OP INTERFACE #3<br />
<br />
TURBINE CON #3<br />
<br />
EVENT IN BNC<br />
<br />
OP INTERFACE #4<br />
<br />
TERMINATION RESISTOR<br />
<br />
STAGELINK (ARCNET) PULSE CODES TO OTHER PLANT EQUIPMENT<br />
<br />
(RG-62 COAX CABLE)<br />
<br />
Typical Layout for External 1 PPM or 1 PPH GTS, with redundant Stagelink Timemasters and multiple Stagelink Networks<br />
<br />
Testing the bc620AT/bc627AT Time and Frequency Board The bc620AT TFP (Time Frequency Processor) comes with a floppy disk labeled, "Demonstration Diskette." This diskette contains a demonstration program called BC620.EXE that can be used to verify that the bc620AT card is functioning correctly. This program requires that the system is running under DOS. A similar program supplied as part of the TCI product software is called G:\EXEC\TEST_620.EXE. This program provides bc620AT/bc627AT testing capability while running under the Windows NT operating system. This program can be used to verify that the GTS interface (pulse or timecode) is present and operational. This section describes how to use this program.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 299<br />
<br />
! Warning<br />
<br />
This program can interfere with the normal timesync operation of the operator interface. This is especially true for pulse input GTSs. This program should only be run when the TCI system service is not running. The ARCNET® device driver must be running in order to use this test program. Restart the TCI system service after running this test program.<br />
<br />
To run the test program: Open a Command Console window Enter TEST_620 A menu of available commands is displayed as shown in the figure below. Also listed below is a number of different tests that can be run: To test the bc620 times registers and/or to test timecode GTSs, go to "Test #1" on page 300. To test the bc620 event recording registers and/or to test 1PPS, 1PPM or 1PPH GTSs, go to "Test #2" on page 301. To test 1PPS GTSs and/or the bc620 time registers go to "Test #3" on page 303. To test the bc620AT FIFO command/response registers go to " Test #4 and #5 on page 304. When tests are completed, select option "x" at the program menu. Restart the TCI System Service. ----------------------------------------------------------------------------------------------------bc620AT Time & Frequency Processor Test Program (NT Version) 1. Read Time 2. Read Event Time (Pos. Edge) I. Read Event Time (Neg. Edge) 3. Request bc620AT Programmable Data 4. Request Model Number & Firmware Version 5. Request D/A Value 6. Request RTC Time 7. Select Operational Mode 8. Select Time Code Format and Type 9. Program Control Register (CRO) A. Program Heartbeats (82C54) B. Preset D/A C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset Enter Selection: x. Exit ------------------------------------------------------------------------------------Main bc620AT/bc627AT Test Program Menu<br />
<br />
Test #1 This test will validate the existence of a timecode GTS (if used) and the time recording registers of the bc620AT. To begin the test, select "1" at the program menu. Hit any key to terminate the test. This test will read the bc620 time registers as rapidly as possible. All of the bc620 time registers are BCD registers. If any digit displays as ":", ";", "<", "=", ">", or "?", then the bc620 time registers are defective or the I/O Port Base Address in the Windows NT registry is wrong. If a timecode GTS is in use and is operational, then each line should show "Tracking" status. Otherwise, each line will show "Flywheeling" status. 300 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
A sample output is shown below in the example below: ----------------------------------------------------------------TIME: 143 14:19:48.859419 Status: 0 (TRACKING) TIME: 143 14:19:48.859710 Status: 0 (TRACKING) TIME: 143 14:19:48.859980 Status: 0 (TRACKING) TIME: 143 14:19:48.860256 Status: 0 (TRACKING) TIME: 143 14:19:48.860524 Status: 0 (TRACKING) TIME: 143 14:19:48.860794 Status: 0 (TRACKING) TIME: 143 14:19:48.861067 Status: 0 (TRACKING) TIME: 143 14:19:48.861336 Status: 0 (TRACKING) TIME: 143 14:19:48.861604 Status: 0 (TRACKING) TIME: 143 14:19:48.861878 Status: 0 (TRACKING) TIME: 143 14:19:48.862147 Status: 0 (TRACKING) TIME: 143 14:19:48.862423 Status: 0 (TRACKING) TIME: 143 14:19:48.862698 Status: 0 (TRACKING) TIME: 143 14:19:48.862967 Status: 0 (TRACKING) TIME: 143 14:19:48.863237 Status: 0 (TRACKING) TIME: 143 14:19:48.863511 Status: 0 (TRACKING) TIME: 143 14:19:48.863779 Status: 0 (TRACKING) TIME: 143 14:19:48.864120 Status: 0 (TRACKING) TIME: 143 14:19:48.864396 Status: 0 (TRACKING) TIME: 143 14:19:48.864665 Status: 0 (TRACKING) TIME: 143 14:19:48.864934 Status: 0 (TRACKING) TIME: 143 14:19:48.865207 Status: 0 (TRACKING) TIME: 143 14:19:48.865476 Status: 0 (TRACKING) TIME: 143 14:19:48.865744 Status: 0 (TRACKING) TIME: 143 14:19:48.866017 Status: 0 (TRACKING) TIME: 143 14:19:48.866287 Status: 0 (TRACKING) ------------------------------------------------------------------<br />
<br />
Sample Read Time Register Output<br />
<br />
Test #2 This test is used to validate the bc620’s event recorder registers, and can be used to validate pulse input GTSs. This test consists of several steps: Program Control Register 0 to enable event recording while disabling event lockout. Do this by selecting option "9" at the program menu, and then enter "08" for the value of CR0. See the figure below for an example. Select option "2" at the program menu. This will start event register recording as shown in the figure below. (This example was created by connecting the "1PPS Output" BNC to the "Event Input" BNC.) To merely test the bc620AT’s event recording capability, place a short circuit on the "Event Input" BNC using a paper clip or jumper wire. Every time the short circuit is removed, a new event time should be shown. All of the bc620 event registers are BCD registers. Only digits 0-9 should be in these registers. If any digit displays as ":", ";","<", "=", ">" or "?", then the bc620 event registers are defective or the I/O Port Base Address in the Windows NT registry is wrong. If a timecode GTS is attached to the "Timecode In" BNC, each line should show "Tracking" status. Otherwise, "Flywheeling" status will be shown.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 301<br />
<br />
To test 1PPS, 1PPM or 1PPH pulse input GTSs, attach the signal to the "Event Input" BNC. Note For 1PPS, this is a temporary connection. 1PPS GTSs are normally connected to the "1PPS Input" BNC. Each time the pulse input changes from logic "0" to logic "1" a new event time should be shown. All of the bc620 event registers are BCD registers. Only digits 0-9 should be in these registers. If any digit displays as ":", ";","<", "=", ">" or "?", then the bc620 event registers are defective or the I/O Port Base Address in the Windows NT registry is wrong. If a timecode GTS is attached to the "Timecode In" BNC, each line should show "Tracking" status. Otherwise, "Flywheeling" status will be shown.<br />
<br />
302 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
----------------------------------------------------------------------3. Request bc620AT Programmable Data 4. Request Model Number & Firmware Version 5. Request D/A Value 6. Request RTC Time 7. Select Operational Mode 8. Select Time Code Format and Type 9. Program Control Register (CR0) A. Program Heartbeats (82C54) B. Preset D/A C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT Enter selection: 9 Current CR0 value: 0x00 Enter new value (hex): 0x08 New value of CR0 written. Press any key to continue: ----------------------------------------------------------------------Programming Control Register 0 -------------------------------------------------------------------C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT Enter selection: 2 Waiting for an event input pulse...hit any key to return Event Time: 143 14:20:52.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:53.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:54.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:55.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:56.0000001 Status: 2 (TRACKING) Event Time: 143 14:20:57.0000001 Status: 0 (TRACKING) Event Time: 143 14:20:58.0000001 Status: 0 (TRACKING) Event Time: 143 14:20:59.0000001 Status: 2 (TRACKING) ------------------------------------------------------------------<br />
<br />
Sample Read Event Register Output<br />
<br />
Test #3 This test will validate the existence of a 1PPS GTS and the time recording registers of the bc620AT. Follow these steps to setup the test: First, select "7" at the program’s menu to select the operational mode of the bc620AT. Select "2" to choose 1PPS synchronization. Press any key to return to the program’s menu. See the sample below for an example of selecting the operational mode. Next, to begin the test, select "1" at the program’s menu. Hit any key to terminate the test. The program will read the bc620 time registers as rapidly as possible. All of the bc620 time registers are BCD registers. Only digits 0-9 should be in these registers. If any digit displays as ":", ";", "<", "=", ">" or "?", then the bc620 time registers are defective or the I/O Port Base Address in the Windows NT registry is wrong. If the 1PPS GTS is connected to the "1PPS Input" BNC and is operational, then each line should show "Tracking" status. Otherwise, each line will show "Flywheeling" status.<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 303<br />
<br />
A sample output is shown in the example below: -----------------------------------------------------------------B. Preset D/A C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT Enter selection: 7 Possible bc620AT Operating Modes: 0 - Time Code Mode (default bc620AT) 1 - Free Running Mode 2 - Synchronize of external 1PPS input 3 - Real Time Clock Mode 4 - GPS - Acutime Mode (default bc627AT) Current bc620AT Operating Mode: 0 - Time Code Decoder Mode Enter new operating mode (0-4): 2 REQUEST SENT TO bc620AT:<br />
<br />
01 41 32 17<br />
<br />
Press any key to continue: ----------------------------------------------------------------------<br />
<br />
Programming bc620AT to use 1PPS GTS<br />
<br />
Test #4 and Test #5 Tests #4 and #5 will validate the bc620AT’s FIFO command and response registers. For test #4, enter "3" at the program’s menu prompt. An output similar to the example below should be displayed. Note If Test #3 above was done, the output will be slightly different. To run test #5, enter "4" at the program’s menu prompt. An output similar to the example below should be displayed. If either test fails, the bc620AT is probably defective, or the I/O Port Base Address in the Windows NT Registry is wrong.<br />
<br />
304 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
------------------------------------------------------------G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT Enter selection: 3 REQUEST: REPLY: REPLY:<br />
<br />
01 4F 33 17 01 6F 33 30 42 4D 42 30 31 2B 30 30 2B 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 17<br />
<br />
bc620AT Programmable Data Mode: : 0 - Time Code Decoder Mode Time Code Format : B - IRIG B Time Code Type : M - Modulated Time Code Generator : B - IRIG B Path Byte : 0x01 Local Time Offset : +00 Propagation Delay Offset : +0.0000000 seconds Heartbeat (82C54) : Mode = 0 : Cnt1 = 0000 : Cnt2 = 0000 Press any key to continue: -----------------------------------------------------------------Sample Request bc620AT Programmable Data Output -------------------------------------------------------------5. Request D/A Value 6. Request RTC Time 7. Select Operational Mode 8. Select Time Code Format and Type 9. Program Control Register (CR0) A. Program Heartbeats (82C54) B. Preset D/A C. Send Path Byte D. Send Command ** bc627AT COMMANDS ONLY ** E. Load Major Time Registers J. Request Year F. Load RTC Time Registers K. Request GPS Leap Seconds G. Load Strobe Time L. Load GPS Leap Seconds H. Program Propagation Delay Offset M. Load GPS Time Offset x. EXIT Enter selection: REQUEST: REPLY: REPLY:<br />
<br />
4<br />
<br />
01 4F 34 17 01 6F 34 62 63 36 32 30 41 54 20 39 35 30 31 31 35 35 17<br />
<br />
Model: bc620AT 9501155 Press any key to continue: ------------------------------------------------------------------<br />
<br />
Sample Request Model Number & Firmware Version Output<br />
<br />
GEH-6126<br />
<br />
Chapter 8 Time Sync • 305<br />
<br />
Notes<br />
<br />
306 • Chapter 8 Time Sync<br />
<br />
GEH-6126<br />
<br />
Glossary of Terms 2137 A 1kHz modulated signal. Frame rate is 1 code per second. This is a time-ofday reference. Resolution: 1 ms. ARCNET A LAN communications protocol developed by Datapoint Corporation, used to link various controllers. Allows a maximum of 255 drops with transmission at 2.5 Mbits/s. BCD Binary Coded Decimal. CF Control Functions. Daylight Savings Time (DST) Time change observed in parts of the world to extend the number of daylight hours. DCS Distributed Control Systems EDT Eastern Daylight Time. Reference to Daylight Savings Time in the Eastern United States. Epoch A reference event. In timing applications, epoch often refers to a one pulse per second event. Flywheel In the timekeeping vernacular to ’flywheel’ means to maintain time or frequency or both after the input reference is removed or lost. GDP Gateway Data Processor, also referred to as <G>. GSM Gateway computer interface for the Mark V Turbine Control System using Ethernet in place of the Stagelink. Please see IDP. GMT Greenwich Mean Time.<br />
<br />
GEH-6126<br />
<br />
Glossary of Terms • 307<br />
<br />
GPS Global Positioning System. The fleet of GPS vehicles is used worldwide for navigational purposes by aircraft and ships for position and velocity measurements. In addition, time-of-year information can be obtained by a GPS receiver. See GPS Time. GPS Time Time reference available from GPS space vehicles which includes the accumulation of leap seconds. Leap seconds are typically added or subtracted on June 30th and December 31st of each year as needed to correct UTC. GSM<br />
<br />
GE Drive Systems Standard Message<br />
<br />
GTS Global Time Source. This is the source of time reference used for synchronization of time for all Mark Vs and DCS subsystems. I/O<br />
<br />
Input/output. Interfaces that allow the flow of data into and out of a device.<br />
<br />
IDP Interface Data Processor, also referred to as <I>. One of the Mark V Turbine Control System’s primary operator interface. Consists of a computer interface with GE’s version of ARCNET called the Stagelink. IRIG - Inter-Range Instrumentation Group. This group defines a family of timecode signals (both modulated and dc level shifted) at various frequencies and frame rates. The IRIG timecodes are time-of-year references. IRIG-A A 10 kHz modulated or dc level shifted signal. Frame rate is 10 codes per second. Resolution: 0.1 ms. IRIG-B A 1kHz modulated or dc level shifted signal. Frame rate is 1 code per second. Resolution: 1 ms. IRQ Interrupt Request Local Time A time reference commonly used in the geographic locale of the equipment. Local time is subject to jerks in time caused by jumping the time reference forward in the Spring for Daylight Savings Time, and jumping backward in the Fall to return to Standard Time (in the Northern hemisphere). Major Time Units of time equal to or larger than seconds. Years, days, hours, minutes and seconds are usually implied.<br />
<br />
308 • Glossary of Terms<br />
<br />
GEH-6126<br />
<br />
NASA-36 A 1KHz modulated or dc level shifted signal. Frame rate is 1 code per second. This is a time-of-year reference. Resolution: 1 ms. PPH Pulse Per Hour. A GTS using periodic pulses to mark an epoch as a time reference. A typical rate is 1 Pulse Per Hour. PPM Pulse Per Minute. A GTS using periodic pulses to mark an epoch as a time reference. A typical rate is 1 Pulse Per Minute. PPS Pulse Per Second. A GTS using periodic pulses to mark an epoch as a time reference. A typical rate is 1 Pulse Per Second. Receptacle A type of electrical fitting designed to connect with a plug, or prong, connector. SBS Straight Binary Seconds. Slave Device that follows commands from a remote master control device. Stagelink GE’s version of ARCNET used in Turbine applications. See ARCNET Timeset The act of setting a clock to a time reference. This action does not imply any particular accuracy. Timesync The act of locking a clock to a time reference. This action implies a continuous operation used to minimize loss of accuracy of the clock being synchronized referenced to the global time source. UTC Universal Time Coordinated. This is the time reference used at the zero meridian. Also known as GMT. XR3 A 250 Hz modulated signal. Frame rate is 1 code per second. This is a time-ofday reference. Resolution: 4 ms.<br />
<br />
GEH-6126<br />
<br />
Glossary of Terms • 309<br />
<br />
Notes<br />
<br />
310 • Glossary of Terms<br />
<br />
GEH-6126<br />
<br />
Appendix A IRIG Nomenclature IRIG Time Codes have alphabetical as well as numerical designations. The nomenclature is defined as follows:<br />
<br />
Rate Designation A:<br />
<br />
1000<br />
<br />
pps<br />
<br />
B:<br />
<br />
100<br />
<br />
pps<br />
<br />
D:<br />
<br />
1<br />
<br />
ppm<br />
<br />
E:<br />
<br />
10<br />
<br />
pps<br />
<br />
G:<br />
<br />
10000<br />
<br />
pps<br />
<br />
H:<br />
<br />
1<br />
<br />
pps<br />
<br />
Form Designation 0:<br />
<br />
Pulse, width-coded<br />
<br />
1:<br />
<br />
Sine wave, amplitude-modulated<br />
<br />
Carrier/Resolution 0:<br />
<br />
No carrier/index count interval<br />
<br />
1:<br />
<br />
100<br />
<br />
Hz/10 ms<br />
<br />
2:<br />
<br />
1000<br />
<br />
Hz/1 ms<br />
<br />
3:<br />
<br />
10000<br />
<br />
Hz/0.1 ms<br />
<br />
4:<br />
<br />
100000 Hz/0.01 ms<br />
<br />
Coded Expressions<br />
<br />
GEH-6126<br />
<br />
0:<br />
<br />
BCD, CF, SBS<br />
<br />
1:<br />
<br />
BCD, CF<br />
<br />
2:<br />
<br />
BCD<br />
<br />
3:<br />
<br />
BCD, SBS<br />
<br />
Appendix A • 311<br />
<br />
IRIG Codes The following is a list of recognized standard IRIG codes: * Format A:<br />
<br />
A000,<br />
<br />
A003,<br />
<br />
A130,<br />
<br />
A133<br />
<br />
* Format B:<br />
<br />
B000,<br />
<br />
B003,<br />
<br />
B120,<br />
<br />
B123<br />
<br />
Format D:<br />
<br />
D001,<br />
<br />
D002,<br />
<br />
D111,<br />
<br />
D112,<br />
<br />
D121,<br />
<br />
D122<br />
<br />
Format E:<br />
<br />
E001,<br />
<br />
E002,<br />
<br />
E111,<br />
<br />
E112,<br />
<br />
E121,<br />
<br />
E122<br />
<br />
Format G:<br />
<br />
G001,<br />
<br />
G002,<br />
<br />
G141,<br />
<br />
G142<br />
<br />
Format H:<br />
<br />
H001,<br />
<br />
H002,<br />
<br />
H111,<br />
<br />
H112,<br />
<br />
H121,<br />
<br />
H122<br />
<br />
* Supported by Turbine Control Time Synchronization<br />
<br />
312 • Appendix A<br />
<br />
GEH-6126<br />
<br />
*HQHUDO(OHFWULF&RPSDQ\ 5RDQRNH%OYG 6DOHP9$86$<br />
<br />
*(,QGXVWULDO &RQWURO6\VWHPV<br />
<br />
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div class="modal fade" id="report" tabindex="-1" role="dialog" aria-hidden="true">
<div class="modal-dialog">
<div class="modal-content">
<form role="form" method="post" action="https://idoc.tips/report/geh6126-hmi-application-manual-pdf-free" style="border: none;">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
<h4 class="modal-title">Report "Geh6126 Hmi Application Manual"</h4>
</div>
<div class="modal-body">
<div class="form-group">
<label>Your name</label>
<input type="text" name="name" required="required" class="form-control" />
</div>
<div class="form-group">
<label>Email</label>
<input type="email" name="email" required="required" class="form-control" />
</div>
<div class="form-group">
<label>Reason</label>
<select name="reason" required="required" class="form-control">
<option value="">-Select Reason-</option>
<option value="pornographic" selected="selected">Pornographic</option>
<option value="defamatory">Defamatory</option>
<option value="illegal">Illegal/Unlawful</option>
<option value="spam">Spam</option>
<option value="others">Other Terms Of Service Violation</option>
<option value="copyright">File a copyright complaint</option>
</select>
</div>
<div class="form-group">
<label>Description</label>
<textarea name="description" required="required" rows="3" class="form-control" style="border: 1px solid #cccccc;"></textarea>
</div>
<div class="form-group">
<div style="display: inline-block;">
<div class="g-recaptcha" data-sitekey="6LcHT8sZAAAAAPKfs_PZGhwvz-OHbUMuekQzz5xK"></div>
</div>
</div>
<script src='https://www.google.com/recaptcha/api.js'></script>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
<button type="submit" class="btn btn-success">Send</button>
</div>
</form>
</div>
</div>
</div>
<script>
$(document).ready(function () {
var inner_height = $(window).innerHeight() - 250;
$('#pdfviewer').css({"height": inner_height + "px"});
});
</script>
<footer class="footer" style="margin-top: 60px;">
<div class="container-fluid">
Copyright © 2025 IDOC.TIPS. All rights reserved.
<div class="pull-right">
<span><a href="https://idoc.tips/about">About Us</a></span> |
<span><a href="https://idoc.tips/privacy">Privacy Policy</a></span> |
<span><a href="https://idoc.tips/term">Terms of Service</a></span> |
<span><a href="https://idoc.tips/copyright">Copyright</a></span> |
<span><a href="https://idoc.tips/contact">Contact Us</a></span> |
<span><a href="https://idoc.tips/cookie_policy">Cookie Policy</a></span>
</div>
</div>
</footer>
<!-- Modal -->
<div class="modal fade" id="login" tabindex="-1" role="dialog" aria-labelledby="myModalLabel">
<div class="modal-dialog" role="document">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-label="Close" on="tap:login.close"><span aria-hidden="true">×</span></button>
<h4 class="modal-title" id="add-note-label">Sign In</h4>
</div>
<div class="modal-body">
<form action="https://idoc.tips/login" method="post">
<div class="form-group">
<label class="sr-only" for="email">Email</label>
<input class="form-input form-control" type="text" name="email" id="email" value="" placeholder="Email" />
</div>
<div class="form-group">
<label class="sr-only" for="password">Password</label>
<input class="form-input form-control" type="password" name="password" id="password" value="" placeholder="Password" />
</div>
<div class="form-group">
<div class="checkbox">
<label class="form-checkbox">
<input type="checkbox" name="remember" value="1" />
<i class="form-icon"></i> Remember me
</label>
<label class="pull-right"><a href="https://idoc.tips/forgot">Forgot password?</a></label>
</div>
</div>
<button class="btn btn-primary btn-block" type="submit">Sign In</button>
</form>
</div>
</div>
</div>
</div>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-177830117-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-177830117-1');
</script>
<script src="https://idoc.tips/assets/js/jquery-ui.min.js"></script>
<link rel="stylesheet" href="https://idoc.tips/assets/css/jquery-ui.css">
<script>
$(function () {
$("#document_search").autocomplete({
source: function (request, response) {
$.ajax({
url: "https://idoc.tips/suggest",
dataType: "json",
data: {
term: request.term
},
success: function (data) {
response(data);
}
});
},
autoFill: true,
select: function (event, ui) {
$(this).val(ui.item.value);
$(this).parents("form").submit();
}
});
});
</script>
<!-- cookie policy -->
<div id="IDOCTIPS_cookie_box" style="z-index:99999; background: #97c479; width: 100%; position: fixed; padding: 5px 15px; text-align: center; left:0; bottom: 0;">
Our partners will collect data and use cookies for ad personalization and measurement. <a href="https://idoc.tips/cookie_policy" target="_blank">Learn how we and our ad partner Google, collect and use data</a>. <a href="#" class="btn btn-success" onclick="accept_IDOCTIPS_cookie_box();return false;">Agree & close</a>
</div>
<script>
function accept_IDOCTIPS_cookie_box() {
document.cookie = "IDOCTIPS_cookie_box_viewed=1;max-age=15768000;path=/";
hide_IDOCTIPS_cookie_box();
}
function hide_IDOCTIPS_cookie_box() {
var cb = document.getElementById('IDOCTIPS_cookie_box');
if (cb) {
cb.parentElement.removeChild(cb);
}
}
(function () {
var IDOCTIPS_cookie_box_viewed = (function (name) {
var matches = document.cookie.match(new RegExp("(?:^|; )" + name.replace(/([\.$?*|{}\(\)\[\]\\\/\+^])/g, '\\$1') + "=([^;]*)"));
return matches ? decodeURIComponent(matches[1]) : undefined;
})('IDOCTIPS_cookie_box_viewed');
if (IDOCTIPS_cookie_box_viewed) {
hide_IDOCTIPS_cookie_box();
}
})();
</script>
<!-- end cookie policy -->
</body>
</html>
