HMI for SPEEDTRONIC™Turbine Controls

Application Manual

GEH-6126

HMI for SPEEDTRONIC™Turbine Controls

Application ManualGEH-6126

Issue Date: 1999-01-25

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.

1999 General Electric Company, U.S.A.All rights reserved.

Printed in the United States of America.

GEH-6126 a

Safety Symbol Legend

Indicates a procedure or condition that, if notstrictly observed, could result in personal injury ordeath.

Indicates a procedure or condition that, if notstrictly observed, could result in damage to ordestruction of equipment.

Note Indicates an essential or important procedure, condition, orstatement.

b GEH-6126

!Warning

To prevent personal injury or equipment damagecaused by equipment malfunction, only adequatelytrained personnel should modify anyprogrammable machine.

!Caution

The example and setup screens in this manual donot reflect the actual application configurations. Besure to follow the correct setup procedures foryour application.

GEH-6126 i

ContentsChapter 1 Overview.....................................................................................................................................1

Introduction............................................................................................................................................................... 1Related Documents ................................................................................................................................................... 4

SPEEDTRONIC Mark V Turbine Control – GEH-5979...................................................................................... 4SPEEDTRONIC Mark V Turbine Control – GEH-5980...................................................................................... 4SPEEDTRONIC Mark V Turbine Control Application Manual Overview – GEH-6195 .................................... 5SPEEDTRONIC Turbine Control Panel Manual Overview – GEH-6354............................................................ 5CIMPLICITY Base System User's Manual – GFK-1180 ..................................................................................... 5Getting Assistance................................................................................................................................................. 5

Chapter 2 Start Up.......................................................................................................................................7Logging On ............................................................................................................................................................... 7Main Cimview........................................................................................................................................................... 7Alarm Displays ......................................................................................................................................................... 8Commands ................................................................................................................................................................ 8

Style Recommendations........................................................................................................................................ 8Advanced Topics ...................................................................................................................................................... 9

Trending................................................................................................................................................................ 9Point Control Panel ............................................................................................................................................... 9Demand Display.................................................................................................................................................. 10

Chapter 3 Theory of Applications ...............................................................................................................11Advanced Data Flow............................................................................................................................................... 11Directory Structure.................................................................................................................................................. 12

TCI Directories: .................................................................................................................................................. 12Drive F: Files ...................................................................................................................................................... 13Drive F: Sub-directories...................................................................................................................................... 14Drive G: Sub-directories ..................................................................................................................................... 14

Program Categories................................................................................................................................................. 15Displays............................................................................................................................................................... 16Control ................................................................................................................................................................ 16Configuration ...................................................................................................................................................... 16Remote Data and Control.................................................................................................................................... 16

Chapter 4 Display Applications ..................................................................................................................17Introduction............................................................................................................................................................. 17ARCWHO............................................................................................................................................................... 17

Purpose................................................................................................................................................................ 17Background ......................................................................................................................................................... 17Operation............................................................................................................................................................. 17

CARD_ID ............................................................................................................................................................... 18Purpose................................................................................................................................................................ 18Background ......................................................................................................................................................... 18

ii GEH-6126

Operation............................................................................................................................................................. 19Examples............................................................................................................................................................. 20

Mark V Example ............................................................................................................................................. 20Mark V LM Example ...................................................................................................................................... 21

CHECKCRC ........................................................................................................................................................... 22Purpose................................................................................................................................................................ 22Background ......................................................................................................................................................... 22Operation............................................................................................................................................................. 23Example .............................................................................................................................................................. 23

Diagnostic Counters Display................................................................................................................................... 24Purpose................................................................................................................................................................ 24File Type ............................................................................................................................................................. 24

Mark V LM ..................................................................................................................................................... 24Mark V ............................................................................................................................................................ 24

Using the Diagnostic Counters Display Program.................................................................................................... 25Executing Diagnostic Counters Display (DIAGC) ............................................................................................. 25

The Diagnostic Counters Display Window............................................................................................................. 26Tree View............................................................................................................................................................ 26Diagnostic Counter Data Window ...................................................................................................................... 27

Header ............................................................................................................................................................. 28Legend............................................................................................................................................................. 28Data Area ........................................................................................................................................................ 28

Selecting a Diagnostic Counters Display ............................................................................................................ 29Interpreting Data ................................................................................................................................................. 29

Information for Card Designers ...................................................................................................................... 29Dynamic Rung Display ........................................................................................................................................... 30

Purpose................................................................................................................................................................ 30File Structure....................................................................................................................................................... 30Dynamic Rung Display Screen Description........................................................................................................ 31

Rung Windows........................................................................................................................................................ 32Rung Window Header......................................................................................................................................... 33Header Timetag................................................................................................................................................... 33

Big Blocks and Comment Rungs .................................................................................................................... 33RLD and Primitive Rungs ............................................................................................................................... 33

Data Display........................................................................................................................................................ 33RLD Rungs ......................................................................................................................................................... 33

Contacts........................................................................................................................................................... 33Coils ................................................................................................................................................................ 34

Primitive Rungs................................................................................................................................................... 34Big Blocks........................................................................................................................................................... 34Comment Rungs.................................................................................................................................................. 35

Picture File Windows.............................................................................................................................................. 36Picture File Window Header ............................................................................................................................... 36Header Timetag................................................................................................................................................... 37

Static Display .................................................................................................................................................. 37Values Display ................................................................................................................................................ 37

Main Frame Window .............................................................................................................................................. 37Using The Dynamic Rung Display ......................................................................................................................... 38

Starting the Dynamic Rung Display.................................................................................................................... 38Selecting a Sequencing Display screen ............................................................................................................... 38Using the Find All function................................................................................................................................. 38Viewing Tabular Data ......................................................................................................................................... 39

Prevote Data Display............................................................................................................................................... 40Purpose................................................................................................................................................................ 40Menu Structure.................................................................................................................................................... 40

File .................................................................................................................................................................. 40

GEH-6126 iii

Edit........................................................................................................................... ....................................... 40View........................................................................................................................... ..................................... 40Help........................................................................................................................... ...................................... 40

Command Line Description ....................................................................................................... ......................... 41Header Timetag................................................................................................................. .................................. 41

Trip History Log ............................................................................................................... ...................................... 41Purpose........................................................................................................................ ........................................ 41File Type ...................................................................................................................... ....................................... 42

Viewing........................................................................................................................ ................................... 42Configuration .................................................................................................................. ................................ 42

Trip History Dialog Box Description............................................................................................ ...................... 44Trip History................................................................................................................... .................................. 44Saved Data ..................................................................................................................... ................................. 44New Data ....................................................................................................................... ................................. 44Data Retrieval ................................................................................................................. ................................ 45Viewing Results ................................................................................................................ .............................. 45

Executing the Trip History Program............................................................................................. ...................... 46Trip History Log List Viewer ................................................................................................... .............................. 47

Purpose........................................................................................................................ ........................................ 47File Type ...................................................................................................................... ....................................... 47Mark V Trip Log List Viewer Dialog Box......................................................................................... ................. 48

Data Retrieval ................................................................................................................. ................................ 48Viewing Results ................................................................................................................ .............................. 48Executing the Mark V Trip Log List Viewer ...................................................................................... ............ 48

VIEW2 .......................................................................................................................... .......................................... 49Purpose........................................................................................................................ ........................................ 49Background ..................................................................................................................... .................................... 49Operation...................................................................................................................... ....................................... 49Examples....................................................................................................................... ...................................... 50

Chapter 5 Control .......................................................................................................................................53Introduction............................................................................................................................................................. 53Logic Forcing Display............................................................................................................................................. 53

Purpose................................................................................................................................................................ 53File Structure....................................................................................................................................................... 55Using the Logic Forcing Display Program.......................................................................................................... 56Forcing and Unforcing Logic Signals ................................................................................................................. 56Starting the Logic Forcing Display ..................................................................................................................... 57Loading a Logic Forcing Display File ................................................................................................................ 58

Logic Forcing Display Window...................................................................................................................... 59Logic Forcing Display Screen Window .......................................................................................................... 59Navigating Within a Logic Forcing Display Screen ....................................................................................... 61Modifying a Pointname or Line ...................................................................................................................... 61Adding and Deleting a Pointname Line .......................................................................................................... 61Using the Command Targets........................................................................................................................... 61Printing From the Logic Forcing Display File ................................................................................................ 62Other Options.................................................................................................................................................. 62Saving a Logic Forcing Display File............................................................................................................... 62Exiting the Logic Forcing Display Program ................................................................................................... 62

Control Constants Display ...................................................................................................................................... 63Purpose................................................................................................................................................................ 63Menu Structure.................................................................................................................................................... 63Command Line Description ................................................................................................................................ 64Header Timetag................................................................................................................................................... 64Changing a Control Constant .............................................................................................................................. 64

iv GEH-6126

Control Constants Adjust Display........................................................................................................................... 65Purpose................................................................................................................................................................ 65

Demand Display...................................................................................................................................................... 65Purpose................................................................................................................................................................ 65Demand Display Menu Screen............................................................................................................................ 66Demand Display Data Screen.............................................................................................................................. 66File Structure....................................................................................................................................................... 66Using the Demand Display Program................................................................................................................... 67Starting the Demand Display Program................................................................................................................ 67Loading Demand Display Files and Screens....................................................................................................... 69The Demand Display Window............................................................................................................................ 70

Demand Display Screens Window.................................................................................................................. 72Header ............................................................................................................................................................. 73Legend............................................................................................................................................................. 74Data Area ........................................................................................................................................................ 74Immediate Action............................................................................................................................................ 75Arm/Execute ................................................................................................................................................... 75Analog Setpoint............................................................................................................................................... 75

Selecting a Demand Display Screen ................................................................................................................... 75Creating a New Demand Display Screen ........................................................................................................ 76Modifying a Demand Display Screen Definition/Type................................................................................... 76Changing a Display Title................................................................................................................................. 77Navigating ....................................................................................................................................................... 78Adding/Deleting a Pointname or Line............................................................................................................. 78Modifying a Pointname or Line ...................................................................................................................... 78Adding a Command Target ............................................................................................................................. 78Deleting a Command Target ........................................................................................................................... 80Modifying a Command Target ........................................................................................................................ 80Using a Command Target ............................................................................................................................... 80Printing............................................................................................................................................................ 81Other Options .................................................................................................................................................. 81Saving Demand Display Screens and Demand Display Files ......................................................................... 81Copying Demand Display Screen Definitions................................................................................................ 82Exiting the Demand Display Program............................................................................................................. 82

Alarm Logger Control............................................................................................................................................. 82Purpose................................................................................................................................................................ 82Using the Alarm Logger Dialog Box .................................................................................................................. 83Select Information to be Printed.......................................................................................................................... 83Select Unit........................................................................................................................................................... 84Executing the Alarm Logger Control .................................................................................................................. 84Command Line Description ................................................................................................................................ 85

Header Timetag............................................................................................................................................... 85Hold List ................................................................................................................................................................. 85

Hold List Points................................................................................................................................................... 86Hold List Programs ............................................................................................................................................. 86Hold List Rules ................................................................................................................................................... 86

Manual Sync Object ................................................................................................................................................ 87Scope Tab............................................................................................................................................................ 88Breaker Tab......................................................................................................................................................... 89Permissives Tab .................................................................................................................................................. 90Buttons Tab ......................................................................................................................................................... 91Values Tab .......................................................................................................................................................... 92Colors Tab........................................................................................................................................................... 93

Chapter 6 Configuration.............................................................................................................................. 93Introduction............................................................................................................................................................. 93

GEH-6126 v

HMI Configuration ................................................................................................................................................. 94HMI Configuration Overview............................................................................................................................. 94TCI Configuration............................................................................................................................................... 96TCI Registry Information - Control Panel Applet............................................................................................... 97TCI Configuration Files ...................................................................................................................................... 98

F:\CONFIG.DAT ............................................................................................................................................ 98F:\TIMEZONE.DAT....................................................................................................................................... 98

Optional Configuration Files............................................................................................................................... 98TCI Font Loading................................................................................................................................................ 99TCI Print Queues ................................................................................................................................................ 99

EPA Log................................................................................................................................................................ 100EPA Logger ...................................................................................................................................................... 100EPA Data Display ............................................................................................................................................. 102

Defining EPA Data Points ............................................................................................................................ 102Turbine Control Maintenance Icons.................................................................................................................. 104

Stagelink ............................................................................................................................................................... 105Terms of Reference........................................................................................................................................... 106Stage Link Characteristics................................................................................................................................. 106

The Primary Operator Interface, HMI........................................................................................................... 107Cable Recommendations............................................................................................................................... 107Total Effective Distance Rules...................................................................................................................... 109Redundant System Rules (Mark V Only)...................................................................................................... 110Examples....................................................................................................................................................... 111

Fiber Optics....................................................................................................................................................... 113Advantages.................................................................................................................................................... 113Disadvantages ............................................................................................................................................... 114

Review of Components ..................................................................................................................................... 114Basics ............................................................................................................................................................ 114Cable ............................................................................................................................................................. 115Hubs .............................................................................................................................................................. 115Connectors .................................................................................................................................................... 116

System Considerations ...................................................................................................................................... 116Installation......................................................................................................................................................... 117Specifications .................................................................................................................................................... 118

Four Fiber Cable without Armor................................................................................................................... 118Four Fiber Cable with Armor........................................................................................................................ 119Fiber Optic Hub ............................................................................................................................................ 121Fiber Optic Connectors ................................................................................................................................. 121Typical Stage Link Addresses....................................................................................................................... 121

Control Hierarchy ................................................................................................................................................. 123Overview........................................................................................................................................................... 123

Defining a Control Hierarchy........................................................................................................................ 123Time Zone Make Utility Program – TZ_MAKE .......................................................................................... 129

TCI Control Panel Applet .................................................................................................................................... 132Auto Login ........................................................................................................................................................ 132ARCNET .......................................................................................................................................................... 132Site .................................................................................................................................................................... 133Time Sync ......................................................................................................................................................... 133TCI Alarm and Event Logger ........................................................................................................................... 133CIMPLICITY Project ....................................................................................................................................... 134

Introduction................................................................................................................................................... 134Setup ............................................................................................................................................................. 134Signals........................................................................................................................................................... 135Alarms........................................................................................................................................................... 136Importing Signals.......................................................................................................................................... 136Configuring Exciter Alarms.......................................................................................................................... 138

vi GEH-6126

Unit Configuration ................................................................................................................................................ 139Unit Configuration Overview............................................................................................................................ 139HMI F: \ Drive Configuration Files .................................................................................................................. 140HMI Unit-Specific Directory ............................................................................................................................ 142

Unit-Specific Assignment Files..................................................................................................................... 142Unit-Specific Data Dictionary Files .............................................................................................................. 143Unit-Specific I/O Configuration Constants ................................................................................................... 144Unit-Specific Table Files .............................................................................................................................. 145Unit-Specific CSP Segment Files.................................................................................................................. 146

Compiling Unit-Specific Configuration Files ................................................................................................... 146Downloading Unit-Specific Configuration Files............................................................................................... 147Control Constants.............................................................................................................................................. 147DABUILD......................................................................................................................................................... 148DCBUILD1....................................................................................................................................................... 149DDLOCATE ..................................................................................................................................................... 151DDUTIL............................................................................................................................................................ 154MK5MAKE....................................................................................................................................................... 155FMVID.............................................................................................................................................................. 157

Overview....................................................................................................................................................... 157Operation....................................................................................................................................................... 157

LDB2RAM........................................................................................................................................................ 158Overview....................................................................................................................................................... 158Operation....................................................................................................................................................... 159

LDBCHK .......................................................................................................................................................... 160Overview....................................................................................................................................................... 160Operation....................................................................................................................................................... 160

ALARM_L........................................................................................................................................................ 160Overview....................................................................................................................................................... 160Operation....................................................................................................................................................... 161

DMD2SRC........................................................................................................................................................ 161Overview....................................................................................................................................................... 161Starting The Demand Display to Source Conversion Program ..................................................................... 167Editing the Demand Display Source File ...................................................................................................... 168

CONSTSET ...................................................................................................................................................... 168Overview....................................................................................................................................................... 168Operation....................................................................................................................................................... 168Application Information................................................................................................................................ 169

CONSTCHK ..................................................................................................................................................... 170Overview....................................................................................................................................................... 170Operation....................................................................................................................................................... 170Example......................................................................................................................................................... 171

SEQCOMPL (Sequencing) ............................................................................................................................... 171Overview....................................................................................................................................................... 171File Structure................................................................................................................................................. 172Executing the Sequence Compiler ................................................................................................................ 172Master Sequencing Configuration File.......................................................................................................... 173

SEQDOCMT (Sequencing)............................................................................................................................... 177Overview....................................................................................................................................................... 177File Structure................................................................................................................................................. 177

SEQEDIT (Sequencing).................................................................................................................................... 181Overview....................................................................................................................................................... 181File Structure................................................................................................................................................. 182Using The Control Sequence Editor.............................................................................................................. 183Starting The Control Sequence Editor........................................................................................................... 184Loading An Existing Segment ...................................................................................................................... 184Loading A New Segment .............................................................................................................................. 185

GEH-6126 vii

The Control Sequence Editor Window ......................................................................................................... 185Navigating Within a Segment Window......................................................................................................... 186Editing an Existing Rung .............................................................................................................................. 186Selecting Rungs............................................................................................................................................. 186Copying Rungs.............................................................................................................................................. 186

Moving Rungs................................................................................................................................................... 187Adding A Rung ............................................................................................................................................. 187Deleting A Rung ........................................................................................................................................... 187Selecting The Rung Type.............................................................................................................................. 187Adding Rld Rungs......................................................................................................................................... 187Adding Primitive Rungs................................................................................................................................ 188Adding BBL Rungs....................................................................................................................................... 188Adding Comment Rungs............................................................................................................................... 188Viewing Multiple Segments Windows.......................................................................................................... 189Saving a Segment.......................................................................................................................................... 189Exiting the Control Sequence Editor............................................................................................................. 190

CSPPRINT........................................................................................................................................................ 190Overview....................................................................................................................................................... 190File Structure................................................................................................................................................. 190Using the CSP Printer Program..................................................................................................................... 191Command Line Arguments ........................................................................................................................... 191Screen Description ........................................................................................................................................ 191Page Setup..................................................................................................................................................... 192Printer Selection............................................................................................................................................ 193How to Print the CSP .................................................................................................................................... 193

TABLE_C (Table Compile).............................................................................................................................. 193Overview....................................................................................................................................................... 193Operation....................................................................................................................................................... 194

IO Configuration ................................................................................................................................................... 195EEPROM .......................................................................................................................................................... 195

Overview....................................................................................................................................................... 195Operation....................................................................................................................................................... 196Application Information................................................................................................................................ 197

UDF ................................................................................................................................................................. 198Overview....................................................................................................................................................... 198Operation....................................................................................................................................................... 199

Chapter 7 Remote Access and Control....................................................................................................201Remote Access...................................................................................................................................................... 201

Web Interface.................................................................................................................................................... 201FTP Interface .................................................................................................................................................... 202Remote Mount Disks ........................................................................................................................................ 202

GEIS Standard Message Formats.......................................................................................................................... 202Introduction....................................................................................................................................................... 202Notation............................................................................................................................................................. 202Timetag Considerations .................................................................................................................................... 204GSM Message Type Summary ......................................................................................................................... 205Administrative Message Formats...................................................................................................................... 206

Supported Controller Request: ...................................................................................................................... 206Supported Controller Response......................................................................................................................... 207Heartbeat Message ............................................................................................................................................ 208Event-Driven Data Messages............................................................................................................................ 209

Alarm Record Establish Request................................................................................................................... 209Alarm Record Establish ACK/NAK Response ............................................................................................. 209Alarm Data Messages ................................................................................................................................... 210

viii GEH-6126

Digital Input Record Establish Request ........................................................................................................ 213Digital Input Record Establish ACK/NAK Response ................................................................................... 214Digital Input Data Messages ......................................................................................................................... 215Software Event Record Establish Request .................................................................................................... 217Software Event Record Establish ACK/NAK Response............................................................................... 218Software Event Data Messages ..................................................................................................................... 219

Periodic Data Messages .................................................................................................................................... 221Periodic Data Request ................................................................................................................................... 221Periodic Data ACK/NAK Response.............................................................................................................. 223Periodic Data Message .................................................................................................................................. 223

Command Messages.......................................................................................................................................... 224Alarm Command Request ............................................................................................................................. 224Alarm Command ACK/NAK Response........................................................................................................ 225Alarm Dump Messages ................................................................................................................................. 226Process Control Command Requests: ........................................................................................................... 230Process Control Command ACK/NAK Response......................................................................................... 231

Application Notes.............................................................................................................................................. 233Networking.................................................................................................................................................... 233TCP communications .................................................................................................................................... 234Telnet Interface ............................................................................................................................................. 234Command Summary:..................................................................................................................................... 235Point ID Hint Parameter ................................................................................................................................ 235EGD .............................................................................................................................................................. 235

TCI Modbus .......................................................................................................................................................... 236Introduction....................................................................................................................................................... 236

Modbus Slave................................................................................................................................................ 236Modbus Master.............................................................................................................................................. 236

MODBUS_L ..................................................................................................................................................... 237Overview....................................................................................................................................................... 237Operation....................................................................................................................................................... 237Specifications ................................................................................................................................................ 238External Communication Links- Modbus Slave mode.................................................................................. 238External Communication Links- Modbus Master Mode............................................................................... 239

RS232 and Modbus ........................................................................................................................................... 239Physical Link Layer/Format, RS232 Communications..................................................................................... 240

Link Layer..................................................................................................................................................... 240Physical Layer ............................................................................................................................................... 240

TCI Modbus Configuration............................................................................................................................... 243F:\IO_PORTS.DAT: Modbus Link Definition.............................................................................................. 243Modbus Master Setup.................................................................................................................................... 244Modbus Slave configuration: Holding Coils, Input Coils, Holding Registers, Input Registers .................... 245Modbus Slave: @SPARE: Unused Coils and Registers................................................................................ 246Modbus Slave: F:\UNITn\MODBUS.DAT: MODBUS Mapping File Format............................................. 246Modbus Master Configuration ...................................................................................................................... 248

Description Of Modbus_Data_File ................................................................................................................... 250Table_Type Table_point CSDB_Pointname............................................................................................... 250MODBUS_L.EXE: MODBUS Listing Program........................................................................................... 251F:\UNITn\MODBUS.LST: MODBUS Listing File ...................................................................................... 252

Modbus Data Format And Scaling.................................................................................................................... 254Modbus Data Conversions: Logics ............................................................................................................... 254Modbus Data Conversions: Analogs ............................................................................................................. 254RS16.............................................................................................................................................................. 254RU16 ............................................................................................................................................................. 255UN12............................................................................................................................................................. 255HW12............................................................................................................................................................ 256NATIVE........................................................................................................................................................ 257

GEH-6126 ix

Modbus Command And Response Definition......................................................................................... .......... 257Introduction................................................................................................................................................... 257

RTU Transmission Mode.................................................................................................................................. 258Message Errors.............................................................................................................................................. 258

Exception Code Response Format .................................................................................................................... 259Function Code Details................................................................................................................................... 260Function Code 01: Read Holding Coils ........................................................................................................ 260Function Code 02: Read Input Coils ............................................................................................................. 261Function Code 03: Read Holding Registers .................................................................................................. 262Function Code 04: Read Input Registers....................................................................................................... 263Function Code 05: Force Single Holding Coil .............................................................................................. 264Function Code 06: Preset Single Holding Register....................................................................................... 264Function Code 07: Read Exception Status ................................................................................................... .265Function Code 08: Diagnostic....................................................................................................................... 266Function Code 0F: Force Multiple Holding Coils......................................................................................... 268Function Code 10: Preset Multiple Holding Registers.................................................................................. 268

Modbus Master Diagnostics.............................................................................................................................. 269Statistics ........................................................................................................................................................ 270

Chapter 8 Time Sync................................................................................................................................271Time Synchronization ........................................................................................................................................... 271

Time Synchronization Features......................................................................................................................... 271Supported GTSs that use periodic pulses: ..................................................................................................... 272

General Architecture ......................................................................................................................................... 273Backup Synchronization ................................................................................................................................... 274Documentation Organization ........................................................................................................................... 274

Overview....................................................................................................................................................... 274Basic Theory of Turbine Control Time Synchronization.............................................................................. 274Hardware Setup............................................................................................................................................. 274Software Setup and Configuration ................................................................................................................ 274General Timesync Operations....................................................................................................................... 274Diagnostics and Troubleshooting.................................................................................................................. 274Sample Timesync Configurations ................................................................................................................. 274Appendix A - IRIG Nomenclature ................................................................................................................ 275Glossary ........................................................................................................................................................ 275Related Documents ....................................................................................................................................... 275Time Synchronization Theory....................................................................................................................... 275Timesync Protocol ........................................................................................................................................ 275GPS Interface ................................................................................................................................................ 277

Hardware Setup..................................................................................................................................................... 278Testing the Time and Frequency Board ............................................................................................................ 278

Board Installation.......................................................................................................................................... 278Setting Base I/O Address .............................................................................................................................. 279Setting the IRQ.............................................................................................................................................. 279Connecting the GTS to bc627AT.................................................................................................................. 280

Time Processing Board TPRO_PC ................................................................................................................... 280Board Installation.......................................................................................................................................... 281Setting Base I/O Address .............................................................................................................................. 281Event Input.................................................................................................................................................... 281Setting the IRQ.............................................................................................................................................. 281Connecting the GTS to the Board ................................................................................................................. 282Connecting the Operator Interface ................................................................................................................ 282

Software Setup ...................................................................................................................................................... 283Timesync Data File ........................................................................................................................................... 283

File Configuration ......................................................................................................................................... 283

x GEH-6126

TCI Control Panel Applet ............................................................................................................................. 287Timesync Operation ...................................................................................................................................... 287General Operations........................................................................................................................................ 287Using the TIMEUTIL Program..................................................................................................................... 288Turning Off the TIMESYNC Function ......................................................................................................... 288Restoring the TIMESYNC Function............................................................................................................. 288Loading MAJOR TIME into the Time Processing Board ............................................................................. 289

Diagnostics and Troubleshooting.......................................................................................................................... 289Obtaining General Information About the Turbine Control Timesync Function .............................................. 289Other Timesync Diagnostic Capabilities........................................................................................................... 291Sample Timesync Configurations ..................................................................................................................... 294

Examples ....................................................................................................................................................... 294Testing the bc620AT/bc627AT Time and Frequency Board ............................................................................ 299

Test #1........................................................................................................................................................... 300Test #2........................................................................................................................................................... 301Test #3........................................................................................................................................................... 303Test #4 and Test #5 ....................................................................................................................................... 304

Glossary of Terms ..................................................................................................................................................... 307

Appendix A............................................................................................................................................................... 311

GEH-6126 xi

Conventions

The following conventional terms, text formats, and symbols are used throughout this documentation for he describedapplications.

Convention Meaning

Bold Indicates that the word is being defined.

Arial Bold Indicates the actual command or operation that is chosen from a menuor 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 offigures, 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 adialog 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 thecommand prompt.

!Warning

This equipment contains a potential hazard ofelectric shock or burn. Only personnel who areadequately trained and thoroughly familiar withthe equipment and the instructions should install,operate, or maintain this equipment.

Isolation of test equipment from the equipmentunder test presents potential electrical hazards. Ifthe test equipment cannot be grounded to theequipment under test, the test equipment’s casemust be shielded to prevent contact by personnel.

To minimize hazard of electrical shock or burn,approved grounding practices and proceduresmust be strictly followed.

To prevent personal injury or equipment damagecaused by equipment malfunction, only adequatelytrained persons should modify any programmablemachine.

xii GEH-6126

GEH-6126 Chapter 1 Overview • 1

Chapter 1 Overview

Introduction

This manual provides information on the use and maintenance of the HumanMachine Interface, referred to here as HMI, for application to Mark V and Mark VLM 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 operatorcan thereby select the units he wishes to monitor or issue commands to. All HMIsare capable of issuing commands to a unit at any time while communicating withMark V control panels. For the purposes of this manual, it is assumed the HMI iscontrolling a single turbine and driven device.

Commands - may be issued to the turbine and driven device. Examples consist ofSTART, 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 VIBRATIONFEEDBACK (see figure on next page).

2 • Chapter 1 Overview GEH-6126

Sample Display

The associated printer(s) enables the operator to manually select and copy anydisplay, to automatically log selected parameters, and to log alarms.

GEH-6126 Chapter 1 Overview • 3

HMI SCREEN(s)

Stage Link

TURBINE

MARK VPANEL

CIMPLICITYSERVER

PointDataBase

DataDictionary

Mark VDevice

Communication

Turbine Control Interface

#1

HMIVIEWER

Windows NT

HMIVIEWER

Windows NT

#2

Ethernet

I/O

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:

• 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

4 • Chapter 1 Overview GEH-6126

The Mark V Stage Link (see GEH-6195 for Mark V, GEH-6353 for Mark V LM) isthe communication link between a turbine control panel and the HMI. Theconfiguration section of this manual includes a section on Stage Link.

Communication with a DCS can also be accomplished using MODBUS protocolover 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 besupplied.

Alarm Logging, though with a lower time resolution, to disk storage is availablethrough CIMPLICITY™ Logging.

Note The auxiliary components of an HMI such as the printer(s) and LDDS(s) maynot be the same for all HMIs on a particular site.

Related Documents

SPEEDTRONIC Mark V Turbine Control User’s Manual– GEH-5979The user’s manual provides information needed by a turbine operator to understandboth the primary and back-up Mark V operator interfaces. Topics in the manualinclude:

• 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 MaintenanceManual – GEH-5980 The maintenance manual provides information needed by control systemmaintenance personnel for installation, calibration, and troubleshooting the Mark Vcontrol 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

GEH-6126 Chapter 1 Overview • 5

SPEEDTRONIC Mark V Turbine Control ApplicationManual 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 ManualOverview – GEH-6354. The application manual is an engineer’s reference for the Mark V LM controlsystem. It provides information needed by control system maintenance personnel forinstallation, calibration, and troubleshooting the Mark V LM control system. Topicsin 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-1180The application manual is an engineer’s reference for the CIMPLICITY BaseSystem.

Getting AssistanceIf assistance is needed, please contact:

GE Industrial SystemsProduct Service Engineering, Rm. 1911501 Roanoke Blvd.Salem, VA 24153-6492 USAPhone + 1 540 387 7595Fax + 1 540 387 8606

6 • Chapter 1 Overview GEH-6126

Notes

GEH-6126 Chapter 2 Start Up • 7

Chapter 2 Start Up

Logging On

After powering on the HMI and waiting until a “window” box appears for logoninstruction log on to the Windows NT® operating system, press Ctrl-Alt-Delete. Alog on window will then appear where you can enter your User ID and password. Ifyou do not have a User ID and password, contact your system administrator to obtaina 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 thelog on. Click on the Cancel button to abort the log on. Click on the Help button forinformation on how to log on. Click on the Shut Down button to halt the systemprior to powering down the computer.

Main Cimview

A typical HMI system will have a Desktop shortcut to the main CimView displayscreen. Double click on the Desktop shortcut to activate the display screen. Somesystems may have a shortcut on the Start menu instead of or in addition to theDesktop shortcut. You can also create shortcuts to other frequently used displayscreens. To create a new shortcut, right click on the Desktop and chooseNew/Shortcut from the pop-up menu.

For more information about CimView, consult the CIMPLICITY Base System User’sManual, GFK-1180

8 • Chapter 2 Start Up GEH-6126

Alarm Displays

A typical HMI system will have one or more alarm displays configured. Somesystems may have a Desktop or Start menu shortcut for each alarm display. Most ofthe CimView display screens will have a transfer button that will call up an alarmdisplay.

The alarm display contains a scrollable viewing area and one or more rows ofbuttons along the bottom of the display. The buttons allow you to take action on thealarms displayed in the viewing area. To take an action on an alarm, select thedesired alarm in the viewing area and click on the button that corresponds to thedesired action (e.g. Acknowledge, Lock).

You may notice that other displays contain an abbreviated alarm display in the lowerportion of the screen. Typically the last few alarms are displayed and there are noaction buttons. You will need to transfer to the alarm display to take action onalarms.

The alarm display has two modes of operation:

• Dynamic mode - all alarms might NOT be displayed. If there are more alarmsthan will fit in the viewing area then only the most recent alarms will bedisplayed until the viewing area is filled. The display updates in real time as thealarm 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 alarmsthan will fit in the viewing area, a scroll bar will appear on the right edge on thewindow. This mode is used if the alarm incoming rate makes it difficult to selectan individual alarm.

Commands

Each CimView display screen contains one or more action objects that will invokecommands. When the mouse pointer is over an action object, a rectangle will appearhighlighting the action object. By clicking the left mouse button or pressing theenter key, you can invoke the configured command(s).

Style RecommendationsGE recommends that push buttons on CimView displays follow a consistent style ofappearance and interaction with the user. Any push button that sends a command oranalog setpoint to the turbine control should adhere to this style.

Consistent color coding of pushbuttons to indicate their function will help preventoperator errors. A suggested scheme for operator pushbuttons is:

• Green - command pushbutton with confirmation• Red - command pushbutton without confirmation• Gray - analog setpoint

GEH-6126 Chapter 2 Start Up • 9

Advanced Topics

TrendingYou can use CIMPLICITY HMI Trending to embed trend charts in CimView andCimEdit screens. The charts can display line trends from CIMPLICITY HMIDatabase 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 bedisplayed in the same chart.

• Display trends with data from different time periods so those differentproduction periods can be compared in the same chart.

• Display trends with different time duration so those production periods ofdiffering length can be compared in the same chart.

• Display trends with auto update enabled so that the most recently logged data isautomatically retrieved from disk while the trend is displayed.

• Display lines containing run-time data as reported by CIMPLICITY HMI PointManagement.

• 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 actualvalues.

• Display long time periods in compressed format where the plotted data is theaverage, 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 PanelThis 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 Pointbrowser opens.

10 • Chapter 2 Start Up GEH-6126

Select the project from which you want to display points. To request a list of allpoints, just select Browse . To refine the list, you can enter search strings for PointID, 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 thepoints you selected. All the points you requested are automatically selected in thePoint Control Panel so that you can just look at them, then delete them from theview if you wish.

The current value, units and timestamp for each point are displayed in the PointControl Panel . If a point is in an alarm condition, its text is displayed in theappropriate color.

You can display point properties for each point in the list. You can also perform asetpoint, 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’sManual, GFK-1180).

Demand DisplayMany applications require monitoring several turbine data points at a time. Some ofthese applications may also require the issuing of simple commands. This tool isdesigned for these applications.

Demand Displays offer flexible monitoring and control of a variety of points and ofmultiple 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 specialprocedures.

• 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 inthe selected Demand Display file. Selecting one of the Demand Display screenson the list accesses the screen.

Note New Demand Display screens must be added to the menu for access. TheDemand 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 Controlsection of this manual.

GEH-6126 Chapter 3 Theory of Applications • 11

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):

• 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.

12 • Chapter 3 Theory of Applications GEH-6126

Point Mgr

AlarmsE-net

Point Data

GE Fanuc

GE Motors & Industrial Systems

CIMPLICITY SERVER

PointDataBase

SRTPEGD

DEVCOM

Devices

Point Data

AlarmMgr

E-net

EXTERNALAlarm MgrInterface

Alrm API

X LibraryMARKVRP

CIMB

ARCNET

DataDictionary

TCI

ALARMSYSTEM

Data Collectionand otherfunctions

Overview of CIMPLICITY Server

Directory Structure

The HMI software is stored in three groups on the hard disk drive; the first isCIMPLICITY, 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 ManualGFK-1180.

TCI Directories:The TCI groups are product-specific software and site-specific software, and aredivided on pseudo or substitute drives. The F: drive contains the site-specificsoftware in various subdirectories. Drive G: contains the software common to allturbine control panels in various subdirectories.

GEH-6126 Chapter 3 Theory of Applications • 13

The hard drive for a typical factory-configured TCI computer is partitioned to be onelogical drive, C:. The following shows a directory tree for C: of a typical TCIcomputer.

C:

CIMPLICITY

TCI

SITE

RUNTIME

DATA

EXEC

LOG

UNIT1

PROM

USER

UTILITY

The following shows a directory tree for the pseudo drive F:.

F:

RUNTIME

UNIT1

USER

PROM

The following shows a directory tree for the pseudo drive G:.

DATA

EXEC

G:

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 runningunder TCI require the above pseudo drive and directory structure for properoperation of the TCI and the transmission of data to and from the unit controlpanel(s).

Drive F: FilesThe top level of the pseudo drive F: contains the following site-specific configurationfiles:

CONFIG.DAT is the master site configuration file. It specifies items such as howmany units exist on the site and the unit names and subdirectory names containingall the unit specific information. It also contains network information about whatcommunication links exist out of the TCI and which units can be reached on thoselinks.

14 • Chapter 3 Theory of Applications GEH-6126

SYSTEM.DD is the master data dictionary file. It contains pointers to all the unit.ddfiles 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 inthe DEMANDNN.DM2 files. It also contains the last ten trip history files from MarkV 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 thecurrent default directory has not changed, the data files output by these programscould be found here.

\UNITN is created for each unit being controlled by a TCI, where n is equal to theunit 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 directoryand should always be kept there. This directory contains the files, which configureand program the unit control (Such as UNITDATA.DAT, IOSCALE.DAT,ALARM.DAT, AND CONSTSET.DAT.).

\UNITN\PROM contains control panel processor PROM-related files. Programssuch as the I/O Configurator, the CSP Documenter, the Control Sequence Editor, theControl Sequence Compiler, and others use them. The files in this sub-directorymust match the BBL and memory location information stored in the processorPROMs for proper configuration and operation of the control panel.

Drive G: Sub-directoriesSub-directories on drive G: contain the following information/files:

\EXEC contains all the executable files/programs that form the basic TCI and anybatch files used during start-up or execution.

\DATA contains any data files, which programs require that are not site-specific. Italso contains any generic data files, which might be used before any site-specificdata files are created. Programs using data files look for and use any files found insite-specific directories on drive F: first. They only use the generic data files if nosite-specific files can be found.

\LOG contains the output from various programs, which might be important fordebugging or troubleshooting purposes. Error log files and normal start-up files arestored here.

GEH-6126 Chapter 3 Theory of Applications • 15

Program Categories

The HMI has three software components:

• CIMPLICITY

• TCI

• CIMB

CIMPLICITY is used primarily for displaying various screens that show the state ofthe turbine, so the operator can monitor the unit(s). Screens typically have a refreshrate of 1 second. CIMPLICITY cannot configure the turbine control. For descriptionof 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 configurea turbine unit and to affect the control of a turbine unit. TCI provides threecategories of functionality: Displays, Control, and Configuration. TCI also providestwo kinds of remote access to turbine data and control.

CIMB (CIMPLICITY Bridge) enables CIMPLICITY to collect data and alarmsfrom a turbine unit. CIMB is made of:

• MARKVRP - Collects data from a Turbine using TCI and forwards theinformation to the CIMPLICITY Point Manager.

• EXTMGR - Collects alarms and forwards them to the CIMPLICITY AlarmManager.

• LOCKOUT - Sends a lockout command to a unit using TCI. It is configuredas a button in the CIMPLICITY Alarm Viewer. The syntax is:

LOCKOUT:<ACTION><UNITNAME><ENCODED_DROP><REFID>[(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)].

16 • Chapter 3 Theory of Applications GEH-6126

DisplaysTCI provides various programs to look at turbine data. Their primary purpose is toallow real-time monitoring of a turbine unit. Some programs show data that updatesevery 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.

ControlTCI provides several programs that display parameters, which are involved in thecontrol of a turbine. They also allow some modification of these control parameters.For example, constants may be viewed and some logical points, which affect thesequencing of the control system, may be forced.

ConfigurationTCI provides several important programs that facilitate the setup and configurationof the HMI and unit control. These programs can be used to change configurationand download configuration to the unit control.

Remote Data and ControlTCI provides two programs for remote data monitoring and unit control. They canprovide a DCS and other remote devices access to turbine control and data.

GEH-6126 Chapter 4 Display Applications • 17

Chapter 4 Display Applications

Introduction

This chapter contains information about programs that display data and configurationinformation about the unit control, Stagelink, and HMI. These programs are usefulin analyzing problems with the control system. None of the programs in this sectionhave the capability to issue control commands.

.

ARCWHO

PurposeARCWHO 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 trackdown ARCNET communication problems, and during the initial installation to verifythat the unit configuration information is correct.

BackgroundThe Mark V family of Turbine Controls communicates with the HMI using anindustry standard ARCNET connection. Each device on the ARCNET is given anaddress that must be unique. This address is used in the F:\CONFIG.DAT file tomatch units with ARCNET addresses.

The ARCWHO utility program uses the ARCNET driver in the HMI to poll for nodeson the ARCNET. All nodes that are present on the ARCNET will be listed, it doesnot matter what type of node (turbine control, HMI, etc.) it is.

OperationARCWHO is normally run from a DOS window. There are no command lineparameters. The ARCNET addresses shown are always presented in HEX, which ishow they are specified in the F:\CONFIG.DAT file (see example on next page).

18 • Chapter 4 Display Applications GEH-6126

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 secondHMI. There are three ARCNET nodes visible, at addresses FE, FC, and 1F. Thiswould be typical of a site with two Mark V controllers (addresses FE and FC) andone other HMI (1F).

CARD_ID

PurposeCARD_ID is a Command Line utility program that will scan a Mark V or Mark VLM turbine control panel and report on the versions of the PROMS that are found. Itis useful in cases where you need to know the version of the panel’s PROMs, such asduring upgrades, field replacements, or advanced troubleshooting.

Note The term firmware is software changed by manipulated hardware. In thiscase, the firmware is different by changing the PROM on the card.

BackgroundThe Mark V and Mark V LM turbine control panels consist of many individualprocessor cards. Each processor card has a PROM associated with it that contains thefirmware that drives the card. Revising the firmware on the card (the PROM revisionlevel) is often required. This determines the available options on the card. Thisinformation is often needed during card replacement and during panel upgrades. Thisinformation can be read from the sticker on the PROM, but it is sometimes easier touse the CARD_ID utility.

There are some differences in the information that is available for the Mark V andthe Mark V LM turbine control panels.

The Mark V turbine control is polled for each possible PROM, and it responds withthe version of the PROM. The version consists of two fields, the card name (such asTCDA) and the version number (such as 1.2).

Note Because the Mark V poll is for any possible card, a panel that does not haveevery possible card will generate a diagnostic alarm when a non-existent card ispolled during this process. These diagnostic alarms can be safely ignored.

GEH-6126 Chapter 4 Display Applications • 19

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 theflexibility in the card sets that can be configured for the panel. The Mark V LM usesthe PANEL.CFG file in the unit configuration directory as a list of cards to poll in thepanel. 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 cardstate. Comparing what the card returned with what is configured in the PANEL.CFGfile will flag any differences. The flag field uses letters to indicate what differenceswere 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 forcards of interest. A card is included in this list if there are any flags indicated. Acommand line parameter (/ALL) can be used to include all cards in this list instead ofonly the flagged cards.

OperationCARD_ID is normally run from a DOS window. If it is run with no parameters orwith 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 canbe used:

/ALL - This option will include every card in the summary instead of only the cardsthat had been flagged.

/FULLID - Normally the information returned by the card is a string that is terminatedwith a null character. Some early cards included information after the null terminatorthat may be of use during advanced debugging. If this option is used the full field(including the information after the null terminator) is shown.

20 • Chapter 4 Display Applications GEH-6126

Examples

Mark V ExampleIn the next example, a Mark V Simplex panel was queried and the PROM revisionsof the cards that were present were reported.

F:\UNIT1> CARD_ID T1Card identification for SALEM PLANT unit T1: System is type ’B’

C-TCCA:(TCCA 4.2 ) C-TCCB:(TCCB 4.1 ) C-320B:(TCCB 4.1 )

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-320B:(TCQB 1.1 )

R-SLCC:(LCCQ 4.4 ) R-SDCC:(DCCQ 6.6 )

R-IOMA:(IOMA 4.5 ) R-TCPA:( ) R-320P:( )

R-TCD1:(TCD1 3.5 ) R-TCD2:( )

R-TCE1:(TCE1 5.2 ) R-TCE2:(TCE2 5.2 ) R-TCE3:(TCE3 5.2 )

No response from <S> No response from <T> Enter any key to exit program:

F:\UNIT1>

GEH-6126 Chapter 4 Display Applications • 21

Mark V LM ExampleIn the next example, a Mark V LM was queried and the PROM revisions of the cardsthat were present were reported. Notice that a card that does not support theCARD_ID message type (R:25 processor 1) will not show up in the list of Items ofInterest. Cards that respond but are unable to determine their own revisions (R:25processor 0) do appear in the Items of Interest.

F:\UNIT2> CARD_ID T2

SYSTEM IS MARK V LM

|----------EXPECTED-----------|------------ACTUAL------------- ---

BMS |PR HARDWARE FIRMWARE |PR HARDWARE FIRMWARE ST HFS

----- |-- ------------ ------------ |-- ------------ ------------ -- ---

R:13 | 0 UCIAG2AC* UCIAP1AAC |

R:25 | 0 UCPBG7AF* DS206TMCAED | 0 DS206TMCAED A7 H

R:25 | 1 UCPBG7AF* DS206TMQAEF |

R1:01 | 0 TCQAG1BF* TCQAP1BBB | 0 TCQAG**** TCQAP1BBB A7

R1:02 | 0 TCQEG1AE* TCQEP1ABB | 0 TCQEG**** TCQEP1ABB A7

R1:02 | 1 TCQEG1AE* TCQEP2AAB | 1 TCQEG**** TCQEP2AAB A7

R1:04 | 0 TCDAG1BF* TCDAP1BCG | 0 TCDAG1BG* TCDAP1BCG-1 A7 HF

R1:12 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7

R1:13 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7

R1:13 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7

R1:15 | 0 TCEAG1BA* TCEAP1BBC | 0 TCEAG**** TCEAP1BBC A7

R1:16 | 0 TCEAG1BA* TCEAP1BBC | 0 TCEAG**** TCEAP1BBC A7

R1:17 | 0 TCEAG1BA* TCEAP1BBC | 0 TCEAG**** TCEAP1BBB-1 A7 F

R2:01 | 0 TCQAG1BF* TCQAP1BBB | 0 TCQAG**** TCQAP1BBC A7 F

R2:12 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7

R2:13 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7

R2:13 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7

R3:01 | 0 TCQAG1BF* TCQAP1BBB | 0 TCQAG**** TCQAP1BBB A7

R3:12 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7

R3:13 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7

R3:13 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7

R5:01 | 0 TCCAG1BA* TCCAP1BAD | 0 TCCAG**** TCCAP1BAD A7

R5:02 | 0 TCCBG1BE* TCCBP1BAC | 0 TCCBG**** TCCBP1BAC A7

R5:02 | 1 TCCBG1BE* TCCBP2BAB | 1 TCCBG**** TCCBP2BAB A7

R5:04 | 0 TCDAG1BF* TCDAP1BCG | 0 TCDAG1BG* TCDAP1BCG A7 H

R5:12 | 0 UCPBG6AF* UCPBP1ACE | 0 UCPBG**** UCPBP1ACE A7

R5:13 | 0 STCAG1AA* STCAP1AAB | 0 STCAG1AA* STCAP1AAB A7

R5:13 | 1 STCAG1AA* STCAP2AAB | 1 STCAG1AA* STCAP2AAB A7

----- |-- ------------ ------------| --- -------- ---- ------

----- LIST OF ITEMS OF INTEREST -----

BMS |PR HARDWARE FIRMWARE | HFS PHYSICAL SLOT (DHTR)

----- |-- ------------ ------------| --- -------- ---- ------

R:25 | 0 UCPBG7AF* DS206TMCAED | H R 1 ( 1H1)

R1:04 | 0 TCDAG1BA* TCDAP1BCG | HF Q11 1 ( )

R1:17 | 0 TCEAG1BA* TCEAP1BAD | F P1 3 ( )

R2:01 | 0 TCQAG1BF* TCQAP1BBB | F R2 2 ( )

R5:04 | 0 TCDAG1BF* TCDAP1BCG | H R51 1 ( )

22 • Chapter 4 Display Applications GEH-6126

CHECKCRC

PurposeCHECKCRC is a Command Line utility program that checks the files distributed bythe TCI Product Code to make sure that all the files exist on the PC, and that theyhave not been corrupted or infected with any computer viruses. It is useful whendebugging software problems to verify that all required Product Code files are inplace and intact.

BackgroundThe TCI Product Code consists of many computer files spread out over multipledirectories. When debugging software problems it is helpful to know that all therequired 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 aTCI.CRC file that contains the Cyclic Redundancy Code (CRC) of all filesdistributed by that product. This file is used by CHECKCRC as the list of files thatmust exist and the CRC of each file. There is one TCI.CRC file in each directory thatTCI populates. This scheme allows multiple Product Code distributions to populatethe same directory - each one will have a separate *.CRC file associated with itsdistribution.

CHECKCRC is currently implemented as a batch file that checks ALL of the *.CRCfiles that it finds in the product distribution directories. This means that runningCHECKCRC will check all products that support this type of CRC file checking.

GEH-6126 Chapter 4 Display Applications • 23

OperationCHECKCRC is normally run from a DOS window. There are no command lineparameters. 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 Serviceis running, then the G: drive will be defined and will be able to find the Product Codefiles 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 thedirectory.

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. Thismeans that the file on the disk is not the same file that was distributed as part of theProduct Code.

ExampleThe next example shows that CHECKCRC found two problems. The first is that theALMRCV.EXE file in the G:\EXEC directory is not the version that was distributedwith the TCI Product Code. (The fact that it is checking the TCI.CRC file means thatthe file is distributed as part of the TCI Product Code.) The second problem was amissing file; the TABLE_C.EXE file appears to have been removed from theG:\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>

24 • Chapter 4 Display Applications GEH-6126

Diagnostic Counters Display

PurposeThe Diagnostic Counters Display (DIAGC) provides information on internal controland I/O card functions used for troubleshooting and/or statistical data gatheringpurposes. This display permits I/O card data not defined in the unit Control SignalDatabase (CSDB) to be viewed. Not all data is defined in the CSDB because eitherthe data must be processed or scaled before it can be used by the Turbine Controlprograms or it is data created by the operating or communication systems of the I/Ocards for troubleshooting purposes.

This information is intended for debugging by experienced field and factorypersonnel. 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 theDiagnostic Counter data on the right. The tree-view can hold and display one unit ata time. Selecting a valid sub-type from the list under a unit/core/card in the tree-view causes that sub-type Diagnostic Counter data to be displayed. That data will bedisplayed until the user selects a different sub-type or changes the unit.

File TypeThe program reads the F:\CONFIG.DAT file to obtain the site information. Theprogram also reads the DIAGC.DAT file for each unit. This file may be located in theF:\UNITN directory or in the F:\UNITN\PROM directory.

Mark V LMThe DIAGC.DAT file is a text file that is produced by the tool programG:\EXEC\DCBUILD1.EXE. DIAGC.DAT should ALWAYS be built from the cardlibrary by the tool program. While DIAGC.DAT is a text file, it should NEVER beedited by hand. DIAGC.DAT files should NEVER be copied from one unit toanother.

Mark VThe DIAGC.DAT file is completed by the Requisition Engineer. This file should NOTbe edited except by qualified field personnel as part of hardware and/or softwaremodifications to the unit control. DIAGC.DAT files should NEVER be copied fromone unit to another.

The program can save the current DIAGC output to a text file. This text file may thenbe opened and viewed with notepad or other text-viewing program. DIAGC cannot beused to open the text file.

GEH-6126 Chapter 4 Display Applications • 25

Using the Diagnostic Counters Display ProgramThis 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 theMain Menu or from the DOS prompt using the command: DIAGC. DIAGC.EXE islocated within the product code in the G:\EXEC subdirectory.

The Diagnostic Counters Display may be launched from the command line with thefollowing 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 dialogbox by entering the command as shown on the command line above, or by selectingthe DIAGC icon from the appropriate program group.

DIAGC - Tree View and Splitter Bar

26 • Chapter 4 Display Applications GEH-6126

The Diagnostic Counters Display WindowThe 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 ison 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 ViewThe Diagnostic Counters tree view window is a graphical window that attempts todepict the hierarchy of panel/core/card/sub-type in a "tree" structure. The tree viewcan 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. Thepanel/core/card levels may be expanded or collapsed to reveal the Diagnostic sub-types available to the user. Selection of a sub-type causes that sub-type DiagnosticCounter data to be displayed in the Diagnostic Counter window. That data will bedisplayed in the data area until the user selects a different sub-type or changes theunit selection.

GEH-6126 Chapter 4 Display Applications • 27

Diagnostic Counter Data Window and Splitter Bar

Diagnostic Counter Data WindowThe Diagnostic Counter Data Window has three main regions:

• Header• Legend• Data Area

28 • Chapter 4 Display Applications GEH-6126

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 thewindow. Although this region may be turned off using the View menu, it isrecommended that users leave the Header visible at all times because of the processinformation displayed.

The Header program name, card, core and socket names all appear on the same lineand serve to uniquely identify the card being examined. The legend contains the sub-type currently being viewed.

Timetag

The Header timetag displays the operator interface time and updates whenever avalid 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 anddisplayed. If there is an error in the number of bytes returned in a message from theunit, the "replies received" field in the Header is highlighted to indicate the mismatchand possible corruption of Diagnostic Counter data on the display.

LegendThe Legend displays the title of the current Diagnostic Counter sub-type. TheLegend 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 thatusers leave the Legend visible at all times.

Data AreaThe Data Area is below the Header and Legend. The Data Area displays the stringsfor the selected Diagnostic Counters sub-type. The value field in the Data Area isupdated at either 1 Hz or 4 Hz.

The timetag displayed in the Header reflects operator interface time when the lastupdate message was received. Unlike the Header and Legend, the information in theData Area may be scrolled with the vertical scroll bar. If the Header "repliesreceived" field is highlighted, the Diagnostic Counter data being displayed may notbe valid.

GEH-6126 Chapter 4 Display Applications • 29

Selecting a Diagnostic Counters DisplaySelecting a particular display establishes a communication link to the card inquestion and asks for the PROM data associated with this display. The tree view onthe left gives an exploded diagram of all the cores within the panel. Each core maybe expanded into its component cards and each card expanded into its diagnosticsdisplays. Use the cursor and keyboard to expand the desired core and card, thenselect the appropriate diagnostic display for the card. The selection is highlightedwith a check mark on the tree view portion of the screen.

Interpreting DataDIAGC is a diagnostic tool for firmware designers and field personnel only. Itspurpose is to assist firmware designers in the performance evaluation of the EPROMbased programming and to assist field personnel in problem diagnosis. While theprogram is a "display only" program that poses no threat to the operation of theturbine control, it does not provide Turbine Operation information and should be runby authorized personnel only.

Information for Card DesignersThe following data types are supported for the Diagnostic Counters Display. Carddesigners should refrain from using data types other than those listed here becausethey 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)

INTEGER 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

Data Types for Diagnostics Counter Display

Type Hn converts signed to unsigned. Type Sn converts unsigned to signed.

30 • Chapter 4 Display Applications GEH-6126

Dynamic Rung Display

PurposeThe Dynamic Rung Display is a tool for stepping through the control programmingof 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 LadderDisplay (RLD) rungs are shown with green representing continuity in contacts andthe energized state in a coil. The Primitive and Big Block rungs may have theirassociated picture files displayed with either signal names or actual point values. ADemand Display with all of the signal names and values from a rung may bedisplayed. A Find utility is included to show the locations and usage of alloccurrences of a signal in the unit’s Control Sequence Program (CSP).

The Dynamic Rung Display may have more than one control segment from a givenunit 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 RungDisplay.

File StructureFiles 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 individualcontrol 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 andprimitives

\PROM\*.SPC Sequencing BBL source files

The files are used by the Dynamic Rung Display to coordinate and accurately displaythe unit control data. These files are also used for unit control configuration andcannot be altered by the Dynamic Rung Display. It is imperative that theconfiguration and sequencing files in the unit control and in the operator interfacematch. The Dynamic Rung display program does NOT independently verify that theoperator interface files match the unit control files. If these files do not match, theDynamic Rung Display may display data that does not reflect the state of the unitcontrol.

GEH-6126 Chapter 4 Display Applications • 31

The Dynamic Rung Display has the capability to save picture file displays in a textformat for future reference. These text files may be opened by any editor or wordprocessing application. It also creates temporary Demand Display (*.DM2) files in thesystem temporary directory when the Demand Display is used to show the points andvalues from a given rung. These files are automatically deleted when the DemandDisplay closes.

Dynamic Rung Display Screen DescriptionThe Dynamic Rung Display is a multiple document interface, which allows the userto open windows with different segments or the same segment. The user may alsohave picture file view windows and sub rung view windows open. The windows aresized to display a full view of a rung; however, the window may be resized andrepositioned.

There are three major types of windows:

• Rung Windows• Picture File Window• Main Frame Window

32 • Chapter 4 Display Applications GEH-6126

Rung WindowsRung Windows are used to display the animation of the control sequencing and tonavigate through the control sequencing segments. Rung Windows may display datafrom 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.

GEH-6126 Chapter 4 Display Applications • 33

Rung Window HeaderHeader 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 isrecommended that users leave the Header visible at all times because the Headercontains valuable process information.

Header Timetag

Big Blocks and Comment RungsThe Header timetag displays the operator interface time of when the rung wasdisplayed.

RLD and Primitive RungsThe Header timetag displays the timetag of the oldest piece of data being displayedin the RLD portions of the rung.

If no data has been received from the unit, then the timetag text will be No ValidData.

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 RungsIn an RLD Rung display, the Header information is displayed in the upper leftcorner. The Header timetag displays the timetag of the oldest piece of data on thisrung. The animation of the rungs occurs once per second. The rules for animatingcontacts and coils are as follows:

Contacts

Normally Open Contacts

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 rectangleoutline around the ">" symbol to highlight the condition.

34 • Chapter 4 Display Applications GEH-6126

Normally Closed Contacts

1. Normally closed contacts are indicated by a slash drawn through thecontact.

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 rectangleoutline around the ">" symbol to highlight the condition. The slashthrough 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 inwith 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 inwith the window background color.

4. Forced signals shall have a ">" symbol in the coil circle. The slashthrough the contacts is broken in the middle to highlight the ">"symbol.

Primitive RungsIn a Primitive Rung display, the Header information is displayed in the upper leftcorner. The Header timetag displays the timetag of the oldest piece of data from theRLD portions of the rung.

The animation of the contacts and coils in the rung occurs once per second. The rulesfor animating contacts and coils are the same as for RLD rungs.

The Primitive Block Rung passed parameter information is not animated in the RungWindow. The user may select the View:Picture File menu selection orView:Demand Display to watch live updates of the Primitive passed parameters.

Big BlocksIn a Big Block Rung display, the Header information is displayed in the upper leftcorner. The Header timetag displays the operator interface time when the rung wasdisplayed and does not update.

The Big Block Rung passed parameter information is not animated in the RungWindow. The user may select the View:Picture File menu selection orView:Demand Display to watch live updates of the Big Block passed parameters.Big Block automatic parameters can only be viewed using the View:DemandDisplay menu selection.

GEH-6126 Chapter 4 Display Applications • 35

Comment RungsIn a Comment Rung display, the Header information is displayed in the upper leftcorner. The Header timetag displays the operator interface time when the rung wasdisplayed and does not update.

There is no animation of a Comment display.

36 • Chapter 4 Display Applications GEH-6126

Picture File WindowsPicture File Windows are used to display the picture file and animation of the passedparameters 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 HeaderThe 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 isrecommended that users leave the Header visible at all times because the Headercontains valuable process information.

GEH-6126 Chapter 4 Display Applications • 37

Header Timetag

Static DisplayThe Header timetag displays the operator interface time of when the rung wasdisplayed.

Values DisplayThe Header timetag displays the timetag of the oldest piece of data being displayedas 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 ValidData.

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 aregular sequencing segment from the files listed in the MSTR_SEQ.CFG file can beopened with the File:Open menu selection.

The user should open a segment, then navigate to the rung that contains the Primitiveor Big block of interest. He may then select View:Picture File to open a newwindow displaying the Picture File.

Picture Files are initially displayed as static with the passed parameter point namesshown as inputs and outputs to the block. Selecting the View:Values menuselection will cause the parameter point names to be replaced by their current valuesfrom 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 tothe static display with the passed parameter point names shown.

Big Block automatic parameters are not animated in the Picture File Window. Theirvalues can only be viewed using the View:Demand Display menu selection.

Users cannot navigate to other rungs or Picture File Windows from a Picture FileWindow. A Picture File Window will remain open until it is closed from theFile:Close menu command or the unit selection is changed.

Main Frame WindowThis window is the outer window that contains the rung and picture file windows. Ifno control sequencing files or picture files are open, this window is empty.

38 • Chapter 4 Display Applications GEH-6126

Using The Dynamic Rung DisplayThis 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 DisplayThe Dynamic Rung Display may be launched from the command line with thefollowing 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 theDynamic Rung Display or enter dynrung.exe in the Run dialog box in the StartMenu, 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 screenOnly a regular sequencing segment from the files listed in the MSTR_SEQ.CFG filecan be opened with the File:Open menu selection. A unit must be selected beforeany sequencing files can be opened. These files contain the Control Sequence foreach control segment. The user may open more than segment at a time, or havemultiple views of the same segment. Use the Window menu selection to changebetween views.

To navigate within a segment, use the Rung menu selections and toolbar buttons.

Using the Find All functionThe Dynamic Rung Display allows users to find the occurrence of a particular signalanywhere within the control sequencing. The Find All Function will locate signalnames in RLD rungs, signal names as passed parameters, signal names as automaticparameters, and Primitive and Big Block names. It will not locate signals and blocknames used in sub rungs. It does not search Comment Rungs. The Find All Functionis 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, enterthe desired signal or block name. Press Find.

The Find All Results dialog box will show the results of the search in a tabularformat.

GEH-6126 Chapter 4 Display Applications • 39

The first column displays the rung number where the rung was found. Double-clickthe left mouse button on the rung number, or highlight the rung number and click theGoto 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 Closebutton or changes units.

Viewing Tabular DataSelecting Demand Display under the View menu starts a Demand Display showingall of the points from the current rung. It includes RLD elements, Big Block andPrimitive passed parameters, and Big Block automatic parameters. Many users findthis 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.

40 • Chapter 4 Display Applications GEH-6126

Prevote Data Display

PurposeThe HMI Prevote Data Display allows a technician to view logic and analog I/Ovalues before the three independent processors have selected a value through voting.This display is useful for troubleshooting voting mismatches or control I/Odiscrepancies. This display only displays data. It has no control actions.

The Prevote Data Display has a header above a list of voted points. The headerincludes: Site Name, Unit Name, and Current time being sent from the unit. Thelist 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. Allpoints 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 bedisplayed 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 canlocate a point in the list.

Set Font - This dialog box sets the font for both the header and the datalist.

Set Default - This sets the font and column widths back to the systemdefault.

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. Ifthe list is scrolled, the new entries will not be updated until the data isunfrozen.

Help

About Prevote … - Dialog box that shows the revision level of thePrevote Data Display.

GEH-6126 Chapter 4 Display Applications • 41

Command Line DescriptionThe 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 fromthat unit. If no unit is specified on the command line and there is more than one unitin the system, the user will be prompted to select a unit.

Example: G:\EXEC\PVOTE /UNIT:T1

Header TimetagThe Header Timetag displays the timetag of the oldest piece of data being displayedin the data list. Before data has been received, the timetag will be No Valid Data. Ifthe oldest piece of data on the screen is more than five seconds old, the timetag willbe highlighted.

Prevote Data Display

Trip History Log

PurposeThe function of the Trip History Program is to assist in the evaluation of turbinetrip events. This is accomplished by providing a chronological record of relevantdata gathered by the unit control. The data is organized according to post-trip, pre-trip, and alarm categories.

42 • Chapter 4 Display Applications GEH-6126

The Trip History Program allows the user to retrieve data from the unit control andview it on the operator interface. To view the data, the user must select a valid unitand choose the type of historical data to be collected. When the data retrievalcompletes successfully, the results are displayed in a separate viewer window.

Control Signal Database Points (CSDBs) can be defined for collection. Thesedefinitions (64 max.) are made in a single file (HIST_B.SRC). All data in the displayis chronologically indexed according to Mark V Control Panel time and a separatepanel counter (HIS_AGE).

File Type

ViewingThe Trip History Program stores the results of the data retrieval in a read-onlytemporary text file. This file will be displayed using Notepad and then may be savedto another permanent file by using the File:Save As menu option in Notepad.

ConfigurationThe Trip History file for the unit resides in the unit configuration directory and isnamed HIST_B.SRC. It contains the points for collection and retrieval by the TripHistory Program. Information logged in the alarm section of the display is not user-definable. Any text editor may modify the file.

For pre-trip and post-trip screens, timetag (TIME) definitions are listed for thedisplayed Control Data Point information. These designations provide achronological index that ties the exhibited signal information to the unit control time.This register can provide valuable information in terms of determining the sequenceof 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 LogDisplay 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 counterreturns 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_AGEshould always be the first point in the HIST_B.SRC file.

GEH-6126 Chapter 4 Display Applications • 43

;------------------------------------------

; HIST_B.SRC

; HIS_AGE MUST BE THE FIRST POINT!

;; Signal Name; -----------HIS_AGEDWATTTNHFSRL52GXL14HRL14HML14HAL14HSL94XL4L3L2TVL28FDXTTXD_1TTXD_2TTXD_3TTXD_4TTXD_5TTXD_6TTXD_7TTXD_8TTXD_9TTXD_10TTXD_11TTXD_12TTXD_13TTXD_14TTXD_15TTXD_17TTXD_18FQGFQL1FSGCTIMCSGVCPDTTXSPLTTXSP1TTXSP2TTXSP3L4CT

After any modifications, this file should be processed and downloaded as describedin the Configuration section of this manual.

44 • Chapter 4 Display Applications GEH-6126

Trip History Dialog Box Description

Trip History Dialog Box

The Trip History dialog box controls the collection of Trip History data andHistorical log data from the unit control. The user must select a valid unit in theSelect Unit list box and choose the type of historical data to be collected from theradio buttons in the Select Log section. Only one type of data may be collected at atime. There are three categories of information that may be collected:

• Trip History

• Saved Data

• New Data

Trip HistoryTrip History is saved when the turbine trips. For Mark V LM unit controls, the datais 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 DataSaved Data is saved into the control memory when the user collects New Data. Itremains in memory until it is overwritten by New Data or until the control is reset.

New DataNew Data is saved to the control memory when the user collects New Data. The datareflects the most recent control data. The data remains in the control memory asSaved Data until it is overwritten or until the control is reset.

GEH-6126 Chapter 4 Display Applications • 45

Note Collecting New Data will overwrite the Saved Data in the control! On MarkV 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 thedata retrieval fails or is stopped by a user command. When the data retrievalcompletes successfully, the results are displayed in a separate viewer window.

Selecting the Close button exits the Trip History dialog box. Any results currentlybeing viewed will remain in their respective windows.

Viewing ResultsWhen the data retrieval completes successfully, the results are displayed usingNotepad in a separate viewer window. The data is designed to be viewed using afixed pitch font (All characters have the same width). Any word wrapping featuresshould be disabled. The results shown are stored in a read-only temporary file. Tosave the information being displayed, the file must be copied to a permanent filelocation 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 filledwith data only when there has been an actual trip. Otherwise, these records willbe 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.

46 • Chapter 4 Display Applications GEH-6126

The Trip History Data Viewer

Executing the Trip History ProgramThe Trip History Program may be launched from the command line with thefollowing optional argument to quickly bring the display to a desired configuration:

The user may use this command line parameter to customize the startup of theprogram, or enter TRIPDLOG.EXE in the Run dialog box in the Start Menu, orsimply double click on the program icon.

The following example specifies the unit name (/UNIT:) as T1:

G:\EXEC\TRIPDLOG.EXE /UNIT:T1

GEH-6126 Chapter 4 Display Applications • 47

Trip History Log List Viewer

PurposeFor Mark V control systems, the trip history data stored in the unit control is lost ifthe unit control is reset or rebooted making the data unavailable for later review andanalysis. (The trip history data is preserved in the controller memory over a unitcontrol reset or reboot in Mark V LM units.)

In order to preserve this data for Mark V controlled units, a special program isincluded as part of the TCI system so that the trip history data is automaticallycollected and stored on the HMI if it is running when the trip occurs. The last tentrips are stored on the HMI. The Mark V Trip Log Viewer program is provided toaccess 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 areshown 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 viewerwindow.

File TypeThe Mark V Trip Log List Viewer Program reads the previously saved trip text filesstored on the disk to display the valid trip times for selection. This file will bedisplayed using Notepad and then may be saved to another permanent file by usingthe File:Save As menu option in Notepad.

The files are stored in the F:\RUNTIME directory. The automatic collection programmanages 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 anynew trip data.

48 • Chapter 4 Display Applications GEH-6126

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 Historydata stored on the disk. The user must select a valid Mark V unit in the Select Unitlist box . The list of past trips for that unit will be listed below for selection. The filesare 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 bedisplayed.

Selecting the Close button exits the Mark V Trip Log List Viewer dialog box.

Data RetrievalTrip History data retrieval for Mark V controlled units is automatically collected andstored 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 anynew trip data.

Viewing ResultsPlease refer to the Viewing Results section on the Trip History Program for adetailed description of the data format and viewer program.

Executing the Mark V Trip Log List ViewerThe Mark V Trip Log List Viewer may be launched from the command line with thefollowing optional argument to quickly bring the display to a desired configuration:

The user may use this command line parameter to customize the startup of theprogram, or enter tripvwr.exe in the Run dialog box in the Start Menu, or simplydouble click on the program icon.

The following example specifies the unit name (/UNIT:) as T1:

G:\EXEC\TRIPVWR.EXE /UNIT:T1

GEH-6126 Chapter 4 Display Applications • 49

VIEW2

PurposeVIEW2 is a command line utility that collects high-speed turbine data from a Mark Vor Mark V LM controller into a memory buffer. When the buffer fills or thecollection is stopped by the user, the data is formatted into ASCII and saved in a diskfile. The data contains a unit-defined timetag, and the values for each of the pointsrequested. It is commonly used for conducting high-speed data collection during aspecific 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 becollected. A Mark V controller can support data at up to 32 Hz, a Mark V LMcontroller can support data at up to 100 Hz.

BackgroundWhen performing advanced diagnostics, it is often handy to be able to collect data ator even above the frame rate of the controller. It allows for the collection of data asfast 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 collectedcan be stored in a Point List file. The name of the Point List file is then passed to theprogram, preventing having to type in each point name every time the test is run. Thepoint list file is an ASCII file containing a list of point names, one point name perline.

OperationVIEW2 is a command line utility program that is run from a DOS window. If runwith 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 of5mSec intervals, although its internal task schedule rate is at 10mSec. For thatreason, non-zero even values for the /SCAN are recommended for Mark V LM units.

50 • Chapter 4 Display Applications GEH-6126

ExamplesThe 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 256CHARACTERS.

COMMAND FORMAT: VIEW2 [OPTIONS] [@POINTLIST_FILE] OUTPUT_FILE

OPTIONS ARE:

/UNIT=<UNIT> WHERE <UNIT> IS THE UNIT NAME

/PROC=<PROC> WHERE <PROC> IS THE NAME OF THE PROCESSOR (OR CORE)

/SCAN=<INT> WHERE N IS MULTIPLIER OF PROCESSOR SCAN RATE (1=EVERY)

/SAMPLES=<INT> 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>

GEH-6126 Chapter 4 Display Applications • 51

In the following example, two points were collected from a Mark V at the defaultrate. The user hitting a key when the test completed, and 2210 samples had beencollected 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 alsoshown below.

F:\UNIT1>TYPE VIEW2.OUT

## UNIT POINTNAME SCALE

-- ---- ------------ -----

1 T1 FSR %

2 T1 CPD PSI

08-DEC 11:23:10.937 16.02 101.6

08-DEC 11:23:10.968 16.02 101.6

08-DEC 11:23:11.000 16.02 101.6

08-DEC 11:23:11.031 16.02 101.6

08-DEC 11:23:11.062 16.02 101.6

08-DEC 11:23:11.093 16.02 101.6

08-DEC 11:23:11.125 16.02 101.6

08-DEC 11:23:11.156 16.02 101.6

08-DEC 11:23:11.187 16.02 101.6

08-DEC 11:23:11.218 16.02 101.6

08-DEC 11:23:11.250 16.02 101.6

08-DEC 11:23:11.281 16.02 101.6

<<< AND SO ON >>>

52 • Chapter 4 Display Applications GEH-6126

Notes

GEH-6126 Chapter 5 Control • 53

Chapter 5 Control

Introduction

This chapter contains information about programs that can issue control commandsto the unit, or in some way alter the unit control functions. These programs are usedto modify the turbine control behavior by issuing basic control commands includingsetpoints, forcing logic points, and modifying control constants. These operatoractions can have a profound affect on turbine control.

!Caution

Only qualified personnel knowledgeable about turbinecontrol and protection should use the program in thischapter..

:

.

Logic Forcing Display

PurposeThe Logic Forcing Display program allows authorized personnel to force any logicdata 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 thelogic data point. During maintenance or troubleshooting it may be necessary to havethe Control Panel "believe" that a certain valve is in a particular position (asindicated by a position limit switch on the valve). A simple approach is to use theLogic Forcing capability of the Control Panel.

!Warning

Only qualified personnel knowledgeable aboutturbine control and protection should use the LogicForcing functions. Improper use may adversely affectthe control and protective features of the controlsystem.

54 • Chapter 5 Control GEH-6126

The Logic Forcing Display program always shows the currently forced points in theunit. The list of forced points appears on the display at the top of the Data Area whenthe program is displaying a blank Logic Forcing Display file. For existing files, theLogic Forcing Display program displays the forced points at the end of thepointname list in the Data Area. Forced Logic signals already appearing on the LogicForcing Display screen are not duplicated. If the list of points is larger than the LogicForcing Display window, scroll bars appear to show the existence of moreinformation. Forced points reappear if deleted. Unforced points do not disappear,their updated values appear on the next scan of data. The Logic Forcing Displayprogram allows forcing of logic data points for the currently selected unit only.

GEH-6126 Chapter 5 Control • 55

!Caution

A delay occurs prior to forced Logic signalsappearing on the Logic Forcing Display screen.When opening a file, wait a few moments priorto taking any action for all of the forced signalsto appear.

File StructureThe 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 LogicForcing Display program to open, modify, and save these files. Each unit will haveits own point list in the data file. It may be useful to set up several different logicforcing 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 foruse in the Display. Logic Forcing Displays obtain their values for these pointsdirectly from the Data Dictionary.

The Logic Forcing Display Window

56 • Chapter 5 Control GEH-6126

Using the Logic Forcing Display ProgramCreating and editing Logic Forcing Displays require both standard Windows andunique 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 themenu 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 LogicForcing 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 aboutturbine control and protection should force logicsignals. Improper use may adversely affect the controland protective features of the control system.

To force a logic signal in the Logic Forcing Display program, position the cursor onthe line corresponding to the desired logic signal. Click on the pointname field toselect it. The pointname highlights. Select one of the forcing Command Targets onthe right side of the screen. To arm the action, select the desired command target onthe right side of the Logic Forcing Display, either Force To One or Force ToZero. 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 theControl Panel. Signals remain forced until either an Unforce command issues fromthe Logic Forcing Display program or until the Control Panel powers off. SelectingCancel from the Execute Command dialog box cancels the forcing command. Thedefault is Cancel.

GEH-6126 Chapter 5 Control • 57

Note This procedure for confirming a forcing action prevents executing falsecommands.

!Caution

Signals remain forced until an unforce commandissues from the Logic Forcing Display program oruntil the Control Panel powers off. Forced signalsmay cause the unit to function improperly ifforgotten. Take care to unforce all unnecessarysignals prior to running the unit.

Returning the logic signals to their normal state is done either by unforcing all of theforced logic signals at once or by individually unforcing the logic signals. To unforcea single logic signal, select the desired logic signal by double clicking on it. After theline is highlighted, select the Unforce Single Command Target. The ExecuteCommand dialog box appears. Select OK to unforce the signal, Cancel to leavethe 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 forcedlogic signals in the Control Panel. Selecting the Cancel button cancels the unforcingcommand. The default action is Cancel.

!Caution

Selecting UNFORCE ALL unforces ALL of the logicsignals forced at the Control Panel, including anysignals forced from other Logic Forcing Display screens.

Starting the Logic Forcing Display Selecting the Logic Forcing Display icon or typing LFORCE and hitting enterwhile at the command prompt starts the Logic Forcing Display program. Accessingthe Start Menu and Run then entering LFORCE will also start the Logic ForcingDisplay. The Logic Forcing Display program is configurable from the commandprompt. However, configuration arguments are not necessary. Typing LFORCE byitself at the prompt will access the display program. The configuration argumentsare:

/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 unitdisplays the Unit Selection dialog box. Single unit sites ignore this argument anddefault to the single unit.

The Logic Forcing Display program allows files to be passed directly to it from thecommand prompt using the argument /FILE:.

58 • Chapter 5 Control GEH-6126

The /FILE: argument opens the Logic Forcing Display program and loads therequested 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 aninvalid 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 LogicForcing 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-downmenu causes the Open dialog box to display. All the *.TXT files located in thedirectory from which the program was run display, along with the directory anddrive. Selecting the file and the OK button displays the requested Logic ForcingDisplay file. Opening *.TXT files in other directories is possible using the Opendialog box and selecting the drive, directory and filename of the desired file and theOK button. Selecting Cancel in the Open dialog box cancels the opening of a LogicForcing Display file.

Loading a Logic Forcing Display FileThere are three ways to load an existing Logic Forcing Display file. If the LogicForcing Display program is started from the command prompt, add the name of thefile after the Logic Forcing Display program execution command, LFORCE, usingthe /FILE: argument. The extension .TXT must be included with the filename. Forexample,

F:\UNIT1\LFORCE /FILE:FILENAME.TXT,

where filename.TXT would be a Logic Forcing Display filename such asLFORCE2.TXT.

To load an existing Logic Forcing Display file after starting the Logic ForcingDisplay program, select the menu bar option File and the Open command from thedrop-down menu. The Open dialog box displays allowing for selection of the file toload. Selecting the toolbar button with the picture of the open file also displays theOpen dialog box. Selecting a previously viewed file listed at the bottom of the menubar option File opens the file directly.

If the specified file does not appear to be a Logic Forcing data file, the user will beprompted 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, adefault blank file loads To create a new Logic Forcing Display file, select the menubar option File and the New command from the drop-down menu or select thetoolbar button with the blank sheet of paper to display a blank Logic Forcing Displayscreen. The blank Logic Forcing Display screen appears with the Logic ForcingDisplay file title UNTITLED.TXT. This file opens blank each time, but only allowssaving once per directory. Saving subsequent copies of UNTITLED.TXT overwritesthe existing UNTITLED.TXT in the same directory. A new Logic Forcing Display filename should be given to this file when saving using the menu bar option File and theSave As command from the drop-down menu. Any logic point forced in the specificunit will be displayed even if there is no specific file chosen.

Note Saving a Logic Forcing Display file without renaming it overwrites the oldLogic 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.

GEH-6126 Chapter 5 Control • 59

Logic Forcing Display WindowThe Logic Forcing Display operates in a Windows environment. Using the LogicForcing Display program is similar to using other Windows applications. The LogicForcing Display program performs functions selected from drop-down menu optionsfrom the menu bar or buttons on the toolbar. The titlebar displays the filenamecurrently in the Logic Forcing Display program. The horizontal scroll bar allowsviewing of display screens that exceed the window’s boundaries.

The menu bar at the top of the screen incorporates several items common toWindows applications along with special items associated with the Logic ForcingDisplay. A summary of these items and their corresponding functionality is shownbelow :

Logic Forcing Display Menu Items and their Functions

MenuItems

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 editedfiles, prints files, exits the LogicForcing Display program.

EditInsert Blank Line, Modify Line,Delete Line, Set Font, SelectUnit, Find

Inserts, deletes and modifiesdisplay lines. Set fonts and selectsunits.

ViewToolbar, Status Bar Edits window display to show or

remove toolbar and status bar.

Help Index, Using Help, AboutDemand Display

Accesses Help screens.

The toolbar immediately beneath the menu bar corresponds to particular drop-downmenu options. The toolbar buttons allow shortcuts to common menu commands.Placing the cursor over any of these buttons causes a pop-up explanatory textwindow (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 itemcalls up Help information for that item.

Logic Forcing Display Screen WindowThe Logic Forcing Display permits viewing and forcing of Logic signals. Opening awindow showing a Demand Display screen allows for viewing Analog signals andmonitoring system reactions to forcing Logic signals.

The Logic Forcing Display screen is made up of three main regions:

• Header

• List View

• Command Target Area

60 • Chapter 5 Control GEH-6126

Header

The Header contains the unit name, site name, program title and timetag. The Headeris in a non-scrolling region and cannot scroll off the window. The menu bar optionView and the Header command toggles the Header on or off. The Header containsvaluable 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 novalid points, or the Data Area contains valid points but no data has been receivedfrom the unit, then the timetag is No Valid Data. A highlighted Header timetagindicates the oldest piece of data in the Data Area has not been updated for fiveseconds.

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 columnbecomes too narrow to display all of the data, an ellipsis (…) appears on the rightside of the column. The Current Value field is updated once per second from theeach processor. The timetag displayed in the Header reflects the timetag of the oldestpiece of data displayed. Only the points visible on the screen are updated. There is nolimit 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 ForcingDisplay updates only the visible points in the List View.

The Pointname field holds the Control Signal pointname (or synonym) of valid unitdatabase points. Entering the pointname causes the Logic Forcing Display programto 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 allowsentering 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<R> processor. If the pointname is invalid or there is no data for the point in the DataDictionary, this field remains blank. Forced points appear with a “>“ characterpreceding the value.

The Units field displays the Engineering units for valid pointnames. The text appearsexactly as entered in the scale code table file. This field is blank for invalidpointnames, but indicates the units for valid points without data in the DataDictionary.

Command Target Area

The Command Target area appears on the right side of the Logic Forcing Displaywindow. There are four Arm/Execute targets available for the Logic Forcingfunction. These targets are for forcing Logic signals to a state of “1” or “0”, tounforce a single Logic signal or to unforce all forced Logic signals. Arm/Executetargets appear green with black text and require a confirmation prior to sending theforce or unforce signal to the unit.

GEH-6126 Chapter 5 Control • 61

Navigating Within a Logic Forcing Display ScreenThere 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 upand down arrow keys on the keyboard, the page up and page down keys on thekeyboard, or the scroll up/down bar on the window.

Modifying a Pointname or LineHighlight the desired line. Select the menu bar option Edit and the Modify Linecommand from the drop-down menu or choose the Modify Line toolbar button. Thehighlighted pointname field becomes an entry field for the user to type in. The LogicForcing Display program allows entering invalid pointnames to accommodate addingtextual information to the Logic Forcing Display screen. The Processor Value andUnit fields remain blank if an invalid pointname is entered. Selecting File:Savemakes the changes permanent.

Adding and Deleting a Pointname LineThe Logic Forcing Display program allows adding lines at any point in the displayscreen. Highlight the line above the desired insertion point. Select the menu baroption Edit and the Insert Blank Line command from the drop-down menu or selectthe Insert Blank Line toolbar button. The Logic Forcing Display program inserts ablank line below the highlighted line. If the display is empty, Insert Blank Line maybe applied without first hightlighting a location. To modify the line, see theModifying a Line section . Saving the Logic Forcing Display file makes the additionpermanent.

The Logic Forcing Display program allows deleting lines. Highlight the pointnamefield in the line to be deleted. Select the menu bar option Edit and the Delete Linecommand from the drop-down menu or select the Delete Line toolbar button. Theline deletes. Saving the Logic Forcing Display file makes the changes permanent.

Note Deleting lines removes lines permanently. Exiting without saving the file isthe only way to undo the line deletion.

Using the Command TargetsThe Logic Forcing Display Command Targets are Arm/Execute targets.Arm/Execute command targets require confirmation of their action prior toperforming the command. After selecting the Command Target, the ExecuteCommand dialog box appears. Selecting the OK button executes the command.Cancel cancels the command execution. The default action for the ExecuteCommand dialog box is Cancel.

Note This procedure for confirming a forcing action prevents executing falsecommands.

62 • Chapter 5 Control GEH-6126

Printing From the Logic Forcing Display FileThe Print command prints the Logic Forcing Display screen. Only the data currentlydisplayed on the screen prints. Select the menu bar option File and either the Print orthe Print Setup commands from the drop-down menu or select the toolbar buttonwith the picture of the printer. All three of these commands present the Print dialogbox. The Print dialog box allows for the selection of the printer and its properties, thenumber of copies, and what to print. Selecting OK prints the data, selecting Cancelcancels the print command. The Print Preview command previews the page andallows accessing the Print dialog box.

Other OptionsThere are other options available in the Logic Forcing Display program. Selectingthe menu bar option Edit and the Set Font command from the drop-down menupresents the Windows Font dialog box. The Font dialog box allows for selecting thefont used for the Logic Forcing Display screen. The selection applies to the entireDisplay screen including the text defined in the Command Targets.

Selecting the menu bar option Edit and the Select Unit command from the drop-down menu allows for unit selections. In multiple unit sites, any unit may bemonitored from one Logic Forcing Display screen. Select Unit causes the UnitSelection dialog box to appear. The currently selected unit is highlighted. Theavailable units are displayed in alphabetical order. Select the desired unit. Thisoption is not available in single unit sites.

Saving a Logic Forcing Display FileSelecting the menu bar option File and the Save command from the drop-downmenu or selecting the toolbar button with the picture of a disk, saves Logic ForcingDisplay files already having filenames. The file saves in the directory of the originalfile. If the file is new, the Save As dialog box appears requesting a filename. If anew directory is not selected, the Logic Forcing Display program saves the file in thedirectory from which the program was executed. Selecting the OK button aftertyping in a name saves the file using the filename. Saving a file overwrites theprevious 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 withdifferent names, select the menu bar option File and the Save As command from thedrop-down menu. The Save As dialog box appears requesting a new filename for thefile. The Save As dialog box also allows entering different directories. If a newdirectory is not entered, the Logic Forcing Display program saves the new filenamein the directory from which the program was executed. Using an already exitingfilename overwrites the data in the old file with the data from the new file.

Exiting the Logic Forcing Display ProgramSelecting the menu bar option File and the Exit command from the drop-down menuexits the Logic Forcing Display program. The Logic Forcing Display program willrequest whether to save changes to any Logic Forcing Display file prior to exiting.

GEH-6126 Chapter 5 Control • 63

Control Constants Display

PurposeThe HMI Control Constants Display displays the value of each of the controlconstants in the selected unit. All control constants in the selected unit’s datadictionary will be displayed. From this display the user can call up the ControlConstants Adjust Display to change any constants that are adjustable.

The Control Constants Display has a header above a list of control constants. Theheader 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 isadjustable. The icon will be a plus sign if the point is adjustable. The icon will be aquestion mark if the values from the three processors (R, S, and T) do not match. Thequestion mark is also displayed if the value is outside the minimum and maximumvalue. Both the plus sign and the question mark can be displayed at the same time.

Menu StructureFile

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 communicatewith.

Find Point … - Brings up the Find point dialog box. From this the user can locate apoint 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 theControl Constants Display.

64 • Chapter 5 Control GEH-6126

Command Line DescriptionThe Control Constants Display can be invoked from the command line with a unitname. If a valid unit name is specified, the Control Constants Display will be startedwith data from that unit. If no unit is specified on the command line and there ismore than one unit in the system, the user will be prompted to select a unit.

Example: G:\EXEC\CONSTDSP /UNIT:T1

Header TimetagThe header timetag displays the timetag of the oldest piece of data being displayed inthe data list. Before data has been received, the timetag will read “No Valid Data”. Ifthe oldest piece of data on the screen is more than five seconds old, the timetag willbe highlighted.

Changing a Control ConstantThe Control Constants Adjust can be invoked in two ways: from the mouse or thekeyboard. Only Control Constants with a plus next to them can be adjusted. From themouse, double click the constant to be adjusted. From the keyboard, use the cursorkeys to move to the constant to be adjusted and then press the enter key.

Control Constants Display

GEH-6126 Chapter 5 Control • 65

Control Constants Adjust Display

PurposeThe HMI Control Constants Adjust Display allows the user to adjust the value ofany control constant that is adjustable. The display is a dialog application. Thedialog application must not be closed until the ramping of the control constant isfinished. If it is closed, the ramping will stop at the current value. More than oneControl Constant Adjust Display can be active at a time. The Control ConstantAdjust Display can be minimized at any time (including while a point is beingramped).

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 informationwill be displayed in the dialog box: Point Name, Current Point Value (if the unit is aTMR, 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 targetdialog box when it is pushed.

• Start Ramp - Button is green with black text. The Start Ramp button will popup a dialog box asking if you really want to start the ramp. The button will begreen with yellow text when the ramp is in action.

• Stop Ramp - Button is red with black text. This button will immediately stopthe ramp.

• Step Change - Button is green with black text. It will pop up a dialog boxasking if you really want to make the step change. A step change can only bemade when the unit is off line.

• Storage Update - Button is green with black text. It will pop up a dialog boxasking if you really want to save all constants into non-volatile memory.

Demand Display

PurposeMany applications require monitoring several data points at a time. Some of theseapplications may also require the issuing of simple commands. The DemandDisplay program is a tool designed for these applications.

• Demand Displays offer flexible monitoring and control of a variety of points andof multiple units. There are several Demand Display features:

• Demand Displays allow for monitoring point data and issuing commands to theunit(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.

66 • Chapter 5 Control GEH-6126

!Caution

Only qualified personnel knowledgeable about turbinecontrol and protection should create and executecommands. The commands can affect the control state andaction of the unit control.

The Demand Display program contains two types of Display windows:

• Demand Display Menu• Demand Display Data

Demand Display Menu ScreenThe first window is the Demand Display Menu screen. This screen includes a list ofall 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. NewDemand Display screens must be added to the menu for access and the DemandDisplay Menu screen must be saved to make the addition permanent.

Demand Display Data ScreenThe second window is the Demand Display Data screen. The Demand Display Datascreen displays the Demand Displays. See the descriptions in the Demand DisplayWindow section.

The definitions of each screen are associated with a particular unit. That way, unit 1may differ from unit 2 in the names and definitions of the displays. Many differenttypes of units may be accommodated in one Demand Display file.

The Demand Display may access data from and issue commands to Mark V andMark V LM units.

File StructureThe executable directory, G:\EXEC, contains the Demand Display program,demand.exe. Never tamper with this file. The Demand Display program attempts toopen files with .DM2 extensions. For example, DEMAND01.DM2 is a DemandDisplay filename. The file format for these files is binary. Never edit the DemandDisplay files directly. Use the Demand Display program to open, modify, and savethese files. The *.DM2 files contain definitions for all of the Demand Display screenslisted on the Demand Display Menu list for that file.

One binary Demand Display file generally saves several Demand Display screensand one unit may use several Demand Display files. The RUNTIME directory in theF:\ drive is the typical location for these files, however, the Demand Display programsaves new Demand Display files in the directory in which the program was executedunless a different directory is selected. Demand Displays use data dictionary filesfor the point list available for use in the Demand Display screens. Demand Displaysobtain the values for these points directly from the Data Dictionary.

Refer to the Demand Display to Source Conversion Program later in this documentfor information on how to create a text representation of the binary file.

GEH-6126 Chapter 5 Control • 67

Using the Demand Display ProgramCreating and editing Demand Displays require both standard and unique operations,which are performed by using the drop-down menu options from the menuselections. 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 Displayfile

• 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 ProgramSelecting the Demand Display icon or typing DEMAND and hitting enter while at thecommand prompt accesses the Demand Display program. The Demand Display mayalso be started by selecting the Windows Start button then selecting Run. EnteringDEMAND.EXE in the Run dialog box will start the Demand Display. The DemandDisplay program is configurable from the command prompt.

Note Typing DEMAND by itself will access the Demand Display program. Theconfiguration 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

68 • Chapter 5 Control GEH-6126

where the unit name must be a valid unit. Selecting an invalid unit or no unit displaysthe Unit Selection dialog box. Single unit sites ignore this argument and default tothe single unit.

The /FILE: argument executes the Demand Display program and loads a requestedDemand 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 aninvalid path or filename displays an error message box and defaults to a blank,untitled Demand Display file. When entering no filename, the Demand Displayprogram attempts to open the default file F:\RUNTIME\DEMAND01.DM2. An errormessage displays if the program cannot open this file, and the blank Demand Displayfile appears.

The /DISPLAY: argument displays the Demand Display screen in a particular DemandDisplay file. For example:

F:\RUNTIME>DEMAND /FILE:OPERATOR.DM2 /DISPLAY:”LUBE OIL”

The Demand Display program ignores the Demand Display screen name if it isinvalid and displays the menu for the Demand Display file requested. If the DemandDisplay file is invalid, the blank Demand Display file appears.

The /TYPE: argument displays the data screen with points specified at the commandline. For example:

F:\RUNTIME>DEMAND /TYPE:(L1,F4)

The Demand Display program displays the blank Demand Display file if the pointtypes are invalid. If a filename is entered, the point types are ignored.

GEH-6126 Chapter 5 Control • 69

Using multiple arguments configures the Demand Display program morespecifically. 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 asingle 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 fileDEMAND01.DM2, located in the F:\RUNTIME directory. This generic Demand Displayfile can use data from multiple units. Selecting the menu option File:Open from thedrop-down menu displays the Open dialog box. The Open dialog box lists the *.DM2files located in the directory from which the program was executed. Selecting the fileand the OK button displays the requested Demand Display file. Opening *.DM2 filesin 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 boxcancels the opening of a Demand Display file.

Loading Demand Display Files and ScreensThere are three ways to load an existing Demand Display file. If the Demand Displayprogram is started at the command line, the name of the file can be added after theDemand Display execution command, Demand, using the /FILE: argument. Theextension .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 asOPERATOR.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 Opendialog box appears allowing for selection of the file to load. Selecting the toolbarbutton with the picture of the open file also displays the Open dialog box. Selectinga previously viewed file listed at the bottom of the menu option File opens the filedirectly.

If no existing file is specified when executing the Demand Display program, thedefault file DEMAND01.DM2 located in the F:\RUNTIME directory loads. To create anew Demand Display file, select the menu option File:New from the drop-downmenu. A blank Demand Display Menu screen displays with the single menu itemDemand Display. This is the blank Demand Display screen template and requiresrenaming after modification. A new Demand Display file name is required, or thecurrent Demand Display file is rewritten with the new file. Selecting the toolbarbutton with the picture of a blank sheet of paper also displays the blank DemandDisplay list screen.

70 • Chapter 5 Control GEH-6126

Note Saving the Demand Display template screen without a new Demand Displayscreen name causes the Demand Display template to no longer be a blank template.Saving a Demand Display file without renaming it overwrites the Demand Displayfile data with the new Demand Display file data. Exiting either the Demand Displayscreen and/or the Demand Display file without saving loses changes to the file.

The Demand Display WindowThe Demand Display program operates in a Windows environment. Using theDemand Display program is similar to using other Windows applications. TheDemand Display program performs functions selected from drop-down menu optionsfrom the menu or buttons on the toolbar. The titlebar displays the filename currentlyin the Demand Display. The horizontal or vertical scroll bars allow viewing ofdisplay screens that exceed the window’s boundaries.

The menu at the top of the screen incorporates several items common to Windowsapplications along with special items associated with the Demand Display. Asummary of these items and their corresponding functionality are shown.

GEH-6126 Chapter 5 Control • 71

MenuItems

Drop Down ListFunction

Description

File New, Open, Close,Save, Save As, Print,Print Preview, PrintSetup, Filename.DM2,Exit

Selects new or existing files,recently edited files, saves editedfiles, prints files, exits the DemandDisplay program.

Edit Insert Blank Line,Modify Line, DeleteLine, Set Font, SelectUnit, Find

Inserts, deletes and modifiesdisplay lines. Set fonts and selectsunits. All others are disabled.

View Toolbar, Status Bar,Header, Legend, Menu

Edits window display to show orremove toolbar and status bar.Edits Display screen to show orremove Header and Legend.Toggles between Demand DisplayMenu screen and last DemandDisplay screen viewed.

Display Definition, Save, SaveAs

Changes Demand Display screento Point List Demand Display typeor Data Dictionary DemandDisplay type. Changes DemandDisplay Title. Saves DemandDisplay screen.

Help Index, Using Help,About Demand Display

Accesses Help screens.

Demand Display Menu Items and their Functions

The toolbar immediately beneath the menu corresponds to particular drop-downmenu options. The toolbar buttons allow shortcuts to common menu commands.Placing the cursor over any of these buttons causes a pop-up explanatory textwindow (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 itemcalls up Help information for that item.

72 • Chapter 5 Control GEH-6126

Demand Display Menu Screen Example

Demand Display Screens WindowThere are two types of Demand Displays. The Menu screen shows the list ofavailable demand displays for the selected unit. From this screen, the user selects theactual 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 tomeet the users needs. These displays are built from points and commands entered bythe user and are the most common type of display. The Demand Display programallows modifying and saving Point List type Demand Displays for reuse.

GEH-6126 Chapter 5 Control • 73

Demand Display Dictionary Based Using Logics Example

The Data Dictionary type Demand Display is built automatically from pointinformation stored in the Data Dictionary. This information is useful wheninvestigating specific point types and command options. Data Dictionary typeDemand Displays use Dictionary Display Options to configure the Demand Displayscreens. These options select what points and commands are shown on the DemandDisplay screen.

The names and definitions of the Demand Display Screens are defined on a per-unitbasis.

Both Demand Display windows are made up of three main regions:

• Header

• Legend

• Data Area

HeaderThe 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 non-scrolling region and cannot scroll off the window. The menu option View:Headertoggles the Header on or off. The Header contains valuable process information andis recommended to remain visible at all times.

The Header timetag displays the oldest of the displayed pointname timetags in theMark V LM Control Panel. If the Data Area is empty (contains no valid points), orthe Data Area contains valid points but no data has been received from the unit, thenthe timetag is No Valid Data. A highlighted Header timetag indicates that the oldestpiece of data in the Data Area has not been updated for five seconds. The Headertimetag in the Demand Display Menu screen displays the PC time.

74 • Chapter 5 Control GEH-6126

LegendThe Legend displays the column headers for the data shown in the Data Area. TheLegend is in a non-scrolling region and can not scroll off the window. The menuoption View and the Legend command toggles the Legend on or off. The Legend isrecommended to remain visible at all times.

Data AreaThe Data Area is below the Header and Legend. In the Demand Display Menuscreen, the Data Area consists of a list of the Demand Display screens available forviewing. In a Demand Display screen, the Data Area consists of an unlimited list ofpointnames, their values and units. This information is in a tabular format. AnyCommand Targets defined appear on the right side of the window. The user maydefine additional pointnames and Command Targets or remove existing ones fromthe Point List Displays only. Adding and deleting Pointnames and CommandPushbuttons from a Data Dictionary Display is temporary and cannot be saved. TheValue 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 DataArea scroll with the scroll bars. The Demand Display program updates only thevisible points in the Data Area.

The Pointname field holds the control signal pointname (or synonym) of valid unitdatabase points. Entering the pointname causes the Demand Display program to usethe currently selected unit’s data, which is the unit listed in the Header. Entering theunit number with a colon prior to the pointname, as in T2:Pointname, displays datafrom the requested unit.

The Pointname field is 15 characters in length. The Demand Display program allowsentering 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 thedata.

The Value field contains point value information. This field updates once eachsecond, is right justified, and may contain up to ten characters. If the value is largerthan ten characters, ten asterisks appear. Enumerated state values display across boththe Value field and the Units field. The Demand Display program centers theEnumerated state values across these fields and truncates them if they are overseventeen characters long. A blank Value field indicates that the point information isinvalid 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 appearsexactly as entered in the data dictionary file. This field is blank for invalidpointnames, but indicates the units for valid points without data in the DataDictionary. The Units field combines with the Value field to display the text forenumerated points.

The Command Target field is the region to the right of the Units field. UnitCommand Targets for sending control commands to the unit typically reside here.There are three Command Target types:

• Immediate Action

• Arm/Execute

• Analog Setpoint

GEH-6126 Chapter 5 Control • 75

Immediate ActionImmediate Action Command Targets send a command to the control immediatelywithout requiring further action. These targets typically perform an incrementalchange to the control such as Raise or Lower. They are red targets whose text turnsyellow if the feedback logic is supplied and met. Not every Immediate ActionCommand Target uses feedback logic, as it is optional.

Arm/ExecuteArm/Execute Command Targets require an Execute Command to confirm execution.The Execute Command dialog box requests confirmation when the Arm/ExecuteCommand Target is selected. If confirmation or cancellation is not received, theDemand Display defaults to canceling the execution of the command. Selecting OKin the Execute Command dialog box sends the command to the unit. SelectingCancel cancels the command. The Arm/Execute Command Target typically performchanges to the control state, such as Start and Stop. They are green targets whose textturns yellow if the feedback logic is supplied and met. Not every Arm/ExecuteCommand Target uses feedback logic, as it is optional.

Analog SetpointAnalog Setpoint Command Targets change the setpoint value of the specified controlsignal, such as a speed or temperature reference. Selecting an Analog SetpointCommand Target displays the Setpoint dialog box. The Setpoint dialog box requeststhe new value for the control signal and must have a confirmation to perform thechange. After entering the new value, selecting OK confirms the change and the newvalue is sent to the unit. Selecting Cancel cancels the change. The Demand Displaycancels the change if neither confirmation nor cancellation is received. The setpointvalues use the current display engineering units. Analog Setpoints do not usefeedback logics.

Note This procedure for confirming commands prior to sending to the unit preventsexecuting false commands.

Demand Display Setpoint Command Dialog Box Example

Selecting a Demand Display ScreenAfter selecting the Demand Display file, the Demand Display Menu screen is shownin the window. The top of this screen contains the Header with the unit name, sitename, file name and PC timetag. Below the Header is the Legend, and then theDemand Display Menu. The Demand Display Menu lists all of the Demand Displayscreens available in the selected Demand Display file. Clicking on the desiredDemand Display screen menu pick or using the arrow keys on the keyboard andhitting enter when the cursor is next to the desired screen menu pick, displays theDemand Display screen. Using the /DISPLAY: argument at the command line alsoselects a particular Demand Display screen as stated earlier. The names and

76 • Chapter 5 Control GEH-6126

definitions of the Demand Display Screens are defined on a per-unit basis. The menuscreen for each unit may vary and definitions for a given name may vary from unit tounit.

Creating a New Demand Display ScreenAdding new Demand Display screens takes place at the Demand Display Menuscreen. Position the cursor on the line for the desired insertion point for the newmenu item. Select the menu item Edit:Insert Line command from the drop-downmenu. The Demand Display program adds a new, blank Demand Display screentitled Untitled:#, where the # is the number of the new screen. After modifying thenew screen, save the screen with a new name.

Modifying a Demand Display Screen Definition/TypeModifying a Demand Display screen definition takes place at the Demand DisplayMenu 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 DisplayDefinition dialog box appears. The Display Definition dialog box contains threesections. The first section indicates the title of the Demand Display screen. Thesecond section allows for changing the Demand Display screen type. The thirdsection selects what point types to display in a Data Dictionary Display. Use thesecond section to change between a Point List type or a Data Dictionary type.Saving the change makes it permanent.

GEH-6126 Chapter 5 Control • 77

Display Definition Dialog Box

Selecting the menu option Display:Definition from the drop-down menu from theDemand Display screen also allows modifying the Display Definition. The DisplayDefinition dialog box appears to allow changes of the Demand Display screendefinition type. Saving the change makes it permanent.

Changing a Display TitleSelecting the menu option Display:Definition on the drop-down menu presents theDisplay Definition dialog box. Use the first section, the Display Title box, to changethe Demand Display screen title. Placing the cursor in this box and typing in a newname changes the name of the Demand Display screen. The Display Title can be upto 25 characters long. Duplicate title names are possible, but not recommended.Display Titles should never be empty or all blanks. The use of ellipsis (.....) placedbefore the title of a Data Dictionary type Demand Display is recommended todifferentiate it from a Point List type Demand Display. Selecting the Save or SaveAs command from the drop-down menu of the Display menu is required to makethe Display Title change permanent. Save As by itself does not change the oldDisplay Title to the new Display title, as it inserts the Demand Display screen to thebottom of the Demand Display Menu list with the new Display Title. If no newDisplay Title is entered, it inserts a copy of the Demand Display screen with thesame Display Title as the old Demand Display screen at the bottom of the DemandDisplay Menu list. The Demand Display program requests whether the Display Titleshould be saved if the Demand Display Menu screen is accessed or the programexited without saving.

NavigatingThere are several ways to navigate within the Demand Display program. To viewmenu items or pointnames that are off the bottom or top of the screen, use the up anddown 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 windowon the sides use the scroll left/right bar on the window.

Adding/Deleting a Pointname or LineAdding lines is possible in either Demand Display screen type, but saving is onlyallowed in a Point List type Demand Display screen. Position the cursor on the linebelow the desired addition location. Selecting the menu option Edit:Insert BlankLine from the drop-down menu inserts a blank line above the selected line. Tomodify the line, see the Modifying a Point Name or Line section below. Saving boththe Demand Display screen and Demand Display file makes the changes permanent.

Deleting lines is possible in either Demand Display screen type, but saving is onlyallowed in a Point List type Demand Display screen. Position the cursor on thedesired line. Selecting the menu option Edit:Delete Line from the drop-down menudeletes the line. If the line corresponds to the first line of a Command Target, thetarget deletes. Saving the Demand Display screen and the Demand Display filemakes the changes permanent.

Modifying a Pointname or LineModifying lines is possible in either Demand Display screen type, but saving is onlyallowed in the Point List type Demand Display screen. Position the cursor on thedesired line. Selecting the menu option Edit:Modify Line from the drop down menudisplays the Point Name dialog box. Entering the desired point name and selectingOK changes the information on the line or adds information to a blank line. TheCancel button cancels any changes. The Define Command button appears when it is

78 • Chapter 5 Control GEH-6126

possible to add or modify a Command Target associated with that line. Saving theDemand Display screen and Demand Display file makes the changes permanent.

Modify Line Dialog Box

Adding a Command TargetAdding Command Targets is possible in either Demand Display screen type, butsaving is only allowed in the Point List type Demand Display screen. Position thecursor on the line that corresponds to the Command Target. One blank line betweentargets in the Target field is required. Select the menu option Edit:Modify Line fromthe drop-down menu. The Point Name dialog box appears. Enter the desired pointname if adding to a blank line. Typically, the point name on the line corresponding tothe 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 aCommand Target and its feedback (optional). Command Targets require definition ofseveral parameters: Button text, unit command pointname, button type, unitcommand value of the point and value type, and feedback signal pointname andsense.

The button text should indicate the Command Target’s action. Enter the button textin the two fields of the button text section. The Command Targets permit two lines

GEH-6126 Chapter 5 Control • 79

of text of up to eight characters on a line. The Demand Display program centers theCommand Target text with the button. Button text appears black and turns yellow ifthe associated feedback logic is supplied and sense met.

The unit command pointname is the control signal pointname that receives thetargets value. Enter the pointname of the unit command in the field for thepointname. 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 thebutton type. Refer to the earlier Demand Display screen section for a description ofthe Command Target types.

The value field holds the value the Command target sends to the unit. There are threeguidelines correlating to the type of pointnames used. A Pushbutton’s value is thenumber 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 Setpointsrequire a value in the engineering units specified for the command signal point.

80 • Chapter 5 Control GEH-6126

The value type governs how the Command Target sends the value to the unit. Thereare 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 AnalogSetpoints. An increment (+) adds the value in the value field to the current value ofan Analog Setpoint and sends it to the unit. Decrement (-) subtracts the value in thevalue 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. ImmediateAction and Arm/Execute button types can use feedback signals. Analog Setpointbutton types cannot. The pointname field is for the control signal pointname of thefeedback signal. These can only be logic point types. The Sense field can invert thesense of the feedback signal.

After completing all of the fields in the Command Definition dialog box, theentries must be confirmed. There are five buttons in the Command Definition dialogbox referring to confirmation. The Check Form button checks the commanddefinition entries for consistency and errors. The OK saves any changes and createsthe target. Help initiates the help data for this dialog box. Cancel cancels anychanges to the command definition. Delete resets the Command Definition anddestroys the Command Target.

Deleting a Command TargetThere are two ways to delete Command Targets: deleting the target itself or deletingthe entire line, pointname and target. To delete the Command target only, positionthe cursor on the pointname in the line corresponding to the top button line of thetarget. Select the menu option Edit:Modify Line from the drop-down menu. ThePoint Name dialog box appears. Select the Define Command button. The CommandDefinition dialog box appears. Selecting Delete resets the Command Definition anddeletes the Command Target.

To delete the associated pointname and the Command Target, position the cursor onthe pointname in the line corresponding to the top button line of the target. Select themenu option Edit:Delete Line from the drop-down menu deletes the point name andthe Command Target.

Modifying a Command TargetIt is possible to modify Command Targets. Position the cursor on the linecorresponding to the top button line of the desired Command Target. Selecting themenu option Edit:Modify Line from the drop-down menu displays the Point Namedialog box. Selecting the Define Command button from the Point Name dialog boxdisplays the Command Definition dialog box. Modify the definition as stated in theAdding a Command Target section above.

Using a Command TargetPositioning the cursor on the Command Target and selecting it activates theCommand Targets. Immediate Action Command Targets are red and activating themimmediately sends the command to the unit.

Arm/Execute Command Targets are green. Activating them displays the ExecuteCommand dialog box to confirm execution. The default action of this dialog box isCancel. OK confirms the execution and the command is then sent to the unit. Cancelcancels the command.

GEH-6126 Chapter 5 Control • 81

Analog Setpoint Command Targets are gray, and when activated, the Setpoint dialogbox appears. The Setpoint dialog box requests a value for the Analog Setpoint andalso to confirm execution. Selecting OK confirms the command and the value is sentto the unit. Cancel cancels the command. The default action is Cancel.

PrintingThe Print command prints the Demand Display screens. Only the data currentlydisplayed in the Demand Display screen window prints. Select the menu optionFile:Print or the Print Setup from the drop-down menu or select the toolbar buttonwith the printer. All three of these commands present the Print dialog box. The Printdialog box allows for the selection of the printer and its properties, the number ofcopies to print, and what to print.

Selecting OK prints the data, selecting Cancel cancels the print command. The PrintPreview command previews the page and allows access to the Print dialog box.

Other OptionsThere are several other options available in the Demand Display program. Selectingthe menu option Edit:Set Font from the drop-down menu presents the WindowsFont dialog box. The Font dialog box allows for selecting the font and color of theDemand Display screen. The selection applies to the entire Demand Display screenexcept for the Command Targets whose colors are predefined.

Selecting the menu option Edit:Select Unit from the drop-down menu allows forunit selections. In multiple unit sites, any unit may be monitored from one DemandDisplay screen. Select Unit displays the Unit Selection dialog box. The currentlyselected unit is highlighted. The available units display in alphabetical order. Selectthe desired unit. This option is not available in single unit sites.

Selecting the menu option View:Menu from the drop-down menu toggles betweenthe menu and the most recently viewed Demand Display screen. Toggling to theDemand Display Menu screen from a Demand Display screen loses any changes ifthe Demand Display screen is not saved. The Demand Display program asks whetheror not to save the Demand Display screen. Selecting Yes saves the Demand Displayscreen, No toggles to the Demand Display Menu screen without saving. SelectingMenu from the Demand Display Menu screen displays the most recently viewedDemand Display screen.

Saving Demand Display Screens and Demand Display FilesDemand Display screens and Demand Display files are saved separately. To save aDemand Display screen, select the menu option Display:Save or Save As from thedrop-down menu. The Save command saves the Demand Display screen changes tothe same Demand Display screen title. The Save As command saves the DemandDisplay screen changes to a new Demand Display screen title on the DemandDisplay Menu. Selecting Save As presents the Display Definition dialog box. If anew Demand Display screen title is not typed in here, another Demand Displayscreen with the same name is added to the bottom of the Demand Display Menu. It isrecommended to re-title edited Demand Display screens if the original is kept. If theDemand Display program is exited prior to saving changes to Demand Displayscreens, the program asks whether the Demand Display screen should be saved priorto exiting. Selecting Yes saves the Demand Display screen, No exits the DemandDisplay screen without saving.

82 • Chapter 5 Control GEH-6126

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 thedrop-down menu to save the changes to the current Demand Display file. Selectingthe Save As command displays the Save As dialog box allowing for the directoryand new file name to be selected. Exiting the Demand Display program prior tosaving changes causes the program to ask whether or not to save the DemandDisplay file. Selecting Yes saves the file, No exits the Demand Display programwithout saving.

Copying Demand Display Screen DefinitionsThe names and definitions of the Demand Display Screens are defined on a per-unitbasis. On locations where there are duplicate units or units that share similarfunctions, it may be useful to Copy a Demand Display Screen from one unit toanother. To do this, open the desired Demand Display Screen. Now, select the Editmenu item. Select Unit and select the new unit. Select the DISPLAY menu item Saveand the Screen is now saved to the new unit. To make this change permanent, selectFile and Save or Save As. Otherwise, the change will be lost when the DemandDisplay program closes.

Exiting the Demand Display ProgramSelecting the menu option File:Exit from the drop-down menu exits the DemandDisplay program. If changes were made to the Demand Display file without saving,the Demand Display program asks whether to save the changes. Selecting Yes savesthe changes to the current Display screens and Demand Display file, No exits theprogram without saving.

Alarm Logger Control

PurposeSeveral classes of turbine control actions may be automatically logged to a hard copyprinter. The Alarm Logger Program allows the user to select the types of alarmsand events to output to the printer. The user must select from four categories ofinformation 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 AlarmPrinter are covered later in this manual.

GEH-6126 Chapter 5 Control • 83

The Alarm Logger Control Dialog Box

Using the Alarm Logger Dialog BoxThe Alarm Logger Control dialog box controls the output of the Alarm Logger. Theuser must make the following decisions when completing the Alarm Logger dialogbox:

• 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 PrintedThere 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 LoggerProgram to enable printing for that information type for that unit. Please note that theconfiguration of the individual points is not a function of the Alarm Logger Control.

84 • Chapter 5 Control GEH-6126

Select UnitEach of the categories of information may be selected on a unit basis. The unit maybe 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 unitto all units.

• Flush Button The Flush button deletes all pending alarm print jobs for ALLunits from the Alarm Printer. The Flush button takes immediate action and doesnot require the OK button to be activated.

• Save Settings Any changes made to the Alarm Logger settings are savedONLY if the user selects OK when leaving the Alarm Logger Control dialogbox. Leaving the dialog box by any other method, such as selecting Close orCancel, causes the changes NOT to be saved.

• File Type The Alarm Logger Control does not access any files when making itschanges. Instead, it writes its output to a special section of global memory that isthen read by the Alarm Log program which writes the alarms and events to thealarm printer.

Executing the Alarm Logger ControlThe Alarm Logger Control may be launched from the command line with thefollowing optional argument to quickly bring the display to a desired configuration:

The user may use this command line parameter to customize the startup of theprogram, or enter logger.exe in the Run dialog box in the Start Menu or simplydouble click on the program icon.

The following example specifies the unit name (/UNIT:) as T1:

G:\EXEC\LOGGER.EXE /UNIT:T1

GEH-6126 Chapter 5 Control • 85

Command Line DescriptionThe Control Constants Adjust Display can be invoked from the command line with aPointname. If no pointname is specified, then a dialog box will appear to enter apoint. The format of the command line argument will be:

/POINT:<UNIT>:<POINT NAME>

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 TimetagThe 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 oldestpiece of data on the screen is more than five seconds old, the timetag will behighlighted.

Control Constants Adjust Display

Hold ListThe Hold List is required for the HMI to support Mark V Large and Medium SteamTurbine Controls on systems that have ATS, Automatic Turbine Startup. The ATScode resides in ROM in the <C> processor only. ATS is active only when theAutomatic mode has been selected. Its purpose is to set speed control targets andvalve positions based on various inputs - steam temperatures and pressures,calculated valve stresses, turbine rotor stresses, and turbine shell stresses, metaltemperatures, speed and operating mode. Turbine operating conditions may cause ahold which prevents ATS from setting the speed or load target to a higher value. Inthe HMI processor, the Hold List Display provides the operator a way to view thecurrent points on the Hold List and to override any or all hold points if he desired.

86 • Chapter 5 Control GEH-6126

Overriding a hold allows the ATS to advance its targets as operating conditionspermit.

Hold List PointsThe points for the Hold list should be listed in the HMI unit configuration directoryF:\UNITN\TOTT_B.SRC file. The list can hold 64 points, maximum. The pointsshould be either Alarms or Events so that they will appear on the Alarm and EventLogger. This file must be compiled by the table compiler, G:\EXEC\TABLE_C.EXE.The point list is then downloaded to <C> and <D> processors with the EEPROMdownloader, G:\EXEC\EEPROM.EXE. Select TOTT for the section to download.The processors should be rebooted to make any list changes active.

Hold List ProgramsThe Hold List is maintained in the <C> and <D> processors by programs in PROM.The Hold List receiver in the HMI is automatically started by the TCI systemservice. 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 toallow only the holds from a given unit on the display and to exclude holds from theregular alarm list. (Of course, the user can change this at any time.)

Hold List RulesThe 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 ALARMin the state field.

• A hold point whose state is a dropped out (0) will display the textNORMAL in the state field.

• A point that picks up and drops out and has been acknowledged isremoved from the Hold List display.

• A picked up hold point may be overridden by an operator using theLock command button.

• Overridden points will display Locked as the first part of their longname 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 longname of each hold point in the list.

• The text Hold will appear in the drop number field and the CSDBoffset will be in the reference field. The reference field is typically notdisplayed.

• The Hold List program in <C>, not <D>, will output a logic signalindicating that there are one or more active holds that have not beenoverridden. This point is named L68DW_ATS_HL. ATS and the turbinecontrol use this signal to set speed, load, and valve position targets.

GEH-6126 Chapter 5 Control • 87

Manual Sync Object

The Manual Sync Object is an OLE object to be used in CIMPLICITY to make ascreen similar to the Synchronizing Display in the MKV <I>. The object contains allthe fields that need to be updated at a fast rate. All data in the object is updated at 16Hz. TCI must be running in the computer that is displaying the object. The objectuses BMS and other TCI resources to get its data and send the commands. Theobject consists of five parts:

• The middle of the object contains the synchroscope. It will be configured usingthe Scope tab on the Properties page.

• The top left of the object displays the breaker close times. It will be configuredusing the Breaker tab on the Properties page.

• The right of the object displays the permissives needed to close the breaker. Itwill be configured using the Permissives tab on the Properties page.

• The center left of the object contains the Breaker Trip and Breaker Closebuttons. 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 updatedquickly. These will be configured using the Values tab on the Properties page.

88 • Chapter 5 Control GEH-6126

Scope Tab

The Scope tab is used to configure the Synchroscope part of the object. It has 7fields to fill in:

• Unit - This field must be filled with the unit name. You can only pick Mark Vand 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 lessthan the Maximum slip frequency.

• Slip Freq. Pointname - This is the signal that will be used to determine thecurrent slip frequency. If this frequency is greater than the maximum slipfrequency, 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 shouldappear on the scope. They are entered in degrees separated by spaces.

• Sync Check Pointname (optional) - This signal will be used to change thecolor of the pointer. If this signal is not defined, the pointer will always bedisplayed 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. Itwill 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 Chapter 5 Control • 89

Breaker Tab

The Breaker tab is used to configure the breaker close times part of the object. It has6 fields to fill in:

• TCEA Socket - This entry defines the BMS socket that should be used forobtaining the TCEA diagnostic message. This message is how the object getsthe breaker close times. This value is usually 15.

• TCEA IO Processor - This entry defines the I/O Processor that is used forobtaining the TCEA diagnostic message. This value is usually 2F HEX.

• TCEA Diagnostic Message type - This entry defines the type for a diagnosticmessage. This value is usually 5.

• Nominal Close Time message offset - This entry defines the offset into thediagnostic message to the nominal close time value. This value is usually 40.

• Learned Close Time message offset - This entry defines the offset into thediagnostic message to the learned close time value. This value is usually 42.

• Actual Close Time message offset - This entry defines the offset into thediagnostic message to the actual close time value. This value is usually 48.

90 • Chapter 5 Control GEH-6126

Permissives Tab

The Permissives tab is used to configure the Permissives part of the object. The listbox has 3 columns. The Sense column determines when a green or red box isdisplayed by the variable. If the value equals the sense value, a green box isdisplayed. A red box is displayed otherwise. When a red box is displayed, a dash isdisplayed next to it. The Pointname column is the logic signal that will be used. TheID String column is the string that will be displayed next to the box. Thepermissives will appear in the object in the same order they are displayed in the listbox.

The Add button is used the add entries to the list. Entries are always added to theend of the list. The Delete button will delete the currently selected entry. The Editbutton will edit the currently selected entry. The Up button will move the currentlyselected entry up one row in the list box. The Down button will move the currentlyselected entry down one row in the list box.

GEH-6126 Chapter 5 Control • 91

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 BreakerClose pushbutton command to. If this field is not filled in, the button will notappear. The duration of the pushbutton command will be set in the durationbox.

• Breaker Trip Pointname (optional) - This is the signal to send the Breaker Trippushbutton 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 breakerclose or trip command will be sent on the release of the command button. The donebutton is used to exit the dialog box.

92 • Chapter 5 Control GEH-6126

Values Tab

The Values tab is used to configure the Values part of the object. The list box has 3columns. The ValueSize column sets the number of digits to use to display thevalue. The number of decimal places and the units string specified in the scale codewill 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 willappear 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 thecurrently selected entry up one row in the list box, and the Down button moves itdown one row.

Colors Tab

The Colors tab is used to change some of the colors in the object. BackgroundColor will set the background color of the object. Foreground Color will set thecolor of the text in the object.

GEH-6126 Chapter 6 Configuration • 93

Chapter 6 Configuration

Introduction

This chapter describes the files, tools, and processes available to personnel formodifying the Unit Control and HMI configuration. The configuration of the HMI isdivided 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 withfriendly, easy to use operator screens providing accurate data display and unitcontrol.

!Caution

Only trained, experienced personnel should be involvedin modifying any aspect of configuration on the HMI.Improper alterations to any configuration on the HMIcan affect unit function, unit control, accuracy of datadisplayed, and unit and external communicationsreliability.

Unit Control Configuration deals with the files and tools available for modifyingthe Unit Control Configuration. These changes may include:

• 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

94 • Chapter 6 Configuration GEH-6126

This manual is intended as a reference to the specific HMI features available to theuser. 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 thatbuilds the files and runs the processes that allow communication with the unit controlpanel. 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 communicatewith the unit.

• Programs for Remote Control, MODBUS and GSM.

CIMPLICITY Configuration in this manual is limited to creation and modificationof the CIMPLICITY point database including points for display, as well as alarms,events, and hold points. The details of creating and modifying CIMPLICITYProjects and View screens and other configuration of CIMPLICITY features are notdescribed in this manual. Please refer to the CIMPLICITY documentation in GFK1180 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 unitcontrol data and send commands to control the unit. These systems must worktogether. The HMI is delivered pre-configured from the factory with the properversions of software. Upgrades to any portion of the HMI software must coordinatedwith the factory in order to insure proper HMI function. The upgrade of any singlecomponent could render the system inoperable. Always check with the factory first.

GEH-6126 Chapter 6 Configuration • 95

!Caution

Software upgrades to the HMI must be coordinated with thefactory. Only qualified personnel should make these changes.Installing the wrong version of software could render the HMIinoperable.

!Caution

Only trained, experienced personnel should be involved inmodifying any aspect of configuration on the HMI. Improperalterations to any configuration on the HMI can affect unitfunction, unit control, accuracy of data displayed, and unitand external communications reliability.

When the Windows NT, HMI, Unit Control and CIMPLICITY systems are properlyconfigured, they work together to provide safe, reliable, and efficient unit operationwith friendly, easy to use operator screens providing accurate data display and unitcontrol.

This section describes the HMI configuration files, tools, and processes available formodifying its configuration. The configuration of the HMI is divided into theseareas:

• 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 onuser accounts. Windows NT is highly flexible, very powerful operating system witha 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 computerresources, which may affect HMI performance. The intended purpose of the HMI isto display unit control data and send user commands to the control.

96 • Chapter 6 Configuration GEH-6126

TCI is the product that builds the files and runs the processes that allowcommunication 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 communicatewith the unit.

• Programs for Remote Control, MODBUS and GSM.

• TCI forms the core of the HMI system and its configuration is critical to properHMI function. The sections in this manual describe how to configure TCI.

CIMPLICITY Bridge is the communication path within the HMI between the TCIand CIMPLICITY. It puts unit control data in the CIMPLICITY database, sendsoperator commands from the HMI to the unit control, and manages the alarm andevent messages between the unit control and CIMPLICITY. There is noconfiguration for the CIMPLICITY Bridge other than to configure the CIMPLICITYpoint database and alarms. These topics are covered under CIMPLICITYconfiguration.

CIMPLICITY Configuration in this manual is limited to creation and modificationof the CIMPLICITY point database including points for display, as well as alarms,events, and hold points. The details of creating and modifying CIMPLICITYProjects and View screens and other configuration of CIMPLICITY features are notdescribed in this manual. Please refer to the CIMPLICITY documentation in GFK1180 for more information on CIMPLICITY.

TCI Configuration

TCI is the software package that provides the Turbine Control Interface. Thissoftware 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 istypically set to start automatically when the computer is restarted, no user needs tobe logged in for the TCI service to be running.

GEH-6126 Chapter 6 Configuration • 97

TCI Registry Information - Control Panel AppletAs a System Service, TCI uses the Windows NT Registry to save configurationinformation. TCI provides a Control Panel Applet (Start - Settings - Control Panel- TCI) for changing its configuration values in the Registry. Available optionsinclude:

Auto Login: This section informs the Windows NT Operating System that when thesystem is booted it should automatically log in the specified user. This prevents auser from having to log in when the computer is started.

Note If the computer is set for Automatic Login, you can disable this feature byholding down the Shift key on the keyboard when the desktop background appearsduring the Windows NT startup process.

TCI Site: This section informs TCI about the options it requires to find and use thesite configuration files. TCI defines the pseudo drive "F:" to point to the TCI siteconfiguration files, and this section informs TCI where those files exist. Other siteoptions, such as whether to run in English, Metric, or Custom engineering units, arealso set here.

Time Sync: This section informs TCI what type of hardware exists for acquiring thecurrent time. (This function is typically used when the HMI is requested to becomea time master on the StageLink.) This setting must match the hardware in the PCthat is being configured. The options for "Time Acquisition Hardware" include:

None: The TCI service will be told that the current time is not available fordissemination.

Low Resolution: The TCI service will be allowed to fetch the normal PC clock as alow-resolution time source.

High Resolution: The TCI service will expect a high resolution time board installedin this PC. If this option is selected the High Resolution Time Card section must befilled out defining which time card is installed and its configuration parameters.

ARCNET: This section informs TCI how to communicate with an installedARCNET card. The ARCNET card is the interface to the StageLink. The settings inthis section must match the settings on the actual ARCNET card.

98 • Chapter 6 Configuration GEH-6126

TCI Configuration FilesThe configuration files for TCI are stored on the pseudo drive "F:". The top level ofthe F: drive contains the files that configure the TCI System Service for a particularsite. Included here is information on where to find the directories that contain theunit configuration files.

Two files are always required for TCI to run, F:\CONFIG.DAT andF:\TIMEZONE.DAT. A number of optional configuration files are only required if theoption they control is in use at this site.

F:\CONFIG.DATF:\CONFIG.DAT is the primary configuration file for the TCI System Service. Thisfile 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.DATF:\TIMEZONE.DAT is used to convert times from UTC to local time. The WindowsNT operating system keeps track of the current conversion, but this file is used byTCI to be able to convert times from historical data correctly.

Optional Configuration FilesOther TCI configuration files are only required if the option that they control is inuse at this site. These potential files include:

F:\IO_PORTS.DAT: This optional data file is used if the TCI System Serviceis to take over any of the RS-232 ports on the computer. This file indicates whichcommunication ports should be used, what the port settings are supposed to be (baudrate, parity…) and what function the port is used for. Functions include MODBUSMaster and MODBUS Slave.

F:\TIMESYNC.DAT: This optional data file is used if the HMI is to be a timemaster on the StageLink. It is also used if you wish this HMI to synchronize itsclock to an external time source, be it a High Resolution Time Card or a time masteron the StageLink.

F:\MODB_FWD.DAT: This optional data file is only used if the MODBUSSlave over Ethernet function is being used and the MODBUS master does notsupport sending a slave address as part of the Ethernet message. This file remaps theindividual slave register sets into one large register set, allowing information frommultiple slaves to be treated as information from one large slave. (This function isonly supported for the MODBUS over Ethernet link, not for RS-232 links.)

GEH-6126 Chapter 6 Configuration • 99

F:\AT_START.DAT: This file defines a set of commands that are run afterTCI is started. It is used to start any site-specific programs that need to be startedafter TCI is started.

F:\AT_STOP.DAT: This file defines a set of commands that are run beforeTCI is shut down. It is normally used to stop any site-specific programs that need tobe stopped before TCI is stopped.

TCI Font LoadingThere are two fonts that are distributed with the TCI Product Code. These areregular 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 fordrawing line and box graphics in a non-proportional spaced font. This is used forprinting out CSP documents, and is used by the Dynamic Rung Display forpresenting information.

GELOF___.TTF: This TrueType font includes GE logos that are used onvarious displays.

TCI Print QueuesTCI has two optional programs that provide a real time printout of information to aprinter. To activate these real time printers, special print queues are created. (If theprint queues are not created, TCI simply assumes that the function is not desired atthis site.)

Real time print queues are typically directed to local printers that are dot matrixprinters. These dot matrix printers print each entry immediately, they do not buffer apage 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" isdefined, TCI will format and send to that printer a real time report of the digitalexception messages from the Turbine Control Panel. These exception messagesinclude: Process Alarms, Diagnostic Alarms, Events, and SOE’s. The LOGGERprogram can be used to fine tune which type of messages are sent to the printer on aper-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 generatedby the Turbine Control Panel.

100 • Chapter 6 Configuration GEH-6126

EPA Log

EPA LoggerThe EPA Logger will provide access to the EPA data that has been configured in theMark V controller. To enable the EPA Logger on the HMI, configure a printer inWindow NT and name it "EPA Printer" and add the following entry toF:\CONFIG.DAT in the Options section:

Options

EPA_LOG=Yes

The EPA logger will periodically poll any units that have EPA logging enabled andreports will be printed as determined by the unit. As this capability is not present inMark VI or Mark V LM controllers, the EPA Logger will only poll Mark Vcontrollers.

The EPA Logger provides access to current EPA data from the controller for use onCIMPLICITY displays.

The printer that you configure as "EPA Printer" should be different from the printerconfigured for alarm logging.

A properly configured demand display should provide enough information to verifythe operation of the EPA logger. A description of the inputs, outputs and operation ofthe EPA function in the controller can be found in the EPALOG.PIC file in your unitdirectory on the F: drive. This feature is also shown in the following twoillustrations.

GEH-6126 Chapter 6 Configuration • 101

EPALOG, <C> DCC Portion

EPALOG -- Wet Low NOx EPA Logger

L3WQIN clear

L83WQL3N

LWLX4MIN

LWLXHRHourly Average:Calculated aftereach 60 pointshave been stored.

clear data

time

clear

MinuteAverages:Stored in 60point circular file

clear data

time

clear

<C> DCC

List of inputsfromEPA_B.SRC

SS

Four Minute Alarm:If WXC>WXJ forfour consecutiveminute avg. thenset LWLX4MIN=1

enable

Hourly Alarm:If WXC>WXJ forhourly averagethen setLWLXHR=1

enable

Calculateaverage of eachinput everyminute based ononce per secondsampling

enable

102 • Chapter 6 Configuration GEH-6126

EPALOG, <I> Processor Portion

EPA Data Display

Defining EPA Data PointsTo define Mark V Control Data Points for the EPA screen, the user must modifythe 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.

EPALOG -- Wet Low NOx EPA Logger

LWLXHR

IO_PORTS.DAT

Enable output toprinter assigned toEPA$PRINTvariable

enable

CONFIG.DAT

IfEPA_LOG=YEScollect data from<C> and enableoutputs

minute average

hourly average

enable

<I> Processor

Output to printer:

All minuteaverages fromhourly averagecalculation

enable

Output to printeronce an hour:

hourly average

enable

Output todisplay:hourly andminuteaverages

AND

GEH-6126 Chapter 6 Configuration • 103

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 thisfile.: The header is automatically created when the program is run.;; SIGNAL NAME; -----------

DWATTCTIMTTXMWXJWXCFQGFQLCMHUM;END OF FILE

Although any valid Mark V data point may be defined for the EPA Display, it isrequired that both WXJ (ACTUAL FUEL/WATER-STEAM RATIO) and WXC(required FUEL/WATER-STEAM RATIO) control data points be included in allEPA displays. In addition, it is required that the points WXJ and WXC be defined forthe 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 becompiled and downloaded to the <C> processor.

104 • Chapter 6 Configuration GEH-6126

Turbine Control Maintenance IconsThe User Icon Program, UICON.EXE, automatically creates the Desktop and StartMenu Icons needed for the major tasks required for both HMI and unit configurationand control. This allows maintenance personnel quick access from the Desktop andStart Menu. Users may customize the menu selections by adding or deleting itemsthrough 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. Theprogram can rebuild the entire Turbine Control Maintenance section, and builddesktop Icons.

GEH-6126 Chapter 6 Configuration • 105

Rebuild Start Menu Dialog Box

The Rebuild Start Menu dialog box appears when the program is started. There isan option to remove the existing definitions then rebuild. This option will delete allicons and folders in the Turbine Control Maintenance section, including any usercreated custom selections, then replace them with the TCI standard set. Do not usethis option to retain user customization. The default option is not to remove theexisting definitions.

The second option adds the unit configuration icons to the desktop. The default isnot to create desktop icons. Removal of desktop unit configuration icons can bedone items through use of the Windows NT user interface features.

StagelinkCommunication between the operator interface(s) (HMI) and the Mark V panel(s) iscarried out by means of the control system’s Stage Link. In its simplestconfiguration, the Stage Link connects one Mark V turbine control panel to a singleHMI (or node) across a single segment (see segment definition below). Thiscommunication topology may however be expanded to accommodate multiple HMIsand/or multiple panels. For example, a single operator interface can be configured toissue commands to and receive turbine data from up to eight Mark V gas/steamturbine controls. In addition, multiple HMIs may be attached to the Stage Link —each HMI communicating with multiple control panels. In this way, the Stage Linkprovides enhanced flexibility for establishing effective communications, which canbe tailored to individual site needs.

The Stage Link was designed specifically to address turbine control needs such asdownloading or uploading software between the Mark V and the HMI, issuingcommands, 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 communicationlink availability and/or enhance network distances.

106 • Chapter 6 Configuration GEH-6126

Terms of ReferenceNODE: Any device connected to the Stage Link system that has a valid address; aTCP core, which for a Mark V is a <C> core (communications processor), or a <D>core (backup communications processor), and for a Mark V LM is a <R> core(communications processor); or an HMI.Where a specific core (communications processor) is meant, like <C>, it would beexplicitly written <C> instead of TCP.

REPEATER: Electronic device that receives, amplifies and re-transmits StageLink 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 twofiber optic ports) for converting electrical signals to or from light pulses for fiberoptic transmission or reception. It can also be used as a repeater to amplify coaxsignals. It is not considered a node because it does not have an address.

SEGMENT: Any Stage Link section that joins two repeaters or connects onerepeater 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 CharacteristicsThe Stage Link consists of a 2.5 MHz/2.5 Megabit-per-second ARCNET system thatuses either fiber optic or standard RG-62 A/U copper cabling. Either type can bepurchased with a variety of insulation systems such as flame retardant Teflon or highdensity polyethylene.

In applications that must meet IEC codes, GE INDUSTRIAL SYSTEMSrecommends using armored co-axial cable. These cable types have a metal sheathouter layer that functions as both a mechanical shield and as an electrical conductorthat can alleviate lightning induced disturbances on short outdoor runs. This outerlayer must be grounded at each building’s entrances and exits. Fiber optic cablingprevents electromagnetic interference and is often a better alternative for longoutdoor segments (See the section on Fiber Optics).

General SpecificationsLocal Area Network (LAN)Type

ARCNET

Communication Type BasebandFrequency/Speed 2.5 MHz/ 2.5MbpsPropagation Delay (Maximum) 31 micro secondsMaximum Network Length,based on Propagation Delay

6,000 meters or19,680 feet

Repeater Nodes TCPOther Repeaters Fiber optic HubsHigh Impedance Nodes HMI

The Mark V Panel

GEH-6126 Chapter 6 Configuration • 107

Within the Mark V panels, the ARCNET cable should be connected to, for Mark Vthe CTBA card, for Mark V LM AAHA board, which is located within the TCPcommunication processor(s). The CTBA or AAHA card communicates directly withthe TCP communication processor(s). This data exchange is carried out through theone internal port of a three port repeater; the remaining two ports are for externalcustomer use. Signals entering any one of these three legs are amplified and sent outthrough the other two. Therefore, a signal entering the first external port will be sentto TCP and re-transmitted on the second external port. Signals entering the internalport will be sent out on both external ports. Should the CTBA or AAHA card losecontrol power, a relay de-energizes and connects the two external ports. In thismanner, all the other nodes on the Stage Link can continue to function as long as thetopology is designed in accordance with the distance rules provided later in thisChapter.

The Primary Operator Interface, HMIThe operator interface (or HMI) utilizes a single high impedance port that distributessignals in both directions on the Stage Link via a "T" type connector. The ARCNETcard within the HMI receives data by tapping off a portion of signal transmitted onthe Stage Link.

Cable RecommendationsIf the turbine control application requires a segment too long for a co-axial cable, afiber optic cable should be used. For more on fiber optic installation, see the sectionon 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

108 • Chapter 6 Configuration GEH-6126

Summary of Topology RulesNo LoopsMaximum Number of Nodes Allowed 100Maximum Number of HMIs in onenetwork

16

Maximum Time Delay between any twoNodes

31 microseconds

Both Ends Of The Stage Link Must Have A 93 ohm TerminatingImpedanceEvery Node must have a unique network address

Maximum Segment LengthsCo-ax Repeater To Repeater 609.6 metersCo-ax Repeater To Single HMI 609.6 metersCo-ax Repeater to More Than One HMI 304.8 metersHMI Between Two Repeaters 304.8 metersMaximum HMIs Per Segment 8Fiber Optic Cable Hub To Hub (62.5/120micron fiber)

1825 meters

Minimum cable length between HMIs 1.5 meters

Segment Rules

The cable and nodes between two repeaters is called a segment. The segmentdistance cannot exceed 609.6 meters for a coax connection. Fiber optic segmentscan go farther as described below. If a TCP loses power, total length becomes thesum of the two adjacent segments (see rule 8 below). TCP is either a Mark V LM<R> core or a Mark V <C> or <D> core.

The segment between fiber optic repeaters can be as much as 1825 meters. Thetypical fiber optic hub is a 4 port repeater that contains two coax and two fiber opticports.

A two-node segment with one repeater and one high impedance node forming theend of the link may be 609.6 meters long. The HMI must have a cable-terminating resistor (shown as R).

TCP TCP< 609.6 meters, coax >

activehub

< 1825 meters fiber optic cable > activehub

coaxcoax

coaxcoax

TCP

HMI

< 609.6 meters, coax >R 93 ohms

GEH-6126 Chapter 6 Configuration • 109

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, anddoes not have a length of cable between the "T" and the card.

High impedance nodes must be separated by a minimum of 1.5 meters of cablebetween the T’s.

On a segment that has one TCP and two or more high impedance nodes, themaximum segment cable distance must be limited to 304.8 meters or less.

The length of a segment with two TCP’s, and one to eight HMI’s, must be limited to304.8 meters or less.

Each TCP repeater has a relay that drops out when the power is off, connecting thetwo ports in order to maintain communication among the remaining nodes. Thiscomplicates the distances allowed between nodes because the segment formed byany sing le failure still must not exceed 609.6 meters. For segments containingHMIs, this distance drops to 304.8 meters.

Total Effective Distance RulesAlways calculate the total "effective cable distance" between the two network nodesthat have the longest effective distance. This is not always the nodes that are farthestapart 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 ofrepeaters * 25 meters) with all lengths in meters

Total "effective cable distance" may not exceed 6000 meters.

TCP8 High Impedance Nodes Maximum

HMI HMI HMI HMI HMI HMI

R

TCPLess than 304.8 meters

HMI HMI HMI HMI HMI HMI

R

TCPLess than 304.8 meters

HMI HMI HMI HMI HMI

TCP

TCP

Less than 304.8 metersand no more than eight HMIs

HMI HMI HMI HMI HMI HMI

RTCP

110 • Chapter 6 Configuration GEH-6126

The maximum 31 micro second propagation delay is approximately equal to thedelay 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 decidingfactor is propagation delay, not total length. If questions arise about a particularapplication, it may be necessary to measure the propagation delay.

Redundant System Rules (Mark V Only)The two Stage Link systems, <C> and <D>, are not interconnected. Interconnectionsare 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 orone node continuously transmitting.

The <C> and <D> cables can be routed independently to minimize opportunities for acommon failure.

Typically unit control nodes are connected in a "daisy-chain" configuration. A cablefrom the <C> Stage Link is routed from one physical end of the daisy chain to thecentral control room. The <D> cable to the central control room is attached to theopposite side of the unit control string. In this way, a break in the cable or loss ofpower to a <C> and/or <D> leaves all other nodes accessible from some HMI in thecentral control room.

On a system with a fiber optic link, the fiber optic repeater pair does not havebridging relays. Some customers may therefore prefer to use two links to the centralcontrol room, one from each end of the chain of unit controls as shown on the Figureof Example 2. In this example, one set of HMIs in the central control room isoperational if any one of the four fiber optic active hubs fails.

GEH-6126 Chapter 6 Configuration • 111

Example 1: A Simple Plant Application

SEGMENTS TOTALS andCOMMENTS

S1 S2 S3 S4Cable length, meters 270 30 55 270 625Effective cable length 3 <TCP>s at 25 = 75, plus 625 700, well below 6000 meter limitMaximum Segmentwith 1 Node FailureCalculations

Failure of Node: * All combined segments have HMIs, thus themaximum is 304.8 meters. <TCP> 2 to HMI 4 the<TCP> 1 to <TCP> 2 segment. HMI 1 to <TCP> 2 isclose to the limit but should work if <TCP>1 fails,depending upon conditions.

<TCP> 1 <TCP> 2 <TCP> 3Results in combined segment of:HMI1 to<TCP> 2

<TCP>1 to<TCP> 3

<TCP> 2 toHMI 4

300 85 325*Total number of Nodes 7, well below 100 maximum

TCP TCP

S1

HMI 1HMI 2

267m

3m

S2 S3

30m

S4

270m

R

TCP HMI 3

HMI 4

30m 25m

R

112 • Chapter 6 Configuration GEH-6126

Example 2: Redundant Link Stage Application (MARK V ONLY)

Example 3: Complex Plant Application

<C> - Communications Processor<D> - Backup Communications Processor

FOH - Fiber Optic HubHMI - Operator Interface

R - Terminating Resistor (93 ohms)

<C>

<D>

<C>

<D>

<C>

<D>

<C>

<D>

<C>

<D>

<C>

<D>

<C>

<D>

<C>

<D>

HMI

HMI

FOH

FOH

HMI HMI

FOH

FOH

HMIHMI

R

R R

R

TCP - Communications ProcessorFOH - Fiber Optic Hub

HMI - Operator InterfaceR - Terminating Resistor (93 ohms)

TCP HMI

FOH4

FOH3

HMI HMI

FOH2

FOH1

HMIHMI

S1R R

TCP TCP TCP TCP TCP

S11

S2 600mFiber Optic

S3 3m

S4 S5 S6 S7 S8

S9 3m

S10 760mFiber Optic

GEH-6126 Chapter 6 Configuration • 113

SEGMENTS TOTALS1 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11

Fiber cable length 600 760 1360Co-ax cable length 6 3 30 30 180 30 150 3 6 438Max. Effective cablelength

(6 <TCP>s at 25) + (4 FOH at 25) + 1.25 * (600 + 760) + 438 2388, well within 6000meter maximum

Maximum Segmentwith 1 Node FailureCalculations

Failure of Node: All are less than609 or 304maximums.

<TCP> 1 <TCP> 2 <TCP> 3 <TCP> 4 <TCP> 5 <TCP> 6Results in combined segment of: FOH 2 to<TCP> 2

<TCP>1 to<TCP> 3

<TCP> 2 to<TCP> 4

<TCP> 3 to<TCP> 5

<TCP> 4 to<TCP> 6

<TCP> 5 to FOH 4

33 60 210 210 180 153Total number of Nodes 15, much less than 100 maximum

Fiber OpticsFiber optics can be an effective substitute for copper coax cabling, especially incases where longer distances are required, or electrical disturbances are a seriousproblem.

AdvantagesLarger diameter fiber extends this to 9000 feet (2,740 m) because the lighttransmitter gets more light into the fiber.

If the plant is in a high lightning area, fiber optic segments can reduce the controloutages caused by lightning.

Grounding problems are avoided with optical cable. The ground potential can risewhen there is a ground fault on transmission lines, caused by currents coming backto the generator neutral grounding point.

Optical cable can be routed through switchyards and other electrically noisy areaswith 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 lessthan a coax segment.

114 • Chapter 6 Configuration GEH-6126

DisadvantagesFiber optic links require powered hubs, with a reliable source of AC power. Failureof power to either hub causes a link failure.

The effective distance of a fiber segment is 1.25 times the actual cable routingdistance. The rule for Stage Link is that the total effective distance between thefarthest 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 tomechanical and performance degradation over time. The highest quality cable isrecommended.

Review of ComponentsThis section will review all of the basic components of a fiber optic system,including cable, hubs, and connectors.

BasicsThe recommended fiber optic hub accepts two copper coax connections and twofiber optic links. A message coming in on any one of the four ports is repeated outthe other three ports. Each fiber port consists of an outgoing fiber and an incomingfiber. The incoming signal is picked up with a phototransistor and converted to anelectrical signal. The outgoing signal is converted from a train of electrical pulses toinfrared light using a light emitting diode. On the fiber segment the optical output ofone 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, isrecommended for the Stage Link (See Section X-4.). The amount of light that getsinto the fiber depends on the brightness of the light source and the area of the light-carrying portion of the fiber. The amount of light that comes out the other enddepends on the clarity of the glass, the distribution of the index of refraction, thecondition of the fiber, and the attenuation of connectors. The amount of electricalsignal generated depends on the light coming out of the fiber and the area andsensitivity 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 onmetallic wires and protects the cable from excessive bends. Mechanical stress candamage fibers. One way to protect the fiber is to spiral it on the inside of a tube filledwith gel. A more reliable system uses tight buffering with precision tensioned Kevlarfibers which carry the stress of pulling and vertical runs.

!Warning

Never look directly into a fiber. Although most fiber linksuse light emitting diodes, which cannot damage the eyes,some longer fiber links use lasers, which can causepermanent damage to the eyes.

GEH-6126 Chapter 6 Configuration • 115

CableHigh quality fiber is recommended, especially for long distance links. It should be62.5/125 optical cable as well.

Cable attenuation should be between 3.0 and 3.3 dB/km at 850 nm, and around 1 to1.2 dB/km at 1300 nm.

The acrylate protective layer of the fiber should be specified with a 100 kpsi prooftest and a 500-micrometer coating, rather than the 50 kpsi and 250-micrometercoating.

Gel filled (or "loose tube") cables should not be used because of the special carerequired during installation, the difficulty of making terminations and problems ofmaintaining the gel seal, particularly in vertical runs where hydrostatic pressure cancause gel leakage.

Use a high quality "break out" cable, which will make each fiber in itself sturdycable that helps prevent too sharp bends.

Combine the sub-cables with more strength and filler members to build up the cablefor resisting mechanical stress and outside environment attack.

In Section X-10.6, there are two sample specifications for fiber cable; one withoutarmor and one with armor. Rodent damage is one of the major causes of failure ofoptical cable. If there is a possibility of wire insulation damage from rodents, thearmored cable should be chosen. Otherwise, the armor is not recommended becauseit is heavier, has a larger bend radius, is more expensive, attracts lightning currents,and has lower impact and crush resistance. Particularly for underground runs, adirect lightning strike through the earth to the cable shield can cause explosiveformation of steam in damp earth that can mechanically damage the cable.

Test the optical characteristics of the cable with either an optical time domainreflectometer (OTDR) which can be provided by the manufacturer or with a simplerdevice that compares light levels at both ends of the cable.

Four-fiber cables can be used to bring redundant communications to a central controlroom, or the extra fibers can be retained as spares. A less expensive option is to getthe same cable with only two fibers.

HubsThe type of hub described throughout this chapter is built particularly for ARCNETcommunications and has the proper impedance to match the ARCNET line (93ohms). For this reason, a fiber hub intended for ETHERNET, for example, will notfunction properly on the Stage Link. It consists of a power supply that runs from 120or 220 volts AC 50 or 60 Hz. The two models can be converted by moving aninternal 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 inon any port will be amplified and transmitted on the other three ports. Ordinarilyonly one card is used. If the system uses two fiber segments, a second hub isrecommended to improve the communications availability. On the card, normallyonly one copper port and one fiber port are used for the same reason. The fiber opticports in the hub’s card have ST connectors, which are the bayonet type. The lightgray is the transmit port, the dark gray the receive port. In service a light grayconnector always attaches to a dark gray one.

116 • Chapter 6 Configuration GEH-6126

ConnectorsConnectors come in two forms, SMA and ST. The ST connectors give less problemsin the field because they are bayonet type and not subject to over tightening. Overtightening the SMA connector can chip the glass fiber surface causing problems withreflections and loss of transmission. The bayonet type effectively uses a spring topush the two connecting fibers together with the proper force.

Ceramic, glass filled plastic, or stainless steel are used to make the connectors. Theycome in three standard sizes to fit the different diameter fibers. Connectors for the62.5/125-micron fiber are relatively easy to procure. The ceramic connectors can beprecisely made and match the coefficient of expansion of glass.

System ConsiderationsHaving two HMIs in the central control room allows one to be down for maintenancewhile continuing control of the turbines from the control room from the remainingHMI. Similarly, having two fiber segments also allows for failure of one of thehubs, or the power to it. A failure of any one of the copper segments also retainscontrol of all machines.

Often only HMIs and possibly an <H> (Historian) will be near the central controlroom. It will have reliable AC, and if that AC is gone, control from that locationstops. 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. Thetotal budget refers to the brightness of the light source divided by the sensitivity ofthe light receiver. These ratios of power are usually measured in dB to makecalculations easier. The difference between the dB power of the source and the dBpower of the receiver represents the total power budget. This must be compared tothe 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, andthe cable loss increase with aging, and the receiver can become less sensitive. For allthese reasons there must be a margin between the available power budget and thelink loss budget of a minimum of 3 dB. A good installation, including using correctparts and cabling, preparing connectors properly, and laying the cable so as to avoidsharp bends and hot locations will help keep availability.

The hub manufacturer specifies one fiber segment to operate as far as 6000 feet with62.5/125 microns fiber, and 9000 feet for the 100/140 microns fiber. These distancelimitation have been incorporated into the Stage Link layout rules. It isrecommended that fiber optic sections used in the Stage Link must not be longer thanthe specified 6,000 and 9,000 feet for the two fiber diameters. If the applicationsignificantly exceeds these distances another hub must be added to amplify theoptical signals.

GEH-6126 Chapter 6 Configuration • 117

InstallationInstall the fiber optic cable in accordance with all local safety codes. Polyurethaneand PVC are two possible options for cable materials that might meet local safetycodes. 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 ofexcellent quality hubs, UPS systems, fiber cable, and connectors should all beincluded in planning the Stage Link.

Install the system so that it will be strong enough for indoor and outdoorapplications, including direct burial.

Strictly adhere to the manufacturer’s recommendations on the minimum bend radiusand 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 fromthe fiber, inserting the end through the connector, and casting it into an epoxy orother plastic. This typically involves using a kit designed for the particular connectorsystem. 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 willminimize the amount of movement they must endure, yet keep them accessible formaintenance.

118 • Chapter 6 Configuration GEH-6126

SpecificationsThe following sections provide specification information for Four-Fiber Cablewith/without Armor, the Fiber Optic Hub, and Fiber Optic connectors.

Four Fiber Cable without ArmorOptical Cable Corporation Part (or its equivalent): RK920929-A

Fiber and buffering:

Fiber Type: MultimodeCore diameter: 62.5 micronsCladding Diameter: 125 micronsFiber proof test: 100 kpsiCoating Diameter: 500 micronsTight buffer diameter: 900 micronsTight buffer material: Hard elastomeric; plastic not

acceptable.Numerical aperture: 0.275Attenuation & Bandwidth Attenuation

Bandwidth850 nm 3.5 dB/km

160 MhzKm1300 nm 1.3 dB/km

500 MhzKmStripping ability: All layers can be easily removed with commerciallyavailable tools.Sub Cables: Four sub cables each with one fiber

Fiber strength member: Aramid yarnSub-cable diameter: 2.5 + - 0.125 mmSub-cable jacket: ElastomericColor-coded: Standard -- blue, orange,

green, and brownCable construction: Sub-cables with filler/strength

memberJacket: Tight bound pressure extruded

Flame retardant polyurethaneColor: BlackCable weight: 65 kg/kmCable diameter: 8.0 mmStrength members: Aramid yarn with individual

precise tensioningConductivity: No electrical conductors may

be used.

Installation:Min bend radius: 16 cm (when pulling)Max tensile load: 2200 NLocation: Aerial, direct burial, or ductPulling: Ordinary cable grips

GEH-6126 Chapter 6 Configuration • 119

Operating:Min bend radius: 8 cmMax tensile load: 550 NTemperature: -40°C to +85°CImmersion: No damageStorage: -55°C to +85°C

Test specification: EIA-STD-RS-455 (orequivalent):

Impact resistance: 1500 impactsCrush resistance: 2200 N/cmCyclic flexing: 2000 cycles

Four Fiber Cable with ArmorOptical Cable Corporation Part (or equivalent): RK920929-A-CST

Comprised of the same cable as described above, but surrounded with steeltape 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 or1 (540) 265-0690.Fiber and buffering:

Fiber Type: MultimodeCore diameter: 62.5 micronsCladding Diameter: 125 micronsFiber proof test: 100 kpsiCoating Diameter: 500 micronsTight buffer diameter: 900 micronsTight buffer material: Hard elastomeric; plastic not acceptable.

Numerical aperture: 0.275Attenuation & Bandwidth Attenuation Bandwidth850 nm 3.5 dB/km 160 MhzKm1300 nm 1.3 dB/km 500 MhzKmStripping ability: All layers easily removed with

commercially available tools.Sub Cables:Four sub cables each with one fiberFiber strength member: Aramid yarnSub-cable diameter: 2.5 +- 0.125 mmSub-cable jacket: ElastomericColor-coded: Standard -- blue, orange,

green, and brown

120 • Chapter 6 Configuration GEH-6126

Cable construction: Sub-cables with filler/strengthmember

Jacket: Tight bound pressure extrudedand flame retardantpolyurethane

Color: Black

Armor: Steel tape nominal 0.155 mm

Armor overlap: 2 mm, Bonded, corrugations inregister.

Over jacket: Polyethylene 1 to 1.5 mm thick

Cable weight: 174 kg/km

Cable diameter: 13.0 mm

Strength members: Aramid yarn with individualprecise tensioning

Installation:Min bend radius: 26 cm (when pulling)

Max tensile load: 2660 N

Location: Aerial, direct burial, or duct

Pulling: Ordinary cable grips

Operating:Min bend radius: 13 cm

Max tensile load: 532 N

Temperature: -40°C to +65°C

Immersion: No damage

Storage: -55°C to +70°C

Test specification: EIA-STD-RS-455:

(or equivalent)

Impact resistance: 50 impacts

Crush resistance: 440 N/cm

GEH-6126 Chapter 6 Configuration • 121

Fiber Optic HubThe Hub Assembly is typically a metal box with a power supply and card slots. TheStage 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 voltapplication. Moving an internal jumper can reconfigure for the other voltage if amistake has been made.

TABLE MOUNTED FLANGE MOUNTED

120 vac MODHUB-16 MODHUB-16F

50/60 Hz EXP-CXS/FOG-ST EXP-CXS/FOG-ST

240 vac MODHUB-16E MODHUB-16EF

50/60 Hz EXP-CXS/FOG-ST EXP-CXS/FOG-ST

MODHUB-16 can hold four cards, each with 4 ports for a total of 16 ports. Thisexpansion module has two optical ports and two copper coax ports.

Fiber Optic Connectors3M Connector model 6100 (or equivalent). This ST bayonet type zirconiaconnector is already filled with a thermoplastic material that is melted for theinsertion of the fiber. The installation kit is model 6150A (or its equivalent). Thefiller is melted, fiber inserted, end cleaved and polished with only one paper. Thisconnector makes fast and reliable connections and is gaining popularity.

Thomas & Betts Connector model 91810-125-2P (or equivalent). ST connector ofcomposite polymer, glass capillary, crimp and polish termination. Filler is a fastdrying epoxy. Assembly Polishing Kit model 91000AKP (or equivalent) includesall parts needed and instructions.

Amphenol Connector model 953-101-5010 (or equivalent). ST connector made ofglass reinforced polymeric, ceramic ferrule, copper crimp ferrule, and PVC bendrelief boot. Termination kit, model 927-100-5000 (or equivalent), includes stripper,curing oven, microscope, crimp tool, snips, polish board, training video. Add ontermination kit has a cleave tool, polishing tool, cable preparation template andinstructions. Filler is heat-cured epoxy.

Typical Stage Link AddressesThe 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 operatorinterface processor node to an existing Stage Link is described in Chapter 3 of theMark V LM Panel Manual (GEH-6353).

Mark V:

Any valid two digit hexadecimal number may be used for any Stage Link addressexcept for <G> processor addresses. For information about using a <G> processorfor Ethernet Communications with a DCS system, see GEH-6195C Chapter 11.

How to assign a new communication processor, Mark V Trainer, or HMI processornode to an existing Stage Link is described in Chapter 5 of the Maintenance Manual,GEH-5980.

122 • Chapter 6 Configuration GEH-6126

Address Description01 Addresses between 01 and the start of the <G> processor addresses are not02 reserved....0F10 8th <G> processor Reserved for communication with

customer’s DCS via Ethernet11 7th <G> processor12 6th <G> processor13 5th <G> processor14 4th <G> processor15 3rd <G> processor16 2nd <G> processor17 1st <G> processor18 8th HMI processor Reserved for HMI processor addresses.19 7th HMI processor1A 6th HMI processor1B 5th HMI processor1C 4th HMI processor1D 3rd HMI processor1E 2nd HMI processor1F 1st HMI processorAddresses 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 VFB 4th Mark VFC 3rd Mark VFD 2nd Mark VFE 1st Mark V

Stage Link Addresses

*Address 00 is reserved

*Address FF is not reserved but typically not used

GEH-6126 Chapter 6 Configuration • 123

Control Hierarchy

Overview

Control Hierarchy is an optional scheme to define different control locations andpass control between these locations. Control locations are defined, and thendifferent elements in the system are configured to only send commands if the currentcontrol location allows them to send commands.

The HMI implements what commands are forwarded to the Mark V control panelthrough Control Hierarchy. This is a cooperative function of the HMI processorand the Mark V panel. The Mark V maintains a CONTROL LEVEL variable, andeach HMI processor looks at the panel’s current control level to decide if that HMI isallowed to send command to the unit.

Any element of the system that can initiate a command is called a CONTROLPORT. The database of an HMI server is an example of a control port, as is theMODBUS link and the ETHERNET link. Control Hierarchy is implemented byspecifying which control ports are allowed to send commands to a unit based uponthe 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.

124 • Chapter 6 Configuration GEH-6126

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 tozero (0) when the control panel is reset. For that reason, Control Location zero (0) isusually defined as being "UNASSIGNED".

Control Location one (1) is often used to indicate control is isolated to the BackupOperator Interface (BOI). No control ports are given permission to send commandsto the unit when the control location is in "BOI". This provides a form of panel-onlycontrol that is often used by maintenance.

The higher numbered control locations are typically used for control locations suchas: "HMI", "MODBUS", and "ETHERNET". At the very extreme is the case wherea different control location is defined for each HMI Server, and only that HMI Serveris 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 isin each control location.

These decisions should be easy once you have defined the number of control levelsneeded. Some sites will opt for the ability for all control ports to send commands tounits that are "UNASSIGNED", while other sites may decide that no commands maybe sent to "UNASSIGNED" units, the control location must be changed to assign theunit to a control location first. If you define a control location of "BOI", do not letany 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 blockcommands based upon a logic signal in the unit. If a LOCKOUT signal is definedfor the unit, when the lockout signal is true only one specified command will be sentto the unit. That one command must have the ability to set the LOCKOUT signal tofalse. This LOCKOUT signal is sometimes used to block commands when the unithas been selected for CABLE REMOTE operation. If the logic is true in the unit thatindicates that the unit is in CABLE REMOTE operation (usually L43CA) it willblock all commands except the SC43 command, which is used to change fromCABLE REMOTE back to AUTO.

GEH-6126 Chapter 6 Configuration • 125

Note It is usually not necessary to block HMI commands while operating the unit inCABLE REMOTE selection, but this can be done if desired. If commands are notdisabled, the HMI will simply be a peer with the cable remote commands. Normalcontrol hierarchy can take care of multiple HMI processors.

STEP 3 - Decide which ports are allowed to change the control location, basedupon the current control location.

The next major decision is what control ports are allowed to change the controllocation from one value to another. This is done dependent upon the current controllocation.

A useful philosophy is that any control port that is "closer" to the turbine can takecontrol if desired. This means that an HMI can take control away from a MODBUSlink, 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. Thisprevents the case of control being turned over to another location, but that locationwas not aware that it was expected to control the unit.

STEP 4 - Create the HMI file F:\CTRL_LOC.DAT according to the decisionsmade in steps 1 - 3.

Once the decisions are made on how the Control Hierarchy is to be implemented, theactual implementation is done by creating a file on each HMI processor. The file isthe F:\CTRL_LOC.DAT file, and it is an ASCII text file that is edited using thestandard text editor.

This data file defines a COMMAND table that indicates what control ports areallowed to forward commands and alarm commands to the unit based upon the unit’scurrent control location. This table will be different for HMI processors at differentlevels. (For example: The local HMI will have the table filled in differently than theremote HMI.)

The data file also defines a TRANSFER table that indicates what control ports areallowed to change the current control location based upon the unit’s current controllocation. 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 thelockout signal is TRUE can be defined.

126 • Chapter 6 Configuration GEH-6126

STEP 5 - (Optional) Modify the HMI configuration to define an enumeratedstate table, which defines the control locations.

The HMI processor uses a special signal in the Mark V control panel to hold thecontrol location. The point used has the pointname of I_C_CTRL_1. This signaldefaults to an "analog" signal scaled with a scale type of CNT15. When displayed, itwill 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 newenumerated type that contains the strings for the control locations. Once this tablehas been defined the I_C_CTRL_1 signal can have its scale type changed fromCNT15 to ENMnn, where "nn" is the number of the newly created control locationsenumerated table. Once this is done, the displays will now show the control locationusing the enumerated string, not the integer value.

If your site is using synonyms, you might also wish to edit the SYNONYM.DAT fileto 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 tochange the control locations. Add control targets to send the I_C_CTRL_1 point thevalue of the desired control location. The HMI will check the command against theTRANSFER table before sending the command to the unit.

GEH-6126 Chapter 6 Configuration • 127

;; 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 header line is simply the word "LOCKOUT".; The data line is the name of the logic signal, followed by the name of; the one command allowed when that logic signal is TRUE. No unit names; can be specified in the point name fields.;;; LOCKOUT ; If logic is true, only this one command is allowed; L43CA SC43 ; 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 ; This defines the command table.

; CTRL CTRL ALRM; LOC CMDS CMDS ; Control Location Description; --- ---- ---- ------------------------------ 0 I.. I.. ; Unassigned 1 I.. I.. ; Local HMI 2 ..E ..E ; 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 ; This table shows what transfers of control loc are allowed

; CUR ---- DESIRED LOC -----

128 • Chapter 6 Configuration GEH-6126

; LOC 0 1 2; --- --- --- --- 0 ... I.. I.E 1 I.. ... I.. 2 I.. I.. I.. 3 ..E I.E ...

;-----------------------------------------------------------------------;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

GEH-6126 Chapter 6 Configuration • 129

Time Zone Make Utility Program – TZ_MAKEThis section describes F:\TIMEZONE.DAT, and the use of the TZ_MAKE.EXE utilityprogram.

TIMEZONE.DAT is used to define the UTC based times of transition to/fromStandard Time from/to Daylight Time. Each transition definition also contains anentry containing the number of minutes to add to a UTC based timetag to arrive atLOCAL.

Note This is the opposite of many time correction schemes, most notably theTIME_ZONE_INFORMATION data structure defined by Windows NT.

TIMEZONE.DAT can contain up to 100 entries. A minimum of 3 entries arerequired. This allows a span of 50 years to be used for UTC/LOCAL timeconversion lookup.

The XT routines use the UTC based transition records to create internal LOCALbased lookup records. These LOCAL based lookup records allowXtLocalTimeToUtcTime () 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 --> LocalTime translation is always exact. No UTC time later than or equal to the lasttransition record can be used. TZ_MAKE.EXE is a utility program that can makeTIMEZONE.DAT (or a file by any other name). It is a rule-based program thatcalculates past and future date/times for transition to/from Standard Time from/toDaylight Time. It generates entries starting 5 years in front of the year in which it isrun, and generates 100 entries. For example, if TZ_MAKE is run in 1996, it willgenerate entries spanning from 1991 through 2040 inclusive.

By default, TZ_MAKE uses the Windows NT GetTimeZoneInformation() routine toobtain 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. Theform of this TZ definition is based on QNX/UNIX timezone rules. (Julian dateformats are not supported however.)

Note The resulting TIMEZONE.DAT file may require editing if local laws changethe actual transition times normally used by a given locale.

The format for entries in TIMEZONE.DAT was selected to allow grafting toF:\TIMESYNC.DAT used for Mark timesync TZ_MAKE Usage: D:>\TZ_MAKE output-datafile-name ["TZ=<timezone definition>"]

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=<timezone definition> is specified, it must be enclosed in quotes (")

If TZ= argument is omitted, local Windows NT timezone rules are used.

<timezone definition> takes the following form (Spaces are for clarity only): stdoffset dst offset, rule

std, dst are strings containing 3 or more characters and spaces. These are the namescorresponding to Standard Time and Daylight Time respectively.

offset takes the form HH[:MM[:SS]], optionally preceded by "+" or "-"

130 • Chapter 6 Configuration GEH-6126

NOTE ------> These indicate the values to add to LOCAL time to

DIRECTION--> 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 DaylightTime, and the second date/time defines the transition from Daylight Time toStandard 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 thatEastern Daylight Time is 4 hours earlier than UTC. Daylight Time begins on the firstSunday in April at 02:00:00. Standard Time begins on the last Sunday in April at02:00:00. Below is an abbreviated sample output. This example used the "TZ="construct to define the transitions for Central Time USA.

GEH-6126 Chapter 6 Configuration • 131

;; 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 TimeTIME_OFFSET 07-APR-1991 08:00:00.000 -300TIME_OFFSET 27-OCT-1991 07:00:00.000 -360TIME_OFFSET 05-APR-1992 08:00:00.000 -300TIME_OFFSET 25-OCT-1992 07:00:00.000 -360TIME_OFFSET 04-APR-1993 08:00:00.000 -300TIME_OFFSET 31-OCT-1993 07:00:00.000 -360TIME_OFFSET 03-APR-1994 08:00:00.000 -300TIME_OFFSET 30-OCT-1994 07:00:00.000 -360TIME_OFFSET 02-APR-1995 08:00:00.000 -300TIME_OFFSET 29-OCT-1995 07:00:00.000 -360TIME_OFFSET 07-APR-1996 08:00:00.000 -300TIME_OFFSET 27-OCT-1996 07:00:00.000 -360TIME_OFFSET 06-APR-1997 08:00:00.000 -300TIME_OFFSET 26-OCT-1997 07:00:00.000 -360TIME_OFFSET 05-APR-1998 08:00:00.000 -300TIME_OFFSET 25-OCT-1998 07:00:00.000 -360TIME_OFFSET 04-APR-1999 08:00:00.000 -300TIME_OFFSET 31-OCT-1999 07:00:00.000 -360TIME_OFFSET 02-APR-2000 08:00:00.000 -300TIME_OFFSET 29-OCT-2000 07:00:00.000 -360TIME_OFFSET 08-APR-2001 08:00:00.000 -300TIME_OFFSET 28-OCT-2001 07:00:00.000 -360

132 • Chapter 6 Configuration GEH-6126

TCI Control Panel AppletThe Turbine Controls Interface (TCI) Control Panel Applet allows you to adjustparameters used by the Turbine Applications. Incorrect values in some of theseentries can cause the Turbine Applications to not work correctly. They will need tobe corrected before the system will function correctly. Most of the changes will nottake affect until the system is rebooted or the correct services are stopped andrestarted.

Auto LoginAuto Login causes the computer to login as the defined user when it is rebooted orwhen the current user logs off. To override the auto login when it is enabled, uponreboot hold the shift key down after the desktop background appears.

Disabled/Enabled - If disabled is selected, the computer will not try to auto loginthe user. If enabled is selected, the computer will try to automatically login the userdefined 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 isusually 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 notmatch, you will get a warning and be asked to enter them again.

ARCNETThis tab allows you to set the parameters the ARCNET driver will use to talk to theARCNET card. The jumpers on the card must be set to match these parameters forthe 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 theARCNET network. All cards on the network must have a unique address.

GEH-6126 Chapter 6 Configuration • 133

SiteThis tab allows you to set the default Site parameters for the Turbine ControlInterface (TCI), On Site Monitor (OSM), Cimplicity Bridge for Mark V (CBV), orHistorian (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 SyncThis tab allows you to set the type of time synchronization hardware on thisTurbine Control Interface. Each individual application will have its ownconfiguration information.

Time Acquisition Hardware - This allows you to select the type of timesynchronization 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 timeboard. This option will only be available if a high-resolution time board wasinstalled when the Turbine Product was setup.

High Resolution Time Card - This allows you to set the parameters for the high-resolution time board. This section will only be available if a high-resolution timeboard was installed when the Turbine Product was setup and High Resolution isselected 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 messagesfrom units on a predefined printer attached to the computer running the TCIsoftware. The Alarm Logger program runs automatically and requires very littlesystem 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 variousunits attached to the system.

The Alarm and Event Logger program requires that the following items be set up aspart 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 shouldgenerally be associated with a line-printing device such as a dot matrix printer ratherthan a page-printing device such as a laser printer. This allows the alarm and eventrecords to be examined as they are received and printed.

134 • Chapter 6 Configuration GEH-6126

The printer must be configured with a small font to allow printing alarm and eventmessages on a single line. Alarm messages can be up to 90 characters wide, eventmessages up to 140 characters wide. A font pitch of 15 characters per inch on 8.5-inch wide paper will allow all alarm messages to be printed on a single line, and allbut the widest event messages to be printer on a single line. This should beconfigured 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 alarmand event messages to the queue named Alarm Printer as they are received, asfiltered by the Logger Control dialog box.

CIMPLICITY Project

IntroductionThe Signal Manager is a utility program for configuring CIMPLICITY points andalarms for Mark V Turbine controllers. It can also be used to view the attributes ofsignals in the Control Signal Database (CSDB). The program can be found on theHMI in G:\EXEC\CSDBUtil.EXE.

The TCI service must be running before using this program since it accesses datafrom each unit’s Data Dictionary, which is built and maintained by the TCI service.

SetupTo enable Mark V alarms in CIMPLICITY, the External Alarm Manager projectoption must be selected and to enable Mark V signal data the Mark V+Communications protocol must be selected. After creating a new CIMPLICITYproject, a CIMPLICITY Port for the Mark V+ Communications protocol must beconfigured before Mark V signals can be imported into the project. See figurebelow.

See also the CIMPLICITY Base System User’s Manual GFK-1180 for moreinformation on creating projects and configuring ports.

GEH-6126 Chapter 6 Configuration • 135

When the Signal Manager imports Mark V signals into CIMPLICITY any neededCIMPLICITY devices and resources are also configured if they are not alreadypresent. For example when importing signals for unit T1, the program will configurea CIMPLICITY device called T1 and a CIMPLICITY resource called T1. For eachdevice configured by the program, three virtual points needed by the MARK V_RPprogram are also configured. If the device were called T1 then these would be thevirtual 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 theunit

SignalsThe program displays data from the Data Dictionary, which describes the unit’sCSDB. Each row of the display shows information about a signal, divided intocolumns. 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 theexpected user interface commands for selecting items, sorting rows and sizingcolumns.

The columns that are displayed can be configured by the user, the followingattributes 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

136 • Chapter 6 Configuration GEH-6126

AlarmsThe 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 alarmsfor an EX2000 exciter.

The CIMPLICITY alarms for turbine controllers are only placeholders and will begiven the appropriate parameters at run time when they occur. Process alarms areconfigured with an alarm id of “P<n>” where n is the drop number reported by thecontroller, likewise diagnostic alarms are configured as “D<n>”.

CIMPLICITY alarms are also used for not only for turbine alarms but for hold listentries, sequence of events and digital events as well. An alarm ID of “HOLD” isconfigured for hold list points. An alarm ID of “SOE” is configured for sequence ofevents. An alarm ID of “EVENT” is configured for digital events. TheseCIMPLICITY alarms are only placeholders and will be generated multiple times atruntime with different parameters for each instance.

When the Signal Manager configures alarms it will also configure alarm classes ifneeded. If a needed alarm class is not configured, it will be added to theCIMPLICITY configuration. If the alarm class is already configured, the existingalarm 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 ofthe fault codes generated by the EX2000 exciter. The exciter alarms are not placeholders and are configured with all parameters fully defined.

Importing SignalsWhen the Signal Manager is started, an empty list is displayed. To populate the listwith signals select New from the File menu. A dialog is displayed allowing the userto specify which signals to fetch from the Data Dictionary. The desired unit shouldbe chosen from the displayed list of units. The user can optionally provide a signalname with wild cards to filter the signals retrieved from the Data Dictionary. Thewild card characters supported are the asterisk (*) which matches zero or moreoccurrences of any character, and the question mark (?) which matches zero or oneoccurrence of any character. The displayed check boxes can be used to filter thesignals by type. Putting a check mark in a box will allow signals of thecorresponding type to pass through the filter.

GEH-6126 Chapter 6 Configuration • 137

To import signals into CIMPLICITY, select the desired signals from the displayedlist (to select all the signals in the display choose Select All from the Edit menu) andchoose Import from the Action menu. A dialog is then displayed allowing the userto select the .GEF file for the desired CIMPLICITY project.

It is sometimes desirable to populate the CIMPLICITY point database with pointsfrom a set of screens. The Signal Manager’s displayed list of signals can bepopulated with the signals referenced in a set of screens. To invoke this functionselect 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 signalsfound can then be selected and imported into the CIMPLICITY point database.

138 • Chapter 6 Configuration GEH-6126

Configuring Exciter AlarmsTo configure alarms for Mark V controllers, select Alarms from the Action menu.The Signal Manager program will then configure process and diagnostic alarms aswell as alarms for Hold List, Sequence of Events and Digital Events.

To configure alarms for EX2000 exciters select EX2000 Alarms from the Actionmenu. 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 CIMPLICITYpoints that contain the exciter fault codes. The exciter core that generates the faultcode must also be specified. After providing the point name and exciter core, selectConfigure. The program will then run some command line utilities and display theiroutput in a scrolling text box. These command line utilities configure events andactions in CIMPLICITY that will generate alarms when the value of the fault codeCIMLICITY point changes value. After these events and actions are configured theuser can then specify another exciter fault code point or select Done.

GEH-6126 Chapter 6 Configuration • 139

Unit Configuration

Unit Configuration OverviewThe TCI service uses the information contained in the F: Drive to determine whichunits to communicate with, how those units are controlled, what data is to becollected and how it is displayed. The configuration files require modification toconfigure and control the units.

!Caution

Only qualified personnel should make changes to theconfiguration files. Any changes can have an impact onthe unit control!

Modifications include modifying the files at the top level of F: to configure the siteparameters and turbine control units the HMI will be communicating with. Next thefiles of each unit configuration must be set up, modified, and tuned to give theturbine control its desired control function and performance through theconfiguration parameters. This accomplished by both directly editing the files andemploying the various HMI turbine tools (programs) to build the unit ControlSystem Database (CSDB). The unit CSDB must be downloaded to the turbinecontrol and the controller must be reinitialized with the new CSDB.

Lastly, the unit configuration directories on each HMI must be kept insynchronization with those on the other HMIs. This is best accomplished bydesignating one HMI as the configuration master. The unit configuration files fromthis HMI can be copied from the configuration master to the other HMIs via networkor diskette.

!Caution

Failure to have the unit configuration files matchthose, which have been downloaded to the unit, couldresult in erroneous data being displayed on the HMI.

140 • Chapter 6 Configuration GEH-6126

HMI F: \ Drive Configuration FilesWhen 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 ControlPanel Applet in the TCI Site tab. This is usually the C:\SITE directory. Usersmust 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 Synchronizationsection.

These files govern which units the HMI is able to communicate with and how timesynchronization is handled.

The F:\CONFIG.DAT file, shown below, is a text file that contains information aboutthe units with which the HMI can communicate. The lines in this file that begin witha semi-colon ( ; ) are comments which do not affect operation and are ignored byHMI programs that use the file.

GEH-6126 Chapter 6 Configuration • 141

; 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 <I> 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 <I>), (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 <I> 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 <I> 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.

142 • Chapter 6 Configuration GEH-6126

The section of the file shown in the example defines the unit information for theHMI. Information in the UNIT_DATA section denotes the unit(s) with which an HMIcan communicate. Each line in the section represents a particular unit; that is, theunit number, the unit name, and the path to the unit’s configuration information (itsunit-specific directory). This information is necessary to determine where the unit-specific files for a particular unit reside. The cautions specified in the commentshould be observed when making modifications to this section, and the TCI servicemust be restarted in order for the changes to take effect.

HMI Unit-Specific DirectoryEach Mark V control panel assigned to communicate with an HMI has a unit-specificdirectory and subdirectory on the hard disk of the HMI. These directories havenames, which refer to the unit. They are located on the F: drive and are defined inF:\CONFIG.DAT. The unit-specific directory for the first unit the HMI communicateswith is usually named F:\UNIT1; its subdirectory is F:\UNIT1\PROM. Subsequentunit-specific directories and their subdirectories would be F:\UNIT2 andF:\UNIT2\PROM, F:\UNIT3 and F:\UNIT3\PROM, and so on.

Configuration files contained in a unit-specific directory can be broken up into thefollowing 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 FilesAssignment files, while not downloaded to a Mark V control panel’s processors,contain unit-specific control signal database pointnames and scale types for many ofthe control signals. The information in assignment files is used when creating theprimary unit Data Dictionary file, UNITDATA.DAT. This file contains all of the unit-specific control signal database pointname information.

For each unit, GE provides the following four assignment files in the HMI’s unit-specific 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 ASCIItext editor.

When I/O devices are connected to a Mark V control panel, they must be assigned acontrol signal database pointname and a scale type. I/O devices connected to a MarkV control panel are specified in the I/O assignment file, IO.ASG. In this file, acontrol 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 processorshave multiple spare control signal database memory locations (points) which areavailable for use (or assignment). To make use of these spare points for new oradditional control and protection functions it is necessary to define the type of pointrequired, the control signal database pointname for the point, and the scale code forthe point. These definitions are made in one of the following assignment files:

GEH-6126 Chapter 6 Configuration • 143

FACTORY.ASG, ALLOCSSP.ASG, or SITE.ASG. The file in which the assignment ismade depends on the type of signal required as well as on who is making theassignment (that is, factory personnel or site personnel, customer or GEPS/BusinessAssociate field personnel). GE or GEPS’s business associates assign control signaldatabase pointnames and scale types to spare memory locations in FACTORY.ASG.This file may be altered to accommodate customization of the Control SequenceProgram for a particular application. The only types of assignments not made inFACTORY.ASG are for additional I/O, spare double-word variables, and spare alarmlogic points. Spare double-word variables and alarm logic points which are requiredfor a particular application are assigned pointnames and scale types inALLOCSSP.ASG (which stands for ALLOCation of Structured Software Points).Both factory (GE and GEPS Business Associates) and field/site personnel can makeassignments for these two types of points in ALLOCSSP.ASG. Customer and/orGEPS/Business Associate field personnel are to make assignments of signalpointnames and scale types to spare control signal database memory locations inSITE.ASG for points other than I/O, double-word variables, and alarm logic points.

Unit-Specific Data Dictionary FilesData Dictionary files contain information about unit-specific control signal databasepointnames, alarm text messages (for both process and diagnostic alarms), anddisplay information for signal pointnames (type/units, messages, etc.). The primaryunit Data Dictionary file, UNITDATA.DAT, can be created on an HMI in the unit-specific 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 anHMI require information from UNITDATA.DAT when modifying or compiling unitconfiguration files for downloading.

Some control signal database pointnames are common to applications (steamturbines or gas turbines) and must reside in memory at specific locations and mustnot be changed. These common, fixed pointnames are contained in template files.The fixed control signal database pointnames, the I/O assignments, and sparememory locations being specified in the assignment files must be included in theUNITDATA.DAT file. If any new assignments are made, they must be included in anew UNITDATA.DAT file.

THE PROGRAM DDLOCATE CREATES UNITDATA.DAT. This program uses theassignment files which are specified at the time DDLOCATE is executed in additionto three template files in the unit-specific PROM sub-directory: UNITDATA.TPL,UNITFREE.TPL, and UNITMAP.TPL. Information from both the assignment filesand the .TPL files (TPL stands for "template") in the PROM sub-directory are used tocreate the unit-specific UNITDATA.DAT file. The command-line format for executingDDLOCATE is:

DDLOCATE IO.ASG FACTORY.ASG ALLOCSSP.ASG SITE.ASG Although theirorder is unimportant, all assignment files for a particular unit must be specified onthe command line each time DDLOCATE is executed. If a modification is made toALLOCSSP.ASG only (such as to use a spare alarm logic point), all the assignmentfiles must be specified on the command line when DDLOCATE is executed. Eachtime DDLOCATE is executed, a new UNITDATA.DAT file is created; all theassignments must be included in this new file. DDLOCATE is run as part ofMK5MAKE.BAT. For more details see the section on MK5MAKE.BAT.

144 • Chapter 6 Configuration GEH-6126

Other Data Dictionary files that must be present in the unit-specific directory forproper 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 forproper 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’sprocessors, but are loaded into the HMI’s RAM each time the HMI is turned on orreset. This information is used to scale and display control signal database pointnameinformation 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 ConstantsI/O Configuration Constants are used to scale or condition signals to and from I/Odevices connected to the Mark V control panel. I/O devices include pressuretransducers, temperature switches, electro-hydraulic servo-valves, positiontransducers or reactors, thermocouples, RTDs, etc.. Many of these I/O devices, beingof the same type, can have differing outputs or require dissimilar inputs. Forexample, thermocouples produce a millivoltage proportional to temperature,however, a Type K thermocouple produces a different millivoltage than a Type T forthe same temperature. An I/O Configuration Constant can be used to appropriatelyscale the input signals from various types of thermocouples. Milliamp transducerscome in several output ranges: 4-20 mA, 0-1 mA, 0-10 mA, etc.. More than one typeof milliamp transducer may be used on a unit or its auxiliaries. I/O ConfigurationConstants are used to scale the input for use in controlling, protecting, or monitoringthe unit.

I/O Configuration Constants are initially contained in the I/O configuration files inthe unit-specific directory. The files are:IOCFG_Q.DAT, IOCFG_C.DAT, andIOCFG_D.DAT. All three files will be present in the unit-specific directory for eachMark V control panel that is to communicate with the HMI, even if the control paneldoes not include a <D> backup communication processor. The information in thesefiles is in hexadecimal format, and can be viewed using the I/O Configuratorprogram, IO_CFG, usually available from the HMI Main Menu. The screenspresented in the I/O Configurator depend on the configuration data files found in thePROM directory for the unit. PROM\IO_CFG.DAT contains the list of files requiredfor the I/O Configurator,such as TCCA_CFG.DAT. The I/O configuration files maybe downloaded to a Mark V control panel’s processor(s) without any intermediatesteps (such as compiling).

GEH-6126 Chapter 6 Configuration • 145

Unit-Specific Table FilesThe majority of unit-specific configuration files are Table Files. These files containtabular listings of control signal database pointnames and information about theirtype, 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 SequenceProgram and the loggers of the Mark V control panel’s processors. Figure 3-3 showsa list of Table Files and a brief description of their contents. Several of the sourceTable Files are dummy files and contain no information. They have been created forsymmetry and possible future use.

Modifications can be made to any of the ASCII text Table Files (known as sourcefiles) using any ASCII text editor. Prior to downloading the information in the sourceTable Files, it must be converted into binary format using the Table Compilerprogram, TABLE_C. The command line format for executing the Table Compiler tocompile all the Table Files is:

TABLE_C ALL

Using the Table Compiler, information in the source Table Files will be convertedinto binary format in files with the same filename but with a .AP1 filenameextension. (For example, CONST_Q.SRC would be compiled into CONST_Q.AP1.)

The Table Compiler uses information contained in UNITDATA.DAT and one of thescale code files (ENGLISH.SCA, by default) when converting the source files intohex files. Since no control signal database pointnames are downloaded to the Mark Vcontrol panel processors, the Table Compiler finds the software signal pointname inUNITDATA.DAT, and uses its memory location/address and scale code and point typewhen creating the downloadable Table Files from the information in the sourceTable Files (see example below).

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 <C> mA outputs

CHNG_B.SRC A list of <C> analog pointnames and ranges monitored forexcursions and logged as events to the Historian

CHNG_Q.SRC A list of <Q> analog pointnames and ranges monitored forexcursions and logged as events to the Historian

EVENT_B.SRC A list of <C> logic signal pointnames logged as events

EVENT_Q.SRC A list of <Q> 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 <C> which are associatedwith command pushbuttons in the CSP

CBLR_Q.SRC A list of digital inputs to <Q> which are associatedwith command pushbuttons in the CSP

146 • Chapter 6 Configuration GEH-6126

Unit-Specific CSP Segment FilesA CSP segment is an ASCII text file, which contains information such as ControlBlocks, parameters, comments, and/or relay ladder diagram sequencing. The ControlSequence Program for a unit is made up of at least two segments — one for <Q> andone for <B>. 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 relatedand/or must be executed at a certain frequency. There can be as many as eight CSPsegments for <B> and eight CSP segments for <Q>.

CSP segments can be viewed and modified using the Control Sequence Editorprogram, SEQEDIT.EXE (Available in the Turbine Control Maintenance section onthe HMI). Refer to the section for the Control Sequence Editor. In some cases, all ofthe unit's control and protection (other than emergency overspeed trip and servoregulator loops) can be accomplished in one CSP segment in <Q>. CSP segmentfiles can have any valid DOS filename (eight characters max) but must have an .SRCfilename extension.

Prior to downloading to a Mark V control panel, the CSP must be converted tobinary (AP1) format using the Control Sequence Compiler, or CSP Compiler. TheCSP Compiler uses information from UNITDATA.DAT, BBL definition files in theunit-specific PROM subdirectory (PRIMITIV.DEF and BIGBLOCK.DEF), and thenames of CSP segment files which have been specified in a unit-specific controlsequencing configuration file, MSTR_SEQ.CFG. The CSP Compiler creates binaryformat downloadable CSP files — SEQ_B.AP1 and SEQ_Q.AP1 (SEQ.AP1 forMark V LM). The CSP Compiler can be executed from the Turbine ControlMaintenance section of an HMI or at the command line of the unit-specific directorywith the COMP_SEQ command.

MSTR_SEQ.CFG (a text file) contains two sections, which define the names of CSPsegment files, which are compiled for <Q>’s CSP and <B>’s CSP. In addition, itdefines the rates and the offsets/skews as well as the order in which CSP segmentsare compiled and executed. (The first segment file specified will be executed first,the second segment file specified will be executed next, the third segment filespecified will be executed next, and so on.) See the section on MSTR_SEQ.CFG formore information.

CSP segments are initially created using BBLs , relay ladder diagram rungs, andcomment rungs. They are customized by GE or its Business Associates to match aparticular application or Customer’s requirements and can be modified in the fieldusing the Control Sequence Editor. New CSP segments can be created using theControl Sequence Editor. If a new segment is created, the name of a new segmentmust be added to MSTR_SEQ.CFG to be included in the downloaded CSP files. Themaximum of segments per <Q> and <B> that can be compiled is eight (16 for Mark

V LM).

Compiling Unit-Specific Configuration FilesThe unit-specific Table and CSP files must be converted to binary format prior todownloading to the processors in a Mark V control panel. This is accomplished byusing the Table Compiler program directly or the MK5MAKE.BAT batch file whichcalls the Table Compiler program. Please refer to the sections on the Table Compilerand MK5MAKE for more details.

GEH-6126 Chapter 6 Configuration • 147

Downloading Unit-Specific Configuration FilesWhen the unit-specific ASCII text Table and CSP files are compiled to binaryformat, they along with the I/O Configuration Constants can be downloaded to theprocessors in the Mark V control panel using the EEPROM Downloader program.The EEPROM Downloader program, EEPROM, is available from the commandline of an HMI.

The EEPROM Downloader program will transfer unit configuration file information(sometimes known as EEPROM partitions or sections) from the HMI computer’shard disk to controller. Please refer to the section on the EEPROM Downloader formore details.

Control ConstantsSpecial care must be exercised when modifying control constants in theCONST_Q.SRC file. These constants are downloaded to nonvolatile memory on theunit control. They are copied to RAM memory when the control is initialized andused during the execution of the CSP.

The values of Control Constants in the processor’s RAM can be changed using theControl Constant Adjust Display program by selecting a constant on the ControlConstants display on an HMI. Control Constants can be adjusted while the unit isrunning, although the rate of change of the Control Constant’s value is quite slowwhen the unit is running to prevent a rapid change from tripping the turbine. Formore information on the Control Constant Adjust Display, refer to its section in thismanual.

A feature of the Control Constants Adjust Display is the copy the Control Constantwhose value was changed in RAM to the controller’s nonvolatile memory. Byclicking on the target Storage Update and then clicking on the OK button in ExecuteDialog Box, the current RAM value of every Control Constant will be copied to theprocessor’s nonvolatile memory.

However, there is no automatic method of updating the values of Control Constantsin the configuration file CONST_Q.SRC. If a Control Constant in a Mark V controlpanel is modified using the Control Constant Adjust Display and the value of theControl Constant in CONST_Q.SRC is not subsequently changed to match the unit’svalue, a re-compiling and downloading of Control Constants will cause thecontrollers nonvolatile storage value of the Control Constant to revert to the oldvalue in CONST_Q.SRC.

Note Whenever a Control Constant is modified using the Control Constant AdjustDisplay, the Control Constant source Table File, CONST_Q.SRC, should be editedto reflect the new value and compiled. This will assure the Control Constant TableFile hexadecimal file, CONST_Q.DAT, will contain the new value and anysubsequent downloads will be done with the correct value.

It is possible to generate a list of the current values of control constants in the unitcontrol using the CONSTCHK program. Refer to its section for more details.

148 • Chapter 6 Configuration GEH-6126

DABUILDDABUILD is a Mark V specific program that is used to configure the alarm text stringfor the Diagnostic Alarms. It is not part of the normal configuration process, it isused 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). Thisprogram 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 reportsit through the use of a diagnostic alarm number. The HMI must be able to matchthat number to the diagnostic alarm text to be shown. This text information is readfrom the unit configuration directory ALARM.DAT file. This file contains the dropnumber and alarm text for each alarm. In order to ensure that the drop numbers andalarm text match, the same file (DIAG.H) is used to create the drops in the unit as isused by the HMI to create the template alarm text file. This file needs to betranslated 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 thediagnostic alarms in the unit and creates the template diagnostic alarm text file forthe HMI. The file used is typically the DIAG.H file in the unit configurationdirectory, but you can specify a different file as a command line parameter. If runwith the parameter "/?" it will provide a help screen. The output from this programwill 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 stringsfor a Mark V after a major upgrade. It uses the Diagnostic Alarm headerfile (DIAG.H) as the source of the text strings. This file is typicallynot required on-site, but some major prom updates may require thatDABUILD 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>

GEH-6126 Chapter 6 Configuration • 149

DCBUILD1DCBUILD1 is a command line configuration program that builds the list of availableDiagnostic Counter Displays for a unit. It places the results into the DIAGC.DAT filein 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 unitsusually distribute the DIAGC.DAT file as part of the distribution instead of building iton site from the Card Library.

Many of the cards in the Mark V or Mark V LM panel provide advanced diagnosticinformation upon request. The Diagnostic Counter Display (DIAGC) is the programthat 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 calledDIAGC.DAT in the unit configuration directory.

When PROMS are changed in the unit, the list of available diagnostic displays maychange, as the new PROMS may change the diagnostic information available fromthe card. DCBUILD1 uses the information in the PANEL.CFG file to determine theset of cards that exist in the panel, including the revision level of each card. It thenreads the Card Library for the list of diagnostic displays that are available from eachcard in the panel, then builds the new DIAGC.DAT file.

DCBUILD1 is a command line utility that is run from the unit configurationdirectory. It uses command line parameters to indicate the location of the CardLibrary. If run with the parameter "/?" it will provide a help screen.

150 • Chapter 6 Configuration GEH-6126

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:<directory>] [/CFG:<filename>] [/GO]

/LIB:<directory> Directory for the card library.

/CFG:<filename> Override default configuration file.

/GO Don’t ask for permission to run.

If /LIB:<directory> is not found it defaults to the current directory.

INPUTS:

- PANEL.CFG Defines the panel configuration.

- <card library> Files that define the contents of each card.

OUTPUTS:

- DIAGC.DAT The data file DIAGC will read.

F:\UNIT2>

GEH-6126 Chapter 6 Configuration • 151

DDLOCATEDDLOCATE 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). Thisprogram takes a list of the signals that are needed and will locate them in the propersection of the CSDB. It handles assignments for both fixed locations (used forhardwired 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 timedatabase used in the unit for controlling the turbine. All I/O signals are read andwritten from the CSDB, and all sequencing runs by reading and writing CSDBsignals.

When the panel is first created there are some "fixed" or "permanent" signals locatedin the CSDB. These signals will always exist, and can not be renamed or moved. Inaddition, 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 alsodetermined, 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 outof a certain type of signal (such as PushButtons or Control Constants) there is noway to add more without a PROM change.

DDLOCATE uses this information (obtained from the PROM subdirectory) todetermine how to layout the rest of the signals in the CSDB. It does this by reading aset of assignment files (*.ASG) which indicate the signals that should be added to theCSDB. For each signal to be added, the type of signal that is required is used todetermine which region of the CSDB will be used to store that signal. HardwiredI/O signals use the name of the input or output to land the signal on an exacttermination point on an I/O card. Software signals simply indicate the type of signaland let DDLOCATE determine the exact location in memory. When done,DDLOCATE writes out the final configuration of the CSDB, which is stored in theUNITDATA.DAT file.

152 • Chapter 6 Configuration GEH-6126

DDLOCATE is a command line utility, but is typically run through the use of theMK5MAKE batch file. It accepts as its command line parameters the list ofassignment files (*.ASG) that contain the signals for it to assign. Each time it is run itcreates a new CSDB layout from scratch; it is not used incrementally. (Toincrementally add a signal, edit the *.ASG file to include the new signal and rerunMK5MAKE.) If run with the parameter "/?" a help screen will be provided:

Assign Files

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>

GEH-6126 Chapter 6 Configuration • 153

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 standardoptions

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 specificinformation.

The basic formats for the assignment files is as follows:

;HARDWARE ASSIGNMENTS

<hardware_name> <software_name> <scale_name>

;SOFTWARE ASSIGNMENTS

?<software_type> <software_name> <scale_name>

There is no required order in the *.ASG files, they are processed in the order that theyare read. Any line that starts with a semi-colon is treated as a comment line andignored.

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 softwaresignal must be mapped to. The scale_name parameter defines how the signal shouldbe scaled for display, and must match one of the scale code names in the scale codefiles (ENGLISH.DAT, METRIC.DAT, HARDWARE.DAT, and CUSTOM.DAT) files.

Software assignments assign a spare signal in a specific region of the CSDB to thegiven signal name. The software_type is used to indicate which region of the CSDBthe signal should be stored in. (A list of the region types is included in the header ofthe 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 softwareassignment.

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. TheMark V uses a "B" for a signal that must be in the <C> (and optional <D>) controller,and a <Q> for a signal in the <R> (and optional <S> and <T>) controller. The MarkV LM only uses <Q>.

The "sss" indicates a sub-class of signal, and these subclasses include:

<none> - 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)

154 • Chapter 6 Configuration GEH-6126

In some cases an array of signals is needed. Each signal in the array has its ownname, but the entire array must be in continuous memory locations. This is doneusing an array assignment in the form shown in the example below:

;ARRAY ASSIGNMENT EXAMPLES?<software_type> * Name1,Name2,Name3,Name4 <scale_name>?<software_type> *4 Name1,Name2,Name3,Name4 <scale_name>;Multi-line example?<software_type> * Name1,Name2,Name3,Name4,Name5,Name6, Name7,Name8,Name9 <scale_name>

An asterisk as the second word on the line indicates array assignments. This asteriskcan have an optional count of the number of signals to follow immediately after theasterisk, as long as the asterisk and the count are one "word". If the count isincluded, a warning will be issued if the required number of signals is not found. Ifno count is given, the number of signals found is used as the number of signals in thearray. The list of signal names must be one "word", with no white space betweensignal names. A comma is used to separate each signal name. The list of signalnames can be split over multiple lines by ending the line with the comma, whichindicates that another signal name will follow.

DDUTILDDUTIL is a command line utility program that will check a unit’s CSDB layout forobvious errors. It does this by checking the UNITDATA.DAT file in the unitconfiguration directory for cases where multiple signals share the same memorylocation, or two different signals were given the same name. It also has the ability tosort 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.DATfile, the sorting is only to make it handy to find signals when viewing or printing thefile.

The UNITDATA.DAT file in the unit configuration directory defines the layout of thesignals in the unit’s memory. There are a few isolated conditions where a mistake inthe configuration can cause a signal to be defined multiple times. This can causeproblems since the name of a signal must uniquely define the signal’s memorylocation in the unit.

DDUTIL will scan the UNITDATA.DAT file looking for cases where multiple signalsshare the same memory location, or separate memory locations share the same signalname. If either of these cases is found, a warning message is displayed. If anyinvalid characters are found in any of the numeric fields of the file, a warning willalso be issued.

If the SORT command line option is used, the original file will be copied to the fileUNITDATA.BAK, and a new signal name sorted version of UNITDATA.DAT will bewritten. The sort will not be performed if there were any invalid entries found, butsorting can be done if there were duplicates found.

DDUTIL is a command line utility run from the unit configuration directory. (It is runas part of the standard MK5MAKE procedure.) If run with the "/?" command lineparameter, a help screen will be provided.

If no errors are found then no messages will be generated during the scanningprocess. If the SORT option was used, a message indicating that the file was sortedwill be printed.

GEH-6126 Chapter 6 Configuration • 155

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 nameorder.

F:\UNIT1>DDUTIL SORT

SORTING COMPLETE: UNITDATA.DAT IS NEW FILE, UNITDATA.BAK IS OLD.

F:\UNIT1>

MK5MAKEMK5MAKE is a batch file that contains the commands typically used when rebuildingthe 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’sconfiguration tables, validate the unit’s alarm list, and recompile sequencing. Theseare 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 helpssimplify that task by running the various tools used to configure the unit in thecorrect order. MK5MAKE is typically run when signals are added to the unit, orparameters on the signals have been changed, such as its scale code.

When run, MK5MAKE performs the following steps:

DDLOCATE is run to lay out the CSDB with the new signal definitions. It is run usingthe following assignment files: IO.ASG FACTORY.ASG ALLOCSSP.ASG SITE.ASG

DDUTIL is run to validate the new layout, and is run such that it sorts the resultingUNITDATA.DAT file

The Table Compiler (TABLE_C) is run to recompile all tables downloaded to theunit

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 theSequence 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 ispassed directly to the Table Compiler (TABLE_C). In the IDP Product, this was usedto change the scale codes set from the default of ENGLISH to a user specified scalecode 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 Compilerwill scan those four scale code sets looking for the matching engineering unitsspecified in the Table Compiler input file.

MK5MAKE creates a log file that is basically the concatenation of the output fromrunning each individual tool. This file is stored as the MK5MAKE.LOG file in theunit configuration directory.

156 • Chapter 6 Configuration GEH-6126

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

---> <Q> segment: F:\UNIT1\SEQ_TRN1.src

... 177 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 --------

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>

GEH-6126 Chapter 6 Configuration • 157

FMVID

OverviewThis 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 FuelMetering Valve (FMV) ID table in a Mark V LM controller. The FMV ID table isused to prevent the unit from trying to run if the required Fuel Metering Valvelinearazation 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 linearazationtable 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 VLM with a linearazation table that does not match the actual valve in use will causeunexpected variations in the fuel flow rate.

To try and prevent these mismatches, each linearazation table has in its ID field theserial number of the valve that it is calibrated for. The Mark V LM control needs tomatch this ID to the actual valve in use, which is where FMVID comes in. FMVIDis how you configure a panel to tell it what valve is actually being used. FMVID isused to display and configure the actual FMVs used in the panel. This information isstored in a special section of the panel’s non-volatile memory. This program readsand 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 numberinformation in the non-volatile memory with the tables downloaded in theLinearazation Data Base (LDB). If the part number and serial number in the FMVID table does not match the part number and serial number in the LDB table, theMark V LM will not allow the unit to be started.

OperationFMVID is a command line configuration program. It requires the name of the unit asa command line parameter. If no additional parameters are given, it will display theFMV IDs stored in the unit.

If run with the /SET option, it will change the FMV ID in the unit to match the serialnumber information in the /SET command. The format of the /SET option is:

FMVID /SET=<NUM>:<PART_NUM>:<SERIAL_NUM>

where <num> is the FMV number, starting with the number one (1) for the firstvalve. The <part_num> is the part number field, which is the part number for thevalve. The <serial_num> field is the serial number as defined in the linearazationtable for that particular valve.

158 • Chapter 6 Configuration GEH-6126

Multiple /SET commands can be given in the FMVID command line. They will beprocessed from left to right. If a valve number is repeated, the last entry will be theone used.

After all /SET commands have been processed, the non-volatile memory in the unitwill 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, asshow 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 <UnitName> [/SET=<num>:<part>:<serial>] 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=<num>:<part_num>:<serial_num> 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

OverviewLDB2RAM is a dynamic configuration tool that allows an individual LinearazationDataBase (LDB) table to be downloaded to the RAM of a Mark V LM. This allowsfor adjustment of the linearazation factors for the run time system without changingthe permanent configuration. Only LDB tables that have the ADJUSTABLEattribute set can be dynamically downloaded into RAM.

When a Mark V LM panel is reset or powered up, it will read the LDB tables fromthe LDB.AP1 unit configuration file and load those tables into RAM. The unit thenuses these RAM based tables for control.

Each table has an attribute indicating if the table is ADJUSTABLE or not. If a tableis not ADJUSTABLE, then the only way to change the table is to recompile it anddownload the unit. On the next restart or power-up the new table will be used. If thetable is ADJUSTABLE then it can be downloaded directly into RAM.

LDB2RAM allows a user to make changes to these RAM resident LDB tables. This isaccomplished by editing the LDB table definition in the HMI and then using theLDB2RAM utility to download that table directly into the RAM of the unit, where thechanges will take effect immediately. Since the LDB.AP1 file in the unit has notbeen changed by this process, restarting the unit will reload the original table intoRAM. (The file on the HMI, however, will have to have the changes undone inorder to prevent the changes from being downloaded during the next panel compileand download.)

In order to be able to download an LDB table to RAM, the following conditionsmust be met:

GEH-6126 Chapter 6 Configuration • 159

• 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

OperationTo change an LDB table in the unit RAM, first make the changes to the appropriateLDB table in the unit configuration directory on the HMI. (You may wish to save abackup 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 LDB2RAMutility. LDB2RAM needs to know which unit to download, and it needs to knowwhich table to download. The unit is specified using the "/UNIT=<unit_name>"qualifier. The table can be specified by using either the file name or the tablenumber, through the use of either the "/FILE=<file_name>" qualifier or the"/TABLE=<table_number>" qualifier. The associated file is compiled anddownloaded directly to the unit.

If run with no command line values or with a command line parameter of "/?" a helpscreen 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=<unitname> [/TABLE=<number>] [/FILE=<filename>] <unitname> is the name of the unit <number> is the number (decimal) of the table to download <filename> is the name of the file to be downloaded

F:\UNIT1>

160 • Chapter 6 Configuration GEH-6126

LDBCHK

OverviewLDBCHK is a command line configuration utility that is used on a Mark V LM todetermine if any of the Linearazation DataBase (LDB) tables are different in theunit’s RAM versus the unit’s LDB.AP1 configuration file. This will indicate if anychanges were made using the LDB2RAM utility since the last panel reset or power-up.

When a Mark V LM control is reset or powered up, it reads the LDB.AP1configuration file and loads the LDB tables found into RAM. The panel then runsusing these RAM resident tables.

A utility program exists (LDB2RAM) that can dynamically change the contents ofthe RAM resident LDB tables. Use of the LDB2RAM program will result in thecontents 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 ofthe RAM and the LDB.AP1 file, giving a list of the changes that were made.

OperationLDBCHK 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 noparameters or the "/?" parameter, it will provide a help screen, as shown in theexample below:

F:\UNIT1>LDBCHK /?LDBCHK - LDB Table Check Utility This program will check the LDB Table definitions in the given unitand 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 <UnitName> <UnitName> - The name of the unit to be checked.

F:\UNIT1>

ALARM_L

OverviewALARM_L is a command line utility program that will generate a printable list of allof the process alarms that a unit can generate, complete with the signal name andalarm text for each one. The resulting alarm list file (ALARM.LST) includes awarning section if there are any alarms defined that do not have any associated alarmtext 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 listingthat ALARM_L created (the ALARM.LST file) was typically printed and hung on thedoor of the Mark V control. This provided a way to look at the process alarmnumber and see the alarm text, as well as the name of the signal that created thatalarm.

This alarm listing has also been useful when connecting the HMI to a DistributedControl System (DCS), since it provides a list of all of the process alarms generatedby each turbine control.

GEH-6126 Chapter 6 Configuration • 161

The last section of the alarm list (if needed) defines all of the alarms that have beendefined, but do not have any alarm text strings defined. This is handy during the unitconfiguration to catch any alarms that don’t have text strings defined for them yet.

OperationALARM_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 containingthe 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

OverviewThe Demand to Source Conversion Program, DM22SRC.EXE, converts theDemand Display binary storage file to a text format for easy editing by hand. Theprogram has a reverse option, which converts the text source file back to a binarystorage file. It is a command line program, not a Windows program. Refer to adescription of the Demand Display program later in this document.

Refer to the section on the Demand Display for a description of the Demand Displaybinary 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 filesproduced by this program.

162 • Chapter 6 Configuration GEH-6126

;;; 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 <num> TITLE "<title>" TYPE "<display type>" |; +-----------------------------------------------------------------+;; DISPLAY RECORD: One of the displays defined. These must; start in the first column.;;; <num> is the decimal unit number. This must match the description; in the F:\CONFIG.DAT file.;; <title> is the title of the display. (Limited to 25 characters.);; <display type > is the type of the display. Only two types are; allowed: Dictionary and Point;;; +------------------------------------------------------------------+; | P "unit" "pointname" |; +------------------------------------------------------------------+;; 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)

GEH-6126 Chapter 6 Configuration • 163

;; <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.;;

164 • Chapter 6 Configuration GEH-6126

;P unit-pointname;- ---- -------------- P "" "L4";;T Text line1 Text line2 BT unit-command-name unit-feedback-name F T value;- ---------- ---------- -- ---- -------------- ---- -------------- - - ------ T "LOAD" "SETPOINT" # "" "L90PSEL_CMD" "" "" 0 = 0x00;;P unit-pointname;- ---- -------------- P "" "L52GX" P "" "L90PSEL_CMD" P "" "DWATT" P "" "TTXM" P "" "" P "" "L1X";;T Text line1 Text line2 BT unit-command-name unit-feedback-name F T value;- ---------- ---------- -- ---- -------------- ---- -------------- - - ------ T "START" "" ? "" "L1START_CPB" "" "L1X" 1 = 0x04;;P unit-pointname;- ---- -------------- P "" "L2TV" P "" "L14HM" P "" "L14HS" P "" "L3";

DM22SRC.EXE Source File Output Example

The following examples show the Demand Display screens from DEMO.DM2corresponding to the DEMO.SRC source file.

• Demand Display Menu File

• Demand Display screen (empty)

• Demand Display Screen “Logics”, a Dictionary based Display. Can show giventypes of points and classes of points.

• Demand Display Screen “Demonstration”, a Point based Display. Populated byuser-selected points and user defined commands.

GEH-6126 Chapter 6 Configuration • 165

Demand Display Menu Screen Example

Demand Display Screen (empty) Example

166 • Chapter 6 Configuration GEH-6126

Demand Display Dictionary Based Using Logics Example

Demand Display Points Base Display, User Defined, Example

GEH-6126 Chapter 6 Configuration • 167

Starting The Demand Display to Source ConversionProgramThe Demand to Source Conversion Program, DM22SRC.EXE, is a command lineprogram, not a Windows program. The program has a reverse option, whichconverts the text source file back to a binary storage file.

To convert a Demand Display binary file (*.DM2) to a text source file (*.SRC), changedirectories to the location of the *.DM2 file, typically F:\RUNTIME. Then enter:

DM22SRC.EXE filename

It is not necessary to enter the file extension as the program will append theappropriate extension. The output file will have the same name with a *.SRCextension.

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), changedirectories to the location of the *.SRC file. Then enter:

DM22SRC.EXE FILENAME /R

It is not necessary to enter the file extension as the program will append theappropriate extension. The output file will have the same name with a *.DM2extension.

Note This procedure will overwrite an existing binary format file with the samename.

The program will display an error message and halt execution if it encounters anerror in the *.SRC file.

Editing the Demand Display Source FileThe Demand Display Source File may be edited by any word processor that can usea fixed pitch font and save to a text format. The rules for formatting the text file aredescribed in the source file example earlier in this document.

Each display must have a Title, which:

• Defines which unit number the screen is applied to.

• Defines the screen title

• Defines the display type

• There are two types of displays:

• Dictionary Based

• May contain only specific point types, and/or point classes.

• They do not contain commands.

• Point Based

• Contain user-defined points.

• May have user defined commands (command spacing is no closer than everyfourth line to prevent overlap.)

168 • Chapter 6 Configuration GEH-6126

CONSTSET

OverviewCONSTSET is a configuration utility used for Mark V turbine controls to make allcontrol constants that are defined adjustable, and to set the default ramp rate for eachcontrol constant. (It is not used for the Mark V LM.)

In previous generations of Operator Interfaces, all control constants were adjustablethrough the Control Constants Display. The HMI now supports a user-controlled listof 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 thatconstant 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 constantconfiguration where all control constants are defined as being adjustable, and thedefault ramp rate is the same rate as used in the IDP Operator Interface. It is used inMark V applications to have the HMI emulate what the previous generation ofoperator interface did, without having to configure each control constant by hand.

Note As of TCI Version 1.2, the CONSTSET.DAT file is still required, but a newoption to automatically generate the default values at Data Dictionary load time hasbeen added. Using this new option eliminates the need for running the CONSTSETprogram at all. (See the application information at the end of this section for moredetails.)

OperationCONSTSET is a command line configuration utility. It requires one command linequalifier, 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, ahelp 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: CONSTSET /UNIT:<unitname>

F:\UNIT1>

The next example shows a sample of the CONSTSET.DAT file, the output of theCONSTSET 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 ValueAFKQG "CNT09" 0.1AFKQPC "CNT05" 0.001AQK0_B "#/sec" 0.01AQK0_E "#/sec" 0.01

GEH-6126 Chapter 6 Configuration • 169

<…and so on…>

Application InformationStarting with TCI Version 1.2, there is an easier way to have the unit generate theMark V default ramp rates than through the use of the CONSTSET program. A newoption was added to the CONSTSET.DAT file that will cause the Data Dictionaryloader to recalculate the default ramp rates and set each control constant to beadjustable while loading the points into the Data Dictionary. This scheme has theadvantage that any additions to the control constants (or new control constants) willautomatically be picked up when TCI is restarted with no additional configurationwork required.

To use this new option, create a CONSTSET.DAT file that contains as its first dataline a line with the option name "*MARK V_DEFAULT". This special line will triggerthe Dictionary Loader to set every control constant as adjustable, and set the ramprate according to the default scale code table. The results of this are the same as theresults of running CONSTSET. If desired, additional lines can be added to theCONSTSET.DAT file to override these defaults. This allows a user to make somecontrol constants non-adjustable or to change the default ramp rate. Make sure thatany lines changing the defaults are after the "*MARK V_DEFAULT" line, or else thelines will be overridden when the defaults are computed.

170 • Chapter 6 Configuration GEH-6126

The next example shows a CONSTSET.DAT where the default values are computedwhen 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;

CONSTCHK

OverviewCONSTCHK is a command line configuration utility that displays control constantsthat have a different value between the unit’s RAM and the unit’s non-volatilestorage. It is useful in determining which control constants have had their RAMvalues changed since the unit was last reset or powered up.

When a turbine control is reset or powered up, it reads the control constant valuesout of non-volatile memory and loads the values into RAM. The panel then runsusing these RAM resident values.

The Control Constant Adjust Display can dynamically change the contents of theRAM resident control constants. Use of the Control Constants Adjust Display willresult in the contents of the RAM and the contents of the non-volatile memory valuebeing different. CONSTCHK is a utility program that will outline the differencesbetween the contents of the RAM and non-volatile storage, giving a list of thechanges that were made.

OperationCONSTCHK is a command line utility program that is typically run from a DOSprompt. It needs one command line parameter, the name of the unit to check. If runwith no parameters or the "/?" parameter, it will provide a help screen.

Normally the program reports only the values of control constants that have differentvalues between the RAM and the non-volatile memory. If the "/ALL" qualifier is usedon the command line, all values will be displayed.

GEH-6126 Chapter 6 Configuration • 171

ExampleThe following example shows a check of a Mark V unit. Two control constants werefound where the value in RAM was different than in non-volatile storage. (TheMark V uses an EEPROM for its non-volatile storage.)

F:\UNIT1>CONSTCHK T1...Site: HMI Development...Unit: T1...Time: 03-DEC-1997 11:58:15

... Name Units RAM (CSDB) EEPROM

...--------- -------- ------------ ------------LK90PSEL "MW" 24.0 22.6LK90SPIN "MW" 3.0 4.0

...There were 2 Control Constants with different values.

F:\UNIT1>

The following example shows a check of a Mark V LM unit. Seven controlconstants were found where the value in RAM was different than that in non-volatilestorage. (The Mark V LM uses an AP1 file on its internal hard drive for its non-volatile storage.)

F:\UNIT2>CONSTCHK T2...Site: HMI Development...Unit: T2...Time: 03-DEC-1997 11:59:28

... Name Units RAM (CSDB) AP1

...--------- -------- ------------ ------------K39VTT_TD "sectd" 0.015 0.000KOTRDITH_M "%" 3.09 0.00KOTRR_LAG "secrt" 10.00 0.00KOTRR_LEAD "secrt" 5.38 0.00KPLTR_LEAD "secrt" 5.88 0.00KPLTR_NLMT "%" 3.19 0.00KPLT_BIAS "%" 3.19 0.00

...There were 7 Control Constants with different values.

F:\UNIT2>

SEQCOMPL (Sequencing)

OverviewThe Control Sequence Compiler is a separate command line program that compilesCSP 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 othersections of this document for more information on the MSTR_SEQ.CFG file. TheSequence Compiler is a command line program, not a Windows program.

!Caution

Only qualified personnel knowledgeable about turbinecontrol and protection should use the SequenceCompiler. Improper use may adversely affect the controland protective features of the control system.

172 • Chapter 6 Configuration GEH-6126

File StructureThe output of the Sequence Compiler is an *.AP1 file (or files) that can bedownloaded to the unit control. The downloadable sequencing filename is SEQ.AP1for Mark V LM. The downloadable sequencing filenames are SEQ_B.AP1 andSEQ_Q.AP1 for Mark V. Please refer to the section on the Downloader for moreinformation on how to download the files to the unit control. The program alwayswrites a text log file - MSTR_SEQ.LOG in the unit configuration directory.

Along with the segment source files, the Control Sequence Compiler uses severalunit specific files that contain signal name database definitions and definitions of theavailable software building blocks. The following Figure is a summary of thesefiles. PRIMITIVE.DEF and BIGBLOCK.DEF files are ASCII files that detail theprogramming blocks available for the particular unit control. UNITDATA.DAT is adata dictionary file the Control Sequence Compiler uses to check the validity ofpointnames used in the segment source files.

UNITDATA.DAT

PROM\PRIMITIVE.DEF

PROM\BIGBLOCK.DEF

SEQCOMPL.EXEControl

SequenceCompiler

MSTR_SEQ.CFG

Segment1

Segment2

Segment name.SRC

SEQ_B.AP1(Mark V)

SEQ_Q.AP1(Mark V)

SEQ.AP1(Mark VLM)

Sequence Compiler Block Diagram

Executing the Sequence Compiler Selecting the Control Sequence Compiler icon or typing SEQCOMPL or hittingenter while at a command prompt in the unit specific directory initiates the compilingprogram. The Control Sequence Compiler creates a listing, MSTR_SEQ.LOG, of theerrors (if any) found in the segments. These errors must be resolved by using theSequence Editor program to make appropriate changes to the sequencing source file(or files) (*.SRC). The *.AP1 output files will not be produced until the SequenceCompiler executes error free. A sample Sequence Compiler execution follows:

GEH-6126 Chapter 6 Configuration • 173

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 --------

Master Sequencing Configuration FileThe Master Sequencing Configuration File, MSTR_SEQ.CFG, governs whichsequencing source files are compiled for which controller in the unit, and at what ratethe segments are executed within the control. It is a text file, which may be modifiedby any word processor. The file is located in the unit configuration directory,typically F:\UNITn.

!Caution

Only qualified personnel knowledgeable about turbinecontrol and protection should modify the MasterSequencing Configuration File, MSTR_SEQ.CFG.Improper use may adversely affect the control andprotective features of the control system.

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 textrepresentation of the AP1 file to be downloaded to the unit. Typically, this directiveis preceded by a ‘.’ to convert it to a comment.

174 • Chapter 6 Configuration GEH-6126

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 willnot be able to execute after it is downloaded. The BIGBLOCK.DEF file revision mustmatch the prom revision in the unit control.

The following listing is a sample MSTR_SEQ.CFG Sequence CompilerConfiguration 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.

The “#B_SEGMENTS” tag indicates sequencing for the <C> & <D> processors.(Mark V only)

The “#END” tag indicates the end of the document information.

GEH-6126 Chapter 6 Configuration • 175

The following example demonstrates the Frequency and Skew features:

Segment Frequency n Skew within scan rate

name power of 2 (>0) (units of 1/16 sec)

W 1 0

X 2 0

Y 2 1

Z 8 3

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 MarkV 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 Z Z Z Z Z Z Z

| | | | |

| | | | | | | | |

| | | | | | | | | | | | | | | | |

|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|

0123456789ABCDEF

0.0sec 0.5sec 1.0sec 1.5sec 2.0sec 2.5sec 3.0sec 3.5sec 4.0sec

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 byone frame.

Segment Z is executed every eight frames, for a 2 Hz execution, and is skewed bythree 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, issimilar to the one for Mark V, except scan rate and offset replace frequency andskew.

176 • Chapter 6 Configuration GEH-6126

The following example (MSTR_SEQ.CFG Sequence Compiler Configuration FileExample for Mark V LM) shows the file for a Mark V LM. The scan rate governs howoften 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

GEH-6126 Chapter 6 Configuration • 177

SEQDOCMT (Sequencing)

OverviewThe Control Sequence Documentor is a separate command line program thatproduces a CSP control document. The CSP document is a text file that contains arepresentation of the CSP control program. This document is used by field serviceand maintenance personnel to check out and debug the unit control. It is also used asa 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 othersections of this document for more information on the MSTR_SEQ.CFG file. TheSequence Documentor is a command line program, not a Windows program.

File StructureTwo files are produced by the CSP Documentor program. The first, CSP.PRN, isa complete representation of the control. The second, CSP_XREF.PRN, is a signalname cross-referencing document. Both of these files will be located in the unitconfiguration directory.

CSP.PRN

The CSP.PRN document is a text file pre-formatted with page breaks to form acomplete document. The CSP.PRN is a complete representation of the unit CSP(Control Sequence Program). It may be viewed with any word processor with afixed pitch font with line drawing characters. It is best to print this document withthe CSP Printer program as it will adapt the format of the document to the selectedprinter. 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 pagenumber within the segment. Each rung starts with a rung number followed by agraphic representation of the rung and finishing with signal and cross-referencinginformation. More than one rung may appear on any page.

178 • Chapter 6 Configuration GEH-6126

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

CSP.PRN Sequence Documentor Output Example

GEH-6126 Chapter 6 Configuration • 179

CSP_XREF.PRN

The CSP_XREF.PRN document is a text file pre-formatted with page breaks to forma complete document. The CSP_XREF.PRN is a cross-reference document whichcontains a list of signal names with the segment and rung number where the signal isused. It may be viewed with any word processor with a fixed pitch font. It is best toprint this document with the CSP Printer program as it will adapt the format of thedocument to the selected printer.

A CSP_XREF.PRN Sequence Documentor Output example is shown below.

Along with the segment source files, the Control Sequence Documentor uses severalunit specific files that contain signal name database definitions and definitions of theavailable software building blocks. PRIMITIVE.DEF and BIGBLOCK.DEF files areASCII files that detail the programming blocks available for the particular unitcontrol. UNITDATA.DAT is a data dictionary file that contains the pointnames andtypes used in the segment source files. *.PIC files are used for the primitive and BBLblock graphics. *.SCA files contain the engineering units. The LONGNAME.DATfile contains the corresponding signal long names.

180 • Chapter 6 Configuration GEH-6126

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 LOGIC

SEQ_640 -8

CPCVRATEVAL -- N/D

SEQ_0 -14 SEQ_640 -8

CPCV_MAN -- RATIO OF SPECIFIC HEATS (CP/CV) FOR MANUAL SELECTION N/D

SEQ_640 8

CPCV_PVGOOD -- RATIO OF SPECIFIC HEATS (CP/CV) FAULT TIME DELAY N/D

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 N/D

SEQ_0 -14 SEQ20_1 42 SEQ20_1 52 SEQ20_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 LOGIC

SEQ_40 -2

D30T2B -- ALMTXT:'COMPRSR INLET TEMP(T2B) SENSOR FAILED' AL 38 LOGIC

SEQ_40 -2

D30T2DIFF -- ALMTXT:'T2A & T2B SENSOR DIFFERENTIAL' AL 42 LOGIC

SEQ_40 -2

Executing the Sequence Documentor

GEH-6126 Chapter 6 Configuration • 181

Selecting the Control Sequence Documentor icon or typing SEQDOCMT or hittingenter while at a command prompt in the unit specific directory initiates the compilingprogram. The Sequence Documentor has four possible parameters. They must belisted in order after the SEQDOCMT.EXE command. For example, a valid commandline is shown with all possible parameters:

F:\UNIT1>SEQDOCMT.EXE METRIC.SCA N -LOG F:\UNIT1

The first parameter is the scale code file name. The default is ENGLISH.SCA.

The second parameter is Y or N. 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 fileSEQDOCMT.LOG. The default is -N, no log file.

The fourth parameter is the path to the unitn directory. The default is to use thecurrent default, or working directory.

The Sequence Documentor may display error messages during execution. Theseerrors must be resolved by using the Sequence Editor program to make appropriatechanges to the sequencing source file (or files) (*.SRC) or other unit configurationfiles as needed. The Sequence Compiler should be run any time changes are madeto the files in the unit configuration directory.

SEQEDIT (Sequencing)

OverviewThe Control Sequence Program (CSP), the Turbine Control Panel’s applicationsoftware, uses a programming language known as Big Block Language, or BBL.BBL is a relay ladder logic based software structure that defines data flow andfunction 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 controlchanges. It is an off-line tool; that is, its changes are made to a source file only. TheSequence 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 compiledby the Sequence Compiler and downloaded to the unit control. The SequenceCompiler and download functions are described later in this document.

The Control Sequence Editor operates on a basic unit of software known as asegment. A segment consists of a series of sequentially executed rungs. The ControlSequence Editor operates on these rungs. The Control Sequence Editor allows fourdifferent types of rungs. Mixing the four rung types within a rung is NOT possible.

The four rung types are:

• RLD rungs. Pure relay ladder diagram rungs.

• PRIMITIVE rungs. Rungs combining RLD operations with a primitivefunctional block call.

• BBL rungs. Rungs without RLD operations, but with a Big Block call. BigBlocks are software modules that perform standardized control functions.

• COMMENT rungs. Rungs containing only text, usually identifying importantinformation about the sequencing or segment.

182 • Chapter 6 Configuration GEH-6126

The Control Sequence Editor creates new CSP segments or edits existing ones.Once the Control Sequence Editor creates the segment source files, the ControlSequence Compiler compiles them into the CSP for downloading to the ControlPanel. The compiler configuration file, MSTR_SEQ.CFG, selects which segmentsto compile and defines a unique scan rate and execution offset for each segment.The downloaded CSP segments provide the Control Panel with the parameters andinstructions on how to control the process.

File StructureThe Sequence Editor operates on segment source files within the unit configurationdirectory, typically F:\UNITn. The files have a *.SRC extension. The CSP segmentsource files have a text format. Never edit the segment source files directly. Use theControl Sequence Editor program to open, modify, and save these files.

Note Other source files in the unit configuration directory have a *.SRC extensionthat are not CSP segment source files. While it is possible to open these files, theyare not sequencing files and their contents could be overwritten if the user attemptsto modify and save them from the Sequence Editor.

GEH-6126 Chapter 6 Configuration • 183

Along with the segment source files, the Control Sequence Editor uses several unitspecific files that contain signal name database definitions and definitions of theavailable software building blocks. The Figure below is a summary of these files.PRIMITIVE.DEF and BIGBLOCK.DEF files are ASCII files that detail theprogramming blocks available for the particular unit control. UNITDATA.DAT is adata dictionary file the Control Sequence Editor uses to check the validity ofpointnames used in the segment source files. It is usually a good idea to restrict theediting of sequencing source files to a single unit at a time as different units mayhave different functions defined in their associated BIGBLOCK.DEF andPRIMITIV.DEF and different signals defined in their UNITDATA.DAT files.

!Caution

Modifications of these files is not necessary, and notrecommended, as their contents correlate directly to thecontents of the unit control’s block library. If a block isadded, modified, or removed from the unit control, thefactory provides new definition files along with new filesfor the controller’s block library.

UNITDATA.DATPROM\

PRIMITIVE.DEFPROM\

BIGBLOCK.DEF

SEQEDIT.EXEControl

SequencingEditor

Segmentname.SRCOriginal or

New sourcefile

The Control Sequence Editor File Structure

Using The Control Sequence EditorEditing a segment requires performing several standard operations. These operationsinclude loading a segment from the disk, creating a new segment, finding an existingrung, creating a new rung, and saving a modified segment to a disk. Using either thedrop-down menu options from the menu bar selections or the buttons on the toolbarperforms these operations.

184 • Chapter 6 Configuration GEH-6126

This section provides information concerning the use of the following functions:

• Starting the Control Sequence Editor and Loading a segment(s)

• The Control Sequence Editor Window

• Navigating within a segment(s)

• Editing a rung(s)

• Selecting a rung(s)

• Copying a rung(s)

• Moving a rung(s)

• Adding/Deleting a rung(s)

• Creating a rung(s)

• Viewing multiple segments

• Saving a segment

• Exiting the Control Sequence Editor

Starting The Control Sequence EditorSelecting the Control Sequence Editor icon or typing SEQEDIT and hitting enter atthe command prompt or in the Start Menu Run Dialog Box starts the ControlSequence Editor. Typing SEQEDIT Segment name.SRC and hitting enter passes thename of the desired segment to the Control Sequence Editor, where Segment name isthe name of a segment file. Insert a space between SEQEDIT and the segment nameand include the file extension .SRC. When accessing the Control Sequence Editorfrom 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 toopen a segment file for editing. The Control Sequence Editor allows openingmultiple segments, each in a separate segment window within the Control SequenceEditor.

Loading An Existing SegmentThe Control Sequence Editor loads existing segments in three ways. If the ControlSequence Editor starts from the command prompt, type the name of the segmentafter the Control Sequence Editor execution command, SEQEDIT. Include thesource extension, .SRC with the segment name. For example:

F:\UNIT1>SEQEDIT Segment name.SRC

Where Segment name.SRC is a sequencing segment filename such as SEQ_160.SRC.

To load an existing segment after starting the Control Sequence Editor, select themenu option File:Open command from the drop-down menu. The Control SequenceEditor provides a list of files with .SRC extensions. Not all of these files aresequencing segment source files. Select the desired file and hit enter to load thesegment. Selecting the toolbar button with the picture of an open file also provides alist of existing files. To load a recently edited segment, select the menu bar optionFile and the segment name from the drop-down menu.

GEH-6126 Chapter 6 Configuration • 185

Loading A New SegmentIf no existing file is specified when the Control Sequence Editor starts, a blankscreen displays. To start a new segment window, select the menu bar optionFile:New command from the drop-down menu.

Note Exiting a new segment file without saving it loses the file.

The Control Sequence Editor WindowThe Control Sequence Editor operates in a Windows environment. Using theControl Sequence Editor is similar to using other Windows applications. TheControl Sequence Editor performs functions selected from drop down menu optionsfrom the menu bar or buttons on the toolbar. The titlebar displays the filenamecurrently in the Control Sequence Editor. The Control Sequence Editor opens eachsegment in a separate segment window. The segment window displays the segmentone rung at a time. RLD rungs display on a an 8x8 matrix. Primitive rungs displayusing a 4x8 permissive matrix and a tile representation of the primitive. Big Blocksdisplay as a tile representation of the Big Block. The horizontal and vertical scrollbars allow viewing portions of rung/blocks that exceed the segment windowboundaries.

The Sequence Editor Window Showing an RLD Rung

The menus and toolbar at the top of the screen incorporates items common toWindows applications along with special items associated with the Control SequenceEditor. The toolbar immediately beneath the menu bar corresponds to particulardrop-down menu options. The toolbar buttons allow short cuts to common menucommands.

186 • Chapter 6 Configuration GEH-6126

Navigating Within a Segment WindowIndividual rungs make up the sequencing segments. Navigating within the segmentinvolves moving about the rungs. The top right hand corner of the segment windowdisplays the rung number. Navigate between the rungs using drop-down menuoptions from the menu bar, toolbar buttons, or the page up and down keys on thekeyboard. The Edit:Find menu selection locates a signal name or block namewithin a given segment. No tools are provided to search all sequencing segmentsource files.

Editing an Existing RungThe Control Sequence Editor allows for editing existing rungs. Double clicking onan RLD component or name within a BBL or Primitive block accesses the signalname point list dialog box for changing the associated control signal name.Selecting a component from the Component menu bar option or from the toolbarand doubling clicking on the addition location adds a component or changes anexisting component. The signal name point list dialog box selects the new controlsignal name. Selecting Edit:Comment from the menu displays the text window withthe existing comment text. The text window allows modifying text or addingadditional text to the comment rung. Changing BBL blocks and Primitive blocksdeletes the components on the rung. Changing the rung type also deletes the rungcomponents. Selecting the Delete Element from the Component menu selectionand double clicking on the component deletes the component. Adding componentsto the resulting gap in the rung is necessary for proper function of the rung.

Selecting RungsSelecting rungs allows access for copying, editing, or deleting. Navigating to therung and selecting the menu bar option Edit and the Select command from the drop-down menu highlights the rung to indicate its selection. Repeating the selectionprocess for other rungs selects multiple rungs. Selecting the menu optionEdit:Deselect deselects the rungs.

Copying RungsThe Control Sequence Editor allows for copying of rungs within a segment windowor to another segment window. Navigate to the rung and select it using the menuoption Edit: Select. The rung highlights. Select the Edit:Copy menu item.Navigate to the insertion point and select the menu bar option Edit:Paste. TheControl Sequence Editor inserts the copied rung and re-numbers the following rungs.Selecting Paste in other locations inserts the copied rung again. Copying multipleselected rungs and pasting them copies the selected rungs and inserts them to thenew location. Toolbar buttons also perform copy and paste functions.

Once a rung is selected and copied, the Control Sequence Editor permits copying toanother segment window. Exiting the existing segment window and opening thenew segment window, or opening a new segment window both allow for copying therung from one segment to another. Copying the rung to another segment follows theabove procedure.

GEH-6126 Chapter 6 Configuration • 187

Moving RungsThe Control Sequence Editor allows for moving one rung or multiple rungs. Theprocedure is identical to that of copying rungs except the menu option Edit: Cut isused to remove the rung and re-number the following rungs. Navigating to the newlocation for the rung and selecting Edit:Paste inserts the rung to the new locationand re-numbers the following rungs. Cutting and pasting multiple selected rungsremoves all selected rungs and inserts them in the new location. Toolbar buttonsalso perform the cut and paste functions.

Adding A RungThe 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 menuoption Rung:Add. The Control Sequence Editor displays a dialog box to selectadding the rung before or after the current rung. The selection adds a blank RLDrung and re-numbers the following rungs.

Deleting A RungThe Control Sequence Editor allows deleting rungs. Navigate to the desired rung.At the rung, select the menu option Rung:Delete. The Control Sequence Editordisplays a dialog box requesting confirmation of the deletion. Deleting a rung ispermanent. Only exiting the Control Sequence Editor without saving restores adeleted rung. There is no undelete selection. To cancel a delete, select the Cancelbutton in the confirmation window.

Selecting The Rung TypeNew rungs are one of four different rung types:

• RLD (relay ladder logic alone)

• Primitive (a basic block with relay ladder logic)

• BBL (one large block alone)

• COMMENT (text only)

Selecting the Rung:Type menu item displays the Modify Rung Type dialog box thatallows the choice of one of the four rungs.

Choosing the RLD rung type displays a blank grid for adding components. Selectingthe BBL or PRIMITIVE rung types displays another dialog box to choose whichBBL 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. TheCOMMENT rung type displays a blank screen without the RLD grid.

Adding RLD RungsSelecting the RLD rung type displays a blank RLD grid on the screen. Selecting theComponents menu option displays a drop-down menu of the different possiblecomponents. Selecting a component from this menu allows for its addition on thegrid. The new rung must begin at the top left grid line and end at the top right gridline. Double clicking on the grid line adds the component to that location. A SignalName dialog box displays if the component is a normally open contact, normallyclosed contact, coil or inverted coil. This dialog box allows for typing the controlsignal name or for “Browsing” the control signal name database to select the controlsignal for that component. If the control signal name is invalid or the type of signal is

188 • Chapter 6 Configuration GEH-6126

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 followstandard relay ladder logic format. Selecting Component:Delete Component fromthe menu and double clicking on the component deletes a component. Using thetoolbar buttons representing components allows for quick component additions anddeletions.

The menu bar option Component has six commands available for editing RLDrungs and the RLD section of Primitive rungs. The drop-down menu commandNOC represents a Normally Open Contact component selection, while the NCCcommand represents a Normally Closed Contact selection. The HOR drop-downmenu command represents a Horizontal connector. This selection creates bothhorizontal and vertical connections. Selecting HOR and double clicking on ahorizontal or vertical grid line adds the connector. The Coil and ICoil commandsfrom the drop-down menu select normal Coils and Inverted Coils respectively. TheDelete Element command deletes any components as described above.

Adding Primitive Rungs Selecting the PRIMITIVE rung type displays a Select Primitive Function dialogbox. The Select Primitive Function dialog box displays a list of the availablePrimitives blocks. After selecting one of the Primitive blocks from the list, thePrimitive block tile for that Primitive appears on the right side of the segmentwindow. The left side of the segment window displays the RLD grid for addingcomponents. Primitive blocks automatically include their associated coil. Doubleclicking on locations requiring control signal names displays the Signal Name dialogbox for selecting the control signal name. Primitive blocks typically require signalnames on the coils and any locations indicated inside the primitive tile itself. Doubleclicking on the names inside the primitive tile displays the Signal Name dialog boxfor selecting the associated control signal name. Typically, a primitive blockrequires a contact(s) to enable it. Follow the Adding RLD rungs rules to add theenabling contact(s). Normally open contacts, normally closed contacts, connectors,or combinations are allowed.

Adding BBL RungsSelecting the BBL rung type displays a Select Block Function dialog box. TheSelect Block Function dialog box displays the list of the available Big Blocks. Afterselecting one of the Big Blocks from the list, the BBL tile for that Big Block appearsacross the entire segment window as BBL blocks do not include any RLD rungcomponents. Double clicking on the names within the block displays the SignalName dialog box for selecting the associated control signal name.

Adding Comment RungsSelecting the COMMENT rung type displays a blank segment window. Adding textinvolves selecting the menu option and Edit:Comment or double clicking anywherein 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 thecomment rung. Selecting the Cancel button cancels the text addition and reverts tothe blank comment rung. The Control Sequence Editor allows comments of 40characters wide and 20 lines long.

GEH-6126 Chapter 6 Configuration • 189

Viewing Multiple Segments WindowsThe Control Sequence Editor allows displaying any number of segments at one time.Selecting the menu option File:Open command from the drop-down menu multipletimes opens multiple segment windows. The Window menu option provides achoice for displaying the multiple segment windows. Cascade displays thewindows one after the other, down the screen in an overlapping fashion. Tiledisplays the windows in a tile fashion across the screen, dependent on the number ofwindows 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 theNew command from the drop-down menu. The Control Sequence Editor allowsmultiple windows of the same segment, and all windows of the same segment reflectchanges to one of the segment windows. The latest segment window displays ontop 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 theWindow drop-down menu. A check mark appears in front of the segment name ofthe active window. A segment window chosen from this list becomes the activewindow.

Minimizing a window by clicking on the top left bar button of the window andselecting Minimize removes the segment window from the presentation window byiconizing it. Double clicking on the icon loads the segment window back onto theControl Sequence Editor window. Selecting Maximize enlarges the segment windowto fit the size of the Control Sequence Editor window. Using the cursor to select theside bar of a segment window allows for adjusting of the size of the window, similarto other Window applications. A highlighted title bar on a segment windowindicates the segment window currently selected.

Saving a SegmentSelecting the menu option File:Save or clicking on the toolbar button of a disk savessegments. 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 thedrop-down menu. A Save As dialog box prompts for a new file name and directorylocation. The Save As dialog box appears if the segment was not given a namepreviously and the Save command or Save toolbar button are selected.

!Caution

Saving a segment overwrites the segment losing the datain the initial (unedited) file. It is recommended that priorto editing a segment, copy the segment to a separatelocation. After verifying the saved segment’sfunctionality, delete the old copy of the segment.

Selecting the menu option File:Close closes a segment. A Save As dialog boxappears when closing with new or not yet saved segments and requests whether tosave 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 newsegment.

190 • Chapter 6 Configuration GEH-6126

Exiting the Control Sequence EditorSelecting the menu option File:Exit exits the Control Sequence Editor program. TheSave As dialog box requests whether to save the segment if the current file has notbeen saved. Selecting No exits the Control Sequence Editor without saving thesegment, losing all changes. Selecting Yes saves the segment.

CSPPRINT

OverviewThe Control Sequence Program Printer, is a utility program for printing CSPdocuments using the standard Windows printing support. The CSP documents areimportant as they represent the sequencing used by the Mark V and Mark V LM forcontrol. The CSP file is a pre-formatted file containing all the necessary informationfor pagination. The CSP Printer program uses this information to display and printthe CSP document. The CSP Printer program is intended for use only with CSPdocuments. It is not designed to display or print other document types.

The CSP Printer program cannot edit or modify the CSP Document. Use theSequence Editor to modify the CSP source code. The CSP document is produced bythe Sequence Documentor command line program. After successfully running theDocumentor, 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 specificsabout its operation.

The CSP Printer program can print all or part of the CSP document. It can also berun from the command line without a window to print the entire CSP document tothe default printer.

During the printing process, the CSP Printer program runs at a lower priority to makethe CPU resources available to other processes.

File StructureThe CSP Printer program operates on CSP.PRN and CSP_XREF.PRN files in the unitconfiguration directory. The CSP documents are produced by the SequenceDocumentor command line program. The CSP output document is pre-formattedcontaining all the necessary information for pagination. The CSP Printer program isintended for use with CSP documents. It is not designed to display or print otherdocument types such as text or other word processing documents.

These files may also be viewed with any word processor that has access to a fixedpitch font with the line drawing characters. However, because the CSP documentsare pre-formatted, they may not print correctly from the word processor.

GEH-6126 Chapter 6 Configuration • 191

Using the CSP Printer ProgramThis section provides information concerning the use of the following functions:

• Starting the CSP Printer Program

• The Display Window

• Page Setup

• Printer Selection

• How to Print the CSP

Command Line ArgumentsThe CSP Printer may be launched from the command line with the file name as anArgument to quickly bring the display to a desired configuration:

G:\EXEC\CSPPRINT.EXE F:\UNIT1\CSP.PRN

Only one file name is permitted on the command line.

The parameter "/p" (case sensitive) when entered on the command line along with afile name will cause the entire CSP document to be printed to the default windowsprinter.

G:\EXEC\CSPPRINT.EXE F:\UNIT1\CSP.PRN /P

No program window will appear when using the "/p" parameter, however a dialogbox will appear showing the status of the formatting of the print job and giving theuser the option to cancel the print job.

Screen DescriptionThe CSP Printer is a single document interface, which allows only one CSPdocument to be displayed by the program at any time. More than one copy of theCSP Printer program may be run to view and print multiple CSP documents at thesame time.

192 • Chapter 6 Configuration GEH-6126

The CSP Printer Window

Only one page of the CSP document is displayed at time. Users can use the Pagemenu or toolbar buttons to navigate through the pages of the CSP document. Thewindow title bar shows the CSP document name including the full path, current pagenumber, and total number of pages in the CSP document.

The print preview window displays the active document as it will appear whenprinted. In print preview mode, the main window is replaced with a print previewwindow in which one or two pages will be displayed in their printed format.

Page SetupThe user may adjust the appearance of the page by accessing the Page Setup DialogBox through the File:Page Setup menu selection. This dialog box allows the user asto adjust the appearance of the printed page. The user can select a header to beprinted 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 tothe current CSP display without changing the page setup.

GEH-6126 Chapter 6 Configuration • 193

Printer SelectionThe printer and its available options are accessed through the File:Print menuselection. This brings up the standard Windows Print Dialog Box. Please refer toyour Windows documentation for how to select the printer and its options using thedialog box.

How to Print the CSPTo print the CSP document, start the CSP printer program. Use the File:Open menuselection to open the *.PRN document in the unit configuration directory. Afteropening the document, use the File:Page Setup menu selection to adjust theappearance of the page. Then, use the File:Print menu selection to bring up the PrintDialog Box. Select the appropriate printer and paper options, then select the OKbutton. A dialog box will appear showing the print progress. The user may cancelthe print at any time from this dialog box.

During the printing process, the CSP Printer program runs at a lower priority to makethe CPU resources available to other processes. If a CPU intensive application isrunning, the CSP Printer Program may appear to be stalled. It is not. It is merelywaiting for some free CPU time to resume processing.

TABLE_C (Table Compile)

OverviewTABLE_C is a configuration tool that compiles the configuration tables for Mark Vand Mark V LM units. It takes the configuration information out of the ASCIIconfiguration source files (*.SRC) and converts it to the binary images that the panelneeds. The results are placed into a set of *.AP1 files.

Some of the configuration information for a Mark V or Mark V LM turbine controlis created by editing a set of tables that contain configuration information. Thesetables contain information such as: which signals are to be totalized, which signalsare to be treated as events, and the values of the control constants. These tables areedited 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 thecontents 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. Thesebinary *.AP1 files are downloaded to the unit to provide the table driven configurationinformation.

There are different tables used in the Mark V from in the Mark V LM, and the binaryformat used between the two are different in some cases. TABLE_C looks for theexistence of the VXFR.AP1 file in the unit configuration directory as the indicationof the unit type. If VXFR.AP1 is found, the unit is assumed to be a Mark V LM. IfVXFR.AP1 is not found, the unit is assumed to be a Mark V.

194 • Chapter 6 Configuration GEH-6126

OperationTABLE_C is a command line configuration program that is run from the unitconfiguration directory. It will look to see whether it is configuring a Mark V or aMark V LM and process the tables accordingly. If run with no parameters or withthe "/?" parameter, a help screen will be provided. This help screen will include thelist of tables supported by the unit type.

A few of the table files contain values, such as the control constant values. Thesevalues must be translated from ASCII values to binary values. To do this, a scalecode table is required. By default the ENGLISH.SCA file is used. This can beoverridden by using the "/SCALE=<filename>" qualifier in the TABLE_C commandline.

TABLE_C requires a list of the tables to compile. This list is supplied as parametersto TABLE_C. There is a special parameter "ALL" that will compile all of the tablefiles, as shown in the example below:

F:\UNIT1>TABLE_C ALLTABLE_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 caseTABLE_C determined that the unit was a Mark V.F:\UNIT1>TABLE_C CONSTTABLE_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>

(The "ALL" parameter is also used by MK5MAKE to compile all tables.)

In the preceding example, only the Control Constant table was compiled. TABLE_Cfound that the Control Constant named "COMMHTHY" was defined in the unit, butno value was given for it in the configuration table. It warns that this constant willbe given the value of zero.

GEH-6126 Chapter 6 Configuration • 195

I/O Configuration

EEPROM

OverviewEEPROM is a Mark V configuration utility that downloads the binary configurationinformation from the HMI into the non-volatile memory (EEPROM) in the Mark Vcontrol panel. (EEPROM is not used for the Mark V LM - it uses the UDF programinstead.)

Various configuration tools create the *.AP1 files that define the configuration of theMark V turbine control. These include the Sequence Compiler, the Table Compiler,and the I/O Configurator. These files are stored in the unit configuration directoryfor each unit. These files must be downloaded from the HMI to the non-volatilememory in the control panel for them to take effect. EEPROM is used to copy thesefiles 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 theMark V and the *.AP1 files on the HMI. It also provides a directory command toview the contents of the Mark V EEPROM, and will do a simple sanity check toverify the unit’s EEPROM has not been corrupted.

196 • Chapter 6 Configuration GEH-6126

OperationEEPROM is a command line utility program that is typically run from a DOSprompt. If run with no parameters or the "/?" parameter, help will be provided, asshown 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 USERcategory] 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>

The available options are:

UP - This option uploads the binary from the Mark V to the HMI. It is used whenyou wish to preserve the contents in the unit as disk files on the HMI. This optionrequires one or more section names.

DOWN - This option will download a binary file from the HMI to the Mark V. It isused 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.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 andcomparing the expected checksum with the actual checksum. Some sections (such asthe 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.Currently the totalizer data (TOTD) section is the only section that is marked to notuse a checksum - due to it constantly changing values. This option requires a sectionname, 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 inthe last line in a batch file driven download.

In addition to the individual sections (or partitions) in the EEPROM, two specialpseudo section names are provided which act as a collection of the other sections.These include:

GEH-6126 Chapter 6 Configuration • 197

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 entireEEPROM and downloads all the sections. This erases all information (includingtotalizer 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 isused in a download. This pseudo section is most commonly used with the Up optionto upload all sections prior to a unit upgrade.

USER - This pseudo section means all of the sections except the FORMAT and TOTDsections. This is commonly used to download all of the user-configured sectionsafter rebuilding the panel configuration.

Consider the example below:

F:\UNIT1>EEPROM DIR T1 RDIRECTORY OF UNIT T1 PROCESSOR R: 03-DEC-1997 10:28:53 Partition offset size --------date-------- cksum -id- SEQ 5000 243A 03-MAY-1997 12:36:48 4E28 SEQ CONST 2000 1000 03-MAY-1997 12:36:26 0936 CNST IOCFG 4000 00CB 24-MAY-1995 13:10:56 2C8F IO UBBL 4800 0117 24-NOV-1993 13:54:34 6B5A UBL HIST 0000 0000 03-MAY-1997 12:36:26 0000 HIST EPA 0000 0000 03-MAY-1997 12:36:26 0000 EPA MAOUT 0DD0 003C 03-MAY-1997 12:36:26 0FCD 4-20 EVENT 0E60 007A 03-MAY-1997 12:36:26 2570 EVNT CHNG 0F60 0100 03-MAY-1997 12:36:28 38BD CHNG BOI 12E0 02B6 03-MAY-1997 12:36:28 847A BOI TOTT 0C00 00A9 03-MAY-1997 12:36:28 1EAF TOTT TOTD 0200 0910 11-MAR-1992 16:40:48 0000 TOTD CBLR 1160 0006 03-MAY-1997 12:36:28 CAFE CBLRF:\UNIT1>

Application InformationThe date and time in the EEPROM header is a copy of the date and time from the fileused to download the panel. This means that the date represents the information inthe panel, not the date that the information was downloaded to the panel. Doing thishelps to correlate the information in the unit to the HMI disk files that were used toconfigure the panel. If a file is uploaded from the unit, the date and time on the HMIwill be set to the date and time from the EEPROM header.

There is a default layout for the EEPROM built into the EEPROM program. Thedefault layout defines what EEPROM partitions exist, where each one starts in theEEPROM, and how large each partition is. Most sites use this default layout with noproblems. Some sites and some product lines redefine the layout to resize thepartitions or to allow for a larger EEPROM supplied on some jobs. This is doneusing the EEPROM.DAT file in the unit configuration directory. If no EEPROM.DATfile exists, the program assumes the default layout. If EEPROM.DAT exists, it usesthe partition layout defined in that file. If the partition layout is changed, theEEPROM will need to be completely reformatted and downloaded for the change totake 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.

198 • Chapter 6 Configuration GEH-6126

The header of the EEPROM contains some unit specific information including thisunit’s ARCNET address, whether the unit is a Simplex or a TMR, and the base framerate. This information, along with the EEPROM directory and partition layout, isstored in a special partition known as FORMAT. Downloading the FORMATpartition to the unit will re-format the EEPROM, loosing all the contents. (TheFORMAT partition is not included in the USER pseudo section.) Because of the unitspecific information in the FORMAT section, extra care needs to be taken if theFORMAT section is copied from one unit configuration to another.

UDF

OverviewUDF (User Defined File) is a Mark V LM configuration utility that downloads thebinary configuration information from the HMI into the non-volatile memory (a diskdrive) in the Mark V LM control panel. (UDF is not used for the Mark V - it uses theEEPROM program instead.)

Various configuration tools create the *.AP1 files that define the configuration of theMark V LM turbine control. These include the Sequence Compiler, the TableCompiler, and the I/O Configurator. These files are stored in the unit configurationdirectory 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. UDF is used to copythese files to the Mark V LM non-volatile memory. The Mark V LM uses a diskdrive 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 LMand the unit configuration directory on the HMI. It also provides a directorycommand to view the contents of the Mark V LM disk drive, and will do a simplesanity check to verify the unit’s files have not been corrupted.

GEH-6126 Chapter 6 Configuration • 199

OperationUDF is a command line utility program that is typically run from a DOS prompt.When the program is run it prompts the user for the desired unit. This must be aMark V LM unit. (Entering a question mark when prompted for the unit name willprovide a list of valid Mark V LM unit names.) The user is then prompted for whichcontroller to talk to, with the default being the <R> controller. UDF then drops into aloop prompting the user with its "UDF>" prompt. The Help command providing thelist of commands is shown below.

A special condition exists when a Mark V LM panel is first loaded. The sequencefor loading a panel (somewhat simplified) is as follows:

Use the serial download via RS-232 cable to load the operating system withARCNET 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 talkon the ARCNET, but not enough software to perform as a turbine control unit. Inthis condition, the panel is not able to function as a unit, so it will not understand ifits address is specified as a unit name. For UDF to contact the unit, the ARCNETaddress of the panel must be used instead of the unit name. To do this, when askedfor the unit name enter instead "0x" followed by the ARCNET address. This allowsthe UDF program to talk to a particular address, even before the unit software hasbeen downloaded to it. When the ARCNET address is used, one additional questionhas 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 wherethe unit must be contacted from a remote location through the HMI. The nodenameis the name of the HMI that is going to act as a passthrough node for the UDFmessages. When run from a remote location, the unit name can not be used tospecify the unit, the ARCNET address must be used instead. Review the examplesbelow:

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>

200 • Chapter 6 Configuration GEH-6126

The date and time on the unit’s disk drive is a copy of the date and time from the fileused to download the panel. This means that the date represents the information inthe panel, not the date that the information was downloaded to the panel. Doing thishelps to correlate the information in the unit to the HMI disk files that were used toconfigure the panel. If a file is uploaded from the unit, the date and time on the HMIwill be set to the date and time from the unit’s disk drive.

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>

GEH-6126 Chapter 7 Remote Access and Control • 201

Chapter 7 Remote Access andControl

Remote AccessAll remote access will be through a Remote Access Service (RAS) connection. Thecomputer phoning the site will have to have Dial Up Networking capability. Aconnection will have to be made to the HMI computer with RAS. To do this, youwill need a user account and password on the HMI. The protocols to communicateover the RAS connection will be TCP/IP and NetBEUI. Most of thecommunications will use TCP/IP. NetBEUI resolves names when mounting remotedisks.

Web InterfaceDemand Display – This display allows the display of the values of a selected list ofpoints. Any point in the data dictionary can be displayed by typing in the pointname. You can add new Point Lists or modify the points contained in a Point List byediting 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 doesnot allow the forcing or unforcing of points.

Control Constants – This display shows each of the control constants and its currentvalue.

HMI Startup log – This display shows the last startup log file for this HMI.

(Browse) – This allows you to pick the log file you would like to see. You can thendisplay the log file.

Point Browser – This display shows all the points in the data dictionary for theselected unit.

ARCWHO – This display shows all the nodes that are alive on the ARCNet.

202 • Chapter 7 Remote Access and Control GEH-6126

FTP InterfaceThe FTP Interface will allow the transfer of files to and from the HMI. The onlydirectories 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.

Remote Mount DisksYou can mount disks from the HMI to your computer. This allows you to copy filesto and from the HMI.

GE Industrial Systems Standard Message Formats

IntroductionThis document defines message formats available to DCS vendors for data collectionand process control. It does not define the message transport mechanism althoughthat is presumed to be a TCP over IP system.

GE INDUSTRIAL SYSTEMS (GEIS) Standard Messages are application levelmessages. These application level messages will be collectively referred to as GSMin this document.

GSM messages are processed by software in an intervening box or gateway to theprocess controllers. These gateways, in turn, can communicate directly withpotentially several process controllers. The general function of the intervening boxis to act as a protocol translator yielding a consistent external interface regardless ofinternal protocols and data representations used. No data will be emitted from thegateway 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 agateway.

NotationUnless otherwise noted all data is specified in Little Endian format. This is the byteorder for Intel processors. For multi-byte data, the least significant byte istransmitted first while the most significant byte is transmitted last.

For notational convenience, multi-byte data is shown below such that the mostsignificant byte is to the left; least significant byte is on the right; but thetransmission sequence of bytes will be right to left. For example, a 32-bit integervalue is shown as follows:

<------------------TRANSMISSION SEQUENCE Bit # 31 0 ±µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ¹µµµµµµµµµ£ ¢ M.S.B. L.S.B. ¢ °µµµµµµµµµ·µµµµµµµµµ·µµµµµµµµµ·µµµµµµµµµ¤

GEH-6126 Chapter 7 Remote Access and Control • 203

Many messages have Name fields within them. The format of a Name field will inall 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 thename 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 showngenerically 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 byrecord size, followed by record specific information. Note that n (record size) maybe 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, whichare implemented as parameter lists. Each item in a parameter list consists of at leasttwo 16-bit words. The first word identifies the parameter. The second wordidentifies the number of bytes to follow which qualify the parameter. These twowords are then followed by zero or more bytes (as defined by the second word).Software may use the parameter size to skip unknown parameters.

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 ¢ .../ /... µµµµµµµµµµ¤

A special item code with a value of 0x0000 is the End-of-list item code. Even if thetotal record size indicates space for more item list entries, no interpretation of databeyond End-of-list should be attempted.

Software that scans item lists must simply bypass unknown or previously undefineditem code entries.

Item Codes and Record Types have unique values. No item code will have the samevalue as a defined record type.

204 • Chapter 7 Remote Access and Control GEH-6126

Most data messages have time tagged data points within them. All time tags arerepresented using GE INDUSTRIAL SYSTEMS Standard Time. The GEINDUSTRIAL SYSTEMS standard time representation is a structure consisting of2 unsigned longwords (32 bits each). The first longword is the number of secondssince 1-JAN-1970 00:00:00.000000 GMT. The second longword is the number ofmicroseconds within the second, having a decimal range of 0-999,999. The latestdate and time that can be stored using this representation is 07-FEB-210606: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 orMBZ. These fields are intended for use in future versions of the GSM specification.To preserve backward/forward compatibility, software, which generates GSMmessages, must fill in RESERVED and MBZ fields with zeros; and software thatreceives GSM messages must ignore these fields.

GSM allows data acquisition/control of multiple process controllers. Part of thegeneric GSM messages is a small message header. This message header consists ofthree parts: a 16-bit message code; a 16-bit sequence number; and an ASCIICprocess controller name. The message code identifies the requested function (dataacquisition, command etc.). The sequence number is an arbitrary number generatedby the data/command requester to uniquely identify a given request; all responses toa given request message will have this sequence number echoed back allowing staledata to be thrown away. The ASCIIC controller name defines which controllerwithin 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.

Timetag ConsiderationsAs shown above the resolution of the GE INDUSTRIAL SYSTEMS Standard Timetag is 1 Microsecond. All time tagged data is stamped at the source of the data, usingthe resolution available in the local process controller. The resolution of time stampsin the local process controller is usually less than 1 microsecond (i.e. it’s morecoarse).

GEH-6126 Chapter 7 Remote Access and Control • 205

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 thatconsecutive data samples collected will be time tagged in multiples of 125milliseconds. Other controllers, such as the SOE (Sequence Of Events) scanner inMark V controller run at a much higher rate like every 122 microseconds.

Time tag accuracy or coherency across different process controllers is the subject oftime setting and time synching. GSM does not define the capability of time settingvia messages over a network nor does it allow the concept of time synching processcontrollers over a network. Where required, time setting/time synching of processcontrollers 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 bysystem requirements.

High-resolution time tagged data does not necessarily imply speedy reporting ofdata. Some process controllers for example, may buffer multiple pieces of timetagged data into envelopes which are delivered at a later time. Due to theasynchronous nature of delivering buffered time tagged data, it is both possible andlikely that different pieces of data will not be delivered in chronological order.

GSM Message Type SummaryGSM supports the following types of request messages:

• Administrative requests

• Requests for event-driven data.

• Requests for periodic data.

• Command requests.

Administrative requests are not associated with a single process controller. Theserequests are DCS to gateway messages, mainly to interrogate the capability of thegateway.

Event-driven data messages are spontaneously sent messages sent as a result of achange in state. There are several classes of event driven data. These include:

• Changes in process alarm state.

• Changes in digital input.

• Software detected changes in pre-defined Boolean variables.

• Deadband crossings detected in pre-defined analog variables.

• Changes in controller alarm (diagnostic) state.

206 • Chapter 7 Remote Access and Control GEH-6126

Periodic data consists of sets of data requested to be transmitted back to therequester either once, or periodically at rates up to once per second. This datatypically is used for updating status displays.

Command requests fall into two generic classes:

• Process alarm command requests.

• Process command requests either in the form of momentary contact pushbuttons or in the form of analog setpoints.

It should be noted that command requests may be rejected by the local controller ormay be blocked by the gateway as dictated by system requirements.

Administrative Message Formats

Supported Controller Request:This request from the DCS to the gateway is used by the DCS to determine whatprocess controllers the gateway can communicate with, along with currentcommunication status. Note that this is a DCS-to-gateway message, and as such theController Name field is inappropriate. The gateway will ignore this field, but theDCS should still fill it in as a zero length name.

The format of the Supported Controller Request message is shown below:

Message Offset NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0100 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Field Ignored °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµµµµµµµµµµµ¤

GEH-6126 Chapter 7 Remote Access and Control • 207

Supported Controller ResponseThe gateway will respond to the previously described request with a list of supportedcontrollers, controller type, and current communication status. The response is a listof parameter lists where each parameter list defines information about a singlecontroller.

The format of the response is shown below.

Message Offset 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 ¢ 15+Size2 *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Controller Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤ . . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8100 ¢ *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Controller Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤

This response contains a list of parameter lists (denoted by *2), and is identified by arecord type value of 0x8000. Each parameter list corresponds to a supportedcontroller. Possible parameters are shown below:

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1000 ¢ Param ID = Controller Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of controller name. °µµµµµµµµµµµµµµµµµµ¡ Controller Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

208 • Chapter 7 Remote Access and Control GEH-6126

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 currentlyactive between the gateway and the controller. A value of zero indicates that thegateway supports the controller, but cannot currently communicate with it.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1020 ¢ Param ID = Controller type ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Controller type.. °µµµµµµµµµµµµµµµµµµ¤

This parameter defines the controller type. Currently defined Controller Typesare:

• 0001 – Turbine Controller

• 0002 – CIMPLICITY

Other values will be defined in the future.

Heartbeat MessageThe DCS requests to be placed on various distribution lists as defined later in thisdocument. The Heartbeat message is merely a keep-alive message in a DCS-to-Gateway administrative message. This message should be transmitted by the DCSapproximately every 20 seconds. If the gateway does not receive a heartbeatmessage from the DCS for a period of 60 seconds, any data lists currently defined onbehalf of the DCS will be automatically canceled and the connection to the DCS willbe terminated.

The gateway does not respond to heartbeat messages.

The format of the Heartbeat message is shown below:

Message Offset NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0200 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 Field Ignored±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Field Ignored°µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµµµµµµµµµµµ¤

GEH-6126 Chapter 7 Remote Access and Control • 209

Event-Driven Data Messages

Alarm Record Establish RequestThis message requests the gateway to place/remove the DCS on/from the distributionlist for process alarm messages. Process alarm messages defined below are containermessages that are issued spontaneously any time a process alarm changes state.State changes include transitions in alarm value; alarm lock/unlock transitions; andremoval of an alarm from the process controller’s alarm queue (if supported in thecontroller). For CIMPLICITY alarms, a resource ID may be substituted for theController 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 °µµµµµµµµµµµµµµµµµµ¤

Alarm Function has 2 defined values. 0x0000 requests that the DCS be added to thealarm distribution list for the specified controller. 0xFFFF requests that the DCS beremoved 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 alarmtext will be omitted. Bits 1-15 are reserved and must be zero.

Alarm Record Establish ACK/NAK ResponseThe gateway responds to an alarm establish request with an establish ACK/NAKresponse.

The format of the establish ACK/NAK response is:

±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0301 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 (Echoed) ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0300 ¢ 5+n Establish Code ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Alarm Function ¢ 7+n (Echoed) ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Status ¢ 9+n ACK/NAK Code °µµµµµµµµµµµµµµµµµµ¤

210 • Chapter 7 Remote Access and Control GEH-6126

The Sequence Number, Controller Name and Alarm Function are echoed from thealarm establish request. The establish code = 0x0300 for an alarm ACK/NAKresponse.

Possible ACK/NAK codes are:

• 0 – Success.

• +1 – DCS on Gateway's distribution list. Communication with processcontroller 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.

Alarm Data MessagesAlarm data messages are sent spontaneously to any DCS, which has been placed onthe gateway's distribution list for alarm messages. Alarm data messages arecontainer messages containing 1 or more alarms, which have changed state. Thesemessages do not provide current status of all alarms.

This message contains a list of parameter lists where each parameter list definesinformation about a single alarm. Not all process controllers support all possibleparameters. Information not relevant to a given process controller will be missing.

GEH-6126 Chapter 7 Remote Access and Control • 211

Message Offset NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0302 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 From Estab. Request ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ 5 *1 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ 7 Record Type *2 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ 9 Size of Response ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8300 ¢ 11 First Alarm Info *3 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ 13 Size of Alarm Info °µµµµµµµµµµµµµµµµµµµ¡ First Alarm Information ¢ 15 Parameter List *4 ...// µµµµµµµµµµµµµµµµµµµµ¤

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ 15+Size2 *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Alarm Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Alarm Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤

These messages contain a list of parameter lists (denoted by *2), and is identified bya record type value of 0x8000. Each parameter list corresponds to a single alarm,which has changed state. Possible parameters are shown below:

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ Param ID = Point Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of point name. °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

This parameter defines the short name of the alarm. This parameter is notincluded if the gateway is incapable of translating the alarm drop into its short nameform.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ Param ID = Timetag ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ Parameter size. ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ Alarm Queue Time °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤

This parameter is the time tag associated with the alarm record.

212 • Chapter 7 Remote Access and Control GEH-6126

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 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 inalarm. 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 = 1if 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 thealarm record is being sent. The following list defines reason codes:

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.

GEH-6126 Chapter 7 Remote Access and Control • 213

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ Param ID = Long Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of long name. °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

This parameter defines the long name (text) associated with the alarm. Thisinformation is not sent if it is not requested in the alarm establish message. Text sizewill 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 hasa sequence number, which is incremented for every alarm record. The alarmsequence number is provided for remote alarm queue management. If the remotealarm queue sequence number (plus 1) does not equal this sequence number, then theremote alarm queue is out-of-sync with the process controller’s alarm queue. In thisevent, the DCS should request an alarm dump (See alarm commands defined later inthis document) to re-synchronize. Note that this value is a two byte-unsigned integerand 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 notbeen acknowledged. Bit 0 = 1 if the alarm has been acknowledged. All other bitsare 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 numberinto its short name form. Reception of this parameter indicates incompletetranslation tables in the gateway.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ Param ID = END-OF-LIST ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ Parameter size. °µµµµµµµµµµµµµµµµµµ¤

No more information about this alarm follows.

Digital Input Record Establish RequestThis message requests the gateway to place/remove the DCS on/from the distributionlist for digital input messages. Digital input messages defined below are containermessages that are issued spontaneously any time a digital input in the processcontroller changes state (if supported in the controller).

The gateway always responds to this request with an establish ACK/NAK message.

214 • Chapter 7 Remote Access and Control GEH-6126

The format of the digital input establish request is:

±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0400 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n °µµµµµµµµµµµµµµµµµµ¤

Establish Function has 2 defined values. 0x0000 requests that the DCS be added tothe digital input distribution list for the specified controller. 0xFFFF requests thatthe DCS be removed from the distribution list. All other values are reserved.

Options request other information be included in spontaneously sent digital inputmessages. Bit 0 = 1 requests that longname descriptive text be included in anygenerated digital input messages; otherwise longname text will be omitted. Bits 1-15are reserved and must be zero.

Digital Input Record Establish ACK/NAK ResponseThe gateway responds to a digital input establish request with an establishACK/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 thedigital input establish request. The establish code = 0x0400 for a digital inputACK/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.

GEH-6126 Chapter 7 Remote Access and Control • 215

Digital Input Data MessagesDigital input data messages are sent spontaneously to any DCS, which has beenplaced on the gateway’s distribution list for digital input messages. Digital input datamessages are container messages containing 1 or more inputs which have changedstate.

This message contains a list of parameter lists where each parameter list definesinformation about a single digital input. Not all process controllers support allpossible parameters. Information not relevant to a given process controller will bemissing.

Message Offset NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0402 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 From Estab. Request ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ 5+n *1 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ 7+n Record Type *2 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ 9+n Size of Response ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8400 ¢ 11+n First Digin Info *3 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ 13+n Size of Digin Info °µµµµµµµµµµµµµµµµµµµ¡ First Digital Input Information ¢ 15+n Parameter List *4 ...// µµµµµµµµµµµµµµµµµµµµ¤

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8400 ¢ 15+Size2 *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Digital Input Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8400 ¢ *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Digital Input Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤

These messages contain a list of parameter lists (denoted by *2), and is identified bya record type value of 0x8000. Each parameter list corresponds to a single digitalinput, which has changed state. Possible parameters are shown below:

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ Param ID = Point Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of point name. °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

This parameter defines the short name of the digital input. This parameter is notincluded if the gateway is incapable of translating the digital input number into itsshort name form.

216 • Chapter 7 Remote Access and Control GEH-6126

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ Param ID = Timetag ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ Parameter size. ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ Alarm Queue Time °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤

This parameter is the time digital input changed state.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ Param ID = Digin State ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Digital Input State °µµµµµµµµµ¤

Bit 0 defines the current state of the digital input. All other bits are reserved.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ Param ID = Long Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of long name. °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

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 establishmessage. Text size will be zero if the gateway cannot provide the associated text.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10D0 ¢ Param ID = Point ID Hint ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Point ID Hint Value °µµµµµµµµµµµµµµµµµµ¤

The gateway will send this parameter if it cannot translate the digital input numberinto its short name form. Reception of this parameter indicates incompletetranslation tables in the gateway.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ Param ID = END-OF-LIST ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ Parameter size. °µµµµµµµµµµµµµµµµµµ¤

No more information about this digital input follows.

GEH-6126 Chapter 7 Remote Access and Control • 217

Software Event Record Establish RequestThis message requests the gateway to place/remove the DCS on/from the distributionlist for software event messages. Event messages defined below are containermessages that are issued spontaneously any time a logic variable in the processcontroller changes state (if supported in the controller). Which logic variablesdefined 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 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Estab. Function ¢ 5+n ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n °µµµµµµµµµµµµµµµµµµ¤

Establish Function has two defined values. 0x0000 requests that the DCS be addedto the event message distribution list for the specified controller. 0xFFFF requeststhat 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 digitalinput messages; otherwise longname text will be omitted. Bits 1-15 are reserved andmust be zero.

218 • Chapter 7 Remote Access and Control GEH-6126

Software Event Record Establish ACK/NAK ResponseThe gateway responds to a event establish request with an establish ACK/NAKresponse.

The format of the establish ACK/NAK response is:

±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0301 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 (Echoed) ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0500 ¢ 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 theevent establish request. The establish code = 0x0500 for an event ACK/NAKresponse.

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.

GEH-6126 Chapter 7 Remote Access and Control • 219

Software Event Data MessagesSoftware event data messages are sent spontaneously to any DCS, which has beenplaced on the gateway’s distribution list for event messages. Event data messages arecontainer messages containing 1 or more logic points, which have changed state.

This message contains a list of parameter lists where each parameter list definesinformation about a single logic variable. Not all process controllers support allpossible parameters. Information not relevant to a given process controller will bemissing.

Message Offset NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0502 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 From Estab. Request ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ 5 *1 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ 7 Record Type *2 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ 9 Size of Response ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8500 ¢ 11 First Event Info *3 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ 13 Size of Event Info °µµµµµµµµµµµµµµµµµµµ¡ First Event Information ¢ 15 Parameter List *4 ...// µµµµµµµµµµµµµµµµµµµµ¤

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8500 ¢ 15+Size2 *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Event Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8500 ¢ *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Event Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤

These messages contain a list of parameter lists (denoted by *2), and is identified bya record type value of 0x8000. Each parameter list corresponds to a single logicvalue, which has changed state. Possible parameters are shown below:

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ Param ID = Point Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of point name. °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

This parameter defines the short name of the event. This parameter is notincluded if the gateway is incapable of translating the event number into its shortname form.

220 • Chapter 7 Remote Access and Control GEH-6126

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ Param ID = Timetag ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ Parameter size. ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ Alarm Queue Time °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤

This parameter is the time logic variable changed state.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1060 ¢ Param ID = Event State ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 1 ¢ Parameter size. °µµµµµµµµ³µµµµµµµµµ¡ ¢ ¢ Event State °µµµµµµµµµ¤

Bit 0 defines the current state of the logic variable. All other bits are reserved.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ Param ID = Long Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of long name. °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

This parameter defines the long name (text) associated with the event. Thisinformation is not sent if it was not requested in the software event establishmessage. Text size will be zero if the gateway cannot provide the associated text.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x10D0 ¢ Param ID = Point ID Hint ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 2 ¢ Parameter size. ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ ¢ Point ID Hint Value °µµµµµµµµµµµµµµµµµµ¤

The gateway will send this parameter if it cannot translate the event number into itsshort name form. Reception of this parameter indicates incomplete translation tablesin the gateway.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ Param ID = END-OF-LIST ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ Parameter size. °µµµµµµµµµµµµµµµµµµ¤

No more information about this event follows.

GEH-6126 Chapter 7 Remote Access and Control • 221

Periodic Data Messages

Periodic Data RequestThe DCS can define lists of data to be returned on a periodic basis. This is typicallyused to maintain real time databases for display purposes. Using this method, anydata point defined in the process controller (and also defined in the gateway’sdatabase) can be returned to the DCS. Multiple data lists may be defined by theDCS. Limitations are placed on list definitions based on the controller as shownbelow.

Controller Max Points Max Lists

Mark V 96 32

Mark V LM 50 64

CIMPLICITY 300 no maximum

The gateway will respond to a periodic data definition with a periodic dataACK/NAK message.

222 • Chapter 7 Remote Access and Control GEH-6126

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 ¢ ..//..µµµµµµµµµµµµµµµµµµµµµ¤

List Name combined with Controller Name defines a unique set of data points to bereturned. If the request contains a List Name/Controller Name that is identical to apreviously defined set, the new request will supersede the previous definition. ListName may be any value.

Establish Function has 2 defined values. 0x0000 requests that the data pointsspecified in the request be returned to the DCS according to Period Code. 0xFFFF-request cancellation of any previously defined list corresponding to ListName/Controller Name.

Period Code defines the number of seconds between data transmissions. It isignored on list cancellation requests. A period code with a value of zero requests thedata to be transmitted only once.

The Point Name parameter list is ignored on list cancellations. The Point Nameparameter is an ASCII string and must match the point name defined in the controllerconfiguration.

GEH-6126 Chapter 7 Remote Access and Control • 223

Periodic Data ACK/NAK ResponseThe gateway responds to a periodic data request with a periodic data ACK/NAKresponse.

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 areechoed from the event establish request. The establish code = 0x0600 for a periodicdata 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 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.

Periodic Data MessagePeriodic data messages are sent periodically to the DCS following the transmissionof 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 inthe message, followed by a parameter list containing a time tag and point values. ForCIMPLICITY data the time tag for the list represents the time tag of the first point inthe list. The point value list is transmitted in the same order as defined in theperiodic data request. If a requested point is undefined, the returned list entry willshow a size of zero. The format of the periodic data message is:

224 • Chapter 7 Remote Access and Control GEH-6126

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 ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

*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, periodictransmission of these messages will cease. Message transmission will resumeautomatically when the gateway regains communication with the process controller.

Command Messages

Alarm Command RequestThis message is used for remote control of the process controller's alarm queue. Thealarm command request can be used to acknowledge, reset, lock or unlock alarms orrequest an alarm dump. Note that not all process controllers will accept all alarmcommands. For CIMPLICITY alarms the drop number is generated by the gatewayand will not be the same between connections.

The gateway always responds to this request with an alarm command ACK/NAKmessage.

GEH-6126 Chapter 7 Remote Access and Control • 225

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 commandvalues, and the meaning of options is shown below:

Command Value Command Function Options Meaning

2 Lock Single Alarm Alarm Drop Number

3 Unlock Single Alarm Alarm Drop Number

4 Acknowledge Alarms Number of alarms *1

6 Reset All Alarms <Ignored>

7 Acknowledge 1 Alarm Alarm Drop Number

8 Reset 1 Alarm Alarm Drop Number

10 Alarm Silence <Ignored>

255 Request Alarm Dump Include Alarm Text Flag *2

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.

Alarm Command ACK/NAK ResponseThe gateway responds to an alarm command request with an ACK/NAK response.

The format of the alarm command ACK/NAK response is:

±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0701 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 (Echoed) ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Alarm Command ¢ 5+n (Echoed) ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Options ¢ 7+n (Echoed) ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ Command Status ¢ 9+n ACK/NAK Code °µµµµµµµµµµµµµµµµµµ¤

226 • Chapter 7 Remote Access and Control GEH-6126

The Sequence Number, Controller Name, Alarm Command and Options are echoedfrom 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.

Alarm Dump MessagesAlarm dump messages are nearly identical to alarm data messages described above.Alarm dump messages are sent following the alarm command ACK/NAK message ifan alarm dump was requested, and the function is supported by the processcontroller. Alarm dump messages provide current status of all alarms. Due to thepotential size of the entire alarm queue information, this message may be broken upinto several GSM messages. The DCS can use the alarm sequence number tosynchronize it's own alarm queue. The alarm sequence number in an alarm dump isthe latest alarm sequence number used in the process controller. This same numberwill appear for multi-GSM messages.

This message contains a list of parameter lists where each parameter list definesinformation about a single alarm. Not all process controllers support all possibleparameters. Information not relevant to a given process controller will be missing.

GEH-6126 Chapter 7 Remote Access and Control • 227

Message NOTES ±µµµµµµµµµ¹µµµµµµµµµ£ Offset ¢ 0x0702 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 From Estab. Request ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Request Status ¢ 5 *1 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8000 ¢ 7 Record Type *2 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 1> ¢ 9 Size of Response ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x8300 ¢ 11 First Alarm Info *3 ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 2> ¢ 13 Size of Alarm Info °µµµµµµµµµµµµµµµµµµµ¡ First Alarm Information ¢ 15 Parameter List *4 ...// µµµµµµµµµµµµµµµµµµµµ¤ ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ 15+Size2 *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size 3> ¢ °µµµµµµµµµµµµµµµµµµ¡ Second Alarm Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤ . . ±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x8300 ¢ *3 ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ °µµµµµµµµµµµµµµµµµµ¡ Last Alarm Information ¢ Parameter List ...// µµµµµµµµµµµµµµµµµµµµ¤

These messages contain a list of parameter lists (denoted by *2), and is identified bya 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 parameterlist containing only the End-Of-List parameter.

Possible parameters are shown below:

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1030 ¢ Param ID = Point Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of point name. °µµµµµµµµµµµµµµµµµµ¡ Point Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

This parameter defines the short name of the alarm. This parameter is notincluded if the gateway is incapable of translating the alarm drop into its short nameform.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1040 ¢ Param ID = Timetag ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 ¢ Parameter size. ±µµµµµµµµµ..//..°µµµµµµµµ¹µµµµµµµµµ¡ ¢ 8 Byte Timetag ¢ Alarm Queue Time °µµµµµµµµµ..//..µµµµµµµµµµµµµµµµµµµ¤

This parameter is the time tag associated with the alarm record.

228 • Chapter 7 Remote Access and Control GEH-6126

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 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 inalarm. 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 = 1if 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 thealarm record is being sent. The following lists defined reason codes:

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.

GEH-6126 Chapter 7 Remote Access and Control • 229

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x1090 ¢ Param ID = Long Name ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ <Size n> ¢ Size of long name. °µµµµµµµµµµµµµµµµµµ¡ Long Name ¢ ...// µµµµµµµµµµµµµµµµµµµµ¤

This parameter defines the long name (text) associated with the alarm. Thisinformation is not sent if it is not requested in the alarm establish message. Text sizewill 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 hasa sequence number, which is incremented for every alarm record. The alarmsequence number is provided for remote alarm queue management. If the remotealarm queue sequence number (plus 1) does not equal this sequence number, then theremote alarm queue is out-of-sync with the process controller’s alarm queue. In thisevent, the DCS should request an alarm dump (See alarm commands defined later inthis document) to re-synchronize. Note that this value is a two byte-unsigned integerand 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 notbeen acknowledged. Bit 0 = 1 if the alarm has been acknowledged. All other bitsare 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 numberinto its short name form. Reception of this parameter indicates incompletetranslation tables in the gateway.

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ Param ID = END-OF-LIST ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ Parameter size. °µµµµµµµµµµµµµµµµµµ¤

No more information about this alarm follows.

230 • Chapter 7 Remote Access and Control GEH-6126

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 processcontroller. The DCS should monitor feedback signals to determine if the commandrequest has been acted upon by the process controller.

To specify the number of scans for a push button use the Setpoint command. Mark Vdefaults to 4 and Mark V LM defaults to 25.

The gateway will respond to a process control command request by a control requestACK/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 /../µµµµµµµµµµµµµµµµµµµµµµ¤

The format of a push button command parameter is:

±µµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0000 ¢ 6+n+m PARAM = End List ´µµµµµµµµ¹µµµµµµµµµ¡ ¢ 0x0000 ¢ 8+n+m Value not required °µµµµµµµµµµµµµµµµµµ¤

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 /../µµµµµµµµµµµµµµµµµµµµµµ¤

GEH-6126 Chapter 7 Remote Access and Control • 231

Process Control Command ACK/NAK ResponseThe gateway responds to a process control command request with a commandrequest ACK/NAK response.

The format of the process control command request ACK/NAK response is:

±µµµµµµµµµ¹µµµµµµµµµ£ ¢ 0x0801 ¢ 0 Message Code ´µµµµµµµµµ¹µµµµµµµµµ¡ ¢ Sequence Number ¢ 2 (Echoed) ±µµµµµµµµµ¹µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Controller Name (ASCIIC) <n> ¢ 4 Controller Name ´µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Process Command Name (ASCIIC) <m> ¢ 5+n (Echoed) °µµµµµµµµµ·µµµµµµµµ/../µµµµµµµµ¹µµµµµµµµµ¡ ¢ Command Status ¢ 6+n+m °µµµµµµµµµµµµµµµµµµ¤

The Sequence Number, Controller Name and Process Command Name are echoedfrom the process control command request.

Possible ACK/NAK codes are:

• 0 – Success. Requested command sent to process controller.

• +1 – Request received by gateway, but communication with processcontroller is not currently possible.

• -1 – Unknown controller Name.

• -2 – Function not supported by process controller.

• -3 – Invalid process command name.

• -4 – Invalid parameter (i.e. Value for Push Button or no value for asetpoint target.)

• -5 – Internal Gateway error.

• -6- Permission violation due to control hierarchy

Note: No more than 10 process control command requests per secondshould be sent to any one controller.

232 • Chapter 7 Remote Access and Control GEH-6126

MESSAGE CODE SUMMARY

Message

Code Message Type Sent By

0x0100 Supported Controller Request DCS

0x0101 Supported Controller Response Gateway

0x0200 Heartbeat Message DCS

0x0300 Alarm Establish Request DCS

0x0301 List Establish ACK/NAK Gateway

0x0302 Alarm Data Message Gateway

0x0400 Digital Input Est. Request DCS

0x0402 Digital Input Data Message Gateway

0x0500 Software Event Est. Request DCS

0x0502 Software Event Data Message Gateway

0x600 Periodic Data Definition DCS

0x601 Periodic Data ACK/NAK Gateway

0x602 Periodic Data Message Gateway

0x700 Alarm Command Request DCS

0x701 Alarm Command ACK/NAK Gateway

0x702 Alarm Dump Data Message Gateway

0x800 Process Control Command Request DCS

0x801 Process Control ACK/NAK Response Gateway

GEH-6126 Chapter 7 Remote Access and Control • 233

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.

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.

Application Notes

NetworkingThe GSM server will use TCP port 768 on all configured network interfaces on thegateway. 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]

and give it the desired value. The key may need to be created if it does not alreadyexist. Each GSM message must be preceded by a two-byte integer indicating the sizeof the message. The recipient can use this size as an indication of how many bytes toread from the network. The maximum GSM message size that the gateway will sendor receive is 4096 bytes.

234 • Chapter 7 Remote Access and Control GEH-6126

TCP communicationsConceptually, a TCP socket represents the endpoint of a virtual circuit. Each clientsocket has a corresponding socket on the server and each client-server socket pair arethe endpoints of a distinct virtual circuit. Thus each client will have a separatecommunication path to the HMI. Responses to requests from Client-A will be sentonly to Client-A.

That the server is using only one port can be confusing. The fundamental abstractionof the TCP protocol is the virtual circuit and each virtual circuit is uniquelyidentified 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 thesame endpoint on the server can be used by multiple virtual circuits because eachvirtual circuit is identified by a PAIR of endpoints.

Telnet InterfaceThe GSM server provides a simple telnet interface that can be used to examine datain the server and trace messages passed to and from a client. To use the telnetinterface, run a telnet client and connect to the gateway on the GSM port (768 bydefault). When the connection is made, the server needs to be informed that theconnection is from a telnet client and not a GSM client. To do this press the ‘z’ keytwice and the server will respond with a command prompt. If the first two characterstyped are not ‘zz’, the server will assume that a GSM client has connected and youwill have to disconnect and try again.

GEH-6126 Chapter 7 Remote Access and Control • 235

Command Summary:show client – displays a list of all connected clients, including which controllers theyhave 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 givenperiodic data list, including point name, point type, last reported value as well as thetime the list was last sent to the client.

trace <client number> – toggle tracing of GSM messages sent to and received fromthe given client.

trace next – enable tracing of GSM messages sent to and received from the nextclient to connect to the server.

trace all – enable tracing of GSM messages sent to and received from all clients thatconnect 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 acommand summary. There is no command line editing capability, except as may beprovided by the telnet client.

Point ID Hint ParameterThe 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 datapoint in a Mark V or Mark V LM controller and when converted to ASCII in baseten, can be used as a point name. This means that any integer offset (converted toASCII) from 0 to 65535 can be used as a point name for Mark V and Mark V LMcontrollers. If there is a point configured for that offset then the GSM server willreturn the appropriate number of bytes, however if no point is configured for thatoffset then two bytes are returned to the client(i.e. the point is assumed to be a 16 bitinteger).

EGDThe GSM server provides access to any EGD data that is being collected on theHMI. A special controller name of EGD should be used in requests. Only periodicdata requests are valid for the EGD controller. Point names for EGD data are colon-separated fields that specify Exchange ID, Offset and Length. For example the 4bytes at offset 45 in exchange 5 would be named 5:45:4.

236 • Chapter 7 Remote Access and Control GEH-6126

TCI Modbus

IntroductionThe Modbus™ interface for the Turbine Control Interface (TCI) can act as eithera slave to the Distributed Control System (DCS) master or as a master to the DCSslave. 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 serialcommunications and Ethernet. Modbus master mode supports RS-232 serialcommunication only.

In Modbus slave mode the DCS can thereby request information from each MarkV(LM) controller or Cimplicity project by sending a Modbus data request messagevia the Modbus link to a specific slave address. The DCS master can also issueModbus command messages to initiate operator commands to each Mark V(LM) orCimplicity. These command messages support both push button commands (such asSTART, STOP) and analog setpoint commands (such as preselected load setpoint).A Modbus data file specifies the correspondence between Modbus coil and registernumbers and the Unit’s data.

In Modbus master mode the TCI can gather data from attached Modbus slaves. Thedata gathered is requested and stored in the TCI database based on points and updaterates specified in a Modbus data file.

Modbus SlaveThe rate at which the data can be collected from a serial Modbus slave is limited bythe transmission rate on the RS232 link, and by the turn-around times of thecomputers on each end of the link. The rate at which the data can be collected froman Ethernet Modbus slave is limited by the Ethernet traffic, and by the turn-aroundtimes of the computers on each end of the connection. The DCS may issue no morethan ten operator command messages per second. A maximum of 8 serial links maybe configured for a single TCI. The number of Ethernet connections an EthernetModbus slave will accept is configurable. Ethernet and serial links may both be usedat the same time. All data to and from a controller will be serialized and operated onone at a time.

The TCI Modbus slave, configured with the appropriate address, will reply with therequested data. A single TCI can respond to multiple slave addresses. Up to amaximum of 16 slave addresses may be configured for a single TCI. Normally eachseparate slave address would be assigned to gather data from a separate unit control.

Modbus MasterThe rate at which the data can be collected is limited by the transmission rate on theRS232 link, by the turn-around times of the computers on each end of the link, andby the periodic rate specified in the configuration data file.

The TCI Modbus master, configured with the appropriate address, will request datafrom a DCS slave at a specified rate. A single TCI can communicate with multipleslave addresses over various communication ports. Up to a maximum of 8communication ports may be used to communicate with up to 48 separate slaveaddresses.

GEH-6126 Chapter 7 Remote Access and Control • 237

MODBUS_L

OverviewIf the HMI is configured to provide a Modbus link, MODBUS_L is used to providea list of the signals that are available over the Modbus link, along with theinformation on how to interpret (scale) the values.

Modbus is an industry standard communication link used by the HMI to provide thecurrent value of plant variables from the HMI to any system that requests it via theModbus link. The HMI acts as a Modbus slave, which means it waits for requestsfrom another computer (a Modbus master) and answers them by returning the currentvalue of the variables requested.

The Modbus protocol is implemented as a set of registers. The HMI supports up to2000 registers of each type from each turbine control. The mapping of the Modbusregister number to the turbine signal name is done via the MODBUS.DAT file in theunit configuration directory. (See the Modbus configuration chapter for moreinformation on configuring the MODBUS interface.)

Once the Modbus configuration has been done, MODBUS_L is used to generate aformatted list of the Modbus register numbers, turbine signal names, and scalinginformation for each signal defined. This information is stored in the MODBUS.LSTfile. The MODBUS.LST file is then used to configure the Master side of the Modbuslink.

OperationMODBUS_L is a command line utility program run from the unit configurationdirectory. It does not require any command line parameters, but a few are availableto change the default format or scale codes generated. If run with the /? parameter, itwill 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>

238 • Chapter 7 Remote Access and Control GEH-6126

SpecificationsThe Modbus interface uses Gould Modicon’s Modbus Protocol. The following textprovides application information only. It does not specify Modbus Protocol.

Detailed information on the Modbus protocol is available from Gould Inc.’sReference Guide PI-MBUS-300 Rev B, January 1985. This is not the Modbus Plusspecification. It is recommended that both this document and the Gould referenceguide be used together.

The TCI system allows easy addition, deletion, or modification of the data lists bythe DCS vendor or customer after equipment installation. The data point capabilityof the Mark V turbine control system generally far exceeds the actual needs of theDCS.

A TCI can be located local, remote, or anywhere within the distance limitations ofthe 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 ofthe RS232 serial communication link or anywhere on the Ethernet link.

External Communication Links- Modbus Slave modeAn external communication link allows an operator at a remote location to initiateany 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 theMark V control system, and analog setpoints are used to set a variable, such as theturbine load, to a predefined level.

It is occasionally more efficient to set targets with an analog number, such asmegawatts, rather than manually entering raise/lower commands. The operator cansend a target setpoint that the Mark V enters into its data base and ramps to the targetat a predetermined ramp rate.

Any operator command that can be initiated from the TCI can be initiated from theremote control system through a communication link. This does not preclude the useof hard-wired remote control interface. However, a traditional hard-wired interfacecan be I/O intensive and needs to be evaluated on a case-by-case basis. Maintenancecommands (editing application software, changing tuning constants, etc.) aregenerally restricted to being issued from a TCI.

GEH-6126 Chapter 7 Remote Access and Control • 239

All application data in the Mark V can be monitored by the remote control systemvia the remote serial communication link. The Mark V data base contains severalthousand points, but usually less than 500 points are of interest to the remote controlsystem. These consist of logical data for alarm and event messages and analog ornumeric data for such variables as speed, load, vibration, temperature, and so forth.

One TCI can interface with up to 16 Mark Vs. Therefore, the externalcommunication link to the remote control system has the capability to communicatethrough the TCI to up to 16 Mark Vs.

External Communication Links- Modbus Master ModeExternal communication links allow the TCI control to communicate with a DCS orother Modbus slaves over up to eight serial communication ports. Communication ispossible over these links with up to 48 different Modbus slaves. For each Modbusslave, the data communicated will be specified by the contents of a data file found inthe unit directory. This file will specify what data is read from the slave and storedin the data dictionary and also what data is sent (written) to the slave.

RS232 and ModbusGE INDUSTRIAL SYSTEMS offers Modbus protocol with an RS232 link as alevel #1 communication link because it is compatible with most control systems. TheDCS is the master, and it issues a command to the Mark V that is the slave. Logicaland analog setpoint commands can be issued from the DCS to preassigned points inTCI to initiate control action. Requests for data can be sent to preassigned points inthe 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 limitationsmust be recognized. The limitations are a 19,200-baud (bit/sec) transmission rate andthe lack of individual time tags for alarms and events.

The RS232 link transmission rate makes it satisfactory for one or two units on asingle communication link depending on the amount of data that is requested fortransmission. A major factor in determining the suitability of the Modbus and RS232is 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 communicationlink to the DCS is used to retrieve data from the Mark V. This data is used to supportthe displays which currently appear on the monitors in the control room. Thisretrieval requires minimal data transmission from the Mark V.

The communication link load is a function of the amount of data that the DCS isrequesting and how often it is to be transmitted. Data in the Mark V requires oneword per analog point and one word for each 16 logic points (such as the state ofalarms and events). An evaluation of the link load for a specific application requiresreviewing the amount and frequency of the data transmission(s) and the specifiedbaud 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 fromthe Mark V to the plant alarm horn system that informs the DCS that a new alarmhas occurred. The DCS can then request a transmission of the alarm states data. Thiseliminates the need to continuously sample the alarm queue at a fast rate. Some sitesprovide a remote printer to get high-resolution local alarm (62ms), event (62ms), andsequence of event logs in the control room without investing in more sophisticatedequipment.

240 • Chapter 7 Remote Access and Control GEH-6126

Physical Link Layer/Format, RS232CommunicationsThese sections detail the physical link layer/format of the Modbus serial link.

Link LayerEach TCI processor can provide up to 8 point-to-point Modbus RS232 serial linksand a defined number of Ethernet connections to a customer’s DCS. Since themaster may communicate with multiple slaves, the TCI will send data upon requestonly. No periodic transmission of data from the TCI is possible, except as a reply toa periodically transmitted request sent from the DCS.

Physical LayerThe TCI processor is used as the communications port for Modbus, typically usingthe TCI’s COM2 serial communications port. If the COM2 port is not available, aserial expander card is required to supply eight more serial ports. The port used isconfigured 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, programmableparity. It is compatible with full duplex data sets (i.e. modems). Modem generatedsignals such as CTS (Clear to Send), CD (Carrier Detect) and RI (Ring Indicator) arenot required to enable the transmitter. The RTS (Ready to Send) and the DTR (DataTerminal Ready) on the TCI are always equal to 1 when the TCI is powered up. Thisprohibits any multi-drop DCS configurations, as these signals cannot enable ordisable 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 reasonablyexpect to handle in a single burst. (See the section below on TCI ModbusConfiguration for timeout configuration.)

GE INDUSTRIAL SYSTEMS does not recommend remote control of turbineproducts over a telephone modem due to the inherent unreliability in this type ofcommunication. If it is necessary to collect data or operate over telephone modems,the maximum number of bits that can be communicated is ten. Therefore thestandard eight bits of Modbus data and the two bits for start/stop is all that can beaccommodated. This means that PARITY is not supported over telephone modems.

RS232 systems require two metallic shielded twisted pair wires to connect the short-haul modems. RS232 transmission distances are defined below:

TRANSMISSION DISTANCE

Baud 26 Gauge 24 Gauge 22 Gauge 19 GaugeRate Miles km Miles km Miles km Miles km 300 10.0 16.1 12.0 19.3 15.0 24.1 25.0 40.2 1200 6.0 9.7 7.5 12.1 9.0 14.5 15.0 24.1 2400 4.5 7.2 5.5 8.9 7.5 12.1 11.0 17.7 4800 3.5 5.6 4.5 7.2 5.5 8.9 7.0 11.3 9600 2.2 3.5 3.2 5.1 4.0 6.4 5.0 8.019200 1.0 1.6 1.2 1.9 1.5 2.4 2.0 3.2

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 mustsupply the cabling and terminations. The standard modems supplied by GEINDUSTRIAL SYSTEMS require power on pin four. The modem connected to theTCI obtains its power from the TCI serial port. The other modem must receive power

GEH-6126 Chapter 7 Remote Access and Control • 241

on pin four from the DCS. If the DCS cannot supply power, the optional modem setis required and must be specified when ordering from GE INDUSTRIALSYSTEMS. This set is powered by an external source.

242 • Chapter 7 Remote Access and Control GEH-6126

RS232 connection to DB9 serial ports with no modems

RS232 connection to DB9 Serial port with modems

V+, the DCS power, is 3-5 mA @ 10 Vdc. It is a nominal 12 Vdc, minimum 6 Vdc,maximum 25 Vdc.

Optional RS232 connection with LDDS

The DCS and the cabling are supplied by the customer.

RXD (2) (2) S1-2 R1-4 (2) RXDTXD (3) (3) S2-1 R2-3 (3) TXDDTR (4) (4) S1-4 S1-2 (4) V+SCOM (5) (5) R2-3 S2-1 (5) SCOM

<I>DB9P (DTE)

DCSData Set(Modem)

Data Set(Modem)

ShieldedTwistedPair wire

Cable

RXD (2) (3) S1 R1 (3) RXD (3)TXD (3) (2) S2 R2 (3) TXD (2)RTS (7) NC R1 S1 (4) RTS (4)CTS (8) NC R2 S2 (5) CTS (5)SCOM (5) (7) (7) SCOM (7)CD (1) NC (8) CD (8)DTR (4) NCDSR (6) NCRI (9) NC

Typical <I>DB9P (DTE)

DB25P (DTE) DCS

Data SetLDDS

Data SetLDDS

Power 120Vac Power 120Vac

RXD (2) Cable TXD (2)TXD (3) RXD (3)RTS (7) NC RTS (4)CTS (8) NC CTS (5)SCOM (5) Common (not shielded) SCOM (7)CD (1) NCDTR (4) NCDSR (6) NCRI (9) NC

Typical <I>DB9P (DTE)

DB25P (DTE) DCS

GEH-6126 Chapter 7 Remote Access and Control • 243

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:

• pin 3 to pin 2 for RXD

• pin 2 to pin 3 for TXD

• pin 4 to pin 7 for RTS

• pin 5 to pin 8 for CTS

• pin 7 to pin 5 for SCOM

• pin 8 to pin 1 for CD

TCI Modbus ConfigurationThis section defines the required additions and/or modifications to configuration fileson a TCI to accomplish the following:

• enable and configure the Modbus task on the TCI

• enable and configure a serial port for Modbus communication

• set up the Modbus mapping tables

• generate the related document for the DCS vendor

F:\IO_PORTS.DAT: Modbus Link DefinitionThe Modbus Master program (MModbus.exe) and the Modbus Slave program(Modbus.exe) share a common configuration file entitled F:\IO_PORTS.DAT tospecify 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 anystandard text editor. Lines are not case sensitive.

The configuration file is divided into sections and each section begins with a titleenclosed in brackets [ ].

The Modbus Slave program uses three sections:

[MODBUS_SLAVE_PORT]

[MODBUS_SLAVE_TIMEOUT]

[MODBUS_ASSIGNMENT]

The Modbus Master program uses one section:

[MODBUS_MASTER_PORT]

The [MODBUS_SLAVE_PORT] and [MODBUS_MASTER_PORT] sections mayappear multiple times to define multiple ports.

In the [MODBUS_SLAVE_PORT] section, the TCI uses information in the TCI portdefinition/configuration file, F:\IO_PORTS.DAT, to assign functions to its availableI/O ports. These ports include the serial port (example: COM2), plus, the serial ports

244 • Chapter 7 Remote Access and Control GEH-6126

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:

• [MODBUS_SLAVE_PORT] – defines a Modbus slave port and itscharacteristics. 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 torespond to Ethernet messages.

• [MODBUS_ASSIGNMENT] – defines slave addressed and modes. Theseslaves can be either Mark V(LM) units or Cimplicity projects.

• [MODBUS_SLAVE_TIMEOUT] – define slave timeout value and NAK code.

• [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.

These sections are defined in more detail in the sample configuration file inG:\DATA\IO_PORTS.DAT.

Modbus Master SetupThe Modbus Master program first reads the section file calledMODBUS_SETUP_FILE file (filename F:\IO_PORTS.DAT) for informationspecifying Modbus port and hardware characteristics. This section,[MODBUS_MASTER_PORT], provides details such as:

• Port, baud rate, parity, etc.

• Modbus address and software characteristics. Provides details such as slaveaddress and unit number. Up to 48 master entries may be specified.

• Modbus timeout and loop characteristics.

This program ignores Modbus slave assignment.

The program then reads A MODBUS_DATA_FILE in the unit directory forinformation specifying a correspondence between Modbus data structures (holdingregisters, holding coils, input registers, input coils, etc.) and the corresponding MarkV (LM) data points and scaling information. The MODBUS_DATA_FILE resides inthe unit directory (F:\UNITn) and has a filename in the form MMBUSnnn.DAT wherennn is the slave address being referenced. Multiple MMBUSnnn.DAT files may existin the same directory. For example, if the F:\IO_PORTS.DAT file specified that wecommunicate 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 unitdirectory to determine the register and coil correspondence. Leading zeros for nnnare not used.

GEH-6126 Chapter 7 Remote Access and Control • 245

Next, the program opens the port specified in (1) above and monitors the port formessages from a Modbus master to one of its 48 slave addresses.

Upon receiving a message reply, the program stores the data in the unit datadictionary as appropriate.

Modbus Slave configuration: Holding Coils, Input Coils,Holding Registers, Input RegistersEach 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 theregisters 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 toassociate the registers and coils with the CIMPLICITY points.

There are two categories of point mapping tables. They are, holding and input. TheModbus protocol supports reading and writing of holding table points, and readingbut not writing of input table points.

The TCI does not make any restrictions on what Mark V CSDB pointnames can bein input and holding tables. The TCI knows on a point by point basis which pointsare Mark V commands and which points are not. A Mark V command is one of thefollowing:

LOGICS: pushbuttons logic state variables.

ANALOGS: analog setpoints enumerated state variables

As such, the holding tables may be used exclusively, and the input tables may beomitted completely. Sending a Modbus write command to a point on a holding tablethat 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 isone 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 CSDBpointname. If the pointname is a Mark V command, a write command from the DCSto any of the mapped holding coils or registers will cause the TCI to execute theMark V command.

HC – holding coils – one bit logic signals that are both readable and writable. LogicMark V commands must be in this table for the TCI to issue the command to theMark V; however, not all points in this table must be logic Mark V commands. LogicMark V commands are not writable from the holding register table.

IC – input coils – one-bit logic signals that are readable but not writable. Any MarkV logic control database signal can be in this table, but logic Mark V commands willnot 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 tothe Mark V, but not all points in this table must be analog Mark V commands. Theycan be any analog control database signal, or a set of (up to) 16 bit packed logiccontrol database signals. Mark V logic commands can be packed into a holdingregister, however, they will not be writable in that format. For the TCI to issue asignal to a logic Mark V command, it must be in the holding coil table. Simply put:packed holding registers are not writable.

246 • Chapter 7 Remote Access and Control GEH-6126

IR – input registers – 16 bit analog values that are readable but not writable. Anyanalog control database signal, or a set of (up to) sixteen (16) bit packed logiccontrol database signals, may be in this table. Analog or logic Mark V commandswill not be writable from this table.

Modbus Slave: @SPARE: Unused Coils and RegistersIf a request for any read or write command from the DCS using a coil or register notmapped to a Mark V CSDB pointname, the TCI will respond with a NAK code of02, 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 fromthe 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 orregister is not used, but is legally defined. The TCI will respond to any DCS requestwith a data value of zero (0) for all coils and registers defined as @SPARE. It is notnecessary to map all the points in the mapping table. The @SPARE is used only to fillin 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 isdefined 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 VCSDB pointnames will always send a value of 0 to the DCS. @SPARE can only beused on an unpacked register when the entire register is unused.

Modbus Slave: F:\UNITn\MODBUS.DAT: MODBUS MappingFile FormatThe hidden text needs to be added when NATIVE mode is added to the Modbus Slavein 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 Slaveis in any mode except NATIVE, F:\UNITN|MODBUS.DAT is used for the pointconfiguration. The following section contains a simple template as an example forfilling out the Modbus mapping file. More details are in the sample file ing:\data\modbus.dat and g:\data\modbus_n.dat.

GEH-6126 Chapter 7 Remote Access and Control • 247

If the Slave is defined to be a CIMPLICITY project, the configuration file isCIMMOD.DAT. They are located in the data directory of the Cimplicity project. Forthe Cimplicity data to work, the TCI Modbus option must be installed. When thisoption is installed, templates of these files will be installed. There is information inthe header of these files on how to fill them out. They are almost the same as theunit 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 When adding or modifying entries in this file, the following rules and guidelinesapply:

• It is not necessary to define all the table points in this file, only the ones that aredesired.

• 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 packedregister. A 0 is returned for bits not mapped.

• When a semi-colon is found in a line, the rest of the line is considered acomment.

• Do not add scaling information or definitions in this file, only the required threefields.

• Never add page breaks (form feeds) in this file.

• The Table entries may be in any order.

• Do not map any one register to both packed Mark V CSDB logic pointnamesand to an analog Mark V CSDB pointname.

• Do not have any one coil or register mapped more that once.

• Group similar Mark V CSDB points together, such as temperatures, speedsignals, or Mark V command feedback signals.

248 • Chapter 7 Remote Access and Control GEH-6126

From the example below, it can be seen that not all table points are defined or inorder, comments are added using a semi-colon ( ; ), there are no duplicate table pointdefinitions, etc. However, the rules outlined above have been followed and the filecan 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.

Modbus Master ConfigurationThis section describes the Modbus Master sections in the TCI portdefinition/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 theline a comment and will be ignored.

There is only one section used by the Modbus Master entitled:

[MODBUS_MASTER_PORT]

but this section may appear up to 8 times. Each appearance should correspond to aseparate communications port for the Modbus Master.

For example, the first [MODBUS_MASTER_PORT] section may be for com2 whilethe next section might be for com3.

These sections should appear as above, including brackets. They may appear in anyorder. 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:

[MODBUS_MASTER_PORT]port com2baud 9600parity 0 ;0-4 (none, odd, even, mark, space)databits 8 ;5-8stopbits 0 ;0-2 (1, 1.5, 2 stop bits)xonxoff 0 ;0-1port_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 RS16MASTER 2 UNIT T3 MODE RS16

[MODBUS_MASTER_PORT]port com3baud 9600MASTER 7 UNIT 63 MODE RU16

GEH-6126 Chapter 7 Remote Access and Control • 249

Comments:

The above example defines two ports for use with Modbus Master. Both com2 andcom3 will be used. Modbus slave ids 1 and 2 will be reached using com2 andModbus 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.

250 • Chapter 7 Remote Access and Control GEH-6126

The only required entries are port and MASTER-UNIT-MODE. Baud defaults to9600. Parity, databits, stopbits, and xonxoff default as shown above. Port_itdefaults 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

Description Of Modbus_Data_FileComments are specified by a semicolon. Any semicolon makes the remainder of theline a comment and will be ignored.

Each line has three required entries:

Table_Type Table_point CSDB_PointnameWhere Table_Type is one of six kinds: HC IC HR IR WC WR Where Table_Point is1 through 2000 Where CSDB_Pointname is a valid control signal databasepointname.

Following the CSDB_Pointname are optional fields to specify the minimum andmaximum CSDB values. These fields should always be specified except in the caseof logic points.

Refer to section 10-5.5 of SPEEDTRONIC™ Mark V Turbine Control ApplicationManual GEH-6195B for details. Table_Types WR and WC have been added forwrite register and write coil capability from the I+ or OSM to the Modbus slave.

GEH-6126 Chapter 7 Remote Access and Control • 251

MODBUS_L.EXE: MODBUS Listing ProgramAfter F:\UNITn\MODBUS.DAT is completed, the document F:\UNITn\MODBUS.LSTis created for use by the DCS vendor for setting up the DCS. This file documents theModbus tables.

The Modbus Listing Program, G:\EXEC\MODBUS_L.EXE, reads the necessaryconfiguration files on the TCI and creates F:\UNITn\MODBUS.LST. This file containsa list of the coil and register maps, complete with scaling information. A new listingfile must be created each time F:\UNITn\MODBUS.DAT is changed, or when themode defined for the Modbus link is changed in F:\IO_PORTS.DAT. This Modbuslisting 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 andregister. 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 DOSline in the unit specific directory F:\UNITn.

There is a corresponding Modbus listing program for Cimplicity. It isCimMod_L.exe. To run this program, create a DOS prompt for the CimplicityConfiguration Cabinet. Change directory to the data directory. Then typeCimMod_L.

The format is shown by typing MODBUS_L /? which returns printout resembling theillustration below:

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, 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.

252 • Chapter 7 Remote Access and Control GEH-6126

MODBUS_L Command Format

The options described below are used to modify the format ofF:\UNITn\MODBUS.LST as follows:

scaling (ENGLISH, METRIC, CUSTOM, HARDWARE) determines whichF:\UNITn\*.SCA file is used (ENGLISH.SCA is the default file).

mode (RS16, RU16, UN12, HW12, NATIVE) used must match the mode definedin F:\IO_PORTS.DAT. MODBUS_L does not read this file, it must be addedmanually.

quiet if used, F:\UNITn\MODBUS.LST should be checked for error messages, asthe 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 ofnonlogic (analog) signals.

MODBUS_L will flag duplicate coil or register assignments, undefined Mark VCSDB pointnames, invalid formats, invalid coil or register numbers, conversionerrors, etc. Resolve all errors before communicating with the DCS.

F:\UNITn\MODBUS.LST: MODBUS Listing FileAn example F:\UNITn\MODBUS.LST file is shown below:

+HR0001 | SWREF_CMD | SIGN16 | 512 | 0 | MW |+HR0002 | DRVAR_CMD | SIGN16 | 512 | 0 | MVAR |+HR0003 | SC43LOAD | UNS16 | 65536 | 0 | STATE | HR0004 | @SPARE | spare | HR0005 | @SPARE | spare |+HR0006 | L90PSEL_CMD | SIGN16 | 512 | 0 | MW | PRESELECTED LOAD ANALOG SETPOINT+HR0009 | SC43 | UNS16 | 65536 | 0 | STATE | TURBINE CONTROL SELECTION HR00010 | SS43 | UNS16 | 65536 | 0 | STATE | TURBINE COMMAND STATESELECTION HR0200.00| L52GX | PACKED | GENERATOR BREAKER CLOSURE HR0200.01| L94X | PACKED | NORMAL SHUTDOWN HR0200.02| L30D_SD | PACKED | NORMAL DISPLAY MESSAGE “ SHUTDOWN STATUS” HR0200.03| L30D_SU | PACKED | NORMAL DISPLAY MESSAGE “ STARTUP STATUS”+HC0001 | L1FAST_CPB | LOGIC | FAST LOAD START SIGNAL+HC0002 | L1START_CPB | LOGIC | START SIGNAL+HC0003 | L70R4R_CPB | LOGIC | SPEED SETPOINT RAISE COMMAND PUSHBUTTON+HC0004 | L70R4L_CPB | LOGIC | SPEED SETPOINT LOWER COMMAND PUSHBUTTON

F:\UNITn\MODBUS.LST

GEH-6126 Chapter 7 Remote Access and Control • 253

Each line in F:\UNITn\MODBUS.LST contains the following information in thisorder:

• (Write Status)

• Table Point

• CSDB Pointname

• Mode

• Gain

• Offset

• Units

• Longname

(Write Status) – A preceding plus sign (+) indicates that this is mapped to a Mark Vcommand. In this case it is legal for the DCS to request a write to the point, and thusthe TCI issues the command to the Mark V. The sample listing shows holdingregister 1 as an analog command, holding coil 1 as a logic command, and holdingregister 9 as a enumerated state variable that can be written to the Mark V. LogicMark V commands can not be written if packed into holding registers (see abovesection 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 arediscussed in Chapter 5.

Table Point – indicates which one of the four Mapping Tables and what point on thetable is used for this point.

CSDB Pointname – Mark V control signal database pointname that the coil orregister 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 andOffset for registers. A entry of HEX indicates that this point is not normallyconverted into engineering units, but displayed in hexadecimal. Special points, suchas 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_Loverwrites any changes.

254 • Chapter 7 Remote Access and Control GEH-6126

Modbus Data Format And Scaling

Modbus Data Conversions: LogicsLogic control database signal values can be transmitted to the DCS using either coilsor registers. Coil data conversion corresponds to a single logic control databasesignal with the LSB indicating its state.

When registers are used to transmit logic control database signal values, each bitcorresponds to the state of a logic control database signal. A register having 16 bitscorresponds to a group of (up to) 16 logicals with the least significant bit being thefirst logic CSDB signal in the group, and the MSbit as the last logic CSDB signal inthe group. The two bytes are packed into the Modbus message using the normal rulesfor MSB and LSB order. The values of undefined bits in a packed register aretransmitted as 0. Read carefully for details on the modes used in transmission ofdata, as some modes may not be suitable for bit packed registers.

Modbus Data Conversions: AnalogsAnalog control database signal values can be transmitted using registers only. SinceDCS vendors handle analog signals in different ways, such as 12 bit positivenumbers, 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 sectiondefines 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 mostunderstandable level. The implementation of these algorithms do not always followthese algorithms directly as there are many different schemes used to preventmathematical overflows in computations. The choice of the final implementation isleft to the DCS vendor.

RS16If a point is of data type SIGN16, it is a signed 16-bit number. In this mode, the mostsignificant bit of the 16 bit analog signal is treated as a sign bit, where a one is usedto for negative values. C2 type signals are transmitted modulo 32768 to prevent thesign bit from being set. H2 and X2 types are transmitted directly with an assumedvalue of (-32768 to +32767). The convention of assuming the raw value is a fractionfrom -1.0 to +1.0 was used in defining the Modbus Gain and Offset. This allows theGain to indicate the maximum (and minimum) value when the Offset is zero. TheModbus listing file defines the Modbus Gain and Offset required to calculate thevalue 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 forconversion to DEG F. If the register value is 1120, the conversion to engineeringunits is:

Engineering units = (1120) / 32768 * 2048 + 0

Engineering units = 70 DEG F

GEH-6126 Chapter 7 Remote Access and Control • 255

RU16If a point is of data type UNS16, it is an unsigned 16-bit number. This modetransmits F2 analog signals as unsigned 16 bit numbers by adding 32768. The mostsignificant bit therefore turns from a sign bit into a bit with a weight of 32768. Thistransforms the range of F2 signals to [0,+65535]. The Modbus listing file defines theModbus Gain and Offset required to calculate the value into engineering units, withthe 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 ofthe 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 requestedas an unsigned number. If the register value of a thermocouple was requested, itshows that in UNS16 mode the Modbus Gain is 4096, and the Offset is -2048 forDEG 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.

UN12If a point is of data type UNS12, it is an unsigned 12-bit number. The function of thismode is to restrict signals to a range of [0,+4095]. The Modbus listing file’s ModbusGain and Offset define the conversion into engineering units, where the conversionis:

Engineering units = (Raw_value) / 4096 * GAIN + OFFSET

For example, if the register value of a thermocouple is requested, the listing fileshows that the Modbus Gain is 4096 and the Offset is -2048 to get to DEG F. Theconversion 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 andshould be avoided.

Certain internal signal types (e.g. H2, X2) become meaningless if restricted to theUNS12 range and would therefore be transmitted directly without conversion (ifrequested by the DCS). Logics packed into registers also become meaningless if theregister’s value is converted. The Modbus listing file will list these points with amode of UNS16. Fortunately most analog signals that are of interest to the DCS arein an F2 representation. A gain of 1/16th is applied to F2 signals and 2048 is added toconvert the range from [-32767,+32767] to [0,+4095]. The unsigned 16 bit signaltype C2 is transmitted Modulo 4096 to also restrict the range to [0,+4095].

256 • Chapter 7 Remote Access and Control GEH-6126

HW12A special version of the UNS12 mode is available for use with some models of DCSsystems. 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 andOFFSET conversion. In these DCS systems, no OFFSET is allowed in theconversion of analog setpoint commands to Modbus register values, only a GAIN.

To accommodate these systems, the HW12 mode reports data to the DCS usingUNS12 mode, but uses a different formula for analog setpoint commands sent fromthe DCS to the Mark V. This scheme allows the DCS the full positive range of theMark V command, but does prevent sending negative values. Analog setpointcommands in these systems are usually scaled in percentages.

Make sure that the programming in the DCS reflects the fact that the scaling of theanalog setpoint command to the Mark V is different than the scaling of the feedbacksignal from the Mark V. (The HW12 mode analog setpoint command is the onlyplace where this is true.)

For data from the Mark V to the DCS, the conversion is the same as the UNS12mode:

Engineering units = (Raw_value) / 4096 * GAIN + OFFSET

For setpoint commands from the Mark V to the DCS and the DCS to the Mark V, theconversion 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 ModbusGain is 256 and the Offset is 0 to get percent. The conversion of the register value of1216 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

GEH-6126 Chapter 7 Remote Access and Control • 257

NATIVEIf a point is of data type NATIVE, all analog signals are transmitted in their internalMark V representation. This is the recommended mode because the signals can betransmitted directly without any manipulation, which could result in decreasedresolution. Any 32-bit signal requires 2 registers to be assigned to it. These datapoints 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:

• L1 logic signal, least significant bit indicating state zero or one.

• F2 16 bit signed two’s complement representation, range: [-32767,+32767].

• C2 16 bit unsigned representation, range: [0,+65535].

• S2 16 bit signed representation, range: [-32767,+32767].

• H2 16 bit unsigned representation used for bit masks.

• X2 16 bit unsigned representation used to form the lower 16 bits of long, 32 bit values.

• F4 32 bit signed two’s complement representation.

• C4 32 bit unsigned representation.

• H4 32 bit unsigned representation used for bit masks.

• R4 32 real floating point number.

Modbus Command And Response Definition

IntroductionThis section describes the commands and responses supported by the TCI toimplement the Modbus communications and control functions needed. The TCI willbe a slave station on an RS232 data link and will respond to commands from themaster. Messages are transmitted and received using the RTU transmission mode,which is one of two Modbus transmission modes, where RTU transmits data in eightbit bytes. The other mode, where characters are transmitted in ASCII, is notsupported. 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%

258 • Chapter 7 Remote Access and Control GEH-6126

RTU Transmission Modeslave address – number from 0 to 255 and specifies the unit with which tocommunicate (a slave address of zero is considered a broadcast message to allslaves).

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. Theabbreviation CRC stands for Cycle Redundancy Check, MSB stands for MostSignificant Byte, and LSB stands for Least Significant Byte. These bytes are used forerror checking and are calculated for each transmitted and received message toinsure that no transmission error has occurred while the message was in transit. Themethod for calculating the CRC-16 is a public protocol and is described in numeroustextbooks and the Gould Modicon Modbus Protocol Reference Guide. Please refer tothese other documents for information on calculation of a correct CRC.

Modbus over Ethernet adds the header below to the message formats. All the samefunctions 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%

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 theTCI Modbus to receive the rest of the message. The rest of the message is exactlywhat is sent and received over the serial connections.

Message ErrorsWhen a message is received that cannot be acted upon, the message is either ignoredand the TCI waits for the next message or it is responded to with an exceptionmessage.

Any messages that are misunderstood, incomplete, or altered in some manner asindicated by framing error, parity error, or CRC-16 error are always ignored due tothe fact that it is not possible to reliably determine for whom the message wasintended. It is the master’s responsibility to detect this timeout condition and resendthe message as necessary (see the section TCI Modbus Configuration above).

Any time a message receipt is in progress and an interval of time corresponding to3.5 character times (based on the baud rate) occurs without receipt of a character, themessage receipt in progress is aborted and ignored. Message failures due to othercauses are responded to with an exception response if no reception error has occurredand if the message was not a broadcast (slave address was zero).

GEH-6126 Chapter 7 Remote Access and Control • 259

The exception code responses that are supported when a normal response isimpossible is shown in the chart below. (see the section above on TCI ModbusConfiguration concerning exception codes 04 and 06).

Exception Code Name Meaning

01 Illegal Function The message function received is notsupported

02 Illegal DataAddress

The address referenced in the data field isnot in a permissible range.

03 Illegal DataValue

The value transmitted in the data field isillegal.

04 Failure inAssociatedDevice

Information requested cannot be provideddue to a communication failure withassociated unit as specified by the slaveaddress.

06 Device Busy Information requested cannot be provideddue to a communication time out with theassociated unit as specified by the slaveaddress.

Exception Code Responses

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%

Exception Code Response Formatslave address – must be in the range [1-255]. Zero is not allowed as a reply, as it isonly used in broadcast messages from the master.

function code – is always equal to the master’s function code with the mostsignificant bit set. Therefore, an exception response sent back to a master that hassent a message with function code 02 hex would have a function code of 82 hex (or130 decimal) in the exception reply.

exception code – as shown in chart below, only codes 01 through 04 and 06 aresupported.

260 • Chapter 7 Remote Access and Control GEH-6126

Function Code Details

Function Code,Hex

Description

01 Read Holding Coils

02 Read Input Coils

03 Read Holding Registers

04 Read Input Registers

05 Force (Write) Single Holding Coil

06 Preset (Write) Single Holding Register

07 Read Exception Status

08 Diagnostic

0F Force (Write) Multiple Holding Coils

10 Force (Write) Multiple Holding Registers

DCS Function Codes

This chart lists the function codes supported by the TCI included in the messagessent from the DCS. Six of the eight function codes implemented in the TCI are usedto read from and/or write to the four table types. See the above sections regardingmapping tables. Each function code and the TCI’s replies are described below.

Function Code 01: Read Holding CoilsFunction code 01 is used to read the holding coil table. The format of a messagefrom 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%

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 thanthe highest holding coil number available in the holding coil table. The startingholding coil number is equal to one less than the number of the first holding coilreturned 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 orderbyte of the starting holding coil number field is sent as the first byte. The low orderbyte is sent next.

number of holding coils value – two bytes in length and must be in the range from1 to 2000 inclusive. It specifies the number of holding coils returned in the normalresponse. The sum of the starting holding coil value and the number of holding coilsvalue must be less than or equal to the highest holding coil number available in theholding coil table. The high order byte of the number of holding coils field is sent asthe first byte. The low order byte is sent next.

GEH-6126 Chapter 7 Remote Access and Control • 261

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 bytesfollow.

data field – is packed holding coil status data. Each byte contains eight holding coilvalues. The LSbit of the first byte contains the value of the holding coil whosenumber is equal to the starting holding coil number plus one. The value of theholding coils are ordered by number starting with the LSbit of the first byte of thedata field and ending with the MSbit of the last byte of the data field. If the numberof the holding coils is not a multiple of eight, then the last data byte contains zeros inone to seven of its highest order bits.

Function Code 02: Read Input CoilsFunction 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%

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 thehighest input coil available in the input coil table. The starting input coil number isequal to one less than the number of the first input coil returned in the normalresponse to this request, i.e. to get the first input coil, input coil number one, enterzero for the starting input coil number. The high order byte of the starting input coilfield 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 1to 2000 inclusive. It specifies the number of input coils returned in the normalresponse. The sum of the starting input coil value and the number of input coils valuemust 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. Thelow order byte is sent next.

262 • Chapter 7 Remote Access and Control GEH-6126

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 bytesfollow.

data field – is packed input coil status data. Each byte contains eight input coilvalues. The LSbit of the first byte contains the value of the input coil whose numberis equal to the starting input coil plus one. The value of the inputs are ordered bynumber starting with the LSbit of the first byte of the data field and ending with theMSbit of the last byte of the data field. If the number of the input coils is not amultiple of eight, then the last data byte contains zeros in one to seven of its highestorder bits.

Function Code 03: Read Holding RegistersFunction code 03 is used to read holding registers. The format of a message fromthe 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%

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 lessthan the highest holding register number available in the holding register table. Thestarting holding register number is equal to one less than the number of the firstholding register returned in the normal response to this request, i.e. to get the firstholding register number, holding register number one, enter zero for the startingholding register number. The high order byte of the starting holding register numberfield 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 rangefrom 1 to 128 inclusive. It specifies the number of holding registers returned in thenormal response. The sum of the starting holding register value and the number ofholding registers value must be less than or equal to the highest holding registernumber available in the holding register table. The high order byte of the number ofholding registers field is sent as the first byte. The low order byte is sent next.

GEH-6126 Chapter 7 Remote Access and Control • 263

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 numberof data bytes follow. The byte count specifies the total number of bytes in themessage following the byte count, not including the two CRC-16 bytes.

holding registers – are returned in the data field in order of number with the lowestnumber holding register in the first two bytes, and the highest number holdingregister in the last two bytes of the data field. The number of the first holding registerin the data field is equal to the starting holding register number plus one. The highorder byte is sent before the low order byte of each holding register.

Function Code 04: Read Input RegistersFunction code 04 is used to read input registers. The format of a message from themaster 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%

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 thanthe highest input register number available in the input register table. The startinginput register number is equal to one less than the number of the first input registerreturned in the normal response to this request, i.e. to get the first input register, inputregister number one, enter zero for the starting input register number. The high orderbyte of the starting input register number field is sent as the first byte. The low orderbyte is sent next.

number of input registers – value is two bytes in length and must be in the rangefrom 1 to 128 inclusive. It specifies the number of input registers returned in thenormal response. The sum of the starting input register value and the number of inputregisters value must be less than or equal to the highest input register numberavailable in the input register table. The high order byte of the number of inputregisters 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 numberof data bytes follow. The byte count specifies the total number of bytes in themessage following the byte count, not including the two CRC-16 bytes.

264 • Chapter 7 Remote Access and Control GEH-6126

input registers – are returned in the data field in order of number with the lowestnumber input register in the first two bytes, and the highest number input register inthe last two bytes of the data field. The number of the first input register in the datafield is equal to the starting input register number plus one. The high order byte issent before the low order byte of each input register.

Function Code 05: Force Single Holding CoilFunction code 05 is used to force (or write) a single holding coil in the holding coiltable. 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% ))+

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 thehighest holding coil number available in the holding coil table. The holding coilnumber is equal to one less than the number of the holding coil forced, i.e. to changethe first holding coil, holding coil number one, enter zero for the holding coilnumber. The high order byte of the starting holding coil number field is sent as thefirst byte. The low order byte is sent next.

state byte – sent by the master with only two possible values. A zero is sent (00h) toturn the specified holding coil off (set false). A value of 255 is sent (FFh) to turn thespecified holding coil on (set true). The state byte is always followed by a single bytewith value zero.

Format of normal message reply from the slave is identical to the receivedmessage.

Function Code 06: Preset Single Holding RegisterFunction code 06 is used to preset (or write) to a single holding register. The formatof 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%

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 thehighest holding register number available in the holding register table. The holdingregister number is equal to one less than the number of the holding register changedby 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 startingholding 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 whichthe holding register specified by the holding register number field is preset. The firstbyte in the data field contains the high order byte of the preset value. The secondbyte in the data field contains the low order byte.

GEH-6126 Chapter 7 Remote Access and Control • 265

Format of normal message reply from the slave is identical to the receivedmessage.

Function Code 07: Read Exception Status.Function code 07 is used to read the exception status data, defined as the first eightholding coils. These can be used to indicate slave controller status or condition ofany other state. Function code 07 thus provides a short form of request for thepurpose 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%

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%

data byte field – the normal response is packed holding coil status data. The databyte contains eight holding coil values. The LSbit of the byte contains the value ofthe holding coil number one (1). The MSbit contains the value of holding coilnumber eight.

266 • Chapter 7 Remote Access and Control GEH-6126

Function Code 08: DiagnosticFunction code 08 is used to get diagnostic data. The purpose of the diagnosticmessage to test the communications system (the TCI); it does not affect thecontroller (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%

slave address – zero indicates that the message received is a broadcast. Non-broadcast messages use a slave address in the range [1-255]. The TCI will respond torequests to its designated slave addresses, or to a broadcast. If the message is not abroadcast, the data returned will be from the unit as defined by the slave address andthe TCI system configuration file. In the event that the message is a broadcast, nodata will be returned. Only commands to reset counters and change Listen Onlymode 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%

When a response is sent at all, the normal response to a diagnostic message by theslave is shown above, with each of the fields listed above identical to thecorresponding field sent in the message received from the master except fordiagnostic codes 0Ah through 0Eh, where the required data is returned.

GEH-6126 Chapter 7 Remote Access and Control • 267

DiagnosticCode (Hex)

Name Meaning

00 Return QueryData

The data passed in the data field will be returnedto the DCS without modification.

01 RestartComm Option

This code causes the TCI to reset the RS232 portif necessary. It will also cause a reset of all errorcounters associated with the Modbus link if thehigh order byte of the data field is 255 (0FFh). Ifthe TCI is in Listen Only caused by a previouslyissued command, the condition is reset to normal.A normal response is returned to the masterbefore the restart is executed if and only if the TCIwas not in Listen Only Mode (LOM).

04 Force slave toListen OnlyMode

When this command is received, the TCI will notrespond to any commands other than the RestartComm Option command listed above.

0A ClearCounters

All error counters and the diagnostic register willbe reset. A normal response will be sent. Allcounters are cleared upon each power up, reboot,Clear Counters command or Restart CommOption command.

0B Return BusMessageCount

The total number of messages addressed to thisTCI (broadcast and non-broadcast messagesmodulo 65536 will be returned to the master. Thiscounter is cleared upon each power up, reboot,Clear Counters command or Restart CommOption command.

0C Return BusCRC ErrorCount

The total number of messages detected by theTCI that had a bad CRC modulo 65536 will bereturned to the master. This counter is clearedupon each power up, reboot, Clear Counterscommand or Restart Comm Option command.

0D Return BusExceptionError Count

The total number of exception responsemessages sent by the TCI modulo 65536 will bereturned to the master. This counter is clearedupon each power up, reboot, Clear Counterscommand or Restart Comm Option command.

0E Return BusSlaveMessageCount

The total number of messages addressed to thisTCI (broadcast and non-broadcast) modulo 65536will be returned to the master. This counter iscleared upon each power up, reboot, ClearCounters command or Restart Comm Optioncommand.

12 Return BusOverrunMessageCount

The total number of error in receiving a messagefrom the serial port modulo 65536. This counter iscleared upon each power up, reboot, ClearCounters command or Restart Comm Optioncommand.

Function Code 08 Diagnostic Codes

268 • Chapter 7 Remote Access and Control GEH-6126

Function Code 0F: Force Multiple Holding CoilsFunction code 0F is used to force (or write) multiple holding coils in the holding coiltable. 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%

Function Code 0F Message Format

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 thehighest holding coil number available in the holding coil table. The holding coilnumber is equal to one less than the number of the holding coil forced, i.e. to changethe first holding coil, holding coil number one, enter zero for the holding coilnumber. The high order byte of the starting holding coil number field is sent as thefirst byte. The low order byte is sent next.

number of holding coils value – two bytes in length. It specifies the number ofholding coils to set. The sum of the starting holding coil value and the number ofholding coils value must be less than or equal to the highest holding coil number inthe holding coil table. The high order byte of the number of holding coils field issent 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 isequal to the starting holding coil number plus one. The value of the holding coils areordered by number starting with the LSbit of the first byte of the data field andending with the MSbit of the last byte of the data field. If the number of the holdingcoils is not a multiple of eight, then the last data byte contains unused data in itshighest order bits.

Format of normal message reply from the slave is identical to the received messagewithout the byte count or the data.

Function Code 10: Preset Multiple Holding RegistersFunction 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)

GEH-6126 Chapter 7 Remote Access and Control • 269

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 thehighest holding register number available in the holding register table. The holdingregister number is equal to one less than the number of the holding register changedby 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 startingholding 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 ofholding registers to set. The sum of the starting holding register value and thenumber of holding registers value must be less than or equal to the highest holdingregister number in the holding register table. The high order byte of the number ofholding 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 inthe data field contains the high order byte of each preset value. The next bytecontains the low order byte.

Format of normal message reply from the slave is identical to the receivedmessage without the byte count or the data.

Modbus Master Diagnostics

When debug is on (on by default), global section trace buffer may be viewed withthe command:

gbl2file MModbus_trace# <some_file_name>

where # is 1,2,3...8 depending on which [MODBUS_MASTER_PORT] sectioncorresponds 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

This will display some debugging and program status information.

The trace option may be turned off by adding /NOTRACE to the

command line: MModbus /NOTRACE

If the program encounters a serious error or warning, the result is placed into a logfile as well as the global section trace buffer. The user should check fileG:\LOG\MModbus#.log where # is defined as above.

270 • Chapter 7 Remote Access and Control GEH-6126

StatisticsThe Modbus Master program gathers statistics and makes counters available fordiagnostic purposes. The program MM_stat.exe has been especially designed as aconsole program to communicate with the Modbus Master program andretrieve/control these diagnostic counters. Running MM_stat displays these countersas shown:

F:\USER>mm_stat

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 asspecified 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.

GEH-6126 Chapter 8 Time Sync • 271

Chapter 8 Time Sync

Time SynchronizationTime Synchronization within the Turbine Control is offered with one of thefollowing:

• Lower Accuracy option with software implementation only.

• Time Synchronization option for SPEEDTRONIC™ Turbine Control systemssynchronizes all Turbine Control panels on the stagelink to a Global TimeSource (GTS) with a limited loss of accuracy. In addition, this option sets alloperator interface computer timeclocks to the GTS. It is recommended that theremaining plant equipment, including Distributed Control Systems (DCSs),synchronize to this common GTS.

Time Synchronization Features• Time Signal Sources

• Turbine Control Time Synchronization supports several GTSs.

Timecode signals supported:

• IRIG-A

• IRIG-B

• NASA-36

• 2137

272 • Chapter 8 Time Sync GEH-6126

Supported GTSs that use periodic pulses:• 1 PPS

• 1 PPM

• 1 PPH

Typical GTSs are GPS (Global Positioning System) receivers such as the StarTimeGPS Clock or other time processing hardware. The preferred time sources areUTC(Universal Time Coordinated) or GPS. However, the Time Synchronizationoption also supports a GTS using local time as its base time reference.

GEH-6126 Chapter 8 Time Sync • 273

Software Setup” on page 283 discusses the setup for specifying local or global.

General ArchitectureThe 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 areplaced in these computers. These boards acquire time from the GTS with a highdegree of accuracy.

When the computers receive the time signal, it is sent to the Turbine Control panelsusing a special purpose Stagelink Timesync protocol. This protocol minimizes timelosses. Figure ## show a general plant-wide time synchronization setup.

C o n tro l

T u r b in e

T O

D C S E Q U IP M E N T

* * *

S T A G E L IN K

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

* O p t io n a l

T E R M IN A T IO NR E S IS T O R

G L O B A L

T IM E S O U R C E

T E R M IN A T IO NR E S IS T O R

C o n tro l

T u rb in e

C o n t ro l

T u rb in e

C o n t ro l

T u rb in e

In te r fa c e

O p e r a to r

In te r fa c e

O p e ra to r

In te r fa c e

O p e ra to r

In te r fa c e

O p e ra to r

Typical Time Synchronization Architecture

274 • Chapter 8 Time Sync GEH-6126

Backup SynchronizationRedundancy provides backup time synchronization. Supplying time/frequencyprocessor boards to two or more operator interfaces is redundant. Not all operatorinterfaces require these boards. Those that do not contain time/frequency processorboards do not attempt to send time to the Turbine Control. Instead, they becometime slaves to the selected Stagelink Time Master in the same way that all TurbineControl panels are time slaves.

The Stagelink Time Master is the common operator interface selected by all otherequipment on the stagelink as the official time source. Failure of this source resultsin all time slaves selecting another, but common, operator interface as the newStagelink Time Master.

Documentation OrganizationThis documentation is organized as follows:

OverviewThis section describes Turbine Control Time Synchronization and its function. Anoverview of this documentation, as well as related publications, are also presented inthis section.

Basic Theory of Turbine Control Time SynchronizationThis section describes how Turbine Control time Synchronization works and thelogic that runs the system. An overview of supported GTSs is given in this section.

Hardware SetupThis section describes how to set up the Turbine Control Time Synchronizationhardware.

Software Setup and ConfigurationThis section describes how to configure the software to run Turbine Control TimeSynchronization.

General Timesync OperationsThis section explains some general operations of Turbine Control Timesynchronization. Use of the TIMEUTIL program is described here.

Diagnostics and TroubleshootingThis section discusses how to get general information from Turbine Control Timesynchronization. Other ways to diagnose problems with the Turbine Control TimeSynchronization are explained here.

Sample Timesync ConfigurationsThree examples of possible Turbine Control Time Synchronization setups arediscussed in this section.

GEH-6126 Chapter 8 Time Sync • 275

Appendix A - IRIG NomenclatureDefines the nomenclature for standard IRIG Time Codes.

GlossaryDefines acronyms and terms used in this documentation.

Related DocumentsGE Industrial Systems provides the applicable documents to customers as needed tosupport equipment it supplies. For documentation that covers equipment from othercompanies, 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 MaintenanceGuide 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

Time Synchronization TheoryThis section refers to the High Accuracy synchronization option and explains thebasic theory of synchronizing Turbine Control time to the GTS. Selection of theStagelink Time Master is discussed in this section as well as supported GTSs.

Timesync ProtocolThe Time Processing Board is used to get time for one or more operator interfacecomputers with a high degree of accuracy. Time is then sent to each Turbine Controland operator interface time slave using an internal Stagelink Timesync protocol.This protocol is specifically designed to minimize the loss of accuracy in the timeslaves.

Each operator interface with a Time Processing Board is an available Stagelink TimeMaster. Each available Stagelink Time Master periodically broadcasts anidentification message to all time slaves. Each time slave collects the list ofavailable 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 sameinstant, what local time it has. The Stagelink Time Master notes the global time atthe instant the request for time is received. Next, the Stagelink Time Master returnsthe recorded global time. The time slave computes the difference between thereturned time and the recorded time of request and adjusts its internal timeaccordingly.

276 • Chapter 8 Time Sync GEH-6126

Local time is used for display of real-time data. This is done by adding a local timecorrection to UTC. A node’s internal time clock is normally Global rather thanLocal. This is done because global time steadily increases at a constant rate whilecorrections are allowed to local time. Historical data is stored with global time tominimize 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 modewith a maximum drift of ±2 ms per hour. In most cases, this allows sufficient time torepair the GTS without severe disruption of the plant’s system time.

If the primary Stagelink Time Master becomes inoperative, then each of the timeslaves picks another, but common, secondary Stagelink Time Master. This meansthat 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 basesfor their references.

The Turbine Control selects the best Stagelink Time Master if multiple Stagelinksexist and Stagelink Time Masters exist on each network. This means that if twooperator interfaces on the same stagelink are available Stagelink Time Masters andone of them has lost contact with the GTS time signals, each time slave selects theother available Stagelink Time Master as its time reference of choice.

If multiple available Stagelink Time Masters exist, each time slave selects the currentTime Master based on the following:

• Is the Time Master tracking the GTS

• Which Time Master has the lowest Stagelink (ARCNET®) address.

• Supported GTSs

The Time Processing Boards support the use of several different time sources.However, the Time Synchronization software does not support all source supportedby the Time Processing Board.

GEH-6126 Chapter 8 Time Sync • 277

The following is a list of time source, and their characteristics that are supported byboth the Time Processing Board and the Time Synchronization software:

• Modulated IRIG-A, IRIG-B, 2137, or NASA-36 timecode signals.

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

• 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

• 1 PPS (one pulse per second) using the External 1 PPS input signal of the TimeProcessing Board

TTL/CMOS compatible voltage levels, positive edge on time

• 1 PPM (one pulse per minute) using the Event Capture input signal of the TimeProcessing Board

TTL/CMOS compatible voltage levels, positive edge on time

20 nanosecond minimum pulse width, 250 nanosecond minimum period

• 1 PPH (one pulse per hour) using the Event Capture input signal of the TimeProcessing Board

TTL/CMOS compatible voltage levels, positive edge on time

20 nanosecond minimum pulse width, 250 nanosecond minimum period

No Signal using the low-drift clock on the Time Processing Board in flywheel modeas the sole time source for the plant

GPS InterfaceThis applies only to bc627AT Time Processing Board

There are two-time source supported by the Time Processing Board but notsupported by the Time Synchronization software. These signals are XR3 tomcodsand Negative Edge on time inputs.

Please refer to Appendix A for IRIG timecode nomenclature.

278 • Chapter 8 Time Sync GEH-6126

Hardware Setup

Testing the Time and Frequency BoardThis section discusses the proper testing procedures for the bc620AT/bc627AT Timeand Frequency Board.

To set up the Time Synchronization hardware, the Time Processing Board must becorrectly installed in the operator interface and then configured for this application.The setup of the Time Processing Board for the Turbine Control TimeSynchronization option, involves setting hardware jumpers to select the base I/Oaddress 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 forTPRO_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 theBoard” on page 282 for TPRO_PC and “Connecting the Operator Interface” onpage 282).

JP1

SW1

J1

J2

BANCOMM bc620AT

I/O ADDRESS

IRQ JUMPERS

Typical bc620AT/bc627AT Time and Frequency Module

Board InstallationThe bc620AT or bc627AT board can be placed in any spare ISA(Industry StandardArchitecture) slot of an operator interface. See the PC vendor user manual thatcomes with the operator interface for proper installation procedures. SeeManufacturing documentation for details of soft switch settings.

GEH-6126 Chapter 8 Time Sync • 279

Setting Base I/O AddressThe bc620AT or bc627AT board is shipped from the Bancomm factory with a baseI/O address of 0x0300. This address conflicts with the base I/O address used inoperator 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 A9 A8 A7 A6 A5 A4

1 2 3 4 5 6

OPEN

ON

OFF

SW1

A9 A8 A7 A6 A5 A0A1A2A3A4

1 0 1 0 0 0 000 0 = 0x0280

ONOFF

= 0= 1

INDICATES DIRECTION OF TOGGLE

SW1 Base I/O Address switch selections

Setting the IRQAdjust the board’s IRQ setting to No IRQ as shown in the figure below:

1 3 5 7 9 11 13 15 17 19 21 23Pin

IRQIR15

IR14

IR12

IR11

IR10 IR

9IR7

IR6

IR4

IR5

IR3

NOIRQ

JP1

IRQ selection on bc620AT and bc627AT

Connecting the GTS to bc627ATThe bc627AT has two connectors, J1 and J2 (see Figure 3-1). J1 is not used for thisapplication. J2 is a 12-pin receptacle and is used to connect to a GPS receiver coremodule. Please refer to bc627AT GPS Satellite Receiver Addendum User’s Guidefor information regarding placement of the GPS antenna.

280 • Chapter 8 Time Sync GEH-6126

Connecting the GTS to bc620ATThe bc620AT has two connectors, J1 and J2 (see Figure 3-1). J2 is not used for thisapplication. 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 BNCadapter is used. This connector consists of a 15-pin plug D-connector, and five BNCreceptacle connectors. Figure 3-4 shows a diagram of this adapter.

1 PPS Output

1 PPS Input

Timecode Output

Event Input

Timecode Input(Modulated)

ReceptacleBNC’s (GTS Source)

(Flywheel Mode Out)

(1 PPS)

(Optional External Use)

(1 PPM or 1 PPH)

(IRIG-A, IRIG-B,NASA36, or 2137)

Adapter

15-pinD Plug

Tobc620AT

J1

15-Pin D to BNC Adapter.

Time Processing Board TPRO_PCThe illustration below shows the general layout of the TPRO_PC board.

P2

J3

J2

P4

P3

J1

IRQ JUMPERS

I/O ADDRESS

TPRO_PC Time Processing Board

GEH-6126 Chapter 8 Time Sync • 281

Board InstallationThe TPRO_PC board can be placed in any spare ISA (Industry StandardArchitecture) slot of an operator interface. See the PC vendor user manual thatcomes with the operator interface for proper installation procedures.

Setting Base I/O AddressThe TPRO_PC board is shipped from KSI Odectics with a base I/O address of0x0300. This address conflicts with the base I/O address used in operatorinterfaces 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 the figure below:

11 10 9 78 5 46Pin

I/O ADDR JP=0

P3

Connected Pins = 0

Open Pins = 1

0 2 8 0

0000 0010 1000 0000 1110 9 8 7 6 5 4

Base I/O Address pin selections

Event InputThe 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, adjustthe board’s settings as shown in the figure below:

P4

E X DEvent Input enabled on TPRO_PC

Setting the IRQAdjust the board's IRQ setting to No IRQ as shown in the figure below:

234567 10111214 15

IRQNO IRQ

P2

IRQ selection on TPRO_PC

282 • Chapter 8 Time Sync GEH-6126

Connecting the GTS to the BoardThe 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 ofGTS determines how J1 is interfaced. For most GTSs, a 15-pin to BNC adapter isused. This connector consists of a 15-pin plug D-connector, and five BNC receptacleconnectors. The figure below shows a diagram of this adapter. J2 can be connectedto a timecode input and J3 may be used as a timecode output.

1 PPS Output

1 PPS Input

Timecode Output

Event Input

Timecode Input(Modulated)

ReceptacleBNC’s (GTS Source)

(Flywheel Mode Out)

(1 PPS)

(Optional External Use)

(1 PPM or 1 PPH)

(IRIG-B or NASA36)

Adapter

15-pinD Plug

ToTPRO_P

J1

15-Pin D to BNC Adapter.

Connecting the Operator InterfaceAll available Stagelink Time Masters are wired as a bus configuration using RG-58coaxial 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 contrastto the 50 ohm resistors required for Ethernet (10 MHz) or the 93 ohm resistorsrequired for Stagelink (2.5 MHz).

!Caution

Use the same lightning protection techniques forthe timelink as for Stagelink or Ethernet. Seethe documentation for these networks forprotection techniques to be used.

!Caution

The timelink cabling (RG-58) is identical to thatused for Ethernet and very similar to that usedfor Stagelink (RG-62). Label all cables used fortimelink differently than the other networkcables. Damage to equipment is possible if thesecables are interconnected.

GEH-6126 Chapter 8 Time Sync • 283

Software SetupThe Timesync software must be configured correctly in order to communicate overthe Stagelink. Data files must be modified to define the Stagelink Time Master andspecify the time base.

Timesync Data FileThe Stagelink driver program in the operator interface sends time to the TurbineControl panels. This program uses the file F:\TIMESYNC.DAT to get informationregarding timesync/timeset information. The key lines in F:\TIMESYNC.DAT areshown 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]----------------------------------------------------------

File ConfigurationA template file for timesync is in G:\DATA\TIMESYNC.DAT. Copy this templatefile to F:\TIMESYNC.DAT and edit as required. An example of the template fileTIMESYNC.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; --------- ----------------------------------

284 • Chapter 8 Time Sync GEH-6126

; 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 operator ;interface does not require a time/frequency board in order to be a time slave.;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 LOCALMARKV_TIME LOCALTIME_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.;;-------------------------------------------------------------------

GEH-6126 Chapter 8 Time Sync • 285

The file’s key words and their significance are listed below:

• TIMESYNC

If the "TIMESYNC" line is missing, the operator interface will not haveStagelink Time Master functions. However, the other lines may be specifiedsuch 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]

• controller

[BC620AT | BC627AT | TPRO_PC]

BC620AT / BC627AT / TPRO_PC is the name of the Time/FrequencyProcessor board.

• MODE <mode>

<mode> defines the type of global time source, and is one of the following:

IRIG-B Modulated IRIG-B Time Code Signal

IRIG-A Modulated IRIG-A Time Code Signal (N/A for TPRO_PC)

NASA-36 Modulated NASA-36 Time Code Signal

2137 Modulated 2137 Time Code Signal (N/A for TPRO_PC)

1PPS One pulse per second time input

1PPM One pulse per minute time input

1PPH One pulse per hour time input

FLYWHEEL Use the Time Processing Board itself as the GTS

GPS GPS Reference Signal (bc627AT only)

LEVEL_SHIFT is used if IRIG-x, NASA-36, or 2137 timecodes are dc LevelShifted instead of modulated signals. This applies to bc620AT only.

TIMESYNC LOWRES

This statement implies that the Lower Accuracy Time Synchronization optionwith software implementation only has been selected.

TIMESYNC SLAVE

This statement implies that the Lower Accuracy Time Synchronization optionwith software implementation only has been selected and that this interface canonly be a Slave, never a Master.

LOCAL_TIMESET [ENABLED | DISABLED]

This line defines whether the operator interface time is set to the time defined bythe 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 theinternal time of the IDP or <I> is set to UTC or Local Time.

286 • Chapter 8 Time Sync GEH-6126

MARKV_TIME [LOCAL | UTC]

This customer-specified parameter defines whether the Mark V panel time is UTCbased or Local Time based.

TIME_SOURCE [LOCAL | UTC]

This line specifies whether the GTS is UTC based or Local Time based. Thisparameter applies only to timecode GTSs; it does not apply to pulse input timesources.

TIME_LOAD [MANUAL | LOCAL | NETWORK]

This line enables or disables the automatic loading of initial major time fields. NoStagelink Timemaster will send time until all major time elements are loaded, andtime is locked to the GTS.

MANUAL disables the operator interface as a Stagelink time master until major timeelements are manually entered. See “Using the TIMEUTIL Program” on page 288describing the TIMEUTIL program for more details.

LOCAL specifies that major time is loaded automatically from the operatorinterface’s CMOS clock.

NETWORK specifies that major time is loaded from another Stagelink Timemaster,assuming multiple operator interfaces on the Stagelink have Time/Frequencyprocessor boards installed.

For IRIG-A, IRIG-B and NASA-36 timecodes, major time elements consist only ofthe year (since these are time-of-year timecodes).

For 2137 timecode, major time consists of current year, month and day, as this is atime-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.

Note All operator interfaces in a system must be setup in F:\TIMESYNC.DAT inan identical fashion, with the exception of those computers not having a TimeProcessing card installed. Failure to have identical system setup can cause shifts inthe Stagelink Time Reference upon power down of the primary Stagelink TimeMaster.

Note Operator interfaces not containing a Time Processing card should have theidentical lines in F:\TIMESYNC.DAT, but with the "TIMESYNC..." linecommented out.

GEH-6126 Chapter 8 Time Sync • 287

TCI Control Panel AppletWhen the TCI system is installed, a Windows NT applet, TCI, is created. With thisapplication, a TCI dialog box containing a tab labeled Time Sync appears. Under thistab, the user is able to make selections concerning the Time Acquisition Hardwareand High Resolution Time Card.

If TCI setup is told that a Time Processing Board exists, the fields containing theBase 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 appletis shown below:

Timesync OperationThis chapter covers normal timesync/timeset operations, as well as use of theTIMEUTIL program.

General Operations• Upon bootup, no operator interface acts as an available Stagelink Timemaster

until the following conditions are met:

• Major Time elements (year, month, day etc.) have been acquired from CMOSmemory, another Stagelink Time Master, or manually through the TIMETUTILprogram.

• The GTS has established its presence and the Time Processing Board hasasserted 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 afterMajor Time was loaded.

• For GPS operation (bc627AT), timesync functions will not commence until thebc627AT has established contact with 4 satellites and determined its position.Depending on installation conditions, this may take anywhere from 3 to 20minutes.

288 • Chapter 8 Time Sync GEH-6126

Note The first item number above does not occur automatically upon bootup ifthe line TIMELOAD MANUAL is specified in F:\TIMESYNC.DAT. Use ofthe TIMEUTIL program is required to load major time elements in this case.

• Every 20 seconds, each available Stagelink Time Master broadcasts anidentification message announcing its availability.

• Every 20-32 seconds, each Turbine Control panel asks the selected StagelinkTime Master for the current date and time. It jumps or slews its internal timebased on the time error calculated. The rate of slew allows for sub-milliseconderrors, assuming the GTS is stable.

• Every 60 seconds, all nodes select the Stagelink Time Master of choice, if morethan one is available. This selection is based on Stagelink address, timesyncaccuracy, and tracking status (as stated in “Time Synchronization Theory” onpage 275).

• Every 20 minutes, each operator interface with the LOCAL_TIMESETENABLED line in F:\TIMESYNC.DAT performs a TIMESET function by askingthe selected Stagelink Time Master for the current date and time. Unlike thetimesync function in the Turbine Control, the timeset function in the operatorinterface does not slew its internal time. Instead, it jumps. The time error in thistimeset function is typically ±10 ms, assuming the GTS is stable.

• Each available Stagelink Time Master does a limited amount of stabilitychecking on the Global Time Source (timecode GTSs only). If the time-of-yearever 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 aminimum of three minutes. If the time-of-year continuously increases at anormal rate for more than three consecutive minutes, the timesync functionautomatically resumes.

Using the TIMEUTIL ProgramThe TIMEUTIL program controls time synchronization in the operator interfacefunctioning as the Stagelink Time Master. This program is used to do the following:

• Obtain status about the Stagelink Time Master, and other available time masterson the Stagelink

• Enable or Disable the timesync functions

• Set the Major Time in the Stagelink Time Master

TIMEUTIL is a maintenance program and is only accessible from the CommandConsole Window. If run without parameters, TIMEUTIL gives limited help on itsusage. Listed below are a few operations in TIMEUTIL.

Turning Off the TIMESYNC FunctionTo turn off the timesync function in an available Stagelink Time Master, enter:

C:\> TIMEUTIL TIMESYNC DISABLE

Restoring the TIMESYNC FunctionTo restore the timesync function in an available Stagelink Time Master, enter:

C:\> TIMEUTIL TIMESYNC ENABLE

GEH-6126 Chapter 8 Time Sync • 289

Loading MAJOR TIME into the Time Processing BoardDepending on the type of GTS and TIME_LOAD option specified inF:\TIMESYNC.DAT, the operator interface may not act as an available StagelinkTime Master until Major Time is loaded and the Time Processing Board is locked onto 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

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 theGTS is UTC based, then a UTC major time should be loaded. Conversely, if theGTS is Local based, then the major time entered should be local.

If the overall timesync function is not turned off, the operator interface automaticallyassumes Stagelink Time Master duties as follows:

• After the next pulse input if the GTS is a pulse

• After the next timecode frame if the GTS is a timecode

• Immediately if the timesync mode is set to FLYWHEEL.

• If "dd-mmm-yyyy hh:mm:ss.cccc" is omitted from the command line, TIMEUTILprompts for this.

Diagnostics and TroubleshootingThis chapter covers some of the Turbine Control Time Synchronization’s built-indiagnostics and troubleshooting features. TIMEUTIL and the trace buffers arediscussed here.

Obtaining General Information About the TurbineControl Timesync FunctionThe information available about Turbine Control Timesync is formatted such that itmay exceed 25 lines of output. For this reason, set the screen to 50 line mode byentering:

C:\> V50

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

The information returned by TIMEUTIL STATUS varies slightly depending onwhether the GTS is a timecode signal, or pulse input.

290 • Chapter 8 Time Sync GEH-6126

Below is a sample output from TIMEUTIL STATUS for an IRIG-B GTS. This examplewas done on May 23, 1997, the 143rd day of the year.

-------------------------------------------------------------------- <I+> TIMESYNC STATUSOverall TIMESYNC Function: ENABLEDTIMESYNC Controller: bc620ATTIMESYNC Mode: IRIG-B (Modulated) Status: TRACKINGGlobal Time Acquired: YES Year: 1997 Days: 143Pulse Correction in Use: N/AMajor Time Load Flag: LOCAL CMOS

Global Time Source: UTCMark V Panel Time: LOCALMark V LM Panel Time: UTC<I> / <G> CPU Time: LOCAL Local Windows NT Timeset: ENABLEDNetwork Address Status Selected 1 0x1F 0x1903 x 2 0x20 0x1903 3 0x22 0x1903

Network #1, Local ARCNET address: 0x1F-----------------------------------------------------------------------------------------------------

Items to Note in the Information Shown Above:

• The GTS is IRIG-B, and current status is TRACKING (the GTS is present).Otherwise, current status would be FLYWHEELING rather than TRACKING.

• If Global Time Acquired was NO, then this operator interface is not going toattempt to pass time to other nodes on the Stagelink. NO, implies that the IRIG-B timecode signal has never been detected by the Time Processing Board; or ifthe GTS is a pulse input, that no pulses have been received.

• If Year is 0, then Major Time elements have not been loaded; this operatorinterface 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.

• If the GTS is a pulse input (1 PPM or 1 PPH), the current pulse correction in useis displayed. This is less than or equal to ±30 seconds for 1 PPM, or ±30minutes for 1 PPH. It shows N/A for timecode GTSs, 1 PPS, or FLYWHEELmodes. The Time Processing Board tracks 1 PPS inputs directly.

• The next five lines of the output reflect information in F:\TIMESYNC.DAT.

• At the bottom of the display is a list of all available Stagelink Time Masters (onthis operator interface Stagelink), their addresses, their status, and which is theselected Stagelink Timemaster used by all nodes on this Stagelink.

GEH-6126 Chapter 8 Time Sync • 291

Note In a normal, functioning system, all status digits displayed for each availableStagelink Timemaster should be identical. If not, then verify thatF:\TIMESYNC.DAT in each operator interface has the same information for thefollowing parameters:

TIME_SOURCE [LOCAL | UTC]

MARKV_TIME [LOCAL | UTC]

I_TIME [LOCAL | UTC]

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: 1 ==> Stagelink Timemaster is tracking the GTS.

Bit 0: 0 ==> Stagelink Timemaster is flywheeling.

Bit 1: Reserved. Normally has a value of 1.

Bits 2-7: Reserved. Normally has a value of 0.

Bit 8: 1 ==> GTS is UTC based

Bit 8: 0 ==> GTS is LOCAL.

Bit 9: 1 ==> <I> ( IDP ) / <G> ( GDP ) time is UTC based.

Bit 9: 0 ==> <I> ( IDP ) / <G> ( GDP ) time is LOCAL.

Bit 10: 1 ==> Mark V’s time is UTC based.

Bit 10: 0 ==> Mark V’s time is LOCAL.

Bits 11-12: Reserved. Normally has a value of 1.

Bits 13-15: Reserved. Normally has a value of 0.

Reserved bit definitions are subject to change.

Other Timesync Diagnostic CapabilitiesEach operator interface with a Time Processing Board installed, maintains a tracebuffer in memory. This trace buffer contains recordings of timesync protocolmessages transmitted or received from the Stagelink. The information in these tracebuffers can show the current time error in each time slave.

292 • Chapter 8 Time Sync GEH-6126

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

The timesync_trace parameter must be in lowercase letters.

Now this information is in the file TIMESYNC.OUT. The timesync protocol tracesfor Message Type: 4 (Time Diagnostic) contain error corrections between theStagelink Time Master and the time slave.

Other message type dumps are used for development purposes only, and are notdiscussed here.

A portion of a sample output from the timesync_trace buffer is shown below:

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, Doing LOCAL TIMESET Function. Old Time: 22-MAY-1997 18:59:22.223 New Time: 22-MAY-1997 18:59:22.360

GEH-6126 Chapter 8 Time Sync • 293

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)

294 • Chapter 8 Time Sync GEH-6126

Sample Timesync ConfigurationsThis chapter shows three examples of possible Turbine Control TimeSynchronization setups.

Example 1

Using a Single Operator Interface as the Global Time SourceThis example uses a single operator interface as the GTS for the entire plant, usingthe low-drift capabilities of the Time Processing Board. The figure below shows atypical layout.

Follow the steps below for setup:

If multiple operator interfaces exist, install the Time Processing Board into theoperator interface containing the lowest Stagelink address. This interface is referredto as the Primary Operator Interface in this example.

If redundant Time Processing Boards exist, install the board(s) in the operatorinterface(s) with a higher Stagelink address(es) than the Primary Operator Interfacedescribed in step 1. These operator interfaces are referred to as Secondary OperatorInterfaces in this example.

Connect RG-58 cable from the TIMECODE OUTPUT BNC connector of the PrimaryOperator Interface to the TIMECODE INPUT BNC connectors on each SecondaryOperator Interface. Use T-connectors to parallel the signal from computer tocomputer. In addition, parallel this cable to any DCS equipment which are to act astime slaves to the Primary Operator Interface.

Optionally, the 1 PPS output can be connected to DCS equipment that are to act astime slaves to the Primary Operator Interface.

The Primary Operator Interface may have F:\TIMESYNC.DAT configured with thefollowing:

TIMESYNC BC620AT MODE FLYWHEEL

TIME_SOURCE LOCAL

MARKV_TIME LOCAL

I_TIME LOCAL

TIME_LOAD LOCAL

LOCAL_TIMESET ENABLED

The F:\TIMESYNC.DAT files in each of the Secondary Operator Interfaces may beconfigured with the following:

TIMESYNC BC620AT MODE IRIG-B

TIME_SOURCE LOCAL

MARKV_TIME LOCAL

I_TIME LOCAL

TIME_LOAD LOCAL

LOCAL_TIMESET ENABLED

GEH-6126 Chapter 8 Time Sync • 295

If TIMESET capability is wanted in any operator interface without a TimeProcessing Board installed, configure F:\TIMESYNC.DAT in those computers withLOCAL_TIMESET ENABLED. (Other parameters are not required.)

TURBINE CON

STAGELINK (ARCNET)

(RG-62 COAX CABLE)

PRIMARY

OP INTERFACE

OP INTERFACE

OP INTERFACE

TIMECODE

# 1

OUT BNC

SECONDARY

SECONDARY

IRIG-B TIMECODETO DCS EQUIPMENT

RG-58COAXCABLE

1PPSOUT BNC

TIMECODEIN BNC

TIMECODEIN BNC

*

*

*

* Optional

1 PPSTO

DCS EQUIPMENT*

TERMINATIONRESISTOR

TERMINATIONRESISTOR

TURBINE CON

# 2

TURBINE CON

# 3

Typical Layout for FLYWHEELING Timesync Mode

Example 2

Using IRIG-B Timecode as the GTS with Multiple Operator Interface StagelinkTimemasters and Multiple Stagelinks

This example uses a single box as the GTS for the entire plant, possibly a satellitereceiver that generates an IRIG-B timecode signal. The figure below shows a typicallayout.

Note For redundancy requirements, no more than two-operator interface computersper Stagelink need to have Time Processing Boards installed.

296 • Chapter 8 Time Sync GEH-6126

Follow the steps below for setup:

Install a Time Processing Board in each operator interface to be used as an availableStagelink Time Master.

Connect RG-58 cable from the source of the IRIG-B timecode signal to each TimeProcessing Board, using the TIMECODE INPUT BNC connector. Use T-connectorsto parallel the signal to each board.

Continue the RG-58 cabling to any other piece of equipment in the plant that is to actas a time slave.

The following is a typical F:\TIMESYNC.DAT configuration for each of the operatorinterfaces that have Time Processing Boards installed:

TIMESYNC BC620AT MODE IRIG-B

TIME_SOURCE LOCAL

MARKV_TIME LOCAL

I_TIME LOCAL

TIME_LOAD LOCAL

LOCAL_TIMESET ENABLED

Note If the timebase of the IRIG-B timecode signal is UTC, change theTIME_SOURCE LOCAL line above to TIME_SOURCE UTC.

If TIMESET capability is wanted in any operator interface without a TimeProcessing Board installed, configure F:\TIMESYNC.DAT in those computers withLOCAL_TIMESET ENABLED. (Other parameters are not required.)

GEH-6126 Chapter 8 Time Sync • 297

TURBINE CON

# 1

STAGELINK (ARCNET)

(RG-62 COAX CABLE)TIMECODEIN BNC

IRIG-B TIMECODETO OTHER PLANT

RG-58COAXCABLE

TIMECODEIN BNC

TERMINATIONRESISTOR

# 1OP INTERFACE

IN BNCTIMECODE

IN BNCTIMECODE

EQUIPMENT

IRIG-B TIMECODEGNAL FROM SATELLITE

RECEIVER OROTHER DEVICE

STAGELINK (ARCNET)

(RG-62 COAX CABLE)

TERMINATIONRESISTOR

TERMINATIONRESISTOR

TERMINATIONRESISTOR

# 2OP INTERFACE

# 3OP INTERFACE

# 4OP INTERFACE

TURBINE CON

# 2

TURBINE CON

# 3

Typical Layout for External IRIG-B GTS, using redundancy and multiple StagelinkNetworks

298 • Chapter 8 Time Sync GEH-6126

Example 3Using Pulse Inputs as the GTS with Multiple Operator Interface StagelinkTimemasters and Multiple Stagelinks

This example uses a single box as the GTS for the entire plant, possibly a satellitereceiver that generates one pulse per minute (or hour) as a time reference. The figurebelow shows a typical layout.

Note For redundancy requirements, no more than two-operator interface computersper 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 availableStagelink Time Master.

Connect RG-58 cable from the source of the pulse input signals to each TimeProcessing Board, using the EVENT INPUT BNC connector. Use T-connectors toparallel the signal to each board.

Continue the RG-58 cabling to any other piece of equipment in the plant that is to actas a time slave.

The following is a typical F:\TIMESYNC.DAT configuration for each of the operatorinterfaces that have Time Processing Boards installed:

TIMESYNC BC620AT MODE 1PPM

TIME_SOURCE LOCAL

MARKV_TIME LOCAL

I_TIME LOCAL

TIME_LOAD LOCAL

LOCAL_TIMESET ENABLED

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 TimeProcessing Board installed, configure F:\TIMESYNC.DAT in those computers withLOCALTIMESET 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 andboth the 1 PPS Input and Event Input signals. Therefore any interface to these inputsmust 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 whenthe reference pulse is active. Pulse input references must be stable, therefore only usestable pulse references. For example, 1 PPM references pulses should be as close to60.00000 seconds apart as possible. Otherwise, Turbine Control timesync losesaccuracy.

The use of electro-mechanical relays for pulse inputs is not recommended. The useof open collector circuits or solid state relays is acceptable. GE does not recommendusing software operating systems in the DCS to generate the reference pulses.

GEH-6126 Chapter 8 Time Sync • 299

Pulse input references are at logic 0 most of the time. Therefore, the Time ProcessingBoard’s BNC connector records a false pulse input when the reference cable isdisconnected from the Time Processing Board. The board senses a positive edgecaused by the internal 4.7 kΩ pull-up resistor. The card then sends invalid time tothe Turbine Control panels until the next true reference pulse is signaled. GErecommends restarting the operator interface software after the reference cables arereconnected.

TURBINE CON

# 1

STAGELINK

(RG-62 COAX CABLE)

BNC

PULSE CODESTO OTHER PLANT

RG-58COAXCABLE

TERMINATIONRESISTOR

EQUIPMENT

1 PULSE PER MINUTEOR 1 PULSE PER HOURSATELLITE RECEIVER

OR OTHER DEVICE

STAGELINK (ARCNET)

(RG-62 COAX CABLE)

EVENT IN

EVENT INBNC

EVENT INBNC

EVENT INBNC

TERMINATIONRESISTOR

TERMINATIONRESISTOR

TERMINATIONRESISTOR

OP INTERFACE# 1

OP INTERFACE# 2

OP INTERFACE# 3

OP INTERFACE# 4

TURBINE CON

# 2

TURBINE CON # 3

Typical Layout for External 1 PPM or 1 PPH GTS, with redundant StagelinkTimemasters and multiple Stagelink Networks

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 calledBC620.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 calledG:\EXEC\TEST_620.EXE. This program provides bc620AT/bc627AT testingcapability while running under the Windows NT operating system.

This program can be used to verify that the GTS interface (pulse or timecode) ispresent and operational. This section describes how to use this program.

300 • Chapter 8 Time Sync GEH-6126

!Warning

This program can interfere with the normal timesyncoperation of the operator interface. This is especiallytrue for pulse input GTSs. This program should onlybe run when the TCI system service is not running.The ARCNET® device driver must be running inorder to use this test program. Restart the TCI systemservice after running this test program.

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. Alsolisted 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" onpage 300.

To test the bc620 event recording registers and/or to test 1PPS, 1PPM or 1PPHGTSs, 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 TCISystem Service.

-----------------------------------------------------------------------------------------------------

bc620AT Time & Frequency Processor Test Program (NT Version)1. Read Time2. Read Event Time (Pos. Edge) I. Read Event Time (Neg. Edge)3. Request bc620AT Programmable Data4. Request Model Number & Firmware Version5. Request D/A Value6. Request RTC Time7. Select Operational Mode8. Select Time Code Format and Type9. Program Control Register (CRO)A. Program Heartbeats (82C54)B. Preset D/AC. Send Path ByteD. Send Command ** bc627AT COMMANDS ONLY **E. Load Major Time Registers J. Request YearF. Load RTC Time Registers K. Request GPS Leap SecondsG. Load Strobe Time L. Load GPS Leap SecondsH. Program Propagation Delay Offset M. Load GPS Time OffsetEnter Selection: x. Exit-------------------------------------------------------------------------------------Main bc620AT/bc627AT Test Program Menu

Test #1This test will validate the existence of a timecode GTS (if used) and the timerecording 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 bc620time 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 theWindows 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.

GEH-6126 Chapter 8 Time Sync • 301

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)

------------------------------------------------------------------

Sample Read Time Register Output

Test #2This test is used to validate the bc620’s event recorder registers, and can be used tovalidate 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 thevalue of CR0. See the figure below for an example.

Select option "2" at the program menu. This will start event register recording asshown in the figure below. (This example was created by connecting the "1PPSOutput" 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 isremoved, a new event time should be shown. All of the bc620 event registers areBCD 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/OPort Base Address in the Windows NT registry is wrong. If a timecode GTS isattached to the "Timecode In" BNC, each line should show "Tracking" status.Otherwise, "Flywheeling" status will be shown.

302 • Chapter 8 Time Sync GEH-6126

To test 1PPS, 1PPM or 1PPH pulse input GTSs, attach the signal to the "EventInput" BNC.

Note For 1PPS, this is a temporary connection. 1PPS GTSs are normally connectedto 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 BCDregisters. 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 PortBase Address in the Windows NT registry is wrong. If a timecode GTS is attachedto the "Timecode In" BNC, each line should show "Tracking" status. Otherwise,"Flywheeling" status will be shown.

GEH-6126 Chapter 8 Time Sync • 303

----------------------------------------------------------------------- 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)------------------------------------------------------------------

Sample Read Event Register Output

Test #3This test will validate the existence of a 1PPS GTS and the time recording registersof the bc620AT.Follow these steps to setup the test:First, select "7" at the program’s menu to select the operational mode of thebc620AT.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 terminatethe test.The program will read the bc620 time registers as rapidly as possible. All of thebc620 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 aredefective 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 eachline should show "Tracking" status. Otherwise, each line will show "Flywheeling"status.

304 • Chapter 8 Time Sync GEH-6126

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: 01 41 32 17

Press any key to continue:----------------------------------------------------------------------

Programming bc620AT to use 1PPS GTS

Test #4 and Test #5Tests #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 theexample 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 theexample below should be displayed.If either test fails, the bc620AT is probably defective, or the I/O Port Base Addressin the Windows NT Registry is wrong.

GEH-6126 Chapter 8 Time Sync • 305

------------------------------------------------------------- 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: 01 4F 33 17 REPLY: 01 6F 33 30 42 4D 42 30 31 2B 30 30 2B 30 30 30 REPLY: 30 30 30 30 30 30 30 30 30 30 30 30 30 17

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: 4

REQUEST: 01 4F 34 17 REPLY: 01 6F 34 62 63 36 32 30 41 54 20 39 35 30 31 31 REPLY: 35 35 17

Model: bc620AT 9501155

Press any key to continue:------------------------------------------------------------------

Sample Request Model Number & Firmware Version Output

306 • Chapter 8 Time Sync GEH-6126

Notes

GEH-6126 Glossary of Terms • 307

Glossary of Terms

2137 A 1kHz modulated signal. Frame rate is 1 code per second. This is a time-of-day 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 at2.5 Mbits/s.

BCD Binary Coded Decimal.

CF Control Functions.

Daylight Savings Time (DST) Time change observed in parts of the world toextend the number of daylight hours.

DCS Distributed Control Systems

EDT Eastern Daylight Time. Reference to Daylight Savings Time in the EasternUnited States.

Epoch A reference event. In timing applications, epoch often refers to a one pulseper second event.

Flywheel In the timekeeping vernacular to ’flywheel’ means to maintain time orfrequency or both after the input reference is removed or lost.

GDP Gateway Data Processor, also referred to as <G>. GSM Gateway computerinterface for the Mark V Turbine Control System using Ethernet in place of theStagelink. Please see IDP.

GMT Greenwich Mean Time.

308 • Glossary of Terms GEH-6126

GPS Global Positioning System. The fleet of GPS vehicles is used worldwide fornavigational purposes by aircraft and ships for position and velocity measurements. Inaddition, 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 theaccumulation of leap seconds. Leap seconds are typically added or subtracted on June30th and December 31st of each year as needed to correct UTC.

GSM GE Drive Systems Standard Message

GTS Global Time Source. This is the source of time reference used forsynchronization of time for all Mark Vs and DCS subsystems.

I/O Input/output. Interfaces that allow the flow of data into and out of a device.

IDP Interface Data Processor, also referred to as <I>. One of the Mark V TurbineControl System’s primary operator interface. Consists of a computer interface withGE’s version of ARCNET called the Stagelink.

IRIG - Inter-Range Instrumentation Group. This group defines a family of timecodesignals (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 persecond. Resolution: 0.1 ms.

IRIG-B A 1kHz modulated or dc level shifted signal. Frame rate is 1 code persecond. Resolution: 1 ms.

IRQ Interrupt Request

Local Time A time reference commonly used in the geographic locale of theequipment. Local time is subject to jerks in time caused by jumping the timereference forward in the Spring for Daylight Savings Time, and jumping backward inthe 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.

GEH-6126 Glossary of Terms • 309

NASA-36 A 1KHz modulated or dc level shifted signal. Frame rate is 1 code persecond. 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 timereference. A typical rate is 1 Pulse Per Hour.

PPM Pulse Per Minute. A GTS using periodic pulses to mark an epoch as a timereference. A typical rate is 1 Pulse Per Minute.

PPS Pulse Per Second. A GTS using periodic pulses to mark an epoch as a timereference. 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 implyany particular accuracy.

Timesync The act of locking a clock to a time reference. This action implies acontinuous operation used to minimize loss of accuracy of the clock beingsynchronized referenced to the global time source.

UTC Universal Time Coordinated. This is the time reference used at the zeromeridian. Also known as GMT.

XR3 A 250 Hz modulated signal. Frame rate is 1 code per second. This is a time-of-day reference. Resolution: 4 ms.

310 • Glossary of Terms GEH-6126

Notes

GEH-6126 Appendix A • 311

Appendix A

IRIG NomenclatureIRIG Time Codes have alphabetical as well as numerical designations. Thenomenclature is defined as follows:

Rate Designation

A: 1000 pps

B: 100 pps

D: 1 ppm

E: 10 pps

G: 10000 pps

H: 1 pps

Form Designation

0: Pulse, width-coded

1: Sine wave, amplitude-modulated

Carrier/Resolution

0: No carrier/index count interval

1: 100 Hz/10 ms

2: 1000 Hz/1 ms

3: 10000 Hz/0.1 ms

4: 100000 Hz/0.01 ms

Coded Expressions

0: BCD, CF, SBS

1: BCD, CF

2: BCD

3: BCD, SBS

312 • Appendix A GEH-6126

IRIG Codes

The following is a list of recognized standard IRIG codes:

* Format A: A000, A003, A130, A133

* Format B: B000, B003, B120, B123

Format D: D001, D002, D111, D112, D121, D122

Format E: E001, E002, E111, E112, E121, E122

Format G: G001, G002, G141, G142

Format H: H001, H002, H111, H112, H121, H122

* Supported by Turbine Control Time Synchronization

*(,QGXVWULDO&RQWURO6\VWHPV

*HQHUDO(OHFWULF&RPSDQ\5RDQRNH%OYG6DOHP9$86$