Toolbox ST

g GE Energy
GEH-6700
ToolboxST
for Mark VIe Control
ToolboxST
for Mark VIe Control
These instructions do not purport to cover all details or variations in equipment, nor to
provide for every possible contingency to be met during installation, operation, and
maintenance. The information is supplied for informational purposes only, and GE makes
no warranty as to the accuracy of the information included herein. Changes,
modifications, and/or improvements to equipment and specifications are made
periodically and these changes may or may not be reflected herein. It is understood that
GE may make changes, modifications, or improvements to the equipment referenced
herein or to the document itself at any time. This document is intended for trained
personnel familiar with the GE products referenced herein.
GE may have patents or pending patent applications covering subject matter in this
document. The furnishing of this document does not provide any license whatsoever to
any of these patents. All license inquiries should be directed to the address below. If
further information is desired, or if particular problems arise that are not covered
sufficiently for the purchasers purpose, the matter should be referred to:
GE Energy
Post Sales Service
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Phone: + 1 888 GE4 SERV (1 888 434 7378, United States)
+ 1 540 378 3280 (International)
Fax: + 1 540 387 8606 (All)
(+ indicates the international access code required when calling from outside the
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 Energy.
GE PROVIDES THE FOLLOWING DOCUMENT AND THE INFORMATION

INCLUDED THEREIN AS IS AND WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED STATUTORY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR PARTICULAR PURPOSE.
2004 by General Electric Company, USA.

All rights reserved.
CIMPLICITY is a registered trademark of GE Fanuc Automation, North America, Inc.

CompactFlash is a registered trademark of Sandisk Corporation.
CompactPCI is a registered trademark of PCIMG.
Ethernet is a registered trademark of Xerox Corporation.
Intel and Pentium are registered trademarks of Intel Corporation.
Modbus is a registered trademark of Schneider Automation,Inc.
TrueType is a registered trademark of Apple Computer, Inc.
Unix is a registered trademark of The Open Group.
Windows and Windows NT are registered trademarks of Microsoft Corporation.
Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not

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

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

strictly followed in order to optimize these applications.
Note Indicates an essential or important procedure, condition, or statement.
GEH-6700 ToolboxST Safety Symbol Legend a

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

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

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

equipment malfunction, only adequately trained personnel
should modify any programmable machine.
Note General ToolboxST commands, such as those in the File and Edit menus have
the same basic characteristics as Microsoft products. Only commands specific to
the ToolboxST products will be defined.
b Safety Symbol Legend GEH-6700 ToolboxST

g
To:
Reader Comments GE Energy

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

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

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

Contents
Chapter 1 About ToolboxST 1-1

Introduction ...............................................................................................................................................1-1
System Requirements ................................................................................................................................1-1
Installation.................................................................................................................................................1-2
Uninstall and Modify .....................................................................................................................1-3
Upgrading ......................................................................................................................................1-3
Licensing ...................................................................................................................................................1-6
Install the UPD...............................................................................................................................1-6
Reinstall UPD ................................................................................................................................1-6
Security .....................................................................................................................................................1-8
Passwords.......................................................................................................................................1-8
Viewing Protection Status..............................................................................................................1-9
Protected Objects .........................................................................................................................1-10
Apply or Change Password..........................................................................................................1-11
Password Caching ........................................................................................................................1-11
Chapter 2 System Configuration 2-1

System Editor ............................................................................................................................................2-1
Opening and Creating Systems ......................................................................................................2-1
Components ...................................................................................................................................2-4
Configuration Files ........................................................................................................................2-8
Menu Reference ...........................................................................................................................2-11
System Information Editor ......................................................................................................................2-12
Alarm Classes ..............................................................................................................................2-13
Format Specifications...................................................................................................................2-15
Measurement Systems..................................................................................................................2-17
System Database (SDB) ..........................................................................................................................2-17
External Device EGD Configuration ...........................................................................................2-18
Chapter 3 Component Editors 3-1

Summary View..........................................................................................................................................3-2
Property Editor ..........................................................................................................................................3-2
Component InfoView ................................................................................................................................3-3
Data Grids .................................................................................................................................................3-4
Editing Data ...................................................................................................................................3-4
Managing Columns ........................................................................................................................3-5
Copying and Moving Data .............................................................................................................3-6
GEH-6700 ToolboxST Contents i

Chapter 4 Finder 4-1
Find Methods.............................................................................................................................................4-2
Replace Options ........................................................................................................................................4-5
Chapter 5 Trender 5-1

Accessing a Trender Window....................................................................................................................5-1
Trender Window Features .........................................................................................................................5-2
Trender Toolbar .............................................................................................................................5-3
Data Toolbar...................................................................................................................................5-3
Working in Trender ...................................................................................................................................5-4
Acquiring Data ...............................................................................................................................5-4
Adding Traces ................................................................................................................................5-4
Live Trends ....................................................................................................................................5-4
Capture Buffer Trends....................................................................................................................5-5
Static File Trends ...........................................................................................................................5-5
Obtaining Data ...............................................................................................................................5-6
Trender Concepts.......................................................................................................................................5-7
Chapters .........................................................................................................................................5-7
Cursors ...........................................................................................................................................5-7
Value ScreenTips ...........................................................................................................................5-8
Events.............................................................................................................................................5-8
Working With Trender Data......................................................................................................................5-9
Graph View Options.......................................................................................................................5-9
Grid Lines.....................................................................................................................................5-10
Sample Markers ...........................................................................................................................5-10
Time Axis.....................................................................................................................................5-11
Traces ...........................................................................................................................................5-11
Auto-Range Trace ........................................................................................................................5-11
Manual Range Adjustment...........................................................................................................5-12
Trace Colors .................................................................................................................................5-12
Hiding Traces ...............................................................................................................................5-12
Statistical Calculations .................................................................................................................5-13
Exchanging Trender Data........................................................................................................................5-13
Exporting to a File........................................................................................................................5-13
Printing Graphs ............................................................................................................................5-14
Chapter 6 EGD Editor for External Devices 6-1

Overview ...................................................................................................................................................6-1
Network Adapters......................................................................................................................................6-1
EGD Configuration ...................................................................................................................................6-3
Produced Pages..........................................................................................................................................6-4
Editing Produced Pages.............................................................................................................................6-5
Page Compression .....................................................................................................................................6-6
Variables....................................................................................................................................................6-6
Editing Exchange Signatures and Configuration Time ..................................................................6-7
Referenced Devices ...................................................................................................................................6-8
Implementation Profile..............................................................................................................................6-9
Menus ......................................................................................................................................................6-11
File Menu .....................................................................................................................................6-11
Edit Menu.....................................................................................................................................6-11
View Menu...................................................................................................................................6-11
Device Menu ................................................................................................................................6-12
Help Menu....................................................................................................................................6-12
ii Contents GEH-6700 ToolboxST

Chapter 7 Tree File Importer 7-1
Overview ...................................................................................................................................................7-1
Running the Tree File Importer.................................................................................................................7-2
Chapter 8 Working Online With a Mark VIe 8-1

Connecting to a Controller ........................................................................................................................8-1
Status Tab..................................................................................................................................................8-2
Controller Attributes ......................................................................................................................8-3
Download to Controller.............................................................................................................................8-5
Download Command .....................................................................................................................8-5
Controller Initial Setup...................................................................................................................8-6
Download Wizard ..........................................................................................................................8-7
Upload Wizard .............................................................................................................................8-10
Controller Diagnostics.............................................................................................................................8-12
Administer Totalizers ..............................................................................................................................8-13
Totalizer Passwords .....................................................................................................................8-14
Modifying Totalizer Values .........................................................................................................8-16
Chapter 9 General 9-1

General Features........................................................................................................................................9-1
Attributes...................................................................................................................................................9-3
Attribute Value Editor ...............................................................................................................................9-4
Network Adapters .....................................................................................................................................9-5
Chapter 10 Hardware 10-1

Overview .................................................................................................................................................10-1
Network Redundancy ..............................................................................................................................10-2
Modules...................................................................................................................................................10-3
Adding Modules...........................................................................................................................10-3
Organizing Modules.....................................................................................................................10-6
Modify Module Configuration .....................................................................................................10-7
Summary View........................................................................................................................................10-8
Summary Tab...............................................................................................................................10-8
Parameters Tab.............................................................................................................................10-9
Internal Points Tab .......................................................................................................................10-9
Diagnostics Tab..........................................................................................................................10-10
Reporting...............................................................................................................................................10-10
Create I/O Report .......................................................................................................................10-10
Upgrade Module ........................................................................................................................10-12
Working Online.....................................................................................................................................10-13
Download Parameters ................................................................................................................10-13
Compare Parameters ..................................................................................................................10-13
Chapter 11 Software 11-1

Software Overview..................................................................................................................................11-1
Function Blocks ...........................................................................................................................11-2
User Blocks ..................................................................................................................................11-3
Programs ......................................................................................................................................11-5
User Block Definitions.................................................................................................................11-5
Library Container Editor .........................................................................................................................11-7
Overview......................................................................................................................................11-7
Library Container Editor/User Block Libraries..........................................................................11-11
GEH-6700 ToolboxST Contents iii

User Block Definitions...............................................................................................................11-13
User Block Variables .................................................................................................................11-14
Software Tab .........................................................................................................................................11-17
Programs Item ............................................................................................................................11-17
Creating a Program.....................................................................................................................11-20
User Block..................................................................................................................................11-25
Variable Editors .........................................................................................................................11-30
Table Definitions........................................................................................................................11-33
Block Diagram Editor............................................................................................................................11-40
View Mode.................................................................................................................................11-40
Edit Mode...................................................................................................................................11-41
Diagram Shortcut Menu .............................................................................................................11-42
Layout Modes.............................................................................................................................11-42
Managing Blocks .......................................................................................................................11-43
Wiring Block Pins ......................................................................................................................11-44
Block Shape Shortcut Menu.......................................................................................................11-45
Connecting Pins .........................................................................................................................11-46
Modifying Live Values ..............................................................................................................11-48
Shape Drawing Tools .................................................................................................................11-49
Additional Toolbar Buttons........................................................................................................11-52
Diagram Settings........................................................................................................................11-52
Rung Editor ................................................................................................................................11-54
Application Documentation...................................................................................................................11-58
Application Software Examples ............................................................................................................11-59
Chapter 12 DDR 12-1

Dynamic Data Recorder (DDR) ..............................................................................................................12-1
Configure DDR .......................................................................................................................................12-1
Status Variables .......................................................................................................................................12-4
Add Variables..........................................................................................................................................12-4
Update DDR ............................................................................................................................................12-5
Import and Export DDR ..........................................................................................................................12-6
Example Setup of DDR ...........................................................................................................................12-7
Chapter 13 Ethernet Global Data 13-1

EGD Configuration .................................................................................................................................13-1
Produced Pages........................................................................................................................................13-2
Editing Produced Pages...........................................................................................................................13-3
Page Compression ...................................................................................................................................13-4
Variables..................................................................................................................................................13-5
Referenced Devices .................................................................................................................................13-7
Chapter 14 Modbus Slave 14-1

Configure Modbus Slave.........................................................................................................................14-1
Modbus Slave Register Pages ......................................................................................................14-2
iv Contents GEH-6700 ToolboxST

Chapter 15 Mark VIe Tools 15-1
Reports ....................................................................................................................................................15-1
Report Types ................................................................................................................................15-1
Creating Reports ..........................................................................................................................15-3
Saving, Retrieving and Printing Reports......................................................................................15-4
Viewing Reports ..........................................................................................................................15-4
Filtering Rows..............................................................................................................................15-6
Finding Data.................................................................................................................................15-8
Importing an I/O Report from a CSV file ....................................................................................15-8
Forced Variables ...................................................................................................................................15-10
Global Variables....................................................................................................................................15-11
Watch Windows ....................................................................................................................................15-12
Managing Variables ...................................................................................................................15-13
Importing and Exporting ............................................................................................................15-13
Control Constants..................................................................................................................................15-14
Control Constants Window ........................................................................................................15-14
Importing and Exporting Control Constants ..............................................................................15-15
Chapter 16 Reference 16-1

Menus......................................................................................................................................................16-1
File Menu .....................................................................................................................................16-1
Edit Menu.....................................................................................................................................16-1
View Menu...................................................................................................................................16-2
Device Menu ................................................................................................................................16-3
Options Menu...............................................................................................................................16-3
Help Menu ...................................................................................................................................16-3
Glossary of Terms G-1
Index I-1
GEH-6700 ToolboxST Contents v

Notes
vi Contents GEH-6700 ToolboxST

Part 1
ToolboxST Overview
CHAPTER 1
Chapter 1 About ToolboxST
Introduction
The ToolboxST control system software includes a configuration application
and support packages for the Mark VIe controller and distributed I/O packs.
Before you install the software:
It is recommended that you exit all Windows programs.

All products are installed under a common folder on your hard disk. You
can define this location the first time you install ToolboxST, but any
subsequent releases will be installed to the previously defined location.
No license key is required to install this product, but to run ToolboxST after
installation, a valid hardware key (dongle) plugged into any Universal
Serial Bus (USB) port is required. Refer to the section, Licensing.
System Requirements
The following are minimum hardware and operating system requirements
needed to run ToolboxST.
Processor 500 MHz Pentium III
Operating System Microsoft Windows 2000
Memory 512 megabytes (MB) RAM
Hard drive 20 gigabytes (GB)
Monitor XGA display (1024 x 768 x 64K colors)
Drive CD-ROM or DVD-ROM drive
Network Ethernet network adapter
For assistance, contact:
GE Energy
General Electric Company
Post Sales Service
1501 Roanoke Blvd.
Phone 1 888 GE4 SERVE (888 434 7378, United States)
+1 540 378 3280 (international)
Fax +1 540 387 8606 (All)
(replace + with the international access code)
GEH-6700 ToolboxST Chapter 1 About ToolboxST 1-1

Installation
To install the software
1 Place the ToolboxST installation CD in the CD-ROM drive. The installation

starts automatically.
Note If the installation does not start automatically, from the Start menu run
the program GE ToolboxST Install.exe.
2 The Welcome dialog box displays. Click Next. The License

Agreement dialog box displays.
3 To continue the installation, you must accept this agreement. Select Agree.
4 Click Next. The User Information dialog box displays. Enter information
for this dialog box as appropriate.
5 Click Next. The Destination Folder dialog box displays. If this is the
first time ToolboxST has been installed on this PC, the browse button
allows you to change the default install location (C:\Program
Files\GE Energy\). If this is a subsequent installation, then this dialog
box informs you where this version of the product will be installed.
6 Click Next. The Select Features dialog box displays and allows you to
select which features to install or not install. All components will be
installed by default.
To select components not

to install, click the icon to
the left of the components
name and select the red X.
7 Once your selections are made, click the Next button until the installation
starts. Click the Finish button when the installation has completed
successfully.
1-2 Chapter 1 About ToolboxST GEH-6700 ToolboxST

Uninstall and Modify
To uninstall or modify ToolboxST
From the Start menu, select Settings, Control Panel, and then
Add/Remove Programs.
Use the scroll bar to

find, GE ToolboxST-
Vxx.xx.xx where
Vxx.xx.xx is the
component version.
Click Change to
add or remove
features from the
installation. Click
Remove to
uninstall.
Upgrading
You can install multiple versions of ToolboxST. When you install a new
version, the icons on the desktop and Start menu update to reflect the most
recently installed copy of ToolboxST.
The Add/Remove Programs control panel lists all installed versions of

ToolboxST. Once you install a newer version, you can remove previous versions
of the product from your computer unless you need to retain them for
compatibility.
Note Always install new versions of ToolboxST before uninstalling older

versions to preserve your personal settings.

To upgrade ToolboxST
1 Install the new version of ToolboxST. Refer to the section, Installation. The
icons on your desktop and in your Start menu will be updated to start the
most recently installed version.
2 From the Start menu, select Settings, Control Panel, and then
Add/Remove Programs.
Click the old version of

ToolboxST, and then
click the Remove button.
ToolboxST ships with software to support a variety of types of controllable

equipment. This support software contains updated firmware for the equipment
and configuration tools that are available as component editors inside a
ToolboxST system. When you install a new version of ToolboxST, newer
versions of component software may be installed as well. To use the new
versions of component software in an existing system, you must upgrade each
component separately.

To upgrade a component
1 Install new component software for the component type that you want to
upgrade by installing the latest version of ToolboxST.
2 Start ToolboxST and open the system file. Double-click a component to
open its component editor.
3 From the File menu, select Upgrade.
Click Next.
Select the new

version, and then
click Finish to
upgrade the
component.

Licensing
To use the ToolboxST control system software, you must purchase a license.
The license includes a hardware key, called a Universal Serial Bus (USB)
Protection Device (UPD). Hardware keys are also known as dongles.
USB Protection Device (UPD or dongle)
The UPD must be installed in an empty USB port on your computer. Each UPD
is programmed at the factory with one or more application keys that control
access to software products produced by GE. ToolboxST will only function if
your UPD contains a valid ToolboxST application key.
Install the UPD

It is very important to NOT plug the UPD into your
computer until after you have installed the ToolboxST
product.
To install the UPD
1 Install ToolboxST (refer to the section, Installation).

2 Plug the UPD into any empty USB port on your computer.
Only one UPD may be installed at a time. If you have valid licenses for more
than one product, your UPD must contain a valid application key for each
product.
Note If you install the UPD before installing ToolboxST, the device may appear
to be installed, but it will not be associated with the correct drivers. You can
correct this after ToolboxST is installed with the Reinstall UPD procedure.
Reinstall UPD
To reinstall the UPD
1 Save and close any open applications/systems.

2 Unplug the UPD.
3 From Windows, click Start, Settings, and then select Control Panel.
4 From the Control Panel, select Administrative Tools and Computer
Management and use the Device Manager to reinstall the UPD.
5 Reinstall the UPD. Windows should now detect the UPD and reinstall it
with the correct drivers.

6 To make sure that the UPD is correctly installed and your ToolboxST
installation is correctly licensed, start ToolboxST. If the installation is not
correct, the following dialog box displays.
Check that you have

installed the proper UPD
correctly and click Retry.

Security
The security provided in ToolboxST is based on passwords entered by the user.
Passwords ensure that only authorized persons who know the correct
password(s) can view or make changes to system components.
There are three different kinds of protection available called Access Rights.
Modify Data allows you to make changes to data values associated with an
object without changing how it works. For example, Modify Data protects
the initial value of a variable defined in a Mark VIe controller. The purpose
of this right is generally to keep unauthorized persons from making unsafe
changes to settings.
View Design allows you to view the internal design of a protected object.
For example, View Design protects the internal design of a library block.
The purpose of this right is to protect intellectual property from
unauthorized persons.
Modify Design allows you to change the way a protected object works.
For example, Modify Design protects block creation and editing of
connections within a library block diagram. The purpose of this right is to
limit the ability to change how the system works to authorized persons.
A protected object can have one or more of these access rights. Each right can
have a different password set on it. Some objects can be protected if they are
contained in another parent object, which is protected by its own password(s).
Passwords
Whenever you attempt to perform an operation on an object that is protected, the
Enter Password dialog box displays.
The title bar displays the

access right that is protected.
Protected Location displays

the object that is protected.
Even if an object is not directly
protected, it can be contained
within another object that is
protected. This box clarifies
which object is requesting a
password.
Enter the password and

click OK.
Note Passwords are case-sensitive 'secret' and 'Secret' are not considered to be
the same password.

Viewing Protection Status
The protection status for an object displays in the Property Editor for that
object. The following example shows the protection for a User Block Library.
From the Property

Editor, expand the
Protection item to
display that all
three access rights
are available for
User Block
Library Lib1.
To view the design of

blocks in this library,
you must know the
View Design
password.
There are four possible status indications for each access right:
No password has been set on this object and none is
required
A password has been set on this object and has not
been entered
A password has been set on this object, but has
already been entered
A password has been set on this objects parent, but
has not been entered

Protected Objects
This section describes items that can be protected and the relationships between
them. For example, the specific actions that are governed by each access right
depend on the specific component type. See the individual component
documentation for more details.
System can only have a Modify Design password. If present, it prevents you
from adding or deleting system components.
Device can have Modify Data and Modify Design passwords. Modify Data
prevents the user from saving changes or changing initial values for variables
defined in the component's application software. Modify Design prevents the
user from modifying any aspect of the hardware or software configuration for
the component.
User Block Library can have passwords for all three access rights. They have
no direct effect on the block library, but are inherited by all block definitions
within that library.
User Block Definition can have passwords for all three access rights. If block
passwords are not applied, the passwords on the library container will apply to
the definition.
User Block Instanced in a program can be given its own passwords for
Modify Data, Modify Design or View Design. If none are assigned, it takes on
the Modify Data and Modify Design protection for the parent component. The
passwords assigned to an instance of some block in a user block library will
initially be set to the passwords that were in force in the definition of that block.
Once instanced though, any changes to the protection on the block definition
will not propagate to instances of that block.

Apply or Change Password
To change an existing password
1 From the Property Editor, expand the Protection item.

2 Select the desired access right, such as modify data, and then click the
Ellipsis button. If there is already a password on that access right and it
has not yet been entered, you will first be asked for the password before
being allowed to change it. The Change Modify Data Password dialog
opens.
The title bar indicates

which access right the
change will apply to,
such as, Modify Data.
Enter the new password

twice in order to
safeguard against typing
errors. A valid password
consists of six or more
Click OK to apply
characters, letters or
the change.
numbers, and is case-
sensitive.
Password Caching
The security system caches passwords that have been previously entered so that
once you enter a unique password, you dont have to enter that password again.
Separate caches are maintained for the system and each major component (such
as a Library Container or a Device). A cached password remains until the
component is closed.
Tip If you have performed an operation in ToolboxST that requires entering

a password, it is recommended to close the protected component when you are
done so that an unauthorized user does not gain inappropriate access.

Notes

CHAPTER 2
Chapter 2 System Configuration
System Editor
When you start ToolboxST, the first window that displays is an empty System
Editor.
Before you can begin using ToolboxST, you must create or open a system.
Systems contain components, which are the basic unit representing devices or
tools in the system. A system is stored in its own folder on disk, which contains
both a .tcw configuration file and a collection of supporting files and folders
representing the system components. (For more information about the folder
structure of a system, refer to the section, Configuration Files.)
Opening and Creating Systems

To create a new system
1 From the File menu, select New System to display the New System
dialog box.
GEH-6700 ToolboxST Chapter 2 System Configuration 2-1

2 Specify the working directory to contain the new system by typing in a path
or by clicking the Browse button. (If you enter a path that does not exist,
ToolboxST creates it for you.)
3 Enter a name for the system. You can refer to the Existing Systems list
to help you select a name that is not already in use. (Some characters are
prohibited; if you enter an invalid character, a small red exclamation mark is
displayed.)
4 Click OK to create the new system. The new system is created and opened
in the System Editor.
2-2 Chapter 2 System Configuration GEH-6700 ToolboxST

To open an existing system
1 From the File menu, select Open System.

2 Locate the .tcw configuration file for the system and select Open. The
system displays in the System Editor.
When a system is open, the System Editor displays overview information

about the components in the system. The window consists of three major areas
as displayed.
Tree View
displays a list of Summary View
all components displays a graphic
in the system.
representation of all
Click the + and
system components
- symbols to
and their network
expand and
connectivity.
collapse groups.
Property Editor
allows you to edit
settings for the
selected
component.

Components
Systems consist of multiple components. Components display in both the Tree
View and the Summary View of the System Editor. Since the System Editor
serves as a navigation tool to open more detailed Component Editors for editing
or viewing system components, you can double-click most components to edit
them.
A list of common components and the icon that represents them in the Tree
View is as follows:
Icon Component
System
Group of Components
Printer
Library Container
Network
Trender Window
External Device (not associated with an application)
You can add components to the root component of a system (represented by the
icon) or a group (represented by a icon). Some components display a
wizard or dialog box that prompts you for additional information when you add
them to the system.

To add a component
In the Tree View, right-click a parent component (either a system or a

group), select Insert New, and then select the desired component type.
Existing components can also be imported from a file.
To import an existing component

group), select Insert Existing, and then select Device. Select the Device
.xml file for the component to be imported and click Open.
To import an existing library container

group), select Insert Existing, and then select Library Container. Select
the Library .xml file for the component to be imported and click Open.
To open the editor for a component
In the Tree View, select a component. Then, from the Edit menu, select
Selected Component.
Or,
In the Tree View or Summary View, double-click a component.
Grouping Components
ToolboxST provides a special component called group, to help you organize
system components. Groups are similar to file folders in that they can contain
one or more other components (including additional groups). You can use
groups to create any organizational system that you like, including division by
physical component location and a variety of logical divisions.
Groups

Moving and Copying Components
Components can be moved within a ToolboxST system using a drag-and drop
operation. Drag-and-drop editing is only available if the System Editor is in
View By Group mode, as the components are automatically organized when
View By Type mode is selected. The default drag-and-drop operation for most
components is move. Some components support a secondary drag-and-drop
operation (usually copy) that can be accessed by holding down the CTRL key
while dragging.
The cursor changes to one of the following cursors during a drag-and-drop

operation to indicate the predicted outcome of the operation:
indicates that the item being dragged cannot be dropped at the location
currently beneath the cursor.
indicates that the item being dragged will be moved to the location
beneath the cursor.
indicates that the item being dragged will be copied and the copy will be
placed at the location beneath the cursor
Most components can be moved and copied in the Tree View, with a few
exceptions:
Library Containers can not be contained inside groups, so they can only be
copied to the system item and can never be moved.
When a group is copied, a new group is created. The contents of the old
group remain in place and are not copied to the new group.
No drag-and-drop operations are supported for networks.
Tip You can import components and Library Containers from either another
copy of ToolboxST or from the Windows file system using drag-and-drop
operations. (To import from the file system, drag the Device.xml or Library.xml
file that represents the component.)

External Device Configuration
When you add an External Device to the system, you must configure the
component with information about both the external application and the
configuration file connected to the device. When an External Device is properly
configured, the external application starts and opens the configuration device
when the component is double-clicked in ToolboxST.
If the configuration for the external device is stored in a file with a special
extension (for example, .m6b for a Mark VI device), you can specify the path to
the configuration file and omit the path to the external application. ToolboxST
will automatically open the application associated with the configuration file. In
all other cases, you must specify the exact application to be run for the external
device.
To configure an external device
1 From the Tree View, select an External Device to configure. (External

devices that have not been configured are represented by a question mark
icon.)
2 In the Property Editor, select the App Path item. Click the ellipsis
button at the right side of the text field to display the Open dialog box.
3 Locate the application executable file used to configure the device, and then
click Open. The App Path property is updated to reflect the new path.
Optional procedures:
If the External Device requires a specific configuration file, select the Doc
Path item and provide the location of the file.
If the External Device application requires switches (which are provided to
the external application on the command line before the contents of Doc
Path), configure the Switches property.
If the External Device application requires a specific working directory
(which is the folder assumed when no path is specified), configure the Start
Directory property.
If the External Device supports Ethernet Global Data (EGD), set the Enable
EGD Editor property to True.

Saving Systems
When you make changes to a system, the changes are stored in memory. If you
do not save your work regularly, your changes will be lost.
In ToolboxST, Save commands affect only the data in the current editor. As
such, the Save command in the System Editor only saves changes to the
system itself. If you have made changes in any other component editors (like a
controller or a library container), you must select the Save command in each of
those editors as well.
To save changes to the current system
From the File menu, select Save System. (Or, click the button on
the toolbar.)
Configuration Files
Folder Structure
Each system is saved in its own folder. Inside the main system folder is a set of
subfolders and configuration files. The folder structure depends on the
components in the currently opened system. A typical system and its associated
file structure is as follows:
System Editor Tree View Windows Explorer Folder View

System Folder is the top-level folder that contains all others. It always has the
same name as the system. (In the example for this section, the System Folder is
named System1.) Files in the folder include:
System1.tcw, containing top-level information for each component in the

system.
FormatSpecifications.xml, containing Format Specifications that define
units and scaling information for data display.
SystemDiagram.xml, containing information about the system block
diagram including both the basic diagram structure and additional drawing
shapes that have been added.
Component Folders contain configuration files for each component in the
system. In the example system, the G1 folder corresponds to a Mark VIe
controller named G1. The exact structure of each Component Folder varies with
the type of component, but all Component Folders have a Device.xml file that
contains basic information about the component.
Library Container Folders are created for each Library Container in the
system. In the example system, the Library Container named Libraries is stored
in a folder correspondingly named Libraries. Objects in this folder include:
Library.xml, containing attributes of the Library Container and a listing of

all libraries.
_Mylibname.xml, a file created for each library in the Container (where
Mylibname is the name of the library).
BlockwareDiagrams, a folder containing the diagrams for user blocks
defined in each library.
Tools Folder contains definitions for all tool components in a system. A folder
for each type of tool is contained inside the Tools Folder. In the example, the
system contains a Trender window, so a TrendRecorder folder is stored inside
the tools folder. Inside the folders for each tool type are additional folders for
each instance of the tool. Since the example system has one Trender window
named Trender1, a single Trender1 folder is stored inside the TrendRecorder
folder.

File Formats
All configuration data for ToolboxST is stored in eXtensible Markup Language
(XML) format.
While XML files can be opened and read in a text

editor, do not modify them. XML files modified using a
text editor do not work with ToolboxST.
Configuration files can be both compressed and encrypted. If you select the
Compress When Saving option in the System Options dialog box, the
configuration data is stored in a compressed format that is not readable with a
text editor but occupies much less disk space. Some portions of XML
configuration files may be also stored in encrypted format to prevent
unauthorized users from viewing the design of password-protected system
components.
Some controller components support a Build operation that produces files to be

downloaded directly to the controller. These files, which are stored in the Output
folder of a component, are in a binary format and are not human readable.
System Options
ToolboxST provides a variety of settings that change the way various functions
operate. While you can also configure settings from inside the component that
they affect, settings for all available components display when the Settings
dialog box is opened from the System Editor.
To open the Settings dialog box
From the System Editor, select the Options menu, and then select
Settings to display the Settings dialog box.
In the Settings dialog box, categories are listed in a Tree View on the left side
of the dialog box. Each category contains one or more settings that display in the
Property Editor on the right side of the dialog box.

The System Options category includes options that affect the system as a
whole. It is available in addition to any other component settings that may
display in the Tree View.
AutoBackup - When set to True, a backup copy of all configuration (.xml)

files is made when configuration changes are saved. The backup files are
automatically named using the format Backup of (original name).xml and are
stored in the same location as the original file.
Compress When Saving - When set to True, ToolboxST compresses most

configuration (.xml) files to save space. Device.xml files are not compressed
even if this option is set to True.
Maximum Build Errors Certain configuration problems can cause a very

large number of error messages to be generated during a build operation. This
option controls how many such errors can occur before the build operation is
stopped.
Menu Reference
File Menu
New System creates a new system.
Open System opens a previously created system.
Close System closes the current system.

Save System saves changes to the current system (but not to any
other component editors).
Save System As saves the current system to a new location or
name.
Recent Files lists the eight most recently accessed systems.
Exit closes ToolboxST and all component editors.
Edit Menu
Delete removes the item currently selected in the Tree View.
Insert New adds a new component to the system.

Insert Existing adds an existing component from a folder on disk.
System Information displays the System Information Editor.
Selected Component displays the Component Editor for the item
currently selected in the Tree View.
View Menu
By Type automatically organizes the Tree View by component
type.
By Group enables manual organization of the Tree View with
group components.
Track keeps selections in the Tree View and Summary View
synchronized.
Launch EMT opens the Ethernet Global Data (EGD) Management
Tool (EMT).

Options Menu
Settings displays a dialog box with system settings.
Window Menu
Cascade arranges open Component Editor windows in a layered
style.
Tile arranges open Component Editor windows in a grid style.
Close All closes all open Component Editor windows.
Help Menu
Contents displays the online product documentation.
Release Notes displays up-to-date information about your version
of ToolboxST.
Send Problem Report lets you send problems and suggestions to
the ToolboxST team.
About displays version and copyright information.
System Information Editor

The System Information Editor edits Alarm Classes and Format Specifications
that are available to all components in the system. If access to a System
Database (SDB) is enabled, the contents of the System Information Editor can
be stored to the SDB.
To open the System Information Editor
From the System Editor, select System Information from the Edit
menu.
Or,
From the System Editor, double-click the System item in the Tree
View.

Alarm Classes
Alarm classes are groups or collections of related alarms that share a common
priority and color scheme.
To edit Alarm Classes
1 Open the System Editor. From the Edit menu, select System
Information.
2 From the Tree View, select Alarm Classes. A data grid with the existing
Alarm Classes displays in the Summary View.
Click the Name box in the append

row and enter a new name to add Click in a grid cell to edit its
a new format specification. contents.
The properties from

the Summary View
also display in the
Property Editor for
the currently selected
row(s).

The following properties are available in the Property Editor when an Alarm
Class is selected:
Name: Name of the Alarm Class. Limited to 5 characters if using an SDB.
Description: The Alarm Classes description. Only the first 50 characters are
stored in an SDB.
Priority: Alarm class priority (0 to 99 where 0 is the highest priority)
Ack Foreground Color: Foreground color for an alarm in the Acknowledged
state.
Ack Background Color: Background color for an alarm in the
Acknowledged state.
Alarm Foreground Color: Foreground color for an alarm in the Alarm state.
Alarm Background Color: Background color for an alarm in the Alarm
state.
Normal Foreground Color: Foreground color for an alarm in the Normal
state.
Normal Background Color: Background color for an alarm in the Normal
state.

Format Specifications
Format specifications control how variables are presented in an HMI. Format
specifications are grouped into sets, which establish a relationship between
different measurement systems for a particular type of data. For example, a
Format Specification Set for temperature could contain two specifications for
temperature one for degrees Fahrenheit in the U.S. measurement system and
one for degrees Celsius in the International System of Units (commonly referred
to as the Metric system).
The Engineering Min and Max values for both format specifications control the
conversions that take place when a measurement system is selected at an HMI.
For example, if a temperature variable is assigned to the Celsius format
specification and the measurement system in use on the HMI is Metric, no
conversion is performed on the HMI displayed value. If the HMIs
measurement system is changed to U.S., the value of the variable is converted
from Celsius to Fahrenheit using the linear equation defined by the Engineering
Min and Max of the Celsius and Fahrenheit format specifications. Variables are
scaled as follows by the HMI:
(val fs1 fs1min ) ( fs 2 max fs 2 min )

Val = + fs 2 min
( fs1max fs1min )
fs 2
Val fs 2 : The converted value, in Format Specification 2
Val fs1 : The initial value, in Format Specification 1
fs1max : The engineering max for Format Specification 1
fs 1min : The engineering min for Format Specification 1
fs 2 max : The engineering max for Format Specification 2
fs 2 min : The engineering min for Format Specification 2
Using this formula, a conversion from Celsius to Fahrenheit would be calculated

by the HMI as follows:
(val o c fs oCmin ) ( fs oFmax fs oFmin )

Val o F = + fs o Fmin
( fs Cmax fs Cmin )
o o
(val o c 0) ( 212 32)

Val o F = + 32
(100 0)
Within a Format Specification Set, all Engineering Min values must represent
the same physical value and all Engineering Max values must represent the same
physical value. (In the previous example, the min for Fahrenheit (32) and the
min for Celsius (0) represent the same temperature, the freezing point of water.)

To create a Format Specification Set
1 From the System Editor Edit menu, select System Information.

2 In the System Information Editor, right-click the Format
Specification Sets item in the Tree View and select Add Format
Specification Set.
3 Enter a name for the new set and click OK.
To add format specifications to a Format Specification Set
1 From the System Editor Edit Menu, select System Information.

2 In the System Information Editor Tree View, click a Format
Specification Set. A grid of format specifications displays in the
Summary View.
Click the Name box in the append

row and enter a new name to add a
new format specification. Click in a grid cell to edit its contents.
The properties from

the Summary View
also display in the
Property Editor for
the currently
selected row(s).
The following properties are available in the Property Editor when a Format
Specification Set is selected:
Format Spec Set: The Format Specification Set that contains the selected
format specification.
Precision: The number of digits to display to the right of the decimal point (for
example, a precision of two displays the fraction 1/3 as .33).
Engineering Max: The maximum value of the range used for unit conversions.
Engineering Min: The minimum value of the range used for unit conversions.
Units: The text that displays to identify the format specification unit.
Measurement System: The measurement system (for example, Metric or
U.S.) to which the unit belongs. (Refer to the section, Measurement Systems.)
Name: A unique name for the format specification. If the system data is Put to
an SDB, a limit of 12 characters is enforced for the Name.

Measurement Systems
Each format specification is assigned to a measurement system. Within a format
set, which represents a particular type of measurement (like temperature), only
one unit per measurement system can be created. (For example, you could not
add both Celsius and Kelvin within the Metric system as units of temperature.)
You can select the two measurement systems that are stored in the System
Database (SDB) in the System Information Editor.
To select the measurement systems used by the SDB
1 In the System Information Editor Tree View, select Format

Specification Sets.
2 Click SDB Meas Sys 1 or SDB Meas Sys 2 in the Property Editor,
then select a measurement system from the drop-down list.
System Database (SDB)

ToolboxST can interface with an SDB from the System Editor.
Click the System item in

the Tree View to access
SDB properties.
This property must be set

to True before other SDB
properties can be
configured.
The host name where

the SDB is located.
The path where the

SDB is located.
The ToolboxST system configuration for Alarm Classes and Format

Specifications can be stored, or put, to an SDB from the System Information
Editor.

To put the system configuration to a System Database (SDB)
1 Open the System Information Editor. From the System menu, select
Put System to SDB. (For more information on opening the System
Information Editor, refer to the section, System Information Editor.)
2 A dialog box displays confirming the destination SDB Host and Path. Click
OK. When it is complete, the results display on the Log tab of the
InfoView.
External Device EGD Configuration

The EGD configuration for a device in the System Database (SDB) can be
retrieved for use in a ToolboxST system. Before you can reference an external
device in the SDB, the SDB Enable property of the system must be set to True.
(Refer to the section, System Database.)
To get an external devices EGD configuration from the SDB
1 If the external device does not already exist as a ToolboxST component,

create a component to represent it. Refer to the section, External Device
Configuration.
2 Select the external device in the System Editor Tree View. The
component properties display in the Property Editor.
3 Set the Enable Get from SDB property to True.
4 Right-click the external device in the Tree View and select Get EGD
from SDB. A dialog box displays confirming the destination SDB Host and
Path.
5 Click OK to proceed with the Get EGD from SDB operation. When it is
complete, the results display on the Log tab of the InfoView.
Note If the EGD Configuration Server option is enabled for the system, the
EGD configuration will also be put to the EGD Configuration server.

CHAPTER 3
Chapter 3 Component Editors
Components in a ToolboxST system are configured using a Component Editor.

When a component is opened, a number of common features are available to
assist with the configuration process.
To open a Component Editor
From the Tree View, double-click a component.
Summary View provides an overview of the item

selected in the Tree View . It can be used to monitor or
edit an item.
Tabbed pages organize the

different elements of the
components configuration.
Tree View lists all major

items in the component.
The list of items change
when a different tab is
selected.
Property Editor
provides an easy and
consistent means to edit
the item selected in the
Tree or Summary View
Component InfoView
displays specific feedback
information of the currently
selected tab.
To edit the component
From the Component Editor, click an item in the Tree View. The
configuration information for that item displays in the Summary View and
Property Editor.
GEH-6700 ToolboxST Chapter 3 Component Editors 3-1

Summary View
The information displayed in the Summary View depends on the item selected
in the Tree View. There are many types of summary views ranging from the
block diagram, which is specialized to edit application software, to simple lists
of referenced files where no editing is possible.
Property Editor
The Property Editor allows you to view and edit the properties of the selected
item. Properties are named values associated with the selected item. The
configuration item displays in the left field and the value displays in the right
field.
Min-Max button allows you to

Double-click this double
quickly resize the Tree
bar to view the Property
View and Property Editor
Editor in a separate
within their shared view.
detached window.
List by Category button allows Alphabetical List button

you to view the list of the allows you to view the list
properties organized according of the properties arranged
to categories. alphabetically by name.
To edit a property in the Property Editor
From the Property Editor, select an item by clicking its value field. The
field can display several options:
Click the ellipsis button to change the value from a dialog box.
Click the drop-down list button to change the value from a drop-down list.
If no button displays, edit the value directly in the corresponding text box on the
right side of the Property editor.
3-2 Chapter 3 Component Editors GEH-6700 ToolboxST

Component InfoView
The Component InfoView always contains the following five tabs that provide
status information. (Depending on the open component type, additional tabs
may also be available.)
Log tab displays messages related to user commands issued in ToolboxST. For
example, if you prepare to download a controller and click the Build command,
messages describing the results of the Build process display in this tab page.
Tip If there is a build problem, the error is listed on the Log tab. Double-
click the error. The input focus goes to the code that caused the error to occur.
The Summary View displays the block diagram and the block variable with
the problem highlighted.
History tab keeps a navigation history for each user session and allows you to
return to different places in the editor. Each time an item is selected in the Tree
View or Summary View the name of that item is added to the top of this list.
Where Used tab tracks variables in the Tree View or Summary View and
displays all other places in the controller where they are used.
Tip From the Where Used tab, double-click the desired item. The input
focus goes to the view represented by that line and the item is selected.
The write icon that displays at the beginning of some lines indicates that the
variable is being written at that location.
Find Results tab displays the results of the Finder. Refer to the section,
Finder.
Info tab displays context-sensitive descriptions for the selected Tree View or
Summary View item.

Data Grids
Data Grids are used to view or edit many of the configuration properties
available in ToolboxST component editors. While each Data Grid contains
different columns and properties, several features are common to all Data Grids,
including column resizing, clipboard operations, and multi-row editing.
Note Some Data Grids, especially those without an Append Row, may not
support all features described in this chapter.
Sort indicator Drag borders to Column

Click to select
resize columns headers
entire grid.
Row
headers
Currently
selected row
Append
row
Selected cell
Editing Data
To... Do this:
Edit a text or numeric

value Left-click inside the cell to be modified. The cell will
change into a text box. Edit the contents of the cell as desired, and then press
Enter to save your changes.
Edit an enumerated
value Left-click inside the cell to be modified. The cell will
change into a drop-down list. Click the down arrow and select the desired value for
the cell.
Edit a complex value
Left-click inside the cell to be modified. The cell will
change into a text box with an ellipsis button, indicating that a dialog box is
available to change the cell contents. To display the dialog box, click the
ellipsis button.
Quickly set a property Left-click the row header for the first row to be edited. Then, while pressing the
to the same value for CTRL key, left-click added row headers. After selecting all desired rows, use the
multiple rows Property Editor to change properties for all selected rows. (Some properties are
omitted when a group of rows is selected, and properties with conflicting values will
display no value in the property editor.)

Managing Columns
Many aspects of a data grids columns are available for customization. You can
select the columns that display, their order from left to right, their width and the
sort criteria.
To... Do this:
Resize a column Drag the vertical bar on the right of the column header to a new location.
Quickly remove a single Right-click the column header and select Hide Column.
column
Move a column to a different Drag the column header to a new location.
location
Sort by a column Click a column header. The column will sort in ascending order. To sort
in descending order, click the column header again.
Reset columns to the original Right-click any column header and select Default Column Organization.
configuration
Add or remove columns Right-click any column header and select Organize Columns to display
the Organize Columns dialog box. (See below)
Add all available

columns to the
data grid.
Add selected
columns to
the data grid.
Move the selected
column up or down
in the column
Remove selected order.
columns from the
data grid.
Remove all
columns from the
data grid.

Copying and Moving Data
To Do this:
Copy and paste a single row Right-click the header for the source row and select Copy Selected/Current
Rows to place the source row on the clipboard. Then, right-click the header for
the append row in the destination grid and select Paste Row(s) to
insert the row into its new location.
Copy and paste multiple Left-click the row header for the first source row. Then, while pressing the
rows CTRL key, left-click added row headers. After selecting all desired rows,
continue to hold down the CTRL key and right-click any selected header.
From the shortcut menu, select Copy Selected/Current Rows to place the
rows on the clipboard. Then, right-click the header for the append row
in the destination grid and select Paste Row(s) to insert the rows into their
new location.
Copy and paste a range of Click the top left cell of the desired range and drag to the bottom right cell.
two or more cells Right-click the selected region and select Copy Selected/Current Rows to
place the cells on the clipboard. Then, click the top left cell of the destination
range and drag to select the same number of columns and rows that were
copied to the clipboard. Right-click inside the destination region and select
Paste Row(s).
Move rows between data Arrange windows on screen so both the source and destination grid are
grids visible. (An entry in a Tree View is acceptable as a destination) Left click the
row header for the first row. Then, while pressing CTRL, click any added row
headers to be moved. Release the CTRL key and drag a row header to the
new data grid.
Add a variable to a block Arrange windows on screen so both the source grid and a destination block
diagram, Trender window or diagram, Trender window or watch window are visible. Then, drag the row
Watch Window from a data header for the variable to the destination window.
grid
Tip You can copy and paste rows between different data grids if the columns
match by following the above procedures and navigating to a different data grid
before pasting the data.
Tip Cells in a data grid can also be copied to and pasted from Microsoft
Excel. The copied data is stored in CSV (comma separated value) format, which
contains no information about column names. To make sure pasted data is
placed into the proper columns, do not change column ordering and always
select the exact destination range in ToolboxST before pasting data from Excel.

CHAPTER 4
Chapter 4 Finder
The Finder provides a powerful way to search items in a ToolboxST system. It

can be used to locate an item in a large system or to rapidly search through
descriptions of many items.
To open the Finder
From the toolbar, click the Finder button.
-or-
From the Edit menu, select Find.
Enter the text to Selects a type of search to Displays a shortcut

search for in this perform. (Refer to the menu of available
box. section, Find Methods) wildcards.
Click to begin the
Select this box to search process.
distinguish between
upper and lower case
characters while
searching. Click to display
added options for
Select to include replacing text.
variable descriptions
in the search.
Searches every
component from the
Select to include libraries System Editor, even
in the search if the scope those without open
is set to Entire system or component editors.
Open Components and
a library editor is open.
Searches all
components from
Select to include items Searches inside the Searches inside the currently the System Editor
in block diagrams (the current component. (The selected item (for example, a with open
as text comments) in name of the component software program.) If no component editors.
the search. will display next to the searchable item is selected when
option button.) the Finder is opened, this option
is disabled.
When a search is completed, the results are displayed on the Find Results tab of
the Component InfoView. To jump directly to a location, double-click it in the
list.
GEH-6700 ToolboxST Chapter 4 Finder 4-1

Find Methods
A variety of find methods are available that control how the text entered in the
Find box is matched to text in the ToolboxST system.
Anywhere finds the specified text anywhere within a searchable text string.
A search for matches but does not match:
abc abc abdc
abcde ab
xyzabc bc
zabcz
Begins with finds the specified text only at the beginning of a searchable text
string.
abc abc xyzabc
abcde abdc
ab
bc
Ends with finds the specified text only at the end of a searchable text string.
abc abc abcde
abdc
xyzabc ab
bc
Match Exactly finds the specified text only when it is exactly equal to an
entire searchable text string.
abc abc abcde
xyzabc
abdc
ab
bc
abc cde
4-2 Chapter 4 Finder GEH-6700 ToolboxST

Match Whole Word finds the named text only when it is exactly equal to an
entire word of a searchable text string, meaning it is surrounded on both sides by
either punctuation or white space.
abc abc abcde
abc cde xyzabc
spell your abc's. abdc
ab
bc
spell your abcs.
Wildcards is similar to Match Exactly, except any single letter can substitute
for a ? character and any sequence of zero or more letters can substitute for a *
character.
a?c abc abdc
adc bc
abc cde
abcde
xyzabc
a* abc bc
adc cde abc
abcde
abdc
ab
abc cde

Regular Expressions processes the text entered in the Find box as a regular
expression (sometimes abbreviated regex). A regular expression is an advanced
system of wildcards used to match a specific set of text. ToolboxST supports a
standard set of regular expression commands similar to many popular third party
tools. While a detailed discussion of regular expression syntax is out of the
scope of this document, there are many excellent books and online resources
available with details about regular expressions.
[cvrm]at cat sat
cats bat
vat
rat
mat
(Mon|Tues|Wednes|Thurs|Fri)day Monday Saturday
Tuesday Sunday
Wednesday Fries
Thursday
Friday
Fridays
var[0-9]+ var0 varx
var9
var7 var
var48
Var($|(a-zA-Z)+) var var5
variable var!
varZZZZ

Replace Options
Besides performing simple searches, the Finder also supports search-and-replace
operations.
To display the Replace options
In the Finder window, click the Replace button. The window expands to
include new options.
Enter the text to be Replaces the currently Navigate to the

substituted for the displayed occurrence next occurrence
find text in this box. of the find text with the of the find text.
Replace With text.
Replaces all occurrences of

the find text with the Replace
With text automatically.

Notes

CHAPTER 5
Chapter 5 Trender
The Trender is a tool that is used to capture and display trend graphs of variables
in the system. It can collect and display values in real-time from controllers and
other sources, and can display data collected by high-speed coherent data
collection systems, such as capture buffers and dynamic data recorders. The
Trender also can display previously captured data from a saved data file.
Accessing a Trender Window

Before you can analyze data trends, you must first open a Trender window in the
Trender. A Trender window is a collection of traces and data that is saved
between uses. You can open a Trender window in one of two ways from inside
ToolboxST or separately from the Start menu. If you open a Trender window
from inside ToolboxST, the window is stored inside either a Component or the
System itself, and you can create as many Trender windows as necessary. If you
open the Trender from the Start menu, files are saved with a .trend extension.
To create a new Trender window or open an existing Trender

window
1 If the Trender application is not already open, select the Windows Start
button, then Programs, GE ToolboxST, ToolboxST, and then select
Trender.
2 From the File menu, select New to create a new Trender window.
-or-
From the File menu, select Open and locate an existing trend file.
To create or open a Trender window from a ToolboxST

component
1 From ToolboxST, navigate to the Component Editor for the

Component that contains the variables you would like to monitor.
2 From the View menu, select Trenders. A list of available Trender
windows displays.
3 Double-click an existing Trender window to open it.
-or-
Click Add, enter a name, and then click OK to create a new Trender window.
GEH-6700 ToolboxST Chapter 5 Trender 5-1

To create or open a Trender window from a ToolboxST system
1 From ToolboxST, navigate to the System Editor.

2 A list of available components displays in the Tree View. Double-click a
Trender window to open it.
3 To add a new Trender window, right-click a container (either the system
item or a group) and select Insert New, Tool, Trender).
To save a Trender window
From the Trender toolbar, select the Save button. If you opened the
current Trender window from within ToolboxST, the Trender window
saves automatically. If you opened the Trender window from the Start
menu, the Trender window saves to a file.
Note While Trender windows opened from ToolboxST components are

associated with one particular component for storage purposes, they are not
restricted to observing only that component and may be used to monitor any
variables.
Trender Window Features

Trender Toolbar
contains commands
for commonly used
tasks in the Trender
window.
Graph View
contains the trend
graphs, which
display the values
represented by
each trace.
Property Editor
allows you to change
settings that affect the
capture and display of
data.
Data Toolbar
contains commands
that manipulate the
current data.
Traces tab Sources tab User Note tab Events tab lists Auxiliary View Mode Indicator
displays traces displays sources allows you to save all events that contains tabs that displays the
currently being where data is comments, have occurred display current mode
monitored by the collected. instructions, and during the information about (Live or Replay).
Trender window. notes about the current Chapter. the current data.
current Chapter.
5-2 Chapter 5 Trender GEH-6700 ToolboxST

Trender Toolbar
Note The Trender toolbar may have fewer buttons if the current Trender
window was opened from ToolboxST.
Open existing Save current Undo Redo

Trender window Trender
Create new
Trender Window
Print Print Preview Go Online
Data Toolbar
Note The buttons available on the Data toolbar may vary according to the
current trace source type.
Record data from Pause Add traces

live source
Upload from Auto-range
capture buffer selected traces
Remove Zoom In & Time Axis Reverse

selected traces Zoom Out & Forward

Working in Trender
Acquiring Data
Before you can analyze data, you must import it into a Trender window.
Variables can be added to the Trender window live, from capture buffers, or
from a static file. While you may add as many variables as you like to a given
Trender window, all of them must be of the same type. (For example, you
cannot display both live and static file variables simultaneously.)
Adding Traces
The Trender represents each variable with a trace. (The term trace is used since
the Trender works similarly to a digital storage oscilloscope, which displays data
by tracing a line across the screen as values are acquired.) As you add traces to
a Trender window, the new traces display in the Traces Tab. (For more
information about managing traces from the Traces tab, refer to the section,
Traces .)
Live Trends
When a Trender window contains live trends, it displays the incoming data
onscreen in real-time. Live trends are useful for monitoring systems in
continuous operation.
To add one or more traces from a live source
1 If the Trender window you would like to add the trace to is not already
open, refer to the section, Accessing a Trender Window .
2 From the Edit menu, select Add Traces. The Add Trace Wizard
displays.
3 If this is the first trace added to the Trender window, the Add Trace
wizard prompts you for the type of trend to configure. Select Live, and then
click Next.
4 Select System Component, and then click Next.
5 If you did not open the current Trender window from ToolboxST, the Add
Trace Wizard prompts you for the name of the system file that contains
the source component. Click the Browse button and locate the system file,
and then select Next.
6 Select the component from which you wish to trend variables, and then
click Next.
7 Select the sampling period you wish to use, and then click Next. (The
sample period represents the time in milliseconds between samples, so
larger numbers result in fewer samples.) The Select Variables wizard
page displays.
8 Click the Add button to display the Variable Browser, then select one or
more variables to monitor. When you are finished, click OK in the
Variable Browser, then click Finish in the wizard. The newly created
traces display in the Trace tab.

Capture Buffer Trends
The Mark VIe controller features two types of synchronous data capture
Capture Buffer blocks and Dynamic Data Recorders (DDR). While each
method addresses different needs, both methods are accessed as Capture
Buffers in the Trender because they have similar underlying data collection
mechanisms.
To add one or more traces from a capture buffer
1 If the Trender window to contain the new trace is not already open, refer to
the section, Accessing a Trender Window.
displays.
Wizard prompts you for the type of trend to configure. Select Capture
Buffer, and then click Next.
4 Select the component from which to trend variables, then click Next. A list
of all available capture buffers displays.
5 Select one capture buffer, and then click Finish. All of the variables from
the selected buffer convert into traces and the Trace tab is updated to
reflect the changes.
Static File Trends

In addition to acquiring data from a controller, the Trender can also display data
from a static file stored on a hard disk. Three formats Data Collection and
Analysis (.dca), Comma Separated Value (.csv), and GE Control System
Toolbox Trend (.trn) are currently supported as static file sources. While each
of these formats is unique, the procedure to add a trace is identical for all.
To add one or more traces from a static file
1 If the Trender window to contain the new trace is not already open, refer to
the section, Accessing a Trender Window.
displays.
Wizard prompts you for the type of trend to configure. Select Static, and
then click Next.
4 Select the type of data source to import from and click Next to display an
Open dialog box.
5 Select the desired static file source, and then click Open.
6 The Select Variables wizard page displays. Click the Add button to
display the Variable Browser. ToolboxST analyzes the selected file and
displays a list of available variables. Select one or more variables to convert
to traces. When you are finished, click OK in the Variable Browser, and
then click Finish in the wizard. The newly created traces display on the
Trace tab.

Obtaining Data
As they depend on the presence of a controller, live and capture buffer traces do
not initially contain any data. (The data from static file traces is automatically
imported and displays as soon as the trace is added.) Once connected to the
controller, the procedure for obtaining data depends on the type of traces
present. Data from live traces is captured in much the same way that a video
recorder operates (with record and pause buttons), while data from a capture
buffer is uploaded from the controller in a single operation.
To connect to the controller
Select the Online button on the Trender toolbar. (If any of the
source controllers are redundant controllers, the Trender prompts you to
select a redundant channel before opening the connection.)
To begin capturing a trend from live traces
On the Data toolbar, select the Record Data button. The Trender
switches to Live mode, and the Graph View continuously scrolls the time
axis to display the latest incoming data while recording.
To freeze the display while capturing a trend from live traces
On the Data toolbar, select the Pause button. Data continues to be

collected and the Trender remains in Live mode, but the time axis stops
continuously scrolling until the Pause button is selected again.
To stop capturing a trend from live traces
On the Data toolbar, select the Record Data button. The Trender
returns to Replay mode.
To retrieve data from a capture buffer
On the Data toolbar, select the Upload button.

Trender Concepts
Chapters
When working with a live or capture buffer source, the Trender can record more
than one set of data. The basic unit of data capture in the Trender is a chapter. A
chapter represents one acquisition session, which is either a single upload for a
capture buffer source or a single period between clicks of the Record Data
button for a live source. Chapters are organized chronologically, so the first
acquisition session is always the first chapter and the most recent session is
always the last chapter.
A Trender window only displays one chapter of information at a time. As each

chapter maintains its own events, the Events tab only displays events
applicable to the currently displayed data. Similarly, the user data field is unique
to each chapter, so comments about a data set are stored alongside each chapter.
Traces and Sources are shared, however, so changes made to a traces properties
affect all chapters.
To navigate between Chapters
Click the Previous Chapter or Next Chapter button on the

Data toolbar. (If these options are disabled, there are no other chapters
available.)
Cursors
In the Graph View, two cursors individually select values of time and together
select ranges of time. The cursors are used by a number of functions in the
Trender, such as trace statistics, user events, and data export. The time
represented by each cursor is displayed in the status bar at the bottom of the
Trender.
Cursor Active cursor
To select a range of time
1 Place the mouse pointer over the diamond at the top of a cursor and drag the
diamond to the desired left boundary location.
2 Place the mouse pointer over the diamond at the top of the other cursor and
drag the diamond to the desired right boundary location.

To select a single time
1 Place the mouse pointer over the diamond at the top of a cursor and drag the
diamond to the desired value.
2 If the diamond for the cursor that represents the time value you wish to
select is not colored white, click the diamond to select it as the active cursor.
Tip When selecting a range of values, there is no left or right cursor you
may arrange the cursors in whichever way is most convenient. The Trender
automatically identifies the leftmost and right most cursors.
Tip While there are always two cursors on the Graph View, it may appear
that there is only one cursor on the Graph View if both cursors are set to the
same time value.
Value ScreenTips
If you place the mouse pointer over

an axis or a trace in the Graph
View, the Trender displays the
exact value in a ScreenTip. The
ScreenTip remains as long as the
pointer is over the selected item.
Events
During real-time monitoring of the controller, certain events may occur such as
alarms and diagnostics. As these events occur, they display in the Trender as a
small triangle on the time axis. All events in the current Chapter appear on the
Events tab, which displays the time and description of each event.
Event Indicator

To jump to an event
From the Event tab, double-click on the description of the desired event.
In addition to events added by the controller, you can add your own User
Events. If added during Live mode, the User Event is placed at the time of the
most recently received sample at the instant the Add User Event command is
selected. During Replay mode, new User Events are added at the time indicated
by the active cursor. (For more information about designating an active cursor,
refer to the section, Cursors.)
To add a user event
1 Select an active cursor.

2 From the Edit menu, select Add User Event. (Or, press the shortcut keys
CTRL+M.)
3 Enter a name for the new event, and select OK.
Working With Trender Data

Graph View Options
The Graph View can display data on either a single graph or a set of stacked
graphs. Single Trace mode displays all traces on the same graph, while Stacked
Trace mode displays each trace on an individual graph. In both modes, all traces
share the same time axis, but each trace maintains its own vertical axis. (If there
are too many traces to display stacked graphs effectively in the available space,
the Trender may revert to Single Trace mode even if you have selected Stacked
Trace mode.)
Note In Single Graph mode, the vertical axis markings correspond to the trace
listed first on the Trace Tab. Each trace is drawn according to its own scale and,
as such, traces other than the first trace may not correspond to the displayed axis
markings.
Stacked Trace Mode, Single Trace Mode
To turn Stacked Trace mode on or off
From the View menu, select Stacked Traces.

Grid Lines
The Trender can display grid lines that correspond to major axis divisions on the
Graph View. These lines, which only display when the Trender is in Replay
mode, can be useful when the exact trace values are important.
Grid Lines On, Grid Lines Off
To enable or disable grid lines
1 From the Options menu, select Settings. The System Options dialog
box displays with Trender selected in the Tree View.
2 From the Property Editor, locate the category Grid Lines and set the
values for Horizontal and Vertical to either True or False.
3 Click OK to close the Settings dialog box.
Sample Markers
When exact values at each sample reading are important, the Trender can
display Sample Markers at each sample collection point. By default, Sample
Markers display when the current Graph View contains ten or fewer samples. If
desired, you can change the Sample Marker threshold.
To set the Sample Marker threshold
1 From the Options menu, select Settings. The System Options dialog
box displays with Trender selected in the Tree View.
2 In the Property Editor, under the category General, enter a new value
for Sample Markers.
3 Click OK to close the Settings dialog box.

Time Axis
The Time Axis controls the range of samples that display in the Graph View. All
traces share a single Time Axis, even when Stacked Trace Mode is enabled.
To change the range displayed on the Time Axis
Click the Reverse or Forward buttons on the Data toolbar.
To display a shorter or longer period of time on the Time Axis
Click the Zoom In (to reduce the duration) or Zoom Out (to
increase the duration) buttons on the Data toolbar.
The Zoom In and Zoom Out commands behave differently depending on the
current mode. In Live mode, the Zoom In command sets the duration to one
third of the current value and the Zoom Out command sets the duration to three
times the current value. In Replay mode, the Zoom Out command still sets the
duration to three times the current value, but the Zoom In command sets the
duration to the exact region selected by the two cursors. (For more information
on selecting a range, refer to the section, Cursors.)
Tip To quickly change the range of an axis, you can click any point on the
axis and drag it to a new location. This operation works for both the value and
time axes and is frequently the most effective way to change the displayed set of
data.
Traces
The Trender window maintains separate settings for each trace. These settings,
which include trace color, sample capacity, and pen width, are accessed through
the Property Editor when a trace is selected on the Trace tab. In addition, Value
(vertical) Axis settings managed through each trace allow an appropriate scale
and range to be determined for each item.
Auto-Range Trace
To display a set of collected samples in the Graph View, an appropriate Value
Axis scale and range must be selected. For most data sets, an optimal scale and
range would display all collected samples in the selected time range with
minimal wasted space. The Auto-Range Trace feature sets the range of the
Value Axis for the currently selected trace(s) to the optimal values. Even if you
decide to further refine the range of the trace, the Auto-Range Trace feature
provides a convenient starting point.
To auto-range a trace
From the Trace tab, select one or more traces, then select the Auto-Range
Selected Traces button on the Data toolbar.

Manual Range Adjustment
When the Auto-Range Trace feature selects an inappropriate range, or if you
want precise control over the range, you can provide a minimum and maximum
value for the Value (vertical) Axis.
To manually adjust the range for a trace
From the Trace tab, select one or more traces, then adjust the Bottom
Value and Top Value properties under Range in the Property Editor.
Trace Colors
The Trender assigns each new trace a color from a set of eight colors stored in
the Settings window. After eight traces are created, these colors are reused. You
may wish to change the color of a trace, especially when multiple traces display
on a single graph.
To change the color assigned to a trace
1 From the Trace tab, select a trace.

2 In the Property Editor, locate the Pen category and select the Color
property.
3 Click the drop-down list and select the Custom (for a color palette) or
Web (for a list of named colors) tab.
4 Click the square that corresponds to the desired trace color. The trace
updates automatically.
To modify the default trace colors
1 From the Options menu, select Settings.

2 Locate and select the Trender item in the Settings window.
3 In the Property Editor, select the number of the trace (for example, 2nd
Trace) to be changed.
4 Click the drop-down list and select the Custom (for a color palette) or
Web (for a list of named colors) tab.
5 Click the square that corresponds to the desired trace color.
6 When you have finished changing trace colors, click OK.
Hiding Traces
In some situations, especially with capture buffers, a Trender window contains
more traces than you want to monitor at a particular time. Traces in a Trender
window can be hidden. They still collect data, but they do not display in the
Graph View or the Trace tab.
To show or hide a trace
From the Edit menu, select Show Traces. Select and clear the check
boxes next to the trace names as desired, then click OK.

Statistical Calculations
The Trender can calculate a set of basic one variable descriptive statistics for
collected data while in the Replay mode. These statistics, which are calculated
only on data in the time range selected by the two cursors, include average,
standard deviation, minimum, maximum, and difference (calculated as final
initial). The calculated values display as columns on the Trend tab when
enabled.
To enable statistical calculations
1 From the Options menu, select Settings.

2 Locate and expand the Trender item in the Settings window. Under the
Trender item, select Replay Columns.
3 In the Available list, select one or more statistics to enable. (To make
multiple selections, hold down the CTRL key while selecting additional
items.)
4 Click the Add button to move the statistics to the Selected list.
5 When you have finished enabling statistics, select OK.
Exchanging Trender Data

Exporting to a File
The Trender can export all traces contained in a Trender window to a file for
external analysis. This file can be imported into third party applications or
exchanged with other users. All traces, including ones which are currently
hidden, are exported.
To export all traces to a file
1 From the File menu, select Export Data.

2 In the Trender Export Data Options box, adjust options as desired to
produce a file compatible with your desired format. The default options
produce a standard Comma Separated Values (CSV) file. (See below for a
description of each option.)
3 Select OK when you have finished selecting options. A Save dialog box
displays.

4 Select a location for the exported file and click OK.
Controls whether the first line of Controls the character

the exported file contains header used to separate values
information for each column. in the exported file.
Controls whether a
column containing Controls the text
timestamps is added exported when no
to the output. data is available
for a trace at a
given point in time.
Controls whether a
column containing
increasing integers is
added to the output. Selects the precision
of the exported
timestamp.
If selected, only the
time range selected
by the cursors is
exported.
Printing Graphs
The Trender can print the currently displayed graph to any printer attached to the
system. Printed graphs reflect the current appearance of the Graph View,
including displayed traces, colors, and axis boundaries.
To preview the results of a print command
From the File menu, select Print Preview.
To print the current Graph View
From the File menu, select Print. Adjust printing options as desired and
click OK.

CHAPTER 6
Chapter 6 EGD Editor for External
Devices
Overview
The EGD Device Editor for External Devices allows you to configure Ethernet
Global Data (EGD) for an external or third party device. The EGD protocol
allows controller devices (sometimes known as nodes) to share information in a
networked environment. EGD allows one controller device, referred to as the
producer of the data, to simultaneously send information to any number of peer
controller devices (consumers) at a fixed periodic rate. This network supports a
large number of controller devices capable of both producing and consuming.
Network Adapters
The General tab configures Ethernet adapters for an external EGD-capable
device. One adapter is created by default, and up to four adapters can be added.
To add a network adapter
1 From the System Editor, right-click an external device component and

select Edit EGD. (If Edit EGD is not available, the EGD Editor Enable
property of the component may be set to False. Refer to the section, Insert
New External Device.) The EGD Component Editor opens.
2 From the Component Editor, select the General tab.
3 From the Tree View, right-click the Network Adapters item and select
Add Adapter.
To remove a network adapter

2 From the Component Editor, select the General tab.
3 From the Tree View, right-click the network adapter to be removed and
select Delete Adapter.
GEH-6700 ToolboxST Chapter 6 EGD Editor for External Devices 6-1

The following properties are available for configuration when a Network
Adapter is selected in the Tree View:
Host Name: The Internet Protocol host name for the selected network
adapter.
IP Address: The Internet Protocol (IP) Address for the selected network
adapter.
Network Name: The name of the connected network.
Subnet Mask: The subnet mask associated with the connected network. (If
working inside a ToolboxST system, this property will be read-
only.)
Wire Speed: The speed of the connected network. (This property is only
available when working inside a ToolboxST system.)
6-2 Chapter 6 EGD Editor for External Devices GEH-6700 ToolboxST

EGD Configuration
To configure EGD for an external device

2 From the Component Editor, select the EGD tab.
3 In the Tree View, select Ethernet Global Data. The Ethernet Global
Data properties display in the Property Editor.
These properties are available for configuration when Ethernet Global Data is
selected in the Tree View:
Collection This property controls the Collection to which this EGD

component belongs when viewed in the EMT tool. This information is published
to the EGD Configuration server in the GUI component document,
GUIDevice.xml.
Producer ID Sets and displays the EGD Producer ID for this component.
This is assigned when the component is created. The Property Editor displays
the EGD Producer ID formatted as an unsigned integer, but dotted and
hexadecimal representations are available by clicking the ellipsis button.

Produced Pages
Produced Pages are data samples configured to be available to other components
on the network.
To add a new Produced Page
1 From the Tree View, right-click the Produced Pages item, and then
select Add Page.
2 Enter a unique name for the new page in the Page Name dialog box and
select OK.
Note When the first Produced Page is created, it automatically becomes the
Default page.
To select the default Produced Page for the standard signals
1 From the EGD tab, select Produced Pages in the Tree View.
2 Select the Default Page Property from the Property Editor, and then
select the desired page from the drop-down list.
Tip Any variable defined with $Default as the EGD page name will
automatically be placed on the currently selected Default page.
To delete a Page
From the Tree View, right-click the page you wish to delete and select
Delete.

Editing Produced Pages
To configure a Produced Page
From the EGD tab Tree View, expand Ethernet Global Data.
Under Produced
Pages, select the
desired page.
The page
properties display
in the property
editor.
The following properties are available for configuration when a Produced Page
is selected in the Tree View:
Ethernet 0 If selected, EGD will be broadcast on Ethernet Adapter 0. (If
more than one Ethernet Adapter has been configured for EGD, additional
Ethernet properties are displayed.)
Mode - This property can be set to Broadcast, Unicast or Multicast, depending
on the modes supported by the device's EGD implementation profile.
Exchanges This property indicates the number of exchanges in the
selected page. It is updated after a build.
Name Use this property to rename the selected page.
Period This read-only property indicates the transmission period of the page
in milliseconds.
Skew Skew is used to prevent exchanges with the same period from being
produced at exactly the same instant. The skew for the first exchange in the
page is set to this value, and each additional exchange skew differs from the
previous exchanges skew by exactly this value. For example, if you have three
exchanges in a page and a skew value of 2, the first exchanges skew is two,
the second exchanges skew is four and the third exchanges skew is six. (The
skew property is measured in nanoseconds.)
Destination IP Address - This property sets the IP address to which the
exchanges on this page are Unicast or Multicast. (If the Mode property is set
to Broadcast, this property is not available.)

Page Compression
When a page compress operation is performed, the variable locations are
optimized. The variables are located in increasing size order, starting with
Booleans, then Words, Double Words, and finally all other variables.
To compress a single page
From the Tree View, right-click the page to compress, and then select
Compress.
To compress all Produced Pages in a component
From the Tree View, right-click Produced Pages, and then select
Compress All.
Variables
To delete a variable from an EGD Page
From the Summary View, right-click the variable to delete, and then select
Delete Selected Row(s).

To copy variable information from an EGD Page to the Clipboard
From the Summary View, right-click a variable, and then select Copy
Selected/Current Row(s). The data is copied in Comma Separated Value
(CSV) format.
Editing Exchange Signatures and Configuration

Time
Normally, the exchange signature is managed automatically. The major
signature must be incremented when the exchange content changes in any way
other than additions to the end. If you are using the EGD Device Editor to
configure EGD for a device and the device signature changes only when the
manufacturer updates the configuration, you may need to manually set the
signature.
To edit exchange signatures and configuration time
1 From the EGD tab, select a produced page in the Tree View.
2 Right-click an exchange in the Summary View and select Edit
Exchange Signatures and Configuration Time.
3 Review the warning about manual Exchange Signature editing and click
OK.
4 Make any desired changes to the signatures and configuration time, and then
click OK to close the dialog box.

Referenced Devices
The EGD variables defined in other components can be added to the current
components variable list by adding a reference. References can only be created
to EGD-capable devices that are consumers of Produced Pages, and as such only
EGD-capable devices are available for referencing.
To select the devices that are referenced
From the Tree View, right-click the Referenced Devices item, and then
select Select Devices to display the Select Devices dialog box.
Select or clear the

check boxes next to
each device
name. Click OK.
The EGD configuration for the selected devices is loaded and the variables
display in the Summary View.
Grayed Exchanges
are not available to
this device.
When EGD configurations are edited in remote devices, you must refresh the
configuration periodically to ensure that the latest variable information is used.
This is automatically done during a Bind and Build operation as well as when a
configuration is saved.
To refresh the configuration of a referenced device
In the Tree View, right-click the device to be refreshed, and then select
Refresh.

Implementation Profile
Each EGD node type has a set of supported EGD features. For example, a
device might have an EGD implementation that only supports broadcast
produced data. The implementation profile contains details about the EGD
implementation of a particular device.

The following properties are available when editing an Implementation Profile:
Configuration Support: Configures the operations supported by the device.
Accepts Deletes: Indicates device support for HTTP deletes.
Multiple Producer IDs: Indicates device support for multiple producer IDs.
Accepts Puts: Indicates device support for HTTP puts.
Zip Content: Indicates device support for zipped transfers.
Data Types: Configures supported data types. (Clicking the ellipsis button will open an
editor window.)
Double Word Alignment: The offset of a DWORD length variable must be evenly divisible by this number.
Word Alignment: True if the device requires that all WORD length variables be aligned on an even
boundary.
Broadcast: Set to true if the device supports broadcast destinations for EGD data or
command packets and false otherwise.
Masked Write: Set to true if the device supports the MaskedWrite command and false otherwise.
Max Coherent Data: This unsigned integer returns the maximum size in bytes of a variable that still is
guaranteed coherent transfer. If the attribute is not present then all data is
guaranteed coherent transfer regardless of size. It is optional and is initialized to
0.
Max Exchanges: This unsigned integer returns the maximum number of exchanges supported by
the device. It is optional and is initialized to 0.
Max String: This unsigned integer returns the maximum size string supported by the device.
If the attribute is not present then the device has no set maximum size for strings.
It is optional and is initialized to 0.
Multicast: This value is set to true if the device supports multicast destinations for EGD data
or command packets and false otherwise.
Skew: This Boolean value represents the capability of the producer to support the
skewing of produced exchanges with respect to time.
Unicast: This boolean is set to true if the device supports unicast destinations for EGD
data or command packets and false otherwise.
Device Class: The Class of the device as defined in the EGD Protocol Specification:
Class Description
0 Supports only the configuration port.
1 Supports the data port and the Data Production PDU.
2 Supports all class 1 services plus at least acts as a responder for the command
port and the commands associated with that port.
3 Supports all class 2 services plus the configuration port and the required
commands associated with that port. Such devices support responding to
configuration requests but do not dynamically bind their consumed variables.
4 Supports all class 3 services plus dynamically binding consumed variables.
Device Class Name: The name of the class of device to which this device belongs.

Menus
File Menu
Save updates the EGD configuration files, refreshes consumed
exchanges and variables, assigns produced variables to exchanges,
and, if an EGD configuration server has been specified, publishes the
configuration to the server.
Import and Export allows you to transfer produced data,
consumed data, symbols, implementation profiles, and GUI device
EGD configuration files to and from a variety of file formats.
Print outputs the summary grid view with the column selection,
order, and width currently visible in the view.
Close closes the currently open device.
Edit Menu
Undo returns the editor to the state it was in before the last action
was performed.
Redo performs an action again after an undo command.
Cut moves the currently selected portion of the data grid to the
clipboard.
Copy transfers a duplicate of the currently selected portion of the
data grid to the clipboard.
Paste transfers the contents of the clipboard into the data grid.
Delete deletes the currently selected item.
Find opens the Finder dialog box. For more information, refer to the
section, Finder.
View Menu
Go Back returns to the view that immediately precedes the current
view in the history.
Go Forward returns to the view that immediately follows the current
Launch EMT opens the EGD Management Tool.

Device Menu
Bind and Build refreshes the consumed information for all
referenced devices, automatically sets the layout of any
unassigned produced variables, and, if no errors occur,
publishes the configuration to the EGD configuration server.
Put Device to SDB command stores the current EGD
configuration to the System Database (SDB). It is only available
if the system has an SDB enabled and configured.
Help Menu
Contents opens this help document.
Release Notes opens the release notes for the current

version of the application.
About shows version and copyright information about the
application.

CHAPTER 7
Chapter 7 Tree File Importer
Overview
The Tree File Importer is a companion application that converts software tree
files from the GE Control System Toolbox to the new .XML file format used by
ToolboxST.
The Tree File Importer is provided as a tool to assist with the

conversion process. It is designed to provide a baseline for
further revision and refinement. As configuration files
produced by the converter may contain errors and/or
omissions, all converted components and library containers
must be thoroughly reviewed and verified before use. A
failure to thoroughly verify any software or configuration
may result in equipment damage and/or malfunction and
subsequent bodily harm or loss of life.
Before using the Tree File Importer, you must complete the following steps:
1 From the Control System Toolbox, export the tree files for a particular
device using the Export All command on the File menu. Make sure the
device is valid before proceeding.
2 From ToolboxST, create a system, add a library container, and then add an
empty component corresponding to the device type that you exported from
the Control System Toolbox. (ToolboxST uses the term component in
place of the older term device from the Control System Toolbox.)
3 Run the Tree File Importer. Select the system and library container you
created in Step 2, and then select the project file from Step 1 to import the
macro and module library tree files. Each use of the Tree File Importer
imports a single file; importing a project file includes all tree files for a
device and is the quickest way to perform a conversion. (For details on the
operation of the Tree File Importer wizard, refer to the section, Running the
Tree File Importer.)
4 From ToolboxST, open the controller and add a reference to the libraries
that were imported in Step 3.
5 Exit ToolboxST and return to the Tree File Importer. Select the system
and device you created in Step 2, and then select the project file from Step 1
to import the function tree files.
GEH-6700 ToolboxST Chapter 7 Tree File Importer 7-1

Running the Tree File Importer
Before beginning, make sure you have created a system to contain the imported
configuration and that the system contains a component of the correct type. (For
example, you would need a system with at least one Mark VIe component to
import a Mark VIe controller configuration.) Also, make sure that ToolboxST is
not running.
To run the Tree File Importer
1 From the Start menu, select Programs, GE ToolboxST, ToolboxST,

and then Tree File Importer to display the Tree File Importer wizard.
2 Click the Browse button. From the Select Workplace window, locate
and select the .tcw file you created in Step 1, and then click Open. Click
Next to continue to Page 2.
3 ToolboxST opens the system selected in Step 1 and displays a list of
available controller and library container components.
7-2 Chapter 7 Tree File Importer GEH-6700 ToolboxST

4 Select a component to receive the imported configuration, and then click
Next to continue to Page 3.

5 Click the Browse button. From the Select Project or Tree File
window, locate and select a source .prj or .tre file, and then click Open.
When you have selected a source file, click Next to begin the import
process.
By default, only .prj files

are displayed. Click here
and select Tree Files from
the drop-down list to display
.tre files.
6 The Application Code Conversion Type dialog box displays. Unless
you are certain another setting applies, select Straight variable name
conversion, and then click OK.

When the import process is completed, Page 4 of the Tree File Importer
wizard displays with a log of errors and warnings that occurred. Warnings are
minor problems that do not prevent the import from being saved (for example, a
function block that cannot be imported). Errors are major problems that prevent
the import from completing (for example, a missing library reference.)
Errors and Warnings displayed by the Tree File

Importer are designed to provide helpful information
about the import process. They are by no means
complete, and the lack of any errors or warnings does
not necessarily indicate that a fully functioning and
correct component was created by the import. Before
using any application code or settings imported by the
wizard, thoroughly review every aspect of the system
for errors, omissions and/or inconsistencies.
7 After reviewing the log, click Finish to save the updated system and
complete the wizard.

Notes

Part 2
Configuring a Mark VIe Controller
CHAPTER 8
Chapter 8 Working Online With a
Mark VIe
The Mark VIe control system is used for control, protection, and monitoring of
turbine and driven load equipment. Vital subsystems, such as servo control,
vibration protection, and synchronization are embedded in the I/O with on-board
processors to optimize performance.
ToolboxST is the configuration and maintenance software tool for Mark VIe
controllers. The system has a CompactPCI controller with networked I/O. The
I/O processors are located on the terminal boards instead of in centralized board
racks. This configuration digitizes the signals on the terminal boards, which can
be mounted local or remote, individually or in groups.
Connecting to a Controller
Many actions in the Mark VIe Component Editor require an active connection to
a controller.
To connect to a controller
From the System Editor, open a Mark VIe Component Editor. From
the Device menu, select Online.
-or-
From the System Editor, open a Mark VIe Component Editor. From
the toolbar, click the Online button.
If you are connecting to a simplex controller, a connection is automatically

established with the R controller. In a dual or TMR configuration, a dialog box
displays to select either a redundant controller (either R, S, or T) or the
controller currently designated as the supplier of initialization data.
GEH-6700 ToolboxST Chapter 8 Working Online With a Mark VIe 8-1

Status Tab
When ToolboxST is connected to a Mark VIe controller, operating state and
equality information is available from the Status tab of the Component
InfoView window. When used in a redundant controller configuration, the
status is shown individually for each controller in the redundant set.
Color text is used throughout the Status tab to display state information at a
glance. Both the tab and the text are green, indicating the normal state for the
control.
The color on the Status

tab indicates the overall
state of the controller.
Color Conditions
Green All controllers functioning normally.
- Control state is controlling
- Controller Equality equal
- DDR Equality equal
Yellow One or more of the following:
- Control state not controlling
- Controller equality not equal
- DDR equality not equal
- Frame Idle time < 20%
Red One or more of the following:
- Control state is failed
- Controller equality has a major difference
8-2 Chapter 8 Working Online With a Mark VIe GEH-6700 ToolboxST

The following example displays the unequal state for a dual redundant control.
The DDR Equality attribute text is orange to indicate that DDR Equality is not
equal, and the Controller Equality attribute text is red to indicate that a major
difference exists. Since the Controller Equality attribute takes precedence over
the DDR Equality attribute as indicated in the above table, the Status tab is red.
Controller Attributes
Control State indicates the current state of the controller. When a controller is
turned on, it transitions through several states before arriving at the normal
controlling state. Valid Control State are as follows:
State Description
Power up Power up controller
Master initialization Initialize controller
Designated controller Determine which controller is designated in a redundant controller
determination configuration
Data initialization Perform initialization of non-designated controllers with NVRAM,
command variables, and constants
Inputs enabled Wait in this state for all of the I/O packs to start transmitting inputs
Input voting Check voting inputs prior to execution of application code
Exchange initialization Populate redundant controllers with dc state variables prior to voting
Exchanging Exchange state variables so that a controller joining a running system
wont have a step in its initial calculations
Sequencing Turn on the application code and execute each task at least once
before driving outputs
Controlling Turn on outputs
Loading Online load is in progress
Load complete Online load has finished. Wait for re-synchronization of redundant
controllers
Fail Failure has occurred. Refer to the section, Controller Diagnostics.

If the indicated Control State is not Controlling, ToolboxST can provide
additional information as follows:
Move the mouse pointer

over the Control State.
Information about the

current state displays.
Or, double-click Control State to display the information in a separate

window.
Controller Equality indicates whether equality exists between the software

configuration in ToolboxST and the configuration currently running in the
controller. Valid states are Equal, Not Equal, and Major Difference. Refer
to the section, Downloading the Controller.
DDR Equality indicates whether equality exists between the Dynamic Data
Recorder configuration in ToolboxST and the configuration currently running in
the controller. Valid states are Equal and Not Equal. Refer to the section,
Dynamic Data Recorder.
Designated Controller indicates the controller that is designated as the

supplier of initialization data to the other controllers.
UDH Communicator indicates the controller responsible for communicating

on the Unit Data Highway (UDH) for the Mark VIe. The UDH Communicator
performs tasks such as sending the EGD exchanges produced by the device.
Frame Idle Time is the percentage of CPU time left in the controller after the
critical control functions of input, compute, and output have been completed.
System Idle Time is the percentage of CPU time left in the controller after all
functions have been completed. It accounts for the critical control functions as
well as background processing and communication overhead. (System Idle
Time is always less than or equal to frame idle time.)
Number of Forced Variables displays the number of forced variables in the

controller. Refer to the section, Forced Variables.
Heart Beat indicates whether the controllers are exchanging the control state
variables. If the number shown is incrementing, the control state variables are
being exchanged.
Controller Time shows the current wallclock time that the controller is using
for timestamping. Refer to the section, View/Set Time.

Download to Controller
ToolboxST is used to configure both a Mark VIe controller and its distributed
I/O modules. Both the controller and the I/O modules have four items of
software that can be downloaded:
1 Boot Loader is software that starts the operating system for the controller
and modules, much like the BIOS on a desktop computer. Changes to the
boot loader are very infrequent.
2 Base Load is software that contains the operating system for the controller
and I/O modules. While changes to the base load are more likely than
changes to the boot loader, they still occur infrequently.
3 Firmware is the software that provides the functionality of the controller
and I/O modules. It can be updated over the lifetime of the controller to
incorporate new features and bug fixes.
4 Application Code contains the configuration of the controller as created in
ToolboxST. Whenever a change is made to the configuration, the
application code must be downloaded. There are two types of application
code download, online and offline. An online download, which is common,
changes the configuration without interrupting control; the new
configuration will take effect between control frames. An offline download
requires a controller restart and is much less frequent. The type of download
needed is determined by the types of changes that have been made to the
controller configuration.
Boot loader, base load, firmware, and offline application

code downloads all require the target device to be restarted.
Before downloading new code to a controller, take necessary
steps to secure the controlled equipment to prevent
equipment damage and/or personal injury.
Download Command
The Download item in the Device menu displays a submenu of commands.
Besides the Controller Initial Setup and Download Wizard commands, the
following commands are available:
Controller Flash Boot Loader is used to install the controller's boot loader on a
CompactFlash memory card. To use this command, you must have a
compatible CompactFlash reader attached to your computer.
Update Dynamic Data Recorders updates the standalone data collectors that
can be reconfigured without affecting any of the control code.
View / Set Time is used to set the time on a controller.

Controller Initial Setup
The Controller Initial Setup wizard prepares a controller for use by configuring
its IP address and redundancy information. A controller cannot communicate on
a network until these setup tasks are complete.
To set up a controller using the Controller Initial Setup wizard
1 Connect a serial cable from the main board of the controller to a free serial
port on your computer.
2 Open the Mark VIe Component Editor for the controller to be
configured.
3 From the Device menu, select Download, and then Controller Initial
Setup.
4 From the first page of the wizard, click Next to display the second wizard
page.
Select the serial port that you

connected the controller to in Step 1.
(Refer to your computer
manufacturers documentation for
assistance in identifying your
computers communication ports.)
Assign the connected board to a
specific redundant controller by
clicking the appropriate option button.
(If the controller is configured as a
simplex or dual controller, some
channels may not be available.)
Click Finish to connect to the

controller and perform the initial
setup. A progress dialog box will
keep you informed about the
status of the setup process.

Download Wizard
The Download Wizard is the primary method of transferring software to a Mark
VIe controller and its Distributed I/O modules over an Ethernet connection. The
wizard can automatically examine the configuration of the system to locate out-
of-date software, or you can manually select individual items to download.
Boot loader, base load, firmware, and offline application code

downloads all require the target device to be restarted. Before
downloading new software to a controller, take necessary steps
to secure the controlled equipment to prevent equipment
damage and/or personal injury.
To download software to a controller
1 Open a Mark VIe Component Editor. From the Device menu, select
Download, and then Download Wizard to display the Mark VIe
Download Wizard.
2 If you have changed configuration settings since the last Build operation, a
message box will display indicating that the software is out of date. Click
Yes to build the current configuration. The Mark VIe Download Wizard
opens.
3 Click the Next button to advance past the wizards introductory page.

Click the Scan button to
examine the system
configuration and locate out-
of-date software. The Scan
operation automatically
selects any software items
that need to be downloaded.
In this example, the G1
controller needs application
code downloaded, but the I/O
module is up to date.
If checked, software
that was identified as
up-to-date by the scan
operation is displayed.
Reboot Required
indicates that an
offline download is
required to update
the application code.
When the appropriate software is

selected for download, click the Next
button. Review the warning that
displays, and then click Next again to
display the Download page.
Check this box to continue

downloading if errors occur.
(If an error occurs during the
download of a particular
target, no further downloads
are attempted for that target.)
Click to begin the

download process.

Displays the overall
progress of the
download.
Displays the progress

of the current file
download.
Click to stop the

download process
after the current file
completes.
4 When the download has completed, click Finish to close the wizard. In the
Component InfoView, click the Log tab and review the status messages to
check for potential warnings or errors that may have occurred during the
download.

Upload Wizard
ToolboxST can retrieve existing configuration information from a Mark VIe
controller using the upload wizard. When a configuration is uploaded, it is
stored as a new Mark VIe component in the currently open system. The
uploaded configuration is useful as a reference for comparisons with other
components and for retrieval of existing code.
To upload the configuration from a Mark VIe controller
1 Open a Mark VIe Component Editor. From the Device menu, select
Upload to display the Mark VIe Upload Wizard.
2 Click Next to advance past the introductory page of the Upload Wizard.
If the Mark VIe is configured as a redundant controller, the following page
displays with an option button for each available redundant controller.
Select a
controller, and
then click Next.

(Optional) Enter the name of
a group to hold the newly
uploaded component.
Enter a name for the newly

uploaded component. (It must
be different than the current
component name and be
unique in the system.)
Click here to begin the

upload process.
3 When the upload completes, click Next to display the final page of the
wizard.
Click here to open

the uploaded
component when
the wizard finishes.

Controller Diagnostics
The Controller Diagnostics window displays diagnostic messages for a Mark
VIe controller. Diagnostic messages are errors or warnings that occur in the
hardware device and could be indications of an improperly functioning device.
Retrieving diagnostic messages should be the first step in diagnosing any
problems with hardware or communications.
To retrieve diagnostic messages
Open a Mark VIe Component Editor. From the View menu, select
Controller Diagnostics.
Manually retrieves the Permanently removes If checked, inactive

latest diagnostic inactive faults from faults are temporarily
messages. the list. hidden.
Select the desired

redundant controller
in a dual or TMR
configuration.
Timestamp when
the message
occurred.
Fault code from 1 - active Description of the fault

the controller. 0 - inactive that occurred.

Administer Totalizers
Each Mark VIe controller maintains a set of 64 counters in non-volatile RAM
(NOVRAM) known as totalizers. Each totalizer counts the number of times that
a particular event has occurred. Events are assigned to totalizers by configuring
a TOTALIZER block. Only one TOTALIZER block is allowed per controller.
Any user may view the current values of the totalizers, but to protect data
integrity, a special password from GE is required to change them.
Note Before modifying totalizer values in a redundant controller, connect to the

R controller and make sure all other redundant controllers are healthy and
communicating.
To view totalizer values
1 Establish a connection to the R controller. For more information, refer to the

section, Connecting to a Controller .
2 From the Device menu, select Administer Totalizers to open the
View/Set Totalizers dialog box.
The name of the TOTALIZER The name of the The current value of the Click here to
block pin connected to the variable connected to counter. The values displayed close the dialog
totalizer. (If blank, the totalizer a configured pin. are retrieved live from the box.
has not been configured.) controller and are updated
once per second as long as the
dialog box is open.

Totalizer Passwords
All users can view totalizer values, but modifying the values requires special
authorization in the form of a temporary password obtained from GE Energy.
Note Totalizer passwords are specific to the connected redundant controller (R,
S, or T) and cannot be used on other controllers.
To request a Totalizer Password
1 Establish a connection to the R controller. For more information, refer to

the section, Connecting to a Controller.
2 From the Device menu, select Administer Totalizers to open the
View/Set Totalizers dialog box.
3 Under Totalizer Identifier and Password, click the Request button. A
file named Totalizer_ID.txt is created in the same folder as the controller
configuration files on your disk. Once the file has been created, it is opened
in Notepad.
4 Follow the directions at the top of the file to contact GE Energy with the
information contained in the file. GE will reply with a new Totalizer_ID.txt
that contains a password customized to your installation:

The 28-character
password contained in
the Totalizer_ID.txt file
from GE consists of
numbers and letters.
5 Highlight the 28-character password and press CTRL+C to copy the
password to the Windows clipboard, and then return to the View/Set
Totalizers dialog box in ToolboxST.
6 Right-click inside the Password box and select the Paste command to
transfer the 28-character password from the clipboard. If the password is
valid, a new countdown timer displays below the Password box indicating
the time remaining before the password expires. (Totalizer passwords are
usually valid for 24 hours from the time of creation.)

Modifying Totalizer Values
Once you have entered a valid password, you can modify any of the totalizer
values. (For assistance with totalizer passwords, refer to the section, Totalizer
Passwords.)
To modify a totalizer value
Open the View/Set Totalizers dialog box and enter a valid password.
From the Totalizers list,

select a totalizer to
change, and then click
the Modify Selected
button to display the
Modify Totalizer Value
dialog box.
Enter a new value for the

totalizer in the New Value
box, and then click the OK
button. The value is
immediately sent to the
controller.

CHAPTER 9
Chapter 9 General
The General tab configures general properties and attributes of a Mark VIe
controller. Some items that can be configured on the General tab include the
redundancy of the controller (simplex, dual, or TMR) and the frame rate of the
controller (its basic scheduling rate).
General Features
To configure Mark VIe General Features
From the System Editor, double-click the Mark VIe Component to

display the Mark VIe Component Editor. The General tab is selected
by default.
Tree View lists the items

that can be configured
on the General Tab .
The list of items changes
when a different tab is
selected.
Property Editor
provides a consistent
way to edit the item
currently selected in the
Tree View .
Component InfoView
displays feedback
information about the
currently selected item.
Summary View provides a

graphic overview of the controller.
GEH-6700 ToolboxST Chapter 9 General 9-1

The following properties are available in the Property Editor when the General
item is selected in the Tree View:
Description is a freeform field to store comments about the current controller.
Frame Period determines the frame period in milliseconds. A frame is the basis
for MarkVI scheduling; the frame period determines the fastest scan time, the rate
at which first class I/O is scanned, and the fundamental frequency for the
scheduling of all tasks.
Major Revision is the time of the build performed after the most recent major
change. (Major changes require the controller to be restarted after download.)
Minor Revision is the time of the build performed after the most recent minor
change (Minor changes do not require a controller restart).
Name reflects the name of the current controller as set in the System Editor. It is
read-only in the Mark VIe Component Editor and must be changed from the
System Editor.
NTP Configuration Mode determines how the Network Time Protocol client
synchronizes the controller time. Valid options are:
Disabled The controller does not perform any time synchronization.
Broadcast The client listens for NTP broadcasts on the network.
Unicast The client uses the specified servers to obtain the time.
NTP Configuration Primary Server is the IP address of the primary server
used when unicast mode is selected.
NTP Configuration Secondary Server is the optional IP address of a
secondary (backup) server used when unicast mode is selected.
Platform is the type of hardware on which the Mark VIe control code is runned.
Product Version is a read-only property that reflects the version of the Mark VIe
product associated with the selected component. The version number is set when
the configuration is first created and is updated with each Upgrade operation.
Profiler Enabled determines if the controller load profiler is enabled. This
feature is not yet implemented.
Protection provides the following two access rights:
Modify Data permits modification of data values and the forcing of variables.
Modify Design permits modification of the design of the controller.
Redundancy determines the level of redundancy of the controller. The following
choices are available:
Simplex a single non-redundant controller.
Dual a two-controller configuration where one controller provides backup
for the other.
TMR a triple module redundant configuration where there are three
controllers that vote on decisions for reliability.
9-2 Chapter 9 General GEH-6700 ToolboxST

Attributes
Attributes are device-level values that affect how the configuration is generated.
When the Attributes item is selected in the Tree View, a grid displays in the
Summary View to view and edit controller attributes.
The following columns are available:

Name is a unique identifier for the attribute.
Description stores added comments about the attribute.
Type sets the data type of the attribute.
Value displays and modifies the current attribute value.
Array Length determines the number of elements in the array the attribute
represents if set to a number greater than zero. (A value of zero indicates
that the attribute is not an array.)
Prompt determines if the user is asked for values when the attribute is used
in instance scripts.
Additionally, when the Attributes item is selected in the Tree View, the
property editor displays the protection passwords for the attributes. The
following protection options are available:
Modify Data permits the modification of the values of device attributes.
Modify Design permits the modification, addition and removal of device
attributes.
View Design permits the user to view the device attributes.

Attribute Value Editor
The Attribute Value Editor provides a way to enter values for a wide variety of
data types.
To open the Attribute Value Editor
From an attribute Data Grid, click a Value Cell, and then click the ellipsis
button.
Name of the attribute

being edited.
If the attribute uses
Value of the attribute. an enumeration,
use this drop-down
box to select a
predefined value.
Additional boxes are used

when an attribute is an
array.
Use this drop-

down box to set
If checked, attribute
the data type of
values are restricted
the attribute.
to an enumeration (a
predefined set of
allowable values.)
The values
currently in the
To add a value to the
enumeration.
enumeration, fill in the
Name, Value and
(optionally) Description
boxes, and then click the
Add button.

Network Adapters
The network adapters that are present in the controller display as items in the
Tree View. The number of adapters depends on the controllers hardware type
and configuration. In most applications, Mark VIe controllers have four network
adapters. The first adapter provides connectivity to the Unit Data Highway
(UDH), and any additional adapters are used for I/O networks. Some adapter
properties may be disabled in certain configurations.

When a Network Adapter item is selected in the Tree View, the following
properties display in the Property Editor:
Host Name is the Internet Protocol host name for the selected network
adapter.
IP Address is the Internet Protocol (IP) Address for the selected network
adapter.
Enabled will disable the selected network adapter if set to False. (This property
is usually unavailable.)
Wire Speed is the speed of the network that the selected adapter connects to.
Subnet Mask controls which portions of the IP address are deemed
significant. (This property is usually unavailable; for I/O networks, the subnet
mask is always a fixed value, and for other networks defined at the system level,
the subnet mask is configured in the System Editor.)
Network sets the network connected to the selected adapter. (Available
networks are determined in the System Editor .)

CHAPTER 10
Chapter 10 Hardware
Overview
ToolboxST manages I/O packs and terminal boards through a logical unit called
a module. A module consists of up to three I/O packs connected to a main
terminal board and (optionally) one or more auxiliary terminal boards. The
configuration is known as a simplex configuration when one I/O pack is present,
dual if two I/O packs are present, and TMR if three I/O packs are present. (The
configuration of module redundancy is independent of the network redundancy
and controller redundancy settings.)
To help with identification and version management, each I/O pack has an I/O
compatibility code and a configuration compatibility code. These codes identify
the I/O map layout and the configuration area for a pack. For each compatibility
code set, there are multiple hardware forms that are used to identify physical
characteristics of the pack. Each I/O pack module that can be added to a Mark
VIe controller device is identified by both its hardware form factor and its
compatibility codes. For example, PDOA_2_2 represents the discrete output
module with I/O compatibility code 2 and configuration code 2.
GEH-6700 ToolboxST Chapter 10 Hardware 10-1

Network Redundancy
A controller can have one, two or three I/O networks in a simplex, dual or TMR
configuration. The configuration of network redundancy is separate from
controller redundancy and module redundancy.
To change the network redundancy
From the Hardware tab Tree View, select the I/O Hardware item.
Select the Network

Redundancyitem in
the Property Editor
and use the drop-down
list to select Simplex,
Dual or TMR.
10-2 Chapter 10 Hardware GEH-6700 ToolboxST

Modules
Adding Modules
To add a module to a device configuration
1 From the Hardware tab, right-click the I/O Hardware item in the Tree
View and select Add Module to display the Insert Module Wizard.
Select an I/O pack

redundancy type.
Select a module type.

(The types of available
modules vary based on
the selected network and
I/O pack redundancy.)
Select Next.

Click to view information
about the currently
selected module version.
Use the drop-down list to

select a module version.
Listed module versions
depend on the available
compatibility codes.
Enter the bar code from the

terminal board attached to
the I/O pack(s). If you are
adding a module to a live
system, any undefined bar
codes connected to the
network are available in the
drop-down list.
If this check box is

selected, the module
must be present and
functioning for the
controller to go online.
Select Next.

Select a terminal
board and
hardware form.
Panel Name and

Terminal Board
Location are optional
and can be configured
later.
Configuration settings
and Ethernet
connections for each I/O
pack are set individually
in this area.
Select Next.
To add auxiliary terminal

boards, select an auxiliary
position from the drop-
down box, and then select
a terminal board and a
hardware form to place in
the selected position.
The Panel Name is copied

from Page 3 and cannot be
changed.
Select Next.

2 From the Confirm LanModule Configuration page, review the
configuration summary, and then click Finish to add the new module.
Review the configuration summary,

and then click Finish to add the
new module.
Organizing Modules
Modules can be stored in units called groups for organizational purposes.
To create a group
From the Hardware tab Tree View, right-click the I/O Hardware item
and select Add Group from the menu. Type a name for the group and press
ENTER.
To add modules to a group
From the Hardware tab Tree View, drag a module to the desired group.
When the mouse pointer changes to a symbol, release the mouse button to
move the module.

Modify Module Configuration
To modify an existing module
From the Tree View, right-click the module to modify, and then select
Modify Module from the shortcut menu to display the Modify Module
dialog box.
If this check box is

selected, the module Selects the I/O
must be present and pack redundancy
functioning for the level (Simplex, Dual
controller to go online. or TMR).
Enter the bar code from the

terminal board attached to
the I/O pack(s). If the
system is live, any Changes the group that
undefined bar codes contains the module in
connected to the network the Tree View and in
are available in the drop- diagrams.
down list.
Use these boxes to

select a terminal
board and hardware
form.
Some modules support Panel Name and

auxiliary terminal boards. Terminal Board
To configure auxiliary Location are optional
terminal boards, select an settings.
auxiliary position from the
drop-down box, and then
select a terminal board
and a hardware form to
place in the selected
position.
The Panel Name Configuration settings

is copied from the and Ethernet
Terminal Board section connections for each
and cannot be changed. I/O pack are set
individually in this
area.

Summary View
When you select a module from the Tree View, a variety of tabs that are used to
configure the module are displayed in the Summary View. Each module
displays four common tabs (Summary, Parameters, Internal Points, and
Diagnostics). Many modules also display custom tabs that configure available
I/O capabilities. For information about the settings configured by I/O pack-
specific tabs, refer to the I/O pack documentation.
For example, the following set of tabs (taken from a PDOA module) contains
the base set of tabs as well as two other tabs, Outputs and Inputs.
Summary Tab
The Summary Tab displays a graphical overview of the selected module.

Parameters Tab
The Parameters tab configures all module-specific parameters. After a parameter
is changed, updated psuedocode files must be downloaded to the I/O packs, but
the download operation is done online and does not require a reboot of either the
controller or the I/O packs.
Note Some infrequently used parameters are classified as Advanced and are
hidden by default. To display Advanced parameters, click the Show/Hide
Advanced button on the toolbar.
Internal Points Tab

The Internal Points tab shows available data points from the module that have no
physical endpoint. These IoPoints exist only internally in the module, and can
be connected to a variable for use in code.

Diagnostics Tab
The Diagnostics tab can check the results of diagnostics that are available on I/O
packs. Each pack has a unique set of diagnostic signals that can be monitored.
For more information about the fault codes used in an I/O pack, refer to the
Diagnostics section of the I/O pack documentation.
Manually retrieves the Permanently removes If checked, inactive

latest diagnostic inactive faults from faults are temporarily
messages. the list. hidden.
Selects the desired

redundancy device in a
Dual or TMR
configuration.
Timestamp when
the message
occurred.
Fault code from 1 - active Description of the fault

the controller. 0 - inactive that occurred.
Reporting
Create I/O Report
ToolboxST can generate an I/O report that contains configuration details about
the I/O Hardware in a system.
To view or print an I/O report
1 From the Hardware tab Tree View, right-click I/O Hardware and select
Create I/O Report.

2 From the Select IO Report Columns dialog box, select and arrange the
columns you want included in your report. When you are finished, click
OK.
Add selected columns Add all available

to the report. columns to the report.
Move the selected

report column up or
down in the column
order.
Remove selected Remove all

columns from the columns from
report. the report.
3 The I/O Report opens in a new window. From the report window, you can
review, filter and print the report. For more information on working with
reports, refer to the section, Reports.

Upgrade Module
Modules can be upgraded to a different compatibility code set if one is available.
To upgrade a module
From the Hardware tab Tree View, right-click the module to be upgraded
and select Upgrade Module. The Upgrade Wizard displays.
For the example module shown below, there are two module versions available:
a PDOA with compatibility code set 2,2 and a PDOA with compatibility code
set 3,3.
Click a new module

version to upgrade
the module.

Working Online
Download Parameters
After modifying parameters in a module, you must download to the module
before the new settings take effect. Downloads to a module are separate from
downloads to a controller.
To download parameters to a module
From the Device menu, select Download, and then select Download
Wizard. (For more information on the Download Wizard, refer to the
section, Download Wizard.)
Compare Parameters
While making changes to a modules configuration, it is often useful to compare
the downloadable configuration items currently stored in the pack with the
current configuration of the same items in ToolboxST.
As module parameters directly affect the operation of the

controller and associated I/O packs, always check the
Compare Parameters dialog box before downloading new
parameter values to a component to reduce the risk of
improper operation or damage to the unit.

To open the Compare Parameters dialog box
From the Hardware tab Tree View, right-click a module to compare and
select Compare Parameters.
The differences between the controller

and the ToolboxST configuration are
displayed in a hierarchical tree view.
To roll back any

changes you have made
in ToolboxST and replace
them with the current
value uploaded from the
pack, select the check
box for the parameter.
Click OK to upload the selected

values from the controller into
ToolboxST, replacing your changes.

CHAPTER 11
Chapter 11 Software
Software Overview
There are two system components for creating downloadable application
software, controllers and library containers. Controller components contain the
application software that is downloaded to a particular controller. Library
containers contain user block libraries of reusable blocks that can be referenced
and used by controller components.
Controller application software consists of function blocks that perform logical

and mathematical operations on the variables of the block. This network of
blocks and connected variables controls a particular machine through physical
inputs and outputs.
Function blocks can be grouped together into user blocks. These user blocks can
be used in other user blocks or in a program. When a program contains a user
block, that user block can be scheduled to run periodically. This period is a
multiple of the controllers frame period and can be offset from the beginning of
its period in order to balance the processor load within the controller.
User block variables can be either global or local, but all program variables are
global. A variable must be global to be connected to either Turbine I/O or
Ethernet Global Data (EGD). A local variable is restricted in scope to its user
block, meaning it cannot be accessed from other locations. Global variables are
referenced using the variable name, program name dot variable name
(Prog1.VarName), or block name dot variable name (USB1.VarName)
according to the Global Name Prefix (GNP) property.
GEH-6700 ToolboxST Chapter 11 Software 11-1

The levels of programs and
user blocks that are
downloaded to the controller
are all shown as items in the
Tree View of the Software Tab
of the Component Editor.
Selecting items in the Tree

View displays the properties of
that item in the Property
Editor as well as pertinent
information in the Summary
View. The item selected in the
Tree View can be
edited in the Property Editor
and Summary View if
the password protection is
unlocked and the item is not in
a linked user block.
Function Blocks
The basic unit of application software in the controller is the function block.
Each function block corresponds to software on the controller and is represented
in ToolboxST by block libraries. These libraries are part of the installation of a
particular type of controller.
Blocks have input and output variables, which can be connected to other
variables, Turbine I/O, or EGD variables. Each instance of a block has a name
that is unique in that blocks context. The combination of the variable name with
the blocks name and context give each variable a unique name within the
controller. Blocks in the same user block can reference each others variables
using the block name and variable name separated by a period.
Blocks are typically added to a user block in either a controller component or a

user block library by dragging them from the library palette to the user blocks
block diagram. For more information about editing blocks, refer to the section,
Block Diagram Editor.
11-2 Chapter 11 Software GEH-6700 ToolboxST

User Blocks
User blocks that are created to be reusable are called User Block Definitions.
They are defined in a user block library, which is contained in a library container
at the system level.
User blocks can be used both to store code for reuse and to break code up into
more understandable sections. There are three types of user blocks:
Linked user blocks are defined as user block definitions in a user block library
and are then inserted into a program or another user block. Linked user blocks
cannot be changed at the instance (with a few exceptions), but they can be
updated with a new version from the user block library. They are shown on the
Tree View as a linked chain .
Unlinked user blocks allow the user to edit the user block in the controller
component and prevents updates from the original user block definition when all
of the user blocks in a controller are instanced. Once linked user blocks are
inserted into a program or another user block, they can be unlinked by setting
the Unlink property to True. They are shown on the Tree View as an unlinked
chain .
Embedded user blocks can be inserted into a program and are not based on
user block definitions. Like function blocks, they are shown as a normal block
with inputs and outputs .
Like function blocks, user blocks can have variables that act as the inputs and
outputs of that user block. Once a linked user block has been added to a
program, that user block can become out of date if the user block definition from
which it came is modified. Use the Instance command to update that user
block. For information about the interaction between user blocks and user block
definitions, refer to the section, Managing Blocks.
To create and use a linked user block
1 From the System Editor, open a library container.

2 Right-click the User Block Libraries item and add a library.
3 Right-click the library and add a user block definition.
4 Save the library by clicking the Save button on the toolbar.

5 From the System Editor, open a controller.
6 Select the Software tab.
7 Make sure the new library displays in the Summary View. If not, right-
click the Programs node in the Tree View, and then select Library
References.

Select the new library
checkbox. Click OK. The
new library displays in
the Summary View.
8 From the Tree View, select a Program or right-click to add a new

Program.
9 Insert a linked user block by selecting the user block definition from the
dialog that displays.
- or -
Insert an embedded user block and then drag the linked user block from the
library palette onto the block diagram for that embedded user block.
To update a linked user block in either a library or controller

component
1 From the System Editor, open a library component.

2 From the Tree View, navigate to the user block to update.
3 Edit the user block using the Summary View or the Property Editor.
4 Save and close the library.
5 From the System Editor, open a library or controller component.
6 From the Tree View, right-click the user block to be updated, and then
select the Instance command from the Shortcut menu.

Programs
Programs hold the user blocks that make up a particular controllers application
software. The user blocks in a program (but not in other user blocks) can be
scheduled individually. Program variables can also be created that are global to
the controller component. Each program is contained in an XML file and can be
imported to other controllers using the Import Existing Program command.
The Programs item properties allow the user to specify particular behavior when
a linked user block is inserted or instanced. From the Property Editor, the
Merge Variables At Instance property applies to the variables of a user
block. If this property is set to True, some of the properties of the instance can
be modified. If there is no default value set in the user block definition, that
property is left intact. If the Merge Variables At Instance property is set to
false, then the variable properties are always updated when the user block is
instanced.
The Remove Unused Variables property helps to keep the variable list short
for user block definitions that use instance scripts to remove particular blocks
from the user block instance. If this property is set to True, any variables in a
user block that are not used are removed when the user block is inserted or
instanced.
User Block Definitions

User block definitions consist primarily of function blocks, user blocks, and
variables. The variables of a user block definition act as the parameters and can
be either local or global. User block definitions with global variables can only be
used once in a given controller unless the variable name contains a text
substitution or the variable's GlobalNamePrefix property is set to Full, Block or
Program.
User block definitions are the origin of both linked and unlinked user blocks.
Each user block has a version and description to help manage reusable
application software.
To specialize user blocks so that a set of code can be used in multiple situations,
instance scripts and text substitution are provided. These two constructs
work with the ToolboxST automation interface and user attributes that belong to
either the user block or the controller component.

User Attributes
User Attributes are named values that allow specialization of user block
Definitions. They consist of a name, a data type, a description, a value and a
PromptforInput property.
The PromptforInput property causes a dialog box to display so that you can
verify the attribute value when the user block that owns the user attributes is
inserted. Named attributes can be used to change the variable names and
connections by substituting strings specified in user block attributes. User
Attributes for a user block can be changed at the instance. For more information
about user attributes, refer to the section, Working with User Blocks.
Instance Scripts
Instance scripts run when a user block is either inserted or instanced. Their
primary purpose is to exclude particular blocks or user blocks from a user block
definition.
Text Substitution
Certain text fields such as variable names, descriptions, and block connections
can have some portion of the text replaced when the user block is inserted or
instanced. To specify that substitution should occur, place the name of a user
attribute with a data type of string between braces {}. For more information,
refer to the section, Application Software Examples.
User Block Libraries

User block definitions are defined in user block libraries, which are contained in
a systems library container. They can be referenced individually in the
controller component.
Each library is contained in an XML file and can be ported to other library
containers using the Add Existing Library command of the user block
libraries item.

Library Container Editor
Overview
The Library Container Editor window is used to create reusable application
software that can be included in other controller components.
Library Containers are added to a system as a separate component. Double-click

the component icon in the Tree View to display the editor as a separate window.
Each library container can contain one or more libraries, which in turn contain
user block definitions. A user block definition is a collection of function blocks
and user blocks with input and output pins. For a more detailed explanation of
user block definitions, refer to the section, Software Overview.
The following window displays the major parts of the Library Container Editor
and the terminology that is used when referring to the editor.

The Validate command checks
the configuration for errors,
connection compatibility, data The Finder is
types, and equations. Validation used to find and
status is displayed in the Log tab. replace items.
User Block
Libraries is the top
item in the Library
Container.
Tree View lists all items

in the Library
Container Editor. It is
also used for major
changes like adding or
deleting libraries.
Property Editor
provides a consistent
way to edit the
currently selected
item.
Component InfoView
displays specific
information about the
currently selected tab.
Summary View provides an overview of the item selected in theTree

View. Application software is edited here in the Block Diagram. The
Block Diagram is used for specific changes like connecting two blocks in a
user block definition.

To add a Library Container to a system
From the System View, right-click the system name and select Insert
New, Library Container as shown below to display the Library
Container Creation Wizard.
Enter the new name

and select the Type of
library. Click Next to
display the Product
Version page.

Select the Version and then
check the Optional Libraries
to include. Click Finish to
create the Library Container.
From theTree View,

double-click the new
Library Container to
display theEditor window.
Tip Different versions of the controller component can be used as the basis
for a Library Component. A software block library is always included that
contains basic function blocks, such as Move and Average. There are also
optional libraries, which contain more specialized blocks that can be included in
the Library Container.
When new versions of the controller software are installed, library containers
continue to use the version they were previously configured with until they are
upgraded. (If the old version is uninstalled, the library container must be
upgraded before it can be opened.)
To upgrade a Library Container
1 From the Tree View, select any Library Container item.

2 From the File menu, select Upgrade to display the Upgrade Wizard.
3 When the introduction page displays, click Next.

Select the
desired version and
click Finish. Verify that
the upgrade completed
successfully by viewing
the Log tab in the
Component InfoView.
You will be informed if
new versions are
unavailable.
Library Container Editor/User Block Libraries

From the System Editor, double-click the Library Containers item to
display the editor window. User Block Libraries is the top item in the Tree
View. Multiple libraries can be added to a library container to break up the
application software into separate pieces. These can be referenced individually
in the controller component.
To add a new library to a Library Container
From the Tree View, right-click the User Block Libraries item, and then
select Add Library to display the Add New Library dialog box.
Enter a name for the new library and click OK.
Note Each library is contained in an XML file and can be imported into other
library containers.

To add an existing library to the Library Container
From the Tree View, right-click the User Block Libraries item, and then
select Add Existing Library to display the Select Existing User Block
Library dialog box.
Select the desired library (.xml file) and click Open.
Tip The Summary View for the User Block Libraries item displays
names and locations of all the function block and user block libraries that are
defined in this library container. The version of the function block library used
by this library container can be determined by looking at the Directory field and
observing the path to the library.
Library Property Editor

When a library is selected, the following properties are available.
Description is the description for this library.

Name is a unique name for this library.
Protection properties allow control of who has the right to View, Modify
Data, or Modify Design of this library. For a more detailed explanation of
protection, refer to the Security section.

Library Summary View
The Summary View shows the name, version, category and description of all
User Blocks in the currently selected Library.
User Block Definitions
Add a User Block Definition

Each library can contain many user block definitions.
To add a User Block Definition to a system
From the Tree View, right-click the library item and select User Block
Definition to display the Add New User Block Definition dialog box.
Enter a new name for the library. Click OK.
Sort User Block Definitions

The User Block definitions can be sorted alphabetically. If additional user block
definitions are added, the sort must be repeated.
To sort User Block Definitions alphabetically
Right-click the Library item and select Sort User Block Definitions.

User Block Variables
The variables of a user block definition act as its parameters and can be either
local or global. The following commands are available when a variable item is
right-clicked in the Tree View.
Add Variable allows a variable to be added to the selected User Block. Once
the new variable is added, properties become available in the Summary View.
For more information on setting variable properties, refer to the section,
Property Editor.
Add Undefined Variable allows you to add all of the undefined variables in
the User Block Definition to the variables of the User Block Definition.
Undefined variables are variables that have been referenced in a User Block
Definition but have not yet been defined as part of the user block variables or
user block.
Working with User Blocks

User Attributes are named values that allow specialization of User Block
Definitions. They consist of a name, a data type, a description, a value and a
PromptforInput property.
The PromptforInput property causes a dialog box to display so that you can
verify the attribute value when the user block that owns the user attributes is
inserted. Named attributes can be used to change the variable names and
connections by substituting strings specified in user block attributes. User
Attributes for a user block can be changed at the instance. Refer to the Overview
section of Application Software Design for examples on how to use
attributes.
To add a User Attribute to a User Block Definition
From the Tree View, right-click the User Block Definition and select
Add User Attribute to display the Add User Attribute dialog box.

Enter a name for the new attribute, and then click OK.
Click the Attributes item in the Tree View to display properties in the
Summary View. The properties can be modified as required.
Instance Scripts
Instance scripts run when a user block is either inserted or instanced. Their
primary purpose is to exclude blocks from a user block definition based on user
attributes that are defined in the controller component. For examples of instance
scripts in use, refer to the section, Application Software Design.
To add an Instance Script
Add Instance Script.
Instance
Select this command to get a new copy of the User Block Definition from the
library. In addition to updating the user blocks, this command causes the
instance scripts and text substitutions for all of the top-level user blocks to run.
It is not possible to undo this command.
To instance a User Block Definition
Instance.
Validate
This command checks the selected User Block Definition for errors. Validate
checks connection compatibility, data types, and equations. Validation status
displays in the Log tab. Double-click the error in the Log tab to locate the
application software that caused the problem.
To check a User Block Definition for errors
Validate.

Property Editor
Description is the description of this user block.

Name is the unique name of this user block.
Instance Script runs when the block is instanced.
Protection properties control the View, Modify Data, or Modify
Design permissions for this library (refer to the section Security).
Version is the user defined version of a user block.
Category is the name of a category to which this block belongs.
Summary View
Most of the work in creating a User Block Definition involves inserting different
types of blocks and connecting them together to perform a function using the
Block Diagram Editor. For more information, refer to the section, Block
Diagram Editor.

Software Tab
The Software tab in the Component Editor contains all of the application
software downloaded to that controller.
Tree View displays an outline

of the application software.
When Programs is expanded,
it displays a list of all the
programs in the controller.
Under the Programs item

are the programs for the
controller. Each program
contains variables,
attributes and blocks.
Summary View displays

a list of all the software
files associated with this
controller, including
function block library
DLLs, user block
libraries and program
files.
Programs Item
The Programs Item is a container that holds all programs in the controller. Its
shortcut menu contains actions that affect all programs in the controller, such as
changing library references and instancing all top user blocks. The shortcut
menu also contains commands to add a new or existing program to the
controller. For more information on adding programs, refer to the section,
Creating a Program.
Library References
A controller has two types of libraries:
Function block libraries that describe software that comes as part of the
controller firmware
User block libraries that combine these function blocks into user blocks

To reference a User Block Library
1 From the Component Editor window, select the Software tab.

2 From the Tree View, right-click the Programs item, and then select
Library References. The Library References dialog displays all block
libraries in two tabs.
3 From the User Block Libraries tab, select the check box next to libraries
that you want to reference in this controller. Clear check boxes for libraries
that should not be referenced.
If all the blocks of a Library

Container are included,
check the Library
Container check box. If all
of the libraries of the system
are included, check the
System check box.

To reference a Function Block Library

2 From the Tree View, right-click the Programs item, and then select
Library References. The Library References dialog displays all
available user block libraries.
3 From the Optional Libraries tab, select the check box next to libraries
that you want to reference this controller. Clear check boxes for libraries
that should not be referenced.
Click the Add Library button to

add an external function block
library. A Browser window
displays the available .dll files.
Instance All
The Instance All command creates a new copy of the top-level user blocks
from the referenced user block libraries. In addition to updating the user blocks,
this command causes the instance scripts and text substitutions for all of the top-
level user blocks to run.
Note It is not possible to undo this command.

Property Editor
The Programs Property Editor has two properties that control how instancing
works:
Remove Unused Variables removes the unused variables for all linked user
blocks in this device when the user block is instanced.
Merge Variables at Instance merges certain variable properties by allowing

them to be modified at the instance and not overwritten when reinstanced. To
merge means to accept the instance value of certain variable properties. This
only happens when the User Block Definition variable property does not have a
value; otherwise, the definition value is used.
Use the drop-down list

box to select.
Creating a Program
The programs item allows you to add programs to a controller.
To add a program

2 From the Tree View, right-click the Programs item to display the
Programs shortcut menu.
Note The Add Existing Program command reads an XML file from another
system or controller into the current controller.
Select Add Program or

Add Existing Program
from the shortcut menu.
3 Enter the new program name or select an existing XML file from the
Select Existing Program dialog box.

Add a User Block
To add a User Block
A User Block can be either linked from a user block library or embedded acting
as a container for function and user blocks.
Right-click the program name

and select Add User Block
from the shortcut menu to display
the Add User Block dialog box.
Enter a name for the

new block.
To insert a linked block,

check the Select Library
Block box.
Then, select a category
for the Categories box
and a block from the
User Blocks box.
Click All to select all available

categories. Click None to
deselect all categories.

Import Table CSV File
Table definitions are multi-dimensional variables used on specific interpolator
blocks. They have either one or two input arrays and a matching one or two-
dimensional output array. A block input is interpolated against the input array or
arrays and an output is interpolated from the corresponding output array. A
single data-structure is provided for this function instead of a block so that it can
be better identified, maintained, and tracked. Table definitions have special
Version and ID text fields and can be imported and exported to a CSV file. For
more information on tables, refer to the section, Table Definitions.
To add a table definition
1 From the Software tab, select a Program in the Tree View.

2 Right-click the program name and select Import Table.csv file from the
shortcut menu to display the Table Definition dialog box.
3 Select the desired table definition file and click Open. The Table Definition
file is inserted into the program.

Program Variables
Program variables are global variables that are associated with a particular
program. The variables display under the program item in the Tree View.
Undefined variables for a program are global variables that have been referenced
in a controller but have not been defined as part of a program or user block. For
more information on variables and the variable data grid, refer to the section,
Variable Data Grid.
To add a variable to a program
1 From the Software tab, expand the program item.
Right-click the Variables item

and select Add Variables or Add
Undefined Variables from the
shortcut menu.
2 Enter the new variable name in the Add New Variable dialog box and
click OK. The new variable is added to the list in the Summary View.
Note Variables can also be added in the Summary View by directly editing the
last row of the variable grid.
Property Editor
The Property Editor allows you to edit the name, description, and execution
order of the program selected in the Tree View.
Description Allows you to describe the program. Click

Description and then click to enter text.
Name Allows you to name the program.
Execution Order Sets the order of execution of this program in the
controller.

Summary View
The Summary View of a program displays all user blocks in that program and
associated scheduling information. The Frame Multiplier and Schedule Offset
fields can be changed from this view (see below). The available columns are as
follows:
Frame Multiplier The number of frames at which the user block runs.
Schedule Offset Offset from beginning of frame at which the user
block runs.
Execution Order Sets the order of execution in the program.
User Block Name The name of this user block.
Period The actual period in milliseconds at which this user
block runs. Calculated by multiplying the frame
multiplier by the controllers frame period, which is
set on the General tab.
Description The description of this user block.

To change the frame multiplier or the schedule offset
Click the Frame Multiplier or Schedule Offset

cell for the user block to be changed and
select from the drop-down list box.
Note Since the schedule offset depends on the frame multiplier, it is possible to
select a frame multiplier for which the current schedule offset is invalid. This
will cause a validation error when you build the application.
User Block
The user blocks of a controller program display in the Tree View below the
Programs item.
User Block
User Block Variable
Instance
Instancing a user block updates it to the latest version from the user block
library. Embedded and unlinked user blocks are disconnected from the library,
so instancing goes through the blocks in that user block and instances the linked
user blocks.
To instance a user block
Right-click the user

block and select Instance
from the shortcut menu to
update the selected
user block.

User Block Variables
User block variables are considered local to a user block and display under the
associated user block item in the Tree View. The variables can only be modified
if the user block is either embedded or unlinked and it is not locked with
password protection. Undefined variables for an embedded or unlinked user
block are local variables that have been referenced in the user block.
To add a variable to a user block
1 From the Software tab, expand to display the Variables item.
Right-click the Variables item

and select Add Variables or Add
Undefined Variables from the
shortcut menu.
2 Enter the new variable name in the Add New Variable dialog box and
click OK. The new variable is added to the list in the Summary View.
Note Variables can also be added in the Summary View by directly editing the
append row of the variable grid.
User Attributes
User block attributes only display on linked or unlinked user blocks whose user
block definition contained attributes in the library. They can be modified so that
when their parent user block is instanced, the modified attributes are used in the
scripts and text substitutions that access them. For more information about
adding and modifying attributes, refer to the section, Working with User Blocks.

User Block Properties
The Property Editor for a user block displays slightly different information
depending on whether it is a top-level user block in the program. Top-level
blocks contain scheduling information, but a user block contained within another
user block does not.
Schedule Offset: Offset from beginning of frame at which the user block
runs.
Frame Multiplier: The number of frames at which the user block runs.
Version: Version is the user-defined version of a user block.
Protection: Expand to show the access rights for this user block
definition.
Unlink: Unlinks the user block from the definition.
Execution Order: Sets the order of execution in the program.
Name: The name of this user block.
Description: The description of this user block.
BlockType: The name of the user block definition in the library
from which this user block started.

Summary View
The Summary View of a user block displays the block diagram for either the
user block selected in the Tree View or its container.
If the top-level user block is selected,

then the block diagram displays
the contents of the user block as
follows.
If a user block is selected within a user block and the

contents of the selected block are collapsed and not
visible, then the block diagram displays the contents
of the container user block with the user block
selected in the Summary View as follows.

If the selected block is a user block within a user block and the contents of the
selected block are expanded and visible, then the block diagram displays the
contents of the selected user block as follows:
Finally, if the selected block is a function block, then the block diagram displays
the contents of the container user block with the function block selected in the
Summary View as follows:

Variable Editors
Variables can be edited using the Data Grid and Property Editors. The Data Grid
is used to view or edit variable definitions, and it can be configured to display a
subset of the variable properties. For more information, refer to the section, Data
Grid Editor.
Click a program or user block The properties of the

variable to display a list of variables variables can be edited
and their properties in the Summary View. from the Data Grid.
Property Editor allows

you to edit all properties of
the variable selected in
the Data Grid.

Variable Properties
Alarm Set True to enable the variable as an alarm. Alarms are used for problems that require
the operators attention and acknowledgement. The alarm queue consists of a list of
time tagged alarm state transitions.
Alarm Class Select a System Configured Alarm Class. This is used by the HMI to classify and
colorize alarms.
Alarm On Zero Set True to cause the alarm on a 1 to 0 transition. Requires Alarm=True.
Event Set True to enable the variable as an Event. Events are stateless messages that are
not queued within the controller. When an event occurs, a time tagged transition
message is sent to any HMIs that have signed up for events.
Hold Set True to enable the variable as a Hold. Holds are similar to alarms. The hold queue
consists of a list of time tagged hold states in the turbine startup sequence.
SOE Description This property can not be modified. It is automatically entered from the hardware library
if the hardware point is defined as an SOE. SOEs are similar to event messages
except they are associated with I/O transitions, instead of application variable
transitions. They are also typically time stamped to a much finer resolution (1ms) than
alarms or events.
Visibility Determines when the pin is shown on the block diagram.
Display High Limit This is the default upper limit for displays on HMI (e.g. bar-graph or trending displays).
If a Format Spec has been specified and this display high attribute is not specified, the
Format Spec Engineering Max will be used.
Display Low Limit This is the default lower limit for displays on HMI (e.g. bar-graph or trending displays).
If a Format Spec has been specified and this display low attribute is not specified, the
Format Spec Engineering Min will be used.
Display Screen Default HMI screen for this variable.
Entry High Limit This is the default upper limit for setpoint entry on HMI (e.g. bar-graph or trending
displays). If a Format Spec has been specified and this entry high attribute is not
specified, the Format Spec Engineering Max will be used.
Entry Low Limit This is the default lower limit for setpoint entry on HMI (e.g. bar-graph or trending
displays). If a Format Spec has been specified and this entry low attribute is not
specified, the Format Spec Engineering Min will be used.
Format Spec Format Specifications can be assigned to a variable. These are system owned format
specifications. The format specifications are unique for each measurement system and
are grouped into sets. (For example, a temperature set may contain a format
specification for English in degrees Fahrenheit and one for metric in degrees Celsius.
Precision Number of digits to show to the right of the decimal point. This is the default for
precision when displaying the number on HMI. If a Format Spec has been specified
and this precision attribute is not specified, the Format Spec Precision will be used.
Units Engineering units. If a Format Spec has been specified and this Units attribute is not
specified, the Format Spec Units will be used. If you are using the SDB version of the
HMI device, this attribute will not be used. Only the format specification's Units string is
used.
Array Number of elements in this array variable.
Connection This allows a variable to be connected to another variable.
Description The description of the variable.
Full Name The full name is the fully qualified name of the variable. For example a variable name
gas_fuel_opt in a user block named Config under the Program CORE would have a
full name of CORE.Config.gas_fuel_opt .
Initial Value Initial value editor allows array length, data type and enumeration editing.
Name The name of the variable.
Nonvolatile Save in Non-Volatile RAM.
Type This is the data type of the variable.
Long Term Deadband Long term deadband if this variable is to be long term data collected. Sent as
DeadBand to a Legacy SDB.

Short Term Deadband Short term deadband if this variable is to be short term data collected.
Access The Access property is used primarily for EGD.
ReadOnly The variable can be read on EGD.
ReadWrite The variable can be written to via EGD.
NoAccess The variable cannot be changed with ToolboxST.
Control Constant This allows a variable to be configured as a setting that is initialized at startup to its
initial value. Control constants can be viewed in the Control Constant view
(View\Control Constant). For additional information, refer to the section, Control
Constant View.
EGD Page This property is used to assign the variable to an Ethernet Global Data Page. Enter the
name of the EGD page that you want this variable to belong to.
Global Name Prefix Variable's Global Name Prefix Type (None, Full, Block, Program). This controls the
form of the global name that displays on the EGD page. For example, the name for
variable IGVA in user block VG_Health in program CORE would display depending on
the Global Name Prefix as:
None IGVA
Program CORE. IGVA
User Block VG_Health.IGVA
Full CORE.VG_Health.IGVA
Scope Variable's Scope (Global, Local.) If a variable is Local, it can only be used in the
program or user block in which it is created. If it is declared Global, it can be used in
other programs and user blocks. A variable must be Global to be used on EGD.
Usage Use to define the behavior of pins on a user block.
Input Input pins are shown on the left of the user block.
Output Output pins are shown on the right side of the user block.
State State pins are shown on the right side of the user block.
Constant Entry is a number. No live data is provided for this pin.

Table Definitions
Many complex mechanical interactions can be modeled using lookup tables. The
controller implements these tables using table definitions. A table definition is
similar to a signal definition, as both are similarly named and are used in
instruction blocks.
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 univariant tables
and consist of X and Z linear arrays of the same length. Tables with two
independent arrays are sometimes called bivariant tables and consist of X and Y
linear arrays and a Z two-dimensional array. Bivariant table definitions display
in the Summary View as follows:
Importing a Table Definition

Table definitions are added to the program by importing a table definition from
an existing CSV file.
To add a table definition
1 From the Component Editor, click the Software tab.
From the Tree View, right-click the

program where the table definition
needs to be added and select Import
Table .CSV file from the shortcut
menu.
2 Select the CSV table definition file (.csv) from the browser window and
click Open.

The table definition is
added under the program
item in the Tree View.

Property Editor
Property Editor allows

you to edit all properties of
the table definition
selected in the Tree
View. The properties are
defined below.
Name The name of the Table Definition.

Adjust The adjust flag determines whether the table's Z
values and limits can be adjusted both in
configurations and online. The Adjust flag is read on
import; if it is false, the table data can not be
changed without another import.
Description The description of the Table Definition.
Identification The Identification text for the Table Definition.
Revision The Revision text for the Table Definition
Maximum Z value Maximum Z value that is used to limit the values
that can be entered in the live or initial values.
Minimum Z value Minimum Z value that is used to limit the values that
can be entered in the live or initial values.
Engineering Y Units Engineering Y units description.
Engineering X Unit Engineering X units description.
Engineering Z Units Engineering Z units description.

Exporting a Table Definition
To export a table definition (.csv)
1 From the Component Editor, click the Software tab.

2 Expand the Table Definitions item and select the table definition to be
exported, such as below.
Right-click the table definition and

select Export Table .CSV file
from the shortcut menu.
3 Select the CSV table definition file (.csv) from the browser window and
click Save.

Online Display and Changes
Table definition data values can be changed when connected to the controller, if
the table has the Adjust property set to True. When online, the live data values
display in green to indicate that there are no differences between the ToolboxST
values and the controller values.
Double-click a value in
the Data Grid. .
Change the value

and click Send &
Close.
The Data Grid displays the differences.
This feature is useful to tune up the table data values in the controller. Once the
table data values are correct, click at the bottom of the

Editor to capture the values in the ToolboxST configuration.

Using Table Definitions in Software Application Code
To add a 2D (Univariant) Linear Interpolator block
The following table definition is used:
1 Connect the Table2D pin to the Table\T_ESPBSJ table.

2 Set the XInput to 40.
3 Build and Download the application code. The output of the block is as
follows.

To Add a 3D (Bivariant) Linear Interpolator block
The following table definition is used:
1 Connect the Table3D pin to the Table\T_DSPNAJ table.

2 Set the XInput to 30.
3 Set the Yinput to 4.
4 Build and Download the application code. The output of the block is as
follows:

Block Diagram Editor
Application software in the controller consists of blocks that perform control
logic functions. The controller provides a library of standard blocks that can be
combined to form user blocks. The Block Diagram Editor allows you to create
and edit user blocks using a visual interface and drag-and-drop tools. The Block
Diagram Editor displays in the Summary View when a user block is selected in
the Tree View.
View Mode
Initially, the user block displays in View mode. In View mode, you cannot
modify the diagram. You can navigate and print the diagram, and you can also
select blocks and pins to display additional information.
Click to switch between Zoom In/Out Detached View

View and Edit mode
Select a user block in the

Tree View. The Block
Diagram Editordisplays
in the Summary View.

Edit Mode
To make changes to a user block, click the View/Edit toggle button to enter
Edit mode. Additional tools will become available on the toolbar and a new
sidebar called the Library View displays on the right side of the Summary
View.
Note If the user block is read only or linked, an error message displays if you
attempt to switch to Edit mode. (For more information about linked user blocks,
refer to the section, User Blocks) If the user block is protected, you will be
prompted to enter the appropriate password.
Library View is divided into multiple

Click to switch between
Additional Editing Tools. categories, each containing one or more
Edit and View mode.
blocks that perform similar functions.
Margin and paper

size rulers.

Diagram Shortcut Menu
The diagram shortcut menu displays when you right-click an empty portion of
the diagram. It contains the following commands:
Auto-Layout Mode controls how the blocks on the diagram are arranged.
Refer to the section, Layout Modes.
Diagram Settings displays the Diagram Settings dialog box.
Insert Sheet inserts a sheet immediately before the current sheet in manual
mode.
Delete Sheet deletes the current sheet in manual mode.
Print Sheet prints the current sheet.
Zoom adjusts the zoom level to either a preset zoom level or a custom value.
View Settings contains options to toggle the rulers, library view, and print
border.
Paste inserts the contents of the clipboard at the selected location.
Layout Modes
When blocks and wires are added to a diagram, they are arranged according to
the rules of the current layout mode. By default, diagrams are created in Classic
Layout mode, where the blocks are arranged by execution order with a focus on
optimal use of space. The Toolbox Classic Layout mode automatically
places wires and creates new sheets as necessary, making it appropriate for
small-to-medium sized diagrams.
List Layout mode arranges blocks in execution order in one column, with
inputs and outputs lined up on the edges of the sheet. All Rung blocks appear as
Rung diagrams instead of as blocks. This mode is ideally suited for sequencing
and can be used to simplify very large diagrams where wiring becomes
confusing.
Manual Layout mode does not arrange blocks or wires and leaves all layout
tasks to the user. It is ideal for users that are familiar with a sheet-oriented
approach to design or for applications where very specific documentation
standards must be met. Manual mode gives you complete freedom to arrange
diagrams, but can be more time consuming to use than the auto-layout modes.

Managing Blocks
To add a block from the Library View
Select the category in the Library View that contains the desired block,
then drag the block to the Edit View. The block displays on the Block
Diagram.
Or,
Press the Insert key to display the Pick Block to Insert dialog box. Select
the desired block and click OK to add it to the Block Diagram.
To edit the properties of a block
Click a block in the Edit View. The block is selected and its properties
display in the Property Editor.

The following properties are available in the Property Editor when a block is
selected:
Instance Name displays a unique identifier that allows the block (as well as its
attributes and pins) to be referenced from other places in ToolboxST.
Selected Pin displays the pin currently highlighted in the Edit View.
Block Type displays the name of the library block that this block was created from
read-only.
Block Data Type displays the name data type for variant pins on the currently
selected block.
Execution Order determines when the block is executed. Setting this property
automatically renumbers other blocks in this User Block. (Execution begins with block
zero and proceeds in increasing order.)
Instance Script scripts that runs when the block is instanced.
Description, text describing the selected block.
Show Description when true, the description text for this block displays on the
diagram.
Top displays the location of the top of the block in the diagram.
Left displays the location of the left of the block in the diagram.
Height displays the height of the block in the diagram.
Width displays the width of the block in the diagram.
Version displays the version number of the source for this block instance.( read-only)
Wiring Block Pins

Block pins are wired together to direct the flow of data through the software.
You can form a connection by using the pointer tool to drag one pin to another
pin. The destination pins Connection property is set to the block that was the
source of the drag-and-drop operation. You can also use the Wiring Tool to
form pin connections, which forms connections to both normal blocks and to
blocks with a configurable number of inputs (called Rubber Pins).
Source of the Wiring Destination, a new

Tool drag-and-drop operation. Rubber pin.

Block Shape Shortcut Menu
When you right-click a block, a shortcut menu displays with the following
commands:
Block Help shows reference documentation on the selected block type in a help
window.
Show Description on Diagram toggles the display of description text for the
block. This text is the most effective way to document a block, as the text stays
attached to the block when the diagram is rearranged.
Edit Block Pins displays the Edit Block Connections dialog box.
Add Pin Group adds the next group of pins in a block with a configurable number
of inputs. For example, on a rung block, this would add the next available pin
unless all 16 are in use.
Remove Empty Pin Groups removes empty pins from the end of a rubber
block. This command does not remove empty pin groups in the middle of the block
(for example, pins A through D cannot be removed if Pin E is used).
Show Boolean Logic as Rung toggles the display of a rung block between a
rung diagram alone and a block containing a rung graphic.
Edit Ladder Logic displays the Rung Editor for a rung block.
Send to Front and Send to Back reorder blocks, causing them to appear above
or below all other blocks and shapes on the diagram when overlap occurs.

Connecting Pins
To connect a single pin
From the Block Diagram Editor, double-click a pin. The Connect Pin
dialog box displays.
This tab is a quick reference Click to access local

showing the variables variables and
connected to the selected pin. enumeration values.
Connect a pin to any

variable or immediate
value by typing the
name of the variable
or the value in this box.
Creates a new
variable in the
user block.
Browse buttons Option buttons

display the Variable specify the type of
Browser. connection.
To connect multiple pins
Double-click a block in the Block Diagram Editor. The Edit Block

Connections dialog box displays.

Click a pin to
select it for editing.
This box displays

the currently
selected pin. Type the name of a
variable or an
intermediate value to
connect to the selected
pin.
Browse buttons
display the
Variable Browser.
Tip Pressing Enter while entering text will select the next pin on the block,
allowing rapid entry of connections.
In the Edit Block Connections dialog box, a prefix letter and a colon
indicate the type of connection. These prefixes allow the connection type to be
specified just like the option buttons on the Connect Pin dialog box, except
prefixes can be typed quickly and pasted from the clipboard. The following are
valid prefixes:
Prefix Type
N: Number or Boolean value

E: Enumeration value
L: Local variable
G: Global variable

Modifying Live Values
While you are connected online to a controller, you can change the current value
stored in a variable. Optionally, you can also force the new value, which
prevents programs defined in block diagrams from overwriting your choices.
To change the value of a variable while online
From anywhere variables are used in the Software tab, double-click a

variable value to display the Send Value dialog box. A dialog box will
display that is appropriate to the data type of the variable as described below:
Boolean Values:
Displays the current

value of the
variable.
Select an option to
change the current
value.
Check this box to

prevent programs from
overwriting your selected
value.
Click here to send the Next Click here to invert the current
Value to the controller and value and immediately send it
close the dialog box. to the controller without closing
the dialog box.
Numerical Values:
Displays the
current value
of the variable.
Enter a new value

for the variable.
Enter a value to be
added to or subtracted
from the variable.
Check this box to
prevent programs
from overwriting your
selected value. Click to increase or Click here to send the Click here to send the Next
decrease the variable by the Next value to the value to the controller
delta value and send the controller and close the without closing the dialog
result to the controller. dialog box. box.

Array Values:
When you are finished
changing values, click here
to close the dialog box.
Double-click an element of
the array to display the
associated Send Value
dialog box.
Shape Drawing Tools

Several drawing tools allow customization of the Block Diagram. These drawing
tools create shapes, which are elements of graphics or text that provide
additional visual information on a drawing sheet. They are accessed from the
Edit View toolbar.
The Variable Tool is only useful in Manual Layout mode as a way to

clarify a variable connection. It inserts a variable reference that can be wired to a
block pin and moved around freely. It is useful for creating diagrams that
conform to specific design standards. For example, all input and output variables
could be drawn on the left and right side of the diagram sheet, clarifying data
flow for the user block. The shape created by the variable tool has the following
properties:
Variable displays the variable represented by the
shape.
Top displays the top location of the variable shape.
Left displays the left location of the variable shape.
Width displays the width of the variable shape.

The Text Tool allows you to enter text anywhere on the diagram. While this
tool is useful in Manual Layout mode, the Description property of each block
may be a more appropriate way to add text when working in one of the two
automatic layout modes.
To use the Text Tool
Click at the desired upper left corner of the text field, drag to the desired
lower right corner and release the mouse button. Enter the text in the dialog
box that displays and click OK. The new shape is added to the drawing.
The shape created by the text tool has the following properties:
Text displays the text displayed by the text shape.
Text Font displays the font used to display the text.
Foreground Color displays the color of the text.
Filled if set to true, the text shape will use the Fill Color as a background color.
Fill Color displays the background color shown behind the text if Filled is set to true.
Top displays the top location of the text shape.
Left displays the left location of the text shape.
Height displays the height of the text shape.
Width displays the width of the text shape.

The Rectangle and Ellipse Tools draw simple geometric shapes with
configurable line and fill colors.
To use the Rectangle or Ellipse Tool
Click the desired upper left corner of the shape, drag to the desired lower
right corner and release the mouse button. The new shape is added to the
drawing.
The Rectangle and Ellipse shapes have the following properties:

Line Color displays the color of the shape's line.
Line Thickness displays the thickness of the shape's line.
Filled when true, the shape is filled with the color specified in the Fill Color property.
Fill Color displays the color the shape is filled with when Filled is set to true.
Top displays the top location of the shape.
Left displays the left location of the shape.
Height displays the height of the shape.
The Image Tool inserts a Windows Metafile (.wmf) or Enhanced Metafile
(.emf) into the diagram.
To use the Image Tool
Click the desired upper left corner of the shape, drag to the desired lower
right corner and release the mouse button. Then, in the Browse for Image
dialog box, provide the path to the .wmf or .emf file that contains the image
and click OK. The image is added as a shape to the drawing.
Note The image file is not embedded in the diagram. All images must be
distributed separately from the XML files for the diagram.
Image shapes have the following properties:

Metafile Path displays the path to the .wmf or .emf file containing the image that is
displayed.
Left displays the left location of the shape.
Top displays the top location of the shape.
Width displays the width of the shape.
Height displays the height of the shape.
Tip To ensure that images can be found when the diagram is moved on the
hard disk, avoid hard-coded path names or mapped drive names. Relative
names, such as ..\Metafiles\bom1.wmf are best.

Additional Toolbar Buttons
Full Screen Editing toggles the Library View, InfoView, and TreeView on
and off. When in full screen mode, more space is devoted to the Edit view
making it easier to work with large drawings.
Detached View Window - This button displays a new window containing a

Block Diagram Editor by itself (without the TreeView or InfoView). The new
window displays same diagram as the main view, but can be scrolled and
zoomed independently.
Tip You can have as many detached views as desired, which can be
convenient for dragging pins from one drawing to another drawing.
Alignment Tools are available when multiple drawing shapes are selected
(either by drawing a selection rectangle around multiple shapes using the Pointer
tool or by holding the CTRL key while selecting additional shapes). The tool
modifies the location, width, or height of each shape to match the selected aspect
of the primary selected object (denoted with green selection handles). The Top,
Bottom, Left, and Right alignment tools affect location, while Width and Height
adjust size. Arrange Horizontal and Arrange Vertical equally space all of the
selected shapes along the Horizontal or Vertical axis.
Diagram Settings
The Diagram Settings dialog box contains options that change how the
diagram editor operates, including paper size and other stylistic options. In most
situations, these settings are consistent across all diagrams in a system, but
occasionally a particular drawing may need custom settings. The Diagram
Settings are arranged hierarchically with system level settings in effect unless
other settings are configured. These settings can be overridden by the Device or
Library settings, which take effect at the Component Editor level. The user
settings, saved on a per user basis, override the Device or Library settings, and
finally the Diagram settings are saved per diagram and override all other
settings.
Diagram
User
Device or Library
System

For example, if the System settings specify the paper size as Letter, the Library
and User settings specify Use Parent Setting, and the diagram settings set the
paper size to Legal, that diagram would be shown on Legal size paper while all
other diagrams would be shown on Letter size paper.
To configure diagram settings
1 Right-click an open area of a diagram while in Edit mode and select

Diagram Settings. A dialog box displays with the available scopes.
2 Select a scope to edit System, Device or Library, User, or Diagram

and click OK. The Edit Dialog Settings box displays.
The Edit Diagram Settings dialog allows you to edit the following options:
Size selects the paper size.
Landscape when checked, the longest dimension of the paper becomes the
horizontal dimension, creating a drawing that is wider than it is tall.
Font Sizes controls the size of fonts in the diagram.
Hide Unused Pins when checked, unconnected pins are hidden.
Show Block Drawings when checked, blocks are drawn using graphical
representations of their operation whenever possible.
Show Wired Pin Connection Text when unchecked, the connection text
for wired pins is hidden, reducing clutter on the drawing.
Tip Selecting Default to parent setting or a gray check box indicates that
you have no preference at the current level. The diagram will use the settings
from the next level down in the hierarchy.

Rung Editor
Boolean logic functions are added to a block diagram inside special blocks
called rung blocks. Rung blocks are named after a component of a Relay Ladder
Diagram. In a Relay Ladder Diagram, one or more contacts (which function
similarly to a mechanical relay switch) are connected as a control network for a
single coil, or output. As the diagram is formed with two vertical buses, one
representing power and one representing ground, the completed diagram
resembles a ladder, with each coil and associated contacts resembling a ladder
rung. Rung blocks, like the rungs in a relay ladder diagram, control a single
output.
The Rung block controls variable values using Boolean logic equations. While
you can specify a Boolean logic equation directly by connecting it to the EQN
pin of the rung block, a graphical relay ladder diagram editor is also available to
simplify the process.

To open the RLD Editor
From a Block Diagram, double-click a Rung Block.
or,
Right-click a Rung Block. From the shortcut menu, select Edit Ladder
Logic.
The RLD Editor window consists of both a 16x16 or smaller grid of cells that
can contain contacts or wires and a set of tools used to edit the contents of the
cells.
Wiring Tools Use the Delete tool Drag separators to add or Click OK to save or cancel
to remove wires and remove columns. to discard changes .
contacts.
Drag separators to Displays the current

add or remove rows . equation or error message .
Contacts
Each contact represents a virtual relay switch that is controlled by a boolean
variable. Contacts which can either represent a variable directly or
the negation of the variable are added to a ladder diagram using the contact
tools.
To add a contact
1 Select the contact tool that matches the type of contact you
want to add. The mouse cursor will change to reflect the selected
contact type.
2 Click a cell to add a new contact.

3 Double-click inside the cell above the newly inserted contact to open the
Connect Contact dialog box.
Check this box to change all

references to the listed
variable in the rung.
Enter or select a variable

to connect to the contact.
Wires
Wires are used to connect contacts to the coil and to each other.
To add a wire
Select the Wire tool , and then click a location on the grid.
Wires can only be drawn vertically or horizontally, as demonstrated below:
A good wire A bad wire
Coils
The diagram always has one Coil.
To connect the coil to a variable
Double-click the coil to open the Connect Contact dialog box. (For more
information, refer to the section, Contacts .)

Adding Rows and Columns
Up to 16 rows or columns can be added to the grid to provide enough space for
large logic diagrams.
To add or remove rows or columns
Drag the boundary between any row or column. Blue text will display
indicating the result of the action.
Errors
You can create rung diagrams in the RLD Editor that do not convert to
compatible Boolean logic functions. Typical errors include not connecting a
contact to a variable, creating a wire or contact that is not connected to power
and ground, or creating a short circuit. If you make one of these mistakes, text
will display on the status bar to help you resolve the error. (When the output
equation is displayed on the status bar, the diagram is correctly drawn and no
errors are detected.)

Application Documentation
For documentation purposes, ToolboxST can print detailed information about
the configuration of a controller. By default, the entire configuration is printed,
but if you are in the Software tab and have selected a Program or User Block,
only the selected item is printed.
Note In some locations, including Reports and the Block Diagram Editor,
shortcut menus contain commands that allow single pages or reports to be
printed.
To print the configuration of a component
Open the Component Editor for the component to be printed. From the
File menu, select Print to display the Print Options dialog box.
The Options tab has the following options:
Page Options tab allows Print Settings tab allows you Print Profile tab manages
you to change the paper to change the destination saved print settings. It stores
size, margins, and printer and its associated all the settings from both the
orientation. settings. Options and Page Option
tabs.
Prints a summary of
configuration settings Page Numbering
for the component. options control page
number assignment.
Linear pages number
sequentially start with
Includes a list of page one.
sections and page Hierarchical pages
numbers. number the same as
linear pages but also
Includes a symbol numbers each section
quick reference and sub-sections,
guide. such as 1., 1.1, 1.2.1
and so on.
Prints all software

programs in the
component.
Prints a reference to Displays a Print Preview Click this button to
all variables in the window with the document print the document.
component. exactly as it prints on paper.

Application Software Examples
The following examples describe five separate, but associated procedures related
to application software design. These procedures build on each other to create a
system, so you must complete them in the order shown below. The procedures
describe how to:
Add a user block definition to a library

Insert a linked user block in a controller
Add a device attribute
Exclude a block from a user block with an instance script
Substitute text into a user block with an attribute
To add a user block definition to a library
1 Open ToolboxST. From the File menu, select New System to display
the New System dialog box.
2 In the Name box, enter test. Click OK to display the System Editor.
3 In the Tree View, right-click the system item to display the system
shortcut menu.

Click Insert New
to display another
shortcut menu.
4 From the second shortcut menu, select Library Container. The Library
Container Creation Wizard opens.

Enter Libraries in the
Name box and click Next.
5 On the Product Version page, click Finish to accept the default library
version and optional libraries.

A new library container is added to the system and the Tree View is updated to
reflect the change.
Open the Library

Editor by double-
clicking the Libraries
item in the Tree View.
Right-click the User

Block Libraries item
and select Add
Library. The Add
New Library dialog
box displays.
Click OK to accept the default library

name. A new library is created and the
Tree View is updated to reflect the
changes.

Right-click the new Lib1 library
item and select Add User
Block Definition. The Add
New User Block Definition
dialog box displays.
Click OK to accept the default

user block name. The user block
definition is created and the Tree
View is again updated to reflect
the changes.
6 Make sure the Lib1Usb1 item is highlighted in the Tree View, then click the
Edit button on the Block Diagram Editor toolbar. The Block Diagram
Editor switches to Edit mode and the Library View displays on the right
side of the block diagram.

From the Library View,
click the Memory Move
category. (You may
need to use the scroll
bars to locate it.)
7 Drag a MOVE block from the Library View to the Block Diagram
Editor to add it to the user block. Repeat this process two more times until
a total of three MOVE blocks display on the block diagram.
8 Save the library container by clicking the Save Configuration button

on the toolbar and close the editor by clicking the Close button in
the upper right corner.

To insert a linked user block in a controller
1 Open the System Editor for the test system created in the previous
procedure.
2 From the Tree View, right-click the system item to display the system
shortcut menu.
From the shortcut

menu, click Insert
New.
Then click Controller, and

Mark VIe Turbine Control.
The Mark VIe Creation
Wizard opens.

Enter the name
G1 for the new
controller.
Click Next to
continue.
Click Finish to accept the default

libraries. A new controller component is
added to the system and the System
Editor updates to reflect the changes.

Open the controller Component
Editor by double-clicking it in
the Tree View or Summary
View.

3 Click the Software tab, and then right-click the Programs item in the
Tree View to display the Programs shortcut menu.
Select Library References
to display the Library
References dialog box.

Click the check box to
the left of library Lib1,
and then click OK to
add a reference to the
library.
4 Right-click the Programs item again and select Add Program from the
shortcut menu. The Add New Program dialog box displays.
Click OK to accept
the default name.
5 Right-click the Prog1 item in the Tree View to display the Program
shortcut menu.
Select Add User Block to

display the Add User Block
dialog box.

Click the User Block
category. The Lib1Usb1
user block will
automatically be
selected, as it is the first
block in the library.
Select the Select

Library Box check
box.
Click OK to accept the

default name. The user
block Lib1Usb1 is
added to Prog1 and
displays on both the
Tree View and the
Summary View.
6 Save the changes by clicking the Save Configuration button on the

toolbar and close the editor by clicking the Exit button .

To add a Device Attribute
examples.
2 From the System Editor, open the controller Component Editor by
double-clicking the controller in either the Tree View or the Summary
View.
From the Component

Editor, click the General
tab. Click the Attributes
item on the Tree View to
display the attribute data
grid in the Summary View.

Click the Name cell on the
append row (indicated by
an asterisk *) and type
Attr1 to name the new
attribute.
3 Change the data type to BOOL by clicking the Type cell on the Attr1 row
and then selecting BOOL from the drop-down list.

4 Change the initial value to False by clicking the Value field of the Attr1
row and then clicking the ellipsis button to display the Modify Value
dialog box.
Select False from

the drop-down
list.
Click OK to accept
the new value.
5 Save the changes by clicking the Save Configuration button on the

toolbar and close the editor by clicking the Exit button .

To exclude a function block from a user block with an instance
script
examples.
2 From the System Editor, open the Library Container Editor by
double-clicking the Libraries item in the Tree View.
Click the plus symbol

to expand the items
Lib1 and Lib1Usb1
and display a list of
blocks.
Right-click the
MOVE_2 block item
to display the block
shortcut menu and
select Add
Instance Script.
The block icon
changes to display
a blue S, indicating
that a script has
been added.
3 Repeat these steps for the MOVE_3 block item.

4 In the Block Diagram Editor, click the Edit button to switch to Edit
mode and then select the MOVE_3 block item in the Tree View. In the
Property Editor, select the Instance Script field and click the ellipsis
button . The script Edit Text dialog box displays with the default
Instance Script: Block.Include =
Device.Attribute("Attr1").BoolValue

5 Add the text NOT between the equal sign and the word Device in the script
to negate the expression as follows: Block.Include = NOT
Device.Attribute("Attr1").BoolValue

on the toolbar, and then close the editor by clicking the Exit button .
7 Open the controller component by double-clicking it in the system editor.
8 Click the General tab. From the Tree View, select the Attributes item.
From the Summary View, click the Value cell of the Attr1 row and then
click the ellipsis button to display the Modify Value dialog box.
9 Change the value to true using the drop-down box and click OK.
10 Click the Software tab. From the Tree View, locate the Prog1 item. If it is
collapsed, click the plus symbol next to the Prog1 item to expand it.
11 From the Tree View, right-click the user block Lib1Usb1 and select
Instance from the shortcut menu to update the user block. The user block
contents display in the Summary View with MOVE_1 and MOVE_2
blocks. MOVE_3 was excluded by the instance script created in step 8
because Attr1 is set to True.
12 Click the General tab. From the Tree View, select Attributes. As before,
click the Value cell in the Attr1 grid row and click the ellipsis button.
In the Modify Value dialog box, set the attribute value to False and click
OK.
13 Return to the Software tab. Right-click the Lib1Usb1 user block and select
Instance from the shortcut menu. This is the same operation that was
performed before, but since Attr1 is now set to false, the instance scripts
will cause the block MOVE_2 to disappear and the block MOVE_3 to
display on the diagram instead.
14 Save the component by clicking the Save Configuration button on

the toolbar, and then close the editor by clicking the Exit button .

To substitute text into a user block with an attribute
examples.
2 From the System Editor, open the Library Container Editor by
double-clicking the Libraries item in the Tree View.
3 From the Tree View, expand Lib1 and right-click the user block Lib1Usb1
to display the shortcut menu.
4 From the shortcut menu, select Add User Attribute to display the Add
New User Attribute dialog box.
5 Change the attribute name to Attr1_u to differentiate it from the previously

created Attr1 and click OK. A new Attributes item will display in the Tree
View under the Lib1Usb1 User Block Definition.
6 From the Tree View, select the Attributes item. The Summary View
displays a list of attributes.
7 Change the Attr1_u data type to STRING by clicking the Type cell (which
currently contains UNDEFINED) and then selecting STRING from the
drop-down list.

8 Change the PromptForInput cell of Attr1_u to True. (You may have to
scroll right in the Summary View to locate the PromptForInput column.)
9 Now that the attribute has been created, we will create a user block variable
with text substitution in its name. From the Tree View, click Variables.
10 From the Summary View, click the Name cell in the Append row
(indicated by an asterisk *) and {Attr1_u}_thing as shown below. Leave the
data type set to the default value, BOOL.
11 Text substitution can also be used in variable connections. To connect the

variable that was just created, click the MOVE_1 block in the Tree View
to display the Block Diagram Editor.
12 Click the Edit toggle button in the Summary View and then double-click
the enable pin of the MOVE_1 block. The Connect Pin dialog box opens.

13 Click the Local Variable option button. Then, enter the variable name
{Attr1_u}_thing in the text box and click OK. The block diagram updates to
reflect the new connection.

on the toolbar and close the editor by clicking the Exit button .
15 To see the text substitution in action, open the Component Editor for the
controller by double-clicking G1 in the System Editor.
16 Click the Software tab. From the Tree View, locate the Prog1 item. If it is
collapsed, click the plus symbol next to the Prog1 item to expand it.
17 From the Tree View, right-click the user block Lib1Usb1 and select
Instance from the shortcut menu to update the user block. An Attributes
item will be added to the Tree View.
18 From the Tree View, click the Attributes item. The Attr1_u attribute
created in step 5 displays in the Summary View.
19 Click the Initial Value cell of the Attr1_u row. Click the Ellipsis button to
edit the value, and then enter the text ABCDEFG to be substituted. Click
OK to close the Modify Value dialog box.
20 From the Tree View, right-click the Lib1Usb1 item and select Instance.
The value entered for Attr1_u will be substituted into the variable
{Attr1_u}_thing and into the MOVE_1 ENABLE pin connection, creating a
variable named ABCDEFG_thing.

21 To verify that the variable name substitution has occurred, click the
Variables item under Lib1Usb1. The ABCDEFG_thing variable will
22 Save the component by clicking the Save Configuration button on

the toolbar and close the editor by clicking the Exit button .

Notes

CHAPTER 12
Chapter 12 DDR
Dynamic Data Recorder (DDR)

The DDR feature collects data when specified trigger events occur. The
advantage of using DDRs over capture blocks is that DDRs can be reconfigured
without having to download application code to the controller. This enables
changes to be made to the DDRs without disrupting the controller during
runtime. Up to 12 DDRs can be configured for the controller.
Configure DDR
To configure a DDR
From the System Editor, double-click the Mark VIe Component. The
Component Editor displays.
From the Component

Editor, click the
Dynamic Data
Recorders tab.
Select the DDR that

you want to
configure.
GEH-6700 ToolboxST Chapter 12 DDR 12-1

Specific DDR information displays in the Summary View.
Edit this information in the Property Editor below.
The Property Editor

displays specific
information for the
selected DDR.
Click any item in the
left column to display a
description of that item.
Click the item in the
right column to edit.
See below for
descriptions of each item.
12-2 Chapter 12 DDR GEH-6700 ToolboxST

Appearance
Name - User defined description for this DDR. This name is used by the
Recorder for the filename.
DataRecorder Setup
Auto Enable - If set, the capture buffer is automatically enabled and then re-
enable 60 seconds after it is uploaded.
Buffer Control
Normal - Data recorder will collect pre-samples before a trigger event and
thereafter continue collecting until Enable transitions false or the collection
fills the buffer.
Circular - Data recorder will collect data indefinitely until Enable

transitions false. The buffer will be filled with the newest samples. No
trigger is used.
Only - Data recorder will evaluate the trigger each execution and only
collect data when the trigger condition is satisfied. Data will be collected
until Enable transitions false or the collection fills the buffer.
Frame Period Multiplier - Extends the sampling period by this multiple. The
base sampling period is the frame period.
Post Trigger Samples - The number of samples that are collected after the
trigger including the trigger sample.
Pre-trigger Samples - The number of samples that are collected before the
trigger.
Setup Variables
Enable - The variable that enables the DDR.
Trigger - The variable that triggers the DDR.
Trigger Setup
Trigger Comparison Type
EQ - The value of the trigger variable must be equal to the trigger value.
GT - The value of the trigger variable must be greater than the trigger value.
GE - The value of the trigger variable must be greater than or equal to the
trigger value.
LT - The value of the trigger variable must be less than the trigger value.
LE - The value of the trigger variable must be less than or equal to the
trigger value.
NE - The value of the trigger variable must not be equal to the trigger value.

Trigger Comparison Value - The value which is compared to the value of
the trigger variable to determine the presence of a trigger. For Boolean trigger
variables, the only valid values for the trigger value are 1.0 for TRUE and 0.0
for FALSE. Note that if an analog trigger variable of a different data type is
configured, it may be possible to specify a trigger value that cannot be exactly
represented by the trigger variable. Users should be aware of this limitation
when specifying the EQ trigger condition.
Trigger Type
Edge - Triggered on the rising edge of the trigger variable.
Level - Triggered on the true condition of the trigger variable.
Status Variables
Status variables, which indicate the status of the associated DDR, are used by
the Recorder to determine when to upload the data. Status variables are always
integers and are automatically defined and placed on the default EGD page.
Add Variables
Variables can be added to a DDR. When a trigger occurs, these variables are
collected by the buffer and are subsequently uploaded by the Recorder and/or
Trender. Each variable is sampled for the total number of samples configured.
This means that if the DDR is set up to record 100,000 samples with three
variables assigned, 300,000 items will be acquired. Up to 96 variables can be
assigned to each DDR.
Note There is a 12 MB size limit on the memory that can be allocated to the
DDRs. If this memory allocation is exceeded, an error is reported during
validation.
To add a variable
1 From the Component Editor, select the Dynamic Data Recorder tab
to display the DDR list.
Right-click the desired

DDR and select Add Variable.

The Variable Browser dialog box displays.
2 Select the desired variables and click OK to insert the variables.
Update DDR
DDRs are updated separately from the application code download.
To update a DDR
1 From the Component Editor, select the Dynamic Data Recorders tab
and click the desired DDR.
2 Click the Build button.
3 From the Device menu, select Download, and then select Update
Dynamic Data Recorder. Or, click the Update Dynamic Data
Recorder button .

Import and Export DDR
To import a DDR from a .tre file
1 From the Component Editor, select the desired DDR.
Right-click the DDR

and select Import
Configuration.
2 From the Import File dialog box, select the .xml file that corresponds to
the DDR you wish to import. Click Open.
Note If the .xml file being imported contains the formatting flags %n, it will be
replaced by the Mark VIe component Design Memo (DM) number. This is a GE
Power Systems project number and can be edited by selecting the General tab
and Requisition Info.
To export a DDR to a .xml file
1 From the list of DDRs, select the DDR to be exported.

2 From the File menu, select Export, and Selected Item. Or, right-click a
DDR in the list and select Export Configuration from the shortcut menu.
3 Select the desired file and click Save.

Example Setup of DDR
This procedure is a simple example of how to set up a DDR to capture two
variables.
1 Add a Program to the Software tab.

2 Add a variable DDREnable (Boolean), which will be used to enable the
DDR
3 Add a variable DDRTrigger (Real), which will be used to trigger the
DDR.
4 Add two variables TriangleOut and SineOut, which will be connected to
the output of the function blocks. These will be the variables that will be
added to the DDR variable collection.
5 Create a User Block in the program, and add two FuncGen blocks. These
are in the Data Collection section. Set up the pins on the two blocks as
shown below. FuncGen1 will be set up as a Sine wave generator and
FuncGen2 will be set up as a Triangle wave generator.
6 Set up the DDR as shown below.

Add the two variables SineOut and TriangleOut to the DDR. Set the Frame
Period Multiplier to 3, which means a sample will be collected every 120 ms.
The base Frame period is typically 40 ms. Set the PreTrigger samples to 20
and the Post Trigger samples to 100, so the entire capture will take 14.4
seconds.
The DDR will be enabled with the DDREnable variable and the Trigger will
use the DDRTrigger variable. The DDR will be triggered when the
DDREnable is True and the DDRTrigger is greater than or equal to 5.
7 Build and download the application code.

8 Go Online to the controller. Select the Variables node of Prog1.
Double-click the green live data for the DDREnable variable. Set to True
and send to the controller.

9 The status of the DDR can be checked on the EGD page. When the
DDREnable is True and the DDR is not triggered it will be in the
Waiting state, as shown below.
10 Now set the value of the DDRTrigger variable equal to or greater than 5
and send to the controller.
11 When the capture is complete, the status will indicate Complete and the
DDR can be uploaded.

12 The Trender is used to upload the capture buffer. From the View menu,
select Trenders to add a new trend. The Trender window displays.
13 Select + and the Trender wizard displays. Select Capture Buffer to select
the DDR to upload. The uploaded DDR variables are shown below.

Notes

CHAPTER 13
Chapter 13 Ethernet Global Data
The Ethernet Global Data (EGD) protocol allows you to share information
globally between controller components (sometimes known as nodes) in a
networked environment. EGD allows one controller component, referred to as
the producer of the data, to simultaneously send information to any number of
peer controller components (consumers) at a fixed periodic rate. This network
supports a large number of controller components capable of both producing and
consuming information.
EGD Configuration
To configure EGD for a controller
1 From the System Editor, double-click on a Mark VIe component to

display the Component Editor.
3 In the Tree View, select Ethernet Global Data. The Ethernet Global
Data properties display in the Property Editor.
The following properties display in the Property Editor when Ethernet Global
Data is selected in the Tree View:
Collection This property controls the Collection to which this EGD

component belongs when viewed in the EGD management tool (EMT). This
information is published to the EGD Configuration server in the GUI component
document, GUIDevice.xml.
Producer ID Sets and displays the EGD Producer ID for this component.
This is assigned when the component is created. The Property Editor displays
the EGD Producer ID formatted as an unsigned integer, but dotted and
hexadecimal representations are available by clicking the ellipsis button.
GEH-6700 ToolboxST Chapter 13 Ethernet Global Data 13-1

Produced Pages
Produced Pages are data samples configured to be available to other components
on the network.
To add a new Produced Page
1 From the Tree right-click the Produced Pages item, and then select
Add Page.
2 Enter a unique name for the new page in the Page Name dialog box and
select OK.
Note When the first Produced Page is created, it automatically becomes the
Default page. When a new Mark Vie is created, the Produced Page Default is
automatically created
To select the default Produced Page for the standard signals
1 From the EGD tab, select Produced Pages in the Tree View.
2 Select the Default Page Property from the Property Editor, and then
select the desired page from the drop-down list.
Tip Any variable defined with $Default as the EGD page name will
automatically be placed on the currently selected Default page.
To delete a page
From the Tree View, right-click the page you wish to delete and select
Delete page.
13-2 Chapter 13 Ethernet Global Data GEH-6700 ToolboxST

Editing Produced Pages
To configure a Produced Page
From the EGD tab Tree View, expand Ethernet Global Data.
Under Produced
Pages, select the
desired page.
The page properties

display in the Property
Editor.
The following properties are available for configuration when a Produced Page
is selected in the Tree View:
Ethernet 0 If selected, EGD will be broadcast on Ethernet Adapter 0. (If more
than one Ethernet Adapter has been configured for EGD, additional Ethernet
properties are displayed.)
Mode - When this property is set to Broadcast, the page is sent to all EGD
nodes. When set to Unicast, the page is only sent to a single destination.
Destination IP Address When Mode is set to Unicast, this property controls
the IP address that receives the exchanges.
Exchanges This property indicates the number of exchanges in the selected
page. It is updated after a build.
Default Page This read-only property is set to True if the selected page is the
Default Page. To change the default page, refer to the section, Produced Pages.

Layout Mode If this property is set to Auto, exchange numbers and offsets
are automatically assigned at build time. If it is set to Manual, exchange numbers
and offsets can be entered manually.
Minimum Length Sets the minimum length of the exchanges on this page.
Some components look only at the length of the exchange. This property can be
set to a value larger than the current size of the exchange so that as variables are
added, the component continues to receive the exchange.
Name Use this property to rename the selected page.
Period This read-only property indicates the transmission period of the page in
milliseconds.
Period Multiplier This value is multiplied by the Controller frame period to
obtain the EGD page period. (The results display in the Period property.)
Skew Skew is used to prevent exchanges with the same period from being
produced at exactly the same instant. The skew for the first exchange in the page
is set to this value, and each additional exchange skew differs from the previous
exchanges skew by exactly this value. For example, if you have three exchanges
in a page and a skew value of 2, the first exchanges skew is two, the second
exchanges skew is four and the third exchanges skew is six. (The skew property
is measured in nanoseconds.)
Starting Exchange ID This Exchange ID is used for the first exchange on
this page. Each additional exchange will be incremented from this number. When
this property is changed, all exchanges are renumbered.
Page Compression
When a page compress operation is performed, the variable locations are
optimized. The variables are located in increasing size order, starting with
Booleans, then Words, Double Words, and finally all other variables.
To compress a single page
From the Tree View, right-click the page to compress, and then select
Compress.
To compress all Produced Pages in a component
From the Tree View, right-click Produced Pages, and then select
Compress All.

Variables
To add a variable to an EGD page

2 From the Tree View, right-click the desired page, and then select Add
Variable to display the Variable Browser.
In the Variable
Browser, select one
or more variables to
add to the page,
then click OK.
The Summary View updates to display

the new variables. The Exchange IDs and
Locations are assigned during the build.
Tip If the variable to be added to the EGD page is already in use on the
Software tab, you can add the variable without using the EGD tab. To add a
variable from the Software tab, select the desired variable(s) in the Summary
View, and then set the EGD Page property using either the Summary View or
the Property Editor.

To delete a variable from an EGD Page
From the Summary View, right-click the variable to delete, and then select
Delete Selected Row(s).
To copy variable information from an EGD Page to the Clipboard
From the Summary View, right-click a variable, and then select Copy
Selected/Current Row(s). The data is copied in Comma Separated Value
(CSV) format.

Referenced Devices
The EGD variables defined in other components can be added to the current
components variable list by adding a reference. References can only be created
to EGD-capable devices that are producers of pages.
To select the devices that are referenced
From the Tree View, right-click the Referenced Devices item, and then
select Select Devices to display the Select Devices dialog box.
Select or clear the

check boxes next to
each component
name. Click OK.
The EGD configuration for the selected devices are loaded and the variables
Grayed Exchanges
are not available to
this component.

When EGD configurations are edited in remote devices, you must refresh the
configuration to ensure that the latest variable information is used.
To refresh the configuration of a referenced device
In the Tree View, right-click the device to be refreshed, and select

Refresh.

CHAPTER 14
Chapter 14 Modbus Slave
The Modbus Slave feature on the Mark VIe controller allows a Modbus
Master to read and/or write data directly from the Mark VIe using the Modbus
protocol over Ethernet.
Configure Modbus Slave

To configure Modbus Slave for a controller
From a Mark VIe Component Editor, click the Modbus Slave tab.
Select the Modbus

Slave option in the Tree
View. Configuration
properties display in the
Property Editor.
GEH-6700 ToolboxST Chapter 14 Modbus Slave 14-1

When Modbus Slave is selected in the Tree View, the following options display
in the Property Editor:
Interface sets the Modbus Slave Interface type. Only Ethernet is currently
supported, but other interfaces like Serial may be supported in future releases.
Command Limit limits the number of commands processed per second. The
command limit is based on commands that have changed, not commands that are
identical to previously received commands.
Data Swapped changes the transmission order of each 16 bit word when set to
True. For example, if Data Swapped is set to true, 0x01234567 would be
transmitted as 0x45 0x67 0x01 0x23 and 0x0123456789ABCDEF
would be transmitted as 0xCD 0xEF 0x89 0xAB 0x45 0x67 0x01
0x23.
Serial Settings are provided for future use if Serial support is added to
ToolboxST. They are disabled in versions that only support Ethernet interfaces.
Modbus Slave Register Pages
The Modbus Slave tab contains four pages that are used to exchange data with a
Modbus Master.The pages differ by the access the master receives to the data
(read-only or read/write) and the type of data (a Boolean or a 16-bit word) as
follows:
Page Data Type Access
Holding Register 16-bit Register Read/Write
Coil Single Bit Read/Write
Input Register 16-bit Register Read-only
Input Single Bit Read-only
14-2 Chapter 14 Modbus Slave GEH-6700 ToolboxST

ToolboxST allows you to specify the points (variables) on each page using a
Data Grid. (For more information, refer to the section, Data Grids.) When you
add a point to a page, both Modbus Slave and the selected page are enabled on
the controller. As you add and remove points, the controller is updated so that
only pages containing points are enabled. To completely disable Modbus Slave,
remove all points on all pages.
The following columns are available when adding a point:
Connected Variable is the variable that is read or written from the Mark VIe or
the referenced device. A variable must be on an EGD page before it can be
added to a Modbus Slave page. You must specify a Connected Variable before
the other columns become active for a point.
Direction determines the type of access to the Connected Variable associated

with a point. If this property is set to Read, the Modbus Master can read the
point, and if set to Write, the Modbus Master can write to the point.
Point Data Type determines the data type of the point and the registers used to
transmit the point data over a Modbus connection as follows:
BOOL is one bit of a 16 bit word. (This is the only option if the Connected
Variable is a BOOL.)
INT is a signed 16 bit word and takes one register
UINT is an unsigned 16 bit word and takes one register.
DINT is a signed 32 bit word and takes two registers.
UDINT is an unsigned 32 bit word and takes two registers.
REAL is a signed 32 bit float and takes two registers.
LREAL is a signed 64 bit float and takes four registers.
Point Address specifies the address of the register. When a point is created, the
Point Address is automatically set to a value adjacent to the highest point
address previously on the page, but the automatic value can be modified. Any
data types that are 32 bits or more (DINT, UDINT, REAL, and LREAL) should
be placed on odd register addresses. Valid ranges for Point Address are 1 to
65534. When specifying a Point Address for a BOOL variable, the bit 0-15
within the 16 bit word is represented by a decimal; for example, 1.00 selects
register address 1 and bit 0, and 10423.7 selects register address 10423 and bit 7.
Raw Min, Raw Max, Eng Min, and Eng Max are columns that convert
Modbus Slave point raw data into engineering units. The Raw Min and Raw
Max columns control the minimum and maximum for the raw data and the Eng
Min and Eng Max columns control the minimum and maximum Engineering
units that the raw data will be scaled to. (The BOOL data type cannot be
scaled.)
Point Name is a read-only identifier that is automatically generated from the

register page name, the point address and, if necessary, an added unique number.
GEH-6700 ToolboxST Chapter 14 Modbus Slave 14-3

Notes
14-4 Chapter 14 Modbus Slave GEH-6700 ToolboxST

CHAPTER 15
Chapter 15 Mark VIe Tools
Reports
Reports provide a variety of controller information in a viewable format.
Reports are displayed in a separate window and can be viewed, printed, and
saved for later use. When viewing a report on screen, you can also sort, filter,
and search the report to quickly locate information.
Report Types
Global Variable Report

The Global Variable report provides a list of all global variables in the
controller. For every variable, the report lists the variable name, description, data
type, alarm/hold/event status, initial value, and units.
Block Pin Report

The Block Pin report provides a list of all block pins in the controller software.
For every variable, the report lists the block pin name, block description, block
execution number, connected variable name, data type of the block pin, the
program in which block resides, pin description, user (macro) block name, block
name, Program execution number, and the pin usage description.
Note For linked user blocks, internal block pins are not listed.
I/O Report
The I/O report provides a list of all hardware inputs and outputs points for the
controller. For every I/O point, the following columns are available for inclusion
in the report:
Entry Counts the number of items in the report. Sort by this column to
place the data in its original order.
Name Name of the point.
Description Describe the I/O point.
Device Tag ID of device attached to the screw.
Screw Name Name of the screw on the terminal board.
Screw Number Number of the screw on the terminal board.
Cable Number ID of the cable attached to the screw.
Wire Number ID of the wire attached to the screw.
Interposing TB ID of the terminal board junction, if any, between the Mark VIe
and the actual I/O.
Wire Jumpers External wire jumper.
Screw Note Additional information about the screw on the terminal board.
GEH-6700 ToolboxST Chapter 15 Mark VIe Tools 15-1

Jumpers List of jumpers on the module.
Jumper Value The position to which to set the module jumpers.
Sense Used for relay and solenoid circuits only. Sense of relay
connected.
TB Name Name of the terminal board.
TB Hardware Module terminal board hardware form.
Form
Panel Name Panel name where the module resides.
Panel Location Panel location of the module.
Module Name Name of the module.
Bar Code Terminal board barcode.
Variable Name Name of the variable attached to the point.
Type Data type of I/O point.
Display High This is the default upper limit for displays on HMI.
Display Low This is the default lower limit for displays on HMI.
Entry High This is the default upper limit for set-point entry on HMI.
Entry Low This is the default lower limit for set-point entry on HMI.
Units Engineering units.
Used In Code Whether the point is used by the CSP.
Alarm Report
The Alarm report creates a spreadsheet displaying all the variables marked as
alarms. For every variable, the report lists the variable name, description, alarm
ID, alarm class, display screen, and a status if it alarms on a zero condition.
Variables are marked as alarms in the variable Property Editor.
Hold Report
The Hold report creates a spreadsheet displaying all the variables marked as
hold variables. This report lists the variable name, description, and the hold ID
for each variable. Variables are marked as holds in the variable Property Editor.
Event Report
The Event report creates a spreadsheet displaying all the variables marked as
events. This report lists the variable name, description, and the event ID for each
variable. Variables are marked as events in the variable Property Editor.
NovRam Report
The NovRam report creates a spreadsheet displaying all the variables marked as
non-volatile. This report lists the variable name and description for each
variable. Variables are marked as NovRam in the variable Property Editor.
15-2 Chapter 15 Mark VIe Tools GEH-6700 ToolboxST

Creating Reports
To create a report
1 Open a Mark VIe Component Editor. From the View menu, select
Reports, and then select the desired report type from the submenu. (For
more information about the available reports, refer to the section, Report
Types.)
2 From the Select Report Columns dialog box, select and arrange the
columns you want to include in your report. When you are finished, click
OK.

Move the selected

report column up or
down in the column
order.

report. the report.
3 The I/O Report will open in a new window.

Saving, Retrieving and Printing Reports
To save a report
From the File menu, select Save Report. In the Save Report dialog box,
enter a file name and click Save.
To open a saved report
From the File menu, select Open Report. In the Open Report dialog
box, locate the report in .csv format and click Open.
To print a report
From the File menu, select Print. In the Print dialog box, verify the
settings are correct, and then click OK.
Viewing Reports
To change the zoom level of a report
From the Report View menu, select Zoom, and then select the desired
zoom value from the submenu.
To sort a column
From the Report window, click any column heading to apply a sort to the
associated column. The first click will sort the column ascending; a second
click will switch the column to a descending sort.
A triangle in a column
header indicates that the
rows are sorted based on
the data in that column.

To change report columns
From the Report menu, select Change Columns to display the Select
Report Columns dialog box.

Move the selected

report column up or
down in the column
order.

report. the report.

Filtering Rows
The report filter feature applies rules to a report to display a specific subset of
the original report.
To apply a report filter
From the Report window, select the Report menu, and then select Apply
Filter to open the Edit Report Filter dialog box.
Lists available Lists available

columns. (Double-click comparison and
a column to add it to Boolean operators.
the equation) (Double-click an
operator to add it to
the equation)
Click to add
parentheses to your
equation.
Enter the filter

equation to be
used in this box.
Click to accept the

filter equation as
shown.
Clears the current Cancels without changing

filter equation. the current filtering settings.
The following operators are available for use in a report:

< Left expression must be less than the right expression.
> Left expression must be greater than the right expression.
<= Left expression must be less than or equal to the right expression.
>= Left expression must be greater than or equal to the right expression.
<> Left expression must not equal the right expression.
= Left expression must be exactly equal to the right expression.
LIKE Expression to the left of the operator must match the wildcard
expression to the right of the operator.
AND Expressions to the left and right of the AND operator must both be true.
OR Either the expression to the left or to the right of the operator must be
true.
NOT Expression to the right of the operator must be false.

In addition, filter equations must obey the following rules:
When using the LIKE operator, you must include a wildcard * at the
beginning and/or end of the right-hand value. For example, [Day Name]
LIKE T* would select Tuesday and Thursday.
You can use as many groups of parentheses as necessary to define an
expression.
Any string values must be enclosed in single quotes: 'string'
To remove a report filter
From the Report window, select the Report menu, select Remove Filter.
The filter will be removed and all available rows will be displayed.
To save a filtered report
From the Report window, select the File menu, select Save Filtered
Report.

Finding Data
The report find feature allows text searches to be performed within the report.
To find text within the report
From the Report window, select the Report menu, and then select Find to
display the Find dialog box.
Enter the text to search Click to locate and highlight the

for in the report. next occurrence of the search text
in the report.
If checked, the
capitalization in the
report and the
search string must
exactly match.
If checked, the find string Determines the direction

must be found as a whole in which the next search
(for example, day would not will proceed.
match Monday)
Importing an I/O Report from a CSV file

The Mark VIe component supports automated importing of data from a
previously generated I/O report.
To avoid potential loss of data, save the Mark VIe

component before attempting any import operation.

To import an I/O Report
1 From the Hardware tab Tree View, select I/O Hardware.

2 From the File menu, select Import and then select I/O Report to display
the Open Report dialog box.
3 In the Open Report dialog box, select a report and then click Open. The
data will be imported. If a part of the data cannot be imported, it will be
highlighted when the imported report is displayed.

Forced Variables
Forced variables are variables whose value is permanently overridden with a
specific value. They are managed using the Forced Variables window while
connected to a controller.
To open the Forced Variables window
Forced Variables to display the Forced Variables window.
To force a value or change a previously forced value
From the Forced Variables window, double-click a value to display the

Send Value dialog box. (For more information about the Send Value
dialog box, refer to the section, Modifying Live Values.)
To remove a single forced value
Right-click a forced variable and select Remove Selected Forces.
To remove all forced values
Right-click anywhere inside the Forced Variables window and select

Remove All Forces.

Global Variables
The Global Variables window displays all controller variables that have been
configured as Global in one central location.
To display the Global Variables window
Global Variables.
Click to toggle between displaying

The Property Editor displays
only modifiable global variables
properties for the currently
and displaying all global variables.
selected row in the data grid.
The Global Variables window is particularly useful when you want to modify a
property for multiple variables. For example, to move multiple variables onto an
EGD page, select the rows for the desired variables and then change the EGD
Page property in the Property Editor. For additional information, refer to the
section, Data Grids.
The Global Variables window has some restrictions on the operations that are
available. Only existing global variables can be changed, so you can not add
new variables from the Global Variables window. You cannot make any change
that affects the name of the global variable (like Name or Global Name Prefix).
Finally, variables from an instanced library user block can only be modified if
the Merge Variables at Instance property of the Programs item on the Software
tab is set to True.

Watch Windows
The easiest way to view and organize live variables in a controller is through
Watch Windows. Watch Windows are created and saved in a component.
Then, they can be exported to XML and CSV files.
To open the Watch Windows dialog box
Watch Windows.
The Watch Windows dialog box displays a list of the windows that have been
configured for the component.
Click to access the

Double-click a
selected Watch Window.
name in the list to
open an existing Click to create a new
Watch Window. Watch Window.
Click to remove a Watch
Window from the list.
Click to save the window to an
XML or CSV file so the collection
of variables can be used by
other components.
Note If this is the first time the Watch Windows dialog has been used for the
selected component, the list will be empty and a new Watch Window will need
to be created or imported.

Managing Variables
Once a Watch Window is created, variables can be managed with the following
commands.
Right-click anywhere inside the variable

list to display the shortcut menu.
Insert Variable allows you to insert new

variables from the Variable Browser.
Remove Variable deletes the selected

variable.
Go to Definition navigates the Component
Editor to the location where the variable is
defined, such as a Program Variable grid.
Change Live Value displays the Change Live

Copy Watch as Text copies the contents of a Watch Value dialog box for the selected variable.
Window (including live variables) to the clipboard as
text. This data is in Comma Separated Value (CSV)
format so it can be pasted into spreadsheets, text
editors, and mail clients.
Variables can be moved to other windows and editors using the drag-and-drop
feature. For example, you can drag
A block pin from the Block Diagram Editor, and drop it into a Watch
Window.
A variable in the Watch Window to a block pin on the Block Diagram
Editor, forming a connection.
A variable from one Watch Window to another Watch Window, copying
the selected variable into the target window.
Importing and Exporting

Once a Watch Window has been created, it may at times be convenient to save it
to an XML file. The resulting XML file can be imported into other components
to reuse a previously selected collection of variables and can also be exchanged
with other ToolboxST users.
To export a Watch Window to an XML file
1 In the Watch Windows dialog, select the desired Watch Window and
then click the Export button.
2 The Export Watch Windows dialog displays. Select the desired
destination and click Save.

Control Constants
Control constants are special read-only variables that are important to key
control algorithms. Control constants must always have a Global scope.
To convert a variable to a control constant
1 From the Software tab, locate and select the variable to convert to a
control constant.
2 From the Property Editor, locate the Scope property and verify it is set
to Global.
3 From the Property Editor, change the value of the Control Constant
property to True.
4 From the Property Editor, assign an Initial Value and edit to Property
Editor. (Optional)
Control Constants Window

All control constants in a controller are displayed in the Control Constants
window, where the constants can be reviewed and the Initial Values can be
modified.
To display the Control Constants window
Control Constants.
Enter a new value into the Initial Value Click to display the
box. Initial Value is the only column that Modify Value dialog box.
can be modified from the Control
Constants window.

Importing and Exporting Control Constants
The control constants for a controller can be exported to a comma separated
value (.csv) file for external viewing and changes. Previously exported control
constant files can be imported back into the controller, but if any fields other
than the Value field have been modified, the control constants will not be
updated. A sample .csv file is provided below to illustrate the output format:
NAME,VALUE,TYPE,UNITS,DESCRIPTION,FORMAT SPECFICATION
ControlConstant3,6.234,REAL,,,
ControlConstant2,55,DINT,,,
ControlConstant6[0],true,BOOL,,,
ControlConstant6[1],false,BOOL,,,
ControlConstant6[3],false,BOOL,,,
ControlConstant4,8769.876,LREAL,,,
ControlConstant5[0],20.1,REAL,,,
ControlConstant1,1,BOOL,,,
To export control constants to a .csv file
Open the Control Constants window. From the File menu, select
Export to CSV. In the dialog box that displays, select a location for the
exported data and click Save.
To import control constants from a .csv file
Open the Control Constants window. From the File menu, select Import
from CSV. In the dialog box that displays, select a location for the
imported data and click Save.

Notes

CHAPTER 16
Chapter 16 Reference
Menus
File Menu
Save saves changes to the current component.
Print creates a paper copy of the entire component configuration.
Upgrade changes the version of the component support software.
Import I/O Report imports an I/O report from a CSV file.

Close ends the component editing session and returns to the main
System Editor.
Edit Menu
Undo returns the component to the state it was in before the last
action was performed.
Redo performs an action again after an undo command.
Cut moves the currently selected item to the clipboard.
Copy places the currently selected item on the clipboard.
Paste places the contents of the clipboard into the currently selected
item.
Delete removes the currently selected item.
Find opens the Finder tool.
Select All selects all available items.
Insert opens the Insert Block dialog box while in the Block Diagram
Editor.
GEH-6700 ToolboxST Chapter 16 Reference 16-1

View Menu
Go Back returns to the view that immediately preceded the current
Go Forward returns to the view that immediately follows the current
Forced Variables opens the Forced Variables dialog box.
Global Variables opens the Global Variables dialog box.

Trenders displays a list of Trender windows associated with the
component.
Watch Windows displays a list of Watch Windows associated with
the component.
Reports
Global Variable creates a report of all global variables in the

controller.
Block Pin creates a report of all block pins in the controller
software.
I/O creates a report of all hardware input and output points.
Alarm creates a report of all variables marked as alarms.
Hold creates a report of all variables marked as hold variables.
Event creates a report of all variables marked as events.
NovRAM creates a report of all variables marked as non-

volatile.
Control Constants opens the Control Constants dialog box.
Controller Diagnostics opens the Controller Diagnostics dialog

box.
Launch EMT opens the EGD Management Tool.
16-2 Chapter 16 Reference GEH-6700 ToolboxST

Device Menu
Online connects to or disconnects from a controller.
Build converts the current configuration into binary files that can be
downloaded to a controller.
Download
Controller Initial Setup opens a wizard that performs basic
configuration tasks on the controller.
Controller Flash Boot Loader installs the controller
bootloader onto a CompactFlash card connected to your
computer.
Download Wizard downloads base load, firmware and
application code to the controller and Distributed I/O modules.
Update Dynamic Data Recorder exchanges updated
information with the DDRs in the controller.
View/Set Time displays a dialog box that controls the controller
time.
Upload retrieves configuration information from the controller and
uses it to create a new controller component in the system.
Put Device to SDB stores the component configuration to a System
Database (SDB).
Pack Variables rearranges variables to minimize the amount of
space used.
Administer Totalizers opens the View/Set Totalizers dialog box.
Options Menu
Settings displays a dialog box with controller settings.
Help Menu
Release Notes
ToolboxST displays up-to-date information about your version of

ToolboxST.
Mark VIe displays up-to-date information about your version of
the Mark VIe support software.
About displays version and copyright information.
GEH-6700 ToolboxST Chapter 16 Reference 16-3

Notes
16-4 Chapter 16 Reference GEH-6700 ToolboxST

Glossary of Terms
application code
Software that controls specific machines or processes.
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.
baud
A unit of data transmission. Baud rate is the number of bits per second
transmitted.
BIOS
Basic input/output system. Performs the boot-up, which includes hardware self-
tests and the file system loader. The BIOS is stored in EEPROM and is not
loaded from the ToolboxST.
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
ToolboxST 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
ToolboxST, it is a data type for logical signals.
bumpless
No disrupt to the control when downloading.
GEH-6700 ToolboxST Glossary of Terms G-1

bus
An electrical path for transmitting and receiving data.
byte
A group of eight binary digits (bits) operated on a single unit.
CMOS
Complementary metal-oxide semiconductor.
collection
A group of signals found on the same network. The Trend Recorder can be
configured by adding collections.
COM port
Serial controller communication ports (two). COM1 is reserved for diagnostic
information and the Serial Loader. COM2 is used for I/O communication.
configure
To select specific options, either by setting the location of hardware jumpers or
loading software parameters into memory.
Control Constant
Control Constant is a signal with an initial value that is read and never written.
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.
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.
fault code
A message from the controller to the HMI indicating a controller warning or
failure.
Finder
A subsystem of the ToolboxST for searching and determining the usage of a
particular item in a configuration.
G-2 Glossary of Terms GEH-6700 ToolboxST

firmware
The set of executable software that is stored in memory chips that hold their
content without electrical power, such as flash memory.
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 variable signal to a particular value, regardless of the value blockware
or I/O is writing to that signal.
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.
Get From Database

The act of retrieving configuration information from some system database.
health
A term that defines whether a variable 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.
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.

initialize
To set values (addresses, counters, registers, and such) to a beginning value prior
to the rest of processing.
instance
Update an item with a new definition.
logical
A statement of a true sense, such as a Boolean.
mGENI controller board

IC660ELB912_. An optional board for the controller that provides an interface
to the Genius I/O bus.
model
Interactive setup data (recipe) that automatically adjusts to the process. This
function is usually used with hot mills or cold mills.
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 ToolboxST 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 ToolboxST, which contain the controller
application configuration code for a device. Pcode is stored in RAM and Flash
memory.
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.
PLC
Programmable Logic Controller. Designed for discrete (logic) control of
machinery. It also computes math (analog) function and performs regulatory
control.
product code (runtime)

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

realtime
Immediate response. It refers to process control and embedded systems, and fast
transaction processing systems that must respond instantly to changing
conditions.
reboot
To restart the controller.
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.
sample set
Set of values taken when signals are being trended together with the Trender.
sampling rate
The period that values are collected to put in a sample set.
simulation
Running a system without all of the configured I/O devices by modeling the
behavior of those devices in software.
skew offset
A property of blocks that allows a user block to run at a different time slice than
other blocks within the same module.
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.

TCP/IP
Communications protocols developed to inter-network dissimilar systems. It is a
defacto 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.
ToolboxST
A Windows-based software package used to configure controllers.
trend
A time-based plot to show the history of values.
Trender
A subsystem of the ToolboxST that monitors and graphs signal values from a
controller.
TrueType
Scaleable font technology that renders printer and screen fonts. Each TrueType
font contains its own algorithms for converting the outline into bitmaps.
Tuning Variable
Tuning Variable is a signal with upper and lower limits, which define the
bounds of the initial value and when making runtime changes.
validate
Makes certain that items or devices do not contain errors and verifies that the
configuration is ready to be built into pcode.
variable
The basic unit for variable information. Variables are the placeholders for
memory locations in the toolboxs different platforms.
word
A unit of information composed of characters, bits, or bytes, that is treated as an
entity and can be stored in one location. Also, a measurement of memory length,
usually 32 bit in length but van also be 4, 8, or 16-bits long.

Index
Contacts 11-58, 11-59

A Control Constant 16-6
Accessing a Trender Window 5-1, 5-4 Control Constants 15-16
Acquiring Data 5-3 Control Constants Window 15-16
Add a User Block 11-30 Controller Diagnostics 8-13
Add Variables 12-4 Controller Initial Setup 8-7
Adding Modules 10-3 Copying and Moving Data 3-6
Adding Rows and Columns 11-60 Create I/O Report 10-11
Adding Traces 5-3 Creating a Program 11-26, 11-29
Additional Toolbar Buttons 11-54 Creating Reports 15-3
Administer Totalizers 8-13 Cursors 5-7, 5-8, 5-11
Alarm Classes 2-13
D
application code 16-5
Application Documentation 11-61 Data Grids 3-5, 14-3
Application Software Examples 11-6, 11-62 Data Toolbar 5-3
ASCII 16-5 dead band 16-6
Attribute Value Editor 9-4 device 16-6
Attributes 9-3 Device Menu 6-11, 16-2
Auto-Range Trace 5-11 Diagnostics Tab 10-11
Diagram Settings 11-55
B Diagram Shortcut Menu 11-45
Baud 16-5 Download Command 8-6
BIOS 16-5 Download Parameters 10-14
bit 16-5 Download to Controller 8-6
block 16-5 Download Wizard 8-8, 10-14
Block Diagram Editor 11-2, 11-25, 11-42 Dynamic Data Recorder (DDR) 12-1
Block Shape Shortcut Menu 11-48
E
board 16-5
Boolean 16-5 Edit Menu 2-11, 6-10, 16-1
bumpless 16-6 Edit Mode 11-44
bus 16-6 Editing Data 3-5
byte 16-6 Editing Produced Pages 6-3, 13-3
EGD Configuration 6-2, 13-1
C EGD Editor for External Devices 6-1
Capture Buffer Trends 5-4 Errors 11-60
CMOS 16-6 Ethernet 16-6
Coils 11-59 Events 5-8
collection 16-6 Example Setup of DDR 12-7
COM port 16-6 Exchanging Trender Data 5-13
Compare Parameters 10-15 Exporting a Table Definition 11-14
Component InfoView 3-3 Exporting to a File 5-13
Components 2-3, 2-11 External Device Configuration 2-6, 2-17
Configuration Files 2-7 External Device EGD Configuration 2-17
configure 16-6
F
Configure Modbus Slave 14-1
Connecting Pins 11-49 Fault code 16-6
Connecting to a Controller 8-2, 8-13, 8-14 File Formats 2-9
GEH-6700 ToolboxST Index I-1

File Menu 2-10, 6-9, 16-1
Filtering Rows 15-7 M
Find Methods 4-2 Managing Blocks 11-3, 11-46
Finder 16-6 Managing Columns 3-6
Finding Data 15-10 Managing Variables 15-15
firmware 16-7 Manual Range Adjustment 5-12
flash 16-7 Measurement Systems 2-16
Folder Structure 2-7 Menu Reference 2-10
font 16-7 Menus 6-9, 16-1
Forced Variables 15-12 Modbus Slave Register Pages 14-2
forcing 16-7 model 16-8
Format Specifications 2-14 Modify Module Configuration 10-8
Function Blocks 11-2 Modifying Live Values 11-51, 15-12
Modifying Totalizer Values 8-17
G
Modules 10-3
Gateway 16-7 Moving and Copying Components 2-5
General Features 9-1
Get From Database 16-7 N
Global Variables 15-13 Network Adapters 6-1, 9-5
Graph View Options 5-9 Network Redundancy 10-2
Grid Lines 5-10 non-volatile 16-8
Grouping Components 2-5
O
H
Obtaining Data 5-6
Health 16-7 online 16-8
Help Menu 2-12, 6-11, 16-3 Online Display and Changes 11-16
Hiding Traces 5-13 Opening and Creating Systems 2-2, 2-10, 2-11
Options Menu 2-11, 16-3
I
Organizing Modules 10-7
I/O 16-7
I/O drivers 16-7 P
I/O mapping 16-7 Page Compression 6-4, 13-4
Implementation Profile 6-8 Parameters Tab 10-10
Import and Export DDR 12-6 PLC 16-8
Import Table CSV File 11-31 Printing Graphs 5-14
Importing a Table Definition 11-12 Produced Pages 6-4, 13-2
Importing an I/O Report from a CSV file 15-10 product code (runtime) 16-9
Importing and Exporting 15-15 Program Variables 11-32
Importing and Exporting Control Constants 15-17 Programs 11-5
initialize 16-8 Programs Item 11-26
Install the UPD 1-7 Property Editor 3-3, 11-14, 11-22, 11-24, 11-32
instance 16-8
Instance 11-34 R
Instance All 11-28
Realtime 16-9
Instance Scripts 11-6
Reboot 16-9
Internal Points Tab 10-10
Referenced Devices 6-7, 13-7
L register page 16-9
relay ladder diagram (RLD) 16-9
Layout Modes 11-45 Replace Options 4-4
Library Container Editor 11-7 Report Types 15-1, 15-3
Library Container Editor/User Block Libraries 11-18 Reporting 10-11
Library Property Editor 11-20 Reports 15-1
Library References 11-26 Resources 16-9
Library Summary View 11-21 Rung Editor 11-56
Live Trends 5-4 Running the Tree File Importer 7-1, 7-2
logical 16-8 runtime 16-9
I-2 Index GEH-6700 ToolboxST

S U
Sample Markers 5-10 Update DDR 12-5
sample set 16-9 Upgrade Module 10-13
sampling rate 16-9 Upload Wizard 8-10
Saving Systems 2-7, 2-11 User Attributes 11-6, 11-35
Saving, Retrieving and Printing Reports 15-4 User Block 11-34
Shape Drawing Tools 11-52 User Block Definitions 11-5, 11-21
simulation 16-9 User Block Libraries 11-6
skew offset 16-9 User Block Properties 11-36
Software Overview 11-1, 11-7 User Block Variables 11-22, 11-35
Software Tab 11-26 User Blocks 11-3
Static File Trends 5-5 Using Table Definitions in Software Application
Statistical Calculations 5-13 Code 11-17
Status Tab 8-3
Status Variables 12-4 V
Summary Tab 10-9 Validate 16-10
Summary View 3-2, 10-9, 11-25, 11-33, 11-37 Value ScreenTips 5-8
System Database (SDB) 2-17, 9-6 variable 16-10
System Editor 2-1 Variable Editors 11-40
System Information Editor 2-11, 2-12 Variables 6-5, 13-4
System Options 2-10, 2-11 View Menu 2-11, 6-10, 16-2
View Mode 11-43
T
Viewing Reports 15-5
Table Definitions 11-11, 11-31
TCP/IP 16-10 W
Text Substitution 11-6 Watch Windows 15-14
Time Axis 5-11 Window Menu 2-12
ToolboxST 16-10 Wires 11-59
Totalizer Passwords 8-14, 8-17 Wiring Block Pins 11-47
Trace Colors 5-12 Working in Trender 5-3
Traces 5-3, 5-11 Working Online 10-14
Trender 16-10 Working With Trender Data 5-9
Trender Concepts 5-7 Working with User Blocks 11-6, 11-23, 11-35
Trender Toolbar 5-3
Trender Window Features 5-2
GEH-6700 ToolboxST Index I-3

Notes
I-4 Index GEH-6700 ToolboxST

g GE Energy General Electric Company
1501 Roanoke Blvd.
GEH-6700
040518
+1 540 387 7000

www.geenergy.com

Toolbox ST

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Toolbox ST

Hochgeladen von

Copyright:

Verfügbare Formate

g GE Energy

GE PROVIDES THE FOLLOWING DOCUMENT AND THE INFORMATION

2004 by General Electric Company, USA.

CIMPLICITY is a registered trademark of GE Fanuc Automation, North America, Inc.

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

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

Indicates a procedure, condition, or statement that should be

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

GEH-6700 ToolboxST Safety Symbol Legend a

Isolation of test equipment from the equipment under test

To minimize hazard of electrical shock or burn, approved

To prevent personal injury or equipment damage caused by

b Safety Symbol Legend GEH-6700 ToolboxST

Reader Comments GE Energy

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

Publication Issue/Revision Date

Detach and fax or mail to the address noted above.

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

Chapter 1 About ToolboxST 1-1

Chapter 2 System Configuration 2-1

Chapter 3 Component Editors 3-1

GEH-6700 ToolboxST Contents i

Chapter 5 Trender 5-1

Chapter 6 EGD Editor for External Devices 6-1

ii Contents GEH-6700 ToolboxST

Chapter 8 Working Online With a Mark VIe 8-1

Chapter 9 General 9-1

Chapter 10 Hardware 10-1

Chapter 11 Software 11-1

GEH-6700 ToolboxST Contents iii

Chapter 12 DDR 12-1

Chapter 13 Ethernet Global Data 13-1

Chapter 14 Modbus Slave 14-1

iv Contents GEH-6700 ToolboxST

Chapter 16 Reference 16-1

Glossary of Terms G-1

GEH-6700 ToolboxST Contents v

vi Contents GEH-6700 ToolboxST

It is recommended that you exit all Windows programs.

For assistance, contact:

(replace + with the international access code)

GEH-6700 ToolboxST Chapter 1 About ToolboxST 1-1

1 Place the ToolboxST installation CD in the CD-ROM drive. The installation

2 The Welcome dialog box displays. Click Next. The License

To select components not

1-2 Chapter 1 About ToolboxST GEH-6700 ToolboxST

Use the scroll bar to

The Add/Remove Programs control panel lists all installed versions of

Note Always install new versions of ToolboxST before uninstalling older

GEH-6700 ToolboxST Chapter 1 About ToolboxST 1-3

Click the old version of

ToolboxST ships with software to support a variety of types of controllable

1-4 Chapter 1 About ToolboxST GEH-6700 ToolboxST

Select the new

GEH-6700 ToolboxST Chapter 1 About ToolboxST 1-5

USB Protection Device (UPD or dongle)

Install the UPD

To install the UPD

1 Install ToolboxST (refer to the section, Installation).

1 Save and close any open applications/systems.

1-6 Chapter 1 About ToolboxST GEH-6700 ToolboxST

Check that you have

GEH-6700 ToolboxST Chapter 1 About ToolboxST 1-7