GEH-6700 ToolboxST User Guide
GEH-6700 ToolboxST User Guide
g
These instructions do not purport to cover all details or variations in equipment, nor to
provide for every possible contingency to be met during installation, operation, and
maintenance. The information is supplied for informational purposes only, and GE makes
no warranty as to the accuracy of the information included herein. Changes,
modifications and/or improvements to equipment and specifications are made
periodically and these changes may or may not be reflected herein. It is understood that
GE may make changes, modifications, or improvements to the equipment referenced
herein or to the document itself at any time. This document is intended for trained
personnel familiar with the GE products referenced herein.
GE may have patents or pending patent applications covering subject matter in this
document. The furnishing of this document does not provide any license whatsoever to
any of these patents.
This document contains proprietary information of General Electric Company, USA and
is furnished to its customer solely to assist that customer in the installation, testing,
operation, and/or maintenance of the equipment described. This document shall not be
reproduced in whole or in part nor shall its contents be disclosed to any third party
without the written approval of GE Energy.
GE provides the following document and the information included therein as is and
without warranty of any kind, expressed or implied, including but not limited to any
implied statutory warranty of merchantability or fitness for particular purpose.
Revised: 090108
Issued: 040120
Fax No.
Your Company’s Name and Address Job Site
Phone No.
GE Requisition No.
E-mail
Your Job Function / How You Use This Publication Publication No.
Address
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 ____________________________________________
____________________________ Place
stamp
____________________________ here.
____________________________
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Index I-1
The ControlST* CD includes the ToolboxST* application and support packages for
the various components. 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 the CD, but any subsequent releases
will be installed to the previously defined location.
• No license key is required to install this product, but to run the ToolboxST
application 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 the ToolboxST application.
Processor ®
1 GHz Pentium IV
Operating System ® ®
Microsoft Windows 2000
Memory 1024 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
Note If the installation does not start automatically, use Windows Explorer to
navigate to your CD-ROM drive and run setup.exe. The Alarm Viewer is part of the
GE WorkstationST option.
2 Select the installation options to install, then click the Install button.
3 The Welcome dialog box displays. Click Next. The License Agreement
dialog box displays.
4 To continue the installation, you must accept this agreement. Select Agree.
5 Click Next. The User Information dialog box displays.
6 Click Next. The Destination Folder dialog box displays. If this is the first
time the ToolboxST application has been installed on this computer, the browse
button allows you to change the default install location (C:\Program
Files\GE Energy\). If this is a subsequent installation, this dialog box
displays where this version of the product will be installed.
7 Click Next. The Select Features dialog box displays and allows you to select
which features to install or not install. All components are installed by default.
To select component
not to be installed,
click the icon next to
the component name,
then select the red X.
8 Once your selections are made, click the Next button until the installation starts.
Click the Finish button when the installation has completed successfully.
- /EGDAction:MODIFY /EGDDevice:
• Go To Variable
• Go To Hardware Diagnostic
• Go To Locator
• -NoSplash
• Archive a ToolboxST System
Note If the ToolboxST application is already opened, starting it again with the
/variable option sends a message to the already running ToolboxST application to
cause it to navigate to the appropriate location.
EMT
The EMT opens a ToolboxST application and navigates to the EGD configuration
tab of a component. It can also add a device with a specified producer ID.
Note If EMT command line arguments are used, the /Variable, /VariableDevice,
/Hardware Diagnostic, and /Navigate to Locator arguments are ignored.
To provide consistency, a common set of command arguments are defined for each
application. The standard format is
/<keyword>:<value>
where
<keyword> defines the operation or action (the <, > are not used).
<value> defines the value to be used in the operation or action (the <, > are not
used).
Go To Variable
If the first command line argument is a valid path to a .tcw file, that system file is
used for the variable search. Otherwise, the first file in the most recently started
ToolboxST application is opened.
Note If the EMT command line arguments are used, the /Variable and
/VariableDevice arguments are ignored.
If the first command line argument is a valid path to a .tcw file, that system file is
used for the variable search. Otherwise, the first file in the most recently started
ToolboxST application is opened.
<deviceName>.<variableName>
The search for the variable uses the deviceName component of the system. The
/VariableDevice keyword can also be used to specify a particular device to search.
This is useful for third-party interfaces where you may want to control the device
that is searched (see the third example below). A message displays if nothing is
found in the component.
Examples
Go To Hardware Diagnostic
If the first command line argument is a valid path to a .tcw file, that system file is
used for the variable search. Otherwise, the first file in the most recently started
ToolboxST system is opened.
Examples
/HardwareDiagnostic:Marky
This causes the last opened system to be opened, the Marky controller to be opened,
and the Device Diagnostic window to display (View/Diagnostics/Controller
Diagnostics item).
/HardwareDiagnostic:Marky.23GROUP
This causes the last opened system to be opened, the Marky controller to be opened,
and the Hardware tab 23GROUP hardware group to be selected.
Go To Locator
This argument opens any locator string displayed in the Find Results tab.
To open a ToolboxST component and navigate to a desired point, use the Finder to
search for a string in a component. Then, from the Find Results tab, select one of the
locator text strings, as shown in the window below.
-NoSplash
If the text –NoSplash is contained in an argument, the splash screen does not display
when the ToolboxST application starts.
This argument opens the most recent ToolboxST system, creates a system archive,
then exits the system. Archiving the most recent ToolboxST system can be
overridden by using the first argument to specify the path to the desired system.
The target file name is optional. If not specified, the file name is the ToolboxST
system name plus the creation date and time. If the target file name is a directory, the
archive file is placed in that directory with the file name of the ToolboxST system
name plus the creation date and time.
Examples
ToolboxST /Archive
The most recent system is opened. An archive.zip file, with the opened system name
and date/time, is created. The archive is placed in the parent folder for the
ToolboxST system. If the parent folder cannot be opened, the archive is placed in the
ToolboxST system’s working folder.
The system c:\MySystem.tcw is opened. An archive.zip file, with the opened system
name and date/time, is created. The archive is placed in the parent folder for the
ToolboxST system. If the parent folder cannot be opened, the archive is placed in the
ToolboxST system’s working folder.
The system c:\MySystem.tcw is opened. An archive.zip file, with the opened system
name and date/time, is created. The archive is placed in the specified folder.
Licensing
To use the GE ControlST 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.
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. The ToolboxST application will only function if
your UPD contains a valid ToolboxST application key.
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 the ToolboxST application, the device
may appear to be installed, but it is not associated with the correct drivers.You can
correct this after the application is installed.
When you start the ToolboxST application, the first window that displays is an
empty System Editor.
Before you can begin using the ToolboxST application, 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. Refer to the section, Configuration Files.
1 From the File menu, select New System to display the New System dialog
box.
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, the
ToolboxST application creates it for you.)
3 Enter a name for the system. Some characters are prohibited; if you enter an
invalid character, a small red exclamation mark displays.
4 Click OK to create the new system. The new system is created, and opens in the
System Editor.
When a system is open, the System Editor displays overview information about all
configured components in the system. The window consists of three major areas as
displayed.
The Property
Editor allows
you to edit the
selected
component.
ToolboxST component icons that display in the Tree View are as follows:
Icon Components
System
Group of Components
Mark VI component
EX2100ST component
WorkstationST
Printer
Library Container
Network
Trender
Watch Windows
LiveView
Network Switch
Grouping Components
The ToolboxST application 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
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:
Tip You can import components and Library Containers from either another copy
of the ToolboxST application 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.)
NTP Diagnostics – No
EGD Diagnostics – No
I/O Diagnostics – No
Number of Forced Variables – 0
DDR Equality – Equal
Configuration Equality - Equal
Unhealthy NTP Diagnostics – No
EGD Diagnostics – No
I/O Diagnostics – No
Number of Forced Variables – 0
DDR Equality – Equal
Configuration Equality – major
difference
If the configuration for the external device is stored in a file with a special extension,
you can specify the path to the configuration file and omit the path to the external
application. The ToolboxST application automatically opens the application
associated with the configuration file. In all other cases, you must specify the exact
application to be run for the external device.
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.
• 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 (provided for 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.
• If the external component does not have a configuration file that is associated
with a particular application, select the App Path item. Click the ellipsis button
to display the Open dialog box.
Saving Systems
When you make changes to a system, the changes are stored in memory. Save your
work to prevent your changes being lost.
In the ToolboxST application, 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.
From the File menu, select Save System. (Or, click the button on the
toolbar.)
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:
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 the ToolboxST application is stored in eXtensible Markup
Language (.xml) format.
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.
Build, when set to True, prompts for confirmation before each build.
Developer Mode, when set to True, allows the developer access to the application
on the GE Salem Intranet.
Force Enable UPD, when set to True, makes the UPD a requirement when on the
GE Salem Intranet with privileges.
Auto Backup, when set to True, creates backup copies of configuration files during
the Save command.
Load Last System, when set to True, automatically loads the previously loaded
system when the application starts.
Maximum Build Errors is the maximum number of errors to occur before exiting
a Build. For unlimited errors, set to zero.
Edit Delete Remove the item currently selected in the Tree View
Insert New Add a new component to the current system
Insert Existing Add an existing component from a folder
Cut Cut the selected item in the Tree View
Copy Copy the selected item in the Tree View
Paste Paste the copied item in the Tree View into the Summary View
System Display the System Information Editor (refer to the section System Information Editor)
Information
Selected Display the Component Editor for the item currently selected in the Tree View
component
View By Type Automatically organize the Tree View by component type
By Group Organize the Tree View by components
Track Synchronize Tree View selections with Summary View selections
Memory Usage Display the currently allocated memory
EGD Diagnostics Access the following EGD diagnostic tools:
EGD Management Tool opens the EGD Management Tool (EMT)
View Online Statistics displays EGD exchange status from the selected component.
Only EGD Class 2 or higher components that respond to EGD Command Message
Protocol (CMP) have this diagnostic window.
WorkstationST Capture Live UDP Packets provides an EGD window only enabled
in a WorkstationST component with an OPC DA server configured. This allows the
WorkstationST runtime to capture up to 10,000 EGD UDP messages, then upload
them for display, printing, and exporting to .csv format.
EGD Network Load Calculation provides network load calculation to determine
memory usage.
EGD Perform one of the following:
Configuration View Differences opens a configuration view window.
Server Work Offline allows you to work offline.
Network Status Display defined networks in the system
Viewer
System Online Work online
Options Settings Configure system settings (refer to the section System Options)
From the System Editor, double-click the System item in the Tree
View.
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.
The following properties are available in the Property Editor when an Alarm Class is
selected:
Name displays the name of the Alarm Class. Limited to five characters if using an
SDB.
Description displays the Alarm Classes description. Only the first 50 characters are
stored in an SDB.
Alarm Foreground Color displays the foreground color for an alarm in the Alarm
state.
Alarm Background Color displays the background color for an alarm in the
Alarm state.
Blink Background Color displays the background color for the blink state of the
active unacknowledged alarm.
Blink Foreground Color displays the foreground color for the blink state of the
active unacknowledged alarm.
Normal Foreground Color displays the foreground color for an alarm in the
Normal state.
Normal Background Color displays the background color for an alarm in the
Normal state.
Sound Reference is the sound definition to select when an active alarm displays
in the WorkstationST Alarm Viewer.
To edit sounds
From the System Editor, select the Edit menu, then select System
Information.
The following properties are available in the Property Editor when a sound is
selected in the Data Grid.
Delay displays the time lapse between sounds (from 100 to 10,000 ms). The Repeat
Quantity property must be 1 or more.
Sound Type displays the type of sound annunciated. The options are Tone, Wave
File, and Text to Speech.
Wave File, if selected as the Sound Type, displays the name of the Wave File.
When the system information is saved, the wave files are published to the Master
WorkstationST.
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 HMI’s 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:
Note In the previous example, the minimum value for Fahrenheit (32) and the
minimum value for Celsius (0) represent the same temperature, the freezing point of
water.
Format Spec Set displays the Format Specification Set that contains the selected
format specification.
Precision displays 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 displays the maximum value of the range used for unit
conversions.
Engineering Min displays the minimum value of the range used for unit
conversions.
Units displays the text that identifies the format specification unit.
Name displays 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 SDB in the System Information
Editor.
HMI Resources
An HMI (Human-Machine Interface) allows you to organize and customize access to
alarms and live data. Variables have an HMI resource property that can be set to one
of the HMI resources defined here. Each resource has a name and an optional
description.
• Adding and deleting screen files to the system (only from the System
Information Editor)
• Editing use of screen files by HMI WorkstationSTs
• Downloading screen files from Master location to HMI WorkstationSTs
• Editing screen files (from the Master location)
To view HMI screen files from the System Information Editor
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, select HMI Screens. HMI WorkstationSTs and HMI
screen files display in the Summary View.
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, right-click the HMI Screens item (or any item under it,
or in the Summary View) and select Add HMI screen file from the short-cut
menu. An Open file window displays.
Archiving Files
A project (or system) can be archived into a zip file from the System Editor,
however, the archive does not retrieve the files stored in the Master location. Also,
when a archived system is unzipped to a specific location, the files in the archive do
not automatically get distributed to the Master location.
When an archive is unzipped, the HMI screen files are located in a subdirectory
relative to the location of the system’s .tcw file. For example, if the system is called
abcSystem, and is stored in C:\Site, the .tcw file is located at
C:\site\acbSystem\abcSystem.tcw. The HMI Screen files are located at
C:\site\abcSystem\HMIScreens. This is the system location of the HMI
screen Files.
To copy files from the system to the Master location or from the
Master location to the System:
1 Open the System Editor. From the Edit menu, select System Information.
2 To copy to the Master location, from the System menu, select Copy Local
to Master.
3 To copy from the Master location to the system, from the System menu,
select Copy Master to Local.
Note If files already exist in the Master location when copying from the system to
the Master location, a warning dialog displays to ask if you wish to overwrite the
existing files.
A particular HMI WorkstationST may not require all screen files in the system.
Defining use of specific screens for each WorkstationST can be done from either the
System Information Editor or from the HMI WorkstationST component. When a
screen is added to the system, all HMI WorkstationSTs use that screen by default.
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, select HMI screen.
3 From the Summary View, select a screen, then in the WorkstationST column
(HMIws1 in the example below), select True to enable HMIws1 to use that
screen or False to disable use.
The HMI screen files are downloaded from the Master location in either the System
Information Editor or a particular HMI WorkstationST component. Downloading
can either occur automatically though a configuration property set for the
WorkstationST component or downloaded manually.
To download HMI screen files from the Master location to all HMI
WorkstationSTs
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, select HMI screen or HMI WorkstationSTs.
3 From the Summary View, select one or more HMI screen files.
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, expand the HMI Workstations item, then select a
WorkstationST component.
3 Select one or more HMI screen files in the Summary View.
4 From the Summary View, right-click to select Download selected HMI
Screens from the short-cut menu.
The System Information Editor can display the status of HMI screen files, including
the date and size of the master HMI screen file and the WorkstationST component’s
screen file.
Note The most important status property is whether the HMI WorkstationST screen
file is current with the master file.
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, select the HMI Screens item, or an HMI
WorkstationST item or a WorkstationST component.
3 From either the Tree View or the Summary View, right-click to select
Refresh HMI screen data from the short-cut menu.
The size and date of both the master and the local HMI screen file display in the
Property Editor.
To edit an HMI screen file, there must be a Windows association between the editing
application and the extension of the HMI screen file name. For example,
CIMPLICITY CimEdit is the application to edit CIMPLICITY screen files. The
standard extension for CIMPLICITY screen files is .cim. To edit CIMPLICITY
screen files in the ToolboxST application, CIMPLICITY must be installed on the
computer, and there must be a file association between the .cim extension and
CimEdit.
When CMS is used, the CMS repository is the source of the HMI screen files. When
editing is completed, the screen file is checked back into the CMS repository, then
copied, at the users discretion, to the master location so it can be used by all the HMI
Workstations that are configured to use it.
• If the HMI screen file is not checked out, you are prompted to check it out.
• If you click Yes, the file is checked out and the screen file is opened in the
appropriate editor.
• If you click No, you are asked if you wish to edit without CMS. If you click No,
editing does not take place. If you click Yes, the screen file opens in the
appropriate editor. Because the file is read-only, perform a Save As..
• Once you save the file and exit the editor, this message displays
• If you click Yes, the HMI screen file is copied to the master location. All HMI
WorkstationSTs that have the Auto Download option set to True get the
modified file next time the file status is checked.
• If you click No, the HMI screen file remains on the computer from which the
editing occurred.
• Check the file back into CMS. Once this is done, you again have the option to
copy the HMI screen file to the master location.
Editing an HMI screen file without CMS enabled
The source of these HMI screen files is the master location. When CMS is disabled,
the Check Out function copies the file from the master location to the computer
where the editing is taking place. The file is then checked back in to the master
location.
The edit dialog box that displays depends on the state of both the master file and
your system file.
Check out the HMI screen file and edit. This will overwrite your local file
locks the master file so that it cannot be edited by another user. The file is copied to
the computer from which you are running the ToolboxST application, and overwrites
any existing system file.
Check out the HMI screen file, but edit the local file locks the master file so
that it cannot be edited by another user at the same time, but does not copy it to the
computer from which you are running the ToolboxST application. The system file
currently on your computer is opened for editing.
Get the master HMI screen file and edit. This will overwrite your local
file does not lock the master file. It is copied to the computer from which you are
running the ToolboxST application and overwrites any existing system file. When
editing is complete, it cannot be saved to the master location.
Just edit local file does not lock the master file. It is not copied to the computer
from which you are running the ToolboxST application. The system file currently on
your computer is opened for editing. Once editing is complete, it cannot be saved to
the master location.
Get the master HMI screen and edit (the edit will be local only) copies to
the computer from which you are running the ToolboxST application and overwrites
any existing system file. The file is then opened for editing. Once editing is
complete, the file cannot be saved to the master location.
Edit only the local file is not copied to the computer from which you are running
the ToolboxST application. The system file currently on your computer is opened for
editing. Once editing is complete, the file cannot be saved to the master location.
Get the master HMI screen and edit (the edit will be local only) copies to
the computer from which you are running the ToolboxST application, and overwrites
any existing system file. This file is then opened for editing. Once editing is
complete, you can save the file to the master location.
When editing the screen file, all edits are saved in the system file. Once you exit
from the edit application, the ToolboxST application provides two options,
depending on the state of the files when you started the edit session.
You are either allowed do a Check In, which saves the file to the master location or
you are not. If you are not allowed (either the file is being edited by someone else or
you choose to edit only the system file), the following dialog displays.
Check in the HMI screen file copies the file to the master location, where it is
unlocked so it can be edited by another user.
Check in the HMI screen file, but leave checked out copies the file to the
master location, but the master file is not unlocked. It cannot be edited by another
user.
Do not check in the HMI screen file, but undo the check out does not copy
the file to the master location, but the master file will be unlocked, so another user
can edit it.
Do not check in the HMI screen file, but leave file checked out does not
copy the file to the master location, and the master file is not unlocked. It cannot be
edited by another user.
The ToolboxST configuration for alarm classes and format specifications can be
stored, or put, to an SDB from the System Information Editor.
1 Open the System Information Editor. From the System menu, select Put
System to SDB. (Refer to the section, System Information Editor.) A dialog
box displays to confirm the destination SDB Host and Path.
2 Click OK. When the process is complete, the results display on the Log tab of
the InfoView.
The WorkstationST
where the master
files are located.
The EGD Configuration Server maintains a group of .xml documents for each EGD
device. The EGD Configuration Server also maintains a MasterSymbolTable.xml file
that contains format specifications, alarm classes, and other system-level
information.
The protocol used to get and put these .xml documents to and from the EGD
Configuration Server is a published HTTP protocol. This protocol is available for
other tools, and is currently used by GE Fanuc’s CIMPLICITY ME. The ToolboxST
application uses the EGD Configuration Server if it has been enabled in the System
Editor.
Base Path is the URL on the EGD Configuration Server where EGD documents
reside. This is normally /EGD.
Note This is normally /EGD and should not be changed unless the system
administrator has installed a custom EGD Configuration Server.
Host Name is the Host Name or IP address of the host running the EGD
Configuration Server.
Note This should not be changed unless the system administrator has installed a
custom EGD Configuration Server.
Use IE Proxy selects the Internet Explorer proxy settings, if set to True. If set to
False, no proxy is used. The default is false and it is recommended not to use a
proxy.
When the EGD Configuration Server is enabled, a status bar indicates the
Online/Offline status. Right-click the status bar to obtain a shortcut menu, which
allows you to toggle between the two modes. If Work Offline is selected, the server
is bypassed when components are opened, built, or saved. This means that any
component saved results in a difference between the EGD Configuration server and
the ToolboxST application.
Or
View Differences displays a difference report for any consumed or produced data
file that exists in both the server and the local system.
View Server File allows you to view the server version of a selected document.
View Local File allows you to view the local version of a selected document.
Equalize Server to Match all Local System nodes makes equal any node that
is marked Not Equal by publishing the local configuration to the EGD Configuration
Server.
Empty Server, then Send all Local System nodes causes all EGD
configuration server content to be removed before the local system nodes are
published.
Note If a component in a .tcw file is not the latest configuration (for example, if the
most current configuration is on another computer), publishing the local EGD
configuration sends the old configuration to the server.
Send This Node Local To Server sends a local copy of a selected document to
the EGD Configuration Server. If the device’s tree node is selected, all documents
under the device are sent to the server.
Delete This Node in Server allows you to delete a selected device in the server.
Refresh Display compares the local system to the EGD Configuration Server and
updates the display.
1 If the external device does not already exist as a ToolboxST component, create
Note If the EGD Configuration Server option is enabled for the system, the EGD
configuration will also be put to the EGD Configuration server.
When there are either multiple versions of ToolboxST.exe (for example, during an
upgrade) or no installed versions of ToolboxST.exe, this dialog box displays all
versions that are equal to, or at a higher version than the selected .tcw file. When this
happens, the following dialog box displays to allow you to browse to and select an
appropriate version of ToolboxST.exe.
In this example, one of the ToolboxST.exe versions exactly matches the .tcw file
version so that entry is the default selection. Click the OK button to start
ToolboxST.exe v03.03.11B. Open the SystemConfigSample.tcw system
configuration after logging on to CMS. The Browse button allows you to locate and
start a version of ToolboxST.exe that is not installed.
For more specific details regarding the security function, including configuration,
refer to GEH-6706, ToolboxST* User Guide for WorkstationST*.
The following property is associated with the Users and Roles item.
Auto LogOff Timeout is the time, in minutes, after which a user who has
temporarily logged on over the existing user, is automatically logged off. If set to 0,
auto logoff does not occur. When the temporary user is logged off, the previous user
is again active.
Name is the user name. In Windows Domains, the name can be the
Domain/UserName.
Role is the role associated with the user, which defines the user’s access privileges.
HMI Resources are the HMI resources associated with a user. They are configured
in the System Information Editor, with assigned variables. Users who have a
resource that matches a variable’s resource can write to live data for that variable if
that privilege is assigned. If a variable does not have a resource, it defaults to
allowing the user to modify the data if the user’s role supports that privilege. Users
with an empty list of resources are only allowed to modify variables without an HMI
resource defined.
Name is the role name, which can be assigned to a user with all the privileges of
that role.
Alarm Privilege allows you to acknowledge and reset alarms in the WorkstationST
Alarm Viewer.
Tag Out Privilege allows you to tag out areas of the control system.
Logging On
From within the SecurityST User Logon Manager, you can:
the icon.
In the Property
Editor, enter the Auto
LogOff Timeout in
minutes.
If the temporary user remains inactive through the timeout period, that user is logged
off and this message displays.
The current user is now logged off. If the current user was the temporary user, the
sub-user now becomes the current user and previously defined user privileges take
effect.
Chapter 3 Software
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 block variables. This network of blocks and
connected variables controls a particular machine through physical inputs and
outputs.
Function blocks arranged and connected within a software element are called Tasks.
Tasks are grouped into other software elements called Programs.
User-defined blocks called user blocks are created using existing function blocks, as
well as other user blocks. These user blocks can be used in a task in the same manner
as function blocks.
Program groups can be used to add a level above programs; and together with user
blocks, the levels of hierarchy can be four or more as shown here:
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 block’s context. The combination of the variable name with the block’s name
and context give each variable a unique name within the controller. Blocks in the
same user block can reference each other’s 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 block’s block
diagram. For more information about editing blocks, refer to the section, Block
Diagram Editor.
Library definitions can contain tasks and/or user blocks created from other
definitions within the same library container. When a library definition is being
created or edited in the library container, the User Blocks tab on the right side of the
block diagram shows all task and user block definitions that exist in the library
container.
Programs, tasks, and user blocks in a controller component can be created from
library definitions. Once the controller component has referenced one or more user
block libraries, the Add Program, Add Task, and Add User Block dialog boxes allow
selection from the library definitions.
The process of updating programs, tasks, or user blocks with current library
definitions is called Instancing.
Note Definitions can contain user blocks or tasks that were created from other
definitions in a library. To be certain that ALL current definitions have propagated to
all necessary places in a controller component:
• Perform an Instance All command in the library container, then save the library
container.
• Perform an Instance All command in the controller component.
Unlink Property
All programs, tasks, and user blocks generated from a library definition have a
Boolean property called Unlink, which is False by default. In this state, they are
called linked.
Linked programs, tasks, and user blocks, with very few exceptions, cannot be
changed. They are updated with the current library definition when the Instance
command is performed.
Unlinked programs, tasks, and user blocks are disassociated from the library
definition, and can be modified. They are NOT updated with the current library
definition when the Instance command is performed.
Note Programs, tasks, and user blocks that do not come from a library definition are
called Embedded, and they do not have the Unlinked property.
9 From the Tree View tab, select a Program or right-click to add a new
Program.
11 In the Add Task dialog box, select the Select Library Block checkbox to
show library blocks.
12 Insert a linked user block by selecting the user block definition from the dialog
that displays.
- or -
Insert an embedded user block, 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
User block definitions are the source of both linked and unlinked user blocks. Each
user block has a version and description to help manage reusable application
software.
Instance scripts and text substitution allow user blocks to use a set of code in
multiple situations. These work with the ToolboxST automation interface and the
user attributes that belong to either the user block or the controller component.
User Attributes
User attributes are named values that allow you to specialize user block definitions.
They consist of a name, a data type, a description, a value, and a PromptforInput
property.
The PromptforInput property displays a dialog box that allows you to 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 command. Refer to the section, Working with User Blocks.
Device Attributes
Device attributes are similar to user attributes. They are named values that consist of
a name, a data type, a description, and a value. However, device attributes are
defined within a device configuration, and can be referenced by any application
software within the device. Device attributes do not have a PromptforInput property.
Refer to the section, Application Software Examples.
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 use substitution within a text field, embed a pair of braces {} within the text and
enclose the name of an attribute within the braces. For user attributes, the syntax is
attributeName and for device attributes, the syntax is device.attributeName. Refer to
the section, Application Software Examples.
The following window displays the major parts of the Library Container Editor and
the terminology used when referring to the editor.
The Component InfoView displays The Summary View is used for editing the
information about the currently selected user block selected in the Tree View .
tab.
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 their current configuration until they are upgraded. (If the old version
is uninstalled, the library container must be upgraded before it can be opened.)
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.
Adding Libraries
From the System Editor, double-click the Library Containers item to display the
editor window. 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.
1 From the Tree View, right-click the Libraries item, then select Add Library.
The Add New Library dialog box displays.
1 From the Tree View, right-click the Libraries item, then select Add Existing
Library to display the Select Existing User Block Library dialog box.
Tip The Summary View for the Libraries item displays names and locations of
all the function block and user block libraries 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.
Protection
Modify Data allows you to modify data values and forcing of variables.
Modify Design allows you to modify the design of defined blocks in this library.
View Design allows you to view details of the defined blocks in this library.
MHtml files (.htm) is a file that documents individual blocks in a library. It has the
same name as the block (Block1.mht) and it is located in the HelpFiles subdirectory
located under the library container. This format allows images and text to be
combined on a page, and can be created by Microsoft Word.
HTML files (.htm) is an html file that documents individual blocks in a library. It
has the same name as the block (Block1.htm), and it is located in the HelpFiles
subdirectory in the library container.
Text files (.txt) is a text file that documents individual blocks in a library. It has the
same name as the block (Block1.htm), and it is located in the HelpFiles subdirectory
in the library container.
• Block3.mht
• Block4.htm
Search Order
The ToolboxST application first searches for a .chm file that corresponds to the
Library name. If this is not found, it searches in the HelpFiles directory for a help file
that matches the block name. The search order is: .mht, then htm, then .txt.
Adjust 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 cannot be changed without another import.
Maximum Z value is the Maximum Z value used to limit the values that can be
entered in the live or initial values.
Minimum Z value is the Minimum Z value used to limit the values that can be
entered in the live or initial values.
3 Select the .csv table definition file (.csv) from the browser window and click
Save.
Double-click a value in
the Data Grid Editor.
This feature allows you to edit the table data values in the controller. Once the table
1 From the Tree View, right-click the library item and select Add User Block
Definition to display the Add New User Block Definition dialog box.
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. Refer to
the section, Property Editor.
Add Undefined Variables allows you to add all 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.
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 section, Application Software Examples
for examples on how to use attributes.
1 From the Tree View, right-click the User Block Definition and select Add
User Attribute to display the Add User Attribute dialog box.
3 Click the Attributes item in the Tree View to display properties in the
Summary View. The properties can be modified.
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
defined in the controller component. Refer to the section, Application Software
Examples.
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.
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.
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. Refer to the section, Block Diagram Editor.
Note In some locations, including Reports and the Block Diagram Editor, shortcut
menus contain commands that allow single pages or reports to be printed.
Page Options tab allows you Print Settings tab allows Print Profile tab manages
to change the paper size, you to change the saved print settings. It stores all
margins, and orientation. destination printer and its the settings from both the
associated settings. Options and Page Option tabs.
1 Open the ToolboxST application. From the File menu, select New System to
display the New System dialog box.
2 Enter a name for the new system, then click OK to display the System Editor.
3 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 updates to
reflect the change.
4 From the Tree View, double-click the Libraries item to open the Library
Editor.
7 Save the library container by clicking the Save button on the toolbar and
close the editor by clicking the Exit button in the upper right corner.
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.
If you do not have the configuration for a Enter the IP address in Click Next to continue.
particular controller, but know its IP the IP Address field.
address, click to select Upload from
Controller.
6 Save the changes by clicking the Save button on the toolbar, and close the
editor by clicking the Close button .
1 Open the System Editor for the test system created in the previous 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.
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.
Click OK to accept
the new value.
5 Save the changes by clicking the Save button on the toolbar, then close the
editor by clicking the Close button .
1 Open the System Editor for the test system created in the previous examples.
2 From the System Editor, open the Library Container Editor by double-
clicking the Libraries item in the Tree View.
Right-click the
Move_2 block
item to display the
block shortcut
mentu, then
select Add.
6 Save the library container by clicking the Save button on the toolbar, then
close the editor by clicking the Close 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, then click the
ellipsis button to display the Modify Value dialog box.
9 Change the value to True using the drop-down box, then click OK.
10 Click the Software tab. From the Tree View, locate the Prog1 item. If it is
collapsed, click the plus symbol to expand it.
11 From the Tree View, right-click the user block Lib1Usb1, then 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.
The block 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 row, then click the ellipsis button. In the
Modify Value dialog box, set the attribute value to False and click OK.
14 Save the component by clicking the Save button on the toolbar, then close
the editor by clicking the Close button .
1 Open the System Editor for the test system created in the previous 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 the item Lib1 and right-click the Lib1Usb1 user
block to display the shortcut menu.
4 From the shortcut menu, select Add User Attribute to display the Add New
User Attribute dialog box.
7 Change the Attr1_u data type to STRING by clicking the Type cell (which
currently contains UNDEFINED), then selecting STRING from the drop-down
list.
14 Save the library container by clicking the Save button on the toolbar, then
close the editor by clicking the Close 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 to expand it.
17 From the Tree View, right-click the user block Lib1Usb1, then select
Instance from the shortcut menu to update the user block. An Attributes item
is added to the Tree View.
18 From the Tree View, click the Attributes item. The attribute Attr1_u 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, then enter the text ABCDEFG to be substituted. Click OK to close
the Modify Value dialog box.
21 To verify that the variable name substitution has occurred, click the Variables
item under the user block Lib1Usb1. The ABCDEFG_thing variable displays
in the Summary View.
22 Save the component by clicking the Save button on the toolbar, then close
the editor by clicking the Exit button .
Application software in the controller consists of blocks that perform control logic
functions. The controller runtime 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.
Additional editing tools display on the toolbar, and a sidebar called the Library View
displays on the right side of the Summary View to allow you to make changes to a
user block.
Note If the user block is read-only or linked, an error message displays. If the user
block is protected, you are prompted to enter the appropriate password.
Auto-Layout Mode controls how the blocks on the diagram are arranged. Refer to
the section, Layout Modes.
Append Sheet adds a new drawing sheet at the end of the drawing.
Insert Sheet inserts a sheet immediately before the current sheet in manual mode.
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.
To rename sheets
From the Tree View, right-click the Programs item or right-click anywhere in
the empty portion of the diagram. The Rename Sheets dialog box displays.
Sheet Names
For a particular sheet, you can enter a complete sheet name or use certain
substitution characters to automatically number or letter the sheets within a particular
diagram.
Substitution
Character Represents Example
# Sheet number
{AttributeName} Attribute
Select Border or
Footer Options
Display a
preview of
selected
options
Edit
the
footer
Select Export or
Import to allow the
reuse of the border.
Coordinates, when selected, draws the grid of letters and numbers on the border.
Outer Line, when selected, draws a rectangle around the outer edge of the border.
Inner Line, when selected, draws a rectangle around the inner edge of the border.
Footer, when selected, draws the footer. When unchecked the Footer Options and
Footer Block section of the dialog is grayed out.
Footer Rows is the number of rows in the footer; each row is allocated vertical
space equal to the footer height divided by the number of rows.
Footer Columns is the number of columns in the footer; each column is allocated
horizontal space equal to the border width (which is paper size- dependent) divided
by the number of columns.
Preview
The Preview section allows you to display what the border looks like with the
current options. You can scroll the preview and zoom in and out. The footer cell
being edited in the Footer Block section is highlighted in the preview, and you can
left-click a footer block to select it for editing. You can also press and hold the left
mouse button and drag a footer block to move it around the footer.
Footer Block
The currently selected cell in the footer can be modified in the Footer Block section.
Next Cell selects the next cell in the footer (list is sorted in Z order back to front)
Previous Cell selects the previous cell in the footer (list is sorted in Z order back to
front)
Delete Cell removes the current cell from the footer. The button is only visible if a
cell is selected.
Create Cell adds a new cell to the footer at the current Row and Column. The
button is only visible if no cell is currently selected. Clicking an empty spot on the
footer in the Preview makes the Create Cell visible and preset the Row and Column
fields to where you clicked in the preview.
Row is the top-most Footer row for the current cell. It does not need to be within the
footer boundaries, which allows special effects like non-rectangular footers.
Export saves the current border from the editor to a specific .xml file.
OK saves the editor to the .xml file for the current device. The border .xml file is
always named SheetBorder.border.xml, and is saved in the same location as the
device .xml file.
Custom Text
Select this option to edit the following:
Text is text displayed in a larger font on the second line of the cell.
For both fields, text is clipped to the size of the cell (no wrapping), and both support
Attribute substitutions. For example if the custom Text for a border cell is Custom
Text with {Attr1} substitution, the {Attr1} is replaced with the current value of the
User Attribute Attr1 in whatever context the border is drawn. If Attr1 is not defined,
it is removed from the text. These attribute substitutions allow you to customize
footer contents for specific programs, tasks, or user blocks; you can also define
attributes at the device level.
Sheet Information
Select this option to edit the following:
• Customer Site
• Customer Name
• Drawing Number
• Engineer
• Requisition Number
• Process Application
• Shop Order Number
• DM Number
• Serial Number
• Machine Size
Certain user blocks and library blocks are designed to be dragged from the
ToolboxST Software tab to the CIMPLICITY application. This screen-building
software allows you to create graphical objects to represent a block, as well as
automatically configure the graphical objects to use global variables defined by the
block.
An example of
bad status
Certain blocks, such as the analog input (AI) block always use status. Pins that have
status contain a small slash, which indicates that more than one value is represented
by the line. Status pins can be connected to each other or connected to non-status
pins or immediate values. If a non-status variable or immediate is connected to a
status input pin, the pin always has the default status value.
Some complex blocks have functional groups of input and output pins.
Grouped
input pins
Certain blocks automatically hide pins that do not apply to the configured mode of
operation, as shown below.
Note Pins hidden by animations always display if they are connected to a variable.
MODE_OPT
set to AUTO Auto
displays Auto mode
mode pins pins
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, but leaves all layout tasks
to the user. It is ideal for users familiar with a sheet-oriented approach to design or
for applications where very specific documentation standards must be met.
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 Block Diagram Editor. The block displays on the Block
Diagram.
Or,
From the Tree View, right-click a task, a user block, or a block, then select
Add Block. The Select Block to Insert dialog box displays. Select the
desired block and click OK to add it to the Block Diagram .
Block Type displays the name of the library block from which this block was
created.
Instance Name displays a unique identifier that allows the block (as well as its
attributes and pins) to be referenced from other places in the ToolboxST application.
Left displays the location of the left of the block in the diagram.
Selected Pin displays the pin currently selected in the block highlighted in the
Block Diagram Editor.
Show Description, when set to True, displays the description text for this block on
the diagram.
Top displays the location of the top of the block in the diagram.
Block Data Type displays the name data type for variant pins on the currently
selected block.
Version displays as read-only the version number of the source for this block
instance.
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.)
Note While using the zoom tool, hyperlinks in the diagram are active.
Block Help shows reference documentation on the selected block type in a help
window.
Add To Trend allows you to open a new Trender window. The block is
automatically added to the new Trender.
Add to Watch allows you to open a new Watch Window. The block is
automatically added to the Watch 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.
Copy allows you to copy a block. Paste displays to allow you to paste the copy to
the Block Diagram Editor.
Cut allows you to cut a block from the Block Diagram Editor.
Delete allows you to delete a block from the Block Diagram Editor.
Bring 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.
Paste After allows you to insert whatever is on the clipboard but sets the execution
order of the blocks to be immediately after the right-clicked block.
Creates a new
variable in the
user block.
Sorted
columns
Pins represent inputs and outputs of a block. Parameters are a special type of Pin that
are always Inputs, and are usually constant values that control block operation. Most
Parameters are drawn on the Blockware diagram under the block; typically, they do
not display if they are left to their default initial value.
Note Clicking the Connection column displays a drop-down list that includes
Browse Globals and Browse Locals. If either of these is selected, the Select a
Variable dialog box displays to allow you to select a variable. Any enumerated
values that are legal for the selected pin also display in the drop-down list.
Note All block pin connection changes take effect immediately (there is no OK or
Cancel button in the Edit Block Pin Connections dialog box). From the Edit menu in
the Component Editor, select the Undo option to reverse any changes.
Tip Pressing Enter while entering text selects the next pin on the block, allowing
rapid entry of connections.
Select an option to
select a True or False
value for the variable.
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
Current value
of the variable
Enter new
variable value.
Enter a value to
be added to , or
subtracted from ,
the variable.
Double-click an element of
the array to display the
associated Send Value
dialog box.
The Variable Rail Tool arranges inputs along the left side of a particular
sheet and outputs along the right side to improve readability. It inserts a variable
reference that can be wired to a block pin and moved around freely.
Inputs Outputs
Variables on a variable rail display with symbols and cross references that indicate
the role of the variable in the system.
Note The Variable Rail tool is only used in Manual Layout mode (refer to the
section, Layout Modes). When you select the Variable Rail tool, a message box
displays that allows you to switch to this mode.
Global
variable
Undefined
variable
EGD
variable
Pin
callout
Note For each variable on the rail, cross references to other variable usages display.
1 From the Block Diagram Editor, select the Variable Rail drawing tool.
2 Press and hold the left-mouse button on the blockware diagram sheet, then drag
the mouse until the size and location of the new variable rail displays. Release
the mouse button when you are satisfied with the location of the rail.
To define a rectangular
area for the rail, click
and drag the cursor.
Note Clicking in the right or left two inches of the sheet docks the rail to the sheet’s
edge.
OR
Drag a pin or variable
from a block to the rail.
OR
Right-click the
rail to add
either a Global
Variable, a
Local Variable
or select from a
list of recently
used variables.
Click to select a desired variable, then drag the variable from the rail and drop it
onto a Block pin to form a wired connection.
Go To Where Used displays a list of all places that the selected variable is used
(hardware I/O, EGD page, and such)
Change Live Value displays the Change Live Value dialog box (you must be
online to use this menu option).
Add To EGD allows you to set the EGD page for the selected variable.
Text Tool
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.
Filled, if set to True, causes the text shape to use the Fill Color as a background
color.
Fill Color displays the background color shown behind the text if Filled is set to
True.
Filled when set to True, causes the shape to be 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.
Image Tool
The Image Tool inserts a Windows Metafile (.wmf) or Enhanced Metafile (.emf)
into the diagram.
Note The image file is not embedded in the diagram. All images must be distributed
separately from the .xml files for the diagram.
Metafile Path displays the path to the .wmf or .emf file containing the image that is
displayed.
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.
Tip You can have as many detached views as desired, which can be convenient for
moving 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
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.
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.
The Edit Diagram Settings dialog box allows you to edit the following options:
Landscape, when checked, makes the longest dimension of the paper, the
horizontal dimension, creating a drawing that is wider than it is tall.
Show Wired Pin Connection Text, when unchecked, hides the connection text
for wired pins, reducing clutter on the drawing.
Tip Selecting the Default to parent setting or a dimmed check box indicates that
you have no preference at the current level. The diagram uses the settings from the
next level down in the hierarchy.
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 RLD Editor is also available to simplify the process.
To add a contact
1 Select the contact tool that matches the type of contact you want
to add. The mouse cursor changes 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.
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:
Creation Wizard
Mark VIe components are created from the System Editor by using the Mark VIe
Creation Wizard screens.
To create a component
From the System Editor Tree View, right-click the system name and select
Insert New from the shortcut menu.
The Component
InfoView displays
feedback information on
the currently selected tab.
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.
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.
The Component InfoView contains several 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 or system events issued in the
ToolboxST configuration.
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 location in the component configuration where the
error occurred.
Status tab displays operating state and equality information about the Mark* VIe
component.
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.
Info tab displays context-sensitive descriptions for the selected Tree View or
Summary View item.
Note Some Data Grids, especially those without an Append Row, may not support
all features described in this chapter.
Row
headers
Currently
selected row
Append
row
Selected cell
Editing Data
To... Do this:
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 column Right-click the column header and select Hide Column.
Move a column to a different location Drag the column header to a new location.
Sort by a column Click a column header. The column sorts 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.
Add selected
column to the
data grid.
Move the
selected
column up or
down in the
Remove selected column order.
columns from the
data grid.
Remove all
columns from the
data grid.
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 rows Left-click the row header for the first source row. Then, while pressing the 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 two or Click the top left cell of the desired range and drag to the bottom right cell. Right-
more cells 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 grids Arrange windows on screen so both the source and destination grid are 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 diagram, Arrange windows on screen so both the source grid and a destination block
Trender window or Watch Window diagram, Trender window or watch window are visible. Then, drag the row header
from a data grid for the variable to the destination window.
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 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 the ToolboxST
configuration before pasting data from Excel.
Note In the Settings dialog box, categories are listed in a Tree View on the left side
of the dialog box.
Show Boot Loader displays the boot loader in the Download Wizard when it does
not have to be downloaded.
Enable I/O diagnostic Alarm Events, when set to True, makes available I/O
diagnostic alarm events for automatic updates in the I/O Diagnostic Viewer.
Show Diagnostic Icons, when set to True, displays diagnostic icons in the Tree
View and serves as a permissive to show more enhanced diagnostic icons in both the
Tree View and the Summary View.
Show More Enhanced Diagnostic Icons, when set to True, displays enhanced
diagnostic icons in the Tree View and the Summary View (Show Diagnostic Icons
must be set to True for this option to be enabled).
• Modify Data allows you to make changes to data values associated with an
object without changing how it works. For example, it protects the initial value
of a variable defined in a controller. The purpose of this right is generally to
keep unauthorized persons from making unsafe changes to settings.
• Modify Design allows you to change the way a protected object works. For
example, this 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 (refer to the section,
Protected Objects). Each right can have a different password set. 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 a protected object, the Enter
Password dialog box displays.
Protected Location
indicates which object is
protected within the system.
Although some object(s)
may not be protected, the
object can be contained
within another protected
object. It is important to
know which object is asking
you to enter a password.
Note Passwords are case-sensitive – secret and Secret are not considered to be the
same password.
Ellipsis button. If there is already a password on that access right and it has
not yet been entered, you are first asked for the password before being allowed
to change it. The Change Modify Design Password dialog box opens.
Password Caching
The security system caches passwords that were previously entered so that once you
enter a unique password, you don’t have to enter that password again. Separate
caches are maintained for the system and each major component (such as a Library
Container). A cached password remains until the component is closed.
Note From the Device menu, select Restore Password Protection to clear all
passwords and protect the component.
Tip If you have performed an operation in the ToolboxST application 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.
Modify Data allows you to modify data values and forcing of variables.
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
you from saving changes or changing initial values for variables defined in the
component's application software. Modify Design prevents you 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 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 are initially 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 do not propagate to instances of
that block.
Upgrading
To upgrade the ToolboxST application
Install the new version. Refer to the section, Installation. The icons on your
desktop and in your Start menu are updated to start the most recently installed
version.
The GE ControlST CD supports a variety of control equipment. These products
include updated firmware for the equipment and configuration tools that are
available as component editors inside the ToolboxST application. When you install a
new version of the CD, newer versions of some components may be installed as
well. To use the new versions, you must upgrade each component separately.
To upgrade a component
1 Install new software for the component type that you want to upgrade by
installing the latest version of the ToolboxST application.
2 Start the ToolboxST application and open the system file. Double-click a
component to open its Component Editor.
Click Next.
1 From the System Editor Tree View, double-click the Mark VIe component
to display the Mark VIe Component Editor.
The report displays configuration differences in areas such as hardware and software.
Differences are arranged in appropriate groups and sub-groups.
Edit Undo Remove the item currently selected in the Tree View
Redo Add a new component to the current system
Cut Cut the selected item in the Tree View
Copy Copy the selected item in the Tree View
Paste Paste the copied item in the Tree View into the Summary View
Delete Display the System Information Editor (refer to the section System Information
Editor)
Find Display the Component Editor for the item currently selected in the Tree View
Bookmarks Mark and toggle between items in the Tree View
View Go Back Return to the view that immediately preceded the current view in the history
Go Forward Return to the view that immediately follows the current view in the history
Forced Variables Display a list of forced variables
General Tab
The General tab allows you to configure general properties and attributes of a Mark
VIe controller, including redundancy (simplex, dual, or Triple Modular Redundant
(TMR)) and frame rate (its basic scheduling rate).
Property Editor
allows you
to edit the item
currently selected in the
Tree View.
% Command Size specifies the maximum size (as a percentage) of both the
command and event portions of the Command and Event log.
% Event Size specifies the maximum size (as a percentage) of the event
portions of the Command and Event log.
Time specifies the number of days that the Command and Event log is kept if
the allocated space is not exceeded.
Compressed Data Log activates the compressed data logging, which causes
selected variables to be collected in the controller data log file.
Note The Compressed Data Log property is only available when the application
running is a 1.5 MW Wind Turbine.
% Size specifies the maximum size (as a percentage) of the Compressed Data
log.
Average Interval Time specifies the interval in minutes over which the data is
averaged and stored.
Enable Compressed Data Log, when set to True, activates the Compressed
Data Log. This causes selected variables to be collected in the controller data log
file.
Time specifies the number of days the Compressed Data log will be kept so long
as the allocated space is not exceeded.
Controller Web Pages, when set to True, enables access to controller web pages
if they are provided by the controller or another product. The controller can provide a
set of default pages as part of the firmware download. Product web pages can also be
downloaded to the controller. For example, the 1.5MW Wind Turbine uses product-
specific web pages that are downloaded separately.
Enable Controller Web Pages, when set to True, activates the Web server on
the controller. It also displays the Web Page Tab.
Web File Path is the directory used as the web page source when downloading
product web pages to the controller.
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.)
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 can only be changed from the
System Editor.
NTP Configuration Mode determines how the Network Time Protocol client
synchronizes the controller time. Valid options are:
NTP Configuration Primary Server is the IP address of the primary server used
when unicast mode is selected.
Platform is the type of hardware on which the Mark VIe control code is started.
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.
• Modify Data permits modification of data values and the forcing of variables.
Logic forcing procedures can result in personal injury or
death, if not strictly followed. Only adequately trained
personnel should modify any programmable machine.
Forcing of control logic for an operating process is strongly
discouraged.
Forcing of protective functions is never permissible for an
operating unit. All safety measures should be strictly
enforced in conjunction with this procedure.
• Modify Design permits modification of the design of the controller.
Redundancy determines the level of redundancy of the controller. The following
choices are available:
Frame Period determines the frame period in milliseconds. A frame is the basis for
Mark VIe 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.
Enable Wind Farm Management System, when set to True, allows a wind
turbine to be controlled by the wind farm controller.
Note The four properties below are only available when the application running is a
Wind Control.
Max Wind Farm Turbines is the maximum number of wind turbines for this
Wind Control
Wind Farm Master Number is the master plant number for this Wind Control.
Wind Farm Update Time (ms) is the time, in milliseconds, to update all wind
turbines.
Wind Turbine Timeout (sec) is the time, in seconds, at which timeout data is
received from the wind turbines.
The name of
the attribute
being modified
The value of
the attribute
If checked, the
attribute values
are restricted to
an enumeration
(a predefined set
of allowable
values).
To add a value to the enumeration, enter the Name, The Data Type
Value, and (optionally) a Description, then click OK. of the attribute
Host Name is the Internet Protocol (IP) host name for the selected network adapter.
Wire Speed is the speed of the network to which the selected adapter is connected.
Network sets the network connected to the selected adapter. (Available networks
are determined in the System Editor.)
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.)
Hardware Tab
The ToolboxST application manages I/O packs and terminal boards through a logical
unit called an I/O module. An I/O 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 used to identify physical characteristics of the
pack. Each I/O pack module that can be added to a Mark VIe controller 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.
Click Next.
Click Next to
preview
configuration
information.
To create a group
From the Hardware tab Tree View, right-click the Distributed I/O item and
select Add Group. The Add Group dialog box displays.
Enter a
Description of
the group
(optional).
Click OK.
the mouse pointer changes to a symbol, release the mouse button to move
the module.
Viewing Modules
Group Layout
When you select a module from the Tree View, several tabs display in the Summary
View. Each module contains four common tabs (Summary, Parameters, Variables,
and Diagnostics). Many modules also contain 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, as well as two other tabs, Inputs and Outputs.
Parameters Tab
The Parameters tab allows you to configure 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.
The Variables tab displays available variables from the module that have no physical
endpoint. These variables exist only internally in the module, and can be connected
to another variable for use in code.
Inputs/Outputs Tabs
This tab contains I/O points (with associated screws in sub-tabs) that have no
meaning to software or firmware, such as those used for excitation.
ExtraCircuits Tab
This tab contains input/output variables found on the module terminal boards, which
can be associated with the application software. For some modules, these tabs are
split into more module-specific input/output tabs that better define their function.
Inputs/Outputs Tabs
These tabs contain input/output variables found on the module terminal boards,
which can be associated with the application software.
Note For some modules, these tabs are split into more module-specific input/output
tabs that better define their function.
If the variable name entered is a defined variable, it continues to display and the
cursor moves to the next field.
If the variable name entered is undefined, the Undefined Variable dialog box
displays. Click Yes to select the desired software item, as shown above.
ExtraCircuits Tab
This tab contains I/O variables (with associated screws in sub-tabs) that have no
meaning to software or firmware, such as those used for excitation.
The Diagnostics tab allows you to check the I/O pack alarms and errors that exist 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.
The state
of the fault
Active Alarm(s)
Status Tab
The Status tab allows you to check the I/O pack version and network communication
status.
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
PEFV with compatibility code set 2,1 and a PEFV with compatibility code set 3,1.
Diagnosing Modules
When a problem with a module is detected, symbols display in the Summary tab. All
symbols provide ToolTips.
The I/O Diagnostic viewer provides a utility to interrogate I/O pack faults, version,
and diagnostic communication data. Diagnostic I/O pack reports can be generated on
a pack, module, or component level.
Normal
Active Alarm(s)
Note Place the mouse over the icon to display detailed messages regarding the
problem.
Working Online
Downloading 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.
Comparing Parameters
The Programs item at the top of the Tree View holds all programs in the controller.
Its shortcut menu contains actions that affect all programs, such as changing library
references and instancing all linked user blocks. The shortcut menu also contains
commands to add a new or existing program to the controller.
Adding a Program
The Programs item allows you to add programs to a controller.
To add a program
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.
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 Tree View, right-click the Programs item, then select Library
References. The Library References dialog box displays all block libraries
in two tabs.
1 From the Tree View, right-click the Programs item, then select Library
References. The Library References dialog displays all available user
block libraries.
2 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.
Instance All
The Instance All command creates a new copy of all linked user blocks from the
referenced user block libraries. In addition to updating the user blocks, this command
causes the instance scripts and text substitutions to run.
The Protection
property defines
access rights to
the overridable
properties list.
To add a task
From the Tree View, right-click on an embedded or unlinked program name to
display the shortcut menu.
Note The Add Task and the Add User Block dialog boxes are identical except for
the title bar, which shows how the new user block is used.
A user block can either be linked from a user block library, or embedded, acting as a
container for function and user blocks.
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 unlink a program
From the Tree View, right-click a program item, then select Unlink
Permanently.
The linked icon next to the item in the Tree View changes and the program is
unlinked from the library.
Note Linked tasks and user blocks can also be unlinked permanently.
Property Editor
The Property Editor displays different properties, depending on which item is
selected in the Tree View.
Remove Unused Variables removes the unused variables for all linked user
blocks in this device when the user block is instanced.
Execution Order sets the order of execution of this program in the controller.
BlockType is the name of the user block definition in the library from which this
user block started.
Protection expands to show the access rights for this user block definition.
Frame Multiplier is the number of frames at which the user block runs.
Schedule Offset is the offset from beginning of frame at which the user block
runs.
Block Type is the name of the library block that the selected block is an instance
of.
Instance Name is a unique identifier that allows the block to be referenced from
other locations in ToolboxST.
Instance Script causes the script to run when the block is instanced.
Show Description, when set to True, displays the description of the selected
block.
Block Data Type is the data type for variant pins in the selected block instance.
Enable, when set to True, enables variables for the selected block.
Version is the version number for the source of the selected block instance.
Variables
Program variables are global variables associated with a particular program. The
variables display under the Programs 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. Undefined variables for tasks and
user blocks are local variables that have been referenced within the task or user
block.
User block and task variables are local by default, and display under the associated
user block item in the Tree View.
Variables can be edited in the Data Grid and Property Editors. The Data Grid is used
to view or edit variable definitions, and can be configured to display a subset of the
variable properties. Refer to the section, Data Grids.
Note Variables can also be added in the Summary View by directly editing the last
row of the variable grid.
Alarm, if set to True, enables the variable as an alarm. Alarms are used for problems
that require the operator’s attention and acknowledgement. The alarm queue consists
of a list of time-tagged alarm state transitions.
Alarm Class selects a System Configured Alarm Class, used by the HMI to
classify and colorize alarms.
Alarm On Zero, if set to True, causes the alarm on a 1-to-0 transition. Requires that
the Alarm be set to True.
Event, if set to True, enables 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, if set to True, enables the variable as a Hold, which is similar to an alarm. The
hold queue contains a list of time-tagged hold states in the turbine startup sequence.
Normal Severity is the value assigned to an alarm in the normal state. The valid
range is 1through 1000, where 1 is the least severe.
Plant Area places variables into logical plant groupings for display in the
WorkstationST Alarm Viewer.
Display High Limit is the default upper limit for displays on the HMI (for
example, bar-graph or trending displays). If a Format Spec has been specified and
this display-high property is not specified, the Format Spec Engineering Max is used.
Display Low Limit is the default lower limit for displays on the HMI (for example,
bar-graph or trending displays). If a Format Spec has been specified and this display-
low property is not specified, the Format Spec Engineering Min is used.
Entry High Limit is the default upper limit for setpoint entry on HMI (for example,
bar-graph or trending displays). If a Format Spec has been specified and this entry-
high property is not specified, the Format Spec Engineering Max is used.
Entry Low Limit is the default lower limit for setpoint entry on HMI (for example,
bar-graph or trending displays). If a Format Spec has been specified and this entry-
low property is not specified, the Format Spec Engineering Min is used.
HMI Resource allows access and visibility of variable and alarm data to be
customized.
Units are engineering units. If a Format Spec has been specified and this Units
attribute is not specified, the Format Spec Units is used. If you are using the SDB
version of the HMI device, this attribute is not used. Only the format specification's
Units string is used.
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 allows array length, data type, and enumeration editing.
EGD Page is used to assign the variable to an Ethernet Global Data Page.
Global Name Prefix is the variable's global name prefix type (None, Full, Block,
Program, Task). 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 task
Task1 in program CORE would display (depending on the Global Name Prefix) as:
None IGVA
Full CORE.VG_Health.IGVA
Block VG_Health.IGVA
Program CORE.IGVA
Task Task1.IGVA
Scope is the 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 global, it can be used
in other programs and user blocks. A variable must be global to be used on EGD.
Output pins are shown on the right side of the user block.
State pins are shown on the right side of the user block.
Virtual HMI Point, if set to True, imports the variable into the HMI as a virtual
point.
Controller Collected, if set to anything other than Not Logged, logs the value to
the Compressed Data Log in the controller.
Note The Controller Collected property is only available when the application
running is a 1.5 MW Wind Turbine.
Note The Override Properties property is only available for global variables that are
contained within a linked program, task, or user block.
Override Value, if set to True, allows the Initial Value of a linked variable to be
modified.
Note The Override Value property is only available for control constants that are
contained within a linked program, task, or user block.
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:
Program Variables
Program variables are global variables associated with a particular program. The
variables display under the Programs 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.
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.
The Summary View displays all user blocks and associated scheduling information
in that program. The Frame Multiplier and Schedule Offset fields can be changed
from this view (see below). The available columns are as follows:
Frame Multiplier is the number of frames at which the user block runs.
Schedule Offset is the offset from beginning of frame at which the user block
runs.
Period, in milliseconds, is the period at which this user block runs. Calculated by
multiplying the frame multiplier by the controller’s frame period, which is set on the
General tab.
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
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.
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 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.
1 From the Software tab, expand the User Block item to display the Variables
item.
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. Refer to the section, Working with
User Blocks.
The Property Editor for a user block displays slightly different information
depending on whether it is a task or just a user block inserted under another user
block. Tasks contain scheduling information, but a user block contained within
another user block does not.
BlockType is the name of the user block definition in the library from which this
user block started.
Protection expands to show the access rights for this user block definition.
Frame Multiplier is the number of frames at which the user block runs.
Schedule Offset is the offset from beginning of frame at which the user block
runs.
Configuring DDR
To configure a DDR
From the System Editor, double-click the Mark VIe Component. The
Component Editor displays.
Name is the user-defined description for this DDR, which is used for the filename.
DataRecorder Setup
Auto Enable, if set to True, automatically re-enables the DDR after 60 seconds
once it is uploaded.
Buffer Control
Normal causes the DDR to collect pre-samples before a trigger event and
thereafter continue collecting until Enable transitions False or the collection fills
the buffer.
Circular causes the DDR to collect data indefinitely until Enable transitions
False. The buffer will be filled with the newest samples. No trigger is used.
Only causes the DDR to evaluate the trigger each execution and only collect data
when the trigger condition is satisfied. Data is 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 are the number of samples collected after the trigger
including the trigger sample.
Pre-trigger Samples are the number of samples collected before the trigger.
Setup Variables
Trigger Setup
EQ is the value of the trigger variable, which must be equal to the trigger value.
GT is the value of the trigger variable, which must be greater than the trigger
value.
GE is the value of the trigger variable, which must be greater than or equal to the
trigger value.
LT is the value of the trigger variable, which must be less than the trigger value.
LE is the value of the trigger variable, which must be less than or equal to the
trigger value.
NE is the value of the trigger variable, which must not be equal to the trigger
value.
Trigger Type
Status Variables
Status variables, which indicate the status of the associated DDR, are used to
determine when to upload the data. Status variables are always integers, and are
automatically defined and placed on the EGD status page.
Adding 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 Recorders tab to
display the DDR list.
Updating DDR
DDRs can be updated separately from the application code download.
To update a DDR
From the Device menu, select Download, and then select Update Dynamic
Data Recorder. Or, click the Update Dynamic Data Recorder button
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 is 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.
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 is set up as a Sine wave generator and FuncGen2 is set up
as a Triangle wave generator.
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.
EGD Configuration
To configure EGD for a component
The following properties display in the Property Editor when Ethernet Global Data is
selected in the Tree View:
Collection 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
Produced Pages
Produced Pages are data samples configured to be available to other components on
the network.
Note When the first Produced Page is created, it automatically becomes the Default
page.
Tip Any variable defined with $Default as the EGD page name is automatically
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.
The properties
for the selected
page display in
the Property
Editor.
The following properties are available for configuration when a Produced Page is
selected in the Tree View:
Mode, when set to Broadcast, sends the page to all EGD nodes. When set to
Unicast, the page is only sent to a single destination.
Default Page can be 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 set to Auto, automatically assigns exchange numbers and offsets
assigned at build time. If set to Manual, exchange numbers and offsets can be
entered manually.
Period Multiplier multiplies the value by the Controller frame period to obtain the
EGD page period. (The results display in the Period property.)
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 exchange’s skew
by exactly this value. For example, if you have three exchanges in a page and a skew
value of 2, the first exchange’s skew is two, the second exchange’s skew is four and
the third exchange’s skew is six. (The skew property is measured in nanoseconds.)
Starting 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 compression is performed, the variables are located in increasing size
order, starting with Booleans, then Words, Double Words, and finally all other
variables. A page compression causes an exchange major signature. Consumers can
mark the exchange variables as unhealthy until the consumed configuratuion can be
rebound.
1 From the Component Editor Tree View, right-click the desired page, and
then select Add Variable. The Select a Variable dialog box displays.
Note To edit exchange signatures and configuration time, set Layout Mode to
Manual.
1 From the EGD tab, select the Configuration tab, then select a Produced
Page in the Tree View.
2 Right-click an exchange in the Summary View, then select Edit Exchange
Signatures and Configuration Time.
3 Review the warning about manual Exchange Signature editing, then click
OK.
4 Make any desired changes to the signatures and configuration time, then click
OK to close the dialog box.
Due Time is the time that a consumer data packet must be received for an exchange
to remain valid
Length is the value for a produced exchange. This length may be the highest
variable offset in the exchange or the highest offset of a variable, which may have
been removed. For a consumed exchange, the value may be the highest variable
offset used or the length of the produced exchange, depending on the bind algorithm
of the individual tool.
Missed Count is the number of data production packets missed since initialization.
A missed packet occurs when a data production message is received that has a
request ID greater by more than one than the last message received (accounting for
counter roll-over).
Refresh Errors are the number of times a refreshment fault has occurred. A
refreshment fault occurs when a subsequent data production packet (or initial packet
at startup time) does not arrive at a consumer within a pre-defined update period.
Note The EMT provides a detailed view of the configuration server contents.
The Filter Toggle button defaults to a filtered state. It displays items that have
the same name but have a different Producer ID as the open component.
The Delete button deletes the selected item(s). If the item(s) were saved as part
of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an
EGD node.
The Referenced Devices item on the EGD tab also has a Compare command that
compares the consumed variable information for the open component against the
EGD configuration server’s content.
Referenced Devices
The EGD variables defined in other components can be added to the current
component’s variable list by adding a reference. References can only be created to
EGD-capable devices that are producers of pages.
Note When EGD configurations are edited in remote devices, you must refresh the
configuration to ensure that the latest variable information is used. The configuration
is automatically refreshed when a component is opened, and when a Build is
performed in the component.
This feature can be implemented using the existing controller (referred to as Mark
VIe integrated Modbus) or an additional controller (referred to as Mark VIe gateway
Modbus).
Using the existing controller allows for a direct Modbus interface, but would expose
the controller to the extra loading and burden of serial interrupts when serial
communication paths are needed. Because a serial interrupt is critical, the Modbus
slave feature supports both serial and Ethernet/TCP capability on Mark VIe gateway
Modbus, while only Ethernet/TCP capability is supported on Mark VIe integrated
Modbus.
Mark VIe gateway Modbus is always run in simplex controller mode without
sequencing blocks.
Modbus Overview
Ethernet
Connection Timeout specifies the time in minutes that the slave remains
connected to the master over Ethernet when no requests are being received. The valid
range is one to 10.
Interface
Shared (both Ethernet and serial) is only supported on Mark VIegateway Modbus.
Baud Rate specifies serial communication rate (bits per second). The valid choices
are 2400, 4800, 9600, 19200, 38400, and 57600.
Data Bits specifies number of bits per character. Only eight bits is supported.
Parity specifies check character. The choices are None, Odd, Even, Mark, and
Space.
Station specifies the slave address associated with the serial port. The valid range is
1 to 255.
Stop Bits specifies serial stop-bits. The valid choices are 1 and 2.
Command Limit limits the number of commands processed per second. This is
based on commands that have changed, not commands that are identical to
previously received commands. The valid range is 0 to 25.
Data Swapped changes the transmission order if the data is greater than 16 bits
when set to True. Refer to the example below.
Settings Example
If set to True 32-bit example: 0x01234567 would be transmitted as 0x45 0x67 0x01
0x23
64-bit example: 0x0123456789ABCDEF would be transmitted as 0xCD
0xEF 0x89 0xAB 0x45 0x67 0x01 0x23
If set to False 32-bit example: 0x01234567 would be transmitted as 0x01 0x23 0x45
0x67
64-bit example: 0x0123456789ABCDEF would be transmitted as 0x01
0x23 0x45 0x67 0x89 0xAB 0xCD 0xEF
NAK Code specifies the Negative Acknowledge code to be used if data is requested
from a controller that is incapable of receiving the Modbus request. Code options are
4, 6 or None. None is selected only if the master needs no reply when
communication fails between the Mark VIegateway Modbus and the target
processor.
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:
Data Types
The ToolboxST application allows you to specify the variables on each page using a
Data Grid. When you add a variable to a page, both the Modbus slave and the
selected page are enabled on the controller. As you add and remove variables, the
controller is updated so that only pages containing variables are enabled. To
completely disable the Modbus slave, remove all variables on all pages or select
None as the Interface in the Property Editor.
Connected Variable is the variable that is read or written from the device or the
referenced device. A variable must be on an EGD page before it can be added to a
Modbus slave page. A connected variable must be added before the other columns
become active.
Point Data Type determines the variable data type and the registers used to
transmit the variable 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 that takes one register
• UINT is an unsigned 16-bit word that takes one register
• DINT is a signed 32-bit word that takes two registers
• UDINT is an unsigned 32-bit word that takes two registers
• REAL is a signed 32-bit float that takes two registers
• LREAL is a signed 64-bit float that takes four registers
Address specifies the register address. When a variable is created, the address is
automatically set to a value adjacent to the highest 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 addresses. The valid
range for addresses is 1 to 65534. When specifying an 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.
Name is a read-only identifier automatically generated from the register page name,
the address, and, if necessary, an added unique number.
Creating Reports
To create a report
Open a Mark VIe Component Editor. From the View menu, select Reports,
then select the desired report type from the drop-down list. Refer to the section,
Report Types. The I/O Report displays in a new window.
Viewing Reports
To change the zoom level of a report
From the Report View menu, select Zoom, then select the desired zoom value
from the submenu.
Lists available
comparison and
Boolean operators
(double-click an
operator to add it to
Lists available the equation).
columns (double-
click a column to
add it to the
equation).
Click to add
parentheses to
your equation.
In this box,
enter the filter
equation to be
used.
Click OK to accept the Click Clear to erase the Click Cancel to cancel the
filter equation as shown. current filter equation. equation without changing
the current filter settings.
If selected, the
capitalization in the
report and the
search string must
exactly match.
3 In the Open Report... dialog box, select a report, then click Open to import
the data. Any data that cannot be imported is highlighted when the imported
report displays.
Multiple Writes are variables used in multiple locations, such as blockware logic,
EGD, or I/O point configuration.
Unused I/O are connected I/O values that are not used anywhere.
Global Variables
The Global Variables window displays all controller variables that have been
configured as Global in one central location.
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. Refer to the section, Data Grids.
Because only existing global variables can be changed, new variables cannot be
added 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.
Note If this is the first time the Watch Windows dialog box has been opened for the
selected component, the list is empty. Add or import a new Watch Window.
2 From the Watch Window dialog box, either add a new Watch Window or
double-click to open an existing one.
Adding a Variable
Use the Add Wizard to add a variable to a Watch Window.
To add a variable
To remove a
variable, select it
and click the
Remove button.
When all variables
have been added,
click Finish.
Select All selects all variables for removing, pasting, or copying to the clipboard.
Go to Definition allows you to display the variable definition from it’s location.
Change Live Value allows you to change the live value when the Watch Window
is online with the controller.
Copy to Clipboard allows you to copy the selected variable to the clipboard.
1 From the Watch Window, double-click the live value of a selected variable.
The Send Value dialog box displays.
2 Enter the desired value, select the Force Value check box, then click Send
and Close.
• For constants in which the Initial Value was checked, the Initial Value is sent to
the controller, making the Live Value equal to the Initial Value.
• For constants in which the Live Value was checked, the Initial Value is set equal
to the Live Value.
Drag-and-Drop
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.
1 In the Watch Windows dialog, select the desired Watch Window, then click
the Export button.
2 The Export Watch Windows dialog displays. Select the desired destination,
then click Save.
1 From the View menu, select LiveViews. The LiveViews dialog box displays.
2 Right-click the desired LiveView, then select View. The LiveView displays.
1 From the View menu, select LiveViews. The LiveViews dialog box displays.
2 Right-click the desired LiveView, then select View. The LiveView displays.
Stop the
running
Delete LiveView
Cut Paste
Run the Show / Hide the
Liveview PropetyGrid
Undo
Show / Hide the
Event Viewer
Layout Toolbar
Advanced Mode
Align Centers Toggles between
The selected controls Simple and
Horizontal center are aligned Advanced Mode
to the horizontal center of the Send to Back
Primary selection
Bring to Front
Align Tops
The selected controls Top are
aligned to the top of the
Primary selection
Align Bottoms Center Horizontally Control Width and
The selected controls Bottom The selected controls are
are aligned to the bottom of Height
centered horizontally to the Both the width and height of
the Primary selection panel the selected controls are
made equal to the primary
selection
Analog Meter – the pointer is Bar Graph – the bar fills with the
deviated with respect to the live live value of the variable.
value of the variable.
To attach a variable
1 From the Tools window, either double-click or drag Var:Live onto the design
surface.
Click Next
Once variables have been attached to a LiveView by using the wizard, additional
variables can be attached directly from the system component.
Note You can also attach a variable by entering the variable name in the variable
property.
Variable Definitions
It is possible to find and display a variable definition.
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)
NAME,VALUE,TYPE,UNITS,DESCRIPTION,FORMAT SPECFICATION
ControlConstant3,6.234,REAL,,,
ControlConstant2,55,DINT,,,
ControlConstant6[0],true,BOOL,,,
ControlConstant6[1],false,BOOL,,,
ControlConstant6[2],true,BOOL,,,
ControlConstant6[3],false,BOOL,,,
ControlConstant6[4],true,BOOL,,,
ControlConstant4,8769.876,LREAL,,,
ControlConstant5[0],20.1,REAL,,,
ControlConstant5[1],23.2,REAL,,,
ControlConstant5[2],34.5,REAL,,,
ControlConstant5[3],40.6,REAL,,,
ControlConstant5[4],55.5,REAL,,,
ControlConstant1,1,BOOL,,,
The Mark VIe component 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.
The ToolboxST configuration is the maintenance software tool for Mark VIe
components. 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 Triple Modular Redundant (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-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-1
Status Tab
When the ToolboxST application is connected to a Mark VIe component, 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 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
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.
6-2 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
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 States are as follows:
State Description
Powerup Power up controller
Master initialization Initialize controller
Designated controller determination Determine which controller is designated in a redundant controller
configuration
Data initialization Perform initialization of non-designated controllers with NVRAM,
command variables, and constants
Inputs enabled Wait in this state for all required 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
won’t 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.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-3
If the indicated Control State is not Controlling, the ToolboxST application can
provide additional information as follows:
DDR Equality indicates whether equality exists between the Dynamic Data
Recorder configuration in the ToolboxST application and the configuration currently
running in the controller. Valid states are Equal and Not Equal.
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. If there
is less than 20% idle time, the status is shown in yellow.
System Idle 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 toolbox communication overhead.
6-4 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
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.
Downloading to a Controller
The ToolboxST application is used to configure both a Mark VIe component and its
distributed I/O modules. Both the component and the I/O modules have four items of
software that can be downloaded:
Boot Loader 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.
Base Load 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.
Firmware 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.
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.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-5
Controller Setup
The Controller 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
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 Setup. When
the Welcome window displays, click Next to continue.
6-6 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
Select the desiredChannel, then click Next to continue. A
progress dialog box displays the status of the setup.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-7
Click the Scan
button to search for
available
CompactFlash
cards.
To configure TCP/IP
Settings, select the
available channel(s),
then enter a Host
Name, a Gateway IP
Address , an IP
Address, and a
Subnet Mask for
each.
Note If the controller is configured as either simplex or dual, some channels may not
be available.
Download Wizard
The Download Wizard is the primary method of transferring software to a Mark VIe
component 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.
1 Open a Mark VIe Component Editor. From the Device menu, select
Download, and then Download Wizard to display the Download Mark VIe
Controller wizard.
2 If you have changed configuration settings since the last Build operation, a
message box displays indicating that the software is out of date. Click Yes to
build the current configuration. The Download Mark VIe Controller wizard
opens.
6-8 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
3 Click the Next button to advance past the wizard’s introductory page.
Click Next.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-9
Shows status of individual
Displays overall progress. download operations.
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.
6-10 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
Dual Controller Download
The ToolboxST application supports the ability for downloading controllers that
have dual redundancy. This feature allows you to select one of the two controllers to
download, then provides a configured time period to review the changes running on
the downloaded controller. Based on that review, the changes can either be
downloaded with the new configuration or reverted to the other controller. That
controller assumes control and the previously running configuration is restored on
the downloaded controller.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-11
If you selected the
recommended First
Download, the
selected controller is
downloaded.
Note During this time period, the controller Editor window displays to allow you to
confirm that the code changes being downloaded are functioning properly. You can
navigate the configuration, as well as access the Trender, Watch Windows and
LiveView features.
6-12 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
3 If you are not satisfied with the code changes during the two-minute time period,
click the Revert button. This causes the second controller to become the
designated controller and causes the first controller to revert its running
configuration to the previous version.
If you initiate a
download after
performing the
revert function, the
second controller
displays as the
designated
controller.
Note If you do not click either the Accept or Revert buttons during the two-minute
time period, the revert function is automatically invoked.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-13
Upload Wizard
The ToolboxST application can retrieve existing configuration information from a
Mark VIe component 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.
1 Open a Mark VIe Component Editor. From the Device menu, select
Upload to display the Upload Controller wizard.
2 Click Next to advance past the introductory page of the Upload Controller
wizard. If the Mark VIe is configured as a redundant component, the following
page displays with an option button for each available redundant component.
Select a controller
and then click Next.
6-14 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
3 When the upload completes, click Next to display the final page of the wizard.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-15
Diagnostics Views
Controller Diagnostics View
The Controller Diagnostics View displays diagnostic messages for a controller
component. Diagnostic messages are errors or warnings that occur in the hardware
component and could cause the component to function improperly. Retrieving these
messages should be one of first steps in diagnosing any problems with hardware,
communications, or other related ToolboxST subsystems.
Click this button to clear Click this button to Select this check box to show
diagnostic messages with the manually retrieve diagnostic messages with status
status of 0. Only these inactive diagnostic messages. of 1 only. Clear this box to show
messages may be reset. all messages.
In a Duplex or TMR
configuration, use this
drop-down list to
select the desired
redundancy
component for which
to retrieve diagnostic
messages.
Displays the
timestamp of the
message.
6-16 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
I/O Diagnostic View
The I/O diagnostic view displays diagnostic messages for a component hardware I/O
module. Retrieving these messages should also be one the first step in diagnosing
any problems with hardware I/O.
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.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-17
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.
6-18 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
Totalizer Passwords
All users can view Totalizer values, but modifying the values requires 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 obtain a password,
follow the appropriate
directions.
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-19
Paste the password in the Password: text box. If the password is valid, a
countdown timer displays to indicate the time remaining before the password
expires.
6-20 • Chapter 6 Working Online With a Mark VIe Component GEH-6700H ToolboxST
Modifying Totalizer Values
Once you have entered a valid password, you can modify Totalizer values. (For
assistance with Totalizer passwords, refer to the section, Totalizer Passwords.)
GEH-6700H ToolboxST Chapter 6 Working Online With a Mark VIe Component • 6-21
CHAPTER 7
Chapter 7 Finder
The Finder is a separate window in the toolbox, which contains several useful tools.
It can help you find items, such as text, overrides, differences, and variable usage
from the different types of components.
When a search is completed, the results display on the Find Results tab of the
Component InfoView. To jump directly to a location, double-click it in the list.
Anywhere finds the specified text anywhere within a searchable text string.
Begins with finds the specified text only at the beginning of a searchable text
string.
A search for matches but does not match:
abc abc xyzabc
abcde abdc
ab
bc
Ends with finds the specified text only at the end of a searchable text string.
A search for matches but does not match:
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.
A search for matches but does not match:
abc abc abcde
xyzabc
abdc
ab
bc
abc cde
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.
A search for matches but does not match:
abc abc abcde
abc cde xyzabc
spell your abc's. abdc
ab
bc
spell your abcs.
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. The ToolboxST
configuration 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.
A search for matches but does not match:
[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 var7a
var7 var
var48
var[a-zA-Z]* var var5
variable var!
varZZZZ
In the Replace With: The Replace button replaces The Find First button
text box, add the text the currently displayed Find navigates to the next
to be substituted text with the Replace With text occurrence of the Find text
Chapter 8 Trender
The Trender is a tool 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.
Note While Trender windows opened from the Component Editor are associated
with one particular component for storage purposes, they are not restricted to
trending only that component, and may be used to monitor any variables.
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.
X-Axis markers
designate alarm
and event times.
Property Editor
allows you to change
settings that affect the
capture and display of
data.
Data toolbar
contains commands
that manipulate the
current data.
User Note tab Sources tab Events tab lists Auxiliary View Mode Indicator
Traces tab allows you to save displays sources all events that contains tabs that displays the
displays traces comments, where data is have occurred display current mode
currently being instructions, and collected. during the information about (Live or Replay).
monitored by the notes about the current chapter. the current data.
Trender window. current chapter.
Create new
Trender Window
Data Toolbar
Note The buttons available on the Data toolbar may vary according to the current
trace source type.
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 static files.
While you may add as many variables as you like to a given Trender window, all of
them must come from the same type of data source. (For example, you cannot
display both live and static file variables simultaneously.)
To add traces
1 From the Edit menu in the Trender window, select Add Traces. If there are
currently no traces on the Trender, the Trender – Add Trace Wizard
Welcome screen displays. From the Welcome screen, click Next to continue.
2 From the following wizard screen, select the data type you wish to trend.
3 From the next wizard screen, select the data source from which to add the
variables to trend.
4 From the next wizard screen, select the specific component from which to select
the variables to trend.
5 From the next wizard screen, select the time period at which the variables will
trend.
Select a variable,
then click OK.
If there are already traces on the Trender, you can add additional traces from the
same component.
1 From the Edit menu, select Add Traces. The Select a Variable dialog box
displays available variables for that component.
2 Add variables from a different component by clicking the drop-down button
next to the Add Traces button.
Note You can add traces from the currently selected component or add traces from a
new component by selecting Add using Add Trace Wizard from the drop-down list.
1 If the Trender window to which you would like to add the trace is not already
open, refer to the section, Accessing a Trender Window.
2 From the Edit menu, select Add Traces. (or click the Add Traces button on
the data toolbar). If there are already traces on the trender, the Select a
Variable dialog box for the current data source displays, which you can use to
select the variables to monitor. If there are no traces on the trender, the Add
Trace Wizard displays. If there are traces and you would like to add traces for
a different live data source, you can also invoke the Add Trace Wizard by
clicking the drop-down list attached to the Add Traces button.
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, then click Next.
4 Select System Component, then click Next.
5 If you did not open the current Trender window from the ToolboxST
application, the Add Trace Wizard prompts you for the name of the system
file that contains the source component. Click the Browse button to locate the
system file, then select Next.
6 Select the component from which you wish to trend variables, then click Next.
7 Select the sampling period you wish to use, then click Next. (The sample period
represents the time in milliseconds between samples, so larger numbers result in
fewer samples.)
8 From the next wizard screen, click the Add button to display the Select a
Variable dialog box, then select one or more variables to monitor. When you
are finished, click OK in the Select a Variable dialog box, then click Finish
in the wizard screen. The newly created traces display in the Traces tab.
1 If the Trender window to contain the new trace 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 Capture Buffer /
Dynamic Data Recorder, 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.
1 If the Trender window to contain the new trace 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 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, then click Open.
6 The Select Variables wizard page displays. Click the Add button to display
the Variable Browser. The ToolboxST application 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, then
click Finish in the wizard. The newly created traces display on the Trace tab.
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 Record Data button. The Trender
returns to Replay mode.
To retrieve data from a capture buffer
A Trender window only displays one chapter of information at a time. Each chapter
maintains its own traces and 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.
Cursors
In Replay Mode 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.
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.
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 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
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.
(Refer to the section, Cursors.)
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.
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.
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.
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.
Click the Zoom In (to reduce the duration) or Zoom Out (to
increase the duration) buttons on the Data toolbar / Click on the time axis and
edit the Duration property in the Property Editor.
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 Traces tab, select one or more traces, then select the Auto-Range
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.
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 hide traces
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.
4 Click the Add button to move the statistics to the Selected list.
5 When you have finished enabling statistics, select OK.
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 Selects the
added to the output. 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.
A digital spectrum analysis of a waveform changes this time domain data into
frequency domain data, also called a frequency spectrum of the dataset. This is also
referred to as a Fast Fourier Transform (FFT).
The effect of an FFT on a sample dataset is shown below. The first is an input
dataset showing actual generator speed (RPM) and PWA accelerometer Y/Z
direction data (force in Gs).
Note The spectral analysis of this data is able to quickly isolate the most common
frequencies at which this data is varying.
Between Cursors, if set to True, applies an FFT between the left and right cursors
that can be positioned inside the graphics window.
Padding Factor provides a way to interpolate between real points with copies of
the same data, which enhances the spectrum resolution.
Remove Mean, if set to True, improves the ability to scale the data for
visualization.
Windowing Mode affects the equations used by the FFT. The following
windowing modes are available:
• None
• Hann
• Hamming
• Barlett
• Welch
The EGD Component 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
components. One adapter is created by default, and up to four adapters can be added.
1 From the System Editor, right-click an external device, then select Edit Selected
Component. (If Edit Selected Component is not available, the EGD Editor
Enable property of the component may be set to False.) 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, then select Add
Adapter.
1 From the System Editor, right-click an external device, then select Edit EGD. (If
Edit EGD is not available, the EGD Editor Enable property of the component
may be set to False.) The EGD Component Editor opens.
2 From the Component Editor, select the General tab.
3 From the Tree View, right-click the network adapter to be removed, then select
Delete Adapter.
Host Name This is the Internet Protocol (IP) host name for the selected network adapter.
IP Address This is the IP address for the selected network adapter.
Wire Speed This is the speed of the connected network.
Network Switch This is the network switch the network adapter is attached to.
Port Number This is the network switch port the network adapter is attached to.
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. The EGD Component Editor opens.)
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 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 sets configured to be available to other components on the
network.
1 From the Tree View, right-click the Produced Pages item, then select Add
Page.
2 Enter a unique name for the new page in the Page Name dialog box, then click
OK.
The following properties are available for configuration when a Produced Page is
selected in the Tree View:
Destination Category
Destination IP This sets the IP address to which the exchanges on this page are unicast or multicast. (If
Address the Mode property is set to Broadcast, this property is not available.)
Ethernet 0 If set to True, EGD is broadcast on Ethernet 0. (If more than one Ethernet Adapter has
been configured for EGD, additional Ethernet properties display.)
Mode This can be set to Broadcast, Unicast, or Multicast, depending on the modes supported
by the component’s EGD implementation profile.
- Broadcast sends the page to all EGD components.
- Unicast sends the page to a single destination.
- Multicast sends the page to the specified multicast addresses.
General Category
Exchanges This indicates the number of exchanges in the selected page. It is updated after
selecting the Build command.
Layout Mode This determines whether the exchange numbers and offsets are assigned automatically at
build time or are entered manually.
Name Use this property to rename the selected page.
Period This is the transmission period of the page in milliseconds.
Skew This 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 exchange’s skew by exactly this value
(in nanoseconds). For example, if you have three exchanges in a page and a skew value of
2, the first exchange’s skew is two, the second exchange’s skew is four and the third
exchange’s skew is six.
Note The Skew property will not be visible if it is not supported in the implementation profile
configuration.
Starting This sets the Exchange ID used for this page. Each additional exchange will be
Exchange ID incremented from the number.
Page Compression
When a page compression is performed, the variables are located in increasing size
order, starting with Booleans, then Words, Double Words, and finally all other
variables. A page compression causes an exchange major signature. Consumers can
mark the exchange variables as unhealthy until the consumed configuratuion can be
rebound.
Note To edit exchange signatures and configuration time, set Layout Mode to
Manual.
1 From the EGD tab, select the Configuration tab, then select a Produced
Page in the Tree View.
2 Right-click an exchange in the Summary View, then select Edit Exchange
Signatures and Configuration Time.
3 Review the warning about manual Exchange Signature editing, then click
OK.
4 Make any desired changes to the signatures and configuration time, then click
OK to close the dialog box.
The EGD configuration for the selected devices is loaded and the variables display in
the Summary View.
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.
Configuration Category
Data Category
Data Types This allows you to configure 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 This is set to True if the component requires that all WORD length variables
be aligned on an even boundary.
Broadcast This is set to True if the component supports broadcast destinations for EGD data or
command packets and False otherwise.
Masked Write This is set to True if the component supports the MaskedWrite command and False
otherwise.
Max Coherent Data This 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 returns the maximum number of exchanges supported by the device. It is optional
and is initialized to 0.
Max String This returns the maximum size string supported by the component. If the attribute is not
present, then the component has no set maximum size for strings. It is optional and is
initialized to 0.
Multicast This is set to True if the component supports multicast destinations for EGD data or
command packets and False otherwise.
Skew This is a Boolean value representing the capability of the producer to support the skewing
of produced exchanges with respect to time.
Unicast This is a Boolean value that is set to True if the component supports unicast destinations
for EGD data or command packets. Otherwise, it is set to False.
General Category
Device Class This is 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 Name This is the name of the class of device to which this device belongs
The generic editor uses CMP to display live data values on a produced or referenced
device summary grid view. The Connection Toolbar button sends the CMP message
to the device to obtain the data.
Due Time is the time that a consumer data packet must be received for an exchange
to remain valid.
Length is the value for a produced exchange. This length may be the highest
variable offset in the exchange or the highest offset of a variable, which may have
been removed. For a consumed exchange, the value may be the highest variable
offset used or the length of the produced exchange, depending on the bind algorithm
of the individual tool.
Missed Count is the number of data production packets missed since initialization.
A missed packet occurs when a data production message is received that has a
request ID greater by more than one than the last message received (accounting for
counter roll-over).
Refresh Errors are the number of times a refreshment fault has occurred. A
refreshment fault occurs when a subsequent data production packet (or initial packet
at startup time) does not arrive at a consumer within a pre-defined update period.
Note The EMT provides a detailed view of the configuration server contents.
The Filter Toggle button defaults to a filtered state. It displays items that have
the same name but have a different Producer ID as the open component.
The Delete button deletes the selected item(s). If the item(s) were saved as part
of the configuration, they can be added again.
The EGD configuration server uses the producer ID to store all the documents for an
EGD node.
If you open two systems, then point to the same configuration server and save a
device of the same name with two different producer IDs to that server, you can end
up with two producer ID nodes with the same device name.
Edit Undo Remove the item currently selected in the Tree View
Redo Add a new component to the current system
Cut Cut the selected item in the Tree View
Copy Copy the selected item in the Tree View
Paste Paste the copied item in the Tree View into the Summary View
Delete Display the System Information Editor (refer to the section System Information
Editor)
Find Display the Component Editor for the item currently selected in the Tree View
View Go Forward Return to the view that immediately follows the current view in the history.
EGD Management Open the EGD Management Tool screen.
Tool
Device Online Send CMP messages to EGD Class 2 or higher devices to view live values from
the device.
Bind and Build Refresh 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 Store the current EGD configuration to the System Database (SDB). It is only
available if the system has an SDB enabled and configured.
Help Release Notes Display the release notes for the current version of the application.
About Display version and copyright information about the application.
Chapter 10 Configuration
Management System (CMS)
• CMS server
• Stand-alone Client is accessed through the Start menu
• Integrated Client is accessed through the ToolboxST* application
CMS Server
CMS Stand-alone Client
The CMS Server software
manages and tracks configuration Separate application
changes on a ToolboxST system CMS Client Functions accessed from Start menu
CMS Overview
• Establishes a security model for the server. CMS security uses Windows
(Domain or Workgroup) security for user authentication (CMS users must exist
as valid domain or workgroup users).
• Creates (or deletes) a master location, called the repository. The repository is a
place where configuration files are stored and maintained. All change revision
history is maintained in the repository.
• Adds (or deletes) CMS user names and privileges to control access to the
systems in the repository.
• Provides a mechanism to Backup and Restore the Repository. The backups
include revision history for all the ToolboxST systems in that repository. User
information for the repository can also be included or excluded from the backup
copy.
• Starts and stops the CMS server application.
The CMS client applications (Stand-alone and Integrated) perform the following
functions:
The CMS server uses a repository to track system changes, and to control client
access. Each repository contains a list of CMS users and permissions for the
repository. The repository maintains the revision change history for ToolboxST
systems that are added to the repository. A CMS server can have one or more
repositories, and each repository can contain one or more ToolboxST systems.
1 Place the CD in the CD-ROM drive. The installation starts automatically. The
Setup dialog box displays.
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.
5 Click Next. The Destination Folder dialog box displays. If this is the first
time the ToolboxST application has been installed on this computer, the Browse
button allows you to change the default install location (C:\Program
Files\GE Energy\). If this is a subsequent installation, this dialog box
displays where this version of the product is installed.
6 Continue to click the Next until the installation starts. Click Finish when the
installation has completed successfully.
CMS uses Windows security (domain or workgroup) for authentication. All CMS
user names must exist in Windows (domain or workgroup) before they can be added
in the CMS server.
For workgroup security, the CMS user names only need to be added as Windows
users on the CMS server computer (users do not need to be added on all CMS client
computers).
For domain security, the CMS user names must be added by the domain
administrator if they do not exist.
1 From the Start menu, select Control Panel, Administrative Tools, and
Computer Management. The Computer Management screen displays.
Enter a
Password,
then re-enter
it to confirm.
Select any of
these options,
if necessary,
then click the
Create button.
Note When creating accounts specifically for CMS use in a workgroup, select the
options User cannot change password, and Password never expires.
1 From the Computer Management screen, right-click the new user and select
Properties. The Properties dialog box displays.
Select the
Administrators group
and click Apply and
OK.
If the Members Of
tab is blank, click the
Add button.
Select
Administrators
then click OK.
The dialog box closes and the previous Select Groups dialog box displays again, with the Administrators group
displayed in the object name text box.
2 Click OK. The User Properties dialog box displays again with the Member
Of tab selected.
3 From the Member Of tab, select the Administrators group, click Apply and
OK.
1 From the Start menu, select All Programs, GE Control ST, and CMS
Server. Click Administrator Tool.
When the CMS Administrator Tool is started for the first time, the CMS Settings
dialog box displays.
If there are any existing repositories with current user types, use this dialog box to
back up all existing repositories in the CMS server.
The repositories
to be backed up
display in the list
box.
2 Enter a Name and Password, then click OK. The CMS Administrator
dialog box displays.
3 Select the Create a new Repository option and click OK.
4 The Create New Repository dialog box displays. Enter the path or click
Browse to find the repository location. To create a new repository folder, click
Browse to open the Browse For Folder and select Make New Folder.
5 Enter the folder and the name of the repository and click OK. The CMS
Administrator screen displays.
• Repository working folders are the root folder location for systems from the
repository
• System working folders have a folder location for each system configuration
added to the repository, or obtained from the repository.
Note Working folders are specific to a particular user. Different users cannot
designate the same working folder.
If a user attempts to use a working folder already selected by another user, the
following message displays:
CMS maintains a list of users and their repository working folders on each computer.
The repository working folder for a user is only shown in the CMS Stand-alone
client (with repository name selected).
• If the user is adding the system to the repository, that user’s system working
folder is set to the current location of the system configuration.
• If a new user performs a Get Latest command on a system that was not added by
them, the system working folder defaults to a location under the repository
working folder (and the Get Latest command places a copy of the system
configuration in that location).
The user’s system working folder is shown in the Stand-alone client when a system
name is selected.
For the Integrated client, the current folder location of the system (.tcw file) is
assumed to be the working folder for that user. The CMS logon fails, and an invalid
working folder dialog box displays if a different user is associated with the system in
that location.
• A copy of the system is placed in the repository. This serves as the starting point
to begin CMS revision tracking for all CMS users.
• The user’s system working folder is set to the current location of the system
configuration.
• Changes are made to the system in the system working folder for use by CMS.
A CVS folder (hidden) is added at the system level and in each component
in the system
System and component configuration files (cf.dat and .xml ) are made Read-
only
Once a system configuration is added to the repository, any user can log on to the
CMS Server to begin using CMS . After log on, the user obtains the current copy of
the configuration (Get Latest), modifies a component (Check Out), then saves the
changes (Check In).
Note The first time you log on to the CMS stand-alone client, you must set the
working folder.
The Component
View displays all
components within
the system that is
currently selected in
the Systems View.
User comments
User that made the change.
entered at check in.
Label is
additional text
to identify a
specific
version.
Sequential
version
numbers
assigned to
each change at
check in.
Get Latest Files, when set to True, gets the latest version upon logon.
Work Local, when set to True, opens the system disconnected from the CMS
server. This is the default when the ToolboxST application is installed, and opens the
system without the CMS Integrated client.
Work Local, when set to False, opens the system connected to the CMS server, and
displays the CMS LogIn dialog box.
Note You must connect to the correct CMS server to log on.
Note The CMS LogIn dialog box does not automatically display unless the
ToolboxST Work Local option was set to False.
If you clicked Cancel, you are not logged into CMS. One of three scenarios occurs,
depending upon your local ToolboxST settings.
1 From the ToolboxST CMS menu, click Connect to Server. The CMS –
Server Details dialog box displays.
2 When the CMS – LogIn dialog box displays, enter your User Name (if not
displayed), Password, and Repository, then click OK.
Note If a question mark icon displays next to the system item in the ToolboxST
System Editor Tree View, perform a Get Latest Version.
The Tree File Importer is a companion application that converts software tree files
from the Control System Toolbox application to the new .xml file format used by the
ToolboxST application.
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 the ToolboxST application, 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. (The ToolboxST application
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, 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. Refer to the section, Running the Tree File
Importer.
4 From the ToolboxST System Editor, open the controller and add a reference
to the libraries that were imported in Step 3.
5 Exit the ToolboxST application and return to the Tree File Importer. Select
the system and device you created in Step 2, then select the project file from
Step 1 to import the function tree files.
Note Information from Control System Solution toolbox system files (files ending in
.syb) are not imported. This includes scales, enumerations, and resources. Use the
toolbox SDB browser to display this information in the ToolboxST system
information editor.
5 After reviewing the log, click Next to save the updated system and complete the
wizard.
6 Click Finish to exit the wizard.
Several I/O functions are available with the Mark VIe component as follows:
• Valve calibration
• Multicasting
• Configuring an enabled analog I/O module
• Configuring PROFIBUS communications
• Retrofiting a Mark Ve component
9 Click the Calibration Mode button to enable all command buttons and to start
the calibration command in each I/O pack. A Trender window displays dynamic
signals.
Note Do not make any changes to the regulator configuration during valve
calibration. Each calibration command is monitored by the ToolboxST application to
verify performance.
1 Click Minimum End to stroke the actuator to the minimum end position.
2 Click Fix Minimum End to read the voltage at the minimum end position.
3 Click Maximum End to stroke the actuator to the maximum end position.
4 Click Fix Maximum End to read the voltage at the maximum end position.
5 Click Calibrate to use the calculated values.
6 Click Save to save the calculated values.
Note Only one command state can be active at any one time.
Verification commands, which are not performed in any sequence, are as follows:
Note LVDT voltages are the values that represent the minimum and maximum
actuator positions stored in the I/O pack. These values are not live data. They display
after the Save button is selected.
Availability
This function is available with the following packs:
Multicasting
A ToolboxST function called power load unbalance (PLU) allows you to configure a
multicast connection between a PGEN I/O pack and a PDOA I/O pack on the same
IONet.
To configure multicasting
From theSelect
Type: list, select
PGEN, then
click Next.
Availability
This function is available with the following packs:
Availability
This function is available with the HART Enabled Analog I/O (PHRA).
Note Only one I/O pack can be actively communicating with its associated
PROFIBUS network.
Select the
PPRF module,
then click Next.
If the Module
Required check
box is selected,
the module must
be present and
functioning for
the controller to
go online.
Click Next to
preview
configuration
information.
1 From the Component Editor Tree View, right-click the Distributed I/O
item, then select GSD Manager.
Note The GSD Manager is not available until a PPRF module has been added.
Slave device
Slave Device
view
4 From the Device view, insert the slave device into the network by selecting and
dragging the device to the purple-colored line in the PROFIBUS Network
view.
Note Any changes made in the PROFIBUS Network tab cannot be undone through
the ToolboxST Undo option under Edit.
If a change is made,
click the Apply
button, then click
OK to return to the
Hardware tab.
Note If any changes are made to the slave device configuration and the OK button is
clicked, the pack is restarted after the controller and pack are downloaded.
Click to enable
Watchdog Control,
which allows this device
to enter fail-safe mode if
an error occurs. The
Interval is the time period
that elapses before fail-
safe mode. The default
time interval is 200 ms.
Click theOK
button to return
to the Hardware
tab.
Select a
parameter,
then use the
drop-down
list to set
the value.
Click the OK
button to
return to the
Hardware
tab.
6 From the Tree View, click the Groups item to add the slave device to an I/O
group.
For descriptions of
values, click the
Help button.
8 From the Tree View, click the DPV1 item to display the screen below.
Note This screen is only active if DPV1 is supported by this device, but this feature
is not supported by the PPRF.
Click the OK
button to return to
the Hardware tab.
For detailed
information, click
the Help button.
10 From the Tree View, click the GSD item to display the contents of the GSD
file(s).
Select a master
device profile from
the drop-down list.
Bus Parameters
displays PROFIBUS
network properties.
Bus Monitoring
displays how the
PROFIBUS network
will be monitored by
the gateway.
Note If any changes are made to the master device configuration and the OK button
is clicked, the pack must be restarted after the controller and the pack are
downloaded.
PROFIBUS slave
addresses are
changed here.
The Variables data grid displays the PROFIBUS configuration, which is defined as a
number of module input and output bytes or words. By default, slave inputs are
followed by slave outputs. Successive rows may be grouped as necessary to create
actual point values that span multiple rows. Packed Boolean values are expanded
into a separate data grid as shown so that Boolean MarkVIe variables can be attached
to the individual bits. The Variables tab contains the following columns.
Var Data Type displays the data type of the variable configured in the MarkVIe
component. Space can be reserved for unused inputs and outputs, enabling
subsequent online loads when variables are added.
Fieldbus Point Data Type displays the data type of the slave device I/O point. If
the size of the point spans multiple rows of input or output bytes or words,
subsequent rows display Continued. The default byte data type for rows associated
with configuration bytes must be changed to a supported data type shown in the table
below.
Raw Min, Raw Max, Eng Min, and Eng Max are values used to calculate scaling
from raw units (the PROFIBUS point) to engineering units (the MarkVIe variable).
Boolean transfers are expanded into individual bits and displayed in the Booleans
tab below the Variables tab.
Input Event Enabled, if set to True, enables input event scanning on a Boolean
transfer.
Note Any field except Var Data Type and Fieldbus Point Data Type It can be
modified without restarting the controller or I/O pack.
Note The connected variable may be added, changed, or removed and loaded
without restarting the controller or I/O pack.
The values that display in the Standard Diagnostics tab are the standard portion of a
PROFIBUS diagnostic message (the first six octets). Except for the Master_Addr
(master address) and Ident_Number (identification number) values, which are UINT
types, the remaining values are BOOL types. The connected values must have
matching data types.
Note The last value in the Standard Diagnostics tab, Station_Diagnostic, is not part
of the PROFIBUS standard diagnostic message. It provides a station diagnostic
present indication. It is set to True if the slave device generates a non-status only
diagnostic. For applications that require station diagnostic presence indication, attach
a defined Boolean-type variable to the Station_Diagnostic.
The Device Diagnostics tab, which is initially empty, is used to connect variables to
data fields within the Device-related portion of a diagnostic message. Entries in the
Diagnostic Byte Off, Diagnostic Bit Off, and Diagnostic Number Of Bits columns
identify bits, bit fields, and analog values within the Device-specific diagnostic,
which is exclusively defined on a per-device basis.
Note The I/O pack must be restarted if lines are added or removed from the Data
Grid, or if an existing entry’s connected value is changed from a Boolean to an
analog-type or vice versa. All other changes to existing entries can be made and
downloaded without restarting the controller or I/O pack.
Note To add a line without specifying the connected variable, you must enter a
space in the Connected Variable field to enable the other fields for data entry.
Note If lines are added or removed from the Data Grid, the I/O pack must be
restarted after being downloaded. Existing Data Grid modifications (adding,
removing, or changing connected variables, changing the Identifier Number and
such) can be downloaded without restarting the controller or the I/O pack.
Note To add a line without specifying the connected variable, you must enter a
space in the Connected Variable field to enable the other fields for data entry.
Channel Diagnostics
The Data Type for the The Identifier Number The Channel Number
Connected Variable must range is 0-495. range is 0-63.
be an UINT. .
Note If lines are added or removed from the Data Grid, the I/O pack must be
restarted after it is downloaded. Existing Data Grid modifications (adding, removing,
or changing connected variables, changing the Identifier Number and such) can be
downloaded without restarting the controller or the I/O pack.
Note To add a line without specifying the connected variable, you must enter a
space in the Connected Variable field to enable the other fields for data entry.
Note The system must be running, and the ToolboxST application must be able to
connect to the Mark VIe component.
Availability
This function is available with the PROFIBUS Master Gateway (PPRF).
Mark Ve Retrofit
The Mark Ve PMVE control I/O pack (based on the UCSx processor board) is an I/O
subsystem that communicates and controls one or more I/O agents across the high-
speed serial link (HSSL). The PMVE currently supports the MVRA and MVRF
boards in a TMR configuration, as well as an MVRC board in a simplex
configuration. Refer to GEI-100689, PMVE Control I/O Pack.
Availability
This function is available with the Control I/O Pack (PMVE).
The CANopen node-id and the device Click the ellipsis button in the
number are the same. For example, if a Connected Variable column to
GS6 fuel valve is attached to Device 2, display the Select a Variable
Variables tab dialog box and add a variable.
the CANopen node-id number is 2.
Note Each configured PCNO module supports up to five GS16 or GS6 fuel valves.
CANopen devices cannot be mixed.
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.
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
application 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 application, it is a data type for logical signals.
bus
An electrical path for transmitting and receiving data.
byte
A group of eight binary digits (bits) operated on a single unit.
collection
A group of signals found on the same network. The Trend Recorder can be
configured by adding collections.
configure
To select specific options, either by setting the location of hardware jumpers or
loading software parameters into memory.
designated controller
In a Mark VIe dual controller system, the designated controller (DC) is the controller
to which the I/O packs listen for outputs when they have the option to listen to
multiple controllers. In a TMR system, the DC is the controller that initilizes the
other controllers.
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 application for searching and determining the usage
of a particular item in a configuration.
firmware
The set of executable software that is stored in memory chips that hold their content
without electrical power, such as 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.
health
A term that defines whether a variable is functioning as expected.
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.
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.
node
In a local network, a component that is connected to other components and is capable
of communicating with other network devices. In a tree structure, a location on the
tree that can have links to one or more nodes below it.
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 application 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.
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.
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.
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.
Rubber block
A block that can extend to include a variable number of pins.
runtime
See product code.
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 application that monitors and graphs signal values
from a controller.
validate
Makes certain that items or devices do not contain errors and verifies that the
configuration is ready to be built into application code.
variable
The basic unit for variable information. Variables are the placeholders for memory
locations in the toolbox’s different platforms.
word
A unit of information composed of characters, bits, or bytes. It is treated as an entity,
and can be stored in one location. Also, a measurement of memory length, usually 32
bits in length, but can also be 4, 8, or 16 bits long.