GEH-6403 Control System Toolbox Mark VI Turbine Controller

GEH-6403A
(Supersedes GEH-6403)
*(,QGXVWULDO6\VWHPV
Control System Toolbox

For a Mark VI Turbine Controller
Publication: GEH-6403
Issued: 1999-06-12
Control System Toolbox

For a Mark VI Turbine Controller
© 1999 General Electric Company, USA.
All rights reserved.
Printed in the United States of America.
These instructions do not purport to cover all details or variations in equipment, nor to provide
every possible contingency to be met during installation, operation, and maintenance. If further
information is desired or if particular problems arise that are not covered sufficiently for the
purchaser’s purpose, the matter should be referred to GE Industrial Systems, Salem, Virginia,
USA.
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
Industrial Systems.
ARCNET is a registered trademark of Datapoint Corporation.

Ethernet is a trademark of Xerox Corporation.
Genius is a registered trademark of GE Fanuc Automation North America, Inc.
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.
PC is a registered trademark of International Business Machines Corporation.
Series 90 is a trademark of GE Fanuc Automation North America, Inc.
QNX is a registered trademark of QNX Software Systems, LTD.
Windows is a registered trademark of Microsoft Corporation.
Windows NT is a registered trademark of Microsoft Corporation.
Safety Symbol Legend
Indicates a procedure or condition that, if not

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

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

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

To prevent personal injury or equipment damage
! caused by equipment malfunction, only adequately
trained personnel should modify any
programmable machine.
Warning
The example and setup screens in this manual do

! not reflect the actual application configurations. Be
sure to follow the correct setup procedures for
your application.
Caution
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 Installation 2-1

Introduction............................................................................................................................ 2-1
Computer Requirements......................................................................................................... 2-2
Installing Control System Solutions....................................................................................... 2-2
License Key ............................................................................................................. 2-3
Destination Directory............................................................................................... 2-3
Registration License Agreement.............................................................................. 2-4
Product Selection ..................................................................................................... 2-5
Uninstall Products.................................................................................................... 2-5
Chapter 3 Using the Toolbox 3-1

Introduction............................................................................................................................ 3-1
Upgrading from Previous Releases ........................................................................................ 3-1
Maintaining Multiple Releases of Toolbox ............................................................. 3-1
Migrating Files to Release 5 .................................................................................... 3-2
Using Controller Files.............................................................................................. 3-2
Starting the Toolbox............................................................................................................... 3-3
Work Area ............................................................................................................... 3-4
Accessing Online Help........................................................................................................... 3-5
Privilege/Password................................................................................................................. 3-5
Toolbox Options .................................................................................................................... 3-8
General..................................................................................................................... 3-8
Database................................................................................................................... 3-9
Directories.............................................................................................................. 3-10
Libraries................................................................................................................. 3-11
Block Diagram....................................................................................................... 3-12
Print ....................................................................................................................... 3-13
Controller ............................................................................................................... 3-14
Innovation Series Drive ......................................................................................... 3-15
OC2000.................................................................................................................. 3-16
AcDcEx2000.......................................................................................................... 3-17
Trend Recorder ...................................................................................................... 3-18
Connecting the Toolbox....................................................................................................... 3-19
Innovation Series/Mark VI Controller ................................................................... 3-19
OC2000.................................................................................................................. 3-19
AcDcEx2000.......................................................................................................... 3-20
Innovation Series Drive ......................................................................................... 3-21
Remote Connection................................................................................................ 3-22
GEH-6403A Toolbox for a Mark VI Controller Contents • i

Chapter 4 Configuring a Mark VI Controller 4-1
Introduction............................................................................................................................ 4-1
Creating a Controller.............................................................................................................. 4-2
Memory Tab ............................................................................................................ 4-4
NTP Tab .................................................................................................................. 4-4
Note Tab .................................................................................................................. 4-5
TMR Tab ................................................................................................................. 4-5
Alarm Scanner Tab .................................................................................................. 4-6
Toolbox Work Area ................................................................................................. 4-8
Working with Controller Files and Menus........................................................................... 4-14
Importing Standard Files........................................................................................ 4-16
Saving Files............................................................................................................ 4-17
Opening and Closing Files..................................................................................... 4-17
Exporting Configuration Files ............................................................................... 4-17
Working with Project Files .................................................................................... 4-18
Locked Items.......................................................................................................... 4-20
Batch Operations.................................................................................................... 4-22
Blockware Concepts............................................................................................................. 4-23
Blocks and Block Pins ........................................................................................... 4-24
Macros, Macro Definitions, and Macro Pins ......................................................... 4-24
Tasks and Scheduling ............................................................................................ 4-25
Modules, Module Definitions and Module Pins .................................................... 4-28
Functions................................................................................................................ 4-29
Libraries................................................................................................................. 4-29
Configuration ....................................................................................................................... 4-29
Create/delete Blockware ........................................................................................ 4-30
Functions................................................................................................................ 4-30
Type Definitions .................................................................................................... 4-31
Scale Definitions.................................................................................................... 4-33
Signal Definitions .................................................................................................. 4-34
Table Definitions ................................................................................................... 4-36
Import Files............................................................................................................ 4-37
Edit Dialog Box ..................................................................................................... 4-38
Module Definitions and Modules .......................................................................... 4-40
Module Pins ........................................................................................................... 4-43
Macro Definitions .................................................................................................. 4-45
Macro Pins ............................................................................................................. 4-46
Tasks ...................................................................................................................... 4-48
Blocks and Macros................................................................................................. 4-51
Block Flow Diagram.............................................................................................. 4-59
Instancing Module and Macro Pins ....................................................................... 4-60
Device Menu Commands ..................................................................................................... 4-63
Database Commands.............................................................................................. 4-63
Validating .............................................................................................................. 4-64
Building Pcode and Symbols ................................................................................. 4-65
Software Setup ..................................................................................................................... 4-67
Controller Setup..................................................................................................... 4-67
Serial Loader.......................................................................................................... 4-68
Initializing the Flash .............................................................................................. 4-68
Configuring TCP/IP............................................................................................... 4-70
Product Code (Runtime) Software......................................................................... 4-71
Application Code ................................................................................................... 4-73
Software Modifications ........................................................................................................ 4-73
Modifying the Application Code ........................................................................... 4-73
Upgrading the Product Code (Runtime) Software ................................................. 4-77
ii • Contents GEH-6403A Toolbox for a Mark VI Controller

Monitoring ..................................................................................................................... ...... 4-80
Going Online/Offline ............................................................................................. 4-80
Control Constant View......................................................................................................... 4-82
Control Constant Work Area ................................................................................. 4-82
Application Documentation ................................................................................................. 4-85
Block Diagrams ..................................................................................................... 4-85
Reports................................................................................................................... 4-88
Application Diagnostics ....................................................................................................... 4-91
Types of Application Diagnostics.......................................................................... 4-91
Generating Application Diagnostics ...................................................................... 4-93
Control Blocks that Generate Diagnostics ............................................................. 4-95
Runtime Data Flow................................................................................................ 4-97
Diagnostic Data...................................................................................................... 4-98
Multilingual Support for Diagnostics on Human-Machine Interface................... 4-100
Chapter 5 Finder 5-1

Introduction............................................................................................................................ 5-1
Using the Finder..................................................................................................................... 5-1
Finder Window ........................................................................................................ 5-2
Target Finds ............................................................................................................. 5-3
Chapter 6 Batch Operations 6-1

Introduction............................................................................................................................ 6-1
Batch Operations File............................................................................................................. 6-1
Configuring A Batch Operation............................................................................... 6-2
Running a Batch Operations File ............................................................................. 6-3
Open/Save Batch Operations File ............................................................................ 6-4
Chapter 7 File Checkin/Checkout 7-1

Introduction............................................................................................................................ 7-1
Initialization ........................................................................................................................... 7-1
Chapter 8 Configuring System Information 8-1

Introduction............................................................................................................................ 8-1
Working with System Information Files ................................................................................ 8-1
Concepts................................................................................................................................. 8-1
Scale Definitions...................................................................................................... 8-2
Broadcast Alarms..................................................................................................... 8-2
Type Definitions (Resource).................................................................................... 8-2
Configuration ......................................................................................................................... 8-3
Creating/Modifying System Information................................................................. 8-3
Inserting Scale Definitions....................................................................................... 8-3
Inserting DLAN+ Groups ........................................................................................ 8-5
Inserting Resources.................................................................................................. 8-7
Chapter 9 Graphics Window 9-1

Introduction............................................................................................................................ 9-1
Graphics Window Objects ..................................................................................................... 9-1
Create Graphics Window......................................................................................... 9-2
Menu Bar ................................................................................................................. 9-2
Drag-and-Drop Data ................................................................................................ 9-6
GEH-6403A Toolbox for a Mark VI Controller Contents • iii

Settings....................................................................................................................... ............ 9-6
Frame Size ............................................................................................................... 9-7
Pen Color and Pen Width......................................................................................... 9-7
Brush Color and Use Brush ..................................................................................... 9-7
Text Font.................................................................................................................. 9-8
Draw Commands.................................................................................................................. .. 9-9
Insert Picture .......................................................................................................... 9-10
Animating Objects ............................................................................................................... 9-11
Value and Enable Return ....................................................................................... 9-12
Numeric Animation ............................................................................................... 9-17
Bar Graph............................................................................................................... 9-18
Trend...................................................................................................................... 9-19
Text........................................................................................................................ 9-20
Color ...................................................................................................................... 9-21
Input Fields .......................................................................................................................... 9-22
Numeric ................................................................................................................. 9-22
Setpoint .................................................................................................................. 9-23
Initial Value ........................................................................................................... 9-23
Text........................................................................................................................ 9-24
Toggle Command .................................................................................................. 9-24
Hyperlinks.............................................................................................................. 9-25
Using Graphics Window Objects......................................................................................... 9-26
Signal Substitution................................................................................................. 9-31
String Substitutions................................................................................................ 9-31
Chapter 10 Hardware and I/O 10-1

Introduction.......................................................................................................................... 10-1
I/O and Network Interface.................................................................................................... 10-1
I/O Points ............................................................................................................... 10-2
Insert I/O and Network Interfaces.......................................................................... 10-3
Mark VI I/O ......................................................................................................................... 10-5
Racks...................................................................................................................... 10-5
Configuring Boards in the Outline View ............................................................. 10-10
Regulators ............................................................................................................ 10-13
Sequence of Events .............................................................................................. 10-16
Trend Recorder .................................................................................................... 10-17
DLAN+ Interface ............................................................................................................... 10-18
Modify DLAN+ ................................................................................................... 10-18
Status_S Pages ..................................................................................................... 10-19
EGD Interface .................................................................................................................... 10-27
Edit EGD ............................................................................................................. 10-27
EGD Exchanges................................................................................................... 10-28
EGD Points .......................................................................................................... 10-31
Genius Networks................................................................................................................ 10-33
Genius Network View.......................................................................................... 10-34
Configuring the Genius LAN Board.................................................................... 10-36
Genius Blocks ...................................................................................................... 10-38
Field Control Station............................................................................................ 10-41
Field Control Module........................................................................................... 10-43
Genius Block and Field Control Module Points .................................................. 10-47
Third Party Operator Interfaces ........................................................................... 10-47
Monitoring Genius............................................................................................... 10-49
Main Board ........................................................................................................................ 10-54
Non-volatile Random-Access Memory................................................................ 10-54
NOVRAM Points................................................................................................. 10-56
iv • Contents GEH-6403A Toolbox for a Mark VI Controller

Register Network ............................................................................................................... 10-58
Ethernet SRTP ..................................................................................................... 10-58
Serial Modbus ...................................................................................................... 10-60
Allen-Bradley Data Highway™ Plus (DH+) ....................................................... 10-62
Custom Register Network.................................................................................... 10-64
Modify Page Settings........................................................................................... 10-66
Modify Point Settings .......................................................................................... 10-67
Chapter 11 Configuring the Network Interface 11-1

Introduction.......................................................................................................................... 11-1
Concepts............................................................................................................................... 11-1
Configuration ....................................................................................................................... 11-2
Creating the Network Interface.............................................................................. 11-2
Working with Network Interface Files .................................................................. 11-4
Defining a Network Connection ............................................................................ 11-5
Inserting/Defining Signals ..................................................................................... 11-7
Mapping Signals to a Network............................................................................... 11-7
Specifying Signals Used by the Network Interface ............................................... 11-8
Put Into Database/Get From Database ................................................................. 11-10
Chapter 12 Signals and the Database 12-1

Introduction.......................................................................................................................... 12-1
Signal Concepts.................................................................................................................... 12-1
AcDcEx2000 Signals ............................................................................................. 12-2
Mark VI Controller Signals ................................................................................... 12-2
Scale Definitions.................................................................................................... 12-7
Signal Selector ....................................................................................................... 12-8
SDB and USDB ................................................................................................................... 12-9
Put into and Get from Database ............................................................................. 12-9
Appendix A System Database (SDB) Browser A-1

Introduction........................................................................................................................... A-1
Starting the SDB Browser ..................................................................................................... A-1
From SDB Server Control ...................................................................................... A-2
From the Toolbox or SDB Utilities......................................................................... A-3
SDB Browser Toolbar ............................................................................................ A-4
SDB Browser Tabs................................................................................................................ A-5
Signal Tab............................................................................................................... A-5
Topology Tab.......................................................................................................... A-9
Where Used Tab ................................................................................................... A-10
Alarms Tab ........................................................................................................... A-11
Scale Tab .............................................................................................................. A-11
NetGroups Tab...................................................................................................... A-12
Resources Tab....................................................................................................... A-12
Signal Fields........................................................................................................................ A-13
Table 1. SDB Signal Fields.................................................................................. A-13
Data Types ............................................................................................................ A-18
Glossary of Terms G-1
GEH-6403A Toolbox for a Mark VI Controller Contents • v

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® 100 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 & EX2000 Digital Exciter
(AcDcEx2000)
Primary functions of the toolbox include:
The toolbox software configures • Graphic-based editor for configuring application code
various control equipment.
• Block macros and module library support
Therefore, each product package
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-6403A 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 provided. It presumes that the user has already
appearance. installed Windows and possesses at least a medium-level knowledge of Windows.
Hardware requirements and instructions for installing the products are 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 Installation. This chapter describes the PC and installation requirements
for the products in Control System Solutions.
Chapter 3 Using the Toolbox. This chapter provides basic startup procedures and
features for using the toolbox to configure a product.
Chapter 4 Configuring a Mark VI Turbine Controller. This chapter describes
how to use the toolbox to configure a controller.
Chapter 5 Finder. This chapter defines the features of the Finder, which searches
the device in the toolbox for items such as text and signals.
Chapter 6 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 7 File Checkin/Checkout. This chapter describes the Checkin/ Checkout
utility, which allows users to share files contained in a master file.
Chapter 8 System Information. This chapter describes the System Information
device which configures information global to a project, making it available to other
interfaces.
Chapter 9 Graphics Window. This chapter describes the Graphic Window, which
creates custom graphics interfaces for customer and process requirements.
Chapter 10 Hardware and I/O. This chapter describes the controller networks and
I/O used in the toolbox.
Chapter 11 Configuring the Network Interface. This chapter provides
instructions for using the toolbox to configure a Network Interface.
Chapter 12 Signals and the Database. This chapter defines signals and their
sources. It also defines the topological information in the database.
Appendix A System Database (SDB) Browser. This chapter describes the SDB
Browser, which is used to view the contents of an SDB, display system topology,
and perform a filtered signal search on the SDB, list system scales, and more.
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-6403A 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 Bold Indicates the actual command or option that is chosen from a
menu or dialog box.
Italic Indicates a word used as a word or a letter used as a letter. For
example, the display should now read SDB has stopped. Italic
also indicates new terms, margin notes, and the titles of figures,
chapters, and other books in the toolbox package.
UPPERCASE Indicates a directory, filename, or block name. Lowercase letters
can be used when typing names in a dialog box or at the
command prompt, unless otherwise indicated for a specific
application or utility.
Monospace Represents examples of screen text or words and characters that
are typed in a text box or at the command prompt.
½ Indicates a procedure.
w 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 choose 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 (á) 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 choosing the
command.
Related Publications
GE provides system instruction manuals that include publications for the different
components of each product. If additional manuals are needed or for questions about
the publications, contact the nearest GE sales office or authorized GE sales
representative.
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 1 Overview • 1-3

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

Chapter 2 Installation
Introduction
This chapter describes the PC and installation requirements for the products in
Control System Solutions. Each product is defined with specific requirements and
any additional system dependencies. These products include the following:
System Integration • Control System Toolbox
Applications includes SDB
Utility, SDB Exchange, • System Integration Applications
DLAN+, GECAMS, ICN, • Innovation Series Controller*
Data Historian and more.
• Innovation Series Drive*
• AC/DC/EX2000 Drive*
• Maintenance & Diagnostics
Maintenance & Diagnostics
includes Mode Logger, • Trend Recorder Data Historian* (requires SDB)
Message Archiver, Message • SDB Server
Viewer, Diagnose, DLAN+
Status, and more. Toolbox applications are denoted with an *.
Section Page
Computer Requirements .......................................................................................... 2-2

Installing Control System Solutions ........................................................................ 2-2
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 2 Installation • 2-1

Computer Requirements
The minimum PC requirements are determined by the selected product combination
and the topology configuration of the PC(s). The minimum requirements to use the
Control System Solutions products are as follows:
• 100 MHz processor (Pentium 166 or higher recommended)
A cursor-positioning device is • Microsoft® Windows® 95 or Windows NT® 4.0
highly recommended.
• VGA display (640 x 480 x 16 color or gray scale)
• 16 MB RAM in Windows 95 (32 MB recommended) or 24 MB RAM in
Windows NT (32 MB recommended)
• 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 communications with the toolbox over a LAN)
• Printer (with appropriate Windows driver installed)
Installing Control System Solutions

For assistance, contact: 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
Industrial Systems
beginning. A dialog box will prompt you for a license key, which can be found on
General Electric Company
the actual CD. Also, you must agree to the standard Software License Agreement for
Product Service Engineering
these products.
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA A default destination directory is set for all products selected. This directory can be
Phone + 1 540 387 7595 modified, but only during the first installation. Setup installs the required
Fax + 1 540 387 8606 components and checks available disk space before copying files. You can also
(replace + with the choose to cancel setup and exit at any time before you initiate the selected products.
international access code)
½ To install from a CD
Install the desired products 1. Place the Control System Solutions CD in the disk drive.
from CD, following the
2. The Setup program executes automatically.
directions on the screen.
Then, install each product file 3. Follow the Setup instructions from the screen.
starting with the SDB
product.
2-2 • Chapter 2 Installation GEH-6403A Toolbox for a Mark VI Turbine Controller

License Key
Enter the License Key number.

This number is printed on the
actual CD. The number is not
case sensitive.
Destination Directory
The destination directory for

each product is set to the
default directory C:\Program
Files\GE Control System
Solutions. If desired select a
different directory to load the
products.
This dialog box option can

only be selected during the
initial installation of these
products. After that all future
installs and upgrades default
to the first directory selected.
Select a directory and click Next. Setup automatically continues to load. The Control
System Solutions product selection dialog box displays to allow you to select desired
products described in the following sections.

Registration License Agreement
The following License Agreement dialog box displays during installation. The
license must be read and agreed to before installation can continue.
Please read the entire

agreement (scroll bar must
be at the bottom of the
dialog box).
Click Yes to accept the

agreement.

Product Selection
Note A description of each product and the disk space required displays when the
product is selected. For additonal information on a product, refer to the
documentation noted in the description.
You must click to the left of each

product you want to install. A
check mark must display beside
the product name.
Click the product name in the left

column to check all the
application in that group. Click
again to uncheck all.
The number beside each product

indicates the amount of space
required for that product.
A description of each product

displays when it is selected
(highlighted).
Products that were not purchased as part of

the Control System Solutions CD do not
appear in the product selection list.
Uninstall Products
Note Before upgrading to Release 5, product components should be uninstalled and
then installed again using the Release 5 CD or network installation.
½ To uninstall product(s)
1. Click Windows Start button, Settings and click Control Panel.

2. From the Control Panel dialog box, double-click on Add/Remove
Programs. The Add/Remove Program Properties dialog box displays.
3. Click on the tab Install/Uninstall. A list of all installed programs displays.
4. From the list box, click on the program(s) to uninstall.
– Or –
To remove all products, click GE Control System Solutions Uninstaller.

5. Click Add/Remove.
The following screen displays to show when uninstall is complete and the status of
all items deleted.
If you choose to remove all products by selecting

GE Control System Solutions Uninstaller, the
following dialog box displays. All installed
products are listed and will be removed.

Chapter 3 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
Upgrading from Previous Releases.......................................................................... 3-1

Starting the Toolbox ................................................................................................ 3-3
Accessing Online Help ............................................................................................ 3-5
Privilege/Password................................................................................................... 3-5
Toolbox Options ...................................................................................................... 3-8
Connecting the Toolbox......................................................................................... 3-19
Upgrading from Previous Releases

Note To upgrade to Version 5 of the toolbox, it is recommended that you first
uninstall any previous version of toolbox.
Maintaining Multiple Releases of Toolbox

To maintain different releases of the toolbox on a single system, consider the
following:
• Multiple versions of Release 5 cannot be installed on one system. The
installation directory for Release 5 of the toolbox is chosen 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. In order to use multiple releases, it is recommended to use
different user accounts for each release.
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 3 Using the Toolbox • 3-1
• 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 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.
Migrating Files to Release 5

Release 5 of the toolbox can read binary files written by Release 4, therefore it is not
necessary to export and re-import. However, if new libraries must be incorporated
into existing configurations, it is necessary to export and re-import the files. 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.
Using Controller Files

Note The following procedure is for a controller only.
To upgrade controller files to use new controller product 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, choose Export 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 import the new product libraries and all other
.tre files required to create the controller. Save the new binary working file.
3-2 • Chapter 3 Using the Toolbox GEH-6403A Toolbox for a Mark VI Turbine Controller
Starting 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
Solutions and GE Control System Toolbox.
To create a device, refer to
Chapter 4.
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 one drive or A drive or controller’s runtime action is configured using the toolbox. From the File
controller is open in the Work menu, begin a New configuration or Open a previously saved configuration file. The
Area, each device will have a toolbox Work Area (shown below) is the main screen and contains the following:
screen with an Outline View
Outline View displays the configuration in a hierarchy, with the drive/controller
and Summary View.
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 that is chosen (highlighted) in the Outline View. When Tracking is off, it freezes the
off. Summary View of the last chosen item.
Find the cause of an error by Log View displays configuration data for the item that is highlighted. This data
double-clicking on the error. compiles during toolbox functions, such as file imports, validations, builds, or errors.
Note The following screen represent a basic toolbox Work Area format. Menu
commands, toolbar, and Outline View items will vary with the product installed.
Titlebar
Toolbar
Bookmark Summary
View
Note
Outline
View
Log
View
Status bar
Status bar
It can be toggled on and off Status Bar displays information across the entire bottom of the screen. When online,
from the View menu. the left side displays a description of various toolbox commands or notes entered by
the user. To display a menu command description, click on the menu command and
move the pointer over the command. The right side displays device information for
the controller or drive selected, such as idle time, connection status or EEPROM
values.
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 Summary
Detached Summary View View are separate from the Summary View (see the section, Toolbox Options). This
window can be sized, configured, and edited.
Double click on the Note Note can be created when most items are inserted into the drive/controller. Choose
icon to edit the note. an item, then choose 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 to
icon . them easily using the Bookmark commands 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 .
Instead of using a menu, click Work Area commands can be accessed through the menu bar or a shortcut toolbar,
a shortcut button to execute depending on the currently selected product file. For more information on each
the command. command, refer to Chapter 4.
Accessing Online Help

To obtain Help for the dialog Specific dialog box Help is 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 on the desired block with the right mouse button and
choose Item Help
Help contents Choose the Help menu and choose Contents
Help Choose the Help menu and choose Using Help
Specific word(s) Choose the Help menu, choose Contents, and choose 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. Then, 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, choose Privilege.
Enter a three-character ID,

such as your initials.
Click OK.
Privilege Level Functions
A password can be assigned to each of the five toolbox privilege levels defined
below. (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 Option menu/
Settings
Print blockware code and reports
Change the password for level 0
1: Change Controller All functions allowed in Level 0, including change
Variables and Signals and password levels in Levels 0 and 1
Drive Advanced Maintenance
Force signals in a controller
Change the value of variables
2: Full Controller Access and All functions allowed in Level 0 and Level 1
Drive Advanced Maintenance
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
Change the location of the password file
3: Drive Block Area and Menu Alter block area and change application menu
Maintenance structure
4: Full Drive Access Change GE parameters
Edit Hardware
½ To change the password
1. From the Options menu, choose Password. The Changing password
dialog box displays.
2. Click on the privilege level to change.
3. Click OK. The following dialog box displays to enter the new password.
Change Password or Default Password Directory
Enter the old password

in text box 1) and press
the Tab key.
Tab
Enter the new password

in textbox 2) and press
the Tab key.
Tab
Enter the new password

again in text box 3) to
verify it is correct.
When a password is created, it is encoded in the file UCPASSWD.INI in the

Windows NT installation directory. This default directory can be changed, if the user
has a privilege level 2.
½ To change the default password file directory
w From the Options menu, choose Settings, and then choose the tab General.
Enter a directory or choose a directory

from Browse…
Enter three characters that identify the current user. You

will not be prompted for initializations when values change.
Note It is recommended that the password file be kept on the local PC to avoid loss
of access in the case of downtime on a remote node.
Toolbox Options
Option settings are saved in The toolbox’s working environment can be defined for each application. This section
the user’s Windows registry describes each tab that can be set to customize the toolbox drive/controller, database,
when the toolbox is closed. block diagrams, and such. These tabs are located in the Options menu under
Settings.
½ To customize the toolbox settings
1. From the Options menu, click Settings. The Setting dialog box displays.
Click on a tab to bring it to the front and select options.
2. Choose OK to apply the changes and close the dialog box. Choose Cancel to
exit and not change any settings. Or, choose Apply to install the change
immediately and continue to customize other tab settings.
General
The General tab applies to all devices as noted and described below.
Choose a font for the Choose a font for the Click the check box to skip a level of verification
Outline View. The default Finder. menus and process changes more quickly.
font is System Bold.
Choose from the following

File options:
Load last file on startup

automatically loads the last
file that was in use when
the toolbox was exited.
Backup files before save

makes a backup copy of
files before saving new
information. This includes
.ucb, .dcb, .icb, and .ocb.
Use compact export

format compresses the .tre
files produced by
exporting. This uses less
hard disk space and is
easier to read and edit.
This setting is
recommended.
Compress files when

saving saves and stores
files in a compressed
format and save disk
space.
Save bookmarks in files

Enter three character Choose an alternate Choose the directory for the
saves bookmarks between
initials, which are used in language that the toolbox password file. A local
closing and reopening files.
the privilege/password. can use to for the directory is recommended.
You will not be prompted database and diagnostic Click Browse… to search
for initializations when symbol table. The default the directory structure and
values change. is English. choose a location.
Database
The Database tab defines the database and any required network information. It
applies to all devices as listed.
Choose a database:
USDB resides on a LynxOS PC.
Put Topology becomes active
when the USDB is selected. It
writes the device’s topology to
the USDB. Topology
information includes the device
attributes, network connections,
and network pages. If the box is
not checked, then the LynxOS
based importer must be used to
write topology information into
the USDB.
Enter the name of the host to

the USDB or SDB. The server
name is not case sensitive. (It
can also be the IP address,
such as 29.3.129.4, if a name
server is not available.)
Enter the location of the SDB

sub-directory on the server
where the database 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 GEDBHOST
environment variable on the
LnxOS PC, such as ustst_usdb.
Directories
The Directories tab defines the default directory structure for products that are
installed. Only enter directory paths where applicable.
Enter the default directory

that will displays when File/
Open is selected.
Enter the directory where the

controller product was
installed, such as the default
C:\Program Files\GE Control
System Solutions\Innovation
Series Controller. This
directory also contains
predefined sub-directories,
such as stdtree and runtime.

drive product files are
installed.

Mark VI product files are
installed.
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.
Choose the product

library to define.
Default libraries are

listed in this text box.
Use the command
buttons to enter and edit
the library list as
follows:
Up and Down rearrange
the order of the list.
Change inserts the
edited library back into
the list.
Add inserts the new
library from the text box.
Remove takes out the
highlighted library from
the list.
Browse... is used to
search the directory
structure and choose an
existing library.
Block Diagram
The Block Diagram tab allows you to specify how the block diagram displays in the
Summary View and Detached Summary View.
Display the blocks in a list with

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

diagrams 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 options for

interconnected block diagrams:
Show all pins displays all block
pins. This command disregards
the text box Visibility, if it is
checked in the Edit Macro Pin
Definition dialog box.
Reorder pins rearranges the
pins to minimize crossing the
connections on the diagram.
Show inputor Show output
connections display the
connection names and values.
Font size changes the font size
of all text on the block diagram.
Change the Summary View tracking feature to display

various levels of the hierarchy, when they are chosen
in the Outline View. Choose the item to display on the
lowest level. The default is Task/Macro.
Print
The Print tab allows you to set print options for the current device. It applies to
controllers and drives as listed.
This option applies only to controllers. Specify the scope of
signal cross referencing in the block diagram that is active.
Choose the font for the text that

displays immediately over blocks
in the diagram. The default font is
Courier New.
Choose the font for the Signal

Definitions and Where Used Lists
at the end of each block sub-
section. The default font is
Courier New.
Choose the font for the text at the

top of each new section and block
sub-section. The default font is
Arial.
Choose the font for all text not

listed above, including block
names and pins. The font size
directly affects the number of
blocks that display on a page of
the diagram. The default font is
Arial Narrow.
Controller
The controller tab allows you to choose options specific to the controller.
Allows 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.
Click to change the current

language to the alternate
language you chose in the
General tab.
Enter the IP address for the

PC with the toolbox software.
(This is used when the PC is
connected to more than one
network.)
Innovation Series Drive
The Innovation Series drive tab allows you to choose options specific to the drive.
Click on the drop-down box to choose the

communication port.
This option changes the

names used on the
diagrams and Outline View
to internal names used
mainly by firmware
developers. It should not
be checked.
Check this option to

program the keypad with
an additional language.
You are prompted for the
language when the
Download to Device and
Keypad menu is chosen.
If you check this option and

choose to go online, the
Device ID Verification
dialog box displays with
identification information
for the toolbox and the
device. It is normally
checked.
OC2000
The OC2000 tab allows you to choose options specific to the OC2000 device as
leader.
Check here to scale the

OC2000 operator panel
to fit the Summary and
Detached Summary
View.
Check here to maintain

proportions in the
operator panel and fit in
the Summary and
Detached Summary
View.
Overlay Font… allows

you to choose a font for
the OC2000 printed
overlay. The default is
Courier New.
Enter an IP Address,
such as 3.29.3.33, for
the default controller that
is serving the OC2000.
AcDcEx2000
The AcDcEx2000 tab allows you to choose options specific to an AcDcEx2000
device as listed.
Check here to display

the EE Addresses of
items in Block Area of
the Outline View.
Choose the Default

Communication
Settings:
Serial requires you to
choose a Baud Rate and
Com Port for
communications.
TCP/IP requires you to
enter either an IP
Address or a host name
in the text box Gateway.
Host names may 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 choose specific options as follows:
Select the font size Signal List Font sets

used in the upper the font type and
window of the Trend size used in the
Recorder. lower window of the
Trend Recorder.
Check Horizontal Grid

Lines to display horizontal
grid lines when in Replay
mode.
Check Vertical Grid Lines
to display vertical grid
lines is in Replay mode.
Check Right Vertical Axis
to display vertical axis on
the right-hand side of the
Trend Recorder.
Click here to automatically

configure the Trend
Recorder with predefined
signals. (This feature
currently only works with
Innovation Series drives
and when performing
MarkVI I/O board
calibrations.)
Click here to zoom in the

Trend Recorder, using the
mouse to drag-and drop a
rectangle on the screen.
Click here for a Yes/No
confirmation prompt to
display before the zoom
takes place.
Select the default pen width This sets the amount of memory the toolbox
(measured in pixels) used to reserves for storing traces. The default value of
draw the signal traces. 2 MB allows 4 signals to be captured at 32 ms
intervals for about 14 minutes before the oldest
data starts to be overwritten.
Click Show memory usage in status barshows
the amount of reserved memory that was used.
Connecting 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 in order 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
Control System Innovation Series Controller

+
- 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)
Remote Connection
For more information, refer Windows can make TCP/IP connections remotely, such as connecting the toolbox to
to the Windows a remote controller, using modems, as shown below.
documentation on 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 4 Configuring a Mark VI
Controller
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
Creating a Controller ............................................................................................... 4-2

Working with Controller Files and Menus............................................................. 4-14
Blockware Concepts .............................................................................................. 4-23
Configuration ......................................................................................................... 4-29
Device Menu Commands....................................................................................... 4-63
Software Setup....................................................................................................... 4-67
Software Modifications.......................................................................................... 4-73
Monitoring ............................................................................................................. 4-80
Control Constant View .......................................................................................... 4-82
Application Documentation ................................................................................... 4-85
Application Diagnostics......................................................................................... 4-91
GEH-6403A Toolbox for Mark VI Controller Chapter 4 Configuring a Mark VI Controller • 4-1
Creating a Controller
When the toolbox is started, the toolbox Work Area displays. This area is used to
configure the controller or maintain the open configuration file in the toolbox. You
must insert a new controller or open an exiting controller configuration file (.m6b).
½ To create a controller
Or click New
w From the File menu, choose New. The New dialog box displays.
Click on the tab,

Controllers.
Click on Mark VI
Turbine Controller.
Click OK.
The controller is
inserted into the Work
Area with the default
name, mkvi1.
The controller name is
the top of the
configuration hierarchy.
4-2 • Chapter 4 Configuring a Mark VI Controller GEH-6403A Toolbox for Mark VI Controller
Once the controller is inserted or opened, the Outline View of the Work Area
displays the following six configuration items under the controller name.
Default name
Configuration
items
½ To modify a controller
Or double-click on the 1. Click on the controller name to highlight it.
controller name.
2. From the Edit menu, choose Modify.
The Controller Properties dialog box displays. The following sections describe
each tab in the dialog box.
General Tab
Name identifies this This is the system SDB number. If set to 0, the next
controller when available SDB number is assigned to the device
communicating with the when data is put into the database.
SDB. It is defaulted to
mkvi1the first time a
controller is created. The
name is saved as a .prj.
For Simplex operations,

supply an IP address for
the R processor only. For
TMR operations supply a
separate address for R, S,
and T processors.
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).
This list box specifies
the hardware platform
that the configuration is
operating on. This field Choose the interval (ms)
Choose the basic I/O This field is not
is important for proper that the I/O mapper task
and compute rate for a applicable to Mark VI
control execution runs. The I/O mapper
Mark VI system. controllers.
records and for selecting task transfers signal
hardware and I/O. between different I/O
points, if the signals are
not used in blockware
code.
Memory Tab
The Memory tab informs the controller (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 of the application
program in memory, which is
necessary to perform an online
download. Memory that is not
allocated here is used by non-
continual process, such as sending
live data to toolbox sessions or
support diagnostic explanations.
Capture Buffer memory 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
NTP informs the controller how to configure its Network Time Protocol (NTP)
client. It is used to synchronize the controller’s clock with that of another computer
on the Ethernet.
Click this option to prevent the
controller from using NTP.
Click Broadcast to start the NTP

client and listen for broadcasts
from an NTP server.
Click Unicast to start the NTP

client and request the time from
the NTP servers specified in the
text boxes Primary Server and
Backup Server.
Note The NTP tab is not

supported in versions before 3.5
of the controller and OC2000
products. The above fields are
grayed out for products before
this version.
Note Tab
Enter configuration
information for this
controller.
The note is not used by the
toolbox. It is information for
you on the project history.
Click OK to close the dialog
box when you have finished
the note.
TMR Tab
In a TMR operation, this integer

signal is the internal process ID
number, where 1=<R>, 2=<S>,
and 3=<T>.
Enter the signal name to access it
within application code.
Enter the Boolean signal that

indicates if the 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 wish to access

this information within the
application, leave the fields blank.
Refer to Chapter 10 for more

information about the TMR
operation.
Alarm Scanner Tab
This tab specifies the parameters required to start up the Alarm subsystem in the
Mark VI controller. This subsystem scans an array of Boolean signals representing
various alarm conditions. When any of the signals change state they are queued
locally and an alarm message is transmitted to the specified alarm display device.
The following dialog box must be entered:
Check this box to enable the Alarm Enter the IP address of the
Scanner text boxes to enter signal names. device that displays the alarm.
Enter the signal name of the alarm ID

array. This array associates an alarm drop
number with each Boolean signal
scanned. The size of the alarm ID array
(number of Integer elements) must match
the size of the alarm signal array.
Enter the signal name of the Boolean array

to be scanned. The individual signals that
comprise the array are populated by the
ALMGRP block. The size of the alarm
signal array must match the size of the
alarm ID array.
Note: The remaining fields are optional

and constitute a standard signal interface
to third party DCS vendors that may be
required to implement a subset of the
alarm display function. These signals may
be connected to the appropriate I/O points
to make them visible to the DCS. The
alarm system drives the outputs and reads
the inputs as described. Horn Driver specifies an output Boolean signal that may be attached to an
external alarm horn contact output.
Alarm Present Indication specifies an
output Boolean signal that is driven TRUE Horn Silence specifies an input Boolean signal that can be used to turn off the
whenever any alarm in the controller is alarm horn via a discrete pushbutton.
active and FALSE when there are no
alarms. Acknowledge specifies an input Boolean signal that can be used to
acknowledge alarms via a discrete pushbutton.
Number of Active Alarms in Queue
specifies an output long Integer signal that Alarm Reset specifies an input Boolean signal that can be used to reset alarms
contains the current number of active via a discrete pushbutton.
alarms in the queue.
Alarm signal and ID (drop) arrays can be created within any signal definition. Only
one of each may exist within a MarkVI. 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. The length of the signal and ID array must be equal.
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)
Toolbox Work Area
Under the Menu bar, the The Toolbox Work Area is used to configure a controller. Across the top of this area
toolbar has shortcut buttons is the Title bar. It contains the name of the controller/file in use. Under the Title bar
for some of the menu is the Menu bar, which contains all the available menu commands.
commands.
Titlebar
Toolbar
Bookmark Summary
View
Note
Outline
View
Log
View
Status bar
Edit Status Connection/revision Idle time
The Status bar for the controller has three fields:
Status Field Displays Background

Edit white
READ yellow
Connection/ Offline gray
revision Equal green
Minor Diff yellow
Major Diff red
Idle time Idle white
File Menu
The File menu allows you to perform file operations with the commands listed.
New creates a new controller/file.

Or click
Open displays an existing controller/file.
Or click
Close exits an existing controller/file.
Save/Save As preserves an opened controller/file to a specified name.
Or click
Import retrieves a file from the specified source.
Or click
Export sends a file(s) to a specified source.
Print Setup allows you to choose a printer and printer connection.
Print provides a paper (hard) copy of a specified file or page.
Or click
Print Preview displays the page as it would be printed.
Mail 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 with the commands listed.
Modify edits the item that is highlighted in the Outline View.

Delete removes the item that is highlighted in the Outline View.
Or click
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 under the item highlighted in the hierarchy of
the Outline View.
Instance updates a single item or choose 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 easily using the menu commands or clicking on the bookmark icon.
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 move your cursor position to earlier
Or click selections in the Outline View.
Finder initiates the Finder window to search text and signal usage.
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 Appendix A).
Force Lists displays forced signals and I/O points that can be edited.
Reports creates a report of the Signal List, Signal Cross Reference, or Simulation
Data. Refer to the section, Reports in this chapter.
Trend Recorder monitors and graphs signal values from a controller (refer to
GEH- 6408).
Control Constants displays a separate window to edit control constants, which be
viewed and compared as a group, exported to .csv files for manipulation outside of
the toolbox, and merged back into the configuration.
Mark VI Status is a separate window, which displays the current revisions of items
in a controller.
Configuration Statistics opens the Device Metrics window to display memory
usage.
Window Menu
The Window menu arranges multiple views of multiple files in the controller Work
Area with the commands listed.
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 reopen files that were used most recently.
Device Menu
The Device menu allows you to manage the controller with the commands listed.
Validate makes certain that items or functions do not contain errors and confirms
Or click that a configuration is ready to build Pcode.
Build compiles the item that is highlighted.
Or click
Pack signals reassign address tokens when signals become fragmented.
Download sends files to the current controller.
Or click
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 and gets information from the database.
Create Undefined Signals produces a signal definition for signals not defined.
Options Menu
The Options menu allows you to manage general options for toolbox operation .
For more information on the

Option menu, refer to Settings allows you to assign general toolbox options.
Chapter 3. 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 that are in the temporarily unlocked state
(refer to the section Lock Function or Software Library).
Re-Lock Function/Software Library locks the either item and enables the
password.
Help Menu
The controller Help menu offers the following Help files.
Content 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 define errors that display in the Log View.
Item Help displays Help information about the item that is highlighted in the
Outline View.
Controller Tutorial presents step-by-step procedures for using the toolbox to
configure a controller.
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 (this feature is only
available if you have connection to the GE intranet.
About Toolbox displays the version number and platform for this application.
Working with Controller Files and Menus

An 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
Back up all files often to
avoid losing data. 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. This file can be downloaded to the controller.
Symbol files (.sym) describe the signals used by diagnostics to the controller. This
file can be downloaded to the controller.
Signal reports (.sig), cross-reference reports (.xrf), Pcode reports (.pcr), and
block diagram printouts (.prn) files can be generated, viewed, and printed.
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
Open Documentation
Import
Print
Open
*.prj file Export

(.tre) Get from
database
Windows NT or Build
The .prj files (Open/Export) Windows 95 *.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 is
SDB or
C:\Program Files\GE Control System Controller
USDB
Solutions\ToolBox.
Importing Standard Files
For more information, see To configure a new controller, you must import a set of standard files, either through
Toolbox options in Chapter 3. 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
runtime software.
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:
1. Sysdata.tre holds data types and eventually external signals defined by getting
information from the database.
2. Sblib.tre specifies the order and data types of basic block parameters of the
Standard Block Library.
3. Mkvi_io.tre specifies the hardware and I/O modules that can be configured with
the toolbox.
4. Turblib.tre is the Turbine specific block library.
½ To import a file
1. From the File menu, choose Import. The Import File dialog box displays a
Or click Import list all the available folders.
2. Choose stdtree.
3. If necessary, from the Files of type drop-down list box, choose .tre. All
available .tre files display in the list.
4. Choose a file from the list box.
Or, type a name in the File name: text box.
5. Click Open.
Saving Files
Saving a controller file writes the entire contents of the configuration to a .ucb 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
1. From the File menu, choose Save. The Save As dialog box displays.
Or click Save
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.
Opening and Closing Files

Opening a .m6b file reads a previously saved controller configuration into the
toolbox.
½ To open a file
1. From the File menu, choose Open. The Open dialog box displays.
Or click Open
2. Choose the file name and click Open.
Check the Release Notes located Note If an older version toolbox is used to open a .m6b that was saved with a newer
in the toolbox Help menu under version, a Warning displays. Either install the version toolbox the .m6b was saved in
About Toolbox. (listed in the Warning box) or consult the toolbox release notes to see if they are
compatible.
½ To close a file
w From the File menu, choose 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.
Exporting Configuration Files

The .tre files can be exported When a block library changes, a controller configuration must be exported to .tre
selectively or for the entire files and the standard library must be updated. This is also done whenever the format
controller. of the .m6b file changes in a non-backward compatible way because of a format
change, such as fields that have been added or subtracted.
Note The first time you export, make sure that each item is configured to be saved in
the desired directory. The default Project directory can be changed from the Options
menu, under Settings and the tab Directories.
½ To export a single file
The .prj file is used together
with the .tre files to transport 1. From the Outline View, choose the item to be exported.
controller software
2. From the File menu, choose Export, then Selected Item. The Export dialog
configurations to different
box displays.
versions of the toolbox that
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
½ To export the entire controller
with the Export All command,
which exports the required set w From the File menu, choose Export, then choose All. The Export All
of .tre and .prj files for the Options dialog box displays.
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 the
user is prompted
for a .tre file name
before this dialog
displays.
Working with Project Files

The project file also includes A project (.prj) file is a text file, which holds the names of all .tre files that go into 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. To prevent a file from being exported, or
dialog box. to lock a file with password protection, refer to the section Lock Function or
Software Library.
½ To create a project file
1. From the Outline View, choose the controller item.
2. From the File menu, choose Export and choose 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, choose a .prj file. This creates a controller and
order may be incorrect. To 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. Refer to the next
file, edit the file with any text section, Files in the .prj.
editor
Files in the .prj
½ To view a list of files included in the project
w From the Outline View, choose the controller name. Make sure Tracking is
Click Tracking on. 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, choose a function or macro and module library
2. From the Edit menu, choose 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, Lock Function or Software Library.)
Note This same No Export option can be applied to function files or macro and
module library files.
Locked Items
Use this dialog box to edit the items Function or Macro and Module Library
(Software Library), which are found in the Outline View of the toolbox.
Modify the function or
library name.
Enter the directory related

to the function or software
library. Click here to enter
a new password.
Check here, if the file is (Refer to the
not to be exported. section, Change
Password.)
Check here 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 in the above, the following dialog
box displays. You must enter the proper password to access the item you have
selected the edit.
Password Protection
When a function or macro/

module library has
passsword protection
enabled, a lock icon
displays beside the name.
Any attempts to edit or use The name of the

any item within a locked locked item you are
function or library requires attempting to open
you to enter the proper always displays in
password for this item. the dialog box.
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.
Anytime 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

w Using the right mouse button, click on the function or library name. The
following popup menu displays.
Choose Re-lock
½ To lock all unlocked items in all open devices

w Click anywhere in the Outline View.
From the Options

menu, choose
Logout User
Logout User clears the user ID and sets the privilege level to zero (refer to the
section, Privilege/Password in Chapter 3). It locks all libraries or functions (in all
open devices) that are in the temporarily unlocked state.
Change Password
1. From the Outline View, click on the Function or Library name.
2. From the Edit menu, choose Modify. The Edit dialog box displays.
3. Click . The following dialog box displays.
Enter old password.
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 executed 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
For more information, see 1. From the File menu, choose New. The Open dialog box displays.
Batch Operation, Chapter 6.
2. Choose Batch Build File and click OK. The Batch operations dialog box
displays.
The controller performs specific batch operations as follows:
• Place Signals puts the controller’s signal data into the database.
• Get Signals obtains other controller’s signal information from the database.
• Validate Device verifies the configuration to be 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 a .ucb 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 controller’s symbol information to the database.
• Download Symbols downloads the symbol file to flash memory.
Blockware Concepts
For more information on The controller software is made up of blocks that perform control logic. The
configuring each item, see the software is referred to as blockware. These blocks correspond to a function block
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 more complex collection of tasks that have a defined scheduling
relationship.
In the toolbox, block, macro and module parameters are called pins (from their
likeness to the pins of an integrated-circuit chip). All pins have a name unique to
For more information, see
their block, macro or module. Pins are connected by signals, which are the basic unit
Chapter 13, Signals and the
for variable information. Signals are created with signal definitions, module pins,
Database.
and macro pins or block pins.
Blocks and Block Pins
Standard library block names Blocks are the smallest programming element. They can perform functions such as
are preceded with an underscore math, solve an RLD, and perform a filter. They can also solve a Boolean equation.
( _ ), such as _CLAMP, to differ (These blocks can be compared to C-language functions, Pascal procedures or
them from macros and blocks in FORTRAN subroutines.) The product code blockware supports a function for each
the Industry block library. block that displays in the standard or Industry block libraries. For more information
about the individual blocks and how they work, see the toolbox’s 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 pins of the block from other blocks in the same task or macro, such as 20:OUT.
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 and contains well-defined inputs
and outputs. The user creates a macro by constructing a macro definition. If the
macro definition changes, add a version number.
Once the macro is defined, the user inserts the macro into a task or another macro.
The inserted macro’s internal blocks and connections cannot be changed. Macros can
be inserted in up to three levels as follows.
Macro pins have unique names and 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 has one macro pin designated as an enable pin. The
enable pin is a logical or Boolean signal that makes the macro’s execution possible.
Macros are shown in the following Outline View. The item, Macro Definitions is
located in 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 of 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.
This is because the libraries only contain code definitions, not code that is 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 more information on If a macro definition is changed, the inserted versions of the macro can be updated
instancing, see the section, by instancing the macro. Instancing a macro replaces all of the blocks and macros,
Instancing Module and and their connections inside the macro, but keeps the connections to the macro pins
Macro Pins. of the macro instance. Macros can only be instanced individually, if they are in a
Task (top level).
Tasks and Scheduling

For more information, refer A task must belong to a module. Tasks divide a module into items that require
to Chapter 5 of GEH-6410, different scheduling parameters. Each task has a period multiplier. The task period
Innovation Series Controller multiplier determines the rate of task execution by a binary multiple of the module
System Manual. base scheduling period. This can be 1, 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).
To equalize CPU loading, each task a has a skew offset that shifts its scheduling
position relative to other tasks without changing its execution frequency. The
possible values for skew offset varies between 0 and 7 as a function of the period
multiplier. The table below lists the possible combinations of skew and period
multiplier and the 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 Task B and TaskB comes before
TaskC. If all three tasks are scheduled with the same module period, period
multiplier, and skew offset, then 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, then 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 chosen 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, then 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
chosen for it.
Task Scan Periods at 5, 40, & 320 ms Module Base
Task Task Skew

PeriodMult Offset+Module
Skew Scan Period Slice 1 Slice 2 Slice 3 Slice 4 Slice 5 Slice 6 Slice 7 Slice 8
0* 0
1 0 5, 40 or 320 ms X X X X X X X X
2 0 10, 80, or 640 ms X X X X

2 1 10, 80, or 640 ms X X X X
4 0 20, 160, or 1280 ms X X

4 1 20, 160, or 1280 ms X X
4 2 20, 160, or 1280 ms X X
4 3 20, 160, or 1280 ms X X
8 0 40, 320, or 2560 ms X

8 1 40, 320, or 2560 ms X
8 2 40, 320, or 2560 ms X
8 3 40, 320, or 2560 ms X
8 4 40, 320, or 2560 ms X
8 5 40, 320, or 2560 ms X
8 6 40, 320, or 2560 ms X
8 7 40, 320, or 2560 ms X
* 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 of 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.
For more information, see the
section, Simulation System. 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 can
not 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. Note, however that all control blocks are written to use
absolute time. This means, for example, 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.
All of the external outputs referenced by the task are transferred from the signal table
to the I/O table at the end of the task execution. The I/O transfers can be over-ridden
by forcing or simulation. 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 stand’s module
instance has a different skew offset, so that all the code won’t 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
that is downloaded can be found in the Outline View, Function level, in the item
Modules.
Note There is not a Modules item in Macro and Module Library level. However
Modules Definitions can be defined there.
There are several types of modules:

• Instanced modules are defined in the item Module Definition under Function
or Macro and Module Library, 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 Function. They are not
meant to be reused.
• Over-ride modules are a combination of the instanced and inline modules. They
are created by instancing a module definition and then over-riding it from the
Module Edit dialog box. Over-riding a module allow 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 module’s 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 over-ridden in an instanced module,
module are discussed in the without actually overriding the entire module definition. This permits users to
section, Tasks and Scheduling. maintain the 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 re-
Function, see the section, 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 inter-
with a .tre file in that each related modules. All of 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
seperate .tre file. with a function, which allows the user 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 and I/O library describes 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.
The macro and module library .tre files have the same basic format as function .tre
files, except for the file descriptor at the beginning and there is no Modules item,
only Macro and Module Definitions. Macro and module libraries can be imported
again, as needed.
For block libraries, the .tre file must be imported and the runtime standard or
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. Refer to the section, Monitoring.
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
Blocks correspond to a function block that exists in the runtime. These blocks are
used to make up macros. Blocks and macros make up tasks. A task(s) can be
inserted into a module and any number of modules makes up a function. All of these
items are inserted into a configuration the same way. Refer to the section, Blockware
Concepts.
Create/delete Blockware
½ To insert blockware into a configuration
1. From the Outline View, click on a blockware item to highlight it.
Once an item exists, another item 2. From the Edit menu, choose Insert First.
can be inserted by following the
Or, click the right mouse button and choose Insert First. Depending on the
same steps, but choose Insert
item being configured, a dialog box 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 choosing the command.
½ To delete a block(s) from a configuration

1. From the Outline View, click on the desired item to highlight it.
Or click Delete
2. From the Edit menu, choose Delete.
Or, choose the Delete key.
Functions
A function acts as a grouping mechanism for inter-related modules. Function names
are limited to eight characters (see Function Names). Each function 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, choose Functions.
another function can be
2. From the Edit menu, choose Insert First.
inserted by following the
same steps, but choose Insert Or, click the right mouse button and choose Insert First. The Function
Next. Name dialog box displays. Enter a name, and click OK.
Function Name
Enter a name with up

to eight characters
and click OK.
This item is inserted
into the Outline View
(shown below).
Function items display in
the Outline View.
These items are described
in the following sections.
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 choose another controller name, instead of using the controller drop number.
½ To insert type definitions into a configuration
1. From the Outline View, click on Type Definitions to highlight it.
Or click the right mouse button 2. From the Edit menu, choose Insert First.
and choose Insert First.
The Type definition dialog box displays to define the data type.
Note Once a type definition exists, another can be inserted by following the same
steps, but choose 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
Or, from the Outline View, 1. From the Outline View, click on the type definition name to highlight it.
double-click on the type
2. From the Edit menu, choose Modify. The Type Definition dialog box
definition name.
displays.
Defining a Type Definition
Enter a name using up to 12
characters.
Enter a description with up to 50
characters, if desired.
Choose the basic data type,

which this type definition is based
upon (refer to the list below).
Type definitions are always
based upon another data type.
Choose 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, choose the
enumeration from the lit box,
change the value or description
and click Add.
- to remove, choose the
enumeration form the list box
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.4E + 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 type, except Boolean
Simple Includes all basic data types
String 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
1. From the File menu, choose Import.
Or click Import
2. From the Import dialog box, import the file Sysdata.tre.
3. From the Outline View, click on 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 System Information. If a scale needs
to be edited, System Information eliminates having to know which binary working
files to open.
½ To insert scale definitions into a configuration
Or, click the right mouse 1. From the Outline View, click on Scale definitions.
button and choose Insert
2. From the Edit menu, choose Insert First. The Scale definition dialog box
First.
displays.
This dialog box is also used to edit existing scale definitions.
½ To edit a scale definition
Or double-click on the scale 1. From the Outline View, click on the scale definition name to highlight it.
definition.
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).
Defining Scale Definition
Enter up to 12 characters for the

name. The Scale ID is automatically
assigned. If desired, enter a note
with up to 50 characters to describe
the scale definition.
Display Settings and Data Entry

Limits are used by the HMI
interface. Clamp Block Settings
are currently not used.
Alarm Settings are used by the

limit detection block to set outputs
corresponding to the different limits
and by the HMI system.
Conversion Settings are used to

convert signals when connected to
I/O points. Scales are posted to the
database to make this information
available. In addition, certain
standard blocks use the information
contained in the scale definitions.
These blocks have the data type,
Scale_A.
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 Function or Macro and Module Library.
Click on
Signal Definitions
2. From the Edit menu, choose Insert First. The Signal Definitions dialog box
displays (refer to the next section). This dialog box is used to define the signal
definition.
½ To edit a signal definition
Or, from the Outline View, 1. From the Outline View, click on the signal definition name to highlight it.
double-click on the signal
2. From the Edit menu, choose Modify. Edit the signal from the Signal
definition name.
Definitions dialog box.
For more information, see
Signal definitions also display when you update the database. When you put signal
Signals and the Database,
information into the database, three items, which hold lists of signals, are inserted
Chapter 13.
under the item System Data (in the Outline View):
Define Signal Definition
Enter the name of a signal with at least Choose a scale definition for this device. Choose
one and up to three regions followed by Custom to create a locally defined scale. Click
a signal name. Separate the region(s) Edit… to view predefined scales.
and name with a backslash, such as
reg1/signal_name. Region can be up to
six characters, and the signal name can
be up to 12 characters.
Enter a note with up to 50 characters to
describe the signal definition.
Type lists all the type definitions and

simple types for this device. Choose
Custom to create a locally defined data
type. Click Edit… to add the specific
information for that locally defined data
type.
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 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).
Connection allows you to connect signal

definitions to other signals. Enter the
name of the signal in the text box or
choose Browse… . When one signal is Enter the length of the signal, if it is an Array and the initial Value for
connected to another signal, they share the elements. If the Array size is greater than one, a list box of the
the same place in memory. initial values for the array elements displays above Value.
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
Once the item Table Definitions exists in the Outline View, import a .tre file using
the pop-up menu, as follows:
Use the right mouse

button and click on the
Table Definition name.
From this pop-up menu,

choose Import Table
Tree File.
Table definitions can be made more useful by exporting the 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 and click on the name of
Table Definition to be exported.
2. From the pop-up menu, choose 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
table’s name of the form region_region_region_signalname.csv.
Edit Dialog Box

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, click on the table definition name to highlight it.
– Or –
w Click on the table definition name with the right mouse button and choose
Modify from the pop-up menu.
Refer to the next two sections, Properties Tab and Initial Values Tab.
Properties Tab
The name of the table display
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

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 and as a tool to reuse blockware. There are three types of modules found
under the Modules item:
• Instanced modules and over-ride modules are defined in the item Module
Definitions of either a function or macro and module library.
• Inline modules are defined in the item Modules of a function.
Instanced and over-ride

modules are defined under
Module Definitions.
Inline modules are defined

under Modules.
Inserting 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 at a later
time. Module definitions are reusable and have a revision number to keep track of
changes to the modules.
Both configuration items are inserted using the same steps (described below). When
both are inserted, they contain another level item called Pins (refer to the section,
Pins). Also, on the same level as Pins, 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, click on Module Definition (found under the item
Function or Macro and Module Library) or Module (found under the item
Or, click the right mouse
Function).
First. 2. From the Edit menu, choose Insert First. The Module Definition Name or
New Module dialog box displays.
Naming the Module Definition
This dialog box is also used for
Macro Definition Name,
Module Pin Name,
Macro Pin Name and
Task Name.
Enter a name for the item you

are inserting. Click OK.
The name displays under the

item you are inserting in the
Outline View.
Naming the Module
Check this box to insert an

Choose an existing module definition. empty inline module and
define it later.
Enter a note for the module.
Enter a name with up to three regions

separated by backslashes.
(The pins, inserted under the item Pins,
use this same region as a full name.)
Edit Modules and Module Definitions

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, click on the name of the module or module definition
to highlight it.
Or, double-click the right
mouse button. 2. From the Edit menu, choose Modify. The Edit Module or Edit Module
Definition dialog box displays. The appropriate fields for the particular module
type are enabled, refer to the 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

Enter a description of the module.
Revision allows you to keep

track of changes to the
module 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??.??.???.
Enter a name for the Graphic

Window file associated with
this module. This is accessed
by choosing a module in the
Outline View, then choose the
Detached Summary View.
Select the module scheduling Select the module Check to change an instanced module to an over-ride
base period. The associated scheduling base skew. The module. An instanced module has a colon ( : ) between the
over-ride check box is only associated Over-ride check region names, such as reg\reg:module. The over-ride
enabled for instanced box is enabled only when module has an at symbol @, such as reg\reg@module.
modules. Check this box the module is instanced. The Over-ride checkbox can toggle to change an edited
makes the fields behave like module definition back to the original. Remove the X and
the connection of a module pin perform an instance. Any custom changes made to the
(the information of the module module when it was overridden is deleted.
instance is not replaced when
it is re-instanced).
Module Pins
Module pins are the parameters for a module. They are inserted under the item Pins.
(Pins is 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 Definition,
click on beside a module to display the item Pins.
Or, click the right mouse 2. Click on Pins to highlight it.

button and choose Insert 3. From the Edit menu, choose Insert First. The naming dialog box displays.
First.
4. Enter a name using up to 12 characters and beginning with an alphabetic
character. Refer to the section, Naming the Module Definition.
Naming the Module Pin

Module Pin Name,
Macro Pin Name and
Task Name.


Outline View.
Edit Module Pin

½ To define a module pin
1. From the Outline View, click on the name of the module pin to highlight it.
Or, double-click on the name 2. From the Edit menu, choose Modify. The Edit Module Pin dialog box
with the right mouse button. displays (refer to the section Module Pin Dialog Box).
Note For instanced pins, only the field, Connection is active.
Module Pin Dialog Box
This dialog box is used to edit both Module Pin and Macro Pin.
Enter a name with up to 12 Choose from a list of data types, made up Choose from a list of scales
characters (must begin with an from all of the type definitions and basic for this controller. Click
alphabet character). Module pins types for this controller. To create a locally Edit… to choose a
names do not include regions. The defined data type, choose Custom from predefined scale.
regions for signals associated with the drop-down list. Then click Edit…to To create a locally defined
module pins have the same region add the specific information for that locally scale, choose Custom from
as the module. defined data type. the drop-down list.
The text box below the name
allows you to enter up to 50
characters to describe the pin.
Choose how the pin is used in

the module from four possible
values: Input, Output, Local (not
intended to be used anywhere
outside of this module), and
State (read and write). Usage is
not verified during validation.
Visibility specifies the

conditions that the pins are
viewed on block flow diagrams.
Currently this field is not used for
module pins.
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 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). Array size and Value define the array length of the signal
(if it is an array) and the initial value for the elements. If the
Connection allows you to connect signal array length is greater than one, a list box of the initial
definitions to other signals. Enter the name of values for the array elements displays above the Value list
the signal in the text box or choose Browse… box (refer to above screen). To edit this box, click on a
to enter the signal. When one signal is value in the box and then enter a value in the Value list box
connected to another signal, they share the or choose from the drop-down list.
same place in memory.
Refer to the section, Modules Inserting and editing module pins is limited to module definitions, inline modules,
Definitions and Modules. and over-ride modules. Module pins are referenced in the module’s 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.
Note Only the pin connection, period, and skew of an instanced module can be
changed from the module definition. Also, the module definition notes are not copied
to the instanced module. An instance specific note can be added to the instanced
module.
Macro Definitions
Macros provide a way to re-use blockware on a lower level than modules. Macros
are only instanced and never inline or over-ride. 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, click on Macro Definitions.
Or, click the right mouse 2. From the Edit menu, choose Insert First. The MacroDef Name dialog box
button and choose Insert displays to name the macro definition.
First.
3. Enter a name using up to 12 characters. The name is inserted in the Outline
View under the item Macro Definitions.
Naming the Macro Definition

Module Pin Name,
Macro Pin Name and
Task Name.


Outline View.
To Edit a Macro Definition

½ To edit a macro definition
1. From the Outline View, click on the macro definition name to highlight it.
2. From the Edit menu, choose Modify. The Edit Macro Definition dialog box
displays.
Macro Definition Dialog Box
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
Edit the name that was created and the final A can be any alphabetic character. If the
in the MacroDef Name dialog format is entered incorrect, the toolbox replaces the
box. It must be not have more revision string with V??.??.???.
than 12 characters.
Enter a note to describe the

Macro Definition.
Enter the name of the pin that

enables the macro or choose
from a list of defined pins in the
drop-down list box.
Macro Pins
Module pins are the parameters for a module. They are inserted under the item Pins.
(Pins is automatically created when the item Module is inserted.)
½ To insert a pin into a Module
1. From the Outline View, under the item Macro Definition, click on
beside a module to display the item Pins.
2. Click on Pins to highlight it.
Or, click the right mouse 3. From the Edit menu, choose Insert First.
button and choose Insert 4. Enter a name using up to seven characters and beginning with an alphabetic
First. character. Refer to the section, Naming the Definition.
Naming the Macro Definition

Module Pin Name,
Macro Definition Name ,
Macro Pin Name and
Task Name.
This name displays under the

Outline View.

are inserting and click OK.
Edit Macro Pin
½ To define a macro pin
Or, double-click on the name 1. From the Outline View, click on the name of the module pin to highlight it.
with the right mouse button.
2. From the Edit menu, choose Modify. The Edit Macro Pin dialog box
displays (refer to the section, Macro Pin Dialog Box).
Note For instanced pins, only the field, Connection is active.
Macro Pin Dialog Box

Change the name that was created in the Macro Pin Name dialog box. It can
Choose from a list of data types, be up to seven characters long and must begin with an alphabetic character.
made up from all of the type Macro pins are not named with regions included.
definitions and basic types for this The text box below the name allows you to enter up to 50 characters to
controller. To create a locally describe the pin. Note: Sometimes this text box is used by MMI to describe
defined data type, choose Custom diagnostic messages.
from the drop-down list. Then click
Edit…to add the specific
information for that locally defined
data type.
Choose how the pin is used in the

macro from five possible values:
Input, Output, Local (not intended
to be used anywhere 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 and Local, Output
or State display on the right.
Visibility specifies the conditions

that the pins are viewed on block
flow diagrams. Always (pin is
always shown), Never (pin is never
shown), Used (pin is shown when
connected to anything ) and Wired
(pin is shown only if connected to
another signal). This option is not
always applicable (see the Option Array size and Value define the array length Enter the name of the signal,
menu, Block Diagram). of the signal (if it is an array) and the initial which the pin will be
value for the elements. If the array length is connected to or click
greater than one, a list box of the initial Browse… to choose from
values for the array elements displays above the Signal Selector dialog
the Value list box. To edit this box, click on a box.
value in the box and then enter a value in the
Value list box or choose from the drop-down
list.
Note For Used and Wired pins, if just a macro instance is selected in the Outline
For more information, see the View with tracking on, then the Summary View displays all pins regardless of their
section, Macros and Macro visibility status.
Pins.
Tasks
See the section, Task and Tasks are both the basic scheduling unit and a blockware grouping mechanism in the
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 Definition,
click on a module name to highlight it.
2. From the Edit menu, choose Insert First. The Task Name dialog box
Or, click the right mouse displays (refer to the section, Naming the Task).
First. 3. Enter a name with up to 12 characters and beginning with an alphabetic
character.
Naming the Task

Module Pin Name,
Macro Pin Name and
Task Name.


Outline View.
Edit a Task
½ To edit a task
Or, double-click the right mouse 1. From the Outline View, click on the task name to highlight it.
button.
2. From the Edit menu, choose Modify. The Edit Task dialog box displays (refer
to the section, Edit Task Dialog Box).
Edit Task Dialog Box

Enter a unique name with up
to 12 characters.
Enter a description of the task.
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 chosen as the Period
Multiplier.
Period Mult determines how

often a task runs. The period
multiplier times the module’s
period equals the period that
this task executes, which is
Event, 1, 2, 4, or 8. (Event
Enable option buttons choose a value for the task enable.
generates a multiplier of zero
Always makes the enable True.
and the task only runs if an
Never makes the enable False.
Event occurs).
Pin enables the drop-down list box to choose the names of this
module’s pins.
Signal changes the drop-down list box to displays the Signal
Selector dialog box to choose a signal.
Tip© When either Pin or Signal is chosen in the Enable options, a module pin or
signal name can also be typed in.
Enable or Disable Task
The following screen displays tasks in the Outline View and with Tracking on, how
the tasks can be display 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
1. Click to go online.
2. From the Outline View, double-click the task name. The Send Value dialog
box displays to enable or disable the task (refer to the next section).
3. Choose the desired value for the enable and click Send. The live enable value is
reflected, provided it is not being written to blockware.
Send Value
Enter the Value to Click Send.

enable or disable the
task execution. The live enable value
is reflected in the
Click this option to Summary View
prevent blockware (provided the task is
from overwritiing the not being set in
Value. blockware).
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
Or, click the right mouse 1. From the Outline View, click on a task name to highlight it.
2. From the Edit menu, choose Insert First. The Select Block/Macro Type
First.
3. From the list, Category, choose a block category, then choose a block from the
block library. (The center text block displays either the Library or the Function
name.)
Or, from the list Macros, choose a macro.
w Click OK or double-click on the block/macro. The item is inserted under Task
name.
½ To delete a block or macro from a configuration
1. From the Outline View, click on the desired item to highlight it.
Or click the Delete
2. From the Edit menu, choose Delete.
Or, choose 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

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.
Choose 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.
Choose 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. It can be scrolled down by clicking the box so that
the cursor displays in the note text and then use the Page Up/Page
Down or arrow keys.
Rubber Blocks
When a block in inserted, all of the pins of the block are included, except 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 may 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 that is a relay
ladder diagram (RLD). The RLD can have from 1 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 a Pin
For more information, see the To connect the pins of a block or macro use the Connect Block Pin dialog box or the
section, RLD Editor. Edit Block/Macro Connections dialog box. Boolean engine blocks can also be
connected using the Relay Ladder Diagram (RLD) editor, which is the default for
Boolean engine blocks.
½ To connect/edit a pin
1. From the Outline View, click on a block or macro to highlight it. The block
diagram displays in the Summary View.
2. From the Summary View, double-click on the desired pin. The Connect
Block Pin dialog box displays (refer to the next section, Connect Block Pin
Dialog Box).
Connect Block Pin Dialog Box
From: displays the selected block number and
pin name, the Type, and the Usage of the pin
being connected.
Enter the value this block or
instanced macro pin will be
connected to.
The following command buttons

select the pin connection. (The Pin
buttons all display the Pin Select
dialog box, described below.)
Signal displays the Signal
Selector dialog box to choose 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 Create Pin allows you to create a macro or module pin that is not in the Pin
a macro definition. It lists macro pins, Select list. It invokes the Edit Module Pin Definition dialog box with the name
which can be connected to this pin. and type preset to the values matching the current pin being connected.
Block Pin is always enabled. This Clicking OK in Edit Module Pin Definition creates a module pin if the block/
command provides a list of all the macro pin is in a Task or creates a macro pin if the block/macro pin is in a
possible block pins that are on the same Macro Definition.
level of blockware (either in the same
task or macro definition). The names The drop down list provides enumerated data types (including Boolean
display as block number, colon, pin variables). Inserting an enumeration in the To text box gives the pin an initial
name (100:IN). value. Initial values can also be connected to block and macro pins by
Inv places a tilde (~) in front of the pin. entering a valid numerical value for pins with a simple numerical data type or
A ~ placed before any signal, inverts the type definitions based on a numerical data type.
signal for the connection being made.
This command is only enabled for
Boolean pins.
Edit Block/Macro 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 choose another pin, the text is applied to the
pin.
½ To edit all pins in a block or macro
1. From the Outline View, click on the block or macro pin to highlight it. The
block diagram displays in the Summary View.
2. From the Summary View, double-click on 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 choose 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 choose 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 box Inv places a tilde (~) in front of the pin. A ~ placed
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, choose Boolean engine blocks can be connected differently than other blocks and macros.
Settings/Controller and click on These blocks perform logical operations on inputs to set the output to some value.
the option, Use 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 that are 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
Or from the Summary View, 1. From the Outline View, click on a Boolean block.
double-click the block name.
2. From the Edit menu, choose Modify. The RLD editor displays.
RLD Editor Toolbar Commands
Choose To
Starts 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 on a contact. The Connect Contact dialog box
displays.
Move a contact, click on the contact and drag-and-drop to the desired grid square.
Copy a contact, press and hold the Ctrl key, click on the contact, and drag and drop to the
desired grid square.
Delete a contact or line segment, click on 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 on 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.
Choose 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 enlarges or
reduces the RLD editor Work Area. If the Work Area is larger than the RLD window,
scroll bars display in order to access and view the entire workspace.
Renumbering, Renaming, and 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
½ To renumber a block(s)
1. From the Outline View, choose a block, or choose a group of blocks by
pressing and holding the Shift key as you click on the block names.
2. From the Edit menu, choose Renumber. The Renumber Block(s) dialog
box displays.
3. Enter the desired numbers and choose OK to apply the new numbers. If the new
numbers overlap with existing blocks, a dialog box displays to state the overlap.
Enter a new starting

number for the block or
block group. Enter the difference
between the new blocks
numbers. For example,
Start at 40 and Step by
10, produces the numbers
40, 50, 60, and so on.
Rename and Copy Blocks

Tasks, modules, and macro and module definitions can be cut-and-pasted. If a name
is repeated, the Rename dialog box, as 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 a 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 Chapter 3. ½ To choose block flow diagram viewing options
w Choose the Options menu, Settings, and then the tab Block Diagram.
These settings determine how the blocks display in the Summary View.
This view of blocks and how they are connected is generated by the toolbox. A
number of operations can be performed from this view as follows:
To From the Block Flow Diagram
Display the RLD editor Double-click on the Boolean engine block name
Display the Edit Block Connection dialog box Double-click on the block or macro name
Display the Connect Block Pin dialog box for Double-click the pin of a block
that pin
Highlight the connection of a pin to another pin Click the pin itself or the area adjacent to the pin name that is reserved
for the pin connection
Connect a module pin already connected to a Click on the module pin, drag-and-drop it on the pin to connect it to.
block pin
Tip © Instead of using the 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.
Instancing Module and Macro Pins
To instance a module or macro means to update the instance with a new definition.
Instancing occurs automatically whenever a function .tre file is imported.
½ To instance a single macro or module
1. From the Outline View, click on the macro or module to highlight it.
2. From the Edit menu, choose Instance.
3. Choose Selected to instance a single item.
Or, choose 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 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 the connections.
Connecting instanced macro pins ½ To edit the connection of a module pin
is described in the section,
w From the Outline View, double-click on the module pin name. The Edit
Blocks and Macros under
Module Pin dialog box displays.
Connect and Edit.
Connection is the only field that can be edited for an instanced module pin.
Connection is the
only field that can be
edited for an instanced
Module Pin.
Enter the name of the

signal, which the pin
will be connected to or
click Browse… to
choose from the
Signal Selector dialog
box.
Both macros and modules can be used to substitute specific portions of blockware at
instance time. This feature is called string substitution (refer to the next section).
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 drive’s 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 Module Pin Definition 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, they are 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 pin’s 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 information into the database/Get information from the 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 and a symbol table file for the configuration.
• Download sends configuration components to the controller.
Database Commands
For more information, see Put into database writes signal and topology information to the database. Get from
Chapter 13, Signals and the database reads other controller’s information from the database and includes it in
Database. 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, choose Put into Database or Get from Database.
available, verify the database
2. Choose Full to include all information or Incremental for specific
and server name entered in
information.
the Database options dialog
box, see Chapter 3.
The Put into database and Get from database commands allow controllers to 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 would
create and put the signal into the system database. The AcDcEx2000 would get the
signal information from the database for that signal. When the controller issues the
RUN command, the AcDcEx2000 would see the signal on its page and take 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
Get from Put into database without Put Topology into Put Symbols
Information database Topology (USDB only) Database into Database
DLAN+ Signals yes yes yes N/A

VME Signals yes N/A 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
Diagnostic Symbols
The toolbox can put diagnostic symbol information into the database. This is signal
information necessary to send a second diagnostic from the OC2000 or Human-
Machine Interface (HMI2000). In addition to signal names and descriptions, the
diagnostic block note is put into the database at the same time. This block
information is indexed according to the signal name on the status pin of the block.
The block information is used by the MM2000 as a second-level diagnostic message.
To put diagnostic symbol information into the database, choose Put Symbols into
Database from the Device menu.
Validating
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, click on an item(s) to highlight it.
Or click Validate
2. From the Device menu, choose Validate.
3. Choose All to validate the entire drive/controller or choose 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 on an error to go to the item in the configuration that was not validated.
Building 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
1. From the Device menu, choose Build. The Build options dialog box
Or click Build/Calc displays.
2. Enter the correct setting as follows. Click OK.
Build Options
Build application control code

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

symbolic table will write the
.sym file. Enter a file name in
the text box or click Browse…
to choose a .sym file already
created.
Note Errors sometimes occur during a build and like validation errors, the error
messages will 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, choose Open.
2. From the Files of type drop-down box, choose Pcode Files (*.pcd).
3. Choose 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.
4. Choose the desired records to include in the report.
5. Choose to view the Pcode Report or save the report to a .txt file.
Create Pcode Report Dialog Box
Click this option to display the

report in the toolbox window. Use
this option for short reports only
(writing to the window takes
much longer than writing to a file
and then viewing the file).
Click this option to write the

report to a file. Click Continue
(below) to name the file and save
as a Pcode Report text file (.txt).
Select 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 here to generate the report.

Click here to receive the entire Click here to clear all record type
.pcd file. boxes that are checked.
Software Setup
The following sections describe how to setup the software portion of the controller
for the first time.
Downloading is when a component of a configuration is sent to 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.
½ 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).
2. Cycle power to activate the new IP settings.
A soft reboot from the toolbox
is not sufficient. 3. From the toolbox, load the product code (runtime).
4. Then, load the application code (Pcode) and symbol files to permanent storage
only.
5. Cycle power again.
Note The remaining sections define each of these steps.
Serial Loader
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. It requires an
RS-232C serial cable, which can be ordered through your local GE authorized
distributor, as part number 336A3582P1. The cable specifications are as follows:
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.
Initializing the Flash

The Flash File System is loaded using the Serial Loader during installation of the
system.
½ To start the Serial Loader
1. From the Start menu, click 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 box.
Click the Serial Port

Settings button 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).
Configuring TCP/IP
Obtain the Computer Name, IP Address, Subnet Mask, Broadcast Mask, and Router
Click on in IP from your network administrator. Enter this data into the proper fields below:
the 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 by the IP software Choose to load or save
to route external network messages. these settings (.ssf file) 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. Then, click the Start Command(s) button.
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 Summary View double-click on the controller name. The
Properties dialog box displays.
From the tab General,

enter the IP address that
was configured by the
Serial Loader.
Select the Platform from

the drop-down box, such
as UCVBG1(which
displays on the extracter
tab of the controller
board itself).
Click OK.
3. Select the Device menu, Download, and Product Code (Runtime). The
Download File dialog box displays.
Some controller versions may

show two files, Runtime.dnl
or Select.dnl.
Runtime.dnl is an obsolete
download file that loads all of
the drivers and uses the most
flash memory.
4. Click Select.dnl and click Open. All possible files that can be downloaded
display in the following dialog box.
5. Click on to uncheck any feature not used by the controller (in order to
conserve flash space). The toolbox deletes the entire directory and then
downloads only the checked items. Click OK. The following message displays.
6. Select No. Do not reboot. Continue to load application code.
Application Code
After validating and building application code, it should be downloaded.
½ To download application code
Or click Download
1. From the Device menu, choose Download and Application Code.... The
Download Application Code dialog box displays.
2. The default screen display with all options checked. Click on Download to
memory to uncheck that option.
Click on this option box to

remove the check mark.
Do not download to
memory.
3. Click OK.
4. Wait until the red FLSH LED on the controller has turned off.
5. 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.
Modifying the 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 the user 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 and
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 controlller. 3. From the Device menu, select Download and then Download Application
Code.
4. Select the desired download option from the Download application code
dialog box.
Check here to replace the current running configuration with the new application code. Then,
select from Memory Download Mode:
Offline - Restart controller stops the controller execution before expanding and loading new
code. All contents are initialized. Use this mode when there is a major configuration change.
Downloads to Online - Init all constants replaces the running configuration without stopping for a fast
RAM download. Since all constants are initialized the process increases.
Online - Init only new constants replaces the running configuration without stopping for a
fast bumpless download.
Check here 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 or choose Browse...
Check here to download the

.sym file to permanent storage.
This changes the active
symbol table in the controller.
Enter the correct .sym file
name or choose Browse...
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 canceled.
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 indidcated 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 configuration
that is running, 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. Refer to the next
section, Major/Minor Differences.
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 all 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.
Upgrading the 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 File menu and Open, and select the existing
application code file (.m6b).
2. From the File menu, select Export All and select an option to export the
application code into its tree file (.tre) components and a project file (.prj).
3. Install the new controller product code using the setup utility.
Note If this is an Innovation Series controller and the ADLIB block library is used,
verify that it is compatible with the new product code or install a compatible version
now.
4. Select the Device menu, Download, and then Product code (Runtime).
Some controller versions may

show two files, Runtime.dnl
or Select.dnl.
Runtime.dnl is an obsolete
download file that loads all of
the drivers and uses the most
flash memory.
5. Click Select.dnl and click Open. All possible files that can be downloaded
display in the following dialog box.
6. Click on 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. Click OK. The following message displays.
7. Select No. Do not reboot.
8. From the File menu, select Close.
9. 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.
10. Select Validate and Build to create a new Pcode file (.pcd) from the
application code.
11. From the File menu, select Save.
12. From the Device menu, choose Download and Application Code.... The
Download Application Code dialog box displays.
13. Check Download to permanent storage and Download symbols.
14. Click OK.
15. Wait until the red FLSH LED on the controller has turned off.
16. Reboot the controller using the power switch.
Monitoring
Once a controller has been configure an download, 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 an executing controller).
½ To go online
w From the Device menu, choose Online. Online blockware information can be
Or click Go monitored from the Status bar and the Summary View.
online/offline
Status Bar
When online is initiated, it is indicated on the status bar in the lower right-hand
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 that are 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 module’s scheduling information. When monitoring live data, the task list also shows the
graphics window, see Chapter enable value and heartbeat, as shown below. When the toolbox is offline, the
16, 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, see the The Summary View (right side) for tasks, macro definitions, macros, blocks, and the
section, Block Flow Diagram. block items of a macro instance is called the block flow diagram. When a block or
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
w From the Summary View, double-click on the values. One of the following
dialog boxes displays.
Modify 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.
Modify Numerical 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.
Delta is the value to be added or

subtracted from the current value.
Token is the logical address of Click here to increment Click here to decrement
the signal. the Current value by the the Current value by the
Delta amount and send it Delta amount and send it
to the controller. to the controller.
Modify Array Value
Click on the
element to
change.
Click Modify.
The Boolean or
Numeric Send
Value dialog
displays with
this element.
Control Constant View

In the toolbox, a constant is a signal with an initial value that is read and never
written. Control constants are specific constants that a user might want to consider
separate from other constants because of their importance to key control algorithms.
A flag indicates the existence Users can flag signal and module definition pins that have this property. Once
or status of a particular flagged, constants can be viewed and compared as a group, exported to .csv files for
condition. manipulation outside of the toolbox, and merged back into the configuration.
Control Constant Work Area
½ To use the Control Constant View
1. Create or open a binary working file (.m6b).
2. From the View menu, choose Control Constants. A separate window
displays, called the Control Constant View. The following sections describe the
menu commands and work area specific to the Control Constant View.
File Menu
Close exits the Control Constant View.

Save/Save As preserves on open file. Save As prompts you for a new file name.
Merge 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 choose a printer and print connection.
Edit Menu
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
Online toggles the controller online/offline to view live data values and enables the
Save Values command.
Save Values obtains the live values displaying in the Control Constant View 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 View has two modes of operation, online and offline. The
offline view displays the Signal Name, Initial Value, Type, Scale, and Note for all
signals that are control constants.
½ To edit a control constant
w Double-click on a signal name. The Signal Edit dialog box for that signal
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
w Double-click on a signal name. The Send Value dialog box displays.
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 here to 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 Enteralso sends
the value and closes the dialog box.
Note In a control constant view, the live values can be saved to the configuration
online from the Device menu.
Application Documentation
The application documentation assists the user in understanding and maintaining
their system by providing online data, which can be printed. This documentation
contains block diagrams and reports. Block diagrams provide information about
controller blockware and reports contain information about signals and Pcode.
Block Diagrams
There are two types of block diagrams in the toolbox for a controller configuration.
The annotated block diagram provides a large amount of information, such as a
detail description of the block, a diagram including pin names and data type, and
application notes. The block flow diagram can help you debug and troubleshoot the
system. This diagram can be used in an online mode together with other diagnostic
features in the toolbox.
Annotated Diagrams
The annotated diagram provides formal documentation of the blockware. The
diagram can be generated at many levels ranging from top level Function items to an
individual task or macro.
½ To create an annotated diagram
1. From the Outline View, click the desired Function, Module, Task, or Macro
for the diagram.
2. From File menu, choose either Print (for a hard copy) or Print Preview (to
view from the screen).
The annotated diagram usually contains many items. Each function, module, module
definition, macro, macro definition, and task in the controller will be identified as an
item. An item can contain other items or blocks on a lower level. For example, an
item with other items could be a function or module. A block that has other items
would be a task or macro definition. The number of items in a diagram, depends on
the amount of code under the item, when selected from the Outline view.
Each item is assigned one or more sheets in the diagram. Each sheet has a unique
code for that particular item. The first page(s) of the diagram list all the items in the
If there are more than 26
diagram and their associated sheet codes. In each item the sheets are designated A to
sheets, the code will designate
Z. The sheet codes display in the bottom right-hand corner of each sheet and all have
them AA to ZZ.
the same structure as follows:
Code Meaning
02:01A Sheet A of the first module in the second function.
05:02:03B Sheet B of the third task in the second module in the fifth function.
02:04:08CD Sheet CD of the eighth task, the fourth module in the second function.
The Comment block can be An item containing blocks can be logically divided into smaller items with a
found in the block library, Comment block (__COMMENT). This block causes a break in the block diagram,
Sblib.tre. which functionally creates level items in the task or macro definition level. All
blocks in the item after the Comment block display on a different sheet. If a note is
placed on the Comment block, it displays at the top of the new sheet. The block itself
does not display in the diagram.
At the end of each of these lower levels are two lists:
The scope limit allows you to The signal definition list contains all the signals in the lower level. For each signal,
choose a range for the signal it lists the signal name, data type, default value, and description.
where used.
The where used list shows all locations in the configuration, within a scope limit,
where the signal in the signal definition list is referenced.
Where Used Scope

½ To set a scope limit
1. From the Options menu, choose Settings.
2. From the Settings dialog box, choose the tab Print (shown in the following
dialog box).
This option applies only to controllers. Specify the scope of

signal cross referencing in the block diagram that is active.
Choose the font for the text that

displays immediately over blocks
in the diagram. The default font is
Courier New.
Choose the font for the Signal

Definitions and Where Used Lists
at the end of each block sub-
section. The default font is
Courier New.
Choose the font for the text at the

top of each new section and block
sub-section. The default font is
Arial.
Choose the font for all text not

listed above, including block
names and pins. The font size
directly affects the number of
blocks that display on a page of
the diagram. The default font is
Arial Narrow.
Tip © Many of the default printer settings can be edited before printing, such as
page orientation, resolution, margins, and paper sources. The type of printer and
the version of printer driver(s) installed determine editing choices. For more
information, see your printer or printer driver manual.
Block Diagram
For more information, see the The block diagram can be captured and viewed (Summary View or the Detached
section, Block Flow Summary View ) or printed to a hard copy (paper) form. The diagram displays the
Diagram. item (task, macro, or macro definition) that is currently highlighted in the Outline
View.
½ To view a block flow diagram
1. From the Outline View, click on the desired item (in the hierarchy list) to
highlight it.
Or click to view the 2. View the diagram from the Summary View or choose Detached Summary
Detached Summary View. View from the Edit menu.
Or, from the File menu, choose Print Preview to view the diagram online or
Or click to print a hard choose 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 pages of
information into orderly the diagram are numbered in a row/column format. (This format makes it easy to
pages. assemble 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, choose Settings.
2. From the Settings dialog box, choose the tab Block Diagram (defined in the
following section).
Block Diagram Tab
Display the blocks in a list with

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

diagrams 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 options for

interconnected block diagrams:
Show all pins displays all block
pins. This command disregards
the text box Visibility, if it is
checked in the Edit Macro Pin
Definition dialog box.
Reorder pins rearranges the
pins to minimize crossing the
connections on the diagram.
Show inputor Show output
connections display the
connection names and values.
Font size changes the font size
of all text on the block diagram.
Change the Summary View tracking feature to display

various levels of the hierarchy, when they are chosen
in the Outline View. Choose 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. Three types of reports can
be generated for the controller:
• Signal List
• Signal Cross-reference
• Simulation Data
½ To generate a report
w From the View menu, choose Reports. Select Signal List, Signal Cross-
reference, or Simulation Data. 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, choose Find. The Report Find dialog box displays
to enter text and search the Report (defined in the following section).
Report Find
Enter the text you want to find

from the report. The found text
is highlighted in the report..
Enter new text or click Cancel.
Signal List
The Signal List report provides a list of all the signals in the controller. For every
signal, the report shows the signal name, the data type, and the token number.
Signals that are 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 the locations in the blockware
where named signals are used. Named signals are signals defined by the user,
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.
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, choose Report and Simulation Data. The Simulation
Output File dialog box displays.
2. Create or choose a file (.ucx) to hold the simulation data. Click Save.
The Simulation Report Options dialog box display (see the next section).
Simulation Report Options
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.
Application Diagnostics
This section describes the application diagnostics feature of the controller.
Application diagnostics inform the operator and/or maintenance engineer why an
action can’t be started, or why it stopped. Application diagnostics are generated from
the same code running the process, so that the user no longer needs to maintain
separate code. Diagnostics can be viewed through HMI programs (Diagnose and
DlanView).
Note For information concerning HMI, refer to the manual GEH-6372, GEMIS
Tools for CIMPLICITY. For OC2000 information, refer to Chapter 11 in this manual
and the section, Displaying Application Diagnostics.
Types of Application Diagnostics

The four character abbreviation There are four types of application diagnostics:
for the diagnostic type can be • triggered (TRGD)
used to filter the diagnostics
that display on the problem • broken run (RUND)
history screen.
• feedback (FDBK)
• sequence (SEQD)
Triggered (TRGD)
There are three types of triggered diagnostics, as follows:
• Start diagnostics are generated when an operator or piece of logic tries to
initiate an action that is not permitted. The start diagnostic indicates why the
action can’t be started. It lists either the permissives that aren’t 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.
Control code can be configured • Requested diagnostics are normally used when a process is going to be started
to generate diagnostics when up after a downturn. When diagnostics are requested no action is initiated.
operator or maintenance Therefore, the operator can actually request the status to correct problems before
personnel request them. it is time to start the process. Diagnostics requested over the diagnostic network
only display the logic with permissives that are not met (the operator does not
have to filter through I’m OK messages).
Note When diagnostics are requested specifically from a human-machine interface

(HMI) screen over Ethernet, a response is always sent back exclusively to the
requesting screen. This assures the operator that specifically needed to know the
diagnostic, 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
that is 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, then a feedback diagnostic is generated.
• When this control code successfully turned something on and then later loses its
feedback. For example, a piece of equipment is moved into position so that it
picked up a limit switch. At some point later in time, perhaps due to softening in
the hydraulic system, that piece of equipment moves off of 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 that is 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, then 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 was
actually initiating 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
shouldn’t 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 that are 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 and 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 to
trace permissives that are not met. 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, then passline 1 permissives must be met. If passline 2 equipment
is used, then 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
which drives in passline 1 (from rung 140) are not healthy. All the detailed
permissives for passline 2 that are 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, then a feedback diagnostic is generated. A time that is 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, then 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, then 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 turned 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 five control blocks that either directly generate diagnostics or supply
information used in the diagnostics generated. They are BENG_D, BENG, PENG,
SFB, and MERGE.
These blocks that directly generate diagnostics have two pins in common:
dispgrp (display group) pin is a 3-character abbreviation for the function that 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, then 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.
In order 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 it’s 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.
PENG
The PENG (permissive engine) generates the following diagnostics:
• When the PENG receives a request to turn on, it checks to make sure it’s start
and run permissives are satisfied. If they are satisfied, it initiates the desired
action. If the permissives are not satisfied, it generates a triggered diagnostic
that lists the missing permissives.
• Next the PENG checks that the feedback goes high within the expected period
of time. If it has not initiated within this time, it generates a feedback diagnostic.
Chapter 5 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 Appendix A).
Section Page
Using the Finder....................................................................................................... 5-1

Finder Window ........................................................................................................ 5-2
Target Finds ............................................................................................................. 5-3
Using the Finder

½ To use the Finder
1. From the View menu, choose Finder. The Finder window displays.
Or click on .
2. Choose a target from the drop-down Target List. (All loaded targets are listed.
The default target is the current device.)
3. Choose 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 on any part of the screen outside the Finder Window. Click to keep the
Finder open.
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 5 Finder • 5-1

Finder Window
Title bar Target list
Toolbar
Tabs To resize the window:

1. Click on the window
to highlight it.
2. Point the mouse
arrow on any side of the
window until the double
arrow displays.
3. Click on the arrow
and drag-and-drop the
window to the desired
size.
Output View
Status bar
The Finder target determines the device and area of the search. When the Finder is
activated, it automatically chooses the current device as the target and displays it in
the Title bar. A target performs various finds, as follows:
Target Can find
SDB Signals
OC2000 Text
AcDcEx2000 Text, variable usage, override, difference

Innovation Series drive Text
Innovation Series and Mark VI Text, signal usage

controller and System Information
Located below the Title bar is the toolbar, as described below.

Click To
Hold the Finder Window open. If this pushpin displays, the Window closes when the area outside the
Finder Window is clicked. Click on 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 on. 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 on an item to edit it.
Hide the tabs and make the Finder window display only the Output View.
5-2 • Chapter 5 Finder GEH-6403A Toolbox for a Mark VI Turbine Controller

Target Finds
The Finder contains tabs that display according to the device chosen in the drop-
down box, Target List and the tab chosen (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
Appendix A. available on all targets, except the SDB. The Signals/Variables 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 displays 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 on an item to search.
2. From the toolbar, click on . The Finder displays to begin your search.
Choose the desired tab as described in the following sections.
Text/Address
Choose the target from the drop-down list
(can be any target except the SDB).
Enter the text to find.

(wildcards such as * and ? are
not supported). the drop-down
list box allows you to access
previous finds.
Click here to include all note

message boxes in the find.
Click the Find button to start

the find.
All text that is found displays

in the Output View.
Status bar
Method allows you to qualify the find by choosing 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 whose text is exactly as the find text.
Address is for the AcDcEx2000 and matches items whose 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
Choose the target from the drop-down list.

Click this button to keep the
Finder window displayed in the
Choose the tab, Signal/Variable Usage.
Outline View.
The Track Highlighted

Item box is already
checked. This means
that the current
highlighted item in the
Outline View is the
signal/variable to find.
The signal/variable
items that are found
display in the Output
View.
INC is the current

highlighted item.
Note When a different item is chosen 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.

Overrides
Overrides apply to The Override tab displays only when the target is an AcDcEx2000 device. An
AcDcEx2000 only. override is a change in an EE location or a parameter value different from the
calculated software made from within the toolbox. Find an override(s) by choosing
the tab, Overrides. The tab displays two additional buttons on the toolbar as follows:
Click To
Clear any chosen overrides.
Clear all overrides in the Output View.
Click this button to keep Choose the target from the drop-down
the Finder window list (must be an AcDcEx device).
displayed in the Outline Choose the Overrides tab.
View.
Choose the type of

override(s) to find. Click
on the option box EE,,
Hardware, and
Parameters. Click again
to turn the option box off.
Click the Find button

to start the find. The match displays in
the Output View.
Status bar

Differences
Differences apply to The Differences tab displays only when the target is an AcDcEx2000 device.
AcDcEx2000 only. Differences are EE locations that are not the same as the calculated values in the
database. Find a difference(s) by choosing the tab, Differences. The Differences tab
displays two additional buttons on the toolbar as follows:
Click To
Verify selected hardware differences and send selected EE differences
to the device.
Send or verify all differences displayed in the Output View, as

appropriate.
Click this button to keep Choose the target from the drop-down
the Finder window list (must be an AcDcEx device).
displayed in the Outline Choose the tab Differences.
View.
Choose the type of

differences to find. Click
on the option box EE, and
Hardware . Click again to
turn the option box off.
Click the Find button The match displays in

to start the find. the Output View.

Chapter 6 Batch Operations
Introduction
This chapter describes the Batch Operation mode. Batch Operations perform a
variety of operations, 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 .............................................................................................. 6-1

Configuring A Batch Operation............................................................................... 6-2
Running a Batch Operations File ............................................................................. 6-3
Open/Save Batch Operations File ............................................................................ 6-4
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
w From the File menu, choose New.
Or choose the New
button
Choose the tab Utilities.
Click Batch Build File

and OK.
The Batch Operaitons

GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 6 Batch Operations • 6-1
Batch Operations Dialog Box
The dialog box commands are as follows:
File Names is a list of the files upon which the
operations are performed. The files are opened in
the order shown in the list. Use the edit buttons to
modify current positions and start the operation.
Add inserts the name of a

file in the File Name list.
Remove takes the
highlighted name(s) off the
File Name list.
Move Up moves a single
file up in the File Name list.
Move Down moves a
single file down in the File
Name list.
Change allows you to edit
the highlighted file name.
Save preserves the current
batch operation to a .bld.
Start executes the batch
operation.
Close exits the current
batch operation dialog box.
Stop on errors allows you to

stop the batch operation when
an error occurs.
Click here to advance the

batch operation to the next file
Check the boxes to select the operations that will be name instead of the next
performed on the file name(s) in the list. The operation for the current file,
operations are executed in the order shown, top to when an error is encountered.
bottom and then left to right. If more than one file
name is highlighted, the operations to be added to
those files will only be the operations checked while
the files are highlighted.
Configuring A Batch Operation

½ To add to the File Name list
w From the Batch Operations dialog box, click on the Add… button. The Add
File dialog box displays.
Enter the name to add
to the File Names: list,
or click Browse… to
choose a file from the
Batch Binary Files
dialog box.
Check this option if

the .prj file is an
AcDcEx.
6-2 • Chapter 6 Batch Operations GEH-6403A Toolbox for a Mark VI Turbine Controller
For more information, refer Tip © If you are using the Checkin/Checkout utility, make sure all files added to
to Checkin/Checkout in the Files Names list are checked out, in Exclusive (read/write) mode. Otherwise,
Chapter 7. operations may not work and not be found until the Error Log file is examined.
½ To configure a batch operation

1. From the Batch Build dialog box, edit any Files Name(s) with the command
buttons, Move Up, Move Down and Change.
2. Choose all operations to be performed on each file.
3. Choose an Error option.
4. Click Save to save the Batch Operation to a .bld file.
5. Click Start to run the Batch Operation.
Running a Batch Operations File

Run a Batch Operations file by choosing the Start button from the Batch Operations
dialog box or from a Disk Operating System (DOS) command line and batch file
(.bat). Use the command line option to do multiple operations on many devices
without user interactions.
To run the toolbox at the DOS command line, 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. For example:
C:\TOOLBOX\TOOLBOX.EXE
C:\TOOLBOX\project_dir\device.bld -r
Also, two command line options are available:
• Type -r to indicate that the batch should run immediately and not wait until the
Start button is pressed.
• In an AcDcEx2000, type -u_ _ _ (3 character User I.D.) so that the Enter −
User I.D. dialog box will not display before each file is opened.
The build file will not be found by the toolbox unless:
• The path is explicitly specified in the command line, or
• The toolbox was previously run on the PC, and the default directory where the
build file resides was specified in the Options menu, under Settings, the tab
Directory, and the text box Default Project.
Running a batch file from the command line works the same as the toolbox
interactive mode, except that the user is never prompted. The toolbox opens, runs,
and completes the Error log. The Error log (.log) can be viewed from a text editor.
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 6 Batch Operations • 6-3
Batch Error Log File
When a Batch Operation runs, an Error log window displays all error messages
produced during the run. This log is written to a file with the same name as the .bld
file and the extension .log. The file is written for each device, so if something
happens, such as a power loss, only the Error log information for the interrupted
device is lost. The file also indicates the overall success of the Batch Operation by
displaying a message that either there were errors or there were no errors.
Open/Save Batch Operations File

A .bld file contains a File Names (including directories) list, operations, and Error
list. To save a .bld file, press the Save button on the Batch Operations dialog box and
enter a name in the Save dialog box.
It is sometimes useful to also have a .txt file with the same list of File Names as in
the .bld file. This .txt file can be read in a text editor or added to the Batch Operation
dialog box.
½ To open an existing .bld file
w From the File menu, choose Open. Choose the desired file name and directory.
½ To create a .txt batch file
w After saving the Batch Operations as a .bld file, save it again using the same
filename and the extension .txt. The first line of the .txt is
Batch_File_List to indicate that the text file can be read by the toolbox.
Then, the File Names are listed, as shown below.
Batch_File_List
D:/TOOLBOX/BATCHLIST/NAME1.UCB
C:/UC2000/BATCHLIST/NAME.UCB
½ To add a .txt batch file to Batch Operations
1. From the Batch Operations dialog box, click on the Add button.
2. Click Browse…and choose the .txt file. The list of files below the line,
Batch_File_List displays the File Name list.
6-4 • Chapter 6 Batch Operations GEH-6403A Toolbox for a Mark VI Turbine Controller
Chapter 7 File Checkin/Checkout
Introduction
This chapter describes the Checkin/Checkout utility, which allows users to share
files contained in a master directory. 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, choose a directory to maintain the Master files.
2. Copy all desired files into this Master directory.
3. From the Program Manager, double-click on the Checkin/Checkout icon.
The Checkin/Checkout Utility dialog box is displayed.
4. Choose 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 choose 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-6403A Toolbox for a Mark VI Turbine Controller Chapter 7 File Checkin/Checkout • 7-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.
7-2 • Chapter 7 File Checkin/Checkout GEH-6403A Toolbox for a Mark VI Turbine Controller
Chapter 8 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, and broadcast alarm messages.
Once the configuration for System Information is defined, the data is put into the
System Database (SDB). This makes the global data available to other drives,
controllers, and interfaces.
Section Page
Working with System Information Files.................................................................. 8-1

Concepts .................................................................................................................. 8-1
Configuration ........................................................................................................... 8-3
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 that is global to a project. This information includes Scale Definitions,
and Resource Names (Type Definitions). System Information puts this information
into the database to make it available to other devices.
GEH-6403A Toolbox for a Mark VI Controller Chapter 8 Configuring System Information • 8-1
Scale Definitions
Refer to the section, Defining Scale definitions are scale factors associated with signals. They are used primarily
Scale Definitions. to scale raw I/O into engineering units used internally by the blockware in a
controller or CIMPLICITY HMI system.
The scale definitions put into the database by System Information are additional to
any scale definitions that other devices put into the database. The ownership of scale
definitions is maintained in the database.
Broadcast Alarms
Broadcast alarms are not Broadcast Alarms are text messages with variable substitutions that a controller can
kept in a queue inside the broadcast onto the diagnostic network (under specific circumstances). The alarms
controller. To distinguish are defined in System Information and then put into the SDB. This allows any
them from alarms that are controller in the system to use the same alarms from the database. The CIMPLICITY
queued, Broadcast alarm HMI system also obtains the alarm definitions through the SDB Utility program.
messages are referred to as
The Mark VI controller is configured to send a broadcast alarm message by coding
Event messages in turbine
an ALARM_XMIT block. For example, the ALARM_XMIT block requires
systems.
parameters that specify which alarm is to be sent (Hydraulic temperature (105 ° C) is
too high), and under what circumstances (when the temperature exceeds 100 ° C).
Once the controller is coded, it is built and downloaded. When the controller detects
that the hydraulic oil is greater than 100 ° C, it broadcasts the appropriate alarm
message on the diagnostic network.
Note Broadcast alarms do not apply to the Mark VI controller. Refer to the section,
Configuring Alarms in Chapter 4.
Type Definitions (Resource)

Any signal that is put into the database can be associated with one resource name
(just like a signal can be associated with a scale definition). This Resource name
groups signals used by the CIMPLICITY HMI system. The resource can be used as a
filter for displaying alarm/event data on a CIMPLICITY HMI.
System Information defines and puts Resource names into the database. This makes
the Resource names available to other devices to assign Resource names to
appropriate signals before putting into the database.
8-2 • Chapter 8 Configuring System Information GEH-6403A Toolbox for a Mark VI Controller
Configuration
Creating/Modifying System Information

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

1. From the Outline View, click on the name to highlight it.
Or double-click on the name. 2. From the Edit menu, choose Modify. The System Device Name dialog box
displays.
Modifying Name
Enter a new name using no

more than five characters.
Click OK.
Inserting 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. If a scale
needs to be edited, System Information eliminates having to know which binary
working files (.syb) to open.
½ To insert scale definitions into a configuration

1. From the Outline View, click on Scale Definitions.
Or use the shortcut keys, 2. From the Edit menu, choose Insert First.
Shift + Insert.
Or, click the right mouse button and choose Insert First. The Scale
definition dialog box displays.
The Scale definition dialog box is also used to modify existing scale definitions.
½ To modify a scale definition
Or double-click on the scale 1. From the Outline View, click on the scale definition name to highlight it.
definition.
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, a locally defined scale cannot be put into the database.
Defining Scale Definition

Enter up to 12 characters for the
name. The Scale ID is automatically
assigned. If desired, enter a note
with up to 50 characters to describe
the scale definition.
Display Settings and Data Entry

Limits are used by the HMI
interface. Clamp Block Settings
are currently not used.
Alarm Settings are used by the

limit detection block to set outputs
corresponding to the different limits
and by the HMI system.
Conversion Settings are used to

convert signals when connected to
I/O points. Scales are posted to the
database to make this information
available. In addition, certain
standard blocks use the information
contained in the scale definitions.
These blocks have the data type,
Scale_A.
Inserting DLAN+ Groups
DLAN+ groups are defined and configured in the Outline View under the item
Network Names for Network Groups, shown below.
Before a network group can be defined, the network for the network group must be
inserted.
Inserting/Modifying Networks
½ To insert a network
1. From the Outline View, click on Network Names for Network Groups to
highlight it.
2. From the Edit menu, choose Insert First. The network item displays in the
Or click the right mouse Outline View with the default name DFLT. This name can be changed as
button and choose Insert follows.
First.
½ To modify the default network name
1. Click on the item DFLT to highlight it.
Or double-click on DFLT. 2. From the Edit menu, choose Modify. The Network Name dialog box
displays.
Modifying Network Name
Enter a new name using no

more than five characters.
Click OK.
After a network name is modified, the item Network Groups can be inserted and
configured.
Inserting/Modifying Network Groups
½ To insert a network group name
1. From the Outline View, click on the network name that this network group
will belong to.
2. From the Edit menu, choose Insert First. A Network Group item displays
Or click the right mouse under the network name with a default name, GRPa. This name can be changed
button and choose Insert by modifying the network group name.
First.
½ To modify the network group name
1. Click on the item GRPa to highlight it.
Or double-click on GRPa. 2. From the Edit menu, choose Modify. The Network Group dialog box
displays.
3. Modify the fields as desired and click OK. Validation is performed.
Modifying Network Group

Enter a new name
using no more than
five characters.
Choose FIXED or
DYNAMIC.
Choose 1 to 31 for
DYNAMIC and 33 to
255 for FIXED.
You may enter a

description of the
network group.
(50-character limit.)
Inserting Resources
Resources are defined as type definitions. For information on inserting general type
defintions, refer to Chapter 4 and the section, Type Definitions. The Resource type
definition allows the 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.
ASCII string (1 to 255 Resource is always of Basic Data type: String. When Resource names are first
characters). Strings must be defined, it is not necessary to assign a Value to the Value name (refer to the
an array whose length equals Resource Name Values dialog box). This is done automatically when System
the maximum number of Information puts the data into the database. For example, the following list displays
characters + 1 for the a set of resources entered without a value.
terminating zero.
After System Information puts its configuration into the SDB, values for each
resource name are assigned automatically by the database, as follows:
Defining Resource Name Values
Values for each

Resource name
are assigned
automatically by
the database.
DEFAULT (50)
PASSLINE2 (51)
PASSLINE1 (52)
EXIT (53)
PROCESS (54)
ENTRY (55)
Notes
Chapter 9 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 create
the graphic objects and then add animation and input data to the process.
Section Page
Graphics Window Objects ....................................................................................... 9-1

Settings .................................................................................................................... 9-6
Draw Commands ..................................................................................................... 9-9
Animating Objects ................................................................................................. 9-11
Input Fields ............................................................................................................ 9-22
Using Graphics Window Objects........................................................................... 9-26
Graphics Window Objects

Drawing objects can be attached to the following animation type(s) for displaying
data:
Object Animation produced
Line Color
Rectangle Bar graph, Trend, and Color
Circle Color
Ellipse Color
Polygon Color
Polyline Color
Text Numeric, Text, and Color
All drawing objects can produce the following input type(s) for entering data:
• Numeric
• Set point
• Initial value
• Toggle
• Text
• Hyperlinks
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 9 Graphics Window • 9-1
Create Graphics Window
½ To create a Graphics Window
The Graphics Window 1. From the File menu, choose New. The New dialog box displays.
displays as a detached view
2. Click on the tab Utilities, click Graphics Window and OK. The Graphics
that can be moved and sized.
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 choosing the Draw menu
graphics_.grw can be and Device.
changed when it is saved.
This dialog box lists all
open devices. Click on the
desired device for this
graphic and 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 are different from the regular toolbox
as the toolbox. menus and are described in the following sections.
9-2 • Chapter 9 Graphics Window GEH-6403A Toolbox for a Mark VI Turbine Controller
Edit Menu
The Edit menu allows you to modify graphic objects, and select animated and input
objects with the following commands:
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
Or click Pull Forward sends the selected object(s) in front of other overlapping 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.
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 four toolbars: Main, Drawing, Animation, and Input.
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.
Draw Menu
The Draw menu allows you to draw with the following commands.
Select is used to choose an object(s). Click on the object or press and hold the
Or click mouse button to 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 following commands 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 Picture inserts a windows metafile (.wmf) into the graphics file.
Or click
Device allows you to choose the device for this graphic file (refer to the section,
Select Device).
Online connects the Graphics Window to the device over the network.
Or click
Animate Menu
The Animation menu allows you to apply signal information to objects with the
following commands.
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
Or click signal.
Input Menu
The Input menu allows you to draw objects and backgrounds with the following
commands.
Numeric is used to enter numerical data into a signal.

Or click
Setpoint is used to set a signal to an assigned value.
Or click
Initial Value makes the current signal value the initial signal value for all the
Or click signals specified.
Or click Text selects a text string to define the value sent to the signal.
Or click Toggle is used to invert a signal from 0 to 1 or 1 to 0 (toggles state True/False).
Or click Hyperlink... is used to open 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 allows you to set the X and Y size of the current screen. No objects can
be drawn outside the frame.
Pen Color sets the current pen color. This color is used for drawing the lines in all
Or click 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).
Brush Color sets the current brush color and fills all objects used with the brush
Or click command (also the background color for text).
Use Brush is a toggle command used to fill rectangles, circles, ellipses, and
Or click polygons with the color chosen in Brush Color.
Text Font selects the current font to use when drawing text.
Or click
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 of the toolbox, click on 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.
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
Frame Size allows you to set the X and Y values to determine the size of the
Graphics Window. No objects can be created outside the frame.
½ To set the frame size
w From the Settings menu, choose Frame Size.
Enter the X and Y values.

The integers must be
between 30 and 10000.
Click OK. The Graphics

Window displays in the
new size.
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 choose a pen color
1. From the Settings menu, choose Pen Color.
Or click
2. Click on the desired color.
– Or –
w Create a custom color by clicking on one of the custom color squares, and click
on the button Define Custom Colors>>.
½ To choose a pen width
w From the Settings menu, choose Pen Width.
Or click
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 chosen.
Objects that can be filled include rectangles, circles, ellipses, polygons, and text
and off by clicking . background. The color can be the same color 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 choose a brush color
1. From the Settings menu, choose Brush Color.
Or click
2. Click on the desired color.
– Or –
w Create a custom color by clicking on one of the custom color squares, and click
on the button Define Custom Colors>>.
½ To fill an object with color
A check mark (áUse Brush) 1. From the Settings menu, choose Use Brush.
displays beside the command
2. From the Draw menu, choose the desired object. The object will be filled with
when it is active.
the color chosen in Brush Color.
Text Font
Text Font allows you to choose 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 choose a font
w From the Settings menu, choose Text Font. The Font dialog box displays.
Or click
Choose a Font, Font

style, and Size.
That 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.
Draw Commands
All images 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
themselves defined by a set of points.
½ To create an object
1. From the Draw menu, choose 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 chosen in Pen
Graphics Window Objects. Color and filled with the settings chosen in Brush Color. Text is created using the
currently chosen font, color, and brush.
Draw Commands
From the Then,

Draw menu
Or click. . . click and hold the left mouse button,
choose. . .
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).
* The Use Brush command must be chosen in order to fill an object with the color chosen 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, choose Select. Or click .

2. Click on the object or draw a box around the object. Handles appear around the
edges of the object to highlight it.
Once the object is highlighted, it can be edited several ways as follows:
• Choose a new setting, such as Pen Color or Text Font.
• Click on a handle and hold the mouse button to drag and resize the object.
• Click on the middle of an object and hold down the mouse button to drag-and-
drop and move the entire object.
½ To select multiple objects
Or, choose multiple objects
by pressing the control key 1. Click to select the draw tool and draw a box around all the desired objects.
while clicking on the objects. The box must include all portions of all objects. All selected objects will have
handles.
2. Click . A group outline box appears around the entire group.

3. To resize the object, click on a handle (curser changes to Ø), press and hold the
mouse button to drag-and-resize.
Or, to move the entire object, click on the edge of an object between the handles
(the curser changes to ), and press and hold the mouse button to drag-and-
drop.
Insert Picture
The Insert Picture command allows you to insert a custom graphic that was 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.
½ 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 on the rectangle to select it.
Or click 3. From the Draw menu, choose Insert Picture.
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.
Animating Objects
Animated objects display signal information. There are five types of animation that
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.
½ To animate an object
1. From the Graphics Window, click on the object.
2. From the Animation menu, choose the type of animation for that object (as
described above). The animation dialog box for that type of animation displays.
3. Click on Value Return and choose a Return (value) for this object (refer to the
next section, Value and Enable Return).
4. Click on Enable Return and choose a Return (value) for this object (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 button. The following dialog box
displays with six different returns (described in the following sections). Each
animation must choose a Return.
Signal
The Signal Value Return produces a value from a signal chosen 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.

signal value to obtain.
Use 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

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.
Return#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.
Default value: is returned if none of
Check to attach the the following comparisons are true.
will not exist.
Compare Type: can be

Off, Equal, Not Equal, or
Greater Than.
Compare group: 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

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.
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.
Click to attach and detach animation Value Return allows you to

to the object. enter the value for the
A checked box contains animation. animation.
Note: If you detach (unchecked) this Specify the direction of the bar from the
option and click OK, the animation is Enable Return uses the value low limit to the high limit.
deleted unless you previously saved of a supplied signal to enable Specify how the bar is drawn.
the .grw file. the animation. 0 = disable Unidirectional starts the bar at the low
value and draws toward the high value.
Bi-directional 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
Rate defines how fast Select the color for the normally displayed in the
the signal data is background of the bar standard colors unless an
collected. graph. alarm limit is exceeded.
Trend
Trend animation displays the recent records of up to eight signals on a trend graph. It
must be attached to a rectangle object.
Pixels per Sample uses the number of pixels in the text box for
each data sample. When the number is increased, the graph
Click to attach and detach animation to the object. widens and less time is covered.
A checked box contains animation. Samples per Pixel uses the number of data samples in the box
Note: If you detach (uncheck) this option and click OK, the for each pixel on the graph. When the number is increased, the
animation is deleted unless you previously saved the .grw file. graph becomes narrower and more time is covered.
Define how fast the signal data

is collected for the animation.
Controls how many grid lines
Displays the total amount of are drawn in the horizontal
time covered by the Trend and vertical direction. One
graph using the size of the grid line is always drawn in
graph, Rate, and Pixels per the center on the graph
Sample/Samples per Pixel. (always given an odd
number of horizontal grid
Samples after Disable lines). Enter the color to
controls how many samples are draw the grid lines.
collected after the Enable
signal goes False. A zero Select the graph line to
means the trend will stop assign and view signal
immediately. Time displays the information and line
amount of time corresponding attributes.
to the Samples after Disable.
Select the the background color
of the trend graph.
Determine the direction the Define the text colors for the
rectangle is drawn from. (If left corresponding alarm limits.
is selected, the trend starts at Off does not use the alarm
the left of the rectangle and limit.
drawn toward to the right.) On uses the value text box
as the alarm limit.
Enable Return uses the value Auto uses the alarm limit
of a supplied signal to enable defined in the scale data for
the animation. 0 = disable the signal. The number is
Define the Enable and Disable normally displayed in the
colors that display in the top standard colors unless an
corner of the trend as a block. alarm limit is exceeded.
Define the size of the block to
display.
Enter the value used by this signal on the trend.
Specify the signal values that correspond to the top and
bottom of the trend graph. If the auto box 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.

contains animation.
animation.

0 = disable

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.
Next and Previous
buttons scroll through all
the possible values.
Note Brush (fill) colors only apply if the object is drawn with the Use Brush setting
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.

contains animation.
animation.

0 = disable

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. The Next and
Previous buttons scroll
through all the possible
values.
Note Brush colors (fill) only apply if the object is drawn with the Use Brush setting
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. Create an object in the Graphics Window.
2. Click on the object to highlight it.
3. Choose the Input menu and choose an input to assign to the object or click on
the Input button.
½ To edit an input value
w Double-click the left mouse button on the input object. The assigned input
dialog box displays to edit.
Tip © To choose an object, click (the button highlights) or choose Select from
the Draw menu (Select will have a á symbol beside it).
Numeric
The numeric input field enters numerical data into a signal in the controller from the
object selected in the Graphics Window.
Check to attach the

Uncheck to detach the
signal.

signal value to obtain.
Use 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/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.

Use 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 here to display the Send Set point
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.
Use 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 choose 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 input field).

Browse… can be used to find a signal if a device is
already selected.
A list of all the text strings displayed in the Select
Text Value dialog box displays. The strings are in
double quotes, followed by a dash, and the value
that is sent to the signal ("Stop" - 0). (They are
displayed in the same order as this list box.)
Edit the list box as follows:
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 entry.
Modify allows you to change the selected entry.
The Select Text dialog box displays when the Graphics

window is online and a text input object is selected.
Choose the appropriate text string.
Click OK to send the corresponding value to the signal
in the device or 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.
Check to attach the input field
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 click

Cancel exit .
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. Click on an object to select it.
Or click
2. From the Input menu, choose Hyperlink.
Hyperlink Dialog Box

Enter the Command Line (Launched Program), Launches Program creates a hyperlink that runs a file type
Filename (Toolbox), or Help File (Help) to external to Toolbox, such as spreadsheets and drawings. It
execute an application or to open a file. also allows hyperlinks to execute DOS command lines
Substitution characters are also supported in this including processing switch parameters.
field to replace any part or all of a path, such as
c:\%2\work.xls. These characters must be Open ToolBox File creates a hyperlink that opens only toolbox
defined in a controller, the Graphics Window file types, such as Trend Recorders (.trd) and Graphics
default Substitution list, or the Hyperlink Windows (.grw).
Substitution list.
Open Help File creates a hyperlink that runs the Windows
Check to attach the hyperlink to the object and Help engine and opens the help file.
uncheck to detach.
Help ID jumps to a particular

section of the Help file specified
in the path.
Display as Pop-up displays the

Help file in a small pop-up
window. If this box is not
checked (default), the Help file
displays as a main window.
Click to display the Edit

Hyperlink Substitutions
dialog box and enter signal
substitutions specific to this
hyperlink. These signal
substitutions function as the
controller substitutions, except
that the 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. Then, the associated application that opens the file will 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 Signal’s Numeric Value

½ To display a signal’s numeric value
1. From the Draw menu, choose Text.
2. Click on the drawing area where the numeric value will display. A character-
Enter text here . sized box with a cursor displays.
3. Type the text that will display in the Graphics Window while offline.
Select object. 4. From the Draw menu, choose Select or click .

5. Click on the text that was entered. A dotted line surrounds the text object.
6. From the Animation menu, choose Numeric. The Numeric Animation
Or click
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.
9. Enter the signal name or Browse… for signals in the current device.
10. Click OK to complete the signal, and click OK to complete the animation.
11. Place the device online to view the live values.
Click to go online.
Create a Signal Trend

½ To create a signal trend
1. From the Draw menu, choose Rectangle.
Or click
2. Draw a rectangle. (Click on 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.)
3. From the Draw menu, choose Select.
Or click 4. Click on the rectangle that was drawn. Handles display on the corners and the
middle of the rectangle to indicate that the rectangle was selected.
5. From the Animation menu, choose Trend. The Trend Animation dialog
Or click 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. Click OK.
8. Click OK to complete the signal.
9. Verify the high and low limits for the value and change if necessary.
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, choose Bar Graph. The Bargraph dialog box
displays.
3. Verify the high and low limits for the value and change, if necessary.
4. Verify the direction and change, if necessary.
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.
2. From the Input menu, choose Numeric. The Input Numeric dialog box
Or click displays.
3. Enter the signal name to be modified and click OK.

4. From the Draw menu, choose 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 eleven characters.
½ To create signal substitutions
1. From Edit menu, choose 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.
String Substitutions
The Graphics Window supports string substitution module pins as supported by the
Innovation Series controller. The substitutions specified by these pins have a higher
priority than those defined in the Graphics Window. When a module’s 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. And, a module in a controller has defined two
substitution pins, SUB1 and SUB7, which reference specific signals. When the user
The purpose of Online selects a module’s Detached Summary View from the toolbox, first the default
Substitutions is to serve as a signals load into Online Substitutions. Next, the substitution of module SUB1
clipboard for signals that are overwrites the online substitution %1, while the substitution of SUB7 overwrites the
used by the Graphics Window empty online substitution %7. It is important to remember that only the online
while connected to a substitution is overwritten, not the default signals saved with the Graphics Window.
controller. The defaults are permanent unless modified by the user.
½ To view signal substitutions
w From the toolbox, while in the Graphics Window, choose 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).
Chapter 10 Hardware and I/O
Introduction
This chapter defines the controller networks and 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 ..................................................................................... 10-1

Mark VI I/O ........................................................................................................... 10-5
DLAN+ Interface................................................................................................. 10-18
EGD Interface ...................................................................................................... 10-27
Genius Networks.................................................................................................. 10-33
Main Board .......................................................................................................... 10-54
Register Network ................................................................................................. 10-58
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 the Outline View
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.
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 10 Hardware and I/O • 10-1
The following items can be inserted in the Outline View of the toolbox, under
Hardware and I/O Definitions:
Available I/O or
Network Interface DS215UCVBG1 DS215UCVBG3 IS215UCVCH1 IS215UCVCH3 IS215UCVCH5
A-B Data Highway Plus á (1) á (1) á (1) á (1) á (1)
Arcnet DLAN+ Networks á (1) á (2) á (1)
Ethernet Global Data (EGD) á á á á á
Ethernet Modbus á á á á á
Ethernet SRTP á á á á á
Mark VI VME I/O á á á á á
Main Board (NVRAM) á á á á á
Genius I/O Networks á (1) á (2) á (1) á (2) á (2)
Serial Modbus Networks á (1) á (1) á (1) á (1) á (1)
(1) – one network interface supported

(2) – two network interfaces supported
I/O Points
Points are the inputs and outputs (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, which transfer data from the input points to their signals
at the beginning of 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
10-2 • Chapter 10 Hardware and I/O GEH-6403A Toolbox for a Mark VI Turbine Controller
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.
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.
In order for I/O and network items to be inserted, the correct platform must be
selected from the controller properties.
½ To edit controller properties
w From the Outline View, double-click on the controller name. The controller
Device Properties dialog box displays.
From the tab General,

choose the Platform
drop-down box, and
choose the correct
controller.
Click OK.
Now, the I/O or
network interface can
be inserted in the
Outline View, under
the item Hardware and
I/O Definitions.
½ To insert I/O or network interface

Or click the right mouse 1. From the Outline View, click on Hardware and I/O Definitions.
2. From the Edit menu, choose Insert First. The New I/O or Network
First.
Interface dialog box displays.
The items that display in this

dialog box depend upon the
product selected in the
controller properties shown
above.
Click on an I/O or network

item and click OK.
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.
½ To insert Mark VI I/O
1. From the Outline View, click on Hardware and I/O Definitions.
Choose 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 on the item, Mark VI I/O to highlight it.
2. From the Edit menu, choose Insert First. The Choose a rack dialog box
displays.
Choose one of the racks
and click OK.
The Mark VI Rack dialog

box displays.
Rack Types
Choose the rack type (refer to the

descriptions below).
If Simplex or Triad is chosen, select

the Channel also .
Choose a unique rack number .
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 on 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 on the TMR rack in the Outline View (Rack 1 The Summary View displays a
A TMR rack displays four in this example) to view all the channels at the graphic of each rack and all the
lines in the Outline View, same time in the Summary View. boards they contain.
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 on 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 on 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 on a rack to highlight it.
2. From the Edit menu, choose Insert Board. Refer to the next section, Choose
an I/O Board.
Choose I/O Board
Choose a board and

click OK.
The Mark VI Board

Enter the slot number

that the board will occupy
in the rack and click OK.
If the selected board has

several terminal board
configurations available,
the Terminal Boards
Choose the terminal

boards that will be used
with the VME board
selected above and click
on the check boxes.
Click OK.
Configuring Boards in the Outline View
In the Outline View, a board item, such as Slot 1: VCMI (shown below) can contain
configuration items under its hierarchy, as follows:
Configuration represents
configuration data that applies
to the whole board.
Card Points contain I/O points
that are not directly associated
with a terminal board.
Internal Variables represent
internal variables on the board
that can be viewed or modified.
(Signals can be attached to I/O
points, but not internal
variables.)
Modify these items by clicking +

to expand it.
Click on an item name with

the right mouse button and
choose Modify from the pop-
up menu.
Refer to the following sections

for more information on each
configuration item.
Note Other configurable item include regulators (see the section, Calibrate
Process), terminal boards (such as J3:IS200TSVOGA1), and monitors.
Configuration Node
Depending on what item is

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

when configuring points under the
item Card Points.)
Point Configuration
A point can have configuration associated with it and be modified by choosing the
Edit menu and Modify. (Refer to the section, Configuration Node.)
The board, VTCC contains a

terminal board connected to
jumpers J3 and J4, called
IS200TBTCG1A.
The point, ThermCpl3 contains

configuration, which can be
modified.
Attaching a Signal to a Point

Points found under configuration items such as, Card Point or a terminal board can
be attached to a signal using the Point Edit dialog box.
½ To attach a signal to a point
1. Expand the configuration item and click on a point.
2. From the Edit menu, choose Modify . The Point Edit dialog box displays.
Enter the name of the signal or

click Browse… to search for an
available signal.
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.
Modifying Internal Variables
The value of internal variables can only be modified when the toolbox is online with
the controller.
½ To modify the value of an internal variable
1. Click on the variable to highlight it.
2. From the Edit menu, choose Modify . The Modify Internal Variable dialog
box displays.
For Boolean variables, choose

True or False.
For float variables, enter the

value.
Click Send to initiate the change.
Downloading Board Configuration

All of the configuration items within a board can be downloaded for one board, a
whole rack, or all of the racks.
Or use the right mouse to ½ To download board configuration
click on the item to download.
1. Click on the item to download.
Choose Download from the
pop-up menu. 2. From the Config menu, choose Download.
Regulators
The Regulator node displays in the Outline View when the VSVO board is inserted
into the configuration (refer to the section Insert I/O Board). Expand the board items
and click on Regulators.
Use the right mouse button and

click on Regulators.
Choose Insert First from the pop-

up dialog box.
Regulator 1 is inserted.
Calibrate Process
Up to four regulators, which are automatically numbered consistently, can be added
to a configuration. Calibrate the regulators as follows:
Double-click on a
Regulator.
If the controller is not

online, the following
Click Yes to go online to

calibrate the regulator.
The LVDT/R Calibration

dialog box displays. Click No and the toolbox allows you to select
to view Constants(refer to the section, LVDT/R
x 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 Calibrate Position Offset tune-up
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 (shown in
parenthesis) 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

values from the board.
The values are saved in the

toolbox and downloaded with a
new sequence number.
Dynamic Signals are Verification commands are as follows:

available while online and
this dialog box displays. Click Off to turn off the Verification Mode.
These signals are supplied
with voted live data through Click Manual to enter a value in the text box.
the controller.
Click Send Manual to send the value enter in the text box 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.
Tip © If the calibrate permissive is not set, all command buttons are grayed out.
The calibration permissive is driven by controller blockware. The output point is
CalibEnabx where x is the selected regulator. Find this point in the controller 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 Calibrate Mode, all of 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, the user receives a message from any of the
requested commands that is not completed. For example, in a TMR operation, if the
Calibrate Mode was requested for all three channels (R, S, and T) and only the R and
S channels are available, then the user is notified that the T channel would not go
into Calibrate Mode. Other commands, such as Min End Pos, Max End Pos also
respond with a message if the requested state was not entered.
In Calibration Mode, the user can step through the calibrate process by selecting
each button in the field, Calibrate Sequence. Each command button, such as Min
End Pos, sends a message to the board requesting it to enter that command state. A
message box displays if any of the channels do not enter the requested state. Also, if
the requested state is achieved by all appropriate systems, the button stays depressed.
If there is a problem, the command 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).
Verification Process
Verification is found on the Calibration dialog box, just under the field Calibrate
Sequence. During the verification process, you can send a Manual value to the board
and inspect the movement of the actuator.
From the LVDT/R Click these buttons to start
Calibration dialog box, click the Trend Recorder and view
Manual. the actuator position
Enter a value in the text box feedback by stepping the
and click Send Manual. This current value, or view
causes a message to be current feedback by stepping
sent to the appropriate board the actuator position value.
with this value.
After the verification process, the Trend Recorder is activated with the necessary
signals for displaying a trend (refer to the section Trend Recorder). Select the
Constants View button to view predefined internal constants in the board.
After the calibration and verification process is complete, save the calculated values
by selecting the Save button. The values are saved in the toolbox and downloaded
with a new sequence number. When the calibration process is complete, select the
Close button.
LVDT/R Calibration Constants Dialog Box
To view the predefined Position Gain (Pos1Gain) and Position Offset (Pos1Offset)
tune-up constants stored in the board, click Constants View. The constants that
display depend on the LVDT selected in the configuration.
This dialog box is modal

to the Calibration dialog
box and must must be
closed before it can
return to the toolbox
application.
Click Close.
Sequence of Events
There are a number of Mark VI boards capable of utilizing sequence of events. In the
example below, the board is a VCCC board. It has a number of contact inputs, which
have events defined.
Validate and build are If a contact input has an event defined and this input is initiated, a message displays
commands in the Device on a defined Cimplicity screen. After the Mark VI is validated and built, a file with
menu of the toolbox. the extension .soe is created and placed on the user’s hard drive in the same
directory as the Pcode file (.pcd ). The .soe file contains the associations between the
sequence of event drop number for this point and its signal name. The file is used in
the system so the event transition can display correctly in the HMI system.
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,
a message is sent to the board to begin the trend. Trending samples are taken at 32
ms. The time scale, x-axis, for the 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.
DLAN+ Interface
DLAN+ uses an ARCNET The Drive Local Area Network (DLAN+) is a control network for the controller. The
token-ring LAN as the protocol over DLAN+ is Status_S. It can send directed, group, or broadcast
physical and data-link layer messages. Devices share data through Status_S pages. They make the addresses of
of the network. the points on the pages known to other controllers through the system database
(SDB).
½ To insert a DLAN+ Interface
For controller properties, 1. From the Outline View, click Hardware and I/O Definitions. You must
right mouse click on the have the correct platform/product selected in the properties dialog box.
controller name and choose
Modify.
Choose DLAN+
and click OK.
DLAN+ displays in the

Outline View.
Modify DLAN+
½ To edit the DLAN+
Or double-click on this w From the Outline View, click on DLAN+ Interface to highlight it.
DLAN+ Interface item.
From the Edit menu, choose Modify. The Edit DLAN+ dialog box displays
(refer to the following section).
Edit DLAN+ Dialog Box
A default name is assigned when DLAN+ is inserted. In the Check here to eliminate the
USDB, the network name exists in the database and is set by feedback points in the Pcode
getting the data from the database. For the SDB, put the records, so they are not
controller name into the database to make it available to other transferred from the signal
controllers (refer to the SDB Browser in the View menu). (variable) to the point. (This
procedure does not stop this
controller from reading in
other controllers’ feedback
signals. It only keeps this
controller from broadcasting
its own feedback.)
Check here to eliminate the

command points associated
with the network in the Pcode
records, so they are not
transmitted.
Check here to block

command re-transmissions
from the controller. Without
this disable command, the
commands are transmitted
three times to ensure their
arrival.
Check here to enable the

controller to act as the
master time keeper for this
DLAN+. All other nodes on
the DLAN+ can synchronize
The ARCNET node number (1 to 240) for this controller on this network their internal clock to the time
(must match the board DIP switch setting). Enter the value 0, and the next master.
available drop # is assigned when it is put into the database. Refer to the
manual, GEH-6371, Unit Controller 2000/VME, Operation and Maintenance.
Enter a description of the network in the Note text box.
Note It is necessary to build and download Pcode for the changes to take effect.
This procedure is useful if the controller wants to monitor other controllers without
affecting this system.
Status_S Pages
Status_S pages provide a way to share live signals (variables) over DLAN+. These
pages are periodically broadcast by the owner using Status_S shared RAM update
messages, known as feedback messages. The broadcast occurs every 320
milliseconds, unless the controller adjusts the broadcast period to some other value.
Devices can update their copy of the page. To save bandwidth, only the blocks of a
page that have changed are broadcast in the feedback messages. To ensure that
controllers coming online are properly initialized, all feeddback pages are broadcast
entirely every five seconds.
A controller can also use the SS_ONE_DEST block to send a command message to
change the contents of another controller’s page. Command messages are sent
immediately when a command block executes and provides a close coupling between
controllers.
The controller’s Status_S page is 256 words (512 bytes) long and is addressed on
word boundaries. Boolean points are packed 16 to a word, and the bit number that
describes which one ranges from 0 to 15. A controller can own up to 16 pages,
although the limit is five by convention.
Command and feedbacks can exist on the same page. Commands are frequently used
as references set by another controller, whereas feedbacks convey status information
to other controllers.
Once the DLAN+ Interface is inserted, the Status_S pages owned by the controller
can be inserted. In USDB systems, pages are assigned to each controller by the
LynxOS importer. In SDB systems, pages owned by the controller must be inserted.
Insert Status_S Pages

½ To insert a Status_S page
Or, click the right mouse 1. From the Outline View, click on the DLAN+ item to highlight it.
First.
The item Pg1 is inserted under the DLAN+ Interface item. The default name of
the page is Page# (where # is the number of pages owned by this controller).
Note Once a page exists, another item can be inserted by following the same steps,
but choose Insert Next.
DLAN+
Status_S page
These pages are sometimes referred to as internal pages in the toolbox, and pages
owned by other controllers are called external pages. Internal pages can be modified
using the Internal Page Settings dialog box (see the next section, Internal Pages).
Status_S Internal Pages

½ To modify a Status_S internal page
Or double-click on the page. 1. From the Outline View, click on an internal page to highlight it.
2. From the Edit menu, choose Modify. The Internal Page Settings dialog
box displays (refer to next section, Internal Page Settings).
Internal Page Settings
Enter the Status_S page name Dialect is the name of the
using up to five characters. Status_S dialect or template
Enter the DLAN+ page number applied to this page.
(1 to 255) or enter 0 for the next Port # is the relative page
available number from the number within the owner
database. controller. Modifications to the
Period is the time between Status_S page are shown by
Status_S feedback transmissions this number.
on the DLAN+ in milliseconds. Version is the current version
The default is 320 ms. number of the controller (major
Identification # is the USDB and minor), such as 0.1. The
identification number. Enter the major number 0 increases
desired number or enter 0 for the whenever the page number
next available number from the changes or the page is
database. compressed. The minor
Note allows you enter up to 50 number 1 increases when a
characters to describe this page. point is added or deleted,
changes address, changes
data type, or changes from a
Sort by signal name rearranges feedback to a command. The
the list of DLAN+ points in the version number is monitored
Outline and Summary Views and by other controllers in the
sorts by signal (variable) name. system. It is checked for
Sort by point name rearranges consistency between the page
the list of DLAN+ signals in the being broadcast by the owner
Outline and Summary Views and and the user’s copy.
sorts by point name. %Free is the amount of page
memory remaining.
%Allocated is the amount of
page memory assigned.
%Lost is the amount of
memory lost by deleting
Compress Page reclaims all Click to keep the memory Click to allow the memory signals in the page and not
lost memory. location of points with signals location of points with compressing.
(variables) on the page. signals to change.
Added points are placed in the next logical memory location (next available word
offset and bit number). This means Boolean points are bit-packed into words that
have other bits. Numeric data types are given as many words as it needs to support
that point. Whenever a point is deleted from a page, that space is not reclaimed, and
only controllers needing a particular addition to the page need to get information
from the database to find out the location of the variable on the page. This loss of
memory can be seen in the field, % Lost. To reclaim this lost space, compress the
page. The following Warning displays:
Status_S External Pages
The exchange healthy is Status_S external pages have one built-in diagnostic mechanism called page healthy.
mapped to the link presence The exchange healthy for a controller is True whenever messages are being received
to provide an interface from that controller. When the page healthy for a controller is True, feedback
similar to DLAN+. messages are being received from that controller. When the health of a variable
connected exclusively to a Status_S point is used in blockware, then the page healthy
is actually the value used.
When the controller gets information from the database, page zero is inserted into the
network and is called LINK. This page holds a list of signals called link presence
bits, which are set whenever a Status_S message is received from a controller. If no
messages arrive for a controller within 4 times the exchange period, 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\LINK_OK, where NET is the name
of the network and DEV is the name of the controller.
External pages cannot be ½ To sort pages or view properties of a Status_S external page
modified; they can only be
1. Click on an external page to highlight it.
viewed and sorted.
2. From the Edit menu, choose Modify. The External Page Settings dialog
box displays.
3. Review the external page setting (refer to the next section).
External Page Settings

Dialect is the name of the
Status_S dialect or template
The Status_S page name can be applied to this page.
up to five characters. Port # is the relative page
The DLAN+ page number can be number within the owner
(1 to 255). controller. Modifications to the
Period is the time between Status_S page are shown by
Status_S feedback transmissions this number.
on the DLAN+ in milliseconds. Version is the current version
The default is 320 ms. number of the controller (major
Identification # is the USDB and minor), such as 0.1. The
identification number. major number 0 increases
whenever the page number
changes or the page is
compressed. The minor number
Sort by signal name rearranges
1 increases when a point is
the list of DLAN+ points in the
added or deleted, changes
Outline and Summary Views and
address, changes data type, or
sorts by signal (variable) name.
changes from a feedback to a
Sort by point name rearranges
command. The version number
the list of DLAN+ signals in the
is monitored by other controllers
Outline and Summary Views and
in the system. It is checked for
sorts by point name.
consistency between the page
being broadcast by the owner
and the user’s copy.
Note Most External Page Settings are read-only and cannot be edited.
Internal/External Page Summary View
½ To view DLAN+ page data
w From the Outline View, click on a page name. (The default name, Pg1, Pg2,
Click (monitor online) and such can be modified.)
and the second column, Value
displays the live data value The Summary View displays columns of data, such as value, point name, direction,
for the page. and data type.
Tip © To sort the data in each column (alpha and numeric), click once on the
column heading.
Click and hold at the column

Click on a column Click online to
separation, then drag-and-drop
heading to sort view live values
to modify the column size
Click on a
DLAN+ page to
view data in the
Summary View
Status_S Points
Status_S pages are made up of points, which are associated with controller signals.
Each point corresponds to a complete signal, regardless of the length or amount of
memory that the point occupies in the Status_S page. The name has the form
Point.WORD.BIT, where WORD is the 16-bit word offset into the page and BIT is
the bit number, which ranges from 0–15 (15 is the most significant bit).
Note A point can only be inserted into an internal page.
½ To insert a point
1. From the Outline View, click on the Status_S page to highlight it.
Or use the shortcut keys, Shift 2. From the Edit menu, choose Insert First.
+ Insert
Or, click the right mouse button and choose Insert First. The Edit Point
dialog box displays. Refer to the next section, Status_S Point Edit, for the dialog
box description. This same dialog box is used to modify a point.
½ To modify a point
Or double-click on the point. 1. From the Outline View, click on the point.
Status_S Point Edit

Choose a data_ type from the drop-down list of
Direction can be Feedback, data types supported by the DLAN+ page. These
Command, or Event for an choices are different from the basic controller
Internal page (described below). data types and are described below.
Name is assigned by
the toolbox, which is
Point.WORD.BIT.
Enter the name of the Provides a detailed

signal associated with explanation of the
this point. This name hardware associated
must be provided to with a Genius point. To
create a point. access the descriptor,
Browse… allows you to the Genius point must
choose the signal using be mapped to a
the Signal Selector Status_S point.
dialog box.
This button displays the
The address entries Signal Edit dialog box.
specify the location of It is only active when
this point. If no value is the point is being
entered, the next inserted.
available address is
assigned.
Word specifies the
location in the Status_S
page. Enter a number Health Word specifies
Bit is the bit of the Health Bit is the bit Check this option to lock the word
between 0 and 255. the location of the
Word, when the number of the offset and bit numbers. However,
point is of type bit. health when the health health mentioned changes to data types that require that
It is between 0 and of a signal is desired above. the point be moved in memory
15. for a Status_S point. disregard this attribute and you are
asked to confirm the change.
Feedback and Command Data Types

Bit 1-bit value
Byte 8-bit signed byte
Ubyte 8-bit unsigned byte
Int 16-bit integer
Uint 16-bit unsigned integer
Lint Long (32 bits) integer
Ulint Long unsigned integer
Float 32-bit floating-point number
Refresh Bit (command data type only) This command bit is updated periodically
by the controller sending the command message to set it. Under normal operations
the bit is reset in the last update message. If the periodic update message is not
received after 1.28 seconds, the bit is reset automatically. This fail-safe mechanism is
useful for operations that should stop if someone is not actively telling it to go.
Directions for Internal Points
For more information on Feedback points are broadcast periodically when they change.
command and feedback
Command points are broadcast with feedbacks. They can only be modified in
points, see the section,
blockware using the controller command block _SS_ONE_DEST or_OUT_XFER, or
Status_S Pages.
by other controllers that send command messages.
For more information on Event bits operate like command points except that the bit in the Status_S memory
event bits, see the section, does not change. The signal that is connected to the event bit is set for one scan of
Tasks and Scheduling. the tasks, in which it is used and then reset. If the signal is also connected to an event
module pin, the task runs when the event bit is set.
Tip © Status_S points can also be created from the Outline View by dragging a
signal definition from another page and dropping it onto the desired page. This point
data type is compatible with the data type of the signal being dropped. The direction
is assumed to be a feedback, which can be modified. Once the point is inserted into
the new page, the point data type can be modified in the Internal Point Settings
dialog box.
Point Summary View
When the Status_S point is highlighted in the Outline View, the Summary View
displays a single point, its data type and direction, and the associated signal and
scaling information (if the signal has a scale). 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 following screen.
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 that uses that signal must be enabled for
an I/O transfer to run and copy the point value into the signal value, or vice versa.
From the Outline View, click on a point. 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 on 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 on the actual point, signal, or scale.
The appropriate Edit dialog box displays.
½ To modify/force a point or signal value
3. From the Summary View, double-click on the actual point value or signal
value. The appropriate edit dialog box displays.
Point in Point - Scale - Signal

Outline View in Summary View
EGD Interface
Ethernet Global Data (EGD) is a control network, as well as a protocol for the Mark
VI controller. EGD uses Ethernet as the physical and data-link layer of the network.
It can send directed or broadcast messages. Devices share data through EGD
Addresses of the points on the exchanges (pages).
exchanges are made known to
other controllers through the Note Exchange is a CIMPLICITY term, which means the same as the term page in
SDB. the toolbox. Exchanges provide a way to share live signals (variables) over Ethernet.
½ To insert the EGD Interface network

2. From the File menu, choose Insert First. The New I/O or Network Interface
3. Choose 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 IP address. To edit
the settings, refer to the next section, Edit EGD.
Edit EGD
The dialog box displays a default name (EGD1), number (0) and IP address.
A default name is assigned when the EGD
is inserted. For the SDB, put the controller
name into the database to make it
available to other controllers (Refer to the
SDB Browser in the View menu).
Number is also found in the database. If

the Value is chosen, this number is
assigned when it is put into the database.
ProducerID default s to the IP address/IP

name, or enter a unique IP address/name.
Refer to the IP address in the Device
Properties dialog box (by double-clicking
on the device name).
Enter a note to describe the network with

up to 50 characters. Click OK and the
network displays in the Outline View under
the item Hardware and I/O Definitions.
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,
unless you adjust the broadcast period to some other value not less than 10
milliseconds and in 10 millisecond intervals. An exchange can be a maximum of
1400 bytes long and is addressed on byte boundaries. Boolean points are packed 8 to
a byte, and the bit number that describes which one ranges from 0 to 7. 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 on the EGD network name to highlight it.
Or, click the right mouse 2. From the Edit menu, choose Insert First.
The item Exch1 is inserted under the item, EGD network. The default name of
First.
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 choose 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 on a exchange to highlight it.
Or double-click on the 2. From the Edit menu, choose Modify. The Internal Exchange Settings
exchange. dialog box displays. Modify the settings (described in the next section).
Internal Exchange Settings
Enter a name using up to five
characters.
Enter a number, 1 to 255, or enter 0

for the device to be posted to the SDB
and the next available number is
obtained from the SDB.
Enter the time between EGD feedback

transmissions on the Ethernet in
milliseconds. The default is 320 ms.
Enter a note to describe the exchange
with up to 50 characters.
Enter the dotted IP address of the

device to direct the exchange.
Click Broadcast to send the exchange
to everyone on the network.
% Allocated is the percentage of

exchange memory that is allocated.
% Free is the percentage of exchange
memory remaining.
% Lost is the amount of memory that is
lost by deleting signals in the exchange
and not compressing.
CfigSig - Configuration Signature is the
current version number of the controller.
It notifies users of modifications to the
exchange, which are monitored by other
Click to keep the Click to unlock all signals Click to reclaim all
controllers in the system. The number is
memory location of and allow the memory lost memory.
checked for consistency between the
points with signals on location of points that
exchange being broadcast by the owner
the exchange. have signals to change.
and the user’s copy.
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 is 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\HEALTHY where NET is the name of the network and
DEV is the name of the controller.
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 8-bit byte offset into the exchange, and BIT is
the bit number, which ranges from 0–7 (7 is the most significant bit).
½ To insert and modify a point
1. From the Outline View, click on the EGD exchange to highlight it.
Or use the shortcut keys, Shift 2. From the Edit menu, choose Insert First. Modify the point settings (described
+ Insert in the next section).
Point Settings
The EGD Point Settings dialog box is used to insert and edit the EGD
point.
Enter the name of the signal associated with

this point. This name must be provided to
create a point. Browse... allows you to choose
the signal using the Signal Selector dialog box.
Choose the Data Type from a drop-down list of

data types supported by the EGD. These data
types are different from the basic controller
data types and are listed below.
Click Lock to set the word offset and bit

number. (Also use the Lock All Signals and
Unlock All Signals command in the
InternalExchange 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 Utility.
The health address is provided Edit Signal displays the Signal Edit dialog
for signals that need health, such box. The button is only active when the
DLAN+ and Genius. point is being inserted.
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 Internal 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
2. From the Summary View, double-click on 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
3. From the Summary View, double-click on the actual point value or signal
value. The appropriate Edit dialog box displays.
Genius Networks
The controller receives inputs from and sends outputs to field devices, such as light
sensors or switches using elements of GE Fanuc’s Genius system line of I/O
products. The products, Genius Blocks and the Field Control I/O modules, are used
by the controller and are 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 add a Genius Network
Another item can be added by 2. From the Edit menu, choose Insert First.
following the same steps, but
Or, click the right mouse button on and choose Insert First. The New I/O or
choose Insert Next.
Network Interface dialog box displays.
3. Choose 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
w Double-click on the item Geni_:IC660ELB912. The Genius Network
Configuration dialog box displays. µ
Genius Network Configuration
Enter the name for the Genius network

that displays on the hardware
elementaries.
Enter or select the number of the µGENI

that identifies it with the controller.
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
Click on Geni1:IC660ELB912
Click here to turn on Tracking.
This displays the Genius Network view.
Right-mouse click
anywhere on this
view (right side) 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 on 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.
Configuring the 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 on the icon to 1. From the Outline View, click on the icon Geni_:IC660ELB912 to expand
reduce the item levels. the level to display the items HwConfigs and SWConfigs.
2. Click on the icon SWConfigs to expand it, as shown. All configurable
items display.
Configuration
items
½ To modify a configuration item

w Double-click on 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 controller’s
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 µGenis, 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.
GlobalData is the setting that enables the µGENI to send global data. Currently, the
list box has three selections to specify the amount of global data to be used. Choose
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 as described in the following
section, Defining Genius 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 toolbox’s Add Genius
Block dialog box.
Insert a Genius Block

½ To insert Genius Block
Another item can be added by 1. From the Outline View, click on network item GENI_:IC660ELB912.
choose Insert Next.
Or, use the right mouse button, click on network item GENI_:IC660ELB912
The Add Genius Block dialog box displays (refer to the next section).
Add Genius Block Dialog Box
Controls the outputs for the chosen 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.
Configuring a Genius Block
Click on the Genius

block in the Outline View
and choose Modify.
The Genius Block Configuration dialog box displays to modify the block fields
(refer to the next section).
Genius Block Configuration Dialog Box

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 block’s 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
(refer to Appendix B).
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
w From the Outline View, click on the Genius Block and click Detached
Summary View.
− Or −
1. Click on the Genius Block to highlight it.
2. From the View menu, choose 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 on and it has been 30 seconds 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 point’s value and the point’s 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
w 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 block’s 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 toolbox’s Add Genius Block dialog box.
For more information, refer There are conventional Field Control modules, which provide or receive just one
to the GE Fanuc’s 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 on network item GENI_:IC660ELB912.
Or, use the right mouse button, click on network item GENI_:IC660ELB912
choose Insert Next.
3. The Add Genius Block dialog box displays. Choose the BIU Field Control as
follows. (The next section describes how to configure the field control.)
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
w From the Outline View, double-click on 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 Block’s 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 on a Field Control BIU.
Or, use the right mouse button, click on the Field Control BIU item and choose
choose Insert Next.
Insert First.
3. The Add Field Control Module dialog box displays. Choose the module as
follows. (The next section describes how to configure the Field Control.)
Enter the Field Control BIU that
Controls the outputs for the chosen drop
displays on the hardware
by enabling/disabling the writes to
elementries.
Genius outputs from the controller.
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.
Configuring a 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

w From the Outline View, double-click on the Field Control Module item. The
Field Control Module Configuration dialog box displays (refer to the next
section).
Field Control Module Dialog Box

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.
Configuring an 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

w From the Outline View, double-click on the Field Control Module item. The
Field Control Module Configuration dialog box displays (refer to the next
section).
Intelligent Field Control Module Dialog Box
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 AQ 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
w From the Outline View, double-click on the point. This displays the Point
Edit dialog box.
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 (refer to the next section, Point Edit Dialog Box).
Point Edit Dialog Box
Enter the point to edit.
Choose 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 on the item
Hardware and I/O Definitions.
2. From the pop-up menu, choose Insert First. The New I/O and Network
3. Choose Genius Network and click OK. Geni:IC660ELB912 is inserted.
4. Use the right-mouse button, click on Geni:IC660ELB912 and click Insert
First. The Add Genius Block dialog box displays.

Select other GENI-GB

Device with GENI
interface.
Configuring a Genius Block
Click on the Genius

block in the Outline View
and choose Modify.
The Genius Block Configuration dialog box displays to modify the block fields
Genius Block Configuration Dialog Box
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 block’s 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
(refer to Appendix B).
Note Block drop numbers must be configured in each block with a hand-held
monitor.
Monitoring 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, displays
from the view as they log in the blocks actively communicating on the network, the fault and force status of each
and out of the network. block, and the output enable/disable state of each block.
½ To view the Genius Net View
w From the Summary View, choose 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
w From the Outline View, click on the Genius block and click the button.
− Or −
See the section, Genius 1. While online, from the Summary View, select the Genius block and activate
Network View. the Genius Net menu.
2. From the Genius Net menu, choose 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 on and it has been 30 seconds 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 point’s value and
the point’s 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.
Uploading
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.
Downloading
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
choose 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, choose a block on the Genius Net View.
3. From the Genius Net menu, choose BlockConfigDownload.
For the Field Control station, choose which part of the Field Control to
download and choose ReferenceAddress.
For the software configuration, click on 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. Choose which
part of the Field Control to download, and choose 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.
Generating the 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.
Generating The 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 BlockDetailView. The BlockDetailView 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 on 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.
Forcing/Unforcing 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, then all output forcing to that block at the controller level does
not take effect. Also, if the controller gets rebooted, then 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 block’s
EEPROM to survive power cycle. The Genius block uses the forced output value for
output, disregarding the controller’s 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
w From the Outline View, choose the Genius block and then click on , to
display the BlockDetailView.
− Or −
1. From the Outline View, choose the Genius Net with the tracking function on.
This activates the Genius Net View in the Summary View.
2. From the Genius Net View, choose the block by clicking on its icon. Choose
BlockDetailView from the menu.
3. Click on 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. Choose 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 on the controller The item Main Board currently holds the non-volatile memory. Inserting the Main
name and choose Modify. Board depends on the type of controller selected in the Properties dialog box, such
From the tab General, as the SD200UCPB, SD215UCV_ , or DS214ACL_
choose Platform and the
desired controller.
½ To insert Main Board
Or click the right mouse 2. From the Edit menu, choose Insert First. The New I/O or Network
button and choose Insert Interface dialog box displays.
First.
3. Click on 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
signal’s 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 that are 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 hardware module
1. From the Outline View, click on Main Board.
Or use the shortcut keys, 2. From the Edit menu, choose Insert First.
Shift + Insert.
Or, click the right mouse button and choose Insert First. The New Hardware
Module dialog box displays.
3. Click on 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 on the item 1. Click on NOVRAM to highlight it.
NOVRAM.
2. From the Edit menu, choose Modify. The NOVRAM Edit dialog box displays
Edit NOVRAM Dialog Box
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 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, then 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
1. From the Outline View, click on the item NOVRAM to highlight it.
Or use the shortcut keys, Shift 2. From the Edit menu, choose Insert First.
+ Insert
Or, click the right mouse button and choose Insert First. The NOVRAM
Insert another item by Point Edit dialog box displays.
choosing Insert Next.
Edit NOVRAM Point
Enter the point to edit.
Choose 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 Modbus™
• A-B Data Highway Plus (DH+)
• Ethernet Modbus
• 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 a Ethernet SRTP
Or, click the right mouse 1. Click on the item Hardware and I/O Definitions.
First.
Choose Ethernet SRTP

and click OK.
The SRTP Interface

Settings dialog box
displays (refer to the
next section).
SRTP Network Settings
The default name is MMI1.
Enter a name using up to five
characters. The name must
begin with a letter of the
alphabet.
Enter a description of the

interface.
Click OK.
The Ethernet SRTP Interface

is inserted in the Outline
View (see below).
Right-mouse click on <name> Ethernet SRTP
Interface. Choose Insert First. Pg1 is inserted.
To insert points, right-mouse click on Pg1 and

choose 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 name must be provided
to create a point. Browse… allows you to
choose the signal using the Signal Selector
dialog box.
Address is assigned by the toolbox to a

point that is Byte.BIT.
Choose the Data type from a drop-down list

of data types supported by the EGD. These
data type are different from the basic
controller data types and are listed below.
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
Utility.
Lock toggles the point between lock and unlock (meaning Click here to allow Edit Signal displays the
that the word offset and bit number are set when locked and thesignal to be scaled Signal Edit dialog box. The
will not change until it is unlocked). ( Also use Lock All for non-bit data types. button is only active when
Signals and Unlock All Signals command buttons in the the point is being inserted.
Internal Exchange Settings dialog box.)
The following screen is an example of the Ethernet SRTP Interface.
Serial Modbus
Serial 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
Communication with the remote controller is implemented using register pages.
controllers.
½ To insert a Serial Modbus
Or, click the right mouse 1. Click on the item Hardware and I/O Definitions.
First.
Note The Mark VI is always a Modbus slave
Choose Serial Modbus and

click OK.
The Serial Modbus dialog
box displays. Enter the
correct settings as described
in the next section.
Serial Modbus Settings
Identifies the Serial
Enter the communication
Modbus network in the
mode for the network.
controller. Enter up to five
Binary mode is the default.
characters.

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.
Baud Rate, Parity, Data

Bits, and Stop Bits define
the communication settings
for the network and must
be set to match all other
controllers on the network
(check this dialog box on
other controllers).
Click OK and insert a

page as shown below.
Right-mouse click on
<name> Serial Modbus
Interface. Choose Insert
First.
Pg1 is inserted.
To insert points, right-mouse

click on Pg1 and choose
Insert First.
Note To modify the 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 1. Click on the item Hardware and I/O Definitions.
2. From the Edit menu, choose Insert First. The New I/O and Network
First.
Choose 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
Identifies the Serial
Modbus network in the
controller. Enter up to five
characters.

port used to talk to the
external controller.
Baud Rate, Parity, Data

Bits, and Stop Bits define
the communication settings
for the network and must
be set to match all other
controllers on the network
(check this dialog box on
other controllers).
Click OK and insert a

page as shown below.
The named DH+ Interface is inserted.
A-B Data Highway
Plus Interface. Choose Insert
First.
Pg1 is inserted.

Insert First.
Note To modify the pages and points, refer to the sections Modify Page Settings
Ethernet Modbus Interface

Ethernet Modbus pages define the interface between the Innovation Series controller
and other controllers. This allows third party computers to read and write signals that
exist in the Innovation Series controller.
½ To insert a Ethernet Modbus Interface
First.
Choose Ethernet Modbus

and click OK.
The Ethernet Modbus
Settings dialog box displays.
Enter the correct settings as
described in the next section.
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. Choose Insert
First.
Pg1 is inserted.

Insert First.
Note To modify the pages and points, refer to the sections Modify Page Settings
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
First.
Choose Custom Register

Network and click OK.
The Configurable Register

Network dialog box displays.
Refer to the next section.
Custom Register Network Dialog Box
Default name can be

edited using up to five
characters.
Select the network

type(s) that this
network supports.
Select the network

configuration
parameter to edit.
Change the value of
the parameter.
Register Network.
Choose Insert First.
Pg1 is inserted.

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 on 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.
Choose the registry/

coil.
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 that is 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 the point, double-click on the point to display the Point Settings dialog box.
Enter the page name

or choose Browse.
Enter the number of

the register that the
signal is connected to.
Enter the data type of

the register. This field
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 can not be non-bit data types.
registers on the page.) moved if you perform
a page compress.
Notes
Chapter 11 Configuring the Network
Interface
Introduction
This chapter provides instructions for using the toolbox to configure the Network
A Level II PC is a PC-based
Interface. The Network Interface is used to configure general type controllers, such
controller that performs high
as Level II PCs (Alpha or Intel 386), or non-GE controllers for interface signals that
level functions, such as
are used on a project. The interface configuration also allows you to store signal
tracking, models, and recipes
ownership and usage in the System Database (SDB). For PCs that connect to
(setup data). It can connect to
DLAN+, the interface produces a signal definition text file (.cfg) to resolve signals
another computer to obtain
during runtime, and routing table text files (.rte) used by the interface drivers to
process data.
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 ................................................................................................................ 11-1

Configuration ......................................................................................................... 11-2
Concepts
The Network Interface is used to configure a Level II PC, usually running the
OpenVMS (virtual memory system) or Microsoft NT operating system. 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.
GEH-6403A Toolbox for a Mark VI Controller Chapter 11 Configuring the Network Interface • 11-1
Configure the Network Interface using the toolbox as follows:
1. Define the signals that the Network Interface owns.
2. Map these signals to the appropriate network.
3. Define the signals that the interface will use.
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 may need to be copied onto the actual Network Interface PC. The
the Network Interface PC interface PC applications read the .cfg files to resolve signals on the appropriate
read the signal text file when networks during runtime. The .rte files are read to determine how to make DLAN+
they first start. command messages and forward DLAN+ messages from one network to another.
For the Network Interface PC that is 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.
Configuration
This section provides instructions for using the toolbox to configure the Network
Interface.
Creating the Network Interface

½ To create a Network Interface
w From the File menu, choose New. The New dialog box displays a list of
Or click available devices.
Click the System

Configuration tab. Then
click Network Interface
to highlight it, and click
OK.
The Network Interface window is created with a temporary name, such as nwdv1.
The Outline View of the window displays five items as follows:
11-2 • Chapter 11 Configuring the Network Interface GEH-6403A Toolbox for a Mark VI Controller
Device name
Modify Network Interface Name

½ To modify the name of a Network Interface
1. From the Outline View, click on the interface name to highlight it.
Or, double-click on the name. The Modify dialog box displays.
Modify Device
Enter a new name using

no more than five
characters.
Enter a note in the text

box, if desired.
Click OK to exit.
Working 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. Users 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.
Exporting 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, choose Export (see menu below).
commands are managed just
3. Choose All. The Export Project dialog box displays to confirm the name of
as other toolbox and
the .prj file.
Windows menus (refer to
Chapter 4). 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, choose Export (see menu above).
3. Choose Selected. The Export HWIO dialog box displays to 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.
Defining a 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, choose Import and choose the mk6_iolib.tre file.
Or, click on the item with the 1. From the Outline View, click on the item Hardware and I/O Definitions.
right mouse button and
choose Insert First.
If the hardware library is not loaded, 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. Choose the desired network connection and click OK. The network item is
inserted in the Outline View as shown below.
Network interfaces
Tip © For more information on editing different networks, refer to Chapter 10.
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 a Dialect
½ To modify a dialect
1. Insert the DLAN+ Interface using the steps in the previous section, Defining a
Or double-click on DLAN+ Network Connection.
Interface.
2. From the Edit menu, choose Modify. The Edit DLAN+ dialog box displays.
Edit DLAN+ Interface Dialog Box

A default name is assigned when
DLAN+ is inserted. In the USDB, the The ARCNET node number (1 to
network name exists in the database and 240) for this controller on this
is set by the command Get From network (must match the board
Database. For the SDB, the name is DIP switch setting). Enter the
made available to other controllers with value 0, and the next available
the command Put Into Database (refer to drop # is assigned when it is put
the SDB Browser in the View menu). into the database.
The dialect identifies the

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

network.
Inserting/Defining Signals
Function names are limited to Network Interface signals are inserted in the toolbox in the Outline View under the
eight characters. item Function. A function acts as a grouping mechanism for inter-related modules.
½ To insert a function into a configuration
Or, click the right mouse 1. From the Outline View, click on the item Functions.
button, and choose Insert
2. From the Edit menu, choose Insert First. The Function Name dialog box
First.
displays to name the function. For example, enter the name func1, and click
OK.
Click on Functions ,
and from the Edit
menu, choose
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 4, Configuring the Mark VI Controller.
Mapping Signals to a Network

See Chapter 10, Hardware Once the signals are defined, they must be mapped to the appropriate network and
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.
Specifying Signals Used by the Network Interface
To specify signals expand the item Functions, and choose the item Modules.
Refer to the section, Module Use the right mouse button

Pins. and click on the pin you
want to edit, and choose
Modify.
The Edit Module Pin Definition dialog box displays. In the Connection text
box, enter the name of the external signal to be connected to the pin, or choose
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 that are 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.
Exporting 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 created, if
the signal and the routing 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, choose 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. Choose Signal Data. The Signal Export File dialog box displays.
Or, choose 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.
Exporting 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, choose Export.
2. Choose Egd Ini.
A dialog displays to confirm the exporting destination of the file.
3. Click Yes, and the initialization file will be stored in the displayed location.
Chapter 12 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 Get from Database. There are two databases: System
and Unified System.
System Database (SDB) is a Windows-based Client/server, which uses .dbf files for
storing data.
®
Unified System Database (USDB) is an Informix SQL relational database
client/server, which runs on a LynxOs based PC.
Section Page
Signal Concepts ..................................................................................................... 12-1

SDB and USDB ..................................................................................................... 12-9
Signal Concepts
Signals are the place holders for memory locations in the toolbox’s 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, see the Signals exist in the database only when they are mapped (connected) to a network
section, SDB and USDB. 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
• Get from database command
• Inserting an item of blockware in a controller
• Creating an AcDcEx2000 device
GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 12 Signals and the Database • 12-1
AcDcEx2000 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 signals tokens
are fixed, since the VARs are created when the device is created and exist as long as
the device exists.
Mark VI Controller Signals

In the toolbox Outline View, controller signal definitions are inserted under the item
Signal Definitions (under the items Function or Macro and Module library). 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.
Signal definitions can be

inserted under the items:
System Data
Macro and Module Libraries
Functions
12-2 • Chapter 12 Signals and the Database GEH-6403A Toolbox for a Mark VI Turbine Controller
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 Limit name to 7 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 macro’s 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 5, 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, see
pins with non-collection data types. Referencing incorrectly causes a validation
Chapter 4.
error. Correct the error by reversing the direction of the connection or by creating a
pin and referencing that pin.
Attaching Signals to I/O
I/O points found under the item Hardware and I/O Definitions 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 in When the output transfer occurs, the engineering units are converted to raw counts.
Chapter 4.
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:
• Proceed the inverse of a Boolean signal with a tilde symbol ~.
• Proceed the health of any signal connected to an I/O point, (Boolean value) with
the number symbol #.
A signal’s 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 that are 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 count Bit 0 =point
health = 1
* The meaning of the Genius Block and circuit fault codes can be obtained from the Genius I/O System and
Communications, User’s Manual, GEK-90486F-1.
Scale Definitions
For more information on A scale can be attached to either a signal definition or module pin definition. Any
defining scales, see the signal can be mapped to a network page owned by the device. When the command
section, Scale Definitions in Put into Database is used, all the signals and any scales attached are put into the
Chapter 4. SDB. The scale is now available to other devices using the command Get from
Database. These scale definitions display under the items System Data/External
Scale Definitions, as shown below:
Signal Selector
The Signal Selector dialog box allows you to choose a signal for the various
functions in the toolbox. It can be opened by choosing to insert a signal or connect
to a signal (using the Browse button found on many dialog boxes). Enter the desired
information for each signal in the Signal Selector dialog box as follows:
Choose the region that

signals can be selected from.
Double-click on the desired
region name .
Then, this list displays
available signal. Double-click
on the desired signal name.
A description of the selected

signal displays here.
Choose the type of signal to display in the Choose either Local or network items,
list above, such as All Types, Boolean, LInt, when available. The default is Local.
MathEqn and so on.
SDB and USDB
The SDB and the USDB are client/server databases. The SDB is a Windows-based
database server that uses .dbf files for storing data. The USDB is an Informix SQL
relational database server which runs on a LynxOs based PC. It is used to integrate
For more information, refer Lynx based products with Windows products. Choose the database from the Options
to GEI-100189. menu under Settings and the tab Database.
The following are differences between a USDB and an SDB database:
• The USDB supports a LynxOs-based importer program, which can load the
USDB from text files. The importer can write topology data to the USDB. If the
importer is used to update topology information, then the toolbox command Put
into Database should not used for topology. The command must be used to send
Genius Signals to the USDB.
For the SDB, only the device that owns the topology and signal data can put that
information into the SDB. There is no separate import program.
• The USDB cannot be created from the toolbox. The USDB must be installed on
the LynxOs PC with the appropriate USDB product.
The SDB can be created from the toolbox as long as the SDB server is running.
• Debug and I/O information are stored in the USDB in a table separate from the
USDB signal table. Normally, only the LynxOs-based HMI has access to this
table.
In the SDB, I/O points and internal signals that can be put into the database are
stored in the signal table.
• The USDB name is specified as a single name in the Options menu, under
Settings and the tab Database.
The SDB is specified by a path qualified sub-directory where the database is
stored. The SDB name must include a drive letter.
Put into and Get from Database

The command Put into Database provides information to 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 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.
• 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 incremented. Full is when the old
signals of a device are deleted from the database and replaced by the signals that the
device presently owns. This is also for network connections and pages owned by a
device.
Incremental adds signals 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, data with the value of 0 is
automatically assigned a new value by the database. The numbers that the database
assigned 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, choose Put into Database. Choose Full to include
all information or Incremental for specific information.
The toolbox displays the message box shown below, indicating which server
will be used and the database. If any of this information is incorrect, cancel the
operation by clicking on No.
2. Click on 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 device’s
Pcode. The command, Get from Database also allows the device to create the actual
value of the signal from the network interface. There are two types: full and
incremental.
In the command full, 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.
An 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 device’s 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, choose Get from Database. Choose Full to include
all information or Incremental for specific information.
The toolbox displays the following message box, indicating which server will be
used and the database. If any of this information is incorrect, cancel the
command by clicking on No.
2. Click on Yes to continue the command. The Error Log View displays the
present state and status of the command.
An example is shown below. 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 device’s 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 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 is 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 The device that is getting scales from the database might own scales that were
put into the database. These scales are maintained, so when the command occurs,
scales owned by the device are not returned and avoids duplicate scales for the
device.
Appendix A System Database (SDB) Browser
Introduction
The Browser can be accessed SDB Browser is used to view the contents of an SDB database, display the topology
from the toolbox with or of a system, and perform a filtered signal search on the SDB, list system scales, and
without having a device open. more. The SDB Browser is implemented as a Dynamic Link Library (.dll), so it must
be started from another application, such as the Control System Toolbox, the SDB
Server Control, or SDB Utilities and the Diagnose application.
Section Page
Starting the SDB Browser....................................................................................... A-1

SDB Browser Tabs ................................................................................................. A-5
Signal Fields ......................................................................................................... A-13
Starting the SDB Browser

The SDB Browser is started from the SDB Server Control command button or from
the toolbox or SDB Utility’s View menu, as described in the following sections.
GEH-6403A Toolbox for a Mark VI Controller Appendix A System Database (SDB) Browser • A-1
From SDB Server Control
Refer to the application ½ To start the SDB Browser from the SDB Server Control
manual, GEI-100189 or the
online help. w From the SDB Server Control dialog box, click on the button,
then click button.
The SDB Maintenance dialog box displays.

database to search.
Click on the Browse

SDB button.
The SDB Browser

window displays.
A-2 • Appendix A System Database (SDB) Browser GEH-6403A Toolbox for a Mark VI Controller
From the Toolbox or SDB Utilities
½ To start the SDB Browser from the toolbox or SDB Utilities
1. Select an SDB in order to enable the SDB Browser.
From the toolbox, select Options menu, Settings, and the tab Database.
From SDB Utilities, select Options menu and Select SDB.
Refer to the online help found 2. From either application, select the View menu, and SDB Browser. The SDB
in both applications. Browser window displays.
SDB Browser Toolbar
The SDB Browser displays the following buttons on the toolbar:
Click To
keep the Browser Window open and on top of the screen. If this pushpin
displays, the window closes when the area outside is clicked. Click on
this pushpin to keep the Browser displayed on top of other windows.
Close the Browser Window when the area outside is clicked. This
pushpin displays when the pushpin above is clicked on. The Browser
Window remains open and on top of the screen when the pushpin is in
this position (even when working in another window).
Hide all tabs and make the Browser window display only the Output
View.
Load signal query settings from a file (only available in the Signal tab).
Save the current signal query settings to a binary file with the extension
.sqs (only available in the Signal tab).
Save results of the signal query to a text file that can be viewed in
Notepad (only available in the Signal tab).
Print the signal query results in the Output View to produce a hard copy
(only available in the Signal tab).
Delete a device and all signals owned by the device from the SDB
database (only available in the Topology tab).
display the Help file for this utility.
SDB Browser Tabs
The following sections describe the tabs that can be selected to start a search.
Signal Tab
½ To perform a signal query
1. From the SDB Browser, choose the tab Signal.
To define the
signal query,
click on the
Query... button
(Refer to the
Query Design
dialog box in
step 2.)
The finished
query displays
in the Output
View
2. From the tab Signal, click on Query. The Query Design dialog box displays.
The order shown in the In the Query Design dialog box, a Field represents each attribute of a signal. The
following screen is the default order of the field columns in the dialog box determines the order of the data
order. when the results of the query display in the Output View. Change this order by
clicking on a column to highlight it, then drag-and-drop to a new location.
Signal fields can be rearranged using
drag-and-drop.
Sort arranges the

order of multicolumns.
Show or Hide
determines the
visibility of a field in
the Output View.
Criteria or Or
establishes the
guidelines of the find
(such as using
Wildcards).
3. Click on the column/cell to highlight it. Choose the Sort and Visibility for each
field. Edit the order of the columns, if desired.
Sort is a drop-down list to arrange the order of the data by choosing None,
Ascending, or Descending. Sort order is from left to right and the default is
None.
Visibility is a drop down list to Show or Hide a field (column) to minimize
the number of columns of the Output View results. Show is the default.
4. Enter the item(s) to query in the row(s) Criteria: and Or:
Criteria: and Or: are used to establish the filter of the query. Enter the item to
match in the desired field (column). Wildcards, such as the asterix symbol *
(match any number of any character) and question mark ? (match one of any
character) are allowed.
5. Click OK and view the results in the Output View.
Criteria Examples
The following are examples of entering multiple criteria in the Query Design dialog
box. Match signals where:
REG1NAME begins with R and REG2NAME equals FEED.
REG1NAME equals MILL1 or REG1NAME equals MILL2.
REG1NAME begins with R and REG2NAME equals FEED or NET_NAME

equals RDL01.
Criteria is evaluated by the
row. Therefore, match signals
where REG1NAME begins
with R and REG2NAME
equals FEED is evaluated
first. Then, the next row,
NET_NAME equals RDL01,
is evaluated.
REG1NAME begins with R and NET_NAME equals RDL01 or REG1NAME

begins with R and NET_NAME equals RDL02.
Signal Query Example
To change the order of The following Query Design changes the default order of the columns. The first five
columns, click on the column columns have Show for the visibility attribute, so the resulting list will only show the
and then drag-and drop to the owning device plus the full signal name. The criteria (or filter) reads:
new location.
Match all signals where REG1NAME begins with the letters FM or where
REG2NAME equals SHAW or REG2NAME = test. (The filter is not case
sensitive.)
The following screen displays the results of the signal query in the Output View.
A query design can be saved. The saved file will include the criteria of each column,
Click to restore a the sort order, visibility, and the order of the columns.
previously saved query
design.
Click to save the query design to a binary file with the extension .sqs.
Click to save the results as a text file that can be viewed in Notepad.
Topology Tab
½ To display topology information
1. From the SDB Browser, choose the tab Topology.
The button gets
recent data from the SDB 2. Click the Update button. The Topology Output View displays as shown
database. below.
View Options
Output Views
Expand the hierarchy by The left Output View displays devices, networks, and pages in a hierarchy. Click on
clicking on the symbol . an item to highlight it. The right Output View displays detailed information about
the item highlighted. Control how this information is organized by choosing one of
the following options:
View by device displays all devices in the SDB as shown below. When expanded,
each device lists all the networks that the device is connected to, and each network
lists the pages that the device owns on that network.
The drop number of the View by Network displays all networks in the SDB as shown below. When
device is in parentheses next expanded, each network lists all the devices connected to that network, and each
to the device name. device name lists all pages that the device owns on that network.
Delete a device and all
signals owned by the device
from the SDB by highlighting
the device and clicking on the
delete button.
Note If a device is accidentally deleted, it can only be recovered through the

appropriate tool (such as the toolbox for drives or controllers).
Where Used Tab

½ To display signal usage information
1. From the SDB Browser, choose the tab Where Used.
The button
starts the search process. 2. Type in a signal name.
3. Click on Update button. The Where Used Output View displays the location
where the signal is used as shown below.
The display window displays all the devices that use the signal UC1\fdlo1\sig2. In
order for a device to display in this list, it must have referenced the above signal in
its code, and performed a successful get from the SDB for that signal.
Alarms Tab
½ To display alarm information
1. From the SDB Browser, choose the tab Alarms.
Click to
display information. 2. Click the Update button. The Alarms Output View displays, as shown below.
Alarms originate in the System Device of the toolbox as Broadcast alarms.
Scale Tab
½ To display scale information
1. From the SDB Browser, choose the tab Scale.
Click to
display information. 2. Click the Update button. The Scale Output View displays, as shown below.
NetGroups Tab
½ To display network group information
1. From the SDB Browser, choose the tab NetGroups.
Click to
display information. 2. Click the Update button. The NetGroups Output View displays, as shown
below.
Resources Tab
½ To display resources information
1. From the SDB Browser, choose the tab Resources.
Click to
display information. 2. Click the Update button. The Resources Output View displays, as shown
below.
Signals can be assigned to a specific resource (see res_ID field in the signal attribute
list). The resource is used to filter which signals get imported into the CIMPLICITY
HMI system using SDB Utility.
Signal Fields
The following tables describes the SDB signal fields (see the section, Signal Tab).
Table 1. SDB Signal Fields

Field Name Name Type Description
Description
REG1NAME Region 1 name String, six The first part of a fully qualified signal name. See SIG_NAME
(part of the fully characters for details on signal naming conventions. The REG1NAME is
qualified signal) maximum a required part for a signal.
REG2NAME Region 2 name String, six The second part of a fully qualified signal name (optional).
(part of the fully characters See SIG_NAME for details on signal naming conventions.
qualified signal) maximum
REG3NAME Region 3 name String, six The third part of a fully qualified signal name (optional) . See
(part of the fully characters SIG_NAME for details on signal naming conventions.
The fourth part of a fully qualified signal name. The
SIG_NAME Signal Name (last String, 12
SIG_NAME is a required part for a signal. The fully qualified
part of fully characters
signal name can be described as,
Reg1name\Reg2name\Reg3name\Sig_name.
Reg2name and reg3name are optional, so a fully qualified
signal could be named at a minimum as,
Reg1name\Sig_name.
The backslashes are part of the fully qualified signal name.
Including the backslashes and the maximum sizes of the
different parts, a fully qualified signal name can be 33
characters long. However, the CIMPLICITY HMI system uses
the fully qualified signal name as the ‘PointID’ when signals
are imported into the HMI point database. The limitation for
‘PointID’ is 32 characters. For this reason, the total size of a
signal is limited to 32 characters when signals are put into the
SDB.
The fully qualified signal name must be unique on a given
network. This means that it is possible for two networks to
have identical fully qualified signal names. The SDB Server
enforces uniqueness for the following fields: Net_name +
reg1name + reg2name + reg3name + sig_name.
The signal name can be the same on two different networks
in order to support routing of a signal from one network to
another.
This is the device that owns the signal. The device name field
DEV_NAME Device Name that String, seven-
should never be blank. The device name can have up to
owns this signal character
seven characters. However, the toolbox enforces a five
maximum (limit
character limit to the device name in order to maintain
of five for the
backwards compatibility with the LynxOs-based USDB.
toolbox name).
SDB Signal Fields — continued
Description
NET_NAME Network Name String, five Name of the network where the signal is made available by the
where this signal character owning device. The device in DEV_NAME is connected to this
is available maximum network when viewing the topology of the SDB.
To support diagnostics on operator stations or an HMI system,
signals that are internal only (to a device) are also stored in the
signal table of the SDB. In this case, network name is
meaningless. In order to differentiate between network available
signals and internal signals, the network name field is forced to
be the same as the device name, and page name
(PAGE_NAME) is assigned the value “NULLP” (for Null page).
PAGE_NAME Page Name String, five This is the name of the page where this signal is mapped. A
where this signal character signal’s address (SIGADDR) is relative to the page named in this
originates maximum field. (See NET_NAME about internal signals.)
For DLAN+ and ISBus, the page has physical meaning
(Status_S page word/bit) within this network’s protocol. However,
for Ethernet™ SRTP and other networks, the page is an artificial
construct used only to group signals.
SCALE_NAME Scale name used String, 12 For analog type signals, this is the name of the scale associated
by this signal character with the signal. For details on the scale, click on the tab Scale in
maximum the SDB Browser. A scale definition includes conversion factors,
alarm limits, entry limits, clamp limits, units, precision, and more.
SDESC Signal String, 50 This is the user entered signal description. In the toolbox, the
description character description is the first 50 characters of the note associated with
maximum the signal definition.
IODESC I/O description String, 50 If the signal points to a physical I/O point, this field is the user-
character entered I/O description. In the toolbox, the I/O description is the
maximum first 50 characters of the note associated with the I/O point.
MEMODESC Memo String, no limit This field is used for controller diagnostics. If this signal is a
description controller internal signal that is the Status Pin on a block that
sends diagnostic messages (PENG, BENG_D, etc), then the
MEMODESC is the note associated with the block. This text
displays in the diagnostic system as the second level when a
diagnostic message is generated.
ALRMENABLE Alarm enabled Boolean, one If the value of this field is False, DO NOT use this signal as an
character alarm. If the value of this field is True, use this signal to generate
alarms. If it is an analog signal with a scale, alarm generation
should be based on the appropriate scale fields. If Boolean
signal, a change in state of this signal may or may not generate
an alarm. This field is primarily used when SDB Signals are
imported into the CIMPLICITY Point database. If this Boolean is
true, then an alarm definition is created for this point in the
CIMPLICITY system.
Description
HOP_COUNT Hop count Numeric, one When a signal is routed from one network to another, this field
(number of significant stores the number of devices that are between this signal and
devices away from digit the actual source of the signal. If a signal is routed through
true owner) device R1 from network 1 to network 2, and then by device R2
from network 2 to network 3, the record for the signal on
network 3 will have a hop count of 2.
SDEV_NO Source Device Numeric, five This field is used for routed signals. This is the device number
Number where significant for the device that originated the routed signal. This data is
signal originates digits required in the controller for signals that are routed through the
DLAN+. The Source Device Number is included in the actual
command message that is sent by a device.
SNET_NO Source Network Numeric, five This field is used for routed signals. This is the network
Number where significant number where the signal originated. This data is required in
signal originates digits the controller for signals that are routed through the DLAN+.
The Source Network Number is included in the actual
command message that is sent by a device.
SSIGADDR Source Signal String, 10 For routed signals, this is the address of the signal for the
Address characters device that sources the signal. This is used for command bits
maximum that are routed for DLAN+.
SRPAGE_NO Source Relative Numeric, two For routed signals, this is the relative page number (Port ID)
Page Number significant where the signal is located for the device that sources the
digits signal. This is used for command bits that are routed.
RES_ID CIMPLICITY String, 12 This field is used to filter signals imported from the SDB into
Resource name characters the CIMPLICITY Point database. Importing methods include
maximum specifying the network and the device from which you wish to
import signals (if desired). There can be thousands of signals
on a given network, but the HMI system may be interested in
only a small percentage of these. For example, assign
Resource names to specific signals; Import all signals on
network FDL01 that have a resource name of ENTRY,
PROCESS, and EXIT.
System Information, under the Resource Type Def defines
resources in the toolbox. When the command Put into
Database is performed, the Resources are stored in the SDB.
Now, when a controller gets from the SDB, the Resource list is
made available, so that I/O points can be assigned a resource.
The Resource is assigned to the points in the toolbox where
the network I/O point is defined. (See the Resources tab in the
SDB Browser for defined resources.)
Description
DATA_TYPE Data type for this String, 8 There is no restriction by the SDB on what is put into the data
signal characters type field. There has to be contract between applications that
Refer to Table 2 maximum puts signals in the database and those that get signals from the
for a list of the database (the separate applications must agree on exactly what
data types used is meant by a DINT data type).
by the toolbox.
SIG_DIR Signal direction Character, This field is used to indicate whether a device that gets this
(read, write, both) R, W, B signal can write to the signal or read the signal, or both.
Feedback signals are typically read only. Command bits or
setpoints are usually both.
SIG_CODE Signal code Character, The signal code is normally only used for Boolean signals. An
(event, refresh, E, R, N event bit is usually a command bit, and when it is set by another
none) device, the owner of the signal will then reset the bit after
detection of the event (the bit goes high). A refresh bit is also
usually a command bit. The device that sets the bit to a one is
required to send ‘set’ commands at a periodic rate in order to
keep the bit set to a one. If the sender does not keep refreshing
the bit, then the owner of the signal forces it to a zero.
The usual example is the JogFwd Command. If an OC2000
sends a command to jog forward, but then it is disconnected
from the network, there is no way for it to reset the jog forward
command. This problem is solved by the fact that it can no
longer refresh its jogfwd command, so the drive stops the jog.
If the signal is neither an event bit nor a refresh bit, then this
field will be set to N for none.
SIGADDR Signal Address String, 10 This is the address of the signal. For Status_S, it is the word
characters and bit number in the form of word_no.bit_no (23.5) or just word
maximum no (34). For a Ethernet SRTP, the address is in the form
%Xnumber (%R543). For Ethernet Global Data protocol (EGD)
it is byte_no.bit_no (45.4) or byte_no (34).
For EGD or DLAN+, the word number or byte number is relative
to the page. For Ethernet SRTP, the number is relative to the
whole network.
HSIGADDR Signal Health String, 10 The form is the same as SIGADDR. The address always points
Address characters to a Boolean. True means the signal is healthy and False (0)
maximum indicates that the value for the signal may not be valid. This field
is used only for DLAN+ or EGD. If no health signal is defined,
then the value in this field is either blank, or 65535.6553.
Description
DEV_TAG Device Tag ID String, 20 This field is the customer or the mill builders item number for the
characters device that this I/O signal is associated with. The value is user
maximum defined.
WIRENO Signal Wire String, eight Enter the wire number on electrical drawings for the I/O related
Number characters to this signal.
maximum
SIG_XREF Signal Cross String, 15 This is a general-purpose field for storing signal cross-reference
Reference characters information.
maximum
DEVLOC Signals Device String, six This field indicates the plant location for the device that
Location characters originates this I/O point, for example, OPPOR1 (Operator Side
maximum of the Payoff Reel 1). The value is user defined.
PNLLOC Panel Location String, 30 This field is for the panel location of the I/O card or terminal strip
where signal is characters that sources the signal.
brought in maximum
PNLCOLID Panel Column ID String, four This field is for the column ID where the panel is located.
characters
maximum
PNL_NAME Panel Name String, 25 Enter the panel name.

characters
maximum
GEDWGREF General Electric String, five Enter the GE Drawing reference. It is the actual sheet number
Drawing characters where this I/O point shows up on the GE elementary.
Reference maximum
SDEVTYPE Source Device String, eight Enter the type of I/O card that sources the signal. This
Type characters information is useful for diagnostics.
maximum
SDEV_NAME Source Device String, eight Enter the name of the I/O card that sources the signal. This
Name characters information is useful for diagnostics.
maximum
SNET_NAME Source Network String, five This field is for the name of network that sources the signal.
Name characters This would normally be the I/O network (such as Genius). This
maximum information is useful for diagnostics.
Description
SDROP_NO Source Drop Numeric, three Enter drop number of the I/O card that sources the signal. This
Number significant digits information is useful for diagnostics.
SMOD_NO Source Module Numeric, three Enter the module number of the I/O card that sources the
Number significant digits signal. This information is useful for diagnostics.
SPOINT_NO Source Point Numeric, three Enter the point number of the I/O card that sources the signal.
Number significant digits This information is useful for diagnostics.
Msg_Class Message Class Numeric, three Status_S message class of the signal used only for (DLAN+)
(for DLAN+). significant digits Status_S signals. The message class is part of the Status_S
Refer to Table 3 broadcast or group command messages and is used by
for a list of the recipients to filter out commands that are not meant for them.
supported
message classes
for DLAN+.
Data Types
Table 2. Data Types Used By Toolbox
BOOL Boolean
BIT Boolean
INT Integer
DINT Double integer
LINT Long integer
UINT Unsigned integer
UDINT Unsigned double integer
ULINT Unsigned long integer
FLOAT Real
BYTE Bit string
WORD Bit string
DWORD Bit string
LWORD Bit string
CHRxxxxx Character (byte) array of length xxxx
TIME Time (hh.mm.ss) (24 hour day)
DATE Date (yyyy.mm.dd)
DATETIME Date and time (yyyy.mm.dd.hh.mm.ss)
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.
ACL controller
Application Control Layer controller. A form of the Innovation Series controller
hosted in the Innovation Series drive rack that performs job specific, outer layer,
drive control loops and sequencing.
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.
bind
The act of retrieving configuration information from some system database.
GEH-6403A Toolbox for a Mark VI Controller Glossary of Terms • G-1

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).
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.
datagrams
Messages sent from the controller to I/O blocks over the Genius network.
G-2 • Glossary of Terms GEH-6403A Toolbox for a Mark VI Controller

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.
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.
gateway
A device that connects two dissimilar LAN or connects a LAN to a wide-area
network (WAN), PC, or a mainframe. A gateway can perform protocol and
bandwidth conversion.
Genius bus
GE Fanuc’s 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.
µGENI 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 Task’s 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 controller’s 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 toolbox.
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 toolbox’s 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.
validate
Makes certain that items or devices do not contain errors and verifies that the
configuration is ready to be built into pcode.
VME controller
A form of the Innovation Series controller that is hosted in a Versa Module Eurocard
(VME) rack.
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 4, 8, or 16-bits long.

7R
*(,QGXVWULDO6\VWHPV
7HFKQLFDO3XEOLFDWLRQV5P
Problem Report 5RDQRNH%OYG

6DOHP9$86$
)D[
General Electric Company *(,QWHUQDO'&
Name Telephone Number
Company Name Fax Number
Address Job Site
GE Requisition Number
Name of Product:
Description of PC Hardware:
Brand Processor Type Processor Speed (MHz)
486 Pentium Other
Description of PC Software
Version (see Help, About Toolbox) Windows NT Version Amount of Memory
Problem Description (Describe problem thoroughly. Include sequence leading up to problem. If the program experienced a runtime
error, attach a printout of the error.log file contained in the tools directory).
Detach, fold, and mail − or fax this side only.

.........................................................................Fold here and close with staple or tape .........................................................................
Place
stamp
here
GE Motors & Industrial Systems

Product Service, Room 191
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
............................................................................................. Fold here first ..............................................................................................

7R
*(,QGXVWULDO6\VWHPV
5HDGHU&RPPHQWV 5RDQRNH%OYG
6DOHP9$86$
*HQHUDO(OHFWULF&RPSDQ\ )D[
*(,QWHUQDO'&
:HZHOFRPHFRPPHQWVDQGVXJJHVWLRQVWRPDNHWKLVSXEOLFDWLRQPRUHXVHIXO
<RXU1DPH 7RGD\¶V'DWH ,IQHHGHGKRZFDQZHFRQWDFW\RX"
)D[1R
<RXU&RPSDQ\¶V1DPHDQG$GGUHVV -RE6LWH
3KRQH1R
*(5HTXLVLWLRQ1R
(PDLO
<RXU-RE)XQFWLRQ+RZ<RX8VH7KLV3XEOLFDWLRQ 3XEOLFDWLRQ1R
$GGUHVV
3XEOLFDWLRQ,VVXH5HYLVLRQ'DWH
*HQHUDO5DWLQJ
([FHOOHQW *RRG )DLU 3RRU $GGLWLRQDO&RPPHQWV
&RQWHQWV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
2UJDQL]DWLRQ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
7HFKQLFDO$FFXUDF\ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
&ODULW\ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
&RPSOHWHQHVV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
'UDZLQJV)LJXUHV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
7DEOHV BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
5HIHUHQFLQJ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
5HDGDELOLW\ BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
6SHFLILF6XJJHVWLRQV&RUUHFWLRQVLQIRUPDWLRQWKDWFRXOGEHH[SDQGHGRQDQGVXFK
3DJH1R &RPPHQWV
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
______ __________________________________________________________________________________
2WKHU&RPPHQWV:KDW\RXOLNHZKDWFRXOGEHDGGHGKRZWRLPSURYHDQGVXFK BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB

___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
___________________________________________________________________________________________
2YHUDOOJUDGH&RPSDUHGWRSXEOLFDWLRQVIURPRWKHUPDQXIDFWXUHUVRIVLPLODUSURGXFWVKRZGR\RXUDWHWKLVSXEOLFDWLRQ"
6XSHULRU &RPSDUDEOH ,QIHULRU 'RQRWNQRZ &RPPHQW BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB
'HWDFKDQGID[RUPDLOWRWKHDGGUHVVQRWHGDERYH
)ROGKHUHDQGFORVHZLWKVWDSOHRUWDSH
BBBBBBBBBBBBBBBBBBBBBBBBBBBB 3ODFH
VWDPS
BBBBBBBBBBBBBBBBBBBBBBBBBBBB KHUH
BBBBBBBBBBBBBBBBBBBBBBBBBBBB
*(,QGXVWULDO&RQWURO6\VWHPV
5RDQRNH%OYG
6DOHP9$86$
)ROGKHUHILUVW

*(,QGXVWULDO6\VWHPV
*HQHUDO(OHFWULF&RPSDQ\
5RDQRNH%OYG
ZZZJHFRP 6DOHP9$86$

GEH-6403 Control System Toolbox Mark VI Turbine Controller

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GEH-6403 Control System Toolbox Mark VI Turbine Controller

Uploaded by

Copyright:

Available Formats



Control System Toolbox

Control System Toolbox

Printed in the United States of America.

ARCNET is a registered trademark of Datapoint Corporation.

Indicates a procedure or condition that, if not

Indicates a procedure or condition that, if not

Indicates a procedure or condition that should be

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

The example and setup screens in this manual do

Chapter 2 Installation 2-1

Chapter 3 Using the Toolbox 3-1

GEH-6403A Toolbox for a Mark VI Controller Contents • i

ii • Contents GEH-6403A Toolbox for a Mark VI Controller

Chapter 5 Finder 5-1

Chapter 6 Batch Operations 6-1

Chapter 7 File Checkin/Checkout 7-1

Chapter 8 Configuring System Information 8-1

Chapter 9 Graphics Window 9-1

GEH-6403A Toolbox for a Mark VI Controller Contents • iii

Chapter 10 Hardware and I/O 10-1

iv • Contents GEH-6403A Toolbox for a Mark VI Controller

Chapter 11 Configuring the Network Interface 11-1

Chapter 12 Signals and the Database 12-1

Appendix A System Database (SDB) Browser A-1

Glossary of Terms G-1

GEH-6403A Toolbox for a Mark VI Controller Contents • v

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

How To Use This Manual

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

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

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

Computer Requirements .......................................................................................... 2-2

GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 2 Installation • 2-1

Installing Control System Solutions

2-2 • Chapter 2 Installation GEH-6403A Toolbox for a Mark VI Turbine Controller

Enter the License Key number.

The destination directory for

This dialog box option can

GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 2 Installation • 2-3

Please read the entire

Click Yes to accept the

2-4 • Chapter 2 Installation GEH-6403A Toolbox for a Mark VI Turbine Controller

You must click to the left of each

Click the product name in the left

The number beside each product

A description of each product

Products that were not purchased as part of

1. Click Windows Start button, Settings and click Control Panel.

GEH-6403A Toolbox for a Mark VI Turbine Controller Chapter 2 Installation • 2-5

If you choose to remove all products by selecting

2-6 • Chapter 2 Installation GEH-6403A Toolbox for a Mark VI Turbine Controller

Upgrading from Previous Releases.......................................................................... 3-1

Upgrading from Previous Releases

Maintaining Multiple Releases of Toolbox

Migrating Files to Release 5

Using Controller Files

Accessing Online Help

Enter a three-character ID,

Change Password or Default Password Directory

Enter the old password

Enter the new password

Enter the new password