Geh 6403 Control System Toolbox For A MK6 Turbine Controller

GE Energy
Control System Toolbox

For a Mark VI Turbine Controller
GEH-6403L
g
These instructions do not purport to cover all details or variations in equipment, nor to
provide for every possible contingency to be met during installation, operation, and
maintenance. The information is supplied for informational purposes only, and GE makes
no warranty as to the accuracy of the information included herein. Changes,
modifications and/or improvements to equipment and specifications are made
periodically and these changes may or may not be reflected herein. It is understood that
GE may make changes, modifications, or improvements to the equipment referenced
herein or to the document itself at any time. This document is intended for trained
personnel familiar with the GE products referenced herein.
GE may have patents or pending patent applications covering subject matter in this
document. The furnishing of this document does not provide any license whatsoever to
any of these patents.
This document contains proprietary information of General Electric Company, USA and
is furnished to its customer solely to assist that customer in the installation, testing,
operation, and/or maintenance of the equipment described. This document shall not be
reproduced in whole or in part nor shall its contents be disclosed to any third party
without the written approval of GE Energy.
GE provides the following document and the information included therein as is and
without warranty of any kind, expressed or implied, including but not limited to any
implied statutory warranty of merchantability or fitness for particular purpose.
If further assistance or technical information is desired, contact the nearest GE Sales or

Service Office, or an authorized GE Sales Representative.
2000 - 2007 General Electric Company, USA. All rights reserved.
CompactFlash is a registered trademark of SanDisk Corporation.

* Trademark of General Electric Company
IBM is a registered trademark of International Business Machines Corporation.
Intel is a registered trademark of Intel Corporation.
Pentium is a registered trademark of Intel Corporation.
Series 90 is a trademark of GE Fanuc Automation North America, Inc.
Windows and Windows NT are registered trademarks of Microsoft Corporation.
g
To:
Reader Comments GE Energy

Documentation Design, Rm. 293
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Fax: 1-540-387-8651
(GE Internal DC 8-278-8651)
We welcome comments and suggestions to make this publication more useful.

Your Name Todays Date If needed, how can we contact you?
Fax No.
Your Companys Name and Address Job Site
Phone No.
GE Requisition No.
E-mail
Your Job Function / How You Use This Publication Publication No.
Address
Publication Issue/Revision Date
General Rating
Excellent Good Fair Poor Additional Comments
Contents { { { { ____________________________________________________________
Organization { { { { ____________________________________________________________
Technical Accuracy { { { { ____________________________________________________________
Clarity { { { { ____________________________________________________________
Completeness { { { { ____________________________________________________________
Drawings / Figures { { { { ____________________________________________________________
Tables { { { { ____________________________________________________________
Referencing { { { { ____________________________________________________________
Readability { { { { ____________________________________________________________
Specific Suggestions (Corrections, information that could be expanded on, and such.)
Page No. Comments
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
Other Comments (What you like, what could be added, how to improve, and such.) ________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)
{ Superior { Comparable { Inferior { Do not know Comment ____________________________________________
Detach and fax or mail to the address noted above.

........................................................................ Fold here and close with staple or tape ..........................................................................................
____________________________ Place
stamp
____________________________ here.
____________________________
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
.......................................................................................... Fold here first ........................................................................................................

Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not

strictly observed, could result in personal injury or death.
Indicates a procedure, condition, or statement that, if not

strictly observed, could result in damage to or destruction of
equipment.
Indicates a procedure, condition, or statement that should be

strictly followed in order to optimize these applications.
Note Indicates an essential or important procedure, condition, or statement.

This equipment contains a potential hazard of electric shock
or burn. Only personnel who are adequately trained and
thoroughly familiar with the equipment and the instructions
should install, operate, or maintain this equipment.
Isolation of test equipment from the equipment under test

presents potential electrical hazards. If the test equipment
cannot be grounded to the equipment under test, the test
equipments case must be shielded to prevent contact by
personnel.
To minimize hazard of electrical shock or burn, approved

grounding practices and procedures must be strictly followed.
To prevent personal injury or equipment damage caused by

equipment malfunction, only adequately trained personnel
should modify any programmable machine.
Contents
Chapter 1 Overview 1-1
Introduction ............................................................................................................................1-1
Before Beginning....................................................................................................................1-2
How To Use This Manual ........................................................................................1-2
Conventions..............................................................................................................1-3
Chapter 2 Using the Toolbox 2-1
Introduction ............................................................................................................................2-1
Computer Requirements .........................................................................................................2-2
Installation ..............................................................................................................................2-2
Upgrade from Previous Releases ............................................................................................2-3
Maintain Multiple Releases of Toolbox ...................................................................2-3
Migrate Files to Release 9 ........................................................................................2-4
Use Controller Files..................................................................................................2-4
Start the Toolbox ....................................................................................................................2-5
Work Area ................................................................................................................2-5
Access Online Help ................................................................................................................2-7
Privilege/Password .................................................................................................................2-8
Privilege Level Functions.........................................................................................2-8
Change Password ...................................................................................................2-10
Toolbox Options ...................................................................................................................2-12
General ...................................................................................................................2-13
Startup ....................................................................................................................2-14
Database .................................................................................................................2-15
Libraries .................................................................................................................2-16
Print ........................................................................................................................2-17
Controller ...............................................................................................................2-18
Block Diagram .......................................................................................................2-19
Accuwave Power Conversion.................................................................................2-20
AVDV Series Drive................................................................................................2-21
Toshiba GE System Drive ......................................................................................2-22
EX2100...................................................................................................................2-23
Static Starter Drive .................................................................................................2-24
OC2000 ..................................................................................................................2-25
AcDcEx2000 ..........................................................................................................2-26
Trend Recorder.......................................................................................................2-27
Innovation Series Drive..........................................................................................2-28
Connect the Toolbox.............................................................................................................2-29
Innovation Series/Mark VI Controller....................................................................2-29
OC2000 ..................................................................................................................2-29
AcDcEx2000 ..........................................................................................................2-30
Innovation Series Drive..........................................................................................2-31
AccuWave Power Conversion Device....................................................................2-32
Toshiba GE System Drive ......................................................................................2-33
Remote Connection ................................................................................................2-34
Chapter 3 Basic Configuration 3-1
Introduction ............................................................................................................................3-1
Create a Controller..................................................................................................................3-2
General Tab ..............................................................................................................3-3
GEH-6403L Toolbox for a Mark VI Turbine Controller Contents i

Memory Tab ............................................................................................................ 3-4
NTP Tab .................................................................................................................. 3-5
Note Tab .................................................................................................................. 3-6
Alarm Scanner Tab.................................................................................................. 3-7
Triple Modular Redundancy (TMR) Tab ................................................................ 3-9
Hold List Scanner Tab............................................................................................3-10
Customer InformationTab ......................................................................................3-11
Ethernet Setup Tab .................................................................................................3-12
Working with Files and Menus.............................................................................................3-13
Import Standard Files .............................................................................................3-15
Save Files................................................................................................................3-16
Revision Tracking...................................................................................................3-16
Open and Close Files..............................................................................................3-17
Export Configuration Files .....................................................................................3-17
Work with Project Files..........................................................................................3-19
Locked Items ..........................................................................................................3-21
Batch Operations ....................................................................................................3-24
Menu Commands....................................................................................................3-25
I/O Checkout.........................................................................................................................3-33
I/O Checkout Status................................................................................................3-35
Filtering ..................................................................................................................3-36
Blockware Concepts .............................................................................................................3-37
Blocks and Block Pins............................................................................................3-38
Macros, Macro Definitions, and Macro Pins ..........................................................3-38
Tasks and Scheduling .............................................................................................3-39
Modules, Module Definitions, and Module Pins ....................................................3-43
Functions ................................................................................................................3-44
Libraries..................................................................................................................3-44
Configuration ........................................................................................................................3-45
Create/Delete Blockware ........................................................................................3-45
Functions and Software Libraries ...........................................................................3-46
Type Definitions .....................................................................................................3-48
Scale Definitions.....................................................................................................3-51
Signal Definitions ...................................................................................................3-53
Table Definitions ....................................................................................................3-58
Import Files ............................................................................................................3-59
Edit Table Definition ..............................................................................................3-60
Module Definitions and Modules ...........................................................................3-63
Module Pins............................................................................................................3-67
Macro Definitions...................................................................................................3-71
Macro Pins..............................................................................................................3-73
Tasks.......................................................................................................................3-75
Blocks and Macros .................................................................................................3-78
Block Flow Diagram ..............................................................................................3-85
Instance Module and Macro ...................................................................................3-86
Alarm Tab...............................................................................................................3-87
Limits Tab ..............................................................................................................3-88
Device Menu Commands......................................................................................................3-91
Database Commands ..............................................................................................3-91
Validate ..................................................................................................................3-92
Build Pcode and Symbols.......................................................................................3-92
Software Setup......................................................................................................................3-94
Controller Setup......................................................................................................3-94
Serial Loader ..........................................................................................................3-95
Initialize Flash ........................................................................................................3-96
Compact Flash Setup ..............................................................................................3-97
ii Contents GEH-6403L Toolbox for a Mark VI Turbine Controller

Configure TCP/IP...................................................................................................3-98
Product Code (Runtime) Software .........................................................................3-99
Application Code..................................................................................................3-100
Software Modifications.......................................................................................................3-101
Modify Application Code.....................................................................................3-101
Upload Mark VI File ............................................................................................3-105
Upgrade Product Code (Runtime) Software.........................................................3-105
Use Totalizers.......................................................................................................3-108
Restore Application Code.....................................................................................3-109
Replicate Device...................................................................................................3-110
Monitor ...............................................................................................................................3-111
Going Online/Offline............................................................................................3-111
Watch Windows ...................................................................................................3-114
Monitor Controller State.......................................................................................3-117
Control Constant and Tuning Variable View .....................................................................3-118
Work Area ............................................................................................................3-118
File Compare View.............................................................................................................3-122
Application Documentation................................................................................................3-125
Print Options.........................................................................................................3-125
Print Preview ........................................................................................................3-130
Block Diagram .....................................................................................................3-131
Reports .................................................................................................................3-133
Application Diagnostics......................................................................................................3-140
Types of Application Diagnostics ........................................................................3-140
Generating Application Diagnostics.....................................................................3-142
Control Blocks that Generate Diagnostics............................................................3-144
Runtime Data Flow ..............................................................................................3-146
Diagnostic Data ....................................................................................................3-146
Dynamic Data Recorder (DDR) .........................................................................................3-148
Create and Delete DDR ........................................................................................3-148
Configure DDR ....................................................................................................3-149
Status Signals .......................................................................................................3-150
Import and Export DDR .......................................................................................3-151
Add Signals ..........................................................................................................3-152
Update DDR .........................................................................................................3-152
Chapter 4 Finder 4-1
Introduction ............................................................................................................................4-1
Using the Finder .....................................................................................................................4-2
Finder .......................................................................................................................4-2
Target Finds..............................................................................................................4-3
Chapter 5 Batch Operations 5-1
Introduction ............................................................................................................................5-1
Batch Operations File .............................................................................................................5-2
Batch Window..........................................................................................................5-3
Configure a Batch Operation....................................................................................5-4
Run a Batch Operations File.....................................................................................5-5
System Make Wizard ...............................................................................................5-5
Open and Save Batch Operations File ......................................................................5-6
Import and Export Batch Operations File.................................................................5-6
Chapter 6 File Checkin/Checkout 6-1
Introduction ............................................................................................................................6-1
Initialization............................................................................................................................6-1

Chapter 7 Configuring System Information 7-1
Introduction............................................................................................................................ 7-1
Working with System Information Files................................................................................ 7-2
Concepts ................................................................................................................................ 7-2
Scale Definitions...................................................................................................... 7-2
Type Definitions ...................................................................................................... 7-2
Measurement System............................................................................................... 7-3
System Overview..................................................................................................... 7-3
Configuration ......................................................................................................................... 7-3
Create/Modify System Information ......................................................................... 7-3
Insert/Modify Scale Definitions .............................................................................. 7-5
Resource Type Definitions ...................................................................................... 7-6
Enumerations........................................................................................................... 7-7
Alarm Classes .......................................................................................................... 7-8
System Overview..................................................................................................... 7-9
Put Data into Database ...........................................................................................7-11
Chapter 8 Graphics Window 8-1
Introduction............................................................................................................................ 8-1
Graphics Window Objects ..................................................................................................... 8-2
Create Graphics Window......................................................................................... 8-3
Menu Bar ................................................................................................................. 8-3
Drag-and-Drop Data ................................................................................................ 8-8
Properties Toolbar ................................................................................................... 8-9
View Signal Summary ........................................................................................................... 8-9
Settings .................................................................................................................................8-10
Frame Size and Options..........................................................................................8-10
Pen Color and Pen Width .......................................................................................8-10
Brush Color and Use Brush ....................................................................................8-11
Text Font ................................................................................................................8-11
Select Controls........................................................................................................8-12
Draw Commands ..................................................................................................................8-14
Insert Object ...........................................................................................................8-16
Insert Picture...........................................................................................................8-16
Animate Objects ...................................................................................................................8-17
Value and Enable Return ........................................................................................8-18
Numeric Animation ................................................................................................8-21
Bar Graph ...............................................................................................................8-22
Trend ......................................................................................................................8-23
Text.........................................................................................................................8-24
Color.......................................................................................................................8-25
Property ..................................................................................................................8-26
Input Fields ...........................................................................................................................8-27
Numeric ..................................................................................................................8-27
Setpoint...................................................................................................................8-28
Initial Value ............................................................................................................8-28
Text.........................................................................................................................8-29
Toggle Command ...................................................................................................8-29
Event Input .............................................................................................................8-30
Hyperlinks ..............................................................................................................8-31
Using Graphics Window Objects..........................................................................................8-32
Signal Substitution..................................................................................................8-37
Forced Signals ........................................................................................................8-38
String Substitutions.................................................................................................8-39
Graphics Windows for the Control Operator Interface (COI) ................................8-40

Chapter 9 Hardware and I/O 9-1
Introduction ............................................................................................................................9-1
I/O and Network Interface ......................................................................................................9-2
I/O Points..................................................................................................................9-2
Insert I/O and Network Interfaces ............................................................................9-3
Mark VI I/O ............................................................................................................................9-5
Racks ........................................................................................................................9-6
Simplex Rack in Outline and Summary View..........................................................9-9
TMR Rack in Outline and Summary View ............................................................9-10
I/O Boards ..............................................................................................................9-11
Configure Boards in Outline View.........................................................................9-13
Upgrade Boards......................................................................................................9-16
Compare I/O Board Commands .............................................................................9-16
Download Firmware...............................................................................................9-19
Compare Board Revisions......................................................................................9-20
Upload Configuration to File..................................................................................9-22
Compare Configuration to File...............................................................................9-22
VSVO Servo Board ................................................................................................9-23
VSCA Serial Interface Board .................................................................................9-27
Sequence of Events ................................................................................................9-31
EGD Interface.......................................................................................................................9-32
Edit EGD ................................................................................................................9-32
EGD Exchanges .....................................................................................................9-33
EGD Points.............................................................................................................9-36
Genius Networks ..................................................................................................................9-39
Genius Network Configuration ..............................................................................9-40
Genius Network View ............................................................................................9-41
Configure Genius LAN Board................................................................................9-43
Genius Blocks.........................................................................................................9-45
Field Control Station ..............................................................................................9-48
Field Control Module .............................................................................................9-51
Genius Block and Field Control Module Points.....................................................9-54
Third Party Operator Interfaces..............................................................................9-54
Monitor Genius.......................................................................................................9-55
Main Board ...........................................................................................................................9-60
Non-volatile Random-Access Memory ..................................................................9-60
NOVRAM Points ...................................................................................................9-63
Register Network ..................................................................................................................9-64
Ethernet SRTP........................................................................................................9-65
Serial/Ethernet Modbus ..........................................................................................9-68
Allen-Bradley Data Highway Plus (DH+)..........................................................9-70
Custom Register Network ......................................................................................9-72
Modify Page Settings .............................................................................................9-74
Modify Point Settings.............................................................................................9-75
Chapter 10 Configuring the Network Interface 10-1
Introduction ..........................................................................................................................10-1
Concepts ...............................................................................................................................10-2
Configuration........................................................................................................................10-3
Create Network Interface .......................................................................................10-3
Work with Network Interface Files ........................................................................10-5
Define Network Connection...................................................................................10-6
Insert/Define Signals ..............................................................................................10-8
Map Signals to a Network ......................................................................................10-8
Specify Signals Used by the Network Interface .....................................................10-9

Put Into Database/Get From Database..................................................................10-11
Profibus Interface .................................................................................................10-13
Chapter 11 Signals and the Database 11-1
Introduction...........................................................................................................................11-1
Signal Concepts ....................................................................................................................11-2
Drive Signals ..........................................................................................................11-2
Controller Signals ...................................................................................................11-2
Scale Definitions.....................................................................................................11-8
Signal Selector........................................................................................................11-9
SDB.....................................................................................................................................11-12
Put Into and Get From Database...........................................................................11-12
Chapter 12 Turbine Historian Configuration 12-1
Introduction...........................................................................................................................12-1
Working with Files and Menus.............................................................................................12-2
Menu Commands....................................................................................................12-2
Configuration ........................................................................................................................12-4
Create Configuration ..............................................................................................12-4
Templates..............................................................................................................................12-6
Collections..............................................................................................................12-8
Signals ..................................................................................................................12-10
Troubleshooting ..................................................................................................................12-15
Chapter 13 Setup for Turbine HMI Configuration 13-1
Introduction...........................................................................................................................13-1
Concepts ...............................................................................................................................13-2
Working With Files and Menus ............................................................................................13-3
Export as .prj and .tre files......................................................................................13-3
Device Menu Commands .......................................................................................13-4
Configuration ........................................................................................................................13-6
Modify HMI Configuration Properties ...................................................................13-7
Define a Network Connection ................................................................................13-8
Insert EGD Exchanges............................................................................................13-9
Signals ..................................................................................................................13-11
Chapter 14 Configuring the COI 14-1
Introduction...........................................................................................................................14-1
Concepts ...............................................................................................................................14-2
Working With Files and Menus ............................................................................................14-3
Configuration ........................................................................................................................14-6
Modify COI Configuration Properties....................................................................14-7
Define Network Connection ...................................................................................14-8
Insert/Define EGD Exchanges................................................................................14-9
Graphics Window Files ........................................................................................14-10
Glossary of Terms G-1
Index I-1

Chapter 1 Overview
Introduction
This manual describes GE Control System Solutions products and the Control
System Toolbox, which is micro-processor-based software used to configure and
maintain control equipment. The toolbox is a Windows-based application, which
runs on a Pentium 166 or higher, personal computer (pc). Major products
configured with the toolbox include:
Mark VI Turbine Controllers
Innovation Series drives
Innovation Series controllers
Operator Console 2000 (OC2000)
AC/DC2000 Digital Adjustable Speed Drive and EX2000 Digital Exciter
(AcDcEx2000)
EX2100 Excitation Control
Toshiba System drives
LS2100 Static Starter Control
Primary functions of the toolbox include:
The toolbox software configures Graphic-based editor for configuring application code
various control equipment.
Therefore, each product package Block, macro, and module library support
can consist of the toolbox, Live data block flow diagrams
product files for the controller or
drive, Trend Recorder, Data Online code change
Historian, and product files for Online Help files
the System Database (SDB). To
order the toolbox software and I/O configuration and monitoring
specific product support files, Signal management and signal trending
refer to the Product Catalog,
GEP-9145. Multi-user file management
Report generation
Batch operation mode
Target firmware upgrades
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 1 Overview 1-1

Before Beginning
Windows-based screen This manual describes the features of the toolbox and presents step-by-step
borders may vary in procedures for using the applications. It presumes that the user has already installed
appearance. Windows and possesses at least a medium-level knowledge of Windows. Hardware
requirements and instructions for installing the products are provided in Chapter 2.
How To Use This Manual

This manual provides the user with information on installing the toolbox and other
products used to configure control equipment. It also describes other features
provided in the toolbox software. This manual is organized as follows:
Chapter 1 Overview. This chapter defines available products and features of the
toolbox, as well as the contents of this manual and conventions used.
Chapter 2 Using the Toolbox. This chapter provides basic installation and startup
procedures for using the toolbox to configure a product.
Chapter 3 Basic Configuration. This chapter describes how to use the toolbox to
configure a controller.
Chapter 4 Finder. This chapter defines the features of the Finder, which searches
the device in the toolbox for items such as text and signals.
Chapter 5 Batch Operations. This chapter describes the Batch Operations mode.
This mode allows you to perform various operations on any number of different file
types at one time.
Chapter 6 File Checkin/Checkout. This chapter describes the Checkin/ Checkout
utility, which allows users to share files contained in a master file.
Chapter 7 System Information. This chapter describes the System Information
device which configures information global to a project, making it available to other
interfaces.
Chapter 8 Graphics Window. This chapter describes the Graphic Window, which
creates custom graphics interfaces for customer and process requirements.
Chapter 9 Hardware and I/O. This chapter describes the controller networks and
I/O used in the toolbox.
Chapter 10 Configuring the Network Interface. This chapter provides
instructions for using the toolbox to configure a Network Interface.
Chapter 11 Signals and the Database. This chapter defines signals and their
sources. It also defines the topological information in the database.
Chapter 12 Turbine Historian Configuration. This chapter describes the toolbox
interface for configuration and use of the Turbine Historian.
Chapter 13 Configuring the HMI Device. This chapter describes the HMI device
and its importation of data from the SDB.
Chapter 14 Configuring the Control Operator Interface (COI). This chapter
describes the Control Operator Interface and its importation of data from the SDB.
Glossary The Glossary provides definitions of terms and toolbox concepts.
Refer to the Table of Contents for the organization of these chapters.
1-2 Chapter 1 Overview GEH-6403L Toolbox for a Mark VI Turbine Controller

Conventions
The following conventional terms, text formats, and symbols are used throughout
this documentation for the toolbox.
Convention Meaning
Bold Indicates that the word is being defined.

Arial Indicates the file name or file path used.
Arial Bold Indicates the menu, the actual command or option selected from a menu, a
button, or title of a dialog box.
Italic Indicates new terms, margin notes, and the titles of figures, chapters, and other
books in the toolbox package.
UPPERCASE Indicates a directory, file name, or block name. Lowercase letters can be used
when typing names in a dialog box or at the command prompt, unless otherwise
indicated for a specific application or utility.
Monospace Represents examples of screen text or words and characters that are typed in a
text box or at the command prompt.
Indicates a procedure.
Indicates a procedure with only one step.
Indicates a list of related information, not procedural steps.
The following list presents some basic guidelines for working with menus:
When a menu is displayed, press the up/down arrow keys to highlight a command
name. Then press Enter to select the menu command. The menu can also be selected
by clicking with a cursor-positioning device (CPD), such as a mouse.
When a command ends in an ellipsis (), the application displays a dialog box that
asks the user to supply more information.
If a command turns a feature on and off, a checkmark (9) is displayed by the
command name when the feature is on.
When a command ends with an arrow ( ), the menu cascades to display more
command names.
If a command name is grayed out, it indicates that the command does not apply to
the current situation or there is another selection or action before selecting the
command.
Related Documents
GE provides system instruction documents for the different components of each
product. For questions or additional documentation, contact the nearest GE sales
office or authorized GE sales representative.
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 1 Overview 1-3

Notes
1-4 Chapter 1 Overview GEH-6403L Toolbox for a Mark VI Turbine Controller

Chapter 2 Using the Toolbox
Introduction
Setting options should be This chapter provides basic instructions for using the toolbox. It defines the toolbox
determined before starting a menu commands, including the Options menu, which has a Settings dialog tab for
configuration. each product. Methods of communication and toolbox connections are also
available.
Section Page
Computer Requirements...........................................................................................2-2
Installation ................................................................................................................2-2
Upgrade from Previous Releases..............................................................................2-3
Start the Toolbox ......................................................................................................2-5
Access Online Help ..................................................................................................2-7
Privilege/Password ...................................................................................................2-7
Toolbox Options.....................................................................................................2-12
Connect the Toolbox ..............................................................................................2-29
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 2 Using the Toolbox 2-1
Computer Requirements
The selected product combination and the pc topology configuration determines the
minimum requirements for CSS products:
300 MHz processor (Pentium II 500 or higher recommended)
A cursor-positioning device is Microsoft Windows
highly recommended.
95/98 (with 64 MB RAM), or
NT (with 64 MB RAM), or
2000 (with 128 MB RAM), or
XP (with 256 MB RAM)
SVGA display (800 x 600 x 256 color or gray scale)
Serial port for direct connection to a controller or drive
PCA198 (ARCNET) board (required if DLAN+ Devcom or Driver is
installed)
Network adapter (required for communication with the toolbox over a LAN)
Printer (with appropriate Windows driver installed)
Installation
Control System Solutions installs various products for control systems as selected in
the setup program. It is recommended that you exit all Windows programs before
beginning. A dialog box will prompt you for a license key, which can be found on
the actual CD. You must agree to the standard Software License Agreement for these
products.
To install the product
1. Place the Control System Solutions CD in the disk drive. The Setup program
executes automatically, or run the program setup.exe.
2. Follow the instructions from each screen. For more help, press F1.
Note If technical assistance is required beyond the instructions provided in the

documentation, contact the nearest GE Sales or Service Office or an authorized GE
Sales Representative.
2-2 Chapter 2 Using the Toolbox GEH-6403L Toolbox for a Mark VI Turbine Controller
Upgrade from Previous Releases
Note To upgrade to Version 9 from Version 4 or earlier, it is recommended that you
first uninstall any previous version of toolbox.
Maintain Multiple Releases of Toolbox

To maintain different releases of the toolbox on a single system, consider the
following:
Multiple versions of Release 5 or greater cannot be installed on one system.
The installation directory for Release 5 or greater of the toolbox is selected only
once, the first time that the Control System Solutions products are installed. The
default directory is C:\Program Files\GE Control System Solutions.
There is only one set of toolbox options settings for a given user on a given
computer. There are several toolbox options settings that may need to be unique
to a particular release of toolbox. For example, Release 4 of the toolbox would
probably need a different directory setting for standard library files than that of
Release 5 or 6. To use multiple releases, it is recommended to use different user
accounts for each release.
Opening a toolbox file from the Windows Explorer is not recommended if
multiple copies of toolbox are installed. When you open a file from the
Windows Explorer, the application that starts up depends on what is registered
for that file type. Releases of toolbox prior to Release 5 register each time they
execute. Release 5 or greater of toolbox, however, registers only at installation.
Modifying a toolbox file can make the file unusable to older releases of
toolbox. A warning dialog displays when the toolbox opens a file that was
written by a previous release. Do not save the file if it must be used by the
previous release.
Migrate Files to Release 9
Release 9 of the toolbox can read binary files written by Release 4 or later; therefore,
it is not necessary to export and re-import. However, Mark VI binary files written by
version 6 or earlier can be read-only, not modified. If they need to be modified, they
should be exported and re-imported with new libraries. When migrating to new
library files, project files may need to be modified with a text editor since the single
installation directory of the Control System Solutions products causes the standard
library path to change.
Use Controller Files

Note The following procedure is for a controller only.
To upgrade controller files to use new controller products and/or libraries, perform
the following steps:
1. Install the new controller product files.
2. Open the binary working file in toolbox.
3. From the File menu, select Export, then select All. This will export several tree
(.tre) files and one project (.prj) file.
4. Open the .prj file in a text editor and replace references to the old controller
product directories with references to the new product directories. For example,
replace references to C:\Program Files\GE Tools\Ucoc2000\stdtree with
C:\Program Files\GE Control System Solutions\Mark VI\stdtree.
5. Open the .prj file in toolbox. This imports the new product libraries and all other
.tre files required to create the controller. Save the new binary working file.
Start the Toolbox
The toolbox is started from the Windows NT or 95 Workstation.
To start the toolbox
1. Click Windows Start button, Programs, GE Control System
To create a device, refer to Solutions, and Control System Toolbox.
Chapter 3, the section Create
a Controller. 2. Click the toolbox icon. The toolbox Work Area displays. It is blank until a
device is created or opened.
Work Area
If more than controller is A controllers runtime action is configured using the toolbox. From the File menu,
open in the Work Area, each begin a New configuration or Open a previously saved configuration file. The
device will have a screen with toolbox Work Area is the main screen and contains the following:
an Outline View and
Work Area commands can be accessed through the menu bar or the toolbar,
Summary View.
depending on the selected product file.
Outline View displays the configuration in a hierarchy, with the drive/controller
name as the first item and other configuration items listed in levels below it.
Summary View displays information based on the item highlighted in the Outline
View. For example, in a controller configuration, the item taskname displays a block
diagram. In a drive configuration, the item Diagram displays drive block diagrams
(which can be configured from this view). The Tracking command controls what
The Tracking button displays in the Summary View. When Tracking is on, it tracks or displays the item
toggles the command on and selected (highlighted) in the Outline View. When Tracking is off, it freezes the
off. Summary View of the last selected item.
Detached Summary View is a separate window from the Work Area window and
Click to display the displays a copy of the Summary View. Option settings for the Detached
Detached Summary View. Summary View are separate from the Summary View (see the section, Toolbox
Options). This window can be sized, configured, and edited.
Note The following screen represents a basic toolbox Work Area format. Menu
commands, toolbar buttons, and Outline View items will vary with the product
installed.
Titlebar
Toolbar
Outline
View
Bookmark
Note
Summary
View
Log
View
Status Privilege Level

bar TMR Processor Connection
Edit Status
Connection/Revision
Idle Time
Double-click to edit the Note can be created when most items are inserted into the drive/controller. Select an
note. item, then select Edit and Insert First. If the item dialog box has a Note text box
and a note is entered, the Note icon displays beside the item in the Outline View
(as shown). Highlight an item containing a Note icon. The note displays in the
Summary View and on the Status Bar at the bottom of the Work Area.
Bookmark items display this Bookmark enables you to mark major items in the Outline View and then return
icon . to them easily using the Bookmarks command in the Edit menu. The Toggle
Bookmark command turns the icon on and off. The Goto Next Bookmark
command jumps to the next item marked with the .
Find the cause of an error by Log View displays configuration data for the highlighted item. This data compiles
double-clicking the error. during toolbox functions, such as file imports, validations, builds, or errors.
It can be toggled on and off Status Bar displays information across the bottom of the screen. When online, the
from the View menu. left side displays a description of various toolbox commands or notes entered. To
display a menu command description, click the menu command and move the
pointer over the command. The right side displays the following information for the
selected controller.
Status Field Displays Background
Privilege Level Privilege Level: 0 -
Privilege Level: 1 -
TMR Processor R Proc -
Connection S Proc -
T Proc -
Edit - white
READ yellow
Connection/Revision Offline gray
Equal green
Minor Diff yellow
Major Diff red
Idle time Idle white
Access Online Help

To obtain Help for the dialog Specific Help dialog boxes are available by pressing the F1 function key, when a
dialog box is displayed. Help can also be accessed using the following methods:
box on the screen, press F1 .
To obtain Help on . . . Do this . . .

Menu commands Highlight the command and press F1
Dialog boxes Press F1 when the dialog box displays on the screen
Block information Click the desired block with the right mouse button and select Item Help
Help contents Click the Help menu and select Contents
Help Click the Help menu and select Using Help
Specific word(s) Click the Help menu, select Contents, and click the tab Find, then enter the word(s)
to search
Privilege/Password
Refer to the next section to The privilege/password system assigns different levels of access to the devices.
change the password. Passwords can be established for the different privilege levels, so that each user can
access a device at the level necessary for the job that person is assigned.
To set a privilege level
From the Options menu, select Privilege. The Select Privilege Level
dialog box displays (refer to the next section, Privilege Level Functions).
Privilege Level Functions

A password can be assigned to each of the toolbox privilege levels. (Each successive
level allows all the functions of the previous level.)
Level Functions
0: Read Only View code
Use the Finder
Monitor live data
Trend (including saving trend definitions in .trn files and saving
collected data)
Change View attributes under Options\Settings
Print blockware code and reports
Change the password for level 0
1: Change Controller Online All functions allowed in Level 0, including change password
Signal Values levels in Levels 0 and 1
Force signals in a controller
Change the value of variables
2: Change Controller Code, All functions allowed in Level 0 and Level 1
Use all Macros
Make code changes
Download
Import/Export
Put in database and Get from database
Validate, build, save, backup, and pack signals
Change the password for Levels 0, 1, and 2
3: View all Macros View structure of macros
4: Change all Macros Delete macros
Modify macros
Change Password
To change the password
From the Options menu, select Passwords. The Changing Password
dialog box displays.
Select the privilege

leve to change.
Click OK.
The Changing
password for level
dialog box displays
(refer to next
section).
Enter the old

password.
Enter the new

password.
Re-enter the new

password for
verification.
Note If a password for a lower level is to be changed, the higher level overrides the
need for the old password and the Temporary Password button does not display.
When a password is created, it is associated with the binary file currently opened. To
remove a password for a particular level, type the old password, but do not enter
anything for the new password.
If a macro has access level 2, a user at privilege level 2 or above can use the macro
in code, but cannot see the blocks or pins that make up the macro, except for any
pins that the macro writer decided to make visible. These pins are displayed in the
Summary View of the block diagram, not in the Outline View. If a Visio diagram
or Help file is associated with the macro, they also can be seen.
If a macro has access level 3, a user at privilege level 2 or above can view the blocks
and pins that make up the macro. They can also select the code and copy it to their
own macro and modify.
If a macro has access level 4, a user at privilege level 2 or above can change or delete
the code.
If the old password is not known, a temporary password can be requested.
To request a temporary password
1. From the Changing Password dialog box, click the Request button. The
Temporary Password Request dialog box displays.
Click OK.
The
Password_ID
text displays.
2. Follow the appropriate instructions from the Password_ID text.
Toolbox Options
Option settings are saved in The toolbox working environment can be defined for each application. This section
the users Windows registry describes each tab that can be set to customize the toolbox device, database, block
when the toolbox is closed. diagrams, and such. These tabs are located in the Options menu under Settings.
To customize the toolbox settings
1. From the Options menu, select Settings. The Settings dialog box displays.
Click a tab to bring it to the front and select options.
2. Click OK to apply the changes and close the dialog box. Click Cancel to exit
and not change any settings.
General
The General tab applies to all devices.
Select a font for the Online View. Select a font Expert Mode allows
The default font is System Bold. for the Finder. extra data to be seen
Use compact export format

compresses the .tre files
produced by exporting. Less
hard disk space is used, and
it is easier to read and edit.
Save Bookmarks in files

saves bookmarks
between closing and
reopening files.
Auto-Save files every [ ]

minutes automatically saves
the files at the set increment.
The default is 15 minutes.
Compress files when Backup files before save

saving saves and stores creates a backup copy of
files in a compressed files before saving new
format to save disk space. information. This includes
.ucb, .dcb, .icb, and .ocb.
Startup
The Startup tab allows you to specify whether you want a file to automatically load
at startup.
Select one of the following

file options:
None dictates that no file

is automatically loaded on
toolbox startup.
Load last file loads the

files that were in use when
the toolbox was exited.
Select file allows you to

select the file that loads
when the toolbox starts.
Click Browse... to locate
the file.
Database
The Database tab defines the database and any required network information. It
applies to all devices as listed.
Select the SDB

database (SDB
is the system
database used
on a Windows
computer).
Note: USDB is
not used by
Static Starter
Control.
Enter the name

of the host to the
database. The
server name is
not case-
sensitive. If a
name server is
not available,
the IP address
must be used.
Enter the location of the SDB sub-directory on the server where the data
files are stored. The name must include the drive letter and at least one
sub-directory. The SDB cannot be located at the root of a drive. For a
USDB, the name is specified in the GEBHOST environment variable on
the LynxOS computer, for example, ustst_usdb.
Libraries
The Libraries tab defines the block and module libraries that are automatically
imported when a new controller (or OC2000) is created.
Note Existing controller libraries are referenced in the .prj file and override these
default libraries.
Select the product

library to define.
Default libraries
are listed. Use the
command buttons
to enter and edit
the library list.
Up and Down
rearranges the
list order.
Change inserts
the edited library
back into the list.
Add inserts the
new library from
the text box.
Remove deletes
the selected library
from the list.
Browse allows you

to search the directory
structure and select
an existing directory.
Print
The Print tab allows you to set print options for the current device. It applies to
controllers and drives as listed.
The Block Diagram Where Used Scope applies
only to controllers. Specify the scope of the signal
cross-referencing in the active block diagram.
Select the font for

the text displayed
immediately over
the blocks in the
diagram. The
default font is
Courier New.
Select the font for the

Signal Definitions and
Where Used Lists at
the end of each block
subsection. The default
font is Courier New.
Select the font for the

text at the top of each
new section and block
subsection. The
default font is Arial.
Select the font for all text
not listed above, including
block names and pins. The
font side directly affects the
number of blocks that
display on a page diagram.
The default font is Arial
Narrow.
Select this check box to

use old-style printing.
Controller
The Controller tab allows you to select the following options.

allow Boolean Engine
(BENG) blocks to be
edited using a Relay
Ladder Diagram (RLD).
If this box is not checked,
modify the block using
the Edit Block
Connections dialog box.
Select to enable
revision tracking, which
allows you to enter
information about a
change to a document
(file) when it is saved.
Select to display file

checkout status.
Refer to the Checkin-
Checkout utility.
Block Diagram
The Block Diagram tab allows you to specify how the block diagram displays in the
Summary View and Detached Summary View.

allow Boolean Engine
(BENG) blocks to be
edited using a Relay
Ladder Diagram (RLD).
If this box is not checked,
modify the block using
the Edit Block
Connections dialog box.
Select to enable
revision tracking, which
allows you to enter
information about a
change to a document
(file) when it is saved.
Select to display file

checkout status.
Refer to the Checkin-
Checkout utility.
Accuwave Power Conversion
The Accuwave Power Conversion tab allows you to select the following options:
Select the
communication port
from the drop-down
list.
Select this option to

program the keyboard
with an additional
language. This prompt
occurs when Keypad
Menus is selected
from Download to the
DSP in the Device
menu.
If you select this option and then go

online, the Device ID Verification
dialog box displays with additional
information for the toolbox and the
device. It is normally checked.
AVDV Series Drive
The AVDV Series Drive tab allows you to select the communication port.
Select a
communications
port from the
drop-down list.
TMdrive Series
The TMdrive Series tab allows you to select the following options.
Select a
communication
port from the
drop-down list.
EX2100
The EX2100 tab allows you to select the following options.
Select the
communication
port from the
drop-down list.
Select this check

box to be prompted
to add another
language to the
keyboard.
Select this check

box to enable
revision tracking,
which allows you to
enter information
about a document
when it is saved.
Static Starter Drive
The Static Starter Drive tab allows you to select the following options.
Select this check

box to be prompted
to add another
language to the
keyboard.
Select to enable
revision tracking,
which allows you
to enter
information about
a change to a
document (file)
when it is saved.
OC2000
The OC2000 tab allows you to select the following options.
Check to scale the

OC2000 operator
panel for the
Summary View and
Detached
Summary View.
Check to maintain
proportions in the
operator panel and
fit in the Summary
View and Detached
Summary View.
Click to select a font

for the OC2000
printed overlay. The
default font is
Courier New.
Enter an IP address,
such as 3.29.3.33, for
the default controller
serving the OC2000.
AcDcEx2000
The AcDcEx2000 tab allows you to select the following options.
Check to display the

EE address of items
in the block area of
the Outline View.
Select the Default

Communications
Settings.
Serial requires a
Baud Rate and
Com Port.
TCP/IP requires either

an IP address or a host
name in the Gateway
field. Host names can
be used when a name
server is present.
Note The default communication setting can be changed for all devices using the
default. The settings must be changed using the Modify Device dialog box.
Trend Recorder
The Trend Recorder tab allows you to select the following options.
Select any of the following

options.
Horizontal Grid Lines

displays the horizontal grid
lines when in replay mode.
Vertical Grid Lines
displays the vertical grid
lines when in replay mode.
Right Vertical Axis
displays the vertical axis
on the right side.
Dual Vertical Axis
displays the outer Y-axis.
Check to automatically
configure the recorder with
predefined signals.
Note: This option only works
with Innovation Series Drives
and when performing Mark VI
I/O board calibrations.
Check to zoom in the Trend

Recorder, using the mouse to
drag-and-drop a rectangle on
the screen.
Check for a Yes/No confirmation
prompt to display before the zoom
takes place.
Select the default pen width, Check to display Enter the amount of memory Click Default Colors to
in pixels, used to draw the the amount of the Easy-Drive reserves for change the colors used
signal traces. reserved memory storing traces. The default to draw the traces.
that was used. value of 2 MB allows four Click Columns to
signals to be captured at 32- select the headings to
ms intervals for about 14 be displayed in the
minutes before the oldest data Lower Signal View.
is overwritten.
Innovation Series Drive
The Innovation Series Drive tab allows you to select the following options.
Select the
communication
port from the
drop-down list.
Select this option to

program the keyboard
with an additional
language. This prompt
occurs when Keypad
Menus is selected from
Download to the DSP
in the Device menu.
If you select this option

and then go online, the
Device ID Verification
dialog box displays with
additional information for
the toolbox and the device.
It is normally checked.
Connect the Toolbox
The toolbox operates over Ethernet through a controller gateway and over a DLAN+
for an OC2000 and AcDcEx2000 or over ISBus to an Innovation Series drive.
Optionally, it can operate over a serial cable to a drive. The toolbox must
communicate with a device to configure or monitor it. There are two methods of
communication available:
See Windows Help Topics: TCP/IP is used to inter-network dissimilar systems. To use TCP/IP, the proper
Windows Setup Help for network software must be installed and configured in Windows NT or Windows 95.
installing and configuring If the toolbox uses TCP/IP to communicate with an OC2000 or drive, a controller is
TCP/IP. required to act as a gateway.
Direct Serial is available only with drives. The toolbox communicates directly with
the drive using the pc serial port. No special network software is required.
Innovation Series/Mark VI Controller

The toolbox can be directly connected to a controller using Ethernet.
Control System Innovation Series Controller

Toolbox
Ethernet
Windows PC
Toolbox connected directly to a controller
OC2000
The OC2000 communicates using DLAN+. The toolbox can communicate with the
OC2000 only when a controller acts as a TCP/IP to the DLAN+ gateway.
Control System OC2000

Innovation Series Controller
Toolbox
TCP\IP DLAN+
Windows PC
Toolbox connection to an OC2000
AcDcEx2000
Serial port communication from the toolbox to the AcDcEx2000 is by direct serial
connection of the pc COMM port and the AcDcEx COMPL connector on the
DS200STBA board. STBA jumpers can be moved from the as-shipped 1-2, 3-4
positions to the 1-3, 2-4 positions to compensate for a different transmit and receive
line cable configuration. TCP/IP communication requires a controller to act as a
TCP/IP to DLAN+ gateway.
Control System AcDcEx

Toolbox
Serial Cable
9-pin receptacle 25-pin plug

COMM connector COMPL connector
Toolbox Connection to an AcDcEx2000 Using Direct Serial Communication
Control System AcDcEx

Innovation Series Controller
Toolbox
TCP\IP DLAN+
Windows PC
Toolbox Connection to AcDcEx2000 Devices Using TCP/IP Communication
Do not reboot the pc with the serial cable connected to

the drive. This will cause a fault that trips the drive.
Innovation Series Drive
Serial port communication from the toolbox to the Innovation Series drive is by
direct serial connection of the pc COMM to the drive COMM connector (located on
the cabinet door just below the keypad). TCP/IP communication requires a controller
to act as a gateway to the Innovation Series bus (ISBus).
Control System
+
AC
Toolbox -
Serial Cable
Innovation
Series
9-pin receptacle
9-pin plug COMM
COMM connector
connector located
below keypad
Toolbox Connection to Drive Using Direct Serial Communication

+
- AC
Toolbox
TCP\IP ISBus
Innovation
Series Drive
Windows PC
ACLI or UCVC +
- AC
Innovation
Series Drive
Toolbox Connection to Drive Using TCP/IP and ISBus
Control System
Toolbox +
- AC
TCP\IP
Innovation
Series
MCL ACL
Dual-port memory
Windows PC
interface
Toolbox Connection to Drive Using TCP/IP (requires ACLA)
AccuWave Power Conversion Device
Serial port communication from the toolbox to the Accuwave Power Conversion
Device is by direct serial connection of the pc COMM to the device COMM
connector. TCP/IP communication is also possible directly to the MACC card.
Control System
+
AC
Toolbox -
Serial Cable
Innovation
Series
9-pin receptacle
9-pin plug COMM
COMM connector
connector located
below keypad
Toolbox Connection to Device Using Direct Serial Communication

+
- AC
Toolbox
TCP\IP ISBus
Innovation
Series Drive
Windows PC
ACLI or UCVC +
- AC
Innovation
Series Drive
Toolbox Connection to Device Using TCP/IP and ISBus
TMdrive Series Drive
Serial port communication from the toolbox to the TMdrive series drive is by direct
serial connection of the pc COMM to the drive COMM connector (located on the
cabinet door just below the keypad). TCP/IP communication requires a controller to
act as a gateway to the Innovation Series bus (ISBus).
Control System +
AC
Toolbox -
Serial Cable*
Tosvert
Series
9-pin receptacle
6-pin RJ45
COMM connector
connector located
on front of keypad
*Toshiba Part Number
3Z3A0382P001 (T-250, T350, T650W)
and
5P3A1563P472 (Leopack)
Toolbox Connection to Drive Using Direct Serial Communication

+
- AC
Toolbox
TCP\IP ISBus
Tosvert
Series Drive
Windows PC
UCVC +
- AC
Tosvert
Series Drive
Toolbox Connection to Drive Using TCP/IP and ISBus
Remote Connection
For more information, refer to Windows can make TCP/IP connections remotely, such as connecting the toolbox to
the Windows documentation on a remote device, using modems.
Remote Access Service and
Dial-up Networking.
Modem/Ethernet
TCP/IP Gateway
Control System
Toolbox TCP/IP
Modem Modem
Ethernet
Windows PC Innovation Series Controller
DLAN+
OC2000 DC2000 AC2000 EX2000
Remote Toolbox Connection to DLAN+ Gateway
Control System
Toolbox TCP/IP Modem/Ethernet
Modem Modem
TCP/IP Gateway
Ethernet
Windows PC Innovation Series Controller +
- AC
Innovation Series
MCL ACL
ISBus
+ +
- AC - AC
Innovation Innovation
Series Series
Remote Toolbox Connection to ISBus Gateway
Chapter 3 Basic Configuration
Introduction
This chapter provides instructions for using the toolbox to configure and monitor a
Mark VI Turbine controller. It also has information on using other features of the
toolbox specific to the controller.
Section Page
Introduction ..............................................................................................................3-1
Create a Controller ...................................................................................................3-2
Working with Files and Menus ..............................................................................3-14
I/O Checkout ..........................................................................................................3-37
Blockware Concepts...............................................................................................3-41
Configuration..........................................................................................................3-49
Software Setup .....................................................................................................3-100
Software Modifications ........................................................................................3-107
Monitor.................................................................................................................3-117
Control Constant and Tuning Variable View .......................................................3-124
File Compare View...............................................................................................3-128
Application Documentation..................................................................................3-131
Application Diagnostics .......................................................................................3-148
Dynamic Data Recorder (DDR) ...........................................................................3-156
Note If you are not able to perform an operation described in this chapter, check
your privilege level (refer to the section, Privilege Level Functions).
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 3 Basic Configuration 3-1
Create a Controller
For details of the toolbox When the toolbox is started, the toolbox Work Area displays. This area is used to
Work Area, see Chapter 2, the configure the controller or maintain the open configuration file in the toolbox. You
section, Work Area. must insert a new controller or open an existing controller configuration file (.m6b).
Note Each .m6b file must be kept in a separate folder.
To create a controller
Or click From the File menu, select New. The New dialog box displays.
Select the Controllers

tab.
Select Mark VI
Turbine Controller.
Click OK.
Product Version
The Choose the desired Product Version dialog box allows you to select the Mark VI
product version for the new controller. Multiple versions can be installed , beginning
with V05.09.00C. Refer to the section, Upgrade Configuration. When you select a
version and click OK, a new Mark VI controller is created, and the appropriate .tre
files are imported from the selected runtime.
3-2 Chapter 3 Basic Configuration GEH-6403L Toolbox for a Mark VI Turbine Controller
Once the controller is created or opened, the Outline View of the Work Area
displays the following configuration items under the controller name.
Default name
Configuration
items
To modify a controller
1. Click the controller name to highlight it.
Or double-click the controller 2. From the Edit menu, select Modify. The Controller Properties dialog box
name. displays.
The following sections describe each tab in the dialog box.
General Tab
The General tab contains the following parameters, described below.
Name specifies this controller when communicating with the SDB. It defaults to
mkvi1 the first time a controller is created. The name is saved as a .prj.
Clock specifies the source of the clock as internal or external. For Mark VI
controllers, set the clock to External (unless the hardware is a simulator).
Platform specifies the hardware platform on which the configuration operates. This
field is important for proper control execution records and for selecting hardware and
I/O. For more detailed information on selecting the appropriate platform, refer to
Chapter 9, Hardware and I/O.
Frame Period allows you to select the basic I/O and compute rate for a Mark VI
system.
Device No. is the system SDB number. If set to 0, the next available SDB number
is assigned to the device when data is entered into the database.
Check the appropriate radio button to select the control type.
Select the interval (ms) that the I/O Mapper task runs. The I/O mapper task
transfers signals between different I/O points, if the signals are not used in blockware
code.
Mark VI Standarads Template allows you to get the standard template of Mark
VI Turbine Controller.
Enable Dual Language Edit allows you to edit signal and pin descriptions in
both the main and alternate language (see Chapter 7, Create/Modify System
Information on how to define the two languages).
See section Configuration, Signal Definitions for more details on the use of dual
languages.
Memory Tab
The Memory tab defines (through Pcode records) how much memory to allocate for
this particular configuration.
System is the amount of memory used to store the configuration in the controller.
This number should not be increased above 2048, unless required. For example, a
110 error received during an online download indicates that the runtime does not
have enough memory available to keep two copies in memory, as is necessary to
perform an online download. Memory not allocated here is used by non-continual
processes, such as sending live data to toolbox sessions to support diagnostic
explanations.
Capture Buffer is the amount of memory to be reserved for data storage by capture
buffer blocks. Set this value to zero if the configuration does not contain capture
buffers.
Tip Error 178 displays during download, if insufficient memory is allocated for
the capture buffers.
NTP Tab
The NTP tab defines how to configure its Network Time Protocol (NTP) client. It is
used to synchronize the controllers clock with that of another computer on the
Ethernet.
Select the option to disable NTP or start the NTP Client and listen for broadcasts
from an NTP server.
The Unicast option allows you to start the NTP Client and request time from the
servers specified as Primary Server and Backup Server.
Note Tab
The Note tab lets you display information for the project history.
Alarm Scanner Tab
This function scans Boolean The Alarm Scanner tab specifies parameters for starting the Alarm subsystem in the
signals that represent various Mark VI. When any signals change state, they are queued locally and an alarm
alarm conditions. message is transmitted to the specified alarm display device. The alarm scanner can
be configured using either ALMGRP blocks, or by using the alarm attribute on the
Signal Definition dialog.
If your version of MarkVI Extended Alarm Queue Size check box allows you to use the larger alarm queue
runtime does not support this size (4096 active alarms versus 128 active alarms) available in supporting versions
option, the check box will be of the MarkVI runtime.
grayed out.
Enter the signal name of the alarm ID Array. This array associates an alarm with
These two fields are not used each Boolean signal scanned. The size of the alarm ID array (number of integer
for the latest Alarm Group elements) must match the size of the alarm signal array (only necessary when using
configuration. ALMGRP block).
Enter the signal name of the Boolean Signal Array to be scanned. The individual
signals that make up the array are populated by the ALMGRP block. The size of the
Some fields are optional and alarm signal array must match the size of the alarm ID array (only necessary if using
constitute a standard signal ALMGRP block).
interface to third party DCS
vendors that might be Alarm Present Indication specifies a Boolean signal that is set by the alarm
required to implement a system when one or more alarms are present in the queue.
subset of the alarm display Number of Active Alarms in Queue specifies an integer signal that the system
function. These signals can will populate with the number of active alarms currently in the queue.
be connected to the
appropriate I/O points to Horn Driver specifies an output that can be attached to an external alarm horn
make them visible to the DCS. contact output.
The alarm system drives the
Horn Silence specifies an input Boolean signal that can be used to turn off the
outputs and reads the inputs
alarm horn with a discrete pushbutton.
as described.
Acknowledge specifies an input Boolean signal that can be used to acknowledge
alarms with a discrete pushbutton.
Alarm Reset specifies an input Boolean signal that can be used to reset alarms with
a discrete pushbutton.
Horn Silence specifies an input Boolean signal that can be used to turn off the
alarm horn with a discrete pushbutton.
Acknowledge specifies an input Boolean signal that can be used to acknowledge
alarms with a discrete pushbutton.
Alarm Reset specifies an input Boolean signal that can be used to reset alarms with
a discrete pushbutton.
The length of the ID and ID (drop) and signal arrays are needed when using the ALMGRP block, and can be
signal array must be equal. created within any signal definition. Only one of each may exist within a Mark VI.
The signal array is an array of Booleans whose length is the maximum number of
alarms the MarkVI needs to use. The ID array identifies an integer array that
associates an alarm ID number with each alarm in the alarm signal array.
Refer to Turblib Help found Alarm Group (ALMGRP) blocks collect individual Boolean signals into a
in the toolbox Help menu contiguous section of memory (array) for the alarm scanner to process. By assigning
under Industry Blocks. a Boolean signal to the LINn pin of the block, it becomes an alarm. IDn is entered as
the corresponding drop number. The two arrays are populated in increments up to 32
assignments per block.
Note ALMGRP blocks can be in several tasks, but all must be connected to the
same signal and ID array.
The LOUT pin is

connected to the
signal array
designated in the
Alarm Scanner tab
(shown above)
and the DRP_ID
pin is connected to
the ID (drop)
array.
The ALMGRP block configuration generates a download error if:

Signal and ID array are not the same size
ID (drop) number is greater than the size of the signal and ID array
ID (drop) number is zero (0 is a drop number reserved by the system)
Duplicate ID (drop) number is used (checked only during an offline download)
Note These two fields are not used for the latest Alarm Group configuration.
Triple Modular Redundancy (TMR) Tab
The TMR tab is illustrated below.
For more information on the In a TMR operation, this integer is the internal process ID number, where 1=<R>,
TMR operation, refer to 2=<S>, and 3=<T>. Enter the signal name to access it within application code.
Chapter 9, Hardware and I/O
Enter the Boolean signal that indicates if this controller is designated. The
designated controller communicates on the LAN for the three TMR channels. This
feature allows you to use this information within the control logic or to export it to
other devices, such as SRTP or EGD.
Note If you do not want to access this information within the application, leave the
fields blank.
Hold List Scanner Tab
The Hold List Scanner tab is required to support Mark VI Large and Medium Steam
Turbine Controls on systems that have Automatic Turbine Startup (ATS). ATS sets
speed control targets and valve positions based on various inputs: steam temperatures
and pressures, calculated valve stresses, turbine rotor and shell stresses, metal
temperatures, and speed and operating mode. Turbine operating conditions can cause
a hold, which prevents ATS from setting the speed or load target to a higher value.
On the HMI, the Hold List Scanner display allows you to view the current points on
the Hold List and to override any or all hold points. Overriding a hold allows the
ATS to advance its targets as operating conditions permit.
Note The Alarm IP Address is used with this Hold List Scanner function. You must
fill in an IP address on the Alarm Scanner tab of this dialog.
Hold List ID Array specifies the hold entry identifier for each corresponding hold
signal in the hold signal array. The size of this array must match the size of the Hold
List ID Array.
Hold List Signal Array specifies the signals to be scanned by the hold scanner.
The size of this array must match the size of the Hold List ID Array.
Note These two fields are not used for the latest Alarm Group configuration.
Hold Present Identification specifies an output Boolean signal that is driven

TRUE if any of the entries in the hold list are TRUE and are not locked out.
Customer InformationTab
The Customer Information tab is illustrated below.
Ethernet Setup Tab
The Ethernet tab is illustrated below.
Ethernet 1 is the only available selection for all platforms earlier than the UCVE.
For more detailed A second Ethernet card can be configured for controllers with a UCVE platform.
information on multiple Additional Ethernet selections display in the drop-down list. To make an additional
Ethernet, refer to the Mark VI Ethernet configuration available, the Enabled option box must be selected.
Runtime documentation.
Enter the IP Name, Address and Subnet Mask for this controller.
Select the check box to enable Use Default Gateway.
Working with Files and Menus
A Mark VI controller is configured using different types of files. The configuration
files generate output files that can be downloaded to the controller.
Configuration files include:
Tree files (.tre) are text files that transport controller software and hardware
configurations to different versions of the toolbox.
Binary working files (.m6b) contain an exact copy of the configuration used by the
toolbox. Users generally work from .m6b files.
Note Each .m6b file should be kept in a separate folder.
Project files (.prj) are text files that keep track of the order of .tre files and hold
some controller configuration information.
Batch build files (.bld) can execute various toolbox operations on a list of different
configuration files.
Output files include:
Pcode files (.pcd) are application files and describe the configuration for the
controller. These files can be downloaded to the controller.
Symbol files (.sym) describe the signals used by diagnostics to the controller. These
files can be downloaded to the controller.
Signal reports (.sig), cross-reference reports (.xrf), Pcode reports (.pcr), and
block diagram printout files (.prn) can be generated, viewed, and printed.
Back up all files often to avoid losing data.
The following diagram shows the relationship between these files and the toolbox.
Programmer Workstation
mkvi_io.tre
sblib.tre
turblib.tre *.m6b file
hardware,
Save
library, and Export
function .tre files
Documentation
Import Open
Print
Open
*.prj file Export
(.tre) Get from
database Windows NT
or
The .prj files (Open/Export) Windows 95 Build
*.pcd & *.sym
list all .tre files that should be running toolbox files
imported for this controller.
Put into Download
database
Note The default installation directory

SDB or Controller
is C:\Program Files\GE Control System
USDB
Solutions\ToolBox.
Import Standard Files
For more information, refer to To configure a new controller, you must import a set of standard files, either through
Toolbox options in Chapter 2. the default library settings, project files, or manually. Most of these files come from
the controller installation, since the set of standard library files must match the
The default files imported by
runtime software.
File>New can be specified in the
Options dialog.
Tip To guarantee that data types used in later files are defined in earlier files, the
standard library files should be imported in the following order.
Sysdata.tre holds data types and eventually external signals defined by getting
information from the database.
Sblib.tre specifies the order and data types of basic block parameters of the Standard
Block Library.
Mkvi_io.tre specifies the hardware and I/O modules that can be configured with the
toolbox.
Turblib.tre is the Turbine-specific block library.
To import a file
Or click . 1. From the File menu, select Import. The Import File dialog box displays a list
all the available folders.
2. Navigate to stdtree (C:\Program Files\GE Control System
Solutions\MarkVI\stdtree).
3. If necessary, from the Files of type drop-down list, select .tre. All available
.tre files display in the list.
4. Select a file from the list. Or, type a name in the File name text box.
5. Click Open.
Save Files
Saving a controller file writes the entire contents of the configuration to a .m6b file.
The content of the file and everything associated with that configuration is preserved.
The prior .m6b is renamed to Backup of xxx.m6b.
To save a file
Or click 1. From the File menu, select Save. The Save As dialog box displays.
2. Enter the file name (change the file type, if desired) and click Save.
Once a configuration is saved, the Save button can save the new file without asking
for a file name. The Save button also indicates when a change is made to the
configuration by highlighting (turning red) and becoming enabled.
Note The Save button highlight feature indicates that the configuration has changed
and that a failure in the computer or toolbox will result in a loss of those changes.
Revision Tracking
Saving controller files starts the revision tracking system in the toolbox. Revision
tracking helps in troubleshooting configurations, as well as providing traceability and
ownership of files changes. The Revision Entry dialog box displays just prior to
the file being saved to disk.
Date/Time
stamp of
this revision.
The user name

of the currently
logged in
WIN98/NT/2000
account.
Enter a
description of
this revision.
Since a revision is required for each Save operation, selecting the Cancel button
also cancels the Save operation.
Revision tracking is enabled by default. To disable revision tracking, change the
toolbox options. Refer to Chapter 2, Toolbox Options.
Open and Close Files
Opening a .m6b file reads a previously saved controller configuration into the
toolbox.
To open a file
Or click 1. From the File menu, select Open. The Open dialog box displays.
2. Select the file name and click Open.
Check the Release Notes located Note If another version of the toolbox is used to open a .m6b that was saved with a
in the toolbox Help menu under different version, a Warning displays. Either install the toolbox version that the .m6b
About Toolbox. was saved in (listed in the Warning box) or consult the toolbox Release Notes to see
if they are compatible.
To close a file
From the File menu, select Close.
Closing a controller file removes the configuration from the toolbox. If the
configuration has not been saved, a dialog box displays and asks if the configuration
should be saved.
Export Configuration Files

This option is normally not required, but is provided when
upgrading between versions of the Mark VI controller runtimes
older than V05.09.00C. The Export command can also be used if
there are problems with a newer version of the toolbox that
changes the configuration file (.m6b) format that is not backward-
compatible, or if there are problems with a runtime upgrade.
Normally, newer versions of the toolbox load configuration files created by older
versions. However, if a problem occurs because of a major change in functionality,
the toolbox may not be able to load the configuration file. In this case, it is necessary
to first export the configuration file with the old version of the toolbox to a project
file, and then open the project file with the new version.
Note The .tre files can be exported selectively, or for the entire controller.
The Upgrade command is also used to upgrade a configuration (.m6b) from one
runtime version to the next. But if the upgrade needs to take place between runtimes
that are less than V05.09.00C, the upgrade command cannot be used. In this case, an
Export All command is performed. The new Mark VI controller runtime is installed,
and the project file that uses the new runtime files is opened, completing the
upgrade.
The manual Export command may also be necessary if there are automatic upgrade
problems due to major changes in the runtime features. The Export command allows
for a manual upgrade, which corrects problems with the automatic upgrade.
Note The first time you export, make sure that each item is configured to be saved in
the desired directory.
The .prj file is used together To export a single file
with the .tre files to manually
1. From the Outline View, select the item to be exported.
transport controller software
configurations to different 2. From the File menu, select Export, then Selected Item. The Export dialog
versions of the toolbox that box displays.
are not backward-compatible.
3. Specify the file name and click Save. The file is exported to the named .tre file.
The project file is generated
with the Export All command, To export the entire controller
which exports the required set
From the File menu, select Export, then select All. The Export All Options
of .tre and .prj files for the
configuration.
Click the desired option button to name and

save the .tre and .prj files.
If you select Use specified folder for all

files, a specific folder can be entered or
select Browse... to search for the folder.
Selecting Use original file name and

folders or Use specified folder for all files
displays all available files in the Checked
files will be exported dialog box shown
below.
Only files that are

checked will be
exported.
If no source file is
defined for the file
to export, then you
are prompted
for a .tre file name
before this dialog
displays.
Work with Project Files
The project file also includes A project (.prj) file is a text file that holds the names of all .tre files for a
controller information, which configuration. Project files allow you to export and import a controller configuration
is entered in the Device Edit without having to know about all the files. You can also prevent a file from being
dialog box. exported by editing the function or the software library and then locking the item.
To create a project file
1. From the Outline View, select the controller item.
2. From the File menu, select Export, and then select either Selected Item
(exports just the .prj file) or All (exports all .tre files and the .prj file).
If the import fails because Once a project file exists, it can be used to create a controller configuration (.m6b
something is undefined, the file). From the File > Open command, select a .prj file. This creates a controller
order may be incorrect. To and starts a series of file imports. The toolbox imports the files listed in the .prj file,
change the order of the .prj including the standard library files, in the order that they display. The project file
file, edit the file with any text also contains the version of the runtime, which defines the standard library files to be
editor imported. Refer to the next section, Files in the .prj.
Files in the .prj
To view a list of files included in the project
From the Outline View, select the controller name. Make sure Tracking is on.
Click Observe the information listed in the Summary View (shown below).
Summary View information
Toolbox revision
Controller properties
Files included in the project
To prevent exporting an item

1. From the Outline View, select a function or macro and module library.
2. From the Edit menu, select Modify. The Edit Function dialog box displays to
edit a function or the Edit Software Library displays to edit a library (refer to
the next section, Locked Items).
Note This same No Export option can be applied to function files or macro and
module library files.
Upgrade Configuration
Note Prior to Mark VI runtime version V05.09.00C, only one runtime product could
be installed at a time. Because an upgrade required uninstalling the old runtime and
installing the new one, all Mark VI runtime configurations were forced to upgrade to
the new runtime. Going forward with V05.09.00C, multiple controller products can
be installed at the same time. Installing a new Mark VI controller runtime leaves the
previous one intact.
When installing a new Mark VI runtime product that is

V05.09.00C or newer, do NOT uninstall the old runtime. Only
uninstall the old runtime once all configuration files have been
upgraded to the new runtime, and the system is operating with
no errors.
This command upgrades the current configuration file to include the features of the
new controler product version. For example, the current Mark VI configuration file
(.m6b) is made with version V05.08.02C. The application requires the features of
version V06.09.00C. Upgrade the configuration file as follows:
To upgrade a file
1. Verify that the new required Mark VI version is installed (refer to Chapter 2).
2. Verify that the current Mark VI configuration file is saved (if it is not saved, the
upgrade process will save it).
3. From the File menu in the current configuration file (.m6b), select Upgrade.
The following message box displays.
If you select Yes, the Select Upgrade Version dialog box displays all newer
installed versions. Select a new version to upgrade.
4. Select the version to upgrade to and click OK. Once the upgrade process is
finished, the following message displays.
Locked Items
To edit the Functions or Macro and Module Libraries (Software Library) items,
located in the Outline View, double-click the item name. The associated edit dialog
box displays.
Modify the function or Click to enter a new

library name. password (refer to
the section, Change
Enter the directory related Password for
to the function or software Locked Items).
library.
Check if the file is not to be

exported.
Check to enable password

protection (refer to the
section, Password
Protection).
Enter a note associated

with this function or library.
Note If Password Protection Enabled is checked, the Enter password for

<item> dialog box displays. You must enter the proper password to access the item.
Password Protection
When a function or
macro/module library
has password
protection enabled, a
lock icon displays
beside the name.
The name of the locked item you are
attempting to open displays in the title
of the dialog box.
Any attempts to
edit or use an
item within a
locked function or
library requires
you to enter the
password for the
item.
The contents of a locked icon can be used within other items of the toolbox without
unlocking the icon by entering the correct password. However, to view contents of a
locked icon item, you must select that item and enter the password to unlock the
icon. Any time a locked icon is accessed from the Outline View, the Enter
password dialog box displays.
Re-lock Command
An unlocked icon means that

a password exists, but is
temporarily disabled (a
password has been entered
to unlock the icon).
To re-lock an item and enable the password

Click the right-mouse button on the function or library name. The following
shortcut menu displays.
Select Re-lock Function
To lock all unlocked items in all open devices
Click anywhere in the Outline View.
From the Options

menu, select
Logout User
The Logout User command clears the user ID and sets the privilege level to zero
(refer to the section, Privilege/Password). It locks all libraries or functions (in all
open devices) that are in the temporarily unlocked state.
Change Password for Locked Items

To change password
1. From the Outline View, click the Function or Library name.
2. From the Edit menu, select Modify. The associated Edit dialog box displays.
3. Click . The Change Password dialog box displays.
Enter a new password.
Enter it again to verify

the new password you
just entered.
Click OK.
Batch Operations
Many operations in a controller configuration can be started for more than one
controller using batch operations. The file name and the operation for each file can
be saved in a batch build file (.bld).
To create a batch build file
1. From the File menu, select New. The New dialog box displays.
2. Click the Utilities tab, select Batch Build File, then click OK. The Batch
operations dialog box displays.
The controller performs the following batch operations:
Put Signals puts the controllers signal data into the database.
Get Signals obtains another controllers signal information from the database.
Validate Device verifies that the configuration is ready to build Pcode.
Export Device writes the .tre and .prj files for a configuration.
Build Device creates a Pcode file.
Save Device writes configuration to an .m6b file.
Offline Download downloads the Pcode file to the controller and restarts it.
Flash Download downloads the Pcode file to flash memory.
Build Symbols creates a symbol file.
Put Symbols writes the controllers symbol information to the database.
Download Symbols downloads the symbol file to flash memory.
Menu Commands
The toolbox work area contains the following Menu bar:
File Menu
The File menu provides the following commands:
New creates a new controller/file.

Or click .
Open displays an existing controller/file.
Or click .
Close exits an existing controller/file.
Or click . Save/Save As preserves an opened controller/file to a specified name.
Import retrieves a file from the specified source. Or, from the menu, select Imports
Or click .
a second language report.csv file.
Export sends file(s) to a specified .tre file.
Compare compares the functions of the currently open file with those of another,
user-specified file.
Upgrade allows you to upgrade the Mark VI configuration file from one version of
the runtime to a newer version.
Print Setup allows you to select a printer and printer connection.
Or click . Print provides a paper (hard) copy of a specified file or page.
Print to MetaFile prints the block diagram to a set of Enhanced Metafiles (*.emf)
instead of sending it to the printer. These metafiles can be viewed using various
graphical software programs, or imported into text processing programs such as
Microsoft Word.
Print Preview displays the page as it would be printed.
Send To opens email and provides a copy of the currently opened file to send (you
must have Windows messaging, such as Exchange).
File 1, 2, 3... lists and opens a previous opened file.
Exit closes the toolbox.
Edit Menu
The Edit menu allows you to modify the controller:
Modify edits the item highlighted in the Outline View.
Or click . Delete removes the item highlighted in the Outline View.
Cut removes the highlighted item and places it on the clipboard.

Or click .
Copy duplicates the highlighted item and places it on the clipboard.
Or click .
Paste places the highlighted item from the clipboard into the current file.
Or click .
Insert First inserts the first new item under the item highlighted in the hierarchy of
the Outline View.
Insert Next inserts the next new item at the same level as the item highlighted in
the hierarchy of the Outline View.
Instance updates a single item or select All to update the entire controller/file.
Renumber changes the numbers of the highlighted blocks.
Bookmark items display this Bookmarks enable you to mark major items in the Outline View and then return to
icon . them using the menu commands or clicking the bookmark icon.
Override Modules unlink all software modules from their library templates.
View Menu
The View menu allows you to view areas within the controller with the commands
listed.
Click to toggle Tracking Tip For faster navigation in the Outline View, turn Tracking off. Only turn
on and off.
Tracking on to view an item in the Summary View.
A check mark ( ) displays by Toolbar displays or hides the Toolbar.
the command name when the
Status Bar displays or hides the Status bar.
feature is on.
Tracking toggles the tracking feature of the Summary View on and off.
Or click .
Close Outline reduces the hierarchy items listed in the Outline View to just the
controller level.
Detached Summary creates a separate window of the Summary View.
Or click .
Zoom In enlarges the view of the block diagram area.
Or click .
Zoom Out reduces the view of the block diagram area.
Or click .
Go Back and Go Forward allows you to return to earlier selections in the
Or click . Outline View.
Finder starts the Finder window to search text and signal usage.
Watch Windows creates a customized, quick-reference list of signals and their
online values.
SDB Browser is a separate window, which can help you find items (such as signal
usage from the different types of controllers), display the topology of a system,
perform a filtered signal search on the SDB, and more (refer to GEI-100271).
Force Lists displays forced signals and I/O points that can be edited.
Reports creates a report of the Alarm List, Hold List, Event List, Scale List, Signal
List, Signal Cross Reference, Multiple Written Signal List, EGD Network,
Simulation Data, Control Options, I/O Report, I/O Point List, Unused I/O Report,
Revision Log Report, Enumerated Data Types, Control Spec Reports (IO Config and
Signal Config), Block Pin Report, or Tuning Variables.
Note Refer to Chapter 3, Application Documentation, Reports for detailed

information on the reports the toolbox can generate.
Trend Recorder monitors and graphs signal values from a controller (refer to
GEH-6408).
Control Constants displays a separate window to view control constants, which
can be viewed and compared as a group, exported to .csv files for manipulation
outside of the toolbox, and merged back into the configuration.
I/O Checkout creates a report of all I/O with columns to indicate if the I/O point
has been checked (its status), when it was checked, and a freeform note for each
point.
Configuration Statistics opens the Device Metrics window to display memory
usage.
Controller Status Commands are hardcoded QNX commands. They display
under one of the following menus: General, File System, Network, or
Process.
Controller Load Profiler allows you to quickly and easily interrogate the
controller to determine what application tasks are scheduled to run and which, if any,
are delayed.
Controller State creates a report on the current state of the controller.
Device Menu
The Device menu allows you to manage the controller with the commands listed.
Validate makes certain that selected items or functions do not contain errors and
Or click . confirms that a configuration is ready to build Pcode.
Build compiles the configuration and generates the Pcode.
Or click .
Pack signals reassigns address tokens when signals become fragmented.
Download sends files to the current controller.
Or click .
Application Code sends the values of all the parameters from the loaded
controller configuration files to the current controller.
Product Code (Runtime) sends the Mark VI firmware configuration to the
current controller.
Compact Flash allows Compact Flash to be reprogrammed.
View/Set Time allows time in controller to be set to pc time.
View/Set Totalizers displays the totalizer information.
Restore from Perm Storage overwrites the application code stored in the
controllers RAM with the code stored in the controllers FLASH.
Upload retrieves Mark VI files from any controller.
Online/offline toggles to initiate communication to the controller.
Or click .
Put Symbols Into Database places diagnostic symbol information into the
database.
Put Into Database places controller information into the database.
Get From Database reads information from the database and places it in the
current configuration.
Create Undefined Signals produces a definition for signals not defined.
Note For additional information on the Put Into Database, Get From
Database, Validate, Upload, Build, and Download commands, refer to the
section, Device Menu Commands.
Options Menu
The Options menu allows you to manage general options for toolbox operation.
For more information on the

Option menu, refer to
Chapter 2, Using the
Toolbox.
Settings allows you to assign general toolbox options.

Privilege sets the privilege level for a session.
Passwords sets the password for a privilege level.
Logout User clears the user ID and sets the privilege level to zero. It locks all
libraries or functions in all open documents in the temporarily unlocked state (refer
to the section, Locked Items).
Re-Lock Function or Software Library locks the item and enables the
password.
Window Menu
The Window menu allows you to manage screen views..
Cascade arranges the windows in an overlapped style.

Tile Horizontal arranges the windows in horizontally non-overlapped tiles.
Tile Vertical arranges the windows in vertically non-overlapped tiles.
Arrange Icons arranges the icons of closed windows.
Close All closes all open windows.
Window 1, 2, ... allows you to view currently open files.
Help Menu
The Help menu offers the following Help files.
Contents displays the Help files for the toolbox.

Using Help displays general instructions on how to use Help.
Standard Blocks displays a block library used across all industries.
Industry Blocks displays a block library used in specific industries, such as
metals, paper, and material handling.
Runtime Errors defines errors that display in the Log View.
Item Help displays Help information about the item highlighted in the Outline
View.
Release Notes provides product changes in the toolbox.
Send Problem Report allows you to submit a system change request for the
toolbox.
Goto Toolbox Web Site takes you to the toolbox home page.
About Toolbox displays the version number and platform for this application.
I/O Checkout
This view allows you to customize the optimal setup by providing live data during
the I/O checkout phase of turbine installation. It allows you to select the columns
desired for the report. Once the report is generated, click the column header to sort
the data in each column.
To view an I/O checkout report
From the View menu, select I/O Checkout.
The Select Columns dialog box displays to allow you to select the desired
information for the report.
Click the
checkbox to
select a column.
Click the box
again to uncheck.
Click OK. The I/O

Checkout view
displays.
Click to zoom in (increase) or
Click to define the zoom out (decrease) the text size
Checkout status (refer to in the checkout view. If the
the status box below). To currently selected font is at its When online, live data displays in green. Points that
Checkout any item, the maximum or minimum, the font do not correspond to data from the Mark VI will be Click on a column
privilege level must be at must be changed to a different font displayed as N/A. To change or force the live data, header to sort that
least 2 in the Options menu right click on the row and choose Change Live Data. column alphabetically
Click
Filter to
determine
items to
display in
columns.
Refer to
section
Filtering
Click to
add or
remove a
column.
The status bar displays three items.

Percentage of filtered points that are in the Verified State.
Percentage of all points that in the Verified State.
Number of points that are currently being displayed.
I/O Checkout Status
During checkout, the point is time stamped
every time its status is changed. Default
operation automatically uses the system
time and date for a time stamp, but the
user may enter a different date by
unchecking the Checkout Date
checkbox. Any change to the checkout
status, date, or note, will be recorded in
the change history log
There are four levels

for the checkout
status.
Verified is for points
once the checkout is
complete.
Incomplete is for
points that are in
progress.
Untested is the
default value for any
point.
Not Applicable is for
points if no checkout
can be performed.
Filtering
Select to display all entries or only one of
each entry. Select Only display one of each
entry for items with identical cell values. All
rows, that include any value in that column
already displayed, is hidden.
Single or multiple
columns can be
filtered. To determine
item(s) that can be
displayed check the
column checkbox,
then in Search Text
enter the search
string (refer to
wildcard
combinations below).
The wildcard combinations are:

Search string or *Search String search for that string anywhere in the cell
*Search string search for cells items that end in the search string
Search string* - search for cell items that begin with the search string
If the visible item represents more than one item due to unique filtering, the
following dialog box displays.
Blockware Concepts
For more information on how The controller software is made up of blocks that perform control logic. The
to configure each item, refer software is referred to as blockware. These blocks correspond to a function block
to the section, Configuring that exists in the product code (runtime). The block definitions are imported as .tre
Controller Blockware. files within the block libraries.
These blocks are used to make up macros. Blocks and macros make up tasks. One or
more tasks can go into a module and any number of modules make up a function.
This hierarchy shows how the different levels of controller blockware display in the
Outline View below.
There are two levels of blockware that can be reused and instanced any number of
times:
Macro(s) contain a standard collection of blocks.
Module(s) are a more complex collection of tasks that have a defined
scheduling relationship.
For more information, see In the toolbox, block, macro and module parameters are called pins (from their
Chapter 11, Signals and the likeness to the pins of an integrated-circuit chip). All pins have a name unique to
Database. their block, macro, or module. Pins are connected by signals, which are the basic
unit for variable information. Signals are created with signal definitions, module
pins, and macro pins or block pins.
Blocks and Block Pins
Standard library block names Blocks are the most basic programming element. They can perform functions such
are preceded with an underscore as math, solve an RLD, and perform a filter. They can also solve a Boolean equation.
( _ ), such as _CLAMP, to (These blocks can be compared to C-language functions, Pascal procedures or
differentiate them from macros FORTRAN subroutines.) The product code blockware supports a function for each
and blocks in the Industry block block that displays in the standard or Industry block libraries. For more information
library. about the individual blocks and how they work, see the toolboxs Block Library
Help.
When a block is inserted into a task, a number and colon is added before the name to
make the use of the block unique, such as 20:MENG. This number is used to refer to
For connecting information,
pins of the block from other blocks in the same task or macro, such as 20:OUT.
refer to the section, Connect a
Pin. Block pins contain signals when the block is inserted. Block pins can be connected
to one another or to other pins and signals using these signals.
Macros, Macro Definitions, and Macro Pins

A macro is a collection of blocks and other macros that contains well-defined inputs
and outputs. You can create a macro by constructing a macro definition. If the macro
definition changes, add a version number.
Once the macro is defined, insert the macro into a task or another macro. The
inserted macros internal blocks and connections cannot be changed. Macros can be
inserted in up to three levels as follows:
Macro pins have unique names; once inserted, they can be referenced just like block
pins. Macro pins are also signals that can be connected to the pins of the constituent
blocks and macros. Once inserted, these macro pins act as the parameters of the
macro whose behavior is specified based on how they are used in the code inside the
macros. The macro can have one macro pin designated as an enable pin. The enable
pin is a logical or Boolean signal that activates a macro.
Macros are shown in the following Outline View. The item, Macro Definitions, is
located in both Function and in the Macro and Module Library. The library provides
a main location for standard modules and macros. Function provides a location for
modules and macros used in a particular function.
If a macro is defined local to a function, it cannot be used outside that function.
Therefore, if the macro is used in more than one function, it should be defined in a
macro library. Also, if the same macro is used in more than one controller on a given
job or used on more than one job, it should also be in a library.
The libraries only contain code definitions, not code already instanced to run in the
controller. By defining the macro in a library, the library can be directly imported
into the second controller without having to separate instanced code. This makes the
maintenance of that macro easier, should it ever need to be changed.
For information on If a macro definition is changed, the inserted versions of the macro can be updated
instancing, refer to the by instancing the macro. Instancing a macro replaces all the blocks and macros, and
section, Instancing Module their connections inside the macro, but keeps the connections to the macro pins of
and Macro Pins. the macro instance. Macros can only be instanced individually, if they are in a Task
(top level).
Tasks and Scheduling

For more information, refer Tasks divide a module into items that require different scheduling parameters. Each
to GEH-6410, Innovation task has a period multiplier. The task period multiplier determines the rate of task
Series Controller System execution by a binary multiple of the module base scheduling period. This can be 1,
Manual. 2, 4, or 8 times the module period or event driven. A task can be scheduled to run
based on 5 ms, 40 ms, or 320 ms module period.
Tip A task cannot be scheduled to run any faster than the Frame Period specified
in the General tab of the Controller Properties dialog box (refer to the section,
Creating a Controller, General Tab).
See the Task Scan Scheduling To equalize CPU loading, each task has a skew offset that shifts its scheduling
Periods Table for a list of position relative to other tasks without changing its execution frequency. The
possible combinations of skew possible values for skew offset vary between 0 and 7 as a function of the period
and period multiplier and the multiplier.
effect of each on task
scheduling. Note Care should be taken when data is shared between modules at two different
time bases. This shared data can change at any time within the slower module, when
the faster module pre-empts it.
Tasks are scheduled to run based on the order that they display in the Outline View.
In the following example, TaskA comes before TaskB and TaskB comes before
TaskC. If all three tasks are scheduled with the same module period, period
multiplier, and skew offset, TaskA always runs before TaskB and TaskB always runs
before TaskC.
For example, the scheduler runs tasks that are scheduled to run in a 40 ms time slice.
If there is extra CPU time before the next 40 ms time slice, it will run any 320 ms
based code currently scheduled to run.
Task Scan Scheduling Periods Table

Within a time slice, the tasks are In the following table, each time slice is either 5 ms, 40 ms, or 320 ms long, based
scheduled based on the order on the scheduling period selected for that module in the Edit Module dialog box. If a
they display in the Outline View. controller has several modules with the same scheduling period, all the tasks within
all these modules end up together in the same scheduling table. In the table, X
represents when a task will run based on the period multiplier and skew offset
selected for it.
Task Scan Periods at 5, 40, & 320 ms Module Base
Task Task Skew Offset+Module Scan Period Slice 1 Slice 2 Slice 3 Slice 4 Slice 5 Slice 6 Slice 7 Slice 8
PeriodMult Skew
0* 0
1 0 5, 40 or 320 X X X X X X X X
ms
2 0 10, 80, or X X X X
640 ms
2 1 10, 80, or X X X X
640 ms
4 0 20, 160, or X X
1280 ms
4 1 20, 160, or X X
1280 ms
4 2 20, 160, or X X
1280 ms
4 3 20, 160, or X X
1280 ms
8 0 40, 320, or X
2560 ms
8 1 40, 320, or X
2560 ms
8 2 40, 320, or X
2560 ms
8 3 40, 320, or X
2560 ms
8 4 40, 320, or X
2560 ms
8 5 40, 320, or X
2560 ms
8 6 40, 320, or X
2560 ms
8 7 40, 320, or X
2560 ms
* A task with a 0 period multiplier is only scheduled if an Event is executed.
Task Execution
Tasks can be enabled and disabled from the blockware by connecting the task enable
to a signal and modifying the online value. Disabling a task prevents it from
executing, regardless of its schedule or any Events put into the database. To prevent
execution of the blocks in that task and the inputs and outputs used in that task from
being transferred, Task enable can be forced to False, using the toolbox.
Tasks are configured to execute periodically. All the external inputs referenced by a
task are automatically transferred from the I/O table to the signal table, just before
the task execution. This signal is frozen for the duration of the execution, as long as
it is not shared by a task in a module with a shorter scheduling period.
Tasks in modules with a 40 ms scheduling period have a higher priority than tasks in
modules with a 320 ms scheduling period. If a 320 ms base task is running when it is
time for a 40 ms base task to run, the 320 ms base task is interrupted for the 40 ms
base task to run. However, within the same module-scheduling period, one task
cannot interrupt another even if it is currently scheduled to run.
For example, taskA is scheduled to run every 640 ms and taskB is scheduled to run
every 2560 ms. If taskB is currently running when it is time for taskA to run, taskA
can not interrupt taskB. However, all control blocks are written to use absolute time.
This means that a timer block in taskA would know and adjust appropriately if more
than 640 ms had passed since it last ran. It would not assume that 640 ms had passed
just because taskA was scheduled to run at that rate.
For more information, see the All the external outputs referenced by the task are transferred from the signal table to
section Simulation System. the I/O table at the end of the task execution. Forcing or simulation can override the
I/O transfers. Even if a task is exited early, its outputs are still written.
Modules can also have a skew. A module skew is added to the task skew offset for
all tasks in the module. It is normally used for processes such as the following. A
module definition is written to control one stand of a finishing mill. The module is
then instanced six times, once for each stand in the finish mill. Each stands module
instance has a different skew offset, so that all the code will not be scheduled to run
at the same time.
Module pin signals can be internal signals, I/O signals, or network signals. Module
pins have an Event option, independent of the signal attached to the pin, which
affects how blockware is scheduled.
Frames
A Mark VI frame is the period in which the controller reads inputs, computes a
control algorithm, and produces outputs at the terminal boards. To insure proper
operation, all tasks must run to completion within this window and still reserve
enough time to perform the I/O.
Input Task Output and Input Task Output and

collection execution distribution collection execution distribution
and voting and voting
Frame 1 Frame 2
40 ms
Example of 40 ms Frame
Modules, Module Definitions, and Module Pins
Modules allow you to reuse blockware on a higher level than macros. All blockware
downloaded can be found in the Outline View, Function level, in the item Modules.
Note There is not a Modules item in the Macro and Module Libraries level.
However, Modules Definitions can be defined there.
There are several types of modules:

Instanced modules are defined in the item Module Definition under Functions
or Macro and Module Libraries, then instanced in the item Modules under
Function. Like macros, these modules are updated by changing the definition
and then instancing that particular module (once instanced, the tasks cannot be
changed).
Inline modules are defined in the item Module under Functions. They are not
meant to be reused.
Override modules are a combination of the instanced and inline modules. They
are created by instancing a module definition and then overriding it from the
Module Edit dialog box. Overriding a module allows you to start with a
standard module definition and then be able to modify it as an inline module.
The pins of a module work similar to macro pins. Module pins are primarily intended
as parameters to the module. However, a local pin can be used to share data between
tasks in the macro.
Module pins can be connected to external signals through the Module pin
definition dialog box. The connections owned by the module pin are kept intact
when a module is instanced. In this way, a module can be updated with a new
module definition and not lose these connections.
All modules have a region name. The complete signal name for a signal associated
with module pins is the modules region and pin name. For example, the instanced
module CM\std1\speed and module pin name, AutoMode produce the signal name
CM\std1\speed\AutoMode. In the module, the block and macro pins can reference the
module pins by using the module pin name only.
The period and skew of a The period and skew of a module can be overridden in an instanced module, without
module are discussed in the actually overriding the entire module definition. This permits users to maintain the
section, Tasks and Scheduling. inter-relation of modules in the same scheduling chart, while incorporating changes
made to a module definition.
To determine if a Module Module Definitions include a revision field. If the definition of the module changes,
Definition should be under the update the revision. When a module definition is instanced, the instance shows
item Module Library or which revision it was instanced from. This helps determine if a module has been
Function, refer to the section, re-instanced after a change was made to the module definition.
Macro Definition.
Functions
Functions are also associated Functions are at the highest level in the hierarchy and used primarily to group
with a .tre file in that each inter-related modules. All the data types scale factors, signals, module definitions,
function is exported as a macro definitions and instances for a given function can be independently associated
separate .tre file. with a function, which allows you to move a function from one controller to another.
Libraries
The controller has three types of libraries:
Block libraries provide a description of the runtime blocks.
Hardware Module libraries describe the different types of I/O that can be wired
into a controller. It is described in the file, mkvi_io.tre.
Macro and Module libraries provide a central location for standard macros and
modules.
For Macro and Module libraries, the .tre files have the same basic format as
Functions .tre files, except for the file descriptor at the beginning. Also, there is no
Modules item, only Macro and Module Definitions. Macro and module libraries can
be imported again, as needed.
For more information, refer For Block libraries, the .tre file must be imported and the runtime standard or
to the section, Monitoring. industry software must be downloaded to the controller. A mismatch of .tre file
libraries and the corresponding runtime software cause the controller to stop
executing when the controller is downloaded. To import a new block library, it is
necessary to export the entire configuration, then import it with the new library .tre
files located where the old files used to be.
Configuration
A controller configuration is constructed by using the toolbox or by importing .tre
files containing blockware. To build the configuration using the toolbox:
Create a controller
Import the necessary libraries
Insert blockware and hardware
For more information, refer Blocks correspond to a function block that exists in the runtime. These blocks are
to the section, Blockware used to make up macros. Blocks and macros make up tasks. A task(s) can be inserted
Concepts. into a module and any number of modules makes up a function. All of these items
are inserted into a configuration the same way.
Create/Delete Blockware
To create blockware into a configuration
1. From the Outline View, click a blockware item to highlight it.
Once an item exists, another item 2. From the Edit menu, select Insert First. Or, click the right-mouse button and
can be inserted by following the select Insert First. Depending on the item being configured, a dialog box
same steps, but select Insert displays to name and define the item.
Next.
Note If a command name is grayed, it indicates that the command does not apply to
the current situation or that you need to make a selection or complete another action
before selecting the command.
To delete a block(s) from a configuration

1. From the Outline View, click the desired item to highlight it.
Or click 2. From the Edit menu, select Delete. Or, press the Delete key.
Functions and Software Libraries
A function or software library acts as a grouping mechanism for inter-related scales,
type, signal, macro and module definitions. Only functions have modules, which
contain the software downloaded to the controller. Each function or software library
can be exported to a .tre file with the default name, funcname.tre.
To insert a function into a configuration
Once a function exists, 1. From the Outline View, select Functions.
another function can be
2. From the Edit menu, select Insert First. Or, click the right-mouse button and
inserted by following the
select Insert First. The Function Name dialog box displays.
same steps, but select Insert
Next.
Enter a name with up

to eight characters
and click OK.
This item is inserted
into the Outline View
(shown below).
To edit a function
1. From the Outline View, highlight the function.
2. From the Edit menu, select Modify. Or, right-click and select Modify from the
shortcut menu. The Edit Funtion dialog box displays.
Displays the default access level of Revision allows you to keep track
this function. of changes to the function
Use - This function will be used in definition. The form of the
code, but you will not be able to view revision must be V##.##.##A,
or change it where ## is at least two decimal
View - view this functions contents, digits and the final A can be any
but not change it. alphabetic character. If the
Change - you have total access to format is entered incorrect, the
this function. toolbox replaces the revision
string with V??.??.???.
The function name displays.

Displays the name of the .tre
file assocated with this
function. This field can be
modified during the export
process.
Enter the location of the help
file assocated with this item.
Item help is selected using
the right-mouse shortcut
menu.
prevent the file from being
exported during an Export
All command.

enable password protection.
Refer to the section, Locked
Items.
This button displays the
Change Password dialog box,
allowing you to set or change
the password to lock this item
when password protection is
enabled.
Enter a note to
describe the
function.
Note The Access Protection is independent of the Password Protection scheme.

Access Protection uses the Privilege level settings, and works in the same manner as
Macro Protection. See Chapter 2: Privilege/Password for more information.
Note As noted before, the above information for Functions also apply to Software
Libraries.
Type Definitions
Type definitions are enumerated data types, which can be used by pin or signal
definitions. An advantage of using type definitions is that the pin of a block, macro,
or module can be limited in scope to particular values or a range of values. Also, you
can select another controller name, instead of using the controller drop number.
To insert type definitions into a configuration
1. From the Outline View, click Type Definitions to highlight it.
Or click the right-mouse button 2. From the Edit menu, select Insert First. The Type definition dialog box
and select Insert First. displays to define the data type.
Note Once a type definition exists, another can be inserted by following the same
steps, but selecting Insert Next. The item can also be deleted.
The Type Definition dialog box is also used to edit existing type definitions.
To edit a type definition
1. From the Outline View, click the type definition name to highlight it.
Or double-click the type 2. From the Edit menu, select Modify. The Type definition dialog box displays
definition name. (refer to the next section, Define Type Definition).
Define Type Definition
Define the type definition below.
Enter a name of up to 12
characters.
Enter a description of up
to 50 characters.
Select the basic data type that
this type definition is based on
(refer to the list below). Type
definitions are always based on
another data type.
Select the data entry restriction.

If Range, assign a minimum
and maximum range definition.
If Enumeration, define the
Value name and value.
To add an enumeration, enter a
name and value, then click
Add.
To modify, select the
enumeration, make changes,
and click Add.
To remove, select the
enumeration and click
Remove.
Basic Data Types

Bool - 8-bit Boolean (0 to 1)
Int - 16-bit signed integer (-32, 768..32,767)
Lint - 32-bit signed integer (-2,147, 483,648...2,147,483,647)
Float - 32-bit IEEE floating point (-3.4 + 38 to 3.4E + + 38)
Lfloat - 64-bit IEEE floating point (-1.8E + 380 to 1.8E + 308)
Collection Data Types
Analog includes all basic data types, except Boolean
Simple includes all basic data types
String is zero-terminated ASCII string (1 to 255 characters)
(Strings must be an array whose length equals the maximum
number of characters + 1 for the terminating zero.
Predefined Type Definitions
Type definitions are used extensively with database settings. Some type definitions
obtain information specific to a particular process by getting it from the database.
To locate predefined type definitions
Or click 1. From the File menu, select Import.

2. From the Import dialog box, import the file Sysdata.tre.
3. From the Outline View, click the symbols next to the item System Data
and again next to Type Definitions to display the predefined type definitions
from the database.
Scale Definitions
Scale definitions can be associated with signals. They are used primarily to scale raw
I/O into engineering units used internally by the blockware. For the controller, scales
can be created in the toolbox and put into the database.
On many large processes, scales are defined in the System Information device. If a
scale needs to be edited, System Information eliminates having to know which
binary working files to open.
To insert a scale definition into a configuration
1. From the Outline View, select Scale definitions.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Scale definition dialog box
button and select Insert First. displays.
This dialog box is also used to edit existing scale definitions.
To edit a scale definition
1. From the Outline View, select the scale definition name.
Or double-click the scale 2. From the Edit menu, select Modify. The Scale definition dialog box
definition. displays.
Note Both scale and type definitions can be defined locally to a signal or pin and
display as -Custom- in the Signal Definition or Module Pin dialog list boxes.
These local definitions do not have names and do not display in the list boxes for
other signals. Also, they cannot be put into the database because they do not have a
name.
Enter the Minimum and Maximum

values of each system and Raw to
provide the conversion infromation.
Measurement System names

(in this case US and METRIC)
are defined in the System
Interface properties dialog,
under Measurement Systems.
Refer to Chapter 7, Create/
Modify System Information,
System Device dialog box.
Enter the Unit names for each

system (five-character limit).
Select the Precision from the
list boxes.
Enter a description of the

scale definition (50-
character limit)
Signal Definitions
Signal definitions are used to define signals associated with a Function or Macro and
Module Library.
To insert signal definitions into a configuration
1. From the Outline View, expand Functions or Macro and Module Libraries.
Click
Signal
Definitions
2. From the Edit menu, select Insert First. The Edit Signal Definition dialog
box displays. This dialog box is used to define the signal definition (refer to the
next section, Define Signal Definition).
To edit a signal definition
1. From the Outline View, click the signal definition name to highlight it.
Or double-click the signal 2. From the Edit menu, select Modify. Edit the signal from the Edit Signal
definition name. Definition dialog box.
For more information, refer to Signal definitions also display when you update the database. When you put signal
Chapter 11, Signals and the information into the database, three items, which hold lists of signals, are inserted
Database. under System Data (in the Outline View):
Define Signal Definition
Define the signal definition below.
Enter the name of the signal with at least one and up to three regions followed by a signal
name. Separate the region(s) and name with a backslash, such as reg1/ signal_name. The
Region can be six characters, maximum; the signal name can be 12 characters maximum.
Enter a descriptive Note below the name with up to 50 characters.
The signal description can be

in a second language. It is not
necessary to have a description
in both description fields. See
the section Create a Controller,
General Tab to edit a description
in both languages.
Type lists all the type

definitions and simple
types for this device.
From the dropdown list
select Custom to create
a locally defined data
type. Click Edit to add
the specific information
for that locally defined
data type.
Enter a scale definition
for this device. From the
dropdown list, select
Custom to create a
locally defined scale.
Click Edit... to view
predefined scales.
FALSE is the default, if

this is not a Control
Constant. Select TRUE
for signal definitions and
module pins that can be
viewed as a group and Connection allows you to Enter the length of the signal, Select these options to make the
exported to a .csv file. connect signal definitions to if it is an Array and the initial module pin a Hold, Event, I/O, or
Select READ to restrict other signals. Enter the name of Value for. the elements. If the Network. If the pin is connected
online changes to this the signal in the text box or click Array size is greater than to a Status_S signal and used in
.
module pin. Browse When one signal is one, a list box of the initial a task, that task is scheduled
connected to another, they share values for the array elements when the value of the signal
the same place in memory. displays above Value. changes, as well as the normally
scheduled execution times.
If a signal has the Network check box selected, then this signal is added to an EGD
Exchange under two circumstances: (See Chapter 9, EGD Interface, EGD
Exchanges, Internal Exchange Settings.)
From the Outline View, right-click an EGD Exchange and select Add Network
Signals. This adds all signals flagged as network signals (but not already connected)
to the Exchange.
Define an Exchange to Receive Network Signals, and then use the command Put to
database.
Note If a Function, or Library module is protected as View only, then a user at
privilege level 2 or above can modify some of the signal attributes. The available
attributes are listed in the Edit Module Pin section dealing with the Pin Override
feature.
Note The second language description is used for Turbine systems that use the
language translation feature of the Turbine Control Interface (TCI). Both
descriptions are stored in the SDB with the Put Into Database command. The TCI
Phrase Translation file is also updated. TCI uses this file to translate from language 1
to language 2 respectively.
Tuning Variables
A tuning variable is a special signal with high and low limits, which is used as a
constant. Initial values and run time changes are bound by the high and low limits.
Only float, lfloat, int, and lint

signals can be a tuning
variable.
The high and low limits apply to setting Select this option to name this signal a
the initial value of a signal and also when tuning variable. If the Tuning Variable
making online changes to the value of a checkbox is not checked, then the high
signal in a controller. and low limits for initial value will not be
displayed.
Note You must be at privilege level 4 to make a signal a tuning variable and set the
initial value limits.
For tuning variables that are defined to be arrays, high and low limits can be defined
for each element in the array. In the example below, the second element has a low
limit of 90 and a high limit of 200 (with an initial value of 100). The first or third
elements can have totally different high and low limits and a different initial value.
The summary screen for the tuning variable test\tune1 shows (see below) the
different initial values and the tuning high limit for each element in the array.
Alarm Tab
The Alarm tab is illustrated below.
Check to make the

Alarm a signal (only
available with a
Boolean signal).
The Alarm Class

dropdown lists all
available alarm
classes. You must
first use the
command, Get from
Database. PRC is
the default.
To select an alarm in
CIMPLICITY, enter
the full path or the
file name (256-
character limit) in
CIMPLICITY Screen
or click Browse... .
Limits Tab
Note The Limits tab is only available for turbine projects (including Mark VI,
EX2100, Static Starter, and ISC in a turbine device). For ISC devices, refer to the
section, General Tab.)
Setpoint Limits are used in CIMPLICITY to limit

the maximum and minimum values that can be
set for that signal in a CIMPLICITY screen.
Display Limits are

defined in the Scale
definition as the
Native System
maximum and
minimum. You can
override the Scale
definition display
limits by enabling the
Signal display limits
and entering new
limits in the Signal.
Click to select and

set the Deadband
value.
Note All values entered are in the signals

Measurement System.
Table Definitions
A lookup table is a reference Many complex mechanical issues can be modeled using lookup tables. The
table that maps an index or controller implements these tables using table definitions. A table definition is
key to a value to be looked up presented like a signal definition in that it is named in the same way and is used in
and returned. It is often used instruction blocks. However, table definitions have other characteristics as required
as an alternative to lengthy by the Control Specifications from GE Aircraft Engines for LM Turbine
runtime calculations. Applications for the Mark VI, and can be used by the Innovation Series Controller.
A table definition consists of a name, note, identification string, revision string,
engineering units, data array dimensions, adjust flag, minimum and maximum Z
values, and data. The data consists of one or two independent arrays (X and Y) and a
dependent array (Z).
Tables with a single independent array are sometimes called univariate tables and
consist of X and Z linear arrays of the same length. Univariate table block pins have
a data-type of UniTable_F. Tables with two independent arrays are sometimes called
bivariate tables and consist of X and Y linear arrays and a Z two-dimensional array.
Bivariate table block pins have a data-type of BiTable_F. Bivariate table definitions
display in the Summary View as follows:
The leftmost column

contains the X (down) array
values.
The top row contains the Y

array values.
The remainder of the cells

are Z array values.
The Z values are arranged
such that the intersection of
the X and Y values give the
corresponding Z value.
Table definitions
are part of the
item Functions.
They can only be

inserted into the
configuration by
importing a table
definition .tre file.
This .tre file is
usually included in
the configuration.
Import Files
To import files
1. From the Outline View, select Table Definitions, then right-click the table
definition name.
2. From the pop-up menu, select Import Table Tree File.
Table definitions can export contents to a comma-separated variable (.csv) file.

These files can then be merged back into the controller configuration.
To export or merge a table definition .CSV file
1. From the Outline View, use the right-mouse button to select the name of the
Table Definition to be exported.
2. From the pop-up menu, select either Export Table .CSV File or Merge
Table .CSV File.
3. Select or enter the .csv file name. The default file name displays, based on the
tables name of the form region_region_region_signalname.csv.
Edit Table Definition

Once a table definition exists, it can be edited. The Table Definition Edit dialog
box consists of a Properties tab and an Initial Values tab. If the controller is online,
an additional Live Data tab displays in front of the Properties tab. The tab displays
live values that can be modified and downloaded.
To edit a table definition
1. From the Outline View, select the table definition name.
Or click the right-mouse 2. From the Edit menu, select Modify. The Table Definition Edit dialog box
button and select Modify. displays (Refer to the next two sections, Properties Tab and Initial Values Tab).
Properties Tab
Define table properties below.
The name of the table displays

automatically and cannot be edited.
It is also used on block pins to which
this table definition is connected.
This is the name of the tree file that

this table definition came from, if it
was not part of a function .tre file.
This field is also modified as a result
of exporting the table definition to a
separate .tre file.
Enter a description of the table

definition.
Enter a free form text identifier.
Enter a free form text revision

number or date.
Enter a free form text describing the

engineering units of the X, Y and Z
data values.
Enter the minimum and maximum for the Z data values. These
Click OK to save
values are used by the toolbox to limit the values that can be
the changes.
entered into the live or initial values. The values are used by
the controller runtime software to limit the output of blocks that
use these Z values.
Initial Values Tab
The Initial Values tab contains all the initial values for the table definition. The cells
are arranged in a table format (as in the Summary View). Edit the values as follows:
Click on the cell to edit in

the table.
To navigate through the

table, click on a cell and
press <Tab> to go right,
<Shift><Tab> to move
left . Press the up and
down arrow keys to move
up and down in the cells.
Live Data Tab
The Live Data tab is illustrated below.
Click on the cell to edit.

To navigate through the
table, click on a cell and
press <Tab> to go right,
<Shift><Tab> to move left.
Press the up and down
arrow keys to move up and
down in the cells.
Click to save the values to

the configuration.
Click to update the Live

values grid with the current
value in the controller.
Click OK to save changes

to the configuration. Save
to Initial Value must be
clicked also.
Click Cancel to undo
changes made to
properties and values.
Download and Save to
Initial Values are not
canceled.
Click to download the modified values to the controller.
Module Definitions and Modules
Module Definitions and Modules are items in the hierarchy that can be used to divide
blockware; they can also be used to reuse blockware.
Instanced and over-ride

modules are defined under
Module Definitions.
Inline modules are defined

under Modules.
Insert Module Definitions and Modules

When a Module is inserted, the type must be specified as defined or inline. Defined
types are existing Module Definitions and inline modules are determined later.
Module definitions are reusable and have a revision number to keep track of changes
to the modules.
Both configuration items are inserted by using the same procedure. When both are
inserted, they contain another level item called Pins (refer to the section, Module
Pins). At this level, you can insert all of the Tasks for the Module Definition or
Module (refer to the section, Tasks).
To insert a module definition or module into a configuration
1. From the Outline View, select Module Definitions (found under the item
Functions or Macro and Module Libraries) or Modules (found under the item
Functions).
Or click the right-mouse 2. From the Edit menu, select Insert First. The Module Definition Name or
button and select Insert First. New Module dialog box displays (refer to the sections Name Module
Definition or Name Module).
Name Module Definition
Define the module name below.
Enter a name for the item you are

inserting. Click OK.
The name displays under the item

you are inserting in the Outline View.
Name Module
The New Module dialog box is illustrated below.
Select an existing
module definition.
Enter a note for
the module.
Check Inline to
insert an empty
inline module and
Enter a name with up define it later.
to three regions
separated by
backslashes. (The
pins, inserted un the
item Pins, use this
same region as a full
name.)
Edit Module Definitions and Modules
Once a module is inserted, it can be edited. The same dialog box is used for a module
definition or module.
To edit a module definition or module
1. From the Outline View, select the name of the module or module definition.
2. From the Edit menu, select Modify. The Edit Module or Edit Module
Or double-click the name with Definition dialog box displays. The appropriate fileds for the particular module
the right-mouse button. type are enabled (refer to the next section, Edit Module Definition or Module
Dialog Box).
Select a module (such as HMI_1) and turn on

Tracking. The Summary View contains the
name and scheduling of the selected module
and a scrolling list of the tasks in the module.
When the toolbox is online

and communicating to the
controller, the text in the task
list turns green and the
online Heartbeat and Enable
Value display in the column.
Edit Module Definition or Module Dialog Box
The Edit Module dialog box is illustrated below.
Check to change an instanced module to an over -ride module. An instanced

module has a colon ( : ) between the region names, such as reg \reg:module.
The over-ride module has an at symbol @, such as reg\reg@module. The
Over-ride checkbox can toggle to change an edited module definition back
to the original. Remove the X and perform an instance. Any custom changes Definition Revision records
made to the module when it was overridden are deleted. the revision of this module's
definition which resides in the
Module and Macro Library.
Module Revision
tracks changes to this
module. The form of
the revision must be
V##.##.##A, where ## is at least
two decimal digits and the final A
can be any alphabetic character.
If the format entered is incorrect,
the toolbox replaces the revision
string with V??.??.???.
Click this button to uncheck the Pin
Override enable checkbox on all
pins under this module. Overridden
pin data is lost unless the module
itself is over-ridden. See the Edit
Module Pin section for details on
the Pin Override feature.
Select the module scheduling
base period. The associated
over-ride check box is only
enabled for instanced modules.
Check this box to make the fields
behave like the connection of a
module pin (the information of
the module instance is not
replaced when it is re-instanced).
Select the module scheduling
base skew. The associated Over-
ride check box is enabled only
when the module is instanced.
Enter a name for the Graphic Enter a name for the Help file
Window or Windows metafile associated with this module.
, module. Enter a description
associated with this Select the module definition or of the module.
This is accessed by selecting instance in the outlineand then
a module in the Outline click Item Help from the right-
View, then selecting the click pop-up menu to display the
Detached Summary View. Help file entered here.
Module Pins
Module pins are parameters for a module. They are inserted under the item Pins.
(Pins are automatically created when the item Module is inserted.)
To insert a pin into a Module
1. From the Outline View, under the item Modules or Module Definitions, click
beside a module to display the item Pins.
2. Select Pins.
Or click the right-mouse 3. From the Edit menu, select Insert First. The Module Pin Name dialog box
The Module Pin Name dialog box is illustrated below.
Enter a name for the item you are inserting.

The name must begin with an alphabetic
character and contain a maximum of 12
characters. Click OK.
The name displays under the item you are

inserting in the Outline View.
Edit Module Pin
To modify a module pin
1. From the Outline View, select the module pin.
Or double-click the name with 2. From the Edit menu, select Modify. The Edit Module Pin dialog box
the right-mouse button. displays.
Note For instanced pins, only the field, Connection is active.
Refer to the section, Module This dialog box is used to edit both the Module and Macro Pins. Inserting and editing
Definitions and Modules. module pins is limited to module definitions, inline modules, and override modules.
Module pins are referenced in the modules blockware using only the pin name. By
maintaining the use of this name exclusively, the modules can be re-used. This same
method is used to make macro definitions re-usable.
This check box is enabled for pins that are in aninstanced
module. When checked, certain attributes of the instanced pin
can be modified. The modifications will be retained even after
re-instancing the module.
Enter a name with up to 12

characters (must begin
with an alphabet character).
Module pin names do not
include regions. The
regions for signals
associated with module
pins have the same region
as the module. The text
box below the name allows
you to enter up to 50
characters to describe the
pin.
FALSE is the default value.

Select TRUE for signal
definitions and module pins
that can be viewed as a
group and exported to a
.csv file. Select READ to
restrict online changes to
this module pin (although it
is still viewed as a normal
control constant).
Select this box to

mark the pin as a
DLAN+ event.
Enter the connection Select these options to make the module pin a Hold, Event point. If the pin
path for the pin. is connected to a signal and used in a task, then that task is scheduled to
run when the value of the signal changes, as well as at the scheduled run
times. The pin can also be checked to show that it is an I/O, Network
(EGD), Tuning Variable, or Virtual HMI Point.
Override Enable check box
The Override Enable check box is enabled for pins that are in an instanced module.
When selected, certain attributes of the instanced pin can be modified. The
modifications will be retained even after re-instancing the module. The Override
Enable check box is enabled, and retains its state, even if the module is overridden
(at the module level). The attributes that can be modified are listed below:
Module pin tab
Override Enabled and checked
Pin Note (description)
Scale
DLAN+ Event checkbox
Hold, Event check box (Boolean only)
I/O, Network, Virtual HMI point check box
Value
Connection
Alarm tab (Booleans only):
Alarm check box
Alarm class (when alarm checkbox is checked)
CIMPLICITY screen (when alarm checkbox is checked)
Limits tab (non Booleans only):
Display Limits enable and values
Set point Limits enables and values
Dead band enable and values
The following attributes are not enabled
Name
Type
Array Size
Tuning Variable
Control Constant
If the Override enable checkbox is unchecked, then the pin attributes will revert to
the values from the library definition. An Undo Pin Override button is available in
the module edit dialog to remove the pin override for all pins under the module.
Note If a function, or library module is protected as View only, then a user at

privilege level 2 or above can modify the same pin attributes that are available with
the Pin Override feature. This is also true of Signal definitions. It is NOT true for
Macro pins or module pins under a Library.
Alarm Tab
Check to make the

available with a
Boolean signal).
The Alarm Class

dropdown lists all
available alarm
classes. You must
first use the
command, Get from
Database. PRC is
the default.
CIMPLICITY, enter
file name (256-
character limit) in
CIMPLICITY Screen
Limits Tab
The Limits tab is shown below.
Display Limitsare
defined in the scale
definition as the
Native System
maximum and
minimum. You can
override the scale
definition display
signal display limits
and entering new
limits in the signal.
Click to select and

set the Deadband
value.
Note All values entered are in the signal's native Measurement System.
Macro Definitions
Macros provide a way to re-use blockware on a lower level than modules. Macros
are only instanced and never inline or override. Therefore, all macros must be
inserted under the item Macro Definitions to be used in blockware.
To insert a macro
1. From the Outline View, select Macro Definitions.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Macro Definitions Name
button and select Insert First. dialog box displays.


Edit Macro Definition
To edit a macro definition
1. From the Outline View, select the macro definition name.
2. From the Edit menu, select Modify. The Edit Macro Definition dialog box
displays.
Revision allows you to keep track of changes to the macro definition. The
form of the revision must be V##.##.##A, where ## is at least two decimal
digits and the final A can be any alphabetic character. If the format is
entered incorrect, the toolbox replaces the revision string with V??.??.???.
Edit the name that was created
in the MacroDef Name dialog
box. It must not have more than
12 characters.
Enter the name of the pin that
enables the macro or select
from a list of defined pins in the
drop-down list box.
Enter the name of the Windows

Metafile associated with this
macro. This is accessed by
selecting a macro in the Outline
View and then selecting the
Detached Summary View.
Enter a name for the help file

associated with this macro or
click Browse to search.
Selecting the macro definition
or instance in the Outline
View and then clicking Item
Help in the right-click pop-up Displays the default access level of this macro.
menu displays the same help Use - you can use this macro in code, but not view or change it
file entered here. View - you can use this macro as well as view its contents
Change - you have total access to this macro
Macro Pins
Macro pins are the parameters for a macro. They are inserted under the item Pins.
(Pins are automatically created when the item Macro is inserted.)
To insert a pin into a Macro
1. From the Outline View, under the item Macro Definitions, click
beside a module to display the item Pins.
2. Select Pins.
Or click the right-mouse 3. From the Edit menu, select Insert First. The Macro Pin Name dialog box
The Macro Pin Name dialog box is illustrated below.


Edit Macro Pin
To edit a macro pin
Or double-click the name with 1. From the Outline View, select the macro pin.
the right-mouse button.
2. From the Edit menu, select Modify. The Edit Macro Pin dialog box displays.
Note For instanced pins, only the Connection field is active.
Change the name created in the Macro Pin Name dialog box. It
can be up to seven characters long and must begin with an
alphabetic character. Macro pins are not named with regions
included. The text box below the name allows you to enter up to
50 characters to describe the pin.
Note: Sometimes this text box is used by HMI to describe
diagnostic messages.
Select from a list of data types,
made up from all of the type
definitions and basic types for this
controller. To create a locally
defined data type, select Custom
from the drop-down list. Then click
Edit... to add the specific
information for that locally defined
data type.
Select how the pin is used in the

macro: Input, Output, Local (not
intended to be used outside of this
module), Const, and State (read
and write). Usage is not verified
during validation. Usage also
indicates if the pin displays on the
left or right of the macro block. An
Input or Const display on the left of
the macro block; Local, Output, or
State display on the right.
Visibility specifies the conditions

under which the pins are viewed on
block diagrams. Always (pin is
always displayed), Never (pin is
never displayed), Used (pin is Array size and Value define the arry length Enter the name of the signal that
displayed when connected to of the signal (if it is an array) and the initial the pin will be connected to, or
anything), or Wired (pin is value for the elements. If the array length click Browse... to select from
displayed only if connected to is greater than one, a list box of the initial the Signal Selector dialog box.
another signal. This option is not values for the array elements displays
always applicable (see the Option above the Value list box. To edit this box,
menu, Block Diagram.) click on a value in the box, then enter a
value in the Value list box or select from
the drop-down list.
For more information, refer Note For Used and Wired pins, if just a macro instance is selected in the Outline
to the section, Macros, Macro View with tracking on, the Summary View displays all pins regardless of their
Definitions, and Macro Pins. visibility status.
Tasks
Refer to the section, Tasks Tasks are both the basic scheduling unit and a blockware grouping mechanism in the
and Scheduling. controller. Tasks are inserted into modules and can be modified.
To insert a task into a Module
1. From the Outline View, under the item Modules or Module Definitions,
select a module name.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Task Name dialog box
The Task Name dialog box is illustrated below.


Edit Task
To edit a task
1. From the Outline View, select the task name.
Or double-click the right-mouse 2. From the Edit menu, select Modify. The Edit Task dialog box displays.
button.
Enter a unique name of up to

12 characters.
Enter the task description.
Change the execution time

slice that this task executes.
This can distribute the
execution of different tasks,
so that overruns do not
occur. The possible values in
the drop-down box depend
on the value selected as the
Period Mult.
Period Mult determines how
often a task runs. The period
multiplier times the module's
period equals the period that
this task executes. This is
Event 1,2,4, or 8. (Event
generates a multiplier of zero Enable option buttons allow selection of a value for the task enable.
and the task only runs if an
Event occurs.) Always makes the enable True.
Never makes the enable False.
Pin enables the drop-down list box to select the names of this
module's pins.
Signal changes the drop-downlist box to display the signal.
Selector dialog box selects a signal.
Tip When either Pin or Signal is selected in the Enable options, a module pin or
signal name can also be typed in.
Enable or Disable Task
Do not enable/disable application code tasks unless you have a

complete understanding of the consequences.
The following screen displays tasks in the Outline View. With Tracking on, it shows
how the tasks can be displayed in the Summary View.
Module, HMI_1
Tasks, SigGen and

geni
Click on the Module
Click on the Task name, such as
name (SigGen) to HMI_1 to display
display its position in Task information in
the block diagram the Summary View.
(Summary View)
To enable or disable a task
Or click 1. If not already online, go online. From the Device menu, select Online.
2. The Go Online dialog box displays.
3. From the Outline View, double-click the task name. The Send Value dialog
displays.
Enter the Value to

enable or disable
the task.
Select this box to

prevent blockware
from overwriting
the Value.
Toggle Value inverts the current

value and sends it to the controller
without closing the dialog box.
Blocks and Macros
Blocks are the basic programming construct for blockware. Macros can group blocks
so that they look like a single block. Once a macro is defined, blocks and macros are
connected similarly to make tasks or other macros. The following sections describe
how block and macros can be connected to create functional controller software.
Insert and Delete
The hierarchy for block and macros can be seen in the Outline View shown below.
Macro
Task
Block
Macro
A macro in the item Macro Definitions displays as mac2. When the macro is
inserted in a task or another macro, it displays as a block because the name is
preceded with a block number and a colon (40:mac2). The pins display directly
under the macro name in its instanced form, instead of under the item Pins under the
macro name. Also, the item Blocks displays on the same level but below the
instanced macro items. Only one block or macro can be inserted at a time.
To insert a block or macro into a task
1. From the Outline View, select a task name.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Select Block Type dialog box
3. From the list, Category, select a block category, then select a block from the
block library. (The center text block displays either the Library or the Function
This process does not apply to name.) Or, from the list Macros, select a macro.
modules that are instanced.
4. Click OK or double-click the block/macro. The item is inserted under Task
name.
To delete a block or macro from a configuration
1. From the Outline View, select the desired item.
Or click 2. From the Edit menu, select Delete. Or, press the Delete key.
Note Blocks or macros that cannot be deleted (those that belong to either a macro or
an instanced module) disable the delete commands when they are selected in the
Outline View.
Select Block Type
The Select Block Type dialog box is illustrated below.
Macros list box is selected in the same way as

the Block categories.
This number identifies the block

within the task or module, which
it is being inserted into. The
number can be modified as long
as it is greater than the previous
block and less than 89999.
This list displays the standard or

industry block library, which are
grouped into similar functions.
Select one or more categories
and the list box on the right
changes to display all the blocks
in that category(s).
The All button displays all the
blocks. The None button displays
none of the blocks.
The blocks that display in this list

box can be inserted into the task.
Select the block and click OK or
double-click the name of the
desired block.
Note is a read-only field, which displays a description of the block or
macro selected. Scroll it by clicking the box so that the cursor
displays in the note text, then use the Page Up/Page Down or arrow keys.
Rubber Blocks
When a block in inserted, all the block pins are included. The exceptions are blocks
with a variable number of pins, known as rubber blocks, which insert only the first
set of pins. The block pins that are active only when they display are called rubber
pins. These blocks are handled differently because their functions can act on a
number of sets of pins, depending on how many pins are present. By showing only
the active pins, the diagrams are less cluttered and both the toolbox and runtime
require less memory.
An example of a rubber block with rubber pins is the _BENG block, which is a relay
ladder diagram (RLD). The RLD can have from one to 16 different signals used in
the ladder. The block is a rubber block because it can stretch from using only one
input to using up to 16 inputs.
Connect Pin
For more information, refer To connect the pins of a block or macro, use the Connect Block Pin dialog box or
to the section, RLD Editor. the Edit Block/Macro Connections dialog box. Boolean engine blocks can also
be connected using the RLD editor, which is the default for Boolean engine blocks.
To connect/edit a pin
1. From the Outline View, select a block or macro. The block diagram displays in
the Summary View.
2. From the Summary View, double-click the desired pin. The Connect Block
Pin dialog box displays.
From displays the selected block number and pin

the Type, and the Usage of the pin being
Enter the value this block or

instanced macro pin will be
connected to.
The following command

select the pin connection. (The
Pin buttons all display thePin Select
dialog box, described below.)
Signal displays the Signal

Selector dialog box to select a fully
qualified signal.
Module Pin is only enabled when editing
a task in a Module or Module
The name is a pin name only, so the
signal name uses the module region
its region.
Macro Pin is only enabled when editing
a macro definition. It lists macro pins, which can be connected to this
Block Pin is always enabled. This command provides a list of all
possible block pins that are on the same level of blockware (either in
same task or macro definition). The names display as block
colon, pin name (100:IN).
Inv places a tilde (~) in front of the pin. A ~ placed before any
inverts the signal for the connection being made. This command is
enabled for Boolean pins.
Create Pin allows you to create a macro or module pin that is not in
Pin Select list. It invokes the Edit Module Pin Definition dialog box with
name and type preset to the values matching the current pin
connected. Clicking OK in Edit Module Pin Definition creates a module
if the block/macro pin is in a Task or creates a macro pin if the
macro pin is in a Macro
The drop down list provides enumerated data types (including
variables). Inserting an enumeration in the To text box gives the pin
initial value. Initial values can also be connected to block and macro
by entering a valid numerical value for pins with a simple numerical
type or type definitions based on a numerical data
Edit Block Connections
The Edit Block and Edit Macro Connections dialog box allow you to edit and
connect block and instanced macro pins for the entire block or macro. The dialog
box accepts inputs on a pin-by-pin basis. This means that once you enter the
connection text and either press Enter or select another pin, the text is applied to the
pin.
To edit all pins in a block or macro
1. From the Outline View, select the block or macro pin. The block diagram
displays in the Summary View.
2. From the Summary View, double-click the desired pin. The Edit Block
Connections (or Macro Connections) dialog box displays.
This is a list of all the pins of the block
being edited. Click on the pin to be This is the instance name Enter a description for every
connected/edited. The Pin name of the block or macro. instance of the block.
displays in the read only box below the
pin names.
This text box allows you to enter the

pin to connect. The command buttons
can also be used to select the pin.
Or, when a single pin is selected for
connecting, it displays in the text box
below the Connection list box. Based
on the pin type, specific help is then
displayed beneath the text box. For
example, for the equation (EQUAT)
pin on a Math block, the help lists all
the mathematical operations that can
be performed, such as +, -, *, / ABS,
or SQR. Also, the drop-down list in the
bottom right-hand corner displays the
required data type for that pin, such
as Float or Boolean.
Signal displays the Signal Selector

dialog box to select a fully qualified
signal.
Module Pin is only enabled when
editing a task in a Module or Module
Definition. The name is a pin name
only, so the full signal name uses the
module region as its region.
Macro Pin is only enabled when editing a macro Block Pin is always enabled. This command
definition. It lists macro pins, which can be provides a list of all the possible block pins that are
connected to this pin. on the same level of blockware (either in the same
Create Pin allows you to create a macro or task or macro definition). The names display as
module pin that is not in the Pin Select list. It block number, colon, pin name (100:IN).
invokes the Edit Module Pin Definition dialog Inv places a tilde (~) in front of the pin. A ~ placed
box with the name and type preset to the values before any signal, inverts the signal for the
matching the current pin being connected. connection being made. This command is only
Clicking OK in Edit Module Pin Definition creates enabled for Boolean pins.
a module pin if the block/macro pin is in a Task
or creates a macro pin if the block/macro pin is in
a Macro Definition.
Relay Ladder Diagram
From the Options menu, select Boolean engine blocks can be connected differently than other blocks and macros.
Settings and click the option, Use These blocks perform logical operations on inputs to set the output to some value.
RLD editor. The operation is determined by a Boolean equation, which uses symbolic pin names
as operants. The Relay Ladder Diagram (RLD) editor transforms the Boolean
equation into a relay ladder diagram, where symbolic relay contacts are arranged so
that power flows to the symbolic output coil on the right from the power bus on the
left when the relay contacts in between make a complete connection.
Arranging the contacts on the drawing area using the mouse creates Boolean
equations. Select a drawing mode and place the elements on the grid by clicking the
mouse in that square. Contacts connected horizontally are logically ANDed and
those line connected vertically are logically ORed. The names of signals or pins are
connected with contacts in either select mode or one of the contact modes by double-
clicking the contact or coil that receives a name.
RLD Editor
To connect a block using the RLD editor
1. From the Summary View, select a Boolean block (titled BENG or BENG_D).
Or double-click the block 2. From the Edit menu, select Modify. The RLD editor displays.
name.
RLD Editor Toolbar Commands
Click To
Start the edit mode, where contacts can be moved, copied, and deleted.
Select a square, place the cursor over a grid square and click the left mouse button.
Connect a contact to a signal or pin, double-click a contact. The Connect Contact dialog box
displays.
Move a contact, click the contact and drag-and-drop to the desired grid square.
Copy a contact, press and hold the Ctrl key, click the contact, and drag and drop to the desired
grid square.
Delete a contact or line segment, click a grid square and press Delete.
Start the drop mode, where a normally open contact can be dropped onto the grid square.
Connect a contact to a signal or pin, double-click a contact. The Connect Contact dialog box
displays.
Start the drop mode where a normally closed contact can be dropped onto the grid square.
Connect contacts, where as the cursor moves through the grid area, a green tracer segment
indicates where a line segment can be added. A red tracer segment indicates where a line
segment or a contact can be deleted (contacts cannot be moved or copied in this mode).
Validate and compress the RLD. Errors are identified with row and column numbers in the grid
square(s).
Insert a row at the currently selected grid square.
Insert a column at the currently selected grid square.
Select a pin and edit the note and connect any non-RLD related pins. This button displays the
Edit Block Connections dialog box.
Tip The drop-down list RLD Size provides different font sizes that enlarge or
reduce the RLD editor Work Area. If the Work Area is larger than the RLD window,
scroll bars display to access and view the entire workspace.
Renumber and Rename, using Window Methods

To maximize productivity, the Starting at the bottom of the controller hierarchy, blocks and macro instances can be
toolbox uses many standard cut-and-pasted whenever it is possible to insert one or the other. The number
Windows methods, such as associated with each block or macro is automatically applied by the toolbox. The
cut-and-paste or drag-and- default increment (Step by:) is 10 for blocks or macros pasted at the end of a task.
drop. However, when a block or macro is pasted between two existing blocks or macros, it
is assigned a number halfway between the numbers of the two existing blocks or
macros. Blocks in a task or macro definition can also be renumbered in groups.
Renumber
Instanced blocks cannot be To renumber a block(s)
renumbered.
1. From the Outline View, select a block, or select a group of blocks by pressing
and holding the Shift key as you select the block names.
2. From the Edit menu, select Renumber. The Renumber Block(s) dialog box
displays.
Enter a new starting

number for the block
or block group. Enter the difference
between the new block(s)
numbers. For example,
Click OK. Start at 40 and Step by 10,
produces the numbers 40,
50, 60, and so on.
Note If the new numbers overlap with existing blocks, a dialog box displays to state
the overlap.
Rename and Copy Blocks

Tasks, modules, and macro and module definitions can be cut and pasted. If a name
is repeated, the Rename Module Region dialog box (shown below) displays to
allow you to give the item a different name. This happens most often when one of
these items is copied to the same name space, such as when a module is copied to the
same controller or when a task is copied in the same module.
Pins can be effectively copied from one module to a module of a different type or
from macro definition to macro definition. Currently, there is no way to transfer a
macro pin to a module or the reverse.
Another useful method using cut-and-paste is when two different controllers are
opened in the same toolbox. The blockware items can be moved or copied from one
controller to another. This makes moving entire functions very easy.
Also, portions of the blockware can be cut and pasted in a text editor, such as
Notepad using the Windows paste buffer. The text can be modified using the editor
and pasted back into the blockware (assuming none of the import rules are broken).
Block Flow Diagram
The block flow diagram displays the links that connect blocks and macros in a task, a
macro definition, and the block level of a macro instance. The diagram is viewed in
the Summary View (and also in the Detached Summary View, a stand-alone version
shown below). Block connections and editing can be performed from both views.
The block diagram has several viewing options.
Refer to the section Using the To select block flow diagram viewing options
Toolbox.
From the Options menu, select Settings, then select the Block Diagram
tab. These settings determine how the blocks display in the Summary View.
Edit the display or connect blocks from this view as follows:
To From the Block Flow Diagram

Display the RLD editor Double-click the Boolean engine block name.
Display the Edit Block Connection dialog box Double-click the block or macro name.
Display the Connect Block Pin dialog box for that pin Double-click the pin of a block.
Highlight the connection of a pin to another pin Click the pin itself or the area adjacent to the pin name reserved
for the pin connection.
Connect a module pin already connected to a block pin Click the module pin, drag-and-drop it on the pin to connect it to.
Modify a live value With the controller online, double-click the green value next to
the pin.
Tip Instead of using the Connect Block Pin dialog box, click a pin inside the
block work area. Drag-and-drop the pin onto the pin of another block.
Instance Module and Macro
Both macros and modules can To instance a single macro or module
be used to substitute specific
1. From the Outline View, select the macro or module.
portions of blockware at
instance time (refer to the 2. From the Edit menu, select Instance.
next section, String
3. Select Selected to instance a single item.
Substitution).
Or, select All to instance the entire controller (every instanced macro and module
will be updated).
Module pins are intended as parameters to the module. However, a local pin can be
used to share data between tasks in the macro. Module pins can be connected to
external signals through the Edit Module Pin dialog box. The connections owned
by the module pin are kept intact when a module is instanced. In this way, a module
can be updated with a new module definition and not lose the connections.
Connecting instanced macro pins To edit the connection of a module pin
is described in the section,
From the Outline View, double-click the module pin name. The Edit Module
Blocks and Macros under
Pin dialog box displays.
Connect and Edit.
Enter a Name (12-

character limit, initial
character: alphabetic).
Module pin names do
not include regions. The
regions for signals
associated with module
pins have the same
region as the module.
Enter a description (up

to 50 characters) of the
pin.
FALSE is the default

value. Select TRUE for
signal definitions and
module pins that can be
viewed as a group and
exported to a .csv file.
Select READ to restrict
online changes to this
module pin (althought it
is still viewed as a
normal control constant).
Select this box to Enter the Select these options to make the module pin a Hold,
mark the pin as a connection an Event, an I/O, or a Network. If the pin is connected
DLAN+ event. path for the to a Status_S signal and used in a task, that task is
pin. scheduled when the value of the signal changes, as
well as at the normally scheduled run times.
Alarm Tab
Check to make the

available with a
Boolean signal).
The Alarm Class

dropdown lists all
available alarm
classes. You must
first use the
command, Get from
Database. PRC is
the default.
CIMPLICITY, enter
file name (256-
character limit) in
CIMPLICITY Screen
Limits Tab
The Limits tab is shown below.
Display Limitsare
defined in the scale
definition as the
Native System
maximum and
minimum. You can
override the scale
definition display
signal display limits
and entering new
limits in the signal.
Click to select and

set the Deadband
value.
Note All values entered are in the signal's native Measurement System.
String Substitution
Portions of blockware in macro or module instances that cannot be affected through
macro and module pin connections can be changed using string substitutions. Also,
even if the macro or module pins affect the blockware, string substitutions might be
used within the pin connections. For example, a particular module may always
interface to a single drive. The pins of the module are consistently connected to
signals of the drive that all have the same region. In the module definition, a string
substitution can be made, so that the drives region is only specified once and the
pins are connected properly for every instance.
String substitution allows you to substitute strings in blockware or pin connections
for standardization. Specify macro or module pins used exclusively for substitution.
Then special characters, such as %0 or %9 or ^ are put in the blockware or other pin
connections. When the macro or module is inserted, the special characters are
replaced with the substitution text.
Special pins in the macro and module definitions, which receive substitutions,
indicate string substitutions. The data type of these pins is StrSub. The pin names
display as Subn, where n = 0 through 9 or ^. Default values for the substitutions are
entered in the field Value of the Edit Module Pin dialog box and hold the actual
substituted values for module or macro instances.
In the main part of the module definition, sub-strings to be substituted are keyed with
a %n where n = 0 through 9 or ^. Substitutions are most commonly made in the pin
connections to the macro or module with the substitution or connections of the
constituent blocks. Substitutions can also be made in notes or names like macros or
scales, although the normal rules of validation must not be broken.
Note When substitutions occur in the pin connections of the macro or module
definition, the pins must be disconnected at the inserted macro or module; otherwise,
the substitutions, as they are defined in the connections to the definition pins, will
not occur. This is because of the rule that all connections to macros and modules
must be respected. This also allows you to change these particular connections and
override them at the instance, if necessary.
In some cases, only a single character is used in the code to be replaced. A special
pin called Sub^ is provided. This pin works like the others, except only the ^ is
required in the definition blockware without the leading %. This allows code to still
follow the validation rules even though it has the string substitution special character
in it. For example, Stand1\speed is a valid signal name. Stand%4\speed is not valid
since the region can only have six characters.
String Substitution Connection Dialog Box

When a pin is inserted, it is scanned for substitute pins. If the SubStr pins are not
connected, you are prompted for the initial connections to be made to the
substitution. The String Substitution Connection dialog box displays for each
substitution pin with the definition pins initial value as a default.
Enter the initial substitution values that are applied as the module or macro is
inserted. To change the values that are substituted, reconnect the substitution pin and
instance the module or macro again. The result is shown in the following screen.
Device Menu Commands
This section describes the following Device menu commands:
Put Into Database and Get From Database let controllers share signals with
other controllers on the network.
Validate confirms that a configuration is ready to build Pcode.
Build creates a Pcode, a symbol table file, and a compressed Mark VI file for
the configuration.
Download sends configuration components to the controller.
Database Commands
For more information, refer to Put Into Database writes signal and topology information to the database. Get
Chapter 11, Signals and the From Database reads other controllers information from the database and
Database. includes it in the controller configuration. Both commands can be performed as Full
or Incremental. The toolbox must also put diagnostic symbol information into the
database for other controllers in the system.
To Put Into Database or Get From Database
If this command is not 1. From the Device menu, select either Put Into Database or Get From
available, verify the database Database.
and server name entered in
2. Select Full to include all information or Incremental for specific information.
the Database options dialog
box (refer to the section, The Put Into Database and Get From Database commands allow controllers to
Using the Toolbox). share signals with other controllers and drives on the network. For example, a RUN
signal from a controller can be used to tell an AcDcEx2000 to run. The controller
creates and puts the signal into the system database. The AcDcEx2000 gets the
signal information from the database for that signal. When the controller issues the
RUN command, the AcDcEx2000 sees the signal on its page and takes the
appropriate action. The following table defines what information can be changed in
either the controller or the database by these commands.
Innovations Series Controller Database Interface
Information Get from Database Put into database Put Topology into Put Symbols
without Topology Database into
(USDB only) Database
DLAN+ Signals yes yes yes N/A
Ethernet Signals no N/A yes N/A
Signal Symbols no no no yes
Device Name no no yes N/A
Device Number yes no yes (assigns if = 0) N/A
Network Name yes no yes N/A

Network Number yes no yes (assigns if = 0) N/A
Scales yes yes yes N/A

System data type yes no no N/A
definitions
Validate
Validate confirms that a configuration is ready to build Pcode. Validation status
displays in the Outline View by the color of the text. Valid items are in black text
and invalid items are in red text. When an item is invalid, the item that owns the
invalid item is also in red text. This status expands up each level, so that the
drive/controller (name) item of an invalid configuration is always red.
In the controller, validating checks connection compatibility, data types, equations,
hardware, and such, which must be correct to build and download a controller.
To validate an item
1. From the Outline View, select an item(s).
Or click 2. From the Device menu, select Validate.
3. Select either All to validate the entire drive/controller or Selected to validate
the highlighted item and all items in the levels below.
If an error(s) is found, it displays in the Log View located below the Outline View.
Double-click an error to go to the item in the configuration that was not validated.
Build Pcode and Symbols

When a controller item is valid, a Pcode file (.pcd) and symbol table file (.sym) can
be built (created). Both are built by the toolbox and can be downloaded to the
controller to change the configuration.
A symbol table is required to place signal information in block diagnostic messages
for the OC2000 and MM2000. This table consists of a list of the signal names with
the address token and a description. This is the same information that goes into the
database when putting diagnostic information into the database, excluding block
notes for the diagnostic detail.
To build Pcode for a controller
Or click From the Device menu, select Build. The Build options dialog box displays.
Build application control

code writes the .pcd file.
Enter a file name in the
text box or click Browse...
to select a .pcd file already
created.
Build application diagnostic

symbol table writes the .sym
file. Enter a file name in the
text box or click Browse... to
select a sym already created.
Select this option to put the

symbols into a database.
Note When errors occur during a build, the error messages display in the Log View.
Pcode Report
The Pcode report is a text file (.pcd) created from the build command. The .pcd file
can be interpreted by the toolbox and described in a report.
To create a Pcode report
1. From the File menu, select Open.
2. From the Files of type drop-down list, select Pcode Files (*.pcd).
3. Select the correct directory and .pcd file from the list of files or enter a .pcd file
name in the File name text box. The Create Pcode Report dialog box
displays.
Create Pcode Report Dialog Box

The Create Pcode Report dialog box is illustrated below.
Check either Module or Task.

Then select one or all modules or
tasks from the drop-down list box.
Select the check boxes to

specify the desired record
types to display in the report.
Click Continue to generate the

report.
Click Mark All to receive the Click UnMark All to clear all record
entire .pcd file. type boxes that are checked.
Software Setup
The following sections describe how to set up the software portion of the controller
for the first time.
Downloading is when a component of a configuration is sent to the component's
controller.
Flash is a non-volatile memory technology that contains the real-time operating
system, the file system, and the TCP/IP software. These are installed with the Serial
Loader, so the remaining runtime and configuration can be downloaded more
efficiently over Ethernet.
The controller is shipped with Basic I/O system (BIOS) performs the boot-up, including hardware self-tests, and
the BIOS, the real-time the Serial Loader.
operating system, and the
Product code (runtime) software converts Application code (Pcode) configurations
runtime software installed.
to executable code (software) and schedules them.
However, to insure that the
latest software is loaded, Application code (Pcode) (.pcd) file, created by the toolbox, contains the controller
perform the controller setup, configuration.
described in the next section.
Symbols table file (.sym), created by the toolbox, contains signal names and
descriptions for diagnostic messages. The information is read into RAM as needed,
making updating the file in permanent storage sufficient.
Ethernet or UDH Cable
Toolbox &
Serial Loader
Software
COM1 Mark VI Controller
RS-232C Serial Loader Cable
Controller Setup
The following steps define how to set up the controller for the first time. It is
assumed that the toolbox and controller are already installed in the pc.
Note CompactFlash setup is available only for those systems having a platform of
UCVE or greater.
To set up the controller

1. Load the flash and configure TCP/IP with the Serial Loader over a serial cable
(see the section, Loading the Flash File System).
A soft reboot from the toolbox 2. Cycle power on the controller to activate the new IP settings.
is not sufficient. 3. From the toolbox, load the product code (runtime).
4. Load the application code (Pcode) and symbol files to permanent storage only.
5. Cycle power on the controller again.
Note The remaining sections define each of these steps.
Serial Loader
The RS-232C cable can be The Serial Loader initializes the controller flash file system and sets its TCP/IP
ordered through your local address to allow it to communicate with the toolbox over Ethernet. It requires an
GE authorized distributor, as RS-232C serial cable. The cable specifications are as follows:
part number 336A3582P1
Controller PC
Pin Pin
Adapter Cable DCD 1 1 DCD
to Controller DSR 6 6 DSR
RD 2 2 RD
COM1 Port
RTS 7 7 RTS
TD 3 3 TD
CTS 8 8 CTS
DTR 4 4 DTR
RI 9 9 RI
GND 5 5 GND
9-Pin Plug 9-Pin 9-Pin 9-Pin Plug

Subminiature D Subminiature D
Receptacle Receptacle
A short adapter cable is required to plug into the controller COM1 Micro-D size
connector. This cable can be ordered as part number 336A4929G1. The Serial
Loader can load the Flash File System and configure the TCP/IP software in the
controller.
To connect the Loader serial cable
1. Connect the end of the cable to COM1 (9-pin connector) on the controller.
2. Connect the end of the serial cable labeled UC2000 connector to the converter
cable.
3. Connect the end of the serial cable labeled pc COM Port to one of the pc COM
ports.
Initialize Flash
The Flash File System is loaded during system installation, using the Serial Loader .
To start the Serial Loader
1. From the Start menu, select Programs, GE Control Systems Solutions,
Mark VI Controller, and Serial Loader. The Serial Loader dialog box
displays.
2. Enter the correct setting as defined in the following Serial Loader dialog box.
3. Click Start Command(s).
TCP/IP Settings include Computer Name, IP Address, Subnet Mask, and
Router IP. (Obtain this information from your network administrator.) Click
this button to display the dialog box to enter this network data (see the
section, Configuring TCP/IP ).
Select Mark VI from the

drop-down list .
Click to define the PC COM

port. Make sure this port
matches the hardware
cable port (usually COM2
or COM3).
Click Load Flash File

System .
Click Display Summary

Information to display
information in this status
window.
Click
to start the selected
commands.
When the load completes, the following message box displays.
Note The button, Source Directory, points to the location of the BIOS, CMOS, and
flash binary files. It is enabled when CPU Type is either Custom or Mark V LM. The
controller directory is automatically set to platform (C:\Program Files\GE Control
System Solution\MarkVI_Controller\platform)
Compact Flash Setup
To write the Compact Flash
From the Device menu, select Download, Compact Flash.
Select the
processor.
Note If the Compact Flash hardware is not found, the following error message
displays. Check the hardware installation and the Compact Flash disk placement.
Select Refresh
to update the
Flash Device
information.
The IP Name, IP
Address, Subnet
Mask and
Default Gateway
are read from
System Information
information and
cannot be
modified from
this dialog box.
Select Write to
write the compact
flash to the device.
Select Cancel to
exit without altering
the compact flash.
Configure TCP/IP
Obtain the Computer Name, IP Address, Subnet Mask, Broadcast Mask, and Router
Click in the IP from your network administrator. Enter this data into the proper fields below:
Serial Loader dialog box.
Enter the Internet Protocol (IP) host
name. For Ethernet networks with a
global name server, the host name
can be used interchangeably with
the IP Address when
communicating to a controller.
IP Address is used to identify a

node on a network and specify
routing information on an Internet.
Enter the 32-bit value used by the

IP software to extract the network
ID and host ID from the IP
address. To be valid, the mask
must contain a "1" for all of the
network bits of the IP address
class (shown above).
This field is calculated

automatically.
Enter the 32-bit value used Click to load or save
by the IP software to route these settings (.ssf file)
external network messages. to the local PC.
Tip All IP addresses and masks are represented in dotted decimal notation,
within each of the four bytes of the address, separated with periods, such as
3.29.22.27. To determine the correct IP addresses and masks, see your network
administrator.
To change only the TCP/IP from its initial setting

1. Modify the TCP/IP Settings dialog box.
2. In the Serial Loader dialog box, check Configure TCP/IP and
Display summary Information.
3. Click Start Command(s).
4. After the command completes, reboot the controller for the change to take
effect.
Product Code (Runtime) Software
Product code is loaded over Ethernet by the toolbox.
To load the product code (runtime)
1. From the toolbox, create a new Mark VI controller, or load an existing file.
2. From the Device menu, select Download, then select Product Code
(Runtime). The Download File dialog box displays.
Note Some controller versions may display two files, Runtime.dnl and Select.dnl.
Select .dnl should always be selected unless instructed otherwise by personnel.
3. Select Select.dnl and click Open. All possible files that can be downloaded
display in the following dialog box.
Click to uncheck
any file not used
by the controller
(to conserve
memory). The
toolbox deletes
the entire
directory , then
downloads only
the checked files.
If you are not sure

which files to
select, click Scan
hardware for
suggestions. All
files associated
with I/O in the
configuration will
be checked.
Application Code
After validating and building application code, download it.
To download application code
Or click 1. From the Device menu, select Download, then select Application Code....
The Download Application Code dialog box displays. The default screen
displays with all options checked.
2. Reboot the controller using the power switch.
Software Modifications
The following sections describe how to modify the application code in the controller
and how to upgrade the product code software to a newer version.
Modify Application Code

The controller executes the application code from RAM. Each time the controller is
rebooted, the application code is copied from permanent storage in the flash into the
RAM. This allows you to try out new application code by downloading it into RAM
and then to restore the original configuration by rebooting. Or alternately, the new
code may be made the default by writing it to permanent storage.
Some application code changes, including editing, inserting, or deleting blockware
may be downloaded to RAM without stopping the control process. This is known as
an online download.
Some application code changes, including modifications to I/O, scales, or variable
addresses may only be downloaded to RAM by stopping and restarting the control
process. This is known as an offline download.
Still other application code changes, including modifications to system memory sizes
cannot be downloaded to RAM but must be downloaded to permanent storage only
and the controller rebooted. Any change that may be implemented with an online or
an offline download may also be performed this way. Refer to the section,
Major/Minor Differences.
Pcode is written when the To change the application code in the controller
menu command, Build
1. From the toolbox, modify the application code.
application control code, is
selected. This file contains all
the application software for 2. Select Validate and Build.
the controller. 3. From the Device menu, select Download, then select Download
Application Code.
4. Select the desired download option from the Download application code
dialog box.
Check Download to memory to replace the current running configuration with the
new application code. Then, select from Memory Download Mode
Online - Init all constants to replace the running configuration without stopping
Downloads to
for a fast download. Since all constants are initialized the process increases.
RAM
Online - Init only new constants to replace the running configuration without
stopping for a fast bumpless download.
Check to download the new

application code (.pcd file) to
flash memory to be used when
the controller is rebooted. This
does not change the current
running configuration.
Downloads to Enter the correct .pcd file name
Flash Browse...
Check to download the .sym

file to permanent storage. This
changes the active symbol
table in the controller.
Enter the correct .sym file
name or click Browse...
Check to download the
compressed Mark VI file to
permanent storage. This file
serves as disaster recovery if
the PC-based file gets
corrupted.
Note When all options are selected, the symbol table is downloaded first. Then the
application code is downloaded to memory. If the download to memory succeeds,
the code is downloaded to permanent storage. If it fails, the download to permanent
storage is cancelled.
Major/Minor Differences
The toolbox detects differences between the application code loaded into it and that
loaded into the controller by comparing the revision dates. The revision in the
toolbox and the controller is stored as two date and time values. These values are
cleared in the toolbox when a major or minor change occurs and set when the
configuration is built (Pcode). When the toolbox is online with a controller, the
major/minor revision of the downloaded configuration in the controller is compared
with the current configuration in the toolbox.
Major and Minor

revision
differences are
indicated in the
Summary View.
The connection/revision status is displayed here.
The controller application files consists of Pcode files and diagnostic symbol table
files. Pcode can be downloaded to either the active RAM to replace the running
configuration, or to permanent storage. Permanent storage is flash memory for the
controller for use the next time the controller boots.
Pcode can be downloaded to the controller RAM in either an online mode, where the
configuration is switched over quickly, or offline where the controller is completely
stopped and then restarted. It is usually beneficial to use the online download, but the
amount of configuration change could make this impossible.
A major difference means that the major revision in the toolbox is different from the
major revision in the controller. A minor difference means that the minor revisions
differ, but the major revisions are the same. Equal means that both major and minor
revisions are the same. These differences display in the Status Bar.
A bumpless download does It is not always possible to download online when a change is made to the
not disrupt the control as a configuration that prevents the download from being bumpless, such as numerous
result of the download. changes to signals in regard to their address tokens, or changes to scales or I/O. In
the toolbox, a major change is one that does not allow an online download. These
include changes caused by additions of hardware modules, or packing signals.
Packing involves reclaiming unused tokens (this does not include connecting signals
to points). Minor changes are any other changes to the configuration including
editing, inserting, or deleting blockware.
The status of changes to the configuration can be seen from the Summary View, as
shown below. The first example shows a configuration just built, the second has
minor changes, and the third major changes.
Upload Mark VI File
The following steps allow you to retrieve a permanently stored Mark VI file (.m6b).
To upload a Mark VI file
From the Device menu, select Upload.
When the file is uploaded, a new window is created with the name <device
name>_dl.m6b.
Enter the IP Address or

the Host Name of the
target controller.
Select the type of
controller. The default is
the currently open device
type, if present.
Upgrade Product Code (Runtime) Software

The following steps define how to install a new version of the product code software
in a previously configured controller. It is assumed that the toolbox and a previous
version of the product code are already installed in the pc, and that an application
code file (.m6b or .ucb) exists.
To upgrade the product code
1. From the toolbox, select the File menu, then Open. Select the existing
application code file (.m6b).
2. From the File menu, select Export, then select All. From the Export All
options dialog box, select an option to export the application code into its tree
files (.tre) and a project file (.prj).
3. Install the new controller product code from the product CD.
4. From the Device menu, select Download, then select Product code
(Runtime).
5. Select Select.dnl and click Open. All possible files that can be downloaded
display in the following dialog box.
6. Click to uncheck any file not used by the controller (in order to conserve
flash space). The toolbox deletes the entire directory and then downloads only
the checked items. If you are not sure which files to check, select Scan
hardware for suggestions. Files that are associated with I/O in the
configuration will be checked.
7. When you are finished with your selections, click OK. The following message
displays.
8. Click No. Do not reboot.

9. From the File menu, select Close.
10. From the File menu, select Open and open the project file. This imports the
component files (.tre) back into the toolbox by opening the project file (.prj).
Note This will create a new Work Area to merge the application code (.tre files)
with the new product code.
11. Click Validate and Build to create a new Pcode file (.pcd) from the
application code.
12. From the File menu, select Save.
13. From the Device menu, select Download, and then select Application
Code.... The Download Application Code dialog box displays.
14. Check Download to permanent storage and Download symbols.
15. Click OK.
16. Wait until the red FLSH LED on the controller has turned off.
17. Reboot the controller using the power switch.
Use Totalizers
Totalizers are timers and counters that store data such as number of trips, number of
starts, number of fired hours and such. They are currently used in Mark VI or
EX2100 application code. The outputs of the timers and counters are then stored in
NOVRAM.
Note A special password is required to modify Totalizer values. To obtain a

password from the GE OnSite Center, click the Save button on the dialog box below
for instructions. No password is required to view the current value of the Totalizers.
To view or modify the totalizers value

From the Device menu, select Download, and View/Set Totalizers. The
Totalizers dialog box displays.
Enter the
password in
Password
field.
Click Modify to
change the value
of the highlighted
item.
To request a totalizer password
1. From the Device menu, select Download, View/Set Totalizers. The
Totalizers dialog box displays an Identifier.
2. Click Save to save the identifier to the hard drive. The Totalizer_ID text
displays the procedure to follow to receive a Totalizer password. The password
sent is valid for 24 hours only.
Restore Application Code

The application code running in the controller's memory may be different from that
in permanent storage. If the code in memory becomes unstable, this command loads
into the controller's memory the uncorrupted code in permanent storage. All changes
to the code in memory will be lost.
Note Restoring from permanent storage cannot revert application code if the major
revisions between permanent storage and memory are not equal.
To restore application code from permanent storage

From the Device menu, select Download, then Restore from Perm
Storage.
Replicate Device
The Replicate command allows you to copy a configuration file from one device to
another. In the case of a multi-unit turbine system, each control unit typically has the
same configuration, such as hardware I/O, network I/O, or sequence code library.
However, each unit requires some unique device identifiers, which require manual
input; this command automates that process.
To replicate a configuration file
1. From the Device menu, select Replicate. A copy of the configuration file
opens and the Mark VI Device Name dialog box displays.
2. Enter the new device name and click OK. The Translate Regions dialog box
displays.
Click this column to
enter the new region.
Select regions
to include in
replication.
Select to save the

new document in a
New Unit Folder.
Enter the new
folder location
or click the
Browse...
button.
Enter the
Sourcefile New
Unit Folder
location or click
the Browse...
button.
3. Verify the new regions to replace and select the desired options. Click OK.
The replication process
Replaces the selected regions
Replaces Sourcefile folder names, if desired
Creates a new folder, if desired
Sets the device number to zero
Deletes all system data
Deletes all external EGD pages and exchanges
Monitor
Once a controller is configured and downloaded, the live signal values can be
viewed. This section defines how to go online to monitor these values and certain
Summary Views when the controller is being monitored. These views are displayed
when the Tracking button is on and an item is selected in the Outline View.
Going Online/Offline
To see the live data from the Summary Views, it is necessary to be online
(communicating to a running controller).
To go online
Or click . From the Device menu, select Online. Online blockware information can be
monitored from the status bar and the Summary View.
Status Bar
When online is started, it is indicated on the status bar in the lower-right corner of
the Device Window, shown below. The difference status and idle time of the
controller replaces the word Offline when the controller and toolbox are
communicating. The status bar also displays the enable value and heartbeat of any
tasks or blocks of tasks in the block flow diagram (Summary View), when the
diagram is active.
Module View
For information on how to The Summary View for a module item displays the task list with the module
configure and view a modules scheduling information. When monitoring live data, the task list also shows the
graphics window, refer to the enable value and heartbeat, as shown below. When the toolbox is offline, the
section, Graphics Window. heartbeat and enable value are replaced with a hyphen. The Detached Summary
View for a module item with graphic window file is called a Graphics Window.
Task, Macro, and Block View

For more information, refer The Summary View (right side) for tasks, macro definitions, macros, blocks, and the
to the section, Block Flow block items of a macro instance is called the block flow diagram. When a block or
Diagram. macro instance is highlighted in the Outline View and Tracking is on, the Summary
View displays that single item. When the controller is online, the block flow diagram
displays live data values (in green) next to the block or macro pin.
To modify the live data values
From the Summary View, double-click the values. One of the following dialog
boxes displays.
Boolean Value
Use the dialog box below to modify a Boolean value.
Use this dialog box to

change or force the live value
of a Boolean signal. Forcing
the value keeps the
blockware from writing over
the forced value, whereas an
unforced value can be over-
written in blockware.
Numerical Value
The numerical value is modified with the dialog box below.
Use this dialog box to enter a
value to be sent to the controller.
These values cannot be forced,
so values that are written in
instruction blocks do not change
to the value being sent.
Current is the live value of the

signal. Enter the Next value and
click Send.
Delta is the value to be added or

subtracted from the current value.
Click here and increment Click here and decrement
Token is the logical address of the Current value by the the Current value by the
the signal. Delta amount and send it Delta amount and send it
to the controller. to the controller.
Array Value
The dialog box below is used to modify the array value.
Click on the
element to
change.
Click Modify.
The Boolean or
Numeric Send
Value dialog
displays with
this element.
Watch Windows
The Watch Windows function creates a quick reference list containing names,
values, units, and description of the online values of signals. Each controller
document can contain multiple, uniquely named watch windows. These are saved,
then exported to or imported from the controller's project file.
To select a Watch Window
From the toolbar, click View, then select Watch Windows. The Select
Watch Window dialog box displays.
All Watch Window

names are listed here.
To create a Watch Window

1. Click the New button. The New Watch Window dialog box displays.
2. Type a unique name. Click OK to view Watch Windows.
Note It is possible to minimize any watch window by clicking the minimize symbol
in the upper right hand part of the dialog.
Selects the appropriate
signal in the configuration
file.
Starts the trender and

inserts the signal
If you are online, this will

pop up the change live
value dialog
This will be signal

definition as a comma
delimited line into the
operating system paste
buffer
You can add comments to any
signal in a watch window.
These comments are saved with
the watch window, not the
signal.
To insert a signal
1. From the Outline View, right-click on a signal to display a shortcut menu.
2. Select Insert Signal to open the toolbox Signal Selector dialog box.
3. Select a signal and click OK.
To delete a signal
From the Outline View, right-click on the signal, then select Delete Signal.
Or, select the signal and press the Delete button.
Note Signals can also be dragged-and-dropped into Watch Window from other
Watch Windows or the Outline View. Dragging an I/O point into a Watch Window
will display the point's attached signal, not the point.
Controller Status Commands

The Controller Status Commands are a set of diagnostic functions that the toolbox
can run on the controller. They allow you to view the status of many control system
functions. If you contact GE for technical support for your controller, you may be
asked to run some of these commands. The results of a command displays in a text
window, which can be saved as a file.
Controller Load Profiler System
To configure Controller Load To configure the Controller Load Profiler
Profiler, you must have
From the Outline View, double-click the controller name.
Standard Block Library
(SBLIB) revision 7 Note You must validate, build, and download for the controller changes to take
(V07.xx.xx) or greater effect.
installed.
Select this box

to enable
Controller Load
Profiler for the
device.
Once the Controller Load Profiler is enabled, select it from the View menu. The
Profiling Controller Load window displays the following information.
The data in this report can be Scheduling Chart Number identifies the three charts in the controller, one for
sorted by clicking on the each base period of module configuration and task schedules. Each scheduling chart
column header and printed to can have multiple modules defined.
a CSV file with the print
Overrun Counter advances if the time to start a task exceeds the time allotted (the
command (CTRL+P).
chart base period).
Chart base period is the maximum period of time allotted for the execution of
application tasks within each time slice in a chart.
Last Run Time is the time needed to run all the tasks in a slice.
Bar Graph is the percentage of the slice used by the tasks. The graph displays in
red when more than 90% of the run time is used.
Last, Minimum, and Maximum Frame Time (in milliseconds) columns
allow the user to reset the minimum and maximum frame times by selecting the first
line in the list and selecting Reset under the Device menu.
Monitor Controller State
The toolbox status bar displays information about the controller state. The status bar
feature called Control State allows the status to be viewed from a remote site.
This displays the current

device state as Unknown.
The four states (in increasing priority) that can be viewed are:
Control - controller is running (green background)
Boot - controller is starting up (yellow background)
UNKN - controller state is unknown; more investigation is required (yellow
background)
Fail - controller has failed (red background)
For Simplex systems, the state displays for that one controller. For TMR systems, the
highest priority state of the set of controllers displays. For example, if both the <R>
and <S> controllers are in the Control state and <T> is in the Fail state, Fail
displays. For more detailed controller state information, display the Controller
State dialog box.
To display the Controller State dialog box
From the status bar, double-click the controller state. Or, from the View Menu,
select Controller State.
The value of the IO The value of the Control
State of the controller. State of the controller.
An asterisk (*)
determines the
designated
controller.
The current
controller
state
Explanation
of current
controller
state
Control Constant and Tuning Variable View
A flag indicates the existence Control Constant is a signal with an initial value that is read and never written.
or status of a particular Control constants are specific constants that a user might want to consider separate
condition. from other constants because of their importance to key control algorithms. Users
can flag signal and module definition pins that have this property. Once flagged,
constants can be viewed and compared as a group, exported to .csv files for
manipulation outside of the toolbox, and merged back into the configuration.
Tuning Variable is a signal with upper and lower limits, which define the bounds
of the initial value and when making runtime changes. Tuning variables are specific
signals that are considered separate from other signals and constants because of their
importance to key control algorithms. Only users at privilege level 4 can flag signals
and module definition pins to have this property, and to set the upper and lower
limits. A user at privilege level 2 and above can change the initial value or runtime
value of a tuning variable, but not outside the range defined by the upper and lower
limits. Once flagged, tuning variables can be viewed and compared as a group,
exported to .csv files for manipulation outside of the toolbox, and merged back into
the configuration.
Work Area
To use the Control Constant View
1. Create or open a binary working file (.m6b).
2. From the View menu, select Control Constants. A separate window
displays, called the Control Constant View.
To use the Tuning Variable View
1. Create or open a binary working file (.m6b).
2. From the View menu, select Reports and then Tuning Variables. A separate
window displays, called the Tuning Variable View.
The following sections describe the menu commands and work area specific to
Control Constant and Tuning Variable View.
File Menu
The File menu is illustrated below.
Close exits the Control Constant View.

Save/Save As preserves on open file. Save As prompts you for a new file name.
Merge in .CSV reads the saved and modified .csv file and overwrites the initial
value of the signals in the configuration with the new value specified.
Export to .CSV writes the signal information to a .csv file. The form of the file
name is DEVICEControlConst.csv, where DEVICE is the actual controller name.
The signal information includes the name, value, scale, type, and a note.
Print provides a paper copy of the Control Constant View.
Print Preview displays the page as it would be printed.
Print Setup allows you to select a printer and print connection.
Edit Menu
The Edit menu is illustrated below.
Modify allows you to edit the selected signal.

Find allows you to search the Control Constant View for text in the signal names.
Device Menu
The Device menu is illustrated below.
Online toggles the controller online/offline to view live data values and enables the
Save Values command.
Save Values obtains the displayed live values and puts them in the controller
configuration. Make these changes permanent by going to the controller window and
saving the binary file.
Modes of Operation
The Control Constant and Tuning Variable Views have two modes of operation,
online and offline. The Control Constant offline view displays the Signal Name,
Initial Value, Type, Scale, and Note for all signals that are control constants.
The Tuning Variable offline view displays the Signal Name, Initial Value, Type,
Scale, Upper and Lower limit, Note, and Path for all signals that are Tuning
Variables.
To edit a view
Double-click a signal name. The Edit Module Pin or Signal Edit dialog box
displays.
In the online mode, the live Value displays (second column). Signal Names that have
differences between the live Value and Initial Value are marked with a red
not-equals symbol ().
To modify the live value
Double-click a signal name. The Send value dialog box displays.
Send Value
Use the dialog box below to modify the send value.
Use this dialog box to enter a

value to be sent to the controller.
These values cannot be forced, so
values that are written in
instruction blocks do not change to
the value being sent.
Current is the live value of the

signal. Enter the Next value and
click Send (or click Send & Close
to exit the dialog box).
Delta is the value to be added or

subtracted from the current value. Click to either Increment or Click here to send the value entered
Decrement the Current in the Next box to the controller. This
Token is the logical address of the value by the Delta amount is the default setting, so typing a
signal. and send it to the controller. value and pressing Enter also sends
the value and closes the dialog box.
The following dialog displays for Tuning Variable View.
Tune High Limit The Next value cannot be greater then the high limit.
Tune Low Limit The Next value cannot be less then the low limit.
If the signal is not a tuning variable, then the high and low limits fields do not show
up in this dialog.
Note In both views, the live values can be saved to the configuration online from
the Device menu.
File Compare View
The File menu contains a Compare command, which compares one configuration
file with another.
Compare All compares an entire file configuration with another selected .m6b file.
Compare Selected compares a selected item of two .m6b files.
Compare Block Configuration compares the application code of each file. It
performs a back-chain from each output signal that compares the inputs, the block
types, and connections that create the signal. Block numbers and code locations in
the Outline View are ignored.
Compare Signals compares each output signal defined in the application code.
Each signal is tested for initial value, data type, and such.
To compare files
1. From the File menu, select Compare, then the desired comparison type. If
more than one .m6b file is open, the Compare dialog box displays.
Select to
compare with
an open file.
Select which
open file to
compare.
Select whether
to compare a
currently open
file or open a
new one, then
click OK. The
Translate
Regions dialog
box displays.
This column displays regions of This column contains the

the Reference file for comparison. same columns for the test file.
Select the regions

to compare.
Click here to change

the name of the
regions to compare.
2. Configure any region relationships, as necessary, and click OK.
The items compare and display as follows:
Select a location to search for items Detailed description of
that are different in the .m6b files. the difference error.
The two
files being
compared.
The items that are different.
Note The menu commands for this screen are the same as basic toolbox menu
commands. Refer to the section, Menu Commands.
Application Documentation
All reports and diagrams Application documentation consists of printable tables, reports, and block diagrams
contain extensive cross- that help you understand and maintain the system. Most Outline View items can be
referencing. printed individually or as part of a larger document that thoroughly describes the
controller configuration. Block diagrams provide information about controller
blockware and reports contain information about signals and Pcode.
The full application document contains numerous optional sections:
Device Summary lists the main settings for the Mark VI controller, including IP
addresses, platform types, and customer information.
Document Reading Aid explains the conventions and symbols used in the
document.
Revision Log is a list of changes made to the controller configuration that
includes the modification date and user name.
Table of Contents provides page numbers for each section heading.
Functions includes the block diagrams of all controller functions.
Macro Definitions includes the block diagrams for all non-protected controller
macros.
Reports include summaries of alarms, I/O, and such.
Signal Cross Reference provides a list of all named signals in the configuration
with type, units, description, and references to signal locations.
Print Options
The item selected in the Outline View determines what gets printed. If you wish to
print the entire controller configuration, select the controller name. If you wish to
print only a single module, function, or task, select that item.
To print application documentation
1. From the Outline View, click the desired item to highlight it.
2. From the File menu, select Print Preview to view the document online or
Print to create a hard copy. The Print Options dialog box displays.
The Print Options dialog box contains four tabs: Options, Margins, Fonts, and
Profiles.
Options Tab
The Options tab lets you select the report type.
Select the reports

to be printed.
The Page Numbering options control page number assignment.

Linear page numbers go sequentially from one. The page number on the
printout corresponds to the actual printed page.
Hierarchical by Module, Task page numbers are divided into three parts:
section, sub-section, and page. The section number starts with one and
increments for every function and module. The sub-section number is
incremented for every task within a section. The page number starts with one for
the first page of a task and counts linearly.
Hierarchical by Function, Module, Task is similar to Hierarchical by Module,
Task except that there are four parts to a page number.
Hierarchical with section names uses text strings for sections instead of
numbers.
Note Cross-references to hierarchical page numbers are often abbreviated within a

section. For example, a reference from the first page to the second page of a task
would only show the page number, not the section and sub-section.
The block diagrams options control printing of block diagrams.
Text Size controls the font size, which determines the diagram scaling.
Show Block Drawings determines whether to include the internal drawings for
complex library blocks. Although these drawings help with understanding the
code, they occupy much space.
Wires can cross page edge selects wire-routing behavior in multi-page
diagrams. This option enables or disables the printing of wires that cross page
boundaries in multi-page diagrams.
Show live data values enable a signal's live value to be printed if you are online
in the toolbox.
Note Because large blocks cannot always fit on a single page if you select a text size
too large for your paper, always preview before printing.
Margins Tab
The Margins tab lets you select either single- or double-sided printing and margin
settings.
Select the check box

for either single-sided
or double-sided
printing.
Note When printing double-sided, the back-page margins are mirror image of the
front-page margins.
Font Tab
The font tab provides font sizing options.
Select the
desired font.
Note Selecting fonts that are too large can result in text printing outside the margins.
Profiles Tab
The Profiles tab allows you to save your print settings for future use.
If you selected Print Preview from the File menu, the layout calculates and
displays, using the current printer setup. If you selected Print, the standard Print
Note In very large controllers, the print layout calculations can take several minutes.
Print Preview
To preview application documentation
1. From the File menu, select Print Preview to see how the application
documentation will look when printed and to proof for mistakes.
2. Click the Print Preview button to close the print preview. Click Print to open
the Print dialog box.
Block Diagram
For more information, refer The block diagram can be captured and viewed (Summary View or the Detached
to the section, Block Flow Summary View) or printed to a hard copy (paper) form. The diagram displays the
Diagram. item (task, macro, or macro definition) currently highlighted in the Outline View.
To view a block flow diagram
1. From the Outline View, click the desired item (in the hierarchy list) to
highlight it.
Or click to view the 2. View the diagram from the Summary View or select Detached Summary
Detached Summary View. View from the Edit menu.
Or, from the File menu, select Print Preview to view the diagram online or select
Or click to print a hard Print to create a hard copy.
copy.
Page breaks divide the report The Block Flow diagram uses the Comment block to force page breaks. The diagram
information into orderly pages are numbered in a row/column format. (This format makes it easy to assemble
pages. the report on a wallboard.) The size and characteristic of the blocks can be edited in
the Block Diagram tab.
To edit the Block Diagram
1. From the Options menu, select Settings. The Settings dialog box displays.
2. Click the tab Block Diagram (defined in the following section).
Block Diagram Tab
The Block Diagram tab is illustrated below.
Display the blocks in a list with no

connections or connected to each
other or the Summary View and
Detached Summary View .
Check to show all List block

diagram pins. This command
disregards the text box Visibility,
if it is checked in the Edit Macro
Pin Definition dialog box. Font
size changes the font size of all
text on the block diagram.
Check the following options for

interconnected block diagrams:
Show all pins displays all
block pins. This command
disregards the text box
Visibility, if checked in the
Edit Macro Pin Definition
dialog box.
Reorder pins rearranges the
pins to minimize crossing the
connections on the diagram.
Show input or Show output
connections displays the
connection names and values.
Font size changes the font Change the Summary View tracking feature to display various levels
size of all text on the block of the hierarchy, when they are selected in the Outline View. Select
diagram. the item to display on the lowest level. The default is Task/Macro.
Reports
Reports provide controller information in a printed form. Reports display in a
separate window and can be viewed, saved, and printed. The following report types
can be generated for the controller:
Alarm List
Hold List
Event List
Scale List
Signal List
Signal Cross-Reference
Multiple Written Signal List
EGD Network
Simulation Data
Control Options
I/O Report
I/O Module Report
I/O Point List
Unused I/O Report
Revision log Report
Enumerated Data Types
Control Spec Reports
IO Config
Signal Config
Block Pin Report
Tuning Variables
2nd Language Report
Orphan Signal Report
To generate a report
From the View menu, select Reports. Select the desired report. The report
displays as a separate window.
When viewing a report, a text find feature is available to search for specific text in
the report. From the View menu, select Find. The Report Find dialog box displays
to enter text and search the report (defined in the following section).
Report Find
The Report Find dialog box is illustrated below.
Enter the text you want to find
from the report. The found text
is highlighted in the report..
Enter new text or click Cancel.
Only Boolean signals can be

selected for the Alarm List, Alarm, Hold, Event Lists
Hold list, and Event List The Alarm List report creates a spreadsheet displaying all the signals marked as
reports. These reports can be alarms. This report lists the signal name, description, and the alarm (drop) id for
used to create the alarm.dat, each signal. Signals are marked as alarms on the Edit Signal Definition or Edit
bold.dat, and event.dat files Module Pin dialog box.
used by the HMI to display
the alarm lists. The Hold List report produces a spreadsheet displaying all the signals marked as
Automatic Turbine Startup (ATS) hold signals. Signals are marked as Holds on the
Edit Signal Definition or Edit Module Pin dialog box. This report, which lists
the signal name, description, and the hold id for each signal, looks exactly like the
Alarm List report.
The Event List reports all the signals marked as Event signals. Signals are marked
as events on the Edit Signal Definition or Edit Module Pin dialog box. This
report, which lists the signal name, description, and the Event id for each signal,
looks exactly like the Alarm List report.
Scale List
The Scale List report provides a list of all scales that are used in the controller
configuration. The list includes both locally defined scales and global scales (Scales
under System Data, External Scale Definitions which are brought into the
configuration when a Get from database is performed).
Signal List
The Signal List report provides a list of all the signals in the controller. For every
signal, the report lists the signal name, the data type, and the token number. Signals
listed in the controller configuration, but not used by any blocks have a blank token.
Signal Cross-Reference
The Signal Cross-Reference report provides a list of all locations in the blockware
where named signals are used. Named signals are signals defined by you, usually
either in a signal definition or as module pins. Automatic signals are generated by the
toolbox. They connect block pins, when neither pin is connected to a named signal.
The first part of the signal cross-reference is an index of the items in the controller.
In the cross-reference, an item is considered down to the level of an item that
contains blocks, which could be a task, a macro, or a macro definition. The code
corresponding to one of these items shows the level of the item.
An example of the index is as follows:
Index of sections for controller uc2k-9
01 Functions
02 tmr_test
02:01 ........\MacroDefs
02:01:01 ........\.........\my_macro
02:02 ........\Pump
02:02:01 ........\....\PumpTask
02:03 ........\Entry\Pump1@Pump
02:03:01 ........\................\PTask
The second part of the signal cross-reference is the actual cross-reference list. Each
location, where the signal is referenced, is listed for every signal. Each reference
consists of a section code for the task macro or macrodef, the block number, and a
flag (*) to show whether the signal is being written on the block. Examples from a
cross-reference report are as follows:
Entry\Pump1\PumpEngine------------:
Signal Entry\Pump1\PumpEngine is not used anywhere in the blockware.

Entry\Pump1\sinout----------------: 02:03:01:0020*
Signal Entry\Pump1\sinout is written to on block 20 of task Ptask, in module

Entry\Pump1@Pump, in function tmr_test.
Entry\Pump1\Start-----------:02:03:01:0030 02:03:01:0030*
The signal Entry\Pump1\Start displays on two pins (one read, one write) on block
30 of the same task.
Multiple Written Signal List

This report provides a list of all signals that are written to by more then one block or
pin. Each row for a signal includes the path to indicate where the point is written to.
There are many times where it is advantageous to write to a signal from multiple
locations, but if it is done accidentally, the consequences can be such that the code
will not operate as intended. This report will show those errors.
EGD Network
The EGD Network report provides a list of all signals and IO that is connected to
the EGD network. It includes which EGD exchange it is connected to, the direction
of the point, data type, update rate, and other selectable data.
Simulation Data
Some controller applications have simulation systems, which drive hardware inputs
and read outputs in a coordinated way on a system-wide basis. A complete
discussion of the simulation system is beyond the scope of this manual. However, the
toolbox supports simulation by writing I/O point configuration information to a .ucx
text file (to be used by the simulation system).
To write simulation data
1. From the View menu, select Report and Simulation Data. The Simulation
Output File dialog box displays.
2. Create or select a file (.ucx) to hold the simulation data. Click Save. The
Simulation Report Options dialog box displays (refer to the next section,
Simulation Report Options).
Simulation Report Options

The Simulation Report Options dialog box is illustrated below.
Click on the option box to

include that I/O type in the
.ucx file.
Click Continue to write the

I/O information to the .ucx.
Control Options
The control options report produces a list of all the control options selected in the
current configuration. For each selected option, the report lists the option name, the
option value, and any additional text or notes that apply to that option.
I/O Report
Once the I/O report option is selected, the IO Report Select Columns dialog box
displays.
Select the columns desired for the report. Once the report is generated, click the
column header to sort the data by column.
The following table describes the columns.
Columns in the I/O Report
Column Name Description

Entry Counts the number of items in the report. Sort by this column to place the data in its
original order.
Device ID of device attached to the screw
Cable Number ID of the cable attached to the screw
Wire Number ID of the wire attached to the screw
Interposing TB ID of the terminal board junction, if any, between the Mark VI and the actual I/O
Sense Used for relay and solenoid circuits only. Sense of relay connected
TB Screw Number of the screw on the terminal board
TB Name Name of the terminal board
TB Location Panel location of the terminal board
Screw Name Name of the screw on the terminal board
Point Name Name of the point that the screw services
Card Jumpers List of jumpers on the VME card and the position to which they should be set
VME Card Name of the VME card
VME Jack Name of the jack on the VME card to which this terminal board connects. Formatted to
match cable labels. Rack number followed by channel designator (Q means R, S, and
T) followed by jack designator as shown on the screen print. Rack designators are
postfixed by the slot number on the screen print.
Signal name Name of the signal attached to the point
Used Whether the point is used by the CSP
Description Note attached to the point. If the point has no note, the note from the signal is attached
Engr Low The Low_Value configuration item of the point, when presen
Engr High The High_Value configuration item of the point, when present
Engr Units Units associated with the scale associated with the signal
Raw Low The Low_Input configuration item of the point, when present
Raw High The High_Input configuration item of the point, when present
Raw Units The units associated with the InputType configuration item of the point, when present
Mask The units associated with the SignalInvert configuration item of the point, when present
Importing an I/O Report from a .csv file
Save the .M6B file before importing.
The Mark VI supports automated import of some or all of an I/O report. This is used
whenever there are multiple sources of the report data.
Do not import columns you To Import an I/O Report
do not want to change.
Highlight the Mark VI I/O in the Outline View.
1. Under the File menu, select Import.
2. Select CSV as the type of the import file.
3. Select the file to be imported.
4. Select the columns to be displayed in the report.
Note If toolbox cannot import the data, it will alert you to the discrepancy. The
number at the beginning of the error message corresponds to the line number in the
.csv file.
I/O Point list

The I/O point list report provides a list of all IO points. The points are referenced
from the device, rack, slot, board type, point name, and terminal board position.
Unused I/O
This provides a filtered version of the I/O report, specific to the points that do not
have any signal attached to them. If the I/O point has a signal name it will determine
if that points signal is being used in the application code.
Revision Log Report

This report displays the revision log of the selected document. Columns include:
Date/time stamp
Username
Computer name
Description
Enumerated Data Types Report
To create an Enumerated Data Types Report
From the View menu, select Reports, then Enumerated Data Types. The
Enumerated Data Types Options dialog box displays.
Select to include
all enumerated
data types in the
document.
Select to include
only data types
defined in Module
and Macro
Libraries.
Select to include
the signal name
currently
assigned to the
data type.
Control Spec Reports/IO Config

The I/O Config report provides a list of all IO points and their configuration. The
columns to include are configurable. There is a row for each configuration item for
an IO point. The configuration name and value are included.
Control Spec Reports/Signal Config

The Signal Config report provides a list of all Signals and their configuration. The
columns to include are configurable. If a signal is an array, there is a row for each
element. Some of the configuration items included are Scale, units, control constant,
used by code, used by IO, ED, alarm, event, hold, Display and setpoint limits, dead
band, alarm class, and Cimplicity Screen.
Block Pin Report

The Block Pin report provides a list of all block pins, by
Function/Module/Task/Block/Pin name, and includes its connection if any. Block
number and block comments are also included.
Tuning Variable Report

The Tuning Variable report provides a list of all signals and pins that are defined to
be Tuning Constants. See the section on Control Constants and Tuning Variable
view for more details.
2nd Language Report

The 2nd Language report provides a list of all signals along with both language
descriptions. The report includes fields that can be used for sorting and filtering.
These fields include: alarm (yes or no), event (yes or no), SOE (yes or no),
hold (yes or no), network (yes or no), and the path. This report can be exported
to a CSV file. The CSV file can then be edited to supply translated descriptions for
signals that require a translation. The CSV file can then be imported back into the
MarkVI configuration, along with the 2nd language descriptions. The import is
performed from the menu item, File/Import/2nd Language.
Orphan Signal Report
The Orphan Signal report provides a list of all signals and pins not driven by
software, I/O, or from a network. Control constants and tuning variables are not
included in this list.
Application Diagnostics
This section describes the application diagnostics feature of the controller.
Application diagnostics inform the operator and/or maintenance engineer why an
action cannot be started, or why it stopped. Application diagnostics are generated
from the same code running the process, so that you no longer need to maintain
separate code. Diagnostics can be viewed through HMI programs (Diagnose and
DLAN View).
Types of Application Diagnostics

There are four types of application diagnostics:
The four-character Triggered (TRGD)
abbreviation for the diagnostic
type can be used to filter the Broken run (RUND)
diagnostics that display on the Feedback (FDBK)
problem history screen.
Sequence (SEQD)
Triggered (TRGD)
There are three types of triggered diagnostics:
Start diagnostics are generated when an operator or piece of logic tries to
initiate an action not permitted. The start diagnostic indicates why the action
cannot be started. It lists either the permissives not satisfied and/or what is
calling for the action to be stopped.
Off diagnostics, which are the reverse of the start diagnostics, are generated if
something is requested to be turned off and off permissives are not met.
Normally with off permissives, the equipment is not being turned off, but is
being toggled to a second state (for example, a dual position solenoid.) The off
permissives are specified when there are permissives for going into the second
state.
Requested diagnostics are normally used when a process is going to be started
up after a downturn. When diagnostics are requested, no action is initiated.
Therefore, the operator can actually request the status to correct problems before
it is time to start the process. Diagnostics requested over the diagnostic network
only display the logic with permissives not met (the operator does not have to
filter through Im OK messages).
Control code can be configured to generate diagnostics when operator or
maintenance personnel request them.
Note When diagnostics are requested specifically from an HMI screen over
Ethernet, a response is always sent back exclusively to the requesting screen. This
assures the operator that all permissives are satisfied.
Broken Run (RUND)
A run permissive is a permissive Broken run diagnostics are generated when an action stops because it loses a run
required for a piece of permissive. The diagnostic tells what permissive(s) changed state, causing the action
equipment to run or for an to stop, and what permissives are required to start the action again.
action to continue.
Frequently, equipment or actions have two different sets of permissives:
Start permissives only need to be met when an action is initiated.
Run permissives need to be met for the action to be initiated and for the action to
continue.
Feedback (FDBK)
There are two types of feedback diagnostics:
When an action is both permitted and requested to start, but there is no feedback
after the expected amount of time. For example, a solenoid is energized to move
a piece of equipment. It is expected to pick up a limit switch when the piece of
equipment is in position. If the limit switch does not pick up in the expected
period of time, a feedback diagnostic is generated.
When this control code successfully turned something on and then later lost its
feedback. For example, a piece of equipment is moved into position so that it
picked up a limit switch. Later at some point, perhaps due to softening in the
hydraulic system, that piece of equipment moves off the limit switch. Since it
was not moved off by an operator or by control code, a feedback diagnostic
would be generated indicating that the equipment was no longer in the proper
position.
Sequence (SEQD)
Sequence diagnostics are generated from the code performing a sequence. There are
two types of sequence diagnostics as follows:
A merge time-out occurs when a sequence has parallel paths that merge back
together. When the sequence is defined, it is expected that the parallel actions will
complete within some pre-defined time from each other. If one of the actions has
completed, and the other action(s) has not, a merge time-out sequence diagnostic is
generated. At this point, the operator should determine if there is a triggered,
feedback, or broken run diagnostic from the piece of code that actually initiated the
control action.
This is a programming A handshaking fault is when one step of the sequence was trying to hand off
diagnostic that an operator in control of the sequence to the next step and a fault is detected. (This is normally
the field should never see. caused by the handshaking signal being written to someplace else in the code when it
should not be.)
Generating Application Diagnostics
When a diagnostic is generated, it can contain more permissive signals than those
connected to the block that detected the problem. The back-chaining feature traces
back through any other rungs that feed into the signals on the block. In the following
example, the permissive engine at rung number 80 (80:_PENG) controls moving a
drive in the forward direction. The run permissive pin on the block is RPRM. The
output coil of the RLD at rung 60 is wired into the run permissive. Also, one of the
inputs to the RLD in rung 60 is the output coil of the RLD at rung 23. If the drive is
running forward and loses a run permissive, the broken run diagnostic will not only
check all of the contacts in rung 60, but also all the contacts in rung 23. If the signal
Drive\Std1\RDYRUN in rung 23 drops out, causing the drive to stop running
forward, then the broken run diagnostic reports the signal that caused the drive to
stop.
Refer to the next section, Blocks contain several pins that control when diagnostics get generated, and how far
Control Blocks that Generate back the diagnostics program in controller will trace through code to find
Diagnostics. permissives not met. These pins are described below. Next to each pin description is
the actual spelling of that pin name as it appears on the block, such as reqdiag.
Request Pin (reqdiag)

The request diagnostics pin does not initiate any actions, but allows the operator to
check a block to see if permissives have been met. It only generates a diagnostic
message if a permissive is not met. This is a rising edge detect pin (the permissives
are only checked when the signal transitions from a low to a high).
Disable Pin (ddiag)
The disable diagnostics pin controls whether or not this block generates a diagnostic
message when a problem is detected. The pin can be tied to a signal so that the block
dynamically adjusts when it generates a diagnostic. For example, some mill
equipment is in auto mode. The block that controls the equipment when it is in
manual mode could be configured to not generate diagnostics when the equipment is
in auto mode. To do this, attach the auto_mode signal to the ddiag pin on the manual
control code block.
Disable Back-Chaining Pin (ddiagbc)

The disable diagnostics back-chaining pin controls how far back through the code
permissives not met can be traced. In the following example, rung 220 puts the entry
section in run mode when requested, as long as all permissives are met. If passline 1
equipment is used, passline 1 permissives must be met. If passline 2 equipment is
used, passline 2 permissives must be met. Therefore, if passline 2 is used, the
detailed permissives for passline 1 are not important. On rung 160, E_PL2 is on the
ddiagbc pin. Therefore, when rung 220 generates a diagnostic, if passline 2 is
selected, and passline 1 permissives are not met, the only passline 1 signal the
operator sees is PL1\perms\ok.
For example, the operator would not see the details of unhealthy drives in passline 1
(from rung 140). All the detailed permissives for passline 2 not met are shown.
Feedback Time Pin (fbtime)
The feedback time pin contains a number, which is the amount of time (ms) the
control block waits between when it asked to take an action until it expects to get
feedback that the action is complete. For example, a solenoid is energized to move a
piece of equipment. It is expected to pick up a limit switch when the piece of
equipment is in position. If the limit switch does not pick up in the specified period
of time, a feedback diagnostic is generated. A time less than zero is equivalent to no
time limit and keeps the control code from ever generating a feedback time
diagnostic.
Merge Time Pin (mrtime)

The merge time pin contains a number, which is the amount of time (ms) the
sequence merge block waits at the completion of a parallel merge. If there are
multiple paths of a sequence, they all merge together with a merge block. This merge
block knows which sequence steps merge together. It keeps track of the time from
when the first sequence step merges until the last sequence step merge is complete. If
this amount of time is longer than the specified merge time, a merge time sequence
diagnostic is generated. A time less than zero is equivalent to no time limit and keeps
the control code from ever generating a merge time diagnostic.
Disable Feedback Fault Pin (dfbflt)

The disable feedback fault pin keeps the control code from generating a diagnostic
when this control code successfully turns something on and then later loses its
feedback. This pin might be used when automatic control code moves equipment
into a specified position. Because the equipment is in position, the feedback is high.
If the operator switches into manual control and subsequently moves the equipment
out of position, use the dfbflt pin to not generate a diagnostic.
Control Blocks that Generate Diagnostics

There are two control blocks that either directly generate diagnostics or supply
information used in the diagnostics generated. They are BENG_D and BENG.
These blocks that directly generate diagnostics have two pins in common:
dispgrp (display group) pin is a three-character abbreviation for the function the
application code is performing. For example, the display group for automatic width
control might be AWC. The display group is used by HMI to determine which
diagnostics are displayed at which stations based on the functions the operator at that
station needs to monitor.
For some control blocks, the status pin uniquely identifies the block of code that produced the diagnostic. (The
status pin has state information same status signal should never be attached to more than one control block.) The
used in performing logic. 50-character signal description for the status signal is the one-line description the
operator sees to describe the diagnostic condition.
BENG_D
The BENG_D (Boolean engine with diagnostics) is a basic RLD, which performs
the logic specified by the contacts in the rung and sets the output coil accordingly.
This block can generate diagnostics in two different circumstances:
If the output coil drops out, it generates a RUND (lists which signal(s) caused
the output coil to drop out). It also back-chains to check for signals in any RLDs
that feed into this block.
If the signal on the request diagnostic pin goes True and the output coil is not
picked up, it generates a TRGD (lists the missing signals in order for the coil to
pick up).
Tip Normally a pushbutton (or other change in a logic state) is combined with
permissives to pick up the output coil. The output coil initiates an action in the mill.
To generate a diagnostic when the action is not permitted, wire the pushbutton to the
reqdiag pin, and also put it into a seal-in circuit in the RLD logic. The output coil
will seal-in around the pushbutton, if the action was initially permitted. In this
configuration, a diagnostic is only generated when the action is not permitted.
The BENG_D block has a disable diagnostics pin. This pin can be used to control if
a diagnostic message is generated or not, in the two circumstances described above.
This block also has a disable diagnostics back-chaining pin. This pin controls if the
diagnostic is traced back through the block to find the root signals or just report the
output coil.
The BENG_D block also keeps a time stamp whenever its signals change state. This
time stamp is used when a RUND is detected. The time stamps are checked to
determine which signals changed state immediately before the broken run condition
occurred.
BENG
The BENG (Boolean engine) is a basic RLD that performs the logic specified by the
contacts in the rung and sets the output coil accordingly. This block also has a
disable diagnostics back-chaining pin, which controls whether this block will allow a
diagnostic to trace back through it to find the root signals, or just report the output
coil. The BENG block keeps a time stamp whenever its signals change state. This
time stamp is used when a broken run diagnostic is detected. The time stamps are
checked to determine which signals changed state immediately before the broken run
condition occurred.
Runtime Data Flow
The following section describes how diagnostics are routed to the HMI.
The HMI must be online when A control block generates a diagnostic. The controller diagnostic code captures the
the message is sent out to state of all inputs to that block, storing the states in a diagnostic message. The value
capture and store the in the dispgrp pin of the block is also stored. The diagnostic message is sent out
application diagnostic. over the diagnostic network and then read by the HMI.
The OC2000 keeps the latest diagnostics and faults, based on the value in the
dispgrp pin. The OC2000 reads the diagnostic message and, if it was configured to
care about this dispgrp value, stores the message in a list.
The diagnostic item in the OC2000 list only identifies the problem of the control
action. However, additional information to find out exactly what permissives caused
the problem can be requested and sent back to the controller over the diagnostic
network.
The larger computer-based HMI systems maintain a long list of all diagnostic and
fault messages sent over the DLAN+ or Ethernet. Again, the diagnostic item in this
HMI list just identifies what control action had a problem. When the operator wants
additional information, the HMI sends this request with the original information back
to the controller. However, in this case, the message is sent back over Ethernet. All
further pieces of information for the operator about this diagnostic are sent over
Ethernet.
Diagnostic Data
In addition to the actual code configuration, diagnostic data is stored in the symbol
table (.sym file) and the SDB.
Symbol Table
The Build and Download Diagnostic data is stored in the application diagnostic symbol table and downloaded
commands are explained in the to the controller. The Build command in the toolbox allows you to build the symbol
section, Building Pcode and table at the same time the configuration code is being built. Similarly, the
Symbols. Download application code dialog box allows you to download the diagnostic
symbol table immediately after the code is downloaded.
The symbol table contains two main pieces of data:
Major revision when code was built
Token numbers (addresses), and associated signal names and signal descriptions
Note When a diagnostic condition is detected, the identified permissives are

referenced by these addresses. The symbol table provides the correlation between the
address and signal name.
The diagnostics function in the controller only uses data from the symbol table when
the major revision of the code that the symbol table was built against matches the
code currently running in the controller. The symbol table and code must match for
the signal addresses in the symbol table to be correct.
Tip If a diagnostic, such as: token # 7074 can't resolve name, displays on the
HMI or OC2000, from the toolbox, rebuild the diagnostic symbol table from a .ucb
that matches what's running in the controller and then download the new diagnostic
symbol table. Also, perform searches using the Finder/Text/Address tab.
Therefore, every time a major revision of the code occurs, the symbol table must
rebuild and download. When a new symbol table is downloaded, controllers do not
need to be stopped.
Tip The toolbox allows you to continually build and download the symbol table.
To automatically build, from the Device menu, select Build and the Build symbol
table option. To automatically download, from the Device menu, select Download/
Application Code and the Download symbols option.
To view the major and minor revision

If the toolbox is connected to the
controller, it also shows the 1. From Outline View, click to turn on Tracking.
major and minor revision of the 2. Click the controller name. The major and minor revision of the code currently
code in the controller. running displays in the Summary View.
Any major revision of the code Major revision of the code changes include:
requires you to rebuild and
Status_S pages changes (even through getting information from the database)
download the diagnostic symbols
table. Genius changes (besides just attaching a different signal to an existing I/O
point)
Point is added to NOVRAM
Network is added or deleted
Signals were packed
Note When extra signals are added that might be in a diagnostic, you must rebuild
and download the diagnostic symbols table, even if the code did not change the
major revision.
Put Diagnostic Symbols into the SDB

When diagnostic symbols are put into the SDB, the data is obtained from the .m6b
currently open in the toolbox (not from the symbol table). The main symbol data
includes signal names and signal descriptions token numbers. Symbols should be put
into the SDB with every build.
Dynamic Data Recorder (DDR)
The DDR feature collects data when specified trigger events occur. The advantage
of using DDRs over capture blocks is that DDRs can be reconfigured without having
to download application code to the controller. This enables changes to be made to
the DDRs without disrupting the controller during runtime. Up to 12 DDRs can be
configured for the controller.
Note DDRs can only be used by Mark VI Runtime V04.00.00C or newer. Also, due
to memory constraints, controller boards that precede the UCVE cannot use DDRs.
Create and Delete DDR

To insert a DDR
1. From the Outline View, click on the Dynamic Data Recorders item to
highlight it.
2. From the Edit menu, select Insert First.
Or, click the right-mouse button and select Insert First.
3. Once a DDR exists, insert another by following the same steps, but selecting
Insert Next.
To delete a DDR
1. From the Outline View, select the DDR to remove.
2. From the Edit menu, select Delete.
Or, click the Delete key.
Configure DDR
To configure a DDR
1. From the Outline View, highlight the DDR to configure.
2. From the Edit menu, select Modify. Or, click the right-mouse button and select
Modify. The Dynamic Data Recorder dialog box displays.
Enter the Name of the Enter the name of the Status
DDR (use standard Signal (integer signal) used to
file name characters). store the DDR status.
Enter a string Description (up to 50

characters) of the DDR.
Enable Signal is used to manually

enable the DDR.
Check Auto Enable to automatically

re-enable the DDR after 60 seconds.
Period Multiplier specifies the
intervals for data collection.
Total Samples specifies the number of

DDR samples to record when the
trigger condition occurs. This includes
Pre-trigger Samples.
Condition is the comparison

condition that helps qualify when the
trigger occurs (refer to the options
below).
Type defines the way the trigger is
detected. Selecting edge means that the
DDR must observe the trigger signal in
the false condition at least once prior to
observing in the true condition.
Enter the signal to apply the trigger condition, type Compare Value is the
and compare value that determine if a trigger has threshold value against which
occurred. the trigger signal is compared.
Trigger Signal Condition options

eq equal to compare value
ge greater than or equal to compare value
le less than or equal to compare value
lt less than compare value
ne not equal to compare value
Note If the trigger signal is a Boolean type, eg and ne are the only available
conditions.
Status Signals
Status signals, which indicate the status of the associated DDR, are used by the Data
Historian to determine when to upload the data. Status signals are always integers.
All 12 status signals must be assigned and placed on an EGD page for validation to
be successful, even if no DDRs are used. This is done because the status signals are
set up with the application code download. Adding the status signals initially
eliminates downloading application code when adding a new DDR.
To add Status Signals
1. In the Outline View, click on Dynamic Data Recorder to highlight it.
2. From the Edit menu, select Modify. Or, click the right-mouse button and select
Modify. The Dynamic Data Recorder Status Signals dialog box displays.
Source File indicates

which .tre file the DDR
setup information has
been exported to.
3. Click Browse to assign a signal. The Signal Selector dialog box displays.
4. Select the signal to be used as the status signal. Click OK.
Import and Export DDR
To import a DDR from a .tre file
1. From the File menu, select Import. Or, select the Import button . The
Import File dialog box displays.
2. From the Import File dialog box, select the .tre file that corresponds to the
DDR you wish to import. Click OK.
Note If the .tre file being imported contains the formatting flags %d or %n, then %d
will be replaced by the device name, and %n will be replaced by the Mark VI
devices Design Memo (DM) number. This is a GE Power Systems project number
whose value can be accessed by editing the device item and going to the Customer
Information tab.
To export a DDR to a .tre file

1. From the Outline View, highlight the DDR to be exported.
2. From the File menu, select Export, then Selected Item. Or, click the right-
mouse button and select Export Selected Item.
3. When the Export dialog box displays, click Save.
Note An Export All includes all the DDRs in a single .tre file.
Add Signals
Signals can be added to a DDR. When a trigger occurs, these signals are collected by
the buffer and subsequently uploaded by the Data Historian and/or Trend Recorder.
Each signal is sampled for the total number of samples configured. This means that if
the DDR is set up to record 100,000 samples with three signals assigned, 300,000
items will be acquired. Up to 96 signals can be assigned to each DDR.
Note There is a 12-MB size limit on the memory that can be allocated to the DDRs.
If this memory allocation is exceeded, an error is reported during validation.
To add a signal
1. In the Outline View, highlight the DDR that you wish to add a signal to.
select Insert First.
The Dynamic Data Recorder Signal dialog box displays.
Enter the signal name

or click Browse... to
search for and select
a signal.
3. Click OK to insert the signal.
Update DDR
DDRs are updated separately from the application code download.
To update a DDR
1. In the Outline View, select Dynamic Data Recorders, then click the
Validate button .
2. From the Device menu, select Download, then Update Dynamic Data
Recorder. Or, click the Update Dynamic Data Recorder button .
Chapter 4 Finder
Introduction
This chapter defines the features of the Finder. The Finder is a separate window in
the toolbox, which contains several useful find tools. It can help you find items, such
as text, overrides, differences, and signal/variable usage from the different types of
devices.
Note The SDB Browser is another window that finds items, such as signal usage,
system topology, signals on the SDB, and more (refer to GEI-100506).
Section Page
Using the Finder .......................................................................................................4-2
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 4 Finder 4-1

Using the Finder
To use the Finder
1. From the View menu, select Finder. The Finder window displays (see the next
Or click .
section, Finder Window).
2. Select a target from the drop-down Target List. (All loaded targets are listed.
The default target is the current device.)
3. Select a tab according to the type of search desired.
4. Enter each field of the tab (described in the next section).
5. Click . Once the search completes, the Output View and Status bar
display the results.
Tip By default, the Finder closes when the Find button is clicked on or when you
click any part of the screen outside the Finder Window. Click to keep the Finder
open.
Finder
Title Bar
To resize the window:
Toolbar
Target List 1. Click the window to
Tabs highlight it.
2. Point the mouse
arrow on any side of
the window until the
double arrow displays.
3. Click the arrow and
drag the window to the
desired size.
Output
View
Status bar
4-2 Chapter 4 Finder GEH-6403L Toolbox for a Mark VI Turbine Controller

The Finder target determines the device and area of the search. When the Finder is
activated, it automatically selects the current device as the target and displays it in
the Title bar. A target performs various finds:
Target Can find
SDB Signals
OC2000 Text
AcDcEx2000 Text, variable usage, override, difference
Innovation Series drive Text
Innovation Series and Mark VI controller and System Information Text, signal usage
EX2100 Text, signal usage
Located below the Title bar is the toolbar.
Click To
Hold the Finder Window open. If this pushpin displays, the Window closes when the area outside the
Finder Window is clicked. Click the pushpin to keep the Finder on top of the Device Window, even when
you click outside the Finder Window.
Close the Finder Window. This pushpin displays when the pushpin above is clicked. The Finder Window
remains opens when the pushpin is in this position (even when working in another window).
Goto an item in the Outline View. Highlight an item in the Output View, then click this button to find it in
the Outline View. Double-click an item to edit it.
Hide the tabs and make the Finder window display only the Output View.
Target Finds
The Finder contains tabs that display according to the device selected in the drop-
down box, Target List and the tab selected (type of find). The following sections
describe each tab.
Refer to the SDB Browser in The Text/Address tab allows you to search for all text and address usage. It is
GEI-100271. available on all targets, except the SDB. The Signals/Variable Usage tab allows you
to search for signals/variables in a controller, AcDcEx2000, or System Information.
Signals apply to a controller
The Override tab and Differences tab display only when the target is an
or System Information target.
AcDcEx2000 device.
Variables apply to an To perform a find
AcDcEx2000.
1. From the Outline View, click an item to search.
2. From the toolbar, click . The Finder displays to begin your search. Select
the desired tab as described in the following sections.

Text/Address
Enter the text to find.
The drop-down box allows

you to access previous
finds.
Click here to include all

note message boxes in
the find.
Click Find to start the find.
All text found displays in

the Output View.
Method allows you to qualify the find by selecting one of the following from the drop-down
box:
Anywhere In matches items that contain the find text anywhere within their text.
Begins with matches items whose text begins with the find text.
Exact matches items who text is exactly as the find text.
Using wildcards (*,?) allows the characters (* and ?) to specify multiple and single match-
anything characters.
Address is for the ACDCEX2000 and matches items who address is the same as the find
text. This method is also useful for finding controller signal names related to token numbers,
such as diagnostic that have an out of date symbol file.

Signal/Variable Usage
Select the target

from the drop-down
list.
The Track Highlighted

Item box is checked by
default. This indicates
that the currently
highlighted item in the
Outline View is the
signal variable to find.
The signal/variable items

that are found display in
the Output View.
Note When a different item is selected in the Outline View, the Find is performed
again. Click the option Track Highlighted Item to uncheck it and prevent the find
from executing each time the Outline View item changes.

Notes

Chapter 5 Batch Operations
Introduction
This chapter describes the Batch Operation mode. This mode performs a variety of
functions, such as Validate and Build, on any number of files of different device
types. This is especially useful when recreating the system database or when the
process contains multiple devices.
Section Page
Batch Operations File ...............................................................................................5-2
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 5 Batch Operations 5-1
Batch Operations File
File name(s) must be added to a new batch operation or names can be edited in an
existing .bld file.
To create a batch operations file
From the File menu, select New. The New dialog box displays.
Or click
Click the tab, Utilities.
Select Batch
Operations
File.
Click OK.
The Batch
Window
displays.
Toolbox Command Line Options
The toolbox can be run from the command line and perform a number of specific
operations. The command line operation allows for performing actions with
automation. A listing of the command line operations is shown below. Command
line options can be sepecified with a dash (-S) or with a forward slash (/S). All
descriptions and examples are shown with the forward slash.
5-2 Chapter 5 Batch Operations GEH-6403L Toolbox for a Mark VI Turbine Controller
The various command line options in the toolbox are as follows:
Command Line Definition Usage Example
/S Disable the Splash Screen when Toolbox/S
starting toolbox
/U Sets the User ID. The command
should be followed by a user
name (3 Chars)
/R Performs batch operations Toolbox /R <file Toolbox /R C:\Site\Master\Batch1.bld
name> (.bld - batch operations file)
/SupressUI Hides the toolbox window
/ControlSpecCsv Generates IO Config Report.csv Toolbox/ControlSpecCsv Toolbox /ControlSpecCsv
and CSP Signal Report.csv files <file name> C:\MkVI1.m6b (should be .m6b file.)
/IoReportCsv Generates IO Report.csv file Toolbox /IoReportCsv Toolbox /IoReportCsv C:\MkVI1.m6b

<file name> (This file should be .m6b file.)
/ControlSpecCsvV9 Same as /ControlSpecCsv. but
the report file is generated in
Version 9 format
/IoReportCsvV9 Same as /IoReportCsv. but the
report file is generated in Version
9 format.
/ImportOrderingDrawing Imports Ordering Drawings Toolbox <Device file Toolbox C:\Mkvi1.m6b
name> ImportOrdering /ImportOrderingDrawing
Drawing <Drawing file C:\Drawing.tsv (Ordering drawing file
name>
should be .tsv or .csv file.)
/ImportControlConstants Imports a Control Constant file to Toolbox ImportControl Toolbox /ImportControlConstants
an .m6b file. Constants <Device file C:\Mkvi1.m6b
name> <Control Constant C:\ControlConstants.csv
file name>
Toolbox Toolbox ImportControlConstants
/ImportControlConstan C:\ControlConstants.csv
ts <file name>
/ExportOSMReports Generates the following .csv files Toolbox Toolbox /ExportOSMReports
- Signal List Report.csv /ExportOSMReports C:\MkVI1.m6b (The file should be a
<file path> .m6b file.)
- Alarm List Report.csv
- Event List Report.csv
- Scale List Report.csv
- Enumerated Data Types
Report.csv
- EGD Network Report.csv
- Control Constants Report.csv
- IO Point List Report.csv
- SOE Report.csv
/BatchCsv Executes a Batch CSV file Toolbox /BatchCsv Toolbox /BatchCsv C:\Batch1.csv
<file name> (The file should be a .csv file.)
/Q Runs batch file in quiet mode. Toolbox /BatchCsv Toolbox /R C:\Batch1.bld /Q
Use with /R and /BatchCsv <file name> /Q Toolbox /BatchCsv C:\Batch1.csv /Q
commands
/Version Writes the version of the /Version <Device file /Version C:\Site\MkVI1.m6b
particular device file to an output path> <Output file C:\Site\version.txt
file. path> The input file should be a device file.
The output file contains the version
number of toolbox that last wrote to it.
Number is in the form: V11.02.03C
Batch Window
File Names is the list of files upon which the commands are
performed. The files are opened in the order shown in the list.
Use the edit buttons to modify current positions. Add Files(s)...inserts
the names of files in
the file names list.
Remove deletes the

highlighted name(s)
from the file names list.
Copy makes an
additional copy of the
highlighted files in the
file names list..
Move Up moves the

highlighted files up the
file names list.
Move Downmoves
the highlighted files
down the file names
list.
If an error occurs:
Stop stops the batch

operation.
Continue continues the

batch operation at the
Add inserts the commands highlighted Remove removes the next command.
the Available Commandslist into the highlighted from the Available
Selected Commandslist. Commands list. Next File continues the
batch operation at the
The window at the bottom of the screen next file.
provides status information, including errors.
Configure a Batch Operation
To add to the File Name list
From the Batch operations dialog box, click Add. The Add File dialog
box displays.
Select the file(s)

to be added to the
File Names list.
For more information, refer Tip If you are using the Checkin/Checkout utility, make sure all files added to the
to Chapter 6, File File Names list are checked out, in Exclusive (read/write) mode. Otherwise,
Checkin/Checkout. operations may not work and not be found until the Error Log file is examined.
To configure a batch operation

1. From the Batch operations dialog box, edit any File Name(s) with the
command buttons (Move Up, Move Down, and Change).
2. Select all commands to be performed on each file.
3. Select an Error option.
4. Click Save to save the Batch Operation to a .bld file.
5. Click Start to run the Batch Operation.
Run a Batch Operations File
Run a Batch Operations file in one of three ways:
1. Click Start in the Batch Window.
2. Select a command prompt.
3. Open a .bat file.
To run the toolbox from the command prompt, type toolbox and the name of the .bld
file. If the directory of either the toolbox or the .bld file is not in the path, the
directory names must be included in the command line.
Two command line options are available:
The -r indicates that the batch should run immediately and not wait until the
Start button is pressed.
The -u_ _ _ (three-character user ID) is used to enter a user ID so that the Enter -
User ID dialog box will not display before each file is opened.
Running a batch file from the command prompt works the same as the toolbox
interactive mode. The toolbox opens, runs, and completes the Error log. The Error
log (.log) can be viewed from a text editor.
A batch operation can also be initiated from the command line using a .csv file
which had been exported from a batch build (.bld) file. The batch operation can also
be run in quiet mode using the Q option (as shown below). In quiet mode, the
toolbox will run minimized, and no message boxes will pop up. All operation
information will be written to the log file. The log file will be created at the same
location in which the command line is run. The command line information is shown
below:
BatchCsv or /BatchCsv - Runs a Batch .csv file.

Usage: Toolbox BatchCsv <file name> or Toolbox /BatchCsv <file
name>
Example: Toolbox /BatchCsv C:\Batch1.csv (should be a .csv file).
Q or /Q - Runs a Batch file in quiet mode.
Usage: Toolbox BatchCsv <file name> Q or Toolbox /BatchCsv
<file name> /Q
This option can be used with both /R and /BatchCsv commands.
Example: Toolbox /R C:\Batch1.bld /Q

Toolbox /BatchCsv C:\Batch1.csv /Q
System Make Wizard
The System Make wizard populates the Batch File with the necessary files and
commands to prepare all project files for download.
To run the System Make Wizard
1. From the Edit menu, select System Make Wizard.
2. Specify the root directory of the project configuration files.
3. Click OK.
The wizard scans all folders beneath the root folder and adds all relevant files to the
file names list. The wizard also selects all necessary commands for those files.
Note Check the file list after running the wizard to make sure that there are no
unnecessary files included in the list.
Batch Error Log File
During a Batch Operation, a log window displays the status messages produced
during the operation. This log is written to a file with the same name as the .bld file
and the extension .log. Any errors that occurred during the operation are also
displayed here.
Open and Save Batch Operations File

To save a .bld file
Press the Save button on the Batch Operations dialog box. From the Save
dialog box that displays, enter a file name.
To open an existing .bld file
From the File menu, select Open. From the Open dialog box that displays,
select the desired file name and directory.
Import and Export Batch Operations File

Batch Operations files may be modified using text editors, then imported or exported
by means of Command Separated Variable (.csv) files.
To export a .csv file
From the File menu, select Export to CSV. From the Save dialog box that
displays, select the desired file name and folder.
To import a .csv file
From the File menu, select Import from CSV. From the Open dialog box that
displays, select the desired file name and folder.
Chapter 6 File Checkin/Checkout
Introduction
This chapter describes the Checkin/Checkout utility, which allows you to share files
contained in a master location. The files in the Master Directory are checked out into
the specified Local Directory in either Share read (read-only) or Exclusive
(read/write) mode.
Initialization
Note This utility does not prevent the File Manager from overwriting the files in the
Master or Local Directory.
To initialize the Master Directory

1. From the File Manager, select a directory to maintain the Master files.
2. Copy all desired files into this Master directory.
3. From the Program Manager, double-click the Checkin/Checkout icon. The
Checkin/Checkout Utility dialog box is displayed.
4. Select the Master Directory and Local Directory.
When the utility is run for the first time, a lock (.lck) file and text (.txt) file are
created in the specified Master Directory. The user.lck file keeps the current lock
state of all files processed by this utility. The userlock.txt keeps track of all the files
in the Lock File Data screen.
The Checkin/Checkout dialog box contains two directories to manage shared files.
The fields and commands are as follows:
Local Directory and Master Directory display a list of files and the current lock
status of each file, based on the List of Files Type list box. Browse allows the
user to select a drive and directory for both the Master and Local Directory.
List of Files Type provides a choice of filenames to display, based on the filename
extensions in parentheses. The default extension is All Files (*.*).
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 6 File Checkin/Checkout 6-1
Click Checkout to copy the highlighted file(s) Details displays the current Lock File
in the Master Directory list to the Local Data (File, Lockstate, Computer: User,
Directory list. Directory access must be Date/Time) of all files that are processed
Shared read file(s) are
granted. by this utility.
copied to the Local
Directory as read only files.
These file(s) are displayed
with an R after the file
name. The file(s) can be
copied, even if locked by
another user. Any attempt
to write to the file causes a
Permission denied error
message.
Exclusive files(s) are
copied to the Local
Directory as read/write
files. This denies anyone
else access to check the
file out in Exclusive mode.
Click to copy the highlighted

file(s) in the Local Directory
to the Master Directory.
Directory access must be
granted.
Note: The highlighted file
must be in Exclusive mode
or it must not exist in the
Master Directory. The file is
set to read only (R) in the
Master and Local
directories after copying. Select the type of file(s) to Access forces the lock of the selected Master Directory to
Other users can now check display in the Master Directory you. Use this only if no other users are using this utility and
out this file. list. the lock is granted to another user. This will happen if the box
is turned off or the task is terminated while running the utility.
Unlock removes the lock on the currently highlighted file(s) in
the Master Directory. This removes the file(s) from being
controlled by the utility. Unlock makes the master copy and
the local copy of the file accessible.
Note The Unlock command is unconditional (the file is not copied or changed in
any way). The user is responsible for managing the file. The read attribute is left
enabled on the master file.
6-2 Chapter 6 File Checkin/Checkout GEH-6403L Toolbox for a Mark VI Turbine Controller
Chapter 7 Configuring System
Information
Introduction
This chapter provides instructions for using the toolbox to configure System
Information. System Information is used to configure information global to a project.
This information includes data such as scale factors, CIMPLICITY Human-
Machine Interface (HMI) resource names, enumerations, and alarm classes.
Once the configuration for System Information is defined, the data is put into the
System Database (SDB) for access by other drives, controllers, and interfaces.
Section Page
Working with System Information Files ..................................................................7-2

Concepts ...................................................................................................................7-2
Configuration............................................................................................................7-3
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 7 Configuring System Information 7-1
Working with System Information Files
System Information is configured using two types of files:
Binary working files (.syb) contain an exact copy of the configuration used by the
toolbox. Users generally work from .syb files.
Project files (.prj) are text files containing property and system configuration
information. The files transport the System Information to different versions of the
toolbox.
Concepts
There is no hardware item for System Information (such as the drive or controller) in
the toolbox. System Information is used primarily to configure and manage
information global to a project. This information includes Scale Definitions, and
resource names (Type Definitions).
Scale Definitions
The ownership of scale Scale definitions are scale factors associated with signals. They are used to
definitions, those of System
Information as well as of Scale raw I/O into engineering units used internally by the blockware in a
controller or CIMPLICITY HMI system.
other devices, is maintained
in the database. Provide unit, precision, and limit information for a signal.
Alarm Classes
An alarm class, which defines the attributes for a classification of alarms, is created
for each group of related alarms that share a common priority and color scheme.
Type Definitions
Resource Names
System Information defines Resource names are stored within a special Type Definition named Resource. Any
and puts resource names into signal put into the database can be associated with one resource name (just like a
the database. This makes the signal can be associated with a scale definition). This resource name groups signals
resource names available to used by the CIMPLICITY HMI system. When some systems import signals into
other devices that can then CIMPLICITY, the resource name is used to determine which signals get imported.
assign them to appropriate (For example, you can import all the signals that have a resource name of Entry.)
signals. The resource name can also be used as a filter for displaying alarm/event data on a
CIMPLICITY HMI.
Enumerations
Enumerations are defined as type definitions. Properly defined enumerations are
stored in the SDB when a System Information Put Into Database command is
performed. To qualify as an enumeration, the Type Definition must be Enumeration
with a Base Datatype of Int. If a second language has been defined, then for each
enumerated field, there are text boxes for both languages. The enumerations is the
SDB are imported into the CIMPLICITY system when the HMI Device performs a
7-2 Chapter 7 Configuring System Information GEH-6403L Toolbox for a Mark VI Turbine Controller
build. One language enumeration description over the other is imported into
CIMPLICITY depending on which language is selected in the HMI Device.
Measurement System
The names are entered in the The Measurement System defines the names of the two measurement systems. The
System Device Name dialog names are used for dual scales when creating a scale definition. Measurement
box. Refer to the section, System 1 should be the primary measurement system used in the project. The default
Configuration. name for System 1 is US, and the default name for System 2 is Metric.
System Overview
The system overview provides the ability to access various configuration files and
other executables through an animated drawing interface. Requisition engineering
provides the overview drawing in a metafile format to be used by the Toolbox.
Configuration
Create/Modify System Information

To create System Information
Or click 1. From the File menu, select New. The New dialog box displays.
2. From the System Configuration tab, select System Information and click
OK. The System Information window is created with a temporary name,
such as sys1. The Outline View contains these items:
To modify System Information name

1. From the Outline View, click the name to highlight it.
Or double-click the name. 2. From the Edit menu, select Modify. The System Device Name dialog box
displays.
Enter the desired Measurement
System names (12 character limit) for Turbine System must be checked to
System 1 and for System 2. The apply Measurement Systems and the
names displayed are the defaults. Dual Language Definition.
Select the desired language

from the drop down boxes.
Language 2 is required for
turbine systems that use the
Language Translation feature of
Turbine Controls Interface (TCI).
This feature allows alarm
messages and events to be
displayed in either Language 1
or Language 2. These definitions
are also used by the HMI device
when importing signals into the
CIMPLICITY HMI system.
Note: Both the Measurement System configuration and the Dual Language
Definition are stored in the SDB when performing the command, Put into
Database for the System Information.
Insert/Modify Scale Definitions
Scale definitions can be associated with signals. They are used primarily to scale raw
I/O into engineering units used internally by the blockware. For the controller, scales
can be created in the toolbox and then put into the database.
Tip On many large processes, scales are defined in System Information, allowing
all controllers to use the global scale. To modify a scale, you can immediately open
the system information file instead of searching all the controllers to find the scale.
To insert scale definitions

1. From the Outline View, select Scale Definitions.
Or use the shortcut keys, Shift Or, click the right-mouse button and select Insert First. The Scale definition
+ Insert. dialog box displays.
To modify scale definitions
1. From the Outline View, select the scale definition name.
Or double-click the scale 2. From the Edit menu, select Modify. The Scale definition dialog box
definition. displays.
Scale Names are defined in the Measurement System dialog box. If
multi-scales are desired, enter the primary scale name in the textbox
for System 1. Refer to the section, Measurement System.
Enter the Minimum

and Maximum values
of each system and
Raw to provide the
conversion informaton.
Enter a description of
the scale definition
(50-character limit).
Enter the Unit names for each system (five-character

limit). Select the Precision from the list boxes.
Resource Type Definitions
Refer to Chapter 3, the Resources are defined as type definitions. The resource type definition allows the
section Type Definitions. CIMPLICITY HMI to group signals. System Information puts the resource name
into the SDB for other devices to get the resource names and associate them with
signals.
Resource is always of Basic Data type: String. When resource names are first
defined, it is not necessary to assign a value to the value name (refer to the resource
Type definition dialog box). This is done automatically when System Information
puts the data into the database. For example, the following list displays a set of
resources entered without a value.
After System Information puts its configuration into the SDB, values for each
resource name are assigned automatically by the database.
Enumerations
Enumerations are defined as type definitions. Properly defined enumerations are
stored in the SDB when a System Information Put Into Database command is
performed. To qualify as an enumeration, the Type Definition must be Enumeration
with a Base Datatype of Int. For each enumerated field, the Note field must be filled
out with not more than 32 characters. The reason for this rule is that the Note field is
multilingual and is used as the enumerated text field in CIMPLICITY.
The following is an example of an enumeration.
The enumerations are placed in the database with the Put into Database
command, which makes them available for use as a datatype by signals.
The HMI configuration will import all enumerations in the SDB into the
CIMPLICITY system. Any signals on EGD that use one of the global enumerations
as a datatype will have the corresponding CIMPLICITY point associated with the
CIMPLICITY enumeration.
Alarm Classes
To insert an alarm class
1. From the Outline View, select Alarm Classes.
select Insert First. The Edit Alarm Class dialog box displays.
Enter the alarm class

Name (five-character
limit).
Enter the alarm class

Priority (0 through 9,
with 0 being highest).
Enter a Description of
up to 50 characters, if
desired.
Select Foreground
and Background
colors for the Normal
State, the Alarm State,
and the Acknowledge
State.
System Overview
The system overview is used to graphically access the configuration files and
programs used in a system. The hyperlinks on the drawing display the associated
binary configuration files.
Configure System Overview Settings
To configure System Overview settings
1. From the Outline View, select the System Overview item. The Edit Overview
Settings dialog box displays.
Select the metafile

to be associated
with the System
Overview.
Click Add to
enter target
information into
the Edit
Overview Target
Settings dialog
box.
2. Click the Add button to display the Edit Overview Target Settings dialog
box.
The target
Name is the
name as it
appears on the
windows
metafile.
Two lines of
text can be
entered to
describe each
target.
Enter the
executable or
binary
configuration
file to be
associated with
the target.
The Summary View then displays the metafile with the target text. The command
associated with the target can be run by double-clicking the hyperlink in the metafile.
Put Data into Database
To make configuration information available to other devices through the system
database, you must use the Put into Database command.
To put data into the database
From the Device menu, select Put Into Database. A warning message box
displays to confirm the operation.
Notes
Chapter 8 Graphics Window
Introduction
This chapter describes the Graphics Window, which is used to create custom
graphics interfaces for customer and process requirements. It describes how to draw
the graphic objects, then attach animation and input data to the objects.
Section Page
Graphics Window Objects........................................................................................8-2

View Signal Summary..............................................................................................8-9
Settings ...................................................................................................................8-10
Draw Commands....................................................................................................8-14
Animate Objects .....................................................................................................8-17
Input Fields.............................................................................................................8-27
Using Graphics Window Objects ...........................................................................8-32
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 8 Graphics Window 8-1
Graphics Window Objects
A Graphics Window is created by drawing graphics objects, then attaching
animation and/or inputs to the objects, as follows:
Object Animation produced

Line Color and Property
Rectangle Bar graph, Trend, Color, and Property
Circle Color and Property
Ellipse Color and Property
Polygon Color and Property
Polyline Color and Property
Text Property, Numeric, Text, and Color
Insert Object Property, Numeric, Text, and Color
All drawing objects can be attached to the following input type(s) for entering data:
Numeric
Set point
Initial value
Text
Toggle
Hyperlinks
In addition, inserted ActiveX Control objects can have Event inputs.
8-2 Chapter 8 Graphics Window GEH-6403L Toolbox for a Mark VI Turbine Controller
Create Graphics Window
To create a Graphics Window
The Graphics Window 1. From the File menu, select New. The New dialog box displays.
displays as a detached view
2. Click the tab Utilities, select Graphics Window, then click OK. The
that can be moved and sized.
Graphics Window displays and creates a graphic file (.grw). Both the
configuration file and the .grw must be opened for the Graphics Window to
function. Therefore, a message displays if there are no controllers or drives
loaded.
Note If more than one controller and drive is open, you must select the one to
configure for the current Graphics Window. Refer to the next section, Select Device.
Select Device
The default file name, Change the current device within the Graphics Window by selecting Device from
graphics_.grw can be the Draw menu.
changed when it is saved.
This dialog box lists all

open devices.
Click on the desired device

for this graphic.
Click OK.
Menu Bar
The File, Options, Window, Create custom graphics and animation in the Graphics Window work area using the
and Help menus are the same Menu bar or toolbar. Some menu commands, which are different from the regular
as the toolbox. toolbox menus, are described in the following sections.
Edit Menu
The Edit menu allows you to modify graphic objects, and select animated and input
objects with the following commands:
Or click . Cut removes the selected object and places it on the clipboard.
Or click . Copy duplicates the selected object and places it on the clipboard.
Or click . Paste inserts the object from the clipboard into the current file.
Or click . Delete removes the selected objects from the current file.
Or click . Push Back sends the selected object(s) behind other overlapping objects.
Or click . Pull Forward sends the selected object(s) in front of other overlapping objects.
Align contains the following options:

Top, Bottom, Left, Right move the objects to align the top, bottom, left, or
right edge with the corresponding edge of the last object selected.
Vertically Space evenly spaces the objects within the area of the top of the
highest selected object and the bottom of the lowest selected object. The top-to-
bottom order of the spaced objects remains the same.
Horizontally Space evenly spaces the objects within the area of the left of the
left-most selected object and the right of the right-most selected object. The left-
to-right order of the spaced objects remains the same.
Match Width, Match Height resizes all selected objects to match the size of
the last object selected.
Group creates a single object from all selected objects. You can perform all normal
operations on this single persistent object. When a group object is selected, Group
will convert the group back into multiple individual drawing objects.
Select Animated highlights all animation objects in the Graphics Window.
Select Input highlights all input objects in the Graphics Window.
Signal Substitutions creates an alias for signal names used in animation/
inputs.
Allow Editing allows you to make changes to the Graphics Window. This option is
enabled by default (indicated by a checkmark next to the option). Unchecking this
option also allows hyperlinks to operate while the device is offline. The setting for
this option is saved for each Graphics Window individually.
View Menu
The View menu allows you to toggle displaying the Toolbar and Status Bar.
Toolbars contains buttons to provide quick access to many commands and features.
There are five toolbars: Main, Drawing, Animation, Input, and Properties.
Status Bar displays information about a command, operation, or insertion point.
Online Substitution displays the current signal name aliases while connected to
a device (refer to the section, Signal Name Substitutions).
View Signal Summary displays a list of signals in use in the Graphics Window,
allowing quick changes.
Draw Menu
The Draw menu allows you to draw with the following commands.
Select selects an object(s). Click the object or press and hold the mouse button to
Or click . draw a box around the desired object(s). Multiple objects can also be selected by
pressing the Ctrl key while clicking on the objects. Then use one of the commands
listed below to create objects and backgrounds for the graphic interface.
Line creates a single line.
Or click .
Rectangle creates a box-shaped object.
Or click .
Circle creates a round object.
Or click .
Ellipse creates an oval object.
Or click .
Polygon creates a closed object with three or more sides.
Or click .
Polyline creates an open object with three or more sides.
Or click .
Text creates numbers, letters, and symbols.
Or click .
Insert Object creates ActiveX controls.
Or click .
Insert Picture inserts a Windows metafile (.wmf) into the currently selected
Or click . rectangle object.
Device allows you to select the device for this graphic file (refer to the section,
Select Device).
Or click . Online connects the Graphics Window to the device over the network.
Animation Menu
The Animation menu allows you to use graphics objects to display signal
information with the following commands.
Or click . Numeric displays the value of a signal in numerical form.
Or click . Bar Graph displays the value of a signal in bar graph form.
Or click . Trend displays the recent records of up to eight signals on a trend graph.
Or click . Text displays text strings depending on the value of the source signal.
Or click . Color changes the color of the attached object depending on the value of the source
signal.
Or click .
Property changes any property of the attached object based on the value of the
source signal.
Input Menu
The Input menu allows you to use graphics objects to change data online with the
following commands.
Or click . Numeric enters numerical data into a signal.
Or click . Setpoint sets a signal to an assigned value.
Or click . Initial Value makes the current signal value the initial signal value for all the
signals specified.
Or click .
Text selects a text string to define the value sent to the signal.
Or click .
Toggle inverts a signal from 0 to 1 or 1 to 0 (toggles state True/False).
Or click .
Event sets a signal as a result of an ActiveX Control event.
Or click .
Hyperlink... opens other applications, toolbox files, or help files.
Settings Menu
The Settings menu allows you to set the following options to draw objects and
backgrounds.
Frame Size and Options allows you to set the height, width, background color,
and background image of the current screen. No objects can be drawn outside the
frame. Additional options include drawing an alignment grid, snapping objects to the
alignment grid, and suppressing undefined signal warnings when going online.
Or click . Pen Color sets the current pen color. This color is used for drawing the lines in all
objects. This includes the outside border around rectangles, circles, ellipses,
polygons, polylines, and text.
Or click . Pen Width sets the current width of all lines drawn (all objects except text).
Or click . Brush Color sets the current brush color and fills all objects used with the brush
command (also the background color for text).
Or click . Use Brush is a toggle command used to fill rectangles, circles, ellipses, and
polygons with the color selected in Brush Color.
Or click . Text Font selects the current font to use when drawing text.
Select Controls allows you to select which ActiveX objects can be inserted into
the Graphics Window with the Insert Object drawing tool.
Drag-and-Drop Data
The toolbox work area The drag-and-drop feature allows you to perform operations in the Graphics
includes the Outline and Window by dragging objects on the screen with the mouse. For example, you can
Summary Views. drag-and-drop a signal or pin from the toolbox work area to a Graphics Window.
Both the device and Graphics Window must be open.
To drag-and-drop a signal or pin to the Graphics Window
1. From the Graphics Window, select (highlight) an object with animation
attached, such as a rectangle.
2. From the Outline or Summary View, click a signal or pin and drag (hold the
mouse button down) it on top of the rectangle in the Graphics Window and drop
(release the mouse button).
Or, create a new numeric animation automatically by dragging the signal or pin
onto an empty space in the Graphics Window.
These objects can be moved, In the Graphics Window, the name of the signal or pin displays as a text object, and
sized, and modified. the value defaults to numeric animation, which displays the signal/pin data.
Properties Toolbar
Use the Properties toolbar to When you select an object, the properties toolbar is filled with named attributes of
quickly modify any drawing that object. This allows quick changes to drawing objects and inserted ActiveX
object. Controls. The following properties are common to all controls:
Name allows you to identify an object for Event Inputs.
Height, Top, Width, and Left allow you to set the position and size of the
selected object.
Line Width allows you to set line attributes.
Pen Color and Brush Color allow you to change the drawing colors. Double-
click these properties to bring up a Select Color dialog box.
There are other properties specific to particular drawing objects and ActiveX
controls. When you double-click properties such as font, color, and picture, custom
dialogs display. If you double-click a true or false value, it toggles the value.
View Signal Summary

The View Signal Summary option within the View menu allows you to make
quick changes to signal names used in the Graphics Window. For example, if a
signal name is changed in a device, the Signal Summary can be used to change the
signal names in the Graphics Window in one operation, rather than changing each
object individually.
Select a signal, then
click on it once to
change it. If you
double-click on a
signal, the object to
which it is attached is
selected with the
Select tool.
The Object Type
provides a quick
description of the
drawing, animation,
or input that the
signal is attached to.
Type the full or partial

name of the signal that
you want to replace.
Type the full or partial

name of the new
signal and then click
Replace to change all
instances of the
signal.
Click the Export List button to save
the signal summary to a text file.
Settings
The Settings menu contains commands that control the way an object is drawn.
Before an object is created with the Draw command, these settings must be defined
as shown in the following sections.
Frame Size and Options

Frame size allows you to set the Width and Height values to determine the size of
the Graphics Window. No objects can be created outside the frame.
To set the frame size
From the Settings menu, select Frame Size and Options. The Frame Size
and Options dialog box displays.
Check Show Grid to show

an alignment grid on the
Graphics Window in Edit
mode. Enter the Width and Height
values. The integers must
Check Snap to Grid to be between 30 and 10000.
force objects to positions
along the alignment grid. Click OK to accept the
changes.
Check Show Undefined Click Cancel to ignore
Signals Warning to be the changes.
notified of missing signals
in the attached device.
Click Change (upper button) to open a standard Color

dialog and select the screen's Background Color.
Click Change (lower button) to open a standard Insert

Picture dialog and select the screen's background .wmf or
.emf.
Pen Color and Pen Width

Pen Color sets the current pen color for drawing the lines in all objects. This
includes the color of the outside border around rectangles, circles, ellipses, polygons,
polylines, and the color of text. Pen Width sets the current width of all lines drawn
(all objects except text). These settings can be edited for each new object to provide
a variety of graphics.
To select a pen color
Or click . 1. From the Settings menu, select Pen Color. The Color palette box displays.
2. Click the desired color and click OK.
Or, create a custom color by clicking one of the custom color squares, and click
Define Custom Colors >>.
To select a pen width
Or click . From the Settings menu, select Pen Width. The Pen Width dialog box displays.
Enter an integer
between 1 and 10.
Click OK.
The object(s) is drawn

in this width until it is edited.
Brush Color and Use Brush

Use Brush can be toggled on Brush Color sets the current fill color for objects drawn when Use Brush is
selected. Objects that can be filled include rectangles, circles, ellipses, polygons, and
and off by clicking .. text background. The color can be the same as the Pen Color command or a new
color.
Note If the Brush Color (fill) and Pen Color are the same when text is added,
only the background will display. The text blends into the background.
To select a brush color
Or click . 1. From the Settings menu, select Brush Color. The Color palette box
displays.
2. Click the desired color.
Or, create a custom color by clicking on one of the custom color squares, and click
Define Custom Colors >>.
To fill an object with color
A check mark ( Use Brush) 1. From the Settings menu, select Use Brush.
displays beside the command
2. From the Draw menu, select the desired object. The object will be filled with
when it is active.
the color selected in Brush Color.
Text Font
Text Font allows you to select the font and size for all the text in the Graphics
Window. The text can be entered with or without a separate background color. The
area of the text background is determined by the font size.
To select a font
Or click . From the Settings menu, select Text Font. The Font dialog box displays.
Select a Font, a
Font style, and a
Size.
Your selected
font displays in
the Sample text
box.
Click OK.
The text displays
in the Graphics
Window. It can be
selected and
moved, or edited.
Note To add a text background color, refer to the section, Brush Color and Use
Brush. Use Brush must be checked to show a background color.
Select Controls
The Add ActiveX Controls to Graphics Window dialog box allows you to
select the third party ActiveX controls to use in the current Graphics Window.
ActiveX controls are generic objects that can be used in many different applications.
They can provide new and improved functionality to any existing software program
that supports them. Many ActiveX controls are available from third party software
companies.
Because ActiveX controls are provided by a third party, they may not always work
properly. Graphics Windows support a wide variety of ActiveX controls, but not all
controls work well in Toolbox. In addition, there is no guarantee that a particular
ActiveX control is installed on all computers using a Graphics Window. Providing
these controls to end users is the responsibility of the Graphics Window user, and is
beyond the scope of this document.
Note ActiveX controls are frequently designed for a particular container. Such
controls may not work in Graphics Windows as expected, and may even cause the
toolbox to fail. The recommended use of ActiveX Graphics Window screens is for
custom functionality, such as alarm windows.
To add an ActiveX Control to Graphics Window
From the Settings menu, select Select Controls. The Add ActiveX Controls to
Graphics Window dialog box displays.
Select the appropriate

controls. If an item is
checked, selecting it will
uncheck it. Checked controls
are available in the Insert
Object dialog. If you do not
have a design time license
for a particular control, you
will not be able to use that
control. A control must be
installed on your computer
for it to appear in the list. Be
sure to only use controls that
have been tested and will
also be installed on client
computers.
Click OK to update the

available controls for the
current Graphics Window.
By default, no controls are
checked.
Note When a new Graphics Window is created, only the controls distributed with
toolbox are checked by default.
Draw Commands
All pictorial objects created with the Draw commands are made up of individual
lines, filled objects, or text. The objects are defined by straight and curved lines,
which are, in turn, defined by a set of points.
To create an object
1. From the Draw menu, select a command.
2. In the Graphics Window, click where you want to anchor the object.
3. Click and hold the left-mouse button. Drag the mouse to draw the line or shape.
Release the mouse button to end. The following table, Draw Commands,
describes each command in more detail.
Refer to the section, Using Shapes such as rectangles and ellipses are drawn with the setting selected in Pen
Graphics Window Objects. Color and filled with the settings selected in Brush Color. Text is created using
the currently selected font, color, and brush.
Draw Commands
From the Draw menu, select. . . Or click. . . Click and hold the left mouse button
Line Drag to the desired line length and release the button. The
line is drawn in the current pen color and pen width.
Rectangle Move the mouse to the opposite corner of the rectangle and
release the button. The rectangle is drawn with the current
pen color and pen width and filled with the brush color*.
Circle At the center of the circle, drag the mouse to the outside
radius, and release the button. The circle is drawn with the
current pen color and pen width and filled with the brush
color*.
Ellipse At the center of the ellipse, drag the mouse to the outside X
and Y radius, and release the button. The ellipse is drawn
with the current pen color and pen width and filled with the
brush color*.
Polygon At the first vertex, release the mouse, and move to the next
vertex and click the button. Move the mouse to each of the
other vertexes and click the button. When the last vertex is
drawn, click the right mouse button. A line will be drawn
between the last vertex and the first vertex. The polygon is
drawn with the current pen color and pen width and filled
with the brush color*.
Polyline At the first vertex, release the mouse and move to the next
vertex and click the button. Move the mouse to each of the
other vertexes and click the button. When the last vertex is
drawn, click the right mouse button. A polyline cannot be
filled with the brush color because it is not a closed object.
Text At the text location, release the mouse and enter text. Press
Enter or click the left mouse button to end. The text is drawn
using the current font and color. The brush color will be used
for the background (if selected).
Insert Object Use this tool in the same manner as the Rectangle tool. The
ActiveX Control will be inserted into the rectangular area you
select. When you release the left mouse button, the Insert
ActiveX Control dialog will appear to let you select which
object to insert.
* The Use Brush command must be selected to fill an object with the color selected in the command Brush Color.
Handles Objects can be moved, resized, and the settings edited using the Select command.
When an object is selected, handles appear around the edges to drag-and-resize or
drag-and-drop to move the entire object.
To edit an object
1. From the Draw menu, select Select.
2. Click the object or draw a box around the object. Handles appear around the
Or click . edges of the object to highlight it.
The blue dashed line indicates that the object was the last one selected. This is the
object that the alignment tools will use to match sizes and edge alignment.
Once the object is highlighted, it can be edited several ways as follows:
Select a new setting, such as Pen Color or Text Font.
Click a handle and hold the mouse button to drag and resize the object.
Click the middle of an object and hold down the mouse button to drag-and-drop
and move the entire object.
Note Refer to the next step to move ActiveX controls.
To group multiple objects
Or select multiple objects by 1. Click to select the draw tool and draw a box around all desired objects. The
pressing the Ctrl key while box must include all portions of all objects. All selected objects have handles.
clicking on the objects.
2. Click . A group outline box appears around the entire group.
3. Once the object has been grouped, it can be moved and resized just like any
other drawing object. Click the Group button again to ungroup the object.
Insert Object
The Insert Object command allows you to insert ActiveX controls into a Graphics
Window.
To insert an ActiveX Control
Or click . 1. From the Draw menu, select Insert Object.

2. Draw a rectangle for the control. The rectangle serves as a frame for the control.
Control options will vary The Insert ActiveX Control dialog box displays.
depending upon the controls
selected. To select controls,
see the previous section Select
Controls.
Select the desired

control.
Click OK.
Note The controls must be selected in the Select ActiveX Controls dialog.
Insert Picture
The Insert Picture command allows you to insert a custom graphic created in
Visio Technical. Use the following guidelines:
All drawings must be created using Visio Technical (Version 4.1 minimum).
Drawings must not include Visio text fields at the top of the drawing. The
Graphics Window inserts these text fields incorrectly.
Save the drawing as a Windows metafile (.wmf).
The .wmf must be inserted into a rectangle created in the Graphics Window.
Note Windows metafile images from other sources may not work.
To insert a picture
1. Draw a rectangle using the Graphics Window drawing tools. The rectangle
serves as a frame for the picture.
2. Click the rectangle to select it.
Or click . 3. From the Draw menu, select Insert Picture. The Insert Picture dialog box
displays.
Insert Picture Dialog Box
Enter the full path of the .wmf
or click Browse... to enter the
path.
Click OK. The picture displays

inside the rectangle.
Resize the picture, if desired,
by clicking and dragging one of
the rectangle handles.
Animate Objects
Animated objects display signal information. The following types of animation can
be assigned to an object:
Numeric animation displays the live value of a signal in numerical form.
Bar Graph animation displays the live value of a signal in a bar graph.
Trend animation displays the recent records of up to eight signals on a trend
graph.
Text animation displays different text strings, depending on the value of the
source signal.
Color animation changes the color of the object, depending on the value of the
source signal.
Property animation changes any named aspect of an object, such as Height or
Caption. This is particularly useful when applied to inserted ActiveX controls.
In addition, more than one property can be animated at a time.
To animate an object
1. Select the object.
2. From the Animation menu, select the type of animation for that object (as
described above). The animation dialog box for that type of animation displays.
3. Click Value Return and select a Return (value) for this object to
display a value of a signal (refer to the next section, Value and Enable Return).
4. Click Enable Return and select a Return (value) for this object
to enable and disable the object based on a value (refer to the next section, Value
and Enable Return).
5. Configure each object as directed by the field definition of the dialog box.
Value and Enable Return
Refer to the section, Using Value Return is used to obtain signal values for the animation. Enable Return is
Graphics Window Objects. used to obtain signal values that turn the objects on and off. From an animation
dialog box, click or . The following dialog box displays
with six different returns (described in the following sections). Each animation must
select a Return.
Signal
The Signal Return produces a value from a signal selected from the Signal
Selector dialog box. This is the most important return in the device.
Check to attach the

input field to the object.
Uncheck to detach the
signal.
Enter the name of the

signal value to obtain.
Click Browse to find a
signal if a device is
already selected.
Math
The Math Return performs a mathematical function on other returns and fixed
values. It can also be used to generate a fixed value for other returns.
Check to attach the input

field to the object. Otherwise
the input field will not exist.
This formula generates the

produced value for this
return. It can contain any of
the following math functions:
add(+), subtract (-), multiply
(*), divide (/) or (|), and (&),
logical or (||), logical and
(&&), absolute value (abs),
and square root (sqrt). A
number preceded by a pound
sign (#), refers to the value of
one of the eight Value
Returns.
Returns #1 - #8 are used in

the above formula. These
can be any of the returns,
including other Math returns.
Compare
The Compare Return produces a value related to the first comparison that is True.
This is most useful in the text and color animation.
Check to attach the input field

to the object. Otherwise the
input field will not exist.
Default value is returned

if none of the following
comparisons are true.
Type can be Off, Equal, Not

Equal, or Greater Than.
Compare groups are
evaluated starting with
Group1 through Group 4.
The value for the first one that
is True is returned. If the drop
down box is set to Off, then
that comparison is not used.
Otherwise the top Return
value is compared to the
bottom Return value using the
selected compare type. To
compare a signal value to a
fixed value, use the math
return with the formula being
just the fixed number.
Maximum
The Maximum Return produces the maximum value of the Returns that are attached
to it.
Check to attach the

Otherwise the input field
will not exist.
Return is used to
produce a value to this
Maximum Return.
Minimum
The Minimum Return produces the minimum value of the Returns that are attached
to it.
Check to attach the

will not exist.
Return is used to
Minimum Return.
Average
The Average Return produces the average value of the Returns attached to it.
Check to attach the

will not exist.
Return is used to
Average Return.
Numeric Animation
Numeric animation displays the live value of a signal. It must be attached to a text
object.
Click to attach and detach animation to the

object. A checked box contains animation.
Note: If you detach (uncheck) this option
and click OK, the animation is deleted
unless you previously saved the .grw file.
Value Return allows you to enter the value
for the animation.
Enable Return uses the value of a supplied

signal to enable the animation.
0 = disable
Rate defines how fast the signal data is

collected for the animation.
Define the text colors for the corresponding

alarm limits.
Off does not use the alarm limit.
On uses the value text box as the alarm limit.
Auto uses the alarm limit defined in the
scale data for the signal. The number is
normally displayed in the standard colors
unless an alarm limit is exceeded.
Note Brush colors (fill) only apply if the object is drawn with the Use Brush
setting active or if the Use Brush setting is active when the object is selected.
Bar Graph
Refer to the section, Using Bar graph animation displays the live value of a signal in a bar graph. It must be
Graphics Window Object. attached to a rectangle object.

Note: If you detach (unchecked)
this option and click OK, the Value Return allows you to enter
animation is deleted unless the value for the animation.
you previously saved Specify the direction of the bar
the .grw file. Enable Return uses the value of from the low limit to the high limit.
a supplied signal to enable the Specify how the bar is drawn.
animation. 0 = disable Unidirectional starts the bar at the low
value and draws toward the high value.
Bidirectional starts the bar at the center
value and draws toward either the high or
low value.
Specify the signal values that correspond

to the ends (and possibly the center) of
the bar graph. Auto uses the values from
the scale data for the signal. Left/Top or
Right/Bottom displays the limit values
next to the bar graph. If the bar graph
flows up/down, the limits are displayed on
the left side or right side of the bar graph.
If the bar graph flows left/right, the limits
are displayed on the top or bottom of the
bar graph.
The values are drawn in the color

indicated in this Color box.
Define the text colors for the

corresponding alarm limits.
Off does not use the alarm limit.
On uses the value text box as
the alarm limit.
Auto uses the alarm limit defined
in the scale data for the signal.
The number is normally displayed
Rate defines how fast Select the color for the in the standard colors unless an
the signal data is background of the bar alarm limit is exceeded.
collected. graph.
Trend
Trend animation displays the recent records of up to eight signals on a trend graph. It
must be attached to a rectangle object.

Note: If you detach (uncheck) this option Pixels per Sample uses the number of pixels in the
and click OK, the animation is deleted text box for each data sample. When the number is
unless you previously saved the .grw file. increased, the graph widens and less time is covered.
Samples per Pixel uses the number of data samples
Define how fast the signal in the box for each pixel on the graph. When the
Displays the total amount data is collected for the number is increased, the graph becomes narrower
of time covered by the animation. and more time is covered.
Trend graph using the
size of the graph, Rate,
and Pixels per Sample -
Samples per Pixel.
Set the number of grid
Samples after Disable lines drawn in the
controls how many horizontal and vertical
samples are collected after direction. One grid line
the Enable signal goes is always drawn in the
False. A zero means the center on the graph
trend will stop immediately. (always given an odd
Time displays the amount number of horizontal
of time corresponding to grid lines). Enter the
the Samples after Disable. color to draw the grid
lines.
Select the the Background
Color of the trend graph. Select the graph line
Set the Direction the to assign and view
rectangle is drawn from. signal information and
(If Left is selected, the line attributes.
trend starts at the left of
the rectangle and drawn
toward to the right.) Define the text colors
for the corresponding
Enable Return uses the alarm limits.
value of a supplied signal Off does not use
to enable the animation. the alarm limit.
0 = disable. On uses the value text
Set the Block Size (size box as the alarm limit.
of the block to display). Auto uses the alarm
Define the Enable and limit defined in the
Disable colors that display scale data for the
in the top corner of the signal. The number is
trend as a block. normally displayed in
the standard colors
Enter the value used by unless an alarm limit
Specify the signal values that correspond to
this signal on the trend. is exceeded.
the top (High Limit) and bottom (Low Limit)
of the trend graph.
If Auto is checked, the values from the scale
data for the signal is used.
If L (left) or R (right) is checked, the limit values are
displayed next to the trend on the side selected. The
limit values are drawn in the color in the Color box.
Text
Text animation displays different text strings depending on the value of the source
signal. It must be attached to a text object.
Click to attach and detach animation to the object. A checked box contains animation.
Note: If you detach (uncheck) this option and click OK, the animation is deleted unless
you previously saved the .grw file.
Value Return allows

you to enter the value
for the animation.
Enable Return uses the

value of a supplied signal
to enable the animation.
0 = disable
Rate defines how fast the

signal data is collected
for the animation.
Define the Text Strings

for each Value Return
and the text colors. The
default string displays if
the Value Return does
not match any of the
value entries that are
turned on. There are
entries for values 0 to 63.
Click Next and Previous
to scroll through all the
possible values.
Note Brush (fill) colors only apply if the object is drawn with the Use Brush
setting active or if the Use Brush setting is active when the object is selected.
Color
Color animation changes the color of the object, depending on the value of the
source signal. It can be attached to any type of object.
Note: If you detach (uncheck) this option and click OK, the animation is deleted unless
you previously saved the .grw file.
Value Return allows

you to enter the value
for the animation.

0 = disable

signal data is collected
for the animation.
Define the Colors of

the base object for each
Value Return. Default
displays the base object
if the Value Returns
value does not match
any of the value entries
that are turned on. There
are entries for values
0 to 63. Click Next and
Previous to scroll
through all the possible
values.
Note Brush colors (fill) only apply if the object is drawn with the Use Brush setting
active or if the Use Brush setting is active when the object is selected.
Property
Property animation changes any named property of any type of object, depending on
the value of the source signal.
Note: If you detach (uncheck) this option and click OK, the animation is deleted
unless you previously saved the .grw file.

signal data is collected for
the animation.
All properties that are

animated are listed here,
along with a description of
the value return block.
Click Add to insert a new
property to be animated.
The Property Animation
(Numeric) dialog box
displays (see figure below).
Click Remove to delete a
property from the list.
Double-click a listed
property to edit the
animation.
Property selects which aspect

of the selected object is to be
animated.
Value Return allows you

to enter the value for the
animation.
Click OK to add the property to

the list of animated properties
for the selected object.
Click Cancel to discard the animation.
Input Fields
Refer to the section, Using Input fields allow you to change signal values in a device. When online, a Graphics
Graphics Window Objects. Window object can assign values to a signal in the device by using an input field
described in this section.
To configure an input field
1. Select the object.
Tip To select an object, click or select Select from the Draw menu.
Or click the associated Input 2. From the Input menu, select an input to assign to the object.
button located on the Input
Toolbar.
To edit an input value
Double-click the input object. The assigned input dialog box displays to edit.
Numeric
The Numeric input field enters numerical data into a signal in the controller from the
object selected in the Graphics Window.

to the object. Uncheck to detach the signal.

signal value to obtain.
Click Browse to find a
signal if a device is
already selected.
Enter the value to use

when live data mode
dialog box increment or
decrement button is
active.
High Limit and Low Limit are used to set the maximum and minimum
value that is sent by this input field.
Off does no limit check.
On uses the values entered into high limit and low limit.
Auto uses the values from the scale data for signal.
Enter Value
The Enter Value dialog box displays when the Graphics Window is online and a
numeric input is selected.
Enter a new value for the signal.

Click Send to send this value.
Increment adds this value to the

value in the Input Numeric
dialog box.
Decrement: subtracts this value
from the value in the Input
Numeric dialog box.
Setpoint
The Setpoint input field sets a signal in the device to the assigned value of the object
selected in the Graphic Window.
Check to attach the input field to the object.

Uncheck to detach the signal.
Enter the name of the signal value to obtain.

Click Browse to find a signal if a device is
already selected.
Enter the value that is sent to the signal when

this input field is selected. Check Confirm
before send to display the Send Setpoint
dialog box to confirm that the Graphics
Window is sending a setpoint to the device.
Initial Value
The Initial Value input field makes the current signal value the initial value for all
the signals specified.
Check to attach the input

field to the object. Uncheck
to detach the signal.
A list of all the signals whose

initial values are set when
this input field is selected
displays. Check Confirm
before send to display a
dialog box to verify that you
really want to send this value.
Click the Add, Browse,

and Delete buttons to
edit the signal list.
Click OK to send or click

Cancel to exit.
Text
The Text input field allows you to create and then select a text string to define the
value sent to the signal in the controller.
Check to attach the input field to
the object. Uncheck to detach the
signal.
Enter a signal (the value is set to
this field). Click Browse to find a
signal if a device is ready.
A list of all the text strings in the
Select Text Value dialog box
displays. The strings are in
double quotes, followed by a
dash and the value sent to the
signal ("Stop" = 0).
They are displayed in the same
order as in this list box.
Edit the list box using the

following buttons:
Up moves the selected entry up
by one.
Down moves the selected entry
down by one.
Add allows you to add a new
string and value to the end of the
list.
Delete removes the selected The Select Text dialog
entry. box displays when the
Modify allows you to change the Graphics Window is
selected entry. online and a text input
object is selected. Select
the appropriate text
string.
Click OK to send the
corresponding value to
the signal in the device.
Click Cancel to exit the
dialog box.
Toggle Command
The Toggle command performs a Boolean inversion, converting the signal from
True to False or False to True.

to the object. Uncheck to
detach the signal.
Enter the desired signal

name.
Check Confirm before send

to display a dialog box to
verify that you really want to
send this value.
Click OK to toggle or
Cancel to exit.
Event Input
Event Inputs can only be attached to ActiveX controls created by the Insert Object
drawing tool. ActiveX controls have a list of events corresponding to user actions,
such as Click or Change. The Event Input allows signals to be changed when these
events occur.
Check to attach the event

input to the object.
Uncheck to delete the
inputs.
Click on the name to
select an event from the list.
Then click Attach to

connect a signal to it or
modify an existing attached
signal. The Event Handler
dialog box displays (see
figure below).
Click Remove to delete a

signal attachment.
Name of the event.
Name of the object.

If unnamed, type of object.
Enter the desired signal name.
Select Send Property to send

a property value from an object
to the signal.
Select the property to send.
Select which object properties

to send. The Selected Object
is the default, but any named
object can be used (see
procedure below).
The Event Handler can send any property from any named object. An object is
Named if its Name property has been set.
To name an object
1. Select an object in the Graphics Window.
2. Make sure that the Property Toolbar is visible. If it is not visible, from the View
menu, select Toolbars, and Properties.
3. In the Properties toolbar, for the Name, click in the edit field (in the Values
column). Type a name of up to 32 characters.
Hyperlinks
The Hyperlink command allows you to link to a variety of file types to objects in
the Graphics Window.
Note Hyperlinks cannot be used in conjunction with Animations.
To create a hyperlink
1. Select an object.
Click , then select
Select from the Draw menu. 2. From the Input menu, select Hyperlink. The HyperLink dialog box displays.
Or click .
Launches Program creates a hyperlink that runs a file type external to

toolbox, such as spreadsheets and drawings. It also allows hyperlinks to
execute DOS command lines, including processing switch parameters.
Open Toolbox File creates a hyperlink that opens only toolbox file types,
such as Trend Recorders (.trd) and Graphics Windows (.grw).
Open Help File creates a hyperlink that runs the Windows Help engine
and opens the help file.
Check to attach the hyperlink to the Automatically close source Graphics Window causes the current
object and uncheck to detach. screen to close before executing the hyperlink.
Enter the Command Line

(Launched Program), Filename
(Toolbox), or Help File (Help) to
execute an application or to open
a file. Substitution characters are
also supported in this field to
replace any part or all of a path,
such as c:\%2\ work.xls. These
characters must be defined in a
controller, the Graphics Window
default Substitution list, or the
Hyperlink Substitution list.
Help Section ID jumps to a

particular section of the Help
file specified in the path.
Click to display the Edit Hyperlink Substitutions Display as PopUp displays the Help
dialog box and enter signal substitutions specific to file in a small pop-up window. If this
this hyperlink. These signals substitutions function box is not checked (default), the Help
as the controller substitutions, except that the file displays as a main window.
hyperlink always inherits the online memory buffer
of its parent Graphics Window, then overwrites any
corresponding signals (refer to Signal Substitution).
Tip If Launches Program is selected, you can enter a document file registered in
Windows. The associated application that opens the file will then run. When entering
the Command Line, you must place the switches and/or parameters in double quotes
to be recognized by DOS. (c:\acdcex.exe "/s /p /w /c:\directory")
Using Graphics Window Objects
The following section shows how to construct basic Graphics Window objects and
add animation or input values. The following examples are created:
Signal's numeric value
Signal trend
Signal bar graph
Object's numeric value
Display a Signals Numeric Value

To display a signals numeric value
1. From the Draw menu, select Text.
Enter text here . 2. Click the drawing area where the numeric value will display. A character-sized
box with a cursor displays.
3. Type the text that will display in the Graphics Window while offline.
Or click . 4. From the Draw menu, select Select.
Select object. 5. Click the text that was entered. A dotted line surrounds the text object.
6. From the Animation menu, select Numeric. The Numeric Animation
Or click Numeric dialog box displays.
Animation from the
Animation Toolbar.
7. Click Value Return to obtain a signal value for the animation. The Select
Return dialog box displays.
8. Click Signal to produce a value from a signal in the current device. Click OK.
The Signal dialog box displays.
9. Enter the signal name or click Browse for signals in the current device.
Click to go online.
10. Click OK to complete the signal, and click OK to complete the animation.
11. Place the device online to view the live values.
Create a Signal Trend

To create a signal trend
Or click . 1. From the Draw menu, select Rectangle.

2. Draw a rectangle. (Click the drawing area where one corner of the trend will
display. Press and hold the mouse button and drag the cursor to the opposite
corner of the trend. Release the mouse button to complete the rectangle.)
Or click . 3. From the Draw menu, select Select.
4. Click the rectangle that was drawn. Handles display on the corners and the
middle of the rectangle to indicate that the rectangle was selected.
Or click . 5. From the Animation menu, select Trend. The Trend Animation dialog box
displays.
6. Click Value Return to obtain a signal value for the animation. The Select
Return dialog box displays.
7. Click Signal to produce a value from a signal in the current device.
8. Click OK to complete the signal.
9. Verify the high and low limits for the value. If necessary, change these limits.
10. To assign additional signals, click one of the option buttons next to
Information for Signal.
11. Click OK to complete the trend.
12. Place the device online to view the live values on the trend graph.
Create a Signal Bar Graph
To create a signal bar graph
1. Draw a rectangle by performing steps 1 through 5 as described for the previous
signal trend.
2. From the Animation menu, select Bar Graph. The Bar Graph dialog box
displays.
3. Verify the high and low limits for the value. If necessary, change these limits.
4. Verify the direction. If necessary, change these settings.
5. Change the standard Alarm Colors to be different from the background color.
6. Place the device online to see the live values on the bar graph.
Create an Object to Input a Numeric Value
To create an object to input a numeric value
1. Draw a rectangle performing steps 1 through 5 as described in the previous
sections for a signal trend and bar graph.
Or click Input Numeric 2. From the Input menu, select Numeric. The Input Numeric dialog box
from the Input Toolbar. displays.
3. Enter the signal name to be modified and click OK.

4. From the Draw menu, select Online.
5. Modify the value online by clicking on the object when the cursor shape
changes to a hand shape. The Enter Value dialog box displays.
6. Modify the value and click Send to leave the dialog box active, or click OK to
close the dialog box.
Signal Substitution
Signal Substitutions can only When configuring animation or input return strings, a signal substitution can be
be edited while offline. used instead of the full signal name or value. Then, when going online to a
controller, the substitution character(s) are replaced with the signal name. The
substitution characters are %N, where N is an integer between 0 and 9 or ^. The
Graphics Window can have a total of 11 characters.
To create signal substitutions
1. From the Edit menu, select Signal Substitutions. The Signal
Substitutions dialog box displays.
2. Enter the desired value or signal name into each substitution field. Click OK.
When configuring animation or input return strings, enter the substitution
character(s) for the desired signal. When the controller goes online, the substitution
character(s) are replaced with the value(s) or signal name(s) entered in the dialog box
above.
Note Any number of characters (defined above) can be used in the Return
Value/Signal dialog box to form the signal name.
Forced Signals
Graphics Window does not display forced signals any differently than non-forced
signals. Additionally, Graphics Window has no concept of I/O Points, so it cannot
directly change or display the forced status of a point. However, pressing the Ctrl
key while clicking an Input online will bring up a summary dialog of the signal
attached to the input, including the I/O points it is connected to.
Double-click the live value to modify a live signal or point. For Boolean signals and
all points, this dialog box includes a checkbox to force the signal.
String Substitutions
The Graphics Window supports string substitution module pins as supported by the
controller. The substitutions specified by these pins have a higher priority than those
defined in the Graphics Window. When a modules Detached Summary View
displays, the substitution signals defined in the Graphics Window (known as
defaults) are loaded into an online memory buffer called Online Substitutions.
Then, the substitutions specified by module pins overwrite their corresponding
default values in that buffer.
For example, a Graphics Window has defined default signal substitutions at
characters %1, %3, and %5. A module in a controller has defined two substitution
pins, SUB1 and SUB7, which reference specific signals. When you select a
The purpose of Online modules Detached Summary View from the toolbox, the default signals load
Substitutions is to serve as a into Online Substitutions. Next, the substitution of module SUB1 overwrites the
clipboard for signals that are online substitution %1, while the substitution of SUB7 overwrites the empty online
used by the Graphics Window substitution %7. It is important to remember that only the online substitution is
while connected to a overwritten, not the default signals saved with the Graphics Window. The defaults
controller. are permanent unless otherwise modified.
To view signal substitutions
From the toolbox, while in the Graphics Window, select the View menu and
Online Substitutions.
Note This is the same dialog box used to enter substitutions, except it cannot be
edited (refer to the previous section, Signal Substitutions).
Graphics Windows for the Control Operator
Interface (COI)
The COI is a standalone panel pc with a touch screen that uses Graphics Window to
build and display operator interface screens. The following differences exist when
developing Graphics Windows for the COI:
All device types that can produce Ethernet Global Data (EGD) exchanges are
supported by the COI.
Signals must be defined on EGD exchanges for Graphics Windows to use them.
EGD signals are one-way, so the same signal typically cannot be connected to
both an animation and an input; this has the side effect that Toggle inputs do not
work properly.
The COI has its own document type in toolbox; typically Graphics Windows are
created and managed in the COI document.
Memory is limited on the Flash memory system in the COI.
Only three fonts are available on the COI: Arial, Lucida Console, and System.
Forcing points and Boolean values is not supported from the COI.
Care should be taken to support the COIs touch screen; buttons need to be large
and well separated. Numeric inputs work by popping up a numeric keypad on
screen when the input is clicked.
To test the screens with live data, it may be necessary to download them to the
COI (see Chapter 14). For some tests, however, it is sufficient to have the
document for the device (Mark VI, EX2100) producing the EGD exchange open
and online. You may need to set the active device (see Select Device above) to
the proper device.
The frame size for a COI screen should be set to 792 by 570.
For complete information on using Graphics Windows with the Control Operator
Interface, refer to Chapter 14, Configuring the Control Operator Interface.
Chapter 9 Hardware and I/O
Introduction
This chapter defines the controller networks and inputs and outputs (I/O) used in the
toolbox. It includes configuring a network interface, and signal and I/O connections
used in blockware.
Section Page
I/O and Network Interface........................................................................................9-2

Mark VI I/O..............................................................................................................9-5
EGD Interface.........................................................................................................9-34
Genius Networks ....................................................................................................9-42
Main Board.............................................................................................................9-63
Register Network....................................................................................................9-67
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 9 Hardware and I/O 9-1
I/O and Network Interface
A controller configuration can be divided into two sections, Blockware and I/O. I/O
items, also known as hardware modules, can be found/created in Outline View of
the toolbox under the item, Hardware and I/O Definitions. These items define the
I/O or network interfaces used by the controller and connect I/O with signals to be
used in blockware. Also, many items monitor the live data of specific I/O points and
their associated signals, so you can see the transfer from I/O to the signal or from the
signal to I/O. All controller hardware modules are composed of points. Sometimes,
between the points and network interface level there is a further division of points
into pages or blocks.
I/O Points
Points are the I/O for the controller and must be associated with signals to be
accessed in blockware. This point-signal association is very important to the
controller function.
I/O points also represent a buffer separate from the signals used by controller
blockware. This memory is modified directly by drivers that handle the various
controller interfaces as well as by blockware. Blockware reads and writes these I/O
points through I/O transfers. These transfer data from input points to their signals at
the execution of tasks that use those signals. Transfers of data from signals to their
associated output points occur at the end of the execution of tasks that use those
signals, as shown below. For any signal connected to an I/O point, the direction of
point determines whether it is considered an input or an output.
Note A point can never be both an input and an output.
Inputs written to
signal space before
a task runs
Network 1 Mark VI Turbine Network 2

I/O Points Controller Signals I/O Points
Outputs written
from signal space
after a task runs
A signal can be connected to more than one point. If one of the points is an input and
one is an output, the controller transfers the value of the point from the input to the
output through the signal. This I/O transfer occurs regardless of whether the signal is
used in a task. The runtime process that performs this function periodically in the
background (during idle time) is called the I/O mapper, since it maps inputs to
outputs.
9-2 Chapter 9 Hardware and I/O GEH-6403L Toolbox for a Mark VI Turbine Controller
Insert I/O and Network Interfaces
I/O and network interfaces are inserted in the Outline View of the toolbox under the
level, Hardware and I/O Definitions.
For I/O and network items to be inserted, the correct platform must be selected from
the controller properties.
To edit controller properties
1. From the Outline View, double-click the device name (top of Outline View).
The controller device Properties dialog box displays.
2. From the General tab, select the following options.
Name specifies this
controller when
communicating with
the SDB. It defaults
to mkvi1 the first
time a controller is
created. The name
is saved as a .prj.
Clock specifies
the source of the
clock as internal or
external. For Mark
VI controllers, set
the clock to
External (unless
the hardware is a
simulator).
Platform specifies
the hardware
platform on which
the configuration
operates. This field
is important for
proper control
execution records
and for selecting Select the Device No. is the system SDB
hardware and I/O. basic I/O and number. If set to 0, the next Select this check Select this check box Select the interval (ms) that
For more detailed compute rate available SDB number is box to to enable the the I/O mapper task runs.
information on for a Mark VI assigned to the device when indicate that Controller Load The I/O mapper task
selecting the system. data is entered into the you are Profiler for the transfers signals between
appropriate database. operating a device. different I/O points, if the
platform, refer to TMR system. signals are not used in
Chapter 9, blockware code.
Hardware and I/O.
Mark VI I/O
The Mark VI Turbine Controller includes its own I/O system, which has cabinets
containing VME racks. The VME racks can have various configurations of VME
boards. There are several different kinds of VME boards designed specifically for
Mark VI I/O.
Displayed options in the To insert Mark VI I/O
dialog box will vary
1. From the Outline View, click Hardware and I/O Definitions.
depending on software
installed. 2. From the Edit menu, select Insert First. The New I/O or Network
Interface dialog box displays.
Select Mark VI I/O

and click OK.
The Mark VI I/O displays

in the Outline View.
Racks
A Mark VI I/O configuration consists of one or more racks, each with a unique
number. The master control rack must be Rack 0, which contains the Mark VI
controller and the VME Communications Interface board (VCMI).
To insert a rack
1. From the Outline View, click the item, Mark VI I/O to highlight it.
2. From the Edit menu, select Insert First. The Select a rack dialog box
displays.
Select one of the racks

and click OK.
The Mark VI Rack

Rack Types
Select the rack type

(refer to the
descriptions below).
If Simplex or Triad
is selected, a
channel must be
selected also.
Enter a unique
rack number.
Select the hardware
form for the channel
indicated.
Click to view the

release notes
The Choose
Compatibility Code
dialog box displays
the available
compatibility codes
with the newest code
displayed at the top of
the list.
Configure the board
slot number.
To configure a
terminal board,
select the item and
double-click or
select Modify to
bring up the
Terminal Board
Properties dialog
box .
The Connector
Name cannot be
changed.
The Connected box

must be selected to
configure the
terminal board and
the hardware form.
Select the terminal

board and hardware
form to be used.
Click OK.
Simplex rack has a rack number
and a channel designation. It cannot
contain voted boards.
TMR rack represents three racks

that share the same rack number.
The racks are identified by their
channel R, S, and T. The TMR rack
contains only voted boards.
Triad represents three racks on the

same channel. The rack numbers
must be consecutive, such as 7, 8,
and 9. The TMR rack contains only
voted boards.
Simplex Rack in Outline and Summary View

The Simplex rack displays in the Summary View as a graphic with all the boards it contains.
A Simplex rack
displays a single line
in the Outline View,
which includes the
rack number,
channel name and
rack type.
Click this line to

insert boards that
operate in Simplex
mode.
Note A Simplex rack or channel number can be modified. The rack can be promoted
to TMR or Triad. However, a TMR rack cannot be demoted to Simplex.
TMR Rack in Outline and Summary View

Click the TMR rack in Outline View to The Summary View displays a graphic of each
display all channels in Summary View. rack, with all the boards it contains.
A TMR rack displays

four lines in Outline
View, which represent
the rack and three
channels. The first line
displays the rack
number, the rack name
Channel R/S/T and the
type TMR. Click this line
to insert boards that
operate in TMR mode.
The next three lines

define each of the three
channels: R, S, and T,
including the rack
number, channel name,
and rack-type Simplex.
Click one of these lines
to insert boards that
operate in Simplex
mode.
Note These TMR racks cannot be modified.
I/O Boards
To insert an I/O board
1. From the Outline View, click the item to upgrade.
2. From the Edit menu, select Insert First. The Select an I/O Board dialog box
displays.
Select the board to

be inserted.
Select the hardware

form for the channel
indicated.
Click to view the

release notes
The Choose Compatibility Code dialog box displays the
available compatibility codes with the newest code
displayed at the top of the list.
Configure the
board's slot
number.
To configure
the terminal
boards, select
the item and
select Modify
(or double-
click) to display
the Terminal
Board
Properties
dialog box.
Configure Boards
A point can have configuration data, as shown in the summary view below for
ThermCpl3.
Configuration is data that
applies to the complete
board.
Card Points contain I/O
points not directly associated
with a terminal board.
Signals can be attached to
Card Points, I/O points, but
not Internal Variables
Modify the board by clicking +

to expand it.
With the right mouse button,

click on an item name. Select
Modify from the pop-up
menu.
Refer to the following sections

for more information on each
board item.
The configurable items for the terminal board points can be modified at one common
window.
To modify a points configuration
1. From the toolbox, Outline View, expand the I/O board.
2. Expand the terminal board (J3J4:IS200TBTC).
3. Right-mouse click on the point to modify and select Modify from the shortcut
menu. The following dialog box displays.
5. Click on the desired Value cell to modify the configurable item. Depending on
the typeof configurable item, drop down items are displayed, or you can enter a
number.
6. Click OK button. The values are saved to the configurable items. When the
point is selected in the toolbox outline view, a list of the configurable items and
their values display in the summary view.
Both board points and points that are part of a terminal board can be connected to a
signal, using the upper part of the MarkVI Point Edit dialog box. A point that does
not have any configurable items uses a different dialog box as shown in the next
section.
Note Other configurable items include regulators, terminal boards and monitors.
Configuration
Depending on what item is

selected under Configuration, a
dialog box displays to enable/
disable, select high/low limits,
select operation mode
such as TMR or Simplex.
(This dialog box is also used

when configuring points under the
item Card Points.)
Card Points
A point can be configured and be modified by selecting the Edit menu, then
Modify. The software configuration dialog box displays.
The board, VTCC,

contains the items
Card Points and
terminal board with
points.
The points contain

Configuration,
which can be
modified.
Both of these items can be connected to a signal using the Point Edit dialog box.
To connect a signal to a point
1. Expand the configuration item and select a point.
2. From the Edit menu, select Modify. The Point Edit dialog box displays.
Enter the name of the signal to

connect or click Browse to
search for an available signal.
Displays the Point Descriptors

dialog box where you enter
distinct information about this
point.
Edit the signal you entered as the

signal connection.
Note Other items in this dialog

box are fixed and cannot be
modified for a Mark VI I/O.
Terminal Boards
Some properties of a terminal board can be modified.
To modify the properties of a terminal board
1. Click on the terminal board to select it
2. From the Edit menu, select Modify. The Terminal Board Properties dialog
box displays
The Connector
Name cannot be
changed.
The Connected
box must be
checked to
configure the
Terminal Board
and the
Hardware Form.
Select the
terminal board
and the hardware
form to be used.
Upgrade Boards
You can upgrade existing boards and modify some of the boards attributes.
To upgrade a board
1. From the Outline View, click the item Mark VI I/O to highlight it.
2. Select the Import button or from the File menu, select Import. The File Open
3. Select the file, Mark_IO.tre. Click Open.
4. Once all .tre files are imported, go back to the Outline View. Select the board
to upgrade. Right-mouse click and, from the shortcut menu, select Upgrade.
5. Select the hardware form factor and other attributes with dialog boxes described
in the preceding section, Select I/O board.
Note If a terminal boards connection status changes, an offline change occurs and a
warning message displays for confirmation. Once inserted, terminal board properties,
hardware form factor, or compatibility codes can only be modified by upgrading the
board.
Compare I/O Board Commands

Use the following commands to compare an uploaded I/O board.
Compare with configuration information
Upload the board configuration to a binary file
Compare a previously loaded binary file to the configuration
Compare Configuration
To compare the board configuration with the current configuration
From the Outline View, right-mouse click on the board and select Compare
Configuration from the shortcut menu.
Any differences display in a window as follows:
Select the check box

next to the item to
read configuration
contents into the
current configuration.
Click to generate a
report of differences.
The following report displays.
Note Comparing a TMR board can result in three differences per board since a
comparison is done for all three boards and generally the same configuration is
downloaded to all three. To accept the boards value into the current configuration
from the Differences dialog box, click the check box next to any one of the three
values, then click OK.
Download Board Configuration
All the configuration items within a board can be downloaded for one board, a whole
rack, or all the racks.
When you select Mark VI I/O To download board configuration
or any of its associated items
1. Select the item to download.
under the Hardware and I/O
Definitions section, the menu 2. From the Config menu, select Download. Or, right-click the item to
bar will change to include the download and select Download from the shortcut menu.
Config menu.
Download Firmware
To download Mark VI firmware
1. In the Outline View, select Mark VI I/O.
2. Click the right-mouse button and select Download from the following menu:
3. From the Download all Mark VI I/O dialog box, select Download Firmware.
Click OK.
4. The following warning displays. Click Yes to start downloading firmware to the
cards in all the project racks. Refer to the status messages at the bottom of the
toolbox window.
Compare Board Revisions
To compare board revisions between device and toolbox
1. In the Outline View, select Mark VI I/O.
2. Click the right-mouse button and select Compare H/W Board Revisions
from the following menu:
3. If the device is not online, the following message box displays:
4. Click Yes to connect to the device and read board revisions. Click No to read
only Toolbox board revisions.
The output is displayed in a window as follows:
A # icon indicates there is a difference between toolbox and device values. The
difference could be in any of the values card name, hardware form, and
firmware revision.
Upload Configuration to File
Upload a board configuration into a binary file to allow it to be accessed for
comparisons.
To upload a configuration into a binary file
1. From the Outline View, right-mouse click on the board to be compared.
2. Select Upload Config to File from the shortcut menu.
3. Select a file name for the binary file (a suggestion is provided, based on device,
name, channel, board, and slot.)
4. Click Save to save the file.
Compare Configuration to File

You must have access to a binary file to use this command.
To compare configurations
1. From the Outline View, right-mouse click on the board to be compared.
2. Select Compare Config to File from the drop-down menu.
3. Select the correct file, then click Open to complete the comparison.
Refer to the section, Compare Configuration, for the results of this compare.
VSVO Servo Board
The VSVO board controls four electohyralic servo values (refer to the section Insert
I/O Board). In the toolbox configurable items include, Regulators and Monitors. Up
to four Regulators, which are automatically numbered consecutively, can be added to
a configuration.
To add a Regulator
1. From the toolbox under VSVO, expand the items and select Regulators.
Right-mouse click on
Regulators
Select Insert First from the

shortcut menu.
Regulator 1 is inserted.
2. Calibrate the Regulators as follows:

(LVDT/R Calibration Dialog Box).
Right-mouse click on the

Regulator 1.
Select Calibrate from the

shortcut menu.
The following Warning
displays.
Click Yes to continue with the calibration process.
If the controller is not online

the following dialog box displays.
Click Yes to go online to

calibrate the regulator.
The LVDT/R Calibration
dialog box displays (refer to
the next section).
Click No and the toolbox allows you to select to view Constant
(refer to the section, LVDT/R Calibration Dialog Box).
LVDT/R Calibration Dialog Box
This command starts the Click View to display the
Note Each variable is Calibration Mode. predefined Position Gain and
monitored to see if the state Click On to enter Calibration Position Offset tuneup
was performed successfully. Mode or click Off to unselect constants stored in the board
the mode. (refer to the section, Calibration
Calibrate Sequence Constants Dialog Box).
commands
are as follows:
Click Min End Pos to stroke

the actuator to the minimum
end position.
Click Fix 1 to read the voltage

at the Min End Pos.
Click Max End Pos to stroke

the actuator to the maximum
end position.
Click Fix 2 to read the voltage

at the Max End Pos.
Click Calibrate to use the

calculated values.
Click Save to save calculated

board values .
The values are saved in the

toolbox and downloaded with a
new sequence number.
Dynamic Signals are During the verification process, you can send a manual
available while online and value to the board and inspect the movement of the
when this dialog box displays. actuator.
These signals are supplied
with voted live data through Verification commands are as follows:
the controller.
Click Off to turn off this mode.
Click Manual to enter a value in the text box.
Click Send Manual to send the entered value to the

board.
Click Verify Position to step the current and monitor the

position.
Click Verify Current to step the position and monitor the

current.
The Trend Recorder allows you to view the actuator

position or current feedback.
Tip If the calibration permissive is not set, all command buttons are grayed out.
This permissive is driven by controller blockware. The output point is CalibEnabx
where x is the selected regulator. Find this point in the application code and
determine why the permissive is not set. Once this permissive is set, return to this
dialog box and select On again.
Once in Calibration Mode, all the command buttons are available. The toolbox
monitors the calibration permissive and the state bit as follows.
If calibration permissive is lost, all buttons on the dialog box gray out, except for
the Constants View button and the Dynamic Signals list.
If the calibrate state bit is lost, all buttons on the dialog box gray out, except for
the Calibration Mode On and Off, the Constants View button, and the
Dynamic Signals list.
In Simplex and TMR operations, you receive a message from any of the requested
commands that are not complete. For example, in a TMR operation, if the
Calibration Mode was requested for all three channels (R, S, and T) and only the R
and S channels are available, you are notified that the T channel would not go into
Calibration Mode.
Verification is found on the In Calibration Mode, you can step through the calibrate process by selecting each
Calibration dialog box, just button in the field, Calibrate Sequence. If the requested state is achieved by all
under the field Calibrate appropriate systems, the button stays depressed. If there is a problem, the command
Sequence. button releases, indicating that the requested state was not achieved. The Min End
Pos, Fix 1, Max End Pos, Fix 2, and Calibrate buttons are mutually exclusive
(only one state may be active at any one time).
Modify Regulator & Monitor

The configurable items Regulator and monitor can be modified at one common
window.
To modify a Regulator or Monitor
1. From the toolbox, expand the VSVO board.
2. Expand the Regulator or Monitor.
3. Right mouse click on the item to modify and select Modify from the shortcut
menu.
Note You must have a privilege level 4 to view the configurable items unless.
4. The following screen displays.
5. Click on the desired cell to modify a configurable item. Depending on the type
of configurable item, shortcut menu displays to allow you to modify the value.
6. Click OK button. The values are saved to the configurable items. When the
Regulator or Monitor is selected in the toolbox outline view, a list of the
configurable items and their values display in the summary view.
Trend Recorder
After the verification process, Position and Current signals are trended. The Position
signals are attached to Reg1_Fdbk, Reg2_Fdbk, Reg3_Fdbk and Reg4_Fdbk. The
Current signals are attached to ServoOutput1, ServoOutput2, ServoOutput3, and
ServoOutput4.
The Trend Recorder is started with the signals ready for trending. After a time delay,
Trending samples are taken
a message is sent to the board to begin the trend. The time scale, x-axis for the
at 32 ms.
command Verify Position, is 10 seconds. The time scale, x-axis for the command
Verify Current, is 30 seconds. The magnitude, y-axis, for Position is defined in
current Regulator mode in the Outline View as follows:
The minimum Position value

is MinPOSValue minus 10.
The maximum Position value

is MaxPOSValue plus 10.
VSCA Serial Interface Board

The VSCA board is different from other I/O boards in that it consists of six
configurable serial ports. The VSCA is never a TMR board. Each port can be
configured as a pressure transducer, electric valve drive, or Modbus master interface.
When a VSCA board in

inserted in the Outline
View, port items display
under the DSCB terminal
board item.
To specify the interface for a particular port
From the Outline View, right-click the port name, then select Insert First
from the shortcut menu.
The following dialog displays.
Because of the unique The pressure transducer and electric drive interfaces have fixed interfaces once they
communications requirements are inserted for a port. The points and software configurations are modified using the
of the pressure transducer same dialog boxes as the fixed interface I/O boards described earlier in this chapter.
interface, it is only available
on ports 1 and 2.
Configurable Items
The Modbus master interface (Modbus Port) can have any number of stations, pages,
and points inserted.
To insert a station
From the Outline View, right-click the item Modbus Stations and select Insert
First from the shortcut menu. The item Station1 displays in the Outline View.
The pages and points of a station can be added by importing a special .csv file that
defines the points for that station. Importing a .csv file into a station with existing
points creates new points provided that the address software config does not conflict
with the address of an existing point on a particular page.
The item, Station 1, displays
in the Outline View.
Four types of pages can be inserted

in each station. These correspond to
the four register types.
Insert a register page by

right-clicking on Modbus
Pages. Select Insert First.
The Select Insertable Hardware Module dialog box displays.
The page is inserted and displays in the Outline View.
Right-mouse click
and select Insert
First.
The Modify Point Connection dialog box displays.

signal or click Browse
to search for an
available signal.
Select the data type for

the scaled point in the
controller, either Bool,
LInt or Float.
Select the direction of
the point, either Read or
Write.
Note Omitting the signal connection displays a spare in the Outline View although
to avoid using Modbus bandwidth the UpdateRate software config should be set to
Never.
Shortcut Menu Commands

The following commands are available for VSCA configurable items.
Modbus points can be
sorted according to
address. The VSCA
firmware can then group
different points into the
same message to make
the link usage more
efficient.
Import points (.csv
file) to Station or
Modbus Pages.
Export the pages
and points of a
station.
Sequence of Events
There are a number of Mark VI boards capable of using sequence of events. The
example below is a VCCC board with contact inputs, which have events defined.
If a contact input has an event defined and this input is enabled through its software
configuration, a message displays on the defined CIMPLICITY screen. An soe.dat
file is created with the Build command and placed on the user's hard drive. This file
has the associations between the sequence of event drop number for this point and its
signal name. It allows the event transition to display correctly on the associated HMI.
Tip Make sure that all devices are kept in separate folders. This soe.dat file will
always be generated, regardless of the device name. For example, if there is a
G1.m6b and a G2.m6b in the same folder, they will both generate the soe.dat file.
The last one to write out the file will be the last available sequence information. So
to get unique device sequence-of-event information, make sure that all devices are in
separate folders.
EGD Interface
Addresses of the points on the Ethernet Global Data (EGD) is a control network, as well as a protocol for the Mark
exchanges are made known to VI controller. EGD uses Ethernet as the physical and data-link layer of the network.
other controllers through the It can send directed or broadcast messages. Devices share data through EGD
SDB. exchanges (pages).
Note Exchange is a CIMPLICITY term, which means the same as the term page in
the toolbox. Exchanges provide a way to share live signals (variables) over Ethernet.
To insert the EGD Interface network

2. From the File menu, select Insert First. The New I/O or Network Interface
3. Select EGD Interface and click OK. The network is inserted into the Outline
View as shown below.
Ethernet Global Data

(EGD) network
The network is assigned a default name (EGD1), number (0) and Producer ID. To
edit the settings, refer to the next section, Edit EGD.
Edit EGD
The dialog box displays a default name (EGD1), number (0) and Producer ID.

Interface to be edited. A
default name is generated
when the EGD is inserted.
The number is found in the

SDB. If set to zero, this is
assigned when it is put into
the database.
The default IP address is

1.1.1.1. A unique address
or name can be entered.
Double-click the device
name to refer to the IP
address in the Device
Properties dialog box.
Enter the .tre file to export.
Enter a note to describe Click OK. The network

the network. The note can displays un the Outline
be up to 50 characters. View under the
Hardware and I/O
Definitions item.
EGD Exchanges
Exchanges (pages) provide a way to share live signals over EGD. These exchanges
are periodically broadcast by the owner using EGD shared RAM update messages,
known as feedback messages. The exchange broadcasts every 320 milliseconds by
default, but you can set the interval to any value not less than 10 milliseconds. An
exchange can be a maximum of 1400 bytes long and is addressed on byte
boundaries. Boolean points are packed eight to a byte, and the bit number that
describes which one ranges from zero to seven. A controller can own up to 16
exchanges, although the limit is five by convention.
Note Once the EGD network is inserted under Hardware and I/O Definitions in the
Outline View, the EGD exchanges must be inserted.
To insert an exchange
1. From the Outline View, click the EGD network name to highlight it.
Or click the right-mouse 2. From the Edit menu, select Insert First. The item Exch1 is inserted under the
button and select Insert First. item, EGD network. The default name of the exchange is Exch# (where # is the
number of exchanges owned by this controller).
Note Once an exchange exists, another item can be inserted by following the same
steps, but select Insert Next.
These exchanges are sometimes referred to as internal exchanges in the toolbox

controller. Exchanges owned by other controllers are called external exchanges.
Internal exchanges can be modified using the Internal Exchange Settings dialog
box.
To modify an internal exchange
1. Click a exchange to highlight it.
Or double-click the exchange. 2. From the Edit menu, select Modify. The Internal Exchange Settings
dialog box displays (refer to the next section, Internal Exchange Settings).
Internal Exchange Settings
This data field is used
by ToolboxST.
Enter a name ( up to five
characters).
Enter a number (1 to 255) or
enter zero for the device to be
posted to the SDB and
assigned the next available
number.
Enter the frame period for the
EGD exchange. Each Frame
Period is equivalent to 40
ms. The Exchange period
determines the time between
EGD feedback transmissions
on Ethernet. The default
Frame Period is 8 (320 ms)
Check this box so this
exchange to receive signals
that are flagged as network
signals when the command
Put to database is used.
Select the Broadcast or

Directed. Broadcast allows
signals to be sent on multiple
Ethernet (if available).
Directed specifies a
destination address for the
exchange.
% Allocated is the
percentage of exchange
memory that is allocated.
% Free is the percentage of
exchange memory remaining
CfigSig is the Configuration
Signature. It provides the
current version number of the
controller and notifies users
of modifications to the
exchange, which are Click to keep the Click to unlock all Click to reclaim all
monitored by other memory location of signals and allow the lost memory.
controllers in the system. The points with signals on memory location of
number is checked for the exchange. points that have
consistency between the signals to change.
exchange being broadcast by
the owner and the users
copy.
Only one internal exchange can be checked to Receive Network Signals. When one
exchange is checked, any previously selected exchange is automatically cleared.
When the command, Put to database is performed, any signals flagged to be
network signal (see Chapter 3, Configuration, Signal Definitions, Define Signal
Definition) are automatically connected to this EGD Exchange. This happens only
for signals that are not already connected. There is also a batch command to
Instance Network Signals, which does the same thing as the command, Put to
database.
For another way to add network signals to an exchange, from the Outline View,
right-click an exchange and select Add Network Signals. This adds all signals
flagged as network signals (but not already connected) to the Exchange.
Whenever a point is deleted from an exchange (in the Outline View), that space is
not reclaimed. All controllers referencing that exchange must update from the
database. This loss of memory can be seen in the % Loss field of the Internal
Exchange Settings dialog box. To reclaim this lost space, compress the exchange.
The following Warning displays.
External Exchanges
The External Exchange data displays in the Summary View (shown below). This
data includes the signal name, a list of the points on that exchange, data type, health,
and so on. When the controller is monitored online, the second column, Value,
displays the live data value for the point on that line.
Note External Exchanges cannot be modified. A message box displays stating that
you are not the owner.
EGD external exchanges have two built-in diagnostic mechanisms: exchange healthy
and link presence. The link presence for a controller is True whenever messages are
being received from that controller. When the exchange healthy for a controller is
True, feedback messages are being received from that controller. When the health of
a variable (signal) connected exclusively to an EGD point is used in blockware, the
exchange healthy is actually the value used.
When the controller gets information from the database, exchange zero is inserted
into the network and called LINK. This exchange holds a list of signals called link
presence bits, which are set whenever an EGD message is received from a controller.
If no messages arrive for a controller in 1.28 seconds, the value of the link presence
signal goes to zero. These signals can be used in blockware like any other signal. The
form of the name is NET\DEV\ExchangeNameHEALTHY where NET is the name of
the network, DEV is the name of the controller, and ExchangeName is the name of
the external exchange.
EGD Points
A point can only be inserted EGD exchanges are made up of points, which are associated with controller signals.
into an internal exchange. Each point corresponds to a complete signal, regardless of the length or amount of
memory that the point occupies in the exchange. The name has the form
EGD.BYTE.BIT, where BYTE is the eight-bit byte offset into the exchange, and BIT
is the bit number, which ranges from zeroseven (seven is the most significant bit).
Note New EGD points added to an existing EGD exchange can be downloaded
online. If points are deleted from an exchange an offline download is required
To insert and modify a point

1. From the Outline View, click the EGD exchange to highlight it.
Or use the shortcut keys, Shift 2. From the Edit menu, select Insert First. The EGD Point Settings dialog
+ Insert box displays. It is used to insert and edit EGD points.
Enter the Name of the signal associated with this point. This
Select the Data Type from name must be provided to create a point. Click Browse... to
a drop-down list of data select the signal using the Signal Selector dialog box.
types supported by the
EGD. These data types
are different from the basic
controller data types and
are listed below.
Select Lock to set the
work offset and bit
number. (Also use the
Lock All Signals and
Unlock All Signals
command in the Internal
Exchange Settings
dialog box).
Address is assigned by
the toolbox to a point that
is Byte.BIT.
Enter Write for the

controller to produce
information or Read to
receive information.
CIMPLICITY Resource
allows you to mark this
particular signal to be
moved into the
CIMPLICITY database
using the SDB Exchange. The Health Address is Edit Signal displays the Signal Edit dialog
provided for signals that box. The button is only active when the point is
need health, such as being inserted.
DLAN+ and Genius.
Feedback Data Types

BOOL - 1-bit value DWORD - Long (32-bits) integer
WORD - 16-bit integer REAL - 32-bit floating point number
Tip EGD points can be created in the Outline View by using drag-and-drop to
insert a signal definition in the exchange item. This point data type is compatible
with the data type of the signal being dropped. The direction is assumed to be a
feedback. Modify the point data type using the EGD Point Settings dialog box.
EGD Points in the Summary View

The Summary View displays a diagram of the point and its connection to a scale
and signal. Each connection can be edited from the Summary View.
To edit the point, signal, or scale
1. From the Outline View, click the point. A diagram of the point and its
connection to a scale and signal display in the Summary View.
2. From the Summary View, double-click the actual point, signal, or scale. The
appropriate Edit dialog box displays.
When the controller is being monitored online, the Summary View displays the
live data value for the point and the signal connected to the point, as shown in the
screen below. Normally these two values should be equal. If they are not, make sure
the task that uses that signal is enabled. At least one task using that signal must be
enabled for an I/O transfer to run and copy the point value into the signal value, or
vice versa.
To modify/force a point or signal value
Or click . 1. From the Device menu, select Online.

2. From the Outline View, click the point. A diagram of the point and its
connection to a scale and signal display in the Summary View.
3. From the Summary View, double-click the actual point value or signal value.
The appropriate Edit dialog box displays.
Genius Networks
This is a Simplex option only. The controller receives inputs from and sends outputs to field devices, such as light
sensors or switches using elements of GE Fanucs Genius system line of I/O
products. The products, Genius Blocks and the Field Control I/O modules, are used
by the controller and defined with the toolbox.
For a description of each A Genius network provides a medium for controllers and I/O devices to
Innovation Series controller, communicate. Each network supports up to 32 devices, including controllers, Genius
refer to GEH-6410, Blocks, Field Control I/O Stations, and others. A controller can support up to two
Innovation Series Controller Genius networks. Each Genius network item is composed of definitions of Genius
System Manual. Blocks and Field Control Stations and their interfaces.
To insert a Genius Network
Another item can be added by 1. From the Outline View, click Hardware and I/O Definitions.
following the same steps, but
2. From the Edit menu, select Insert First. Or, click the right mouse button and
select Insert Next.
select Insert First. The New I/O or Network Interface dialog box displays.
3. Select Genius Network. Click OK. The item Geni_:IC660ELB912 is inserted

as shown below. This network can be modified (see the next procedure).
Up to two Genius
networks can be
inserted
To modify the Genius Network
Double-click the item Geni_:IC660ELB912. The Genius Network
Configuration dialog box displays.
Genius Network Configuration

Genuis network that
displays on the
hardware
elementaries.
Select a number from

the drop-down list of
the GENI that
identifies it with the
controller.
Specify the .tre file to
which the
configuration will be
exported.
Genius Network View
When toolbox is offline, the The Genius Network view represents the physical Genius network. It displays all 32
Genius Network view displays drops of the network, the name and type of occupied drops of the network, and the
names and types on the drops, discrepancies, if any, between what is defined to be on the network in the
as defined in the toolbox. configuration and what is actually on the network.
To display the Genius Network view
1. Click the item Geni1:IC660ELB912.
2. Click the Tracking icon to turn on tracking. This displays the Genius
Network View.
Right-mouse click
anywhere on this
view to display a
command menu to
upload, download,
and display
network and block
data. These
commands are
described below.,
Note When online, certain menu commands apply to a selected block in the view.
Click a block to highlight it (in the color cyan) before activating the Genius Net
menu.
Display Fault/Fault Info is used to show the force and fault status of each block
on the Genius Net view.
Display Block Detail View displays the Detached Summary View for the
block highlighted in the Genius Net view.
Download Block Configuration downloads the configuration from the toolbox
to the highlighted block in the Genius Net view.
Upload Block Configuration uploads the configuration from the highlighted
block on the Genius Net view.
Compare Block Configuration compares the configuration of the highlighted
block to the contents of the toolbox. Differences are noted in the Genius List
dialog box and can be saved.
Display Block Forces displays a list of all forced points for the highlighted blocks
using the Genius List dialog box. This list can be saved.
Display Block Faults displays a list of all faults on the highlighted block using the
Faultlist dialog box. This list can be saved.
Display Block Edit Dialog activates the Genius Block dialog box for the
highlighted block.
Download Network Configuration downloads configuration of All or Selected
blocks.
Upload Network Configuration uploads configuration of All or Selected blocks.
Display Network Forces displays a list of all forced points on the network using
the Genius List dialog box. This list can be saved.
Display Network Faults displays a list of all faults on the network using the
Faultlist dialog box. This list can be saved.
Display Network Edit Dialog activates the Genius Network dialog box to add,
delete, and move blocks on the net.
Configure Genius LAN Board
The Genius LAN board (GENI) is the Genius Network interface module for the
controllers. Each GENI that connects a controller to a Genius network requires a
number of software configuration items. These items are given default values when
the Genius LAN is defined and can require custom configuration, as follows:
To view the GENI software configuration items
Click the icon to reduce 1. From the Outline View, click the icon Geni_:IC660ELB912 to expand
the item levels. the level to display the items HwConfigs and SWConfigs.
2. Click the icon SWConfigs to expand it, as shown. All configurable items
display.
Configuration
items
To modify a configuration item

Double-click an item, such as Sri. The Software Configuration dialog box
for this item displays.
Note This dialog is the same for all items under SWConfigs. The GENI
configuration is sent to the controller as part of the Pcode. It is necessary to reboot
the controller after downloading so that the GENI is reconfigured with the new
pcode.
The SWConfig items are defined as follows:
SRI is the location of the GENI Shared RAM Interface (SRI) in the controllers
physical memory space. In a DS200UCPB controller and VME controller, the
address is 0xC8000 for Geni1 and 0xCC000 for Geni2. The controller runtime
software writes output values to the SRI, and the GENI sends output to each block
every bus scan. The runtime software code reads from the SRI the input values
reported by the Genius Blocks and Field Control Stations every bus scan.
IoPort is the I/O port address used to start and reset the GENI. It is also used to
read the status of the GENI. In a DS200UCPB controller, the I/O Port is a single
byte at port address 334 for both GENIs. For a VME controller, the I/O port
address is 334 for Geni1 and 335 for Geni2. There should be separate ports for each
GENI in a pc.
SetupPort is the I/O port address used to configure the GENI. In a DS200UCPB
controller and a VME controller, the SetupPort is 336 for Geni1and 337 for Geni2.
DropNumber is the drop number of the GENI on the attached Genius network. It
must be between 0 and 31. Drop number 31 is the recommended setting of this
parameter for the GENI. For additional Genius, use drops 1, 2, and so on for
efficient datagram operation. Drop 0 is typically reserved for a hand-held monitor.
BaudRate is the speed of data transmission on the Genius network. It is usually set
to 153.6 kBd, but can be reduced for long Genius networks. If the network is longer
than 4500 feet, use the 38.4 kBd setting; between 3500 and 4500 feet, set the baud
rate to 76.8 kBd; between 2000 and 3500 feet, use the 153.6 kBd extended setting;
and if the network is shorter than 2000 feet, use the 153.6 kBd standard setting.
OutputEnable is a GENI setting that determines whether the GENI sends output
data to all blocks immediately after it is started. The recommended setting is
Disabled. The controller runtime software determines when the GENI is enabled to
send output to each individual block. Output Enable is also a Genius Block
configuration field. A block with output enabled contains a Pcode record that
instructs the controller to enable the GENI to send output to the block.
Refer to the section Genius GlobalData is the setting that enables the GENI to send global data. Currently, the
Blocks. list box has three selections to specify the amount of global data to be used. Select
either None (the default), glb32GENI, or glb128GENI. The item glb32GENI
enables 32 bytes of global data to be configured, apportioned as 128 discrete and 8
analog points. The gbl128GENI enables 128 bytes of global data to be configured,
apportioned as 64 analog points. Outgoing global data is modeled as a pseudo block
that is automatically inserted in the Genius network tree when the GlobalData
selection is entered. Its block number is the drop number of the associated GENI,
and its name is that of the GlobalData selection (glb32GENI or gbl128GENI).
Global data broadcast can be received from other sources, such as Series 90-70 PLCs
or controllers, by adding appropriate global data blocks.
Genius Blocks
To add and configure Field Individual I/O field devices are connected to Genius Blocks or Field Controls, which
Controls, refer to the section, communicate their states (ON/OFF) and values to the controller over the Genius
Field Control Station. Network. Genius Blocks in a controller are inserted using the Add Genius Block
dialog box.
Insert a Genius Block

To insert a Genius Block
Another item can be added by 1. From the Outline View, click network item GENI_:IC660ELB912.
following the same steps, but
2. From the Edit menu, select Insert First. Or, use the right-mouse button, click
select Insert Next.
network item GENI_:IC660ELB912 and select Insert First.
The Add Genius Block dialog box displays (refer to the next section).
Add Genius Block Dialog Box

Controls the outputs for the selected Enter the Field Control BIU for the
drop by enabling/disabling the writes to Genius network that displays on
Genius outputs from the controller. the hardware elementries.
Enter a drop location

for the block (0-31).
Select a Field Control

Module from the drop-
down list. They display
in alphabetical order.
Configure Genius Block
Click on the Genius

block in the Outline View
and select Modify.
The Genius Block Configuration dialog box displays to modify the block fields
(refer to the next section).
Enter the block name on the

hardware elementary diagrams or
change and enter a new label in
the text box.
Set the drop location for this

block.
Enter the blocks table

address in a GE Fanuc
Series Six.
Enable or disable the outputs

for this block.
Automatically aligns the dual

resolver I/O module offsets.
Note Block drop numbers must be configured in each block with a hand-held
monitor.
Genius Block Detail View
The Block Detail View displays live data of points belonging to the Genius Block. If
Click to go online and
the block output is enabled to be sent to the physical block, the output values are
view data.
displayed in green. If output values are disabled (on hold at the GENI SRI), they
are displayed in yellow. All other live data displays in green. If there is no online
data, the data displays in black.
To display the Block Detail View
1. From the Outline View, click the Genius Block and click . Or
2. Click the Genius Block to highlight it.
3. From the View menu, select Detached Summary View.
The following window displays Genius Block data.
Genius Block Menu

The Block Detail View has a menu of commands to force/unforce points, display and
clear point faults, write notes, and such. Force and fault information on points
displays automatically. Updates of the force/fault information is updated any of three
ways:
When a point is clicked and 30 seconds have passed since last update
If a point is forced/unforced
If Display Block Fault or Display Point Fault command is selected from
the Genius Block menu
A forced point is indicated by the character F. A fault on a point is indicated by a red
dot (stop light). Both display between the points value and the points name. When
the force/fault information is at least 30 seconds old, the gray background displays
on the force/fault display area.
To display the Genius Block menu
Click the right-mouse button anywhere in the Genius Block Detail View. The
following commands display:
Display Block Faults displays a list of all faults on the block using the Faultlist
dialog box.
Unforce All Points on Block removes forcing from forced points on the block.
Toggle Output Enable changes the blocks output/enable state to the opposite
state after you respond to a Yes/No confirmation dialog box.
Display Block Edit Dialog activates the Genius Block dialog box.
Display Block Notes displays the Notes dialog box to enter notes on the Genius
block.
Display Point Fault displays all faults associated with the highlighted point.
Force/UnForce Point activates the Point Forcing dialog box to force/unforce
the selected point.
Display Point Notes displays the Notes dialog box to enter notes about the
highlighted point.
Field Control Station

Refer to the section, Genius A Field Control Station is made up of a Genius Bus Interface Unit (BIU) and up
Networks. to eight Field Control I/O Modules. Each Field Control module communicates on
the Genius Network through the BIU. The Field Controls BIU is inserted to the
Genius Network using the Add Genius Block dialog box.
For more information, refer There are conventional Field Control modules, which provide or receive just one
to the GE Fanucs Genius type of I/O data (usually referred to as reference data). Also, there are intelligent
product manual, GFK-0825C. modules that provide and receive multiple types of I/O data, usually referred to as
reference parameters. To insert and configure conventional and intelligent modules,
refer to the next three sections.
The field parameters to be set include the length and reference address for each
Series 90-70 register type (I, Q, AI, AQ) and the starting address for each field
control module in the Field Control Station.
All lengths are in I/O points or Series 90-70 registers, and all addresses are in the
corresponding register space, which all begin with register 1. The size of an I/O point
or register depends on the register type where register types I and Q are one bit in
size, and register types AI and AQ are one word in size.
To insert a Field Control BIU
1. From the Outline View, click the network item GENI_:IC660ELB912.
Another item can be added by 2. From the Edit menu, select Insert First. Or, use the right-mouse button, click
following the same steps, but network item GENI_:IC660ELB912 and select Insert First.
select Insert Next.
The Add Genius Block dialog box displays (refer to the next section, Insert Field
Control BIU).
Insert Field Control BIU


Select a Field Control

Module from the drop-
down list. They display
in alphabetical order.
Configure Field Control BIU
To configure the Field Control BIU
From the Outline View, double-click the BIU Field Control, such as
IC670GBI002 (under the item GENI:IC660ELB912). The Field Control
BIU Configuration dialog box displays.
Field Control Station name

that displays on hardware Blocks table address in a
elementaries. GE Fanuc Series Six.
Sets the drop location for

this block.
Check to enables (uncheck

to disable) outputs from the
controller.
Enter the starting reference

address (usually 1) for each
data type.
Enter the length for the total

number of points for each
data type.
Auto Map automatically assigns the current address mapping. All four values in the Address row must be set. Check
that the starting points for each of the register types (Address row) are properly set as follows:
If the Genius Network connects only to the controller, then set the Address row to 1 (default setting) for each
register type (I, Q, AI, AQ).
If the network connects to a Series 90-70 controller, then the Address row must be set to the starting register in the
Series 90-70 where the field control data is configured to display.
Tip GE recommends using AutoMap because mapping can be a complex process

with many interlocking rules.
Field Control Module
To insert a Field Control module
1. From the Outline View, click a Field Control BIU.
Another item can be added by 2. From the Edit menu, select Insert First. Or, use the right-mouse button, click
following the same steps, but the Field Control BIU item and select Insert First.
select Insert Next.
The Add Field Control Module dialog box displays.
Enter the Field Control BIU that

Controls the outputs for the selected drop
displays on the hardware
by enabling/disabling the writes to
Genius outputs from the controller. elementries.
Enter the drop

location (0 - 31).
Select a Field
Control Module
from the drop-down
list. They display in
alphabetical order.
The following message box displays when the module and OK are selected.
Tip GE recommends using AutoMap because mapping can be a complex process

with many interlocking rules.
Configure Conventional Field Control Module
Once the module is inserted, the module configuration and its points can be
modified.
BIU Field
Control
Field Control
Module
Field Control
Points
To modify a conventional Field Control module

From the Outline View, double-click the Field Control Module item. The
Field Control Module Configuration dialog box displays.

Genius Field Control
module that displays on the
hardware elementary
diagrams.
Enter the slot number for

this module ( 1- 8).
Displays the I/O type for this

Field Control module.
Enter the starting reference

address for this module.
Displays the number of the

I/O type in points.
Configure Intelligent Field Control Module
Once the module is inserted, the module configuration and its points can be
modified.
BIU Field Control
Field Control
module
Field Control points
To modify an Intelligent Field Control module

From the Outline View, double-click the Field Control Module item. The
Field Control Module Configuration dialog box displays.
Enter the name for the Genius

Field Control module that
displays on the hardware
elementary diagrams.
Edit the slot for this module.
This field allows you to set up

the different reference
parameters (data types) for this
Intelligent Field Control module.
Any number of data types (1-4)
can be defined for a particular
Field Control module.
For the RTD module shown above, I, Q, and DQ data is defined, but not AI data;
therefore, it is grayed out. The addresses are reference addresses, just like
conventional modules. The lengths are in points, also like conventional modules.
Genius Block and Field Control Module Points
A point within a Genius Block or a Field Control Module can be an input from the
block to the controller or an output from the controller to the block.
To modify a point, signal, or descriptor
1. From the Outline View, double-click the point. The Point Edit dialog box
displays.
2. Use this dialog box to attach a signal to an I/O point, edit characteristics of the
signal, and specify the values of all the miscellaneous data fields associated with
the point.
Enter the point to edit.
Select Input or Output.
Data Type is the named

type of the I/O point.
To attach a signal to the

point or change the signal
associated with the point
enter the name of the
signal related to this point. Descriptors edit the various elements Click here to display the Signal
Click Browse... to select a associated with the I/O point, including a note Definition dialog box to edit
signal. string, a name plate string, the panel location, attributes of the signal, such as data
the panel name, type, tag, auxiliary drawing type, scale factor, initial value,
number, panel column ID, wire number, location descriptive text, and connection
and GE drawing number. The values in these (refer to the next section).
fields depend on the particular product process.
Third Party Operator Interfaces

A third-party operator can Third-party operator interfaces that contain a Genius Bus Interface (such as those
manufacture devices for use from AFE Technologies or Computer Technology Corporation) can be connected to
with a major manufacturer's the Mark VI Controller. These devices communicate by reading and writing data
products, usually without through an STRP register page in the controller. The data can be shared by both the
involvement from the major Cimplicity HMI and the operator interfaces.
manufacturer.
To insert a generic Genius Block device
1. From the Outline View, use the right-mouse button and click the item
Hardware and I/O Definitions.
2. From the pop-up menu, select Insert First. The New I/O and Network
Interface dialog box displays.
3. Select Genius Network and click OK. Geni:IC660ELB912 is inserted.
4. Use the right-mouse button to click Geni:IC660ELB912 and click Insert
First. The Add Genius Block dialog box displays.

Select other GENI-GB

Device with GENI
interface.
Note To configure the Genius Block, refer back to the procedures described in the
section, Genius Blocks.
Monitor Genius
The menus and dialog boxes The state of inputs and outputs, and the status of Genius Blocks and Field Control
are described in other Stations can be viewed using the toolbox. The functions described in this section
sections of this chapter. apply to online data on an active Genius Network.
Genius Network Live Data Display

Blocks display/disappear The online data display of the Genius network, called the Genius Net View,
from the view as they log in displays the blocks actively communicating on the network, the fault and force status
and out of the network. of each block, and the output enable/disable state of each block.
To view the Genius Net View
From the Summary View, select Geni_:IC660ELB912 and click to

turn on tracking.
If the toolbox is online, the blocks connected to the network are represented by small
pictures as follows:
If the block definition in a drop matches the physical block, the picture looks
like a Genius Block, a Field Control Station, or a GENI.
If the block definition does not match the physical block, the picture is an X
formed by two blocks, and the physical block type is indicated in parentheses.
If there is no defined block where a physical block displays, the icon is a block
with Undefined written on it.
If the block type is supported under the Hardware Module Library item, the
block type name is shown. Otherwise, the block type number is shown.
The following screen is an example of the Genius Net View/Summary View.
The view has a command menu to upload and display network and block data.
When the Genius Net View is started, the force/fault status of each block present is
obtained using Genius datagrams and displays for 30 seconds at the spot between the
block icon and drop number. Presence of fault in a block is indicated by a red dot
(stop light), and presence of forced points is indicated by the character F. After 30
seconds, the block output enable/disable live data indicator (OE, OD) replaces the
force/fault status display. A block with OE displayed next to it means outputs get
sent to the block; a block with OD means outputs are held up in the GENI shared
RAM interface (SRI). The force/fault status is shown on demand using the
ShowForceFaultInfo command in the Genius Net View menu.
Genius Block Live Data Display
The Genius Block or field control online data display, called the Block Detail
View, displays values of points in the block, the force and fault status of the points,
and the output enable/disable status of the block.
To display the Block Detail View
1. From the Outline View, select the Genius block, then click .
2. While online, from the Summary View, select the Genius block and activate
the Genius Net menu.
3. From the Genius Net menu, select BlockDetailView.
The Block Detail View displays live data of points belonging to the Genius Block
or Field Control. If the block output is enabled to be sent to the physical block, the
output values are displayed in green. If output values are disabled (on hold at the
GENI SRI), they are displayed in yellow. All other live data displays in green. If
there is no online data, the data displays in black.
Force and fault information on points displays automatically. Update of the
fault/force information is not automatic. Update of force/fault information on all
points is done when a point is clicked and 30 seconds have passed since last update.
Update is also done if a point is forced/unforced, or if a BlockFault or a
PointFault command is selected from the Genius Block menu.
A fault on a point is indicated by a red dot (stoplight). Forcing on a point is indicated
by the character F. Both the stoplight and F display between the points value and
the points name. When the force/fault information is at least 30 seconds old, the
gray background displays on the force/fault display area.
The Block Detail View has a menu of commands to force/unforce points, display and
clear point faults, write notes, and such. You can display the Genius Block menu
by clicking the right-mouse button anywhere in the Block Detail View.
A forced point has its forced value displayed. Forced value of Field Control output
and Genius Block analog output are obtained using datagrams and are therefore
updated at the same time as the point force/fault status. A gray background on a
point value means that it has been 30 seconds since the value was updated.
Upload
The NetConfigUpload and BlockConfigUpload commands are used to read
configurations to the toolbox from the actual devices in the Genius Network. This
operation overwrites the configuration originally in the tool for the selected blocks.
The Genius Block and Field Control Selection dialog box displays to allow you
to select all or several blocks and field controls to upload. Upload of a field control
includes the address map, BIU, and all I/O module configurations.
For a partial upload of a field control, use the BlockConfigUpload command.
Status of the upload is shown on the bottom windowpane. The uploaded
configuration data is viewed on a Genius Block dialog box, which is activated with
the BlockDialog command in the Genius Net menu.
Download
The NetConfigDownload and BlockConfigDownload commands are used to
download configurations from the toolbox to actual devices in the Genius Network.
The Genius Block and Field Control Selection dialog box display to allow you
to select all or several blocks and field controls to download. Download of a Genius
block includes changing the I/O configuration of the block (all input and output), if
necessary, as determined by the toolbox. This change takes the block out of the
network for about two seconds.
Download of a field control includes the address map, BIU, and all I/O module
configurations. A new address map and a configuration for a new I/O module cause
the Field Control BIU to get out of the network for about two seconds. For a partial
download of a field control, use the BlockConfigDownload command. Status of
the download is shown on the bottom window.
To download software configuration for block or field control station
1. Establish a connection to the target controller.
2. From the Summary View, select a block on the Genius Net View.
3. From the Genius Net menu, select BlockConfigDownload.
4. For the Field Control station, select which part of the Field Control to download
and select ReferenceAddress.
5. For the software configuration, click the Field Control station icon. Click the
right-mouse button anywhere on the view, except on the icons and names, to
show the Genius Net menu. Select BlockConfigDownload. Select which
part of the Field Control to download, and select the I/O module.
Note Genius Blocks and Field Control Stations can be configured at the factory and
downloaded when the system is shipped. If blocks are programmed on-site, compare
the blocks with the configuration and resolve differences before downloading.
Generate Force List

Forcelist commands are in the Genius List dialog box. The displayed information
includes the date and time the information is taken, the point name, and the
associated signal name and forced value. The complete name of a Field Control point
includes the drop number, point reference address, the I/O module slot number, and
I/O module point number. The information can be saved to a text file. Force list
commands are:
BlockForceList - generates a force list of all forced points in a block.
NetForceList - generates a force list of all forced points in a network.
Generate Fault List and Clearing Faults
Faults are displayed and cleared through the Faultlist dialog box. The Faultlist
dialog is activated when you issue a BlockFaultList command or a NetFaultList
command from the Genius Net View menu.
The Faultlist dialog is also activated when you issue a BlockFault command or a
Point Fault command from the Block Detail View. The Block Detail View
displays as a separate view in two ways. The first is activated is by selecting the
Genius block on the Outline View and then clicking the DetailView button of the
TOOLBAR. The second is activated by selecting the Genius network on the Outline
View with the tracking function on. This activates the Genius Net View in the
Summary View.
The fault list includes block faults, module faults, and point faults. The information
displayed includes date and time the information is taken, the network name, the
block name, the point name, the associated signal name, if any, and the fault text.
The Faultlist dialog has a ClearFaults button used to clear all faults in the list that
have been corrected. It comes back after a ClearFaults command with a list of
remaining faults. This information can be saved to a text file.
Force/Unforce I/O Points at the Genius Block Level
Forcing points in the controller can be done at the controller level or at the Genius
block level. At the controller level, forcing is implemented by the controller when it
writes the forced output value to the GENI SRI regardless of the control code
output. It uses the forced input value in place of the input value in the SRI. If output
to a block is disabled, all output forcing to that block at the controller level does not
take effect. Also, if the controller gets rebooted, forcing is lost until the controller is
running and starts implementing forcing again.
Forcing at the Genius block level is initiated when the forced value is sent by
datagram to the Genius block. The forcing information is kept in the blocks
EEPROM to survive power cycle. The Genius block uses the forced output value for
output, disregarding the controllers output data. It broadcasts the forced input value
in place of the actual input coming from the field device.
To force/unforce points at the Genius Block level
From the Outline View, select the Genius block, then click to display the
Block Detail View.
Or
1. From the Outline View, select the Genius Net with the tracking function on.
This activates the Genius Net View in the Summary View.
2. From the Genius Net View, select the block by clicking on its icon. Select
Block Detail View from the menu.
3. Click the name of point to be forced to highlight point.
4. Click anywhere on the view with the right-mouse button to activate the menu.
5. Select Point(Un)Force to display the Point Forcing dialog box. The Force
button enables the force value edit field to allow you to enter the force value.
The Unforce button unforces all points in the block.
Main Board
Right-click the controller The item Main Board currently holds the non-volatile memory. Inserting the Main
name and select Modify. Board depends on the type of controller selected in the Properties dialog box, such
From the tab General, select as the SD200UCPB, SD215UCV_, or DS214ACL_.
Platform and the desired
controller.
To insert Main Board
Or click the right-mouse 2. From the Edit menu, select Insert First. The New I/O or Network
button and select Insert First. Interface dialog box displays.
3. Select Main Board and click OK.
Non-volatile Random-Access Memory

Non-volatile random-access memory (NOVRAM) is battery-backed memory that
holds its values even when the controller loses power. This is used in the controller
to save values that change over time and need to be maintained through a power loss.
Upon starting the controller, the initial values specified in Pcode are written to the
signals RAM locations, followed by the values held in NOVRAM. The NOVRAM
values are not transferred into the signals when the NOVRAM major revision
changes (meaning the location of existing signals in NOVRAM changes) or for
points that were just added. Once the controller is running, signals associated with
the NOVRAM points are written to the battery-backed memory at the end of the task
in which the signals are used. When NOVRAM is added to a controller for the first
time, it is necessary to download the Pcode to permanent storage and reboot the
controller since the controller needs to add resources that it can only do at startup.
In the controller, NOVRAM is modeled as I/O. This means that each NOVRAM
location corresponds to a point. The NOVRAM signals are written as part of I/O
transfers after the execution of the tasks where those signals are used.
Insert/Modify NOVRAM
To insert NOVRAM in a Main Board module
1. From the Outline View, click Main Board.
Or use the shortcut keys, 2. From the Edit menu, select Insert First. Or, click the right-mouse button and
Shift + Insert. select Insert First. The New I/O or Network Interface dialog box displays.
3. Select Nonvolatile RAM (NOVRAM) and click OK.
The list of signals and their corresponding NOVRAM locations must be static for the
controller to restore values to the proper signals. Therefore, never move NOVRAM
points. The NOVRAM Edit dialog box displays statistics on memory space. It also
displays the option to sort the page order and the command to compress the memory
space, if required.
To modify NOVRAM
Or double-click the item 1. In the Outline View, click NOVRAM.
NOVRAM.
2. From the Edit menu, select Modify. The NOVRAM Edit dialog box displays.
Statistics display data on memory space as follows:

Version is a number incremented by the toolbox whenever a change takes place, such as
1.0. The first number is the major number and the second is the minor number.
% Allocated displays the amount of memory used.
% Free displays the amount of NOVRAM that can still be used.
% Lost displays the amount of NOVRAM that was lost because of the deletion of the points
that are not reclaimed so that the mapping of points is deterministic.
Page Sort Order rearranges

the list of NOVRAM points in
the Outline and Summary
Views, so that it is sorted
alphabetically by the signal
name or the point name. This
does not affect the order of
points in the NOVRAM.
Compress Page recovers unused

memory in NOVRAM that
accumulates when points are
removed without compressing.
This command increases the
major version number.
Note Only compress the page if a large % space is lost and not enough % space is
free in which to add the required data.
Modifications to the NOVRAM are shown in the Version number, such as 1.0. The
major number (1) increases whenever the page is compressed. The minor number (0)
increases when a point is added or deleted. This version number is used by the
runtime to know when to initialize the signal from NOVRAM when the controller
starts up. If the major number changes, nothing is transferred to local memory when
the controller starts. If the minor number changes, only the points that have not
changed are transferred to local memory.
NOVRAM Points
When NOVRAM points are inserted, the numeric value of the highest point number
is saved and used to assign the next point number/name. If a NOVRAM point is
deleted, the memory location of the point is not reclaimed until the Compress
Page command is executed.
To insert a NOVRAM point
Or use the shortcut keys, 1. From the Outline View, click NOVRAM.
Shift + Insert
Insert another item by select Insert First. The NOVRAM Point Edit dialog box displays.
selecting Insert Next.
Enter the point to edit.
Select Input or Output.
Data Type is the named

type of the I/O point.
Enter the name of the signal related to this View the signal note to make sure
point. Click Browse... to select a signal. this is the correct signal.
Sometimes a NOVRAM point is also mapped to another input point from a network.
When the controller starts up, the signal is restored to the value stored in NOVRAM.
In addition, the input point is given the same restored value, so that the first I/O
transfer from the point to the signal cannot give it meaningless values.
Signals that are forced in the controller are saved in NOVRAM and are not lost when
the controller is restarted. These force values are not restored if the major revision of
the application code changes because it is possible that the addresses of the signals
may have all changed. The NOVRAM is divided such that using all of the 512 points
available should not infringe on the memory available for forced points.
NOVRAM points can be added to the list of points using drag-and-drop. Drag the
signal onto the item NOVRAM in the Outline View. The point name and data types
are assigned automatically based on the signal that is dragged.
Register Network
Register network interfaces allow the controller to communicate with other devices
that do not use EGD over Ethernet or Status_S over the DLAN+, such as the
CIMPLICITY Human Machine Interface (HMI) and others, which hold their internal
data in registers.
Data is modeled as a set of register spaces that are either words or bits. Each register
space is given a type name, such as %M (bits) or %R (words). A number identifies
Pages can be created and
registers within a space. The controller interfaces with devices using a form of
instanced in the controller
shared memory that is updated over a network. The shared memory is referred to as
and put into the SDB.
register pages. A register page corresponds to part or all of one register space. The
HMI reads or writes registers defined by the controller. The %M and %R spaces
provide the only general purpose register facilities for bits and 16-bit words,
respectively.
The toolbox generates the required mapping for controller signals into the register
pages. The toolbox can also generate appropriate text or binary files to configure
other controllers to match up with the register page(s) images in the controller. This
section describes the following register networks that provide an interface to Mark
VI controllers:
Ethernet Service Request Transfer Protocol (SRTP)
Serial/Ethernet Modbus
A-B Data Highway Plus (DH+)
Ethernet Modbus (Legacy)
Custom Register Network
Ethernet SRTP
The controller communicates with the CIMPLICITY HMI through SRTP. The SRTP
driver responds to the protocols' commands to read and write register pages.
To insert an Ethernet SRTP
1. Click the item Hardware and I/O Definitions.
Select
Ethernet
SRTP and
click OK.
The SRTP
Interface
Settings
dialog box
displays.
SRTP Network Settings
Enter a Network Name

(the default is MMI1).
The name must begin
with a letter and can be
up to five characters
long.
Enter the file to which
the configuration will be
exported.
Enter a description of
the interface.
Click OK. The interface
is inserted in the
Outline View .
Right-mouse click on <name> Ethernet SRTP

Interface. Select Insert First from pop-up
menu. Pg1 is inserted.
To insert points, right-mouse click on Pg1 and

select Insert First. The Point Settings dialog
box displays (refer to the next section).
Tip To modify pages, refer to the following section, Modify Page Settings at the
end of this chapter.
Point Settings
Enter the name of the signal

associated with this point. This
must be provided to create a
point.
Browse... allows you to select
the signal using the Signal
dialog box.
Address is assigned by the
toolbox to a point that is
Byte.BIT.
Select the Data Type from a
drop-down list of data types.
These types are different from
the controller data types.
Enter Write for the controller

to produce information or
Read to receive information.
CIMPLICITY Resource allows

you to mark this particular
signal to be moved into the
database using the SDB
Exchange.
Lock toggles the point between Click here to allow Edit Signal displays
lock unlock (meaning that the word the signal to be the Signal Edit dialog
offset and bit number are set when scaled for non-bit box. The button is only
locked and will not changed until data types. active when the point is
unlocked). Also, Lock All Signals being inserted.
and Unlock All Signals command
buttons are in the Internal Settings
dialog box.
The following screen is an example of the Ethernet SRTP Interface.
Serial/Ethernet Modbus
Serial/Ethernet Modbus interface provides communication between the Mark VI
controller and other non-GE controllers using the Serial RS-232C connection,
RS-485 is used for multiple
Ethernet or both. Communication with the remote controller is implemented using
controllers.
register pages. The register maps may be independent or shared (overlapping).
To insert a Serial Modbus
Note The Mark VI is always a Modbus slave unless it is using the VSCA.
Select Serial/Ethernet
Modbus and click OK.
Serial Modbus Settings
Baud Rate, Parity, Data Bits , and Stop
Bits define the communication settings for
Enter the communication the network and must be set to match all
Mode for the network. The other controllers on the network (check this
default mode is Binary. dialog box on other controllers).
Identifies the Serial Modbus

network in the controller.
Enter up to five characters.
Enter the communication

Port used to talk to the
external controller (COM1 is
not available).
Enter the network address
of the controller. It must be
a unique number between 1
and 255.
Select the desired
physical Modbus
interface. Shared pages
can receive commands
from either the Serial or
Ethernet interfaces.
Input Enable Signal:

Inputs to this controller can
be enabled and disabled
programatically by
specifying a Boolean signal
here and manipulating it
with blockware. Enter a note to describe this This option is only available in
modbus interface. Expert Mode and at Privilege Level
4. It limits the number of
commands processed per second.
<name> Serial Modbus
Interface. Select Insert
First.
Pg1 is inserted.
To insert points, right-mouse

click on Pg1 and select
Insert First.
Note To modify pages and points, refer to the sections, Modify Page Settings and
Modify Point Settings at the end of this chapter.
Allen-Bradley Data Highway Plus (DH+)
DH+ functions over a serial connection to remote controllers. Communication with
remote controllers is implemented using register pages.
To insert a DH+ interface
Or click the right-mouse 2. From the Edit menu, select Insert First. The New I/O and Network
Select A-B Data Highway

Plus (DH+) and click OK.
The DH+ Interface dialog box
displays. Enter the correct
settings as described in the
next section.
DH+ Settings
The named DH+ Interface is inserted.
Right-mouse click
A-B Data Highway
Plus Interface. Select Insert
First.
Pg1 is inserted.

click on Pg1 and select
Insert First.
Note To modify the pages and points, refer to the sections Modify Page Settings and
Ethernet Modbus Settings
Enter the Network Name

using up to five characters.
The name must begin with
a letter of the alphabet.
Enter a Note to describe

the interface.
Click OK. The <name>

Ethernet Modbus Interface
is inserted.
Ethernet Modbus
Interface. Select Insert
First.
.
Pg1 is inserted.
To insert points, right-

mouse click Pg1 and
.
Note To modify the pages and points, refer to the sections Modify Page Settings and
Custom Register Network
Custom Register Network provides specialized application-specific register network-
based communications. They are predefined by GE product developers and used in
specific or unique applications.
To insert a Custom Register Network
Select Custom Register

Network and click OK.
The Configurable Register

Network dialog box displays.
Right-mouse click
Register Network.
Select Insert First.
Pg1 is inserted.

click Pg1 and select
Insert First.
Tip To modify pages, refer to the section, Modify Page Settings at the end of this
chapter.
Modify Page Settings

To modify a page
Double-click the page name to display the Page Settings dialog box.
Enter the page name

using up to five
characters.
Enter the page length

for the defined
address.
First Address cannot
be outside of
available memory.
Select the register type

used for this page.
Sort the list of pages

by name or by
address.
Toggle the page

options on and off,
as desired. Page
version and heartbeat
functionality requires
client support and is
generally not
applicable.
% Allocated is the
percentage of page
memory that is
allocated.
% Free is the Click to keep the Click to unlock all signals and Click to reclaim all
percentage of page memory location of allow the memory location of lost memory.
memory remaining. points with signals points that have signals to
% Lost is the amount on the page. change.
of memory lost
by deleting signals in
the page and not
compressing.
Modify Point Settings
Register pages consist of individual register points (much like Status_S pages).
To modify a point
Double-click the point to display the Point Settings dialog box.
Enter the page name

or select Browse...
Enter the number of

the register that the
signal is connected to.
Enter the Data Type

the register. This field
of
is only enabled for
word-type register
pages. Bit-type pages
must be a bit-by-
definition. The four
data types supported
are Bit, Short, Long
and Float. (Long
integer and Float point Click to restrict the Click to allow the Click to edit the signal
are double word-type signal address. The signal to be scaled for connected to the point.
and occupy two point cannot be non-bit data types.
registers on the page.) moved if you perform
a page compress.
Notes
Chapter 10 Configuring the Network
Interface
Introduction
A Level II pc is a pc-based This chapter provides instructions for using the toolbox to configure the Network
controller that performs Interface. The Network Interface is used to configure general-type controllers, such
high-level functions, such as as Level II computers (Alpha or Intel 386), or non-GE controllers for interface
tracking, models, and recipes signals that are used on a project. The interface configuration also allows you to
(setup data). It can connect to store signal ownership and usage in the System Database (SDB). For pcs that
another computer to obtain connect to DLAN+, the interface produces a signal definition text file (.cfg) to
process data. resolve signals during runtime, and routing table text files (.rte) used by the interface
drivers to make up the DLAN+ command messages. For pcs that connect to an
Ethernet Global Data (EGD) network, the interface produces an EGD initialization
file, based on data from the SDB for use by the ICN Service.
Once the Network Interface configuration is defined, the data is put into the SDB.
This makes the signal information available to other controllers and drives.
Section Page
Concepts .................................................................................................................10-2
Configuration..........................................................................................................10-3
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 10 Configuring the Network Interface 10-1
Concepts
The Network Interface is used to configure a device, such as a pc, that communicates
on one of the GE control networks. It normally interfaces with all devices in a
system and can be used to define non-GE controller signal interface for storage in the
SDB.
The Network Interface is similar to a controller, except no code is entered. It is only
used to define the signal interface between the Level II pc and any networks
connected to it, such as DLAN+, Ethernet, and Genius.
Configure the Network Interface using the toolbox as follows:
1. Define the signals owned by the Network Interface
2. Map these signals to the appropriate network
3. Define the signals used by the Network Interface
4. Put signal data into the SDB
5. Get signal data from the SDB
6. Export signal text files (.cfg), routing text files (.rte), and/or EGD initialization
files (ICNSDB.ini), if required
Most applications that run on The .cfg and .rte files may need to be copied onto the actual Network Interface pc.
the Network Interface pc read The interface pc applications read the .cfg files to resolve signals on the appropriate
the signal text file when they networks during runtime. The .rte files are read to determine how to make DLAN+
first start. command messages and forward DLAN+ messages from one network to another.
For the Network Interface pc connected to an EGD network, the initialization file is
always named ICNSDB.ini when Export/Egd Ini is selected. This file is always
written to the windows directory (in most cases, this is C:\WINNT\) and is used by
the ICN service, which is responsible for reading and writing data to and from the
network during runtime. The initialization file contains information as to which
devices are on the network, their addressing, and how much data they own. The ICN
service uses this information to determine whether it should capture data off the
network and what data it needs to send out on the EGD network.
The toolbox Batch Operations utility supports available operations for the Network
Interface. Refer to Chapter 5 for details on Batch Operations.
10-2 Chapter 10 Configuring the Network Interface GEH-6403L Toolbox for a Mark VI Turbine Controller
Configuration
This section provides instructions for using the toolbox to configure the Network
Interface.
Create Network Interface

To create a Network Interface
From the File menu, select New. The New dialog box displays a list of
Or click .
available devices.
Click the
System
Configuration
tab.
Select Network
Interface.
Click OK.
The Network Interface window is created with a temporary name, such as nwdv1.
The Outline View of the window displays items as follows:
Device name
Modify Network Interface Name
To modify the name of a Network Interface
1. From the Outline View, click the interface name to highlight it.
Or double-click the name. 2. From the Edit menu, select Modify. The Modify Device dialog box displays.
Enter a new name

(maximum: five
characters).
Enter a note in the text

box, if desired.
Work with Network Interface Files
The Network Interface is configured using three types of files:
Binary working files (.alb) contain an exact copy of the configuration used by
the toolbox. You will generally work from .alb files.
Tree files (.tre) are text files that contain configuration information.
Project files (.prj) are text files that can group all .tre files that make up an
interface.
Export as .prj and .tre files

To save the Network Interface to a .prj file
1. From the Outline View, highlight the interface name you want to export.
Network Device menu 2. From the File menu, select Export (see menu below).
commands are managed just
3. Select All. The Export Project dialog box displays to confirm the name of the
as other toolbox and
.prj file.
Windows menus (refer to
Chapter 3). 4. Click OK to save the .prj file.
To save part of an interface configuration to a .tre file

1. From the Outline View, highlight the item you want to export.
2. From the File menu, select Export (see menu above).
3. Select Selected. The dialog box that corresponds to the item you selected in
step 1 displays so you can select the name for the .tre file.
4. Click OK to save the .tre file.
Tip For instructions on exporting signal files, routing files, and EGD
initialization files, see the sections, Exporting Signal and Routing Files and
Exporting EGD Initialization Files.
Define Network Connection
To define a network connection
Tip The hardware library must be loaded before the network connection can be
made. From the File menu, select Import and select the mk6_iolib.tre file.
1. From the Outline View, click the item Hardware and I/O Definitions.
Or click the right-mouse 2. From the Edit menu, select Insert First. If the hardware library is not loaded,
button and select Insert First. the following warning dialog displays.
3. Click OK and load the uc_iolib.tre file. Repeat steps 1 and 2.

4. The New I/O or Network Interface dialog box displays.
5. Select the desired network connection and click OK. The network item is
inserted in the Outline View.
Tip For more information on editing different networks, refer to Chapter 9.
Device Dialect
Message class is a number The dialect identifies the type of physical pc or PLC the Network Interface is
included in each DLAN+ configuring. Dialect information is required by other devices, so that the command
command message and used messages sent to this device contain the correct message class. If the message class
by devices as a filter. for a command does not match the message class for the receiving device, the
command is ignored.
The primary use of dialect/message class is when a command is broadcast (or sent to
a group), but is intended only for a specific type of device (such as a drive). The
dialect/message class makes sure only the specific devices of the correct type receive
the command message.
Note When a controller or drive is configured, the device type is already known and
the dialect is preset.
Modify Dialect
To modify a dialect
1. Insert the DLAN+ Interface using the steps in the previous section, Defining a
Network Connection.
Or double-click DLAN+ 2. From the Edit menu, select Modify. The Edit DLAN+ dialog box displays.
Interface.
A default name is assigned when DLAN+ is inserted. In the USDB, the

network name exists in the database and is set by the command Get
From Database. For the SDB, the name is made available to other
controllers with the command Put Into Database(refer to the Sdb
Browser in the View menu).
The ARCNET node

number (1 to 240) for this
controller on this network
(must match the board
DIP switch setting). Enter
the value 0, and the next
available drop number is
assigned when it is put
into the database.
Dialect identifies the type

of physical PC or PLC the
Network Interface is
configuring. Select the
dialect to use from the
drop-down box .
Enter a description of the

network.
Insert/Define Signals
Function names are limited to Network Interface signals are inserted in the toolbox in the Outline View under the
eight characters. item Functions. A function acts as a grouping mechanism for inter-related modules.
To insert a function into a configuration
1. From the Outline View, click the item Functions.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Function Name dialog box
button and select Insert First. displays to name the function. For example, enter the name func1, and click
OK.
Select Functions.
From the Edit
menu, select
Insert First.
The Function Name dialog box

displays to name the function.
Once a function is inserted, signals can be inserted/edited and defined as described in

Chapter 3, Configuring a Mark VI Controller.
Map Signals to a Network

See Chapter 9, Hardware and Once the signals are defined, they must be mapped to the appropriate network and
I/O. page, under the item Hardware and I/O Definitions. This makes the signals available
to other devices on the appropriate networks. The following Outline View has
signals mapped to an Ethernet page and to a DLAN+ page.
Note A Network Interface can map STRING-type signals to the Ethernet (as the
signal file is interpreted by the runtime code). The string lengths are user-defined.
Specify Signals Used by the Network Interface
Refer to the section, Module To specify signals expand the item Functions, and click the item Modules.
Pins.
Click the right-mouse

button on the pin you want
to edit, and select Modify.
The Edit Module Pin dialog box displays. In the Connection text box, enter the
name of the external signal to be connected to the pin, or click Browse for a
defined signal either locally or from the SDB.
The following screen displays where the signals are used.
Note A Network Interface can own scales, which are put in the database. Global
scales can be obtained, making them available to Network Interface-owned signals.
Put Into Database/Get From Database
The command Put Into Database makes all Network Interface signal information
available to other devices. The command Get From Database finds all the signals
in the SDB that the Network is configured to use, but does not own. The get process
creates the necessary pages and point information in the Outline View to connect
the signals on module pins with the actual external signals. The following screen
displays the network points that can result from the command Get From
Database.
The command finds the signals defined as being attached to the module pins for this
Network Interface. Those signals are accessed through DLAN+ and are from the
controller device called UC1 in the page called PG1.
Export Signal and Routing File(s)
An Alpha or NT-based pc Once the Network Interface's signals are defined and the commands Put Into
connected to DLAN+ needs Database and Get From Database are performed, the .cfg and .rte can be
the signal and the routing created, if required by the Network Interface.
tables.
A .cfg file is a signal definition text file, which allows other programs to resolve
signal addressing.
A .rte file is a routing definition text file, which defines to other programs how a
signal is to be routed from one DLAN+ network to another.
An ICNSDB.ini file is the Ethernet Global Data (EGD) initialization text file for the
EGD Integrated Control Network (ICN) service.
To create a .cfg or .rte file
1. From the File menu, select Export.
Exports the interface signal's

configuration file for use by
other programs.
Exports the routing text file

for DLAN+ message routing.
Exports the Ethernet Global

Data (EGD) initialization file
(ICNSDB.ini).
2. Select Signal Data. The Signal Export File dialog box displays. Or, select
Route Data. A text file is produced with routing data for the Network
Interface.
3. Enter the location and file name to save the signal data.
4. Click OK. All interface signal data is written to this file and location.
Export EGD Initialization Files
Once the Network Interface's connection to the proper EGD network is defined (see
the section, Defining a Network Connection) and a Put and Get from the Database is
performed, the EGD initialization file can be exported.
To create a ICNSDB.ini file
1. From the File menu, select Export.
2. Select Egd Ini. A dialog displays to confirm the exporting destination of the
file.
3. Click Yes. The initialization file will be stored in the displayed location.
Profibus Interface
Profibus interfaces can be inserted into the Hardware and I/O Definitions tree to
access the Profibus functionality available on certain hardware forms. Profibus
interfaces have no pages. No cards that precede UCVE use the Profibus interfaces.
To insert a Profibus interface
1. From the Outline View, click on the Hardware and I/O Definitions item to
highlight it.
3. The New I/O or Network Interface dialog box displays. Select Profibus,
then click OK.
To configure a Profibus interface
1. Click to highlight the Profibus interface to be configured.
2. From the Edit menu, select Modify or, click the right-mouse button and select
Modify. The Profibus Interface dialog box displays.
The Network Name is
the interface name
(five characters,
maximum).
Interface is the unique
inteface number,
which will vary with
hardware forms.
Notes should include

a string description of
this DDR (50
characters, maximum).
3. Click OK.
Chapter 11 Signals and the Database
Introduction
This chapter defines signals and their sources. It also defines the topological
information in the database. The database is a collection of signals, scales, and other
topological information, which all devices in a system share for communication.
Devices place information into the database with the command Put Into Database
and obtain information with the command Get From Database. There are two
databases: System and Unified System.
System Database (SDB) is a Windows-based client/server database, which uses .dbf
files for storing data.
Unified System Database (USDB) is an Informix SQL relational client/server
database, which runs on a LynxOs-based PC.
Section Page
Signal Concepts......................................................................................................11-2
SDB ......................................................................................................................11-12
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 11 Signals and the Database 11-1
Signal Concepts
Signals are the placeholders for memory locations in the toolboxs different
platforms. Signals also connect both the pins in blockware and blockware to the
points in hardware. They are created by signal definitions and pins as part of
blockware. Every block, macro, or module that is inserted has a signal associated
with its pins.
For more information, refer Signals exist in the database only when they are mapped (connected) to a network
to the section, SDB. I/O point and the device configuration command, Put Into Database, is used.
When a signal is put into the database, it is made available to other devices to get.
Signals can be created by:
Inserting a signal definition
Sending the Get From Database command
Inserting an item of blockware in a controller
Drive Signals
Signals in the AcDcEx2000 are owned by variables (VARs). The number and types
of signals depend on the type of AcDcEx2000 being configured. The signal tokens
are fixed, since the VARs are created when the device is created and exist as long as
the device exists.
Controller Signals
In the toolbox Outline View, controller signal definitions are inserted under the
item Signal Definitions (under the items Functions or Macro and Module Libraries).
Signal definitions are also placed under the item System Data, under the items
External Signal Definition and Undefined Signal Definition, using the command,
Get From Database. Also, in the item System Data, a list of LINK_OK signals are
placed under the item Network Signal Definitions.
11-2 Chapter 11 Signals and the Database GEH-6403L Toolbox for a Mark VI Turbine Controller
Signal definitions can be
inserted under the items
System Data, Macro and
Module Libraries,
Functions.
Macro Pin vs. Module Pin
A Mark VI Controller signal is defined in a macro pin or module pin before
instancing. The following table provides guidelines on how and when to define a pin.
When to use a macro pin: Guidelines for Macro Definition Pin

For any signal that needs to be accessed outside this Name is limited to seven characters.
macro.
Can attach a 50-character note.
For signals that will help with debugging, especially if it will
When a macro is instanced, the macros pin names are
avoid having to look inside the macro.
combined with the instance number to automatically make
the signal name.
Use a module pin when: Guidelines for Module Definition Pin
Signal is used in more than one task. Name is limited to 12 characters.
Signal is a Status_S or I/O signal (do not use fully qualified Can attach a 50-character note.
signal name, such as R1/R2/R3/name).
Can attach a scale factor to the signal.
One or more tasks in the module need to be event-started
Inserting a module pin makes it obvious which signals are
on the rising edge of this signal.
inputs/outputs.
Signal is not used elsewhere, but needs a custom signal
The pins on blocks and macros in the module definition can
description. (A custom signal description is needed for any
be written to point to this module pin, no matter what region
signal that might end up as a permissive that could be
prefixes were specified when the module was instanced.
diagnosed, such as an input to a BENG or a BENG D
block).
Signal/Pin Connection
Signals are created by signal definitions or for pins as part of blockware. Every
block, macro, or module that is inserted has a signal associated with its pins. When a
signal is created:
A block pin or instanced macro pin is automatically named based on the pin
name and block number. They are referenced from pins on other blocks using
# :pin_name (# is the block number: name of pin). There is no signal description
associated with this signal. This signal can only be used within the same level of
code. If the block is in a macro, it can only be used within that macro and if the
block is in a task, it can only be used within that task.
A module instanced pin or inline module pin are global to the device. They can
be connected to a Status_S variable or an I/O point. The signal name is in the
form R1\R2\R3\module_pin_name, where R1\R2\R3 was specified when the
module was instanced.
A signal definition is also global to the device. It can be connected to a Status_S
variable or an I/O point. The signal name is in the form R1\R2\R3\signal_name.
A scale factor can be attached to the signal.
Pins are connected to other pins or signals to make blockware function in a
prescribed way. A connection is generally indicated in the Outline View by a name
in parentheses following the pin name, such as:
For more information, see Pin connections display in a hierarchy that can be seen in the Finder under the tab
Chapter 4, Finder. Signal/Variable Usage, as shown.
The hierarchy reflects the way pins and signals are connected. Each item in the list
references the item in the level above it. A signal hierarchy, excluding I/O points, is
represented in Pcode by a single address token. This means that only one initial value
or scale is used and the top level is the source of such information.
It is important to recognize the directional nature of connections to obtain the correct
data type. Pins with a collection data type, such as Analog or Simple, must reference
For a list of data types, refer
pins with non-collection data types. Referencing incorrectly causes a validation
to Chapter 2, Using the
error. Correct the error by reversing the direction of the connection or by creating a
Toolbox.
pin and referencing that pin.
Attaching Signals to I/O
I/O points found under the Hardware and I/O Definitions item can be used in
blockware only when they are connected to signals. The Summary View below
displays an example of the connected signal and scale.
The I/O mapper task is a program that transfers inputs to outputs in the controller.
The toolbox creates I/O transfer Pcode records for any signal connected to both input
and output points. Similar records are also created for tasks that have signals with
I/O points connected to block pins.
More than one point can be connected to a signal. These multiple connections direct
the mapper task to move inputs to outputs using I/O transfers, although the signal is
not used in any task. To have more than one input point results in a validation error.
However, it is possible to connect multiple output points to this signal, along with a
single input point.
For more information, see the Scale factors are associated with signals and not points, so that all points connected
sections, Status_S Points and to a particular signal will all use the same scale factor. When the input transfer
Genius Block and Field occurs, the raw counts are converted to engineering units used by the blockware.
Control Module Points. When the output transfer occurs, the engineering units are converted to raw counts.
Note Because the I/O mapper is not synchronized with the scheduling frame, Mark
VI I/O should not be configured for transfer.
Special Signal Properties
Properties of certain signals can be accessed in blockware and used as part of the
normal logic by preceding the name of the pin or signal, as follows:
Precede the inverse of a Boolean signal with a tilde symbol ~.
Precede the health of any signal connected to an I/O point, (Boolean value) with
the number symbol #.
A signals health status indicates whether the associated point is functioning as
intended. The value of the signal health varies depending on the points to which the
signal is connected. The following table shows what information goes into the value
of the health. The health of signals not connected to I/O points is TRUE. Generally,
signals connected to output points are always healthy.
Input I/O Type # Health is

Genius No Genius point or block faults and block present and GENI_ON
Field I/O No point, module, or block faults and block present
Register I/O I/O semaphore, page, and heartbeat healthy for register I/O types depending on
required client functionality
Internal Status_S Input page healthy
External Status_S Input page healthy and signal health as filled out by the I/O mapper task if the
source device signal is connected to both an input and output
Signals connected to Genius points also have an extended health with the
symbols ##. The extended health of a point is a 32-bit mapped value used to extract
more specific health information on a given I/O point. The meaning of the bits differ
according to the I/O type. The table below defines different I/O types.
I/O Type Byte 3 (MSB) Byte 2 Byte 1 Byte 0 (LSB)
GENIUS Bit0 = GENI_ON Bit0 = block present *Block fault code *Circuit fault
code
Field I/O Bit0 = GENI_ON Bit0 = block present *Block fault code *Circuit fault
code
Bits 4-7: module fault code,
reset same as Genius
Register I/O Not used Bit0 = I/O semaphore Bit0 = heartbeat Bit 0 = page
health = 1 health = 1 health = 1
NOVRAM Byte 2 error count Byte 1 error count Byte 0 error Bit 0 = point
count health = 1
* The meaning of the Genius Block and circuit fault codes can be obtained from the Genius I/O System and
Communications, Users Manual, GEK-90486F-1.
Scale Definitions
A scale can be attached to either a signal definition or module pin definition. Any
signal can be mapped to a network page owned by the device. When the command
Put Into Database is used, all the signals and any scales attached are put into the
SDB. The scale is now available to other devices using the command Get From
Database. These scale definitions display under the System Data/External Scale
Definitions items, as shown below:
Signal Selector
The Signal Selector dialog box allows you to select a signal for various toolbox
functions.
To select a signal
1. In the Outline View, select Functions, Signal Definition, then right-click the
signal name and select Modify. The Edit Signal definition dialog box
displays.
2. Click the Browse... button to display the Signal Selector dialog box shown
below.
Double-click on the
region to select
signals from.
A list of available
signals displays.
Double-click to
select the desired
signal.
A description of the
selected signal
displays here.
Select the type of signal to display Select either Local or Network

in the list above, such as All Types Items, when available. The default
or Boolean. is Local.
3. Click the SDB Browse button. The SDB Signal Browser dialog box displays.
In the example above, a specific Network, a Device, and a Data Type are selected
from drop-down menus to display just those selected signals.
Another method of selecting a desired filter region is to click the Browse Region
button. The Select a Region dialog box displays.
4. Click the Attributes button on the SDB Signal Browser
dialog box to define the columns displayed in the list box in the Select Signal
Fields to View dialog box.
The Add All, Add, Remove, and Remove All buttons move signals from the left
list box to the right.
SDB
For more information, refer The SDB is a client/server Windows-based database that uses .dbf files for storing
to GEI-100506. data. Only the device that owns the topology and signal data can put that information
into the SDB. There is no separate import program.
Select the database from the Options menu, Settings option, and Database tab.
The SDB:
Can be created from the toolbox as long as the SDB server is running.
Is specified by a path-qualified sub-directory where the database is stored. The
SDB name must include a drive letter.
I/O points and internal signals that can be put into the database are stored in the
signal table.
Put Into and Get From Database

The command Put Into Database provides information for other devices in the
system. The command Get From Database allows the devices to obtain this
information. All devices put the same information into the database depending on the
configuration (except the System Device). The following data can be put into the
database:
Device information (topology data), such as device name, type, and number.
Network information (topology data), such as the networks connected to the
device, pages associated with each network connection, and drop numbers when
applicable.
Signals owned by the device and mapped to pages owned by the device.
Scales owned by the device, which are attached to signals that get put into the
database.
Put Into Database
The Put Into Database command can be full or incremental. By selecting the Full
option, the old signals of a device are deleted from the database and replaced by the
signals that the device presently owns. This is also true for network connections and
pages owned by a device.
If you select the Incremental option, signals are added that have been created since
the last Put Into Database command. All previous signals are still in the database
(even if they were removed from the device configuration). Incremental is especially
useful for devices that have thousands of signals and it is necessary to add one or two
new signals with out taking the time to re-put everything.
When the command Put Into Database is used, certain fields that have a value of
0 are automatically assigned a new value by the database. The numbers that the
database assigns are used in the device configuration. This includes data such as:
Device number (must start at 256 or database reassigns number)
Drop number (DLAN+)
Page number (DLAN+)
To put information into the database
1. From the Device menu, select Put Into Database. Select Full to include all
information or Incremental for specific information.
The toolbox displays the message box shown below, indicating which server and
database will be used. If any of this information is incorrect, click No to cancel the
operation.
2. Click Yes to continue the command, Put Into Database. The Error Log
View displays the present state and status of the command.
Get From Database
The get process also searches for undefined signals in the database. Then, the
database server returns signal attributes and the signals are assigned owners. The
owners are the external devices on the same network as the device performing the
get. The signal attributes returned by the database are used for building the devices
Pcode. The command, Get From Database also allows the device to obtain the
actual value of the signal from the network interface during runtime.
There are two types of get: full and incremental.
In the Full command, the list of External Signal Definitions under the item
System Data are ignored. After the command is completed, this list is rebuilt,
and the point list for external pages under the item I/O Display Definitions is
rebuilt.
The Incremental command applies only to signals. When getting from the
database, the toolbox creates a list of signals used by the device, but not owned
by the device. Signals in the item External Signal Definition are not bound, but
the new bound signals are added to the item and to the external devices pages.
A warning is issued in the An incremental get can be faster then a full get, especially if a device is using
Error Log View when an thousands of signals. However, the incremental will not receive any updates to
incremental get is performed. external signal data that existed before and may have changed.
To get information from database
1. From the Device menu, select Get From Database. Select Full to include all
information or Incremental for specific information.
One of the following message boxes, displays:
2. Click OK to continue the command. Click Cancel to end process

The signals are displayed under the item External Signal Definitions.
Tip During the command Get From Database, the toolbox creates a list of all
signals that are used and not owned by the device. It then attempts to find them in the
database. The signals that are found are placed under System Data/External Signal
Definitions. They are also shown as points in the devices external page under
Hardware and I/O Definitions.
If signals are not found in the database, a message box displays to create Undefined
Signals Definitions. If undefined signals are created, they are displayed under the
item UnDefined Signal Definitions, as shown below.
Signal found in the database

and not owned by the device
are compiled here
Signal not found in the

database are compiled here
Scale Results
When a scale is associated with a signal, the scale name and information are included
with the signal. Global scale definitions do not change as often as signal usage. So,
after getting topology and signals, a dialog box displays to Get Scales. Click No and
receive a warning that scales were not received and previously defined external
scales were not touched. Click Yes and the item Externally Defined Scales is
replaced with all the scales defined in the database.
Note Get scales returns all the scales in the SDB, including those owned by this
device. However, these scales are ignored by the device since it is the owner.
Global Enumerations
System Configuration can define Enumeration Type definitions, which are global.
When System Configuration performs a Put into Database command, these
enumerations are stored in the SDB. Any device that performs a Get from
Database command will get these global enumerations, along with signals, scales,
and other data. These global enumerations are stored as shown below.
These standard
type definitions
are used for
Status_S.
These five type

definitions are
global.
These global enumerations can be used as data types for signals. It is only necessary
to define the enumeration once to use it in any number of devices.
Chapter 12 Turbine Historian
Configuration
Introduction
Once collected, the data can The Turbine Historian Configuration device is used to generate configuration files,
be accessed either by GE data configure the historical data collection, and implement the configuration for the
analysis applications or by Mark VI, PI-based, Turbine Historian.
PI-ProcessBook.
This device configures the Turbine Historian to collect the following signal data and
distribute over the Unit Data Highway (UDH).
Mark VI, Ethernet Global Data (EGD)
Alarm and Event
Sequence Of Event (SOE)
Hold
Section Page
Working with Files and Menus ..............................................................................12-2

Configuration..........................................................................................................12-4
Templates ...............................................................................................................12-6
Troubleshooting....................................................................................................12-15
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 12 Turbine Historian Configuration 12-1
Working with Files and Menus
The Turbine Historian is configured, using one of three types of configuration files:
For more information, refer Turbine Historian binary (.thb) file is the binary file form of the configuration
to Turbine Historian System created through the Save command. The configuration can also be exported to a
Guide, GEH-6422. projected file.
Project (.prj) file is a text file that holds configuration information.
Menu Commands
Turbine Historian Configuration menus, such as File, Edit, and View, are managed
just as other toolbox and Windows menu commands.
Device Menu
The Device menu contains the following commands:
Validate checks the configuration for errors.

Build is disabled under Build is used to produce the Turbine Historian configuration files and to configure
specific conditions. Refer to the PI database with the points defined in each collection.
the Troubleshooting section.
Put In Database verifies that the device properties are correct and inserts the
device into the database. Configuration and the defined network connections are
inserted into the SDB Device and Topology tables. This data is then used when the
Turbine Historian Configuration creates text files during the Build command.
Get From Database retrieves signal information from the database. Each time that
a signal or set of signals is added to a Collection, you must use this command.
Restart Services may not be Restart Services stops and then starts the HST and ICN Services. This enables
enabled under specific any changes to the configuration.
conditions. Refer to the
Troubleshooting section.
Note A Build requires that F:\config.dat be defined, PI services installed and

running, and the HST service installed.
12-2 Chapter 12 Turbine Historian Configuration GEH-6403L Toolbox for a Mark VI Turbine Controller
Build Command
The Build command:
Produces the unit-specific files alarm.dat, event.dat, hold.dat, soe.dat, and
unit_egd.dat for the HST runtime system
Produces the historian-specific unit files egd_push.u and piconfig.u
Runs the utility program ddbuild2 to create the unit-specific files longname.dat
and unitdata.dat for the HST runtime system
Runs the utility program hstdbs to create the system level egd_push.dat and
piconfig.dif files, and for non-Mark VI units, create the system level
pi_push.dat file
Produces the file enetalm.dat file for the HST runtime alarm subsystem
Produces the EGD icn.ini file
Modifies the HOSTS file
Runs the utility program piconfig to populate the PI database
The following files are generated by the Build for each Mark VI unit defined in
F:\config.dat.
F:\UNITn\ALARM.dat
F:\UNITn\EVENT.dat
F:\UNITn\HOLD.dat
F:\UNITn\LONGNAME.dat
F:\UNITn\SOE.dat
F:\UNITn\UNIT_EGD.dat
F:\UNITn\UNITDATA.dat
F:\UNITn\EGD_PUSH.u
F:\UNITn\PICONFIG.u
The following list of files is generated by the Build for the Turbine Historian site
configuration.
F:\EGD_PUSH.dat
F:\PI_PUSH.dat (if non-Mark VI units are correctly defined)
F:\PICONFIG.dif
F:\ENETALM.dat
%WINDIR%\ICN.ini (merge of SDB data with F:\ICN_EX.ini, if it exists)
%WINDIR%\SYSTEM32\DRIVERS\ETC\HOSTS (intelligent merge of SDB
data and existing HOSTS file)
Configuration
This section defines the four major items for configuring the Turbine Historian.
Create
Templates
Collections
Signals
Create Configuration
To create a configuration
1. From the File menu, select New. The New dialog box displays.
2. Click the System Configuration tab.
Or click .
3. Select Turbine Historian Configuration and click OK.
The Outline View displays the following items:
The Turbine Historian

Configuration is given
the default name, th1.
To modify the name

Or double-click the device 1. From the Outline View, click the device name to highlight it.
name.
2. From the Edit menu, select Modify. The Turbine Historian Device
Properties dialog box displays.
The default Device Name is
th1. Enter the new name
here.
The Plant Data Highway

(PDH) name must match the
Historian's computer
found on the control panel
applet network' identification
tab. The IP address must
match the IP address
assigned to the Historian's
network interface board
connected to the PDH.
Network Name for the PDH
must be unique, since all
Turbine Historian Devices
and all HMI devices
connected to a PDH will
this name to identify that
PDH.
Enter the root location for

PI data archive
Select the Measurement Systemwhose The Unit Data Highway Computer Computer Click OK to
engineering units and conversion data Name(UDH)
must be unique. The UDH IP Addressmust apply changes.
used to store and display the data on match the IP address assigned to the
Turbine Historian. Refer toChapter 7, network interface board connected to the UDH.
Configuring System , to configure UDH Network Namemust match the EGD
multiple
I f tiscales. name that all Mark VIs will use to communicate with
Turbine Historian.
Templates
A Turbine Historian template is a grouping of signals typically based on turbine
type/turbine size. Templates can be imported or created manually.
To import a Template
1. From the Outline View, click Turbine Historian Templates.
2. From the File menu, select Import. The Import File dialog box displays.
3. Highlight the desired template tree file.
4. Click Open. The template file is imported.
To manually create a Template
Or, click an existing template 1. From the Outline View, click Turbine Historian Templates.
to highlight It, then right-click
2. From the Edit menu, select Insert First. The Turbine Historian Template
and select Insert First.
Name dialog box displays.
Enter a unique
template name.
To modify Template properties

Right-click the Template and 1. From the Outline View, under the item Turbine Historian Templates, highlight
select Modify. Or, double- the template.
click the Template.
2. From the Edit menu, select Modify. The Template Properties dialog box
displays.
Enter the Name here.
Enter the folder name to

which the Template will
be exported. If left
blank, the template file
is stored in the folder
where the Turbine
Historian resides.
Enter a Note about

the template.
Click OK to apply
changes.
Collections
A Turbine Historian collection is a group of signals from one unit (turbine
network/controller pair). Collections can be created by instancing templates or
adding points manually.
To create a Collection
1. From the Outline View, click Turbine Historian Collections to highlight
it.
Or right-click an existing
collection and select Insert 2. From the Edit menu, select Insert First. The Turbine Historian Collection
First. Name dialog box displays.
3. Enter a unique name and click OK. This name should be the two-character unit
name assigned to the unit in F:\config.dat.
Enter a unique Collection

name here. The name
should be the two-
character unit name
assigned to the unit in
F:\config.dat.
To instance or remove a Template

Or double-click the 1. From the Outline View, click the collection to highlight it.
collection.
2. From the Edit menu, select Modify. The Collection Properties dialog box
displays.
Or right-click the highlighted 3. Click a template in the Templates Available list to select it.
collection and select Modify. 4. Click Add to add it to the Templates In Collection list. The template now
Multiple templates can be moves from the Templates Available list.
added to a collection. 5. Click OK to add the template signals to the collection.
Note An instanced template must have its wildcard substitution variables, %0, %1,
%9 and ^, defined. To define the wildcard substitution variables, select the
template in the Templates In Collection list, then select the substitution variable in
the Substitutions list, then enter the string value. Click Apply. The %C substitution
is always set to the Collection name and cannot be edited.
Enter a unique collection
name. This name should be
the two-character unit name
assigned to the unit in
F:\CONFIG.DAT.
Enter the name of the folder

where the collection file
will be exported. If left
blank, the collection file is
stored in the folder where
the Turbine Historian Device
file is located.
This displays the list of
templates available to be
added to the collection.
Select a template and click
Add to add the template to
the collection. The
Templates in Collection
box displays a list of the
templates already added.
To remove a template,
highlight the template name
and click Remove.
Enter a note describing the

collection.
To see the substitution symbols for a particular template, highlight the Template name
in the Templates in Collection list. The symbols for that template display in the
Substitutions box. To enter a value for a substitution symbol, highlight the symbol in
the Substitutions list, enter the value, and click Apply.
Note To add a signal to a Collection, refer to the section, Signals.
Signals
Signals can be added to a collection manually by selecting the desired signals from
the available network signals. When a signal is added, default information is put into
the signals fields. When the command Get From Database is performed, some
fields may be overwritten with data from the SDB. The Exception Deviation field
must be updated for each manually entered signal.
Field Name Description Signal Definition vs. SDB Definition

Signal Name EGD signal name Cannot be different from SDB
Description Signal Description Uses SDB
Exception Deviation Change in engineering units that Must enter, not in SDB
triggers writing the signal to the
historian subsystem
Data Collection Determines if point is saved in Default is ENABLED, not in SDB
history
Data Type For example, REAL, BOOL Uses SDB
Units Engineering Units Uses SDB, if this field is blank
Precision Number of decimal places to Uses whichever is greater between the
display signal and SDB definitions
Maximum Data Plot Maximum plot limit, for display Default is 100, not in SDB
purpose only
Minimum Data Plot Minimum plot limit, for display Default is 0, not in SDB
purpose only
Maximum Raw Counts Maximum input value used to Default is 100, not in SDB
convert data to different
engineering units
Minimum Raw Counts Minimum input value used to Default is 0, not in SDB
engineering units
Maximum Engineering Units Maximum target value used to Default is 100, not in SDB.
engineering units
Minimum Engineering Units Minimum target value used to Default is 0, not in SDB
engineering units
Maximum Quality Limit Maximum value, in engineering Default is *, not in SDB
units, over which the quality bit is
set when saved in the database
Minimum Quality Limit Minimum value, in engineering Default is *, not in SDB
units, over which the quality bit is
set when saved in the database
Add Signals From the Outline View
To add a signal to a collection
Or click an existing signal to 1. From the Outline View, click an existing template under Turbine Historian
highlight it and then right- Templates, or click an existing collection under Turbine Historian
click and select Insert First. Collections to highlight it.
2. From the Edit menu, select Insert First. The Turbine Historian Signal
Name dialog box displays.
Append a unique
signal name to %C.
For a collection
signal, append a
unique name to the
<collection name>
or click Browse. . .
to display the SBD
Signal Browser.
.
To add signals using the SDB Signal Browser

When the SDB Signal From the Turbine Historian Signal Name dialog box, click Browse. The
Browser is opened from this SDB Signal Browser dialog box displays.
dialog box, only single-signal
selection is allowed.
Select EGD
network.
Click Query to
display a list of
network signal
that are defined in
the SDB. A list of
signals displays
in the Available
Signals list.
Highlight the
desired
signal(s) and
click Add. The
added signals
display in the
Selected
Signals list.
When finished
selecting, click
OK to apply the
changes.
Add Signals Using the SDB Browser

To add signals using the SDB Browser
1. To start the SDB Browser, click the View menu and select SDB Browser.
The SDB Browser dialog box displays.
2. Select the Signal tab and click Query. The Query Design dialog box
displays.
Fill in the
appropriate
Criteria and
click OK.
The query
searches the
SDB and
displays the
results in the
SDB Browser
dialog box.
3. Highlight the desired signal(s) and press Ctrl+C to copy the signal information
to the paste buffer.
4. From the Outline View, highlight the target template or collection, then press
Ctrl+V to paste the signals into the template or collection.
Modify Signals
To modify Signal properties
Or, right-click the Signal and 1. From the Outline View, highlight the signal.
select Modify. Or, double-
2. From the Edit menu, select Modify. The Edit Turbine Historian Signal
click the Signal.
Definition dialog box displays.
Enter the Signal Name or click

Browse... to display the SDB
Signal Browser where you can
select a signal.
As the Exception Deviation,

enter the minimum number of
scaled units a signal must
change prior to being written to
the Historian subsystem ( see
note below).
Enable or disable Data

Collection to save this signal to
the Historian subsystem.
Display Settings:
The engineering Units depend
on the Measurement System
selected in the Device
Properties and the
corresponding value in the Mark
VI signal scale. Refer to Chapter
7, Configuring System
Information, to configure scales.
Precision is the number of
decimal places defined by the
Mark VI signal scale.
Conversion Settings:
The Conversion Settings
values are used for converting
the controller data from its
native format to a new format in
the Turbine Historian. Values The Quality Limits values, The maximum and minimum Data
are determined by the Mark VI in engineering units, are Plotting limits are defined by the
signal scale conversion settings over or under which the maximum and minimum conversion
and the Measurement System questionable bit is set. settings of the scales unless the Mark
selected for this device. These are typically set to ^, VI signal plotting limits are enabled.
allowing all data to be saved Refer to Chapter 3, Basic
Enter a signal Note. without setting the Configuration, to enable and set
questionable bit. the signal plotting limits.
Note The Exception Deviation field will be disabled, and will use the Mark VI's
signal deadband, if it is enabled. Leave the field blank to use 0.5% of the scaled data
plotting limits.
To edit multiple signals
1. From the Outline View, highlight a signal, then press and hold the ---Ctrl or
Shift key to highlight multiple signals.
2. From the Edit menu, select Modify. The Edit Turbine Historian Signal
Definition dialog box displays with the Signal Name field disabled
3. Use the mouse to select or press the Tab key to move to the fields to modify.
4. Enter changes and click OK. The following dialog box displays.
5. Select Yes to update all fields.

Select No to return to the Edit Turbine Historian Signal Definition without
making any changes. All selected signals will match this configuration.
Troubleshooting
When troubleshooting or The commands Build and Restart Services are disabled.
reporting errors, refer to the
Verify that the following PI Services are running:
Error Number in the error
message. This number relates Network Manager
specific information regarding
the nature of the encountered Update Manager
problem. Archive Subsystem
Snapshot Subsystem
Base Subsystem
Verify that the following files exist in the specified drives and directories:
F:\config.dat
G:\exec\hst.exe
The commands Put In Database and Get From Database are disabled.
Verify that the SDB is defined correctly (refer to the Options menu, Settings, and
Database tab).
Notes
Chapter 13 Setup for Turbine HMI
Configuration
Introduction
TCI is part of the Turbine This chapter provides instructions for using the toolbox to configure the Turbine
runtime system, which HMI. The Turbine HMI configuration is used to import data into CIMPLICITY HMI
integrates the Mark VI and to generate a number of text files used by the Turbine Control Interface (TCI)
controller, CIMPLICITY system. Most of the information for the Turbine HMI configuration is obtained from
HMI, and PI or Historian the System Database (SDB).
systems
Section Page
Concepts .................................................................................................................13-2
Working With Files and Menus..............................................................................13-3
Configuration..........................................................................................................13-6
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 13 Setup for Turbine HMI Configuration 13-1
Concepts
The HMI configuration requires some setup tasks for the Build command to load the
CIMPLICITY system with signals from the SDB, and to automatically produce the
text files required by the TCI. The HMI configuration:
Creates and defines configuration properties
Specifies the network connection
Specifies the EGD exchanges it uses
Puts data into the SDB
Gets signal data from the SDB
Validates and saves the configuration file
Uses the Build command to automatically perform the following:
Import signals and other data into the CIMPLICITY system
Produce the EGD icn.ini file
Produce the turbine Alarm.dat, Hold.dat, Event.data, Soe.dat, and
unit_EGD.dat text files for the TCI runtime system
Produce the turbine Enet_alm.dat file for the TCI runtime alarm
subsystem
Modify the HOSTS file, if required
Modify the CIMPLICITY CimHost.txt file, if required
Run the utility program ddbuild2 that produces intermediate files for the
TCI subsystem
13-2 Chapter 13 Setup for Turbine HMI Configuration GEH-6403L Toolbox for a Mark VI Turbine Controller
Working With Files and Menus
The HMI configuration uses three types of files:
Binary working files (.hmb) contain an exact copy of the configuration used by
the toolbox. Users generally work from .hmb files.
Project files (.prj) are text files that can group all .tre files in a configuration.
Export as .prj and .tre files

To save the HMI Configuration to a .prj file
1. From the Outline View, highlight the interface name you want to export.
HMI Configuration menu 2. From the File menu, select Export (see menu below).
commands are managed just
3. Select All. The Export Project dialog box displays to confirm the name of the
as other toolbox and
.prj file.
Windows menus (refer to
Chapter 3). 4. Click OK to save the .prj file.
To save part of an HMI Configuration to a .tre file

1. From the Outline View, highlight the item you want to export.
2. From the File menu, select Export (see menu above).
3. Select Selected. The Export dialog box displays to select the name for the .tre
file.
4. Specify a file name or use the default, then click OK to save the .tre file.
To put HMI configuration data into the SDB
1. From the Device menu, select Put to Database.
2. When the message box displays, click Yes.
The HMI configuration and the defined network connections are inserted into the
SDB device and topology tables. This data is then used when the HMI configuration
creates text files during the Build command.
To get signal data from the SDB
1. From the Device menu, select Get from Database.
2. Click Yes on the toolbox message box.
The Get From Database gets all signals defined in the SDB for exchanges defined
in the HMI configuration. The signals are placed in the .tre file under each exchange.
To validate and build the HMI Configuration
1. Select the HMI configuration name at the top level of the Outline View.
2. From the Device menu, select Validate. A Validation complete message
displays in the status window.
3. From the Device menu, select Build.
When the following message box displays, click Yes.
Signal Attributes
Setpoint limits can be defined for a signal in the toolbox. Setpoint limits
are not attributes of a scale. Enter the limits in the Native Measurement
System for the signal (if the signals native measurement system is U.S. and
has units of inches, setpoint limits may be setpoint low limit = 1 inch and
setpoint high limit = 10 inches).
Display limits are initialized by the scale associated with the signal. The
display limits are fixed by the minimum and maximum engineering values
for the selected native measurement system of the scale. If the scales
selected native measurement system is U.S. and has units of inches, and the
minimum value is one inch and the maximum value is 10 inches, the
display low limit will be one inch and display high limit will be 10 inches.
However, it is possible to define display limits for a signal, independent of
the scale. If this is done, the display limits for the signal overrides those for
the scale. Just as for the setpoint limits, the signals display limits are defined
in the signals selected native measurement system. If the signal's display
limits are defined, these will be used for importing a point's display limits.
If the signals display limits are not defined, the display limits from the
scale are used to define the CIMPLICITY point display limits.
Alarm class. If a signal is defined with an Alarm attribute, you may
assign an Alarm Class to the signal (alarm classes are defined in the system
information file of the toolbox. Controllers have a list of defined alarm
classes available after performing a get from the SDB). The signals alarm
class is imported into the CIMPLICITY system as an attribute of the point.
CIMPLICITY screen name. If a signal is defined with an Alarm attribute,
you may assign the name of a CIMPLICITY screen file as an attribute of
the signal. The signals CIMPLICITY screen is imported into the
CIMPLICITY system as an attribute of the point. When an alarm is
generated in CIMPLICTY from the signal, you may then easily access the
defined screen from the CIMPLICITY alarm screen.
CIMPLICITY enumerations. CIMPLICITY enumerations show up in the
work inch under Points/Point Enumerations in the left-hand tree view. If an
SDB signal has an enumeration associated with it, the enumerations name is
included in the CIMPLICITY point attribute. The enumeration itself will
have been imported during the build before signals are imported.
Configuration
This section provides instructions for using the toolbox to setup and configure the
HMI.
To create a Turbine HMI configuration
1. From the File menu, select New. When the New window displays, click the
System Configuration tab.
2. Select Turbine HMI Configuration. Click OK.
The HMI Configuration window is created with a temporary name, such as hmi1.
The Outline View of the window displays the following items:
Configuration name
Modify HMI Configuration Properties
To modify HMI configuration properties
1. From the Outline View, click the interface name to highlight it.
2. From the Edit menu, select Modify. The HMI Configuration Properties
Enter a Network Name for the PDH
or select from the drop-down list.
Enter the Configuration

Name.
Enter the name and

address information for
the Plant Data Highway
(PDH).
Enter the name and

address for the Unit Data
Highway (UDH).
Enter the location and

name
. of the HMI
CIMPLICITY Project File.
Select either Language 1

or 2 to specify which
language will be used for
descriptions when
importing signals into the
CIMPLICITY HMI system.
The language names are
derived from the System
Information (see chapter
7), which puts the names
in the SDB.
Define a Network Connection
Or right-click and select 1. From the Outline View, click the item Hardware and I/O Definitions.
Insert First.
3. The Enter or Select a Network dialog box displays.
4. Enter the network name or select a network from the drop-down list.
5. Click OK. The network item is inserted in the Outline View.
EGD
Network
Interface
Edit EGD Network
To modify a network connection
1. Click the network name to highlight it.
Or right-click the Network
2. From the Edit menu, select Modify. The Edit EGD Interface dialog box
name and select modify.
displays.
Network Name
Network Number is assigned

by the SDB when the command
Put in Database is performed.
Producer ID is usually the

name of the computer on the
UDH
Source is the name and

location of the exported .tre file.
If the network has not been
exported, this field will be blank.
Insert EGD Exchanges

Any number of EGD exchanges are inserted in the toolbox in the Outline View
under the EGD network. The exchanges should contain the signals needed by the
CIMPLICITY HMI system. Once the exchanges are inserted, use the command Get
from Database to make the signals for each defined exchange available for import
into the CIMPLICITY HMI.
To insert one or more Exchanges into a configuration
1. From the Outline View, click the desired network.
Or click the right- mouse 2. From the Edit menu, select Insert First. The Select EGD Exchange(s)
Once the Exchanges are 3. Either type the name of the exchange directly in the exchange text box, or click
inserted, signals can be one or more of the exchanges in the list. The format for the exchange is <device
inserted using the command name:exchange name>.
Get From Database.
4. Click OK. The Outline View displays all the selected exchanges.
After the Get from Database command is performed, the signals associated with
each exchange are inserted into the tree view, as shown below.
Signals
All signals for each exchange defined in the HMI configuration are imported into the
CIMPLICITY point database when a build is performed. A number of automatic
actions take place during this step of the build.
If the required devices and resources have not been defined in CIMPLICITY
yet, this step of the build creates them in the CIMPLICITY system. The defined
measurement systems (typically US and metric) are inserted or updated in the
CIMPLICITY system.
If there is a scale associated with the SDB signal, a CIMPLICITY measurement
unit is created and identified by the SDB scale name. If dual scaling has been
defined, these are used to create the required measurement units and the
associations required for switching between measurement systems in the
CIMPLICITY system. If the signal is a float (or real) and the precision has been
defined, this data defines the CIMPLICITY precision. If it is not defined in the
SDB, a default precision of 2 is used.
If there is an enumeration associated with the SDB signal, the enumeration name
is included as an attribute of the CIMPLICITY point.
All signals imported into CIMPLICITY use the ICN DevCom and the
Unsolicited and On Change update mode.
If the signal being imported has the scale enabled, the build defines the forward
and reverse scale equations for the equivalent CIMPLICITY point. A signals
scale is enabled or disabled by the device that owns the signal.
CIMPLICITY can own signals on EGD. For these signals, CIMPLICITY writes
the values with the EGD exchanges being broadcast on the exchanges periodic
rate. The signals must be defined by a Network Interface device, in order to
accomplish this (which essentially represents the CIMPLICITY system). The
producer IP and the IP address for the Network Interface must match the IP of
the box on which the CIMPLICITY server is located, which is also the IP of the
HMI Device. The Network Interface is Put to the SDB. When the HMI
Device is configured to use the exchanges from the Network interface and a
Get from database is performed, the signals will be configured as Read/Write.
This is the direction the signals will have when imported into CIMPLICITY,
giving it the ability to write the values.
Note Refer to the section, EGD Point Settings, for details on how to enable/disable
scaling for an EGD signal.
Notes
Chapter 14 Configuring the COI
Introduction
This chapter provides instructions for using the toolbox to set up and run the Control
Operator Interface (COI) configuration. The COI configuration generates and
downloads configuration files used by the Control Operator Interface system. Most
of the information for the COI configuration is obtained from the System Database
(SDB).
Section Page
Concepts .................................................................................................................14-2
Working With Files and Menus..............................................................................14-3
Configuration..........................................................................................................14-6
GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 14 Configuring the COI 14-1
Concepts
The COI configuration requires the following setup procedures and toolbox device
commands.
1. Create and define configuration properties
2. Specify the EGD network
3. Specify the EGD exchanges it uses
4. Put data into the SDB
5. Get signal data from the SDB
6. Insert Graphics Window file names to be downloaded
7. Validate and save the configuration file
8. Build the configuration files required to communicate with the controller and
run Graphics Window
Note The Download command stops the Graphics Window, sends the COI a copy
of the configuration files, then automatically reboots the COI.
14-2 Chapter 14 Configuring the COI GEH-6403L Toolbox for a Mark VI Turbine Controller
Working With Files and Menus
The COI Configuration uses three types of files:
Binary working files (.oib) contain an exact copy of the configuration used by
the toolbox. Users generally work from .oib files.
Project files (.prj) group all .tre files into one configuration.
Export Files
The export command saves the configuration files to a .tre or .prj file.
Select Selected
to save to a .tre
file.
Select All to
save each item
as a .tre file and
create a .prj file.
Note For more information, refer to Chapter 3 and the section, Working with Files
and Menus.
The Device menu allows you to put and get data from the SDB, as well as to
validate, build, and download.
To put COI configuration data into the SDB
1. From the Device menu, select Put Into Database.
2. When this message displays, click Yes.
The COI configuration and the defined network connections are inserted into the
SDB device and topology tables. This data is used when the COI configuration
creates text files during the Build command.
To get signal data from the SDB
1. From the Device menu, select Get From Database.
2. When this message displays, click Yes.
All signals defined in the SDB for exchanges in the COI configuration are placed in
the Outline View under each exchange.
To validate and build the COI configuration
1. Select the COI name at the top level of the Outline View.
2. From the Device menu, select Validate. A Validation complete message
displays in the status window.
3. From the Device menu, select Build.
When the following message box displays, click Yes.
The Build command creates the configuration required by the COI to communicate
with the controller and to run the Graphics Window.
To download the COI configuration
1. From the Device menu, select Download.
2. When the following message box displays, click Yes.
The Download command stops the Graphics window, sends the COI a copy of the
configuration files, then automatically reboots the COI.
Configuration
This section provides procedures for using the toolbox to setup and configure the
COI.
To create a COI configuration
From the File menu, select New. The New dialog box displays a list of
Or click .
available devices.
The COI Configuration window is created with a temporary name, such as coi1.
The Outline View of the window displays the following items:
Device name
Modify COI Configuration Properties
To modify COI configuration properties
1. From the Outline View, click the device name to highlight it.
2. From the Edit menu, select Modify. The Control Operator Interface
Configuration Properties dialog box displays.
Enter the device

name (maximum:
five characters).
Enter the name and

address for the COI
on the Unit Data
Highway
Define Network Connection
1. From the Outline View, click the item Hardware and I/O Definitions.
Or right-click and select 2. From the Edit menu, select Insert First.
Insert First.
3. The Enter or Select a Network dialog box displays.
4. Enter the name of the network in the text box or select from the drop-down list
of available EGD networks in the SDB.
5. Click OK.
The network item

is inserted in the
Outline View
Edit EGD Network

1. From the Outline View, click the network name to hightlight it.
Or right-click the Network
2. From the Edit menu, select Modify. The Edit EGD Interface dialog box
name and select modify.
displays.
Network Name
Network Number
is assigned by the
SDB.
ProducerID is
either the computer
name or IP address
for the COI.
Source is the name
and location of the
exported tree file. If
the network has not
been exported, this
field will be blank.
Insert/Define EGD Exchanges
EGD exchanges are inserted in the toolbox from the Outline View under the item,
EGD Network. Any number of exchanges can be inserted. The exchanges inserted
must contain the signals needed by the Graphics Window screens that will reside on
the COI. Once the exchanges are inserted, use the Get from Database command
to populate each exchange with its defined signals. During the Build, these
exchanges are exported to the coi_egd .tre file, which is used by the Graphics
Window screens.
To insert one or more Exchanges into a configuration
1. From the Outline View, click the desired network.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Select EGD Exchange(s)
3. Enter the name of the exchange or select one or more exchanges from the list.
Once the exchanges are inserted, signals can be inserted using the command Get
From Database.
Note The format for the exchange is <device name:exchange name>.
4. Click OK. The exchange displays in the Outline View as follows:
Graphics Window Files
Graphics Window files (.grw) and any related meta files (.wmf) or (.emf) are
inserted in the toolbox in the Outline View under the item, Graphics Window
Files. Insert all Graphics Window files to download to the COI.
To insert a file into a configuration
1. From the Outline View, click Graphics Window Files to highlight it.
Or click the right-mouse 2. From the Edit menu, select Insert First. The Graphics Window File Name
Enter a unique file name,

or click Browse... to
display the Graphics
Window File Locator.
Select a Graphics Window
file from the Graphics
Window File Locator
dialog box.
If the file extension is not

entered, .grw is used.
Note One of the Graphics Window files must be selected as the default Graphics
Window screen for the COI. The default screen is the first screen displayed on the
COI after a reboot.
Highlight the
file to insert
and click
Open.
This file is
inserted in the
Outline View.
To edit a Graphics Window file

1. From the Outline View, select the Graphics Window file to edit.
2. From the Edit menu, select Edit Graphics Window. The Graphics Window
editor displays the file.
Note Only files with the .grw extension can be edited.
Glossary of Terms
AcDcEx2000
Refers to the dc drives (DC2000), ac drives (AC2000), and exciters (EX2000), which
are all referenced in the combined device type name. These three devices can use the
same application control boards and devices in the toolbox.
application code
Software that controls specific machines or processes.
ARCNET
Attached Resource Computer Network. A LAN communications protocol developed
by Datapoint Corporation. The physical (coax and chip) and datalink (token ring and
board interface) layer of a 2.5 MHz communication network which serves as the
basis for DLAN+. See DLAN+.
ASCII
American Standard Code for Information Interchange. An 8-bit code used for data.
attributes
Information, such as location, visibility, and type of data that sets something apart
from others. In signals, an attribute can be a field within a record.
automatically named signals

Signals that are created as a result of inserting some instruction block(s) other than a
Signal Definition. One or more regions of such signals is of the form }00123.
baud
A unit of data transmission. Baud rate is the number of bits per second transmitted.
BIOS
Basic input/output system. Performs the boot-up, which includes hardware self-tests
and the file system loader. The BIOS is stored in EEPROM and is not loaded from
the toolbox.
bit
Binary Digit. The smallest unit of memory used to store only one piece of
information with two states, such as One/Zero or On/Off. Data requiring more than
two states, such as numerical values 000 to 999, requires multiple bits (see Word).
GEH-6403L Toolbox for a Mark VI Turbine Controller Glossary of Terms i

block
Instruction blocks contain basic control functions, which are connected together
during configuration to form the required machine or process control. Blocks can
perform math computations, sequencing, or continuous control. The toolbox receives
a description of the blocks from the block libraries.
board
Printed wiring board.
Boolean
Digital statement that expresses a condition that is either True or False. In the
toolbox, it is a data type for logical signals.
bus
An electrical path for transmitting and receiving data.
bumpless
No disrupt to the control when downloading.
byte
A group of eight binary digits (bits) operated on a single unit.
CMOS
Complementary metal-oxide semiconductor.
collection
A group of signals found on the same network. The Trend Recorder can be
configured by adding collections.
COM port
Serial controller communication ports (two). COM1 is reserved for diagnostic
information and the Serial Loader. COM2 is used for I/O communication.
configure
To select specific options, either by setting the location of hardware jumpers or
loading software parameters into memory.
Control Constant
Control Constant is a signal with an initial value that is read and never written.
datagrams
Messages sent from the controller to I/O blocks over the Genius network.
dead band
A range of values in which the incoming signal can be altered without changing the
outgoing response.
device
A configurable component of a process control system.
ii Glossary of Terms GEH-6403L Toolbox for a Mark VI Turbine Controller

DLAN+
GE Industrial System's LAN protocol, using an ARCNET controller chip with
modified ARCNET drivers. A communications link between exciters, drives, and
controllers, featuring a maximum of 255 drops with transmissions at 2.5 MBs.
gateway
A device that connects two dissimilar LANs or connects a LAN to a wide-area
network (WAN), PC, or a mainframe. A gateway can perform protocol and
bandwidth conversion.
download gateway
A controller that communicates to Ethernet and DLAN+, running the special
software that can download an OC2000.
Ethernet
LAN with a 10/100 MB baud collision avoidance/collision detection system used to
link one or more computers together. Basis for TCP/IP and I/O services layers that
conforms to the IEEE 802.3 standard, developed by Xerox, Digital, and Intel.
event
A property of Status_S signals that causes a task to execute when the value of the
signal changes.
fault code
A message from the controller to the HMI indicating a controller warning or failure.
Finder
A subsystem of the toolbox for searching and determining the usage of a particular
item in a configuration.
firmware
The set of executable software that is stored in memory chips that hold their content
without electrical power, such as EEPROM.
flash
A non-volatile programmable memory device.
font
One complete collection of letters, punctuation marks, numbers, and special
characters with a consistent and identifiable typeface, weight, posture, and size.
forcing
Setting a live signal to a particular value, regardless of the value blockware or I/O is
writing to that signal.
function
The highest level of the blockware hierarchy and the entity that corresponds to a
single .tre file.
Get From Database

The act of retrieving configuration information from some system database.
Genius bus
GE Fanucs distributed network of intelligent I/O blocks.

Genius global data
Data that is automatically and repeatedly broadcast by a bus controller. All other bus
controllers on the same bus are capable of receiving the data, although some bus
controllers can choose not to. The controller can broadcast global data and receive
global data from certain devices, such as the Series 90-70 PLC and other controllers.
Graphic Window
A subsystem of the toolbox for viewing and setting the value of live signals.
Groups. See Resources.
health
A term that defines whether a signal is functioning as expected.
heartbeat
A signal emitted at regular intervals by software to demonstrate that it is still active.
hexadecimal (hex)
Base 16 numbering system using the digits 0-9 and letters A-F to represent the
decimal numbers 0-15. Two hex digits represent 1 byte.
initialize
To set values (addresses, counters, registers, and such) to a beginning value prior to
the rest of processing.
I/O
Input/output interfaces that allow the flow of data into and out of a device.
I/O drivers
Interface the controller with input/output devices, such as sensors, solenoid valves,
and drives, using a choice of communication networks.
I/O mapping
Method for moving I/O points from one network type to another without needing an
interposing application task.
insert
Adding an item either below or next to another item in a configuration, as it is
viewed in the hierarchy of the Outline View of the toolbox.
instance
Update an item with a new definition.
item
A line of the hierarchy of the Outline View of the toolbox, which can be inserted,
configured, and edited (such as Function or System Data).
logical
A statement of a true sense, such as a Boolean.
macro
A group of instruction blocks (and other macros) used to perform part of an
application program. Macros can be saved and reused.

model
Interactive setup data (recipe) that automatically adjusts to the process. This function
is usually used with hot mills or cold mills.
module
A collection of tasks that have a defined scheduling period.
mGENI controller board

IC660ELB912_. An optional board for the controller that provides an interface to the
Genius I/O bus.
non-volatile
The memory specially designed to store information even when the power is off.
online
Online mode provides full CPU communications, allowing data to be both read and
written. It is the state of the toolbox when it is communicating with the system for
which it holds the configuration. Also, a download mode where the device is not
stopped and then restarted.
pcode
A binary set of records created by the toolbox, which contain the controller
application configuration code for a device. Pcode is stored in RAM and Flash
memory.
period
The time between execution scans for a Module or Task. Also a property of a
Module that is the base period of all of the Tasks in the Module.
period multiplier
A property of a Task that permits the Tasks execution rate to be a multiple of its
Modules period.
physical
Refers to devices at the electronic or machine level in contrast with logical. Logical
implies a higher view than the physical. Users relate to data logically by data element
name; however, the actual fields of data are physically located in sectors on a disk.
pin
Block, macro, or module parameter that creates a signal used to make
interconnections.
PLC
Programmable Logic Controller. Designed for discrete (logic) control of machinery.
It also computes math (analog) function and performs regulatory control.
product code (runtime)

Software stored in the controllers Flash memory that interrupts the application
configuration and performs the requested activities. This includes code such as I/O
drivers and control block libraries.
put into database

Command in the Device menu used to add configuration information into a system
database.

realtime
Immediate response. It refers to process control and embedded systems, and fast
transaction processing systems that must respond instantly to changing conditions.
reboot
To restart the controller.
recipe
Information for process line or paper mill that provides setup data, such as speed,
length, and tension.
register page
A form of shared memory that is updated over a network. Register pages can be
created and instanced in the controller and posted to the SDB.
relay ladder diagram (RLD)

A ladder diagram has a symbolic power source. Power is considered to flow from the
left rail through a contact to the coil connected to the right.
Resources
Also known as groups. Resources are systems (devices, machines, or work stations
where work is performed) or areas where several tasks are carried out. Resource
configuration plays an important role in the CIMPLICITY system by routing alarms
to specific users and filtering the data users receive.
runtime
See product code.
runtime errors
controller problems indicated on the front panel by coded flashing LEDS and also in
the Log View of the toolbox.
sample set
Set of values taken when signals are being trended together with the Trend Recorder.
sampling rate
The period that values are collected to put in a sample set.
Serial Loader
Connects the controller to the toolbox PC using the RS-232C COM ports. The Serial
Loader initializes the controller flash file system and sets its TCP/IP address to allow
it to communicate with the toolbox over Ethernet.
service
Functionality derived from a particular software program. For example, the Recorder
Service transmits and provides conversion of data in the SDB.
signal
The basic unit for variable information. Signals are the placeholders for memory
locations in the toolboxs different platforms.
simulation
Running a system without all of the configured I/O devices by modeling the behavior
of those devices in software.

skew
A property of modules that allows a module to execute at a different time slice than
other modules with the same period.
skew offset
A property of tasks that allows a task to execute at a different time slice than other
tasks within the same module.
Status_S
GE proprietary communications protocol that provides a way of commanding and
presenting the necessary control, configuration, and feedback data for a device. The
protocol over DLAN+ is Status_S. It can send directed, group, or broadcast
messages.
Status_S pages
Devices share data through Status_S pages. They make the addresses of the points on
the pages known to other devices through the system database.
symbols
Created by the toolbox and stored in the controller, the symbol table contains signal
names and descriptions for diagnostic messages.
task
A group of blocks and macros scheduled for execution by the user.
TCP/IP
Communications protocols developed to inter-network dissimilar systems. It is a de
facto UNIX standard, but is supported on almost all systems. TCP controls data
transfer and IP provides the routing for functions, such as file transfer and e-mail.
time slice
Division of the total module scheduling period. There are eight slices per single
execution period. These slices provide a means for scheduling modules and tasks to
begin execution at different times.
toolbox
A Windows-based software package used to configure controllers and drives.
trend
A time-based plot to show the history of values.
Trend Recorder
A subsystem of the toolbox that monitors and graphs signal values from a controller
or drive.
TrueType
Scaleable font technology that renders printer and screen fonts. Each TrueType font
contains its own algorithms for converting the outline into bitmaps.
Tuning Variable
Tuning Variable is a signal with upper and lower limits, which define the bounds of
the initial value and when making runtime changes.

validate
Makes certain that items or devices do not contain errors and verifies that the
configuration is ready to be built into pcode.
Windows NT
Windows New Technology. Advanced 32-bit operating system from Microsoft for
386s and above. It runs NT-specific applications as well as those written for DOS,
Windows 3.x (16 and 32-bit), OS/2 character mode (non-graphical) and POSIX. NT
does not use DOS; it is a self-contained operating system.
word
A unit of information composed of characters, bits, or bytes, that is treated as an
entity and can be stored in one location. Also, a measurement of memory length,
usually 32 bit in length but van also be 4, 8, or 16-bits long.

Controller tab 2-18
Create a controller 3-45
Index Database
SDB and USDB 11-2
DLAN+ Interface
Status_S pages 3-147, 9-75
Draw commands 8-14
Dynamic Data Recorder (DDR) 3-148
Add Signals 3-152, 12-11, 12-12
Configure DDR 3-149
Status Signals 3-150
UpdateDDR 3-152
A
E
AcDcEx2000 tab 2-26
Alarm Scanner tab 3-7, 3-10 EGD Interface
Application Code Edit 13-9, 14-8
Download 3-100, 3-101, 3-107 Exchanges 9-32, 9-33, 9-35, 13-9, 13-10, 14-9
Modify 3-101 Insert 13-9
Application Diagnostics
Generating 3-142, 9-59 F
Application Documentation
Block diagram 3-125 Field Control module
Reports 3-28, 3-125, 3-133, 3-139 Conventional 9-52
Intelligent 9-53
Points 9-2, 9-14, 9-36, 9-37, 9-48, 9-54, 9-63, 11-6
B Finder window
Batch Operations Text/Address tab 3-146, 4-3
Error log 5-5 Forcelist commands 9-58
Block Diagram tab 2-19, 3-131, 3-132
Blocks G
Description 3-137, 3-138, 12-10
Flow diagram 3-131 Genius Block Detail View 9-47, 9-48
Rename 3-83, 3-84 Genius network
Renumber 3-26, 3-83, 3-84 Field Control Station 9-39, 9-44, 9-45, 9-48, 9-55, 9-
Rubber 3-79 56, 9-58
LAN board 9-43
View 9-41
C Get From Database command 3-91, 11-2
Checkin/Checkout utility 5-4, 6-1 Graphics window
Comment block 3-131 Create 8-3
Configuration files Draw commands 8-14
Export 3-17 Properties toolbar 8-9, 8-30
Control Constant View View Signal Summary 8-5, 8-9
access 3-118 Graphics Windows for the Control Operator Interface
Access 2-7, 2-34 (COI) 8-40
Controller Properties
Alarm Scanner 3-7, 3-10 H
General 2-13, 3-3, 3-39, 9-4
Memory 3-10 Hardware and I/O Definitions
Note 3-6 Description 3-137, 3-138, 12-10
NTP 3-5 Help
TMR 3-9 Menu 3-32
GEH-6403L Toolbox for a Mark VI Turbine Controller Index I-1

Hold List Scanner tab 3-10 Description 3-137, 3-138, 12-10
Points 3-137, 9-14, 9-30, 9-37, 9-47, 9-48, 9-54, 9-59,
I 9-63, 9-66, 9-69, 9-71, 9-72, 9-75, 13-11
NTP tab 3-5
I/O Mapper 3-3
I/O or Network Interface
O
Insert 9-3, 9-23
Mark VI 2-4, 2-29, 3-1, 3-3, 3-7, 3-8, 3-10, 3-12, 3- OC2000 tab 2-25
13, 3-29, 3-42, 3-57, 3-58, 3-91, 3-96, 3-99 Output files
I/O Points 8-38, 9-2, 9-59 Types 3-28, 3-139, 3-140, 9-6, 9-36
Inline module 3-43 Override module 3-43
Innovation Series Drive tab 2-20, 2-28
Instanced module 3-43 P
Passwords
L
Changing 2-10, 2-11
Libraries Pcode files (.pcd)
Description 3-137, 3-138, 12-10 Build 3-24, 3-29, 3-91, 3-92, 3-101, 3-107, 3-146, 3-
Libraries tab 2-16 147, 5-1, 9-31, 12-2, 12-3, 12-15
License Description 3-137, 3-138, 12-10
Agreement 2-2 Print tab 2-17
Privilege level
M Functions 2-8, 2-9, 3-1, 3-21, 3-43, 3-44, 3-46, 3-53,
3-63, 3-125, 3-134, 10-8, 10-9, 11-2
Macro and Module libraries Setting 2-1
Lock 6-1 Product code (runtime)
Macro Definition Load 3-28, 3-94, 3-116
Description 3-137, 3-138, 12-10 Upgrade 2-3, 3-105, 9-16
Edit 3-72, 3-74, 3-81 Profibus Interface 10-13, 10-14
Macro Pins Project files (.prj)
Description 3-137, 3-138, 12-10 Create and view 3-137, 3-138, 12-10
Macros
Description 3-137, 3-138, 12-10
R
Main Board
NOVRAM 3-108, 9-60, 9-61, 9-62, 9-63, 11-7 Register network
Memory tab 3-4 Custom Register Network 9-64, 9-72
Menus DH+ 9-64, 9-70, 9-71
Help 2-7, 2-10, 2-29, 3-8, 3-17, 3-32, 3-38, 8-3 Ethernet Modbus 9-64, 9-68, 9-71, 9-72
Module Definitions Ethernet SRTP 9-65, 9-67
Description 3-137, 3-138, 12-10 Serial Modbus 9-68, 9-69
Edit 3-65 Reports
Insert 3-63 Generate 3-142, 3-144, 9-58
Module Pins Signal Cross Reference 3-28, 3-125
Description 3-137, 3-138, 12-10 Signal list 3-133
Modules Simulation data 3-133
Description 3-137, 3-138, 12-10 Requirements 2-2
Resource name 7-2
N RLD editor
Commands 3-25, 3-28, 3-29, 3-83, 3-91, 3-115, 3-
Network Interface 124, 8-14, 9-16, 9-30, 12-2, 13-4, 14-3, 14-4
Create 10-3 Description 3-137, 3-138, 12-10
Dialect 10-7
Signals 3-24, 3-29, 3-37, 3-53, 3-91, 3-115, 3-122, 3-
S
133, 3-134, 3-152, 4-3, 8-38, 8-40, 9-25, 9-63
Note tab 3-6 Scale definitions
NOVRAM Description 3-137, 3-138, 12-10
I-2 Index GEH-6403L Toolbox for a Mark VI Turbine Controller

Serial Loader
Starting 3-83
Settings
AcDcEx2000 2-26
Controller 2-18
Database 2-15, 11-12, 12-15
EX2100 2-23
General 2-13, 3-3, 3-39, 9-4
Innovation Series Drive 2-20, 2-28
Libraries 2-16
OC2000 2-25
Print 2-17
Static Starter Drive 2-24
Tosvert Series Drive 2-22
Trend Recorder 2-27
Signals
Concepts 3-37, 3-45, 7-2, 10-2, 13-2, 14-2
Pin connection 11-5
Status_S pages 3-147, 9-75
String substitution 3-89
System information
Files 7-2
T
TCP/IP
Configure 3-98
TMR tab 3-9
W
Watch Windows 3-28, 3-114, 3-115
Select Watch Window 3-114
Work Area
Detached Summary View 2-5, 2-19, 3-85, 3-112, 3-
131, 8-39, 9-41, 9-47
GEH-6403L Toolbox for a Mark VI Turbine Controller Index I-3

Notes
I-4 Index GEH-6403L Toolbox for a Mark VI Turbine Controller

g GE Energy
1501 Roanoke Blvd.
1 540 387 7000

www.geenergy.com

Geh 6403 Control System Toolbox For A MK6 Turbine Controller

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Geh 6403 Control System Toolbox For A MK6 Turbine Controller

Загружено:

Авторское право:

Доступные форматы

GE Energy

Control System Toolbox

If further assistance or technical information is desired, contact the nearest GE Sales or

2000 - 2007 General Electric Company, USA. All rights reserved.

CompactFlash is a registered trademark of SanDisk Corporation.

Reader Comments GE Energy

We welcome comments and suggestions to make this publication more useful.

Publication Issue/Revision Date

Detach and fax or mail to the address noted above.

.......................................................................................... Fold here first ........................................................................................................

Indicates a procedure, condition, or statement that, if not

Indicates a procedure, condition, or statement that, if not

Indicates a procedure, condition, or statement that should be

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

Isolation of test equipment from the equipment under test

To minimize hazard of electrical shock or burn, approved

To prevent personal injury or equipment damage caused by

GEH-6403L Toolbox for a Mark VI Turbine Controller Contents i

ii Contents GEH-6403L Toolbox for a Mark VI Turbine Controller

GEH-6403L Toolbox for a Mark VI Turbine Controller Contents i

ii Contents GEH-6403L Toolbox for a Mark VI Turbine Controller

GEH-6403L Toolbox for a Mark VI Turbine Controller Contents i

Glossary of Terms G-1

ii Contents GEH-6403L Toolbox for a Mark VI Turbine Controller

GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 1 Overview 1-1

How To Use This Manual

1-2 Chapter 1 Overview GEH-6403L Toolbox for a Mark VI Turbine Controller

Bold Indicates that the word is being defined.

GEH-6403L Toolbox for a Mark VI Turbine Controller Chapter 1 Overview 1-3

1-4 Chapter 1 Overview GEH-6403L Toolbox for a Mark VI Turbine Controller

Note If technical assistance is required beyond the instructions provided in the

Maintain Multiple Releases of Toolbox

Use Controller Files

Status Privilege Level

Access Online Help

To obtain Help on . . . Do this . . .

Privilege Level Functions

Select the privilege

Enter the old

Enter the new

Re-enter the new

2. Follow the appropriate instructions from the Password_ID text.

Use compact export format

Save Bookmarks in files

Auto-Save files every [ ]

Compress files when Backup files before save

Select one of the following

None dictates that no file

Load last file loads the

Select file allows you to

Select the SDB

Enter the name

Select the product

Browse allows you

Select the font for

Select the font for the

Select the font for the

Select this check box to

Select this check box to

Select to display file

Select this check box to

Select to display file

Select this option to