Geh 6706
Geh 6706
ToolboxST™ Guide
for WorkstationST™
GEH-6706B
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.
Fax No.
Your Company’s Name and Address Job Site
Phone No.
GE Requisition No.
E-mail
Your Job Function / How You Use This Publication Publication No.
Address
General Rating
Excellent Good Fair Poor Additional Comments
Contents { { { { ____________________________________________________________
Organization { { { { ____________________________________________________________
Technical Accuracy { { { { ____________________________________________________________
Clarity { { { { ____________________________________________________________
Completeness { { { { ____________________________________________________________
Drawings / Figures { { { { ____________________________________________________________
Tables { { { { ____________________________________________________________
Referencing { { { { ____________________________________________________________
Readability { { { { ____________________________________________________________
Specific Suggestions (Corrections, information that could be expanded on, and such.)
Page No. Comments
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
_____ _________________________________________________________________________________
Other Comments (What you like, what could be added, how to improve, and such.) ________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)
{ Superior { Comparable { Inferior { Do not know Comment ____________________________________________
____________________________ Place
stamp
____________________________ here.
____________________________
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Index I-1
System Requirements
The following are minimum hardware and operating system requirements needed to
run the ToolboxST application.
Processor 1 GHz Pentium III
Operating System ® ®
Microsoft Windows 2000
Memory 1024 megabytes (MB) RAM
Hard drive 20 gigabytes (GB)
Monitor XGA display (1024 x 768 x 64K colors)
Drive CD-ROM or DVD-ROM drive
Network ®
Ethernet network adapter
Note If the installation does not start automatically, use Windows Explorer to
navigate to your CD-ROM drive and run GEControlST Install.exe.
2 The Welcome dialog box displays. Click Next. The License Agreement
dialog box displays.
3 To continue the installation, you must accept this agreement. Select Agree.
4 Click Next. The User Information dialog box displays. Enter information for
this dialog box as appropriate.
5 Click Next. The Destination Folder dialog box displays. If this is the first
time 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.
6 Click Next. The Select Features dialog box displays and allows you to select
which features to install or not install. All components will be installed by
default.
7 Once your selections are made, click the Next button until the installation starts.
Click the Finish button when the installation has completed successfully.
You can install multiple versions of the ToolboxST application. If a new version is
included, the desktop and Start menu update to reflect the most recently installed
version.
The Add/Remove Programs option lists all installed versions. Once you install a
newer version, you can remove previous versions of the product from your computer
unless you need to retain them for compatibility.
Note Always install new versions of the ToolboxST application before removing
older versions to preserve your personal settings.
Note If ToolboxST is already opened, starting it again with the /variable option
sends a message to the already running ToolboxST to cause it to navigate to the
appropriate location.
EMT
The EMT opens a ToolboxST system 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>
<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 system 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 system is opened.
<deviceName>.<variableName>
The search for the variable uses the deviceName component of the system. The
/VariableDevice keyword can also be used to specify a particular device to search.
This is useful for third-party interfaces where you may want to control the device
that is searched (see the third example below). A message displays if nothing is
found in the component.
Examples
Go To Hardware Diagnostic
If the first command line argument is a valid path to a .tcw file, that system file is
used for the variable search. Otherwise, the first file in the most recently started
ToolboxST system is opened.
Examples
/HardwareDiagnostic:Marky
This causes the last opened system to be opened, the Marky controller to be opened,
and the Device Diagnostic window to display (View/Diagnostics/Controller
Diagnostics item).
/HardwareDiagnostic:Marky.23GROUP
This causes the last opened system to be opened, the Marky controller to be opened,
and the Hardware tab 23GROUP hardware group to be selected.
Go To Locator
This argument opens any locator string displayed in the Find Results tab.
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.
-NoSplash
If the text –NoSplash is contained in an argument, the splash screen will 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 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.
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.
Licensing
To use the GE ControlST system software, you must purchase a license. The license
includes a hardware key, called a Universal Serial Bus (USB) Protection Device
(UPD). Hardware keys are also known as dongles.
The UPD must be installed in an empty USB port on your computer. Each UPD is
programmed at the factory with one or more application keys that control access to
software products produced by GE. The ToolboxST application will only function if
your UPD contains a valid ToolboxST application key.
Only one UPD may be installed at a time. If you have valid licenses for more than
one product, your UPD must contain a valid application key for each product.
Note If you install the UPD before installing the ToolboxST application, the device
may appear to be installed, but it will not be associated with the correct drivers.You
can correct this after the application is installed with the Reinstalling UPD
procedure.
System Editor
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.
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
the components in the system. The window consists of three major areas as
displayed.
The Property
Editor allows
you to edit the
selected
component.
A list of common components and the icon that represents them in the Tree View is
as follows:
Icon Component
System
Group of Components
Printer
Library Container
Network
Trender Window
External Device (not associated with an application)
You can add components to the root component of a system (represented by the
icon) or a group (represented by a icon). Some components display a wizard or
dialog box that prompts you for additional information when you add them to the
system.
To add a component
In the Tree View, right-click a parent component (either a system or a group),
select Insert New, then select the desired component type.
Existing components can also be imported from a file.
To import an existing component
In the Tree View, right-click a parent component (either a system or a group),
select Insert Existing, then select Device. Select the Device .xml file for the
component to be imported and click Open.
To open the editor for a component
In the Tree View, select a component. Then, from the Edit menu, select
Selected Component.
Or,
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.)
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 will automatically open the application
associated with the configuration file. In all other cases, you must specify the exact
application to be run for the external device.
To configure an external device
1 From the Tree View, select an External Device to configure. (External
devices that have not been configured are represented by a question mark
icon.)
2 In the Property Editor, select the App Path item. Click the ellipsis button
at the right side of the text field to display the Open dialog box.
3 Locate the application executable file used to configure the device, and then
click Open. The App Path property is updated to reflect the new path.
Optional procedures:
• If the External Device requires a specific configuration file, select the Doc
Path item and provide the location of the file.
• If the External Device application requires switches (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. If you do
not save your work your changes will be 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.
To save changes to the current system
From the File menu, select Save System. (Or, click the button on the
toolbar.)
Each system is saved in its own folder. Inside the main system folder is a set of sub-
folders and configuration files. The folder structure depends on the components in
the currently opened system. A typical system and its associated file structure is as
follows:
System Folder is the top-level folder that contains all others. It always has the
same name as the system. (In the example for this section, the system folder is
named System1.) Files in the folder include:
Tools Folder contains definitions for all tool components in a system. A folder for
each type of tool is contained inside the tools folder. In the example, the system
contains a Trender window, so a TrendRecorder folder is stored inside the tools
folder. Inside the folders for each tool type are additional folders for each instance of
the tool. Since the example system has one Trender window named Trender1, a
single Trender1 folder is stored inside the TrendRecorder folder.
File Formats
All configuration data for the ToolboxST application is stored in eXtensible Markup
Language (.xml) format.
While .xml files can be opened and read in a text editor, do not
modify them. The .xml files modified using a text editor do not
work with the ToolboxST application.
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.
The ToolboxST application provides a variety of settings that change the way
various functions operate. While you can also configure settings from inside the
component that they affect, settings for all available components display when the
Settings dialog box is opened from the System Editor.
To open the Settings dialog box
From the System Editor, select the Options menu, and then select Settings
to display the Settings dialog box.
In the Settings dialog box, categories are listed in a Tree View on the left side of the
dialog box. Each category contains one or more settings that display in the Property
Editor on the right side of the dialog box.
The System Options category includes options that affect the system as a whole.
It is available in addition to any other component settings that may display in the
Tree View.
AutoBackup, when set to True, makes a backup copy of all configuration (.xml)
files when configuration changes are saved. The backup files are automatically
named using the format Backup of (original name).xml and are stored in the same
location as the original file.
Maximum Build Errors helps to trace certain configuration problems, which can
cause a very large number of error messages to be generated during a build
operation. This option controls how many such errors can occur before the build
operation is stopped.
Edit Menu
Delete removes the item currently selected in the Tree View.
Options Menu
Settings displays a dialog box with system settings.
Window Menu
Cascade arranges open Component Editor windows in a layered style.
Help Menu
Contents displays the online product documentation.
Release Notes displays up-to-date information about your version of the
ToolboxST application.
Other Documents displays a list of related documents.
Send Problem Report lets you send problems and suggestions to the
ToolboxST team.
About displays version and copyright information.
From the System Editor, double-click the System item in the Tree
View.
Alarm Classes
Alarm classes are groups or collections of related alarms that share a common
priority and color scheme.
To edit Alarm Classes
1 Open the System Editor. From the Edit menu, select System Information.
2 From the Tree View, select Alarm Classes. A data grid with the existing
Alarm Classes displays in the Summary View.
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.
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.
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.
To select the measurement systems used by the SDB
1 In the System Information Editor Tree View, select Format
Specification Sets.
2 Click SDB Meas Sys 1 or SDB Meas Sys 2 in the Property Editor, then
select a measurement system from the drop-down list.
HMI Resources
A resource is a way for an HMI (Human-Machine Interface), to organize and tailor
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.
The ToolboxST configuration for alarm classes and format specifications can be
stored, or put, to an SDB from the System Information Editor.
To put the system configuration to an SDB
1 Open the System Information Editor. From the System menu, select Put
System to SDB. (Refer to the section, System Information Editor.)
2 A dialog box displays confirming the destination SDB Host and Path. Click OK.
When it is complete, the results display on the Log tab of the InfoView.
The EGD Configuration Server maintains a group of .xml files for each EGD
producer device. The EGD Configuration Server also maintains a
MasterSymbolTable.xml file that contains format specifications, alarm classes, and
other system-level information.
The .xml files are stored in folders for each producer ID. The protocol used to get
and put these .xml files 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. ToolboxST 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 files reside.
This is normally /EGD.
Enable, if set to True, enables the interface to the EGD Configuration Server. If this
is enabled, the EGD configuration is sent to the server when a device is saved. An
EGD configuration for referenced devices is obtained from the EGD Configuration
Server if the configuration time is newer in the server than in the ToolboxST
system's local directory for that referenced device. For example, if your ToolboxST
system was located at C:\MySystem and a device was referencing a device Dev1, the
EGD configuration for Dev1 would be obtained from the EGD Configuration Server
if that configuration had a newer timestamp than the configuration at
c:\MySystem\Dev1. Otherwise the local c:\MySystem\Dev1 configuration would be
used.
Host Name is the Host Name or IP address of the host running the 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 any
component saved when offline, will result in a difference between the EGD
Configuration server and the ToolboxST system.
Viewing Differences
Use the System Editor View menu or right-click the status bar shortcut menu to
compare the local configuration to the server configuration.
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.
Send 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.
Refresh Display compares the local system to the EGD Configuration Server and
updates the display.
Note If the EGD Configuration Server option is enabled for the system, the EGD
configuration will also be put to the EGD Configuration server.
Property Editor
provides an easy and
consistent means to edit
the item selected in the
Tree or Summary View
Component InfoView
displays specific feedback
information of the currently
selected tab.
Property Editor
The Property Editor allows you to view and edit the properties of the selected item.
Properties are named values associated with the selected item. The configuration
item displays in the left field and the value displays in the right field.
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 occured.
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.
The three different kinds of protection available are called Access Rights.
• 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.
• View Design allows you to view the internal design of a protected object. For
example, this protects the internal design of a library block. The purpose of this
right is to protect intellectual property from unauthorized persons.
• Modify Design allows you to change the way a protected object works. For
example, 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 on it. Some objects
can be protected if they are contained in another parent object, which is protected by
its own password(s).
Passwords
Whenever you attempt to perform an operation on 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.
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 or a Device). A cached password remains until the component is closed.
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.
There are four possible status indications for each access right:
No password has been set on this object
and none is required
A password has been set on this object
and has not been entered
A password has been set on this object,
but has already been entered
A password has been set on this object’s
parent, but has not been entered
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 will apply to the
definition.
User Block Instanced in a program can be given its own passwords for Modify
Data, Modify Design, or View Design. If none are assigned, it takes on the Modify
Data and Modify Design protection for the parent component. The passwords
assigned to an instance of some block in a user block library will initially be set to
the passwords that were in force in the definition of that block. Once instanced
though, any changes to the protection on the block definition will not propagate to
instances of that block.
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:
Add all
available
columns to
the data grid.
Add selected
column to the Move the selected
data grid. column up or down
in the column order.
Remove selected
columns from the
data grid. Remove all columns
from the 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.
Repository Path can be edited if the EGD Configuration Server is enabled. The
EGD Configuration Server keeps all configuration files at this location. If this entry
is blank, the EGD Configuration Server's EgdCfgServer.exe.config file in the
installation folder can have an entry to determine the path to the repository. If both
the entry is blank and the EgdCfgServer.exe.config file entry is not present, the
configuration files will reside in a subfolder of the EGD Configuration Server's
installation folder.
Name reflects the name of the current controller as set in the System Editor. It is
™
read-only in the Mark VIe Component Editor, and must be changed from the
System Editor.
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.
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.
Timecard
If a timecard is used by the workstation, information about the timecard must be
configured with NTP.
Configuration Manual
Override overrides system
NTP settings and uses local
WorkstationST component
settings only.
Configuration Option
selects the supported NTP
configuration option to be
started on the target
WorkstationST computer.
Configuration Manual Override overrides the system NTP settings, and uses
local WorkstationST component settings only.
NTP Operation Mode selects the NTP operating mode to start on the target
WorkstationST computer.
Primary Time Reference displays the name of the WorkstationST that this
WorkstationSt is using as its primary time reference.
When a Network Adapter item is selected in the Tree View, the following properties
display in the Property Editor:
Enabled, if set to False, disables the selected network adapter. (This property is
usually unavailable.)
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.
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.)
Task Description
(optional)
Specify an optional
end time.
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.
3 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.
Disk Category
General Category
Historical Category
Historical alarm path The path used to hold the historical alarm data files
written by the Alarm Server.
Historical D03 Alarms If True, the Alarm server writes legacy-style D03 alarm
enabled files into the historical alarm path. The file extension is
.d03. The default value is False.
Historical If True, the Alarm Server writes the WorkstationST style
WorkstationST alarms of alarm data into the Historical alarm path. The file
enabled extension used is .bin. The default value is True.
Historical If True, the Alarm Server writes alarm data files in .csv
WorkstationST Text format, including headers. The file extension is .txt. The
Alarms Enabled default value is False.
Enable Live Alarm If True, enables the toolbar on the WorkstationST Alarm
Viewer Toolbar Viewer. The toolbar allows acknowledging, resetting,
locking, and unlocking of live alarms within the system.
Printing Category
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
Configuration alarm data is received and 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.
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 Server If True, the alarm server uses this configuration to
process alarm/events from the external 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.
HMI Configuration
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.
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.
3 In the Summary View, enable the OPC DA Server by selecting True. The
OPC DA Server tab displays, and the OPC DA Server configuration form also
displays in the Summary View.
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, MarkVI, and MarkVIe
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.
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.
To add an OPC group to the connection
1 From the Tree View, right-click on the created connection. 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. The server must be able to access
the client computer to return data values. Remember, many times OPC servers are
running as the System user (not the Administrator). 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 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.
Routing
Alarm and event routing is shown below. The OPC AE Server can be connected
locally or remotely from another computer.
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 device name is G1, the boolean variable name is TooHot, and
variable properties are Alarm = True, Event = True and Hold = True.
Example 2
In the table below, the device name is G1, the boolean variable name is TooHot, and
the variable properties are Alarm = True, Event = False and Hold = False.
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.
The OPC AE Server implements and acknowledges Alarms, Diagnostics and Holds
as condition-related states. Events and SOEs are simple events, and cannot be
acknowledged from any external OPC AE client.
Diagnostics
Severity items.
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
1 From the Tree View, select the desired device.
2 Click the right-mouse button, then select Add Collection.
3 From the drop-down list, select the collection type.
Continuous Sampling
Communication
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 hours, that the files are maintained on disk.
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.
Triggered Sampling
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.
Trip Log
Trip logs contain data from capture buffers along with data collected for each
variable defined in the capture buffers for the previous 24 hours.
Method is the method, either Automatic or Manual used to configure this collection.
Setup
Capture Buffer
Capture buffers are high-speed data buffers located in the component. The Capture
Buffer collection uploads and writes to the buffer specified by the status variable in
the collection.
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.
Deleting a Collection
To delete a collection
1 From the Tree View, select the collection to be deleted.
2 Click the right-mouse button, then select Delete from the drop-down list.
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.
To add 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.
To delete a variable
1 From the grid, select the variables to be deleted.
2 Click the right-mouse button, then select Delete Selected Row(s).
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.
EGD Configuration
To configure EGD for a WorkstationST
1 From the System Editor, double-click on a WorkstationST component to
display the Component Editor.
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.
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
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.
To add a new Produced Page
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.
To delete a Produced Page
From the Tree View, right-click the page you wish to delete, then select
Delete.
Under Produced
Pages, select the
desired page.
The following properties are available for configuration when a Produced Page is
selected in the Tree View:
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.
Destination IP Address controls the IP address that receives the exchanges when
Mode is set to Unicast or Multicast.
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.
Timeout Multiplier gets or sets the Timeout Multiplier for all produced exchanges
within this page. The exchange period scaled by this multiplier yields the timeout
period for all exchanges in this page. If any variable on an exchange is written to (by
whatever source produces the data) within this timeout, the exchange is marked as
healthy and will remain healthy. The default is a multiplier of 0. If set to a value
larger than 0, the exchange will begin life un-healthy and will transition healthy
when any variable is written. The exchange will remain healthy as long as any
variable is written before the timeout expires. If a page has multiple exchanges, each
exchange requires a write of one of its variables to remain healthy. Setting this
multiplier to zero, means each exchange is always healthy.
Skew is used to prevent exchanges with the same period from being produced at
exactly the same instant. The skew for the first exchange in the page is set to this
value, and each additional exchange skew differs from the previous exchange’s skew
by exactly this value. For example, if you have three exchanges in a page and a skew
value of 2, the first exchange’s skew is two, the second exchange’s skew is four and
the third exchange’s skew is six. (The skew property is measured in nanoseconds.)
Starting Exchange ID is used for the first exchange on this page. Each additional
exchange will be incremented from this number. When this property is changed, all
exchanges are renumbered.
Page Compression
When a page compression is performed, the variable locations are optimized. The
variables are located in increasing size order, starting with Booleans, then Words,
Double Words, and finally all other variables.
To compress a single page
From the Tree View, right-click the page to compress, then select Compress.
Tip If the variable to be added to the EGD page is already in use on the OPC DA
Server tab, you can add the variable without using the EGD tab. To add a variable
from the OPC DA Server tab, select the desired variable(s) in the Summary View,
then set the EGD Page property using either the Summary View or the Property
Editor.
Note To edit exchange signatures and configuration time, set Layout Mode to
Manual.
3 Review the warning about manual Exchange Signature editing, then click
OK.
Referenced Devices
The EGD variables defined in other components can be added to the current
component’s variable list by adding a reference. References can only be created to
EGD-capable devices that are producers of pages.
To select referenced devices
From the Tree View, right-click the Referenced Devices item, then select
Select Devices to display the Select Devices dialog box.
Grayed
exchanges are
not available to
this component.
When EGD configurations are edited in remote devices, refresh the configuration to
ensure that the latest variable information is used. A refresh automatically occurs
when a WorkstationST component is opened, and when it is built.
To refresh the configuration of a referenced device
In the Tree View, right-click the device to be refreshed, and select Refresh.
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
When the collection is started, the runtime will begin storing all EGD messages
received. When the queue gets full, old messages are deleted. When the UI stops the
collection and uploads the data, all messages display in the grid.
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.
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.
Introduction
The WorkstationST™ Runtime features include Monitoring, Data Collection, Alarm
Collection, and Human Machine Interface (HMI). The WorkstationST Service is one
of two processes with which toolbox interfaces to obtain status and live data, and to
perform downloading.
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 will then expand 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.
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.
To open the Finder
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
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
observing only that component and may be used to monitor any variables.
Graph View
contains the trend
graphs, which
display the values
represented by
each trace.
Property Editor
allows you to change
settings that affect the
capture and display of
data.
Data Toolbar
contains commands
that manipulate the
current data.
Traces tab Sources tab User Note tab Events tab lists Auxiliary View Mode Indicator
displays traces displays sources allows you to save all events that contains tabs that displays the
currently being where data is comments, have occurred display current mode
monitored by the collected. instructions, and during the information about (Live or Replay).
Trender window. notes about the current Chapter. the current data.
current Chapter.
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.)
Obtaining Data
As they depend on the presence of a controller, live and capture buffer traces do not
initially contain any data. (The data from static file traces is automatically imported
and displays as soon as the trace is added.) Once connected to the controller, the
procedure for obtaining data depends on the type of traces present. Data from live
traces is captured in much the same way that a video recorder operates (with record
and pause buttons), while data from a capture buffer is uploaded from the controller
in a single operation.
To connect to the controller
Select the Online button on the Trender toolbar. (If any of the source
controllers are redundant controllers, the Trender prompts you to select a
redundant channel before opening the connection.)
To begin capturing a trend from live traces
On the Data toolbar, select the Record Data button. The Trender
switches to Live mode, and the Graph View continuously scrolls the time axis
to display the latest incoming data while recording.
To freeze the display while capturing a trend from live traces
On the Data toolbar, select the Record Data button. The Trender
returns to Replay mode.
Trender Concepts
Chapters
When working with live, or capture buffer, or some historical sources, the Trender
can record more than one set of data. The basic unit of data capture in the Trender is
a chapter. A chapter represents one acquisition session, which is either a single
upload for a capture buffer source or a single period between clicks of the Record
Data button for a live source. Chapters are organized chronologically, so the first
acquisition session is always the first chapter and the most recent session is always
the last chapter.
A Trender window only displays one chapter of information at a time. 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.
To navigate between Chapters
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.
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.)
To add a user event
1 Select an active cursor.
2 From the Edit menu, select Add User Event. (Or, press the shortcut keys
CTRL+M.)
3 Enter a name for the new event, and select OK.
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.
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.
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.
To change the color assigned to a trace
1 From the Traces tab, select a trace.
2 In the Property Editor, locate the Pen category and select the Color
property.
3 Click the drop-down list and select the Custom (for a color palette) or Web
(for a list of named colors) tab.
4 Click the square that corresponds to the desired trace color. The trace updates
automatically.
To modify the default trace colors
1 From the Options menu, select Settings.
2 Locate and select the Trender item in the Settings window.
3 In the Property Editor, select the number of the trace (for example, 2nd Trace)
to be changed.
4 Click the drop-down list and select the Custom (for a color palette) or Web
(for a list of named colors) tab.
5 Click the square that corresponds to the desired trace color.
6 When you have finished changing trace colors, click OK.
Hiding Traces
In some situations, especially with capture buffers, a Trender window contains more
traces than you want to monitor at a particular time. Traces in a Trender window can
be hidden. They still collect data, but they do not display in the Graph View or the
Trace tab.
To hide traces
1 From the Traces tab, select one or more traces.
2 From the Edit menu, select Hide Selected Traces, or right-click on the
selected traces and select Hide Selected from the context menu.
To show or hide a trace
From the Edit menu, select Show Traces. Select and clear the check boxes
next to the trace names as desired, then click OK.
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
added to the output. Selects the precision
of the exported
timestamp.
If selected, only the
time range selected
by the cursors is
exported.
Printing Graphs
The Trender can print the currently displayed graph to any printer attached to the
system. Printed graphs reflect the current appearance of the Graph View, including
displayed traces, colors, and axis boundaries.
To preview the results of a print command
From the File menu, select Print Preview.
To print the current Graph View
From the File menu, select Print. Adjust printing options as desired and click
OK.
Network Adapters
The General tab configures Ethernet adapters for an external EGD-capable device.
One adapter is created by default, and up to four adapters can be added.
To add a network adapter
1 From the System Editor, right-click an external device, 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 Adapters item, then select
Add Adapter.
To remove a network 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 is the Internet Protocol (IP) host name for the selected network adapter.
Subnet Mask is the subnet mask associated with the connected network.
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.
To add a new Produced Page
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.
To delete a Produced Page
From the Tree View, right-click the page you wish to delete, then select
Delete.
Under Produced
Pages, select the
desired page.
The page
properties display
in the Property Editor.
The following properties are available for configuration when a Produced Page is
selected in the Tree View:
Ethernet 0, if selected, broadcasts EGD on Ethernet 0. (If more than one Ethernet
Adapter has been configured for EGD, additional Ethernet properties displays.)
Allow Editing when False, a variable's exchange ID and offset for variables on a
manual page cannot be edited. A page compress will also be disabled. This prevents
you from inadvertently editing a page with manual selected as Layout mode.
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.
Destination IP Address sets the IP address to which the exchanges on this page
are unicast or multicast. (If the Mode property is set to Broadcast, this property is
not available.)
Page Compression
When a page compression is performed, the variables are located in increasing size
order, starting with Booleans, then Words, Double Words, and finally all other
variables.
To compress a single page
From the Tree View, right-click the page to compress, and then select
Compress.
Note To edit exchange signatures and configuration time, set Layout Mode to
Manual.
5 Review the warning about manual Exchange Signature editing, then click
OK.
6 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.
To refresh the configuration of a referenced device
In the Tree View, right-click the device to be refreshed, and then select
Refresh.
Multiple Producer IDs indicates device support for multiple producer IDs.
Data Types allows you to configure supported data types. (Clicking the ellipsis
button will open an editor window.)
Double Word Alignment indicates that the offset of a DWORD length variable
must be evenly divisible by this number.
Word Alignment is set to True if the device requires that all WORD length
variables be aligned on an even boundary.
Broadcast is set to True if the device supports broadcast destinations for EGD data
or command packets and False otherwise.
Max Coherent Data 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 String returns the maximum size string supported by the device. If the
attribute is not present then the device has no set maximum size for strings. It is
optional and is initialized to 0.
Multicast is set to True if the device supports multicast destinations for EGD data
or command packets and False otherwise.
Skew is a Boolean value representing the capability of the producer to support the
skewing of produced exchanges with respect to time.
Unicast is a Boolean value that is set to True if the device supports unicast
destinations for EGD data or command packets. Otherwise, it is set to False.
Device Class Name is name of the class of device to which this device belongs.
The generic editor uses CMP to display live data values on a produced or referenced
device summary grid view. The Connection Toolbar button sends the CMP message
to the device to obtain the data.
Due Time is the time that a consumer data packet must be received for an exchange
to remain valid.
Length is the value for a produced exchange. This length may be the highest
variable offset in the exchange or the highest offset of a variable, which may have
been removed. For a consumed exchange, the value may be the highest variable
offset used or the length of the produced exchange, depending on the bind algorithm
of the individual tool.
Missed Count is the number of data production packets missed since initialization.
A missed packet occurs when a data production message is received that has a
request ID greater by more than one than the last message received (accounting for
counter roll-over).
Refresh Errors are the number of times a refreshment fault has occurred. A
refreshment fault occurs when a subsequent data production packet (or initial packet
at startup time) does not arrive at a consumer within a pre-defined update period.
Note The EMT provides a detailed view of the configuration server contents.
G1
G2
The Filter Toggle button defaults to a filtered state. It displays nodes that
have the same name but have a different Producer ID as the open component.
The Delete button deletes the selected node or nodes. If the nodes 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 Menu
Edit Menu
Undo returns the editor to the state it was in before the last action was
performed.
Redo performs an action again after an undo command.
Cut moves the currently selected portion of the data grid to the clipboard.
Copy transfers a duplicate of the currently selected portion of the data grid to
the clipboard.
Paste transfers the contents of the clipboard into the data grid.
Delete deletes the currently selected item.
Find opens the Finder dialog box. For more information, refer to Chapter,
Finder.
View Menu
Go Back returns to the view that immediately precedes the current view in the
history.
Go Forward returns to the view that immediately follows the current view in
the history.
Help Menu
Contents opens this help document.
Release Notes opens the release notes for the current version of the
application.
About shows version and copyright information about the application.
Chapter 8 Configuration
Management System (CMS)
The CMS Administrator tool allows you to perform the following administrator tasks
on the CMS server:
Note To run the Administrator tool, you must have administrative permissions on
your computer.
To create a new repository, select the Create a new Repository option and click
OK.
Main menu
User List
Permissions
Repository Menu
Restore ends the component editing session and returns to the main System Editor.
The user who creates the repository becomes the default administrator.
2 From the drop-down list, select a repository, then click Open. The CMS
Administrator window displays with all users.
Enter the folder path and the name of the repository you would like to create and
click OK.
Deleting a Repository
To delete a repository
1 From the Repository menu, click Delete. The Delete Repository dialog
box displays.
2 From the drop-down list, select the repository to be deleted, then click OK.
Restoring a Repository
To restore a repository
1 From the Repository menu, click Restore. The Restore Repository dialog
box displays.
Adding a User
To add a user
1 From the Users menu, select Add or right-click the User list and select Add
User. The Add User dialog box displays.
Editing a User
To edit a user's permissions
1 Highlight the user to be edited.
2 From the Users menu, select Edit, or right-click the User list and select Edit.
The Edit User dialog box displays.
The status of the server changes to Running, and the button displays Stop Server.
If there are any existing repositories with current user types, use this dialog box to
back up all existing repositories in the CMS server.
Click OK to back up
the repositories.
Once all the repositories have been backed up, the Administrator Tool must be
restarted. The administrator who restores this repository becomes the default
administrator.
2 When the Server Details dialog box displays, type the IP address of the
machine on which the server is installed.
3 Type your User Name, Password, and the name of the Repository, then
click OK. A WorkingFolder dialog box displays:
2 The Server Details window displays again. Re-enter the IP address, then when
the LogIn window displays, repeat the logon steps.
Adding a System
A system must be added to begin version control. The working folder must be set,
and you must have modify permission.
To add a system
From the File menu, select Add System, or in the System View, right-click
the repository, then select Add System.
Deleting a System
You must have modify permission to delete a system. This command deletes the
system, but not the system folder. A system folder can only be deleted by an
administrator.
To delete a system
From the File menu, select Delete System, or in the System View, right-
click the repository, then select Delete System.
Source Menu
Retrieving a Configuration
To retrieve a system or device configuration
1 From the System View, select a system, or from the Device View, select a
device.
2 From the Source menu, select Get Latest Version, or from the selected
system or device, right-click to select Get Latest Version.
The most recent configuration, in read-only mode, is placed in the working folder
you specified.
2 From the Source menu, select Check In to save the changes. The CheckIn
dialog box displays.
3 If desired, enter a comment in the Comments text field, then click OK.
To revert your changes back to the previous version
From the Source menu, select Undo Checkout.
Tools Menu
Showing History
A historical record of all system or device operations is available for viewing.
To view CMS history
From the Tools menu, select Show History. The History window displays.
Chapter 9 Reference
Menus
File Menu
Save saves changes to the current component.
Close ends the component editing session and returns to the main
System Editor.
Edit Menu
Undo returns the component to the state it was in before the last action
was performed.
Redo performs an action again after an undo command.
Paste places the contents of the clipboard into the currently selected item.
View Menu
Go Back returns to the view that immediately preceded the current view in
the history.
Go Forward returns to the view that immediately follows the current view
in the history.
Global Variables displays all global variables, and allows grid viewing,
sorting, and editing.
Trenders display a list of Trender windows associated with the
component.
Watch Windows displays a list of Watch Windows associated with the
component.
Test OPC Client opens an OPC client window that connects to any OPC
DA Server to verify communication.
EGD Management Tool opens the EGD Management Tool.
WorkstationST Alarm Viewer opens the Alarm Viewer (this only
displays if an Alarm Viewer was installed).
Build converts the current configuration into binary files that can be downloaded
to a controller.
Download opens the download wizard to download application configuration.
Put Device to SDB stores the component configuration to a System Database
(SDB).
Help Menu
Runtime Release Notes opens the Release Notes Viewer for the selected item
(WorkstationST Features, OPC DA Server, or EGD Configuration Server.
Release Notes opens the Release Notes Viewer.
About displays version and copyright information.
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 pcode.
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 G
acronyms and abbreviations 1-10 global parameters
alarm classes 2-11 adding 3-25
alarm scanner 3-21 deleting 3-26
editing 3-26
C
I
capture buffer 3-44
command line arguments 1-4 implementation profile 7-9
Component InfoView 3-3 installation 1-2
components
grouping 2-4 L
moving and copying 2-4 licensing 1-8
Configuration Management System
administrator tool 8-1 M
client interface 8-13
Menus
Tools menu 8-11
Device 7-15, 9-2
User menu 8-9
Edit 2-9, 7-14, 9-1
configuring
File 2-9, 7-14, 8-15, 9-1
alarms tab 3-18
Help 2-10, 7-15, 9-2
OPC AE Server tab 3-33
Options 2-10
OPC DA Server tab 3-27
View 2-10, 7-14, 8-16, 9-1
consumed devices 3-13
Window 2-10
D N
data grids
network adapters 3-16, 7-1
copying 3-10
editing 3-8 P
organizing 3-9
download wizard 4-3 page compression 3-50, 7-5
Produced Pages 3-48
E property editor 3-2
editing Produced Pages 3-49, 7-4 R
EGD
configuration 3-48, 7-3 referenced devices 3-53, 7-8
configuration server 2-17 replace options 5-4
configuration server interaction 2-19 Repository menu
configuration server reports 3-60 backing up 8-7
diagnostics 3-55, 7-12 deleting 8-6
packet logging 3-56 restoring 8-7
Ethernet 3-48, 9-4 selecting 8-5
routing 3-33
F
S
File menu
adding 8-15 sampling
connecting 8-15 continious 3-41
deleting 8-15 triggered 3-42
setting 8-15 security
find methods 5-2
GEH-6706B
Revised 060920
Issued 050915