GE Energy
for Mark* VIe Control
ToolboxST* User Guide
GEH-6700J
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.
If further assistance or technical information is desired, contact the nearest GE Sales or Service Office, or an authorized GE Sales Representative.
© 2007 - 2009 General Electric Company, USA. All rights reserved.
Revised: 090415 Issued: 070511
* Trademark of General Electric Company
We welcome comments and suggestions to make this publication more useful.
Your Name Today’s Date
Your Company’s Name and Address Job Site
GE Requisition No.
Publication No. Your Job Function / How You Use This Publication
Publication Issue/Revision Date
If needed, how can we contact you? Fax No.
Phone No. E-mail 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.)________________________________________________
__________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________ __________________________________________________________________________________________
g
Reader Comments
To: GE Energy Documentation Design, Rm. 293 1501 Roanoke Blvd. Salem, VA 24153-6492 USA Fax: 1-540-387-8651 (GE Internal DC 8-278-8651)...Fold here and close with staple or tape... ____________________________ ____________________________ ____________________________
GE
Energy
Documentation Design, Rm. 293 1501 Roanoke Blvd. Salem, VA 24153-6492 USA...Fold here first... Place stamp here.
Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not strictly observed, could result in personal injury or death.
Indicates a procedure, condition, or statement that, if not strictly observed, could result in damage to or destruction of equipment.
Indicates a procedure, condition, or statement that should be strictly followed in order to optimize these applications.
This equipment contains a potential hazard of electric shock or burn. Only personnel who are adequately trained and thoroughly familiar with the equipment and the instructions should install, operate, or maintain this equipment.
Isolation of test equipment from the equipment under test presents potential electrical hazards. If the test equipment cannot be grounded to the equipment under test, the test equipment’s case must be shielded to prevent contact by personnel.
To minimize hazard of electrical shock or burn, approved grounding practices and procedures must be strictly followed.
To prevent personal injury or equipment damage caused by equipment malfunction, only adequately trained personnel should modify any programmable machine.
Contents
Chapter 1 About the ToolboxST Application
1-1
System Requirements ...1-1 Installation...1-2 Command Line Arguments ...1-5 Licensing ...1-10 Installing the UPD...1-10 Reinstalling UPD ...1-10 Acronyms and Abbreviations...1-11
Chapter 2 System Configuration
2-1
Opening and Creating Systems ...2-1 Components and Tools...2-3 System Editor Status ...2-5 Configuring External Devices ...2-7 Saving Systems ...2-7 Configuration Files...2-8 Folder Structure...2-8 File Formats ...2-9 System Options ...2-10 System Editor Menus ...2-11 System Information Editor ...2-13 Alarm Classes ...2-13 Diagnostic Translations...2-15 Sound Options...2-23 Plant Areas ...2-25 Format Specifications...2-26 Measurement Systems...2-28 HMI Resources ...2-28 HMI Screens ...2-29 System Database (SDB) ...2-42 Master File ...2-43 EGD Configuration Server...2-44 Working Online with the EGD Configuration Server...2-45 ToolboxST/EGD Configuration Server Interaction ...2-45 Viewing Differences ...2-46 Configuring an External EGD Device ...2-48 Starting ToolboxST from an Existing System Configuration ...2-49 SecurityST...2-50 Configuring SecurityST Logon...2-51 Displaying Current User ...2-52 Logging On ...2-53 Auto Logging Off...2-54 Logging Off ...2-55
Unlink Property...3-4 User Block Definitions...3-7 Library Container Editor ...3-8 Adding Libraries ...3-11 Library Property Editor ...3-13 Library Summary View...3-13 Library Help Files ...3-14 Table Definition Property Editor...3-15 Exporting a Table Definition...3-16 Online Display and Changes ...3-17 Using Table Definitions in Software Application Code...3-18 User Block Definitions...3-20 User Block Variables ...3-21 Working with User Blocks...3-22 Application Documentation...3-28 Application Software Examples ...3-29 User Block Definition ...3-29 Linked User Block ...3-34 Device Attribute ...3-40 Block Exclusion with an Instance Script...3-43 Text Substitution with an Attribute ...3-44
Chapter 4 Block Diagram Editor
4-1
Diagram Shortcut Menu ...4-2 Renaming Sheets ...4-3 Sheet Names...4-3 Customizing Sheet Borders ...4-4 Border Options ...4-5 Preview...4-5 Footer Block...4-6 Custom Text ...4-7 Sheet Information...4-8 Variables and Blocks...4-9 Variables with Status...4-9 Blocks with Status...4-9 Block Shapes...4-11 Variable Input Blocks...4-12 Layout Modes...4-14 Managing Blocks...4-14 Wiring Block Pins ...4-16 Wire Styles and Colors...4-16 Zoom and Pan Tools ...4-17 Block Shape Shortcut Menu ...4-18 Connecting Pins...4-20 Changing a Pin Connection...4-21 Toggling Live Data Layers...4-22 Modifying Live Values...4-23 Shape Drawing Tools ...4-25 Variable Rail Tool...4-26 Adding a Variable Rail...4-27 Adding Variables to a Variable Rail ...4-28 Managing Variables on a Rail ...4-29 Working with Variables ...4-30 Text Tool...4-30 Rectangle/Ellipse Tools...4-31 Image Tool ...4-32
Additional Toolbar Buttons...4-33 Diagram Settings ...4-33 Rung Editor ...4-35 Contacts...4-37 Wires...4-37 Coils ...4-38 Adding Rows and Columns ...4-38 Errors...4-38
Chapter 5 Sequential Function Chart (SFC)
5-1
Creating an SFC ...5-1 Editing an SFC ...5-3 Adding a Transition ...5-6 Adding an End Transition ...5-8 Variable Connections...5-11 SFC Online Operations from the ToolboxST Application ...5-11 Changing SFC Modes ...5-12 Publishing an SFC on an EGD Page ...5-13
Chapter 6 Mark VIe Component Editor
6-1
Creation Wizard ...6-1 Summary View...6-5 Property Editor ...6-6 Component InfoView...6-7 Log Tab...6-8 Data Grids ...6-9 Editing Data ...6-9 Organizing Columns ...6-10 Copying and Moving Data ...6-11 Component Options...6-12 Security ...6-13 Passwords...6-13 Password Caching ...6-14 Viewing Protection Status...6-15 Protected Objects ...6-16 General Tab ...6-17 Attributes...6-22 Attribute Value Editor...6-23 Network Adapters ...6-24 Auto-Reconfiguration ...6-26 Upgrading...6-27 Compare To Controller ...6-29 Compare Devices ...6-30 Mark VIe Menus ...6-31 Hardware Tab...6-33 Network Redundancy...6-34 Adding Modules...6-35 Organizing Modules...6-39 Modifying Modules...6-40 Viewing Modules...6-40 Upgrading Modules...6-47 Diagnosing Modules ...6-50
Library References ...6-62 Instance All ...6-63 Overridable Properties...6-64 Adding a Task ...6-65 Adding a User Block ...6-66 Unlink Permanently...6-69 Property Editor ...6-70 Variables ...6-74 Table Definitions...6-79 User Block...6-83 Dynamic Data Recorder (DDR) Tab ...6-86 Configuring DDR...6-86 Status Variables...6-89 Adding Variables ...6-89 Updating DDR ...6-90 Importing and Exporting DDR...6-91 DDR Setup ...6-92 Ethernet Global Data (EGD) Tab ...6-98 EGD Configuration ...6-98 Produced Pages ...6-98 Editing Produced Pages...6-99 Page Compression...6-101 Variables ...6-102 Editing Exchange Signatures and Configuration Time ...6-103 EGD Diagnostics...6-105 EGD Configuration Server Tab...6-106 EGD Configuration Server Reports ...6-107 Referenced Devices...6-108 Modbus Slave Tab...6-110 Configuring Modbus Slave ...6-111 Modbus Slave Register Pages ...6-113 Mark VIe Tools ...6-115 Reports ...6-115 Creating Reports...6-115 Saving, Retrieving and Printing Reports ...6-115 Viewing Reports...6-116 Filtering Rows...6-117 Finding Data...6-120 Importing an I/O Report from a .csv File ...6-120 Coding Practices Report...6-122 Auto-Reconfiguration Reports ...6-123 Forced Variables ...6-129 Global Variables...6-130 Watch Windows ...6-131 Adding a Variable ...6-136 Managing Variables ...6-140 Forcing Live Values...6-140 Reconciling Constant Differences...6-140 Drag-and-Drop ...6-141 Importing and Exporting ...6-141 LiveView...6-142 Adding and Opening LiveViews...6-142 LiveView Editor Features ...6-147 LiveView Controls ...6-149 Attaching a Variable...6-151 Saving a LiveView...6-157 Variable Definitions ...6-157 Control Constants ...6-158
Chapter 7 Working Online With a Mark VIe Component
7-1
Connecting to a Controller ...7-1 Status Tab...7-2 Controller Attributes ...7-3 Downloading to a Controller...7-5 Download Command ...7-5 Controller Setup ...7-6 Download Wizard ...7-8 Dual Controller Download...7-11 Upload Wizard ...7-14 Controller Diagnostics View ...7-16 I/O Diagnostics View...7-17 Administer Totalizers ...7-18 Totalizer Passwords ...7-19 Modifying Totalizer Values ...7-20Chapter 8 Finder
8-1
Find Methods...8-2 Replace Options ...8-4
Chapter 9 Trender
9-1
Accessing a Trender Window ...9-1 Trender Window Features ...9-2 Trender Toolbar ...9-3 Data Toolbar ...9-3 Working in Trender...9-4 Acquiring Data...9-4 Adding Traces...9-4 Live Trends ...9-7 Triggered Live Trends...9-8 Capture Buffer Trends...9-9 Static File Trends ...9-9 Obtaining Data ...9-10 Trender Concepts ...9-11 Chapters ...9-11 Cursors ...9-11 Value ScreenTips ...9-12 Events...9-12 Working With Trender Data...9-13 Graph View Options ...9-13 Grid Lines ...9-13 Sample Markers ...9-14 Time Axis...9-15 Traces...9-15 Auto-Range Trace ...9-15 Manual Range Adjustment...9-16 Trace Colors...9-16 Hiding Traces...9-17 Statistical Calculations...9-17 Exchanging Trender Data...9-18 Exporting to a File...9-18
Chapter 10 EGD Editor for External Devices
10-1
Network Adapters...10-1 EGD Configuration ...10-3 Produced Pages...10-3 Editing Produced Pages...10-4 Page Compression ...10-6 Variables...10-6 Editing Exchange Signatures and Configuration Time ...10-7 Referenced Devices ...10-8 Implementation Profile...10-9 Viewing Live Data Values ...10-11 EGD Diagnostics...10-12 EGD Configuration Server Tab...10-13 External Device Menus ...10-14
Chapter 11 Configuration Management System (CMS)
11-1
Installing the CMS Server ...11-1 Creating Windows User Accounts ...11-3 Configuring the CMS Server...11-7 Accessing the Administrator Tool...11-7 Working Folder ...11-10 Repository Working Folder...11-11 System Working Folder ...11-12 Add System / System Working Folder...11-13 Recommendations ...11-14 CMS Stand-alone Client...11-16 Opening the CMS Stand-alone Client ...11-16 Adding a System to a Repository ...11-17 Getting the Latest Version...11-18 CMS Stand-alone Client Menus...11-19 CMS Integrated Client...11-21 Opening the CMS Integrated Client...11-22 CMS Menu Items ...11-25 Troubleshooting...11-26
Chapter 12 TreeFileImporter 12-1
Running the Tree File Importer ...12-1
Chapter 13 Special I/O Functions
13-1
Calibrating Valve Circuits...13-1 Availability...13-3 Multicasting...13-4 Availability...13-7 Configuring a HART Device...13-8 Availability...13-9 PROFIBUS Communications...13-10 Adding a Slave Device...13-13 Configuring the Master Device ...13-19 Enabling a Slave Device ...13-20 Displaying the PROFIBUS Network ...13-20 Standard Diagnostics Tab...13-23 Device Diagnostics Tab ...13-25 Identifier Diagnostics Tab...13-27
Mark Ve Retrofit ...13-30 Availability ...13-30 Configuring a PCNO Module...13-31
Glossary of Terms
13-35
Index
13-39
C
H A P T E R1
Chapter 1 About the ToolboxST
Application
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.
For assistance, contact the nearest GE Sales or Service office, or an authorized GE sales representative.
Installation
To install the software
1 Place the ControlST* CD in the CD-ROM drive. The installation starts
automatically. The Setup-GE ControlST dialog box displays.
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.
If you are upgrading from a previous version, and you select GE HMI Viewer Tools, a message displays to let you know that viewer tools are already installed.
The GE CMS Server and GE Hart Message Server options are typically only installed on one computer at a site. Therefore, if either of these options is selected, a message displays asking you to verify that you want to install the option at more than one location.
Click Next to continue.
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.
To select a component not to be installed, click the icon next to the component name, then select the red X.
8 Once your selections are made, click the Next button until the installation starts.
To remove or change the ToolboxST application
From the Start menu, select Settings, Control Panel, then Add/Remove
Programs.
Use the scroll bar to find GE
WorkstationST Package.
Click Change or Remove to change or uninstall features from the installation.
Command Line Arguments
The ToolboxST application contains the following command line arguments: • EGD Management Tool (EMT) arguments, including
- /EGDAction:ADD /EGDDevice: - /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
EMT
The EMT opens a ToolboxST application and navigates to the EGD configuration tab of a component. It can also add a device with a specified producer ID.
Note If EMT command line arguments are used, the /Variable, /VariableDevice,
/Hardware Diagnostic, and /Navigate to Locator arguments are ignored. Standard Action Arguments
/EGDAction:ADD /EGDDevice allows a device to be added.
Note Using /EGDAction:ADD requires no /EGDDevice identifier. The application
started determines the ProducerID(s) and device names(s) to be used.
/EGDAction:MODIFY /EGDDevice:<producer ID> allows the device-assigned Producer ID to be modified.
/EGDCollection:<collection name> is defined for tools that can manage collections of device configurations. Collection names are defined in the GuiDevice.xml file. EMT Argument Rules
The following rules apply to EMT arguments:
• The /EGDAction must be the first argument, followed by the /EGDDevice argument.
• Only one set of //EGDAction and /EGDDevice pairs should be defined. The ProducerID value must be represented as a four-byte unsigned integer. An IP address in dotted-quad format must be converted to the unsigned decimal equivalent before it can be used in the argument (for example: the IP address 1.2.3.4 converts to the value 67305985).
To provide consistency, a common set of command arguments are defined for each application. The standard format is
/<keyword>:<value> where
/ (slash) is a required delimiter start of an argument.
<keyword> defines the operation or action (the <, > are not used). : (colon) is a required delimiter that separates the keyword and value.
<value> defines the value to be used in the operation or action (the <, > are not used).
Formatting Command Line Arguments
The following rules apply to all command line arguments: • Process keywords, ignoring case.
• Process values, ignoring case.
• Do not use spaces around colons (:) and after slashes (/).
• A space is required between keyword-value pairs (Example: after MODIFY and before /EGDDevice).
• The /EGDAction must be the first argument, followed by the /EGDDevice argument.
• Define only one set of //EGDAction and /EGDDevice pairs.
Go To Variable
/Variable:<variableName> [/VariableDevice:<deviceName>] searches a ToolboxST application for the first write occurrence of the specified variable. If never written, the first read-only location is used. If the variable is not found, a message box displays.
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. Opening a ToolboxST System
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.
Opening a ToolboxST Component and Navigating to a Variable The format for ToolboxST variable names is
<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
ToolboxST /Variable: G1.Var - the G1 component of the most recently loaded ToolboxST system will be searched.
ToolboxST c:\site\mySystem\mySystem.tcw /Variable: G1.Var - the G1 component of the c:\site\mySystem\MySystem.tcw system will be searched.
Go To Hardware Diagnostic
/HardwareDiagnostic:<devName> [.HardwareGroup] - navigates to either the Device Diagnostics window or the Hardware Module Group.
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. /NavigateToLocator:<locator string shown in Find results>
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.
Copy the selected Find results to the clipboard to use as a locator command argument. ToolboxST opens the component, then navigates to the specified location in the configuration.
-NoSplash
If the text –NoSplash is contained in an argument, the splash screen does not display when the ToolboxST application starts.
Archive a ToolboxST System
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.
ToolboxST c:\MySystem.tcw /archive
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 specified archive name, is created.
ToolboxST c:\MySystem.tcw /archive:c:\MyArchiveFolder
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.
USB Protection Device (UPD or dongle)
The UPD must be installed in an empty USB port on your computer. Each UPD is programmed at the factory with one or more application keys that control access to software products produced by GE. The ToolboxST application will only function if your UPD contains a valid ToolboxST application key.
Installing the UPD
It is very important to NOT plug the UPD into your computer until after you have installed the ToolboxST application.
To install the UPD
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.
3 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.
Reinstalling UPD
To reinstall the UPD
1 Save and close any open applications/systems. 2 Unplug the UPD.
3 From Windows, click Start, Settings, and then select Control Panel. 4 From the Control Panel, select Administrative Tools and Computer
Management and use the Device Manager to reinstall the UPD.
6 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.
Check that you have installed the proper UPD
correctly and click Retry.
Acronyms and Abbreviations
EGD Ethernet Global Data EMT EGD Management Tool
EU Engineering Units
HMI Human-Machine Interface
NVRAM Non-volatile Random Access Memory
OPC® OLE (Object Linking and Embedding) process control server
SDB System Database
SOE Sequence of Events TMR Triple modular redundant UDH Unit Data Highway UDP User Datagram Protocol UPD USB Protective Device USB Universal Serial Bus
C
H A P T E R2
Chapter 2 System Configuration
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 .
Opening and Creating Systems
To create a new system
1 From the File menu, select New System to display the New System dialog
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.
To open an existing system
1 From the File menu, select Open System.
2 Locate the .tcw configuration file for the system and select Open. The system
displays in the System Editor.
3 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 Summary View displays a graphic representation of all system components and their network connectivity.
The Tree View displays a list of all components in the system. The Property Editor allows
you to edit the selected component.
Components and Tools
Systems consist of multiple components that display in both the Tree View and the Summary View of the System Editor. The System Editor serves as a navigation tool to open more detailed Component Editors for editing or viewing. You can double-click most components in either the Tree View or the Summary View to edit them. ToolboxST component icons that display in the Tree View are as follows:
Icon Components
System
Group of Components
Mark VIe component
Mark VIeS component
Mark VI component
EX2100ST component
Power Conversion component
WorkstationST Printer Library Container Network Trender Watch Windows LiveView
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.
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
Moving and Copying Components
Components can be moved within a ToolboxST application using a drag-and drop operation. Drag-and-drop editing is only available if the System Editor is in View By Group mode, as the components are automatically organized when View By Type mode is selected. The default drag-and-drop operation for most components is move. Some components support a secondary drag-and-drop operation (usually copy) that can be accessed by holding down the CTRL key while dragging.
The cursor changes to one of the following cursors during a drag-and-drop operation to indicate the predicted outcome of the operation:
• indicates that the item being dragged cannot be dropped at the location currently beneath the cursor.
• indicates that the item being dragged will be moved to the location beneath the cursor.
• indicates that the item being dragged will be copied and the copy will be placed at the location beneath the cursor
Most components can be moved and copied in the Tree View, with a few exceptions: • Library Containers cannot be contained inside groups, so they can only be
copied to the system item and never moved.
• When a group is copied, a new group is created. The contents of the old group remain in place and are not copied to the new group.
• No drag-and-drop operations are supported for networks.
Tip You can import components and Library Containers from either another copy
of 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
System Editor Status
When a ToolboxST system goes online, the status for all active components in that system displays next to the component icon in the Summary View.
The following status icons can display.
Icon Status Indicates
Healthy Component Diagnostics – No
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
EGD Diagnostics – Yes I/O Diagnostics – Yes
Number of Forced Variables – 1 DDR Equality – Not equal
Configuration Equality – Not equal Component was added after the system went online
Logic forcing procedures can result in personal injury or death, if not strictly followed. Only adequately trained personnel should modify any programmable machine. Forcing of control logic for an operating process is strongly discouraged.
Forcing of protective functions is never permissible for an operating unit. All safety measures should be strictly enforced in conjunction with this procedure.
Configuring External Devices
When you add an External Device to the system, you must configure the component with information about both the external application and the configuration file connected to the device. When an External Device is properly configured, the external application starts and opens the configuration device when the component is double-clicked in the ToolboxST application.
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
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. 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.
Configuration Files
Folder Structure
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 Editor Tree View Windows Explorer Folder View
System Folder is the top-level folder that contains all others. It always has the
same name as the system. (In the example for this section, the system folder is named System1.) Files in the folder include:
• System1.tcw, containing top-level information for each component in the system.
• FormatSpecifications.xml, containing format specifications that define units and scaling information for data display.
• SystemDiagram.xml, containing information about the system block diagram including both the basic diagram structure and additional drawing shapes that have been added.
Component Folders contain configuration files for each component in the
system. In the example system, the G1 folder corresponds to a controller named G1. The exact structure of each component folder varies with the type of component, but all component folders have a Device.xml file that contains basic information about the component.
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:
• Library.xml, containing attributes of the Library Container and a listing of all libraries.
• _Mylibname.xml, a file created for each library in the Container (where Mylibname is the name of the library).
• BlockwareDiagrams, a folder containing the diagrams for user blocks defined in each library.
File Formats
All configuration data for the ToolboxST application is stored in eXtensible Markup Language (.xml) format.
The .xml files used by the ToolboxST application should NEVER be modified by ANY other 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.
Some controller components offer a Build command that produces files to be downloaded directly to the controller. These files, which are stored in the Output folder of a component, are in a binary format, and are not human-readable.
System Options
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 view system options
From the System Editor, select the Options menu, and then select Settings to display the Settings 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.
Main Font is the font used for most application text.
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.
• Automatic mode creates backup files in a device.zip file during a Build command, and provides an option to download the device.zip in the Download Wizard.
• Manual mode does not create a device.zip file so there is no option to download back-up files from the Download Wizard.
Incremental Build Enabled, if set to True, enables incremental downloads with
controllers that support them.
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.
User Identification is the three-character ID of the user making the changes.
System Editor Menus
Menu Command Use to
File New System Create a new system
Open System Open an existing system
Close System Close the current system
Save System Save system-level changes to the current system (does not save component-level changes)
Save System As
Save the current system with a new name or to a new location
Archive System
Select system components to be archived
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 Information
Display the System Information Editor (refer to the section System
Information Editor)
Selected component
Display the Component Editor for the item currently selected in the Tree View
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
Configuration Server
Perform one of the following:
View Differences opens a configuration view window. Work Offline allows you to work offline.
Network Status Viewer
Display defined networks in the system
System Online Work online
Options Settings Configure system settings (refer to the section System Options)
Window Cascade Arrange open Component Editors in a layered style
Tile Arrange open Component Editors in a grid style
Close All Close all open Component Editors
CMS Refer to the section CMS Menu Items.
Help Contents Display the online product documentation
Release Notes Display current information about your ToolboxST software version.
Send Problem Report
System Information Editor
The System Information Editor edits alarm classes, format specifications, and other items available to all components in the system. If access to a System Database (SDB) is enabled, the contents of the System Information Editor can be stored to the SDB.
To open the System Information Editor
From the System Editor, select System Information from the Edit menu. Or,
From the System Editor, double-click the System item in the Tree
View.
Alarm Classes
Alarm classes are groups or collections of related alarms that share a common priority and color scheme.
To edit Alarm Classes
2 From the Tree View, select Alarm Classes. A data grid with the existing
The following properties are available in the Property Editor when an Alarm Class is selected:
Name displays the name of the Alarm Class. Limited to five characters if using an
SDB.
Description displays the Alarm Classes description. Only the first 50 characters are
stored in an SDB.
Priority shows alarm class priority (1 to 99 where 1 is the highest priority). Ack Foreground Color shows foreground color for an alarm in the
Acknowledged state.
Ack Background Color shows background color for an alarm in the
Acknowledged state.
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 Enabled, if set to True, enables blinking ability.
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.
Diagnostic Translations
The Diagnostic Translations option allows you to display alarm diagnostic text in a second language.
Note The second Language option must be selected in the System Editor Property
To export diagnostics to a .csv file
1 From the System Editor Tree View, double-click the system item. The System Information Editor displays.
From the Tree View, right-click
Diagnostic Translations, then
select Export Product
Diagnostics….
The Please select a file to Export
the Product Diagnostic
Translations to window 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
Note Expand the Diagnostic Translations item to display each I/O pack in the
system, as well as packs for Mark VIe and certain diagnostics grouped as Common. Translations for common diagnostics only need to be entered once.
Diagnostics text can be translated in either the .csv file or in the System Information Editor.
Export These Diagnostics
The Export these Diagnostics…. option exports the translated text back to the .csv file. This can be done from either Tree View item.
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
To add a missing translation to a running system
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.
Note If the controller configuration in the ToolboxST application is equal to the
configuration running on the controller, the new information is published to the EGD Config Server. The next time the diagnostic occurs, the translated text displays. If the configuration and the running controller are not equal, the controller must be
Displaying Second-Language Diagnostics
Displaying second-language diagnostics can be selected from two different locations.
To display second-language diagnostics
From the WorkstationST component Tree
View, select the General tab and
the General item.
From the Property
Editor, select Use Second Language.
If you want all other users of this WorkstationST to be able to display a second language, select True. Or
From the WorkstationST tray icon, right-click to display Regional Settings and select User Second Language.
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.
Creating a Master WorkstationST
To avoid having diagnostic alarm text stored on every WorkstationST in a system, a Master WorkstationST can be configured.
To configure a Master WorkstationST
From the System Editor
Property Editor, select Master Location. From
the drop-down list, select the WorkstationST to designate as the master. Enter the Path to the files.
An example is RootPath\Help\Diagnostics\PAIC\PAICDiags.sp.chm, where
RootPath is the path configured in the System Property Editor. Refer to GEI-100620, WorkstationST Alarm Viewer, for more information about viewing language options.
Sound Options
Use the System Information Editor to define sound options that can annunciate certain sounds within the Alarm Viewer. A specific sound definition is assigned to an alarm class.
To configure sounds
♦ From the System Editor, select the Edit menu, then select System
Information.
From the Tree View, select Sounds.
In the Data Grid, enter a sound Name, for example,
Chimes. Right-click the Sound Type column, then
select from the drop-down list (for example, Wave File).
From the Wave File column, click the ellipsis button to display a Windows Open screen.
From the Open screen, navigate to
Windows \ Media to select the desired .wav
To edit sounds
From the System Editor, select the Edit menu, then select System
Information.
From the Tree View, select Sounds .
Currently configured sounds display in the Data Grid .
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.
Duration displays the sound’s duration (from 100 to 10,000 ms). Frequency displays the sound’s frequency (range is 100 to 500 Hz). Name is the sound’s name.
Repeat Quantity displays the number of times the sound is repeated.
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.
Plant Areas
Plant areas are locations that represent a plant or facility within the control system. These locations are selected from the Plant Area property of all variables defined in each system component. One or more variables can use the same location. These locations are used for filtering the alarms that display in the Alarm Viewer.
To edit plant areas
From the System Editor, select the Edit menu, then select System
Information.
Right-click any plant area to display a drop- down menu with additional options.
Format Specifications
Format specifications control how variables are presented in an HMI. Format specifications are grouped into sets, which establish a relationship between different measurement systems for a particular type of data. For example, a Format
Specification Set for temperature could contain two specifications for temperature – one for degrees Fahrenheit in the U.S. measurement system and one for degrees Celsius in the International System of Units (commonly referred to as the Metric system).
The Engineering Min and Max values for both format specifications control the conversions that take place when a measurement system is selected at an HMI. For example, if a temperature variable is assigned to the Celsius format specification and the measurement system in use on the HMI is Metric, no conversion is performed on the HMI displayed value. If the 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:
min min max min max min
2
)
1
1
(
)
2
2
(
)
1
(
1 2fs
fs
fs
fs
fs
fs
val
Val
fs fs+
−
−
∗
−
=
: The converted value, in Format Specification 2
: The initial value, in Format Specification 1
: The engineering max for Format Specification 1
: The engineering min for Format Specification 1
: The engineering max for Format Specification 2
: The engineering min for Format Specification 2 1 fs 2
Val
fsVal
max1
fs
min1
fs
max2
fs
min2
fs
Using this formula, a conversion from Celsius to Fahrenheit would be calculated by the HMI as follows:
min min max min max min
fs
F
C
fs
C
fs
F
fs
F
fs
C
fs
c
val
Val
F o o o o o oo
o
=
−
∗
−
−
+
)
(
)
(
)
(
32
)
0
100
(
)
32
212
(
)
0
(
+
−
−
∗
−
=
val
c
Val
o
Fo
Within a Format Specification Set, all Engineering Min values must represent the same physical value and all Engineering Max values must represent the same physical value.
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.
To create a Format Specification Set
1 From the System Editor Edit menu, select System Information. 2 In the System Information Editor, right-click the Format Specification
Sets item in the Tree View and select Add Format Specification Set. 3 Enter a name for the new set and click OK.
To add format specifications to a Format Specification Set 1 From the System Editor Edit Menu, select System Information. 2 In the System Information Editor Tree View, click a Format
Specification Set. A grid of format specifications displays in the Summary View.
The properties from the
Summary View also display
in the Property Editor for the currently selected row(s).
Click the Name box in the append row, then enter a new name to add a new format specification.
Click in a grid cell to edit its contents.
The following properties are available in the Property Editor when a Format Specification Set is selected:
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.
Measurement System displays the measurement system (for example, Metric or
U.S.) to which the unit belongs. (Refer to the section, Measurement Systems )
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
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.
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 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
Different views of HMI screen files can be obtained by selecting any one of the WorkstationST component items in the Tree View.
Adding and Deleting HMI Screen Files
To add an HMI screen file to the system
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. To delete an HMI screen file from the system
1 From the Summary View, select the screen file to be deleted.
2 Either right-click the screen file and select Delete or from the toolbar, click the Delete icon, or from the Edit menu, select Delete.
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.
Defining HMI Screen Use
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.
To define the use of HMI screens for a WorkstationST
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.
When a particular WorkstationST is selected in the Tree View, the Use property can also be changed from both the Summary View and the Property Editor.
From the Tree View, select a WorkstationST (for example, HMIws1).
From the Summary
View, the use of a
particular screen can be enabled by selecting True.
The use of the screen selected in the
Summary View can
also be enabled in the
Property Editor.
Downloading HMI Screen Files
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.
When pre-configured, WorkstationST runtime periodically compares the date of the Master screen file to the file being used by the HMI project on the WorkstationST. When an HMI screen file is saved to the Master location, it’s date changes. The WorkstationST detects the change and automatically copies the new file to the WorkstationST’s HMI project.
Note If a WorkstationST is configured for automatic download, a manual download
