Ge Energy: Toolboxst User Guide
Ge Energy: 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: 090415
Issued: 070511
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 10-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 is the recommended hardware and operating system requirements
needed to run the ToolboxST application.
Recommended
CPU 2.8 GHz Pentium (or faster)
OS Windows® XP Professional
Memory 3 GB RAM (or more)
HD 40 GB (or more)
Video 1280 x 1024 x Truecolor (24 million or better)
Drive DVD
Network Ethernet 10/100 mb
USB Two available USB Ports
Note Windows 2000 Professional is supported for legacy systems only. Windows
Server 2003 is supported using a single user configuration. Windows 64-bit
Operating Systems are not supported.
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.
Note The WorkstationST Alarm Viewer can be installed by itself for use on a
remote computer.
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.
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
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.
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.
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.
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.
ToolboxST c:\MySystem.tcw
/archive:c:\MyArchiveFolder\MySystemArchive.zip
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.
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.
1 Install the ToolboxST application (refer to the section, Installation (on page
2)).
2 Plug the UPD into any empty USB port on your computer.
Only one UPD may be installed at a time. If you have valid licenses for more than
one product, your UPD must contain a valid application key for each product.
Note If you install the UPD before installing 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.
To make sure that the UPD is correctly installed and your ToolboxST installation is
correctly licensed, start the application. If the installation is not correct, the following
dialog box displays.
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
Warning NTP Diagnostics – Yes
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.
Optional procedures:
• If the External Device requires a specific configuration file, select the Doc
Path item and provide the location of the file.
• If the External Device application requires switches (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.)
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.
Library Container Folders are created for each library container in the system. In
the example system, the library container named Libraries is stored in a folder
correspondingly named Libraries. Objects in this folder include:
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.
Controller Backup Option determines how controller backup files are handled in
the Build and Download commands, as well as the status control.
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
Information Editor)
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.
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.
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.
Note The second Language option must be selected in the System Editor Property
Editor.
1 From the System Editor Tree View, double-click the system item. The
System Information Editor displays.
Note The Export Product Diagnostics option creates a .csv file that contains
diagnostics for all I/O packs installed on this computer. The default file name is
All_Product_Diagnostic Translations.csv. It can be opened in Notepad or in an .xml
spreadsheet.
2 From the Tree View, right-click the Diagnostic Translations item to select
the .csv file just created.
Note Selecting the Diagnostic Translations item exports all pack items beneath to a
single .csv file. However, if an individual pack is selected, the diagnostics for that
pack only are exported.
Validate Diagnostics
If you are using CMS, perform a Get Latest for all controllers on your computer. The
Validate Diagnostics option verifies the I/O packs attached to a particular system,
then checks to see that a translation has been entered for each I/O pack in the list of
required packs.
Any errors or warnings occurring from the Validation display in the Component
InfoView. Double-click an error or warning to be connected to that diagnostic.
The Validation option applies to all translations entered into a system. Even if you
have Common selected when you start to validate, all translations are validated.
Warnings and errors do not prevent controllers from running the Build and
Download commands, but rather ensure that all second-language diagnostic text
displays correctly at run time. If there is no second-language translation for a
particular diagnostic, the text displays in English. .
Delete Diagnostics
Only I/O packs used on your job need to have translations entered. Unused I/O packs
can be selected from the Tree View and deleted. You have the opportunity to cancel
the Delete command before it’s performed. However, once it’s performed, it cannot
be Undone.
Note This command only deletes these translation records. If a diagnostic occurs
whose translation record was deleted, it still displays in English.
1 From the Tree View, select a pack, add the translated text in the Second
Language Message Text column, then click Save.
2 Open all controllers that use the I/O pack with the missing translation and
perform a Save command.
From the
WorkstationST
component Tree
View, select the
General tab and
the General item.
Or
Note When you select Use Second Language from Regional Settings, that becomes
your permanent default setting, regardless of what is configured in the General tab in
the ToolboxST application.
The WorkstationST Alarm Viewer provides a means to override this setting. For
more information, refer to GHT-200009, How to Configure a Second Language for
the ToolboxST Application and HMIs.
The option Select Active Measurement System allows you to specify either English
or metric measurements. Refer to GHT-200016, How to Configure a Measurement
System for Use by ControlST HMI Applications.
To configure 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.
Different views of HMI screen files can be obtained by selecting any one of the
WorkstationST component items in the Tree 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.
3 From the Open file window, select the screen file or files you wish to add, then
click Open.
4 The screen file(s) is added to the system and displays in the Summary View.
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.
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.
4 From the Summary View, right-click to select Download selected HMI
screens from the short-cut menu.
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.
The process of editing an HMI screen file is different, depending on whether CMS is
enabled.
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
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.
Note The system file is NOT the one used by the CIMPLICITY application, rather,
it is the one stored in the HMI screens directory that also stores the .tcw 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.
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, 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.
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.
A Second Language
must be selected before
diagnostic text can be
translated in the System
Information Editor.
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.
Remote computer
CIMPLICITY CimView/
Communication CimEdit
Processes
Authentication UI
- Right-click allows for logon
or change of user (logout /
logon)
Get Current User * - UI displays to request
logon if users are configured
and a user is not already
logged on.
-The current user and role
display
ToolboxST
Tray Icon
Security Login Get Current User *
Logon Changed Application
Intercom Message **
WorkstationST
Get Current User *
Alarm Viewer
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.
The user selected replaces the current user. The previously defined user privileges
take effect.
The user Maint is now logged on over the current user (or now sub-user) operator.
The previously defined user privileges for maint take effect.
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.
Logging Off
To log off the Current User
Right-click the WorkstationST or SecurityST icon in the taskbar notification
area to display the shortcut menu.
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 WorkstationST
Component Editor
Creation Wizard
WorkstationST components are created from the System Editor by using the
WorkstationST Creation Wizard screen.
To create a component
From the System Editor Tree View, right-click the system name and select
Insert New from the shortcut menu.
The WorkstationST Component Editor displays in the Tree View and in the
Summary View.
The Component
InfoView displays specific
feedback information
about 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
WorkstationST 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.
Each time a Build command is performed, the Log tab is updated with current errors,
warnings, and general information. Concurrently, with each Build command, a file is
generated in the component folder that reflects the contents of the Log tab. This file,
called Build.log, remains until the next Build command then is updated.
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.
Windows, and then runs as a tray icon . When a warning or error occurs with
the WorkstationST Service or any configured feature, an error icon
displays .
Note When the WorkstationST Service starts, it attempts to start all configured
features, and to keep the features running. If a feature is stopped from the Status
Monitor, WorkstationST Service will not attempt to restart it. If the feature is started
again from the Status Monitor (or WorkstationST Service is restarted), the feature
starts again.
Information displays for each configured feature. The WorkstationST Service runs a
System Data Interface (SDI) server. The Status Monitor uses an SDI client to obtain
the information displayed. Information is not available when the WorkstationST
Service is not running.
Click the Details tab to display Place the cursor on each column
additional details. header to display a column data tooltip.
Specify Remote Host allows you to display NTP service status on a remote
computer (the local computer is the default display).
Data Logging displays a dialog box that allows you to log the Status Viewer’s data
to a log file.
When the Alarm Server feature is selected in the WorkstationST Status Monitor, the
server status displays with the Alarm Server Status menu item.
Select the Alarm Queues tab to Click any ellipsis button to display
display alarm queue information information for the selected queue.
from the Alarm Server.
Alarm Server Hostname is the hostname on the local computer (default) that has
the Alarm Server enabled.
Save Status to Text File allows you to save the current Alarm Server status to a
text file.
This menu option allows you to copy the selected WorkstationST Status Viewer list
to the clipboard.
Advanced Menu
View Detail Log allows you to display detailed events for the selected feature.
Save and Zip all feature logs allows you to save configured log files to a
specified zip archive.
• 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.
Protected Objects
Specific actions governed by each access right depend on the specific component
type. Examples of protected objects are:
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.
Alarm and event information displays by using advanced filtering and sorting
capabilities, as well as functions such as Acknowledging, Locking, and Silencing
Alarm and Events. Refer to GEI-100620, WorkstationST Alarm Viewer, for detailed
information.
Alarm Server To Use allows you to select the WorkstationST currently running
the Alarm Server to get alarms.
Name reflects the name of the current controller as set in the System Editor. It is
read-only in the WorkstationST Component Editor, and must be changed from the
System Editor.
Modify Data allows you to modify data values and force variables.
Minor Revision is the time that the last WorkstationST Build command was started
after a minor component change. When a minor change is made, the revision is set to
zero until a Build command starts.
Web Access, if set to True, allows the WorkstationST Web server to interact with
Web clients.
Active Diagnostics Severity defines the OPC AE severity value for a diagnostic
alarm in the active condition. This value is used for display purposes on the
WorkstationST Alarm Viewer.
Normal Diagnostics Severity defines the OPC AE severity value for diagnostic
alarm in the normal condition. This value is used for display purposes on the
WorkstationST Alarm Viewer.
Config Path defines the path for downloading the WorkstationST runtime
configuration.
Configuration Manual Override overrides the system NTP settings, and uses
local WorkstationST component settings only.
Site Time Reference Option specifies the method that this WorkstationST
computer uses to synchronize to a time source, either another computer or a Time
Server, outside the system configuration.
To schedule a task
Task Description
(optional)
Specify an optional
end time.
Host Name is the Internet Protocol (IP) host name for the selected network adapter.
IP Address is the Internet Protocol address for the selected network adapter.
Redundant, if set to True, indicates that the adapter is part of a redundant pair.
Wire Speed is the speed of the network to which the selected adapter connects.
Network sets the network connected to the selected adapter. (Available networks
are determined in the System Editor.)
Subnet Mask controls the significant portions of the IP address. (This property is
usually unavailable; for I/O networks, the subnet mask is always a fixed value, and
for other networks defined at the system level, the subnet mask is configured in the
System Editor.)
Network Switch is the network switch device to which this network adapter is set.
Port Number is the network switch port to which this network adapter is
connected.
Backup Network Switch is the backup switch for this network connection.
Backup Port Number is the network switch port to which the backup port is
connected.
On Site Monitor
The On Site Monitor (OSM) feature of WorkstationST supports the Universal OnSite
Monitor (UOSM). The UOSM is a standalone computer that serves as a gateway to
the customer’s system data, which is used by GE’s Maintenance and Diagnostic
(M&D) group to detect and diagnose system problems.
The OSM collects system configuration data from the WorkstationST Config Reader
and writes data files for the UPC (Universal Product Code), which communicates
with the M&D group. The OSM provides realtime data using the WorkstationST
OPC DA Server.
To enable OSM
2 From the drop-down list, select True to enable the On Site Monitor.
During system startup, the Network Monitor determines where the devices are
physically connected. During normal system operation, changes in network topology
should not occur, therefore, any changes would indicate an abnormal condition. For
example, devices may be incorrectly reconnected after a network switch is replaced
or new network cables are run. This feature is also an important debugging tool
because it allows network issues to be spotted or ruled out very quickly. The
Network Monitor also enhances network stability and security by providing alarms
in the event of an unauthorized connection to the network.
ToolboxST System
Overview Screen
Computers, Controllers, Network Monitor Service
Network Switches...
Network Monitor Network
Data Client Monitor Data
Device Status Connection Client
Monitor threads
Network Monitor
Data Client Network Status Display
Connection Utility
Alarm Queue
Network
Network Monitor
Monitor Data
Alarm Client
Client
connection
WorkstationST Alarm
Viewer
Alarm Server
Alarm Client
Network Alarm Client
Connection
Monitor
Alarm Client
The system network drawing displays all physical networks, as well as network
switches and devices, their physical locations, and their interconnection. The host
name and IP address of each device network connection on a per network basis, as
well as the switch and port where the physical connection is made is also provided.
This information is entered for the network switches and devices as they are added to
the system in ToolboxST.
1 From the System Editor Tree View, right-click the system name and select
Insert New from the shortcut menu.
The Summary View in the ToolboxST System Editor displays all system devices and
their simplified connections to the defined networks. It also displays the composite
health of the connection of each device to each network by displaying healthy
connections with a green line and unhealthy connections with a red or orange line.
An example of a
network error
An example of a
healthy network
The Network Status Viewer allows you to troubleshoot network issues down to the
device level. This utility retrieves status data from the Network Monitor.
The Network View tab displays the network hierarchy; the networks are the top-level
items. The switches are at the next level, followed by the devices.
The Device View As Configured tab displays the devices in their configured
locations, as well as deviations of the device connections from their configured
locations. This is used to find occurrences of a device connected to the wrong port
that is masking the location of an offline device, but configured to be connected to
that port.
The Device View By Connection tab displays the actual location of each device’s
switch and port.
The alarm scanner option scans variables from the OPC DA server running on the
local workstation, and generates alarms and events based on the variable
configuration.
1 From the Tree View, select the Features item. The available features display
in the Summary View.
2 In the Summary View, enable the Alarm Server by selecting True. The
Alarms tab displays, and the Alarms configuration form also displays in the
Summary View.
The tables below describe the configuration properties and values of the Alarm
Server.
Send Alarms to If True, sends alarms to the CIMPLICITY alarm manager, if False, disables the
CIMPLICITY sending of alarms.
Disk Category
Disk Cleanup Enabled If True, all files in the Historical Alarm Path directory are deleted if the file age
exceeds the value specified in Historical File Age. If False, the files are left on disk.
Historical File Age Indicates the elapsed time in days from when the file was last updated. The default is
30 days.
General Category
Automatically Reset If True, an acknowledged alarm in the normal state is automatically reset. If False,
Acknowledged Alarms select and reset the alarm manually.
Emulate CIMPLICITY and If True, the Alarm Server maintains event queues and manages events the same as
Sequence of Events (SOE) alarms. This allows the WorkstationST Alarm Viewer to emulate CIMPLICITY alarm
behavior view behavior.
Enable Controller If True, controller and pack diagnostics are logged to the historical alarm log. If False,
Diagnostic Alarm Support pack and controller diagnostics must be retrieved using the ToolboxST application.
Historical Alarm Path The path used to hold the historical alarm data files written by the Alarm Server.
Historical WorkstationST If True, the Alarm Server writes the WorkstationST style of alarm data into the
Alarms Enabled Historical alarm path. The file extension used is .bin. The default value is True.
Alarm Printer The name of the printer to be used by the alarm server for printing alarms. The format
of the name must be \\ServerName\PrinterName if it is a network printer or just the
printer name if the printer is local to the computer.
Alarm Printing Enabled If True, activates the printing of alarms received by the WorkstationST runtime. The
Alarm Printer and Print Device Configuration must be defined.
Print Device Specifies one or more devices in the system from which alarm data is received and
Configurations printed. Alarm information is printed to the printer configured in Alarm Printer.
Print Queue Limit The maximum number of alarms allowed in the internal alarm manager queue to be
printed. Any alarms received after this limit is reached are discarded.
Alarm Scanner
The alarm scanner periodically scans the values of the configured variables. Based
on the conditions of the variables, an alarm and/or an event is generated.
Note Each OPC AE server must be installed and configured before you add the
server to the list and get the published categories/condition names.
When an OPC AE server is added and selected in the Tree View, the data grid
displays the translation of each event category/condition name published by the OPC
AE server. Additional properties are available in the property grid display. These are:
General
Enable Connection To If True, the alarm server uses this configuration to process alarm/events from the external
Server server. If False, the configuration is preserved but NOT used.
OPC Server Time Units These specifies how to interpret the time stamps coming from the AE server. The choices
are UTC Time or Local Time.
Enable Simple Events If True, consumes and translates these OPC AE simple events to an EVENT type. If
False, ignores all simple event types from the server.
Simple Events Alarm Class This is the alarm class to be used by the WorkstationST Alarm Viewer for the display of
color for this event.
Enable Tracking Events If True, consumes and translates these OPC AE tracking events to an EVENT type. If
False, ignores all tracking event types from the server.
Simple Events Alarm Class This is the alarm class to be used by the WorkstationST Alarm Viewer for the display of
color for this event.
In the Outline View, set the Enabled property for the HMI feature to True. The
HMI Config tab displays.
HMI Screen Files are listed in the Summary View, and when selected, are those
used by this HMI.
HMI Graphics without a Project, if set to True (the default), requires you to
define the CIMPLICITY project file path, if CIMPLICITY 7.x is being used.
CIMPLICITY 7.x allow you to view and edit screens with a direct connection to
WorkstationST Services. This eliminates the need to synchronize a CIMPLICITY
project database. Refer to GEI-100697, WorkstationST CIMPLICITY Advanced
Viewer Integration.
Auto Download Screen Files enables the automatic download of HMI screen
files when the master screen files change.
Screen Editor overrides the default editor, which is based on the screen file
extension.
Screen File Path overrides the default local screen directory.This path can be
absolute or relative. When relative, it is based on the location of the CIMPLICITY
project (defined in the Project File Path). If the screen file path is blank, the default
screen file path is \screens, relative to the project file path parameter (for example, if
the project file path is c:\site\cimproj, the screen file path is c:\site\cimproj\screens.)
Note If the HMI Graphics without a Project property is set to False, Global Project
Parameters displays in the Tree View and the following properties display in the
Property Editor.
Project File Path is the location and file name for the CIMPLICITY project into
which data will be imported.
Set Point Audit Trail enables CIMPLICITY to send information to the Event Log
about user-defined setpoints.
Override Use Second Language is used to override the Use Second Language
property in the WorkstationST General tab when importing into CIMPLICITY. If the
override is False, the Importer follows the setting in the General tab. If the override
is True, the HMI Importer always imports the primary language description into
CIMPLICITY.
Global Parameters
Global System Parameters are user-defined, system-level global parameters that are
imported into a CIMPLICITY project. Global Project Parameters are user-defined,
project-level global parameters that are imported into a CIMPLICITY project.
1 From the Tree View, select either Global System Parameters or Global
Project Parameters.
2 In the Summary View, select the parameter to edit.
1 From the Tree View, select either Global System Parameters or Global
Project Parameters.
2 In the Summary View, select the parameter(s) to delete.
HMI Screens
HMI screen files are managed from a master location and downloaded to the HMI
WorkstationSTs. These screen files can be managed from either the System Editor or
from any of the HMI WorkstationST components that use them. HMI screen file
management consists of the following functions:
• 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 CMS or from the Master location if CMS is not
enabled)
If the CMS is enabled for your project, certain operations are restricted based on
whether or not files are checked out of CMS. The affected operations are as follows.
• The System must be checked out to add and/or delete HMI Screens (only from
the System Information Editor)
• The System must be checked out to edit the use of screens by any HMI
WorkstationST.
• Only the HMI screen file need be checked out to edit it.
Various CMS commands can be performed on individual HMI screen files when
CMS is enabled for the project.
Note The options depend on the CMS state of the HMI screen file selected.
Note When starting an edit session of an HMI screen file, you are prompted to first
check it out.
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.
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.
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, select HMI Screens Files.
3 From the Summary View, select one or more HMI screen files.
4 From the Summary View, right-click to select Download selected HMI
Screens from the short-cut menu.
The Download WorkstationST wizard displays the items that can and need to be
downloaded. A scan is done automatically, with the parts that are not equal being
selected for download.
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.
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.
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 the Summary View, select an HMI screen file.
4 From the Summary View, right-click to select Edit selected HMI Screen
from the short-cut menu.
The edit dialog box that displays depends on the state of both the master file and
your system file.
Note The system file is NOT the one used by the CIMPLICITY application, rather,
it is the one stored in the HMI screens directory that also stores the .tcw 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.
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, 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 OPC DA Server receives Ethernet Global Data (EGD) from all EGD-referenced
devices consumed by the workstation (refer to the section General Tab). The OPC
DA Server provides live, timestamped data. Write access allows you to write to
variables. These writes are channeled to the EGD devices through EGD Command
Message Protocol writes. The OPC DA Server can also own variables defined under
the OPC DA Server Variables area, or in the OPC DA client. The OPC DA Server
has various data plug-ins. If enabled, an SDI data plug-in allows access to named
variables from a device that speaks SDI protocol, such as a MarkVIe, MarkVI, or
UC2000. The OPC DA client data plug-in allows the server to obtain variables from
an external OPC DA Server. Refer to www.opcfoundation.org for more information.
Enable Client Writes is enabled by default. If set to False, OPC and SDI clients
(for example, ToolboxST) cannot write to a variable.
Maximum Client Rate is the maximum client data update rate in milliseconds.
Enable Setpoint Logging enables or disables the logging of variables to the OPC
server from connected OPC clients. It writes to the OPC server's optional EGD-
produced variables from another EGD node through EGD Command Message
Protocol (from an HMI computer). The logging occurs in the OPC Server Service’s
log file.
Number of Backup Files are the number of backup log files to keep. The log files
are two megabytes in size, and are kept in the application startup directory (normally
C:\Program Files\GE Energy\GeCssOpcServer). After changing this
setting, the OPC Server Service must be re-started.
SDI Data Enabled enables solicited data through the SDI protocol. If enabled, the
server contains additional internal variables for UC2000, Mark VI, and Mark VIe
controllers. These variables are in addition to the public EGD variables. Although
the internal variables are present in the server and available for OPC browsing, they
are not updated with live data until an OPC client assigns them to a group.
1 From the OPC DA client Tree View, right-click the OPC Server
Connections item, then select Add Server Connection.
2 Enter a host name, then select an OPC DA Server from the OPC Server
drop-down list.
An OPC connection contains one or more groups that are collections of variables to
be updated.
1 From the Tree View, right-click the created connection and select Add Group.
The Add OPC Client Group dialog box displays.
To connect all
items in the
Tree View, select
the top-level item,
then click the
Go On/Offline
icon or right-click
and select
Connect.
If an individual server
connection is
selected, only that
connection is made
when the
Go On/Offline icon
is clicked.
A connection between the client and the OPC DA Server requires access and launch
permissions by the client on the server computer. Since OPC servers often run as
System users (not Administrators), the server must be able to access the client
computer to return data values. The client computer must allow access by the System
account to the client. For information on DCOM settings, refer to GEI-100621,
WorkstationST OPC DA Server.
The .csv file format is one line of variable names and a second line of data values,
for example:
Var1,Var2,Var3
3.7,true,4.5
/Header - Includes a column header line. This option is only used when the /Horiz
option is used
If the /SeparateDateTimeColumns options was specified, Date and Time are also
valid column headers
If the /AdditionalColumns option was used, the headers specified are also valid for
the ColumnOrder list. This is only valid when used with the /Horiz option.
If the argument following the options is a valid file path, the file is expected to
contain a list of variables, one per line with optional comma separated columns for
scale, offset and a translated output name (see an example below). Otherwise, the
argument following the options can be a list of comma-separated variable names
var,scale,offset,translatedName
G1.Celcius,1.8,32,G1.Farenheit
/ColumnOrder="Area,Name,Value,Date,Time,Description,Units,Second Language
Description" var1,var2,var3 outputfile.csv
This utility can be used with the WorkstationST Task Scheduler to provide periodic
writing of .csv data.
To show redundancy
On the EGD tab, select a Produced Page.
The following example displays variables defined in the OPC DA Server tab to be
written by an external OPC DA client.
The WorkstationST OPC DA Server provides EGD and other data to OPC DA
clients. If redundant data must be sent to multiple OPC DA clients, multiple
WorkstationST computers can be configured and each OPC DA client can connect to
a different WorkstationST OPC DA Server. The OPC DA client must determine
page health and select the best source.
The OPC AE Server is OPC AE version 1.10-compliant. Optional interfaces that are
provided allow browsing of published content, enabling/disabling content by Area or
Source, and providing a keep-alive heart-beat to maintain the client connection.
The server is based on the Microsoft.Net Framework, and runs on Windows 2000
and Windows XP. The server is implemented as a service with the name
GeCssOpcAeServer.
WorkstationST
Mark VIe, Mark VI, Computer
Wind, and Pitch
Controllers Acknowledgements
GeCssOpcAeServer
Alarm Server V1.10 Compliant Acknowledgements
Acknowledgements
Alarm/Event
Notifications Alarm/Event
Translation
Alarm/Event Alarm/Event Alarm/Event
Notifications Notifications Notifications
Server Attributes
When an alarm/event is received by the Alarm Server, it is sent to the OPC AE
Server through an internal client connection. Before connected OPC AE clients are
notified, variable name and condition states must be translated.
In the table below, the component name is G1, the boolean variable name is TooHot,
and variable properties are Alarm = True, Event = True and Hold = True.
WorkstationST Alarm Viewer
Example 2
In the table below, the component name is G1, the boolean variable name is TooHot,
and the variable properties are Alarm = True, Event = False and Hold = False.
WorkstationST Alarm Viewer
State Translations
The three alarm/event types that can have a state are Alarm, Diagnostic, and Hold.
Event and Sequence of Events (SOE) are considered simple by OPC AE, and do not
have states.
Note Events and SOEs are simple events, and cannot be acknowledged from any
external OPC AE client.
The Diagnostics Severity is edited in the General tab Property Editor for each
configured component. For variables, the severity is used based on the alarm class
assigned to the variable. If no alarm class is assigned, the default alarm class is used
based on the alarm type.
Diagnostics
Severity items.
1 From the General tab Tree View, click the Features item.
2 From the Summary View, click the Enabled column for Alarm Server and
OPC AE Server, then select True for each. The Alarms and OPC AE
Server tabs display.
Note The Alarm Server must be enabled for the OPC AE Server to be used.
4 Click the Alarms tab to verify that the necessary options have been set. There
are no options defined here that affect the operation of the OPC AE Server.
The WorkstationST can be built and downloaded. Use the status monitor to check
the running health of the OPC AE Server. The DCOM configuration settings may
need to be modified for the GeCssOpcAeServer application before external clients
may successfully connect.
The Outline View contains an entry for each component selected on the General tab.
A system entry will be created for collecting data from multiple components.
Signals on the EGD network are automatically routed to a continuous live collection
if their short-term dead band property contains a value.
For components with an Upload Type property on the Capture Buffer, setting this
property to Automatic creates a collection for this capture buffer. Setting the
property to Trip creates a Trip Log that includes this capture buffer.
Automatic collections only allow modification on the storage, scan rate, and
description properties. All other modifications must be done in the component.
Adding a Collection
To add a collection
Source is the network (Ethernet through the OPC DA server) over which data
values are obtained.
General
Life Span
Disk Usage is the amount of disk space, in megabytes, that this collection is
allowed.
Storage Time is the time, in days, that the files are maintained on disk.
Setup
Method is the method, either Triggered Level or ContinuousLiveData, used for data
collection.
Scan Rate is the rate, in milliseconds, that the data is scanned for changes.
Trigger Setup
Post-Sample Time is the amount of time, in seconds, that data is collected after
the trigger occurs.
Pre-Sample Time is the amount of time, in seconds, that data is collected before
the trigger occurs.
General
Method is the method, either Automatic or Manual used to configure this collection.
Setup
Characters Per Line is the number of characters the printer can fit on one line.
Create CSV File creates a Comma Separated Value (.csv) file in addition to the
.dcaST file.
To delete a collection
Note Removing a component from the Tree View causes that component and all of
its collections to be deleted. An automatic collection can only be deleted by removal
from the component’s configuration.
Adding a Variable
1 From the Tree View, select the collection to which a variable will be added.
2 Click the right-mouse button, then select Add Variable.
Deleting a Variable
Refreshing a Collection
The Refresh command reloads the automatic collections from a selected component
or for all the components, if selected from the Recorder tab.
Modbus Tab
Modbus is an application layer messaging protocol for client/server communications
between components connected on different types of busses or networks. The
WorkstationST application supports both serial and Ethernet communication, and
can operate as both a Master and a Slave. Refer to GEI-100696, WorkstationST
Modbus, for detailed information.
Historian Tab
The WorkstationST Historian is the configuration interface between ToolboxST and
WorkstationST components and third-party Historian systems used for collecting
long-term data from the system components. Refer to GEI-100628, WorkstationST
Historian for detailed information.
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). Refer to GEI-100625, Ethernet Global
Data (EGD) Generic Editor.
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 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.
Under Produced
Pages, select the
desired page.
Ethernet 0, if selected, broadcasts EGD on Ethernet 0. (If more than one Ethernet
Adapter has been configured for EGD, additional Ethernet properties display.)
Mode, when set to Broadcast, sends the page to all EGD nodes. When set to Unicast
or Multicast, the page is only sent to a single destination.
Redundancy is the redundancy mode for the produced exchanges in this page.
Address Zero Health, when set to True, prevents the health of the produced
exchange from being affected (except by a variable at offset 0).
Health Timeout Multiplier gets or sets the timeout multiplier for all produced
exchanges within this page. Setting this property to zero means each exchange is
always healthy.
Layout Mode if set to Auto, exchanges numbers and automatically assigns offsets
at build time. If it is set to Manual, exchange numbers and offsets can be entered
manually.
Minimum Length sets the Minimum Length of the exchanges on this page. Some
components look only at the length of the exchange. This property can be set to a
value larger than the current size of the exchange so that as variables are added, the
component continues to receive the exchange.
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.
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 are loaded and the variables display
in the Summary View.
Grayed
exchanges are
not available to
this component.
EGD Diagnostics
The EGD protocol includes a Command Message Protocol (CMP) to obtain the
status of a Class 2 or higher EGD device. WorkstationST is a Class 3 EGD device.
When any EGD item in the Tree View other than a referenced device is selected, the
EGD Statistics from [Device] tab displays the statistics from the open component.
When a Referenced Devices item is selected, the statistics are obtained from that
device, and the name of the tab page changes accordingly.
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.
Enabling the translation of the data in the Source Address column to a host
name with a Tool Tip. This translation can take some time, so the feature is only
enabled upon request.
Saving the data to csv format
Receive Time is the UTC time when the message was received.
0,1 = Reserved
1,1 = Reserved
Major Signature is the major number reflecting the primary exchange format, and
must be equal in both Producer and Consumer. Truncating or rearranging data within
an exchange is not backward-compatible and requires a change in the major number.
Time Stamp is a time value in POSIX 1003.4 timespec format (32-bit unsigned
integer seconds followed by 32-bit nanoseconds) correlated with the data contained
in the message. The nanoseconds field is limited to values greater than or equal to 0,
and less than 1000000000.
Production Status Flags are bit marks that indicate the validity of the data
sample produced: Bit 0: Set if production error or invalid (old) dataBit 1: Set if
timestamp is not synchronized on producer node (see Table 5: Consumed Exchange
Conditions) Bit 2: A producer that knows of a pending configuration change may set
this to 1 until the configuration change occurs. Otherwise 0.
RDS_Query 0
Retrieve_Configuration_Rqst 3. / 0x03
Retrieve_Configuration_Resp 4. / 0x04
Summary_Rqst 7. / 0x07
Summary_Resp 8. / 0x08
Capabilties_Rqst 9. / 0x09
PDU Version Number is the Protocol Version Number identifying the PDU
format. It must be set to 1.
Message Bytes are the total number of bytes, including header and data.
Reserved 1 is reserved.
Reserved 2 is reserved.
Note You can select devices to search against. The individual pages, with just
variables, perform the same Compare.
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.
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.
Note The initial value for a variable is not available from the OPC Server.
• 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 List dialog box, click the Import button. The Import
Watch Windows dialog box displays.
1 From the Watch Windows List dialog box File menu, select Add Existing.
The Add Existing Watch Window dialog box displays.
Connecting to a WorkstationST
To connect to a WorkstationST
From the System Editor, open a WorkstationST Component Editor.
From the Device menu, select Online.
-or-
From the System Editor, open a WorkstationST Component Editor.
From the toolbar, click the Online button.
The WorkstationST Service provides a command for obtaining feature status, and
sending download requests. Live Data Connection provides live data values for
WorkstationST-monitored variables. The OPC DA Server Service of WorkstationST
Runtime provides the live data connection. When the WorkstationST Component
Editor connects to the WorkstationST Runtime, both the command connection and
the live connection are established.
The Status tab shows information about the running WorkstationST platform.
Color Conditions
Green All features functioning normally.
Yellow One or more of the following:
- There is a minor configuration difference
between the tool and runtime.
- One or more features has a warning.
Red One or more of the following:
- There is a minor configuration difference
between the tool and runtime.
- One or more configured features is not running
or has a fault.
Downloading to WorkstationST
The ToolboxST configuration defines the features of the WorkstationST. The
WorkstationST runtime has a WorkstationST service, which receives the download
request. It expands the zipped download file into the computer's configuration folder
(c:\Config by default). After a bind of consumed EGD configuration is performed,
all running WorkstationST features are informed of a completed download through a
workstation intercom message.
If checked, software
identified as up-to-date
is displayed.
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.
Chapter 5 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 6 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.)
Adding Traces
The Trender represents each variable with a trace. (The term trace is used since the
Trender works similarly to a digital storage oscilloscope, which displays data by
tracing a line across the screen as values are acquired.) As you add traces to a
Trender window, the new traces display in the Traces Tab. (Refer to the section,
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 Select a Variable dialog box. 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 Select a
Variable dialog box, 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.
-or-
♦ Select the check box next to the variable name in the Traces tab or the
Auxiliary View to hide or show the trace on the graph.
♦ Select the check box next to the variable name in the Traces tab or the
Auxiliary View to hide or show the trace on the graph.
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
Address multicast. (If 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.
Exchanges This indicates the number of exchanges in the selected page. It is updated
after selecting the Build command.
Setup Category
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
Exchange ID be 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 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.
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
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 Store the current EGD configuration to the System Database (SDB). It
SDB 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 8 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.
Note For the CMS server to work correctly, the Use Simple File Sharing option
check box must be cleared.
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.
2 The dialog box closes and the previous Select Groups dialog box displays
again, with the Administrators group displayed in the object name text box.
3 Click OK. The User Properties dialog box displays again with the Member
Of tab selected.
4 From the Member Of tab, select the Administrators group, click Apply and
OK.
Users Add Add a new user. Enter the user ID and configure Permissions. If you select
User can modify system, that user cannot access the CMS Administrator.
Delete Remove a user from the system.
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.
Note To run the Administrator Tool and log in, you must have administrative
permissions on your computer. The first time you start the CMS Administrator Tool,
you must select the user type (before login). This determines the security model to be
used with 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.
Working Folder
CMS has two types of working folders:
• 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:
The user must enter the root location as the working folder, not the system working
folder (described in next section).
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 system working folder is not the repository working folder. Typically, the
system working folder is located in the repository working folder (but it can also be
in any folder). This location can also be changed from within the Stand-alone client
(but is not recommended).
The user’s system working folder is shown in the Stand-alone client when a system
name is selected.
• 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 repositories available are those that were created using the CMS
Administrator.
The Component
View displays all
components within
the system that is
currently selected in
the Systems View.
1 From the File menu, select Add System. The Add System dialog box
displays.
2 Locate and select the system to be added, then click OK. The system displays in
the Tree View.
Or
Note When a system is added to a repository, the current folder where the system is
located becomes the working folder for that system.
If a component is checked
out, the Overwrite
Components dialog box
displays. Select any
components to overwrite,
then click OK.
Note A Recursive Get command retrieves a copy of the system, as well as all
configured components.
View Refresh/System Get the current system status. The status conditions include: Equal,
Repository Checked Out, Unknown, or Missing.
Note: If Missing displays in the Status column, do a Get Latest Version.
Clear Status Clear the Log View of all error and event information
Window
Source Get Latest Version Retrieve the last checked-in version of the configuration files from the
repository. Components under CMS control will always be Read-Only
until the component is Checked Out.
Attention: When you perform a Get Latest Version, all files that you
currently have checked out are overwritten.
Check In Check a file back into the repository and save changes
Check Out Check a file out of the repository to make changes
Undo Check Out Return a checked-out file to the repository without saving changes
Label Mark the current repository component with a text label. If the label is
assigned to the system component, the system and all components in
the system are assigned the same text label. The label displays in the
History screen when you select Show History. The label can be used for
specific version identification, as well as for future file retrievals.
Tools
Show Differences Display the differences between the master copy in the repository and
the local copy in the working folder
Note: From the Show History window, you can select a version and
click the Diff button to compare the selected version in the repository
with the local copy in the working folder. You can also select two
versions and click the Diff button to compare the two selected versions
in the repository.
Show History Display the versions/modifications for a selected configuration file
Note: From the Show History window, you can select a version and
click the Diff button to compare the selected version in the repository
with the local copy in the working folder. You can also select two
versions and click the Diff button to compare the two selected versions
in the repository.
Help Contents Open the help file for the Stand-alone Client
About Display the software version information
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.
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.
application code
Software that controls specific machines or processes.
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.
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.
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.
Finder
A subsystem of the ToolboxST application for searching and determining the usage
of a particular item in a configuration.
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.
Resources
Also known as groups. Resources are systems (devices, machines, or work stations
where work is performed) or areas where several tasks are carried out. Resource
configuration plays an important role in the CIMPLICITY system by routing alarms
to specific users and filtering the data users receive.
runtime
See product code.
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.
A F
alarm classes • 13 find methods • 2
alarm scanner • 44
G
C
global parameters
capture buffer • 88 adding • 50
CMS
accessing CMS administrator tool • 8 I
configuring • 7 implementation profile • 9
creating user accounts • 4 installation • 2
installing • 3
CMS recommendations • 15 L
CMS stand-alone client
licensing • 11
menus • 19
opening • 17 N
CMS troubleshooting • 26
CMS working folder network adapters • 29, 1
repository • 11 P
system • 13
command line arguments • 5 page compression • 95, 5
Component InfoView • 6 Produced Pages • 92
components property editor • 5
grouping • 4
moving and copying • 4 R
configuring referenced devices • 98, 8
alarms tab • 42 replace options • 4
OPC AE Server tab • 75 routing • 76
OPC DA Server tab • 62
consumed devices • 24 S
D sampling
triggered • 86
data grids security
copying • 9 passwords • 18
editing • 8 Viewing Protection Status • 19
organizing • 8 Status tab • 2
download wizard • 3 summary view • 4
system editor
E
configuration files • 8
editing Produced Pages • 93, 4 opening and creating systems • 1
EGD saving systems • 7
configuration • 91, 2 system information editor
configuration server • 44 alarm classes • 13
configuration server interaction • 45 format specifications • 26
configuration server reports • 105 HMI resources • 28
diagnostics • 100, 12 measurement systems • 28
packet logging • 101 System Requirements • 1
Ethernet • 91, 28
T
tab
Alarms • 42
Ethernet Global Data • 91
General • 22
HMI Config • 47
OPC AE Server • 75
OPC DA Server • 62
Recorder • 82
time card • 26
Trender
adding traces • 3
capture buffer trends • 7
concepts • 10
cursors • 10
events • 11
exporting to a file • 16
hiding traces • 15
live trends • 7
obtaining data • 9
printing graphs • 16
trace colors • 14
Trender concepts • 10
Trender window features
data toolbar • 3
Trender toolbar • 3
trip log • 87
U
UPD
installing • 12
reinstalling • 12
g GE Energy
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA